Opt 81 rls 25.40 ld 137 not invoked during mids

[dualbags]

All

I have an older switch that is only accessible remotely. Site opened a trouble ticket because cores werent swapping during midnight routines. I went in and looked around and ld 117 had incorrect IP address for inactive core so I fixed that. I edd'ed.
I looked at ld 137 stat and rdun was disabled (it disabled after i changed Ip address- it was up prior to the change). so i data rdun and everything was peachy keen.
stat elnk was fine - it was up, ld 48 stat elan is fine.
so i went into LD 135 and invoked mids and it still wont run ld 137. it completely stops after ld 135.
so i swapped cores and cant see the other side due to a bad transceiver on that side.
anyone see this before?
could it be a bad CP II card or something?
You can swap cores manually just fine - it just wont invoke during mids.

thanks
tia perry - avaya gov solutions

 

[johnpoole]

what is the transceiver used for? seems a little old for cp or symposium.. you could have added those to that rls, but just barely..

replace the transceiver. when the active side sees the bad unit, it will not force it over.. i assume, since the ip was bad and you did a scpu, the ip side is not in service.. the box doesn't know that...

john poole
bellsouth business
columbia,sc

 

[bhassell2000]

is ld 137 in the mids in ld 17 OVLy data?

Thanks,

Buddy

 

[dualbags]

in case anyone was interested - I think i found the issue.
CP II core cards have LAN 1 that has a cable to jack 31 in the back of the module. Lan 2 gets connected to the other core module CPII card on LAN 2 with a cross over cable.
When Lan 1 Core 1 is active it can be pinged and I can get into remotely via ELAN. When core 1 is active- the active IP address for the switch is no longer pingable.
SO we have a bad ethernet cable, a bad ethernet hub port (possible wrong speed set up) or a bad CP II LAN 1 jack for COre 0.

thanks for the return replies.

tia perry
avaya gov solutions