|
|
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.
Note This chapter provides advanced configuration instructions for the Catalyst 8540 MSR, Catalyst 8510 MSR, and LightStream 1010 ATM switch routers. For an overview of virtual connection types and applications, refer to the Guide to ATM Technology. For complete descriptions of the commands mentioned in this chapter, refer to the ATM Switch Router Command Reference publication.
The tasks to configure virtual connections are described in the following sections:
This section lists the various virtual connections (VC) types in Table 6-1.
| Connection | Point-to- Point |
Point-to- Multipoint |
Transit | Terminate |
|---|---|---|---|---|
This section describes configuring virtual channel connections (VCCs) on the ATM switch router. 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.
An end-to-end VCC, as shown in Figure 6-1 between user A and user D, has two parts:
The common endpoint between an internal connection and a link occurs at the switch interface. The endpoint of the internal connection is also referred to as a connection leg or half-leg. A cross-connect connects two legs together.
To configure a point-to-point VCC, perform the following steps, beginning in global configuration mode:
| Step | Command | Purpose |
|---|---|---|
| 1 | ||
| 2 | atm pvc vpi-A [vci-A | any-vci1] [rx-cttr index] [tx-cttr index] interface atm card/subcard/port[.vpt#] vpi-B [vci-B | any-vci] |
| 1The any-vci parameter is only available for interface atm0. |
Note The row index for rx-cttr and tx-cttr must be configured before using this optional parameter. See the section "Configuring the Connection Traffic Table" in the chapter "Configuring Resource Management."
Note When configuring PVC connections, begin with lower VCI numbers. Using low VCI numbers allows more efficient use of the switch fabric resources.
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 0/0/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.
Note The above examples show how to configure cross-connections using one command. This is the preferred method, but it is also possible to configure each leg separately, then connect them with the atm pvc vpi vci interface atm card/subcard/port vpi vci command. This alternative method requires more steps, but might be convenient if each leg has many additional configuration parameters or if you have configured individual legs with SNMP commands and you want to connect them with one CLI command.
To show the VCC configuration, use the following EXEC commands:
| Command | Purpose |
|---|---|
The following example shows the Switch B PVC configuration on ATM interface 3/0/1:
The following example shows the Switch B PVC configuration on ATM interface 3/0/1:
The following example shows the Switch B PVC configuration on ATM interface 3/0/1, VPI = 0, VCI = 50, with the switch processor feature card installed:
This section describes configuring point-to-point and point-to-multipoint terminating PVC connections. Terminating connections provide the connection to the ATM switch router's route processor for LAN Emulation (LANE), IP over ATM, and control channels for Integrated Local Management Interface (ILMI), signalling, 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 atm0 to connect to the route processor.
Note With this release of the system software, addressing the interface on the processor (CPU) has changed. The ATM interface is now called atm0, and the Ethernet interface is now called ethernet0. The old formats (atm 2/0/0 and ethernet 2/0/0) are still supported.
To configure both point-to-point and point-to-multipoint terminating PVC connections, perform the following steps, beginning in global configuration mode
| 1The any-vci feature is only available for interface atm0. |
:
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.
Note The row index for rx-cttr and tx-cttr must be configured before using this optional parameter. See the section "Configuring the Connection Traffic Table" in the chapter "Configuring Resource Management."
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 route processor interface atm0, VPI = 0, and VCI unspecified:
The following example shows how to configure the route processor leg of any terminating PVC:
When configuring the route processor 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.
Note If configuring a specific VCI value for the route processor leg, select a VCI value higher than 300 to prevent a conflict with an automatically assigned VCI for well-known channels if the ATM switch router reboots.
To display the terminating PVC configuration VCs on the interface, use the following EXEC command:
| Command | Purpose |
|---|---|
See the section "Displaying VCCs" for examples of the show atm vc commands.
This section describes configuring a PVP connection. Figure 6-3 shows an example of PVPs configured through the ATM switch routers.
To configure a PVP connection, perform the following steps, beginning in global configuration mode:
| Step | Command | Purpose |
|---|---|---|
| 1 | ||
| 2 | atm pvp vpi-A [rx-cttr index] [tx-cttr index] interface atm card/subcard/port vpi-B |
Note The row index for rx-cttr and tx-cttr must be configured before using this optional parameter. See the section "Configuring the Connection Traffic Table" in the chapter "Configuring Resource Management."
Note When configuring PVP connections, begin with lower VPI numbers. Using low VPI numbers allows more efficient use of the switch fabric resources.
The following example shows how to configure the internal cross-connect PVP within Switch B between interfaces 4/0/0, VPI = 30, and interface 1/1/1, VPI = 45:
The following example shows how to configure the internal cross-connect PVP within Switch C between interfaces 0/1/3, VPI = 45, and interface 1/1/0, VPI = 50:
Each subsequent PVP cross connection and link must be configured until the VP is terminated to create the entire PVP.
To show the ATM interface configuration, use the following EXEC command:
The following example shows the PVP configuration of Switch B:
The following example shows the PVP configuration of Switch B with the switch processor feature card installed:
This section describes configuring point-to-multipoint PVC connections. In Figure 6-4, cells entering the ATM switch router 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 figure.
Note If desired, one of the leaf points can terminate in the ATM switch router at the route processor interface atm0.
To configure the point-to-multipoint PVC connections shown in Figure 6-4, perform the following steps, beginning in global configuration mode:
| Step | Command | Purpose |
|---|---|---|
| 1 | ||
| 2 | atm pvc vpi-A vci-A [cast-type type-A] [rx-cttr index] [tx-cttr index] interface atm card/subcard/port[.vpt#] vpi-B vci-B [cast-type type-B] |
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.
Note The row index for rx-cttr and tx-cttr must be configured before using this optional parameter. See the section "Configuring the Connection Traffic Table" in the chapter "Configuring Resource Management."
The following example shows how to configure the root-point PVC on ATM switch router interface 0/0/0, VPI = 50, VCI =100, to the leaf-point interfaces (see Figure 6-4):
To display the point-to-multipoint PVC configuration, use the following EXEC mode command:
| Command | Purpose |
|---|---|
The following example shows the PVC configuration of the point-to-multipoint connections on ATM interface 0/0/0:
The following example shows the VC configuration on interface 0/0/0, VPI = 50, VCI = 100, with the switch processor feature card installed:
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 ATM switch router at the root point (the left side at interface 4/0/0), VPI = 50, are duplicated and switched to the leaf points (output interfaces), on the right side of the figure.
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.
Note The row index for rx-cttr and tx-cttr must be configured before using this optional parameter. See the section "Configuring the Connection Traffic Table" in the chapter "Configuring Resource Management."
The following example shows how to configure the root-point PVP on ATM switch router interface 4/0/0, VPI = 50, to the leaf point interfaces 1/1/1, VPI = 60, 3/0/0, VPI = 70, and 3/0/3, VPI = 80 (see Figure 6-5):
To display the ATM interface configuration, use the following EXEC command:
The following example shows the PVP configuration of the point-to-multipoint PVP connections on ATM interface 4/0/0:
The following example shows the PVP configuration of the point-to-multipoint PVP connections on ATM interface 4/0/0 VPI = 50 with the switch processor feature card installed:
This section describes configuring soft PVC connections, which provide the following features:
Figure 6-6 illustrates the soft PVC connections used in the following examples.
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 Retrieve the ATM address of the destination end of the soft PVC using the show atm address command.
Step 4 Retrieve the VPI/VCI values for the circuit using the show atm vc command.
Step 5 Configure the source (active) end of the soft PVC. At the same time, complete the soft PVC setup using the information derived from Step 3 and Step 4. Be sure to select an unused VPI/VCI value (one that does not appear in the show atm vc display).
To configure a soft PVC connection, perform the following steps, beginning in privileged EXEC mode:
Note The row index for rx-cttr and tx-cttr must be configured before using this optional parameter. See the section "Configuring the Connection Traffic Table" in the chapter "Configuring Resource Management."
The following example shows 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/2, source VPI = 0, VCI = 1000; and Switch C, destination VPI = 0, VCI = 1000 with a specified ATM address (see Figure 6-6):
To display the soft PVC configuration at either end of a ATM switch router, use the following EXEC commands:
| Command | Purpose |
|---|---|
The following example shows the soft PVC configuration of Switch B, on interface 0/0/2 out to the ATM network:
The following example shows the soft PVC configuration of Switch C, on interface 1/1/1 out to the ATM network:
The following example shows the soft PVC configuration of Switch B, on interface 0/0/2, VPI = 0, VCI = 1000 out to the ATM network with the switch processor feature card installed:
To display a soft PVC connection successfully routed over an explicit path, use the following EXEC command:
| Command | Purpose |
|---|---|
Displays the soft PVC connection status including the PNNI explicit path routing status for the last setup attempt. |
The following example shows the last explicit path status for a soft PVC using the show atm vc interface EXEC command. Note that the first listed explicit path new_york.path2 shows an unreachable result, but the second explicit path new_york.path1 succeeded.
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:
The row index for rx-cttr and tx-cttr must be configured before using this optional parameter. See the section "Configuring the Connection Traffic Table" in the chapter "Configuring Resource Management."
The following example shows how to configure a soft PVP on Switch B between interface 0/0/2, source VPI = 75, and Switch C, destination VPI = 75, with a specified ATM address (Figure 6-7):
To display the ATM soft PVP configuration, use the following EXEC command:
The following example shows the soft PVP configuration at Switch B, on interface 0/0/2 out to the ATM network:
The following example shows the soft PVP configuration on interface 1/1/1 at Switch C out to the ATM network:
The following example shows the soft PVP configuration at Switch B on interface 0/0/2, VPI = 75, out to the ATM network with the switch processor feature card installed:
This section describes the soft PVP or soft PVC route optimization feature. Most soft PVPs or soft PVCs have a much longer lifetime than SVCs. The route chosen during the soft connection setup remains the same even though the network topology might change.
Soft 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 "Configuring the Global Administrative Weight Mode" in the chapter "Configuring ATM Routing and PNNI."
Configuring soft PVP or soft PVC route optimization is described in the following sections:
For overview information about the route optimization feature refer to the Guide to ATM Technology.
Soft PVP or 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 route optimization, use the following global configuration command:
The following example enables route optimization and sets the threshold percentage to
85 percent:
Soft PVP or 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/PVP interface with route optimization, perform the following steps, beginning in global configuration mode:
The following example shows how to configure an interface with a route optimization interval configured as every 30 minutes between the hours of 6:00 P.M. and 5:00 A.M.:
To display the interface route optimization configuration, use the following EXEC command:
| Command | Purpose |
|---|---|
show atm interface [atm card/subcard/port | serial card/subcard/port:cgn] |
Shows the interface configuration route optimization configuration. |
The following example shows the route optimization configuration of ATM interface 0/0/0:
Normally the default well-known VCs are automatically created with default VCIs. However, for the unusual instances where the ATM switch router interfaces with nonstandard equipment, you can configure nondefault well-known VCI values on a per-interface basis.
For overview information about the well-known PVCs refer to the Guide to ATM Technology.
Table 6-2 lists the default well-known VCs and their default configuration.
Table 6-2 Well-Known Virtual Channels
| Channel Type | Virtual Path Identifier | Virtual Channel Identifier |
|---|---|---|
| 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. |
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 the running-configuration file to the startup-configuration file.
To configure the nondefault VCs for signalling, ILMI, and PNNI, perform the following steps, beginning in global configuration mode:
Note An error condition occurs if either the signalling or ILMI well-known VCs remain unconfigured when an interface is enabled.
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 signalling from 5 (the default) to 35 using the atm pvc 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.
An example of this procedure follows:
Normally, soft PVCs and soft PVPs are automatically routed by PNNI over paths that meet the traffic parameter objectives. However, for cases where manually configured paths are needed, PNNI explicit paths can optionally be specified for routing the soft PVC or soft PVP. For detailed information on configuring PNNI explicit paths, refer to the section "Configuring Explicit Paths" in the chapter "Configuring ATM Routing and PNNI."
The explicit paths are assigned using precedence numbers 1 through 3. The precedence 1 path is tried first and if it fails the soft connection is routed using the precedence 2 path and so forth. If all of the explicit paths fail, standard on-demand PNNI routing is tried unless the only-explicit keyword is specified.
If the soft connection destination address is reachable at one of the included entries in an explicit path, any following entries in that path are automatically disregarded. This allows longer paths to be reused for closer destinations. Alternatively, the upto keyword can be specified for an explicit path in order to disregard later path entries.
The following example shows how to configure a soft PVC between ATM switch router dallas_1 and an address on ATM switch router new_york_3 using either of the two explicit paths new_york.path1 and new_york.path2. If both explicit paths fail, the ATM switch router uses PNNI on-demand routing to calculate the route.
Explicit paths can be added, modified or removed without tearing down existing soft PVCs by using the redo-explicit keyword. Only the source VPI and VCI options need to be specified. All applicable explicit path options are replaced by the respecified explicit path options.
The soft PVC is not immediately rerouted using the new explicit path. However, reroutes using the new explicit path can happen for the following four reasons:
1. A failure occurs along the current path.
2. The EXEC command atm route-optimization soft-connection is entered for the soft PVC.
3. route-optimization is enabled and the retry time interval has expired.
4. The soft PVC is disabled and then reenabled using the disable and enable keywords.
The following example shows how to change the explicit path configuration for an existing soft PVC on the ATM switch router dallas_1 without tearing down the connection. The new configuration specifies the two explicit paths, new_york.path3 and new_york.path4, and uses the only-explicit option.
Note The configuration displayed for soft connections with explicit paths is always shown as two separate lines using the redo-explicit keyword on the second line, even if it is originally configured using a single command line.
You can configure a virtual path identifier/virtual channel identifier (VPI/VCI) range for switched virtual circuits and switched virtual paths (SVCs and SVPs). ILMI uses the specified range to negotiate the VPI/VCI range parameters with peers. This feature allows you to:
You can still configure PVPs and PVCs in any supported range, including any VPI/VCI range you configured for SVPs/SVCs.
The default maximum switched virtual path connection (SVPC) VPI is equal to 255. You can change the maximum SVPC VPI by entering the atm svpc vpi max value command. See Table 6-3 for the allowable ranges.
Table 6-3 Maximum SVPC VPI Range Note The maximum value specified applies to all interfaces except logical interfaces, which have
a fixed value of 0.
For further information and examples of using VPI/VCI ranges for SVPs/SVCs, refer to the Guide to ATM Technology.
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:
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.
To confirm the VPI or VCI range configuration, use one of the following commands:
The following example shows how to confirm the VPI and 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.
The following example shows how to confirm the peer's local values for VPI and VCI range configuration by displaying the ILMI status on an ATM interface:
Note Note that the show atm ilmi-status command displays the information above only if the peer
supports it.
This section describes configuring virtual path (VP) tunnels, which provide the ability to interconnect ATM switch routers across public networks using PVPs. 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.
Figure 6-8 shows a public UNI interface over a DS3 connection between the ATM switch router (HB-1) in the Headquarters building and the ATM switch router (SB-1) in the Remote Sales building. To support signalling across this connection, a VP tunnel must be configured.
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.
To configure a VP tunnel connection for a single service category, perform the following steps, beginning in global configuration mode:
Note The row index for nondefault rx-cttr and tx-cttr must be configured before these optional
parameters are used.
The following example shows how to configure the ATM VP tunnel on the ATM switch router (HB-1) at interface 1/0/0, VPI 99:
The following example shows how to configure the ATM VP tunnel on the ATM switch router (SB-1) at interface 0/0/0, VPI 99:
To show the ATM virtual interface configuration, use the following EXEC command:
The following example shows the ATM virtual interface configuration for interface 1/0/0.99:
This section describes configuring a shaped VP tunnel for a single service category with rate-limited tunnel output on a switch.
A shaped VP tunnel is configured as a VP of the CBR service category. By default, this tunnel can carry VCs only of the CBR service category. However, you can 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.
Note Shaped VP tunnels are supported only on systems with the FC-PFQ feature card.
(Catalyst 8510 MSR and LightStream 1010)
A shaped VP tunnel is defined as a CBR VP with a PCR. The following limitations apply:
To configure a shaped VP tunnel, perform the following steps, beginning in global configuration mode:
The following example shows how to configure a shaped VP tunnel with a VPI of 99 as ATM interface 0/0/0.99
To display the shaped VP tunnel interface configuration, use the following EXEC command:
For an example display from the show atm interface command, see the section "Displaying the Hierarchical VP Tunnel Configuration."
This section describes configuring a hierarchical VP tunnel for multiple service categories with rate-limited tunnel output.
A hierarchical VP tunnel 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. 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. See the section "Configuring VC Merge" in the chapter "Configuring Tag Switching."
Service categories supported include the following:
Note Hierarchical VP tunnels are supported only on systems with the FC-PFQ feature card.
(Catalyst 8510 MSR and LightStream 1010)
While capable of carrying any traffic category, a hierarchical VP tunnel is itself defined as CBR with a PCR. The following limitations apply on the Catalyst 8540 MSR:
The following limitations apply on the Catalyst 8510 MSR and LightStream 1010:
The following limitations apply on the Catalyst 8540 MSR, Catalyst 8510 MSR and LightStream 1010:
Before configuring a hierarchical VP tunnel, you must first enable hierarchical mode, then reload the ATM switch router. Perform the following steps, beginning in global configuration mode:
Note Enabling hierarchical mode causes the minimum rate allocated for guaranteed bandwidth to
a connection to be increased.
The following example shows how to enable hierarchical mode, then save and reload the configuration.
To configure a hierarchical VP tunnel, perform the following steps, beginning in global configuration mode:
The following example shows how to configure a hierarchical VP tunnel with a PVP of 99 as ATM interface 0/0/0.99
To display the hierarchical VP tunnel interface configuration, use the following EXEC command:
The following example shows the VP tunnel configuration on interface ATM 1/0/0 with PVP 99.
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:
The following restrictions apply to an end point of a PVC-to-PVP tunnel subinterface:
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:
To confirm PVC interface configuration, use the following EXEC command:
The following example shows the configuration of ATM subinterface 1/0/0.99 on the ATM switch router Switch(HB-1):
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.
This feature can also be used to support connections over a virtual UNI.
To configure a VP tunnel connection signalling VPCI, perform the following steps, beginning in global configuration mode:
The following example configures a VP tunnel on ATM interface 0/0/0, PVP 99, and then configures the connection ID VCPI as 0.
To confirm the VP tunnel VPCI configuration, use the following privileged EXEC command.
To delete a VP tunnel connection, perform the following steps, beginning in global configuration mode:
The following example shows deleting subinterface 99 at ATM interface 1/0/0 and the
To confirm the ATM virtual interface deletion, use the following EXEC command:
The following example shows that ATM subinterface 1/0/0.99 on the ATM switch router-1 (HB-1) has been deleted:
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.
Note Only cells that belong to existing connections are sent to the snoop test port. Any received
cells that do not belong to existing connections are not copied. In addition, the STS-3c (or other)
overhead bytes transmitted at the test port are not copies of the overhead bytes at the monitored port.
With the FC-PCQ installed, only the highest port on the last module in the ATM switch router can be configured as a snoop test port. Table 6-4 lists the interface number of the allowed snoop test port for the various port adapter types. If you specify an incorrect snoop test port for the currently installed port adapter type, an error appears on the console. The FC-PCQ also does not support per-connection snooping.
The port number of the test port depends on the card type. Table 6-4 lists the allowed snoop test port number for the supported interfaces.
Table 6-4 Allowed ATM Snoop Ports with FC-PCQ
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 port adapter type with a bandwidth less than or equal to the port adapter bandwidth for the test port can be monitored by snooping.
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 signalling 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:
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:
The atm snoop interface atm command enables a snoop test port. 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:
The following example shows how to configure ATM interface 12/1/3 as the port in snoop mode to monitor ATM interface 3/0/0, tested in the receive direction:
To display the test port information, use the following EXEC command:
The following example shows the snoop configuration on the OC-3c port and the actual register values for the highest interface:
With per-connection snooping you must specify both the snooped connection endpoint and the snooping connection endpoint. The 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:
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.
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:
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:
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:
To display the test per-connection information, use the following EXEC commands:
The following example shows all VC snoop connections on the ATM switch router:
The following example shows the VC snoop connections on ATM interface 0/1/2:
The following example shows the VC snoop connection 0, 55 on ATM interface 0/0/2 in extended mode with the switch processor feature card installed:
The following example shows all VP snoop connections on the ATM switch router:
The following example shows all VP snoop connections on ATM interface 0/1/2, VPI = 57, in extended mode with the switch processor feature card installed:
VPI Bit Type
Maximum Value Range
1Only available on ATM NNI interfaces.
Step
Command
Purpose
1
2
3
4
Displaying the VPI/VCI Range Configuration
Command
Purpose
Examples
Configuring VP Tunnels
Figure 6-8 Public VP Tunnel Network Example
Configuring a VP Tunnel for a Single Service Category
Examples
Displaying the VP Tunnel Configuration
Command
Purpose
Configuring a Shaped VP Tunnel
Configuring a Shaped VP Tunnel on an Interface
Example
Displaying the Shaped VP Tunnel Configuration
Command
Purpose
Configuring a Hierarchical VP Tunnel for Multiple Service Categories
Enabling Hierarchical Mode
Example
Configuring a Hierarchical VP Tunnel on an Interface
Example
Displaying the Hierarchical VP Tunnel Configuration
Command
Purpose
Example
Configuring an End-Point PVC to a PVP Tunnel
Example
Displaying PVCs
Command
Purpose
Example
Configuring Signalling VPCI for VP Tunnels
Step
Command
Purpose
1
2
Example
Displaying the VP Tunnel VPCI Configuration
Deleting VP Tunnels
Step
Command
Purpose
1
2
3
Example
PVP half-leg 99:
Confirming VP Deletion
Command
Purpose
Example
Configuring Interface and Connection Snooping
Snooping Test Ports (Catalyst 8510 MSR and LightStream 1010)
Interface
Port Number
1Both transmit and receive interfaces must be on 25-Mbps port adapters.
Effect of Snooping on Monitored Port
Shutting Down Test Port for Snoop Mode Configuration
Other Configuration Options for Snoop Test Port
Caution
You should ensure that all options are valid and configured correctly while in the snoop mode. Configuring Interface Snooping
Example
Displaying Interface Snooping
Example
Configuring Per-Connection Snooping
Examples
Displaying Per-connection Snooping
Examples
Posted: Wed Jan 22 01:40:43 PST 2003
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
