Virtual IPO Packet Loss 1

[liquidshokk]

Users are reporting robotic sounding speech and call dropouts on virtual IPO 10.0.0.2 on internal and external calls. High packet loss being reported in wireshark trace of the IPO VM interface but not other VM's on the same server.

Bandwidth on voice VLAN very low and packet loss experienced out of hours when system unused.

118701 packets captured
121234 packets received by filter
2525 packets dropped by kernel

System status reporting packet loss of up to 40% intermittently throughout the day but not all calls. Cannot see anything untoward in monitor and have logged with Avaya, but just wondering if anyone else has experienced similar issues with virtual IPO??

 

[rdoubrava]

What kind of Virtual Server?

 

[liquidshokk]

It is a customer managed server, All I know is it is VMWare vSphere hypervisor (?)

 

[rdoubrava]

What version of vSphere ?
We have an SE on vSphere 5.5 and a R10 on 6.0

 

[janni78]

Is this a VMWare server that the customer built themselves?

It could very well be a configuration/hardware issue, but I don't know what hardware this is running on, how many servers it is running, what kind of servers and how it's configured.

"Trying is the first step to failure..." - Homer

 

[liquidshokk]

I'm waiting for the customer to confirm re spec, but as a test they have picked up the VM and moved it to another virtual server (Xen hypervisor) Since doing that we are unable to access the configuration as it keeps asking for the passwords to be set but won't save them! Guess this is normal behaviour as it doesn't like being picked up and moved??

 

[liquidshokk]

I was able to reset the password using the Web GUI, however there are now alarms saying that the system ID has changed. How do we go about getting the licenses valid again?

 

[Pepp77]

That would be a licence swap with your disti or on PLDS.

| ACSS SME |

 

[John563]

On the VMWare server, I would have checked the CPU co-stop and ready values to see if they were high. If they were, you could set the CPU shares to high and/or reserve CPU. I believe the documentation currently recommends reserving about 70% of the total MHz (Cores assigned x core speed.) Keep in mind that the new hypervisor they are using is not supported by Avaya.