Полезная информация

cc/td/doc/product/software/ios120/120newft/120t
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

IETF-Compliant PPP over ATM

Feature Summary

Platforms

Supported MIBs and RFCs

Configuration Tasks

Configuration Examples

Command Reference

IETF-Compliant PPP over ATM

Feature Summary

The IETF-Compliant PPP over ATM feature allows you to configure PPP over ATM using a VC multiplexed encapsulation mode. This feature complies with IETF RFC 2364 titled PPP over AAL5. In addition, Cisco  IOS Release  12.0(1)T allows you to configure multiple PPP-over-ATM PVCs on multipoint subinterfaces for IETF-Compliant PPP over ATM as well as for Cisco's proprietary PPP over ATM.

For information on configuring IETF-Compliant PPP over ATM and Cisco's proprietary PPP over ATM, refer to the "Configuration Tasks" section later in this document. For background information on Cisco's proprietary PPP over ATM, see the section "Configure PPP over ATM" in the chapter "Configuring ATM" of the Wide-Area Networking Configuration Guide for Cisco  IOS Release  12.0.

Benefits

You can configure both IETF-Compliant PPP over ATM and Cisco's proprietary PPP over ATM for multiple PPP-over-ATM PVCs on multipoint subinterfaces. This significantly increases the maximum number of PPP-over-ATM sessions running on a router.

List of Terms

Asymmetric Digital Subscriber Line (ADSL)---One of four DSL technologies. ADSL is designed to deliver more bandwidth downstream (from the central office to the customer site) than upstream. Downstream rates range from 1.5 to 9 Mbps, while upstream bandwidth ranges from 16 to 640 kbps. ADSL transmissions work at distances up to 18,000 feet (5,488 meters) over a single copper twisted pair.

Asynchronous Transfer Mode (ATM)---International standard for cell relay in which multiple service types (such as voice, video, or data) are conveyed in fixed-length (53-byte) cells. Fixed-length cells allow cell processing to occur in hardware, thereby reducing transit delays. ATM is designed to take advantage of high-speed transmission media such as E3, SONET, and T3.

command line interface (CLI)---Interface that allows the user to interact with the operating system by entering commands and optional arguments. The UNIX operating system and DOS provide CLIs.

Internet Engineering Task Force (IETF)---Task force consisting of over 80 working groups responsible for developing Internet standards. The IETF operates under the auspices of the Internet Society (ISOC).

permanent virtual circuit (PVC)---Virtual circuit that is permanently established. PVCs save bandwidth associated with circuit establishment and tear down in situations where certain virtual circuits must exist all the time. In ATM terminology, it is also called a permanent virtual connection.

Point-to-Point Protocol (PPP)---Successor to SLIP that provides router-to-router and host-to-network connections over synchronous and asynchronous circuits. Whereas SLIP was designed to work with IP, PPP was designed to work with several network layer protocols, such as IP, IPX, and ARA. PPP also has built-in security mechanisms, such as CHAP and PAP. PPP relies on two protocols: LCP and NCP.

switched virtual circuit (SVC)---Virtual circuit that is dynamically established on demand and is torn down when transmission is complete. SVCs are used in situations where data transmission is sporadic. Also called a switched virtual connection in ATM terminology.

virtual circuit (VC)---Logical circuit created to ensure reliable communication between two network devices. A virtual circuit is defined by a VPI/VCI pair, and can be either permanent (PVC) or switched (SVC). Virtual circuits are used in Frame Relay and X.25. In ATM, a virtual circuit is also called a virtual channel.

Restrictions

The following restrictions apply to this feature for Cisco  IOS Release  12.0(1)T:

Platforms

IETF-Compliant PPP over ATM is supported on these platforms:


Note On the Cisco 7200 series routers, only the ATM-CES port adapter supports this feature. On the Cisco  7500 series routers, only the ATM Interface Processor (AIP) supports this feature.

Supported MIBs and RFCs

None

Configuration Tasks

This section describes how to configure both IETF-compliant PPP over ATM and Cisco's proprietary PPP over ATM on multipoint subinterfaces. Decide which encapsulation method you want to use, then use the commands in one of the following sections:

Configure IETF-Compliant PPP over ATM on Multipoint Subinterfaces

