Configuring ATM Network Interfaces

This chapter describes how to explicitly configure ATM network interface types. Explicitly configuring interfaces is the alternative to Integrated Local Management Interface (ILMI) autoconfiguration, which senses the peer interface type and appropriately configures the interface on the ATM switch.

The network configuration tasks described in this chapter are used to explicitly change your ATM switch operation from the defaults, which are suitable for most networks. The following sections are included:

Note For a complete description of the commands mentioned in this chapter, refer to the LightStream 1010 ATM Switch and Catalyst 8510 MSR Command Reference publication.

Example Network Configuration

The example network shown in Figure 7-1 illustrates some standard ATM interface configurations you might want to set up after completing the tasks in the chapter "Initially Configuring the ATM Switch."

Figure 7-1: Example Network Configuration

The network configuration shown in Figure 7-1 is an example of a corporate campus ATM backbone network connecting three buildings with an ATM connection across the WAN to a remote sales office.

The following sections provide examples of the hypothetical network configuration shown in Figure 7-1:

Disabling Autoconfiguration

Autoconfiguration determines an interface's type when the interface initially comes up. To change the configuration of the interface type (such as UNI, NNI, or IISP), side, or version, you must first disable autoconfiguration.

Note When you change the interface type, side, or version, ATM signalling and ILMI are restarted on the interface. When ATM signalling is restarted, all switched virtual connections (SVCs) across the interface are cleared; permanent virtual connections are not affected.

To disable autoconfiguration on an interface, perform the following steps, beginning in global configuration mode:

Step Command Task

