Cisco WAN Manager User's Guide, 12.0 - Managing Connections [Cisco WAN Manager]

Table Of Contents

Managing Connections

Connection Manager Overview

Supported Connection and Card Types

Connection Modes for Configuration Management

Supported Connection Service Types

User Logins and Passwords (TACACS)

Managing with Connection Manager

Launching Connection Manager

Navigating with Connection Manager

Connection Manager Main Window

Connection Manager Menu Bar

Connection Manager Toolbar

Deleting Connections

Editing the Filter Settings

Displaying Existing Connections

Configuring a Cross Connect for VISM

Displaying the Available Entries in the Channel ID Cross Connect List

Adding a Cross Connect Entry for AAL2 Bearer

Deleting an Entry in the Channel ID Cross Connect List

Managing AutoRoute Connections (PVCs)

AutoRoute Connections (PVCs) Supported Types

Creating a PVC Connection

Creating a CESM-CESM Connection

Creating an ATM-ATM Connection

Displaying a PVC Connection

Modifying a PVC Connection

Managing PNNI Connections (SPVCs)

PNNI Connections (SPVCs) Supported Types

Creating a SPVC Connection

Displaying a SPVC Connection

Modifying a SPVC Connection

Configuring a Point-to-Multipoint Connection

Adding a P2MP Party Connection

Deleting a P2MP Party Connection

Managing a Preferred Route Connection

Preferred Route Overview

Associating a Preferred Route

Disassociating a Preferred Route

Managing XPVC Connections

Understanding XPVC Connections

Implementing XPVC

XPVC as a Migration Connection

Provisioning and Managing XPVC/XPVP

Connection Manager Support for XPVCs

XPVC Supported Connections

XPVC Platform, Card, and Connection Types

XPVC Connection Types

Creating an XPVC Connection

Configuring the XPVC Preferred Table Configurator

Adding a XPVC Entry

Deleting an XPVC Entry

Configuring the XPVC Connections

Adding an XPVC Connection

Modifying an XPVC Connection

Displaying XPVC Segments

Displaying Additional XPVC Segments

Displaying Information on a Specified XPVC Segment

Understanding Hybrid Connections

Configuring Connection Templates

Creating Connection Templates

Displaying Connection Templates

Modifying Connection Templates

Deleting Connection Templates

Configuring the Connection Descriptor

Displaying the Editable Connection Parameters

Editing the Connection Parameters

Managing Connections

This chapter describes the CWM Connection Manager (CM) application. You use Connection Manager to create and maintain end-to-end connections including permanent virtual circuits (PVCs), soft permanent virtual circuits (SPVCs), XPVCs, and Hybrid connections.

Contents of this chapter include:

•Connection Manager Overview

•Supported Connection and Card Types

•User Logins and Passwords (TACACS)

•Managing with Connection Manager

•Configuring a Cross Connect for VISM

•Managing AutoRoute Connections (PVCs)

•Managing PNNI Connections (SPVCs)

•Managing XPVC Connections

•Understanding Hybrid Connections

•Configuring Connection Templates

•Configuring the Connection Descriptor

Connection Manager Overview

