Table of Contents

Configuring Virtual Connections

This chapter describes how to configure virtual connections (VCs) in a typical ATM network after autoconfiguration has established the default network connections. The network configuration modifications described in this chapter are used to optimize your ATM network operation.

The tasks to configure virtual connections are described in the following sections:

Characteristics and Types and of Virtual Connections

The characteristics of the VC, established when the VC is created, include the following:

These switching features can be turned off with interface configuration commands; autonomous switching must be explicitly enabled per interface.

Table 6-1 list the types of supported virtual connections.

Table 6-1   Supported LightStream 1010 ATM switch Virtual Connection Types

Configuring Permanent Virtual Channel Connections

This section describes configuring LightStream 1010 ATM switch VCCs. A VCC is established as a bidirectional facility to transfer ATM traffic between two ATM layer users. Figure 6-1 shows an example VCC between ATM user A and user D.

To configure a point-to-point VCC, perform the following steps, beginning in global configuration mode:

Examples

The following example shows how to configure the internal cross-connect PVC on Switch B between interface 3/0/1, VPI = 0, VCI = 50 and interface 3/0/2, VPI = 2, VCI = 100 (see Figure 6-1):

The following example shows how to configure the internal cross-connect PVC on Switch C between interface 4/1/0, VPI = 2, VCI = 100 and interface 0/0/1, VPI 50, VCI = 255:

Each subsequent VC cross-connection and link must be configured until the VC is terminated to create the entire VCC.

The following example shows how to configure the CPU leg of any terminating PVC:

When configuring the CPU leg of a PVC that is not a tunnel, the VPI should be configured as 0. The preferred method of VCI configuration is to select the any-vci parameter, unless a specific VCI is needed as a parameter in another command, such as map-list.

Display Virtual Channel Connections

To show the VC configuration, use the following EXEC commands:

Examples

The following example displays the Switch B PVC configuration on ATM interface 3/0/1:

The following example displays the Switch B PVC configuration on ATM interface 3/0/1:

The following example displays the Switch B configuration on interface 3/0/1, VPI = 0, VCI = 50 with feature card per-class queueing (FC-PCQ) (Feature Card 1) installed:

The following example displays the Switch B PVC configuration on ATM interface 3/0/1, VPI = 0, VCI = 50, with feature card per-flow queueing (FC-PFQ) installed:

Configuring Terminating PVC Connections

This section describes configuring point-to-point and point-to-multipoint terminating PVC connections. Terminating connections provide the connection to the LightStream 1010 ATM switch CPU for LAN Emulation (LANE), IP over ATM, and control channels for Interim Local Management Interface (ILMI), signaling, and Private Network-to-Network Interface (PNNI) plus network management.

Figure 6-2 shows an example of transit and terminating connections.

Point-to-point and point-to-multipoint are two types of terminating connections. Both terminating connections are configured using the same commands as transit connections (discussed in the previous sections). However, all switch terminating connections use interface 2/0/0 to connect to the switch CPU.

To configure both point-to-point and point-to-multipoint terminating PVC connections, perform the following steps, beginning in global configuration mode

:

When configuring point-to-multipoint PVC connections using the atm pvc command, the root point is port A and the leaf points are port B.

Examples

The following example shows how to configure the CPU leg of any terminating PVC:

When configuring the CPU leg of a PVC that is not a tunnel, the VPI should be configured as 0. The preferred method of VCI configuration is to select the any-vci parameter, unless a specific VCI is needed as a parameter in another command, such as map-list.

The following example shows how to configure the internal cross-connect PVC between interface 3/0/1, VPI = 1, VCI =50 and the terminating connection at the CPU interface 2/0/0, VPI = 0, and VCI unspecified:

The following example shows how to configure a point-to-multipoint connection from the root-point PVC on switch interface 0/0/0, VPI = 50, VCI =100 and the terminating connection at the leaf-point switch CPU interface 2/0/0, VPI = 0, VCI = 300:

Display the Terminating PVC Connections

To show the terminating PVC configuration, use the following EXEC commands:

See the section "Display Virtual Channel Connections" for examples of the show atm vc commands.

Configuring Permanent Virtual Path Connections

This section describes configuring a PVP connection. Figure 6-3 shows an example of a LightStream 1010 ATM switch with PVPs configured through the switch.

To configure a PVP connection, perform the following steps, beginning in global configuration mode:

Examples

The following example shows how to configure the internal cross-connect PVP within Switch B between interfaces 3/0/1, VPI = 1 and interface 3/0/2, VPI = 2:

The following example shows how to configure the internal cross-connect PVP within Switch C between interfaces 4/1/0, VPI = 2 and interface 0/0/1, VPI = 50:

Each subsequent PVP cross connection and link must be configured until the VP is terminated to create the entire PVP.

Display the Virtual Path Connection

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

Example

The following example displays the PVP configuration of Switch B:

The following example displays the PVP configuration of Switch B with FC-PCQ (Feature Card 1) installed:

The following example displays the PVP configuration of Switch B with FC-PFQ installed:

Configuring Point-to-Multipoint PVC Connection

This section describes configuring point-to-multipoint PVC connections. In Figure 6-4, cells entering the switch at the root point (on the left side at interface 0/0/0, VPI = 50, VCI = 100), are duplicated and switched to the leaf points (output interfaces) on the right side of the example.

To configure the point-to-multipoint PVC connections shown in Figure 6-4, perform the following steps, beginning in global configuration mode:

To configure the point-to-multipoint PVC connections using the atm pvc command, the root point is port A and the leaf points are port B.

Examples

The following example shows how to configure the root-point PVC on switch interface 0/0/0, VPI = 50, VCI =100 to the leaf-point interface 0/1/0, VPI = 60, VCI = 200 (see Figure 6-4):

The following example shows how to configure the same root-point PVC to the leaf point interface 0/1/1, VPI = 70, VCI = 210:

The following example shows how to configure the same root-point PVC to the leaf point interface 0/1/2, VPI = 80, VCI = 220:

Display Point-to-Multipoint PVC Configuration

To show the point-to-multipoint PVC configuration, use the following EXEC mode commands:

Examples

The following example displays the point-to-multipoint PVC configuration on interface 0/0/1 with FC-PFQ installed:

The following example displays the VC configuration on interface 0/0/0, VPI = 50, VCI = 100 with FC-PCQ (Feature Card 1) installed:

The following example displays the VC configuration on interface 0/0/0, VPI = 50, VCI = 100 with FC-PFQ installed:

Configuring Point-to-Multipoint PVP Channels

This section describes configuring point-to-multipoint PVP connections. Figure 6-5 provides an example of point-to-multipoint PVP connections.

In Figure 6-5, cells entering the switch at the root point (the left side at interface 0/0/0), VPI = 50, are duplicated and switched to the leaf points (output interfaces), on the right side of the example.

To configure point-to-multipoint PVP connections, perform the following steps, beginning in global configuration mode:

To configure the point-to-multipoint PVP connections using the atm pvp command, the root point is port A and the leaf points are port B.

Examples

The following example shows how to configure the root-point PVP on switch interface 0/0/0, VPI = 50 to the leaf point interface 0/1/0, VPI = 60 (see Figure 6-5):

The following example shows how to configure the same root-point PVP to the leaf-point interface 0/1/0, VPI = 70:

The following example shows how to configure the same root-point PVP to the leaf-point interface 0/1/2, VPI = 80:

Display Point-To-Multipoint PVP Configuration

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

Examples

The following example displays the PVP configuration of the point-to-multipoint PVP connections on ATM interface 0/0/0:

The following example displays the PVP configuration of the point-to-multipoint PVP connections on ATM interface 0/0/0 VPI = 50 with FC-PCQ (Feature Card 1) installed:

The following example displays the PVP configuration of the point-to-multipoint PVP connections on ATM interface 0/0/0 VPI = 50 with FC-PFQ installed:

Configuring Soft PVC Connections

This section describes configuring soft PVC connections, which provide the following features:

Figure 6-6 is an illustration of the soft PVC connections used in the following examples.

Guidelines for Creating Soft PVCs

Perform the following steps when you configure soft PVCs:

Step 2   Decide which of these two ports you want to designate as the destination (or passive) side of the soft PVC.

This decision is arbitrary—it makes no difference which port you define as the destination end of the circuit.

Step 3   Configure the destination (passive) side of the soft PVC.

You must configure the destination end of the soft PVC first, to define an ATM address for that port.

You must retrieve this address (see Step 4), and the VPI/VCI values for the circuit (see Step 5), and use these elements as part of the command string when you configure the source (active) end of the soft PVC (see Step 6).

Step 4   Retrieve the ATM address of the destination end of the soft PVC using the show atm address command. This command typically produces output in the following form:

Step 5   Retrieve the VPI/VCI values for the circuit using the show atm vc command. This command typically produces output in the following form:

Step 6   Configure the source (active) end of the soft PVC. At the same time, complete the soft PVC setup using the information derived from Step 4 and Step 5.

You must configure the source end of the soft PVC last because this not only defines the configuration information for the source port, but also requires you to enter the ATM address and VPI/VCI values for the destination port.

If you have not already defined the destination port for the soft PVC (as required in Step 3), this ATM address is not defined for the destination port, and the VPI/VCI values are not available, as required in Step 6 for use in completing the soft PVC.

Soft Permanent Virtual Channel Configuration

To configure a soft PVC connection, perform the following steps, beginning in privileged EXEC mode:

Examples

The following example shows how to allow User A to determine the destination ATM address of the interface connected to User D:

The following example shows how to configure a soft PVC on Switch B between interface 0/0/0, source VPI = 0, source VCI = 200; and switch C, destination ATM address = 47.0091.8100.00.0000.1111.1111.1111.1111.1111.1111.00, VPI = 0, VCI = 100 (see Figure 6-6):

Display Soft VC Configuration

To display the soft VC configuration at either end of a switch, use the following EXEC commands:

Examples

The following example displays the soft VC configuration of Switch B, on interface 0/0/0 out to the ATM network:

The following example displays the soft VC configuration of Switch C, on interface 4/0/0 out to the ATM network:

The following example displays the soft VC configuration of Switch B, on interface 0/0/0, VPI = 0, VCI = 200 out to the ATM network with FC-PCQ (Feature Card 1) installed:

The following example displays the soft VC configuration of Switch B, on interface 0/0/0, VPI = 0, VCI = 200 out to the ATM network with FC-PFQ installed:

Configuring Soft PVP Connections

This section describes configuring soft PVP connections, which provide the following features:

Figure 6-7 is an illustration of the soft PVP connections used in the examples in this section.

To configure a soft PVP connection, perform the following steps, beginning in global configuration mode:

Example

The following example shows how to configure a soft PVP on Switch B between interface 0/0/0, source VPI = 75, and Switch C, destination ATM address = 47.0091.8100.00.0000.1111.1111.1111.1111.1111.1111.00, VPI = 50 (Figure 6-7):

Display Virtual Path Connection

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

Examples

The following example displays the soft VP configuration at Switch B, on interface 0/0/0 out to the ATM network:

The following example displays the soft VP configuration at Switch C, on interface 4/0/0 out to the ATM network:

The following example displays the soft VP configuration at Switch B, on interface 0/0/0, VPI = 75 out to the ATM network with FC-PCQ (Feature Card 1) installed:

The following example displays the soft VP configuration at Switch B, on interface 0/0/0, VPI = 75 out to the ATM network with FC-PFQ installed:

Configuring the Soft PVC Route Optimization Feature

This section describes the soft PVC route optimization feature. Most soft PVCs have a much longer lifetime than SVCs. The route chosen during PVC setup remains the same even though the network topology may change.

