Guest

Cisco SES PNNI WAN Software

3.0.00 Version Software Release Notes, Cisco SES PNNI Controller

  • Viewing Options

  • PDF (466.0 KB)
  • Feedback
3.0 Software Release Notes for the SES Controller

Table Of Contents

3.0 Software Release Notes for the SES Controller

Contents

About Release 3.0

SES PNNI and SVC Controller

System Requirements

Hardware Compatibility Matrix

Software Compatibility

Compatible Releases

Additional Deliverables

New and Changed Information for Release 3.0

SNTP

Priority Routing of Connections

Preferred Routing of Connections

Per Connection Based Utilization of SPVCs

Standards Based Path and Connection Trace

Single-ended SPVC/SPVP Configuration

100K Connections

Upgrading the SES Node

Upgrading to a New Software Release

Special Installation/Upgrade Requirements

Upgrading from SES Release 1.1.75 to Release 3.0

Upgrading the Backup Boot Image

Upgrading the Backup Boot on Non-Redundant Systems

Upgrading the SES PNNI Runtime Image

Upgrading the Runtime Image on Redundant Systems

Upgrading the Runtime Image on Non-Redundant Systems

Upgrade Path

SES PNNI Controller Bring Up Procedure

Limitations and Restrictions

General Limitations and Restrictions

Recommendations

Caveats

Open Anomalies in This Release

Open Anomalies in Release 1.1.75

Problems Fixed in Release 1.1.75

Problems Fixed in Release 1.1.70

Anomalies Status Changes for Release 1.1.70

Fixed Anomalies for Release 1.1.60

Related Documentation

Cisco WAN Manager Release 11

Service Expansion Shelf PNNI Controller Release 3

Cisco WAN Switching Software Release 9.3.40

Conventions

Obtaining Documentation

World Wide Web

Documentation CD-ROM

Ordering Documentation

Documentation Feedback

Obtaining Technical Assistance

Cisco.com

Technical Assistance Center

Cisco TAC Web Site

Cisco TAC Escalation Center


3.0 Software Release Notes for the SES Controller


Contents

This document contains the following sections:

About Release 3.0

These release notes describe the system requirements, new and changed procedures, upgrade procedures, and limitations that apply to Release 3.0 of the SES controller. These notes also contain Cisco support information. The 3.0 software release supports the Cisco WAN switching products: BPX 8600 series with SES controller.

SES PNNI and SVC Controller

Release 3.0 of the Service Expansion Shelf (SES) controller is compatible with the BPX 8600 series software Release 9.3.30 and with the later 9.3 Releases. The SES controller is connected to the BPX 8600 series switch via a BXM-155 (or T3/E3) port configured as a trunk. Redundant SES systems contain two controller cards which offer APS protection on the ports connecting to the BPX.

Feature Overview

The SES controller is a Virtual Switch Interface (VSI) controller which provides a BPX 8600 series wide-area switch the capability to create switched virtual circuits (SVCs) and soft permanent virtual circuits (SPVCs) using the User-to-Network Interface (UNI) and Private Network-to-Network Interface (PNNI) protocols. One SES controller is required for each BPX 8600 series node that will be originating, transporting, or terminating SVC/SPVC connections. The SES controller is offered in redundant or non-redundant configurations.

Detailed Feature Information

As networks grow in size, PNNI becomes a critical element in the ability to scale a network. PNNI provides a standard, interoperable, and scalable method to grow PVC (SPVC) networks to large sizes. In addition, applications such as voice, video, and LAN require WAN switches to provide dynamic connection capabilities in the form of SVCs. The SES controller provides the BPX 8600 series switch with a centralized controller for establishing SPVCs and SVCs in both the BPX 8600 series networks and in mixed vendor environments.

The BPX 8600 series switch in combination with the SES controller (Release 1.1) supports the following features:

SNTP

Priority routing of connections

Preferred routing of connections

Standards based path and connection trace facilities

Single-ended SPVC and SPVP configuration

ATM UNI 3.0/3.1, 4.0 (CBR, VBR, UBR)

PNNI Single Peer Group and Multiple Peer Group (MPG)

AINI

60 K LCN

Point to Point SVCs, SPVCs, and SPVPs

IISP with PNNI Inter-networking

E.164 and AESA/NSAP (DCC, ICD, E.164) addressing

Address filtering (source and destination)

ILMI 4.0

SPVC and SPVP endpoint provisioning (including ABR)

OC-3/STM-1, T3/E3 interfaces

OC-12/STM-4 interfaces

Intelligent CAC

Call Processor Redundancy (calls stable across switchover)

APS on controller uplinks to BPX 8600

Connection and Path Trace facilities

Integrated management via CWM and SNMP MIBs

100 K connections (SVC+SVP+SPVC+SPVP) per node

100 K max endpoints per node (if all 50K connections are DACS)

99 UNI/PNNI SVC ports per node

100 calls per second

Dynamic partitioning and soft partitioning

SPVC support on feeder trunks

Dedicated Q-bin for control signaling

Graceful upgrade on the SES controller from Release l.1.75 to Release 3.0.

System Requirements

This section describes the hardware supported in this release and the software compatibility requirements.

Hardware Compatibility Matrix

Table 1 and Table 2 list the hardware supported in Release 3.0, and show which back cards are compatible with each front card.

Table 1 OC3 Hardware Compatibility

OC3 Combinations (Shipping/Customer Configurations)
No.
Description
Front Card (PXM)
PXM UI Back Card
PXM Uplink Back Card

1

MMF OC3

SES-PXM-CNTL-4-155

(with 4-port OC3)

P/N 800-06454-01 or later

PXM-UIA

Rev. A0 or later

MMF-4-155

Rev. A0 or later

2

SMF-OC3, Intermediate Range

SES-PXM-CNTL-4-155

(with 4-port OC3)

P/N 800-06454-01 or later

PXM-UIA

Rev. A0 or later

SMFIR-4-155

Rev. A0 or later

SMFIR-4-155/B

Rev. A0 or later


Table 2 T3/E3 Hardware Compatibility

T3/E3 Combinations (Shipping/Customer Configurations)
No.
Description
Front Card (PXM)
PXM UI Back Card
PXM Uplink Back Card

1

T3

SES-PXM-CNTL-2T3E3

(with 2-port T3E3)

P/N 800-06699-01

PXM-UIA

Rev. A0 or later

BNC-2T3

Rev. A0 or later

2

E3

SES-PXM-CNTL-2T3E3

(with 2-port T3E3)

P/N 800-06699-01

PXM-UIA

Rev. A0 or later

BNC-2E3

Rev. A0 or later


Table 3 lists the MGX hardware which is compatible with Release 3.0 of the SES controller.

Table 3 MGX Hardware Compatibility

Feeder
MGX 8850 R1
MGX 8220
Release
1.1.34
5.0.16

HW Cards

PXM-1

PXM1-2T3E3

PXM1-4OC3

PXM1-OC12

SRM-3T3

CESM-8E1

CESM-8T1

AUSMB-8E1

AUSMB-8T1

CESM-T3

CESM-E3

FRSM-8E1

FRSM-8T1

FRSM-HS2

FRSM-2CT3

FRSM-2T3

FRSM-2E3

FRSM-HS1/B

VISM-8T1

VISM-8E1

RPM

RPM-PR

FRSM-4T1/4E1/4T1-C/4E1-C

SRM-T1E1

SRM-3T3

CESM-4T1/4E1

CESM-8T1/8E1

AUSM-4T1/4E1

FRSM-8T1/8E1

AUSM-8T1/8E1

AUSMB-8T1/8E1

