Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

BCM 200 3.6 Alleged HD Failure. No Backup.

Status
Not open for further replies.

QLand

Technical User
Nov 26, 2004
10
DM
Hi everyone.

Our company has a BCM 200 release 3.6.

Telephony functions work fine but unable to access the network incomming or outgoing trunks. All the LED's are flashing with the exception of the fan, temperature and power.

The function tray has been changed and also the back plain of the unit to verify that these aren't the cause of the disaster.

I can't access the BCM via the Ethernet nor the serial interface, but when adding a terminal to the bcm vga port I see the boot-up process go as normal.

I removed the hard drive from the bcm and scanned all the drives on a Windows XP PC using Chkdsk. I found no errors.

I figured that it's maybe the OS on the disk that may have become corrupt or something to that eefect. Another hard drive was added (3.6) and that works via the serial cable and 10.10.10.1 can be pinged via the ethernet cable (but can't login).

Having said all that, the problem that I'm faced with is that a back-up has not been done since we've been using 3.6
one was done only a few months ago when we were using 3.5.

What i would like to know is if by initiallising this new 3.6 hard drive would it be possible to move the key configuration files from the old hardrive accross without having to program the whole system all over again. And if so
what would those key files be. We don't use voicemail on this BCM.

Any help would be appreciated
 
It would be quicker and safer to just INI the system and progran all new.

Why change the engine if all you need is to change the spark plugs.


 
If you don't use voicemail on that system, you can put in a new 3.6 hard drive, run a platform initialization, set your IP address, then re-enter whatever keycodes you need. The telephony programming will stay on the MSC card. If you have IP phones or IP trunks, you may need to reprogram those, but you shouldn't have to rebuild the telephony side of the system.
 
The sys ID is on the MSC so just retrieve keys for the same ID and re-enter
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top