Mitel Forums - The Unofficial Source
Mitel Forums => Mitel MiVoice Business/MCD/3300 => Topic started by: NewVoIP on July 05, 2009, 11:39:38 PM
-
hello,
When 5340 boots and indicates vlan none pri none, why is this happening. When we have set on our HP switches vlan 30 (VoIp) and priorty 7.
-
Assuming you are using DHCP to assign addresses to the phones, you need to use DHCP options to tell the phone what VLAN it should be a member of:
To use an external DHCP server you need the following options in your scope(s)
128 - The Ip address of the controller
129 - The IP address of the controller - again.
130 - String MITEL IP PHONE
132 - VLAN ID
133 - IP Priority (Mitel want it set to 6)
-
yes, we are using the dhcp from the 3300IPC, no external. Do we need to set this options still within the 3300IPC?
-
Hi it depends on the setup.
The phone is only aware of Vlan tagging info it is given by a DHCP server. So it depends how you have setup the switch. If you are using fixed vlan ports for the phones (I.E the port is fixed to Vlan 30 no matter what is plugged in) then no Vlan info is needed by the phone as it doesnt need to 'tag' the packets with a Vlan ID as this is done at the switch. However if you are using the ports as 'dynamic' (I.E plugging a PC into the phone pass through and connecting to a different vlan then the DHCP server will need to inform the phone of the voice vlan. In this setup though you would either be using LDAP or 2 DHCP servers 1 in default Vlan & 1 in Voice Vlan.
Hope this helps.
-
We are configured for dynamic (pc connects to phone to the switch)
2 dhcp (MS Windows dhcp for data, default vlan), (3300IPC dhcp for phones, vlan 30)
Below is what is configured on the 3300IPC dhcp options.
3 Router 172.168.30.1 IP Address
125 Mitel id:ipphone.mitel.com;sw_tftp=172.168.30.2;call_srv=172.168.30.2;dscp=46v46s26 ASCII String
128 TFTP Server 172.168.30.2 IP Address
129 Call Server 172.168.30.2 IP Address
130 IP Phone Identifier MITEL IP PHONE ASCII String
134 DSCP 46 Numeric
If i understand what you are suggestion, then would we need to include
132 = vlan30
133 = Ip Priority 6
Is this correct?
-
Yep -but
132=30
133=6
no text in there.....
-Chak
-
I believe the HP switches can do LLDP to discover the voice vlan
-
Ok, First thing, you need to know how the phones are booting up and finding VLAN 30 there are two ways:
1. The DHCP in the default Vlan (data) has the mitel IP phone rules in its scope including 132 (vlan id) and 133 (priority). when the IP phone boots is broadcasts for a DHCP server and receives an offer from the default vlan DHCP. As soon as the IP set receives this offer it accepts because it has the mitel options. When it sees option 132 (vlan 30) it will reboot and broadcast for an DHCP server but this time it does it on Vlan 30 it will then receive an offer from the 3300. You should not need the the valn ID or the priority on this DHCP server.
2. The network switches are set to use cpd/lldp. In this setup you configure the switches with a voice vlan. When the phones boot and use cdp/lldp to discover what vlan they belong to. They will then reboot and broadcast on the voice vlan for a DHCP server. You should not need the vlan info on this DHCP scope either as the phone already knows what vlan it is in.
Do you actually have a fault or are you just curious as to why the set displays 'vlan=none priority=none'?
-
the fault we are having is that we are getting echos, jitters, and delays. Not seeing the "vlan id and priorty" on the display got us to think that it needed to be set with the dhcp options of the 3300 to help with the Qos priorty.
The phones are working though. Thank to all who responded it has given us great information.
We are still trying to work on the above faults.
-
Are the telephones on the correct vlan?
To check go to
Maintenance and Diagnostics
IP Telephones
All IP Telephones
Look at the IP address of the sets. Are they in the voice vlan or data vlan?
-
the ip address are in the voice vlan. Any other suggestion why is it that we have so much echo?
-
can you post some more info on your hardware? System variant? cards installed? Trunks? number of stations etc? Is this a new install? Has this problem only recentley occured?
-
hello, This is new install. Our setup is
HP switches, 2 vlans (default, vlan30)
(Default vlan for data, consist of MS DHCP, untagged)(vlan30 Voip, priorty 6, Mitel DHCP, tagged)
All ports for Vlan30 are tagged, phones are getting address from Mitel dhcp, options are set below
3 Router 172.168.30.1 IP Address
125 Mitel id:ipphone.mitel.com;sw_tftp=172.168.30.2;call_srv=172.168.30.2;dscp=46v46s26 ASCII String
128 TFTP Server 172.168.30.2 IP Address
129 Call Server 172.168.30.2 IP Address
130 IP Phone Identifier MITEL IP PHONE ASCII String
134 DSCP 46 Numeric
No routing is set
We have been told that we need to set the vlan30 interface port that is trunk to Mitel 3300 to untagged and No to default vlan. Then we will need to set opiton 125, the same as the vlan id 30 and priorty that we have set on the hp switch.
With these changes is should reduce the amount of delay, echo, and jitters that we are having.
-
You never said how many phones you were dealing with here.
If you have a large amount of phones or if you are pumping a lot of data around your network then setting up VLANS should help.
As a side note, do your self a favor and be sure that the Data Switch port connected to your MS DHCP server does not have the voice vlan associated with it. Twice now, I've been brought in to a problem where phones will not boot because that data switch port had both the voice and data vlan tied to it.
Ralph
www.statewide-dental-plans.com (http://www.statewide-dental-plans.com)
-
Also, 172.16.30.0/24 isn't an rfc1918 network.
-
Also, 172.16.30.0/24 isn't an rfc1918 network.
I had to stop an look up the RFC.
172.16.0.0 - 172.31.255.255 (172.16/12 prefix) is the actual private space subnet.
172.16.30.0/24 is just subnetting it down further. Shouldn't be an issue.
Ralph
-
Been out sick, here are additional informations, we have a total of 102 phones, the MS Dhcp isn't assosicated with the VoIp vlan, Keep in mind the phones are working but there is so much echo, etc. We were told that we need to Untag the port that Mitel 3300 ICP and then set the opiton 125 of the mitel dhcp, Vlan 30 and Priorty 6. We test everything worked fine. Echo, jitters, etc tremendously reduce. But now we need to configure our HP switch to route/dhcp relay.
There are 5550 consoles, third party CA and VM that are interface with the Mitel via IP. We are trying to use one nic for above items needs. They need too access both data and voice network.
Thanks for all whom reply, greatly apprieciated.
-
Your ports should be configured something like this
The MS DHCP server untagged on the data vlan only
the 3300 server untagged on the voice vlan only
Phones and PC's untagged data vlan and tagged voice vlan
for QoS type-of-service diff-services is the line in the configuration for HP it shouldn't really matter if its all on the same lan.
I have a document on how to configure the MS DHCP server but its too large to attach here.
PM your address an I will send it to you or maybe one of the moderators can raise the limit on the size of attachments.
-
Also,
You shouldn't need an IP Helper address if the options are set correctly in the native VLAN DHCP server.
Ralph
-
Didn't realize it was so low - bumped it to a meg - is that enough?
-Chak
-
2.5 meg unzipped
Here is the DHCP configuration guide for the MS DHCP server
This is a ZIP file rename it from .txt to .zip
-
Also, 172.16.30.0/24 isn't an rfc1918 network.
I had to stop an look up the RFC.
172.16.0.0 - 172.31.255.255 (172.16/12 prefix) is the actual private space subnet.
172.16.30.0/24 is just subnetting it down further. Shouldn't be an issue.
That should have read 172.168.30.0/24 isn't a valid rfc1918 network.
-
I am curious as to why the echo problems would have been reduced. His IP sets were in the correct subnet (Voice Vlan IP address range, correct??)
Is it possible that the sets could have been in the right Vlan, but the data wans't being tagged / prioritized properly?
If someone could explain what was wrong, and is now corrected, I would appreciate it!!
-
Using option 125 to identify the Vlan ID and priority is juts another way of providing the same info as options 132, 133. So was it the untagging of the port that the 3300 was connected to, that fixed the echo?
NewVoip - Do your IP sets now tell you what VLan / Piority they have, as they boot up??