BCM400 4.0 to BCM450 6.0 migration failure 2

[Straggle]

Interesting happenings tonight.

Tried to do a BCM400 4.0 to 450 6.0 migration tonight, and failed. I followed the guides exactly: Patched current, applied keycode of UM seat to allow DMM to run, ran backup to my PC, ran DMM tool to export config, prepared the DMM file for application to the 450, proper system shutdown, step-by-step through the hardware replacement (fan, new interface card, new BFT, new HDD), then powered it up.

Once power was applied there were lots of lights flashing (all the status lights on the DSM32+ MBMs were flashing red, all the lights on the 3 PRI cards were dancing), but nothing was working; the PRIs wouldn't sync, the digital stations wouldn't come up, and I could not log in to Element Manager (though the system did 'reply' to pings while I was connected to the OEM port).

I left it to 'boot up' for about 30 minutes, hoping for a miracle...which didn't occur. I then reversed everything (except the patches and keycode application) that I'd done and restored full service via the BCM400 4.0.

Anybody have any advice to offer?

 

[telcodog]

Had the same thing happen to me once. It was a defective BFT. Replaced it with a spare and the system came right up.

 

[Straggle]

That's interesting, telcodog. I was thinking it could be the HDD, but couldn't think of any way to test that.

Anybody got a spare BCM450 BFT I can borrow?

 

[bluemr2]

The upgrades come with a multi image hard drive. Did you connect to the bcm and prepare the hard drive for the correct software?

 

[Straggle]

Bluemr2, I installed the drive in the left hand most drive slot, and powered it up. After I did that I was unable to get the OAM or LAN ports to let me get into anything.

Where would I have gone to prepare the drive?

 

[bluemr2]

While connected to the OAM port, start a PUTTY session to 10.10.11.1. Follow the prompts to select which version of bcm you are running. It will install the correct version of software, and delete the others.

 

[Straggle]

Interesting that they didn't put that into any of the Avaya guides I was following.

So not doing that would have had the effect of not letting the BCM boot up like I'd expect, and make all the lights flash incessantly?

What would I look for to indicate that it might be a bad BFT like telcodog experienced?

 

[bluemr2]

It says in the upgrade guide to "prepare" the hard drive. I needed to look in another manual to find out how to prepare it. It took me a couple hours to figure this out. You need to have the correct software on the hard drive before you can make any determination on the BFT.

 

[telcodog]

Not every upgrade comes with a multi-image drive. Check the box the drive came in, if it says multi-image, do what bluemr2 says. If it doesn't, it will be the BFT.

 

[Straggle]

Ok, I've finely made time to run these tests on my shop BCM400...and sure enough, once Putty was connected to 10.10.11.1 while I was plugged into the OAM port, the BCM450 R6.0 was installing within 5 minutes.

Good call Bluemr2!

 

[Straggle]

Hey bluemr2, went on site to install the upgrade in the cust equipment and failed. Called the equipment supplier and they said that there was a "known issue" with the HDD. So Avaya recalled it, I sent it to them, and they just got my replacement to me yesterday.

I get to my shop BCM400, throw in the replacement BFT and the new HDD, and try to Putty (using Telenet, SSH, and Serial) through the OAM port and the LAN1 port, as well as the serial port, and cannot connect to it. (Using both a straight-through and a crossover cable).

Would you be so kind as to give me a dummy's guide to PUTTYing into this drive? Please assume I'm the very definition of a dummy (as this is still my first BCM400 to 450 upgrade.

Thanks a million,
Chris

PS. If you'd like to save the time used to write this out and just call me, shoot me a private message and I'll respond with my phone number.

 

[SupportDude]

OAM Port by default is 10.10.11.1.
Change your PC IP to 10.10.11.2.
Subnet mask is 255.255.255.0.

Use a cross-over cable to the OAM port and make sure you can ping 10.10.11.1.
Open Putty, select SSH, input the BCM IP of 10.10.11.1 and click open.

HTH!

-SD-

http://www.mysupportguy.net

 

[dibthree]

I use the serial port. Null Modem cable female-to-female 8 none 1 baud 115000.

The first one of these got me too. I thought I had an expensive toaster.

Having to set the software release is something I have never seen in the doc's but maybe I have overlooked it.

I like connecting with a serial cable because I can see what is going on and do something before the linux kernel starts the NICS.