En iAN8K B1000 Operation Guide R3.2 V1

Hardware Platform: iAN8KB1000

Issue 1.1

Release 3.2Operations Manual

iAN8K B1000

Hardware Platform: iAN8KB1000

Issue 1.1

iAN8K B1000®

Release 3.2Operations Manual

Copyright © 2006, UTStarcom, Inc. All rights reserved. No part of this documentation may be reproduced in any form or byany means or used to make any derivative work (such as translation, transformation, or adaptation) without prior writtenpermission from UTStarcom, Inc.

UTStarcom, Inc. reserves the right to revise this documentation and to make changes in content from time to time withoutobligation on the part of UTStarcom, Inc. to provide notification of such revision or change.

UTStarcom, Inc. provides this documentation without warranty of any kind, either implied or expressed, including, but notlimited to, the implied warranties of merchantability and fitness for a particular purpose. UTStarcom may make improvementsor changes in the product(s) and/or the program(s) described in this documentation at any time.

UNITED STATES GOVERNMENT LEGENDS:If you are a United States government agency, then this documentation and the software described herein are provided to yousubject to the following:

United States Government Legend: All technical data and computer software is commercial in nature and developed solelyat private expense. Software is delivered as Commercial Computer Software as defined in DFARS 252.227-7014 (June 1995)or as a commercial item as defined in FAR 2.101(a) and as such is provided with only such rights as are provided inUTStarcom's standard commercial license for the Software. Technical data is provided with limited rights only as provided inDFAR 252.227-7015 (Nov 1995) or FAR 52.227-14 (June 1987), whichever is applicable. You agree not to remove or defaceany portion of any legend provided on any licensed program or documentation contained in, or delivered to you in conjunctionwith, this User Guide.

UTStarcom, the UTStarcom logo, !-Volution, AIRSTAR, AN-2000, AN-FTTB, CommWorks, the CommWorks logo, iAN, iCell,Internode, Intranode, iPATH, ISP, MovingMedia, mSwitch, Next Generation Network Technology. Now, NGDLC, PAS, PASWireless, Seamless World, Softexchange, Sonata, Sonata Access Tandem, Sonata HLR, Sonata IP, Sonata MSC, SonataWLL, Telos, Total Control, Unitech, WACOS, WICOPS, WLL, and Xtreme IP are registered trademarks or trademarks ofUTStarcom, Inc. and its subsidiaries.

Intel and Pentium are registered trademarks of the Intel Corporation or its subsidiaries in the United States and othercountries. Microsoft, Windows, Windows NT, and NetMeeting are registered trademarks of Microsoft Corporation. Sun, Java,and Solaris are trademarks or registered trademarks of Sun Microsystems, Inc. Oracle is a registered trademark of OracleCorporation. HP, HP-UX, and HP Openview are trademarks or registered trademarks of the Hewlett-Packard Company.

Other brand and product names may be registered trademarks or trademarks of their respective holders.

CONTENTS

ABOUT THIS GUIDEOrder of Tasks.......................................................................................................................... 23Conventions ............................................................................................................................. 23

Notices................................................................................................................................ 24Figures and Screen Captures............................................................................................. 24Text ..................................................................................................................................... 24

Related Documentation............................................................................................................ 25Contacting Customer Service .................................................................................................. 25Contacting Technical Documentation....................................................................................... 25

1 NETWORK MANAGEMENTSystem Structure...................................................................................................................... 27Functional Components ........................................................................................................... 27Primary Management Functions .............................................................................................. 28

Basic Management Functions ............................................................................................ 28Topology Management.................................................................................................. 28Fault Management ........................................................................................................ 28Security Management ................................................................................................... 28Log Management .......................................................................................................... 28System Tools................................................................................................................. 29

2 DEVICE MANAGERConfiguration Menu.................................................................................................................. 33

Get Configuration ............................................................................................................... 33Save Configuration ............................................................................................................. 33Erase Configuration............................................................................................................ 33Erase Shelf Configuration................................................................................................... 34System Log......................................................................................................................... 34

System Log Data........................................................................................................... 37Radius Server..................................................................................................................... 40

RADIUS Server ............................................................................................................. 41Statistics ........................................................................................................................ 42

Telnet Port .......................................................................................................................... 43Maximum Power Setting..................................................................................................... 44Packet Count Reset............................................................................................................ 45Node ID .............................................................................................................................. 45iSmart Feature.................................................................................................................... 46LTC Configure .................................................................................................................... 47

Profile Menu............................................................................................................................. 50ADSL Line Profile ............................................................................................................... 50

iAN8K B1000 July 2006 Operations Manual

6

Configuration Template ................................................................................................. 50Service Profile............................................................................................................... 51Spectrum Profile............................................................................................................ 53

SHDSL Line Profile ............................................................................................................ 58Ethernet PM Profile ............................................................................................................ 61ADSL PM Profile ................................................................................................................ 63Access List Profile .............................................................................................................. 65Packet Priority Classification .............................................................................................. 70Traffic Management Profile ................................................................................................ 78

Batch Menu.............................................................................................................................. 81Create ATM VC .................................................................................................................. 81Delete ATM VC................................................................................................................... 83Module Configuration ......................................................................................................... 84

Video Service Menu................................................................................................................. 87Multicast Group Packaging ................................................................................................ 88

Default Rate .................................................................................................................. 88Multicast Group............................................................................................................. 89Multicast Package......................................................................................................... 91

Access Control ................................................................................................................... 92Account lockout Policy .................................................................................................. 92Reset Period ................................................................................................................. 93User Account ................................................................................................................ 94

Usage Statistics.................................................................................................................. 96Call Usage Recognition Time........................................................................................ 96Usage Statistics ............................................................................................................ 96

Tools Menu .............................................................................................................................. 97MAC Tracing....................................................................................................................... 97

3 PROVISIONING - NODESystem..................................................................................................................................... 99IP Address ............................................................................................................................. 100Time Server ........................................................................................................................... 103NMP Access .......................................................................................................................... 104

SNMP ............................................................................................................................... 105Telnet................................................................................................................................ 106

ARP ....................................................................................................................................... 107Routing Table......................................................................................................................... 109Reset ......................................................................................................................................111Master Shelf Configuration .................................................................................................... 114Slave Shelves Configuration.................................................................................................. 116Linecard Image File Information ............................................................................................ 118

4 PROVISIONING - ICM3/3G MODULENode Level Configuration ...................................................................................................... 123

Reset ................................................................................................................................ 123Module Summary................................................................................................................... 124

iAN8K B1000 Operations Manual July 2006

7

Shelf Level Configuration....................................................................................................... 126Slot Level Configuration......................................................................................................... 128

ICM3/3G ........................................................................................................................... 129Forwarding Database ....................................................................................................... 130Mirror Port......................................................................................................................... 132Trunk Group...................................................................................................................... 134Protection Link.................................................................................................................. 137Redundancy Support........................................................................................................ 139

Redundancy Setup via CLI ......................................................................................... 143Switchover ........................................................................................................................ 144VBAS ................................................................................................................................ 145External Ethernet Port ...................................................................................................... 147

Port Level Configuration ........................................................................................................ 148Ethernet Port Configuration .............................................................................................. 149

Internal Ethernet Ports ................................................................................................ 150External Ethernet Ports ............................................................................................... 152Trunk Ports.................................................................................................................. 155

RSTP ................................................................................................................................ 158RSTP........................................................................................................................... 158RSTP Port ................................................................................................................... 160

VLAN ................................................................................................................................ 162General ....................................................................................................................... 165VLAN Setup ................................................................................................................ 167Routed VLAN Interface ............................................................................................... 170In-band Management .................................................................................................. 173

Multicast ........................................................................................................................... 175IGMP Snooping........................................................................................................... 178

General .................................................................................................................. 178Group Membership................................................................................................ 179

IGMP Proxy................................................................................................................. 180General .................................................................................................................. 180Group Membership................................................................................................ 181

PIM-SM ....................................................................................................................... 182General .................................................................................................................. 182RP Router .............................................................................................................. 183Multicast Routing Table ......................................................................................... 185Neighbor Details .................................................................................................... 185Interface Setup ...................................................................................................... 186

Routing ............................................................................................................................. 188RIP .............................................................................................................................. 191

General .................................................................................................................. 191Redistribution Setup .............................................................................................. 192Neighbor Setup...................................................................................................... 194Peer Details ........................................................................................................... 195Key Setup .............................................................................................................. 196Interface Setup ...................................................................................................... 198

OSPF .......................................................................................................................... 201


8

General.................................................................................................................. 201Route Redistribution.............................................................................................. 203Area Setup............................................................................................................. 205Address Ranges.................................................................................................... 208LSDB Table............................................................................................................ 209Neighbor Details .................................................................................................... 212Interface Setup ...................................................................................................... 213

ARP............................................................................................................................. 216DHCP ............................................................................................................................... 219

Server ......................................................................................................................... 219Profile.......................................................................................................................... 220Subnet Mapping.......................................................................................................... 224Pool............................................................................................................................. 226Map............................................................................................................................. 228Lease .......................................................................................................................... 230Option 60 .................................................................................................................... 231Option 82 .................................................................................................................... 233VLAN........................................................................................................................... 234

Packet Classification ........................................................................................................ 236Masks.......................................................................................................................... 236Actions ........................................................................................................................ 239Meters ......................................................................................................................... 242Flow Counters............................................................................................................. 243Rules........................................................................................................................... 244

QoS .................................................................................................................................. 246Priority......................................................................................................................... 247DSCP Priority.............................................................................................................. 248Queue Mapping .......................................................................................................... 250L2 Scheduling ............................................................................................................. 252

5 PROVISIONING - PCU MODULENode Level Configuration ...................................................................................................... 255

Reset ................................................................................................................................ 255Module Summary................................................................................................................... 256Shelf Level Configuration....................................................................................................... 257Slot Level Configuration......................................................................................................... 258

PCU.................................................................................................................................. 259Clock Source .................................................................................................................... 259Alarm Indication................................................................................................................ 261PDP .................................................................................................................................. 262

6 PROVISIONING - IFXS1 MODULEViewing iFXS1 Module Information........................................................................................ 265Configuring Module IP Address ............................................................................................. 266Configuring MG Interface....................................................................................................... 268

Configuring Call Server .................................................................................................... 268


9

Configuring Misc............................................................................................................... 269Configuring T.38 ............................................................................................................... 270

Configuring QoS .................................................................................................................... 271Configuring TOS/DSCP.................................................................................................... 271Configuring VLAN Tag ...................................................................................................... 272

Configuring User Interface ..................................................................................................... 274Node Configuration........................................................................................................... 274Port Configuration............................................................................................................. 275

Modifying a FXS Port .................................................................................................. 277Configuring Ring Definition............................................................................................... 277

Configuring MG Media ........................................................................................................... 279Configuring VoIP Media.................................................................................................... 279Configuring Jitter Buffer .................................................................................................... 280

Configuring SIP...................................................................................................................... 282Configuring SIP Port......................................................................................................... 282SIP Summary Statistics .................................................................................................... 283SIP Supported Methods ................................................................................................... 283SIP Methods Statistics...................................................................................................... 284

Configuring SIP UA................................................................................................................ 285General Config ................................................................................................................. 285Server Table ..................................................................................................................... 286MG Table .......................................................................................................................... 287User Table ........................................................................................................................ 288

7 PROVISIONING - IPXDSL MODULENode Level Configuration ...................................................................................................... 292

Reset ................................................................................................................................ 292Module Summary................................................................................................................... 294

Module Information........................................................................................................... 294Active Ports ...................................................................................................................... 294

Shelf Level Configuration....................................................................................................... 295Virtual Board Assignment ................................................................................................. 297

Module Level Configuration ................................................................................................... 298IPxDSL ............................................................................................................................. 298Customized Filter..............................................................................................................299

Semi-Static Forwarding ............................................................................................... 299Gateway ARP Filter..................................................................................................... 300Aging Timer................................................................................................................. 300Upstream Multicast Filter ............................................................................................ 300ARP Tracking .............................................................................................................. 302NetBIOS Filter ............................................................................................................. 303DHCP Filter ................................................................................................................. 303DLF Counter................................................................................................................ 304IGMP Snooping........................................................................................................... 304DHCP Option82 .......................................................................................................... 305

Test Timeout ..................................................................................................................... 309PPPoE Snooping.............................................................................................................. 310


10

Port Level Configuration ........................................................................................................ 311WAN Port.......................................................................................................................... 312xDSL................................................................................................................................. 313

ADSL Port ................................................................................................................... 314SHDSL Port ................................................................................................................ 315Line Status .................................................................................................................. 317Channel Status............................................................................................................ 320Previous Status ........................................................................................................... 321Status Change Time Info............................................................................................. 322Rate Summary ............................................................................................................ 323Port Label.................................................................................................................... 324Bit Loading .................................................................................................................. 325iSmart.......................................................................................................................... 326CPE............................................................................................................................. 328

ATM .................................................................................................................................. 330ATM VC....................................................................................................................... 331Traffic Profile ............................................................................................................... 332

Bridge ............................................................................................................................... 335MAC Address Per Port................................................................................................ 335Packet Policing ........................................................................................................... 337

Packet Policing Setup............................................................................................ 337IP Address Summary............................................................................................. 339

Forwarding Database.................................................................................................. 339ARP Table ................................................................................................................... 342Flood Limit .................................................................................................................. 343

IGMP ................................................................................................................................ 344Authentication Parameter ........................................................................................... 344CAC ............................................................................................................................ 345Multicast Group........................................................................................................... 346Multicast Host ............................................................................................................. 347

VLAN ................................................................................................................................ 348VLAN........................................................................................................................... 349Ingress Rule................................................................................................................ 351VLAN Untag ................................................................................................................ 353

Access List ....................................................................................................................... 353QoS .................................................................................................................................. 356

Packet Priority............................................................................................................. 358Port Based Priority ...................................................................................................... 360802.1p Tag .................................................................................................................. 362

8 PERFORMANCE MANAGEMENTICM3 Module ......................................................................................................................... 366

Ethernet PM ..................................................................................................................... 366General Counters........................................................................................................ 366Error Counters ............................................................................................................ 368Traffic Load ................................................................................................................. 370

Bridge PM......................................................................................................................... 371


11

Control......................................................................................................................... 3715 Minutes Report......................................................................................................... 37215 Minutes Report....................................................................................................... 373

IPADSLx Module .................................................................................................................... 373ATM PVC.......................................................................................................................... 374Bridge Port........................................................................................................................ 374

Bridge PM Control....................................................................................................... 375Bridge.......................................................................................................................... 3755 Minutes Report......................................................................................................... 37715 Minutes Report....................................................................................................... 378

WAN Port.......................................................................................................................... 378Threshold Controls...................................................................................................... 37815 Minutes................................................................................................................... 37924 Hours...................................................................................................................... 381

ADSL Port......................................................................................................................... 381ADSL 15 Minutes Summary........................................................................................ 381ADSL 24 Hours Summary........................................................................................... 383Threshold Controls...................................................................................................... 383ATUC 15 Minutes ........................................................................................................ 384ATUC 24 Hours ........................................................................................................... 386ATUR 15 Minutes ........................................................................................................ 386ATUR 24 Hours ........................................................................................................... 386Channel Level ............................................................................................................. 386

Downstream 15 Minutes........................................................................................ 386Downstream 24 Hours........................................................................................... 387Upstream 15 Minutes............................................................................................. 387Upstream 24 Hours................................................................................................ 387

IPSHDSL3 Module................................................................................................................. 388

9 DIAGNOSTICSF4/F5 Loopback ..................................................................................................................... 391DELT ...................................................................................................................................... 394SELT ...................................................................................................................................... 399

10 FAULT MANAGEMENTNetman 4000 ......................................................................................................................... 406

Audible And Visual Alarm ................................................................................................. 406Alarm Presentation ........................................................................................................... 406

Alarm Report .......................................................................................................................... 407Alarm Report .................................................................................................................... 408Alarm Summary................................................................................................................ 412Filter Setup ....................................................................................................................... 413

Alarm List ............................................................................................................................... 414Node Alarm....................................................................................................................... 415External Alarm .................................................................................................................. 416ICM3 Alarm....................................................................................................................... 416


12

IP-ADSLx Alarm ............................................................................................................... 416IP-SHDSL3 Alarm ............................................................................................................ 418iFXS1 Alarm ..................................................................................................................... 419Event List for iFXS1 Module............................................................................................. 420

11 SYSTEM ADMINISTRATIONNode File Management ......................................................................................................... 423Software Upgrade.................................................................................................................. 424

ICM3 Module .................................................................................................................... 424Upgrade with A Redundant ICM3 Module .................................................................. 425

IPxDSL Modules............................................................................................................... 427ISM Module ...................................................................................................................... 428ASM Module..................................................................................................................... 428

File Transfer........................................................................................................................... 428Download ......................................................................................................................... 431Upload .............................................................................................................................. 432Delete ............................................................................................................................... 432

ICM3 Module Backup ............................................................................................................ 432ICM3 Module Replacement ................................................................................................... 433Remote Access...................................................................................................................... 435

A ACCESS CONFIGURATION EXAMPLEPPPoE Access Deny Configuration Example........................................................................ 437

Scenario ........................................................................................................................... 437Analysis ............................................................................................................................ 437Solution ............................................................................................................................ 438Conclusion........................................................................................................................ 443

IP Address Conflict ................................................................................................................ 443Scenario ........................................................................................................................... 443Analysis ............................................................................................................................ 443Solution ............................................................................................................................ 444Conclusion........................................................................................................................ 449

Deny Specific Subscriber To Access FTP.............................................................................. 449Scenario ........................................................................................................................... 449Analysis ............................................................................................................................ 449Solution ............................................................................................................................ 449Conclusion........................................................................................................................ 456

Prohibit A Specific Subscriber To Access ABC IM Service.................................................... 456Scenario ........................................................................................................................... 456Analysis ............................................................................................................................ 456Solution ............................................................................................................................ 457Conclusion........................................................................................................................ 463


13

LIST OF TABLESTable 1 Notice Icon Descriptions......................................................................................... 24Table 2 Text Convention Descriptions................................................................................. 24Table 3 iAN8K B1000 Release 3.1 Documentation Set ...................................................... 25Table 4 Configuration - System Log Table .......................................................................... 36Table 5 Configuration - RADIUS Server - RADIUS Server - Add Table.............................. 42Table 6 RADIUS Server - RADIUS Server - Statistics Table .............................................. 43Table 7 Profile - ADSL Line Profile - Service Profile Table ................................................. 53Table 8 Profile - ADSL Line Profile - Spectrum Profile Table .............................................. 56Table 9 Line Standard / Line Card Co-relation Table .......................................................... 58

Table 10 Profile - SHDSL Line Profile - Add Table............................................................... 60Table 11 Profile - Ethernet PM Profile Table ......................................................................... 62Table 12 Profile - ADSL PM Profile Table ............................................................................. 64Table 13 Profile - Access List Profile - Add - From / To Table .............................................. 67Table 14 ACL Rule Combination Table ................................................................................. 67Table 15 Profile - Packet Priority Classification Table........................................................... 71Table 16 Profile - Packet Priority Classification - Add - Type Table ...................................... 71Table 17 Profile - Traffic Management Profile - Add / Modify Tables .................................... 80Table 18 Batch - Create ATM VC Table................................................................................ 83Table 19 Batch - Module Configuration Tables .................................................................... 85Table 20 Video Service - Multicast Group Packaging - Multicast Group Field Description ... 89Table 21 Video Service - Multicast Group Packaging - Multicast Package Field Description91Table 22 Video Service - Access Control - Account Lockout Policy Field Description.......... 93Table 23 Node - System Table............................................................................................ 100Table 24 Node - IP Address Table ...................................................................................... 101Table 25 Node - ARP Field Description............................................................................... 108Table 26 Node - Routing Table Table ................................................................................. 110Table 27 Node - Master Shelf Configuration Table ............................................................. 115Table 28 Node - Slav Shelves Configuration Table............................................................. 117Table 29 Node - Linecard Image File Information Table ..................................................... 119Table 30 ICM3/3G - Module Summary Table...................................................................... 126Table 31 ICM3/3G Module Placements Details................................................................... 128Table 32 ICM3/3G - ICM3/3G Table.................................................................................... 130Table 33 ICM3/3G - Forwarding Database Table................................................................ 131Table 34 ICM3/3G - Mirror Port Table ................................................................................. 134Table 35 ICM3/3G - Trunk Group Table.............................................................................. 136Table 36 ICM3/3G - Protection Link Table .......................................................................... 139Table 37 ICM3/3G - VBAS Table ........................................................................................ 147Table 38 ICM3/3G - Ethernet Port Configuration - Internal Ethernet Ports Table ............... 152Table 39 ICM3/3G - Ethernet Port Configuration - External Ethernet Ports Table .............. 154Table 40 ICM3/3G - Ethernet Port Configuration - Trunk Ports Table................................. 157Table 41 ICM3/3G - RSTP - RSTP Table............................................................................ 159Table 42 ICM3/3G - RSTP - RSTP Port Table .................................................................... 161Table 43 ICM3/3G - VLAN - General Table......................................................................... 166Table 44 ICM3/3G - VLAN - VLAN Setup Table.................................................................. 168Table 45 ICM3/3G - VLAN - VLAN Interface - Add Table ................................................... 173Table 46 ICM3 - VLAN -Inband VLAN Interface - Add Table .............................................. 175Table 47 ICM3/3G - Multicast - IGMP Snooping - General Table ....................................... 178Table 48 ICM3/3G - Multicast - IGMP Snooping - Group Membership Table ..................... 180Table 49 ICM3/3G - Multicast - IGMP Proxy - General Table ............................................. 181Table 50 ICM3 - Routing - Routing Table Field Descriptions .............................................. 189Table 51 ICM3 - Routing - RIP - General Table .................................................................. 192Table 52 ICM3 - Routing - RIP - Redistribution Setup Table............................................... 193


14

Table 53 ICM3 - Routing - RIP - Neighbor Details Table .....................................................195Table 54 ICM3 - Routing - RIP - Peer Details Table ............................................................196Table 55 ICM3 - Routing - RIP - Key Setup Table ...............................................................197Table 56 ICM3 - Routing - RIP - Interface Setup Table .......................................................199Table 57 ICM3 - Routing - OSPF - General Table ...............................................................202Table 58 ICM3 - Routing - OSPF - Route Redistribution Table ...........................................204Table 59 ICM3 - Routing - OSPF - Area Setup Table ..........................................................206Table 60 ICM3 - Routing - OSPF - Address Ranges Table .................................................208Table 61 ICM3 - Routing - OSPF - LSDB Table...................................................................210Table 62 ICM3 - Routing - OSPF - LSDB Table - LS Type Table ........................................211Table 63 ICM3 - Routing - OSPF - Neighbor Details Table .................................................213Table 64 ICM3 - Routing - OSPF - Interface Setup Table....................................................215Table 65 ICM3 - Routing - ARP Field Description................................................................217Table 66 ICM3/3G - DHCP - Server Field Description .........................................................220Table 67 ICM3/3G - DHCP - Profile - Add Table..................................................................223Table 68 ICM3/3G - Packet Classification - Masks - Add Field Description.........................238Table 69 ICM3/3G - Packet Classification - Actions - Add Field Description .......................241Table 70 ICM3/3G - Packet Classification - Meters - Add Field Description ........................243Table 71 ICM3/3G - QoS - DSCP Mapping..........................................................................252Table 72 ICM3/3G - QoS - L2 Scheduling - Weight for WRR / SP+WRR ............................254Table 73 PCU - Module Summary Table .............................................................................257Table 74 PCU Module Placements Details ..........................................................................258Table 75 PCU - PCU Table ..................................................................................................259Table 76 PCU - Clock Source Table ....................................................................................261Table 77 PCU - Alarm Indication Table................................................................................262Table 78 PCU - PDP Table ..................................................................................................263Table 79 iFXS1 Module Information Window Field Description ...........................................265Table 80 IP Configuration Window Field Description ...........................................................267Table 81 Call Server Window Field Description ...................................................................269Table 82 Misc Configuration Window Field Description .......................................................270Table 83 T.38 Window Field Descriptio................................................................................271Table 84 TOS/DSCP Window Field Description ..................................................................272Table 85 VLAN Tag Window Field Description ...................................................................274Table 86 Node Configuration Window Field Description......................................................275Table 87 Port Configuration Window Field Description........................................................276Table 88 Ring Definition Window Field Description .............................................................278Table 89 VoIP Media Window Field Description .................................................................280Table 90 Jitter Buffer Window Field Description .................................................................281Table 91 SIP Port Window Field Description .......................................................................283Table 92 SIP Supported Method Window Field Description ................................................284Table 93 General Configuration Window Field Description..................................................286Table 94 General Configuration Window Field Description..................................................287Table 95 MG Table Window Field Description ....................................................................288Table 96 User Table Window Field Description ...................................................................289Table 97 ICM3 - Module Summary - Module Information Table...........................................294Table 98 ICM3 - Module Summary - Active Ports Table ......................................................295Table 99 IPxDSL Module Placements Details......................................................................296Table 100 IPxDSL - IPxDSL Table.........................................................................................299Table 101 Format of Circuit ID Sub-option in DHCP Option 82 .............................................305Table 102 Format of Remote ID Sub-option in DHCP Option 82...........................................306Table 103 IPxDSL - Customized Filter Table .........................................................................307Table 104 IPxDSL - PPPoE Snooping Table .........................................................................311Table 105 IPxDSL - ADSL - ADSL Port Table .......................................................................315Table 106 IPxDSL - SHDSL - SHDSL Port Table ..................................................................316Table 107 IPxDSL - ADSL - Line Status Table ......................................................................318


15

Table 108 IPxDSL - SHDSL - Line Status Table ................................................................... 319Table 109 IPxDSL - ADSL - Channel Status Table ............................................................... 320Table 110 IPxDSL - ADSL - Status Change Time Info Table................................................ 323Table 111 IPxDSL - ADSL Rate Summary Table.................................................................. 324Table 112 IPxDSL - ADSL - CPE Table ................................................................................ 330Table 113 IPxDSL - ATM - ATM VC Encapsulation Table .................................................... 331Table 114 IPxDSL - Traffic Profile - Modification Table......................................................... 333Table 115 IPxDSL - Bridge - MAC Address Per Port Table .................................................. 336Table 116 IPxDSL - Bridge - Packet Policing - Packet Policing Setup Table........................ 338Table 117 IPxDSL - Bridge - Packet Policing IP Address Summary Table ........................... 339Table 118 IPxDSL - Bridge - Forwarding Database Table .................................................... 341Table 119 IPxDSL - Forwarding Database - Add Table ........................................................ 341Table 120 IPxDSL - Bridge - ARP Table ............................................................................... 343Table 121 IPxDSL - IGMP - Multicast Group Table............................................................... 347Table 122 IPxDSL - IGMP - Multicast Host Table ................................................................. 348Table 123 IPxDSL- QoS - Recommended User Priority to Traffic Class Mappings .............. 357Table 124 IPxDSL - QoS - 802.1p Tag Marking on Line Card .............................................. 358Table 125 IPxDSL - QoS - Port Based Priority - Tag Operation Table.................................. 362Table 126 ICM3 - Ethernet PM - General Counters Table .................................................... 367Table 127 ICM3 - Ethernet PM - Error Counters Table ......................................................... 369Table 128 ICM3 - Ethernet PM - Traffic Load Table.............................................................. 370Table 129 ICM3 - Bridge PM - Control Table ........................................................................ 371Table 130 ICM3 - Bridge PM - 5 Minutes Report Table ........................................................ 372Table 131 IPADSLx - ATM PVC Table.................................................................................. 374Table 132 IPADSLx - Bridge Port - Bridge PM Control Table ............................................... 375Table 133 IPADSLx - Bridge Port - Bridge Table .................................................................. 376Table 134 IPADSLx - Bridge Port - 5 Minutes Report Table ................................................. 377Table 135 IPADSLx - WAN Port - Thresholds Control Table ................................................ 379Table 136 IPADSLx - WAN Port - 15 Minutes Table ............................................................. 380Table 137 IPADSLx - ADSL Port - ADSL 15 Minutes Summary Table ................................. 382Table 138 IPADSLx - ADSL Port - Thresholds Control Table ............................................... 384Table 139 IPADSLx - ADSL Port - ATUC 15 Minutes Table ................................................. 385Table 140 IPADSLx - Channel - Downstream 15 Minutes Table .......................................... 387Table 141 IPSHDSL3 - Bridge Table..................................................................................... 388Table 142 SELT - Test Result Field Description ................................................................... 400Table 143 Node Alarm Tree Entity ........................................................................................ 407Table 144 Alarm Report - Subtree......................................................................................... 411Table 145 Alarm Report - Alarm Class.................................................................................. 412Table 146 Alarm Report - Alarm Severity.............................................................................. 412Table 147 Alarm Report - Alarm List Entity ........................................................................... 412Table 148 Node Alarm List .................................................................................................... 415Table 149 External Alarm List ............................................................................................... 416Table 150 ICM3 Alarm List .................................................................................................... 416Table 151 IP-ADSLx Alarm List ............................................................................................. 416Table 152 IP-SHDSL3 Alarm List .......................................................................................... 418Table 153 Alarm List of iFXS1 Based on SIP........................................................................ 419Table 154 Alarm List of RTP Related .................................................................................... 419Table 155 Alarm List of Uplink FE Interface .......................................................................... 420Table 156 Event List Based on SIP....................................................................................... 420Table 157 Basic Event List .................................................................................................... 421Table 158 Node File Description ........................................................................................... 424


16

LIST OF FIGURESFigure 1 Invoking Device Manager From Netman 4000 ..................................................... 31Figure 2 Device Manager Main Window ............................................................................. 32Figure 3 Configuration - Erase Configuring ........................................................................ 33Figure 4 Configuration - Erase Shelf Configuring Window ................................................. 34Figure 5 Configuration - System Log .................................................................................. 36Figure 6 Configuration - System Log - Add ........................................................................ 37Figure 7 Configuration - RADIUS Server - RADIUS Server ............................................... 41Figure 8 Configuration - RADIUS Server - RADIUS Server - Add ...................................... 41Figure 9 RADIUS Server - RADIUS Server - Statistics ...................................................... 43Figure 10 Configuration - Telnet Port ................................................................................... 44Figure 11 Configuration - Maximum Power Setting .............................................................. 44Figure 12 Configuration - Packet Count Reset ..................................................................... 45Figure 13 Configuration - Node ID ........................................................................................ 45Figure 14 Configuration - iSmart Feature ............................................................................. 47Figure 15 Configuration - LTC Configure ............................................................................. 48Figure 16 Configuration - LTC Configure - Add .................................................................... 48Figure 17 Configuration - LTC Configure - Configure - LTC Splitter ..................................... 49Figure 18 Configuration - LTC Configure - Configure - Test Timeout ................................... 50Figure 19 Profile - ADSL Line Profile - Configuration Template Window ............................. 51Figure 20 Profile - ADSL Line Profile - Configuration Template - Add Window .................... 51Figure 21 Profile - ADSL Line Profile - Service Profile Window ............................................ 52Figure 22 Profile - ADSL Line Profile - Service Profile - Add Window .................................. 52Figure 23 Profile - ADSL Line Profile - Spectrum Profile Window ........................................ 54Figure 24 Profile - ADSL Line Profile - Spectrum Profile - Add Window ............................... 55Figure 25 Profile - SHDSL Line Profile Window ................................................................... 59Figure 26 Profile - SHDSL Line Profile - Add Window .......................................................... 60Figure 27 Profile - Ethernet PM Profile ................................................................................. 62Figure 28 Profile - Ethernet PM Profile - Add / Modify .......................................................... 63Figure 29 Profile - ADSL PM Profile ..................................................................................... 64Figure 30 Profile - ADSL PM Profile - Add / Modify .............................................................. 65Figure 31 Profile - Access List Profile ................................................................................... 66Figure 32 Profile - Access List Profile - Add - Any to Any .................................................... 68Figure 33 Profile - Access List Profile - Add - ARP-Send-IP To ARP-Send-MAC ................ 68Figure 34 Profile - Access List Profile - Add - Ethernet Type To IP Address ........................ 69Figure 35 Profile - Access List Profile - Add - MAC Address To Protocol Type ................... 69Figure 36 Profile - Access List Profile - Add - TCP Port To UDP Port .................................. 70Figure 37 Profile - Packet Priority Classification Window ..................................................... 70Figure 38 Profile - Packet Priority Classification - Add - DSCP Window .............................. 72Figure 39 Profile - Packet Priority Classification - Add - VLAN ID Window .......................... 72Figure 40 Profile - Packet Priority Classification - Add - IP Protocol Type Window .............. 73Figure 41 Profile - Packet Priority Classification - Add - Send TCP Port .............................. 73Figure 42 Profile - Packet Priority Classification - Add - Send UDP Port ............................. 74Figure 43 Profile - Packet Priority Classification - Add - Receive TCP Port ......................... 74Figure 44 Profile - Packet Priority Classification - Add - Receive UDP Port ......................... 75Figure 45 Profile - Packet Priority Classification - Add - Source IP - IP Address With Subnet Mask 75Figure 46 Profile - Packet Priority Classification - Add - Source IP - IP Address Range ...... 76Figure 47 Profile - Packet Priority Classification - Add - Destination IP - IP Address With Subnet Mask 76Figure 48 Profile - Packet Priority Classification - Add - Destination IP - IP Address Range 77Figure 49 Profile - Packet Priority Classification - Add - Ethernet Type ............................... 77Figure 50 Profile - Packet Priority Classification - Add - TOS Bits ........................................ 78


17

Figure 51 Profile - Traffic Management Profile ..................................................................... 79Figure 52 Profile - Traffic Management Profile - Add / Modify - Strict Priority ...................... 79Figure 53 Profile - Traffic Management Profile - Add / Modify - Min/Max with Strict Priority 80Figure 54 Profile - Traffic Management Profile - Add / Modify - Min/Max with WRR ............ 80Figure 55 Batch - Create ATM VC Window .......................................................................... 82Figure 56 Batch - Delete ATM VC Window .......................................................................... 84Figure 57 Batch - Module Configuration Window ................................................................. 84Figure 58 Video Service - Multicast Group Packaging - Default Rate .................................. 88Figure 59 Video Service - Multicast Group Packaging - Multicast Group ............................. 89Figure 60 Video Service - Multicast Group Packaging - Multicast Group - Add ................... 90Figure 61 Video Service - Multicast Group Packaging - Multicast Package ......................... 91Figure 62 Video Service - Multicast Group Packaging - Multicast Package - Add ............... 92Figure 63 Video Service - Access Control - Account Lockout Policy .................................... 93Figure 64 Video Service - Access Control - Reset Period .................................................... 94Figure 65 Video Service - Access Control - User Account ................................................... 94Figure 66 Video Service - Multicast Group Packaging - User Account - Add ....................... 95Figure 67 Video Service - Usage Statistics - Call Usage Recognition Time ......................... 96Figure 68 Video Service - Usage Statistics - Usage Statistics ............................................. 97Figure 69 Tools - MAC Tracing ............................................................................................. 98Figure 70 Node - System Window ...................................................................................... 100Figure 71 Node - IP Address Window ................................................................................ 101Figure 72 Node - Time Server Window .............................................................................. 103Figure 73 Node - NMP Access Window ............................................................................. 105Figure 74 Node - NMP Access - Add SNMP Entry Window ............................................... 106Figure 75 Node - NMP Access - Add Telnet Entry Window ............................................... 106Figure 76 Node - ARP Window ........................................................................................... 108Figure 77 Node - ARP - Add Window ................................................................................. 109Figure 78 Node - Routing Table Window ............................................................................ 110Figure 79 Node - Routing Table - Add Window .................................................................. 111Figure 80 Node - Reset Window ......................................................................................... 113Figure 81 Node - Master Shelf Configuration Window ....................................................... 115Figure 82 Node - Slav Shelves Configuration Window ....................................................... 117Figure 83 Node - Linecard Image File Information Window ............................................... 119Figure 84 Provisioning - ICM3 Window .............................................................................. 121Figure 85 Provisioning - ICM3GWindow ............................................................................. 122Figure 86 ICM3 - Node - Reset Window ............................................................................. 124Figure 87 ICM3G- Module Summary Window .................................................................... 125Figure 88 ICM3- Module Summary Window ....................................................................... 126Figure 89 ICM3 - Shelf View Window ................................................................................. 127Figure 90 ICM3G - Shelf View Window .............................................................................. 128Figure 91 ICM3/3G - ICM3 Window .................................................................................... 129Figure 92 ICM3/3G - Forwarding Database Window .......................................................... 131Figure 93 ICM3/3G - Forwarding Database - Dynamic Entry Window ............................... 132Figure 94 ICM3/3G - Forwarding Database - Add Window ................................................ 132Figure 95 ICM3/3G - Mirror Port Window ........................................................................... 133Figure 96 ICM3/3G - Trunk Group Window ........................................................................ 135Figure 97 ICM3/3G - Trunk Group - Add Window .............................................................. 136Figure 98 ICM3/3G - Trunk Group - Add - Note Window .................................................... 137Figure 99 ICM3/3G - Protection Link Configuration ............................................................ 138Figure 100 ICM3/3G - Protection Link ................................................................................. 139Figure 101 ICM3/3G - Redundancy Support Window ......................................................... 143Figure 102 ICM3/3G - Switchover Widow ............................................................................ 145Figure 103 ICM3/3G - VBAS Widow .................................................................................... 147Figure 104 Standby ICM3/3G - External Ethernet Port Window .......................................... 148Figure 105 ICM3/3G - Ethernet Port Configuration - Internal Ethernet Ports Window ........ 151


18

Figure 106 ICM3/3G - Ethernet Port Configuration - Internal Ethernet Ports - Modify Window 152Figure 107 ICM3/3G - Ethernet Port Configuration - External Ethernet Ports Window ....... 153Figure 108 ICM3/3G - Ethernet Port Configuration - External Ethernet Ports - Modify Window 154Figure 109 ICM3/3G - Ethernet Port Configuration - Trunk Ports Window .......................... 156Figure 110 ICM3/3G - Ethernet Port Configuration - Trunk Ports - Modify Window ............ 157Figure 111 ICM3/3G - RSTP - RSTP Window ..................................................................... 159Figure 112 ICM3/3G - RSTP - RSTP Port Window ............................................................. 161Figure 113 ICM3/3G - VLAN Frame Forwarding with VLAN - Part 1 .................................. 163Figure 114 ICM3/3G - VLAN Frame Forwarding with VLAN - Part 2 .................................. 164Figure 115 ICM3G - VLAN - General Window ..................................................................... 165Figure 116 ICM3 - VLAN - General Window ....................................................................... 166Figure 117 ICM3G - VLAN - VLAN Setup Window .............................................................. 167Figure 118 ICM3 - VLAN - VLAN Setup Window ................................................................ 168Figure 119 ICM3/3G - VLAN - VLAN Setup - Add Window ................................................. 170Figure 120 ICM3G - VLAN - VLAN Interface Window ......................................................... 171Figure 121 ICM3 - VLAN - Routed VLAN Interface Window ............................................... 172Figure 122 ICM3/3G - VLAN - VLAN Interface - Add Window ............................................ 172Figure 123 ICM3 - VLAN - Inband VLAN Interfaces Window .............................................. 174Figure 124 ICM3 - VLAN - Inband VLAN Interfaces - Add VLAN Interface Window ........... 175Figure 125 ICM3G- Multicast Window ................................................................................. 176Figure 126 ICM3 - Multicast Window ................................................................................... 177Figure 127 ICM3 - Multicast - IGMP Snooping - General Window ...................................... 178Figure 128 ICM3 - Multicast - IGMP Snooping - Group Membership Window .................... 179Figure 129 ICM3 - Multicast - IGMP Proxy - General Window ............................................ 180Figure 130 ICM3 - Multicast - IGMP Proxy - Group Membership ........................................ 181Figure 131 ICM3 - Multicast - PIM-SM - General Window .................................................. 183Figure 132 ICM3 - Multicast - PIM-SM - RP Router Window .............................................. 184Figure 133 ICM3 - Multicast - PIM-SM - RP Router - Add Window ..................................... 184Figure 134 ICM3 - Multicast - PIM-SM - Multicast Routing Table Window .......................... 185Figure 135 ICM3 - Multicast - PIM-SM - Neighbor Details Window ..................................... 186Figure 136 ICM3 - Multicast - PIM-SM - Interface Setup Window ....................................... 187Figure 137 ICM3 - Multicast - PIM-SM - Interface Setup - Add Window ............................. 188Figure 138 ICM3 - Routing - Routing Table Window ........................................................... 189Figure 139 ICM3 - Routing - Add ......................................................................................... 190Figure 140 ICM3 - Routing - RIP - General Window ........................................................... 192Figure 141 ICM3 - Routing - RIP - Redistribution Setup Window ........................................ 193Figure 142 ICM3 - Routing - RIP - Redistribution Setup - Add Window .............................. 194Figure 143 ICM3 - Routing - RIP - Neighbor Details Window ............................................. 194Figure 144 ICM3 - Routing - RIP - Neighbor Details - Add Window .................................... 195Figure 145 ICM3 - Routing - RIP - Peer Details Window .................................................... 196Figure 146 ICM3 - Routing - RIP - Key Setup Window ....................................................... 197Figure 147 ICM3 - Routing - RIP - Key Setup - Add Keychain Window .............................. 198Figure 148 ICM3 - Routing - RIP - Key Setup - Add Key Window ....................................... 198Figure 149 ICM3 - Routing - RIP - Interface Setup Window ................................................ 199Figure 150 ICM3 - Routing - RIP - Interface Setup - Add Window ...................................... 200Figure 151 ICM3 - Routing - OSPF - General Window ....................................................... 202Figure 152 ICM3 - Routing - OSPF - Route Redistribution Window .................................... 204Figure 153 ICM3 - Routing - RIP - Route Redistribution- Add Window ............................... 205Figure 154 ICM3 - Routing - OSPF - Area Setup Window .................................................. 206Figure 155 ICM3 - Routing - OSPF - Area Setup - Add Window ......................................... 207Figure 156 ICM3 - Routing - OSPF - Address Ranges Window .......................................... 208Figure 157 ICM3 - Routing - OSPF - Address Ranges - Add Window ................................ 209Figure 158 ICM3 - Routing - OSPF - LSDB Table Window ................................................. 210


19

Figure 159 ICM3 - Routing - OSPF - Neighbor Details Window .......................................... 213Figure 160 ICM3 - Routing - OSPF - Interface Setup Window ............................................ 214Figure 161 ICM3 - Routing - OSPF - Interface Setup - Add Window .................................. 215Figure 162 ICM3 - Routing - ARP Window .......................................................................... 217Figure 163 ICM3 - Routing - ARP - Add Window ................................................................ 218Figure 164 ICM3 - Routing - ARP - Delete Advanced Window ........................................... 218Figure 165 ICM3 - DHCP - Server Window ......................................................................... 220Figure 166 ICM3 - DHCP - Profile Window ......................................................................... 221Figure 167 ICM3/3G - DHCP - Profile - Add Window .......................................................... 222Figure 168 ICM3 - DHCP - Subnet Mapping Window ......................................................... 225Figure 169 ICM3/3G - DHCP - Subnet Mapping - Add Window .......................................... 226Figure 170 ICM3 - DHCP - Pool Window ............................................................................ 227Figure 171 ICM3/3G - DHCP - Pool - Add Window ............................................................. 228Figure 172 ICM3 - DHCP - Map Window ............................................................................. 229Figure 173 ICM3/3G - DHCP - Map - Add Window ............................................................. 230Figure 174 ICM3 - DHCP - Lease Window .......................................................................... 231Figure 175 ICM3 - DHCP - Option 60 Window .................................................................... 232Figure 176 ICM3/3G - DHCP - Option 60 - Add Window ..................................................... 232Figure 177 ICM3 - DHCP - Option 82 Window .................................................................... 233Figure 178 ICM3/3G - DHCP - Option 82 - Add Window ..................................................... 234Figure 179 ICM3 - DHCP - VLAN Window .......................................................................... 235Figure 180 ICM3/3G - DHCP - VLAN - Modify Window ....................................................... 236Figure 181 ICM3 - Packet Classification - Masks Window .................................................. 237Figure 182 ICM3/3G - Packet Classification - Masks - Add Window ................................... 238Figure 183 ICM3 - Packet Classification - Actions ............................................................... 240Figure 184 ICM3/3G - Packet Classification - Actions - Add ............................................... 241Figure 185 ICM3 - Packet Classification - Meters ............................................................... 242Figure 186 ICM3/3G - Packet Classification - Meters - Add ................................................ 243Figure 187 ICM3 - Packet Classification - Flow Counters ................................................... 244Figure 188 ICM3 - Packet Classification - Rules ................................................................. 245Figure 189 ICM3/3G - Packet Classification - Rules - Add .................................................. 246Figure 190 ICM3 - QoS - Priority ......................................................................................... 247Figure 191 ICM3 - QoS - Priority - Modify ........................................................................... 248Figure 192 ICM3 - QoS - DSCP Priority .............................................................................. 249Figure 193 ICM3 - QoS - DSCP Priority - Modify ................................................................ 250Figure 194 ICM3 - QoS - Queue Mapping ........................................................................... 251Figure 195 ICM3 - QoS - DSCP Mapping - Modify .............................................................. 252Figure 196 ICM3 - QoS - L2 Scheduling .............................................................................. 253Figure 197 PCU -Node - Reset ............................................................................................ 256Figure 198 PCU - Module Summary Window ...................................................................... 257Figure 199 PCU - Shelf View Window ................................................................................. 258Figure 200 PCU - PCU Window .......................................................................................... 259Figure 201 PCU - Clock Source Window ............................................................................. 260Figure 202 PCU - Alarm Indication Window ........................................................................ 261Figure 203 PCU - PDP Window ........................................................................................... 263Figure 204 iFXS1 Module Information ................................................................................. 265Figure 205 IP Configuration ................................................................................................. 267Figure 206 Call Server ......................................................................................................... 268Figure 207 Misc Config ........................................................................................................ 269Figure 208 T.38 ................................................................................................................... 271Figure 209 TOS/DSCP ........................................................................................................ 272Figure 210 VLAN Tag .......................................................................................................... 273Figure 211 Node Configuration ............................................................................................ 274Figure 212 Port Configuration .............................................................................................. 276Figure 213 Ring Definition ................................................................................................... 278


20

Figure 214 VoIP Media ........................................................................................................ 280Figure 215 Jitter Buffer ........................................................................................................ 281Figure 216 SIP Port ............................................................................................................. 282Figure 217 SIP Summary Statistics ..................................................................................... 283Figure 218 SIP Supported Methods .................................................................................... 284Figure 219 SIP Methods Statistics ...................................................................................... 285Figure 220 General Config .................................................................................................. 286Figure 221 Server Table ...................................................................................................... 287Figure 222 MG Table ........................................................................................................... 288Figure 223 User Table ......................................................................................................... 289Figure 224 IPxDSL Provisioning Main Window ................................................................... 291Figure 225 Node - Reset ..................................................................................................... 293Figure 226 IPxDSL - Module Summary - Module Information Window ............................... 294Figure 227 IPxDSL - Module Summary - Active Ports Window ........................................... 295Figure 228 IPxDSL - Shelf Window ..................................................................................... 296Figure 229 IPxDSL - Virtual Board Assignment Window ..................................................... 297Figure 230 IPxDSL - Virtual Board Assignment - Module Type Window ............................. 297Figure 231 IPxDSL - Virtual Board Deassignment Window ................................................ 298Figure 232 IPxDSL - IPADSL3A Window ............................................................................ 299Figure 233 IPxDSL - Customized Filter - Upstream Multicast Filter Packet Flow - Enabled 301Figure 234 IPxDSL - Customized Filter - Upstream Multicast Filter Packet Flow - Disabled 302Figure 235 IPxDSL - Customized Filter Window ................................................................. 307Figure 236 IPxDSL - Test Timeout Window ........................................................................ 310Figure 237 IPxDSL - PPPoE Snooping Window ................................................................. 311Figure 238 IPxDSL - WAN - WAN Port Window .................................................................. 313Figure 239 IPxDSL - ADSL - ADSL Port Window ................................................................ 314Figure 240 IPxDSL - ADSL - ADSL Port - Assign Profile Window ...................................... 315Figure 241 IPxDSL - SHDSL - SHDSL Port Window .......................................................... 316Figure 242 IPxDSL - SHDSL - SHDSL Port - Assign Profile Window ................................. 317Figure 243 IPxDSL - xDSL - Line Status Window ............................................................... 318Figure 244 IPxDSL - ADSL - Channel Status Window ........................................................ 320Figure 245 IPxDSL - ADSL - Previous Status Window ....................................................... 321Figure 246 IPxDSL - ADSL - Status Change Time Info Window ......................................... 322Figure 247 IPxDSL - ADSL - Rate Summary Window ......................................................... 323Figure 248 IPxDSL - xDSL - Port Label Window ................................................................. 324Figure 249 IPxDSL - xDSL - Port Label - Modify Window ................................................... 325Figure 250 IPxDSL - ADSL - Bit Loading Window ............................................................... 326Figure 251 IPxDSL - xDSL - iSmart Window ....................................................................... 328Figure 252 IPxDSL - ADSL - CPE Window ......................................................................... 329Figure 253 IPxDSL - ADSL - CPE - Modify Window ........................................................... 330Figure 254 IPxDSL - ATM - ATM VC Window ..................................................................... 331Figure 255 IPxDSL - ATM - ATM VC - Add Window ........................................................... 332Figure 256 IPxDSL - ATM - Traffic Profile Window ............................................................. 334Figure 257 IPxDSL - ATM - Traffic Profile - Assign Profile Window .................................... 335Figure 258 IPxDSL - Bridge - MAC Address Per Port Window ........................................... 336Figure 259 IPxDSL - Bridge - MAC Address Per Port - Modify Window ............................. 337Figure 260 IPxDSL - Bridge - Packet Policing - Packet Policing Setup Window ................. 338Figure 261 IPxDSL - Bridge - Packet Policing IP Address Summary Window .................... 339Figure 262 IPxDSL - Bridge - Forwarding Database Window ............................................. 340Figure 263 IPxDSL - Forwarding Database - Add Window ................................................. 341Figure 264 IPxDSL - Bridge - ARP Table Window .............................................................. 343Figure 265 IPxDSL - Bridge - Flood Limit Window .............................................................. 344Figure 266 IPxDSL - IGMP - Authentication Parameters Window ...................................... 345Figure 267 IPxDSL - IGMP - Authentication Parameters - Modify Window ......................... 345Figure 268 IPxDSL - IGMP - CAC Window ......................................................................... 346


21

Figure 269 IPxDSL - IGMP - Multicast Group Window ........................................................ 347Figure 270 IPxDSL - IGMP - Multicast Host Window .......................................................... 348Figure 271 IPxDSL - VLAN - VLAN Window ....................................................................... 350Figure 272 IPxDSL - VLAN - VLAN - Add Window .............................................................. 351Figure 273 IPxDSL - VLAN - Ingress Rule Window ............................................................. 352Figure 274 IPxDSL - VLAN - Ingress Rule - Modify Window ............................................... 352Figure 275 IPxDSL - VLAN - VLAN Untag Window ............................................................. 353Figure 276 IPxDSL - Access List Window ........................................................................... 354Figure 277 IPxDSL - Access List - Edit Window .................................................................. 355Figure 278 IPxDSL - Access List - Edit - New Window ....................................................... 356Figure 279 IPxDSL - QoS - Packet Priority Window ............................................................ 359Figure 280 IPxDSL - QoS - Packet Priority - Edit Window .................................................. 359Figure 281 IPxDSL - QoS - Packet Priority - Edit - Add Window ......................................... 360Figure 282 IPxDSL - QoS - Port Based Priority Window ..................................................... 361Figure 283 IPxDSL - QoS - Port Based Priority - Modify Window ....................................... 361Figure 284 IPxDSL - QoS - 802.1p Tag Window ................................................................. 363Figure 285 Performance Management Main Window ......................................................... 365Figure 286 ICM3 - Ethernet PM- General Counters ............................................................ 367Figure 287 ICM3 - Ethernet PM - Error Counters ................................................................ 369Figure 288 ICM3 - Ethernet PM - Traffic Load ..................................................................... 370Figure 289 ICM3 - Bridge PM - Control ............................................................................... 371Figure 290 ICM3 - Bridge PM - 5 Minutes Report ............................................................... 372Figure 291 IPADSLx - ATM PVC ......................................................................................... 374Figure 292 IPADSLx - Bridge Port - Bridge PM Control ...................................................... 375Figure 293 IPADSLx - Bridge Port - Bridge ......................................................................... 376Figure 294 IPADSLx - Bridge Port - 5 Minutes Report ........................................................ 377Figure 295 IPADSLx - WAN Port - Thresholds Control ....................................................... 379Figure 296 IPADSLx - WAN Port - 15 Minutes .................................................................... 380Figure 297 IPADSLx - ADSL Port - ADSL 15 Minutes Summary ........................................ 382Figure 298 IPADSLx - ADSL Port - Thresholds Control ...................................................... 384Figure 299 IPADSLx - ADSL Port - ATUC 15 Minutes ........................................................ 385Figure 300 IPADSLx - Channel - Downstream 15 Minutes ................................................. 387Figure 301 IPSHDSL3 - Bridge ............................................................................................ 388Figure 302 Diagnostics Main Window ................................................................................. 391Figure 303 F4/F5 Loopback Window ................................................................................... 393Figure 304 F4/F5 Loopback - F4 Test Window ................................................................... 393Figure 305 F4/F5 Loopback - F5 Test Window ................................................................... 394Figure 306 DELT Window .................................................................................................... 395Figure 307 DELT - Result - Hlin(f) ....................................................................................... 396Figure 308 DELT - Result - Hlog(f) ...................................................................................... 396Figure 309 DELT - Result - QLN(f) ...................................................................................... 397Figure 310 DELT - Result - SNR(f) ...................................................................................... 397Figure 311 DELT Window - Result - Report ........................................................................ 398Figure 312 SELT Window .................................................................................................... 399Figure 313 SELT - Test Result ............................................................................................ 400Figure 314 SELT - Test Result - Table ................................................................................ 402Figure 315 SELT - Test Result - File - Directory .................................................................. 403Figure 316 SELT - Test Result - View - Inband Noise ......................................................... 403Figure 317 Platform Level Alarms ....................................................................................... 405Figure 318 Alarm Tree ......................................................................................................... 407Figure 319 Fault Management Main Window ...................................................................... 408Figure 320 Node Alarm ........................................................................................................ 409Figure 321 Equipment Alarm ............................................................................................... 410Figure 322 Port Alarm .......................................................................................................... 411Figure 323 Alarm Summary Window ................................................................................... 413


22

Figure 324 Alarm Filter Window .......................................................................................... 414Figure 325 Software Upgrade ............................................................................................. 425Figure 326 Tools - TFTP ..................................................................................................... 429Figure 327 Tools - TFTP - Client Mode ............................................................................... 429Figure 328 Tools - TFTP Window ........................................................................................ 430Figure 329 Tools - TFTP Window - Expanded .................................................................... 431Figure 330 Backup Node ..................................................................................................... 433Figure 331 Profile Menu - Access List Profiles .................................................................... 438Figure 332 Access List Profile Summary Window ............................................................... 438Figure 333 PPPoE Access Deny - Add Access List Profile - Deny ..................................... 439Figure 334 PPPoE Access Deny - Add Access List Profile - Permit ................................... 440Figure 335 PPPoE Access Deny - 2 Profiles Added ........................................................... 440Figure 336 PPPoE Access Deny - IPxDSL Module - Access List ....................................... 441Figure 337 PPPoE Access Deny - IPxDSL Module - Applying Profiles to Outbound .......... 442Figure 338 PPPoE Access Deny - Complete ...................................................................... 443Figure 339 Profile Menu - Access List Profiles .................................................................... 444Figure 340 Access List Profile Summary Window ............................................................... 444Figure 341 IP Address Conflict - Add Access List Profile - Permit ...................................... 445Figure 342 IP Address Conflict - Add Access List Profile - Deny ........................................ 446Figure 343 IP Address Conflict - 2 Profiles Added .............................................................. 446Figure 344 IP Address Conflict - IPxDSL Module - Access List .......................................... 447Figure 345 IP Address Conflict - IPxDSL Module - Applying Profiles to Outbound ............. 448Figure 346 IP Address Conflict - Complete ......................................................................... 449Figure 347 Profile Menu - Access List Profiles .................................................................... 450Figure 348 Access List Profile Summary Window ............................................................... 450Figure 349 FTP Access Deny - Add Access List Profile - Deny .......................................... 451Figure 350 FTP Access Deny - Add Access List Profile - Permit ........................................ 452Figure 351 FTP Access Deny - 2 Profiles Added ................................................................ 452Figure 352 FTP Access Deny - IPxDSL Module - Access List ............................................ 453Figure 353 FTP Access Deny - IPxDSL Module - Applying Profiles to Inbound ................. 454Figure 354 FTP Access Deny - IPxDSL Module - Applying Profiles to Outbound ............... 455Figure 355 FTP Access Deny - Complete ........................................................................... 456Figure 356 Profile Menu - Access List Profiles .................................................................... 457Figure 357 Access List Profile Summary Window ............................................................... 457Figure 358 ABC IM Service Access Deny - Add Access List Profile - Deny IP Address Range 458Figure 359 ABC IM Service Access Deny - Add Access List Profile - Deny Specific IP Address 459Figure 360 ABC IM Service Access Deny - Add Access List Profile - Permit ..................... 460Figure 361 ABC IM Service Access Deny - 3 Profiles Added ............................................. 460Figure 362 ABC IM Service Access Deny - IPxDSL Module - Access List ......................... 461Figure 363 ABC IM Service Access Deny - IPxDSL Module - Applying Profiles to Outbound ..462Figure 364 ABC IM Service Access Deny - Complete ........................................................ 463


ABOUT THIS GUIDE

This chapter contains the order in which tasks should be completed, lists guide conventions and related documentation, and describes how to contact customer service and technical documentation.

This guide describes the provisioning procedures for iAN8K B1000 Device Manager and configuration procedures for iAN8K B1000 node and the line modules.

Release notes are issued with some products—visit our website at http://support.utstar.com. If the information in the release notes differs from the information in this guide, follow the instructions in the release notes.

Order of Tasks To install the iAN8K B1000 product, complete the tasks in the following order:

1 Complete all the procedures in the iAN8K B1000 Release 3.1 Installation Manual.

2 Complete all the procedures in the Netman 4000 Installation Manual.

Conventions This guide may contain notices, figures, screen captures, and certain text conventions.


24 About This Guide

Notices Table 1 lists notice icons used in this guide.

Figures and ScreenCaptures

This guide provides figures and screen captures as examples. These examples contain sample data. This data may vary from the actual data on an installed system.

Text Table 2 lists text conventions in this guide.

Table 1 Notice Icon Descriptions

Icon Notice Type DescriptionInformation Note Information that contains important features or

instructions but is not hazard-related.

Caution or Warning Cautions are preceded with the word Caution. This type of caution indicates a potentially hazardous situation which, if not avoided, may result in minor or moderate injury. It may also alert against unsafe practices and potential program, data, system, or device damage.

Warnings are preceded with the word Warning. This type of warning indicates a potentially hazardous situation which, if not avoided, could result in death or serious injury.

Caution or Warning due to potential electrical hazard

Cautions due to potential electrical hazards are preceded with the word Caution. This type of caution indicates a potential electrical hazard. This hazard, if not avoided, may result in minor or moderate injury. It may also alert against unsafe practices and potential program, data, system, or device damage.

Warnings due to potential electrical hazards are preceded with the word Warning. This type of warning indicates a potential electrical hazard. This hazard, if not avoided, could result in death or serious injury.

ESD Information that indicates proper grounding precautions are required before handling a product.

Table 2 Text Convention Descriptions

Convention DescriptionText represented as a screen display

This typeface represents text that appears on a terminal screen, for example login:.

Text represented as user entry.

This typeface represents commands entered by the user, for example, cd $HOME.

Text represented as menu, sub-menu, tab, and field names

This typeface represents all menu, sub-menu, tab, and field names within procedures, for example:

On the File menu, click New.

Text represented by <variable> This typeface represents a required variable, for example: <filename>


Related Documentation 25

Related Documentation

The following lists the documentation set for iAN8K B1000 Release 3.1 system:

Contacting Customer Service

For information about customer service, including support, training, code releases and updates, contracts, and documentation, visit our website at http://support.utstar.com.

Refer to the documentation CD-ROM for information about product warranty.

Before contacting technical support, have this information available:

■ Contract number

■ Problem description

■ Symptoms

■ Known causes

■ Product information

■ Software and hardware versions

■ Serial numbers

■ Trouble locating and clearing attempts

Contacting Technical Documentation

To provide comments on this documentation, send an e-mail to:

[email protected]

Table 3 iAN8K B1000 Release 3.1 Documentation Set

Guide Part NumberNetman 4000 Installation Manual

Netman 4000 Operations Manual

iAN8K B1000 Release 3.1 B1000 Installation Manual UTSI-NJTC-20050914

iAN8K B1000 Release 3.1 B1000 IS Installation Manual UTSI-NJTC-20050870

iAN8K B1000 Release 3.1 Operations Manual UTSI-NJTC-20050696

iAN8K B1000 Release 3.1 Command Line Interface (CLI) User Manual

UTSI-NJTC-20050624

iAN8K B1000 Release 3.1 IP Service Module (ISM) Operations Manual

UTSI-NJTC-20050697

iAN8K B1000 Release 3.1 IP Service Module (ISM) Command Line Interface (CLI) User Manual

UTSI-NJTC-20050698

iAN8K B1000 Release 3.1 ATM Service Module (ASM) Operations Manual

UTSI-NJTC-20050699

iAN8K B1000 Release 3.1 ATM Service Module (ASM) Command Line Interface (CLI) User Manual

UTSI-NJTC-20050700


26 About This Guide

Please include the name and part number of the guide being referenced. If applicable, provide the chapter and page number.


1
NETWORK MANAGEMENT
The Netman 4000 system employs advanced object-oriented design with platform-independent Java programming, and is based on TCP/IP, SNMP, UNCP and TL1 protocols. Netman 4000 provides completely unified network management. The Netman 4000 system ultimately enables the network management functions defined in TMN, including configuration, fault, security and log performance management. Its advanced network management functionalities, sophisticated architecture and support for open standards make it well suited for a wide range of networking environments.

System Structure The Netman 4000 system employs hierarchical system architecture, which accords with the hierarchical nature of the telecommunication network. In this hierarchical network management structure, network management modules on different layers have different functions. The two main layers of Netman 4000 being:

■ Element Management Layer: Provides operations and management functions for one or more Network Elements (NE)

■ Network Management Layer: Comprises network layer management functions such as monitoring network traffic, network topology and dispatching resources and so on.

Functional Components

Netman 4000 is an overall network management system solution, and has the following functional components:

■ OMC-A: OMC is located in the EMS layer of the network management system architecture, and comprises IPiAN8K B1000, AN2000, iAN8000, iAN2000, CPE, PWLAN and WLANs

■ Alarm Panel: Is a wall-mountable audio/visual alarm device with a large Liquid Crystal Display (LCD). The alarm functions are customized to meet O&M requirements. The panel can be mounted in equipment rooms and works with Netman 4000 to provide audible and visual alarms for broadband networks

■ CLI: Netman 4000 provides a Command Line Interface (CLI) as well as the friendly GUI management access method. An operator can use text commands to configure, monitor and troubleshoot an NE. Refer to CLI user manuals in Related Documentation for more details.


28 Chapter 1: Network Management

Primary Management Functions

Netman 4000 is a unified entry point for all network-layer functions and integrates system equipment management to achieve the overall management of UTStarcom broadband access products.

Basic ManagementFunctions

Netman 4000 supports the following functions:

Topology ManagementThe system supports the entire network topology display and the hierarchical physical views within the topology map. The topology map enables users to check network topology via physical location, and to obtain a global view of the entire network from NE data displayed in the network topology. The hierarchical management functionality facilitates convenient NE query and location. In addition, the system supports synchronous zoom in and out of the background and the topology maps, and also facilitates switching between sub-maps.

Users can add or delete topology elements (including groups, nodes and links), browse properties of managed objects, and implement specific device management via the device management interface.

The system synchronizes the topology data between the server and client, automatically detects the NE and updates its status. The topology map supports real-time alarm display and visual/audio alert.

Fault ManagementThe Fault Management module receives the NE traps and categorizes them as alarms/events with alarm indications. Alarm information can be viewed through the UI client to help network managers to obtain real-time fault data, in order to ensure continuous and reliable network service. The system also supports customized alarms/events views; allowing users to modify the events and alarms by configuring alarm suppression or filter settings.

Security ManagementThe security management module adopts the Users-Role-Management Domain security management scheme, to ensure the permitted use of network resources, data maintenance integrity and security requirements. Users can create a client account, setup passwords and access domain/privileges using the NMS system management interface. The access privilege prevents unauthorized system access. Access privileges can be narrowly defined to include read/write operations for just one individual managed object.

Log ManagementNetman 4000 initiates a log management at startup. Log records guarantee accurate operations history and convenient system maintenance.

The Netman 4000 log management module can be used to create a system log, or a user operation log, and to provide view, filter and backup log functions.


Primary Management Functions 29

System ToolsSystem provides multiple extended management tools, including Subscriber Management System (SMS), TFTP, node automatic back-up configuration file, SNMP forwarding, CPE management, ADSL Port quality inspection, etc.


30 Chapter 1: Network Management


2
DEVICE MANAGER
Netman 4000 supports configurations of the node and the plug-in modules through the node device manager.

Double-click the node in the tree view panel or the main window to access the device manager. The device manager can also be accessed by right clicking the node and the select the Device Manager as shown in Figure 1. The device manager main window is promoted as shown in Figure 2.

Figure 1 Invoking Device Manager From Netman 4000


32 Chapter 2: Device Manager

Figure 2 Device Manager Main Window

The Device manager provides the following configuration menus:

■ Configuration Menu

■ Profile Menu

■ Batch Menu

■ Video Service Menu

■ Tools Menu

Note: Please note the following naming convention for the modules:

■ IPADSLx is a joint name for all ADSL line cards modules including IPADSL3A, IPADSL3B, IPADSL6A and IPADSL6B

■ IPxDSL is a joint name for all line card modules including IPADSL3A, IPADSL3B, IPADSL6A, IPADSL6B and IPSHDSL3

Note: Please refer to the following manual for more information of Netman 4000 platform configuration:

■ Netman 4000 Installation Manual

■ Netman 4000 Operations Manual


Configuration Menu 33

Configuration Menu iAN8K B1000 supports the following options in the Configuration menu:

■ Get Configuration - To obtain the latest configuration information from Node in real time

■ Save Configuration - To save configuration data into the flash memory of ICM3 module

■ Erase Configuration - To erase configuration data from the flash memory of ICM3 on the master shelf

■ Erase Shelf Configuration - To erase configuration data from the flash of ICM3 on a specific shelf (for shelf stacked node)

■ System Log - To view system log configuration/collector

■ Radius Server - To configure radius server for authentication

■ Telnet Port - To assign the telnet port number

■ Maximum Power Setting - To change the power spectral mask for the modules

■ Packet Count Reset - To change the bridge counters reset behavior

■ Node ID - To assign an unique ID to the node

■ iSmart Feature - To enable / disable iSmart functionality on the line card

■ LTC Configure - To configure LTC setting

Get Configuration Select Get Configuration from Configuration menu. This command refreshes the iAN8K B1000 node configuration.

Save Configuration Select Save Configuration from Configuration menu. This command saves configuration changes made on the Netman 4000 client to the storage memory of iAN8K B1000 node.

Erase Configuration Select Erase Configuration from Configuration menu. Figure 3 prompts for confirmation. Click Yes to erase configuration data from the flash memory of the ICM3 on the master shelf.

Figure 3 Configuration - Erase Configuring

CAUTION: If you reset the system after erasing all configurations the communication via SNMP (Netman) will be disabled. By design the AN-2000



IPiAN8K B1000 won’t communicate over SNMP with Netman (or any other SNMP Manager) until the Netman IP address has been entered. You’ll need to configure one or two Netman IP addresses via CLI command “netman-destination” found on page 325 of the CLI manual to restore SNMP. There are 2 possible entries here for “primary” and “secondary” for the Netman address. It basically maps to the Trap Destination Setup on Netman’s Device Manager screen. As long as these addresses are non-zero it will allow SNMP communication. The addresses don’t have to point to valid Netman Server addresses. However you’ll need valid addresses if you expect to receive traps from the node at these locations.

Erase ShelfConfiguration

Select Erase Shelf Configuration from Configuration menu. Figure 4 prompts for shelf selection. Select an shelf ID and click Apply to erase configuration data from the flash memory of the ICM3 module on the selected shelf. Click Close to exit.

Note: This feature is applicable to shelf stacked nodes only.

Figure 4 Configuration - Erase Shelf Configuring Window

CAUTION: If you reset the system after erasing all configurations the communication via SNMP (Netman) will be disabled. By design the AN-2000 IPiAN8K B1000 won’t communicate over SNMP with Netman (or any other SNMP Manager) until the Netman IP address has been entered. You’ll need to configure one or two Netman IP addresses via CLI command “netman-destination” found on page 325 of the CLI manual to restore SNMP. There are 2 possible entries here for “primary” and “secondary” for the Netman address. It basically maps to the Trap Destination Setup on Netman’s Device Manager screen. As long as these addresses are non-zero it will allow SNMP communication. The addresses don’t have to point to valid Netman Server addresses. However you’ll need valid addresses if you expect to receive traps from the node at these locations.

System Log iAN8K B1000 system supports sending system log messages to an external system log collector. The format of system log message conforms to RFC 3164. Netman 4000 displays the syslog and allows user to configure a Syslog server.



Up to five servers can be added to the system. If no Syslog servers are configured or if the IP address is 0.0.0.0, the syslog function is disabled and no messages are sent out. The supported Syslog categories includes:

■ Login

■ DHCP

■ DSL link up/down

■ DSL line error

■ ICM/LC Ethernet link up/down

■ Configuration change

■ Line module status

■ System alarm

■ Multicast CAC Threshold exceeded

■ ASM ATM link up/down

■ ASM Ethernet link up/down

■ ASM configuration change

■ ASM module status

■ Broadcast video over DSL status

■ Power management status change

■ Shelf stacking status change

Refer to System Log Data for more details of the messages.

Select System Log from Configuration menu. Figure 5 prompts for confirmation. Click Retrieve to obtain the latest information. Refer to Table 4 for more details.



Figure 5 Configuration - System Log

Click Add or select an entry and click Modify in Figure 5. Configure the parameters and click Apply in Figure 6.

Table 4 Configuration - System Log Table

Field DescriptionID Log ID number

Description A suitable description for the syslog collector

Address The IP address of system log collector

Port UDP Port number for Syslog data

Value range: 1-65535

Default: 514

Facility Facility code for each type of event

Value range: 16 - 23 Local use 0 - 7 respectively

Default: 23 local use 7

Category Categories included in the log



Figure 6 Configuration - System Log - Add

Select an entry in Figure 5 and click Delete to remove an existing entry. Click Close to exit the window.

System Log DataiAN8K B1000 generates Syslog messages according the the type of events occur. The description of each types of events are specified in the following sections:

■ Login

No. Event1 User login from console port

2 User logout from console port

3 User failed to login at console port (password authentication fails)

4 Telnet request from IP address a.b.c.d

5 User telnet from IP address a.b.c.d and login to the node

6 User from IP address a.b.c.d logout from telnet session

7 User telnet from IP address a.b.c.d and login to the node failed

8 A received SNMP message has been dropped due to wrong community string or illegitimate source IP address or message parsing error caused by malformed packet.

9 RADIUS message sent to server a.b.c.d timeout

10 RADIUS server is marked as temporary down

11 RADIUS server is recovered from temporary down



■ DHCP

■ DSL link up/down

■ DSL line error

■ ICM/LC Ethernet link up/down

■ Configuration change

No. Event1 A DHCPACK message is snooped in downstream (from WAN port to ADSL ports)

2 DHCP contract expired

No. Event1 ADSL/SHDSL port status change

No. Event1 ADSL line stays in idle or training mode for over five minutes

2 ADSL line goes to unknown state

3 ATU-R /ATU-C capability mismatch

No. Event1 WAN port link goes down (port was administratively enabled)

2 WAN port link comes up (port was administratively enabled and was down)

3 Internal Ethernet link partially down

4 Internal Ethernet link down

5 Internal Ethernet link up

6 External Ethernet link down

7 External Ethernet link up

8 External Ethernet port in trunk down

9 External Ethernet port in trunk up

10 External Ethernet trunk down

11 External Ethernet trunk up

No. Event1 ADSL/SHDSL port admin status change

2 Any other configuration changes

3 Configuration is saved

4 Configurations are erased



■ Line module status

■ System alarm

■ ASM ATM link up/down

■ ASM Ethernet link up/down

■ ASM configuration change

No. Event1 Line card restart

2 Line card restart by management station

3 Line card plug in/out

4 DSL module type mismatch

5 DSL module type mismatch, configured line profile is not supported by physical module, use default profile

No. Event1 Fan failure

2 Fuse alarm

3 Fan recover

4 External clock down, while primary clock source is set as external clock,

5 External clock recovery, while primary clock source is set as external clock

6 External clock is no longer configured as primary clock source, while an external clock down alarm is outstanding

7 Fuse recovery

No. E1 port status change1 T1 port status change

2 OC3/STM-1 port status change

3 IMA group status change

No. Event1 ASM Ethernet port link goes down (port was administratively enabled)

2 ASM Ethernet port link comes up (port was administratively enabled and was down)

No. Event1 E1 port admin status change

2 T1 port admin status change

3 OC3/STM-1 port admin status change

4 Any other configuration changes

5 Configuration is saved

6 Configuration is erased



■ ASM module status

■ Broadcast video over DSL status

■ Power management status change

Radius Server iAN8K B1000 supports a RADIUS client in compliance with IETF RFC 2865 for authentication of CLI login through Telnet or console port.

When the feature is enabled and the user ID fails the local authentication, the login information is sent to the Radius server for authentication. if the user is configured locally and the local authentication fails, the information is not sent to RADIUS. User shall not configure local user and RADIUS user with the same user ID.

Select Radius Server from Configuration menu. Radius server supports the following configuration:

■ RADIUS Server

■ Statistics

No. Event1 ASM card restart

2 ASM card restart by management station

3 ASM card plug in/out

No. Event1 CAC threshold exceeded

No. Event1 Power Management Status change

2 Forced power management state change



RADIUS ServerSelect Radius Server from Configuration menu. The radius server window is displayed as shown in Figure 7. Click Retrieve to obtain the latest statistics.

Figure 7 Configuration - RADIUS Server - RADIUS Server

Select Disable or Enabled and click Apply in Figure 7 to disable/enable the RADIUS authentication. By default, this feature is disabled.

Click Add in Figure 7 to create a new entry. Figure 8 prompts for radius server information. Configure the parameters and click Apply to add the entry. Maximum of 4 radius server entries can be configured. Refer to Table 5 for more information of the parameters.

Figure 8 Configuration - RADIUS Server - RADIUS Server - Add



Select an entry in Figure 7 and click Delete to remove the entry. Click Close in Figure 7 to exit the window.

StatisticsSelect Radius Server from Configuration menu and select the Statistics tab to open Figure 9. Click Retrieve to obtain the latest statistics. Refer to Table 6 for more details.

Table 5 Configuration - RADIUS Server - RADIUS Server - Add Table

Parameter Value RangeIP Address IP Address of the Radius server.

Port UDP port number.

Value range: 1 - 65535.

Default: 1812

Server Name A unique character string with maximum of 32 characters

Secret A unique character string with maximum of 32 characters

Priority Priority of the server.

Value range: 1-4

Recovery time The waiting time before the server to become active again after the server does not respond and the system has to switch to the next server for 2 consecutive times.

Value range: 1 - 3600 seconds

Default: 300

Retries The number of retries when no response received from a server before proceeding to the next server with the highest priority.

Value range: 0-10

Default:3

Timeout The time to wait for response from a server before proceeding to the next available server with the highest priority.

Value range: 1-30 seconds

Default: 5 seconds



Figure 9 RADIUS Server - RADIUS Server - Statistics

Telnet Port iAN8K B1000 supports telnet access to the ICM3 module and the telnet port number is configurable with valid range of 23 and 1025 to 65535. The default

Table 6 RADIUS Server - RADIUS Server - Statistics Table

Parameter Value RangeUnknown Authentication Reply

The counter for the number of Unknown Authentication

Value range: 32-bit counter

IP Address IP address of the server

Port Port number of the server

Priority Priority setting of the server

Server Name Name of the server

Server State Active Temporary down: the server does not respond and the system has to switch to the next server for 2 consecutive times. The sever then becomes temporary down until the Recovery Time is passed.

Down Times The counter for the number of server goes down.


Requests The counter for the number of Access Requests.


Accepts The counter for the number of Access Accepts.


Rejects The counter for the number of Access Rejects.


Timeouts The counter for the number of Access Timeouts.


Retransmits The counter for the number of Access Retries.




value is 23. The iAN8K B1000 system allows user to remotely access the CLI interface of the IPxDSL line modules via ICM3. The CLI access is protected by password.

Changing the telnet port number disconnects all active telnet sessions. The new port number comes into effect for the new telnet sessions.

Select Telnet Port from Configuration menu to open the telnet port setup window shown in Figure 10. Configure the parameter and click Apply to take the modification into effect. Click Close to exit the window.

Figure 10 Configuration - Telnet Port

Maximum Power Setting This command allows reduction of the power spectral mask for IPADSL module by 1db.

Select Maximum Power Setting from Configuration menu to open the maximum power setting window shown in Figure 11. Configure the parameter and click Apply to take the modification into effect. Click Close to exit the window.

Figure 11 Configuration - Maximum Power Setting



Packet Count Reset This command changes the bridge counters reset behavior and ATM PVC counters based on the administrative state of the port.

■ When disabled, all counters are not reset when the corresponding xDSL line becomes administratively locked.

■ When enabled, all counters are reset when the corresponding xDSL line becomes administratively locked.

Select Packet Count Reset from Configuration menu to open the packet count reset window shown in Figure 12. Configure the parameter and click Apply to take the modification into effect. Click Close to exit the window.

Figure 12 Configuration - Packet Count Reset

Node ID This command provides node ID assignment. Please refer to the Netman 4000 Operations Manual for more details of inventory management.

Select Node ID from Configuration menu to open the node ID window shown in Figure 13. Configure the parameter and click Apply to take the modification into effect. Click Close to exit the window.

Note: Node ID modification does not take effect until ICM3 module is reset.

Figure 13 Configuration - Node ID



iSmart Feature iSmart addresses home-port identity issue for PAP-based PPPoE sessions. Home-port refers to the DSL port from which the PPPoE session is originated. In many instances, this information is required by B-RAS (the PPPoE server) to implement features like account binding (bind username-password to particular DSL port). iSmart inserts the home port identity to PAP authentication packet, therefore relays the information to PPPoE server.

When iSmart is enabled, user can configure the user name option for each DSL port to:

■ Replacement

PPPoE PAP Authenticate-Request message (RFC 1134) received from the DSL port is modified to:

Replace the peer-ID field with node_id#shelf_id#slot_id#port_id. The node_id is an integer from 1 to 9999 and it is provisioned by the user in Node ID section. The shelf_id is an integer indexed from 1. The slot_id is an integer indexed from 1 and slot B is indexed as 17. The port_id is an integer indexed from 1.

■ Extension

PPPoE PAP Authenticate-Request message (RFC 1134) received from the DSL port is modified to:

Replace the peer-ID field with node_id#shelf_id#slot_id#port_id#old_ peer_id. The node_id is an integer from 1 to 9999 and it is provisioned by the user in Node ID section. The shelf_id is an integer indexed from 1. The slot_id is an integer indexed from 1 and slot B is indexed as 17. The port_id is an integer indexed from 1. The old_peer_id is the peer ID field in the original received packet.

■ No modification

PPPoE PAP Authenticate-Request message (RFC 1134) received from the DSL port is not modified.

Note: Refer to Chapter 7- iSmart for more information of iSmart configuration.

Select iSmart Feature from Configuration menu to open the iSmart feature window shown in Figure 14. Select the shelf ID to display the corresponding slot configuration. Select the port and click Enable/Disable to enable/disable iSmart on the selected port. Click Close to exit the window.



Figure 14 Configuration - iSmart Feature

LTC Configure Select LTC Configure from Configuration menu to open the LTC configure window shown in Figure 15. Click Retrieve to obtain the latest information.



Figure 15 Configuration - LTC Configure

Click Add in Figure 15 to create a new entry. Configure the parameters and click Apply in Figure 16.

Figure 16 Configuration - LTC Configure - Add

Select an entry in Figure 15 and click Delete to remove an existing entry.

Select an entry in Figure 15 and click Configure to open Figure 17. Select the slot and and click test-in, test-out or un-test in Figure 17.



Figure 17 Configuration - LTC Configure - Configure - LTC Splitter

Select the Test Timeout tab in Figure 17 to open Figure 18. Click Retrieve to obtain the latest information. Configure the parameter and click Apply take the modification into effect. Click Close to exit the window.



Figure 18 Configuration - LTC Configure - Configure - Test Timeout

Profile Menu iAN8K B1000 supports the following options for profile configuration:

■ ADSL Line Profile - to configure ADSL line profile

■ SHDSL Line Profile - to configure SHDSL line profile

■ Ethernet PM Profile - to configure Ethernet performance profile

■ ADSL PM Profile - to configure ADSL performance profile

■ Access List Profile - to configure access list profile

■ Packet Priority Classification - to configure packet priority classification rules

■ Traffic Management Profile - to configure traffic management profile

ADSL Line Profile This feature allows ADSL line profile template configuration. Maximum of 64 templates, 64 service profiles and 64 spectrum profiles can be configured for each node.

■ Configuration Template

■ Service Profile

■ Spectrum Profile

ADSL templates can not be modified/deleted if it is assigned to any ADSL port. Service profiles and spectrum profiles can not be modified/deleted if it is is associated with any ADSL templates.

Note: Refer to Chapter 7 for more information of ADSL line profile assignment on IPADSL modules.

Configuration TemplateSelect ADSL Line Profile from Profile menu to open Figure 19. Click Retrieve to obtain the latest information.


Profile Menu 51

Figure 19 Profile - ADSL Line Profile - Configuration Template Window

Click Add or select a profile and click Modify to open Figure 20. Select the pre-configured service profile and spectrum profile. Click Apply to confirm the modification.

Figure 20 Profile - ADSL Line Profile - Configuration Template - Add Window

Note: Templates can not be modified/deleted if it is assigned to any ADSL port.

Service ProfileThis feature allows configuration of downstream/upstream rate and L2 rates.

Select ADSL Line Profile from Profile menu. Click Service Profile tab to open Figure 21. Click Retrieve to obtain the latest information.



Figure 21 Profile - ADSL Line Profile - Service Profile Window

Dissociate the service profile with any ADSL profile templates before attempting to modify/delete the profile. Click Add or select a profile and click Modify to open Figure 22. Configure the parameters and click Apply to confirm. Refer to Table 7 for more details.

Figure 22 Profile - ADSL Line Profile - Service Profile - Add Window


Profile Menu 53

Spectrum ProfileThis feature allows configuration of line standards, transmission mode, SNR margin, etc.

Select ADSL Line Profile from Profile menu. Click Spectrum Profile tab to open Figure 23. Click Retrieve to obtain the latest information.

Table 7 Profile - ADSL Line Profile - Service Profile Table

Field DescriptionService Profile A character string up to 32 characters

Downstream Min Rate Value range: 32 - 32736 Kbps in step of 4 with line standard 1 or 2, otherwise in step of 32

Default: 32 Kbps

Downstream Max Rate Value range: 32 - 32736 Kbps in step of 4 with line standard 1 or 2, otherwise in step of 32

Default: 8064 Kbps

Downstream Interleave Delay Value range: 1-63 ms

Default: 8 ms

Upstream Min Rate Value range: 32 - 1536 Kbps in step of 4 with line standard 1 or 2, otherwise in step of 32

Default: 32 Kbps

Upstream Max Rate Value range: 32 - 1536 Kbps in step of 4 with line standard 1 or 2, otherwise in step of 32

Default: 864 Kbps

Upstream Interleave Delay Value range: 1-16 ms

Default: 8 ms

L2 Entry Rate This parameter specifies the downstream data rate threshold that triggers entry into L2 power state. L2 entry rate must be less than L2 exit rate

Value range: 0- 1024 kbps

Default: 64 Kbps

Min L2 Data Rate This parameter specifies the minimum data rate during L2 power state. L2 data rate must be greater then L2 exit rate

Value range: 256 - 1024 kbps

Default: 256 Kbps

L2 Exit Rate This parameter specifies the downstream data rate that triggers the exit from L2 power state. L2 exit rate must be less than L2 data rate

Value range: 0- 1024 kbps

Default: 128 Kbps



Figure 23 Profile - ADSL Line Profile - Spectrum Profile Window

Dissociate the spectrum profile with any ADSL profile templates before attempting to modify/delete the profile. Click Add or select a profile and click Modify to open Figure 24. Configure the parameters and click Apply to confirm. Refer to Table 8 for more details.


Profile Menu 55

Figure 24 Profile - ADSL Line Profile - Spectrum Profile - Add Window



Table 8 Profile - ADSL Line Profile - Spectrum Profile Table

Field DescriptionSpectrum Profile A character string up to 32 characters

Line Standard ■ ADSL2/ReADSL2/G.DMT Annex A Automode

■ ADSL2plus/ADSL2/ReADSL2/G.DMT Annex A Automode

■ ADSL2plus/ADSL2/G.DMT Annex B Automode

■ ADSL2/G.DMT Annex B Automode

■ G.dmt Annex A

■ G.dmt Annex B

■ Annex A multimode

■ T1.413

■ G.lite Annex A

Refer to Table 9 for the specific standards supported by each linecards.

Transmission mode Value range: Echo Cancellation / FDM

Default: FDM

Tx Power Attenuation Value range: 0-40 dB in increment of 1dB

Default: 0 dB

ATM Header Compression Value range: Enable / Disable

Default: Disable

Rate Mode Value range: Fixed / Adaptive at Startup / Adaptive at Runtime

Default: Adaptive at Runtime

Spectrum Mask Value range: No Mask / RFI Mask

Default: No Mask

DownstreamTarget Downstream SNR Margin Value range: 0 ~ 31 dB

Default: 6 dB

Min Downstream SNR Margin Must be at least 3 dB lower than target downstream SNR margin.

Value range: 0 ~ 31 dB

Default: 0 dB

Downstream Upshift SNR Margin Only applicable with adaptive rate mode at run time. Must be at least 1 dB higher than target downstream SNR margin.


Default: 9 dB

Downstream Downshift SNR Margin

Only applicable with adaptive rate mode at run time. Must be at least 1 dB lower than target downstream SNR margin.


Default: 3 dB


Profile Menu 57

The line standard, Annex type, downstream spectrum and upstream spectrum are interdependent and each one changes as per the modification carried out in

Max Downstream SNR Margin Must be at least 3 dB higher than target downstream SNR margin.


Default: 31 dB

Downstream Bit Swapping Value range: Enable / Disable

Default: Enable

Downstream minimum Upshift Time

Only applicable with adaptive rate mode at run time.

Value range: 1 ~ 16383 s

Default: 60 s

Downstream minimum Downshift Time

Only applicable with adaptive rate mode at run time.


Default: 60 s

UpstreamTarget Upstream SNR Margin Value range: 0 ~ 31 dB

Default: 6 dB

Min Upstream SNR Margin Must be at least 3 dB lower than target upstream SNR margin.


Default: 0 dB

Max Upstream SNR Margin Must be at least 3 dB higher than target upstream SNR margin.


Default: 31 dB

Upstream Bit Swapping Value range: Enable / Disable

Default: Enable

Power Management State Value range: Disabled / L3 only/ L2 only / L3 and L2

Default: None

Min Time Between An Exit and the Next Entry

Not applicable when L2 state is disabled. The minimum time between an exit from L2 state and the next entry into the L2 state.


Default: 180 s

Min L2 Entry Time Not applicable when L2 state is disabled.


Default: 900 s

Table 8 Profile - ADSL Line Profile - Spectrum Profile Table

Field Description



the other. Table 9 lists the correlation and interdependencies between the line card and relevant line standards

SHDSL Line Profile This command allows SHDSL line profile configuration. Maximum of 64 SHDSL profile templates can be created for each node.

Select SHDSL Line Profile from Profile menu to open Figure 25. Click Retrieve to obtain the latest information.

Note: Refer to Chapter 7 for more information of SHDSL line profile assignment on IPSHDSL3 modules.

Table 9 Line Standard / Line Card Co-relation Table

Line standard IPADSL3A/6A IPADSL3B/6BADSL2/ReADSL2/G.DMT Annex A Automode V

ADSL2plus/ADSL2/ReADSL2/G.DMT Annex A Automode V

ADSL2plus/ADSL2/G.DMT Annex B Automode V

ADSL2/G.DMT Annex B Automode V

G.dmt Annex A V

G.dmt Annex B V

Annex A multimode V

T1.413 V

G.lite Annex A V


Profile Menu 59

Figure 25 Profile - SHDSL Line Profile Window

Click Add or select a profile and click Modify in Figure 25. Configure the parameters in Figure 26 and click Apply to take the modification into effect. Refer to Table 10 for more details.



Figure 26 Profile - SHDSL Line Profile - Add Window

Table 10 Profile - SHDSL Line Profile - Add Table

Parameter Value RangeProfile Name A character string up to 32 characters

Transmission Mode Value range: Annex A / Annex B

Default: Annex A

Min Rate Applicable with adaptive rate mode.

Value range:

■ For 2-wire, 200 to 2312 Kbps in increments of 64 Kbps


Default:

■ 200 Kbps for 2-wire



Profile Menu 61

Select a profile in Figure 25 and click Delete to delete the profile. Click Close in Figure 25 to exit.

Ethernet PM Profile This command allows configuration of performance thresholds for Ethernet traffic. The system supports two time durations for the profile, 15 minutes and 24 hours.

Select Ethernet PM Profile from Profile menu to open Figure 27. Click Retrieve to obtain the latest information. Refer to Table 11 for more details.

Note: Refer to Chapter 7 for more information of performance profile assignment.

Max Rate Applicable with adaptive rate mode.

Value range:



Default:



Fixed Rate Applicable with fixed rate mode.

Value range:



Default:



Rate Mode Value range: Adaptive Rate / Fixed Rate

Default: Adaptive Rate

Downstream Current Condition Target SNR Margin

Value range: -10 to 20 dB

Default: 0 dB

Downstream Worst Condition Target SNR Margin


Default: 0 dB

Upstream Current Condition Target SNR Margin


Default: 0 dB

Upstream Worst Condition Target SNR Margin


Default: 0 dB

Wire interface Value range: Two Wire / Four Wire

Default: Two Wire

Table 10 Profile - SHDSL Line Profile - Add Table

Parameter Value Range



Figure 27 Profile - Ethernet PM Profile

Click Add or select a profile and click Modify in Figure 27 to configure profiles in Figure 28. Configure the parameters and click Apply to take the modification into effect.

Table 11 Profile - Ethernet PM Profile Table

Field Description15 Minutes The error threshold for the past 15 minutes interval.

Value range: 0-900

24 Hours The error threshold for the past 24 hours interval.

Value range: 86400.

Alignment Error The number of alignment errors permitted in a period of time

CRC Error The number of cyclical redundancy check error permitted in a period of time

Oversized Frame The number of oversized frames permitted in a period of time

Collision The number of collision permitted in a period of time


Profile Menu 63

Figure 28 Profile - Ethernet PM Profile - Add / Modify


ADSL PM Profile This command allows configuration on performance thresholds for ADSL traffic. The system supports two time durations, 15 minutes and 24 hours.

Select ADSL PM Profile from Profile menu to open Figure 29. Click Retrieve to obtain the latest information. Refer to Table 12 for more details.

Note: Refer to Chapter 7 for more information of performance profile assignment.



Figure 29 Profile - ADSL PM Profile


Table 12 Profile - ADSL PM Profile Table

Field Description15 Min The number of errors permitted in 15 minutes interval

24 Hr The number of errors permitted in 24 hours interval

LOF The number of frame lost

LOS The number of signal lost

LOL The number of link lost

LPR The number of power lost

ES The number of errored seconds

SES The number of severely errored seconds

UAS The number of unavailable seconds


Profile Menu 65

Figure 30 Profile - ADSL PM Profile - Add / Modify


Access List Profile The iAN8K B1000 system allows user to configure access list profile on the node level, and apply the access list to the inbound or outbound of one or more bridge ports on IPxDSL modules including the WAN ports. Up to ten access lists are allowed on each bridge port and up to 512 access-lists are allowed on the node.

If access list is configured on inbound traffic of the bridge port, the IPxDSL module examines the incoming packet against the access-list in the order it is configured. When the first matched access-list is found, the IPxDSL module permits/denies the packet based on the Action field of the access-list. After a match is found, the IPxDSL module does not continue to examine the remaining



access-list. If no match is found, the packet is discarded. If no access list is configured on inbound of the bridge port, the incoming packet is permitted.

If access list is configured on outbound traffic of the bridge port, the IPxDSL module examines the outgoing packet against the access-list in the order it is configured. When the first matched access-list is found, the IPxDSL module permits/denies the packet based on the Action field of the access-list. After a match is found, the IPxDSL module does not continue to examine the remaining access-list. If no match is found, the packet is discarded. If no access list is configured on outbound of the bridge port, the outgoing packet is permitted.

Only subscriber traffic is subject to ACL rule. In-band management traffic (in VLAN 4093 and 4094) is not subject to ACL filtering.

If upgrading from an old release, where a rule with invalid combination is created, such rule is inherited as it is. (It’s user’s choice to delete or keep these invalid rules)

Select Access List Profile from Profile menu to open Figure 31. Click Retrieve to obtain the latest information.

Note: Refer to Chapter 7 for more information of access list profile assignment.

Figure 31 Profile - Access List Profile


Profile Menu 67

Click Add in Figure 31 to configure profiles. Table 13 lists the variation of the From and To fields and the applicable parameters.

Table 14 lists the valid ACL rule combination supported on the system.

Table 13 Profile - Access List Profile - Add - From / To Table

Field DescriptionAny - Figure 32 Any sources/destination

ARP-Send-IP - Figure 33 Value range: IP address with network mask or with a range

ARP-Send-MAC - Figure 33 Value range: MAC address

Ethernet Type - Figure 34 Value range: Two bytes, hex value

IP Address - Figure 34 IP address with network mask or with a range

Value range: Valid IP address

MAC Address - Figure 35 Value range: Valid MAC address

Protocol Type - Figure 35 Value range: One byte, a decimal value

TCP Port - Figure 36 Port number and range. Starting from x, and for y consecutive numbers

x: 1 to 65535

y: greater or equal to x, less or equal to 65535

UDP Port - Figure 36 Port number and range. Starting from x, and for y consecutive numbers

x: 1 to 65535

y: greater or equal to x, less or equal to 65535

Table 14 ACL Rule Combination Table

From

Any MAC EtherType Arp IP Arp Mac IP Prot Type TCP Port UDP Port

To

Any V V V V V V V V V

MAC V V V V V V V V V

Ether Type V V

Arp IP V V V V

Arp Mac V V V V

IP V V V V V V

Prot Type V V V

TCP Port V V V V

UDP Port V V V V



Figure 32 Profile - Access List Profile - Add - Any to Any

Figure 33 Profile - Access List Profile - Add - ARP-Send-IP To ARP-Send-MAC


Profile Menu 69

Figure 34 Profile - Access List Profile - Add - Ethernet Type To IP Address

Figure 35 Profile - Access List Profile - Add - MAC Address To Protocol Type



Figure 36 Profile - Access List Profile - Add - TCP Port To UDP Port


Packet PriorityClassification

Select Packet Priority Classification from Profile menu to open Figure 37. Click Retrieve to obtain the latest information. Refer to Table 15 for more information

Figure 37 Profile - Packet Priority Classification Window


Profile Menu 71

.

Click Add in Figure 37 to create a new profile. Table 16 lists the variation of the Type fields and the applicable parameters.

Table 15 Profile - Packet Priority Classification Table

Field DescriptionIndex An unique index for the rule

Value range: 1-65535

Name An unique name of the rule

Value range: maximum 32 characters

Priority Value range: 0 - 7

Default: 1

Type Classification type. Refer to Table 16.

IP Protocol Type Values of the classification type. Refer to Table 16.

Table 16 Profile - Packet Priority Classification - Add - Type Table

Field DescriptionDSCP - Figure 38 Value range: 0 - 63, or 6 digits binary format

VLAN ID - Figure 39 Value range: 1 - 4094

IP Protocol Type - Figure 40 Value range: 0 - 255

Send TCP Port - Figure 41 Port number and range. Starting from x, and for y consecutive numbers

x: 1-65535

y: 1 to 65536-x

Send UDP Port - Figure 42 Port number and range. Starting from x, and for y consecutive numbers

x: 1-65535

y: 1 to 65536-x

Receive TCP Port - Figure 43 Port number and range. Starting from x, and for y consecutive numbers

x: 1-65535

y: 1 to 65536-x

Receive UDP Port - Figure 44 Port number and range. Starting from x, and for y consecutive numbers

x: 1-65535

y: 1 to 65536-x

Source IP - Figure 45 & Figure 46 Value range: IP address with subnet mask or with a range

Destination IP - Figure 47 & Figure 48 Value range: IP address with subnet mask or with a range

Ethernet Type - Figure 49 Value range: Heximal value, two bytes

TOS Bits - Figure 50 Value range: 0 - 15, or 4 digits binary format



Figure 38 Profile - Packet Priority Classification - Add - DSCP Window

Figure 39 Profile - Packet Priority Classification - Add - VLAN ID Window


Profile Menu 73

Figure 40 Profile - Packet Priority Classification - Add - IP Protocol Type Window

Figure 41 Profile - Packet Priority Classification - Add - Send TCP Port



Figure 42 Profile - Packet Priority Classification - Add - Send UDP Port

Figure 43 Profile - Packet Priority Classification - Add - Receive TCP Port


Profile Menu 75

Figure 44 Profile - Packet Priority Classification - Add - Receive UDP Port

Figure 45 Profile - Packet Priority Classification - Add - Source IP - IP Address With Subnet Mask



Figure 46 Profile - Packet Priority Classification - Add - Source IP - IP Address Range

Figure 47 Profile - Packet Priority Classification - Add - Destination IP - IP Address With Subnet Mask


Profile Menu 77

Figure 48 Profile - Packet Priority Classification - Add - Destination IP - IP Address Range

Figure 49 Profile - Packet Priority Classification - Add - Ethernet Type



Figure 50 Profile - Packet Priority Classification - Add - TOS Bits


Traffic ManagementProfile

Netman 4000 supports 64 DSL port traffic profile templates and a single linecard supports maximum of 8 profiles (including the default profile) at the same time.

Select Traffic Management Profile from Profile menu to open Figure 51. Click Retrieve to obtain the latest information.

Note: Refer to Chapter 7 for more information of traffic profile assignment.


Profile Menu 79

Figure 51 Profile - Traffic Management Profile


Figure 52 displays the configuration options for Strict Priority scheduler. Figure 53 displays the configuration options for Min/Max with Strict Priority scheduler. Figure 54 displays the configuration options for Min/Max with WRR scheduler. Refer to Table 17 for more details.

Figure 52 Profile - Traffic Management Profile - Add / Modify - Strict Priority



Figure 53 Profile - Traffic Management Profile - Add / Modify - Min/Max with Strict Priority

Figure 54 Profile - Traffic Management Profile - Add / Modify - Min/Max with WRR

Table 17 Profile - Traffic Management Profile - Add / Modify Tables

Parameter Value Range NotesProfile name Character string up to 32 characters

Scheduler Strict Priority, Min-Max with strict priority, Min-Max with WRR

Default: Strict priority

Minimum egress rate for Traffic Class 0 (kbps) 0 - to any 32-bit value Note1



Batch Menu 81

Note: Please note the following for traffic management profile:

1 N/A if scheduler is configured as Strict Priority. For Min-Max with strict priority and Min-Max WRR this field must be provisioned.

2 0 means no limit. Maximum egress rate has to be either 0 or larger than the minimum egress rate configured at same traffic class

3 Valid only if scheduler is configured as Min-max with WRR. The total weight from four traffic class shall equal to 100%. Columbia limitation calls for sharing weight to start from 1%, instead of 0%.

Select a profile in Figure 51 and click Delete to delete the profile. Click Close to exit.

Batch Menu To expedite configuration procedures, Netman 4000 offers batch configuration option. This allows creation of ATM VC and configuration on multiple IPxDSL modules in the system. iAN8K B1000 supports the following options for batch configuration

■ Create ATM VC - Bulk automated creation of ATM VC's on multiple IPxDSL Modules

■ Delete ATM VC - Bulk deletion of ATM VC's on multiple IPxDSL Modules

■ Module Configuration - Bulk configuration of multiple IPxDSL Modules

Create ATM VC This feature allows creating ATM VC's on multiple IPxDSL modules at once.



Maximum egress rate limit for Traffic Class 0 (kbps) 0 - to any 32-bit value Note1 & Note2




Excessive bandwidth sharing weight for Traffic class 0 1%-100% in step of 1%

Default: 25%

Note3


Default: 25%

Note3


Default: 25%

Note3


Default: 25%

Note3

Table 17 Profile - Traffic Management Profile - Add / Modify Tables

Parameter Value Range Notes



When CPE management is disabled, the IPxDSL module supports a pool of 192 PVC and each port supports maximum of 8 PVC.

When CPE management is enabled, the IPxDSL module supports a pool of 168 PVC and each port supports maximum of 7 PVC.

Note: In case that the configuration is not allowed on one or more ADSL ports of a module (e.g. an ATM VC already exists), Netman 4000 skips the entire configuration on the corresponding module, (e.g. no ATM VC is added on any ADSL port for that module) and continues with the rest of the modules.

Note: The Netman 4000 reports to the user, module by module the outcome of the batch configuration. The information conveyed is:

■ Configuration completed

■ No ATM VC is added. Configuration is rejected due to sanity check

■ Node response timeout. The operation might not be executed or only partially executed at the module

Select Create ATM VC from Batch menu to open Figure 55. Select the module type and all the installed modules of the type are displayed. User can modify the module individually or click Select All to select all modules.

Configure the parameters and click Apply to bring the modification into effect. Click Close in Figure 55 to exit the batch configuration window. Refer to Table 18 for more details.

Figure 55 Batch - Create ATM VC Window


Batch Menu 83

Delete ATM VC This feature allows deleting ATM VC's on multiple IPxDSL Modules at once.

Note: In case that the delete configuration is not allowed on one or more xDSL ports of a module (e.g. the xDSL port is unlocked), Netman 4000 skips the entire configuration on the corresponding module, (e.g. no ATM VC is removed from the corresponding module) and continues with the rest of the modules.

Note: The Netman 4000 reports to the user, module by module the outcome of the batch configuration. The information conveyed is:

■ Configuration completed

■ No ATM VC is removed. Configuration is rejected due to sanity check

■ Node response timeout. The operation might not be executed or only partially executed at the module

Select Delete ATM VC from Batch menu to open Figure 56. Select the modules or click Select All to select all modules. Click Apply to delete the selected modules. Click Close in Figure 56 to exit the batch configuration window.

Table 18 Batch - Create ATM VC Table

Field DescriptionVPI Value range: 0 - 255

Default: 0

VCI Value range: 32 - 65535

Default: 35

CoS Value range: UBR

Read only

Connection Type Value range: PVC

Read only

Multiplexing Method Value range:

■ Bridged PDU over RFC2684 with LLC Multiplexing

■ Bridged PDU over RFC2684 with VC Multiplexing

■ VC Multiplexing for PPPoA (convert to PPPoE)

■ LLC Multiplexing for PPPoA (convert to PPPoE)

■ Auto Detection, PPPoA to PPPoE conversion enabled

■ Auto Detection, PPPoA to PPPoE conversion disabled

Default: Bridged PDU over RFC2684 with LLC Multiplexing



Figure 56 Batch - Delete ATM VC Window

Module Configuration This feature allows users to configure multiple IPxDSL modules simultaneously.

Select Module Configuration from Batch menu to open Figure 57. Select the module type from the drop-down box to display all the matching modules in the node. Refer to Table 19 for more details.

Figure 57 Batch - Module Configuration Window


Batch Menu 85

Table 19 Batch - Module Configuration Tables

Field DescriptionSemi Static Forwarding When Semi-static forwarding database feature is enabled, all the learnt MAC address entries of DSL

ports in forwarding database are treated as static configured entry. These entries are not aged out based on aging timer, and these entries are not overwritten by new traffic. These entries are displayed as dynamic entries in Netman 4000.

Value range: Disable / Enable (flush on port down) / Enabled (flush on port lock)

Default: Disable

Gateway ARP Filter The IPADSL module supports a gateway ARP filtering function. When feature is enabled, the IPADSL module monitors the ARP request/reply packets on all ADSL port uplink traffic. The ARP packet is discarded if its "sender protocol address" matches the gateway address configured by the user. The packet discard counter for that bridge port is increased accordingly.

Value range: Enable / Disable

Default: Disable

Gateway IP Address Value range: Valid IP address

Aging Timer To set the bridge ageing timer. The default timer length is 14400 seconds (4 hours). After this interval all the forwarding table entries are flushed.

Value range: 10 to 1000000 seconds

Default: 14400

Unknown VLAN The treatment to unknown VLAN tagged frames.

Value range: Discard / Forward

Default: Discard

Upstream Multicast Filter By enabling this option, the upstream multicast packet will be forwarded to all the ports if they are IP or ARP broadcast packets. OR they will be forwarded as per IGMP snooping rules if it's a IGMP multicast packet with IGMP snooping enabled.


Default: Disable

IGMP last query interval IGMP last query interval

Value range: 1-255

Default: 2

IGMP no-response-leave query interval

IGMP no-response-leave query interval

Value range: 1-255

Default: 2

ILMI Based CPE Management

Enable or disable Interim Local Management Interface for CPE management. When enabled, IPxDSL modules forward the SNMP trap received from ILMI channel to Netman server address.


Default: Enable

ARP Tracking Provides information on the mapping between subscriber's IP address and MAC address. It is implemented by snooping the ARP traffic passing through the module. The ARP table provides a history of snooping results.


Default: Disable



NetBIOS Filter When NetBIOS filter is enabled, incoming packet filters are applied on all ADSL ports and Ethernet port; to filter out (discard) the NetBIOS packets that are encapsulated over TCP/UDP or directly carried by IEEE 802.2 LLC

Value range: Disabled / Uplink Only / Both Directions

Default: Uplink Only

DHCP Filter This can be used to avoid subscribers getting DHCP service from an unauthorized DHCP server if existing on a user port.

■ Uplink Filter - When enabled, an incoming packet filter is applied on all ADSL ports, as a result, all DHCP server to client packets are discarded

■ Downlink Filter - When enabled, an outgoing packet filter is applied on all ADSL ports, as the result, all DHCP client to server packets are discarded

Value range: Disabled / Uplink Only / Downlink Only / Both directions

Default: Disabled

DLF Counter (Database Lookup Failure)

Database Lookup Failure (DLF) occurs when the IPxDSL module cannot find an entry, within its database, for the incoming Ethernet frame. The IPxDSL module allows operator to limit the rate of total DLF frames that could be forwarded (e.g. broadcast) by the bridge. Within a period of one second, if the total number of DLF frames (including the latest one) is less or equal to the threshold specified by the user, the latest DLF frame are forwarded to all ports excluding the one from which the DLF frame is received; if the total number of DLF frames is larger than the threshold specified by the user, the latest DLF frame is discarded. The discarding is counted in the bridge discarding PM counter.

Value range: 10 - 65535 DLF frames per second

Default: 100

IGMP Snooping IGMP is a protocol used by IP hosts to register their dynamic multicast group membership. The switches uses information in the IGMP packets to determine which segments should receive packets directed to the group address. IGMP snooping allows bridges to monitor IGMP packets and reduces the flooding of IP multicast traffic through the ADSL access line.

Value range: Enabled, forward unknown/ Enabled, discard unknown / Disabled

Default: Enabled, discard unknown

DHCP Option 82 The DHCP relay agent information option (option 82) enables a Dynamic Host Configuration Protocol (DHCP) relay agent to include information about itself when forwarding client-originated DHCP packets to a DHCP server. The DHCP server can use this information to implement IP address or other parameter-assignment policies.iAN8K B1000 supports DHCP Option 82 feature on all linecard modules in compliance with IETF RFC3046 with some exceptions as explained above. This feature is enabled/disabled on a per module basis. The Option 82 feature is disabled by default.


Default: Enable


Field Description


Video Service Menu 87

User can modify the module individually or click Select All to highlight all the modules of the same type. Click Apply to bring the modification into effect. Click Close in Figure 57 to exit the batch configuration window.

Note: In case that part of the configuration is not allowed on one module (e.g. the ADSL port is unlocked therefore encapsulation method is not changed), Netman 4000 skips the entire configuration on the corresponding module, and continues with the rest of the modules.

Video Service Menu iAN8K B1000 provides full video service management capabilities. iAN8K B1000 provides full video service management capabilities. iAN8K B1000 supports 256 video channels, including both full access and preview channels. Each channel can be individually configured for the data rate, maximum duration for each preview, maximum number of previews, and blackout duration after each preview. Each broadcast channel is logically mapped to a multicast group and the multicast groups can be grouped together into up to 32 different service packages.

A CAC facility is provided at the line card level which can be used to ensure video bandwidth for each port on the card as well as the entire card. Users can be assigned any number of packages with authentication performed at the PVC level.

The steps required for provisioning video services in which all subscribers are assigned a package of channels consists of the following steps. Refer to Appendix A - Access Configuration Example for details.

1 Enable IGMP snooping on ICM3

2 Enable IGMP snooping on each linecard

3 Create multicast group

IGMP last query count IGMP last query count

Value range: 0 - 3

Default: 1

IGMP no-response-leave query count

IGMP no-response-leave query count

Value range: 1 - 3

Default: 1

PPPoE Intermediate Agent Enable or disable PPPoE Intermediate agent. The PPPoE Intermediate Agent intercepts PPPoE discovery packets, including PADI, PADO, PADR, and PADS. Upon reception of a PADI or PADR packet sent by the PPPoE client, the Intermediate Agent adds a TAG to the packet sent upstream. The TAG contains the identification of the DSL line on which the PADI or PADR packet was received.


Default: Enable


Field Description



4 Create multicast packages

5 Create users

6 Enable authentication on each PVC

7 Check usage statistics

iAN8K B1000 supports the following options for video service configuration:

■ Multicast Group Packaging

■ Access Control

■ Usage Statistics

Multicast GroupPackaging

Select Multicast Group Packaging from Video Service menu. Multicast group packaging supports the following configuration:

■ Default Rate

■ Multicast Group

■ Multicast Package

Default RateSelect Multicast Group Packaging from Video Service menu and the Default Rate window is promoted as shown in Figure 58. Figure 58 allows configuration on the default data rate of the learned multicast group. The default value is 4000 and the value range is from 64 to 32000 Kbps.

Click Retrieve to obtain the latest information. Modify the rate and click Apply to take the modification into effect.

Figure 58 Video Service - Multicast Group Packaging - Default Rate



Multicast GroupSelect Multicast Group Packaging from Video Service menu and select Multicast Group tab to open Figure 59. Click Retrieve to obtain the latest information. Refer to Table 20 for more information.

Figure 59 Video Service - Multicast Group Packaging - Multicast Group

Table 20 Video Service - Multicast Group Packaging - Multicast Group Field Description

Field DescriptionGroup Name The name of the multicast group.

Value range: a character string up to 32 characters.

IP Address The IP address of the multicast group

Value range: valid IP address

Rate The committed data rate of the multicast group to be used in CAC calculations.

Value range: 64 - 32000

Default: 4000



Click Add in Figure 59 to create a new entry. Or select an entry and click Modify to modify an existing entry. Configure the parameters and click Apply in Figure 60.

Figure 60 Video Service - Multicast Group Packaging - Multicast Group - Add

Session Timeout The maximum number of seconds the user can access this multicast group. This attribute is enforced when the subscriber has limited access to this multicast group. When a session time exceeds configured session timeout, the subscriber's DSL interface is removed from the multicast group, and all future joins are prohibited until the subscriber's session time is reset. The session time is recognized only if it exceeds recognition time. The session time is cumulative.


Default: 120

Max Joint Count The maximum number of times a particular user can join this multicast group. This attribute is enforced when the subscriber has limited access to this multicast group. When a subscriber's join count exceeds the MAX Join count, the subscriber's DSL interface is removed from the multicast group, and all future joins are prohibited until the subscriber's join count is reset. Max join count is not updated if the session time is less than the recognition time.


Default: 10

Blackout Period The wait time between two consecutive join of a multicast group by the same subscriber. This attribute is enforced when the subscriber has limited access to this multicast group.


Default: 60

Table 20 Video Service - Multicast Group Packaging - Multicast Group Field Description

Field Description




Multicast PackageSelect Multicast Group Packaging from Video Service menu and select Multicast Package tab to open Figure 61. Click Retrieve to obtain the latest information. Refer to Table 21 for more information.

Figure 61 Video Service - Multicast Group Packaging - Multicast Package

Click Add in Figure 61 to create a new entry. Or select an entry in Figure 61 and click Modify to modify an existing entry. Check mark the groups and click Apply in Figure 62.

Table 21 Video Service - Multicast Group Packaging - Multicast Package Field Description

Field DescriptionPackage Name The name of the multicast package.

Multicast group list The name of the multicast group.

Up to 256 multicast group names.



Figure 62 Video Service - Multicast Group Packaging - Multicast Package - Add


Access Control Select Access Control from Video Service menu. Access control supports the following configuration:

■ Account lockout Policy

■ Reset Period

■ User Account

Account lockout PolicySelect Access Control from Video Service menu and the Account Lockout Policy window is promoted as shown in Figure 63. Click Retrieve to obtain the latest information. Modify the parameters and click Apply to take the modification into effect. Refer to Table 22 for more information.



Figure 63 Video Service - Access Control - Account Lockout Policy

Reset PeriodSelect Access Control from Video Service menu and select Reset Period tab to open Figure 64. Click Retrieve to obtain the latest information. Modify the parameters and click Apply to take the modification into effect.

Table 22 Video Service - Access Control - Account Lockout Policy Field Description

Field DescriptionQuiet Period (seconds) 0-300 disables quiet period.

Default: 10

Max Consecutive Failures 1-100

Default: 20



Figure 64 Video Service - Access Control - Reset Period

User AccountCreate multicast users to enforce authentication against the video services. Users can be granted full or limited access to packages, providing an additional level of capability. The user entries are placed in a database located on the ICM3 and it supports a maximum of 1024 users. It is important to know that the authentication database is for the entire iAN8K B1000, i.e. for all line cards in the iAN8K B1000 system. Further it is important to know that each iAN8K B1000 has its own database.

Select Access Control from Video Service menu and select User Account tab to open Figure 65. Click Retrieve to obtain the latest information.

Figure 65 Video Service - Access Control - User Account



Click Add in Figure 65 to create a new entry. Or select an entry and click Modify to modify an existing entry. Configure the parameters and click Apply in Figure 66.

The format and parameters of the user name are:

node_id:shelf_id:slot_id:port_id:vpi.vci■ node_id: an integer from 1 to 9999

■ shelf_id: an integer from 1 to 4

■ slot_id: an integer from 1 to 16

■ port_id: an integer from 1 to the number of DSL ports

■ vpi.vci: ATM virtual circuit over the DSL line

Figure 66 Video Service - Multicast Group Packaging - User Account - Add




Usage Statistics The iAN8K B1000 collects usage statistics on a per multicast user basis. A record is triggered when a user leaves a multicast group. A usage recognition time provides a specific period of time before a channel switchover (multicast leave and join) is recognized as a true channel change. This is to avoid unnecessary record generation due to channel surfing. This factor comes into play because the iAN8K B1000 has storage for 2400 usage records before a rollover occurs.

Select Usage Statistics from Video Service menu. Usage statistics supports the following configuration:

■ Call Usage Recognition Time

■ Usage Statistics

Call Usage Recognition TimeSelect Usage Statistics from Video Service menu and the Call Usage Recognition Time window is promoted as shown in Figure 67. Click Retrieve to obtain the latest information. Modify the parameter and click Apply to take the modification into effect.

Figure 67 Video Service - Usage Statistics - Call Usage Recognition Time

Usage StatisticsSelect Usage Statistics from Video Service menu and select Usage Statistics tab to open Figure 68. Click Retrieve to obtain the latest information.


Tools Menu 97

Figure 68 Video Service - Usage Statistics - Usage Statistics

Tools Menu

MAC Tracing MAC tracing is to identify the subscriber location according to the given MAC address and VLAN.

With the subscriber MAC address and VLAN ID, iAN8K B1000 can lookup the forwarding table to check which DSL port the subscriber come from. Four cases may encounter:

1 Cannot find the MAC address binding with VLAN ID throughout the IPiAN8K B1000. In this case, respond "Cannot identify";

2 The IPiAN8K B1000 finds the request MAC address binding with VLAN ID is learned at uplink port, respond "The subscriber may be connected to other equipment";

3 The IPiAN8K B1000 finds the MAC address binding with VLAN ID is learned internal port connected to LC at ICM board but cannot find it at corresponding LC, respond "Cannot identify";

4 A successful lookup. Respond the subscriber port information of shelf ID, slot ID, port ID and VLAN ID. The VLAN ID is the requested VLAN ID.

Select MAC Tracing from Tools menu to open Figure 69. Configure the parameters and click Get to obtain the trace information.



Figure 69 Tools - MAC Tracing


3
PROVISIONING - NODE
This chapter provides configuration information for iAN8K B1000 node. iAN8K B1000 supports the following node level configuration:

■ System

■ IP Address

■ Time Server

■ NMP Access

■ ARP

■ Routing Table

■ Reset

■ Master Shelf Configuration

■ Slave Shelves Configuration

■ Linecard Image File Information

System Select the node to display the system information shown in Figure 70. Click Retrieve to obtain the latest configuration information. Modify the parameters and click Apply to bring the modification into effect. Refer to Table 23 for more information.


100 Chapter 3: Provisioning - Node

Figure 70 Node - System Window

IP Address Netman 4000 uses IP addressing to identify all the iAN8K B1000 nodes in a network for network management. Each node in the network must have a unique IP address to ensure reliable network management connectivity.

The IP pool consists of IP addresses assigned to ICM3 modules and every IPxDSL modules in the system. The IP addresses must be configured properly prior to the system starts up. To avoid service interruption, do not change the configuration in this section during the operation.

Select the node and click IP Address tab to open Figure 71. Refer to Table 24 for more details.

Table 23 Node - System Table

Parameter DescriptionSystem Uptime The duration of time that the node is up since the last reset.

System Description The type of the system

System Name A unique name given to the node for identification

System Location The physical location of the node

Contact Information Contact information customized by the administrator


IP Address 101

Figure 71 Node - IP Address Window

Table 24 Node - IP Address Table

IP Address Description

ICM IP addressPrimary IP The IP address of the node. This is the management IP address assigned to ICM3.


Default: 10.20.30.1

Subnet Mask A mask used to determine what subnet an IP address belongs to.

Value range: valid netmask

Default: 255.255.255.0

Trap Destination to NetmanDestination 1 The first IP address of the PCs to which the trap messages will be sent. One of these is generally set to

the IP Address of the Netman 4000 Server (on an Ethernet network) and it is recommended that the other be set as the PPP Interface Peer address of the node.


Destination 2 The second IP address of the PCs to which the trap messages will be sent. One of these is generally set to the IP Address of the Netman 4000 Server (on an Ethernet network) and it is recommended that the other be set as the PPP Interface Peer address of the node.




Modify the parameters and click Apply to bring the modification into effect. Click Retrieve to obtain the latest configuration information.

Note: The following trap categories for the trap messages are supported:

■ ICM module cold start

■ LC module cold start

■ DSL link down

■ DSL link up

■ Ethernet link on ICM down

■ Ethernet link on ICM up

■ Removal of module

■ Fan Alarm

■ Power module failure

■ Session record reporting enabled

■ Session record reporting disabled

■ IGMP joint over CAC threshold

IP Pool for Line CardStarting IP Address The starting IP address of IPxDSL modules in the IP Pool.


Default: 192.168.100.1



Default: 255.255.255.0

IP Pool Size The size of the IP Pool. The entire range is the sum of starting address of the IP Pool and the size.

Default: 33

Read only.

IP Pool for Standby ICMStarting IP Address The starting IP address of the standby ICM3 module in the IP Pool.


Default: 192.168.200.1



Default: 255.255.255.0

IP Pool Size The size of the IP Pool. The entire range is the sum of starting address of the IP Pool and the size.

Default: 2

Read only

Table 24 Node - IP Address Table

IP Address Description


Time Server 103

■ Invalid community string in the received SNMP message

■ Invalid username or password detected during CLI login

Time Server The Network Time Protocol (NTP) and Simple Network Time Protocol (SNTP) are widely used to synchronize computer clocks in the global Internet. It provides comprehensive mechanisms to access national time and frequency dissemination service, organize the time-synchronization subnet and adjust the local clock in each participating subnet peer. In most places of today's Internet, NTP provides accuracies of 1-50 ms depending on the characteristics of the synchronization source and network paths. NTP and SNTP are designed for use by clients and servers with a wide range of capabilities and over a wide range of network delays and jitter characteristics.

Assigning a SNTP server address helps maintaining a synchronous time across nodes spread out over a geographical area. It thus provides more accuracy in report generation and statistical analysis.

Select the node and click Time Server tab to open Figure 72. Click Retrieve to obtain the latest configuration information. Modify the parameters and click Apply to bring the modification into effect.

Figure 72 Node - Time Server Window



NMP Access iAN8K B1000 system supports network management port (NMP) access control. Netman 4000 allows user to disable and enable the NMP access control based on SNMP, telnet or both.

The iAN8K B1000 node processes SNMP/Telnet packets from legitimate IP source address/Netman 4000 clients only. Packets containing illegitimate source address are discarded and the system generates system log entries when receiving these packets. IP source addresses are designated legitimate by creating an access list. There can be up to three entries in for SNMP access list and up to ten entries for Telnet access list. Each entry contains an IP address and a network mask. Different classes of IP address and mask can be used to designate a range of IP address as legitimate IP addresses. By default NMP is disabled.

Select the node and click NMP Access tab to open Figure 73. Refer to SNMP section or Telnet section for more configuration details.


NMP Access 105

Figure 73 Node - NMP Access Window

SNMP In the Snmp section of Figure 73, click Add button and Figure 74 prompts for SNMP information. Configure the parameters and click Apply to add the entry. Maximum of 3 SNMP entries can be configured.



Figure 74 Node - NMP Access - Add SNMP Entry Window

Select an entry in Figure 73 and click Delete to remove the SNMP entry. SNMP must be disabled before an entry can be removed.

Select the Enable or Disable radio button and click Apply to enable or disable SNMP access control.

Click Retrieve in the SNMP section to obtain the latest configuration information.

Telnet In the Telnet section of Figure 73, click Add button and Figure 75 prompts for telnet information. Configure the parameters and click Apply to add the entry. Maximum of 10 Telnet entries can be configured.

Figure 75 Node - NMP Access - Add Telnet Entry Window

Select an entry in Figure 75 and click Delete to remove the telnet entry. Telnet must be disabled before an entry can be removed.

Select the Enable or Disable radio button and click Apply to enable or disable Telnet access control.

Click Retrieve in the telnet section to obtain the latest configuration information.


ARP 107

ARP ICM3 module learns ARP entries from the received ARP request messages. iAN8K B1000 ensures that any IP traffic originated from the DSL subscriber only appears on one and only one subscriber Ethernet interface. Hence, the ICM3 module can correctly discover and associate the subscriber IP address with the Ethernet interface and insert a route entry into the routing table without static configuration or the aid of complex dynamic routing protocols

ICM3 sends ARP requests when it needs to:

■ resolve correct mapping between an IP address and MAC address

■ a complete ARP entry times out

■ ARP response timeout for incomplete ARP entries.

A complete ARP cache entry is one that has complete MAC and IP address mapping. Timeout triggers new address resolution (confirmation) attempt. If the attempt succeeds, the timer restarts. If it fails, the entry will not be used for forwarding and the user shall see the entry as incomplete.

The timeout for new incomplete dynamic ARP entries during address resolution for is three times of the retransmission timeout. After timeout the entry is not used for forwarding and it is displayed as incomplete. An incomplete ARP cache entry is one that does not have full MAC address information.

Select the node and click ARP tab to open Figure 76. Configure the parameters and click Apply to bring the modification into effect. Click Retrieve to obtain the latest information. Refer to Table 25 for more details.



Figure 76 Node - ARP Window

When the Complete Entry Timeout or the Retransmission Timeout is modified, the new timers do not effect the existing ARP entries. Those existing entries continue to use the previous timer value until the complete entry timer expires. Then when the ICM3 refreshes those entries, the new timer is used for these entries.

Table 25 Node - ARP Field Description

Field DescriptionComplete Entry Timeout Valid range: 1 - 30 minutes

0: Disable

Default: 20 minutes

Retransmission Timeout Valid range: 1 - 30 seconds

Default: 1 second

VLAN ID VLAN ID number

MAC Address The MAC address of a subscriber.

IP Address The IP address of a subscriber.

Type Value range: Dynamic / Static

Static ARP entries remains in the table until manually deleted by the operator.


Routing Table 109

Click Add in Figure 76 and Figure 77 prompts for new entry information. Or select an entry in Figure 76 and click Modify to modify the entry. Configure the parameters and click Apply to create the new entry.

Figure 77 Node - ARP - Add Window

Select a static entry in Figure 76 and click Delete to remove a static entry. Or click Delete All to remove all entries.

Note: only static entry can be deleted.

Routing Table This section provides configuration for management data route only. The subscriber data routing is governed by the data plane routing table. Please refer to Chapter 4 - Provisioning - ICM3/3G Module for more information.

The default route is indicated by a destination IP address of 0.0.0.0 with the subnet mask of 0.0.0.0. Only ONE default route can be set in the system to be used for both management and data traffic. This shall be kept in mind when planning and provisioning a default route in the network.

Select the node and click the Routing Table tab to open Figure 78. Click Retrieve in the to obtain the latest configuration information. Refer to Table 26 for more information.



Figure 78 Node - Routing Table Window

Table 26 Node - Routing Table Table

Field DescriptionNumber Index number of the entries

Type Value range: Static / Connected Interface

Destination Destination IP address

The default route is indicated by a destination IP address of 0.0.0.0 with the subnet mask of 0.0.0.0.

Subnet Mask Subnet mask

Gateway Address Gateway IP address


Reset 111

Click Add to add a new entry in Figure 79. Configure the parameters and click Apply to add the entry.

Figure 79 Node - Routing Table - Add Window

Select an entry and click Delete in Figure 78 to delete a specific entry.

Reset Netman 4000 provides reset function that allows software reset or hardware reset on the node and the modules.

■ ICM3 module

ICM3 supports both hardware and software reset.

Interface The VLAN interface

Metric Route metric. Not applicable to static routes.

Value range:

■ 1 - 65535 for internal routes

■ 1 - 1667214 for external routes

Administrative Distance Configurable for static routes. Read only for dynamic routes. 0 for connected interface routes.1 for all other static routes.


Table 26 Node - Routing Table Table

Field Description



The hardware reset on the ICM3 will forcibly move any ICM3 upgrade image in flash to memory and boot with the new image irrespective of whether the new image is the same, higher or lower than the previous image version. The software reset is used to recover the module from any software loop conditions or other anomalies. The ICM3 also checks if there is a higher version upgrade image available in the flash. If so then the higher version is moved from the flash to the running memory and the ICM3 boots with the new upgrade image.

■ Line module

Hardware reset forces download of software image from ICM3 to a line card irrespective of the version on the line card. For virtual modules, this hardware reset is performed after a software reset. The hardreset forces line module to download software image from ICM3 before reboot. If the corresponding LC software image is not in the ICM3 flash during the hardreset, the reset is applied but no download of software image from ICM3 is required.The softreset allows line modules to check the software version and software is downloaded when there is a higher version available in ICM 3Flash than the one running on the module. If the corresponding LC software image is not in the ICM3 flash or has equal or lower version, the reset is applied but no download of software image from ICM is required.A software reset can also be used to recover the module from any software loop conditions or other anomalies. A typical example is; though the card is physically presented in the system but the system does not recognize the module correctly. In such scenarios, a software reset shall be followed by a hardware reset.

■ PCU module

PCU supports both hardware and software reset.The hard reset forces the PCU module to download software image from ICM3 and reboot.The soft reset forces the PCU module to reboot without downloading software image from ICM3. There is no checking of software version during the soft reset.

■ ISM module

ISM module supports only software reset. The soft reset forces the ISM module to reboot. For module software upgrade and download, please refer to Chapter 11 - System Administration for more information.

■ ASM module

ASM module supports only software reset. The soft reset forces the ASM module to reboot. For module software upgrade and download, please refer to Chapter 11 - System Administration for more information.


Reset 113

Select the node and click Reset tab to open Figure 80. All modules are indicated with its shelf ID and slot ID. Click Retrieve to obtain the latest modules information.

Figure 80 Node - Reset Window

CAUTION: If you reset the system after erasing all configurations the communication via SNMP (Netman) will be disabled. By design the AN-2000 IPiAN8K B1000 won’t communicate over SNMP with Netman (or any other SNMP Manager) until the Netman IP address has been entered. You’ll need to configure one or two Netman IP addresses via CLI command “netman-destination” found on page 325 of the CLI manual to restore SNMP.



There are 2 possible entries here for “primary” and “secondary” for the Netman address. It basically maps to the Trap Destination Setup on Netman’s Device Manager screen. As long as these addresses are non-zero it will allow SNMP communication. The addresses don’t have to point to valid Netman Server addresses. However you’ll need valid addresses if you expect to receive traps from the node at these locations.

For ICM3 module, select the module from Reset ICM3 section and click Hard Rest or Soft Reset radio button. Click Reset to begin the reset.

For IPxDSL and PCU modules, select the module from Reset Module section and click Hard Rest or Soft Reset radio button. Click Reset to begin the reset.

For ISM module or ASM module, select the module and click Soft Reset radio button. Click Reset to begin the reset. The Reset button is not available if the Hard Reset radio button is selected.

Master Shelf Configuration

Master Shelf Configuration provides basic information of the master and slave shelves. It also allows registering and deregistering slave shelves to the master shelf. All slave shelves must register to the Authorized Slave Shelf in order to communicate with the master shelf.

Note: This feature is applicable when there are slave shelves configured in the node.

Select the node and click Master Shelf Configuration tab to open Figure 81. Click Retrieve to obtain the latest information. Configure the parameters and click Apply to take the modification into effect.

Select a slave shelf ID in the Authorized Slave Shelves Information section and click Delete or Add to deregister or register the shelf. Refer to Table 27 for more details.


Master Shelf Configuration 115

Figure 81 Node - Master Shelf Configuration Window

Table 27 Node - Master Shelf Configuration Table

Field Description

Master InformationMaster Shelf Id Value range: 1 ~ 8

Last Command Time The timestamp of the last command

Last Command Type Value range: SNMP / CLI



Note: Adding or deleting shelf in the authorized slave list will not automatically update the node tree on the left, since it is possible that only the configuration has been added at this point but these slave shelves have not yet registered. The user must update the node tree manually.

Slave Shelves Configuration

Slave Shelves Configuration provides basic information of the slave shelves. It provides the option to erase all configuration data of multiple shelves at once. It also supports manual synchronization of entire generic configuration between master shelf and selected slave shelf.


Select the node and click Slave Shelves Configuration tab to open Figure 82. Click Retrieve to obtain the latest information. Refer to Table 28 for more details.

Last Command Result last per-command generic configuration synchronization result

Value range: Successful / Not Successful

Registered Slave Shelves Count

Number of shelves registered

Reachable Slave Shelves Count

Number of shelves registered and reachable

Generic Flash Version Flash entire generic configuration version #

Generic Runtime Version Runtime entire generic configuration version #

Accepting Generic Configuration Changes

Value range: Yes / No / Busy

Tftp Trigger Slave shelf base part application image file synchronization control Flag. This value applies to all slaves shelves.

Value range: Force Sync on Slave Lower Version / Never Sync

Authorized Slave Shelves InformationAuthorized slave shelves Value range: 1 ~ 8 excluding master shelf id

Table 27 Node - Master Shelf Configuration Table

Field Description


Slave Shelves Configuration 117

Figure 82 Node - Slav Shelves Configuration Window

Table 28 Node - Slav Shelves Configuration Table

Field DescriptionShelf ID Slave shelf ID number

Value range: 1 ~ 8

Registered Time The date and time of the slave shelf registered with the master shelf

MAC Address MAC address of the slave shelf

Reachable Status The status of the slave shelf

Value range: Reachable / Unreachable

Last Generic Conf Sync Start time

Last entire generic configuration synchronization starting time

Generic Conf Sync Status Last entire generic configuration synchronization result

Value range: Success / Failure / No need to synchronize

F/W Sync Status Firmware synchronization status

Value range: Synchronized / Not Synchronized

Erase All Data Erase all configuration data of the shelf

Drop down box selection

Value range: No / Yes



Select a slave shelf and click Manual Sync to synchronize the entire generic configuration between master shelf and the selected slave shelf. Select another shelf and proceed with the same procedure if needed.

Select Yes from the Erase All Data drop down box to erase the configuration data for the selected shelves. Click Apply to confirm the erase.

Linecard Image File Information

Linecard Image File Information provides basic information of the firmware on the slave shelves ICM3 modules. This is used to determine the software currently available from ICM3 for upgrade process or module reset.


Select the node and click Linecard Image File Information tab to open Figure 83. Click Retrieve to obtain the latest information. Refer to Table 29 for more details.

Generic Flash Version Flash entire generic configuration version number

Generic Runtime Version Runtime entire generic configuration version number

Current Firmware Version Current generic configuration version number

Updated Firmware Version Updated generic configuration version number

Table 28 Node - Slav Shelves Configuration Table

Field Description


Linecard Image File Information 119

Figure 83 Node - Linecard Image File Information Window

Table 29 Node - Linecard Image File Information Table

Field DescriptionShelf ID Slave shelf ID number

Linecard Firmware File Name Linecard firmware file name currently on the slave shelf ICM3

Linecard Firmware File Version Linecard firmware file version number currently on the slave shelf ICM3




4
PROVISIONING - ICM3/3G MODULE
This chapter provides configuration procedures for IP Concentration Module (ICM3/3G). The IP Concentration Module (ICM3/3G) is a high performance module that provides system controller, management and L2/L3 functionality to IP DSLAM system. Additionally the ICM3/3G provides FE/GE uplinks interfaces providing connectivity to IP networks.

ICM3/3G is the mandatory module for IP DSLAM Release 3.x system. It controls all other line modules in the system and it also provides element management agent function and connects to Netman 4000 EMS. Figure 84 and Figure 85 shows the main window of the ICM3/3G provisioning management.

Figure 84 Provisioning - ICM3 Window


122 Chapter 4: Provisioning - ICM3/3G Module

Figure 85 Provisioning - ICM3GWindow

ICM3/3G Module supports the following configurations:

■ Node Level Configuration

■ Reset

■ Module Summary

■ Shelf Level Configuration

■ Slot Level Configuration

■ ICM3/3G

■ Forwarding Database

■ Mirror Port

■ Trunk Group

■ Protection Link

■ Redundancy Support

■ Switchover


Node Level Configuration 123

■ VBAS

■ External Ethernet Port (Standby ICM3/3G module only)

■ Port Level Configuration

■ Ethernet Port Configuration

■ RSTP

■ VLAN

■ Multicast

■ Routing (Master shelf ICM3 module only)

■ DHCP (Master shelf ICM3/3G module only)

■ Packet Classification (Master shelf ICM3/3G module only)

■ QoS

Node Level Configuration

ICM3/3G module supports module reset at the node level configuration.

Reset ICM3/3G module supports both hardware reset and software reset through Netman 4000.

The hardware reset on the ICM3/3G will forcibly move any ICM3/3G upgrade image in flash to memory and boot with the new image irrespective of whether the new image is the same, higher or lower than the previous image version.

The software reset is used to recover the module from any software loop conditions or other anomalies. The ICM3/3G also checks if there is a higher version upgrade image available in the flash. If so then the higher version is moved from the flash to the running memory and the ICM3/3G boots with the new upgrade image.

Select the node and click Reset tab to open Figure 86. All modules are indicated with its shelf ID and slot ID. Click Retrieve to obtain the latest modules information.

Select an ICM3/3G module, click Hard Rest or Soft Reset radio button and click Reset to begin the reset.



Figure 86 ICM3 - Node - Reset Window

Module Summary Module Summary section provides basic information and module location for PCU module.

Expand the node from the navigation tree and select Module Summary to open Figure 88 or Figure 88. Click Retrieve to obtain the latest information. Refer to Table 30 for more details.


Module Summary 125

Figure 87 ICM3G- Module Summary Window



Figure 88 ICM3- Module Summary Window

Shelf Level Configuration

The shelf level configuration provides the actual slot occupier for the entire chassis.

Expand the node from the navigation tree and select Shelf to open Figure 89 or Figure 90. Click Retrieve to obtain the latest information.

Table 30 ICM3/3G - Module Summary Table

Field DescriptionModule Module type

Entity Module location

X-Y: Shelf X Slot Y

PCU module is always at slot P

Hardware Version Module hardware version number

Software Version Module software version number


Shelf Level Configuration 127

Figure 89 ICM3 - Shelf View Window



Figure 90 ICM3G - Shelf View Window

In Figure 89 or Figure 90, the ICM3/3G modules are represented with board images in slot A and B. Double click on the board image opens the Slot Level Configuration.

Table 31 lists the guidelines for module placement and virtual configuration detail.

Slot Level Configuration

Active ICM3/3G module supports the following configuration at the slot level:

■ ICM3/3G


■ Mirror Port

■ Trunk Group

Table 31 ICM3/3G Module Placements Details

Module TypeMaximum Number of Board Per Shelf Slot Used Virtual Configuration

ICM3/3G 2 A, B No


Slot Level Configuration 129

■ Protection Link

■ Redundancy Support

■ Switchover

■ VBAS

Standby ICM3/3G module supports the following configuration at the slot level:

■ ICM3/3G

■ External Ethernet Port

Note: On the ICM3/3G modules, retain only the files required for the modules existed in the node. Keeping unnecessary files will consume the flash memory, which may hinder the synchronization between the active and standby ICM3/3G.

ICM3/3G Select the active or standby ICM3/3G module from the tree view to open Figure 91. Click Retrieve to obtain the latest information. Refer to Table 32 for more details.

Figure 91 ICM3/3G - ICM3 Window



Forwarding Database The switch configuration window displays and allows the configuration of layer 2 switch related information. The Address Resolution Logic (ARL), on receiving a destination address, determines the destination port number to identify the port the frames will be forwarded to. If the ARL cannot find and identify the Destination Address (DA), the frame is treated as a frame with an unknown DA. One of the following mechanisms can be used to handle the frames with unknown DA.

■ When DLF frame discard is enabled, the MAC frame with unknown unicast destination address is discarded.

■ When DLF frame forward is enabled, the MAC frame with unknown unicast destination address is sent to all ports in the same VLAN except the source port.

■ Broadcast frames are forwarded to all ports within the same VLAN except the source port itself.

Select the active ICM3/3G module from the tree view and select Forwarding Database tab to open Figure 92. Click Retrieve to obtain the latest information. Configure the parameters and click Apply to take the modification into effect. Refer to Table 33 for more details.

Table 32 ICM3/3G - ICM3/3G Table

Field Name DescriptionHardware Version The current hardware version for the ICM3/3G module.

Software Version The current software version for the ICM3/3G module.

Serial Number Module serial number

Uptime The duration of time that the ICM3/3G module is up since the last reset



Figure 92 ICM3/3G - Forwarding Database Window

Click Reset in Figure 92 to reset the switch engine for the selected VLAN.

Table 33 ICM3/3G - Forwarding Database Table

Field DescriptionDLF frame To discard the MAC frame with unknown unicast destination address or to

forward the MAC frame with unknown unicast destination address to all ports in the same VLAN, except the source port.

Value range: Forward / Discard

Default: Forward

Aging timer The layer two switch-aging timer in seconds. The aging time is the number of seconds a MAC address is kept in the forwarding database after having received a packet from this MAC address. The entries in the forwarding database are periodically timed out to ensure they won't remain in the table forever.

Value range: 10 - 1000000 seconds

Default: 300 seconds

VLAN ID To display the forwarding rules of the selected VLAN

Static Entries

MAC Address The Mac address of the port.

Port ID The port ID number

VLAN ID The VLAN ID number



Click Dynamic Entry in Figure 92 to view dynamic entry lists shown in Figure 93. Select a VLAN ID in Figure 93 and click Retrieve to obtain the latest information. Click Close to exit the window.

Figure 93 ICM3/3G - Forwarding Database - Dynamic Entry Window

Click Add in Figure 92 to create a new static entry. Configure the parameters and click Add in Figure 94.

Figure 94 ICM3/3G - Forwarding Database - Add Window

Select an entry and click Delete in Figure 92 to remove the entry.

Mirror Port Port Mirroring is a process whereby one switch port, the mirror port, can be configured to reflect the traffic appearing on another port, the monitored port.



ICM3/3G allows any port (external FE, GE) to be the mirror port to monitor transmit and/or receive activity of any of remaining FE or GE port. Two different ports can be configured as monitored ports simultaneously, one for transmit traffic and one for receive traffic.

The receive-port and transmit-port can be the same port. The bandwidth of the receive-port and transmit-port cannot exceed the mirror-port. Otherwise the mirror port is not able to fully capture the traffic on the monitored ports.

Select the active ICM3/3G module from the tree view and select Mirror Port tab to open Figure 95. Click Retrieve to obtain the latest information. Configure the parameters and click Apply to take the modification into effect. Refer to Table 34 for more details.

Figure 95 ICM3/3G - Mirror Port Window



Note: A port cannot be configured as mirror port if it is a part of a trunk group and vice-versa. Mirrored transmit port and receive port can be the same port or different port.

Trunk Group Port trunking or link aggregation is used to combine a number of ports together to make a single high-bandwidth data pipeline. The participating parts are called members of a trunk group. ICM3/3G module supports link aggregation of 2 or 4 ports into a logical link of up to 400 Mbps. The two GE ports can also be aggregated to for a 2 Gbps trunk port. Ports that are used to support xDSL applications (internal ports) cannot be used for link aggregation. A port cannot be part of more than two trunk groups i.e. no overlapping is allowed.

When a trunk group is created, static entries in forwarding database originally mapped to the member ports are now mapped to trunk port and dynamic entries are automatically removed. When a trunk is removed, entries in forwarding database or ARP entries mapped to trunk port are automatically removed.

A trunk group cannot be created if one or more of the following condition exists:

■ The candidate trunk member port is an IGMP multicast router port

■ The candidate trunk member port is a mirror port

■ The candidate trunk member ports have different orientations

■ The candidate trunk member ports belong to different VLANs

■ The candidate trunk member ports have different DSCP priority mappings

■ RIP, OSPF or PIM-SM is enabled on the VLAN interfaces associated with the trunk

■ The trunk is a statically configured multicast router port

Table 34 ICM3/3G - Mirror Port Table

Field DescriptionMirror Port One external port only. Internal FE ports can not be used as mirror

ports. If neither mirrored receive ports nor mirrored transmit ports are specified, the mirror port can only be used to mirror traffic classified by ACLs.

Value range: None / FE1 ~ FE4 / GE1 ~ GE2

Default: None

Mirrored Receive Port One internal port or external port/trunk except for the mirror port

Value range: None / Internal 1~ Internal 16 / FE1 ~ FE4 / GE1 ~ GE2

Default: None

Mirrored Transmit Port One internal port or external port/trunk except for the mirror port

Value range: None / Internal 1~ Internal 16 / FE1 ~ FE4 / GE1 ~ GE2

Default: None



When a trunk group is deleted, the trunk port is removed from IGMP snooping/proxy results. The member port is not added to any multicast group until an IGMP report is later received from the port. ICM3/3G resets the following port parameters to the default values upon trunk deletion:

■ RSTP port path cost

■ RSTP port priority

■ Multicast limit

■ DLF limit

■ DSCP priority mapping

■ In limit

■ Out limit

■ Broadcast limit

■ Other port related parameters shall remain unaffected.

Select the active ICM3/3G module from the tree view and select Trunk Group tab to open Figure 96. Click Retrieve to obtain the latest information. Refer to Table 35 for more details.

Figure 96 ICM3/3G - Trunk Group Window



Click Add in Figure 96 to create a new group. Configure the parameters and click Apply in Figure 97. Figure 98 prompts for trunk group rules. Click Ok to continue.

Figure 97 ICM3/3G - Trunk Group - Add Window

Table 35 ICM3/3G - Trunk Group Table

Field DescriptionTrunk Group ID A unique ID number of the trunk group.

Value range: Trunk 1 to 3

Trunk Group Name The name of the trunk group.

Value range: a character string, maximum of 32 characters

Port List Value range: FE1 - FE4 / GE1 - GE2



Figure 98 ICM3/3G - Trunk Group - Add - Note Window

Select a group and click Delete in Figure 96 to remove a group.

Protection Link The protection link for a single shelf configuration comprises one uplink from each ICM3/3G. The protection link for multi-shelf configuration comprises of multiple uplink/downlink pairs from ICM3/3Gs in the rack. Figure 99 illustrates the protection link for a multi-shelf configuration using single GE port for uplink/downlink.



Figure 99 ICM3/3G - Protection Link Configuration

ICM3/3G switchover occurs when one or more GE/FE ports in active ICM3/3G's protection link goes down while the standby ICM3/3G is in redundant state. The protection link status is propagated to the peer ICM3/3G and adjacent ICM3/3G in the protection link.

When one or more GE/FE ports in standby ICM3/3G's protection link goes down, the ICM3/3G is put into protection link down prohibited state. The protection link status is propagated to the peer ICM3/3G and adjacent ICM3/3G in the protection link. This prohibits switchover from active link when the standby link is down.

Once the fault is cleared, the protection link of the module is turned ON and the information is propagated to the rest of the links. As the result, the rest of protection links will come up for this propagation.

ICM3

(B)

ICM3

(A)

ICM3

(B)

ICM3

(A)

ICM3

(B)

ICM3

(A)

ICM3

(B)

ICM3

(A)

GE link

GE link

GE link GE link

GE link GE link

GE link GE link

Shelf 1

Shelf 2

Shelf 3

Shelf 4

ISM

(B)

ISM

(A)



Select the active ICM3/3G module from the tree view and select Protection Link tab to open Figure 100. Click Retrieve to obtain the latest information.

Figure 100 ICM3/3G - Protection Link

Configure the parameters and click Apply to bring the modification into effect. An uplink port is required and a downlink port is optional.

Note: When a GE/FE port or trunk group has been configured as protection link, the system prohibits reconfiguration until it is removed from the protection link.

Redundancy Support When two ICM3/3G modules are presented in the system, each assumes a different protection mode: one as active and one as standby. The active ICM3/3G is responsible for system management. The standby ICM3/3G is

Table 36 ICM3/3G - Protection Link Table

Field DescriptionUplink Port of Protection Link Required for both single shelf system or multi-shelf system

Value range: FE1 ~ FE4 / GE1 ~ GE2 / Trunk1 ~ Trunk3

Downlink Port of Protection Link Required for multi-shelf system

Optional for single shelf system

Value range: None / FE1 ~ FE4 / GE1 ~ GE2 / Trunk1 ~ Trunk3



synchronized with the active ICM3/3G and automatically takes over the management functionality when the active module fails.

The first ICM3/3G plugged into the shelf becomes the active ICM3/3G; the second one becomes the standby ICM3/3G. If both ICM3/3Gs come up together, the ICM3/3G in slot A becomes active while the ICM3/3G in slot B becomes standby.

The active ICM3/3G uses the IP address of its management port for the management of IP DSLAM system. The standby ICM3/3G does not have IP address on its management port. The active ICM3/3G and standby ICM3/3G communicate to each other via HDLC link (2Mbps). The default IP address used on HDLC interface is 192.168.200.1 and 192.168.200.2. Both IP address are configurable.

IP DSLAM allows user to configure the standby ICM3/3G operation including:

■ Support redundancy

■ Prohibit redundancy (default)

The standby ICM3/3G supports the following states:

■ Initializing

■ Redundant

■ Prohibited

The ICM3/3G states can be mapped to the administrative states, operational states, and standby status defined in ITU-T X.731 as follows:

Initialization state refers to the time period when standby ICM3/3G first power up to the point when it is fully synchronized with active ICM3/3G. After initialization state, the following conditions are applied to the standby ICM3/3G:

■ Containing the same flash files as the active ICM3/3G flash

■ The running image is the same as the image on flash (in another words, standby ICM3/3G runs the image that is on active ICM3/3G flash).

■ Synchronizing with the active ICM3/3G on running system information.

■ If standby ICM3/3G is in initialization state, the active ICM3/3G rejects the following:

Initializing Prohibited Redundant ActiveAdmin (RW) Unlocked Locked Unlocked Unlocked

Operational (R) Disabled Disabled Enabled Enabled

Standby (R) N/A N/A Hot standby Providing service



■ Any configuration change on the active ICM3/3G

■ Any configuration change on the standby ICM3/3G

■ Any configuration change on the line modules

■ Reset module

■ Download file to active ICM3/3G

Note: On the ICM3/3G modules, retain only the files required for the modules existed in the node. Keeping unnecessary files will consume the flash memory, which may hinder the synchronization between the active and standby ICM3/3G.

Note: When replacing ICM3/3G module, ensure the flash memory of the replacement ICM3/3G is empty.

After the standby ICM3/3G powers up, the active ICM3/3G verifies whether the standby ICM3/3G contains the same ICM3/3G image file as the one on its own flash image files. If a mismatch is detected, the active ICM3/3G downloads its version to the standby ICM3/3G and resets the standby ICM3/3G.

If the standby ICM3/3G runs a higher version (this typically occurs in upgrade scenarios), an equipment alarm is raised. The standby ICM3/3G is changed to redundant state if allowed, which is configurable. This alarm is cleared after ICM3/3G switches over or the standby ICM3/3G is removed.

If the standby ICM3/3G runs a lower version (this is an error condition), an equipment alarm is also raised. The standby ICM3/3G remains in initializing state and cannot be configured. This alarm is cleared after the standby ICM3/3G is removed

In initializing and prohibited states, the standby ICM3/3G administratively locks the Ethernet ports Internal1~16, GE1~7 or FE1~4 and GE1~2. The port link status remains down. In redundant state, the standby ICM3/3G administratively unlocks the Ethernet ports Internal1~16, and sets the administrative status of GE1~7 or FE1~4 and GE1~2 per user's last configuration.

The behavior of standby ICM3/3G operation during each state is as shown below:

Initialization Prohibit RedundancySwitchover Not allowed Not allowed Allowed

Allow configuration change No Yes Yes

E1-E4, G1-G2 status Locked, appear down Locked, appear down Per user configuration

Layer two switch process packet No No No



The parameters that are synchronized in the standby ICM3/3G during runtime are shown below:

If standby ICM3/3G cannot support switchover (in initialization or prohibit state), resetting active ICM3/3G is rejected and CLI/Netman 4000 display "Standby ICM3/3G is operationally disabled, switchover can not be performed".

Select the active ICM3/3G module from the tree view and select Redundancy Support tab to open Figure 101. Click Retrieve to obtain the latest information. Configure the parameters and click Apply to bring the modification into effect

Parameters Real time synchronization of standby ICM3/3GISM configuration No, ISM configuration is sent to ISM. ICM3/3G does not maintain ISM configuration

ASM configuration No, ASM configuration is sent to ISM. ICM3/3G does not maintain ASM configuration

ICM3/3G configuration Yes

All other configuration Yes

File download to ICM3/3G Yes

Save configuration Yes

Outstanding alarm for active ICM3/3G

No

All other outstanding alarm Yes

FWDB for ICM3/3G layer-two switch No. The static entries configured on active ICM3/3G are automatically copied to standby ICM3/3G and therefore shall appear on both FWDB

IGMP snooping results No. The static router port configured on active ICM3/3G are automatically copied to standby ICM3/3G and therefore shall appear on both results

DHCP assignment, statistics No

MAC black list match Yes

CLI access history No

ICM3/3G switch port statistics No

SNMP access statistics Yes

ICM3/3G STP statistics No

ICM3/3G ARP table No

RADIUS transaction, statistics No



Figure 101 ICM3/3G - Redundancy Support Window

Redundancy Setup via CLIIn the initial system startup, ICM3/3G redundancy is disabled by default. The procedure below describes the set up of redundancy in the IP DSLAM system.

■ System startup

■ Issue CLI command redundancy to the active ICM3/3G on every shelf

■ Issue CLI command protection-link G1 G2 to the active ICM3/3G on every shelf except the last shelf

■ Adding a Node to the last shelf

■ Install the shelf as the last shelf of the rack

■ Connect GE links between the G1 port of ICMs of the last shelf and the G2 port of ICM3/3G of the previous shelf. The ICM3/3G connections should be slot A to slot A and slot B to slot B.

■ Issue CLI command redundancy to the active ICM3/3G of the last shelf

■ Issue CLI command protection-link G1 G2 to the active ICM3/3G of the previous shelf

■ Issue CLI command protection-link G1 to the active ICM3/3G of the last shelf.



■ If the active/standby ICM3/3G of the last shelf do not match the active/standby ICMs on the previous shelf, issue CLI command switchover to the active ICM of the last shelf

■ Removing a Node from the last shelf

■ Issue CLI command protection-link G1 to the active ICM3/3G of the previous shelf

■ Remove GE links between the last shelf and the previous shelf

■ Remove the last shelf from the rack

Switchover Two types of switchover are be supported. Switchover is nonreversible.

■ Manual switchover - Operator manually switches over ICM3/3G. he manual switchover does not cause reset on existing ICM3/3G. It can not be preformed when standby ICM is in initialization or prohibited state.

■ Automatic switchover - Initiated by ICM (active or standby). Automatic switchover is triggered when active ICM is reset or in major fault. The major fault conditions are those that will prevent system from switching user traffic, such as watchdog reset, and uplink failure.

Select the active ICM3/3G module from the tree view and select Switchover tab to open Figure 102. Click Switch between active and standby ICM3/3G box and click Apply to start switching the ICM3/3G modules.



Figure 102 ICM3/3G - Switchover Widow

If standby ICM3/3G cannot support switchover (in initialization or prohibit state), resetting active ICM3/3G is rejected and CLI/Netman 4000 display "Standby ICM3/3G is operationally disabled, switchover can not be performed".

Note: Prior to switch to an ICM3/3G module or replace the old ICM3/3G module with a new ICM3/3G module, confirm the following:

■ The new ICM3/3G module contains the same configuration as the old ICM3/3G module.

Or■ Insert the new ICM3/3G module without any configuration and download a

copy of the previously saved configuration of the old ICM3/3G module.

VBAS For the ADSL line identification purpose, a VBAS session between IPDSLAM and BAS is introduced during the PPP Authentication. After received PPP authentication request from subscriber, the BAS will send one VBAS request to IP DSLAM for the subscriber's information of shelf ID (Which may have been identified through the tagged VLAN ID to BAS.), slot ID and ADSL physical port ID. The IPDSLAM will respond the request with a VBAS response message to report the ADSL line identification information.



The IPDSLAM maintains a VBAS Client MAC Address in the database. This address is the DSLAM MAC address and it is statically configured at BAS for BAS to determine where the VBAS message shall be forwarded to. Each IPDSLAM has a unique VBAS client MAC address.

Upon receiving a VBAS request message, the system check the destination MAC address at MAC layer. If the MAC address is same as "VBAS Client MAC Address" of the IPDSLAM, perform the normal identification operation. Otherwise, it is discarded by VBAS task.

The IPDSLAM supports at least multiple concurrent active VBAS sessions. One active VBAS session means the IPDSLAM received a VBAS request message but does not respond yet. The VBAS Session ID is the label of each active session. Each active VBAS session has a maximum life-cycle of maximum response interval.

■ If the number of active VBAS sessions reaches the maximum session allowed, discard the further VBAS request message until a VBAS session is available again, i.e. one active VBAS session has ended with the VBAS respond message sent

■ If received VBAS request message with a VBAS Session ID falls into the range of active VBAS sessions, discard this VBAS request message

■ When the life-cycle of one active VBAS session reaches the maximum response interval, (a.k.a. active VBAS session expires), destroy this session and respond a VBAS response message with Operation Result Code;

■ For an active VBAS session, sending a VBAS responding message is the last process for the IPDSLAM to end this active VBAS session.

Select the active ICM3/3G module from the tree view and select VBAS tab to open Figure 102. Modify the parameter and click Apply. Click Retrieve to obtain the latest information. Click Reset Statistics to reset the counters. Refer to Table 37 for more details.



Figure 103 ICM3/3G - VBAS Widow

External Ethernet Port This function allows the user to lock or unlock FE and GE ports for the standby ICM3/3G module.

Select the standby ICM3/3G module from the tree view and select External Ethernet Port tab to open Figure 104. Click Retrieve to obtain the latest information. Select a port and click Lock to lock the selected port. Select a port and click Unlock to unlock the selected port.

Table 37 ICM3/3G - VBAS Table

Field Description

GeneralAdministrative State Value range: Enabled / Disabled

Client MAC Address DSLAM MAC address. Each IPDSLAM has unique VBAS client MAC address

Number of Active Sessions The number of current active VBAS sessions

StatisticsNumber of Requests Received Number of Received VBAS Request Messages

Number of Error Requests Number of Received Error VBAS Request Messages

Number of Discarded Requests Number of Discarded VBAS Request Messages

Number of Responses Sent Number of Transmitted VBAS Response Messages



Figure 104 Standby ICM3/3G - External Ethernet Port Window

Port Level Configuration

Active ICM3/3G module supports the following configuration at the port level:

■ Ethernet Port Configuration

■ RSTP

■ VLAN

■ Multicast

■ IGMP Snooping

■ IGMP Proxy

■ PIM-SM (Master shelf ICM3 only)

■ Routing (Master shelf ICM3 only)

■ RIP

■ OSPF

■ ARP

■ DHCP (Master shelf ICM3/3G only)

■ Packet Classification (Master shelf ICM3/3G only)

■ QoS


Port Level Configuration 149

Ethernet PortConfiguration

■ Maximum Ethernet Frame Length

ICM3/3G module supports Ethernet frame length from 64 bytes to 1522 bytes (1518 bytes + 4-byte VLAN tag). Frames outside this range are classified as part of oversized frame.

■ Framing Filtering

Frames with any kind of error are filtered. Error types include CRC, alignment, false carrier sense, short event, runt event, long event and jabber.

■ Jabber Lookup Protection

A port is considered to be jabbering if it active for more than 50,000 bit periods continuously. A jabbering port is automatically partitioned from the system to prevent it from impairing system performance.

■ Auto Negotiation

ICM3/3G module supports auto-negotiation for all 10/100Mbps ports as well as 100/1000Mbps ports with copper PHYs to adjust the mode of operation (half/full duplex and speed (10/100/1000 Mbps) according to the device at the other end of link. A manual mode of operation is also provided to enable the user to configure the operation mode, speed and flow-control.Gigabit ports always operate in full-duplex mode while the 10/100Mbps ports can operate in half-duplex or full-duplex mode.Auto-negotiation is not supported on 100/1000Mbps ports when optical PHYs are provided. Ports always operate as gigabit ports in this case.

■ Flow Control

ICM3/3G module supports a flow control mechanism for each port that can be enabled or disabled by the user. Flow control activity is triggered when the buffer utilization exceeds the pre-defined thresholds of the dedicated port buffer and shared buffer. Pause frame based flow-control is used for full-duplex operation while backpressure based flow control is used for half-duplex operation.

■ Head of Line Blocking Protection

Head of line blocking can be prevented by providing a limit on the maximum number of frames allowed in the queue. Frames at the queue input (i.e., queue tail) are dropped once this limit is reached.

■ Framing Forward

■ Unicast Frames

The Address Resolution Logic (ARL), on receiving a destination address, determines the destination port number to identify the port the frames should be forwarded to. If the ARL cannot find identify the Destination Address (DA), the frame is treated as a frame with unknown DA. One of the following mechanisms can be used to handle the frames with unknown DA.

When DLF frame discard is set to ON, the MAC frame with unknown unicast destination address will be discarded. When DLF frame forward is



enabled, the MAC frame with unknown unicast destination address will be sent to all ports in the same VLAN, except the source port.

■ Broadcast Frames

Broadcast frames are forwarded to all ports within the same VLAN except the source port itself.

■ Multicast Frames

Multicast frames are forwarded to all members of the same multicast group within the specified VLAN if VLAN tagged. The untagged multicast frames are tagged with receiving port (FE or GE) PVID or default VLAN ID (if no PVID is defined for the Rx port) and then get forwarded to all the member ports of the same multicast group, which also are members of Rx Port VLAN.

■ Broadcast Speed Limit

ICM3/3G module supports a throttling mechanism to prevent broadcast storms. The throttling mechanism, when enabled, drops incoming frames if they exceed the configured threshold. The threshold can be configured independently for each port at 6% or 20% of port rate.

■ Rate Limiting

ICM3/3G module provides control of ingress as well egress data rate on each port. Rate control can be enabled or disabled independently for each port. Transmit and receive rate can be controlled independently for each port. If no rate control is enabled, full 10/100Mbps rate is permitted. Eight levels of rate configuration are provided for each 10/100Mbps port as shown in the table below.

If the receiving traffic is faster than the configured rate, the behavior for excess traffic is defined by the flow control mechanism defined for that port (back pressure in half duplex and pause frame in full duplex mode). In case no flow control mechanism has been defined for a port, the excess frames are dropped.

If the transmit traffic is faster than the configured rate, transmission is suspended so that the average transmit traffic is within the defined rate.

Ethernet port configuration supports the following options:

■ Internal Ethernet Ports

■ External Ethernet Ports

■ Trunk Ports

Internal Ethernet PortsExpand the active ICM3/3G module from the tree view and select Ethernet Port Configuration to open the internal Ethernet ports summary shown in Figure 105. Click Retrieve to obtain the latest information.



Figure 105 ICM3/3G - Ethernet Port Configuration - Internal Ethernet Ports Window

Select a port in Figure 105 and click Modify to modify the port. Configure the parameters in Figure 106 and click Apply to bring the modification into effect. Refer to Table 38 for more details.



Figure 106 ICM3/3G - Ethernet Port Configuration - Internal Ethernet Ports - Modify Window

External Ethernet PortsExpand the active ICM3/3G module from the tree view and select Ethernet Port Configuration. Click External Ethernet Ports tab to view the external Ethernet ports summary shown in Figure 107. Click Retrieve to obtain the latest information.

Table 38 ICM3/3G - Ethernet Port Configuration - Internal Ethernet Ports Table

Parameter DescriptionPort ID Value range: Internal1 - 16

Orientation Network, Subscriber

Incoming Speed Limit Value range: Enabled / Disabled

Outgoing Speed Limit Value range: Enabled / Disabled

Broadcast Rate Threshold (pps) Value range: 0 - 262143

Default: 0, Disabled

Multicast Rate Threshold (pps) Value range: 0 - 262143


DLF Rate Control Threshold (pps) Value range: 0 - 262143




Figure 107 ICM3/3G - Ethernet Port Configuration - External Ethernet Ports Window


No modification is allowed on trunks ports. Disassociate with trunk port before attempting to modify the parameters.



Figure 108 ICM3/3G - Ethernet Port Configuration - External Ethernet Ports - Modify Window

Table 39 ICM3/3G - Ethernet Port Configuration - External Ethernet Ports Table

Parameter DescriptionPort ID Value range: FE1-FE4 or GF1-GE2

Administrative State Value range: Locked / Unlocked

Default: Unlocked

Orientation Value range: Network / Subscriber

Default: Network

Read-only if the port is a member of a trunk group.

Speed / Duplex Value range: Auto, 10Mbps/Full, 100Mbps/Full, 10Mbps/Half, 100Mbps/Half

Default: Auto

Configurable for FE ports only.

Read-only if the port is a member of a trunk group.



Trunk PortsExpand the active ICM3/3G module from the tree view and select Ethernet Port Configuration. Click Trunk Ports tab to view the trunk ports summary shown in Figure 109. Click Retrieve to obtain the latest information.

Flow Control Value range: On / Off

Default: On

Incoming Speed Limit Value range:

■ Disabled / 64kbps to 100Mbps in 64kbps granularity for FE ports

■ Disabled / 64kbps to 1Gbps in 64kbps granularity for GE ports

Default: Disabled

Outgoing Speed Limit Value range:



Default: Disabled

Broadcast Rate Threshold

Value range: 0 - 262143 pps

Default: Disabled

Multicast Rate Threshold Value range: 0 - 262143 pps

Default: Disabled

DLF Rate Control Threshold

Value range: 0 - 262143 pps

Default: Disabled

Table 39 ICM3/3G - Ethernet Port Configuration - External Ethernet Ports Table

Parameter Description



Figure 109 ICM3/3G - Ethernet Port Configuration - Trunk Ports Window




Figure 110 ICM3/3G - Ethernet Port Configuration - Trunk Ports - Modify Window

Table 40 ICM3/3G - Ethernet Port Configuration - Trunk Ports Table

Parameter DescriptionPort ID Value range: Trunk 1 - 3

Administrative State Value range: Locked / Unlocked

Default: Unlocked

Orientation Value range: Network / Subscriber

Default: Network

Speed / Duplex Value range: Auto, or the sum of the member ports' configured speed

Default: Auto

Read-only

Flow Control Value range: On / Off

Default: On

Read-only



RSTP The ICM3/3G module supports Spanning Tree Algorithm (SPA) on all bridge ports.

Abbreviated STP, a link management protocol part of the IEEE 802.1 standard for media access control bridges. Using the spanning tree algorithm, STP provides path redundancy while preventing undesirable loops in a network that are created by multiple active paths between stations. Loops occur when there are alternate routes between hosts. To establish path redundancy, STP creates a tree that spans all of the switches in an extended network, forcing redundant paths into a standby, or blocked, state. STP allows only one active path at a time between any two network devices (this prevents the loops) but establishes the redundant links as a backup if the initial link should fail. If STP costs change, or if one network segment in the STP becomes unreachable, the spanning tree algorithm reconfigures the spanning tree topology and reestablishes the link by activating the standby path. Without spanning tree in place, it is possible that both connections may be simultaneously live, which could result in an endless loop of traffic on the LAN.

Spanning-Tree Protocol operation is transparent to end stations, which are unaware whether they are connected to a single LAN segment or a switched LAN of multiple segments.

RSTPExpand the active ICM3/3G module from the tree view and select RSTP to open Figure 111. Click Retrieve to obtain the latest information. Modify the parameters in Figure 111 and click Apply to bring the modification into effect. Refer to Table 41 for more details.

Incoming Speed Limit Value range:



Default: Disabled

Outgoing Speed Limit Value range:



Default: Disabled

Broadcast Rate Threshold (pps)



Multicast Rate Threshold (pps)



DLF Rate Control Threshold (pps)



Table 40 ICM3/3G - Ethernet Port Configuration - Trunk Ports Table




Figure 111 ICM3/3G - RSTP - RSTP Window

Table 41 ICM3/3G - RSTP - RSTP Table

Field Name Description Spanning Tree Algorithm

Enable / disable SPA


Priority The configurable portion of the Bridge ID. The bridge with the lowest bridge ID will be selected as the root.


Default: 32768

Bridge Hello Time The interval of time between the transmissions of BPDU frames by a Bridge that is attempting to become the Root or is the Root. The parameter is the interval of time between the transmissions of Topology Changes Notifications BPDUs towards the Root when a topology change has occurred.

Value range: 1 to 10 s

Default: 2 s

Time since topo changed

The interval of time since the last change in the topology of the network (basically a link going down or going to forwarding), was detected by a bridge and the event was advertised to the whole bridged network by the root bridge

Format: Hours:Minutes:Seconds:

Read Only



RSTP PortAt the STP Port, the user is allowed to configure STP port priority and path cost.

Expand the active ICM3/3G module from the tree view and select RSTP. Select the RSTP Port tab to open Figure 112. Click Retrieve to obtain the latest information. Modify the parameters in Figure 112 and click Apply to bring the modification into effect. Refer to Table 42 for more details.

Designated Root The unique identifier of the bridge in the network designated or assumed to be the root.

Read Only

Root Port The port closest to the root bridge. The port that provides the least cost from the link to the root is elected as the designated root port. It is not significant when the Bridge is the Root, and is set to zero

Read Only

Hello Time The current setting of the interval of time between the transmissions of BPDU frames by a Bridge that is attempting to become the Root or is the Root. The current interval of time the between the transmissions of Topology Changes Notifications BPDUs towards the Root when a topology change has occurred.

Read Only

Bridge Address The Bridge to which the Port belongs, in the case of a Designated Port; or other wise, The bridge believed to be the Designated Bridge for the LAN to which this port is attached.

Read Only

Bridge Max Age The maximum time a BPDU received on a port is considered valid before it is discarded.

Value range: 6 - 40 s

Bridge Forward Delay The interval of time a port will be in the Listening and the Learning State before moving to the Learning or Forwarding State, respectively.

Value range: 4 - 30 s

Number of changes The number of detected topology changes since the last reset of line card.

Read Only

Root Cost The cumulative cost of all the links to the root bridge. When the bridge is the root the value will be zero

Read Only

Max Age The current setting of the maximum a time a BPDU received on a port is considered valid before it is discarded.

Read Only

Forward Delay The current setting of the interval of time a port will be in the Listening and the Learning State before moving to the Learning or Forwarding State, respectively

Read Only

Table 41 ICM3/3G - RSTP - RSTP Table

Field Name Description



Figure 112 ICM3/3G - RSTP - RSTP Port Window

Table 42 ICM3/3G - RSTP - RSTP Port Table

Field Name Description Port ID The Port identifier that identifies the port uniquely among the Ports on the

Bridge. This parameter is used as the value for Port identifier parameter of all configuration messages transmitted through the Port.

Value range: WAN, 1 to 24 with VPI:VCI

Path Cost The contribution of the path through this Port, when the Port is the Root Port, to the total cost of the path to the Root for this Bridge.

Value range: 1 to 200000000

Designated Root The unique identifier of the bridge in the network designated or assumed to be the root for the LAN to which the port is attached.

Read Only

Designated Bridge The Bridge to which the Port belongs, in the case of a Designated Port; or other wise, The bridge believed to be the Designated Bridge for the LAN to which this port is attached.

Read Only

Priority The configurable portion of the Port ID. Determines between two equal cost ports, which one will be selected to be in forwarding mode, putting the other port in blocking.The port with the lowest priority will be selected.

Value range: 0 to 240

Default: 128



VLAN VLAN can be defined as a collection of switch ports within a network, grouped together to enable broadcast traffic reduction as well as provide security.

ICM3/3G supports 4092 bridged VLANs and 32 routed VLANs. Both port-based and tag-based VLAN mechanisms are supported in compliance with IEEE 802.1Q.

■ Port Based VLAN

Port-based VLAN is typically used to reduce broadcast traffic and increase security. A group of network users assigned to a VLAN forms a broadcast domain that is separate from other VLANs configured on the ICM3/3G. The frames are forwarded between ports that are members of the same VLAN. The VLAN membership can be defined based on ports, e.g., ports 1, 3, 5, and 7 can be one VLAN and port 2, 4, 6, and 8 could be another.

■ Untagged Frames

If an untagged ingress frame is received on a port, it is assigned a VLAN ID as that of the port PVID. The frame is then forwarded to the destination port, if the VLAN membership criterion is met. The frame will exit the L2 switch tagged/untagged based on the egress rules defined for the destination port. (Egress Packet Untag setting).VLAN ID = PVID for untagged frames

■ Tagged Frames

If an ingress frame is received with an 802.1q (known) tag, it is forwarded based on tag and Ingress rules.

■ Unknown VLAN Tag

The ingress frame with unknown VLAN tag can be processed as:■ Forwarded - flooding to all the ports

■ Discarded

STP State Displays the current status of the port. The values of the parameters is controlled by the protocol.

Value range: Disable Listening Forwarding / Blocking

Read Only

Designated Cost For the Designated Port, the path cost (equal to the Root Path Cost of the Bridge) offered to the LAN to which the port is attached; otherwise, The cost of the path to the Root offered by the Designated Port on the LAN to which this port is attached.

Read Only

Designated Port The Port Identifier of the Bridge port, on the Designated Bridge, through which the Designated Bridge transmits the configuration messages stored by this Port

Read Only

Table 42 ICM3/3G - RSTP - RSTP Port Table




■ Forwarded to GE

■ Ingress Checking

When enabled, the source port ID is compared with the VLAN port membership. If the source port belongs to the same VLAN, the frame is forwarded to the destination port otherwise it is dropped.

■ Frame Forwarding Flow Chart

The following two diagrams depict the flow chart for frame forwarding. It is possible to define default VLAN in the ICM. This flow chart applies to all unicast and multicast traffic flows.

Figure 113 ICM3/3G - VLAN Frame Forwarding with VLAN - Part 1

Incoming Framefrom port

Is frame tagged(802.1q)

No

Does port haveport VLAN ID

(PVID)No

Tag the frame(802.1q) with

Default VLAN ID(entry[0])

Tag the frame(802.1q) with

PVID

Yes

Yes

B



Figure 114 ICM3/3G - VLAN Frame Forwarding with VLAN - Part 2

ICM3/3G module supports the following VLAN configuration:

■ General (Master shelf ICM3/3G only)

■ VLAN Setup

■ Routed VLAN Interface

Lookup 802.1qtag in VLAN

tableFound Not Found

'Forward to all'option enabled

Yes

(Use unknown VLANtag rule)

Send the frame toall the ports

Get index and portmembership No

Use source portmembership

entry [0] (defaultVLAN)

Ingress/EgressCheck PassYes

No

Follow portmembershipto forward

Drop theframe

B

Is untaggingenabled on thedestination port

Yes

Untag theframe

No

Frameforwarded

Membersfound

No

'Drop' Option enabled

Yes'Forward to trunk

ports'option enabled



GeneralThis feature is applicable for single shelf ICM3/3G module or master shelf ICM3/3G module only.

ICM3/3G supports double VLAN tagging (Q-in-Q) based transparent LAN service on a per module basis. When enabled, all existing layer 2 (except bridged in-band management VLAN-s), layer 3 and ACL configurations are purged. Other configurations, including management VLANs, are not affected. Similarly, when disabled, all existing layer 2 (except bridged in-band management VLAN-s) and ACL related configurations are purged.

ICM3/3G allows TPID configuration for service provider VLANs. If the TPID received on a network oriented interfaces does not match the configured TPID of the service provider VLANs, the Ethernet packet is considered without a service provider tag and is silently discarded.

Subscriber isolation is supported on a per module basis. Subscriber isolation prevents switching between two subscriber interfaces. When enabled, frames received from a subscriber port that are destined for other subscriber port(s) are silently discarded.

Expand the active ICM3/3G module from the tree view and select VLAN to open Figure 116. Click Retrieve to obtain the latest information. Configure the parameters and click Apply to take modification into effect. Refer to Table 43 for more details.

Figure 115 ICM3G - VLAN - General Window



Figure 116 ICM3 - VLAN - General Window

After entered double tagging mode, the ICM3/3G sub tree in the left panel is restructured. The following configuration options are removed:

■ Layer 3 related configuration (i.e. VLAN Interface, RIP, OSPF, ARP etc.)

Table 43 ICM3/3G - VLAN - General Table

Field DescriptionQ-in-Q Setup

Double Tagging Enable/disable VLAN tagging (Q-in-Q) based transparent LAN service. The ICM3/3G module is reset when tagging mode is changed.

Value range: Enabled/Disabled

Default: Disabled

TPID TPID for the service provider VLAN.

Value range: 16-bit hexadecimal

Default: 8100

Subscriber Isolation Setup

Subscriber Isolation To enable/disable silently discarding frames received from a subscriber port that are destined for other subscriber port(s).

Value range: Enabled/Disabled

Default: Disabled



■ Multicasting configuration (IGMP and PIM-SM)

■ DHCP

VLAN SetupEach VLAN interface can be associated with multiple Ethernet interfaces.

Traffic between different Ethernet interfaces of the same VLAN interface is locally switched and is bypassing the router. Therefore, network oriented and subscriber oriented Ethernet interfaces can not be associated to the same VLAN interface.

Expand the active ICM3/3G module from the tree view and select VLAN. Click VLAN Setup to open Figure 118. Click Retrieve to obtain the latest information. Refer to Table 44 for more details.

Figure 117 ICM3G - VLAN - VLAN Setup Window



Figure 118 ICM3 - VLAN - VLAN Setup Window

Table 44 ICM3/3G - VLAN - VLAN Setup Table

Parameter DescriptionUnknown VLAN Value range: Discard / Forward

Ingress Check When enabled, the source port ID is compared with the VLAN port membership. If the source port belongs to the same VLAN, the frame is forwarded to the destination port otherwise it is dropped.

Value range: Enabled / Disabled

Default: Enabled

VLAN ID Value Range: 2-4092

VLAN Name A character string with maximum of 20 characters

Mode Value Range:

■ Single tagging mode: Full Bridging / Limited Bridging / Routing

■ Double tagging mode: Full Bridging / Limited Bridging

Default: Full Bridging

Up to 8 VLANs can have limited bridging mode. Up to 32 VLANs can be set to routing mode

Orientation This is only applicable to a routed VLAN. The orientation is inherited from the first associated interface. The orientation is unknown when no interface is associated with the routed VLAN. Default VLAN is always subscriber oriented.

Value range: Network / Subscriber / Unknown (for routed VLANs) / None (for bridged VLANs)

Default:

■ Unknown for routed VLANs

■ None for bridged VLANs.

Read-only



Click Add or select an entry and click Modify in Figure 118. Configure the parameters and click Apply in Figure 119.

Note: When double tagging mode is enabled, the Add and Modify option has the following changes:

■ All network oriented bridge ports act as Tagged Ports for Service Provider VLAN

■ All subscriber oriented bridge ports act as Untagged Ports for Service Provider VLAN

■ Routing mode is not available (only Full & Limited Bridging will be available)

802.1 Priority The actual IEEE 802.1 priority for double tagging. Not applicable for single tagging mode.

Tagged Port List of tagged ports for this VLAN

Untagged Port List of untagged ports for this VLAN

Table 44 ICM3/3G - VLAN - VLAN Setup Table




Figure 119 ICM3/3G - VLAN - VLAN Setup - Add Window

A VLAN can not be deleted if it is associated with any ports. Use Modify to remove all tagged and untagged ports. Select an entry and click Delete in Figure 118 to remove the entry.

Routed VLAN InterfaceA Routed VLAN interface in consisted of the VLAN/IP address combination.

Expand the active ICM3/3G module from the tree view and select VLAN. Select the Routed VLAN Interface/ VLAN Interface tab to open Figure 121. Click Retrieve to obtain the latest information.



Figure 120 ICM3G - VLAN - VLAN Interface Window



Figure 121 ICM3 - VLAN - Routed VLAN Interface Window

Click Add or select an entry and click Modify in Figure 121. Configure the parameters and click Apply in Figure 122. Refer to Table 45 for more details.

Figure 122 ICM3/3G - VLAN - VLAN Interface - Add Window



Select an entry and click Delete in Figure 121 to remove an entry.

In-band ManagementVLAN can be added/removed to In-band management access list through command line interface (CLI), or through Device manager for ICM3 module, but for ICM3G only through command line interface (CLI).

Follow the procedures below to configure in-band management:

■ Create a VLAN (through device manager or CLI).

■ Use the following CLI command to add the VLAN to in-band management access list (through CLI only):

AN2000_IB#access in-band vid <2-4092> address <A.B.C.D> netmask <A.B.C.D>

AN2000_IB#access in-band vid <2-4092> mode <master|slave1|slave2>

■ Modify tagged port or untagged port for the in-band management VLAN (through device manager or CLI)

■ Remove all the tagged and untagged ports before remove the selected VLAN (through device manager or CLI).

■ Use the following command to remove VLAN from in-band management access list (through CLI only):

AN2000_IB#access no in-band vid <all|2-4092>

Table 45 ICM3/3G - VLAN - VLAN Interface - Add Table

Parameter DescriptionVLAN ID Value Range: 2-4092

Orientation This is only applicable to a routed VLAN. The orientation is inherited from the first associated interface. The orientation is unknown when no interface is associated with the routed VLAN. Default VLAN is always subscriber oriented.

Value range: Network / Subscriber / Unknown (for routed VLANs) / None (for bridged VLANs)

Default:

■ Unknown for routed VLANs

■ None for bridged VLANs.

Read-only

Sub-Interface ID Sub-interface 1 is the primary interface

Read-only

IP Address Valid range: valid IP address

Subnet Mask Valid range: valid subnet mask



Note: Refer to iAN8K B1000 CLI User Manual UTSI-NJTC-20050624 for more details on CLI configuration.

Expand the active ICM3 module from the tree view and select VLAN. Select the Inband VLAN Interfaces tab to open Figure 123. Click Retrieve to obtain the latest information.

Figure 123 ICM3 - VLAN - Inband VLAN Interfaces Window



Click Add or select an entry and click Modify in Figure 123. Configure the parameters and click Apply in Figure 124. Refer to Table 45 for more details.

Figure 124 ICM3 - VLAN - Inband VLAN Interfaces - Add VLAN Interface Window

Select an entry and click Delete in Figure 123 to remove an entry.

Multicast The IP DSLAM can be configured as a layer 2 or layer 3 device. Running the IP DSLAM at layer 2 with IGMP Snooping is the most straightforward configuration for video delivery. IGMP Snooping allows the IP DSLAM to track active video channels and only forward video streams to the viewing subscribers and therefore reduces unnecessary flooding of IP multicast traffic.

When layer 3 routing, the DSL subscribers are no longer directly connected to the upstream multicast router at the network layer. This presents a problem for IGMP since IGMP only works with multicast routers and hosts in the same broadcast domain. To overcome this problem, IGMP Proxy can be used the route the two multicast domain together while providing the same benefits of IGMP Snooping.

Table 46 ICM3 - VLAN -Inband VLAN Interface - Add Table

Parameter DescriptionVLAN ID Value Range: 2-4092

Sub-Interface ID Sub-interface 1 is the primary interface

Read-only

IP Address Valid range: valid IP address

Subnet Mask Valid range: valid subnet mask



In some networks, the video source is located several network hops away from the IP DSLAM. In such cases, PIM-SM can be used to propagate IGMP Joins to the RP multicast router and route multicast video streams towards the video subscriber in a bandwidth efficient manner.

IP DSLAM also supports IGMP Report Aggregation to minimize the number of unnecessary IGMP multicast sent to the upstream router.

Expand the active ICM3/3G module from the tree view and select Multicast to open Figure 126. Click Retrieve to obtain the latest information.

Figure 125 ICM3G- Multicast Window



Figure 126 ICM3 - Multicast Window

Modify the parameters and click Apply in Figure 126 to bring the modification into effect.

ICM3/3G module supports the following configuration for multicast

■ IGMP Snooping

■ General

■ Group Membership

■ IGMP Proxy

■ General


■ PIM-SM (Master shelf ICM3 only)

■ General

■ RP Router

■ Multicast Routing Table

■ Neighbor Details

■ Interface Setup



IGMP Snooping■ General


General Expand the active ICM3/3G module from the tree view and expand Multicast. Select IGMP Snooping to open Figure 127. Click Retrieve to obtain the latest information. Configure the parameters and click Apply to bring the modification into effect. Refer to Table 47 for more details.

Figure 127 ICM3 - Multicast - IGMP Snooping - General Window

Table 47 ICM3/3G - Multicast - IGMP Snooping - General Table

Field Name Description IGMP Snooping Read-only.

Unknown Group Value range: Forward / Discard

No-response-leave query count Value range: 1-3



Group Membership Expand the active ICM3/3G module from the tree view and expand Multicast. Select IGMP Snooping and click Group Membership tab to open Figure 127. Click Retrieve to obtain the latest information. Refer to Table 48 for more details.

Figure 128 ICM3 - Multicast - IGMP Snooping - Group Membership Window

No-response-leave query interval Value range: 1-255

Last query count Value range: 0-3

Last query interval Value range: 1-255

Multicast Router Mode Value range: Auto / Manual

Multicast Router Interface Value range: FE1-4 / GE1-2 / Trunk1-3

Table 47 ICM3/3G - Multicast - IGMP Snooping - General Table




IGMP Proxy■ General


General Expand the active ICM3/3G module from the tree view and expand Multicast. Select IGMP Proxy to open Figure 129. Click Retrieve to obtain the latest information. Configure the parameters and click Apply to bring the modification into effect. Refer to Table 49 for more details.

Figure 129 ICM3 - Multicast - IGMP Proxy - General Window

Table 48 ICM3/3G - Multicast - IGMP Snooping - Group Membership Table

Field Name Description Group Address IP Address

VLAN ID 2-4092

Port List List of interfaces that are members of the given multicast group.



Group Membership Expand the active ICM3/3G module from the tree view and expand Multicast. Select IGMP Proxy and click Group Membership tab to open Figure 130. Click Retrieve to obtain the latest information.

Figure 130 ICM3 - Multicast - IGMP Proxy - Group Membership

Table 49 ICM3/3G - Multicast - IGMP Proxy - General Table

Field Name Description IGMP Proxy Read-only.

No-response-leave query count Value range: 1-3

No-response-leave query interval Value range: 1-255

Last query count Value range: 0-3

Last query interval Value range: 1-255

Multicast Router Mode Value range: Auto / Manual

Multicast Router Interface Value range: None



PIM-SMThis feature is applicable for single shelf ICM3 module or master shelf ICM3 module only.

ICM3 module supports the following PIM-SM configuration:

■ General

■ RP Router

■ Multicast Routing Table


■ Interface Setup

General Expand the active ICM3/3G module from the tree view and expand Multicast. Select PIM-SM to open Figure 131. Click Retrieve to obtain the latest information. Configure the parameters and click Apply to bring the modification into effect.



Figure 131 ICM3 - Multicast - PIM-SM - General Window

RP Router Expand the active ICM3/3G module from the tree view and expand Multicast. Select PIM-SM and click RP Router tab to open Figure 132. Click Retrieve to obtain the latest information.



Figure 132 ICM3 - Multicast - PIM-SM - RP Router Window

Click Add or select an entry and click Modify in Figure 132. Configure the parameters and click Apply in Figure 133 to bring the modification into effect. Only one RP router is allowed.

Figure 133 ICM3 - Multicast - PIM-SM - RP Router - Add Window



Select an entry and click Modify in Figure 132. Configure the parameter to 0.0.0.0 to disable the router.

Multicast Routing Table Expand the active ICM3/3G module from the tree view and expand Multicast. Select PIM-SM and click Multicast Routing Table tab to open Figure 134. Click Retrieve to obtain the latest information.

Figure 134 ICM3 - Multicast - PIM-SM - Multicast Routing Table Window

Neighbor Details Expand the active ICM3/3G module from the tree view and expand Multicast Select PIM-SM and click Neighbor Details tab to open Figure 135. Click Retrieve to obtain the latest information.



Figure 135 ICM3 - Multicast - PIM-SM - Neighbor Details Window

Interface Setup Expand the active ICM3/3G module from the tree view and expand Multicast Select PIM-SM and click Interface Setup tab to open Figure 136. Click Retrieve to obtain the latest information.



Figure 136 ICM3 - Multicast - PIM-SM - Interface Setup Window

Click Add or select an entry and click Modify in Figure 136. Configure the parameters and click Apply in Figure 137 to bring the modification into effect.



Figure 137 ICM3 - Multicast - PIM-SM - Interface Setup - Add Window

Select an entry in Figure 132 and click Delete to remove the entry.

Routing This feature is applicable for single shelf ICM3 module or master shelf ICM3 module only.

This section provides configuration for subscriber data route only. Please refer to Chapter 7 for more details on management data route configuration.

ICM3 module supports 8000 entries in data traffic routing table. The default route is indicated by a destination IP address of 0.0.0.0 with the subnet mask of 0.0.0.0. Only ONE default route can be set in the system to be used for both management and data traffic. This shall be kept in mind when planning and provisioning a default route in the network.

Expand the active ICM3 module from the tree view and select Routing to open Figure 138. Click Retrieve to obtain the latest information. Refer to Table 50 for more details.



Figure 138 ICM3 - Routing - Routing Table Window

Click Add in Figure 138. Configure the parameters and click Apply in Figure 139 to bring the modification into effect.

Table 50 ICM3 - Routing - Routing Table Field Descriptions

Parameter Value RangeNumber Value range: 1 - 8000

Type Value range: RIP / OSPF / Static / Connected / Subnet

Destination Value range: valid IP address

Subnet Mask Value range: valid subnet mask

Gateway Value range: valid IP address

Interface VLAN Interface name

Metric Not applicable to static routes.

Administrative Distance Route preference value. Configurable for static routes. Read-only for dynamic routes. 0 for connected interface routes. 1 for all other static routes




Figure 139 ICM3 - Routing - Add


The ICM3 module supports the following routing configuration options:

■ RIP

■ General

■ Redistribution Setup

■ Neighbor Setup

■ Peer Details

■ Key Setup

■ Interface Setup

■ OSPF

■ General

■ Route Redistribution

■ Area Setup

■ Address Ranges

■ LSDB Table


■ Interface Setup

■ ARP



RIPThis feature is applicable for single shelf ICM3 module or master shelf ICM3 module only.

RIP supports network oriented VLAN interfaces and the ICM3 modules supports RIP-1, RIP-1 compatibility and RIP-2 modes. Refer to the following section for more details:

■ General

■ Redistribution Setup

■ Neighbor Setup

■ Peer Details

■ Key Setup

■ Interface Setup

General Expand the active ICM3 module from the tree view and expand Routing. Select RIP to open Figure 140. Click Retrieve to obtain the latest information. Refer to Table 51 for more details.



Figure 140 ICM3 - Routing - RIP - General Window

Redistribution Setup Maximum of 3 types of routes could be imported into RIP domain.

Expand the active ICM3 module from the tree view and expand Routing. Select RIP and click Redistribution Setup tab to open Figure 141. Click Retrieve to obtain the latest information. Refer to Table 52 for more details.

Table 51 ICM3 - Routing - RIP - General Table

Field DescriptionRoute Changes The number of route changes made to the routing database by

RIP excluding the refresh of a route's age.

Value range: 32-bit integer

Queries Received The number of responses sent to RIP queries




Figure 141 ICM3 - Routing - RIP - Redistribution Setup Window

Click Add in Figure 141 or select an entry and click Modify to modify. Configure the parameters in Figure 142 and click Apply to take the modification into effect.

Table 52 ICM3 - Routing - RIP - Redistribution Setup Table

Field DescriptionProtocol Redistributing any combination of connected, static and OSPF

routes into RIP domain is allowed. Routing entries from other protocols exist 120 seconds after the source is removed from the redistribution list.

Value range: Connected / Static / OSPF / None (None: disable redistribution of non-RIP routes)

Metric RIP metric

Value range: 0 - 16



Figure 142 ICM3 - Routing - RIP - Redistribution Setup - Add Window

Neighbor Setup Expand the active ICM3 module from the tree view and expand Routing. Select RIP and click Neighbor Details tab to open Figure 143. Click Retrieve to obtain the latest information. Refer to Table 53 for more details.

Figure 143 ICM3 - Routing - RIP - Neighbor Details Window



Click Add in Figure 143 to create a new entry. Configure the parameters in Figure 144 and click Apply to take the modification into effect.

Figure 144 ICM3 - Routing - RIP - Neighbor Details - Add Window

Peer Details Expand the active ICM3 module from the tree view and expand Routing. Select RIP and click Peer Details tab to open Figure 145. Click Retrieve to obtain the latest information. Refer to Table 54 for more details.

Table 53 ICM3 - Routing - RIP - Neighbor Details Table

Field DescriptionSerial Number Neighbor ID number

Neighbor Address Maximum of 16 RIP neighbors can be configured. The RIP neighbor IP address must be in the same subnet of the network VLAN interface.



Figure 145 ICM3 - Routing - RIP - Peer Details Window

Key Setup ICM3 randomly select keys from the keychain for plain text and MD5 authentication for RIP authentication.

Expand the active ICM3 module from the tree view and expand Routing. Select RIP and click Key Setup tab to open Figure 146. Click Retrieve to obtain the latest information. Refer to Table 55 for more details.

Table 54 ICM3 - Routing - RIP - Peer Details Table

Field DescriptionPeer Address Peer address

Version Version number

Bad Packets Count The number of bad packets

Bad Routes Count The number of bad routes

Last Update The time of last update



Figure 146 ICM3 - Routing - RIP - Key Setup Window

Click Add in the Keychain Setup section of Figure 146 to create a new keychain. Or select a keychain and click Modify to modify the name. Configure the parameters in Figure 147 and click Apply to take the modification into effect.

Table 55 ICM3 - Routing - RIP - Key Setup Table

Field DescriptionKeychain Setup

Serial Number Keychain ID number

Maximum of 6 keychains

Keychain Keychain name

Key Setup

Key Index Key ID number

Maximum of 255 keys

Key Key name



Figure 147 ICM3 - Routing - RIP - Key Setup - Add Keychain Window

Select a keychain in the Keychain Setup section and the corresponding keys are then listed in the Key Setup section.

Click Add in the Key Setup section of Figure 146 to create a new key. Or select a key and click Modify to modify the name. Configure the parameters in Figure 148 and click Apply to take the modification into effect.

Figure 148 ICM3 - Routing - RIP - Key Setup - Add Key Window

Interface Setup Expand the active ICM3 module from the tree view and expand Routing. Select RIP and click Interface Setup tab to open Figure 149. Click Retrieve to obtain the latest information. Refer to Table 56 for more details.



Figure 149 ICM3 - Routing - RIP - Interface Setup Window

Table 56 ICM3 - Routing - RIP - Interface Setup Table

Field DescriptionVLAN Interface Available VLAN interface

Authentication Type Value range: Plain Text / MD5

Default: Plain Text

Keychain Only applicable to network oriented routed VLAN interfaces.

Value range: None / Key1-6 (previously created)

Default: None

Mode Enables or disables the RIP module from transmitting/receiving updates on the VLAN interface. Only applicable to network oriented routed VLAN interfaces.

Value range: Active / Passive

Default: Active




Figure 150 ICM3 - Routing - RIP - Interface Setup - Add Window

Transmit Version Controls the version of update packets transmitted by the RIP module on the VLAN interface. Only applicable to network oriented routed VLAN interfaces.

Value range: Disable Transmit / v1 / v1-compatible / V2

Default: v1-compatible

Receive Version Controls the version of update packets accepted by the RIP module on the VLAN interface. Only applicable to network oriented routed VLAN interfaces.

Value range: v1 / v2 / v1-v2 / Disable Receive

Default: v1-v2

Split Horizon Enables or disables split horizon. Poisoned-Reverse instructs the RIP module whether or not to transmit update packets on the interface using split horizon with poison reverse.Only applicable to network oriented routed VLAN interfaces

Value range: Disabled / Simple / Poisoned-Reverse

Default: Poisoned-Reverse

Table 56 ICM3 - Routing - RIP - Interface Setup Table

Field Description




OSPFThis feature is applicable for single shelf ICM3 module or master shelf ICM3 module only.

OSPF supports network oriented VLAN interfaces and also a link-state database that can store up to 8000 LSAs. Refer to the following sections for more details:

■ General

■ Route Redistribution

■ Area Setup

■ Address Ranges

■ LSDB Table


■ Interface Setup

General Expand the active ICM3 module from the tree view and expand Routing. Select OSPF to open Figure 151. Click Retrieve to obtain the latest information. Configure the parameter and click Apply to bring the modification into effect. Refer to Table 57 for more details.



Figure 151 ICM3 - Routing - OSPF - General Window

Table 57 ICM3 - Routing - OSPF - General Table

Field Name Description OSPF Routing Value range: Enable / Disable

Router ID Value range: valid IP address

SPF Delay The SPF schedule delay time in seconds.

Value range: 0 - 2147483647

SPF Holdtime The hold time between SPFs in seconds.

Value range: 0 - 2147483647

Area Border Router Value range: Yes / No

AS Border Router Value range: Yes / No



Route Redistribution Expand the active ICM3 module from the tree view and expand Routing. Select OSPF and click Route Redistribution to open Figure 152. Click Retrieve to obtain the latest information. Configure the parameter and click Apply to bring the modification into effect. Refer to Table 58 for more details.

Default Information Originate Enable / disable generating a default external route into an OSPF routing domain.

Value range: Disable / Enable / Always (Always: advertises the default route regardless of whether the software has a default route)

Metric Metric used for generating the default route


Metric Type External link type associated with the default route advertised into the OSPF routing domain

Value range: Type 1 / Type 2

Number of Areas The number of OSPF areas configured.


Total LSAs Originated The total number of LSA originated

Total LSAs Received The total number of LSA received

Table 57 ICM3 - Routing - OSPF - General Table




Figure 152 ICM3 - Routing - OSPF - Route Redistribution Window


Table 58 ICM3 - Routing - OSPF - Route Redistribution Table

Field Name Description Protocol To redistribute any combination of connected, static and RIP

routes into OSPF domain.

Value range: Connected / Static / RIP / None (None: disable redistribution of non-OSPF routes. Connected routes is redistributes as external to the autonomous system)

Metric Metric used for generating the default route


Metric Type External link type associated with the default route advertised into the OSPF routing domain

Value range: Type 1 / Type 2



Figure 153 ICM3 - Routing - RIP - Route Redistribution- Add Window

Area Setup Expand the active ICM3 module from the tree view and expand Routing. Select OSPF and click Area Setup tab to open Figure 154. Click Retrieve to obtain the latest information. Refer to Table 59 for more details.



Figure 154 ICM3 - Routing - OSPF - Area Setup Window

Table 59 ICM3 - Routing - OSPF - Area Setup Table

Field DescriptionArea ID ID number in w.x.y.z format.

Maximum of 4 areas can be configured.

Area Type Value range: Plain / Stub NSSA

Default: Stun

Summary LSA Allow importing of OSPF summary LSAs. Only applicable to stub and NSSA area types.

Value range: Enabled / disabled

Default: Enabled

Status Value range:

Default:

SPF Run The number of times that the intra-area route table has been calculated using this area's link-state database.

ABR Count Area Border Router Count. The total number of area border routers reachable within this area.



Click Add in Figure 154 or select an entry and click Modify. Configure the parameters and click Apply in Figure 155 to bring the modification into effect.

Figure 155 ICM3 - Routing - OSPF - Area Setup - Add Window

ASBR Count Area Border Router Count. The total number of AS border routers reachable within this area.

LSA Count The number of LSAs in this area.

LSA Checksum The sum of LSA checksums.

Default Cost Cost of default route sent into OSPF stub and NSSA area. Only applicable to ABR attached to a stub or NSSA.


Default: 1

No-Redistribution Used to block redistribution of imported routes to NSSA when the router is an NSSA ABR. Redistribution of imported routes to normal areas are not affected by this setting.


Default: Enable

Default Information Originate

Generate of type 7 default route into OSPF domain. Only applicable to NSSA area type.


Default: Disable

Table 59 ICM3 - Routing - OSPF - Area Setup Table

Field Description




Address Ranges Expand the active ICM3 module from the tree view and expand Routing. Select OSPF and click Address Ranges tab to open Figure 156. Click Retrieve to obtain the latest information. Refer to Table 60 for more details.

Figure 156 ICM3 - Routing - OSPF - Address Ranges Window

Table 60 ICM3 - Routing - OSPF - Address Ranges Table

Field DescriptionArea ID ID number in w.x.y.z format

Address Common IP address prefix of the summarized networks. This is only applicable when the ICM3 is the ABR or ASBR. Up to 64 ranges can be specified for an area.



Select an area ID. Click Add in Figure 156 or select an entry and click Modify. Configure the parameters and click Apply in Figure 157 to bring the modification into effect.

Figure 157 ICM3 - Routing - OSPF - Address Ranges - Add Window


LSDB Table LSDB tables supports 8000 entries.

Expand the active ICM3 module from the tree view and expand Routing. Select OSPF and click LSDB Table tab to open Figure 158. Click Retrieve to obtain the latest information. Refer to Table 61 for more details.

Mask Subnet mask for the IP address

Type Value range: Router(1) / Network(2) / Network-Summary(3) / ASBR-Summary (4) / AS-External(5) / NSSA-External(7)

Advertize True: advertise generates a Type 3 summary LSA based on the IP address range.

False: not-advertise suppresses the Type 3 summary LSA specified by the address range and the component networks remain hidden from other networks.

Table 60 ICM3 - Routing - OSPF - Address Ranges Table

Field Description



Figure 158 ICM3 - Routing - OSPF - LSDB Table Window

Table 61 ICM3 - Routing - OSPF - LSDB Table

Field DescriptionArea ID Type of the area

Value range: All / Internal / External / previously created Area ID

Area LSA Count The number of LSAs in this area.

Area LSA Checksum The sum of LSA checksums.

Area ID Area ID in w.x.y.z format

LS Type Value range: Router / Network / Network-Summary / ASBR-Summary / AS-External / NSSA-External

Link State ID Value range: valid IP address

Advertising Router Value range: valid IP address

LS Sequence Number Value range: Hexadecimal

LS Age LS age in seconds

LS Checksum Value range: Hexadecimal



Select an area ID type to display all, internal or external area. Highlight a specific entry to display detailed information. Depending on the LS type of the entry, different information are displayed:

Table 62 ICM3 - Routing - OSPF - LSDB Table - LS Type Table

Field DescriptionLS Type is Router:

Router Type AS Boundary Router, Area Border Router, Endpoint Active Virtual Link, Internal Router

Number of Links Number of individual links inside this link state record


Network / Subnet Point to Point: router ID of the neighboring router.

Transit Network: IP address of designated router interface to the network.

Stub Network: IP address of network or subnet.

Virtual Link: router ID of the virtual link neighbor.

Value range: IP address

Network Mask Value range: IP address

Link Connection Connection offered by the router interface.

Value range: Point to Point /Transit Network / Sub Area / Virtual Link

LS Type is Network:

Network Mask The mask for the network to which the designated router is attached.


Attached Routers Read-only. Router ID for all routers attached to the network adjacent with the designated router.


LS Type is Network-Summary or ASBR-Summary:

Network Mask Mask for the summarized network.


Metric Cost of reaching the summary network/ASBR from the advertising router/ASBR.


LS Type is AS-External or NSSA-External:

Network Mask Mask for the network.


Metric Type OSPF type 1 or type 2 network.

Value range: 1 / 2



Neighbor Details Expand the active ICM3 module from the tree view and expand Routing. Select OSPF and click Neighbor Details tab to open Figure 159. Click Retrieve to obtain the latest information. Refer to Table 63 for more details.

Metric Cost of reaching the external network from the advertising router (ASBR).


Forwarding Address Address to which packets for the advertised external network must be sent.


External Route Tag Tag that can be applied to a route by the protocol from which it originates.

Value range: Decimal number

Table 62 ICM3 - Routing - OSPF - LSDB Table - LS Type Table

Field Description



Figure 159 ICM3 - Routing - OSPF - Neighbor Details Window

Interface Setup Expand the active ICM3 module from the tree view and expand Routing. Select OSPF and click Interface Setup tab to open Figure 160. Click Retrieve to obtain the latest information.

Table 63 ICM3 - Routing - OSPF - Neighbor Details Table

Field DescriptionNeighbor Address Neighbor IP address

Router ID Neighbor router IP address

Priority The priority assigned to the neighbor router




Figure 160 ICM3 - Routing - OSPF - Interface Setup Window

Click Add or select an entry and click Modify in Figure 160. Configure the parameters and click Apply in Figure 161 to bring the modification into effect. Refer to Table 64 for more details.

Configure the VALN priority to 0 to prevent the ICM3 from becoming the Designated Router or the Backup Designated Router.



Figure 161 ICM3 - Routing - OSPF - Interface Setup - Add Window


Table 64 ICM3 - Routing - OSPF - Interface Setup Table

Field DescriptionVLAN Interface Available VLAN interface

Area ID Area ID in w.x.y.x format

Cost Value range: 1 - 65535

Priority Value range: 0 - 255

Default: 1

Authenticate Enable / disable plain text authentication

Value range: None / Text

Default: None

Password Used for plain text authentication. Only applicable to network oriented routed VLAN interfaces. The password is displayed as "********" regardless of the password length. The password is displayed in CLI.

Transmit Delay Value range: 1 - 3600 seconds

Default: 1 s

Retransmit Delay Value range: 1 - 3600 seconds

Default: 5 s

Hello Interval Value range: 1 - 65535 seconds

Default: 10

Dead Interval Value range: 1 - 65535 seconds

Default: 40



ARPThis feature is applicable for single shelf ICM3 module or master shelf ICM3 module only.

ICM3 module learns ARP entries from the received ARP request messages. IP DSLAM ensures that any IP traffic originated from the DSL subscriber only appears on one and only one subscriber Ethernet interface. Hence, the ICM3 module can correctly discover and associate the subscriber IP address with the Ethernet interface and insert a route entry into the routing table without static configuration or the aid of complex dynamic routing protocols

ICM3 sends ARP requests when it needs to:

■ resolve correct mapping between an IP address and MAC address

■ a complete ARP entry times out

■ ARP response timeout for incomplete ARP entries.

A complete ARP cache entry is one that has complete MAC and IP address mapping. Timeout triggers new address resolution (confirmation) attempt. If the attempt succeeds, the timer restarts. If it fails, the entry will not be used for forwarding and the user shall see the entry as incomplete.

The timeout for new incomplete dynamic ARP entries during address resolution for is three times of the retransmission timeout. After timeout the entry is not used for forwarding and it is displayed as incomplete. An incomplete ARP cache entry is one that does not have full MAC address information.

Expand the active ICM3 module from the tree view and expand Routing. Select ARP to open Figure 162. Click Retrieve to obtain the latest information. Refer to Table 65 for more details.



Figure 162 ICM3 - Routing - ARP Window

Configure the parameters and click Apply in Figure 162 to bring the modification into effect.

When the Complete Entry Timeout or the Retransmission Timeout is modified, the new timers do not effect the existing ARP entries. Those existing

Table 65 ICM3 - Routing - ARP Field Description

Field DescriptionComplete Entry Timeout Valid range: 0 - 30 minutes

0: disable

Default: 20 minutes

Retransmission Timeout Valid range: 1 - 30 seconds

Default: 1 second

VLAN ID VLAN ID number

Ethernet Port Ethernet Port ID

MAC Address The MAC address of a subscriber.

IP Address The IP address of a subscriber.

Type Value range: Dynamic / Static

Static ARP entries remains in the table until manually deleted by the operator.



entries continue to use the previous timer value until the complete entry timer expires. Then when the ICM3 refreshes those entries, the new timer is used for these entries.


Figure 163 ICM3 - Routing - ARP - Add Window

Select an entry in Figure 162 and click Delete to remove the entry. Or click Delete Advanced to delete entries with the same criteria in Figure 164.

Figure 164 ICM3 - Routing - ARP - Delete Advanced Window



DHCP This feature is applicable for single shelf ICM3/3G module or master shelf ICM3/3G module only.

ICM3/3G supports DHCP relay function for routed DHCP packets. The DHCP relay agent relays DHCP packets with DHCP option 82 present.

Note: DHCP function is upgraded to support routed layer 3 VLANs in Release 3.1. All layer 2 bridged VLAN DHCP configurations from previous releases become invalid and are removed during the software upgrade. User must configure the DHCP parameters to recreate DHCP interface.

ICM3/3G module supports the following configuration for DHCP:

■ Server

■ Profile

■ Subnet Mapping

■ Pool

■ Map

■ Lease

■ Option 60

■ Option 82

■ VLAN

ServerExpand the active ICM3/3G module from the tree view and select DHCP to open Figure 165. Click Retrieve to obtain the latest information. Configure the parameters and click Apply to bring the modification into effect. Refer to Table 66 for more details.

Note: After any changes are made for DHCP server or DHCP relay, the DHCP server must be disabled and then re-enabled for the modification to take effect.

Note: The DHCP server must always be enabled in order for management communication between ICM3/3G module and line modules to occur, except when it is momentarily disabled then re-enabled as noted above.



Figure 165 ICM3 - DHCP - Server Window

ProfileExpand the active ICM3/3G module from the tree view and select DHCP. Click the Profiles tab to open Figure 166. Click Retrieve to obtain the latest information.

Table 66 ICM3/3G - DHCP - Server Field Description

Parameter DescriptionDHCP Service Enable / disable DHCP server and relay functions at the module level.

Timeout This counter parameter sets the number of times the DHCP server pings an address before it determines that the address is not in use.

Value range: 1-10

Default: 2

Interval (ms) This parameter specifies the time frame the DHCP server waits for each ping reply. The interval value is specified in milliseconds.

Value range: 100-10000 ms

Default: 500 ms



Figure 166 ICM3 - DHCP - Profile Window

Click Add or select an entry and click Modify in Figure 166. Configure the parameters and click Apply in Figure 167 to bring the modification into effect. Refer to Table 67 for more details.



Figure 167 ICM3/3G - DHCP - Profile - Add Window



Table 67 ICM3/3G - DHCP - Profile - Add Table

Parameter Field DescriptionProfile name A character string with maximum of 20 characters

Default Lease Time Value range: up to 49170 days

Default: 86400 seconds (1 day)

Maximum Lease Time Value range: up to 49170 days

Default: 172800 seconds (2 day)

Subnet Mask Value range: valid IP address

Time Offset Value range: 32-bit integer

Host Name Value range: character string with maximum of 256 characters

Boot File Size Value range: 0 - 65535

Merit Dump File Value range: character string with maximum of 64 characters

Domain Name Value range: character string with maximum of 256 characters

Swap Server Value range: valid IP address

Root Path Value range: character string with maximum of 128 characters

IP Forwarding Value range: Enable / Disable

Non-local Source Routing Value range: Enable / Disable

Default IP TTL Value range: 1 - 255

Path MTU Aging Timeout Value range: 0 - 4294967295 seconds

Interface MTU Value range: 0 65536

All Submits Are Local Value range: Enable / Disable

Broadcast Address Value range: valid IP address

Perform Mask Discovery Value range: Enable / Disable

Mask Supplier Value range: Enable / Disable

Perform Router Discovery Value range: Enable / Disable

Router Solicitation Address Value range: valid IP address

Static Routes Value range: maximum of 4 destination/router address pairs

Trailer Encapsulation Value range: Enable / Disable

ARP Cache Timeout Value range: 0 - 4294967295 seconds

Ethernet Encapsulation Value range: Enable / Disable

TCP Default TTL Value range: 1 - 255

TCP Keepalive Interval Value range: 0 - 4294967295 seconds

TCP Keepalive Garbage Value range: Enable / Disable

Network Information Service Domain Value range: character string with maximum of 256 characters

NetBIOS over TCP/IP Node Type Value range: None / B-node / P-node / M-node / H-node

NetBIOS over TCP/IP Scope Value range: character string with maximum of 64 characters.

TFTP Server Name Value range: character string with maximum of 64 characters



Select an entry in Figure 166 and click Delete to remove the entry. Or click Delete All to remove all entries.

Subnet MappingExpand the active ICM3/3G module from the tree view and select DHCP. Click the Subnet Mapping tab to open Figure 168. Click Retrieve to obtain the latest information.

Bootfile Name Value range: character string with maximum of 128 characters

Vendor Specific Information Value range: character string with maximum of 64 characters

Router IP Addresses Maximum of 4 IP addresses

Time Servers Maximum of 4 IP addresses

Name Servers Maximum of 4 IP addresses

Domain Name Servers Maximum of 4 IP addresses

Log Servers Maximum of 4 IP addresses

Cookie Servers Maximum of 4 IP addresses

LPR Servers Maximum of 4 IP addresses

Impress Servers Maximum of 4 IP addresses

Resource Location Servers Maximum of 4 IP addresses

Network Information Servers Maximum of 4 IP addresses

Network Time Protocol Servers Maximum of 4 IP addresses

NetBios Name Servers Addresses Maximum of 4 IP addresses

X Font Servers Maximum of 4 IP addresses

X Display Managers Maximum of 4 IP addresses

Path MTU Plateau Table Maximum of 9 entries


Static Route Destination Maximum of 4 static route pairs

Static Route Address Maximum of 4 static route pairs

Policy Filter Address Maximum of 4 policy filter pairs

Policy Filter Netmask Maximum of 4 policy filter pairs

Table 67 ICM3/3G - DHCP - Profile - Add Table

Parameter Field Description



Figure 168 ICM3 - DHCP - Subnet Mapping Window




Figure 169 ICM3/3G - DHCP - Subnet Mapping - Add Window


PoolAddress pools are automatically assigned to a routed VLAN interface based on the VLAN interface subnet.

Expand the active ICM3/3G module from the tree view and select DHCP. Click the Pool tab to open Figure 170. Click Retrieve to obtain the latest information.



Figure 170 ICM3 - DHCP - Pool Window




Figure 171 ICM3/3G - DHCP - Pool - Add Window


MapExpand the active ICM3/3G module from the tree view and select DHCP. Click the Map tab to open Figure 172. Click Retrieve to obtain the latest information.



Figure 172 ICM3 - DHCP - Map Window




Figure 173 ICM3/3G - DHCP - Map - Add Window


LeaseExpand the active ICM3/3G module from the tree view and select DHCP. Click Lease tab to open Figure 174. Click Retrieve to obtain the latest information.



Figure 174 ICM3 - DHCP - Lease Window

Select an entry in Figure 174 and click Validate Selection to validate the entry. Or click Validate All to remove all entries.

Option 60DHCP server selects the corresponding DHCP profile and address scope based on option 60 filter. The DHCP profile selected via option 60 takes precedence over DHCP profile selected via IP subnet. However, the DHCP profile selected via option 82 takes precedence over DHCP profile selected via option 60.

Expand the active ICM3/3G module from the tree view and select DHCP. Click Option 60 tab to open Figure 175. Click Retrieve to obtain the latest information.



Figure 175 ICM3 - DHCP - Option 60 Window


Figure 176 ICM3/3G - DHCP - Option 60 - Add Window



Option 82DHCP server selects the corresponding DHCP profile and address scope based on option 82 filter. Up to 16 option 82 filters are supported. The DHCP profile selected via option 82 takes precedence over DHCP profile selected via option 60.

Expand the active ICM3/3G module from the tree view and select DHCP. Click Option 82 tab to open Figure 177. Click Retrieve to obtain the latest information.

Figure 177 ICM3 - DHCP - Option 82 Window




Figure 178 ICM3/3G - DHCP - Option 82 - Add Window

VLANICM3/3G supports 2 DHCP relay server per route/subscriber VLAN.

Expand the active ICM3/3G module from the tree view and select DHCP. Click the VLAN tab to open Figure 179. Click Retrieve to obtain the latest information.



Figure 179 ICM3 - DHCP - VLAN Window

Select an entry and click Modify in Figure 179. Configure the parameters and click Apply in Figure 180 to bring the modification into effect.



Figure 180 ICM3/3G - DHCP - VLAN - Modify Window

Packet Classification This feature is applicable for single shelf ICM3/3G module or master shelf ICM3/3G module only.

Classification is the basis for flow-based packet processing. Classification can be used for ACL to drop un-wanted packets, packet priority to set internal priority or change 802.1p/DSCP, rate metering or packet mirroring.

ICM3/3G supports ACL configuration per port and also supports support 10 classification masks and 80 rules shared by all external and internal ports.

The packet is forwarded if there is no match found in any configured ACLs.

ICM3/3G module supports the following configuration or packet classification:

■ Masks

■ Actions

■ Meters

■ Flow Counters

■ Rules

MasksIP DSLAM supports 10 ACL masks based on a combination of packet fields.

Expand the active ICM3/3G module from the tree view and select Packet Classification to open Figure 181. Click Retrieve to obtain the latest information.



Figure 181 ICM3 - Packet Classification - Masks Window

Click Add in Figure 181. Configure the parameters and click Apply in Figure 182. The mask can be any combination of the options with the exception listed in Table 68. Refer to Table 68 for more details.



Figure 182 ICM3/3G - Packet Classification - Masks - Add Window

Table 68 ICM3/3G - Packet Classification - Masks - Add Field Description

Field DescriptionPriority Determines which field to be filtered first. 10 has the highest priority

Value range: 1-10

Name A character string up to 20 characters

Source MAC address The 48 wildcard bits identify the bits to ignore in the source address.

Default: 00:00:00:00:00:00

Destination IP The 32 wildcard bits identify the bits to ignore in the source address.

Default: 00:00:00:00:00:00

Destination MAC address The 48 wildcard bits identify the bits to ignore in the source address.

Default: 00:00:00:00:00:00

Ethernet Type Filtering based on ethernet type

Source IP The 32 wildcard bits identify the bits to ignore in the source address.

Default: 00:00:00:00:00:00



Select an entry in Figure 181 and click Delete to remove the entry. A mask cannot be removed if there’s rules associated with it. Delete the rules associated with the selected mask first.

ActionsICM3/3G modules supports up to 8 combined actions for each ACL.

Expand the active ICM3/3G module from the tree view and select Packet Classification. Click the Actions tab to open Figure 183. Click Retrieve to obtain the latest information.

Destination IP The 32 wildcard bits identify the bits to ignore in the destination address.

Default: 00:00:00:00:00:00

IP Protocol Type Not applicable if any of the following fields are selected: Source TCP, Source UDP port, Destination TCP, Destination UDP, TCP ACK, TCP SYN, TCP FIN

Source TCP port Not applicable if any of the following fields are selected: IP protocol type, Source UDP, Destination UDP.

Source UDP port Not applicable if any of the following fields are selected: IP protocol type, Source TCP, Destination TCP, TCP ACK, TCP SYN, TCP FIN.

Destination TCP port Not applicable if any of the following fields are selected: IP protocol type, Source UDP, Destination UDP.

Destination UDP port Not applicable if any of the following fields are selected: IP protocol type, Source TCP, Destination TCP, TCP ACK, TCP SYN, TCP FIN.

VLAN ID Filtering based on VLAN ID

802.1p Filtering based on 802.1p

TOS Precedence Bits IP Type of Service precedence bits.

Not applicable if DSCP is selected.

TOS Bits IP Type of Service bits.

Not applicable DSCP is selected.

DSCP Not applicable if TOS Precedence Bits or TOS Bits is selected.

Egress Port Filtering based on egress port

TCP ACK Not applicable if any of the following fields are selected: IP protocol type, Source UDP, Destination UDP.

TCP SYN Not applicable if any of the following fields are selected: IP protocol type, Source UDP, Destination UDP.

TCP FIN Not applicable if any of the following fields are selected: IP protocol type, Source UDP, Destination UDP.

Table 68 ICM3/3G - Packet Classification - Masks - Add Field Description

Field Description



Figure 183 ICM3 - Packet Classification - Actions

Click Add in Figure 183. Configure the parameters and click Apply in Figure 184. The action can be any combination of the options with the exception listed in Table 69. Refer to Table 69 for more details.



Figure 184 ICM3/3G - Packet Classification - Actions - Add

Table 69 ICM3/3G - Packet Classification - Actions - Add Field Description

Field DescriptionIndex Value range: 1 - 80

Name Up to 20 characters

Permit Set permission

Deny Set permission

Set 802.1p Value range: 0 - 7

Set DSCP Value range: 0 - 63

Not applicable if Set TOS precedence or Set TOS is selected.

Set TOS Precedence Value range: 0 - 7

Not applicable if Set DSCP is selected.



Select an entry in Figure 183 and click Delete to remove the entry. An action cannot be removed if there’s rules associated with it. Delete the rules associated with the selected action first.

MetersMetering is applied on egress ports. If the egress port line rate is lower than the configured CIR, ICM3/3G applies the maximum CIR and burst size supported by the egress port.

Expand the active ICM3/3G module from the tree view and select Packet Classification. Click the Meters tab to open Figure 185. Click Retrieve to obtain the latest information.

Figure 185 ICM3 - Packet Classification - Meters

Change VLAN ID Value range: 1 - 4092

Change Destination Interface

Value range: Internal 1 -16 / FE 1 - 4 / GE 1 - 2

Set Priority Value range: 0 - 7

Set Destination MAC Value range: valid MAC address

Copy To Mirror Port Enable coping to mirror port

Set Drop Precedence Enable drop precedence

Table 69 ICM3/3G - Packet Classification - Actions - Add Field Description

Field Description



Click Add in Figure 185. Configure the parameters and click Apply in Figure 186. Refer to Table 69 for more details.

Figure 186 ICM3/3G - Packet Classification - Meters - Add


Flow CountersICM3/3G supports 32 flow-based traffic statistics counters.

Expand the active ICM3/3G module from the tree view and select Packet Classification. Click the Flow Counters tab to open Figure 187. Click Retrieve to obtain the latest information.

Table 70 ICM3/3G - Packet Classification - Meters - Add Field Description

Field DescriptionIndex Value range: 1 - 64

CIR Value range: 64 - 1000000

Burst Size Value range: 4K - 512K



Figure 187 ICM3 - Packet Classification - Flow Counters

Select an entry in Figure 187 and click Reset to reset the packet counters. Or click Reset ALL to reset all the counters.

RulesCreate Masks and Actions before creating packet classification rules. IP DSLAM supports 80 rules shared between all ports.

Expand the active ICM3/3G module from the tree view and select Packet Classification. Click the Rules tab to open Figure 188. Click Retrieve to obtain the latest information.



Figure 188 ICM3 - Packet Classification - Rules




Figure 189 ICM3/3G - Packet Classification - Rules - Add


QoS ICM3/3G module supports the following QoS configuration:

■ Priority

■ DSCP Priority

■ Queue Mapping

■ L2 Scheduling



PriorityThis feature enables/disables the mapping between DSCP and 802.1p.

Expand the active ICM3/3G module from the tree view and select QoS to open Figure 190. Click Retrieve to obtain the latest information.

Figure 190 ICM3 - QoS - Priority

Click the DSCP Priority field of a port and configure the priority in the drop down menu as shown in Figure 191. Click Apply to bring the modification into effect.



Figure 191 ICM3 - QoS - Priority - Modify

DSCP PriorityThis feature configures the 802.1p priority for DSCP.

Expand the active ICM3/3G module from the tree view and select QoS. Click the DSCP Priority tab to open Figure 192. Click Retrieve to obtain the latest information.



Figure 192 ICM3 - QoS - DSCP Priority

Click the IEEE 802.1p Priority field of a DSCP and configure the priority in the drop down menu as shown in Figure 193. Click Apply to bring the modification into effect.



Figure 193 ICM3 - QoS - DSCP Priority - Modify

Queue MappingThis feature configures the CoS traffic class for 802.1p priority.

Expand the active ICM3/3G module from the tree view and select QoS. Click the Queue Mapping tab to open Figure 194. Click Retrieve to obtain the latest information.



Figure 194 ICM3 - QoS - Queue Mapping

Click the CoS Traffic Class field of 802.1p priority and configure the traffic class in the drop down menu as shown in Figure 195. Click Apply to bring the modification into effect. Refer Table 71 to for more details.



Figure 195 ICM3 - QoS - DSCP Mapping - Modify

L2 SchedulingExpand the active ICM3/3G module from the tree view and select QoS. Click the L2 Scheduling tab to open Figure 196. Click Retrieve to obtain the latest information.

Table 71 ICM3/3G - QoS - DSCP Mapping

802.1p PriorityCoS Traffic Class

Range Default0 0-7 2

1 0-7 0

2 0-7 1

3 0-7 3

4 0-7 4

5 0-7 5

6 0-7 6

7 0-7 7



Figure 196 ICM3 - QoS - L2 Scheduling

Click the Enable or Disable radio button in Figure 196 to enable/disable WRED (Weighted Random Early Discard) option. Click Apply to bring the modification into effect.

Select a scheduling algorithm in Figure 196 and click Apply to bring the modification into effect.

ICM3/3G support the following scheduling method:

■ Strict priority (SP)

Any packets residing in the higher-priority queues are transmitted first. Only when these queues are empty packets of the next lower priority are allowed to be transmitted.

■ Weighted round robin (WRR)

The scheduler selects one packet from each queue and go around all active queues that have a pending packet. All active queues are programmed with weights according to the desired packet distribution.

■ Weighted Fair Queue (WFQ)

The scheduler provides a certain minimum bandwidth to all queues for transmission preventing the starvation of packets in lower priority queues.



Configured guaranteed bandwidth is first supplied per queue. Any remaining bandwidth up to the configured maximum bandwidth is distributed either by priority or in round-robin fashion. The provides for controllable CoS behavior while not allowing starvation of low priority queues.

■ WRR+SP combination

Both strict priority and weighted round-robin are supported. The weight of one or more of the CoS queues can be set to zero (largest number) and non-zero weights are assigned for other queues. Packets in queues with weight 0 are always sent first as long as there are packets in the Transaction Queues for these queues. If there are no packets in the queues of weight 0, then packets are sent from other queues in a weighted round-robin fashion.

■ WFQ+SP combination

Both strict priority and weighted fair queuing are supported. User assigned priority queues are scheduled on a strict priority basis up to their maximum bandwidth settings, while the remaining queues are scheduled in a WFQ fashion according to their relative bandwidth settings.

Table 72 lists the default weight for the scheduling method:

Note: the total weights for SP queues and WFQ queues must be less than or equal to 100%. If the total weight of SP queues is less than 100%, the remaining bandwidth is divided among WFQ queues based on the configured weights in weighted round-robin fashion. If the total weight of WFQ queues is less than 100%, the remaining bandwidth is distributed among the queues in strict priority fashion. When a queue is removed from the strict priority queue list, the queue weight is set to the default value of 0, which indicates that no minimum bandwidth is allocated to it.

Table 72 ICM3/3G - QoS - L2 Scheduling - Weight for WRR / SP+WRR

Parameter WRR / SP+WRR WFQ or SP+WFQ Weights for Queue 0 1 3

Weights for Queue 1 1 3








5
PROVISIONING - PCU MODULE
This chapter provides configuration procedures for Peripheral Control Unit (PCU) module.

PCU Module supports the following configurations:


■ Reset

■ Module Summary


■ Slot Level Configuration

■ PCU

■ Clock Source

■ Alarm Indication

■ PDP


PCU module supports module reset at the node level configuration.

Reset PCU module supports both hardware reset and software reset through Netman 4000.

The hard reset forces the PCU module to download software image from ICM3 module and reboot.

The soft reset forces the PCU module to reboot without downloading software image. There is no checking of software version during the soft reset.

Select the node from navigation tree and click Reset tab to open Figure 197. All modules are indicated with its shelf ID and slot ID. Click Retrieve to obtain the latest modules information.

Select a PCU module and click Hard Rest or Soft Reset radio button. Click Reset in the Reset Module section to begin the reset.


256 Chapter 5: Provisioning - PCU Module

Figure 197 PCU -Node - Reset

Module Summary Module Summary section provides basic information and module location for PCU module.

Expand the node from the navigation tree and select Module Summary to open Figure 198. Click Retrieve to obtain the latest information. Refer to Table 73 for more details.



Figure 198 PCU - Module Summary Window



Expand the node from the navigation tree and select Shelf to open Figure 199. Click Retrieve to obtain the latest information.

Table 73 PCU - Module Summary Table



X-Y: Shelf X Slot Y

PCU module is always at slot P





Figure 199 PCU - Shelf View Window

In Figure 199, PCU module is represented with a board image in slot P. Double click on the PCU board image opens the Slot Level Configuration.


Slot Level Configuration

PCU module supports the following configuration:

■ PCU

■ Clock Source

■ Alarm Indication

Table 74 PCU Module Placements Details


PCU 1 P No



■ PDP

PCU PCU provides the basic module information for the selected module.

Expand the node and expand a shelf from the navigation tree. Select Slot P: PCU from the tree view to open Figure 200. Click Retrieve to obtain the latest n information. Refer to Table 75 for more details.

Figure 200 PCU - PCU Window

Clock Source System timing signal can be generated from external network timing or from internal clock generator. PCU module supports two external network timing signal: E1 type 2MHz timing reference and 64 KHz AMI composite Annex C timing reference. A proper PCU population switches between the internal and external source accordingly to kept synchronized. Moreover, ICM3 must also be properly configured for the external clock type.

The external clock source is connected on PCU rear adaptor (RJ 45 socket marked CO Clock IN).

If the Annex-C clock is lost, the line module resets the loops that are currently using Annex-C (including lines that select Annex-C as standard and lines that

Table 75 PCU - PCU Table

Parameter DescriptionHardware Version The hardware version for this PCU module.

Software Version The software version for this PCU module.

Serial Number The serial number of the PCU module.



use Annex-C as a result of selecting auto-mode). If the line standard selected is auto-mode, the line module force the DSP to retain at the next best non-Annex-C line standard when such a ranking result is available. Otherwise the line module force the port to go through installation stage and scan without two Annex-C line standards. If the line standard selected is any Annex-C profile, the module forces the line to retrain using default profile. When Annex-C clock is recovered, the IPxDSL modules mark the event so that for the next line retrain, all the lines that have switched over to Non-Annex-C mode due to loss of clock will revert back to Annex-C mode.

Expand the node and expand a shelf from the navigation tree. Select Slot P: PCU from the tree view and select the Clock Source tab to open Figure 201. Click Retrieve to obtain the latest information. Configure the clock source and click Apply to bring the modification into effect. Refer to Table 76 for more details.

Figure 201 PCU - Clock Source Window



Alarm Indication Netman 4000 supports user-defined labels for PCU external alarms. The PCU collects external alarms from 8 general purpose sources that are defined by specific customer configuration. The ICM3 monitors the status of these external alarms and reports to Netman 4000.

Expand the node and expand a shelf from the navigation tree. Select Slot P: PCU from the tree view and select the Alarm Indication tab to open Figure 202. Click Retrieve to obtain the latest information. Refer to Table 77 for more details.

Figure 202 PCU - Alarm Indication Window

Table 76 PCU - Clock Source Table

Field DescriptionNo External Clock System runs on internal Clock source.

Default.

E1 Clock Select the external E1 Clock connected on PCU rear adaptor.

Annex C Clock Select the external Annex C clock connected on PCU rear adaptor.



Click Default in Figure 202 to reset all configurations to their default values.

Configure the parameters and click Apply to bring the modification into effect.

Note: Please refer to the iAN8K B1000 Release 3.1 Installation Manual for the exact location of the external alarm inputs.

PDP PCU module supports audible alarm warning, visual alarm display and alarm collection from PDP modules.

Visual alarm displays are implemented in two levels. On PDP, system LED is turned on when an external rack fan failure occurs. On PCU, one of the three severity-based LED (CRITICAL, MAJOR, MINOR) indicates the current highest alarm severity.

Audible alarm is generated from PDP. It is triggered when either an external rack fan failure or fuse failure occurs. The audio sound can be turned off temporarily (until next alarm triggers it) with the AUDIO button on the PDP. Visual alarm indications, however, cannot be temporarily altered. User can define the alarm visual/audible display behavior from the CLI/Netman 4000.

Expand the node and expand a shelf from the navigation tree. Select Slot P: PCU from the tree view and select the PDP tab to open Figure 203. Click Retrieve to obtain the latest information.

Configure the parameters and click Apply to bring the modification into effect. Refer to Table 78 for more details.

Table 77 PCU - Alarm Indication Table

Field DescriptionPin Label The user-defined alarm label (Note: the pin label field does not

synchronized with the pin label configured from CLI.)

Value range: a character string up to 138 characters

Default: Not Configured

Severity The severity of alarm for the detected the provisioned condition.

Value range: Warning / Minor / Major / Critical

Default: Warning

Level The signal level at which the alarm will be raised. If Never Raise Alarm is selected all other fields are ignored.

Value range: Low / High / Never Raise Alarm

Default: Never Raise Alarm



Figure 203 PCU - PDP Window

Table 78 PCU - PDP Table

Field DescriptionCollect Alarm From PDP To enable/disable collecting alarm from PDP.

Default: Disable

Control LED on PDP To enable/disable PDP LED control. This parameter is applicable if Collect Alarm From PDP is enable.

Default: Disable

Control Buzzer on PDP To enable/disable PDP buzzer control. This parameter is applicable if Collect Alarm From PDP is enable.

Default: Disable




6
PROVISIONING - IFXS1 MODULE
iFXS1 module can be managed by UTStarcom's NMS platform - Netman 4000. This chapter describes iFXS module operations in Netman 4000 device management system.

Viewing iFXS1 Module Information

From the configuration management navigation tree, select [Node/Shelf (x) /Slot (y):iFXS1], and click the Board Info tab to display the iFXS1 Module Information Window. Refer to Table 79 for field descriptions.

Figure 204 iFXS1 Module Information

Table 79 iFXS1 Module Information Window Field Description

Fields Description Serial Number Displays the module serial number

Hardware Version Displays the module hardware version

Software Version Displays the module software version


266 Chapter 6: Provisioning - iFXS1 Module

Configuring Module IP Address

From the configuration management navigation tree, select [Node/Shelf (x) /Slot (y):iFXS1], and click IP Config tab to display the IP Configuration window. The window enables users to set iFXS1 IP address for both media and signalling stream. Refer to Table 80 for field description.

System Uptime Displays the system run time since last reset

FPGA Ver. Displays the module FPGA version

Firmware Ver. Displays the module firmware version

CPU Usage Displays the percent of the module CPU usage

Memory Usage Displays the percent of the module memory usage

<Hard Reset> The hard reset forces iFXS to download software image from ICM3 before reboot.

If iFXS software image is not in the ICM3 flash during the hard reset, the reset shall be applied but no download of software image from ICM3 is required.

The same is applicable for FPGA image

<Soft Reset> The soft reset enables iFXS module to check the software version and software image shall be downloaded when there is a higher version available in ICM3 Flash than the one running on the module.

If iFXS software image is not in the ICM3 flash or has equal or lower version, the reset shall be applied but no download of software image from ICM is required.

The same is applicable for FPGA image.

Table 79 iFXS1 Module Information Window Field Description

Fields Description


Configuring Module IP Address 267

Figure 205 IP Configuration

Table 80 IP Configuration Window Field Description

Fields Description IP Config Mode Static or DHCP.

Static: users need to set IP address, net mask, gateway and DNS IP address for the iFXS1 module.

DHCP: the iFXS1 module gets IP address, net mask, gateway and DNS IP address from DHCP server

DNS Option The DNS option is always enabled.

IP Sets the iFXS1 module IP address

Netmask Sets the netmask for the module IP address

Gateway Sets the gateway for the module IP address

Usage Selects the IP address usage. Possible values are : unused, signaling, media, both



Configuring MG Interface

Configuring Call Server From the configuration management navigation tree, select [Node/Shelf (x) /Slot (y):iFXS1/ MG Interface], and click the Call Server tab to display the Call Server Configuration window. The window enables users to set call server protocol and call server type. Refer to Table 81 for field descriptions.

Figure 206 Call Server

Primary/Secondary Sets primary and secondary DNS IP address and port

DNS Sets primary/secondary DNS IP address

DNS Port Sets primary/secondary DNS port

Table 80 IP Configuration Window Field Description

Fields Description


Configuring MG Interface 269

Configuring Misc From the configuration management navigation tree, select [Node/Shelf (x) /Slot (y):iFXS1/ MG Interface], and click the Misc Config tab to display the Misc Config Configuration window. Users may enable/disable heartbeat and set SIP authentication option. Refer to Table 82 for field descriptions.

Figure 207 Misc Config

Table 81 Call Server Window Field Description

Fields DescriptionCall Server Protocol Selects the call server protocol. Possible values are: SIP/ MGCP

Call Server Type Selects the call server type. Possible values are: UTS, Broadsoft, Nortel, Asterisk



Configuring T.38 From the configuration management navigation tree, select [Node/Shelf (x) /Slot (y):iFXS1/ MG Interface], and click the T.38 tab to display the T.38 Configuration window. Refer to Table 83 for field description.

Table 82 Misc Configuration Window Field Description

Fields DescriptionHeart Beat Enable or disable heart beat.

When heart-beat option is enabled, MG will send and maintenance heart-beat message between MG and call server.

When heart-beat option is disabled, MG will not send heart-beat messages to call server.

SIP Auth Option Select the SIP authentication, possible values are MG Level and User Level. Only MG level is supported currently.

When SIP Auth Option is MG Level, MG will use unique auth password for each SIP user to register to SIP registrar, and only SIP MG-level auth password is necessary to be configured.

When SIP Auth Option is User Level, each SIP will use respective auth password to register to SIP registrar, and operator has to configure each SIP auth password in SIP user level.

InterDigitTimer Displays the inter digit timer. The value range is 5-20s. The default value is 5s.

BusyTone Displays the busy tone length. The value range is 20-60s. The default value is 30s.

DialTone Displays the dial tone length. The value range is 10-60s. The default value is 16s.

RingTone Displays the ringing back tone length. The value range is 60-300. The default value is 180s.

CallWaitingTone Displays the call waiting tone length. The value range is 20-60s. The default value is 30s.

HowlerTone Displays the howler tone length. The value range is 0-300s. The default value is 60s.

RecorderTone Displays the recorder tone length. The value range is 20-60s. The default value is 30s.


Configuring QoS 271

Figure 208 T.38

Configuring QoS

Configuring TOS/DSCP From the configuration management navigation tree, select [Node/Shelf (x) /Slot (y):iFXS1/ QoS], and click the TOS/DSCP tab to display the TOS/DSCP Configuration window. Users are enabled to set TOS/DSCP parameters. Refer to Table 84 for field descriptions.

Table 83 T.38 Window Field Descriptio

Fields DescriptionReversal Option Enable or disable the reversal option.

T.38 Option Enable or disable the T.38 option.

DTMF 2833 Option Enable or disable the DTMF 2833 option.

T.38 Fax mode Select T.38 fax mode from the drop-down list box. Possible values are: MGC controlled, GW controlled, SIP/MG controlled.

CallID Type Selects caller ID type from the drop-down list box. Possible values are: Bellcore, ETSI, NTT, UK, Chinese

DigitMap Configures the digit map for SIP user. String up to 512 letters from 0~9, T, A, B, C, D, #, *, x, [,], -.



Figure 209 TOS/DSCP

Configuring VLAN Tag From the configuration management navigation tree, select [Node/Shelf (x) /Slot (y):iFXS1/ QoS], and click the VLAN Tag tab to display the TOS/DSCP

Table 84 TOS/DSCP Window Field Description

Fields DescriptionTOS/DSCP Option Select QoS option. Possible values are TOS, DSCP, NONE

TOS

RTP Precedence Sets the IP precedence bits of the TOS byte in the IP header on media packets (RTP). The value range is 0 -7. The default value is 5.

Signaling Precedence Sets the IP precedence bits of the TOS byte in the IP header on signaling packets. The value range is 0 -7. The default value is 5.

DSCP the DSCP value in the IP header on signaling packets (SIP, MGCP), VoIP media packets (RTP)

RTP DSCP Sets the DSCP value in the IP header on VoIP media packets (RTP). Possible values are: AF11, AF12, AF13, AF21, AF22, AF23, AF31, AF32, AF33, AF41, AF42, AF43, BE, EF. The default is AF11.

Signaling DSCP Sets the DSCP the DSCP value in the IP header on signaling packets. Possible values are: AF11, AF12, AF13, AF21, AF22, AF23, AF31, AF32, AF33, AF41, AF42, AF43, BE, EF. The default is AF11.


Configuring QoS 273

Configuration window. Users are enabled to configure VLANs for signaling and media streams per iFXS1 module. Refer to Table 85 for field description.

Figure 210 VLAN Tag



Configuring User Interface

Node Configuration From the configuration management navigation tree, select [Node/Shelf (x) /Slot (y):iFXS1/ User Interface], and click the Node Configuration tab to display the Node Configuration window. Refer toTable 86 for field description.

Figure 211 Node Configuration

Table 85 VLAN Tag Window Field Description

Fields DescriptionVLAN Option Enables or disables VLAN option

RTP VLAN ID Enters the VLAN ID for VoIP media stream. The value range is 1-4092.

RTP VLAN Mode The mode is always fullbridging

Signaling VLAN ID Enters the VLAN ID for signaling. The value range is 1-4092.

Signaling VLAN Mode

The mode is always fullbridging


Configuring User Interface 275

Port Configuration From the configuration management navigation tree, select [Node/Shelf (x) /Slot (y):iFXS1/ User Interface], and click the Port Configuration tab to display the Port Configuration window. Refer to Table 87 for field description.

Table 86 Node Configuration Window Field Description

Fields DescriptionHook Flash (min) Selects the minimum flash hook timing. The value range is 50 -

1000ms with the step of 50ms.

Hook Flash (max) Selects the maximum flash hook timing. The value range is 100 - 1000ms with the step of 50ms.

Impedance Selects the impedance. possible values are: 600 ohm, customized, default complex, 900 ohm

Compander Selects the PCM type for the FXS port. Possible values are: A-law, U-law

Caller ID Select the caller ID type. Possible values are Bellcore, ETSI, NTT, UK, Chinese

Ring Duration (ms) Selects the Caller ID initial ring duration. The value range is 400 - 2000ms.



Figure 212 Port Configuration

Table 87 Port Configuration Window Field Description

Fields DescriptionPort Displays the FXS port number

Tx Displays the Tx gain of the FXS port. The value range is 0 - -9dB with the step of 0.5dB.

Rx Displays the Rx gain of the FXS port. The value range is 0 - -9dB with the step of 0.5dB.

Admin Displays the administrative state of the FXS port. Possible values are Unlocked, Shutting down, Locked

Operate Displays the operational status of the FXS port. Possible values are Enabled, Disabled, Testing

Usage Display the port status. Possible values are Idle, Active, Busy, Fault, Unknown


Configuring User Interface 277

Modifying a FXS PortFollow the steps below to modify a FXS port.

1 Select User Interface under the iFXS1 module from the configuration navigation tree.

2 Click Port Configuration tab.

The Port Configuration window is displayed as shown in Figure 212.

3 Select a port.

4 Click <Modify>.

The iFXS Port Level Config window is displayed.

5 Modify the port according to description in Table 87.

6 Click <Apply>.

The port information is displayed in iFXS Port Level Config window.

Configuring RingDefinition

From the configuration management navigation tree, select [Node/Shelf (x) /Slot (y):iFXS1/ User Interface], and click the Ring Definition tab to display the Ring Definition window. Users are enabled to configure up to 7 different patterns of distinctive ringing as well as basic ringer pattern per node.



Figure 213 Ring Definition

Add a Ring Definition

Follow the steps below to add a ring definition.

1 Select User Interface under the iFXS1 module from the configuration navigation tree.

Table 88 Ring Definition Window Field Description

Fields DescriptionIndex Displays the ring pattern index. The value range is 1-8. 1 refers to

the basic ring pattern.

Definition Displays the ring pattern definition. Pattern of ring cadence is a cycle of ring on and off duration with semicolon. For example, 400;200;400;2000 means 400 ms on, 200 ms off, 400 ms on, 2000 ms off

Pattern Definition shall follow the format as listed below. It shall be a complete cycle of ringing period.

<on 1>:<off 1>,<on 2>:<off 2>, <on 3>:<off 3>, <on 4>:<off 4>


Configuring MG Media 279

2 Click Ring Definition tab.

The Ring Definition Configuration window is displayed as shown in Figure 213.

3 Click <Add>.

The Ring Definition Config window is displayed.

4 Refer to Table 14 to configure the ring pattern.

5 Click <Apply>.

The new added entry is listed in Ring Definition Configuration window.

Configuring MG Media

Configuring VoIP Media From the configuration management navigation tree, select [Node/Shelf (x) /Slot (y):iFXS1/ MG Media], and click the VoIP Media tab to display the VoIP Media Window. Users are enabled to configure IP address of each RTP stream. Refer to Table 89 for field description.



Figure 214 VoIP Media

Configuring Jitter Buffer From the configuration management navigation tree, select [Node/Shelf (x) /Slot (y):iFXS1/ MG Media], and click the Jitter Buffer tab to display the Jitter Buffer Window. Refer to Table 90 for field description.

Table 89 VoIP Media Window Field Description

Fields DescriptionRTP UDP Port Base Address

Displays the IP address of each RTP stream

RTP UDP Number of ports Selects the RTP UDP number of the FXS ports. Possible values are: 24, 48

Echo tail length Selects the echo tail length value. Possible values are 8, 16, 32, and 64.


Configuring MG Media 281

Figure 215 Jitter Buffer

Table 90 Jitter Buffer Window Field Description

Fields DescriptionIndex Displays the jitter buffer entry index for different Codec type

Codec Type Displays the Codec type. Possible values are:

g711ALaw64KAudio,

g711ULaw64KAudio,

g726d32KAudio,

g729dAudio,

7231dAudio

Packet Size

Max Jitter Displays the maximum jitter buffer size for the specified codec type

Min Jitter Displays the minimum jitter buffer size for the specified codec type

Nom Jitter Displays the normal jitter buffer size for the specified codec type



Configuring SIP

Configuring SIP Port From the configuration management navigation tree, select [Node/Shelf (x) /Slot (y):iFXS1/ SIP], and click the SIP Port tab to display the SIP Port Window. Refer to Table 91 for field descriptions.

Figure 216 SIP Port

Priority The priority for the codec type. The value range is 1-5, the lower value refers to the higher priority

Num Channel Displays the number of channels

Bad Channel Displays the number of bad channels

Table 90 Jitter Buffer Window Field Description

Fields Description


Configuring SIP 283

SIP Summary Statistics From the configuration management navigation tree, select [Node/Shelf (x) /Slot (y):iFXS1/ SIP], and click the SIP Summary Statistics tab to display the SIP Summary Statistics Window. The window displays SIP summary statistics information.

Figure 217 SIP Summary Statistics

SIP Supported Methods From the configuration management navigation tree, select [Node/Shelf (x) /Slot (y):iFXS1/ SIP], and click the SIP Supported Methods tab to display the SIP Supported Methods Window. Refer to Table 92 for field descriptions.

Table 91 SIP Port Window Field Description

Fields DescriptionApp Index Displays the application index

SIP Port Displays the port number of SIP register. The default value is 5060.

Transport Protocol Displays the transport protocol



Figure 218 SIP Supported Methods

SIP Methods Statistics From the configuration management navigation tree, select [Node/Shelf (x) /Slot (y):iFXS1/ SIP], and click the SIP Methods Statistics tab to display the SIP Methods Statistics Window. The window displays the SIP method statistics information.

Table 92 SIP Supported Method Window Field Description

Fields DescriptionApp Index Displays the SIP application index

Method Index Displays the method index.

Method Name Displays the method name. Basic methods include INVITE, ACK, CANCEL, OPTIONS, BYE, and REGISTER. Advanced methods depend on service.


Configuring SIP UA 285

Figure 219 SIP Methods Statistics

Configuring SIP UA

General Config From the configuration management navigation tree, select [Node/Shelf (x) /Slot (y):iFXS1/ SIP UA], and click the General Config tab to display the General Config window. Refer to Table 93 for field descriptions.



Figure 220 General Config

Server Table From the configuration management navigation tree, select [Node/Shelf (x) /Slot (y):iFXS1/ SIP UA], and click the Server Table tab to display the Server Table window. Refer to Table 94 for field descriptions.

Table 93 General Configuration Window Field Description

Fields DescriptionHome Domain Enters the name of SIP domain that a SIP UA belongs to. String

up to 128 ASCII characters

SIP Proxy Address Displays the active SIP proxy IP address

SIP Registrar Address Displays the active SIP registrar IP address



Figure 221 Server Table

MG Table From the configuration management navigation tree, select [Node/Shelf (x) /Slot (y):iFXS1/ SIP UA], and click the MG Table tab to display the MG Table window. Refer to Table 95 for field descriptions.

Table 94 General Configuration Window Field Description

Fields DescriptionApp Index Displays the SIP application index

Server Index Displays the server index

Server Function Displays the server function

Server Address Type Displays the server address type

Server Address Displays the server IP address

Server Type Displays the server type



Figure 222 MG Table

User Table From the configuration management navigation tree, select [Node/Shelf (x) /Slot (y):iFXS1/ SIP UA], and click the User Table tab to display the User Table window. Refer to Table 22 for field descriptions.

Table 95 MG Table Window Field Description

Fields DescriptionMG Index Displays the MG index

Host Name Displays SIP home domain name

Port Num Displays the SIP port number

expires Displays the expiring period. The default value is 3600s

Heart Beat Timer Displays the heart beat timer. The value range is 10-1000s. The default value is 60s.

Admin Status Displays the MG administrative status: locked, shutting down, unlocked

Operation Status Displays MG operation status: Up/Down

Auth Password Displays the authentication password which is all SIP users to register to SIP registrar when authentication digest requires

Profile Displays the MGC profile



Figure 223 User Table

Table 96 User Table Window Field Description

Fields DescriptionUser Index Displays the SIP user index

User ID Displays the SIP user ID

Phone Number Displays the phone number

Display Name Displays the SIP user display name. The default is user ID.

Auth ID Displays the SIP authentication ID

Auth Password Displays the SIP authentication password

profile Displays the SIP profile name




7
PROVISIONING - IPXDSL MODULE
This chapter provides configuration procedures for IPxDSL module. Figure 224 shows the main window of the IPxDSL provisioning management.

Figure 224 IPxDSL Provisioning Main Window

IPxDSL module supports the following configurations:


■ Reset

■ Module Summary


■ Module Level Configuration

■ IPxDSL

■ Customized Filter

■ PPPoE Snooping
iAN8K B1000
July 2006 Operations Manual

292 Chapter 7: Provisioning - IPxDSL Module

■ Test Timeout

■ Port Level Configuration

■ WAN Port

■ xDSL

■ ATM

■ Bridge

■ IGMP

■ VLAN

■ Access List

■ QoS




■ xDSL is a joint name for all DSL port including ADSL and SHDSL


IPxDSL module supports module reset at the node level configuration.

Reset IPxDSL modules support both hardware reset and software reset through Netman 4000.

Hardware reset forces download of software image from ICM3 to a line card irrespective of the version on the line card. For virtual modules, this hardware reset is performed after a software reset.

The hardreset forces line module to download software image from ICM3 before reboot. If the corresponding LC software image is not in the ICM3 flash during the hardreset, the reset is applied but no download of software image from ICM3 is required.

The softreset allows line modules to check the software version and software is downloaded when there is a higher version available in ICM 3Flash than the one running on the module. If the corresponding LC software image is not in the ICM3 flash or has equal or lower version, the reset is applied but no download of software image from ICM is required.

A software reset can also be used to recover the module from any software loop conditions or other anomalies. A typical example is; though the card is


Node Level Configuration 293

physically presented in the system but the system does not recognize the module correctly. In such scenarios, a software reset shall be followed by a hardware reset.

Select the node and click the Reset tab to open Figure 225. Click Retrieve to obtain the latest modules information.

Figure 225 Node - Reset

For IPxDSL modules, select the module and click Hard Rest or Soft Reset radio button. Click Reset to begin the reset.



Module Summary IPxDSL modules supports the following options for module summary:

■ Module Information

■ Active Ports

Module Information Module Summary section provides basic information and module location for PCU module.

Expand the node from the navigation tree and select Module Summary to open Figure 226. Click Retrieve to obtain the latest information. Refer to Table 97 for more details.

Figure 226 IPxDSL - Module Summary - Module Information Window

Active Ports Active Ports section provides lists of active ports for IPxDSL modules.

Table 97 ICM3 - Module Summary - Module Information Table



X-Y: Shelf X Slot Y





Expand the node from the navigation tree and select Module Summary. Click Active Ports tab to open Figure 227. Click Retrieve to obtain the latest information. Refer to Table 98 for more details.

Figure 227 IPxDSL - Module Summary - Active Ports Window



Expand the node from the navigation tree and select Shelf to open Figure 228. Click Retrieve to obtain the latest information.

Table 98 ICM3 - Module Summary - Active Ports Table

Field DescriptionModule IPxDSL module type


X-Y: Shelf X Slot Y

Active Ports Active ports list



Figure 228 IPxDSL - Shelf Window

In Figure 228, the physical IPxDSL modules are represented with a board image. For example, slot 2, 4, and 5. Virtual modules are represented with text VACANT followed by its board-name. For example, slot 6 to 13. All other slots are empty slots. Double click on the board image opens the Module Level Configuration.


Table 99 IPxDSL Module Placements Details


IPADSL3A 16 1 - 16 Yes

IPADSL3B 16 1 - 16 Yes



Virtual BoardAssignment

The board assignment feature permits assigning virtual module board to a vacant slot on iAN8K B1000 shelf. The virtual board assignment is supported for all IPxDSL modules. Provisioning can be carried out without the physical module presented in the node.

When adding or removing a virtual board from the system or moving a virtual board to a different slot, the board must be de-assigned or reassigned to the related slot.

From the shelf view, right click on an empty slot in Figure 228. Figure 229 prompts for confirmation. Click Yes to confirm the creation and click OK in Figure 230 after selecting the virtual board type. The new virtual board then appears in the slot with a label VACANT followed by the board_name.

Figure 229 IPxDSL - Virtual Board Assignment Window

Figure 230 IPxDSL - Virtual Board Assignment - Module Type Window

IPADSL6A 16 1 - 16 Yes

IPADSL6B 16 1 - 16 Yes

IPSHDSL3 16 1 - 16 Yes

Table 99 IPxDSL Module Placements Details




To de-assign a slot, right click a virtual board to open Figure 231. Click Yes to confirm the deletion. The virtual board is then removed immediately. The configuration of this virtual board is removed permanently.

Figure 231 IPxDSL - Virtual Board Deassignment Window

When a physical module is inserted to a slot that has virtual configuration, the module assumes all the virtual configuration if the module types are the same.

If the module type does not match the virtual module assigned in the slot, a module type mismatch alarm is raised and the inserted module becomes inoperative. To clear the alarm, de-assigned the virtual module or remove the physical module. A Syslog event is generated along with the alarm.

If a slot is occupied with a physical module, right clicking the slot will not bring up any dialogue box since no board assignment / de-assignment is applicable to this slot. However, double clicking a slot with a physical board will bring up the module configuration window for this board.

Module Level Configuration

The module configuration can be accessed either by selecting a IPxDSL module in the tree view of the device manager window or by double clicking the module in the shelf view. IPxDSL modules supports the following configuration at the slot level:

■ IPxDSL

■ Customized Filter

■ Test Timeout

■ PPPoE Snooping




■ xDSL is a joint name for all DSL port including ADSL and SHDSL

IPxDSL This feature provides the basic module information.


Module Level Configuration 299

Select an IPxDSL module from the tree view to open Figure 232. Click Retrieve to obtain the latest information. Refer to Table 100 for more details.

Figure 232 IPxDSL - IPADSL3A Window

Customized Filter The system allows the user to configure/view various filtering related function at module level.

Semi-Static Forwarding This feature is designed to prevent malicious users from using duplicated MAC address.

When Semi-static forwarding database feature is enabled, all the learnt MAC address entries of DSL ports in forwarding database are treated as static configured entry. These entries are not aged out based on aging timer, and these entries are not overwritten by new traffic. These entries are displayed as dynamic entries in CLI/Netman 4000.

Table 100 IPxDSL - IPxDSL Table

Field Name DescriptionHardware Version The current hardware version for this board.

Software Version The current software version for this board.

Serial Number The serial number for the module.

Uptime The duration that the board is up since the last reset.Read-only.



In the situation that the subscriber needs to switch PC or switch ADSL port, the ADSL line should be reset, which will clear out the old entries for this ADSL port and force the line card to re-learn the address.

Gateway ARP FilterThe IPxDSL module supports Gateway ARP filtering function. When this feature is enabled, the IPxDSL module monitors the ARP request/reply packets on all ADSL ports uplink traffic. The ARP packet is discarded if its "sender protocol address" matches the gateway address configured by the user. The packet discard counter for that bridge port is increased accordingly.

Aging TimerThe aging time is the number of seconds a MAC address is kept in the forwarding database after having received a packet from this MAC address. The entries in the forwarding database are periodically timed out to ensure they won't stay around forever.

The IPxDSL module can set the bridge ageing timer per module configuration. The default timer length is 14400 seconds (4 hours). The valid timer values are a range of 10 seconds to 1 million seconds.

Upstream Multicast FilterIPxDSL module supports a module level "upstream multicast filtering". When upstream multicast filtering is enabled, upstream multicast/broadcast packet is forwarded as shown below:



Figure 233 IPxDSL - Customized Filter - Upstream Multicast Filter Packet Flow - Enabled

When "upstream multicast filtering" is disabled (default), the upstream multicast packets are forwarded as shown below. Broadcast packets are forwarded to all ports.

UpstreamMulticast packet

IsIGMPsnooping

Enabled ?Forward to all

ports

Discard

Upstreammulticastfiltering

broadcastpacket ?

IP or ARPpacket ?

IP Multicastpacket ?

IGMP packet ?

Enabled

Yes No

Yes No No Yes

No

No Yes

Forward per IGMP snoopingrequirement

Disabled

Follow Next Figure

Yes



Figure 234 IPxDSL - Customized Filter - Upstream Multicast Filter Packet Flow - Disabled

ARP TrackingProvides information on the mapping between subscriber's IP address and MAC address. It is implemented by snooping the ARP traffic passing through the module.

Unlike the ARP table used by any IP host, which always provides the up-to-date ARP mapping by sending and receiving ARP packets, the ARP table here provides a history of snooping results. Entries are not aged out. Each entry is uniquely identified by the MAC address filed, the content of the entry remains current so long as the device owning the MAC address remains active. The

Incoming Multicatpacket

IsIGMPsnooping

Enabled ?

Search groupaddress

checkIGMPsnoop

rule

Forward permullticast group

port map

NOYES

Found Not found

Unknown forwardUnknown discard

Discard

IGMP packet?

Forward per IGMPsnooping requirements

Yes No

Forward asbroadcast packet



entry stays in the table after the device becomes inactive. Operators can reset the table to obtain a snapshot of active subscriber and flush out such inactive entries.

The approach not only simplifies the implementation, but it also allows the operator to view the history information for those users that were active on the module and then turned in-active at the time the table is viewed. The size of ARP table is limited to 100 entries. If the table overflows, new entry overwrites old entries by the rule of "first in first out". IP address is unique in the ARP table. New entry with identical IP address overwrites old entry. ARP snooping enables the feature.

Disabling ARP table tracking also resets the ARP table and the content of ARP table is cleared after module reset.

NetBIOS FilterIPxDSL module supports NetBIOS packet filtering function. The NetBIOS filter can either be disabled, applied on uplink only or applied on both directions.

When NetBIOS filter is applied on both directions, packets received from any bridge port are filtered in such way that the NetBIOS packets encapsulated over TCP/UDP or directly carried by IEEE 802.2 LLC are discarded.

When NetBIOS filter is applied on uplink only, only packets received from PVC-mapped bridge ports are filtered.

For the NetBIOS packets carried over TCP/UDP, the filter discards any packets that are sending to the UDP/TCP port 137, 138, 139 or 445.

This helps in preventing users from using applications like Microsoft Network Neighborhood for unauthorized access.

DHCP FilterThis can be used to avoid subscribers getting DHCP service from an unauthorized DHCP server on user ports.

DHCP filters are used to filter DHCP server type packets. Filters can be applied on uplink/downlink or both types of traffic.

■ DHCP uplink filtering

The IPxDSL module supports DHCP uplink filtering function. When DHCP uplink filter is enabled, packets received from PVC-mapped bridge ports are filtered in such way that all DHCP to client packets are discarded.

■ DHCP downlink filtering



The IPxDSL module supports DHCP downlink filtering function. When DHCP downlink filter is enabled, packets transmitted from PVC-mapped bridge ports are filtered in such way that all DHCP to server packets are discarded.

DLF CounterDatabase Lookup Failure (DLF) occurs when the IPxDSL module cannot find a destination MAC address entry, within its database, for the incoming Ethernet frame. The IPxDSL module allows operator to limit the rate of total DLF frames that could be forwarded by the bridge. Within a period of one second, if the total number of DLF frames (including the latest one) is less or equal to the threshold specified by the user, the latest DLF frame are forwarded to all ports excluding the one from which the DLF frame is received; if the total number of DLF frames is larger than the threshold specified by the user, the latest DLF frame is discarded. The discarding is counted in the bridge discarding PM counter.

IGMP SnoopingTraditional Ethernet bridges and switches forward packets with broadcast or multicast destination to each of the interface on the device, excluding the one from which the packets are received. This approach works well for broadcast packets, which are meant to be seen by all hosts on the network. In the case of multicast packets, however, this approach could lead to less efficient use of network bandwidth. Allowing switches to snoop IGMP packet is a creative effort to solve this problem. (IGMP is a protocol used by IP hosts to register their dynamic multicast group membership). The switches use the information in the IGMP packets as they are being forwarded through the switch to determine which segments should receive packets directed to the group address. IGMP snooping allows the bridge device to monitor the IGMP packets and reduces the flooding of IP multicast traffic through the ADSL access line. The main function is to reduce the flooding of IP multicast traffic.

Unrecognized IGMP messages are not used to build membership table and are forwarded to all ports. The IGMP membership reports and leave group messages are forwarded only to the WAN port. IGMP membership report and IGMP leave group message received from the WAN port are discarded. When IGMP membership report is intercepted from PVC-based bridge port the bridge forwards this IGMP report only to the WAN port. The IGMP query (general or group-specific) message received from the WAN port is forwarded to all PVC-based bridge ports. The IPxDSL module monitors the response of IGMP query. If a port fails to respond to IGMP query for three consecutive times, the port is removed from the member list.

If an IGMP query message is received from the PVC-based bridge port, the message is discarded. After, all PVC-based bridge port members leave a group; the group information is removed.

IPxDSL modules support 256 groups per module and 256 groups per port.



The handling of the multicast packet is explained below:

■ When IGMP snoop is disabled, all multicast packets are forwarded as broadcast packets.

■ When IGMP snoop is enabled, incoming downstream-multicast packet, which is not IGMP packets, are forwarded according to a multicast-forwarding table (MAC address based) for corresponding VLAN. The forwarding table is derived from the multicast group membership table learnt via IGMP snooping. If the multicast group MAC address cannot be found in the membership table, The packets are forwarded according to the following:

■ user configured "forward unknown" when enable IGMP snooping, the received packet is forwarded to all ports,

■ user configured "discard unknown" when enable IGMP snooping, the received packet is discarded.

DHCP Option82The DHCP relay agent information option (option 82) enables a Dynamic Host Configuration Protocol (DHCP) relay agent to include information about itself when forwarding client-originated DHCP packets to a DHCP server. The DHCP server can use this information to implement IP address or other parameter-assignment policies.

iAN8K B1000 supports DHCP Option 82 feature on all linecard modules in compliance with IETF RFC3046 with exceptions as explained below. This feature is enabled/disabled on a per module basis. The Option 82 feature is disabled by default.

The Option 82 feature supports agent circuit ID sub-option (code 1) specified in the IETF RFC3046. The circuit ID sub-option follows the format below:

Table 101 Format of Circuit ID Sub-option in DHCP Option 82

Field Length DescriptionSub-option 1 byte 0x01 circuit ID sub-option

Length 1 byte Total length of the port label

Port label 1 - 64 bytes Port label



The Option 82 feature supports agent remote ID sub-option (code 2) specified in the IETF RFC3046. The remote ID sub-option follows the format below:

The Option 82 feature, when enabled, supports the following rules for client-to-server DHCP packets for IPADSL1 modules:

■ For a received DHCP packet, if the GIADDR field is set (i.e., non-zero) and the relay agent information option 82 already presents, iAN8K B1000 forwards the packet along without changing anything.

■ For a received DHCP packet, if the GIADDR field is not set (i.e., zero) and the relay agent information option 82 is already present, iAN8K B1000 overwrites relay agent information option 82 with its own information.

■ For a received DHCP packet, if the relay agent information option 82 is not present, iAN8K B1000 adds the relay agent information option 82 with its own information.

The Option 82 feature, when enabled, supports the following rules for client-to-server DHCP packets for IPADSL3/3A/3B and IPSHDSL/3 modules:

■ For a received DHCP packet, if the relay agent information option 82 is present, IP-DSLMAN overwrites relay agent information option 82 with its own information.

■ For a received DHCP packet, if the relay agent information option 82 is not present, iAN8K B1000 adds the relay agent information option 82 with its own information.

Select an IPxDSL module from the tree view and select Customized Filter tab to open Figure 235. Click Retrieve to obtain the latest information. Configure the

Table 102 Format of Remote ID Sub-option in DHCP Option 82

Field Length DescriptionSub-option 1 byte 0x02 remote ID sub-option

Length 1 byte Total length of the value fields

Vendor ID 4 bytes 0x079d UTStarcom vendor ID

Port Type 1 byte 0x01 ATM port

Version 1 byte 0x01 version 1

VLAN ID 2 bytes Port VLAN ID (0x00 for untagged)

NAS_MAC 6 bytes MAC address of line card Ethernet port

NAS_IP 4 bytes GIADDR (0x00 not used by a bridge)

Node 2 bytes Node ID

Shelf 1 byte Shelf ID

Slot 1 byte Line card slot

Port 1 byte Line card port

VPI 1 byte VPI of port

VCI 2 bytes VCI of port



parameters and click Apply to bring the modification into effect. Refer to Table 103 for more details.

Figure 235 IPxDSL - Customized Filter Window

Table 103 IPxDSL - Customized Filter Table

Field Name DescriptionSemi-static Forwarding When Semi-static Forwarding is enabled, all the learnt MAC address entries in forwarding database are

treated as static configured entry. These entries are not aged out based on aging timer, and these entries are not overwritten by new traffic. These entries are displayed as dynamic entries in Netman forwarding DB display.

Value range: Disabled / Enabled (flush on port down) / Enabled (flush on port lock)

Default: Disabled

Gateway ARP Filter The IPADSL module supports a gateway ARP filtering function. When feature is enabled, the IPADSL module monitors the ARP request/reply packets on all ADSL port uplink traffic. The ARP packet is discarded if its "sender protocol address" matches the gateway address configured by the user. The packet discard counter for that bridge port is increased accordingly.


Default: Disabled

Gateway IP Address IP address of router at the WAN uplink, used with the gateway ARP filter

Value range: valid IP Address



Aging Timer To set the bridge ageing timer. After this interval all the forwarding table entries are flushed.

Value range: 10 - 1 million seconds

Default: 14400 seconds

Unknown VLAN Packet processing for unknown VLAN.

Value range: Discard / Forward

Default: Discard

Read-only

Upstream Multicast Filter By enabling this option, the upstream multicast packet will be forwarded to all the ports if they are IP or ARP broadcast packets. Or they will be forwarded as per IGMP snooping rules if it's a IGMP multicast packet with IGMP snooping enabled.


Default: Disabled

Note: Receipt of any Spanning Tree Protocol (STP) packets from the CPE at the ICM3 will increase the time required to upgrade the ICM3 due to the additional STP packet processing during initialization. Enable this filter during the upgrade process if the time to upgrade the ICM3 seems longer the normal. This prevents any STP packets originating from the CPE from being received at the ICM during its upgrade and initialization.

IGMP Last Query Interval The amount of time the line module waits for a response to an IGMP Group Specific Query the line module has issued after an IGMP Leave message is received from a PVC-based bridge port.


Default: 1

IGMP no-response-leave Query Interval

The amount of time the line module waits for a response to an IGMP Group query the line module has issued when a port fails to respond to a router's query.This is used along with the IGMP no-response-leave query count field.


Default: 2

ILMI Based CPE Management

When enabled, ILMI PVC is created. When disabled, ILMI PVC is deleted automatically.


ARP Tracking Provides information on the mapping between subscriber's IP address and MAC address. It is implemented by snooping the ARP traffic passing through the module. This is for information purpose only and does not effect packet forwarding loopup.


Default: Disabled

NetBIOS Filtering When NetBIOS filter is enabled, incoming packet filters are applied on all ADSL ports and Ethernet port; to filter out (discard) the NetBIOS packets that are encapsulated over TCP/UDP or directly carried by IEEE 802.2 LLC.

Value range: Disabled / Uplink Only / Both Directions






Test Timeout This feature is applicable to "IF Testing."

Select an IPxDSL module from the tree view and select Test Timeout tab to open Figure 236. Click Retrieve to obtain the latest information. Configure the parameters and click Apply to bring the modification into effect.

DHCP Filtering Uplink Filter - When DHCP uplink filter is enabled, an incoming packet filter is applied on all ADSL ports, as a result, all DHCP server to client packets are discarded

Downlink Filter - When DHCP downlink filter is enabled, an outgoing packet filter is applied on all ADSL ports, as the result, all DHCP client to server packets are discarded.

This is used to avoid subscribers getting DHCP service from an unauthorized DHCP server if existing on a user port. This field is applicable only is server is on DSL port.

Value range: Disabled / Uplink Only / Downlink Only / Both Directions


DLF Counter Database Lookup Failure (DLF) occurs when the IPADSL module cannot find an entry, within its database, for the incoming Ethernet frame.This selection allows operator to limit the rate of total DLF frames that could be forwarded (e.g. broadcast) by the bridge. Within a second frame, if the total number of DLF frames (including the latest one) is less or equal to the threshold specified by the user, the latest DLF frame shall be forwarded to all ports excluding the one from which the DLF frame is received; if the total number of DLF frames is larger than the threshold specified by the user, the latest DLF frame shall be discarded. (Note that the discarding is counted in bridge discarding PM counter.

Value range: 10 - 65535DLF frames per sec.

Default: 10

IGMP Snooping IGMP is a protocol used by IP hosts to register their dynamic multicast group membership. The switches uses information in the IGMP packets to determine which segments should receive packets directed to the group address. IGMP snooping allows bridges to monitor IGMP packets and reduces the flooding of IP multicast traffic through the ADSL access line.

Value range: Enabled, forward Unknown / Enabled, discard unknown / Disabled

Default: Disabled

DHCP Option 82 The DHCP relay agent information option (option 82) enables a Dynamic Host Configuration Protocol (DHCP) relay agent to include information about itself when forwarding client-originated DHCP packets to a DHCP server. The DHCP server can use this information to implement IP address or other parameter-assignment policies. iAN8K B1000 supports DHCP Option 82 feature on all linecard modules in compliance with IETF RFC3046 with some exceptions as explained above. This feature is enabled/disabled on a per module basis. When enable, packet policing address assignment for DHCP must be checked on.


Default: Disabled

IGMP Last Query Count Value range: 0 - 3

Default: 1

IGMP no-response-leave Query Count

The number of queries sent by the line modules after a port fails to respond to a router's query.

Value range: 1 - 3

Default: 1

PPPoE Intermediate Agent Enable/disable intercepting PPPoE discovery packets, including PADI, PADO, PADR, and PADS. Upon reception of a PADI or PADR packet sent by the PPPoE client, the Intermediate Agent adds a TAG to the packet sent upstream. The TAG contains the identification of the DSL line on which the PADI or PADR packet was received.






Figure 236 IPxDSL - Test Timeout Window

PPPoE Snooping IPxDSL module can snoop the IP address assignment occurred in PPPoE traffic, including both native PPPoE traffic and PPPoE traffic converted from PPPoA.

Select an IPxDSL module from the tree view and select PPPoE Snooping tab to open Figure 237. Click Retrieve to obtain the latest information. Configure the parameter and click Apply to bring the modification into effect. Click Reset to reset all counters. Refer to Table 104 for more details.



Figure 237 IPxDSL - PPPoE Snooping Window

Port Level Configuration

IPxDSL modules supports the following configuration at the port level:

■ WAN Port

■ xDSL

■ ADSL Port

■ SHDSL Port

■ Line Status

■ Channel Status

■ Previous Status

■ Status Change Time Info

■ Rate Summary

■ Port Label

■ Bit Loading

■ iSmart

■ CPE

Table 104 IPxDSL - PPPoE Snooping Table

Field DescriptionPPPoE IP Assignment Snooping Enable / Disable PPPoE IP address snooping

ACK Counter The counter for received IPCP ACK messages

Discard Counter The counter for discarded IPCP ACK messages



■ ATM

■ ATM VC

■ Traffic Profile

■ Bridge

■ MAC Address Per Port

■ Packet Policing


■ ARP Table

■ Flood Limit

■ IGMP

■ Authentication Parameter

■ CAC

■ Multicast Group

■ Multicast Host

■ VLAN

■ VLAN

■ Ingress Rule

■ VLAN Untag

■ Access List

■ QoS

■ Packet Priority

■ Port Based Priority

■ 802.1p Tag

WAN Port The feature provides basic port information of the WAN port.

Expand an IPxDSL module from the tree view and select WAN to open Figure 238. Click Retrieve to obtain the latest information.



Figure 238 IPxDSL - WAN - WAN Port Window

xDSL IPxDSL modules supports the following configuration at port level of DSL port:

■ ADSL Port

■ SHDSL Port

■ Line Status

■ Channel Status

■ Previous Status

■ Status Change Time Info

■ Rate Summary

■ Port Label

■ Bit Loading

■ iSmart

■ CPE



ADSL PortExpand an IPADSLx module from the tree view and select ADSL to open Figure 239. Click Retrieve to obtain the latest information. Refer to Table 105 for more details.

Figure 239 IPxDSL - ADSL - ADSL Port Window



Select a port and click Assign Profile to open Figure 240. Select a profile and click Ok.

Figure 240 IPxDSL - ADSL - ADSL Port - Assign Profile Window

Select a port and click Lock / Unlock to lock or unlock the port. Click Test to test the port and click Restore to restore the port.

SHDSL PortExpand an IPSHDSL3 module from the tree view and select SHDSL to open Figure 241. Click Retrieve to obtain the latest information. Refer to Table 106 for more details.

Table 105 IPxDSL - ADSL - ADSL Port Table

Field DescriptionPort The index number of the port

Value range: 1 - 24 for IPADSL3A/3B. 1-48 for IPADSL6A/6B

Administrative State The administrative state of the port.

Locked: all configuration is allowed

Unlocked: no configuration allowed except adding new ATM VC

Default: Locked

Operational State The operational state of the port.


Profile The profile assigned to the port

Line Standard The line standard assigned to the port

Power State The power state of the port



Figure 241 IPxDSL - SHDSL - SHDSL Port Window

Table 106 IPxDSL - SHDSL - SHDSL Port Table

Field DescriptionPort The index number of the port

Value range: 1 - 24

Profile The profile assigned to the port

Administrative State Displays whether the port is locked or unlocked for administrative purposes.

Locked: all configuration is allowed

Unlocked: no configuration allowed except adding new ATM VC

Default: Locked



Select a port and click Assign Profile to open Figure 242. Select a profile and click Apply.

Figure 242 IPxDSL - SHDSL - SHDSL Port - Assign Profile Window

Select a port and click Lock / Unlock to lock or unlock the port. Click Lock All / Unlock All to lock or unlock all ports.

Line StatusExpand an IPxDSL module from the tree view and select xDSL. Click Line Status tab to open Figure 243. Click Retrieve to obtain the latest information. Refer to Table 107 for ADSL line status information and refer to Table 108 for SHDSL line status information.

Operational State The operational state of the port.


Actual rate (kbps) The actual rate for the port

Attainable rate (kbps) The possible highest rate for the port

Table 106 IPxDSL - SHDSL - SHDSL Port Table

Field Description



Figure 243 IPxDSL - xDSL - Line Status Window

Table 107 IPxDSL - ADSL - Line Status Table


ATU-C ParametersPort Port Index number

G944 Vender ID G944 Vender ID

System Vendor ID System Vendor ID

Version Number Version Number

Serial Number Serial number

Status ■ No Defect

■ Loss Of Frame

■ Loss Of Signal

■ Loss Of Power

■ Loss of Signal Quality

■ Loss Of Link

■ Data Initialization Failure

■ Configuration Initialization Failure

■ Protocol Initialization Failure

■ No Peer ATU Present

SNR margin (dB) The signal to noise margin in dB on each port

Attainable rate (kbps) The highest possible rate

Output power (dBm) The amount of power output for each ports



Attenuation (dB) The Attenuation on each port

Spectrum Mask Value range: Normal

Header Compression Value range: On / Off

Power State L3: ADSL Port is locked

L3-F: ADSL Port is forced into L3 state

Value range: L0 / L2 / L3 / L3-F

ATU-R ParametersPort Port Index number

Status ■ no Defect

■ loss Of Framing

■ loss Of Signal

■ loss Of Power

■ loss Of Signal Quality



Output power (dBm) The amount of power output for each ports

Attainable rate (kbps) The highest possible rate

Vender ID Vendor ID

Serial number Serial number

Version number Version Number

Table 108 IPxDSL - SHDSL - Line Status Table

Parameter Value RangePort Port Index number

Type Port type

Value range: STU-C / STU-R

Current Status ■ No Defect

■ Power Back Off

■ Device Fault

■ DC Continuity Fault

■ SNR Margin Alarm

■ Loop Attenuation Alarm

■ Loss of Signal Failure Alarm

■ Configuration Initialization Failure

■ Protocol Initialization Failure

■ Neighbor not Present

■ Loopback Active

Table 107 IPxDSL - ADSL - Line Status Table




Channel StatusExpand an IPADSLx module from the tree view and select ADSL. Click Channel Status tab to open Figure 244. Click Retrieve to obtain the latest information. Refer to Table 109 for more details.

Figure 244 IPxDSL - ADSL - Channel Status Window



Operational State

Table 108 IPxDSL - SHDSL - Line Status Table


Table 109 IPxDSL - ADSL - Channel Status Table

Field DescriptionPort Port index number

Value range: 1 - 24 for IPADSL3A/3B, 1 - 48 for IPADSL6A/6B

Type ATU-C / ATU-R

Current Tx Rate (Kbps) Current transmit rate



Previous StatusThe ADSL physical port previous information is the ADSL physical port information before its latest operational state transitions from up to down. This helps troubleshooting the cause of ADSL physical port down and a validation of the ADSL loop

Expand an IPADSLx module from the tree view and select ADSL Port. Click Previous Status tab to open Figure 245. Click Retrieve to obtain the latest information.

Figure 245 IPxDSL - ADSL - Previous Status Window

Previous Tx Rate (Kbps) Previous transmit rate. The previous transmit rate displays data rate achieved in the last successful training. This value is reset to zero after module reset.

Interleave Delay (ms) For interleaved latency only

Value range: 1 / 2 / 4 / 8 / 16 / 32 / 64 ms

CRC Block Length The length of the CRC block

Table 109 IPxDSL - ADSL - Channel Status Table

Field Description



The previous status window displays the following information:

■ ATU-C Status

■ ATU-C Attenuation

■ ATU-C Attenuation

■ ATU-C Output Power

■ ATU-C Attainable Rate

■ ATU-C Line Standard

■ ATU-R SNR Margin

■ ATU-R Output Power

■ ATU-R Attenuation

■ ATU-R Status

■ ATU-R Attainable Rate

■ ATU-R Line Standard

Status Change Time InfoExpand an IPADSLx module from the tree view and select ADSL. Click Status Change Time Info tab to open Figure 246. Click Retrieve to obtain the latest information. Refer to Table 110 for more details.

Figure 246 IPxDSL - ADSL - Status Change Time Info Window



Rate SummaryExpand an IPADSLx module from the tree view and select ADSL. Click Rate Summary tab to open Figure 247. Click Retrieve to obtain the latest information. Refer to Table 111 for more details.

Figure 247 IPxDSL - ADSL - Rate Summary Window

Table 110 IPxDSL - ADSL - Status Change Time Info Table

Field DescriptionPort Port Index

Latest Administrative State Change Duration

The duration between the latest administrative state change and now

Previous before The Last Operational State Duration

The duration between the time of previous before the last operational state change and the time of the last operational state change

Previous Operational State Duration

The duration between the time of current operational state change and the time of the last operational state change

Current State Duration The duration between the time of the late operational state change and the current time



Port LabeliAN8K B1000 supports a customized description label to be attached to each port.

Expand an IPxDSL module from the tree view and select xDSL. Click Port Label tab to open Figure 248. Click Retrieve to obtain the latest information.

Figure 248 IPxDSL - xDSL - Port Label Window

Table 111 IPxDSL - ADSL Rate Summary Table

Field DescriptionPort The number of the port

Value range: 1 - 24 for IPADSL3A/3B, 1 - 48 for IPADSL6A/6B

Type Value range: ATU-C / ATU-R

Attainable Rate Attainable rate (kbps)

Current Rate Current rate (kbps)

Previous Rate Previous rate (kbps). The previous rate displays data rate achieved in the last successful training. This value is reset to zero after module reset.

Configured rate Configured rate (kbps)



Select a port and click Modify in Figure 248 to modify the port. Configure the parameter and click Apply in Figure 249 to take the modification into effect.

Figure 249 IPxDSL - xDSL - Port Label - Modify Window

Bit LoadingiAN8K B1000 displays the ADSL bit-loading map in graphic format. The graph plots number of bits allocated in each tone for upstream direction and for downstream direction. Up to 1024 bins for downstream and 64 bins for upstream is supported.

If the corresponding ADSL port is running in Annex C FBM mode, the graph displays the FEXT bin loading for both upstream and downstream. If the corresponding ADSL port is running in Annex C DBM mode, the graph displays the NEXT bin loading for both upstream and downstream direction in addition to FEXT upstream/downstream bin loading.

Expand an IPADSLx module from the tree view and select ADSL Click Bit Loading tab to open Figure 250. Select a Port ID and click Retrieve to obtain the latest information.



Figure 250 IPxDSL - ADSL - Bit Loading Window

iSmartThis feature configures iSmart feature on specific port(s). iSmart addresses home-port identity issue for PAP-based PPPoE sessions. Home-port refers to the DSL port from which the PPPoE session is originated. In many instances, this information is required by B-RAS (the PPPoE server) to implement features like account binding (bind username-password to particular DSL port). iSmart inserts the home port identity to PAP authentication packet, therefore relays the information to PPPoE server.

User can disable (default) and enable the feature at module level. When enabled, the user name option for each DSL port can be configured to one of the following:

■ Replacement

■ Extension

■ No Modification



When configured to Replacement, PPPoE PAP Authenticate-Request message (RFC 1134) received from the DSL port is modified as following:

■ Replace the peer-ID field with "node_id#shelf_id#slot_id#port_id",

■ where node_id is an integer from 1 to 9999, node ID is provisioned by the user.

■ shelf_id is an integer indexed from 1.

■ slot_id is an integer indexed from 1, slot B is indexed as 17 for R1.x system

■ port_id is an integer indexed from 1

When configured to Extension, PPPoE PAP Authenticate-Request message (RFC 1134) received from the DSL port is modified as following:

■ Replace the peer-ID field with "node_id#shelf_id#slot_id#port_id#old_peer_id",

■ where node_id is an integer from 1 to 9999, node ID is provisioned by the user.

■ shelf_id is an integer indexed from 1.

■ slot_id is an integer indexed from 1, slot B is indexed as 17.

■ port_id is an integer indexed from 1

■ and old_peer_id is the peer ID field in the original received packet.

When configured to No Modification, PPPoE PAP Authenticate-Request message (RFC 1134) received from the DSL port is not modified.

Expand an IPxDSL module from the tree view and select xDSL. Click iSmart tab to open Figure 251. Click Retrieve to obtain the latest information. Configure the parameters and click Apply to take the modification into effect.



Figure 251 IPxDSL - xDSL - iSmart Window

CPEThe ILMI Based CPE Management in Customized Filter must be enabled. "Error in retrieving CPE information" is prompted if not enabled. The ILMI PVC is created when ILMI-based CPE management is enabled. It’s automatically removed when CPE management is disabled.

IPxDSL module allows management system to manage remote ADSL CPE via SNMP. SNMP is carried between ADSL ATU-C and ATU-R over ILMI PVC (VPI 0, VCI 16). Community string is used to differentiate the SNMP message intended for line module and the SNMP message intended for CPE.



The content of the SNMP message is transparent to line module. Line module is only responsible for forwarding SNMP between CPE and management system.

Expand an IPADSLx module from the tree view and select ADSL Click CPE tab to open Figure 252. Click Retrieve to obtain the latest information. Refer to Table 112 for more details.

Figure 252 IPxDSL - ADSL - CPE Window



Select a port and click Modify to open Figure 253. Configure the parameters and click Apply to take the modification into effect.

Figure 253 IPxDSL - ADSL - CPE - Modify Window

ATM iAN8K B1000 supports encapsulation layer conversion between PPPoA and PPPoE on line card modules. The PPPoA is compliant with IETF RFC2364 and the PPPoE is compliant with IETF RFC2516. The PPPoA to PPPoE conversion is supported on a per VC basis. Each VC with PPPoA to PPPoE conversion enabled requests its own PPPoE session ID.

IPxDSL module supports a maximum of 8 PVCs including the PVC used by CPE management, if any.

IPxDSL module supports the following ATM configuration options:

■ ATM VC

■ Traffic Profile

Table 112 IPxDSL - ADSL - CPE Table

Field DescriptionPort Port index

CPE Management Manageable: when ADSL admin status is UP and CPE remote management capability is supported by remote CPE.

Non-manageable: when ADSL admin status is down or when remote management capability is not supported by remote CPE.

Value range: Manageable / Not manageable

Auto Configuration Value range: Allowed / Not Allowed

Local Configuration Index Local Configuration Index

Serial Number CPE serial number



ATM VCExpand an IPxDSL module module from the tree view and select ATM to open Figure 254. Click Retrieve to obtain the latest information. Refer to Table 113 for more details.

Figure 254 IPxDSL - ATM - ATM VC Window

Table 113 IPxDSL - ATM - ATM VC Encapsulation Table

Multiplexing Setting Displayed Encapsulation MethodVC Multiplexing for Bridge PDU VC-mux Bridge

VC Multiplexing for PPPoA (convert to PPPoE) VC-mux PPPoA

LLC Multiplexing for Bridge PDU LLC-mux Bridge



Click Add in Figure 254 to create a new entry. Configure the parameters and click Apply in Figure 255.

Figure 255 IPxDSL - ATM - ATM VC - Add Window

Select an entry and click Delete in Figure 254 to remove the entry.

Traffic ProfileNote: Configure the packet priority on WAN port after configure the traffic profiles.

LLC Multiplexing for PPPoA (convert to PPPoE) LLC-mux PPPoA

Auto detection (PPPoA to PPPoE conversion enabled)

or

Auto detection (PPPoA to PPPoE conversion disabled)

Based on detection results:

■ LLC-mux PPPoA

■ LLC-mux Bridge

■ VC-mux Bridge

■ VC-mux PPPoA

■ Unknown

■ In-detection

LLC- auto detection (PPPoA to PPPoE conversion enabled)

Based on detection results:

■ LLC-mux PPPoA

■ LLC-mux Bridge

■ Unknown

■ In-detection

Table 113 IPxDSL - ATM - ATM VC Encapsulation Table

Multiplexing Setting Displayed Encapsulation Method



iAN8K B1000 supports traffic management profile on each DSL channel. One channel is supported for each DSL port. By default, the default profile, tm-default, is assigned to all ports. Refer to Table 114 for more details.

Expand an IPxDSL module. Select ATM VC and click Traffic Profile tab to open Figure 256. Click Retrieve to obtain the latest information.

Table 114 IPxDSL - Traffic Profile - Modification Table

TM profile is assigned

port adm (locked/unlocked) port ops (up/down)

re-assign? yes yes

modify? no no

deleted? no no

TM profile is not assigned

port adm (locked/unlocked) port ops (up/down)

re-assign? yes yes

modify? yes yes

deleted? yes yes



Figure 256 IPxDSL - ATM - Traffic Profile Window

Select a port and click Assign Profile to assign traffic profile in Figure 257. Select the profile and click Ok to apply the profile.

Note: Refer to Profile Menu - Traffic Management Profile for profile configuration.



Figure 257 IPxDSL - ATM - Traffic Profile - Assign Profile Window

Bridge Refer to the following sections for Bridge configuration:

■ MAC Address Per Port

■ Packet Policing


■ ARP Table

■ Flood Limit

MAC Address Per PortThe IPxDSL module can limit the number of MAC addresses learnt at each IPxDSL port. If the number of MAC addresses learnt has reached the limit defined, any incoming packets with unknown MAC addresses are discarded. When learning is disabled, the source MAC address of received packet is not added to the forwarding database.

The static entry added to a bridge port is not counted towards the number of MAC address learnt on each xDSL port.

Expand an IPxDSL module and select Bridge and to open Figure 258. Click Retrieve to obtain the latest information. Refer to Table 115 for more details.



Figure 258 IPxDSL - Bridge - MAC Address Per Port Window

Select a port and click Modify in Figure 258 to modify the port. Configure the parameter and click Apply in Figure 259 to take the modification into effect.

Table 115 IPxDSL - Bridge - MAC Address Per Port Table

Field DescriptionPort Port index

MAC Address Limit The number source MAC addresses allowed to learn at each port

Value range: 0 - 10 / Infinite / Disable learning

Default: 2



Figure 259 IPxDSL - Bridge - MAC Address Per Port - Modify Window

Packet PolicingPacket Policing comprises of 2 protocol filters.

■ ARP Filter:

■ When enabled, the IPxDSL module monitors the ARP request/reply packets on all ADSL ports uplink traffic. The ARP packet is discarded unless its sender protocol address matches any of the IP address assigned to this ADSL port or it is 0.0.0.0. The packet discard counter for that bridge port is increased accordingly.

■ When enabled, the IPxDSL module monitors the ARP request/reply packets received from PVC-based bridge port. The ARP packet is discarded if its target protocol address matches any of the IP address assigned to this port. The packet discard counter for that bridge port is increased accordingly.

■ IP source address Filter: When source address enforcement is enabled, the IPxDSL module snoops the uplink traffic on all ADSL port. If the packet is an IP packet with source IP address matching one of the IP addresses assigned to its ADSL port, or if the source IP address is 0.0.0.0, the packet is forwarded normally, otherwise the IP packet is discarded. Non-IP packets are forwarded normally. If no IP address has been assigned to the ADSL port, only packet with source address as 0.0.0.0 is forwarded.

Packet Policing Setup Expand an IPxDSL module. Select Bridge and click Packet Policing tab to open Figure 260. Click Retrieve to obtain the latest information. Configure the parameters and click Apply to bring the modification into effect. Refer to Table 116 for more information.



Figure 260 IPxDSL - Bridge - Packet Policing - Packet Policing Setup Window

Table 116 IPxDSL - Bridge - Packet Policing - Packet Policing Setup Table

Field DescriptionADSL Port Select the appropriate ADSL Port for packet policing setup.

Protocol Filter

ARP When ARP enforcement is enabled IPADSL module monitors the ARP request/reply packets on all ADSL port uplink traffic. The ARP packet is discarded unless its "sender protocol address" matches any of the IP address assigned to this ADSL port or it is 0.0.0.0. The packet discard counter for that bridge port is increased.

IP When source address enforcement is enabled, the IPADSL module snoops the uplink traffic on all ADSL port. If the packet's source IP address matches one of the IP address assigned to its ADSL port, or if the source IP address is 0.0.0.0, the packet is forwarded, otherwise the IP packet is discarded. Non-IP packets are forwarded normally. If no IP address has been assigned to the ADSL port, only packet with source address as 0.0.0.0 are forwarded

IP Address Assignment

DHCP The IPADSL module has an internal database tracking the legitimate IP addresses assigned to each ADSL port. With the DHCP option database entry is dynamically created by the DHCP tracking feature. This is also used to add in DHCP option 82 information.The dynamically DHCP assigned entries are shown as "Dynamic" entries.

Static The IPADSL module has an internal database tracking the legitimate IP addresses assigned to each ADSL port. The manually entered IP addresses are displayed in the table as "Static" entries.



IP Address Summary Expand an IPxDSL module. Select Bridge and click Packet Policing tab. Select to IP Address Summary tab to open Figure 261. Refer to Table 117 for more details.

Figure 261 IPxDSL - Bridge - Packet Policing IP Address Summary Window

Click Add to create a new entry. Select an entry and and click Delete to remove the entry.

Forwarding DatabaseIPxDSL module supports semi-static forwarding database feature. When flush on port down is enabled, dynamic entries in forwarding database are not aged out based on aging timer. The dynamic entries are only flushed out when bridge

Table 117 IPxDSL - Bridge - Packet Policing IP Address Summary Table

Field Name DescriptionPort Port ID number.

IP Address IP address of the port.

Type Port Type

Value range: Static / Dynamic



port becomes operationally disabled (that is when underline xDSL port or WAN port goes down). When flush on port lock is enabled, dynamic entries in forwarding database are not aged out based on aging timer nor flushed out when bridge port becomes operationally disabled (that is when underline xDSL port or WAN port goes down). The dynamic entries are flushed out only when corresponding DSL port is administratively locked.

For both cases, the incoming Ethernet packet is discard if its source MAC address existed in forwarding database under a bridge port different from the port it is received from.

In Shared VLAN Learning (SVL) scenario, each FWDB entry is distinguished by MAC address. In Independent VLAN Learning (IVL) scenario, each FWDB entry is distinguished by the combination of MAC address and VLAN ID. That is for IVL, if same MAC address were learnt in two separate VLANs, they are counted as two entries for MAC address per port purpose.

Expand an IPxDSL module. Select Bridge and click Forwarding Database tab to open Figure 262. Click Retrieve to obtain the latest information. Refer to Table 118 for more details.

Figure 262 IPxDSL - Bridge - Forwarding Database Window



Select a VLAN from the VLAN ID drop down menu to display the corresponding entry for the VLAN selected.

Click Add in Figure 262 to create a new entry. Configure the parameters and click Apply in Figure 263. Refer to Table 119 for more details.

Figure 263 IPxDSL - Forwarding Database - Add Window

Select a static entry from Figure 262 and click Delete to remove the entry.

Note: Only static FDB entries may be deleted.

Table 118 IPxDSL - Bridge - Forwarding Database Table

Field Name DescriptionVLAN ID VLAN ID number

Type Static - Created by user. Does not get flushed out

Dynamic - Created automatically and gets flushed out based on the configuration

MAC address Destination MAC Address (L2 info.)

Port WAN Port or ADSL Ports where the MAC address in consideration is active. (L1 info.)

Table 119 IPxDSL - Forwarding Database - Add Table

Field DescriptionVLAN VLAN ID.

Unicast MAC Address Source MAC Address (L2 info.)

Value range: valid MAC address

Forwarding Port To discard or forward packets for designated destination MAC address

Value range: Discard / WAN Port / ADSL Port



ARP TableAddress Resolution Protocol (ARP) provides information on the mapping between subscriber's IP address and MAC address. It is implemented by snooping the ARP traffic passing through the module.

Unlike the ARP table used by any IP host, which always provides the up-to-date ARP mapping by sending and receiving ARP packets, the iAN8K B1000 ARP table provides a history of snooping results. Entries are not aged out. Each entry is uniquely identified by the MAC address filed and the content of the entry remains current so long as the device owning the MAC address remains active. The entry stays in the table after the device becomes inactive. Operators can reset the table to obtain a snapshot of active subscriber and flush out such inactive entries. These entries are information only and do not effect packet forwarding.

This approach not only simplifies the implementation, but it also allows the operator to view the history information for those users who were active on the module and then became in-active at the time the table is viewed. The size of ARP table is limited to 100 entries. If the table overflows, new entry overwrites old entries by the rule of "first in first out."

Expand an IPxDSL module. Select Bridge and click ARP Table tab to open Figure 264. Click Retrieve to obtain the latest information. Click Reset to reset all the statistics. Refer to Table 120 for more details.



Figure 264 IPxDSL - Bridge - ARP Table Window

Flood LimitWhen broadcast rate limit or multicast rate limit is provisioned to a value, IPxDSL modules count the incoming broadcast packets for each bridge port (exclude WAN port) in every given 1-second period. Incoming packets within the provisioned limit are forwarded and incoming packets exceed the provisioned limit are discarded. Packets discarded are counted in the Incoming packets discard parameter on the port from which the discarded packet was received.

Expand an IPxDSL module. Select Bridge and click Flood Limit tab to open Figure 265. Click Retrieve to obtain the latest information. Configure the parameters and click Apply to take the modification into effect.

Table 120 IPxDSL - Bridge - ARP Table

Field DescriptionPort The bridge port index number

IP Address The IP address of a subscriber

MAC Address The MAC address of a subscriber



Figure 265 IPxDSL - Bridge - Flood Limit Window

IGMP Refer to the following section for IGMP configuration:

■ Authentication Parameter

■ CAC

■ Multicast Group

■ Multicast Host

Authentication ParameterThis feature applies for video service.

Expand an IPxDSL module and select IGMP and to open Figure 266. Click Retrieve to obtain the latest information.



Figure 266 IPxDSL - IGMP - Authentication Parameters Window

Select an entry and click Modify. Configure the parameter and click Apply in Figure 267.

Figure 267 IPxDSL - IGMP - Authentication Parameters - Modify Window

CACiAN8K B1000 reserves band width for other traffic if oversubscription threshold input less than 100%.



Expand an IPxDSL module. Select IGMP and click CAC tab to open Figure 256. Click Retrieve to obtain the latest information. Modify the parameters and click Apply to take the modification into effect.

Figure 268 IPxDSL - IGMP - CAC Window

Multicast GroupExpand an IPxDSL module. Select IGMP and click Multicast Group tab to open Figure 269. Click Retrieve to obtain the latest information. Refer to Table 121 for more details.



Figure 269 IPxDSL - IGMP - Multicast Group Window

Multicast HostExpand an IPxDSL module. Select IGMP and click Multicast Host tab to open Figure 270. Click Retrieve to obtain the latest information. Refer to Table 122 for more details.

Table 121 IPxDSL - IGMP - Multicast Group Table

Field Name DescriptionIP Address IP address of a multicast group.

VLAN ID VLAN ID number.

Port Port ID number.



Figure 270 IPxDSL - IGMP - Multicast Host Window

VLAN VLAN is a networking technology that allows networks to be segmented logically. With VLAN the logical topology is independent of the physical topology of the network nodes. This isolation reduces unnecessary traffic flooding and leads to better network performance. The highlights of VLAN feature on iAN8K B1000 are:

■ Supports up to 256 Virtual LANs (VLANs). Each VLAN has a VLAN name, a VLAN ID and a list of bridge ports that are in the VLAN.

■ A bridge port can be placed in one and only one VLAN as un-tagged port. However a bridge port is allowed in multiple VLANs as a tagged port.

■ Within each VLAN, the IPxDSL module supports user isolation feature. When enabled, packets received from ADSL port are not forwarded to any other ADSL port. When disabled, packets received from ADSL port are forwarded

Table 122 IPxDSL - IGMP - Multicast Host Table

Field Name DescriptionIP Address IP address of a multicast group.

VLAN ID VLAN ID number.

Port Port ID number.

Host IP Address IP address of a multicast host.



normally (e.g. based on bridge forwarding database and VLAN configuration).

■ When a VLAN is deleted, all untagged bridge ports originally assigned to the VLAN return to default VLAN as untagged port, the tagged ports are removed, and Netman provides a warning for the delete action.

The VLAN association of incoming packets is determined by, in the order of:

■ 802.1q tag, if tagged. Incoming packets with VLAN ID set as 0 is considered as untagged packets.

■ VLAN of which the incoming port is associated with as untagged port, if packets are un-tagged.

If an incoming packet is tagged with a unknown VLAN tag, IPxDSL modules always discard these packets.

If an incoming packet is tagged with a VLAN for which the port is not provisioned to be part of, the IPxDSL modules allow user to configure the ingress rule to decide whether to discard the packet or to forward the packet based on the tag. Ingress rule could be configured for each bridge port. The valid options are:

■ Admit only configured VLAN

■ Admit all VLAN (default)

Refer to the following for VLAN configuration:

■ VLAN

■ Ingress Rule

■ VLAN Untag

VLANExpand an IPxDSL module and select VLAN and to open Figure 271. Click Retrieve to obtain the latest information.



Figure 271 IPxDSL - VLAN - VLAN Window

Click Add or select a port and click Modify in Figure 271. Figure 272 prompts for VLAN configuration. Configure the parameters and click Apply to bring the modification into effect.



Figure 272 IPxDSL - VLAN - VLAN - Add Window

Select a port and click Delete in Figure 271 to remove the entry,

Ingress RuleExpand an IPxDSL module. Select VLAN and click Ingress Rule tab to open Figure 273. Click Retrieve to obtain the latest information.



Figure 273 IPxDSL - VLAN - Ingress Rule Window

Select a port and click Modify in Figure 273. Figure 274 prompts for VLAN configuration. Configure the parameters and click Apply to bring the modification into effect.

Figure 274 IPxDSL - VLAN - Ingress Rule - Modify Window



VLAN UntagExpand an IPxDSL module. Select VLAN and click VLAN Untag tab to open Figure 275. Click Retrieve to obtain the latest information.

Figure 275 IPxDSL - VLAN - VLAN Untag Window

Select a port and click the Enable or Disable radio button to enable or disable VLAN untag. Click Apply to bring the modification into effect.

Access List IP-iAN8K B1000 supports maximum of 512 ACL entries on the node.

Expand an IPxDSL module and select Access List to open Figure 276. Click Retrieve to obtain the latest information.



Figure 276 IPxDSL - Access List Window

Select a port and click Edit in Figure 276. Figure 277 prompts for the inbound access list profile configuration. Click Outbound tab to configure for outbound access list.



Figure 277 IPxDSL - Access List - Edit Window

Click Up/Down in Figure 277 to adjust the priority order of the profiles.

Click New in Figure 277 to open access list profiles. Select a profile and click OK in Figure 278 to confirm. Click Apply in Figure 277 to bring the modification into effect.



Figure 278 IPxDSL - Access List - Edit - New Window

Note: After applying customized access list profiles to the ports, the user must create and apply another access list profile that admits all packets. Applying this access list profile will grant access permission to all other packets.

Note: Apply command takes modification into effect immediately. However, it does not save the modification. Before exiting device manager, the user must save the modification with Save Configuration command in order to keep the modification for future usage

QoS IPxDSL modules support traffic prioritization based on the following user-configurable classification criteria:

■ Diffserv code point (DSCP) (bit 0 to bit 5 of TOS byte)

■ TOS bits (bit 3 to bit 6 of TOS byte)

■ Ether type

■ 8021.q tag (VLAN ID)

■ Source IP address,

■ Destination IP address

■ IP Protocol type

■ Source TCP port

■ Source UDP port

■ Destination TCP port

■ Destination UDP port

Priority queuing is supported to expedite forwarding of higher priority packets. The priority queuing is handled based on the priority of incoming packets determined by classifying the packets, applying pre-assigned priority on the



receiving ports, or inspecting the 802.1p tagged priority of the packets, queuing to the appropriate queue based on assigned priority and dispatching the packet from the queue. There are 8 upstream priorities (0 - 7) and 4 downstream priority queues (traffic classes) (0 - 3) in the line card modules.

The packet is placed into proper egress queue based on the priority assigned on packet per "priority to traffic class mapping " table specified in Table 8-2 of IEEE 802.1Q. The table has been extracted below for convenience. For traffic queued at the WAN port (Upstream Traffic) column with 8 traffic classes is applied. For traffic queued on the ADSL port (Downstream Traffic), column with 4 traffic classes is applied.

The rationale behind the choice of values shown in this table is discussed in Annex H.2 of ISO/IEC 15802-3. A consequence of the mapping shown is that frames carrying the default user priority are given preferential treatment relative to user priority 1 and 2 in Bridges that implement four or more traffic classes.

If multiple user rules are applied, the first match determines packet priority. User can arrange rule orders on bridge port.

If none of the above prioritization criteria is applicable (when no user rule is configured; port-based is disabled and incoming packet is not 802.1p tagged), packet is assigned to priority 0.

The line card module supports scheduling with strict priority queuing. Packets are retrieved from queues for egress transmission based on the strict order of queue priority.

For upstream traffic, a configuration parameter can be used to enable/disable the marking of the 802.1p tag. When 802.1p tag marking is enabled, every

Table 123 IPxDSL- QoS - Recommended User Priority to Traffic Class Mappings

Number of Available Traffic Classes

1 2 3 4 5 6 7 8

User Priority

0 (Default) 0 0 0 1 1 1 1 2

1 0 0 0 0 0 0 0 0

2 0 0 0 0 0 0 0 1

3 0 0 0 1 1 2 2 3

4 0 1 1 2 2 3 3 4

5 0 1 1 2 3 4 4 5

6 0 1 2 3 4 5 5 6

7 0 1 2 3 4 5 6 7



packet on the WAN outbound traffic has to be forwarded with an 802.1p tag value set according to the following mapping:

The line card DSL ports can be configured with a fixed line rate mode for support of rate limiting on a per port basis. The line rates can be configured with minimum rate and maximum rate for both upstream and downstream directions. The fixed line rates enforce an upper bandwidth ceiling on all the traffic passing through the ports. This mechanism is applied with the assumption that every port, as a result of its auto-negotiation, can achieve higher bandwidth than the intended maximum line rate.

IPxDSL modules support strict priority based scheduling mechanism.

Refer to the following section for IPADSL3/3A/3B and IPSHDSL3 QoS configuration:

■ Packet Priority

■ Port Based Priority

■ 802.1p Tag

Packet PriorityExpand an IPxDSL module and select QoS to open Figure 279. Click Retrieve to obtain the latest information.

Table 124 IPxDSL - QoS - 802.1p Tag Marking on Line Card

Queue index Marked 802.1p Tag Value0 1

1 2

2 0

3 3

4 4

5 5

6 6

7 7



Figure 279 IPxDSL - QoS - Packet Priority Window

Select a port and click Edit in Figure 279. Figure 280 prompts for rule index selection. Select the rule and click Apply to confirm.

Figure 280 IPxDSL - QoS - Packet Priority - Edit Window



Click Add in Figure 280 and Figure 281 prompts for rule addition. Select the rule and click Ok to add the rules.

Figure 281 IPxDSL - QoS - Packet Priority - Edit - Add Window

Port Based PriorityIPxDSL module supports port-based priority for ADSL ports. When enabled, user can provision a priority (0-7) for each PVC-based bridge port. The priority of the packet received from PVC-based bridge port is assigned as the priority provisioned for the incoming port.

Expand an IPxDSL module. Select QoS and click the Port Based Priority to open Figure 282. Click Retrieve to obtain the latest information.



Figure 282 IPxDSL - QoS - Port Based Priority Window

Select a port and click Edit in Figure 282. Figure 283 prompts for priority selection. Select the priority and click Apply to confirm.

Figure 283 IPxDSL - QoS - Port Based Priority - Modify Window



802.1p TagIPxDSL modules support re-generation of the 802.1p tag. When enabled, the module regenerate the 802.1p tag for packets received from ADSL port. The new 802.1p tag value is set to the priority value assigned to the packet by the line module.

The tag regeneration only tries to overwrite the packet received from ADSL port, not the packet received from WAN port. The packets received from ADSL port can be transmitted out via WAN port or via ADSL port. In both scenarios, its priority tag will be regenerated.

The 802.1p tag operations are listed in Table 125:

Expand an IPxDSL module. Select QoS and click the 802.1p Tag to open Figure 284. Click Retrieve to obtain the latest information. Configure the parameter and click Apply to bring the modification into effect.

Table 125 IPxDSL - QoS - Port Based Priority - Tag Operation Table

Incoming Port Destination PortOutgoing Port VLAN Tag Configuration Outgoing 802.1p tag

ADSL port WAN port tagged Contain 802.1p tag, tag value is the priority of the packet

ADSL port WAN port untagged No 802.1p tag

WAN port ADSL port tagged Contain 802.1p tag, tag value is the same as incoming packet's priority tag (0, if incoming packet is untagged)

WAN port ADSL port untagged No 802.1p tag

ADSL port ADSL port tagged Contain 802.1p tag, tag value is the priority of the packet

ADSL port ADSL port untagged No 802.1p tag

Any port Any Port tagged Contain 802.1p tag, tag value is the same as incoming packet's priority tag (0, if incoming packet is untagged)

Any port Any port untagged No 802.1p tag



Figure 284 IPxDSL - QoS - 802.1p Tag Window




8
PERFORMANCE MANAGEMENT
Performance Management supports monitoring statistical performance counters for the Bridge ports, Ethernet and ADSL interfaces in iAN8K B1000 system. Figure 285 shows the main window of the Performance management.

Figure 285 Performance Management Main Window

iAN8K B1000 supports performance management for the following modules:

■ ICM3 Module

■ IPADSLx Module

■ IPSHDSL3 Module

Note: Both physical and virtual boards are displayed in the tree view of the performance section. However, only the physical boards contains meaningful data. The report for all virtual boards displays null or 0 value in the fields.


366 Chapter 8: Performance Management

ICM3 Module The ICM3 module supports the following statistical counters reports for each port including Internal 1 - 16, FE1 - 4 and GE1 - 2.

■ Ethernet PM

■ General Counters

■ Error Counters

■ Traffic Load

■ Bridge PM

■ Control

■ 5 Minutes Report


The performance management allows user to reset the Ethernet counters on an individual Ethernet port or on all the Ethernet ports. The counter resets under the following conditions:

■ User manually resets the counters for the port

■ User administratively locks the port (Internal ports are never administratively locked. Therefore the counters can only be reset manually by the user).

Note: All counters are free run counters and the counter value wraps after exceeding the limit (32 bit value).

Ethernet PM ICM3 module supports the following Ethernet performance reports:

■ General Counters

■ Error Counters

■ Traffic Load

General CountersExpand the active ICM3 module from the tree view and select Ethernet PM to open Figure 286.

Select a port and click Reset to reset the counts for a specific port. Click Reset All to reset all counts for all ports. Click Retrieve to obtain the latest information. Refer to Table 126 for more details.


ICM3 Module 367

Figure 286 ICM3 - Ethernet PM- General Counters

Table 126 ICM3 - Ethernet PM - General Counters Table

Field DescriptionPort ID Internal 1 - Internal 16 / FE 1 - FE 4 / GE 1 - GE 2

Rx total octets Counter of total octets for incoming traffic

Rx unicast frames Counter of unicast frames for incoming traffic

Rx multicast frames Counter of multicast frames for incoming traffic

Rx broadcast frames Counter of broadcast frames for incoming traffic

Rx pause frames Counter of pause frames for incoming traffic

Tx total octets Counter of total octets for outgoing traffic

Tx unicast frames Counter of unicast frames for outgoing traffic

Tx multicast frames Counter of multicast frames for outgoing traffic

Tx broadcast frames Counter of broadcast frames for outgoing traffic



Error CountersExpand the active ICM3 module from the tree view and select Ethernet PM. Click Error Counters tab to open Figure 287.

Select a port and click Reset to reset the counts for a specific port. Click Reset All to reset all counts for all ports. Click Retrieve to obtain the latest information. Refer to Table 127 for more details.

Tx pause frames Counter of pause frames for outgoing traffic

Rx 64 bytes Counter of 64 bytes for incoming traffic

Rx 65 to 127 bytes Counter of 65 to 127 bytes for incoming traffic


Rx 256 to 511 bytes Counter of R256 to 511 bytes for incoming traffic



Table 126 ICM3 - Ethernet PM - General Counters Table

Field Description


ICM3 Module 369

Figure 287 ICM3 - Ethernet PM - Error Counters

Table 127 ICM3 - Ethernet PM - Error Counters Table

Parameter Value RangePort ID Internal 1 - Internal 16 / FE 1 - FE 4 / GE 1 - GE 2

Rx Undersize Frames Counter of undersize frames for incoming traffic

Rx Oversize Frames Counter of oversize frames for incoming traffic

Rx Fragments Counter of fragments for incoming traffic

Rx Jabber Frames Counter of jabber frames for incoming traffic

Rx FCS Error Frames Counter of FCS error frames for incoming traffic

Rx Alignment Error Frames Counter of alignment error frames for incoming traffic



Traffic LoadExpand the active ICM3 module from the tree view and select Ethernet PM. Click Traffic Load tab to open Figure 288. Click Retrieve to obtain the latest information. Refer to Table 128 for more details.

Figure 288 ICM3 - Ethernet PM - Traffic Load

Table 128 ICM3 - Ethernet PM - Traffic Load Table

Parameter Value RangePort ID Internal 1 - Internal 16 / FE 1 - FE 4 / GE 1 - GE 2

Traffic Load (kbps) Traffic load in kbps

Traffic Load (%) Traffic load


ICM3 Module 371

Bridge PM ICM3 module supports the following Bridge performance reports:

■ Control



ControlExpand the active ICM3 module from the tree view and select Bridge PM to open Figure 289. Click Retrieve to obtain the latest information. Configure the parameters and click Apply to take the modification into effect. Refer to Table 129 for more details.

Figure 289 ICM3 - Bridge PM - Control

Table 129 ICM3 - Bridge PM - Control Table

Parameter Value RangeBridge Port 5 Minutes PM Monitoring

Disable / enable 5 minutes performance monitoring for the bridge port

Bridge Port 15 Minutes PM Monitoring


History Capacity History buffer size



5 Minutes ReportExpand the active ICM3 module from the tree view and select Bridge PM. Click 5 Minutes Report tab to open Figure 290.

Click Retrieve to obtain the latest information. Click Reset to reset the statistics listed in the Current Interval section. Previous Intervals section lists the history statistics. Refer to Table 130 for more details.

Figure 290 ICM3 - Bridge PM - 5 Minutes Report

Table 130 ICM3 - Bridge PM - 5 Minutes Report Table

Parameter Value RangePort List Internal 1 - Internal 16 / FE 1 - FE 4 / GE 1 - GE 2

Time Elapse / End Time Period of time for collecting the error

Valid Validation of the data

Incoming Octets The number of octets that have been received by the bridge port from its segment

Incoming unicast frames The number of unicast packets received from this bridge segment


IPADSLx Module 373

15 Minutes Report15 Minutes Report shares identical parameters with 5 Minutes Report. Please refer to 5 Minutes Report for more details.

IPADSLx Module IPADSLx modules support the following performance reports:

■ ATM PVC

■ Bridge Port

■ Bridge PM Control

■ Bridge



■ WAN Port

■ Threshold Controls

■ 15 Minutes

■ 24 Hours

■ ADSL Port

■ ADSL 15 Minutes Summary

■ ADSL 24 Hours Summary


■ ATUC 15 Minutes

■ ATUC 24 Hours

■ ATUR 15 Minutes

■ ATUR 24 Hours

■ Channel Level

Incoming multicast frames The number of multicast packets received from this bridge segment

Incoming broadcast frames The number of broadcast packets received from this bridge segment

Outgoing Octets The number of octets that have been transmitted by this port to its segment.

Outgoing unicast frames The number of unicast packets that has been transmitted through this bridge segment

Outgoing multicast frames The number of multicast packets that has been transmitted through this bridge segment

Outgoing broadcast frames The number of broadcast packets that has been transmitted through this bridge segment

Table 130 ICM3 - Bridge PM - 5 Minutes Report Table




ATM PVC Select an IPADSLx module from the tree view to open ATM PVC report shown in Figure 291.

Select a port and click Reset to reset the counters for the port. Click Retrieve to obtain the latest performance report. Refer to Table 131 for more details.

Figure 291 IPADSLx - ATM PVC

Bridge Port IPADSLx modules support the following performance reports for Bridge port:

■ Bridge PM Control

■ Bridge


Table 131 IPADSLx - ATM PVC Table

Parameter DescriptionPort Port type: Bridge port / WAN port / ADSL port

VPI VPI value

VCI VCI value

Cells Received Number of ATM cells received on PVC, not including idle cells and OAM cells

Cells Transmitted Number of ATM cells transmitted on PVC, not including idle cells and OAM cells

Cells Received Dropped Number of cells received and dropped.


IPADSLx Module 375


Bridge PM ControlExpand an IPADSLx module from the tree view and select Bridge Port to open Figure 292. Click Retrieve to obtain the latest information. Configure the parameters and click Apply to take the modification into effect. Refer to Table 132 for more details.

Figure 292 IPADSLx - Bridge Port - Bridge PM Control

BridgeSelect a IPADSLx module from the tree view to view the bridge report shown in Figure 293. Refer to Table 133 for more details.

Select a port and click Reset Counter to reset the counters for a specific port. Click Reset All Counters to reset all counters for all ports. Click Retrieve to obtain the latest performance report.

Table 132 IPADSLx - Bridge Port - Bridge PM Control Table

Parameter Value RangeBridge Port 5 Minutes PM Monitoring


Bridge Port 15 Minutes PM Monitoring


History Capacity History buffer size



Figure 293 IPADSLx - Bridge Port - Bridge

Note: All counters are 32 bits long except incoming/outgoing octets counters are 64 bit long.

Table 133 IPADSLx - Bridge Port - Bridge Table

PM Parameter DescriptionPort Port type. WAN port or ADSL port

VPI:VCI VPI, VCI values



Incoming frames The number of frames that have been received by the bridge port from its segment.

Outgoing frames The number of frames that have been transmitted by this port to its segment

Incoming discard frames The number of valid frames received from this bridge segment and are discarded by the forwarding process and the filtering process








IPADSLx Module 377

Note: All counters in Bridge report are automatically reset after the ADSL line is reset or re-trained.

5 Minutes ReportExpand an IPADSLx module from the tree view and select Bridge Port. Click 5 Minutes Report tab to open Figure 294.

Click Retrieve to obtain the latest information. Click Reset to reset the statistics listed in the Current Interval section. Previous Intervals section lists the history statistics. Refer to Table 134 for more details.

Figure 294 IPADSLx - Bridge Port - 5 Minutes Report

Table 134 IPADSLx - Bridge Port - 5 Minutes Report Table

Parameter Value RangePort List Port list

Time Elapse / End Time Period of time for collecting the error

Valid Validation of the data








15 Minutes Report15 Minutes Report shares identical parameters with 5 Minutes Report. Please refer to 5 Minutes Report for more details.

WAN Port IPADSLx modules support the following performance reports for WAN port:


■ 15 Minutes

■ 24 Hours

Threshold ControlsExpand an IPADSLx module from the tree view and select WAN Port to open Figure 295. Click Retrieve to obtain the latest information. Configure the parameters and click Apply to take the modification into effect. Refer to Table 135 for more details.




Table 134 IPADSLx - Bridge Port - 5 Minutes Report Table



IPADSLx Module 379

Figure 295 IPADSLx - WAN Port - Thresholds Control

15 MinutesExpand an IPADSLx module from the tree view and select WAN Port. Click the 15 Minutes tab to open Figure 296.

Table 135 IPADSLx - WAN Port - Thresholds Control Table

Field DescriptionProfile Name The Name of the profile selected.

Alignment Error Count of frames received on a particular interface that is not an integral number of octets in length and do not pass the FCS check.

CRC Error Count of frames received on a particular interface that is an integral number of octets in length but do not pass the FCS check. This count does not include frames received with frame-too-long or frame-too-short error.

Oversize Frame Count of frames received on a particular interface that exceeds the maximum permitted frame size.

Collision Count of successfully transmitted frames on a particular interface for which transmission is inhibited by collision.



Click Retrieve to obtain the latest information. Click Reset Counters to reset the statistics listed in the Current Interval section. Previous Intervals section lists the history statistics. Refer to Table 136 for more details.

Figure 296 IPADSLx - WAN Port - 15 Minutes

Table 136 IPADSLx - WAN Port - 15 Minutes Table

Field DescriptionPM Monitoring Enabled or Disabled.

Read-only.

Port Admin State Locked or Unlocked.

Read-only.

Time Elapsed Period of time for collecting the error




IPADSLx Module 381

24 Hours24 Hours report shares identical parameters with 15 Minutes report. Please refer to 15 Minutes for more details.

ADSL Port IPADSLx modules support the following performance reports for ADSL port:

■ ADSL 15 Minutes Summary

■ ADSL 24 Hours Summary


■ ATUC 15 Minutes

■ ATUC 24 Hours

■ ATUR 15 Minutes

■ ATUR 24 Hours

■ Channel Level

ADSL 15 Minutes SummarySelect a IPADSLx module from the tree view and click the ADSL 15 Minutes Summary tab to view the 15 minutes summary shown in Figure 297.

Select a port and click Reset 15 Minutes Current Counter to reset the counts for a specific port. Click Retrieve to obtain the latest performance report. Refer to Table 137 for more information.



Previous Intervals History of the performance report

Table 136 IPADSLx - WAN Port - 15 Minutes Table

Field Description



Figure 297 IPADSLx - ADSL Port - ADSL 15 Minutes Summary

Table 137 IPADSLx - ADSL Port - ADSL 15 Minutes Summary Table

Parameters DescriptionPort ADSL port ID number

LOF - Loss of Frame This parameter is a count of 1-second intervals with loss of frames.

Applicable for IPADSL3x modules only.

LOS - Loss of Signal This parameter is a count of 1-second intervals with loss of signal.


LOL - Loss of Link This parameter is a count of 1-second intervals with loss of link.


ES - Errored Seconds This parameter is a count of 1-second intervals with:

■ one or more CRC-8 anomalies

■ one or more LOS defects

■ one or more SEF defects

■ one or more LPR defects


IPADSLx Module 383

ADSL 24 Hours SummaryADSL 24 Hours Summary shares identical parameters with ADSL 15 Minutes Summary. Please refer to ADSL 15 Minutes Summary for more details.

Threshold ControlsExpand an IPADSLx module from the tree view and expand ADSL Port. Select an ADSL Port # to open Figure 298. Click Retrieve to obtain the latest information. Configure the parameters and click Apply to take the modification into effect. Refer to Table 138 for more details.

SES - Severely Errored Seconds This parameter is a count of 1-second intervals with:

■ 18 or more CRC-8 anomalies

■ one or more LOS defects

■ one or more SEF defects

■ one or more LPR defects.

UAS - Unavailable Seconds This parameter is a count of 1-second intervals for which the ADSL line is unavailable. The ADSL line becomes unavailable at the onset of 10 contiguous SES-Ls. The 10 SES-Ls are included in unavailable time. Once unavailable, the ADSL line becomes available at the onset of 10 contiguous seconds with no SES-Ls. The 10 seconds with no SES-Ls are excluded from unavailable time.

LPR - Loss of Power This parameter is a count of 1-second intervals with loss of power

Table 137 IPADSLx - ADSL Port - ADSL 15 Minutes Summary Table

Parameters Description



Figure 298 IPADSLx - ADSL Port - Thresholds Control

ATUC 15 MinutesAll ATUC/ATUR 15 minutes and 24 hours performance reports share identical parameters.

Expand an IPADSLx module from the tree view and expand ADSL Port. Select an ADSL Port # and click the ATUC 15 Minutes tab to open Figure 299. Click Retrieve to obtain the latest information. Refer to Table 139 for more details.

Table 138 IPADSLx - ADSL Port - Thresholds Control Table

Field DescriptionProfile Name The Name of the profile selected.






IPADSLx Module 385

Figure 299 IPADSLx - ADSL Port - ATUC 15 Minutes

Table 139 IPADSLx - ADSL Port - ATUC 15 Minutes Table

Field DescriptionPM Monitoring Enabled or Disabled.

Read-only.

Port Admin State Locked or Unlocked.

Read-only.

Time Elapsed / End Time Period of time for collecting the error

Valid Yes or No

LOF - Loss of Frame Count of loss of frame

LOS - Loss of Signal Count of loss of signal

LOL - Loss of Link Count of loss of link

ES - Errored Seconds Count of errored seconds

SES - Severely Errored Seconds Count of severely errored seconds

UAS - Unavailable Seconds Count of unavailable seconds

Previous Intervals History record of the performance report



ATUC 24 HoursATUC 24 Hours report shares identical parameters with ATUC 15 Minutes report. Please refer to ATUC 15 Minutes more details.

ATUR 15 MinutesATUR 15 Minutes report shares identical parameters with ATUC 15 Minutes report. Please refer to ATUC 15 Minutes more details.

ATUR 24 HoursATUR 24 Hours report shares identical parameters with ATUC 15 Minutes report. Please refer to ATUC 15 Minutes more details.

Channel LevelIPADSLx modules support the following channel performance reports for ADSL port:

■ Downstream 15 Minutes

■ Downstream 24 Hours

■ Upstream 15 Minutes

■ Upstream 24 Hours

Downstream 15 Minutes All downstream/upstream 15 minutes and 24 hours performance reports share identical parameters.

Expand an IPADSLx module from the tree view and expand ADSL Port. Expand an ADSL Port # and select Channel to open Figure 300. Click Retrieve to obtain the latest information. Refer to Table 140 for more details.


IPADSLx Module 387

Figure 300 IPADSLx - Channel - Downstream 15 Minutes

Downstream 24 Hours Downstream 24 Hours report shares identical parameters with Downstream 15 Minutes report. Please refer to Downstream 15 Minutes more details.

Upstream 15 Minutes Upstream 15 Minutes report shares identical parameters with Downstream 15 Minutes report. Please refer to Downstream 15 Minutes more details.

Upstream 24 Hours Upstream 24 Hours report shares identical parameters with Downstream 15 Minutes report. Please refer to Downstream 15 Minutes more details.

Table 140 IPADSLx - Channel - Downstream 15 Minutes Table

Field DescriptionTime Elapsed / End Time Period of time for collecting the error

Valid Yes or No.

Tx Blocks Count of Transmitted Blocks

Rx Blocks Count of Received Blocks

Corrected Blocks Count of blocks received with error that are corrected

Un-corrected Blocks Count of blocks received with un-correctable errors



IPSHDSL3 Module IPSHDSL3 modules support slot level performance report, which is the Bridge performance report.

Select a IPSHDSL3 module from the tree view to view the bridge report shown in Figure 301. Refer to Table 141 for more details.

Figure 301 IPSHDSL3 - Bridge

Table 141 IPSHDSL3 - Bridge Table

Field DescriptionPort Port type. WAN port or ADSL port

VPI:VCI VPI, VCI values



Incoming frames The number of frames that have been received by the bridge port from its segment.

Outgoing frames The number of frames that have been transmitted by this port to its segment

Incoming discard frames The number of valid frames received from this bridge segment and are discarded by the forwarding process and the filtering process




IPSHDSL3 Module 389

Select a port and click Reset Counter to reset the counts for a specific port. Click Reset All Counters to reset all counts for all ports. Click Retrieve to obtain the latest performance report.





Table 141 IPSHDSL3 - Bridge Table

Field Description




9
DIAGNOSTICS
Diagnostics provides loop test for IPADSLx modules in iAN8K B1000 system. Figure 302 shows the main window of the Diagnostics.

Figure 302 Diagnostics Main Window

iAN8K B1000 supports the following diagnostics for IPADSLx modules:

■ F4/F5 Loopback

■ DELT

■ SELT (for IPADSL3A/6A modules only)

F4/F5 Loopback ITU-T I.610 defines five hierarchical flows to support bi-directional flow for Operation and Maintenance (OAM) functions. Out of which, F4 and F5 are two upper flows for the ATM layer. Both flows are bidirectional, in-band management flows.


392 Chapter 9: Diagnostics

The F4 is used for the VP while the F5 is used for VC. Both can be based upon a segment or an end-to-end basis. Typical applications for F4/F5 loopback are:

■ On-demand connectivity monitoring - A VP/VC end-to-end loopback can be initiated at the iAN8K B1000 side or CPE side to monitor connectivity

■ Fault localization - A VP/VC segment loopback to diagnosis fault segment.

■ Pre-service connectivity verification.

For F4 loopback test:

■ The ATM F4 loopback of end-to-end and segment loopback are supported per ATM PVP and SPVP. VCI value of 3 indicating a F4 segment loopback. VCI value of 4 indicating a F4 end-to-end loopback;

■ Each cell is sent in one second apart regardless of the previous cell is received successfully or not. The loopback cell is considered lost if it is not returned within 5 seconds. It is counted toward lost loop-back cells.

■ If receiving a F4 end-to-end or segment loopback cell, the line card at the loopback point (indicated by the loopback location ID in the OAM cell) sends back the cell via the original VP. It is required to set the loopback indication field from 1 to 0 prior looping the cell back to the originator to indicate that the loopback has occurred.

For F5 loopback test:

■ After the loopback test is initiated, line module sends ATM F5 end-to-end or segment loopback OAM cells via the VC as specified by the user.

■ Each cell is sent in one second apart if reply is successfully received for the previous cell. Otherwise, IPxDSL module waits up to five-seconds before sending next cell.

Expand an IPADSLx module and click F4/F5 Loopback to open Figure 303. Select a port and click F5 Test or F4 Test to begin testing. Figure 304 prompts for F4 test parameters and Figure 305 prompts for F5 test parameters.

.Note: The operational state of the port must be enabled to perform F4 or F5 loopback test on the port.


F4/F5 Loopback 393

Figure 303 F4/F5 Loopback Window

Figure 304 F4/F5 Loopback - F4 Test Window



Figure 305 F4/F5 Loopback - F5 Test Window

Configures the parameters and click Start to begin the test. The test results are:

■ The number of transmitted F4/F5 loopback cells

■ The number of received F4/F5 loopback cells

DELT Dual Ended Loop Testing (DELT) is a new line-diagnose procedure introduced by ITU G.992.3 (ADSL2). DELT is typically used when the line quality is too poor to reach data mode and is activated to troubleshoot the problem. DELT enables the immediate measurement of line conditions at both ends of the line without dispatching maintenance technician to attach test equipment to the line. The result information helps to isolation the location and the source (crosstalk, radio frequency interference, bridge tap) of impairments.

Note: For more information, please refer to the following document:

■ ITUT-T G.992.3 Asymmetric digital subscriber line transceivers 2 (ADSL2) (01/2005) section 8.15 Loop diagnostics mode procedures

Both CO and CPE must support DELT. In addition, DELT must be started from ONE side only while the other side initiates a normal startup.

Expand an IPADSLx module and click DELT to open Figure 306. Select a port and click Start to begin testing.

Note: The Administrative State of the port must be locked to perform DELT test.


DELT 395

Figure 306 DELT Window

The Operational State of the port becomes In DELT Test when under testing. The port remains in-delt-test state until manually stopped. The DELT status displays in-progress, successful or failed. DELT test result can be retrieved only when DELT status become successful. Click Result to display the testing results.

Samples of the test results are displayed in Figure 307, Figure 308, Figure 309 and Figure 310.



Figure 307 DELT - Result - Hlin(f)

Figure 308 DELT - Result - Hlog(f)


DELT 397

Figure 309 DELT - Result - QLN(f)

Figure 310 DELT - Result - SNR(f)



Click Report to display the data for the test results as shown in Figure 311. Click Close to exit.

Note: SNR margin is not supported in this release. The value is always 51.2 db in current release. It will be supported in a future release.

Figure 311 DELT Window - Result - Report


SELT 399

SELT SELT is used to characterize/test the loop during pre-service activation or during failure diagnose. SELT does not require CPE to be installed at the remote end. SELT operation does not impact the regular service on the adjacent ports.

Single Ended Loop Testing (SELT) is not standardized in ITU. The requirements developed in this section are based on Conexant proprietary technology.

Note: SELT test result can be viewed with Netman 4000 Client application only. Please install Netman 4000 Client application before runing the test.

Expand an IPADSL3A/6A module and click SELT to open Figure 312. Select a port and click Start to begin testing.

Note: The Administrative State of the port must be locked to perform SELT test.

Figure 312 SELT Window

The Operational State of the port becomes In SELT Testing when under testing. When the test is complete, the Operational State of the port becomes Disabled again. Click Result to display the testing results shown in Figure 313. Refer to Table 142 for more information of the results.



Figure 313 SELT - Test Result

Table 142 SELT - Test Result Field Description

Field DescriptionLoop Information

Loop Length This parameter determines the loop length in feet.

SELT results are valid for loop length between approximately 600 feet to 9000 feet. If loop length is outside the range, SELT test returns Invalid.

Termination This parameter determines if the loop is an open or short circuit.

■ Open

■ Short

Gauge This parameter determines the wire gauge information.

■ 0.4mm or 26 AWG

■ 0.5mm or 24 AWG


SELT 401

Click Table button to display the numerical data of the test results as shown in Figure 314. Click Close to exit the window.

Capacity Capacity margin in dB. User configurable.

Default: 6dB.

Upstream This parameter determines the upstream shannon capacity in Kbps. Shannon capacity is the theoretical maximum rate under ideal, unimpaired conditions, i.e., no noise, attenuation, etc.

Downstream This parameter determines the downstream shannon capacity in Kbps. Shannon capacity is the theoretical maximum rate under ideal, unimpaired conditions, i.e., no noise, attenuation, etc.

Plots

Inband Noise 512 values that indicate inband noise in dBm/Hz, covering both bands, from 0 to 2.2MHz.

■ Magnitude: -150 - 0 dBm/Hz

■ Frequency: 0 - 2.2 MHz

Termination Response 180 values that indicate signal termination response magnitude from 0 to 18 kft in 100 ft increments.

The absolute maximum or peak corresponds to loop length or the location of the first open/short. Local maxima may correspond to other open/shorts or discontinuities in the loop.

■ Relative Magnitude: Varies according to the actual result

■ Distance: 0 - 18000 feet

DMT Margin vs. Rate (UP) 150 values that indicate upstream SNR margin in dB/10 at a particular rate are provided, at 100 k increments, up to 15 Mbp.

■ Margin: -6 - 40 dB

■ Rate: 0 - 2 Mbps

DMT Margin vs. Rate (DN) 150 values that indicate downstream SNR margin in dB/10 at a particular rate are provided, at 100 k increments, up to 15 Mbps.

■ Margin: -6 - 80 dB

■ Rate: 0 - 30 Mbps

Table 142 SELT - Test Result Field Description

Field Description



Figure 314 SELT - Test Result - Table

Note: Plot requires a program called “WHIP.” Start the program and run SELT test again. Refer to WHIP user manual for more information.

The File menu provides the options to save the results or open an old DAT file previously saved. The default directory is C:\NMSClient\lib.


SELT 403

Figure 315 SELT - Test Result - File - Directory

The View menu provides the options to enlarge the graphical view of the 4 graphical results in Figure 313. A sample is shown in Figure 316.

Figure 316 SELT - Test Result - View - Inband Noise




10
FAULT MANAGEMENT
Fault Management provides the most current alarm information for the node to ensure network reliability. It allows users to perform monitoring and troubleshooting of IP DSLAM nodes from the desktops.

IP DSLAM system alarms are detected and reported to Netman 4000 platform. This information can be used as a base to further determine a troubleshooting scheme. The node supports the following fault management configuration options:

■ Netman 4000

■ Alarm Report

■ Alarm List

Note: Fault Management is applicable only for single shelf system. For stacking configuration, retrieve alarms from NetmanTM4000 platform. The alarms are listed in the bottom left panel according to the categories and severities. Clicking on each alarm numbers to view more details.

Figure 317 Platform Level Alarms


406 Chapter 10: Fault Management

Netman 4000 When an alarm is detected and administrative state of affected resource is unlocked, the node reports the alarms as followed:

1 Update the operational state of the affected resource

2 Save the alarm in ICM3

3 Refreshes the PCU alarm lamp and PDP buzzer status

4 Sends alarm trap to Netman 4000

When an alarm is detected and administrative state of affected resource is locked, the node updates the operational state of the affected resource.

Alarm reporting follows a hierarchy with alarm severity propagation, alarms at the port level affect the status of the board and alarms at the board level affect the status of the node. The system map is at the highest level in the alarm reporting hierarchy. The color of a node icon shows the alarms with the highest severity on the node. Alarm details are also displayed at the highest view bar.

Audible And VisualAlarm

IP DSLAM node supports audible and visual alarm display. Visual alarm displays are implemented in two levels. On PDP module, LED SYSALM is turned on when the current highest alarm severity has reached to a severity level customized by the user. On PCU module, the LED indicates the fan failure alarm.s

Audible alarm is generated from PDP. It is triggered when a new alarm reaches the severity level customized by the user. The audio sound can be turned off temporarily (until the next alarm triggers it) with the AUDIO button on the PDP. Visual alarm indications, however, cannot be temporarily altered. User can define the alarm visual/audible display behavior from Netman 4000 platform.

Alarm Presentation Alarms are represented in an alarm tree as shown in Figure 318. The alarm tree is based on a parent-child relationship. The tree starts with a node. Below the node branch are shelf, equipment and external. Below shelf branch are boards, ports and channels.

An IP DSLAM node reports alarms and states change notifications to the management system on-demand and autonomously.


Alarm Report 407

Figure 318 Alarm Tree

Table 143 describes entities and their relationship with other entities. An entity can be a placeholder that doesn't have any alarms of its own. However it will reflect the sub-tree level severity e.g. shelf entity reflects the highest severity for all the child entities below the shelf branch.

Alarm Report IP DSLAM supports the following configuration for alarm reporting:

■ Alarm Report

Table 143 Node Alarm Tree Entity

Entity Description Instance Naming Parent EntityNode The top-level entity that represents an IP DSLAM access node. All

the system alarms shall be reported on this entity.Node name None

Shelf This entity represents a shelf of the IP DSLAM access node. It is a placeholder entity.

1 to 6 IP DSLAM node

Slot It represents a slot in a particular shelf. 1 to 16, A, B, P Shelf

Board name If a board is inserted in the slot, all the alarms related to the board are reported on this entity.

Board type Slot

<Port Type> Port This entity represents a physical port on a particular board. This is a base class for specific port entities. Alarms related to a specific port are reported on the respective specific port entity

1 to 24 Slot

Channel It represents a logical port that is a part of physical ports, for example in the IPADSL board, an ADSL port is the physical port, while the fast-channel that is carried by this port is the channel.

Number Slot

ATM Interface This entity represents an ATM layer Interface Id (channel index or the interface number)

Channel

Equipment This entity is a placeholder for the system components of the IP DSLAM access node e.g. fuse, etc.

None IP DSLAM Node

Clock This entity is a placeholder for clock related alarms None Equipment

PDP Fuse It represents the PDP fuses. None Equipment

External This entity is used to report all the alarms that are detected on external devices like PCU.

None IP DSLAM Node



■ Alarm Summary

■ Filter Setup

Alarm Report To view the alarm tree, click on Alarm tab in the bottom of device manager window. The alarm window is promoted as shown in Figure 319.

Figure 319 Fault Management Main Window

Select an entry from the tree view to display its alarm report. Figure 320 displays the node alarm report, Figure 321 displays the equipment alarm report and Figure 322 displays the port alarm report.


Alarm Report 409

Figure 320 Node Alarm



Figure 321 Equipment Alarm


Alarm Report 411

Figure 322 Port Alarm

For more detail information of the alarm report, please refer to Table 144, Table 145, Table 146 and Table 147.

Table 144 Alarm Report - Subtree

Field DescriptionEntity Type Shows the Entity (board, port etc.) for described alarms

Entity Instance The location in terms of Shelf-Slot-Port.

Subtree severity The highest severity of the sub-tree. Due to the parent child nature of the relationship of an entity with all its sub entities, the parent reflects the highest severity among itself and its children



Click Alarm Summary to display all alarms for the entire system. Refer to Alarm Summary section for more information.

Click Filter Setup to configure alarm filter for the modules. Refer to Filter Setup section for more information.

Click Retrieve to obtain the latest alarm information.

Alarm Summary The alarm summary window displays all the alarms in the node. Select an entity from the tree view and click Alarm Summary to display Figure 323. For more information of parameters, please refer to Table 144, Table 145, Table 146 and Table 147.

Click Retrieve to obtain the latest alarm information. Click Close button to exit the window.

Table 145 Alarm Report - Alarm Class

Category DescriptionCommunication Alarm Associated with the procedures and/or processes required to convey information from one point to

another

Quality Of Service Alarm Associated with a degradation in the quality of a service

Equipment Alarm Associated with an equipment fault

Processing Error Alarm Associated with a software or processing fault

Environmental Alarm Associated with a condition relating to an enclosure in which the equipment resides

Table 146 Alarm Report - Alarm Severity

Category Color DescriptionCritical Red Indicates that a service affect condition has occurred and an immediate corrective action is required.

Major Orange Indicates that a service affect condition has developed and an urgent corrective action is required.

Minor Yellow Indicates the existence of a non-service affect fault condition and that corrective action shall be taken in order to prevent more serious fault (for example, service affecting).

Warning Blue Indicates the detection of a potential or impending service affecting fault, before any significant effects have been felt. Action shall be taken to further diagnose if required and correct the problem in order to prevent it leading to a more serious service affecting fault.

Table 147 Alarm Report - Alarm List Entity

Category DescriptionProbable Cause This parameter defines further qualification as to the probable cause of the alarm.

Specific Problems This parameter identifies further refinements to the Probable cause of the alarm.

Severity This parameter defines severity levels as listed in Table 146.

Time Stamp This parameter contains the time the event occurs.

Alarm Class This parameter indicates the type of alarm as listed in Table 145.

Additional Text This parameter allows a free form text description to be reported. Optional.


Alarm Report 413

Figure 323 Alarm Summary Window

Filter Setup Filters allow temporary isolation of alarms from the entire alarm list, which helps the troubleshooting. Filtering can be configured based on the alarm category, alarm severity and probable cause. Filters are not propagated across the alarm tree hierarchy.

Select an entity from the tree view and click Filter Setup to open Figure 324. For more information of the parameters, please refer to Table 144, Table 145, Table 146 and Table 147.

Select a board in Figure 324 and configure the filters. Click Apply to enable the new filter configuration. Click Retrieve to obtain the latest filter information. Click Close to exit the window.



Figure 324 Alarm Filter Window

Note: The probable causes listed in Figure 324 varies according to the module selected.

Alarm List The following alarms are included in the IP DSLAM alarm reporting scheme.

■ Node Alarm

■ External Alarm\

■ ICM3 Alarm

■ IP-ADSLx Alarm

■ IP-SHDSL3 Alarm

■ iFXS1 Alarm


Alarm List 415

Node Alarm

The module type mismatch alarm is raised and the inserted module becomes non-operational, if the physical module inserted does not match the virtual module assigned in the slot. The alarm is cleared after virtual module is

Table 148 Node Alarm List

Event TypeProbable Cause Specific Problems

Managed Object Severity

Occurrence Cause

Clear Condition Remedy

Processing Error Alarm

Software Download Failure

Download Time Out; Additional Info = "Failure in Slot #<slot number>"

Node Warning SW download timeout

SW download success

Remove redundant files from flash. Reset line card.

Environmental Alarm

Fuse Failure Fuse Down - Fuse #<fuse number>

Node Minor Fuse burned Fuse recovered

Replace Fuse

Environmental Alarm

Fan Failure Fan failure - fan <x>; Fan failure - rack fan

Node Major Fan failure Fan is up Replace the bad fan unit

Equipment Alarm

Timing Problem

External Clock Down Clock Major External clock down

External clock signal is received

Check external clock status

Equipment Alarm

Module Removed from slot x

Null Node Critical Module removed from a slot

Module is plugged in

Check if the module is plugged in properly

Equipment Alarm

Module type mismatch

Specify the slot ID, the physical module type and virtual module type

Node Major Inserted board type mismatch

The wrong board unplugged

Unplug the wrong board

Processing Alarm

Black List Address Match

Null Node Warning MAC address matches provisioned black list

When black list feature is disabled

N/A

Equipment Alarm

ICM Switchover

Null Node Critical ICM switched to redundant unit

N/A Check ICM board status

Equipment Alarm

Standby ICM3 is running a higher version image

Null Node Warning Standby ICM is running a higher version image

Compatible software version is running

Install compatible software version

Equipment Alarm

Standby ICM3 is running a lower version image

Null Node Major Standby ICM is running a lower version image

Compatible software version is running

Install compatible software version

Processing error alarm

Feature key can not be found

Region setting could not be determined

Node Critical Region setting could not be determined

When the region is determined

Install correct region key file

Processing error alarm

External module work status changed

Board Minor A configured external module is not accessible

The external module becomes accessible

Check external module status.

Check connection to the external module.

Check configuration of the external module.



de-assigned (i.e., module shall become manageable after the virtual module is de-assigned) or after the physical module is removed.

External Alarm

ICM3 Alarm

IP-ADSLx Alarm

Table 149 External Alarm List

Event Type Probable CauseSpecific Problems


Occurrence Cause

Clear Condition Remedy

Equipment Alarm External Interface Device Problem

Per user configuration



Per user configured alarm



Table 150 ICM3 Alarm List

Event TypeSpecific Problems Managed Object Severity

Occurrence Cause Clear Condition Remedy

Communication Alarm

NULL Internal Ethernet interface (displayed as internal x/y, x=1..16 (chassis dependent), y=1,2)

Major Internal link partially down

Internal link up. Check backplane connection. Reset the module.

Communication Alarm

NULL Internal Trunk interface (displayed as internal x, x=1..16, chassis dependent)

Critical Internal link down

Internal link up. Check backplane connection. Reset the module.

Communication Alarm

NULL External Ethernet interface, (displayed as FE x where x = 1..4; GE y where y=1..4; or 10G 1)

Critical External Link down

External Ethernet interface connection is established.

Check external Ethernet connection. Check configurations such as speed.

Communication Alarm

NULL External Ethernet interface Major External Link in trunk down

External link up. Check link connectivity

Communication Alarm

NULL External Trunk interface Critical External trunk down

External trunk up. Check link connectivity

Table 151 IP-ADSLx Alarm List

Event Type Probable Cause Specific ProblemsManaged Object

Perceived Severity

Communication Alarm Initialization failure Null ADSL port Critical

Communication Alarm Loss of signal Null ADSL Port Critical

Communication Alarm Loss of link No link with ATU-R ADSL Port Major

Communication Alarm ATU-R capability mismatch 1 ATU-C, ATU-R profile setting mismatch ADSL Port Major

QoS Alarm ATU-C Threshold crossed 15 Min. LOF, Threshold value, Arm time ADSL port Minor

QoS Alarm ATU-C Threshold crossed 15 Min. LOS, Threshold value, Arm time ADSL port Minor

QoS Alarm ATU-C Threshold crossed 15 Min. LOL, Threshold value, Arm time ADSL port Minor


Alarm List 417

Note: The capability mismatch alarm is only supported with GSV compatible ATU-R device. Such device will respond to ATU-C polling and report its current capability setting. When ADSL link goes down, ATU-C polls the ATU-R for capability value. If returned capability mis-matches the ATU-C's own capability setting, an alarm is raised. If no capability value is returned (ATU-R does not support this feature) or the returned capability matches ATU-C capability, no alarm would be raised. The alarm is cleared when ADSL link comes up or when

QoS Alarm ATU-C Threshold crossed 15 Min. ES, Threshold value, Arm time ADSL port Minor

QoS Alarm ATU-C Threshold crossed 15 Min. SES, Threshold value, Arm time ADSL port Minor

QoS Alarm ATU-C Threshold crossed 15 Min. UAS, Threshold value, Arm time ADSL port Minor

QoS Alarm ATU-C Threshold crossed 24 Hr. LOF, Threshold value, Arm time ADSL port Minor

QoS Alarm ATU-C Threshold crossed 24 Hr. LOS, Threshold value, Arm time ADSL port Minor

QoS Alarm ATU-C Threshold crossed 24 Hr. LOL, Threshold value, Arm time ADSL port Minor

QoS Alarm ATU-C Threshold crossed 24 Hr. ES, Threshold value, Arm time ADSL port Minor

QoS Alarm ATU-C Threshold crossed 24 Hr. SES, Threshold value, Arm time ADSL port Minor

QoS Alarm ATU-C Threshold crossed 24 Hr. UAS, Threshold value, Arm time ADSL port Minor

QoS Alarm ATU-R Threshold crossed 15 Min. LOF, Threshold value, Arm time ADSL port Minor

QoS Alarm ATU-R Threshold crossed 15 Min. LOS, Threshold value, Arm time ADSL port Minor

QoS Alarm ATU-R Threshold crossed 15 Min. LPR, Threshold value, Arm time ADSL port Minor

QoS Alarm ATU-R Threshold crossed 15 Min. ES, Threshold value, Arm time ADSL port Minor

QoS Alarm ATU-R Threshold crossed 15 Min. SES, Threshold value, Arm time ADSL port Minor

QoS Alarm ATU-R Threshold crossed 15 Min. UAS, Threshold value, Arm time ADSL port Minor

QoS Alarm ATU-R Threshold crossed 24 Hr. LOF, Threshold value, Arm time ADSL port Minor

QoS Alarm ATU-R Threshold crossed 24 Hr. LOS, Threshold value, Arm time ADSL port Minor

QoS Alarm ATU-R Threshold crossed 24 Hr. LPR, Threshold value, Arm time ADSL port Minor

QoS Alarm ATU-R Threshold crossed 24 Hr. ES, Threshold value, Arm time ADSL port Minor

QoS Alarm ATU-R Threshold crossed 24 Hr. SES, Threshold value, Arm time ADSL port Minor

QoS Alarm ATU-R Threshold crossed 24 Hr. UAS, Threshold value, Arm time ADSL port Minor

QOS Alarm WAN port threshold Crossed 15 Min. Alignment Error, Threshold value, Arm time

WAN port Minor

QOS Alarm WAN port threshold Crossed 15 Min. CRC Error, Threshold value, Arm time WAN port Minor

QOS Alarm WAN port threshold Crossed 15 Min. Over sized Frame, Threshold value, Arm time

WAN port Minor

QOS Alarm WAN port threshold Crossed 15 Min. Collision, Threshold value, Arm time WAN port Minor

QOS Alarm WAN port threshold Crossed 24 Hr. Alignment Error, Threshold value, Arm time

WAN port Minor

QOS Alarm WAN port threshold Crossed 24 Hr. CRC Error, Threshold value, Arm time WAN port Minor

QOS Alarm WAN port threshold Crossed 24 Hr. Over sized Frame, Threshold value, Arm time

WAN port Minor

QOS Alarm WAN port threshold Crossed 24 Hr. Collision, Threshold value, Arm time WAN port Minor

Communication Alarm Excessive CRC errors for consecutive 10 seconds

Automatic Full Retrain engaged DSL Port Major

Table 151 IP-ADSLx Alarm List

Event Type Probable Cause Specific ProblemsManaged Object

Perceived Severity



returned ATU-R capability matches ATU-C capability. Currently capabilities are grouped as following:

■ T1.413

■ G.dmt Annex A FDM

■ G.dmt Annex A EC

■ G.dmt Annex B FDM

■ G.dmt Annex B EC

■ G.dmt Annex C FDM

■ G.dmt Annex C EC

■ G.lite Annex A FDM

■ G.lite Annex C EC

■ G.lite Annex FDM

■ G.span Annex A FDM

■ G.span Annex A EC

■ G.span+ EC

■ G.span+ FDM

Depending on the profile, ATU-C will support one or more capabilities. If ATU-R supports any one of the capabilities that is supported by ATU-C, and then a match is considered.

IP-SHDSL3 Alarm

Table 152 IP-SHDSL3 Alarm List

Event Type Probable Cause Specific Problems Managed Object Perceived SeverityCommunication Alarm Loss of signal NULL SHDSL port Critical


Alarm List 419

iFXS1 Alarm

Table 153 Alarm List of iFXS1 Based on SIP

Alarm TypeSpecific Problems Managed Object Severity


Communication Alarm

Failure to resolve AS IP address

Module Major DNS problem

As IP address resolved

Check DNS

Communication Alarm

Cannot reach AS

Module Major Network problem

Network problem solved

Check network

Communication Alarm

Loss of connection to AS

Module Critical Server down or network problem

Server up or network problem resolved

Check AS and network

Communication Alarm

User registration failed

Port Minor Display error code from AS

User can register Resolve misconfiguration

Table 154 Alarm List of RTP Related



QoS Alarm Cumulative number of packets lost threshold exceeded

Module Minor Accumulated packet loss in a 15 min interval exceeds threshold setting

When the next 15 min interval begins

Resolve network troubles

QoS Alarm Interarrival jitter exceeded

Module Minor Interarrival jitter in a 15 min interval exceeds threshold setting





Event List for iFXS1Module

QoS Alarm Jitter buffer overflow

Module Minor Jitter buffer overflow in a 15 min interval exceeds threshold setting



QoS Alarm Jitter buffer underflow

Module Minor Jitter buffer underflow in a 15 min interval exceeds threshold setting



QoS Alarm Excessive delay in the network

Module Minor Average delay in a 15 min interval exceeds threshold setting



Table 154 Alarm List of RTP Related



Table 155 Alarm List of Uplink FE Interface

Alarm Type Probable Cause Specific Problems


Communication Alarm

Loss of signal at Ethernet interface

FE interface loss of signal before MG interface activates

Port Warning

Communication Alarm

Loss of signal at Ethernet interface

FE interface loss of signal after MG interface activates

Port Critical

Table 156 Event List Based on SIP

Event Type Event Information DescriptionMG interface provisioning MG interface administrative

on/offMG interface locked

MG interface unlocked

Register to AS Register to the AS Node

Logout from AS Logout from the AS Node

AS protection switching AS switchover Node switch to other AS


Alarm List 421

Table 157 Basic Event List

Event Type Event Information DescriptionMG starts up MG starts up iFXS1 module starts up




11
SYSTEM ADMINISTRATION
System Administration encompasses updating firmware and User Management.

■ Node File Management

■ Software Upgrade

■ ICM3 Module

■ IPxDSL Modules

■ ISM Module

■ ASM Module

■ File Transfer

■ Download

■ Upload

■ Delete

■ ICM3 Module Backup

■ ICM3 Module Replacement

■ Remote Access

Node File Management

Use the procedures in this section to delete, upload, and download node files. The Netman 4000 File Transfer function can be used over the entire IP network. The ICM3 has a flash memory of 16Mb, please refer to Table 158 for the description and approximate size of node files.

Please verify that the ICM3 has enough space before loading any files. Please see the remarks section in the table below for any Node file management.

The files as shown in Table 158 below are line card image files and should be downloaded into the system only if the respective line card is present. These files should be loaded sequentially and not at the same time even though the TFTP server may support multiple file transfers.

Please backup the existing icm_upgrade.gz and icm2_config.gz.


424 Chapter 11: System Administration

Software Upgrade

ICM3 Module This section provides information for upgrading ICM3 software from Release 3.x to a higher version of Release 3.1.x.

Refer contact an UTStarcom IPS representative for detailed instruction of upgrading from Release 2.x to Release 3.1.x or upgrading with shelf stacking system.

Note: Prior to switch to an ICM3 module or replace the old ICM3 module with a new ICM3 module, confirm the following:

■ The new ICM3 module contains the same configuration as the old ICM3 module.

Or■ Insert the new ICM3 module without any configuration and download a copy

of the previously saved configuration of the old ICM3 module.

Table 158 Node File Description

Sr. No. Module Name File Name Approximate Size in bytes1 ICM3 Icm_upgrade.gz 5016851 bytes

2 ICM3 icm2_config.gz Size varies based on configuration

3 ICM3 loader_rev_2_0.gz 109551 bytes

4 ICM3 jffs2.tar.gz 15053867 bytes

5 ICM3h icm3hB1K_loader_rev_0_8.gz 116445 bytes

6 IPADSL3A ipadsl3a.img 2008276 bytes

7 IPADSL3A dslfw3a.img 170548 bytes

8 IPADSL3B ipadsl3b.img 2014208 bytes

9 IPADSL3B dslfw3b.img 170856 bytes

10 IPADSL6A ipadsl6a.img 2009136 bytes

11 IPADSL6A dslfw6a.img 170548 bytes

12 IPADSL6B ipadsl6b.img 2015132 bytes

13 IPADSL6B dslfw6b.img 170856 bytes

14 IPSHDSL3 ipshdsl3.img 1994732 bytes

15 IPSHDSL3 shdslfw3.img 97308 bytes

16 PCU pcu.bin 23618 bytes

17 ISM system.fw 8885768 bytes

18 ASM asm_3.0.0.04_full.bin 5,302,214 bytes


Software Upgrade 425

Upgrade with A Redundant ICM3 ModuleFigure 325 is a pictorial depiction of the software upgrade process when the redundant ICM is present.

■ Part 1: before software upgrade and module switchover.

■ Part 2: uploading software to the flash memory of both ICM3 modules.

■ Part 3: upgrading the standby ICM3 module, ICM3-B.

■ Part 4: ICM3 module switchover and upgrading the ICM3-A module.

Figure 325 Software Upgrade

ICM3-A

RAM

Flash

OLD

Active Standby

OLD

ICM3-B

RAM

Flash

OLD

(1)

OLD

ICM3-A

RAM

Flash

OLD

Active Standby

ICM3-B

RAM

Flash

OLD

(2)

NEW NEW

ICM3-A

RAM

Flash

Active Standby

ICM3-B

RAM

Flash

NEW

(3)

NEWNEW

OLD

ICM3-A

RAM

Flash

Standby Active

ICM3-B

RAM

Flash

(4)

NEWNEW

NEW NEW



When standby ICM3 module is presented, follow the procedures below for upgrading from Release 3.1.x to a higher version of Release 3.1.x:

1 Confirm the standby ICM3 module has sufficient space (ICM3-B).

a Use the following CLI command to check the flash memory for the ICM3 module:

ICM3 Board

172.16.4.155 login: admin

Password:

You are now in the Privileged Mode

AN2000_IB#show memory

file file-size

/tmp/tftp/icm2_config.gz 76206

/tftpboot/dslfw3a.img 170548

/tftpboot/dslfw3b.img 170856

/tftpboot/ipadsl3a.img 2004588

/tftpboot/ipadsl3b.img 2010484

/tftpboot/pcu.bin 8507

/tftpboot/system.key 396

Filesystem 1k-blocks Used Available Use% Mounted on

/dev/mtdblock/1 31744 24468 7276 77% /

b Remove files from all ICM3 modules if it contains unnecessary files. From the CLI global configuration mode, use one of the following command to erase files from the ICM3 modules:

AN2000_IB#erase config all

AN2000_IB#erase memory <file name>

AN2000_IB#erase memory all

Note: The erase memory <file name> command removes the specified file from the standby ICM3 module and/or the active ICM3 module. If the file exists only on the standby module, the system may return an error message of “The file is not found...” . This occurs due to the file does not exist on the active ICM3 module. However the specified file is removed from the standby ICM3 module.

2 Start downloading new image to active ICM3 Flash memory.


Software Upgrade 427

3 Active ICM3 (ICM3-A) Flash memory is downloaded with new image and standby ICM3 (ICM3-B) Flash memory is synchronized with new image.

4 Reset the standby ICM3 (ICM3-B). ICM3 is rebooted with new image running.

5 Reset the active ICM3 (ICM3-A). The ICM3-B is switched over to active and runs new image. The ICM3-A becomes standby and is rebooted with new image running.

Note: If ICM3 module does not recognize the line modules correctly after system reboot, softreset all the line modules in slot 1 to 16. Do not reset ICM3 module. To guarantee accurate module recognition, ICM3 must become fully functional before all line modules becoming functional. Refer to Chapter 3 for more information of resetting line module in Device manager.

IPxDSL Modules Follow the procedures in this section to upgrade line modules software:

1 Confirm the ICM3 module has sufficient space.

a Use the following CLI command to check the flash memory for the ICM3 module:

ICM3 Board

172.16.4.155 login: admin

Password:


AN2000_IB#show memory

file file-size

/tmp/tftp/icm2_config.gz 76206

/tftpboot/dslfw3a.img 170548

/tftpboot/dslfw3b.img 170856

/tftpboot/ipadsl3a.img 2004588

/tftpboot/ipadsl3b.img 2010484

/tftpboot/pcu.bin 8507

/tftpboot/system.key 396

Filesystem 1k-blocks Used Available Use% Mounted on

/dev/mtdblock/1 31744 24468 7276 77% /

b Remove files from the ICM3 module if it contains unnecessary files. From the CLI global configuration mode, use one of the following command to erase files from the ICM3 modules:

AN2000_IB#erase config all

AN2000_IB#erase memory <file name>

AN2000_IB#erase memory all



Note: The erase memory command removes the specified file from the active ICM3 module and/or the standby ICM3 module. If the file exists only on the standby module, the system may return an error message of “The file is not found...” . This occurs due to the file does not exist on the active ICM3 module. However the specified file is removed from the standby ICM3 module.

2 Download a single line card image on the ICM3 and reset the module in which the relevant line card is present. This will initiate a forced download of the image. Refer to Chapter 3 - Provisioning - Node - Reset for more information on softreset and hardreset.

3 Delete the line card image from the ICM3 module.

4 Repeat Steps 1 and 2 till all the line card images are downloaded to the line cards via ICM3.

Note: Do not retain line card images file on ICM3 modules.

ISM Module Refer to ISM manual for more information:

■ iAN8K B1000 Release 3.1 IP Service Module (ISM) Operations Manual UTSI-NJTC-20050697

ASM Module Refer to ASM manual for more information:

■ iAN8K B1000 Release 3.1 IP ATM Service Module (ASM) Operations Manual UTSI-NJTC-20050699

File Transfer Netman 4000 supports TFTP option to allowing files management of:

■ Download - File transfer from client PC to node (ICM3)

■ Upload - File transfer from node (ICM3) to client PC

■ Delete - Node file deletion

This procedure is used to manage node files. The Netman 4000 File transfer function can be used over the entire IP network.

In the Netman 4000 main system map, select TFTP from the Tools menu as shown in Figure 326. Select the Client Mode radio button in Figure 327.


File Transfer 429

Figure 326 Tools - TFTP

Figure 327 Tools - TFTP - Client Mode

The TFTP window is prompted as shown in Figure 328. Expand the window with the arrows to view the directories.



Figure 328 Tools - TFTP Window

In Figure 329, the left side displays the directories for the local station and the right side displays the node directories.


File Transfer 431

Figure 329 Tools - TFTP Window - Expanded

Download

Note: In the case of a file not being successfully downloaded, the truncated file may remain in the flash. This file needs to be removed manually with the procedures listed in the Delete section. In the event of the flash being inaccessible, please reboot the system and retry the operation.

Follow the procedures below to transfer files from any local station to the node:

1 Locate the file to be transferred from the local station.

2 Select a directory from the node.

3 Click the Download button to start downloading files.

4 Users can verify the process by comparing the file size. Click Refresh and compare the file size on the local and remote systems. If the size is the same, the transfer was successful. If the file does not show up on the remote system directory structure, download failed. Repeat the file transfer procedures.



5 If the ICM3 flash is full or there isn't enough space for the files to be downloaded, Netman 4000 prompts an error message. Delete unused files on ICM3.

Upload Follow the procedures below to transfer files from the node to any local station:

1 Select a file from the node.

2 Locate the directory on the local station to place the node files.

3 Click the Upload button to start uploading files.

4 Users can verify the process by comparing the file size. Click Refresh and compare the file size on the local and remote systems. If the size is the same, the transfer was successful. If the file does not show up on the local system directory structure, upload failed. Repeat the file transfer procedures.

Delete Follow the procedures below to permanently delete files from the node:

WARNING: Avoid using this deletion command. Removal of certain files will cause system malfunctions. Please consult with Customer Service before deleting any system files.

1 Select a file from the node.

2 Click the Delete button to remove the selected files.

Note: Files in the running directory cannot be deleted.

ICM3 Module Backup Netman 4000 also provides an option to backup the entire node.

In the Netman 4000 main system map, right click a node and select Backup Node to start backing up all the files in the node.


ICM3 Module Replacement 433

Figure 330 Backup Node

ICM3 Module Replacement

The new ICM3 from the factory must not be directly plugged in a live system, with a faulty ICM3. Uploading the new ICM3 with the existing backed up database must be done in a different iAN8K B1000 system than in the live system where the bad ICM3 resides. This is due to the new ICM3 initially has a different database and if inserted into a live system, it would cause all the IPxDSL modules to reset and interrupt user traffic.

Note: When replacing/switching the ICM3 module, the new ICM3 module must contain the same configuration as the original ICM3 modules or contain no configuration in order to prevent configuration conflict.

Once the new ICM3 contains the identical IP and module database then replace the bad ICM3 without interrupting user traffic.

The iAN8K B1000 system has been designed such that the IPxDSL modules can continue to provide basic user service without the ICM3 for a brief period during which the faulty ICM3 is being replaced.

WARNING: There should not be any module resets when there is no ICM3 in the system. Doing so the module will be rendered out of service. If the system is reset, the module will not come up again without the ICM3.

The ICM3 module from the factory comes with an initial factory configuration and a default IP address (10.20.30.1). To upload the configuration and



provisioning data stored in a client PC, first the IP address must be changed, so that communication with the ICM3 can be setup. This is done by accessing the ICM3 module through its maintenance port (Serial Port on its faceplate) using windows standard hyper-terminal software.

Note: When replacing/switching the ICM3 module, the new ICM3 module must contain the same configuration as the original ICM3 modules or contain no configuration in order to prevent configuration conflict.

Follow the steps below to replace an ICM3 module:

1 Connect a Serial cable between the Console Port of ICM3 and a COM port of Management Terminal.

2 Run HyperTerminal application on the Management terminal. Set the COM port Communication Port parameters as 9600, N, 8, 1.

3 Press the Enter key on the key board and follow the command below:

ICM3 board 172.16.4.155

login: admin

Password:


AN2000_IB#

4 Use this command to setup the node IP address. The Netmask parameter is optional and if not specified the system takes the default Netmask as 255.255.255.0.

ip management address <A.B.C.D> netmask <A.B.C.D>

5 Use this command to setup Netman server address and primary/secondary trap destinations.

snmp netman-destination <A.B.C.D> <primary/secondary>

Note: Refer to iAN8K B1000 Release 3.1 CLI User Manual for more information of gateway ip, router configuration, etc.

6 For B820 chassis, connect PCU NMS IN Port to the LAN using a CAT5 ethernet cable. For B1000 chassis, use NMS IN Port on ICM3 adapter module.

7 Connect CLI PC to LAN using a CAT5 ethernet cable.

8 Start communication with the node. You are now ready to carry out the Provisioning and Management.


Remote Access 435

Remote Access iAN8K B1000 supports a direct CLI interface and Telnet access of the node for maintenance purpose. Please refer to the following manuals for more information:

■ iAN8K B1000 Release 3.1 Command Line Interface (CLI) User Manual UTSI-NJTC-20050624

■ iAN8K B1000 Release 3.1 IP Service Module (ISM) Command Line Interface (CLI) User Manual UTSI-NJTC-20050698

■ iAN8K B1000 Release 3.1 ATM Service Module (ASM) Command Line Interface (CLI) User Manual UTSI-NJTC-20050700




A
ACCESS CONFIGURATION EXAMPLE
This document provides the following ACL application examples for development and field engineers for ACL deployment:

■ PPPoE Access Deny Configuration Example

■ IP Address Conflict

■ Deny Specific Subscriber To Access FTP

■ Prohibit A Specific Subscriber To Access ABC IM Service

PPPoE Access Deny Configuration Example

Scenario This is an example of using ACL to deny PPPoE access. Through ACL, the user can prohibit subscriber access through PPPoE and at the same time allow access through other methods (i.e. dedicated line, etc.).

Analysis PPPoE relies on two widely accepted standards: PPP and Ethernet. PPPoE is a specification for connecting users on an Ethernet to the Internet through a common broadband medium, such as a single DSL line, wireless device or cable modem. For Ethernet, all users over the Ethernet share a common connection. So the Ethernet principle of multiple users in a LAN combines with the PPP principle of serial connections.

In other words PPPoE is a relay protocol between Ethernet and dialup. It inherits the advantage of the speed of the Ethernet, the simplicity of PPP dialup, with subscriber authentication, IP distribution, etc. In the actual implementation, PPPoE emulates Ethernet's mechanism. It connects the 10 BaseT port of ADSL Modem to the internal Ethernet. ADSL Modem uses RFC1483 bridging to encapsulate PPP packets by LLC/SNAP. By connecting the 2 PVCs between ADSL Modem and network side broadband access server, dynamic PPP access is accomplished. PPPoE access uses 1 PVC between network side and ADSL Modem to accomplish multiple access on Ethernet.

There are 2 phases for establishing point-to-point protocol on one Ethernet: Discovery phase and Session phase. In Discovery phase, subscriber PC broadcasts and searches for all possible access multiplexers and it then obtains the Ethernet address. Then it selects the access concentrator that needs to be connected for establishing PPP dialog. In Session phase, subscriber and access concentrator start PPP dialog according to PPP dialog connecting


438 APPENDIX A: ACCESS CONFIGURATION EXAMPLE

parameters agreed to in the Discovery phase. Correspondingly, Ethernet point-to-point protocol frame has 2 types of formats: In Discovery phase, Ethernet frame type field is 0x8863; In Session phase, Ethernet frame type field is 0x8864. IEEE certifies both formats. When creating a configuration, the user may consider denying a specific type of Ethernet frame (types 0x8863). By doing this, PPPoE access deny is accomplished from the beginning (Discovery phase).

Solution

1 From Profile menu, select Access List Profiles shown in Figure 331 to open the access list profile summary shown in Figure 332.

Figure 331 Profile Menu - Access List Profiles

Figure 332 Access List Profile Summary Window

2 Click Add in Figure 332 to create profiles.


PPPoE Access Deny Configuration Example 439

3 Add 2 profiles. Configure first profile to Deny from Ethernet Type of 0x8863 to Any as shown in Figure 333.

Figure 333 PPPoE Access Deny - Add Access List Profile - Deny

4 Configure second profile to Permit from Any to Any as shown in Figure 334.



Figure 334 PPPoE Access Deny - Add Access List Profile - Permit

5 The new profiles are shown in Figure 335.

Figure 335 PPPoE Access Deny - 2 Profiles Added

6 Select the Access List of the IPxDSL module to open Figure 336.


PPPoE Access Deny Configuration Example 441

Figure 336 PPPoE Access Deny - IPxDSL Module - Access List

7 Select the WAN port and click Edit. Apply both profiles to Outbound of WAN port as shown in Figure 337.



Figure 337 PPPoE Access Deny - IPxDSL Module - Applying Profiles to Outbound

8 The result is shown in Figure 338. Access control configuration for PPPoE access denial is complete.


IP Address Conflict 443

Figure 338 PPPoE Access Deny - Complete

Conclusion After applying the above configuration to iAN8K B1000, subscriber's PPPoE will then be prohibited. The above configuration denies PPPoE for all subscribers (24 lines) on IPxDSL card. Similarly, this scheme can also be used to deny PPPoE for some specific subscribers of a specific ADSL board.

IP Address Conflict

Scenario For subscriber's PC dialing up through PPPoE, the connectivity is:

■ PC connects UT300-R modem

■ UT300-R modem connects to iAN8K B1000

■ iAN8K B1000 modem connects to B-RAS

After subscriber PC has dialed up, an error message is displayed (192.168.1.3 and system hardware address conflict).

Analysis With UT-300R modem default setting, modem starts the internal DHCP Server with address pool in 192.168.1.m subnet. After subscriber's PC is connected to modem, the network card obtains an IP address from 192.168.1.n pool. When 2



subscribers obtain the same IP address, the address conflict error message occurs.

Shutting down the DHCP service gateway of the modem can solve this problem easily, but modifying modem configuration becomes complicated when a lot of them are deployed. In such scenario, modifying ACL of iAN8K B1000 can solve this problem.

Solution







3 Add 2 profiles. Configure first profile to Permit from Any to Any as shown in Figure 341.

Figure 341 IP Address Conflict - Add Access List Profile - Permit

4 Configure second profile to Deny from ARP-send-IP to Any as shown in Figure 342. Configure the ARP sent IP address to the modem DHCP address pool (usually is 192.168.1.0).



Figure 342 IP Address Conflict - Add Access List Profile - Deny


Figure 343 IP Address Conflict - 2 Profiles Added




Figure 344 IP Address Conflict - IPxDSL Module - Access List

7 Select the WAN port and click Edit. Apply both profiles to Outbound of WAN port as shown in Figure 345.



Figure 345 IP Address Conflict - IPxDSL Module - Applying Profiles to Outbound

8 The result is shown in Figure 346. Access control configuration for IP address conflict is complete.


Deny Specific Subscriber To Access FTP 449

Figure 346 IP Address Conflict - Complete

Conclusion After configuring iAN8K B1000 with above settings, iAN8K B1000 will not forward the ARP messages received from subscriber PC. This way other PC will not have any information of the IP address. Even when the IP addresses of subscribers duplicate, there will be no IP conflict error message.

Deny Specific Subscriber To Access FTP

Scenario Administrator of network management center wants to deny a specific subscriber from using FTP.

Analysis FTP uses TCP port 21. Therefore the solution is to block this port number through ACL of iAN8K B1000.

Solution







3 Add 2 profiles. Configure first profile to Deny from Any to TCP Port as shown in Figure 349. Configure the port number to 21.



Figure 349 FTP Access Deny - Add Access List Profile - Deny

4 Configure second profile to Permit from Any to Any as shown in Figure 350.



Figure 350 FTP Access Deny - Add Access List Profile - Permit


Figure 351 FTP Access Deny - 2 Profiles Added




Figure 352 FTP Access Deny - IPxDSL Module - Access List

7 Select the WAN port and click Edit. Apply both profiles to Inbound and Outbound of WAN port as shown in Figure 353 and Figure 354



Figure 353 FTP Access Deny - IPxDSL Module - Applying Profiles to Inbound



Figure 354 FTP Access Deny - IPxDSL Module - Applying Profiles to Outbound




Figure 355 FTP Access Deny - Complete

Conclusion This scheme prohibits a specific subscriber to use FTP. Network management administrator can also apply similar schemes to prohibit subscriber to use other applications such as telnet.

Prohibit A Specific Subscriber To Access ABC IM Service

Scenario Network Administrator wants to prohibit subscriber from using ABC IM service for online chat.

Analysis Must obtain the exact domain name and IP address of the server that is frequently used by ABC IM Software. For example:

■ sz.tencent.com 61. 144. 238. 145

■ sz2.tencent.com 61. 144. 238. 146

■ sz3.tencent.com 202. 104. 129. 25

Use ACL to block the IP address of ABC IM server.


Prohibit A Specific Subscriber To Access ABC IM Service 457

Solution





3 Add 3 profiles. Configure first profile to Deny from Any to IP Address as shown in Figure 358. Click the Range radio button and configure the starting and ending IP addresses.



Figure 358 ABC IM Service Access Deny - Add Access List Profile - Deny IP Address Range

4 Configure second profile to Deny from Any to IP Address as shown in Figure 359. Configure a specific IP address and its netmask.



Figure 359 ABC IM Service Access Deny - Add Access List Profile - Deny Specific IP Address

5 Configure third profile to Permit from Any to Any as shown in Figure 360.



Figure 360 ABC IM Service Access Deny - Add Access List Profile - Permit


Figure 361 ABC IM Service Access Deny - 3 Profiles Added




Figure 362 ABC IM Service Access Deny - IPxDSL Module - Access List

8 Select the WAN port and click Edit. Apply all three profiles to Outbound of WAN port as shown in Figure 363.



Figure 363 ABC IM Service Access Deny - IPxDSL Module - Applying Profiles to Outbound




Figure 364 ABC IM Service Access Deny - Complete

Conclusion The scheme prohibits a specific subscriber to use ABC IM service. Network administrator can also shut down a specific port used by ABC IM in order to prohibit ABC IM service.




UTStarcom, Inc. USA 1275 Harbor Bay Parkway Alameda, CA 94502, USA Tel. 510-864-8800 Fax. 510-864-8802

ChinaNo. 368 Liuhe Road,Hi-Tech Industry Development Zone, Binjiang, Hangzhou 310053, PRC+86-571-81920000

India805 Signature Towers II,South City IGurgaon, Haryana 122001, India+91 124 5166100

JapanShiba Koen Parktower 9F/10F2-11-1 Shiba-koen, Minato-kuTokyo 105-0011 JAPAN+81-3-6430-8600

EuropeCampus Kronberg 7Kronberg, 61476Germany+49 (617) 3946-3460

Latin America2801 SW 149th AveSuite 100Miramar, FL 33027, USA954-447-3077

About UTStarcom www.utstar.com

Headquartered in the United States with sales, support, and manufacturing facilities worldwide, UTStarcom designs, manufactures, sells, and installs an integrated suite of wireless and wireline access network and switching systems. UTStarcom’s complete suite of network equipment gives telecommunication service providers the means to cost-effectively provide efficient and scalable voice, data, and Internet services around the globe.

Copyright © 2006 UTStarcom, the UTStarcom logo, !-Volution, AIRSTAR, AN-2000, AN-FTTB, CommWorks, the CommWorks logo, iAN, iCell, Internode, Intranode, iPATH, ISP, MovingMedia, mSwitch, Next Generation Network Technology. Now, NGDLC, PAS, PAS Wireless, Seamless World, Softexchange, Sonata, Sonata Access Tandem, Sonata HLR, Sonata IP, Sonata MSC, Sonata WLL, Telos, Total Control, Unitech, WACOS, WICOPS, WLL, and Xtreme IP are registered trademarks or trademarks of UTStarcom, Inc. and its subsidiaries.

Documents

En iAN8K B1000 Operation Guide R3.2 V1