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!

BCM400 3.7 Patch error

Status
Not open for further replies.

morgansdad

Technical User
Oct 17, 2005
163
US
I am trying to load the current patches on a BCM400 3.7, the BCM wizard goes through the motions, performs the system health check and comes back with "The MSC Core Telephony software could not be recognized, check that all sets are functioning" and then stops the patch procedure. All of the sets are working properly. This error happens with all of the 3.7 patches?
 
Log into BCM configuration. Highlight System. Go to tools and Refresh System Inventory. Wait 5 minutes (not the 1 minute indicated). Go to tools, Display Inventory. If the inventory displayed shows as having been generated within 5 minutes of the current time, log out and execute your patch. If not the inventory service may need a kick start.
 
And where would I kick start the Inventory Service?
 
Also, the time on the inventory service was about 3 hours ahead of current time, although the date was correct, and it only listed installed patches.
 
There is a software management patch. Also if you've used any of the wizards at all during the time prior to trying to install the patches you may have corrupted the Hard Drive
 
Is it possible that some of the services may not be running, for example an old patch failed to fully load?

From the main menu (via telnet or serial), select platofrm initialization menu. Select initialize menu. Select option 2 (set service startup to auto). Reboot the BCM and try again.

The software management patch is for BCM 50s far as I'm aware. If wizards corrputer the hard drive, I can't imagine any BCM in existence that would be running properly.
 
Actually, I had that same error a couple times while loading the DST patches on 3.7 systems. A platform initialization fixed the problem on both accounts
 
I remember now. This has been bothering me for days. We had this problem with 4 switches in a row and I couldnt remember what it was. Thomen is right but the Platform Init is to dramatic. The reason the patch wont take is because the MSC Card is not uploaded to the motherboard. Do an MSC Upload from the telset interface and everything should work like butter!!!!!
 
Biv 343
There is a patch portion of a patch for the 200/400 as well.
Also I know from personal repeated experience that doing DN changes from the Wizards before the patches have been applied has caused me great heartache.
 
What would be the procedure for an MSC upload from the telset interface? Never done anything from the BCM telset except f*0 and f*3.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top