VoIP Phones Not Working on Secondary Switches

Greetings,

I have a site where I have several Yealink T26P phones connected to multiple Aruba (HP) 2530 POE switches.  There is a stack of 4 switches, with the primary switch connected to a SonicWALL TZ300 router.  All the phones on the primary switch work normally.  The phones do not work on the secondary switches.  I have two VLANS (data and voice).  Basically, I have every port tagged with the voice VLAN and untagged with the data VLAN.  The only difference is that I have two ports on the primary switch that are untagged for the voice VLAN only (voice uplink from SonicWALL and phone controller).  In testing with other phone types, I've been able to plug into the POE port on any switch and have it work.  This is my first interaction with the Yealink phones, and it is remote.  As the only difference between the switches is the uplink port config, I'm guessing that I need to have a port untagged for the voice VLAN only and a different port untagged for the data VLAN only?  This would seem like a very poor design, as it would effectively require the use of up to 4 ports per switch.  So, what am I missing?  My SonicWALL is serving as the DHCP server and seems to be working fine and it actually shows the non-working phones actually get an IP.  They just don't connect.  Move them to the first switch and they immediately connect.

Thank you for any assistance that you can provide.

Jeremy
LVL 3
JerAsked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
JerConnect With a Mentor Author Commented:
Bah.  The matter was resolved.  Due to not being able to find anything wrong with the config, I had staff at the site double check all devices connected to the wall.  As it turns out, someone have plugged both LAN and WAN ports of a single phone into live jacks.  As such, I suspect the VLAN tagging was being stripped.  I'm kind of surprised that it didn't create any looping entries in my switch logs.  Anyhow, the problem has been solved.  Now to figure out a way to prevent it from happening.
0
 
JerAuthor Commented:
Quick update.  On the phone display, it states "Waiting for IP address" on the non-working phones.
0
 
Hemil AquinoNetwork EngineerCommented:
If is not working on the secondary switch is because you dont have a trunk port, OR maybe you haven't permitted your vlans to go through it.
I dont know too much about HP and Aruba's equipment ,but I can give you an Idea how everything should be.
I'm more Cisco than anything.

Let start with the obvious:

1- VLAN10 name DATA
2- VLAN20 name VOICE
3- TRUNK link between switches (as you know)
4- VLANS needs to be tagged in order to pass information.
5- Untagged vlan is default one  like (vlan1) that does not need to be tagged.

Once you have this in place, you should be ok.
0
Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
JerAuthor Commented:
That is the issue that I'm having.  With HP, I'm thinking that I'm not setting up the trunk correctly.  There is online content regarding configs and differences from Cisco, but none have helped, so far.  I've got a test environment setup, so it is just a lot of trial and error for now.  Hoping that someone have been there, done that with HP.
0
 
Hemil AquinoConnect With a Mentor Network EngineerCommented:
Here is a link that would help you how to do it.
Follow the steps. Any question please let me know.

https://community.spiceworks.com/topic/153622-how-to-configure-trunk-port-between-hp-and-cisco-switches
0
 
JerAuthor Commented:
The solution had nothing to do with any other suggestion and was found on my own.  Still want to give Hemil points for trying to help.
0
All Courses

From novice to tech pro — start learning today.