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

Transcription

1 Release Notes for Cisco Voice Switch Service Module (VXSM) Release These release notes are part number OL Rev. A0, October 31, The Voice Switch Service Module (VXSM) product is supported by the MGX 8880 Media Gateway and the MGX 8850 Multiservice Switch. Refer to these 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 and Command Reference, Release , which is available on cisco.com. Table of Contents About Release New Features in Release Additional VTG/VT to DS1 Mapping Scheme2... Introduction...2 Mapping Schemes...2 User Interface...3 Feature Clarications...4 Online Diagnostic Feature as applied to VXSM...4 DSP Resources under Mixed Codec Conditions...5 Configuring Switching and Trunking Modes...5 VXSM Management Information Base...5 Compatibility...5 Caveats for VXSM Release Open Caveats in Release Resolved Caveats in Release Related Documentation...9 Corporate Headquarters: Cisco Systems, Inc., 170 West Tasman Drive, San Jose, CA USA Copyright 2004 Cisco Systems, Inc. All rights reserved.

2 About Release Obtaining Documentation...9 Cisco.com...9 Ordering Documentation...10 Documentation Feedback...10 Obtaining Technical Assistance...10 Cisco TAC Website...10 Opening a TAC Case...11 TAC Case Priority Definitions...11 Obtaining Additional Publications and Information...11 About Release The VXSM Release follows Release and is a maintenance release of the VXSM software. This release also introduces one small feature to permit users to use the M13 Count method of mapping DS1s to VTG/VGs in OC-3 streams (see New Features section in these notes for details). New Features in Release Additional VTG/VT to DS1 Mapping Scheme Introduction In order to accommodate networks that employs certain types of DACS equipment (Tellabs 5500 DACS), VXSM Release also supports the Tellabs Titan numbering scheme (also referred to as the M13 count method). Release only supports the Bellcore Std. TR 253. With this feature, the user can specify which of the two numbering scheme is to be used. This feature adds two new CLI commands; one to display the currently selected mapping scheme and one to change the mapping scheme. This feature also adds the appropriate MIB objects and traps. Mapping Schemes The SONET-VT1.5/SDH-VC11 payload path type supports 7 VTGs each containing 4 VTs for total of 28 DS1s. In the ITU-T GR.253 spec, the VTG-VT number pairs are incremented such that the VTG number increments from 1-7 before the VT number is incremented. That is, the first VTG-VT pair is 1-1, the second pair is 2-1, the third pair is 3-1 and so on up to 7-1. The next pair is then 1-2, followed by 2-2, 3-2, , then 1-3, and so on until finally, 1-4, 2-4, In the M13 Count numbering scheme, VTG-VT number pair are incremented such that the VT increments from 1-4, before the VTG is incremented. That is, the first VTG-VT pair is 1-1, the second pair is 1-2, and so on up to 1-4. The next pair is then 2-1, followed by 2-2, 2-3, 2-4, then 3-1, 3-2, 3-3, 3-4 and so on until finally, 7-1, 7-2, 7-3,

3 New Features in Release The complete mapping schemes are shown in Table 1 Table 1 VTG/VT to DS1 Mapping DS1 ITU-T GR 253 M13 Count VTG VT VTG VT User Interface CLI The VTG/VT to DS1 mapping feature adds the following two new CLI commands. 3

4 Feature Clarifications Display VT Mapping Syntax: dspvtmapping This command displays the current setting of VTG/VT to DS1 mapping scheme, values are standard or Titan. Standard denotes ITU-T GR 253, Titan denotes M13 Count. Configure VT Mapping Syntax: cnfvtmapping <VtMappingMode> 1 - standard (default) 2 - titan This command switches the current setting of VTG/VT to DS1 mapping scheme to the alternative scheme. Note To execute the cnfvtmapping command: 1. The cnfvtmapping command is valid on the VXSM-155 card only. 2. All SONET lines on the card must be down. 3. All SONET lines on the card must be configured with medium type as sonet. 4. All SONET paths on the card must be configured as VT1.5. Note When VT mapping mode is set to 'titan', the following commands will be affected on the VXSM-OC3 card. cnfln: the option -slt (Medium Type) will be rejected cnfpath -sts: the options -payload and -tg will be rejected In Titan mode, the DS1 path order will be changed in the following commands (see Table 1 for path order). CLI: dsppaths -ds1 dsppathalms -ds1 dsppathstates (for ds1 only) dspvif***s (for ds1 only) dsplapds (for ds1 only) dspberts -ds1 dspds0xcons (for ds1 only) Feature Clarifications Online Diagnostic feature as applied to VXSM. The online diagnostics feature as implemented on the PXM45 card is supported on VXSM Release 5.0. When enabled, using the PXM45 cnfdiag command, this feature performs non-intrusive diagnostic tests that use four of the VXSM s DSP codecs. If the user executes the VXSM dspdspcodecpools command, the resulting display shows the four codecs being used (for diagnostics) and subtracts them from the remaining available codecs (see example below). 4

5 VXSM Management Information Base MGX VXSM.a > dspdspcodecpools ============================================================= DSP codec capacity usage ============================================================= Codec pool Current utilized Current available capacity (#calls) capacity (#calls) ========== ================= ================= G711 family G729/G726/T.38 family The online diagnostics feature does not reduce the maximum number of 8064 codecs available for calls on the VXSM card. If the number of call requests on the VXSM is sufficiently high, the online diagnostic feature is disabled automatically and the four codecs are made available for active calls. DSP Resources under Mixed Codec Conditions When the same codec is used to setup calls on the gateway the available DSP resources will be fully utilized. However when different codecs are used to setup calls the amount of utilizable DSP resources may be limited in certain cases due to fragmentation. Fragmentation is said to have occurred when the available capacities on two different DSP resources have enough available capacity to support a call of a particular codec type but cannot support that codec type individually. Consider two DSP resources whose available capacity is 1 unit each making the total available capacity 2 units. However a codec that requires 2 units cannot be supported in the system because the available capacities have been fragmented across the individual DSP resources. The DSP allocation algorithm on VXSM does make an attempt to smooth the effects of fragmentation but towards the end, fragmentation could happen as the future pattern of calls cannot be predicted beforehand. Configuring Switching and Trunking Modes The simultaneous operation of mixed application modes (Switched VoIP applications and Non-switched Trunking applications) is not supported on a VXSM card. However, both modes can be supported in the Media Gateway by using multiple VXSM cards. VXSM Management Information Base The VXSM Management Information Base (MIB) Version is available by request through your Cisco VXSM product marketing representative. Compatibility Note VXSM Release is only supported with PXM-45. 5

6 Compatibility VXSM software interoperability with the Cisco MGX 8850 (PXM45) Multiservice Switch or the MGX 8880 Media Gateway platform software is listed in Table 2. Table 2 VXSM Software Interoperability Product Latest Firmware Min. Firmware PXM RPM-XF 12.3(2)T5 12.3(2)T5 CWM VISM-PR MGX-AXSM /B MGX-AXSM-4-622/B Table 3 describes the software images available for Release 5.0 for VXSM. Table 3 Software Images for Release 5.0 for VXSM Board Pair Latest Boot Code Version Minimum Boot Code Version Firmware MGX-VXSM-155 vxsm_ _bt.fw vxsm_ _bt.fw vxsm_ fw MGX-VXSM-T1E1 vxsm_ _bt.fw vxsm_ _bt.fw vxsm_ fw 6

7 Caveats for VXSM Release Caveats for VXSM Release This section describes software caveats for Release Open Caveats in Release Table 4 describes the open caveats in VXSM Release Table 4 Open Software Caveats for VXSM Release DDTS Issue CSCee88282 CSCef30919 Description Headline: Ecan still ON during hairpin modem calls Symptom: Modem calls have high transmission error rate. Conditions: h.248 hairpin modem call Workaround: None. Further Problem Description: Ecan should be OFF when modem upspeed occurs. Ecan is ON. This is shown with dsph248calls command. Headline: Standby card failure on performing switchovers Symptom: The standby card fails on performing multiple switchovers and creating ip packet loss. Conditions: There must be 10% packet loss in the network and a switchover must take place during this packet loss. CSCef33806 CSCef44373 Workaround: None. Headline: Resource Allocation failures after 3 swovers at 70cps Symptom: Calls fail after multiple switchovers at 70cps and 100s hold time.. Conditions: Switchovers must happen within about 10 minutes of each other. One single switchover will not cause this problem Workaround: None Headline: addcon fails when 2 controllers(par,pnni) are configured on PXM Symptom: This problem occurs when both controllers, PNNI and PAR are enabled on the shelf and then deleting PAR and then readding it would cause the addcon to fail. Conditions: The condition is when PAR is added on the PXM and then deleted and readded back on the switch. Workaround: None Further Problem Description: Even though PAR is not supported by VXSM card, it is better to identify the problem as what is the interaction between these 2 controllers that is causing VXSM addcon to fail. 7

8 Caveats for VXSM Release Table 4 Open Software Caveats for VXSM Release (continued) DDTS Issue CSCef59551 CSCin76515 CSCuk52672 Description Headline: Call failures at high call rate with announcements Symptom: At high call rates when announcements are played, some calls will fail with error code 500. (The failure is caused because of a race condition between an announcement stop request and the subtraction of the termination.) Conditions: This would happen when announcements are played on some terminations. The exact scenario that causes this is still under investigation. Workaround: None. Headline: Few lines go down on VXSM 48T1E1 after VXSM switchover. Symptom: When vxsm card with 48 T1E1 back card is in 1:1 redundancy configuration and when slot 4 or slot 12 become active during switchover some lines may report alarms. Conditions: The alarms condition occur only for slot 4 or slot 12 with Redundant back card and also these slot become active due to failover from slot 3 or slot 11 (adjacent slot) redundant pair. Workaround: None Further Problem Description:Reconfiguring the certain device register to resolve these alarms Headline: VXSM sends error 430 when receives NULL context audit on busy term Symptom: 430 error code is used when MGC sends a audit in null context for a termination that is actually in context. 435 should be used instead. Conditions: MGC must be auditing a termination that is in a context Workaround: None Resolved Caveats in Release Table 5 describes the open caveats that existed in VXSM Release and are now resolved in Release Table 5 Release Caveats that are resolved in Release DDTS Issue CSCed84520 CSCed88312 CSCed92138 CSCed93276 CSCed93674 CSCed95634 CSCee01411 CSCee02176 CSCee02614 Description Bulk delcid/addcid fails intermittently on OC3 card. CID alarm not reported for last cid when ds1 is in alarm. VXSM reports presence of RCON when there is none installed. It takes 1 minute to connect to MGC after MGC switchover. VXSM HSS Toolkit Suspend while IP network outage. VXSM card comes in Failed state after card reinsertion. MCCI memory allocation failure for play tone list inside sequential. Race condition in crml when stream_del/res_dealloc flow is changed. With Back Card failure APS fails to respond 8

9 Related Documentation Table 5 Release Caveats that are resolved in Release (continued) DDTS Issue CSCee02940 CSCee03061 CSCee03737 CSCee05324 CSCee09371 CSCee10529 CSCee10536 CSCee11279 CSCee13014 CSCee18475 CSCee23125 CSCin70838 CSCin71355 CSCin72233 Description With HHM enabled and FDL, subsequent call on DS1 fails. Crash when playing SSL over both SCN & PDN terminations 70 cps memory leak when MGC disconnects. Megaco PPC in suspend state with 7K calls and 96 announcements. BFG MB console sends out garbage characters during boot up. VQ issues with 5.0(0.24)P1 with VAD enabled. Calls keep failing after VXSM sw/o during sw upgrade Need to disable humvee for standby card. After VXSM 4xOC3 reset cids stay in lnalm but there is none present. Backcards come up in mismatch mode. After resetsys, one redundant pvc failed. TDM HP without DSP crashes the card. IL: Tones not passing in HP call after ECAN set OFF, switchback. addcon fail with exception err when NULL pointer enable in this image. The MGX-VXSM-155 card is also known as the MGX-VXSM-4OC card. The MGX-VXSM-T1/E1 card is also known as the MGX-VXSM-48T1/E1 card. Related Documentation The following documents contains information that may be useful to software Release 5.0 for VXSM: Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Configuration Guide, Release 5 Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide, Release 4 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: You can access the Cisco website at this URL: 9

10 Documentation Feedback International Cisco websites can be accessed from this URL: Ordering Documentation 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 Ordering tool: Nonregistered Cisco.com users can order documentation through a local account representative by calling Cisco Systems Corporate Headquarters (California, USA) at or, elsewhere in North America, by calling NETS (6387). Documentation Feedback You can submit 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 We appreciate your comments. 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: Accessing all the tools on the Cisco TAC website requires a Cisco.com user ID and password. If you have a valid service contract but do not have a login ID or password, register at this URL: 10

11 Obtaining Additional Publications and Information 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. To open a case by telephone, use one of the following numbers: Asia-Pacific: (Australia: ) EMEA: USA: For a complete listing of Cisco TAC contacts, go to this URL: 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: 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: 11

12 Obtaining Additional Publications and Information 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: iq Magazine is the Cisco bimonthly publication that delivers the latest information about Internet business strategies for executives. You can access iq Magazine at this URL: 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: Training Cisco offers world-class networking training. Current offerings in network training are 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 United States and certain other countries. All other trademarks mentioned in this document or Website 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. (0401R) Copyright 2004, Cisco Systems, Inc. All rights reserved. 12