[Contents] [Prev] [Next] [Index] [Report an Error]

Configuring Container Interfaces

JUNOS 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 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. 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.

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.

The following configuration steps are required:

Specify the total number of container interfaces (up to 128) to create using the device-count number statement at the [edit chassis container-devices] hierarchy level:[edit chassis container-devices] user@host# set device-count number
Configure the container interface parameters for a specified container cin as follows:
1. Specify the container interface using the numbered identifier cin:[edit interfaces] user@host# edit cin
2. Specify the container interface encapsulation as cisco-hdlc or ppp:[edit interfaces cin] user@host# set encapsulation (cisco-hdlc | ppp)
3. 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
4. Specify the container interface member-interface type as sonet:[edit interfaces cin] user@host# set interfaces cin container-options member-interface-type sonet
5. 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
6. 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
Configure each of the required two SONET interfaces as follows:
1. Specify the SONET interfaces and their container options; including the container-list, identified by its cin.
2. 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 config 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 config 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 interface
  Optionally, 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

Example Container Interface Configuration

The following snippet is an example container interface configuration:



[edit chassis]

container-devices {
device-count 1;
}
[edit interfaces]
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;
}


}


}

You can run the show aps command to display the APS container interface configuration, as follows:

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

[Contents] [Prev] [Next] [Index] [Report an Error]