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/VISM-PR 3.1(2) Release is a maintenance release of the VISM/VISM-PR 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.

Features in Previous Release 3.1.3

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 > cnfvismmode2

WARNING: Available CLI Commands will be changed, do you want to proceed (Yes/No)? yes

INFORMATION: 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 1

INFORMATION: 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 > dspaissuppression

AIS Suppression : ENABLED

Step 4 To disable AIS suppression, use the cnfaissuppression command with the value of 2.

mgx.1.12.VISM8.a > cnfaissuppression2

INFORMATION: 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.

Display Alarms

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:

dspconcnt <LCN>

The following example shows the output:

mgx.1.12.VISM8.a > dspconcnt 131

ChanNum: 131

Chan State: alarm

Chan XMT ATM State: Sending FERF OAM

Chan RCV ATM State: Receiving AIS OAM

Chan Status Bit Map: 0x2

OAM Lpb Lost Cells: 20

AAL2 HEC Errors: 2

AAL2 CRC Errors: 0

AAL2 Invalid OSF Cells: 1

AAL2 Invalid Parity Cells: 0

AAL2 CPS Packet Xmt: 118467937

AAL2 CPS Packet Rcv: 116227849

AAL2 Invalid CID CPS: 0

AAL2 Invalid UUI CPS: 0

AAL2 Invalid Len. CPS: 0

AAL5 Invalid CPI: 0

AAL5 oversized SDU PDU: 0

AAL5 Invalid Len. PDU: 0

AAL5 PDU CRC32 Errors: 0

AAL5 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 131

SarShelfNum: 1

SarSlotNum: 5

SarChanNum: 131

Tx Rx

--------------- ---------------

Total Cells: 406656 333840

Total CellsCLP: 0 0

Total CellsAIS: 0 13

Total CellsFERF: 12 0

Total CellsEnd2EndLpBk: 85 69

Total CellsSegmentLpBk: 0 0

RcvCellsDiscOAM: 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 1

LineNum: 1

LineAlarmState: No Alarms

LineStatisticalAlarmState: Alarm(s) On --

SEFS24hrAlarm

UAS24hrAlarm

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 1

LineNum: 1

LineAlarmState: Alarm(s) On --

RcvRAI

XmtAIS

LineStatisticalAlarmState: Alarm(s) On --

SEFS24hrAlarm

UAS15minAlarm

UAS24hrAlarm

Alarms not Suppressed

Alarm suppression does not affect the following AAL2 type 3 packet alarms (transmitted and received per CID):

•external AIS

•external RDI

•connection AIS

•connection RDI

These alarms allow the line alarms that are received due to a T1/E1 failure to be propagated to the remote end.

Upgrade Notes

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:

•addcid

•cnfprofparams

•cnfprofelemvoice

•cnfprofelemvbd

•dspprofparams

•dspaal2profile

addcid

To add an AAL2 channel identifier (CID) on a VISM/VISM-PR card, use the addcid command.

(Optional) Value to enable or disable DTMF tone transport as AAL2 type 3 packets. It can be one of the following values:

•1 = On (Default)

•2 = Off

Note The dtmf_tone_transport_as_AAL2 argument value must be set to 1 (on) when the codec_type is configured for codecs other than G.711 and G.726.

|ICS_enable|

(Optional) Value to enable or disable idle code suppression (ICS) for the CID.

•1 = Enable

•2 = Disable

|pktPeriod|

(Optional) Packetization period (defined in milliseconds). This parameter applies only to G.729a compression.

•10 ms

•20 ms

•30 ms

Note The pktPeriodargument applies only to G.729a compression (codec_type argument value = 4). If you have selected any other compression value, ignore this argument.

Command Modes

AAL2 trunking

Usage Guidelines

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

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

cnfprofparams

To configure a profile preference, use the cnfprofparams command.

cnfprofparams <profileType> <profileNumber> <profilePreference>

Syntax Description

profileType

Profile type to be used for the CID.

•1 = International Telecommunication Union (ITU) I.366.2

•3 = Custom

profileNumber

Number of the profile.

•1 = ITU profile

•2 = ITU profile

•3 = ITU profile

•7 = ITU profile

•8 = ITU profile

•12 = ITU profile

•100 = Custom profile

•101 = Custom profile

•110 = Custom profile

•200 = Custom profile

•210 = Custom profile

profilePreference

Profile preference. It can be one of the following values:

•0 = No preference; exclude the profile from xGCP profile negotiation

•1-11 where 1 is the highest preference (default) and 11 is the lowest preference

Command Modes

Switched AAL2 PVC and AAL2 trunking

Usage Guidelines

Follow standard CLI procedures for this command.

Examples

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

cnfprofelemvoice

To configure the profile voice element, use the cnfprofelemvoice command.

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 > cnfcascode1 4 65

NOTE:In order for VISM card to use the new Idle Code :

Either Reset the Card OR re-add the Cids

