01-04-2017 05:47 PM
I have recently replaced all my network switches with Cisco 2960X switches. I have 6 voice vlans and approximately 100 data vlans. Just recently on one of my switches which just happens to be a stack with a 2960X-24ps and three 2960X-48LPD, all of the Avaya 1120E phones quit communicating with the switch. The ports all show up and connected but I could no longer ping the phone or the PC connected to the phone. We have Juniper Switches layer 3 switches that do the routing. When I check the ARP table on the Juniper switches, the phone and PC IP addresses are no longer in the table. The only way to get the phones and systems back is to shut the interface down and bring it back up (killing the power to the phone causing it to reboot) or reboot the switch. The Cisco switches replaced juniper switches and we never had this issue when the entire network was juniper. I have attached part of the switch config. Below is a description of the vlans configured.
113 - Management
117 - printer
220 - Data
502 - Voice
506 - Voice
999 - Park Unused
888 - Native
Update
Update - I thought I might have missed configured auto qos because on the interface with Avaya phone I put the command auto qos trust. I think the correct correct command should have been auto qos voip trust. I removed all qos and reconfigured each interface with a phone with the auto qos voip trust. This didn't fix the issue. I am not a qos expert but when I looked at the switch and issued the show mls qos interface statistics command I got the results in the attached file. Look at switch 4 in the stack mostly. There are a few ports on the other switches as well but mostly switch 4. I had cleared all of the qos statistics at 8:00 that morning and this information was captured at 4:00 p.m. Initially this stack consisted of three switches. The initial complaint of outages was the phones kept rebooting. As a temporary fix beings this was in production, I added a fourth switch to the stack. All of the phones that were "rebooting" were in the third switch. I moved all the cables to the fourth switch and the issues moved to the newly added switch. Please let me know if you have any ideas.
01-04-2017 06:17 PM
What IOS is the switches running on?
01-04-2017 06:45 PM
I don't have access to the switch right now but I think the IOS is either 15.2.5bE or 15.0.2a-EX5. Pretty sure its the first one though.
01-05-2017 06:29 AM
Hello
The Cisco switches replaced juniper switches and we never had this issue when the entire network was juniper.
The junipers support LLDP as CDP won't be applicable - so I am assuming lldp was used to negotiate the trunking for the phones
In Cisco you can do either cdp or lldp but again I am assuming these phone don't support CDP
If you manually apply static addressing to the clients or phone can you ping the L3?
Lastly try using LLDP
Looking at the port config, can you try the following:
1) Remove port security and the hard-coded mac addressing and clear its cache for now- clear port-security dynamic interface x/x
2) remove the qos priority queuing ( for now)
3) enable LLDP globally or on the interface
example:
conf t
lldp run
intterface GigabitEthernet1/0/4
no switchport port-security
lldp transmit
lldp receive
sh lldp neigbours
sh lldp entry
res
Paul
01-07-2017 06:12 AM
Update - I thought I might have missed configured auto qos because on the interface with Avaya phone I put the command auto qos trust. I think the correct correct command should have been auto qos voip trust. I removed all qos and reconfigured each interface with a phone with the auto qos voip trust. This didn't fix the issue. I am not a qos expert but when I looked at the switch and issued the show mls qos interface statistics command I got the results in the attached file. Look at switch 4 in the stack mostly. There are a few ports on the other switches as well but mostly switch 4. I had cleared all of the qos statistics at 8:00 that morning and this information was captured at 4:00 p.m. Initially this stack consisted of three switches. The initial complaint of outages was the phones kept rebooting. As a temporary fix beings this was in production, I added a fourth switch to the stack. All of the phones that were "rebooting" were in the third switch. I moved all the cables to the fourth switch and the issues moved to the newly added switch. Please let me know if you have any ideas.
01-07-2017 07:04 AM
Hello
did you try using LLDP on your ports?
01-08-2017 01:07 PM
Paul,
Yes I have LLDP configured globally.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide