possible faulty port on the IPO?

[MandyDroid]

I have been experiencing an intermitent problem wiht one of my IPOs. It seems that every now and then that packets on my local switch seem to be delayed instead of the nomrla 1 - 3 ms delays it spikes to 350 - 1200 ms delays that casue very bad voice connections. Teh problem is not in my WAN connections as the packets to fluctuate in roudn trip accross my WAN it is specifically on my LAN. I have further isolated that it only happens to my IPO not other devices connected to the same Cisco 3750 switch. All other ports respoind at <1 - 1 ms roudn trip delay.

I have also moved the physical port of the IPO and the same result is occuring. Does anyone know how I can begin to trouble shoot this issue? I feel it can be the IPO failing in some way but I do not know how to begin to investigate this issue.

Avaya, Panasonic, Polycom, APC, MCP, A+, CCENT
##################################
"When I was a child, I spoke like a child, I thought like a child, I reasoned like a child.
When I became a man, I gave up childish ways.

 

[intrigrant]

I would start off with a monitor trace were my PC is connected to tha other LAN of the IPO and trace the network of LAN1
See if you have ip conflicts on ports used by IPO
I have had this once were a switch had the same ip address as the ipo but only the tftp option of that switch was active so the switch reacted on tftp request which were meant for the ipo, the ipo got really confused and the LAN sometimes stopped reacting on all traffic for upto three seconds.

A simple mind delivers great solutions

 

[DrDrayAvaya]

that's a goodie Intrigant! on a similar angle, we had some VPN users that were being dished out dynamic addresses from a pool that overlapped with the IPO LAN1 address...
caused by different IT managers and lack of documentation etc, original installers of that IPO had given up trying to fix the fault. took 3 visits to catch it.
unplug the IPO and ping the IPO LAN1 addy, see if you get a response!
what we found was the ping time got gradually bigger when they were both on the LAN.

Just another thought anyhow,

Cheers,

Chris

 

[intrigrant]

This is a common issue which can be from any source and hard to tackle.

A simple mind delivers great solutions

 

[DrDrayAvaya]

sure gave me some grey hairs! the symptom our client was complaining about was voicemail stopping all the time! and rightly so, nothing else was connecting to LAN1, no PMP, IP Phones etc, so no other symptoms... it would just show as not binding

fun times!

 

[tlpeter]

That could also be cause by a wrong DHCP server setup on the IPO.
Mostly people set the IPO to 192.168.42.1 and the VMPro to 192.168.42.2 (example) and then DHCP turned on starting from 192.168.42.2
The IPO does not check if that IP address is free and when you dial in and you get the 192.168.42.2 then VMPro will stop working.
Seen it happening


BAZINGA!

I'm not insane, my mother had me tested!