You can have up to four Connection Manager windows per CM GUI instance opened from the CWM desktop application running on your workstation at any one time (though only one can be started from the CWM Desktop; the others must be started from a Connection Manager window's File menu).

The Security Management feature, which each CWM user has their own access profile, determines whether you have the rights to use each option in the CWM Connection Manager. The security mapping for CWM Connection Manager includes:

•If you have Read Permission, you can list only connections.

•If you have Create Permission, you can add new connections and perform diagnostics. In addition, you have Read Permission privileges.

•If you have Modify Permission, you can modify connections. In addition, you have Read Permission privileges.

•If you have both create and modify permissions, you can also create and modify templates.

•If you have Delete Permission, you can delete connections or templates. In addition, you have Read Permission privileges.

•If you have Multiple Delete Permission, you can delete multiple connections or templates. In addition, you have Read Permission privileges

•If you have All Permissions, you can do all of the above.

Supported Connection and Card Types

This section describes the various connections, card types, and platforms.

Table 4-1 lists the types of connection and various card types that are supported in CWM.

Table 4-1 Supported Connection and Card Types in CWM

Connection

Card

ATM

AUSM (4T1, 4E1, 8T1, 8E1)

AUSMB (8T1, 8E1)

PXM (T3, E3, OC3, OC12)

ASI (T3, E3, OC3)

ASI-155

BXM (OC3, OC12, T3, E3)

UXM

BXME (OC3, OC12)

AXSM

AXSM/B

AXSM-E

AXSM-OC3

AXSM-OC12

AXSM-OC48

AXSM-T3E3

AXSM-XG

PXM1-E

ATMRPM

RPM-PR

RPM/B

RPM-XF

Frame Relay

FRSM (4T1, 4E1, 8T1, 8E1, HS1b.V35)

FRM

UFM

FRP

FRSM-VHS

FRSM (2CT3, 2E3, 2T3, HS2)

FRSM (HS2B)

FRSM-12

Circuit Emulation

CESM (4T1, 4E1, 8T1, 8E1, T3, E3, 8T1B)

Voice/Data

CVM

UVM

CDP

VISM

CVM

UVM

HDM

LDM

SDP

LDP

VISM

VISM

VISM-PR

Table 4-2 lists the various cards supported by platform for Release 12 of CWM.

Table 4-2 Supported Cards and Platforms

Platform

Card

Cisco IGX (8410, 8420, 8430, 8450)

NPM

UXM

UXM-E

FRM

UFM U

UFM

CVM

UVM

LDM

HDM

URM

Cisco BPX (8600, 8620, 8650)

BXM (T3, E3, OC3, OC12)

BXM E (OC3, OC12)

ASI

BNI

BME

BCC

Cisco BPX-SES

PXM1 (T3, E3, OC3, OC12)

PXM1-based switches

(Cisco MGX 8850, Cisco MGX 8250, Cisco MGX 8230, and Cisco MGX 8220)

PXM1

SRM 3T3

SRM 3T3B

SRM 3T3C

SRM E

FRSM-8T1

FRSM-8E1

FRSM-8T1-C

FRSM-HS2

FRSM-HS2B

FRSM-2T3/E3

FRSM-2CT3

AUSM-8T1

AUSM-8T1/B

AUSM-8E1

CESM 8T1

CESM 8E1

CESM T3

PXM1-based switches

(Cisco MGX 8850, Cisco MGX 8250, and Cisco MGX 8230)

(continued)

CESM E3

CESM 4T1

CESM 4E1

RPM/B

RPM-PR

VISM-8T1

VISM-8E1

VISM-PR 8T1

VISM-PR 8EI

PXM1E-based switches

(Cisco MGX 8850 and Cisco MGX 8830)

PXM1E

SRM 3T3 C

SRM E

FRSM-8T1

FRSM-8T1/C

FRSM-8E1

FRSM-HS2-B

FRSM-2T3E3

FRSM-2CT3

AUSM-8T1/B

AUSM-8E1

CESM 8T1B

CESM 8E1

RPM-PR

VISM-PR

PXM45-based switches

(Cisco MGX 8850)

PXM45/A

PXM45/B

PXM45/C

AXSM-A (T3, E3, OC3, OC12)

AXSM-B (T3, E3, OC3, OC12, OC48)

AXSM-E

RPM-PR

RPM-XF

FRSM-8T1

FRSM-8E1

FRSM-2CT3

FRSM 12

CESM 8T1

CESM 8E1

VISM-PR

SRME

PXM45-based switches

(Cisco MGX 8950)

PXM45/A

PXM45/B

PXM45/C

AXSM-B (T3, E3, OC3, OC12, OC48)

AXSM-XG

RPM-PR

RPM-XF

Connection Modes for Configuration Management

This section describes the connection modes for configuration management.

The following connection modes that support CWM Connection Manager are

•Normal—Specifies normal/regular PVCs.

The following operations are

–Browse connection list

–Browse Root to Leaf connectivity for multicast

–Add a new connection

–Modify a connection

–Delete a connection

The following connection types are

–Frame Relay to Frame Relay

–ATM to ATM

–ATM to Frame Relay

–CE to CE (Circuit Emulation)

–Voice to Voice

–VISM to VISM

–VISM to ATM

–Data to Data

–ATM to CE

–RPM to RPM

–RPM to ATM

–RPM to FR

–VISM to ATM

–VISM to VISM

–VISM to RPM

•Multicast

Supported Connection Service Types

When adding a new connection from the Connection Manager application, you are asked to specify the service type and protocol (PVC, SPVC, Single-SPVC, XPVC, Single-Hybrid, or Hybrid). For a list of the various connection and connection service types, see Table 4-7 and Table 4-9.

User Logins and Passwords (TACACS)

The CWM Service Agent and Connection Manager GUI accept RPM user logins and passwords as input parameters to provision connections on the RPM card on Cisco MGX 8850 (PXM1) feeders. Both the Service Agent and Connection Manager GUI support multiple users and passwords configured on the RPM card. Currently, the Service Agent and Connection GUI require that the login and enable passwords on the RPM module are different. The maximum length of the login/enable password is increased from the current 8 characters to 25 characters.

Two new input parameters, RPM Login User Id and RPM Login Password, can be configured in the Connection Manager GUI along with Login User Id, Password, and RPM Enable Password. RPM Login User Id and RPM Login Password are not mandatory parameters; the default value of both parameters is set to NULL. However, if a user name and password are configured on the RPM card, then this information is required to provision connections.

To support RPM user logins and passwords, two new MIB objects, rpmEndPointRpmLoginUser and rpmEndPointRpmPasswd, are added to the rpmEndPointTable of the CWM Service MIB.

Note A TACACS server installed in your network is required.

Managing with Connection Manager

The following tasks are used to manage the connections:

•Launching Connection Manager

•Navigating with Connection Manager

•Deleting Connections

•Editing the Filter Settings

•Displaying Existing Connections

For information on how to test connections, see "Monitoring Network Faults," "Testing Connections" section.

Launching Connection Manager

To start Connection Manager, choose Apps > Connection Manager or click the Connection Manager button from the toolbar.

After the Connection Manager application is launched, the Connection Manager main window appears (see Figure 4-1). The Connection Manager main window displays a list of the current connections as well as the options for creating, modifying, deleting, and testing connections.

Figure 4-1 Connection Manager Main Window

1

Menu bar

2

Toolbar

3

Start node tree

4

Filter tree

5

Connections listing pane

6

Button panel

Navigating with Connection Manager

The following sections describe the navigation of connection manager:

•Connection Manager Main Window

•Connection Manager Menu Bar

•Connection Manager Toolbar

Connection Manager Main Window

The Connection Manager main window (see Figure 4-1) includes three panes:

•Upper left pane—Displays the node tree.

•Lower left pane—Displays the filter tree.

•Right-hand pane—Provides a list of existing connections along with the selected parameter values.

Note When Connection Manager is initially launched, the listing pane is empty.

The options for the Connection Manager main window are listed in Table 4-3.

Table 4-3 Connection Manager Main Window Options

Options

Task

Menu bar

For a definition, see Table 4-4.

Toolbar

For a definition, see Table 4-5.

Start Node Tree

Displays the full path of the currently selected node as discovered by CWM. The Start Node Tree shows the network equipment that is being managed by CWM. You can select any node from the hierarchy to be the current start node. The label on the top of this pane shows the current selected node.

Filter Tree

Displays the filter categories and values currently selected that enables you to select different display characteristics for existing connections.

Connections Listing Pane

Lists a subset of connections managed by CWM based on the selected start node and filter values.

Button Panel

Contains the following navigational buttons:

•Apply—Retrieves the number of connections with the selected filters.

•Refresh—Refreshes the list of connections from the Connection Server but does not apply new filters to the connections.

•Modify—Modifies connection parameters.

•Delete—Deletes the selected connections.

Connection Manager Menu Bar

The menu bar provides available menu options for the connection manager application.

The options and functions are listed in Table 4-4.

Table 4-4 Connection Manager Menu Bar

Menu-Bar Options

Task

File

New CM GUI

Opens a new instance of Connection Manager application. You can have up to four instances of the Connection Manager running at any one time on a workstation. Only one is started from the CWM Desktop; the others are started from one of the running programs.

New Connections

Displays a list of available connection types from which to select when adding a new connection. For more information, see Table 4-1.

Close

Closes the current Connection Manager main window when you are running multiple sessions of the Connection Manager. If you are running only one instance, you are returned to the CWM main menu.

Exit

Exits the Connection Manager instance and the other sessions. This option works only on the window in which the option is selected. When you have started other Connection Managers, they continue to run.

Edit

Filters

Displays the Filter Settings dialog that filters the connections using the following criteria:

•End to End Type

•Enabling Filter Categories

•Type

•Service Type

•Status

•Multicast

•Remote

•Connection Descriptor

•Endpoint Filter Levels

For filter setting definitions, see Table 4-6.

Delete Template

Displays the Delete Template dialog that is used to delete the selected templates.

View

Alarm Console

Displays the Alarm Console log.

MultiCast Group

Displays members of the MultiCast Group.

XPVC Segments

Displays the XPVC Connection and Segments window.

Search

Find Node

Displays a Find Node dialog that is used to search for a given node.

Options

Connection Status Update

Selects or deselects a connection status update option.

Show Cps params in K bps

Displays character parameters on a connection in kbps. You can turn the display on or off. The traffic parameters shown in cps are shown in kps for all connections added or modified from all the CMGUI sessions associated with the CMGUI instance.

Diagnostic

Test Connection

Tests the integrity of a connection between a card and the remote end within the WAN switching network by sending a single collection of supervisory cells to the remote end. The terminal displays only a pass or fail message.

Test Delay

Tests the integrity of an external connection by sending a single collection of supervisory cells to the remote end of the network and back. The terminal displays a pass or fail message and the round trip time in ms.

Test Connection Segment

Tests the integrity of a connection segment.

Test Ping OAM

Tests the operations, administration, and maintenance of the network using the PING program.

Connection Trace

Displays connection trace information.

Detailed Status

Displays detailed status and configuration information for a specified group.

Reroute

Displays the reroute timer settings.

Connection Up

Ups a connection for SPVC segments only.

Connection Down

Downs a connection for SPVC segments only.

Loopback Connection

Performs a loopback test on a connection.

Local Loopback

Performs a local loopback test on a FRSM12 connection.

View Cross Connect¹

Displays an established cross connect already on a PVC².

Create Cross Connect¹

Establishes a binding between a DS0 and PVC on the VISM-PR service module. The following types of cross connects are available:

•CID³ cross connect—Establishes a binding between a DS0 (endpoint) and an AAL2-bearer PVC on the VISM-PR.

•RTP⁴ cross connect—Establishes a binding between a DS0 (RTP connection) and an AAL5-bearer PVC on the VISM-PR.

•HDLC⁵ cross connect—Establishes a binding between a DS0 and an AAL5-signaling PVC.

Help

Displays the version of Connection Manager.

¹Cross connect is available for VISM-8T1/E1 and VISM-PR 8T1/E1 cards, and is applicable when VISM is running in trunk mode.

²PVC = permanent virtual circuit

³CID = channel ID

⁴RTP = routing table protocol

⁵HDLC = high-level data link control

Connection Manager Toolbar

The toolbar contains buttons that are used frequently (see Table 4-5). Move the pointer over a button to display the feature.

Table 4-5 Connection Manager Toolbar Buttons

Toolbar Options

Task

Delete Template

Deletes the selected templates.

Filters

Filters the connections that are displayed in the Connection Manager main window. By default, all connections for the selected node are displayed. For a list of the criteria under the Filter menu option, see Table 4-4.

Help

For a Help definition, see Table 4-4.

Deleting Connections

To delete a connection, complete the following procedure:

Step 1 Select the applicable connection from the Connection Manager main window.

Click Delete.

Step 2 Click OK to confirm the deleted connection.

If a successful deletion is confirmed, the notation "d" appears next to the connection number in the display table.

Step 3 Click OK to close the Delete Connections dialog window.

Step 4 Click Refresh to remove the connection from the display table.

Editing the Filter Settings

The filtering scheme defines the types of connections that are displayed in the Connection Manager main window (see Figure 4-1). By default, all connections for the selected device are displayed.

To edit the filter settings, complete the following procedure:

Step 1 Choose Edit > Filters, click the Filter button from the toolbar, or right-click on any of the categories in the filter tree.

The Filter Settings window appears (see Figure 4-2).

Figure 4-2 Filter Settings Window

Step 2 Click the applicable tabs to access the settings for a specific filter category.

Table 4-6 defines the filter settings.

Table 4-6 Filter Setting Definitions

Name

Definition

End To End Type

Defines the types of circuits for PVC, SPVC, Hybrid, Single-SPVC, Single-Hybrid, XPVC, and a dangling XPVC segment.

Enabling Filter Categories

Enables or disables the filters based on one of the eight categories.

Type

Defines one or more of the eleven basic connection types, for example, ATM-ATM, ATM-FR, and so forth.

Service Type

Defines the connection service types, for example, cbr1, vbr1_nrt, and so forth.

Status

Specifies the connection status, for example, OK, Down, Failed, Incomplete, Pending, or Error.

Multicast

Defines the multicast connection, for example, Normal, Root, or Leaf.

Remote

Enables filtering down to the port level for the remote endpoint.

Connection Descriptor

Enables filtering on the Connection Descriptor text string.

Endpoint Filter Levels

Defines whether local and feeder connections are displayed in addition to the connections that terminate at the selected node.

Displaying Existing Connections

Before you can display existing connections, you must first define the set of filters used to select a subset of all the connections currently stored in the CWM database.

To display existing connections, complete the following procedure:

Step 1 Select an object from the Node Tree pane (see Figure 4-1). The object can be either at the node, card, line, or port level.

Step 2 Expand and select a filter setting from the Filter Tree pane. For example, choose Status then Active if you want to retrieve only active connections.

Step 3 Click Apply.

The Connection Retrieval window (see Figure 4-3) appears with the number of connections matching the filtering criteria.

Figure 4-3 Connection Retrieval Window

You have the choice to display all connections associated with the selected object or just a single connection.

Step 4 Choose either Get All or Get<n> connections to list the connections in the List of Connections window.

Figure 4-4 shows the successful retrieval of connections after choosing the Get radio button and entering 100 connections in the Connections field.

If the Connection Retrieval window appears with zero connections, you can choose Get All. Any event or alarm for all newly, created connections, with at least one endpoint on the selected node, is dynamically refreshed.

Note If the newly, added connections do not have at least one endpoint on the selected node, no alarms or events are refreshed for the connections.

Figure 4-4 List of Connections Window

Click OK.

Configuring a Cross Connect for VISM

When setting up VISM connections, you must configure a cross connect for VISM.

The VISM card consists of eight T1/E1 lines. Each line contains 24 x DSOs (endpoint) per line (T1) and 31 x DS0s (E1) at 64 kbps. The Channel ID (CID) cross connect table contains a DS0 endpoint to Logical Channel Number (LCN) mapping.

Currently, CWM creates a Virtual Channel (VC) from VISM towards the network. A link must be established between a VC and each DS0 endpoint on a specific line to enable data to pass through. In Voice Over ATM (VoATM) mode, the link is established by adding a CID entry into the cross connect table. Therefore, the CID cross connect establishes a link between a DSO endpoint and a VC.

These tasks describe how to configure a CID cross connect for AAL2 Bearer processing:

•Displaying the Available Entries in the Channel ID Cross Connect List

•Adding a Cross Connect Entry for AAL2 Bearer

•Deleting an Entry in the Channel ID Cross Connect List

Note To configure a cross connect for VISM, at least one of the endpoints must be on a VISM.

Displaying the Available Entries in the Channel ID Cross Connect List

To list the available entries in the CID cross connect list, complete the following procedure:

Step 1 Right-click an existing connection from the list of connections and choose View Cross Connect or choose Diagnostic > View Cross Connect.

Figure 4-5 displays the cross connect list for AAL2 Bearer.

Figure 4-5 Cross Connect List for AAL2 Bearer

Step 2 Select the applicable CID entry from the cross connect list for AAL2 Bearer.

Step 3 Click View Detailed to display the Detailed Cross Connect for AAL2 Bearer window (see Figure 4-6).

Figure 4-6 Detailed Cross Connect for AAL2 Bearer

Adding a Cross Connect Entry for AAL2 Bearer

To add a cross connect entry for AAL2 Bearer processing, complete the following procedure:

Step 1 Right-click an existing connection from the list of connections and choose Create Cross Connect or choose Diagnostic > Create Cross Connect.

Figure 4-7 displays the Cross Connect for AAl2 Bearer configuration window.

Figure 4-7 Cross Connect for AAL2 Bearer Configuration Window

Step 2 Enter the applicable value for CID in the CID Number field.

The range is from 8-255.

Step 3 Enter the applicable endpoint value in the Endpoint Number field.

The endpoint number is the logical representation of the DS0 time slot. For example, the endpoint number maps to a DS0.

The range is from 1-248.

Step 4 Choose one of the following profile options from the Profile Type drop-down arrow:

•itu—Specifies the International Telecommunication Union (ITU) standard profiles.

•atm—Not supported.

•custom—Specifies the customized profiles that are specific to VISM.

•none—Not supported.

The default value is custom.

The AAL2 profile is used by the media gateway for the bearer traffic parameters if they are not provided by the call agent or the call agent is not involved, for example, trunking.

Step 5 Choose one of the following profile values from the Profile Number drop-down arrow:

•1—Specifies the value for ITU.

•2—Specifies the value for ITU.

•3—Specifies the value for ITU.

•7—Specifies the value for ITU.

•8—Specifies the value for ITU.

•12—Specifies the value for ITU.

•100—Specifies the value for custom.

•101—Specifies the value for custom.

•110—Specifies the value for custom.

•200—Specifies the value for custom.

The default value is 100.

Step 6 Choose one of the following codec values from the Codec Type drop-down arrow:

•g711u

•g711a

•g726r32000

•g729a

•g729ab

•clearChannel

•g726r16000

•g726r24000

•g726r40000

•g726h

•g723ah

•g7231

•g723al

•none

Step 7 Check the DTMF Transport check box to enable the Dual Tone Multi-Frequency (DTMF) transport for AAL2 CID.

Step 8 Check the CAS Transport check box to enable the Channel Associated Signaling (CAS) transport for AAL2 CID.

Note If the line signaling is CAS, the default is true. Otherwise, the default is false.

Step 9 Check the ECAN Enable check box to enable Echo Cancellation (ECAN) for AAL2 CID.

Step 10 Enter the initial Voice Activity Detection (VAD) timer value in the Initial Vad Timer field.

The range is from 250-65535. The default value is 250.

Step 11 Choose one of the following packet period values from the Packet Period drop-down arrow:

•five

•ten

•twenty

•thirty

•forty

The default value is ten.

Step 12 Check the ICS Enable check box to enable Idle Channel Suppression (ICS) for trunking. When enabled, ICS stops generating voice packets in regards to silence.

Step 13 Check the Local Cross Connect check box to enable the cross connect entry.

Step 14 Check the Add Remote Cross Connect check box to enable the cross connect entry.

Step 15 Click Apply to add the cross connect entry for AAL2 Bearer processing.

Deleting an Entry in the Channel ID Cross Connect List

To delete an entry in the CID cross connect list for AAL2 Bearer, complete the following procedure:

Step 1 Select the applicable CID entry from the cross connect list for AAL2 Bearer (see Figure 4-5).

Step 2 Click Delete to delete the CID entry from the cross connect list for AAL2 Bearer.

Managing AutoRoute Connections (PVCs)

This section describes how to manage AR connections (PVCs).

The following PVC types include:

•Single-segment—Specifies a connection between two ports on two routing nodes.

•Two-segment—Specifies one connection segment is a feeder segment that originates on a feeder node, for example, Frame Relay port Cisco MGX 8250. The second segment is a network backbone segment that connects a feeder trunk port and a user port on a routing node or nodes. The two segments are automatically linked by CWM.

•Three-segment—Specifies an additional, second feeder segment. The connection endpoints for CWM are both feeder ports.

The following tasks to manage AR connections (PVCs) include:

•AutoRoute Connections (PVCs) Supported Types

•Creating a PVC Connection

•Displaying a PVC Connection

•Modifying a PVC Connection

AutoRoute Connections (PVCs) Supported Types

This section provides the supported AR connections (PVCs) types and cards.

Table 4-7 lists the PVC connection types, which are followed by Local and Remote EndPoint Card Types. The Local and Remote Endpoints are reversed and the same rules and restrictions apply. All cards should be on a Auto Route Platform namely Cisco BPX, Cisco IGX, Cisco MGX 8220, and
Cisco MGX PXM1-based products (Cisco MGX 8230, Cisco MGX 8250, and Cisco MGX 8850).

Table 4-7 PVC Connections

Connection

CWM Service

Local Endpoint

Card Type

Remote Endpoint Card Type

Comments or Restrictions

FR-FR

with ForeSight

FR

FR

No QOS support.

FR-FR

with ForeSight

FRQOS

FR, FRQOS

QOS can be specified by ChanServType and it has to be abr (4).

FR-FR

without ForeSight

FR

FR

No QOS support.

FR-FR

without ForeSight

FRQOS

FR,
FRQOS

Following QOS specified by "ChanServType" attribute

hi_priority, ubr, nrt-vbr, rt-vbr, stdabr

ATM-FR

nrt-vbr3,
abr.fs

ATM

FR

No QOS support on FR endpoint.

ATM-FR

cbr1
ubr(1,2)
nrt-vbr(2,3)
rt-vbr(2,3)
abr.fs
abr.1
ubr(1,2)

ATM

FRQOS

QOS supported on FR endpoint, QOS chosen by CWM automatically based on service.

Some ATM endpoints may not support all service types.

See Table 4-8 for the service type restrictions on ATM endpoints.

RPM-FR

nrt-vbr3

RPM

FR

No QOS support on FR endpoint.

RPM-FR

nrt-vbr3,
ubr1,
abr1

RPM

FRQOS

QOS supported on FR endpoint; QOS chosen by CWM automatically based on service.

ATM-ATM

cbr1
nrt-vbr(1,2,3)
rt-vbr(1,2,3)
ubr(1,2)
abr.1
abr.fs

ATM

ATM

Both ATM endpoints must support the service.

See Table 4-8 for the service type restrictions on ATM endpoints.

RPM-RPM

nrt-vbr3
abr1
ubr1

RPM

RPM

—

ATM-RPM

nrt-vbr3
abr1
ubr1

ATM

RPM

—

ATM-ATM

atfst

BXM/BXM-E/UXM

BXM/BXM-E/UXM

—

ATM-FR

atfst

BXM/BXM-E/UXM

FR, FRQOS

—

ATM-FR

atftfst
atfxfst

BXM/BXM-E/UXM

UFM

UFM card must be on a routing IGX node.

ATM-ATM

cbr1
nrt-vbr(1,2,3)
ubr(1,2)
abr.1
abr.fs

ATM-Multicast

ATM-Multicast

multicast connection; local and remote port combinations: root-leaf

CE-CE

cbr1

CE

CE

Structured/unstructured; both endpoints must be either structured or unstructured with matching bandwidth

ATM-CE

cbr1

ATM

CE

CE structured or unstructured; ATM endpoint bandwidth should be equal to or greater than the CE endpoint bandwidth

Data-Data

data

DATA

DATA

The data service modules are listed in the section above.

Voice-Voice

voice

VOICE

VOICE

All voice service modules are listed in the above section except VISM is supported for this connection type.

ATM-VISM

cbr1,
nrt-vbr(1,2,3),

rt-vbr(1,2,3)

ATM

VISM

Some VISM and ATM endpoints may not support all service types.

See Table 4-8 for the service type restrictions on ATM and VISM endpoints.

VISM-VISM

cbr1,
nrt-vbr(1,2,3),

rt-vbr(1,2,3)

VISM

VISM

Some VISM endpoints do not support all service types.

See Table 4-8 for service type restrictions on VISM.

VISM-RPM

nrt-vbr3

VISM

VISM

Some VISM endpoints do not support all service types.

See Table 4-8 for service type restrictions on VISM.

Table 4-8 lists the PVC card types that belong to the various groups such as ATM, FRQOS, and so forth.

Table 4-8 PVC Card Types

Card Group

Cards on Auto Route Platform

FR

FRSM (4T1, 4E1, HS1b.V35)

FRSM-8T1/E1 with Release < 10.0.20

FRM

UFM

UFM-U

FRP

FRQOS

FRSM (2CT3, 2E3, 2T3, HS2)

FRSM-8T1/8E1 with Release >10.0.20

Chan Service Type Restrictions:

. stdabr is supported on FRSM-VHS (2CT3, 2E3, T3, HS2) cards only from version 10.2.01.

ATM

AUSM (4T1, 4E1, 8T1, 8E1)

AUSMB (8T1, 8E1)

PXM1

ASI

ASI-155

BXM

BXM-E

UXM

UXM-E

Service Type Restrictions:

•rt-VBR support is present only in AUSM-8T1/E1 from version 10.0.20, no other AUSM card supports it.

•abr.fs is not supported on PXM1 card.

•rt-VBR is not supported on ASI, ASI-155 cards.

•abr-fs from ASI family (ASI, BXM, UXM) to FRP family (FRP.FRM.UFM) maps to atfst service type.

ATM-Multicast

BME

CE

CESM (4T1,4E1,8T1,8E1,T3,E3)

RPM

RPM-B

RPM-PR

VISM

VISM

VISM-PR

Service Type Restrictions:

. rt-vbr2, rt-vbr3, nrt-vbr2, and nrt-vbr3 service types are not supported for VISM cards less than 3.0 version.

VOICE

CVM

UVM

CDP

DATA

CVM

UVM

HDM

LDM

SDP

LDP

Creating a PVC Connection

This section describes how to configure PVC connections.

The following examples are used for PVC connections:

•Creating a CESM-CESM Connection

•Creating an ATM-ATM Connection

Creating a CESM-CESM Connection

To create a CESM 8T1 and CESM 8E1, complete the following procedure:

Step 1 Choose File > New Connections > CE > New CE-CE from the Connection Manager main window.

Figure 4-8 shows the new CE-CE Connection window.

Figure 4-8 New CESM to CESM Connection Window

Step 2 Choose the ATM service type. For a circuit emulation connection, the default is cbr1.

Step 3 Choose the applicable End-To-End Type from the drop-down arrow (see Figure 4-8).

Note For a CESM connection, PVC and Hybrid are appropriate.

The following End-To-End types are

•PVC

•SPVC

•Hybrid

Step 4 Choose the applicable Port Type from the drop-down arrow for the local and remote end points.

The port type for the local end point example is Structured-8T1. The port type for the remote end point example is Structured-8E1.

Note•While choosing the port, ensure the port speed is the DS0 number (channelized) that is the same for both sides of T1 and E1.

•Verify that the CAS bits are configured to basic by viewing the CESM Category Card Channels window from CiscoView. For more information, see "Managing Devices."

Step 5 Enter the local and remote end points for the connection in the Node field or click Node to display the Equipment Selector window (see Figure 4-13).

Choose the applicable node. Click OK.

The Equipment Selector window displays the supported cards and ports for the chosen connection and end-to-end types.

Step 6 Click Next to display the default parameters for a structured 8T1/8E1 connection.

Step 7 Select the following two methods to modify the default parameters:

a. Click Load Template to use a preconfigured connection template stored in CWM.

b. Click the left arrow to display a complete list of default parameters for the connection type.

The All Parameters window is displayed that shows the default parameters for a structured 8T1/8E1 connection.

Step 8 Click Edit to modify the default parameters. You can modify any applicable parameter.

Step 9 For the Ingress UPC Parameters, modify the following default parameters for both local and remote end points:

a. Maximum buffer sizes. For the ranges, see "Managing Devices."

b. Maximum cell delay variation (CDV) Rxt ranges. For the ranges, see "Managing Devices."

c. Enable Signalling Pass Thro.... Choose no for basic CAS bits.

d. CBR clock modes drop-down arrow.

Step 10 Click the Connection Descriptor tab to add text in the text field (see Figure 4-9).

Figure 4-9 Connection Descriptor Window
The following example for the connection descriptor text is shown:
ce-ce-dallas-washington
Click OK to confirm connection descriptor text.

Step 11 Click OK to close the New Connections window after the connection is successfully added.

You have now successfully added a new connection.

Creating an ATM-ATM Connection

Once a line and port are added and configured on an AXSM card, a connection is created between two ports in the network. For more information on line and port configuration, see "Managing Devices." Creating a connection consists of associating a line and port to a VPI and VCI, and modifying the default parameters for the connection.

To create a new ATM-ATM connection, complete the following procedure:

Step 1 Choose File > New Connections > ATM > New ATM-ATM from the Connection Manager main window.

Figure 4-10 shows the new ATM-ATM Connection window.

Figure 4-10 New ATM-ATM Connection Window

Step 2 Choose the applicable service type from the drop-down arrow. The following service types are

•cbr1

•vbr.1_nrt

•vbr.2_nrt

•vbr.3_nrt

•vbr.1_rt

•vbr.2_rt

•vbr.3_rt

•abrfs

•abr1

•ubr1

•ubr2

Figure 4-11 shows the service type options.

Figure 4-11 Service Type Options

Step 3 Choose the applicable End-To-End Type from the drop-down arrow (see Figure 4-11). The following End-To-End types are

•PVC

•SPVC

•Hybrid

•XPVC

•P2MP-SPVC

Note Release 12 of CWM supports provisioning for the connection types with Cisco MGX 8850
(PXM1E and PXM45), Cisco MGX 8830 (PXM1E), and Cisco SES PNNI Controller (BXM) using Cisco BPX for Release 3 and above for single-ended SPVC (Hybrid) connections. Cisco MGX 8850 (PXM1E and PXM45), Cisco MGX 8830 (PXM1E), and Cisco SES PNNI Controller (BXM) using Cisco BPX for Release 4 and above for Point-to-Multipoint connections.

•If you want to provision single-ended connections, choose File > New Connections > ATM > New ATM-Unknown to provision single-ended SPVC connections and single hybrid connections.

•Single-ended SPVC connections are supported for ATM and Frame Relay connections. You can configure the remote parameters on the local master end of the Single-SPVC or Single-Hybrid connections.

•All cards residing on any supported feeder are supported as a single-ended hybrid connection. Virtual path connections are added only for ATM and RPM connections. RPM-PR and RPM-XF support only UBR subtype for virtual path connections.

Step 4 Enter the local and remote end points for the connection in the Node field (see Figure 4-12) or click Node to display the Equipment Selector window.

Figure 4-12 Local and Remote Node Information

The Equipment Selector window (see Figure 4-13) displays the supported cards and ports for the chosen connection, service, and end-to-end types.

Figure 4-13 Equipment Selector

Choose the applicable node. Click OK.

Step 5 Click VpiVci to enter the applicable local and remote end points for the VPI and VCI values.

Figure 4-14 shows the VpiVci Selector window with a list of all resource partitions.

The VCI range is 1—65535.

Figure 4-14 Vpi Vci Selector

Note The VCI can be an asterisk (*) to indicate the connection is a virtual path connection (so the VCI has no meaning within the network). Virtual path connections are added on ATM (RPM) endpoints only. Both endpoints are virtual path endpoints.

Step 6 Click OK.

Figure 4-15 shows the VPI and VCI values added to the VpiVci data fields.

Figure 4-15 Local and Remote Vpi and Vci Values

Step 7 Click Edit to set the VPI and VCI parameters from the All Parameters window.

Step 8 Set the PCR, SCR, CDVT0, and MBS values.

Figure 4-16 displays the PCR0+1 values entered in cps in the applicable data fields.

Figure 4-16 PCR0+1 Values Added

Step 9 After entering all the values, click OK to view parameters for your new connection from the Connection Manager main window.

Figure 4-17 displays the new connection parameter values.

Figure 4-17 New Connection Parameters Window

Step 10 To set the Connection Descriptor, choose Edit > Filters.

Click the Connection Descriptor tab from the Filter Settings window or right-click the Connection Descriptor and choose Edit Filters from the Filter Tree.

Step 11 Enter the applicable text in the text field (see Figure 4-9).

Click OK to confirm the connection descriptor text.

Step 12 Click Apply to confirm the ATM connection from the Connection Manger main window.

Step 13 Click OK to close the New Connections window after the connection is successfully added.

Figure 4-18 displays the Success-Added Connection window.

Figure 4-18 Success - Added Connection

You have now successfully added a new connection.

If you want to add further connections and build templates, click Apply to retain the new connection window.

Displaying a PVC Connection

To display a new PVC connection, for example, CE-CE connection, complete the following procedure:

Step 1 Choose CE-CE type from the Filter tree.

Step 2 Click Apply to ensure that the connection is displayed.

The new CE-CE connection is automatically displayed in the Connection Manager main window.

If you launch a new instance of the CM GUI, you can either set the filter settings for the CE-CE connection type or choose the applicable node or node, slot, and line that you provisioned and click Apply.

Modifying a PVC Connection

To modify a PVC connection, for example, CE-CE connection, complete the following procedure:

Step 1 Right-click the CE-CE connection and choose Modify from the Connection Manager main window.

Step 2 Modify the required parameters.

Step 3 Click Apply to apply the changes and not close the window.

Step 4 Click OK to modify the connection, apply the changes, and close the window.

Managing PNNI Connections (SPVCs)

This section describes how to manage SPVC connections specifically for PNNI networks.

Compared to an AR network PVC, SPVCs do not reserve bandwidth in the backbone switches when the connection is added. This happens only when data is transported across the connection. SPVCs are always searching for better paths and can dynamically reroute based on changes in traffic parameters and network failures.

The following tasks to manage PNNI connections (SPVCs) include:

•PNNI Connections (SPVCs) Supported Types

•Creating a SPVC Connection

•Displaying a SPVC Connection

•Modifying a SPVC Connection

•Deleting Connection Templates

•Configuring a Point-to-Multipoint Connection

•Managing a Preferred Route Connection

PNNI Connections (SPVCs) Supported Types

This section describes the PNNI connections (SPVCs) supported connection and card types.

Table 4-9 lists the connection types support for SPVC connections, which is followed by Local and Remote EndPoint Card Types. The Local and Remote Endpoints are reversed and the same rules and restrictions apply. All cards should be on a PNNI Platform such as Cisco BPX with SES,
Cisco MGX 8850 (PXM1E and PXM45), Cisco MGX 8950, and Cisco MGX 8830 (PXM1E).

Table 4-9 SPVC Connections

Connection

CWM Service

Local Endpoint

Card Type

Remote Endpoint Card Type

Comments or Restrictions

FR-FR

Without ForeSight

FR

FR

No ForeSight support on PNNI; chanServType on FR end can be chosen to be one of high_priority, nrt-vbr, rt-vbr, ubr and stdabr.

ATM-FR

cbr1
nrt-vbr(2,3)
rt-vbr(2,3)
ubr(1,2)
abr.1

ATM

FR

See Table 4-10 or restrictions on service types for FR endpoints and Internal and External VS/VD on ATM endpoints.

RPM-FR

nrt-vbr3
rt-vbr3
ubr1
abr1

RPM

FR

Some RPM endpoints may not support all of these Service Types.

See Table 4-10 for service type restrictions on RPM endpoints.

ATM-ATM

cbr1
nrt-vbr(1,2,3)
rt-vbr(1,2,3)
ubr(1,2)
abr.1

ATM

ATM

See Table 4-10 for restrictions on Internal and External VS/VD on ATM AXSM endpoints.

ATM-RPM

nrt-vbr3
rt-vbr3
abr-1
ubr-1

ATM

RPM

Some RPM endpoints may not support all of these service types.

See Table 4-10 for service type restrictions on RPM endpoints.

RPM-RPM

nrt-vbr3
rt-vbr3
abr1
ubr1

RPM

RPM

Some RPM endpoints may not support all of these Service Types.

See Table 4-10 for service type restrictions on RPM endpoints.

CE-CE

cbr1

CE

CE

Structured/unstructured; both endpoints must be either structured or unstructured with matching bandwidth.

ATM-CE

cbr1

ATM

CE

CE structured or unstructured; ATM endpoint bandwidth should be equal to or greater than the CE endpoint bandwidth

ATM-VISM

cbr1
nrt-vbr(1,2,3)
rt-vbr(1,2,3)

ATM

VISM

—

VISM-VISM

cbr1
nrt-vbr(1,2,3)
rt-vbr(1,2,3)

VISM

VISM

—

VISM-RPM

nrt-vbr3
rt-vbr3

VISM

RPM

Some RPM endpoints may not support all of these service types.

See Table 4-10 for service type restrictions on RPM endpoints.

Table 4-10 lists the cards that belong to the various card groups.

Table 4-10 SPVC Card Types

Card Groups

Cards

ATM

AUSM in PXM1E-based Cisco MGX 8850 and Cisco MGX 8830 switches

AXSM

AXSM-E

PXM1E

BXM applies to Cisco BPX using Cisco SES PNNI Controller

Service Type Restrictions:

Internal and External VSVD are set to enable only on AXSM-E cards for ABR.1 service type.

FR

FRSM-12

FRSM cards on PXM1-E based Cisco MGX 8850 and Cisco MGX 8830

Service Type Restrictions:

rt-vbr2, nrt-vbr2, and ubr2 service types are not supported for FRSM-12 cards.

CE

CESM cards on Cisco MGX8830 (PXM1E), Cisco MGX 8850 (PXM1E), and Cisco MGX8850 (PXM45B/C).

RPM

RPM-PR

RPM-XF in Cisco MGX 8850 (PXM1E and PXM45) and Cisco MGX8830 switches.

Service Type Restrictions:

•abr-1 is not supported for RPM-XF card.

•vbr3-rt is not supported for RPM-PR card.

VISM

VISM

VISM-PR in Cisco MGX 8850 (PXM1E and PXM45) and Cisco MGX 8830 switches.

Creating a SPVC Connection

For a SPVC connection, a connection between Frame Relay to Frame Relay is used as an example.

To create a frame relay to frame relay connection, complete the following procedure:

Step 1 Choose File > New Connections > FR > New FrameRelay> FrameRelay from the Connection Manager main window.

Figure 4-19 shows the new Frame Relay to Frame Relay connection window.

Figure 4-19 New Frame Relay to Frame Relay Connection Window

Step 2 Choose the applicable service type from the drop-down arrow. The following service types are

•Without ForeSight

Note Without ForeSight is the default.

•With ForeSight

Step 3 Choose the applicable End-to-End Type from the drop-down arrow. The following End-To-End types are

•PVC

•SPVC

•Hybrid

•XPVC

Step 4 Enter the local and remote end points for the connection in the Node field (see Figure 4-19) or click Node to display the Equipment Selector window (see Figure 4-13).

Note For FRSM cards, the port information is shown as follows: Line_number.Physical_portnumber[Logical_portnumber](PortSpeed).

•The physical port number is the start ds0 number for channelized FRSM cards.

•The logical port number is typically shown on the CLI when using the dspports command; however, CWM uses the physical port number for connection provisioning.

The Equipment Selector window (see Figure 4-13) displays the supported cards and ports for the chosen connection, service, and end-to-end types.

Choose the applicable entries. Click OK.

Step 5 Enter the Dlci range in the DLCI field or click Dlci to display the available range for the applicable local and remote end points. The valid DLCI range is 16—1023.

Step 6 Click Edit to make adjustments to the parameter values from the All Parameters window.

Step 7 Set the Ingress Policing Parameters for committed information rate (CIR) for both local and remote end points. For maximum values for both the T1 and E1 cards, see the Channels Objects table of the Managing Devices chapter (add x-ref).

Step 8 Click the Egress Queue tab to set the Egress Queue Parameters for both the local and remote endpoints of the channel service type.

Step 9 After entering all the parameters, click OK to view parameters for your new connection from the All Parameters window.

Step 10 To set the Connection Descriptor, choose Edit > Filters.

Step 11 Click the Connection Descriptor tab from the Filter Settings window or right-click the Connection Descriptor and choose Edit Filters from the Filter Tree.

Step 12 Enter the applicable text in the text field (see Figure 4-9). The following text can be used as the connection descriptor example:
fr-fr-basic-service
Click OK to confirm the connection descriptor text.

Step 13 Click OK to close the New Connections window after the connection is successfully added.

You have now successfully added a new connection.

Displaying a SPVC Connection

To display the new SPVC connection, for example, ATM-ATM connection, complete the following procedure:

Step 1 Choose ATM-ATM type from the Filter tree.

Step 2 Click Apply to ensure that the connection is displayed.

The new ATM-ATM connection is displayed in the Connection Manager main window.

Modifying a SPVC Connection

To modify a SPVC connection, for example, ATM-ATM connection, complete the following procedure:

Step 1 Right-click the applicable node and choose Modify.

Figure 4-20 displays the connection listing for P2MP-SPVC end-to-end type.

Figure 4-20 Connection Manager Listing

Step 2 Modify the required parameters.

Step 3 Click Apply to apply the changes and not close the window.

Step 4 Click OK to modify the connection, apply the changes, and close the window.

Configuring a Point-to-Multipoint Connection

The section describes how to configure point-to-multipoint (P2MP) SPVC connections.

The P2MP feature enables a Cisco BPX 8600 series, Cisco SES, Cisco MGX 8950, Cisco MGX 8830, and Cisco MGX 88850 switches to support PNNI network applications such as data and video broadcast and LAN emulation. P2MP operates only on BXM, AXSM, AXSM-B, AXSM-E, AXSM-XG, and PXM1E card types.

The following functions for P2MP include:

•Populates a new database table called party.

•Supports provisioning to add, modify, and delete P2MP connections with CBR, UBR, and rt-VBR service types only.

The following limitations for P2MP include:

•P2MP SPVC party parameters cannot be modified.

•TestDelay and TestContinuity diagnostics are not supported.

•Total number of parties per connection cannot be more than 1000.

•Total number of parties in a node cannot be more than 1000.

Table 4-11 defines the P2MP terms. A P2MP connection takes place through a single node.

Table 4-11 P2MP Terminology

Name

Definition

root

Specifies that one endpoint serves as the root of a simple tree topology and is labeled the root end point. The data traffic is uni-directional. All data flows from the root endpoint to the destination endpoints.

leaf

Specifies a connection end point on an outgoing switch interface called a leaf. At the edge of the network, the leaf represents the connection between the network and the party. SVCs are established between the root and each leaf. At the interface that hosts the leaf, the received data is forwarded to each party using AESA¹.

party

Specifies a destination endpoint is called a party. A party is an ATM end station that connects to an edge switch and receives data from the connection root. Each party is identified by an AESA.

¹AESA = ATM end station address

Adding a P2MP Party Connection

You can provision the master end node of the P2MP connections using NSAP.VPI.VCI and party reference as the index. Remote parameters for the local end cannot be set for P2MP connections.

Parties are added or deleted from the Point-to-Multipoint SPVC/Party Configuration window (see Figure 4-22).

Note You cannot make any party modifications.

To add a P2MP SPVC connection, complete the following procedure:

Step 1 Choose File > New Connections > ATM > New ATM-ATM from the Connection Manager main window (seeFigure 4-1).

Step 2 Choose cbr1 from the Service Type drop down arrow as an example.

Step 3 Choose P2MP-SPVC from the EndToEnd Type (see Figure 4-21) drop down arrow.

Figure 4-21 Point-to-Multipoint Connection: Connection Manager Window

Step 4 Select the applicable multipoint type, for example, Root and Leaf.

Step 5 Click the Node button to select the applicable node from the Equipment Selector window.

Click OK.

The Point-to-Multipoint SPVC/Party Configuration window (see Figure 4-22) appears.

Figure 4-22 Point-to-Multipoint SPVC/Party Configuration

Table 4-12 lists the P2MP party parameters.

Table 4-12 P2MP Party Parameters

Name

Definition

Root IfIndex

Specifies the rt_ifindex parameter.

No

Specifies the serial number for the number of parties for AXSM-B or AXSM-XG.

Oper Status

Specifies operational status of the party as oper_status.

Admin Status

Specifies the administrative status of the party as admin_status. The parameter is set to up, down, or reroute the parties.

NSAP.Vpi.Vci

Specifies the VPI¹ and VCI² of the root end point that the party is associated to.

Party Reference

Specifies an arbitrary integer that distinguishes between the multiple parties attached to a P2MP SPVC as party_ref.

Party NSAP Address

Specifies the ATM NSAP address of the party that contains the 20 B NSAP address of the party as p_nsap_addr.

Vpi

Specifies the VPI value of the party.

Vci

Specifies the VCI value of the party.

¹VPI = virtual path identifier

²VCI = virtual channel identifier

Step 6 From the Add Party area, enter the applicable NSAP address of the party or click the Node button to select the end point in the Equipment Selector popup window.

After selecting the end point, the NSAP address is provided in the Party NSAP Address field.

Step 7 Click Add to add the P2MP party.

Deleting a P2MP Party Connection

To delete a P2MP party connection, complete the following procedure:

Step 1 Select the applicable P2MP-SPVC party from the Point-to-Multipoint SPVC/Party Configuration window (see Figure 4-22).

Step 2 Right-click the applicable P2MP-SPVC type. Choose Delete to delete the P2MP-SPVC party type.

Managing a Preferred Route Connection

This section describes how to manage a preferred route connection.

For information about displaying provisioned preferred routes in network topology, see "Getting Started with Cisco WAN Manager," "Displaying SPVC Preferred Route" section.

The following contents include:

•Preferred Route Overview

•Associating a Preferred Route

•Disassociating a Preferred Route

Preferred Route Overview

The preferred route enables the Cisco MGX 8850 (PXM1E and PXM45), Cisco MGX 8950,
Cisco MGX 8830 (PXM1E), Cisco SES, and Cisco BPX 8600 series to specify a most desired route for an SPVC. A preferred route is also known as preferred path, specified route, or specified path.

CWM supports the option of a directed route; therefore, a preferred route is called a directed route. If the preferred route is unavailable, the connection is not routed on any alternative paths; therefore, it s declared failed. If the connection is not directed, the associated connection is routed to the preferred route. If the preferred route is not available, an alternative route is considered as per PNNI routing policies.

The provisioned preferred route is associated with a SPVC, hybrid, or XPVC connection. The preferred route for hybrid connections is shown if a preferred route exists between the local and remote routing nodes. The source and destination node IDs of the preferred route must match with the local and remote node IDs of the connection. Connection Manager associates and disassociates a preferred route for a connection. The preferred routes are displayed at the specific source node to associate or disassociate a connection.

The following functions are supported:

•Controls how the connections are routed in the network.

•Helps in overall resource allocation and distribution, redundancy planning, and overall traffic.

•Specifies a single peer group or across multiple peer groups.

•Specifies that a preferred route is provisioned only at a source node.

•Represents a list of network elements (NEs) that are part of the route. If the preferred route is through multiple peer groups, all NE nodes of the preferred route are at the lowest level of the peer groups.

•Specifies that each network element is represented by the intermediate node name and an outgoing physical trunk port, for example, slot:[bay.line]:port.

The following limitations are

•Up to twenty NEs in a preferred route.

•Only one preferred route per SPVC.

•Up to 5000 preferred routes per PXM45/PXM1E nodes.

•Up to 1000 preferred routes per Cisco SES node.

•Up to 500 different nodes that includes the source node are specified on a PXM45/PXM1E node.

•Up to 250 different nodes that includes the source node are specified on a Cisco SES node.

Associating a Preferred Route

If a preferred route is associated while adding a connection, the preferred route is taken without reroute. Connection trace verifies the preferred path. If the preferred route is associated while modifying a connection, reroute the connection is required to take the preferred path.

Note If connections are associated with that preferred route, it cannot be deleted.

To associate a preferred route while adding a connection, complete the following procedure:

Step 1 Select the PNNI Preferred Route ID field from the All Parameters pane (see Figure 4-23).

Figure 4-23 Preferred Route Association: During Connection Addition

Step 2 Click Edit to display the All Parameters window (see Figure 4-24). The preferred route parameter is listed under routing parameters.

Figure 4-24 All Parameters: Preferred Route Association

Step 3 Click PNNI Preferred Route ID to display the PNNI Preferred Route Association window
(see Figure 4-25).

Figure 4-25 PNNI Preferred Route Association

The PNNI Preferred Route Association window displays all the routes configured between the local and remote nodes.

Step 4 Select one of the applicable preferred route from the PNNI Preferred Route Association window
(see Figure 4-25).

Step 5 Click Associate to associate the applicable preferred route.

Step 6 Click Apply to apply the selections for the All Parameters window (see Figure 4-24).

Figure 4-25 shows the preferred route ID as 132 and DirectRoute flag are configured for the connection.

The default value for the PNNI preferred route ID is 0.

If the DirectRoute flag is set to true, the preferred route is available and the connection takes only the preferred route. If the preferred route is broken, the connection goes to a fail state and cannot take a PNNI routing path.

If the DirectRoute flag is set to false, the associated connection takes a preferred path if the preferred route is available. If the preferred route is broken, the connection takes the PNNI routing path.

The default value for the DirectRoute flag is false.

Disassociating a Preferred Route

To disassociate a preferred route, complete the following procedure:

Step 1 Select the applicable preferred route from the PNNI Preferred Route Association window
(see Figure 4-25).

Step 2 Click Disassociate (see Figure 4-26) to disassociate a connection that is already associated with a valid preferred route.

Figure 4-26 Disassociate a PNNI Preferred Route

Step 3 Click Apply to apply the selections for the All Parameters window (see Figure 4-24).

Figure 4-27 shows that the preferred route disassociation selects preferred route ID as 0 for the connection.

Figure 4-27 All Parameters: Preferred Route Disassociation

Managing XPVC Connections

This section describes how to manage XPVC connections.

The following tasks to manage XPVC connections include

•Understanding XPVC Connections

•Implementing XPVC

•Provisioning and Managing XPVC/XPVP

•XPVC Supported Connections

•XPVC Platform, Card, and Connection Types

•Creating an XPVC Connection

•Configuring the XPVC Preferred Table Configurator

•Configuring the XPVC Connections

•Adding an XPVC Connection

•Modifying an XPVC Connection

•Displaying XPVC Segments

•Displaying Information on a Specified XPVC Segment

Understanding XPVC Connections

The local and remote endpoint of the connection must be in different networks separated by at least one XLMI link.

The following XPVC platform combinations are supported:

•AutoRoute --> PNNI ---> AutoRoute

•AutoRoute --> PNNI or

PNNI ---> AutoRoute

•AutoRoute --> AutoRoute Feeder on PNNI or

AutoRoute Feeder on PNNI --> AutoRoute

The AutoRoute endpoints are on a routing or a feeder node. An intersection of the connection types that are supported for both PVC and SPVC are listed in Table 4-7 and Table 4-9). The following rules and restrictions apply:

•Both endpoints of the XPVC connection must support the service type. For AutoRoute endpoints, see Table 4-7: PVC Connections. For PNNI endpoints, see Table 4-9: SPVC Connections for the restrictions.

•If the ForeSight supported end is in the AutoRoute network, XPVC supports abr.fs connection service types between PNNI endpoints and Auto Route endpoints. This is called a ForeSight - ABR interworking connection where there is one congestion control loop, which is a foresight loop in the AutoRoute network. Another congestion control loop is an ABR loop in the PNNI network. The PNNI network configures the service type as ABRSTD and enables InternalVSVD if applicable.

•CWM discovers the Cisco IGX node as a feeder node for Cisco MGX 8850 (PXM1E and PXM45) or Cisco MGX 8830 (PXM1E) in a PNNI network.

•All cards on Cisco IGX and all CESM cards are not supported as XPVC endpoints in Release 12 of CWM.

Implementing XPVC

This section describes how to implement XPVC with CWM Release 12.

To implement an XPVC, complete the following procedure:

Note eXtended permanent Virtual Circuit (XPVC) also implies extended permanent virtual path (XPVP), unless the section says explicitly that one or the other is not applicable.

Step 1 Use the switch CLI to configure XLMI and ENNI on BPX and MGX ports.

eXtended Link Local Management Interface protocol (XLMI), in conjunction with the LMI Neighbor Discovery feature, enables the exchange of connection status and topology information between the BPX and MGX switches.

Refer to the Cisco WAN Switching Command Reference, Release 9.3.30 for command syntax and a detailed description of the process of configuring BPX ports to support XLMI. Refer to the Update to the Cisco MGX 8850 Routing Switch Software Configuration Guide, Release 2.1 for command syntax and a detailed description of the process of configuring Cisco MGX 8850 Release 2.1 ports to support XLMI.

Enhanced (or Friendly) Network-to-Network Interface (ENNI) links individual networks of Cisco Automatic Routing Management switches to individual networks of PNNI switches. When a port is configured to ENNI, all new SPVC/SPVPs added to that port will have the OAM segment configured as non-segment.

Note If there are already existing connections on a port, you cannot configure the port from UNI or NNI to EUNI or ENNI, or so forth. You must delete all existing connections on a port before configuring the port to ENNI or EUNI.

In a regular connection, links joining two network domains serve as segment endpoints for OAM (segment) loopback. In order for all OAM cell types to traverse end-to-end without being looped back or terminated at the ingress of the intermediate links, XPVCs and XPVPs are provisioned across ENNI networks to allow segment OAM cells to flow over end-to-end OAM segment loops for the provisioned length of the XPVC or XPVP.

Refer to the Cisco WAN Switching Command Reference, Release 9.3.30 for command syntax and a detailed description of the process of configuring BPX ports to support ENNI. Refer to the Update to the Cisco MGX 8850 Routing Switch Software Configuration Guide, Release 2.1 for command syntax and a detailed description of the process of configuring Cisco MGX 8850 Release 2.1 ports to support ENNI.

