Cisco 10000 Series Router Line Card Configuration Guide
4-Port OC-3/STM-1 ATM Line Card Configuration

Table Of Contents

4-Port OC-3/STM-1 ATM Line Card Configuration

Software Support

Checking Hardware and Software Compatibility

Default Values

Line Card VC Limitations

Interface Syntax

Interface Configuration Examples

Creating a Subinterface

Creating a PVC

Creating a VC Class

Applying a VC Class

Enabling ILMI PVC Discovery

Completing a Configuration

ATM Commands

Global Configuration Command

Interface and Subinterface Commands

Creating and Entering Subinterfaces

Attaching an ATM VC Class to an Interface

Creating ATM PVPs

Creating a PVC

Enabling ATM ILMI

Activating ATM ILMI PVC Discovery

Specifying the ATM ILMI Keepalive Rate

Configuring the ATM Clock

Specifying the ATM Flag

Controlling ATM Alarm Reporting

Specifying the ATM Alarm Thresholds

Controlling the S1 SONET Overhead Byte

Running Loopbacks

ATM PVC Commands

Specifying a Protocol

Configuring a Broadcast

Configuring Inverse ARP

Attaching an ATM VC Class to a PVC

Configuring VBR-NRT

Specifying Encapsulation

Enabling ILMI Management

Configuring OAM Retry

Enabling OAM Loopback Cell Generation and Management

Useful show Commands


4-Port OC-3/STM-1 ATM Line Card Configuration


This chapter describes the procedures for configuring the Cisco 10000 series 4-Port OC-3/STM-1c ATM line card, hereafter known as the 4-Port OC-3/STM-1 ATM line card.

The 4-Port OC-3/STM-1 ATM line card is a NEBS-compliant device that performs Layer 2 Asynchronous Transfer Mode (ATM) functions. This line card receives and transmits ATM cells on each network physical interface connected to a line card port, and simultaneously transmits and receives packets from the Cisco 10000 series router backplane.

This chapter contains the following sections:

Software Support

Default Values

Line Card VC Limitations

Interface Syntax

Interface Configuration Examples

ATM Commands

Software Support

Table 1-1 shows the minimum Cisco IOS release on each release train that supports the 4-Port OC-3/STM-1 ATM line card.

Table 1-1 4-Port OC-3/STM-1 ATM Line Card Software Support 

Required PRE
Minimum Cisco IOS Releases

PRE1

Cisco IOS Release 12.0(21)SX and later releases of Cisco IOS Release 12.0SX
Cisco IOS Release 12.0(20)ST and later releases of Cisco IOS Release 12.0ST
Cisco IOS Release 12.0(22)S and later releases of Cisco IOS Release 12.0S
Cisco IOS Release 12.2(8)BZ and later releases of Cisco IOS Release 12.2BZ

PRE2

Cisco IOS Release 12.3(7)XI and later releases of Cisco IOS 12.3XI
Cisco IOS Release 12.2(15)BX and later releases of Cisco IOS Release 12.2BX
Cisco IOS Release 12.2(28)SB and later releases of Cisco IOS 12.2SB


Checking Hardware and Software Compatibility

The PRE installed in the Cisco 10000 series router chassis must support the Cisco IOS software running on the router. Use the show version command to check the PRE version installed.

To see if a feature is supported by a Cisco IOS release, to locate the software document for that feature, or to check the minimum software requirements of Cisco IOS software with the hardware installed on your router, Cisco maintains the Software Advisor tool on Cisco.com at http://www.cisco.com/pcgi-bin/Support/CompNav/Index.pl

This tool does not verify whether line cards within a system are compatible, but does provide the minimum Cisco IOS requirements for individual hardware line cards, modules, or options.

You must be a registered user on Cisco.com to access this tool.

Default Values

Table 1-2 lists default configuration values for the 4-Port OC-3/STM-1 ATM line card. This table also includes the command used to modify a default value, and provides information about values to set on the remote end of the connection.

Table 1-2 4-Port OC-3/STM-1 ATM line card Defaults 

Command Name
Default Setting
Command Syntax
Remote Side Setting

mtu (maximum transmission unit)*

4470 bytes

[no] mtu bytes

same

atm clock internal

no atm clock internal

[no] atm clock internal

opposite

loopback

loopback none

[no] loopback [line | diagnostic {parallel | path | serial}]


Line Card VC Limitations

The Cisco 10000 series router supports four ATM service categories for virtual circuits (VCs):

Constant Bit Rate (CBR)

Variable Bit Rate-non-real-time (VBR-nrt)

Unspecified Bit Rate (UBR) with a peak cell rate (PCR), referred to as shaped UBR

UBR without a PCR, referred to as unshaped UBR

The segmentation and reassembly (SAR) mechanism configures priority and additional traffic management parameters for the various ATM service categories. Table 1-3 lists the priority levels the SAR sets for the service categories.

Table 1-3 ATM Service Categories

Parameter
CBR
VBR-rt
VBR-nrt
Shaped UBR
Unshaped UBR

