Mitel Forums - The Unofficial Source
Mitel Forums => Mitel MiVoice Business/MCD/3300 => Topic started by: gimitel on November 02, 2016, 05:14:16 PM
-
Dear Mitel friends,
I have one question.
I have a Mitel 3300 Mxe that has lan ip 10.182.229.x.
Customer want that the Mxe lease ip for the office phones and hotel rooms phones
Office phone is on Vlan x 172.16.4.0 and hotel rooms phone on Vlan y 172.16.0.0. Both with their own network subnet.
Do i need to program 2x Option 125? One Option 125 with Vlan x and the other Option 125 with Vlan y ?
As i have 1x option 3 for the Gateway, do i need configure the ip routing on the mitel
Please advise,
Thanks,
GiMitel
-
You configure option 125 as a global, and then all other options (like option 3 for default gateway) per subnet or scope.
-
I've only used a real DHCP server rather than the phone controller, but when I looked at it, my impression was that you would need Option125 per scope as the VLAN is ID'd by the Option.
-
First things first, you need the network access switches to be able to send the phones over to the subnet/VLAN the controller is on. If you're using Cisco, you'd do this via an IP helper.
Then you need to program each subnet in the DHCP Subnet form, and create an address range for each subnet in DHCP IP Address range. DHCP Options would all be programmed with a scope of each subnet, not global.
-
Dear Mitel friends,
This customer has 3 vlan instead of 2.
Vlan 100: 10.182.229.32
Vlan 200: 172.16.4.0
Vlan 300: 172.16.0.0
I programmed today 3x subnet ID, 3x dhcp pool range, 3x option (3) & 3x option (125).
PBX ip is:
10.182.229.36
255.255.255.254
10.182.229.33
I programmed these options in the dhcp.
1: Option 3 Router 10.182.229.33 (Format) IP Address (Scope) Subnet 10.182.228.32
2: Option 3 Router 172.16.0.1 (Format) IP Address (Scope) Subnet 172.16.0.0
3: Option 3 Router 172.16.4.1 (Format) IP Address (Scope) Subnet 172.16.4.0
1: Option 125: Mitel id:ipphone.mitel.com;sw_tftp=10.182.229.36;call_srv:10.182.229.36; vlan=100;l2p=6,6,3;dscp=46,46,26 ASCII String (Subnet 10.182.228.32)
2: Option 125: Mitel id:ipphone.mitel.com;sw_tftp=10.182.229.36;call_srv:10.182.229.36; vlan=200;l2p=6,6,3;dscp=46,46,26 ASCII String (Subnet 172.16.4.0)
3: Option 125: Mitel id:ipphone.mitel.com;sw_tftp=10.182.229.36;call_srv:10.182.229.36; vlan=300;l2p=6,6,3;dscp=46,46,26 ASCII String (Subnet 172.16.0.0)
Option 128 TFTP Server 10.182.229.36
Option 129 Call Server 10.182.229.36
Option 130 IP Phone Identifier MITEL IP PHONE
Option 134 DSCP 46
In the IP Routing on the mitel i add the subnet id (Vlan 200 & 300) in the table
After all these programming when i connect a mitel phone into a port with vlan 200, it will not get an ip address from the scope. This is also when connect into a port with vlan 300.
But when i put an static ip and vlan id into the phone, the phone will register with the mitel pbx.
I put one laptop with static ip on both vlan 200 & 300 and i ping them both side.
The only thing that is not working is, that the phones are not getting ip address from the dhcp on the mitel.
Can someone help me !
Thanks,
Gimitel
-
Like Lundah said, each of 172.16.0.1 & 172.16.4.1 need an IP helper on them.
-
You have to understand: the DHCP request is a broadcast, so it stays within its own VLAN. If the DHCP server is on a different VLAN, then the router on the segment where the DHCP broadcast is occurring needs to pass it on to the VLAN where the DHCP server is, otherwise the DHCP server doesn't see it.
-
Thanks VinceWhirlwind and Lundah.
I programmed for every vlan an subnet in the dhcp subnet form and a dhcp range for each subnet.
The Options is (3) & (125) is also programmed with the scope of each subnet.
The other options i can leave them like this ?
Option 128 TFTP Server 10.182.229.36
Option 129 Call Server 10.182.229.36
Option 130 IP Phone Identifier MITEL IP PHONE
Option 134 DSCP 46
The ip helper need to point to the ip address (10.182.229.36) of the Mitel or the Default gateway (10.182.229.33) of the Mitel ?
Please advise, so i can test it tomorrow.
Thanks,
Gianni
-
The other options are the same for all.
IP helper points at the 3300's IP address.
-
Thanks VinceWhirlwind.
Last question.
When programming Option 125 you choose your scope from the drop down box you have either Global/Subnet/Range.
For Option 125 do i need to choose Range and option 3 Subnet
Thanks
Gimitel
-
I asked myself the same question.
Martyn says it can be either.
-
I've used Subnet scope for option 125 before when working with multiple subnets. If all of the information in that option stays exactly the same across all subnets, you could select Global instead.
-
Hi Lundah,
I will test it tomorrow and will feedback to you all.
Regards,
Gimitel
-
Hello guys,
I tried everything but no success.
I used static ip on the phones so they can work.
Is there something else i can try ?
gimitel
-
Can you confirm how your switch is programmed.
Are the ports you're connecting too tagged for VLAN200 & 300? What is the untagged (native) vlan.
Bear in mind that you will need a DHCP offer on the native vlan to tell the phone what VLAN it belongs to.
-
Bear in mind that you will need a DHCP offer on the native vlan to tell the phone what VLAN it belongs to.
Sarond is correct. But if your dataswitch ports are in Access Mode (Cisco) then the native VLAN is your voice vlan. One thing you might want to try is putting wireshark on your laptop to see what you get when you do a DHCP request.
Ralph
-
Bear in mind that you will need a DHCP offer on the native vlan to tell the phone what VLAN it belongs to.
This isn't required, as CDP or LLDP take care of that.
-
Let's summarise how this is meant to work:
Switch config:
LLDP enabled
VLAN200 voice
Switchport config (Access):
Phones/PCs:
VLAN100 untagged(=access)
VLAN200 tagged
Services (eg DHCP server):
VLAN100 untagged
Switchport config (uplink):
VLAN100 tagged
VLAN200 tagged
Router/Layer3 Switch config:
VLAN100 IP address 10.1.100.1
VLAN200 IP address 10.1.200.1, IP HELPER: 10.1.100.20
Router/L3 Switch physical interface config:
VLAN100 tagged
VLAN200 tagged
DHCP config:
Server IP address: 10.1.100.20
Scope 10.1.100.21-199
Scope 10.1.200.21-199, Option125 incl gateway address, QoS, & VLAN
-
Bear in mind that you will need a DHCP offer on the native vlan to tell the phone what VLAN it belongs to.
This isn't required, as CDP or LLDP take care of that.
This is assuming CDP/LLDP is being used for voice.
The problem I see is that it may not be desired as you would need different VLANs, not all phones belong in the same VLAN.
I would use helpers on each subnet/vlan to point to the 3300.
Program each DHCP option as you have done but remove the VLAN options in 125.
Program ports as untagged/access for the desired vlan. That you are connecting phones to.
If you offer a VLAN in the DHCP option it will tagged the phones packets and it will fail (I believe)
If you are wanting to connect a device on the PC port then this will be a different setup again.
-
The problem I see is that it may not be desired as you would need different VLANs, not all phones belong in the same VLAN.
The general approach is that each Access-layer switch (or switch-stack) has a single Voice VLAN.
That VLAN has the "VLAN ID Voice" command issued against it.
Every phone that is patched to that switch gets the LLDP message to use that switch's Voice VLAN.
On a different switch, a different VLAN is configured and called "voice" and phones on that switch join that VLAN.
The basic principle of VLAN design is to have as few VLANs per switch as possible and they are not spanned across multiple switches.
VLANs are not a security mechanism (except inasmuch as they assist in managing availability risk), they are a convenience to improve efficient management.
Sadly, networking textbooks *still* explain VLANs as a way to security-separate functional business units, an approach that was made obsolete in about 1994 when Windows NT came out.