Step 2 Use the Network Browser and Topology Map to display XLMI link status.

Step 3 Right-click an XLMI link to display the XLMI trunk popup (see Figure 4-28).

Figure 4-28 Display XLMI Trunk Popup

Choose Display Trunk to display the Display Trunk window for XLMI trunks (see Figure 4-29).

Figure 4-29 XLMI Trunks Display

You can also verify the status of the ENNI ports in the Network Browser application as shown in Figure 4-30.

Figure 4-30 Verifying ENNI Ports in the Network Browser

For more information on the Network Browser application, see "Monitoring Network Faults."

Step 4 Check Active Entries in the Show xpvc preferred group field from the XPVC Preferred Table Configurator window to manually define the AR-PNNI interface(s).

Step 5 Define whether the selected BPX node should use a particular preferred node when setting up an XPVC connection.

For more information on the XPVC Preferred Table Configurator, see the "Configuring the XPVC Preferred Table Configurator" section.

Step 6 Evaluate the status of your XPVC using the end-to-end test delay diagnostic. For examples of this diagnostic tool, see "Monitoring Network Faults," "Testing Connections" section.

XPVC as a Migration Connection

An XPVC is an end-to-end virtual circuit that traverses at least one UNI or NNI interface where XLMI is enabled. Figure 4-31 displays an XPVC example that provides the first step towards migration from an existing proprietary Automatic Routing Management infrastructure toward standards-based PNNI by encompassing networks with both Automatic Routing Management and PNNI routing nodes.

