IP In use

[AH64Armament]

recently upgraded a 3300 CX controller to 9.0.3.15... since then, we are having PC's with a duplicate IP error... and telephones that aren't coming up... they constantly reboot until they eventually come up.
The phone display shows some semblance of "DHCP using option 125 offer 1 ACC" and hangs there till it reboots itself.
We have gone and hard coded the phones into VLAN 14 (the voice VLAN) and they came up fine.

The system logs are flooded with errors similar to the following...
*****
Possibly 2 computers with the same IP address (172.20.3.129).One of those computers has MAC address 00:13:20:93:d6:cc.If this IP is used by the Mitel RTC card, E2T card, a phone or router, there may be disruption in telephone service.
*****

I've scanned the network for DHCP servers using SolarWinds port scanner... looking for port 547. The site has two items that show up in the voice subnet and one that shows in the Data...
The Data shows as the Adtran router, and the voice shows the phone system and the adtran... I've checked the Adtran, and there are no scopes built up, but the router will always respond to the port request. It could also be the IP helper-address responding to it - in any case, it's not running a DHCP server.

I've checked and triple checked the DHCP settings in the controller and don't see anything that could cause this... I've even re-built the DHCP option 125, just to ensure that it was done correctly.

I've opened a ticket with Mitel tech support, they looked at the controller too, and couldn't see anything wrong.
They suggested that I do a wireshark of a PC that's having the problem to see what might be happening. I'll be doing this tomorrow.

Just to play it safe, I've even upgraded the firmware on the HP switches to the latest - they are 2626 and 2650's.

Has anyone seen this?
sorry to be long about this...
- Mark

 

[kwbMitel]

What device is providing the original DHCP offer.

I suspect the VLAN option is set to 14 instead of 0E (Hex required)

For the duplicate address issue, is it always the same address? I've had several of my customers install redundant switch gear for critical servers and routers that are programmed with the same addresses. There is a method to prevent them from responding to ARP? requests that will make your system happier.

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[RossBC]

be aware that the procurves have dhcp-relay on by default. telnet to it, type "config" and enter "show dhcp-relay" to confirm.
enter "no dhcp-relay" to disable and then "write memory"

would need to know a bit more about your config.

how are the phones learning they should be on vlan 14, data dhcp options or LLDP?

if data dhcp options, then is that server on a procurve port that is untagged data/tagged voice. some NICs are vlan aware and the data dhcp server can be responding on the voice vlan. make sure the data dhcp server is on a procurve port that is data only - no access to voice.

 

[AH64Armament]

KWB - the DHCP option is in the 3300 itself and we are using option 125... it uses clear text... I doublechecked this as well as having Mitel tech support look at it. I only wish it was that simple - windows server kicked us on that mistake a couple years back.

No redundant equipment..

Yes the IP addresses in question all appear to be the same each time... there are several in question, but they are always the same.

The site has two other locations, both with HP procurve switches and Adtran Routers with similar config, both with DHCP hosted by the 3300 controller.

Ross, I'll check this out... the I'm not familiar with the DHCP-Relay command and how it's used... I've seen it in Dell switches, but never looked at it regarding HP's. We are using the IP Helper-address in both the HP's and Adtran router. I'm thinking that I need to eliminate this from the HP switch since it's not doing any routing.

I'll check this out and post an update... thanks for the advice guys.

- Mark

 

[kwbMitel]

Mark,

The symptom of your DHCP problem looks exactly as if the phone is being provided the wrong VLAN on the first discovery. Stalls at second discovery because can't see controller.

You've proven that the VLAN is the issue by statically assigning the VLAN and having everything work.

Are you CERTAIN that the 3300 is providing the response to the FIRST discovery.



*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[slapin]

How about someone setting up static IP in DHCP range? Can you track this IP down? Normally you will see its MAC on the router and then just find it on your switches. If you cannot trace the cable, just shut down the port. Whoever will call you is the troublemaker

 

[LoopyLou]

You could do this:

Description/Symptoms
How to program the 3300 DHCP server to only serve Mitel IP Phones


Body/Solutions
In order to prevent any other device except a Mitel IP Phone from getting an IP from the Mitel DHCP server, follow these steps

1. Give your IP Address Range the following name: ipphone.mitel.com
2. Enable the Client's class ID must match name option in the IP Range.

This causes the DHCP server to ignore all non-mitel IP Phone requests for an IP address. Please note that controller must be running 7.0 software or higher. As well if any new phones are added, then this option needs to be turned off until they upgrade their flash for the first time.

 

[AH64Armament]

KWB... yes I'm certain the 3300 is the first response to the DHCP... the phones are getting an IP address in the data VLAN and staying there.
Normally the phone will boot, get an IP address in the data VLAN, along with the VLAN ID of the Voice VLAN... see this as "I'm in the wrong VLAN", release the incorrect Data IP address, holding onto the Voice VLAN ID... requesting an IP address from the proper VLAN. It's as if the phones are getting an incorrect VLAN ID and not going beyond it.

Slapin - Excellent idea! I might try that when I get to the site - hopefully this afternoon.

