- Preface
- ATM Commands on the Cisco IOS XR Software
- Ethernet Interface Commandson the Cisco IOS XR Software
- Ethernet OAM Commands on the Cisco IOS XR Software
- Frame Relay Commands on the Cisco IOS XR Software
- Global Interface Commandsonthe Cisco IOS XR Software
- Link Bundling Commands on the Cisco IOS XR Software
- Management Ethernet Interface Commands on the Cisco IOS XR Software
- Multilink Commands on the Cisco IOS XR Software
- Null Interface Commands
- Packet-over-SONET Interface Commands on the Cisco IOS XR Software
- PPP Commands onthe Cisco IOS XR Software
- Serial Interface Commands on the Cisco IOS XR Software
- SONET Controller Commands on the Cisco IOS XR Software
- T3, E3, T1, E1 Controller Commands on the Cisco IOS XR Software
- 802.1Q VLAN Subinterface Commandsonthe Cisco IOS XR Software
- Index
- atm address-registration
- atm ilmi-config disable
- atm ilmi-keepalive
- atm ilmi-trap disable
- atm maxvpi-bits 12
- atm mcpt-timers
- atm oam flush
- cell-packing
- class-int
- class-vc
- encapsulation (ATM)
- f4oam disable
- interface atm
- l2transport (ATM)
- oam ais-rdi
- oam-pvc manage
- oam retry
- ping atm interface atm
- pvc (ATM)
- pvp (ATM)
- shape
- show atm cell-packing
- show atm class-link
- show atm ilmi-status
- show atm interface atm
- show atm pvc
- show atm pvp
- show atm vc-class
- show atm vp-tunnel
- show controllers atm
- shutdown (ATM)
- vc-class atm
- vp-tunnel
ATM Commands on the Cisco IOS XR Software
This module provides command line interface (CLI) commands for configuring ATM on your router.
- atm address-registration
- atm ilmi-config disable
- atm ilmi-keepalive
- atm ilmi-trap disable
- atm maxvpi-bits 12
- atm mcpt-timers
- atm oam flush
- cell-packing
- class-int
- class-vc
- encapsulation (ATM)
- f4oam disable
- interface atm
- l2transport (ATM)
- oam ais-rdi
- oam-pvc manage
- oam retry
- ping atm interface atm
- pvc (ATM)
- pvp (ATM)
- shape
- show atm cell-packing
- show atm class-link
- show atm ilmi-status
- show atm interface atm
- show atm pvc
- show atm pvp
- show atm vc-class
- show atm vp-tunnel
- show controllers atm
- shutdown (ATM)
- vc-class atm
- vp-tunnel
atm address-registration
To enable the router to engage in address registration and callback functions with the Interim Local Management Interface (ILMI), use the atm address-registration command in interface configuration mode. To disable ILMI address registration functions, use the no form of this command.
atm address-registration
no atm address-registration
Syntax Description
This command has no keywords or arguments.
Command Default
If ILMI is configured on a PVC and its host ATM interface, then address registration and callback function enabled on the router by default.
If ILMI is not configured on a PVC and its host ATM interface, then address registration and callback functionality is disabled on the router and must be enabled with the atm address-registration command.
Command Modes
Interface configuration (config-if)
Command History
Release |
Modification |
---|---|
Release 3.4.0 |
This command was introduced. |
Usage Guidelines
Note | The atm address-registration command is effective only when an ILMI PVC is created under the physical ATM interface. |
Task ID
Task ID |
Operations |
---|---|
atm |
read, write |
Examples
The following example shows how to enable the ATM interface 0 in slot 6 to register its address:
RP/0/0/CPU0:router# configure RP/0/0/CPU0:router(config)# interface atm 0/6/0/0 RP/0/0/CPU0:router(config-if)# atm address-registration
atm ilmi-config disable
To disable Interim Local Management Interface (ILMI) on an ATM interface, use the atm ilmi-config disable command in interface configuration mode. To re-enable ILMI on an ATM interface, use the no form of this command.
atm ilmi-config disable
no atm ilmi-config disable
Syntax Description
This command has no keywords or arguments.
Command Default
If an ILMI PVC is configured on the ATM interface, then ILMI is automatically enabled on the ATM interface that hosts that PVC.
If an ILMI PVC is not configured on the ATM interface, then ILMI is disabled by default on the ATM interface.
Command Modes
Interface configuration (config-if)
Command History
Release |
Modification |
---|---|
Release 3.4.0 |
This command was introduced. |
Usage Guidelines
Note | The atm ilmi-config disable command is effective only when an ILMI PVC is created under the physical ATM interface. |
Task ID
Task ID |
Operations |
---|---|
atm |
read, write |
Examples
The following example shows how to disable ILMI on an ATM interface:
RP/0/0/CPU0:router# configure RP/0/0/CPU0:router(config)# interface atm 0/6/0/0 RP/0/0/CPU0:router(config-if)# atm ilmi-config disable
The following example shows how to re-enable ILMI on an ATM interface:
RP/0/0/CPU0:router# configure RP/0/0/CPU0:router(config)# interface atm 0/6/0/0 RP/0/0/CPU0:router(config-if)# no atm ilmi-config disable
Related Commands
Command | Description |
Displays status information that is related to ILMI. |
atm ilmi-keepalive
To enable Interim Local Management Interface (ILMI) keepalives on an ATM interface and configure keepalive polling frequency, use the atm ilmi-keepalive command in interface configuration mode. To disable ILMI keepalives, use the no form of this command.
atm ilmi-keepalive [ act-poll-freq frequency ] [ retries count ] [ inact-poll-freq frequency ]
no atm ilmi-keepalive [ act-poll-freq frequency ] [ retries count ] [ inact-poll-freq frequency ]
Syntax Description
act-poll-freq frequency |
(Optional) Number of polling seconds between active keepalives. Range is from 1 through 65535 seconds. Default is 5 seconds. |
retries count |
(Optional) ILMI keepalive retry count. Range is from 2 through 5. Default is 4 retries. |
inact-poll-freq frequency |
(Optional) Number of polling seconds between inactive keepalives. Range is from 1 through 65535 seconds. Default is 1 second. |
Command Default
act-poll-freq frequency: 5
retries count: 4
inact-poll-freq frequency: 1
Command Modes
Interface configuration (config-if)
Command History
Release |
Modification |
---|---|
Release 3.4.0 |
This command was introduced. |
Usage Guidelines
Note | The atm ilmi-keepalive command is effective only when an ILMI PVC is created under the physical ATM interface. |
Task ID
Task ID |
Operations |
---|---|
atm |
read, write |
Examples
The following example shows how to enable ILMI keepalives for the ATM interface 0 in slot 6:
RP/0/0/CPU0:router# configure RP/0/0/CPU0:router(config)# interface atm 0/6/0/0 RP/0/0/CPU0:router(config-if)# atm ilmi-keepalive
The following example shows how to configure the ATM interface 1 in slot 6 to poll the number of inactive keepalives every 10 seconds:
RP/0/0/CPU0:router# configure RP/0/0/CPU0:router(config)# interface atm 0/6/0/1 RP/0/0/CPU0:router(config-if)# atm ilmi-keepalive inact-poll-freq 10
The following example shows how to disable ILMI keepalives for the ATM interface 0 in slot 6:
RP/0/0/CPU0:router# configure RP/0/0/CPU0:router(config)# interface atm 0/6/0/0 RP/0/0/CPU0:router(config-if)# no atm ilmi-keepalive
Related Commands
Command | Description |
Displays status information that is related to ILMI. |
atm ilmi-trap disable
To disable Interim Local Management Interface (ILMI) trap generation on an ATM interface, use the atm ilmi-trap disable command in interface configuration mode. To reenable ILMI trap generation, use the no form of this command.
atm ilmi-trap disable
no atm ilmi-trap disable
Syntax Description
This command has no keywords or arguments.
Command Default
Support for ATM ILMI trap generation is enabled.
Command Modes
Interface configuration (config-if)
Command History
Release |
Modification |
---|---|
Release 3.5.0 |
This command was introduced. |
Usage Guidelines
Task ID
Task ID |
Operations |
---|---|
atm |
read, write |
Examples
The following example shows how to disable ILMI trap generation on the ATM interface 0 in slot 6:
RP/0/0/CPU0:router# configure RP/0/0/CPU0:router(config)# interface atm 0/6/0/0 RP/0/0/CPU0:router(config-if)# atm ilmi-trap disable
The following example shows how to reenable ILMI trap generation on the ATM interface 0 in slot 6:
RP/0/0/CPU0:router# configure RP/0/0/CPU0:router(config)# interface atm 0/6/0/1 RP/0/0/CPU0:router(config-if)# no atm ilmi-trap disable
Related Commands
Command | Description |
Displays ATM-specific information about an ATM interface. |
atm maxvpi-bits 12
To enable support for the 12-bits virtual path identifier (VPI) Network-Node Interface (NNI) cell format, use the atm maxvpi-bits 12 command in interface configuration mode. To disable support for the 12-bits VPI NNI cell format, use the no form of this command.
atm maxvpi-bits 12
no atm maxvpi-bits 12
Syntax Description
This command has no keywords or arguments.
Command Default
Support for the 12-bits VPI NNI cell format is disabled.
Command Modes
Interface configuration (config-if)
Command History
Release |
Modification |
---|---|
Release 3.4.0 |
This command was introduced. |
Usage Guidelines
Note | Out of the twelve bits, four bits in the ATM UNI cell header are reserved for local standardized generic flow control (GFC). |
Task ID
Task ID |
Operations |
---|---|
atm |
read, write |
Examples
The following example shows how to enable support for the 12-bits VPI NNI cell format on the ATM interface 0 in slot 6:
RP/0/0/CPU0:router# configure RP/0/0/CPU0:router(config)# interface atm 0/6/0/0 RP/0/0/CPU0:router(config-if)# atm maxvpi-bits 12
The following example shows how to disable support for the 12-bits VPI NNI cell format on the ATM interface 1 in slot 6:
RP/0/0/CPU0:router# configure RP/0/0/CPU0:router(config)# interface atm 0/6/0/1 RP/0/0/CPU0:router(config-if)# no atm maxvpi-bits 12
Related Commands
Command | Description |
Displays ATM-specific information about an ATM interface. |
atm mcpt-timers
To define the three Maximum Cell Packing Timeout (MCPT) timers under a main ATM interface, use the atm mcpt-timers command in interface configuration mode. To return the three timers to the default configuration, use the no form of this command.
atm mcpt-timers timer-1 timer-2 timer-3
no atm mcpt-timers
Syntax Description
timer-1 |
Maximum number of microseconds to wait to complete cell packing on a single packet before that packet is transmitted. Range is from 50 through 4095.
|
||
timer-2 |
Maximum number of microseconds to wait to complete cell packing on a single packet before that packet is transmitted. Range is from 50 through 4095.
|
||
timer-3 |
Maximum number of microseconds to wait to complete cell packing on a single packet before that packet is transmitted. Range is from 50 through 4095.
|
Command Default
timer-1 : 50
timer-2 : 50
timer-3 : 50
Command Modes
Interface configuration (config-if)
Command History
Release |
Modification |
---|---|
Release 3.4.1 |
This command was introduced. |
Usage Guidelines
Use the cell-packing command to attach one of the three MCPT timers to an individual L2VPN port, PVC, or PVP. If the associated MCPT timer expires before the maximum number of cells that can be packed is reached, then the packet is transmitted with the number of cells that have been packed thus far.
Note | We recommend configuring a low, medium, and high value for the three MCPT timers to accommodate the different ATM traffic classes. Low- latency CBR traffic typically uses a low MCPT timer value, while high-latency UBR traffic typically requires a high MCPT timer value. VBR-rt and VBR-nrt traffic typically use a median MCPT timer value. |
Task ID
Task ID |
Operations |
---|---|
atm |
read, write |
Examples
The following example shows how to configure the three MCPT timers and then apply one of them to an interface with the cell-packing command:
RP/0/0/CPU0:router# configure RP/0/0/CPU0:router(config)# interface atm 0/6/0/0 RP/0/0/CPU0:router(config-if)# atm mcpt-timers 50 100 200 RP/0/0/CPU0:router(config-if)# l2transport RP/0/0/CPU0:router(config-if-l2)# cell-packing 6 1
Related Commands
Command | Description |
Configures the maximum number of cells allowed per packet, and specifies a MCPT timer for cell packing. | |
Displays ATM-specific information about an ATM interface. |
atm oam flush
To drop all current and future Operation, Administration, and Maintenance (OAM) cells received on an ATM interface, use the atm oam flush command in interface configuration mode. To receive OAM cells on an ATM interface, use the no form of this command.
atm oam flush
no atm oam flush
Syntax Description
This command has no keywords or arguments.
Command Default
The dropping of OAM cells is disabled.
Command Modes
Interface configuration (config-if)
Command History
Release |
Modification |
---|---|
Release 3.4.0 |
This command was introduced. |
Usage Guidelines
Task ID
Task ID |
Operations |
---|---|
atm |
read, write |
Examples
The following example shows how to enable the dropping of all current and future OAM cells received on the ATM interface 0 in slot 6:
RP/0/0/CPU0:router# configure RP/0/0/CPU0:router(config)# interface atm 0/6/0/0 RP/0/0/CPU0:router(config-if)# atm oam flush
The following example shows how to disable the dropping of all current and future OAM cells received on the ATM interface 1 in slot 6:
RP/0/0/CPU0:router# configure RP/0/0/CPU0:router(config)# interface atm 0/6/0/0 RP/0/0/CPU0:router(config-if)# no atm oam flush
Related Commands
Command | Description |
Displays ATM-specific information about an ATM interface. | |
Displays configuration information for the parameters on a VC class that is associated with a particular PVC. | |
Displays information about all ATM VC classes on the router or for a specific ATM VC-class. | |
Displays VP tunnel information for the entire router or for a specific interface. |
cell-packing
To configure the maximum number of cells allowed per packet, and specify a Maximum Cell Packing Timeout (MCPT) timer for cell packing, use the cell-packing command in the appropriate mode. To return the interface to the default cell packing configuration, use the no form of this command.
cell-packing cells timer
no cell-packing
Syntax Description
cells |
Maximum number of cells to use per packet. Range is from 2 through 86. |
||
timer |
Indicates the appropriate MCPT timer to use for cell packing. Can be 1, 2, or 3.
|
Command Default
If you do not configure the maximum number of cells allowed per packet, only one cell is carried per packet.
Command Modes
ATM layer 2 transport interface configuration (config-if-l2)
ATM layer 2 transport PVC configuration (config-atm-l2transport-pvc)
ATM layer 2 transport PVP configuration (config-atm-l2transport-pvp)
Command History
Release |
Modification |
---|---|
Release 3.4.1 |
This command was introduced. |
Usage Guidelines
Use the atm mcpt-timers command to configure the three MCPT timers under the main ATM interface.
Task ID
Task ID |
Operations |
---|---|
atm |
read, write |
Examples
The following example shows how to configure cell packing parameters on an ATM interface:
RP/0/0/CPU0:router# configure RP/0/0/CPU0:router(config)# interface atm 0/6/0/0 RP/0/0/CPU0:router(config-if)# l2transport RP/0/0/CPU0:router(config-if-l2)# cell-packing 6 3
Related Commands
Command | Description |
Defines the three MCPT timers under a main ATM interface. | |
Displays cell packing information for the Layer 2 attachment circuits (ACs) configured on your system. | |
Displays ATM-specific information about an ATM interface. | |
Displays ATM PVC and traffic information for the entire router. | |
Displays ATM PVP and traffic information for the entire router, or a specific VPI or ATM interface. |
class-int
To assign a virtual circuit (VC) class to an ATM main interface, use the class-int command in interface configuration mode. To remove a VC-class, use the no form of this command.
class-int vc-class-name
no class-int vc-class-name
Syntax Description
vc-class-name |
Name of the VC-class you are assigning to your ATM main interface or subinterface. |
Command Default
No VC-class is assigned to an ATM main interface or subinterface.
Command Modes
Interface configuration (config-if)
Command History
Release |
Modification |
---|---|
Release 3.4.0 |
This command was introduced. |
Usage Guidelines
When you create a VC-class for an ATM main interface or subinterface, you can use the shape and encapsulation commands to define your parameters.
Parameters that are applied to an individual VC supersede interface- and subinterface-level parameters. Parameters that are configured for a VC through discrete commands entered in interface-ATM-VC configuration mode supersede VC-class parameters assigned to an ATM main interface or subinterface by the class-int command.
Note | This command is not available for Layer 2 interfaces. |
Task ID
Task ID |
Operations |
---|---|
atm |
read, write |
Examples
The following example shows how to create a class called “classA” and then apply that class to ATM main interface 1 in slot 6:
RP/0/0/CPU0:router# configure RP/0/0/CPU0:router(config)#vc-class atm classA RP/0/0/CPU0:router(config-vc-class-atm)# shape cbr 40000 RP/0/0/CPU0:router(config-vc-class-atm)# encapsulation aal5snap RP/0/0/CPU0:router(config-vc-class-atm)# oam-pvc manage 300 RP/0/0/CPU0:router(config-vc-class-atm)# commit RP/0/0/CPU0:router(config-vc-class-atm)# exit RP/0/0/CPU0:router(config)# interface atm 0/6/0/1 RP/0/0/CPU0:router(config-if)# class-int classA RP/0/0/CPU0:router(config-if)#
Related Commands
Command | Description |
Displays configuration information for the parameters on a VC class that is associated with a particular PVC. | |
Displays information about all ATM VC classes on the router or for a specific ATM VC-class. |
class-vc
To attach a virtual circuit (VC) class to an ATM permanent virtual circuit (PVC), use the class-vc command in ATM PVC configuration mode for a PVC that is configured on an ATM subinterface. To remove a VC-class from a PVC, use the no form of this command.
class-vc vc-class-name
no class-vc vc-class-name
Syntax Description
vc-class-name |
Name of the VC-class you are assigning to your ATM PVC. |
Command Default
No VC-class is assigned to an ATM PVC.
Command Modes
ATM PVC configuration (config-atm-vc)
Command History
Release |
Modification |
---|---|
Release 3.4.0 |
This command was introduced. |
Usage Guidelines
When you create a VC-class for an ATM subinterface PVC, you can use the shape and encapsulation commands to define your parameters.
Parameters that are applied to an individual VC supersede PVC-level parameters. Parameters that are configured for a VC through discrete commands entered in interface-ATM-VC configuration mode supersede VC-class parameters assigned to a PVC by the class-vc command.
Note | The class-vc command is available in ATM PVC configuration mode for a PVC that is configured on an ATM subinterface only. This command is not available in ATM PVC configuration mode for an ATM main interface. |
Task ID
Task ID |
Operations |
---|---|
atm |
read, write |
Examples
The following example shows how to create a class called “classA” and then apply that class to the subinterface 1 on the ATM main interface 1 in slot 6:
RP/0/0/CPU0:router# configure RP/0/0/CPU0:router(config)# vc atm classA RP/0/0/CPU0:router(config-vc-class-atm)# shape cbr 40000 RP/0/0/CPU0:router(config-vc-class-atm)# commit RP/0/0/CPU0:router(config-vc-class-atm)# exit RP/0/0/CPU0:router(config)# interface atm 0/6/0/1.1 point-to-point RP/0/0/CPU0:router(config-if)# pvc 10/100 RP/0/0/CPU0:router(config-atm-vc)# class-vc classA RP/0/0/CPU0:router(config-atm-vc)#
Related Commands
Command | Description |
Displays configuration information for the parameters on a VC class that is associated with a particular PVC. | |
Displays information about all ATM VC classes on the router or for a specific ATM VC-class. |
encapsulation (ATM)
To configure the ATM adaptation layer (AAL) and encapsulation type for a virtual circuit (VC) class, ATM permanent virtual circuit (PVC), or ATM permanent virtual path (PVP), use the encapsulation command in the appropriate configuration mode. To remove an encapsulation type, use the no form of this command.
For point-to-point ATM PVCs and vc-classes:
encapsulation { aal5mux ipv4 | aal5nlpid | aal5snap }
no encapsulation { aal5mux ipv4 | aal5nlpid | aal5snap }
For ATM Layer 2 PVCs:
encapsulation { aal0 | aal5 }
no encapsulation { aal0 | aal5 }
Syntax Description
aal5mux ipv4 |
Specifies IPv4 encapsulation for multiplex (MUX)-type VCs.
|
||
aal5nlpid |
Specifies the AAL and encapsulation type that allows ATM interfaces to interoperate with High-Speed Serial Interfaces (HSSIs), which are using an ATM data service unit (ADSU) and running ATM-Data Exchange Interface (DXI). Supported on ATM PVCs only.
|
||
aal5snap |
Specifies the AAL encapsulation type that supports Inverse ARP. Logical Link Control/Subnetwork Access Protocol (LLC/SNAP) precedes the protocol datagram.
|
||
aal0 |
Specifies the AAL encapsulation type that contains 48 bytes of data within an ATM cell. AAL0 cells are also referred to as “raw cells.” The payload consists of 48 bytes.
|
||
aal5 |
Specifies the AAL encapsulation type that carries higher-layer datagrams while enhancing the link layer with services available through ATM. AAL5 is defined in the ITU standard I.363.5, and is typically used to carry IP datagrams over ATM.
|
Command Default
For point-to-point PVCs, the default encapsulation type is aal5snap.
For Layer 2 PVCs, the default encapsulation type is aal5.
Command Modes
ATM PVC configuration (config-atm-vc)
ATM VC-class configuration (config-vc-class-atm)
ATM layer 2 transport PVC configuration (config-atm-l2transport-pvc)
Command History
Release |
Modification |
---|---|
Release 3.4.0 |
This command was introduced. |
Release 3.4.1 |
To support Layer 2 VPN ACs, the encapsulation command was updated to include the aal0 and aal5 keywords in ATM Layer 2 transport PVC configuration mode. |
Usage Guidelines
Use the aal5mux ipv4 encapsulation option 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 ipv4 or aal5snap encapsulation depends on the type of network you are configuring, and the pricing offered by that network. If the pricing of the network depends on the number of PVCs set up, we recommend aal5snap encapsulation. If pricing depends on the number of bytes transmitted, we recommend aal5mux ipv4 encapsulation because it has less overhead than aal5snap and aal5mux ipv4 encapsulation.
If you configure VC-class parameters for a PVC after that PVC is configured, you must enter the shutdown command followed by the no shutdown command on the ATM subinterface that hosts the PVC. This action restarts the interface, causing the newly configured VC-class parameters to take effect on that interface.
Unless specifically configured otherwise, a PVC automatically inherits the encapsulation type of the VC-class that is assigned to the main interface or subinterface that hosts the PVC. If no VC-class is assigned, then the PVC inherits the encapsulation type of the main interface or subinterface that hosts the PVC. If no encapsulation is configured of the main interface or subinterface, then the PVC inherits the default aal5snap encapsulation.
Use the encapsulation command in ATM PVC configuration mode to modify the inherited or default encapsulation assigned to a PVC. You can modify the encapsulation for each individual PVC to be different from the encapsulation configured for the VC-class that is assigned to the ATM main interface or subinterface that hosts the PVC.
If you do not use the encapsulation command to configure the encapsulation type for a new ATM PVC, then the PVC inherits the one of the following default configurations (listed in order of precedence from lowest to highest):
- The encapsulation assigned to the VC-class that is assigned to the PVC itself.
- The encapsulation assigned to the VC-class that is assigned to the ATM subinterface that hosts the PVC.
- The encapsulation assigned to the VC-class that is assigned to the ATM main interface that hosts the PVC
- The default aal5snap encapsulation
When configuring a PVC range or an individual PVC within a PVC range, the following encapsulation types are supported:
Task ID
Task ID |
Operations |
---|---|
atm |
read, write |
Examples
The following example shows how to configure a VC-class with aal5snap encapsulation:
RP/0/0/CPU0:router# configure RP/0/0/CPU0:router(config)# vc atm classA RP/0/0/CPU0:router(config-vc-class-atm)# encapsulation aal5snap
The following example shows how to configure an individual PVC with aal5mux encapsulation:
RP/0/0/CPU0:router# configure RP/0/0/CPU0:router(config)# interface atm 0/2/0/0.1 point-to-point RP/0/0/CPU0:router(config-subif)# pvc 10/100 RP/0/0/CPU0:router(config-atm-vc)# encapsulation aal5mux
The following example shows how to remove aal5mux ipv4 encapsulation from a VC-class:
RP/0/0/CPU0:router# configure RP/0/0/CPU0:router(config)# vc atm classA RP/0/0/CPU0:router(config-vc-class-atm)# no encapsulation aal5mux ipv4
The following example shows how to configure an individual Layer 2 PVC with aal0 encapsulation:
RP/0/0/CPU0:router# configure RP/0/0/CPU0:router(config)# interface atm 0/6/0/1.10 l2transport RP/0/0/CPU0:router(config-if)# pvc 30/300 RP/0/0/CPU0:router(config-atm-l2transport-pvc)# encapsulation aal0
Related Commands
Command | Description |
Displays ATM PVC and traffic information for the entire router. | |
Displays information about all ATM VC classes on the router or for a specific ATM VC-class. |
f4oam disable
To disable the F4 Operations Administration and Maintenance (OAM) packets for a VP-tunnel, enter the f4oam disable command in ATM VP-tunnel configuration mode. To re-enable F4 OAM packets for a VP-tunnel, enter the no form of this command.
f4oam disable
no f4oam disable
Syntax Description
This command has no keywords or arguments.
Command Default
F4 OAM is enabled by default.
Command Modes
ATM Vp-tunnel configuration
Command History
Release |
Modification |
---|---|
Release 3.4.0 |
This command was introduced. |
Usage Guidelines
Task ID
Task ID |
Operations |
---|---|
atm |
read, write |
Examples
The following example shows how to restrict a VP from passing OAM packets:
RP/0/0/CPU0:router# config RP/0/0/CPU0:router (config)# interface atm 0/6/0/0 RRP/0/0/CPU0:router(config-if)# vp-tunnel 10 RP/0/0/CPU0:router(config-atm-vp-tunnel)# f4oam disable
The following example shows how to re-enable the passing of OAM packets on a VP:
RP/0/0/CPU0:router# config RP/0/0/CPU0:router (config)# interface atm 0/6/0/0 RRP/0/0/CPU0:router(config-if)# vp-tunnel 10 RP/0/0/CPU0:router(config-atm-vp-tunnel)# no f4oam disable
Related Commands
Command | Description |
Displays ATM-specific information about an ATM interface. | |
Displays configuration information for the parameters on a VC class that is associated with a particular PVC. | |
Displays information about all ATM VC classes on the router or for a specific ATM VC-class. | |
Displays VP tunnel information for the entire router or for a specific interface. |
interface atm
To configure an ATM interface and enter ATM interface configuration mode, use the interface atm command in global configuration mode. To delete the interface configuration, use the no form of this command.
interface atm interface-path-id [ . subinterface ] [ point-to-point | l2transport ]
no interface atm interface-path-id [ . subinterface ]
Syntax Description
interface-path-id. [subinterface] |
Physical interface or virtual interface followed by the optional subinterface path ID. Naming notation is interface-path-id..subinterface. The period in front of the subinterface value is required as part of the notation. For more information about the syntax for the router, use the question mark (?) online help function. |
point-to-point |
Interface functions as one endpoint of a point-to-point link. |
l2transport |
Interface functions as one endpoint on an Layer 2 link. |
Command Default
No interfaces are configured.
Command Modes
Global configuration (config)
Command History
Release |
Modification |
---|---|
Release 3.4.0 |
This command was introduced. |
Release 3.4.1 |
To support Layer 2 VPN ATM ACs, this command was updated to include the l2transport keyword. |
Usage Guidelines
The interface command enters interface configuration mode to allow you to configure interfaces. If a virtual interface is configured, then the interface is created if it did not already exist.
When you issue the interface atm command in global configuration mode, the CLI prompt changes to “config-if,” indicating that you have entered interface configuration submode for an ATM interface.
Note | Although the CLI prompt looks the same in the interface configuration mode for an ATM main interface and for an ATM subinterface, the commands that are available under each interface type vary. |
In the following sample output, the question mark (?) online help function displays all the commands available under the interface configuration submode for a ATM main interface:
RP/0/0/CPU0:router(config)# interface atm 0/2/0/0 RP/0/0/CPU0:router(config-if)#? affinity Affinity to include/exclude atm Global ATM interface configuration subcommands bandwidth Set the bandwidth of an interface cdp Enable CDP on an interface class-int Apply a VC class commit Commit the configuration changes to running crypto Set crypto parameters dampening configure state dampening on the given interface describe Describe a command without taking real actions description Set description for this interface do Run an exec command exit Exit from this submode flow Netflow configuration frame-relay Frame Relay interface configuration commands ipv4 IPv4 interface subcommands ipv6 IPv6 interface subcommands l2transport Enable Layer 2 transport and enter its configuration submode load-interval Specify interval for load calculation for an interface mpls MPLS interface subcommands mtu Set the MTU on an interface no Negate a command or set its defaults pvc Configure a pvc on this interface root Exit to the global configuration mode show Show contents of configuration --More--
In the following sample output, the question mark (?) online help function displays all the commands available under the interface configuration submode for a point-to-point ATM subinterface:
RP/0/0/CPU0:router(config)# interface atm 0/2/0/0.1 point-to-point RP/0/0/CPU0:router(config-if)# ? affinity Affinity to include/exclude bandwidth Set the bandwidth of an interface cdp Enable CDP on an interface class-int Apply a VC class commit Commit the configuration changes to running crypto Set crypto parameters dampening configure state dampening on the given interface describe Describe a command without taking real actions description Set description for this interface do Run an exec command exit Exit from this submode flow Netflow configuration frame-relay Frame Relay interface configuration commands ipv4 IPv4 interface subcommands ipv6 IPv6 interface subcommands load-interval Specify interval for load calculation for an interface logging Per-interface logging configuration mpls MPLS interface subcommands mtu Set the MTU on an interface no Negate a command or set its defaults pvc Configure a pvc on this interface root Exit to the global configuration mode show Show contents of configuration shutdown shutdown the given interface --More--
In the following sample output, the question mark (?) online help function displays all the commands available under the interface configuration submode for an ATM Layer 2 subinterface:
RP/0/0/CPU0:router(config)#interface atm 0/2/0/0.1 l2transport RP/0/0/CPU0:router(config-if)#? bandwidth Set the bandwidth of an interface cdp Enable CDP on an interface commit Commit the configuration changes to running crypto Set crypto parameters dampening configure state dampening on the given interface describe Describe a command without taking real actions description Set description for this interface do Run an exec command exit Exit from this submode firewall Configure a Virtual Firewall on this Interface flow Netflow configuration frame-relay Frame Relay interface configuration commands ipv4 IPv4 interface subcommands ipv6 IPv6 interface subcommands load-interval Specify interval for load calculation for an interface logging Per-interface logging configuration mpls MPLS interface subcommands mtu Set the MTU on an interface no Negate a command or set its defaults pvc Configure a pvc on this interface pvp Configure a pvp on this interface pwd Commands used to reach current submode root Exit to the global configuration mode show Show contents of configuration
Cisco IOS XR software supports bulk removal of subinterfaces. To remove several subinterfaces with a single command enter, replace the subinterface argument with an asterisk (*), as shown in the following example:
RP/0/0/CPU0:router(config)# no interface atm 0/6/0/1.*
Note | Before you can perform a bulk removal of several subinterfaces, OAM F5 loopback cell generation must be enabled on the PVCs that are configured under the subinterfaces you want to remove. To enable OAM F5 loopback cell generation on a PVC, use the oam-pvc manage command. |
Note | The l2transport keyword is mutually exclusive with any Layer 3 interface configuration. |
Task ID
Task ID |
Operations |
---|---|
interface |
read, write |
Examples
The following example shows how to enter interface configuration mode for the ATM main interface 1 in slot 6:
RP/0/0/CPU0:router# configure RP/0/0/CPU0:router(config)# interface atm 0/6/0/1 RP/0/0/CPU0:router(config-if)#
The following example shows how to enter ATM interface configuration mode for a point-to-point subinterface. In this example, the user adds a subinterface to the ATM main interface 0 in slot 2:
RP/0/0/CPU0:router# configure RP/0/0/CPU0:router(config)# interface atm 0/2/0/0.1 point-to-point RP/0/0/CPU0:router(config-if)#
The following example shows how to enter ATM interface configuration mode for a Layer 2 subinterface. In this example, the user adds a subinterface to the ATM main interface 0 in slot 2:
RP/0/0/CPU0:router# configure RP/0/0/CPU0:router(config)# interface atm 0/2/0/0.1 l2transport RP/0/0/CPU0:router(config-if)#
Related Commands
Command | Description |
Displays ATM-specific information about an ATM interface. |
l2transport (ATM)
To enable Layer 2 transport port mode on an ATM interface and enter Layer 2 transport configuration mode, use the l2transport command in interface configuration mode. To disable Layer 2 transport port mode on an ATM interface, use the no form of this command.
l2transport
no l2transport
Syntax Description
This command has no keywords or arguments.
Command Default
No default behavior or values
Command Modes
Interface configuration (config-if)
Command History
Release |
Modification |
---|---|
Release 3.4.1 |
This command was introduced. |
Usage Guidelines
When you issue the l2transport command in interface configuration mode, the CLI prompt changes to “config-if-l2,” indicating that you have entered the Layer 2 transport configuration submode. In the following sample output, the question mark (?) online help function displays all the commands available under Layer 2 transport configuration submode for an ATM interface:
RP/0/0/CPU0:router# configure RP/0/0/CPU0:router(config)# interface atm 0/2/0/0 RP/0/0/CPU0:router(config-if)# l2transport RP/0/0/CPU0:router(config-if-l2)# ? cell-packing Configure L2VPN cell packing parameters commit Commit the configuration changes to running describe Describe a command without taking real actions do Run an exec command exit Exit from this submode no Negate a command or set its defaults pwd Commands used to reach current submode root Exit to the global configuration mode service-policy Configure QoS Service policy show Show contents of configuration RP/0/0/CPU0:router(config-if-l2)#
Note | The l2transport command is mutually exclusive with any Layer 3 interface configuration. |
Task ID
Task ID |
Operations |
---|---|
l2vpn |
read, write |
Examples
The following example shows how to enable Layer 2 transport port mode on an ATM interface and enter Layer 2 transport configuration mode:
RP/0/0/CPU0:router# configure RP/0/0/CPU0:router(config)# interface ATM 0/2/0/0 RP/0/0/CPU0:router(config-if)# l2transport RP/0/0/CPU0:router(config-if-l2)#
Related Commands
Command |
Description |
---|---|
show l2vpn xconnect |
Displays brief information on configured xconnects. |
oam ais-rdi
To configure the behavior of an ATM permanent virtual circuit (PVC) when it receives Operation, Administration, and Maintenance (OAM) alarm indication signal and remote defect indication (AIS/RDI) cells, use the oam ais-rdi command in ATM PVC configuration or ATM VC-class configuration mode. To return the PVC to the default behavior, use the no form of this command.
oam ais-rdi [ down-count [up-count] ]
no oam ais-rdi [ down-count [up-count] ]
Syntax Description
down-count |
(Optional) Number of consecutive OAM AIS/RDI cells received on a PVC before that PVC is brought down. Range is from 1 through 60. The default is 1. |
||
up-count |
(Optional) Number of seconds after which a down PVC is brought up if no OAM AIS/RDI cells are received. Range is from 3 through 60. The default is 3. The specified up-count applies under the following conditions only:
|
Command Default
down-count: 1
up-count: 3
Command Modes
ATM VC-class configuration (config-vc-class-atm)
ATM PVC configuration (config-atm-vc)
Command History
Release |
Modification |
---|---|
Release 3.4.0 |
This command was introduced. |
Usage Guidelines
Use the oam ais-rdi command to configure the following:
- the maximum number of Operation, Administration, and Maintenance (OAM) alarm indication signals and remote defect indication (AIS/RDI) cells that can be received on a PVC before it is brought down.
- the interval after which a downed PVC comes back up if no OAM AIS/RDI cells have been received.
Use the oam ais-rdi command in ATM PVC configuration mode to configure the OAM AIS/RDI down count and up count for a specific PVC.
Use the oam ais-rdi command in ATM VC-class configuration mode to configure the OAM AIS/RDI down count and up count for all PVCs that are associated with the specified class map.
Keep the following in mind when configuring the OAM AIS/RDI down count and up count:
- Unless specifically configured otherwise, a PVC automatically inherits the OAM AIS/RDI down count and up count of the VC-class that is assigned to the main interface or subinterface that hosts the PVC.
- If the OAM AIS/RDI down count and up count is not configured for the VC-class, or if no VC-class is assigned to the main interface or subinterface that hosts the PVC, or to the PVC itself, then the PVC inherits the default OAM AIS/RDI down count and up count.
The default values for the OAM AIS/RDI down count and up count are used in the following situations:
- If the oam ais-rdi command has not been entered
- If the oam ais-rdi command is entered without the up-count or down-count argument
- If the no oam ais-rdi command is entered
If the oam ais-rdi command is entered without the up-count or down-count argument, the command does not appear in the show running-config command output.
Task ID
Task ID |
Operations |
---|---|
atm |
read, write |
Examples
The following example shows how to bring down a PVC after 25 consecutive OAM AIS/RDI cells have been received on the PVC. The PVC is brought up when no OAM AIS/RDI cells have been received for 5 seconds.
RP/0/0/CPU0:router# configure RP/0/0/CPU0:router(config)# interface atm 0/2/0/0.1 point-to-point RP/0/0/CPU0:router(config-subif)# pvc 50/100 RP/0/0/CPU0:router(config-atm-vc)# oam ais-rdi 25 5
The following example shows how to configure the OAM AIS/RDI down count and up count for a VC-class. In this example, all PVCs that are associated with the VC-class called “classA” inherit an OAM AIS/RDI down count of 30 and up count of 10:
RP/0/0/CPU0:router# configure RP/0/0/CPU0:router(config)# vc atm classA RP/0/0/CPU0:router(config-vc-class-atm)# oam ais-rdi 30 10
Related Commands
Command | Description |
Displays configuration information for the parameters on a VC class that is associated with a particular PVC. | |
Displays ATM PVC and traffic information for the entire router. |
oam-pvc manage
To enable ATM Operation, Administration, and Maintenance (OAM) F5 loopback cell generation and configure continuity check (CC) management for an ATM permanent virtual circuit (PVC), use the oam-pvc manage command in ATM PVC configuration or ATM VC-class configuration mode. To disable OAM F5 continuity checking on a PVC, use the no form of this command.
In ATM PVC configuration mode:
oam-pvc manage [ f requency ] [disable] [ keep-vc-up [seg-aisrdi-failure] ]
no oam-pvc manage [frequency] [disable] [ keep-vc-up [seg-aisrdi-failure] ]
In ATM VC class configuration mode:
oam-pvc manage [frequency]
no oam-pvc manage [frequency]
Syntax Description
frequency |
(Optional) Frequency (in seconds) at which end-to-end F5 OAM loopback cells are transmitted. Range is from 0 through 600. |
||
disable |
(Optional) Disables OAM management on the specified PVC.
|
||
keep-vc-up |
(Optional) Specifies that PVC remains in the UP state when CC cells detect connectivity failure.
|
||
seg-aisrdi-failure |
(Optional) Specifies that if segment AIS/RDI cells are received, the VC will not be brought down because of end CC failure or loopback failure.
|
Command Default
frequency: 10 seconds
Command Modes
ATM PVC configuration (config-atm-vc)
ATM VC class configuration (config-vc-class-atm)
Command History
Release |
Modification |
---|---|
Release 3.4.0 |
This command was introduced. |
Usage Guidelines
Keep the following in mind when configuring the OAM F5 loopback cell generation and CC management for an ATM PVC:
- Unless specifically configured otherwise, a PVC automatically inherits the OAM F5 loopback cell management configuration from the VC-class that is assigned to the main interface or subinterface that hosts the PVC.
- If OAM F5 loopback cell generation is not enabled for the assigned VC-class, or if no VC-class is assigned to the PVC itself, or to main interface or subinterface that hosts the PVC, then OAM F5 loopback cell generation is disabled on that PVC. To enable OAM F5 loopback cell generation on that PVC, you need to use the oam-pvc manage command in ATM PVC configuration mode.
- VC-classes support the configuration of the seconds argument only; the keep-vc-up, disable, and seg-aisrdi-failure keywords are available in ATM PVC configuration mode only and are configured directly on each individual PVC.
Task ID
Task ID |
Operations |
---|---|
atm |
read, write |
Examples
The following example shows how to enable OAMF5 loopback cell generation on a PVC, and configure the PVC to remain up when CC cells detect connectivity failure:
RP/0/0/CPU0:router# configure RP/0/0/CPU0:router(config)# interface atm 0/2/0/0.1 point-to-point RP/0/0/CPU0:router(config-subif)# pvc 10/100 RP/0/0/CPU0:router(config-atm-vc)# oam-pvc manage 200 keep-vc-up
The following example shows how to disable OAMF5 loopback cell generation on a PVC:
RP/0/0/CPU0:router# configure RP/0/0/CPU0:router(config)# interface atm 0/2/0/0.1 point-to-point RP/0/0/CPU0:router(config-subif)# pvc 10/100 RP/0/0/CPU0:router(config-atm-vc)# oam-pvc manage disable
The following example shows how to configure the OAM F5 loopback frequency for a VC-class. In this example, all PVCs associated with the VC-class called “classA” transmit end-to-end F5 OAM loopback cells every 300 seconds:
RP/0/0/CPU0:router# configure RP/0/0/CPU0:router(config)# vc atm classA RP/0/0/CPU0:router(config-vc-class-atm)# oam-pvc manage 300
The following example shows how to remove the configured ATM OAM F5 loopback frequency from a VC-class:
RP/0/0/CPU0:router# configure RP/0/0/CPU0:router(config)# vc atm classA RP/0/0/CPU0:router(config-vc-class-atm)# no oam-pvc manage
Related Commands
Command | Description |
Displays configuration information for the parameters on a VC class that is associated with a particular PVC. | |
Displays ATM PVC and traffic information for the entire router. |
oam retry
To configure the number of F5 Operation, Administration, and Maintenance (OAM) loopback cells that need to be successfully transmitted by a down ATM permanent virtual circuit (PVC) before it is brought up, use the oam retry command in ATM PVC configuration or ATM VC-class configuration mode. To return the PVC to the default behavior, use the no form of this command
oam retry [ up-count [ down-count [retry-frequency] ] ]
no oam retry [ up-count [ down-count [retry-frequency] ] ]
Syntax Description
retry-count |
(Optional) Number of consecutive end-to-end F5 OAM loopback cell responses that must be received to change a connection state to up. |
down-count |
(Optional) Number of consecutive unreceived end-to-end F5 OAM loopback cells allowed on a PVC before its state changes to down. |
retry-frequency |
(Optional) Frequency (in seconds) at which end-to-end F5 OAM loopback cells are transmitted when a change in the up or 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) is specified using the oam-pvc manage command, loopback cells are sent at the retry frequency to verify whether the PVC is down. |
Command Default
up-count: 3
down-count: 5
retry-frequency: 1 second
Command Modes
ATM PVC configuration (config-atm-vc)
ATM VC-class configuration (config-vc-class-atm)
Command History
Release |
Modification |
---|---|
Release 3.4.0 |
This command was introduced. |
Usage Guidelines
Keep the following in mind when configuring the OAM AIS/RDI down count and up count:
- Unless specifically configured otherwise, a PVC automatically inherits the OAM AIS/RDI down count and up count of the VC-class that is assigned to the main interface or subinterface that hosts the PVC.
- If no encapsulation is configured for the VC-class, or if no VC-class is assigned to the main interface or subinterface that hosts the PVC, or to the PVC itself, then the PVC inherits the default OAM AIS/RDI down count and up count.
Keep the following in mind when configuring the F5 OAM loopback cell up count, down count, and retry frequency:
- Unless specifically configured otherwise, a PVC automatically inherits the F5 OAM loopback cell up count, down count, and retry frequency of the VC-class that is assigned to the main interface or subinterface that hosts the PVC.
- If the F5 OAM loopback cell up count, down count, and retry frequency are not configured for the VC-class, or if no VC-class is assigned to the PVC itself, or to the main interface or subinterface that hosts the PVC, then the PVC inherits the default F5 OAM loopback cell up count, down count, and retry frequency.
In other words, if the oam retry command is not explicitly configured on an individual PVC, then that PVC inherits the following default configuration (listed in order of precedence):
-
F5 OAM loopback cell up count, down count, and retry frequency configured for the VC-class that is assigned to the PVC itself
-
F5 OAM loopback cell up count, down count, and retry frequency configured for VC-class assigned to the ATM subinterface that hosts the PVC
-
F5 OAM loopback cell up count, down count, and retry frequency configured for the VC-class assigned to the ATM main interface that hosts the PVC
Note | For the defaults, it is assumed that OAM loopback cell generation is enabled on the PCV. To enable OAM F5 loopback cell generation, use the oam-pvc manage command. |
Task ID
Task ID |
Operations |
---|---|
atm |
read, write |
Examples
The following example shows how to OAM management parameters for an ATM PVC. In this example, the PVC is brought down after five consecutive OAM AIS/RDI cells are received and then brought back up when no OAM AIS/RDI cells are received for 10 seconds. End-to-end F5 OAM loopback cells are transmitted every five seconds if a change in the up or down state is verified.
RP/0/0/CPU0:router# configure RP/0/0/CPU0:router(config)# interface atm 0/2/0/0.1 point-to-point RP/0/0/CPU0:router(config-subif)# pvc 10/100 RP/0/0/CPU0:router(config-atm-vc)# oam retry 5 10 5
The following example shows how to configure OAM management parameters for a VC-class. In this example, all PVCs that are associated with the VC-class called “classA” inherit an OAM up-count of 3, down-count of 5, and retry-frequency of 10:
RP/0/0/CPU0:router# configure RP/0/0/CPU0:router(config)# vc atm classA RP/0/0/CPU0:router(config-vc-class-atm)# oam retry 10 20 10
Related Commands
Command | Description |
Displays configuration information for the parameters on a VC class that is associated with a particular PVC. | |
Displays ATM PVC and traffic information for the entire router. |
ping atm interface atm
To verify connectivity between two ATM connection endpoints through a permanent virtual circuit (PVC) or VP-tunnel, use the ping atm interface atm command in EXEC mode.
ping atm interface atm interface-path-id [ . subinterface ] [ vpi/vci ] [ end-loopback packets | seg-loopback packets ] [ timeout seconds ]
Syntax Description
interface-path-id [.subinterface] |
Physical interface or virtual interface followed by the optional subinterface path ID. Naming notation is interface-path-id.subinterface. The period in front of the subinterface value is required as part of the notation. For more information about the syntax for the router, use the question mark (?) online help function. |
||
vpi/vci |
(Optional) ATM virtual path identifier (VPI) and virtual channel identifier (VCI) numbers. The absence of the slash (/) and a vpi value defaults the vpi value to 0.
|
||
end-loopback packets |
(Optional) Sends a specified number of end-to-end OAM loopback packets over the connection. Replace packets with the number of end-to-end OAM loopback packets you want to send over the ATM interface. |
||
seg-loopback packets |
(Optional) Sends a specified number of segmented OAM loopback packets over the connection. Replace packets with the number of OAM loopback packets you want to send over the ATM interface. |
||
timeout seconds |
Predetermined time during which the destination can send an OAM loopback response cell back to the source. Replace seconds with number of seconds to wait for an OAM loopback response before the ping times out. The default value of the timeout is 2 seconds on Cisco routers. |
Command Default
seconds: 2
Command Modes
EXEC (#)
Command History
Release |
Modification |
---|---|
Release 3.4.0 |
This command was introduced. |
Usage Guidelines
The following guidelines apply to PVCs and VC-classes.
The ping atm interface atm command sends an OAM packet to verify ATM PVC connectivity. The status of the PVC is displayed when a response to the OAM packet is received. This is a common method for testing the accessibility of the devices.
The ping atm interface atm command is used to determine the following:
- Whether a remote host is active or inactive.
- The round-trip delay in communicating with the host.
- Packet loss.
For the interface-path-id argument, use the following guidelines:
- If specifying a physical interface, the naming notation is rack/slot/module/port. The slash between values is required as part of the notation. An explanation of each component of the naming notation is as follows:
- If specifying a virtual interface, the number range varies, depending on interface type.
Include the end-loopback packets keyword argument with the ping atm interface atm command to verify end-to-end PVC integrity.
Include the seg-loopback packets keyword argument with the ping atm interface atm command to verify PVC integrity to the immediate neighboring ATM device.
Note | The ping command is not available for Layer 2 ACs. |
Task ID
Task ID |
Operations |
---|---|
basic-services |
execute |
atm |
read |
Examples
The following example shows how verify connectivity between two ATM connection endpoints through a PVC with a VPI of 10 and a VCI of 100.
RP/0/0/CPU0:router# ping atm interface atm 0/2/0/0.10 10/100
Related Commands
Command | Description |
Displays ATM-specific information about an ATM interface. |
pvc (ATM)
To create an ATM permanent virtual circuit (PVC) with Interim Local Management Interface (ILMI) encapsulation and enter ATM virtual circuit configuration mode, use the pvc command in interface configuration mode or subinterface configuration mode. To remove an ATM PVC from an interface, use the no form of this command.
In interface configuration mode for a point-to-point ATM main interface:
pvc vpi /vci ilmi
no pvc vpi /vci ilmi
In interface configuration mode for an ATM subinterface:
pvc vpi /vci
no pvc vpi /vci
Syntax Description
vpi/ |
ATM network virtual path identifier (VPI) for this PVC. If support for the 12-bits VPI Network-Node Interface (NNI) cell format is enabled on the ATM main interface that hosts this PVC, then the range is from 0 through 4095. If support for the 12-bits VPI NNI cell format is not enabled on the host ATM main interface, then the range is from 0 through 255.
|
||||
vci |
ATM network virtual channel identifier (VCI) for this PVC. Range is from 1 through 65535. The VCI is a 16-bit field in the header of the ATM cell. The VCI value is unique only on a single link, not throughout the ATM network, because it has local significance only.
|
||||
ilmi |
Sets up communication with the Interim Local Management Interface (ILMI). The associated VPI is 0, and VCI the associated VCI is any VCI.
|
Command Default
No PVC is defined.
Command Modes
Interface configuration (config-if)
Subinterface configuration (config-subif)
Command History
Release |
Modification |
---|---|
Release 3.4.0 |
This command was introduced. |
Release 3.4.1 |
This command was supported in subinterface configuration mode for ATM subinterface attachment circuits (ACs). |
Usage Guidelines
The pvc command creates a PVC and attaches it to the specified VPI and VCI. Both the vpi and vci arguments cannot be simultaneously specified as 0; if one is 0, the other cannot be 0.
Cisco IOS XR software dynamically creates rate queues as necessary to satisfy the requests of the PVC commands.
When you issue the pvc command in interface or subinterface configuration mode for a point-to-point ATM main interface, the CLI prompt changes to “config-atm-vc,” indicating that you have entered the ATM virtual circuit configuration submode.
Note | Although the CLI prompt looks the same for the ATM virtual circuit configuration submode under the ATM main interface and the ATM subinterface in point-to-point configurations, the commands that are available under each interface type vary. |
When you issue the pvc command in subinterface configuration mode for an ATM AC, the CLI prompt changes to “config-atm-l2transport-pvc,” indicating that you have entered the ATM layer 2 transport PVC configuration submode.
Note | For the 4-Port OC-3 and 4-Port OC-12 line cards, the VCI range is 19 through 65535. |
In the following sample output, the question mark (?) online help function displays all the commands available under the ATM virtual circuit configuration submode for the main ATM interface:
RP/0/0/CPU0:router# configure RP/0/0/CPU0:router(config)# interface atm 0/2/0/0.1 point-to-point RP/0/0/CPU0:router(config-if)# pvc 10/100 RP/0/0/CPU0:router(config-atm-vc ? commit Commit the configuration changes to running describe Describe a command without taking real actions do Run an exec command exit Exit from this submode no Negate a command or set its defaults root Exit to the global configuration mode RP/0/0/CPU0:router(config-atm-vc)#
In the following sample output, the question mark (?) online help function displays all the commands available under the ATM virtual circuit configuration submode for the ATM subinterface:
RP/0/0/CPU0:router# configure RP/0/0/CPU0:router(config-if)# interface atm 0/2/0/0.1 point-to-point RP/0/0/CPU0:router(config-subif)# pvc 20/200 RP/0/0/CPU0:router(config-atm-vc)# ? class-vc Configure vc-class commit Commit the configuration changes to running describe Describe a command without taking real actions do Run an exec command encapsulation Configure encapsulation on this PVC exit Exit from this submode no Negate a command or set its defaults oam Configure ATM OAM VC commands oam-pvc Enter OAM to generate OAM cells root Exit to the global configuration mode service-policy Configure QoS Service policy shape ATM Traffic Shaping show Show contents of configuration RP/0/0/CPU0:router(config-atm-vc)#
In the following sample output, the question mark (?) online help function displays all the commands available under the ATM layer 2 transport PVC configuration submode for the ATM interface:
RP/0/0/CPU0:router# configure RP/0/0/CPU0:router(config-if)# interface atm 0/2/0/0.1 l2transport RP/0/0/CPU0:router(config-subif)# pvc 20/200 RP/0/0/CPU0:router(config-atm-l2transport-pvc)# ? cell-packing Configure L2VPN cell packing parameters class-vc Configure vc-class commit Commit the configuration changes to running describe Describe a command without taking real actions do Run an exec command encapsulation Configure encapsulation on this PVC exit Exit from this submode no Negate a command or set its defaults oam Configure ATM OAM VC commands oam-ac Configure L2VPN OAM parameters oam-pvc Enter OAM to generate OAM cells pwd Commands used to reach current submode root Exit to the global configuration mode service-policy Configure QoS Service policy shape ATM Traffic Shaping show Show contents of configuration
Task ID
Task ID |
Operations |
---|---|
atm |
read, write |
Examples
The following example shows how to create an ATM PVC with ILMI encapsulation on an ATM main interface, and enter ATM virtual circuit configuration mode:
RP/0/0/CPU0:router# configure RP/0/0/CPU0:router(config)# interface atm 0/6/0/1 RP/0/0/CPU0:router(config-if)# pvc 5/100 ilmi RP/0/0/CPU0:router(config-atm-vc)#
The following example shows how to create an ATM PVC on a point-to-point ATM subinterface and enter ATM virtual circuit configuration mode:
RP/0/0/CPU0:router# configure RP/0/0/CPU0:router(config-if)# interface atm 0/2/0/0.1 point-to-point RP/0/0/CPU0:router(config-subif)# pvc 20/200 RP/0/0/CPU0:router(config-atm-vc)#
The following example shows how to create an ATM PVC on an ATM layer 2 subinterface and enter ATM layer 2 transport PVC configuration mode:
RP/0/0/CPU0:router# configure RP/0/0/CPU0:router(config-if)# interface atm 0/2/0/0.1 l2transport RP/0/0/CPU0:router(config-subif)# pvc 20/200 RP/0/0/CPU0:router(config-atm-l2transport-pvc)#
Related Commands
Command | Description |
Displays configuration information for the parameters on a VC class that is associated with a particular PVC. | |
Displays ATM PVC and traffic information for the entire router. |
pvp (ATM)
To create an ATM permanent virtual path (PVP) and enter ATM layer 2 transport PVP configuration mode, use the pvp command in subinterface configuration mode. To remove an ATM PVP from an interface, use the no form of this command.
pvp vpi
no pvp vpi
Syntax Description
vpi |
ATM network virtual path identifier (VPI) for this PVC. If support for the 12-bit VPI Network-Node Interface (NNI) cell format is enabled on the ATM main interface that hosts this PVP, then the range is from 1 through 4095. If support for the 12-bit VPI NNI cell format is not enabled on the host ATM main interface, then the range is from 1 through 255.
|
Command Default
No PVC is defined.
Command Modes
Subinterface configuration (config-subif)
Command History
Release |
Modification |
---|---|
Release 3.4.1 |
This command was introduced. |
Usage Guidelines
The pvp command creates a PVP and attaches it to the specified VPI.
Cisco IOS XR software dynamically creates rate queues as necessary to satisfy the requests of the PVP commands.
When you issue the pvp command in subinterface configuration mode, the CLI prompt changes to “config-atm-l2transport-pvp,” indicating that you have entered the ATM layer 2 transport PVP configuration submode.
Note | The pvp command is available for layer 2 subinterfaces only. |
Note | PVPs do not support a VPI of 0. |
In the following sample output, the question mark (?) online help function displays all the commands available under the ATM layer 2 transport PVP configuration submode for the ATM subinterface:
RP/0/0/CPU0:router# configure RP/0/0/CPU0:router(config-if)# interface atm 0/2/0/0.1 l2transport RP/0/0/CPU0:router(config-subif)# pvp 20 RP/0/0/CPU0:router(config-atm-l2transport-pvp)# ? cell-packing Configure L2VPN cell packing parameters commit Commit the configuration changes to running describe Describe a command without taking real actions do Run an exec command exit Exit from this submode no Negate a command or set its defaults pwd Commands used to reach current submode root Exit to the global configuration mode shape ATM Traffic Shaping show Show contents of configuration
Task ID
Task ID |
Operations |
---|---|
atm |
read, write |
Examples
The following example shows how to create an ATM PVP on an ATM subinterface, and enter ATM layer 2 transport PVP configuration mode:
RP/0/0/CPU0:router# configure RP/0/0/CPU0:router(config-if)# interface atm 0/2/0/0.1 l2transport RP/0/0/CPU0:router(config-subif)# pvp 20 RP/0/0/CPU0:router(config-atm-l2transport-pvp)#
Related Commands
Command | Description |
Displays ATM PVP and traffic information for the entire router, or a specific VPI or ATM interface. |
shape
To configure ATM traffic shaping for a PVC, use the shape command in the appropriate command mode. To remove the configured ATM traffic shaping and return the PVC to using the default constant bit rate (CBR) traffic shaping, use the no form of this command.
shape { cbr peak_output_rate | ubr peak_output_rate | vbr-nrt peak_output_rate sustained_output_rate burst_size | vbr-rt peak_output_rate sustained_output_rate burst_size }
no shape
Syntax Description
cbr |
Configures the service class for the VC or VP-tunnel to be CBR. Range is from 38 through 622000 kbps. This is the default service class. |
||
ubr |
Configures the service class for the VC or VP-tunnel to be unspecified bit rate (UBR). UBR is intended for non-real-time applications that do not require any maximum bound on the transfer delay or on the cell loss ratio. Ranges follow: |
||
vbr-nrt |
Configures the service class for the VC or VP-tunnel to be variable Bit Rate-Non Real Time (VBR-nrt). |
||
vbr-rt |
Configures the service class for the VC or VP-tunnel to be variable bit rate-real time (VBR-rt). |
||
peak_output_rate |
Peak output rate for the bit rate. Replace the peak_output_rate argument with the peak output rate in kbps. For VP-tunnels, the ranges follow: For VCs, the ranges follow:
|
||
sustained_output_rate |
Sustained output rate for the bit rate. Replace the sustained_output_rate argument with the sustained output rate in kbps. For VP-tunnels, the ranges follow: For VCs, the ranges follow:
|
||
burst_size |
Burst cell size for the bit rate. Replace the sustained_output_rate argument with the burst size. Range is from 1 through 8192. |
Command Default
The default service class for the VC is cbr.
Command Modes
ATM PVC configuration (config-atm-vc)
ATM VC-class configuration (config-vc-class-atm)
ATM Layer 2 transport PVC configuration (config-atm-l2transport-pvc)
ATM Layer 2 transport PVP configuration (config-atm-l2transport-pvp)
ATM VP tunnel configuration mode (config-atm-vp-tunnel)
Command History
Release |
Modification |
---|---|
Release 3.4.0 |
This command was introduced. |
Release 3.4.1 |
This command was supported in ATM layer 2 transport PVC configuration mode and ATM layer 2 transport PVP configuration mode. |
Usage Guidelines
Task ID
Task ID |
Operations |
---|---|
atm |
read, write |
Examples
The following example shows how to configure the service class for a PVC to be UBR, with a peak output of 150,000 kbps:
RP/0/0/CPU0:router#config RP/0/0/CPU0:router(config)# interface atm 0/6/0/0.2 point-to-point RP/0/0/CPU0:router(config-subif)# pvc 20/200 RP/0/0/CPU0:router(config-atm-vc)# shape ubr 150000
The following example shows how to configure the service class for a VP-tunnel to be CBR, with a peak output of 150,000 kbps:
RP/0/0/CPU0:router#config RP/0/0/CPU0:router(config)# interface atm 0/6/0/0 RP/0/0/CPU0:router(config-if)# vp-tunnel 10 RP/0/0/CPU0:router(config-atm-vp-tunnel)# shape cbr 150000
The following example shows how to configure the service class for a VC to be VBR-nrt:
RP/0/0/CPU0:router# config RP/0/0/CPU0:router(config)# vc-class atm class1 RP/0/0/CPU0:router(config-vc-class-atm)# shape vbr-nrt 100000 100000 8000 RP/0/0/CPU0:router(config-vc-class-atm)# exit RP/0/0/CPU0:router(config)# exit Uncommitted changes found, commit them before exiting(yes/no/cancel)? [cancel]:y RP/0/0/CPU0:router#
Related Commands
Command | Description |
Displays ATM PVC and traffic information for the entire router. | |
Displays ATM PVP and traffic information for the entire router, or a specific VPI or ATM interface. | |
Displays VP tunnel information for the entire router or for a specific interface. |
show atm cell-packing
To display cell packing information for the Layer 2 attachment circuits (ACs) configured on your system, use the show atm cell-packing command in EXEC mode.
show atm cell-packing
Syntax Description
This command has no keywords or arguments.
Command Default
No default behavior or values
Command Modes
EXEC (#)
Command History
Release |
Modification |
---|---|
Release 3.4.1 |
This command was introduced. |
Usage Guidelines
Task ID
Task ID |
Operations |
---|---|
atm |
read |
Examples
The following sample output is from the show atm cell-packing command:
RP/0/0/CPU0:router# show atm cell-packing
avg # avg #
Circuit local cells/pkt negotiated cells/pkt MCPT
Type MNCP rcvd MNCP sent (us)
ATM0/2/0/1.200 vc 1/200 1 0 1 0 50
ATM0/2/0/1.300 vc 1/300 1 0 1 0 50
Field |
Description |
---|---|
Circuit Type |
AC instance and virtual channel identifier. |
Local MNCP |
Maximum number of cells that can be packed on the local AC. |
AVG cells/pkt rcvd |
Average number of cells in a packed cell received from the peer, or the average number of cells packed by the peer. |
negotiated MNCP |
Negotiated maximum number of cells that can be packed on a psuedowire between PE routers. |
AVG cells/pkt sent |
Maximum number of cells that can be packed on the peer AC. |
MCPT |
Maximum number of cells allowed per packet configured on the local MCPT. |
show atm class-link
To display configuration information for the parameters on a virtual circuit (VC) class that is associated with a particular PVC, use the show atm class-link command in privileged EXEC mode.
show atm class-link vpi /vci
Syntax Description
vpi/vci |
ATM VPI and VCI numbers. The absence of the slash (/) and a vpi value defaults the vpi value to 0.
|
Command Default
The absence of the slash (/) and a vpi value defaults the vpi value to 0.
Command Modes
EXEC (#)
Command History
Release |
Modification |
---|---|
Release 3.4.0 |
This command was introduced. |
Release 3.4.1 |
The show atm class-link command output was modified to include Layer 2 VPN parameters when appropriate. |
Usage Guidelines
Note | If a PVC or its host interface is associated with a VC-class, then that PVC inherits all the values configured for that VC-class. If no VC-class is configured for a PVC or its host interface, then the command output displays a message that says “VC class not supported on this VC.” |
Task ID
Task ID |
Operations |
---|---|
atm |
read |
Examples
The following sample output is from the show atm class-link command:
RP/0/0/CPU0:router# show atm class-link 10/100
ATM0/2/0/0.1: VPI: 10 VCI: 100
shape : cbr 100000 (VC-class configured on VC)
encapsulation : aal5snap (VC-class configured on VC)
oam-pvc : manage 300 (VC-class configured on VC)
oam retry : 3 5 1 (Default value)
oam ais-rdi : 1 3 (Default value)
Table 1 describes the significant fields shown in the display.
The following sample output is from the show atm class-link command when there is no VC-class associated with the specified PVC:
RP/0/0/CPU0:router# show atm class-link 0/50 Detailed display of VC(s) with VPI/VCI = 0/50 Class link for VC 0/50 ATM0/2/0/2: VPI: 0 VCI: 50 ILMI VC (VC class not supported on this VC)
Related Commands
Command | Description |
Assigns a VC class to an ATM main interface. | |
Creates a VC class for an ATM PVC or an ATM interface and enters VC-class configuration mode. |
show atm ilmi-status
To display status information that is related to Interim Local Management Interface (ILMI), use the show atm ilmi-status command in EXEC mode.
show atm ilmi-status [ atm interface-path-id [.subinterface] ]
Syntax Description
atm |
(Optional) ATM interface for which you want to display information.Use the interface-path-id argument to specify the ATM interface. |
interface-path-id[.subinterface] |
Physical interface or virtual interface followed by the optional subinterface path ID. Naming notation is interface-path-id.subinterface. The period in front of the subinterface value is required as part of the notation. For more information about the syntax for the router, use the question mark (?) online help function. |
Command Default
Entering the show atm ilmi-status command without specifying an interface displays ILMI-related status information for all ATM interfaces.
Command Modes
EXEC (#)
Command History
Release |
Modification |
---|---|
Release 3.4.0 |
This command was introduced. |
Usage Guidelines
Task ID
Task ID |
Operations |
---|---|
atm |
read |
Examples
The following sample output is from the show atm ilmi-status command:
RP/0/0/CPU0:router# show atm ilmi-status
Interface : ATM0/2/0/1 Interface Type : Private UNI (User-side)
ILMI VCC : (20, 30)
ILMI Keepalive : Disabled
ILMI State: WaitDevType
Peer IP Addr : 0.0.0.0 Peer IF Name : ATM1/2
Active Prefix(s) :
The following sample output is from the show atm ilmi-status command with the atm instance keyword and argument:
RP/0/0/CPU0:router# show atm ilmi-status atm 0/2/0/2
Interface : ATM0/2/0/2 Interface Type : Private UNI (User-side)
ILMI VCC : (0, 16) ILMI Keepalive : Disabled
ILMI State: UpAndNormal
Peer IP Addr: 0.0.0.0 Peer IF Name: ATM1/2
Active Prefix(s) :
Field |
Description |
||
---|---|---|---|
Interface |
Interface type and instance. The instance is displayed in the rack/slot/module/port format. |
||
Interface Type |
ATM interface type (Private or Public), and the communication protocol used by this interface.
|
||
ILMI VCC |
The virtual channel connection associated with this interface. |
||
ILMI Keepalive |
ILMI keepalives polling frequency configured on this interface. To modify the ILMI keepalives polling frequency, use the atm ilmi-keepalive command. |
||
ILMI State |
Status of ILMI for this interface. Possible ILMI states are:
|
||
Peer IP Addr |
IP address for the remote (neighbor) end point of the connection. |
||
Peer IF Name |
Identifies the interface at the remote (neighbor) end point of the connection. |
||
Active Prefix(s) |
Network prefix that is registered from the switch side and is active and valid. |
Related Commands
Command | Description |
Disables ILMI on an ATM interface. | |
Enables ILMI keepalives on an ATM interface and configure keepalive polling frequency. |
show atm interface atm
To display ATM-specific information about an ATM interface, use the show atm interface atm command in EXEC mode.
show atm interface atm interface-path-id
Syntax Description
interface-path-id |
Physical interface or virtual interface.
For more information about the syntax for the router, use the question mark (?) online help function. |
Command Default
No default behavior or values
Command Modes
EXEC (#)
Command History
Release |
Modification |
---|---|
Release 3.4.0 |
This command was introduced. |
Release 3.4.1 |
The show atm interface atmcommand output was modified to include Layer 2 VPN parameters when appropriate. |
Usage Guidelines
Task ID
Task ID |
Operations |
---|---|
atm |
read |
Examples
The following sample output is from the show atm interface atm command:
RP/0/0/CPU0:router# show atm interface atm 0/2/0/3
Interface : ATM0/2/0/3
AAL Enabled : AAL5
Max-VP : 254
Max-VC : 2046
Configured L2 PVPs : 0
Configured L2 PVCs : 0
Configured L3 VP-Tunnels : 0
Configured L3 PVCs : 1
L2 PVPs in Down State : 0
L2 PVCs in Down State : 0
L3 VP-Tunnels in Down State : 0
L3 PVCs in Down State : 0
Cell packing count : 0
Received Side Statistics:
Received Cells : 0
Received Bytes : 0
Received AAL Packets : 0
Receive Side Cells Dropped:
Unrecognized VPI/VCI : 0
Receive Side AAL5 Packets Dropped:
Unavailable SAR Buffer : 0
Non-Resource Exhaustion : 0
Reassembly Timeout : 0
Zero Length : 0
Unavailable Host Buffer : 0
Packet size exceeds MPS : 0
AAL5 Trailer Length Errors : 0
Transmit Side Statistics:
Transmitted Cells : 1899716067
Transmitted Bytes : 0
Transmitted AAL Packets : 0
Transmit Side Cells Dropped:
Unrecognized VPI/VCI : 0
Transmit Side AAL5 Packets Dropped:
Unavailable SAR Buffer : 0
Non-Resource Exhaustion : 0
WRED Threshold : 0
WRED Random : 0
Field |
Description |
---|---|
Interface |
Interface type and instance. The instance is displayed in the rack/slot/module/port format. |
Layer2 Transport Port Mode |
Displays whether Layer 2 transport mode is enabled or disabled on this interface. |
Cell Packing Data Unavailable |
Displays whether cell packing is enabled or disabled on this interface. |
Received Side Statistics |
Displays the following statistical information for the receiving end of this interface: |
Receive Side Cells Dropped |
Displays the following information about AAL5 packets received from the remote end that were dropped by this end of the interface:
|
Receive Side AAL5 Packets Dropped |
Displays the number of received AAL5 packet drops that occurred on this interface due to the following errors: |
Receive Side Cells Dropped |
Number of unrecognized VPI and VCI cells received from the remote end that were dropped. |
Receive side AAL5 Packets Dropped: |
Displays the following information about AAL5 packets received from the remote end that were dropped by this end of the interface:
|
Transmit Side Statistics |
Displays the following statistical information for the transmit side of this interface: |
Transmit side Cells Dropped |
Number of VPI and VCI cells transmitted to the remote end that were dropped because they were not recognized by the remote end. |
Transmit Side AAL5 Packets Dropped |
Displays the following information about transmitted AAL5 packets that were dropped by the remote end:
|
Cell-packing statistics |
Displays the following cell packing statistics for the specified interface: |
Related Commands
Command | Description |
Configures an ATM interface and enters ATM interface configuration mode. |
show atm pvc
To display ATM permanent virtual circuit (PVC) and traffic information for the entire router, or a specific VPI/VCI or ATM interface, use the show atm pvc command in EXEC mode.
show atm pvc [ vpi /vci | interface atm interface-path-id ]
Syntax Description
vpi/vci |
(Optional) ATM virtual path identifier (VPI) and virtual channel identifier (VCI) numbers. The absence of the slash (/) and a vpi value defaults the vpi value to 0.
|
||
interface atm |
(Optional) ATM interface for which you want to display information.Use the interface-path-id argument to specify the ATM interface. |
||
interface-path-id |
Physical interface or virtual interface.
For more information about the syntax for the router, use the question mark (?) online help function. |
Command Default
Entering the show atm pvc command without specifying the vpi/vci argument or interface atm instance keyword argument displays ATM PVC and traffic information for the entire router.
Command Modes
EXEC (#)
Command History
Release |
Modification |
---|---|
Release 3.4.0 |
This command was introduced. |
Release 3.4.1 |
The show atm pvc command output was modified to include Layer 2 VPN parameters when appropriate. |
Usage Guidelines
Task ID
Task ID |
Operations |
---|---|
atm |
read |
Examples
The following sample output is from the show atm pvc command:
RP/0/0/CPU0:router# show atm pvc
Peak Avg/Min Burst
Interface VPI VCI Type Encaps SC Kbps Kbps Cells Sts
ATM0/1/0/0.230 15 230 PVC AAL0 UBR 622000 N/A N/A UP
ATM0/1/0/3.19 17 19 PVC SNAP UBR 622000 N/A N/A UP
Field |
Description |
||
---|---|---|---|
Interface |
Interface type and instance. The instance is displayed in the rack/slot/module/port format. |
||
VPI |
ATM network virtual path identifier (VPI) associated with the specified interface. |
||
VCI |
ATM network virtual channel identifier (VCI) associated with the specified interface. |
||
Type |
Type of VPI/VCI associated with the specified interface. In this release, only PVCs are supported. |
||
Encaps |
Encapsulation type that configured on the specified interface. Possible encapsulation types follow:
|
||
SC |
Service class that is assigned to the specified ATM interface. Possible service classes follow:
|
||
Peak Kbps |
Peak output rate for the bit rate in kbps.
|
||
Avg/Min Kbps |
Number of kilobits per second sent at the average (sustained) rate.
|
||
Burst cells |
Identifies the burst cell size in terms of number of cells. This number is the maximum number of ATM cells the VC can send at the peak rate.
|
||
Sts |
Status of the PVC. Can be “UP” or “DOWN.” |
The following sample output is from the show atm pvc command with the vpi/vci argument included:
RP/0/0/CPU0:router# show atm pvc 10/100
Detailed display of VC(s) with VPI/VCI = 10/100
ATM0/2/0/3.100: VPI: 10 VCI: 100
UBR, PeakRate: 622000 Kbps
AAL5-LLC/SNAP
OAM frequency: 10 second(s), OAM retry frequency: 1 second(s),
OAM up retry count: 3, OAM down retry count: 5,
OAM Keep-vc-up: False, OAM AIS-RDI failure: None,
OAM AIS-RDI down count: 1, OAM AIS-RDI up time: 3 second(s),
OAM Loopback status: No loopback enabled,
OAM VC state: Loopback Not verified,
VC is not managed by OAM,
OAM cells received: 0,
F5 InEndLoop: 0, F5 InSegLoop: 0,
F5 InEndAIS: 0, F5 InSegAIS: 0,
F5 InEndRDI: 0, F5 InSegRDI: 0,
OAM cells sent: 0,
F5 OutEndLoop: 0, F5 OutSegLoop: 0,
F5 OutEndAIS: 0, F5 OutSegAIS: 0,
F5 OutEndRDI: 0, F5 OutSegRDI: 0,
OAM cells drops: 0
InPkts: 0 OutPkts: 0
InBytes: 0 OutBytes: 0
WRED pkt drop: 0
Non WRED pkt drop: 0
Internal state: READY
Status: UP
Field |
Description |
||||
---|---|---|---|---|---|
Detailed display of VC(s) with VPI/VCI |
Displays the following general information for the specified PVC:
|
||||
OAM frequency |
Frequency (in seconds) at which end-to-end F5 OAM loopback cells are transmitted when a change in the up or down state of a PVC is being verified.
|
||||
OAM retry frequency |
Frequency (in seconds) at which end-to-end F5 OAM loopback cells are transmitted when a change in the up or down state is being verified.
|
||||
OAM up retry count |
Number of consecutive end-to-end F5 OAM loopback cell responses that must be received in order to modify a PVC state to up. |
||||
OAM down retry count |
Number of consecutive unreceived end-to-end F5 OAM loopback cell responses allowed before a PVC state changes to down. |
||||
OAM AIS-RDI down count: |
Number of OAM AIS/RDI cells received on a PVC before it is brought down.
|
||||
OAM AIS-RDI up time |
Interval after which a PVC is brought up if it has not received any OAM AIS/RDI cells.
|
||||
OAM Loopback status |
Status of end-to-end F5 OAM loopback cell generation for this VC. Possible value follow: |
||||
OAM VC state |
Current state of the specified VC. Possible VC states follow:
|
||||
OAM cells received |
Number of OAM cells that have been received by this interface. |
||||
F5 InEndLoop: |
Number of end-to-end F5 OAM loopback cells received by this interface. |
||||
F5 InSegLoop |
Number of segment F4 OAM loopback cells received by this interface. |
||||
F5 InAIS |
Number of F4 OAM AIS cells received by this interface. |
||||
F5 InRDI |
Number of F4 OAM RDI cells received by this interface. |
||||
OAM cells sent |
Total number of OAM cells sent on this VC. |
||||
F5 OutEndLoop |
Number of end-to-end F5 OAM loopback cells sent from this interface. |
||||
F5 OutSegLoop |
Number of segment F5 OAM loopback cells sent from this interface. |
||||
F5 OutAIS |
Number of F5 OAM AIS cells sent from this interface. |
||||
F5 OutRDI |
Number of F5 OAM RDI cells sent from this interface. |
||||
OAM cells drops |
Number of OAM cells dropped (or flushed) by this interface. |
||||
InPkts |
Total number of packets received on this VC. This number includes all fast-switched and process-switched packets. |
||||
OutPkts |
Total number of packets sent on this VC. This number includes all fast-switched and process-switched packets. |
||||
InBytes |
Total number of bytes received on this VC. This number includes all fast-switched and process-switched bytes. |
||||
OutBytes |
Total number of bytes sent on this VC. This number includes all fast-switched and process-switched bytes. |
||||
WRED pkt drop |
Total number of AAL5 packets that were dropped by this interface because their size exceeded the maximum threshold set for Weighted Random Early Discard (WRED). |
||||
Non WRED pkt drop |
Total number of dropped AAL5 packets that did not exceeded the maximum threshold set for Weighted Random Early Discard (WRED). |
||||
Internal state |
Internal PVC state. |
||||
Status |
Current status of this PVC. Can be “Up” or “Down.” |
Related Commands
Command | Description |
Creates an ATM PVC with ILMI encapsulation and enters ATM virtual circuit configuration mode. |
show atm pvp
To display ATM PVP and traffic information for the entire router, or a specific VPI or ATM interface, use the show atm pvp command in EXEC mode.
show atm pvp [ vpi | interface atm instance ]
Syntax Description
vpi |
(Optional) ATM virtual path identifier (VPI) number. Replace vpi with the VPI of the PVP whose information you want to display. |
||
interface atm instance |
(Optional) Displays all PVCs on the specified ATM interface.
|
Command Default
Entering the show atm pvp command without specifying the vpi argument or interface atm instance keyword argument displays ATM PVP and traffic information for the entire router.
Command Modes
EXEC (#)
Command History
Release |
Modification |
---|---|
Release 3.4.1 |
This command was introduced. |
Usage Guidelines
Task ID
Task ID |
Operations |
---|---|
atm |
read |
Examples
The following example shows how to display ATM PVP and traffic information for the entire router:
RP/0/0/CPU0:router# show atm pvp interface atm 0/3/0/1
Peak Avg/Min Burst
Interface VPI SC Kbps Kbps Cells Sts
ATM0/3/0/1.100 100 UBR 155000 N/A N/A UP
Field |
Description |
||
---|---|---|---|
Interface |
Interface type and instance. The instance is displayed in the rack/slot/module/port format. |
||
VPI |
ATM network virtual path identifier (VPI) associated with the specified interface. |
||
SC |
Service class that is assigned to the specified ATM interface. Possible service classes follow:
|
||
Peak Kbps |
Peak output rate for the bit rate in kbps.
|
||
Avg/Min Kbps |
Number of kilobits per second sent at the average (sustained) rate.
|
||
Burst cells |
Identifies the burst cell size in terms of number of cells. This number is the maximum number of ATM cells the PVP can send at the peak rate.
|
||
Sts |
Status of the PVP. Can be “UP” or “DOWN.” |
The following example shows how to display ATM PVP and traffic information for the a specific VPI:
RP/0/0/CPU0:router# show atm pvp 100
Detailed display of L2PVP(s) with VPI = 100
ATM0/3/0/1.100: VPI: 100
UBR, PeakRate: 155000 Kbps
AAL0
OAM frequency: 10 second(s), OAM retry frequency: 1 second(s),
OAM up retry count: 3, OAM down retry count: 5,
OAM AIS-RDI down count: 1, OAM AIS-RDI up time: 3 second(s),
OAM Loopback status: No loopback enabled,
OAM L2PVP state: Unknown,
L2PVP is not managed by OAM,
OAM cells received: 0,
F4 InEndLoop: 0, F4 InSegLoop: 0,
F4 InEndAIS: 0, F4 InSegAIS: 0,
F4 InEndRDI: 0, F4 InSegRDI: 0,
OAM cells sent: 8948,
F4 OutEndLoop: 0, F4 OutSegLoop: 0,
F4 OutEndAIS: 8948, F4 OutSegAIS: 0,
F4 OutEndRDI: 0, F4 OutSegRDI: 0,
OAM cells drops: 0
InPkts: 8948 OutPkts: 0
InBytes: 465296 OutBytes: 0
Internal state: READY
Status: UP
Field |
Description |
||||
---|---|---|---|---|---|
ATM0/1/0/0.30 |
Associated interface type and instance in the type rack/slot/module/port.subinterface format.
|
||||
VPI |
VPI associated with the specified PVP. |
||||
UBR |
Service class that is assigned to the specified ATM interface. The example shows that vbr-rt is assigned to the interface that hosts the specified PVP. Possible service classes are: |
||||
PeakRate |
Peak output rate for the bit rate in kbps.
|
||||
AAL0 |
ATM adaptation layer (AAL) and encapsulation type for the PVP. Currently, only AAL0 is the only supported encapsulation type for PVPs. |
||||
OAM frequency |
Frequency (in seconds) at which end-to-end F5 OAM loopback cells are transmitted when a change in the up or down state of a PVC is being verified.
|
||||
OAM retry frequency |
Frequency (in seconds) at which end-to-end F5 OAM loopback cells are transmitted when a change in the up or down state is being verified.
|
||||
OAM up retry count |
Number of consecutive end-to-end F5 OAM loopback cell responses that must be received in order to modify a PVC state to up. |
||||
OAM down retry count |
Number of consecutive unreceived end-to-end F5 OAM loopback cell responses allowed before a PVC state changes to down. |
||||
OAM AIS-RDI down count |
Number of OAM AIS/RDI cells received on a PVC before it is brought down.
|
||||
OAM AIS-RDI up time |
Interval after which a PVC is brought up if it has not received any OAM AIS/RDI cells.
|
||||
OAM Loopback status |
Status of end-to-end F5 OAM loopback cell generation for this VC. Possible value follow: |
||||
OAM L2PVP state |
Current state of the specified VC.
|
||||
OAM cells received |
Number of OAM cells that have been received by this interface. |
||||
F4 InEndLoop: |
Number of end-to-end F4 OAM loopback cells received by this interface. |
||||
F4 InSegLoop |
Number of segment F4 OAM loopback cells received by this interface. |
||||
F4 InEndAIS |
Number of F4 OAM AIS cells received by this interface. |
||||
F4 InSegAIS |
Number of segment F4 OAM AIS cells received by this interface. |
||||
F4 InEndRDI |
Number of F4 OAM RDI cells received by this interface. |
||||
F4 InSegRDI |
Number of F4 segment OAM RDI cells received by this interface. |
||||
OAM cells drops |
Number of OAM cells dropped (or flushed) by this interface. |
||||
InPkts |
Total number of packets received on this VC. This number includes all fast-switched and process-switched packets. |
||||
OutPkts |
Total number of packets sent on this VC. This number includes all fast-switched and process-switched packets. |
||||
InBytes |
Total number of bytes received on this VC. |
||||
OutBytes |
Total number of bytes sent on this VC. |
||||
Internal state |
Internal PVC state. |
||||
Status |
Current status of this PVC. Can be “Up” or “Down.” |
Related Commands
Command | Description |
Creates an ATM PVP and enters ATM layer 2 transport PVP configuration mode. |
show atm vc-class
To display information about all ATM virtual circuit (VC) classes on the router or for a specific ATM VC-class, use the show atm vc-class command in EXEC mode.
show atm vc-class vc-class-name
Syntax Description
vc-class-name |
Name of the VC-class whose information you want to display. |
Command Default
Entering the show atm vc-class command without specifying the vc-class-name argument displays ATM PVC and traffic information for the entire router.
Command Modes
EXEC (#)
Command History
Release |
Modification |
---|---|
Release 3.4.0 |
This command was introduced. |
Release 3.4.1 |
The show atm vc-class command output was modified to include Layer 2 VPN parameters when appropriate. |
Usage Guidelines
Task ID
Task ID |
Operations |
---|---|
atm |
read |
Examples
The following sample output is from the show atm vc-class command:
RP/0/0/CPU0:router# show atm vc-class
ATM vc-class class1
encapsulation - aal5mux ip
shape - cbr 100000
oam ais-rdi - 35
oam retry - 300
oam-pvc - manage 300
ATM vc-class class2
encapsulation - aal5nlpid
shape - ubr 40000
oam ais-rdi - 30
oam retry - 30
oam-pvc - manage 300
ATM vc-class class3
encapsulation - aal5snap
shape - vbr-nrt 60000 60000 1000
oam ais-rdi - 30
oam retry - 30
oam-pvc - manage 300
Field |
Description |
||||
---|---|---|---|---|---|
encapsulation |
Type of ATM adaptation layer (AAL) encapsulation type that is enabled on the specified VC-class. Possible AAL encapsulation types follow:
|
||||
shape |
Displays traffic shaping information for the service class that is assigned to the specified VC-class. Possible service classes follow:
|
||||
oam ais-rdi |
Displays the maximum number of OAM AIS/RDI cells that can be received on a PVC before it is brought down.
|
||||
oam retry |
Displays the following information related to F5 OAM loopback cells, if this information was configured for the specified VC-class:
|
||||
oam-pvc |
Frequency (in seconds) at which end-to-end F5 OAM loopback cells are transmitted on this PVC. Range is from 0 through 600.
|
The following sample output is from the show atm vc-class command with the vc-class-name argument included:
RP/0/0/CPU0:router# show atm vc-class class1
ATM vc-class class1
encapsulation - aal5mux ip
shape - cbr 100000
oam ais-rdi - 35
oam retry - 300
oam-pvc - manage 300
Related Commands
Command | Description |
Attaches a VC class to an ATM PVC. | |
Creates a VC class for an ATM PVC or an ATM interface and enters VC-class configuration mode. |
show atm vp-tunnel
To display virtual path (VP) tunnel information for the entire router or for a specific interface, use the show atm vp-tunnel command in EXEC mode.
show atm vp-tunnel [ interface atm interface-path-id ]
Syntax Description
interface atm |
(Optional) ATM interface for which you want to display information.Use the interface-path-id argument to specify the ATM interface. |
||
interface-path-id |
Physical interface or virtual interface.
For more information about the syntax for the router, use the question mark (?) online help function. |
Command Default
Entering the show atm vp-tunnel command without specifying the instance argument displays ATM VP-tunnel information for the entire router.
Command Modes
EXEC
Command History
Release |
Modification |
---|---|
Release 3.4.0 |
This command was introduced. |
Usage Guidelines
Task ID
Task ID |
Operations |
---|---|
atm |
read |
Examples
The following sample output is from the show atm vp-tunnel command:
RP/0/0/CPU0:router# show atm vp-tunnel Data Peak Avg/Min Burst Interface VPI SC VCs Kbps Kbps Cells Status ATM0/6/0/0 10 CBR 0 155000 N/A N/A DOWN ATM0/6/0/0 20 CBR 0 155000 N/A N/A DOWN ATM0/6/0/0 30 CBR 0 155000 N/A N/A DOWN ATM0/6/0/0 40 CBR 0 155000 N/A N/A DOWN ATM0/6/0/1 10 VBR_NRT 0 155000 155000 800 DOWN ATM0/6/0/1 20 VBR_NRT 0 155000 155000 800 DOWN
Field |
Description |
||
---|---|---|---|
Interface |
Interface type and instance. The instance is displayed in the rack/slot/module/port format. |
||
VPI |
ATM network virtual path identifier (VPI) associated with the specified interface. |
||
SC |
Service class that is assigned to the specified ATM interface. Possible service classes follow:
|
||
Data VCs |
Number of VCs that are attached to the specified VP tunnel. |
||
Peak Kbps |
Peak line rate (bandwidth) required for the specified ATM interface, in kilobits per second.
|
||
Avg/Min Kbps |
Number of kilobits per second sent at the average rate. |
||
Burst Cells |
Identifies the burst cell size in terms of number of cells. This number is the maximum number of ATM cells the VC can send at the peak rate.
|
||
Status |
Current state for this interface. Possible states are “Up” or “Down.” |
The following sample output is from the show atm vp-tunnel command with the interface atm instance keyword argument included:
RP/0/0/CPU0:router# show atm vp-tunnel interface atm 0/6/0/1 Data Peak Avg/Min Burst Interface VPI SC VCs Kbps Kbps Cells Status ATM0/6/0/1 10 VBR_NRT 0 155000 155000 800 DOWN ATM0/6/0/1 20 VBR_NRT 0 155000 155000 800 DOWN
Table 1 describes the significant fields shown in the display.
Related Commands
Command | Description |
Configures a VP tunnel on an interface and enters ATM VP-tunnel configuration mode. |
show controllers atm
To display information about the physical status of the ATM interface, use the show controllers atm command in EXEC mode.
show controllers atm interface-path-id [ all | traffic { f4oam | port | vc vpi/vci | vp vpi } ]
Syntax Description
interface-path-id |
Physical interface or virtual interface.
For more information about the syntax for the router, use the question mark (?) online help function. |
||
f4oam |
Displays information about the ATM layer f4oam traffic that is transmitted and received on the specified interface. |
||
port |
(Optional) Displays information about the ATM layer traffic that is transmitted and received by the ports associated with the specified interface. |
||
vc vpi/vci |
(Optional) Displays information about the ATM layer traffic carried by specific ATM VC (virtual channel). Replace vpi/vci with the ATM virtual path identifier (VPI) and virtual channel identifier (VCI) of the VC whose information you want to display. |
||
vp vpi |
(Optional) Displays information about the ATM layer traffic carried by specific ATM virtual path. Replace vpi with the ATM virtual path identifier (VPI) whose information you want to display. |
Command Default
Entering the show controllers atm command without specifying the instance argument displays ATM controller status and configuration information for the entire router.
Command Modes
EXEC (#)
Command History
Release |
Modification |
---|---|
Release 3.4.0 |
This command was introduced. |
Usage Guidelines
Task ID
Task ID |
Operations |
---|---|
interface |
read |
Examples
The following example shows partial output from the show controllers atm command:
RP/0/0/CPU0:router# show controllers atm 0/6/0/0
SAR Counters:
tx_packets :4085 tx_bytes :212420
tx_total_resource_errs:0 tx_total_other_errs :0
tx_wred_thresh_drops :0 tx_wred_random_drops :0
rx_packets :0 rx_bytes :0
rx_total_resource_errs:0 rx_total_other_errs :0
rx_buffer_exhaust_errs:0 rx_CRC32_errors :0
rx_packet_abort_errs :0 rx_trailer_len_errs :0
rx_mps_errors :0 rx_reassembly_timeout:0
The following are per-SAR counters:
Reassembly SAR:
sys_rx_unopen_vc_cls :0 sys_tx_unopen_vc_cls :0
sys_ecc_errors :0 sys_ecc_and_addr : 0xf
fffffff
sys_ecc_or_addr : 0x0
Segmentation SAR:
sys_rx_unopen_vc_cls :0 sys_tx_unopen_vc_cls:0
sys_ecc_errors :0 sys_ecc_and_addr : 0xf
fffffff
sys_ecc_or_addr : 0x0
RSAR 0: (6.0.2.1c)
RSAR Build ID= E7EE
SSAR 0: (6.0.2.1c)
SSAR Build ID= 570
--More--
Field |
Description |
---|---|
SAR Counters |
Counters that provide information about the Segmentation and Reassembly (SAR) chip. |
tx_packets |
Number of AAL5 packets transmitted. |
tx_bytes |
A 64-bit counter of the bytes transmitted on this interface, including OAM cells and AAL5 header encapsulations (such as AAL5SNAP). This should be approximately the total number of bytes transmitted on each of the VCs. |
tx_total_resource_errs |
Total number of packets that were not transmitted because of any resource exhaustion error. This does not necessarily imply an error, because this counter includes tx_wred_thresh_drops and tx_wred_random_drops, as well as packet drops due to complete buffer exhaustion on the SAR. This should be equal to the sum of the number of resource errors that occur on all the VCs. |
tx_total_other_errs |
Total number of packets that were not transmitted because of any error other than resource exhaustion, but not including no-vc drops. This includes malformed packets, CRC errors, and so on. This should be approximately the total number of tx_other_errors that occur on all the VCs on this interface. |
tx_wred_thresh_drops |
Total number of WRED maximum threshold drops on this interface. This counter is included in the tx_total_resource_errs counter. |
tx_wred_random_drops |
Total number of WRED random drops on this interface. This counter is included in the tx_total_resource_errs counter. |
rx_packets |
Total number of packets reassembled on this interface by the SAR, including OAM cells. |
rx_bytes |
Number of AAL5 packets received on this interface. |
rx_total_resource_errs |
Total number of packet reassemblies that failed due to resource exhaustion. This error should not occur if the queue thresholds are not oversubscribed. This error includes rx_buffer_exhaust_errs. |
rx_total_other_errs |
Total number of packet reassemblIes that failed due to errors besides resource exhaustion (not including “no-vc” cells), including rx_crc32_errors, rx_packet_abort_errs, rx_trailer_len_errs, rx_mps_errors, and rx_reassembly_timeout. |
rx_buffer_exhaust_errs |
Total number of packet reassemblies that failed due to complete buffer exhaustion on the SAR. This error should not occur if the queue thresholds are not oversubscribed. This is included in rx_total_resource_errs. |
sys_tx_unopen_vc_cls |
Total number of packets transmitted by this endpoint that failed due to an error other than those listed in the show controllers atm command output. |
Reassembly SAR |
Counters that provide information specific to the reassembly chip. |
sys_ecc_and_addr |
Total number of single bit end and addressing errors detected on the reassembly SAR. |
sys_ecc_errors |
Total number of single bit errors detected on the reassembly SAR. |
sys_ecc_or_addr |
Total number of single bit end or addressing errors detected on the reassembly SAR. |
Segmentation SAR |
Counters that provide information specific to the segmentation chip. |
sys_tx_unopen_vc_cls |
Total number of packet reassemblies transmitted by this endpoint that failed due to errors other than those listed in the show controllers atm command output. |
sys_rx_unopen_vc_cls |
Total number of packet reassemblies received by this endpoint that failed due to errors other than those listed in the show controllers atm command output. |
rx_CRC32_errors |
Total number of packet reassemblies that failed due to an invalid AAL5 CRC32 trailer. This is included in rx_total_other_errs. |
rx_packet_abort_errs |
Total number of packet reassemblies that failed due to receiving a trailer length of 0. This is included in rx_total_other_errs. |
rx_trailer_len_errs |
Total number of packet reassemblies that failed due to a packet whose AAL5 trailer had an invalid trailer length. This is included in rx_total_other_errs. |
rx_mps_errors |
Total number of packet reassemblies that failed due to a packet size greater than the maximum allowed packet size. This is included in rx_total_other_errs. |
rx_reassembly_timeout |
Total number of packet reassemblies that failed due to timing out before receiving the last cell of a packet. This is included in rx_total_other_errs. |
sys_rx_unopen_vc_cls |
Packets received on nonexistent VC. |
RSAR 0 |
RSAR ID. |
RSAR Build ID |
Unique number that identifies the RSAR build. |
SSAR 0 |
SSAR ID. |
SSAR Build ID |
Unique number that identifies the SAR build. |
Related Commands
Command | Description |
Displays ATM-specific information about an ATM interface. |
shutdown (ATM)
To disable an ATM interface, use the shutdown command in interface configuration mode. To re-enable an ATM interface, use the no form of this command.
shutdown
no shutdown
Syntax Description
This command has no keywords or arguments.
Command Default
The ATM interface is up.
Command Modes
Interface configuration (config-if)
Command History
Release |
Modification |
---|---|
Release 3.4.0 |
This command was introduced. |
Usage Guidelines
Use the show interface atm command in EXEC mode to verify that the ATM interface is administratively up or down.
Task ID
Task ID |
Operations |
---|---|
interface |
read, write |
Examples
The following example shows how to bring down an ATM interface:
RP/0/0/CPU0:router# configure RP/0/0/CPU0:router(config)# interface atm 0/2/0/0 RP/0/0/CPU0:router(config-if)# shutdown
The following example shows how to re-enable an ATM interface that has been brought down with the shutdown command:
RP/0/0/CPU0:router# no shutdown
Related Commands
Command | Description |
Displays ATM-specific information about an ATM interface. |
vc-class atm
To create a virtual circuit (VC) class for an ATM permanent virtual circuit (PVC) or an ATM interface and enter VC-class configuration mode, use the vc-class atm command in global configuration mode. To remove a VC-class, use the no form of this command.
vc-class atm name
no vc-class atm name
Syntax Description
name |
Name of your VC class. |
Command Default
No VC-class is defined.
Command Modes
Global configuration (config)
Command History
Release |
Modification |
---|---|
Release 3.4.0 |
This command was introduced. |
Usage Guidelines
When you issue the vc-class atm command in global configuration mode, the CLI prompt changes to “config-vc-class-atm,” indicating that you have entered the VC-class configuration submode. In the following sample output, the question mark (?) online help function displays all the commands available under the VC-class configuration submode:
RP/0/0/CPU0:router(config)# vc-class atm classA RP/0/0/CPU0:router(config-vc-class-atm)# ? commit Commit the configuration changes to running describe Describe a command without taking real actions do Run an exec command encapsulation Configure encapsulation exit Exit from this submode no Negate a command or set its defaults oam Configure OAM parameters oam-pvc OAM PVC management configuration shape ATM Traffic Shaping show Show contents of configuration RP/0/0/CPU0:router(config-vc-class-atm)#
Task ID
Task ID |
Operations |
---|---|
atm |
read, write |
Examples
The following example shows how to create a VC-class. In this example, the class is called “class1.”
RP/0/0/CPU0:router(config)# vc-class atm class1 RP/0/0/CPU0:router(config-vc-class-atm)#
Related Commands
Command | Description |
Attaches a VC class to an ATM PVC. | |
Displays information about all ATM VC classes on the router or for a specific ATM VC-class. |
vp-tunnel
To configure a virtual path (VP) tunnel on an interface and enter ATM VP-tunnel configuration mode, use the vp-tunnel command in interface configuration mode.
vp-tunnel vpi
Syntax Description
vpi |
VPI for this tunnel. Range is from 0 through 4095. |
Command Default
No default behavior or values
Command Modes
Interface configuration
Command History
Release |
Modification |
---|---|
Release 3.4.0 |
This command was introduced. |
Usage Guidelines
For Vp-tunnels, a VPI of 0 is not supported on the following line cards:
When you issue the vp-tunnel command in global configuration mode, the CLI prompt changes to “config-atm-vp-tunnel,” indicating that you have entered ATM VP-tunnel configuration submode. In the following sample output, the question mark (?) online help function displays all the commands available under the ATM VP-tunnel configuration submode:
RP/0/0/CPU0:router(config-if)# vp-tunnel 10 RP/0/0/CPU0:router(config-atm-vp-tunnel)# ? commit Commit the configuration changes to running describe Describe a command without taking real actions do Run an exec command exit Exit from this submode f4oam F4 OAM configuration no Negate a command or set its defaults shape ATM Traffic Shaping show Show contents of configuration RP/0/0/CPU0:router(config-atm-vp-tunnel)#
Task ID
Task ID |
Operations |
---|---|
atm |
read, write |
Examples
The following example shows how to configure a virtual path (VP) tunnel on an interface and enter ATM VP-tunnel configuration mode:
RP/0/0/CPU0:router(config-if)# vp-tunnel 10 RP/0/0/CPU0:router(config-atm-vp-tunnel)#
Related Commands
Command | Description |
Displays VP tunnel information for the entire router or for a specific interface. |