1
interface atm card/subcard/port [.vpt #]

Select the interface to be configured.

2
no atm auto-configuration

Disable autoconfiguration on the interface.

Step	Command	Task
1	interface atm card/subcard/port [.vpt #]	Select the interface to be configured.
2	no atm auto-configuration	Disable autoconfiguration on the interface.

Example

The following example shows how to disable autoconfiguration on interface ATM 1/0/0:

Switch(config)# interface atm 1/0/0

Switch(config-if)# no atm auto-configuration

Switch(config-if)#
%ATM-6-ILMINOAUTOCFG: ILMI(ATM1/0/0): Auto-configuration is disabled, current interface 
parameters will be used at next interface restart.

Display the Autoconfiguration

To confirm that autoconfiguration is disabled for the interface, use the following EXEC command:

Command Task

show atm interface atm card/subcard/port

Show the ATM interface configuration.

Command	Task
show atm interface atm card/subcard/port	Show the ATM interface configuration.

Example

The following example shows the autoconfiguration status of ATM interface 1/0/0 as disabled:

Switch# show atm interface atm 1/0/0

Interface:      ATM1/0/0        Port-type:      oc3suni
IF Status:      UP              Admin Status:   up

  
Auto-config:    disabled        AutoCfgState:   not applicable
IF-Side:        Network         IF-type:        NNI
Uni-type:       not applicable  Uni-version:    not applicable
Max-VPI-bits:   8               Max-VCI-bits:   14
Max-VP:         255             Max-VC:         16383
ConfMaxSvpcVpi: 255             CurrMaxSvpcVpi: 255
ConfMaxSvccVpi: 255             CurrMaxSvccVpi: 255
ConfMinSvccVci: 35              CurrMinSvccVci: 35
Svc Upc Intent: pass            Signalling:     Enabled
ATM Address for Soft VC: 47.0091.8100.0000.00e0.4fac.b401.4000.0c80.8000.00
Configured virtual links:
  PVCLs SoftVCLs   SVCLs   TVCLs   PVPLs SoftVPLs   SVPLs Total-Cfgd Inst-Conns
      4        0       0       0       1        0       0          5          3
Logical ports(VP-tunnels): 0
Input cells:    263250          Output cells:   269783
5 minute input rate:             0 bits/sec,       0 cells/sec
5 minute output rate:            0 bits/sec,       0 cells/sec
Input AAL5 pkts: 171880, Output AAL5 pkts: 175134, AAL5 crc errors: 0

Configuring UNI Interfaces

The UNI specification defines communications between ATM end stations (such as workstations and routers) and ATM switches in private ATM networks.

Figure 7-2 shows a private UNI interface between the ATM switch (HB-1) in the Headquarters building to the Cisco 7000 (HB-1) in the same building.

Figure 7-2: Private UNI Example

To configure a UNI interface, perform the following steps, beginning in global configuration mode:

Step Command Task

1
interface atm card/subcard/port[.vpt#]

Select the interface to be configured.

2
no atm auto-configuration

Disable autoconfiguration on the interface.

3
atm uni [side {network | user}]
[type {private | public}]
[version {3.0 | 3.1 | 4.0}]

Configure the ATM UNI interface.

Step	Command	Task
1	interface atm card/subcard/port[.vpt#]	Select the interface to be configured.
2	no atm auto-configuration	Disable autoconfiguration on the interface.
3	atm uni [side {network \| user}] [type {private \| public}] [version {3.0 \| 3.1 \| 4.0}]	Configure the ATM UNI interface.

Example

The following example shows how to disable autoconfiguration on ATM interface 0/1/0 and configure the interface as the user side of a private UNI running version 4.0:

Switch(HB-1)(config)# interface atm 0/1/0

Switch(HB-1)(config-if)# no atm auto-configuration

Switch(HB-1)(config-if)#
%ATM-6-ILMINOAUTOCFG: ILMI(ATM0/1/0): Auto-configuration is disabled, current interface 
parameters will be used at next interface restart.
Switch(HB-1)(config-if)# atm uni side user type private version 4.0

Switch(HB-1)(config-if)#
%ATM-5-ATMSOFTSTART: Restarting ATM signalling and ILMI on ATM0/1/0.

Display the UNI Interface Configuration

To show the UNI configuration for an ATM interface, use the following EXEC command:

Command Task

show atm interface atm card/subcard/port[.vpt#]

Show the ATM interface configuration.

Command	Task
show atm interface atm card/subcard/port[.vpt#]	Show the ATM interface configuration.

Example

The following example shows the ATM interface 0/1/0 UNI configuration:

Switch(HB-1)# show atm interface atm 0/1/0

Interface:      ATM0/1/0        Port-type:      oc3suni
IF Status:      UP              Admin Status:   up
Auto-config:    disabled        AutoCfgState:   not applicable
IF-Side:        Network         IF-type:        UNI

  
Uni-type:       private                 Uni-version:    V4.0
<information deleted)

Configuring NNI Interfaces

The Network-to-Network Interface (NNI) specification defines communications between two ATM switches in a private ATM network.

Figure 7-3 shows a private NNI interface from the ATM switch (HB-1) in the Headquarters building to the ATM switch (EB-1) in the Engineering building.

Figure 7-3: Private NNI Example

You must configure NNI connections to allow for route discovery and topology analysis between the ATM switches. To configure the NNI interface, perform the following steps, beginning in global configuration mode:

Step Command Task

1
interface atm card/subcard/port[.vpt#]

Select the interface to be configured.

2
no atm auto-configuration

Disable autoconfiguration on the interface.

3
atm nni

Configure the ATM NNI interface.

Step	Command	Task
1	interface atm card/subcard/port[.vpt#]	Select the interface to be configured.
2	no atm auto-configuration	Disable autoconfiguration on the interface.
3	atm nni	Configure the ATM NNI interface.

Example

The following example shows how to configure ATM interface 3/0/0 as an NNI interface:

Switch(HB-1)(config)# interface atm 3/0/0

Switch(HB-1)(config-if)# no atm auto-configuration

Switch(HB-1)(config-if)# 
%ATM-6-ILMINOAUTOCFG: ILMI(ATM3/0/0): Auto-configuration is disabled, current interface 
parameters will be used at next interface restart.
Switch(HB-1)(config-if)# atm nni

Switch(HB-1)(config-if)# 
%ATM-5-ATMSOFTSTART: Restarting ATM signalling and ILMI on ATM3/0/0.

Display the NNI Interface Configuration

To show the NNI configuration for an ATM interface, use the following EXEC command:

Command Task

show atm interface atm card/subcard/port[.vpt#]

Show the ATM interface configuration.

Command	Task
show atm interface atm card/subcard/port[.vpt#]	Show the ATM interface configuration.

Example

The following example shows the configuration of the NNI interface ATM 3/0/0 on the ATM switch-1 (HB-1) located in the headquarters building:

Switch(HB-1)#  show atm interface atm 3/0/0

Interface:      ATM3/0/0        Port-type:    oc3suni
IF Status:      UP              Admin Status: up
Auto-config:    disabled        AutoCfgState: not applicable

  
IF-Side:        Network         IF-type:      NNI
Uni-type:       not applicable  Uni-version:  not applicable
<information deleted>0

Configuring IISP Interfaces

The Interim Interswitch Signalling Protocol (IISP) defines a static routing protocol for use between ATM switches. IISP provides support for switched virtual circuits (SVCs) on switches that do not support the Private Network-to-Network Interface (PNNI) protocol. For further information, see the chapter "Configuring ATM Routing and PNNI."

Figure 7-4 shows an IISP between the ATM switch (SB-1) in the Remote Sales building and the ATM switch (SB-1) in the same building.

Figure 7-4: IISP Network Segment Example

To configure an IISP interface, perform the following tasks, beginning in global configuration mode:

Step Command Task

1
interface atm card/subcard/port[.vpt#]

Select the interface to be configured.

2
no atm auto-configuration

Disable autoconfiguration on the interface.

3
atm iisp [side {network | user}]
[version {3.0 | 3.1 | 4.0}]

Configure the ATM IISP interface.

4
exit

Exit interface configuration mode.

5
atm route addr-prefix atm card/subcard/port[.sub_inter #]

Configure the ATM route address prefix.

Step	Command	Task
1	interface atm card/subcard/port[.vpt#]	Select the interface to be configured.
2	no atm auto-configuration	Disable autoconfiguration on the interface.
3	atm iisp [side {network \| user}] [version {3.0 \| 3.1 \| 4.0}]	Configure the ATM IISP interface.
4	exit	Exit interface configuration mode.
5	atm route addr-prefix atm card/subcard/port[.sub_inter #]	Configure the ATM route address prefix.

Example

The following example shows how to configure ATM interface 3/0/0 on the ATM switch (SB-1) as user side IISP and specifies an ATM route address prefix:

Switch(SB-1)(config)# interface atm 3/0/0

Switch(SB-1)(config-if)# no atm auto-configuration

Switch(SB-1)(config-if)# 
%ATM-6-ILMINOAUTOCFG: ILMI(ATM3/0/0): Auto-configuration is disabled, current interface 
parameters will be used at next interface restart.
Switch(SB-1)(config-if)# atm iisp side user

Switch(SB-1)(config-if)# 
%ATM-5-ATMSOFTSTART: Restarting ATM signalling and ILMI on ATM3/0/0.
Switch(SB-1)(config-if)# exit

Switch(SB-1)(config)# atm route 47.0091.8100.0000.0000.0ca7.ce01 atm 3/0/0

Display the IISP Configuration

To show the interface IISP configuration, use the following EXEC command:

Command Task

show atm interface atm card/subcard/port[.vpt#]

Show the interface configuration.

Command	Task
show atm interface atm card/subcard/port[.vpt#]	Show the interface configuration.

Example

The following example shows the configuration of ATM interface 3/0/0 on the ATM switch (SB-1):

Switch(SB-1)# show atm interface atm 3/0/0

Interface:      ATM3/0/0        Port-type:      oc3suni
IF Status:      UP              Admin Status:   up
Auto-config:    disabled        AutoCfgState:   not applicable

  
IF-Side:        User            IF-type:        IISP
Uni-type:       not applicable  Uni-version:    V3.0
Max-VPI-bits:   8               Max-VCI-bits:   14
Max-VP:         255             Max-VC:         16383
ConfMaxSvpcVpi: 255             CurrMaxSvpcVpi: 255
ConfMaxSvccVpi: 255             CurrMaxSvccVpi: 255
ConfMinSvccVci: 35              CurrMinSvccVci: 35
Svc Upc Intent: pass            Signalling:     Enabled
ATM Address for Soft VC: 47.0091.8100.0000.00e0.4fac.b401.4000.0c80.8000.00
Configured virtual links:
  PVCLs SoftVCLs   SVCLs   TVCLs   PVPLs SoftVPLs   SVPLs Total-Cfgd Inst-Conns
      3        0       0       0       0        0       0          3          2
Logical ports(VP-tunnels):     0
Input cells:    264089          Output cells:   273253
5 minute input rate:             0 bits/sec,       0 cells/sec
5 minute output rate:            0 bits/sec,       0 cells/sec
Input AAL5 pkts: 172421, Output AAL5 pkts: 176993, AAL5 crc errors: 0

Configuring VP Tunnels

Virtual path (VP) tunnels provide the ability to interconnect ATM switches across public networks using permanent VPs. You can configure a VP tunnel to carry a single service category, or you can configure a VP tunnel to carry multiple service categories, including merged VCs. The following sections describe the types of VP tunnels and their configuration:

Configuring a VP Tunnel for a Single Service Category

The type of VP tunnel described in this section is configured as a VP of a single service category. Only virtual circuits (VCs) of that service category can transit the tunnel.

Figure 7-5 shows a public UNI interface over a DS3 connection between the ATM switch (HB-1) in the Headquarters building and the ATM switch (SB-1) in the Remote Sales building. To support signalling across this connection, a VP tunnel must be configured.

Figure 7-5: Public VP Tunnel Network Example

To configure a VP tunnel connection for a single service category, perform the following steps, beginning in global configuration mode:

Step Command Task

1
atm connection-traffic-table-row [index row-index] vbr-nrt pcr rate scr10 scrval

Optionally, configure the connection-traffic-table-row index for any nondefault traffic values.

2
interface atm card/subcard/port

Select the physical interface to be configured.

3
atm pvp vpi [rx-cttr index] [tx-cttr index]

Configure an interface permanent virtual path (PVP) leg.

4
interface atm card/subcard/port.vpt #

Create a VP tunnel using a VPT number that matches the PVP leg virtual path identifier (VPI).

Step	Command	Task
1	atm connection-traffic-table-row [index row-index] vbr-nrt pcr rate scr10 scrval	Optionally, configure the connection-traffic-table-row index for any nondefault traffic values.
2	interface atm card/subcard/port	Select the physical interface to be configured.
3	atm pvp vpi [rx-cttr index] [tx-cttr index]	Configure an interface permanent virtual path (PVP) leg.
4	interface atm card/subcard/port.vpt #	Create a VP tunnel using a VPT number that matches the PVP leg virtual path identifier (VPI).

Note The row index for nondefault rx-cttr and tx-cttr must be configured before these optional parameters are used.

Examples

The following example shows how to configure the ATM VP tunnel on the ATM switch (HB-1) at interface 1/0/0, VPI 99:

Switch(HB-1)(config)# interface atm 1/0/0

Switch(HB-1)(config-if)# atm pvp 99

Switch(HB-1)(config-if)# exit

Switch(HB-1)(config)# interface atm 1/0/0.99

Switch(HB-1)(config-subif)# end

Switch(HB-1)# 
%SYS-5-CONFIG_I: Configured from console by console

The following example shows how to configure the ATM VP tunnel on the ATM switch (SB-1) at interface 0/0/0, VPI 99:

Switch(SB-1)(config)# interface atm 0/0/0

Switch(SB-1)(config-if)# atm pvp 99

Switch(SB-1)(config-if)# exit

Switch(SB-1)(config)# interface atm 0/0/0.99

Switch(SB-1)(config-subif)# end

Switch(SB-1)# 
%SYS-5-CONFIG_I: Configured from console by console

Display the VP Tunnel Configuration

To show the ATM virtual interface configuration, use the following EXEC command:

Command Task

show atm interface atm card/subcard/port.vpt #

Show the ATM interface configuration.

Command	Task
show atm interface atm card/subcard/port.vpt #	Show the ATM interface configuration.

The following example shows the ATM virtual interface configuration for interface 1/0/0.99:

Switch# show atm interface atm 1/0/0.99


  
Interface:      ATM1/0/0.99     Port-type:      vp tunnel
IF Status:      UP              Admin Status:   up
Auto-config:    enabled         AutoCfgState:   waiting for response from peer
IF-Side:        Network         IF-type:        UNI
Uni-type:       Private         Uni-version:    V3.0
<information deleted>

Configuring a VP Tunnel for a Single Service Category with Rate-Limited Tunnel Output

The type of tunnel described in this section is configured as a VP of the CBR service category. By default, this tunnel can carry VCs only of the CBR service category. However, it is possible to configure this VP tunnel to carry VCs of other service categories. The overall output of this VP tunnel is rate-limited by hardware to the peak cell rate (PCR) of the tunnel. This type of tunnel is also called a shaped VP tunnel.

Note Shaped VP tunnels are supported only on systems with the FC-PFQ.

A shaped VP tunnel is defined as a CBR VP with a PCR. The following limitations apply:

A maximum of 64 shaped VP tunnels can be defined on interfaces x/0/y; similarly, a maximum of 64 shaped VP tunnels can be defined on interfaces x/1/y.
The bandwidth of the shaped VP tunnel is shared by the active VCs inside the tunnel in strict round-robin (RR) fashion.
Even though the shaped VP tunnel is defined as CBR, it can carry VCs of another service category by substituting the new service category after the tunnel interface has been initially configured. For configuration information, see the section "Configure Interface Service Category Support" in the chapter "Configuring Resource Management."
Shaped VP tunnels do not support merged VCs for tag switching.
UBR+ and ABR VCs with non-zero MCR are not allowed on a shaped VP tunnel interface.
A maximum of 128 VCs can transit a shaped VP tunnel interface.

Configure a Shaped VP Tunnel on an Interface

To configure a shaped VP tunnel, perform the following steps, beginning in global configuration mode:

Step Command Task

1
atm connection-traffic-table-row [index row-index] cbr pcr rate

Configure the connection-traffic-table row for the desired PVP CBR cell rate.

2
interface atm card/subcard/port

Select the physical interface to be configured.

3
atm pvp vpi shaped rx-cttr index tx-cttr index

Configure an interface permanent virtual path (PVP) leg.

4
exit

Exit interface configuration mode.

5
interface atm card/subcard/port.vpt #

Create a shaped VP tunnel using a VPT number that matches the PVP leg virtual path identifier (VPI).

Step	Command	Task
1	atm connection-traffic-table-row [index row-index] cbr pcr rate	Configure the connection-traffic-table row for the desired PVP CBR cell rate.
2	interface atm card/subcard/port	Select the physical interface to be configured.
3	atm pvp vpi shaped rx-cttr index tx-cttr index	Configure an interface permanent virtual path (PVP) leg.
4	exit	Exit interface configuration mode.
5	interface atm card/subcard/port.vpt #	Create a shaped VP tunnel using a VPT number that matches the PVP leg virtual path identifier (VPI).

Note The rx-cttr and tx-cttr row indexes must be configured before they are used.

Example

The following example shows how to configure a shaped VP tunnel with a PVP of 99 as ATM interface 0/0/0.99

Switch(config)# interface atm 0/0/0

Switch(config-if)# atm pvp 99 shaped rx-cttr 100 tx-cttr 100

Switch(config-if)# exit

Switch(config-if)# int atm 0/0/0.99

Display the Shaped VP Tunnel Configuration

To display the shaped VP tunnel interface configuration, use the following EXEC command:

Command Task

show atm interface atm card/subcard/port.vpt#

Show the ATM VP interface configuration.

Command	Task
show atm interface atm card/subcard/port.vpt#	Show the ATM VP interface configuration.

For an example display from the show atm interface command, see the section "Display the Hierarchical VP Tunnel Configuration."

Configuring a VP Tunnel for Multiple Service Categories with Rate-Limited Tunnel Output

The type of VP tunnel described in this section allows VCs of multiple service categories to pass through the tunnel. In addition, the overall output of the VP tunnel is rate-limited to the PCR of the tunnel. This type of tunnel is also called a hierarchical VP tunnel. There is no general limit on the number of connections allowed on a such a tunnel. Hierarchical VP tunnels can also support merged VCs for tag switching. Refer to the section "Configure VC Merge" in the chapter "Configuring Tag Switching."

Service categories supported include the following:

Constant bit rate (CBR)
Variable bit rate (VBR)
Available bit rate (ABR) with a nonzero minimum cell rate (MCR)
Unspecified bit rate (UBR+) with a nonzero MCR

While capable of carrying any traffic category, a hierarchical VP tunnel is itself defined as CBR with a PCR. The following limitations apply:

Hierarchical VP tunnels are supported only with the FC-PFQ.
Hierarchical VP tunnels can be defined only on interfaces in slots 0 and 3.
A maximum of 30 hierarchical VP tunnels can be defined on interfaces 0/0/x and 3/0/x. A maximum of 30 hierarchical VP tunnels can be defined on interfaces 0/1/x and 3/1/x.

Enable Hierarchical Mode

Before configuring a hierarchical VP tunnel, you must first enable hierarchical mode, then reload the ATM switch. To do, perform the following steps, beginning in global configuration mode:

Step Command Task

1
atm hierarchical-tunnel

Enable hierarchical mode.

2
exit

Exit global configuration mode.

3
copy system:running-config nvram:startup-config

Save the running configuration to the startup configuration.

4
reload

Reload the operating system.

Step	Command	Task
1	atm hierarchical-tunnel	Enable hierarchical mode.
2	exit	Exit global configuration mode.
3	copy system:running-config nvram:startup-config	Save the running configuration to the startup configuration.
4	reload	Reload the operating system.

Note Enabling hierarchical mode causes the minimum rate allocated for guaranteed bandwidth to a connection to be increased.

Example

The following example shows how to enable hierarchical mode, then save and reload the configuration.

Switch(config)# atm hierarchical-tunnel

Switch(config)# exit

Switch# copy system:running-config nvram:startup-config

Switch# reload

Configure a Hierarchical VP Tunnel on an Interface

To configure a hierarchical VP tunnel, perform the following steps, beginning in global configuration mode:

Step Command Task

1
atm connection-traffic-table-row [index row-index] cbr pcr rate

Configure the connection-traffic-table row for the desired PVP CBR cell rate.

2
interface atm card/subcard/port

Select the physical interface to be configured.

3
atm pvp vpi hierarchical rx-cttr index tx-cttr index

Configure an interface permanent virtual path (PVP) leg.

4
exit

Exit interface configuration mode.

5
interface atm card/subcard/port.vpt #

Create a hierarchical VP tunnel using a VPT number that matches the PVP leg virtual path identifier (VPI).

Step	Command	Task
1	atm connection-traffic-table-row [index row-index] cbr pcr rate	Configure the connection-traffic-table row for the desired PVP CBR cell rate.
2	interface atm card/subcard/port	Select the physical interface to be configured.
3	atm pvp vpi hierarchical rx-cttr index tx-cttr index	Configure an interface permanent virtual path (PVP) leg.
4	exit	Exit interface configuration mode.
5	interface atm card/subcard/port.vpt #	Create a hierarchical VP tunnel using a VPT number that matches the PVP leg virtual path identifier (VPI).

Note The rx-cttr and tx-cttr row indexes must be configured before they are used.

Example

The following example shows how to configure a hierarchical VP tunnel with a PVP of 99 as ATM interface 0/0/0.99

Switch(config)# interface atm 0/0/0

Switch(config-if)# atm pvp 99 hierarchical rx-cttr 100 tx-cttr 100

Switch(config-if)# exit

Switch(config-if)# interface atm 0/0/0.99

Display the Hierarchical VP Tunnel Configuration

To display the hierarchical VP tunnel interface configuration, use the following EXEC command:

Command Task

show atm interface atm card/subcard/port.vpt#

Show the ATM VP interface configuration.

Command	Task
show atm interface atm card/subcard/port.vpt#	Show the ATM VP interface configuration.

Example

The following example shows the VP tunnel configuration on interface ATM 1/0/0 with PVP 99.

switch# show atm interface atm 1/0/0.99

Interface:      ATM1/0/0.99     Port-type:      vp tunnel
IF Status:      UP              Admin Status:   up
Auto-config:    enabled         AutoCfgState:   waiting for response from peer
IF-Side:        Network         IF-type:        UNI
Uni-type:       Private         Uni-version:    V3.0
Max-VPI-bits:   0               Max-VCI-bits:   14
Max-VP:         0               Max-VC:         16383
ConfMaxSvpcVpi: 0               CurrMaxSvpcVpi: 0
ConfMaxSvccVpi: 0               CurrMaxSvccVpi: 0
ConfMinSvccVci: 35              CurrMinSvccVci: 35
Signalling:     Enabled
ATM Address for Soft VC: 47.0091.8100.0000.0060.3e64.fe01.4000.0c81.9000.63
Configured virtual links:
  PVCLs SoftVCLs   SVCLs   TVCLs Total-Cfgd Inst-Conns
      4        0       0       0          4          4

Configuring Signalling VPCI for VP Tunnels

You can specify the value of the virtual path connection identifier (VPCI) that is to be carried in the signalling messages within a VP tunnel. The connection identifier information element (IE) is used in signalling messages to identify the corresponding user information flow. The connection identifier IE contains the VPCI and VCI.

Note By default, the VPCI is the same as the VPI on the ATM switch.

For example, if you want to configure a PVP tunnel connection from a ATM switch on VPI 2, VCI X, to a router with a virtual path switch in between, the signalling message would contain connection ID, VPI 2, VCI X. Since the PVP tunnel at the router end is on VPI 3, VCI X, the connection is refused. By configuring VPCI to 3, you can configure the signalling message explicitly to contain connection ID VPI 3, VCI X, instead of VPI 2, VCI X.

This command can also be used to support virtual UNI connections.

To configure a VP tunnel connection signalling VPCI, perform the following steps, beginning in global configuration mode:

Step Command Task

1
interface atm card/subcard/port.vpt #

Select the subinterface.

2
atm signalling vpci vpci-number

Configure the atm signalling VPCI number 0 to 255.

Step	Command	Task
1	interface atm card/subcard/port.vpt #	Select the subinterface.
2	atm signalling vpci vpci-number	Configure the atm signalling VPCI number 0 to 255.

Example

The following example configures a VP tunnel on ATM interface 0/0/0, PVP 99, and then configures the connection ID VCPI as 0.

Switch(config)# interface atm 1/0/0

Switch(config-if)# atm pvp 99

Switch(config-if)# exit

Switch(config)# interface atm 1/0/0.99


  
Switch(config-subif)# atm signalling vpci 0

Switch(config-subif)# end

Display the VP Tunnel VPCI Configuration

To confirm the VP tunnel VPCI configuration, use the following privileged EXEC command.

Command Task

more system:running-config

Show the PVP tunnel subinterface configuration.

Command	Task
more system:running-config	Show the PVP tunnel subinterface configuration.

Deleting VP Tunnels

To delete a VP tunnel connection, perform the following steps, beginning in global configuration mode:

Step Command Task

1
no interface atm card/subcard/port.vpt #

Delete the subinterface.

2
interface atm card/subcard/port

Select the physical interface to be modified.

3
no atm pvp vpi

Delete the interface PVP half-leg.

Step	Command	Task
1	no interface atm card/subcard/port.vpt #	Delete the subinterface.
2	interface atm card/subcard/port	Select the physical interface to be modified.
3	no atm pvp vpi	Delete the interface PVP half-leg.

Example

The following example shows deleting subinterface 99 at ATM interface 1/0/0 and the
PVP half-leg 99:

Switch(HB-1)(config)# no interface atm 1/0/0.99

Switch(HB-1)(config)# interface atm 1/0/0

Switch(HB-1)(config-if)# no atm pvp 99

Confirm VP Deletion

To confirm the ATM virtual interface deletion, use the following EXEC command:

Command Task

show atm interface [atm card/subcard/port[.vpt #]]

Show the ATM interface configuration.

Command	Task
show atm interface [atm card/subcard/port[.vpt #]]	Show the ATM interface configuration.

Example

The following example shows that ATM subinterface 1/0/0.99 on the ATM switch-1 (HB-1) has been deleted:

Switch(HB-1)# show interface atm 1/0/0

IF Status:      UP              Admin Status:   up
Auto-config:    disabled        AutoCfgState:   not applicable
IF-Side:        Network         IF-type:        NNI
Uni-type:       not applicable  Uni-version:    not applicable
Max-VPI-bits:   8               Max-VCI-bits:   14
Max-VP:         255             Max-VC:         16383
ConfMaxSvpcVpi: 255             CurrMaxSvpcVpi: 255
ConfMaxSvccVpi: 255             CurrMaxSvccVpi: 255
ConfMinSvccVci: 35              CurrMinSvccVci: 35
Svc Upc Intent: pass            Signalling:     Enabled
ATM Address for Soft VC: 47.0091.8100.0000.00e0.4fac.b401.4000.0c80.8000.00
Configured virtual links:
  PVCLs SoftVCLs   SVCLs   TVCLs   PVPLs SoftVPLs   SVPLs Total-Cfgd Inst-Conns
      4        0       0       0       0        0       0          4          3
Logical ports(VP-tunnels):     0
Input cells:    263843          Output cells:   273010
5 minute input rate:             0 bits/sec,       0 cells/sec
5 minute output rate:            0 bits/sec,       0 cells/sec
Input AAL5 pkts: 172265, Output AAL5 pkts: 176838, AAL5 crc errors: 0

Configuring a PVC to a VP Tunnel

To configure an end point of a permanent virtual circuit (PVC) to a previously created PVP tunnel, perform the following steps, beginning in global configuration mode:

Step Command Task

1
interface atm card/subcard/port

Select the physical interface to be configured.

2
atm pvc vpi-a vci-a [upc upc] [pd pd] [rx-cttr index] [tx-cttr index] interface atm card/subcard/port[.vpt #] vpi-b vci-b [upc upc]

Configure the PVC with the VPI of the tunnel leg matching the tunnel VPT number.

Step	Command	Task
1	interface atm card/subcard/port	Select the physical interface to be configured.
2	atm pvc vpi-a vci-a [upc upc] [pd pd] [rx-cttr index] [tx-cttr index] interface atm card/subcard/port[.vpt #] vpi-b vci-b [upc upc]	Configure the PVC with the VPI of the tunnel leg matching the tunnel VPT number.

The following restrictions apply to an end point of a PVC-to-PVP tunnel subinterface:

The VPI number of the tunnel leg of any PVC connection must match the VPT number of the tunnel.

For single service-category VP tunnels, the service class specified by the connection-traffic-table-row (CTTR) of any PVC connections must match the service category for the row(s) selected for the tunnel PVP (for simple VP tunnels), or the configured service category (for shaped VP tunnels). This restriction does not apply to VP tunnels configured for multiple service categories (hierarchical VP tunnels).
For service classes other than UBR, the PCRs of all PVCs must be within the peak cell rate of the tunnel PVP. This setup requires new CTTR rows to be defined for CBR or VBR PVCs, with peak cell rates that are less than the intended tunnel PVP.

Example

The following example shows how to configure the example tunnel ATM1/0/0.99 with a PVC from interface ATM 0/0/1 to the tunnel at ATM interface 1/0/0.99:

Switch(HB-1)(config)# interface atm 0/0/1

Switch(HB-1)(config-if)# atm pvc 0 50 interface atm 1/0/0.99 99 40

Display PVCs

To confirm PVC interface configuration, use the following EXEC command:

Command Task

show atm vc interface atm card/subcard/port

Show the ATM VC interface configuration.

Command	Task
show atm vc interface atm card/subcard/port	Show the ATM VC interface configuration.

Example

The following example shows the configuration of ATM subinterface 1/0/0.99 on the ATM switch-1 (HB-1):

Switch(HB-1)# show atm vc interface atm 0/0/1

Interface    VPI   VCI   Type    X-Interface  X-VPI X-VCI  Encap Status
ATM0/0/1     0     5      PVC     ATM2/0/0     0     41    QSAAL  UP
ATM0/0/1     0     16     PVC     ATM2/0/0     0     33    ILMI   UP
ATM0/0/1     0     50     PVC     ATM1/0/0.99  99    40           UP

Configuring a VPI/VCI Range for SVPs/SVCs

You can configure a virtual path identifier/virtual channel identifier (VPI/VCI) range for switched virtual circuits/switched virtual paths (SVCs/SVPs). ILMI uses the specified range to negotiate the VPI/VCI range parameters with peers. This feature allows you to do the following:

Specify ranges for SVCs and SVPs.
Avoid VPI/VCI conflicts when attempting to set up soft PVCs or soft PVPs. For example, if you specify a soft PVC with VPI 0 and VCI 50 on the destination interface, an SVC on that interface might have already taken VPI 0 and VPI 50 just before the soft PVC setup message arrives at the destination interface. In this case, the soft PVC is rejected because VPI 0 and VPI 50 are already taken. By specifying the VPI/VCI range for SVPs/SVCs, you can avoid connection setup rejections.

You can still configure PVCs and PVPs in any supported range, including any VPI/VCI range you configured for SVCs/SVPs.

Note This feature is supported in ILMI 4.0.

The default maximum switched virtual path connection (SVPC) VPI is equal to the maximum VPI supported on the interface. You can change the maximum SVPC VPI by entering the atm svpc vpi max value command. Substitute value with:

A number in range of 0 to 3 for 25-Mbps interfaces.
A number in range of 0 to 255 for all other interfaces except logical interfaces, which have a fixed value of 0.

In the example shown in Figure 7-6, the maximum SVPC VPI is 100. Therefore, VPIs 1 to 100 are reserved for SVPCs. You can use VPIs 101 to 255 for PVPs; however, you are not restricted to that range.

Figure 7-6: Example SVPC VPI Range

The default maximum switched virtual channel connection (SVCC) VPI is equal to the maximum VPI supported on the interface. You can change the maximum SVCC VPI by entering the atm svcc vpi max value command. Substitute value with:

A number in the range of 0 to 3 for 25-Mbps interfaces.
A number in the range of 0 to 255 for all other interfaces except logical interfaces, which have a fixed value of 0.

The default minimum SVCC VCI is equal to 35. You can change the minimum SVCC VCI by entering the atm svcc vci min value command. Substitute value with a number in the range of 32 to 4095.

In the example shown in Figure 7-7, the maximum SVCC VPI is 100 and the minimum SVCC VCI is 60. Therefore, VPIs 0 through 100 and VCIs 60 through 16,383 are reserved for SVCCs.

Figure 7-7: Example SVCC VPI/VCI Range

Every interface negotiates the local values for the maximum SVPC VPI, maximum SVCC VPI, and minimum SVCC VCI with the peer's local value during ILMI initialization. The negotiated values determine the ranges for SVPs and SVCs. If the peer interface does not support these objects or autoconfiguration is turned off on the local interface, the local values determine the range.

To configure a VPI/VCI range for SVCs/SVPs, perform the following steps, beginning in global configuration mode:

Step Command Task

1
interface atm card/subcard/port[.subinterface#]

Select the physical interface to be configured.

2
atm svpc vpi max value

Configure the maximum VPI value for a SVPC.

3
atm svcc vpi max value

Configure the maximum VPI value for a SVCC.

4
atm svcc vci min value

Configure the minimum VCI value for a SVCC.

Step	Command	Task
1	interface atm card/subcard/port[.subinterface#]	Select the physical interface to be configured.
2	atm svpc vpi max value	Configure the maximum VPI value for a SVPC.
3	atm svcc vpi max value	Configure the maximum VPI value for a SVCC.
4	atm svcc vci min value	Configure the minimum VCI value for a SVCC.

The following example shows configuring ATM interface 0/0/0 with the SVPC and SVCC VPI maximum set to 100 and SVCC VCI minimum set to 60.

Switch(config)# interface atm 0/0/0

Switch(config-if)# atm svpc vpi max 100

Switch(config-if)# atm svcc vpi max 100

Switch(config-if)# atm svcc vci min 60

Display the VPI/VCI Range Configuration

To confirm the VPI/VCI range configuration, use one of the following commands:

Command Task

show atm interface atm card/subcard/port [.subinterface#]

Show the ATM interface configuration.

show atm ilmi-status atm card/subcard/port [.subinterface#]

Show the ILMI status on the ATM interface.

Command	Task
show atm interface atm card/subcard/port [.subinterface#]	Show the ATM interface configuration.
show atm ilmi-status atm card/subcard/port [.subinterface#]	Show the ILMI status on the ATM interface.

Examples

The following example shows how to confirm the VPI/VCI range configuration on an ATM interface. The values displayed for ConfMaxSvpcVpi, ConfMaxSvccVpi, and ConfMinSvccVci are local values. The values displayed for CurrMaxSvpcVpi, CurrMaxSvccVpi, and CurrMinSvccVci are negotiated values.

Switch# show atm interface atm 0/0/0

Interface:      ATM0/0/0        Port-type:      oc3suni
IF Status:      DOWN            Admin Status:   down
Auto-config:    enabled         AutoCfgState:   waiting for response from peer
IF-Side:        Network         IF-type:        UNI
Uni-type:       Private         Uni-version:    V3.0
Max-VPI-bits:   8               Max-VCI-bits:   14
Max-VP:         255             Max-VC:         16383

  
ConfMaxSvpcVpi: 100             CurrMaxSvpcVpi: 100

  
ConfMaxSvccVpi: 100             CurrMaxSvccVpi: 100

  
ConfMinSvccVci: 60              CurrMinSvccVci: 60
Svc Upc Intent: pass            Signalling:     Enabled
ATM Address for Soft VC: 47.0091.8100.0000.0040.0b0a.2a81.4000.0c80.0000.00
Configured virtual links:
  PVCLs SoftVCLs   SVCLs   TVCLs   PVPLs SoftVPLs   SVPLs Total-Cfgd Inst-Conns
      3        0       0       0       0        0       0          3          0
Logical ports(VP-tunnels):     0
Input cells:    0               Output cells:   0
5 minute input rate:             0 bits/sec,       0 cells/sec
5 minute output rate:            0 bits/sec,       0 cells/sec
Input AAL5 pkts: 0, Output AAL5 pkts: 0, AAL5 crc errors: 0

The following example shows how to confirm the peer's local values for VPI/VCI range configuration by displaying the ILMI status on an ATM interface:

Switch# show atm ilmi-status atm 0/0/0

Interface : ATM0/0/0 Interface Type : Private NNI 
ILMI VCC : (0, 16) ILMI Keepalive : Disabled
Addr Reg State:   UpAndNormal
Peer IP Addr:     172.20.40.232   Peer IF Name:     ATM0/0/0
Peer MaxVPIbits:  8               Peer MaxVCIbits:  14

  
Peer MaxVPCs:     255                         Peer MaxVCCs:     16383 

  
Peer MaxSvccVpi:  255                         Peer MinSvccVci:  255 

  
Peer MaxSvpcVpi:  48 
Configured Prefix(s) :
47.0091.8100.0000.0010.11ba.9901

Note Note that the show atm ilmi-status command displays the information above only if the peer supports it.

Table of Contents

Configuring ATM Network Interfaces

Example

Example

Example

Example

Example

Example

Example

Example

Examples

Example

Example

Example

Example

Example

Example

Example

Example

Example

Examples