To configure IETF-compliant PPP over ATM that supports VC multiplexed PPP payloads as specified by the IETF document called PPP over AAL5 (RFC 2364), use the following commands starting in global configuration mode:
Step Command Purpose

1 . 

interface atm slot/0.subinterface-number multipoint

or

interface atm number.subinterface-number multipoint

Specify an ATM multipoint subinterface using the appropriate format of the interface atm command.1

2 . 

pvc [name] vpi/vci

Configure the PVC.

3 . 

encapsulation aal5mux ppp virtual-template number

Configure VC multiplexed encapsulation.

1Use the interface atm slot/0 command with the AIP on Cisco 7500 series routers or with the ATM-CES port adapter on the Cisco  7200 series routers. Use the interface atm number command with the NPM on the Cisco  4500 and 4700 routers.

IETF-Compliant PPP over ATM is not supported on ATM SVCs and can only be applied to PVCs using the new ATM CLI. For general information about configuring PVCs using the new ATM CLI, see the chapter "Configuring ATM" in the Wide-Area Networking Configuration Guide for Cisco  IOS Release  12.0.

The IETF-Compliant PPP over ATM feature was designed to support installations with ADSL circuits. See the example "ADSL Termination Example" in the section "Configuration Examples" later in this document.

Configure Cisco's Proprietary PPP over ATM on  Multipoint  Subinterfaces

Multiple PPP-over-ATM PVCs on multipoint subinterfaces increases the maximum number of PPP-over-ATM sessions per router. In previous releases of Cisco's proprietary PPP over ATM, you configured ATM PVCs for PPP over ATM on point-to-point subinterfaces which required you to configure both a virtual access interface and an ATM subinterface for each PVC.

To configure Cisco's proprietary PPP over ATM on multipoint subinterfaces, use the following commands starting in global configuration mode:
Step Command Purpose

1 . 

interface atm slot/0.subinterface-number multipoint

or

interface atm number.subinterface-number multipoint

Specify an ATM multipoint subinterface using the appropriate format of the interface atm command.1

2 . 

pvc [name] vpi/vci

Configure the PVC.

3 . 

encapsulation aal5ciscoppp virtual-template number

Configure Cisco's proprietary PPP over ATM encapsulation.

1Use the interface atm slot/0 command with the AIP on Cisco 7500 series routers or with the ATM-CES port adapter on the Cisco  7200 series routers. Use the interface atm number command with the NPM on the Cisco  4500 and 4700 routers.

For more information about Cisco's proprietary PPP over ATM, refer to the section "Configure PPP over ATM" in the chapter "Configuring ATM" of the Wide-Area Networking Configuration Guide for Cisco  IOS Release  12.0.

Configuration Examples

This section provides the following examples for configuring IETF-compliant PPP over ATM and Cisco's proprietary PPP over ATM:

PPP over ATM with Differing Encapsulation Types Example

PVCs with different PPP-over-ATM encapsulation types can be configured on the same subinterface. In the following example, three PVCs are configured for PPP over ATM on subinterface ATM 2/0.1. PVC 0/60 is configured with IETF-Compliant PPP over ATM encapsulation. Its traffic shaping parameter is an unspecified bit rate with peak cell rate at 500 kbps. PVC 0/70 is also configured with IETF-Compliant PPP over ATM encapsulation, but its traffic shaping parameter is non-real-time variable bit rate, with peak cell rate at 1 Mbps, sustainable cell rate at 500 kbps, and burst cell size of 64 cells. PVC 0/80 is configured with the Cisco's proprietary PPP over ATM encapsulation. Its traffic shaping parameter is an unspecified bit rate with peak cell rate at 700 kbps.

Router(config)# interface atm 2/0.1 multipoint
Router(config-if)# pvc 0/60
Router(config-if-atm-vc)# encapsulation aal5mux ppp virtual-template 3
Router(config-if-atm-vc)# ubr 500
Router(config-if-atm-vc)# exit
 
Router(config-if)# pvc 0/70
Router(config-if-atm-vc)# encapsulation aal5mux ppp virtual-template 3
Router(config-if-atm-vc)# vbr-nrt 1000 500 64
Router(config-if-atm-vc)# exit
 
Router(config-if)# pvc 0/80
Router(config-if-atm-vc)# encapsulation aal5ciscoppp virtual-template 3
Router(config-if-atm-vc)# ubr 700
Router(config-if-atm-vc)# exit
Router(config-if)#

ADSL Termination Example

The IETF-Compliant PPP over ATM feature was designed to support installations with ADSL circuits. Figure 1 illustrates a topology for ADSL termination. This topology allows you to establish a PPP connection to a Cisco 7200 series router.

The example also illustrates the use of PPP Tunneling using L2TP to provide VPDN services, in this case for the domain cisco.com. Thus, a user who logs in as bob@cisco.com is automatically tunneled to IP address 10.1.2.3. (See the chapter Configuring Virtual Private Dialup Networks in the Cisco  IOS Release  12.0 Dial Solutions Configuration Guide for details about setting up VPDN services.)

An example of the commands that you might enter for the User, dsl7200, and cisco-gateway (as shown in Figure 1) are described below.


Figure 1: ADSL Termination


user_router Configuration
user_router(config)# interface virtual-template 1
user_router(config-if)# ip address negotiated
user_router(config-if)# ppp chap hostname user_router@cisco.com
user_router(config-if)# ppp chap password 0 cisco
user_router(config-if)# exit
 
user_router(config)# interface atm 0
user_router(config-if)# pvc 0/40
user_router(config-if-atm-vc)# encapsulation aal5mux ppp virtual-template 1
user_router(config-if-atm-vc)# exit
user_router(config-if)# exit
user_router(config)#
dsl7200 Configuration
dsl7200(config)# username user_router@cisco.com password 0 cisco
dsl7200(config)# username dsl7200 password 0 cisco
 
dsl7200(config)# vpdn enable
 
dsl7200(config)# vpdn-group 1
dsl7200(config)# request dialin l2tp ip 10.2.1.1 domain cisco.com
 
dsl7200(config)# interface virtual-template 1
dsl7200(config-if)# ppp authentication chap
dsl7200(config-if)# exit
 
dsl7200(config)# interface atm 2/0
dsl7200(config-if)# pvc 0/40
dsl7200(config-if-atm-vc)# encapsulation aal5mux ppp virtual-template 1
dsl7200(config-if-atm-vc)# exit
dsl7200(config-if)# exit
dsl7200(config)# 
cisco-gateway Configuration
cisco_gateway(config)# username cisco_gateway password 0 cisco
cisco_gateway(config)# username user_router@cisco.com password 0 cisco
 
cisco_gateway(config)# vpdn enable
 
cisco_gateway(config)# vpdn-group 1
cisco_gateway(config)# accept dialin l2tp virtual-template 1 remote dsl7200
 
cisco_gateway(config)# interface loopback 0
cisco_gateway(config-if)# ip address 10.0.1.1 255.255.255.0
cisco_gateway(config-if)# exit
 
cisco_gateway(config)# interface virtual-template 1
cisco_gateway(config-if)# ip unnumbered loopback 0
cisco_gateway(config-if)# peer default ip address pool pool-1
cisco_gateway(config-if)# exit
 
cisco_gateway(config)# ip local pool pool-1 10.1.2.1 10.1.2.254

Two Routers with Back-to-Back PVCs Example

Figure 2 illustrates an ATM interface with two PPP sessions over two PVC session connections. (See the chapter Dial-In Terminal Service and Remote Node Configuration in the Cisco  IOS Release  12.0 Dial Solutions Configuration Guide for details on PPP configuration.) The sample commands following Figure 2 establish the back-to-back router configuration.


Figure 2: Two Routers with Back-to-Back PVCs


R1 Configuration
Router1(config)# interface atm 2/0
Router1(config-if)# atm clock internal
Router1(config-if)# pvc 0/60
Router1(config-if-atm-vc)# encapsulation aal5mux ppp virtual-template 1
Router1(config-if-atm-vc)# ubr 90
Router1(config-if-atm-vc)# exit
 
Router1(config-if)# pvc 0/70
Router1(config-if-atm-vc)# encapsulation aal5mux ppp virtual-template 2
Router1(config-if-atm-vc)# vbr-nrt 90 50 1024
Router1(config-if-atm-vc)# exit
 
Router1(config-if)# interface virtual-template 1
Router1(config-if)# ip address 10.0.1.1 255.255.255.0
 
Router1(config-if)# interface virtual-template 2
Router1(config-if)# ip address 10.0.2.1 255.255.255.0
Router1(config-if)# exit
Router1(config)#
R2 Configuration
Router2(config)# interface atm 2/0.1 multipoint
Router2(config-if)# pvc 0/60
Router2(config-if-atm-vc)# encapsulation aal5mux ppp virtual-template 1
Router2(config-if-atm-vc)# ubr 90
Router2(config-if-atm-vc)# exit
 
Router2(config-if)# pvc 0/70
Router2(config-if-atm-vc)# encapsulation aal5mux ppp virtual-template 2
Router2(config-if-atm-vc)# vbr-nrt 90 50 1024
Router2(config-if-atm-vc)# exit
Router2(config-if)# exit
 
Router2(config)# interface virtual-template 1
Router2(config-if)# ip address 10.0.1.2 255.255.255.0
Router2(config-if)# exit
 
Router2(config)# interface virtual-template 2
Router2(config-if)# ip address 10.0.2.2 255.255.255.0

Multiplexed Encapsulation Using VC Class Example

In the following example, PVC 0/60 is configured on subinterface ATM 2/0.1 with a VC class attached to it. (For details on creating and applying a VC class, see the section "Configure VC Classes" in the chapter "Configuring ATM" of the Wide-Area Networking Configuration Guide for Cisco  IOS Release  12.0.) By rule of inheritance, PVC 0/60 runs with IETF-Compliant PPP over ATM encapsulation using the configuration from interface virtual-template 1. Its parameter is an unspecified bit rate with peak cell at 90 kbps.

Router(config)# interface atm 2/0.1
Router(config-if)# pvc 0/60
Router(config-if-atm-vc)# class pvc-ppp
Router(config-if-atm-vc)# exit
Router(config-if)# exit
 
Router(config)# vc-class atm pvc-ppp
Router(config-vc-class)# encapsulation aal5mux ppp virtual-template 1
Router(config-vc-class)# ubr 90
Router(config-vc-class)# exit
Router(config)#

Command Reference

This section describes enhancements to the following commands:

encapsulation

To configure the ATM adaptation layer (AAL) and encapsulation type for an ATM PVC, SVC, or VC class, use the encapsulation command in the appropriate command mode. Use the no form of this command to remove an encapsulation from a PVC, SVC, or VC class.

encapsulation aal-encap [virtual-template number]
no encapsulation aal-encap [virtual-template number]

Note To configure ILMI, QSAAL, or SMDS encapsulations for an ATM PVC, use the pvc command.

Syntax Description

aal-encap

ATM adaptation layer (AAL) and encapsulation type. When aal5mux is specified, a protocol is required. Possible values for aal-encap are as follows:

aal5ciscoppp---For Cisco's proprietary PPP over ATM. Supported on ATM PVCs only. You must use the virtual-template number argument to identify the virtual template. (If you need to establish a virtual template, use the interface virtual-template command.)

aal5mux apollo---For a multiplex (MUX)-type virtual circuit using the Apollo protocol.

aal5mux appletalk---For a MUX-type virtual circuit using the AppleTalk protocol.

aal5mux decnet---For a MUX-type virtual circuit using the DECnet protocol.

aal5mux frame---For a MUX-type virtual circuit for Frame Relay-ATM Internetworking on the Cisco MC3810.

aal5mux ip---For a MUX-type virtual circuit using the IP protocol.

aal5mux ipx---For a MUX-type virtual circuit using the IPX protocol.

aal5mux ppp---For a MUX-type virtual circuit running IETF-Compliant PPP over ATM. You must use the virtual-template number argument to identify the virtual template. (If you need to establish a virtual template, use the interface virtual-template command.)

aal5mux vines---For a MUX-type virtual circuit using the VINES protocol.

aal5mux voice---For a MUX-type virtual circuit for voice over ATM on the Cisco MC3810.

aal5mux xns---For a MUX-type virtual circuit using the XNS protocol.

aal5nlpid---Allows ATM interfaces to interoperate with High-Speed Serial Interfaces (HSSIs) that are using an ATM data service unit (ADSU) and running ATM-Data Exchange Interface (DXI). Supported on ATM PVCs only.