Soft PVC connections, with the route optimization percentage threshold set, provide the following features:

Route optimization is directly related to administrative weight which is similar to hop count. For a description of administrative weight, see the section "Configure the Global Administrative Weight Mode" in the chapter "Configuring ATM Routing and PNNI."

Configuring soft PVC route optimization is described in the following sections:

Enable Soft PVC Route Optimization

Soft PVC route optimization must be enabled and a threshold level configured to determine the point when a better route is identified and the old route is reconfigured.

To enable and configure soft PVC route optimization, use the following global configuration command:

Example

The following example enables soft PVC route optimization and sets the threshold percentage to 250 percent:

Configure a Soft PVC Interface with Route Optimization

Soft PVC route optimization must be enabled and configured to determine the point at which a better route is found and the old route is reconfigured.

To enable and configure a soft PVC interface with route optimization, perform the following steps, beginning in global configuration mode:

Example

The following example shows how to configure a soft PVC with a route optimization interval configured as every 30 minutes between the hours of 6:00 P.M. and 5:00 A.M.:

Display Soft PVC Route Optimization Configuration

To display the soft PVC route optimization configuration, use the following EXEC command:

Example

The following example displays the soft PVC configuration on interface 0/0/0:

Configuring Nondefault Well-Known PVCs

Normally the default well-known VCs are automatically created with default VCIs. However, for the unusual instances where the LightStream 1010 ATM switch interfaces with nonstandard equipment, you can configure nondefault well-known VCI values on a per-interface basis.

Table 6-2 lists the default well-known VCs and their default configuration.

Table 6-2   Well-Known Virtual Channels

Caution Do not change the well-known channels to use a VC where the remote end is sending AAL5 messages not intended for the well-known VC. For example, do not swap VC values between two types of well-known VCs.

Overview of Nondefault PVC Configuration

Following is an overview of the steps needed to configure nondefault well-known VCs:

Step 2   Delete any existing automatically created well-known VCs.

Step 3   Configure the individual encapsulation type as follows:

Step 4   Copy running-configuration file to startup-configuration file.

Configure Nondefault PVCs

To configure the nondefault VCs for signaling, ILMI, and PNNI, perform the following steps, beginning in global configuration mode:

Example

The following example shows the nondefault VC configuration steps:

Step 2   Change to interface configuration mode for ATM interface 0/0/0.

Step 3   Enter manual well-known-vc mode and delete the existing default well-known VCs using the atm manual-well-known-vc delete command.

Step 4   Confirm deletion by entering y.

Step 5   Configure the nondefault VC for signaling from 5 (the default) to 35 using the atm pvc 1 35 interface atm 2/0/0 0 any-vci encap qsaal command.

Step 6   Configure the ILMI VC, then configure the PNNI VC if needed using the same procedure.

Step 7   Save the new running configuration to the startup configuration using the copy running-config startup-config command.

An example of this procedure follows:

Configuring Interface and Connection Snooping

Snooping allows the cells from all connections, in either receive or transmit direction, on a selected physical port to be transparently mirrored to a snoop test port where an external ATM analyzer can be attached. Unlike shared medium LANs, an ATM system requires a separate port to allow nonintrusive traffic monitoring on a line.

Snooping Overview

The following sections provide background information on how snooping functions on the LightStream 1010 ATM switch.

Snooping the Receive Direction

Figure 6-8 shows snooping the receive direction of a port. Snoop test port X receives copies of cells that enter the switch at port A and belong to existing connections, regardless of the connection destinations that the cells mirrored before the cell output queues. Discarded cells do not reach the test port. All cells transmitted at test port X retain the cell headers present at the original receive port A.

Snooping the Transmit Direction

Figure 6-9 shows snooping the transmit direction of a port. Snoop test port X transparently receives copies of all cells that belong to connections destined for port A, regardless of the source port. The test port cells are duplicated during the output stage of the switching process after the cell output queues. Cell discards, cell buffering, and cell priority scheduling affect both copies of the cells in the same way. The cell headers transmitted from test port X matche the cell headers transmitted from the monitored port A.

