stack with "Option 128 missing"

[voipneerd]

Dear All
I have migrating from Mitel 3300 LX to virtual vMCD .
I have windows 2008 R2 with DHCP server enabled. with options 132, 130, 129, 128, 66,67,(still can't configure option 125)
I have 2 vlans vlan 10 for data and vlan 20 for voice.
I have set up the DHCP option on the MSL.
the phone hangs when booting with a message stating "Option 128 missing."
I have noticed that but The phone is ACKing and Releasing the first DHCP .

I've assign static IP address for the phone and it's working Fine.
any suggesting.

Best Regards

 

[danramirez]

I would imagine that you should have had a router or layer 3 switch doing dhcp helper (i.e. forwarding dhcp broadcasts)to your 2003 server. Now you have changed your DHCP to your MSL, so the question is: have you told your router that your new helper address is now your MSL?

Your DHCP service on your MsL should include both scopes and your option 125 should include vlan ID 20

Let us know if you are pointing your dhcp broadcasts to the right place in the network

http://www.hatkana.com

http://www.wtelecom.com

 

[LoopyLou]

When you say MSL are you talking about the MSL that is part of vMCD?



I'd tell you a UDP joke but I'm afraid you won't get it. TCP jokes are the best because you always get them.

 

[voipneerd]

Hi danramirez
I've setup the vMCD with the same setting and IP address as the old Mitel 3300 lx controller. and I've dedicated one physical network card for the vMCd and connected in the same port on the switch where was the 3300 LX controller connected.

If I switch of the vmcd and switch on the 3300 Lx every things are working fine.

is this could be because of missing 125 options in win2008 server?

Best Regards

 

[voipneerd]

Hi LoopyLou
yes the MSl is part of the vMCD

Best Regards

 

[LoopyLou]

You can use option 125 or the other older options ( 128, 130 etc ). The move from the older options to Option 125 was that other applications somwtimes wanted to use those options as well.

The LX has a built in DHCP server and that is why it works. The vMCD doesn't have a DHCP server so you are trying to use the DHCP server of the MSL. You see the phone releasing the first address so that would suggest the 2008 server is ok. At that point the phone should have picked up that its on VLAN 20 and should be issueing a second DHCP request on that VLAN. Is the LX tagging its packets by any chance or is the port the vMCD is connected to on VLAN 20?

Do you have the VLAN 20 subnet assigned in the local networks panel of the MSL?

I'd tell you a UDP joke but I'm afraid you won't get it. TCP jokes are the best because you always get them.

 

[voipneerd]

Hi LoopyLou
vMCd is now connected to the same port for 3300 LX.

and yes I've setup the vlan 20 sub net in the local networks.

BR

 

[sarond]

How is the switch port that the vMCD plugged in to programmed, as Loopy stated earlier is the LX tagging packets? The switch port will need to be access/untagged vlan 20 if you are not tagging the packets.

 

[kwbMitel]

The phone is Acking and releasing the initial DHCP.

When it does so, it should display the new parameters for the VLAN and Priority.

I strongly suspect you will find that the VLAN is 32 (Hex 20).

Somewhere along the line I think your confusing Hex with Decimal.


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