Catalyst 6500 Series Switch SIP, SSC, and SPA Software Configuration Guide

Step 1 

Router(config)# interface atm slot/subslot/port

Enters interface configuration mode for the indicated port on the specified ATM SPA.

Step 2 

Router(config-if)# ip address address mask [secondary]

(Optional in some configurations) Assigns the specified IP address and subnet mask to the interface. Repeat the command with the optional secondary keyword to assign additional, secondary IP addresses to the port.

Step 3 

Router(config-if)# description string

(Optional) Assigns an arbitrary string, up to 80 characters long, to the interface. This string can identify the purpose or owner of the interface, or any other information that might be useful for monitoring and troubleshooting.

Step 4 

Router(config-if)# no shutdown

Enables the interface.

Repeat Step 1 through Step 4 for each port on the ATM SPA to be configured.

Step 5 

Router(config-if)# end

Exits interface configuration mode and returns to privileged EXEC mode.

Step 1 

Router(config)# interface atm slot/subslot/port

Enters interface configuration mode for the indicated port on the specified ATM SPA.

Step 2 

Router(config-if)# mtu bytes

(Optional) Configure the maximum transmission unit (MTU) size for the interface. The valid range for bytes is from 64 to 9216 bytes, with a default of 4470 bytes. As a general rule, do not change the MTU value unless you have a specific application need to do so.

Note If the IP MTU or MPLS MTU values are currently the same size as the interface MTU, changing the interface MTU size also automatically sets the IP MTU or MPLS MTU values to the same value.

Step 3 

Router(config-if)# ip mtu bytes

(Optional) Configures the MTU value, in bytes, for IP packets on this interface. The valid range for an ATM SPA is 64 to 9288, with a default value equal to the MTU value configured in Step 2.

Step 4 

Router(config-if)# mpls mtu bytes

(Optional) Configures the MTU value, in bytes, for MPLS-labeled packets on this interface. The valid range for an ATM SPA is 64 to 9216 bytes, with a default value equal to the MTU value configured in Step 2.

Note Repeat Step 1 through Step 4 for each interface port on the ATM SPA to be configured.

Step 5 

Router(config-if)# end

Exits interface configuration mode and returns to privileged EXEC mode.

Step 1 

Router(config)# interface atm slot/subslot/port

or

Router(config)# interface atm slot/subslot/port.subinterface

Enters interface or subinterface configuration mode for the indicated port on the specified ATM SPA.

Step 2 

Router(config-if)# ip address address mask

Assigns the specified IP address and subnet mask to the interface or subinterface.

Step 3 

Router(config-if)# atm tx-latency milliseconds

(Optional) Configures the default transmit latency for VCs on this ATM SPA interface. The valid range for milliseconds is from 1 to 200, with a default of 100 milliseconds.

Step 4 

Router(config-if)# pvc [name] vpi/vci [ilmi | qsaal]

Configures a new ATM PVC by assigning its VPI/VCI numbers and enters ATM VC configuration mode. The valid values for vpi/vci are:

vpi—Specifies the VPI ID. The valid range is 0 to 255.

vci—Specifies the VCI ID. The valid range is 1 to 65535. Values 1 to 31 are reserved and should not be used, except for 5 for the QSAAL PVC and 16 for the ILMI PVC.

You can also configure the following options:

name—(Optional) An arbitrary string that identifies this PVC.

ilmi—(Optional) Configures the VC to exclusively carry ILMI protocol traffic (default).

qsaal—(Optional) Configures the VC to exclusively carry qsaal protocol traffic.

Note When using the pvc command, remember that the vpi/vci combination forms a unique identifier for the interface and all of its subinterfaces. If you specify a vpi/vci combination that has been used on another subinterface, the Cisco IOS software assumes that you want to modify that PVC's configuration and automatically switches to its parent subinterface.

Step 5 

Router(config-if-atm-vc)# protocol protocol {protocol-address | inarp} [[no] broadcast]

Configures the PVC for a particular protocol and maps it to a specific protocol-address.

protocol—Typically set to either ip or ppp, but other values are possible.

protocol-address—Destination address or virtual interface template for this PVC (if appropriate for the protocol).

inarp—Specifies that the PVC uses Inverse ARP to determine its address.

[no] broadcast—(Optional) Specifies that this mapping should (or should not) be used for broadcast packets.

Step 6 

Router(config-if-atm-vc)# inarp minutes

(Optional) If using Inverse ARP, configures how often the PVC transmits Inverse ARP requests to confirm its address mapping. The valid range is 1 to 60 minutes, with a default of 15 minutes.

Step 7 

Router(config-if-atm-vc)# encapsulation aal5snap

(Optional) Configures the ATM adaptation layer (AAL) and encapsulation type. The default and only supported type is aal5snap.

Step 8 

Router(config-if-atm-vc)# tx-limit buffers

(Optional) Specifies the number of transmit buffers for this VC. The valid range is from 1 to 57343, with a default value that is based on the current VC line rate and on the latency value that is configured with the atm tx-latency command.

Note Repeat Step 4 through Step 8 for each PVC to be configured on this interface.

Step 9 

Router(config-if-atm-vc)# end

Exits ATM VC configuration mode and returns to privileged EXEC mode.

Step 1 

Router(config)# interface atm slot/subslot/port.subinterface point-to-point

Creates the specified point-to-point subinterface on the given port on the specified ATM SPA, and enters subinterface configuration mode.

Step 2 

Router(config-subif)# ip address address mask

Assigns the specified IP address and subnet mask to this subinterface.

Step 3 

Router(config-subif)# pvc [name] vpi/vci [ilmi | qsaal]

Configures a new ATM PVC by assigning its VPI/VCI numbers and enters ATM VC configuration mode. The valid values for vpi/vci are:

vpi—Specifies the VPI ID. The valid range is 0 to 255.

vci—Specifies the VCI ID. The valid range is 1 to 65535. Values 1 to 31 are reserved and should not be used, except for 5 for the QSAAL PVC and 16 for the ILMI PVC.

You can also configure the following options:

name—(Optional) An arbitrary string that identifies this PVC.

ilmi—(Optional) Configures the PVC to use ILMI encapsulation (default).

qsaal—(Optional) Configures the PVC to use QSAAL encapsulation.

Note When using the pvc command, remember that the vpi/vci combination forms a unique identifier for the interface and all of its subinterfaces. If you specify a vpi/vci combination that has been used on another subinterface, the Cisco IOS software assumes that you want to modify that PVC's configuration and automatically switches to its parent subinterface.

Step 4 

Router(config-if-atm-vc)# protocol protocol protocol-address [[no] broadcast]

Configures the PVC for a particular protocol and maps it to a specific protocol-address.

protocol—Typically set to ppp for point-to-point subinterfaces, but other values are possible.

protocol-address—Destination address or virtual template interface for this PVC (as appropriate for the specified protocol).

[no] broadcast—(Optional) Specifies that this mapping should (or should not) be used for broadcast packets.

The protocol command also has an inarp option, but this option is not meaningful on point-to-point PVCs that use a manually configured address.

Step 5 

Router(config-if-atm-vc)# encapsulation aal5snap

(Optional) Configures the ATM adaptation layer (AAL) and encapsulation type. The default and only supported type is aal5snap.

Repeat Step 1 through Step 5 for each point-to-point subinterface to be configured on this ATM SPA.

Step 6 

Router(config-if)# end

Exits interface configuration mode and returns to privileged EXEC mode.

Step 1 

Router(config)# interface atm slot/subslot/port.subinterface multipoint

Creates the specified point-to-multipoint subinterface on the given port on the specified ATM SPA, and enters subinterface configuration mode.

Step 2 

Router(config-subif)# ip address address mask

Assigns the specified IP address and subnet mask to this subinterface.

Step 3 

Router(config-subif)# no ip directed-broadcast

(Optional) Disables the forwarding of IP directed broadcasts, which are sometimes used in denial of service (DOS) attacks.

Step 4 

Router(config-subif)# pvc [name] vpi/vci [ilmi | qsaal]

Configures a new ATM PVC by assigning its VPI/VCI numbers and enters ATM VC configuration mode. The valid values for vpi/vci are:

•vpi—Specifies the VPI ID. The valid range is 0 to 255.

•vci—Specifies the VCI ID. The valid range is 1 to 65535. Values 1 to 31 are reserved and should not be used, except for 5 for the QSAAL PVC and 16 for the ILMI PVC.

You can also configure the following options:

•name—(Optional) An arbitrary string that identifies this PVC.

•ilmi—(Optional) Configures the PVC to use ILMI encapsulation (default).

•qsaal—(Optional) Configures the PVC to use QSAAL encapsulation.

Note When using the pvc command, remember that the vpi/vci combination forms a unique identifier for the interface and all of its subinterfaces. If you specify a vpi/vci combination that has been used on another subinterface, the Cisco IOS software assumes that you want to modify that PVC's configuration and automatically switches to its parent subinterface.

Step 5 

Router(config-if-atm-vc)# protocol protocol {protocol-address | inarp} broadcast

Configures the PVC for a particular protocol and maps it to a specific protocol-address.

•protocol—Typically set to ip for multipoint subinterfaces, but other values are possible.

•protocol-address—Destination address or virtual template interface for this PVC (if appropriate for the protocol).

•inarp—Specifies that the PVC uses Inverse ARP to determine its address.

•broadcast— Specifies that this mapping should be used for multicast packets.

Step 6 

Router(config-if-atm-vc)# inarp minutes

(Optional) If using Inverse ARP, configures how often the PVC transmits Inverse ARP requests to confirm its address mapping. The valid range is 1 to 60 minutes, with a default of 15 minutes.

Step 7 

Router(config-if-atm-vc)# encapsulation aal5snap

(Optional) Configures the ATM adaptation layer (AAL) and encapsulation type. The default and only supported type is aal5snap.

Note Repeat Step 1 through Step 7 for each multipoint subinterface to be configured on this ATM SPA.

Step 8 

Router(config-if)# end

Exits interface configuration mode and returns to privileged EXEC mode.

Step 1 

Router(config)# interface atm slot/subslot/port.subinterface point-to-point

(Optional) Creates the specified point-to-point subinterface on the given port on the specified ATM SPA card, and enters subinterface configuration mode.

Note Although it is most common to create the PVCs on subinterfaces, you can also omit this step to create the PVCs for RFC 1483 bridging on the main interface.

Step 2 

Router(config-subif)# pvc [name] vpi/vci [ilmi | qsaal]

Configures a new ATM PVC by assigning its VPI/VCI numbers and enters ATM VC configuration mode. The valid values for vpi/vci are:

•vpi—Specifies the VPI ID. The valid range is 0 to 255.

•vci—Specifies the VCI ID. The valid range is 1 to 65535. Values 1 to 31 are reserved and should not be used, except for 5 for the QSAAL PVC and 16 for the ILMI PVC.

You can also configure the following options:

•name—(Optional) An arbitrary string that identifies this PVC.

•ilmi—(Optional) Configures the PVC to use ILMI encapsulation (default).

•qsaal—(Optional) Configures the PVC to use QSAAL encapsulation.

Step 3 

Router(config-if-atm-vc)#bridge-domain vlan-id [access | dot1q | dot1q-tunnel] [ignore-bpdu-pid] | {pvst-tlv CE-vlan} [increment] [split-horizon]

Binds the PVC to the specified vlan-id. You can optionally specify the following keywords:

•dot1q—(Optional) Includes the IEEE 802.1Q tag, which preserves the VLAN ID and class of service (CoS) information across the ATM cloud.

•dot1q-tunnel—(Optional) Enables tunneling of IEEE 802.1Q VLANs over the same link. See the "Configuring RFC 1483 Bridging for PVCs with IEEE 802.1Q Tunneling" section.

•ignore-bpdu-pid—(Optional) Ignores bridge protocol data unit (BPDU) packets, to allow interoperation with ATM customer premises equipment (CPE) devices that do not distinguish BPDU packets from data packets. Without this keyword, IEEE BPDUs are sent out using a PID of 0x00-0E, which complies with RFC 1483. With this keyword, IEEE BPDUs are sent out using a PID of 0x00-07, which is normally reserved for RFC 1483 data.

•pvst-tlv—When transmitting, the pvst-tlv keyword translates PVST+ BPDUs into IEEE BPDUs. When receiving, the pvst-tlv keyword translates IEEE BPDUs into PVST+ BPDUs.

•split-horizon—(Optional) Enables RFC 1483 split horizon mode to globally prevent bridging between PVCs in the same VLAN.

Step 4 

Router(config-if-atm-vc)# encapsulation aal5snap

(Optional) Configures the ATM adaptation layer (AAL) and encapsulation type. The default and only supported type is aal5snap.

Note Repeat Step 1 through Step 4 for each interface on the ATM SPA to be configured.

Step 5 

Router(config-if-atm-vc)# end

Exits ATM VC configuration mode and returns to privileged EXEC mode.

Step 1 

Router(config)# interface atm slot/subslot.port.subinterface point-to-point

(Optional) Creates the specified point-to-point subinterface on the given port on the specified ATM SPA, and enters subinterface configuration mode.

Note Although it is most common to create the PVCs on subinterfaces, you can also omit this step to create the PVCs for RFC 1483 bridging on the main interface.

Step 2 

Router(config-subif)# pvc [name] vpi/vci [ilmi | qsaal]

Configures a new ATM PVC by assigning its VPI/VCI numbers and enters ATM VC configuration mode. The valid values for vpi/vci are:

•vpi—Specifies the VPI ID. The valid range is 0 to 255.

•vci—Specifies the VCI ID. The valid range is 1 to 65535. Values 1 to 31 are reserved and should not be used, except for 5 for the QSAAL PVC and 16 for the ILMI PVC.

You can also configure the following options:

•name—(Optional) An arbitrary string that identifies this PVC.

•ilmi—(Optional) Configures the PVC to use ILMI encapsulation (default).

•qsaal—(Optional) Configures the PVC to use QSAAL encapsulation.

Note When using the pvc command, remember that the vpi/vci combination forms a unique identifier for the interface and all of its subinterfaces. If you specify a vpi/vci combination that has been used on another subinterface, the Cisco IOS software assumes that you want to modify that PVC's configuration and automatically switches to its parent subinterface.

Step 3 

Router(config-if-atm-vc)# bridge-domain vlan-id dot1q-tunnel

Binds the PVC to the specified vlan-id and enables the use of IEEE 802.1Q tunneling on the PVC. This preserves the VLAN ID information across the ATM cloud.

Step 4 

Router(config-if-atm-vc)# encapsulation aal5snap

(Optional) Configures the ATM adaptation layer (AAL) and encapsulation type. The default and only supported type is aal5snap.

Note Repeat Step 1 through Step 4 for each interface on the ATM SPA to be configured.

Step 5 

Router(config-if-atm-vc)# end

Exits ATM VC configuration mode and returns to privileged EXEC mode.

Step 1 

Router(config)# interface atm slot/subslot/port.subinterface multipoint

Creates the specified point-to-point subinterface on the given port on the specified ATM SPA, and enters subinterface configuration mode.

Step 2 

Router(config-subif)# ip address address mask [secondary]

Assigns the specified IP address and subnet mask to this subinterface. This IP address should be on the same subnet as the remote bridged network (the Ethernet network).

Step 3 

Router(config-subif)# pvc [name] vpi/vci [ilmi | qsaal]

Configures a new ATM PVC by assigning its VPI/VCI numbers and enters ATM VC configuration mode. The valid values for vpi/vci are:

•vpi—Specifies the VPI ID. The valid range is 0 to 255.

•vci—Specifies the VCI ID. The valid range is 1 to 65535. Values 1 to 31 are reserved and should not be used, except for 5 for the QSAAL PVC and 16 for the ILMI PVC.

You can also configure the following options:

•name—(Optional) An arbitrary string that identifies this PVC.

•ilmi—(Optional) Configures the PVC to use ILMI encapsulation (default).

•qsaal—(Optional) Configures the PVC to use QSAAL encapsulation.

Note When using the pvc command, remember that the vpi/vci combination forms a unique identifier for the interface and all of its subinterfaces. If you specify a vpi/vci combination that has been used on another subinterface, the Cisco IOS software assumes that you want to modify that PVC's configuration and automatically switches to its parent subinterface.

Step 4 

Router(config-if-atm-vc)# encapsulation aal5snap bridge

(Optional) Configures the ATM adaptation layer (AAL) and encapsulation type, and specifies that half-bridging should be used.

Step 5 

Router(config-if-atm-vc)# end

Exits ATM VC configuration mode and returns to privileged EXEC mode.

Step 1 

Router(config)# interface atm slot/subslot/port.subinterface point-to-point

Creates the specified multipoint subinterface on the given port on the specified ATM SPA, and enters subinterface configuration mode.

Step 2 

Router(config-subif)# atm route-bridge ip

Enables ATM RFC 1483 half-bridging (RBE bridging).

Note The atm route-bridge ip command can be given either before or after you create the PVC.

Step 3 

Router(config-subif)# ip address address mask [secondary]

Assigns the specified IP address and subnet mask to this subinterface. This IP address should be on the same subnet as the remote bridged network (the Ethernet network).

Step 4 

Router(config-subif)# pvc [name] vpi/vci [ilmi | qsaal]

Configures a new ATM PVC by assigning its VPI/VCI numbers and enters ATM VC configuration mode. The valid values for vpi/vci are:

•vpi—Specifies the VPI ID. The valid range is 0 to 255.

•vci—Specifies the VCI ID. The valid range is 1 to 65535. Values 1 to 31 are reserved and should not be used, except for 5 for the QSAAL PVC and 16 for the ILMI PVC.

You can also configure the following options:

•name—(Optional) An arbitrary string that identifies this PVC.

•ilmi—(Optional) Configures the PVC to use ILMI encapsulation (default).

•qsaal—(Optional) Configures the PVC to use QSAAL encapsulation.

Note When using the pvc command, remember that the vpi/vci combination forms a unique identifier for the interface and all of its subinterfaces. If you specify a vpi/vci combination that has been used on another subinterface, the Cisco IOS software assumes that you want to modify that PVC's configuration and automatically switches to its parent subinterface.

Step 5 

Router(config-if-atm-vc)# encapsulation aal5snap

(Optional) Configures the ATM adaptation layer (AAL) and encapsulation type. The only supported encapsulation for an RBE PVC is aal5snap.

Step 6 

Router(config-if-atm-vc)# end

Exits ATM VC configuration mode and returns to privileged EXEC mode.

Step 1 

Router(config)# interface atm slot/subslot/port

Enters interface configuration mode for the indicated port on the specified ATM SPA.

Step 2 

Router(config-if)# no ip address

Assigns no IP address to the interface.

Step 3 

Router(config-if)# spanning-tree bpdufilter enable

(Optional) Blocks all Spanning Tree BPDUs on the ATM interface. This command should be used if this ATM interface is configured only for BRE VLANs.

Note If this ATM interface is configured for both BRE and RFC 1483 bridged VLANs, do not enter this command unless you want to explicitly block BPDUs on the interface.

Step 4 

Router(config-if)# no shutdown

Enables the interface.

Step 5 

Router(config-if)# interface atm slot/subslot/port.subinterface point-to-point

Creates the specified point-to-point subinterface on the given port on the specified ATM SPA, and enters subinterface configuration mode.

Step 6 

Router(config-subif)# no ip address

Assigns no IP address to the subinterface.

Step 7 

Router(config-subif)# pvc [name] vpi/vci [ilmi | qsaal]

Configures a new ATM PVC by assigning its VPI/VCI numbers and enters ATM VC configuration mode. The valid values for vpi/vci are:

•vpi—Specifies the VPI ID. The valid range is 0 to 255.

•vci—Specifies the VCI ID. The valid range is 1 to 65535. Values 1 to 31 are reserved and should not be used, except for 5 for the QSAAL PVC and 16 for the ILMI PVC.

You can also configure the following options:

•name—(Optional) An arbitrary string that identifies this PVC.

•ilmi—(Optional) Configures the PVC to use ILMI encapsulation (default).

•qsaal—(Optional) Configures the PVC to use QSAAL encapsulation.

Note When using the pvc command, remember that the vpi/vci combination forms a unique identifier for the interface and all of its subinterfaces. If you specify a vpi/vci combination that has been used on another subinterface, the Cisco IOS software assumes that you want to modify that PVC's configuration and automatically switches to its parent subinterface.

Step 8 

Router(config-if-atm-vc)# bre-connect vlan-id [mac mac-address]

Enables BRE bridging on the PVC, where:

•mac mac-address—(Optional) Specifies the hardware (MAC) address of the destination customer premises equipment (CPE) device at the remote end of the VLAN connection.

Step 9 

Router(config-if-atm-vc)# interface gigabitethernet slot/port

Enters interface configuration mode for the specified Gigabit Ethernet interface.

Step 10 

Router(config-if)# switchport

Configures the Gigabit Ethernet interface for Layer 2 switching.

Step 11 

Router(config-if)# switchport access vlan vlan-id

(Optional) Specifies the default VLAN for the interface. This should be the same VLAN ID that was specified in the bre-connect command in Step 8.

Step 12 

Router(config-if)# switchport mode access

Puts the interface into nontrunking mode.

Step 13 

Router(config-if)# end

Exits interface configuration mode and returns to privileged EXEC mode.

Step 1 

Router(config)# interface atm slot/subslot/port

Enters interface configuration mode for the indicated port on the specified ATM SPA.

Step 2 

Router(config-if)# ip address

Assigns an IP address to the interface.

Step 3 

Router(config-if)#atm route-bridge ip

Configures RBE.

Step 4 

Router(config-if)# mpls ip

Configures MPLS.

Step 1 

Router(config)# policy-map policy-map-name

Creates or modifies a policy map that can be attached to one or more interfaces to specify a service policy.

•policy-map-name—Name of a service policy map to be created. The name can be a maximum of 40 alphanumeric characters.

Step 2 

Router(config-pmap)# class {class-name | class-default}

Specifies the class policy to be configured.

•class-name—Name of class you want to configure. Note that WRED can be defined for a user-defined class only if the class has the bandwidth/shape feature enabled.

•class-default—Default class.

Step 3 

Router(config-pmap-c)# random-detect [precedence-based] aggregate [minimum-thresh min-thresh maximum-thresh max-thresh mark-probability mark-prob]

Enables aggregate WRED based on IP precedence values. If optional parameters for a default aggregate class are not defined, these parameters will be set based on interface (VC) bandwidth.

•precedence-based—(Optional) Specifies that aggregate WRED is to drop packets based on IP precedence values. This is the default.

•min-thresh—(Optional) Minimum threshold in number of packets. The value range of this argument is from 1 to 12288.

•max-thresh—(Optional) Maximum threshold in number of packets. The value range of this argument is from the value of the minimum threshold argument to 12288.

•mark-prob—(Optional) Denominator for the fraction of packets dropped when the average queue depth is at the maximum threshold. The value range is from 1 to 255.

Step 4 

Router(config-pmap-c)# random-detect precedence values sub-class-val1 [...[sub-class-val8]] minimum-thresh min-thresh maximum-thresh max-thresh [mark-probability mark-prob]

Configures the WRED parameters for packets with one or more specific IP precedence values.

•sub-class-val1 [...[sub-class-val8]] —One or more specific IP precedence values to which the following WRED profile parameter specifications are to apply. A maximum of 8 subclasses (IP precedence values) can be specified per CLI entry. The IP precedence value can be a number from 0 to 7.

•min-thresh—Minimum threshold in number of packets. The value range of this argument is from 1 to 12288.

•max-thresh—Maximum threshold in number of packets. The value range of this argument is from the value of the minimum threshold argument to 12288.

•mark-prob—Denominator for the fraction of packets dropped when the average queue depth is at the maximum threshold. The value range is from 1 to 255.

Repeat this command for each set of IP precedence values that share WRED parameters.

Step 5 

Router(config-pmap-c)# interface atm slot/subslot/port.subinterface point-to-point

Creates the specified point-to-point subinterface on the given port on the specified ATM SPA, and enters subinterface configuration mode.

•slot—Chassis slot number where the SIP is installed.

•subslot—Secondary slot of the SIP where the SPA is installed.

•port —Number of the individual interface port on the SPA.

•.subinterface—Subinterface number. The number that precedes the period must match the number to which this subinterface belongs. The range is 1 to 4,294,967,293.

Step 6 

Router(config-subif)# ip address address mask

Assigns the specified IP address and subnet mask to the interface.

•address—IP address.

•mask—Subnet mask.

Step 7 

Router(config-subif)# pvc [name] vpi/vci [ilmi | qsaal]

Configures a new ATM PVC by assigning an optional name and its VPI/VCI numbers.

•name—(Optional) An arbitrary string that identifies this PVC.

•vpi—VPI ID. The range is 0 to 255.

•vci—VCI ID. The valid range is 1 to 65535. Values 1 to 31 are reserved and should not be used, except 5 for the QSAAL PVC and 16 for the ILMI PVC.

Step 8 

Router(config-subif)# service-policy output policy-map-name

Attaches the specified policy map to the subinterface.

•policy-map-name—Name of a service policy map to be attached. The name can be a maximum of 40 alphanumeric characters.

Step 1 

Router(config)# policy-map policy-map-name

Creates or modifies a policy map that can be attached to one or more interfaces to specify a service policy.

•policy-map-name—Name of a service policy map to be created. The name can be a maximum of 40 alphanumeric characters.

Step 2 

Router(config-pmap)# class {class-name | class-default}

Specifies the class policy to be configured.

•class-name—Name of class you want to configure. Note that WRED can be defined for a user-defined class only if the class has the bandwidth/shape feature enabled.

•class-default—Default class.

Step 3 

Router(config-pmap-c)# random-detect dscp-based aggregate [minimum-thresh min-thresh maximum-thresh max-thresh mark-probability mark-prob]

Enables aggregate WRED based on DSCP values. If optional parameters for a default aggregate class are not defined, these parameters will be set based on interface (VC) bandwidth.

•min-thresh—(Optional) Minimum threshold in number of packets. The value range of this argument is from 1 to 12288.

•max-thresh—(Optional) Maximum threshold in number of packets. The value range of this argument is from the value of the minimum threshold argument to 12288.

•mark-prob—(Optional) Denominator for the fraction of packets dropped when the average queue depth is at the maximum threshold. The value range is from 1 to 255.

Step 4 

Router(config-pmap-c)# random-detect dscp values sub-class-val1 [...[sub-class-val8]] minimum-thresh min-thresh maximum-thresh max-thresh [mark-probability mark-prob]

Configures the WRED parameters for packets with one or more specific DSCP values.

•sub-class-val1 [...[sub-class-val8]] —One or more DSCP values to which the following WRED parameter specifications are to apply. [A maximum of 8 subclasses (IP precedence values) can be specified per CLI entry.] The DSCP value can be a number from 0 to 63, or it can be one of the following keywords: ef, af11, af12, af13, af21, af22, af23, af31, af32, af33, af41, af42, af43, cs1, cs2, cs3, cs4, cs5, or cs7

•min-thresh—Specifies the minimum threshold in number of packets. The value range of this argument is from 1 to 12288.

•max-thresh—Specifies the maximum threshold in number of packets. The value range of this argument is from the value of the minimum threshold argument to 12288.

•mark-prob—Specifies the denominator for the fraction of packets dropped when the average queue depth is at the maximum threshold. The value range is from 1 to 255.

Repeat this command for each set of DSCP values that share WRED parameters.

Step 5 

Router(config-pmap-c)# interface atm slot/subslot/port.subinterface point-to-point