Snoop Test Port is Highest Port

Only the highest port on the last module of a LightStream 1010 ATM switch can be configured as a snoop test port. The highest port can be configured as either the snoop test port or used as a standard port that acts as any other port. Table 6-3 lists the interface number of the allowed snoop test port for the various port adapter module (PAM) types. If you specify an incorrect snoop test port for the currently installed PAM type, an error appears on the console.

The port number of the test port depends on the card type. Table 6-3 defines the snoop test port number for the various interfaces.

Table 6-3   ATM Snoop Port Numbers

---

Note      If FC-PFQ is installed on your ASP, interface snooping is implemented in the software and has no restriction on the snoop test port. The snoop test port can be any port in the system. Also, multiple interfaces can be snooped simultaneously. You can configure snooping on both transmit and receive directions on two different ports and monitor traffic in both directions simultaneously.

---

Effect of Snooping on Monitored Port

There is no effect on cell transmission, interface or VC status and statistics, front panel indicators, or any other parameters associated with a port being monitored during snooping. Any port, other than the highest port, that contains a PAM type with a bandwidth less than or equal to the PAM bandwidth for the test port can be monitored by snooping.

Test Port Shutdown for Snoop Mode Configuration

The port being configured as a test port must be shut down before configuration. While the test port is shut down and after snoop mode has been configured, no cells are transmitted from the test port until it is reenabled using the no shutdown command. A test port can be put into snoop mode even if there are existing connections to it; however, those connections remain "Down" even after the test port is reenabled using the no shutdown command. This includes any terminating connections for ILMI, PNNI, or signaling channels on the test port.

If you use a show atm interface command while the test port is enabled in snoop mode, the screen shows the following:

• Interface state appears as "Snooping" instead of "up" or "down."
• Other ATM layer information for the test port is still displayed.
• Any previously configured connections on the test port remain installed, but are listed as Connection Status = down.
• Data for transmitted cells and output rates indicates the snooping cells are being transmitted.
• Counts for receive cells should remain unchanged and the input rate should be 0.

Other Configuration Options for Snoop Test Port

Most inapplicable configurations on the test port interface are disregarded while in snoop mode. However, the following configuration options are not valid when specified for the snoop test port and may affect the proper operation of the snoop mode on the test port.

• Diagnostic and PIF loopbacks of the snoop test port. These types of loopbacks do not function in snooping mode since the PIF receive side signals are disabled.
• Other physical layer loopbacks (line, cell, or payload) function normally when in snooping mode since they loop toward the line and are unaffected by the lack of PIF receive input.
• Interface pacing (with the rate for the snoop test port lower than the rate for the monitored port).
• Network-derived clock source using the snoop test port.
• Clock-source = loop-timed for the snoop test port.

---

Caution You should ensure that all options are valid and configured correctly while in the snoop mode.

---

Configure Interface Snooping

The atm snoop interface atm subcommand enables a port for snoop test only if the port is the highest system port residing on card 4 and subcard 1 (which has been shut down). Cells transmitted from the snoop test port are copies of cells from a single direction of a monitored port.

When in snoop mode, any prior permanent virtual connections to the snoop test port remain in the down state.

To configure interface port snooping, perform the following steps, beginning in global configuration mode:

Step	Command	Task
1	interface atm card/subcard/port	Select the interface to be configured.
2	atm snoop interface atm card/subcard/port direction [receive | transmit]	Specify the interface and direction to be snooped.

Example

The following example shows how to configure ATM interface 4/1/3 as the highest port in snoop mode to monitor ATM interface 1/1/0, tested in the transmit direction:

Switch# config term

Enter configuration commands, one per line. End with CNTL/Z.

Switch(config)# interface atm 4/1/3

Switch(config-if)# atm snoop interface atm 1/1/0 direction transmit

Display Interface Snooping

To display the test port information, use the following EXEC command:

