Guest

Cisco SES PNNI WAN Software

4.0.10 Software Release Notes for the SES Controller

  • Viewing Options

  • PDF (585.6 KB)
  • Feedback
4.0.10 Software Release Notes for the Cisco SES PNNI Controller

Table Of Contents

4.0.10 Software Release Notes for the Cisco SES PNNI Controller

Contents

About Release 4.0.10

SES PNNI and SVC Controller

Feature Overview

New and Changed Information for Release 4.0.10

Resource Monitoring

New and Changed Information for Release 4.0.00

Closed User Groups

Preferred Routes for PNNI Multipeer Group Networks

Point-to-Multipoint SVC/SPVC Support

IGX as an AAL5 Feeder

Detailed Feature Information

System Requirements

Hardware Compatibility Matrix

Software Compatibility

Certified Releases

Additional Deliverables

Upgrade Notes and Cautions

Upgrading the SES Node

Upgrading to a New Software Release

Special Installation and Upgrade Requirements

Upgrading from SES Release 1.1.75, Release 3.0.23, or Release 4.0 to Release 4.0.10

Upgrading the Backup Boot Image

Upgrading the Backup Boot on Non-Redundant Systems

Upgrading the Cisco SES PNNI Runtime Image

Upgrading the Runtime Image on Redundant Systems

Upgrading the Runtime Image on Non-Redundant Systems

Cisco SES PNNI Controller Bring Up Procedure

Limitations and Restrictions

General Limitations and Restrictions

Recommendations

Caveats

Open Anomalies in Release 4.0.10

Anomalies Fixed in Release 4.0.10

Anomalies Status Change from Previous Release 4.0

BXM Firmware MFY Release Notes

About the Firmware MFY

Front Cards

Front Card for APS Compatibility

Back Cards

New Features supported in BXM Firmware MFY

Support for Pseudo AIS

Special Installation/Upgrade Requirements

APS Issues

Channel Statistics Issues

Features Obsoleted

Notes, Cautions, and Clarifications

Known Anomalies in MFY

BXM Firmware Filenames and Sizes

Anomalies Fixed in MFY

Anomalies Fixed in MFX

Anomalies Fixed in MFW

Related Documentation

Cisco WAN Manager Release 12

SES PNNI Release 4.0.10

Cisco WAN Switching Software Release 9.4

Conventions

Obtaining Documentation

Cisco.com

Documentation CD-ROM

Ordering Documentation

Documentation Feedback

Obtaining Technical Assistance

Cisco.com

Technical Assistance Center

Cisco TAC Website

Cisco TAC Escalation Center

Obtaining Additional Publications and Information


4.0.10 Software Release Notes for the Cisco SES PNNI Controller


Contents

This document contains the following sections:

About Release 4.0.10

Release 4.0.10 supports the Cisco BPX 8600 series with SES controller.

These release notes describe the system requirements, and Cisco support information, new and changed procedures, upgrade procedures, and limitations that apply to Release 4.0.10 of the Service Expansion Shelf (SES) controller.

SES PNNI and SVC Controller

Release 4.0.10 of the SES controller is compatible with the Cisco BPX 8600 series software Release 9.4.10. The SES controller is connected to the Cisco 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 enables the Cisco BPX 8600 switch 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 Cisco 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.

New and Changed Information for Release 4.0.10

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

Resource Monitoring

The resource monitoring feature periodically checks the switch resources and takes appropriate actions when there is a resource shortage or a a resource recovery. The following resources are monitored:

Memory (all SSI partitions and VxWorks(TM) partition)

Hard Disk space

IPC buffers

CPU

SSI Sync Timers

SSI File Descriptors

VxWorks file descriptors

System up time

If there is a resource shortage or a resource recovery, the resource monitoring feature performs the following actions when appropriate:

Alarm

Trap

Log

Use the following new CLI commands to configure and display information about switch resources:

cnfrmrsrc —configure resource monitoring behavior

dsprmrsrc—display particular resource information in detail

dsprmrsrcs—display all the resources in summary

dsprmalms—display resource related alarms


Note The dspcdalm command has been modified to include a resource monitoring category.


New and Changed Information for Release 4.0.00

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

Closed User Groups

The Closed User Groups (CUG) supplementary service enables network users to form groups, to and from which access is restricted. A network user may be associated with one CUG, multiple CUGs, or no CUG. Members of a specific CUG typically communicate among themselves, and not with network users outside of the CUG. Specific network users can have additional restrictions preventing them from originating calls to, or receiving calls from, network users within the same CUG (Outgoing Calls Blocked or Incoming Calls Blocked). In addition, a network user can be further restricted in originating calls to, or receiving calls from, network users outside of any CUG membership defined for the network user (Outgoing Access or Incoming Access).

Consider the following information when configuring CUGS:

The CUG feature is based on the ITU-T Q.2955.1 recommendation.

This feature is aligned with the 4.0 release. All the features supported by the previously deployed releases for the MGX 8850/8830/8950, and SES will be supported and seamless upgrade capabilities will be provided.

CUGs can only be applied to SVCs. CUGs are not supported on SPVCs.

Preferred Routes for PNNI Multipeer Group Networks

Preferred routing of connections allows the network operator to bypass PNNI route selection and configure a specific path through the network which a connection will follow. Preferred routes can be configured as either Preferred or Directed routes. A Preferred route follows the configured path if it is available, but reverts to a PNNI-selected route if the preferred route is unavailable. A Directed route follows only the configured path; if the configured path is not available, the connection remains unrouted.

Use the CLI or SNMP to specify preferred routes for SPVCs, from the source switch to the destination switch. The end-to-end preferred route for SPVCs can span across multiple peer groups. The implementation is based on PNNI 1.1 specification.

Point-to-Multipoint SVC/SPVC Support

The SVC/SPVC point-to-multipoint (P2MP) feature enables one root SVC/SPVC connection to establish a simple tree topology to one or more leaf connections. The data traffic is uni-directional, from root multicast to all leaves. In other words, what is sent from the root data channel is received by all leaves. From the root, leaves can be added to the connection via SETUP/ADD_PARTY signaling messages. P2MP is a mandatory feature described in UNI 3.0, UNI3.1 and UNI4.0 specs. The implementation is compliant with Q2971.

IGX as an AAL5 Feeder

This feature enables the IGX to act as an AAL5 feeder to the PXM45-based Cisco MGX 8850, the PXM1E-based Cisco MGX 8850 and Cisco MGX 8830, or the BPX+SES. In prior releases, the IGX could only be a feeder to the BPX (or another IGX). The two nodes communicate by using Annex G LMI over a proprietary Auto Route Networking Channel.

This new IGX AAL5 feeder support encapsulates the LMI messages in ATM AAL5 cells on a UXM feeder trunk that is connected to a BXM card.

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 Cisco BPX 8600 series switch with a centralized controller for establishing SPVCs and SVCs in both Cisco BPX 8600 series networks and in mixed vendor environments.

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

SPVC and SVC real time statistics with MIB support

SNTP

Priority routing of connections

Standards based path and connection trace facilities

Single-ended and double-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,000 LCN on BXM-E

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 the Cisco BPX 8600

Connection and Path Trace facilities

Integrated management via CWM and SNMP MIBs

100, 000 connections (SVC+SVP+SPVC+SPVP) per node. 100,000 connection for DACS only, or routed SPVCs only, or mixed.

200,000 max endpoints per node (if all 100,000 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

SPVC Connection Statistics

Closed User Group

Preferred Routes

Point to Multipoint SVC/SPVC

IGX as an AAL5 Feeder

Resource monitoring

System Requirements

This section describes the hardware supported and the software compatibility requirements in Release 4.0.10.

Hardware Compatibility Matrix

Table 1 and Table 2 list the hardware supported in Release 4.0.10, 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 8850/8220/8230 Release1 hardware which is compatible with Release 4.0.10 of the SES controller.

Table 3 Compatible MGX 8850/8220/8230 Release 1 Hardware

Front Cards
Part Number/
Min. Version
Rev.
Back Cards

PXM1

800-05084-02

800-05760-01

800-07888-01

A0

A0

PXM-UI

PXM-UI-S3

PXM1-4-155

800-05086-02

800-05762-01

800-06229-02

A0

A0

A0

PXM-UI

PXM-UI-S3

MGX-MMF-4-155/B

MGX-SMFIR-4-155/B

MGX-SMFLR-4-155/B

PXM1-1-622

800-05085-02

800-05763-01

800-06228-02

A0

A0

A0

PXM-UI

PXM-UI-S3

MGX-SMFIR-1-622/B

MGX-SMFLR-1-622/B

PXM1-2-T3E3

800-05087-02

800-05602-01

800-06230-02

A0

A0

A0

PXM-UI

PXM-UI-S3

MGX-BNC-2E3

MGX-BNC-2E3A

MGX-BNC-2T3

MGX-VISM-PR-8E1

800-07991-02

A0

AX-SMB-8E1

AX-R-SMB-8E1

AX-RJ48-8E1

AX-R-RJ48-8E1

MGX-RJ48-8E1


Software Compatibility

Table 4 lists the software that is compatible with switches running Release 4.0.10 or previously released 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

MFU

9.3.36

10.5.10
Patch 1

PXM1

3.0

pxm1_003.000.000.000_bt.fw

1.1.75

MFV

9.3.40

11.0

PXM1

3.0.10

pxm1_003.000.010.001_bt.fw

3.0.00

MFW

9.3.42

11.0.10

PXM1

3.0.20

pxm1_003.000.010.002_bt.fw

3.0.00

MFW

9.3.45

11.0.10
Patch 1

PXM1

4.0.00

pxm1_004.000.000.201_bt.fw

4.0.00

MFW

9.3.47

12.0.00

PXM1

4.0.10

pxm1_004.000.010.202_bt.fw

4.0.10

MFW

9.3.47

12.0.00

Patch 1.1


Certified Releases

BPX SWSW Version 9.4.10 (see Software Compatibility Notes Matrix, first and second bullets)

BXM firmware version MFY (see Software Compatibility Notes Matrix, first and second bullets)

Cisco WAN Manager (CWM) Release 12.0.00 Patch 1.1

BCC-3-64

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

MGX 8850/8830/8950 Release 4.0.10

MGX 8850/8230/8250 Release 1.2.21

MGX 8220 Release 5.0.19

SNMP MIB for Release 4.0.10 is bpxsesrel4010mib.tar

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

Additional Deliverables

The SES controller MIB is being provided with the delivery of Release 4.0.10 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.

Upgrade Notes and Cautions

Use the following sequence to upgrade different components in your network to the latest software releases:

1. Upgrade CWM.

2. Upgrade the BXM firmware.

3. Upgrade the BPX/IGX software.

4. Upgrade the SES software.

Upgrading the SES Node

Use the following procedure to upgrade an SES node:


Step 1 At the BPX node, upgrade the BXM firmware to MFY.

For detailed information on BXM firmware upgrades, refer to the 9.4.10 Version Release Notes Cisco WAN Switching Software.

Step 2 At the BPX node, upgrade the BCC switch software to Release 9.4.10.

For detailed information on BCC switch software upgrades, refer to the 9.4.10 Version Release Notes Cisco WAN Switching Software.

Step 3 Upgrade the SES controller to Release 4.0.10. The current boot image is pxm1_004.000.010.202_bt.fw. The current runtime software is pxm1_004.000.010.202_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.

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

1. Upgrade the PXM boot software.

2. Upgrade the PXM runtime software.

The sections that follow describe how to upgrade the PXM cards.

Special Installation and 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, Release 3.0.23, or Release 4.0 to Release 4.0.10

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

Graceful upgrades to Release 4.0.10 are fully supported from Release 4.0, Release 3.0.23, and Release 1.1.75. If you are running a release prior to 1.1.75, use the appropriate upgrade paths as follows:

If you are running release 1.0.15, upgrade to Release 3.0.23 or Release 1.1.75 before you upgrade to Release 4.0.10.

If you are running release 1.0.14 or lower, upgrade to Release 1.0.15. Once Release 1.0.15 is up on your switch, upgrade to Release 1.1.75 or Release 3.0.23, and then upgrade to Release 4.0.10.

Upgrading the Backup Boot Image

This section provides instructions for upgrading the backup boot images from Release 1.1.75 or 3.0.23 to Release 4.0.10. 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 upgrading redundant cards, perform 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_004.000.010.202_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, 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 The default password is 1ciscoinc. If you have changed the default password to a new password, use your new password.


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, as shown in the following example:

put pxm1_004.000.010.202_bt.fw

Replace <PXM backup boot image name> with the boot image name. For Release 4.0.10 of the SES, the boot image name is pxm1_004.000.010.202_bt.fw.

h. Enter the bye command to end your session.

Step 2 At the SES controller, 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, as shown in the following example:

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, as shown in the following example:

ses1.2.PXM.s> sh

Step 7 Enter the sysBackupBoot command, as shown in the following example:

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 4.


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 as shown in the following example.

pxm1bkup>sysPxmRemove

After you enter 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 up in the standby state (approximately four or five minutes), then telnet into the standby PXM and repeat Step 5 and Step 6. After the sysPxmRemove command is entered, the active PXM can not reset the standby.

Step 11 Enter the cd "C:/FW" command from pxm1bkup> prompt to get the FW directory, as shown in the following example:

pxm1bkup> cd "C:/FW"

Step 12 Enter the ls command to verify that the boot firmware file is there, as shown in the following example:

pxm1bkup>ls

Step 13 Enter the sysFlashBootBurn <"boot firmware file name"> command to burn the image on the disk, as shown in the following example:

pxm1bkup>sysFlashBootBurn "pxm1_004.000.010.202_bt.fw"

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

Step 14 When the pxm1bkup> prompt returns, enter the reboot command, as shown in the following example:

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, as shown in the following example:

ses1.1.PXM.a> switchcc 

b. Log in to the SES controller.

c. Perform Step 6 to Step 14 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, use the following procedures to upgrade the backup boot.


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

a. At the SES, 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 The default password is 1ciscoinc. If you have changed the default password to a new password, use your new password.


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, as shown in the following example:

put 4.0.10

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

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, as shown in the following example:

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, as shown in the following example:

pxm1bkup>cd "C:/FW"

Step 6 Enter the ls command to verify the boot firmware file is there, as shown in the following example:

pxm1bkup>ls

Step 7 Enter the sysFlashBootBurn <"boot firmware file name"> command to burn the image on the disk, as shown in the following example:

pxm1bkup>sysFlashBootBurn "pxm1_004.000.010.202_bt.fw"

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

Step 8 At the pxm1bkup> prompt, enter the reboot command, as shown in the following example:

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 Cisco SES PNNI Runtime Image

This section provides instructions for upgrading the runtime images from Releases 1.1.75 or 3.0.20 to Release 4.0.10.

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 Release 4.0.10 is pxm1_004.000.010.202_bt.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, 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 The default password is 1ciscoinc. If you have changed the default password to a new password, use your new password.


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, as shown in the following example:

put pxm1_004.000.010.202_bt.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, as shown in the following example:

ses1.1.PXM.a>loadrev 2 4.0(10.202)

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, as shown in the following example:

ses1.1.PXM.a>runrev 2 4.0(10.202)

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 shown in the following example:

ses1.1.PXM.a>abortrev 1 4.0(10.202)

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

ses1.1.PXM.a>commitrev 2 4.0(10.202)

Step 7 Enter the dspcd command to verify a successful upgrade, as shown in the following example:

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. Traffic is disrupted on the card during a non-graceful upgrade.

Use the following procedure to upgrade the runtime image on a non-redundant system.


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

a. At the SES, 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 The default password is 1ciscoinc. If you have changed the default password to a new password, use your new password.


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, as shown in the following example:

put pxm1_004.000.010.202_bt.fw

h. Enter the bye command to end your session.

Step 2 Use the following procedure to set the new version of the runtime image on the controller card:

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

ses1.1.PXM.a>loadrev 1 4.0(10.202)

Note No cards will reset.


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

c. Enter the dspcd command to display the card revision, as shown 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 the runtime image on the controller card, as shown in the following example:

ses1.1.PXM.a>runrev 1 4.0(10.202)

The card resets and runs the new revision when it returns.

Step 4 Enter the dspcd command to verify a successful upgrade, as shown in the following example:

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

Step 5 At this point, you can still abort this upgrade if needed. To abort the upgrade, enter the abortrev command, as shown in the following example:

ses1.1.PXM.a> abortrev 1 4.0(10.202)

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

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

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

ses1.1.PXM.a> commitrev 1 4.0(10.202)

Step 7 Enter the dspcd command to verify that the runtime image is correct on the card, as shown in the following example:

ses1.1.PXM.a> dspcd 1

Cisco 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/rel30/scg/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 Release 4.0.10:

The SVCC-RCCs between LGNs are not established after the level is changed on one of the LGNs. The Upnode id of the uplinks to the level changed LGN displayed by the command dsppnni-inducing-uplink still shows the old level instead of the new level. The Upnode is enabled immediately after the node level is changed. Use the following sequence of commands to change the Upnode level.

a. cnfpnni-node <node-index> -enable false

b. cnfpnni-node -level <level> -nodeId <node-id> -pgId <pg-id>

c. cnfpnni-node <node-index> -enable true

When you issue the delpnni-node command for a higher level node, a dynamic memory buffer leaks. This will not cause a problem unless the dynamic memory partition is low on memory. Enter the switchcc command as a workaround for this problem.

If you modify a Closed User Group (CUG) membership configuration, the CUG interlock code information that is maintained by the routed SVC connections is not altered. The CUG feature is not supported on nodes that are configured with the right-justified E.164 addresses using the cnfe164justify command. This feature allows a maximum of 10 CUGs per AESA address at a UNI interface.CUG membership can be provisioned at a maximum of 50 AESA addresses per node. When configuring CUGs on a node, you can specify up to 500 different 20-byte AESA administrative addresses (50 addresses with 10 CUGs each) in the leading portion of the node's CUG interlock codes.

The SES supports only 100 signaling features. The192 signaling feature has been tested on PXM45/B and PXM45/C on MGX8850 and MGX8950 platform only.

Preferred routes that are configured with a higher node ID cannot be blocked. Please see CSCdz41145, CSCdz49001. QoS precedence over preferred route does not apply to MPG networks (CSCdz40310).

SES 4.0 lets you enter the delpref command while the preferred route in use. SES 3.0 does not let you enter the delpref command while the preferred route in use.

After you upgrade the SES to Release 4.0, you will need to re-provision any preferred routes that were configured in SES Release 3.0.

When you add an IGX as a feeder to a SES/BPX or MGX node, it has a default node number. This node number may not be unique within the network. If it is not unique, you must use the
rnmnd <node_number> command to modify the node number so that it is unique with respect to all other auto-route nodes. Replace <node_number> with the unique node number.

To view the other node numbers in the network, enter the dspnds +n command. If you do not create a unique node number, the CWM Databroker may form an incorrect hybrid connection database, and the CWMGUI may show the connection as incomplete.

The IGX cannot function as both a feeder and switch at the same time.

A graceful upgrade can be completed only from an SES controller running software Releases 1.1.75 or 3.0.23.

If you are running release 1.0.15, upgrade to Release 3.0.23 or Release 1.1.75 before you upgrade to Release 4.0.10.

If you are running release 1.0.14 or lower, upgrade to Release 1.0.15. Once Release 1.0.15 is up on your switch, upgrade to Release 11.75 or Release 3.0.23, and then upgrade to Release 4.0.10.

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

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.

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 that prevents multiple masters of SPVC connections from pointing to the same slave. When you provision a second connection to a slave VPI/VCI that is already in use, there is no CLI warning that tells you 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 works only if the cell rate is higher than 50 cells per second.

Release 3.0.20 and above of the SES controller allows 100,000 connections. However, for CWM sync up reliability, Cisco recommends that you use outband management channel (i.e.LAN connection) if your SES has more than 50,000 connections provisioned.

The following limitation is in the BXM firmware release MFL and all the releases that follow: due to limited memory space and increased code size on the BXM card, the channel statistics level 0 is no longer supported on the following cards: BXM-155-4, BXM-155-8, BXM-622, BXM-622-2, BXM-T3-8, BXM-T3-12, BXM-E3-8, BXM-E3-12.

When the BXM card firmware is upgraded to MFL or any post MFL release, regardless how many connections are 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 the 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 per card. If a card has more than 16 K connections configured, you must relocate some of the connections to other BXM interfaces in order to reduce the total number of connections to be less than 16 K. Reset the card after changing to run statistics level 1.

Replace the BXM card with a BXM-E card. The BXM-E card can continue running statistics level 0. Statistics level 0 can support a maximum of 32 K connections per card.

Recommendations

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

When APS is enabled, do not pull out the backcard. If you pull out the back card, the switchcc command will not function. (See DDTS CSCeb45350 for more information.)

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

To establish a double-ended DACS 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 the burst SPVC add and delete size is more than 1 K connections, Cisco recommends that you pace your setup and delete rate to be 1 connection per second in order to avoid trap loss.

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

If the SES is 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 4.0.10.

Open Anomalies in Release 4.0.10

Bug ID
Description

CSCdw53912

Headline

CIT30:uplink shows down after load new image, but call can go through.

Symptom

The uplink was down after loaded the new image, but calls could still go through.

Conditions

The nodes were running an older Release 3 image, everything worked fine. clrallcnf was done on SES nodes, and loaded newer image which was a patch image built on top of a stable label. After SES came up, the dsplmilink command showed no information about the uplink, the dspnode command on BPX showed the SES was UNREACHABLE. But the ports on SES were all up (dsppnports). Added lnloop on some port on BPX, SES was updated. But the change of the name of SES, BPX was not updated. Calls could go through these nodes. After deleting the controller and shelf configuration on BPX and added it back, the problem was gone. Did the same scenario on several nodes, the problem was noticed on some of the nodes.

Workaround

None.

CSCdw76129

Headline

addcon is allowed to add slave with slavepersflag 1.

Symptom

The addcon command is allowed with slavepersflag 1 while adding the slave end point.

Conditions

Always.

Workaround

None.

Additional Information

Does not effect the connections.

CSCeb45350

Headline:

APS does not switch to Prot. when backcard of Working is pulled out.

Symptom:

APS fails to switchover to protection line.

Conditions:

Backcard of primary/working slot is pulled out.

Workaround:

None

CSCeb69469

Headline:

The addcon command is allowed to add slave with slavepersfalg 1

Symptom:

The addcon command is allowed with slavepersflag 1 while adding the slave end point.

Conditions:

Always.

Workaround:

None.

Additional Information:

Does not effect the connections.

CSCeb82039

Headline:

PXM1 (SES) PXM boot Login password always fails.

Symptom:

Unable to log into PXM's boot mode via telnet (PXM Boot Login). This is not service affecting because the only time you need to login via this access is when the card is already down, like for upgrading.

Conditions:

This only happens when you telnet to the pxm. If you are consoled in, you do not get this prompt.

Workaround:

Using the console port will avoid login prompt.

Otherwise, if there is no console port, then boot login/password is cisco/1ciscoinc

CSCeb82698

Headline:

SES: addcon command cannot add -int_vsvd (3.0) or -frame (4.0).

Symptom:

SES addcon command fails with the error message "ERROR:slave pers flag is for master end alone."

Condition:

Attempting to use addcon to add a slave endpoint to an SES with connection parameters -int_vsvd (SES PXM SW revision 3.0) or -frame (SES PXM SW revision 4.0).

Workaround:

Add the connection endpoint without specifying -int_vsvd or -frame.

After adding the connection endpoint, the cnfcon command may be used to change these parameters.

Further Description:

The -slavepersflag can only be specified on the master end of a connection. The SW is incorrectly blocking the addcon if the -int_vsvd (3.0) or -frame (4.0) parameters are specified. The failure to correctly block the -slavepersflag parameter on the slave endpoint was fixed by CSCdw23963.


Anomalies Fixed in Release 4.0.10

Bug ID
Description

CSCea41723

Add ICR range check to SES CLI interface (cnfcon and addcon)

CSCea74459

Invalid entries in atm_connection for SES endpoints

CSCea78204

CIT40: SES node stays in mem and leg congestion

CSCdz63826

P2MP_DT: Nodal conn limit can be exceeded when p2p and p2mp combine


Anomalies Status Change from Previous Release 4.0

Table 5 describes the known anomalies status that changed in Release 4.0.10 from Release 4.0 of the SES controller. A more in depth discussion of each bug is available in the release note enclosure in Bug Navigator.

Table 5 Anomalies Status Change from Previous Release

Bug ID
Description

CSCea02774

UPGRD:lmiRootTask complains time spec is out of range. Duplicated to CSCdw61915

CSCea13938

REG4: Incoming CUG call is not correctly checked at destination CUG. Junked

CSCea42668

CIT40:while port dn-in-prog, admin state change up to dn after switch. Closed


BXM Firmware MFY Release Notes

This section contains information about the BXM firmware MFY.

About the Firmware MFY

BXM firmware version MFY supports all existing interfaces and models of BXM hardware. The tables in this section outline various levels of hardware revisions supported for BXM firmware version MFY.

Front Cards

Table 6 Front Cards Supported by MFY Firmware 

Model Number
Description
FW model
HW Rev
FW Rev

BXM-155-4

4 port OC3 Line Module (Front Card)

F

B

MFY

BXM-155-8

8 port OC3 Line Module (Front Card)

F

B

MFY

BXM-622

1 port OC12 Line Module (Front Card)

F

D

MFY

BXM-622-2

2 port OC12 Line Module (Front Card)

F

D

MFY

BXM-T3-8

8 port T3 Line Module (Front Card)

F

B

MFY

BXM-T3-12

12 port T3 Line Module (Front Card)

F

B

MFY

BXM-E3-8

8 port E3 Line Module (Front Card)

F

B

MFY

BXM-E3-12

12 port E3 Line Module (Front Card)

F

B

MFY

BXM-155-8DX

8 port OC3 Line Module (Front Card)

F

A0

MFY

BXM-155-8D

8 port OC3 Line Module (Front Card)

F

A0

MFY

BXM-155-4DX

4 port OC3 Line Module (Front Card)

F

A0

MFY

BXM-155-4D

4 port OC3 Line Module (Front Card)

F

A0

MFY

BXM-622-2DX

2 port OC12 Line Module (Front Card)

F

A0

MFY

BXM-622-2D

2 port OC12 Line Module (Front Card)

F

A0

MFY

BXM-622-DX

1 port OC12 Line Module (Front Card)

F

A0

MFY

BXM-T3-12EX

12 port T3 Line Module (Front Card)

F

A0

MFY

BXM-T3-12E

12 port T3 Line Module (Front Card)

F

A0

MFY

BXM-T3-8E

8 port T3 Line Module (Front Card)

F

A0

MFY

BXM-E3-12EX

12 port E3 Line Module (Front Card)

F

A0

MFY

BXM-E3-12E

12 port E3 Line Module (Front Card)

F

A0

MFY

BXM-E3-8E

8 port E3 Line Module (Front Card)

F

A0

MFY


Front Card for APS Compatibility

Table 7 Front Cards Supporting APS with MFY Firmware 

Model Number
Description
FW model
HW Rev
FW Rev

BXM-155-4

4 port OC3 Line Module (Front Card)

F

C

MFY

BXM-155-8

8 port OC3 Line Module (Front Card)

F

C

MFY

BXM-622

1 port OC12 Line Module (Front Card)

F

E

MFY

BXM-622-2

2 port OC12 Line Module (Front Card)

F

E

MFY

BXM-155-8DX

8 port OC3 Line Module (Front Card)

F

A0

MFY

BXM-155-8D

8 port OC3 Line Module (Front Card)

F

A0

MFY

BXM-155-4DX

4 port OC3 Line Module (Front Card)

F

A0

MFY

BXM-155-4D

4 port OC3 Line Module (Front Card)

F

A0

MFY

BXM-622-2DX

2 port OC12 Line Module (Front Card)

F

A0

MFY

BXM-622-2D

2 port OC12 Line Module (Front Card)

F

A0

MFY

BXM-622-DX

1 port OC12 Line Module (Front Card)

F

A0

MFY


Back Cards

Table 8 Back Cards Supported by MFY Firmware 

Model Number
Description
HW Rev
FW Rev

MMF-155-4

4 port multi-mode fiber back card

A

na

MMF-155-8

8 port multi-mode fiber back card

A

na

SMF-155-4

4 port single-mode fiber intermediate-reach back card

A

na

SMF-155-8

8 port single-mode fiber intermediate-reach back card

A

na

SMFMR-155-4

4 port single-mode fiber long-reach back card

A

na

SMFMR-155-8

4 port single-mode fiber long-reach back card

A

na

SMF-622

1 port intermediate-reach OC12 back card

A

na

SMF-622-2

2 port intermediate-reach OC12 back card

A

na

SMFMR-622

1 port long-reach OC12 back card

A

na

SMFMR-622-2

2 port long-reach OC12 back card

A

na

XLR-622

1 port extra long-reach OC12 back card

A

na

XLR-622-2

2 port extra long-reach OC12 back card

A

na

BPX-T3/E3-12

12 port T3/E3 back card

A

na

BPX-T3/E3-8

8 port T3/E3 back card

A

na

RDNT-LR-622-2

2 port long-reach OC12 redundant back card

A

na

RDNT-SM-622-2

2 port intermediate reach OC12 redundant back cards

A

na

RDNT-SM-622

1 port intermediate reach OC12 redundant back cards

A

na

RDNT-LR-155-8

8 port long-reach OC3 redundant back cards

A

na

RDNT-SM-155-4

4 port intermediate-reach OC3 redundant back cards

A

na

RDNT-SM-155-8

8 port intermediate-reach OC3 redundant back cards

A

na


New Features supported in BXM Firmware MFY

Support for Pseudo AIS

This feature makes the customer-specific behavior where AIS-P will be triggered from UAS configurable. In previous releases starting with MFP this was always "ON" whereas now the default is "OFF" and it must be turned "ON" using the CLI command cnfndparm 61. This feature requires switch software release 9.4.10 or higher.

Special Installation/Upgrade Requirements

APS Issues

Upgrading from MEK and lower firmware to MFY when feeder trunks are utilized with APS while the BPX node does not have APS requires the following procedure:


Step 1 Change the PXM1-based MGX feeder to use APS1+1 unidirectional AND disable K1K2 processing (may need to delete and then add back APS). On the BPX temporarily configure to use unidirectional mode.

Step 2 After PXM1-based MGX dspapsln shows both lines OK, delete the APS line on the BPX.

Step 3 Proceed to upgrade the BXM cards as if YRED.

Step 4 After both cards are MFW, add back the APS on the BPX.

Step 5 Reconfigure both PXM1-based MGX and BPX to use the appropriate APS configurations.


BXM cards with MCB/MDA firmware or later can be smoothly migrated to the MFA or above version of firmware by using Y-cable redundancy.

To upgrade a BXM card pair in Y-red configuration, complete the following steps:


Step 1 Upgrade the standby card with the MFA or above firmware version. Wait for all of the configuration to be downloaded into the card.

Step 2 Do a switchyred to switch to the card with firmware MFA or above version.

Step 3 Burn the other card with the desired version MFA or above firmware. Follow the standard firmware upgrade procedure for downloading and burning the firmware into the cards.

Step 4 If BCC SWSW version is 9.1.18 and dspnovram shows 0 or 4 for Number of Channel Stats, go directly to MFC or above versions from MCC.


For APS (1+1) MEx or MFA image versions are not to be treated as compatible with MFx (minus MFA) image versions. During an upgrade procedure from MEx or MFA image to MFx (minus MFA) image, both cards must be upgraded to the MFx (minus MFA) image with minimal interval between them.

The incompatibility is due to APS intercard messages from one end not being recognized by the other end. See bug CSCdu67053 for the symptoms caused by this incompatibility.

Intra-MFx (minus MFA) and intra-MEx upgrades are compatible.

Channel Statistics Issues

While upgrading from firmware, on OC3, 1 port OC12 BXM cards, if stats level on BXM is greater than 1, use one of the following upgrade procedures listed below.

Upgrade from firmware revision MEA or higher.


Step 1 Upgrade SWSW to 9.2.30 or higher.

Step 2 Upgrade the firmware to MFW.


Upgrade from firmware revisions lower than MEA.

This procedure avoids card mismatch.


Step 1 Upgrade firmware to MEC.

Step 2 Upgrade the SWSW to 9.2.30 or higher revision.

Step 3 Upgrade the firmware to MFW.

A firmware burn must not be interrupted. A card reset in the middle of burn firmware results in the BXM being maintained in the core state (identified by blinking yellow LED) or failed state (identified by a solid red LED). In this case the dspcds screen reports the card as FAILED. This state can be recovered by reburning the firmware into the card.


Features Obsoleted

The following features have been obsoleted:

1. VSI 1.0 is obsoleted by VSI 2.2 in the MDA release onwards.

2. From versions MFJ to MFN channel statistics level 0 is no longer supported for BXM-155-4, BXM-155-8, BXM-622, BXM-622-2, BXM-T3-8, BXM-T3-12, BXM-E3-8, BXM-E3-12 models. In MFN onwards conditional support for statistics level 0 is revoked. See the Notes, Cautions, and Clarifications section point 13 for more details.

3. In all other models channel statistics level 0 is supported by all firmware versions (BXM-155-8DX, BXM-155-8D, BXM-155-4DX, BXM-155-4D, BXM-622-2DX, BXM-622-2D, BXM-622-DX, BXM-T3-12EX, BXM-T3-12E, BXM-T3-8E, BXM-E3-12EX, BXM-E3-12E, BXM-E3-8E).

Notes, Cautions, and Clarifications

1. BXM Model F firmware is intended for use with 9.3 and 9.4 switch software. BXM Model F firmware may be used to upgrade BXM cards during the upgrade process from SWSW Release 9.2 to 9.3 or 9.3 to 9.4. BXM Model F firmware has not been tested for compatibility with SWSW Releases 8.4, 8.5, and 9.1. It is compatible with IOS version 12.05t2 or greater for MPLS.

2. M.F.E is a not on CCO as it is an SES specific release.

3. Protection Switching based on BER on BXM may not comply to standards. The GR-253 and ITU-T G.783 requires that switching be completed within 60 msec from the time the error starts. BXM is unable to detect BER threshold crossing until the next poll, which occurs every 250 msec. Thus, switching time may be up to 250 msec under certain circumstances.

4. In APS 1+1 default configuration, both back card LEDs show green when primary card is active and selection is from PROT line. When primary card is active and it is selecting from PROT, PROT backcard should be green, since it is carrying traffic. WORK backcard should also be green since that is the physical path for the primary (and active) card to pass traffic. Backcard LED green means the backcard is directly or indirectly carrying traffic, and pulling the backcard causes traffic disruption (CSCdm53430).

5. In APS 1+1 default configuration and a manual W->P is on and a switchyred is issued, a manual W->P event is logged. By default, on switchyred the new active card comes up in "clear" state. But in this case since there is a manual W->P on, the APS line switches to PROT and the switching is logged (CSCdm53404).

6. In APS 1+1 default configuration if the selected line is PROT and last user request is clear and a switchyred is issued, line switches to WORK. If the last user request is "clear", full automatic APS switching is in effect with the working line being active by default. When there is no last user switch request to switch to any particular line, the working line becomes active. (CSCdm53420)

7. When APS Annex B is added to local end which has the secondary card active, the APS trunk goes into Comm Failure for few seconds and then clears. If the secondary card is active, do a switchyred to make the primary card active. Then, add APS Annex B (CSCdm46359).

8. MFK and above versions support LCN CAC for Class of Services. The controller reserves some LCNs for control VC as default. These reserved LCNs cannot be used by any Class of Service in MFT. If all the LCNs for the partition have been used in a version earlier than MFK after the MFT version is updated in the switch, some connections may not be added. These connections try to use LCNs reserved for control VC which is not allowed. Configure more LCNs for the partition to make sure enough LCNs exist for all the connections.

9. The OC-3 MultiMode Fiber backcards do not support Y-cable redundancy.

10. APS 1:1 is not supported for VSI in versions before MFE. (Bug CSCdp42996) APS 1:1 should not be configured on ports intended to be used by PNNI or MPLS as after switchover traffic flow is stalled on the protection line for releases before MFE. However, in MFE and above, this problem is fixed.

11. Total bandwidth allocated to all VSI partitions on a BXM should not be more that OC12 rate, 1412832 cps. BCC SWSW allows users to configure more than OC12 rate, in which case all the PNNI connection commit requests are NACKed by BXM.

12. In firmware versions prior to MFF signaling bandwidth for an SES controller was not guaranteed. In MFF and above the signaling Qbin feature has been added (with SWSW 9.3.10 and above and SES image 1.0.10 and above) to guarantee signaling bandwidth.

13. Statistics level 0 for legacy BXM cards was obsoleted in Model F releases until MFN. However, in version MFP and above conditional support statistics level 0 for legacy cards has been revoked. Statistics level 0 is not supported if VSI configurations exist on the card.

If a card was configured with statistics level 0 with VSI enabled in a previous release of firmware (Model C or E), upgrading to MFP or above revisions causes a mismatch on legacy cards. To avoid impacting VSI operations, reconfigure the card to statistics level 1 or above before upgrading.


Note BXME (enhanced cards) support all statistics levels unconditionally with all valid configurations, models, and releases.


14. Excessive BIP-8 error rates (10-3) which escalate into unavailable seconds (UAS) are now reported to Switch Software as red alarms. This feature is not configurable, and may cause failed connections and rerouted trunks in configurations where APS is not enabled, alternate trunk routes do not exist or on UNI ports. This feature is not active when APS is configured and enabled.

Known Anomalies in MFY

The following table lists the known anomalies for the BXM MFY firmware.

Table 9 Known Anomalies in MFY 

Bug ID
Description
Apply to SES

CSCdx52484

Symptom:

CBR traffic got dropped on ENNI link on BPX side where there is congestion.

Condition:

resetcd of BXM can solve the problem.

Workaround:

Unknown.

No

CSCdx79141

Symptom:

chan allocation inconsistency between BPX and SES.

Condition:

Have only 1 part. first (Max. lcn > Min.),add conns. > min..Add more parts such that sum(Min.s)>Max(max.).

Workaround:

None

Yes

CSCdz36965

Symptom:

BXM fail after firmware burn

After BXM Burns, the BXM card comes up as failed. On resetting the card and or reprogramming the card the card gets successfully upgraded

Conditions:

BPX 8620, with 9.2.32 BCC with HDM and the BXM with MEJ being upgraded to MFT.

Workaround:

Depends on the card. ON resetting the card hard, the card comes back in standby and successfully burnt on not at all. If burn is not successful a second attempt goes through fine

No


BXM Firmware Filenames and Sizes

The following table contains the firmware file information for the BXM Firmware release MFY.

Table 10 BXM Firmware Filenames and Sizes for Release MFY 

Firmware Filename
Size (Bytes)

BXMMFY.000

65536

BXMMFY.001

65536

BXMMFY.002

65536

BXMMFY.003

65536

BXMMFY.004

65536

BXMMFY.005

65536

BXMMFY.006

65536

BXMMFY.007

65536

BXMMFY.008

65536

BXMMFY.009

65536

BXMMFY.010

65536

BXMMFY.011

65536

BXMMFY.012

65536

BXMMFY.013

65536

BXMMFY.014

65536

BXMMFY.015

65536

BXMMFY.016

65536

BXMMFY.017

65536

BXMMFY.018

65536

BXMMFY.019

65536

BXMMFY.020

65536

BXMMFY.021

65536

BXMMFY.022

65536

BXMMFY.023

65536

BXMMFY.024

65536

BXMMFY.025

48064

BXMMFY.026

14

BXMMFY.027

2

BXMMFY.IMG

784

BXMMFY.img

784


Anomalies Fixed in MFY

Table 11 Anomalies Fixed in MFY 

Bug ID
Description

CSCea08808

Symptom:

In a BPX/SES PNNI scenario, SVC/SPVC connections do not route over PNNI virtual interface (VNNI, virtual trunk) when using different VPIs in both ends of the Virtual Path Connection. Connections fail with cause code #35:

Last Fail Cause: requested VPCI/VCI not available.

Conditions:

The scenario is similar to this:

BXM_VNNI-----VPI1-----VPC_Cloud-----VPI2----BXM_VNNI

where VPI1 is different than VPI2

Workaround:

Disable ILMI auto configuration using the command from the SES Controller. With auto-configuration disabled, the ILMI slave does not start ATM layer parameter-negotiation while ports come up. Instead, the ILMI slave uses the local configuration parameters. The default state for auto-configuration is enabled.

Further Problem Description:

If this problem is present, the command dsppnport shows a minSvccVpi greater than maxSvccVpi, and minSvccVci greater than maxSvccVci in the end with higher VPI value. This can be seen below:

nodename.7.PXM.a > dsppnport 1:1.4:14
Port:               1:1.4:14          Logical ID:       16848910
IF status:          up                Admin Status:     up
UCSM:               enable            SVC Routing Pri:  8
Auto-config:        enable            Addrs-reg:        enable
IF-side:            network           IF-type:          nni
UniType:            private           Version:          pnni10
PassAlongCapab:     n/a
Input filter:       0                 Output filter:    0
minSvccVpi:         11                maxSvccVpi:       10     <=====
minSvccVci:         35                maxSvccVci:       65535
minSvpcVpi:         11                maxSvpcVpi:       10     <=====

Only firmware release MFY will resolve this issue. For this particular feature, both sides have to be running firmware release MFY or later.

CSCea85590

Symptom:

Pseudo AIS on path BIP 8 errors on BXM cards with SONET interfaces is not configurable feature

Condition:

Always

Workaround:

None, new feature.

This ddts makes configurable the customer-specific behavior where AIS-P will be triggered from UAS. In previous releases starting with MFP this was always "ON" whereas now the default is "OFF" and it must be turned "ON" via command cnfndparm 61 using swsw 9.4.00 or higher. For a more detailed description see swsw release notes.


Anomalies Fixed in MFX

Table 12 Anomalies Fixed in MFX 

Bug ID
Description

CSCdw16017

Symptom: Traffic is only seen on the ingress of the master and slave nodes.

Condition: This problem is triggered by a network condition that causes the VPC to reroute. VPC experiencing this problem have been ABRSTD with VSVD enabled one megabits or larger VPC connections.

Workaround: Closed. Workaround is to not assign VCI to 0. Up-ing and downing the connection clears the problem.

CSCdw76023

Symptom:

For APS 1:1 intracard configuration, "dspapsln" command keeps showing false and misleading alarm "APS missing card"

Conditions:

APS 1:1 intracard setup using "R" (redundant) designated backcard.

Workaround:

Do not use an "R"-designated backcard when configuring APS 1:1 intracard setup.

Use just the normal backcard. It is just a false alarm. All APS functionality should still be working correctly.

CSCdw95063

Symptom:

"dspapsln" doesn't show "card missing" on standby even though the standby card has been removed. "dspapsln" shows OK even though standby BXM card is removed to cause a switchover to the newly active card

Conditions:

Remove the active BXM to cause the switchover to the newly active card in an APS 1+1 configuration setup

Workaround:

Insert back the standby BXM card.

CSCdx28781

Symptom:

When bit errors happen on a line, all the connections provisioned on the line fail.

Conditions:

MFM onwards (There is a code change went into firmware image MFM, which puts the line into Path AIS as long as UAS-P condition persists. This change is good for trunks as alternate routes could be chosen. But on lines, especially when they are error prone, there is no choice but to keep using the line, application might slow down

but at least connection does not get failed)

Workaround:

Use images before MFM or replace the buggy physical cable

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:

This affects OAM cell counting on all SPVC connections. It will occur with firmware MFW or lower revision.

Workaround:

None.

CSCdx50089

Symptom:

ILMI did not update its neighbor's IP address and IfName to be "N/A", when its physical link on which it was running went down. dspnebdisc would show the previous neighbor's IP address and IfName in this situation.

Conditions:

The physical link on which ILMI was running went down.

Workaround:

Reset the card will clear the old information.

CSCdx72292

Symptom:

Commit connection request is failed due to NAK from BXM, while still a lot of available bandwidth at partition level.

Condition:

1.Single/Multiple partitions on a interface enabled.

2.The bandwidth common pool of this interface is zero.

3.At least in one partition, sum of (cos_min_bw) > part_min_bw, due to the round up

when applying the policy parameters -minbw to get cos_min_bw.

Workaround:

When configure the multiple partitions, gives at least 20 cells in common pool. The work around for CSCdv03058 applies to this problem.

See CSCdv03058 for detail workaround explanation.

CSCdy16927

Symptom:

BXM LMI clears Abit alarms on SPVC feeder after switchcc or switchyred.

Conditions:

SPVC feeder1 === BPX1/SES1=== BPX2/SES2 === SPVC feeder **

1. The connection segment in the BPX/SES network is down.

2. The corresponding segment in the SPVC feeder is in Abit alarm

3. After a switchcc or a BXM switchyred on BPX1, the BXM LMI session at "**"

tells SPVC feeder1 to clear the Abit alarm on the segment corresponding to the

downed VSI connection in the BPX/SES network.

Workaround:

None.

CSCdy57435

Symptom:

Fatal PRFD Pending error has been seen at BXM card. (SIMBA errors excess its threshold).

Conditions:

Most likely, it happens during FW/SW upgrade.

Workaround:

none

CSCdy75277

Symptom:

A pnport stuck is in down state after being added and configured

Conditions:

Add and configure pnport on a freshly added trunk/port. Delete all the configuration and down all interfaces, then newly add and configure the pnport from scratch.

Workaround:

Unknown

CSCdy80205

Symptom:

When physical interface in alarm (LOS), dsppnport shows the operstatus as up

in SES.

Conditions:

When SES is running 3.0(10.0) or later, even if the physical interface is in alarm (LOS), if ILMI is enabled, with out configuring signalling type (NNI or UNI) in SES, the operstatus of interface is shown as UP.

With BXM Image MFW or prior.

Workaround:

Configure signalling type in SES.

CSCdy89521

Symptom:

The AAL5 Feeder attached to the BPX routing hub becomes unreachable after a delshelf command was issued on the BPX, even though there are no existing connections on either the feeder or the BPX.

Conditions:

BXM runs the LMI protocol.

Workaround:

None

CSCdz49797

Symptom:

Doing a switchyred on BXM causes AXSM connection to go into Abit/AIS alarm.

Conditions:

A switchyred on BXM card running XPVC in a mixed MGX8220 BPX MGX1 MGX45 network can go into alarm, and then the alarm will not clear. Typically a transition outside of the PNNI network (a switchyred on the BPX in this case) can cause the ingress port to generate an AIS alarm, which it sends into the PNNI network and is received by CPE at the other end. Because the AIS is incorrect, there's never any indication to the ingress port that it should clear the alarm.

Workaround:

Executing dncon/upcon on the AXSM end which is generating switch side Tx AIS (if that is the master connection) If the problem is on the slave end need to delete and re-add the connection

CSCin33357

Symptom:

After burn MFW image, the BXM enhanced card went to resetting.

Conditions:

BXME card with stats lvl 0 and VSI connections.

Workaround:

Don't use stats lvl 0 for BXME card.

CSCdz60041

Symptom:

BPX may not be able to recover clock from the line with PLCP framing configuration.

Conditions:

BPX may experience clock recovery issues when recovering clock from the line connected to other vendor equipment.

Workaround:

None


Anomalies Fixed in MFW

Table 13 Anomalies Fixed in MFW 

Bug ID
Description

CSCdw80712

Symptom: 1:1 APS allows manual/forced switchapsln P->WLine.

Conditions:

1. 1:1 APS with Bi-Dir configured; remote is AXSM/B.

2. Manual switchaps W->PLine from AXSM/B.

3. Forced switchaps P->WLine from BXM.

Workaround: None.

CSCdx45385

Symptom: BXM did not update SES with the latest available cos level LCN when there is cnfrsrc LCN resources (LCN) change on this partition (part_min_lcn, part_max_lcn).

Conditions:

1. A PNNI partition has been configured with some connections up. dsppnportrsrc reports the correct available lcn for each cos level.

2. Do cnfrsrc on this partition, to change the min_lcn and max_lcn at partition level. The available lcn at cos level in SES dose not get updated.

Workaround: Add a con or down a con to trigger the update.

CSCdx55794

Symptom: BXM incorrectly sends back LMI version 4 to IGX AAL5 feeder, while it does not support LMI version 4.

Conditions:

1. IGX AAL5 feeder is added to a BXM feeder trunk in the BPX.

2. IGX feeder LMI is running LMI version 4, and talk to BXM LMI.

Workaround: None.

CSCdx56537

Symptom: Setting cnftrkparm 9 2500/15000 causes trunk failure.

Conditions: BXM running MFU firmware. Found in lab environment but likely to also be found in a live network if these trunkparm values are used and the trunk passes over another medium such as a TDAX or SDH backbone.

Workaround: Set cnftrkparm 9 2500/10000 which is the default for STM1. Do not use the values 2500/15000 for cnftrkparm 9. Tests have yet to show if this would effect other values but default settings have been confirmed problem free.

CSCdx59080

Symptom: Customer is performing tests of MFU firmware prior to deployment in live network and has found that when a BXM trunk is configured for loop clock yes at both ends it remains in a "Looped Back" state when the BXM is reset by command "resetcd? h".

Conditions: BXME trunk needs to be configured for loop clock yes and the BXM card be reset. Tests showed that causing a LOS or resetting the card again would not recover the trunk.

Workaround: Issue cnftrk and change none of the parameters by stepping through them.

CSCdy01870

Symptom: SIMBA reset card errors logged due to PRFD Pending Errors

Conditions: BXM image MEE and SWSW image 9.3.00

Workaround: None.

CSCdy01951

Symptom: Unnecessary alarms are triggered when BXM sends slot errors to SWSW.

Conditions: The FW adds all slot errors before sending them to BCC. There are situations when the number of traffic related slot errors will trigger unnecessary alarms on SWSW. These alarms will be suppressed.

Workaround: None.

CSCdy05515

Symptom: Current BXM firmware only support a few statistics counters. In order to enhance customer operation and maintenance capability, a few new stats counters have been added. The detail description about the new created stats and associated CLI command and MIB can be found in the latest VSI document. See DDTS case CSCdy05597 (SES and Mibs).

Conditions: All previous FW do not support the new connection stats.

Workaround: Not applicable.

CSCdy13987

Symptom: Newly added routed SPVC carries counter values of previously deleted SPVC.

Conditions: Delete routed SPVC. Then re-add the SPVC with same VPI/VCI values.

Workaround: Problem is fixed in MFW (MF20).

CSCdy75277

Symptom: pnport stuck in down state

Conditions: Configure PNNI trunk between SES and MGX 8850 (PXM45) using automation script PROU001.

Workaround: Unknown.


Related Documentation

This "Related Documentation" section describes the technical manuals and release notes listed in the "Guide to Cisco Multiservice Switch Documentation." That guide, part DOC-7815358=, shipped with your product.

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


Note Starting in April 2003, the documents listed in the "Related Documentation" section will be available online only.


There are several ways you can find these documents online:

In your browser's URL field, enter www.cisco.com. In the top right search field, enter the document part number (for example, OL-3837-01) and click on GO.

For all documents, in your browser's URL field, enter http://www.cisco.com/univercd/cc/td/doc/product/wanbu/index.htm. Look for the switch name, then release number (for example, MGX 8850 (PXM1E), then Release 4.0.10).

Cisco WAN Manager Release 12

Table 14 lists the product documentation for the Cisco WAN Manager (CWM) network management system for Release 12.

Table 14 Cisco WAN Manager Release 12 Documentation 

Title
Description

Cisco WAN Manager Installation Guide for Solaris 8, Release 12

OL-3837-01

Provides procedures for installing Release 12 of the CWM network management system and Release 5.4 of CiscoView on a Solaris 8 platform.

Cisco WAN Manager User's Guide, Release 12

OL-3838-01

Describes how to use the CWM Release 12 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 Guide, Release 12

OL-3840-01

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 12

OL-3839-01

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


SES PNNI Release 4.0.10

Table 15 lists the product he product documentation for the understanding, the installation, and the operation of the Service Expansion Shelf (SES) Private Network-to-Network Interface (PNNI) Controller.

Table 15 SES PNNI Controller Release 4.0.10 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.

PNNI Network Planning Guide for MGX and SES Products

OL-3847-01

Provides guidelines for planning a PNNI network that uses Cisco MGX 8830, Cisco MGX 8850 (PXM45 and PXM1E), Cisco MGX 8950, and Cisco BPX 8600 switches. When connected to a PNNI network, each Cisco BPX 8600 series switch requires an SES for PNNI route processing.

* This book was last updated for Release 3.


Cisco WAN Switching Software Release 9.4

Table 16 lists the product documentation for the installation and operation of the Cisco WAN Switching Software Release 9.4.

Table 16 Cisco WAN Switching Release 9.4 Documentation 

Title
Description

9.4.00 Version Software Release Notes Cisco WAN Switching System Software

OL-3189-01

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

Cisco BPX 8600 Series Installation and Configuration, Release 9.3.30

DOC-7812907=

Provides a general description and technical details of the Cisco 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-05

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

Cisco IGX 8400 Series Provisioning Guide

OL-1166-03

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

Cisco IGX 8400 Series Regulatory Compliance and Safety Information

DOC-7813227=

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


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 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 ([ ]).


Note Means reader take note. Notes contain helpful suggestions or references to material not covered in the manual.



Caution Means reader be careful. In this situation, you might do something that could result in equipment damage or loss of data.


Tips Means the following information will help you solve a problem. The tips information might not be troubleshooting or even an action, but could be useful information, similar to a Timesaver.



Warning This warning symbol means danger. You are in a situation that could cause bodily injury. Before you work on any equipment, you must be aware of the hazards involved with electrical circuitry and be familiar with standard practices for preventing accidents. (To see translated versions of this warning, refer to the Regulatory Compliance and Safety Information document that accompanied the product.)


Obtaining Documentation

Cisco provides several ways to obtain documentation, technical assistance, and other technical resources. These sections explain how to obtain technical information from Cisco Systems.

Cisco.com

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

http://www.cisco.com/univercd/home/home.htm

You can access the Cisco website at this URL:

http://www.cisco.com

International Cisco websites can be accessed from this 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 may have shipped with your product. The Documentation CD-ROM is updated regularly and may be more current than printed documentation. The CD-ROM package is available as a single unit or through an annual or quarterly subscription.

Registered Cisco.com users can order a single Documentation CD-ROM (product number DOC-CONDOCCD=) through the Cisco Ordering tool:

http://www.cisco.com/en/US/partner/ordering/ordering_place_order_ordering_tool_launch.html

All users can order monthly or quarterly subscriptions through the online Subscription Store:

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

Ordering Documentation


Note As of April 2003, the documents listed in the "Related Documentation" section will be available online only.


There are several ways you can find these documents online:

In your browser's URL field, enter www.cisco.com. In the top right search field, enter the document part number (for example, OL-3837-01) and click on GO.

For all documents, in your browser's URL field, enter http://www.cisco.com/univercd/cc/td/doc/product/wanbu/index.htm. Look for the switch name, then release number (for example, MGX 8850 (PXM1E), then Release 4).

You can find instructions for ordering other Cisco documentation at this URL:

http://www.cisco.com/univercd/cc/td/doc/es_inpck/pdi.htm

You can order Cisco documentation in these ways:

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

http://www.cisco.com/en/US/partner/ordering/index.shtml

Nonregistered Cisco.com users can order documentation through a local account representative by calling Cisco Systems Corporate Headquarters (California, U.S.A.) at 408 526-7208 or, elsewhere in North America, by calling 800 553-NETS (6387).

Documentation Feedback

You can submit comments electronically on Cisco.com. On the Cisco Documentation home page, click Feedback at the top of the page.

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

You can submit comments by using the response card (if present) behind the front cover of your document or by writing to the following address:

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

We appreciate your comments.

Obtaining Technical Assistance

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

Cisco.com

Cisco.com offers a suite of interactive, networked services that let you access Cisco information, networking solutions, services, programs, and resources at any time, from anywhere in the world.

Cisco.com provides a broad range of features and services to help you with these tasks:

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

To obtain customized information and service, you can self-register on Cisco.com at this URL:

http://tools.cisco.com/RPF/register/register.do

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: the Cisco TAC website and the Cisco TAC Escalation Center. The type of support that you choose depends on the priority of the problem and the conditions stated in service contracts, when applicable.

We categorize Cisco TAC inquiries according to urgency:

Priority level 4 (P4)—You need information or assistance concerning Cisco product capabilities, product installation, or basic product configuration. There is little or no impact to your business operations.

Priority level 3 (P3)—Operational performance of the network is impaired, but most business operations remain functional. You and Cisco are willing to commit resources during normal business hours to restore service to satisfactory levels.

Priority level 2 (P2)—Operation of an existing network is severely degraded, or significant aspects of your business operations are negatively impacted by inadequate performance of Cisco products. You and Cisco will commit full-time resources during normal business hours to resolve the situation.

Priority level 1 (P1)—An existing network is "down," or there is a critical impact to your business operations. You and Cisco will commit all necessary resources around the clock to resolve the situation.

Cisco TAC Website

The Cisco TAC website provides online documents and tools to help troubleshoot and resolve technical issues with Cisco products and technologies. To access the Cisco TAC website, go to this URL:

http://www.cisco.com/tac

All customers, partners, and resellers who have a valid Cisco service contract have complete access to the technical support resources on the Cisco TAC website. Some services on the Cisco TAC website require 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 this URL to register:

http://tools.cisco.com/RPF/register/register.do

If you are a Cisco.com registered user, and you cannot resolve your technical issues by using the Cisco TAC website, you can open a case online at this URL:

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

If you have Internet access, we recommend that you open P3 and P4 cases online so that you can fully describe the situation and attach any necessary files.

Cisco TAC Escalation Center

The Cisco TAC Escalation Center addresses priority level 1 or priority level 2 issues. 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 automatically opens a case.

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

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

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

Obtaining Additional Publications and Information

Information about Cisco products, technologies, and network solutions is available from various online and printed sources.

The Cisco Product Catalog describes the networking products offered by Cisco Systems, as well as ordering and customer support services. Access the Cisco Product Catalog at this URL:

http://www.cisco.com/en/US/products/products_catalog_links_launch.html

Cisco Press publishes a wide range of networking publications. Cisco suggests these titles for new and experienced users: Internetworking Terms and Acronyms Dictionary, Internetworking Technology Handbook, Internetworking Troubleshooting Guide, and the Internetworking Design Guide. For current Cisco Press titles and other information, go to Cisco Press online at this URL:

http://www.ciscopress.com

Packet magazine is the Cisco quarterly publication that provides the latest networking trends, technology breakthroughs, and Cisco products and solutions to help industry professionals get the most from their networking investment. Included are networking deployment and troubleshooting tips, configuration examples, customer case studies, tutorials and training, certification information, and links to numerous in-depth online resources. You can access Packet magazine at this URL:

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

iQ Magazine is the Cisco bimonthly publication that delivers the latest information about Internet business strategies for executives. You can access iQ Magazine at this URL:

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

Internet Protocol Journal is a quarterly journal published by Cisco Systems for engineering professionals involved in designing, developing, and operating public and private internets and intranets. You can access the Internet Protocol Journal at this URL:

http://www.cisco.com/en/US/about/ac123/ac147/about_cisco_the_internet_protocol_journal.html

Training—Cisco offers world-class networking training. Current offerings in network training are listed at this URL:

http://www.cisco.com/en/US/learning/le31/learning_recommended_training_list.html