Configuring Container Interfaces for APS on SONET Links
Configuring Container Interfaces on SONET Links
To configure a container interface on SONET links, you should perform the following:
- 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.
- Configure each container interface, here, 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.
The following procedure explains configuring a container interface on SONET links in detail.
To configure a container interface on SONET links:
- In configuration mode, go to the edit chassis container-devices hierarchy level.[edit]user@host# edit chassis container-devices
- Specify the total number of container interfaces (up to
128) to create using the device-count number statement.[edit chassis container-devices]user@host# set device-count number
Note: You can create more container interfaces later if required, up to 128 (total). The resulting container interfaces are designated sequentially from ci0 up to a maximum of ci127, depending on the device-count number specified. SONET interfaces can be assigned to any container interface cin.
- Configure the container interface parameters for a specified
container cin as follows:
- Specify the container interface using the numbered identifier cin:[edit interfaces]user@host# edit cin
- Specify the container interface encapsulation as cisco-hdlc or ppp:[edit interfaces cin]user@host# set encapsulation (cisco-hdlc | ppp)
- Specify the container options container-type as aps; a SONET interface is required for APS selection:[edit interfaces cin]user@host# set container-options container-type aps
- Specify the container interface member-interface type as sonet:[edit interfaces cin]user@host# set interfaces cin container-options member-interface-type sonet
- Specify the container member-interface-speed speed to match the specified installed SONET interface
links; the available values are OC3, OC12, OC48, OC192, OC768, or mixed.
The member-interface-speed speed statement
setting applies to all SONET member interfaces of the specified container cin.[edit interfaces cin]user@host# set interfaces cin container-options member-interface-type sonet member-interface-speed speed
- Specify the container interface's unit number, family,
IP address, and mask:[edit interfaces cin] user@host# set interfaces cin unit number family inet address ip-address/mask
- Specify the container interface using the numbered identifier cin:
- Configure each of the required two SONET interfaces as
follows:
- Specify the SONET interfaces and their container options; including the container-list, identified by its cin.
- Specify the container-type as primary (corresponding to an APS working-circuit)
or standby (corresponding to an APS
protect-circuit).
For example, setting so-0/0/0 as the primary and so-0/0/1 as the standby SONET interfaces for container interface ci0:
[edit]user@host# edit interfaces so-0/0/0 # Enter configuration mode for interface so-0/0/0
[edit interfaces so-0/0/0]user@host# set container-options container-list ci0 primary # Set so-0/0/0 as APS primary interface
[edit interfaces so-0/0/0]user@host# top
[edit]user@host# edit interfaces so-0/0/1 # Enter configuration mode for interface so-0/0/1
[edit interfaces so-0/0/1]user@host# set container-options container-list ci0 standby # Set so-0/0/1 as APS standby interfaceOptionally, you can set the allow-configuration-override statement to allow the physical configuration of a member link to override the container configuration:
[edit interfaces so-0/0/1]user@host# set container-options container-list ci0 standby allow-configuration-override
Displaying Container Interface Configuration
Purpose
To display a container interface.
Action
To display a container interface configuration in SONET/SDH where the device-count is 1 with the so-1/0/2 interface as primary and the so-1/0/3 interface as secondary, and the encapsulation is set to cisco-hdlc.
- In configuration mode, go to the [edit chassis] hierarchy level.[edit]user@host# edit chassis
- Issue the show operational mode command.[edit chassis]user@host# show
- The following output is displayed.
container-devices { device-count 1; }
- In configuration mode, go to the [edit interfaces] hierarchy level.[edit]user@host# edit interfaces
- Issue the show operational mode command.[edit chassis]user@host# show
- The following output is displayed.
so-1/0/2 { container-options { container-list ci0; primary; } } so-1/0/3 { container-options { container-list ci0; standby; } } ci0 { encapsulation cisco-hdlc; container-options { container-type aps { member-interface-type sonet { member-interface-speed mixed; } } } unit 0 { family inet { address 192.168.11.1/24; } } }
Displaying the APS Container Interface Configuration
Purpose
Display the APS container interface configuration parameters.
Action
You can run the show aps operational mode command to display the APS container interface configuration.
user@host> show aps
Interface Group Circuit Intf state ci0 CONTAINER_ci0 Container enabled, up so-1/2/2 MEMBER_OF_ci0 Working enabled, up so-1/2/3 MEMBER_OF_ci0 Protect disabled, up