Table Of Contents
Map a Protocol Address to a PVC
Configure Communication with the ILMI
Configure ATM UNI Version Override
Configure Generation of End-to-End F5 OAM Loopback Cells to Verify Connectivity
Configure the PVC that Performs SVC Call Setup
Configure the Idle Timeout Interval
Configure Point-to-Multipoint Signaling
Configure IP Multicast over ATM Point-to-Multipoint Virtual Circuits
Configure Generation of End-to-End F5 OAM Loopback Cells to Verify Connectivity
PVC with AAL5 and LLC/SNAP Encapsulation Examples
PVCs in a Fully Meshed Network Example
Configure Communication with the ILMI Example
Configure Generation of End-to-End F5 OAM Loopback Cells Example
SVCs in a Fully Meshed Network Example
SVCs with Multipoint Signaling Example
VC Class Configuration Examples
New VC Configuration
Functional Description
The New VC Configuration subfeature allows you to configure ATM PVCs, SVCs, static maps, and associated virtual circuit (VC) parameters using new ATM commands in new ATM VC command modes. The new configuration approach allows you to configure ATM parameters more easily and with fewer errors.
Backwards Compatibility
This subfeature is not intended to change the underlying functionality of the Cisco IOS ATM software. Only the method of creating ATM PVCs, SVCs, static maps, and associated VC parameters is changed.
The configuration commands used prior to this release are still available. However, you are encouraged to use the new command syntax introduced in this subfeature for easier configuration and access to improved functionality.
Configuration Tasks
This section describes how to configure ATM PVCs and SVCs using the new commands and command modes introduced in this document:
Refer to the "" chapter for command reference and debug command documentation.
Configure PVCs
To use a permanent virtual circuit (PVC), you must configure the PVC on both the router and the ATM switch. PVCs remain active until the circuit is removed from either configuration.
All virtual circuit characteristics listed in the sections "AIP Virtual Circuits," "ATM Port Adapter Virtual Circuits," and "NPM Virtual Circuits" in the "Wide-Area Networking Overview" chapter of Cisco IOS Release 11.3 Wide-Area Networking Configuration Guide apply to these PVCs. When a PVC is configured, all the configuration options are passed on to the AIP, ATM port adapter, or NPM, respectively. These PVCs are writable into the nonvolatile RAM (NVRAM) as part of the Route Processor (RP) configuration and are used when the RP image is reloaded.
Some ATM switches might have point-to-multipoint PVCs that do the equivalent of broadcasting. If a point-to-multipoint PVC exists, then that PVC can be used as the sole broadcast PVC for all multicast requests.
To configure a PVC, perform the tasks in the following sections. The first two tasks are required; the other tasks are optional:
•
Map a Protocol Address to a PVC
•
•
•
•
•
•
•
Create a PVC
To create a PVC and enter interface-ATM-VC configuration mode, perform the following task in interface configuration mode:
Note
Once you specify a name for a PVC, you can re-enter the interface-ATM-VC configuration mode by simply entering pvc name.
For a list of AAL types and encapsulations supported for the aal-encap argument, refer to the encapsulation command in the "Enhanced ATM VC Configuration and Management Commands" chapter of this feature set. The global default is AAL5 with SNAP encapsulation.
See examples of PVC configurations in the section "PVC Configuration Examples" at the end of this chapter.
Map a Protocol Address to a PVC
The ATM interface supports a static mapping scheme that identifies the network address of remote hosts or routers. This section describes how to map a PVC to an address, which is a required task for configuring a PVC.
To map a protocol address to a PVC, perform the following task in interface-ATM-VC configuration mode:
Note
See examples of PVC configurations in the section "PVC Configuration Examples" at the end of this chapter.
Configure Communication with the ILMI
You can configure a PVC for communication with the Interim Local Management Interface (ILMI) so the router can receive SNMP traps and new network prefixes. The recommended vpi and vci values for the ILMI PVC are 0 and 16, respectively. To configure ILMI communication, complete the following task in interface-ATM-VC configuration mode:
Note
Enable Inverse ARP
To enable Inverse ARP on a PVC, perform the following task in interface-ATM-VC configuration mode:
Enable Inverse ARP on a PVC.
protocol protocol inarp [[no] broadcast]
(Optional) Adjust the Inverse ARP time period.
inarp minutes
Note
Configure ATM UNI Version Override
Depending on the router platform configuration you are using, refer to the section "Configure ATM UNI Version Override" in one of the following chapters in the Cisco IOS Release 11.3 Wide-Area Networking Configuration Guide:
•
•
•
Configure Generation of End-to-End F5 OAM Loopback Cells to Verify Connectivity
You can optionally configure the PVC to generate end-to-end F5 OAM loopback cells to verify connectivity on the virtual circuit. The remote end must respond by echoing back such cells. If OAM response cells are missed (indicating the lack of connectivity), the PVC state goes down. If all the PVCs on a subinterface go down, the subinterface goes down. For more information, refer to the "VC Integrity Management" chapter in the Enhanced ATM VC Configuration and Management feature set in Cisco IOS Release 11.3(2)T.
To configure transmission of end-to-end F5 OAM cells on a PVC, perform the following tasks in interface-ATM-VC configuration mode:
Use the up-count argument to specify the number of consecutive end-to-end F5 OAM loopback cell responses that must be received in order to change a PVC connection state to up. Use the down-count argument to specify the number of consecutive end-to-end F5 OAM loopback cell responses that are not received in order to tear down a PVC. Use the retry-frequency argument to specify the frequency (in seconds) that end-to-end F5 OAM loopback cells should be transmitted when a change in UP/DOWN state is being verified. For example, if a PVC is up and a loopback cell response is not received after the frequency (in seconds) specified using the oam-pvc command, then loopback cells are sent at the retry-frequency to verify whether or not the PVC is down.
Configure Broadcast on a PVC
To send duplicate broadcast packets for all protocols configured on a PVC, perform the following task in interface-ATM-VC configuration mode:
Note
Assign a VC Class to a PVC
By creating a VC class, you can preconfigure a set of default parameters that you may apply to a PVC. To create a VC class, refer to the section "Configure VC Classes" later in this document.
Once you have created a VC class, perform the following task in interface-ATM-VC configuration mode to apply the VC class to a PVC:
The vc-class-name is the same as the name you specified when you created a VC class using the vc-class atm command. Refer to the section "Configure VC Classes" later in this document for a description of how to create a VC class.
Monitor and Maintain ATM PVCs
After configuring an ATM PVC, you can display its status. To show current PVC settings and statistics, perform the following tasks in privileged EXEC mode:
Configure SVCs
ATM switched virtual circuit (SVC) service operates much like X.25 SVC service, although ATM allows much higher throughput. Virtual circuits are created and released dynamically, providing user bandwidth on demand. This service requires a signaling protocol between the router and the switch.
The ATM signaling software provides a method of dynamically establishing, maintaining, and clearing ATM connections at the User-Network Interface (UNI). The ATM signaling software conforms to ATM Forum UNI 3.0 or ATM Forum UNI 3.1 depending on what version is selected by ILMI or configuration.
In UNI mode, the user is the router and the network is an ATM switch. This is an important distinction. The Cisco router does not perform ATM-level call routing. Instead, the ATM switch does the ATM call routing, and the router routes packets through the resulting circuit. The router is viewed as the user and the LAN interconnection device at the end of the circuit, and the ATM switch is viewed as the network.
illustrates the router position in a basic ATM environment. The router is used primarily to interconnect LANs over an ATM network. The workstation connected directly to the destination ATM switch illustrates that you can connect not only routers to ATM switches, but also any computer with an ATM interface that conforms to the ATM Forum UNI specification.
Figure 1 Basic ATM Environment
You must complete the tasks in the following sections to use SVCs:
•
The tasks in the following sections are optional SVC tasks for customizing your network. These tasks are considered advanced; the default values are almost always adequate. You should not have to perform these tasks unless you need to customize your particular SVC connection.
•
•
•
•
•
•
•
•
Configure the PVC that Performs SVC Call Setup
Unlike X.25 service, which uses in-band signaling (connection establishment done on the same circuit as data transfer), ATM uses out-of-band signaling. One dedicated PVC exists between the router and the ATM switch, over which all SVC call establishment and call termination requests flow. After the call is established, data transfer occurs over the SVC, from router to router. The signaling that accomplishes the call setup and teardown is called Layer 3 signaling or the Q.2931 protocol.
For out-of-band signaling, a signaling PVC must be configured before any SVCs can be set up. illustrates that a signaling PVC from the source router to the ATM switch is used to set up two SVCs. This is a fully meshed network; workstations A, B, and C all can communicate with each other.
Figure 2
One or More SVCs Require a Signaling PVC
To configure the signaling PVC for all SVC connections, perform the following task in interface configuration mode:
Configure the signaling PVC for an ATM main interface that uses SVCs.
pvc [name] vpi/vci qsaal
Note
The VPI and VCI values must be configured consistently with the local switch. The standard values for VPI and VCI are 0 and 5, respectively.
Configure the NSAP Address
This section describes how to configure the source NSAP address of the SVC connection. Depending on the router platform configuration you are using, refer to "Configure the NSAP Address" in one of the following chapters in the Cisco IOS Release 11.3 Wide-Area Networking Configuration Guide:
•
•
•
Create an SVC
To create an SVC, perform the following tasks starting in interface configuration mode:
Once you specify a name for an SVC, you can re-enter the interface-ATM-VC configuration mode by simply entering svc name; You can remove an SVC configuration by entering no svc name.
For a list of AAL types and encapsulations supported for the aal-encap argument, refer to the encapsulation command in the command reference section of this document. The default is AAL5 with SNAP encapsulation.
Configure the Idle Timeout Interval
You can specify an interval of inactivity after which any idle SVC on an interface is torn down. This timeout interval might help control costs and free router memory and other resources for other uses.
To change the idle timeout interval, perform the following tasks in interface-ATM-VC configuration mode:
Configure the interval of inactivity after which an idle SVC will be torn down.
idle-timeout seconds [minimum-rate]
In addition to configuring the interval of inactivity, you can optionally specify the minimum-rate in kilobits per second (Kbps). This is the minimum traffic rate required on an ATM SVC to maintain the connection.
Configure Point-to-Multipoint Signaling
Point-to-multipoint signaling (or multicasting) allows the router to send one packet to the ATM switch and have the switch replicate the packet to the destinations. It replaces pseudobroadcasting on specified virtual circuits for protocols configured for broadcasting.
You configure multipoint signaling on an ATM interface after you have mapped protocol addresses to NSAPs and configured one or more protocols for broadcasting.
After multipoint signaling is set, the router uses existing static map entries that have the broadcast keyword set to establish multipoint calls. The call is established to the first destination with a Setup message. Additional parties are added to the call with AddParty messages each time a multicast packet is sent. One multipoint call will be established for each logical subnet of each protocol that has the broadcast keyword set.
To configure multipoint signaling on an ATM interface, complete the following tasks starting in global configuration mode:
If multipoint virtual circuits are closed, they are reopened with the next multicast packet. Once the call is established, additional parties are added to the call when additional multicast packets are sent. If a destination never comes up, the router constantly attempts to add it to the call by means of multipoint signaling.
For an example of configuring multipoint signaling on an interface that is configured for SVCs, see the "SVCs with Multipoint Signaling Example" later in this chapter.
Configure IP Multicast over ATM Point-to-Multipoint Virtual Circuits
This task is documented in the "Configuring IP Multicast Routing" chapter of the Cisco IOS Release 11.3 Network Protocols Configuration Guide, Part 1.
Configure SSCOP
Depending on the router platform configuration you are using, refer to the section "Configure SSCOP" in one of the following chapters in the Cisco IOS Release 11.3 Wide-Area Networking Configuration Guide:
•
•
•
Configure Generation of End-to-End F5 OAM Loopback Cells to Verify Connectivity
You can optionally configure the SVC to generate end-to-end F5 OAM loopback cells to verify connectivity on the virtual circuit. The remote end must respond by echoing back such cells. If OAM response cells are missed (indicating the lack of connectivity), the SVC is torn down. For more information, refer to the "VC Integrity Management" chapter in the Enhanced ATM VC Configuration and Management feature set in Cisco IOS Release 11.3(2)T.
To configure transmission of end-to-end F5 OAM loopback cells on an SVC, perform the following tasks in interface-ATM-VC configuration mode:
The up-count argument does not apply to SVCs, but it must be specified in order to configure the down-count and retry-frequency. Use the down-count argument to specify the number of consecutive end-to-end F5 OAM loopback cell responses that are not received in order to tear down an SVC. Use the retry-frequency argument to specify the frequency (in seconds) that end-to-end F5 OAM loopback cells should be transmitted when a change in UP/DOWN state is being verified. For example, if an SVC is up and a loopback cell response is not received after the frequency (in seconds) specified using the oam-svc command, then loopback cells are sent at the retry-frequency to verify whether or not the SVC is down.
Note
Configure Broadcast on an SVC
To send duplicate broadcast packets or send a single broadcast packet using multipoint signaling for all protocols configured on an SVC, perform the following task in interface-ATM-VC configuration mode:
Note
Assign a VC Class to an SVC
By creating a VC class, you can preconfigure a set of default parameters that you may apply to an SVC. To create a VC class, refer to the section "Configure VC Classes" later in this document.
Once you have created a VC class, perform the following task in interface-ATM-VC configuration mode to apply the VC class to an SVC:
The vc-class-name is the same as the name you specified when you created a VC class using the vc-class atm command. Refer to the section "Configure VC Classes" later in this document for a description of how to create a VC class.
Monitor and Maintain ATM SVCs
After configuring an ATM SVC, you can display its status. To show current SVC settings and statistics, perform the following tasks in privileged EXEC mode:
Configure VC Classes
A VC class is a set of preconfigured VC parameters that you configure and apply to a particular VC or ATM interface. You may apply a VC class to an ATM main interface, subinterface, PVC or SVC. For example, you can create a VC class that contains VC parameter configurations that you will apply to a particular PVC or SVC. You might create another VC class that contains VC parameter configurations that you will apply to all VCs configured on a particular ATM main interface or subinterface. Refer to "VC Class Configuration Examples" section later in this document for examples of VC class configurations.
To create and use a VC class, complete the following tasks:
Create a VC Class
To create a VC class, perform the following task in global configuration mode:
Configure VC Parameters
After you create a VC class and enter vc-class configuration mode, configure VC parameters using one or more of the following commands:
•
•
•
•
•
•
•
•
•
•
•
•
Refer to the sections "Configure PVCs" and "Configure SVCs" for descriptions on how to configure these commands for PVCs and SVCs.
If an SVC command (for example, idle-timeout or oam-svc) is configured in a VC class, but the VC class is applied on a PVC, the SVC command is ignored. This is also true if a PVC command is applied to an SVC.
Apply a VC Class
Once you have created and configured a VC class, you can apply it directly on an ATM PVC or SVC, or you can apply it on an ATM interface or subinterface.
To apply a VC class directly on an ATM PVC or SVC, perform the following tasks starting in interface configuration mode:
Step 1
–
–
pvc [name] vpi/vci
svc [name] nsap address
Step 2
class vc-class-name
To apply a VC class on an ATM main interface or subinterface, perform the following tasks starting in global configuration mode:
Configuration Examples
The following sections give examples for configuring ATM PVCs, SVCs, and VC classes:
•
PVC Configuration Examples
This section contains the following PVC configuration examples:
•
•
•
•
Create a PVC Example
The following example creates a PVC on an ATM main interface. AAL5/MUX encapsulation is configured and a VBR-NRT QOS is specified. For further information, refer to the related task section "Create a PVC" presented earlier in this chapter.
interface 2/0pvc cisco 1/20encapsulation aal5mux ipvbr-nrt 100000 50000 20exitPVC with AAL5 and LLC/SNAP Encapsulation Examples
The following example creates PVC 0/10 on ATM interface 3/0. It uses the global default LLC/SNAP encapsulation over AAL5. The interface is at IP address 1.1.1.1 with 1.1.1.5 at the other end of the connection. For further information, refer to the related task sections "Create a PVC" and "Map a Protocol Address to a PVC" presented earlier in this chapter.
interface atm 3/0ip address 1.1.1.1 255.255.255.0pvc 0/10protocol ip 1.1.1.5 broadcastexit!ip route-cache cbusThe following example is of a typical ATM configuration for a PVC:
interface atm 4/0ip address 172.21.168.112 255.255.255.0atm maxvc 512pvc 1/1protocol ip 171.21.168.110exit!pvc 2/2protocol decnet 10.1 broadcastexit!pvc 6/6protocol clns 47.004.001.0000.0c00.6e26.00 broadcastexit!decnet cost 1clns router iso-igrp cometexit!router iso-igrp cometnet 47.0004.0001.0000.0c00.6666.00exit!router igrp 109network 172.21.0.0exit!ip domain-name CISCO.COMPVCs in a Fully Meshed Network Example
illustrates a fully meshed network. The configurations for Routers A, B, and C follow the figure. In this example, the routers are configured to use PVCs. Fully meshed indicates that any workstation can communicate with any other workstation. Note that the two protocol statements configured in Router A identify the ATM addresses of Routers B and C. The two protocol statements in Router B identify the ATM addresses of Routers A and C. The two protocol statements in Router C identify the ATM addresses of Routers A and B. For further information, refer to the related task sections "Create a PVC" and "Map a Protocol Address to a PVC" presented earlier in this chapter.
Figure 3 Fully Meshed ATM Configuration Example
Router A
ip routing!interface atm 4/0ip address 131.108.168.1 255.255.255.0pvc 0/10protocol ip 131.108.168.2 broadcastexit!pvc 0/20protocol ip 131.108.168.3 broadcastexitRouter B
ip routing!interface atm 2/0ip address 131.108.168.2 255.255.255.0pvc test-b-1 0/10protocol ip 131.108.168.1 broadcastexit!pvc test-b-2 0/30protocol ip 131.108.168.3 broadcastexitRouter C
ip routing!interface atm 4/0ip address 131.108.168.3 255.255.255.0pvc 0/20encapsulation aal5snapprotocol ip 131.108.168.1 broadcastexit!pvc 0/30encapsulation aal5snapprotocol ip 131.108.168.2 broadcastexitDynamic Rate Queue Examples
Both of the following examples assume that no permanent rate queues have been configured. The software dynamically creates rate queues when a pvc command creates a new PVC that does not match any user-configured rate queue. For further information, refer to the related task section "Create a PVC" presented earlier in this chapter.
In the following example, the software sets the peak rate to the maximum that the PLIM will allow and sets the average rate to the peak rate. Then it creates a rate queue for the peak rate of this VC.
interface 2/0pvc 1/1exitIn the following example, the software creates a 100-Mbps rate queue with an average rate of 50-Mbps and a burst size of 64 cells:
interface 2/0pvc 2/2vbr-nrt 100000 50000 64exitIn the following example, the software creates a 15-Mbps rate queue and sets the average rate to the peak rate:
interface 2/0pvc 3/3ubr 15000exitConfigure Communication with the ILMI Example
The following example configures the ILMI protocol on an ATM main interface. For further information, refer to the related task section "Configure Communication with the ILMI" presented earlier in this chapter.
interface 2/0pvc cisco 0/16 ilmiexitEnable Inverse ARP Example
The following example enables Inverse ARP on an ATM interface and specifies an Inverse ARP time period of 10 minutes. For further information, refer to the related task section "Enable Inverse ARP" presented earlier in this chapter.
interface 2/0pvc 1/20protocol ip inarp no broadcastinarp 10exitConfigure Generation of End-to-End F5 OAM Loopback Cells Example
The following example enables OAM management on an ATM PVC. The PVC is assigned the name routerA and the VPI and VCI are 0 and 32, respectively. OAM management is enabled with a frequency of 3 seconds between OAM cell transmissions. For further information, refer to the related task section "Configure Generation of End-to-End F5 OAM Loopback Cells to Verify Connectivity" presented in this document. For further information, refer to the related task section "Configure Generation of End-to-End F5 OAM Loopback Cells to Verify Connectivity" presented earlier in this chapter.
interface atm 2/0pvc routerA 0/32oam-pvc manage 3oam retry 5 5 10SVC Configuration Examples
This section contains the following SVC configuration examples:
•
•
SVCs in a Fully Meshed Network Example
The following example is also a configuration for the fully meshed network shown in , but this example uses SVCs. PVC 0/5 is the signaling PVC. For further information, refer to the following related task sections presented earlier in this chapter:
•
Router A
interface atm 4/0ip address 131.108.168.1 255.255.255.0atm nsap-address AB.CDEF.01.234567.890A.BCDE.F012.3456.7890.1234.12atm maxvc 1024pvc 0/5 qsaalexit!svc svc-1 nsap BC.CDEF.01.234567.890A.BCDE.F012.3456.7890.1334.13protocol ip 131.108.168.2exit!svc svc-2 nsap BC.CDEF.01.234567.890A.BCDE.F012.3456.7890.1334.12protocol ip 131.108.168.3exitRouter B
interface atm 2/0ip address 131.108.168.2 255.255.255.0atm nsap-address BC.CDEF.01.234567.890A.BCDE.F012.3456.7890.1334.13atm maxvc 1024pvc 0/5 qsaalexit!svc svc-1 nsap AB.CDEF.01.234567.890A.BCDE.F012.3456.7890.1234.12protocol ip 131.108.168.1exit!svc svc-2 nsap BC.CDEF.01.234567.890A.BCDE.F012.3456.7890.1334.12protocol ip 131.108.168.3exitRouter C
interface atm 4/0ip address 131.108.168.3 255.255.255.0atm nsap-address BC.CDEF.01.234567.890A.BCDE.F012.3456.7890.1334.12atm maxvc 1024pvc 0/5 qsaalexit!svc nsap AB.CDEF.01.234567.890A.BCDE.F012.3456.7890.1234.12protocol ip 131.108.168.1exit!svc nsap BC.CDEF.01.234567.890A.BCDE.F012.3456.7890.1334.13protocol ip 131.108.168.2exitSVCs with Multipoint Signaling Example
The following example configures an ATM interface for SVCs using multipoint signaling. For further information, refer to the related task section "Configure Point-to-Multipoint Signaling" presented earlier in this chapter.
interface atm 2/0ip address 4.4.4.6 255.255.255.0atm nsap-address de.cdef.01.234567.890a.bcde.f012.3456.7890.1234.12atm multipoint-signallingatm maxvc 1024pvc 0/5 qsaalexit!svc mcast-1 nsap cd.cdef.01.234566.890a.bcde.f012.3456.7890.1234.12 broadcastprotocol ip 4.4.4.4 broadcastexit!svc mcast-2 nsap 31.3233.34.352637.3839.3031.3233.3435.3637.3839.30 broadcastprotocol ip 4.4.4.7 broadcastexitTraffic Parameters Example
The following example maps specified SVCs to protocol addresses of remote hosts. Then it sets traffic parameters for certain protocol traffic. For further information, refer to the related task section "Create an SVC" presented earlier in this chapter.
interface atm 4/0svc svc-1 nsap 47.0091.81.000000.0041.0B0A.1581.0040.0B0A.1585.00vbr-nrt 8000 4000 64 10000 5000 64exit!interface atm 2/0svc svc-1 nsap 47.0091.81.000000.0041.0B0A.1581.0040.0B0B.1585.00ubr 10000 5000exit!interface atm 3/0svc svc-1 nsap 47.0091.81.000000.0041.0B0A.1581.0040.0B0C.1585.00ubr+ 8000 4000 10000 3000exitVC Class Configuration Examples
This section contains the following VC class configuration examples:
Create a VC Class Examples
The following example creates a VC class named main and configures UBR and encapsulation parameters. For further information, refer to the related task sections "Create a VC Class" and "Configure VC Parameters" presented earlier in this chapter.
vc-class atm mainubr 10000encapsulation aal5mux ipThe following example creates a VC class named sub and configures UBR and PVC management parameters. For further information, refer to the related task sections "Create a VC Class" and "Configure VC Parameters" presented earlier in this chapter.
vc-class atm sububr 15000oam-pvc manage 3The following example creates a VC class named pvc and configures VBR-NRT and encapsulation parameters. For further information, refer to the related task sections "Create a VC Class" and "Configure VC Parameters" presented earlier in this chapter.
vc-class atm pvcvbr-nrt 10000 5000 64encapsulation aal5snapApply a VC Class Examples
The following example applies the VC class named main to the ATM main interface 4/0:
interface atm 4/0class mainexitThe following example applies the VC class named sub to the ATM subinterface 4/0.5:
interface atm 4/0.5 multipointclass subexitThe following example applies the VC class named pvc directly on the PVC 0/56:
interface atm 4/0.5 multipointpvc 0/56class pvcexit
