Another (hopefully last) Migration question

[MitelInMyBlood]

At the 11th hour we've been asked to add the processor expansion kit (add 2nd processor and echo canceler) physically not too challenging. OK it's in there. Now when I boot it up the 2nd processor (for E2T) is grabbing an address (from the scope) that I don't want to have. I want to hard code it to reuse the same E2T address as the old LX.

This is the same E2T address that the data restore process is currently putting in the DHCP Static address location, tho a reboot ignores this and grabs yet another address for the added controller.

Do I need to go into the E2T programming (secure telnet to port 2007) to fix this? I'm thinking I do.

 

[kwbMitel]

Yes and no worries.

Hardcoding the Expansion E2T will not affect the restore 1 bit. The DHCP scope option is redundant and only good for record keeping afterwards.

Hardcoding is done via port 2007 as you've noted.

The LX requires the Tapi Cable if you plan on re-deploying the LX as a resilient controller or some such.

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[MitelInMyBlood]

That's what I thought. Just need some reassuring. The old LX after a couple weeks of holding onto it just-in-case, will eventually be going to the band saw and then to the recycler. (I'll keep the old HD and MMC cards)

 

[kwbMitel]

Keep the SysID as well, you never know...

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[MitelInMyBlood]

Good point. Can't begin to count the number of old 2K sysid's we've been able to leverage.

 

[kwbMitel]

Mitel might actually offer trade in on an LX chassis once Rev X comes out. Again, you never know...

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[MitelInMyBlood]

Getting "Can't Load Boot File" error on e2t Have seen that before long time ago, but don't recall the cause. E2T seems to be looking for an address in 192.168 something, but all that was changed. we're using 10.x.x.x addresses.

 

[kwbMitel]

double check the IP Address on the E2T, then check again. only slower. Make sure your seeing what's actually there and not seeing only what you expect. (I do this too often to count)

If Port 2007 is no longer responding you may need to follow this proceedure.

Telnet to port 2007
Login
If prompt is not ->

In new Window
Telnet to port 2002 (RTC Shell)
Login
-> ToggleCpu 1 (reboots E2T)

Observe original window (Port 2007) and stop reboot at appropriate moment.



*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[MitelInMyBlood]

Never mind

0x0 (in the bootline)

Duhhh.....

(default ox40)

 

[kwbMitel]

As I said, I've done it too many times myself.

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[MitelInMyBlood]

Yup, me too. Last time I had to hard code an E2T it was on the LX that is the target of this same replacement effort. Duh. Burned twice on the same problem, same site though a few years apart. Need to stamp it in braille on the front of the chassis.

Data restore from last night came up on the new box OK, so I'm planning to swap it out tonight. Thanks again.

 

[kwbMitel]

Ironically, it was hardcoding an E2T on an LX, (and doing it wrong)that initially led me to this forum. It was your FAQ on the TAPI cable that saved me.

Order is now restored to the universe.

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[MitelInMyBlood]

What goes around, comes around.

 

[MitelInMyBlood]

Pulled the trigger last night. Up & running, all is well. MOH comes from a universal ASU, had to power cycle the ASU a couple times to get MOH back.

QSIG to the Cisco CM came up OK.
Phones up (bumped the POE)
Did the upgrade bootrom thing for the new E2T card

Life is good
Thanks again