VISIT WEBSITE >>>>> http://gg.gg/y83ws?769026 <<<<<<
This will tell you what the phone "thinks". Does the phone know about the voice vlan? I can't see it in voice vlan. Phone thinks voice vlan is and it is "tagged". On the switch you should have: vlan tagged 17 voice vlan xxx datavlan untagged The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise.
By using this site, you accept the Terms of Use and Rules of Participation. End of content United States. Once they were rebooted it would come up with discover xx. After that discovery we thought possibly DHCP related. So I think that portion is working. Now it looks like the phones will only boot up if the phone VLAN is set to untagged.
Typically most users have computers that connect through the phones leaving the phone vlan untagged really isn't an option. This has worked for the past six years not sure why just this week it stopped. Of course then the computers wont work. If I make the change back to default pvid 10 with untagpvid only the phone goes back to discover xx.
You might need vendor support on this. It hasn't been changes recently making sure maybe a typo or something isn't causing the issue. Finally figured it out last night. Anyway basically all I did was create a new virtual switch in Hyper-V for that server and now all the phones reboot and find dhcp addresses fine.
And this is affecting all the phones in the environment, not just a subset of phones? If so have you looked at the switch environment to validate nothing funky is going on? You see anything in the switch logs that would indicate some sort of odd problem? It is all phones. Atleast we've tested about 10 connected to different access switches around the building. It seems like tagged traffic just isn't being routed properly or something.
Usually one of those protocols is used with the phones to determine VLANs for voice and data, etc SOunds like that information may not be being communicated. So based on Wireshark you are seeing the following? If not this is the first thing I would attempt to do. You have to find out where the DHCP request stops being communicated properly. Once you do that we can narrow down where you should look. One would think it almost has to be either a the DHCP server itself or b core switching infrastructure that is not routing the requests properly.
Also connect your server to one port on the switch assign it to the voice vlan then enable voice vlan also on that port. Should work flawless. I think thats the step you are forgetting. To continue this discussion, please ask a new question. Get answers from your peers along with millions of IT pros who visit Spiceworks.
Any assistance would be greatly appreciated! Avaya Cisco
Comments