Figure 4-31 Migration Connection Example

The following basic types of XPVC that you can create using CWM Release 12 include

•AR-PNNI-AR—Originates and terminates at endpoints on an Automatic Routing Management BPX switch, Cisco MGX 8220 feeder node, or Cisco MGX feeder node attached to a Cisco BPX switch. This is a three-segment (PVC to SPVC to PVC) XPVC.

•AR-PNNI—Originates at an Automatic Routing Management switch or feeder endpoint, and terminates at a PNNI endpoint on an Cisco MGX 8850 switch (or vice versa). This is a two-segment (PVC to SPVC) XPVC.

•AR-PNNI (Hybrid)—Defines a two segment XPVC with one segment in the AutoRoute network and the PNNI network but ends on a feeder attached to a PNNI node. For example, BXM (Cisco BPX node) to AUSM (Cisco MGX 8850 (PXM1) is attached to Cisco MGX 8850 (PXM45)).

Note All the AR and PNNI common parameters are provided by users for the SPVC and PVC parameters for a new established XPVC. The SCT fields for AXSM assigned values are as per recommendation.

Each XPVC segment consists of an actual virtual circuit, which is a PVC, an SPVC, or a Hybrid (feeder) VC. Each of these circuits could, in turn, comprise more than one segment if feeders are included. CWM ties together these circuits to create an end-to-end XPVC. XPVC provisioning is supported across a maximum of three networks.

In earlier releases, you could construct circuits across multiple networks that were connected with NNI interfaces. However, the NNI interface loops back the management messages (OAM segment cells) so that end-to-end management of the circuit is not possible. This problem is resolved with the proprietary ENNI interface that is supported on BXM cards in the Cisco BPX switch and on the AXSM and PXM45 cards in the Cisco MGX 8850 switches.

The following definitions for XPVC include:

•XLMI—Enables neighbor discovery between Automatic Routing Management and PNNI domains.

•ENNI—Enables end-to-end OAM cell flow, which provides end-to-end management.

Provisioning and Managing XPVC/XPVP

To provision and manage an XPVC using Cisco WAN Manager Release 12, you use:

•SNMP Service Agent.

•Connection Manager

Before creating an XPVC, you must configure the BPX and MGX ports that connect the Automatic Routing Management and PNNI networks to support XLMI and ENNI. This is done by using the switch CLI. Once you have done this, you verify the successful activation and discovery of the XLMI links through the Network Browser and by inspection of the Topology Map.

Although CWM is able to automatically discover the XLMI links, you must define manually how each BPX node, including those that are not directly attached to an MGX PNNI port, reaches the PNNI network. The XPVC Preferred Table Configurator defines the XLMI interface that XPVCs from a particular BPX switch must use to reach the PNNI network. The Configurator also includes an XPVC Preferred Flag, which you must enable on a node-basis to enable XPVC routing between two BPX nodes. For more information about the XPVC Preferred Table Configurator, see the "Configuring the XPVC Preferred Table Configurator" section.

Once you have created the XPVC by using Connection Manager, you can provision connections and also perform an end-to-end test that provides the round-trip delay on a selected connection. End-to-end test delay is also available through the SNMP service agent.

Table 4-13 summarizes the endpoint and XPVC connection types. Associated with each connection type are specifically supported service types. Refer to the Cisco WAN Manager 12 Release Notes for a complete mapping of the specific connection and service types supported.