aal5snap---The only encapsulation supported for Inverse ARP. Logical Link Control/Subnetwork Access Protocol (LLC/SNAP) precedes the protocol datagram.

virtual-template number

(This argument is required for aal5ciscoppp and aal5mux ppp encapsulations only). Specifies which virtual template to use. (If you need to establish a virtual template, use the interface virtual-template command.)

Default

The global default encapsulation is aal5snap. See the "Usage Guidelines" section for other default characteristics.

Command Mode

Interface-ATM-VC configuration (for an ATM PVC or SVC)

VC-class configuration (for a VC class)

Usage Guidelines

This command first appeared in Cisco IOS Release 11.3 T.

Use of one of the aal5mux encapsulation options to dedicate the specified PVC to a single protocol; use the aal5snap encapsulation option to multiplex two or more protocols over the same PVC. Whether you select aal5mux or aal5snap encapsulation might depend on practical considerations, such as the type of network and the pricing offered by the network. If the network's pricing depends on the number of PVCs set up, aal5snap might be the appropriate choice. If pricing depends on the number of bytes transmitted, aal5mux might be the appropriate choice because it has slightly less overhead.

When configuring Cisco's proprietary PPP over ATM, specify the aal5ciscoppp encapsulation for the aal-encap argument. For VC multiplexed IETF-Compliant PPP over ATM, use the aal5mux ppp encapsulation. When you use either one of these encapsulations, you must also use the virtual-template number argument.

It is possible to implicitly create a virtual template when configuring PPP over ATM. In other words, if the parameters of the virtual template are not explicitly defined before configuring the ATM PVC, the PPP interface will be brought up using default values from the virtual template identified. However, some parameters (such as an IP address) take effect only if they are specified before the PPP interface comes up. Therefore, we recommend that you explicitly create and configure the virtual template before configuring the ATM PVC to ensure such parameters take effect.

Although you may assign an explicit network layer address to a virtual-template interface, we recommend that you consider two other procedures. One procedure is to use AAA to assign an address to the virtual-access interface created from the virtual-template, instead of configuring any network-layer address on the virtual-template. The other procedure is to use an unnumbered IP address on the virtual-template.

When you use virtual-profiles in PPP over ATM, fast-switching is supported.

It is currently not possible to disable a virtual-access on an individual basis. To achieve a similar effect, either delete the relevant RADIUS user entries or deconfigure the VC associated with the virtual-access.

If the encapsulation command is not explicitly configured on an ATM PVC or SVC, the VC inherits the following default configuration (listed in order of next highest precedence):

Example

The following example configures an ATM PVC with VPI 0 and VCI 33 for a MUX-type encapsulation using IP:

pvc 0/33
encapsulation aal5mux ip

show atm pvc

To display all ATM PVCs and traffic information, use the show atm pvc privileged EXEC command.

show atm pvc [vpi/vci | name | interface atm interface_number | ppp]

Syntax Description

vpi/vci

(Optional) The ATM VPI and VCI numbers. If you do not use the slash character (/) and vpi value, the vpi value defaults to  0.

name

(Optional) Name of the PVC.

interface atm interface_number

(Optional) Interface number or subinterface number of the PVC. Displays all PVCs on the specified interface or subinterface.

The interface-number uses one of the following formats, depending on what router platform you are using:

· For the AIP on Cisco 7500 series routers; For the ATM port adapter, ATM-CES port adapter, and enhanced ATM port adapter on Cisco  7200 series routers; For the 1-port ATM-25 network module on Cisco  2600 and 3600 series routers: slot/0[.subinterface-number multipoint]

· For the ATM port adapter and enhanced ATM port adapter on Cisco 7500 series routers: slot/port-adapter/0[.subinterface-number multipoint]

· For the NPM on Cisco 4500 and 4700 routers: number[.subinterface-number multipoint]

For a description of these arguments, refer to the interface atm command.

ppp

(Optional) Displays each PVC configured for PPP over ATM. See the fourth sample display below.

Command Mode

Privileged EXEC

Usage Guidelines

This command first appeared in Cisco IOS Release 11.3 T.

If the vpi/vci or name is not specified, the output of this command is the same as that of the show atm vc command but only the configured PVCs are displayed. See the first sample output below.

