Table Of Contents
Cisco Unified CallManager Support
Usage Guidelines and Restrictions
Detailed Installation and Configuration Procedures
Important Notes in Cisco IOS Release 12.3(8)XY
Important Notes in Cisco IOS Release 12.3(8)XY
Automatically Upgrading Feature Cards FPGA
Downgrading Feature Cards FPGA
Ethernet to FastEthernet Interface Change Notice
Media Termination Point Port Density
Caveats for Cisco IOS Release 12.3(8)XY
Open Caveats in Release 12.3(8)XY7
Closed Caveats in Release 12.3(8)XY7
Open Caveats in Release 12.3(8)XY3
Resolved Caveats in Release 12.3(8)XY3
Open Caveats in Release 12.3(8)XY2
Resolved Caveats in Release 12.3(8)XY2
Open Caveats in Release 12.3(8)XY1
Resolved Caveats in Release 12.3(8)XY1
Open Caveats in Release 12.3(8)XY
Resolved Caveats in Release 12.3(8)XY
Manual Configuration in the Absence of CMM-Specific XML Files
Obtaining Documentation, Obtaining Support, and Security Guidelines
Release Notes for the Cisco Catalyst 6500 Series and the Cisco 7600 Series Communication Media Module for Cisco IOS Release 12.3(8)XY
July 26, 2006
Cisco IOS Release 12.3(8)XY7
OL-6314-01 Rev A2
These release notes for the Cisco Catalyst 6500 Series and the Cisco 7600 Series Communication Media Module (CMM) describe the enhancements provided in the Cisco IOS Release 12.3(8)XY releases. These release notes are updated as needed.
For a list of the software caveats that apply to Cisco IOS Release 12.3(8)XY, see the "Caveats for Cisco IOS Release 12.3(8)XY" section and Caveats for Cisco IOS Release 12.3 T. The caveats document is updated for every maintenance release and is located on Cisco.com.
Use these release notes with Cross-Platform Release Notes for Cisco IOS Release 12.3 located on Cisco.com.
Cisco recommends that you view the field notices for this release to see if your software or hardware platforms are affected. If you have an account on Cisco.com, you can find field notices at http://www.cisco.com/warp/customer/tech_tips/index/fn.html. If you do not have a Cisco.com login account, you can find field notices at http://www.cisco.com/warp/public/tech_tips/index/fn.html.
Note
Throughout this publication, except where specifically differentiated, the following terms apply:
•
•
•
•
Contents
•
•
•
System Requirements
This section describes the system requirements for the CMM software release.
Hardware Supported
CMM requires either a Supervisor Engine 1, Supervisor Engine 2, Supervisor Engine 720, or Supervisor Engine 32. The supervisor engine can have an MSFC, MSFC2, or MSFC3, but CMM does not require one for configuration or operation. See the software recommendations in Table 1.
Table 1 Software Recommendations for the Communication Media Module
Software Version
Software VersionWS-SVC-CMM
Communication Media Module
12.3(8)XY7
12.3(8)XY7
12.3(8)XY7
7.6(8)
1 See the "Software Requirements" section for detailed information on which software releases support the various supervisor engines.
Software Requirements
Note
•
•
The software requirements for CMM to support Voice Features for Cisco IOS Release 12.3(8)XY7 are as follows:
•
•
•
The software requirements for CMM to support all other features are as follows:
•
–
–
–
•
–
–
–
Note
•
Cisco Unified CallManager Support
Cisco IOS Release 12.3(8)XY7 supports Cisco Unified CallManager Release 3.2(2) and later releases.
Memory Recommendations
The memory requirements for Cisco IOS Release 12.3(8)XY are shown in Table 2.
Feature Sets
Table 3 lists the supported features for the CMM T1 and E1 port adapters.
Table 4 lists the supported features for the CMM ad-hoc conferencing and transcoding port adapter.
Table 5 Lists the supported features for the FXS Analog Interface Module.
Table 6 lists the parameters for the FXS Analog Interface Module Fax and Modem Transport.
Table 3 T1 and E1 Port Adapters Supported Features
Line code—HDB33 , AMI
Frame format—with CRC4/no CRC46
SRST7
SRST
MGCP gateway fallback
MGCP gateway fallback
FDL with T1 CAS/PRI for extended super frame (only) signaling.
-
MGCP and H.323:
T1-PRI—Supports up to 18 ports
T1-CAS—Supports up to 18 ports
T1-CAS E&M8 Wink Start
T1-CAS E&M Delay Dial
T1-CAS E&M Immediate Start9
T1-CAS FXS Loop Start
T1-CAS FXO Loop Start
T1-CAS FXS Ground Start
T1-CAS FXO Ground Start
Fax Pass-through
Cisco Fax Relay
T.38 fax relay
Modem Pass-through
Music on Hold (unicast, multicast)
DTMF Relay10 , 11
G711 codec (sampling size: 10, 20, and 30 ms)
G729 codec (sampling size: 10, 20, 30, 40, 50, 60 ms)
QSIG backhaulMGCP and H.323:
E1-PRI—Supports up to 18 ports
Fax Pass-through
Cisco Fax Relay
DTMF Relay13
Modem Pass-through
Music on Hold (unicast, multicast)
G711 codec (sampling size: 10, 20, and 30 ms)
G729 codec (sampling size: 10, 20, 30, 40, 50, 60 ms)
QSIG backhaul
E1 R2 CAS signaling9Fax Pass-through
Cisco Fax Relay
T.38 fax relay
Modem Pass-through
Music on Hold (unicast, multicast)
DTMF Relay10 , 11
G711 codec (sampling size: 10, 20, and 30 ms)
G729 codec (sampling size: 10, 20, 30, 40, 50, 60 ms)
QSIG backhaul
1 B8ZS = binary 8-zero substitution.
2 AMI = alternate mark inversion.
3 HDB3 = high-density bipolar with three zeros.
4 SF = super framing.
5 ESF = extended super framing.
6 CRC = cyclic redundancy check.
7 SRST = Survival Remote Site Telephony.
8 E&M = ear and mouth.
9 Supported only with H.323.
10 DTMF = Dual Tone Multi-Frequency.
11 DTMF is supported; DTMF/MF is not supported.
Table 4 Ad-Hoc Conferencing and Transcoding Port Adapter Supported Features
Media support for transcoding and conferencing:
•
•
–
–
–
Speaker selection (three loudest speakers).
Performance: Each ACT port adapter can support up to 128 ports with a max of 128 participants in a single conference.
IP precedence bits, DSCP1 , and 802.1Q marking.
One registration entity per port adapter.
Standalone transcoding without associated conference. Codecs and packetization intervals supported are the same as for conferencing.
MTP 2 support.
Modem and fax support through MTP.
Fallback support for transcoding and ad-hoc conferences.
Support for spanning conferences between digital signal processors (DSP) on the same port adapter.
1 DSCP = differentiated services code point.
2 MTP = media termination point.
Usage Guidelines and Restrictions
This section provides usage guidelines and restrictions for CMM:
•
•
Installation Notes
Detailed Installation and Configuration Procedures
For detailed installation and configuration procedures, refer to the Catalyst 6500 Series and Cisco 7600 Series CMM Installation and Configuration Note at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/lan/cat6000/cfgnotes/78_14107.htmSupported Version
Cisco IOS Release 12.3(8)XY only works with field-programmable gate array (FPGA) erasable programmable logic device EPLD B version 10 (hex 0XA). EPLD B firmware upgrade occurs automatically when Cisco IOS Release 12.3(8)XY is loaded on CMM the first time.
MIBs
To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL:
http://tools.cisco.com/ITDIT/MIBS/servlet/index
If Cisco MIB Locator does not support the MIB information that you need, you can also obtain a list of supported MIBs and download MIBs from the Cisco MIBs page at the following URL:
http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml
To access Cisco MIB Locator, you must have an account on Cisco.com. If you have forgotten or lost your account information, send a blank e-mail to cco-locksmith@cisco.com. An automatic check will verify that your e-mail address is registered with Cisco.com. If the check is successful, account details with a new random password will be e-mailed to you. Qualified users can establish an account on Cisco.com by following the directions found at this URL:
http://tools.cisco.com/RPF/register/register.do
The Cisco Catalyst 6500 Series and the Cisco 7600 Series CMM support Simple Network Management Protocol (SNMP) Version 3 support for the following MIBs:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Important Notes
The following sections contain important notes about Cisco IOS Release 12.3(8)XY that can apply to the Cisco Catalyst 6500 series and the Cisco 7600 series communication media module.
Deferrals
Cisco IOS software images are subject to deferral. Cisco recommends that you view the deferral notices at the following location to determine if your software release is affected:
http://www.cisco.com/kobayashi/sw-center/sw-ios-advisories.shtml
Field Notices and Bulletins
For general information about the types of documents listed in this section, refer to the following document:
http://www.cisco.com/warp/customer/cc/general/bulletin/software/general/1654_pp.htm
•
•
•
•
•
Important Notes in Cisco IOS Release 12.3(8)XY
The following section describes important notes for Cisco IOS Release 12.3(8)XY.
Release Upgrade Notice
The CMM wscmm-i6s-mz.123-8.XY image contains a new bundle 4.4.X DSPware infrastructure. Once downloaded, this software will perform an automatic FPGA upgrade to version 10 (hex 0xA) in order to take advantage of the new bundle 4.4.X DSPware infrastructure.
After the upgrade, power cycling CMM is required. If you have an ACT module on CMM, you must reconfigure the ACT module with the new FastEthernet interface instead of Ethernet. Any other CMM release before wscmm-i6s-mz.123-8.XY image will require an automatic bundle FPGA upgrade to version 10 (hex 0xA).
Note
Important Notes in Cisco IOS Release 12.3(8)XY
The following section describes important notes for Cisco IOS Release 12.3(8)XY. Please read the entire release note before downloading and installing the CMM 12.3(8)XY image. See the following sections:
•
•
•
Automatically Upgrading Feature Cards FPGA
The first time you are loading the Cisco IOS Release 12.3(8)XY image, any FPGA EPLD B on T1/E1/FXS module and any FPGA EPLD A on the FXS module with a version not set to 10(hex 0xA) will be upgraded automatically to version 10(hex 0xA). This upgrade is necessary to work with the Cisco IOS software 12.3(8)XY image.
1.
a.
b.
Note
Example:
CMM#term monitor ?<cr>2.
a.
Note
b.
An alternative method to the above steps is to remove CMM from the Catalyst 6000chassis and then insert CMM into the chassis again. Before hot swapping CMM, refer to the safety precautions and port adapter removal procedures in the Catalyst 6500 Series and Cisco 7600 Series CMM Installation and Configuration Note at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/lan/cat6000/cfgnotes/78_14107.htm3.
4.
5.
Sample screen logs for upgrade FPGA output are shown in the following section.
Sample Upgrade Screen Logs
In the following examples, the first log shows an upgrade EPLD B on E1, and the second log shows an upgrade EPLD A on FXS.
--------- Downloading E1 module EPLD B screen log ------System Bootstrap, Version 12.2(1r)T1, RELEASE SOFTWARE (fc1)TAC Support: http://www.cisco.com/tacCopyright (c) 2002 by cisco Systems, Inc.-SVC-CMM platform with 262144 Kbytes of main memoryBoot config value : 0^Mrommon 1 > b bootflash:wscmm-i6s-mz.xySelf decompressing the image : ####################################################################################################################### [OK]Cisco IOS Software, Cat6K-lc Software (wscmm-I6S-M), Experimental Version 12.3(20040717:022843) [atrang-xy 116]^MCopyright (c) 1986-2004 by Cisco Systems, Inc.Compiled Fri 27-Aug-04 16:45 by atrangImage text-base: 0x60010F60, data-base: 0x61100000controller E1 1/0controller E1 1/1controller E1 1/2controller E1 1/3framing NO-CRC4linecode amids0-group 1 timeslots 1-15,17-31 type e&m-melcas-winkcontroller E1 1/4controller E1 1/5framing NO-CRC4linecode amids0-group 1 timeslots 1-15,17-31 type e&m-melcas-winkvoice-port 1/3:1echo-cancel coverage 64voice-port 1/5:1echo-cancel coverage 64mediacard 2port 1/3:1port 1/5:1Updating Daughterboard ID/index: 0/73 EPLD B = 3840Takes a few seconds ...Press RETURN to get started!*Mar 1 00:00:09.639: %JAGGER-6-INFO: ms_dsprm_init is NOT ACTIVE, FPGA epld will be upgraded*Mar 1 00:00:09.755: %SYS-6-LOGGERSTART: Logger process started*Mar 1 00:00:11.639: %SYS-5-CONFIG_I: Configured from memory by console*Mar 1 00:00:11.895: %SYS-5-RESTART: System restarted --Cisco IOS Software, Cat6K-lc Software (wscmm-I6S-M), Experimental Version 12.3(20040717:022843) [atrang-xy 116]Copyright (c) 1986-2004 by Cisco Systems, Inc.Compiled Fri 27-Aug-04 16:45 by atrang*Mar 1 00:00:11.895: %SNMP-5-COLDSTART: SNMP agent on host at-jagger is undergoing a cold start*Mar 1 00:00:11.899: %EPLD-4-START_WARNING:############### START FPGA DOWNLOAD PROCESS ################## All feature cards will not be enabled during FPGA ## download. Please ignore configuration 'invalid' messages ## at boot up time. Do not change/save configuration ## until after FPGA download is completed and power-cycle ## or configurations for feature cards will be lost... ##############################################################*Mar 1 00:00:12.015: %EPLD-3-UPGRADE: Module 1 upgrade FPGA B to version 10*Mar 1 00:00:12.287: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0,changed state to down*Mar 1 00:00:13.063: %LINK-5-CHANGED: Interface FastEthernet1/0, changed state to administratively down*Mar 1 00:00:13.295:*Mar 1 00:00:13.763: %LINK-3-UPDOWN: Interface GigabitEthernet1/0, changed state to up*Mar 1 00:00:14.239: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet1/0, changed state to down*Mar 1 00:00:21.291: %SCP-5-ONLINE: Module online*Mar 1 00:00:21.291: %PIM-5-DRCHG: DR change from neighbor 0.0.0.0 to 10.1.1.107 on interface GigabitEthernet1/0 (vrf default)*Mar 1 00:00:21.407: %EPLD-6-INFO: Start programming FPGA B, this can take up to 6 minutes per download...*Mar 1 00:00:22.199: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0,changed state to up*Mar 1 00:00:22.199: %PIM-5-NBRCHG: neighbor 10.1.1.1 UP on interface GigabitEthernet1/0(vrf default) MODULE 1 FPGA download completion 5 percent...MODULE 1 FPGA download completion 10 percent...*Mar 1 00:00:47.879: %HSRP-6-STATECHANGE: GigabitEthernet1/0 Grp 0 state Standby -> ActiveMODULE 1 FPGA download completion 15 percent...MODULE 1 FPGA download completion 20 percent...MODULE 1 FPGA download completion 25 percent...MODULE 1 FPGA download completion 30 percent...MODULE 1 FPGA download completion 35 percent...MODULE 1 FPGA download completion 40 percent...MODULE 1 FPGA download completion 45 percent...MODULE 1 FPGA download completion 50 percent...MODULE 1 FPGA download completion 55 percent...MODULE 1 FPGA download completion 60 percent...MODULE 1 FPGA download completion 65 percent...MODULE 1 FPGA download completion 70 percent...MODULE 1 FPGA download completion 75 percent...MODULE 1 FPGA download completion 80 percent...MODULE 1 FPGA download completion 85 percent...MODULE 1 FPGA download completion 90 percent...MODULE 1 FPGA download completion 95 percent...Updating Daughterboard ID/index: 0/73 EPLD B = 10Takes a few seconds ...*Mar 1 00:04:39.039: %EPLD-6-INFO: FPGA B download slot 1 successfully completed!*Mar 1 00:04:45.255: %EPLD-4-COMPLETE:############# FEATURE CARDS FPGA DOWNLOAD COMPLETED ######### ^M# In order for feature cards to function, power-cycle CMM # ^M# immediately! Do not change/save configuration # ^M# until after power-cycle or configurations for feature # ^M# cards will be lost... # ^M############################################################# ^M----------- Downloading FXS EPLD A screen log ------Updating Daughterboard ID/index: 1/71 EPLD A = 3840Takes a few seconds ...Press RETURN to get started!*Mar 1 00:00:09.835: %JAGGER-6-INFO: ms_dsprm_init is NOT ACTIVE, FPGA epld will be upgraded*Mar 1 00:00:09.951: %SYS-6-LOGGERSTART: Logger process started*Mar 1 00:00:10.275: %SYS-5-CONFIG_I: Configured from memory by console*Mar 1 00:00:10.527: %SYS-5-RESTART: System restarted --Cisco IOS Software, Cat6K-lc Software (wscmm-I6S-M), Experimental Version 12.3(20040717:022843) [atrang-xy 116]Copyright (c) 1986-2004 by Cisco Systems, Inc.Compiled Fri 27-Aug-04 16:45 by atrang*Mar 1 00:00:10.527: %SNMP-5-COLDSTART: SNMP agent on host at-jagger is undergoing a cold start*Mar 1 00:00:10.531: %EPLD-4-START_WARNING:############### START FPGA DOWNLOAD PROCESS ################## All feature cards will not be enabled during FPGA ## download. Please ignore configuration 'invalid' messages ## at boot up time. Do not change/save configuration ## until after FPGA download is completed and power-cycle ## or configurations for feature cards will be lost... ##############################################################*Mar 1 00:00:10.647: %EPLD-3-UPGRADE: Module 2 upgrade FPGA A to version 10*Mar 1 00:00:11.463: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0,changed state to down*Mar 1 00:00:12.163:*Mar 1 00:00:12.163:*Mar 1 00:00:12.163: %LINK-5-CHANGED: Interface FastEthernet1/0, changed state to administratively down*Mar 1 00:00:12.395: %LINK-3-UPDOWN: Interface GigabitEthernet1/0, changed state to up*Mar 1 00:00:13.339: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet1/0, changed state to down*Mar 1 00:00:13.571: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0, changed state to up*Mar 1 00:00:13.819: %PIM-5-DRCHG: DR change from neighbor 0.0.0.0 to 10.1.1.107 on interface GigabitEthernet1/0 (vrf default)*Mar 1 00:00:15.275: %PIM-5-NBRCHG: neighbor 10.1.1.1 UP on interface GigabitEthernet1/0 (vrf default)*Mar 1 00:00:20.747: %SCP-5-ONLINE: Module online*Mar 1 00:00:21.927: %EPLD-6-INFO: Start programming FPGA A, this can take up to 5 minutes per download...ODULE 2 FPGA download completion 5 percent...MODULE 2 FPGA download completion 10 percent...*Mar 1 00:00:46.499: %HSRP-6-STATECHANGE: GigabitEthernet1/0 Grp 0 state Standby -> ActiveMODULE 2 FPGA download completion 15 percent...MODULE 2 FPGA download completion 20 percent...MODULE 2 FPGA download completion 25 percent...MODULE 2 FPGA download completion 30 percent...MODULE 2 FPGA download completion 35 percent...ODULE 2 FPGA download completion 40 percent...MODULE 2 FPGA download completion 45 percent...MODULE 2 FPGA download completion 50 percent...MODULE 2 FPGA download completion 55 percent...MODULE 2 FPGA download completion 60 percent...MODULE 2 FPGA download completion 65 percent...MODULE 2 FPGA download completion 70 percent..MODULE 2 FPGA download completion 80 percent...MODULE 2 FPGA download completion 85 percent...MODULE 2 FPGA download completion 90 percent...MODULE 2 FPGA download completion 95 percent...Updating Daughterboard ID/index: 1/71 EPLD A = 10Takes a few seconds ...*Mar 1 00:04:42.495: %EPLD-6-INFO: FPGA A download slot 2 successfully completed!*Mar 1 00:04:48.827: %EPLD-4-COMPLETE:############# FEATURE CARDS FPGA DOWNLOAD COMPLETED ######### ^M# In order for feature cards to function, power-cycle CMM # ^M# immediately! Do not change/save configuration # ^M# until after power-cycle or configurations for feature # ^M# cards will be lost... # ^M############################################################# ^MDowngrading Feature Cards FPGA
If you need to run an image earlier than Cisco IOS Release 12.3(8)XY after upgrading FPGA to version 10 (hex 0XA), FPGA must be downgraded to version 2 for CMM to function correctly. For more information, see the following jam message link:
http://www.cisco.com/cgi-bin/tablebuild.pl/cmm
Use the following downgrade procedure.
1.
2.
3.
4.
5.
Note
Example:
CMM#term monitor ?<cr>6.
7.
8.
9.
10.
11.
Sample screen logs for downgrade FPGA output are shown in the following section.
Sample Screen Logs For Downgrade FPGA
Router# test fpga downgrade 1##################################################################### Slot 1 FPGA will be downgraded to version 2.### Make sure you have <anokha_t1_e1.jam> file for T1/E1 card### and <anokha_fxs.jam> file for FXS card in bootflash##################################################################### MUST RUN ZP IMAGE WITH DOWNGRADE FPGA VERSION 2 AFTER DOWNLOAD!!!##################################################################Proceed with downgrade?[confirm]Updating Daughterboard ID/index: 0/70Takes a few seconds ...MUST RELOAD CMM IMMEDIATELY to download FPGA code.Router# reloadProceed with reload? [confirm]*Mar 1 00:35:16.947: %SYS-5-RELOAD: Reload requested by console. ReloadReason: Reload command.*Mar 1 00:35:16.947: %HSRP-6-STATECHANGE: GigabitEthernet1/0 Grp 0 stateActive -> InitSystem Bootstrap, Version 12.2(1r)T1, RELEASE SOFTWARE (fc1)TAC Support: http://www.cisco.com/tacCopyright (c) 2002 by cisco Systems, Inc.WS-SVC-CMM platform with 262144 Kbytes of main memoryBoot config value : 2Autoboot: Executing boot bootflash:wscmm-i6s-mzSelf decompressing the image :########################################################################################## #####################[OK]Cisco IOS Software, Cat6K-lc Software (wscmm-I6S-M), Experimental Version12.3(20040309:050923) [r0308 109]Copyright (c) 1986-2004 by Cisco Systems, Inc.Compiled Wed 10-Mar-04 15:18Image text-base: 0x60010A78, data-base: 0x61000000############################################################## ## FEATURE CARD FPGA UPGRADE/DOWNGRADE ## ## One or more feature card FPGA will be download at boot up ## up. All feature cards will not be enabled during FPGA ## download. Please ignore all configuration 'invalid' ## message at boot up time. Do not change/save ## configuration until after FPGA download is completed and ## power-cycle, or configurations for feature cards will be ## lost. ## ##############################################################controller T1 1/0^framing sf^linecode amiPress RETURN to get started!Router>*Mar 1 00:00:10.195: %SYS-5-CONFIG_I: Configured from memory by console*Mar 1 00:00:10.443: %SYS-5-RESTART: System restarted --Cisco IOS Software, Cat6K-lc Software (wscmm-I6S-M), Experimental Version12.3(20040309:050923) [r0308 109]Copyright (c) 1986-2004 by Cisco Systems, Inc.Compiled Wed 10-Mar-04 15:18*Mar 1 00:00:10.443: %SNMP-5-COLDSTART: SNMP agent on host at-jagger isundergoing a cold start*Mar 1 00:00:10.447: %EPLD_B-4-START_WARNING:############### START FPGA DOWNLOAD PROCESS ################## All feature cards will not be enabled during FPGA ## download. Please ignore configuration 'invalid' messages ## at boot up time. Do not change/save configuration ## until after FPGA download is completed and power-cycle ## or configurations for feature cards will be lost... ##############################################################*Mar 1 00:00:10.563: %EPLD_B-6-INFO: Slot 1: File <anokha_t1_e1.jam>opens OK !!!*Mar 1 00:00:10.563: %EPLD_B-3-DOWNGRADE: Module 1 downgrade FPGA toversion V.2*Mar 1 00:00:11.259: %LINEPROTO-5-UPDOWN: Line protocol on InterfaceGigabitEthernet1/0, changed state to down*Mar 1 00:00:11.727:*Mar 1 00:00:12.427: %LINK-3-UPDOWN: Interface GigabitEthernet1/0,changed state to up*Mar 1 00:00:12.907: MGCP: Codec g711ulaw is not available on thisrouter.*Mar 1 00:00:12.907: MGCP: Default codec changed to G.711 u-law*Mar 1 00:00:13.631: %LINEPROTO-5-UPDOWN: Line protocol on InterfaceGigabitEthernet1/0, changed state to up*Mar 1 00:00:21.751: %EPLD_B-6-INFO: Start programming FPGA, this cantake up to 6 minutes per card...*Mar 1 00:00:24.743: %SCP-5-ONLINE: Module online*Mar 1 00:00:39.431: MODULE 1 FPGA download completion 5 percent...*Mar 1 00:00:46.431: %HSRP-6-STATECHANGE: GigabitEthernet1/0 Grp 0 stateStandby -> Active*Mar 1 00:00:57.551: MODULE 1 FPGA download completion 10 percent...*Mar 1 00:01:15.671: MODULE 1 FPGA download completion 15 percent...*Mar 1 00:01:33.775: MODULE 1 FPGA download completion 20 percent...*Mar 1 00:01:51.923: MODULE 1 FPGA download completion 25 percent...*Mar 1 00:02:10.035: MODULE 1 FPGA download completion 30 percent...*Mar 1 00:02:28.147: MODULE 1 FPGA download completion 35 percent...*Mar 1 00:02:46.283: MODULE 1 FPGA download completion 40 percent...*Mar 1 00:03:04.407: MODULE 1 FPGA download completion 45 percent...*Mar 1 00:03:22.515: MODULE 1 FPGA download completion 50 percent...*Mar 1 00:03:42.283: MODULE 1 FPGA download completion 55 percent...*Mar 1 00:04:02.107: MODULE 1 FPGA download completion 60 percent...*Mar 1 00:04:21.903: MODULE 1 FPGA download completion 65 percent...*Mar 1 00:04:41.687: MODULE 1 FPGA download completion 70 percent...*Mar 1 00:05:01.511: MODULE 1 FPGA download completion 75 percent...*Mar 1 00:05:21.307: MODULE 1 FPGA download completion 80 percent...*Mar 1 00:05:41.095: MODULE 1 FPGA download completion 85 percent...*Mar 1 00:06:20.711: MODULE 1 FPGA download completion 95 percent...Updating Daughterboard ID/index: 0/70Takes a few seconds ...*Mar 1 00:06:35.715: %EPLD_B-6-INFO: FPGA download slot 1 successfullycompleted!*Mar 1 00:06:41.815: %EPLD_B-6-INFO: ONLY RUN ZP IMAGE with this moduleor CMM will be CORRUPTED!*Mar 1 00:06:41.931: %EPLD_B-4-COMPLETE_ZP:############# FEATURE CARDS FPGA DOWNLOAD COMPLETED ########## In order for feature cards to function, power-cycle CMM ## immediately and reload with ZP image! ## Do not change/save configuration until after power-cycle ## or configurations for feature cards will be lost... ##############################################################*Mar 1 00:06:51.931: %EPLD_B-4-COMPLETE_ZP:############# FEATURE CARDS FPGA DOWNLOAD COMPLETED ########## In order for feature cards to function, power-cycle CMM ## immediately and reload with ZP image! ## Do not change/save configuration until after power-cycle ## or configurations for feature cards will be lost... ##############################################################Software Upgrade Procedure
Use the following procedure to upgrade your software.
Note
Obtaining a New Image to Bootflash:
Use the following procedure to obtain a new image into bootflash. Use the dir bootflash: command to ensure that there is enough space in the bootflash: directory to hold the new image.
CMM# dir bootflash:Directory of bootflash:/1 -rw- 10503084 <no date> wscmm-i6s-mz.123-8.XY4.fc233030140 bytes total (22526992 bytes free)
Note
After deleting the unwanted images, enter the squeeze bootflash: command to recover the free memory. Proceed with the software upgrade as follows:
CMM# copy tftp bootflash:Address or name of remote host []? 192.1.2.201Source filename []? wscmm-i6s-mz.123-8.XY2Destination filename [wscmm-i6s-mz.123-8.XY2]?Accessing tftp://192.1.2.201/wscmm-i6s-mz.123-8.XY2...Erase bootflash:before copying? [confirm]nLoading wscmm-i6s-mz.123-8.XY2 from 192.1.2.201 (via GigabitEthernet1/0):!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!![OK - 5064616/10128384 bytes]Verifying checksum... OK (0x23)5064616 bytes copied in 31.964 secs (163374 bytes/sec)CMM#Booting a Specific CMM Image
To store images and configure the system to boot a specific CMM image, Cisco recommends that you store two images in the CMM bootflash: the golden (existing) image and the new image. You should store the golden image in the first boot location and the new image in the second boot location. Then configure the image that needs to be booted up to the golden image using the following commands:
CMM# configure terminalCMM(conf)> boot system bootflash: cmm-golden-imageCMM(conf)> config-register 0x2By setting the configuration register to 0x2, the default booting from bootflash: is enabled. The booting will take place from the first file. The boot system command overrides the default booting from bootflash:. Hence it is important to have the golden image (the image that needs to be booted) as the first file in the bootflash: and also to set the command boot system bootflash: cmm-golden-image to boot with the golden image. By setting the boot system bootflash: cmm-golden-image, there is no chance of accidentally booting up with an unwanted image.
Setting the configuration register to 0x01 would use the first image from the bootflash:.The recommended setting for the configuration register is 0x2 and the configuration of the boot system bootflash: cmm-golden-image.
If you have console access to the CMM module and wish to enter ROMMOM every time the CMM reloads, you can configure the config-register to be 0x0.
Note
Ethernet to FastEthernet Interface Change Notice
If you are running an earlier CMM Cisco IOS image and have WS-SVC-CMM-ACT modules on board, loading Cisco IOS Release 12.3(8)XY image for the first time will change the Ethernet interfaces corresponding to the WS-SVC-CMM-ACT modules to FastEthernet interfaces with no IP address configured and in the shutdown state.
We recommend that you save and record the Ethernet interface configurations before upgrading to Cisco IOS Release 12.3(8)XY and that you reconfigure the FastEthernet interface once CMM is up and running.
Media Termination Point Port Density
Media Termination Point (MTP) Port Density provides increased transcoder port density to support additional MTP sessions. This feature provides the following media support for transcoding and conferencing:
•
•
–
–
–
Table 7 lists the numbers of ports and MTP sessions this feature supports:
Table 7 Port Density and MTP Sessions
Per DSP
128
64
Per Ad-Hoc Conferencing and Transcoding Port Adapter
512
256
Per Communications Media Module (CMM)
2048
1024
Sample Screen Logs For MTP Port Density
mediacard 1resource-pool mtpl dsps 4!mediacard 2resource-pool xcoder3 dsps 4sccp local GigabitEthernet1/0sccp ccm 10.1.1.8 identifier 1sccp ccm 10.1.1.58 identifier 2sccp!sccp ccm group 1associate ccm 1 priority 1associate ccm 2 priority 2associate profile 1 register MTP0003feacc83fassociate profile 2 register MTP0003feacc840!dspfarm!dspfarm profile 1mtpcodec g711ulaw packetization-period 30codec g711alaw packetization-period 30associate resource-pool mtp1Caveats for Cisco IOS Release 12.3(8)XY
This section documents possible unexpected behavior by Cisco IOS Release 12.3(8)XY and describes only severity 1 and 2 caveats and select severity 3 caveats.
These sections describe the following caveats:
•
•
•
•
•
•
•
•
•
•
•
Open Caveats in Release 12.3(8)XY7
There are no open caveats in this release.
Closed Caveats in Release 12.3(8)XY7
There are no closed caveats in this release.
Open Caveats in Release 12.3(8)XY3
•
Symptoms: When a voice gateway is reset by a Cisco CallManager, the voice gateway may not reregister with the Cisco CallManager, even when the output of the show isdn statistics command indicates the following state:
MULTIPLE_FRAME_ESTABLISHED and L3 Protocol(s) = CCM-Manager.This problem occurs when the voice gateway fails to send a restart message (RM) to the Cisco CallManager.
Conditions: This symptom is observed on a Cisco 3745 that functions as a voice gateway and that runs Cisco IOS Release 12.3(4)T6, 12.3(8)T3, or 12.3(8)T4.
Workaround: Enter the shutdown controller configuration command followed by the no shutdown controller configuration command on the T1 controller of the interface that connects to the Cisco CallManager.
•
Symptoms: Cisco Catalyst 6509 Sup720 running 12.2(18)SXD2, populated with WS-CMM-SVC module with Cisco IOS Release 12.3(8)XY2, WS-CMM-SVC module experienced frequent crash.
Workaround: There is no workaround.
•
Symptoms: A Cat6k with CMM module may see FCS errors increasing on the CMM ports when repeating the show counters x command on the supervisor, where x is the slot the CMM resides in. There isn't any impact seen at this time; the problem appears to be cosmetic only.
Conditions: Sup2 running 7.6(8) and CMM running 12.3(8)XY1. It's not known at this time whether the problem is seen with other supervisors or different code versions on either the supervisor or CMM.
Workaround: There is no known workaround.
Note
Resolved Caveats in Release 12.3(8)XY3
•
Symptoms: An MGCP gateway (GW) does not send a DLCX message with the proper reason code (E:) when an RTP loss occurs because the Ethernet interface through which the RTP transfer occurs on the GW is shut down.
Because the GW does not notify the CA about the RTP loss via a DLCX message with the proper reason code, the CA continues to send MGCP messages to the GW and vice versa in a normal way. However, these MGCP messages do not reach the GW or CA because the Ethernet interface on the GW is shut down, preventing the deletion of existing connections on the GW.
Conditions: This symptom is observed on a Cisco platform that functions as an MGCP GW and that has a single interface to the CA and terminating GW.
Workaround: Delete the connections on the MGCP GW manually through MGCP CLIs.
Open Caveats in Release 12.3(8)XY2
There are no new open caveats in this release. See Open Caveats in Release 12.3(8)XY1.
Resolved Caveats in Release 12.3(8)XY2
•
Symptom: CMM module fails to come online when Supervisor running CatOS set test diaglevel complete or minimum
Condition: Sup1, Sup2 and Sup3 CatOS 8-2-1
Workaround: Set test diaglevel bypass
•
Symptom: CMM displayed FABRIC ERRORS and will not comes online when plug into a CAT6K chassis that has Sup720-3B/3BXL running either CATOS or IOS.
Condition: CMM currently does not interoperate with Sup720-3B/3BXL VSSO changes. The bootup sequence is different with Sup720-3B/3BXL VSSO support. CMM line card will need to change to this new boot up sequence.
Workaround: None. CMM currently does not support Sup720-3B/3BXL.
Open Caveats in Release 12.3(8)XY1
•
Symptom: Digital signal processors (DSP), mostly in the range of slot#/24 to slot#/31, fail occasionally and a message is printed on the screen indicating it is recovered.
Conditions: This has been observed under regular stress conditions, so far.
Workaround: The DSPs are recovered automatically and reinstated into service. There is no impact to the functionality of CMM. However, any existing calls at the time of the failure, on the failing DSPs, are terminated.
•
Symptoms: CMM failed to come online after the FXS module got upgraded with the new FPGA; it is displayed as <no faulty> when the show module command is entered in the Cisco Catalyst 6000 supervisor.
Conditions: CatOS running 8.8-2-2 CMM configured with mixed T1 and FXS modules, running image version: wscmm-i6s-mz.xy.Sep1 and after reload.
Workaround:
1.
2.
3.
For example:
Console> enableRouter# clear cam dynamic(cr)•
Symptom: Hung fax-relay calls - some calls do not disconnect.
Conditions: After long hours of excessive fax-relay stress in a CAS environment and G.729 is the configured codec, some calls are not disconnected after the fax transmisson is completed. This is seen only in a fax-relay test environment using a bulk call generator.
Workaround: No workaround is available.
Resolved Caveats in Release 12.3(8)XY1
•
•
•
Symptom: One way audio or no audio observed during conferencing calls and transcoding calls through ACT
Condition: Configure loop back interface with Supervisor Native Cisco IOS
Workaround: Shut down loop back interface
•
Symptom: The CMM module cannot ping default gateway (VLAN interface) from the slot 5 in Cisco Catalyst 6K 6513 chassis with Sup720
Conditions: CMM version: all images with Sup720
Workaround: Try moving the CMM module to any other empty slot.
•
•
Symptom:
Without Auto config enabled: When bootup CMM in h.323 config without pri cables pre-connected to the ports, all E1 controllers are still down (lost of signal) after connected cables once module is online and all DSPs are up.
With Auto config: Some of the E1 controllers are remaining shut down when connected the PRI cables after the xml downloaded config on CMM. Conditions:Booup CMM without PRI cables pre-connected.
Workaround:
–
–
•
•
•
Symptoms: DSP time-out errors received in CMM causing the ISDN connection go to TEI_ASSIGNED.
Conditions: CMM is operating in normal conditions, running MGCP with CMM 3.3.3SR4a. Two ports connected to PBX and one connected to PSTN. Controller to PSTN configure as ISDN switch type PRI-EURO. Controllers connected to PBX running QSIG .
Workaround: Reset the controller.
Open Caveats in Release 12.3(8)XY
•
Conditions: CMM version: all images with Sup720
Workaround: Try moving the CMM module to any other empty slot.
•
CSCef76283: One way audio during call with transcoderSymptom: One way audio or no audio observed during conferencing calls and transcoding calls through ACT
Condition: Configure loop back interface with Supervisor Native Cisco IOS
Workaround: Shut down loop back interface
•
Symptom: Digital signal processors (DSP), mostly in the range of slot#/24 to slot#/31, fail occasionally and a message is printed on the screen indicating it is recovered.
Conditions: This has been observed under regular stress conditions, so far.
Workaround: The DSPs are recovered automatically and reinstated into service. There is no impact to the functionality of CMM. However, any existing calls at the time of the failure, on the failing DSPs, are terminated.
•
Symptom: Very rarely a digital signal processors (DSP) fails with dsp timeout messages on the screen and the DSP is not recovered.
Workaround: There is no workaround.
•
Symptoms: CMM failed to come online after the FXS module got upgraded with the new FPGA; it is displayed as <no faulty> when the show module command is entered in the Cisco Catalyst 6000 supervisor.
Conditions: CatOS running 8.8-2-2 CMM configured with mixed T1 and FXS modules, running image version: wscmm-i6s-mz.xy.Sep1 and after reload.
Workaround:
1.
2.
3.
For example:
Console> enableRouter# clear cam dynamic(cr)•
Symptom: Hung fax-relay calls - some calls do not disconnect.
Conditions: After long hours of excessive fax-relay stress in a CAS environment and G.729 is the configured codec, some calls are not disconnected after the fax transmisson is completed. This is seen only in a fax-relay test environment using a bulk call generator.
Workaround: No workaround is available.
Resolved Caveats in Release 12.3(8)XY
•
Symptoms: DSP timeouts after saving running configuration via CLI.
Conditions: Usually seen with high call volume but is dependent on the CPU load and other factors at the time of saving the configuration.
Workaround: Defer saving configuration to a time when the call volume and the incoming call rate are very low.
•
FDL ATT does not work
Symptoms: When a T1 circuit in a CMM (Communications Media Module) is configured for FDL (Facility Data Link) protocol type AT&T, it doesn't respond to AT&T requests.
Conditions: Under normal circumstances whenever 'fdl att' is configured under the T1 controller.
Workaround: No workaround is available.
•
Output statistics for FE always 0
Symptoms: The output statistics for the FE interface are not accounted even though the packets are transmitted.
Conditions: This can be observed when the show interface fast command is entered.
is entered.
•
CMM crash at ms_dsprm_close
Symptom: CMM reloads during regular operation.
Conditions: The CMM reload is followed by DSP Timeout messages (waiting for error stats).
Workaround: No workaround is available.
•
Symptoms: No audio when invoking the CMM conference resource. Unable to ping from supervisor to ethernet interface on CMM module.
Conditions:
- Supervisor image: c6sup22-jo3sv-mz.121-22.E2.bin - CMM image/version: Version 12.2(13)ZP3 - Turn on debug ip icmp on CMM and there was no packet coming in while pinging from supervisor.
Workaround: No workaround is available.
Further Problem Description:
- Ping from supervisor to GigEth interface on CMM is good
- Conference bride/transcoding resource are registered using Gig1/0 interface
- No audio when invoking conference resource
Manual Configuration in the Absence of CMM-Specific XML Files
If you do not have the CMM-specific XML files or do not want to install CMM-specific XML files, you need to perform the following tasks:
Note
•
•
–
–
•
•
The manual configuration is lost on a reload if you set CMM for a configuration download from Cisco CallManager. If you lose the configuration, you must reconfigure. To retain the manual configuration, disable the automatic configuration download from Cisco CallManager before reloading CMM.
Related Documentation
For more detailed installation and configuration information, refer to these publications:
•
•
•
•
•
•
•
•
•
•
Obtaining Documentation, Obtaining Support, and Security Guidelines
For information on obtaining documentation, obtaining support, providing documentation feedback, security guidelines, and also recommended aliases and general Cisco documents, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
