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 gmmastros on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Option 43 for DHCP Server

Status
Not open for further replies.

jnzy111

MIS
Jan 3, 2008
65
US
I'm trying to configure option 43 for our optipoint 420 phones (Hipath 4000 V2) and setup a voice vlan.

My Vlan is 666, however according to the hex converter I use it is 29A in hex so I tried the following:

01 0A 53 69 65 6D 65 6E
73 00 00 00 02 04 00 00
00 29A 00 00 00 00 00 FF

Due to the 3 digits of 29A, the option cant be set..

Any one know of a solution to define vlan 666 as my voice vlan?

---Mike


 
Did you have a look here?


Avaya_Red.gif

___________________________________________
It works! Now if only I could remember what I did...

Dain Bramaged
___________________________________________
 
Yes, I did and it's a great example if my vlan were 100 or under, however my voice vlan is 666 which translates to:

00 00 00 29A

The problem is that "29A" won't go into the DHCP server options due to the 3 digits.

Still looking for the solution to identify vlan 666 in my option 43....
 
I haven't read the whole lot there, but is your DHCP server in the VLAN666 or is it in the Default or other VLAN?

If it's in a default or other VLAN then you'll need to do a route add command from a dos box.
And your one of your switches needs a L3 switch that can do VLAN routing.
Say your DHCP on the default VLAN is 192.168.1.0/24
and the scope on VLAN666 192.168.6.0/24
If so then do the following.

open a dos box and typ;

route add 192.168.6.0 mask 255.255.255.0 192.168.1.x -p

192.168.1.x is your routing switch, and the -p is to make it permanent, so if you don't use -p then it will loose the route after rebooting or disconneting the LAN cable.

Avaya_Red.gif

___________________________________________
It works! Now if only I could remember what I did...

Dain Bramaged
___________________________________________
 
Wouldnt this work:

01 0A 53 69 65 6D 65 6E 73 00 00 00 02 04 00 00 02 9A 00 00 00 00 00 FF

 
Hello

There are only 255 possible vlans, therefore 666 is not a valid vlan ID.

you must choose between 1 and 255
 
Hi Denny - I thought that would work too, however when you run it through the hex converter at it translates to decimal 8346

Bas1234 - Thanks but routing is not an issue at all, we have a fully implemented OSPF infrastructure and I have verified routing is good between the two different subnets and back.

Juldal - we are running Cisco IOS 12.x on a catalyst 4506 where the maximum number of vlans is actually 1005

Still looking for a solution :-(
 
Hello did you find your solution?
I am not using option 43 as this is the worst thing you can use, VLAN Discovery by DHCP works and I am using vlan 1118 for exemple (not on cisco but nortel switch) so you can configure that on a Win2003 DHCP server.

let me know
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top