Configuring the OC-12 ATM Line Card

This chapter describes the procedures for configuring a Cisco 10000 ESR OC-12 ATM line card (Figure 7-1). In addition, this chapter includes a table of default values and interface configuration examples. Principal ATM commands are also described.

Figure 7-1: OC-12 ATM Line Card

OC-12 ATM Line Card Default Values

Table 7-1 lists default configuration values for the OC-12 ATM line card. The commands marked with an asterisk (*) are described in the Cisco IOS Command Reference. The other commands are among those described in this chapter.

This table includes the command used to modify a default value, and provides information about values to set on the remote end of the connection.

Table 7-1: OC-12 ATM Line Card Defaults

Command Name Default Setting Command Syntax Remote Side Setting

mtu (maximum transmission unit)*

9180 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}]

—

pvc encapsulation

aal5snap

encapsulation [aal5snap | aal5mux ip]

same

Command Name	Default Setting	Command Syntax	Remote Side Setting
mtu (maximum transmission unit)*	9180 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}]	—
pvc encapsulation	aal5snap	encapsulation [aal5snap \| aal5mux ip]	same

OC-12 ATM Line Card Syntax

To specify an interface number in a configuration command, use the syntax in Table 7-2 to identify interfaces on the OC-12 ATM line card.

Table 7-2: OC-12 ATM Interface Syntax
Type of Interface
Slot
Subslot
Port
Subinterface

OC-12 main interface

1 to 8/

0/

0.

—

OC-12 subinterface

1 to 8/

0/

0.

1 to 4294967295

**Table 7-2: OC-12 ATM Interface Syntax**
Type of Interface	Slot	Subslot	Port	Subinterface
OC-12 main interface	1 to 8/	0/	0.	—
OC-12 subinterface	1 to 8/	0/	0.	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)#

OC-12 ATM Line Card Interface Configuration Samples

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

Creating a Subinterface

Use the following procedure to create a subinterface.

Step 1 Divide 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 an OC-12 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 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 interface 2/0/0.1. To enter this interface, use the following command:

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

Router(config-subif)#

Creating a PVC

You can create up multiple PVCs on the OC-12 ATM 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 creates 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 Assign a peer IP address to the PVC using the protocol ip configuration subcommand, as 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.

Step 1 To create a PVC boilerplate, use the global configuration mode vc-class atm command. The following example creates 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 named boston. This example shows how to specify that the class uses AAL5+MUX encapsulation and configure a variable bit rate-nonreal 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 OC-12 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 OC-12 ATM line card.

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

Completing a Configuration

This section offers general information on completing a configuration of an OC-12 ATM line card.

Step 1 After you configure the interfaces for ATM, you may need to enter interface configuration mode and specify routing protocols, network addresses, and so on.

Step 2 After you have included 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.

OC-12 ATM Commands

The OC-12 ATM line card consists of a single OC-12 interface. You can put all the PVCs on this interface, or you can create subinterfaces. This section describes the principal commands for customizing interfaces and PVCs:

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 word that describes the class.

After you create the class, you enter VC class configuration mode. In this mode, you describe the action you want the class to take by entering commands and 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

Use the interface command to divide the OC-12 ATM interface into multiple subinterfaces to simplify management of the card, create interfaces with different MTU sizes, and 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 8
subslot and port are both 0
subinterface is a number from 1 to 4294967295
type is 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 for an OC-12 ATM line card in slot 1.

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

Enter an existing subinterface.

Router(config)# interface atm 1/0/0.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/0.2 multipoint
Router(config-subif)#

: After creating the subinterface, you can create PVCs that go to the same network. Figure 7-2 shows a multipoint subinterface on a fully meshed network. Fully meshed indicates that any workstation can communicate with any other workstation.

Figure 7-2: Multipoint ATM Configuation

Table 7-3 provides the configuration commands used to configure the multipoint connections in the network shown in Figure 7-2.

Table 7-3: Multipoint Configuration Example

Router A Router B Router C

interface atm 4/0/0.2 multi   ip address 131.108.168.1
   255.255.255.0   pvc 0/35   protocol ip 131.108.168.2
   broadcast   pvc 0/36   protocol ip 131.108.168.3
   broadcast
interface atm 2/0/0.1 multi   ip address 131.108.168.2
   255.255.255.0   pvc 0/35   protocol ip 131.108.168.1
   broadcast   pvc 0/37   protocol ip 131.108.168.3
   broadcast
interface atm 5/0/0.1 multi   ip address 131.108.168.3
   255.255.255.0   pvc 0/36   protocol ip 131.108.168.1
    broadcast   pvc 0/37   protocol ip 131.108.168.2
    broadcast

