VLAN CONFIGURATION.

[Laylobrown]

we have a 200 mx connected to a POE switch. The client has a metro fiber ring and right now have 3 locations on it. They are using on controller for all locations and decided to put a vlan up on each of the hp procurves. Their IT guys set up the vlan up themselves.

At the location with the controller the phones boot up. No special dhcp options were changed on the controller there. They do have voice as vlan 5 on their hp switches.

At the remote locations all the phones are plugged into hp poe switches and their ports are tagged for vlan 5 as well.

At the remote locations the phones boot up and then rejects dhcp stating it rejects it because it's missing option 128. I'm telling them that their local dhcp servers at each location should have the mitel options inside of it. Eventhough they already tagged the ports the phones are plugged into as vlan 5.

 

[kwbMitel]

I will assume the remote locations have different subnets eventhough they have the same VLAN. This being the case, you will need to use the IPhelper command (or equivelent)to broadcast the DHCP accross subnets

*******************************************************
Hard work often pays off after time, but laziness always pays off now.

 

[StilPhone]

Have you tried specifying a static IP as a test? This would prove the DHCP theory.

 

[slapin]

Laylobrown, your problem requires to review their network diagram and I beleave cannot be answered here. Too many unknowns. Do they have a single broadcast domain for each VLAN for all locations? Do they run separate DHCP for each location? Do they have Voice VLAN option at all DHCP servers? And so far so on...

 

[Laylobrown]

Yes that is what we ended up doing. In the beginning they said they had all the vlans and ports tagged and what-not. I told them that if they have dhcp servers at each location that they needed to add those options. But the client insisted that since the ports were tagged for vlan 5 (voice) that they wont be able to communicate with nothing but the phone subnet.

Of course I looked at them all cock-eyed.

All the phones at the icp location comes up as they are suppose to because the switch is giving out dhcp to phones, they are plugged into tagged ports.

But I told them that for the remote locations the phones will pick dhcp from the local server and if the options are there it will drop the ip and require of the vlan listed in the options. But you it is hard trying to convince someone of something on their own network.

I went ahead and statically assigned the vlan options in the phones and they came up. On the second day they finally was willing to allow the dhcp server to have the options but guess what?

They were running novell and the server doesn't support the data syntax in which the vlan options for 132 and 133 needed to be entered. Kept saying bad vlan. 0X5 vlan and 0X6 priority was not a supported option, changed it to string, ip address, and other options in there but whatever microsoft supports was not in Norvell.

So statically assigning just the vlan options allowed the phones to boot up directly from the phones system which were on vlans. Had to tell the phones to look at the right vlan.

 

[kwbMitel]

About the syntax error on the server.

I never worry about entering the data in Hex.

Just type the decimal value and the system will automatically convert it to hex. (if required)

Saves lots of time from trying to calculate the Hex value.



*******************************************************
Hard work often pays off after time, but laziness always pays off now.

 

[slapin]

Do they have L2 voice network spanned across multiple locations or it's just the same VLAN numbers for all the locations?

 

[Laylobrown]

it's vlan 5.

And kwb this is on a novell server?

can you give me an example of what you are typing?

 

[slapin]

Laylobrown, VLAN 5 is not a magic spell. There are different approches and I'm trying to figure out how to help you.

 

[kwbMitel]

just try typing 5 and save not 0x5

*******************************************************
Hard work often pays off after time, but laziness always pays off now.

 

[MitelMail]

I have a zip file with extensive screen shots for setting up DHCP on Novell. Let me know if you're intereested, giv eme your email address

 

[Lundah]

Not sure if it's going to help in your situation, but another tidbit I've found is when you're using a tagged voice VLAN, you have to make sure that the switchport connected to the default VLAN's DHCP server does NOT have access to the voice VLAN. Otherwise, the external DHCP server will respond to the DHCP request before the ICP and the phone will respond with an Option 128 Missing error.

 

[slapin]

The name of the thinkg is "native VLAN". If host doesn't tag packets, switch will process untagged traffic in a native for this particular port VLAN. This allows to have multiple "data" VLANs mixed with Voice VLAN. Besides that it's possible to have multiple Voice VLANs in the network.