VLAN issue with VoIP phone through Procurve 2524 switches

Issue:
Mitel 5330 VoIP phone displays "Missing option 128" meaning it's unable to connect to the Mitel 3300 phone server

Environment:
Main Switch #1 = Procurve 5406ZL connected via fiber run to Switch #2 Procurve 2524 which connects via CAT5 to another Procurve 2524 switch #3

VLAN 1 and VLAN10 are set up and Mitel 5330 VoIP phone works on Main switch #1 and Switch #2.

VLAN10 is the Voice VLAN

On switch #3 I've tried adding the IP ROUTE 0.0.0.0 0.0.0.0 172.16.1.1 but I receive the error message:  
ip route 0.0.0.0/0 next-hop 172.16.1.1: Inconsistent value

172.16.1.1 is my Default Gateway

This is the only leg of my network that has a "third" switch on the line. Data is routing correctly but the Voice VLAN is not making it all the way to the VoIP phone on Switch #3. I think the problem could either be with VLAN tagging on Switch #2 not passing the correct traffic OR with the default IP route that doesn't exist on Switch #3

Any ideas\suggestions? Thank you in advance!

Running configuration: Switch #2
J4813A Configuration Editor; Created on release #F.04.08
ip default-gateway 172.16.1.1
vlan 1
   name "DEFAULT_VLAN"
   untagged 2-6,8-14,16-23,25-26
   no untagged 1,7,15,24
   ip address 172.16.2.103 255.255.0.0
   exit
vlan 10
   name "VLAN10"
   untagged 1,7,15,24
   tagged 2-6,8-14,16-23,25-26
   no ip address
ip route 0.0.0.0 0.0.0.0 172.16.1.1

Running configuration: Switch #3
J4813A Configuration Editor; Created on release #F.04.08
ip default-gateway 172.16.1.1
vlan 1
   name "DEFAULT_VLAN"
   untagged 1-26
   ip address 172.16.2.104 255.255.0.0
   exit
vlan 10
   name "VLAN10"
   tagged 1-26
   no ip address
mj8chAsked:
Who is Participating?
 
atrevidoConnect With a Mentor Commented:
VLAN 1 untagged and VLAN 10 tagged is normal for a VoIP phone.  That will work fine.

so the trunk ports need VLAN1 tagged and no setting for VLAN10?
No, I said that the uplink ports need to carry tagging on both (aka ALL) vlans.
for for switch 3 your config would look like:

J4813A Configuration Editor; Created on release #F.04.08
ip default-gateway 172.16.1.1
vlan 1
   name "DEFAULT_VLAN"
   untagged 1-25,26
   tagged 24
   ip address 172.16.2.104 255.255.0.0
   exit
vlan 10
   name "VLAN10"
   tagged 1-26
   no ip address

For switch 2 your config would look like:

ip default-gateway 172.16.1.1
vlan 1
   name "DEFAULT_VLAN"
   untagged 2-6,8-14,16-23,26
   no untagged 1,7,15,24
  tagged 25
   ip address 172.16.2.103 255.255.0.0
   exit
vlan 10
   name "VLAN10"
   untagged 1,7,15,24
   tagged 2-6,8-14,16-23,25-26
   no ip address


By the way, from a best practice standpoint, life is much easier if you put your uplinks at the end of your switch, like ports 24, 25 or whatever.  Just cleaner
Also, labelling your ports is always a good idea, just for important ports
switch#2(config)#int 25
switch#2(config-int 25)#name "uplink to switch 1"
switch#2(config-int 25)#exit
0
 
atrevidoCommented:
what is the port on switch 3 and switch 2 that ties those 2 together?
and what is the port on switch 2 that goes to switch 1?

What I can see on your switch 3 config is that whatever your uplink port is you have no vlan 1 tagging.
I'm of course assuming that switch 1 goes to switch 2 which then goes to switch 3
If you have switch 2 and 3 both connecting back to switch 1 then the same principal would apply
The VLAN tagging for ALL vlans must be on those uplinks on all switches

Let's pretend on switch #3 port 26 is the uplink to switch#2, it goes to port 26 on switch 2 as well
then your programming would change like this

switch3(config)#vlan 1
switch3(config-vlan-1)#tag 26
switch3(config-vlan-1)#exit

on switch#2 it would change to
switch3(config)#vlan 1
switch3(config-vlan-1)#tag 26
0
 
mj8chAuthor Commented:

(thank you atrevido)
switch #2 port 25 is fed from switch #1 (switch #2 is working properly with data & voice)
switch #2 port 4 feeds to switch #3 port 24

And yes switch 1 goes to switch 2 then to switch 3

Tagged versus untagged is definitely part of my confusion.

i want switch #3 port 2 to operate the VoIP phone. VoIP is on VLAN10. Should the VLAN10 ports be tagged with VLAN10 and untagged on VLAN1?
0
Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

 
atrevidoCommented:
ok 2 major points here
first
For multiple VLANs to traverse switches the uplinks or trunks need to be tagged for all VLANs
so on switch 2 - port 25 should be tagged for VLAN 1 and 25
And also on switch 2 port 4 should be tagged for VLAN 1 and 25

for switch 3 - port 24 shoud be tagged for VLAN 1, 25

This brings all VLANs up to the core switch

the second part of this is the VoIP itself
Is the VoIP phone in front of a computer?  Or is it standalone on the port?
Is the phone statically set or DHCP?

If the VoIP phone is all by itself on that port 2 on switch #3 then you could make port 2 untagged vlan 10
but normally you would run any VoIP/PC ports as (in cisco terms a trunk port) in Procurve terms - VLAN 1 untagged, vlan 10 tagged
Because PC nics are not vlan aware but VoIP phone nics are.

Where is your VoIP controller?

0
 
mj8chAuthor Commented:

the voip phone is standalone on the port

voip phone is using DHCP from voip controller which is connected to switch #1

i thought that VLAN1 untagged and VLAN10 tagged was correct for the phone. That's working everywhere else.

so the trunk ports need VLAN1 tagged and no setting for VLAN10?
0
 
mj8chAuthor Commented:
OK - that cleared it up and all is working. THANK YOU for you time and great help!
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.