If the vpi/vci or name is specified, the output of this command is the same as the show atm vc vcd command, plus extra information related to PVC management including connection name, detailed states, and OAM counters. See the second sample output below.

If the interface atm interface-number option is included in the command, all PVCs under that interface or subinterface are displayed. See the third sample output below.

Sample Displays

The following is sample output from the show atm pvc command:

Router# show atm pvc
 
	VCD/					Peak	Avg/Min	Burst	
Interface	Name	VPI	VCI	Type	Encaps	Kbps	Kbps	Cells	Sts
2/0	1	0	5	PVC	SAAL	155000	155000		UP
2/0	2	0	16	PVC	ILMI	155000	155000		UP
2/0.2	101	0	50	PVC	SNAP	155000	155000		UP
2/0.2	102	0	60	PVC	SNAP	155000	155000		DOWN
2/0.2	104	0	80	PVC	SNAP	155000	155000		UP
2/0	hello	0	99	PVC	SNAP	1000			UP
 

The following is sample output from the show atm pvc command with the VPI and VCI specified:

Router# show atm pvc 0/99
 
ATM 2/0.2: VCD 102, VPI: 0, VCI: 60
UBR, PeakRate: 155000
AAL5-LLC/SNAP, etype:0x0, Flags: 0xC20, VCmode: 0x1
OAM frequency: 3 second(s), OAM retry frequency: 1 second(s)
OAM up retry count: 3, OAM down retry count: 5
OAM Loopback status: OAM Sent
OAM VC state: Not Verified
ILMI VC state: Not Managed
VC is managed by OAM
InARP frequency: 15 minute(s)
InPkts: 1, OutPkts: 1, InBytes: 32, OutBytes: 32
InPRoc: 1, OutPRoc: 0, Broadcasts: 0
InFast: 0, OutFast:0, InAS: 0, OutAS: 0
OAM cells received: 14
F5 InEndloop: 14, F5 InSegloop: 0, F5 InAIS: 0, F5 InRDI: 0
F4 InEndloop: 0, F4 InSegloop: 0, F4 InAIS: 0, F4 InRDI: 0
OAM cells sent: 25
F5 OutEndloop: 25, F5 OutSegloop: 0, F5 OutRDI: 0
OAM cell drops: 0
PVC Discovery: NOT_VERIFIED
Status: DOWN, State: NOT_VERIFIED
 

The following is sample output from the show atm pvc command with the ATM subinterface specified:

Router# show atm pvc interface atm 2/0.2
 
	VCD/					Peak	Avg/Min	Burst	
Interface	Name	VPI	VCI	Type	Encaps	Kbps	Kbps	Cells	Sts
2/0.2	101	0	50	PVC	SNAP	155000	155000		UP
2/0.2	102	0	60	PVC	SNAP	155000	155000		DOWN
2/0.2	104	0	80	PVC	SNAP	155000	155000		UP
 
 

The following is sample output from the show atm pvc command with PPP specified:

Router# show atm pvc ppp
 
ATM Int.	Name	VPI	VCI	Type	VCst	VA	VASt
2/0.1	10	0	60	PVC	UP	1	UP

The following is sample output from the show atm pvc command that shows the virtual access state:

stirling# show atm pvc 0/100
ATM 2/0.100: VCD 100, VPI: 0, VCI: 100
UBR, PeakRate: 155000, Average Rate: 155000
AAL5-CISCOPPP, etype:0x9, Flags: 0xC29, VCmode: 0xE000
OAM frequency: 0 second(s), OAM retry frequency: 0 second(s)
OAM up retry count: 0, OAM down retry count: 0
OAM Loopback status: OAM Disabled
OAM VC state: Not Managed
ILMI VC state: Not Managed
InARP DISABLED
InPkts: 0, OutPkts: 22, InBytes: 0, OutBytes: 308
InPRoc: 0, OutPRoc: 22, Broadcasts: 0
InFast: 0, OutFast: 0, InAS: 0, OutAS: 0
OAM cells received: 0
F5 InEndloop: 0, F5 InSegloop: 0, F5 InAIS: 0, F5 InRDI: 0
F4 InEndloop: 0, F4 InSegloop: 0, F4 InAIS: 0, F4 InRDI: 0
OAM cells sent: 0
F5 OutEndloop: 0, F5 OutSegloop: 0, F5 OutRDI: 0
OAM cell drops: 0
Status: UP
PPP: Virtual-Access 1 from Virtual-Template 1
	

