Configuring IPoDWDM
This chapter provides information about configuring IP over dense wavelength-division multiplexing (IPoDWDM) on the Cisco 7600 Series Ethernet Services Plus (ES+) and Ethernet Services Plus T (ES+T) line cards on the Cisco 7600 series router.
IP over DWDM can be configured on the following Cisco 7600 Series ES+ Extended Transport (ES+XT) line cards:
- 76-ES+XT-2TG3CXL
- 76-ES+XT-4TG3CXL
- 76-ES+T-2TG
- 76-ES+T-4TG
- 76-ES+XC-20G3C
- 76-ES+XC-20G3CXL
- 76-ES+XC-40G3C
- 76-ES+XC-40G3CXL
For more information about the commands in this chapter, see the Cisco IOS Release 12.2 SR Command References at http://www.cisco.com/en/US/products/ps6922/prod_command_reference_list.html .
Note
Unless specified otherwise, the information provided in this chapter is applicable to ES+XT, ES+T and ES+XC line cards. IPoDWDM is supported on ES+XC line cards from SRE1 and later releases.
WAN PHY and OTN Support on ES+XC Combination Line Cards
The 10GE ports on the ES+ and ES+T line cards are hardware, which are capable of supporting the Optical Transport Network (OTN) and Wide Area Network (WAN) PHY. This feature provides the software functionality to support OTN and WAN PHY on ES+ and ES+T line cards on Cisco 7600 series router platforms. WAN PHY leverages 10 Gig SONET infrastructure and accesses WAN facilities using:
- Dark Fiber
- Dark Wavelengths
- SONET TDM Networks
This feature provides low cost optic solutions required for short distances networks that implement store and forward network design requiring no optical amplifiers.
The OTN is based on the Optical Transport Hierarchy (OTH) developed by ITU. The OTN is based on the network architecture defined in ITU G.872 "Architecture for the Optical Transport Network (OTN)". The G.872 standard defines an architecture composed of the Optical Channel (OCh), Optical Multiplex Section (OMS), and Optical Transmission Section (OTS). The use of digitally framed signal with digital overhead for optical channel enables you to implement the management requirements of OCh. It also allows the use of Forward Error Correction (FEC) system to improve the system performance. The two new digital layer networks introduced to implement this feature are ODU and OTU.
OTN architecture (ITU-T G.872 standard) defines two interface classes:
- Inter-domain interface (IrDI): The OTN IrDI interface class defines the interface (with the 3Rs [Reamplification, Reshaping and Retiming] processing) at each end of the operator interface. the operator interface can also be the interface between different vendors within the same operator
- Intra-domain interface (IaDI): The IaDI interface class defines the interface within an operator or a vendor domain.
OTN has the following advantages:
- Stronger forward error correction
- More levels of Tandem Connection Monitoring (TCM)
- Transparent transport of client signals
- Switching scalability
Restrictions and Usage Guidelines
When configuring the WAN PHY / OTN support on ES+ and ES+T line cards, follow these restrictions and usage guidelines:
- The distances between the two switching equipments using the WAN PHY and the DWDM facility depends on the XFP used. Refer the data sheets of relevant XFP.
- The MAC address is common for WAN PHY and LAN PHY. The WAN PHY operates at a rate compatible with the payload rate of OC-192c/VC-464c.
Configuring ITU-T G.709 Transport Modes
Use the transport-mode command in interface configuration mode to configure LAN, WAN, and OTN transport modes. The transport-mode command otn option has the bit-transparent sub-option, using which bit transparent mapping into OPU1e or OPU2e can be configured.
Note The hardware combination of Cisco-INTEL OC192 + 10GBASE-L XFP is not supported because of bit rate incompatibility between INTEL XFP and OTN for the following transport mode configurations:
- opu1e - 10GBASE-R over OPU1e without fixed stuffing (11.0491Gb/s)
- opu2e - 10GBASE-R over OPU2e with fixed stuffing (11.0957Gb/s)
SUMMARY STEPS
1. enable
2. configure terminal
3. interface tengigabitethernet slot/port
4. transport-mode {lan | wan | otn bit-transparent {opu1e | opu2e}}
DETAILED STEPS
|
|
|
Step 1 |
enable
|
Enables privileged EXEC mode.
- Enter your password if prompted.
|
Step 2 |
configure terminal
Router# configure terminal |
Enters global configuration mode. |
Step 3 |
interface tengigabitethernet slot/port
Router(config)# interface tengigabitethernet 4/1 |
Specifies the Ten Gigabit Ethernet interface to configure, where:
- slot/port—Specifies the location of the interface.
|
Step 4 |
transport-mode {lan | wan | otn bit-transparent {opu1e | opu2e}}
Router(config-if)# transport-mode otn bit-transparent opu2e |
Configures the transport mode. |
DWDM Provisioning
All DWDM provisioning configurations take place on the controller. To configure a DWDM controller, use the controller dwdm command in global configuration mode.
Prerequisites
The g709 configuration commands can be used only when the controller is in the shutdown state. Use the no shutdown command after configuring the parameters, to remove the controller from shutdown state and to enable the controller to move to up state.
SUMMARY STEPS
1. enable
2. configure terminal
3. controller dwdm slot/port
DETAILED STEPS
|
|
|
Step 1 |
enable
|
Enables privileged EXEC mode.
- Enter your password if prompted.
|
Step 2 |
configure terminal
Router# configure terminal |
Enters global configuration mode. |
Step 3 |
controller dwdm slot/port
Router(config)# controller dwdm 1/3 |
Configures the DWDM controller. |
Examples
The following are examples of IP over DWDM commands:
Router# show run int te2/3
Building configuration...
Current configuration : 96 bytes
interface TenGigabitEthernet2/3
ip address 11.11.11.2 255.255.255.0
transport-mode otn bit-transparent opu2e
Router# show controller dwdm 2/3
Controller dwdm 3/1, is down (shutdown)
Transport mode LAN (10GBASE-R, 10.3125Gb/s)
Description: connected to a ginsu LC
AIS = 0 BDI = 1 BIP = 14504
TIM = 0 IAE = 0 BEI = 2289
Q > 6.45 Q Margin > 7.52 DBQ
Alarm reporting enabled for: LOS LOF LOM OTU-AIS OTU-IAE OTU-BDI OTU-TIM ODU-AIS ODU-OCI ODU-LCK ODU-BDI ODU-PTIM ODU-TIM ODU-BIP Alert reporting enabled for: OTU-SM-TCA ODU-SD-BER ODU-SF-BER ODU-PM-TCA BER thresholds: ODU-SF = 10e-3 ODU-SD = 10e-6 TCA thresholds: SM = 10e-3 PM = 10e-3
OTU TTI Sent String ASCII: This_is_a_static_string
OTU TTI Received String ASCII:
OTU TTI Received String HEX : 0000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000
000000000000000000000000000000 OTU TTI Expected String ASCII: This_is_a_static_string
ODU TTI Sent String ASCII: This_is_a_static_string
ODU TTI Received String ASCII:
ODU TTI Received String HEX : 0000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000
000000000000000000000000000000 ODU TTI Expected String ASCII: This_is_a_static_string
optics type: DWDM XFP Tunable
Wavelength: C-band, channel 10, 1558.17 nm, 192.40 THz Transceiver Rx optical power = -40.0 dBm
Transceiver Tx power = 1.5 dBm
TX Laser current bias = 20988 uAmps
Adjacency info: This_is_a_static_string
Network Connection ID : This_is_a_static_string
Set 1: 6142 19113 14477 26689 4989 31230
Set 2: 14967 7234 29164 19852 15452 17460
Set 3: 14852 28561 6364 12832 21486 14312
Set 4: 30337 19184 28532 15403 21048 27105
Set 5: 18102 24607 16426 14253 21500 21952
Set 6: 13523 17545 7863 538 5251 18205
Set 7: 22331 27781 17862 26935 10028 16539
Set 8: 865 29015 7144 20299 27504 2190
Set 9: 13470 7222 8500 6988 18852 20882
Set 10: 21512 702 14117 1870 19304 13075
Set 11: 11919 26281 1898 18454 9948 15302
Set 12: 24263 24747 5275 29138 17325 19226
Set 13: 10917 18739 16263 20739 13147 18471
Set 14: 1126 24967 26662 16266 32124 32739
Set 15: 20342 29828 7591 18968 2421 24934
Set 16: 3366 27109 22805 3591 7227 9339
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# int tenGigabitEthernet 2/3
Router(config-if)# transport
Router(config-if)# transport-mode ?
lan 10GBASE-R LAN pass-through (10.3125Gb/s)
otn 10GE over Optical Transport Network (G.709)
wan 10GBASE-W WAN SONET/SDH (9.95328Gb/s)
Router(config-if)# transport-mode otn ?
bit-transparent 10GBASE-R transparently mapped into OTU-2
Router(config-if)# transport-mode otn bit-transparent ?
opu1e 10GBASE-R over OPU1e without fixed stuffing (11.0491Gb/s)
opu2e 10GBASE-R over OPU2e with fixed stuffing (11.0957Gb/s)
Router(config-if)# transport-mode otn bit-transparent opu2e
Router# show int tenGigabitEthernet2/3
TenGigabitEthernet2/3 is up, line protocol is up (connected)
Hardware is X40G 10Gb 802.3, address is 00d0.03e2.1c00 (bia 00d0.03e2.1c00)
Internet address is 11.11.11.1/24
MTU 1500 bytes, BW 10000000 Kbit, DLY 10 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Full-duplex, 10Gb/s, clock source internal
Transport mode OTN (10GBASE-R over OPU2e with fixed stuffing, 11.0957Gb/s)
input flow-control is off, output flow-control is off
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:03, output 00:00:03, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Output queue: 0/40 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
L2 Switched: ucast: 0 pkt, 0 bytes - mcast: 2360 pkt, 221372 bytes
L3 in Switched: ucast: 0 pkt, 0 bytes - mcast: 0 pkt, 0 bytes mcast
L3 out Switched: ucast: 0 pkt, 0 bytes mcast: 0 pkt, 0 bytes
2392 packets input, 223718 bytes, 0 no buffer
Received 2477 broadcasts (0 IP multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 0 multicast, 0 pause input
0 input packets with dribble condition detected
2477 packets output, 229905 bytes, 0 underruns
0 output errors, 0 collisions, 13 interface resets
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier, 0 pause output
0 output buffer failures, 0 output buffers swapped out
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# controller dwdm 2/3
Router(config-controller)#?
Controller configuration commands:
Network Configure Vtxp Netwrok parameters
Virtual-Link Configure Virtual Link (PPC)
admin-state Configure the transport admin state of the controller
default Set a command to its defaults
description Controller specific description
exit Exit from controller configuration mode
g709 Configure G709 parameters
help Description of the interactive help system
no Negate a command or set its defaults
shutdown Configure dwdm controller processing
transport-mode Configure 10GE PHY transport mode
wavelength Configure transponder wavelength
Router(config-controller)# g709 ?
odu Configure odu parameters
otu Configure otu parameters
tti-processing Configure Trail Trace Identifier processing
Router(config-controller)# g709 fec ?
enhanced Enhanced FEC mode
standard Standard FEC mode
Router(config-controller)# g709 odu ?
overhead Configure ODU overhead
report Configure odu alarm reporting
threshold Configure odu threshold
Router(config-controller)#g709 odu overhead ?
tti Configure ODU Trail Trace Identifier buffer
Router(config-controller)#g709 odu overhead tti ?
expected Set expected TTI
Router(config-controller)#g709 odu overhead tti expected ?
hex Enter hex string- Length should be even number
Router(config-controller)#g709 odu overhead tti expected ascii ?
WORD LINE ASCII text (Max 64 characters)
Router(config-controller)#g709 odu overhead tti expected hex ?
Hex-data LINE Hex nibbles (Max 128- The string length should
Router(config-controller)#g709 odu overhead tti sent ?
hex Enter hex string- Length should be even number
Router(config-controller)#g709 odu overhead tti sent ascii ?
WORD LINE ASCII text (Max 64 characters)
Router(config-controller)#g709 odu overhead tti sent hex ?
Hex-data LINE Hex nibbles (Max 128- The string length should
Router(config-controller)# g709 odu report ?
ais Set Alarm Indication Signal reporting status
bdi Set Backward Defect Indication reporting status
lck Set Upstream Connection Locked reporting status
oci Set Open Connection Indication reporting status
pm-tca Set Path Monitoring BER TCA reporting status
ptim Set Payload Type Identifier Mismatch reporting status
sd-ber Set SM BER in excess of SD threshold reporting status
sf-ber Set SM BER in excess of SF threshold reporting status
tim Set Trace Identifier Mismatch reporting status
Router(config-controller)# g709 odu threshold ?
pm-tca Set Path Monitoring Threshold Crossing Alert threshold
sd-ber Set Signal Degrade BER threshold
sf-ber Set Signal Failure BER threshold
Router(config-controller)# g709 odu threshold pm-tca ?
<3-9> Bit Error Rate (10 to the minus n) (default 3)
Router(config-controller)# g709 odu threshold sd-ber ?
<3-9> Bit Error Rate (10 to the minus n) (default 6)
Router(config-controller)# g709 odu threshold sf-ber ?
<3-9> Bit Error Rate (10 to the minus n) (default 3)
Router(config-controller)# g709 otu ?
overhead Configure OTU overhead
report Configure otu alarm reporting
threshold Configure otu threshold
Router(config-controller)#g709 otu overhead ?
tti Configure OTU Trail Trace Identifier buffer
Router(config-controller)#g709 otu overhead tti ?
expected Set expected TTI
Router(config-controller)#g709 otu overhead tti expected ?
hex Enter hex string- Length should be even number
Router(config-controller)#g709 otu overhead tti expected ascii ?
WORD LINE ASCII text (Max 64 characters)
Router(config-controller)#g709 otu overhead tti expected hex ?
Hex-data LINE Hex nibbles (Max 128- The string length should be an
Router(config-controller)#g709 otu overhead tti sent ?
hex Enter hex string- Length should be even number
Router(config-controller)#g709 otu overhead tti sent ascii ?
WORD LINE ASCII text (Max 64 characters)
Router(config-controller)#g709 otu overhead tti sent hex ?
Hex-data LINE Hex nibbles (Max 128- The string length should be an
Router(config-controller)# g709 otu report ?
ais Set Alarm Indication Signal reporting status
bdi Set Backward Defect Indication reporting status
fecmismatch Set FEC Mismatch reporting status
iae Set Incoming Alignment Error reporting status
lof Set OTU Loss of Frame reporting status
lom Set Loss of Multiple Frame reporting status
los Set Loss of Signal reporting status
sm-tca Set Section Monitoring BER TCA reporting status
tim Set Trace Identifier Mismatch reporting status
sd-ber Set SM BER in excess of SD threshold reporting status
sf-ber Set SM BER in excess of SF threshold reporting status
Router(config-controller)# g709 otu threshold ?
sd-ber Set Signal Degrade BER threshold
sf-ber Set Signal Failure BER threshold
sm-tca Set Section Monitoring Threshold Crossing Alert threshold
Router(config-controller)# g709 otu threshold sd-ber ?
<3-9> Bit Error Rate (10 to the minus n) (default 6)
Router(config-controller)# g709 otu threshold sf-ber ?
<3-9> Bit Error Rate (10 to the minus n) (default 3)
Router(config-controller)# g709 otu threshold sm-tca ?
<3-9> Bit Error Rate (10 to the minus n) (default 3)
Enabling OTN Mode Alarms Assertion
By default, all the OTN mode alarms are enabled. To control OTN alarms, disable all the alarms and enable the specific alarms by performing the following steps. Standard FEC is the default FEC mode. Use the show controller command to verify the alarm status and FEC mode. Perform the steps detailed in the section to enable OTN mode alarm assertion. Configure same transport mode or FEC mode on both the routers. The FEC modes, standard and disable, are compatible with each other.
SUMMARY STEPS
1. enable
2. configure terminal
3. controller dwdm slot/port
4. shut
5. {g709 | no g709 } fec { disable | standard | enhanced }
6. { g709 | no g709 } otu report { ais | bdi | fecmismatch | iae | lof | lom | los | sm-tca | tim | sd-ber | sf-ber }
7. { g709 | no g709 } odu report { ais | bdi | lck | oci | pm-tca | ptim | sd-ber | sf-ber | tim }
8. { g709 | no g709 } otu threshold {sd-ber | sf-ber | sm-tca} value
9. { g709 | no g709 } odu threshold { pm-tca | sd-ber | sf-ber } value
10. { g709 | no g709 } otu overhead tti{ expected | sent } { ascii | hex } tti-string
11. { g709 | no g709 } odu overhead tti{ expected | sent } { ascii | hex } tti-string
12. no shut
13. end
DETAILED STEPS
|
|
|
Step 1 |
enable
|
Enables privileged EXEC mode.
- Enter your password if prompted.
|
Step 2 |
configure terminal
Router# configure terminal |
Enters global configuration mode. |
Step 3 |
controller dwdm slot/port
Router(config)# controller dwdm 4/21 |
Configures the DWDM controller. |
Step 4 |
shut
Router(config-controller)# shut |
Shuts down the DWDM controller. |
Step 5 |
{g709 | no g709 } fec { disable | standard | enhanced}
Router(config-controller)# g709 fec enhanced |
Configures the FEC modes |
Step 6 |
{ g709 | no g709 } otu report { ais | bdi | fecmismatch | iae | lof | lom | los | sm-tca | tim | sd-ber | sf-ber }
Router(config-controller)# no g709 otu report lof |
Specifies the supported otu alarms and configures the otu threshold. By default, all alarms are reported. |
Step 7 |
{ g709 | no g709 } odu report { ais | bdi | lck | oci | pm-tca | ptim | sd-ber | sf-ber | tim }
Router(config-controller)# no g709 otu threshold sm-tca |
Specifies the supported odu alarms and configures the odu threshold. By default, all the alarms are reported. |
Step 8 |
{ g709 | no g709 } otu threshold {sd-ber | sf-ber | sm-tca} value
Router(config-controller)# g709 odu threshold sd-ber 3 |
Set the threshold value to detect section monitoring signal degrade or signal failure alerts. |
Step 9 |
{ g709 | no g709 } odu threshold { pm-tca | sd-ber | sf-ber } value
Router(config-controller)# g709 odu threshold sd-ber 3 |
Sets the ber threshold limit to t_value power of ten. |
Step 10 |
{ g709 | no g709 } otu overhead tti{ expected | sent } { ascii | hex } tti-string
Router(config-controller)# g709 otu overhead tti expected ascii tti_new |
Specifies the trail trace identifier for otu level. |
Step 11 |
{ g709 | no g709 } odu overhead tti{ expected | sent } { ascii | hex } tti-string
Router(config-controller)# g709 odu overhead tti expected ascii tti_new |
Specifies the trail trace identifier for odu level. |
Step 12 |
no shut
Router(config-controller)# no shut |
Sets the controller to no shutdown mode. |
Step 13 |
end
Router(config-controller)# end |
Ends the session. |
Note You need to shutdown the interface using shut command before changing the FEC mode to EFEC.
Router#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)#controller dwdm 4/21
Router(config-controller)#shut
Router(config-controller)#g709 fec enhanced
Router(config-controller)#g709 otu report los
Router(config-controller)#no g709 otu report lof
Router(config-controller)#no g709 otu threshold sm-tca
Router(config-controller)#g709 odu threshold sd-ber 3
Router(config-controller)#no shut
Router(config-controller)#end
Verification
Use the show controllers command to verify the configuration for alarm assertion.
Router#show controllers dwdm 4/21
Controller dwdm 4/2, is up (no shutdown)
Q > 6.45 Q Margin > 7.52 DBQ
Alarm reporting enabled for: LOS LOF LOM OTU-AIS OTU-IAE OTU-BDI ODU-AIS ODU-OCI ODU-LCK ODU-BDI ODU-PTIM ODU-BIP Alert reporting enabled for: OTU-SM-TCA ODU-SD-BER ODU-SF-BER ODU-PM-TCA BER thresholds: ODU-SF = 10e-3 ODU-SD = 10e-6 TCA thresholds: SM = 10e-3 PM = 10e-3
OTU TTI Sent String ASCII: Tx TTI Not Configured
OTU TTI Received String ASCII:
OTU TTI Received String HEX : 0000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000
000000000000000000000000000000O OTU TTI Expected String ASCII: Exp TTI Not Configured
ODU TTI Sent String ASCII: Tx TTI Not Configured
ODU TTI Received String ASCII:
ODU TTI Received String HEX : 0000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000
000000000000000000000000000000 ODU TTI Expected String ASCII: Exp TTI Not Configured
Wanphy Alarm Reports
Enable wanphy alarm reporting on ES + line cards by using the command: wanphy report-alarm. The default configuration is applicable to the reporting of LOF, LOP, and LOS alarms.
However, you can include the following report-alarms in the configuration to enable them.
|
|
|
Section |
LOF and LOS |
Line |
AIS and RDI |
Path |
AIS, REI, LOP, and PLM |
WIS |
SEF, LCD-P, FELCD-P, and FEAIS-P |
Configuring Wanphy Alarm Reporting
Use the following steps to configure WANPHY alarm reporting.
| |
|
|
Step 1 |
enable |
Enables privileged EXEC mode.
- Enter your password if prompted.
|
Step 2 |
configure terminal |
Enters global configuration mode |
Step 3 |
Controller wanphy slot/port
Example: SUP-HA(config)#controller wanphy 7/2
|
Enters the controller configuration mode. The slot and port numbers specify the location of the interface. |
Step 4 |
wanphy
Example: SUP-HA(config-controller)#wanphy
|
Configures the wanphy controller processes |
Step 5 |
report-alarm { default | line | path | section | wis }
Example: SUP-HA(config-controller)#wanphy report-alarm wis
|
Configures wanphy alarm reporting |
Step 6 |
exit |
Exits the interface configuration mode |
Wanphy Alarms Configuration Example
Enter configuration commands, one per line. End with CNTL/Z.
SUP-HA(config)#controller wanphy ?
<7-8> Controller slot number
SUP-HA(config)#controller wanphy 7?
SUP-HA(config)#controller wanphy 7/?
<1-4> Controller unit number
SUP-HA(config)#controller wanphy 7/2 ?
SUP-HA(config)#controller wanphy 7/2
SUP-HA(config-controller)#wanphy report-alarm
Wanphy Alarms Report Example
Sample Report on Wanphy Alarms Declared or Cleared
Use the show running-config command to view the wanphy alarms that are configured to be reported. Use the show logging command to view the alarms that are declared or cleared.
SUP-HA#show running-config | i report
Enter configuration commands, one per line. End with CNTL/Z.
SUP-HA(config)#controller wanphy 7/2
SUP-HA(config-controller)#wanphy report-alarm path
SUP-HA(config-controller)#wanphy report-alarm section
*Feb 4 05:51:33.378: %WANPHY-4-WANALARM: TenGigabitEthernet7/2: WLOS declared
SUP-HA(config-controller)#wanphy report-alarm wis
SUP-HA(config-controller)#
*Feb 4 05:51:43.378: %WANPHY-4-WANALARM: TenGigabitEthernet7/2: SER declared
SUP-HA#show running-config | i report
*Feb 4 05:52:07.154: %SYS-5-CONFIG_I: Configured from console by console
wanphy report-alarm section
*Feb 4 05:51:33.378: %WANPHY-4-WANALARM: TenGigabitEthernet7/2: WLOS cleared
Configuring Tunable DWDM
The DWDM wavelengths of DWDM-XFP-C (DWDM XFP tunable) module on the Cisco 7600-ES+ line card is tunable. You can configure the DWDM ITU wavelengths using the itu channel command in the interface configuration mode.
The following table contains the wavelength mapping information for DWDM-XFP-C.
Table 10-1 DWDM-XFP-C Wavelength Mapping
|
|
|
|
1 |
191.95 |
1561.83 |
2 |
192.00 |
1561.42 |
3 |
192.05 |
1561.01 |
4 |
192.10 |
1560.61 |
5 |
192.15 |
1560.20 |
6 |
192.20 |
1559.79 |
7 |
192.25 |
1559.39 |
8 |
192.30 |
1558.98 |
9 |
192.35 |
1558.58 |
10 |
192.40 |
1558.17 |
11 |
192.45 |
1557.77 |
12 |
192.50 |
1557.36 |
13 |
192.55 |
1556.96 |
14 |
192.60 |
1556.55 |
15 |
192.65 |
1556.15] |
16 |
192.70 |
1555.75 |
17 |
192.75 |
1555.34 |
18 |
192.80 |
1554.94 |
19 |
192.85 |
1554.54 |
20 |
192.90 |
1554.13 |
21 |
192.95 |
1553.73 |
22 |
193.00 |
1553.33 |
23 |
193.05 |
1552.93 |
24 |
193.10 |
1552.52 |
25 |
193.15 |
1552.12 |
26 |
193.20 |
1551.72 |
27 |
193.25 |
1551.32 |
28 |
193.30 |
1550.92 |
29 |
193.35 |
1550.52 |
30 |
193.40 |
1550.12 |
31 |
193.45 |
1549.72 |
32 |
193.50 |
1549.32 |
33 |
193.55 |
1548.91 |
34 |
193.60 |
1548.51 |
35 |
193.65 |
1548.11 |
36 |
193.70 |
1547.72 |
37 |
193.75 |
1547.32 |
38 |
193.80 |
1546.92 |
39 |
193.85 |
1546.52 |
40 |
193.90 |
1546.12 |
41 |
193.95 |
1545.72 |
42 |
194.00 |
1545.32 |
43 |
194.05 |
1544.92 |
44 |
194.10 |
1544.53 |
45 |
194.15 |
1544.13 |
46 |
194.20 |
1543.73 |
47 |
194.25 |
1543.33 |
48 |
194.30 |
1542.94 |
49 |
194.35 |
1542.54 |
50 |
194.40 |
1542.14 |
51 |
194.45 |
1541.75 |
52 |
194.50 |
1541.35 |
53 |
194.55 |
1540.95 |
54 |
194.60 |
1540.56 |
55 |
194.65 |
1540.16 |
56 |
194.70 |
1539.77 |
57 |
194.75 |
1539.37 |
58 |
194.80 |
1538.98 |
59 |
194.85 |
1538.58 |
60 |
194.90 |
1538.19 |
61 |
194.95 |
1537.79 |
62 |
195.00 |
1537.40 |
63 |
195.05 |
1537.00 |
64 |
195.10 |
1536.61 |
65 |
195.15 |
1536.22 |
66 |
195.20 |
1535.82 |
67 |
195.25 |
1535.43 |
68 |
195.30 |
1535.04 |
69 |
195.35 |
1534.64 |
70 |
195.40 |
1534.25 |
71 |
195.45 |
1533.86 |
72 |
195.50 |
1533.47 |
73 |
195.55 |
1533.07 |
74 |
195.60 |
1532.68 |
75 |
195.65 |
1532.29 |
76 |
195.70 |
1531.90 |
77 |
195.75 |
1531.51 |
78 |
195.80 |
1531.12 |
79 |
195.85 |
1530.72 |
80 |
195.90 |
1530.33 |
81 |
195.95 |
1529.94 |
82 |
196.00 |
1529.55 |
Summary Steps
1. enable
2. configure terminal
3. interface tengigabitethernet slot/port
4. itu channel number
Detailed Steps.
| |
|
|
Step 1 |
enable
|
Enables privileged EXEC mode. If prompted, enter your password. |
Step 2 |
configure terminal
Router# configure terminal |
Enters global configuration mode. |
Step 3 |
interface tengigabitethernet slot/port Router(config)# interface tengigabitethernet 4/11 |
Specifies the Ten Gigabit Ethernet interface to configure, where: slot/port—Specifies the location of the interface. |
Step 4 |
itu channel number
Router(config-if)# itu channel 28 |
Sets the ITU channel. number - Specifies the ITU channel number. The acceptable values are from 1 to 82. |
Verification
In this example show idprom interface command checks the ITU configuration:
Router # configure terminal
Router(config)# interface TenGigabitEthernet 4/11
Router(config-if)#itu channel 28
Router# show running-config interface TenGigabitEthernet 4/11
Current configuration : 114 bytes
interface TenGigabitEthernet4/11
ip address 5.5.5.5 255.255.255.0
transport-mode otn bit-transparent opu1e
Router# show idprom interface TenGigabitEthernet 4/11 detail
Hexadecimal dump of TRANSCEIVER SEPROM :
000: 0C 00 49 00 F8 00 46 00 FB 00
010: 00 00 00 00 00 00 00 00 A6 04
020: 09 C4 8C A0 13 88 9B 83 0F 8D
030: 62 1F 18 A6 13 94 00 0A 0C 5A
040: 00 10 00 18 FF E8 00 0C FF F4
050: 00 00 00 00 00 00 00 00 00 00
060: 00 BF 25 1C 00 C4 00 00 01 F4
070: 00 00 00 00 00 00 00 00 00 00
080: 00 00 00 00 BE 20 00 00 00 00
090: 00 00 00 00 00 00 20 F3 00 00
100: 00 00 00 00 00 00 00 00 00 00
110: A2 B8 00 15 00 00 00 00 00 00 <<See byte 113, the hexa decimal equivalent for ITU channel 21>>
120: 00 00 00 00 00 00 00 01
Performance Monitoring on DWDM Controllers
Performance monitoring (PM) on DWDM controllers allows you to gather, store, set thresholds for, and report performance data for early detection of problems. Thresholds are used to set error levels for each performance monitoring parameter. During the accumulation cycle, if the current value of a performance monitoring parameter reaches or exceeds its corresponding threshold value, a threshold crossing alert (TCA) is generated. The TCAs provide early detection of performance degradation.
Performance monitoring statistics are accumulated on a 15-minute basis, synchronized to the start of each quarter-hour. They are also accumulated on a daily basis starting at midnight. Historical counts are maintained for thirty-three 15-minute intervals and two daily intervals.
The Cisco 7600 DWDM controller performs the following monitoring tasks:
- Retrieves performance monitoring transmission degradation counts and statistics defined in Table 10-2 .
- Maintains performance monitoring parameter counts and checks against configured threshold values.
- Generates performance monitoring related threshold crossing alerts (TCA).
- Provides performance monitoring numbers to network engineering managers.
Table 10-2 lists the performance monitoring parameters.
Table 10-2 Cisco 7600 DWDM Performance Monitoring Parameters
|
|
|
BBE-PM |
Path monitoring background block error (BBE-PM) indicates the number of background block errors recorded in the optical transport network (OTN) path during the PM time interval. |
BBE-SM |
Section monitoring background block error (BBE-SM) indicates the number of background block errors recorded in the OTN section during the PM time interval. |
BBER-PM |
Path monitoring background block errors ratio (BBER-PM) indicates the background block errors ratio recorded in the OTN path during the PM time interval. |
BBER-SM |
Section monitoring background block errors ratio (BBER-SM) indicates the background block errors ratio recorded in the OTN section during the PM time interval. |
BIEC |
Bit errors corrected (BIEC) indicates the number of bit errors corrected in the DWDM trunk line during the PM time interval. |
ES-PM |
Path monitoring errored seconds (ES-PM) indicates the errored seconds recorded in the OTN path during the PM time interval. |
ESR-PM |
Path monitoring errored seconds ratio (ESR-PM) indicates the errored seconds ratio recorded in the OTN path during the PM time interval. |
ESR-SM |
Section monitoring errored seconds ratio (ESR-SM) indicates the errored seconds ratio recorded in the OTN section during the SM time interval. |
ES-SM |
Section monitoring errored seconds (ES-SM) indicates the errored seconds recorded in the OTN section during the PM time interval. |
FC-PM |
Path monitoring failure counts (FC-PM) indicates the failure counts recorded in the OTN path during the PM time interval. |
FC-SM |
Section monitoring failure counts (FC-SM) indicates the failure counts recorded in the OTN section during the PM time interval. |
LBC-MIN |
Laser bias current minimum (LBC-MIN) is the minimum laser bias current. |
LBC-AVG |
Laser bias current average (LBC-AVG) is the average laser bias current. |
LBC-MAX |
Laser bias current maximum (LBC-MAX) is the maximum laser bias current. |
OPT-AVG |
Average transmit optical power (dBm). |
OPT-MAX |
Maximum transmit optical power (dBm). |
OPT-MIN |
Minimum transmit optical power (dBm). |
OPR-AVG |
Optical power average (OPR-AVG) is the measure of average optical power on the unidirectional port. |
OPR-MAX |
Optical power maximum (OPR-MAX) is the measure of maximum value of optical power on the unidirectional port. |
OPR-MIN |
Optical power minimum (OPR-MIN) is the measure of minimum value of optical power on the unidirectional port. |
SES-PM |
Path monitoring severely errored seconds (SES-PM) indicates the severely errored seconds recorded in the OTN path during the PM time interval. |
SES-SM |
Section monitoring severely errored seconds (SES-SM) indicates the severely errored seconds recorded in the OTN section during the PM time interval. |
Configuring Performance Monitoring on DWDM Controllers
This section describes how to configure and verify performance monitoring on DWDM controllers.
The controller dwdm command is supported only on the following cards:
- 76-ES+XT-2TG3CXL
- 76-ES+XT-4TG3CXL
- 76-ES+T-2TG
- 76-ES+T-4TG
- 76-ES+XC-20G3C
- 76-ES+XC-20G3CXL
- 76-ES+XC-40G3C
- 76-ES+XC-40G3CXL
Note Before you configure performance monitoring using the pm command, you should change the transport mode to transport-mode otn.
SUMMARY STEPS
1. configure terminal
2. controller dwdm instance
3. pm { 15-min | 24-hour } fec threshold { ec-bits | uc-words } threshold
4. pm { 15-min | 24-hour } optics threshold { lbc | opr | opt } { max | min } threshold
5. pm { 15-min | 24-hour } otn threshold otn-parameter threshold
6. pm { 15-min | 24-hour } fec report { ec-bits | uc-words } enable
7. pm { 15-min | 24-hour } optics report { lbc | opr | opt } { max-tca | min-tca } enable
8. pm { 15-min | 24-hour } otn report otn-parameter enable
9. end
10. show controllers dwdm instance pm history [ 15-min | 24-hour | fec | optics | otn ]
11. show controllers dwdm instance pm interval { 15-min | 24-hour } [ fec | optics | otn ]
DETAILED STEPS
|
|
|
Step 1 |
configure terminal
router# configure terminal |
Enters global configuration mode. |
Step 2 |
controller dwdm instance
router(config)# controller dwdm 4/1 |
Specifies the DWDM controller name in the notation module/port and enters the DWDM configuration mode. |
Step 3 |
pm { 15-min | 24-hour } fec threshold { ec-bits | uc-words } threshold
router(config-controller)# pm 15-min fec threshold ec-bits 900 router(config-controller)# pm 15-min fec threshold uc-words 800 |
Configures a performance monitoring threshold for specific parameters on the FEC layer. |
Step 4 |
pm { 15-min | 24-hour } optics threshold { lbc | opr | opt } { max | min } threshold
router(config-controller)# pm 15-min optics threshold opt max 900 router(config-controller)# pm 15-min optics threshold lbc min 700 |
Configures a performance monitoring threshold for specific parameters on the optics layer. |
Step 5 |
pm {
15-min |
24-hour }
otn threshold
otn-parameter
threshold
router(config-controller)# pm 15-min otn threshold bbe-pm-ne 800 router(config-controller)# pm 15-min otn threshold es-sm-fe 900 |
Configures a performance monitoring threshold for specific parameters on the optical transport network (OTN) layer. OTN parameters are as follows:
- bbe-pm-fe —Far-end path monitoring background block errors (BBE-PM)
- bbe-pm-ne —Near-end path monitoring background block errors (BBE-PM)
- bbe-sm-fe —Far-end section monitoring background block errors (BBE-SM)
- bbe-sm-ne —Near-end section monitoring background block errors (BBE-SM)
- bber-pm-fe —Far-end path monitoring background block errors ratio (BBER-PM)
- bber-pm-ne —Near-end path monitoring background block errors ratio (BBER-PM)
- bber-sm-fe —Far-end section monitoring background block errors ratio (BBER-SM)
- bber-sm-ne —Near-end section monitoring background block errors ratio (BBER-SM)
- es-pm-fe —Far-end path monitoring errored seconds (ES-PM)
- es-pm-ne —Near-end path monitoring errored seconds (ES-PM)
- es-sm-fe —Far-end section monitoring errored seconds (ES-SM)
- es-sm-ne —Near-end section monitoring errored seconds (ES-SM)
- esr-pm-fe —Far-end path monitoring errored seconds ratio (ESR-PM)
- esr-pm-ne —Near-end path monitoring errored seconds ratio (ESR-PM)
- esr-sm-fe —Far-end section monitoring errored seconds ratio (ESR-SM)
- esr-sm-ne —Near-end section monitoring errored seconds ratio (ESR-SM)
- fc-pm-fe —Far-end path monitoring failure counts (FC-PM)
- fc-pm-ne —Near-end path monitoring failure counts (FC-PM)
- fc-sm-fe —Far-end section monitoring failure counts (FC-SM)
- fc-sm-ne —Near-end section monitoring failure counts (FC-SM)
|
|
|
- ses-pm-fe —Far-end path monitoring severely errored seconds (SES-PM)
- ses-pm-ne —Near-end path monitoring severely errored seconds (SES-PM)
- ses-sm-fe —Far-end section monitoring severely errored seconds (SES-SM)
- ses-sm-ne —Near-end section monitoring severely errored seconds (SES-SM)
- sesr-pm-fe —Far-end path monitoring severely errored seconds ratio (SESR-PM)
- sesr-pm-ne —Near-end path monitoring severely errored seconds ratio (SESR-PM)
- sesr-sm-fe —Far-end section monitoring severely errored seconds ratio (SESR-SM)
- sesr-sm-ne —Near-end section monitoring severely errored seconds ratio (SESR-SM)
- uas-pm-fe —Far-end path monitoring unavailable seconds (UAS-PM)
- uas-pm-ne —Near-end path monitoring unavailable seconds (UAS-PM)
- uas-sm-fe —Far-end section monitoring unavailable seconds (UAS-SM)
- uas-sm-ne —Near-end section monitoring unavailable seconds (UAS-SM)
|
Step 6 |
pm { 15-min | 24-hour } fec report { ec-bits | uc-words } enable
router(config-controller)# pm 15-min fec report ec-bits enable router(config-controller)# pm 15-min fec report uc-words enable |
Configures threshold crossing alert (TCA) generation for specific parameters on the FEC layer. |
Step 7 |
pm { 15-min | 24-hour } optics report { lbc | opr | opt } { max-tca | min-tca } enable
router(config-controller)# pm 15-min optics report opt enable router(config-controller)# pm 15-min optics report lbc enable |
Configures TCA generation for specific parameters on the optics layer. |
Step 8 |
pm {
15-min |
24-hour }
otn report
otn-parameter
enable
router(config-controller)# pm 15-min otn report bbe-pm-ne enable router(config-controller)# pm 15-min otn report es-sm-fe enable |
Configures TCA generation for specific parameters on the optical transport network (OTN) layer. OTN parameters are as shown in Step 5. |
Step 9 |
end
router(config-controller)# end |
Saves configuration changes. |
Step 10 |
show controllers dwdm instance pm history [ 15-min | 24-hour | fec | optics | otn ]
router# show controllers dwdm 4/1 pm history 24-hour fec router# show controllers dwdm 4/1 pm history |
Displays all of the performance measurement and TCA generation information for the DWDM controller. |
Step 11 |
show controllers dwdm instance pm interval { 15-min | 24-hour } [ fec | optics | otn ]
router# show controllers dwdm 4/1 pm interval 24-hour 0 router# show controllers dwdm 4/1 pm interval 15-min optics 1 |
Displays performance measurement and TCA generation information for a specific interval. |
Configuration Examples
This example shows how to configure performance monitoring for the optics parameters:
router(config)# controller dwdm 4/21
router(config-controller)# pm 15-min optics threshold opt max 2000000
router(config-controller)# pm 15-min optics threshold opt min 200
router(config-controller)# pm 15-min optics threshold lbc max 3000000
router(config-controller)# pm 15-min optics threshold lbc min 300
router(config-controller)# pm 15-min optics threshold opr max 4000000
router(config-controller)# pm 15-min optics threshold opr min 400
router(config-controller)# pm 15-min optics report opt max-tca enable
router(config-controller)# pm 15-min optics report opt min-tca enable
router(config-controller)# pm 15-min optics report opr max-tca enable
router(config-controller)# pm 15-min optics report opr min-tca enable
router(config-controller)# pm 15-min optics report lbc max-tca enable
router(config-controller)# pm 15-min optics report lbc min-tca enable
router(config-controller)# exit
Verification
Verify the configuration by using the show controllers dwdm command.
This example displays the performance measurement and TCA generation information for a specific interval:
router# show controllers dwdm 4/21 pm interval 24-hour 1
g709 OTN in interval 1 [HH:MM:SS Month Date Year – Month Date Year]
ES-SM : 0 Threshold : 0 TCA(enable) : NO
ESR-SM : 0 Threshold : 0 TCA(enable) : NO
SES-SM : 0 Threshold : 0 TCA(enable) : NO
SESR-SM : 0 Threshold : 0 TCA(enable) : NO
UAS-SM : 0 Threshold : 0 TCA(enable) : NO
BBE-SM : 0 Threshold : 0 TCA(enable) : NO
BBER-SM : 0 Threshold : 0 TCA(enable) : NO
FC-SM : 0 Threshold : 0 TCA(enable) : NO
ES-PM : 0 Threshold : 0 TCA(enable) : NO
ESR-PM : 0 Threshold : 0 TCA(enable) : NO
SES-PM : 0 Threshold : 0 TCA(enable) : NO
SESR-PM : 0 Threshold : 0 TCA(enable) : NO
UAS-PM : 0 Threshold : 0 TCA(enable) : NO
BBE-PM : 0 Threshold : 0 TCA(enable) : NO
BBER-PM : 0 Threshold : 0 TCA(enable) : NO
FC-PM : 0 Threshold : 0 TCA(enable) : NO
g709 FEC in the current interval []
EC-BITS : 0 Threshold : 0 TCA(enable) : NO
UC-WORDS : 0 Threshold : 0 TCA(enable) : NO
Optics in the current interval []
MIN AVG MAX Threshold TCA Threshold TCA
(min) (enable) (max) (enable)
LBC[mA ] :0 0 0 0 NO 0 NO
OPT[dBm] :0 0 0 0 NO 0 NO
OPR[dBm] :0 0 0 0 NO 0 NO
Troubleshooting Tips
Table 10-3 Troubleshooting Solutions for the Performance Monitoring Feature
|
|
|
Not able to disable the logging of ODU alarms on the console. |
Use the no g709 odu report command in DWDM configuration mode to disable the logging.
Router(config-controller)#
no g709 odu report
For disabling the logging of OTU alarms, use the no g709 otu report command in DWDM configuration mode. |
IPoDWDM Proactive Protection
Proactive Protection (PP) is a mechanism that uses Bit Error Rate (BER) from the optical drivers to detect the failure of signal transmission before it actually occurs. It also corrects the errors introduced during the transmission, or due to a degrading signal.
In IPoDWDM, the Forward Error Correction (FEC) circuitry resides on a router line card. Therefore, the router has the visibility into the BER statistics before the FEC mechanism corrects these errors. This allows the router to realize that the working path is degrading beyond a reasonable point (a threshold you can configure). At this point, the router starts its protection logic and establishes a protection path while the traffic continues to flow on the degrading working path. Depending on the failure mode, the router may have ten or even hundreds of milliseconds to move away from the working path before the FEC mechanism fails.
Proactive Protection is required because the prevailing video encoding is based on MPEG-2 and MPEG-4 standards, which uses differential coding of the frame with reference to a full frame that is only sent infrequently. When this frame (called the I-frame) is lost, a large number of users may experience a visible outage on their screens, lasting up to several seconds. High resolution encoding schemes, such as MPEG-4, are actually more prone to longer outages because I-frames are less common in the data stream. For this reason, it is important to minimize the packet loss even below the SONET or SDH benchmark, ideally aiming for zero packet loss.
Restrictions
Following restrictions apply for proactive protection:
- Only the following line cards support this feature:
– 76-ES+XT-2TG3CXL
– 76-ES+XT-4TG3CXL
– 76-ES+T-2TG
– 76-ES+T-4TG
– 76-ES+XC-20G3C
– 76-ES+XC-20G3CXL
– 76-ES+XC-40G3C
– 76-ES+XC-40G3CXL
- The polling interval of 10ms is not guaranteed in IOS. The actual polling intervals vary depending on the load on CPU.
- You can expect a time lag while triggering or reverting the proactive protection.
- Even though the configuration range offered for the thresholds is from 9E-3 to 1E-9, the working range is only from 9E-4 to 1E-7. Since the values below this range are negligible, it is rounded off to 0. The values above this range are too high, and can cause the interface to be unstable.
- If you enable proactive protection, and shut down the primary interface, the Loss of Signal Reporting (LOS) will be sent to the other end. Because of this, the PP FSM goes to local state. But on the local end, where an OTU-BDI is declared, the FSM does not go to remote failed state. Because of this, the FSM states will not be in sync on both sides.
Configuring Proactive Protection
Proactive protection involves enabling the protection mechanism, configuring the threshold, polling of the fast re-route (FRR) pointers, and triggering the FRR.
Complete the following steps:
SUMMARY STEPS
1. configure terminal
2. controller dwdm slot port
3. proactive enable
4. proactive trig-threshold x-coeff y-power
5. proactive trig-window window
6. proactive rvrt-threshold x-coeff y-power
7. proactive rvrt-window window
8. end
DETAILED STEPS
|
|
|
Step 1 |
configure terminal
Router# config terminal |
Enters global configuration mode. |
Step 2 |
controller dwdm slot port
Router(config)# controller dwdm 0/1 |
Specifies the DWDM controller and enters DWDM controller mode. |
Step 3 |
proactive enable
Router(config-controller)# proactive enable |
Enables automatic triggering of FEC-FRR. |
Step 4 |
proactive trig-threshold x-coeff y-power
Router(config-controller)# proactive trig-threshold 1 5 |
Configures the trigger threshold of FEC-FRR in the form of x E- y. |
Step 5 |
proactive trig-window window
Router(config-controller)# proactive trig-window 2045 |
Configures the trigger window (in milliseconds) in which FRR may be triggered. |
Step 6 |
proactive rvrt-threshold x-coeff y-power
Router(config-controller)# proactive rvrt-threshold 1 6
|
Configures the revert threshold (in the form of x E- y) to trigger reverting from the FEC-FRR route back to the original route. |
Step 7 |
proactive rvrt-window window
Router(config-controller)# proactive rvrt-window 20345 |
Configures the revert window in which reverting from the FEC-FRR route back to the original route is triggered. |
Step 8 |
end
Router(config-controller)# end |
Saves configuration changes. |
Configuration Examples
This example shows how to configure automatic triggering of FEC-FRR:
Router# configure terminal
Router(config)# controller dwdm 0/1
Router(config-controller)# proactive enable
Router(config-controller)# proactive trig-threshold 1 5
Router(config-controller)# proactive trig-window 2045
Router(config-controller)# proactive rvrt-threshold 1 6
Router(config-controller)# proactive rvrt-window 20345
Router(config-controller)# end
Verification
Verify the configuration by using the show controllers dwdm proactive status command.
router#show controllers dwdm 3/1 proactive status
Proactive Protection Status: ON
Transport admin-state: IS
Trigger integration window: 2000
Revert integration window: 3000
Troubleshooting Tips
Table 10-4 Troubleshooting Solutions for the Proactive Protection Feature.
|
|
|
How do I verify whether or not the proactive protection is triggered? |
Use the show controller dwdm 3/1 proactive status command. In the command output, check if the APS bytes on the local side is 0xAF (sent), and the remote end APS received is 0xAF. Also, use the show proactive infrastructure fsm command to check whether or not the FSM state is in local or remote failed state. For further debugging, run the debug proactive infrastructure fsm command. You should run the debug command from the line card. In the debug output, the Tx APS bytes show the various state of FSM:
- 0x0F --> FSM is in Normal state.
- 0xAF --> FRR is triggered by PP. FSM is in Local Failed state.
- 0xEF --> FSM is in Local Maintenance state.
|
How do I verify whether or not the FRR is triggered correctly? |
Check the output of the show mpls traffic-eng fast-reroute database command. This example displays the output:
router#
show mpls traffic-eng fast-reroute database
P2P Headend FRR information:
Protected tunnel In-label Out intf/label FRR intf/label Status
--------------------------- -------- -------------- -------------- ------
Tunnel1 Tun hd Te3/1:implicit-n Tu2:implicit-nul Ready
P2P LSP midpoint frr information:
LSP identifier In-label Out intf/label FRR intf/label Status
--------------------------- -------- -------------- -------------- ------
P2MP Sub-LSP FRR information:
src_lspid[subid]->dst_tunid In-label Out intf/label FRR intf/label Status
--------------------------- -------- -------------- -------------- ------
* Sub-LSP identifier format: <TunSrc>_<LSP_ID>[SubgroupID]-><TunDst>_<Tun_ID>
Note: Sub-LSP identifier may be truncated.
Use 'detail' display for the complete key.
Please check the state of the backup tunnel. The backup tunnel in READY state indicates that the FE FRR is not triggered. The backup tunnel in ACTIVE state indicates that the FE TRR is triggered. |
Virtual Transponder on Cisco 7600 IPoDWDM Line Card
Virtual transponder feature allows you to configure the L1 parameters of a Cisco 7600 IPoDWDM line card from an ONS 15454 MSTP Network Craft Terminal (CTC). Using this feature, you can monitor port status, and retrieve monitoring points such as Optical Power, Q Factor, BER, Alarm Status, and so on.
These cards support virtual transponder on the Cisco 7600:
- 76-ES+XT-2TG3CXL
- 76-ES+XT-4TG3CXL
- 76-ES+T-2TG
- 76-ES+T-4TG
- 76-ES+XC-20G3C
- 76-ES+XC-20G3CXL
- 76-ES+XC-40G3C
- 76-ES+XC-40G3CXL
Configuring Virtual Transponder
Configuring virtual transponder involves provisioning a control channel and data link on both ONS15454 and Cisco 7600. Configuration involves these steps:
- Node authentication
- SSH server configuration
- Provisional Patch Code (PPC) local and remote node configuration
You need to configure PPC through Cisco Transport Controller (CTC) on the ONS15454 because Cisco 7600 does not support PPC. For detailed configuration information, see the ONS documentation at the following URL:
http://www.cisco.com/en/US/docs/optical/15000r9_2/dwdm/reference/guide/454d92_optcircuitref.html#wp373015
http://www.cisco.com/en/US/docs/optical/15000r9_2/dwdm/procedure/guide/454d92_opticalchannelcirc.html#wp656975
Feedback