Académique Documents
Professionnel Documents
Culture Documents
Issue 1.1
iAN8K B1000
Release 3.2 Operations Manual
Issue 1.1
Copyright 2006, UTStarcom, Inc. All rights reserved. No part of this documentation may be reproduced in any form or by any means or used to make any derivative work (such as translation, transformation, or adaptation) without prior written permission from UTStarcom, Inc. UTStarcom, Inc. reserves the right to revise this documentation and to make changes in content from time to time without obligation 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 not limited to, the implied warranties of merchantability and fitness for a particular purpose. UTStarcom may make improvements or 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 you subject to the following: United States Government Legend: All technical data and computer software is commercial in nature and developed solely at 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 in UTStarcom's standard commercial license for the Software. Technical data is provided with limited rights only as provided in DFAR 252.227-7015 (Nov 1995) or FAR 52.227-14 (June 1987), whichever is applicable. You agree not to remove or deface any portion of any legend provided on any licensed program or documentation contained in, or delivered to you in conjunction with, 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, 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. Intel and Pentium are registered trademarks of the Intel Corporation or its subsidiaries in the United States and other countries. 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 Oracle Corporation. 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
NETWORK MANAGEMENT
System Structure...................................................................................................................... 27 Functional Components ........................................................................................................... 27 Primary Management Functions .............................................................................................. 28 Basic Management Functions ............................................................................................ 28 Topology Management.................................................................................................. 28 Fault Management ........................................................................................................ 28 Security Management ................................................................................................... 28 Log Management .......................................................................................................... 28 System Tools................................................................................................................. 29
DEVICE MANAGER
Configuration Menu.................................................................................................................. 33 Get Configuration ............................................................................................................... 33 Save Configuration ............................................................................................................. 33 Erase Configuration............................................................................................................ 33 Erase Shelf Configuration................................................................................................... 34 System Log......................................................................................................................... 34 System Log Data........................................................................................................... 37 Radius Server..................................................................................................................... 40 RADIUS Server ............................................................................................................. 41 Statistics ........................................................................................................................ 42 Telnet Port .......................................................................................................................... 43 Maximum Power Setting..................................................................................................... 44 Packet Count Reset............................................................................................................ 45 Node ID .............................................................................................................................. 45 iSmart Feature.................................................................................................................... 46 LTC Configure .................................................................................................................... 47 Profile Menu............................................................................................................................. 50 ADSL Line Profile ............................................................................................................... 50
July 2006
Configuration Template ................................................................................................. 50 Service Profile............................................................................................................... 51 Spectrum Profile............................................................................................................ 53 SHDSL Line Profile ............................................................................................................ 58 Ethernet PM Profile ............................................................................................................ 61 ADSL PM Profile ................................................................................................................ 63 Access List Profile .............................................................................................................. 65 Packet Priority Classification .............................................................................................. 70 Traffic Management Profile ................................................................................................ 78 Batch Menu.............................................................................................................................. 81 Create ATM VC .................................................................................................................. 81 Delete ATM VC................................................................................................................... 83 Module Configuration ......................................................................................................... 84 Video Service Menu................................................................................................................. 87 Multicast Group Packaging ................................................................................................ 88 Default Rate .................................................................................................................. 88 Multicast Group............................................................................................................. 89 Multicast Package......................................................................................................... 91 Access Control ................................................................................................................... 92 Account lockout Policy .................................................................................................. 92 Reset Period ................................................................................................................. 93 User Account ................................................................................................................ 94 Usage Statistics.................................................................................................................. 96 Call Usage Recognition Time........................................................................................ 96 Usage Statistics ............................................................................................................ 96 Tools Menu .............................................................................................................................. 97 MAC Tracing....................................................................................................................... 97
PROVISIONING - NODE
System ..................................................................................................................................... 99 IP Address ............................................................................................................................. 100 Time Server ........................................................................................................................... 103 NMP Access .......................................................................................................................... 104 SNMP ............................................................................................................................... 105 Telnet................................................................................................................................ 106 ARP ....................................................................................................................................... 107 Routing Table ......................................................................................................................... 109 Reset ......................................................................................................................................111 Master Shelf Configuration .................................................................................................... 114 Slave Shelves Configuration.................................................................................................. 116 Linecard Image File Information ............................................................................................ 118
July 2006
Shelf Level Configuration....................................................................................................... 126 Slot Level Configuration......................................................................................................... 128 ICM3/3G ........................................................................................................................... 129 Forwarding Database ....................................................................................................... 130 Mirror Port......................................................................................................................... 132 Trunk Group...................................................................................................................... 134 Protection Link.................................................................................................................. 137 Redundancy Support........................................................................................................ 139 Redundancy Setup via CLI ......................................................................................... 143 Switchover ........................................................................................................................ 144 VBAS ................................................................................................................................ 145 External Ethernet Port ...................................................................................................... 147 Port Level Configuration ........................................................................................................ 148 Ethernet Port Configuration .............................................................................................. 149 Internal Ethernet Ports ................................................................................................ 150 External Ethernet Ports ............................................................................................... 152 Trunk Ports.................................................................................................................. 155 RSTP ................................................................................................................................ 158 RSTP........................................................................................................................... 158 RSTP Port ................................................................................................................... 160 VLAN ................................................................................................................................ 162 General ....................................................................................................................... 165 VLAN Setup ................................................................................................................ 167 Routed VLAN Interface ............................................................................................... 170 In-band Management .................................................................................................. 173 Multicast ........................................................................................................................... 175 IGMP Snooping........................................................................................................... 178 General .................................................................................................................. 178 Group Membership ................................................................................................ 179 IGMP Proxy................................................................................................................. 180 General .................................................................................................................. 180 Group Membership ................................................................................................ 181 PIM-SM ....................................................................................................................... 182 General .................................................................................................................. 182 RP Router .............................................................................................................. 183 Multicast Routing Table ......................................................................................... 185 Neighbor Details .................................................................................................... 185 Interface Setup ...................................................................................................... 186 Routing ............................................................................................................................. 188 RIP .............................................................................................................................. 191 General .................................................................................................................. 191 Redistribution Setup .............................................................................................. 192 Neighbor Setup...................................................................................................... 194 Peer Details ........................................................................................................... 195 Key Setup .............................................................................................................. 196 Interface Setup ...................................................................................................... 198 OSPF .......................................................................................................................... 201
iAN8K B1000 Operations Manual
July 2006
General.................................................................................................................. 201 Route Redistribution .............................................................................................. 203 Area Setup............................................................................................................. 205 Address Ranges .................................................................................................... 208 LSDB Table............................................................................................................ 209 Neighbor Details .................................................................................................... 212 Interface Setup ...................................................................................................... 213 ARP............................................................................................................................. 216 DHCP ............................................................................................................................... 219 Server ......................................................................................................................... 219 Profile.......................................................................................................................... 220 Subnet Mapping.......................................................................................................... 224 Pool............................................................................................................................. 226 Map ............................................................................................................................. 228 Lease .......................................................................................................................... 230 Option 60 .................................................................................................................... 231 Option 82 .................................................................................................................... 233 VLAN........................................................................................................................... 234 Packet Classification ........................................................................................................ 236 Masks.......................................................................................................................... 236 Actions ........................................................................................................................ 239 Meters ......................................................................................................................... 242 Flow Counters............................................................................................................. 243 Rules........................................................................................................................... 244 QoS .................................................................................................................................. 246 Priority......................................................................................................................... 247 DSCP Priority.............................................................................................................. 248 Queue Mapping .......................................................................................................... 250 L2 Scheduling ............................................................................................................. 252
July 2006
Configuring Misc............................................................................................................... 269 Configuring T.38 ............................................................................................................... 270 Configuring QoS .................................................................................................................... 271 Configuring TOS/DSCP.................................................................................................... 271 Configuring VLAN Tag ...................................................................................................... 272 Configuring User Interface ..................................................................................................... 274 Node Configuration........................................................................................................... 274 Port Configuration............................................................................................................. 275 Modifying a FXS Port .................................................................................................. 277 Configuring Ring Definition............................................................................................... 277 Configuring MG Media ........................................................................................................... 279 Configuring VoIP Media.................................................................................................... 279 Configuring Jitter Buffer.................................................................................................... 280 Configuring SIP...................................................................................................................... 282 Configuring SIP Port......................................................................................................... 282 SIP Summary Statistics .................................................................................................... 283 SIP Supported Methods ................................................................................................... 283 SIP Methods Statistics...................................................................................................... 284 Configuring SIP UA................................................................................................................ 285 General Config ................................................................................................................. 285 Server Table ..................................................................................................................... 286 MG Table .......................................................................................................................... 287 User Table ........................................................................................................................ 288
July 2006
10
Port Level Configuration ........................................................................................................ 311 WAN Port.......................................................................................................................... 312 xDSL................................................................................................................................. 313 ADSL Port ................................................................................................................... 314 SHDSL Port ................................................................................................................ 315 Line Status .................................................................................................................. 317 Channel Status............................................................................................................ 320 Previous Status ........................................................................................................... 321 Status Change Time Info............................................................................................. 322 Rate Summary ............................................................................................................ 323 Port Label.................................................................................................................... 324 Bit Loading .................................................................................................................. 325 iSmart.......................................................................................................................... 326 CPE............................................................................................................................. 328 ATM .................................................................................................................................. 330 ATM VC....................................................................................................................... 331 Traffic Profile ............................................................................................................... 332 Bridge ............................................................................................................................... 335 MAC Address Per Port................................................................................................ 335 Packet Policing ........................................................................................................... 337 Packet Policing Setup............................................................................................ 337 IP Address Summary............................................................................................. 339 Forwarding Database.................................................................................................. 339 ARP Table ................................................................................................................... 342 Flood Limit .................................................................................................................. 343 IGMP ................................................................................................................................ 344 Authentication Parameter ........................................................................................... 344 CAC ............................................................................................................................ 345 Multicast Group........................................................................................................... 346 Multicast Host ............................................................................................................. 347 VLAN ................................................................................................................................ 348 VLAN........................................................................................................................... 349 Ingress Rule................................................................................................................ 351 VLAN Untag ................................................................................................................ 353 Access List ....................................................................................................................... 353 QoS .................................................................................................................................. 356 Packet Priority............................................................................................................. 358 Port Based Priority ...................................................................................................... 360 802.1p Tag .................................................................................................................. 362
PERFORMANCE MANAGEMENT
ICM3 Module ......................................................................................................................... 366 Ethernet PM ..................................................................................................................... 366 General Counters........................................................................................................ 366 Error Counters ............................................................................................................ 368 Traffic Load ................................................................................................................. 370 Bridge PM......................................................................................................................... 371
July 2006
11
Control......................................................................................................................... 371 5 Minutes Report......................................................................................................... 372 15 Minutes Report....................................................................................................... 373 IPADSLx Module .................................................................................................................... 373 ATM PVC.......................................................................................................................... 374 Bridge Port........................................................................................................................ 374 Bridge PM Control....................................................................................................... 375 Bridge.......................................................................................................................... 375 5 Minutes Report......................................................................................................... 377 15 Minutes Report....................................................................................................... 378 WAN Port.......................................................................................................................... 378 Threshold Controls...................................................................................................... 378 15 Minutes................................................................................................................... 379 24 Hours...................................................................................................................... 381 ADSL Port......................................................................................................................... 381 ADSL 15 Minutes Summary........................................................................................ 381 ADSL 24 Hours Summary........................................................................................... 383 Threshold Controls...................................................................................................... 383 ATUC 15 Minutes ........................................................................................................ 384 ATUC 24 Hours ........................................................................................................... 386 ATUR 15 Minutes ........................................................................................................ 386 ATUR 24 Hours ........................................................................................................... 386 Channel Level ............................................................................................................. 386 Downstream 15 Minutes ........................................................................................ 386 Downstream 24 Hours ........................................................................................... 387 Upstream 15 Minutes............................................................................................. 387 Upstream 24 Hours................................................................................................ 387 IPSHDSL3 Module ................................................................................................................. 388
DIAGNOSTICS
F4/F5 Loopback ..................................................................................................................... 391 DELT ...................................................................................................................................... 394 SELT ...................................................................................................................................... 399
10
FAULT MANAGEMENT
Netman 4000 ......................................................................................................................... 406 Audible And Visual Alarm ................................................................................................. 406 Alarm Presentation ........................................................................................................... 406 Alarm Report.......................................................................................................................... 407 Alarm Report .................................................................................................................... 408 Alarm Summary................................................................................................................ 412 Filter Setup ....................................................................................................................... 413 Alarm List ............................................................................................................................... 414 Node Alarm....................................................................................................................... 415 External Alarm .................................................................................................................. 416 ICM3 Alarm....................................................................................................................... 416
iAN8K B1000 Operations Manual
July 2006
12
IP-ADSLx Alarm ............................................................................................................... 416 IP-SHDSL3 Alarm ............................................................................................................ 418 iFXS1 Alarm ..................................................................................................................... 419 Event List for iFXS1 Module............................................................................................. 420
11
SYSTEM ADMINISTRATION
Node File Management ......................................................................................................... 423 Software Upgrade .................................................................................................................. 424 ICM3 Module .................................................................................................................... 424 Upgrade with A Redundant ICM3 Module .................................................................. 425 IPxDSL Modules............................................................................................................... 427 ISM Module ...................................................................................................................... 428 ASM Module..................................................................................................................... 428 File Transfer........................................................................................................................... 428 Download ......................................................................................................................... 431 Upload .............................................................................................................................. 432 Delete ............................................................................................................................... 432 ICM3 Module Backup ............................................................................................................ 432 ICM3 Module Replacement ................................................................................................... 433 Remote Access...................................................................................................................... 435
July 2006
13
LIST OF TABLES
Table 1 Table 2 Table 3 Table 4 Table 5 Table 6 Table 7 Table 8 Table 9 Table 10 Table 11 Table 12 Table 13 Table 14 Table 15 Table 16 Table 17 Table 18 Table 19 Table 20 Table 21 Table 22 Table 23 Table 24 Table 25 Table 26 Table 27 Table 28 Table 29 Table 30 Table 31 Table 32 Table 33 Table 34 Table 35 Table 36 Table 37 Table 38 Table 39 Table 40 Table 41 Table 42 Table 43 Table 44 Table 45 Table 46 Table 47 Table 48 Table 49 Table 50 Table 51 Table 52
July 2006
Notice Icon Descriptions......................................................................................... 24 Text Convention Descriptions................................................................................. 24 iAN8K B1000 Release 3.1 Documentation Set ...................................................... 25 Configuration - System Log Table .......................................................................... 36 Configuration - RADIUS Server - RADIUS Server - Add Table .............................. 42 RADIUS Server - RADIUS Server - Statistics Table .............................................. 43 Profile - ADSL Line Profile - Service Profile Table ................................................. 53 Profile - ADSL Line Profile - Spectrum Profile Table .............................................. 56 Line Standard / Line Card Co-relation Table .......................................................... 58 Profile - SHDSL Line Profile - Add Table............................................................... 60 Profile - Ethernet PM Profile Table ......................................................................... 62 Profile - ADSL PM Profile Table ............................................................................. 64 Profile - Access List Profile - Add - From / To Table .............................................. 67 ACL Rule Combination Table ................................................................................. 67 Profile - Packet Priority Classification Table........................................................... 71 Profile - Packet Priority Classification - Add - Type Table ...................................... 71 Profile - Traffic Management Profile - Add / Modify Tables .................................... 80 Batch - Create ATM VC Table................................................................................ 83 Batch - Module Configuration Tables .................................................................... 85 Video Service - Multicast Group Packaging - Multicast Group Field Description ... 89 Video Service - Multicast Group Packaging - Multicast Package Field Description 91 Video Service - Access Control - Account Lockout Policy Field Description .......... 93 Node - System Table............................................................................................ 100 Node - IP Address Table ...................................................................................... 101 Node - ARP Field Description............................................................................... 108 Node - Routing Table Table ................................................................................. 110 Node - Master Shelf Configuration Table ............................................................. 115 Node - Slav Shelves Configuration Table............................................................. 117 Node - Linecard Image File Information Table ..................................................... 119 ICM3/3G - Module Summary Table...................................................................... 126 ICM3/3G Module Placements Details................................................................... 128 ICM3/3G - ICM3/3G Table.................................................................................... 130 ICM3/3G - Forwarding Database Table................................................................ 131 ICM3/3G - Mirror Port Table ................................................................................. 134 ICM3/3G - Trunk Group Table.............................................................................. 136 ICM3/3G - Protection Link Table .......................................................................... 139 ICM3/3G - VBAS Table ........................................................................................ 147 ICM3/3G - Ethernet Port Configuration - Internal Ethernet Ports Table ............... 152 ICM3/3G - Ethernet Port Configuration - External Ethernet Ports Table .............. 154 ICM3/3G - Ethernet Port Configuration - Trunk Ports Table................................. 157 ICM3/3G - RSTP - RSTP Table............................................................................ 159 ICM3/3G - RSTP - RSTP Port Table .................................................................... 161 ICM3/3G - VLAN - General Table......................................................................... 166 ICM3/3G - VLAN - VLAN Setup Table.................................................................. 168 ICM3/3G - VLAN - VLAN Interface - Add Table ................................................... 173 ICM3 - VLAN -Inband VLAN Interface - Add Table .............................................. 175 ICM3/3G - Multicast - IGMP Snooping - General Table ....................................... 178 ICM3/3G - Multicast - IGMP Snooping - Group Membership Table ..................... 180 ICM3/3G - Multicast - IGMP Proxy - General Table ............................................. 181 ICM3 - Routing - Routing Table Field Descriptions .............................................. 189 ICM3 - Routing - RIP - General Table .................................................................. 192 ICM3 - Routing - RIP - Redistribution Setup Table............................................... 193
iAN8K B1000 Operations Manual
14
Table 53 ICM3 - Routing - RIP - Neighbor Details Table .....................................................195 Table 54 ICM3 - Routing - RIP - Peer Details Table ............................................................196 Table 55 ICM3 - Routing - RIP - Key Setup Table ...............................................................197 Table 56 ICM3 - Routing - RIP - Interface Setup Table .......................................................199 Table 57 ICM3 - Routing - OSPF - General Table ...............................................................202 Table 58 ICM3 - Routing - OSPF - Route Redistribution Table ...........................................204 Table 59 ICM3 - Routing - OSPF - Area Setup Table ..........................................................206 Table 60 ICM3 - Routing - OSPF - Address Ranges Table .................................................208 Table 61 ICM3 - Routing - OSPF - LSDB Table...................................................................210 Table 62 ICM3 - Routing - OSPF - LSDB Table - LS Type Table ........................................211 Table 63 ICM3 - Routing - OSPF - Neighbor Details Table .................................................213 Table 64 ICM3 - Routing - OSPF - Interface Setup Table....................................................215 Table 65 ICM3 - Routing - ARP Field Description ................................................................217 Table 66 ICM3/3G - DHCP - Server Field Description .........................................................220 Table 67 ICM3/3G - DHCP - Profile - Add Table..................................................................223 Table 68 ICM3/3G - Packet Classification - Masks - Add Field Description.........................238 Table 69 ICM3/3G - Packet Classification - Actions - Add Field Description .......................241 Table 70 ICM3/3G - Packet Classification - Meters - Add Field Description ........................243 Table 71 ICM3/3G - QoS - DSCP Mapping..........................................................................252 Table 72 ICM3/3G - QoS - L2 Scheduling - Weight for WRR / SP+WRR ............................254 Table 73 PCU - Module Summary Table .............................................................................257 Table 74 PCU Module Placements Details ..........................................................................258 Table 75 PCU - PCU Table ..................................................................................................259 Table 76 PCU - Clock Source Table ....................................................................................261 Table 77 PCU - Alarm Indication Table ................................................................................262 Table 78 PCU - PDP Table ..................................................................................................263 Table 79 iFXS1 Module Information Window Field Description ...........................................265 Table 80 IP Configuration Window Field Description ...........................................................267 Table 81 Call Server Window Field Description ...................................................................269 Table 82 Misc Configuration Window Field Description .......................................................270 Table 83 T.38 Window Field Descriptio................................................................................271 Table 84 TOS/DSCP Window Field Description ..................................................................272 Table 85 VLAN Tag Window Field Description ...................................................................274 Table 86 Node Configuration Window Field Description ......................................................275 Table 87 Port Configuration Window Field Description ........................................................276 Table 88 Ring Definition Window Field Description .............................................................278 Table 89 VoIP Media Window Field Description .................................................................280 Table 90 Jitter Buffer Window Field Description .................................................................281 Table 91 SIP Port Window Field Description .......................................................................283 Table 92 SIP Supported Method Window Field Description ................................................284 Table 93 General Configuration Window Field Description..................................................286 Table 94 General Configuration Window Field Description..................................................287 Table 95 MG Table Window Field Description ....................................................................288 Table 96 User Table Window Field Description ...................................................................289 Table 97 ICM3 - Module Summary - Module Information Table...........................................294 Table 98 ICM3 - Module Summary - Active Ports Table ......................................................295 Table 99 IPxDSL Module Placements Details......................................................................296 Table 100 IPxDSL - IPxDSL Table.........................................................................................299 Table 101 Format of Circuit ID Sub-option in DHCP Option 82 .............................................305 Table 102 Format of Remote ID Sub-option in DHCP Option 82 ...........................................306 Table 103 IPxDSL - Customized Filter Table .........................................................................307 Table 104 IPxDSL - PPPoE Snooping Table .........................................................................311 Table 105 IPxDSL - ADSL - ADSL Port Table .......................................................................315 Table 106 IPxDSL - SHDSL - SHDSL Port Table ..................................................................316 Table 107 IPxDSL - ADSL - Line Status Table ......................................................................318
iAN8K B1000 Operations Manual July 2006
15
Table 108 IPxDSL - SHDSL - Line Status Table ................................................................... 319 Table 109 IPxDSL - ADSL - Channel Status Table ............................................................... 320 Table 110 IPxDSL - ADSL - Status Change Time Info Table................................................ 323 Table 111 IPxDSL - ADSL Rate Summary Table.................................................................. 324 Table 112 IPxDSL - ADSL - CPE Table ................................................................................ 330 Table 113 IPxDSL - ATM - ATM VC Encapsulation Table .................................................... 331 Table 114 IPxDSL - Traffic Profile - Modification Table......................................................... 333 Table 115 IPxDSL - Bridge - MAC Address Per Port Table .................................................. 336 Table 116 IPxDSL - Bridge - Packet Policing - Packet Policing Setup Table........................ 338 Table 117 IPxDSL - Bridge - Packet Policing IP Address Summary Table ........................... 339 Table 118 IPxDSL - Bridge - Forwarding Database Table .................................................... 341 Table 119 IPxDSL - Forwarding Database - Add Table ........................................................ 341 Table 120 IPxDSL - Bridge - ARP Table ............................................................................... 343 Table 121 IPxDSL - IGMP - Multicast Group Table............................................................... 347 Table 122 IPxDSL - IGMP - Multicast Host Table ................................................................. 348 Table 123 IPxDSL- QoS - Recommended User Priority to Traffic Class Mappings .............. 357 Table 124 IPxDSL - QoS - 802.1p Tag Marking on Line Card .............................................. 358 Table 125 IPxDSL - QoS - Port Based Priority - Tag Operation Table.................................. 362 Table 126 ICM3 - Ethernet PM - General Counters Table .................................................... 367 Table 127 ICM3 - Ethernet PM - Error Counters Table ......................................................... 369 Table 128 ICM3 - Ethernet PM - Traffic Load Table.............................................................. 370 Table 129 ICM3 - Bridge PM - Control Table ........................................................................ 371 Table 130 ICM3 - Bridge PM - 5 Minutes Report Table ........................................................ 372 Table 131 IPADSLx - ATM PVC Table.................................................................................. 374 Table 132 IPADSLx - Bridge Port - Bridge PM Control Table ............................................... 375 Table 133 IPADSLx - Bridge Port - Bridge Table .................................................................. 376 Table 134 IPADSLx - Bridge Port - 5 Minutes Report Table ................................................. 377 Table 135 IPADSLx - WAN Port - Thresholds Control Table ................................................ 379 Table 136 IPADSLx - WAN Port - 15 Minutes Table ............................................................. 380 Table 137 IPADSLx - ADSL Port - ADSL 15 Minutes Summary Table ................................. 382 Table 138 IPADSLx - ADSL Port - Thresholds Control Table ............................................... 384 Table 139 IPADSLx - ADSL Port - ATUC 15 Minutes Table ................................................. 385 Table 140 IPADSLx - Channel - Downstream 15 Minutes Table .......................................... 387 Table 141 IPSHDSL3 - Bridge Table..................................................................................... 388 Table 142 SELT - Test Result Field Description ................................................................... 400 Table 143 Node Alarm Tree Entity ........................................................................................ 407 Table 144 Alarm Report - Subtree......................................................................................... 411 Table 145 Alarm Report - Alarm Class.................................................................................. 412 Table 146 Alarm Report - Alarm Severity.............................................................................. 412 Table 147 Alarm Report - Alarm List Entity ........................................................................... 412 Table 148 Node Alarm List .................................................................................................... 415 Table 149 External Alarm List ............................................................................................... 416 Table 150 ICM3 Alarm List .................................................................................................... 416 Table 151 IP-ADSLx Alarm List............................................................................................. 416 Table 152 IP-SHDSL3 Alarm List .......................................................................................... 418 Table 153 Alarm List of iFXS1 Based on SIP........................................................................ 419 Table 154 Alarm List of RTP Related .................................................................................... 419 Table 155 Alarm List of Uplink FE Interface .......................................................................... 420 Table 156 Event List Based on SIP....................................................................................... 420 Table 157 Basic Event List .................................................................................................... 421 Table 158 Node File Description ........................................................................................... 424
July 2006
16
LIST OF FIGURES
Figure 1 Figure 2 Figure 3 Figure 4 Figure 5 Figure 6 Figure 7 Figure 8 Figure 9 Figure 10 Figure 11 Figure 12 Figure 13 Figure 14 Figure 15 Figure 16 Figure 17 Figure 18 Figure 19 Figure 20 Figure 21 Figure 22 Figure 23 Figure 24 Figure 25 Figure 26 Figure 27 Figure 28 Figure 29 Figure 30 Figure 31 Figure 32 Figure 33 Figure 34 Figure 35 Figure 36 Figure 37 Figure 38 Figure 39 Figure 40 Figure 41 Figure 42 Figure 43 Figure 44 Figure 45 Mask Figure 46 Figure 47 Mask Figure 48 Figure 49 Figure 50
iAN8K B1000 Operations Manual
Invoking Device Manager From Netman 4000 ..................................................... 31 Device Manager Main Window ............................................................................. 32 Configuration - Erase Configuring ........................................................................ 33 Configuration - Erase Shelf Configuring Window ................................................. 34 Configuration - System Log .................................................................................. 36 Configuration - System Log - Add ........................................................................ 37 Configuration - RADIUS Server - RADIUS Server ............................................... 41 Configuration - RADIUS Server - RADIUS Server - Add ...................................... 41 RADIUS Server - RADIUS Server - Statistics ...................................................... 43 Configuration - Telnet Port ................................................................................... 44 Configuration - Maximum Power Setting .............................................................. 44 Configuration - Packet Count Reset ..................................................................... 45 Configuration - Node ID ........................................................................................ 45 Configuration - iSmart Feature ............................................................................. 47 Configuration - LTC Configure ............................................................................. 48 Configuration - LTC Configure - Add .................................................................... 48 Configuration - LTC Configure - Configure - LTC Splitter ..................................... 49 Configuration - LTC Configure - Configure - Test Timeout ................................... 50 Profile - ADSL Line Profile - Configuration Template Window ............................. 51 Profile - ADSL Line Profile - Configuration Template - Add Window .................... 51 Profile - ADSL Line Profile - Service Profile Window ............................................ 52 Profile - ADSL Line Profile - Service Profile - Add Window .................................. 52 Profile - ADSL Line Profile - Spectrum Profile Window ........................................ 54 Profile - ADSL Line Profile - Spectrum Profile - Add Window ............................... 55 Profile - SHDSL Line Profile Window ................................................................... 59 Profile - SHDSL Line Profile - Add Window .......................................................... 60 Profile - Ethernet PM Profile ................................................................................. 62 Profile - Ethernet PM Profile - Add / Modify .......................................................... 63 Profile - ADSL PM Profile ..................................................................................... 64 Profile - ADSL PM Profile - Add / Modify .............................................................. 65 Profile - Access List Profile ................................................................................... 66 Profile - Access List Profile - Add - Any to Any .................................................... 68 Profile - Access List Profile - Add - ARP-Send-IP To ARP-Send-MAC ................ 68 Profile - Access List Profile - Add - Ethernet Type To IP Address ........................ 69 Profile - Access List Profile - Add - MAC Address To Protocol Type ................... 69 Profile - Access List Profile - Add - TCP Port To UDP Port .................................. 70 Profile - Packet Priority Classification Window ..................................................... 70 Profile - Packet Priority Classification - Add - DSCP Window .............................. 72 Profile - Packet Priority Classification - Add - VLAN ID Window .......................... 72 Profile - Packet Priority Classification - Add - IP Protocol Type Window .............. 73 Profile - Packet Priority Classification - Add - Send TCP Port .............................. 73 Profile - Packet Priority Classification - Add - Send UDP Port ............................. 74 Profile - Packet Priority Classification - Add - Receive TCP Port ......................... 74 Profile - Packet Priority Classification - Add - Receive UDP Port ......................... 75 Profile - Packet Priority Classification - Add - Source IP - IP Address With Subnet 75 Profile - Packet Priority Classification - Add - Source IP - IP Address Range ...... 76 Profile - Packet Priority Classification - Add - Destination IP - IP Address With Subnet 76 Profile - Packet Priority Classification - Add - Destination IP - IP Address Range 77 Profile - Packet Priority Classification - Add - Ethernet Type ............................... 77 Profile - Packet Priority Classification - Add - TOS Bits ........................................ 78
July 2006
17
Figure 51 Profile - Traffic Management Profile ..................................................................... 79 Figure 52 Profile - Traffic Management Profile - Add / Modify - Strict Priority ...................... 79 Figure 53 Profile - Traffic Management Profile - Add / Modify - Min/Max with Strict Priority 80 Figure 54 Profile - Traffic Management Profile - Add / Modify - Min/Max with WRR ............ 80 Figure 55 Batch - Create ATM VC Window .......................................................................... 82 Figure 56 Batch - Delete ATM VC Window .......................................................................... 84 Figure 57 Batch - Module Configuration Window ................................................................. 84 Figure 58 Video Service - Multicast Group Packaging - Default Rate .................................. 88 Figure 59 Video Service - Multicast Group Packaging - Multicast Group ............................. 89 Figure 60 Video Service - Multicast Group Packaging - Multicast Group - Add ................... 90 Figure 61 Video Service - Multicast Group Packaging - Multicast Package ......................... 91 Figure 62 Video Service - Multicast Group Packaging - Multicast Package - Add ............... 92 Figure 63 Video Service - Access Control - Account Lockout Policy .................................... 93 Figure 64 Video Service - Access Control - Reset Period .................................................... 94 Figure 65 Video Service - Access Control - User Account ................................................... 94 Figure 66 Video Service - Multicast Group Packaging - User Account - Add ....................... 95 Figure 67 Video Service - Usage Statistics - Call Usage Recognition Time ......................... 96 Figure 68 Video Service - Usage Statistics - Usage Statistics ............................................. 97 Figure 69 Tools - MAC Tracing ............................................................................................. 98 Figure 70 Node - System Window ...................................................................................... 100 Figure 71 Node - IP Address Window ................................................................................ 101 Figure 72 Node - Time Server Window .............................................................................. 103 Figure 73 Node - NMP Access Window ............................................................................. 105 Figure 74 Node - NMP Access - Add SNMP Entry Window ............................................... 106 Figure 75 Node - NMP Access - Add Telnet Entry Window ............................................... 106 Figure 76 Node - ARP Window ........................................................................................... 108 Figure 77 Node - ARP - Add Window ................................................................................. 109 Figure 78 Node - Routing Table Window ............................................................................ 110 Figure 79 Node - Routing Table - Add Window .................................................................. 111 Figure 80 Node - Reset Window ......................................................................................... 113 Figure 81 Node - Master Shelf Configuration Window ....................................................... 115 Figure 82 Node - Slav Shelves Configuration Window ....................................................... 117 Figure 83 Node - Linecard Image File Information Window ............................................... 119 Figure 84 Provisioning - ICM3 Window .............................................................................. 121 Figure 85 Provisioning - ICM3GWindow ............................................................................. 122 Figure 86 ICM3 - Node - Reset Window ............................................................................. 124 Figure 87 ICM3G- Module Summary Window .................................................................... 125 Figure 88 ICM3- Module Summary Window ....................................................................... 126 Figure 89 ICM3 - Shelf View Window ................................................................................. 127 Figure 90 ICM3G - Shelf View Window .............................................................................. 128 Figure 91 ICM3/3G - ICM3 Window .................................................................................... 129 Figure 92 ICM3/3G - Forwarding Database Window .......................................................... 131 Figure 93 ICM3/3G - Forwarding Database - Dynamic Entry Window ............................... 132 Figure 94 ICM3/3G - Forwarding Database - Add Window ................................................ 132 Figure 95 ICM3/3G - Mirror Port Window ........................................................................... 133 Figure 96 ICM3/3G - Trunk Group Window ........................................................................ 135 Figure 97 ICM3/3G - Trunk Group - Add Window .............................................................. 136 Figure 98 ICM3/3G - Trunk Group - Add - Note Window .................................................... 137 Figure 99 ICM3/3G - Protection Link Configuration ............................................................ 138 Figure 100 ICM3/3G - Protection Link ................................................................................. 139 Figure 101 ICM3/3G - Redundancy Support Window ......................................................... 143 Figure 102 ICM3/3G - Switchover Widow ............................................................................ 145 Figure 103 ICM3/3G - VBAS Widow .................................................................................... 147 Figure 104 Standby ICM3/3G - External Ethernet Port Window .......................................... 148 Figure 105 ICM3/3G - Ethernet Port Configuration - Internal Ethernet Ports Window ........ 151
July 2006 iAN8K B1000 Operations Manual
18
Figure 106 ICM3/3G - Ethernet Port Configuration - Internal Ethernet Ports - Modify Window 152 Figure 107 ICM3/3G - Ethernet Port Configuration - External Ethernet Ports Window ....... 153 Figure 108 ICM3/3G - Ethernet Port Configuration - External Ethernet Ports - Modify Window 154 Figure 109 ICM3/3G - Ethernet Port Configuration - Trunk Ports Window .......................... 156 Figure 110 ICM3/3G - Ethernet Port Configuration - Trunk Ports - Modify Window ............ 157 Figure 111 ICM3/3G - RSTP - RSTP Window ..................................................................... 159 Figure 112 ICM3/3G - RSTP - RSTP Port Window ............................................................. 161 Figure 113 ICM3/3G - VLAN Frame Forwarding with VLAN - Part 1 .................................. 163 Figure 114 ICM3/3G - VLAN Frame Forwarding with VLAN - Part 2 .................................. 164 Figure 115 ICM3G - VLAN - General Window ..................................................................... 165 Figure 116 ICM3 - VLAN - General Window ....................................................................... 166 Figure 117 ICM3G - VLAN - VLAN Setup Window .............................................................. 167 Figure 118 ICM3 - VLAN - VLAN Setup Window ................................................................ 168 Figure 119 ICM3/3G - VLAN - VLAN Setup - Add Window ................................................. 170 Figure 120 ICM3G - VLAN - VLAN Interface Window ......................................................... 171 Figure 121 ICM3 - VLAN - Routed VLAN Interface Window ............................................... 172 Figure 122 ICM3/3G - VLAN - VLAN Interface - Add Window ............................................ 172 Figure 123 ICM3 - VLAN - Inband VLAN Interfaces Window .............................................. 174 Figure 124 ICM3 - VLAN - Inband VLAN Interfaces - Add VLAN Interface Window ........... 175 Figure 125 ICM3G- Multicast Window ................................................................................. 176 Figure 126 ICM3 - Multicast Window ................................................................................... 177 Figure 127 ICM3 - Multicast - IGMP Snooping - General Window ...................................... 178 Figure 128 ICM3 - Multicast - IGMP Snooping - Group Membership Window .................... 179 Figure 129 ICM3 - Multicast - IGMP Proxy - General Window ............................................ 180 Figure 130 ICM3 - Multicast - IGMP Proxy - Group Membership ........................................ 181 Figure 131 ICM3 - Multicast - PIM-SM - General Window .................................................. 183 Figure 132 ICM3 - Multicast - PIM-SM - RP Router Window .............................................. 184 Figure 133 ICM3 - Multicast - PIM-SM - RP Router - Add Window ..................................... 184 Figure 134 ICM3 - Multicast - PIM-SM - Multicast Routing Table Window .......................... 185 Figure 135 ICM3 - Multicast - PIM-SM - Neighbor Details Window ..................................... 186 Figure 136 ICM3 - Multicast - PIM-SM - Interface Setup Window ....................................... 187 Figure 137 ICM3 - Multicast - PIM-SM - Interface Setup - Add Window ............................. 188 Figure 138 ICM3 - Routing - Routing Table Window ........................................................... 189 Figure 139 ICM3 - Routing - Add ......................................................................................... 190 Figure 140 ICM3 - Routing - RIP - General Window ........................................................... 192 Figure 141 ICM3 - Routing - RIP - Redistribution Setup Window ........................................ 193 Figure 142 ICM3 - Routing - RIP - Redistribution Setup - Add Window .............................. 194 Figure 143 ICM3 - Routing - RIP - Neighbor Details Window ............................................. 194 Figure 144 ICM3 - Routing - RIP - Neighbor Details - Add Window .................................... 195 Figure 145 ICM3 - Routing - RIP - Peer Details Window .................................................... 196 Figure 146 ICM3 - Routing - RIP - Key Setup Window ....................................................... 197 Figure 147 ICM3 - Routing - RIP - Key Setup - Add Keychain Window .............................. 198 Figure 148 ICM3 - Routing - RIP - Key Setup - Add Key Window ....................................... 198 Figure 149 ICM3 - Routing - RIP - Interface Setup Window ................................................ 199 Figure 150 ICM3 - Routing - RIP - Interface Setup - Add Window ...................................... 200 Figure 151 ICM3 - Routing - OSPF - General Window ....................................................... 202 Figure 152 ICM3 - Routing - OSPF - Route Redistribution Window .................................... 204 Figure 153 ICM3 - Routing - RIP - Route Redistribution- Add Window ............................... 205 Figure 154 ICM3 - Routing - OSPF - Area Setup Window .................................................. 206 Figure 155 ICM3 - Routing - OSPF - Area Setup - Add Window ......................................... 207 Figure 156 ICM3 - Routing - OSPF - Address Ranges Window .......................................... 208 Figure 157 ICM3 - Routing - OSPF - Address Ranges - Add Window ................................ 209 Figure 158 ICM3 - Routing - OSPF - LSDB Table Window ................................................. 210
iAN8K B1000 Operations Manual July 2006
19
Figure 159 ICM3 - Routing - OSPF - Neighbor Details Window .......................................... 213 Figure 160 ICM3 - Routing - OSPF - Interface Setup Window ............................................ 214 Figure 161 ICM3 - Routing - OSPF - Interface Setup - Add Window .................................. 215 Figure 162 ICM3 - Routing - ARP Window .......................................................................... 217 Figure 163 ICM3 - Routing - ARP - Add Window ................................................................ 218 Figure 164 ICM3 - Routing - ARP - Delete Advanced Window ........................................... 218 Figure 165 ICM3 - DHCP - Server Window ......................................................................... 220 Figure 166 ICM3 - DHCP - Profile Window ......................................................................... 221 Figure 167 ICM3/3G - DHCP - Profile - Add Window .......................................................... 222 Figure 168 ICM3 - DHCP - Subnet Mapping Window ......................................................... 225 Figure 169 ICM3/3G - DHCP - Subnet Mapping - Add Window .......................................... 226 Figure 170 ICM3 - DHCP - Pool Window ............................................................................ 227 Figure 171 ICM3/3G - DHCP - Pool - Add Window ............................................................. 228 Figure 172 ICM3 - DHCP - Map Window ............................................................................. 229 Figure 173 ICM3/3G - DHCP - Map - Add Window ............................................................. 230 Figure 174 ICM3 - DHCP - Lease Window .......................................................................... 231 Figure 175 ICM3 - DHCP - Option 60 Window .................................................................... 232 Figure 176 ICM3/3G - DHCP - Option 60 - Add Window ..................................................... 232 Figure 177 ICM3 - DHCP - Option 82 Window .................................................................... 233 Figure 178 ICM3/3G - DHCP - Option 82 - Add Window ..................................................... 234 Figure 179 ICM3 - DHCP - VLAN Window .......................................................................... 235 Figure 180 ICM3/3G - DHCP - VLAN - Modify Window ....................................................... 236 Figure 181 ICM3 - Packet Classification - Masks Window .................................................. 237 Figure 182 ICM3/3G - Packet Classification - Masks - Add Window ................................... 238 Figure 183 ICM3 - Packet Classification - Actions ............................................................... 240 Figure 184 ICM3/3G - Packet Classification - Actions - Add ............................................... 241 Figure 185 ICM3 - Packet Classification - Meters ............................................................... 242 Figure 186 ICM3/3G - Packet Classification - Meters - Add ................................................ 243 Figure 187 ICM3 - Packet Classification - Flow Counters ................................................... 244 Figure 188 ICM3 - Packet Classification - Rules ................................................................. 245 Figure 189 ICM3/3G - Packet Classification - Rules - Add .................................................. 246 Figure 190 ICM3 - QoS - Priority ......................................................................................... 247 Figure 191 ICM3 - QoS - Priority - Modify ........................................................................... 248 Figure 192 ICM3 - QoS - DSCP Priority .............................................................................. 249 Figure 193 ICM3 - QoS - DSCP Priority - Modify ................................................................ 250 Figure 194 ICM3 - QoS - Queue Mapping ........................................................................... 251 Figure 195 ICM3 - QoS - DSCP Mapping - Modify .............................................................. 252 Figure 196 ICM3 - QoS - L2 Scheduling .............................................................................. 253 Figure 197 PCU -Node - Reset ............................................................................................ 256 Figure 198 PCU - Module Summary Window ...................................................................... 257 Figure 199 PCU - Shelf View Window ................................................................................. 258 Figure 200 PCU - PCU Window .......................................................................................... 259 Figure 201 PCU - Clock Source Window ............................................................................. 260 Figure 202 PCU - Alarm Indication Window ........................................................................ 261 Figure 203 PCU - PDP Window ........................................................................................... 263 Figure 204 iFXS1 Module Information ................................................................................. 265 Figure 205 IP Configuration ................................................................................................. 267 Figure 206 Call Server ......................................................................................................... 268 Figure 207 Misc Config ........................................................................................................ 269 Figure 208 T.38 ................................................................................................................... 271 Figure 209 TOS/DSCP ........................................................................................................ 272 Figure 210 VLAN Tag .......................................................................................................... 273 Figure 211 Node Configuration ............................................................................................ 274 Figure 212 Port Configuration .............................................................................................. 276 Figure 213 Ring Definition ................................................................................................... 278
July 2006 iAN8K B1000 Operations Manual
20
Figure 214 VoIP Media ........................................................................................................ 280 Figure 215 Jitter Buffer ........................................................................................................ 281 Figure 216 SIP Port ............................................................................................................. 282 Figure 217 SIP Summary Statistics ..................................................................................... 283 Figure 218 SIP Supported Methods .................................................................................... 284 Figure 219 SIP Methods Statistics ...................................................................................... 285 Figure 220 General Config .................................................................................................. 286 Figure 221 Server Table ...................................................................................................... 287 Figure 222 MG Table ........................................................................................................... 288 Figure 223 User Table ......................................................................................................... 289 Figure 224 IPxDSL Provisioning Main Window ................................................................... 291 Figure 225 Node - Reset ..................................................................................................... 293 Figure 226 IPxDSL - Module Summary - Module Information Window ............................... 294 Figure 227 IPxDSL - Module Summary - Active Ports Window ........................................... 295 Figure 228 IPxDSL - Shelf Window ..................................................................................... 296 Figure 229 IPxDSL - Virtual Board Assignment Window ..................................................... 297 Figure 230 IPxDSL - Virtual Board Assignment - Module Type Window ............................. 297 Figure 231 IPxDSL - Virtual Board Deassignment Window ................................................ 298 Figure 232 IPxDSL - IPADSL3A Window ............................................................................ 299 Figure 233 IPxDSL - Customized Filter - Upstream Multicast Filter Packet Flow - Enabled 301 Figure 234 IPxDSL - Customized Filter - Upstream Multicast Filter Packet Flow - Disabled 302 Figure 235 IPxDSL - Customized Filter Window ................................................................. 307 Figure 236 IPxDSL - Test Timeout Window ........................................................................ 310 Figure 237 IPxDSL - PPPoE Snooping Window ................................................................. 311 Figure 238 IPxDSL - WAN - WAN Port Window .................................................................. 313 Figure 239 IPxDSL - ADSL - ADSL Port Window ................................................................ 314 Figure 240 IPxDSL - ADSL - ADSL Port - Assign Profile Window ...................................... 315 Figure 241 IPxDSL - SHDSL - SHDSL Port Window .......................................................... 316 Figure 242 IPxDSL - SHDSL - SHDSL Port - Assign Profile Window ................................. 317 Figure 243 IPxDSL - xDSL - Line Status Window ............................................................... 318 Figure 244 IPxDSL - ADSL - Channel Status Window ........................................................ 320 Figure 245 IPxDSL - ADSL - Previous Status Window ....................................................... 321 Figure 246 IPxDSL - ADSL - Status Change Time Info Window ......................................... 322 Figure 247 IPxDSL - ADSL - Rate Summary Window ......................................................... 323 Figure 248 IPxDSL - xDSL - Port Label Window ................................................................. 324 Figure 249 IPxDSL - xDSL - Port Label - Modify Window ................................................... 325 Figure 250 IPxDSL - ADSL - Bit Loading Window ............................................................... 326 Figure 251 IPxDSL - xDSL - iSmart Window ....................................................................... 328 Figure 252 IPxDSL - ADSL - CPE Window ......................................................................... 329 Figure 253 IPxDSL - ADSL - CPE - Modify Window ........................................................... 330 Figure 254 IPxDSL - ATM - ATM VC Window ..................................................................... 331 Figure 255 IPxDSL - ATM - ATM VC - Add Window ........................................................... 332 Figure 256 IPxDSL - ATM - Traffic Profile Window ............................................................. 334 Figure 257 IPxDSL - ATM - Traffic Profile - Assign Profile Window .................................... 335 Figure 258 IPxDSL - Bridge - MAC Address Per Port Window ........................................... 336 Figure 259 IPxDSL - Bridge - MAC Address Per Port - Modify Window ............................. 337 Figure 260 IPxDSL - Bridge - Packet Policing - Packet Policing Setup Window ................. 338 Figure 261 IPxDSL - Bridge - Packet Policing IP Address Summary Window .................... 339 Figure 262 IPxDSL - Bridge - Forwarding Database Window ............................................. 340 Figure 263 IPxDSL - Forwarding Database - Add Window ................................................. 341 Figure 264 IPxDSL - Bridge - ARP Table Window .............................................................. 343 Figure 265 IPxDSL - Bridge - Flood Limit Window .............................................................. 344 Figure 266 IPxDSL - IGMP - Authentication Parameters Window ...................................... 345 Figure 267 IPxDSL - IGMP - Authentication Parameters - Modify Window ......................... 345 Figure 268 IPxDSL - IGMP - CAC Window ......................................................................... 346
iAN8K B1000 Operations Manual July 2006
21
Figure 269 IPxDSL - IGMP - Multicast Group Window ........................................................ 347 Figure 270 IPxDSL - IGMP - Multicast Host Window .......................................................... 348 Figure 271 IPxDSL - VLAN - VLAN Window ....................................................................... 350 Figure 272 IPxDSL - VLAN - VLAN - Add Window .............................................................. 351 Figure 273 IPxDSL - VLAN - Ingress Rule Window ............................................................. 352 Figure 274 IPxDSL - VLAN - Ingress Rule - Modify Window ............................................... 352 Figure 275 IPxDSL - VLAN - VLAN Untag Window ............................................................. 353 Figure 276 IPxDSL - Access List Window ........................................................................... 354 Figure 277 IPxDSL - Access List - Edit Window .................................................................. 355 Figure 278 IPxDSL - Access List - Edit - New Window ....................................................... 356 Figure 279 IPxDSL - QoS - Packet Priority Window ............................................................ 359 Figure 280 IPxDSL - QoS - Packet Priority - Edit Window .................................................. 359 Figure 281 IPxDSL - QoS - Packet Priority - Edit - Add Window ......................................... 360 Figure 282 IPxDSL - QoS - Port Based Priority Window ..................................................... 361 Figure 283 IPxDSL - QoS - Port Based Priority - Modify Window ....................................... 361 Figure 284 IPxDSL - QoS - 802.1p Tag Window ................................................................. 363 Figure 285 Performance Management Main Window ......................................................... 365 Figure 286 ICM3 - Ethernet PM- General Counters ............................................................ 367 Figure 287 ICM3 - Ethernet PM - Error Counters ................................................................ 369 Figure 288 ICM3 - Ethernet PM - Traffic Load ..................................................................... 370 Figure 289 ICM3 - Bridge PM - Control ............................................................................... 371 Figure 290 ICM3 - Bridge PM - 5 Minutes Report ............................................................... 372 Figure 291 IPADSLx - ATM PVC ......................................................................................... 374 Figure 292 IPADSLx - Bridge Port - Bridge PM Control ...................................................... 375 Figure 293 IPADSLx - Bridge Port - Bridge ......................................................................... 376 Figure 294 IPADSLx - Bridge Port - 5 Minutes Report ........................................................ 377 Figure 295 IPADSLx - WAN Port - Thresholds Control ....................................................... 379 Figure 296 IPADSLx - WAN Port - 15 Minutes .................................................................... 380 Figure 297 IPADSLx - ADSL Port - ADSL 15 Minutes Summary ........................................ 382 Figure 298 IPADSLx - ADSL Port - Thresholds Control ...................................................... 384 Figure 299 IPADSLx - ADSL Port - ATUC 15 Minutes ........................................................ 385 Figure 300 IPADSLx - Channel - Downstream 15 Minutes ................................................. 387 Figure 301 IPSHDSL3 - Bridge ............................................................................................ 388 Figure 302 Diagnostics Main Window ................................................................................. 391 Figure 303 F4/F5 Loopback Window ................................................................................... 393 Figure 304 F4/F5 Loopback - F4 Test Window ................................................................... 393 Figure 305 F4/F5 Loopback - F5 Test Window ................................................................... 394 Figure 306 DELT Window .................................................................................................... 395 Figure 307 DELT - Result - Hlin(f) ....................................................................................... 396 Figure 308 DELT - Result - Hlog(f) ...................................................................................... 396 Figure 309 DELT - Result - QLN(f) ...................................................................................... 397 Figure 310 DELT - Result - SNR(f) ...................................................................................... 397 Figure 311 DELT Window - Result - Report ........................................................................ 398 Figure 312 SELT Window .................................................................................................... 399 Figure 313 SELT - Test Result ............................................................................................ 400 Figure 314 SELT - Test Result - Table ................................................................................ 402 Figure 315 SELT - Test Result - File - Directory .................................................................. 403 Figure 316 SELT - Test Result - View - Inband Noise ......................................................... 403 Figure 317 Platform Level Alarms ....................................................................................... 405 Figure 318 Alarm Tree ......................................................................................................... 407 Figure 319 Fault Management Main Window ...................................................................... 408 Figure 320 Node Alarm ........................................................................................................ 409 Figure 321 Equipment Alarm ............................................................................................... 410 Figure 322 Port Alarm .......................................................................................................... 411 Figure 323 Alarm Summary Window ................................................................................... 413
July 2006 iAN8K B1000 Operations Manual
22
Figure 324 Alarm Filter Window .......................................................................................... 414 Figure 325 Software Upgrade ............................................................................................. 425 Figure 326 Tools - TFTP ..................................................................................................... 429 Figure 327 Tools - TFTP - Client Mode ............................................................................... 429 Figure 328 Tools - TFTP Window ........................................................................................ 430 Figure 329 Tools - TFTP Window - Expanded .................................................................... 431 Figure 330 Backup Node ..................................................................................................... 433 Figure 331 Profile Menu - Access List Profiles .................................................................... 438 Figure 332 Access List Profile Summary Window ............................................................... 438 Figure 333 PPPoE Access Deny - Add Access List Profile - Deny ..................................... 439 Figure 334 PPPoE Access Deny - Add Access List Profile - Permit ................................... 440 Figure 335 PPPoE Access Deny - 2 Profiles Added ........................................................... 440 Figure 336 PPPoE Access Deny - IPxDSL Module - Access List ....................................... 441 Figure 337 PPPoE Access Deny - IPxDSL Module - Applying Profiles to Outbound .......... 442 Figure 338 PPPoE Access Deny - Complete ...................................................................... 443 Figure 339 Profile Menu - Access List Profiles .................................................................... 444 Figure 340 Access List Profile Summary Window ............................................................... 444 Figure 341 IP Address Conflict - Add Access List Profile - Permit ...................................... 445 Figure 342 IP Address Conflict - Add Access List Profile - Deny ........................................ 446 Figure 343 IP Address Conflict - 2 Profiles Added .............................................................. 446 Figure 344 IP Address Conflict - IPxDSL Module - Access List .......................................... 447 Figure 345 IP Address Conflict - IPxDSL Module - Applying Profiles to Outbound ............. 448 Figure 346 IP Address Conflict - Complete ......................................................................... 449 Figure 347 Profile Menu - Access List Profiles .................................................................... 450 Figure 348 Access List Profile Summary Window ............................................................... 450 Figure 349 FTP Access Deny - Add Access List Profile - Deny .......................................... 451 Figure 350 FTP Access Deny - Add Access List Profile - Permit ........................................ 452 Figure 351 FTP Access Deny - 2 Profiles Added ................................................................ 452 Figure 352 FTP Access Deny - IPxDSL Module - Access List ............................................ 453 Figure 353 FTP Access Deny - IPxDSL Module - Applying Profiles to Inbound ................. 454 Figure 354 FTP Access Deny - IPxDSL Module - Applying Profiles to Outbound ............... 455 Figure 355 FTP Access Deny - Complete ........................................................................... 456 Figure 356 Profile Menu - Access List Profiles .................................................................... 457 Figure 357 Access List Profile Summary Window ............................................................... 457 Figure 358 ABC IM Service Access Deny - Add Access List Profile - Deny IP Address Range 458 Figure 359 ABC IM Service Access Deny - Add Access List Profile - Deny Specific IP Address 459 Figure 360 ABC IM Service Access Deny - Add Access List Profile - Permit ..................... 460 Figure 361 ABC IM Service Access Deny - 3 Profiles Added ............................................. 460 Figure 362 ABC IM Service Access Deny - IPxDSL Module - Access List ......................... 461 Figure 363 ABC IM Service Access Deny - IPxDSL Module - Applying Profiles to Outbound .. 462 Figure 364 ABC IM Service Access Deny - Complete ........................................................ 463
July 2006
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 productsvisit 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.
July 2006
24
Notices
Table 1 lists notice icons used in this guide. Table 1 Notice Icon Descriptions
Icon Notice Type Information Note Description 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.
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.
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. Table 2 lists text conventions in this guide. Table 2 Text Convention Descriptions
Convention Text represented as a screen display Text represented as user entry. Text represented as menu, sub-menu, tab, and field names Description This typeface represents text that appears on a terminal screen, for example login:. user, for example, cd
Text
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>
July 2006
Related Documentation
25
Related Documentation
The following lists the documentation set for iAN8K B1000 Release 3.1 system: Table 3 iAN8K B1000 Release 3.1 Documentation Set
Guide Netman 4000 Installation Manual Netman 4000 Operations Manual iAN8K B1000 Release 3.1 B1000 Installation Manual iAN8K B1000 Release 3.1 B1000 IS Installation Manual iAN8K B1000 Release 3.1 Operations Manual iAN8K B1000 Release 3.1 Command Line Interface (CLI) User Manual iAN8K B1000 Release 3.1 IP Service Module (ISM) Operations Manual iAN8K B1000 Release 3.1 IP Service Module (ISM) Command Line Interface (CLI) User Manual iAN8K B1000 Release 3.1 ATM Service Module (ASM) Operations Manual iAN8K B1000 Release 3.1 ATM Service Module (ASM) Command Line Interface (CLI) User Manual UTSI-NJTC-20050914 UTSI-NJTC-20050870 UTSI-NJTC-20050696 UTSI-NJTC-20050624 UTSI-NJTC-20050697 UTSI-NJTC-20050698 UTSI-NJTC-20050699 UTSI-NJTC-20050700 Part Number
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:
Product information
July 2006
26
Please include the name and part number of the guide being referenced. If applicable, provide the chapter and page number.
July 2006
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.
July 2006
28
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. Netman 4000 supports the following functions: Topology Management The 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 Management The 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 Management The 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 Management Netman 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.
July 2006
29
System Tools System 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.
July 2006
30
July 2006
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
July 2006
32
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:
July 2006
Configuration Menu
33
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. 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. 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
Save Configuration
Erase Configuration
CAUTION: If you reset the system after erasing all configurations the communication via SNMP (Netman) will be disabled. By design the AN-2000
July 2006 iAN8K B1000 Operations Manual
34
IPiAN8K B1000 wont communicate over SNMP with Netman (or any other SNMP Manager) until the Netman IP address has been entered. Youll 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 Netmans Device Manager screen. As long as these addresses are non-zero it will allow SNMP communication. The addresses dont have to point to valid Netman Server addresses. However youll need valid addresses if you expect to receive traps from the node at these locations. Erase Shelf Configuration 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 wont communicate over SNMP with Netman (or any other SNMP Manager) until the Netman IP address has been entered. Youll 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 Netmans Device Manager screen. As long as these addresses are non-zero it will allow SNMP communication. The addresses dont have to point to valid Netman Server addresses. However youll 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.
July 2006
Configuration Menu
35
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.
July 2006
36
Click Add or select an entry and click Modify in Figure 5. Configure the parameters and click Apply in Figure 6.
July 2006
Configuration Menu
37
Select an entry in Figure 5 and click Delete to remove an existing entry. Click Close to exit the window. System Log Data iAN8K 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
Event User login from console port User logout from console port User failed to login at console port (password authentication fails) Telnet request from IP address a.b.c.d User telnet from IP address a.b.c.d and login to the node User from IP address a.b.c.d logout from telnet session User telnet from IP address a.b.c.d and login to the node failed 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. RADIUS message sent to server a.b.c.d timeout RADIUS server is marked as temporary down RADIUS server is recovered from temporary down
No. 1 2 3 4 5 6 7 8 9 10 11
July 2006
38
DHCP
Event A DHCPACK message is snooped in downstream (from WAN port to ADSL ports) DHCP contract expired
No. 1 2
No. 1
No. 1 2 3
No. 1 2 3 4 5 6 7 8 9 10 11
Configuration change
Event ADSL/SHDSL port admin status change Any other configuration changes Configuration is saved Configurations are erased
No. 1 2 3 4
July 2006
Configuration Menu
39
No. 1 2 3 4 5
System alarm
Event Fan failure Fuse alarm Fan recover External clock down, while primary clock source is set as external clock, External clock recovery, while primary clock source is set as external clock External clock is no longer configured as primary clock source, while an external clock down alarm is outstanding Fuse recovery
No. 1 2 3 4 5 6 7
No. 1 2 3
No. 1 2
No. 1 2 3 4 5 6
July 2006
40
No. 1 2 3
No. 1
No. 1 2
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:
July 2006
Configuration Menu
41
RADIUS Server Select 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
July 2006
42
Select an entry in Figure 7 and click Delete to remove the entry. Click Close in Figure 7 to exit the window. Statistics Select 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.
July 2006
Configuration Menu
43
Down Times
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
iAN8K B1000 Operations Manual
July 2006
44
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
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
July 2006
Configuration Menu
45
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
July 2006
46
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.
July 2006
Configuration Menu
47
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.
July 2006
48
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.
July 2006
Configuration Menu
49
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.
July 2006
50
Profile Menu
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
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.
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 Template Select ADSL Line Profile from Profile menu to open Figure 19. Click Retrieve to obtain the latest information.
July 2006
Profile Menu
51
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 Profile This 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.
July 2006
52
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
July 2006
Profile Menu
53
Spectrum Profile This 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.
July 2006
54
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.
July 2006
Profile Menu
55
July 2006
56
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 Downstream Target 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. Value range: 0 ~ 31 dB 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. Value range: 0 ~ 31 dB Default: 3 dB
July 2006
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
July 2006
58
the other. Table 9 lists the correlation and interdependencies between the line card and relevant line standards Table 9 Line Standard / Line Card Co-relation Table
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 V V V V V IPADSL3A/6A V V V V IPADSL3B/6B
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.
July 2006
Profile Menu
59
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.
July 2006
60
For 2-wire, 200 to 2312 Kbps in increments of 64 Kbps For 4-wire, 400 to 4624 Kbps in increments of 128 Kbps
Default:
July 2006
Profile Menu
61
For 2-wire, 200 to 2312 Kbps in increments of 64 Kbps For 4-wire, 400 to 4624 Kbps in increments of 128 Kbps
Default:
Fixed Rate
For 2-wire, 200 to 2312 Kbps in increments of 64 Kbps For 4-wire, 400 to 4624 Kbps in increments of 128 Kbps
Default:
Rate Mode
Downstream Current Condition Value range: -10 to 20 dB Target SNR Margin Default: 0 dB Downstream Worst Condition Target SNR Margin Upstream Current Condition Target SNR Margin Upstream Worst Condition Target SNR Margin Wire interface Value range: -10 to 20 dB Default: 0 dB Value range: -10 to 20 dB Default: 0 dB Value range: -10 to 20 dB Default: 0 dB Value range: Two Wire / Four Wire Default: Two Wire
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.
July 2006
62
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.
July 2006
Profile Menu
63
Select a profile in Figure 27 and click Delete to delete the profile. Click Close in Figure 27 to exit. 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.
July 2006
64
Click Add or select a profile and click Modify in Figure 29 to configure profiles in Figure 30. Configure the parameters and click Apply to take the modification into effect.
July 2006
Profile Menu
65
Select a profile in Figure 29 and click Delete to delete the profile. Click Close in Figure 29 to exit. 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
July 2006
66
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. (Its users 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
July 2006
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 13 Profile - Access List Profile - Add - From / To Table
Field Any - Figure 32 ARP-Send-IP - Figure 33 ARP-Send-MAC - Figure 33 Ethernet Type - Figure 34 IP Address - Figure 34 Description Any sources/destination Value range: IP address with network mask or with a range Value range: MAC address Value range: Two bytes, hex value IP address with network mask or with a range Value range: Valid IP address MAC Address - Figure 35 Protocol Type - Figure 35 TCP Port - Figure 36 Value range: Valid MAC address Value range: One byte, a decimal value 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 lists the valid ACL rule combination supported on the system. Table 14 ACL Rule Combination Table
From Any Any MAC Ether Type Arp IP To Arp Mac IP Prot Type TCP Port UDP Port V V V V V V V V V MAC V V V V V V V V V V V V V V V V V V V V V V EtherType V V Arp IP V V Arp Mac V V IP V V Prot Type V V TCP Port V V UDP Port V V
July 2006
68
July 2006
Profile Menu
69
Figure 35 Profile - Access List Profile - Add - MAC Address To Protocol Type
July 2006
70
Figure 36 Profile - Access List Profile - Add - TCP Port To UDP Port
Select a profile in Figure 31 and click Delete to delete the profile. Click Close in Figure 31 to exit. Packet Priority Classification 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
July 2006
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 16 Profile - Packet Priority Classification - Add - Type Table
Field DSCP - Figure 38 VLAN ID - Figure 39 IP Protocol Type - Figure 40 Send TCP Port - Figure 41 Description Value range: 0 - 63, or 6 digits binary format Value range: 1 - 4094 Value range: 0 - 255 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 Destination IP - Figure 47 & Figure 48 Ethernet Type - Figure 49 TOS Bits - Figure 50 Value range: IP address with subnet mask or with a range Value range: IP address with subnet mask or with a range Value range: Heximal value, two bytes Value range: 0 - 15, or 4 digits binary format
July 2006
72
July 2006
Profile Menu
73
July 2006
74
July 2006
Profile Menu
75
Figure 45 Profile - Packet Priority Classification - Add - Source IP - IP Address With Subnet Mask
July 2006
76
Figure 47 Profile - Packet Priority Classification - Add - Destination IP - IP Address With Subnet Mask
July 2006
Profile Menu
77
July 2006
78
Select a profile in Figure 37 and click Delete to delete the profile. Click Close in Figure 37 to exit. Traffic Management Profile 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.
July 2006
Profile Menu
79
Click Add or select a profile and click Modify in Figure 51 to configure profiles in Figure 52. Configure the parameters and click Apply to take the modification into effect. 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
July 2006
80
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
Notes
Note1 Note1
July 2006
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.
July 2006
82
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
July 2006
Batch Menu
83
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
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.
July 2006
84
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
July 2006
Batch Menu
85
July 2006
86
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. Value range: Enable / Disable Default: Enable
July 2006
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.
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
iAN8K B1000 Operations Manual
July 2006
88
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:
Select Multicast Group Packaging from Video Service menu. Multicast group packaging supports the following configuration:
Default Rate Select 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
July 2006
89
Multicast Group Select 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 Group Name Description 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
July 2006
90
Table 20 Video Service - Multicast Group Packaging - Multicast Group Field Description
Field Session Timeout Description 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. Value range: 1 - 6000 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. Value range: 1 - 100 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. Value range: 1 - 7200 Default: 60
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
July 2006
91
Select an entry in Figure 59 and click Delete to remove an existing entry. Multicast Package Select 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
Table 21 Video Service - Multicast Group Packaging - Multicast Package Field Description
Field Package Name Multicast group list Description The name of the multicast package. The name of the multicast group. Up to 256 multicast group names.
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.
July 2006
92
Select an entry in Figure 61 and click Delete to remove an existing entry. Access Control Select Access Control from Video Service menu. Access control supports the following configuration:
Account lockout Policy Select 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.
July 2006
93
Table 22 Video Service - Access Control - Account Lockout Policy Field Description
Field Quiet Period (seconds) Description 0-300 disables quiet period. Default: 10 Max Consecutive Failures 1-100 Default: 20
Reset Period Select 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.
July 2006
94
User Account Create 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
July 2006
95
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
July 2006
96
Select an entry in Figure 65 and click Delete to remove an existing entry. 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 Select 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 Statistics Select Usage Statistics from Video Service menu and select Usage Statistics tab to open Figure 68. Click Retrieve to obtain the latest information.
July 2006
Tools Menu
97
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.
July 2006
98
July 2006
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.
July 2006
100
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.
July 2006
IP Address
101
July 2006
102
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
July 2006
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
July 2006
104
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.
July 2006
NMP Access
105
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.
July 2006
106
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.
July 2006
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.
July 2006
108
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.
iAN8K B1000 Operations Manual July 2006
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.
July 2006
110
July 2006
Reset
111
Administrative Distance
Configurable for static routes. Read only for dynamic routes. 0 for connected interface routes.1 for all other static routes. Value range: 0 - 255
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
Reset
Netman 4000 provides reset function that allows software reset or hardware reset on the node and the modules.
July 2006
112
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.
July 2006
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 wont communicate over SNMP with Netman (or any other SNMP Manager) until the Netman IP address has been entered. Youll 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.
July 2006 iAN8K B1000 Operations Manual
114
There are 2 possible entries here for primary and secondary for the Netman address. It basically maps to the Trap Destination Setup on Netmans Device Manager screen. As long as these addresses are non-zero it will allow SNMP communication. The addresses dont have to point to valid Netman Server addresses. However youll 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 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.
July 2006
115
July 2006
116
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 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. Note: This feature is applicable when there are slave shelves configured in the node. 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.
July 2006
117
July 2006
118
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 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. Note: This feature is applicable when there are slave shelves configured in the node. 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.
July 2006
119
July 2006
120
July 2006
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
July 2006
122
Reset
ICM3/3G Forwarding Database Mirror Port Trunk Group Protection Link Redundancy Support Switchover
July 2006
123
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
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.
July 2006
124
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.
July 2006
Module Summary
125
July 2006
126
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.
July 2006
127
July 2006
128
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. Table 31 ICM3/3G Module Placements Details
Module Type ICM3/3G Maximum Number of Board Per Shelf Slot Used 2 A, B Virtual Configuration No
Active ICM3/3G module supports the following configuration at the slot level:
July 2006
129
Standby ICM3/3G module supports the following configuration at the slot level:
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
July 2006
130
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.
July 2006
131
Click Reset in Figure 92 to reset the switch engine for the selected VLAN.
July 2006
132
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.
July 2006
133
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
July 2006
134
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
July 2006
135
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
July 2006
136
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
July 2006
137
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.
July 2006
138
Shelf 1
GE link
GE link
Shelf 2
I C M 3 (B)
I C M 3 (A)
GE link
GE link
Shelf 3
I C M 3 (B)
I C M 3 (A)
GE link
GE link
Shelf 4
I C M 3 (B)
I C M 3 (A)
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.
iAN8K B1000 Operations Manual July 2006
139
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
iAN8K B1000 Operations Manual
July 2006
140
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:
The ICM3/3G states can be mapped to the administrative states, operational states, and standby status defined in ITU-T X.731 as follows:
Initializing Admin (RW) Operational (R) Standby (R) Unlocked Disabled N/A Prohibited Locked Disabled N/A Redundant Unlocked Enabled Hot standby Active Unlocked Enabled Providing service
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:
July 2006
141
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 Switchover Allow configuration change E1-E4, G1-G2 status Layer two switch process packet Not allowed No Locked, appear down No Prohibit Not allowed Yes Locked, appear down No Redundancy Allowed Yes Per user configuration No
July 2006
142
The parameters that are synchronized in the standby ICM3/3G during runtime are shown below:
Parameters ISM configuration ASM configuration ICM3/3G configuration All other configuration File download to ICM3/3G Save configuration Outstanding alarm for active ICM3/3G All other outstanding alarm FWDB for ICM3/3G layer-two switch IGMP snooping results DHCP assignment, statistics MAC black list match CLI access history ICM3/3G switch port statistics SNMP access statistics ICM3/3G STP statistics ICM3/3G ARP table RADIUS transaction, statistics Real time synchronization of standby ICM3/3G No, ISM configuration is sent to ISM. ICM3/3G does not maintain ISM configuration No, ASM configuration is sent to ISM. ICM3/3G does not maintain ASM configuration Yes Yes Yes Yes No Yes No. The static entries configured on active ICM3/3G are automatically copied to standby ICM3/3G and therefore shall appear on both FWDB No. The static router port configured on active ICM3/3G are automatically copied to standby ICM3/3G and therefore shall appear on both results No Yes No No Yes No No No
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
July 2006
143
Redundancy Setup via CLI In 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
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.
July 2006
144
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
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
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.
July 2006
145
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.
July 2006
146
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.
July 2006
147
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.
July 2006
148
Active ICM3/3G module supports the following configuration at the port level:
DHCP (Master shelf ICM3/3G only) Packet Classification (Master shelf ICM3/3G only) QoS
July 2006
149
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
July 2006
150
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.
Internal Ethernet Ports Expand 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.
July 2006
151
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.
July 2006
152
Figure 106 ICM3/3G - Ethernet Port Configuration - Internal Ethernet Ports Modify Window
External Ethernet Ports Expand 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.
July 2006
153
Figure 107 ICM3/3G - Ethernet Port Configuration - External Ethernet Ports Window
Select a port in Figure 107 and click Modify to modify the port. Configure the parameters in Figure 108 and click Apply to bring the modification into effect. Refer to Table 39 for more details. No modification is allowed on trunks ports. Disassociate with trunk port before attempting to modify the parameters.
July 2006
154
Figure 108 ICM3/3G - Ethernet Port Configuration - External Ethernet Ports Modify Window
July 2006
155
Disabled / 64kbps to 100Mbps in 64kbps granularity for FE ports Disabled / 64kbps to 1Gbps in 64kbps granularity for GE ports
Disabled / 64kbps to 100Mbps in 64kbps granularity for FE ports Disabled / 64kbps to 1Gbps in 64kbps granularity for GE ports
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
Trunk Ports Expand 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.
July 2006
156
Select a port in Figure 109 and click Modify to modify the port. Configure the parameters in Figure 110 and click Apply to bring the modification into effect. Refer to Table 40 for more details.
July 2006
157
Figure 110 ICM3/3G - Ethernet Port Configuration - Trunk Ports - Modify Window
158
Disabled / 64kbps to 100Mbps in 64kbps granularity for FE ports Disabled / 64kbps to 1Gbps in 64kbps granularity for GE ports
Disabled / 64kbps to 100Mbps in 64kbps granularity for FE ports Disabled / 64kbps to 1Gbps in 64kbps granularity for GE ports
Default: Disabled Broadcast Rate Threshold (pps) Value range: 0 - 262143 Default: 0, Disabled
Multicast Rate Threshold Value range: 0 - 262143 (pps) Default: 0, Disabled DLF Rate Control Threshold (pps) Value range: 0 - 262143 Default: 0, Disabled
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. RSTP Expand 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.
July 2006
159
July 2006
160
RSTP Port At 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.
July 2006
161
July 2006
162
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:
July 2006
163
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.
No
No
Yes Yes
July 2006
164
Found
Yes 'Forward to trunk ports' option enabled Yes Ingress/Egress Check Pass
Members found
Frame forwarded
General (Master shelf ICM3/3G only) VLAN Setup Routed VLAN Interface
July 2006
165
General This 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.
July 2006
166
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.)
July 2006
167
VLAN Setup Each 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.
July 2006
168
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:
Read-only
iAN8K B1000 Operations Manual
July 2006
169
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)
July 2006
170
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 Interface A 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.
July 2006
171
July 2006
172
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
July 2006
173
Read-only Sub-Interface ID Sub-interface 1 is the primary interface Read-only IP Address Subnet Mask Valid range: valid IP address Valid range: valid subnet mask
Select an entry and click Delete in Figure 121 to remove an entry. In-band Management VLAN 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>
July 2006
174
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
July 2006
175
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.
July 2006
176
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
July 2006
177
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
IGMP Proxy
July 2006
178
IGMP Snooping
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
July 2006
179
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
July 2006
180
IGMP Proxy
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
July 2006
181
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
July 2006
182
PIM-SM This feature is applicable for single shelf ICM3 module or master shelf ICM3 module only. ICM3 module supports the following PIM-SM configuration:
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.
July 2006
183
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.
July 2006
184
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
July 2006
185
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.
July 2006
186
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.
July 2006
187
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.
July 2006
188
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.
July 2006
189
Click Add in Figure 138. Configure the parameters and click Apply in Figure 139 to bring the modification into effect.
July 2006
190
Select an entry in Figure 138 and click Delete to remove the entry. 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 Neighbor Details Interface Setup
ARP
July 2006
191
RIP This 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.
July 2006
192
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.
July 2006
193
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.
July 2006
194
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
July 2006
195
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.
July 2006
196
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.
iAN8K B1000 Operations Manual
July 2006
197
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.
iAN8K B1000 Operations Manual
July 2006
198
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.
July 2006
199
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
July 2006
200
Click Add or select an entry and click Modify in Figure 149. Configure the parameters and click Apply in Figure 150 to bring the modification into effect. Figure 150 ICM3 - Routing - RIP - Interface Setup - Add Window
July 2006
201
Select an entry in Figure 149 and click Delete to remove the entry. OSPF This 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 Neighbor Details 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.
July 2006
202
July 2006
203
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.
July 2006
204
Click Add or select an entry and click Modify in Figure 152. Configure the parameters and click Apply in Figure 153 to bring the modification into effect.
July 2006
205
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.
July 2006
206
July 2006
207
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
July 2006
208
Select an entry in Figure 154 and click Delete to remove the entry. 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
July 2006
209
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
Select an entry in Figure 156 and click Delete to remove the entry. 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.
July 2006
210
July 2006
211
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 LS Type is Router: Router Type Number of Links AS Boundary Router, Area Border Router, Endpoint Active Virtual Link, Internal Router Number of individual links inside this link state record Value range: 16-bit integer 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 Link Connection Value range: IP address 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. Value range: IP address Attached Routers Read-only. Router ID for all routers attached to the network adjacent with the designated router. Value range: IP address LS Type is Network-Summary or ASBR-Summary: Network Mask Mask for the summarized network. Value range: IP address Metric Cost of reaching the summary network/ASBR from the advertising router/ASBR. Value range: 16-bit integer LS Type is AS-External or NSSA-External: Network Mask Mask for the network. Value range: IP address Metric Type OSPF type 1 or type 2 network. Value range: 1 / 2 Description
July 2006
212
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.
July 2006
213
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.
July 2006
214
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.
July 2006
215
Transmit Delay
Select an entry in Figure 160 and click Delete to remove the entry.
July 2006 iAN8K B1000 Operations Manual
216
ARP This 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.
July 2006
217
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
July 2006 iAN8K B1000 Operations Manual
218
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. Click Add or select an entry and click Modify in Figure 162. Configure the parameters and click Apply in Figure 163 to bring the modification into effect. 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
July 2006
219
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
Server Expand 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.
July 2006
220
Profile Expand 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.
July 2006
221
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.
July 2006
222
July 2006
223
July 2006
224
Select an entry in Figure 166 and click Delete to remove the entry. Or click Delete All to remove all entries. Subnet Mapping Expand 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.
July 2006
225
Click Add in Figure 168. Configure the parameters and click Apply in Figure 169 to bring the modification into effect.
July 2006
226
Select an entry in Figure 168 and click Delete to remove the entry. Or click Delete All to remove all entries. Pool Address 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.
July 2006
227
Click Add in Figure 170. Configure the parameters and click Apply in Figure 171 to bring the modification into effect.
July 2006
228
Select an entry in Figure 170 and click Delete to remove the entry. Or click Delete All to remove all entries. Map Expand 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.
July 2006
229
Click Add in Figure 172. Configure the parameters and click Apply in Figure 173 to bring the modification into effect.
July 2006
230
Select an entry in Figure 172 and click Delete to remove the entry. Lease Expand 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.
July 2006
231
Select an entry in Figure 174 and click Validate Selection to validate the entry. Or click Validate All to remove all entries. Option 60 DHCP 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.
July 2006
232
Click Add in Figure 175 or select an entry and click Modify. Configure the parameters and click Apply in Figure 176 to bring the modification into effect. Figure 176 ICM3/3G - DHCP - Option 60 - Add Window
July 2006
233
Option 82 DHCP 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
Click Add in Figure 177 or select an entry and click Modify. Configure the parameters and click Apply in Figure 178 to bring the modification into effect.
July 2006
234
VLAN ICM3/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.
July 2006
235
Select an entry and click Modify in Figure 179. Configure the parameters and click Apply in Figure 180 to bring the modification into effect.
July 2006
236
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 IP 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.
July 2006
237
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.
July 2006
238
July 2006
239
Select an entry in Figure 181 and click Delete to remove the entry. A mask cannot be removed if theres rules associated with it. Delete the rules associated with the selected mask first. Actions ICM3/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.
July 2006
240
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.
July 2006
241
July 2006
242
Select an entry in Figure 183 and click Delete to remove the entry. An action cannot be removed if theres rules associated with it. Delete the rules associated with the selected action first. Meters Metering 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
July 2006
243
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
Select an entry in Figure 185 and click Delete to remove the entry. Flow Counters ICM3/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.
July 2006
244
Select an entry in Figure 187 and click Reset to reset the packet counters. Or click Reset ALL to reset all the counters. Rules Create 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.
July 2006
245
Click Add or select an entry and click Modify in Figure 188. Configure the parameters and click Apply in Figure 189 to bring the modification into effect.
July 2006
246
Select an entry in Figure 188 and click Delete to remove the entry. Or click Delete All to remove all entries. QoS ICM3/3G module supports the following QoS configuration:
July 2006
247
Priority This 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.
July 2006
248
DSCP Priority This 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.
July 2006
249
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.
July 2006
250
Queue Mapping This 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.
July 2006
251
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.
July 2006
252
L2 Scheduling Expand 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.
July 2006
253
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.
July 2006
254
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: Table 72 ICM3/3G - QoS - L2 Scheduling - Weight for WRR / SP+WRR
Parameter Weights for Queue 0 Weights for Queue 1 Weights for Queue 2 Weights for Queue 3 Weights for Queue 4 Weights for Queue 5 Weights for Queue 6 Weights for Queue 7 WRR / SP+WRR 1 1 1 2 2 4 8 15 WFQ or SP+WFQ 3 3 3 6 6 12 23 44
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.
July 2006
This chapter provides configuration procedures for Peripheral Control Unit (PCU) module. PCU Module supports the following configurations:
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.
July 2006
256
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.
July 2006
257
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 199. Click Retrieve to obtain the latest information.
July 2006
258
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. Table 74 lists the guidelines for module placement and virtual configuration detail. Table 74 PCU Module Placements Details
Module Type PCU Maximum Number of Board Per Shelf Slot Used 1 P Virtual Configuration No
259
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
iAN8K B1000 Operations Manual
July 2006
260
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
July 2006
261
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
July 2006
262
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.
July 2006
263
July 2006
264
July 2006
iFXS1 module can be managed by UTStarcom's NMS platform - Netman 4000. This chapter describes iFXS module operations in Netman 4000 device management system.
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
July 2006
266
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.
July 2006
267
The DNS option is always enabled. Sets the iFXS1 module IP address Sets the netmask for the module IP address Sets the gateway for the module IP address Selects the IP address usage. Possible values are : unused, signaling, media, both
July 2006
268
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
July 2006
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
July 2006
270
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.
Displays the inter digit timer. The value range is 5-20s. The default value is 5s. Displays the busy tone length. The value range is 20-60s. The default value is 30s. Displays the dial tone length. The value range is 10-60s. The default value is 16s. Displays the ringing back tone length. The value range is 60-300. The default value is 180s. Displays the call waiting tone length. The value range is 20-60s. The default value is 30s. Displays the howler tone length. The value range is 0-300s. The default value is 60s. Displays the recorder tone length. The value range is 20-60s. The default value is 30s.
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.
July 2006
Configuring QoS
271
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.
iAN8K B1000 Operations Manual
July 2006
272
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. 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.
Signaling DSCP
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
July 2006
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
July 2006
274
Signaling VLAN ID Enters the VLAN ID for signaling. The value range is 1-4092.
July 2006
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.
July 2006
276
July 2006
277
Modifying a FXS Port Follow 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 Ring Definition 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.
July 2006
278
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.
iAN8K B1000 Operations Manual July 2006
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.
July 2006
280
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.
July 2006
Configuring MG Media
281
July 2006
282
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
July 2006
Configuring SIP
283
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
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.
iAN8K B1000 Operations Manual
July 2006
284
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.
July 2006
Configuring SIP UA
285
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.
July 2006
286
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.
July 2006
Configuring SIP UA
287
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.
July 2006
288
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.
July 2006
Configuring SIP UA
289
July 2006
290
July 2006
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
Reset
July 2006
292
Test Timeout
WAN Port xDSL ATM Bridge IGMP VLAN Access List QoS
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 xDSL is a joint name for all DSL port including ADSL and SHDSL
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
July 2006
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.
July 2006
294
Module Summary
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.
July 2006
295
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
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 228. Click Retrieve to obtain the latest information.
July 2006
296
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 lists the guidelines for module placement and virtual configuration detail. Table 99 IPxDSL Module Placements Details
Module Type IPADSL3A IPADSL3B Maximum Number of Board Per Shelf Slot Used 16 16 1 - 16 1 - 16 Virtual Configuration Yes Yes
July 2006
297
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
July 2006
298
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.
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:
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 xDSL is a joint name for all DSL port including ADSL and SHDSL
IPxDSL
iAN8K B1000 Operations Manual
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.
July 2006
300
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 Filter The 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 Timer 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 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 Filter IPxDSL module supports a module level "upstream multicast filtering". When upstream multicast filtering is enabled, upstream multicast/broadcast packet is forwarded as shown below:
July 2006
301
Figure 233 IPxDSL - Customized Filter - Upstream Multicast Filter Packet Flow - Enabled
Upstream Multicast packet
Enabled
Disabled
Yes
broadcast packet ?
Yes
IP or ARP packet ?
No
No
IP Multicast packet ?
Yes
No
IGMP packet ?
Yes
Is IGMPsnooping Enabled ?
Yes
Discard
When "upstream multicast filtering" is disabled (default), the upstream multicast packets are forwarded as shown below. Broadcast packets are forwarded to all ports.
July 2006
302
Figure 234 IPxDSL - Customized Filter - Upstream Multicast Filter Packet Flow - Disabled
Incom M ing ulticat packet
YS E
Is IG P M snooping E nabled ?
N O
Yes
IGMP packet?
No
F ound
N found ot
D iscard
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. 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
iAN8K B1000 Operations Manual July 2006
303
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 Filter IPxDSL 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 Filter This 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.
July 2006
304
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 Counter Database 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 Snooping Traditional 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.
July 2006
305
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 Option82 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 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 Sub-option Length Port label Length 1 byte 1 byte 1 - 64 bytes Description 0x01 circuit ID sub-option Total length of the port label Port label
July 2006
306
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: Table 102 Format of Remote ID Sub-option in DHCP Option 82
Field Sub-option Length Vendor ID Port Type Version VLAN ID NAS_MAC NAS_IP Node Shelf Slot Port VPI VCI Length 1 byte 1 byte 4 bytes 1 byte 1 byte 2 bytes 6 bytes 4 bytes 2 bytes 1 byte 1 byte 1 byte 1 byte 2 bytes Description 0x02 remote ID sub-option Total length of the value fields 0x079d UTStarcom vendor ID 0x01 ATM port 0x01 version 1 Port VLAN ID (0x00 for untagged) MAC address of line card Ethernet port GIADDR (0x00 not used by a bridge) Node ID Shelf ID Line card slot Line card port VPI of port VCI of port
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
iAN8K B1000 Operations Manual
July 2006
307
parameters and click Apply to bring the modification into effect. Refer to Table 103 for more details. Figure 235 IPxDSL - Customized Filter Window
July 2006
308
July 2006
309
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.
July 2006
310
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.
July 2006
311
ADSL Port SHDSL Port Line Status Channel Status Previous Status Status Change Time Info Rate Summary Port Label Bit Loading iSmart CPE
iAN8K B1000 Operations Manual
July 2006
312
ATM
Bridge
MAC Address Per Port Packet Policing Forwarding Database ARP Table Flood Limit
IGMP
VLAN
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.
July 2006
313
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
July 2006
314
ADSL Port Expand 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
July 2006
315
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 Port Expand 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.
July 2006
316
July 2006
317
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 Status Expand 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.
July 2006
318
Value Range
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
The signal to noise margin in dB on each port The highest possible rate The amount of power output for each ports
July 2006
319
no Defect loss Of Framing loss Of Signal loss Of Power loss Of Signal Quality
SNR margin (dB) Attenuation (dB) Output power (dBm) Attainable rate (kbps) Vender ID Serial number Version number
The signal to noise margin in dB on each port The Attenuation on each port The amount of power output for each ports The highest possible rate Vendor ID Serial number Version Number
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
July 2006
320
Channel Status Expand 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
July 2006
321
Previous Status The 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
July 2006
322
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 Info Expand 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
July 2006
323
Rate Summary Expand 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
July 2006
324
Configured rate
Port Label iAN8K 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
July 2006
325
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 Loading iAN8K 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.
July 2006
326
iSmart This 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:
July 2006
327
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.
July 2006
328
CPE The 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. Its 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.
July 2006
329
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
July 2006
330
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:
July 2006
331
ATM VC Expand 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
July 2006
332
Auto detection (PPPoA to PPPoE conversion enabled) Based on detection results: or Auto detection (PPPoA to PPPoE conversion disabled)
LLC-mux PPPoA LLC-mux Bridge VC-mux Bridge VC-mux PPPoA Unknown In-detection
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 Profile Note: Configure the packet priority on WAN port after configure the traffic profiles.
July 2006
333
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. Table 114 IPxDSL - Traffic Profile - Modification Table
TM profile is assigned port adm (locked/unlocked) re-assign? modify? deleted? TM profile is not assigned port adm (locked/unlocked) re-assign? modify? deleted? yes yes yes port ops (up/down) yes yes yes yes no no port ops (up/down) yes no no
Expand an IPxDSL module. Select ATM VC and click Traffic Profile tab to open Figure 256. Click Retrieve to obtain the latest information.
July 2006
334
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.
July 2006
335
Bridge
MAC Address Per Port Packet Policing Forwarding Database ARP Table Flood Limit
MAC Address Per Port The 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.
July 2006
336
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.
July 2006
337
Figure 259 IPxDSL - Bridge - MAC Address Per Port - Modify Window
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.
July 2006
338
Figure 260 IPxDSL - Bridge - Packet Policing - Packet Policing Setup Window
Table 116 IPxDSL - Bridge - Packet Policing - Packet Policing Setup Table
Field ADSL Port 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. 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 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. 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. Description Select the appropriate ADSL Port for packet policing setup.
IP
Static
July 2006
339
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 Database IPxDSL 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
July 2006 iAN8K B1000 Operations Manual
340
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
July 2006
341
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.
iAN8K B1000 Operations Manual
July 2006
342
ARP Table Address 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.
July 2006
343
Flood Limit When 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.
July 2006
344
IGMP
Authentication Parameter This feature applies for video service. Expand an IPxDSL module and select IGMP and to open Figure 266. Click Retrieve to obtain the latest information.
July 2006
345
Select an entry and click Modify. Configure the parameter and click Apply in Figure 267. Figure 267 IPxDSL - IGMP - Authentication Parameters - Modify Window
CAC iAN8K B1000 reserves band width for other traffic if oversubscription threshold input less than 100%.
July 2006 iAN8K B1000 Operations Manual
346
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 Group Expand 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.
July 2006
347
Multicast Host Expand 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.
July 2006
348
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
July 2006
349
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:
VLAN Expand an IPxDSL module and select VLAN and to open Figure 271. Click Retrieve to obtain the latest information.
July 2006
350
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.
July 2006
351
Select a port and click Delete in Figure 271 to remove the entry, Ingress Rule Expand an IPxDSL module. Select VLAN and click Ingress Rule tab to open Figure 273. Click Retrieve to obtain the latest information.
July 2006
352
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
July 2006
353
VLAN Untag Expand 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.
July 2006
354
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.
July 2006
355
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.
July 2006
356
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
iAN8K B1000 Operations Manual
July 2006
357
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. Table 123 IPxDSL- QoS - Recommended User Priority to Traffic Class Mappings
Number of Available Traffic Classes 1 0 (Default) 1 User Priority 2 3 4 5 6 7 0 0 0 0 0 0 0 0 2 0 0 0 0 1 1 1 1 3 0 0 0 0 1 1 2 2 4 1 0 0 1 2 2 3 3 5 1 0 0 1 2 3 4 4 6 1 0 0 2 3 4 5 5 7 1 0 0 2 3 4 5 6 8 2 0 1 3 4 5 6 7
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
July 2006
358
packet on the WAN outbound traffic has to be forwarded with an 802.1p tag value set according to the following mapping: Table 124 IPxDSL - QoS - 802.1p Tag Marking on Line Card
Queue index 0 1 2 3 4 5 6 7 Marked 802.1p Tag Value 1 2 0 3 4 5 6 7
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 Expand an IPxDSL module and select QoS to open Figure 279. Click Retrieve to obtain the latest information.
July 2006
359
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
July 2006
360
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 Priority IPxDSL 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.
July 2006
361
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
July 2006
362
802.1p Tag IPxDSL 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: Table 125 IPxDSL - QoS - Port Based Priority - Tag Operation Table
Incoming Port ADSL port ADSL port WAN port WAN port ADSL port ADSL port Any port Any port Destination Port WAN port WAN port ADSL port ADSL port ADSL port ADSL port Any Port Any port Outgoing Port VLAN Tag Configuration Outgoing 802.1p tag tagged untagged tagged untagged tagged untagged tagged untagged Contain 802.1p tag, tag value is the priority of the packet No 802.1p tag Contain 802.1p tag, tag value is the same as incoming packet's priority tag (0, if incoming packet is untagged) No 802.1p tag Contain 802.1p tag, tag value is the priority of the packet No 802.1p tag Contain 802.1p tag, tag value is the same as incoming packet's priority tag (0, if incoming packet is untagged) No 802.1p tag
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.
July 2006
363
July 2006
364
July 2006
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
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.
July 2006
366
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
Bridge PM
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 Expand 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.
July 2006
ICM3 Module
367
July 2006
368
Error Counters Expand 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.
July 2006
ICM3 Module
369
July 2006
370
Traffic Load Expand 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
July 2006
ICM3 Module
371
Bridge PM
Control Expand 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
July 2006
372
5 Minutes Report Expand 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
July 2006
IPADSLx Module
373
15 Minutes Report 15 Minutes Report shares identical parameters with 5 Minutes Report. Please refer to 5 Minutes Report for more details.
IPADSLx Module
WAN Port
ADSL Port
ADSL 15 Minutes Summary ADSL 24 Hours Summary Threshold Controls ATUC 15 Minutes ATUC 24 Hours ATUR 15 Minutes ATUR 24 Hours Channel Level
iAN8K B1000 Operations Manual
July 2006
374
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:
July 2006
IPADSLx Module
375
15 Minutes Report
Bridge PM Control Expand 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
Bridge Select 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.
July 2006 iAN8K B1000 Operations Manual
376
Note: All counters are 32 bits long except incoming/outgoing octets counters are 64 bit long.
iAN8K B1000 Operations Manual
July 2006
IPADSLx Module
377
Note: All counters in Bridge report are automatically reset after the ADSL line is reset or re-trained. 5 Minutes Report Expand 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
July 2006
378
15 Minutes Report 15 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:
Threshold Controls Expand 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.
July 2006
IPADSLx Module
379
15 Minutes Expand an IPADSLx module from the tree view and select WAN Port. Click the 15 Minutes tab to open Figure 296.
July 2006
380
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
July 2006
IPADSLx Module
381
24 Hours 24 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 Threshold Controls ATUC 15 Minutes ATUC 24 Hours ATUR 15 Minutes ATUR 24 Hours Channel Level
ADSL 15 Minutes Summary Select 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.
July 2006
382
one or more CRC-8 anomalies one or more LOS defects one or more SEF defects one or more LPR defects
July 2006
IPADSLx Module
383
18 or more CRC-8 anomalies one or more LOS defects one or more SEF defects one or more LPR defects.
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. This parameter is a count of 1-second intervals with loss of power
ADSL 24 Hours Summary ADSL 24 Hours Summary shares identical parameters with ADSL 15 Minutes Summary. Please refer to ADSL 15 Minutes Summary for more details. Threshold Controls Expand 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.
July 2006
384
ATUC 15 Minutes All 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.
July 2006
IPADSLx Module
385
July 2006
386
ATUC 24 Hours ATUC 24 Hours report shares identical parameters with ATUC 15 Minutes report. Please refer to ATUC 15 Minutes more details. ATUR 15 Minutes ATUR 15 Minutes report shares identical parameters with ATUC 15 Minutes report. Please refer to ATUC 15 Minutes more details. ATUR 24 Hours ATUR 24 Hours report shares identical parameters with ATUC 15 Minutes report. Please refer to ATUC 15 Minutes more details. Channel Level IPADSLx modules support the following channel performance reports for ADSL port:
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.
July 2006
IPADSLx Module
387
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.
July 2006
388
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
July 2006
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.
July 2006
390
July 2006
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
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.
July 2006
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.
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.
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.
July 2006
F4/F5 Loopback
393
July 2006
394
Chapter 9: Diagnostics
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.
July 2006
DELT
395
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.
July 2006
396
Chapter 9: Diagnostics
July 2006
DELT
397
July 2006
398
Chapter 9: Diagnostics
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
July 2006
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.
July 2006
400
Chapter 9: Diagnostics
Description
Open Short
Gauge
July 2006
SELT
401
Downstream
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
150 values that indicate upstream SNR margin in dB/10 at a particular rate are provided, at 100 k increments, up to 15 Mbp.
150 values that indicate downstream SNR margin in dB/10 at a particular rate are provided, at 100 k increments, up to 15 Mbps.
Click Table button to display the numerical data of the test results as shown in Figure 314. Click Close to exit the window.
July 2006
402
Chapter 9: Diagnostics
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.
July 2006
SELT
403
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
July 2006
404
Chapter 9: Diagnostics
July 2006
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:
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
July 2006
406
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.
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.
July 2006
Alarm Report
407
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. Table 143 Node Alarm Tree Entity
Entity Node Shelf Slot Board name Description The top-level entity that represents an IP DSLAM access node. All the system alarms shall be reported on this entity. This entity represents a shelf of the IP DSLAM access node. It is a placeholder entity. It represents a slot in a particular shelf. If a board is inserted in the slot, all the alarms related to the board are reported on this entity. Instance Naming Node name 1 to 6 1 to 16, A, B, P Board type Parent Entity None IP DSLAM node Shelf Slot Slot
<Port Type> Port This entity represents a physical port on a particular board. This is a 1 to 24 base class for specific port entities. Alarms related to a specific port are reported on the respective specific port entity 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. This entity represents an ATM layer Number
Slot
ATM Interface
Interface Id (channel index or the interface number) None None None None
Channel
This entity is a placeholder for the system components of the IP DSLAM access node e.g. fuse, etc. This entity is a placeholder for clock related alarms It represents the PDP fuses. This entity is used to report all the alarms that are detected on external devices like PCU.
Alarm Report
Alarm Report
iAN8K B1000 Operations Manual
July 2006
408
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.
July 2006
Alarm Report
409
July 2006
410
July 2006
Alarm Report
411
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 Entity Type Entity Instance Subtree severity Description Shows the Entity (board, port etc.) for described alarms The location in terms of Shelf-Slot-Port. 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
July 2006
412
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.
iAN8K B1000 Operations Manual
July 2006
Alarm Report
413
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.
July 2006
414
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
July 2006
Alarm List
415
Environmental Fuse Failure Alarm Environmental Fan Failure Alarm Equipment Alarm Equipment Alarm Equipment Alarm Timing Problem
Fuse burned Fan failure External clock down Module removed from a slot Inserted board type mismatch
Null Module Removed from slot x Module type mismatch Specify the slot ID, the physical module type and virtual module type
Node
Critical
Node
Major
Processing Alarm
Node
Warning
MAC address matches provisioned black list ICM switched to redundant unit Standby ICM is running a higher version image
When black N/A list feature is disabled N/A Check ICM board status Install compatible software version
ICM Switchover
Null
Node
Critical
Standby ICM3 Null is running a higher version image Standby ICM3 Null is running a lower version image Feature key can not be found External module work status changed
Node
Warning
Equipment Alarm
Node
Major
Standby ICM is Compatible running a lower software version image version is running Region setting When the could not be region is determined determined A configured external module is not accessible The external module becomes accessible
Critical
Install correct region key file Check external module status. Check connection to the external module. Check configuration of the external module.
Minor
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
July 2006 iAN8K B1000 Operations Manual
416
de-assigned (i.e., module shall become manageable after the virtual module is de-assigned) or after the physical module is removed. External Alarm Table 149 External Alarm List
Event Type Probable Cause Specific Problems Per user configuration Managed Object Per user configuration Severity Per user configuration Occurrence Clear Cause Condition Per user configured alarm Per user configured alarm Remedy Per user configured alarm
Communication Alarm
NULL
Critical
Communication Alarm
NULL
External Ethernet interface, Critical (displayed as FE x where x = 1..4; GE y where y=1..4; or 10G 1) External Ethernet interface Major
NULL
External External link up. Link in trunk down External trunk down
NULL
Critical
Probable Cause Initialization failure Loss of signal Loss of link ATU-R capability mismatch 1 ATU-C Threshold crossed ATU-C Threshold crossed ATU-C Threshold crossed
Specific Problems Null Null No link with ATU-R ATU-C, ATU-R profile setting mismatch 15 Min. LOF, Threshold value, Arm time 15 Min. LOS, Threshold value, Arm time 15 Min. LOL, Threshold value, Arm time
Managed Object ADSL port ADSL Port ADSL Port ADSL Port ADSL port ADSL port ADSL port
July 2006
Alarm List
417
15 Min. CRC Error, Threshold value, Arm time WAN port WAN port WAN port
24 Hr. Alignment Error, Threshold value, Arm WAN port time 24 Hr. CRC Error, Threshold value, Arm time 24 Hr. Over sized Frame, Threshold value, Arm time 24 Hr. Collision, Threshold value, Arm time Automatic Full Retrain engaged WAN port WAN port WAN port DSL Port
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
July 2006 iAN8K B1000 Operations Manual
418
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 Communication Alarm Probable Cause Loss of signal Specific Problems NULL Managed Object SHDSL port Perceived Severity Critical
July 2006
Alarm List
419
Major Critical
Network problem Server down or network problem Display error code from AS
Network problem solved Server up or network problem resolved User can register
Communication Alarm
Minor
Resolve misconfiguration
Accumulate When the next 15 Resolve network troubles min interval d packet loss in a 15 begins min interval exceeds threshold setting Interarrival When the next 15 Resolve network jitter in a 15 min interval troubles min interval begins exceeds threshold setting
QoS Alarm
Minor
July 2006
420
QoS Alarm
Minor
QoS Alarm
Minor
Probable Cause Loss of signal at Ethernet interface Loss of signal at Ethernet interface
Specific Problems FE interface loss of signal before MG interface activates FE interface loss of signal after MG interface activates
Event List for iFXS1 Module Table 156 Event List Based on SIP
Event Type MG interface provisioning Event Information MG interface administrative on/off Register to the AS Logout from the AS AS switchover Description MG interface locked MG interface unlocked Node Node Node switch to other AS
July 2006
Alarm List
421
July 2006
422
July 2006
11
SYSTEM ADMINISTRATION
File Transfer
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.
July 2006
424
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.
July 2006
Software Upgrade
425
Upgrade with A Redundant ICM3 Module Figure 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.
(1)
Active ICM3-A RAM Standby ICM3-B RAM Active ICM3-A RAM
(2)
Standby ICM3-B RAM
OLD
OLD
OLD
OLD
Flash
Flash OLD
Flash NEW
Flash NEW
OLD
(3)
Active ICM3-A RAM Standby ICM3-B RAM Standby ICM3-A RAM
(4)
Active ICM3-B RAM
OLD
NEW
NEW
NEW
Flash NEW
Flash NEW
Flash NEW
Flash NEW
July 2006
426
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 /tmp/tftp/icm2_config.gz /tftpboot/dslfw3a.img /tftpboot/dslfw3b.img /tftpboot/ipadsl3a.img /tftpboot/ipadsl3b.img /tftpboot/pcu.bin /tftpboot/system.key Filesystem file-size 76206 170548 170856 2004588 2010484 8507 396
/dev/mtdblock/1
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.
July 2006
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: You are now in the Privileged Mode AN2000_IB#show memory file /tmp/tftp/icm2_config.gz /tftpboot/dslfw3a.img /tftpboot/dslfw3b.img /tftpboot/ipadsl3a.img /tftpboot/ipadsl3b.img /tftpboot/pcu.bin /tftpboot/system.key Filesystem file-size 76206 170548 170856 2004588 2010484 8507 396
/dev/mtdblock/1
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
July 2006 iAN8K B1000 Operations Manual
428
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
iAN8K B1000 Release 3.1 IP ATM Service Module (ASM) Operations Manual UTSI-NJTC-20050699
File Transfer
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.
July 2006
File Transfer
429
The TFTP window is prompted as shown in Figure 328. Expand the window with the arrows to view the directories.
July 2006
430
In Figure 329, the left side displays the directories for the local station and the right side displays the node directories.
July 2006
File Transfer
431
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.
July 2006
432
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.
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.
July 2006
433
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
July 2006
434
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: You are now in the Privileged Mode 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.
July 2006
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
July 2006
436
July 2006
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
Analysis
438
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
July 2006
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.
July 2006
440
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.
July 2006
441
7 Select the WAN port and click Edit. Apply both profiles to Outbound of WAN port as shown in Figure 337.
July 2006
442
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.
July 2006
IP Address Conflict
443
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
iAN8K B1000 Operations Manual
July 2006
444
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 1 From Profile menu, select Access List Profiles shown in Figure 339 to open the access list profile summary shown in Figure 340. Figure 339 Profile Menu - Access List Profiles
July 2006
IP Address Conflict
445
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).
July 2006
446
5 The new profiles are shown in Figure 343. Figure 343 IP Address Conflict - 2 Profiles Added
6 Select the Access List of the IPxDSL module to open Figure 344.
July 2006
IP Address Conflict
447
7 Select the WAN port and click Edit. Apply both profiles to Outbound of WAN port as shown in Figure 345.
July 2006
448
8 The result is shown in Figure 346. Access control configuration for IP address conflict is complete.
July 2006
449
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.
Analysis
Solution 1 From Profile menu, select Access List Profiles shown in Figure 347 to open the access list profile summary shown in Figure 348.
July 2006 iAN8K B1000 Operations Manual
450
2 Click Add in Figure 348 to create profiles. 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.
July 2006
451
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.
July 2006
452
Figure 350 FTP Access Deny - Add Access List Profile - Permit
5 The new profiles are shown in Figure 351. Figure 351 FTP Access Deny - 2 Profiles Added
6 Select the Access List of the IPxDSL module to open Figure 352.
July 2006
453
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
July 2006
454
Figure 353 FTP Access Deny - IPxDSL Module - Applying Profiles to Inbound
July 2006
455
Figure 354 FTP Access Deny - IPxDSL Module - Applying Profiles to Outbound
8 The result is shown in Figure 355. Access control configuration for PPPoE access denial is complete.
July 2006
456
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.
Analysis
sz.tencent.com 61. 144. 238. 145 sz2.tencent.com 61. 144. 238. 146 sz3.tencent.com 202. 104. 129. 25
457
Solution 1 From Profile menu, select Access List Profiles shown in Figure 356 to open the access list profile summary shown in Figure 357. Figure 356 Profile Menu - Access List Profiles
2 Click Add in Figure 357 to create profiles. 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.
July 2006
458
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.
July 2006
459
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.
July 2006
460
Figure 360 ABC IM Service Access Deny - Add Access List Profile - Permit
6 The new profiles are shown in Figure 361. Figure 361 ABC IM Service Access Deny - 3 Profiles Added
7 Select the Access List of the IPxDSL module to open Figure 362.
July 2006
461
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.
July 2006
462
Figure 363 ABC IM Service Access Deny - IPxDSL Module - Applying Profiles to Outbound
9 The result is shown in Figure 364. Access control configuration for PPPoE access denial is complete.
July 2006
463
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.
July 2006
464
July 2006
UTStarcom, Inc. USA 1275 Harbor Bay Parkway Alameda, CA 94502, USA Tel. 510-864-8800 Fax. 510-864-8802
China No. 368 Liuhe Road, Hi-Tech Industry Development Zone, Binjiang, Hangzhou 310053, PRC +86-571-81920000
India 805 Signature Towers II, South City I Gurgaon, Haryana 122001, India +91 124 5166100
Japan Shiba Koen Parktower 9F/10F 2-11-1 Shiba-koen, Minato-ku Tokyo 105-0011 JAPAN +81-3-6430-8600
Latin America 2801 SW 149th Ave Suite 100 Miramar, FL 33027, USA 954-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. UTStarcoms 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.