Download Print this page

Nokia 7450 ESS Interface Configuration Manual

Ethernet service switch, service router, extensible routing system, virtualized service router.
Hide thumbs
   
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914

Advertisement

INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5
7450 ETHERNET SERVICE SWITCH
7750 SERVICE ROUTER
7950 EXTENSIBLE ROUTING SYSTEM
VIRTUALIZED SERVICE ROUTER
INTERFACE CONFIGURATION GUIDE
RELEASE 15.0.R5
3HE 11968 AAAC TQZZA 01
Issue: 01
September 2017
Nokia — Proprietary and confidential.
Use pursuant to applicable agreements.

Advertisement

Chapters

   Related Manuals for Nokia 7450 ESS

   Summary of Contents for Nokia 7450 ESS

  • Page 1: Issue

    INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 7450 ETHERNET SERVICE SWITCH 7750 SERVICE ROUTER 7950 EXTENSIBLE ROUTING SYSTEM VIRTUALIZED SERVICE ROUTER INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 3HE 11968 AAAC TQZZA 01 Issue: 01 September 2017 Nokia — Proprietary and confidential. Use pursuant to applicable agreements.

  • Page 2

    © 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.

  • Page 3: Table Of Contents

    INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Table of Contents Getting Started ................9 About This Guide..................9 Interface Configuration Process ..............11 Interfaces ..................13 Configuration Overview ................13 2.1.1 Chassis Slots and Cards ................13 2.1.2 MCMs .......................15 2.1.3 MDA-a, MDA-aXP, MDA, MDA-XP and MDA-e Modules......15 2.1.4 XMAs/C-XMAs...................18 2.1.5...

  • Page 4

    INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 2.3.2.15 Ethernet Local Management Interface (E-LMI) ........109 2.3.2.16 Link Layer Discovery Protocol (LLDP).............110 2.3.2.17 Exponential Port Dampening..............114 2.3.3 Per Port Aggregate Egress Queue Statistics Monitoring......117 Port Cross-Connect (PXC) ..............119 2.4.1 PXC Terminology ..................120 2.4.2 PXC - Physical Port in Cross-Connect (Loopback) Mode .......121 2.4.2.1 Operational State..................122 2.4.3...

  • Page 5

    INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 G.8031 Protected Ethernet Tunnels ............172 G.8032 Protected Ethernet Rings............173 Ethernet Port Monitoring .................174 2.10 802.3ah OAM ..................178 2.10.1 OAM Events ....................180 2.10.1.1 Link Monitoring ..................181 2.10.2 Remote Loopback ...................187 2.10.3 802.3ah OAM PDU Tunneling for Epipe Service........188 2.10.3.1 802.3ah Grace Announcement..............188 2.11...

  • Page 6

    INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 2.19.1.9 Forwarding Path Extension (FPE) Commands........279 2.19.1.10 Port APS Commands ................279 2.19.1.11 Ethernet Commands................280 2.19.1.12 Interface Group Handler Commands............288 2.19.1.13 Multilink Bundle Commands ..............288 2.19.1.14 SONET-SDH Commands ................290 2.19.1.15 TDM Commands ..................292 2.19.1.16 DS3 Commands ..................295 2.19.1.17 E1 Commands..................296 2.19.1.18...

  • Page 7

    INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 2.20.1.4 Debug Commands...................633 2.20.1.5 Tools Commands ..................633 2.20.2 Command Descriptions ................634 2.20.2.1 Hardware Show Commands..............635 2.20.2.2 PEQ Show Commands................699 2.20.2.3 APS Show Commands ................706 2.20.2.4 Port Show Commands................710 2.20.2.5 Multilink Bundle Show Commands ............805 2.20.2.6 LAG Show Commands ................825 2.20.2.7 MACsec Show Commands..............836...

  • Page 8

    INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 3HE 11968 AAAC TQZZA 01 Issue: 01...

  • Page 9: Getting Started

    SR OS router. Table 1 Supported SR OS Router Chassis Types 7450 ESS 7750 SR 7950 XRS • 7450 ESS-7/12 running in • 7450 ESS-7/12 running in • 7950 XRS-16c standard mode (not mixed- mixed-mode (not standard • 7950 XRS-20/40...

  • Page 10

    Getting Started INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Note: This guide generically covers Release 15.0.Rx content and may contain some content that will be released in later maintenance loads. Refer to the SR OS R15.0.Rx Software Release Notes, part number 3HE 12060 000x TQZZA or the VSR Release Notes, part number 3HE 12092 000x TQZZA, for information on features supported in each load of the Release 15.0.Rx software.

  • Page 11: Interface Configuration Process

    INTERFACE CONFIGURATION GUIDE Getting Started RELEASE 15.0.R5 1.2 Interface Configuration Process Table 2 lists the tasks necessary to configure IOMs and XCMs (also referred to as cards), MDAs and XMAs, and ports. Note: For consistency across platforms, XMAs are modeled in the SR OS (CLI and SNMP) as MDAs.

  • Page 12

    Getting Started INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 3HE 11968 AAAC TQZZA 01 Issue: 01...

  • Page 13: Interfaces

    • the term “MDA” is used generically to refer to both MDAs and XMAs Nokia routers provide the capability to configure chassis slots to accept specific card and MDA types and set the relevant configurations before the equipment is actually installed.

  • Page 14

    A:SR12-1>config# card 1 A:SR12-1>config>card# card-type iom3-xp The 7450 ESS-7/12, and 7750 SR-7/12, and 7750 SR-12e platforms also support a variety of IMMs in designated chassis slots. IMMs have integrated MDAs. The provisioning requirements depends on the generation of IMM that you use. Refer to the IMM Installation Guide for more information.

  • Page 15: Mcms

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 The 7750 SR-e platforms support the IOM-e modules in dedicated slots in the rear of each chassis. The 7750 SR-1e supports one physical IOM-e module. This IOM-e is represented in the CLI as card 1. The 7750 SR-2e supports two physical IOM-e cards.

  • Page 16

    =============================================================================== A:ALU-3>config>card# On the 7450 ESS-7/12, 7750 SR-7/12, and 7750 SR-12e, MDAs plug into IOMs. (MDA and MDA-XP modules plug into the IOM3-XP/-B/-C. MDA-e modules plug into the IOM4-e and IOM4-e-B). Up to two MDAs can be provisioned on an IOM.

  • Page 17

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 On the 7750 SR-c12/SR-c4, 7450 ESS-7/12, 7750 SR-7/12, and 7750 SR-12e platforms, MDA names in the CLI start with the letter 'm' (for example, m10-1gb-xp- sfp). The following example displays the card, card-type, mda, and mda-type command usage in the 7750 SR-7: A:SR7>config# card 1...

  • Page 18: Xmas/c-xmas

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 A:SR1e# admin display-config . . . ---------------------------------------------- echo "Card Configuration" #--------------------------------------------- card 1 card-type iom-e mda 1 mda-type me10-10gb-sfp+ exit mda 4 mda-type me1-100gb-cfp2 exit exit ---------------------------------------------- A:SR1e# 2.1.4 XMAs/C-XMAs Note: For consistency across platforms, XMAs are modeled in the system as MDAs, and unless specified otherwise, the term MDA is used generically in this document to refer to both MDAs and C-XMA/XMAs.

  • Page 19: Cmas

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 echo "Card Configuration " #------------------------------------------ card 1 card-type xcm-x20 mda 1 mda-type cx2-100g-cfp power-priority-level 130 exit mda 2 mda-type cx20-10g-sfp power-priority-level 135 exit exit ---------------------------------------------- A:XRS20# On the 7950 XRS, the show card state output displays an “x” in the name of the XMA and “cx”...

  • Page 20: Versatile Service Module (vsm)

    A VSM, like an MDA, is installed and provisioned as a pluggable module in an IOM. The VSM is supported on the 7450 ESS-7/12, 7750 SR-7/12, and 7750 SR-12e platforms. The VSM is not supported on the 7950 XRS or on the 7750 SR-c12/c4 platforms.

  • Page 21: Rate Limiting

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 • packet classification and scheduling 2.1.7.1 Rate Limiting The oversubscribed MDA or CMA limits the rate at which traffic can enter the MDA or CMA on a per-port basis. If a port exceeds its configured limits then the excess traffic will be discarded, and 802.3x flow control frames (pause frames) are generated.

  • Page 22

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 • The packet is classified into 16 classes. Typically, these are the eight forwarding classes and each packet is assigned one priority per forwarding class. After classification, the packet is offered to the queuing model. This queuing model is limited to three queues each having four thresholds.

  • Page 23: Channelized Mda/cma Support

    Each port for the channelized ASAP OC-3/STM-1 MDA supports channelization down to DS-0 and accepts one OC-3/STM-1 SFP small form factor pluggable (SFP) module. The same SFP optics used on Nokia’s SONET/SDH MDAs can be used on the channelized ASAP OC-3/STM-1 MDA.

  • Page 24: Channelized Oc-12/stm-4 Asap Mdas

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 enables enhanced Layer 1 and Layer 2 data path functionality, for example ATM TM features, MDA-based channel or port queuing, or multilink applications like Inverse ATM Multiplexing (IMA). This MDA is supported on the 7750 SR-7/12 and the 7750 SR-c4/c12 platforms.

  • Page 25: Channelized Oc-3/stm-1 Circuit Emulation Services (ces) Cma And Mda

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 E-1 (G.704) channels. Also, 56 kb/s channels cannot be part of a bundle. E-3 ports do not support channelization, only clear channel operation. This MDA is supported on the 7750 SR-7/12 and the 7750 SR-c4/c12 platforms. 2.1.8.7 Channelized OC-3/STM-1 Circuit Emulation Services (CES) CMA and MDA...

  • Page 26: Network Interconnections

    2.1.8.8 Network Interconnections Nokia routers can fill the needs of smaller service providers as well as the more remote point of presence (PoPs) locations for larger service providers. To support the use of lower speed links as network links in the likelihood that lower speed circuits...

  • Page 27: Digital Diagnostics Monitoring

    Interfaces RELEASE 15.0.R5 2.2 Digital Diagnostics Monitoring Some Nokia SFPs, XFPs, QSFPs, CFPs and the MSA DWDM transponder have the Digital Diagnostics Monitoring (DDM) capability where the transceiver module maintains information about its working status in device registers including: • temperature •...

  • Page 28

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 =============================================================================== High Alarm High Warn Low Warn Low Alarm Lane Tx Bias Current (mA) 78.0 75.0 25.0 20.0 Lane Rx Optical Pwr (avg dBm) 2.30 2.00 -11.02 -13.01 ------------------------------------------------------------------------------- Lane ID Temp(C)/Alm Tx Bias(mA)/Alm Tx Pwr(dBm)/Alm Rx Pwr(dBm)/Alm -------------------------------------------------------------------------------...

  • Page 29

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 DDM information is populated into the router’s MIBs, so the DDM data can be retrieved by Network Management using SNMP. Also, RMON threshold monitoring can be configured for the DDM MIB variables to set custom event thresholds if the factory-programmed thresholds are not at the desired levels.

  • Page 30

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Table 5 DDM Alarms and Warnings Parameter SFP/XFP Units Required? MSA DWDM Temperature - High Alarm - Low Alarm - High Warning - Low Warning Supply Voltage µV - High Alarm - Low Alarm - High Warning - Low Warning TX Bias Current...

  • Page 31: Sfps And Xfps

    The availability of the DDM real-time information and the warning and alarm status is based on the transceiver. It may or may not indicate that DDM is supported. Although some Nokia SFPs support DDM, Nokia has not required DDM support in releases prior to Release 6.0. Non-DDM and DDM-supported SFPs are distinguished by a specific ICS value.

  • Page 32: Ports

    2.3.1 Port Types Before a port can be configured, the slot must be provisioned with a card type and MDA type. Nokia routers support the following port types: • Ethernet — Supported Ethernet port types include: − Fast Ethernet (10/100BASE-T) −...

  • Page 33

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Once the port is changed to hybrid, the default MTU of the port is changed to match the value of 9212 bytes currently used in network mode (higher than an access port), ensuring that both SAP and network VLANs can be accommodated.

  • Page 34

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 When a named pool policy is applied to the hybrid port’s MDA or to the hybrid port, the port’s fair share of total buffers available to the MDA is split into three parts: default pools, named pools local to the port, and named pools on the ports MDA.

  • Page 35: Port Features

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 • APS — Automatic Protection Switching (APS) is a means to provide redundancy on SONET equipment to guard against linear unidirectional or bidirectional failures. The network elements (NEs) in a SONET/SDH network constantly monitor the health of the network. When a failure is detected, the network proceeds through a coordinated pre-defined sequence of steps to transfer (or switchover) live traffic to the backup facility (called protection facility.) This is done very quickly to minimize lost traffic.

  • Page 36: Network Access Control

    2.3.2.2 802.1x Network Access Control Nokia routers support network access control of client devices (PCs, STBs, and so on) on an Ethernet network using the IEEE. 802.1x standard. 802.1x is known as Extensible Authentication Protocol (EAP) over a LAN network or EAPOL.

  • Page 37

    RELEASE 15.0.R5 2.3.2.2.1 802.1x Modes Nokia routers support port-based network access control for Ethernet ports only. Every Ethernet port can be configured to operate in one of three different operation modes, controlled by the port-control parameter: • force-auth — Disables 802.1x authentication and causes the port to transition to the authorized state without requiring any authentication exchange.

  • Page 38

    EAPOL-start PDU, if it doesn't receive the EAP- Request/ID frame during bootup. The client responds on the EAP-Request/ID with a EAP-Response/ID frame, containing its identity (typically username + password). Figure 2 802.1x Authentication Scenario Client 7450 ESS RADIUS Authentication Server Port Unauthorized EAPOL-Start...

  • Page 39

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 The RADIUS server checks the supplied credentials, and if approved will return an Access Accept message to the router. The router notifies the client with an EAP- Success PDU and puts the port in authorized state. 2.3.2.2.3 802.1x Timers The 802.1x authentication procedure is controlled by a number of configurable timers...

  • Page 40

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 • quiet-period — Indicates number of seconds between authentication sessions It is started after logoff, after sending an EAP-Failure message or after expiry of the supplicant-timeout timer. The default value is 60. The range is 1 to 3600. RADIUS timer and scaler: •...

  • Page 41: Macsec

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 2.3.2.2.5 802.1x Configuration and Limitations Configuration of 802.1x network access control on the router consists of two parts: • Generic parameters, which are configured under config>security>dot1x • Port-specific parameters, which are configured under config>port>ethernet>dot1x 801.x authentication: •...

  • Page 42

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Figure 4 802.1 AE LAN-MODE Autheticated Excrypted 802.1AE LAN-MODE DMAC SMAC 802.1AE Header 802.1Q ETYPE Payload 0x88e5 MISEec Ether PACKET TCI/AN SCI (optional) Type NUMBER sw0126 The forwarding on a MACSec packet is performed using the destination MAC address, which is in clear text.

  • Page 43

    802.1AE dictates that the 802.1Q VLAN needs to be encrypted. Some vendors give the option of configuring the MACSec on a port with VLAN in clear text. SR OS supports both modes. On the 7750 SR, 7450 ESS, and 7950 XRS, 1/10 Gig cards support both mode of operation.

  • Page 44

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Table 7 MACsec Key Management Modes (Continued) Keying Explanation SR OS Support Where Used Static CAK PRE SHARED KEY Uses a dynamic Supported Switch to switch MACSec Key Management (MKA) and uses a configured pre shared key to drive the CAK.

  • Page 45

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Figure 7 MACsec Concepts for Static-CAK Node 1 CA1 Node 2 CA1 Port 1/1/1 security zone 1 Port 1/1/1 security zone 1 SC1-node1 SecY 1 SecY 1 TxSC1 TxSC1 TxSA1 (Active) TxSA1 (Inactive) SCI-node2 TxSA2 (Inactive) TxSA2 (Active) RxSC1...

  • Page 46

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Table 8 MACsec Terms (Continued) MACsec Term Description SA: Security Association In the cases of SR OS 2 SA per SC, each with a different SAK, each SC comprises a succession of SAs. Each SA is identified by the SC identifier, concatenated with a two-bit association number.

  • Page 47

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Figure 8 MACsec Generating the CAK Supplicant Authenticator RADIUS EAP Authentication Server MKA Protocol PSK: PSK: EAPoL for Authentication CAK Value: 128 or 256 CAK Value: CKN Value: 16 Char CAK: CKN Value: derived from EAP or PSK Key Server KEK: ICK:...

  • Page 48

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Figure 9 MACsec Control Plane Supplicant Authenticator RADIUS EAP Authentication Server MKA Protocol PSK: PSK: EAPoL for Authentication CAK Value: 128 or 256 CAK Value: CKN Value: 16 Char CAK: CKN Value: derived from EAP or PSK Key Server KEK: ICK:...

  • Page 49

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 2.3.2.3.7 Each peer operates the MACsec Key Agreement Protocol (MKA). Each node can operate multiple MKAs base on the number of CA that it belongs to. Each instance of MKA is protected by a distinct secure connectivity Association key (CAK), that allows each PAE to ensure that information for a given MKA instance is only accepted from other peer that also possess that CAK, and therefore identifying themselves as members or potential members of the same CA.

  • Page 50

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 To avoid a new participant having to respond to each MKPDU from each partner as it is received, or trying to delay its reply until it is likely that MI MN tuples have been received from all potential partners, each participant maintains and advertises both a live peers list and a potential peers list.

  • Page 51

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 2.3.2.3.10 MACsec Capability, Desire, and Encryption Offset 802.1x-2010 had identified two fields in the MKA PDU. Those fields are: • MACsec Capability • Desire MACsec Capability signals weather MACsec is capable of integrity and confidentiality.

  • Page 52

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 • cipher suite selection • SAK generation and distribution • SA assignment • identifying the CA when two or more CAs merge Each participant in an MKA instance uses the Key Server priority (an 8-bit integer) encoded in each MKPDU to agree on the Key Server.

  • Page 53

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 2.3.2.3.13 P2P (Switch to Switch) Topology In a point-to-point topology, each router needs a single security zone and single Tx- SC for encryption and a single Rx-SC for decryption. Each SC has two SAs. In total for point-to-point topology, four SAs are needed, two RxSA for RxSC1 and two TXSA for TxSC1.

  • Page 54

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Figure 11 Switch Multi-point to Switch Multi-point Topology SAI: (11:22:33:44:55:02, 00, 01) Node 2 CA1 SecY 1 N1 is Server TxSC1-----TxSA1, TxSA2 N1 Send SAK to every body RxSC1-----RxSA1, RxSA2-peer1 RxSC2-----RxSA3, RxSA4-peer2 RxSC32-----RxSA63, RxSA64-peer32 RxSC33-----NA-peer33 SAI: (11:22:33:44:55:01, 00, 01) Node 1 CA1...

  • Page 55

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Note: The operator must ensure that the number of peers do not exceed the limit of maximum peers per security zone or maximum peers per port (for example, exceeds the port max-peer parameter). If the maximum peer is exceeded, the peer connectivity will be random in case of a node failure or packet loss.

  • Page 56: Sonet/sdh Port Attributes

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 2.3.2.3.17 802.1X Tunneling and Multihop MACsec MACsec is an Ethernet packet and, as with any other Ethernet packet, can be forwarded through multiple switches via Layer 2 forwarding. The encryption and decryption of the packets will be performed via the 802.1x (MKA) capable ports. To ensure that MKA is not terminated on any intermediate switch or router, the user can enable 802.1x tunneling on the corresponding port.

  • Page 57: Sonet/sdh Path Attributes

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 The port’s transmit clock rate can be node or loop timed. The port’s receive clock rate can be used as a synchronization source for the system. The Section Trace (C1) byte can be configured by the user to ensure proper physical cabling. The port can activate and deactivate local line and internal loopbacks.

  • Page 58: Multilink Frame Relay

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Table 13 Valid SONET and SDH Path Configurations (Continued) Framing Path Configuration Options Max Number of Paths Max Number of Paths Per Physical Port Per Physical Port Per TDM Satellite Port SONET OC3>STS1 SPE>VT GROUP>VT1.5 84 DS1 or 512 n*64 kb/s 84 DS1 SPE>DS1...

  • Page 59

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 The MLFR implementation supports FRF.16.1 bundle link integrity protocol to verify serviceability of a member link. 2.3.2.6.1 MLFR Bundle Data Plane FRF.16.1 reuses the UNI/NNI fragmentation procedures defined in FRF.12. Frames on all FR SAP on the MLFR bundle have the UNI/NNI fragmentation header added regardless if they are fragmented or not.

  • Page 60

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 2.3.2.6.2 MLFR Bundle Link Integrity Protocol FRF.16.1 defines a MLFR Bundle Link Integrity Protocol which verifies the serviceability of a member link. If a problem is found on the member link the link integrity protocol will identify the problem, flag the link as unusable, and adjust the Bundle’s available bandwidth.

  • Page 61: Frf.12 End-to-end Fragmentation

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 The control messages are encapsulated in a single-fragment frame where the C-bit, the B-bit, and the E-bit are all set. The details of the message format are given in FRF.16.1. Table 14 lists the user configured control parameters with values as specified in FRF.16.1.

  • Page 62: Frf.12 Uni/nni Link Fragmentation

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 The following is the mode of operation for the fragmentation in the transmit direction of the FR SAP. Frames of all the FR SAP forwarding class queues are subject to fragmentation. The fragmentation header is, however, not included when the frame size is smaller than the user configured fragmentation size.

  • Page 63: Mlfr/frf.12 Support Of Aps, Bfd, And Mirroring Features

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 The operator must delete all configured FR SAPs on a port before enabling or disabling FRF.12 UNI/NNI on that port. Also, the user must shut down the port in order to change the value of the fragmentation threshold. A FR SAP on a FR circuit with FRF.12 UNI/NNI fragmentation enabled can be part of a VLL, VPLS, IES, or VPRN service.

  • Page 64: Multilink Point-to-point Protocol (mlppp)

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 2.3.2.10 Multilink Point-to-Point Protocol (MLPPP) Multilink point-to-point protocol is defined in the IETF RFC 1990, The PPP Multilink Protocol (MP), and provides a way to distribute data across multiple links within an MLPPP bundle to achieve high bandwidth. MLPPP allows for a single frame to be fragmented and transmitted across multiple links.

  • Page 65

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Figure 13 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 SR-series routers can support and negotiate the alternate 12-bit frame format.

  • Page 66

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 2.3.2.10.3 Sequence Number Sequence numbers can be either 12 or 24 bits long. The sequence number is zero for the first fragment on a newly constructed AVC 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.

  • Page 67

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 • No async control character map • No link quality monitoring • No compound frames • No self-describing-padding Any non-LCP packets received during this phase must be silently discarded. 2.3.2.10.8 Link Fragmentation and Interleaving Support Link Fragmentation and Interleaving (LFI) provides the ability to interleave high priority traffic within a stream of fragmented lower priority traffic.

  • Page 68: Multi-class Mlppp

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 3. The fragments are then transmitted out the egress port. 4. After the transmission of the fragments has begun, high priority frames arrive in the high priority queue. 5. The transmission of the remaining fragments stops and the high priority packets are transmitted out the egress interface.

  • Page 69

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Table 15 Header Formats Original MLPPP Header Format MC-MLPPP Short Sequence Header Format The new MC-MLPPP header format uses the two (previously unused) bits before the sequence number as the class identifier. This allows four distinct classes of service to be identified into separate re-assembly contexts.

  • Page 70

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Table 16 Default Packet Forwarding Class to MLPPP Class Mapping (Continued) FC ID FC Name Scheduling Priority MLPPP Class 4- MLPPP Class 3- MLPPP Class (Default) class bundle class bundle 2-class bundle Expedited Non-Expedited Non-Expedited Non-Expedited Non-Expedited...

  • Page 71

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Table 18 MLPPP Class Queue Threshold Parameters Class 0 Class 1 Class 2 Class 3 Queue Threshold (in ms @ Available bundle rate) 2-Class Bundle Default Egress QoS Profile 3-Class Bundle Default Egress QoS Profile 4-Class Bundle Default Egress QoS Profile 4-Class Bundle...

  • Page 72

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Table 19 MLPPP Class Queue Scheduling Parameters (Continued) WRR Parameters Profile 2 <1% Profile 3 <1% Figure 16 MLPPP Class Queue Scheduling Scheme Class0 > 100% Class1 > MIR Strict Priority Class2 Class3 OSSG259 Note that all queue threshold and queue scheduling parameters are adjusted to the available bundle rate.

  • Page 73

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Ingress MLPPP Class Reassembly For an MLPPP bundle with the multi-class option enabled, there is a default profile for setting the re-assembly timer value for each class. When the pre-defined MLPPP ingress QoS profile 1 is applied to a 4-class bundle, the values of the timers are modified as shown in Table Table 20...

  • Page 74

    − Changes to any parameters in the ingress and egress QoS profiles. The CLI commands for the creation of ingress and egress QoS profiles and configuration of the individual QoS parameters are described in the 7450 ESS, 7750 SR, 7950 XRS, and VSR Quality of Service Guide.

  • Page 75: Cisco Hdlc

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 2.3.2.12 Cisco HDLC Cisco HDLC (cHDLC) is an encapsulation protocol for information transfer. It is a bit- oriented synchronous data-link layer protocol that specifies a data encapsulation method on synchronous serial links using frame characters and checksums. cHDLC monitors line status on a serial interface by exchanging keepalive request messages with peer network devices.

  • Page 76

    PPP. 2.3.2.12.1 SLARP A cHDLC interface on a Nokia router will transmit a SLARP address resolution reply packet in response to a received SLARP address resolution request packet from peers. The cHDLC interface will not transmit SLARP address resolution request packets.

  • Page 77: Automatic Protection Switching (aps)

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 The two key SONET/SDH parameters are scrambling and signal-label (C2-byte). Scrambling is off by default. The default value of the C2-byte is 0xCF. These two parameters can be modified using the CLI. The other SONET overhead values (for example, j0) follow the same rules as the current POS implementation.

  • Page 78

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Figure 17 APS Protection (Single Chassis APS) and Switchover GigE Working Facility GigE Protection Facility 7750 SR 7750 SR GigE Working Facility GigE Protection Facility 7750 SR 7750 SR GigE Working Facility GigE Protection Facility 7750 SR 7750 SR Data Flow...

  • Page 79

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 • Revertive Switching • Bidirectional 1+1 Switchover Operation Example • Protection of Upper Layer Protocols and Services • APS User-Initiated Requests • APS and SNMP • APS Applicability, Restrictions and Interactions • Sample APS Applications 2.3.2.13.1 Single Chassis and Multi-Chassis APS APS can operate in a single chassis configuration (SC-APS) or in a multi-chassis...

  • Page 80

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 APS on a Single Node (SC-APS) In a single chassis APS both circuits of an APS group are terminated on the same node. The working and protect lines of a single chassis APS group can be: •...

  • Page 81

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 impacted so it is recommended to avoid a mix of platforms in the same MC-APS group where possible. The configuration consistency between the working circuit/ router and the protection circuit/router is not enforced by the 7750 SR. Service or network-specific configuration data is not signaled nor synchronized between the two service routers.

  • Page 82

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 2.3.2.13.2 APS Switching Modes APS behavior and operation differs based on the switching mode configured for the APS group as shown in Table 24. Several switching modes are supported in the router. The switching mode affects how the two directions of a link behave during failure scenarios and how APS tx operates.

  • Page 83

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Bidirectional 1+1 Signaling APS In Bidir 1+1 Sig APS switching mode the Tx data is sent on the active link only (it is not bridged to both links simultaneously). 1+1 signaling, however, is used for full interoperability with signaling-compliant 1+1 architectures.

  • Page 84

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Unidirectional 1+1 Signaling APS In Uni 1+1 Sig APS switching mode the Tx data is sent on the active link only (it is not bridged to both links simultaneously). 1+1 signaling, however, is used for full interoperability with signaling-compliant 1+1 architectures.

  • Page 85

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 − If the remote end indicates an APS switch and the router can RX and TX on the circuit newly selected by the remote end, then the router will move its TX direction and will perform an APS switch of its RX direction (unless the router already TX and RX on the newly selected circuit).

  • Page 86

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 2.3.2.13.3 APS Channel and SONET Header K Bytes The APS channel (bytes K1 and K2 in the SONET header) exchanges APS protocol messages for all APS modes. K1 Byte The switch priority of a request is assigned as indicated by bits 1 through 4 of the K1 byte (as described in the rfc3498 APS-MIB);...

  • Page 87

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Table 26 shows bits 5 to 8 of a K1 byte and K2 Bits 1 to 4 and the channel number code assignments. Table 26 K1 Byte, Bits 5 to 8 (and K2 Bits 1 to 4), Channel Number Code Assignments Channel Number Channel and Notes Code...

  • Page 88

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Table 27 K2 Byte Functions (Continued) Bits 1 to 8 Function 6 to 8 Line AIS Line RDI Provisioned for bi-directional switching Provisioned for uni-directional switching (reserved for future use) (reserved for future use) (reserved for future use) (reserved for future use) Differences in SONET/SDH Standards for K Bytes...

  • Page 89

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 APS Protection Switching Byte Failure An APS Protection Switching Byte (APS-PSB) failure indicates that the received K1 byte is either invalid or inconsistent. An invalid code defect occurs if the same K1 value is received for 3 consecutive frames (depending on the interface type (framer) used, the 7750 SR may not be able to strictly enforce the 3 frame check per GR-253 and G.783/G.841) and it is either an unused code or irrelevant for the specific switching operation.

  • Page 90

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 APS Far-End Protection Line Failure An APS far-end protection line (APS-FEPL) failure corresponds to the receipt of a K1 byte in 3 consecutive frames that indicates a signal fail (SF) at the far end of the protection line.

  • Page 91

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Table 29 Actions for the Bi-directional Protection Switching Process Status APS Commands Sent in K1 and Action K2 Bytes on Protection Line B -> A A -> B At Site B At Site A No failure No request.

  • Page 92

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Annex B APS Outage Reduction Optimization Typical standard Annex B behavior when a local SF is detected on the primary section (circuit), and this SF is the highest priority request on both the local side and from the remote side as per the APS specifications, is to send a request to the remote end and then wait until a reverse request is received before switching over to the secondary section.

  • Page 93

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Figure 20 shows an example in which the APS working circuit is connected to IOM- 1/MDA-1 and the protection circuit is connected to IOM-2/MDA-1. In this example, assume that the working circuit is currently used to transmit and receive data. Figure 20 APS Working and Protection Circuit Example Flexible FastPath...

  • Page 94

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Switchover Process for Received Data The Flexible Fast-Path complexes for both working and protect circuits are programmed to process ingress. The inactive (protect) circuit however is programmed to ignore all packet data. To perform the switchover from working circuit to the protect circuit the Flexible Fast-Path complex for the working circuit is set to ignore all data while the Flexible Fast-Path complex of the protect circuit will be changed to accept data.

  • Page 95

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Forced Switching of Active to Protection The forced switch of active to protection command switches the active line to the protection line unless a request of equal or higher priority is already in effect. When the forced switch of working to protection command is in effect, it may be overridden either by a lockout of protection or by detecting a signal failure on the protection line.

  • Page 96

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Table 30 Switching Mode to MIB Mapping (Continued) switching-mode TIMETRA-APS-MIB APS-MIB tApsProtectionType apsConfigDirection Uni 1+1 Sig+Data APS onePlusOne unidirectional (uni-1plus1) apsConfigMode in the APS-MIB is set to onePlusOneOptimized for Annex B operation. 2.3.2.13.10 APS Applicability, Restrictions and Interactions Note: The Release Notes for the relevant SR OS release should be consulted for details about APS restrictions.

  • Page 97

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 IMA APS protection is supported only when the router is connected to another piece of equipment (possibly through an ADM) running a single IMA instance at the far end. By design, the IMA APS implementation is expected to keep the IMA protocol up as long as the far end device can tolerate some frame loss.

  • Page 98

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Table 32 MDA/Port Type Pairing for APS MDA Type Unchannelized Circuit Channelized SONET/SDH SONET/SDH For example: Emulation Any Service Satellite (POS) m4-atmoc12/3- (CES) Any Port For example: For example: (ASAP) m16-oc12/3- m4-choc3-ces- For example: m1-choc12-as- Unchannelized Supported...

  • Page 99

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 APS Switchover During CFM/CPM Switchover An APS switchover immediately before, during or immediately after a CFM/CPM switchover may cause a longer outage than normal. Removing or Failure of a Protect MDA The detection of a CMA/MDA removal or a CMA/MDA failure can take additional time.

  • Page 100

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Figure 21 SC-APS MLPPP on Channelized Access Interfaces Example PDSN, AAA GigE Switch MLS B BITS I/F GigE T1 # 2 EV-DO GigE GigE T3/OC-3/OC-12 DACS T1 # 1 Aggregation DHCP Relay GigE Router A MLS A GigE Switch...

  • Page 101

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Figure 22 MC-APS MLPPP on Channelized Access Interfaces Example PDSN, AAA Aggregation DHCP Relay Router B MLS B GigE T3/OC-3/ Switch OC-12 GigE BITS I/F T1 # 2 EV-DO VRRP GigE GigE DACS OSPF Area T1 # 1 GigE...

  • Page 102

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Figure 23 Multi-Chassis APS Application Router 7750 Switch 1483B or 7670 Edge Service Device OCx ATM 1 IP/MPLS ATM Network Network 1483B Edge Service OCx ATM 2 Device Physical Link 7750 Router Data Flow IG0001 Communication between service routers A and B is established through link 3.

  • Page 103

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Figure 24 Access and Node and Network Resilience TLDP Active Standby Aggregation Aggregation Node Node Active Standby Active Standby Inter-ChassisPW Inter-ChassisPW MSAN MSAN for VLL for VLL Standby Active Standby Active Aggregation Aggregation Node Node Standby Active...

  • Page 104

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Figure 25 MC-APS with ATM VLL Redundancy Pseudo-wire Active/Standby Segments Pseudo-wire T-PE T-PE S-PE Convergent GSM/GPRS E1 TDM Packet Network 7750 7750 SR-7 SR-7 IP MPL Core E1 ATM Layer 3 VPNs E1 IMA ATM 7750 7750 7750...

  • Page 105

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Figure 26 Mobile RAN with Microwave Transport Example E1’s (GSM / TDM / 3G) STM-1 7750c4 GSM/TDM 7750c12 STM-1’s POS 1+1/STM1 ch (MLPPP) E1’s STM-1 MLPPP/STM-1’s POS 1+1 8660 7750c4 Future 7750 7750c12 = STM-1 Microwave radio E1’s link deployed as transport (GSM / TDM / 3G)

  • Page 106: Inverse Multiplexing Over Atm (ima)

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 • Active RX circuits are selected based on local conditions only. The SONET K Bytes are not needed to coordinate switch actions, but they are still used since they flow through and reach the far-end router. •...

  • Page 107

    Hardware Applicability IMA is supported on channelized ASAP MDAs. Software Capabilities Nokia’s implementation supports IMA functionality as specified in ATM Forum’s Inverse Multiplexing for ATM (IMA) Specification Version 1.1 (af-phy-0086.001, March 1999). The following capabilities are supported: • TX Frame length — Only IMA specification default of 128 cells is supported.

  • Page 108

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 • IMA version — Both versions 1.0 and 1.1 of IMA are supported. There is no support for automatically falling to version 1.0 if the far end advertises 1.0 support, and the local end is configured as 1.1. Due to potential protocol interoperability issues between IMA 1.0 implementations, it is recommended that IMA version 1.1 is used whenever possible.

  • Page 109: Ethernet Local Management Interface (e-lmi)

    • IMA test pattern — Nokia’s implementation supports test pattern procedures specified in the IMA specification. Test pattern procedures allow debugging of IMA group problems without affecting user data.

  • Page 110: Link Layer Discovery Protocol (lldp)

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 The bandwidth profile sub-information element associated with the EVC Status IE does not use information from the SAP QoS policy. A value of 0 is used in this release as MEF 16 indicates the bandwidth profile sub-IE is mandatory in the EVC Status IE. The EVC identifier is set to the description of the SAP and the UNI identifier is set to the description configured on the port.

  • Page 111

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Figure 28 LLDP Internal Architecture for a Network Node Organizationally Organizationally Defined Local Device Defined Remote Device LLDP MIB Extension LLDP MIB Extensions PTOPO MIB (Optional) (Optional) (Optional) Entity MIB (Optional) LLDP Local System LLDP Remote Systems Interface MIB (Optional)

  • Page 112

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Figure 29 Generic Customer Use Case For LLDP MPLS/Native ETH SG/R Core SG/R QinQ DSLAMs Ethernet Links - FE/GE/10GE OSSG263 IEEE 802.1ab LLDP running on each Ethernet interfaces in between all the above network elements may be used to discover the topology information. Operators who are utilizing IOM3/IMM and above can tunnel the nearest-bridge at the port level using the tunnel-nearest-bridge command under the config>port>ethernet>lldp>destmac (nearest-bridge) hierarchy.

  • Page 113

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 LLDP itself does not contain a mechanism for soliciting specific information from other LLDP agents, nor does it provide a specific means of confirming the receipt of information. LLDP allows the transmitter and the receiver to be separately enabled, making it possible to configure an implementation so the local LLDP agent can either transmit only or receive only, or can transmit and receive LLDP information.

  • Page 114: Exponential Port Dampening

    SAM. Including the port-desc option as part of the tx-tlv configuration allows a Nokia remote peer supporting port-desc preferred display logic (11.0r1) to display the value in the port description TLV instead of the port-id field value. This does not change the encoding of the port-id field.

  • Page 115

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 where: N(t) is the quantity that still remains after a time t is the initial quantity is the half-life ½ In dampening, N refers to the starting penalties from the last link-down event. The quantity N(t) refers to the decayed penalties at a specific time, and is calculated starting from the last link-down event (that is, from the time when N last changed).

  • Page 116

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 i. the accumulated penalties are incremented by 1000 ii. the accumulated penalties now equal 1000, which is less than the suppress threshold (of 1500), so the dampening state is idle iii. because the dampening state is idle, link-down is passed to the upper layer iv.

  • Page 117: Per Port Aggregate Egress Queue Statistics Monitoring

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 7. t = 46: Accumulated penalties drop below the reuse threshold i. the accumulated penalties drop below the reuse threshold, so the dampening state changes to idle ii. because the dampening state is idle and the current link state is up, link-up is passed to the upper layer iii.

  • Page 118

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 config port <port-id> [no] monitor-agg-egress-queue-stats When enabled, the line card will poll the related queues to derive the aggregates which provide the delta of the queue statistics since turning on the monitoring. This means that the reported statistics are not reduced by those from a deleted queue and so the aggregates correctly represent the forwarded/dropped statistics since the start of monitoring.

  • Page 119: Port Cross-connect (pxc)

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 2.4 Port Cross-Connect (PXC) Port Cross-Connect (PXC) functionality refers to a method of redirecting ingress traffic received on I/O ports to an operator-chosen forwarding complex (anchor point). This traffic is then pre-processed in the egress data path of the anchor card and consequently looped back into the ingress data path on the same anchor card.

  • Page 120: Pxc Terminology

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Figure 31 Traffic Pre-Processing Utilizing Cross-Connected Port (PXC) SR OS Node Line Card 1 Port 1 Egress Path Ingress Path Second Stage of Port 3 Ingress Processing Ingress Path (PXC) Line Card 2 Port 2 Egress Path Ingress Path Line Card 3 —...

  • Page 121: Pxc - Physical Port In Cross-connect (loopback) Mode

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 2.4.2 PXC - Physical Port in Cross-Connect (Loopback) Mode The concept of a PXC port on an FP3-based line card is shown in Figure 32. The PXC does not require an optical transceiver. Figure 32 100 GE 2x100 Gb/s 1x200 Gb/s...

  • Page 122: Operational State

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 • Once inside the PXC ID configuration, the physical port cannot be used outside of the PXC context. For example, a regular IP interface cannot use this physical port, or a SAP on that port cannot be associated with a service. •...

  • Page 123

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Figure 33 Two Cross-Connected Ports vs Single Cross-Connected Port 10Gbps Full Duplex External Cross-Connect Physical Port 1/1/1 Physical Port 1/1/2 Upstream 10Gbps 10GE 10GE 10Gbps Downstream Optical Fiber Transition from a dual port cross-connect, to a single port cross-connect 10Gbps Single Duplex External Cross-Connect Physical Port 1/1/1...

  • Page 124: Pxc Sub-port Operational State

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 port pxc-<pxc-id>.b shutdown The two PXC sub-ports are distinguishable by .a and .b suffixes. They transmit traffic toward each other, thus simulating two ports that are interconnected. The PXC sub-ports can be accessed through the configuration in order to modify their parameters (QoS, and so on).

  • Page 125: Port Statistics

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 2.4.4 Port Statistics There are two types of statistics that can be collected on a regular (non PXC) Ethernet port: • Physical port level statistics provide information about conditions on the data- link layer and physical level, for example, the aggregate number of forwarded and dropped octets/bytes on a MAC level, FCS errors, number of collisions, and so on.

  • Page 126: Lag With Pxc Ports - Pxc Lag

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Statistics are cleared when a physical port enters or leaves the PXC mode. Statistics collection to a local file is not supported on physical PXC ports. Queues are not instantiated on physical PXC ports and therefore, the network level (queue) statistics are not maintained on physical PXC ports.

  • Page 127: Basic Pxc Provisioning

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Statistics in the output of the show lag id statistics command represent combined traffic carried over the referenced lag id and its pair (LAG 1 and LAG 2 in the above example). 2.4.6 Basic PXC Provisioning The CLI flow is shown in Figure 35.

  • Page 128: Qos

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 2.4.7 QoS Upstream and downstream traffic on a PXC is funneled through the same physical port. In other words, upstream and downstream traffic is transmitted and then received by the same port. Each forwarding direction (upstream and downstream) is represented by a corresponding PXC sub-port (.a or .b).

  • Page 129: Pool Allocations On Pxc Ports

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 2.4.7.2 Pool Allocations on PXC Ports Queue buffers are created in buffer pools and are used for traffic buffering when queues are congested. Buffer pools are allocated per forwarding complex or per PXC physical port. Each physical PXC port has three associated buffer pools: •...

  • Page 130: Mirroring And Li On Pxc Ports

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 2.4.8 Mirroring and LI on PXC Ports Traffic on a PXC sub-port can be mirrored or lawfully intercepted (LI). For example, subscriber “Annex1” traffic arriving on a PXC sub-port will be mirrored if “Annex1” is configured as a mirror or LI source.

  • Page 131: Configuration Example

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 • efm-oam — The Information OAMPDUs are transmitted by each peer (PXC sub- port) at the configured intervals. Their purpose is to perform keepalive and critical notification functions. • CRC errors are only recorded, if frames are transmitted. •...

  • Page 132

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 configure port 3/1/1 description "access I/O port on card 3; ecap is null which means that all VLAN tagged and untagged traffic will be accepted” ethernet mode access encap-type null port 4/1/1 description "access I/O port on card 4; ecap is null which means that all VLAN tagged and untagged traffic will be accepted”...

  • Page 133

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 The following displays an example of a PXC LAG configuration: configure lag 1 create description "terminating side of the cross-connect” port pxc-1.a port pxc-2.a lag 2 create description "transient side of the cross-connect” port pxc-1.b port pxc-2.b Passing traffic from the I/O side on access (ports 3/1/1 and 4/1/1) via the transient PXC sub-ports pxc-1.b and pxc-2.b to the termination side of the PXC is performed...

  • Page 134: Forwarding Path Extensions (fpe)

    (7450 ESS, 7750 SR, and VSR Triple Play Service Delivery Architecture Guide, 7450 ESS, 7750 SR, 7950 XRS, and VSR Layer 3 Services Guide: IES and VPRN, and 7450 ESS, 7750 SR, 7950 XRS, and VSR Layer 2 Services and EVPN Guide: VLL, VPLS, PBB, and EVPN).

  • Page 135

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Figure 36 FPE - Sample Provisioning Steps Operator (manually) configured System (dynamically) configured configure port-xc configure pxc 1 create port pxc-1.a port 1/1/1 [no] shutdown [no] shutdown port pxc-1.b pxc 2 create [no] shutdown port 1/1/3 port pxc-2.a [no] shutdown...

  • Page 136: Lag

    Packet sequencing must be maintained for any given session. The hashing algorithm deployed by the Nokia routers is based on the type of traffic transported to ensure that all traffic in a flow remains in sequence while providing effective load sharing across the links in the LAG.

  • Page 137: Lacp Multiplexing

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 2.6.1.1 LACP Multiplexing The router supports two modes of multiplexing RX/TX control for LACP: coupled and independent. In coupled mode (default), both RX and TX are enabled or disabled at the same time whenever a port is added or removed from a LAG group. In independent mode, RX is first enabled when a link state is UP.

  • Page 138: Active-standby Lag Operation

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 • If the port encapsulation is QinQ, a 0.* SAP (for example, 1/1/10:0.*) can be used to tunnel these packets. LAG port states may be impacted if LACP frames are lost due to incorrect prioritization and congestion in the network carrying the tunnel.

  • Page 139

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Figure 37 Active-Standby LAG Operation without Deployment Examples In case of a link failure, as shown in Figure 38 Figure 39, the switch over behavior ensures that all LAG-members connected to the same IOM as failing link become standby and LAG-members connected to other IOM become active.

  • Page 140: Lag On Access Qos Consideration

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 2.6.3 LAG on Access QoS Consideration The following section describes various QoS related features applicable to LAG on access. 2.6.3.1 Adapt QoS Modes Link Aggregation is supported on the access side with access or hybrid ports. Similarly to LAG on the network side, LAG on access aggregates Ethernet ports into all active or active-standby LAG.

  • Page 141

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 When port-fair mode is enabled, per-Vport hashing is automatically disabled for subscriber traffic such that traffic sent to the Vport no longer uses the Vport as part of the hashing algorithm. Any QoS object for subscribers, and any QoS object for SAPs with explicitly configured hashing to a single egress LAG port, will be given the full bandwidth configured for each object (in a similar way to link mode).

  • Page 142: Per-fp-ing-queuing

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Table 33 Adapt QoS Bandwidth/Rate Distribution (Continued) distribute link port-fair distribute include-egr-hash-cfg % # local linksa 100% 100% rate (SAP 100% bandwidth (SAP hash to a one Scheduler bandwidth hash to one link) link) %# all linksb % # local linksa (SAP hash to all (SAP hash to all...

  • Page 143: Per-fp-sap-instance

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 When the feature is enabled in the config>lag>access context, the queue and virtual scheduler allocation will be optimized. Only one queuing set and one H-QoS virtual scheduler tree per SAP/encap group will be allocated per egress forwarding path (FP) instead of one set per each port of the LAG.

  • Page 144: Lag And Ecmp Hashing

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 • SAP instance optimization applies to LAG-level. Whether a LAG is sub-divided into sub-groups or not, the resources are allocated per forwarding path for all complexes LAG’s links are configured on (i.e. irrespective of whether a given sub-group a SAP is configured on uses that complex or not).

  • Page 145: Per Flow Hashing

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 For LAG load balancing: 1. LAG link map profile 2. Per link hash 3. Consistent per service hashing 4. Per flow hashing 2.6.4.1 Per Flow Hashing Per flow hashing uses information in a packet as an input to the hash function ensuring that any given flow maps to the same egress LAG port/ECMP path.

  • Page 146

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 − The hashing procedure that used to be applied for all VPLS BUM traffic would result in PBB BUM traffic being sent out on BVPLS SAP to follow only a single link when MMRP was not used. Therefore, traffic flooded out on egress BVPLS SAPs is now load spread using the algorithm described above for VPLS known unicast.

  • Page 147

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 When the ECMP set includes an IP interface configured on a spoke-SDP (IES/VPRN spoke interface), or a Routed VPLS interface, the unicast IP packets—which will be sprayed over this interface—will not be further sprayed over multiple RSVP LSPs (part of the same SDP), or multiple LDP FEC next-hops when available.

  • Page 148

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 This provides some control to the user such that this feature is disabled if labeled packets received on a specific interface include non IP packets that can be confused by the hash routine for IP packets. These could be VLL and VPLS packets without a PW control word.

  • Page 149

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 LSR IP-Only Hash Option Enabled This option behaves like the label-IP hash option except that when the algorithm reached the bottom of the label stack in the ECMP round and finds an IP packet, it throws the outcome of the label hash and only uses the source and destination address fields in the IP packet’s header.

  • Page 150

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Currently, if multiple routers have the same set of ECMP next hops, traffic will use the same nexthop at every router hop. This can contribute to the unbalanced utilization of links. The new hash option avoids this issue. This feature when enabled, enhances the default per-flow hashing algorithm described earlier.

  • Page 151

    Note: Enhanced multicast load balancing is not supported with Layer 2 and ESM services. It is supported on all platforms except for the 7750 SR-c4 and SR-c12 and the 7450 ESS in standard mode. Security Parameter Index (SPI) Load Balancing IPSec tunneled traffic transported over LAG typically falls back to IP header hashing only.

  • Page 152: Per Link Hashing

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 2.6.4.2 Per Link Hashing The hashing feature described in this section applies to traffic going over LAG and MC-LAG. Per link hashing ensures all data traffic on a given SAP or network interface uses a single LAG port on egress. Because all traffic for a given SAP/ network interface egresses over a single port, QoS SLA enforcement for that SAP, network interface is no longer impacted by the property of LAG (distributing traffic over multiple links).

  • Page 153

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Multiple classes allow grouping of SAPs/interfaces/subscribers by similar bandwidth class/type. For example a class can represent: voice – negligible bandwidth, Broadband – 10 to 100 Mb/s, Extreme Broadband – 300 Mb/s and above types of service.

  • Page 154: Explicit Per Link Hash Using Lag Link Mapping Profiles

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Optionally an operator can use a tools perform lag load-balance command to manually re-balance all weighted per-link-hashed SAPs/interfaces/subscribers on a LAG. The rebalance follows the algorithm as used on a link failure moving SAPs/ interfaces/subscribers to different LAG links to minimize SAPs/interfaces/ subscribers impacted.

  • Page 155: Consistent Per Service Hashing

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 • Secondary link—defines a port of the LAG to be used by a SAP/network interface as a backup when the primary link is not available (not configured or down) and the secondary link is UP. •...

  • Page 156

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Per-service-hashing was introduced to ensure consistent forwarding of packets belonging to one service. The feature can be enabled using the [no] per-service- hashing configuration option under config>service>epipe and config>service>vpls, valid for Epipe, VPLS, PBB Epipe, IVPLS and BVPLS. The following behavior applies to the usage of the [no] per-service-hashing option.

  • Page 157: Esm - Lag Hashing Per Vport

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 ISID Hashing Physical Link -------- ----------------------- ------------- per-service(if enabled) 3/2/8 A:Dut-B# tools dump map-to-phy-port lag 11 isid 1 end-isid 4 ISID Hashing Physical Link -------- ----------------------- ------------- per-service(if enabled) 3/2/8 per-service(if enabled) 3/2/7 per-service(if enabled) 1/2/2 per-service(if enabled) 1/2/3...

  • Page 158

    The Vport instances of the same Vport on another member links are irrelevant for QoS treatment. The Vport for Nokia routers is referenced via inter-dest-string, which can be returned via RADIUS. For this reason, the terms hashing per inter-dest-string or hashing per Vport can be interchangeably used.

  • Page 159

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 This feature can be enabled using the CLI command config>subscriber- mgmt>sub-profile>vport-hashing. On the HSMDA, the secondary shaper supports Vport hashing through the config>subscriber-mgmt>sub- profile>secondary-shaper-hashing command. 2.6.4.5.4 Multicast Consideration Multicast traffic that is directly replicated per subscriber follows the same hashing algorithm as the rest of the subscribers (per inter-dest-string hashing).

  • Page 160: Lag Hold Down Timers

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 First the ECMP hash. It consists of an initial hash based on the source port/system IP address. Each label in the stack is then hashed separately with the result of the previous hash, up to a maximum of five labels. The net result will be used to select which LDP FEC next-hop to send the packet to using a modulo operation of the net result with the number of next-hops.

  • Page 161: Bfd Over Lag Links

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 1. Port-level hold-time up/down timer This optional timer allows operator to control delay for adding/removing a port from LAG when the port comes UP/goes DOWN. Each LAG port runs the same value of the timer, configured on the primary LAG link. See the Port Link Dampening description in Port Features for more details on this timer.

  • Page 162: Mixed Port-speed Lag Support

    RELEASE 15.0.R5 2.6.7 Mixed Port-Speed LAG Support Nokia routers support mixing different speed member ports in a single LAG. The LAG must be configured explicitly to allow mixed port-speed operation through the port- weight-speed command. The port-weight-speed defines both the lowest port speed for a member port in that LAG and the type of higher speed ports allowed to be mixed in the same LAG.

  • Page 163

    • PIM lag-usage-optimization is not supported and must not be configured • LAG member links must have the default configuration for config port ethernet egress-rate/ingress-rate • not supported on the 7450 ESS-6V • not supported for ESM Issue: 01 3HE 11968 AAAC TQZZA 01...

  • Page 164: Lag Upgrade

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 2.6.7.1 LAG Upgrade Migrating LAGs to higher speed links involves using mixed-speed LAGs initially, and later removing lower speed links. However, a consequence is that the lower speed links in the mixed-speed LAG set the member link limit. Even after all lower speed links are removed, the higher-speed links maintain a higher weight and this limits how many physical links that a mixed-port speed LAG can include.

  • Page 165: Overview

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Typically, MC-LAG is deployed in a network-wide scenario providing redundant connection between different end points. The whole scenario is then built by combination of different mechanisms (for example, MC-LAG and redundant pseudowire to provide e2e redundant p2p connection or dual homing of DSLAMs in Layer 2/3 TPSDA).

  • Page 166

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 − In case there is a tie in the selection algorithm, for example, two sub-groups with identical aggregate weight (or number of active links) the group which is local to the system with lower system LACP priority and LAG system ID is taken.

  • Page 167

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Figure 41 MC-LAG Layer 2 Dual Homing to Remote PE Pairs PE-A PE-D IP/MPLS MSAN MSAN Network PE-B PE-C PE-A IP/MPLS MSAN PE-C MSAN Network PE-B Fig_6 Issue: 01 3HE 11968 AAAC TQZZA 01...

  • Page 168

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Figure 42 MC-LAG Layer 2 Dual Homing to Local PE-Pairs PE-A MSAN MSAN PE-B PE-A MSAN PE-B MSAN PE-A MSAN PE-B MSAN PE-C Fig_7 The forwarding behavior of the nodes abide by the following principles. Note that logical destination (actual forwarding decision) is primarily determined by the service (VPLS or VLL) and the principle below applies only if destination or source is based on MC-LAG:...

  • Page 169: Mc-lag And Subscriber Routed Redundancy Protocol (srrp)

    Refer to the 7450 ESS, 7750 SR, and VSR Triple Play Service Delivery Architecture Guide for information about SRRP.

  • Page 170

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Figure 43 P2P Redundant Connection Through a Layer 2 VPN Network TLDP Aggregation Aggregation node node Active Standby Active Standby Active Standby Inter-chassis Inter-chassis MSAN MSAN PW for VLL PW for VLL Standby Active Standby Active Aggregation...

  • Page 171: Dslam Dual Homing In Layer 2/3 Tpsda Model

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 2.6.8.4 DSLAM Dual Homing in Layer 2/3 TPSDA Model Figure 44 shows a network configuration where DSLAM is dual homed to pair of redundant PEs by using MC-LAG. Inside the aggregation network redundant-pair of PEs is connecting to VPLS service which provides reliable connection to single or pair of Broadband Service Routers (BSRs).

  • Page 172: Protected Ethernet Tunnels

    ITU-T G.8031 specification to achieve 50 ms resiliency for failures in a native Ethernet backbone. For further information regarding Ethernet tunnels, refer to “G.8031 Protected Ethernet Tunnels” in the 7450 ESS, 7750 SR, 7950 XRS, and VSR Services Overview Guide.

  • Page 173: Protected Ethernet Rings

    Ethernet OAM and often referred to as Ring Automatic Protection Switching (R- APS). For further information regarding Ethernet rings, Refer to “G.8032 Protected Ethernet Rings” in the 7450 ESS, 7750 SR, 7950 XRS, and VSR Services Overview Guide. Issue: 01 3HE 11968 AAAC TQZZA 01...

  • Page 174: Ethernet Port Monitoring

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 2.9 Ethernet Port Monitoring Ethernet ports can record and recognize various medium statistics and errors. There are two main types of errors: • Frame Based — Frame based errors are counted when the arriving frame has an error that means the frame is invalid.

  • Page 175

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 ---------------------------------------------- symbol-monitor sd-threshold 5 multiplier 5 sf-threshold 3 multiplier 5 no shutdown exit show port 2/1/2 ethernet =============================================================================== Ethernet Interface =============================================================================== Description : 2/1/2 Interface : 2/1/2 Oper Speed : N/A Link-level : Ethernet Config Speed : 1 Gbps Admin State...

  • Page 176

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Transceiver Data Transceiver Status : not-equipped =============================================================================== Traffic Statistics =============================================================================== Input Output ------------------------------------------------------------------------------- Octets Packets Errors Utilization (300 seconds) 0.00% 0.00% =============================================================================== =============================================================================== Port Statistics =============================================================================== Input Output ------------------------------------------------------------------------------- Unicast Packets Multicast Packets Broadcast Packets Discards Unknown Proto Discards ===============================================================================...

  • Page 177

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 A port is not returned to service automatically when a port enters the failed condition as a result of crossing a signal failure threshold for both CRC-Monitor and Symbol- Monitor. Since the port is operationally down without a physical link error monitoring stops.

  • Page 178: Ah Oam

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 2.10 802.3ah OAM 802.3ah Clause 57 (efm-oam) defines the Operations, Administration, and Maintenance (OAM) sub-layer, which provides mechanisms useful for monitoring link operation such as remote fault indication and remote loopback control. In general, OAM provides network operators the ability to monitor the health of the network and quickly determine the location of failing links or fault conditions.

  • Page 179

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 The value 00:00:00:00 is sent for all releases that do not support the non-zero value or are unable to identify the required elements. There is no decoding of the peer or local vendor information fields on the network element. The hexadecimal value is included in the show port port-id ethernet efm-oam output.

  • Page 180: Oam Events

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Accounting Policy : None Collect-stats : Disabled Acct Plcy Eth Phys : None Collect Eth Phys : Disabled Egress Rate : Default Ingress Rate : Default Load-balance-algo : Default LACP Tunnel : Disabled Down-when-looped : Disabled Keep-alive : 10...

  • Page 181: Link Monitoring

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 • Link Fault: The PHY has determined a fault has occurred in the receive direction of the local DTE • Dying Gasp: An unrecoverable local failure condition has occurred • Critical Event: An unspecified critical event has occurred The local node can set an unset the various Flag fields based on the operational state of the port, shutdown or activation of the efm-oam protocol or locally raised events.

  • Page 182

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 A degraded condition is raised when the configured signal degrade sd-threshold is reached. This provides a first level log only action indicating a link could become unstable. This event does not affect the port state. The critical failure condition is raised when the configured sf-threshold is reached.

  • Page 183

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 • Window: The size of the unique measurement period for the error type. The window is only checked at the end. There is not mid-window checking. • Threshold: The value of the configured sf-threshold •...

  • Page 184

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Symbol error, errored-symbols, monitoring is also supported but requires specific hardware revisions and the appropriate code release. The symbol monitor differs from the frame error monitors. Symbols represent a constant load on the Ethernet wire whether service frames are present or not.

  • Page 185

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Peer Mac Address : d8:1c:01:02:00:01 Peer Vendor OUI : 00:16:4d (alu) Peer Vendor Info : 00:01:00:02 Peer Mode : active Peer Pdu Size : 1518 Peer Cfg Revision Peer Support : LB Peer Grace Rx : false Loopback State : None...

  • Page 186

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 A clear command “clear port port-id ethernet efm-oam events [local | remote]” has been added to clear port affecting events on the local node on which the command is issued. When the optional [local | remote] options are omitted, both local and remote events will be cleared for the specified port.

  • Page 187: Remote Loopback

    Flag fields in the Information OAMPDU using the info-notifications command options when fault notification to a peer is required. Non-Nokia vendor specific information will not be processed. 2.10.1.1.1 Capability Advertising A supported capability, sometimes requiring activation, will be advertised to the peer.

  • Page 188: Ah Oam Pdu Tunneling For Epipe Service

    2.10.3 802.3ah OAM PDU Tunneling for Epipe Service Nokia routers support 802.3ah. Customers who subscribe to Epipe service treat the Epipe as a wire, so they demand the ability to run 802.3ah between their devices which are located at each end of the Epipe.

  • Page 189

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 procedure for EFM-OAM will clear all remote events that it received from the peer that performed the soft reset. The local events will not be cleared on the peer that has not undergone soft reset. The Information OAM PDU Flag fields are critical in propagating the local event to the peer.

  • Page 190

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Figure 45 Grace TLV Passive Node with Soft Reset Passive Active 1/1/1 2/2/2 Port State: Down Discovery: Start Port State: Down Port State: Up Discovery: Complete Port State: Up Info PDU Info PDU Operator Initiates Info PDU (Grace 900s) ISSU / Soft Reset Info PDU (Grace ACK)

  • Page 191

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Figure 46 Grace TLV Active Node with Soft Reset Passive Active 1/1/1 2/2/2 Port State: Down Discovery: Start Port State: Down Port State: Up Discovery: Complete Port State: Up Info PDU Info PDU Operator Initiates Info PDU (Grace 900s) ISSU / Soft Reset Info PDU (Grace ACK)

  • Page 192

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 The vendor-specific grace function benefits are realized when both peers support the transmitting, receiving and processing of the vendor-specific Grace TLV. In the case of mixed code versions, products, or vendor environments, a standard EFM-OAM message to the peer can be used to instruct the peer to treat the session as failed.

  • Page 193

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 These features do not support the clearing of an IOM which does not trigger a soft reset. IOM clearing is a forceful event that does not trigger graceful protocol renegotiation. A number of show commands have been enhanced to help operators determine the state of the802.3ah OAM Grace function and whether or not the peer is generating or receiving the Grace TLV.

  • Page 194

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Peer Grace Rx • False — Not receiving Grace TLV from the peer • True — Receiving Grace TLV from the peer 3HE 11968 AAAC TQZZA 01 Issue: 01...

  • Page 195: Mtu Configuration Guidelines

    • When the network group encryption (NGE) feature is enabled, additional bytes due to NGE packet overhead must be considered. Refer to the “NGE Packet Overhead and MTU Considerations” section in the 7450 ESS, 7750 SR, 7950 XRS, and VSR Layer 3 Services Guide: IES and VPRN for more information.

  • Page 196: Modifying Mtu Defaults

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Table 34 MTU Default Values (Continued) Port Type Mode Encap Type Default (bytes) SONET path or TDM channel network — 9208 SONET path or TDM channel access frame-relay 1578 SONET path or TDM channel access 1524 Note:...

  • Page 197

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Figure 47 MTU Configuration Example ALA-A ALA-B 1/1/1 Network Network 4/1/1 encap: 2/1/1 3/1/1 encap: null OSSG012 Since ALA-A uses Dot1q encapsulation, the SAP MTU must be set to 1518 to be able to accept a 1514 byte service frame (see Table 34 for MTU default values).

  • Page 198: Deploying Preprovisioned Components

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 2.12 Deploying Preprovisioned Components When a card, CMA, MDA, XCM or XMA is installed in a preprovisioned slot, the device detects discrepancies between the preprovisioned card type configurations and the types actually installed. Error messages display if there are inconsistencies and the card will not initialize.

  • Page 199: Setting Fabric Speed

    The system does not support any FP2 based cards when the chassis is set to fabric- speed-b. Note: For the 7750 SR-7/12 and 7450 ESS-7/12, the chassis must have a manufacturing date of 2008 or later (show chassis detail) to set fabric-speed-b.

  • Page 200: Versatile Service Module

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 2.14 Versatile Service Module 2.14.1 VSM-CCA-XP The VSM-CCA-XP MDA offers a hybrid mode for simplified provisioning and a high capacity VSM when inserted on IOM cards. The complete forwarding path bandwidth (in this case 25 Gb/s) is available, allowing single conversations up to 25 Gb/s on a single MDA.

  • Page 201

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 =============================================================================== *A:PE-1# The following is a sample VSM-CCM-XP configuration for ports: port 1/2/1 ethernet exit no shutdown exit port 1/2/2 ethernet exit no shutdown exit Port and Ethernet QoS parameters may be configured as they are for a physical port. The Ethernet on VSM-CCA-XP has a reduced set of features.

  • Page 202

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 ies 122 customer 1 create interface "Loopback" create address 10.1.1.1/24 sap lag-2:1001 create ingress qos 3 exit egress qos 1010 exit exit exit no shutdown exit 3HE 11968 AAAC TQZZA 01 Issue: 01...

  • Page 203: Configuration Process Overview

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 2.15 Configuration Process Overview Figure 48 displays the process to provision chassis slots, cards, MDAs, and ports. Figure 48 Slot, Card, MDA, and Port Configuration and Implementation Flow Start Chassis Specify Chassis Slot Slot Card Designate the Specific Card Type for the Slot Designate the Specific MDA Type for the Slot...

  • Page 204: Configuration Notes

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 2.16 Configuration Notes The following information describes provisioning caveats: • If a card or MDA type is installed in a slot provisioned for a different type, the card will not initialize. • A card or MDA installed in an unprovisioned slot remains administratively and operationally down until the card type and MDA is specified.

  • Page 205: Configuring Physical Ports With Cli

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 2.17 Configuring Physical Ports with CLI This section provides information to configure cards, MDAs, and ports. 2.17.1 Preprovisioning Guidelines SR OSs have a console port, either located on the CPM or CCM, or integrated into the chassis (on the 7750 SR-c4 models), to connect terminals to the router.

  • Page 206: Maximizing Bandwidth Use

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 − Configure an access port for customer facing traffic on which services are configured. An encapsulation type may be specified in order to distinguish services on the port or channel. Encapsulation types are not required for network ports. To configure an Ethernet access port, see Ethernet Access Port.

  • Page 207: Basic Configuration

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 2.17.2 Basic Configuration The most basic configuration must specify the following: • chassis slot • line card type (must be an allowed card type) • MCM slot for the 7750 SR-c4 and SR-c12 only (not required for CMA) •...

  • Page 208

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 card-type iom-xp mcm 1 mcm-type mcm-xp no shutdown exit mcm 3 mcm-type mcm-xp no shutdown exit mcm 7 mcm-type mcm-xp no shutdown exit mda 1 mda-type m4-choc3-as-sfp no shutdown exit mda 3 mda-type m8-oc3-sfp no shutdown exit mda 5...

  • Page 209: Common Configuration Tasks

    Card configurations include a chassis slot designation. A slot must be preconfigured with the type of cards and MDAs which are allowed to be provisioned. The following example shows card and MDA configurations for the 7750 SR or 7450 ESS: #-------------------------------------------------- ‘echo "Card Configuration"...

  • Page 210

    (optional) to create and edit QoS pool resources on egress network ports, channels, and ingress MDAs. Network-queue and slope policies are configured in the config>qos context. The following example shows an MDA pool configuration for 7750 SR or 7450 ESS: A:ALA-B>config>card>mda# info ----------------------------------------------...

  • Page 211: Configuring Cards, Mcms, And Mcas

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 2.17.3.1.2 Configuring MDA Policies for Named Pools Mode Network ingress queues can use either MDA ingress named pools or ingress default pools but not port named pools. In the case with an IOM with multiple MDAs sharing the same buffer space (iom3-xp), network ingress queues will use only the MDA 1 named pools.

  • Page 212: Configuring Ports

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 2.17.3.2.1 Configuring Cards and CMAs Card configurations must include a chassis slot designation. A slot must be preconfigured with the type of cards and CMAs (Compact Media Adapters) which are allowed to be provisioned. CMAs are configured using the MDA command.

  • Page 213

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Normally, the amount of active bandwidth is considered as opposed to total potential bandwidth for the port when determining the ports fair share. If a port is channelized and not all bandwidth is allocated, only the bandwidth represented by the configured channels with queues configured is counted towards the bandwidth represented by the port.

  • Page 214

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 • All queues defined for a port receive buffers from the same buffer pool. The Named Buffer Pools feature offers the following new capabilities: • Ability to modify the port bandwidth considered for buffer allocation without changing the active port bandwidth.

  • Page 215

    20 network 40 2.17.3.3.3 Changing APS Parameters Note: Nokia recommends grouping working lines and protect lines on separate IOMs. APS configuration rules: • A working port must be added first. Then a protection port can be added or removed at any time.

  • Page 216

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 The following shows a sample configuration for an ATM SC-APS group that contains an aPipe SAP: A:ALA-274>config# port (1/1/1) ---------------------------------------------- sonet-sdh speed oc3 exit no-shutdown ---------------------------------------------- A:ALA-274>config>port# aps-1 ---------------------------------------------- working-circuit 1/1/1 protect-circuit 1/1/2 exit sonet-sdh path exit...

  • Page 217

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 neighbor 13.1.1.1 protect-circuit 2/2/2 exit no shutdown ---------------------------------------------- A:ALA-274>config>port# 2.17.3.3.4 Configuring Ethernet Port Parameters Ethernet Network Port A network port is network facing and participates in the service provider transport or infrastructure network processes. The following example shows a network port configuration: A:ALA-B>config>port# info ----------------------------------------------...

  • Page 218

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 slope-policy "slopePolicy2" exit exit exit ethernet mode access encap-type dot1q exit no shutdown ---------------------------------------------- A:ALA-A>config>port# Configuring 802.1x Authentication Port Parameters The following example shows an 802.1x port configuration: A:ALA-A>config>port>ethernet>dot1x# info detail ---------------------------------------------- port-control auto radius-plcy dot1xpolicy re-authentication re-auth-period 3600...

  • Page 219

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 • ATM OC-12 • Channelized ASAP OC3 • Channelized ASAP OC12 When an Ethernet port is configured in WAN mode (xgig wan), you can change certain SONET/SDH parameters to reflect the SONET/SDH requirements for this port.

  • Page 220

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 SONET/SDH Access Port The following example shows a SONET/SDH access port configuration for the 7750 SR: A:ALA-A>config>port# info ---------------------------------------------- description "SONET/SDH access port" sonet-sdh path mode access encap-type frame-relay mac 00:03:47:c8:b4:86 frame-relay exit no shutdown exit exit no shutdown...

  • Page 221

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Table 36 Channelization Options Available on the 7750 SR Channelized MDAs (Continued) Framing Channelization/Mapping Option Channelized MDAs Supporting Services on the Port/ Channel STM4>AUG4>AUG1>VC4>TUG3>VC3 m1-choc12 m4-choc3 m12-chds3 m4-choc3-as STM4>AUG4>AUG1>VC3 m1-choc12 m4-choc3 m12-chds3 m4-choc3-as SONET OC12>STS12>STS1 SPE m1-choc12 m4-choc3...

  • Page 222

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Table 36 Channelization Options Available on the 7750 SR Channelized MDAs (Continued) Framing Channelization/Mapping Option Channelized MDAs Supporting Services on the Port/ Channel STM4>AUG4>AUG1>VC4>TUG3>VC3>DS3 m1-choc12 m4-choc3 m12-chds3 m4-choc3-as STM4>AUG4>AUG1>VC3>DS3 m1-choc12 m4-choc3 m12-chds3 m4-choc3-as SONET OC12>STS12>STS1 SPE>VT GROUP>VT2 SPE m1-choc12 m4-choc3...

  • Page 223

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Table 36 Channelization Options Available on the 7750 SR Channelized MDAs (Continued) Framing Channelization/Mapping Option Channelized MDAs Supporting Services on the Port/ Channel STM4>AUG4>AUG1>VC3>TUG2>VC12 m1-choc12 m4-choc3 m12-chds3 m4-choc3-as STM4>AUG4>AUG1>VC4>TUG3>VC3>DS3 m1-choc12 m4-choc3 m12-chds3 m4-choc3-as STM4>AUG4>AUG1>VC3>DS3 m1-choc12 m4-choc3 m12-chds3...

  • Page 224

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Table 37 Channelized Port Syntax Examples Port ID for Physical Port Speed Channel OC12/STM4 OC3/STM1 DS3/E3 speed SONET/SDH STS12/STM4 port.sts12 STS3/STM1 port.sts3-{1 to 4} port.sts3 STS1/STM0 port.sts1-{1 to 4}.{1 to 3} port.sts1-{1 to 3} TUG3 port.tug3-{1 to 4}.{1 to 3} port.tug3-{1 to 3}...

  • Page 225

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Verify the MDA Type To make sure that you have a channel-capable MDA, verify that the MDA-type you are configuring by entering a show mda slot-id command. The MDAs shown in the MDA Provisioned column in the following output are a 12- port channelized DS3 MDA (m12-ds3) on card 1, MDA slot 1, and a 1-port channelized OC12-SFP MDA (m1-choc12-sfp) on card 1, MDA slot 2.

  • Page 226

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Figure 49 Channelized DS3 Port Structure The following shows the steps to configure a channelized port on a 12-port DS3 MDA: A:ALA-A>config# port 7/1/1 A:ALA-A>config>port# tdm In order to set the channelized mode on a port, the DS3 parameter must be in a shut down state.

  • Page 227

    Services can be applied to the configured channelized ports. The following example shows the CLI usage to configure a customer IES service with interface SAPs on the channelized ports. Refer to the 7450 ESS, 7750 SR, 7950 XRS, and VSR Services Overview Guide for information about how to configure services.

  • Page 228

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 A:ALA-A>config>service# ies 103 customer 1 create A:ALA-A>config>service>ies$ interface test1 create A:ALA-A>config>service>ies>if$ address 102.21.1.1/24 A:ALA-A>config>service>ies>if# sap 7/1/1.1.2 create A:ALA-A>config>service>ies>if>sap$ exit A:ALA-A>config>service>ies>if# no shutdown A:ALA-A>config>service>ies>if# exit A:ALA-A>config>service>ies# interface test2 create A:ALA-A>config>service>ies>if$ address 102.22.1.1/24 A:ALA-A>config>service>ies>if$ sap 7/1/1.2.1 create A:ALA-A>config>service>ies>if>sap$ exit A:ALA-A>config>service>ies>if# no shutdown A:ALA-A>config>service>ies>if# exit...

  • Page 229

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Figure 50 Channelized OC-12 Port Structure The following shows an example to configure a channelized port on a 1-port channelized OC-12-SFP MDA: ALA-A>config# port 5/2/1 At this level you must choose the tributary. When provisioning DS3 nodes on a channelized OC-12 MDA, you must provision the parent STS1-1 SONET path first.

  • Page 230

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 In order to set the channelized mode on a port, the DS3 parameter must be in a shut down state. Clear channel uses out-of-band signaling, not in-band signaling, so the channel's entire bit rate is available. Channelized ports use in-band signaling and must be explicitly enabled.

  • Page 231

    Services can be applied to the configured channelized ports. The following example shows the CLI usage to configure a customer IES service with interface SAPs on the channelized ports. Refer to the 7450 ESS, 7750 SR, 7950 XRS, and VSR Services Overview Guide for information about how to configure services.

  • Page 232

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 ---------------------------------------------- interface "testA" create address 192.22.1.1/24 sap 5/2/1.1.1.1.1 create exit exit interface "testB" create address 192.23.1.1/24 sap 5/2/1.1.1.1.2 create exit exit no shutdown ---------------------------------------------- A:ALA-A>config>service>ies# Configuring a Channelized Any Service Any Port (ASAP) OC3-SFP Port This section provides examples to configure PPP, FR, cHDLC, and ATM n*DS0 channels on a channelized port on channelized ASAP OC-3 SFP MDA in slot 1/1/1.

  • Page 233

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 A:ALA-A>config>port>tdm>ds3# no shutdown A:ALA-A>config>port>tdm>ds3# exit A:ALA-A>config>port# info ---------------------------------------------- sonet-sdh path sts1-1 no shutdown exit exit ds3 1 channelized e1 no shutdown exit exit no shutdown ---------------------------------------------- A:ALA-A>config>port# In the TDM E1 context, configure DS0 channel groups and their parameters. For a DS1 channel-group, up to 24 timeslots can be assigned (numbered 1 to 24).

  • Page 234

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 e1 1.1 channel-group 1 timeslots 2 no shutdown exit channel-group 2 encap-type frame-relay frame-relay exit timeslots 10 no shutdown exit channel-group 3 encap-type cisco-hdlc cisco-hdlc exit timeslots 11,12 no shutdown exit no shutdown exit e1 1.2 channel-group 1 encap-type atm...

  • Page 235

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 encap-type {bcp-null|bcp-dot1q|ipcp|ppp- auto|frame-relay|wan-mirror|cisco- hdlc} timeslots timeslots no shutdown The following example shows SONET/SDH access mode configuration command usage: Example: A:ALA-29>config>port>tdm# ds3 A:ALA-29>config>port>tdm>ds3# channelized ds1 A:ALA-29>config>port>tdm>ds3# no shutdown A:ALA-29>config>port>tdm>ds3# exit A:ALA-29>config>port>tdm# ds1 1 A:ALA-29>config>port>tdm>ds1# no shutdown A:ALA-29>config>port>tdm>ds1# channel-group 1 A:ALA-29>config>port>tdm>ds1>channel-group# timeslots 1- A:ALA-29>config>port>tdm>ds1>channel-group# encap-type...

  • Page 236

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 2.17.3.3.7 Configuring Channelized STM1/OC3 Parameters The following example shows basic syntax to configure channelized STM1/OC3 parameters: CLI Syntax: config# port port-id sonet-sdh framing {sonet|sdh} group sonet-sdh-index payload {tu3|vt2|vt15} path [sonet-sdh-index] payload {sts3|tug3|ds3|e3} trace-string [trace-string] no shutdown Example: config# port 5/2/1...

  • Page 237

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 group tug3-3 payload vt2 path vt2-1.1.1 trace-string "LO-path 3.7.3" no shutdown exit path vt2-3.7.3 no shutdown exit exit e1 1.1.1 channel-group 1 timeslots 2-32 no shutdown exit no shutdown exit e1 3.7.3 channel-group 2 timeslots 2-32 no shutdown exit...

  • Page 238

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 BERT Errors BERT Status : idle BERT Total Bits Cfg Alarm : ais los Alarm Status =============================================================================== A:sim216# Configuring a Channel Group The following shows an example of a DS1 channel group configured for CES. A:sim216# show port 1/5/1.1.3.1 ===============================================================================...

  • Page 239

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 ATM SAP in an Epipe Service The following shows a sample Epipe service SAP configuration: B:ALA-701>config>service# info ---------------------------------------------- epipe 5 customer 1 create shutdown sap 2/1/2:15/25 create exit sap 2/1/3:25/35 create exit exit ---------------------------------------------- B:ALA-701>config>service# 2.17.3.3.9 Configuring DWDM Port Parameters...

  • Page 240

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 *A:ALA-A>config>port>dwdm>wavetracker># info detail ---------------------------------------------- power-control target-power -7.50 exit encode key1 205 key2 749 report-alarm enc-fail enc-degr pwr-fail pwr-degr pwr-high pwr-low ---------------------------------------------- 2.17.3.3.10 Configuring WaveTracker Parameters The following example shows the default configuration with WaveTracker disabled: *A:ALA-A>config>port>dwdm># info ---------------------------------------------- channel 44...

  • Page 241

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 exit rxdtv-adjust ---------------------------------------------- *A:ALA-A>config>port>dwdm># wavetracker *A:ALA-A>config>port>dwdm>wavetracker># info ---------------------------------------------- power-control target-power -7.50 exit encode key1 205 key2 749 ---------------------------------------------- *A:ALA-A>config>port>dwdm>wavetracker># info detail ---------------------------------------------- power-control target-power -7.50 exit encode key1 205 key2 749 report-alarm enc-fail enc-degr pwr-fail pwr-degr pwr-high pwr-low ---------------------------------------------- The following is an example of the show port <portId>...

  • Page 242

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 1001 1004 1018 1021 1035 1038 1052 1055 1069 1072 1086 1089 1103 1573 1587 1106 1120 1590 1604 1123 1137 1607 1621 1140 1154 1624 1638 1157 1171 1641 1655 1174 1188 1658 1672 1191 1205...

  • Page 243

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 3704 3718 2168 2182 3721 3735 2185 2199 3738 3752 2202 2216 3755 3769 2219 2233 3772 3786 2236 2250 3789 3803 2253 2267 3806 3820 2270 2284 3823 3837 2287 2301 3840 3854 2304 2318 3857...

  • Page 244

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 exit ---------------------------------------------- The following example shows the show port <portId> otu detail for the default OTU configuration as shown above: *A:ALA-A# show port 3/2/1 otu detail =============================================================================== OTU Interface =============================================================================== OTU Status : Enabled FEC Mode : enhanced Async Mapping...

  • Page 245

    ATM interface parameters can only be configured for SONET/SDH ports/paths and TDM ports/channels supporting ATM encapsulation, and for IMA multilink bundles. ATM interface parameters allow users to configure characteristics of an ATM interface. The Nokia routers support configuration of the following ATM interface characteristics: Issue: 01...

  • Page 246

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 • Cell-format — Allows user to select the ATM cell format to be used on a given interface: UNI/NNI • ILMI — Allows user to enable/disable ILMI protocol • Traffic-desc — Allows user to configure ILMI PVCC TM characteristics over a given ATM interface ingress and egress direction characteristics can be configured separately) •...

  • Page 247

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Table 39 Alarm State Interactions (Continued) Content of the Received Signal Status Field Values Prob Prob Down Lower Far End Layer Alarm Rx Down Prob None Lower Incoming Layer Down Prob Prob Down Lower Incoming Layer Down...

  • Page 248

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 ATM Interface Configurations Use the following CLI syntax to configure ATM interface parameters for SONET/SDH paths: CLI Syntax: config# port port-id sonet-sdh path [sonet-sdh-index] cell-format cell-format ilmi [vpi/vci] egress traffic-desc traffic-desc- profile-id ingress traffic-desc traffic-desc- profile-id keep-alive [poll-frequency seconds] [poll-count value]...

  • Page 249

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 channel-group 1 cell-format cell-format min-vp-vpi value e3 [sonet-sdh-index] cell-format cell-format min-vp-vpi value 2.17.3.3.13 Configuring Frame Relay Parameters Frame Relay pipes are used to provide customer-to-customer Frame Relay PVCs or to interconnect individual Frame Relay clouds. Frame Relay parameters can only be configured in SONET/SDH and channelized TDM MDA contexts.

  • Page 250

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 frame-relay lmi-type itu mode dte n393dce 4 n393dte 4 n391dte 6 n392dce 3 n392dte 3 t391dte 10 t392dce 15 exit no shutdown exit exit exit no shutdown ---------------------------------------------- A:ALA-7>config>port# SONET/SDH Interfaces This section applies also to FR interfaces on Sonet/SDH high-speed channels on ASAP MDAs.

  • Page 251: Configuring Multilink Ppp Bundles

    "OC-3/OC-12 SONET/SDH" mode access encap-type frame-relay no mtu no mac crc 32 no scramble trace-string "Nokia 7750 ALA-" report-alarm plop pplm puneq no report-alarm pais prdi prei signal-label 0xcf frame-relay lmi-type itu mode dte n393dce 4 n393dte 4...

  • Page 252

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Multilink bundling operations are modeled after a virtual PPP link-layer entity where packets received over different physical link-layer entities are identified as belonging to a separate PPP network protocol (the Multilink Protocol, or MP) and recombined and sequenced according to information present in a multilink fragmentation header.

  • Page 253

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Configuration notes: An IMA group has common interface characteristics (for example, configuration that applies to a logical ATM interface either configured via the IMA group context or taken from the primary link) The following list details those common IMA group interface characteristics: •...

  • Page 254

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 • IMA group maximum bandwidth and minimum link settings allows, by default, for over-subscription of shaped services; however when that occurs scheduling of traffic over an IMA group ATM interface degrades to round-robin between shaped services, therefore to preserve full ATM TM even during a member link failure, it is recommended that maximum bandwidth is set to minimum links.

  • Page 255

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 2.17.3.3.16 Multi-Class MLPPP The following guidelines apply to multi-class MLPPP: • MC-MLPPP must be configured before links are added to a bundle. • MC-MLPPP and LFI (config>port>ml-bundle>interleave-fragments) are mutually exclusive. • MC-MLPPP is not supported when port is configured as network mode. •...

  • Page 256

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 1. The test procedure is performed as defined by the IMA specification version 1.1, i.e. a test pattern is sent over the specified link and is expected to be looped back over all the links in the group. ICP cells are used to perform the test. 2.

  • Page 257

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 config>card# mda 2 config>card>mda# mda-type m4-choc3-as-sfp config>card>mda# no shutdown config>card>mda# exit Configure an APS group with working and protection circuits on the ASAP MDAs. Example: config# port aps-1 config>port# aps config>port>aps# working-circuit 3/2/1 config>port>aps# protect-circuit 10/2/1 config>port>aps# exit config>port# no shutdown Create eight ATM DS1 channels on the APS group.

  • Page 258

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 config>port>multilink-bundle# protect-bundle bundle-ima- 2/1.1 config>port>multilink-bundle# member aps-1.1.1.1 config>port>multilink-bundle# member aps-1.1.2.1 config>port>multilink-bundle# member aps-1.1.3.1 config>port>multilink-bundle# member aps-1.1.4.1 config>port>multilink-bundle# member aps-1.1.5.1 config>port>multilink-bundle# member aps-1.1.6.1 config>port>multilink-bundle# member aps-1.1.7.1 config>port>multilink-bundle# member aps-1.1.8.1 config>port>multilink-bundle# exit config>port>multilink-bundle# no shutdown config>port>multilink-bundle# exit config>port# no shutdown Finally, a service can be configured on this bundle using the BPGrp ID (for example, an ATM VC 0/32 SAP would be: sap bpg-ima-1:0/32).

  • Page 259

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 − To increase the BPGrp robustness, it is recommended to provision more IMA/MLPPP links than is required and set the minimum links and max bandwidth parameters to the number of required links. This type of configuration is required on the far end as well.

  • Page 260

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Hardware Data Part number : Sim Part# CLEI code : Sim CLEI Serial number : mda-7 Manufacture date : 01012003 Manufacturing string : Sim MfgString mda-7 Manufacturing deviations : Sim MfgDeviation mda-7 Administrative state : up Operational state : up...

  • Page 261

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 no shutdown exit channel-group 2 encap-type frame-relay frame-relay exit timeslots 10 no shutdown exit channel-group 3 encap-type cisco-hdlc cisco-hdlc exit timeslots 11,12 no shutdown exit no shutdown exit e1 1.2 channel-group 1 encap-type atm exit no shutdown exit...

  • Page 262

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 port 1/5/1 port 1/7/1 port 1/9/1 dynamic-cost port-threshold 4 action down ---------------------------------------------- A:ALA-A>config>lag# Configuring BFD on LAG Links BFD can be configured under the LAG context to create and establish the micro-BFD session per link after the LAG and associated links have been configured. An IP interface must be associated with the LAG or a VLAN within the LAG, if dot1q encapsulation is used, before the micro-BFD sessions can be established.

  • Page 263

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 • Max-Time-Admin-Down - This parameter controls how long the system will wait before bringing the associated link out of service if an admin down message is received from the far-end. The following is a sample configuration: *A:Dut-C>config>lag# info ---------------------------------------------- family ipv4...

  • Page 264

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 • The operator can update these port parameters only if the port is the sole member of an Ethernet tunnel. This means that in the example below, the operator needs to remove port 1/1/4 and port 1/1/5 before being allowed to modify 1/1/1 for the above parameters.

  • Page 265

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 no shutdown Issue: 01 3HE 11968 AAAC TQZZA 01...

  • Page 266: Service Management Tasks

    MDA,MCM, CMA, or the XMA from the configuration. To modify or delete CMAs or XMAs, use the MDA command structure. Use the following CLI syntax to modify an MDA on the 7450 ESS and 7750 SR platforms (or an XMA on the 7950 XRS platforms): CLI Syntax: config>...

  • Page 267: Deleting A Card

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 You must reset the IOM after changing the MDA type from MS-ISA to any other MDA type. Use the following CLI syntax to modify a card type already provisioned for a specific slot: CLI Syntax: config>...

  • Page 268: Deleting Port Parameters

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 2.18.4 Deleting Port Parameters Use the following CLI syntax to delete a port provisioned for a specific card or CMA: CLI Syntax: config>port port-id shutdown no port port-id 2.18.5 Soft IOM Reset This section provides basic procedures for soft IOM reset service management tasks.

  • Page 269: Deferred Mda Reset

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Although the majority of protocols stay up during a Soft Reset, there are some limitations for a few protocols. Refer to Known Limitations in the Release Notes for the relevant release for details. Configuration changes are not allowed while any card is in the process of a soft reset. The soft IOM reset procedure is applicable during the ISSU process and for a manual soft reset procedure.

  • Page 270

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 If the MDA/IMM is not hard reset by the operator, and then a software upgrade is performed, and the older firmware is no longer compatible with the newest load being upgraded to, then the soft reset will be blocked (or an automatic hard reset will occur for Major ISSU).

  • Page 271: Configuration Command Reference

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 2.19 Configuration Command Reference 2.19.1 Command Hierarchies • Card Commands • MCM Commands • MDA Commands • Power Commands • Virtual Scheduler Commands • Forwarding Plane (FP) Commands • Port Configuration Commands • Port XC Commands •...

  • Page 272: Mcm Commands

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 — [no] reset-on-recoverable-error 2.19.1.2 MCM Commands config — [no] card slot-number — [no] mcm-slot — mcm-type mcm-type — no mcm-type — [no] shutdown 2.19.1.3 MDA Commands config — [no] card slot-number — [no] mda-slot —...

  • Page 273: Power Commands

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 — ingress-xpl — threshold threshold — window window — mda-type mda-type — no mda-type — named-pool-mode — egress — named-pool-policy policy-name — no named-pool-policy — ingress — named-pool-policy policy-name — no named-pool-policy — network —...

  • Page 274: Virtual Scheduler Commands

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 — [no] peq-slot [chassis chassis-id] — peq-type peq-type — no peq-type — input-power-mode amperage — [no] shutdown — power-safety-alert wattage — power-safety-level percent 2.19.1.5 Virtual Scheduler Commands config — [no] card slot-number — virtual-scheduler-adjustment —...

  • Page 275

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 — accounting-policy acct-policy-id — no accounting-policy — [no] collect-stats — description description-string — no description — policer-control-override [create] — no policer-control-override — max-rate {rate | max} — priority-mbs-thresholds — min-thresh-separation size [bytes | kilobytes] —...

  • Page 276: Port Configuration Commands

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 — no policer policer-id — {size [bytes | kilobytes] | default} — no — {size [bytes | kilobytes] | default} — no — packet-byte-offset{add bytes | subtract bytes} — no packet-byte-offset — rate {max | kilobits-per-second} [cir {max | kilobits-per-second}] —...

  • Page 277

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 — [no] report-alarms [ild] [tmp] [mth] [mtl] [los] [lop] [com] — channel channel — coherent — channel channel — compatibility mode — cpr-window-size window-size — dispersion dispersion — mode {automatic | manual} — report-alarms [modflt] [mod] [netrx] [nettx] [hosttx] —...

  • Page 278

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 — resv-cbs percent-or-default amber-alarm-action step percent max [percentage] — resv-cbs percent-or-default — no resv-cbs — slope-policy name — no slope-policy — [no] — [no] async-mapping — {enhanced | g709} — no — otu2-lan-data-rate {11.049 | 11.0957} —...

  • Page 279: Port Xc Commands

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 — mismatch-reaction {squelch-rx} — no mismatch-reaction — auto-generated — bytes byte-string [byte-string] — string identifier — no — [no] shutdown 2.19.1.8 Port XC Commands config — port-xc — pxc-id [create] — no pxc-id — description description-string —...

  • Page 280: Ethernet Commands

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 — — advertise-interval advertise-interval — no advertise-interval — hold-time hold-time — no hold-time — hold-time-aps [lsignal-failure sf-time] [lsignal-degrade sd-time] — no hold-time-aps — [no] mode-annexb — neighbor ip-address — no neighbor — protect-circuit port-id —...

  • Page 281

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 — max-peer max-peer — no max-peer — [no] rx-must-be-encrypted — [no] shutdown — port-control {auto | force-auth | force-unauth} — quiet-period seconds — radius-plcy name — no radius-plcy — re-auth-period seconds — no re-auth-period —...

  • Page 282

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 — sf-threshold errored-frames — [no] shutdown — window packets — errored-frame-seconds — [no] event-notification — sd-threshold errored-seconds — no sd-threshold — sf-threshold errored-seconds — [no] shutdown — window deciseconds — errored-symbols — [no] event-notification —...

  • Page 283

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 — max-rate rate — no max-rate — scheduling-class class rate rate — scheduling-class class weight weight-in-group — no scheduling-class class — hs-scheduler-policy policy-name — no hs-scheduler-policy — hs-secondary-shaper secondary-shaper-name [create] — no hs-secondary-shaper secondary-shaper-name —...

  • Page 284

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 — [no] ccm-enable — ccm-ltm-priority priority — no ccm-ltm-priority — ccm-padding-size ccm-padding — no ccm-padding-size — ccm-tlv-ignore [port-status] [interface-status] — no ccm-tlv-ignore — collect-lmm-stats — no collect-lmm-stats — [no] csf-enable — multiplier multiplier-value — no multiplier —...

  • Page 285

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 — ieee-address — no — min-frame-length byte-length — mode {access | network | hybrid} — no mode — [no] mon-port-sch — mtu-bytes — no — pbb-etype [ethertype-value] — no pbb-etype — ptp-asymmetry nanoseconds — no ptp-asymmetry —...

  • Page 286

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 — [no] queue-group queue-group-name [create] [instance instance-id] — accounting-policy acct-policy-id — no accounting-policy — [no] agg-rate — [no] limit-unused-bandwidth — [no] queue-frame-based-accounting — rate kilobits-per-second — no rate — [no] collect-stats — description description-string —...

  • Page 287

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 — no host-match dest destination-string — [no] mon-port-sch — port-scheduler-policy port-scheduler-policy-name — no port-scheduler-policy — ingress — [no] queue-group queue-group-name [create] — accounting-policy acct-policy-id — no accounting-policy — [no] collect-stats — description description-string — no description —...

  • Page 288: Interface Group Handler Commands

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 — [no] hs-turbo — queue-overrides — queue queue-id [create] — no queue queue-id — adaptation-rule [pir {max | min | closest}] [cir {max | min | closest}] — no adaptation-rule — size-in-kbytes — no —...

  • Page 289

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 — no max-bandwidth — test-pattern-procedure — [no] shutdown — test-link port-id — no test-link — test-pattern pattern — no test-pattern — version IMA-version — no version — [no] interleave-fragments — [no] member port-id — minimum-links minimum-links —...

  • Page 290: Sonet-sdh Commands

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 — no qos-profile — [no] magic-number — multiclass count — no multiclass — [no] stateless-aps-switchover — mrru mrru — no mrru — [no] protect-bundle bundle-id — red-differential-delay red-diff-delay [down] — no red-differential-delay — [no] short-sequence —...

  • Page 291

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 — ilmi [vpi/vci] — no ilmi — egress — traffic-desc traffic-desc-profile-id — no traffic-desc — ingress — traffic-desc traffic-desc-profile-id — no traffic-desc — keep-alive [poll-frequency seconds] [poll-count value] [test-frequency seconds] — no keep-alive — protocol protocol-type —...

  • Page 292: Tdm Commands

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 — no n393dce — n393dte count — no n393dte — t391dte keepalive — no t391dte — t392dce keepalive — no t392dce — load-balancing-algorithm option — no load-balancing-algorithm — ieee-address — no — mode {access | network | hybrid} —...

  • Page 293

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 — no bert — bit-error-insertion rate — no bit-error-insertion — [no] channel-group channel-group — — cell-format cell-format — min-vp-vpi value — cisco-hdlc — down-count down-count — no down-count — keepalive time-interval — no keepalive —...

  • Page 294

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 — no idle-cycle-flag — idle-payload-fill {all-ones} — idle-payload-fill pattern pattern — no idle-payload-fill — idle-signal-fill {all-ones} — idle-signal-fill pattern pattern — no idle-signal-fill — load-balancing-algorithm option — no load-balancing-algorithm — ieee-address — no — [no] mode {access | network} —...

  • Page 295: Ds3 Commands

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 2.19.1.16 DS3 Commands config — [no] port {port-id} — — [no] [sonet-sdh-index] — — cell-format cell-format — mapping mapping — min-vp-vpi value — bert {2e3 | 2e9 | 2e11 | 2e15 | 2e20 | 2e20q | 2e23 | ones | zeros | alternating} duration duration —...

  • Page 296: E1 Commands

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 — n392dce threshold — no n392dce — n392dte threshold — no n392dte — n393dce count — no n393dce — n393dte count — no n393dte — t391dte keepalive — no t391dte — t392dce keepalive — no t392dce —...

  • Page 297

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 — bit-error-insertion rate — no bit-error-insertion — [no] channel-group channel-group-id — — cell-format cell-format — min-vp-vpi value — cisco-hdlc — down-count down-count — no down-count — keepalive time-interval — no keepalive — up-count up-count —...

  • Page 298: E3 Commands

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 — idle-payload-fill pattern pattern — no idle-payload-fill — idle-signal-fill {all-ones} — idle-signal-fill pattern pattern — no idle-signal-fill — load-balancing-algorithm option — no load-balancing-algorithm — ieee-address — no — [no] mode {access | network} — mtu-bytes —...

  • Page 299

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 — cell-format cell-format — min-vp-vpi value — bert {2e3 | 2e9 | 2e11 | 2e15 | 2e20 | 2e20q | 2e23 | ones | zeros | alternating} duration duration — no bert — bit-error-insertion rate —...

  • Page 300: Lag Commands

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 — no t392dce — framing (E-3) {g751 | g832 | e3-unframed} — idle-cycle-flag {flags | ones} — no idle-cycle-flag — load-balancing-algorithm option — no load-balancing-algorithm — loopback {line | internal} — no loopback — ieee-address —...

  • Page 301

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 — receive-interval interval — no receive-interval — remote-ip-address ip-address — no remote-ip-address — shutdown — no shutdown — transmit-interval interval — no transmit-interval — description long-description-string — no description — [no] dynamic-cost — encap-type {dot1q | null | qinq} —...

  • Page 302

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 — [no] rx-eth-vsm-grace — [no] tx-eth-vsm-grace — low-priority-defect {allDef | macRemErrXcon | remErrXcon | errXcon | xcon | noXcon} — mac-address mac-address — no mac-address — one-way-delay-threshold seconds — [no] shutdown — hold-time down hold-down-time —...

  • Page 303: Macsec Commands

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 2.19.1.20 MACsec Commands config — macsec — connectivity-association ca-name [create] — no connectivity-association ca-name — cipher-suite {type} — no cipher-suite — clear-tag-mode clear-tag-mode — no clear-tag-mode — description description — no description — encryption-offset {encryption-offset} —...

  • Page 304

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 — no path-threshold — [no] path path-index — control-tag qtag[.qtag] — no control-tag — description description-string — no description — eth-cfm — [no] mep-id domain md-index association ma-index — alarm-notification — fng-alarm-time time — fng-reset-time time —...

  • Page 305: Multi-chassis Redundancy Commands

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 2.19.1.22 Multi-Chassis Redundancy Commands config — redundancy — bgp-multi-homing — boot-timer seconds — no boot-timer — site-activation-timer seconds — no site-activation-timer — site-min-down-timer seconds — no site-min-down-timer — multi-chassis — peer ip-address [create] — [no] peer ip-address —...

  • Page 306: Configuration Command Descriptions

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 — no interface — service-id service-id — no service-id — [no] path-b — [no] range vlan-range — [no] path-excl — [no] range vlan-range — ring-node ring-node-name [create] — no ring-node ring-node-name — connectivity-verify — dst-ip ip-address —...

  • Page 307: Generic Commands

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 • Power Commands • Virtual Scheduler Commands • Forwarding Plane Configuration Commands • General Port Commands • Port XC Commands • APS Commands • Ethernet Port Commands • 802.1x Port Commands • LLDP Port Commands •...

  • Page 308

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 config>port>ethernet>network>egr>qgrp config>port>ethernet>egress>hs-secondary-shaper config>port-xc>px config>redundancy>multi-chassis>peer Description This command creates a text description for a configuration context to help identify the content in the configuration file. The no form of this command removes any description string from the context. This command is supported on TDM satellite.

  • Page 309

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Context config>card config>card>mda config>interface-group-handler config>port config>port>ethernet config>port>sonet-sdh>path config>port>tdm>ds1 config>port>tdm>ds1>channel-group config>port>tdm>ds3 config>port>tdm>e1 config>port>tdm>e1>channel-group config>port>tdm>e3 config>port>ml-bundle>ima>test-pattern-procedure config>port>sonet-sdh>path>atm>ilmi config>lag config>port>ethernet>dampening config>port>ethernet>eth-cfm>mep config>port>ethernet>efm-oam config>redundancy>multi-chassis>peer config>redundancy>mc>peer>mcr config>redundancy>mc>peer>mc-lag config>redundancy>mc>peer>mcr>ring config>redundancy>mc>peer>mcr>node>cv config>redundancy>multi-chassis>peer>sync Description This command administratively disables an entity. When disabled, an entity does not change, reset, or remove any configuration settings or statistics.

  • Page 310: Card Commands

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 2.19.2.2 Card Commands card Syntax [no] card slot-number Context config Description This mandatory command enables access to the chassis card Input/Output, Control Forwarding Module (IOM/CFM), slot, MCM, MDA, XCM and XMA CLI contexts. The no form of this command removes the card from the configuration. All associated ports, services, and MDAs must be shutdown.

  • Page 311

    Failed. This Failed state will persist until the clear card command is issued (reset) or the card is removed and re-inserted (re-seat). If the condition persists after re-seating the card, then Nokia support should be contacted for further investigation. Issue: 01...

  • Page 312

    • CHASSIS event ID# 2103 tmnxEqCardChipIfCellEvent On platforms without independent IOM/IMM and CPM cards, such as the 7750 SR c4/c12 or 7450 ESS-1, the node will be rebooted if fail-on-error is enabled and one of the card level errors is encountered.

  • Page 313: Mcm Commands

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 The named pool mode may be enabled and disabled at anytime. Care should be taken when changing the pool mode for an IOM as the process of changing to or from named pool mode causes an IOM reset if MDAs are currently provisioned on the slot.

  • Page 314: Mda (xma) Commands

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Parameters mcm-slot — The MCM slot number to be configured. Even slot numbers 2 to 12 are invalid. MCM provisioning is not required to provision Compact Media Adapters (CMAs). Values 7750 SR-c4: 1, 3 7750 SR-c12: 1, 3, 5, 7, 9, 11 mcm-type Syntax...

  • Page 315: Mcm

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Parameters mda-slot — The MDA slot number to be configured. Slots are numbered 1 and 2. On vertically oriented slots, the top MDA slot is number 1, and the bottom MDA slot is number 2. On horizontally oriented slots, the left MDA is number 1, and the right MDA slot is number 2.

  • Page 316

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 The feature uses values configured in the config>card>mda>egress-xpl context. When this feature is enabled on a MDA, if window consecutive minutes pass in which the MDA experiences more than threshold Egress XPL Errors per minute, then the MDA will be put in the failed state.

  • Page 317

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 window Syntax window window Context config>card>mda>egress-xpl Description This command configures the Error Window value used by the fail-on-error feature. Default Parameters window — Specifies the time (in minutes) that the MDA can experience frequent Egress XPL Errors.

  • Page 318

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Some MDA hardware can support two different firmware loads. One load includes the base Ethernet functionality, including 10G WAN mode, but does not include 1588 port-based timestamping. The second load includes the base Ethernet functionality and 1588 port-based timestamping, but does not include 10G WAN mode.

  • Page 319

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 7450 ESS: isa-aa, isa2-aa, isa-video, isa2-video, m1-10gb, m1- 10gb-hs-xfp-b, m1-10gb-xp-xfp, m1-oc192, m10-1gb+1-10gb, m10- 1gb-hs-sfp-b, m10-1gb-sfp-b, m10-1gb-xp-sfp, m12-1gb+2-10gb- xp, m12-1gb-xp-sfp, m16-atmoc3-sfp, m16-atmoc3-sfp-b, m16- oc12/3-sfp, m16-oc12/3-sfp-b, m16-oc3-sfp, m2-10gb-xp-xfp, m2- oc192-xp-xfp, m2-oc48-sfp, m20-100eth-sfp, m20-1gb-xp-sfp, m20- 1gb-xp-tx, m4-10gb-xp-xfp, m4-oc48-sfp, m4-oc48-sfp-b, m48-1gb-...

  • Page 320

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 ingress Syntax ingress Context config>card>mda>named-pool-mode config>port>named-pool-mode Description The ingress node within the named-pool-mode context is used to contain the ingress named- pool-policy configuration. Enter the ingress node when defining or removing the MDA or port level ingress named pool policy.

  • Page 321: Mda/port Qos Commands

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 power-priority-level Syntax power-priority-level priority Context config>card>mda Description This command sets the power priority value for the 7950 XRS. Default Parameters priority — An operator must assign a priority value to each XMA using a range of number from 1 to 200.

  • Page 322

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Context config>port>access config>card>mda>access config>card>mda>network config>port>network Description This command enables the context to configure egress buffer pool parameters which define the percentage of the pool buffers that are used for CBS calculations and specify the slope policy that is configured in the config>qos>slope-policy context.

  • Page 323

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 config>port>access>ingress>pool config>port>network>egress>pool Description This command configures the threshold for the amber alarm on the over-subscription allowed. Users can selectively enable amber or red alarm thresholds. But if both are enabled (non- zero) then the red alarm threshold must be greater than the amber alarm threshold. The no form of the command reverts to the default value.

  • Page 324

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Context config>port>access>egress>pool config>port>ethernet>network config>card>mda>access>egress config>card>mda>access>ingress config>card>mda>network>egress config>card>mda>network>ingress config>port>access>egress>channel>pool config>port>access>ingress>pool config>port>network>egress>pool Description This command defines the percentage or specifies the sum of the pool buffers that are used as a guideline for CBS calculations for access and network ingress and egress queues. Two actions are accomplished by this command: •...

  • Page 325

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 max [percentage] — Specifies the maximum percentage for the reserved CBS size of the pool. When using the default value, the adaptive CBS sizing is disabled. To enable adaptive CBS sizing, max value must be set to non-default value along with the step percent.

  • Page 326

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 ingress-xpl Syntax ingress-xpl Context config>card>mda Description This command enables the context to configure ingress MDA XPL interface error parameters. threshold Syntax threshold threshold Context config>card>mda>ingress-xpl Description This command configures the Ingress XPL Error Threshold value used by the fail-on-error feature.

  • Page 327: Power Commands

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 network Syntax network Context config>card>mda config>port Description This command enables the network context to configure egress and ingress pool policy parameters. On the MDA level, network egress pools are only allocated on channelized MDAs/CMAs. 2.19.2.6 Power Commands The following power commands are supported the 7950 XRS only.

  • Page 328

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Parameters peq-slot — Identifies the APEQ slot. Values 1 to 12 chassis-id — Specifies chassis ID for the router chassis. Values 1, 2 peq-type Syntax peq-type peq-type no peq-type Context config>system>pwr-mgmt>peq Description This command sets the type of APEQ for the designated APEQ slot. The no form of this command moves the APEQ to an unprovisioned state.

  • Page 329: Virtual Scheduler Commands

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 power-safety-alert Syntax power-safety-alert wattage Context config>system>pwr-mgmt Description This command sets a value in watts for the Power Safety Alert. The Power Safety Alert minor alarm is generated when the system power capacity drops below the Power Safety Level (in watts) + the Power Safety Alert.

  • Page 330

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Default default Parameters weight-mode — Specifies the internal scheduler weight mode. Values default, force-equal, offered-load, capped-offered-load rate-calc-min-int Syntax rate-calc-min-int [fast-queue percent-of-default] [slow-queue percent-of-default] no rate-calc-min-int Context config>card>virt-sched-adj Description This command overrides the default minimum time that must elapse before a policer or queue’s offered rate may be recalculated.

  • Page 331

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Default no rate-calc-min-int Parameters fast-queue percent-of-default — The fast-queue percent-of-default parameter is optional and is used to modify the default minimum rate calculation time for “fast” queues. Defining 100.00 percent is equivalent to removing the override (restoring the default) on the fast queue minimum rate calculation time.

  • Page 332

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 slow-queue-thresh Syntax slow-queue-thresh kilobits-per-second no slow-queue-thresh Context config>card>virt-sched-adj Description This command is used to override the system default rate threshold where policers and queues are placed in the “slow” queue category. Slow rate policers and queues use a different minimum rate calculation interval time than fast rate queues.

  • Page 333: Forwarding Plane Configuration Commands

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Parameters percent-of-default: — The percent-of-default parameter is required and is used to modify the default task scheduling interval for the hierarchical virtual scheduling task on the card. Defining 100.00 percent is equivalent to removing the override. Values 0.01% to 1000.00% Default...

  • Page 334

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Description This command specifies the egress QoS high threshold delta for this port. Parameters size-in-bytes — Specifies high threshold data in bytes. Values 0 to 65536 hs-pool-policy Syntax hs-pool-policy name no hs-pool-policy Context config>card>fp Description This command specifies the egress QoS HS scheduler policy for this port.

  • Page 335

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 The mega-pools provide buffers to the second tier buffer pools. The default mega-pool services all default pools and explicitly created named pools. As the name implies, the WRED mega-pool services all the WRED buffer pools created for the WRED queues. The WRED mega-pool allows each WRED queue pool to be configured to an appropriate size while allowing the sum of the WRED queue pool sizes to oversubscribe the total amount set aside for WRED queue buffering without affecting the queues using the default or named pools.

  • Page 336

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Description This command defines the amount of buffers within the WRED mega-pool that will be set aside for WRED queues operating within their configured CBS thresholds. Note that the min percentage and max percentage parameters must be set to the same value. The forwarding plane protects against WRED queue buffer starvation by setting aside a portion of the buffers within the WRED mega-pool.

  • Page 337

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Description This command configures WRED slopes within the WRED mega-pool. The WRED slopes in the WRED mega-pool are used when WRED queues are requesting buffers from the mega- pool while they are over their CBS threshold. Once over the CBS threshold, the WRED queue stops receiving buffers from the CBS reserve in the mega-pool and starts competing for buffers in the shared portion of the mega-pool.

  • Page 338

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 The no form of the command enables WRED queuing on an egress forwarding plane. Default shutdown hi-bw-mcast-src Syntax hi-bw-mcast-src [alarm] [group group-id] [default-paths-only] no hi-bw-mcast-src Context config>card>fp Description This command designates the forwarding plane as a high-bandwidth IP multicast source, expecting the ingress traffic to include high-bandwidth IP multicast traffic.

  • Page 339

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 access Syntax access Context config>card>fp>ingress Description This CLI node contains the access forwarding-plane parameters. queue-group Syntax queue-group queue-group-name instance instance-id [create] no queue-group Context config>card>fp>ingress>access Description This command creates an instance of a named queue group template on the ingress forwarding plane of a given IOM/IMM.

  • Page 340

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 An accounting policy must be configured before it can be associated to an interface. If the accounting policy-id does not exist, an error is returned. Accounting policies associated with service billing can only be applied to SAPs. The accounting policy can be associated with an interface at a time.

  • Page 341

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Parameters policer-control-policy-name — Specifies the name of the policer-control policy to use for the queue-group. The name can be up to 32 characters long. policer-control-override Syntax no policer-control-override policer-control-override [create] Context config>card>fp>ingress>access>queue-group Description This command configures policer control overrides. Parameters create —...

  • Page 342

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 The no max-rate command returns the policer-control-policy’s parent policer maximum rate to max. Default Parameters rate — Defining a kilobits-per-second value is mutually exclusive with the max parameter. The kilobits-per-second value must be defined as an integer that represents the number of kilobytes that the parent policer will be decremented per second.

  • Page 343

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Description The mbs-contribution command is used to configure the policy-based burst tolerance for a parent policer instance created when the policy is applied to a SAP or subscriber context. The system uses the parent policer’s min-thresh-separation value, the priority level’s mbs- contribution value and the number of child policers currently attached to the priority level to derive the priority level’s shared-portion and fair-portion of burst tolerance within the local priority level.

  • Page 344

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 This level of fair aggregate burst tolerance is based on the decrement rate of the parent policer’s PIR bucket while the individual fair bursts making up the aggregate are based on each child’s FIR decrement rate. The aggregate fair rate of the priority level is managed by the system with consideration of the current rate of traffic in higher priority levels.

  • Page 345

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 In most cases, lower priority traffic in the policer will be responsible for the greater part of congestion above the parent policer rate. Since this traffic is discarded with a lower threshold, this lowers the effective burst tolerance even while the highest priority traffic is present. Configuring a Priority Level's MBS Contribution Value In the most conservative case, a priority level’s mbs-contribution value may be set to be greater than the sum of child policer’s mbs and one max-size-frame per child policer.

  • Page 346

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 bytes, kilobytes — The bytes keyword is optional and is mutually exclusive with the kilobytes keyword. When specified, size is interpreted as specifying the size of min- thresh-separation in bytes. The kilobytes keyword is optional and is mutually exclusive with the bytes keyword. When specified, size is interpreted as specifying the size of min-thresh-separation in kilobytes.

  • Page 347

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 • When a parent policer instance’s priority level has one child policer associated, the fair- portion will be equal to the maximum of the min-thresh-separation value and the priority level’s mbs-contribution value. • When a parent policer instance's priority level has two or more child policers associated, the fair-portion will be equal to the maximum of the following: −...

  • Page 348

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 One thing to note is that a priority level’s shared-portion of the parent policer’s PIR bucket depth is only necessary to provide some separation between a lower priority’s discard-all threshold and this priority’s discard-unfair threshold. It is expected that the burst tolerance for the unfair packets is relatively minimal since the child policers feeding the parent policer priority level all have some amount of fair burst before entering into an FIR exceed or unfair state.

  • Page 349

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Parameters level — Specifies the priority level. Values 1 to 8 policer-override Syntax [no] policer-override Context config>card>fp>ingress>access>queue-group config>card>fp>ingress>network>queue-group Description This command, within the SAP ingress or egress contexts, is used to create a CLI node for specific overrides to one or more policers created on the SAP through the sap-ingress or sap- egress QoS policies.

  • Page 350

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 The system will allow a policer to be created on a SAP QoS policy regardless of the ability to support policers on objects where the policy is currently applied. The system only scans the current objects for policer support and sufficient resources to create the policer when a forwarding class is first mapped to the policer ID.

  • Page 351

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 bytes — When byte is defined, the value given for size is interpreted as the queue’s MBS value given in bytes. kilobytes — When kilobytes is defined, the value is interpreted as the queue’s MBS value given in kilobytes.

  • Page 352

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 default — Specifying the keyword default sets the MBS to its default value. packet-byte-offset Syntax packet-byte-offset {add add-bytes | subtract sub-bytes} no packet-byte-offset Context config>card>fp>ingress>access>qgrp>policer-over>plcr config>card>fp>ingress>network>qgrp>policer-over>plcr Description This command is used to modify the size of each packet handled by the policer by adding or subtracting a number of bytes.

  • Page 353

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 no rate Context config>card>fp>ingress>access>qgrp>policer-over>plcr config>card>fp>ingress>network>qgrp>policer-over>plcr Description This command is used to configure the policer’s metering and optional profiling rates. The metering rate is used by the system to configure the policer’s PIR leaky bucket’s decrement rate while the profiling rate configures the policer’s CIR leaky bucket’s decrement rate.

  • Page 354

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 cir {max | rate} — The optional cir keyword is used to override the default CIR rate of the policer. Specifying the keyword max or an explicit rate parameter directly following the cir keyword is required and identifies the policer’s profiling rate for the CIR leaky bucket.

  • Page 355

    The command will fail if insufficient policer counter resources exist to implement minimal where the QoS policer is currently applied and has a forwarding class mapping. Parameters — See the 7450 ESS, 7750 SR, 7950 XRS, and VSR Quality of Service Guide for details on the policer stat-mode parameters. ingress-buffer-allocation...

  • Page 356

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 bandwidth-policy Syntax bandwidth-policy policy-name no bandwidth-policy Context config>card>fp>ingress>mcast-path-management Description This command is used to explicitly associate a bandwidth policy to a forwarding plane or MDA. The bandwidth policy defines the dynamic rate table and the multicast paths bandwidth and queuing parameters.

  • Page 357

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Stable pool sizing preserves the ability to modify the effective bandwidth used to determine a port’s relative share of the available buffers through the use of the ing-percentage-of-rate and egr-percentage-of-rate commands under the port configuration. Changing the values associated with these commands will cause a reevaluation of buffer distribution and thus a possible resizing of pools on each port within the module.

  • Page 358: Macsec Commands

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 create — Keyword used to create the queue-group instance. 2.19.2.9 MACsec Commands macsec Syntax macsec Context config Description This command enables the context for MACsec configuration. The MACsec MKA profile can be configured under this command. connectivity-association Syntax connectivity-association ca-name [create]...

  • Page 359

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Parameters type — Specifies the algorithm. Values gcm-aes-128 — algorithm is used for control plain encryption gcm-aes-256 — algorithm is used for control plain encryption gcm-aes-xpn-128 — algorithm with extended packet number is used for control plain encryption gcm-aes-xpn-256 —...

  • Page 360

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Parameters clear-tag-mode — Specifies the clear tag mode. Values single-tag or dual-tag description Syntax description description no description Context config>macsec>connectivity-association Description This command enters a description for connectivity association. The no form of this command removes the connectivity association description. Parameters description —...

  • Page 361

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Table 41 MACsec Basic Settings (Continued) Setting Description The following are supported: • Integrity without confidentiality • Integrity and confidentiality with a confidentiality offset of 0, 30, or 5 Note: 1. SR OS supports (3) Integrity without confidentiality and Integrity and confidentiality with a confidentiality offset of 0, 30, or 50.

  • Page 362

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 When replay protection is enabled, the sequence of the ID number of the received packets are checked. If the packet arrives out of sequence and the difference between the packet numbers exceeds the replay window size, the packet is counted by the receiving port and then discarded.

  • Page 363

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Parameters number-of-packets — Specifies the window that the packets can arrive out of order. Values 0 to 4294967294 Default shutdown Syntax [no] shutdown Context config>macsec>connectivity-association Description This command shuts down the CA profile. All ports using this profile will not transmit PDUs as this command shuts down the MACsec for this profile.

  • Page 364

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 no mka-key-server-priority Context config>macsec>connectivity-association>static-cak Description This command specifies the key server priority used by the MACsec Key Agreement (MKA) protocol to select the key server when MACsec is enabled using static connectivity association key (CAK) security mode. The no form of this command disables the mka-key-server-priority.

  • Page 365

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Syntax cak {value} [hash | hash2] no cak {value} Context config>macsec>connectivity-association>static-cak>pre-shared-key Description Specifies the connectivity association key (CAK) for a pre-shared key. Two values are derived from CAK. • KEK (Key Encryption Key), this is used to encrypt the MKA and SAK (symmetric key used for datapath PDUs) to be distributed between all members.

  • Page 366: General Port Commands

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 2.19.2.10 General Port Commands port Syntax [no] port {port-id | bundle-id | bpgrp-id | aps-id} Context config Description This command enables access to the context to configure ports, multilink bundles, and bundle protection groups (BPGs). Before a port can be configured, the chassis slot must be provisioned with a valid card type and the MDA parameter must be provisioned with a valid MDA type.

  • Page 367

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 For example: router1>config# port bundle-ppp-5/1.1 (multilink PPP bundle) router1>config# port bundle-ima-5/1.2 (IMA bundle) aps-id — This option configures APS on unbundled SONET/SDH ports. All SONET-SDH port parameters, with certain exceptions, for the working and protection circuit ports must be configured in the config>port>aps-group-id context.

  • Page 368

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 The same rules apply for physical ports, bundles deletions apply to APS ports/ bundles deletions (for example an aps-group-id must be shutdown, have no service configuration on it, and no path configuration on it). In addition working and protection circuits must be removed before an aps-group-id may be removed.

  • Page 369

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Context config>port>dwdm Description This command enables you to tune the optical amplifier parameters. report-alarms Syntax [no] report-alarms [ild] [tmp] [mth] [mtl] [los] [lop] [com] Context config>port>dwdm>amplifier Description This command allows users to enable/disable the optical amplifier alarms for the port. Default All alarms are enabled Parameters...

  • Page 370

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 • The 'dwdm channel' must set to a non-zero value before the port is set to 'no shutdown' • The port must be 'shutdown' before changing the dwdm channel. • The port must be a physical port to set the dwdm channel Parameters channel —...

  • Page 371

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Table 42 DWDM Channel Numbers (Continued) C-Band 100 GHz Grid 50GHz Grid Channel Channel 1541.35 194.50 1541.75 194.45 1542.14 194.40 1542.54 194.35 1542.94 194.30 1543.33 194.25 1543.73 194.20 1544.13 194.15 1544.53 194.10 1544.92 194.05 1545.32 194.00 1545.72...

  • Page 372

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Table 42 DWDM Channel Numbers (Continued) C-Band 100 GHz Grid 50GHz Grid Channel Channel 1561.42 192.00 1561.83 191.95 1562.23 191.90 1562.64 191.85 1563.05 191.80 1563.45 191.75 1563.86 191.70 — — — compatibility Syntax compatibility mode Context config>port>dwdm>coherent Description...

  • Page 373

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 wavetracker Syntax wavetracker Context config>port>dwdm Description This command validates whether or not the port supports Wavetracker. Default power-control Syntax [no] power-control Context config>port>dwdm>wavetracker>power-control Description This command specifies whether the power control loop should be turned on to actively control the laser’s launch power to the specified target power.

  • Page 374

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Parameters power — Specifies the desired average output power in dBm. Values -20.00 to 3.00 report-alarm Syntax [no] report-alarm [encode-fail] [encode-degrade] [power-fail] [power-degrade] [power- high] [power-low] [missing] Context config>port>dwdm>wavetracker Description This command specifies the alarms which are enabled or outstanding against a Wave Tracker-enabled interface.

  • Page 375

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Table 43 Value Ranges for DWDM ITU Channel DWDM ITU Key 1 Key 1 Key 2 Key 2 Channel Number Minimum Maximum Minimum Maximum 1276 1290 1760 1774 1259 1273 1743 1757 1242 1256 1726 1740 1225...

  • Page 376

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Table 43 Value Ranges for DWDM ITU Channel (Continued) DWDM ITU Key 1 Key 1 Key 2 Key 2 Channel Number Minimum Maximum Minimum Maximum 1276 1290 1760 1774 1259 1273 1743 1757 1140 1154 1624 1638...

  • Page 377

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Table 43 Value Ranges for DWDM ITU Channel (Continued) DWDM ITU Key 1 Key 1 Key 2 Key 2 Channel Number Minimum Maximum Minimum Maximum 1276 1290 1760 1774 1259 1273 1743 1757 3806 3820 2270 2284...

  • Page 378

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Table 43 Value Ranges for DWDM ITU Channel (Continued) DWDM ITU Key 1 Key 1 Key 2 Key 2 Channel Number Minimum Maximum Minimum Maximum 1276 1290 1760 1774 1259 1273 1743 1757 1446 1460 1930 1944...

  • Page 379

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Context config>port>dwdm>coherent Description This command configures the residual chromatic dispersion to be compensated when the coherent receiver is operating in manual dispersion control mode. Default Parameters dispersion — Specifies the dispersion compensation. Values -5000 to 5000 mode Syntax mode {automatic | manual}...

  • Page 380

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Description This command allows users to Enable/disable logging of tdcm alarms on the port. Default All alarms are enabled Parameters nrdy — Reports Tdcm not ready faults. mth — Reports module case temperature high faults. mtl —...

  • Page 381

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 rx-los-thresh Syntax rx-los-thresh threshold Context config>port>dwdm>coherent Description This command configures the average input power LOS (Loss of Signal) threshold. Default Parameters threshold — Specifies the port’s rx los threshold. Values -23.00 to -13.00 sweep Syntax sweep start dispersion-start end dispersion-end Context...

  • Page 382

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Parameters dispersion-start — Specifies the lower range limit for the dispersion compensation. Values -50000 to 50000 Default -25500 dispersion-end — Specifies the upper range limit for the dispersion compensation. Values -50000 to 50000 Default 2000 rxdtv-adjust Syntax...

  • Page 383

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 The no version of this command deletes the queue-group instance from the network egress context of the port. Parameters queue-group-name — Specifies the name of the queue group template up to 32 characters in length. instance-id —...

  • Page 384

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Context config>port>otu>fec Description This command enables the Forwarding Error Correction (FEC) encoder/decoder and specifies the FEC encoder/decoder mode to use when enabled. The following rules must be followed: • The port’s OTU must be enabled to set or change the FEC mode. •...

  • Page 385

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Description This command specifies the method used to determine the signal fail and signal degrade alarms. When select the bip8 method is selected, the SM-BIP8 errors are used. When the FEC method is selected, the FEC corrected bits are used. The following rules must be followed: •...

  • Page 386

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Description This command the signal fail (SF) threshold clear. Parameters threshold — Specifies the exponent of the error rate, thus an error rate from 10E-3 to 10E-7. Values 5 to 9 Default coefficient — Specifies the coefficient of the SF threshold. Values 10 to 99 Default...

  • Page 387

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Parameters threshold — Specifies the exponent of the error rate, thus an error rate from 10E-3 to 10E-7. Values 3 to 10 Default coefficient — Specifies the coefficient of the SD threshold. Values 10 to 99 Default sm-tti Syntax...

  • Page 388

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 mismatch-reaction Syntax mismatch-reaction {none | squelch-rx} Context config>port>otu>sm-tti Description This command allows the user to configure the consequent action to a sm-tti mismatch. Default Parameters none — Specifies that the received traffic is passed through. squelch-rx —...

  • Page 389

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Parameters auto-generated — Specifies to use the system generated (default) TTI. identifier — Sets the PM TTI to the string provided by the user. If the string is less than 64 bytes, the remaining bytes will be set to 0. byte-string —...

  • Page 390

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Parameters auto-generated — Sets the default. identifier — Sets the PM TTI to the string provided by the user. If the string is less than 64 bytes, the remaining bytes will be set to 0. Up to 64 byte strings can be specified in a single statement.

  • Page 391

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 • iomnum — The second section contains the IOM slot number. • mdanum — The third section contains the MDA slot number. • portnum — The fourth section contains the port number. • dwdmchan — The fifth section contains the DWDM channel number (see DWDM Channel Numbers).

  • Page 392

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 mismatch-reaction Syntax mismatch-reaction {none | squelch-rx} Context config>port>otu>psi-tti Description This command allows the user to configure the consequent action to a psi-tti mismatch. Default Parameters none — Specifies the received traffic is passed through. squelch-rx —...

  • Page 393

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Context config>port>otu>psi-payload Description This command allows the user to configure the consequent action to a psi-payload type mismatch. Default Parameters none — Specifies the received traffic is passed through. squelch-rx — Specifies the received traffic is blocked. async-mapping Syntax [no] async-mapping...

  • Page 394

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Table 44 Alarm Descriptions Alarm Description Loss of lock. Loss of OTU framing. Loss of Multi-frame. Loss of signal transitions on the data. losTx otu-ais OTU Alarm Indication Signal (all 1s, overwrites all OTU overhead, even framing bytes).

  • Page 395

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Context config>port Description This command enables the context for configuring hybrid port buffer allocation parameters. egr-weight Syntax egr-weight access access-weight network network-weight no egr-weight Context config>port>hybrid-buffer-allocation Description This command configures the sharing of the egress buffers allocated to a hybrid port among the access and network contexts.

  • Page 396

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 monitor-agg-egress-queue-stats Syntax [no] monitor-agg-egress-queue-stats Context config>port Description This command enables the monitoring of aggregate egress queue statistics on the port. All queues on the port are monitored, including SAP egress, network egress, subscriber egress, and egress queue group queues, as well as system queues that can be used, for example, to send port-related protocol packets (LACP, EFM, and so on).

  • Page 397

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 A value of 100 (the default value) is equivalent to executing the no egr-percentage-of-rate command and restores the egress active rate to the normal value. The no egr-percentage-of-rate command is used to remove any artificial increase or decrease of the egress active bandwidth used for egress buffer space allocation to the port.

  • Page 398

    • The maximum rate for each priority level 8 through 1. • The CIR associated with each priority level 8 through 1. See the 7450 ESS, 7750 SR, 7950 XRS, and VSR Quality of Service Guide for command syntax and usage for the port-scheduler-policy command.

  • Page 399

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 The no form of this command removes the local port priority level rate overrides. Once removed, the port priority level will use the port scheduler policies level command for that priority level. Parameters priority-level — Identifies which of the eight port priority levels are being overridden. Values 1 to 8 pir-rate —...

  • Page 400

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 The egress-scheduler-override max-rate command supports a parameter that allows the override command to restore the default of not having a rate limit on the port scheduler. This is helpful when the port scheduler policy has an explicit maximum rate defined and it is desirable to remove this limit at the port instance.

  • Page 401

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 The no form of this command removes a port scheduler policy from an egress port or channel. Once the scheduler policy is removed, all orphaned policers, queues, and schedulers revert to a free running state governed only by the local queue or scheduler parameters.

  • Page 402

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 no t391 Context config>port>ethernet>elmi Description This command configures the polling timer for UNI-C. Parameters value — Specifies the polling timer for UNI-C. Values 5 to 30 t392 Syntax t392 [5 to 30] no t392 Context config>port>ethernet>elmi Description...

  • Page 403

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 An access port or channel is used for customer facing traffic on which services are configured. A Service Access Point (SAP) can only be configured on an access port or channel. When a port is configured for access mode, the appropriate encap-type must be specified to distinguish the services on the port or SONET path.

  • Page 404

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Special Cases SONET/SDH Path — When network mode is selected, the appropriate control protocols are activated when the need arises. For example, configuring an IP interface on the SONET path activates IPCP while the removal of the IP interface causes the IPCP to be removed.

  • Page 405

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 no mtu Context config>port>ethernet config>port>sonet-sdh>path config>port>tdm>ds1>channel-group config>port>tdm>ds3 config>port>tdm>e1>channel-group config>port>tdm>e3 Description This command configures the maximum payload MTU size for an Ethernet port, PPP-enabled port or sub-port and Frame Relay-enabled port or subport. The Ethernet port level MTU parameter indirectly defines the largest physical packet the port can transmit or the far-end Ethernet port can receive.

  • Page 406

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Table 45 Default MTU Values (Continued) Type Mode Encap Type Default (Bytes) SONET/SDH or TDM Access frame-relay 1578 ATM, SONET/SDH or TDM Access 1524 10/100 or 100FX Ethernet Network null 1514 10/100 or 100FX Ethernet Network dot1q 1518...

  • Page 407

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 queue-policy Syntax queue-policy name no queue-policy Context config>card>mda>network>ingress config>port>sonet-sdh>path>network Description This command specifies the network-queue policy which defines queue parameters such as CBS, high priority only burst size, MBS, CIR and PIR rates, as well as forwarding-class to queue mappings.

  • Page 408

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 The no form of the command disables the header compression. Default no compress Parameters acfc — Specifies address and control field compression. pfc — Specifies protocol field compression. ber-sf-link-down Syntax [no] ber-sf-link-down Context config>port>tdm>ds1>channel-group>ppp config>port>tdm>e1>channel-group>ppp Description This command enables the port down on BER-SF alarm.

  • Page 409

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 rai — Reports resource availability indicator events. When configured, rai events are not raised and cleared. Default rai alarms are not issued looped — Reports looped packets errors. Default looped alarms are not issued scramble Syntax [no] scramble...

  • Page 410: Port Xc Commands

    — Specifies the number of consecutive keepalive failed request attempts or remote replies that can be missed after which the port is operationally downed. Values 1 to 255 2.19.2.11 Port XC Commands The port xc commands are supported on the 7450 ESS only. port-xc Syntax port-xc Context config Description This command enables the context to configure port-cross connect functionality.

  • Page 411

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Context config>port-xc>pxc Description This command configures the referenced Ethernet port as a loopback or a cross-connect port (PXC). Once this command is executed, the system automatically creates two PXC sub-ports under this Ethernet port. The two PXC sub-ports are logical configurations used by the node to transmit traffic bi-directionally through a single physical port that is internally cross- connected.

  • Page 412: Forwarding Path Extension (fpe) Commands

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 sub-port-id — When this the pxc-id is configured, two logical sub-ports are automatically created. These logical sub-ports are used to create two paths within the loop; one upstream path, and one downstream path. These sub-ports are destroyed when either this PXC row is destroyed, this object is de-provisioned.

  • Page 413

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Description This command is used to reference a PXC (pair of PXC sub-ports) and consequently create an association between the PXC and the application which is referenced under the same FPE object. Each application will utilize the PXC in the form of an internal cross-connect. The exact use and internal provisioning of this cross-connect depends on the application itself.

  • Page 414

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 sub-mgmt-extensions Syntax [no] sub-mgmt-extensions Context config>fwd-path-ext>fpe Description This command configures FPE for subscriber management extensions. The FPE cannot be used for other applications but can be used for multiple subscriber management applications. The no version of this command disables FPE for subscriber management extensions. Default no sub-mgmt-extensions vxlan-termination...

  • Page 415: Aps Commands

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 sdp-id-range Syntax sdp-id-range from id to id no sdp-id-range Context config>fwd-path-ext Description This command is used to reserve SDP id range used by the FPE based PW-Port and VXLAN termination applications. Each configured FPE based PW-Port is associated with two internal SDPs (one in each direction) whose id(s) are allocated from the configured sdp-id-range.

  • Page 416

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 advertise-interval Syntax advertise-interval advertise-interval no advertise-interval Context config>port>aps Description This command specifies the time interval, in 100s of milliseconds, between 'I am operational' messages sent by both protect and working circuits to their neighbor for multi-chassis APS. The advertise-interval value is valid only for a multi-chassis APS as indicated by the value of the neighbor command value if it is not set to 0.0.0.0.

  • Page 417

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Description This command configures hold-down timers to debounce signal failure conditions (lais, b2err- sf) and signal degrade conditions (b2err-sd) for Uni 1+1 Sig+Data APS switching mode (switching mode uni-1plus1). The no version of this command resets the hold-down timer to the default value. Default 0 (disabled) Parameters...

  • Page 418

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Parameters ip-address — Specifies the neighbor's IP address only on a multi-chassis APS where the working and protect circuits are configured on different routers. The node should be connected with a direct interface to ensure optimum fail-over time. Values ipv4-address: a.b.c.d...

  • Page 419

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Parameters port-id — Specifies the physical port that will act as the protection circuit for this APS group in the following format. port-id slot/mda/port eth-sat-id esat-id/slot/port esat keyword 1 to 20 pxc-id pxc-id.sub-port keyword 1 to 64 sub-port a, b...

  • Page 420

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 A change in the minutes value takes effect upon the next initiation of the wait to restore (WTR) timer. It does not modify the length of a WTR timer that has already been started. The WTR timer of a non-revertive switch can be assumed to be infinite.

  • Page 421

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 When a port is being configured as a working circuit of an APS group, all common configuration as described above and all service configurations related to the APS port is operationally inherited by the working circuit from the aps-group-id. If the working circuit cannot inherit that configuration, for example, due to resource limitations, the configuration attempt fails and an error is returned to the user.

  • Page 422

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Rx S1 Byte : 0x00 (stu) Rx K1/K2 Byte : 0x00/0x00 Tx S1 Byte : 0x0f (dnu) Tx DUS/DNU : disabled Rx J0 String (Hex) : 81 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Cfg Alarm : loc lais lrdi ss1f lb2er-sd lb2er-sf slof slos lrei Alarm Status...

  • Page 423: Ethernet Port Commands

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Packets 3870094 6656408 Discards Unknown Proto Discards =============================================================================== A:NS044050253# wtr-annexb Syntax wtr-annexb minutes Context config>port>aps Description This command waits to restore for Annex B mode operation. The delay after which the newly active section becomes the primary section after a switch-over from the primary section to the secondary section occurs and the switch request clears normally.

  • Page 424

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Description This command configures an Ethernet port for access, network, or hybrid mode of operation. It also configures a TDM channel or SONET/SDH path (sub-port) for access or network mode operation. An access port or channel is used for customer facing traffic on which services are configured.

  • Page 425

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Default network — For Ethernet ports. access — For TDM channel or SONET paths. Parameters access — Configures the Ethernet port, TDM channel or SONET path as service access. network — Configures the Ethernet port, TDM channel or SONET path for transport network use.

  • Page 426

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Within the access node, queue groups are also configured as ingress or egress. Access ingress queue groups can only be used by ingress SAP forwarding classes and only a single ingress queue group per port is supported. Multiple access egress queue groups may be created on a single port and are used by egress SAP forwarding classes.

  • Page 427

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 A port queue group cannot be removed from the port when a forwarding class is currently redirected to the group. All forwarding class redirections must first be removed prior to removing the queue group. Parameters group-name —...

  • Page 428

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Queue groups may be created on both access and network oriented ports. When the port is in access mode, the queue groups must be created within the port access node. Within the access node, queue groups are also configured as ingress or egress. Access ingress queue groups can only be used by ingress SAP forwarding classes and only a single ingress queue group per port is supported.

  • Page 429

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 A port queue group cannot be removed from the port when a forwarding class is currently redirected to the group. All forwarding class redirections must first be removed prior to removing the queue group. Parameters queue-group-name —...

  • Page 430

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 limit-unused-bandwidth Syntax [no] limit-unused-bandwidth Context config>port>ethernet>access>egr>qgrp>agg-rate config>port>ethernet>access>egr>vport>agg-rate config>port>ethernet>network>egr>qgrp>agg-rate config>port>sonet-sdh>path>access>egress>vport Description This command is used to enable (or disable) aggregate rate overrun protection on the agg- rate context. queue-frame-based-accounting Syntax [no] queue-frame-based-accounting Context config>port>ethernet>access>egr>qgrp>agg-rate config>port>ethernet>access>egr>vport>agg-rate config>port>ethernet>network>egr>qgrp>agg-rate config>port>sonet-sdh>path>access>egress>vport Description...

  • Page 431

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 hs-turbo Syntax [no] hs-turbo-queues Context config>port>ethernet>access>egress>queue-group config>port>ethernet>network>egress>queue-group Description This command enables/disables HS turbo queues. policer-control-policy Syntax policer-control-policy policy-name no policer-control-policy Context config>port>ethernet>network>egress>queue-group>policer-control-policy Description This command configures the policer control policy for the QoS egress queue-group. Parameters policy-name —...

  • Page 432

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Description This command associates a queue for use in a queue group template. The defined queue-id acts as a repository for the default parameters for the queue. The template queue is created on each queue-group object which is created with the queue group template name. Each queue is identified within the template by a queue-id number.

  • Page 433

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 adaptation-rule Syntax adaptation-rule [pir adaptation-rule] [cir {max | min | closest}] no adaptation-rule Context config>port>ethernet>access>egr>qgrp>qover>q config>port>ethernet>access>ing>qgrp>qover>q config>port>ethernet>network>egr>qover>q Description This command specifies the method used by the system to derive the operational CIR and PIR settings when the queue is provisioned in hardware. For the CIR and PIR parameters individually, the system attempts to find the best operational rate depending on the defined constraint.

  • Page 434

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 no burst-limit Context config>port>ethernet>access>egr>qgrp>qover>q Description The queue burst-limit command overrides the shaping burst size for a queue. The configured size defines the shaping leaky bucket threshold level that indicates the maximum burst over the queue’s shaping rate. The no form of this command removes the current burst limit override for the queue.

  • Page 435

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Parameters size-in-kbytes — The size parameter is an integer expression of the number of kilobytes reserved for the queue. If a value of 10KBytes is desired, enter the value 10. A value of 0 specifies that no reserved buffers are required by the queue (a minimal reserved size can still be applied for scheduling purposes).

  • Page 436

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Syntax mbs {size [bytes | kilobytes] | default} no mbs Context config>port>ethernet>access>egr>qgrp>qover>q config>port>ethernet>access>ing>qgrp>qover>q config>port>ethernet>network>egr>qgrp>qover>q Description The Maximum Burst Size (MBS) command specifies the default maximum buffer size for the template queue. The value is given in kilobytes. The MBS value is used by a queue to determine whether it has exhausted all of its buffers while enqueuing packets.

  • Page 437

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 monitor-depth Syntax [no] monitor-depth Context config>port>eth>access>ing>qgrp>qover>q config>port>eth>access>egr>qgrp>qover>q config>port>ethernet>network>egr>qgrp>qover>q Description This command enables queue depth monitoring for the specified queue. This command and the dynamic-mbs command are mutually exclusive on the related queue group queue. The no form of the command removes queue depth monitoring for the specified queue.

  • Page 438

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 The CIR defines the rate at which the system prioritizes the queue over other queues competing for the same bandwidth. In-profile then out-of-profile packets are preferentially queued by the system at egress and at subsequent next hop nodes where the packet can traverse.

  • Page 439

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 The no form of the command removes all of the scheduler overrides and returns the scheduler’s parent weight and CIR weight, and its PIR and CIR to the values configured in the applied scheduler policy. scheduler Syntax scheduler scheduler-name [create]...

  • Page 440

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 The override weights are ignored if the scheduler does not have a parent command configured in the scheduler policy - this allows the parent of the scheduler to be removed from the scheduler policy without having to remove all of the queue group overrides. If the parent scheduler does not exist, causing the configured scheduler to be fostered on an egress port scheduler, the override weights will be ignored and the default values used;...

  • Page 441

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Description This command can be used to override specific attributes of the specified scheduler rate. The rate command defines the maximum bandwidth that the scheduler can offer its child queues or schedulers. The maximum rate is limited to the amount of bandwidth the scheduler can receive from its parent scheduler.

  • Page 442

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 agg-burst Syntax agg-burst Context config>port>ethernet>egress>exp-secondary-shaper Description This command specifies the aggregate burst limits. high-burst-increase Syntax high-burst-increase size [bytes | kilobytes] no high-burst-increase Context config>port>ethernet>egress>exp-secondary-shaper>agg-burst Description This command specifies a high burst increase. Parameters size — Specifies the shaping burst size. Values 0 to 65528 bytes —...

  • Page 443

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Context config>port>ethernet>egress>exp-secondary-shaper Description This command assigns the low burst maximum class to associate with the Ethernet egress expanded secondary shaper. The no form of the command returns the class id for the Ethernet egress expanded secondary shaper to the default value.

  • Page 444

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Description This command is used to configure the shaper’s metering and optional profiling rates. The metering rate is used by the system to configure the shaper’s PIR leaky bucket’s decrement rate. The decrement function empties the bucket while packets applied to the bucket attempt to fill it based on the each packets size.

  • Page 445

    (single copy of each channel) and subscriber’s unicast traffic. The bandwidth control point for this PON port resides in the upstream Nokia BNG node in the form of a Vport. In the case where the multicast delivery method of the BNG utilizes redirection, the multicast traffic in the BNG will flow outside of the subscriber or the Vport context and thus will bypass any bandwidth enforcement in the Nokia router.

  • Page 446

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 • In case the agg-rate within the Vport is configured, its value will be modified based on the IGMP activity associated with the subscriber under this Vport. • In case the port-scheduler-policy within the Vport is referenced, the max-rate defined in the corresponding port-scheduler-policy will be modified based on the IGMP activity associated with the subscriber under this Vport.

  • Page 447

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Parameters description-string — The destination character string. Allowed values are any string up to 32 characters long composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed within double quotes.

  • Page 448

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 If a given subscriber host queue does not have the port-parent option enabled, it will be foster- parented to the Vport used by this subscriber and which is based on matching the dest string and org string.

  • Page 449

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Router requires that autonegotiation be disabled or limited for ports in a Link Aggregation Group to guarantee a specific port speed. The no form of this command disables autonegotiation on this port. Default autonegotiate Parameters limited —...

  • Page 450

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 max-time — Specifies the maximum suppression time, in seconds, which is the time it can take after the physical link comes up before the worst case accumulated penalties have decayed to the reuse threshold. The maximum penalty is derived from the maximum suppression time, half-life, and reuse threshold, using the following equation: maximum penalty = (reuse threshold) ×...

  • Page 451

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Parameters value — Specifies the Ethertype to expect in the form 0x0600 to 0xffff. Values 1536 to 65535, accepts in decimal or hex Default If the encap-type is dot1p, then the default is 0x8100. If the encap-type is qinq, then the default is 0x8100.

  • Page 452

    00:16:4d (ALU) or the configured grace-vendor-oui value. The grace-tx-enable command should not be configured if the Nokia Vendor Specific Grace TLV is not supported on the remote peer, including Nokia 7750 SR equipment prior to release 11.0 R4. Default config>system>ethernet>efm-oam>no dying-gasp-tx-on-reset config>port>ethernet>efm-oam>dying-gasp-tx-on-reset...

  • Page 453

    Nokia Vendor Specific Grace TLV is not supported on the remote peer, including Nokia 7750 SR equipment prior to release 11.0 R4. The no form of the command disables the sending of the Nokia Vendor Specific Grace TLV. Default config>system>ethernet>efm-oam>no grace-tx-enable...

  • Page 454

    This optional command configures an additional peer vendor OUI which indicates support for the Vendor Specific EFM-OAM Grace functionality, allowing grace to be preferred over dying gasp when both are configured. This is in addition to the Nokia Vendor OUI 00:16:4d. When both...

  • Page 455

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 ignore-efm-state Syntax [no] ignore-efm-state Context config>port>ethernet>efm-oam> Description When the ignore-efm-state command is configured, any failure in the protocol state machine (discovery, configuration, timeout, loops, and so on) does not impact the state of the port. There is only be a protocol warning message on the port.

  • Page 456

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 config>port>ethernet>efm-oam>link-mon>errored-frame-period config>port>ethernet>efm-oam>link-mon>errored-frame-seconds Description Allows the frame error sf-threshold crossing events to transmit the Event Notification OAMPDU with the specific Link Event TLV information. The Event Notification OAM PDU will only be generated when the initial sf-threshold is reached. No subsequent notification will be sent until the event that triggered until the event is manually cleared.

  • Page 457

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Description The option is used to define the number of frame errors within the configured window which indicates the port has exceeded an acceptable error rate. A log event will be raised, and the port will be taken out of service by default.

  • Page 458

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Context config>port>ethernet>efm-oam>link-mon>errored-frame-period Description The option is used to define the number of errored frames within the configured window which indicates the port has gone beyond an acceptable error rate and should be considered degraded. This is a first level warning that a port may be suspect. This generates an information log event message only and will be recorded in the Port event index but has no port level actions when the error count is equal to or greater than the threshold.

  • Page 459

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Parameters packets — The number of received packets. Values 1 to 4,294,967,295 Default 1,488,095 (representing 1 Gb/s @ 1s) errored-frame-seconds Syntax errored-frame-seconds Context config>port>ethernet>efm-oam>link-monitoring Description The context used to define errored frame seconds parameters including thresholds, and windows of time to which the error count will be compared.

  • Page 460

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Description The option is used to define the number of errors seconds within the configured window which indicates the port has exceeded an acceptable error rate. A log event will be raised, and the port will be taken out of service by default.

  • Page 461

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Description This command allows the symbol error event threshold crossing actions to transmit the Event Notification OAM PDU with the specific Link Event TLV information. The Event Notification OAM PDU will only be generated on the initial sf-threshold is reached. No subsequent notification will be sent until the event that triggered the notification clears, through manual intervention or a window where the configured sd-threshold is not reached.

  • Page 462

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Description This command defines the number of symbol errors within the configured window which indicates the port has exceeded an acceptable error rate. A log event will be raised, and the port will be taken out of service by default. Configuration options exist to take additional actions when the error rate exceeds the threshold.

  • Page 463

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Context config>port>ethernet> efm-oam>link-mon>errored-frame config>port>ethernet>efm-oam>link-mon>errored-frame-period config>port>ethernet>efm-oam>link-mon>errored-frame-seconds config>port>ethernet>efm-oam>link-mon>errored-symbols Description This command enables or disables the local counting, thresholding and actions associated with this type of local monitor. Peer received errors are not controlled by this command. Reaction to peer messaging is defined in the peer-rdi-rx hierarchy.

  • Page 464

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Description The context allows the operator to set different flags in the Information OAM PDU. The flags can be used to notify the peer that a local signal failure threshold has been exceeded within the configured window.

  • Page 465

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Interactions: The signal failure threshold will trigger these actions. Default local-port-action out-of-service Parameters log-only — Keyword that prevents the port from being affected when the configured signal failure threshold is reach within the window. The event will be logged but the port will remain operational.

  • Page 466

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Default critical-event local-port-action out-of-service Parameters local-port-action — Defines whether or not the local port will be affected when a critical event is received from a peer. log-only — Keyword that prevents the port from being affected when the local peer receives a critical event.

  • Page 467

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Description This command defines how to react to the reception of event TLVs contained in the Event Notification OAMPDU. The event TLVs contained in the event notification OAMPDU will be analyzed to determine if the peer has crossed the error threshold for the window. The analysis does not consider any local signal degrades or signal failure threshold.

  • Page 468

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 transmit-interval Syntax [no] transmit-interval interval [multiplier multiplier] Context config>port>ethernet>efm-oam Description This command configures the transmit interval of OAM PDUs. Default transmit-interval 10 multiplier 5 Parameters interval — Specifies the transmit interval. Values 1 to 600 (in 100 milliseconds) multiplier —...

  • Page 469

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 The no form of the command disables tunneling. Default no tunneling egress-rate Syntax egress-rate sub-rate no egress-rate Context config>port>ethernet Description This command configures the rate of traffic leaving the network. The configured sub-rate uses packet-based accounting.

  • Page 470

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Context config>port>ethernet Description This command configures port link dampening timers which reduce the number of link transitions reported to upper layer protocols. The hold-time value is used to dampen interface transitions. When an interface transitions from an up state to a down state, it is immediately advertised to the rest of the system if the hold-time down interval is zero, but if the hold-time down interval is greater than zero, interface down transitions are not advertised to upper layers until the hold-time down interval has expired.

  • Page 471

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Description This command enables the context to configure ingress and egress HSMDA scheduler override parameters. Executing hsmda-scheduler-override places the current CLI context into the egress scheduler override node either at the ingress MDA or egress port level. Default values are listed in Table Table 46...

  • Page 472

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 hs-scheduler-overrides Syntax hs-scheduler-overrides [create] no hs-scheduler-overrides Context config>port>ethernet>egress Description This command enables the context to configure HS scheduler overrides. Parameters create — Keyword used to create HS scheduler overrides. This keyword is requirement and can be enabled or disabled in the environment>create context. group Syntax group group-id rate rate...

  • Page 473

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 scheduling-class Syntax scheduling-class class rate rate scheduling-class class weight weight-in-group no scheduling-class class Context config>port>ethernet>egress>hs-scheduler-overrides Description This command configures a scheduling class. The no form of the command removes the parameters from the scheduler override configuration.

  • Page 474

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Parameters secondary-shaper-name — Specifies the secondary shaper name up to 32 characters in length. aggregate Syntax [no] aggregate Context config>port>ethernet>egress>hs-secondary-shaper Description This command enables the context to configure aggregate parameters. The no form of the command removes the parameter values from the configuration. low-burst-max-class Syntax low-burst-max-class class...

  • Page 475

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 class Syntax [no] class class-number Context config>port>ethernet>egress>hs-secondary-shaper Description This command specifies the hs-secondary-shaper class. The no form of the command reverts to the default. Parameters class-number — Specifies the HS secondary shaper class identifier. Values 1 to 6 group...

  • Page 476

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Context config>port>ethernet>hsmda Description This command overrides the max-rate parameters configured in the hsmda-scheduler-policy associated with the egress port or ingress MDA. When a max-rate is defined at the override level, the HSMDA scheduler policy’s max-rate parameter is ignored. The hsmda-scheduler-override max-rate command supports a max parameter that allows the override command to restore the default of not having a rate limit on the port scheduler.

  • Page 477

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 When the scheduling class is not a member of a weighted group, the scheduling-class command may be used to modify the maximum rate allowed for the scheduling class. This is done using the rate parameter followed by either the max keyword or an actual rate defined as megabits-per-second.

  • Page 478

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 ingress-rate Syntax ingress-rate sub-rate no ingress-rate Context config>port>ethernet Description This command configures the maximum amount of ingress bandwidth that this port can receive with the configured sub-rate using packet-based accounting. The ingress-rate command is only valid for oversubscribed Ethernet MDAs. See the Oversubscribed Ethernet MDAs section for details.

  • Page 479

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Description This command specifies the load balancing algorithm to be used on this port. In the default mode, no load-balancing-algorithm, the port inherits the global settings. The value is not applicable for ports that do not pass any traffic. The configuration of load-balancing-algorithm at logical port level has three possible values: •...

  • Page 480

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Context config>port>ethernet Description This command configures the minimum transmitted frame length. Parameters byte-length — Specifies the number of bytes for the minimum frame length. Values 64, 68 Default 64 bytes pbb-etype Syntax pbb-etype [ethertype-value] no pbb-etype Context config>port>ethernet...

  • Page 481

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Description This command configures the Ethertype used for Q-in-Q encapsulation. The no form of this command reverts the qinq-etype value to the default. Parameters qinq-etype-value — Specifies the qinq-etype to expect in the form of 0x600 to 0xfff. Values 1536 to 65535 in decimal or hex formats report-alarm...

  • Page 482

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Context config>port>ethernet Description This command enables sFlow data collection for a port and its SAPs that support sFlow data collection. The no form of this of this command disables sFlow. Default no sflow single-fiber Syntax [no] single-fiber Context...

  • Page 483

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Syntax Context config>port>ethernet Description This command enables the Ethernet Synchronization Messaging Channel (ESMC) for the Ethernet port. ESMC carries the Synchronization Status Message (SSM) code representing the quality level of the source of frequency of the central clock of the node. code-type Syntax code-type [sonet | sdh]...

  • Page 484

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Description This command configures Ethernet Symbol Monitoring parameters. Support for symbol monitoring is hardware dependent. An error message indicating that the port setting cannot be modified will be presented when attempting to enable the feature or configure the individual parameters on unsupported hardware.

  • Page 485

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 multiplier — Specifies the multiplier used to scale the symbol error ratio. Values 1 to 9 window-size Syntax window-size seconds no window-size Context config>port>ethernet>sym-mon Description This command specifies sliding window size over which the symbols are sampled to detect signal failure or signal degraded conditions.

  • Page 486

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Description This command configures a 10 Gb/s interface to be in Local or Wide Area Network (LAN or WAN) mode. When configuring the port to be in WAN mode certain SONET/SDH parameters can be changed to reflect the SONET/SDH requirements for this port. When the port is configured for LAN mode, all SONET/SDH parameters are pre-determined and not configurable.

  • Page 487

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 no sf-threshold Context config>port>ethernet>crc-monitor Description This command specifies the error rate at which to declare the Signal Fail condition on an Ethernet interface. The value represents M*10E-N errored frames over total frames received over W seconds of the sliding window. The CRC errors on the interface are sampled once per second.

  • Page 488: Port Commands

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Default no down-on-internal-error Parameters tx-disable — Specifies that the laser should be disabled if an internal MAC transmit error is encountered. When used, this option requires that the operator explicitly cycle the admin state of the port to clear the error and re-enable the laser. single-fiber Syntax [no] single-fiber...

  • Page 489

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Description This command configures the Connectivity Association (CA) for this port. The specified CA provides the MACsec parameter to be used or negotiated with other peers. Parameters ca-name — Specifies the appropriate ca to be used under this port. Values Up to 32 characters.

  • Page 490

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 max-peer Syntax max-peer max-peer no max-peer Context config>port>ethernet>dot1x>macsec Description This command configures the max peer allowed under this MACsec instance. Note: The peer establishment is a race condition and first come first serve. On any security zone, only 32 peers can be supported.

  • Page 491

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Description This command shuts down the MACsec under this port specifically, including MKA negotiation. In the shutdown state, this port is not MACsec capable and all PDUs will be transmitted without encryption and authentication. The no form of this command puts the port in MACsec-enabled mode.

  • Page 492

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 auto — Enables 802.1x authentication. The port starts in the unauthorized state, allowing only EAPoL frames to be sent and received through the port. Both the router and the host can initiate an authentication procedure. The port will remain in un- authorized state (no traffic except EAPoL frames is allowed) until the first client is authenticated successfully.

  • Page 493

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 no re-auth-period Context config>port>ethernet>dot1x Description This command configures the period after which re-authentication is performed. This value is only relevant if re-authentication is enabled. The no form of this command returns the value to the default. Default 3600 Parameters...

  • Page 494

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 supplicant-timeout Syntax supplicant-timeout seconds no supplicant-timeout Context config>port>ethernet>dot1x Description This command configures the period during which the router waits for a client to respond to its EAPOL messages. When the supplicant-timeout expires, the 802.1x authentication session is considered to have failed.

  • Page 495

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 The no form of this command disables tunneling of untagged 802.1x frames. Default no tunneling down-when-looped Syntax down-when-looped Context config>port>ethernet Description This command configures Ethernet loop detection attributes. dot1x Syntax dot1x Context config>port>ethernet Description This command enables access to the context to configure port-specific 802.1x authentication attributes.

  • Page 496: Lldp Port Commands

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Default no retry-timeout Parameters timer — Specifies the minimum wait time before re-enabling port after loop detection. Values 0, 10 to 160 use-broadcast-address Syntax [no] use-broadcast-address Context config>port>ethernet>dwl Description This command specifies whether or not the down when looped destination MAC address is the broadcast address, or the local port MAC address, as specified in the port's MAC address.

  • Page 497

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 admin-status Syntax admin-status {rx | tx | tx-rx | disabled} Context config>port>ethernet>lldp>dstmac Description This command configures LLDP transmission/reception frame handling. Parameters rx — Specifies the LLDP agent will receive, but will not transmit LLDP frames on this port. tx —...

  • Page 498

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 tunnel-nearest-bridge Syntax [no] tunnel-nearest-bridge Context config>port>ethernet>lldp>dstmac Description The command allows LLDP packets received on the port with the destination address of the nearest bridge to be tunneled without being intercepted on the local port. The dest-mac nearest-bridge must be disable for tunneling to occur.

  • Page 499: Network Port Commands

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Parameters port-desc — Indicates that the LLDP agent should transmit port description TLVs. sys-name — Indicates that the LLDP agent should transmit system name TLVs. sys-desc — Indicates that the LLDP agent should transmit system description TLVs. sys-cap —...

  • Page 500

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 The no form of this command removes the accounting policy association from the network interface, and the accounting policy reverts to the default. Default No accounting policies are specified by default. You must explicitly specify a policy. If configured, the accounting policy configured as the default is used.

  • Page 501: Interface Group Handler Commands

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 config>port>tdm>ds1>network config>port>tdm>ds3>network config>port>tdm>e1>network config>port>tdm>e3>network Description This command specifies the existing network queue policy which defines queue parameters such as CBS, high priority only burst size, MBS, CIR and PIR rates, as well as forwarding- class to queue mappings.

  • Page 502: Multilink-bundle Port Commands

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 The no form of this command removes the specified port ID from the associated IGH. Parameters portid — Identifies the port to be associated with the interface group handler. threshold Syntax threshold num-members no threshold Context config>interface-group-handler Description...

  • Page 503

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 no fragment-threshold Context config>port>multilink-bundle Description This command sets the maximum length in bytes of a fragment transmitted across a multilink bundle. The no form of this command resets the fragment threshold back to the default value. Default Parameters fragment-threshold —...

  • Page 504

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 port-id slot/mda/port.channel eth-sat-id esat-id/slot/port esat keyword 1 to 20 pxc-id pxc-id.sub-port keyword 1 to 64 sub-port a, b minimum-links Syntax minimum-links minimum-links no minimum-links Context config>port>multilink-bundle Description This command sets the minimum number of links that must be active for the bundle to be active.

  • Page 505

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Description This command defines the identifier for the MLFR bundle. The no form of this command resets the value to null. Default null Parameters frf16-identifier — Specifies the bundle ID string. The string can be up to 49 characters long.

  • Page 506

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 qos-profile Syntax qos-profile profile-id no qos-profile Context config>port>ml-bundle>mlfr>ingress config>port>ml-bundle>mlfr>egress config>port>tdm>channel-group>frame-relay>egress config>port>sonet-sdh>path>frame-relay>egress Description This command specifies the ingress or egress QoS profile to be used for the configuration of the ingress or egress QoS parameters of an MLFR bundle or a Frame Relay port with FRF.12 UNI/NNI fragmentation enabled.

  • Page 507

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Context config>port>ml-bundle>mlfr>frame-relay Description This command configures the DCE/DTE mode of the Frame Relay interface. Parameters dce — Enables the DCE mode. dte — Enables the DTE mode. bidir — Enables the bidirectional mode for LMI types ANSI and ITU. n391dte Syntax n391dte intervals...

  • Page 508

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Parameters count — Specifies the number of errors that will place the bundle in an operationally down state. Values 1 to 10 n393dce Syntax n393dce count no n393dce Context config>port>ml-bundle>mlfr>frame-relay Description This command configures the DCE monitored event count for the LMI. Parameters count —...

  • Page 509

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 t392dce Syntax t392dce keepalive no t392dce Context config>port>ml-bundle>mlfr>frame-relay Description This command configures the DCE keepalive timer value for the LMI. Parameters keepalive — Specifies the expected interval in seconds between status inquiries issued by the DTE equipment. Values 5 to 30 hello-interval...

  • Page 510

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Parameters timer — Specifies the wait period in seconds. Values 1 to 10 retry-limit Syntax retry-limit count no retry-limit Context config>port>ml-bundle>mlfr Description This command specifies the value of the MLFR bundle N_RETRY counter. The counter specifies the number of times a retransmission onto a bundle link will be attempted before an error is declared and the appropriate action taken.

  • Page 511

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Description This command sets the maximum length in bytes of a fragment transmitted across a frame relay port with the FRF.12 UNI/NNI fragmentation enabled. The no form of this command resets the fragment threshold back to the default value. Default Parameters fragment-threshold —...

  • Page 512

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Description This command specifies the egress QoS profile to be used for the outgoing traffic over this MLPPP bundle. The no form of the command removes the parameters from the configuration. Parameters profile-id — Specifies the egress QoS profile to be used for the outgoing traffic over this MLPPP bundle.

  • Page 513

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 magic-number Syntax [no] magic-number Context config>port>ml-bundle>mlppp Description This command allows loopback detection to be enabled and disabled for MLPPP bundles. It is disabled by default. When the magic number option is disabled, the magic number option will not be requested when a member is trying to bring up the LCP layer on a member link;...

  • Page 514

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 stateless-aps-switchover Syntax [no] stateless-aps-switchover Context config>port>ml-bundle> mlppp Description This command specifies whether the bundle will perform a stateful or a stateless APS switchover. The value can be changed for APS bundle protection groups of type MLPPP. A stateless switchover implies that PPP is re-negotiated on each member link after the switchover.

  • Page 515

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Description This command configures a protect bundle that is part of this BPGrp. Parameters bundle-id — Specifies the protection multilink bundle in the bundle protection group. The command syntax must be configured as follows: Values bundle-type-slot/mda.bundle-num bundle-PPP or IMA-slot/mda.bundle-...

  • Page 516

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Default no short-sequence working-bundle Syntax [no] working-bundle bundle-id Context config>port>multilink-bundle Description This command configures a working bundle that is part of this BPGrp. Parameters bundle-id — Specifies the working multilink bundle in the bundle protection group. The command syntax must be configured as follows: Values bundle-type-slot/mda.bundle-num...

  • Page 517

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Context config>port>multilink-bundle Description This command enables the context to configure parameters for an Inverse Multiplexing over ATM (IMA) group. An IMA group is a collection of physical links bundled together and assigned to an ATM interface. IMA enables a high-speed channel that is composed of ATM cells to be transported as a number of lower-speed circuits.

  • Page 518

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Where: M is the IMA frame size (128) Primary member link speed is either E-1 — 1920 kb/s or DS-1 — 1539 kb/s. E-1 speed is used for a group with no members. The total ATM bandwidth of services over shaped VCs cannot exceed the MCAB value as result of adding more services or removing member links.

  • Page 519

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 esat keyword 1 to 20 pxc-id pxc-id.sub-port keyword 1 to 64 sub-port a, b aps-id aps-group-id[.channel] keyword group-id 1 to 128 test-pattern Syntax test-pattern pattern no test-pattern Context config>port>ml-bundle>ima>test-pattern-procedure Description This command specifies the transmit test pattern in an IMA group loopback operation. This value can only be changed when the test-pattern-procedure command is shut down The no form of this command restores the test-pattern to the default.

  • Page 520: Sonet/sdh Port Commands

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Description This command configures the IMA version for the multilink bundle group. If there is a version mismatch between this IMA group and the far end IMA group, the IMA group will become operationally down. Automatic version changing is not supported. To change the IMA version, all member links must be removed from the group first.

  • Page 521

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Parameters loop-timed — The link recovers the clock from the received data stream. node-timed — The link uses the internal clock when transmitting data. framing Syntax framing {sonet | sdh} Context config>port>sonet-sdh Description This command specifies SONET/SDH framing to be either SONET or SDH. This command is supported by TDM satellite.

  • Page 522

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 vt2 — Configures the path as a virtual tributary group of type vt2. vt15 — Configures the path as a virtual tributary group of type vt15. hold-time Syntax hold-time hold-time {[up hold-time up] [down hold-time down]} no hold-time Context config>port>sonet-sdh...

  • Page 523

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 This command is supported by TDM satellite. Default no loopback Parameters line — Set the port into line loopback state. internal — Set the port into internal loopback state. report-alarm Syntax [no] report-alarm [loc] [lais] [lrdi] [ss1f] [lb2er-sd] [lb2er-sf] [slof] [slos] [lrei] Context config>port>sonet-sdh Description...

  • Page 524

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 slof — Reports section loss of frame errors. When configured, slof alarms are raised and cleared. Default slof alarms are issued slos — Reports a section loss of signal error on the transmit side. When configured, slos alarms are raised and cleared.

  • Page 525

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 speed Syntax speed {oc3 | oc12} no speed Context config>port>sonet-sdh Description This command configures the speed of a SONET/SDH port as either OC3 or OC12. The framer for this MDA operates in groups of four. Changing the port speed for a port requires resetting the framer and causes a slight disruption on all four ports.

  • Page 526: Sonet/sdh Path Commands

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 This command is supported on TDM satellite. Default no tx-dus threshold Syntax threshold {ber-sd | ber-sf} rate threshold-rate no threshold {ber-sd | ber-sf} Context config>port>sonet-sdh Description This command configures the line signal degradation bit error rate (BER) and line signal failure thresholds.

  • Page 527

    The sonet-sdh-index differs for SONET and SDH ports. Values sts192 (for the 7950 XRS only) sts1-x.x (for the 7450 ESS and 7750 SR), tu3, vt2, vt15 SONET OC-192 STS-48-index...

  • Page 528

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 vt2 — Configures the path STS1 payload as vt2 as a virtual tributary group. Only allowed on STS-1 nodes (SONET VT container). vt15 — Configures the path as a virtual tributary group. Only allowed on STS-1 nodes (SONET VT container).

  • Page 529

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 prdi — Reports path remote defect indication errors. When configured, prdi alarms are raised and cleared. Default prdi alarms are not issued pplm — Reports a path payload mismatch, as a result the channel will be operationally downed.

  • Page 530

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Description This command configures the encapsulation method used to distinguish customer traffic on an access SONET/SDH channel sub-port. When the encap-type is set to ATM the CRC default cannot be changed. When the encap-type is ATM, ATM sub-layer verification (GR-1248-CORE, Generic Requirements for Operations of ATM Network Elements (NEs)) is automatically enabled.

  • Page 531

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 wan-mirror — The port is used for mirroring of frame-relay and POS ports. On these ports, no link management protocol would run. cisco-hdlc — Monitors line status on a serial interface by exchanging keepalive request messages with peer network devices.

  • Page 532

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 scramble Syntax [no] scramble Context config>port>sonet-sdh>path Description This command enables SONET/SDH payload scrambling. Scrambling randomizes the pattern of 1s and 0s carried in a SONET frame. Rearranging or scrambling the pattern prevents continuous strings of all 1s or all 0s and meets the needs of physical layer protocols that rely on sufficient transitions between 1s and 0s to maintain clocking.

  • Page 533

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 The no form of this command resets the string to its default. This command is supported on TDM satellite. Default The default J1 value is Alcatel-Lucent XXX YYY where XXX is the platform number, such as “7750”...

  • Page 534: Atm Interface Commands

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Description This command configures the number of continual keepalive packets that have to be received in order to declare the link up. It is expected that the nodes at the two endpoints of the cHDLC link are provisioned with the same values.

  • Page 535

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 mapping Syntax mapping mapping Context config>port>tdm>ds3>atm Description This command configures the ATM cell mapping for DS-3 channels. The mapping value specifies the cell mapping that is to be used on this ATM interface. Default direct cell mapping Parameters mapping —...

  • Page 536

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 buffer-pool Syntax buffer-pool value Context config>port>sonet-sdh>path>atm>custom-buffer-mode Description This command configures the ATM port buffer pool percentage. Parameters value — Specifies the percentage of the buffers configured on this interface over the maximum allowed. Values 1 to 100 vc-threshold Syntax...

  • Page 537

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Description This command enables the context to configure egress traffic attributes for the ILMI link. ingress Syntax ingress Context config>port>sonet-sdh>path>atm>ilmi Description This command enables the context to configure ingress traffic attributes for the ILMI link. traffic-desc Syntax traffic-desc traffic-desc-profile-id...

  • Page 538: Frame Relay Commands

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 value — Specifies the number of consecutive polls on this interface for which no ILMI response message is received before ILMI connectivity is declared lost. Values 1 to 255 test-frequency seconds — Specifies the frequency for testing for connectivity when the link is establishing before polling begins.

  • Page 539

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 The port’s encapsulation type must be set to frame-relay in the config>port>sonet- sdh>path>encap-type frame-relay context. The no form of this command removes the Frame Relay LMI operational parameters. frf-12 Syntax [no] frf-12 Context config>port>tdm>ds1>channel-group>frame-relay config>port>tdm>e1>channel-group>frame-relay config>port>tdm>ds3>frame-relay config>port>tdm>e3>frame-relay...

  • Page 540

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Parameters profile-id — Specifies the profile number. The value can only be modified if the FR port is shut down. Values 1 to 128 fragment-threshold Syntax fragment-threshold fragment-threshold no fragment-threshold Context config>port>tdm>channel-group>frame-relay>frf.12 config>port>sonet-sdh>path>frame-relay>frf.12 Description This command sets the maximum length in bytes of a fragment transmitted across a frame relay port with the FRF.12 UNI/NNI fragmentation enabled.

  • Page 541

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 config>port>tdm>e3>frame-relay Description This command configures the Local Management Interface (LMI) type for Frame Relay interfaces. LMIs are sets of enhancements to the basic Frame Relay specification. The no form of this command changes the LMI type back to the default value. Default Parameters ansi —...

  • Page 542

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 config>port>tdm>ds3>frame-relay config>port>tdm>e1>channel-group>frame-relay config>port>tdm>e3>frame-relay Description This command sets the DTE full status polling interval for the Frame Relay Local Management Interface (LMI). The number specifies the frequency at which inquiries expect a full status report. The no form of this command returns the n391dte counter to the default value.

  • Page 543

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 config>port>tdm>ds3>frame-relay config>port>tdm>e1>channel-group>frame-relay config>port>tdm>e3>frame-relay Description This command sets the DTE error threshold for the Frame Relay Local Management Interface (LMI). The count specifies the number of errors needed to bring down a link. The no form of this command returns the n392dte counter to the default value. Default Parameters count —...

  • Page 544

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 config>port>tdm>e1>channel-group>frame-relay config>port>tdm>e3>frame-relay Description This command sets the DTE monitored event count for the Frame Relay Local Management Interface (LMI). The no form of this command returns the n393dte counter to the default value. Default Parameters number —...

  • Page 545: Tdm Commands

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 config>port>tdm>e1>channel-group>frame-relay config>port>tdm>e3>frame-relay Description This command sets the DCE keepalive timer for the Frame Relay Local Management Interface (LMI). This number specifies the period at which the DCE checks for keepalive responses from the DTE and updates status depending on the DCE error threshold value. The no form of this command returns the t392dce keepalive timer to the default value.

  • Page 546

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 North America uses the T-Carrier system while Europe uses the E-Carrier system of transmission, using multiples of the DS- system. Digital signals are carried inside the carrier systems. T-1 transmits DS-1-formatted data at 1.544 Mb/s through the network. The corresponding European carrier is E-1 with a data rate of 2.048 Mb/s.

  • Page 547

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Syntax e1 [e1-id] Context config>port>tdm Description This command enables the context to configure E-1 parameters. E-1 is a basic time division multiplexing scheme used to carry digital circuits. It is also a standard WAN digital communication format designed to operate over copper facilities at a rate of 2.048 Mb/s.

  • Page 548

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Parameters sonet-sdh-index — Specifies the components making up the specified SONET/SDH Path. Depending on the type of SONET/SDH port the sonet-sdh-index must specify more path indexes to specify the payload location of the path. The sonet-sdh-index differs for SONET and SDH ports.

  • Page 549

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 2e20 — Sends a pseudo-random 2^20 -1 pattern. Not available on channelized ASAP MDAs. 2e23 — Sends a pseudo-random 2^23 -1 pattern. bit-error-insertion Syntax bit-error-insertion rate no bit-error-insertion Context config>port>tdm>ds1 config>port>tdm>ds3 config>port>tdm>e1 config>port>tdm>e3 Description This command inserts bit errors into a running BERT test.

  • Page 550

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Context config>port>tdm Description This command configures link dampening timers in 100s of milliseconds. This guards against reporting excessive interface transitions. This is implemented by not advertising subsequent transitions of the interface to upper layer protocols until the configured timer has expired. This command is only supported on the m4-chds3-as, m12-chds3-as, and c4-ds3 MDAs.

  • Page 551

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Description This command applies only to a DS-1 port configured with a 'short' buildout. The length command configures the length of the line (in feet). For line lengths longer than 655 feet, configure the DS-1 port buildout as 'long'. For 'long' buildout the following values are valid: NotApplicable —...

  • Page 552

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Description This command specifies that the associated DS-3 is a channelized DS-3 with DS-1/E-1 sub- channels. Depending on the MDA type, the DS-3 parameters must be disabled if clear channel is the default (for example, on m12-ds3 MDAs). Clear channel is a channel that uses out-of-band signaling, not in-band signaling, so the channel's entire bit rate is available.

  • Page 553

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 The following tables show MDAs that support loop timing at DS3/E3 and DS1/E1 channelization options. TDM DS3/E3 LoopTimed Default Channelized OC-12 node-timed Channelized OC-3 node-timed Channelized DS3/E3 node-timed Channelized ASAP OC-12 node-timed Channelized ASAP OC-3 node-timed Channelized ASAP DS3/E3 node-timed...

  • Page 554

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 32 for ATM channel-groups configured under DS-1 and E-1, and for ATM E-3 and DS-3 channels/ports. The default cannot be changed. Parameters 16 — Uses 16 bit checksum for the associated port/channel. 32 — Uses 32 bit checksum for the associated port/channel. down-count Syntax down-count down-count...

  • Page 555

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 • PLCP Severely Errored Framing Seconds • PLCP Alarm State • PLCP Unavailable Seconds Counter When ATM direct cell mapping is used, the result of the verification includes: • Out of Cell Delineation (OCD) event count. The OCD event count is described in RFC 2515, Definitions of Managed Objects for ATM Management.

  • Page 556

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 cem — On circuit emulation CMAs and MDAs, only the cem encap-type is supported. All other values are blocked with an appropriate warning. The cem encap-type is not supported on other CMAs and MDAs and are blocked with an appropriate warning. feac-loop-respond Syntax [no] feac-loop-respond...

  • Page 557

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 framing (E-1) Syntax framing {no-crc-g704 | g704 | e1-unframed} Context config>port>tdm>e1 Description This command specifies the E-1 framing to be used with the associated channel. Default g704 Parameters g704 — Configures the E-1 port for G.704 framing. no-crc-g70 —...

  • Page 558

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Default E-3 non-ATM:g751 and cannot be changed. E-3 ATM: g832 and cannot be changed. Parameters g751 — Configures the E-3 port/channel for g751 framing. g832 — Configures the E-3 port/channel for g832 framing. unframed-e3 — Specifies e-3 unframed mode for E-3 interfaces. This parameter allows the configuration of an unstructured E-3 channel on a CES MDA.

  • Page 559

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Default all-ones Parameters all-ones — Defines the 8 bit value to be transmitted as 11111111. pattern — Transmits a user-defined pattern. Values 0 to 255, accepted in decimal, hex or binary idle-signal-fill Syntax idle-signal-fill {all-ones} idle-signal-fill pattern pattern no idle-signal-fill Context...

  • Page 560

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Description This command causes all data bits to be inverted, to guarantee ones density. Typically used with AMI line encoding. Default no invert-data loopback Syntax loopback {line | internal | fdl-ansi | fdl-bellcore | payload-ansi | inband-ansi | inband- bellcore} no loopback Context...

  • Page 561

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Description This command puts the specified port or channel into a loopback mode. The corresponding port or channel must be in a shutdown state in order for the loopback mode to be enabled. The upper level port or channel or parallel channels should not be affected by the loopback mode.

  • Page 562

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 mdl-transmit Syntax mdl-transmit {path | idle-signal | test-signal} no mdl-transmit [path | idle-signal | test-signal] Context config>port>tdm>ds3 Description This command enables the transmission of an MDL message on a DS-3/E-3 over channelized interface. The no form of this command disables transmission of the specified message or all messages.

  • Page 563

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Context config>port>tdm>ds1 config>port>tdm>e1 Description This command enables logging of DS-1/DS-3 or E-1/E-3 alarms for DS-1/DS-3 or E-1/E-3 ports or channels. The no form of this command disables logging of the specified alarms. Parameters ais — Reports alarm indication signal errors. When configured, ais alarms are not raised and cleared.

  • Page 564

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 speed Syntax speed {56 | 64} Context config>port>tdm>ds1>channel-group config>port>tdm>e1>channel-group Description This command sets the speed of the DS-0 channels used in the associated channel-group. Default Parameters 56 — Specifies that 56k byte (7-bits per byte) encoding will be used for the associated DS-0 channels.

  • Page 565

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 config>port>tdm>e1 Description This command configures the line signal degradation bit error rate (BER) and line signal failure thresholds. Line signal (b2) bit interleaved parity error rates are measured and when they cross either the degradation or failure thresholds alarms are raised (see the report-alarm command), furthermore if the failure threshold is crossed the link will be set to operationally down.

  • Page 566: Lag Commands

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 2.19.2.25 LAG Commands Syntax [no] lag [lag-id] Context config Description This command creates the context for configuring Link Aggregation Group (LAG) attributes. A LAG can be used to group multiple ports into one logical link. The aggregation of multiple physical links allows for load sharing and offers seamless redundancy.

  • Page 567

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 access Syntax access Context config>lag Description This command enables the context to configure access parameters. adapt-qos Syntax adapt-qos {link | port-fair | distribute [include-egr-hash-cfg]} Context config>lag>access Description This command specifies how the LAG SAP queue and virtual scheduler buffering and rate parameters are adapted over multiple active XMAs/MDAs.

  • Page 568

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 A LAG instance that is currently in adapt-qos link mode may be placed at any time in port-fair mode. Similarly, a LAG instance that is currently in adapt-qos port-fair mode may be placed at any time in link mode. However, a LAG instance in adapt-qos distribute mode may not be placed into port-fair (or link) mode while QoS objects are associated with the LAG instance.

  • Page 569

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 booking-factor Syntax booking-factor factor no booking-factor Context config>lag>access config>port>ethernet>access Description This command specifies the booking factor applied against the port or LAG admin bandwidth by SAP admin bandwidth CAC. The service manager keeps track of the available admin bandwidth for each port or LAG configured with an admin bandwidth.

  • Page 570

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Description This command specifies whether a more efficient method of queue allocation for LAG SAPs should be utilized. The no form of the command disables the method of queue allocation for LAG SAPs. per-fp-sap-instance Syntax [no] per-fp-sap-instance Context...

  • Page 571

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 family Syntax family [ipv4 | ipv6] no family Context config>lag>bfd Description This command is used to specify which address family should be used for the micro-BFD session over the associated LAG links. Default family ipv4 Parameters ipv4 —...

  • Page 572

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 d: [0 to 255]D max-admin-down-time Syntax max-admin-down-time [[-1 to 3600] | infinite] no max-admin-down-time Context config>lag>bfd>family Description This command specifies the maximum amount of time the router will continue to forward traffic over a link after the micro-BFD sessions has transitioned to a Down state because it received an ADMIN-DOWN state from the far-end.

  • Page 573

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 multiplier Syntax multiplier [3 to 20] no multiplier Context config>lag>bfd>family Description This command specifies the detect multiplier used for a micro-BFD session over the associated LAG links. If a BFD control packet is not received for a period of multiplier X receive-interval then the session is declared down.

  • Page 574

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Default no remote-ip-address Parameters ip-address — Specifies the IP address. Values ipv4-address: a.b.c.d ipv6-address: x:x:x:x:x:x:x:x (eight 16-bit pieces) x:x:x:x:x:x:d.d.d.d x:-[0 to FFFF]H d: [0 to 255]D transmit-interval Syntax transmit-interval transmit-interval no transmit-interval Context config>lag>bfd>family Description This command specifies the transmit timer used for micro-BFD session over the associated LAG links.

  • Page 575

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Context config>lag Description This command enables OSPF or ISIS costing of a Link Aggregation Group (LAG) based on the available aggregated, operational bandwidth. The path cost is dynamically calculated based on the interface bandwidth. OSPF path cost can be changed through the interface metric or the reference bandwidth.

  • Page 576

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 If the encapsulation type of the LAG port is changed, the encapsulation type on all the port members will also change. The encapsulation type can be changed on the LAG port only if there is no interface associated with it. If the MTU is set to a non default value, it will be reset to the default value when the encap type is changed.

  • Page 577

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Note that if any of the parameters are omitted, the existing configuration is preserved. The default parameter values are used if a parameter is never explicitly configured. Default no lacp Parameters mode — Specifies the mode in which LACP will operate. Values passive —...

  • Page 578

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Context config>lag Description This command specifies the interval signaled to the peer and tells the peer at which rate it should transmit. Default fast Parameters slow — Transmits packets every 30 seconds. fast — Transmits packets every second. lacp-xmit-stdby Syntax [no] lacp-xmit-stdby...

  • Page 579

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Context config>lag>link-map-profile Description This command designates one of the configured ports of the LAG to be used on egress as either a primary or secondary link (based on the option selected) by all SAPs/network interfaces that use this LAG link map profile.

  • Page 580

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 per-link-hash — Specifies egress traffic for SAPs/network interfaces using this link- map-profile is rehashed on remaining, available LAG links using per-link-hash algorithm. SAP/network interface QoS configurations dictate what traffic is discarded on any link that may become oversubscribed as result of the re-hash. port Syntax port port-id [port-id] [priority priority] [subgroup sub-group-id]...

  • Page 581

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 priority — Port priority used by LACP. The port priority is also used to determine the primary port. The port with the lowest priority is the primary port. In the event of a tie, the smallest port ID becomes the primary port.

  • Page 582

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Description This command configures the behavior for the Link Aggregation Group (LAG) if the number of operational links is equal to or below a threshold level. The no form of this command reverts to the default values. Default 0 action down Parameters...

  • Page 583

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Parameter specified with the command defines what type of ports are allowed in a LAG, and what is the weight of each port for total LAG weight calculation. The no form specifies that all LAG links must be of the same speed. Each link weight is 1. The no form disables mixed port-speed LAG operation if there are no mixed-speed links.

  • Page 584

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 highest-weight — Selects a sub-group with the highest aggregate weight as an active subgroup (not applicable to “power-off” mode of operations). Aggregate weight is calculated as the sum of (65535 - port priority) all ports within a sub-group. best-port —...

  • Page 585: Eth Tunnel Commands

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 The no form of this command disabled weight-threshold operation in LAG. Default 0 action down Parameters value — The decimal integer threshold number of operational links for the LAG at or below which the configured action will be invoked. If the number of operational links exceeds the port-threshold value, any action taken for being below the threshold value will cease.

  • Page 586

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Context config>eth-tunnel Description This command configures eth-tunnel CCM dampening timers. The no form of the command reverts to the default. Default no ccm-hold-time Parameters down-timeout — Specifies the eth-tunnel CCM down timers. Values 0 to 1000 in 100ths of seconds Default up-timeout —...

  • Page 587

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Description This command configures the encapsulation method. Default encap-type dot1q Parameters dot1q — Specifies dot1q encapsulation. qinq — Specifies qinq encapsulation. Syntax [no] mac ieee-address Context config>eth-tunnel>ethernet Description This command assigns a specific MAC address to an Ethernet port, Link Aggregation Group (LAG), Ethernet tunnel or BCP-enabled port or sub-port.

  • Page 588

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Context config>eth-tunnel>lag-emulation>access Description This command configures how the Ethernet Tunnel group SAP queue and virtual scheduler buffering and rate parameters are adapted over multiple active MDAs. The no form of the command reverts the default. Default no adapt-qos Parameters...

  • Page 589

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 no path-threshold Context config>eth-tunnel>lag-emulation Description This command configures the behavior for the eth-tunnel if the number of operational members is equal to or below a threshold level Parameters num-paths — Specifies the threshold for the Ethernet Tunnel group. Values 0 to 15 protection-type...

  • Page 590

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 path Syntax [no] path path-index Context config>eth-tunnel Description This command configures one of the two paths supported under the Ethernet tunnel. Although the values indicate 1 to 8, only two paths, 1 and 2, are currently supported. The no form of this command removes the path from under the Ethernet tunnel.

  • Page 591

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 The following port-level configuration needs to be the same across the two member ports of an Ethernet tunnel: • port>ethernet>access>{ingress|egress}>queue-group • port>ethernet>egress-scheduler-policy • port>access>egress>pool • port>ethernet>dot1q-etype • port>ethernet>qinq-etype • port>ethernet>pbb-etype • port>ethernet>mtu The Ethernet tunnel will inherit the configuration from the first member port for these parameters.

  • Page 592

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 The no form of this command is used just to indicate that a control-tag is not configured. The procedure described above, based on ‘no path’ command must be used to un-configure/ change the control-tag assigned to the path. Default no control tag specified Parameters...

  • Page 593

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 md-index — Specifies the maintenance domain (MD) index value. Values 1 to 4294967295 ma-index — Specifies the MA index value. Values 1 to 4294967295 control-mep Syntax [no] control-mep Context config>eth-tunnel>path>eth-cfm>mep Description This command enables the Ethernet ring control on the MEP. The use of control-mep command is mandatory for a ring.

  • Page 594