Shoretel & Sonicwall for DHCP

Im trying to determine what DHCP server options to use on my Sonciwall NSA3500 for my Shoretel 480g phones.

Ideally I want to place my VoIP system on a totally separate VLAN with DHCP options telling the phones to go onto that VLAN. On a past Mitel deployment I used DHCP option 128,129,130,132,& 133 and just package them onto a group.

This told the phones to go onto VLAN XXX once it got the DHCP option commands from the first VLAN.

Im just not sure what the specific Vendor ID is for Shoretel 480g phones.

I have the networking piece handled, just need to know the best DHCP options recommended for this scenario. LLDP and CDP are not an option.
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Blue Street TechLast KnightCommented:
Hi systems_Quixote,

I'd create a VLAN for the phones and assign it to a separate Zone. Then setup Interface, Zone and assign a port to the VLAN. This will allow you to run it to your switch to disseminate in an allocated manner to your phones.

Create a new DHCP dynamic group for distribution or Statics, whichever you prefer and assign it to the VLAN zone.

If you need step-by-steps just left me know...I'd be glad to provide them but you said "you had the networking piece handled" so wasn't sure if that is what you meant.

systems_QuixoteAuthor Commented:
Hey diverseit,

The same ports on the wall/switch will be used for PCs as well.

Im not quite understanding how the switch would know what device goes to what VLAN when a computer or phone is plugged in.

On the firewall I am creating a whole new interface, plugging that into the switch, tag all the uplinks and ports that will have phones. Then DHCP scope for the new interface/zone will send out options to tell the phone what VLAN to hop onto based on vendor specific information.

Not quite sure I understand your way of letting the switch and or port know what is a phone and what is a PC?

Blue Street TechLast KnightCommented:
I don't know how big your operation is so without knowing that info it may sway my solution.

But with PortShielding you can assign the port to a Zone thereby allocating the traffic that runs on it to the VLAN. If you run a switch off of that port everything it connects to will be allocated by design to the VLAN because the port is assigned to it.

Does that make sense?

BTW: It looks like Shortel is DHCP option (Option 156).

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Simple Misconfiguration =Network Vulnerability

In this technical webinar, AlgoSec will present several examples of common misconfigurations; including a basic device change, business application connectivity changes, and data center migrations. Learn best practices to protect your business from attack.

Blue Street TechLast KnightCommented:
Any update on this? How's it going?
systems_QuixoteAuthor Commented:
It turns out shoretel only uses DHCP option 156. In Sonicwalls version 5.8... It did not support the string you would typically enter into a Microsoft DHCP server; 5.8 needs a hex entry. In version 5.9... It allows you to enter the exact sting you need for option 156.

I then added my options to all the DHCP scopes, tagged all the ports with dot1q tags for my Voice VLAN and the phones put themselves on the correct VLAN.
Blue Street TechLast KnightCommented:
Great, I'm glad I could help (http:#a39481738) and I'm glad your issue is now resolved!
systems_QuixoteAuthor Commented:
I've requested that this question be closed as follows:

Accepted answer: 0 points for systems_Quixote's comment #a39506023

for the following reason:

None of the other solutions recommended using the new Sonicwall firmware that allow an option 156 string DHCP option.
Blue Street TechLast KnightCommented:

Did my comment (http:#a39481738) not give you Option 156 as the correct DHCP option? I included the reference as well, which explains it further. Please advise for my own knowledge.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Hardware Firewalls

From novice to tech pro — start learning today.