Minimum TCM3 Versions on the Acme Packet 3950/4900
The SBC uses the TCM3 module on the AP3950 and AP4900 platforms. The TCM3 vendor periodically releases these modules with upgrades, including new memory. TCM3 operation on the SBC is, therefore, dependent on SBC software version. You must ensure compatibility between TCM3 and SBC software. Oracle provides you with multiple means of verifying software and TCM3 compatibility, including ACLI command output, SNMP traps, alarms and log messages.
Older SBC software versions does not operate properly with new TCM3 memory, but does allow the TCM3 cards to boot. Furthermore, system behavior when you use older software with this new memory is unpredictable. New SBC software provides backward compatibility, supporting both the most recent as well as the older TCM3 memory operating on the same SBC.
See the Transcoding section of your version's Release Notes to see the specific TCM3 cards supported by your software.
If you have booted the SBC to a version that does not support the correct TCM3 memory, the system persists with informing you of this incompatibility using several mechanisms including printing an incompatibility message to the console and SSH sessions every time you press the Enter key.
TCM 5 (Options 2) is not supported by Transcoding Vocallo 05.04.03-B571-PR (HDT=01.07.01-B1898) (aid:xxxx, tid: tttt)Additional means of verifying TCM3 support are presented below.
Applicable show Commands
The SBC provides two show commands, including show xcode dbginfo and show xcode xlist, that provide information from which you can determine TCM3 status.
The output of the show xcode dbginfo appears as follows.
Oracle# show xcode dbginfo
07:43:21
TRANSCODING SUPPORT:
Octasic DSP firmware version : Vocallo 05.04.04-B591-PR (HDT=01.07.01-B1898)
Startup Time : 2023-02-02 20:34:48.114
Last Clear Time : 2023-02-02 20:34:48.114
Last Read Time : 2023-02-08 07:43:08.174
Current Time : 2023-02-08 07:43:21.559
Up Time : 5 Days, 11 Hours 8 Minutes 57 Seconds
-- Life Time -- -- Recent --
PktApiStats:
OpenConnectionCnt = 12
OpenSessionCnt = 12
TotalPktSentCnt = 144 72
TotalPktRecvCnt = 32943 88
… Note:
The Hardware Debugging Toolset (HDT) and Vocallo version are system software components.The output of the show xcode xlist can provide insight into TCM3 module status. The state row displays operational TCM3 modules as ‘Active’ and presents the string ‘Boot Failure’, which can be a result of TCM and SBC software incompatibility.
Oracle# show xcode xlist
09:39:17
TCM DSPs #Sess Load State
=== ==== ===== ==== =========
00 1 0 0% 1 Active
01 1 0 0% 1 Active
02 - - - 1 Boot Failure
03 1 0 0% 1 Active
04 1 0 0% 1 Active
05 - - - 1 Boot Failure
06 - - -
07 - - - Applicable SNMP Trap
The SBC generates an SNMP trap when the TCM3 modules are not supported. The system uses the generic HARDWARE_ERROR_TRAP trap to notify you of this failure. The trap string appears as follows.
DSP Boot Failure.Applicable Alarms
The SBC generates an alarm if the BOOT FAILURE has occurred due to unsupported TCM3 modules. The system uses the generic BOOT FAILURE trap to notify you of this failure. The trap string appears as follows.
DSP#2 Boot Failure!The system only generates this alarm the first time it detects an unsupported module regardless of how many unsupported TCM3 modules are present. The system also presents this alarm when you run the display-alarms command.
Applicable Logging
The SBC writes log messages to the log.xserv file when it detects both supported and unsupported TCM3 modules. The system generates either a supported or unsupported log messages for each installed TCM3.
There are two versions of this log message. A successful log message appear as follows.
Apr 25 14:55:43.328 [XSERV] (0) [NOTICE]
Vocallo 05.04.04-B591-PR (HDT=01.07.01-B1898) supports Options 0 (TCM-4)
An unsuccessful log message appear as follows.
Apr 25 14:55:43.328 [XSERV] (0) [NOTICE]
Vocallo 05.04.04-B591-PR (HDT=01.07.01-B1898) does not support Options 2 (TCM-5)