cc/td/doc/product/mels/15540x
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table Of Contents

Release Notes for Cisco ONS 15540 ESPx
for Cisco IOS Release 12.1(12c)EV

Contents

Introduction

System Requirements

Memory Requirements

Hardware Supported

Determining the Software Version

Upgrading the System Image

Feature Set Table

New and Changed Information

New Features in Release 12.1(12c)EV

New Features in Release 12.1(10)EV3

New Features in Release 12.1(10)EV2

Caveats

Limitations and Restrictions

Transponder Modules

Related Documentation

Obtaining Documentation

Cisco.com

Documentation CD-ROM

Ordering Documentation

Documentation Feedback

Obtaining Technical Assistance

Cisco.com

Technical Assistance Center

Obtaining Additional Publications and Information

Release Notes for Cisco ONS 15540 ESPx
for Cisco IOS Release 12.1(12c)EV


This document describes caveats for Cisco IOS Release 12.1(12c)EV for the Cisco ONS 15540 ESPx.

Date: January 27, 2003

Text Part Number: OL-3404-03

Contents

This document includes the following information:

Introduction

System Requirements

New and Changed Information

Caveats

Limitations and Restrictions

Related Documentation

Obtaining Documentation

Obtaining Technical Assistance

Introduction

The Cisco ONS 15540 ESPx is an optical transport platform that employs DWDM (dense wavelength division multiplexing) technology. With the Cisco ONS 15540 ESPx, users can take advantage of the availability of dark fiber to build a common infrastructure that supports data, SANs (storage area networks), and TDM (time-division multiplexing) traffic. The system uses an enhanced chassis with front fiber-optic cable access for optical interconnections between transponders and optical mux/demux modules. For more information about DWDM technology and applications, refer to the Introduction to DWDM Technology publication and the Cisco ONS 15540 ESPx Planning Guide.

System Requirements

This section describes the system requirements for Cisco IOS Release 12.1(12c)EV and includes the following sections:

Memory Requirements

Hardware Supported

Determining the Software Version

Upgrading the System Image

Feature Set Table

Memory Requirements

The DRAM memory configuration is 128 MB, which is the default for the Cisco ONS 15540 ESPx.

Hardware Supported

Table 1 lists the hardware components supported on the Cisco ONS 15540 ESPx and the minimum software version required. See the "Determining the Software Version" section for information on determining your software version.

Table 1 Cisco ONS 15540 ESPx Supported Hardware Modules and Minimum Software Requirements 

Component
Part Number
Description
Minimum Software Version Required

Chassis

15540-CHSB=

Chassis external connection system —19" RM, 14 U, 12 slots

12.1(10)EV1

Power supplies and spare power supply cables

15540-PWR-AC

120 to 240 VAC power supply

12.1(10)EV1

15540-CAB-AC

Custom AC-input power entry cable

12.1(10)EV1

15500-CAB-AC

North America

12.1(10)EV1

15500-CAB-ACA

Australia

12.1(10)EV1

15500-CAB-ACE

Europe

12.1(10)EV1

15500-CAB-CU

UK

12.1(10)EV1

15500-CAB-ACI

Italy

12.1(10)EV1

15500-CAB-ACR

Argentina

12.1(10)EV1

Blank motherboards and blank modules

15540-COV-07

Mux/demux motherboard blank panel

12.1(10)EV1

15540-COV-08

4 / 8 Ch. mux/demux blank panel

12.1(10)EV1

15540-COV-09

Line card motherboard blank panel

12.1(10)EV1

15540-COV-10

Transponder module blank panel

12.1(10)EV1

Fans

15540-FTMP=

Fan tray module populated with eight fans

12.1(10)EV1

Processor cards

15540-CPU

Processor card

12.1(10)EV1

Flash PC Cards

15500-PCMCIA16=

PCMCIA Memory Card 16Mb

12.1(10)EV1

15500-PCMCIA20=

PCMCIA Memory Card 20Mb

12.1(10)EV1

Mux/demux motherboards

15540-MMMB-1100

Supports mux/demux modules with OSC

12.1(10)EV1

15540-MMMB-1200

Supports mux/demux modules without OSC

12.1(10)EV1

Mux/demux modules without OSC

15540-MDXC-04A0

4-channel Band A

12.1(10)EV1

15540-MDXC-04B0

4-channel Band B

12.1(10)EV1

15540-MDXC-04C0

4-channel Band C

12.1(10)EV1

15540-MDXC-04D0

4-channel Band D

12.1(10)EV1

15540-MDXC-04E0

4-channel Band E

12.1(10)EV1

15540-MDXC-04F0

4-channel Band F

12.1(10)EV1

15540-MDXC-04G0

4-channel Band G

12.1(10)EV1

15540-MDXC-04H0

4-channel Band H

12.1(10)EV1

15540-MDXC-08A0

8-channel Band AB

12.1(10)EV1

15540-MDXC-08B0

8-channel Band CD

12.1(10)EV1

15540-MDXC-08C0

8-channel Band EF

12.1(10)EV1

15540-MDXC-08D0

8-channel Band GH

12.1(10)EV1

Mux/demux modules with OSC

15540-MDXD-04A0

4-channel Band A

12.1(10)EV1

15540-MDXD-04B0

4-channel Band B

12.1(10)EV1

15540-MDXD-04C0

4-channel Band C

12.1(10)EV1

15540-MDXD-04D0

4-channel Band D

12.1(10)EV1

15540-MDXD-04E0

4-channel Band E

12.1(10)EV1

15540-MDXD-04F0

4-channel Band F

12.1(10)EV1

15540-MDXD-04G0

4-channel Band G

12.1(10)EV1

15540-MDXD-04H0

4-channel Band H

12.1(10)EV1

15540-MDXD-08A0

8-channel Band AB

12.1(10)EV1

15540-MDXD-08B0

8-channel Band CD

12.1(10)EV1

15540-MDXD-08C0

8-channel Band EF

12.1(10)EV1

15540-MDXD-08D0

8-channel Band GH

12.1(10)EV1

15540-MDXD-32A0

32-channel AH

12.1(10)EV1

Line card motherboards

15540-LCMB-1100

Supports four transponders with protection or four extended range transponders with protection

12.1(10)EV1

15540-LCMB-1200

Supports four transponders without protection or four extended range transponders without protection

12.1(10)EV1

15540-LCMB-1400

Supports two 10-GE transponders with protection

12.1(10)EV2

15540-LCMB-1401

Supports two 10-GE transponders without protection

12.1(10)EV2

MM transponder modules

15540-TSP1-01A3

Ch 1-2 —1310-nm MM 16 to 622 Mbps with SC

12.1(10)EV1

15540-TSP1-03A3

Ch 3-4 —1310-nm MM 16 to 622 Mbps with SC

12.1(10)EV1

15540-TSP1-05A3

Ch 5-6 —1310-nm MM 16 to 622 Mbps with SC

12.1(10)EV1

15540-TSP1-07A3

Ch 7-8 — 310-nm MM 16 to 622 Mbps with SC

12.1(10)EV1

15540-TSP1-09A3

Ch 9-10 — 1310-nm MM 16 to 622 Mbps with SC

12.1(10)EV1

15540-TSP1-11A3

Ch 11-12 — 1310-nm MM 16 to 622 Mbps with SC

12.1(10)EV1

15540-TSP1-13A3

Ch 13-14 — 1310-nm MM 16 to 622 Mbps with SC

12.1(10)EV1

15540-TSP1-15A3

Ch 15-16 —1310-nm MM 16 to 622 Mbps with SC

12.1(10)EV1

15540-TSP1-17A3

Ch 17-18 —1310-nm MM 16 to 622 Mbps with SC

12.1(10)EV1

15540-TSP1-19A3

Ch 19-20 —1310nm MM 16 to 622 Mbps with SC

12.1(10)EV1

15540-TSP1-21A3

Ch 21-22 —1310-nm MM 16 to 622 Mbps with SC

12.1(10)EV1

15540-TSP1-23A3

Ch 23- 24—1310-nm MM 16 to 622 Mbps with SC

12.1(10)EV1

15540-TSP1-25A3

Ch 25-26—1310-nm MM 16 to 622 Mbps with SC

12.1(10)EV1

15540-TSP1-27A3

Ch 27-28—1310-nm MM 16 to 622 Mbps with SC

12.1(10)EV1

15540-TSP1-29A3

Ch 29-30—1310-nm MM 16 to 622 Mbps with SC

12.1(10)EV1

15540-TSP1-31A3

Ch 31-32—1310-nm MM 16 to 622 Mbps with SC

12.1(10)EV1

SM transponder modules

15540-TSP1-01B3

Ch 1-2—1310-nm SM 16 Mbps to 2.5 Gbps with SC

12.1(10)EV1

15540-TSP1-03B3

Ch 3-4—1310-nm SM 16 Mbps to 2.5 Gbps with SC

12.1(10)EV1

15540-TSP1-05B3

Ch 5-6—1310-nm SM 16 Mbps to 2.5 Gbps with SC

12.1(10)EV1

15540-TSP1-07B3

Ch 7-8—1310-nm SM 16 Mbps to 2.5 Gbps with SC

12.1(10)EV1

15540-TSP1-09B3

Ch 9-10—1310-nm SM 16 Mbps to 2.5 Gbps with SC

12.1(10)EV1

15540-TSP1-11B3

Ch 11-12—1310-nm SM 16 Mbps to 2.5 Gbps with SC

12.1(10)EV1

15540-TSP1-13B3

Ch 13-14— 1310-nm SM 16 Mbps to 2.5 Gbps with SC

12.1(10)EV1

15540-TSP1-15B3

Ch 15-16—1310-nm SM 16 Mbps to 2.5 Gbps with SC

12.1(10)EV1

15540-TSP1-17B3

Ch 17-18—1310-nm SM 16 Mbps to 2.5 Gbps with SC

12.1(10)EV1

15540-TSP1-19B3

Ch 19-20—1310nm SM 16 Mbps to 2.5 Gbps with SC

12.1(10)EV1

15540-TSP1-21B3

Ch 21-22—1310-nm SM 16 Mbps to 2.5 Gbps with SC

12.1(10)EV1

15540-TSP1-23B3

Ch 23- 24—1310-nm SM 16 Mbps to 2.5 Gbps with SC

12.1(10)EV1

15540-TSP1-23B3

Ch 23- 24—1310-nm SM 16 Mbps to 2.5 Gbps with SC

12.1(10)EV1

15540-TSP1-25B3

Ch 25-26—1310-nm SM 16 Mbps to 2.5 Gbps with SC

12.1(10)EV1

15540-TSP1-27B3

Ch 27-28—1310-nm SM 16 Mbps to 2.5 Gbps with SC

12.1(10)EV1

15540-TSP1-29B3

Ch 29-30 —1310-nm SM 16 Mbps to 2.5 Gbps with SC

12.1(10)EV1

15540-TSP1-31B3

Ch 31-32—1310-nm SM 16 Mbps to 2.5 Gbps with SC

12.1(10)EV1

Extended range transponder modules supporting SFP optics

15540-TSP2-0100

Ch 1-2

12.1(10)EV1

15540-TSP2-0300

Ch 3-4

12.1(10)EV1

15540-TSP2-0500

Ch 5-6

12.1(10)EV1

15540-TSP2-0700

Ch 7-8

12.1(10)EV1

15540-TSP2-0900

Ch 9-10

12.1(10)EV1

15540-TSP2-1100

Ch 11-12

12.1(10)EV1

15540-TSP2-1300

Ch 13-14

12.1(10)EV1

15540-TSP2-1500

Ch 15-16

12.1(10)EV1

15540-TSP2-1700

Ch 17-18

12.1(10)EV1

15540-TSP2-1900

Ch 19-20

12.1(10)EV1

15540-TSP2-2100

Ch 21-22

12.1(10)EV1

15540-TSP2-2300

Ch 23-24

12.1(10)EV1

15540-TSP2-2500

Ch 25-26

12.1(10)EV1

15540-TSP2-2700

Ch 27-28

12.1(10)EV1

15540-TSP2-2900

Ch 29-30

12.1(10)EV1

15540-TSP2-3100

Ch 31-32

12.1(10)EV1

Single port 10-Gigabit Ethernet transponder modules

15540-10GE-03B301

10-GE 1310nm SM Client with SC and ITU Laser Ch 1

12.1(10)EV2

15540-10GE-03B302

10-GE 1310nm SM Client with SC and ITU Laser Ch 2

12.1(10)EV2

15540-10GE-03B303

10-GE 1310nm SM Client with SC and ITU Laser Ch 3

12.1(10)EV2

15540-10GE-03B304

10-GE 1310nm SM Client with SC and ITU Laser Ch 4

12.1(10)EV2

15540-10GE-03B305

10-GE 1310nm SM Client with SC and ITU Laser Ch 5

12.1(10)EV2

15540-10GE-03B306

10-GE 1310nm SM Client with SC and ITU Laser Ch 6

12.1(10)EV2

15540-10GE-03B307

10-GE 1310nm SM Client with SC and ITU Laser Ch 7

12.1(10)EV2

15540-10GE-03B308

10-GE 1310nm SM Client with SC and ITU Laser Ch8

12.1(10)EV2

15540-10GE-03B309

10-GE 1310nm SM Client with SC and ITU Laser Ch 9

12.1(10)EV2

15540-10GE-03B3010

10-GE 1310nm SM Client with SC and ITU Laser Ch 10

12.1(10)EV2

15540-10GE-03B3011

10-GE 1310nm SM Client with SC and ITU Laser Ch 11

12.1(10)EV2

15540-10GE-03B3012

10-GE 1310nm SM Client with SC and ITU Laser Ch 12

12.1(10)EV2

15540-10GE-03B3013

10-GE 1310nm SM Client with SC and ITU Laser Ch 13

12.1(10)EV2

15540-10GE-03B3014

10-GE 1310nm SM Client with SC and ITU Laser Ch 14

12.1(10)EV2

15540-10GE-03B3015

10-GE 1310nm SM Client with SC and ITU Laser Ch 15

12.1(10)EV2

15540-10GE-03B3016

10-GE 1310nm SM Client with SC and ITU Laser Ch 16

12.1(10)EV2

15540-10GE-03B3017

10-GE 1310nm SM Client with SC and ITU Laser Ch 17

12.1(10)EV2

15540-10GE-03B3018

10-GE 1310nm SM Client with SC and ITU Laser Ch 18

12.1(10)EV2

15540-10GE-03B3019

10-GE 1310nm SM Client with SC and ITU Laser Ch 19

12.1(10)EV2

15540-10GE-03B3020

10-GE 1310nm SM Client with SC and ITU Laser Ch 20

12.1(10)EV2

15540-10GE-03B3021

10-GE 1310nm SM Client with SC and ITU Laser Ch 21

12.1(10)EV2

15540-10GE-03B3022

10-GE 1310nm SM Client with SC and ITU Laser Ch 22

12.1(10)EV2

15540-10GE-03B3023

10-GE 1310nm SM Client with SC and ITU Laser Ch 23

12.1(10)EV2

15540-10GE-03B3024

10-GE 1310nm SM Client with SC and ITU Laser Ch 24

12.1(10)EV2

15540-10GE-03B3025

10-GE 1310nm SM Client with SC and ITU Laser Ch 25

12.1(10)EV2

15540-10GE-03B3026

10-GE 1310nm SM Client with SC and ITU Laser Ch 26

12.1(10)EV2

15540-10GE-03B3027

10-GE 1310nm SM Client with SC and ITU Laser Ch 27

12.1(10)EV2

15540-10GE-03B3028

10-GE 1310nm SM Client with SC and ITU Laser Ch 28

12.1(10)EV2

15540-10GE-03B3029

10-GE 1310nm SM Client with SC and ITU Laser Ch 29

12.1(10)EV2

15540-10GE-03B3030

10-GE 1310nm SM Client with SC and ITU Laser Ch 30

12.1(10)EV2

15540-10GE-03B3031

10-GE 1310nm SM Client with SC and ITU Laser Ch 31

12.1(10)EV2

15540-10GE-03B3032

10-GE 1310nm SM Client with SC and ITU Laser Ch 32

12.1(10)EV2

Pluggable SFP optics for extended range transponder modules

15500-XVRA-01A2

ESCON and OC-3 1310-nm MM MT-RJ

12.1(10)EV1

15500-XVRA-03B1

Gigabit Ethernet and Fibre Channel (1 Gbps)
1310-nm SM MTLC

12.1(10)EV1

15500-XVRA-03B2

Fibre Channel (1 Gbps and 2 Gbps) 1310-nm SM MTLC

12.1(10)EV1

15500-XVRA-02C1

Gigabit Ethernet and Fibre Channel (1 Gbps)
850-nm MM MTLC

12.1(10)EV1

15500-XVRA-02C2

Fibre Channel (2 Gbps) 850-nm MM MTLC

12.1(10)EV1

15500-XVRA-07B1

SONET OC-12 1310-nm SM MTLC

12.1(10)EV1

15500-XVRA-07B1

SONET OC-48 1310-nm SM MTLC

12.1(10)EV1

Protection switch module

15540-PSM-01

ONS 15540 protection switch module

12.1(12c)EV

Optical cross connect

15500-CCDK01

ONS 15500 cross connect drawer kit

12.1(10)EV1

15500-CSDK01

ONS 15500 cable storage drawer kit

12.1(10)EV1

15500-VCGK01

ONS 15500 vertical cable guide kit

12.1(10)EV1

15500-CAB-MU-ADTR=

ONS 15540 MU-MU insertion adapter

12.1(10)EV1

15500-CAB-TL01=

Cable installation and removal tool. SFP removal tool.

12.1(10)EV1

Optical cable kits

15500-CAB-KIT1

Cable kit 1 - (order 1x for LCMB without splitter, order 2x for LCMB with splitter): 2x MTP-8MU, 2x MU adapter, 8x MU-MU

12.1(10)EV1

MTP cables

15500-CAB-MTP-01=

86" MTP to MTP cable - 2.5-Gbps line card motherboard

12.1(10)EV1

Optical trunk cables (symplex)

15500-CAB-MSC01=

1.0m Tuned Low Loss MU to SC SM Patch Cable

12.1(10)EV1

15500-CAB-MSC02=

3.0m Tuned Low Loss MU to SC SM Patch Cable

12.1(10)EV1

15500-CAB-MST03=

1.0m Tuned Low Loss MU to ST SM Patch Cable

12.1(10)EV1

15500-CAB-MST04=

3.0m Tuned Low Loss MU to ST SM Patch Cable

12.1(10)EV1

Optical OADM and intra chassis cables (symplex)

15500-CAB-MMU-01=

0.25m (10") tuned low loss MU to MU SM OADM patch cable

12.1(10)EV1

15500-CAB-MMU-02=

0.35m (14") tuned low loss MU to MU SM OADM patch cable

12.1(10)EV1

15500-CAB-MMU-03=

0.45m (17") tuned low loss MU to MU SM OADM patch cable

12.1(10)EV1

15500-CAB-MMU-04=

0.5m (20") tuned low loss MU to MU SM OADM patch cable

12.1(10)EV1

15500-CAB-MMU-05=

1.0m (40") tuned low loss MU to MU SM OADM patch cable

12.1(10)EV1

15500-CAB-MMU-09=

1.16m (46") tuned low loss MU to MU SM OADM patch cable

12.1(10)EV1

15500-CAB-MMU-06=

1.5m (60") tuned low loss MU to MU SM OADM patch cable

12.1(10)EV1

15500-CAB-MMU-07=

2.0m (79") tuned low loss MU to MU SM OADM patch cable

12.1(10)EV1

15500-CAB-MMU-08=

2.5m (98") tuned low loss MU to MU SM OADM patch cable

12.1(10)EV1

Optical client cables (symplex)

15500-CAB-SC11=

1.0m SC to SC 62.5/125um MM cable

12.1(10)EV1

15500-CAB-SC19=

1.0m SC to SC 50/125um MM cable

12.1(10)EV1

15500-CAB-SC12=

1.0m SC to SC SM cable

12.1(10)EV1

15500-CAB-SC13=

3.0m SC to SC 62.5/125um MM cable

12.1(10)EV1

15500-CAB-SC20=

3.0m SC to SC 50/125um MM cable

12.1(10)EV1

15500-CAB-SC14=

3.0m SC to SC SM cable

12.1(10)EV1

15500-CAB-ST15=

1.0m SC to ST 62.5/125um MM cable

12.1(10)EV1

15500-CAB-ST21=

1.0m SC to ST 50/125um MM cable

12.1(10)EV1

15500-CAB-ST16=

1.0m SC to ST SM cable

12.1(10)EV1

15500-CAB-ST17=

3.0m SC to ST 62.5/125um MM cable

12.1(10)EV1

15500-CAB-ST22=

3.0m SC to ST 50/125um MM cable

12.1(10)EV1

15500-CAB-ST18=

3.0m SC to ST SM cable

12.1(10)EV1

Optical y-cables

15500-CAB-YMM-SC=

50/125um multimode y cable with SC for channel protection

12.1(10)EV1

15500-CAB-YMM2-SC=

62.5/125um multimode y cable with SC for channel protection

12.1(10)EV1

15500-CAB-YSM-SC=

single mode y cable with SC for channel protection

12.1(10)EV1

15500-CAB-YMM-SC=

50/125um multimode y cable with SC for channel protection

12.1(10)EV1


Determining the Software Version


Note We strongly recommend that you use the latest available software release for all Cisco ONS 15540 ESPx hardware.


To determine the version of Cisco IOS software currently running on a Cisco ONS 15540 ESPx system, log in to the system and enter the show version EXEC command.

Upgrading the System Image

To ensure proper system functioning, follow the system image upgrading procedure described in the Cisco ONS 15540 ESPx Software Upgrade Guide.


Note Always set the configuration register to 0x2102 when upgrading the system image using the config-reg 0x2102 command in configuration mode.



Caution Improper system image upgrades can affect system functioning and redundancy. Always follow the recommended upgrade procedures.

Feature Set Table

The Cisco IOS Release software is packaged in feature sets (also called software images) depending on the platform. Each feature set contains a specific set of Cisco IOS software features. Table 2 lists the Cisco IOS software feature sets available for the Cisco ONS 15540 ESPx.

Table 2 Feature Sets Supported by the Cisco ONS 15540 ESPx 

Feature Set
12.1(12c)EV
12.1(10)EV3
12.1(10)EV2
12.1(10)EV1

Gigabit Ethernet

X

X

X

X

Fast Ethernet

X

X

X

X

Ethernet

X

X

X

X

ATM OC-3/STM-1, OC-12/STM-4, and OC-48/STM-16

X

X

X

X

SONET1 /SDH2

X

X

X

X

POS3

X

X

X

X

Fibre Channel (1 Gbps)

X

X

X

X

Fibre Channel (2 Gbps)

X

X

X

X

FDDI4

X

X

X

X

ESCON5 SM (200 Mbps)

X

X

X

X

FICON6 (800 Mbps)

X

X

X

X

Token Ring

X

X

X

X

SNMP

X

X

X

X

CiscoView

X

X

X

X

Cisco Transport Manager

X

X

X

X

CDP7

X

X

X

X

IP packets

X

X

X

X

OSCP8

X

X

X

X

APS9 protocol packets

X

X

X

X

Point-to-point

X

X

X

X

Hubbed ring

X

X

X

X

Meshed ring

X

X

X

X

IBM GDPS10 ETR/CL

X

X

X

X

IBM GDPS 10 coupling link

X

X

X

X

Unidirectional path switching

X

X

X

X

Bidirectional path switching

X

X

X

X

CDL over 10-GE

X

X

X

 

1 SONET = Synchronous Optical Networking

2 SDH = Synchronous Digital Hierarchy

3 POS = Packet over SONET

4 FDDI = Fiber Distributed Data Interface

5 ESCON = Enterprise Systems Connection

6 FICON = Fiber Connection

7 CDP = Cisco Discovery Protocol

8 OSCP = Optical Supervisory Channel Protocol

9 APS = Automatic Protection Switching

10 GDPS = Geographically Dispersed Parallel Sysplex


New and Changed Information

This section lists new features that appear in Cisco IOS Release 12.1.

New Features in Release 12.1(12c)EV

The following new feature is available for the Cisco ONS 15540 ESPx in Cisco IOS Release 12.1(12c)EV:

The Cisco ONS 15540 Protection Switch Module (PSM) allows a customer to protect the entire fiber path by splitting an optical signal from one fiber trunk into two redundant fiber paths. This offers customers a cost-effective protection option and added protection against fiber cuts in the network.

New Features in Release 12.1(10)EV3

No new features are available for the Cisco ONS 15540 ESPx in Cisco IOS Release 12.1(10)EV3.

New Features in Release 12.1(10)EV2

The following new features are available for the Cisco ONS 15540 ESPx in Cisco IOS Release 12.1(10)EV2:

Hardware:

Non-protected dual subslot motherboard for Cisco ONS 15540 ESPx

Splitter protected dual subslot motherboard for Cisco ONS 15540 ESPx

10-GE transponder module

Software:

CDL over 10-GE

Caveats

This section lists the caveats and corrected caveats for each release. Use Table 3 to determine the status of a particular caveat. In the tables, "C" indicates a corrected caveat, and "O" indicates an open caveat.

Table 3 Caveat Matrix for the Cisco ONS 15540 ESPx 

DDTS Number
12.1(12c)EV
12.1(10)EV3
12.1(10)EV2
12.1(10)EV1

CSCdx07666

O

O

O

O

CSCdx32438

O

O

O

O

CSCdx37144

C

C

C

C

CSCdx42463

C

C

C

C

CSCdx70683

C

C

C

C

CSCdx80175

C

C

C

C

CSCdx80804

C

C

C

C

CSCdx85761

C

C

   

CSCdx87061

C

C

C

C

CSCdx89540

C

C

C

C

CSCdy03076

C

C

C

C

CSCdy03245

C

C

   

CSCdy08228

C

C

   

CSCdy20002

C

C

   

CSCdy20010

C

C

   

CSCdy20022

C

C

   

CSCdy20792

C

C

C

 

CSCdy30497

C

C

   

CSCdy40352

C

C

O

O

CSCdy40429

C

C

C

C

CSCdy40465

C

C

C

C

CSCdy40864

C

C

   

CSCdy40882

C

C

   

CSCdy44129

C

C

O

 

CSCdy49146

C

C

C

C

CSCdy49249

C

C

   

CSCdy53288

C

C

   

CSCdy58197

C

C

O

 

CSCdy61641

C

C

   

CSCdy62752

C

C

   

CSCdy63359

C

C

   

CSCdy65411

C

C

   

CSCdy78546

C

C

   

CSCdy79161

C

C

O

 

CSCdy79659

C

C

   

CSCdy79812

C

C

O

 

CSCdy81888

C

C

O

 

CSCdy83757

C

C

   

CSCdy85563

C

C

   

CSCdy87237

C

C

   

CSCdy88154

C

C

   

CSCdz00116

C

C

   

CSCdz02296

C

C

   

CSCdz02340

C

C

   

CSCdz03989

C

C

   

CSCdz06004

C

C

   

CSCdz06602

C

C

   

CSCdz08774

C

C

   

CSCdz12919

C

C

   

CSCdz13538

C

C

   

CSCdz13673

C

C

   

CSCdz14420

C

C

   

CSCdz18757

C

C

   

CSCdz18815

C

C

   

CSCdz19099

C

C

   

CSCdz20508

C

C

   

CSCdz22455

C

C

   

CSCdz25739

C

O

   

CSCdz28582

C

C

   

CSCdz28903

C

C

   

CSCdz29723

O

O

   

CSCdz31593

O

O

   

CSCdz33752

C

C

   

CSCdz36420

C

C

   

CSCdz36424

C

O

   

CSCdz36823

C

C

   

CSCdz37698

C

C

   

CSCdz37968

C

C

   

CSCdz38075

C

C

   

CSCdz38448

C

O

   

CSCdz38968

C

C

   

CSCdz39112

C

O

   

CSCdz39793

C

O

   

CSCdz40675

C

     

CSCdz41160

C

O

   

CSCdz42547

C

O

   

CSCdz42565

C

O

   

CSCdz43279

C

O

   

CSCdz58866

C

     

CSCdz62296

O

     

CSCdz62553

C

     

CSCdz66609

O

     

CSCdz75109

C

     

CSCdz79336

O

     

CSCdz80042

O

     

CSCdz83169

O

     

CSCdz85458

O

     

This section describes the caveats in the Cisco ONS 15540 ESPx.

CSCdx07666

Symptom: Loss of signal might occur before SD (signal degrade) and SF (signal failure) thresholds are exceeded and traffic may still continue to pass transparently.

The loss of signal detection is taken from the OE (optical to electrical) conversion subsystem, which is different from the source of the SD and SF counters. The loss of light sensitivity is a characteristic of the OE conversion unit, and it may vary from unit to unit but is always < -30dBm.

Workaround: None.

CSCdx32438

Symptom: When the Rx port fiber is removed from the transponder module, ingress alarms are reported and cleared repeatedly. The alarm should not clear and the alarm should be reported only once.

Workaround: None

CSCdx37144

Symptom: Processor card gets into a nonresponsive state.

Workaround: None

CSCdx42463

Symptom: Processor card gets into a nonresponsive state for an extended interval, during which time the active standby LEDs may not indicate the correct active standby state.

Workaround: If the processor card has not been reset by the redundant processor card, the nonresponsive processor card can be removed and re-inserted in the chassis. This may cause a brief hit to data traffic, but the redundant processor card should take over and bring the system back up.

CSCdx70683

Symptom: The reprogram for the standby processor card fails.

Workaround: Run the reprogram on the active processor card, enable the processor switchover after switchover, and then run the reprogram on the new active processor card. Remove and reinsert the processor card for the new FPGA to become effective.

CSCdx80804

Symptom: The encapsulation fastethernet command fails on multimode transponders. The clock rate 100000 command succeeds but then pings over the signal fail intermittently.

Workaround: None.

CSCdx80175

Symptom: The show interface command output for a wave interface displays an "up" state, but the Signal Quality shows loss of sync.

Workaround: None.

CSCdx85761

Symptom: Multiple %METOPT-2-PORTFAIL messages are seen when using the y-cable aps configuration with single AFOV. However, this does not affect the functionality.

Workaround: None.

CSCdx87061

Symptom: CiscoView might display a different receive LED status on transponders from what is actually seen on the device.

Workaround: None.

CSCdx89540

Symptom: Client transmit enabled upon insertion disrupts y-cable clients.

Workaround: Remove client transmit fiber (y-cable leg) from the standby transponder before reinserting. Connect it back a few seconds after re-insertion of the standby transponder.

CSCdy03076

Symptom: The first time you OIR the OSC linecard, the card is brought into the admindown state.

Workaround: Enter the no shutdown command when the interface recovers.

CSCdy03245

Symptom: Topology Neighbour configuration is lost on mux-demux motherboard OIR.

Workaround:The topology neighbour is viewable after reconfiguring the wdm interface.

CSCdy08228

Symptom:Interface reports up/up even when there is no light source connected.

Workaround: Perform a shut and then a no shut on the interface.

CSCdy20002

Symptom: A transparent interface carrying Gigabit Ethernet traffic and configured with gigabit Fibre Channel encapsulation shows good quality signal on the show interfaces transparent command output and does not assert any ingress alarms. The wave interface assert loss of lock and loss of sync alarms.

Workaround: OIR the transponder will bring it to the correct state.

CSCdy20010

Symptom: The LoF alarms donot reassert inthe show facility-alarm status after shut/no shut.

Workaround:Disabling and reenabling the monitoring for the transparent interface will bring back the alarms.

CSCdy20022

Symptom: The show facility-alarm status does not report existing LoF/LoSync/LoLock alarms after

OIR/hw-mod power off/on.

Workaround: Disable and enable monitoring back reassert existing alarms in the show facility-alarm status.

CSCdy20792

Symptom: After removing and reinserting (OIR) of a transponder, the laser frequency is not programmed to the transponder correctly which results in a wavelength filter mismatch and the wavelength not coming out of the filter.

Workaround: Configure the Wave interface for the alternate frequency and then program it back to the desired frequency using the laser frequency <value in MHz> command.

CSCdy30497

Symptom: Line card function version in IOS should return the hex value.

Workaround: None.

CSCdy40352

Symptom: The processor card gets stuck in a nonresponsive state waiting for the console UART TxReady to get set. Normally a watchdog timeout will force recovery, but in some instances the Standby processor card does not recover on its own.

Workaround: Remove and replace the standby processor card.

CSCdy40429

Symptom: Under some situations the erratas of the system controller used on the processor card (GT64120A) can cause:

— A software forced crash due to memory ECC errors

— A bus error exception

— Corruption of data

Workaround: None.

CSCdy40465

Symptom: Processor card becomes nonresponsive and does not respond to an NMI.

Workaround: Update processor card image to version 1.25 or higher.

CSCdy40864

Symptom: A compatibility problem was detected in the released images that caused them to reject communication with the new images with a different cpu_red client version. This will cause the Active cpu to reset the Peer cpu.

Workaround: Since this problem comes into existance only if the cpu_red client version is different between 2 images, this problem doesn't exist in the old released images. Since the new images with the incremented cpu_red client version contains the fix for compatibility as well, this bug should not cause any impact in the field.

CSCdy40882

Symptom: CPU info showing up in sh hard, even after removing.

Workaround: None.

CSCdy44129

Symptom: If a Downlink Client interface is configured for CDL but is connected to a non-CDL device, the CDL message channel is down.

Workaround: Ensure Downlink Client interface is configured correctly.

CSCdy49146

Symptom: Under some circumstances, single bit ECC errors occur and are corrected by the system controller, but are not recorded; the user is unaware of these occurances.

Workaround: None.

CSCdy49249

Symptom: If a line card which was earlier removed or never inserted before switchover and if it gets inserted while a switchover is happening, then the line card and its interfaces may not come up properly.

Workaround: Re-insert line cardafter switchover is complete.

CSCdy53288

Symptom: The Cisco ONS 15540 might crash when using the is_optical_ifstatus_up command; this is an intermittent problem.

Workaround: None.

CSCdy58197

Symptom: In a configuration where a Cisco ONS 15540 ESPx has 10-GE downlinks to two Cisco ONS 15530 systems, the tengigethernetphy interface is administratively shut down and the ESCON ports associated with the first Cisco ONS 15530 are also downed. However, the ESCON ports connected to the second Cisco ONS 15530 are still up.

Workaround: Down the tengigethernetphy interface associated with the second Cisco ONS 15530.

CSCdy61641

Symptom: Following a CPU crash and switchover, if a show redundancy command is issued on the new Active CPU, it currently shows "Reported Switchover Reason" as "Not known". If a show version is issued on the Standby CPU that crashed, it shows additional troubleshooting information.

Workaround: None.

CSCdy62752

Symptom: A few kinds of software exceptions on the Active CPU can disable the ability for the standby CPU to reset the Active CPU if the Active CPU becomes non-responsive.

Workaround: None.

CSCdy63359

Symptom: getmany on ifMIB hangs in a loop.

Workaround: None.

CSCdy65411

Symptom:It takes about 15 minutes for a mode-mismatch event/trap to be set/generated after the mis-configuration that causes it is configured on the system.

Workaround: None.

CSCdy78546

Symptom: From snmp, ptopoConnEntry can be created with entPhysicalIndex, which does not correspond to any valid interface on the box.

Workaround: None.

CSCdy79161

Symptom: Configuring both line and trunk side loopback on the 10-GE trunk card affects the Traffic flow.

Workaround: Reconfigure the 10-GE trunk card with loopback on only line or trunk side, not both. OIR the 10-GE card to restore traffic.

CSCdy79659

Symptom: Incorrect OPM behavior.

Workaround: None.

CSCdy79812

Symptom: CDL hec counters are displayed in the show interface tengigethernetphy when CDL is disabled.

Workaround: None.

CSCdy81888

Symptom: Traffic is disrupted on bootup and switchover when the client side of the 10-GE trunk card has CDL disabled and both the client side and the trunk side are configured for cdl force hop

Workaround: Use the no cdl defect-indication force hop command on the client side.

CSCdy83757

Symptom: Unable to manage box configured with eigrp after a CPU switchover.

Workaround: Connect to the console port and remove passive-interface config in eigrp configuration.

CSCdy85563

Symptom:The DI error message does not indicate DI bit status.

Workaround: None.

CSCdy87237

Symptom: Line Laser Failure not reported in sh fac stat at TSP2 XCVR OIR.

Workaround: None.

CSCdy88154

Symptom: Some interfaces will not be available to the NMS station since the agent does not create them on OIR.

Workaround: Reload the box after removal/insertion of the cards.

CSCdz00116

Symptom: APS message channel configured for UDP/IP does not work over more than 2 IP hops. The UDP/IP packet gets dropped at the end of the second hop.

Workaround: None.

CSCdz02296

Symptom: Oir of SFA doesnt reflect correct patch status for pom & mux.

Workaround: None.

CSCdz02340

Symptom: Traceback @optical_idb_wave_ethernet_phy_report.

Workaround: None.

CSCdz03989

Symptom: Both active and standby lasers in a bidirectional y-cable APS configuration on modules in sub-slot 0 turn on erroneously.

Workaround: This bug has been fixed by using the correct format for programming the switchover-command register.

CSCdz06004

Symptom: The redundancy reload shelf command on the Active cpu can cause a switchover if the peer cpu is in Rommon.

Workaround: Use the reload command to reload the Active cpu, if the peer cpu is in Rommon.

CSCdz06602

Symptom: All interval entries of OPM are not returned by getnext.

Workaround: None.

CSCdz08774

Symptom: ciscoFlashDeviceChangeTrap should be supported on ONS155xx platforms since it is a basic operation. Whenever a removable flash device is removed/inserted, this trap should be generated.

Workaround:None.

CSCdz12919

Symptom: When forward laser control feature is enabled in hardware (either due to user configuration or due to Y-cable configuration), and the waveEthernet interface laser is shut by this safety feature, the laser soft-start procedure has to be followed when the laser is enabled again.

Workaround: None.

CSCdz13538

Symptom: The egress Loss of Signal alarm is not reasserted in the show facility status after hw-module power is turned off/on.

Workaround: None.

CSCdz13673

Symptom: The wave i/f remains down when the signal quality is GOOD and after the hw-module power off/on.

Workaround: None.

CSCdz14420

Symptom: The Rx Power display in some cases is off by +/-4dBm in comparision with the real reading using power meter.

Workaround: Use a calibrated transponder.

CSCdz18757

Symptom: The default laser frequencies of the transponders in 'odd' subslot (i. e. x/1 or x/3) are not restored correctly after the second OIR. The laser frequencies are stored correctly for the first OIR only.

For example, when inserting a transponder (channel n and channel n+1) to subslot x/1 the first time, the default laser frequency is n+1 (correct). Remove this transponder and insert another (channel m and channel m+1), the default laser frequency becomes m (incorrect; it should be m+1).

Workaround:OIR the linecard.

CSCdz18815

Symptom: False alarm LCMDC-3-OPT-SWITCH-FAIL while force APS switchover.

Workaround: None.

CSCdz19099

Symptom: Not obvious. The optical receive power level displayed on the show interface is not very accurate. It may be off as much as +/-4dBm in some cases but most of the cases it is OK.

Workaround: None.

CSCdz20508

Symptom: The wavepatches are stuck in the down state after using the sh/no sh of wave interface command with splitter APS after the trunk fiber has been cut.

Workaround: None.

CSCdz22455

Symptom:System crashes due to PCI Master abort while doing Sandisk OIR.

Workaround: None.

CSCdz25739

Symptom: The low warning threshold alarm is not cleared in the show facility command output.

Workaround: None.

CSCdz28582

Symptom: After a fiber cut, the OSC interface remains up with signal quality good.

Workaround: Use the shut/no shut command.

CSCdz28903

Symptom: For the sysplex protocol, the end-to-end FLC setting in the ctrl-mode is not correctly programmed after the OIR/FPGA reprogram.

Workaround: Using the no encap and encap sysplex etr commands on the transparent interface will program it correctly.

CSCdz29723

Symptom: When APS communication goes down, and an APS failure is subsequently detected, APS may switchover even though the communication is down. Based on this type of failure, there may be a unidirectional switchover. For IBM sysplex CLO/ETR applications, unidirectional switchover may lead to data corruption.

Workaround: None.

CSCdz31593

Symptom: In a point-to-point bidirectional situation, when the trunk Rx on both NEs are pulled and one of them is later replaced, APS may go back-and-forth between Working and Protection. The root cause is a hardware limitation consisting of no monitoring on the standby. As a result, the driver declares both Working and Protection as down when the wave interface goes down. In bidirectional APS this essentially means that the local side may inform the remote side that Working/Protection is down when it is not really down. APS has the ability to settle down on the good side, however, due to the bidirectional message (DO-NOT-REVERT in this case) from the far side; the local side switches away from the good side, and the cycle repeats. Note that this problem does not always happen, and requires certain timing in order for it happen.

Workaround:

1. Use force switch or lockout to peg the receive to the good side.

2. Temporarily change the direction from bidirectional to unidirectional. This however requires disabling the group.

CSCdz33752

Symptom: In bidirectional APS, if both NEs have the same priority request, the master/slave determination fails, leading to both claiming the control and resulting in not sending a REVERSE-REQUEST.

Workaround: None.

CSCdz36420

Symptom: In a pre-configured APS group (for the case when the interfaces don't exist), if the group is configured for revertive mode, it cannot be enabled.

Workaround: None.

CSCdz36424

Symptom: Attempting to read a flash card formatted on another system causes advisory messages to be continuously printed to the console.

Workaround:None.

CSCdz36823

Symptom: cpu crash after midnight with optical performance on when an interface capable of performance monitoring is un-shutdown.

Workaround:None.

CSCdz37698

Symptom: Both working and protection client tx active in y-cable aps.

Workaround:None.

CSCdz37968

Symptom: The hw-module power on/off command is not supported for 10G downlink cards on the Cisco ONS 15540.

Workaround: None.

CSCdz38075

Symptom: Data traffic hit during the CPU switchover when the splitter aps is configured.

Workaround: None.

CSCdz38448

Symptom:In 10G Y-cable bi-directional APS configuration, whenever there are lots of CVRD errors received on the standby trunk due to a bad signal,(but still signal quality is GOOD in "sh interface") all the four FDI-H/E, and BDI-H/E bits in the DECCSR register MIGHT get latched. Due to this, lots of interrupts would be generated and the console flooded with a similar message for that interface:

00:15:17: %APS-3-PORT_FAIL: External Port Fail On WaveEthernetPhy10/1

Workaround: Improve the quality of the signal by removing some attenuation and/or cleaning the optical connectors so that CVRD errors are not seen.

CSCdz38968

Symptom: Spurious memory access is seen on OIR of 10G downlink card.

Workaround: None.

CSCdz39112

Symptom:When an invalid channel number is detected by the OSCP client while it processes the client message received from peer, OSCP does not free the message buffer. This results in buffer starvation over a period of time and connectivity via Network Management interface and Back Plane ethernet(IPC and OSCP) interface are lost.

Workaround: None.

CSCdz39793

Symptom: The optical alarms are not asserted or cleared correctly when the wave is in the administrative down state.

Workaround: Use the shut/no shut command on the Active wavepatch; the no shut command on the wave will clear the false alarms.

CSCdz40675

Symptom: When Rx power is low, the alarm and warning are not asserted on the wavepatch interface after switchover, from active wavepatch to standby wavepatch.

Workaround: None.

CSCdz41160

Symptom: Continuous SRC poll failure after removing the calibrated transponder and inserting it back into the non-calibrated transponder/POM card.

Workaround: None.

CSCdz42547

Symptom: Using the no shut command on the tenGigEthernetPhy or waveethernetPhy interfaces (which is DOWN due to Loss of Lock) brings the interface state to UP, even though the Loss of Lock is still asserted.

Workaround: Use the sh/no sh command on the interface for it to show the DOWN state.

CSCdz42565

Symptom: Loss of Sync is not re-asserted on the tengigEthernetPhy interface after a shut/no shut command has been issued on the interface, or on an OIR of the 10G module.

Workaround: None.

CSCdz43279

Symptom: The EtherDcc interface for 10GE cards is not in the ADMIN DOWN state onthe initial OIR of the module.

Workaround: None.

CSCdz58866

Symptom: Threshold group line is missing in the show interfaces waveethernetphy command output.

Workaround: None.

CSCdz62296

Symptom: PSMs are incorrectly recognized as a mux/demux card with IOS images that do not support the PSM.

Workaround: Upgrade software to 12.1(12c)EV.

CSCdz62553

Symptom: The tengigEthernetPhy interface is getting BDIH while the in-band message channel is disabled.

Workaround: None.

CSCdz66609

Symptom: Traffic loss of 30-45 sec may occur when a y-cable APS configuration with protection switchover is used with the Catalyst 6000 family.

Workaround: Disable auto-negotiation and enable debounce timer with a 100-ms delay on Catalyst 6000 family using the set port debounce mod/port enable command.

CSCdz75109

Symptom: When y-cable APS is configured, shutting off the power to the transponder using the hw-module power off command brings the power back on again immediately.

Workaround: Remove the APS configuration and perform power off.

CSCdz79336

Symptom: APS switchover time (50 ms) is not guaranteed for loss of lock, loss of sync, or loss of frame.

Workaround: None.

CSCdz80042

Symptom: The output of the show waveethernetphy interface command sometimes shows a high receive power value when there is no input signal connected to the card.

Workaround: OIR the card.

CSCdz83169

Symptom: Could not get a wave interface power reading graph with CiscoView 2.0/2.1 for an uncalibrated transponder.

Workaround:Use a calibrated transponder.

CSCdz85458

Symptom: When the 10-GE trunk (waveethernetphy) laser is down due to the FLC (forward laser control action), removing the FLC configuration does not turn back the laser on.

Workaround: None.

Limitations and Restrictions

This section provides limitations and restrictions for Cisco ONS 15540 ESPx hardware and software.

Transponder Modules

This section contains limitiations and restrictions that apply to transponder modules.

When you insert the standby transponder module in a y-cable protected configuration, remove the cable from the transponder module before inserting the transponder module into the shelf. Failure to remove the cable might result in errors that can affect the performance of the active signal received by the client equipment.

CRC errors occur with 2-Gbps Fibre Channel on single-mode transponders when high input power levels are received from the client laser sources.

Data errors or link-down conditions for 2-Gbps Fibre Channel might occur on single-mode transponders when used with certain client laser sources. Transmitters in some client GBIC and SFP transceiver units might send large overshoots in optical power with signal bit transitions, causing momentary overload conditions on the transponder client side receiver. The average transmitted power level from the GBIC does not violate the overload specification of the transponder client side receiver, so a power meter does not detect the overload.

The workaround is to attenuate the signal from the client equipment to a recommended level of -12 dBm when transmitting 2-Gbps Fibre Channel services.

If both processor cards are removed, traffic through the system is affected as follows:

For Type 2 extended range transponder modules, traffic is shut down.

For 10-GE transponder modules, traffic is shut down.

Type 1 SM transponder modules and MM transponder modules do not operate reliably. The traffic might be affected.

In the shutdown state, the Status LED on the line card motherboard turns orange.


Note Traffic on pass through optical channels (which passively pass through the mux/demux modules) are not affected by the removal of the processor cards.


Related Documentation

Refer to the following documents for more information about the Cisco ONS 15540 ESPx:

Regulatory Compliance and Safety Information for the Cisco ONS 15500 Series

Cisco ONS 15540 ESPx Planning Guide

Cisco ONS 15540 ESPx Hardware Installation Guide

Cisco ONS 15540 ESPx Optical Transport Turn-Up and Test Guide

Cisco ONS 15540 ESPx Cleaning Procedures for Fiber Optic Connections

Cisco ONS 15540 ESPx Configuration Guide

Cisco ONS 15540 ESPx Command Reference

Cisco ONS 15540 ESPx System Alarms and Error Messages

Cisco ONS 15540 ESPx Troubleshooting Guide

Network Management for the Cisco ONS 15540 ESPx

Cisco ONS 15540 ESPx TL1 Commands

MIB Quick Reference for the Cisco ONS 15500 Series

Cisco ONS 15540 ESPx Software Upgrade Guide

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 web sites 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 monthly and may be more current than printed documentation. The CD-ROM package is available as a single unit or through an annual subscription.

Registered Cisco.com users can order the Documentation CD-ROM (product number DOC-CONDOCCD=) through the online Subscription Store:

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

Ordering Documentation

You can find instructions for ordering 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

Registered Cisco.com users can order the Documentation CD-ROM (Customer Order Number DOC-CONDOCCD=) 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 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 your comments by mail by using the response card 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://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 levels of support are available: the Cisco TAC website and the Cisco TAC Escalation Center. The avenue 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.

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 workaround 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 workaround is available.

Cisco TAC Website

You can use the Cisco TAC website 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 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/en/US/support/index.html

If you have Internet access, we recommend that you open P3 and P4 cases through the Cisco TAC website so that you can describe the situation in your own words 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 level of 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 monthly periodical that provides industry professionals with the latest information about the field of networking. You can access Packet magazine at this URL:

http://www.cisco.com/en/US/about/ac123/ac114/about_cisco_packet_magazine.html

iQ Magazine is the Cisco monthly periodical that provides business leaders and decision makers with the latest information about the networking industry. You can access iQ Magazine at this URL:

http://business.cisco.com/prod/tree.taf%3fasset_id=44699&public_view=true&kbns=1.html

Internet Protocol Journal is a quarterly journal published by Cisco Systems for engineering professionals involved in the design, development, and operation of 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, with current offerings in network training listed at this URL:

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


hometocprevnextglossaryfeedbacksearchhelp

Posted: Wed Nov 3 16:31:31 PST 2004
All contents are Copyright © 1992--2004 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.