Router A	Router B	Router C
interface atm 4/0/0.2 multi ip address 131.108.168.1 255.255.255.0 pvc 0/35 protocol ip 131.108.168.2 broadcast pvc 0/36 protocol ip 131.108.168.3 broadcast	interface atm 2/0/0.1 multi ip address 131.108.168.2 255.255.255.0 pvc 0/35 protocol ip 131.108.168.1 broadcast pvc 0/37 protocol ip 131.108.168.3 broadcast	interface atm 5/0/0.1 multi ip address 131.108.168.3 255.255.255.0 pvc 0/36 protocol ip 131.108.168.1 broadcast pvc 0/37 protocol ip 131.108.168.2 broadcast

Attaching an ATM VC Class to an Interface

To attach an ATM VC class to an interface, use the class-int command. 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 299,520 Kbps and you can also enter 599,040 Kbps. The PVP peak rate value supersedes all cell rate values set for VBR-NRT PVCs.
no-f4-oam (optional) restricts the PVP from passing operations/administration/maintenance (OAM) packets. When you create a PVP, the system creates 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 50000 Kbps. The subsequent VCs created 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

Creating a PVC

You can create a 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 of 0.

vci_value is in the range from 1 to 65535. The VCI value should be at least 33, because all of the lower-numbered PVCs are generally used for specific purposes.

word is a name referring to this connection.

the 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. It is highly recommended that you use this argument with PVC 0/16. For more information about activating ILMI, see the section "Activating ATM ILMI PVC Discovery" section.

By default, the pvc command creates a UBR PVC; to create a VBR-NRT PVC, see the "Configuring VBR-NRT" section.

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

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 the 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. In order for peers to exchange ILMI information, you must create PVC 0/16, using the ilmi argument.

The following example disables ILMI:

Router(config)# interface atm 5/0/0

Router(config-if)# no atm ilmi-enable

Activating ATM ILMI PVC Discovery

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

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 on an OC-12 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 Keep-Alive Rate

To specify the ILMI keep-alive rate, enter the atm ilmi-keepalive command.

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 ATM Clock

To configure the clock source as internal, use the atm clock internal command:

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

To specify the ATM flag value for the s1s0 bit, use the atm flag s1s0 command. This command is typically used to meet a standards requirement or to ensure interoperability with another vendor's equipment.

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 assigns a value of 2 to the ATM flag:

Router(config)# interface atm 5/0/0

Router(config-if)# atm flag s1s0 2

Specifying ATM Scrambling

To specify an ATM scrambling mode, use the atm scrambling command:

atm scrambling [cell-payload | sts-stream]
no atm scrambling [cell-payload | sts-stream]

Where

cell-payload scrambles only the payload of the cell (not the header)
sts-stream scrambles the SONET/SDH Layer 1 stream

By default, the system scrambles both the cell payload and the STS stream.

The following example shows how to scramble the payload of the cell:

Router(config)# interface atm 5/0/0

Router(config-if)# atm scrambling cell-payload

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 (BEF) 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. A defect is a problem indication that is a candidate for an alarm.

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^-9representing 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

Running Loopbacks

You can run a loopback by using the loopback command:

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 the 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, you should use the broadcast argument if you want 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

To configure broadcast packet duplication and transmission for an ATM PVC or VC class, use the broadcast command.

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 the Protocol" section for additional information about the protocol ip command.

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

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

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

To attach an ATM VC class to a PVC, use the class-vc command.

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

To configure the variable bit rate-nonreal 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, use the vbr-nrt command. Use vbr-nrt in interface-ATM-VC 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 84 Kbps to 299,520 Kbps and 599,040 Kbps.The PCR must be at least equal to the sustainable cell rate (SCR)
sustainable is the sustainable cell rate (SCR) from 84 Kbps to 299,520 Kbps and 599,040 Kbps.
maximum is a number from 1 to 256 that 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).

You can create up to 254 VBR-NRT PVCs on an OC-12 ATM line card.

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

To specify the ATM adaptation layer (AAL) and encapsulation type for an ATM PVC or VC class, use the encapsulation command in interface-ATM-VC configuration mode or VC-class configuration mode.

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 remove an encapsulation from a PVC or VC class.

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

To enable ILMI management on an ATM PVC, use the ilmi manage command in interface-ATM-VC configuration mode or VC-class configuration mode. 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

To configure OAM retry, use the oam retry command in interface-ATM-VC configuration mode or VC-class configuration mode.

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 a VC is up.

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

: Default is 5 retries.

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

: Default is 1 second.

Use the no form of the command to remove oam retry parameters.

The following example shows how to configure OAM retry to 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 interface-ATM-VC configuration mode or VC-class configuration mode.

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

Where

manage is an optional keyword that brings the line down 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 enables OAM loopback cell and OAM management to 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     599040                UP
2/0/0          9              0   100   PVC    MUX      599040                UP
2/0/0.2        7              2    32   PVC    SNAP     599040                UP
2/0/0          8              2    33   PVC    SNAP     599040                UP
2/0/0          18             2   100   PVC    SNAP     599040                UP
2/0/0.2        6              4    24   PVC    SNAP     599040                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: 599040
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#

Table of Contents

Configuring the OC-12 ATM Line Card

Attaching an ATM VC Class to an Interface