Table 1 Parameters for the cnfcascode Command

Parameter

Description

endpt_num

Endpoint number which is to be configured with CAS idle code and seized code. Value is one of the following ranges:

•For template number 1:

–For VISM, from 1 to 145

–For VISM-PR T1, from 1 to 192

–For VISM-PR E1, from 1 to 248

•For template number 2:

–For VISM T1, from 1 to 192

–For VISM E1, from 1 to 248

•For template number 3:

–For VISM, from 1 to 120

–For VISM-PR T1, from 1 to 192

–For VISM-PR E1, from 1 to 248

•For template number 4:

–For VISM-PR, from 1 to 144

Note If the second (optional) endpts_num argument is specified, this argument value is the first endpoint in a consecutive number of endpoints.

idle_code

Four-bit idle code. Value can be in the range from 0-15. This argument represents the four signaling bits—A, B, C, and D—in binary, as bits 3, 2, 1, and 0 respectively, with bit 3 the most significant.

seized_code

Four-bit seized code. Value can be in the range from 0-15. This arguments represents the four signaling bits—A, B, C, and D—in binary, as bits 3, 2, 1, and 0 respectively, with bit 3 the most significant.

[endpts_num]

(Optional) Total consecutive range of endpoints on which the cnfcascode command is applied. Value is from one of the following ranges:

•For template number 1:

–For VISM, from 1 to 145

–For VISM-PR T1, from 1 to 192

–For VISM-PR E1, from 1 to 248

•For template number 2:

–For VISM T1, from 1 to 192

–For VISM E1, from 1 to 248

•For template number 3:

–For VISM, from 1 to 120

–For VISM-PR T1, from 1 to 192

–For VISM-PR E1, from 1 to 248

•For template number 4:

–For VISM-PR, from 1 to 144

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 > dspds0cascode1 1

Ds1 line number: 1

ds0 number: 1

Ds0 If Index: 1

Ds0 Idle Code : 4

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

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

Upgrade Notes

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.

Note VISM/VISM-PR Release 3.1.3 supports the same elements as 3.1(2).

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.

VISM Redundancy

Table 2 provides the support level for 1:N Service Module Redundancy (N = 1 through 11).

Table 2 Service Module Redundancy

Front Card Model Number

Redundancy Support

MGX-VISM-8T1

1:N redundancy (bulk mode support for T1 lines only).

MGX-VISM-8E1

1:N redundancy (bulk mode support for E1 lines only).

MGX-VISM-PR-8T1

1:N redundancy (bulk mode support for T1 lines only).

MGX-VISM-PR-8E1

1:N redundancy (bulk mode support for E1 lines only).

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.

VISM/VISM-PR cards support bulk distribution using the SRM-3T3 and SRM-E (OC3) cards. In a redundancy configuration VISM/VISM-PR cards in bulk distribution mode do not require any backcards.

VISM/VISM-PR Release 3.1.3.1 provides a procedure for the graceful upgrade (one in which the existing VISM/VISM-PR configuration is preserved throughout the upgrade procedure) from one of the following releases:

•From VISM 1.5 to VISM 3.1.3.1

•From VISM 2.1 to VISM 3.1.3.1

•From VISM 2.2 to VISM 3.1.3.1

•From VISM 3.0 to VISM 3.1.3.1

•From VISM 3.1(0) to VISM 3.1.3.1

•From VISM 3.1(1) to VISM 3.1.3.1

•From VISM 3.1(2) to VISM 3.1.3.1

•From VISM 3.1(3) to VISM 3.1.3.1

Caution Installing VISM software updates from VISM Release 2.2 with CALEA to VISM Release 3.1.3.1 without CALEA is not graceful.

Prerequisites

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.

Upgrade VISM/VISM-PR Firmware with PXM1 Card

Software Release 3.1.3.1 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.1 are available:

•003.001.003.001—without CALEA

•003.051.003.001—with CALEA

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(3) and prior.

•New-rev refers to the firmware after the upgrade, Release 3.1.3.1.

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>

where:

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_003.001.003.001.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>

where:

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>

where:

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.

Note If the VISM or VISM-PR card is not part of a redundancy group, complete Step 1 to Step 3.

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/VISM-PR boot code for previous VISM/VISM-PR cards using the VISM/VISM-PR runtime image version 1.0 to 2.0.

Step 1 Telnet to MGX shelf and cc to the VISM/VISM-PR card.

Note VISM/VISM-PR must be in the active state in order to update the VISM/VISM-PR boot code.

Step 2 Access the server where the VISM/VISM-PR boot code resides and TFTP the VISM/VISM-PR boot code to the VISM/VISM-PR card:

a. Type tftp <IP address of the MGX shelf>

b. Type bin at the tftp prompt.

Caution Ensure that you perform
Step 2b. If you to not perform
Step 2b., 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/VISM-PR 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/VISM-PR prompt. This behavior is normal and expected.

