03-05-2014 07:24 PM
Why are the channel numbers output from "show controllers tenGigE <port> phy" reporting incorrect channels?
I have seen this in IOS XR 4 and 5 now. The channel is incorrect but the tuned wave is correct and the channel appears correct in the configuration.
I searched for caveats but found nothing... Am I just overlooking something?
RP/0/RSP0/CPU0:ios(config)#int tenGigE 0/1/0/0
RP/0/RSP0/CPU0:ios(config-if)#shut
RP/0/RSP0/CPU0:ios(config-if)#controller dwdm 0/1/0/0
RP/0/RSP0/CPU0:ios(config-dwdm)#admin-state maintenance
Wed Mar 5 11:29:49.698 UTC
Maintenance will be Forced one if it is disabled for this port. You may first verify the status by the show interfaces command.
RP/0/RSP0/CPU0:ios(config-dwdm)#commit
Wed Mar 5 11:29:50.818 UTC
RP/0/RSP0/CPU0:ios(config-dwdm)#wavelength 55
RP/0/RSP0/CPU0:ios(config-dwdm)#commit
Wed Mar 5 11:29:58.577 UTC
RP/0/RSP0/CPU0:ios(config-dwdm)#admin-state in-service
RP/0/RSP0/CPU0:ios(config-dwdm)#commit
Wed Mar 5 11:30:05.217 UTC
RP/0/RSP0/CPU0:ios(config-dwdm)#int tenGigE 0/1/0/0
RP/0/RSP0/CPU0:ios(config-if)#no shut
RP/0/RSP0/CPU0:ios(config-if)#commit
Wed Mar 5 11:30:13.810 UTC
RP/0/RSP0/CPU0:ios(config-if)#exit
RP/0/RSP0/CPU0:ios(config)#exi
RP/0/RSP0/CPU0:ios#
RP/0/RSP0/CPU0:ios#
RP/0/RSP0/CPU0:ios#show controllers tenGigE 0/1/0/0 phy | begin Signal
Wed Mar 5 11:30:32.570 UTC
Signal Condition Control: Normal Async REFCLK,
Thresholds: Alarm High Warning High Warning Low Alarm Low
Temperature: 73.000 70.000 -5.000 -8.000
Voltage: 0.000 Volt 0.000 Volt 0.000 Volt 0.000 Volt
Bias: 85.000 mAmps 72.000 mAmps 10.000 mAmps 5.000 mAmps
Transmit Power: 3.981 mW (6.00 dBm) 2.512 mW (4.00 dBm) 0.794 mW (-1.00 dBm) 0.501 mW (-3.00 dBm)
Receive Power: 0.398 mW (-4.00 dBm) 0.251 mW (-6.00 dBm) 0.002 mW (-27.96 dBm) 0.001 mW (-30.00 dBm)
Laser First Frequency: 191 THz, 950.000 GHz
Laser Last Frequency: 196 THz, 0.000 GHz
Laser Min Grid Spacing: 50.000 GHz
Wavelength Control: setpoint=1550.05 nm, error=0.00 nm
FEC Control: amplitude_threshold=50.00%, phase_setpoint=50.00%
Temperature: 42.949
Voltage: 0.000 Volt
Tx Bias: 20.654 mAmps
Tx Power: 1.413 mW (1.50 dBm)
Rx Power: 0.000 mW (<-40.00 dBm)
Control Status: Module NR, Interrupt, Rx LOS, Rx not ready, Rx CDR not locked,
Wavelength Channel: 30
Wavelength Error: 0.000 GHz
03-10-2014 12:15 AM
1)
CLI configures XR Channel.
'wavelength 55' maps to Wavelength '1550.116 nm'
The following CLI gives CLI mapping to Wavelength (nm).
RP/0/RSP0/CPU0:RR03#sh controllers dwdm 0/1/0/0 wavelength-map
55 6 193.40 1550.116
2)
SW translates configured 'wavelength <channel number>' to
Optics Channel number (30) to get Wavelength 1550.05 nm.
RP/0/RSP0/CPU0:ios#show controllers tenGigE 0/1/0/0 phy | begin Signal
..
Laser First Frequency: 191 THz, 950.000 GHz
Laser Last Frequency: 196 THz, 0.000 GHz
Laser Min Grid Spacing: 50.000 GHz
Wavelength Control: setpoint=1550.05 nm, error=0.00 nm
FEC Control: amplitude_threshold=50.00%, phase_setpoint=50.00%
Temperature: 42.949
Voltage: 0.000 Volt
Tx Bias: 20.654 mAmps
Tx Power: 1.413 mW (1.50 dBm)
Rx Power: 0.000 mW (<-40.00 dBm)
Control Status: Module NR, Interrupt, Rx LOS, Rx not ready, Rx CDR not locked,
Wavelength Channel: 30
Wavelength Error: 0.000 Ghz
3)
Instead we recommend our customers to use the following CLI which gives option to
Configure wavelength in 'nm'.
RP/0/RSP0/CPU0:RR03(config-dwdm)#wavelength update ?
<1528773-1568362> Enter 7-digit Wavelength data; e.g. 1532290 for 1532.29 nm
Available wavelength is given by this CLI.
RP/0/RSP0/CPU0:RR03#sh controllers dwdm 0/1/0/0 wavelength-map
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: