Guest

Cisco MGX 8880 Media Gateways

Release Notes for Cisco Voice Switch Service Module (VXSM), Release 5.3.10

  • Viewing Options

  • PDF (295.3 KB)
  • Feedback
Release Notes for Cisco Voice Switch Service Module (VXSM) Release 5.3.10.201

Table Of Contents

Release Notes for Cisco Voice Switch Service Module (VXSM) Release 5.3.10.201

Table of Contents

About Release 5.3.10.201

Firmware Images

Upgrading from an Earlier VXSM Release

Interrupted Procedure Recovery

VXSM Management Information Base

Service Module Support By Platform

Compatibility

Caveats for VXSM Release 5.3.10.201

Open Caveats in Release 5.3.10.201

Removed Caveats in Release 5.3.10.201

Resolved Caveats in Release 5.3.10.201

Related Documentation

Obtaining Documentation

Cisco.com

Documentation DVD

Ordering Documentation

Documentation Feedback

Cisco Product Security Overview

Reporting Security Problems in Cisco Products

Obtaining Technical Assistance

Cisco Technical Support Website

Submitting a Service Request

Definitions of Service Request Severity

Obtaining Additional Publications and Information


Release Notes for Cisco Voice Switch Service Module (VXSM) Release 5.3.10.201


These release notes are Part Number OL-11295-01 Rev. B0, April 2007.

The Voice Switch Service Module (VXSM) product is supported by the MGX 8880 Media Gateway and the MGX 8850 Multiservice Switch. Refer to their respective release notes for platform and version level support guidelines.

The VXSM software release notes are supported by the Cisco Voice Switch Services (VXSM) Configuration Guide, Release 5.3 and the Cisco Voice Switch Services (VXSM) Command Reference, Release 5.3, both of which are available on cisco.com.

Table of Contents

About Release 5.3.10.201

Firmware Images

Upgrading from an Earlier VXSM Release

Interrupted Procedure Recovery

VXSM Management Information Base

Service Module Support By Platform

Compatibility

Caveats for VXSM Release 5.3.10.201

Open Caveats in Release 5.3.10.201

Removed Caveats in Release 5.3.10.201

Resolved Caveats in Release 5.3.10.201

Related Documentation

Obtaining Documentation

Obtaining Technical Assistance

About Release 5.3.10.201

Version .201 of Release 5.3.10 is a patch release that does not introduce new features. For information about resolved anomalies in Version .201, see Table 5.

The VXSM Release 5.3.10.201 follows VXSM Release 5.3.00.200.

Firmware Images

For each VXSM card type (OC-3, T1/E1, or T3), two firmware images are available, namely, Non-CALEA and CALEA. At order time, the user must specify whether a Non-CALEA or CALEA image is required.

The Non-CALEA image supports three Media Gateway Call Control (MGC) protocols, namely, H.248, MGCP, and TGCP. However, the image supports only one protocol at a time. The user must choose between the H.248, MGCP, and TGCP versions when the image is first loaded from the PXM using the setrev command.

The CALEA image supports TGCP and MGCP only. The protocol must be explicitly selected when the image is loaded from the PXM using the setrev command.

Upgrading from an Earlier VXSM Release

VXSM can be gracefully upgraded (configuration is preserved) from any VXSM Release 5.2.x.x (or later) so long as the original and the upgraded images are of the same version (for example Non-CALEA, TGCP to Non-CALEA, TGCP). When loading or upgrading a boot or runtime image to a VXSM card, users must observe the following caution.


Warning Many of the commands involved in loading or upgrading boot and runtime images can take several minutes to execute completely. If the user resets or otherwise disturbs the VXSM card during a loading or upgrading process, the card can easily be damaged even to the extent that it must be returned to the factory for repair.

In particular:
Do not reset VXSM or PXM cards manually or through commands such as resetcd or resetsys
Do not save all MGX configurations with commands such as saveallcnfs.
Do not toggle primary/secondary cards through commands such as switchredcd, delred
Do not change the name of software image before or during the upgrade
Do not change any configuration of active primary card during the upgrade

THE REAPPEARANCE OF THE COMMAND PROMPT AFTER A COMMAND IS ENTERED DOES NOT INDICATE THAT THE IMAGE LOAD OR UPGRADE HAS BEEN COMPLETED.