Note•Not all service modules are supported for XPVC user endpoints in Cisco WAN Manager Release 12. Specifically, the CESM and VISM cards are not included.

•Supported cards: BXM, ASI, AUSM, FRSM, RPM/RPM-PR, ATM = ATM or RPM endpoint

Table 4-13 Supported Connections for XPVCs

End Point Type

XPVC type

ATM-ATM

FR-FR

ATM-FR

Cisco BPX Feeder¹ to Cisco BPX Feeder¹

AR-PNNI-AR

Y

Y

Y

Cisco BPX Feeder¹ to Cisco MGX R2 Feeder¹

AR-PNNI (Hybrid)

Y

Y

Y

Cisco BPX to Cisco BPX

AR-PNNI-AR

Y

—

—

Cisco BPX to Cisco MGX 8850

AR-PNNI

Y

—

—

Cisco BPX to Cisco BPX Feeder¹

AR-PNNI-AR

Y

—

Y

Cisco BPX to Cisco MGX R2 Feeder¹

AR-PNNI (Hybrid)

Y

—

Y

Cisco BPX Feeder¹ to Cisco MGX 8850

AR-PNNI

Y

—

Y

¹Cisco BPX feeder or Cisoc MGX R2 feeder = Cisco MGX 8220, Cisco MGX 8230, Cisco MGX 8250,
Cisco MGX 8850 (PXM1)

Connection Manager Support for XPVCs

The Connection Manager in Cisco WAN Manager Release 12 provides support for XPVCs. By using Connection Manager to create XPVC connections, you can:

•Filter on XPVCs and dangling segments. A dangling segment is an XPVC segment that has been discovered by Cisco WAN Manager but which is not part of an end-to-end XPVC.

•Display the parameters for XPVCs and individual XPVC segments.

•Add a new XPVC connection.

•Modify an existing XPVC connection.

•Delete an existing XPVC connection.

•Monitor alarm status for an XPVC or an individual XPVC segment.

•Deletion of dangling segments.

•End-to-end test delay.

XPVC Supported Connections

AutoRoute one, two, and three segment PVCs are transformed to two and three segment XPVCs in the following two stages:

•Deletion of PVC.

•Addition of SPVC. The SPVC of the resulting XPVC replaces, substitutes, and extends one of the routing PVC legs of the original PVC multi-segment connection.

For the ATM - ATM (AUSM-AUSM 3 segment, BXM - BXM 1 segment) PVC and SPVC routing segment is the same for all ATM service types: cbr, rt-VBR, nrt-VBR, ubr, abrstd, abrfst.

For the FR - FR (FRSM-FRSM 3 segment), with atfr PVC middle segment, the SPVC segment type is nrt-VBR.

For the FR - FR with ForeSight (FRSM-FRSM 3 segment) PVC, with atfst PVC middle segment, the SPVC segment type is abrstd.

For the ATM (cbr, rt-VBR, nrt-VBR, ubr) - FR (FRSM - BXM 2 segment, AUSM - FRSM 3 segment) PVC, the middle/routing segment is the same ATM type SPVC.

For the ATM (abrfst) - FR (FRSM - BXM 2 segment, AUSM - FRSM 3 segment) PVC, the middle/routing segment is abrstd SPVC.

For the ATM - FR with ForeSight (atfst) PVC routing segment (only 2 segment supported) the middle/routing segment is abrstd SPVC.

For the RPM-RPM (3 segment), RPM-ATM (2 or 3 segment), RPM-FR (2 or 3 segment) nrt-VBR3/ubr1/abr1, the middle segment is nrt-VBR3/ubr1/abr1.

Note ABRFST is not supported in the SPVC model; these connections are converted to Standard ABR.

XPVC Platform, Card, and Connection Types

This section describes the XPVC platform, card, and connection types.

The following platforms are supported for provisioning XPVC user endpoints:

•Cisco BPX 8600

•Cisco MGX 8220

•Cisco MGX 8230, Cisco MGX 8250

•Cisco MGX 8850 (PXM1E and PXM45), Cisco MGX 8850 (PXM1)

The following platforms are supported through nodes, but are not supported for XPVC user endpoints creation:

•Cisco IGX 8400

•Cisco MGX 8950

The following cards are supported for XPVC user endpoints:

•BXM and BXM-E

•ASI

•PXM1 and PXM1E

•AXSM

•AUSM

•FRSM

•RPM/B

•RPM-XF

•FRSM-12

•RPM-PR

The following cards are not supported as user endpoints:

•CESM

•VISM

•Cards from IGX

XPVC Connection Types

This section describes the connection types for XPVC.

The following XPVC connection types include:

•AR-PNNI-AR XPVC

•AR-PNNI

•AR-Hybrid

Table 4-14 lists two Segment XPVC services and segments.

Table 4-14 Two Segment XPVC

XPVC Service

AR Feeder Segment

AR Segment

PNNI Routing Segment

PNNI Feeder Segment

ABR - ABRFS

ABRFST

ABRFST with FCES

ABRSTD without VsVd

ABRSTD with termination

ATM-FR

ATFR

ATFR

ATM (CBR, rt-VBR, nrt-VBR, UBR)

ATM (CBR, rt-VBR, nrt-VBR, UBR)

ATM-FR ForeSight

ATFST

ATFST with FCES

ABRSTD without VsVd

ABRSTD with termination

ATM-RPM

nrt-VBR3/ubr1

nrt-VBR3/ubr1

nrt-VBR3/ubr1

nrt-VBR3/ubr1

nrt-VBR3/ubr1

ATM-RPM

abr1

abr1 with termination

abr1 without VSVD

abr1

abr1 with termination

RPM/

RPM-PR

RPM/RPM-PR

nrt-VBR3/ubr1

nrt-VBR3/ubr1

nrt-VBR3/ubr1

nrt-VBR3/ubr1

nrt-VBR3/ubr1

RPM/

RPM-PR

RPM/RPM-PR

abr1

abr1 with termination

abr1 without VSVD

abr1

abr1 with termination

RPM/

RPM-PR

FR

nrt-VBR3/ubr1

nrt-VBR3/ubr1

nrt-VBR3/ubr1

nrt-VBR3/ubr1

nrt-VBR3/ubr1

RPM/

RPM-PR

FR

abr1

abr1 with termination

abr1 without VSVD

abr1

abr1 with termination

Creating an XPVC Connection

To create and verify an XPVC or XPVP, complete the following procedure:

Step 1 Use the applicable switch CLI to perform the following tasks:

•Configure, activate, and verify the XPVC endpoints, for example, lines and ports.

–Activate XLMI on the BXM and AXSM ports.

–Activate ENNI on the XLMI links.

Step 2 Verify that the XLMI links are displayed on the Network Topology Map.

Step 3 Choose Actions > Node > XPVC Preferred Cnf to use the XPVC Preferred Table Configurator to associate BXM ports with MGX PNNI ports.

For more information about the XPVC Preferred Table Configurator, see the "Configuring the XPVC Preferred Table Configurator" section.

Step 4 If your connections are using nondefault parameters, modify the appropriate parameter file.

Step 5 Add the connection using the cwmAddConn script.

Step 6 Choose Apps > Connection Manager to launch the Connection Manager.

Step 7 Select the applicable node. Choose View > XPVC Segments.

Step 8 Test connection end-to-end round-trip delay.

Configuring the XPVC Preferred Table Configurator

The XPVC Preferred Table Configurator is a CWM application that defines the mapping between XLMI/ENNI ports on BPX nodes and the corresponding AXSM ports in the PNNI network.

The XPVC Preferred Configurator option adds, modifies, or deletes data to or from the XPVC Table Configurator. If there is no entry, then no provisioning can be done. The xpvc_preferred data is used by Connection Manager and the Proxy subsystem for the provisioning of XPVCs.

To configure the XPVC Preferred Table Configurator, complete the following procedure:

Step 1 Right-click a node and choose Node > SPVC Preferred Cnf or choose Actions > Node > XPVC Preferred Cnf to launch the XPVC Configurator.

Figure 4-32 displays the XPVC Preferred Table Configurator window.

Figure 4-32 XPVC Preferred Table Configurator

The XPVC Preferred data displays Active Entries, which are the current active entries in the xpvc_preferred table) or Inactive Entries.

Step 2 Click the Active Entries radio button from the Show xpvc preferred group field.

Note Active entries are the default.

Step 3 Click the Inactive Entries radio button from the Show xpvc preferred group field.

An inactive entry is a route that is manually deleted from the XPVC Configurator but can still be used for connections.

Note Inactive entries cannot be deleted.

Adding a XPVC Entry

To add a XPVC entry, complete the following procedure:

Step 1 Click Add Entry from the XPVC Preferred Table Configurator window (see Figure 4-32).

Figure 4-33 displays the Edit Entry window.

Figure 4-33 XPVC Edit Entry

Table 4-15 lists the parameters for the XPVC edit entry window.

Table 4-15 Parameters for XPVC Edit Entry

Name

Definition

Edge Network

Specifies either all networks or individual AR networks if CWM discovered multiple networks.

XPVC End Point Node Name

Lists all BPX nodes in the selected network(s).

Primary Link

Displays the XLMI links discovered by CWM for the applicable node.

Is Preferred

Enables the XPVC preferred flag. The protocol type is automatically assigned as XPVC, provided that all user endpoints that are selected in the AR network have a xpvc_preferred table entry with the preferred flag set.

Step 2 Choose either All Networks or Individual AutoRoute Networks from the Edge Network drop-down arrow.

Note CWM attempts XPVC provisioning on the node or its feeders, provided that all user endpoints are selected in the AR network have an Active xpvc_preferred table entry with the preferred flag set.

Step 3 Choose the applicable XPVC node from the XPVC End Point Node Name drop-down arrow.

Step 4 Choose the applicable primary link from the drop-down arrow.

Step 5 Check or uncheck the Is Preferred box.

Deleting an XPVC Entry

To delete an XPVC entry, complete the following procedure:

Step 1 Choose an active entry from the XPVC Preferred Table Configurator window.

Step 2 Click Delete.

If the XPVC connection exists, the entry is marked inactive and is displayed as Inactive Entries.

Configuring the XPVC Connections

This section describes how to configure XPVC connections.

The following XPVC connection types are supported:

•ATM-ATM

•FR-FR

•RPM-RPM

•ATM-FR

•ATM-RPM

•FR-RPM

The following tasks are

•Adding an XPVC Connection

•Modifying an XPVC Connection

•Displaying XPVC Segments

•Displaying Additional XPVC Segments

