Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

3300 MXe crashes due to Hyper-V server having Teamed NIC's

Status
Not open for further replies.

cknipe

MIS
Jul 28, 2005
597
US
Is there anyone else out there running virtualized servers using the Hyper-v platform? We have had an issue with random reboots over the past few months and just this week, it started happening more than once a day. There was nothing to indicate anything was wrong with the 3300 in the logs, just an enourmous amount of duplicate IP address detected messages in the logs. The duplicate IP addresses did not conflict with any mitel equipment at all. We found that when he had the Nic's "teamed" or bonded on the server with both nics using that 1 ip address, we were constant filling up these logs with these messages which was causing the system to become unresponsive. has anyone else ran into this issue? After we unbonded or un "teamed" the NICs the random reboots stopped.
 
What type of server had the nics bonded?
Was it a Mitel application?
There are quite a lot of rules on different Mitel application servers regarding teaming

Share what you know - Learn what you don't
 
I forgot to mention that our pbx is a mitel CX running MCD 4.1

On the server side, one of the servers was Your Assistant. The other server was a non mitel server, just thier local backup server. No other network monitoring software was recieving these types of alerts for duplicate IP.
 
teaming in the nics causes the two nics to have one IP however you still have two mac addresses.

I would imagine the reboots occured as the logs being generated were too much. 3300 picked up the same ip with two diff mac addresses.

I've seen this before too but not sure how to fix. either disable duplicate IP warning in Mitel or get Mitel to understand teamed NICS.

maybe a DCR in the making?
 
was the YA server NIC's teamed?
This is not supported.

Share what you know - Learn what you don't
 
yea it was on the YA server.....but even after we unteamed (acutally we powered off the server and left it off for a day first) it. we still had another reboot occur because the backup servers teamed nic was filling up the logs with the duplicate ip messages. We still have a few duplicate IP messages from other servers but nothing like what we saw the other day. Now we are seeing 1 every 3 or 4 hours while the other day you would see 400 pages of the same message fill up the log in a matter of 1 minute or less (followed by a reboot of course). I know I had seen these messages in the log in the past but just as many as I had seen that day
 
leading up to this we would have a random reboot maybe once every 2 months. Being a small site we were not worried about the reboots until last week when they started occuring multiple times in a day. Im starting to think that the older reboots were probably caused by other duplicate IP messages filling up the logs at a slower pace than what I was experiencing last week.
 
very odd that this backup server should have an affect like this.
unless both nics were plugged into the same switch
normally teamed nics each nic would connect to different switches as connecting to a single switch could cause a network loop


Share what you know - Learn what you don't
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top