Download  Print this page

Nokia 7450 Interface Configuration Manual

Ethernet service switch; service router; extensible routing system
Hide thumbs
   
1
2
Table Of Contents
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

Advertisement

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

Advertisement

Table of Contents
loading

  Related Manuals for Nokia 7450

  Summary of Contents for Nokia 7450

  • Page 1 INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 7450 ETHERNET SERVICE SWITCH 7750 SERVICE ROUTER 7950 EXTENSIBLE ROUTING SYSTEM INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 3HE 11968 AAAA TQZZA 01 Issue: 01 March 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.R1 Table of Contents Getting Started ................9 About This Guide..................9 Interface Configuration Process ..............10 Interfaces ..................11 Configuration Overview ................11 2.1.1 Chassis Slots and Cards ................12 2.1.2 MCMs .......................13 2.1.3 MDA-a, MDA-aXP, MDA, MDA-XP and MDA-e Modules......14 2.1.4 XMAs/C-XMAs...................16 2.1.5...
  • Page 4 INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 2.3.2.15 Link Layer Discovery Protocol (LLDP)............94 2.3.3 Per Port Aggregate Egress Queue Statistics Monitoring......98 Port Cross-Connect (PXC) ..............100 2.4.1 PXC Terminology ..................101 2.4.2 PXC - Physical Port in Cross-Connect (Loopback) Mode .......102 2.4.2.1 Operational State..................103 2.4.3 PXC Sub-Ports ..................104 2.4.3.1...
  • Page 5 INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 Ethernet Port Monitoring .................154 2.10 802.3ah OAM ..................157 2.10.1 OAM Events ....................160 2.10.1.1 Link Monitoring ..................160 2.10.2 Remote Loopback ...................167 2.10.3 802.3ah OAM PDU Tunneling for Epipe Service........167 2.10.3.1 802.3ah Grace Announcement..............168 2.11 MTU Configuration Guidelines ..............173 2.11.1 Default MTU Values ................173 2.11.2...
  • Page 6 INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 2.23.7 Configuring Channelized STM1/OC3 Parameters........214 2.23.7.1 Sample Cpipe Port Configurations ............215 2.23.8 Configuring ATM SAPs................216 2.23.8.1 ATM SAP in an IES Service ..............216 2.23.8.2 ATM SAP in an Epipe Service..............217 2.23.9 Configuring DWDM Port Parameters ............217 2.23.10 Configuring WaveTracker Parameters ............218 2.23.11...
  • Page 7 INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 2.25.1.17 E1 Commands..................274 2.25.1.18 E3 Commands..................276 2.25.1.19 LAG Commands ..................277 2.25.1.20 Ethernet Tunnel Commands..............280 2.25.1.21 Multi-Chassis Redundancy Commands ..........281 2.25.1.22 Forward Path Extension Commands............283 2.25.2 Configuration Command Descriptions.............283 2.25.2.1 Generic Commands.................284 2.25.2.2 Card Commands ..................286 2.25.2.3 MCM Commands..................290 2.25.2.4...
  • Page 8 INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 2.26.2.6 LAG Show Commands ................772 2.26.2.7 Monitor Commands .................783 2.26.2.8 Clear Commands..................793 2.26.2.9 Tools Commands ..................798 Standards and Protocol Support ..........823 3HE 11968 AAAA 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: Interface Configuration Process

    Getting Started INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 Note: This guide generically covers Release 15.0 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, for information on features supported in each load of the Release 15.0 software.
  • Page 11: 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 12: Chassis Slots And Cards

    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 13: Mcms

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 The 7750 SR-a platforms support IOM-a cards in dedicated chassis slots. The 7750 SR-a4 supports one physical IOM-a in slot 3. This IOM-a is represented in the CLI as card 1. The 7750 SR-a8 supports two physical IOM-a cards, one in slot 3, the other in slot 6.
  • Page 14: Mda-A, Mda-Axp, Mda, Mda-Xp And Mda-E Modules

    =============================================================================== 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 15 MDA type matches the provisioned type. If the parameters do not match, the MDA remains offline. 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).
  • Page 16: Xmas/C-Xmas

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 The following example shows the card, card-type, mda, and mda-type command usage in the 7750 SR-1e: A:SR1e>config# card 1 A:SR1e>config>card# card-type iom-e A:SR1e>config>card# mda 1 A:SR1e>config>card>mda# mda-type me10-10gb-sfp+ A:SR1e>config>card>mda# exit A:SR1e>config>card# mda 4 A:SR1e>config>card>mda# mda-type me1-100gb-cfp2 A:SR1e>config>card>mda# exit The following example displays the configuration: A:SR1e# admin display-config...
  • Page 17 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 A:XRS20>config>card# card-type xcm-x20 A:XRS20>config>card# mda 1 A:XRS20>config>card>mda# mda-type cx2-100g-cfp A:XRS20>config>card>mda# power-priority-level 130 A:XRS20>config>card>mda# exit A:XRS20>config>card# mda 2 A:XRS20>config>card>mda# mda-type cx20-10g-sfp A:XRS20>config>card>mda# power-priority-level 135 A:XRS20>config>card>mda# exit The following example displays the configuration: A:XRS20# admin display-config .
  • Page 18: Cmas

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 2.1.5 CMAs CMAs (Compact Media Adapter) are supported on the 7750 SR-c12 and SR-c4 and are configured and provisioned in the same manner as MDAs. Up to twelve CMAs may be provisioned on a 7750 SR-c12, and up to 4 CMAs may be provisioned on an SR-c4.
  • Page 19: Oversubscribed Ethernet Mdas

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 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. Versatile Service Module for more details.
  • Page 20 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 • If the service QoS policy for the SAP contains a Dot1p classification, the Dot1p field in the customer packets is used for classification on the MDA/CMA. • If the service QoS policy for the SAP contains a DSCP classification, the DSCP field in the customer packets is used for classification on the MDA/CMA.
  • Page 21: Channelized Mda/Cma Support

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 Table 3 Typical Mapping Of Classes Onto Queues/Threshold Counter {Queue Threshold Traffic Class} “fc-be / in-profile”} “fc-be / out-profile”} A counter is associated with each mapping. Note that the above is an example and is dependent on the type of classification (such as dscp-exp, dot1p, and so on).
  • Page 22: Channelized Any Service Any Port (Asap) Choc-3/Stm-1

    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 23: Channelized Ds-3/E-3 Asap Mda (12-Port)

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 2.1.8.6 Channelized DS-3/E-3 ASAP MDA (12-Port) The 12-port MDA provides 12 ports configurable as DS-3 or E-3. The MDA has twenty-four (24) 1.0/2.3 connectors and accepts up to twenty-four (24) DS-3/E-3 coax patch cables. Each physical DS-3 connection can support a full clear-channel DS-3, or it can be channelized into independent DS-1/E-1 data channels.
  • Page 24: 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 25 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 For QSFPs and CFPs, DDM Temperature and Supply voltage is available only at the Module level as shown in Table Refer to the Statistics Collection section for details about the QSFP and CFP sample DDM and DDM Lane information.
  • Page 26: Alarm Thresholds

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 Manufacture date : 2011/02/11 Media : Ethernet Serial Number : C22CQYR Part Number : FTLC1181RDNL-A5 Optical Compliance : 100GBASE-LR4 Link Length support: 10km for SMF =============================================================================== Transceiver Digital Diagnostic Monitoring (DDM) =============================================================================== Value High Alarm High Warn Low Warn Low Alarm...
  • Page 27 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 • Link/router fault isolation — With the information returned by the DDM-capable optics module, any optical problem affecting a port can be quickly identified or eliminated as the potential problem source. Supported real-time DDM features are summarized in Table Table 4 Real-Time DDM Information...
  • Page 28 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 Table 5 DDM Alarms and Warnings (Continued) Parameter SFP/XFP Units Required? MSA DWDM Supply Voltage µV - High Alarm - Low Alarm - High Warning - Low Warning TX Bias Current µA - High Alarm - Low Alarm - High Warning - Low Warning...
  • Page 29: Sfps And Xfps

    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 30: 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 31 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 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); this is to ensure that both SAP and network VLANs can be accommodated.
  • Page 32 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 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 33 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 • 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 34: Port Features

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 2.3.2 Port Features • Port State and Operational State • 802.1x Network Access Control • SONET/SDH Port Attributes − SONET/SDH Path Attributes • Multilink Frame Relay • FRF.12 End-to-End Fragmentation • FRF.12 UNI/NNI Link Fragmentation •...
  • Page 35: 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 36 RELEASE 15.0.R1 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 37 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 38 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 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 39 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 • 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 40: Sonet/Sdh Port Attributes

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 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 41: Sonet/Sdh Path Attributes

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 The CMA contains 3 LEDs for power, status and link state of port #1. The MDA contains LEDs for power, status and one for each link state. The power LED is blue if power is connected and off if no power is present. The status LED is green when operationally up, amber when operationally down, off when administratively shutdown and blinking green during initialization.
  • Page 42: Multilink Frame Relay

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 Table 7 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 STM1>AUG1>VC3>DS3 3 DS3 —...
  • Page 43 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 In order to provide priority based scheduling of the FR SAP fragments over the bundle links, the user configures a FR scheduling class for each FR SAP configured on the bundle. As in MC-MLPPP, four scheduling classes are supported. A separate fragmentation context is used by each FR SAP.
  • Page 44 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 • Detect loopbacks on the member link. This is always enabled on the 7750 SR. The near-end monitors the magic number Information Element (IE) sent by the far-end and if its value matches the one it transmitted in ten consecutive control messages, it sends a remove_link message to the far-end and brings the link down.
  • Page 45: Frf.12 End-To-End Fragmentation

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 T_HELLO Timer - this timer controls the rate at which hello messages are sent. Following a period of T_HELLO duration, a HELLO message is transmitted onto the Bundle Link. Note that T_HELLO Timer is also used, during the Bundle Link adding process, as an additional delay before re-sending an ADD_LINK message to the peer Bundle Link when this peer Bundle Link does not answer as expected.
  • Page 46: Frf.12 Uni/Nni Link Fragmentation

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 2.3.2.6.1 SAP Fragment Interleaving Option This option provides a different mode of operation for the fragmentation in the transmit direction of the FR SAP than in the default behavior of a FRF.12 end-to-end fragmentation. It allows for the interleaving of high-priority frames and fragments of low-priority frames.
  • Page 47: Mlfr/Frf.12 Support Of Aps, Bfd, And Mirroring Features

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 2.3.2.8 MLFR/FRF.12 Support of APS, BFD, and Mirroring Features The following APS support is provided: • Single-chassis APS is supported on a SONET/SDH port with FRF.12 UNI/NNI fragmentation enabled on the port or on a constituent TDM circuit. •...
  • Page 48 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 MP is negotiated during the initial LCP option negotiations of a standard PPP session. A router indicates to its peer that it is willing to perform MLPPP by sending the MP option as part of the initial LCP option negotiation. This negotiation indicates the following: 1.
  • Page 49 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 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. 2.3.2.9.1 Protocol Field (PID) The protocol field is two octets its value identifies the datagram encapsulated in the Information field of the packet.
  • Page 50 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 The MRRU will have the same default value as the MTU for PPP. The MRRU is always negotiated during LCP. 2.3.2.9.5 Padding On transmission, the Information field of the ending fragment may be padded with an arbitrary number of octets up to the MRRU.
  • Page 51 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 2.3.2.9.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. This feature helps avoid excessive delays to high priority, delay-sensitive traffic over a low-speed link. This can occur if this traffic type shares a link with lower priority traffic that utilizes much larger frames.
  • Page 52: Multi-Class Mlppp

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 On the ingress side, LFI requires that the ingress port can receive non-fragmented packets within the fragment stream and pass these packets directly on to the forwarding engine and then continue with the reassembly process for the fragmented frames.
  • Page 53 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 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. 2.3.2.10.1 QoS in MC-MLPPP If the user enables the multiclass option under an MLPPP bundle, the MDA egress data path provides a queue for each of the four classes of MLPPP.
  • Page 54 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 Table 11 Packet Forwarding Class to MLPPP Class Mapping (Continued) FC ID FC Name Scheduling Priority (Default) MLPPP Class (MLPPP Egress QoS profile 1, 2, and 3) Expedited Expedited Non-Expedited Non-Expedited Non-Expedited Non-Expedited The MLPPP class queue parameters and its scheduling parameters are also configured by applying one of the three pre-defined egress QoS profiles to an MLPPP bundle.
  • Page 55 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 Table 12 MLPPP Class Queue Threshold Parameters (Continued) Class 0 Class 1 Class 2 Class 3 4-Class Bundle 1000 Egress QoS Profile 3 Figure 7 MLPPP Class Queue Thresholds for In-Profile and Out-of-Profile Packets Service Egress SAP Queue MDA Class Queue Scheduler...
  • Page 56 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 Figure 8 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. If a member link goes down or a new member link is added to the bundle, the scheduling parameters MIR, W1, W2, W3, as well as the per class queue thresholds OOP and max are automatically adjusted to maintain the same values.
  • Page 57 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 Table 14 MLPPP Ingress QoS Profile: Reassembly Timers (msec) Class 0 Class 1 Class 2 Class 4 MLPPP ingress QoS default profile 25ms 25ms (2-Class bundle) MLPPP ingress QoS default profile 25ms 25ms 25ms (3-Class bundle) MLPPP ingress QoS default profile 25ms...
  • Page 58 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 4. The values of the ingress per-class re-assembly timer are configured in the ingress QoS profile. 5. The mapping of the system forwarding classes to the MLPPP Classes are configured in the egress QoS profile. There is a many-to-one relationship between the system FC and an MLPPP class.
  • Page 59: Cisco Hdlc

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 2.3.2.11 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 60 PPP. 2.3.2.11.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 61: Automatic Protection Switching (Aps)

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 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 62 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 Figure 9 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 63 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 • 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.12.1 Single Chassis and Multi-Chassis APS APS can operate in a single chassis configuration (SC-APS) or in a multi-chassis...
  • Page 64 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 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 65 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 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 66 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 2.3.2.12.2 APS Switching Modes APS behavior and operation differs based on the switching mode configured for the APS group as shown in Table 18. 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 67 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 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 68 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 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 69 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 − 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 70 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 2.3.2.12.3 APS Channel and SONET Header K Bytes The APS channel (bytes K1 and K2 in the SONET header) is used to exchange 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 71 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 Table 20 shows bits 5 to 8 of a K1 byte and K2 Bits 1 to 4 and the channel number code assignments. Table 20 K1 Byte, Bits 5 to 8 (and K2 Bits 1 to 4), Channel Number Code Assignments Channel Number Channel and Notes Code...
  • Page 72 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 Table 21 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 73 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 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 74 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 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 75 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 Table 23 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 76 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 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 77 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 Figure 12 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 12 APS Working and Protection Circuit Example Flexible FastPath...
  • Page 78 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 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 79 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 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 80 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 Table 24 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.12.10 APS Applicability, Restrictions and Interactions Note: The Release Notes for the relevant the SR OS release should be consulted for details about APS restrictions.
  • Page 81 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 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 82 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 Table 26 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 83 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 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 84 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 Figure 13 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 85 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 Figure 14 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 86 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 Figure 15 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 87 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 Figure 16 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 88 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 Figure 17 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 89 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 Figure 18 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 90: Inverse Multiplexing Over Atm (Ima)

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 • 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 91 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 92 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 • 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 93: 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 94: Link Layer Discovery Protocol (Lldp)

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 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 95 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 Figure 20 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 96 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 Figure 21 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 97 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 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 98: Per Port Aggregate Egress Queue Statistics Monitoring

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 The implementation defaults to setting the port-id field in the LLDP OAMPDU to tx- local. This encodes the port-id field as ifIndex (sub-type 7) of the associated port. This is required to support some releases of SAM. SAM may use the ifIndex value to properly build the Layer Two Topology Network Map.
  • Page 99 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 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 100: Port Cross-Connect (Pxc)

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 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 101: Pxc Terminology

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 Figure 22 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 102: Pxc - Physical Port In Cross-Connect (Loopback) Mode

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

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 • 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 104: Pxc Sub-Ports

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 2.4.3 PXC Sub-Ports To explain the need for PXC sub-ports under an internally cross-connected physical port, an analogy with two distinct physical ports that are connected via external cable is shown in Figure Figure 24 Two Cross-Connected Ports vs Single Cross-Connected Port 10Gbps Full Duplex External Cross-Connect Physical Port 1/1/1...
  • Page 105 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 Once the physical port is associated with a PXC ID, a pair of mated PXC sub-ports is automatically created by the system: configure port pxc-<pxc-id>.a shutdown 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.
  • Page 106: Pxc Sub-Port Operational State

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 2.4.3.1 PXC Sub-Port Operational State At creation time, the administrative state of the PXC sub-ports is set to shutdown. The operational state of the PXC sub-ports is dependent on the operational state of the underlying physical port and the state of the corresponding PXC ID. 2.4.4 Port Statistics There are two types of statistics that can be collected on a regular (non PXC) Ethernet port:...
  • Page 107: Statistics On Physical Pxc Ports

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 2.4.4.1 Statistics on Physical PXC Ports The statistics on physical PXC ports are maintained only on MAC level. The internal q-tag used for PXC sub-port identification within the router is included in the displayed octet count. The port-level statistics on a physical PXC port represent the combined upstream and downstream traffic carried by the corresponding PXC sub- ports.
  • Page 108: Lag With Pxc Ports - Pxc Lag

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 2.4.5 LAG with PXC Ports – PXC LAG PXC sub-ports can be aggregated to form a PXC LAG for increased capacity and anchor point redundancy. A logical concept of a PXC LAG is shown in Figure Figure 25 Logical Concept of a LAG on PXC Ports...
  • Page 109: Basic Pxc Provisioning

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 2.4.6 Basic PXC Provisioning The CLI flow is shown in Figure 26. The oval marked ‘Operator’ represents a configuration step that must be performed by the operator. The block marked ‘Dynamic’ represents a step that is performed automatically by the system without an operator’s assistance.
  • Page 110: Qos

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 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 111: Pool Allocations On Pxc Ports

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 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 112: Mirroring And Li On Pxc Ports

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 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 113 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 • 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 114: Configuration Example

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 2.4.11 Configuration Example In the following example, subscriber (ESM) traffic with QinQ encapsulation arriving on two different I/O line cards (3 and 4) is terminated on the PXC LAG on line cards 1 and 2. With this method, if one of the I/O line cards fails, the subscriber traffic remains unaffected (continues to be terminated on line cards 1 and 2) provided that the proper protection mechanism is implemented in the access part of the network.
  • Page 115 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 configured here” encap-type qinq no shutdown port pxc-1.b description "transition PXC side; all VLAN tags (*) will be transparently passed via this side” encap-type dot1q no shutdown port pxc-2.a description "together with pxc-1.a, this sub-port is a member of LAG 1”...
  • Page 116: Forwarding Path Extensions (Fpe)

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 sap lag-1:11.* capture-sap create description "termination side of PXC; traffic with S-tag=11 will be extracted here”. 2.5 Forwarding Path Extensions (FPE) Certain applications in the SR OS require extra traffic processing in the forwarding plane.
  • Page 117 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 • Application-specific configuration is performed in step 6, partially by the operator and partially by the system. This is described in the application- specific user guides. Figure 27 FPE - Sample Provisioning Steps Operator (manually) configured System (dynamically) configured configure port-xc...
  • Page 118: 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 119: Lacp Multiplexing

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 When LACP is enabled, an operator can see LACP changes through traps/log messages logged against the LAG. See the TIMETRA-LAG-MIB.mib for more details. 2.6.1.1 LACP Multiplexing The router supports two modes of multiplexing RX/TX control for LACP: coupled and independent.
  • Page 120: Active-Standby Lag Operation

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 • If the port encapsulation is null, a null SAP can be configured on a port to tunnel these packets. • If the port encapsulation is dot1q, either a dot1q explicit null SAP (for example, 1/1/10:0) or a dot1q default SAP (for example, 1/1/11:*) can be used to tunnel these packets.
  • Page 121 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 Figure 28 Active-Standby LAG Operation without Deployment Examples In case of a link failure, as shown in Figure 29 Figure 30, the switch over behavior ensures that all lag-members connected to the same IOM as failing link will become stand-by and lag-members connected to other IOM will become active.
  • Page 122: Lag On Access Qos Consideration

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 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 access side with access/hybrid ports. Similarly to LAG on network side, LAG on access is used to aggregate Ethernet ports into all active or active/standby LAG.
  • Page 123 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 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 124: Per-Fp-Ing-Queuing

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 Table 27 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 125: Per-Fp-Sap-Instance

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 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 126: Lag And Ecmp Hashing

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 • 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 127: Per Flow Hashing

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 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 128 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 − 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 129 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 Note that 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 130 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 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 131 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 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 132 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 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 133 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 134: Per Link Hashing

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 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 135 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 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 Mbps, Extreme Broadband – 300 Mbps and above types of service.
  • Page 136: Explicit Per Link Hash Using Lag Link Mapping Profiles

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 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 137: Consistent Per Service Hashing

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 • 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 138 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 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 139: Esm - Lag Hashing Per Vport

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 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 140 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 141 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 This feature can be enabled using the CLI command config>subscriber- mgmt>sub-profile>vport-hashing. On the HSMDA, the secondary shaper is used to support 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 rests of the subscribers (per inter-dest-string hashing).
  • Page 142: Lag Hold Down Timers

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 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 143: Bfd Over Lag Links

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 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 144: Mixed Port-Speed Lag Support

    RELEASE 15.0.R1 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 145 • 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 • not supported with weighted per-link-hash...
  • Page 146: Lag Upgrade

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 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 147: Overview

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 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 148 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 − 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 149 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 Figure 32 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 AAAA TQZZA 01...
  • Page 150 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 Figure 33 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 151: Mc-Lag And Subscriber Routed Redundancy Protocol (Srrp)

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 • Packets received from the MC-LAG sap will be forwarded to active destination pseudo-wire or active local links of destination-sap. In case there are no such objects available at the local node, the packets will be cross-connected to inter- chassis pseudowire.
  • Page 152 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 Figure 34 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 153: Dslam Dual Homing In Layer 2/3 Tpsda Model

    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, and 7950 XRS Services Overview Guide.
  • Page 154: Protected Ethernet Rings

    APS). For further information regarding Ethernet rings, Refer to G.8032 Protected Ethernet Rings in the 7450 ESS, 7750 SR, and 7950 XRS Services Overview Guide. 2.9 Ethernet Port Monitoring Ethernet ports can record and recognize various medium statistics and errors. There are two main types of errors: •...
  • Page 155 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 The configured error thresholds are compared to the operator specified sliding window to determine if one or both of the thresholds have been crossed. Statistics are gathered every second. This means that every second the oldest statistics are dropped from the calculation.
  • Page 156 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 Tx DUS/DNU : Disabled Tx Quality Level : N/A SSM Code Type : sdh Down On Int. Error : Disabled CRC Mon SD Thresh : Disabled CRC Mon Window : 10 seconds CRC Mon SF Thresh : Disabled Sym Mon SD Thresh : 5*10E-5...
  • Page 157: Ah Oam

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 The above configuration results in an SD threshold of 5*10E-5 (0.00005) and an SF threshold of 5*10E-3 (0.005) over the default 10 second window. If this port is a 1GbE port supporting symbol monitoring then the error rate is compared against 1,250,000,000 symbols (10 seconds worth of symbols on a 1GbE port 125,000,000).
  • Page 158 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 • Loopback — A mechanism is provided to support a data link layer frame-level loopback mode. Both remote and local loopback modes are supported • efm-oam PDU tunneling • High resolution timer for efm-oam in 100ms interval (minimum) •...
  • Page 159 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 =============================================================================== Description : 10/100/Gig Ethernet SFP Interface : 1/1/3 Oper Speed : N/A Link-level : Ethernet Config Speed : 1 Gbps Admin State : up Oper Duplex : N/A Oper State : down Config Duplex : full Reason Down : efmOamDown...
  • Page 160: Oam Events

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 or clear conditions. Adding and removing this optional ignore command will immediately represent the Port State and Oper State based on the active configuration. For example, if the ignore-efm-state is configured on a port that is exhibiting a protocol error that protocol error does not affect the port state or operational state and there is no Reason Down code.
  • Page 161 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 Link monitoring can be enabled for three types of frame errors; errored-frame, errored-frame-period and errored-frame-seconds. The errored-frame monitor is the number of frame errors compared to the threshold over a window of time. The errored-frame-period monitor is the number of frame errors compared to the threshold over a window of number of received packets.
  • Page 162 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 As discussed earlier, the Information OAMPDU conveys link information using the Flags field; dying gasp, critical link and link fault. This method of communication has a number of significant advantages over the Event Notification OAMPDU. The Information OAMPDU is sent at every configured transmit-interval.
  • Page 163 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 recovery actions will cause the generation of the Event Notification OAMPDU. If the chosen recovery action is not otherwise recognized by the peer and the Information OAMPDU Flag fields have not been configured to maintain the current event state, there is a high probability that the ports will have different forwarding states, notwithstanding any higher level protocol verification that may be in place.
  • Page 164 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 The errored-symbol window is a measure of time that is automatically converted into the number of symbols for that specific medium for that period of time. The standard MIB entries “dot3OamErrSymPeriodWindowHi” and “dot3OamErrSymPeriodWindowLo” are marked as read-only instead of read-write. There is now way to directly configure these values.
  • Page 165 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 SD Threshold : disabled (0) SD Threshold : disabled (0) Window : 10 ds Window : 1488095 frames Errored Symbol Period Errored Frame Seconds Summary Enabled : no Enabled : no Event Notify : enabled Event Notify : enabled SF Threshold...
  • Page 166 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 If the clear command is used to clear remote events, events conveyed to the local node by the peer, no notification is generated to the peer to indicate a clear function has been performed. Since the Event Notification OAMPDU is only sent when the initial event was raised, there is no further Event Notification and blackholes can result.
  • Page 167: Remote Loopback

    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 168: Ah Grace Announcement

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 When OAM PDU tunneling is enabled, 802.3ah OAM PDUs received at one end of an Epipe are forwarded through the Epipe. 802.3ah can run between devices that are located at each end of the Epipe. When OAM PDU tunneling is disabled (by default), OAM PDUs are dropped or processed locally according to the efm-oam configuration (shutdown or no shutdown).
  • Page 169 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 will not allow those ports to generate the vendor specific Grace TLV. This functionality must be enabled at both the system and port level prior to the ISSU or soft reset function. If this is enabled during a soft reset or after the ISSU function is already in progress it will have no affect during that window.
  • Page 170 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 Figure 37 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 171 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 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 172 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 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 173: Mtu Configuration Guidelines

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 Peer Grace Rx • False — Not receiving Grace TLV from the peer • True — Receiving Grace TLV from the peer 2.11 MTU Configuration Guidelines Observe the following general rules when planning your service and physical MTU configurations: •...
  • Page 174: Modifying Mtu Defaults

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 Table 28 MTU Default Values (Continued) Port Type Mode Encap Type Default (bytes) SONET path or TDM channel access IPCP 1502 SONET path or TDM channel network — 9208 SONET path or TDM channel access frame-relay 1578...
  • Page 175: Configuration Example

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 2.11.3 Configuration Example In order for the maximum length service frame to successfully travel from a local ingress SAP to a remote egress SAP, the MTU values configured on the local ingress SAP, the SDP (GRE or MPLS), and the egress SAP must be coordinated to accept the maximum frame size the service can forward.
  • Page 176: Deploying Preprovisioned Components

    The fabric_speed_a parameter enables the 7450 ESS-7/12 and the 7750 SR-7/12/ 12e to permit FP2/FP3 based cards to co-exist. The fabric_speed_a parameter operates a 100 Gbytes per slot on the 7450 ESS-7/12 and 7750 SR-7/12 and 200 Gbytes per slot on the 7750 SR-12e.
  • Page 177: Versatile Service Module

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 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 Gbps) is available, allowing single conversations up to 25 Gbps on a single MDA.
  • Page 178 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 =============================================================================== *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 179: Configuration Process Overview

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 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 2.15 Configuration Process Overview Figure 39 displays the process to provision chassis slots, cards, MDAs, and ports. Figure 39 Slot, Card, MDA, and Port Configuration and Implementation Flow...
  • Page 180: Configuration Notes

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 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 remain administratively and operationally down until the card type and MDA is specified.
  • Page 181: Configuring Physical Ports With Cli

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 2.17 Configuring Physical Ports with CLI This section provides information to configure cards, MDAs, and ports. Topics in this section include: • Preprovisioning Guidelines − Predefining Entities − Preprovisioning a Port − Maximizing Bandwidth Use •...
  • Page 182: Preprovisioning Guidelines

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 − Modifying or Deleting an MDA, MCM, CMA or XMA − Modifying a Card Type − Deleting a Card − Deleting Port Parameters 2.18 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 183: Maximizing Bandwidth Use

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 • Ethernet − 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 184: Basic Configuration

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 2.19 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 185 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 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 186: 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 187: Configuring Mda Access And Network Pool Parameters

    (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 188: Configuring Mda Policies For Named Pools Mode

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 ---------------------------------------------- mda-type cx20-10g-sfp network egress pool slope-policy "B" exit exit exit access ingress pool resv-cbs 50 slope-policy "A" exit exit exit ---------------------------------------------- A:ALA-B>config>card>mda# 2.21.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.
  • Page 189: Configuring Cards And Cmas

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 Output for Media Dependent Adapters (MDAs) show an “m” in the mda-type description, for example, m60-eth10/100-tx. Use the config > info command to display card configuration information: A:PE-1>config>card# info ---------------------------------------------- card-type iom4-e mda 1 mda-type me10-10gb-sfp+ no shutdown exit...
  • Page 190: Configuring Ports

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 2.23 Configuring Ports This section provides the CLI syntax and examples to configure the following: • Configuring Port Pool Parameters • Changing Hybrid-Buffer-Allocation • Configuring APS Parameters • Configuring Ethernet Port Parameters • Configuring SONET/SDH Port Parameters •...
  • Page 191 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 After the active bandwidth is calculated for the port, the result may be modified through the use of the ‘ing-percentage-of-rate’ and ‘egr-percent-of-rate’ commands. The default value of each is 100% which allows the system to use all of the ports active bandwidth when deciding the relative amount of buffer space to allocate to the port.
  • Page 192: Changing Hybrid-Buffer-Allocation

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 • Pools can be default, MDA common pools, or port specific pools The following example shows port pool configurations: A:ALA-B>config>port# info ---------------------------------------------- access egress pool slope-policy "slopePolicy1" exit exit exit network egress pool slope-policy "slopePolicy2" exit exit exit...
  • Page 193: Configuring Aps Parameters

    Interfaces RELEASE 15.0.R1 2.23.3 Configuring 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 194 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 protect-circuit 1/1/2 exit sonet-sdh path exit no-shutdown exit exit no-shutdown exit ---------------------------------------------- A:ALA-274>config>service# apipe 100 ---------------------------------------------- sap aps-1:0/100 create exit spoke-sdp 1:100 create exit no-shutdown ---------------------------------------------- The following shows an example of the configuration for the working circuit/node of an MC-APS group: A:ALA-274>config>port (2/1/1)# info ----------------------------------------------...
  • Page 195: Configuring Ethernet Port Parameters

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 2.23.4 Configuring Ethernet Port Parameters 2.23.4.1 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 ---------------------------------------------- description "Ethernet network port"...
  • Page 196: Configuring 802.1X Authentication Port Parameters

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 exit no shutdown ---------------------------------------------- A:ALA-A>config>port# 2.23.4.3 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 max-auth-req 2 transmit-period 30 quiet-period 60 supplicant-timeout 30 server-timeout 30...
  • Page 197: Sonet/Sdh Network Port

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 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. The following CLI output shows an example of a SONET/SDH configuration for a WAN PHY Ethernet port.
  • Page 198: Configuring Channelized Ports

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 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 ---------------------------------------------- A:ALA-A>config>port# 2.23.6 Configuring Channelized Ports • Configuring a Channelized DS3 Port • Configuring a Channelized OC-12-SFP Port •...
  • Page 199 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 Table 30 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 200 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 Table 30 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 201 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 Table 30 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 202 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 Table 31 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 203: Verify The Mda Type

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 2.23.6.1 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 204 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 Figure 40 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 205 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, and 7950 XRS Services Overview Guide for information about how to configure services.
  • Page 206: Configuring A Channelized Oc-12-Sfp Port

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 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 207 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 Figure 41 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 208 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 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 209 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, and 7950 XRS Services Overview Guide for information about how to configure services.
  • Page 210: Configuring A Channelized Any Service Any Port (Asap) Oc3-Sfp Port

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 ---------------------------------------------- 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# 2.23.6.4 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 211 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 A:ALA-A>config>port>tdm>ds3# shutdown A:ALA-A>config>port>tdm>ds3# channelized e1 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 212: Configuring Cisco Hdlc On A Channelized Port

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 no shutdown exit 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...
  • Page 213 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 keepalive time-interval up-count up-count 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-...
  • Page 214: Configuring Channelized Stm1/Oc3 Parameters

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 2.23.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 215: Sample Cpipe Port Configurations

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 group tug3-1 payload vt2 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...
  • Page 216: Configuring Atm Saps

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 Last State Change : 10/31/2006 14:23:12 Channel IfIndex : 580943939 Loopback : none Invert Data : false Remote Loop respond: false In Remote Loop : false Load-balance-algo : default Egr. Sched. Pol : n/a BERT Duration : N/A BERT Pattern...
  • Page 217: Atm Sap In An Epipe Service

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 address 2.4.5.1/24 sap 2/1/1:18/300 create exit exit no shutdown ---------------------------------------------- B:ALA-701>config>service>ies# 2.23.8.2 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...
  • Page 218: Configuring Wavetracker Parameters

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 ---------------------------------------------- *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 ---------------------------------------------- 2.23.10 Configuring WaveTracker Parameters The following example shows the default configuration with WaveTracker disabled:...
  • Page 219 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 encode key1 205 key2 749 exit ---------------------------------------------- *A:ALA-A>config>port>dwdm># info detail ---------------------------------------------- channel 44 wavetracker 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 exit rxdtv-adjust ---------------------------------------------- *A:ALA-A>config>port>dwdm># wavetracker *A:ALA-A>config>port>dwdm>wavetracker># info ---------------------------------------------- power-control...
  • Page 220 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 Key1 Key1 Key2 Key2 Channel ------- ---- ---- ---- ---- 1548 1548 2032 2032 1001 1004 1018 1021 1035 1038 1052 1055 1069 1072 1086 1089 1103 1573 1587 1106 1120 1590 1604 1123 1137 1607 1621...
  • Page 221: Configuring Otu Port Parameters

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 1480 1494 1964 1978 1497 1511 1981 1995 1514 1528 1998 2012 1531 1545 2015 2029 1548 1562 2032 2046 3585 3599 2049 2063 3602 3616 2066 2080 3619 3633 2083 2097 3636 3650 2100 2114 3653...
  • Page 222 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 tx auto-generated expected auto-generated no mismatch-reaction exit psi-tti tx auto-generated expected auto-generated no mismatch-reaction exit psi-payload tx auto expected auto no mismatch-reaction 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 ===============================================================================...
  • Page 223 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 FEC Corrected 0s FEC Corrected 1s FEC Unrrectable Sub-rows FEC ES FEC SES FEC UAS Pre-FEC BER 0.000E+00 Post-FEC BER 0.000E+00 ------------------------------------------------------------------------------- SM BIP8 SM ES SM SES SM UAS SM-BIP8-BER 0.000E+00 ------------------------------------------------------------------------------- PM BIP8 PM ES PM SES PM UAS...
  • Page 224: Configuring Atm Interface Parameters

    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: • Cell-format — Allows user to select the ATM cell format to be used on a given interface: UNI/NNI •...
  • Page 225 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 Table 33 Alarm State Interactions Content of the Received Signal Status Field Values Local Local Local Local Far End Far End Path Path PLCP Signal Frame Payld PLCP Framing PLCP Sonet Oper Interface Alarm Framing Framing Alarm...
  • Page 226: Atm Interface Configurations

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 • Samples and uses for performance monitoring received FEBE bits of G1 octet and transmits the number of BIP-8 errors detected by the receive framer using the FEBE bits of the G1 octet.Detects a PLCP Far End Alarm when 10 consecutive PLCP frames are received with the RAI bit set, and transmits a set RAI bit when the local port has declared PLCP-LOF.
  • Page 227: Configuring Frame Relay Parameters

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 Use the following CLI syntax to configure ATM interface parameters for TDM channels: CLI Syntax: config# port {port-id} ds1 [ds1-id] channel-group 1 cell-format cell-format min-vp-vpi value ds3 [sonet-sdh-index] cell-format cell-format min-vp-vpi value mapping {direct | plcp} e1 [e1-id] channel-group 1 cell-format cell-format...
  • Page 228: Sonet/Sdh Interfaces

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 no mdl-transmit no loopback report-alarm ais los no report-alarm oof rai looped no shutdown exit ds1 ds1-1 shutdown framing esf no loopback report-alarm ais los no report-alarm oof rai looped channel-group 1 description "DS3/E3" mode access encap-type frame-relay no mtu...
  • Page 229 "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 230: Configuring Multilink Ppp Bundles

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 2.23.14 Configuring Multilink PPP Bundles Multilink bundles can have from 1 to 8 members (ports) specified. The bundles aggregate channelized ports which define available bandwidth to carry data over a DS1 channel. 56 multilink bundles can be configured per MDA. 256 MLPPP groups are supported per ASAP MDA.
  • Page 231 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 CLI Syntax: configure# port bundle-type-slot/mda.bundle-num description description-string multilink-bundle fragment-threshold value cell-format {uni|nni} min-vp-vpi vp-vpi-value exit link-delay {activate |deactivate} milli- seconds max-bandwidth number-links version ima-version red-differential-delay red-diff-delay down member port-id 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 232 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 After the primary member has been added each additional member added to the group will only be accepted if it matches the configuration of the IMA group. ATM interface characteristics are not part of this verification as they are overwritten/reset to defaults when a link is added to/removed from an IMA bundle.
  • Page 233: Multi-Class Mlppp

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 • The 7750 SR supports automatic IMA version changing when the far end IMA group version matches the configured version. The group will remain operationally down until one of the IMA groups changes version. •...
  • Page 234: Ima Test Procedure

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 2.23.16.1 IMA Test Procedure Use the following CLI commands to perform an IMA Test Pattern Procedure on a member link of an IMA group: CLI Syntax: configure# port bundle-type-slot/mda.bundle-num multilink-bundle test-pattern-procedure test-link port-id test-pattern [pattern] no shutdown An operator can deploy IMA test procedures to verify operations of IMA group and its member links.
  • Page 235: Configuring Bundle Protection Group Ports

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 2.23.17 Configuring Bundle Protection Group Ports Bundle Protection groups enable APS protection of one bundle residing on a working circuit of an APS group port by another bundle residing on the protection circuit of that APS group port.
  • Page 236 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 config>port>tdm>ds1>channel-group# encap-type atm config>port>tdm>ds1>channel-group# no shutdown config>port>tdm>ds1>channel-group# exit config>port>tdm# ds1 1.8 config>port>tdm>ds1# channel-group 1 config>port>tdm>ds1>channel-group# encap-type atm config>port>tdm>ds1>channel-group# no shutdown config>port>tdm>ds1>channel-group# exit Next, configure an IMA-type/MLPPP-type BPGrp with working and protection bundles on working and protection circuits of aps-1 and members the created DS1s (this creates 2 IMA bundles, one on working and one on protection circuit): Example: config# port bpgrp-ima-1...
  • Page 237: Configuring A Channelized Ds1 Card

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 − The BPGrp link activation timer should be configured to a value small enough to allow a quick recovery from any IMA failure occurring during the switchover. A recommended value is 1 second. − The ADM that terminates APS should support standard APS switchover time requirements.
  • Page 238 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 c4-ds3 c4-ds3 =============================================================================== A:7710-3> A:7710-3>config# show mda 1/7 detail =============================================================================== MDA 1/7 detail =============================================================================== Slot Provisioned Equipped Admin Operational Mda-type Mda-type State State ------------------------------------------------------------------------------- c8-chds1 c8-chds1 MDA Specific Data Maximum port count Number of ports equipped Network ingress queue policy : default Capabilities...
  • Page 239 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 ALA-A>config>port>tdm>e1>channel-group# timeslots 11,12 ALA-A>config>port>tdm>e1>channel-group# encap-type cisco-hdlc ALA-A>config>port>tdm>e1>channel-group# no shutdown ALA-A>config>port>tdm>e1>channel-group# exit ALA-A>config>port>tdm>e1# no shutdown ALA-A>config>port>tdm>e1# exit ALA-A>config>port>tdm# e1 1.2 ALA-A>config>port>tdm>e1# no shutdown ALA-A>config>port>tdm>e1# channel-group 1 ALA-A>config>port>tdm>e1>channel-group# encap-type atm ALA-A>config>port>tdm>e1>channel-group# no shutdown ALA-A>config>port>tdm>e1>channel-group# exit ALA-A>config>port>tdm>e1# no shutdown ALA-A>config>port>tdm# info ---------------------------------------------- ds3 1...
  • Page 240: Configuring Lag Parameters

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 2.23.18 Configuring LAG Parameters LAG configurations should include at least two ports. Other considerations include: • A maximum of 64 ports (depending on the lag-id) can be included in a LAG. All ports in the LAG must share the port characteristics inherited from the primary port.
  • Page 241: Configuring G.8031 Protected Ethernet Tunnels

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 When configuring the local and remote IP address for the BFD over LAG link sessions, the local-ip parameter should always match an IP address associated with the IP interface to which this LAG is bound. In addition, the remote-ip parameter should match an IP address on the remote system and should also be in the same subnet as the local-ip address.
  • Page 242 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 • If the operator wants to replace an existing member port or a control-tag, the whole path needs to be shutdown first. The alternate path will be activated as a result keeping the traffic interruption to a minimum. Then the whole path must be deleted and re-created.
  • Page 243: Service Management Tasks

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 path 1 member 1/1/1 control-tag 100 precedence primary eth-cfm mep 51 domain 1 association 1 ccm-enable low-priority-defect allDef mac-address 00:AE:AE:AE:AE:AE control-mep no shutdown no shutdown path 2 member 2/2/2 control-tag 200 eth-cfm mep 52 domain 1 association 2 direction down ccm-enable low-priority-defect allDef mac-address 00:BE:BE:BE:BE:BE...
  • Page 244: Modifying A Card Type

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 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> port port-id shutdown CLI Syntax: config> card slot-number...
  • Page 245: Deleting A Card

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 [no] mcm mcm-number no mcm-type mcm-type shutdown 2.24.3 Deleting a Card To delete a card type provisioned for a specific slot, you must shutdown existing port configurations and shutdown and remove all MDA, XMA, or CMA configurations. For 7750 SR-c12/c4 systems, after removing MDA configurations, you can shutdown and remove the MCM from service before modifying the card.
  • Page 246: Soft Reset

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 2.24.5.1 Soft Reset Soft reset is an advanced high availability feature that greatly reduces the impact of IOM/IMM resets either during a software upgrade or during other maintenance or debug operations. The combination of In Service Software Upgrade (ISSU) and Soft reset maximizes service availability in an operational network.
  • Page 247: Deferred Mda Reset

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 The show card and show mda commands indicate that a soft IOM reset is occurring during the soft reset process. Soft Reset is not supported on the 7750 SR-c4. On the 7750 SR-c12, Soft Reset is not supported but the ISSU procedure will avoid resetting soft reset capable MDAs/ CMAs (as long as there is not new firmware for the CMA/MDA in the new image).
  • Page 248 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 3HE 11968 AAAA TQZZA 01 Issue: 01...
  • Page 249: Configuration Command Reference

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 2.25 Configuration Command Reference 2.25.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 250: Card Commands

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 2.25.1.1 Card Commands config — [no] card slot-number — card-type card-type — no card-type — [no] fail-on-error — [no] named-pool-mode [now] — [no] reset-on-recoverable-error 2.25.1.2 MCM Commands config — [no] card slot-number — [no] mcm-slot —...
  • Page 251 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 — slope-policy name — no slope-policy — clock-mode adaptive — clock-mode differential [timestamp-freq {19440 | 77760 | 103680}] — egress — egress-xpl — threshold threshold — window window — [no] fail-on-error — ingress-xpl — threshold threshold —...
  • Page 252: Power Commands

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 2.25.1.4 Power Commands config — system — power-management — mode [none | basic | advanced] — [no] peq-slot [chassis chassis-id] — [no] peq-type peq-type — input-power-mode amperage — [no] shutdown — power-safety-alert wattage — power-safety-level percent 2.25.1.5...
  • Page 253 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 — access — queue-group queue-group-name instance instance-id [create] — 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} —...
  • Page 254: Port Configuration Commands

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 — [no] policer-override — policer policer-id [create] — no policer policer-id — {size [bytes | kilobytes] | default} — no — {size [bytes | kilobytes] | default} — no — packet-byte-offset{add bytes | subtract bytes} —...
  • Page 255 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 — dwdm — amplifier — [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} —...
  • Page 256 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 — red-alarm-threshold percentage — no red-alarm-threshold — 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} —...
  • Page 257: Port Xc Commands

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 — sf-threshold-clear threshold [coefficient coefficient] — sm-tti — expected auto-generated — expected bytes byte-string [byte-string... (up to 64 byte-strings max, 64 bytes max)] — expected string identifier — expected use-rx — mismatch-reaction {squelch-rx} — no mismatch-reaction —...
  • Page 258: Port Aps Commands

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 2.25.1.10 Port APS Commands config — [no] port {aps-id} — — 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 —...
  • Page 259 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 — no re-auth-period — [no] re-authentication — server-timeout seconds — no server-timeout — supplicant-timeout seconds — no supplicant-timeout — transmit-period seconds — no transmit-period — tunneling — no tunneling — down-on-internal-error [tx-disable] — no down-on-internal-error —...
  • Page 260 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 — window deciseconds — errored-symbols — [no] event-notification — sd-threshold errored-symbols — no sd-threshold — sf-threshold errored-symbols — [no] shutdown — window deciseconds — local-sf-action — event-notification-burst packets — info-notification — [no] critical-event — [no] dying-gasp —...
  • Page 261 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 — no n393 — t391 [5 to 30] — no t391 — t392 [5 to 30] — no t392 — encap-type {dot1q | null | qinq} — no encap-type — eth-cfm — [no] mep-id domain md-index association ma-index [vlan vlan-id] —...
  • Page 262 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 — one-way-delay-threshold seconds — [no] shutdown — hold-time {[up hold-time up] [down hold-time down] [seconds | centiseconds]} — no hold-time — hsmda-scheduler-overrides [create] — [no] hsmda-scheduler-overrides — group group-id rate rate — no group group-id —...
  • Page 263 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 — symbol-monitor — sd-threshold threshold [multiplier multiplier] — no sd-threshold — sf-threshold threshold [multiplier multiplier] — no sf-threshold — [no] shutdown — window-size seconds — no window-size — util-stats-interval seconds — xgig {lan | wan} config —...
  • Page 264 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 — {size [bytes | kilobytes] | default} — no — monitor-depth — [no] monitor-depth — parent [weight weight] [cir-weight cir-weight] — no parent — rate pir-rate [cir cir-rate] — no rate — scheduler-policy scheduler-policy-name —...
  • Page 265: Interface Group Handler Commands

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 — no accounting-policy — [no] collect-stats — egress — [no] queue-group queue-group-name [instance instance id] [create] — accounting-policy acct-policy-id — no accounting-policy — agg-rate — no agg-rate — [no] limit-unused-bandwidth — [no] queue-frame-based-accounting — rate kilobits-per-second —...
  • Page 266: Multilink Bundle Commands

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 2.25.1.13 Multilink Bundle Commands config — [no] port {bundle-id} — multilink-bundle — fragment-threshold fragment-threshold — fragment-threshold unlimited — no fragment-threshold — — — cell-format cell-format — min-vp-vpi value — link-delay {activate | deactivate} milli-seconds —...
  • Page 267: Sonet-Sdh Commands

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 — identifier frf16-identifier — no identifier — ingress — qos-profile profile-id — no qos-profile — retry-limit count — no retry-limit — mlppp — egress — qos-profile profile-id — no qos-profile — endpoint-discriminator class {ip-address | global-mac-address |null} [discriminator-id discriminator-id] —...
  • Page 268 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 — rate kilobits-per-second — no rate — description description-string — no description — [no] egress-rate-modify — host-match dest description-string [create] — no host-match destination-string — [no] mon-port-sch — port-scheduler-policy port-scheduler-policy- name — no port-scheduler-policy —...
  • Page 269 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 — frame-relay — [no] frf-12 — egress — qos-profile profile-id — no qos-profile — fragment-threshold threshold — no fragment-threshold — lmi-type {ansi | itu | none | rev1} — mode {dce | dte | bidir} —...
  • Page 270: Tdm Commands

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 — threshold {ber-sd | ber-sf} rate threshold-rate — no threshold {ber-sd | ber-sf} — [no] tx-dus 2.25.1.15 TDM Commands config — [no] port {port-id} — — buildout {long | short} — [no] ds1-id — bert {2e3 | 2e9 | 2e11 | 2e15 | 2e20 | 2e20q | 2e23 | ones | zeros | alternating} duration duration...
  • Page 271 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 — mode {dce | dte | bidir} — n391dte intervals — no n391dte — n392dce threshold — no n392dce — n392dte threshold — no n392dte — n393dce count — no n393dce — n393dte count —...
  • Page 272: Ds3 Commands

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 — [no] remote-loop-respond — [no] report-alarm [ais] [los] [oof] [rai] [looped] [ber-sd] [ber-sf] — [no] shutdown — signal-mode {cas} — no signal-mode — threshold {ber-sd | ber-sf} rate {1 | 5 | 10 | 50 | 100} —...
  • Page 273 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 — encap-type {atm | bcp-null | bcp-dot1q | ipcp | ppp-auto | frame-relay | wan-mirror | cisco-hdlc | cem} — [no] feac-loop-respond — frame-relay — [no] frf-12 — egress — qos-profile profile-id — no qos-profile —...
  • Page 274: E1 Commands

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 — no subrate 2.25.1.17 E1 Commands config — [no] port {port-id} — — [no] [e1-id] — bert {2e3 | 2e9 | 2e11 | 2e15 | 2e20 | 2e20q | 2e23 | ones | zeros | alternating} duration duration —...
  • Page 275 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 — 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 276: E3 Commands

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 — no signal-mode {cas} — threshold {ber-sd | ber-sf} rate {1 | 5 | 10 | 50 | 100} — no threshold {ber-sd | ber-sf} 2.25.1.18 E3 Commands config — [no] port {port-id} — —...
  • Page 277: Lag Commands

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 — mode {dce | dte | bidir} — n391dte intervals — no n391dte — n392dce threshold — no n392dce — n392dte threshold — no n392dte — n393dce count — no n393dce — n393dte count —...
  • Page 278 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 — [no] per-fp-ing-queuing — [no] per-fp-sap-instance — — [no] disable-soft-reset-extension — family {ipv4 | ipv6} — [no] bfd-on-distributing-only — local-ip-address ip-address — no local-ip-address — max-admin-down-time [[-1 to 3600] | infinite] — no max-admin-down-time —...
  • Page 279 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 — [no] eth-test-enable — bit-error-threshold bit-errors — test-pattern {all-zeros | all-ones} [crc-enable] — no test-pattern — [no] facility-fault — grace — eth-ed — max-rx-defect-window seconds — no max-rx-defect-window — priority priority — no priority —...
  • Page 280: Ethernet Tunnel Commands

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 — no port-weight-speed — selection-criteria {highest-count | highest-weight | best-port} [slave-to-partner] [subgroup-hold-time hold-time] — no selection-criteria — [no] shutdown — standby-signaling {lacp | power-off} — no standby-signaling — weight-threshold value [action {dynamic-cost | down}] —...
  • Page 281: Multi-Chassis Redundancy Commands

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 — no test-pattern — grace — eth-ed — max-rx-defect-window seconds — no max-rx-defect-window — priority priority — no priority — [no] rx-eth-ed — [no] tx-eth-ed — eth-vsm-grace — [no] rx-eth-vsm-grace — [no] tx-eth-vsm-grace — low-priority-defect {allDef | macRemErrXcon | remErrXcon | errXcon | xcon | noXcon}...
  • Page 282 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 — keep-alive-interval interval — no keep-alive-interval — [no] passive-mode — [no] shutdown — system-priority value — no system-priority — [no] mc-lag — hold-on-neighbor-failure multiplier — no hold-on-neighbor-failure — keep-alive-interval interval — no keep-alive-interval — lag-id lacp-key admin-key system-id system-id [remote-lag remote-lag-id] system-priority system-priority source- bmac-lsb use-lacp-key...
  • Page 283: Forward Path Extension Commands

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 — source-address ip-address — no source-address — [no] sync — [no] igmp — [no] igmp-snooping — [no] mc-ring — [no] — [no] mld-snooping — pim-snooping [sap] [spoke-sdp] — no pim-snooping — port port-id [sync-tag sync-tag] [create] —...
  • Page 284: Generic Commands

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 • Network Port Commands • Interface Group Handler Commands • Multilink-Bundle Port Commands • SONET/SDH Port Commands • SONET/SDH Path Commands • ATM Interface Commands • Frame Relay Commands • TDM Commands • LAG Commands •...
  • Page 285 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 Parameters description-string — The description character string. Strings can be up to 80 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 286: Card Commands

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 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>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. The operational state of the entity is disabled as well as the operational state of any entities contained within.
  • Page 287 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 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 288 • 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 289 (some may be suppressed in the system by default). In order to facilitate post-failure analysis, Nokia recommends that you enable the reporting of the specific events/errors (configure log event-control) when fail-on- error is enabled.
  • Page 290: Mcm Commands

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 Description This command specifies that if there is a recoverable error in the forwarding path, but that recovery action can have a traffic forwarding impact of a few seconds, the card will reset instead of taking the recovery action. The no form of the command specifies that the recovery action will be taken instead of the card being reset.
  • Page 291: Mda (Xma) Commands

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 Parameters mcm-type — The type of MCM to provision for that slot. Values mcm-v1, mcm-v2 2.25.2.4 MDA (XMA) Commands Syntax mda mda-slot no mda mda-slot Context config>card Description This mandatory command enables access to a card’s MDA CLI context to configure MDAs. Default no mda Parameters...
  • Page 292 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 differential — Specifies that MDA is in the differential clock mode. This CMA/MDA can use differential clock recovery methods. timestamp-freq — This sets the differential timestamp frequency to be 103.68 MHz (default), 77,76 MhZ or 19.44 MHz. The frequency value is entered in kHz, thus valid values are 103680, 77760 and 19440.
  • Page 293 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 threshold Syntax threshold threshold Context config>card>mda>egress-xpl Description This command configures the Egress XPL Error Threshold value used by the fail-on-error feature. Default 1000 Parameters threshold — Specifies an upper limit on the frequency of Egress XPL Errors that can occur on the MDA.
  • Page 294 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 A maximum of two MDAs can be provisioned on an IOM/XCA. Only one MDA can be provisioned per IOM/MDA slot. To modify an MDA slot, shut down all port associations. A maximum of six MDAs or eight CMAs (or a combination) can be provisioned on a 7750 SR- c12.
  • Page 295 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 Description The named-pool-mode CLI context is used to store the MDA and port level named pool mode configuration commands. Currently, only the ingress and egress named-pool-policy commands are supported. Any future named pool mode configuration commands or overrides will be placed in the named-pool-mode CLI context.
  • Page 296 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 Description The named-pool-policy command is used to associate a named pool policy with an MDA or port ingress or egress context. The policy governs the way that named pools are created at the MDA or port level. The policy may be applied regardless of whether the IOM is in named pool mode;...
  • Page 297: Mda/Port Qos Commands

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 Description This command enables synchronous Ethernet on the MDA. Then any port on the MDA can be used as a source port in the sync-if-timing configuration. The no form of the command disables synchronous Ethernet on the MDA. 2.25.2.5 MDA/Port QoS Commands access...
  • Page 298 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 config>port>access>ingress config>port>network>egress config>port>network>ingress config>port>access>uplink>egress Description This command configures pool policies. On the MDA level, access and network egress and access ingress pools are only allocated on channelized MDAs. On the MDA level, access and network egress and access ingress pools are only allocated on channelized MDAs.
  • Page 299 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 no red-alarm-threshold Context config>card>mda>access>egress>pool config>card>mda>access>ingress>pool config>card>mda>network>egress>pool config>card>mda>network>ingress>pool config>port>access>egress>pool config>port>access>ingress>pool config>port>network>egress>pool Description This command configures the threshold for the red 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.
  • Page 300 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 • The size of the shared portion of the buffer pool is indirectly established. The shared size is important to the calculation of the instantaneous-shared-buffer-utilization and the average-shared-buffer-utilization variables used in Random Early Detection (RED) per packet slope plotting.
  • Page 301 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 Context config>port>access>egress>pool 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 specifies an existing slope policy which defines high and low priority RED slope parameters and the time average factor. The policy is defined in the config>qos>slope-policy context.
  • Page 302: Power Commands

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 Default 1000 Parameters threshold — Specifies an upper limit on the frequency of Ingress XPL Errors that can occur on the MDA. When fail-on-error is enabled, if the MDA experiences more than threshold errors per minute for window minutes, the MDA will be put in the failed state.
  • Page 303 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 mode Syntax mode {none | basic | advanced} Context config>system>power-management Description This command sets the power mode. Default basic mode Parameters none — Specifies that there is no management of power to modules. In this mode, no gradual shutdown of active XCMs and XMAs is enforced.
  • Page 304 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 Parameters peq-type — Identifies the APEQ type. Values apeq-dc-2000, apeq-dc-2200-2800, apeq-ac-3000, apeq-hvdc- 3000 Default apeq-dc-2000 input-power-mode Syntax input-power-mode amperage Context config>system>pwr-mgmt>peq Description This command sets the input-power-mode of the APEQ for the designated APEQ slot. Parameters amperage —...
  • Page 305: Virtual Scheduler Commands

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 power-safety-level Syntax power-safety-level percent Context config>system>pwr-mgmt Description This command sets the Power Safety Level, which is a percentage of the calculated worst case power draw value. Once a Power Safety Level is configured by the operator, both the Basic and Advanced modes use the Power Safety Level as a reference for calculating the power redundancy using N+1 algorithm during start up and recovery from power depression.
  • Page 306 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 Description This command overrides the default minimum time that must elapse before a policer or queue’s offered rate may be recalculated. A minimum time between offered rate calculations is enforced to both prevent inaccurate estimation of the offered rate and excessive input to the virtual scheduler process.
  • Page 307 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 slow-queue percent-of-default — The slow-queue percent-of-default parameter is optional and is used to modify the default minimum rate calculation time for “slow” queues. Defining 100.00 percent is equivalent to removing the override (restoring the default) on the slow queue minimum rate calculation time.
  • Page 308 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 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. The rate is determined based on the previous calculated offered rate for the policer or queue.
  • Page 309: Forwarding Plane Configuration Commands

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 2.25.2.8 Forwarding Plane Configuration Commands Syntax fp [fp-number] Context config>card Description This command enables access to the configuration of the forwarding planes on a card. Depending on the type of card, there may be one or two forwarding planes. The default forwarding plane is 1.
  • Page 310 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 Description The buffer-allocation command defines the amount of buffers that will be set aside for WRED queue buffer pools. Note that the min percentage and max percentage parameters must be set to the same value. The forwarding plane protects against cross application buffer starvation by implementing a hierarchy of buffer pools.
  • Page 311 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 Context config>card>fp>egress>wred-queue-control 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 312 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 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 313 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 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 314 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 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 315 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 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 316 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 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 317 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 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 318 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 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 319 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 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 320 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 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 321 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 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 322 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 • 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 323 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 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 324 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 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 325 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 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 326 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 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 327 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 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 328 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 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 329 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 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 330 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 The stat-mode setting defined for the policer in the QoS policy may be overridden on an sla- profile or SAP where the policy is applied. If insufficient policer counter resources exist to implement the override, the stat-mode override command will fail. The previous stat-mode setting active for the policer will continue to be used by the policer.
  • Page 331 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 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 332 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 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 333: General Port Commands

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 create — Keyword used to create the queue-group instance. 2.25.2.9 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).
  • Page 334 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 where: bundle: keyword slot: IOM/MDA slot numbers bundle-num: 1 to 336 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 335 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 The no form of this command deletes an aps-group-id or bundle-aps-group-id. In order for an aps-group-id to be deleted, 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).
  • Page 336 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 amplifier Syntax amplifier 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 337 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 Description This command configures the Dense Wavelength Division Multiplexing (DWDM) ITU channel at which a tunable MDA optical interface will be configured to operate. It is expressed in a form that is derived from the laser's operational frequency. For example 193.40 THz corresponds to DWDM ITU channel 34 in the 100 GHz grid and 193.45 THz corresponds to DWDM ITU channel 345 in the 50 GHz grid.
  • Page 338 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 Table 34 DWDM Channel Numbers (Continued) C-Band 100 GHz Grid 50GHz Grid Channel Channel 1538.19 194.90 1538.58 194.85 1538.98 194.80 1539.37 194.75 1539.77 194.70 1540.16 194.65 1540.56 194.60 1540.95 194.55 1541.35 194.50 1541.75 194.45 1542.14 194.40 1542.54...
  • Page 339 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 Table 34 DWDM Channel Numbers (Continued) C-Band 100 GHz Grid 50GHz Grid Channel Channel 1558.17 192.40 1558.58 192.35 1558.98 192.30 1559.39 192.25 1559.79 192.20 1560.20 192.15 1560.61 192.10 1561.01 192.05 1561.42 192.00 1561.83 191.95 1562.23 191.90 1562.64...
  • Page 340 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 Parameters window-size — Indicates the number of symbols used for carrier phase recovery algorithm of the receiver. When this parameter is changed, the link will bounce because the receiver needs to be reconfigured. Values [2, 4, 8, 16, 32, 64] symbols wavetracker Syntax...
  • Page 341 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 target-power Syntax target-power power Context config>port>dwdm>coherent Description This command configures the target transmit optical power for the port. Default 1.00 dBm 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-...
  • Page 342 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 Parameters wave-key — The wave-key values must be selected based on the currently configured DWDM ITU channel. Both keys must be odd or both keys must be even. One even key and one odd key cannot be configured. The ranges of values for each key are defined in Table Table 35...
  • Page 343 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 Table 35 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 1157 1171 1641 1655...
  • Page 344 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 Table 35 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 3502 3516 4014 4028...
  • Page 345 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 Table 35 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 3908 3922 2372 2386...
  • Page 346 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 dispersion Syntax dispersion dispersion 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...
  • Page 347 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 report-alarms Syntax [no] report-alarms [nrdy] [mth] [mtl] [unlck] [tlim] [einv] [com] Context config>port>dwdm>tdcm 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 —...
  • Page 348 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 Parameters squelch — Specifies the squelch (turn off) the transmit signal on RX LOS. 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 —...
  • Page 349 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 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 350 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 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 351 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 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 352 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 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 353 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 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 354 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 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 355 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 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 356 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 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 357 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 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 — [byte1 byte2 to byte64]. Sets the PM TTI to the sequence of bytes provided by the user.
  • Page 358 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 • portnum — The fourth section contains the port number. • dwdmchan — The fifth section contains the DWDM channel number (see DWDM Channel Numbers). Parameters auto-generated — Specifies to use the system generated (default) TTI. identifier —...
  • Page 359 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 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 360 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 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 361 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 Table 36 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 362 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 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 363 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 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 364 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 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 365 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 egress-scheduler-override Syntax egress-scheduler-override [create] no egress-scheduler-override Context config>port>sonet-sdh>path config>port>ethernet config>port>tdm>ds3 config>port>tdm>ds1>channel-group config>port>tdm>e1>channel-group config>port>tdm>e3 Description This command applies egress scheduler overrides. When a port scheduler is associated with an egress port, it is possible to override the following parameters: •...
  • Page 366 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 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 367 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 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 368 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 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 369 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 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 370 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 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 371 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 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 372 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 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 373 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 Table 37 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 374 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 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 375 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 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 376 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 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 377: 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.25.2.10 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 378 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 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 379: Forwarding Path Extension (Fpe) Commands

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 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 380 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 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 381 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 Description This command configures FPE for subscriber management. Default no sub-mgmt-extensions vxlan-termination Syntax [no] vxlan-termination Context config>fwd-path-ext>fpe Description This command informs the system about the type of the cross-connect that is required in order to terminate non-system IPv4 and IPv6 VXLAN. Internally, it will trigger the automatic creation of two internal IP interfaces in the PXC ports and will enable those internal interfaces to process and terminate VXLAN.
  • Page 382: Aps Commands

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 2.25.2.12 APS Commands Syntax Context config>port Description This command configures APS (Automatic Protection Switching). APS is used by SONET/ SDH add/drop multiplexers (ADMs) or other SONET/SDH-capable equipment to protect against circuit or equipment failure. An APS group contains a working and a protect circuit and can span a single node (SC-APS) or two nodes (MC-APS).
  • Page 383 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 no hold-time Context config>port>aps Description This command specifies how much time can pass, in 100s of milliseconds, without receiving an advertise packet from the neighbor before the multi-chassis signaling link is considered not operational. The hold-time is usually 3 times the value of the advertise-interval.
  • Page 384 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 neighbor Syntax neighbor ip-address no neighbor Context config>port>aps Description This command specifies the neighbor's IP address only on a multi-chassis APS where the working and protect circuits are configured on different routers. When the value the neighbor IP address is set to 0.0.0.0, this implies that the APS group is configured as a single-chassis APS group.
  • Page 385 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 When a port is a protect-circuit of an APS group, the configuration options available in the config>port port-id>sonet-sdh context is not allowed for that port unless it is part of the noted exceptions. The exception list includes these SONET/SDH commands: •...
  • Page 386 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 • circuit–RDI alarms are H/W-generated independently on each working and protect circuit based on RX failure of that circuit regardless of APS line status. • suppress–RDI H/W generation on working and protect circuits is suppressed. No alarms are generated on RX failure of that circuit.
  • Page 387 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 working-circuit Syntax working-circuit port-id [number number] no work-circuit [number number] Context config>port>aps Description This command configures a physical port that will act as the working circuit for this APS group. The working circuit port must contain only the default configuration and cannot be part of another APS group.
  • Page 388 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 Modifying Hold-Down Timer Values Note that for APS configurations, the hold-time down and hold-time up default values are 100 ms and 500 ms respectively. But, if there is a large difference in the transmission delay between the APS working (working-circuit) and protect line (protect-circuit), it is highly recommended that you increase the default timer on the working line accordingly with the transmission delay present on the protect line.
  • Page 389: Ethernet Port Commands

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 Hold time up : 500 milliseconds Hold time down : 0 milliseconds Transceiver Data Transceiver Type : SFP Model Number : SFP-OC48-SR1 Transceiver Code : OC48 SR Laser Wavelength : 1310 Diag Capable : yes Connector Code : LC Vendor OUI...
  • Page 390 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 Description This command enables access to configure Ethernet port attributes. This context can only be used when configuring Fast Ethernet, gigabit, or 10-Gb Ethernet LAN ports on an appropriate MDA. mode Syntax mode {access | network | hybrid} no mode Context config>port>ethernet...
  • Page 391 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 The user configures a network IP interface under config>router>if>port by providing the port name which consists of the port-id of the hybrid mode port and an unused VLAN tag value. The format is <port-id>:qtag1. The user must explicitly enter a valid value for qtag1. The <port-id>:* value is not supported on a network IP interface.
  • Page 392 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 queue-group Syntax queue-group queue-group-name [instance instance-id] [create] no queue-group queue-group-name [instance instance-id] Context config>port>ethernet>access>egress config>port>ethernet>access>ingress Description This command creates an ingress or egress queue group on an Ethernet port. A queue group is a collection of queues identified by a group name. Queue groups created on access ports are used as an alternative queue destination for SAPs.
  • Page 393 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 A queue group does not have an administrative shutdown or no shutdown command. A queue group is considered to be always on once created. When creating a queue group, the system will attempt to allocate queue resources based on the queues defined in the queue group template.
  • Page 394 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 queue-group Syntax [no] queue-group queue-group-name [instance instance-id] [create] Context config>port>ethernet>access>egr config>port>ethernet>access>ing Description This command creates an ingress or egress queue group on an Ethernet port. A queue group is a collection of queues identified by a group name. Queue groups created on access ports are used as an alternative queue destination for SAPs.
  • Page 395 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 A queue group does not have an administrative shutdown or no shutdown command. A queue group is considered to be always on once created. When creating a queue group, the system will attempt to allocate queue resources based on the queues defined in the queue group template.
  • Page 396 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 rate Syntax rate kilobits-per-second no rate 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 Description This command defines the enforced aggregate rate for all queues associated with the agg- rate context. A rate must be specified for the agg-rate context to be considered to be active on the context’s object (SAP, subscriber, VPORT and so on).
  • Page 397 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 host-match Syntax host-match dest destination-string [create] no host-match dest destination-string Context config>port>ethernet>access>egr>qgrp Description This command configures host matching for the Ethernet port egress queue-group. The no form of the command removes host matching for the Ethernet port egress queue- group.
  • Page 398 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 Description This command enables the context to define optional queue parameter overrides for each queue within the queue group. queue Syntax queue queue-id [create] no queue queue-id Context config>port>ethernet>access>egr>qgrp>qover config>port>ethernet>access>ing>qgrp>qover config>port>eth>network>egr>qgrp>qover 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.
  • Page 399 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 Parameters weight — Weight defines the relative weight of this queue in comparison to other child schedulers and queues while vying for bandwidth on the parent scheduler-name. Any queues or schedulers defined as weighted receive no parental bandwidth until all strict queues and schedulers on the parent have reached their maximum bandwidth or are idle.
  • Page 400 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 adaptation-rule — Specifies the adaptation rule to be used while computing the operational CIR or PIR value. Values max — The max (maximum) option is mutually exclusive with the min and closest options. When max is defined, the operational PIR for the queue will be equal to or less than the administrative rate specified using the rate command.
  • Page 401 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 size — When a numeric value is specified (size), the system interprets the value as an explicit burst limit size. The value is expressed as an integer and by default is interpreted as the burst limit in kilobytes. If the value is intended to be interpreted in bytes, the byte qualifier must be added following size.
  • Page 402 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 config>port>ethernet>network>egr>qgrp>qover>q Description This command enters the context to configure queue drop tail parameters. Syntax Context config>port>eth>access>ing>qgrp>qover>q>drop-tail config>port>eth>access>egr>qgrp>qover>q>drop-tail config>port>ethernet>network>egr>qgrp>qover>q>drop-tail Description This command enters the context to configure the queue low drop tail parameters. The low drop tail defines the queue depth beyond which out-of-profile packets will not be accepted into the queue and will be discarded.
  • Page 403 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 The MBS value is used by a queue to determine whether it has exhausted all of its buffers while enqueuing packets. Once the queue has exceeded the amount of buffers allowed by MBS, all packets are discarded until packets have been drained from the queue. The queue-group or network egress QoS context for mbs provides a mechanism for overriding the default maximum size for the queue.
  • Page 404 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 percent-rate Syntax percent-rate pir-percent [cir cir-percent] Context config>port>ethernet>network>egr>qgrp>qover>q Description This command specifies percent rates (CIR and PIR). Parameters pir-percent — Specifies the PIR as a percentage. Values 0.01 to 100.00 cir-percent — Specifies the CIR as a percentage. Values 0.00 to 100.00 rate...
  • Page 405 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 Parameters pir-rate — Defines the administrative PIR rate, in kilobits, for the queue. When the rate command is executed, a valid PIR setting must be explicitly defined. When the rate command has not been executed, the default PIR of max is assumed. Fractional values are not allowed and must be given as a positive integer.
  • Page 406 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 create — Creates a new secondary shaper for this port. 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.
  • Page 407 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 class Syntax class class-number rate rate [monitor-threshold size-in-kilobytes] [burst-limit size] [bytes | kilobytes] no class class-number 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 408 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 rate Syntax rate rate [monitor-threshold size-in-kbytes] no rate Context config>port>ethernet>egress>exp-secondary-shaper 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.
  • Page 409 (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 410 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 A multicast channel bandwidth is subtracted from or added to the Vport rate limit according to the received IGMP Join/Leave messages and the channel bandwidth definition policy associated with the Vport (indirectly through a group-interface). Since the multicast traffic on the PON port is shared amongst subscribers behind this PON port, only the first IGMP Join or the last IGMP Leave per multicast channel is tracked for the purpose of the Vport bandwidth modification.
  • Page 411 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 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 412 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 The parent Vport of a subscriber host queue, which has the port-parent option enabled, is determined by matching the destination string dest string associated with the subscriber and the organization string org string associated with the subscriber host with the strings defined under a Vport on the port associated with the subscriber.
  • Page 413 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 If the autonegotiate limited keyword option is specified the port will auto-negotiate but will only advertise a specific speed and duplex. The speed and duplex advertised are the speed and duplex settings configured for the port. One use for limited mode is for multi-speed Gb ports to force Gb operation while keeping autonegotiation enabled for compliance with IEEE 801.3.
  • Page 414 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 Parameters full — Sets the link to full duplex mode. half — Sets the link to half duplex mode. efm-oam Syntax efm-oam Context config>port>ethernet Description This command configures EFM-OAM attributes. accept-remote-loopback Syntax [no] accept-remote-loopback Context config>port>ethernet>efm-oam Description...
  • Page 415 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 416 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 417 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 hold-time Syntax hold-time time-value no hold-time Context config>port>ethernet>efm-oam Description This command configures efm-oam operational transition dampening timers which reduce the number of efm-oam state transitions reported to upper layers. Default Parameters time-value — Indicates the number of seconds that the efm-oam protocol will wait before going back to the operational state after leaving the operational state.
  • Page 418 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 Description This context contains link monitoring specific options defining the various local thresholds, port interaction and peer notification methods. In order to activate Link monitoring function, this context must be configured with the no shutdown option. Shutting down link monitoring will clear all historical link monitoring counters.
  • Page 419 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 sd-threshold Syntax sd-threshold errored-frames no sd-threshold Context config>port>ethernet>efm-oam>link-mon>errored-frame 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.
  • Page 420 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 Description This command defines the size of the window using a 100ms base deciseconds. Errors are accumulated until the end of the window. At the end of the window the actual errors are compared to the thresholds to determine if a threshold has been crossed. There is no mid- window threshold checking.
  • Page 421 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 sf-threshold Syntax sf-threshold errored-frames Context config>port>ethernet>efm-oam>link-mon>errored-frame-period 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 422 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 sd-threshold Syntax sd-threshold errored-frames no sd-threshold Context config>port>ethernet>efm-oam>link-mon>errored-frame-seconds Description The option is used to define the number of errored frame seconds within the configured window which indicates the port has gone beyond an acceptable error rate and should be considered degraded.
  • Page 423 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 Description This command defines the size of the window using a 100ms base deciseconds. Errored seconds are accumulated until the end of the window. At the end of the window, the actual errors are compared to the thresholds to determine if a threshold has been crossed. There is no mid-window threshold checking.
  • Page 424 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 Context config>port>ethernet>efm-oam>link-mon>errored-symbols Description This command defines 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. An event is raised when the error count is equal to or greater than this value.
  • Page 425 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 Parameters deciseconds — Specifies the number of 100ms increments in increments of 10 (full seconds). Values 10 to 600 Default shutdown Syntax [no] shutdown Context config>port>ethernet>efm-oam>link-monitoring Description This command enables or disables the link monitoring function. Issuing a no shutdown will start the process.
  • Page 426 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 event-notification-burst Syntax event-notification-burst packets Context config>port>ethernet>efm-oam>link-mon>local-sf-action Description This command defines the number of the Event Notification OAM PDU to be send to the peer if the local signal failure threshold (sf-threshold) has been reached. The sending of the Event Notification OAMPDU is configured under the individual monitors.
  • Page 427 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 critical-event Syntax [no] critical-event Context config>port>ethernet>efm-oam>link-mon>local-sf-action>info-notification Description This command sets the critical event Flag field in the Information OAMPDU when the local signal failure (sf-threshold) threshold is reached. This will be maintained in all subsequent Information OAM PDUs until the situation is cleared.
  • Page 428 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 Default active Parameters active — Provides capability to initiate negotiation and monitoring activities. passive — Relies on peer to initiate negotiation and monitoring activities. peer-rdi-rx Syntax peer-rdi-rx Context config>port>ethernet>efm-oam Description This container allows an action to be configured for the various event conditions that can be received from a peer under the context of the EFM OAM protocol.
  • Page 429 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 Parameters local-port-action — Defines whether or not the local port will be affected when a dying gasp event is received from a peer. log-only — Keyword that prevents the port from being affected when the local peer receives a dying gasp.
  • Page 430 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 Description This command defines how to react to the reception of a link fault flag set in the informational PDU from a peer. Default link-fault local-port-action out-of-service Parameters local-port-action — Defines whether or not the local port will be affected when a link fault is received from a peer.
  • Page 431 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 The no form of this command disables this functionality. Default no trigger-fault Parameters dying-gasp — Keyword to set the dying gasp flag. critical-event — Keyword to set the critical event flag. tunneling Syntax [no] tunneling Context config>port>ethernet>efm-oam Description...
  • Page 432 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 The no form of this command restores the default. Default null Parameters dot1q — Ingress frames carry 802.1Q tags where each tag signifies a different service. null — Ingress frames will not use any tags to delineate a service. As a result, only one service can be configured on a port with a null encapsulation type.
  • Page 433 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 hold-time down — The delay, in seconds or centiseconds, to notify the upper layers after an interface transitions from an up state to a down state. Values 0 to 36000 seconds 0, 10 to 3600000 centiseconds in 5 centisecond increments seconds | centiseconds —...
  • Page 434 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 group Syntax group group-id rate rate no group group-id Context config>port>ethernet>hsmda Description This command changes the maximum rate allowed for a weighted scheduling group on the local HSMDA scheduler. Scheduling classes within the group are managed with an aggregate rate limit when either an explicit group rate is defined on the HSMDA scheduling policy or a local override is defined based on the group override command.
  • Page 435 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 Parameters rate — The rate parameter is mutually exclusive to specifying the max keyword. When executing the max-rate override command either the keyword max or a rate in megabits-per-second must be specified. Values 1 to 10000, max (Mbps) max —...
  • Page 436 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 When a scheduling class has a local rate override, the HSMDA policy associated with the override cannot move the scheduling class into a weighted scheduling group. Similarly, when a scheduling class has a local weight override, the HSMDA policy associated with the override cannot define a rate (neither max nor a megabit-per-second value) for the scheduling class.
  • Page 437 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 Default no ingress-rate Parameters sub-rate — The egress rate in mbps. Values 1 to 100000 mbps lacp-tunnel Syntax [no] lacp-tunnel Context config>port>ethernet Description This command enables LACP packet tunneling for the Ethernet port. When tunneling is enabled, the port will not process any LACP packets but will tunnel them instead.
  • Page 438 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 The hashing algorithm addresses finer spraying granularity where many hosts are connected to the network. To address more efficient traffic distribution between network links (forming a LAG group), a hashing algorithm extension takes into account Layer 4 information (src/dst L4-protocol port).
  • Page 439 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 pbb-etype Syntax pbb-etype [ethertype-value] no pbb-etype Context config>port>ethernet Description This command configures the Ethertype used for PBB encapsulation. Default 0x88E7 Parameters ethertype-value — Specifies the Ethertype value in the form of 0x600 to 0xfff. Values 1536 to 65535 (accepted in decimal or hex) ptp-asymmetry...
  • Page 440 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 report-alarm Syntax [no] report-alarm [signal-fail] [remote] [local] [no-frame-lock] [high-ber] [no-block-lock] [no-am-lock] [duplicate-lane] Context config>port>ethernet Description This command specifies when and if to generate alarms and alarm clear notifications for this port. Parameters signal-fail — Reports an Ethernet signal lost alarm. remote —...
  • Page 441 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 single-fiber Syntax [no] single-fiber Context config>port>ethernet Description This command enables packet gathering and redirection of IP packets from a single fiber (RX) port of the Ethernet or SONET/SDH interface and redistributes packets to other interfaces through either static routes or policy-based forwarding.
  • Page 442 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R1 code-type Syntax code-type [sonet | sdh] Context config>port>ethernet>ssm Description This command configures the encoding of synchronization status messages. For example, whether to use an SDH or SONET set of values. Configuring the network-type is only applicable to SyncE ports.
  • Page 443 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R1 Context config>port>ethernet>sym-mon Description This command specifies the error rate at which to declare the Signal Degrade condi