Page 1
Interface Configuration Guide
7705 SERVICE AGGREGATION
ROUTER | RELEASE 8.0.R7
Interface Configuration Guide
3HE 11011 AAAC TQZZA
Edition: 01
September 2017
Nokia — Proprietary and confidential.
Use pursuant to applicable agreements.
Page 2
Interface Configuration Guide
Nokia is a registered trademark of Nokia Corporation. Other products and company
names mentioned herein may be trademarks or tradenames of their respective
owners.
The information presented is subject to change without notice. No responsibility is
assumed for inaccuracies contained herein.
© 2016-2017 Nokia.
Contains proprietary/trade secret information which is the property of Nokia and must
not be made available to, or copied or used by anyone outside Nokia without its
written authorization. Not to be used or disclosed except in accordance with
applicable agreements.
2
3HE 11011 AAAC TQZZA Edition: 01
Page 3
Interface Configuration Guide
Table of Contents
1 Preface...........................................................................................15
1.1 About This Guide.......................................................................................15
1.1.1 Audience....................................................................................................17
1.1.2 List of Technical Publications ....................................................................17
1.1.3 Technical Support......................................................................................18
2 7705 SAR Interface Configuration Process................................19
3 7705 SAR Interfaces.....................................................................21
3.1 Configuration Overview .............................................................................22
3.1.1 Configuring the IOM and Card Slot ...........................................................22
3.1.2 Configuring Adapter Cards and Modules ..................................................23
3.1.2.1 Provisioning Chassis Slots for Adapter Cards...........................................23
3.1.2.2 Maximum Number of Adapter Cards in a Chassis ....................................24
3.1.2.3 Evolution of Ethernet Adapter Cards, Modules, and Platforms .................27
3.1.2.4 Channelized Adapter Card Support...........................................................28
3.1.3 Configuring Ports.......................................................................................29
3.1.3.1 Ethernet .....................................................................................................30
3.1.3.2 TDM...........................................................................................................37
3.1.3.3 DSL............................................................................................................41
3.1.3.4 GNSS Receiver .........................................................................................42
3.1.3.5 GPON ........................................................................................................42
3.1.3.6 Multilink Bundles........................................................................................43
3.1.3.7 IMA ............................................................................................................43
3.1.3.8 SONET/SDH..............................................................................................43
3.1.3.9 Voice..........................................................................................................44
3.1.3.10 Microwave Link..........................................................................................48
3.1.3.11 CLI Identifiers for Adapter Cards, Modules and Platforms ........................48
3.1.3.12 Access, Network, and Hybrid Ports ...........................................................54
3.1.4 Configuring SCADA Bridges......................................................................66
3.2 Port Features.............................................................................................67
3.2.1 Multilink Point-to-Point Protocol.................................................................68
3.2.1.1 MLPPP Overview ......................................................................................68
3.2.1.2 Protocol Field (PID) ...................................................................................70
3.2.1.3 B&E Bits ....................................................................................................70
3.2.1.4 Sequence Number.....................................................................................70
3.2.1.5 Information Field........................................................................................70
3.2.1.6 Padding .....................................................................................................71
3.2.1.7 FCS ...........................................................................................................71
3.2.1.8 LCP............................................................................................................71
3.2.1.9 T1/E1 Link Hold Timers .............................................................................72
3.2.2 Multi-Class MLPPP....................................................................................72
3.2.2.1 QoS in MC-MLPPP....................................................................................73
3.2.3 cHDLC ......................................................................................................75
3.2.3.1 SLARP ......................................................................................................76
Edition: 01 3HE 11011 AAAC TQZZA 3
Page 4
Interface Configuration Guide
3.2.4 Inverse Multiplexing Over ATM (IMA)........................................................76
3.2.5 Network Synchronization on Ports and Circuits ........................................77
3.2.5.1 Network Synchronization on T1/E1, Ethernet, GPON, and DSL
Ports ..........................................................................................................77
3.2.5.2 Network Synchronization on SONET/SDH Ports ......................................79
3.2.5.3 Network Synchronization on DS3/E3 Ports ...............................................80
3.2.5.4 Network Synchronization on DS3 CES Circuits ........................................80
3.2.5.5 Network Synchronization on T1/E1 Ports and Circuits..............................80
3.2.6 Node Synchronization From GNSS Receiver Ports ..................................81
3.2.7 Flow Control on Ethernet Ports .................................................................82
3.2.8 Ethernet OAM............................................................................................82
3.2.8.1 Ethernet OAM Overview............................................................................83
3.2.8.2 CRC (Cyclic Redundancy Check) Monitoring............................................84
3.2.8.3 Remote Loopback .....................................................................................85
3.2.8.4 802.3ah OAMPDU Tunneling and Termination for Epipe Service.............86
3.2.8.5 Dying Gasp................................................................................................87
3.2.9 Ethernet Loopbacks...................................................................................87
3.2.9.1 Line and Internal Ethernet Loopbacks.......................................................88
3.2.9.2 CFM Loopbacks for OAM on Ethernet Ports .............................................89
3.2.10 Ethernet Port Down-When-Looped ...........................................................93
3.2.11 Ethernet Ring (Adapter Card and Module) ................................................94
3.2.12 MTU Configuration Guidelines ..................................................................95
3.2.12.1 MTU Configuration Overview ....................................................................95
3.2.12.2 IP Fragmentation.......................................................................................97
3.2.12.3 Jumbo Frames...........................................................................................97
3.2.12.4 Default Port MTU Values.........................................................................100
3.2.13 LAG .........................................................................................................102
3.2.13.1 LAG Overview .........................................................................................103
3.2.13.2 LACP and Active/Standby Operation ......................................................106
3.2.13.3 QoS Adaptation for LAG on Access ........................................................108
3.2.13.4 Access Ingress Fabric Shaping...............................................................111
3.2.13.5 Hold-down Timers ...................................................................................112
3.2.13.6 Multi-Chassis LAG...................................................................................112
3.2.13.7 Static LAG (Active/Standby LAG Operation without LACP) ....................113
3.2.13.8 LAG Support on Mixed-Generation Hardware.........................................114
3.2.14 LAG and ECMP Hashing.........................................................................119
3.2.14.1 Per-Flow Hashing....................................................................................120
3.2.14.2 Per-Service Hashing................................................................................122
3.2.14.3 LSR Hashing ...........................................................................................123
3.2.14.4 Layer 4 Load Balancing...........................................................................125
3.2.14.5 TEID Hashing for GTP-encapsulated Traffic ...........................................126
3.2.14.6 Entropy Labels.........................................................................................126
3.2.15 Automatic Protection Switching ...............................................................127
3.2.15.1 APS Overview .........................................................................................127
3.2.15.2 SC-APS ...................................................................................................128
3.2.15.3 MC-APS...................................................................................................129
3.2.15.4 K1 and K2 Bytes......................................................................................132
3.2.15.5 Revertive Mode .......................................................................................135
3.2.15.6 APS Tools Commands ............................................................................136
4
3HE 11011 AAAC TQZZA Edition: 01
Page 5
Interface Configuration Guide
3.2.15.7 APS Failure Codes..................................................................................138
3.2.16 Deploying Preprovisioned Components ..................................................139
3.2.17 Microwave Link........................................................................................140
3.2.17.1 Microwave Link Overview........................................................................140
3.2.17.2 Standalone Mode ....................................................................................141
3.2.17.3 Single NE Mode.......................................................................................141
3.2.17.4 Frequency Synchronization .....................................................................150
3.2.17.5 RSL History .............................................................................................150
3.2.18 DSL Bonding ...........................................................................................152
3.2.18.1 DSL Bonding Overview ...........................................................................152
3.2.18.2 ATM Bonding...........................................................................................153
3.2.18.3 PTM Bonding...........................................................................................154
3.2.18.4 Pairs Within a Bonded Group..................................................................155
3.2.18.5 Configuration ...........................................................................................156
3.2.18.6 Layer 3 Protocol Support and Service Provisioning ................................157
3.2.19 Custom Alarms on Ethernet Ports ...........................................................158
3.3 802.1x Network Access Control ..............................................................159
3.3.1 802.1x Basics ..........................................................................................160
3.3.2 802.1x Modes ..........................................................................................162
3.3.3 802.1x Timers..........................................................................................163
3.3.4 802.1x Configuration and Limitations ......................................................164
3.4 MAC Authentication.................................................................................166
3.5 Link Layer Discovery Protocol (LLDP).....................................................168
3.5.1 LLDP Protocol Features ..........................................................................170
3.6 Surveillance, Control, and Data Acquisition (SCADA) Support ...............172
3.6.1 Multidrop Data Bridge..............................................................................172
3.6.2 PCM Multidrop Bridge .............................................................................174
3.6.3 Redundant Masters .................................................................................176
3.6.4 Squelch Functionality ..............................................................................176
3.6.5 Voice Conference Bridge.........................................................................177
3.6.5.1 VCB Applications.....................................................................................178
3.6.5.2 Gain .........................................................................................................178
3.6.6 Serial Transport Over Raw Sockets ........................................................179
3.6.6.1 Raw Socket Configuration .......................................................................181
3.6.6.2 Raw Socket Packet Processing...............................................................181
3.6.6.3 Raw Socket Squelch Functionality ..........................................................183
3.7 Configuration Notes.................................................................................184
3.7.1 Reference Sources..................................................................................184
3.8 Configuring Physical Components with CLI ............................................185
3.9 Preprovisioning Guidelines......................................................................186
3.9.1 Predefining Entities..................................................................................186
3.9.2 Preprovisioning a Port or SCADA Bridge ................................................186
3.9.3 Maximizing Bandwidth Use .....................................................................187
3.9.4 Using Partial Bandwidth ..........................................................................188
3.10 Basic Configuration .................................................................................190
3.11 Common Configuration Tasks .................................................................194
3.11.1 Configuring Cards and Adapter Cards ....................................................195
3.11.1.1 Configuring Cards....................................................................................195
3.11.1.2 Configuring Adapter Card Network Queue QoS Policies ........................198
Edition: 01 3HE 11011 AAAC TQZZA 5
Page 6
Interface Configuration Guide
3.11.1.3 Configuring Ring Adapter Card or Module Network and Network
Queue QoS Policies ................................................................................198
3.11.1.4 Configuring Adapter Card Fabric Statistics .............................................199
3.11.1.5 Configuring Adapter Card Fabric Profile..................................................199
3.11.1.6 Configuring Adapter Card Clock Mode....................................................200
3.11.1.7 Configuring Adapter Card Voice Attributes..............................................201
3.11.1.8 Configuring Ring Adapter Card or Module Parameters...........................202
3.11.1.9 Configuring Auxiliary Alarm Card, Chassis, and Ethernet Port
External Alarm Parameters .....................................................................203
3.11.1.10 Displaying Adapter Card Information.......................................................206
3.11.2 Configuring Ports.....................................................................................208
3.11.2.1 Configuring APS Port Parameters...........................................................209
3.11.2.2 Configuring a Microwave Link .................................................................222
3.11.2.3 Configuring Ethernet Port Parameters ....................................................223
3.11.2.4 Configuring DSL Port Parameters ...........................................................230
3.11.2.5 Configuring SONET/SDH Port Parameters .............................................232
3.11.2.6 Configuring Voice Ports...........................................................................240
3.11.2.7 Configuring Teleprotection Ports .............................................................244
3.11.2.8 Configuring TDM PPP .............................................................................245
3.11.2.9 Configuring Channelized Ports................................................................245
3.11.2.10 Configuring Fractional T1/E1 Ports for PPP Encapsulation ....................251
3.11.2.11 Configuring T1 Line Buildout ...................................................................254
3.11.2.12 Configuring TDM E1 SSM .......................................................................255
3.11.2.13 Configuring ATM Interface Parameters ...................................................256
3.11.2.14 Configuring Multilink PPP Bundles..........................................................257
3.11.2.15 Configuring MC-MLPPP .........................................................................259
3.11.2.16 Configuring LAG Parameters ..................................................................260
3.11.2.17 Configuring Multilink ATM Inverse Multiplexing (IMA) Groups ................262
3.11.2.18 Configuring SDI Ports for IPCP Encapsulation .......................................265
3.11.2.19 Configuring TDM and SDI Ports for Frame Relay Encapsulation ...........267
3.11.2.20 Configuring TDM and SDI Ports for HDLC Encapsulation ......................271
3.11.2.21 Configuring TDM and SDI Ports for Cisco HDLC Encapsulation ............274
3.11.2.22 Configuring GNSS Receiver Port Parameters.........................................276
3.11.2.23 Configuring Serial Ports for Raw Socket Transport.................................277
3.11.3 Configuring SCADA Bridge Parameters..................................................277
3.12 Service Management Tasks ....................................................................281
3.12.1 Changing a Provisioned Adapter Card Type ...........................................281
3.12.2 Deleting an Adapter Card ........................................................................282
3.13 Configuration Command Reference ........................................................283
3.13.1 Command Hierarchies.............................................................................283
3.13.1.1 Card Commands .....................................................................................284
3.13.1.2 Adapter Card Commands........................................................................284
3.13.1.3 External Alarm Commands......................................................................285
3.13.1.4 APS Port Commands ..............................................................................286
3.13.1.5 Microwave Link Commands ....................................................................286
3.13.1.6 Port Configuration Commands ................................................................287
3.13.1.7 Ethernet Commands................................................................................287
3.13.1.8 DSL Commands ......................................................................................289
3.13.1.9 GPON Commands...................................................................................290
6
3HE 11011 AAAC TQZZA Edition: 01
Page 7
Interface Configuration Guide
3.13.1.10 GNSS Commands ...................................................................................291
3.13.1.11 IEEE 802.1x Ethernet Port Commands ...................................................291
3.13.1.12 LLDP Ethernet Port Commands ..............................................................292
3.13.1.13 Ring Virtual Port Ethernet Commands ....................................................292
3.13.1.14 Ring MAC Operations Commands ..........................................................293
3.13.1.15 Multilink Bundle and IMA Group Commands...........................................293
3.13.1.16 Serial Commands ....................................................................................294
3.13.1.17 SONET/SDH Commands ........................................................................298
3.13.1.18 TDM Commands .....................................................................................299
3.13.1.19 DS1 Commands ......................................................................................299
3.13.1.20 DS3 Commands ......................................................................................301
3.13.1.21 E1 Commands.........................................................................................303
3.13.1.22 E3 Commands.........................................................................................304
3.13.1.23 Voice Commands ....................................................................................305
3.13.1.24 LAG Commands......................................................................................306
3.13.1.25 SCADA Commands.................................................................................307
3.13.2 Command Descriptions ...........................................................................309
3.13.2.1 Generic Commands.................................................................................310
3.13.2.2 Card Commands .....................................................................................313
3.13.2.3 Adapter Card Commands........................................................................315
3.13.2.4 Interface QoS Commands .......................................................................325
3.13.2.5 External Alarm Commands......................................................................330
3.13.2.6 APS Port Commands ..............................................................................338
3.13.2.7 Microwave Link Commands ....................................................................344
3.13.2.8 General Port Commands.........................................................................349
3.13.2.9 Ethernet Commands ...............................................................................351
3.13.2.10 DSL Commands ......................................................................................383
3.13.2.11 GPON Commands...................................................................................385
3.13.2.12 GNSS Commands ...................................................................................386
3.13.2.13 IEEE 802.1x Ethernet Port Commands ..................................................388
3.13.2.14 LLDP Ethernet Port Commands ..............................................................393
3.13.2.15 Ring MAC Operations Commands .........................................................396
3.13.2.16 Serial Commands ....................................................................................400
3.13.2.17 RS-232, V.35, and X.21 Channel Group Commands..............................423
3.13.2.18 SONET/SDH Port Commands.................................................................428
3.13.2.19 SONET/SDH Path Commands................................................................434
3.13.2.20 Network Port Commands ........................................................................441
3.13.2.21 Multilink Bundle and IMA Group Commands...........................................447
3.13.2.22 ATM Interface Commands.......................................................................457
3.13.2.23 TDM Commands .....................................................................................459
3.13.2.24 DS1 and E1 Commands..........................................................................466
3.13.2.25 DS1 and E1 Channel Group Commands ................................................476
3.13.2.26 DS3 and E3 Commands..........................................................................484
3.13.2.27 Voice Commands ....................................................................................491
3.13.2.28 Voice Channel Group Commands...........................................................499
3.13.2.29 LAG Commands......................................................................................501
3.13.2.30 Frame Relay Commands.........................................................................510
3.13.2.31 Cisco HDLC Commands .........................................................................515
3.13.2.32 SCADA Commands.................................................................................517
Edition: 01 3HE 11011 AAAC TQZZA 7
Page 8
Interface Configuration Guide
3.14 Show, Monitor, Clear, and Debug Command Reference ........................525
3.14.1 Command Hierarchies.............................................................................525
3.14.1.1 Show Commands ....................................................................................526
3.14.1.2 Monitor Commands .................................................................................527
3.14.1.3 Clear Commands.....................................................................................527
3.14.1.4 Debug Commands...................................................................................527
3.14.2 Command Descriptions ...........................................................................528
3.14.2.1 Show Commands ....................................................................................529
3.14.2.2 Monitor Commands .................................................................................836
3.14.2.3 Clear Commands.....................................................................................844
3.14.2.4 Debug Commands...................................................................................848
5 Standards and Protocol Support ..............................................877
8
3HE 11011 AAAC TQZZA Edition: 01
Page 9
Interface Configuration Guide
List of Tables
2 7705 SAR Interface Configuration Process................................19
Table 1 Configuration Process .............................................................................19
3 7705 SAR Interfaces.....................................................................21
Table 2 Ethernet Adapter Card, Module, and Platform Generations .....................27
Table 3 Maximum Number of Cards/Modules Supported in Each Chassis ...........33
Table 4 Configuration Options for the 6-port E&M Adapter Card ..........................45
Table 5 Configuration Options for the 6-port FXS Adapter Card ...........................47
Table 6 Default Port Mode per Adapter Card, Module, or Platform .......................57
Table 7 MC-MLPPP Class Priorities ......................................................................74
Table 8 Packet Forwarding Class to MC-MLPPP Class Mapping ........................74
Table 9 cHDLC Information Frame ........................................................................75
Table 10 Loopbacks Supported on Ethernet, DSL, and GPON Ports .....................87
Table 11 Maximum MTU (or MRU) per Ethernet Encapsulation Type ...................97
Table 12 Port MTU Default and Maximum Values ...............................................101
Table 13 Adaptive QoS Rate and Bandwidth Distribution ....................................109
Table 14 Port Command Applicability for LAG Configurations on Mixed-
Table 15 Hashing Algorithm Inputs (ECMP and LAG) .........................................120
Table 16 K1 Byte Switch Priorities .......................................................................132
Table 17 K2 Byte Functions .................................................................................134
Table 18 1+1 APS for Bidirectional Mode – Actions Taken ...................................135
Table 19 RSL History Attributes ...........................................................................151
Table 20 DSL Pairs by Bonding Group .................................................................153
Table 21 DSL Module and Port Limits ...................................................................157
Table 22 PCM Multidrop Bridge Modularity ...........................................................175
Table 23 VCB Modularity .......................................................................................177
Table 24 Shaper Policy Defaults ..........................................................................327
Table 25 Port MTU Default and Maximum Values ...............................................372
Table 26 Supported PoE/PoE+ Combinations on the 7705 SAR-H ......................375
Table 27 Synchronous Clocking Options .............................................................402
Table 28 Adapter Cards and Encapsulation Types in Access Mode .....................477
Table 29 Default and Maximum Port MTU ............................................................481
Table 30 Idle and Seized Codes for FXO and FXS Signaling Types ....................492
Table 31 Show APS Output Fields .......................................................................531
Table 32 Show Card Output Fields ......................................................................535
Table 33 Show Card State Output Fields .............................................................539
Table 34 Show Card (IOM) Detailed Output Fields ..............................................540
Table 35 Show CSM Card Output Fields .............................................................542
Table 36 Show MDA Output Fields ......................................................................547
Table 37 Show MDA Detail Output Fields ............................................................558
Table 38 Show MDA Fabric Statistics Output Fields .............................................563
Table 39 Show MDA Fabric IP-Transport Statistics Output Fields ........................569
Table 40 Show MDA Fabric Mirror Statistics Output Fields ..................................571
Table 41 Show MDA Fabric Security Encryption Statistics Output Fields .............573
Generation Hardware ............................................................................118
Edition: 01 3HE 11011 AAAC TQZZA 9
Page 10
Interface Configuration Guide
Table 42 Show MDA Fabric Security Firewall Statistics Output Fields .................575
Table 43 Show MDA With Fabric Statistics Output Fields .....................................576
Table 44 Show MDA Aggregate Statistics Output Fields ......................................583
Table 45 Show MDA Ring FDB Output Fields .......................................................587
Table 46 Show Specific Alarm Fields ...................................................................590
Table 47 Show External Alarm Input Fields .........................................................593
Table 48 Show External Alarm Input Detail Fields ...............................................594
Table 49 Show External Alarm Output Fields .......................................................596
Table 50 Show External Alarm Output Detail Fields ............................................597
Table 51 Show External Alarm Name Fields ........................................................598
Table 52 Show Microwave Link Detail Fields .......................................................602
Table 53 Show MPR-e Radio Detail Fields ..........................................................604
Table 54 Show MPR-e Radio Power Measurement Fields ..................................606
Table 55 Show MPR-e Radio Software State Fields ............................................606
Table 56 Show General Port Output Fields ..........................................................614
Table 57 Show Port Statistics Output Fields ........................................................617
Table 58 Show Specific Port Output Fields (GigE Port with Optical SFP) ............620
Table 59 Show PoE Port Output Fields (Ethernet) ................................................632
Table 60 Show Specific Port Output Fields (Serial Port) .......................................640
Table 61 Show Specific Port Output Fields (SONET/SDH Port) ...........................642
Table 62 Show Specific Port Output Fields (E&M Voice Port) ..............................647
Table 63 Show Specific Port Output Fields (FXO Voice Port) ...............................649
Table 64 Show Specific Port Output Fields (FXS Voice Port) ...............................650
Table 65 Show Specific Port Output Fields (DS0 Voice Channel Group) .............652
Table 66 Show Port Detail Output Fields (SONET/SDH Port) .............................655
Table 67 Show Port Detail Output Fields (Ethernet, Access Mode) ......................662
Table 68 Show Port Detail Output Fields (Ethernet, Network Mode) ....................674
Table 69 Show Port Detail Output Fields (DSL) ....................................................676
Table 70 Show Port Detail Output Fields (GPON) ................................................684
Table 71 Show Port Detail Output Fields (Ring Ethernet) .....................................694
Table 72 Show Port Detail Output Fields (v-port) ..................................................704
Table 73 Show Port Detail Output Fields (TDM DS1 Interface) ...........................715
Table 74 Show Port Serial Channel Output Fields ................................................722
Table 75 Show Port Voice Channel Output Fields ................................................732
Table 76 Show Port Channel Group Output Fields ..............................................738
Table 77 Show Port Channelized DS3 Output Fields ...........................................742
Table 78 Show Port Clear Channel DS3 Output Fields ........................................746
Table 79 Show Port ACR Detail Output Fields ......................................................748
Table 80 Show Port dot1x Output Fields ..............................................................751
Table 81 Show Port Description Output Fields ......................................................757
Table 82 Show Port Associations Output Fields ..................................................758
Table 83 Show Port IMA Link Output Fields ..........................................................759
Table 84 Show Port PPP Output Fields ................................................................761
Table 85 Show Port CEM Output Fields ................................................................762
Table 86 Show Port Frame Relay Output Fields ...................................................764
Table 87 Show Port Frame Relay DLCI Output Fields ..........................................767
Table 88 Show Port Output Fields (TDM Codirectional or TPIF) ..........................772
Table 89 Show Port Output Fields (GNSS) ...........................................................774
Table 90 Show DSL Port Output Fields .................................................................778
10
3HE 11011 AAAC TQZZA Edition: 01
Page 11
Interface Configuration Guide
Table 91 Show Port LLDP Output Fields ...............................................................781
Table 92 Show Port LLDP Detail Output Fields ...................................................783
Table 93 Show Port ATM Output Fields ...............................................................786
Table 94 Show Port ATM Connections Output Fields ...........................................788
Table 95 Show Port ATM PVC Output Fields ........................................................789
Table 96 Show Port ATM PVC VPI/VCI Output Fields ..........................................790
Table 97 Show Port ATM PVC VPI/VCI Detail Output Fields ................................791
Table 98 Show Port ATM PVP Output Fields .......................................................793
Table 99 Show Port ATM PVP Detail Output Fields .............................................794
Table 100 Show Port-tree Output Fields ................................................................797
Table 101 Show LAG Summary Output Fields .......................................................799
Table 102 Show LAG Detailed Output Fields .........................................................801
Table 103 Show LAG Statistics Output Fields ........................................................804
Table 104 Show LAG Associations Output Fields ..................................................804
Table 105 Show LAG Description Output Fields ....................................................805
Table 106 Show LAG LACP Partner Output Fields ................................................806
Table 107 Show LAG Detailed LACP Partner Output Fields ..................................808
Table 108 Show LAG Port Output Fields ...............................................................809
Table 109 Show Multilink Bundle Output Fields .....................................................812
Table 110 Show Multilink Bundle IMA Group Output Fields ...................................814
Table 111 Show Multilink Bundle IMA Group Detailed Output Fields ....................816
Table 112 Show Multilink Bundle MLPPP Output Fields ........................................820
Table 113 Show Multilink Bundle MLPPP Detail Fields .........................................822
Table 114 Show Multilink Bundle IMA ATM Output Fields ......................................827
Table 115 Show Multilink Bundle IMA ATM Connections Output Fields .................827
Table 116 Show Multilink Bundle IMA ATM PVC Output Fields .............................829
Table 117 Show Multilink-bundle IMA ATM PVP Output Fields .............................830
Table 118 Show SCADA Bridge Detail Output Fields ............................................832
Table 119 Show Specific SCADA Bridge Detail Output Fields ...............................833
4 List of Acronyms ........................................................................849
Table 120 Acronyms ...............................................................................................849
5 Standards and Protocol Support ..............................................877
Table 121 EMC Industrial Standards Compliance ...................................................878
Table 122 EMC Regulatory and Customer Standards Compliance ........................879
Table 123 Environmental Standards Compliance ...................................................882
Table 124 Safety Standards Compliance ................................................................883
Table 125 Telecom Interface Compliance ...............................................................885
Table 126 Directives, Regional Approvals and Certifications Compliance ..............886
Edition: 01 3HE 11011 AAAC TQZZA 11
Page 12
Interface Configuration Guide
12
3HE 11011 AAAC TQZZA Edition: 01
Page 13
Interface Configuration Guide
List of Figures
3 7705 SAR Interfaces.....................................................................21
Figure 1 Hybrid Port Application ..............................................................................65
Figure 2 MLPPP 24-bit Fragment Format................................................................69
Figure 3 MLPPP 12-bit Fragment Format................................................................69
Figure 4 Original MLPPP Header Format................................................................73
Figure 5 MC-MLPPP Header Format ......................................................................73
Figure 6 EFM Capability on the 7705 SAR..............................................................86
Figure 7 CFM Loopback on Ethernet Ports .............................................................91
Figure 8 MTU Points on the 7705 SAR ...................................................................96
Figure 9 LAG on Access Interconnection ..............................................................107
Figure 10 LAG on Access Failure Switchover .........................................................107
Figure 11 SC-APS with Physical Port and Adapter Card Protection .......................129
Figure 12 SC-APS Application.................................................................................129
Figure 13 MC-APS with Physical Port, Adapter Card and Node Protection............131
Figure 14 MC-APS Application................................................................................131
Figure 15 MC-APS with Pseudowire Redundancy and ICB ....................................132
Figure 16 1+1 HSB with SD Deployment ................................................................148
Figure 17 Example of a TDA Application.................................................................149
Figure 18 802.1x Architecture..................................................................................160
Figure 19 Authentication Scenario...........................................................................162
Figure 20 802.1x EAPOL Timers and RADIUS Timers ...........................................164
Figure 21 LLDP Internal Architecture for a Network Node ......................................169
Figure 22 Network Example For LLDP....................................................................170
Figure 23 LLDPDU Format......................................................................................171
Figure 24 SCADA MDDB Network ..........................................................................174
Figure 25 SCADA PCM Multidrop Bridge Network..................................................175
Figure 26 Serial Transport Over Raw Socket Application .......................................180
Figure 27 Raw Socket Packet Processing...............................................................182
Edition: 01 3HE 11011 AAAC TQZZA 13
Page 14
Interface Configuration Guide
14
3HE 11011 AAAC TQZZA Edition: 01
Page 15
Interface Configuration Guide Preface
1 Preface
1.1 About This Guide
This guide describes system concepts and provides configuration examples to
provision CSM cards, adapter cards, modules and ports for the 7705 SAR.
This guide is organized into functional chapters and provides concepts and
descriptions of the implementation flow, as well as Command Line Interface (CLI)
syntax and command usage.
For hardware information on the 7705 SAR chassis, adapter cards, and modules,
including installation, connections, LEDs, and pinouts, refer to:
• 7705 SAR-8 Chassis Installation Guide
• 7705 SAR-18 Chassis Installation Guide
• 7705 SAR-A Chassis Installation Guide
• 7705 SAR-Ax Chassis Installation Guide
• 7705 SAR-H Chassis Installation Guide
• 7705 SAR-Hc Chassis Installation Guide
• 7705 SAR-M Chassis Installation Guide
• 7705 SAR-O Chassis Installation Guide
• 7705 SAR-W Chassis Installation Guide
• 7705 SAR-Wx Chassis Installation Guide
• 7705 SAR-X Chassis Installation Guide
• 7705 SAR 10-port 1GigE/1-port 10GigE X-Adapter Card Installation Guide
• 7705 SAR 2-port 10GigE (Ethernet) Adapter Card/Module Installation Guide
• 7705 SAR 4-port SAR-H Fast Ethernet Module Installation Guide
• 7705 SAR 4-port T1/E1 and RS-232 Combination Module Installation Guide
• 7705 SAR 6-port E&M Adapter Card Installation Guide
• 7705 SAR 6-port FXS Adapter Card Installation Guide
• 7705 SAR 6-port SAR-M Ethernet Module Installation Guide
• 7705 SAR 8-port FXO Adapter Card Installation Guide
• 7705 SAR 8-port Voice & Teleprotection Card Installation Guide
• 7705 SAR Auxiliary Alarm Card Installation Guide
• 7705 SAR CWDM OADM Adapter Card/Module Installation Guide
Edition: 01 3HE 11011 AAAC TQZZA 15
Page 16
Preface
Interface Configuration Guide
• 7705 SAR DS3/E3 Adapter Card Installation Guide
• 7705 SAR DSL Module Installation Guide
• 7705 SAR Ethernet/Gigabit Ethernet Adapter Card Installation Guide
• 7705 SAR GNSS Receiver Card Installation Guide
• 7705 SAR GPON Module Installation Guide
• 7705 SAR GPS Receiver Module Installation Guide
• 7705 SAR Integrated Services Card Installation Guide
• 7705 SAR Packet Microwave Adapter Card Installation Guide
• 7705 SAR Power Injector Card Installation Guide
• 7705 SAR Serial Data Interface Card Installation Guide
• 7705 SAR SONET/SDH Adapter Card Installation Guide
• 7705 SAR T1/E1 ASAP Adapter Card Installation Guide
Note: This manual generically covers Release 8.0 content and may contain some content
that will be released in later maintenance loads. Please refer to the 7705 SAR OS 8.0.Rx
Software Release Notes, part number 3HE11057000xTQZZA, for information on features
supported in each load of the Release 8.0 software.
Note:
As of Release 7.0, support for the following hardware has been deprecated:
•CSMv1
•7705SAR-F
• 8-port Ethernet Adapter card, version 1
• 16-port T1/E1 ASAP Adapter card, version 1
These components are no longer recognized in the release.
16
3HE 11011 AAAC TQZZA Edition: 01
Page 17
Interface Configuration Guide Preface
1.1.1 Audience
This guide is intended for network administrators who are responsible for configuring
the 7705 SAR routers. It is assumed that the network administrators have an
understanding of networking principles and configurations. Concepts described in
this guide include the following:
• CLI concepts
• adapter card and port configuration
• QoS policies
• services
1.1.2 List of Technical Publications
The 7705 SAR documentation set is composed of the following guides:
• 7705 SAR Basic System Configuration Guide
This guide describes basic system configurations and operations.
• 7705 SAR System Management Guide
This guide describes system security and access configurations as well as event
logging and accounting logs.
• 7705 SAR Interface Configuration Guide
This guide describes card and port provisioning.
• 7705 SAR Router Configuration Guide
This guide describes logical IP routing interfaces, filtering, and routing policies.
• 7705 SAR MPLS Guide
This guide describes how to configure Multiprotocol Label Switching (MPLS),
Resource Reservation Protocol for Traffic Engineering (RSVP-TE), and Label
Distribution Protocol (LDP).
• 7705 SAR Services Guide
This guide describes how to configure service parameters such as service
access points (SAPs), service destination points (SDPs), customer information,
and user services.
• 7705 SAR Quality of Service Guide
This guide describes how to configure Quality of Service (QoS) policy
management.
Edition: 01 3HE 11011 AAAC TQZZA 17
Page 18
Preface
Interface Configuration Guide
• 7705 SAR Routing Protocols Guide
This guide provides an overview of dynamic routing concepts and describes how
to configure them.
• 7705 SAR OAM and Diagnostics Guide
This guide provides information on Operations, Administration and Maintenance
(OAM) tools.
1.1.3 Technical Support
If you purchased a service agreement for your 7705 SAR router and related products
from a distributor or authorized reseller, contact the technical support staff for that
distributor or reseller for assistance. If you purchased a Nokia service agreement,
follow this link to contact a Nokia support representative and to access product
manuals and documentation updates:
Product Support Portal
18
3HE 11011 AAAC TQZZA Edition: 01
Page 19
Interface Configuration Guide 7705 SAR Interface Configuration Process
2 7705 SAR Interface Configuration
Process
Table 1 lists the tasks that are required to provision CSM cards, adapter cards, ports,
and SCADA bridges.
This guide is presented in an overall logical configuration flow. Each section
describes a software area and provides CLI syntax and command usage to configure
parameters for a functional area.
Table 1 Configuration Process
Area Task/Description Chapter
Provisioning Configure chassis slots and cards Configuring the IOM and Card Slot
Configure adapter cards Configuring Adapter Cards and Modules
Configure ports and bridges Configuring Ports
Reference List of IEEE, IETF, and other
proprietary entities
Configuring SCADA Bridges
Standards and Protocol Support
Edition: 01 3HE 11011 AAAC TQZZA 19
Page 20
7705 SAR Interface Configuration Process
Interface Configuration Guide
20
3HE 11011 AAAC TQZZA Edition: 01
Page 21
Interface Configuration Guide 7705 SAR Interfaces
3 7705 SAR Interfaces
This chapter provides information about configuring chassis slots, cards, and ports.
Topics in this chapter include:
• Configuration Overview
• Port Features
• 802.1x Network Access Control
• MAC Authentication
• Link Layer Discovery Protocol (LLDP)
• Surveillance, Control, and Data Acquisition (SCADA) Support
• Configuration Notes
• Configuring Physical Components with CLI
• Configuration Command Reference
• Show, Monitor, Clear, and Debug Command Reference
Edition: 01 3HE 11011 AAAC TQZZA 21
Page 22
7705 SAR Interfaces
3.1 Configuration Overview
Interface Configuration Guide
This guide uses the term “preprovisioning” in the context of preparing or
preconfiguring entities such as chassis slots, the IOM, adapter cards, ports, and
interfaces, prior to hardware actually being installed in the chassis. These entities
can be installed but not enabled. When the entity is in a no shutdown state
(administratively enabled), the entity is considered to be provisioned.
Nokia 7705 SAR routers provide the capability to configure chassis slots to accept
specific adapter card types and set the relevant configurations before the equipment
is actually installed. The preprovisioning ability allows you to plan your configurations
as well as monitor and manage your router hardware inventory. Ports and interfaces
can also be preprovisioned. When the functionality is needed, the cards can be
inserted into the appropriate chassis slots as required.
The following sections are discussed:
• Configuring the IOM and Card Slot
• Configuring Adapter Cards and Modules
• Configuring Ports
• Configuring SCADA Bridges
3.1.1 Configuring the IOM and Card Slot
The 7705 SAR card slot ID is always 1 and the card type for the IOM is always
iom-sar.
On the 7705 SAR-8 and 7705 SAR-18, the CSM, which can only be installed in slot
A or B of the chassis, does not need to be provisioned. However, the IOM, which is
virtualized in the 7705 SAR software, must be activated before the adapter cards,
ports, and SCADA bridges can be preprovisioned and configured. The IOM is
activated by designating it a card slot ID and card type. This enables the chassis slots
to accept the adapter cards.
Note: On the 7705 SAR-8, the CSM is called the CSMv2; both terms are used
interchangeably in these guides. The CSMv2 supports bandwidth of 10 Gb/s, 2.5 Gb/s and
1 Gb/s in the first two adapter card slots and 2.5 Gb/s and 1 Gb/s in the remaining four
adapter card slots. Support for 2.5 Gb/s and 10 Gb/s adapter cards by the CSMv2 is only
available on the 7705 SAR-8 Shelf V2.
22
3HE 11011 AAAC TQZZA Edition: 01
Page 23
Interface Configuration Guide 7705 SAR Interfaces
The 7705 SAR-M (all variants), 7705 SAR-H, 7705 SAR-Hc, 7705 SAR-A (both
variants), 7705 SAR-Ax, 7705 SAR-W, 7705 SAR-Wx (all variants), and
7705 SAR-X have a fixed physical configuration and each router uses only one
control and switching functional block, which is referred to on the CLI as CSM A. The
CSM and IOM do not need to be provisioned in order to provision the interface at the
adapter card level.
The slot ID (1) is used as part of the adapter card and port identifier on the CLI.
3.1.2 Configuring Adapter Cards and Modules
This section contains information on the following topics:
• Provisioning Chassis Slots for Adapter Cards
• Maximum Number of Adapter Cards in a Chassis
• Evolution of Ethernet Adapter Cards, Modules, and Platforms
• Channelized Adapter Card Support
3.1.2.1 Provisioning Chassis Slots for Adapter Cards
A chassis slot and card type must be specified and provisioned before an adapter
card can be provisioned. A chassis slot is a physical slot designated with an MDA ID.
On the 7705 SAR-8, the MDA ID is from 1 to 6. On the 7705 SAR-18, the MDA ID is
from 1 to 12 for the MDA slots and from X1 to X4 for the XMDA slots. An adapter card
is provisioned when a card designated from the allowed adapter card types is
inserted. A preprovisioned adapter card slot can remain empty without conflicting
with populated slots.
The adapter cards can be installed in the chassis in any combination that does not
exceed the maximum number. However, network applications require at least one
network-capable adapter card to be installed as part of the mix.
Once installed and enabled, the system verifies that the installed adapter card type
matches the configured parameters. If the parameters do not match, the adapter
card remains offline.
Edition: 01 3HE 11011 AAAC TQZZA 23
Page 24
7705 SAR Interfaces
3.1.2.2 Maximum Number of Adapter Cards in a Chassis
Interface Configuration Guide
Note: Unless otherwise specified, references to adapter cards with multiple versions
include all versions of the cards.
A maximum of six adapter cards can be installed in the 7705 SAR-8 chassis. The
following adapter cards are supported:
• 2-port 10GigE (Ethernet) Adapter card (maximum of 4 in a 7705 SAR-8 with
CSMv2)
• 2-port OC3/STM1 Channelized Adapter card (maximum of 6, depending on
channelization and CSM variant installed – see note below)
• 4-port OC3/STM1 / 1-port OC12/STM4 Adapter card (maximum of 4 in a
7705 SAR-8 with CSMv2)
• 4-port OC3/STM1 Clear Channel Adapter card (maximum of 6)
• 4-port DS3/E3 Adapter card (maximum of 6, depending on channelization and
CSM variant installed – see note below)
• 6-port E&M Adapter card (maximum of 6)
• 6-port FXS Adapter card (maximum of 6)
• 6-port Ethernet 10Gbps Adapter card (maximum of 6 in a 7705 SAR-8 Shelf V2
with CSMv2 only)
• 8-port Ethernet Adapter card (maximum of 6)
• 8-port FXO Adapter card (maximum of 6)
• 8-port Gigabit Ethernet Adapter card (maximum of 6)
• 8-port Voice & Teleprotection card (maximum of 6)
• 12-port Serial Data Interface card (maximum of 6)
• 16-port T1/E1 ASAP Adapter card (maximum of 6)
• 32-port T1/E1 ASAP Adapter card (maximum of 6)
• Auxiliary Alarm card (maximum of 6)
• CWDM OADM Adapter card (maximum of 6)
• Integrated Services card (maximum of 6)
• Packet Microwave Adapter card (maximum of 6)
• Power Injector card (maximum of 4)
24
3HE 11011 AAAC TQZZA Edition: 01
Page 25
Interface Configuration Guide 7705 SAR Interfaces
A maximum of 12 MDA adapter cards and 4 XMDA adapter cards can be installed in
the 7705 SAR-18 chassis. The following adapter cards are supported:
• 2-port 10GigE (Ethernet) Adapter card (maximum of 6)
• 2-port OC3/STM1 Channelized Adapter card (maximum of 12, depending on
channelization – see note below)
• 4-port OC3/STM1 / 1-port OC12/STM4 Adapter card (maximum of 6, depending
on channelization – see note below)
• 4-port OC3/STM1 Clear Channel Adapter card (maximum of 12)
• 4-port DS3/E3 Adapter card (maximum of 12, depending on channelization –
see note below)
• 6-port E&M Adapter card (maximum of 12)
• 6-port FXS Adapter card (maximum of 12)
• 6-port Ethernet 10Gbps Adapter card (maximum of 12)
• 8-port Ethernet Adapter card, version 2 (maximum of 12)
• 8-port FXO Adapter card (maximum of 12)
• 8-port Gigabit Ethernet Adapter card (maximum of 12)
• 8-port Voice & Teleprotection card (maximum of 12)
• 10-port 1GigE/1-port 10GigE X-Adapter card (maximum of 4)
• 12-port Serial Data Interface card (maximum of 12)
• 16-port T1/E1 ASAP Adapter card, version 2 (maximum of 12)
• 32-port T1/E1 ASAP Adapter card (maximum of 12)
• Auxiliary Alarm card (maximum of 12)
• CWDM OADM Adapter card (maximum of 12)
• Integrated Services card (maximum of 12)
• Packet Microwave Adapter card (maximum of 12)
• Power Injector card (maximum of 8)
Edition: 01 3HE 11011 AAAC TQZZA 25
Page 26
7705 SAR Interfaces
Interface Configuration Guide
Note:
• On a 7705 SAR-8 chassis with a CSMv2:
− a maximum of six 2-port OC3/STM1 Channelized Adapter cards can be installed
in MDA slots 1 to 6 if DS3 channelization is being used. If DS1/E1 or DS0 (64 kb/s)
channelization is being used, a maximum of four 2-port OC3/STM1 Channelized
Adapter cards can be installed in MDA slots 1 to 6.
− a maximum of six 4-port DS3/E3 Adapter cards can be installed in MDA slots 1 to
6 if DS3/E3 or DS1/E1 channelization is being used. If DS0 (64 kb/s)
channelization is being used, a maximum of four 4-port DS3/E3 Adapter cards can
be installed in MDA slots 1 to 6.
− a maximum of four 4-port OC3/STM1 / 1-port OC12/STM4 Adapter cards can be
installed in MDA slots 1 to 6 if DS1/E1 channelization is being used. DS0 and
DS3/E3 channelization is not supported on the 4-port OC3/STM1 / 1-port
OC12/STM4 Adapter card.
− a maximum of six 6-port Ethernet 10Gbps Adapter cards can be installed in MDA
slots 1 to 6. When installed in MDA slot 1 or 2, the 6-port Ethernet 10Gbps Adapter
card supports a 10-Gb/s fabric rate. When installed in MDA slots 3 through 6, the
aggregate fabric rate is 2.5 Gb/s.
• On a 7705 SAR-18 chassis:
− a maximum of twelve 2-port OC3/STM1 Channelized Adapter cards can be
installed in MDA slots 1 to 12 if DS3 channelization is being used. If DS1/E1 or
DS0 (64 kb/s) channelization is being used, a maximum of four 2-port OC3/STM1
Channelized Adapter cards can be installed in MDA slots 1 to 12.
− a maximum of twelve 4-port DS3/E3 Adapter cards can be installed in MDA slots
1 to 12 if DS3/E3 or DS1/E1 channelization is being used. If DS0 (64 kb/s)
channelization is being used, a maximum of four 4-port DS3/E3 Adapter cards can
be installed in MDA slots 1 to 12.
− a maximum of six 4-port OC3/STM1 / 1-port OC12/STM4 Adapter cards can be
installed in MDA slots 1 to 12 if DS1/E1 channelization is being used. DS0 and
DS3/E3 channelization is not supported on the 4-port OC3/STM1 / 1-port
OC12/STM4 Adapter card.
• The total number of channel groups that can be configured per card and per node is
bound by release-specific system limits. For more information, please contact your
Nokia technical support representative.
26
Note: Because the 6-port E&M Adapter card, 12-port Serial Data Interface card, 8-port
Voice & Teleprotection card, 8-port FXO Adapter card, and 6-port FXS Adapter card support
access mode only, and the Integrated Services card is a resource card that supports an
access functionality only, for network applications, the maximum number of each of these
adapter cards that can be installed in a 7705 SAR-8 chassis is 5, and the maximum number
that can be installed in a 7705 SAR-18 chassis is 11.
3HE 11011 AAAC TQZZA Edition: 01
Page 27
Interface Configuration Guide 7705 SAR Interfaces
3.1.2.3 Evolution of Ethernet Adapter Cards, Modules, and Platforms
The 7705 SAR hardware components have improved as technology has developed.
Table 2 lists the Ethernet adapter cards, modules, and platforms according to their
generation. Second-generation (Gen-2) components have additional features,
increased card memory and/or improved QoS mechanisms over first-generation
(Gen-1) components. Similarly, third-generation (Gen-3) components improve upon
second-generation components.
Table 2 Ethernet Adapter Card, Module, and Platform Generations
Generation Card, Module, and Platform
First Generation 8-port Ethernet Adapter card
Second Generation 2-port 10GigE (Ethernet) Adapter card (v-port)
2-port 10GigE (Ethernet) module (v-port) (for 7705 SAR-M)
8-port Gigabit Ethernet Adapter card
10-port 1GigE/1-port 10GigE X-Adapter card
Packet Microwave Adapter card
7705 SAR-A
7705 SAR-Ax
7705 SAR-H
7705 SAR-Hc
7705 SAR-M
7705 SAR-W
7705 SAR-Wx
4-port SAR-H Fast Ethernet module
6-port SAR-M Ethernet module
Edition: 01 3HE 11011 AAAC TQZZA 27
Page 28
7705 SAR Interfaces
3.1.2.4 Channelized Adapter Card Support
Interface Configuration Guide
Table 2 Ethernet Adapter Card, Module, and Platform Generations
Generation Card, Module, and Platform
Third Generation 6-port Ethernet 10Gbps Adapter card
7705 SAR-X
The following cards and modules support channelization down to the DS0 level:
• 16-port T1/E1 ASAP Adapter card
• 32-port T1/E1 ASAP Adapter card
• 12-port Serial Data Interface card
• 6-port E&M Adapter card
• 2-port OC3/STM1 Channelized Adapter card
• 4-port DS3/E3 Adapter card
• 8-port Voice & Teleprotection card
• 8-port FXO Adapter card
• 6-port FXS Adapter card
• 4-port T1/E1 and RS-232 Combination module
On the 16-port T1/E1 ASAP Adapter card, 32-port T1/E1 ASAP Adapter card,
2-port OC3/STM1 Channelized Adapter card, and 4-port DS3/E3 Adapter card (DS3
ports only), and on the T1/E1 ports of the 4-port T1/E1 and RS-232 Combination
module, up to 24 channel groups are supported on a DS1 circuit and up to 32 channel
groups on an E1 circuit.
The 12-port Serial Data Interface card supports a single channel group on a
channelized V.35 circuit, RS-232 (also known as EIA/TIA-232) circuit, or X.21 circuit.
The RS-232 ports on the 4-port T1/E1 and RS-232 Combination module also support
a single channel group on a channelized RS-232 circuit.
The 6-port E&M Adapter card supports a single channel group on a channelized
E&M voice interface.
The 8-port Voice & Teleprotection card supports a single channel group on a
channelized G.703 (codirectional) circuit, an IEEE C37.94 teleprotection interface
(TPIF) circuit, FXS circuit, or FXO circuit.
28
The 8-port FXO Adapter card supports a single channel group on an FXO circuit.
3HE 11011 AAAC TQZZA Edition: 01
Page 29
Interface Configuration Guide 7705 SAR Interfaces
The 6-port FXS Adapter card supports a single channel group on an FXS circuit.
The 4-port OC3/STM1 / 1-port OC12/STM4 Adapter card supports channelization at
the DS1/E1 level only.
3.1.2.4.1 PPP Over Fractional T1/E1
The 16-port T1/E1 ASAP Adapter card, 32-port T1/E1 ASAP Adapter card, and the
T1/E1 ports on the 4-port T1/E1 and RS-232 Combination module each support
fractional T1/E1 on a PPP channel group in network mode. Fractional T1/E1 allows
one or more DS0 channels to be bundled together (up to the maximum bandwidth of
the network link), allowing the customer to use only that portion of the link that is
needed. This means that the PPP service can use a selected number of timeslots
(octets) in the network T1 or E1 link, thus reducing the amount of T1 or E1 bandwidth
that must be leased or purchased from the attached carrier. This leads to
multiplexing efficiencies in the transport network.
Only one channel group can be configured per port. When the channel group is
configured for ppp-auto encapsulation and network mode, all timeslots (channels)
are automatically allocated to the channel group. The user can then configure the
number of timeslots needed. Timeslots not selected cannot be used.
3.1.3 Configuring Ports
A port can be configured after the IOM is activated (the card slot and card type are
designated) and the adapter card slot is preprovisioned with an allowed adapter card
type.
The 7705 SAR supports the port types listed below:
• Ethernet
• TDM
• DSL
• GNSS Receiver
• GPON
• Multilink Bundles
• IMA
• SONET/SDH
• Voice
Edition: 01 3HE 11011 AAAC TQZZA 29
Page 30
7705 SAR Interfaces
3.1.3.1 Ethernet
Interface Configuration Guide
• Microwave Link
In addition, this section contains information on the following topics:
• CLI Identifiers for Adapter Cards, Modules and Platforms
• Access, Network, and Hybrid Ports
Ethernet ports are supported on the following cards, modules, and platforms:
• 6-port Ethernet 10Gbps Adapter Card
• 8-port Ethernet Adapter Card
• 8-port Gigabit Ethernet Adapter Card
• 10-port 1GigE/1-port 10GigE X-Adapter Card
• 2-port 10GigE (Ethernet) Adapter Card/Module
• Packet Microwave Adapter Card
• 4-port SAR-H Fast Ethernet Module
• 6-port SAR-M Ethernet Module
• 7705 SAR-A
• 7705 SAR-Ax
• 7705 SAR-H
• 7705 SAR-Hc
• 7705 SAR-M
• 7705 SAR-W
• 7705 SAR-Wx
• 7705 SAR-X
3.1.3.1.1 6-port Ethernet 10Gbps Adapter Card
The 6-port Ethernet 10Gbps Adapter card has four SFP ports for 1-Gb/s fiber or
copper SFP transceivers and two SFP+ ports for 10-Gb/s fiber or copper SFP+
transceivers. The card also supports synchronous Ethernet timing. The 6-port
Ethernet 10Gbps Adapter card is designed to complement or replace the 8-port
Ethernet Adapter card or the 8-port Gigabit Ethernet Adapter card in situations where
greater processing power and higher throughput capacity are required.
30
3HE 11011 AAAC TQZZA Edition: 01
Page 31
Interface Configuration Guide 7705 SAR Interfaces
The ports and features on the 6-port Ethernet 10Gbps Adapter card are identical to
the ports and features on the 8-port Gigabit Ethernet Adapter card, version 3, except
that the 6-port Ethernet 10Gbps Adapter card uses only 4-priority schedulers for QoS
instead of 4-priority or 16-priority schedulers.
3.1.3.1.2 8-port Ethernet Adapter Card
The 8-port Ethernet Adapter card (the 7705 SAR-18 only supports version 2) has six
RJ-45 ports for 10/100Base-T (Ethernet and Fast Ethernet) connections. The card
also has two SFP ports for fiber or copper SFPs. Fast Ethernet and Gigabit (100 Mb/s
and 1000 Mb/s) fiber connections and 10/100/1000Base-T copper connections are
supported. This variety of connections enables the 8-port Ethernet Adapter card to
be connected to different devices at the customer site, including wireless base
stations, DSL modems, microwave boxes, and other auxiliary equipment. As well,
with fiber connections, the adapter card can be directly connected to the Metro
Ethernet Provider (MEP) central office. Version 2 of the 8-port Ethernet Adapter card
also supports synchronous Ethernet timing.
3.1.3.1.3 8-port Gigabit Ethernet Adapter Card
The 8-port Gigabit Ethernet Adapter card has eight SFP ports for fiber or copper
SFPs. The card supports dual rate (100 Mb/s and 1000 Mb/s) and Gigabit (1000
Mb/s) fiber connections and 10/100/1000Base-T copper connections. The card also
supports synchronous Ethernet timing. The 8-port Gigabit Ethernet Adapter card is
designed to complement or replace the 8-port Ethernet Adapter card in situations
where greater processing power and higher throughput capacity are required.
There are three versions of the 8-port Gigabit Ethernet Adapter card. Version 1 and
version 2 are identical except that version 2 provides larger table space for FIBs,
ACLs, and so on. Version 2 also supports the full IPv6 subnet range for IPv6 static
routes and interface IP addresses. The static route range is from /1 to /128, and the
default route is ::/0. Supported interface IP address prefixes are from /4 to /127, and
/128 on system or loopback interfaces. Version 3 is identical to version 2 except that
it is equipped with a hardware-based encryption engine to support features such as
IPSec.
Higher limits and full subnet ranges are supported only when all the adapter cards in
a particular node are equipped with hardware for larger table support.
Edition: 01 3HE 11011 AAAC TQZZA 31
Page 32
7705 SAR Interfaces
3.1.3.1.4 10-port 1GigE/1-port 10GigE X-Adapter Card
Interface Configuration Guide
Gigabit Ethernet optical ports offer significant advantages over fast Ethernet ports,
even where lower-speed services are currently offered. With Gigabit Ethernet,
service providers have the opportunity to standardize access infrastructure, ensure
that capacity is available to accommodate growing bandwidth requirements, and
minimize the operational costs associated with future service upgrades to hardware
and software.
There are two versions of the 10-port 1GigE/1-port 10GigE X-Adapter card. Both
versions are identical except that version 2 is equipped with a hardware-based
encryption engine to support features such as IPSec.
When the 10-port 1GigE/1-port 10GigE X-Adapter card (supported only on the
7705 SAR-18) is configured in 10-port GigE mode, 10 SFP ports are available for
fiber SFP transceivers. In this mode, the card supports dual-rate (100 Mb/s and
1000 Mb/s) and Gigabit (1000 Mb/s) fiber connections. The card also supports
synchronous Ethernet timing.
When the 10-port 1GigE/1-port 10GigE X-Adapter card is configured in 1-port GigE
mode, only one SFP+ (port 1) of the 10 ports is active and available for use with fiber
SFP+ transceivers. The card supports 10-Gb/s fiber connections. The card also
supports synchronous Ethernet timing. The 1-port GigE mode is designed for use in
situations where greater processing power and higher throughput capacity are
required.
The 10-port 1GigE/1-port 10GigE X-Adapter card also provides larger table space for
FIBs, ACLs, and so on. The card also supports the full IPv6 subnet range for IPv6
static routes and interface IP addresses. The static route range is from /1 to /128, and
the default route is ::/0. Supported interface IP address prefixes are from /4 to /127,
and /128 on system or loopback interfaces.
Higher limits and full subnet ranges are supported only when all the adapter cards in
a particular node are equipped with hardware for larger table support.
32
3HE 11011 AAAC TQZZA Edition: 01
Page 33
Interface Configuration Guide 7705 SAR Interfaces
3.1.3.1.5 2-port 10GigE (Ethernet) Adapter Card/Module
The 2-port 10GigE (Ethernet) Adapter card/module is used to connect to and from
access rings carrying a high concentration of traffic. Table 3 lists the maximum
number of cards or modules that are supported on each platform. A single card can
be installed in the 7705 SAR-8 and the 7705 SAR-18; however, it is strongly
recommended that a minimum of two cards be installed for redundancy.
Table 3 Maximum Number of Cards/Modules Supported in Each
Chassis
Chassis Maximum Number of Cards or Modules
7705 SAR-8 with CSMv2 Up to four cards
7705 SAR-18 Up to six cards
7705 SAR-M One module
The 2-port 10GigE (Ethernet) Adapter card/module has two small form-factor
pluggable (XFP) ports on its faceplate. The two XFP ports are for 10-Gigabit Ethernet
XFPs. The card provides high processing power and throughput capacity and
operates at 10 Gb/s for Ethernet ports and 2.5 Gb/s for the virtual port (v-port).
The 2-port 10GigE (Ethernet) Adapter card provides larger table space for FIBs,
ACLs, and so on. The card also supports the full IPv6 subnet range for IPv6 static
routes and interface IP addresses on the v-port. The supported range for statically
provisioned or dynamically learned routes is from /1 to /128. Supported interface IP
address prefixes are from /4 to /127, and /128 on system or loopback interfaces.
The 2-port 10GigE (Ethernet) module supports IPv6 on the v-port. The supported
range for statically provisioned or dynamically learned routes is from /1 to /64 or is
/128 (indicating a host route). Supported interface IP address prefixes are from /4 to
/64, and /128 on system or loopback interfaces.
The 2-port 10GigE (Ethernet) Adapter card/module supports LLDP on the Ethernet
ports but not on the v-port.
3.1.3.1.6 Packet Microwave Adapter Card
The Packet Microwave Adapter card has two RJ-45 ports (ports 1 and 2) and six SFP
ports (ports 3 through 8). All ports provide 10/100/1000 Mb/s connections (when
connected to an MPR-e radio, they are always in Gigabit Ethernet (1-Gb/s) mode).
Ports 1 through 4 support Microwave Awareness (MWA) and Ethernet/IP/MPLS
networking; ports 5 through 8 support Ethernet/IP/MPLS networking only.
Edition: 01 3HE 11011 AAAC TQZZA 33
Page 34
7705 SAR Interfaces
3.1.3.1.7 4-port SAR-H Fast Ethernet Module
3.1.3.1.8 6-port SAR-M Ethernet Module
Interface Configuration Guide
All Gigabit Ethernet ports provide the same networking feature capability as the
8-port Gigabit Ethernet Adapter card. For frequency synchronization, synchronous
Ethernet and SSM are the mechanisms that are applied when using optical
1000Base-SX to connect to an MPR-e radio. When using electrical 1000Base-T to
connect the Packet Microwave Adapter card and an MPR-e radio, Proprietary Clock
Recovery (PCR) is used (a copper SFP is mandatory on ports 3 and 4).
The 4-port SAR-H Fast Ethernet module has four RJ-45 Fast Ethernet ports
(10/100 Mb/s) on its faceplate. Any functionality supported on the 7705 SAR-H
Ethernet ports is also supported on the 4-port SAR-H Fast Ethernet module, with the
exception of hierarchical QoS (H-QoS) functionality and hybrid mode.
The 6-port SAR-M Ethernet module has six Ethernet ports:
• two SFP Fast Ethernet ports (10/100 Mb/s) (ports 1 and 2)
• two XOR (combination) SFP/RJ point five Gigabit Ethernet ports
(10/100/1000 Mb/s) (ports 3a/3b and 4a/4b)
• two PoE-capable RJ point five copper Gigabit Ethernet ports
(10/100/1000 Mb/s) (ports 5 and 6)
Ports 5 and 6 can each support Power over Ethernet (PoE). Port 5 can also support
PoE+, but if it is configured for PoE+, then port 6 cannot support PoE power.
Any functionality supported on the 7705 SAR-M Ethernet ports is also supported on
the 6-port SAR-M Ethernet module, with the exception of half-duplex mode (all ports)
and hybrid mode (Fast Ethernet ports only).
3.1.3.1.9 7705 SAR-A
The 7705 SAR-A has two variants with fixed physical configurations. One variant
supports both Ethernet and T1/E1 ports. The other variant supports only Ethernet
ports. Both variants of the 7705 SAR-A have 12 Ethernet ports:
34
• four XOR (combination) Gigabit Ethernet ports, either 10/100/1000Base-T
RJ-45 (ports 1A to 4A) or 100/1000 Mb/s SFP (ports 1B to 4B)
• four SFP Gigabit Ethernet ports (100/1000 Mb/s) (ports 5 to 8)
3HE 11011 AAAC TQZZA Edition: 01
Page 35
Interface Configuration Guide 7705 SAR Interfaces
• four RJ-45 Fast Ethernet ports (10/100 Mb/s) (ports 9 to 12)
3.1.3.1.10 7705 SAR-Ax
The 7705 SAR-Ax has a fixed physical configuration that has 12 Ethernet ports:
• four XOR (combination) Gigabit Ethernet ports, either 10/100/1000Base-T
RJ-45 (ports 1A to 4A) or 100/1000 Mb/s SFP (ports 1B to 4B)
• eight SFP Gigabit Ethernet ports (100/1000 Mb/s) (ports 5 to 12)
3.1.3.1.11 7705 SAR-H
The 7705 SAR-H has a fixed physical configuration that has eight Ethernet ports:
• two SFP Gigabit Ethernet ports (10/100/1000 Mb/s) (ports 1 and 2)
• two XOR (combination) RJ-45/SFP Gigabit Ethernet ports (10/100/1000 Mb/s)
(ports 3 and 4)
• four PoE-capable RJ-45 Gigabit Ethernet ports (10/100/1000 Mb/s) (ports 5 to 8)
The 7705 SAR-H also has two module slots.
If a PoE Power Supply is connected, it increases the number of Ethernet ports that
can supply PoE to a connected device.
3.1.3.1.12 7705 SAR-Hc
The 7705 SAR-Hc has a fixed physical configuration that has six Ethernet ports:
• two SFP Gigabit Ethernet ports (10/100/1000 Mb/s) (ports 1 and 2)
• two Gigabit Ethernet RJ-45 ports (10/100/1000 Mb/s) (ports 3 and 4)
• two PoE-capable RJ-45 Gigabit Ethernet ports (10/100/1000 Mb/s) (ports 5 and
6)
Edition: 01 3HE 11011 AAAC TQZZA 35
Page 36
7705 SAR Interfaces
3.1.3.1.13 7705 SAR-M
3.1.3.1.14 7705 SAR-W
Interface Configuration Guide
The 7705 SAR-M has a fixed physical configuration that has four variants. All
variants of the 7705 SAR-M have seven Ethernet ports:
• four SFP Gigabit Ethernet ports (10/100/1000 Mb/s) (ports 1 to 4)
• three Gigabit Ethernet RJ-45 ports (10/100/1000 Mb/s) (ports 5 to 7)
Two variants of the 7705 SAR-M also have a module slot.
The 7705 SAR-W has a fixed physical configuration that has five Ethernet ports:
• three SFP Gigabit Ethernet ports (10/100/1000 Mb/s) (ports 1 to 3)
• two PoE+ capable Gigabit Ethernet RJ-45 ports (10/100/1000 Mb/s) (ports 4 and
5)
3.1.3.1.15 7705 SAR-Wx
The 7705 SAR-Wx has six variants with fixed physical configurations that provide the
following Ethernet interfaces.
Two variants have five Gigabit Ethernet ports:
• three SFP Gigabit Ethernet ports (10/100/1000 Mb/s) (ports 1 to 3)
• two Gigabit Ethernet RJ-45 ports (10/100/1000 Mb/s) (ports 4 and 5)
Two variants have five Gigabit Ethernet ports:
• three SFP Gigabit Ethernet ports (10/100/1000 Mb/s) (ports 1 to 3)
• one Gigabit Ethernet RJ-45 port (10/100/1000 Mb/s) (port 4)
• one PoE+ Gigabit Ethernet RJ-45 port (10/100/1000 Mb/s) (port 5)
Two variants have four Gigabit Ethernet ports:
• three SFP Gigabit Ethernet ports (10/100/1000 Mb/s) (ports 1 to 3)
• one Gigabit Ethernet RJ-45 port (10/100/1000 Mb/s) (port 4)
36
3HE 11011 AAAC TQZZA Edition: 01
Page 37
Interface Configuration Guide 7705 SAR Interfaces
3.1.3.1.16 7705 SAR-X
The 7705 SAR-X has a fixed physical configuration that has 14 Ethernet ports:
• four XOR (combination) RJ-45/SFP Gigabit Ethernet ports (10/100/1000 Mb/s)
(ports 2/1A, 2/2A, 3/1A, 3/2A for RJ-45 and 2/1B, 2/2B, 3/1B, 3/2B for SFP)
• eight SFP Gigabit Ethernet ports (10/100/1000 Mb/s) (ports 2/3 to 2/6 and 3/3 to
3/6)
• two SFP+ 10-Gigabit Ethernet ports (ports 2/7 and 3/7)
3.1.3.2 TDM
TDM ports are supported on the following cards, modules, and platforms:
• 16-port T1/E1 ASAP Adapter Card
• 32-port T1/E1 ASAP Adapter Card
• 2-port OC3/STM1 Channelized Adapter Card
• 4-port OC3/STM1 / 1-port OC12/STM4 Adapter Card
• 4-port DS3/E3 Adapter Card
• 8-port Voice & Teleprotection Card
• 12-port Serial Data Interface Card
• 4-port T1/E1 and RS-232 Combination Module
• 7705 SAR-A
• 7705 SAR-Hc
• 7705 SAR-M
• 7705 SAR-X
3.1.3.2.1 16-port T1/E1 ASAP Adapter Card
There are two versions of the 16-port T1/E1 ASAP Adapter card. The 7705 SAR-18
only supports version 2.
Channelization is supported down to the DS0 level. To change port types, all ports
must first be shut down. The ports can be configured for DS1 (T1) or E1 operation.
All ports on the card must be either T1 or E1; there cannot be a mix of the two types.
When the first port is configured on a card, all other ports on the card must be set to
the same type.
Edition: 01 3HE 11011 AAAC TQZZA 37
Page 38
7705 SAR Interfaces
3.1.3.2.2 32-port T1/E1 ASAP Adapter Card
Interface Configuration Guide
The 16-port T1/E1 ASAP Adapter card supports fractional T1/E1 on network ports
configured for PPP. Fractional T1/E1 allows a portion of the link to be used for traffic
(up to the full link bandwidth).
DS1 ports on the 16-port T1/E1 ASAP Adapter card, version 2, can be configured for
either B8ZS (bipolar with eight-zero substitution) zero code suppression or AMI
(alternate mark inversion). B8ZS and AMI are line coding techniques.
On the 32-port T1/E1 ASAP Adapter card, channelization is supported down to the
DS0 level. To change port types, all ports must first be shut down. The ports can be
configured for DS1 (T1) or E1 operation. All ports on the card must be either T1 or
E1; there cannot be a mix of the two types. When the first port is configured on a card,
all other ports on the card must be set to the same type.
The 32-port T1/E1 ASAP Adapter card supports fractional T1/E1 on network ports
configured for PPP. Fractional T1/E1 allows a portion of the link to be used for traffic
(up to the full link bandwidth).
DS1 ports on the card can be configured for either B8ZS (bipolar with eight-zero
substitution) zero code suppression or AMI (alternate mark inversion). B8ZS and AMI
are line coding techniques.
3.1.3.2.3 2-port OC3/STM1 Channelized Adapter Card
On the 2-port OC3/STM1 Channelized Adapter card, channelization is supported
down to the DS0 level. To change port types, all ports must first be shut down. The
ports can be configured for DS1 (T1) or E1 channelization. All ports on the card must
be either SONET or SDH; there cannot be a mix of the two types. When the first port
is configured on a card, all other ports on the card must be set to the same type.
The 2-port OC3/STM1 Channelized Adapter card also supports DS3 channelization.
3.1.3.2.4 4-port OC3/STM1 / 1-port OC12/STM4 Adapter Card
The 4-port OC3/STM1 / 1-port OC12/STM4 Adapter card can be configured to be in
4-port OC3/STM1 mode or 1-port OC12/STM4 mode (using the mda-mode
command).
38
3HE 11011 AAAC TQZZA Edition: 01
Page 39
Interface Configuration Guide 7705 SAR Interfaces
When the 4-port OC3/STM1 / 1-port OC12/STM4 Adapter card is configured in 4-port
OC3/STM1 mode, four SFP ports are available for optical and electrical SFP
transceivers. In this mode, the card supports OC3 SONET or STM1 SDH
transmission.
When the 4-port OC3/STM1 / 1-port OC12/STM4 Adapter card is configured in 4-port
OC3/STM1 mode, channelization is supported down to the DS1 level. To change
port types, all ports must first be shut down. The ports can be configured for DS1 (T1)
or E1 channelization in access mode, or PPP/MLPPP or POS in network mode. All
ports on the card must be either SONET or SDH; there cannot be a mix of the two
types. When the first port is configured on a card, all other ports on the card must be
set to the same type. Switching between port types causes the adapter card to reset.
When the 4-port OC3/STM1 / 1-port OC12/STM4 Adapter card is configured in 1-port
OC12/STM4 mode, SFP port 1 is available for optical SFP transceivers. Ports 2
through 4 are not available. In this mode, the card supports OC12 SONET and STM4
SDH transmission. The 1-port OC12/STM4 mode is designed for use in situations
where greater bandwidth is required on a single port.
3.1.3.2.5 4-port DS3/E3 Adapter Card
The 4-port DS3/E3 Adapter card has four TDM DS3/E3 ports. The port type must be
configured to be either DS3 or E3. Each DS3 port can be clear channel or
channelized down to DS0 (64 kb/s). E3 ports can be clear channel only. Once the
first port type has been configured, all other ports on the same 4-port DS3/E3
Adapter card must be set to the same type.
To change between types, the ports must first be deleted. DS3 ports provide B3ZS
(bipolar with three-zero substitution) zero code suppression and E3 ports provide
HDB3 (high density bipolar of order 3) zero code suppression. B3ZS and HDB3 zero
code suppression are line coding techniques.
Channelization is supported down to the DS0 level (for DS3 ports only). To change
port types, all ports must first be shut down. The ports can be configured for DS1 (T1)
or E1 operation. All ports on the card must be either T1 or E1; there cannot be a mix
of the two types. When the first port is configured on a card, all other ports on the
card must be set to the same type.
Edition: 01 3HE 11011 AAAC TQZZA 39
Page 40
7705 SAR Interfaces
3.1.3.2.6 8-port Voice & Teleprotection Card
3.1.3.2.7 12-port Serial Data Interface Card
Interface Configuration Guide
On the 8-port Voice & Teleprotection card, channelization is supported down to the
DS0 level. To change port types, all ports must first be shut down. The ports can be
configured for DS1 (T1) or E1 operation. All ports on the card must be either T1 or
E1; there cannot be a mix of the two types. When the first port is configured on a card,
all other ports on the card must be set to the same type.
Channelization is supported on the two codirectional G.703 ports and two IEEE
C37.94 teleprotection interface ports.
The 12-port Serial Data Interface card has four connectors, which support three
serial data ports each. Each port grouping may be configured for V.35, RS-232, or
X.21 operation. When a port has been configured for a specific interface type, the
other two ports in that same grouping can only be configured for the same type.
The card also supports an RS-530 interface with the use of an adapter cable that
connects to a DB15 connector on the front of the X.21 distribution panel. There is no
configuration specifically for the RS-530 interface; configuration is done in X.21
mode and applies to the RS-530 interface when it is physically enabled through
hardware.
All X.21 functionality is available on the RS-530 interface, except that only DCE
operation is supported for RS-530. However, because X.21 does not support all the
control leads available for RS-530, only a subset of the RS-530 control leads are
supported.
Channelization on the 12-port Serial Data Interface card is supported down to the
DS0 level.
3.1.3.2.8 4-port T1/E1 and RS-232 Combination Module
T1/E1 ports on the 4-port T1/E1 and RS-232 Combination module (supported on the
7705 SAR-H) support channelization down to the DS0 level. To change port types,
all ports must first be shut down. The ports can be configured for DS1 (T1) or E1
operation. All ports on the module must be either T1 or E1; there cannot be a mix of
the two types. When the first port is configured on a module, all other ports on the
card must be set to the same type.
40
3HE 11011 AAAC TQZZA Edition: 01
Page 41
Interface Configuration Guide 7705 SAR Interfaces
3.1.3.2.9 7705 SAR-A
The 7705 SAR-A has two variants with fixed physical configurations. One variant
supports both Ethernet and T1/E1 ports. The other variant supports only Ethernet
ports. The variant that supports T1/E1 ports includes eight RJ-45 T1/E1 ports. All
ports must be configured as either T1 or E1 ports; a mix of T1 and E1 ports is not
allowed.
DS1 (T1) ports on the chassis can be configured for either B8ZS (bipolar with
eight-zero substitution) zero code suppression or AMI (alternate mark inversion).
B8ZS and AMI are line coding techniques.
3.1.3.2.10 7705 SAR-Hc
The 7705 SAR-Hc has a fixed physical configuration that includes two RS-232 RJ-45
ports. The chassis also includes Gigabit Ethernet/Ethernet support via SFP and
RJ-45 ports.
3.1.3.2.11 7705 SAR-M
The 7705 SAR-M has a fixed physical configuration that has four variants. Two
variants have 16 RJ-45 T1/E1 ports. All ports must be configured as either T1 or E1
ports; a mix of T1 and E1 ports is not allowed.
DS1 (T1) ports on the chassis can be configured for either B8ZS (bipolar with
eight-zero substitution) zero code suppression or AMI (alternate mark inversion).
B8ZS and AMI are line coding techniques.
3.1.3.2.12 7705 SAR-X
The 7705 SAR-X has a fixed physical configuration that provides TDM pseudowire
services via eight T1/E1 RJ-45 ports.
3.1.3.3 DSL
The 6-port DSL Combination module and the 8-port xDSL module (supported on the
7705 SAR-M), and two variants of the 7705 SAR-Wx support DSL.
Edition: 01 3HE 11011 AAAC TQZZA 41
Page 42
7705 SAR Interfaces
3.1.3.4 GNSS Receiver
Interface Configuration Guide
The 6-port DSL Combination module has six RJ-11 ports on its faceplate. Four of the
RJ-11 ports support G.SHDSL.bis pairs, and two RJ-11 ports support xDSL
operating in ADSL2,ADSL2+, or VDSL2 mode with no intermixing of DSL types.
The 8-port xDSL module has eight RJ-11 ports on its faceplate that support ADSL2,
ADSL2+, or VDSL2 mode with no intermixing of DSL types.
The 7705 SAR-M views the Ethernet link on a DSL module as an Ethernet port. Any
services on the 7705 SAR that are supported on an Ethernet port are also supported
on the Ethernet link on a DSL module.
Two variants of the 7705 SAR-Wx support one 4-pair xDSL port.
The 7705 SAR-H GPS Receiver module is equipped with a GPS RF port for retrieval
and recovery of GPS and GLONASS signals. The 7705 SAR-Ax and some variants
of the 7705 SAR-Wx are equipped with an integrated GNSS receiver and a GNSS
RF port for retrieval and recovery of GPS and GLONASS signals.
The GNSS Receiver card installed in the 7705 SAR-8 or 7705 SAR-18 is equipped
with a GNSS RF port for retrieval and recovery of both GPS and GLONASS signals.
Note: GLONASS-only signal recovery is not supported in this release.
3.1.3.5 GPON
The GPON module is a single-port optical network terminal (ONT) that integrates
passive optical network (PON) capabilities into the 7705 SAR-M. The GPON module
serves as an Ethernet Layer 2 connection point for receiving data from and
transmitting data into a GPON network.
The GPON module connects to the 7705 SAR-M as a Gigabit Ethernet port. From an
operational perspective, the 7705 SAR-M views the module as one of its Ethernet
ports.
42
3HE 11011 AAAC TQZZA Edition: 01
Page 43
Interface Configuration Guide 7705 SAR Interfaces
3.1.3.6 Multilink Bundles
A multilink bundle is a collection of channels on channelized ports that physically
reside on the same adapter card. Multilink bundles are used by providers who offer
either bandwidth-on-demand services or fractional bandwidth (DS3) services.
Multilink bundles are supported over PPP channels (MLPPP). All member links of an
MLPPP group must be of the same type (either E1 or DS1).
The following cards, modules, and platforms support multilink bundles:
• T1/E1 ports on the 7705 SAR-A (variants with T1/E1 ports)
• T1/E1 ports on the 7705 SAR-M (variants with T1/E1 ports)
• T1/E1 ports on the 7705 SAR-X
The following must have all member links of an MLPPP bundle configured on
the same card or module:
− 16-port T1/E1 ASAP Adapter card
− 32-port T1/E1 ASAP Adapter card
− T1/E1 ports on the 4-port T1/E1 and RS-232 Combination module (on
7705 SAR-H)
The following must have all member links of an MLPPP bundle configured on
the same card or module, and on the same port:
− 2-port OC3/STM1 Channelized Adapter card
− 4-port OC3/STM1 / 1-port OC12/STM4 Adapter card
3.1.3.7 IMA
The 16-port T1/E1 ASAP Adapter card, 32-port T1/E1 ASAP Adapter card, and the
2-port OC3/STM1 Channelized Adapter card support Inverse Multiplexing over ATM
(IMA). IMA is a standard developed to address the increasing need for bandwidth
greater than the DS1 or E1 link speeds (1.544 or 2.048 Mb/s, respectively) but less
than higher link speeds such as DS3 (44.736 Mb/s). IMA combines the transport
bandwidth of multiple DS1 or E1 channels in a logical link (called an IMA group) to
provide scalable bandwidth.
3.1.3.8 SONET/SDH
The 4-port OC3/STM1 Clear Channel Adapter card has four hot-pluggable,
SFP-based ports that can be independently configured to be SONET (OC3) or SDH
(STM1).
Edition: 01 3HE 11011 AAAC TQZZA 43
Page 44
7705 SAR Interfaces
3.1.3.9 Voice
Interface Configuration Guide
The 2-port OC3/STM1 Channelized Adapter card has two hot-pluggable, SFP-based
ports that can be configured to be SONET (OC3) or SDH (STM1). All ports on the
2-port OC3/STM1 Channelized Adapter card must be of the same type (either
SONET or SDH).
The 4-port OC3/STM1 / 1-port OC12/STM4 Adapter card has four hot-pluggable,
SFP-based ports that can be configured to be SONET (OC3 or OC12) or SDH (STM1
or STM4). The card can be configured to be in either 4-port mode or 1-port mode
(using the mda-mode command). In 4-port mode, all four ports can be configured as
OC3 or STM1. In 1-port mode, only port 1 can be configured as OC12 or STM4. All
ports on the 4-port OC3/STM1 / 1-port OC12/STM4 Adapter card must be of the
same type (either SONET or SDH).
Voice ports are supported on the following cards:
• 6-port E&M Adapter Card
• 8-port Voice & Teleprotection Card
• 8-port FXO Adapter Card
• 6-port FXS Adapter Card
3.1.3.9.1 6-port E&M Adapter Card
The 6-port E&M Adapter card has six RJ-45 ports that support the transport of an
analog voiceband signal between two analog devices over a digital network. The
analog signals are converted into a 64 kb/s digital Pulse Code Modulation (PCM)
format using either Mu-Law (North America) or A-Law (Rest of World) companding.
The type of companding is selectable on a per-card basis. Companding conversion
(that is, Mu-Law to A-Law or vice versa) is not supported.
The signaling type is selectable on a per-card basis depending on companding type.
When A-Law companding is configured, the signaling type is automatically type V.
When Mu-Law companding is configured, all signaling types can be selected;
however, the only supported configurations are both ends of the connection
operating in the same mode (for example, Type I to Type I) or one end operating in
Type I mode and the other in Type V mode. The default signaling type for Mu-Law is
Type I.
44
3HE 11011 AAAC TQZZA Edition: 01
Page 45
Interface Configuration Guide 7705 SAR Interfaces
Each voice port can be configured to operate in either a two-wire or four-wire
(default) mode. The ports (in groups of three – ports 1 to 3 and ports 4 to 6) can also
be configured to operate in transmission-only mode, which provides a four-wire audio
path with no signaling. A transmit and receive transmission level point (the
analog-to-digital decibel level) can be configured for each port. See Table 4 for the
signaling type, companding law and audio wires configuration options on the 6-port
E&M Adapter card.
Table 4 Configuration Options for the 6-port E&M Adapter Card
Signaling Type Companding Type Number of Wires
Type I, Type II, Type V Mu-Law Two-wire or four-wire
Type V A-Law Two-wire or four-wire
Transmission-only (no signaling) Mu-Law or A-Law Four-wire
3.1.3.9.2 8-port Voice & Teleprotection Card
The 8-port Voice & Teleprotection card supports the transport of an analog
voiceband signal between two analog devices over a digital network
The card has two FXS RJ-45 ports and two FXO RJ-45 ports that support analog
voiceband signals. The analog signals are converted into a 64 kb/s digital Pulse
Code Modulation (PCM) format using either Mu-Law (North America) or A-Law (Rest
of World) companding. The type of companding is selectable on a per-card basis.
Companding conversion (that is, Mu-Law to A-Law or vice versa) is not supported.
The signaling type is selectable at the port level on a per-port basis depending on
companding type.
FXO supports:
• 1511profile1 (1511 Loop Start) – A-Law companding
• 3600ls (Loop Start) – Mu-Law companding
• 3600re (Remote Extension) – A-Law companding
FXS supports:
• 3600plar (Private Line Automatic Ringdown) – A-Law and Mu-Law companding
• 1511plar – A-Law companding
• 1511profile1 (Loop Start) – A-Law companding
• 3600ls (Loop Start) – Mu-Law companding
Edition: 01 3HE 11011 AAAC TQZZA 45
Page 46
7705 SAR Interfaces
3.1.3.9.3 8-port FXO Adapter Card
Interface Configuration Guide
• 3600re (Remote Extension) – A-Law companding
The default signaling type for FXO and FXS is 3600ls for Mu-Law companding and
3600re for A-Law companding.
The 8-port FXO Adapter card supports the transport of an analog voiceband signal
between two analog devices over a digital network
The card supports analog voiceband signals through four RJ-45 connectors that
provide eight Foreign Exchange Office (FXO) ports, with two ports supported per
connector. The analog signals are converted into a 64 kb/s digital Pulse Code
Modulation (PCM) format using either Mu-Law (North America) or A-Law (Rest of
World) companding. The type of companding is selectable on a per-card basis.
Companding conversion (that is, Mu-Law to A-Law or vice versa) is not supported.
The signaling type is selectable at the port level on a per-port basis depending on
companding type.
FXO supports:
• 1511profile1 (1511 loop start) – A-Law companding
• 3600ls (loop start) – Mu-Law companding
• 3600re (remote extension) – A-Law companding
The default signaling type is 3600ls for Mu-Law companding and 3600re for A-Law
companding.
3.1.3.9.4 6-port FXS Adapter Card
The 6-port FXS Adapter card provides the capability of transporting a large number
of voice circuits from one 7705 SAR location and terminating them at another
7705 SAR location that is connected to a PBX.
The card can also be configured for a Private Line Automatic Ringdown (PLAR)
application, which is typically used outside of a PBX network, in order to provide a
site-to-site or remote site-to-control center hotline functionality.
46
3HE 11011 AAAC TQZZA Edition: 01
Page 47
Interface Configuration Guide 7705 SAR Interfaces
The card has six Foreign Exchange Subscriber (FXS) ports. Each port provides a
short-reach, on-premises analog interface to an analog telephone set. After an
incoming analog signal from a set is terminated on one of the FXS interfaces, it is
converted into a digital 64 kb/s Pulse Code Modulation (PCM) format using either
Mu-Law companding (North America) or A-Law companding (Rest of World).
The signal is then mapped into the E1 Channel Associated Signaling (CAS) transport
scheme for A-Law or the T1 Robbed Bit Signaling (RBS) transport scheme for
Mu-Law and transmitted using a Cpipe over any 7705 SAR network interface that
supports the Cpipe service. For standard TDM, the network interface can be a T1/E1
or OC3/STM1 channelized interface. For MPLS, an Ethernet, T1/E1, OC3/STM1
channelized MLPPP, or OC3/STM1 clear channel interface can be used.
For a PBX application, the signal is terminated at the 7705 SAR hub location that is
connected to a PBX by either an FXO interface or a T1/E1 interface (assuming the
signaling formats are compatible). The FXO interface can be provided by either an
8-port FXO Adapter card or 8-port Voice & Teleprotection card that is installed in a
7705 SAR-8 or 7705 SAR-18 chassis at the 7705 SAR hub location.
For a PLAR application, the signal is terminated on an FXS interface on either
another 6-port FXS Adapter card or an 8-port Voice & Teleprotection card that is
installed in a 7705 SAR-8 or 7705 SAR-18 chassis that is located at a remote
location, or terminated on a 3600 MainStreet or 1511 MAX. The connection is made
over an E1 interface ⌠(3600 MainStreet or 1511 MAX) or a T1 interface (3600
MainStreet). A hotline call can originate from a 3600 MainStreet or 1511 MAX and
terminate on an FXS interface on a 6-port FXS Adapter card (or on an FXS interface
on an 8-port Voice & Teleprotection card).
Table 5 shows the configuration options available on a 6-port FXS Adapter card. The
companding law type is configured at the card level; the other options are configured
at the voice port level.
Table 5 Configuration Options for the 6-port FXS Adapter Card
Configuration Supported Options
Companding type Mu-Law (the default)
A-Law
Fault signaling Idle (the default)
Seized
Line balance Nominal (the default)
800
Edition: 01 3HE 11011 AAAC TQZZA 47
Page 48
7705 SAR Interfaces
Interface Configuration Guide
Table 5 Configuration Options for the 6-port FXS Adapter Card
Configuration Supported Options
Ring generation 16 Hz (the default)
20 Hz
25 Hz
Signaling type 3600 Private Line Automatic Ringdown (PLAR) (if Mu-Law
or A-Law is used)
1511 PLAR (if A-Law is used)
1511 Profile1 (if A-Law is used)
3600 Loop Start (LS) (if Mu-Law is used; this is the default)
3600 Remote Extension (RE) (if A-Law is used; this is the
default)
Transmission level point
(TLP)
Rx: –7 dB to 0 dB (1-dB increments; the default is –3 dB)
Tx: –4 dB to +3 dB (1-dB increments; the default is 0 dB)
3.1.3.10 Microwave Link
A microwave link can be configured as a virtual port object on a 7705 SAR-8 or
7705 SAR-18 in order to provide a basic microwave connection or the Microwave
Awareness (MWA) capability to an MPR-e node
For more information, see Microwave Link.
3.1.3.11 CLI Identifiers for Adapter Cards, Modules and Platforms
On the CLI, the adapter cards are referred to as MDAs. A port is identified using the
format slot/mda/port, where slot identifies the IOM card slot ID (always 1), mda
identifies the physical slot in the chassis for the adapter card, and port identifies the
physical port on the adapter card; for example, 1/5/1. Adapter cards are configured
at the card and port level.
48
On the fixed platforms, no configuration is required at the adapter card level in order
to provision the ports.
On the CLI for the 7705 SAR-A, the slot/mda identifier for T1/E1 ports is 1/2 and for
Ethernet ports is 1/1. T1/E1 ports are identified as 1/2/1 through 1/2/8 for the variant
of the chassis with T1/E1 ports. Ethernet ports for both variants of the 7705 SAR-A
are identified as 1/1/1 through 1/1/12.
3HE 11011 AAAC TQZZA Edition: 01
Page 49
Interface Configuration Guide 7705 SAR Interfaces
On the CLI for the 7705 SAR-Ax, the slot/mda identifier for Ethernet ports is 1/1 and
for the GNSS RF port is 1/2.
On the CLI for the 7705 SAR-H, the slot/mda identifier for Ethernet ports is 1/1. The
chassis has two slots for modules (the 4-port T1/E1 and RS-232 Combination
module, the GPS Receiver module, and the 4-port SAR-H Fast Ethernet module). On
the CLI, the slot/mda identifier for a module installed in the first slot position is 1/2
and for a module installed in the second slot position is 1/3. Ethernet ports are
identified as 1/1/1 through 1/1/8. Module ports are identified as 1/2/port-num for
modules installed in the first slot position and 1/3/port-num for modules installed in
the second slot position.
On the CLI for the 7705 SAR-Hc, the slot/mda identifier for Ethernet ports is 1/1 and
for RS-232 ports is 1/2. Ethernet ports are identified as 1/1/1 through 1/1/6 and
RS-232 ports are identified as 1/2/1 and 1/2/2.
On the CLI for the 7705 SAR-M, the slot/mda identifier for T1/E1 ports is 1/2 and for
Ethernet ports is 1/1. For those variants of the chassis that have a module slot, the
slot/mda identifier for the module on the CLI is 1/3. The 7705 SAR-M variants with
module slots support the following modules: GPON module, 6-port DSL Combination
module, 8-port xDSL module, CWDM OADM module, 2-port 10GigE (Ethernet)
module, and 6-port SAR-M Ethernet module. T1/E1 ports are identified as 1/2/1
through 1/2/16 for those variants of the chassis with T1/E1 ports. Ethernet ports for
all variants of the 7705 SAR-M are identified as 1/1/1 through 1/1/7. Those variants
of the chassis that have module slots identify module ports as 1/3/port-num.
On the CLI for the 7705 SAR-W, the slot/mda identifier for the Ethernet ports is 1/1.
Ethernet ports are identified as 1/1/1 through 1/1/5. The 7705 SAR-W also has an
internal (virtual) port used for in-band Ethernet management connection. The virtual
port is identified as vrtl-mgmt on the CLI and as 1/1/6 via SNMP.
On the CLI for the 7705 SAR-Wx, the slot/mda identifier for the Ethernet ports is 1/1
and 1/2 for the xDSL port. Ethernet ports for the Ethernet-only variant and the
Ethernet and PoE+ variant are identified as 1/1/1 through 1/1/5. For the variant
supporting Ethernet ports and an xDSL port, the Ethernet ports are identified as 1/1/1
through 1/1/4 and the DSL port is identified as 1/2/1 through 1/2/4.
On the CLI for the 7705 SAR-X, the slot/mda identifier is specified as 1 for T1/E1
ports and 2 or 3 for Ethernet ports. The port number is specified as a variable that
can have a value from 1 to 8 for T1/E1 ports or 1 to 7 for Ethernet ports, depending
on how the port is configured.
Edition: 01 3HE 11011 AAAC TQZZA 49
Page 50
7705 SAR Interfaces
Interface Configuration Guide
For the 16-port T1/E1 ASAP Adapter card, 32-port T1/E1 ASAP Adapter card, and
4-port DS3/E3 Adapter card, the channel-group-id identifies the DS1 or E1 channel
group; for example, 1/5/1.20. For the 2-port OC3/STM1 Channelized Adapter card,
the channel-group-id identifies the DS1, E1, or DS3 channel group. For the 4-port
OC3/STM1 / 1-port OC12/STM4 Adapter card, the channel-group-id identifies the
DS1 or E1 channel group. For the 12-port Serial Data Interface card, the
channel-group-id identifies the V.35, RS-232, or X.21 channel group; only one
channel group per port is supported on the card, so the format would be 1/1/1.1.
For the 6-port E&M Adapter card, the channel-group-id identifies the E&M voice
channel group; only one channel group per port is supported on the card, so the
format would be 1/1/1.1. For the 8-port Voice & Teleprotection card, the 8-port FXO
Adapter card, and the 6-port FXS Adapter card, the channel-group-id identifies the
DS0 channel group; only one channel group per port is supported on the card, so the
format would be 1/1/1.1.
For the 4-port T1/E1 and RS-232 Combination module, the channel-group-id
identifies the DS1 or E1 channel group for the T1/E1 ports (for example, 1/2/3.5) or
the channel group for the RS-232 ports (for example, 1/2/2.1).
On the CLI for the 2-port 10GigE (Ethernet) Adapter card or 2-port 10GigE (Ethernet)
module, for virtual-port configuration, an Ethernet port is identified as v-port.
The following output examples display the administrative and operational states of
adapter cards for all platforms.
For the 7705 SAR-8 with a CSMv2:
ALU-1>show card state
==============================================================================
Card State
==============================================================================
Slot/ Provisioned Type Admin Operational Num Num Comments
Id Equipped Type (if different) State State Ports MDA
-----------------------------------------------------------------------------1 iom-sar up up 6
1/1 a12-sdiv2 up provisioned 12
1/2 a4-oc3 up provisioned 4
1/3 a16-chds1 up provisioned 16
1/4 a4-chds3 up provisioned 4
1/5 a8-eth up provisioned 8
1/6 a2-choc3 up provisioned 2
A csmv2-10g up up Active
B csmv2-10g up down Standby
==============================================================================
ALU-1>#
50
3HE 11011 AAAC TQZZA Edition: 01
Page 51
Interface Configuration Guide 7705 SAR Interfaces
For the 7705 SAR-18:
*A:ALU-1# show card state
==============================================================================
Card State
==============================================================================
Slot/ Provisioned Type Admin Operational Num Num Comments
Id Equipped Type (if different) State State Ports MDA
-----------------------------------------------------------------------------1 iom-sar up up 12
1/1 aux-alarm up up
1/2 a8-ethv2 up up 8
1/3 a8-ethv2 up up 8
1/4 a8-ethv2 up provisioned 8
1/5 a8-ethv2 up provisioned 8
1/6 a32-chds1v2 up up 32
1/7 a32-chds1v2 up up 32
1/8 a8-pmc up up 8
1/9 mw-pic-2 up up 2
1/10 a4-oc3 up provisioned 4
1/11 a4-chds3 up provisioned 4
1/12 a2-choc3 up provisioned 2
1/X1 x-10GigE up provisioned 1
1/X2 x-10GigE up provisioned 1
1/X3 x-10GigE up provisioned 1
1/X4 x-10GigE up provisioned 1
A csm-10g up up Active
B csm-10g up down Standby
==============================================================================
*A:ALU-1#
For the 7705 SAR-A:
*A:ALU-1# show card state
==============================================================================
Card State
==============================================================================
Slot/ Provisioned Type Admin Operational Num Num Comments
Id Equipped Type (if different) State State Ports MDA
-----------------------------------------------------------------------------1 iom-sar up up 2
1/1 i12-eth-xor up up 12
1/2 i8-chds1 up up 8
A csm-2.5g up up Active
==============================================================================
*A:ALU-1#
Edition: 01 3HE 11011 AAAC TQZZA 51
Page 52
7705 SAR Interfaces
Interface Configuration Guide
For the 7705 SAR-Ax:
*A:sar-Ax# show card state
===============================================================================
Card State
===============================================================================
Slot/ Provisioned Type Admin Operational Num Num Comments
Id Equipped Type (if different) State State Ports MDA
------------------------------------------------------------------------------1 iom-sar up up 2
1/1 i12-1gb-xor up up 12
1/2 i1-gnss up up 1
A csm-2.5g up up Active
===============================================================================
For the 7705 SAR-H:
*A:ALU-1# show card state
==============================================================================
Card State
==============================================================================
Slot/ Provisioned Type Admin Operational Num Num Comments
Id Equipped Type (if different) State State Ports MDA
-----------------------------------------------------------------------------1 iom-sar up up 3
1/1 i8-1gb up up 8
1/2 p4-combo up up 4
1/3 p4-combo up up 4
A csm-2.5g up up Active
==============================================================================
*A:ALU-1#
52
For the 7705 SAR-Hc:
*A:ALU-1# show card state
==============================================================================
Card State
==============================================================================
Slot/ Provisioned Type Admin Operational Num Num Comments
Id Equipped Type (if different) State State Ports MDA
-----------------------------------------------------------------------------1 iom-sar up up 2
1/1 i6-1gb up up 6
1/2 i2-sdi up up 2
A csm-2.5g up up Active
==============================================================================
*A:ALU-1#
3HE 11011 AAAC TQZZA Edition: 01
Page 53
Interface Configuration Guide 7705 SAR Interfaces
For the 7705 SAR-M:
*A:ALU-1# show card state
==============================================================================
Card State
==============================================================================
Slot/ Provisioned Type Admin Operational Num Num Comments
Id Equipped Type (if different) State State Ports MDA
-----------------------------------------------------------------------------1 iom-sar up up 3
1/1 i7-1gb up up 7
1/2 i16-chds1 up up 16
1/3 p1-GPON up up
A csm-2.5g up up Active
==============================================================================
*A:ALU-1#
For the 7705 SAR-W:
*A:ALU-1# show card state
==============================================================================
Card State
==============================================================================
Slot/ Provisioned Type Admin Operational Num Num Comments
Id Equipped Type (if different) State State Ports MDA
-----------------------------------------------------------------------------1 iom-sar up up 1
1/1 i5-1gb up up 6
A csm-2.5g up up Active
==============================================================================
*A:ALU-1#
For a 7705 SAR-Wx Ethernet variant:
*A:ALU-1# show card state
==============================================================================
Card State
==============================================================================
Slot/ Provisioned Type Admin Operational Num Num Comments
Id Equipped Type (if different) State State Ports MDA
-----------------------------------------------------------------------------1 iom-sar up up 1
1/1 i5-1gb-b up up 5
A csm-2.5g up up Active
==============================================================================
*A:ALU-1#
Edition: 01 3HE 11011 AAAC TQZZA 53
Page 54
7705 SAR Interfaces
Interface Configuration Guide
For a 7705 SAR-Wx Ethernet with xDSL variant:
*A:ALU-1# show card state
==============================================================================
Card State
==============================================================================
Slot/ Provisioned Type Admin Operational Num Num Comments
Id Equipped Type (if different) State State Ports MDA
-----------------------------------------------------------------------------1 iom-sar up up 2
1/1 i4-1gb-b up up 4
1/2 i4-xdsl up up 1
A csm-2.5g up up Active
==============================================================================
*A:ALU-1#
For a 7705 SAR-X:
*A:ALU-1# show card state
==============================================================================
Card State
==============================================================================
Slot/ Provisioned Type Admin Operational Num Num Comments
Id Equipped Type (if different) State State Ports MDA
-----------------------------------------------------------------------------1 iom-sar up up 3
1/1 i8-chds1-x up up 8
1/2 i7-mix-eth up up 7
1/3 i7-mix-eth up up 7
A csm-2.5g up up Active
===============================================================================
*A:ALU-1#
54
3.1.3.12 Access, Network, and Hybrid Ports
All ports must be set to access (customer-facing), network, or hybrid mode. When
the mode is configured on a port, the appropriate encapsulation type must be
configured to distinguish the services on the port or channel (for access mode), or to
define the transport mode (for network mode).
For the 16-port T1/E1 ASAP Adapter card, version 2, 32-port T1/E1 ASAP Adapter
card, and 4-port DS3/E3 Adapter card, the card must be enabled to support a set of
software services before the encapsulation type is configured. This support is
enabled using the mda-mode command (see the mda-mode command in the
Configuration Command Reference section):
• access ports — configured for customer-facing traffic on which services are
configured. If a Service Access Point (SAP) is to be configured on the port or
channel, the port or channel must be configured as an access port or channel.
3HE 11011 AAAC TQZZA Edition: 01
Page 55
Interface Configuration Guide 7705 SAR Interfaces
On the 16-port T1/E1 ASAP Adapter card, version 1, the encapsulation type can
be ipcp, cem, or atm. The encapsulation type on the 16-port T1/E1 ASAP
Adapter card, version 2, and the 32-port T1/E1 ASAP Adapter card can be ipcp,
cem, atm, frame-relay, hdlc, or cisco-hdlc.
On the 12-port Serial Data Interface card, the encapsulation type can be cem,
ipcp, frame-relay, hdlc, or cisco-hdlc. V.35 ports and X.21 ports at super-rate
speeds (64 kb/s and above) support all of the above encapsulation types.
RS-232 ports and X.21 ports operating at subrate speeds support only cem
encapsulation.
On the 4-port T1/E1 and RS-232 Combination module, the encapsulation type
for T1/E1 ports can be ipcp or cem. RS-232 ports operating at subrate speeds
support only cem encapsulation.
On the 6-port E&M Adapter card, 8-port Voice & Teleprotection card,
8-port FXO Adapter card, and 6-port FXS Adapter card, the encapsulation type
must be cem.
On the 8-port Ethernet Adapter card, the 8-port Gigabit Ethernet Adapter card,
the 6-port Ethernet 10Gbps Adapter card, the 10-port 1GigE/1-port 10GigE
X-Adapter card, the Packet Microwave Adapter card, the 4-port SAR-H Fast
Ethernet module, the 6-port SAR-M Ethernet module, the xDSL ports on the
7705 SAR-Wx, and the Ethernet ports on all fixed platforms with Ethernet ports,
the encapsulation type can be set as null, dot1q, or qinq.
Note:
• The 10-port 1GigE/1-port 10GigE X-Adapter card supports qinq only when it is
in 10-port 1GigE mode.
• The Packet Microwave Adapter card supports qinq only when the port is not in
mw-link mode.
On the 4-port OC3/STM1 Clear Channel Adapter card, the encapsulation type
must be atm.
On the 4-port DS3/E3 Adapter card, the encapsulation type for DS3/E3 clear
channel ports can be atm, cem, or frame-relay. The encapsulation type for DS3
channelized ports can be cem or frame-relay.
On the 2-port OC3/STM1 Channelized Adapter card, the encapsulation type can
be ipcp, cem, or atm.
On the 4-port OC3/STM1 / 1-port OC12/STM4 Adapter card, the encapsulation
type must be cem.
• network ports — configured for network-facing traffic. Network ports are used as
uplinks for Ethernet, ATM, PPP, and TDM pseudowires.
Edition: 01 3HE 11011 AAAC TQZZA 55
Page 56
7705 SAR Interfaces
Interface Configuration Guide
On the Ethernet cards, the Packet Microwave Adapter card, the 2-port 10GigE
(Ethernet) Adapter card, and 2-port 10GigE (Ethernet) module, the
encapsulation type can be set as null or dot1q.
Note: QinQ encapsulation is not supported on a port in network mode.
The encapsulation type must be ppp-auto for PPP/MLPPP bundles on the
following:
− T1/E1 ports on the 7705 SAR-A (variants with T1/E1 ports)
− T1/E1 ports on the 7705 SAR-M (variants with T1/E1 ports)
− T1/E1 ports on the 7705 SAR-X
− 16-port T1/E1 ASAP Adapter card
− 32-port T1/E1 ASAP Adapter card
− 2-port OC3/STM1 Channelized Adapter card
− 4-port OC3/STM1 / 1-port OC12/STM4 Adapter card
− T1/E1 ports on the 4-port T1/E1 and RS-232 Combination module (on
7705 SAR-H)
Network PPP (encapsulation type ppp-auto) can be configured to use some with
fractional ppp or all the timeslots on T1/E1 ports on the following cards:
− T1/E1 ports on the 7705 SAR-A (variants with T1/E1 ports)
− T1/E1 ports on the 7705 SAR-M (variants with T1/E1 ports)
− T1/E1 ports on the 7705 SAR-X
− 16-port T1/E1 ASAP Adapter card
− 32-port T1/E1 ASAP Adapter card
− T1/E1 ports on the 4-port T1/E1 and RS-232 Combination module (on
7705 SAR-H)
On the 4-port OC3/STM1 Clear Channel Adapter card, 4-port OC3/STM1 /
1-port OC12/STM4 Adapter card, and 4-port DS3/E3 Adapter card, the
encapsulation type must be ppp-auto. Fractional PPP is not supported on these
cards; all timeslots of the DS1 will be used.
• hybrid ports — configured for access (customer-facing) and network-facing
traffic. Hybrid ports can support access and network modes simultaneously over
different VLANs. Within the span of a port, some of the VLANs can be in access
mode and associated with SAPs for various services, while other VLANs can be
in network mode and support any of the network-side operations, including label
switching, IP forwarding (GRT IP routing), GRE SDPs, and so on.
56
3HE 11011 AAAC TQZZA Edition: 01
Page 57
Interface Configuration Guide 7705 SAR Interfaces
The default modes are listed in Table 6. All channel groups on a port must either be
all access or all network channel groups; there cannot be a mix. When the first
channel group is configured, all other channel groups on that port must be set to the
same mode. To change modes, all channel groups must first be shut down.
Table 6 Default Port Mode per Adapter Card, Module, or Platform
Default Mode Adapter Card, Module, or Platform
Network 2-port 10GigE (Ethernet) Adapter card
2-port 10GigE (Ethernet) module
6-port DSL Combination module
8-port xDSL module
10-port 1GigE/1-port 10GigE X-Adapter card
GPON module
Edition: 01 3HE 11011 AAAC TQZZA 57
Page 58
7705 SAR Interfaces
Interface Configuration Guide
Table 6 Default Port Mode per Adapter Card, Module, or Platform
Default Mode Adapter Card, Module, or Platform
Access 2-port OC3/STM1 Channelized Adapter card
4-port DS3/E3 Adapter card
4-port OC3/STM1 / 1-port OC12/STM4 Adapter card
4-port OC3/STM1 Clear Channel Adapter card
4-port SAR-H Fast Ethernet module
4-port T1/E1 and RS-232 Combination module is access for
the T1/E1 ports; the RS-232 ports operate in access mode
only
6-port E&M Adapter card
6-port Ethernet 10Gbps Adapter card
6-port FXS Adapter card
6-port SAR-M Ethernet module
8-port Ethernet Adapter card
8-port FXO Adapter card
8-port Gigabit Ethernet Adapter card
8-port Voice & Teleprotection card
12-port Serial Data Interface card
16-port T1/E1 ASAP Adapter card
32-port T1/E1 ASAP Adapter card
Auxiliary Alarm card
CWDM OADM Adapter card
GNSS Receiver card
GPS Receiver module
Integrated Services card
Packet Microwave Adapter card
Power Injector card
7705 SAR-A
7705 SAR-Ax
7705 SAR-H
7705 SAR-Hc
7705 SAR-M
7705 SAR-W
7705 SAR-Wx
7705 SAR-X
58
3HE 11011 AAAC TQZZA Edition: 01
Page 59
Interface Configuration Guide 7705 SAR Interfaces
3.1.3.12.1 Rate Limiting
The 7705 SAR supports egress-rate limiting and ingress-rate limiting on Ethernet
ports.
The egress rate is set at the port level in the config>port>ethernet context.
Egress-rate limiting sets a limit on the amount of traffic that can leave the port to
control the total bandwidth on the interface. If the egress-rate limit is reached, the
port applies backpressure on the queues, which stops the flow of traffic until the
queue buffers are emptied. This feature is useful in scenarios where there is a fixed
amount of bandwidth; for example, a mobile operator who has leased a fixed amount
of bandwidth from the service provider.
The ingress-rate command configures a policing action to rate-limit the ingress
traffic. Ingress-rate enforcement uses dedicated hardware for rate limiting; however,
software configuration is required at the port level (ingress-rate limiter) to ensure that
the network processor or the adapter card or port never receives more traffic than
they are optimized for.
The configured ingress rate ensures that the network processor does not receive
traffic greater than this configured value on a per-port basis. Once the ingress-rate
value is reached, all subsequent frames are dropped. The ingress-rate limiter drops
excess traffic without determining whether the traffic has a higher or lower priority.
3.1.3.12.2 Access Ports
Access ports on the following can be configured for PPP/MLPPP channel groups:
• 2-port OC3/STM1 Channelized Adapter card
• 16-port T1/E1 ASAP Adapter card
• 32-port T1/E1 ASAP Adapter card
• T1/E1 ports on the 4-port T1/E1 and RS-232 Combination module (on
7705 SAR-H)
• T1/E1 ports on the 7705 SAR-A (variants with T1/E1 ports)
• T1/E1 ports on the 7705 SAR-M (variants with T1/E1 ports)
• T1/E1 ports on the 7705 SAR-X
Customer IP traffic can be transported directly over PPP or MLPPP links. Access
ports on the following can also be configured for TDM to transport 2G traffic from
BTSs or ATM/IMA to transport 3G UMTS traffic from Node Bs:
• 2-port OC3/STM1 Channelized Adapter card
Edition: 01 3HE 11011 AAAC TQZZA 59
Page 60
7705 SAR Interfaces
Interface Configuration Guide
• 16-port T1/E1 ASAP Adapter card
• 32-port T1/E1 ASAP Adapter card
• T1/E1 ports on the 7705 SAR-M (variants with T1/E1 ports)
In access mode, PPP channels can be associated with n × DS0 channel groups.
Although multiple PPP channel groups are supported per T1/E1 port, all the channel
groups must be the same encapsulation type. For example, if one channel group on
a given port is set for ipcp encapsulation, another channel group on the same port
cannot be set to cem. If MLPPP channels are used, an MLPPP channel group fills
up an entire DS1 or E1 link.
The 2-port OC3/STM1 Channelized Adapter card supports ipcp encapsulation of
PPP/MLPPP packets for transport over an Ipipe.
The data ports on the 12-port Serial Data Interface card and the RS-232 ports on the
4-port T1/E1 and RS-232 Combination module provide transport between two data
devices. Each data stream that is transported across the network can be mapped
into a TDM pseudowire (Cpipe) for transport across an MPLS network. The other end
can terminate either on another 7705 SAR or a multiplexer capable of terminating the
pseudowire.
The 12-port Serial Data Interface card supports frame-relay encapsulation of data on
V.35 and X.21 channel groups for transport over a frame relay pseudowire (Fpipe)
or IP interworking pseudowire (Ipipe). The 12-port Serial Data Interface card also
supports ipcp and cisco-hdlc encapsulation of PPP and Cisco HDLC packets,
respectively, for transport over an Ipipe.
The 12-port Serial Data Interface card and the 4-port T1/E1 and RS-232
Combination module can also be part of a system architecture where a circuit
originates on an SDI port on the 7705 SAR, transits over an MPLS network, and
terminates on a 3600 MainStreet node connected to a 7705 SAR over a T1/E1
connection. In addition to the MPLS network functionality, the 12-port Serial Data
Interface card and the 4-port T1/E1 and RS-232 Combination modulec an also
operate in a TDM SAP-to-SAP mode where the other SAP can be another port on
the 12-port Serial Data Interface card or on a T1/E1 ASAP card.
Access ports on the 8-port Ethernet Adapter card, 8-port Gigabit Ethernet Adapter
card, 6-port Ethernet 10Gbps Adapter card, 10-port 1GigE/1-port 10GigE X-Adapter
card, the Packet Microwave Adapter card, and the xDSL ports on the 7705 SAR-Wx,
can transport traffic from sources such as e911 locators, site surveillance equipment,
VoIP phones, and video cameras. The Ethernet traffic is transported over the PSN
using Ethernet VLLs.
60
3HE 11011 AAAC TQZZA Edition: 01
Page 61
Interface Configuration Guide 7705 SAR Interfaces
Note: For information on VLLs, refer to the 7705 SAR Services Guide, “VLL Services”.
A microwave link from a Packet Microwave Adapter card port in access mode can
peer with user equipment such as a node B or MPR-e radio. The 7705 SAR-8 and
the 7705 SAR-18 treat the microwave access link as a normal SAP into a service
such as Epipe, Ipipe, or VPLS/VPRN.
Voice ports on the 6-port E&M Adapter card, 8-port Voice & Teleprotection card, and
8-port FXO Adapter card provide voiceband transmission between two analog
devices over a digital network. A 7705 SAR-8 or 7705 SAR-18 terminates the voice
circuit and then transmits the data over a TDM-based network interface
(SAP-to-SAP) or an MPLS packet-based network interface (SAP-to-SDP). For
standard TDM, a T1 or E1 interface is used to transmit the data across the network.
For MPLS, any network interface (that is, Ethernet, T1/E1 MLPPP, or OC3/STM1)
can be used. The traffic originating from the 6-port E&M Adapter card, 8-port Voice
& Teleprotection card, or 8-port FXO Adapter card can be mapped into a TDM
pseudowire (Cpipe) for transport across the MPLS network. The 6-port E&M Adapter
card, 8-port Voice & Teleprotection card, and 8-port FXO Adapter card support one
TDM pseudowire per port.
The voice circuit can terminate on another 7705 SAR-8 or 7705 SAR-18 over the
MPLS or T1/E1 TDM connection, on other TDM-capable equipment (such as a 3600
MainStreet node) over a T1/E1 TDM connection, or on other MPLS-capable
equipment over an MPLS pseudowire emulation (PWE) connection. A 3600
MainStreet or 1511 MAX can also connect to an FXO port on the 8-port Voice &
Teleprotection card.
Voice ports on a 6-port FXS Adapter card can be configured for a PBX application or
a PLAR (hotline) application. For a PBX application, the voice circuits are terminated
on an FXO interface at a 7705 SAR hub location that is connected to a PBX. The
FXO interface can be provided by either an 8-port FXO Adapter card or 8-port Voice
& Teleprotection card that is installed in a 7705 SAR-8 or 7705 SAR-18 chassis at
the 7705 SAR hub location. For a PLAR application, voice circuits are terminated on
an FXS interface on either another 6-port FXS Adapter card or an 8-port Voice &
Teleprotection card that is installed in a 7705 SAR-8 or 7705 SAR-18 chassis located
at a remote location, or terminated on a 3600 MainStreet or 1511 MAX. A hotline call
can also originate from a 3600 MainStreet or 1511 MAX and terminate on an FXS
interface on a 6-port FXS Adapter card (or on an FXS interface on an 8-port Voice &
Teleprotection card.
SONET/SDH ports in access mode on a 4-port OC3/STM1 Clear Channel Adapter
card can be configured for ATM (such as for 3G UMTS Node Bs).
Edition: 01 3HE 11011 AAAC TQZZA 61
Page 62
7705 SAR Interfaces
Interface Configuration Guide
The DS3/E3 clear channel access ports on the 4-port DS3/E3 Adapter card can be
configured for ATM PW services (categories CBR, VBR-rt, VBR-nrt, UBR, and
UBR+MCR), for TDM PW services to transport 2G traffic from BTSs, and for frame
relay PW service.
Access ports on the 2-port OC3/STM1 Channelized Adapter card can be configured
for TDM to transport 2G traffic from BTSs or ATM/IMA to transport 3G UMTS traffic
from Node Bs. Access ports on the 4-port OC3/STM1 / 1-port OC12/STM4 Adapter
card can only be configured for TDM.
All member links of the IMA group must reside on the same card. The 2G traffic is
transported across the PSN encapsulated in a TDM VLL. The 3G traffic is
transported using ATM VLLs.
For PPP/MLPPP channel groups, the encapsulation type must be ipcp. For Ethernet
VLLs, the encapsulation type can be null, dot1q, or qinq. For TDM VLLs, the
encapsulation type must be cem. For ATM VLLs, the encapsulation type must be
atm.
H-QoS for Access Egress Ethernet Ports
To support hierarchical QoS (H-QoS) on second-generation Ethernet adapter cards,
the 7705 SAR supports the configuration of one aggregate CIR rate for all the
unshaped 4-priority access egress Ethernet SAPs on a port, thereby ensuring that
all the unshaped SAPs can compete with the shaped SAPs on the port for fabric
bandwidth. Use the config>port>ethernet>access>egress>unshaped-sap-cir
command to set the aggregate CIR rate.
Third-generation (Gen-3) Ethernet adapter cards and platforms have 4-priority
schedulers, and all SAPs are shaped SAPs. See Table 2 for a list of first-, second-,
and third-generation adapter cards, modules, and platforms. Refer to the “QoS for
Gen-3 Adapter Cards and Platforms” section in the 7705 SAR Quality of Service
Guide for more information on 4-priority schedulers for Gen-3 hardware.
Ports on the 4-port SAR-H Fast Ethernet module do not support H-QoS.
For more information on H-QoS and on shaped and unshaped Ethernet SAPs, refer
to the “Per-SAP Aggregate Shapers (H-QoS)” section in the 7705 SAR Quality of
Service Guide.
62
3HE 11011 AAAC TQZZA Edition: 01
Page 63
Interface Configuration Guide 7705 SAR Interfaces
3.1.3.12.3 Network Ports
Network uplinks can be configured as standalone PPP ports, or MLPPP can be
configured on T1/E1 ports or channels. All member links of an MLPPP group must
be of the same type (either E1 or Ds1).
The following cards, modules, and platforms support multilink bundles:
• T1/E1 ports on the 7705 SAR-A (variants with T1/E1 ports)
• T1/E1 ports on the 7705 SAR-M (variants with T1/E1 ports)
• T1/E1 ports on the 7705 SAR-X
The following must have all member links of an MLPPP bundle configured on
the same card or module:
− 16-port T1/E1 ASAP Adapter card
− 32-port T1/E1 ASAP Adapter card
− T1/E1 ports on the 4-port T1/E1 and RS-232 Combination module (on
7705 SAR-H)
The following must have all member links of an MLPPP bundle configured on
the same card or module, and on the same port:
− 2-port OC3/STM1 Channelized Adapter card
− 4-port OC3/STM1 / 1-port OC12/STM4 Adapter card
Ethernet ports on the 8-port Ethernet Adapter card, 8-port Gigabit Ethernet Adapter
card, 6-port Ethernet 10Gbps Adapter card, 10-port 1GigE/1-port 10GigE X-Adapter
card, and Packet Microwave Adapter card can be configured for network mode.
Ethernet uplinks can be used as a cost-effective alternative to T1/E1 links.
On the 2-port 10GigE (Ethernet) Adapter card and 2-port 10GigE (Ethernet) module,
the Ethernet ports and the v-port can be configured for network mode only.
A microwave link from a Packet Microwave Adapter card port in network mode
provides a network uplink to an MPR-e radio. The 7705 SAR-8 or 7705 SAR-18
treats the microwave link as a Gigabit Ethernet network link with MPLS always
running over it. All standard MPLS/IP functions available on a network port or SDP
are also available on the microwave link.
For network uplinks on the 4-port OC3/STM1 Clear Channel Adapter card and 4-port
OC3/STM1 / 1-port OC12/STM4 Adapter card, a clear channel port can be
configured for POS to connect to the packet network. PPP can be enabled on a port
by setting the encapsulation type to ppp-auto.
On the 4-port DS3/E3 Adapter card, a DS3/E3 clear channel port can be configured
for PPP as the network uplink. The encapsulation type must be set to ppp-auto.
Edition: 01 3HE 11011 AAAC TQZZA 63
Page 64
7705 SAR Interfaces
Interface Configuration Guide
The 7705 SAR supports both copper and fiber uplinks.
Aggregate CIR for Unshaped VLANs on Network Egress Ethernet Ports
The 7705 SAR supports the configuration of one aggregate CIR rate for all the
unshaped network egress Ethernet VLANs on a port, thereby ensuring that all the
unshaped VLANs can compete with the shaped VLANs (that is, network interfaces)
at the port level for egress bandwidth. Use the config>port>ethernet>
network>egress>unshaped-if-cir command to set the aggregate CIR rate.
Note: The unshaped-if-cir command does not apply to Gen-3 Ethernet adapter cards and
platforms, except for network egress in hybrid mode. In this case, the shaper-if-cir
command applies.
For more information on shaped and unshaped Ethernet VLANs, refer to the
“Per-VLAN Network Egress Shapers” and “QoS for Gen-3 Adapter Cards and
Platforms” sections in the 7705 SAR Quality of Service Guide.
3.1.3.12.4 Hybrid Ports
Hybrid ports are supported on Ethernet ports, where they provide the capabilities and
features of access and network mode ports on a per-VLAN basis. The following
services support hybrid port functionality: Epipe PW, Ipipe PW, IP-VPN, VPLS, and
IES.
For ingress traffic, QoS and traffic management on a hybrid port behaves in the same
way for access and network port modes. Refer to the 7705 SAR Quality of Service
Guide, “QoS for Hybrid Ports on Gen-2 Hardware” and “QoS for Gen-3 Adapter
Cards and Platforms” for details.
Network VLANs on a hybrid port provide OAM down MEP support, as well as port
loopback support (in line mode with latched timers only).
The following hardware supports hybrid ports:
• 6-port SAR-M Ethernet module (except for the Fast Ethernet ports (ports 1 and
2))
• 6-port Ethernet 10Gbps Adapter card
• 8-port Gigabit Ethernet Adapter card
• 10-port 1GigE/1-port 10GigE X-Adapter card (only in 10-port 1GigE mode)
• Packet Microwave Adapter card (only in Ethernet port mode (not mw-link mode))
64
3HE 11011 AAAC TQZZA Edition: 01
Page 65
Interface Configuration Guide 7705 SAR Interfaces
FC=EF
FC=AF SAP-1
Hybrid
Por t
FC=BE
FC=EF
FC=AF VLAN-1
FC=BE
7705 SAR
7705 SAR
Agg.
vlan-2
vlan-1
24074
• 7705 SAR-A Ethernet ports (except for the Fast Ethernet ports (ports 9 to 12))
• 7705 SAR-Ax Ethernet ports
• 7705 SAR-M Ethernet ports
• 7705 SAR-H Ethernet ports
• 7705 SAR-Hc Ethernet ports
• 7705 SAR-W Ethernet ports
• 7705 SAR-Wx Ethernet ports
• 7705 SAR-X Ethernet ports
In some scenarios, combining the access and network capabilities under the same
port is beneficial. A typical scenario is shown in Figure 1, where a single port hosts
both access-side services and a traffic management model together with
network-side IP/MPLS routing and switching capabilities simultaneously.
In this scenario, a network interface is configured to ensure connectivity between the
cell site 7705 SAR and the aggregation site 7705 SAR. The network interface is used
for all IP/MPLS traffic and is bound to VLAN-1. Another VLAN (VLAN-2) is configured
to bind the management traffic of a microwave radio (an MPR-e) to an access-side
service such as an Ethernet PW or VPLS. For security reasons, many mobile
operators prefer to transport management traffic of network elements under a service
construct as opposed to basic GRT-based routing. To accommodate this preference,
an access-side service and a network interface can be configured to coexist on the
same port when the port is configured for hybrid mode.
Figure 1 Hybrid Port Application
Edition: 01 3HE 11011 AAAC TQZZA 65
Page 66
7705 SAR Interfaces
3.1.4 Configuring SCADA Bridges
Interface Configuration Guide
Surveillance, Control, and Data Acquisition (SCADA) bridges are configured on an
Integrated Services card as part of the multidrop data bridge (MDDB), pulse code
modulation (PCM) multidrop bridge, and voice conference bridge (VCB) functionality.
MDDB, PCM, and VCB are used to support SCADA systems on a 7705 SAR-8 or
7705 SAR-18.
For information on MDDB, see Multidrop Data Bridge. For information on PCM
multidrop bridge, see PCM Multidrop Bridge. For information on VCB, see Voice
Conference Bridge.
A SCADA bridge can be configured after the IOM is activated (the card slot and card
type are designated) and the adapter card slot is preprovisioned with the Integrated
Services card mda-type.
66
3HE 11011 AAAC TQZZA Edition: 01
Page 67
Interface Configuration Guide 7705 SAR Interfaces
3.2 Port Features
This section contains information on the following topics:
• Multilink Point-to-Point Protocol
• Multi-Class MLPPP
• cHDLC
• Inverse Multiplexing Over ATM (IMA)
• Network Synchronization on Ports and Circuits
• Node Synchronization From GNSS Receiver Ports
• Flow Control on Ethernet Ports
• Ethernet OAM
• Ethernet Loopbacks
• Ethernet Port Down-When-Looped
• Ethernet Ring (Adapter Card and Module)
• MTU Configuration Guidelines
• LAG
• LAG and ECMP Hashing
• Automatic Protection Switching
• Deploying Preprovisioned Components
• Microwave Link
• DSL Bonding
• Custom Alarms on Ethernet Ports
Edition: 01 3HE 11011 AAAC TQZZA 67
Page 68
7705 SAR Interfaces
3.2.1 Multilink Point-to-Point Protocol
Interface Configuration Guide
This section contains information on the following topics:
• MLPPP Overview
• Protocol Field (PID)
• B&E Bits
• Sequence Number
• Information Field
• Padding
• FCS
• LCP
• T1/E1 Link Hold Timers
3.2.1.1 MLPPP Overview
Multilink point-to-point protocol (MLPPP) is a method of splitting, recombining, and
sequencing packets across multiple logical data links. MLPPP is defined in the IETF
RFC 1990, The PPP Multilink Protocol (MP).
MLPPP allows multiple PPP links to be bundled together, providing a single logical
connection between two routers. Data can be distributed across the multiple links
within a bundle to achieve high bandwidth. As well, MLPPP allows for a single frame
to be fragmented and transmitted across multiple links. This capability allows for
lower latency and also for a higher maximum receive unit (MRU).
Multilink protocol is negotiated during the initial LCP option negotiations of a standard
PPP session. A system indicates to its peer that it is willing to perform MLPPP by
sending the MP option as part of the initial LCP option negotiation.
The system indicates the following capabilities.
• The system offering the option is capable of combining multiple physical links
into one logical link.
• The system is capable of receiving upper layer protocol data units (PDUs) that
are fragmented using the MP header and then reassembling the fragments back
into the original PDU for processing.
• The system is capable of receiving PDUs of size N octets, where N is specified
as part of the option, even if N is larger than the maximum receive unit (MRU)
for a single physical link.
68
3HE 11011 AAAC TQZZA Edition: 01
Page 69
Interface Configuration Guide 7705 SAR Interfaces
01234567890123456789012345678901
1111111111222222222233
Address 0xff
BE
Control 0x03 PID 0x003d
Sequence
Fragment Data...
Fragment Data... FCS
19487
01234567890123456789012345678901
1111111111222222222233
Address 0xff
BE
Control 0x03 PID 0x003d
Sequence Fragment Data
Fragment Data...
Fragment Data... FCS
19488
Once MLPPP has been successfully negotiated, the sending system is free to send
PDUs encapsulated and/or fragmented with the MP header.
MP introduces a new protocol type with a protocol ID (PID) of 0x003d. Figure 2 and
Figure 3 show the MLPPP fragment frame structure. Framing to indicate the
beginning and end of the encapsulation is the same as that used by PPP and
described in RFC 1662, PPP in HDLC-like Framing.
MP frames use the same HDLC address and control pair value as PPP: Address –
0xFF and Control – 0x03. The 2-octet protocol field is also structured the same way
as in PPP encapsulation.
Figure 2 MLPPP 24-bit Fragment Format
Figure 3 MLPPP 12-bit Fragment Format
The required and default format for MP is the 24-bit format. During the LCP state, the
12-bit format can be negotiated. The 7705 SAR is capable of supporting and
negotiating the alternate 12-bit frame format.
The maximum differential delay supported for MLPPP is 25 ms.
Edition: 01 3HE 11011 AAAC TQZZA 69
Page 70
7705 SAR Interfaces
3.2.1.2 Protocol Field (PID)
3.2.1.3 B&E Bits
Interface Configuration Guide
The protocol field is two octets. Its value identifies the datagram encapsulated in the
Information field of the packet. In the case of MP, the PID also identifies the presence
of a 4-octet MP header (or 2-octet, if negotiated).
A PID of 0x003d identifies the packet as MP data with an MP header.
The LCP packets and protocol states of the MLPPP session follow those defined by
PPP in RFC 1661. The options used during the LCP state for creating an MLPPP
NCP session are described in the sections that follow.
The B&E bits are used to indicate the start and end of a packet. Ingress packets to
the MLPPP process will have an MTU, which may or may not be larger than the
maximum received reconstructed unit (MRRU) of the MLPPP network. The B&E bits
manage the fragmentation of ingress packets when the packet exceeds the MRRU.
The B-bit indicates the first (or beginning) packet of a given fragment. The E-bit
indicates the last (or ending) packet of a fragment. If there is no fragmentation of the
ingress packet, both B&E bits are set to true (=1).
3.2.1.4 Sequence Number
Sequence numbers can be either 12 or 24 bits long. The sequence number is 0 for
the first fragment on a newly constructed bundle and increments by one for each
fragment sent on that bundle. The receiver keeps track of the incoming sequence
numbers on each link in a bundle and reconstructs the desired unbundled flow
through processing of the received sequence numbers and B&E bits. For a detailed
description of the algorithm, refer to RFC 1990.
3.2.1.5 Information Field
The Information field is zero or more octets. The Information field contains the
datagram for the protocol specified in the protocol field.
The MRRU will have the same default value as the MTU for PPP. The MRRU is
always negotiated during LCP.
70
3HE 11011 AAAC TQZZA Edition: 01
Page 71
Interface Configuration Guide 7705 SAR Interfaces
3.2.1.6 Padding
On transmission, the Information field of the ending fragment may be padded with an
arbitrary number of octets up to the MRRU. It is the responsibility of each protocol to
distinguish padding octets from real information. Padding must only be added to the
last fragment (E-bit set to true).
3.2.1.7 FCS
The FCS field of each MP packet is inherited from the normal framing mechanism
from the member link on which the packet is transmitted. There is no separate FCS
applied to the reconstituted packet as a whole if it is transmitted in more than one
fragment.
3.2.1.8 LCP
The Link Control Protocol (LCP) is used to establish the connection through an
exchange of configure packets. This exchange is complete, and the LCP opened
state entered, once a Configure-Ack packet has been both sent and received.
LCP allows for the negotiation of multiple options in a PPP session. MP is somewhat
different from PPP, and therefore the following options are set for MP and are not
negotiated:
• no async control character map
• no magic number
• no link quality monitoring
• address and control field compression
• protocol field compression
• no compound frames
• no self-describing padding
Any non-LCP packets received during this phase must be silently discarded.
Edition: 01 3HE 11011 AAAC TQZZA 71
Page 72
7705 SAR Interfaces
3.2.1.9 T1/E1 Link Hold Timers
3.2.2 Multi-Class MLPPP
Interface Configuration Guide
T1/E1 link hold timers (or MLPPP link flap dampening) guard against the node
reporting excessive interface transitions. Timers can be set to determine when link
up and link down events are advertised; that is, up-to-down and down-to-up
transitions of the interface are not advertised to upper layer protocols (are
dampened) until the configured timer has expired.
The 7705 SAR supports multi-class MLPPP (MC-MLPPP) to address end-to-end
delay caused by low-speed links transporting a mix of small and large packets. With
MC-MLPPP, large, low-priority packets are fragmented to allow opportunities to send
high-priority packets. QoS for MC-MLPPP is described in QoS in MC-MLPPP.
MC-MLPPP allows for the prioritization of multiple types of traffic flowing over
MLPPP links, such as traffic between the cell site routers and the mobile operator’s
aggregation routers. MC-MLPPP, as defined in RFC 2686, The Multi-Class
Extension to Multi-Link PPP, is an extension of the MLPPP standard. MC-MLPPP is
supported on access ports wherever PPP/MLPPP is supported, except on the 2-port
OC3/STM1 Channelized Adapter card. It allows multiple classes of fragments to be
transmitted over an MLPPP bundle, with each class representing a different priority
level mapped to a forwarding class. The highest-priority traffic is transmitted over the
MLPPP bundle with minimal delay regardless of the order in which packets are
received.
72
Figure 4 shows the original MLPPP header format that allowed only two implied
classes. The two classes were created by transmitting two interleaving flows of
packets; one with MLPPP headers and one without. This resulted in two levels of
priority sent over the physical link, even without the implementation of multi-class
support.
Figure 5 shows the short and long sequence number fragment format MC-MLPPP
headers. The short sequence number fragment format header includes two class bits
to allow for up to four classes of service. Four class bits are available in the long
sequence number fragment format header, but a maximum of four classes are still
supported. This extension to the MLPPP header format is detailed in RFC 2686.
3HE 11011 AAAC TQZZA Edition: 01
Page 73
Interface Configuration Guide 7705 SAR Interfaces
20492
Address 0xff
BE00
Control 0x03
PID (H) 0x00 PID(L) 0x3D
Seq. Number
Fragment Data
.....
FCS
20491
Address 0xff
BE
Control 0x03
PID (H) 0x00 PID(L) 0x3D
CLS
Seq. Number
Fragment Data
.....
FCS
Address 0xff
BE 0 0
Control 0x03
PID (H) 0x00 PID(L) 0x3D
CLS
Seq. Number
Sequence Number (L)
Fragment Data
.....
Short Sequence Number Fragment
Fromat MC-MLPPP Header
Long Sequence Number Fragment
Fromat MC-MLPPP Header
FCS
Figure 4 Original MLPPP Header Format
Figure 5 MC-MLPPP Header Format
The new MC-MLPPP header format uses the previously unused bits before the
sequence number as the class identifier to allow four distinct classes of service to be
identified.
3.2.2.1 QoS in MC-MLPPP
MC-MLPPP on the 7705 SAR supports scheduling based on multi-class
implementation. Instead of the standard profiled queue-type scheduling, an
MC-MLPPP encapsulated access port performs class-based traffic servicing. The
four MC-MLPPP classes are scheduled in a strict priority fashion, as shown in
Edition: 01 3HE 11011 AAAC TQZZA 73
Table 7.
Page 74
7705 SAR Interfaces
Interface Configuration Guide
Table 7 MC-MLPPP Class Priorities
MC-MLPPP Class Priority
0 Priority over all other classes
1 Priority over classes 2 and 3
2 Priority over class 3
3No priority
For example, if a packet is sent to an MC-MLPPP class 3 queue and all other queues
are empty, the 7705 SAR fragments the packet according to the configured fragment
size and begins sending the fragments. If a new packet arrives at an MC-MLPPP
class 2 queue while the class 3 fragment is still being serviced, the 7705 SAR
finishes sending any fragments of the class 3 packet that are on the wire, then holds
back the remaining fragments in order to service the higher-priority packet.
The fragments of the first packet remain at the top of the class 3 queue. For packets
of the same class, MC-MLPPP class queues operate on a first-in, first-out basis.
The user configures the required number of MLPPP classes to use on a bundle. The
forwarding class of the packet, as determined by the ingress QoS classification, is
used to determine the MLPPP class for the packet. The mapping of forwarding class
to MLPPP class is a function of the user-configurable number of MLPPP classes.
The mapping for 4-class, 3-class, and 2-class MLPPP bundles is shown in Table 8.
Table 8 Packet Forwarding Class to MC-MLPPP Class Mapping
FC ID FC Name MLPPP Class
4-class Bundle
7NC000
6H1000
5EF111
4H2111
3L1221
2AF221
1L2321
0BE321
MLPPP Class
3-class Bundle
MLPPP Class
2-class Bundle
74
3HE 11011 AAAC TQZZA Edition: 01
Page 75
Interface Configuration Guide 7705 SAR Interfaces
If one or more forwarding classes are mapped to a queue, the scheduling priority of
the queue is based on the lowest forwarding class mapped to it. For example, if
forwarding classes 0 and 7 are mapped to a queue, the queue is serviced by
MC-MLPPP class 3 in a 4-class bundle model.
3.2.3 cHDLC
The 7705 SAR supports Cisco HDLC, which is an encapsulation protocol for
information transfer. Cisco HDLC is a bit-oriented synchronous data-link layer
protocol that specifies a data encapsulation method on synchronous serial links
using frame characters and checksums.
Cisco HDLC monitors line status on a serial interface by exchanging keepalive
request messages with peer network devices. The protocol also allows routers to
discover IP addresses of neighbors by exchanging SLARP address-request and
address-response messages with peer network devices.
The basic frame structure of a cHDLC frame is shown in Table 9.
Table 9 cHDLC Information Frame
Flag Address Control Protocol Information FCS
0x7E 0x0F, 0x8F 0x00 0x0800,
0x8035
— 16 or 32 bit
The fields in the cHDLC frame have the following characteristics:
• Address field—supports unicast (0x0F) and broadcast (0x8F) addresses
• Control field—always set to 0x00
• Protocol field—supports IP (0x0800) and SLARP (0x8035; see SLARP for
information about limitations)
• Information field—the length can be 0 to 9 kbytes
• FCS field—can be 16 or 32 bits. The default is 16 bits for ports with a speed
equal to or lower than OC3, and 32 bits for all other ports. The FCS for cHDLC
is calculated with the same method and same polynomial as PPP.
Edition: 01 3HE 11011 AAAC TQZZA 75
Page 76
7705 SAR Interfaces
3.2.3.1 SLARP
Interface Configuration Guide
The 7705 SAR supports only the SLARP keepalive protocol.
For the SLARP keepalive protocol, each system sends the other a keepalive packet
at a user configurable interval. The default interval is 10 seconds. Both systems must
use the same interval to ensure reliable operation. Each system assigns sequence
numbers to the keepalive packets it sends, starting with zero, independent of the
other system. These sequence numbers are included in the keepalive packets sent
to the other system. Also included in each keepalive packet is the sequence number
of the last keepalive packet received from the other system, as assigned by the other
system. This number is called the returned sequence number. Each system keeps
track of the last returned sequence number it has received. Immediately before
sending a keepalive packet, the system compares the sequence number of the
packet it is about to send with the returned sequence number in the last keepalive
packet it has received. If the two differ by 3 or more, it considers the line to have
failed, and will not route higher-level data across it until an acceptable keepalive
response is received.
3.2.4 Inverse Multiplexing Over ATM (IMA)
IMA is a cell-based protocol where an ATM cell stream is inverse-multiplexed and
demultiplexed in a cyclical fashion among ATM-supporting channels to form a higher
bandwidth logical link. This logical link is called an IMA group. By grouping channels
into an IMA group, customers gain bandwidth management capability at in-between
rates (for example, between DS1 and DS3 or between E1 and E3) through the
addition or removal of channels to or from the IMA group. The 7705 SAR supports
the IMA protocol as specified by the Inverse Multiplexing for ATM (IMA) Specifica tion
version 1.1.
In the ingress direction, traffic coming over multiple ATM channels configured as part
of a single IMA group is converted into a single ATM stream and passed for further
processing to the ATM layer, where service-related functions (for example, Layer 2
traffic management or feeding into a pseudowire) are applied. In the egress direction,
a single ATM stream (after service functions are applied) is distributed over all paths
that are part of an IMA group after ATM layer processing takes place.
An IMA group interface compensates for differential delay and allows for only a
minimal cell delay variation. The maximum differential delay supported for IMA is
75 ms on 16-port T1/E1 ASAP Adapter cards and 32-port T1/E1 ASAP Adapter cards
and 50 ms on 2-port OC3/STM1 Channelized Adapter cards.
76
3HE 11011 AAAC TQZZA Edition: 01
Page 77
Interface Configuration Guide 7705 SAR Interfaces
The interface deals with links that are added or deleted, or that fail. The higher layers
see only an IMA group and not individual links; therefore, service configuration and
management is done using IMA groups, and not individual links that are part of it.
The IMA protocol uses an IMA frame as the unit of control. An IMA frame consists of
a series of 128 consecutive cells. In addition to ATM cells received from the ATM
layer, the IMA frame contains IMA OAM cells. Two types of cells are defined: IMA
Control Protocol (ICP) cells and IMA filler cells. ICP cells carry information used by
the IMA protocol at both ends of an IMA group (for example, IMA frame sequence
number, link stuff indication, status and control indication, IMA ID, Tx and Rx test
patterns, version of the IMA protocol). A single ICP cell is inserted at the ICP cell
offset position (the offset may be different on each link of the group) of each frame.
Filler cells are used by the transmitting side to fill up each IMA frame in case there
are not enough ATM stream cells from the ATM layer, so a continuous stream of cells
is presented to the physical layer. Those cells are then discarded by the receiving
end. IMA frames are transmitted simultaneously on all paths of an IMA group, and
when they are received out of sync at the other end of the IMA group link, the receiver
compensates for differential link delays among all paths.
3.2.5 Network Synchronization on Ports and Circuits
The 7705 SAR provides network synchronization on the following ports and CES
circuits:
• Network Synchronization on T1/E1, Ethernet, GPON, and DSL Ports
• Network Synchronization on SONET/SDH Ports
• Network Synchronization on DS3/E3 Ports
• Network Synchronization on DS3 CES Circuits
• Network Synchronization on T1/E1 Ports and Circuits
3.2.5.1 Network Synchronization on T1/E1, Ethernet, GPON, and DSL Ports
Line timing mode provides physical layer timing (Layer 1) that can be used as an
accurate reference for nodes in the network. This mode is immune to any packet
delay variation (PDV) occurring on a Layer 2 or Layer 3 link. Physical layer timing
provides the best synchronization performance through a synchronization
distribution network.
Edition: 01 3HE 11011 AAAC TQZZA 77
Page 78
7705 SAR Interfaces
Interface Configuration Guide
On the 7705 SAR-A variant with T1/E1 ports, line timing is supported on T1/E1 ports.
Line timing is also supported on all synchronous Ethernet ports on both 7705 SAR-A
variants. Synchronous Ethernet is supported on the XOR ports (1 to 4), configured
as either RJ-45 ports or SFP ports. Synchronous Ethernet is also supported on SFP
ports 5 to 8. Ports 9 to 12 do not support synchronous Ethernet and, therefore, do
not support line timing.
On the 7705 SAR-Ax, line timing is supported on all Ethernet ports.
On the 7705 SAR-H, line timing is supported on:
• all Ethernet ports
• T1/E1 ports on a chassis equipped with a 4-port T1/E1 and RS-232 Combination
module
On the 7705 SAR-Hc, line timing is supported on all Ethernet ports.
On the 7705 SAR-M (variants with T1/E1 ports), line timing is supported on T1/E1
ports. Line timing is also supported on all RJ-45 Ethernet ports and SFP ports on the
7705 SAR-M (all variants).
On the 7705 SAR-W, line timing is supported on:
• RJ-45 Ethernet ports and optical SFP ports (these ports support synchronous
Ethernet and IEEE 1588v2 PTP)
On the 7705 SAR-Wx, line timing is supported on:
• RJ-45 Ethernet ports and optical SFP ports (these ports support synchronous
Ethernet and IEEE 1588v2 PTP)
On the 7705 SAR-X, line timing is supported on T1/E1 ports and Ethernet ports.
In addition, line timing is supported on the following modules when they are installed
in chassis variants with module slots:
• GPON module
• 8-port xDSL module (NTR over ADSL2, ADSL2+, or VDSL2)
• 6-port DSL Combination module (two references are available: NTR over
SHDSL and NTR over ADSL2, ADSL2+, or VDSL2)
• 2-port 10GigE (Ethernet) module
• 6-port SAR-M Ethernet module
78
3HE 11011 AAAC TQZZA Edition: 01
Page 79
Interface Configuration Guide 7705 SAR Interfaces
On the 7705 SAR-8 and 7705 SAR-18, line timing is supported on:
• 16-port T1/E1 ASAP Adapter card (version 1 is not supported on the
7705 SAR-18)
• 32-port T1/E1 ASAP Adapter card
• 8-port Ethernet Adapter card, version 2, on the two Ethernet SFP ports with
SFPs that support synchronous Ethernet
• 6-port Ethernet 10Gbps Adapter card
• 8-port Gigabit Ethernet Adapter card (dual-rate and copper SFPs do not support
synchronous Ethernet)
• 2-port 10GigE (Ethernet) Adapter card
• 10-port 1GigE/1-port 10GigE X-Adapter card (not supported on the
7705 SAR-8)
• 4-port DS3/E3 Adapter card
• 2-port OC3/STM1 Channelized Adapter card
• 4-port OC3/STM1 / 1-port OC12/STM4 Adapter card
• 4-port OC3/STM1 Clear Channel Adapter card
• Packet Microwave Adapter card on ports that support synchronous Ethernet and
on ports that support PCR
Synchronous Ethernet is a variant of line timing and is automatically enabled on ports
and SFPs that support it. The operator can select a synchronous Ethernet port as a
candidate for the timing reference. The recovered timing from this port is then used
to time the system. This ensures that any of the system outputs are locked to a
stable, traceable frequency source.
3.2.5.2 Network Synchronization on SONET/SDH Ports
Each SONET/SDH port can be independently configured to be loop-timed
(recovered from an Rx line) or node-timed (recovered from the SSU in the active
CSM).
A SONET/SDH port’s receive clock rate can be used as a synchronization source for
the node.
Edition: 01 3HE 11011 AAAC TQZZA 79
Page 80
7705 SAR Interfaces
3.2.5.3 Network Synchronization on DS3/E3 Ports
3.2.5.4 Network Synchronization on DS3 CES Circuits
Interface Configuration Guide
Each clear channel DS3/E3 port on a 4-port DS3/E3 Adapter card can be
independently configured to be loop-timed (recovered from an Rx line), node-timed
(recovered from the SSU in the active CSM), or differential-timed (derived from the
comparison of a common clock to the received RTP timestamp in TDM pseudowire
packets). When a DS3 port is channelized, each DS1 or E1 channel can be
independently configured to be loop-timed, node-timed, or differential-timed
(differential timing on DS1/E1 channels is supported only on the first three ports of
the card). When not configured for differential timing, a DS3/E3 port can be
configured to be a timing source for the node.
Each DS3 CES circuit on a 2-port OC3/STM1 Channelized Adapter card card can be
loop-timed (recovered from an Rx line) or free-run (timing source is from its own
clock). A DS3 circuit can be configured to be a timing source for the node.
3.2.5.5 Network Synchronization on T1/E1 Ports and Circuits
Each T1/E1 port can be independently configured for loop-timing (recovered from an
Rx line) or node-timing (recovered from the SSU in the active CSM).
In addition, T1/E1 CES circuits on the following can be independently configured for
adaptive timing (clocking is derived from incoming TDM pseudowire packets):
• 16-port T1/E1 ASAP Adapter card
• 32-port T1/E1 ASAP Adapter card
• 7705 SAR-M (variants with T1/E1 ports)
• 7705 SAR-X
• 7705 SAR-A (variant with T1/E1 ports)
• T1/E1 ports on the 4-port T1/E1 and RS-232 Combination module
T1/E1 CES circuits on the following can be independently configured for differential
timing (recovered from RTP in TDM pseudowire packets):
• 16-port T1/E1 ASAP Adapter card, version 2
• 32-port T1/E1 ASAP Adapter card
• 4-port OC3/STM1 / 1-port OC12/STM4 Adapter card (DS1/E1 channels)
80
3HE 11011 AAAC TQZZA Edition: 01
Page 81
Interface Configuration Guide 7705 SAR Interfaces
• 4-port DS3/E3 Adapter card (DS1/E1 channels on DS3 ports; E3 ports cannot
be channelized); differential timing on DS1/E1 channels is supported only on the
first three ports of the card
• 7705 SAR-M (variants with T1/E1 ports)
• 7705 SAR-X
• 7705 SAR-A (variant with T1/E1 ports)
• T1/E1 ports on the 4-port T1/E1 and RS-232 Combination module
A T1/E1 port can be configured to be a timing source for the node.
Note: Adaptive timing and differential timing are not supported on DS1 or E1 channels that
have CAS signaling enabled.
3.2.6 Node Synchronization From GNSS Receiver Ports
The GNSS receiver port on the 7705 SAR-Ax, 7705 SAR-Wx, and 7705 SAR-H GPS
Receiver module, and the GNSS Receiver card installed in a 7705 SAR-8 or
7705 SAR-18, can provide a synchronization clock to the SSU in the router with the
corresponding QL for SSM. This frequency can then be distributed to the rest of the
router from the SSU as configured with the ref-order and ql-selection commands;
refer to the 7705 SAR Basic System Configuration Guide for information. The GNSS
reference is qualified only if the GNSS receiver port is operational, has sufficient
satellites locked, and has a frequency successfully recovered. A PTP
master/boundary clock can also use this frequency reference with PTP peers.
In the event of GNSS signal loss or jamming resulting in the unavailability of timing
information, the GNSS receiver automatically prevents output of clock or
synchronization data to the system, and the system can revert to alternate timing
sources.
A 7705 SAR using GNSS or IEEE 1588v2 PTP for time of day/phase recovery can
perform high-accuracy OAM timestamping and measurements. Refer to the
7705 SAR Basic System Configuration Guide for information about node timing
sources.
Edition: 01 3HE 11011 AAAC TQZZA 81
Page 82
7705 SAR Interfaces
3.2.7 Flow Control on Ethernet Ports
Interface Configuration Guide
IEEE 802.3x Flow Control, which is the process of pausing the transmission based
on received pause frames, is supported on Fast Ethernet, Gigabit Ethernet, and
10-Gigabit Ethernet (SFP+) ports. In the transmit direction, the Ethernet ports
generate pause frames if the buffer occupancy reaches critical values or if port FIFO
buffers are overloaded. Pause frame generation is automatically handled by the
Ethernet Adapter card when the system-wide constant thresholds are exceeded. The
generation of pause frames ensures that newly arriving frames still can be processed
and queued, mainly to maintain the SLA agreements.
If autonegotiation is on for an Ethernet port, enabling and disabling of IEEE 802.3x
Flow Control is autonegotiated for receive and transmit directions separately. If
autonegotiation is turned off, the reception and transmission of IEEE 802.3x Flow
Control is enabled by default and cannot be disabled.
Ingress flow control for the 6-port SAR-M Ethernet module is Ethernet link-based and
not port-based. When IEEE 802.3x Flow Control is enabled on the 6-port SAR-M
Ethernet module, pause frames are multicast to all ports on the Ethernet link. There
are two Ethernet links on the 6-port SAR-M Ethernet module: one for ports 1, 3, and
5, and one for ports 2, 4, and 6. Pause frames are sent to either ports 1, 3, and 5, or
to ports 2, 4, and 6, depending on which link the pause frame originates.
3.2.8 Ethernet OAM
This section contains information on the following topics:
• Ethernet OAM Overview
• CRC (Cyclic Redundancy Check) Monitoring
• Remote Loopback
• 802.3ah OAMPDU Tunneling and Termination for Epipe Service
• Dying Gasp
82
3HE 11011 AAAC TQZZA Edition: 01
Page 83
Interface Configuration Guide 7705 SAR Interfaces
3.2.8.1 Ethernet OAM Overview
802.3ah Clause 57 (EFM OAM) defines the Operations, Administration, and
Maintenance (OAM) sublayer, which is a link level Ethernet OAM that is supported
on 7705 SAR Ethernet ports and DSL ports configured as network or access ports.
It provides mechanisms for monitoring link operations such as remote fault indication
and remote loopback control. EFM OAM is not supported on the 7705 SAR-M GPON
module.
Ethernet OAM gives network operators the ability to monitor the status of Ethernet
links and quickly determine the location of failing links or fault conditions.
Because some of the sites where the 7705 SAR will be deployed will only have
Ethernet uplinks, this OAM functionality is mandatory. For example, mobile operators
must be able to request remote loopbacks from the peer router at the Ethernet layer
in order to debug any connectivity issues. EFM OAM provides this capability.
EFM OAM is supported on network and access Ethernet and DSL ports, and is
configured at the port level. The access ports can be configured to tunnel the OAM
traffic originated by the far-end devices.
EFM OAM has the following characteristics.
• All EFM OAM, including loopbacks, operate on point-to-point links only.
• EFM loopbacks are always line loopbacks (line Rx to line Tx). Line loopbacks
are not supported on DSL ports.
• When a port is in loopback, all frames (except EFM frames) are discarded. If
dynamic signaling and routing is used (dynamic LSPs, OSPF, IS-IS, or BGP
routing), all services also go down. If all signaling and routing protocols are static
(static routes, LSPs, and service labels), the frames are discarded but services
stay up.
The following EFM OAM functions are supported:
• OAM capability discovery
• configurable transmit interval with an Information OAMPDU
• active or passive mode
• OAM loopback
• OAMPDU tunneling and termination (for Epipe service)
• dying gasp at network and access ports
For information on Epipe service, refer to the 7705 SAR Services Guide, “Ethernet
VLL (Epipe) Services”, and the 7705 SAR OAM and Diagnostics Guide, “Ethernet
OAM Capabilities”.
Edition: 01 3HE 11011 AAAC TQZZA 83
Page 84
7705 SAR Interfaces
3.2.8.2 CRC (Cyclic Redundancy Check) Monitoring
Interface Configuration Guide
CRC errors typically occur when Ethernet links are compromised due to optical fiber
degradation, weak optical signals, bad optical connections, or problems on a
third-party networking element. As well, higher-layer OAM options such as EFM and
BFD may not detect errors and trigger appropriate alarms and switchovers if the
errors are intermittent, since this does not affect the continuous operation of other
OAM functions.
CRC error monitoring on Ethernet ports allows degraded links to be alarmed or failed
in order to detect network infrastructure issues, trigger necessary maintenance, or
switch to redundant paths. This is achieved through monitoring ingress error counts
and comparing them to the configured error thresholds. The rate at which CRC errors
are detected on a port can trigger two alarm states. Crossing the configured signal
degrade (SD) threshold (sd-threshold) causes an event to be logged and an alarm
to be raised, which alerts the operator to a potential issue on a link. Crossing the
configured signal failure (SF) threshold (sf-threshold) causes the affected port to
enter the operationally down state, and causes an event to be logged and an alarm
to be raised.
The CRC error rates are calculated as M×10E-N, which is the ratio of errored frames
allowed for total frames received. The operator can configure both the threshold (N)
and a multiplier (M). If the multiplier is not configured, the default multiplier (1) is
used. For example, setting the SD threshold to 3 results in a signal degrade error rate
threshold of 1×10E-3 (1 errored frame per 1000 frames). Changing the configuration
to an SD threshold of 3 and a multiplier of 5 results in a signal degrade error rate
threshold of 5×10E-3 (5 errored frames per 1000 frames). The signal degrade error
rate threshold must be lower than the signal failure error rate threshold because it is
used to notify the operator that the port is operating in a degraded but not failed
condition.
A sliding window (window-size) is used to calculate a statistical average of CRC
error statistics collected every second. Each second, the oldest statistics are
dropped from the calculation. For example, if the default 10-s sliding window is
configured, at the 11th second the oldest second of statistical data is dropped and
the 11th second is included. This sliding average is compared against the configured
SD and SF thresholds to determine if the error rate over the window exceeds one or
both of the thresholds, which will generate an alarm and log event.
84
3HE 11011 AAAC TQZZA Edition: 01
Page 85
Interface Configuration Guide 7705 SAR Interfaces
When a port enters the failed condition as a result of crossing an SF threshold, the
port is not automatically returned to service. Because the port is operationally down
without a physical link, error monitoring stops. The operator can enable the port by
using the shutdown and no shutdown port commands or by using other port
transition functions such as clearing the MDA (clear mda command) or removing the
cable. A port that is down due to crossing an SF threshold can also be re-enabled by
changing or disabling the SD threshold. The SD state is self-clearing, and it clears if
the error rate drops below 1/10th of the configured SD rate.
Note: CRC monitoring is not supported on GPON or DSL ports.
3.2.8.3 Remote Loopback
EFM OAM provides a link-layer frame loopback mode, which can be controlled
remotely.
To initiate a remote loopback, the local EFM OAM client sends a loopback control
OAMPDU by enabling the OAM remote loopback command. After receiving the
loopback control OAMPDU, the remote OAM client puts the remote port into local
loopback mode.
OAMPDUs are slow protocol frames that contain appropriate control and status
information used to monitor, test, and troubleshoot OAM-enabled links.
To exit a remote loopback, the local EFM OAM client sends a loopback control
OAMPDU by disabling the OAM remote loopback command. After receiving the
loopback control OAMPDU, the remote OAM client puts the port back into normal
forwarding mode.
When a port is in local loopback mode (the far end requested an Ethernet OAM
loopback), any packets received on the port will be looped back, except for EFM
OAMPDUs. No data will be transmitted from the node; only data that is received on
the node will be sent back out.
When the node is in remote loopback mode, local data from the CSM is transmitted,
but any data received on the node is dropped, except for EFM OAMPDUs.
Remote loopbacks should be used with caution; if dynamic signaling and routing
protocols are used, all services go down when a remote loopback is initiated. If only
static signaling and routing is used, the services stay up. On the 7705 SAR, the
Ethernet port can be configured to accept or reject the remote-loopback command.
Edition: 01 3HE 11011 AAAC TQZZA 85
Page 86
7705 SAR Interfaces
Metro Ethernet
NW
20479
7705 SAR
MEN
BSC
7750 SR
A
Ports
BCDEFGHIJKL
BTS
MEN
1
3
2
3.2.8.4 802.3ah OAMPDU Tunneling and Termination for Epipe
Interface Configuration Guide
Service
Customers who subscribe to Epipe service might have customer equipment running
802.3ah at both ends. The 7705 SAR can be configured to tunnel EFM OAMPDUs
received from a customer device to the other end through the existing network using
MPLS or GRE, or to terminate received OAMPDUs at a network or an access
Ethernet port.
Note: This feature applies only to port-based Epipe SAPs because 802.3ah runs at port
level, not at VLAN level.
While tunneling offers the ability to terminate and process the OAM messages at the
head-end, termination on the first access port at the cell site can be used to detect
immediate failures or can be used to detect port failures in a timelier manner. The
user can choose either tunneling or termination, but not both at the same time.
In Figure 6, scenario 1 shows the termination of received EFM OAMPDUs from a
customer device on an access port, while scenario 2 shows the same thing except
for a network port. Scenario 3 shows tunneling of EFM OAMPDUs through the
associated Ethernet PW. To configure termination (scenario 1), use the
config>port>ethernet>efm-oam>no shutdown command.
Figure 6 EFM Capability on the 7705 SAR
86
3HE 11011 AAAC TQZZA Edition: 01
Page 87
Interface Configuration Guide 7705 SAR Interfaces
3.2.8.5 Dying Gasp
Dying gasp is used to notify the far end that EFM-OAM is disabled or shut down on
the local port. The dying gasp flag is set on the OAMPDUs that are sent to the peer.
The far end can then take immediate action and inform upper layers that EFM-OAM
is down on the port.
When a dying gasp is received from a peer, the node logs the event and generates
an SNMP trap to notify the operator.
3.2.9 Ethernet Loopbacks
This section contains information on the following topics:
• Line and Internal Ethernet Loopbacks
• CFM Loopbacks for OAM on Ethernet Ports
Table 10 lists the loopbacks supported on Ethernet, DSL module (6-port DSL
Combination module and 8-port xDSL module), and GPON module ports.
Table 10 Loopbacks Supported on Ethernet, DSL, and GPON Ports
Loopback
Ethernet DSL GPON
Timed network line loopback ✓✓
Timed and untimed access line loopbacks ✓✓
Timed and untimed access internal
loopbacks
Persistent access line loopback ✓
Persistent access internal loopback ✓
MAC address swapping ✓
CFM loopback on network and access
ports
CFM loopback on ring ports and v-port ✓
✓✓✓
✓✓✓
Edition: 01 3HE 11011 AAAC TQZZA 87
Page 88
7705 SAR Interfaces
3.2.9.1 Line and Internal Ethernet Loopbacks
Interface Configuration Guide
A line loopback loops frames received on the corresponding port back towards the
transmit direction. Line loopbacks are supported on ports configured for access or
network mode.
Similarly, a line loopback with MAC addressing loops frames received on the
corresponding port back towards the transmit direction, and swaps the source and
destination MAC addresses before transmission. See MAC Swapping for more
information.
An internal loopback loops frames from the local router back to the framer. This is
usually referred to as an equipment loopback. The transmit signal is looped back and
received by the interface. Internal loopbacks are supported on ports configured in
access mode.
If a loopback is enabled on a port, the port mode cannot be changed until the
loopback has been disabled.
A port can support only one loopback at a time. If a loopback exists on a port, it must
be disabled or the timer must expire before another loopback can be configured on
the same port. EFM-OAM cannot be enabled on a port that has an Ethernet loopback
enabled on it. Similarly, an Ethernet loopback cannot be enabled on a port that has
EFM-OAM enabled on it.
When an internal loopback is enabled on a port, autonegotiation is turned off silently.
This is to allow an internal loopback when the operational status of a port is down.
Any user modification to autonegotiation on a port configured with an internal
Ethernet loopback will not take effect until the loopback is disabled.
The loopback timer can be configured from 30 s to 86400 s. All non-zero timed
loopbacks are turned off automatically under the following conditions: an adapter
card reset, DSL module reset, GPON module reset, an activity switch, or timer
expiry. Line or internal loopback timers can also be configured as a latched loopback
by setting the timer to 0 s, or as a persistent loopback with the persistent keyword.
Latched and persistent loopbacks are enabled indefinitely until turned off by the user.
Latched loopbacks survive adapter card resets and activity switches, but are lost if
there is a system restart. Persistent loopbacks survive adapter card resets and
activity switches and can survive a system restart if the admin-save or
admin-save-detail command was executed prior to the restart. Latched loopbacks
(untimed) and persistent loopbacks can be enabled only on Ethernet access ports.
88
Persistent loopbacks are the only Ethernet loopbacks saved to the database by the
admin-save and admin-save-detail commands.
3HE 11011 AAAC TQZZA Edition: 01
Page 89
Interface Configuration Guide 7705 SAR Interfaces
An Ethernet port loopback may interact with other features. See Interaction of
Ethernet Port Loopback with Other Features for more information.
3.2.9.1.1 MAC Swapping
Typically, an Ethernet port loopback only echoes back received frames. That is, the
received source and destination MAC addresses are not swapped. However, not all
Ethernet equipment supports echo mode, where the original sender of the frame
must support receiving its own port MAC address as the destination MAC address.
The MAC swapping feature on the 7705 SAR is an optional feature that will swap the
received destination MAC address with the source MAC address when an Ethernet
port is in loopback mode. After the swap, the FCS is recalculated to ensure the
validity of the Ethernet frame and to ensure that the frame is not dropped by the
original sender due to a CRC error.
MAC swapping is not supported on the GPON module, 6-port DSL Combination
module, or 8-port xDSL module.
3.2.9.1.2 Interaction of Ethernet Port Loopback with Other Features
EFM OAM and line loopback are mutually exclusive. If one of these functions is
enabled, it must be disabled before the other can be used.
However, a line loopback precedes the dot1x behavior. That is, if the port is already
dot1x-authenticated it will remain so. If it is not, EAP authentication will fail.
Ethernet port-layer line loopback and Ethernet port-layer internal loopback can be
enabled on the same port with the down-when-looped feature. EFM OAM cannot be
enabled on the same port with the down-when-looped feature. For more information,
see Ethernet Port Down-When-Looped.
3.2.9.2 CFM Loopbacks for OAM on Ethernet Ports
This section contains information on the following topics:
• CFM Loopback Overview
• CFM Loopback Mechanics
Edition: 01 3HE 11011 AAAC TQZZA 89
Page 90
7705 SAR Interfaces
3.2.9.2.1 CFM Loopback Overview
Interface Configuration Guide
Connectivity fault management (CFM) loopback support for loopback messages
(LBMs) on Ethernet ports allows operators to run standards-based Layer 1 and Layer
2 OAM tests on ports receiving unlabeled packets.
The 7705 SAR supports CFM MEPs associated with different endpoints (that is,
spoke SDP Down MEPs, network interface facility MEPs, and SAP Up and SAP
Down MEPs). In addition, for traffic received from an uplink (network ingress), the
7705 SAR supports CFM LBM for both labeled and unlabeled packets. CFM
loopbacks are applied to the Ethernet port.
Refer to the 7705 SAR OAM and Diagnostics Guide, “Ethernet OAM Capabilities”,
for information on CFM MEPs.
Figure 7 shows an application where an operator leases facilities from a transport
network provider in order to transport traffic from a cell site to their MTSO. The
operator leases a certain amount of bandwidth between the two endpoints (the cell
site and the MTSO) from the transport provider, who offers Ethernet Virtual Private
Line (EVPL) or Ethernet Private Line (EPL) PTP service. Before the operator offers
services on the leased bandwidth, the operator runs OAM tests to verify the SLA.
Typically, the transport provider (MEN provider) requires that the OAM tests be run
in the direction of (towards) the first Ethernet port that is connected to the transport
network. This is done in order to eliminate the potential effect of queuing, delay, and
jitter that may be introduced by a spoke SDP or SAP.
90
3HE 11011 AAAC TQZZA Edition: 01
Page 91
Interface Configuration Guide 7705 SAR Interfaces
Metro Ethernet
NW
21212
DO, LTE
1x
Ethernet
EVPL
Cell Site
MTSO
Ethernet
nxT1
7705 SAR
Ethernet
Verifier
DSC
2
1
7750 SR
DA=SAR1 SA=Verif LBM
LBM 2SA=SAR DA=Verif
DO = Evolution Data Only
LTE = Long Term Evolution
EVPL = Ethernet Virtual Private Line
DSC = Digital Cross-Connect
DA = Destination MAC Address
SA = Source MAC Address
LBM = Loopback Message
Legend:
Figure 7 CFM Loopback on Ethernet Ports
Edition: 01 3HE 11011 AAAC TQZZA 91
3.2.9.2.2 CFM Loopback Mechanics
Figure 7 shows an Ethernet verifier at the MTSO that is directly connected to the
transport network (in front of the 7750 SR). Thus, the Ethernet OAM frames are not
label-encapsulated. Given that Ethernet verifiers do not support label operations and
the transport provider mandates that OAM tests be run between the two hand-off
Ethernet ports, the verifier cannot be relocated behind the 7750 SR node at the
MTSO. Therefore, CFM loopback frames received are not MPLS-encapsulated, but
are simple Ethernet frames where the type is set to CFM (dot1ag or Y.1731).
The following list contains important facts to consider when working with CFM
loopbacks:
• CFM loopbacks can be enabled on a per-port basis, and:
− the port can be in access or network mode
− once enabled on a port, all received LBM frames are processed, regardless
of the VLAN and the service that the VLAN or SAP is bound to
Page 92
7705 SAR Interfaces
Interface Configuration Guide
− there is no associated MEP creation involved with this feature; therefore, no
domain, association, or similar checks are performed on the received frame
− upon finding a destination address MAC match, the LBM frame is sent to
the CFM process
• CFM loopback support on a physical ring port on the 2-port 10GigE (Ethernet)
Adapter card or 2-port 10GigE (Ethernet) module differs from other Ethernet
ports. For these ports, cfm-loopback is configured, optionally, using dot1p and
match-vlan to create a list of up to 16 VLANs. The null VLAN is always applied.
The CFM Loopback Message will be processed if it does not contain a VLAN
header, or if it contains a VLAN header with a VLAN ID that matches one in the
configured match-vlan list.
• received LBM frames undergo no queuing or scheduling in the ingress direction
• at egress, loopback reply (LBR) frames are stored in their own queue; that is, a
separate new queue is added exclusively for LBR frames
• users can configure the way a response frame is treated among other user traffic
stored in network queues; the configuration options are high-priority, low-priority,
or dot1p, where dot1p applies only to physical ring ports
• for network egress, where profiled scheduling is enabled, the following
conditions apply:
− high-priority: either cir = port_speed, which applies to all frames that are
scheduled via an in-profile scheduler; or round-robin (RR) for all other
(network egress queue) frames that are in-profile
− low-priority: either cir = 0, pir = port_speed, which applies to all frames that
are scheduled as out-of-profile, or RR for all other frames that are
out-of-profile
• for network egress or access egress, where 4-priority scheduling is enabled:
− high-priority: either cir = port_speed, which applies to all frames that are
scheduled via an expedited in-profile scheduler, or RR for all other (network
egress queue) frames that reside in expedited queues and are in an
in-profile state
− low-priority: either cir = 0, pir = port_speed, which applies to all frames that
are scheduled via a best effort out-of-profile scheduler, or RR for all other
frames that reside in best-effort queues and are in an out-of-profile state
• for the 8-port Gigabit Ethernet Adapter card, the 10-port 1GigE/1-port 10GigE
X-Adapter card, and the v-port on the 2-port 10GigE (Ethernet) Adapter card and
2-port 10GigE (Ethernet) module, for network egress, where 16-priority
scheduling is enabled:
− high-priority: has higher priority than any user frames
− low-priority: has lower priority than any user frames
92
3HE 11011 AAAC TQZZA Edition: 01
Page 93
Interface Configuration Guide 7705 SAR Interfaces
• for the physical ring ports on the 2-port 10GigE (Ethernet) Adapter card and
2-port 10GigE (Ethernet) module, which can only operate as network egress, the
priority of the LBR frame is derived from the dot1p setting of the received LBM
frame. Based on the assigned ring-type network queue policy, dot1p-to-queue
mapping is handled using the same mapping rule that applies to all other user
frames.
• the above queue parameters and scheduler mappings are all preconfigured and
cannot be altered. The desired QoS treatment is selected by enabling the CFM
loopback and specifying high-priority, low-priority, or dot1p.
3.2.10 Ethernet Port Down-When-Looped
Newly provisioned circuits are often put into loopback with a physical loopback cable
for testing and to ensure the ports meet the SLA. If loopbacks are not cleared, or
physically removed, by the operator when the testing is completed, they can
adversely affect the performance of all other SDPs and customer interfaces (SAPs).
This is especially problematic for point-to-multipoint services such as VPLS, since
Ethernet does not support TTL, which is essential in terminating loops.
The down-when-looped feature is used on the 7705 SAR to detect loops within the
network and to ensure continued operation of other ports. When the
down-when-looped feature is activated, a keepalive loop PDU is transmitted
periodically toward the network. The Ethernet port then listens for returning keepalive
loop PDUs. In unicast mode, a loop is detected if any of the received PDUs have an
Ethertype value of 9000, which indicates a loopback (Configuration Test Protocol),
and the source (SRC) and destination (DST) MAC addresses are identical to the
MAC address of the Ethernet port. In broadcast mode, a loop is detected if any of the
received PDUs have an Ethertype value of 9000 and the SRC MAC address matches
the MAC address of the Ethernet port and the DST MAC address matches the
broadcast MAC address. When a loop is detected, the Ethernet port is immediately
brought down. Down-when-looped is supported on Ethernet ports, DSL module
ports, and GPON module ports.
Ethernet port-layer line loopbacks and the down-when-looped feature can be
enabled on the same port. The keepalive loop PDU is still transmitted; however, if the
port receives its own keepalive loop PDU, the keepalive PDU is extracted and
processed to avoid infinite looping.
Edition: 01 3HE 11011 AAAC TQZZA 93
Page 94
7705 SAR Interfaces
3.2.11 Ethernet Ring (Adapter Card and Module)
Interface Configuration Guide
Ethernet port-layer internal loopbacks and the down-when-looped feature can also
be enabled on the same port. When the keepalive PDU is internally looped back, it
is extracted and processed as usual. If the SRC MAC address matches the port MAC
address, the port is disabled due to detection of a loop. If the SRC MAC address is
a broadcast MAC address because the swap-src-dst-mac option in the loopback
command is enabled, then there is no change to port status and it remains
operationally up.
EFM OAM and down-when-looped cannot be enabled on the same port.
The 2-port 10GigE (Ethernet) Adapter card can be installed in a 7705 SAR-8 or
7705 SAR-18 chassis and the 2-port 10GigE (Ethernet) module can be installed in a
7705 SAR-M to connect to and from access rings carrying a high concentration of
traffic. For the maximum number of cards or modules supported per chassis, see
Table 3.
A number of 7705 SAR nodes in a ring typically aggregate traffic from customer sites,
map the traffic to a service, and connect to an SR node. The SR node acts as a
gateway point out of the ring. A 10GigE ring allows for higher bandwidth services and
aggregation on a per-7705 SAR basis. The 2-port 10GigE (Ethernet) Adapter
card/module increases the capacity of backhaul networks by providing 10GigE
support on the aggregation nodes, thus increasing the port capacity.
In a deployment of a 2-port 10GigE (Ethernet) Adapter card/module, each 7705 SAR
node in the ring is connected to the east and west side of the ring over two different
10GigE ports. If 10GigE is the main uplink, the following are required for redundancy:
• two cards per 7705 SAR-8
• two cards per 7705 SAR-18
• two 7705 SAR-M nodes, each equipped with 2-port 10GigE (Ethernet) module
With two cards per 7705 SAR-8 or 7705 SAR-18 node, for example, east and west
links of the ring can be terminated on two different adapter cards, reducing the impact
of potential hardware failure.
The physical ports on the 2-port 10GigE (Ethernet) Adapter card/module boot up in
network mode and this network setting cannot be disabled or altered. At boot-up, the
MAC address of the virtual port (v-port) is programmed automatically for efficiency
and security reasons.
94
3HE 11011 AAAC TQZZA Edition: 01
Page 95
Interface Configuration Guide 7705 SAR Interfaces
There is native built-in Ethernet bridging among the ring ports and the v-port.
Bridging destinations for traffic received from one of the ring ports include the 10GigE
ring port and the network interfaces on the v-port. Bridging destinations for traffic
received from the v-port include one or both of the 10GigE ring ports.
With bridging, broadcast and multicast frames are forwarded over all ports except the
received one. Unknown frames are forwarded to both 10GigE ports if received from
the v-port or forwarded to the other 10GigE port only if received from one of the
10GigE ports (the local v-port MAC address is always programmed).
The bridge traffic of the physical 10GigE ports is based on learned and programmed
MAC addresses.
3.2.12 MTU Configuration Guidelines
This section contains information on the following topics:
• MTU Configuration Overview
• IP Fragmentation
• Jumbo Frames
• Default Port MTU Values
3.2.12.1 MTU Configuration Overview
Because of the services overhead (that is, pseudowire/VLL, MPLS tunnel,
dot1q/qinq and dot1p overhead), it is crucial that configurable variable frame size be
supported for end-to-end service delivery.
Observe the following general rules when planning your service and physical
Maximum Transmission Unit (MTU) configurations.
• The 7705 SAR must contend with MTU limitations at many service points. The
physical (access and network) port, service, and SDP MTU values must be
individually defined. Figure 8 identifies the various MTU points on the
7705 SAR.
• The ports that will be designated as network ports intended to carry service
traffic must be identified.
• MTU values should not be modified frequently.
• MTU values must conform to both of the following conditions:
− the service MTU must be less than or equal to the SDP path MTU
Edition: 01 3HE 11011 AAAC TQZZA 95
Page 96
7705 SAR Interfaces
19688
NP
SAP
NP
SDP
Access Port MTU
SAP MTU
Service MTU
3
Network Port MTU
5
Path MTU
4
1
2
Ingress Line
Card
Network Egress
Line Card
Fabric
Access Network
Interface Configuration Guide
− the service MTU must be less than or equal to the access port (SAP) MTU
• When the allow-fragmentation command is enabled on an SDP, the current
MTU algorithm is overwritten with the configured path MTU. The administrative
MTU and operational MTU both show the specified MTU value. If the path MTU
is not configured or available, the operational MTU is set to 2000 bytes, and the
administrative MTU displays a value of 0. When allow-fragmentation is
disabled, the operational MTU reverts to the previous value.
For more information, refer to the “MTU Settings” section in the 7705 SAR Services
Guide. To configure various MTU points, use the following commands:
• port MTUs are set with the mtu command, under the config>port context,
where the port type can be Ethernet, DSL, GPON, TDM, serial, or SONET/SDH
• service MTUs are set in the appropriate config>service context
• path MTUs are set with the path-mtu command under the config>service>sdp
context
Figure 8 MTU Points on the 7705 SAR
Frame size configuration is supported for an Ethernet port configured as an access
or a network port.
For an Ethernet adapter card that does not support jumbo frames, all frames
received at an ingress network or access port are policed against 1576 bytes (1572
+ 4 bytes of FCS), regardless of the port MTU. Any frames longer than 1576 bytes
are discarded and the “Too Long Frame” and “Error Stats” counters in the port
statistics display are incremented. See Jumbo Frames for more information.
At network egress, Ethernet frames are policed against the configured port MTU. If
96
the frame exceeds the configured port MTU, the “Interface Out Discards” counter in
the port statistics is incremented.
3HE 11011 AAAC TQZZA Edition: 01
Page 97
Interface Configuration Guide 7705 SAR Interfaces
When the network group encryption (NGE) feature is used, additional bytes due to
NGE packet overhead must be considered. Refer to the “NGE Packet Overhead and
MTU Considerations” section in the 7705 SAR Services Guide for more information.
3.2.12.2 IP Fragmentation
IP fragmentation is used to fragment a packet that is larger than the MTU of the
egress interface, so that the packet can be transported over that interface.
For IPv4, the router fragments or discards the IP packets based on whether the DF
(Do not fragment) bit is set in the IP header. If the packet that exceeds the MTU
cannot be fragmented, the packet is discarded and an ICMP message
“Fragmentation Needed and Don’t Fragment was Set” is sent back to the source IP
address.
For IPv6, the router cannot fragment the packet so must discard it. An ICMP
message “Packet too big” is sent back to the source node.
As a source of self-generated traffic, the 7705 SAR can perform packet
fragmentation.
Fragmentation can be enabled for GRE tunnels. Refer to the “GRE Fragmentation”
section in the 7705 SAR Services Guide for more information.
3.2.12.3 Jumbo Frames
Jumbo frames are supported on Ethernet ports except on the 8-port Ethernet
Adapter card (version 1).
The maximum MTU size for a jumbo frame on the 7705 SAR is 9732 bytes. The
maximum MTU for a jumbo frame may vary depending on the Ethernet
encapsulation type, as shown in Table 11. The calculations of the other MTU values
(service MTU, path MTU, and so on) are based on the port MTU. The values in
Table 11 are also maximum receive unit (MRU) values. MTU values are
user-configured values. MRU values are the maximum MTU value that a user can
configure on an adapter card that supports jumbo frames.
Table 11 Maximum MTU (or MRU) per Ethernet Encapsulation Type
Encapsulation Maximum MTU (bytes)
Null 9724
Edition: 01 3HE 11011 AAAC TQZZA 97
Page 98
7705 SAR Interfaces
Interface Configuration Guide
Table 11 Maximum MTU (or MRU) per Ethernet Encapsulation Type
Encapsulation Maximum MTU (bytes)
Dot1q 9728
QinQ 9732
For an Ethernet Adapter card, all frames received at an ingress network or access
port are policed against the MRU for the ingress adapter card, regardless of the
configured MTU. Any frames larger than the MRU are discarded and the “Too Long
Frame” and “Error Stats” counters in the port statistics display are incremented.
At network egress, frames are checked against the configured port MTU. If the frame
exceeds the configured port MTU and the DF bit is set, then the “MTU Exceeded”
discard counter will be incremented on the ingress IP interface statistics display, or
on the MPLS interface statistics display if the packet is an MPLS packet.
For example, on adapter cards that do not support an MTU greater than 2106 bytes,
fragmentation is not supported for frames greater than the maximum supported MTU
for that card (that is, 2106 bytes). If the maximum supported MTU is exceeded, the
following occurs.
• An appropriate ICMP reply message (Destination Unreachable) is generated by
the 7705 SAR. The router ensures that the ICMP generated message cannot be
used as a DOS attack (that is, the router paces the ICMP message).
• The appropriate statistics are incremented.
Jumbo frames offer better utilization of an Ethernet link because as more payload is
packed into an Ethernet frame of constant size, the ratio of overhead to payload is
minimized.
From the traffic management perspective, large payloads may cause long delays, so
a balance between link utilization and delay must be found. For example, for ATM
VLLs, concatenating a large number of ATM cells when the MTU is set to a very high
value could generate a 9-kbyte ATM VLL frame. Transmitting a frame that large
would take more than 23 ms on a 3-Mb/s policed Ethernet uplink.
98
3HE 11011 AAAC TQZZA Edition: 01
Page 99
Interface Configuration Guide 7705 SAR Interfaces
3.2.12.3.1 Behavior of Adapter Cards Not Supporting Jumbo Frames on
7705 SAR-8 and 7705 SAR-18 only
The 7705 SAR-8 (with CSMv2) and the 7705 SAR-18 do not support ingress
fragmentation, and this is true for jumbo frames. Therefore, any jumbo frame packet
arriving on one of these routers that gets routed to an adapter card that does not
support jumbo frame MTU (for example, a 16-port T1/E1 ASAP Adapter card or a
4-port OC3/STM1 / 1-port OC12/STM4 Adapter card) is discarded if the packet size
is greater than the TDM port’s maximum supported MTU. If the maximum-supported
MTU is exceeded, the following occurs.
• An appropriate ICMP reply message (Destination Unreachable) is generated by
the 7705 SAR. The router ensures that the ICMP-generated message cannot be
used as a DOS attack (that is, the router paces the ICMP message).
• The port statistics show IP or MPLS Interface MTU discards, for IP or MPLS
traffic, respectively. MTU Exceeded Packets and Bytes counters exist
separately for IPv4/6 and MPLS under the IP interface hierarchy for all discarded
packets where ICMP Error messages are not generated.
For example, if a packet arrives on an 8-port Gigabit Ethernet Adapter card and is to
be forwarded to a 16-port T1/E1 ASAP Adapter card with a maximum port MTU of
2090 bytes and a channel group configured for PPP with the port MTU of 1000 bytes,
the following may occur.
• If the arriving packet is 800 bytes, then forward the packet.
• If the arriving packet is 1400 bytes, then forward the packet, which will be
fragmented by the egress adapter card.
• If the arriving packet is fragmented and the fragments are 800 bytes, then
forward the packet.
• If the arriving packet is 2500 bytes, then send an ICMP error message (because
the egress adapter card has a maximum port MTU of 2090 bytes).
• If the arriving packet is fragmented and the fragment size is 2500 bytes, then
there is an ICMP error.
3.2.12.3.2 Jumbo Frame Behavior on the Fixed Platforms
The 7705 SAR-A, 7705 SAR-Ax, 7705 SAR-H, 7705 SAR-Hc, 7705 SAR-M,
7705 SAR-W, 7705 SAR-Wx, and 7705 SAR-X are able to fragment packets
between Ethernet ports (which support jumbo frames) and TDM ports (which do not
support jumbo frames). In this case, when a packet arrives from a port that supports
jumbo frames and is routed to a port that does not support jumbo frames (that is, a
TDM port) the packet will get fragmented to the port MTU of the TDM port.
Edition: 01 3HE 11011 AAAC TQZZA 99
Page 100
7705 SAR Interfaces
3.2.12.3.3 Multicast Support for Jumbo Frames
Interface Configuration Guide
For example, if a packet arrives on a 7705 SAR-A and is to be forwarded to a TDM
port that has a maximum port MTU of 2090 bytes and a channel group configured for
PPP with the port MTU of 1000 bytes (PPP port MTU), the following may occur.
• If the arriving packet is 800 bytes, then forward the packet.
• If the arriving packet is 1400 bytes and the DF bit is 0, then forward the packet,
which will be fragmented to the PPP port MTU size.
• If the arriving packet is 2500 bytes and the DF bit is 0, then forward the packet,
which will be fragmented to the PPP port MTU size.
Jumbo frames are supported in a multicast configuration as long as all adapter cards
in the multicast group support jumbo frames. If an adapter card that does not support
jumbo frames is present in the multicast group, the replicated multicast jumbo frame
packet will be discarded by the fabric because of an MRU error of the fabric port (RX).
The multicast group replicates the jumbo frame for all adapter cards, regardless of
whether they support jumbo frames, only when forwarding the packet through the
fabric. The replicated jumbo frame packet is discarded on adapter cards that do not
support jumbo frames.
3.2.12.3.4 PMC Jumbo Frame Support
For the Packet Microwave Adapter card (PMC), ensure that the microwave hardware
installed with the card supports the corresponding jumbo frame MTU. If the
microwave hardware does not support the jumbo frame MTU, it is recommended that
the MTU of the PMC port be set to the maximum frame size that is supported by the
microwave hardware.
3.2.12.4 Default Port MTU Values
Table 12 displays the default and maximum port MTU values that are dependent
upon the port type, mode, and encapsulation type.
Note: The 7705 SAR now supports a lower IP MTU value of 128 bytes (from the original
512-byte minimum). The IP MTU is derived from the port MTU configuration for network
ports. This lower IP MTU is supported only on Ethernet encapsulated ports. Refer to the
7705 SAR Services Guide, “Bandwidth Optimization for Low-speed Links” for information.
100
3HE 11011 AAAC TQZZA Edition: 01
Loading...