Table 1 describes significant fields shown in the displays.

Table 1: Show ATM PVC Field Descriptions
Field Description

ATM Int.

ATM interface on which the PVC is configured.

Interface

Interface and subinterface slot and port.

VCD/Name

Virtual circuit descriptor (virtual circuit number). The connection name is displayed if a name for the VC was configured using the pvc command.

VPI

Virtual path identifier.

VCI

Virtual channel identifier.

Type

Type of PVC detected from PVC discovery, either PVC-D, PVC-L, or PVC-M.

  • PVC-D indicates a PVC created due to PVC discovery.

  • PVC-L indicates that the corresponding peer of this PVC could not be found on the switch.

  • PVC-M indicates that some or all of the QOS parameters of this PVC mismatch that of the corresponding peer on the switch.

Encaps

Type of ATM adaptation layer (AAL) and encapsulation.

Peak

or

PeakRate

Kilobits per second transmitted at the peak rate.

Avg/Min

or

Average Rate

Kilobits per second transmitted at the average rate.

Burst Cells

Value that equals the maximum number of ATM cells the virtual circuit can transmit at peak rate.

Sts or Status

Status of the VC connection.

  • UP indicates that the connection is enabled for data traffic.

  • DOWN indicates that the connection is not ready for data traffic. When the Status field is DOWN, a State field is shown. See a description of the different values for this field listed later in this table.

  • INACTIVE indicates that the interface is down.

VCSt

Virtual circuit state.

VA

Virtual access interface number.

VASt

Virtual access interface state.

Connection Name

The name of the PVC.

UBR, UBR+, or VBR-NRT

UBR---Unspecified Bit Rate QOS is specified for this PVC. See the ubr command for further information.

UBR+---Unspecified Bit Rate QOS is specified for this PVC. See the ubr+ command for further information.

VBR-NRT---Variable Bit Rate-Non Real Time QOS rates are specified for this PVC. See the vbr-nrt command for further information.

etype

Encapsulation type.

Flags

Bit mask describing virtual circuit information. The flag values are summed to result in the displayed value.

0x40---SVC

0x20---PVC

0x10---ACTIVE

0x0---AAL5-SNAP

0x1---AAL5-NLPID

0x2---AAL5-FRNLPID

0x3---AAL5-MUX

0x4---AAL3/4-SMDS

0x5---QSAAL

0x6---ILMI

0x7---AAL5-LANE

0x9---AAL5-CISCOPPP

VCmode

AIP-specific or NPM-specific register describing the usage of the virtual circuit. This register contains values such as rate queue, peak rate, and AAL mode, which are also displayed in other fields.

OAM frequency

Number of seconds between sending OAM loopback cells.

OAM retry frequency

The frequency (in seconds) that end-to-end F5 loopback cells should be transmitted when a change in UP/DOWN state is being verified. For example, if a PVC is up and a loopback cell response is not received after the frequency (in seconds) specified using the oam-pvc command, then loopback cells are sent at the retry-frequency to verify whether or not the PVC is down.

OAM up retry count

Number of consecutive end-to-end F5 OAM loopback cell responses that must be received in order to change a PVC state to up. Does not apply to SVCs.

OAM down retry count

Number of consecutive end-to-end F5 OAM loopback cell responses that are not received in order to change a PVC state to down or tear down an SVC.

OAM Loopback status

Status of end-to-end F5 OAM loopback cell generation for this VC. This field has one of the following values:

  • OAM Disabled---End-to-End F5 OAM loopback cell generation is disabled.

  • OAM Sent---OAM cell was sent.

  • OAM Received---OAM cell was received.

  • OAM Failed---OAM reply was not received within the frequency period or contained bad correlation tag.ssss

OAM VC state

This field has one of the following states for this VC:

  • AIS/RDI---The VC received AIS/RDI cells. End-to-end F5 OAM loopback cells are not sent in this state.

  • Down Retry---An OAM loopback failed. End-to-end F5 OAM loopback cells are sent at retry frequency to verify the VC is really down. After down-count unsuccessful retries, the VC goes to the Not Verified state.

  • Not Managed---VC is not being managed by OAM.

  • Not Verified---VC has not been verified by end-to-end F5 OAM loopback cells. AIS and RDI conditions are cleared.

  • Up Retry---An OAM loopback was successful. End-to-end F5 OAM loopback cells are sent at retry frequency to verify the VC is really up. After up-count successive and successful loopback retries, the VC goes to the Verified state.

  • Verified---Loopbacks are successful. AIS/RDI cell was not received.