Priority

0

1

2

3

None


The number of SAR priority levels and the service categories supported at each priority level vary from line card to line card. For example, the 4-port OC-3 line card supports the two levels of priority and the service categories listed in Table 1-4.

The ATM line cards support a maximum number of VCs per priority. That VC limit depends on the VC limit of the SAR (SAR limit) and the number of priority levels configured. Table 1-4 describes how to determine the VC limit per priority level per port for the 4-port OC-3 line card.

Table 1-4 Maximum Number of VCs per Priority

ATM Line Card
SAR Priority Levels
VC Rate
Maximum Number of VCs per Priority

4-Port OC-3

0 = CBR, VBR-nrt VCs
1 = UBR VCs

Half line rate and below

SAR limit / number of PHYs / number of priority levels

2 priority system:

65,536 / 4 / 2 = 8192 VCs per priority level per port


Configuring more channels or VCs than there are available priority locations can cause random channels or VCs to get stuck in the SAR. This occurs when an active channel tries to reschedule itself, but no priority locations are available. Therefore, the channel cannot find a place to reschedule itself, which results in a lost event for the channel, and the channel becomes stuck in the SAR.

On the PRE2, when a VC becomes stuck in the SAR, the PRE2 scheduler stops forwarding traffic on only the VC that is stuck in the SAR; the other VCs still carry traffic. On the PRE3, the PRE3 scheduler stops forwarding traffic on all the VCs configured on that ATM line card.

Interface Syntax

To specify an interface number in a configuration command, use the syntax in Table 1-5 to identify main interfaces and subinterfaces on the 4-Port OC-3/STM-1 ATM line card in Cisco Series 10000 routers.

Table 1-5 4-Port OC-3 ATM Interface Syntax 

Type of Interface
Router
Slot
Subslot
Port
Subinterface

Main interface

10008

1 through 8/

0/

0 to 3

Subinterface

10008

1 through 8/

0/

0.n to 3.n

n = 1 to 4294967295

Main interface

10005

1 through 5/

0/

0 to 3

Subinterface

10005

1 through 5/

0/

0.n to 3.n

n = 1 to 4294967295


Examples:

Modify a PVC associated with the main interface.

Router(config)# interface atm 2/0/0
Router(config-if)# pvc 0/200
Router(config-if-atm-vc)#

Modify a permanent virtual circuit (PVC) associated with a subinterface.

Router(config)# interface atm 7/0/0.1
Router(config-subif)# pvc 0/101
Router(config-if-atm-vc)#

Interface Configuration Examples

This section provides sample procedures for creating ATM subinterfaces, permanent virtual circuits (PVCs), and virtual circuit (VC) classes, and procedures for enabling Integrated Local Management Interface (ILMI).

Creating a Subinterface

Use the following procedure to create a subinterface.


Step 1 Separate the ATM interface into subinterfaces using the interface command. You can create either a point-to-point or multipoint subinterface.

In the following example, multipoint subinterface number 1 is created on port 0 of the 4-Port OC-3/STM-1 ATM line card in slot 2.

Router(config)# interface atm 2/0/0.1 multipoint
Router(config-subif)#

Step 2 Assign an IP address and subnet mask to the created interface using the ip address configuration subcommand, as shown in the following example:

Router(config-subif)# ip address 172.27.48.209 255.255.0.0
Router(config-subif)#

You have created ATM subinterface 2/0/0.1. To configure or modify this interface, use the following command:

Router(config)# interface atm 2/0/0.1
Router(config-subif)#

Creating a PVC

You can create multiple PVCs on a 4-Port OC-3/STM-1 ATM line card interface. You can create PVCs on the main interface or on a subinterface.

To create a PVC


Step 1 Enter interface or subinterface configuration mode.

Use the pvc command to specify a virtual path identifier (VPI) value between 0 and 255 and a virtual channel identifier (VCI) value between 0 and 65535. The following example shows how to create a PVC with a VPI value of 0 and VCI value of 100 on a subinterface.

Router(config-subif)# pvc 0/100
Router(config-if-atm-vc)#

Step 2 Use the protocol ip configuration subcommand to assign a peer IP address to the PVC, as shown in the following example:

Router(config-if-atm-vc)# protocol ip 172.16.32.49
Router(config-if-atm-vc)#

Creating a VC Class

This procedure demonstrates how to create an ATM VC class. An ATM VC class is a PVC boilerplate—a PVC description that you can apply to one or more PVCs.

To create a PVC boilerplate:


Step 1 Use the global configuration mode vc-class atm name command, where name is the name value you assign. The following example shows how to create the
ATM VC class named boston.

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

Step 2 Enter commands to describe the ATM VC class you named boston. This example shows how to specify that the boston class uses AAL5+MUX encapsulation with a variable bit-rate non real-time (VBR-NRT) PVC.

Router(config-vc-class)# encaps aal5mux ip
Router(config-vc-class)# vbr-nrt 30000 20000 128
Router(config-vc-class)# exit
Router(config)#

You have created a VC class named boston. The next procedure describes how to apply this class to a PVC or subinterface.

Applying a VC Class

You can apply a VC class (created in the previous procedure) to a PVC or an interface.

In the following example, the class named boston is applied to subinterface 5/0/0.1.

Router(config)# interface atm 5/0/0.1
Router(config-subif)# class-int boston
Router(config-subif)#

In the following example, the class named boston is applied to a new PVC (0/102) in subinterface 5/0/0.2.

Router(config)# interface atm 5/0/0.2
Router(config-subif)# pvc 0/102
Router(config-if-atm-vc)# class-vc boston
Router(config-if-atm-vc)#

You have completed the steps for assigning a VC class to a PVC.

Enabling ILMI PVC Discovery

You can enable ILMI to automatically discover PVCs on neighboring switches and duplicate those PVC entries on the 4-Port OC-3/STM-1 ATM line card.

To enable ILMI:


Step 1 Create PVC 0/16 on the main interface as shown in the following example:

Router(config)# interface atm 5/0/0
Router(config-if)# pvc 0/16 ilmi
Router(config-if-atm-vc)# exit
Router(config-if)#

Step 2 In the following example, ILMI PVC discovery is enabled for the selected port on the 4-Port OC-3/STM-1 ATM line card (step 1 references port 0).

Router(config-if)# atm ilmi-pvc-discovery 

You have completed the steps required for running ILMI PVC discovery. You can use the show atm pvc command to display the PVCs on the Cisco 10000 series router.

Completing a Configuration

This section offers general information on creating and completing a configuration of an 4-Port OC-3/STM-1 ATM line card.

To configure and interface:


Step 1 Enter interface configuration mode and then specify necessary parameters, such as the IP address and subnet mask.

Step 2 After you enter all of the configuration subcommands to complete the configuration, enter Ctrl-Z (hold down the Control key while you press Z) to exit configuration mode.

Step 3 Write the new configuration to memory:

Router# copy running-config startup-config

The system displays an OK message when the configuration is stored. After you have completed your configuration, you can check it by using show commands.

ATM Commands

Each 4-Port OC-3/STM-1 ATM line card permits you to specify up to four OC-3 interfaces. You can put all the PVCs on the main interfaces, or you can create associated subinterfaces. This section describes the principal commands for customizing interfaces and PVCs:

Global Configuration Command

Interface and Subinterface Commands

ATM PVC Commands

Useful show Commands

Global Configuration Command

A PVC boilerplate is a PVC description that you can apply to one or more PVCs or interfaces.

To create a PVC boilerplate, use the global configuration mode vc-class atm command:

vc-class atm class_name

Where class_name is any value that describes the VC class.

After you enter the vc-class atm command, you are placed in VC class configuration mode. In this mode, you describe the action you want the class to take by entering commands and their arguments. These commands and arguments are described in the "ATM PVC Commands" section.

In the following example, an ATM VC class named cambridge is created and defined. This example shows how to specify that the class uses AAL5+MUX encapsulation and a VBR-NRT PVC.

Router(config)# vc-class atm cambridge
Router(config-vc-class)# encaps aal5mux ip
Router(config-vc-class)# vbr-nrt 30000 20000 128
Router(config-vc-class)# exit
Router(config)#

For information on applying a VC class name, see the "Attaching an ATM VC Class to an Interface" section and the "Attaching an ATM VC Class to a PVC" section.

Interface and Subinterface Commands

This section describes principal commands for configuring ATM interfaces and subinterfaces. This section describes the following global configuration commands:

Creating and Entering Subinterfaces

Attaching an ATM VC Class to an Interface

Creating ATM PVPs

Creating a PVC

Enabling ATM ILMI

Activating ATM ILMI PVC Discovery

Specifying the ATM ILMI Keepalive Rate

Configuring the ATM Clock

Specifying the ATM Flag

Controlling ATM Alarm Reporting

Specifying the ATM Alarm Thresholds

Controlling the S1 SONET Overhead Byte

Running Loopbacks

Creating and Entering Subinterfaces

Use the interface command to segment an OC-3 ATM main interface into multiple subinterfaces to simplify line card management, to create interfaces with different MTU sizes, and to create connections to different networks.

interface atm slot/subslot/port.subinterface type
no interface atm slot/subslot/port.subinterface type

Where:

slot is 1 to 5 for a Cisco 10005 router

slot is 1 to 8 for a Cisco 10008 router

subslot is always 0 for a full-height line card

port is 0 to 3

subinterface is a value from 1 to 4294967295

type is always point-to-point or multipoint

To enter the subinterface at a later time, you do not need to specify the type.

To remove a subinterface and its PVCs, use the no interface command. To change a subinterface type, you must first remove the subinterface.

Examples:

Create subinterface number 1 at port 3 for 4-Port OC-3/STM-1 ATM line card in slot 1.

Router(config)# interface atm 1/0/3.1 point-to-point
Router(config-subif)#

Enter an existing subinterface.

Router(config)# interface atm 1/0/3.1
Router(config-subif)#

Use a multipoint subinterface.

If you want multiple PVCs to go to the same network, you must create a multipoint subinterface. For example:

Router(config)# interface atm 4/0/2.2 multipoint
Router(config-subif)#

After you create the subinterface, you can create PVCs that are attached to the same network. Figure 1-1 shows a multipoint subinterface on a fully meshed network. Fully meshed indicates that any workstation can communicate with any other workstation.

Figure 1-1 Multipoint ATM Configuration

The following example commands for routers A, B, and C show how to configure the ATM interfaces for each router shown in Figure 1-1. These examples show the configuration commands you must enter to configure the multipoint connections in that network:

Router A

Router(config) # interface atm 4/0/0.2 multi
Router(config-subif) # ip address 131.108.168.1 255.255.255.0
Router(config-subif) # pvc 0/35
Router(config-if-atm-vc) # protocol ip 131.108.168.2 broadcast
Router(config-if-atm-vc)# en
Router(config-subif) # pvc 0/36
Router(config-if-atm-vc) # protocol ip 131.108.168.3 broadcast
Router(config-if-atm-vc)# en
Router(config-subif) # en

Router B

Router(config) # interface atm 2/0/0.1 multi
Router(config-subif) # ip address 131.108.168.2 255.255.255.0
Router(config-subif) # pvc 0/35
Router(config-if-atm-vc) # protocol ip 131.108.168.1 broadcast
Router(config-if-atm-vc)# en
Router(config-subif) # pvc 0/37
Router(config-if-atm-vc) # protocol ip 131.108.168.3 broadcast
Router(config-if-atm-vc)# en
Router(config-subif) # en

Router C

Router(config) # interface atm 5/0/0.1 multi
Router(config-subif) # ip address 131.108.168.3 255.255.255.0
Router(config-subif) # pvc 0/36
Router(config-if-atm-vc) # protocol ip 131.108.168.1 broadcast
Router(config-if-atm-vc)# en
Router(config-subif) # pvc 0/37
Router(config-if-atm-vc) # protocol ip 131.108.168.2 broadcast
Router(config-if-atm-vc)# ex
Router #

Attaching an ATM VC Class to an Interface

Use the class-int command to attach an ATM VC class to an interface. If you customize a PVC, its customization takes precedence over the interface class.

class-int class_name

Where class_name is the name of the class created using the global configuration class-vc atm command.

In the following example, a VC class named cambridge is created and attached to subinterface 3/0/0.1.

Router(config)# vc-class atm cambridge
Router(config-vc-class)# encaps aal5mux ip
Router(config-vc-class)# vbr-nrt 30000 20000 128
Router(config-vc-class)# exit
Router(config)# interface atm 3/0/0.1
Router(config-subif)# class-int cambridge

Creating ATM PVPs

To create a permanent virtual path (PVP) used to multiplex one or more VBR-NRT VCs, use the atm pvp interface configuration command.

atm pvp vpi peak-rate [no-f4-oam]
no atm pvp vpi

Where:

vpi is the ATM network virtual path identifier (VPI) of the VC used to multiplex the permanent virtual path. The range is 0 to 255. You must use a VPI value that is not already in use (by a VC).

peak-rate is the maximum rate in Kbps at which the PVP can transmit data. You can enter values from 84 Kbps to 74,880 Kbps, and you can also enter 149,760 Kbps. The PVP peak rate value supersedes all rate values set for VBR-NRT PVCs associated with the PVP.

no-f4-oam (optional) restricts the PVP from passing operations/administration/maintenance (OAM) packets. When you create a PVP, the system creates (by default) PVCs with VCI values of 3 and 4 for each PVP, which pass OAM packets.

To verify the configuration of a PVP, use the show atm vp exec command.

The following example shows how to create a PVP with a peak rate of 50,000 Kbps. The subsequent created VCs are multiplexed onto this virtual path.

Router(config)# interface atm 7/0/0
Router(config-if)# atm pvp 25 50000
Router(config-if)# pvc 25/100
Router(config-if-atm-vc)# vbr-nrt 10000 5000 16
Router(config-if-atm-vc)# exit
Router(config-if)# pvc 25/101
Router(config-if-atm-vc)# vbr-nrt 10000 5000 16
Router(config-if-atm-vc)# exit
Router(config-if)# pvc 25/102
Router(config-if-atm-vc)# vbr-nrt 10000 5000 16
Router(config-if-atm-vc)# exit
Router(config)#

Creating a PVC

This section describes how to create a permanent virtual circuit.


Note You can only create one PVC on a point-to-point interface. Multiple PVCs can be created on a multipoint interface.


You can establish an unspecified bit rate (UBR) PVC by entering the pvc command:

pvc [word] [vpi_value/]{vci_value} [ilmi]

Where:

vpi_value is in the range from 0 to 255. If you do not specify a VPI value, the system assigns the value 0.

vci_value is in the range 1 to 65535. The VCI value should be 33 or greater because all lower-numbered PVCs are already assigned.

word is an optional name referring to this connection.

ilmi parameter maps the ILMI channel to the PVC for this interface. You can only use this argument for PVCs created on the main interface. We recommend that you use this argument with PVC 0/16. For more information about activating ILMI, see the "Activating ATM ILMI PVC Discovery" section.

By default, the pvc command creates a UBR PVC. To specify a VBR-NRT PVC, see the "Configuring VBR-NRT" section.

Examples:

Create PVC 0/105 on the main interface.

Router(config)# interface atm 5/0/0
Router(config-if)# pvc 105
Router(config-if-atm-vc)

Create PVC 2/102 on a subinterface.

Router(config)# interface atm 5/0/0.1
Router(config-subif)# pvc 2/102
Router(config-if-atm-vc)#

Enabling ATM ILMI

Use the atm ilmi-enable interface configuration command to enable ILMI on a port.

atm ilmi-enable 
no atm ilmi-enable

The default is ILMI is enabled, but you should disable the ILMI if the peer does not support ILMI. For peers to be able to exchange ILMI information, you must create PVC 0/16 using the ilmi argument.

The following example shows how to disable ILMI:

Router(config)# interface atm 5/0/0
Router(config-if)# no atm ilmi-enable

Activating ATM ILMI PVC Discovery

This command causes ILMI-compliant devices to propagate PVCs. Use the atm ilmi-pvc-discovery interface configuration command to activate ATM PVC discovery.

atm ilmi-pvc-discovery [subinterface]
no atm ilmi-pvc-discovery [subinterface]

Where:

subinterface instructs the software to associate all PVCs with existing subinterface numbers equal to their VPI numbers. For example: PVC 2/102 would be listed under subinterface 7/0/0.2, PVC 12/156 would be listed under 7/0/0.12, and so on.


Note The subinterface argument associates PVCs only with subinterfaces that have already been created. If there is no subinterface for a VPI value, the system associates the PVC with the main interface.


The following example shows how to enable PVC discovery on the ATM main interface 7/0/0, for port 0, on a 4-Port OC-3/STM-1 ATM line card that has ILMI enabled.

Router(config)# interface atm 7/0/0
Router(config-if)# pvc 0/16 ilmi
Router(config-if-atm-vc)# exit
Router(config-if)# atm ilmi-pvc-discovery

Specifying the ATM ILMI Keepalive Rate

Use the atm ilmi-keepalive command to specify the ILMI keepalive rate.

atm ilmi-keepalive [seconds [retry counts]]

Where:

seconds is a value from 1 to 65535

retry counts is a value from 2 to 5

The default value for seconds is 5000 and for retry counts is 4.

The following example shows how to enable ILMI keepalives for the ATM interface 5/0/0:

Router(config)# interface atm 5/0/0
Router(config-if)# atm ilmi-keepalive 10000 retry 3

Configuring the ATM Clock

Use the atm clock internal command to configure the clock source as internal.

atm clock internal
no atm clock internal

The default clock setting is no atm clock internal, which means that clocking is derived from the line.

In the following example, clocking is set from the router.

Router(config)# interface atm 5/0/0
Router(config-if)# atm clock internal

Specifying the ATM Flag

This command is typically used to meet a standards requirement or to ensure interoperability with another vendor's equipment. Use the atm flag s1s0 command to specify the ATM flag value for the s1and s0 bits.

atm flag s1s0 value

Where:

s1s0 is part of the payload pointer byte

value is from 0 to 3

The default s1s0 value is 0.

The following example shows how to assign a value of 2 to the ATM flag:

Router(config)# interface atm 5/0/0
Router(config-if)# atm flag s1s0 2

Controlling ATM Alarm Reporting

To control selected SONET alarms so that they are logged to the console for an ATM interface, use the atm report interface configuration command.

atm report {b1-tca | b2-tca | b3-tca | lais | lcd | lrdi | pais | plop | prdi | rdool | 
sd-ber | sf-ber | slof | slos} 

no atm report {b1-tca | b2-tca | b3-tca | lais | lcd | lrdi | pais | plop | prdi | rdool | 
sd-ber | sf-ber | slof | slos}

Where:

b1-tca—B1 bit error rate (BER) threshold crossing alarm

b2-tca—B2 BER threshold crossing alarm

b3-tca—B3 BER threshold crossing alarm

lais—Line Alarm Indication Signal

lcd—Loss of cell delineation

lrdi—Line Remote Defect Indication

pais—Path Alarm Indication Signal

plop—Path Loss of Pointer

prdi—Path Remote Defect Indication

rdool—Receive Data Out Of Lock

sd-ber—Line bit interleave parity error (LBIP) BER in excess of signal degrade (SD) threshold

sf-ber—LBIP BER in excess of signal fail (SF) threshold

slof—Section Loss of Frame

slos—Section Loss of Signal

To disable logging of select SONET alarms, use the no form of this command.

Reporting an alarm means that the alarm can be logged to the console. Not all alarms are logged. SONET alarm hierarchy rules dictate that only the most severe alarm of an alarm group is reported. Whether an alarm is reported or not, you can view the current state of a defect by checking the Active Defects line from the show controllers atm command output.

The following example shows how to enable reporting of SD-BER and LAIS alarms on the interface:

Router(config)# interface atm 3/0/0
Router(config-if)# atm report sd-ber
Router(config-if)# atm report lais
Router(config-if)# end
Router#

Specifying the ATM Alarm Thresholds

Specify the bit error rate (BER) threshold by using the atm threshold command:

atm threshold {b1-tca | b2-tca | b3-tca | sd-ber | sf-ber} value

Where:

b1-tca—B1 BER threshold crossing alarm

b2-tca—B2 BER threshold crossing alarm

b3-tca—B3 BER threshold crossing alarm

sd-ber—Set Signal Degrade BER threshold

sf-ber—Set Signal Fail BER threshold

value is an exponential value from 10-3 to 10-9 representing the BER at which an alarm occurs.

The default for all thresholds, except sf-ber, is 10-6. The default for sf-ber is 10-3.

The following example shows how to specify the B1 BER threshold crossing alarm value of 4:

Router(config)# interface atm 5/0/0
Router(config-if)# atm threshold b1-tca 4

Controlling the S1 SONET Overhead Byte

On Cisco 10000 series routers, ATM line cards run over SONET. In most situations, the default value for the S1 SONET overhead byte (0x0) does not need to be changed. Refer to the SONET standards for information about the possible values for the S1 SONET overhead byte and the definition of each value.

Controlling a Transmitted S1 Overhead Byte

In Cisco IOS Release 12.2(28)SB, use the pos flag s1-byte tx command in interface configuration mode to control the transmission of the S1 SONET overhead byte.

pos flag s1-byte tx value

Where:

value is in the range of 0x0 to 0xF

0x0 is the default value

In the following example the S1 SONET overhead byte is set to 0xF:

pos flag s1-byte tx 0xF

Reacting to a Received S1 Overhead Byte

In Cisco IOS Release 12.2(28)SB, use the pos flag s1-byte rx-communicate command to direct the router to switch the clock source to internal when it receives an S1 SONET overhead byte with a value of 0xF. When the S1 SONET overhead byte changes from 0xF to any other value, the clock source reverts back to the clock source specified in the user configuration.

The S1 overhead byte is ignored by the receiving router unless the pos flag s1-byte rx-communicate command is issued.

pos flag s1-byte rx-communicate

no pos flag s1-byte rx-communicate

The following example directs the router to switch to internal clocking when it receives an S1 SONET overhead byte with a value of 0xF:

pos flag s1-byte rx-communicate

The default for the pos flag s1-byte rx-communicate command is disabled or off.

Running Loopbacks

Use the loopback command to run a loopback diagnostic tests.

loopback {line | diagnostic {parallel | path | serial}}
no loopback {line | diagnostic {parallel | path | serial}}

Where:

line is the line loopback

diagnostic starts an internal diagnostic loopback

parallel is the internal diagnostic parallel loopback

path is the internal diagnostic path loopback

serial is the internal diagnostic serial loopback

The following example shows hot to run the diagnostic serial loopback:

Router(config)# interface atm 5/0/0
Router(config-if)# loopback diagnostic serial

ATM PVC Commands

After you create a PVC using the pvc command, you can customize the PVC or a VC class by using the commands described in this section.

Specifying a Protocol

Configuring a Broadcast

Configuring Inverse ARP

Attaching an ATM VC Class to a PVC

Configuring VBR-NRT

Specifying Encapsulation

Enabling ILMI Management

Configuring OAM Retry

Enabling OAM Loopback Cell Generation and Management

Specifying a Protocol

Use the protocol ip command in interface-ATM-VC configuration mode or VC-class configuration mode to do one or both of the following:

Configure a static map for an ATM PVC or VC class.

Enable Inverse ARP or Inverse ARP broadcasts on an ATM PVC by either configuring Inverse ARP directly on the PVC or in a VC class (applies to IP protocols only).

protocol ip {protocol-address | inarp} [[no] broadcast]
no protocol ip {protocol-address | inarp} [[no] broadcast]

Where:

protocol-address is the peer destination address that is being mapped to a PVC.

inarp (valid only for IP protocols on PVCs) enables Inverse ARP on an ATM PVC. If you specify a protocol-address instead of inarp, Inverse ARP is automatically disabled for that protocol.

[no] broadcast (optional) indicates that this PVC sends out broadcast packets (for example, IGRP updates). Pseudo broadcasting is supported. The broadcast keyword of the protocol ip command takes precedence if you previously configured the broadcast command on the ATM PVC.

For PVCs created under point-to-point subinterfaces, broadcast is enabled by default. For PVCs created under multipoint subinterfaces, use the broadcast argument to propagate IP routes.

Use the no form of this command to remove a static map or disable Inverse ARP.


Note Use the inarp command to configure Inverse ARP frequency.


The following example shows how to specify IP protocol on an ATM PVC:

Router(config)# interface atm 5/0/0
Router(config-if)# pvc 0/105
Router(config-if-atm-vc)# protocol ip 172.16.32.49

Configuring a Broadcast

Use the broadcast command to configure broadcast packet duplication and transmission for an ATM PVC or VC class.

The broadcast command is not used to enable ATM cell-level multicast, broadcast, replication, or to set up the broadcast of user level traffic. The broadcast command indicates which PVC (or PVCs) sends out broadcast traffic. This is typically limited to traffic associated with routing protocols and routing updates (for example, OSPF hello packets).


Note The broadcast argument within the protocol ip command takes precedence over the broadcast command. See the "Specifying a Protocol" section for more information.


Use the default form of this command to restore the default behavior described below.

broadcast
no broadcast

The default is broadcast.

Use the no form of this command to disable transmission of broadcast packets.

For PVCs created under point-to-point subinterfaces, broadcast is enabled by default. For PVCs created under multipoint subinterfaces, you should use the broadcast command if you want to propagate IP routes (only the first PVC on a multipoint interface receives broadcast traffic).

The following example shows how to use the broadcast command to restore the default behavior:

Router(config)# interface atm 5/0/0.4
Router(config-subif)# pvc 0/105
Router(config-if-atm-vc)# broadcast
Router(config-if-atm-vc)#

Configuring Inverse ARP

Use the inarp command in interface-ATM-VC configuration mode or VC-class configuration mode to configure the Inverse ARP time period for an ATM PVC or VC class.

inarp minutes
no inarp minutes

Where minutes is the inverse ARP frequency from 1 to 60 minutes.

The default frequency is 15 minutes.

Use the no form of this command to restore the default inverse ARP time period behavior.


Note This command is supported only for AAL5+SNAP encapsulation (the default) when Inverse ARP is enabled. Use the encapsulation command to configure AAL5+SNAP encapsulation and the protocol command to enable Inverse ARP.


The following example shows how to specify an inverse ARP frequency of 40 minutes on an ATM PVC:

Router(config)# interface atm 5/0/0
Router(config-if)# pvc 0/105
Router(config-if-atm-vc)# inarp 40

Attaching an ATM VC Class to a PVC

Use the class-vc command to attach an ATM VC class to a PVC.

class-vc name

Where:

name is the name of the class created with the global configuration class-vc atm command.

The following example shows how to assign an ATM VC class named boston to an ATM PVC:

Router(config)# interface atm 5/0/0.4
Router(config-subif)# pvc 2/100
Router(config-if-atm-vc)# class-vc boston

Configuring VBR-NRT

Use the vbr-nrt command to configure the variable bit rate non real-time (VBR-NRT) traffic management type and specify output peak cell rate, output sustainable cell rate, and output maximum burst cell size for an ATM PVC or VC class.

You can use the vbr-nrtv command in PVC configuration mode or VC-class configuration mode.

vbr-nrt peak_cell_rate sustainable_cell_rate maximum_burst_size
no vbr-nrt peak_cell_rate sustainable_cell_rate maximum_burst_size

Where:

peak is the peak cell rate (PCR) from 38 Kbps to 149,760 Kbps. The PCR must be at least equal to the sustainable cell rate (SCR)

sustainable is the sustainable cell rate (SCR) from 38 Kbps to the PCR

maximum is a number from 1 to 65,535, which represents maximum burst size (MBS) in cells

The default class of service is unspecified bit rate (UBR) running at the maximum line rate of the physical interface.

Use the no form of this command to remove the VBR-NRT parameters and return the PVC to its default of unspecified bit rate (UBR).

The following example shows how to configure the VBR-NRT traffic parameters on an ATM PVC:

Router(config)# interface atm 5/0/0
Router(config-if)# pvc 0/105
Router(config-if-atm-vc)# vbr-nrt 50000 20000 200

Specifying Encapsulation

Use the encapsulation command in PVC configuration mode or VC-class configuration mode to specify the ATM adaptation layer (AAL) and encapsulation type for an ATM PVC or VC class.

encapsulation {aal5mux ip | aal5snap}
no encapsulation {aal5mux ip | aal5snap}

Where:

aal5mux ip is AAL5+MUX encapsulation

aal5snap is AAL5+LLC/SNAP encapsulation (the default)

Use the no form of this command to return an encapsulation to the default SNAP.

The following example shows how to specify aal5mux ip encapsulation for an ATM PVC:

Router(config)# interface atm 5/0/0.4
Router(config-subif)# pvc 0/105
Router(config-if-atm-vc)# encaps aal5mux ip

Enabling ILMI Management

Use the ilmi manage command in PVC configuration mode or VC-class configuration mode to enable ILMI management on an ATM PVC. This command changes the convergence of higher-level protocols based on link-state changes.

ilmi manage
no ilmi manage

Use the no form of this command to disable ILMI management.

The following example shows how to enable ILMI management on an ATM PVC:

Router(config)# interface atm 5/0/0
Router(config-if)# pvc 0/105
Router(config-if-atm-vc)# ilmi manage

Configuring OAM Retry

Use the oam retry command in PVC configuration mode or VC-class configuration mode to configure OAM retry.

oam retry up_value [down_value frequency]
no oam retry up_value [down_value frequency]

Where:

up_value is a number from 1 to 600 that represents the OAM retry count before declaring that a VC is up.

The default is 3 retries.

down_value is a number from 1 to 600 that represents the OAM retry count before declaring a VC is down.

The default is 5 retries.

frequency is a number from 1 to 1000 that represents the OAM retry polling frequency, in seconds.

The default is 1 second.

Use the no form of this command to return OAM retry to its default values.

The following example shows how to configure OAM retry for an ATM PVC:

Router(config)# interface atm 5/0/0
Router(config-if)# pvc 0/105
Router(config-if-atm-vc)# oam retry 10 10 5

Enabling OAM Loopback Cell Generation and Management

To enable end-to-end F5 OAM loopback cell generation and OAM management for an ATM PVC or VC class, use the oam-pvc command in PVC configuration mode or VC-class configuration mode.

oam-pvc [manage] [frequency]
no oam-pvc [manage] [frequency]

Where:

manage is an optional keyword that brings down the interface or subinterface if the PVC loopback fails.

frequency (optional) is the number of seconds between transmitting OAM loopback cells. Values range from 0 to 600 seconds.

The default value is 10 seconds.

Use the no form of this command to disable generation of OAM loopback cells and OAM management.

The following example shows how to enable OAM loopback cell generation for an ATM PVC:

Router(config)# interface atm 5/0/0
Router(config-if)# pvc 0/105
Router(config-if-atm-vc)# oam-pvc 300

Useful show Commands

show atm vc

Use the show atm vc command to display information about the VCs on the interface.

Router#show atm vc
               VCD /                                     Peak Avg/Min Burst
Interface      Name         VPI   VCI  Type   Encaps     Kbps   Kbps  Cells Sts
2/0/0          1              0    16   PVC    ILMI	149760	UP
2/0/0          9              0   100   PVC    MUX	 149760	UP
2/0/0.2        7              2    32   PVC    SNAP	149760	UP
2/0/0          8              2    33   PVC    SNAP	149760	UP
2/0/0          18             2   100   PVC    SNAP	149760	UP
2/0/0.2        6              4    24   PVC    SNAP	149760	UP
2/0/0          2             25     3   PVC    F4-OAM	 50000	UP
2/0/0          3             25     4   PVC    F4-OAM	 50000	UP
2/0/0          14            25   100   PVC    SNAP	 50000	 50000    0	UP
2/0/0          16            25   101   PVC    SNAP	 50000	 50000    0	UP
2/0/0          17            25   102   PVC    SNAP	 50000	 50000    0	UP
2/0/0          10            26     3   PVC    F4-OAM	 50000	UP
2/0/0          11            26     4   PVC    F4-OAM	50000	UP
2/0/0          12            27     3   PVC    F4-OAM	 50000	UP
2/0/0          13            27     4   PVC    F4-OAM	 50000	UP
2/0/0          19            33   100   PVC    SNAP	 10000	 8000   10	UP
Router#

show atm vp

Use the show atm vp command to display information about the VPs on the interface.

Router#show atm vp
                    Data  CES    Peak    CES 
Interface    VPI    VCs   VCs    Kbps    Kbps     Status
ATM2/0/0     25     3     0      50000   0        ACTIVE
ATM2/0/0     26     0     0      50000   0        ACTIVE
ATM2/0/0     27     0     0      50000   0        ACTIVE
Router#

show atm pvc

Use the show atm pvc vpi_number/vci_number command to display detailed information about a specific PVC.

Router#show atm pvc 0/100

ATM2/0/0: VCD: 9, VPI: 0, VCI: 100
UBR, PeakRate: 149760
AAL5-MUX, etype:0x800, Flags: 0xC23, VCmode: 0x0
OAM frequency: 0 second(s), OAM retry frequency: 1 second(s)
OAM up retry count: 3, OAM down retry count: 5
OAM Loopback status: OAM Disabled
OAM VC state: Not Managed
ILMI VC state: Not Managed
InARP DISABLED
InPkts: 0, OutPkts: 0, InBytes: 0, OutBytes: 0
InPRoc: 0, OutPRoc: 0, Broadcasts: 0
InFast: 0, OutFast: 0, InAS: 0, OutAS: 0
InPktDrops: 0, OutPktDrops: 0
Out CLP=1 Pkts: 0
OAM cells received: 0
F5 InEndloop: 0, F5 InSegloop: 0, F5 InAIS: 0, F5 InRDI: 0
OAM cells sent: 0
F5 OutEndloop: 0, F5 OutSegloop: 0, F5 OutRDI: 0
OAM cell drops: 0
PVC Discovery: NOT_VERIFIED
Status: UP
Router#