Table Of Contents
Migration From Automatic Routing Management to PNNI Using Cisco WAN Manager
Upgrade Cisco WAN Manager from 10.x to 11.
Preparing To Upgrade Cisco BPX Switch Software From 9.2.34 to 9.3.30
Gracefully Upgrading the BCC Card Pair on the BPX node
Gracefully Upgrading the Rest of the Cards on the BPX Node
Upgrading Existing Switch Software to 9.3.30
Upgrading the MGX 8850 from Release 2 to Release 2.1 Software
XPVC as a Migration Connection
XPVC/XPVP Provisioning and Management
Connection Creation for XPVC/XPVPs
XPVC Preferred Table Configurator
Example (Delete an XPVC Command Syntax)
Connection Manager Support for XPVCs
XPVC Provisioning via Service Agent
Adding an XPVC Connection: AddConn script
Deleting an XPVC Connection: DelConn script
Fault Segment Isolation: FaultIsolation script
Get Any Connection: GetAnyConn script
Get Connection Errors: GetConErr script
Get Connection Details: GetConnDetails script
Get Connection Index: GetConnIndex script
Modifying an XPVC Connection: ModConn script
End to End Test Connection or Test Delay: TestConnDelay script
Displaying Information on a Specified XPVC Segment
Migration From Automatic Routing Management to PNNI Using Cisco WAN Manager
This chapter provides details on the AutoRoute to PNNI migration process, including upgrading switch software, and creating and managing extended permanent virtual circuits (XPVCs) and extended permanent virtual paths (XPVPs).
Migration Process Overview
The migration process consists of the following tasks:
•
Upgrading Cisco WAN Manager from Release 10.x to 11
•
•
•
•
Upgrade Cisco WAN Manager from 10.x to 11.
Upgrade Cisco WAN Manager from Release 10.x to 11. Refer to the Upgrading Cisco WAN Manager chapter in the Cisco WAN Manager Installation Guide for Solaris, Release 11.
Preparing To Upgrade Cisco BPX Switch Software From 9.2.34 to 9.3.30
Upgrade the Cisco BPX switch software from Release 9.2.34 to Release 9.3.30. Complete the following steps:
Step 1
Refer to Chapter 13, "Saving and Restoring Node Configurations", in the Cisco WAN Manager User's Guide, Release 11 for detailed instructions on using the Config-save-restore GUI to save the configuration on the switch.
Step 2
Step 3
Refer to the Compatibility Matrixes in the Switch Software Release Notes for Release 9.2.34 to confirm this.
The user can also verify the same information using Network Browser. Refer to Chapter 5, "Network Browser", in the Cisco WAN Manager User's Guide, Release 11 for detailed instructions on using the Network Browser.
Step 4
Syntax and detailed descriptions of these commands are available in the Cisco WAN Switching Command Reference, Release 9.3.30.
Step 5
Syntax and detailed descriptions of these commands are available in the Cisco WAN Switching Command Reference, Release 9.3.30.
Step 6
Step 7
Step 8
Step 9
Refer to the Cisco WAN Switching Command Reference, Release 9.3.30 for syntax and a detailed description of the dspports command.
Step 10
Refer to Chapter 5, Network Browser, in the Cisco WAN Manager User's Guide, Release 11 for detailed instructions on using the Network Browser GUI. Refer to Chapter 3, Connection Manager, in the Cisco WAN Manager User's Guide, Release 11 for detailed instructions on using the Connection Manager GUI.
Step 11
Refer to the Cisco WAN Switching Command Reference, Release 9.3.30 for syntax and a detailed description of the dsptrks and dsplns commands.
Step 12
Refer to Chapter 5, Network Browser, in the Cisco WAN Manager User's Guide, Release 11 for detailed instructions on using the Network Browser GUI and to Chapter 3, Topology Manager, in the Cisco WAN Manager User's Guide, Release 11 for detailed instructions on using the Topology application.
Step 13
Refer to the Cisco WAN Switching Command Reference, Release 9.3.30 for syntax and a detailed description of the tstdelay command. All incomplete and failed connections are in failed state.
Step 14
Refer to the Cisco WAN Switching Command Reference, Release 9.3.30 for syntax and a detailed description of the tstconseg command. All incomplete and failed connections are in failed state.
Gracefully Upgrading the BCC Card Pair on the BPX node
Perform the following steps to upgrade gracefully the BCC cards on a BPX node
Step 1
Refer to Chapter 12, Downloading Software and Firmware, in the Cisco WAN Manager User's Guide, Release 11 for detailed instructions on entering TFTP commands to load the new version of software and firmware to the node.
Step 2
Step 3
dspcd 7 and dspcd 8 commands to verify that the SWSW version displayed is 9.3.30.Step 4
Gracefully Upgrading the Rest of the Cards on the BPX Node
Perform the following steps to upgrade gracefully the remaining cards on a BPX node
Step 1
The SWSW version displayed should be 9.3.30 and all the cards in the network should not display any alarms.
Step 2
Step 3
Refer to the Cisco WAN Switching Command Reference, Release 9.3.30 for syntax and a detailed description of the dspalms and dspnodes commands.
Step 4
Refer to Chapter 5, Network Browser, in the Cisco WAN Manager User's Guide, Release 11 for detailed instructions on using the Network Browser GUI. Refer to Chapter 3, Topology Manager, in the Cisco WAN Manager User's Guide, Release 11 for detailed instructions on using the Topology application.
Step 5
The user can also verify the same information using the Connection Manager GUI, and/or the user_connection and atm_connection tables that none of the existing complete connections is in failed state, and there are no A-bit or OAM alarms. All incomplete and failed connections are in failed state.
Step 6
The user can also verify the same information using the Connection Manager and the Network Browser application, that the ports are free of alarms.
Refer to Chapter 5, Network Browser, in the Cisco WAN Manager User's Guide, Release 11 for detailed instructions on using the Network Browser GUI and to Chapter 3, Connection Manager, in the Cisco WAN Manager User's Guide, Release 11 for detailed instructions on using the Connection Manager GUI.
Step 7
Refer to the Cisco WAN Switching Command Reference, Release 9.3.30 for syntax and a detailed description of the dsptrks and dsplns commands.
Step 8
Refer to Chapter 5, Network Browser, in the Cisco WAN Manager User's Guide, Release 11 for detailed instructions on using the Network Browser GUI and to Chapter 3, Topology Manager, in the Cisco WAN Manager User's Guide, Release 11 for detailed instructions on using the Topology application.
Step 9
Refer to the Cisco WAN Switching Command Reference, Release 9.3.30 for syntax and a detailed description of the tstdelay command. All incomplete and failed connections are in failed state.
Step 10
Refer to the Cisco WAN Switching Command Reference, Release 9.3.30 for syntax and a detailed description of the tstconseg command. All incomplete and failed connections are in failed state.
Upgrading Existing Switch Software to 9.3.30
This section describes the process of upgrading to the appropriate Release of switch software to migrate from Automatic Routing Management to PNNI. To begin the software upgrade procedure, enter the loadrev command. The node will search for the specified software revision from a Cisco WAN Manager workstation, a PC running StrataView Lite, or from another node. Once the node finds a download source, the flash EEPROM on the active processor card will erase. The flash EEPROM will then be loaded with the new software using a block file transfer protocol. This process takes approximately one hour using the 19.2 Kbps serial port or 45 minutes via Ethernet.
Much less time is required for downloading from neighbor nodes via network trunks. Output during a download is shown below:
Info NPM [or BCC or NPC] 1 downloading Flash with Revision 9.3.30 17:49:45Info NPM [or BCC or NPC] 1 downloaded Flash with Revision 9.3.30 18:39:29Once the flash EEPROM on the active processor card has been loaded, the RAM image on the standby processor card is erased in preparation for the new software image download. Once the RAM is cleared, the new image is downloaded into RAM from the flash EEPROM on the active processor. When the RAM is successfully downloaded, the standby processor restarts with the new software. This example shows the NPM on an IGX; it is equally valid for a BCC on a BPX.
The following lines are typical event log messages resulting from the loadrev command completing the download.
Info NPM 2 Removed 18:39:32Info NPM 2 Restarted due to a Primary Revision Change 18:39:42Info Standby NPM [or BCC or NPC] 2 downloading Revision 8.3.20 18:39:48Info Standby NPM [or BCC or NPC] 2 Update Completed 18:41:11Info Standby NPM [or BCC or NPC] 2 downloaded Revision 8.3.20 18:52:25Info NPM 2 Removed 18:52:26Info NPM 2 Restarted due to a Completed Download 18:52:32When a new revision of software is loaded into the standby processor card's RAM, the existing database of configuration parameters must be converted to the new structure. When this process is completed, the standby processor card will enter the "Upgraded" state.
Info Standby NPM 2 Update Completed 19:00:52To run the new software, enter the runrev command. This causes a processor switch-over, so the standby processor that's loaded with the new software version (in RAM) becomes the active processor. The processor with the original software revision enters a "locked" state. The original version of software is maintained in the locked processors' RAM in case a fall-back is necessary. The node operates in a non-redundant mode until the "locked" processor is upgraded to the new software revision.
Info NPM 1 Revision Installation - switched to NPM 2 19:40:09Info Standby NPM 1 downloaded Revision 9.2.34 19:40:09Info Standby NPM 1 Update Completed 19:40:18When the new software revision is verified to be operating correctly, the "locked" processor must be updated with the new software. Enter another loaders command to purge the original software version. The "locked" processor restarts and loads RAM with the new software image from flash EEPROM.
Finally, both processor cards are loaded with the new software.
Info NPM 2 downloading Flash with Revision 8.3.20 19:41:57Info Standby NPM 1 Update Completed 19:42:54Info NPM 1 Removed 19:42:55Info NPM 1 Restarted due to a Completed Download 19:43:04Info NPM 2 downloaded Flash with Revision 8.3.20 19:44:23Info Standby NPM 1 Update Completed 19:52:05Upgrading the MGX 8850 from Release 2 to Release 2.1 Software
Refer to Appendix A, "Downloading and Installing Software Upgrades" of the Cisco MGX 8850 and Cisco MGX 8950 Routing Switch Software Configuration Guide, Release 2.1. This appendix describes how to locate, download, and install software updates for the switch. Because software updates are stored in the switch file system, it also includes a section on browsing the file system. This appendix includes the following sections:
•
•
•
•
•
•
•
•
•
XPVC Creation Overview
Note that in the following sections, mention of 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
Extended 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
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
Figure 11-1 below shows the popup menu item that appears when you right-click on an XLMI link.
Figure 11-1 Display XLMI Trunk Popup
The display that opens after selecting the Display Trunk popup is shown in Figure 11-2.
Figure 11-2 XLMI Trunks Display
You can also verify the status of the ENNI ports in the Network Browser application, as shown in Figure 11-3.
Figure 11-3 Verifying ENNI Ports in the Network Browser
For more information on the Network Browser application and its use, see Chapter 5, "Network Browser" of the Cisco WAN Manager User's Guide, Release 11.
Step 3
For an example of the Preferred Table Configurator application, refer to Chapter 3 of the Cisco WAN Manager User's Guide, Release 11.
Note
Step 4
The above list summarizes the steps required to create and verify an XPVC using CWM Release 11.
XPVC as a Migration Connection
An XPVC is an end-to-end virtual circuit that traverses at least one UNI or NNI interface on which XLMI has been enabled. The XPVC, which is shown in the following graphic, Figure 11-4, 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 11-4 Migration Connection Example
There are two basic types of XPVC that you can create using Cisco WAN Manager 11:
•
•
Each XPVC segment consists of an actual virtual circuit, that 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. Cisco WAN Manager software 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 MGX 8850 switches.
1.
2.
XPVC/XPVP Provisioning and Management
There are two ways to provision an XPVC using Cisco WAN Manager Release 11:
1.
2.
You can provision end-to-end XPVCs using either a script that is manually invoked from the Cisco WAN Manager Unix command line (the CWM-XPVC-CLI) or programmatically via the SNMP interface of the Service Agent. Note that the CWM-XPVC-CLI supports addition and deletion only, whereas you can also modify an existing XPVC using the Service Agent.
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 can be done by using the switch CLI. Once you have done this, you will be able to verify the successful activation and discovery of the XLMI links through the Network Browser and by inspection of the Topology Map.
Although Cisco WAN Manager 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 application 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. Details of the Configurator are included later in this chapter.
Once you have created the XPVC using the CWM-XPVC-CLI, you can use the Connection Manager to display status information and also to perform an end-to-end test that will provide the round-trip delay on a selected connection. End-to-end test delay is also available through the SNMP service agent.
Supported cards: BXM, ASI, AUSM, FRSM, RPM/RPM-PR, ATM = ATM or RPM endpoint
BPX feeder or MGX R2 feeder = Cisco MGX 8220, Cisco MGX 8230, Cisco MGX 8250,
Cisco MGX 8850 Release 1The above table summarizes the endpoint and XPVC connection types that are supported in Cisco WAN Manager 11. Associated with each connection type are specifically supported service types. Refer to the Cisco WAN Manager 11 Release Notes for a complete mapping of the specific connection and service types supported.
Note
Connection Creation for XPVC/XPVPs
The following steps summarize the process for creating and verifying an XPVC or XPVP.
Creating an XPVC
Step 1
•
–
–
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
XPVC Preferred Table Configurator
The XPVC Preferred Table Configurator is a Cisco WAN Manager application that allows you to define the mapping between XLMI/ENNI ports on BPX nodes and the corresponding AXSM ports in the PNNI network. The overall function of the XPVC Preferred Table Configurator is described in Chapter 3, "Using Network Topology" in the Cisco WAN Manager User's Guide, Release 11.
CWM-XPVC-CLI
This section highlights the main features of the CWM-XPVC-CLI. These features are as follows.
•
•
•
–
–
•
a.
b.
c.
d.
The CLI is invoked from the Unix command line, and in turn invokes the ConnProxy process in the Cisco WAN Manager Service Agent. The Service Agent must have been previously installed on the Cisco WAN Manager workstation. Also, HP OpenView must be installed and running since the CLI uses the SNMP command tools included with OpenView.
The CLI supports the addition and deletion of XPVCs, but not modification. If you need to modify an XPVC, you must first delete it then add it again with the new parameters.
In addition to the add and delete scripts, Cisco WAN Manager provides several parameter files. These files are sample templates that you can modify if the default parameters are not appropriate. The parameter files are of two basic types:
1.
2.
The shell scripts and the parameter files are stored in the /usr/users/svplus/tools directory.
Adding an XPVC
The following example shows how the syntax for the cwmAddConn command is used to create an XPVC. This command and its associated parameters are entered at the Unix command line by an authorized Cisco WAN Manager user. Mandatory parameters are shown like this <cwmHost>, and optional parameters as shown inside brackets, for example: [-tout ...].
Example (Add an XPVC Syntax)
Add an XPVC CLI syntax%cwmAddConn<cwmHost><snmpCommunity><localEndpoint><localEndpointType><remoteEndpoint><RemoteEndpointType><serviceType>[-help][-tout <TimeOut> ][-vc <VCType>][-desc \"<ConnectionDescriptor>\"][-lfile <LocalEndpointParameterFile>][-rfile <RemoteEndpointParameterFile>][-cfile <ConnectionParameterFile>]The mandatory parameters for cwmAddConn are shown in Table 11-2.
Optional parameters are indicated by keywords, and are shown in Table 11-3
Note
The following example shows a cwmAddConn command for creating an XPVC. In this example, the local endpoint is an ATM port on a BPX node, bpx1. The port is slot 4, port 1 and the VPI.VCI is 20.356. The remote endpoint is on port1, line 2 of the FRSM card in slot 6 of the feeder node mgx08 attached to bpx6. The circuit has the DLCI 356.
%cwmAddConncwm1 \ <cwmHost>private \ <snmpCommunity>bpx1..4..1.20.356 \ <localEndpoint>atm \ <localEndpointType>bpx6.mgx08.6.2.1.356 \ <remoteEndpoint>fr \ <RemoteEndpointType>vbr3 \ <serviceType>-desc "ATFR bpx1-mgx08" \-cfile /usr/users/ATFR_parms1Note that each parameter in the command is entered on a separate line, and that each line except the last is terminated by " \" (space backslash).
This example also includes a user-created connection parameter file (AFR_parms1) that includes one or non-default settings.
%cd /usr/users/svplus/config%cp connfparm.conf /usr/users/ATFR_parms1%vi /usr/users/ATFR_parms1### ATFR_parms1svConnOvrSubOvrRide 2 # enable oversub on FRSMsvConnTrkAvoidType 2 # avoid satellite trunks#:wq!
Note
You will need to verify the allowable values for the parameters you wish to modify. The Service MIB is stored in /usr/users/svplus/mibs/SV+Service.mib, and can be viewed from the Unix command line. Alternatively, refer to the Cisco WAN Manager SNMP Service Agent Release 11.%cwmAddConncwm1 \...-cfile /usr/users/ATFR_parms1Deleting an XPVC
The syntax for the cwmDelConn command is shown in the following example.
Example (Delete an XPVC Command Syntax)
Example 1
%cwmDelConn<cwmHost><snmpCommunity><anyEndpoint><EndpointType>[-help][-tout <TimeOut> ][-rend <RemoteEndPoint>][-lfile <LocalEndpointParameterFile>][-rfile <RemoteEndpointParameterFile>]The following is an example of the cwmDelConn command that is used to delete an XPVC with RPM endpoints.
Example 2
%cwmDelConncwm1 \ <cwmHost>private \ <snmpCommunity>bpx2.mgx02.9..1.0.250 \ <anyEndpoint>*rpm \ <EndpointType>-lfile /usr/users/RPM/passwds **
Note
Note
When deleting an XPVC, you provide either the local or the remote endpoint.
The endpoint type must be appropriate for the endpoint that you select.
Parameters that differ from those for cwmAddConn are shown in Table 11-4.
Note
Connection Manager Support for XPVCs
The Connection Manager in Cisco WAN Manager Release 11 provides support for XPVCs. Supported features include the following:
•
•
•
•
•
XPVC Provisioning via Service Agent
This section provides procedures for provisioning XPVC connections via the Service Agent.
For a XLMI Configuration
SET svAtmPortSignallingProtocol in svATMPortTable to XLMI for NNI port.
For a ENNI Configuration
SET svATMPortType in svATMPortTable to ENNI or EUNI.
For Adding an XPVC Connection
SET endpoints and parameters in End Point Tables. rpmEndPointTable, atmEndPointTable, frEndPointTable are applicable.
SET svConnRowStatus in svConnTable to create (4).
SET svConnProtocolType to xpvc for XPVC connection.
An XPVC connection can be added using the CWM-XPVC-CLI without specifying the VC type or using the Service MIB without specifying the svConnProtocolType.
The ConnProxy will determine the correct protocol type (PVC/SPVC/HYBRID/XPVC) based on the endpoints chosen and the contents of the xpvc_preferred table.
The protocol type will be automatically chosen as XPVC provided all user endpoints chosen in the Automatic Routing network have a xpvc_preferred table entry with the preferred flag set.
For Deleting an XPVC Connection
SET svConnRowStatus for XPVC deletion.
For Modifying an XPVC Connection
SET endpoints and parameters in End Point Tables and svConnTable (except CC related objects).
SET cwmConnPrefRoute for PVC segment of the XPVC in cwmConnTable.
Location of ConnProxy Scripts
Scripts can be found in /usr/users/svplus/scripts/proxyscripts/connproxy. The following scripts are provided:
•
•
•
•
•
•
•
•
•
Adding an XPVC Connection: AddConn script
AddConn <proxyHost> <localType> <localNode> <localChan> <remoteType> <remoteNode> <remoteChan> <conSubType> <totalNumberOfConnections> <numberOfSimultaneousRequests> <local_parameter_set | -> <remote_parameter_set | -> <connection type>
When configuring the parameters, the user should observe the following rules.
•
Note
•
•
•
•
•
•
Features
The script allows bulk provisioning by incrementing the VCI or the DLCI based on the value given for the input parameter "totalNumberOfConnections." The script also allows simultaneous provisioning based on the value given for the input parameter "numberOfSimultaneousRequests".
Example Parameter Files
Filename: /tmp/parmfile (atm connection)atmEndPointSCRZeroPlus1 87atmEndPointPCRZeroPlus1 297svConnCellRouting 1svConnOvrSubOvrRide 1Filename: /tmp/parmfile (rpm connection on MGX8850 R1)rpmEndPointNodeUser ciscorpmEndPointNodePasswd ciscorpmEndPointRpmPasswd labrpmEndPointPeak 50Filename: /tmp/parmfile (fr connection)frEndPointPercUtil 77frEndPointCIR 67svConnCellRouting 2svConnOvrSubOvrRide 2Example AddConn Commands:
AddConn host1 atm igx1 5.2.1.1 atm bpx1 2.2.1.1 vbr2 2000 8 - - -AddConn host1 fr pop1 2.0.1.1 atm pop2 3.1.10.10 abr-fs 1023 5 - - hybridLogs
AddConn.time.log in the $TMP_DIR contains the time log of all the connection additions using AddConn. $TMP_DIR/AddConn.<localChan>_<remoteChan>.out will be created for all the failure cases (For example, /tmp/AddConn.2.2.1.11_2.2.2.11.out).
Sample Output
In the following example, 3 connections are added with 2 simultaneous requests. The third connection addition fails, since the end-point is already in use.
AddConn cwmult60 atm nmsbpx16 2.2.1.9 atm nmsbpx16 2.2.2.9 vbr2 3 2 - - pvcnmsbpx16 [2.2.1.9] [atm] <--- [vbr2] - [pvc] ---> [atm] [2.2.2.9] nmsbpx16+ /opt/OV/bin/snmpset -d -t 3000 -p 8161 -c private -r 0 cwmult60 atmEndPointRowStatus.8.110.109.115.98.112.120.49.54.0.2.2.1.9 integer 4 atmEndPointRowStatus.8.110.109.115.98.112.120.49.54.0.2.2.2.9 integer 4 svConnLocalEndPt.0 objectidentifier atmEndPointNodeName.8.110.109.115.98.112.120.49.54.0.2.2.1.9 svConnRemoteEndPt.0 objectidentifier atmEndPointNodeName.8.110.109.115.98.112.120.49.54.0.2.2.2.9 svConnSubType.0 integer 3 svConnRowStatus.0 integer 4 svConnOvrSubOvrRide.0 integer 2 svConnProtocolType.0 integer 1+ 1>> /tmp/AddConn.2.2.1.9_2.2.2.9.out 2>& 1- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -nmsbpx16 [2.2.1.10] [atm] <--- [vbr2] - [pvc] ---> [atm] [2.2.2.10] nmsbpx16+ /opt/OV/bin/snmpset -d -t 3000 -p 8161 -c private -r 0 cwmult60 atmEndPointRowStatus.8.110.109.115.98.112.120.49.54.0.2.2.1.10 integer 4 atmEndPointRowStatus.8.110.109.115.98.112.120.49.54.0.2.2.2.10 integer 4 svConnLocalEndPt.0 objectidentifier atmEndPointNodeName.8.110.109.115.98.112.120.49.54.0.2.2.1.10 svConnRemoteEndPt.0 objectidentifier atmEndPointNodeName.8.110.109.115.98.112.120.49.54.0.2.2.2.10 svConnSubType.0 integer 3 svConnRowStatus.0 integer 4 svConnOvrSubOvrRide.0 integer 2 svConnProtocolType.0 integer 1+ 1>> /tmp/AddConn.2.2.1.10_2.2.2.10.out 2>& 1- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -nmsbpx16 [2.2.1.9] [atm] <--- [vbr2] - [pvc] ---> [atm] [2.2.2.9] nmsbpx16Connection index of the connection given above: 2681- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -nmsbpx16 [2.2.1.10] [atm] <--- [vbr2] - [pvc] ---> [atm] [2.2.2.10] nmsbpx16Connection index of the connection given above: 2682- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -Time elapsed to add 2 connection[s] in this loop : 4Total connections added till now : 2Total number of errors seen till now : 0Total time taken till now : 4Average time to add a connection till now : 2.00================================================================================nmsbpx16 [2.2.1.11] [atm] <--- [vbr2] - [pvc] ---> [atm] [2.2.2.11] nmsbpx16+ /opt/OV/bin/snmpset -d -t 3000 -p 8161 -c private -r 0 cwmult60 atmEndPointRowStatus.8.110.109.115.98.112.120.49.54.0.2.2.1.11 integer 4 atmEndPointRowStatus.8.110.109.115.98.112.120.49.54.0.2.2.2.11 integer 4 svConnLocalEndPt.0 objectidentifier atmEndPointNodeName.8.110.109.115.98.112.120.49.54.0.2.2.1.11 svConnRemoteEndPt.0 objectidentifier atmEndPointNodeName.8.110.109.115.98.112.120.49.54.0.2.2.2.11 svConnSubType.0 integer 3 svConnRowStatus.0 integer 4 svConnOvrSubOvrRide.0 integer 2 svConnProtocolType.0 integer 1+ 1>> /tmp/AddConn.2.2.1.11_2.2.2.11.out 2>& 1- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -Connection :nmsbpx16 [2.2.1.11] [atm] <--- [vbr2] - [pvc] ---> [atm] [2.2.2.11] nmsbpx16Log file : /tmp/AddConn.2.2.1.11_2.2.2.11.outRequest id : 12469stratacom.svplus.serviceGroup.connGroup.svCmpaErrorTable.svCmpaErrorEntry.svCmpaErrorReqId .12469 : INTEGER: 12469stratacom.svplus.serviceGroup.connGroup.svCmpaErrorTable.svCmpaErrorEntry.svCmpaErrorDesc. 12469 : DISPLAY STRING- (ascii): [08/14/2001 14:52:23] EndPoint already in use: 0.2.2.1.11stratacom.svplus.serviceGroup.connGroup.svCmpaErrorTable.svCmpaErrorEntry.svCmpaErrorEcode .12469 : INTEGER: endpt-exists- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -Time elapsed to add 1 connection[s] in this loop : 0Total connections added till now : 2Total number of errors seen till now : 1Total time taken till now : 4Average time to add a connection till now : 1.33================================================================================********************************************************************************TOTAL NUMBER OF CONNECTIONS ADDED : 2TOTAL NUMBER OF CONNECTION ADDITIONS FAILED : 1TOTAL TIME TAKEN TO ADD ALL THE CONNECTIONS : 4APPROXIMATE AVERAGE TIME TAKEN TO ADD A CONNECTION : 1.33********************************************************************************Deleting an XPVC Connection: DelConn script
Use the delComm command to delete an XPVC connection.
DelConn <proxyHost> <Type> <Node> <Chan> <totalNumberOfConnections> <numberOfSimultaneousRequests> <local_parameter_set | -> <remote_parameter_set | -> <connection type>When configuring the parameters, the user should observe the following rules.
•
•
•
•
•
•
Example
DelConn cwmult65 atm igx1 5.2.1.1 100 5 - -Fault Segment Isolation: FaultIsolation script
FaultIsolation <cwmHost> <connIndex> <xpvcSegmentNumber>where
The connIndex parameter is the xpvc_id in the XPVC table if the connection is an XPVC or the snmp_index in the user_connection table if the connection is either a PVC, an SPVC, or a hybrid connection.
Note
The xpvcSegmentNumber can be 1, 2, or 3. The numbering starts from the local end of the connection. This number should not exceed the number of segments in the specified connection, of course. You should not try to test for faults on segment 3 of a two segment connection.
Note
Example
FaultIsolation cwmult65 1000000015 1Check for faults on the first segment of the connection with the index of 1000000015
Get Any Connection: GetAnyConn script
GetAnyConn <Host> <connIndex> <local_parameter_set | -> <remote_parameter_set | ->•
Example:
GetAnyConn cwmult65 1000000015 - -Get Connection Errors: GetConErr script
GetConErr <Host> <"Request ids">•
Note
Get Connection Details: GetConnDetails script
GetConnDetails <Host> <Options> <ConnIndex>•
-l : Get local endPt.
-r : Get remote endPt.
-c : Get connection parameters
-a : Get all
Get Connection Index: GetConnIndex script
GetConnIndex <Host> <endptType> <Node[.Shelf]> <ChanInfo>•
Note
Modifying an XPVC Connection: ModConn script
ModConn <proxyHost> <localType> <localNode> <localChan> <totalNumberOfConnections> <numberOfSimultaneousRequests> <local_parameter_set | -><remote_parameter_set | ->•
•
•
Example
ModConn cwmult65 atm igx1 5.2.1.1 100 10 - -"Give the local endpoint type, node and channel information, not the remote endpoint information
End to End Test Connection or Test Delay: TestConnDelay script
Use the TestConnDelay to execute and end-to-end connection.
TestConnDelay <ProxyHost> <ConnIndex> <1 for TestConn, 2 for TestDelay>Example
TestConnDelay cwmult65 1000000015 1Execute an end to end Test Connection on the connection with the index of 1000000015
Trap support for XPVCs
The following existing traps support XPVCs
•
•
•
•
•
•
•
Sent to user when there is a change in the alarm status of a XPVC connection and the end to end XPVC connection status is failed.
•
Sent to user when the entire XPVC connection or at least one segment of the XPVC connection is downed.
The following new traps support XPVC management:
•
End-To-End Connection described by the above endpoints is added. This trap is generated when a new End-To-End connection is added from any Connection Manager interface (GUI or Service Agent). A connection alarm status trap is also generated along with this. Currently this TRAP is generated for XPVC connections only.
•
End-To-End Connection described by the above endpoints is deleted. This trap is generated when a connection is deleted from any Connection Manager interface (GUI or Service Agent). Currently this TRAP is generated for XPVC connections only.
•
Connection Descriptor for the End-To-End connection is modified. Currently this TRAP is generated for XPVC connections only.
Displaying XPVC Status
To view XPVC status within the Connection Manager, edit the filter settings to set the end to end Type to XPVC, and select Apply. You will then see a display similar to that shown in Figure 11-5 and/or Figure 11-6 below.
Figure 11-5 XPVC Display at Opening
Figure 11-6 XPVC Display Expanded
With Release 11 you can also view additional information relating to the individual XPVC segments. After highlighting to select an XPVC in the Main Window, activate the Segment View GUI by selecting
