IP Trunks Down--They won't bounce back up

[extreme4x4mt]

Hi all,

One of my IP trunks have just gone down between location a and location b. I have done the following but the trunks will not come back alive.

busy trunk 23 on both ends
release trunk 23 on both ends
busy sig 23 on both ends
release sig 23 on both ends
test sig 23 on both ends

results for test sig are:
TEST RESULTS

Port Maintenance Name Alt. Name Test No. Result Error Code

23 H323-SGR 1386 PASS
23 H323-SGR 1392 PASS
23 H323-SGR 1387 FAIL 1007


Test result 1387, error 1007 says "1007
PING to the destination failed through this port because the
destination was down."

I've verified that the point to point line is 100% functional.

Any ideas on getting these to come back up?

Thanks all for your help.

Mike

 

[BuckWeet]

make sure you can ping the clans and medpros from each end..

and make sure the node-names are correct for the remote switch..

BuckWeet

 

[extreme4x4mt]

Update on resolution

I brought AVAYA in on this to get it fixed as it's covered under my 8x5 maintenance contract with them.

busy trunk 23 on both ends
release trunk 23 on both ends
busy sig 23 on both ends
release sig 23 on both ends
test sig 23 on both ends
reset packet-inter 2

We tried the commands above with no luck and ultimately reseating the CLAN card at the remote office worked. Strangly enough, immediately after reseating the CLAN card, our T1 internet connection went down and we had to reset our firewall to get it to come back up.

In preliminary testing, it was noticed that when doing a trace route from the remote PBX to the main PBX via the remote PBX, the traffic was trying to route to 6x.xxx.xxx.xxx IP address which is extremely wrong. That would possibly explain why the firewall to the internet had to be rebooted.

Has anybody ever seen anything like this? It's like the CLAN had a bad route and was trying to route traffic over our internet connection instead of the point to point.

 

[cduff]

I have seem this before and it sounds like a network issue display your signaling groups for each side and map on paper out how they route from clan to clan.
Next display node-names IP to get the IP address and then do a ping test ( ping ip-address 10.51.71.151 board 1c18 ). make sure each end sees eye to eye if they don't it could result with the issues you are experiencing

 

[extreme4x4mt]

You know what's weird about this is that when it's up and running, which is 99% of the time, it works as advertised and you would never suspect anything is mis programmed or setup incorrectly. Then, out of the blue, it's trying to route out over our internet connection via 6x.xxx.xxx.xxx which is the external interface on our router going out to the internet.

I'm supecting CDP, RIP, or IGMP or some ARP wars but we aren't running CDP, RIP, or IGMP. The features are turned off and we're running static routes everywhere. So, that just leaves an ARP war to suspect I guess. Next time this happens, I'm going to unplug the ethernet cable from the back of the CLAN and see if it starts working. That would be enough to clear the ARP table and maybe kick it in the right direction.


I'm going to get all the firmware upgraded on my clan and medpro boards soon and hopefully the problem will go away.

Thanks for you help

Mike

 

[hoffdog]

I had the same problem earlier this year... Busy out all your sig groups and trunks then use the "refresh ip-route all" command then release them... it worked for me and I hope this helps you out.
Ed