•Displaying Information on a Specified XPVC Segment

For information about deleting connections, see the "Deleting Connections" section.

For information about testing XPVC connections, see "Monitoring Network Faults," "Testing XPVC Connections" section.

Adding an XPVC Connection

This section describes how to add an XPVC connection.

To add an XPVC connection, complete the following procedure:

Step 1 Choose File > New Connections > ATM > New ATM-ATM from the Connection Manager main window.

Figure 4-34 displays the new ATM-ATM Connection Manager window for the XPVC end-to-end type.

Figure 4-34 XPVC End-to-End Type: ATM-ATM Connection

Step 2 Choose the applicable service type from the drop-down arrow. The following are the service types:

•cbr1

•vbr.1_nrt

•vbr.2_nrt

•vbr.3_nrt

•vbr.1_rt

•vbr.2_rt

•vbr.3_rt

•abrfs

•abr1

•ubr1

•ubr2

Step 3 Choose XPVC from the EndToEnd Type drop-down arrow.

Step 4 Enter the local and remote end points for the connection in the Node field (see Figure 4-12) or click Node to display the Equipment Selector window (see Figure 4-13).

Step 5 Choose the applicable node. Click OK.

Step 6 Click VpiVci to enter the applicable local and remote end points for the VPI and VCI values (see Figure 4-14).

The VCI range is 1-65535.

Click OK.

Step 7 Click Next to commit to the end points for the connection.

The All Parameters window (see Figure 4-35) displays the parameters.

Figure 4-35 New ATM-ATM Connection: XPVC Parameters

Step 8 Click Edit to set the VPI and VCI parameters from the All Parameters window.

Step 9 Set the PCR, SCR, CDVT0, and MBS values.

Step 10 After entering all the values, click OK to view parameters for your new connection from the Connection Manager main window.

Step 11 To set the Connection Descriptor, choose Edit > Filters.

Click the Connection Descriptor tab from the Filter Settings window or right-click the Connection Descriptor and choose Edit Filters from the Filter Tree.

Step 12 Enter the applicable text in the text field (see Figure 4-9).

Click OK to confirm the connection descriptor text.

Step 13 Click Apply to confirm the XPVC connection from the Connection Manger main window.

Step 14 Click OK to close the New Connections window after the connection is successfully added.

You have now successfully added a new connection.

Modifying an XPVC Connection

This section describes how to modify an existing XPVC connection.

To modify an existing XPVC connection, complete the following procedure:

Step 1 Right-click the ATM-ATM connection and choose Modify from the Connection Manager main window.

The end points and connection parameters are displayed for the selected XPVC connection.

Step 2 Modify the required parameters.

Step 3 Click Apply to apply the changes and not close the window.

Step 4 Click OK to modify the connection, apply the changes, and close the window.

Displaying XPVC Segments

The following operations that you can perform on XPVCs, which are similar to those available for SPVCs and PVCs, include:

•Sorting

•End to End XPVC Test Delay

Note This test is equivalent to the standard Test delay, but it crosses the two types of networks.

For an AR-PNNI-AR XPVC, the two end-to-end types that you can filter are XPVC and XPVC-D, which is a dangling XPVC. Dangling segments of an XPVC are complete or incomplete PVC, SPVC, or Hybrid connections that terminate on one or two ENNI ports. Since CWM cannot automatically join discovered XPVC segments, the segments remain dangling. Dangling segments, which are incomplete connections or incomplete XPVCs, are deleted only. They cannot be modified.

To display XPVC segments, complete the following procedure.

Step 1 Right-click the End-to-End Type and choose Edit Filters in the Filter Tree or choose Edit > Filters to display the Filter Settings window for either an AR-PNNI-AR XPVC or a dangling XPVC (XPVC-D).

Step 2 Edit the filter settings to set the end-to-end type to XPVC (see Figure 4-2).

Click OK.

Step 3 Ensure the end-to-end type is XPVC from the XPVC Connection & Segments window (see Figure 4-37 or Figure 4-36).

Figure 4-36 XPVC Display Expanded

Figure 4-37 XPVC Segments

Step 4 Edit the filter settings to set the end-to-end type to Dangling Segments of XPVC (see Figure 4-38).

Figure 4-38 Filter Settings, Dangling Segments of XPVC

Click OK.

Step 5 Repeat Step 3.

Displaying Additional XPVC Segments

You can also view additional information relating to the individual XPVC segments.

To display additional XPVC segments, complete the following procedure:

Step 1 Choose an XPVC in the Connection Manager main window to view additional information relating to the individual XPVC segments.

Step 2 Choose View > XPVC Segments to activate the Segment View GUI.

The following information is displayed:

•The XLMI links for the XPVC. Primary links are displayed only in this screen. The secondary links are not currently supported.

•The status of the end-to-end XPVC in the first line of the Connection and Segments pane.

•The status and endpoint type of each of the two or three XPVC segments that constitute the end-to-end connection.

Displaying Information on a Specified XPVC Segment

With Release 12 of Cisco WAN Manager you can also view additional information relating to the individual XPVC segments.

To display information on a specified XPVC segment, complete the following procedure:

Step 1 Choose an XPVC in the Connection Manager main window.

Step 2 Right-click the applicable connection (see Figure 4-40) or choose View > XPVC Segments to activate the Segment View GUI (see Figure 4-39).

Figure 4-39 Choose XPVC Segment Pull-down

Figure 4-40 Choose XPVC Segment Popup

The following information that is displayed includes:

•The XLMI links for the XPVC.

•The status of the end-to-end XPVC in the first line of the Connection and Segments pane.

•The status and endpoint type of each of the two or three XPVC segments that constitute the end-to-end connection. Figure 4-37 lists the three segments for an AR-PNNI-AR XPVC.

Understanding Hybrid Connections

The hybrid connection helps to facilitate the phased migration of existing AR networks to PNNI.
For example, an existing network can have a core of AR switching nodes with many feeder nodes attached. A service provider can transition their network to PNNI without disrupting the user facilities that can replace the core switches with PNNI-enables devices while keeping the feeder nodes intact.

The local and remote endpoint of the connection must be within the same network.

The following hybrid platform combinations are supported:

•AutoRoute Feeder on PNNI -> PNNI or

PNNI --> AutoRoute Feeder on PNNI

•AutoRoute Feeder on PNNI --> PNNI ---> AutoRoute Feeder on PNNI

The following types of hybrid connections include

•AR PVC feeder segment(s)

•PNNI network backbone segment

An intersection of all connection types that are supported are listed in Table 4-7: PVC Connections and Table 4-9: SPVC Connections. The following rules and restrictions apply:

•Both endpoints of the hybrid connection must support the service type. For AutoRoute endpoints, see Table 4-7: PVC Connections. For PNNI endpoints, see Table 4-9: SPVC Connections for the restrictions.

•Since PNNI platform does not support ForeSight, no foresight service types are supported for two segment hybrid connections.

Configuring Connection Templates

You can configure templates for the new or modified connection parameters. A template is a set of connection parameters for a specified connection, for example, ATM-ATM connection. CWM provides templates with default settings for all supported connection types. You can use the default templates unchanged, or modify a template and save it under a new name for later use.

The following tasks to configure connection templates include:

•Creating Connection Templates

•Displaying Connection Templates

•Modifying Connection Templates

•Deleting Connection Templates

Creating Connection Templates

To create connection templates, complete the following procedure:

Step 1 Click Save Template from the New Connections window (see Figure 4-41) to save a template that contains the new connection parameters.

Figure 4-41 displays the Save To Template window.

Figure 4-41 Save to Template Dialog Window

Step 2 Enter a name for your template in the Template Name field.

Step 3 Click OK to display the Success-Created template window (see Figure 4-42).

Figure 4-42 Success—Created Template Dialog Window

Step 4 Click Load Template from the New Connections window (see Figure 4-16) to load a template once the endpoints are selected and both contain the same combination of card types.

Figure 4-43 displays the Select Template window.

Figure 4-43 Select Template Dialog Window

Step 5 Select the applicable template.

Step 6 Click Load to load the template.

Figure 4-44 displays the Informational Message Dialog to announce that the template is successfully loaded. All the committed parameters are stored in the template for the connection.

Figure 4-44 Successfully Loaded Template Dialog Window

Step 7 After you saved and loaded the template that contains the new connection parameters, click OK.

The Success - Added Connection window (see Figure 4-18) appears to announce that a new connection is added.

Displaying Connection Templates

This section describes how to display connection templates.

To display connection templates, complete the following procedure:

Step 1 Click Load Template to display all the templates that are applicable for that connection from the New Connections window (see Figure 4-16).

Step 2 Click Load to display the parameters that are applicable for the connection template (see Figure 4-43).

Modifying Connection Templates

This section describes how to modify connection templates.

To modify connection templates, complete the following procedure:

Step 1 From the list of templates in the Select Template window (see Figure 4-43), click Load to load the template to be modified.

Step 2 Modify the applicable parameters.

Step 3 After you saved and loaded the template with the modified parameters, click OK.

Deleting Connection Templates

To delete templates, complete the following procedure:

Step 1 Choose Edit > Delete Template or click Delete Template from the toolbar.

Figure 4-45 displays the Delete Templates window to delete any template that has already been successfully loaded.

Figure 4-45 Delete Templates Dialog Window

Step 2 Select the applicable template to delete.

Click Delete.

Configuring the Connection Descriptor

The connection descriptor is independently configurable at each end of a connection. The following example is shown:
Character Limitations: None. Range: 
The maximum length for the descriptor is 64 characters. You cannot enter any length '^' character that is reserved and it cannot be used in the descriptor.

The following tasks include:

• Displaying the Editable Connection Parameters

•Editing the Connection Parameters

Displaying the Editable Connection Parameters

To display the editable connection parameters, complete the following procedure:

Step 1 Choose the applicable node.

Step 2 Click Apply to display connections and the status of connections for the selected node.

Step 3 Choose a connection with a status of "O.K."

Step 4 Click Modify to bring up a modification window for the selected connection.

The Modify Connection window displays information about the selected connection and editable parameters.

Click the right and left arrows to expand or collapse the Modify Connection and All Parameters windows.

Editing the Connection Parameters

To edit the connection parameters, complete the following procedure:

Step 1 Choose the parameter that you want to edit.

Click Edit from the All Parameters window.

The Edit screen appears with all editable parameters.

Step 2 Make any necessary changes.

Click Apply to save all the values. Click OK to return to the Modify Connection screen.

Step 3 After applying modifications to a connection, click Save Template to save changes to a connection template for later use.

To retrieve a previously modified connection template, click Load Template.