Creates the specified point-to-point subinterface on the given port on the specified ATM SPA, and enters subinterface configuration mode.

•slot—Chassis slot number where the SIP is installed.

•subslot—Secondary slot of the SIP where the SPA is installed.

•port—Number of the individual interface port on the SPA.

•.subinterface—subinterface number. The number that precedes the period must match the number to which this subinterface belongs. The range is 1 to 4,294,967,293.

Step 6 

Router(config-subif)# ip address address mask

Assigns the specified IP address and subnet mask to the interface.

•address—IP address.

•mask—Subnet mask.

Step 7 

Router(config-subif)# pvc [name] vpi/vci [ilmi | qsaal]

Configures a new ATM PVC by assigning an optional name and its VPI/VCI numbers.

•name—(Optional) An arbitrary string that identifies this PVC.

•vpi—VPI ID. The range is 0 to 255.

•vci—VCI ID. The valid range is 1 to 65535. Values 1 to 31 are reserved and should not be used, except 5 for the QSAAL PVC and 16 for the ILMI PVC.

Step 8 

Router(config-subif)# service-policy output policy-map-name

Attaches the specified policy map to the subinterface.

•policy-map-name—Name of a service policy map to be attached. The name can be a maximum of 40 alphanumeric characters

Step 1 

Router(config)# interface atm slot/subslot/port

Enters interface configuration mode for the indicated port on the specified ATM SPA.

Step 2 

Router(config-subif)# pvc [name] 0/5 qsaal

Configures a new ATM PVC to be used for SVC signaling:

•name—(Optional) An arbitrary string that identifies this PVC.

•vpi—Specifies the VPI ID. The valid range is 0 to 255, but the recommended value for vpi for the signaling PVC is 0.

•vci—Specifies the VCI ID. The valid range is 1 to 65535, but the recommended value for vci for the QSAAL signaling PVC is 5.

Note The ATM switch must be configured with the same VPI and VCI values for this PVC.

•qsaal—Configures the signaling PVC to use QSAAL encapsulation.

Step 3 

Router(config-subif)# pvc [name] 0/16 ilmi

Creates a new ATM PVC to be used for ILMI signaling:

•name—(Optional) An arbitrary string that identifies this PVC.

•vpi—Specifies the VPI ID. The valid range is 0 to 255, but the recommended value for vpi for the ILMI PVC is 0.

•vci—Specifies the VCI ID. The valid range is 1 to 65535, but the recommended value for vci for the ILMI PVC is 16.

•ilmi—Configures the PVC to use ILMI encapsulation.

Note The signaling and ILMI PVCs must be set up on the main ATM interface, not on a subinterface.

Step 4 

Router(config-if-atm-vc)# exit

Exits ATM PVC configuration mode and returns to interface configuration mode.

Step 5 

Router(config-if)# atm ilmi-keepalive [seconds] [retry counts]

(Optional) Enables ILMI keepalive messages and sets the interval between them. ILMI keepalive messages are disabled by default.

•seconds—(Optional) The amount of time, in seconds, between keepalive messages between the Catalyst 6500 Series switch and the ATM switch. The valid range is 1 to 65535, with a default of 3 seconds.

•retry counts—(Optional) Specifies the number of times the Catalyst 6500 Series switch should resend a keepalive message if the first message is unacknowledged. The valid range is 2 to 5, with a default of 4.

Step 6 

Router(config-if)# atm esi-address esi.selector

Specifies the end station ID (ESI) and selector fields for the local portion of the ATM interface's NSAP address, and configures the interface to get the NSAP prefix from the ATM switch.

•esi—Specifies a string of 12 hexadecimal digits, in dotted notation, for the ATM interface's ESI value. This value must be unique across the network.

•selector—Specifies a string of 2 hexadecimal digits for the selector byte for this ATM interface.

To configure the ATM address, you need to enter only the ESI (12 hexadecimal digits) and the selector byte (2 hexadecimal digits). The NSAP prefix (26 hexadecimal digits) is provided by the ATM switch.

or

or

Router(config-if)# atm nsap-address nsap-address

Assigns a complete NSAP address (40 hexadecimal digits) to the ATM interface. The address consists of a network prefix, ESI, and selector byte, and must be in the following format:

XX.XXXX.XX.XXXXXX.XXXX.XXXX.XXXX.XXXX.XXXX.XXXX.XX

Note The above dotted hexadecimal format provides some validation that the address is a legal value. If you know that the NSAP address is correct, you may omit the dots.

Note The atm esi-address and atm nsap-address commands are mutually exclusive. Configuring the Catalyst 6500 Series switch with one of these commands automatically negates the other. Use the show interface atm command to display the NSAP address that is assigned to the interface.

Step 7 

Router(config-if)# interface atm slot/subslot/port.subinterface [multipoint | point-to-point]

(Optional) Creates the specified subinterface on the specified ATM interface, and enters subinterface configuration mode.

Note You can create SVCs on either the main ATM interface or on a multipoint subinterface.

Step 8 

Router(config-subif)# svc [name] nsap address

Creates an SVC and specifies the destination NSAP address (40 hexadecimal digits in dotted notation). You can also configure the following option:

•name—(Optional) An arbitrary string that identifies this SVC.

Step 9 

Router(config-if-atm-vc)# oam-svc [manage] [frequency]

Enables end-to-end Operation, Administration, and Maintenance (OAM) loopback cell generation and management of the SVC.

•manage—(Optional) Enables OAM management of the SVC.

•frequency—(Optional) Specifies the delay between transmitting OAM loopback cells. The valid range is 0 to 600 seconds, with a default of 10 seconds.

Step 10 

Router(config-if-atm-vc)# protocol protocol {protocol-address | inarp} [[no] broadcast]

Configures the SVC for a particular protocol and maps it to a specific protocol-address.

•protocol—Typically set to either ip or ppp, but other values are possible.

•protocol-address—Destination address or virtual interface template for this SVC (if appropriate for the protocol).

•inarp—Specifies that the SVC uses Inverse ARP to determine its address.

•[no] broadcast—(Optional) Specifies that this mapping should (or should not) be used for broadcast packets.

Step 11 

Router(config-if-atm-vc)# encapsulation aal5snap

(Optional) Configures the ATM adaptation layer (AAL) and encapsulation type. The default and only supported type is aal5snap.

Note Repeat Step 7 through Step 11 for each SVC to be created.

Step 12 

Router(config-if-atm-vc)# end

Exits SVC configuration mode and returns to privileged EXEC mode.

Step 1 

Router(config)# interface atm slot/subslot
or
Router(config)# interface atm slot/subslot/port.subinterface [multipoint | point-to-point]

Enters interface or subinterface configuration mode for the indicated port on the specified ATM SPA.

Step 2 

Router(config-if)# pvc [name] vpi/vci
or
Router(config-if)# svc [name] nsap-address

Specifies the PVC or SVC to be configured, and enters PVC/SVC configuration mode.

Note When using the pvc command, remember that the vpi/vci combination forms a unique identifier for the interface and all of its subinterfaces. If you specify a vpi/vci combination that has been used on another subinterface, the Cisco IOS software assumes that you want to modify that PVC's configuration and automatically switches to its parent subinterface.