AUSMB-8T1/8E1

FRSM-HS1

FRSM-HS1/B

FRSM-HS2

IMATM-T3T1/E3E1

IMATMB-T1/E1


Software Compatibility

Table 4 lists the software that is compatible for use in a switch running Release 3.0 software.

Table 4 Software Compatibility Matrix 

Board Pair
SES Controller Release
Latest Boot Code Version
Minimum
Boot Code
Version
BXM Firmware
SWSW
CWM

PXM1

1.0.10

pxm1_001.000.001.000_bt.fw

1.0.01

MFH

9.3.10

10.3

PXM1

1.0.11

pxm1_001.000.011.001_bt.fw

1.0.11

MFJ

9.3.10

10.4

PXM1

1.0.12

pxm1_001.000.011.001_bt.fw

1.0.11

MFL

9.3.11

10.4

PXM1

1.0.13

pxm1_001.000.013.000_bt.fw

1.0.13

MFM

9.3

10.4

PXM1

1.0.14

pxm1_001.000.013.000_bt.fw

1.0.13

MFN

9.3.11

9.3.24

10.4

PXM1

1.0.15

pxm1_001.000.013.000_bt.fw

1.0.13

MFN

9.3.11

9.3.24

10.4

PXM1

1.1.60

pxm1_001.001.060.102_bt.fw

1.1.60

MFN

9.3.30

10.5

PXM1

1.1.70

pxm1_001.001.070.201_bt.fw

1.1.60

MFR

9.3.35

10.5.10

PXM1

1.1.75

pxm1_001.001.075.101_bt.fw

1.1.60

MFR

9.3.36

10.5.10
Patch 1

PXM1

3.0

pxm1_003.000.000.000_bt.fw

1.1.75

MFR

9.3.36

10.5.10
Patch 1


Compatible Releases

Release 3.0 of the SES controller is been certified with the following releases:

Graceful upgrade to Release 3.0 from Release 1.1.75.

BPX SWSW Version 9.3.30 or later (see Software Compatibility Notes Matrix, first and second bullets)

BXM Firmware version MFN or later (see Software Compatibility Notes Matrix, first and second bullets)

CiscoView Version 5.0

Cisco WAN Manager (CWM) Release 10.5.10 Patch 1

BCC-3-64

BPX-BCC-4V or BPX-BCC-4V/B

MGX 8850 Release 1, Release 1.1.40

MGX 8220 5.0.16

SNMP MIB for Release 1.1.75 is sesmibs1175.tar

For further information on the BXM card, refer to the 9.3 Version Release Notes Cisco WAN Switching Software.

Additional Deliverables

The SES controller MIB is being provided with the delivery of Release 3.0 of the SES controller software on CCO. The MIB is in standard ASN.1 format, and is included in the same directory where the SES controller software is located within CCO. The SNMP SES controller MIB file can be compiled with most standards-based MIB compilers.

Refer to the Cisco SES PNNI Controller Software Configuration Guide, Release 3, Appendix D, "SNMP Management Information Base," for a description of the MIBs supported by the SES controller.

New and Changed Information for Release 3.0

This section describes new and changed features in Release 3.0 of the SES controller.

SNTP

The SNTP feature enables BPX SES nodes with Time of Day (TOD) synchronization. This features allows BPX SES nodes to act as time of day (TOD) servers for the network. Accurate time of day service synchronized to Universal Time Coordinated (UTC). Through SNTP, the BPX SES node can synchronize to any SNTP/NTP time server. This provides accurate time for statistics and alarms generated on the switch and enables accurate synchronization of such events between switches. In a network of BPX SES and MGX switches, the TOD must be set on the BPX in order to be distributed consistently throughout the network.

Priority Routing of Connections

Use the priority routing feature to specify priority of connections, so that high priority connections will be established before low priority connections. During failures, high priority connections are released before low priority connections. High priority connections are rerouted and reestablished before low priority connections.

Preferred Routing of Connections

You can configure a connection's specific path through the network through the preferred routing feature. Through this feature, a network operator bypasses automatic PNNI route selection. Connections are configured as either preferred routes or directed routes.

A preferred route follows the configured path if it is available. If the preferred route is not available, the connection reverts to a PNNI-selected route.

A directed route follows only the configured path. If the configured path is not available, the connection remains un-routed.

In this first implementation of Preferred routes, a set of preferred routes is configured and assigned reference numbers called "route sets". As connections are configured, they can be assigned to a particular route set. Each route set contains one preferred or directed route.

Preferred routes can be specified only across a single PNNI peer group. Preferred routes are interoperable with any standard PNNI implementation. You can control the selection of routes based on criteria other than those allowed in the route selection algorithms offered by PNNI.

Per Connection Based Utilization of SPVCs

The percentage utilization factor for SPVCs improves your control of network utilization for multiple tiers of service on networks supporting various trunk capacities. The percentage utilization factor is used for Connection Admission Control (CAC) for the connection. The actual bandwidth used for CAC is based on the following factors:

PCR/SCR configured for the connection

percentage utilization factor configured for the connection

percent utilization configured for interfaces in the selected path.

This feature enables service providers to provide differentiated overbooking on a per connection basis, rather than only on the uniform basis allowed by interface overbooking.

Standards Based Path and Connection Trace

You can determine the path taken by a connection through the path and connection trace feature. The path trace feature collects information about the path of new connections in the process of being established. The connection trace feature is collects information on existing connections that have already been established. The path and connection trace feature conforms to the ATM Forum standard PNNI Addendum for Path and Connection Trace, Version 1.0 af-cs-0141.000. Path and connection trace is a standards based feature that enables SES interoperability with other vendor equipment.

Single-ended SPVC/SPVP Configuration

You can configure both the endpoints of the SPVCs at the master end of the connection. In previous release, you could only configure double-ended SPVCs, which meant you had to configure both the master and slave ends of a connection. In release 3.0, the slave end of the connection is activated when the connection is established by the master end. This feature enables improved interoperability with other vendor equipment and management stations.

100K Connections

Release 3.0.00 of the SES Controller allows 100 K connections. Since CWM can not support a large number of connections, the number of persistent SPVC connections is limited to 100 K. Also, when using inband management, only 50 K connections are supported.

Upgrading the SES Node

Use the following sequence to upgrade an SES node:


Step 1 At the BPX node, upgrade the BXM firmware to MFR. For detailed information on BXM firmware upgrades, refer to the 9.3 Version Release Notes Cisco WAN Switching Software.

Step 2 At the BPX node, upgrade the BCC switch software to Release 9.3.35. For detailed information on BCC switch software upgrades, refer to the 9.3 Version Release Notes Cisco WAN Switching Software.

Step 3 Upgrade the SES controller to release 3.0. The current boot image is pxm1_003.000.000.000_bt.fw. The current runtime software is pxm1_001.001.075.101_ses.fw. The latest upgrade procedures are included in the sections that follow.

Step 4 If applicable, upgrade other feeders in your network to a newer release.


Upgrading to a New Software Release

This section contains installation and upgrade instructions. For complete details, refer to the Cisco SES PNNI Controller Software Configuration Guide, Release 3.0 part number 78-14258-01.


Note You can gracefully upgrade the SES controller software from Release 1.1.75 to Release 3.0.


When upgrading your node, upgrade the software in the following order:

1. PXM boot software

2. PXM runtime software

The following sections describe how to upgrade the PXM cards.

Special Installation/Upgrade Requirements

This section covers the procedures for upgrading the backup boot and runtime images for the following hardware:

Redundant controller card

Single controller card (the PXM)

Upgrading from SES Release 1.1.75 to Release 3.0

The procedures for upgrading the boot and runtime software are in the sections that follow.


Note You can only upgrade to Release 3.0 from Release 1.1.75. If you are running a release prior to 1.1.75, (such as 1.1.70, or 1.0.16), you must upgrade to1.1.75 before you download the 3.0 boot and runtime images. For information on upgrading to Release 1.1.75, refer to the 1.1.75 Version Software Release Notes Cisco SES Controller Software.


Upgrading the Backup Boot Image

This section provides instructions for upgrading the backup boot images from Release 1.1.75 to
Release 3.0. The boot upgrade can be graceful or non-graceful, depending on the type of card to be upgraded and the configuration of the node.

Upgrading the Backup Boot on Redundant Systems


Note Use the following procedure to upgrade the boot on both the active and the redundant controller cards. When performing upgrades on redundant cards, run this procedure on the standby card and not on the active card. This keeps the node in service during the upgrades. Before you upgrade the boot image, FTP the new backup boot firmware, pxm1_003.000.000.000_bt.fw, to the disk (should be the same as the PXM FW procedure.)


To upgrade the boot image on the active controller cards on redundant systems, follow these steps:


Step 1 Transfer the backup boot image to the card disk, as follows:

a. At the SES CLI, enter the dspipif command on the active controller card to find the node's IP address. The field internet address for lnPci 0 interface is the node IP address.

b. From the workstation containing the PXM backup boot image, enter ftp <Node IP address>.

c. Enter the username cisco.

d. Enter your password.


Note Your password is supplied with the image.


e. Enter the cd C:/FW command to get to the switch directory.

f. Enter the bin command (for a binary transfer).

g. Enter the put <PXM backup boot image name> command to transfer the backup boot and runtime files from the server to the switch directory C:/FW. See the following example:

put pxm1_003.000.000.000_bt.fw

Replace <PXM backup boot image name> with the boot image name. For Release 3.0 of the SES, the boot image name is pxm1_003.000.000.000_bt.fw.

h. Enter the bye command to end your session.

Step 2 At the SES controller CLI, enter the dspcds command to determine the standby card slot number.

Step 3 To verify that the boot IP for both the active and standby card is unique, enter the bootchange command.

Step 4 Press Enter until you see inet on ethernet (e). This is the boot IP address for the active PXM.

To change the boot IP address to make it unique, type a new address at the inet on ethernet (e) prompt.


Note Changing the boot IP address on the active PXM also changes it on the standby PXM.


Step 5 Enter the cc <slot number> command to change to the standby card.

ses1.1.PXM.a> cc 2

Replace <slot number> with the slot number of the card you want to work on.

Step 6 Type sh to go to the shellConn.

ses1.2.PXM.s> sh

Step 7 Enter the sysBackupBoot command.

PXM1> sysBackupBoot

Step 8 Press Return after you see the disk sync message to get back to active PXM.

Step 9 Exit or open a new telnet window. Telnet into the standby IP host inet address from Step 3.


Note An alternate way to get to the standby card is via the console port on the standby.


Step 10 Perform the following tasks to reset the card:

a. Verify that the card is at the pxm1bkup> prompt. If it is not, enter the sysBackupBoot shellConn command on the standby card.

b. Enter the sysPxmRemove command:

pxm1bkup>sysPxmRemove

After you issue the sysBackupBoot command, it takes about one minute for the active PXM to reset the card. If the active PXM resets the standby PXM, wait until it comes to the standby state (approximately four or five minutes), then telnet into the standby and repeat Step 5 and Step 6. After the sysPxmRemove command is issued the active PXM can not reset the standby.

Step 11 Enter the cd "C:/FW" command from pxm1bkup> prompt to get the FW directory.

pxm1bkup> cd "C:/FW"

Step 12 Enter the ls command to verify that the boot firmware file is there.

pxm1bkup>ls

Step 13 Enter the sysFlashBootBurn <"boot firmware file name"> command to burn the image on the disk:

pxm1bkup>sysFlashBootBurn "3.0"

The system will ask if you want to proceed. Enter Y for Yes.

Step 14 When the pxm1bkup> prompt returns, enter the reboot command.

Flash Download completed...
value = 0 = 0x0
pxm1bkup> reboot

Step 15 Log in to the active PXM.

a. Enter the dspcds command to ensure the standby is in standby state.

b. Enter the dspcd <standby slot #> command to verify the firmware was loaded successfully.

Step 16 Load the backup boot onto the active PXM.

a. Enter the switchcc command to change cards.

ses1.1.PXM.a> switchcc 

b. Log in to the SES controller.

c. Perform Step 5 to Step 13 on the new standby PXM.

Upgrading the Backup Boot on Non-Redundant Systems

The upgrade of the boot on a non-redundant controller card is non-graceful. This means the traffic gets disrupted on the card during this operation. The upgrade can only take place when the card is in the BOOT stage. Because there is only one controller card, there will be a node outage as well.

For non-redundant systems, follow these steps to upgrade the backup boot:


Step 1 Transfer the backup boot image to the card disk using FTP as follows:

a. At the SES CLI, enter the dspipif command at the active controller card to find the Node's IP address. The field internet address for lnPci 0 interface is the node IP address.

b. From the workstation containing the PXM backup boot image, enter ftp <Node IP address>.

c. Enter the username cisco.

d. Enter your password.


Note Your password is supplied with the image.


e. Enter the cd C:/FW command to get to the switch directory.

f. Enter the bin command (for a binary transfer).

g. Enter the put <PXM backup boot image name> command to transfer the backup boot and runtime files from the server to the switch directory C:/FW. See the following example:

put 3.0

Replace <PXM backup boot image name> with the boot image name. For Release 1.1.75 of the SES, the boot image name is 3.0.

h. Enter the bye command to end your session.

Step 2 Log in to the SES.

Step 3 At the shell, enter the sysBackupBoot command to put the controller card into the PXM backup prompt stage.

pxm1>sysBackupBoot

The PXM card resets.

Step 4 Log in to the PXM.

Step 5 Enter the cd "C:/FW" command at the pxm1bkup> prompt to get the FW directory.

pxm1bkup>cd "C:/FW"

Step 6 Enter the ls command to verify the boot firmware file is there.

pxm1bkup>ls

Step 7 Enter the sysFlashBootBurn <"boot firmware file name"> command to burn the image on the disk.

pxm1bkup>sysFlashBootBurn"3.0"

The system will ask if you want to proceed. Enter Y for Yes.

Step 8 At the pxm1bkup> prompt, enter the reboot command.

pxm1bkup> reboot

The node resets.

Step 9 Log in to the node.

Step 10 Log in to active PXM.

Step 11 Enter the dspcd <active card> command to determine if the upgrade was successful.

ses1.1.PXM.a> dspcd 1

Upgrading the SES PNNI Runtime Image

This section provides instructions for upgrading the runtime images from 1.1.75 to 3.0.

The upgrade of the runtime image on the redundant controller card is graceful. This means the traffic will not be disrupted. The new runtime image for 3.0 is pxm1_003.000.000.000_ses.fw.

Upgrading the Runtime Image on Redundant Systems

Follow these steps to upgrade the runtime image on redundant systems:


Step 1 Use FTP to transfer the runtime image to the card disk.

a. At the SES CLI, enter the dspipif command at the active controller card to find the node's IP address. The field internet address for lnPci 0 interface is the node IP address.

b. From the workstation containing the PXM backup boot image, enter ftp <Node IP address>.

c. Enter the username cisco.

d. Enter your password.


Note Your password is supplied with the image.


e. Enter the cd C:/FW command to get to the switch directory.

f. Enter the bin command (for a binary transfer).

g. Enter the put <runtime image name> command to transfer the runtime files from the server to the switch directory C:/FW. See the following example:

put pxm1_003.000.000.000_ses.fw

h. Enter the bye command to end your session.

Step 2 Enter the dspcds command to determine the standby slot.

Step 3 Enter the loadrev <standby slot> <image version> command to load the new version of runtime image on the controller card.

		ses1.1.PXM.a>loadrev 2 3.0(0.0)

The standby card resets and comes up in the new revision.

Step 4 When the standby card is in the STANDBY state, enter the runrev <standby slot> <image version> command to run the new version of runtime image on the controller card.

ses1.1.PXM.a>runrev 2 3.0(0.0)

The active card resets and the standby card takes over as active. Both cards are running the new revision.

Step 5 When the standby card is in STANDBY again, enter the abortrev <standby slot> <image version> command to abort this upgrade if needed, as in the following example:

ses1.1.PXM.a>abortrev 1 3.0(0.0)

Step 6 Enter the commitrev <standby slot> <image version> command to commit the new version of the runtime image of the controller card, as in the following example:

ses1.1.PXM.a>commitrev 2 3.0(0.0)

Step 7 Enter the dspcd command to verify a successful upgrade.

ses1.1.PXM.a>dspcd 1
ses1.1.PXM.a>dspcd 2

Upgrading the Runtime Image on Non-Redundant Systems

The upgrade of the runtime image on the a non-redundant controller card is non-graceful. That means the traffic is disrupted on the card during this operation.

For non-redundant systems, follow these steps.


Step 1 Use FTP to transfer the runtime image to the card disk.

a. At the SES CLI, enter the dspipif command at the active controller card to find the node's IP address. The field internet address for lnPci 0 interface is the node IP address.

b. From the workstation containing the PXM backup boot image, enter ftp <Node IP address>.

c. Enter the username cisco.

d. Enter your password.


Note Your password is supplied with the image.


e. Enter the cd C:/FW command to get to the switch directory.

f. Enter the bin command (for a binary transfer).

g. Enter the put <runtime image name> command to transfer the runtime files from the server to the switch directory C:/FW. See the following example:

put pxm1_001.001.075.101_ses.fw

h. Enter the bye command to end your session.

Step 2 Set the new version of the runtime image on the controller card as in the following procedure:

a. Enter the loadrev <slot> <image version> command as in the following example:

ses1.1.PXM.a>loadrev 1 3.0(0.0)

Note No cards will reset.


b. Reply Y (yes) to the proceed question.

c. Enter the dspcd command in the following example:

ses1.1.PXM.a>dspcd 1

The secondary revision on the PXM is set to new image version.

Step 3 Enter the runrev <slot> <image version> command to run the new version of runtime image on the controller card.

ses1.1.PXM.a>runrev 1 3.0(0.0)

The card will reset and run the new revision when it returns.

Step 4 Enter the dspcd command to verify a successful upgrade.

ses1.1.PXM.a>dspcd 1
ses1.1.PXM.a>dspcd 2

Step 5 At this point, you can still

Step 6 abort this upgrade if needed. To abort the upgrade, enter the abortrev command.

ses1.1.PXM.a> abortrev 1 3.0(0.0)

Step 7 Enter the commitrev <slot> <image version> command to commit the new version of the runtime image of the controller card.

ses1.1.PXM.a> commitrev <slot> <image version>

ses1.1.PXM.a> commitrev 1 3.0(0.0)

Step 8 Enter the dspcd command to verify that the runtime image is correct on the card.

ses1.1.PXM.a> dspcd 1


Upgrade Path

Release 3.0 supports upgrades from Release 1.1.75. If you are running a release prior to 1.1.75, you must upgrade to Release 1.1.75 before you upgrade to Release 3.0.

For information on upgrading to Release 1.0.76, refer to the 1.0.76 Version Software Release Notes Cisco SES Controller Software.

SES PNNI Controller Bring Up Procedure

For detailed procedure changes, refer to the Cisco SES PNNI Controller Software Configuration Guide at the following URL:

http://www.cisco.com/univercd/cc/td/doc/product/wanbu/bpx8600/pnni_ses/rel11/sescnf/index.htm

Limitations and Restrictions

The following sections describe issues in this release:

General Limitations and Restrictions

Recommendations

General Limitations and Restrictions

The following list describes limitations and restrictions that apply to this release:

A graceful upgrade can only be completed from the SES controller software Release 1.1.75.

The number of connections is always less then the max con value used in the addpart command. This is due to the fact that each card needs 1 LCN for control VC. If it is a PNNI network, there is another VC for RCC. Therefore, if the max con value is set to 9000 connections, only 8999 or 8998 connections can be added.

The dspcons command does not support ranges for VPI/VCI. If you enter dspcons -vpi 2, all SPVCs with a VPI less than and equal to 2 are displayed; not just the SPVCs with a VPI equal to 2.

The Route Optimization algorithm is node-by-node and is based on connection mastership. It is not distributed across the node. For example, if Node A is connected to Node C via Node B, Node A only knows about the connections from A to B, and not about the connections from B to C. This limitation does not allow Node A to use route optimization for connections from B to C.

There is no check for preventing multiple masters of SPVC connections from pointing to the same slave. When provisioning a second connection to a slave VPI/VCI that is already used, there will be no CLI warning that the connection has failed.

In a large network, it can take up to 30 seconds (or more) to accept new calls after a switchover. This is because PNNI relearns the topology on a switchover. For existing connections, the control plane and the data plane are not affected on a switchover.

Node names are not required for each node. A node name can be entered and distributed, but there is no check for node name uniqueness within the network. Multiple nodes with the same name do not cause inconsistencies in PNNI routing.

BXM interface (OC and T3) traffic policing only works if the cell rate is higher than 50 cells per second.

When the master endpoint is deleted on a DAX SPVC connection, the slave endpoint is also deleted.

The following limitation is in the BXM firmware release MFL and all the releases that follow: due to limited memory space on the BXM card and increased code size, channel statistics level 0 is no longer supported on BXM cards (BXM-155-4, BXM-155-8, BXM-622, BXM-622-2, BXM-T3-8, BXM-T3-12, BXM-E3-8, BXM-E3-12 models). When the BXM card firmware is upgraded to MFL or any post MFL release, regardless how many connections have been provisioned, channel statistics level 0 is no longer supported. If a BXM card has channel statistics level 0 turned on, use one of the following upgrade paths to upgrade BXM firmware to MFL or any post MFL release:

Change the BXM card to run channel statistics level 1. Statistics level 1 supports a maximum of
16 K connections on a card. If a card has more than 16 K connections configured, some connections must to be relocated to other BXM interfaces to reduce the total number of connections to be less than 16 K. Reset the card after changing to statistics level 1.

Upgrade the BXM card to the BXM-E card. The BXM-E card can continue running statistics level 0. Statistics level 0 can support a maximum of 32 K connections on a card.

Recommendations

The following recommendations apply to Release 1.1.75 of the SES controller:

SPVC connections are provisioned according to a two-ended provisioning model, similar to the way connections are provisioned using AR. This provisioning model enables more robust management (including fault conditions) of both connection endpoints, as opposed to a model which only provisions the master endpoint.

In order to establish a double-ended DAX or a double-ended routed SPVC, provision the slave endpoint before provisioning the master endpoint. The traffic parameters and QoS parameters on both the master and slave endpoints must match in order to establish an SPVC. To establish a single-ended SPVC connection, you only need to provision the master endpoint.

For each SPVC addition, deletion, or modification, the SES controller generates a trap to CWM. This trap enables CWM to sync up its connection management database with the BPX SES node in real time. The trap information exchange between CWM and SES is handled by an inter-system communication protocol. The trap-handling rate is much slower than the script driven SPVC setup or delete rate. When you use a script to do burst SPVC addition or deletion, the trap queue may overflow and cause trap loss due to limited trap queue size. If burst SPVC add/delete size is more than 1 K connections, Cisco recommends that you pace your setup/delete rate to be 1 connection per second to avoid trap loss.

The minSvccVci value for the partition is defaulted to 35. VCI 33 and 34 are marked for future control plane use.

In the case of obtaining optimized routes while performing PNNI on demand route lookup, Cisco recommends that you change the routing policy to the best fit option

Caveats

This section provides information on the open anomalies in Release 3.0.

Open Anomalies in This Release

The following table describes known anomalies in this SES controller software delivery. A more in depth discussion of each bug is available in the release note enclosure in Bug Navigator.

Table 5 Open Anomalies for Release 3.0

Bug ID
Description
S2 BUGS
 

CSCdx60401

Symptom:

Node continuously resets.

Conditions:

Hello packet flooding at line rate.

Workaround:

Unknown

CSCdw03688

Symptom:

Software error on handler when executing runrev while upgrading.

Condition:

48k DAX SPVCs and 11k routed SPVCs on the SES-BPX node.

Workaround:

None.

CSCdx35791

Symptom:

PXM45 fails to come up. If it were a standby PXM, the dspcds on the active PXM indicates that the Standby PXM slot is empty. Output from the debug console shows junk characters.

Condition:

When the PXM45's console port is connected through a terminal server with echo mode turned on, junk characters come into the console port of the PXM45. When this card is reset, the runtime image stops its initialization when it received these junk characters on the console port.

Workaround:

1. Configure the terminal server to disable the echo mode.

2. Alternatively, pull out the console port cable and reset the card.

CSCdw51798

Symptom:

S-PVC Calling/Called PVCC IE is not be corrected encoded.

Conditions:

PNNI conformance test failed under section R3.1.1.4/R3.1.1.5 The following test verifies the initiating PVPC/PVCC establishment procedure as outlined in AF-CS-0127.000 Section 9.2.1 and PICS conformance as described in ATM Forum AF-CS-0127.000 PNNI SPVC Addendum Version 1.0, July, 1999 and ATM Forum AF-CS-012@7.000PNNI SPVC Addendum Version 1.0, July, 1999.

Workaround:

None.

CSCdw57706

Symptom:

The VCI values are given with a value of "0" for the Calling and Called Party Soft PVPC or PVCC Information Element. The requirement states (This octet - VCI is only present in case of a soft PVCC.

Conditions:

Called/Calling Soft PVPC or PVCC Information Element as described in Section 6.4.6.1 and Section 6.4.6.2 of AF-CS-0127.000.

Workaround:

None.

CSCdw61915

Symptom:

Event logged specified incorrect time data by LMI. Date is being set by BPX on SES feeder.

Conditions:

A new field was added to time structure. This field is not initialized by LMI and can take various values. Under certain conditions, this value is in error and causes the event to be logged.

Workaround:

None.

CSCdw64939

Symptom:

BPX-SES is responding with an incorrect Cause 43d rather than 100d when a SETUP message is received with an "access information element" with invalid content. Per Non conformance to Q2931 para. 5.6.8.2.

Conditions:

None.

Workaround:

None.

CSCdw74433

Symptom:

PNNI conformance test failed in Q2931 para 5.6.8.2, When a SETUP message is received with invalid length in a non-mandatory IE, The BPX/SES is not taking action on the call.

Conditions:

Running a test suite.

Workaround:

None.

CSCdx32349

Symptom:

SES did not add SPVC endpoint.

Conditions:

None.

Workaround:

None.

CSCdx40378

Symptom:

When sending F5 OAM end to end flows through a DACS SPVC, only the "egress" counters of dspconstats increment. This true for F5 end to end AIS, or F5 end to end loopback.

Conditions:

None.

Workaround:

None.

CSCdx40400

Symptom:

When the tstdelay command is entered on an SPVC on the SES, the "Cells sent total local egress" counter increments, which suggests that a tstdelay (which measures delay inside the network) results in cells being sent over a UNI, outside of the network (that would be wrong). However, using an HP BSTS to monitor traffic on the other side of the interface, it is clear that no cells are sent. So the counter increment is bogus.

Conditions:

None.

Workaround:

None.

CSCdx45385

Symptom:

On the SES, the dsppnportrsrc command is used to check the available VSI resources on a port. Testing shows that dsppnportrsrc keeps aligned with the exact state of VSI resources when an SPVC endpoint is added to the port. However, the dsppnportrsrc display is not updated following a change of the VSI resources done using the cnfrsrc <slot.port> command on a BPX. This is especially troublesome when a port runs out of LCNs. The dsppnportrsrc command display shows "# Avl Tx Chans:" = 0. After going on the BPX and increasing the size of the VSI partition, the dsppnportrsrc command display still shows the number of available LCN as being 0, so the SES will reject any provisioning attempt on that port, even though there truly are resources available to accept the SPVC endpoint.

Conditions:

Following are screenshots of an example triggering of the problem:

On the BPX, on a BXM-T3-12 card, up a single port. The card must have only port (to facilitate VSI management). The bug also happens with more than one port.

Configure the port as follows:

Up the port.

Enable a VSI partition on the port, with overlapping VPI range, half the BW and min VSI LCN = 0, Max VSI LCN = 1. cnfvssiif <slot.port> 2 cnfrsrc.

On the SES, do a dsppnportrsrc and check the number of available LCNs as seen by the SES (the UNI Signalling Channel is disabled, "cnfpnportsig 3.1 - univer none".

On the BPX, increase the number of Max VSI LCNs from 1 to 5.

On the SES, dsppnportrsrc still shows 1. This never gets updated it seems

Provision an SPVC endpoint against that port. That gets dsppnportrsrc to be updated to the correct value (4).

Provision 4 additional SPVC endpoints against that port. This exhausts the VSI LCNs on the port and gets dsppnportrsrc to show "0".

On the BPX, via cnfrsrc, increase the Max VSI LCN for the port from 5 to 10.

Check dsppnportrsrc on the SES. It still shows 0 available LCNs for nrtvbr.

As a result the SES rejects a provisioning attempt for nrtvbr SPVC endpoint on that port.

On the BPX, increase Max VSI LCN for that port from 10 to 15.

On the SES dsppnportrsrc is still not accurate and still maintains a discrepancy between nrtvbr and other ATM Service Categories.

Workaround:

None.

CSCdx76273

Symptom:

The cnfqosdefault command is unusable and does not provide what the ATM Forum specifications intended. The cnfqosdefaut command should be port-specific and NOT node-wide.

Condition:

SES is running 1.1.75.103.

Workaround:

None.

CSCdx78946

Symptoms:

MGX 8230/ SES dspsigstats shows "Connect Ack" Messages on AINI SES 1.1.75.103

Conditions:

The configuration is: - 2 SES connected via an AINI. - One SPVC configured with Master endpoint on one SES and Slave endpoint on the other. The problem is that according to ATM Signalling standards the "CONNECT ACK" message only exists in UNI Signalling. It does not exist in AINI. AINI implementation generates a CONNECT ACK message and as a result does not conform with the ATM Forum specification af-cs-0125.000.

Workaround:

Unknown.


Open Anomalies in Release 1.1.75

The following table describes the open anomalies in the 1.1.75 SES controller software delivery. A more in depth discussion of each bug is available in the release note enclosure of the problem record in Bug Navigator.

Table 6 Open Anomalies for Release 1.1.75 

Bug ID
Description
S2 BUGS
 

CSCdt12655

Symptom:

Too many stat collection FTP errors.

Conditions:

Unknown.

Workaround:

None.

CSCdw03688

Symptom:

Software error on handler when executing runrev while upgrading.

Condition:

None

Workaround:

None.

S3 BUGS

 

CSCds74052

Symptom:

Given a redundant SES node, pull out the trunk back-card from the active PXM's slot. This causes the active PXM to reboot and the standby PXM to take over as the active front-card. The previously-active PXM card should come up as the standby card but instead, it keeps rebooting.

Condition:

Not known as yet. It is suspected that some task is trying to access the NOVRAM on the (absent) trunk back-card.

Workaround:

None. The only thing to do is not to pull out the trunk back-card while the front-card is either in the active or standby role.

CSCdv22425

Symptom:

Standby card goes into rolling boot.

Condition:

Enter the resetcd command to reset the standby card.

Workaround:

None

CSCdw15621

Symptom:

Cannot enable diagnostics on SES PNNI.

Condition:

Enter the cnfdiag command to enable diagnostics (online/offline).

Workaround:

None

CSCdw57706

Symptom:

The VCI values are given with a value of "0" for the Calling and Called Party Soft PVPC or PVCC Information Element. The requirement states (This octet - VCI is only present in case of a soft PVCC.

Condition:

Called/Calling Soft PVPC or PVCC Information Element as described in Section 6.4.6.1 and Section 6.4.6.2 of AF-CS-0127.000

Workaround:

None

CSCdw64939

Symptom:

BPX-SES is responding with an incorrect Cause 43d rather than 100d when a SETUP message is received with an "access information element" with invalid content. Per Non conformance to Q2931 para. 5.6.8.2

Condition:

None

Workaround:

None


Problems Fixed in Release 1.1.75

The following table describes the anomalies fixed in the 1.1.75 SES controller software delivery. A more in depth discussion of each bug is available in the release note enclosure of the problem record in Bug Navigator.

Table 7 Anomalies Fixed in Release 1.1.75 

Bug ID
Description
S1 BUGS
 

CSCdv59710

PNNI link corrupted after upgrade from 1.0.15 to 1.1(60.101)

Symptom:

PNNI link in attempt state. PNNI VC entry is corrupted.

Condition:

SES upgrade from 1.0.15 to 1.1(60.101).

Workaround:

None. Fixed in 1.1.75.

CSCdw34252

SES doesn't support MBS less than 9.

none.

CSCdw56907

An error can occur with management protocol processing. Please use the following URL for further information:

http://www.cisco.com/cgi-bin/bugtool/onebug.pl?bugid=CSCdw65903

S2 BUGS
 

CSCdv63740

After changing SES node name to small one, conn shows part of old name.

Symptom:

After changing SES node name to small one, conn shows part of old name.

Condition:

Occurs whenever user assigns a shorter node name to an SES node with a long node name.

Workaround:

None. Fixed in 1.1.75.

CSCdv74376

a-bit alarms not cleared after a a switch y-red

Symptom:

Few AXIS connections are in a-bit alarms

Condition:

Occurs whenever user executes a switch y-red on BXM while connections are in a-bit alarms

Workaround:

Execute switch y-red again OR

Execute dncon and upcon on connections that have a-bit alarms (this is service affecting)

CSCdv79733

DEV: ADDR-5-ADDR_ERROR in dsperrs after reroutes

$$prefcs

CSCdv83155

CLI: compilation error due to basic CLI prototype definition

$$prefcs

CSCdw08130

REG21:add/cnfcon is allowed on slave side for SES.

Symptom:

dspcon shows frame discard enable on slave side, which has to be on SES.

Condition:

cnfcon/addcon with frame discard enable on SES, which is the slave side.

Workaround:

None.

CSCdw10812

Few SPVC are in temporary failure.

$$prefcs

CSCdw36332

Statistics for connections can't be cleared / reset.

Symptom:

The statistics collection can not be cleared for the connection level statistics and all the counters remain the same after CLI command is executed to clear the statistics.

Condition:

The statistics collected for a connection cannot be cleared by executing CLI command.

Workaround:

Not known yet other than reset etc.

CSCdw44217

CBR.1 S-PVC is allows only through-put 50pcs.

Symptom:

The CBR.1 S-PVC with PCR = 1000 cps only allowed traffic through-put at a rate of 50 cps.

Condition:

1. Initiate a CBR.1 S-PVC and verify that the UPC functions as specified by the traffic contract.

PCR = 1000 cps

CDVt = 150 us

CDV = 10000 us

CTD = 150 ms

2. Generate user traffic at a rate of 500 cps.

Workaround:

Reset interface cards (BXM) then the traffic can run at rate of 500 cps.

CSCdw43522

pnCcb suspended by switchcc on the new active card.

Symptom:

Standby card undergoes system reload on switchcc.

Conditions:

If node atm prefix is added as an address on a port and the node is a PGL node which has an SVCC based RCC to PEER MPG LGN.

Workaround:

Adding of node prefix as an address on ports is not supported and this address should be deleted. The higher level PNNI node may also be configured with a different ATM address that does not fall under this prefix. This is a configuration problem and will not happen in properly configured nodes.

CSCdw46658

Counting of control connections on NNI interfaces.

Symptom:

Control connections are not counted at the originating node. This can lead to mismatch in number of connections at two ends of trunk.

Conditions:

Control connections are not counted at the originating node.

Workaround:

None.

CSCdw47729

Size mismatch when FTPing statistics files from SES node.

Symptom:

CWM cannot get SES SPVC stats.

Conditions:

Due to new changes in CWM, the FTP client in CWM tries to match the size of the file downloaded with the size given via an ftp lib command. This fails and the CWM rejects the downloaded file.

Workaround:

None.

CSCdw62579

Should be able to do snmp get for CBR CDVT,show should on cli as well

Symptom:

snmp get for CBR CDVT returns wrong value

Condition:

Can't do snmp get for CBR CDVT value

Workaround:

No work around for snmp get and set (equivalent of cli cnfcon). cdvt can still be set as part of snmp get request (equivalent of cli addcon).

CSCdw74115

IPCONN: changes to handle low network memory problems

Symptom:

Workstation or network management system cannot reach node via TCP/IP. Ping, telnet, etc. no longer work.

Condition:

IP Connectivity cache and IP routing in an inconsistent state. IP route exists for atm interface (routeShow) but corresponding interface cache entry does not exist (dspipifcache).

Workaround:

IP route must be manually deleted using routeDelete command.

S3 BUGS
 

CSCdw15621

REG21:Cannot enable off/online diag on SES

Symptom:

Cannot enable diagnostics on SES PNNI.

Condition:

Enabling diagnostics (online/offline) using cnfdiag.

Workaround:

None

CSCdw25965

REG21:cnfcon -frame option does not work on SES

Symptom:

dsppncon shows frame discard to be disabled.

Condition:

Use cnfcon to enable frame discard.

Workaround:

Add connection using the -frame option.

CSCdw44760

Symptom:

Can not telnet to the standby controller during backup boot upgrade.

Condition:

Workaround:

None.

CSCdv38486

REG21:No/Incorrect error displayed when level 105 is assigned.

Symptom:

No/Incorrect error displayed when level changed to 105.

Condition:

Change the level to 105.

Workaround:

None.

CSCdv69644

Environmental Device Traps must be self contained: PER 3917.

Symptom:

The information in Environmental device traps are not sufficient to figure out for which device it is applicable

Condition:

When any Environmental Device traps are sent

Workaround:

Look at the cwTrapIndex value and perform SNMP Walk on entPhysicalTable with the INDEX value obtained from cwTrapIndex varbind.


Problems Fixed in Release 1.1.70

The following table describes anomalies fixed in the 1.1.70 SES controller software delivery. A more in depth discussion of each bug is available in the release note enclosure of the problem record in Bug Navigator.

Table 8 Anomalies Fixed in Release 1.1.70 

Bug ID
Description
S1 BUGS
 

CSCdv48381

Bulk set on proxy slave not functioning.

CSCdv54458

Upgrade from 1.0 to 1.1.60 does not work due to SHM_REP_RAM_NODE_DB change.

CSCdv57330

Connection addition fails (disk update failing).

CSCdv59710

PNNI link corrupted after upgrade from 1.0.15 to 1.1(60.101).

CSCdv84753

Call stuck in setup state.

S2 BUGS
 

CSCdt08059

DLS—Telnet daemon allows access without authentication.

CSCdt78006

DLS—switchcc resulted in temporary connection mismatch on 2 nodes.

CSCdu22913

Pulling out feeder trunk led to pnredman reset stdby (window timeout).

CSCdu24540

1.0.13verify:dbsvr failed to upgrade after stdby pxm1 reset.

CSCdv49665

JAN: AIS sent down to VSIS, but not to LSM in slot1 only.

CSCdv58746

60302 not send out when conn created failed, chanID reused in new con.

CSCdv63740

After changing SES node name to small one, conn shows part of old name.

CSCdv67375

SLT: PXM got rst in SES shelf and IPC buffer leaks after configuration.

CSCdv79733

DEV: ADDR-5-ADDR_ERROR in dsperrs after reroutes.

CSCdv81833

Port stuck in down in progress.

CSCdw07942

REG21:cnfcon -frame option does not work on SES shelf.

CSCdw09142

addshelf command not working in the SES image.

CSCdw10812

Few SPVC are in temporary failure.

CSCdw17431

REG21: standby PXM1 failed after clrallcnf/restoreallcnf in SES PNNI.

S3 BUGS

 

CSCdv12060

BPX report wrong intf physical ID, dsppnport not work, pnccb runaway.

CSCdv27904

Duplicate error message in spvc2cli_errcd.

CSCdv37284

Evt.Log: <ccc session> continuous error message.

CSCdv46656

MGX/BPX: Incompatible info_length interpretation in sys_cap IG.


Anomalies Status Changes for Release 1.1.70

The following table describes anomalies set to a state other than resolved in this SES controller software delivery. A more in depth discussion of each bug is available in the release note enclosure of the problem record in the Bug Navigator.

Table 9 Anomalies Status Changes for Release 1.1.70

Bug ID
Description
S2 BUGS
 

CSCdu19130

1.0.13Verify:node crashes after abortrev on other node in network; duplicated.


Fixed Anomalies for Release 1.1.60

The following table describes fixed anomalies in the Release 1.1.60 SES controller software delivery. A more in depth discussion of each bug is available in the release note enclosure of the problem record in the Bug Navigator.

Table 10 Fixed Anomalies for Release 1.1.60 

Bug ID
Description
S2 BUGS
 

CSCdt08059

Symptoms:

The telnet daemon allowed user access into the switch without authentication.

Conditions:

While in boot mode, you can telnet to the node. Access via telnet during boot mode is not restricted.

Workaround:

None.

CSCdt12655

Symptoms:

Too many stat collection FTP errors.

Conditions:

Unknown.

Workaround:

None.

CSCdu19130

Symptoms:

After entering the abortrev command on one node in the network, the other node with 50 K routed connections crashed. It did not respond to certain CLI commands, such as dsppnports and dspcons.

Conditions:

There are 50 K routed connections between node pswpop7/pswbpx2 and orses18/svcbpx23 via node pswpop6/pswbpx6. I entered the loadrev and runrev commands to upgrade the orses18 node from 1.0 to 1.1. Everything was fine after upgrade. I then entered the abortrev command to bring the orses18 node back to the 1.0 image. After entering the abortrev command on the pswpop7 node, it suddenly crashed; many tasks were deleted. The pswpop7 node did not respond to some CLI commands, such as dsppnports, dspcons, and dspconinfo. However, the dspdate, dsplogs, and dsperrs commands worked fine.

Workaround:

None.

CSCdu22913

Symptoms:

The SSI_SRAM_WIN_TIMEOUT Redman Error caused the standby PXM reset.

Condition:

There were about 50 k routed SPVC connections between two Orion/BPX nodes. One Orion node had redundant PXM cards. I pulled out the Y-cable on the feeder trunk. The RedmanError SSI_SRAM_WIN_TIMEOUT caused the standby PXM to reset.

Workaround:

Unknown.

CSCdu24540

Symptoms:

After running the script to dncon/upcon on an SES node, the dbsvr command failed to upgrade after the standby PXM reset.

Condition:

There were about 50 K routed SPVC connections between node orses18/svcbpx23 and node pswpop7/pswbpx2. I ran script to dncon/ upcon on orses18, at the same time reset standby PXM1 on orses18. dbsvr failed to upgrade.

Workaround:

Unknown.

CSCdt78006

Symptoms:

Connections went into mismatch after replacing the PXMs in a node and entering the switchcc command.

Conditions:

A customer was going through an exercise of replacing PXMs on their nodes. On two nodes, the standby PXM was replaced, and the switchcc command was entered to make the new PXM the active one. Connections went into mismatch state for a short while, and then cleared. We were not able to get into the node to collect information while this condition existed.

Workaround:

Unknown.

S3 BUGS

 

CSCds74052

Symptoms:

I pulled out the trunk back-card from the active PXM's slot on a redundant SES node. This caused the active PXM to reboot and the standby PXM to take over as the active front-card. The previously-active PXM card should have come up as the standby card, but it kept rebooting.

Condition:

Unknown. It is suspected that some task is trying to access the NOVRAM on the (absent) trunk back-card.

Workaround:

None. Do not pull the trunk back-card out while the front-card is in the active or standby role.


Related Documentation

The following Cisco publications contain additional information related to the operation of this product and associated equipment in a Cisco WAN switching network.

Cisco WAN Manager Release 11

The product documentation for the Cisco WAN Manager (CWM) network management system for Release 11 is listed in Table 1.

Table 1 Cisco WAN Manager Release 11 Documentation 

Title
Description

Cisco WAN Manager Installation Guide for Solaris 7, Release 11

DOC-7813567=

Provides procedures for installing Release 11 of the CWM network management system and Release 5.4 of CiscoView.

Cisco WAN Manager User's Guide, Release 11

DOC-78-13568=

Describes how to use the CWM Release 11 software, which consists of user applications and tools for network management, connection management, network configuration, statistics collection, and security management.

Cisco WAN Manager SNMP Service Agent, Release 11

DOC-7813569=

Provides information about the CWM Simple Network Management Protocol Service Agent, an optional adjunct to CWM that is used for managing Cisco WAN switches using SNMP.

Cisco WAN Manager Database Interface Guide, Release 11

DOC-7813542=

Provides information about accessing the CWM Informix OnLine database that is used to store information about the network elements.


Service Expansion Shelf PNNI Controller Release 3

The product documentation for the installation and operation of the Service Expansion Shelf (SES) PNNI Controller is listed in Table 2.

Table 2 SES PNNI Controller Release 3 Documentation 

Title
Description

Cisco SES PNNI Controller Software Configuration Guide, Release 3

DOC-7814258=

Describes how to configure, operate, and maintain the SES PNNI Controller.

Cisco SES PNNI Controller Command Reference, Release 3

DOC-7814260=

Provides a description of the commands used to configure and operate the SES PNNI Controller.

Cisco MGX and SES PNNI Network Planning Guide for MGX Release 3 and SES Release 3

DOC-7814261=

Provides guidelines for planning a PNNI network that uses the MGX 8850 and the MGX 8950 switches and the BPX 8600 switches. When connected to a PNNI network, each BPX 8600 series switch requires a SES for PNNI route processing.


Cisco WAN Switching Software Release 9.3.40

The product documentation for the installation and operation of the Cisco WAN Switching Software Release 9.3.40 is listed in Table 3.

Table 3 Cisco WAN Switching Software Release 9.3.40 Documentation 

Title
Description

Cisco BPX 8600 Series Installation and Configuration, Release 9.3.30

DOC-7812907=

Provides a general description and technical details of the BPX broadband switch.

Cisco WAN Switching Command Reference, Release 9.3.30

DOC-7812906=

Provides detailed information on the general command line interface commands.

Cisco IGX 8400 Series Installation Guide

OL-1165-01 (online only)

Provides hardware installation and basic configuration information for IGX 8400 Series switches that are running Switch Software Release 9.3.30 or earlier.

Cisco IGX 8400 Series Provisioning Guide

OL-1166-01 (online only)

Provides information for configuration and provisioning of selected services for the IGX 8400 Series switches that are running Switch Software Release 9.3.40 or earlier.

Cisco IGX 8400 Series Regulatory Compliance and Safety Information

DOC-7813227=

Provides regulatory compliance, product warnings, and safety recommendations for the IGX 8400 Series switch.

9.3.40 Version Software Release Notes for Cisco WAN Switching System Software

78-13538-01

Provides new feature, upgrade, and compatibility information, as well as known and resolved anomalies.


Conventions

This publication uses the following conventions.

Command descriptions use these conventions:

Commands and keywords are in boldface.

Arguments for which you supply values are in italics.

Required command arguments are inside angle brackets (< >).

Optional command arguments are in square brackets ([ ]).

Alternative keywords or variables are separated by vertical bars ( | ).

Examples use these conventions:

Terminal sessions and information the system displays are in screen font.

Information you enter is in boldface screen font.

Nonprinting characters, such as passwords, are in angle brackets (< >).

Default responses to system prompts are in square brackets ([ ]).

Notes use the following conventions and symbols


Note Means reader take note. Notes contain helpful suggestions or references to materials not contained in this manual.


Obtaining Documentation

The following sections explain how to obtain documentation from Cisco Systems.

World Wide Web

You can access the most current Cisco documentation on the World Wide Web at the following URL:

http://www.cisco.com

Translated documentation is available at the following URL:

http://www.cisco.com/public/countries_languages.shtml

Documentation CD-ROM

Cisco documentation and additional literature are available in a Cisco Documentation CD-ROM package, which is shipped with your product. The Documentation CD-ROM is updated monthly and may be more current than printed documentation. The CD-ROM package is available as a single unit or through an annual subscription.

Ordering Documentation

Cisco documentation is available in the following ways:

Registered Cisco.com users (Cisco direct customers) can order Cisco product documentation from the Networking Products MarketPlace:

http://www.cisco.com/cgi-bin/order/order_root.pl

Registered Cisco.com users can order the Documentation CD-ROM through the online Subscription Store:

http://www.cisco.com/go/subscription

Nonregistered Cisco.com users can order documentation through a local account representative by calling Cisco corporate headquarters (California, USA) at 408 526-7208 or, elsewhere in North America, by calling 800 553-NETS (6387).

Documentation Feedback

If you are reading Cisco product documentation on Cisco.com, you can submit technical comments electronically. Click the Fax or E-mail option under the "Leave Feedback" at the bottom of the Cisco Documentation home page.

You can e-mail your comments to bug-doc@cisco.com.

To submit your comments by mail, use the response card behind the front cover of your document, or write to the following address:

Cisco Systems
Attn: Document Resource Connection
170 West Tasman Drive
San Jose, CA 95134-9883

We appreciate your comments.

Obtaining Technical Assistance

Cisco provides Cisco.com as a starting point for all technical assistance. Customers and partners can obtain documentation, troubleshooting tips, and sample configurations from online tools by using the Cisco Technical Assistance Center (TAC) Web Site. Cisco.com registered users have complete access to the technical support resources on the Cisco TAC Web Site.

Cisco.com

Cisco.com is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information, networking solutions, services, programs, and resources at any time, from anywhere in the world.

Cisco.com is a highly integrated Internet application and a powerful, easy-to-use tool that provides a broad range of features and services to help you to

Streamline business processes and improve productivity

Resolve technical issues with online support

Download and test software packages

Order Cisco learning materials and merchandise

Register for online skill assessment, training, and certification programs

You can self-register on Cisco.com to obtain customized information and service. To access Cisco.com, go to the following URL:

http://www.cisco.com

Technical Assistance Center

The Cisco TAC is available to all customers who need technical assistance with a Cisco product, technology, or solution. Two types of support are available through the Cisco TAC: the Cisco TAC Web Site and the Cisco TAC Escalation Center.

Inquiries to Cisco TAC are categorized according to the urgency of the issue:

Priority level 4 (P4)—You need information or assistance concerning Cisco product capabilities, product installation, or basic product configuration.

Priority level 3 (P3)—Your network performance is degraded. Network functionality is noticeably impaired, but most business operations continue.

Priority level 2 (P2)—Your production network is severely degraded, affecting significant aspects of business operations. No work-around is available.

Priority level 1 (P1)—Your production network is down, and a critical impact to business operations will occur if service is not restored quickly. No work-around is available.

Which Cisco TAC resource you choose is based on the priority of the problem and the conditions of service contracts, when applicable.

Cisco TAC Web Site

The Cisco TAC Web Site allows you to resolve P3 and P4 issues yourself, saving both cost and time. The site provides around-the-clock access to online tools, knowledge bases, and software. To access the Cisco TAC Web Site, go to the following URL:

http://www.cisco.com/tac

All customers, partners, and resellers who have a valid Cisco services contract have complete access to the technical support resources on the Cisco TAC Web Site. The Cisco TAC Web Site requires a Cisco.com login ID and password. If you have a valid service contract but do not have a login ID or password, go to the following URL to register:

http://www.cisco.com/register/

If you cannot resolve your technical issues by using the Cisco TAC Web Site, and you are a Cisco.com registered user, you can open a case online by using the TAC Case Open tool at the following URL:

http://www.cisco.com/tac/caseopen

If you have Internet access, it is recommended that you open P3 and P4 cases through the Cisco TAC Web Site.

Cisco TAC Escalation Center

The Cisco TAC Escalation Center addresses issues that are classified as priority level 1 or priority level 2; these classifications are assigned when severe network degradation significantly impacts business operations. When you contact the TAC Escalation Center with a P1 or P2 problem, a Cisco TAC engineer will automatically open a case.

To obtain a directory of toll-free Cisco TAC telephone numbers for your country, go to the following URL:

http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml

Before calling, please check with your network operations center to determine the level of Cisco support services to which your company is entitled; for example, SMARTnet, SMARTnet Onsite, or Network Supported Accounts (NSA). In addition, please have available your service agreement number and your product serial number.