After the execution of the burnboot, clrsmcnf, loadrev, or setrev commands, the user must execute either a dspcds or dsprev command periodically to verify that the state of the VXSM card being loaded or upgraded is either Active, Standby, or Failed.

ONLY WHEN THE CARD IS DISPLAYED TO BE IN ONE OF THESE STATES IS IT SAFE TO GO TO THE NEXT STEP.

If the upgrade procedure is interrupted for reasons outside the control of the user (for example, a power outage), see "Interrupted Procedure Recovery" below for instructions.


Interrupted Procedure Recovery

In the event that a VXSM software upgrade procedure is interrupted (for example, power outage), and both Primary and Secondary are stuck in 'Failed-U' state, perform the following procedure


Step 1 Execute the abortrev command:

abortrev <PrimarySlot> <NewImageRevision>

Step 2 If the primary VXSM becomes "Failed/Active" (out of Failed-U/Active), then execute the resetcd command

resetcd <PrimarySlot> (

Step 3 If the secondary VXSM becomes "Failed/Active" (out of Failed-U/Active), then execute the resetcd command:

resetcd <SecondarySlot>

Step 4 Both primary and secondary VXSM cards should now have their original SW image and original DB


VXSM Management Information Base

The VXSM Management Information Base (MIB) Version 5.3 is available by request through your Cisco VXSM product marketing representative.

Alternatively, users with CCO accounts can access the MIB and VXSM software on-line at:

http://www.cisco.com/kobayashi/sw-center/sw-wan.shtml

The procedure is:


Step 1 Log on to http://www.cisco.com/kobayashi/sw-center/sw-wan.shtml

Step 2 Locate the VXSM platform (either VXSM 8880 or VXSM 8850) and click the down arrow to expand the "Select Release Level" drop down menu.

Step 3 Select the desired MIB release level (for example, Release 5300) to display a list of downloadable files.

Step 4 Click on the desired file (for example, mgx8850-fw-5300.tar).

Step 5 Read the license agreement and, if approved, click Accept.

Step 6 In the Software Download dialog box, click on Download: filename (where filename is the name of the file selected for download). This step starts the download procedure.

Step 7 Follow the normal file download procedure for your computer.

Step 8 When the file has been downloaded, untar or unzip the downloaded file. The MIB file is included in the downloaded file and is listed as a tar file (for example mgx8850rel5300mib.tar).

Step 9 Untar the MIB file to display its contents.


Service Module Support By Platform

Service Module
MGX8880
MGX8850
PXM45/C
PXM1
PXM45/A
PXM45/B
PXM45/C
PXM1E

MGX-RPM-XF-512

Yes

   

Yes

Yes

 

VISM-PR

Yes

Yes

 

Yes

Yes

Yes

AXSM-1-2488/B

Yes

   

Yes

Yes

 

AXSM-16-155/B

Yes

   

Yes

Yes

 

AXSM-4-622/B

Yes

   

Yes

Yes

 

AXSM-16-T3/E3/B

Yes

   

Yes

Yes

 

AXSM-32-T1E1-E

Yes

   

Yes

Yes

 

MGX-VXSM-155

Yes

   

Yes

Yes

 

MGX-VXSM-T1E1

Yes

   

Yes

Yes

 

MGX-VXSM-T3

Yes

   

Yes

Yes

 

MPSM-T3E3-155

     

Yes

Yes

Yes

RCON-1TO5-8850

Yes

         

Compatibility


Note VXSM Release 5.3.10.201 is supported only with PXM-45.


VXSM software interoperability with the MGX 8880 Media Gateway or the Cisco MGX 8850 (PXM45) Multiservice Switch platform software is listed in Table 1.

Table 1 VXSM Software Interoperability 

Product
Latest Firmware
Min. Firmware

PXM45

5.3.10.201

5.3.10.201

MGX-RPM-XF-512

12.4(6)T1

12.4(6)T1

CWM

15.1.50P1

15.1.50P1

CTM

7.0

7.0

VISM-PR

3.3.25

3.3.25

AXSM-1-2488/B

5.3.10.200

5.3.10.200

AXSM-16-155/B

5.3.10.200

5.3.10.200

AXSM-4-622/B

5.3.10.200

5.3.10.200

AXSM-16-T3/E3/B

5.3.10.200

5.3.10.200

AXSM-32-T1E1-E

5.3.10.200

5.3.10.200

AXSM-XG OC3

5.3.10.200

5.3.10.200

MPSM-T3E3-155

5.3.10.200

5.3.10.200

BTS

4.5

4.5

PGW

9.5.2

9.5.2

Cisco 2600 Series Routers

c2600-ipvoice-mz.123-9.13.T

c2600-ipvoice-mz.123-9.13.T

Cisco 2600 for use as an

IP Transfer Point

c2600-itp-mz.122-21.SW bin

c2600-itp-mz.122-21.SW bin

Cisco 3700 Series Routers

c3725-ipvoice-mz,123-9.13.T

c3725-ipvoice-mz,123-9.13.T

Cisco ATA 188

3.2.0 for SIP/MGCP/H323

3.2.0 for SIP/MGCP/H323

Linksys PAP2 Phone Adapter

Version 2.0.6 (LS)

Version 2.0.6 (LS)

Linksys RT31 Router

Version 1.27.01

Version 1.27.01

Sipura 2100 ATA

Version 3.2.3

Version 3.2.3


Table 2 describes the software images available for Release 5.3.10.201 for VXSM.

Table 2 Software Images for Release 5.3.10.201 for VXSM 

Board Pair
Latest Boot Code Version
Minimum Boot Code Version
Firmware

MGX-VXSM-155, CALEA

vxsm_005.003.010.201_bt.fw

vxsm_005.003.010.201_bt.fw

vxsm_005.053.010.201.fw

MGX-VXSM-155, Non-CALEA

vxsm_005.003.010.201_bt.fw

vxsm_005.003.010.201_bt.fw

vxsm_005.003.010.201.fw

MGX-VXSM-T1E1, CALEA

vxsm_005.003.010.201_bt.fw

vxsm_005.003.010.201_bt.fw

vxsm_005.053.010.201.fw

MGX-VXSM-T1E1, Non-CALEA

vxsm_005.003.010.201_bt.fw

vxsm_005.003.010.201_bt.fw

vxsm_005.003.010.201.fw

MGX-VXSM-T3, CALEA

vxsm_005.003.010.201_bt.fw

vxsm_005.003.010.201_bt.fw

vxsm_005.053.010.201.fw

MGX-VXSM-T3, Non-CALEA

vxsm_005.003.010.201_bt.fw

vxsm_005.003.010.201_bt.fw

vxsm_005.003.010.201.fw


Caveats for VXSM Release 5.3.10.201

This section describes software caveats for Release 5.3.10.201.

Open Caveats in Release 5.3.10.201

Table 3 describes the open caveats in VXSM Release 5.3.10.201.

Table 3 Open Software Caveats in VXSM Release 5.3.10.201 

DDTS Issue
Description

CSCek72659

Headline: Low priority RUDP session remains In service.

Symptom: In a Backhaul session group, containing two or more RUDP sessions, the lower priority session becomes in service.

Conditions: This may happen when call agent switch over is done or a call agent is restarted.

Workaround: Delete and add the RUDP sessions in the session group on VXSM.

CSCek54023

Headline: DSP exception while running the mix codec calls.

Symptom: Call setup or call modification failure is seen on calls that are affected by this non-fatal error. This error also results in associated PXM logs indicating 'a DSP Channel EXCEPTION'

Conditions: This issue was seen twice in an overnight run with a single codec of G.711. There is no permanent damage at the card level due to this error. The error only affects single calls. Subsequent calls on the same TDM endpoint will be unaffected by the previous occurrence of this error.

Workaround: None.


Removed Caveats in Release 5.3.10.201

Table 4 lists caveats that were listed as open in Release 5.3.10.201 but have been removed because they are unreproducible or otherwise invalid.

Table 4 Removed Software Caveats for VXSM Release 5.3.10.201 

DDTS Issue
Description

CSCek50487

t38 call doesn't downspeed if midcall mdcx is sent

CSCek33012

VQM RFC 3611 Dup pkts (1 in 100) cause incorrect loss rate 99.6%

CSCek40572

Fax upspeed fails after modifying H248 call to a new codec

CSCek53995

db missing dsp info after upgrade from 2.5 to 2.5mr


Resolved Caveats in Release 5.3.10.201

Table 5 describes the caveats that are resolved in VXSM Release 5.3.10.201.

Table 5 Resolved Software Caveats in VXSM Release 5.3.10.201 

DDTS Issue
Description

CSCek70797

Fax fails on T.38 devices when call starts at G729

CSCek71988

Offline diagnostics of DSP fails

CSCek70797

Fax fails on T.38 devices when call starts at G729

CSCek70878

VXSM mgcgwdn mismatch results in COT failure

CSCek70228

H.248:Hung RTP terminations due to res dealloc failures in CRML

CSCek70227

H.248:Megaco PPC task suspended when stuck in a for loop.

CSCek70118

VXSM H.248 returns Pending transactions

CSCek70226

H.248:Out of resource error due to CDB leak.

CSCek70116

VXSM sends incorrect H.248 error code 500 when no termiation matches

CSCek67800

H248:Restart SC shud be sent on redirection before registration

CSCsh15755

SS7 trunks stay at TERM_ACTIVE_IDLE after TGCP OC3 VXSM cnfgwoos

CSCek69459

MGCP T.38:Upspeed fails when remote port changes during T.38 switch

CSCek68407

cant cnfgwdn or adddnsdn after upgrade to 5.3(10.200)

CSCek60744

Calls not cleared in MG while H248 Midcall Codec Chg call rate test

CSCek68398

H248:CED not re-enabled on 1300Hz detection (during V.90 ups)

CSCek68160

DSP Knob cnfdsp -ec does not work

CSCek68159

Default PLC config does not take effect during call-setup

CSCek54391

cnfvifparam NonLinearProcess 2 disable does not work

CSCuk61637

VXSM stays in service after an Unauthorized message from CA

CSCek65372

VXSM OC-3 TGCP could not handle RQNT with cot

CSCek63961

T.38 with fallback to G.711

CSCek66095

Modify command failure from CRML is returned as success to MGC.

CSCuk61635

VXSM replies with Internal Gw error to a Modify in a T38 call

CSCek65910

Standby Card resets frequently

CSCek65479

VXSM failure in response to resource allocation request

CSCek64573

VXSM cli stops working after adding 1st session grp when 2nd exists

CSCek64524

VXSM gives err-442 when Term-desc is not at first pos in Media desc

CSCek65232

Cisco MGX did not recover from call server sequential restart

CSCek63961

T.38 with fallback to G.711

CSCek62444

SDP Attribute X- Parsing

CSCek56163

Toolkit Crash during Mem Free

CSCek60782

SDP Parameters String Copy Corrections

CSCek61398

VXSM crashes when SDP contains long strings

CSCek60782

SDP Parameters String Copy Corrections

CSCek61398

VXSM crashes when SDP contains long strings

CSCek60782

SDP Parameters String Copy Corrections

CSCek59917

Toolkit Memory Corruption with SDP Parameters > 10 bytes

CSCek61396

VXSM Crashes with audit on RTP in Null Context

CSCek61259

Double free in tVsi slave

CSCek60782

SDP Parameters String Copy Corrections

CSCek60784

Remove 435 Error Code

CSCek59071

Progress Tone modification for German Ring back tone cadence.

CSCek57817

VXSM rejected call with 400 msg (due to resource leak from hairpin?)

CSCek58493

Compare strings failed because of null string pointers

CSCek55569

Standby card recreate failed by NULL ldibptr

CSCek58229

154 bytes of a-X-cluster causes PPC exception

CSCei56675

Need to interop with linksys ATAs using odd RTP port numbers

CSCek57550

cnfgwoos failed to clean up dangling call legs

CSCek54040

Mix codec calls with COT enabled on BTS caused vxsm VTSP crash

CSCek56325

VXSM should ignore unsupported codec

CSCek57181

increase TM_MM_BUFF_NT_ADDR buffer from 2 to 20 bytes

CSCek52060

dsm debugging logging support

CSCek55130

enhancement to store the MB & dcap exception in BRAM

CSCek52060

dsm debugging logging support

CSCek55130

enhancement to store the MB & dcap exception in BRAM

CSCek53543

Dual PVC failure will not recover if failure threshold is 2

CSCek38528

enable card switch-over if IOS tasks crash

CSCek56341

Need to hung CCB detection task in standby VXSM

CSCek56159

RTP terms left hanging on standby even after deleting the call

CSCek56719

RQNT followed by mid-call codec change and subsequent call fails

CSCek54076

Adding tone-gen on/off response time stats to DSPAPI perf suite

CSCek53969

DSM rejects some DSP responses with no pending requests error

CSCek55602

Mem Leak in MGCP app

CSCek55865

Time duration too long (~48hrs) for audit on NULL context

CSCek54219

Double open in standby VXSM

CSCek52935

VXSM intermittently uses G723 resources instead of specified G711

CSCek54902

CCAPI memory leak when handling disconnect timeout

CSCek54911

Standby card crashes with DSP channel exception

CSCek52788

Inconsistent severity and huge amount of H248 log messages

CSCek54015

Memory leak in DSPAPI buffers on the daughtercard

CSCek52027

semGive error in PXM log

CSCek52788

Inconsistent severity and huge amount of H248 log messages

CSCek27498

After switchover

CSCek52939

Long delay in pipc processing when other cards are reset

CSCek14798

Sub all/double ADD on actv results in stby recreate failure


Table 6 describes the caveats that were opened after Release 5.3.10.200, but are now resolved in VXSM Release 5.3.10.201.

Table 6 Resolved Software Caveats for VXSM Release 5.3.10.201

DDTS Issue
Description

CSCek41878

VXSM returns 500 error for Add command after many TDMHP calls w/ecan

CSCek45680

Long response delay for Subtract command

CSCek46762

NTE payload advertisement needs to have the full fmtp range

CSCek49354

VXSM DS0 in PN state when ADD+AV+AV sent within microsec

CSCek50798

SUB+AV(root)+AV(all) sent to same DS0 within microsec->wrong AV


.

Related Documentation

The following documents contains information that may be useful to software Release 5.3 for VXSM:

Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Hardware Installation Guide, Releases 2 Through 5.3

Cisco ATM Services (AXSM) Configuration Guide and Command Reference for MGX Switches, Release 5.2

Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide Release 4

Cisco MGX 8880 Media Gateway, Release 5.3: A Guide to User Documentation.

Release Notes for Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Switches, Release 5.3.10

Obtaining Documentation

Cisco documentation and additional literature are available on Cisco.com. Cisco also provides several ways to obtain 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 at this URL:

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

You can access the Cisco website at this URL:

http://www.cisco.com

You can access international Cisco websites at this URL:

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

Documentation DVD

Cisco documentation and additional literature are available in a Documentation DVD package, which may have shipped with your product. The Documentation DVD is updated regularly and may be more current than printed documentation. The Documentation DVD package is available as a single unit.

Registered Cisco.com users (Cisco direct customers) can order a Cisco Documentation DVD (product number DOC-DOCDVD=) from the Ordering tool or Cisco Marketplace.

Cisco Ordering tool:

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

Cisco Marketplace:

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

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 Ordering tool:

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

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

Documentation Feedback

You can send comments about technical documentation 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.

Cisco Product Security Overview

Cisco provides a free online Security Vulnerability Policy portal at this URL:

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

From this site, you can perform these tasks:

Report security vulnerabilities in Cisco products.

Obtain assistance with security incidents that involve Cisco products.

Register to receive security information from Cisco.

A current list of security advisories and notices for Cisco products is available at this URL:

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

If you prefer to see advisories and notices as they are updated in real time, you can access a Product Security Incident Response Team Really Simple Syndication (PSIRT RSS) feed from this URL:

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

Reporting Security Problems in Cisco Products

Cisco is committed to delivering secure products. We test our products internally before we release them, and we strive to correct all vulnerabilities quickly. If you think that you might have identified a vulnerability in a Cisco product, contact PSIRT:

Emergencies — security-alert@cisco.com

Nonemergencies — psirt@cisco.com


Tip We encourage you to use Pretty Good Privacy (PGP) or a compatible product to encrypt any sensitive information that you send to Cisco. PSIRT can work from encrypted information that is compatible with PGP versions 2.x through 8.x.

Never use a revoked or an expired encryption key. The correct public key to use in your correspondence with PSIRT is the one that has the most recent creation date in this public key server list:

http://pgp.mit.edu:11371/pks/lookup?search=psirt%40cisco.com&op=index&exact=on


In an emergency, you can also reach PSIRT by telephone:

1 877 228-7302

1 408 525-6532

Obtaining Technical Assistance

For all customers, partners, resellers, and distributors who hold valid Cisco service contracts, Cisco Technical Support provides 24-hour-a-day, award-winning technical assistance. The Cisco Technical Support Website on Cisco.com features extensive online support resources. In addition, Cisco Technical Assistance Center (TAC) engineers provide telephone support. If you do not hold a valid Cisco service contract, contact your reseller.

Cisco Technical Support Website

The Cisco Technical Support Website provides online documents and tools for troubleshooting and resolving technical issues with Cisco products and technologies. The website is available 24 hours a day, 365 days a year, at this URL:

http://www.cisco.com/techsupport

Access to all tools on the Cisco Technical Support Website requires a Cisco.com user ID and password. If you have a valid service contract but do not have a user ID or password, you can register at this URL:

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


Note Use the Cisco Product Identification (CPI) tool to locate your product serial number before submitting a web or phone request for service. You can access the CPI tool from the Cisco Technical Support Website by clicking the Tools & Resources link under Documentation & Tools. Choose Cisco Product Identification Tool from the Alphabetical Index drop-down list, or click the Cisco Product Identification Tool link under Alerts & RMAs. The CPI tool offers three search options: by product ID or model name; by tree view; or for certain products, by copying and pasting show command output. Search results show an illustration of your product with the serial number label location highlighted. Locate the serial number label on your product and record the information before placing a service call.


Submitting a Service Request

Using the online TAC Service Request Tool is the fastest way to open S3 and S4 service requests. (S3 and S4 service requests are those in which your network is minimally impaired or for which you require product information.) After you describe your situation, the TAC Service Request Tool provides recommended solutions. If your issue is not resolved using the recommended resources, your service request is assigned to a Cisco TAC engineer. The TAC Service Request Tool is located at this URL:

http://www.cisco.com/techsupport/servicerequest

For S1 or S2 service requests or if you do not have Internet access, contact the Cisco TAC by telephone. (S1 or S2 service requests are those in which your production network is down or severely degraded.) Cisco TAC engineers are assigned immediately to S1 and S2 service requests to help keep your business operations running smoothly.

To open a service request by telephone, use one of the following numbers:

Asia-Pacific: +61 2 8446 7411 (Australia: 1 800 805 227)
EMEA: +32 2 704 55 55
USA: 1 800 553-2447

For a complete list of Cisco TAC contacts, go to this URL:

http://www.cisco.com/techsupport/contacts

Definitions of Service Request Severity

To ensure that all service requests are reported in a standard format, Cisco has established severity definitions.

Severity 1 (S1)—Your 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.

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

Severity 3 (S3)—Operational performance of your network is impaired, but most business operations remain functional. You and Cisco will commit resources during normal business hours to restore service to satisfactory levels.

Severity 4 (S4)—You require information or assistance with Cisco product capabilities, installation, or configuration. There is little or no effect on your business operations.

Obtaining Additional Publications and Information

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

Cisco Marketplace provides a variety of Cisco books, reference guides, and logo merchandise. Visit Cisco Marketplace, the company store, at this URL:

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

Cisco Press publishes a wide range of general networking, training and certification titles. Both new and experienced users will benefit from these publications. For current Cisco Press titles and other information, go to Cisco Press at this URL:

http://www.ciscopress.com

Packet magazine is the Cisco Systems technical user magazine for maximizing Internet and networking investments. Each quarter, Packet delivers coverage of the latest industry trends, technology breakthroughs, and Cisco products and solutions, as well as network deployment and troubleshooting tips, configuration examples, customer case studies, certification and training information, and links to scores of in-depth online resources. You can access Packet magazine at this URL:

http://www.cisco.com/packet

iQ Magazine is the quarterly publication from Cisco Systems designed to help growing companies learn how they can use technology to increase revenue, streamline their business, and expand services. The publication identifies the challenges facing these companies and the technologies to help solve them, using real-world case studies and business strategies to help readers make sound technology investment decisions. 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/ipj

World-class networking training is available from Cisco. You can view current offerings at this URL:

http://www.cisco.com/en/US/learning/index.html