Table Of Contents
Release Notes for Cisco Voice Interworking Service Module Release 3.1.3
These release notes are part number OL-4801-01 Rev B0, October 10, 2003.
The Voice Interworking Service Module (VISM) product is supported by MGX Voice Media Gateways. Refer to these release notes for Media Gateway and version level support guidelines.
About Release 3.1.3
The VISM 3.1.3 Release is a patch release of the VISM 3.1.2 Release and contains the following features:
For information on the caveats that are resolved in this release, see the "Resolved Caveats for Release 3.1.3" section.
Note If you have a VISM-E1 card with G.711 or Clear Channel codecs in template 2, and you have added more than 240 endpoints per card, see the "Open Caveat in Release 3.1.3" section for the workaround options.
About Release 3.1(2)
The VISM 3.1(2) Release is a maintenance release of the VISM 3.1 Release and contains no new features. This release is a general availability (GA) firmware release for VISM/VISM-PR. See the "Resolved Caveats in Release 3.1(2)" section for information on the caveat resolutions introduced with this release.
Note The content of VISM Release 3.1(2) supersedes Release 3.1(1) and all previous releases.
The software Release 3.1(2) for VISM/VISM-PR is supported by the Cisco VISM Installation and Configuration Guide, which is available on the Web at the following locations:
These release notes contain the following sections:
Features Introduced in Previous Releases of VISM Software
You can access lists of features and descriptions of features contained in previous releases of VISM software at the following location:
Alarm Suppression Feature in Release 3.1.3
The purpose of this feature is to prevent the CPE from dropping calls when a network link failure is temporary.
If the endpoint is in AAL2 trunking mode, the VISM/VISM-PR propagates network alarms to the T1/E1 line that is associated with the network link. The CPE equipment (PBX) receives this alarm and drops the calls.
VISM/VISM-PR processes several alarms. However, for this feature, only the following alarms are suppressed:
•OAM Alarm Indication Signal (AIS)
•OAM Far End Receive Failure (FERF)
•OAM Remote Defect Indication (RDI)
In this release only, these alarms do not propagate onto the T1/E1 lines as line alarms, which cause call drops.
Since this alarm suppression causes network link failures to be ignored, the OAM end-to-end loopback monitoring function must be configured to detect permanent network failures.
Configure AIS Suppression
By default, AIS suppression is disabled. VISM/VISM-PR cards on both ends of the AAL2 trunk need to be loaded with firmware that supports and enables AIS suppression.
To enable AIS suppression, complete the following steps.
Note You can only enable or disable AIS suppression in the AAL2 trunking mode. The other modes do not support this function.
Step 1 Ensure that the VISM/VISM-PR card is in AAL2 trunking mode.cvgmgx1a.1.12.VISM8.a > cnfvismmode 2WARNING: Available CLI Commands will be changed, do you want to proceed (Yes/No)? yesINFORMATION: The new 'aal2Trunking' mode has 182 CLI commands.
Step 2 To enable AIS suppression, use the cnfaissuppression command.mgx.1.12.VISM8.a > cnfaissuppression <enableFlag>
Replace <enableFlag> with 1 to enable AIS suppression.mgx.1.12.VISM8.a > cnfaissuppression 1INFORMATION: Successfully Enabled AIS Suppression.
If you attempt to enable AIS suppression when it is already enabled, the following message displays:WARNING: AIS Suppression is already enabled.
Step 3 To show that AIS suppression has been enabled, use the dspaissuppression command.mgx.1.12.VISM8.a > dspaissuppressionAIS Suppression : ENABLED
Step 4 To disable AIS suppression, use the cnfaissuppression command with the value of 2.mgx.1.12.VISM8.a > cnfaissuppression 2INFORMATION: Successfully Disabled AIS Suppression.
Configure OAM Loop Count
Since an OAM end-to-end loopback failure can still cause line alarms, you must configure the OAM loop count to be longer than the expected duration of the temporary network outage due to a reroute.
Note The OAM end-to-end loopback functionality has not been changed.
Step 1 Ensure that the VISM/VISM-PR is in AAL2 trunking mode.mgx.1.12.VISM8.a > cnfvismmode <2>
Step 2 To check the OAM loop count, enter the dspoamloopcnt command.mgx.1.12.VISM8.a > dspoamloopcnt
The loop count is displayed with the default value of 5 seconds.OAM Loopback Cell Timeout Count: 5
Step 3 To configure the OAM loop count, enter the cnfoamloopcnt command.mgx.1.12.VISM8.a > cnfoamloopcnt <count>
Replace <count> with the number of seconds in the range 5 to 60.
With this feature, VISM/VISM-PR discovers network outages via OAM end-to-end loopback failures. Lost OAM loopback cells can be monitored by using the following command:
The following example shows the output:mgx.1.12.VISM8.a > dspconcnt 131ChanNum: 131Chan State: alarmChan XMT ATM State: Sending FERF OAMChan RCV ATM State: Receiving AIS OAMChan Status Bit Map: 0x2OAM Lpb Lost Cells: 20AAL2 HEC Errors: 2AAL2 CRC Errors: 0AAL2 Invalid OSF Cells: 1AAL2 Invalid Parity Cells: 0AAL2 CPS Packet Xmt: 118467937AAL2 CPS Packet Rcv: 116227849AAL2 Invalid CID CPS: 0AAL2 Invalid UUI CPS: 0AAL2 Invalid Len. CPS: 0AAL5 Invalid CPI: 0AAL5 oversized SDU PDU: 0AAL5 Invalid Len. PDU: 0AAL5 PDU CRC32 Errors: 0AAL5 Reassembly Timer expired PDU: 0
OAM AIS and FERF cells that are transmitted and received are accounted for via counters. With this feature, an alarm is not generated on the line.
The following examples show alarms after an OC-3 failure. AIS alarm cells are received, and FERF cells are transmitted in response.
•Use the dspsarcnt <LCN> command to show the number of AIS, FERF, OAM end-to-end loopback, and total cells that are received and transmitted.mgx.1.12.VISM8.a > dspsarcnt 131SarShelfNum: 1SarSlotNum: 5SarChanNum: 131Tx Rx--------------- ---------------Total Cells: 406656 333840Total CellsCLP: 0 0Total CellsAIS: 0 13Total CellsFERF: 12 0Total CellsEnd2EndLpBk: 85 69Total CellsSegmentLpBk: 0 0RcvCellsDiscOAM: 0
•Use the dspalm -ds1 <LineNum> command to show the line alarm state with the AIS suppression feature. The LineAlarmState does not show any alarms. With the alarm suppression feature, no alarms are generated on the line in response to the OAM AIS alarm received.mgx.1.12.VISM8.a > dspalm -ds1 1LineNum: 1LineAlarmState: No AlarmsLineStatisticalAlarmState: Alarm(s) On --SEFS24hrAlarmUAS24hrAlarm
Note Once the configured number of OAM end-to-end loopback cells are lost, the dspalm status shows that the lines are in alarm.
Without the AIS suppression feature, the LineAlarmState shows XmtAIS and RcvRAI.mgx.1.12.VISM8.a > dspalm -ds1 1LineNum: 1LineAlarmState: Alarm(s) On --RcvRAIXmtAISLineStatisticalAlarmState: Alarm(s) On --SEFS24hrAlarmUAS15minAlarmUAS24hrAlarm
Alarms not Suppressed
Alarm suppression does not affect the following AAL2 type 3 packet alarms (transmitted and received per CID):
These alarms allow the line alarms that are received due to a T1/E1 failure to be propagated to the remote end.
The default for AIS suppression in Release 3.1.3 is disabled. If you upgrade to Release 3.1.3 from a release with AIS suppression enabled, you must re-enable AIS suppression.
After the upgrade, enable AIS suppression using the cnfaissuppression command.
G.729a Codec with 20 ms
In Release 3.1.3, VISM/VISM-PR cards contain a new custom profile to support G.729a with
20 milliseconds (ms) packetization period.
The new Custom profile type, 210, supports upspeeding from G.729a with 20 ms packetization period to other codecs, for example, G.711 mu/A law.
G.729a with 20 ms packetization period is supported for AAL2 trunking and applies to templates 1, 3, and 4 on the VISM/VISM-PR cards.
The following commands have been modified to support this feature:
To add an AAL2 channel identifier (CID) on a VISM/VISM-PR card, use the addcid command.
addcid <endpt_num> <LCN> <cid_num> <codec_type> <profile_type> <profile_number> <voice_activity_detection> <vad_init_timer> <echo_cancellation> <triple_redundancy_protection> <cas_signaling_transport> <dtmf_tone_transport_as_AAL2> <ICS_enable> <pktPeriod>
This command establishes a relationship between an endpoint and an LCN/CID pair. The endpoint is bound to a DS0, and the CID binds a DS0 to a logical channel—ensuring an endpoint-to-endpoint trunk. The following conditions must be met before you use this command:
•A previously added endpoint must exist.
•PVC must be of bearer type and provisioned using the addcon command.
•The current DSP template must contain the desired codec type.
This command can be used on an endpoint that has no associated CAS variant. However, if a CAS variant is specified for the endpoint, it must be Q.50 variant (file q50.o)—the only CAS variant supported by this command.
The G.723.1 codecs are supported for VISM-PR cards and are not supported for VISM cards.
The following example creates a CID for endpoint 10, LCN 140, with a CID number of 10. The codec type is 4 (G.729a), profile type is 3 (Custom), profile number is 210 (Custom), VAD is 1 (on), VAD holdover is 300 milliseconds, echo cancelling is 1 (on), type 3 redundancy is 1 (on), CAS transport is 1 (on), DTMF transport is 1 (on), idle code suppression is 1 (on) and the packet period is 20 milliseconds.mgx.1.14.VISM8.a > addcid 10 140 10 4 3 210 1 300 1 1 1 1 1 20
To configure a profile preference, use the cnfprofparams command.
cnfprofparams <profileType> <profileNumber> <profilePreference>
Switched AAL2 PVC and AAL2 trunking
Follow standard CLI procedures for this command.
The following example shows that the Custom profile type, profile number 210, is configured with the midrange preference level of 4:mgx.1.14.VISM8.a > cnfprofparams 3 210 4
To configure the profile voice element, use the cnfprofelemvoice command.
cnfprofelemvoice <profileType> <profileNumber> <voice_codec_type> <pktPeriod > <sid>
Switched AAL2 PVC and AAL2 trunking
Use the dspaal2profile command to identify the valid combinations of codec type, packetization period, and SID.
The G.723.1 codecs are supported for VISM-PR cards and are not supported for VISM cards.
The following example shows that the Custom profile type, profile number 210, is configured with the G.729a codec type (4), a packetization period of 20 ms, and VAD enabled:mgx.1.14.VISM8.a > cnfprofelemvoice 3 210 4 20 2
To display the profile elements and the preference for all profiles, use the dspprofparams command.
This command has no arguments or keywords.
Switched AAL2 PVC and AAL2 trunking
When you execute this command, the display includes the default voice and voiceband data profile element which correspond to each supported profile.
The following example shows the profile elements and preferences for all profiles, including the results of the cnfprofparams and cnfprofelemvoice commands.mgx.1.14.VISM8.a > dspprofparams- - - - - - - - - - - - - - - - - - - - - -Profile Type : ITUProfile Number : 1Profile Preference : 4Voice Profile Codec : G.711uVoice Profile Packetization-period(ms): fiveVoice Profile SID : VAD onVBD Profile Codec : G.711uVBD Profile Packetization-period (ms) : five- - - - - - - - - - - - - - - - - - - - - -Profile Type : ITUProfile Number : 2Profile Preference : 3Voice Profile Codec : G.711uVoice Profile Packetization-period(ms): fiveVoice Profile SID : sidGenricVBD Profile Codec : G.711uVBD Profile Packetization-period (ms) : fiveType <CR> to continue, Q<CR> to stop:- - - - - - - - - - - - - - - - - - - - - -Profile Type : ITUProfile Number : 3Profile Preference : 1Voice Profile Codec : G.726-32KVoice Profile Packetization-period(ms): fiveVoice Profile SID : sidGenricVBD Profile Codec : G.711uVBD Profile Packetization-period (ms) : five- - - - - - - - - - - - - - - - - - - - - -Profile Type : ITUProfile Number : 7Profile Preference : 2Voice Profile Codec : G.729abVoice Profile Packetization-period(ms): tenVoice Profile SID : sid729VBD Profile Codec : G.711uVBD Profile Packetization-period (ms) : fiveType <CR> to continue, Q<CR> to stop:- - - - - - - - - - - - - - - - - - - - - -Profile Type : ITUProfile Number : 8Profile Preference : 5Voice Profile Codec : G.729abVoice Profile Packetization-period(ms): tenVoice Profile SID : sid729VBD Profile Codec : G.711uVBD Profile Packetization-period (ms) : five- - - - - - - - - - - - - - - - - - - - - -Profile Type : ITUProfile Number : 12Profile Preference : 10Voice Profile Codec : G.723.1a-HVoice Profile Packetization-period(ms): thirtyVoice Profile SID : sid723VBD Profile Codec : G.723.1-HVBD Profile Packetization-period (ms) : thirtyType <CR> to continue, Q<CR> to stop:- - - - - - - - - - - - - - - - - - - - - -Profile Type : CustomProfile Number : 100Profile Preference : 6Voice Profile Codec : G.726-32KVoice Profile Packetization-period(ms): tenVoice Profile SID : sidGenricVBD Profile Codec : G.711uVBD Profile Packetization-period (ms) : five- - - - - - - - - - - - - - - - - - - - - -Profile Type : CustomProfile Number : 101Profile Preference : 7Voice Profile Codec : G.729abVoice Profile Packetization-period(ms): tenVoice Profile SID : sid729VBD Profile Codec : G.711uVBD Profile Packetization-period (ms) : fiveType <CR> to continue, Q<CR> to stop:- - - - - - - - - - - - - - - - - - - - - -Profile Type : CustomProfile Number : 110Profile Preference : 8Voice Profile Codec : G.729abVoice Profile Packetization-period(ms): thirtyVoice Profile SID : sid729VBD Profile Codec : G.711uVBD Profile Packetization-period (ms) : five- - - - - - - - - - - - - - - - - - - - - -Profile Type : CustomProfile Number : 200Profile Preference : 9Voice Profile Codec : clr chanVoice Profile Packetization-period(ms): fiveVoice Profile SID : VAD offVBD Profile Codec : clr chanVBD Profile Packetization-period (ms) : fiveType <CR> to continue, Q<CR> to stop:- - - - - - - - - - - - - - - - - - - - - -Profile Type : CustomProfile Number : 210Profile Preference : 4Voice Profile Codec : G.729aVoice Profile Packetization-period(ms): twentyVoice Profile SID : VAD offVBD Profile Codec : G.711uVBD Profile Packetization-period (ms) : five
To display data about a specified AAL2 profile type and profile number, use the dspaal2profile command.
dspaal2profile <profileType> <profileNumber>
The AAL2 profiles correspond to the profile types ITU and ATMF as defined in the ITU-T I.366.2 and ATM forum AF-VTOA-0113 standards respectively.
The following example shows that the data for AAL2 profile type 3 and profile number 210 is displayed:mgx.1.14.VISM8.a > dspaal2profile 3 210UUI Packet Packet Seq. No.Codepoint Length Time IntervalRange (octets) Codec SID M (ms) (ms)0-7 40 PCMU No SID 1 5 50-7 40 PCMA No SID 1 5 58-15 40 G726-32 No SID 2 10 58-15 20 G729ab SID729 2 20 58-15 20 G729a No SID 2 20 5
E1 CAS Idle Code
In Release 3.1.3 when VISM/VISM-PR is configured for E1 channel associated signaling (CAS) transport in AAL2 trunking mode, the default idle signaling pattern is 13.
Configure the Idle Code
You can change the default idle ABCD CAS code on endpoint basis on the VISM/VISM-PR E1 cards. ABCD refers to the robbed-bit signaling bits that are sent in CAS lines.
Step 1 Log in to your VISM/VISM-PR card.
Step 2 Ensure that you are in the AAL2 trunking mode.
Step 3 To configure the idle CAS code as 4, enter the cnfcascode command.
Note The cnfcascode command can be used only on existing endpoints.
mgx.1.14.VISM8.a > cnfcascode <endpt_num> <idle_code> <seized_code> [endpts_num]
Replace the arguments with the values listed in the next table.
The following example shows the idle CAS code as 4 on endpoints 1-6. Seized code is not used for AAL2 trunking.mgx.1.14.VISM8.a > cnfcascode 1 4 6 5NOTE:In order for VISM card to use the new Idle Code :Either Reset the Card OR re-add the Cids
Step 4 To show the configured idle code on endpoint 1, enter the dspds0cascode command.mgx.1.14.VISM8.a > dspds0cascode <line_number> <ds0_number>
Replace the line_number argument with a value 1-8 and ds0_number with a value 1-24 for T1 lines or 1-31 for E1 lines.
The following example show the idle CAS code on endpoint 1 that you configured in Step 3.mgx.1.14.VISM8.a > dspds0cascode 1 1Ds1 line number: 1ds0 number: 1Ds0 If Index: 1Ds0 Idle Code : 4Ds0 Seized Code: 6
Step 5 To view the status of all the DS0s on a line, enter the dsplndsx0s command.mgx.1.14.VISM8.a > dsplndsx0s <line_number>
The following example shows the idle code you configured using the cnfcascode command on line 2.mgx.1.14.VISM8.a > dsplndsx0s 1Ds0 If Robbed Bit Idle Seized EndPt If Variant Cadence CadenceIndex Signaling Code Code Num Type Name OnTime OffTime------ ---------- ----- ------- ------ -------------- --------- -------- --------1 False 4 6 1 bearer 75 752 False 4 6 2 bearer 75 753 False 4 6 3 bearer 75 754 False 4 6 4 bearer 75 755 False 4 6 5 bearer 75 756 False 4 6 6 bearer 75 757 False 2 4 7 bearer 75 758 False 2 4 8 bearer 75 759 False 2 4 9 bearer 75 7510 False 2 4 10 bearer 75 7511 False 13 15 -1 - 75 7512 False 13 15 -1 - 75 7513 False 13 15 -1 - 75 7514 False 13 15 -1 - 75 7515 False 13 15 -1 - 75 7516 False 13 15 -1 - 75 7517 False 13 15 -1 - 75 7518 False 13 15 -1 - 75 7519 False 13 15 -1 - 75 7520 False 13 15 -1 - 75 7521 False 13 15 -1 - 75 7522 False 13 15 -1 - 75 7523 False 13 15 -1 - 75 7524 False 13 15 -1 - 75 7525 False 13 15 -1 - 75 7526 False 13 15 -1 - 75 7527 False 13 15 -1 - 75 7528 False 13 15 -1 - 75 7529 False 13 15 -1 - 75 7530 False 13 15 -1 - 75 7531 False 13 15 -1 - 75 75
Step 6 To update the new CAS code on previously existing endpoints, reset the VISM/VISM-PR card.
CAS Code Sent When Adding a CID
If the local end CID is added first, the VISM/VISM-PR continues to provide the configured idle code on the DS0 (TDM interface) until the remote AAL2 CID is added and starts sending the CAS signaling traffic over the ATM network.
If the local end CID is added after the remote end CID is added, the VISM/VISM-PR is already receiving a CAS signaling pattern from the remote AAL2 CID. The VISM/VISM-PR begins propagating the received signaling code on the line side (TDM interface).
Note It is assumed the AAL2 CIDs that are added have CAS transport enabled on them. If CAS transport is disabled, the CAS signaling bits do not propagate end-to-end.
CAS Code Sent When Deleting a CID
If the remote end AAL2 CID is deleted first, the VISM/VISM-PR continues to send the last received CAS signaling pattern from the remote CID to the line side (TDM interface).
If the local end CID is deleted first, the VISM/VISM-PR sends the idle code (configured on this endpoint) to the line side (TDM interface).
Before upgrading from 3.1.x to 3.1.3, configure the CAS code on the endpoints on the previous release. This step ensures that the configured idle code is carried over to the upgraded VISM/VISM-PR and used on all the endpoints.
If you install a new VISM/VISM-PR card with Release 3.1.3, and you want to configure a new CAS code on some endpoints, the new idle code is used on the CIDs which are added after configuring the CAS code.
Elements of Release 3.1.3
Note VISM/VISM-PR Release 3.1.3 supports the same elements as 3.1(2).
This section describes the following elements of software Release 3.1.3 for VISM/VISM-PR:
VISM Management Information Base
The VISM Management Information Base (MIB) Version 0.0.30 is available by request through your Cisco VISM product marketing representative.
Table 2 provides the support level for 1:N Service Module Redundancy (N = 1 through 11).
Note You can use a VISM-PR card as a redundant card for a VISM card, but a VISM card cannot be used as a redundant card for a VISM-PR card.
There is support for Bulk Distribution using the SRM-3T3 and SRM-E (OC3) cards.
VISM Call Rate
Software Release 3.1.3 for VISM/VISM-PR handles 10 CAS, SS7, or PRI calls per second per VISM card.
VISM software interoperability with Cisco MGX 8830, Cisco MGX 8850 PXM1E-based, Cisco MGX 8850 PXM1-based, Cisco MGX 8850 PXM45-based, Cisco MGX 8250, and Cisco MGX 8230 platform software is listed in Table 3.
VISM software interoperability with other Cisco products is described in Table 4.
Table 4 Software Release 3.1.3 for VISM/VISM-PR Interoperability with Other Cisco Products
Table 5 describes the software images available for Release 3.1.3 for VISM/VISM-PR.
Table 5 Software Images for Release 3.1.3 for VISM/VISM-PR
Product Name Software Image Firmware Description
This image does not support the CALEA1 feature.
Use this image for CALEA1 feature support.
1 CALEA = Commission on Accreditation for Law Enforcement Agencies.
2 The CALEA implementation supports the CALEA law intercept confirmation interface.S
Table 6 describes the software boot code and run-time firmware requirements for software Release 3.1.3 for VISM/VISM-PR.
Note Loading this release of the backup bootcode is required for existing VISM cards not using this new release.
Limitations and Restrictions
Note Release 3.1.3 does not contain any new limitations or restrictions. The same limitations and restrictions in 3.1(2) apply to this release.
The following limitations and restrictions are valid for software Release 3.1.3 for VISM/VISM-PR:
•Software Release 3.1.3 for VISM/VISM-PR requires you to use 64 Mb VISM cards or VISM-PR cards exclusively.
•Cisco recommends that you use the cnfcodecjtrdelay command to configure the jitter-delay argument to 20 ms when using DSP firmware versions 3.4 and 3.6.
•In a PNNI network, upspeeding SVC fax or modem calls requires an increase in bandwidth between the voice codec and the vbd codec. For fax calls to go through, you must disable policing.
•For improved voice quality, Cisco recommends that you use G.729a codec instead of the G.729ab codec. If VAD is required, use the generic VAD algorithm.
Installation and Upgrade Procedures
This section describes the following installation and upgrade procedures:
VISM/VISM-PR Release 3.1.3 provides a graceful upgrade procedure for the following releases:
•From VISM 1.5 to VISM 3.1.3
•From VISM 2.1 to VISM 3.1.3
•From VISM 2.2 to VISM 3.1.3
•From VISM 3.0 to VISM 3.1.3
•From VISM 3.1(0) to VISM 3.1.3
•From VISM 3.1(1) to VISM 3.1.3
•From VISM 3.1(2) to VISM 3.1.3
Software Release 3.1.3 for VISM/VISM-PR provides a procedure for the graceful upgrade (one in which the existing VISM configuration is preserved throughout the upgrade procedure) from an earlier release.
Caution Installing VISM software updates from VISM Release 2.2 with CALEA to VISM Release 3.1.3 without CALEA is not graceful.
To ensure that the VISM/VISM-PR configuration is preserved throughout the upgrade procedure, you must complete the prerequisites listed in this section.
Before starting the graceful upgrade procedure, complete the following prerequisites:
•Configure your MGX 8000 Series shelf with at least two VISM cards in a redundant configuration.
For more information on adding redundancy, refer to the add redundancy, addred, command in the Cisco MGX 8250, Cisco MGX 8230, and Cisco MGX 8850 PXM1-based Command Reference documentation and the Cisco MGX 8830 and MGX 8850 PXM1E/ PXM45-based Command Reference documentation.
•Ensure that the VISM/VISM-PR cards are running at least Release 2.0.
•Download software Release 3.1.3 for VISM/VISM-PR to the MGX 8000 Series shelf.
•If you are using the CALEA feature, ensure that you have the version of VISM/VISM-PR software that supports CALEA.
VISM/VISM-PR Upgrades with PXM1
This section describes the procedures for upgrading VISM/VISM-PR software when the VISM/VISM-PR is used with a PXM1 card.
Download VISM/VISM-PR Boot Code and Firmware to PXM1
To download the VISM/VISM-PR boot code and firmware to the PXM1 card, use TFTP.
Step 1 Log in to your TFTP server.
Step 2 Download the bootcode and firmware images from the Cisco website.
Step 3 Download the selected revision of service module boot code into the service module.
a. tftp <node_name or IP address>
c. put <backup boot> POPEYE@SM_1_0.BT
Step 4 Download the selected firmware file.
a. tftp <node_name or IP address>
c. put <FW file> POPEYE@SM_1_0.FW
d. put <FW file> POPEYE@SM_1_<slot number of card to upgrade>.FW
Note Do not enter two put commands in the same TFTP session.
Step 5 Proceed to the "Upgrade VISM/VISM-PR Firmware with PXM1 Card" section to install the download.
Upgrade VISM/VISM-PR Firmware with PXM1 Card
Software Release 3.1.3 is for VISM and VISM-PR cards. Ensure that the VISM and VISM-PR cards have the minimum boot code version of vism_8t1e1_BT_3.1.00.fw.
The following versions of VISM software Release 3.1.3 are available:
In this procedure the following conditions apply:
•If two VISM or VISM-PR cards are part of a redundancy group, initially the primary card is in the active state, and the secondary card is in the standby state.
•Old-rev refers to the firmware, Release 3.1(2) and prior.
•New-rev refers to the firmware after the upgrade, Release 3.1.3.
Perform the firmware upgrade on the VISM or VISM-PR cards. Do not remove the VISM cards and replace them with VISM-PR cards at this time.
Step 1 Log in to the active PXM1 card (slot 7 or 8).
Step 2 Save the existing configuration as a contingency plan by entering:
savesmcnf <SM slot#>
This command saves the existing configuration in the C:CNF directory. This file can be used during the downgrade procedure, if necessary.
Step 3 Execute the PXM install command:
install sm <SM slot#> <new-rev>
SM slot# is the slot number of the primary VISM or VISM-PR card and new-rev is the file name of the new firmware (for example, vism_8t1e1_300.001.003.000.fw).
This command causes the secondary VISM or VISM-PR card to reset and come up in the standby state, running the new-rev firmware. The primary VISM or VISM-PR card is unaffected by this command.
Step 4 Execute the PXM newrev command:
newrev sm <SM slot#> <new-rev>
SM slot# is the slot number of the primary VISM or VISM-PR card and new-rev is the filename of the new firmware.
This command causes the primary VISM or VISM-PR card to reset and the secondary VISM or VISM-PR card to become active and running the new-rev firmware.
Step 5 Execute the PXM commit command:
commit sm <SM slot#> <new-rev>
SM slot# is the slot number of the primary VISM or VISM-PR card and new-rev is the filename of the new firmware.
The two VISM or VISM-PR cards are now back to their original condition except that both cards are now running the new-rev firmware.
Step 6 Log in to the active VISM or VISM-PR card and use the display commands (for example, dspendpts, dspcasvar, and so forth) to confirm that the configuration has been preserved through the upgrade process.
Note For more than one primary VISM or VISM-PR card in a redundancy group, ensure that the secondary card is in the standby state and repeat Step 4 and Step 5 for each VISM card in the redundancy group.
It is also recommended that you perform the following verifications:
•Make minor modifications to the configuration.
•Check that the changes have been executed correctly.
•Change the configuration back again.
Boot Code Upgrade Procedure with PXM1 Cards
Complete the following steps to upgrade the new backup boot code when you are using PXM1 cards in in a Cisco MGX 8230, Cisco MGX 8250, and Cisco MGX 8850 chassis:
Note This procedure re-programs the VISM boot code for previous VISMs using the VISM runtime image version 1.0 to 2.0.
Step 1 Telnet to MGX shelf and cc to the VISM card.
Note VISM must be in the active state in order to update the VISM boot code.
Step 2 Access the server where the VISM boot code resides and TFTP the VISM boot code to the VISM card:
a. Type tftp <IP address of the MGX shelf>
b. Type bin at the tftp prompt.
Caution Ensure that you perform Step 2 b. If you to not perform Step 2 b. the boot code is corrupted and not recoverable.
c. Type install [bt] [sm <slot>] <version> at the PXM prompt.
Caution Do not touch the VISM card until the status comes back ('Sent xxx bytes in yyy seconds'). Failure to follow this recommendation corrupts the boot code, which cannot be recovered.
When the boot code is being written to PROM, you see comments displayed at the VISM prompt. This behavior is normal and expected.
Step 3 Use the resetcd command for VISM from the PXM card for the latest boot take effect.
Step 4 Type the version command to verify the correct boot code.
Note Step 4 is optional.
VISM-PR Upgrades with PXM1E and PXM45
This section describes the procedures for upgrading VISM-PR software when the VISM-PR is used with a PXM1E or PXM45 card.
Download VISM-PR Boot Code and Firmware to PXM1E and PXM45
To download the VISM-PR boot code and firmware to the PXM1E or PXM45 card, use FTP.
Step 1 Access the image on the Cisco Web site.
Step 2 To download the image, enter the ftp command.
where node-ip is the IP address of the node to which you want to download the image.
Step 3 Enter your username and password.
Step 4 Enter bin.
Step 5 Access the appropriate directory.
Step 6 Download the image to your C:FW directory.
where image-version is the downloaded image from Step 1.
Step 7 To exit the download procedure, enter bye.
Upgrade VISM-PR Firmware with PXM1E and PXM45 Cards
Ensure that the VISM-PR cards have the minimum boot code version of vism_8t1e1_BT_3.1.00.fw.
The following versions of VISM-PR software Release 3.1.3 are available:
Perform the firmware upgrade on the VISM-PR cards.
Step 1 Log in to the active PXM1E or PXM45 card.
Step 2 Ensure that the card is in the redundant mode, where the active card is the primary card.
Step 3 To save the existing configuration as a contingency plan, enter the saveallcnf command.
Step 4 To load the new software, enter the loadrev command.
loadrev sm-primary-slot-num new-rev
where sm-primary-slot-num is the slot number of the VISM-PR card in which you want to install the new software; and new-rev is the new firmware version number for the VISM-PR software.
Caution Temporary traffic loss occurs.
Step 5 To execute the download, enter the runrev command.
runrev sm-primary-slot-num new-rev
Caution Temporary traffic loss occurs.
Step 6 To commit the new download to the VISM-PR card, enter the commitrev command.
commitrev sm-primary-slot-num new-rev
Boot Code Upgrade Procedure with PXM1E and PXM45 Cards
The boot code has not changed from VISM Release 3.1(2) to Release 3.1.3. Therefore, the procedure in this section is the same as the upgrade procedure for Release 3.1(2).
Complete the following steps to upgrade the new backup boot code when you are using PXM1E or PXM45 cards in your MGX 8000 Series chassis:
Step 1 Complete the steps in the VISM-PR Upgrades with PXM1E and PXM45.
Step 2 Log in to the PXM1E or PXM45 card.
Step 3 Use the burnboot sm-primary-slot-num new-rev command, where sm-primary-slot-num is the slot number of the VISM-PR card you want to upgrade and new-rev is the firmware version number of the new VISM software, to upgrade the VISM-PR boot code.
The VISM-PR card automatically resets and becomes active with the latest boot code image. You have completed the boot code upgrade procedure.
VISM/VISM-PR Downgrade Procedure
Use this procedure to downgrade VISM software from software Release 3.1.3 to an earlier VISM release. By following the downgrade procedure described here, the configurations are retained after the downgrade.
Note The configurations that existed with old-rev firmware should have been saved earlier. You cannot downgrade from VISM-PR to VISM.
Complete the following steps to downgrade the VISM software from software Release 3.1.3 for VISM/VISM-PR to Release 3.1, 3.0, 2.2, 2.1, or 2.0:
Step 1 If the VISM card is in a redundancy group, remove the redundancy.
delred <SM slot#>
Step 2 Download the old-rev firmware onto the MGX shelf.
Step 3 Execute the PXM clrsmcnf command:
clrsmcnf <SM slot#>
SM slot# is the slot number of the VISM card to be downgraded.
The VISM card resets on executing this command. Wait for the card to come active.
Step 4 Execute the PXM restoresmcnf command:
restoresmcnf -f <filename> -s <SM slot#>
The filename is the name of the old configuration file that was saved while the old-rev firmware was running. The file can be found in the C:CNF directory on the MGX shelf.
The SM slot# is the slot number of the VISM card to be downgraded.
The VISM card resets again. When the card becomes active, it has the old-rev firmware running with the old configuration.
Step 5 Reconfigure redundancy group, if required.
VISM to VISM-PR Hardware Upgrade
Complete the following steps to upgrade your system from VISM cards to VISM-PR cards.
Caution You must install the redundant (standby) VISM-PR card first. Failure to follow this recommendation results in traffic loss. In addition, do not remove an active VISM card from your chassis. Ensure that you configure an active VISM card to the standby state before you remove it and replace it with a VISM-PR card.
Step 1 Remove the redundant (standby) VISM card from your chassis.
Step 2 Install a VISM-PR card in the slot you removed the VISM card from in Step 1.
Step 3 Administratively configure the VISM-PR card you installed in Step 2 as primary (active).
Step 4 Remove the now redundant VISM card from your chassis.
Step 5 Install a VISM-PR card in the slot you removed the VISM card from in Step 4.
Step 6 Log in to the redundant (secondary) VISM-PR card and execute the dspcd command. Verify that the output from the dspcd command lists the card type under FunctionModuleType as a VISM-PR card. If the card type still indicates the VISM card, execute the resetcd slot-num command from the PXM and repeat the dspcd command to insure that the correct card type is shown.
Step 7 Log in to the active VISM-PR card and execute the dspcd command. Verify that the output from the dspcd command lists the card type under FunctionModuleType as a VISM-PR card. If the card type still indicates the VISM card, execute the resetcd slot-num command from the PXM and repeat the dspcd command to insure that the correct card type is shown.
Step 9 Remove a standby VISM card from your chassis.
Step 10 Install a VISM-PR card in the slot you removed the VISM card from in Step 9.
Caveats for VISM Release 3.1.3
This section describes resolved and open software caveats for Release 3.1.3 of VISM. Caveats describe unexpected behavior or defects in VISM software.
Resolved Caveats for Release 3.1.3
Table 7 describes the caveats that have been resolved in VISM Release 3.1.3.
Open Caveat in Release 3.1.3
Table 8 describes the open caveat in VISM Release 3.1.3.
Caveats for VISM Release 3.1(2)
This section describes resolved and open software caveats for Release 3.1(2) of VISM.
Resolved Caveats in Release 3.1(2)
Table 9 describes the caveats that have been resolved in VISM Release 3.1(2).
Open Caveats in Release 3.1(2)
Table 10 describes the open caveats in VISM Release 3.1(2).
Anomaly Status Changes in Release 3.1(2)
The following table lists anomalies that have changed status since in Release 3.1(2). Changed status means that the anomaly went from open to a state other than resolved. The status field states whether the anomaly is closed, junked, duplicated, or unreproducible.
Caveats Resolved in Release 3.1(1)
Table 11 describes the caveats issued against VISM software that have been resolved in software Release 3.1(1).
The following documents contains information that may be useful to software Release 3.1.3 for VISM/VISM-PR:
•Cisco VISM Installation and Configuration Guide, Release 3.0
•Cisco MGX 8830, MGX 8850 (PXM45 and PXM1E), and MGX 8950 Command Reference, Release 3
•Cisco MGX 8850 (PXM45 and PXM1E) Hardware Installation Guide, Release 3
•Cisco MGX 8850 (PXM45) and MGX 8950 Software Configuration Guide, Release 3
Cisco provides several ways to obtain documentation, technical assistance, and other technical resources. These sections explain how to obtain technical information from Cisco Systems.
You can access the most current Cisco documentation on the World Wide Web at this URL:
You can access the Cisco website at this URL:
International Cisco web sites can be accessed from this URL:
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:
You can find instructions for ordering documentation at this URL:
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:
•Registered Cisco.com users can order the Documentation CD-ROM (Customer Order Number DOC-CONDOCCD=) through the online Subscription Store:
•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).
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 firstname.lastname@example.org.
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:
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 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:
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:
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:
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:
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:
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:
•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:
•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:
•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:
•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:
•Training—Cisco offers world-class networking training, with current offerings in network training listed at this URL:
CCIP, CCSP, the Cisco Arrow logo, the Cisco Powered Network mark, Cisco Unity, Follow Me Browsing, FormShare, and StackWise are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, and iQuick Study are service marks of Cisco Systems, Inc.; and Aironet, ASIST, BPX, Catalyst, CCDA, CCDP, CCIE, CCNA, CCNP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, the Cisco IOS logo, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Empowering the Internet Generation, Enterprise/Solver, EtherChannel, EtherSwitch, Fast Step, GigaStack, Internet Quotient, IOS, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, LightStream, MGX, MICA, the Networkers logo, Networking Academy, Network Registrar, Packet, PIX, Post-Routing, Pre-Routing, RateMUX, Registrar, ScriptShare, SlideCast, SMARTnet, StrataView Plus, Stratm, SwitchProbe, TeleRouter, The Fastest Way to Increase Your Internet Quotient, TransPath, and VCO are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and certain other countries.
All other trademarks mentioned in this document or Web site are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0304R)
Copyright © 2003, Cisco Systems, Inc.
All rights reserved.