SONET/SDH Configuration Tasks

To configure SONET/SDH on a cOCx/STMx interface:

1. Select an interface.
2. Specify a clock source for the interface.
3. Specify that the mode be SDH, or accept the default mode, SONET.
4. (Optional) Assign a text description or an alias to the interface.
5. (Optional) Disable processing of SNMP link status information for the section and line layers of the interface.
6. Configure the path for the interface.
7. (Optional—not recommended) Overwrite the automatic setting for the path signal label (C2) byte.
8. (Optional) Enable processing of SNMP link status information for the path layer of the interface.
9. (Optional) Configure the router to use remote defect indications (RDIs) at the path layer to determine the operational status of a path.
10. (MPLS fast reroute over SONET/SDH interfaces) Specify the time duration after which the router sets an alarm when it records a defect at the path layer.
11. (MPLS fast reroute over SONET/SDH interfaces) Specify the time duration after which the router sets an alarm when it records a defect at the line or section layer.
12. Configure APS/MSP for the interface.

    For information about configuring APS/MSP, see Configuring APS/MSP in Configuring Unchannelized OCx/STMx Interfaces .

You must now configure the next layer on the interface: E1, T1, or E3. See T1/E1 Configuration Tasks or T3 Configuration Tasks.

clock source

• Use to configure the transmit clock source for the interface.
• For production networks, configure all STMx ports on the line module for internal chassis timing. You must also ensure that the chassis reference clock is of good quality — Stratum 3 or better, recovered either from a known good STM port or from one of the BITS inputs.
• Although the CLI enables you to specify the keywords internal module to use the line module’s internal clock, in a production network we recommend that you do not do this. Instead, specify the keywords internal chassis to use the router’s internal clock.
• For production networks, never specify the keyword line to use the line’s receive clock as the transmit clock. Although the CLI enables this configuration, it is not supported because jitter transfer is not compliant for this timing and because pointer adjustments takes place on the outgoing link.
• In a nonproduction network, you can configure some ports with internal clock sources and others with line clock sources. However, all ports with internal clock sources must use either the router’s clock or the module’s clock. You cannot configure some ports on the I/O module to use the router’s clock and others to use the module’s clock.
• To change the clock source of the ports on a cOC3/STM1 I/O module from the router’s clock to the module’s clock or vice versa, first change the clock source of all ports to the line setting, and then to the new internal clock setting.
• Example

  host1(config-controll)#clock source internal chassis

• Use the no version to revert to the default, line.
• See clock source.

controller sonet

• Use to select an interface on which you want to configure channelized SONET or SDH.
• Example

  host1(config)#controller sonet 4/0

• There is no no version.
• See controller sonet.

description

• Use to assign a text description or an alias to a channelized SONET interface.
• You can use this command to help you identify the interface and keep track of interface connections.
• The description or alias can be a maximum of 64 characters.
• Use the show controllers sonet command to display the text description.
• Example

  host1(config-controll)#description boston-sonet-interface

• Use the no version to remove the text description or alias.
• See description.

path

• Use to configure paths over channelized SONET and SDH interfaces.
• Specify the correct identifier for the type of interface. See Interface Types and Specifiers in JUNOSe Command Reference Guide for details of the syntax.
• Example for a cOC3/STM1 interface

  host1(config-controller)#path 2 oc1

• Example for a cOC12/STM4 interface in SONET mode

  host1(config-controller)#path 2 oc1 1/2

• Example for a cOC12/STM4 interface in SDH mode

  host1(config-controller)#path 2 stm1 2

• Use the no version to delete a SONET or SDH path.
• See path.

path description

• Use to assign a text description or an alias to a channelized SONET path.
• You can use this command to help you identify the interface and keep track of interface connections.
• The description or alias can be a maximum of 64 characters.
• Example

  host1(config-controll)#path 2 description westford

• Use the no version to remove the description.
• See path description.

path overhead c2

• Use to overwrite the automatic setting for the path signal label (C2) byte.
• By default, the value of the C2 byte for the path is determined by the layers configured above the SONET/SDH interface and set automatically. The E-series router sets this default value in accordance with RFC 2558. (See References.)

  Caution: Use this command only if you know that the automatic setting does not match the setting on the remote device. Otherwise, the remote device might send an unexpected value, and the router might lose data.

• Example

  host1(config-controll)#path 2 overhead c2 20

• Use the no version to restore the default setting, in which the value of the C2 byte is determined by the layers configured above the SONET/SDH interface.
• See path overhead c2.

path shutdown

• Use to disable a specified path.
• Paths are enabled by default.
• Example

  host1(config-controll)#path 2 shutdown

• Use the no version to restart a disabled path.
• See path shutdown.

path snmp trap link-status

• Use to enable SNMP link status processing for the path layer of the interface.
• The default is disabled.
• Example

  host1(config-controll)#path 2 snmp trap link-status

• Use the no version to disable SNMP link status processing.
• See path snmp trap link-status.

path trigger alarm prdi

• Use to configure the router to use remote defect indications (RDIs) at the path layer to determine the operational status of a path.
• Example

  host1(config-controll)#path 2 trigger alarm prdi

• Use the no version to restore the default setting, in which the software uses loss of pointer and AIS defects at the path layer to determine the operational status of a path.
• See path trigger alarm prdi.

path trigger delay

• Use to set the time duration after which the router sets an alarm when it records a defect at the path layer.
• Change this value from the default only when you are using MPLS fast reroute over a SONET/SDH interface.
  • Specify a value of 0 milliseconds if this interface does not use APS/MSP or if MPLS should have priority over APS/MSP.
  • Specify a value of at least 100 milliseconds if this interface uses APS/MSP and if APS/MSP should have priority over MPLS.
• Example

  host1(config-controll)#path 2 trigger delay msec 1000

• Use the no version to restore the default setting, 2500 milliseconds.
• See path trigger delay.

sdh

• Use to specify that the interface supports SDH.
• Example

  host1(config-controller)#sdh

• Use the no version to revert to SONET operation on this interface.
• See sdh.

snmp trap link-status

• Use to enable SNMP link status processing for the section and line layers of the interface.
• The default is enabled.
• Example

  host1(config-controll)#no snmp trap link-status

• Use the no version to disable SNMP link status processing.
• See snmp trap link-status.

trigger delay

• Use to set the time duration after which the router sets an alarm when it records a defect at the line or section layer.
• Change this value from the default only when you are using MPLS fast reroute over a SONET/SDH interface.
  • Specify a value of 0 milliseconds if the interface does not use APS/MSP or if MPLS should have priority over APS/MSP.
  • Specify a value of at least 100 milliseconds if this interface uses APS/MSP and if APS/MSP should have priority over MPLS.
• Example

  host1(config-controll)#trigger delay msec 1000

• Use the no version to restore the default setting, 2500 milliseconds.
• See trigger delay.

Copyright © 2008, Juniper Networks, Inc. All rights reserved. Trademark Notice.