Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

Container Interfaces for APS on SONET Links Overview

 

The Junos OS supports container interfaces for APS on SONET links. Physical interfaces and logical interfaces remain up on switchover, and their APS parameters are auto-copied from the container interface to the member links. See Understanding Container Interfaces for more information.

Container interfaces support the following features:

  • Cisco HDLC or PPP encapsulation methods.

  • Unpaired groups.

  • Bidirectional APS.

  • Non-container and container-based APS on the same system.

  • Use of any combination of (nonchannelized) SONET interfaces installed on the same router.

To configure a container interface, you must first create the number of container devices that you require. You can create up to a maximum of 128 container interfaces per router using the device-count statement at the [edit chassis container-devices] hierarchy level.

To configure each container interface, you must assign two SONET interfaces (so-fpc/pic/port) using the container-list cin statement, and specify the member-interface-speed speed and container-options for each SONET interface.

Within each of the two SONET interfaces' container options, you must set one container-type as primary (corresponding to an APS working circuit) and the other as standby (corresponding to an APS protect circuit). For each SONET interface, you can also use the allow-configuration-override statement to allow the physical configuration of a member link to override the container configuration.