5330 sets won't boot.

[BrianWarner]

MCD 4.2
MXeIII Controller

Native Vlan = 13
Voice VLan ID = 950

No DHCP server on native Vlan. DHCP server is configured on the MXeIII. Statically assign the VLan ID into the set. The set receives an address from the controller but once it sees the VLan ID from the controller it will reboot. If I statically assign the VLan ID into a 5360 the set will boot. I have verified switch port configurations and all is well. I removed option 125 and built 128-132. Trouble is still the same. The fact that it is only affecting the 30's is what has me confused. Any suggestions would be appreciated. Going on site tommorrow after I go to prison! That would be a service call to the state correctional facility.

 

[kwbMitel]

I had issues recently with 5360's where I had to get them to do their upgrades on the Voice VLAN before they would properly boot on a multi VLAN port.

**********************************************
What's most important is that you realise ... There is no spoon.

 

[LoopyLou]

So you statically assign the VLAN of 950 into the sets and let them boot. 5330's don't boot but 5360's do. Is that the issue?

If you statically assign the VLAN 950 to the sets they then should be tagging their packets and their DHCP requests should be on the Voice VLAN where the Mxe would respond. You are getting an address so if there is no DHCP on the native VLAN then the IP is coming from the MXe. I would still use Option 125 because its clearer. I assume you have all the correct info i.e MITEL IP PHONE etc. Can you get a set to boot if you statically assign all the info ( gateway, RTP etc )? I might follow kwbMitel's suggestion and connect a phone directly to the 3300 to upgrade it to the current load and then try your statically assigning the VLAN info.

Would not have setup the system this way as you have to statically assign the VLAN to every phone. Waste of time in my opinon. I guess the layer 2 switches don't support LLDP or CDP?

The beatings will continue until morale improves.

 

[kwbMitel]

Sorry, I just read this again.

The set receives an address from the controller but once it sees the VLan ID from the controller it will reboot.

This will not happen if the VLAN provided by DHCP and the VLAN of the phone agree.

As you are statically assigning the VLAN anyway, remove the VLAN info from DHCP.

**********************************************
What's most important is that you realise ... There is no spoon.

 

[sarond]

As you are statically assigning the VLAN anyway, remove the VLAN info from DHCP.

No disrespect but I though with a managed L2/L3 switch that you had to have the VLAN in the option if you are using one.
I'm sure I've had an issue where the phones would not boot because it was missing an option for VLAN and the phone was statically set for it.
The Phone would display (0.0.0.0) and not proceed any further.

 

[kwbMitel]

@ Sarond, Nope, If the VLAN info is provided by a source other than the controller, it is not required in the controller.

This assume that the controller is on a port that is untagged for the voice vlan but I'm sure it would still be ok if the controller were set to tag the packets.

Do it all the time. Never had any issues.

**********************************************
What's most important is that you realise ... There is no spoon.

 

[BrianWarner]

I talked to the on-site contact on Friday. The problem is something in the config of his core switch. If he plugs a 5330 into a switch other than the core it will boot. I provided him the switch port configuration from the tech hand book. I will reach out to him today and see how it goes.