Step 3 For the latest boot to take effect, use the resetcd command for VISM/VISM-PR from the PXM card prompt.

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.1 are available:

•003.001.003.001—without CALEA

•003.051.003.001—with CALEA

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 Ensure that the redundant card is returned to the standby state by executing the dspcds command.

Note You must wait for the redundant card to return to the standby state. If you issue the runrev command too early, an error message is generated. The rev change does not occur.

Step 6 To execute the download, enter the runrev command.

runrev sm-primary-slot-num new-rev

Caution Temporary traffic loss occurs.

Step 7 Ensure that the primary slot completes booting and goes into the standby state by executing the dspcds command.

Note You must wait for the primary slot to finish booting and get to standby state. Issuing the commitrev command early might be accepted without an error. However the active and standby cards might not be swapped back to their original state. For example, the original primary card might be left in standby, and the original redundant card might be left as active.

Step 8 To commit the new download to the VISM-PR card, enter the commitrev command.

commitrevsm-primary-slot-num new-rev

The commitrev command switches the primary card from a standby state to an active state and the redundant card from an active state back to a standby state.

Step 9 To verify the card states, execute the dspcds command.

Boot Code Upgrade Procedure with PXM1E and PXM45 Cards

The boot code has not changed from VISM Release 3.1(3) to Release 3.1.3.1. Therefore, the procedure in this section is the same as the upgrade procedure for Release 3.1(3).

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 3 Use the burnbootsm-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-PR 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/VISM-PR software from software Release 3.1.3.1 to an earlier VISM/VISM-PR 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/VISM-PR software from software Release 3.1.3.1 for to Release 3.1, 3.0, 2.2, 2.1, or 2.0:

Step 1 If the VISM/VISM-PR 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#>

where:

SM slot# is the slot number of the VISM/VISM-PR card to be downgraded.

The VISM/VISM-PR card resets on executing this command. Wait for the card to become active.

Step 4 Execute the PXM restoresmcnf command:

restoresmcnf -f <filename> -s <SM slot#>

where:

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/VISM-PR card to be downgraded.

The VISM/VISM-PR 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 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 resetcdslot-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 resetcdslot-num command from the PXM and repeat the dspcd command to insure that the correct card type is shown.

Step 8 If you have no other VISM cards in your chassis, you have completed the hardware upgrade procedure; do not proceed to Step 9. If you have more VISM cards in your chassis, proceed to Step 9.

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.

Step 11 Repeat Step 9 and Step 10 to remove any remaining VISM cards in your chassis and replace them with VISM-PR cards.

Symptom: VISM-PR card reboots when all E1 lines with CIDs goes into alarm.

Conditions: None.

Workaround: None.

CSCdz64206

Symptom: Degradation of voice quality occurs when sending announcement RQNTs on 240 endpoints. Voice quality is good up to 185 endpoints, but quality starts to progressively deteriorate up to 240 endpoints.

Conditions: When more than 145 concurrent announcements exist on VISM and VISM-PR cards, traffic is lost on multiple endpoints. This symptom occurs on MGX 8850 with VISM cards running Release 3.1.0.35-I.

Conditions: If voice calls are configured on an MGX utilizing AAL2 SVCs, the voice calls are dropped when a manual or automatic PXM switch-over occurs.

Workaround: None.

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.

Bug ID

Status

CSCdy88166

Voice clipping with buffer overflow; Closed.

Workaround: If you use AAL2 trunking, it is recommended that you use the cnfcodecjtrdelay "codecType jitter_mode jitter_initdelay" to set the jitter_mode to fixed and the init_delay to 20 ms.

Caveats Resolved in Release 3.1(1)

Table 13 describes the caveats issued against VISM/VISM-PR software that have been resolved in software Release 3.1(1).

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 on the World Wide Web at this URL:

Obtaining Technical Assistance

For all customers, partners, resellers, and distributors who hold valid Cisco service contracts, the Cisco Technical Assistance Center (TAC) provides 24-hour-a-day, award-winning technical support services, online and over the phone. Cisco.com features the Cisco TAC website as an online starting point for technical assistance. If you do not hold a valid Cisco service contract, please contact your reseller.

Cisco TAC Website

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

Opening a TAC Case

Using the online TAC Case Open Tool is the fastest way to open P3 and P4 cases. (P3 and P4 cases are those in which your network is minimally impaired or for which you require product information.) After you describe your situation, the TAC Case Open Tool automatically recommends resources for an immediate solution. If your issue is not resolved using the recommended resources, your case will be assigned to a Cisco TAC engineer. The online TAC Case Open Tool is located at this URL:

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

TAC Case Priority Definitions

To ensure that all cases are reported in a standard format, Cisco has established case priority definitions.

Priority 1 (P1)—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.

Priority 2 (P2)—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.

Priority 3 (P3)—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.

Priority 4 (P4)—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. Go to this URL to visit the company store:

•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 online at this URL:

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

•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:

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)