Command	Task
show atm snoop	Display the snoop configuration.

Example

The following example displays the snoop configuration on the OC3 port and the actual register values for the highest interface:

Switch# show atm snoop

Snoop Test Port Name: ATM4/1/3 (interface status=SNOOPING)

Snoop option: (configured=enabled) (actual=enabled)

Monitored Port Name: (configured=ATM3/0/0) (actual=ATM3/0/0)

Snoop direction: (configured=receive) (actual=receive)

Configure Per-Connection Snooping

With per-connection snooping you must specify both the snooped connection endpoint and the snooping connection endpoint. The switch IOS adds the snooping connection endpoint as a leaf to the snooped connection. The root of the temporary multicast connection depends on the direction being snooped. Snooping in the direction of leaf to root is not allowed for multicast connections. Per-connection snooping features are as follows:

• Per-VC snooping
• Per-VP snooping

The snooping connection can be configured on any port when there is no VPI/VCI collision for the snoop connection with the existing connections on the port. Also the port should have enough resources to satisfy the snoop connection resource requirements. In case of failure, due to VPI/VCI collision or resource exhaustion, a warning message is displayed, and you can reconfigure the connection on a different port.

To snoop both transmit and receive directions of a connection, you need to configure two different snoop connections.

---

Note      Per-connection snooping is only available if you have FC-PFQ installed on your ASP.

---

Nondisruptive per-connection snooping is achieved by dynamically adding a leaf to an existing connection (either unicast or multicast). This can lead to cell discard if the added leaf cannot process the snooped cells fast enough. For a multicast connection ,the queue buildup is dictated by the slowest leaf in the connection. The leaf added for snooping inherits the same traffic characteristics as the other connection leg. This ensures that the added leaf does not become the bottleneck and affect the existing connection.

To configure connection snooping, perform the following steps, beginning in global configuration mode:

Step	Command	Task
1	interface atm card/subcard/port	Select the interface to be configured.
2	atm snoop-vc [a_vpi a_vci] interface atm card/subcard/port x_vpi x_vci [direction {receive | transmit}]	Configure the virtual channel to be snooped. a denotes the snooping connection. x denotes the snooped connection.
3	atm snoop-vp [a_vpi] interface atm card/subcard/port x_vpi [direction {receive | transmit}]	Configure the virtual path to be snooped.

Examples

The following example shows how to configure VC 100 200 on ATM interface 3/1/0 to snoop a VC 200 150, on ATM interface 1/0/0:

Switch# config term

Enter configuration commands, one per line. End with CNTL/Z.

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

Switch(config-if)# atm snoop-vc 100 200 interface atm 1/0/0 200 150 direction receive

The following example shows how to configure VP 100 on ATM interface 3/1/0 to snoop a VP 200, on ATM interface 1/0/0:

Switch# config term

Enter configuration commands, one per line. End with CNTL/Z.

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

Switch(config-if)# atm snoop-vp 100 interface atm 1/0/0 200 direction receive

Display Per-connection Snooping

To display the test per-connection information, use the following EXEC commands:

Command	Task
show atm snoop-vc [interface atm card/subcard/port [x_vpi x_vci]]	Display the snoop VC information.
show atm snoop-vp [interface atm card/subcard/port [x_vpi]]	Display the snoop VP information.

Examples

The following example shows all VC snoop connections on the switch:

Switch> show atm snoop-vc

Snooping Snooped

Interface VPI VCI Type X-Interface X-VPI X-VCI Dir Status

ATM0/0/2 0 5 PVC ATM0/1/1 0 5 Rx DOWN

ATM0/0/2 0 16 PVC ATM0/1/1 0 16 Rx DOWN

ATM0/1/2 0 5 PVC ATM0/0/1 0 5 Tx DOWN

ATM0/1/2 0 16 PVC ATM0/0/1 0 16 Tx DOWN

ATM0/1/2 0 18 PVC ATM0/0/1 0 18 Tx UP

