Cisco Media Convergence Servers 7816-I4, 7825-I4 (and IBM x3250-M2 equivalent) and 7828-I4 have recently been experiencing technical issues. These servers are used by Cisco Unified Communications Manager and various other Cisco Collaboration software products.
The symptom is that the local disk drives' file-system goes into read-only mode, which can manifest as application services going down, the server becoming unresponsive via the network or the management interfaces, or worst case data corruption necessitating a reinstall and restore from backup.
Root cause has been identified by Cisco and its suppliers as a disk drive issue stemming from interaction with system firmware.
Field Notice 63374 has been published and includes more technical details regarding this issue. Cisco and its suppliers are committed to high quality and apologize for any disruptions or impact caused by this issue.
The file-system going read-only issue which has recently been affecting server models MCS-7816-I4, MCS-7825-I4, and MCS-7828-I4 (or their IBM equivilants) in the field is addressed by CSCti52867 - "IBM 7816-I4 and 782x-I4 READONLY file system".
The fix for CSCti52867 is now available and requires the application of two patch files. Install both of these patch files in the order listed below.
This installer is completely independant of the OS installed on the server.
Note: Installing the FWUpdate v3.0(1) or later will get you firmware with the fix for this defect. It is always recommended that you apply the latest FWUCD available for your server.
Refer to the Release Note of CSCti52867 and the Readme file for each of the above mentioned patch files for more details.
The file system goes READONLY, then CUCM services may go down, the server may become "unresponsive" meaning that it is not possible to ssh into the server, login to the console, or web into the server although it may still respond to pings.
Traces from all services stop writing (including syslog)
You see the following error on the server console
EXT3-fs error (device sda6) in start_transaction: Jornal has aborted
If you are able to login to the server via SSH, the following output may be displayed.
Last login: Mon Aug X XX:XX:XX XXXX from XXX.XXX.XXX.XXX
Command Line Interface is starting up, please wait ...
java.io.FileNotFoundException: /var/log/active/platform/log/cli.bin (Read-only file system)
at java.io.RandomAccessFile.open(Native Method)
log4j:ERROR No output stream or file set for the appender named [CLI_LOG].
Welcome to the Platform Command Line Interface
The /common file system is mounted read only. <<<<<<<<<<<<<<<<<<
Please use Recovery Disk to check the file system using fsck.
How to determine the current version of firmware on the hard drive
For MCS-7825-I4 and MCS-7828-I4, running Cisco UCM 7.1 and above, you can use the CLI command 'show hardware' to verify the firmware version.
HW Platform : 7828I4
Processors : 1
Type : Intel(R) Core(TM)2 Quad CPU Q9400 @ 2.66GHz
CPU Speed : 2660
Memory : 8192 MBytes
Object ID : 126.96.36.199.188.8.131.52.899
OS Version : UCOS 184.108.40.206-34
Serial Number : KQRBVVB
RAID Version :
Raid firmware version: 1.26.81.00
Raid Bios version: 6.16.00.00
BIOS Information :
IBM IBMBIOSVersion1.44-[M9E144AUS-1.44]- 06/11/2009
RAID Details :
LSI Logic IR Configuration Utility 2.00.15
Read configuration has been initiated for controller 0
The text highlited in red are the info you need. This output shows a server with two drives with model number WD2502ABYS on 3B04 firmware. These drives should be upgraded as soon as possible.
For MCS-7825-I4 and MCS-7828-I4 models running Cisco UCM versions previous to 7.1, as well as any version of Cisco UCM running on a MCS-7816-I4 model server, you must download and boot off of a CD burned with Cisco-HDD-FWUpdate-3.0.1-I.ISO (refer to the "Solution" section for links to download the ISO and readme). Upon successful boot of the Cisco-HDD-FWUpdate-3.0.1-I.ISO CD, you will be presented with the current HDD FW version as well as the opportunity to upgrade to HDD FW version 02.03B06.
What should be done if filesystem issues persist after applying the patches?
As of 16 February 2011 if you encounter any further filesystem or hard drive issues after applying both the firmware and disk exerciser you should proceed to replace the affected drive(s).
There are three ways you can replace the drive(s).
If you have an MCS server with an active Cisco support contract open a TAC service request.
If you purchased the IBM x3250 M2 MCS equivalent and have an IBM support contract contact IBM support.
If you do not have any support contract for the server you can purchase a new drive from Cisco or IBM.
The Cisco part number for the hard drive is HDD-7825-I4-250=.
Contact your IBM reseller to confirm the correct part number for the 250GB SATA simple-swap HD for the x3250 M2 server.
If you have any questions you can leave a comment on this document. The firstname.lastname@example.org email address is no longer active as of 1 September 2014.
Sending the email will not generate a TAC SR but will allow us to collect more information. This is an informal submission with no associated SLA and we will make every effort to follow up submissions but cannot guarantee a response.
Greetings, I am having problem with registering SIP Phones 7811, 7821 series.I got some SDL logs from the CUCM and the error I am getting after I try to register the phone with a secure SIP profile and install/upgrade the LSC is this: SIP/2.0 40...
Hi, we currently have the Nuance Management Station 5.x suite and looking to get away from Nuance. Does anyone have a recommended UCCX 12.5.1.X ASR/TTS vendor solution other then Nuance? I found LumenVox but not familiar with this vendor. T...
Hello, I was asked to provide a solution for following scenario---There are 2 DIDs -1111 and 2222. Create a hunt group for calls to 1111 and if all agents are busy, queue the calls and play a message after 1min saying someone will be with you shortl...
This is my first time being part of a deployment where we are using a VVB instead of VXML gateway. With bootstrap, ringback and error tcl configured on VVB, do we still need to define the service application for them on ingress CUBE along with dial-peers ...