weird ipsi problem 1

[nohuhu]

colleagues,

got a real strange one here. i'm now installing a new s8730 cm5 system, high availability with duplicated ipsi boards and ethernet switches. the problem is, ipsi in cabinet A can't get ip address from either of the media servers, while ipsi in cabinet B works fine. swapped 'em, same thing. swapped backplane connectors, same thing. swapped 'em switches, no go. connected offending ipsi to the customer network and assigned it ip address manually -- all green, i can ping it and telnet onto it, so its network interfaces seem to be working. placed it back into control network a, assigned it ip address manually -- no go, can't ping either server, ipsi doesn't register and seems like it doesn't see the network. from the tdm side everything is fine, all tests pass. there are two alarms related to that situation: PKT-INT err type 1 and 257 but i guess that's because ipsi is out of service.
well, i'm lost. can't imagine what make ipsi behave that bad. any thoughts?

 

[Mitch672]

We have had a bunch of defective IPSIs lately, most of the problems have been tone/clock related, or static on phone calls, but several have failed. I wouldn't kill yourself looking for the issue, it might just be a bad one. Call your distributor or open a case with AVAYA and get it replaced

mitch


AVAYA Certified Specialist

 

[nohuhu]

Mitch672,

can't be bad one, they behave exactly the same way when i swap 'em. i mean, one in B cabinet gets ip address and works like charm and one in cab A doesn't. swap 'em, same thing: cab B works, cab A does not.

 

[lopes1211]

I ran into a mislabeled carrier once. That made the ipsi 1 slot over from where it was supposed to be.

-CL

 

[nohuhu]

lopes1211,

you mean it was in a02 instead of a01? not my case, list conf all shows it in the right place, a01 with correct hw and fw vintages.
i dunno, maybe that's an error in server configuration? maybe something in control network a settings? i tried to connect this ipsi to the customer network and assigned it ip address manually and it seems to work -- it's just control network a that it doesn't see. checked every settings page i could think of, all green. real weirdo, this one...

 

[Mitch672]

run through "configure server" aagin on both S8730's, perhaps CN-A didn't get setup correctly. You can also do an "ifconfig" on each S8730, to check the "eth?" interfaces, and you can also try a "pingall" via the linux prompt as well.

You do know the LAN interfaces are all in different places on the S8730, its nothing like the S8720.

view from the rear:

upper left: eth5 (unused)
lower left: eth4 (Corporate LAN suaully)

upper right: eth3 (CN B usually)
lower right: eth2 (CN A usually)

center top: eth1 (services usually)
center bottom: eth0 (duplication usually)

mitch


AVAYA Certified Specialist

 

[nohuhu]

Mitch672,

you're the man! you're right and the installation diagram that came with media servers is wrong, so i confused duplication link with control network a. no wonder i couldn't find it... switched 'em right and now everything's fine. thanks a lot and have your star.