Step 3 

Router(config-if-atm-vc)# cbr rate

Configures constant bit rate (CBR) quality of service (QoS) and average cell rate for the PVC or SVC:

•rate—Average cell rate in kbps. The valid range is 48 to 149760 (OC-3) or 599040 (OC-12).

or

Router(config-if-atm-vc)# ubr output-pcr [input-pcr]

Configures unspecified bit rate (UBR) quality of service (QoS) and peak cell rate (PCR) for the PVC or SVC:

•output-pcr—Output PCR in kbps. The valid range is 48 to 149760 (OC-3), 599040 (OC-12), or 2396160 (1-Port OC-48c/STM-16 ATM SPA).

•input-pcr—(Optional for SVCs only) Input PCR in kbps. If omitted, input-pcr equals output-pcr.

or

or

Router(config-if-atm-vc)# vbr-nrt output-pcr output-scr output-mbs [input-pcr] [input-scr] [input-mbs]

Configures the variable bit rate-nonreal time (VBR-nrt) QoS, the peak cell rate (PCR), sustainable cell rate (SCR), and maximum burst cell size (MBS) for the PVC or SVC:

•output-pcr—Output PCR in kbps. The valid range is 48 to 149760 (OC-3), 599040 (OC-12), or 2396160 (1-Port OC-48c/STM-16 ATM SPA).

•output-scr—Output SCR in kbps. The valid range is 48 to PCR, and typically is less than the PCR value.

•output-mbs—Output MBS in number of cells. The valid range is 1 to 65535, depending on the PCR and SCR values. If the PCR and SCR are configured to the same value, the only valid value for MBS is 1.

•input-pcr—(Optional for SVCs only) Input PCR in kbps.

•input-scr—(Optional for SVCs only) Input SCR in kbps.

•input-mbs—(Optional for SVCs only) Input MBS in number of cells.

or

or

Router(config-if-atm-vc)# vbr-rt pcr scr burst

Configures the variable bit rate-real time (VBR-rt) QoS, and the PCR, average cell rate (ACR), and burst cell size (BCS) for the PVC or SVC:

•pcr—PCR in kbps. The valid range is 48 to 149760 (OC-3), 599040 (OC-12), or 2396160 (1-Port OC-48c/STM-16 ATM SPA).

•scr—SCR in kbps. The valid range is 48 to PCR, and typically is less than the PCR value.

•burst—Burst size in number of cells. The valid range is 1 to 65535, depending on the PCR and SCR values. If the PCR and SCR are configured to the same value, the only valid value for burst is 1.

Step 4 

Router(config-if-atm-vc)# transmit-priority level

(Optional) Configures the PVC for a new transmit priority level.

•level—Priority level from 1 to 6. The default value is determined by the PVC's configured service class (see Table 7-1 for the default levels).

Note Repeat Step 2 through Step 4 for each PVC or SVC to be configured.

Step 5 

Router(config-if-atm-vc)# end

Exits PVC/SVC configuration mode and returns to privileged EXEC mode.

Step 1 

Router(config)# vc-class atm vc-class-name

Creates an ATM virtual circuit (VC) class and enters VC-class configuration mode.

•vc-class-name—Arbitrary name to identify this particular VC class.

Step 2 

Router(config-vc-class)# configuration-commands

Enter any PVC or SVC configuration commands for this VC class. See the "Creating a Permanent Virtual Circuit" section and "Creating and Configuring Switched Virtual Circuits" section for additional information.

Note You can specify both PVC and SVC configuration commands in the same VC class. If a command is not appropriate for a PVC or SVC, it is ignored when the VC class is assigned to the PVC or SVC.

Step 3 

Router(config-vc-class)# interface atm slot/subslot/port

or

Router(config-vc-class)# interface atm slot/subslot/port.subinterface [multipoint | point-to-point]

Enters subinterface configuration mode for the specified ATM interface or subinterface.

Step 4 

Router(config-if)# class-int vc-class-name

(Optional) Applies a VC class on the ATM main interface or subinterface. This class then applies to all PVCs or SVCs that are created on that interface.

•vc-class-name—Name of the VC class that was created in Step 1.

Step 5 

Router(config-if)# pvc [name] vpi/vci

or

Router(config-if)# svc [name] nsap-address

Specifies the PVC or SVC to be configured, and enters ATM VC configuration mode.

Note When using the pvc command, remember that the vpi/vci combination forms a unique identifier for the interface and all of its subinterfaces. If you specify a vpi/vci combination that has been used on another subinterface, the Cisco IOS software assumes that you want to modify that PVC's configuration and automatically switches to its parent subinterface.

Step 6 

Router(config-if-atm-vc)# class-vc vc-class-name

Assigns the specified VC class to this PVC or SVC.

•vc-class-name—Name of the VC class that was created in Step 1.

Step 7 

Router(config-if-atm-vc)# configuration-commands

Any other VC configuration commands to be applied to this particular PVC or SVC. Commands that are applied to the individual PVC or SVC supersede any conflicting commands that were specified in the VC class.

Step 8 

Router(config-if)# end

Exits interface configuration mode and returns to privileged EXEC mode.

Step 1 

Router(config)# ip cef [distributed]

Enables Cisco Express Forwarding (CEF) Layer 3 switching on the Catalyst 6500 Series switch. The Catalyst 6500 Series switch enables CEF by default.

•distributed—(Optional) Enables distributed CEF (dCEF).

Step 2 

Router(config)# mpls label protocol ldp

Specifies the default label distribution protocol for a platform.

Step 3 

Router(config)# interface atm slot/subslot/port

or

Router(config)# interface atm slot/subslot/port.subinterface [multipoint | point-to-point]

Enters interface configuration mode for the specified ATM interface or subinterface.

Step 4 

Router(config-if)# mpls ip

Enables MPLS forwarding of IPv4 packets along normally routed paths for the interface.

Step 5 

Router(config-if)# bundle bundle-name

Creates an ATM virtual circuit (VC) bundle and enters bundle configuration mode.

•bundle-name—Arbitrary name to identify this particular VC bundle.

Step 6 

Router(config-if-atm-bundle)# class-bundle vc-class-name

(Optional) Applies a VC class to this bundle. The class configuration is then applied to all VCs in the bundle.

•vc-class-name—Name of the VC class to be applied to this bundle and its PVCs or SVCs. See the "Configuring Virtual Circuit Classes" section for information on creating VC classes.

Step 7 

Router(config-if-atm-bundle)# configuration-commands

Enter any other PVC or SVC configuration commands for this VC bundle. See "Creating a Permanent Virtual Circuit" section and "Creating and Configuring Switched Virtual Circuits" section for additional information.

Note Configuration commands applied directly to the VC bundle supersede a configuration that is applied through a VC class.

Step 8 

Router(config-if-atm-bundle)# pvc-bundle [name] vpi/vci

Creates a member PVC of the bundle and enters PVC bundle configuration mode.