ATM0/1/2 0 100 PVC ATM0/0/1 0 100 Tx DOWN

ATM0/1/2 0 201 PVC ATM0/0/1 0 201 Tx DOWN

ATM0/1/2 0 202 PVC ATM0/0/1 0 202 Tx DOWN

ATM0/1/2 0 300 PVC ATM0/0/1 0 300 Tx DOWN

ATM0/1/2 0 301 PVC ATM0/0/1 0 301 Tx DOWN

The following example shows the VC snoop connections on ATM interface 0/1/2:

Switch> show atm snoop-vc interface atm 0/1/2

Snooping Snooped

Interface VPI VCI Type X-Interface X-VPI X-VCI Dir Status

ATM0/1/2 0 5 PVC ATM0/0/1 0 5 Tx DOWN

ATM0/1/2 0 16 PVC ATM0/0/1 0 16 Tx DOWN

ATM0/1/2 0 18 PVC ATM0/0/1 0 18 Tx UP

ATM0/1/2 0 100 PVC ATM0/0/1 0 100 Tx DOWN

ATM0/1/2 0 201 PVC ATM0/0/1 0 201 Tx DOWN

ATM0/1/2 0 202 PVC ATM0/0/1 0 202 Tx DOWN

ATM0/1/2 0 300 PVC ATM0/0/1 0 300 Tx DOWN

ATM0/1/2 0 301 PVC ATM0/0/1 0 301 Tx DOWN

The following example shows the VC snoop connection 0, 55 on ATM interface 0/0/2 in extended mode with FC-PCQ (Feature Card 1) installed:

Switch> show atm snoop-vc interface atm 0/0/2 0 55

Interface: ATM0/0/2, Type: oc3suni

VPI = 0 VCI = 55

Status: DOWN

Time-since-last-status-change: 00:01:59

Connection-type: PVC

Cast-type: snooping-leaf

Packet-discard-option: disabled

Usage-Parameter-Control (UPC): pass

Number of OAM-configured connections: 0

OAM-configuration: disabled

OAM-states: Not-applicable

Cross-connect-interface: ATM0/1/1, Type: oc3suni

Cross-connect-VPI = 0

Cross-connect-VCI = 5

Cross-connect-UPC: pass

Cross-connect OAM-configuration: disabled

Cross-connect OAM-state: Not-applicable

Rx cells: 0, Tx cells: 0

Rx connection-traffic-table-index: 3

Rx service-category: VBR-RT (Realtime Variable Bit Rate)

Rx pcr-clp01: 424

Rx scr-clp01: 424

Rx mcr-clp01: none

Rx cdvt: 1024 (from default for interface)

Rx mbs: none

Tx connection-traffic-table-index: 3

Tx service-category: VBR-RT (Realtime Variable Bit Rate)

Tx pcr-clp01: 424

Tx scr-clp01: 424

Tx mcr-clp01: none

Tx cdvt: none

Tx mbs: none

The following example shows the VC snoop connection 0, 55 on ATM interface 0/0/2 in extended mode with FC-PFQ installed:

Switch> show atm snoop-vc interface atm 0/0/2 0 55

Interface: ATM0/0/2, Type: oc3suni

VPI = 0 VCI = 55

Status: DOWN

Time-since-last-status-change: 00:01:59

Connection-type: PVC

Cast-type: snooping-leaf

Packet-discard-option: disabled

Usage-Parameter-Control (UPC): pass

Wrr weight: 32

Number of OAM-configured connections: 0

OAM-configuration: disabled

OAM-states: Not-applicable

Cross-connect-interface: ATM0/1/1, Type: oc3suni

Cross-connect-VPI = 0

Cross-connect-VCI = 5

Cross-connect-UPC: pass

Cross-connect OAM-configuration: disabled

Cross-connect OAM-state: Not-applicable

Threshold Group: 6, Cells queued: 0

Rx cells: 0, Tx cells: 0

Tx Clp0:0, Tx Clp1: 0

