Mitel 3300's. DHCP Option Tag 133

[mlgary]

In our environment we are deploying Mitel to our smaller retail outlets now.   These are small sites with about 3-5 users per site.   We don't segment a voice VLAN at the site it is a flat vlan.   Our QOS is handled through the Cisco DMVPN system.   With us not having a Voice VLAN at all is it recommended to carry Option tag 133 via our DHCP server?   

My thought is if we are not tagging a voice vlan then why would I assign a VLAN priority value.   Is it needed or is it unnecessary since we have a flat network.

Thanks,

Mike

[ZuluAlpha]

With all traffic on the same network I wouldn't worry about it and let QOS do its thing. Even without QOS I doubt you'd see a big impact in traffic from 5 phones. Unless the circuit gets maxed out from other data quality should be fine.

*Edit - QoS would not affect the amount of traffic on the network

[mlgary]

So you recommend not adding the tag 133 at all?  Because we are a flat vlan without tagging would the priority function even do anything?   We are trying to standardize our DHCP config before we roll out to 200 locations.  We are in a pilot right now.

[martyn]

Option 133 is a legacy option these days and has been super seeded by option 125 which replaces 128,129, 130, 133, etc, all in the one option.

[VinceWhirlwind]

DHCP Option 133 sets Layer2 QoS. This is unlikely to be useful, especially as it sounds like you aren't using any kind of VLAN tagging, so you just don't get Layer2 QoS.

It's Layer3 QoS that is critical. This is set on the controller, and in the standard Mitel Option 125 for the handsets.