Table Of Contents
atm sonet threshold
To configure the bit error rate (BER) threshold values for an ATM interface, use the atm sonet threshold command in interface configuration mode. To reset a threshold value to its default value, use the no form of this command.
atm sonet threshold {b1-tca value | b2-tca value | b3-tca value | sd-ber value | sf-ber value}
no atm sonet threshold {b1-tca | b2-tca | b3-tca | sd-ber | sf-ber}
Syntax Description
Defaults
The default values are 6 (10e-6) for b1-tca, b2-tca, b3-tca, and sd-ber. The default value is 3 (10e-3) for sf-ber.
Command Modes
Interface configuration
Command History
Usage Guidelines
The atm sonet threshold command configures the allowable threshold for errors before a Synchronous Optical Network (SONET) alarm is reported. The different SONET alarms report on errors at different points in the SONET network, allowing for the source of a problem to be more easily identified.
Use the atm sonet threshold command to increase or decrease the sensitivity of the ATM interface to these SONET alarms, depending on the nature of your network and application needs. In particular, if a particular problem seems to be occurring, you can increase the sensitivity of the related alarm to help you more quickly troubleshoot and diagnose the problem.
Examples
The following example shows how to configure the threshold for B1 threshold crossings:
Router# configure terminal
Router(config)# interface atm 3/1/1
Router(config-if)# atm sonet threshold b1-tca 9Router(config-if)# end
Router#
Use the show controllers atm command to display the currently configured BER threshold values:
Router# show controllers atm 5/1/0Interface ATM5/1/0 is upFraming mode: SONET OC3 STS-3c Clock source: LineATM framing errors:HCS (correctable): 0HCS (uncorrectable): 0SONET Subblock:APSCOAPS = 0 PSBF = 0State: PSBF_state = falseRx(K1/K2): 0 /0 Tx(K1/K2): 0 /0SECTIONLOF = 0 LOS = 0 BIP(B1) = 603LINEAIS = 0 RDI = 2 FEBE = 2332 BIP(B2) = 1018PATHAIS = 0 RDI = 1 FEBE = 28 BIP(B3) = 228LOP = 0 NEWPTR = 0 PSE = 1 NSE = 2Active Defects: NoneActive Alarms: NoneAlarm reporting enabled for: SF SLOS SLOF B1-TCA B2-TCA PLOP B3-TCABER thresholds: SF = 10e-3, SD = 10e-6TCA thresholds: B1 = 10e-6, B2 = 10e-6, B3 = 10e-6Rx S1S0 = 00, Rx C2 = 13PATH TRACE BUFFER : STABLERouter#
Note
The actual display from the show controllers atm command varies slightly, depending on the type of line card.
Related Commands
atm svc-upc-intent
To change the intended usage parameter control (UPC) mode that is to be used on the cell flow received into the switch fabric for switched virtual circuits (SVCs) or destination legs of soft permanent virtual circuits (PVCs) on an interface, use the atm svc-upc-intent command in interface configuration mode. Any change in this parameter is applied to SVCs or soft PVCs subsequently established on the interface. To assign the default value to the parameter, use the no form of this command.
atm svc-upc-intent [abr | cbr | vbr-rt | vbr-nrt | ubr] {tag | pass | drop}
no atm svc-upc-intent
Syntax Description
Command Default
Cells received on the interface are passed to the switching fabric with no change, regardless of their conformance to the traffic contract.
Command Modes
Interface configuration
Command History
Usage Guidelines
This configuration parameter determines the UPC to use for SVCs and for the destination leg of soft VC and VP. If policing is desired, it should be applied once for traffic entering a network.
Examples
In the following example, the intended UPC for SVCs on an interface is set to tagging:
Router(config-if)# atm svc-upc-intent tagIn the following example, the UBR traffic on an interface is passed while all other traffic is policed:
Router(config-if)# atm svc-upc-intent ubr passRouter(config-if)# atm svc-upc-intent cbr tagRouter(config-if)# atm svc-upc-intent vbr-rt tagRouter(config-if)# atm svc-upc-intent vbr-nrt tagRouter(config-if)# atm svc-upc-intent abr dropRelated Commands
atm txbuff
To set the maximum number of transmit buffers for simultaneous packet fragmentation, use the atm txbuff command in interface configuration mode. To restore the default value, use the no form of this command.
atm txbuff number
no atm txbuff
Syntax Description
number
Maximum number of packet fragmentations that the ATM Interface Processor (AIP) can perform simultaneously. Range is from 0 to 512. Default is 256.
Defaults
256
Command Modes
Interface configuration
Command History
Usage Guidelines
This command is supported on the AIP for Cisco 7500 series routers. This command is not supported on the ATM port adapter for Cisco 7200 and 7500 series routers, nor is it supported on Cisco 4500 and Cisco 4700 routers.
Examples
The following example configures the AIP to perform up to 300 packet fragmentations simultaneously:
atm txbuff 300atm tx-latency
To specify the default transmit latency for an ATM Shared Port Adapter (SPA) interface, use the atm tx-latency command in interface configuration mode. To reset the default transmit latency to its default value, use the no form of this command.
atm tx-latency milliseconds
no atm tx-latency
Syntax Description
milliseconds
The default transmit latency for the interface, in milliseconds. The valid range is from 1 to 200, with a default of 100 milliseconds.
Defaults
100 milliseconds
Command Modes
Interface configuration (ATM interface only)
Command History
Usage Guidelines
The atm tx-latency command specifies the default maximum latency for all virtual circuits (VC) on a particular ATM SPA interface. This value is used, together with the value of the tx-limit command, to configure the interface and its VCs for the maximum number of transmit buffers for each VC, so that each VC can maintain the desired latency at the VC's configured line rate.
Caution
Tip
Examples
The following example shows the default transmit latency for a particular ATM SPA interface being set to 20 milliseconds:
Router# configure terminalRouter(config)# interface atm 3/1/1Router(config-if)# atm tx-latency 20Router(config-if)#Related Commands
tx-limit
Specifies the maximum number of transmit buffers for an ATM virtual circuit (VC).
atm uni-version
To specify the User-Network Interface (UNI) version (3.0 or 3.1) the router should use when Interim Local Management Interface (ILMI) link autodetermination is unsuccessful or ILMI is disabled, use the atm uni-version command in interface configuration mode. To restore the default value to 3.0, use the no form of this command.
atm uni-version version-number
no atm uni-version version-number
Syntax Description
Defaults
Version 3.0
Command Modes
Interface configuration
Command History
Usage Guidelines
Normally, when the ILMI link autodetermination is enabled on the interface and is successful, the router accepts the UNI version returned by ILMI. If the ILMI link autodetermination is unsuccessful or ILMI is disabled, the UNI version defaults to 3.0. You can override the default UNI version by using this command to enable UNI 3.1 signalling support. The no form of the command sets the UNI version to one returned by ILMI if ILMI is enabled and the link autodetermination process is successful. Otherwise, the UNI version reverts to 3.0.
Examples
The following example specifies UNI version 3.1 signaling port on the ATM interface 2/0:
interface atm 2/0atm uni-version 3.1atm vc-per-vp
To set the maximum number of virtual channel identifier (VCIs) to support per virtual path identifier (VPI), use the atm vc-per-vp interface configuration command. To restore the default value, use the no form of this command.
atm vc-per-vp number
no atm vc-per-vp
Syntax Description
Defaults
1024
Command Modes
Interface configuration
Command History
Usage Guidelines
This command controls the memory allocation in the ATM Interface Processor (AIP), ATM port adapter, ATM network module, or network processor module (NPM) to deal with the VCI table. It defines the maximum number of VCIs to support per VPI; it does not bound the VCI numbers.
An invalid VCI causes a warning message to be displayed.
Cisco 2600 and 3600 Series with IMA
Note
Table 9 lists the possible VCI ranges and corresponding VPI ranges for the Cisco 2600 and 3600 series with IMA.
Table 9 VCI and VPI Ranges for Cisco 2600 and 3600 Series with IMA
0-255
0-15, 64-79, 128-143, and 192-207
0-511
0-15, 64-79
0-1023
0-15
Examples
The following example sets the maximum number of VCIs per VPI to 512:
atm vc-per-vp 512Related Commands
atm vp-filter
To set the ATM Interface Processor (AIP) filter register, use the atm vp-filter command in interface configuration mode. To restore the default value, use the no form of this command.
atm vp-filter hexvalue
no atm vp-filter
Syntax Description
Defaults
0x7B
Command Modes
Interface configuration
Command History
Usage Guidelines
This command is supported on Cisco 7500 series routers, but not on Cisco 4500 and Cisco 4700 routers. This command is not supported on ATM port adapters.
This command allows you to specify a virtual path identifier (VPI) or range of VPIs to be used for ATM adaptation layer 3/4 (AAL3/4) processing. All other VPIs map to AAL5 processing. If only AAL5 processing is required, you can either let the virtual path filter default or set it to an arbitrary VPI so that AAL5 processing is performed on all VPIs.
This command configures the hexadecimal value used in the virtual path filter register in the reassembly operation. The virtual path filter comprises 16 bits. The virtual path filter register uses the most significant bits (bits 15 through 8, the left half of the filter) as mask bits, and uses bits 7 through 0 (the right half of the filter) as compare bits.
When a cell is received, the right half of the filter is exclusively NORed with the binary value of the incoming VPI. The result is then ORed with the left half of the filter (the mask). If the result is all ones, reassembly is done using the VCI/message identifier (MID) table (AAL3/4 processing). Otherwise, reassembly is done using the VPI-VCI pair table (AAL5 processing).
Examples
In the following example, all incoming cells are reassembled using AAL3/4 processing:
atm vp-filter ff00In the following example, all incoming cells with the virtual path equal to 0 are reassembled using AAL3/4 processing; all other cells are reassembled using AAL5 processing:
atm vp-filter 0In the following example, all incoming cells with the most significant bit of the virtual path set are reassembled using AAL3/4 processing; all other cells are reassembled using AAL5 processing:
atm vp-filter 7f80atm-address
To override the control ATM address of a Multiprotocol over ATM client (MPC) or a Multiprotocol over ATM server (MPS), use the atm-address command in interface configuration mode. To revert to the default address, use the no form of this command.
atm-address atm-address
no atm-address
Syntax Description
Command Default
An automatically-generated ATM address is used.
Command Modes
Interface configuration
Command History
Usage Guidelines
This command specifies the control ATM address that an MPC or MPS should use when it comes up if it is associated with a hardware interface.
The atm-address command overrides the default operational control address of the MPC or MPS. When this address is deleted (using the no form of the command), the MPC or MPS uses an automatically generated address as its control address.
Examples
The following example shows how to specify the ATM address for an MPC:
Router(config-if)# atm-address 47.0091810000000061705b7701.00400BFF0011.00The following example shows how to specify the ATM address for an MPS:
Router(config-if)# atm-address 47.0091810000000061705C2B01.00E034553024.00atmsig close atm
To disconnect a switched virtual circuit (SVC), use the atmsig close atm command in EXEC mode.
AIP on Cisco 7500 series; ATM, ATM-CES, Enhanced ATM Port Adapter on Cisco 7200 Series; 1-port ATM-25 Network Module on Cisco 2600 and 3600 Series
atmsig close atm slot/port vcd
ATM and Enhanced ATM Port Adapter on Cisco 7500 series
atmsig close atm slot/port-adapter/port vcd
NPM on Cisco 4500 and Cisco 4700
atmsig close atm number vcd
Syntax Description
Command Modes
EXEC
Command History
Usage Guidelines
Execute this command if you want to close a particular SVC. Because virtual circuits are numbered per interface, you must specify the ATM interface by its slot number.
Examples
The following example closes SVC 2 on ATM interface 4/0:
atmsig close atm4/0 2bre-connect
To enable the bridging of routed encapsulations (BRE) over a permanent virtual circuit (PVC) or switched virtual circuit (SVC), use the bre-connect command in VC configuration mode. To disable the bridging of routed encapsulations, use the no form of this command.
bre-connect vlan-id [mac mac-address]
no bre-connect
Syntax Description
Command Default
Bridging of route encapsulations is disabled.
Command Modes
VC configuration mode
Command History
Usage Guidelines
The bre-connect command allows the OC-12 ATM OSM or ATM SPA to receive RFC 1483 routed encapsulated packets and forward them as Layer 2 frames. When the bre-connect command is configured on a PVC (or SVC), the PVC (or SVC) receives routed packets, removes the RFC 1483 routed encapsulation header, and adds an Ethernet MAC header to the packet. The Layer 2 encapsulated packet is then switched to the Layer 2 interface that is determined by the VLAN number and the MAC address for the remote CPE device (if specified).
Note
Note
Examples
The following example shows a PVC being configured for BRE bridging using a VLAN ID of 10:
Router# configure terminal
Router(config)# interface atm3/1.1 point-to-point
Router(config-subif)# pvc 1/101
Router(config-if-atm-vc)# bre-connect 10
Router(config-if-atm-vc)# endRelated Commands
bridge-vlan
Configures a PVC for RFC 1483-compliant, point-to-point bridging of Layer 2 packets over an ATM interface.
show atm pvc
Displays the configuration of a particular permanent virtual circuit (PVC).
bridge-domain
To enable RFC 1483 ATM bridging or RFC 1490 Frame Relay bridging to map a bridged VLAN to an ATM permanent virtual circuit (PVC) or Frame Relay data-link connection identifier (DLCI), use the bridge-domain command in Frame Relay DLCI configuration, interface configuration, interface ATM VC configuration, or PVC range configuration mode. To disable bridging, use the no form of this command.
bridge-domain vlan-id [access | dot1q [tag] | dot1q-tunnel] [broadcast] [ignore-bpdu-pid] [pvst-tlv CE-vlan] [increment] [lan-fcs] [split-horizon]
no bridge-domain vlan-id
Syntax Description
Command Default
Bridging is disabled.
Command Modes
Frame Relay DLCI configuration
Interface configuration—Only the dot1q and dot1q-tunnel keywords are supported in interface configuration mode.
Interface ATM VC configuration
PVC range configurationCommand History
Usage Guidelines
RFC 1483 bridging on ATM interfaces supports the point-to-point bridging of Layer 2 packet data units (PDUs) over Ethernet networks. RFC 1490 Frame Relay bridging on Packet over SONET (POS) or serial interfaces that are configured for Frame Relay encapsulation provides bridging of Frame Relay packets over Ethernet networks.
The Cisco 7600 router can transmit BPDUs with a PID of either 0x00-0E or 0x00-07. When the router connects to a device that is fully compliant with RFC 1483 Appendix B, in which the IEEE BPDUs are sent and received by the other device using a PID of 0x00-0E, you must not use the ignore-bpdu-pid keyword.
If you do not enter the ignore-bpdu-pid keyword, the PVC between the devices operates in compliance with RFC 1483 Appendix B. This is referred to as strict mode. Entering the ignore-bpdu-pid keyword creates loose mode. Both modes are described as follows:
•
•
Cisco-proprietary PVST+ BPDUs are always sent out on data frames using a PID of 0x00-07, regardless of whether you enter the ignore-bpdu-pid keyword.
Use the ignore-bpdu-pid keyword when connecting to devices such as ATM digital subscriber line (DSL) modems that send PVST (or 802.1D) BPDUs with a PID of 0x00-07.
The pvst-tlv keyword enables BPDU translation when the router interoperates with devices that understand only PVST or IEEE Spanning Tree Protocol. Because the Catalyst 6500 series switch ATM modules support PVST+ only, you must use the pvst-tlv keyword when connecting to a Catalyst 5000 family switch that understands only PVST on its ATM modules, or when connecting with other Cisco IOS routers that understand IEEE format only.
When the router or switch is transmitting, the pvst-tlv keyword translates PVST+ BPDUs into IEEE BPDUs.
When the router or switch is receiving, the pvst-tlv keyword translates IEEE BPDUs into PVST+ BPDUs.
Note
To preserve class of service (CoS) information across the ATM network, use the dot1q option. This configuration uses IEEE 802.1Q tagging to preserve the VLAN ID and packet headers as they are transported across the ATM network.
To enable service providers to use a single VLAN to support customers that have multiple VLANs, while preserving customer VLAN IDs and segregating traffic in different customer VLANs, use the dot1q-tunnel option on the service provider router. Then use the dot1q option on the customer routers.
Note
RFC 1483 bridging is supported on AAL5-MUX and AAL5-LLC Subnetwork Access Protocol (SNAP) encapsulated PVCs. RFC-1483 bridged PVCs must terminate on the ATM interface, and the bridged traffic must be forwarded over an Ethernet interface, unless the split-horizon option is used, which allows bridging of traffic across bridged PVCs.
Note
In interface configuration mode, only the dot1q and dot1q-tunnel keyword options are supported.
Examples
The following example shows a PVC being configured for IEEE 802.1Q VLAN bridging using a VLAN ID of 99:
Router# configure terminalRouter(config)# interface ATM6/2Router(config-if)# pvc 2/101Router(config-if-atm-vc)# bridge-domain 99 dot1qRouter(config-if-atm-vc)# endThe following example shows how to enable BPDU translation when a Catalyst 6500 series switch is connected to a device that understands only IEEE BPDUs in an RFC 1483-compliant topology:
Router(config-if-atm-vc)# bridge-domain 100 pvst-tlv 150The ignore-bpdu-pid keyword is not used because the device operates in an RFC 1483-compliant topology for IEEE BPDUs.
The following example shows how to enable BPDU translation when a Catalyst 5500 ATM module is a device that understands only PVST BPDUs in a non-RFC1483-compliant topology. When a Catalyst 6500 series switch is connected to a Catalyst 5500 ATM module, you must enter both keywords.
Router(config-if-atm-vc)# bridge-domain 100 ignore-bpdu-pid pvst-tlv 150To enable BPDU translation for the Layer 2 Protocol Tunneling (L2PT) topologies, use the following command:
Router(config-if-atm-vc)# bridge-domain 100 dot1q-tunnel ignore-bpdu-pid pvst-tlv 150The following example shows a range of PVCs being configured, with the bridge domain number being incremented for each PVC in the range:
Router(config)# interface atm 8/0.100Router(config-subif)# range pvc 102/100 102/199Router(config-if-atm-range)# bridge-domain 102 incrementRelated Commands
bre-connect
Enables the BRE over a PVC or SVC.
show atm pvc
Displays the configuration of a particular PVC.
bridge-dot1q encap
To add a VLAN ID at an ATM PVC over an ATM xDSL link, use the bridge-dot1q encap command in PVC configuration mode. To prevent a VLAN ID from being sent across the link, use the no form of this command.bridge-dot1q encap outgoing_vlan_id
no bridge-dot1q encap outgoing_vlan_id
Syntax Description
outgoing_vlan_id
The VLAN ID to be carried over ADSL. The valid value of the VLAN ID can range from 1 to 4094.
Command Default
PVC configuration mode.
Command Modes
ATM PVC configuration modes (config-if-atm-vc)
Command History
Usage Guidelines
You can configure only one bridge-dot1q encap 802.1Q VLAN tag under a PVC.
If the incoming packet at the FE port contains an ingress 802.1Q tag, then the incoming packet is replaced by the egress 802.1Q tag while forwarding the packet over ADSL.
The Transporting 802.1q tag over PVC feature is supported only for AAL5-SNAP encapsulation.
Examples
The following example of configuring one bridge-dot1q encap 802.1Q VLAN tag under a PVC:
Router> enableRouter# configure terminalRouter(config)# interface ATM0.100 point-to-pointRouter(config-if)# pvc 1/1Router(config-if-atm-vc)# bridge-dot1q encap 100Router(config-if-atm-vc)# endRelated Commands
show atm pvc
Displays all ATM permanent virtual connections (PVCs) and traffic information.
broadcast
To configure broadcast packet duplication and transmission for an ATM virtual circuit (VC) class, permanent virtual circuit (PVC), switched virtual circuit (SVC), or VC bundle, use the broadcast command in the appropriate command mode. To disable transmission of broadcast packets for your ATM VC class, PVC, SVC, or VC bundle, use the no form of this command. To restore the default behavior according to the description in the "Usage Guidelines" section, use the default form of this command.
broadcast
no broadcast
default broadcast
Syntax Description
This command has no arguments or keywords.
Command Default
Broadcast transmission is not enabled.
For classical IP SVCs, broadcast is enabled.Command Modes
Interface-ATM-VC configuration (for ATM PVCs and SVCs)
VC-class configuration (for a VC-class)
Bundle configuration (for a VC bundle)
PVC range configuration (for an ATM PVC range)
PVC-in-range configuration (for an individual PVC within a PVC range)Command History
Usage Guidelines
If broadcasting and multipoint signalling are enabled on an SVC, a multipoint SVC will be created to handle the SVC.
Note
If the broadcast command is not explicitly configured on an ATM PVC, SVC, or VC bundle, the VC inherits the following default configuration (listed in order of precedence):
•
•
•
Note
To use the broadcast command in bundle configuration mode, enter the bundle command to enact bundle configuration mode for the bundle for which you want to enable broadcast forwarding.
Examples
The following example enables the transmission of broadcast packets on an ATM PVC named "router5":
pvc router5 1/32 broadcastThe following example enables the transmission of broadcast packets on an ATM PVC bundle named "bundle1":
bundle bundle1 broadcastRelated Commands
cbr
To configure the constant bit rate (CBR) for the ATM circuit emulation service (CES) for an ATM permanent virtual circuit (PVC) on the Cisco MC3810 or the PA-A3 port adapter for the Cisco 7200 and 7500 series routers, use the cbr command in the appropriate configuration mode. To restore the default, use the no form of this command.
cbr rate
no cbr rate
Syntax Description
Command Default
The CBR is not configured.
Command Modes
Interface-ATM-VC configuration (for ATM PVCs and SVCs)
PVC range configuration (for an ATM PVC range)
PVC-in-range configuration (for an individual PVC within a PVC range)
ATM PVP configurationCommand History
Usage Guidelines
This command applies to ATM configuration on the Cisco MC3810 and the PA-A3 port adapter on the Cisco 7200 and 7500 series routers.
Examples
The following example configures the constant bit rate on ATM PVC 20 on the Cisco MC3810:
pvc 20cbr 56Related Commands
ces
To configure circuit emulation service (CES) on a router port and enter CES configuration mode, use the ces command in global configuration mode.
ces slot/port
Syntax Description
slot/port
Backplane slot number and port number on the interface. The port value is always 0 because the interface configuration applies to all ports in the slot. The slash (/) is required.
Command Default
No CES interface is configured.
Command Modes
Global configuration
Command History
Usage Guidelines
This command is used on Cisco 2600 series and 3600 series routers that have OC-3/STM-1 ATM CES network modules.
The ces command enters CES configuration mode. Use CES configuration mode to configure CES parameters such as the CES clock.
Examples
The following example configures the CES interface in slot 2:
ces 2/0Related Commands
ces aal1 clock
To configure the ATM adaptation layer 1 (AAL1) timing recovery clock for the constant bit rate (CBR) interface, use the ces aal1 clock command in interface configuration mode. To return the clock to the default, use the no form of this command.
ces aal1 clock {adaptive | srts | synchronous}
no ces aal1 clock
Syntax Description
Defaults
The timing recovery is set to synchronous for structured mode.
Command Modes
Interface configuration
Command History
Usage Guidelines
The clock mode must be synchronous for structured mode. In unstructured mode, use the adaptive keyword when a network-derived clock is not available.
Use the srts keyword when a network-derived clock is available but devices attached to the CES port use a different clock reference. The srts keyword samples the incoming clock, subtracts from the network clock, and sends the remainder in an AAL1 header. The clock is reconstructed during output by adding the residual to the network reference.
Use the synchronous keyword for all other modes.
Examples
The following command sets the AAL1 timing recovery clock to adaptive mode:
interface cbr 4/0ces aal1 clock adaptiveRelated Commands
ces aal1 service
To configure the type of circuit emulation service used on the constant bit rate (CBR) interface, use the ces aal1 service command in interface configuration mode. To return the type of service to unstructured, use the no form of this command.
ces aal1 service {structured | unstructured}
no ces aal1 service
Syntax Description
structured
Sets the type of service to structured (cross-connect).
unstructured
Sets the type of service to unstructured (clear-channel).
Defaults
The type of service is set to unstructured (clear-channel).
Command Modes
Interface configuration
Command History
Usage Guidelines
The structured keyword means that each time slot is an independent entity grouped into circuits, where each circuit has an independent permanent virtual circuit (PVC).
The unstructured keyword reduces the incoming serial data on the receiving end of the ATM network. The keyword also sets the service to single circuit, single PVC, where all time slots are carried.
Examples
The following example changes the mode for the ces aal1 service command to structured:
interface cbr 4/0ces aal1 service structuredRelated Commands
ces circuit
To configure the connection attributes for the constant bit rate (CBR) interface, use the ces circuit command in interface configuration mode. To return the connection attributes to the default or to enable the circuit, use the no form of this command.
ces circuit circuit-number [cas | no cas] [cdv range] [circuit-name name] [on-hook-detection hex-number] [partial-fill range] [shutdown | no shutdown] [timeslots range]
no ces circuit circuit-number [[no] cas] [cdv range] [circuit-name name] [on-hook-detection hex-number] [partial-fill range] [[no] shutdown] [timeslots range]
Syntax Description
Command Default
No circuit is configured.
Command Modes
Interface configuration
Command History
Usage Guidelines
Channel-associated signalling (CAS) provides information about the time slot (on or off the hook) and is updated once per multiframe.
With both the CAS and on-hook detection features enabled, these features work together to enable an ingress node in an ATM network to monitor on-hook and off-hook conditions for a specified 1 x 64 structured CES circuit. As implied by the notation "1 x 64," the on-hook detection (or bandwidth-release) feature is supported only in a structured CES circuit that involves a single time slot at each end of the connection.
The time slot configured for the structured CES circuit at the ingress node (time slot 2) can be different from the DS0 time slot configured at the egress node (time slot 4). Only one such time slot can be configured at each end of the circuit when the on-hook detection feature is used.
When you invoke the on-hook feature, the ingress ATM-CES port adapter monitors the ABCD bits in the incoming CBR bit stream to detect on-hook and off-hook conditions in the circuit. In an "off-hook" condition, all the bandwidth provisioned for the specified CES circuit is used for transporting ATM AAL1 cells across the network from the ingress node to the egress node.
In an on-hook condition, the network periodically sends dummy ATM cells from the ingress node to the egress node to maintain the connection. However, these dummy cells consume only a fraction of the circuit's reserved bandwidth, leaving the rest of the bandwidth available for use by other network traffic. This bandwidth-release feature enables the network to make more efficient use of its resources.
When the CAS feature is enabled for a CES circuit, the bandwidth of the DS0 channel is limited to 56 kbps for user data, because CAS functions consume 8 kbps of channel bandwidth for transporting the ABCD signalling bits. These signalling bits are passed transparently from the ingress node to the egress node as part of the ATM AAL1 cell stream.
In summary, when the optional CAS and on-hook detection features are enabled, the following conditions apply:
•
•
•
•
Examples
The following example sets the structured service CDV range to 5000 milliseconds and enables the interface:
interface cbr 4/0ces circuit 3 cdv 5000ces circuit 3 no shutdownRelated Commands
ces dsx1 clock source
To configure a transmit clock source for the constant bit rate (CBR) interface, use the ces dsx1 clock source command in interface configuration mode. To return the clock source to the default, use the no form of this command.
ces dsx1 clock source {loop-timed | network-derived}
no ces dsx1 clock source
Syntax Description
loop-timed
Configures the transmit clock to loop (RX-clock to TX-clock).
network-derived
Configures the transmit clock to be derived from the network.
Command Default
The transmit clock is derived from the network.
Command Modes
Interface configuration
Command History
Examples
The following example sets the clock source to loop-timed:
interface cbr 4/0ces dsx1 clock source loop-timedRelated Commands
ces dsx1 framing
To select the frame type for the data line on the constant bit rate (CBR) interface, use the ces dsx1 framing command in interface configuration mode. To return the frame type to the default, use the no form of this command.
T1
ces dsx1 framing {esf | sf}
no ces dsx1 framing
E1
ces dsx1 framing {e1_crc_mfCASlt | e1_crc_mf_lt | e1_lt | e1_mfCAS_lt}
no ces dsx1 framing
Syntax Description
Defaults
esf (for T1)
e1_lt (for E1)Command Modes
Interface configuration
Command History
Usage Guidelines
Use this command in configurations where the router communicates with the data line. The service provider determines which framing type is required for your circuit.
Examples
The following example sets the data line type to super frame:
interface cbr 4/0ces dsx1 framing sfRelated Commands
ces dsx1 lbo
To configure cable length for the constant bit rate (CBR) interface, use the ces dsx1 lbo command in interface configuration mode. To return the cable length to the default, use the no form of this command.
ces dsx1 lbo length
no ces dsx1 lbo
Syntax Description
length
Sets the cable length. Values (in feet) are 0_110, 110_200, 220_330, 330_440, 440_550, 550_660, 660_above, and square_pulse. Values represent a range in feet.
Defaults
0_110 feet
Command Modes
Interface configuration
Command History
Usage Guidelines
Set the cable length to the desired number of feet on your system.
Examples
The following example sets the cable length to 440 feet:
interface cbr 4/0ces dsx1 lbo 440_550Related Commands
ces dsx1 linecode
To select the line code type for the constant bit rate (CBR) interface, use the ces dsx1 linecode command in interface configuration mode. To return the line code to the default, use the no form of this command.
T1
ces dsx1 linecode {ami | b8zs}
no ces dsx1 linecode
E1
ces dsx1 linecode {ami | hdb3}
no ces dsx1 linecode
Syntax Description
Defaults
For T1 interfaces, B8ZS is used as the line code type. For E1 interfaces, HDB3 is used as the line code type.
Command Modes
Interface configuration
Command History
Usage Guidelines
Use this command in configurations where the switch communicates with the data line. The service provider determines which line code type is required for your circuit.
Examples
The following example specifies B8ZS as the line code type:
interface cbr 4/0ces dsx1 linecode b8zsRelated Commands
ces dsx1 loopback
To enable a loopback for the constant bit rate (CBR) interface, use the ces dsx1 loopback command in interface configuration mode. To disable the loopback, use the no form of this command.
ces dsx1 loopback {line | noloop | payload}
no ces dsx1 loopback {line | noloop | payload}
Syntax Description
Command Default
No loopback is enabled.
Command Modes
Interface configuration
Command History
Usage Guidelines
This command is useful for testing the circuit emulation port adapter module.
Examples
The following example sets a payload loopback:
interface cbr 4/0ces dsx1 loopback payloadRelated Commands
ces dsx1 signalmode robbedbit
To enable the signal mode as robbed bit on a constant bit rate (CBR) interface, use the ces dsx1 signalmode robbedbit command in interface configuration mode. To return the signal mode to the default, use the no form of this command.
ces dsx1 signalmode robbedbit
no ces dsx1 signalmode robbedbit
Syntax Description
This command has no arguments or keywords.
Command Default
No signal mode is enabled.
Command Modes
Interface configuration
Command History
Usage Guidelines
A T1 frame consists of 24 time slots (DS0) that send at a rate of 64 kbps. T1 defines the ability to send signaling in-band on individual time slots by removing the low bit of each byte for signaling in robbedbit mode. This procedure allows 8 kbps for signalling and leaves 56 kbps for data.
In structured mode, you can send the T1 signalling information across the network. Structured mode means that after you enable robbedbit signalling mode on the port, and enable CAS on individual circuits that need this type of service, you are robbing bits from the DS0. The system then puts the bits in the specified format to be sent across the network and reinserts them at the passive side on the CES-IWF connection.
Examples
The following example enables channel-associated signaling and robbed-bit signaling:
interface cbr 4/0ces circuit 1 casces dsx1 signalmode robbedbitRelated Commands
ces partial-fill
To configure the number of user octets per cell for the ATM circuit emulation service (CES), use the ces partial-fill command in interface configuration mode. To delete the CES partial-fill value, use the no form of this command.
ces partial-fill octets
no ces partial-fill octets
Syntax Description
octets
Number of user octets per cell for the CES. Possible values of octet range from 0 to 47. The default is 47.
Defaults
47 octets
Command Modes
Interface configuration
Command History
Usage Guidelines
This command applies to ATM configuration on the Cisco MC3810.
Setting the value of the ces partial-fill command to zero disables partial cell fill and causes all cells to be completely filled before they are sent. This command is supported on serial ports 0 and 1 when the encapsulation atm-ces command is enabled.
Examples
The following example sets the CES partial cell fill to 20 octets per cell for serial port 0:
interface serial 0ces partial-fill 20Related Commands
ces pvc
To configure the destination port for the circuit on the constant bit rate (CBR) interface, use the ces pvc command in interface configuration mode. To remove the destination port on the circuit, use the no form of this command.
ces pvc circuit-number interface atm slot/port vpi number vci number
no ces pvc circuit-number interface atm slot/port vpi number vci number
Syntax Description
Command Default
No destination port is configured.
Command Modes
Interface configuration
Command History
Usage Guidelines
Use the interface option to create a hard PVC. Use the dest-atm-addr option to create a soft PVC. Soft PVCs are not supported on Cisco 7200 series routers.
You must configure both sides of the CES circuits because at the source (the active side in CES-IWF), the time slots are not recognized at the destination (the passive side).
Each CES circuit has an ATM address. When configuring the source PVC, you need the destination ATM address.
Examples
The following example shows setting a hard PVC. In this example, the destination of ATM port 0 in slot 1 is assigned to circuit 31 on CBR port 0 in slot 1.
interface cbr 1/0ces pvc 31 interface atm 1/0 vpi 0 vci 512Related Commands
ces-cdv
To set the cell delay variation, use the ces-cdv command in interface-ATM-VC configuration mode.
ces-cdv time
Syntax Description
time
Maximum tolerable cell arrival jitter with a range from 1 to 65535 microseconds. Default is 5000.
Defaults
5000 microseconds
Command Modes
Interface-ATM-VC configuration
Command History
Usage Guidelines
This command is used on Cisco 2600 series and 3600 series routers that have OC-3/STM-1 ATM CES network modules.
Examples
The following example configures the maximum tolerable cell arrival jitter at 7500 microseconds:
interface atm1/0pvc 0 0/41 cesces-cdv 7500Related Commands
class-int
To assign a virtual circuit (VC) class to an ATM main interface or subinterface, 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
Command Default
No VC class is assigned to an ATM main interface or subinterface.
Command Modes
Interface configuration
Command History
Usage Guidelines
Use this command to assign a previously defined set of parameters (defined in a VC class) to an ATM main interface or subinterface. To create a VC class that defines these parameters, use the vc-class atm command. Refer to the section "Configuring VC Classes" in the "Configuring ATM" chapter of the Cisco IOS Wide-Area Networking Configuration Guide for more information.
To use this command for assigning a VC class to an ATM main interface or subinterface, you must first enter the interface atm command to enter interface configuration mode.
When you create a VC class for an ATM main interface or subinterface, you can use the following commands to define your parameters: abr, broadcast, bump, encapsulation, idle-timeout, ilmi manage, inarp, oam-bundle, oam-pvc, oam retry, oam-svc, protocol, ubr, ubr+, and vbr-nrt.
Parameters 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.
Examples
In the following example, a class called "classA" is first created and then applied to ATM main interface 2/0:
! The following commands create the class classA:vc-class atm classAubr 10000encapsulation aal5mux ip! The following commands apply classA to ATM main interface 2/0:interface atm 2/0class-int classARelated Commands
class-vc
To assign a virtual circuit (VC) class to an ATM permanent virtual circuit (PVC), switched virtual circuit (SVC), or VC bundle member, use the class-vc command in the appropriate configuration mode. To remove a VC class, use the no form of this command.
class-vc name
no class-vc name
Syntax Description
Command Default
No VC class is assigned.
Command Modes
Bundle-vc configuration (for VC bundle members)
Interface-ATM-VC configuration (for ATM PVCs and SVCs)
PVC-in-range configuration (for an individual PVC within a PVC range)Command History
Usage Guidelines
Use this command to assign a previously defined set of parameters (defined in a VC class) to an ATM PVC, SVC, or VC bundle member. To create a VC class that defines these parameters, use the vc-class atm command.
ATM PVCs and SVCs
To use this command for assigning a VC class to an ATM PVC or SVC, you must first enter the interface atm command in global configuration mode and then the pvc or svc command in interface configuration mode.
When you create a VC class for an ATM PVC or SVC, you can use the following commands to define your parameters: abr, broadcast, bump, encapsulation, idle-timeout, ilmi manage, inarp, oam-bundle, oam-pvc, oam retry, oam-svc, protocol, ubr, ubr+, and vbr-nrt.
Parameters that are configured for a PVC or SVC through discrete commands entered in interface-ATM-VC configuration mode supersede VC class parameters assigned to an ATM PVC or SVC by the class-vc command.
ATM VC Bundle Members
To use this command for assigning a VC class to a VC bundle member, you must first use the pvc-bundle command to enter bundle-vc configuration mode.
When you create a VC class for a VC bundle member, you can use the following commands to define your parameters: bump, precedence, protect, ubr, ubr+, and vbr-nrt.
You cannot use the following commands in vc-class configuration mode to configure a VC bundle member: broadcast, encapsulation, inarp, and protocol. These commands are usable only at the bundle level, not the bundle member level.
Parameters applied to an individual VC supersede bundle-level parameters. Parameters that are directly configured for a VC through discrete commands entered in bundle-vc configuration mode supersede VC class parameters assigned to a VC bundle member by the class-vc command.
Examples
In the following example, a class named classA is created and then applied to an ATM PVC:
! The following commands create the class classA:vc-class atm classAubr 10000encapsulation aal5mux ip! The following commands apply classA to an ATM PVC:interface atm 2/0pvc router5 1/32class-vc classAIn the following example, a class named classA is created and then applied to a bundle member named vcmember, which is a member of bundle bundle1:
! The following commands create the class classA:vc-class atm classAprecedence 6-5no bump trafficprotect groupbump explicitly 7vbr-nrt 20000 10000 32! The following commands create bundle1, add vcmember to bundle1, and then applies classA! to vcmember:bundle bundle1pvc-bundle vcmemberclass-vc classAIn the preceding example, because of hierarchy precedence rules, the VC bundle member named vcmember has the following characteristics:
•
•
•
•
Related Commands
clear atm arp
To clear Address Resolution Protocol (ARP) entries for an ATM interface that is configured as an ARP server, use the clear atm arp command in privileged EXEC mode.
clear atm arp atm-interface {ip-address | *}
Syntax Description
atm-interface
ATM interface number (for example, 3/0).
ip-address
Clears the ARP entry for the specified IP address.
*
Clears all ARP entries on the interface.
Command Default
None
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use this command to clear ARP entries for an ATM interface. Specify the IP address of a particular entry to be deleted, or use the asterisk (*) to delete all the ARP entries for the interface.
If an ARP entry for an existing virtual circuit (VC) is deleted, the ARP server will immediately try to get another entry for that VC.
Examples
The following example shows how to delete the ARP entry for 172.20.173.28:
Router# clear atm arp 3/0 172.20.173.28clear atm vc
To release a specified switched virtual circuit (SVC), use the clear atm vc command in privileged EXEC mode.
clear atm vc vcd
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
For multicast or control virtual channel connections (VCCs), this command causes the LAN emulation (LANE) client to exit and rejoin an emulated LAN.
For data VCCs, this command also removes the associated LAN Emulation Address Resolution Protocol (LE ARP) table entries.
Examples
The following example shows how to release SVC 1024:
Router# clear atm vc 1024clear lane le-arp
To clear the dynamic LAN Emulation Address Resolution Protocol (LE ARP) table or a single LE ARP entry of the LANE client configured on the specified subinterface or emulated LAN, use the clear lane le-arp command in user EXEC or privileged EXEC mode.
Cisco 7500 Series
clear lane le-arp [interface slot/port [.subinterface-number] | name elan-name] [mac-address mac-address | route-desc segment segment-number bridge bridge-number]
Cisco 4500 and 4700 Routers
clear lane le-arp [interface number [.subinterface-number] | name elan-name] [mac-address mac-address | route-desc segment segment-number bridge bridge-number]
Syntax Description
Command Modes
User EXEC
Privileged EXECCommand History
Usage Guidelines
This command removes dynamic LE ARP table entries only. It does not remove static LE ARP table entries.
If you do not specify an interface or an emulated LAN, this command clears all the LE ARP tables of any LANE client in the router.
If you specify a major interface (not a subinterface), this command clears all the LE ARP tables of every LANE client on all the subinterfaces of that interface.
This command also removes the fast-cache entries built from the LE ARP entries.
Examples
The following example shows how to clear all the LE ARP tables for all clients on the router:
Router# clear lane le-arpThe following example shows how to clear all the LE ARP tables for all LANE clients on all the subinterfaces of interface 1/0:
Router# clear lane le-arp interface 1/0The following example shows how to clear the entry corresponding to MAC address 0800.aa00.0101 from the LE ARP table for the LANE client on the emulated LAN named red:
Router# clear lane le-arp name red 0800.aa00.0101The following example shows how to clear all dynamic entries from the LE ARP table for the LANE client on the emulated LAN named red:
Router# clear lane le-arp name redThe following example shows how to clear the dynamic entry from the LE ARP table for the LANE client on segment number 1, bridge number 1 in the emulated LAN named red:
Router# clear lane le-arp name red route-desc segment 1 bridge 1
Note
clear lane server
To force a LAN emulation (LANE) server to drop a client and allow the LANE configuration server to assign the client to another emulated LAN (ELAN), use the clear lane server command in user EXEC or privileged EXEC mode.
Cisco 7500 Series
clear lane server {interface slot/port [.subinterface-number] | name elan-name} [mac-address mac-address | client-atm-address atm-address | lecid lane-client-id | route-desc segment segment-number bridge bridge-number]
Cisco 4500 and 4700 Routers
clear lane server {interface number [.subinterface-number] | name elan-name} [mac-address mac-address | client-atm-address atm-address | lecid lecid | route-desc segment segment-number bridge bridge-number]
Syntax Description
Command Modes
User EXEC
Privileged EXECCommand History
Usage Guidelines
After changing the bindings on the configuration server, use this command on the LANE server to force the client to leave one emulated LAN. The LANE server will drop the Control Direct and Control Distribute virtual channel connections (VCCs) to the LANE client. The client will then ask the LANE configuration server for the location of the LANE server of the emulated LAN it should join.
If no LANE client is specified, all LANE clients attached to the LANE server are dropped.
Examples
The following example shows how to force all the LANE clients on the emulated LAN named red to be dropped. The next time they try to join, they will be forced to join a different emulated LAN.
Router# clear lane server name redRelated Commands
clear mpoa client cache
To clear the ingress and egress cache entries of one or all Multiprotocol over ATM (MPOA) clients (MPCs), use the clear mpoa client cache command in user EXEC or privileged EXEC mode.
clear mpoa client [name mpc-name] cache [ingress | egress] [ip-address ip-address]
Syntax Description
Defaults
The system defaults are:
•
•
•
Command Modes
User EXEC
Privileged EXECCommand History
Examples
The following example shows how to clear the ingress and egress cache entries for the MPC named ip_mpc:
Router# clear mpoa client name ip_mpc cacheRelated Commands
show mpoa client cache
Displays the ingress or egress cache entries matching the IP addresses for the MPCs.
clear mpoa server cache
To clear the ingress and egress cache entries, use the clear mpoa server cache command in user EXEC or privileged EXEC mode.
clear mpoa server [name mps-name] cache [ingress | egress] [ip-address ip-address]
Syntax Description
Command Modes
User EXEC
Privileged EXECCommand History
Examples
The following example shows how to clear all cache entries:
Router# clear mpoa server cacheRelated Commands
show mpoa server cache
Displays ingress and egress cache entries associated with the MPS.
clear pppatm interface atm
To clear PPP ATM sessions on an ATM interface, use the clear pppatm interface atm command in privileged EXEC mode.
clear pppatm interface atm interface-number[.subinterface-number] [vc {[vpi/]vci | virtual-circuit-name}]
Syntax Description
Command Modes
Privileged EXEC
Command History
12.2(13)T
This command was introduced.
12.2(28)SB
This command was integrated into Cisco IOS Release 12.2(28)SB.
Usage Guidelines
This command clears the PPP over ATM (PPPoA) sessions in an interface, or in a VC when the VC is specified.
When the clear pppatm interface atm command is used to clear sessions on an interface, PPP keepalives continue to work and can be used to detect a broken link.
Examples
The following example clears a PPP ATM session on ATM interface 1/0.10:
Router# clear pppatm interface atm 1/0.10Related Commands
debug pppatm
Enables reports for PPPoA events, errors, and states either globally or conditionally on an interface or VC.
show pppatm summary
Displays PPPoA session counts.
client-atm-address name
To add a LAN emulation (LANE) client address entry to the configuration server's configuration database, use the client-atm-address name command in database configuration mode. To remove a client address entry from the table, use the no form of this command.
client-atm-address atm-address-template name elan-name
no client-atm-address atm-address-template
Syntax Description
Command Default
No address and no emulated LAN name are provided.
Command Modes
Database configuration
Command History
Usage Guidelines
The effect of this command is to bind any client whose address matches the specified template into the specified emulated LAN. When a client comes up, it consults the LANE configuration server, which responds with the ATM address of the LANE server for the emulated LAN. The client then initiates join procedures with the LANE server.
Before this command is used, the emulated LAN specified by the elan-name argument must have been created in the configuration server's database by use of the name server-atm-address command.
If an existing entry in the configuration server's database binds the LANE client ATM address to a different emulated LAN, the new command is rejected.
This command affects only the bindings in the named configuration server database. It has no effect on the LANE components themselves.
See the lane database command for information about creating the database, and the name server-atm-address command for information about binding the emulated LAN's name to the server's ATM address.
The client-atm-address name command is a subcommand of the global lane database command.
ATM Addresses
A LANE ATM address has the same syntax as a network service access point (NSAP), but it is not a network-level address. It consists of the following:
•
–
•
•
Address Templates
LANE ATM address templates can use two types of wildcards: an asterisk (*) to match any single character (nibble), and an ellipsis (...) to match any number of leading, middle, or trailing characters. The values of the characters replaced by wildcards come from the automatically assigned ATM address.
In LANE, a prefix template explicitly matches the prefix but uses wildcards for the ESI and selector fields. An ESI template explicitly matches the ESI field but uses wildcards for the prefix and selector.
In our implementation of LANE, the prefix corresponds to the switch, the ESI corresponds to the ATM interface, and the selector field corresponds to the specific subinterface of the interface.
Examples
The following example shows how to use an ESI template to specify the part of the ATM address corresponding to the interface. This example allows any client on any subinterface of the interface that corresponds to the displayed ESI value, no matter to which switch the router is connected, to join the emulated LAN named engineering:
ATM(lane-config-database)# client-atm-address ...0800.200C.1001.** name engineeringThe following example shows how to use a prefix template to specify the part of the ATM address corresponding to the switch. This example allows any client on a subinterface of any interface connected to the switch that corresponds to the displayed prefix to join the emulated LAN named marketing:
ATM(lane-config-database)# client-atm-address 47.000014155551212f.00.00... name marketingRelated Commands
create on-demand
To configure ATM PVC autoprovisioning, which enables a permanent virtual circuit (PVC) or range of PVCs to be created automatically on demand, use the create on-demand command in ATM PVC range configuration mode, Interface-ATM-VC configuration mode, PVC-in-range configuration mode or VC-class configuration mode. To disable the ATM PVC autoprovisioning configuration, use the no form of this command.
create on-demand [type]
no create on-demand [type]
Syntax Description
Command Default
PVCs or range of PVCs cannot be created automatically.
Command Modes
ATM PVC range configuration (config-if-atm-range)
Interface-ATM-VC configuration (config-if-atm-range-pvc)
PVC-in-range (config-if-atm-range-pvc)
VC-class configuration (config-vc-class)Command History
Usage Guidelines
Use the create on-demand command to configure ATM PVC autoprovisioning, which enables a PVC or range of PVCs to be created automatically on demand. A VC will not be created until there is an activity on that virtual path identifier (VPI)/virtual channel identifier (VCI) pair. When you use the shutdown or no shutdown on an ATM interface, all create on-demand VCs on that interface will remain in INACTIVE state until the first incoming packet triggers the VC creation. During router reload, the create-on-demand VCs will not be established until there is incoming traffic.
You can erase, modify and restore the configuration. To erase the configuration, enter the no create on-demand aaa command.
To erase an individual PVC configuration within a range, use the no create on-demand aaa command in PVC-in-range mode on the VC.
To erase the entire RADIUS configuration from the router, use the erase command.
To modify VC attributes from the command, you must erase the configuration and disable the create-on-demand VCs by using no create on-demand aaa.
To restore configuration from RADIUS, you can use the create command.
To provision VC Class attributes from RADIUS server, you must enable the create on-demand aaa in the VC class. The RADIUS user-name attribute for each VC Class is uniquely defined as hostname {ip address / vc-class-name}.
You can configure the password by using radius-server command. You can use the create command to manually download the configuration.
After receiving RADIUS response to a VC provisioning request, if the VC-class name is specified in the response, the VC-class will be searched for locally on the router. If the VC-class is configured as create-on-demand and not yet provisioned, VC-class RADIUS request will be sent.
Examples
The following example shows how to configure VPI/VCI from 0/50 to 0/60 via RADIUS, on subinterface ATM 5/0.1:
Router> enableRouter# configure terminalRouter(config)# interface atm 5/0.1 multipointRouter(config-subif) range auto pvc 0/50 0/60Router(config-if-atm-range)# create on-demand aaaThe following example shows how to configure ATM PVC autoprovisioning on VC class:
Router> enableRouter# configure terminalRouter(config)# interface atm 5/0 multipointRouter(config)# vc-class atm vctestRouter(config-vc-class)# create on-demandRelated Commands