Loopy - I'm not sure how this would be useful... the 3300 is hosting DHCP for both the Voice and Data subnets. I'll have to lab this out.

- Mark

 

[kwbMitel]

Mark, Your description of the VLAN issue is bang on.

"It's as if the phones are getting an incorrect VLAN ID and not going beyond it."

If you are Certain that the 3300 is providing the DHCP in both discoveries then Why/How/Where is the 3300 providing the wrong VLAN ID on the first discovery.

Additionally, the phone should display the VLAN ID that it is trying to use prior to the second discovery. What value do you observe?

Lastly, I've seen it happen where the VLAN ID is correct but the Priority has not been setup and this also cause the phone to Stall at the same place. Verify the priority settings as well.


*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[LoopyLou]

MarkAcompton:
I was assuming you have a seperate voice and data VLANs and had a seperate IP scope for each. Your orginal post mentioned PC reporting duplicate IP's and sets not coming up. I thought maybe the PC's might be grabbing addresses from the same IP address range as the phones. The process I show ensures nothing but phones can get an IP address from whatever scope is the one serving the voice VLAN. Sorry if that advice didn't help.

 

[AH64Armament]

Thanks Loopy... your advice was great... I'm just not sure how to deploy it regarding HP switches, where the phones come up directly into their Voice VLAN. The PC's and phones both come up in a default VLAN for that port... the port is untagged(data VLAN), and Tagged (Voice VLAN).
the phones will boot into the data, hold onto the VLAN ID, rejecting all other info, then boot into the voice VLAN.

What appears to be happening here is the phones are coming up into the Data VLAN and hanging. For some reason, PC's appear to be getting a duplicate IP address.

Both scopes are hosted from the 3300 controller, and they both are using .101-.250... there isn't (supposed to be) anything hard coded/static within the ranges.

- Mark

 

[AH64Armament]

Loopy - if you have a good config from an HP switch that lets the phone come up directly into the Voice VLAN, AND allow the PC to be connected to the back of the phone and into it's proper VLAN... I'd love to take a look at it.
you can send it to mark_compton@phonesav.com.

I've been doing telephone work since '97 and computers have been a hobby since the 80's, and turned into profession (necessity) around 2002.
I've had to learn a great deal about switches and routers... I don't by any stretch consider myself an expert, but I have deployed nearly 30,000 IP telephones.

If there's a better way to do something, I'm always for it... especially if its easier and saves time.

- Mark

 

[LoopyLou]

Will see what I can do. Typicaly on HP switches you setup LLDP. This is similair to Cisco's CDP. What happens is the phones boot and say "hey I'm a phone". LLDP then says "yeah ok then you are on VLAN X" ( Which is the voice VLAN ). The phones then reboot and issue their DHCP request on the voice VLAN. Using this menthod prevents anything but a recognized voice device getting on the voice VLAN. Its the best way.

 

[LoopyLou]

Try this.

hostname "ProCurve Switch 2910"
qos dscp-map 101100 name "Voice-Quality-QOS"
qos dscp-map 101100 priority 6
interface 1
name "MN3300"
exit
interface 24
name "MyTestPC"
exit
ip routing
snmp-server community "public" Unrestricted
vlan 1
name "unused"
no ip address
no untagged 1-48
exit
vlan 101
name "voip"
untagged 1
ip address 10.101.210.1 255.255.255.0
tagged 2-48
voice
exit
vlan 102
name "data"
untagged 2-48
ip address 10.102.210.1 255.255.255.0
exit
lldp enable-notification 2-48
primary-vlan 102


Sorry I didn't create it but got it from someone else as I don't really work on HP switches.

 

[Billz66]

can you post all your DHCP options from The mitel

 

[AH64Armament]

Sorry guys... I got the problem resolved... major oversight!

Thanks for the LLDP configuration posting... I'll play with it on my next install... today

I have to dig through old running-configs from the HP switch, but when I was finally able to go to the site to see for myself what was happening, I chased cables and made sure that things were plugged into the ports that were configured for specific devices... such as uplink to another switch, connection to Adtran Router, Connection to the 3300 ICP...

All were okay, EXCEPT for the connection to the 3300... somehow it was set to TAGGED on the Data VLAN and Untagged on the Voice VLAN.

This port should have been NO on the Data VLAN and Untagged on the Voice VLAN.

Like I said, Ill have to look at old configs to see when and if it had been changed.
Funny thing, they didn't have this problem on release 6.0.5.4 software... or so I understand.

Thanks again for all the help.
- Mark

 

[AH64Armament]

The LLDP configuration worked like a champ! The site has a Firewall (SNAP SG560) that is handing out DHCP to their data subnet. They wanted to continue to use it on the Data Side. The Mitel is handing out DHCP on the Voice side. The LLDP config solved this problem quite nicely. I will be implementing it on every new install.

one little hiccup with it though, is that the 5000 series IP phones don't support LLDP. I had 4 IP Paging units - they program as though they are a 5010 IP phone. I just set the switch port for them as untagged on the Voice subnet and NO on the data subnet.

Thanks everyone for their input.
- Mark