ILMI VC state

This field has one of the following states for this VC:

  • Not Managed---VC is not being managed by ILMI.

  • Not Verified---VC has not been verified by ILMI.

  • Verified---VC has been verified by ILMI.

VC is managed by OAM/ILMI

VC is managed by OAM and/or ILMI.

InARP frequency

Number of minutes for the Inverse ARP time period.

InARP DISABLED

InARP is disabled.

InPkts

Total number of packets received on this virtual circuit. This number includes all fast-switched and process-switched packets.

OutPkts

Total number of packets sent on this virtual circuit. This number includes all fast-switched and process-switched packets.

InBytes

Total number of bytes received on this virtual circuit. This number includes all fast-switched and process-switched bytes.

OutBytes

Total number of bytes sent on this virtual circuit. This number includes all fast-switched and process-switched bytes.

InPRoc

Number of process-switched input packets.

OutPRoc

Number of process-switched output packets.

Broadcasts

Number of process-switched broadcast packets.

InFast

Number of fast-switched input packets.

OutFast

Number of fast-switched output packets.

InAS

Number of autonomous-switched or silicon-switched input packets.

OutAS

Number of autonomous-switched or silicon-switched output packets.

OAM cells received

Total number of OAM cells received on this virtual circuit.

F5 InEndloop

Number of end-to-end F5 OAM loopback cells received.

F5 InSegloop

Number of segment F5 OAM loopback cells received.

F5 InAIS

Number of F5 OAM AIS cells received.

F5 InRDI

Number of F5 OAM RDI cells received.

F4 InEndloop

Number of end-to-end F4 OAM loopback cells received.

F4 InSegloop

Number of segment F4 OAM loopback cells received.

F4 InAIS

Number of F4 OAM AIS cells received.

F4 InRDI

Number of F4 OAM RDI cells received.

OAM cells sent

Total number of OAM cells sent on this virtual circuit.

F5 OutEndloop

Number of end-to-end F5 OAM loopback cells sent.

F5 OutSegloop

Number of segment F5 OAM loopback cells sent.

F5 OutRDI

Number of F5 OAM RDI cells sent.

OAM cell drops

Number of OAM cells dropped (or flushed).

PVC Discovery

NOT_VERIFIED---This PVC is manually configured on the router and not yet verified with the attached adjacent switch.

WELL_KNOWN---This PVC has a VCI value of 0 through 31.

DISCOVERED---This PVC is learned from the attached adjacent switch via ILMI.

MIXED---Some of the traffic parameters for this PVC were learned from the switch via ILMI.

MATCHED---This PVC is manually configured on the router, and the local traffic shaping parameters match the parameters learned from the switch.

MISMATCHED---This PVC is manually configured on the router, and the local traffic shaping parameters do not match the parameters learned from the switch.

LOCAL_ONLY---This PVC is configured locally on the router and not on the remote switch.

Status

When the Status field indicates UP, the VC is established. When the Status field indicates DOWN, refer to the State field for further information about the VC state. The State field values are described later in this table.

State

When the Status field is UP, this field does not appear. When the Status field is DOWN or INACTIVE, the State field appears with one of the following values:

NOT_VERIFIED---The VC has been established successfully; Waiting for OAM (if enabled) and ILMI (if enabled) to verify that the VC is up.

NOT_EXIST---VC has not been created.

HASHING_IN---VC has been hashed into a hash table.

ESTABLISHING---Ready to establish VC connection.

MODIFYING---VC parameters have been modified.

DELETING---VC is being deleted.

DELETED---VC has been deleted.

NOT_IN_SERVICE---ATM interface is shut down.

PPP:

For PPP over ATM, indicates the virtual access interface number and virtual template number being used.


hometocprevnextglossaryfeedbacksearchhelp
Posted: Mon Jan 25 10:19:27 PST 1999
Copyright 1989-1999©Cisco Systems Inc.