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 Westi on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

BCM 400 Upgrade 3.6/3.7 to 4.0

Status
Not open for further replies.

7upp

Technical User
Feb 4, 2008
31
US
I ran the pre check and it Fail MSC Check.The Failure said (KSU version(MSC Core)is [30DiC06] which is Not supported.
I discovered that the log in screen where you put your user and password in shows BCM 3.7. The MSC shows 3.6 Build 2.2. I have the system setup to backup to the customers network once a week. I checked the backup and it says the backup is 3.6. This sytem was upgraded from 3.6 to 3.7 two or three years ago. The key code for the upgrade shows up in the keycode screen. I believe what may have happened is a 3.6 backup may have been restored on this BCM which is a 3.7 system. I'm thiking I may need to Re-initialize the system and repram by hand. I'm looking for suggestions before I go through the trouble of reprogramming from scratch.
Thanks 7upp
 
From my understanding a 3.6 backup wouldn't work on a 3.7. If your system is showing 3.6 build 2.2, to me that indicates your system is still at 3.6. U may have the 3.7 upgrade keycode but was the actual upgrade done via the disks?

Another thought is was the 3.7 HD replaced w/ a 3.6 HD at some point after the upgrade was done taking it back to 3.6?

Is your system fully patched?
 
I'm sure the system had the latest patches before the upgrade from 3.6 to 3.7. Once the system was upgraded it had not had any patches added to it. The drive was replaced do to the system failing the precheck upgrade and the recommendation was to replace the hard drive, so the hard drive ws replced about a year ago. After the drive replacement and the pre-check was ran again and the MSC failure came up. The upgrades were put off until now do to budget reasons. The system was upgraded via disk.
 
When u replaced the drive, did u replace it w/ a 3.6 or a 3.7? If the system had been upgraded to 3.7 and then the HD replaced later w/ a 3.6, your system will now be a 3.6 not a 3.7. HD should've been replaced w/ a 3.7HD if the upgrade had in fact been done a yr prior.
 
Login in to the console menu using Telnet, Putty, or a direct connect to the serial port. See what version shows up there.
Version 30DiC06 indicates the core is at 3.7.

You may also want to dump your Internet Explorer cache.
I've seen some funky things display due to old files in the cache being called up.


-SD-
 
Sounds to me like it just needs a platform initialisation the hard drive and the MSC might be out of sync

If its not broke tweak it..
 
Run into this problem today turns out the core is at 3.7 and the hard drive is at 3.6

It was fixed by forcing a core upload

Telnet into the system

Select option 1
then option 2 MSC upload menu
select the correct core for your area..

Once the process has completed with a nice tune reboot the BCM and your core should now be at 3.6 and the upgrade check will pass


If its not broke tweak it..
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top