Cisco NCS1004 - Page 37

Port : OTU4 0/0/0/0
Controller State : Up
Inherited Secondary State : Normal
Configured Secondary State : Maintenance
Derived State : Maintenance
Loopback mode : Internal
BER Thresholds : SF = 1.0E-5 SD = 1.0E-7
Performance Monitoring : Enable
Bandwidth : 100.0Gb/s
Alarm Information:
LOS = 1 LOF = 0 LOM = 0
OOF = 0 OOM = 0 AIS = 0
IAE = 0 BIAE = 0 SF_BER = 0
SD_BER = 0 BDI = 0 TIM = 0
FECMISMATCH = 0 FEC-UNC = 0
Detected Alarms : None
Bit Error Rate Information
PREFEC BER : 0.00E+00
POSTFEC BER : 0.00E+00
TTI :
Remote hostname : ios
Remote interface : OTU4 0/0/0/0
Remote IP addr : 0.0.0.0
FEC mode : STANDARD
AINS Soak : None
AINS Timer : 0h, 0m
AINS remaining time : 0 seconds
Configuring Loopback on 2-QDD-C Card
From R7.3.1 onwards, 2-QDD-C card supports loopback on the 100 and 400GE controllers.
On applying client side loopbacks, traffic is looped and does not continue in the 2-QDD-C card. QSFP
squelching happens on applying internal loopback.
Note
To configure the loopback on the controllers, use the following commands.
configure
controller controllertype Rack/Slot/Instance/Port/Lanenumber
sec-admin-state maintenance
loopback [ line | internal ]
commit
The following is a sample in which the internal loopback is configured on the 100GE controller.
RP/0/RP0/CPU0:ios#configure
RP/0/RP0/CPU0:ios(config)#controller hundredGigECtrlr 0/0/0/5
RP/0/RP0/CPU0:ios(config-eth-ctrlr)#sec-admin-state maintenance
RP/0/RP0/CPU0:ios(config-eth-ctrlr)#loopback internal
RP/0/RP0/CPU0:ios(config-eth-ctrlr)#commit
Configuring Controllers
37
Configuring Controllers
Loopback