Step 9 

Router(config-if-atm-member)# mpls experimental [level | other | range]

(Optional) Configures the MPLS EXP levels for the PVC bundle member.

•level—MPLS EXP level for the PVC bundle member. The valid range is 0 to 7.

•other—Any MPLS EXP levels in the range from 0 to 7 that are not explicitly configured (default).

•range—A range of MPLS EXP levels between 0 and 7, separated by a hyphen.

Step 10 

Router(config-if-atm-member)# bump {implicit | explicit precedence-level | traffic}

(Optional) Configures the bumping rules for the PVC bundle member.

•implicit—Bumped traffic is carried by a VC with a lower precedence (default).

•explicit precedence-level—Specifies the precedence level of the traffic that should be bumped when the PVC member goes down. The precedence-level can range from 0 to 9.

•traffic—The PVC member accepts bumped traffic (default). Use no bump traffic to specify that the PVC member does not accept bumped traffic.

Step 11 

Router(config-if-atm-member)# protect {group | vc}

(Optional) Specifies that the PVC bundle member is protected.

•group—Specifies that the PVC bundle member is part of a protected group. When all members of a protected group go down, the bundle goes down.

•vc—Specifies that the PVC bundle member is individually protected. When a protected VC goes down, it also takes the bundle down.

By default, PVC bundle members are not protected.

Step 12 

Router(config-if-atm-member)# configuration-commands

Any other VC configuration commands to be applied to this particular VC bundle member. Commands that are applied to a bundle member supersede any conflicting commands that were specified in the VC class or VC bundle.

Note Repeat Step 8 through Step 12 for each PVC member of the bundle to be created.

Step 13 

Router(config-if-atm-member)# end

Exits interface configuration mode and returns to privileged EXEC mode.

Step 1 

Router(config)# interface virtual-template number

Creates a virtual template and enters interface configuration mode.

•number—Arbitrary value to identify this virtual template.

Step 2 

Router(config-if)# bandwidth value

Specifies the bandwidth, in kbps, for the interfaces that use this virtual template:

•value—Bandwidth, in kilobits per second, for the interface.

Step 3 

Router(config-if)# service-policy input policy-name

Attaches the specified policy map to the input interface that uses this virtual template:

•policy-name—Name of the policy map that was created by the policy-map command to be used.

Step 4 

Router(config-if)# service-policy output policy-name

Attaches the specified policy map to the output interface that uses this virtual template:

•policy-name—Name of the policy map that was created by the policy-map command to be used.

Step 5 

Router(config-if)# ppp multilink [bap]

Enables multilink PPP (MLP) on the interfaces that use this virtual template:

•bap—(Optional) Enables bandwidth allocation control negotiation and dynamic allocation of bandwidth on a link, using the bandwidth allocation protocol (BAP).

Step 6 

Router(config-if)# ppp multilink fragment delay max-delay

(Optional) Configures the maximum delay for the transmission of a packet fragment on an MLP bundle.

•max-delay—Maximum amount of time, in milliseconds, that should be required to transmit a fragment. The range is from 1 to 1000, with a default value of 30 for MLP bundles.

Step 7 

Router(config-if)# ppp multilink interleave

Enables interleaving of the fragments of larger packets on an MLP bundle.

Step 8 

Router(config-if)# interface atm slot/subslot/port.subinterface point-to-point

Creates the specified point-to-point subinterface and enters interface configuration mode.

Step 9 

Router(config-if)# pvc [name] vpi/vci [ilmi | qsaal]

Configures a new ATM PVC by assigning its VPI/VCI numbers and enters ATM VC configuration mode. The valid values for vpi/vci are:

•vpi—Specifies the VPI ID. The valid range is 0 to 255.

•vci—Specifies the VCI ID. The valid range is 1 to 65535. Values 1 to 31 are reserved and should not be used, except for 5 for the QSAAL PVC and 16 for the ILMI PVC.

You can also configure the following options:

•name—(Optional) An arbitrary string that identifies this PVC.

•ilmi—(Optional) Configures the PVC to use ILMI encapsulation (default).

•qsaal—(Optional) Configures the PVC to use QSAAL encapsulation.

Note When using the pvc command, remember that the vpi/vci combination forms a unique identifier for the interface and all of its subinterfaces. If you specify a vpi/vci combination that has been used on another subinterface, the Cisco IOS software assumes that you want to modify that PVC's configuration and automatically switches to its parent subinterface.

Step 10 

Router(config-if-atm-vc)# protocol ppp virtual-template number

Configures the PVC for PPP with the parameters from the specified virtual template.

Step 11 

Router(config-if-atm-vc)# end

Exits interface configuration mode and returns to privileged EXEC mode.

Step 1 

Router(config)# interface atm slot/subslot/port
or
Router(config)# interface virtual-template number
or
Router(config)# interface dialer number

Enters interface configuration mode for an interface on the ATM SPA, or for a virtual template or dialer template interface.

Step 2 

Router(config-if)# ip rcp header-compression [passive]

Enables RCP header compression.

•passive—(Optional) Compresses outgoing RCP packets only if incoming RCP packets on the same interface are compressed. The default compresses all RCP packets on the interface.

Step 3 

Router(config-if)# ip tcp header-compression [passive]

Enables TCP header compression.

•passive—(Optional) Compresses outgoing TCP packets only if incoming TCP packets on the same interface are compressed. The default compresses all TCP packets on the interface.

Note By default, RCP and TCP header compression are enabled on ATM interfaces when they are configured with an IP address. You do not need to give the ip rcp header-compression and ip tcp header-compression commands unless you have previously disabled these features, or you want to use the passive options.

Step 4 

Router(config-if)# ip rcp compression-connections number

Specifies the total number of RCP header compression connections that can be supported on the interface.

•number—Number of RCP header compression connections. The valid range is 3 to 1000, with a default of 32 connections (16 calls).

Step 5 

Router(config-if)# ip tcp compression-connections number

Specifies the total number of TCP header compression connections that can be supported on the interface.

•number—Number of TCP header compression connections. The valid range is 3 to 1000, with a default of 32 connections (16 calls).

Step 6 

Router(config-if)# end

Exits interface configuration mode and returns to privileged EXEC mode.

Step 1 

Router(config)# interface loopback interface-number

Creates a loopback interface and enters interface configuration mode:

•interface-number—An arbitrary value from 0 to 2,147,483,647 that uniquely identifies this loopback interface.

Step 2 

Router(config-if)# ip address ip-address mask [secondary]

Specifies the IP address and subnet mask for this loopback interface. If the Working and Protect interfaces are on the same router, this IP address should be in the same subnet as the Working interface. If the Working and Protect interfaces are on different routers, this IP address should be in the same subnet as the Ethernet interface that provides the connectivity between the two routers.

Repeat this command with the secondary keyword to specify additional IP addresses to be used for this interface.

Step 3 

Router(config-if)# interface atm slot/subslot/port

Enters interface configuration mode for the Working interface on the ATM SPA.

Step 4 

Router(config-if)# ip address ip-address mask [secondary]