Rx Clp0:0, Rx Clp1: 0

Rx Upc Violations:0, Rx cell drops:0

Rx Clp0 q full drops:0, Rx Clp1 qthresh drops:0

Rx connection-traffic-table-index: 3

Rx service-category: VBR-RT (Realtime Variable Bit Rate)

Rx pcr-clp01: 424

Rx scr-clp01: 424

Rx mcr-clp01: none

Rx cdvt: 1024 (from default for interface)

Rx mbs: none

Tx connection-traffic-table-index: 3

Tx service-category: VBR-RT (Realtime Variable Bit Rate)

Tx pcr-clp01: 424

Tx scr-clp01: 424

Tx mcr-clp01: none

Tx cdvt: none

Tx mbs: none

The following example shows all VP snoop connections on the switch:

Switch> show atm snoop-vp

Snooping Snooped

Interface VPI Type X-Interface X-VPI Dir Status

ATM0/1/2 57 PVP ATM0/0/1 57 Tx DOWN

The following example shows all VP snoop connections on ATM interface 0/1/2, VPI = 57, in extended mode with FC-PCQ (Feature Card 1) installed:

Switch> show atm snoop-vp interface atm 0/1/2 57

Interface: ATM0/1/2, Type: oc3suni

VPI = 57

Status: DOWN

Time-since-last-status-change: 00:14:46

Connection-type: PVP

Cast-type: snooping-leaf

Usage-Parameter-Control (UPC): pass

Number of OAM-configured connections: 0

OAM-configuration: disabled

OAM-states: Not-applicable

Cross-connect-interface: ATM0/0/2, Type: oc3suni

Cross-connect-VPI = 57

Cross-connect-UPC: pass

Cross-connect OAM-configuration: disabled

Cross-connect OAM-state: Not-applicable

Rx cells: 0, Tx cells: 0

Rx connection-traffic-table-index: 1

Rx pcr-clp01: 7113539

Rx scr-clp01: none

Rx mcr-clp01: none

Rx cdvt: 1024 (from default for interface)

Rx mbs: none

Tx connection-traffic-table-index: 1

Tx service-category: UBR (Unspecified Bit Rate)

Tx pcr-clp01: 7113539

Tx scr-clp01: none

Tx mcr-clp01: none

Tx cdvt: none

Tx mbs: none

The following example shows all VP snoop connections on ATM interface 0/1/2, VPI = 57, in extended mode with FC-PFQ installed:

Switch> show atm snoop-vp interface atm 0/1/2 57

Interface: ATM0/1/2, Type: oc3suni

VPI = 57

Status: DOWN

Time-since-last-status-change: 00:14:46

Connection-type: PVP

Cast-type: snooping-leaf

Usage-Parameter-Control (UPC): pass

Wrr weight: 32

Number of OAM-configured connections: 0

OAM-configuration: disabled

OAM-states: Not-applicable

Cross-connect-interface: ATM0/0/2, Type: oc3suni

Cross-connect-VPI = 57

Cross-connect-UPC: pass

Cross-connect OAM-configuration: disabled

Cross-connect OAM-state: Not-applicable

Threshold Group: 5, Cells queued: 0

Rx cells: 0, Tx cells: 0

Tx Clp0:0, Tx Clp1: 0

Rx Clp0:0, Rx Clp1: 0

Rx Upc Violations:0, Rx cell drops:0

Rx Clp0 q full drops:0, Rx Clp1 qthresh drops:0

Rx connection-traffic-table-index: 1

Rx service-category: UBR (Unspecified Bit Rate)

Rx pcr-clp01: 7113539

Rx scr-clp01: none

Rx mcr-clp01: none

Rx cdvt: 1024 (from default for interface)

Rx mbs: none

Tx connection-traffic-table-index: 1

Tx service-category: UBR (Unspecified Bit Rate)

Tx pcr-clp01: 7113539

Tx scr-clp01: none

Tx mcr-clp01: none

Tx cdvt: none

Tx mbs: none