On our test lab, we upgrade a 2 MC7845 (pub/sub) from 4.x to 7.x, then pulled a Raid1 drive to simulate a failure. This crash our subscriber which requires a rebuilt. We pulled it base on assumptions from CCO docs for 4.x and earlier. I started looking for a cco doc on the "correct" procedure on 5.X and above but could not find it...so my question is:
1. Is RAID 1 support meaning I can pull a drive out while is it live and subsequently put in a spare drive?
2. Can anyone find the cco doc to recover because with 4.X there was that F1 or F2 choice on reboot.
I can't answer your question, but wanted to pass something along that we came upon a few weeks back. In preparation for an upgrade we had a Raid 1 mirror on an old 4.X box (MCS78XX-I - IBM server Cisco branded). Pulled the second drive, shutdown the box, pulled the first drive, plugged the second to make sure it would come up - so we could use it as an escape route. When we inserted the second drive back in and tried to boot, the server said the drive was bad.
Turns out that some of the IBM servers will remember a drive failing and they will flag it bad AND REMEMBER even when it is put back in and is in fact fiune. If this is the case you need to find the original CDs that came with the server, put in the raid CD, run the utility and tell it the drive is OK.
Cisco only supports replacing failed hard drives. Cisco does not support drive pulling/swapping as a method of fast upgrade reversion, restore, or server recovery. For information on replacing a failed hard drive, refer to the Troubleshooting Guide for Cisco Unified Communications Manager.
I don't think there's any contradiction here, upgrades are not supported with 'pulled' drives and but failed drives can be replaced without a restart. In order for the drive to be pulled the CUCM OS must mark the drive as failed.
From the link you posted
The following procedures do not apply and are not supported if you attempt disk replacement for a disk that is not detected as failed per the following procedures.
Step 3 Enter the CLI command,show hardware, again and perform one of the following:
–If none of the physical disks displays the status as "Failed", you need not perform any further action.
–If the logical drive status is not OK or Optimal, and any physical disk is displaying as "Failed", identify the physical disk on the server as follows.
Perhaps pulling a disk isn't isn't the best way to simulate a drive failing in this case.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...