Specifies the IP address and subnet mask for the Working interface.

Repeat this command with the secondary keyword to specify additional IP addresses to be used for the interface.

Step 5 

Router(config-if)# aps group group-number

Enables the use of the APS Protect Group Protocol for this Working interface.

•group-number—Unique number identifying this pair of Working and Protect interfaces.

Note The aps group command is optional if this is the only pair of Working and Protect interfaces on the router, but is required when you configure more than one pair of Working and Protect interfaces on the same router.

Step 6 

Router(config-if)# aps working circuit-number

Identifies the interface as the Working interface.

•circuit-number—Identification number for this particular channel in the APS pair. Because only 1+1 redundancy is supported, the only valid values are 0 or 1, and the Working interface defaults to 1.

Step 7 

Router(config-if)# aps authentication security-string

(Optional) Specifies a security string that must be included in every OOB message sent between the Working and Protect interfaces.

•security-string—Arbitrary string to be used as a password between the Working and Protect interfaces. This string must match the one configured on the Protect interface.

Step 8 

Router(config-if)# interface atm slot/subslot/port

Enters interface configuration mode for the Protect interface on the ATM SPA.

Step 9 

Router(config-if)# ip address ip-address mask [secondary]

Specifies the IP address and subnet mask for the Protect interface.

Note This should be the same address that was configured on the Working interface in Step 4.

Repeat this command with the secondary keyword to specify additional IP addresses to be used for the interface. These should match the secondary IP addresses that are configured on the Working interface.

Step 10 

Router(config-if)# aps group group-number

Enables the use of the APS Protect Group Protocol for this Protect interface.

•group-number—Unique number identifying this pair of Working and Protect interfaces.

Note The aps group command is optional if this is the only pair of Working and Protect interfaces on the router, but is required when you configure more than one pair of Working and Protect interfaces on the same router.

Step 11 

Router(config-if)# aps protect circuit-number ip-address

Identifies this interface as the Protect interface:

•circuit-number—Identification number for this particular channel in the APS pair. Because only 1+1 redundancy is supported, the only valid values are 0 or 1, and the Protect interface defaults to 0.

•ip-address—IP address for the loopback interface that was configured in Step 2. The Protect interface uses this IP address to communicate with the Working interface.

Note If you do not want to use a loopback interface for this configuration, this IP address should be the address of the Working interface if the Protect and Working interfaces are on the same router. If the Working and Protect interfaces are on different routers, this should be the IP address of the Ethernet interface that provides interconnectivity between the two routers.

Step 12 

Router(config-if)# aps authentication security-string

(Optional) Specifies a security string that must be included in every OOB message sent between the Working and Protect interfaces.

•security-string—Arbitrary string to be used as a password between the Working and Protect interfaces. This string must match the one configured on the Working interface.

Step 13 

Router(config-if)# aps revert minutes

(Optional) Enables the Protect interface to automatically switch back to the Working interface after the Working interface has been up for a specified number of minutes.

•minutes—Number of minutes until the interface is switched back to the Working interface after the Working interface comes back up.

Note If this command is not given, you must manually switch back to the Working interface using either the aps force circuit-number or the aps manual circuit-number command.

Step 14 

Router(config-if)# end

Exits interface configuration mode and returns to privileged EXEC mode.

Step 1 

Router(config)# interface atm slot/subslot/port

Enters interface configuration mode for the indicated port on the specified ATM SPAs.

Step 2 

Router(config-if)# atm clock internal

(Optional) Configures the interface to use its own internal (onboard) clock to clock transmitted data. The default (no atm clock internal) configures the interface to use the transmit clock signal that is recovered from the receive data stream, allowing the switch to provide the clocking source.

Step 3 

Router(config-if)# atm framing {sdh | sonet}

(Optional) Configures the interface for either SDH or SONET framing. The default is SONET.

Step 4 

Router(config-if)# [no] atm sonet report {all | b1-tca | b2-tca | b3-tca | default | lais | lrdi | pais | plop | pplm | prdi | ptim | puneq | sd-ber | sf-ber | slof | slos}

(Optional) Enables ATM SONET alarm reporting on the interface. The default is for all reports to be disabled. You can enable an individual alarm, or you can enable all alarms with the all keyword.

Note This command also supports a none [ignore] option, which cannot be used with any of the other options. See the "Configuring for Transmit-Only Mode" section for details.

Step 5 

Router(config-if)# no] atm sonet-threshold {b1-tca value | b2-tca value | b3-tca value | sd-ber value | sf-ber value}

(Optional) Configures the BER threshold values on the interface. The value specifies a negative exponent to the power of 10 (10 to the power of minus value) for the threshold value. The default values are the following:

•b1-tca = 6 (10e-6)

•b2-tca = 6 (10e-6)

•b3-tca = 6 (10e-6)

•sd-ber = 6 (10e-6)

•sf-ber = 3 (10e-3)

Step 6 

Router(config-if)# end

Exits interface configuration mode and returns to privileged EXEC mode.

Step 1 

Router(config)# interface atm slot/subslot/port[.subinterface]

Enters interface (or subinterface) configuration mode for the indicated port on the specified ATM SPA.

Step 2 

Router(config-if)# no ip address ip-address mask

Removes the IP address that is assigned to this interface (if one has been configured). All IP and other Layer 3 configurations must be removed from the interface before ATM SONET alarms can be ignored.

Step 3 

Router(config-if)# atm sonet report none ignore

Disables the generation of all ATM SONET alarms, and instructs the ATM interface to remain up and operational when such alarm conditions exist.

Step 4 

Router(config-if)# end

Exits interface configuration mode and returns to privileged EXEC mode.

Step 1 

Router(config)# interface atm slot/subslot/port

Enters interface configuration mode for the indicated port on the specified ATM SPA.

Step 2 

Router(config-if)# shutdown

Shuts down the interface.

Repeat Step 1 and Step 2 for each interface to be shut down.

Step 3 

Router(config-if)# end

Exits interface configuration mode and returns to privileged EXEC mode.

Step 1 

Router(config)# hw-module subslot slot/subslot shutdown [powered | unpowered]

Shuts down the ATM SPA.

•powered—(Optional) Shuts down the ATM SPA and leaves it in the reset state. This is the default and is typically done when you want to shut down the SPA but leave it physically installed and cabled in the Catalyst 6500 Series switch.

•unpowered—(Optional) Shuts down the ATM SPA and leaves it in the unpowered state. Typically, this is done before removing the ATM SPA card from the chassis.

Note Repeat this step for each ATM SPA to be shut down.

The hw-module subslot shutdown command can be given in both the global configuration and privileged EXEC modes. If this command is given in global configuration mode, it can be saved to the startup configuration so that it is automatically executed after each reload of the switch. If given in privileged EXEC mode, the command takes effect immediately, but it is not saved to the configuration. In either case, the hw-module subslot shutdown command remains in effect during the current session of the Catalyst 6500 Series switch until it is reversed using the no form of the command.

Step 2 

Router(config)# end

Exits configuration mode and returns to privileged EXEC mode.