interface eth 0/14
switchport mode trunk
switchport voice vlan 2
Make sure that LLDP is enabled in the switch, that will tell the phone to use VLAN 2 for voice and pass the native VLAN to the PC port.
No Joy. I have tried this before did it again to be thorough. This gives both phone and PC 10.10.11.x address.
The NetVanta enables LLDP by default I believe. All options are checked in the advertisements section of LLDP.
Any other ideas?
Check the phone configuration to verify that LLDP is active and the voice VLAN is selected by LLDP. Does the switch see the phone as an LLDP neighbor? If LLDP isn't supported on the phone set the voice VLAN in the phone configuration to 2.
Does the Adtran IP706 have these settings?
The 7100 doesn't seem to recognize any phone neighbors. Its sees an Access Point and another switch, but no other neighbors.
This doesnt make sense, everything is Adtran so why isnt this working natively without manually setting the phones VLAN?
Well, I looked at the IP706 manual here: https://portal.adtran.com/pub/Library/Reference_Guides/Default/ADTRAN%20IP%20700%20Series%20Admin%20Guide.pdf
There's no mention of LLDP so presumably the phone doesn't support it. Page 26 shows the network settings from the phone's web interface. By default, VLAN tagging is off and (if enabled) it would use VLAN 400. And, it says that this can be configured from DHCP, the phone interface, or the web interface.
I see that you have a DHCP option 157 with the proper information, but that string is in the Voice pool which is presented on the interface as tagged. Because the phone boots with the default untagged setting, it will try to boot using the untagged DHCP server which doesn't have the options. I would add this to the Data DHCP settings:
ip dhcp pool "Data"
option 157 ascii Layer2Tagging=True,VlanID=2
You probably don't need to put all of the FTP parameters here but if the phone doesn't pull FTP then you might. The idea is that at boot, the phone will pull the option 157 info from the default untagged DHCP pool, then switch to tagged VLAN 2 and re-initiate DHCP where it should pull the full new string with FTP data (and the same VLAN data).
Give this a shot.
Personal note: I don't know what Adtran was thinking. DHCP is a really dumb way to do this. If this indeed works and I suspect it will, it means that you're required to set a DHCP option on a scope, VLAN, and subnet that the phone will never use! Hopefully and presumably the data devices using native VLAN 1 and its DHCP server will simply ignore that option.
DHCP is a Layer 3 protocol and in this case it is being used to set a Layer 2 parameter. That's backwards. The VLAN should be assigned before the phone even sends a DHCPDISCOVER packet. LLDP or Brand C's semi-proprietary CDP are much better suited. If you don't want to deal with the DHCP ugly hack, you can set tagging on and the VLAN from the web interface or the phone menu and then save it. Settings from the phone menu or web interface take precedence over DHCP. This of course requires touching every phone.
It doesn't look like tagging or VLAN can be set from the configuration file which makes sense. In order to pull that file, the phone needs to already be on the right VLAN and have an IP address.
EDIT: You'll need to keep the switch ports configured as trunks. Because the phones don't do LLDP, the switch won't know to enable the voice VLAN.
Sorry for the delay. I will try adding the option 157 to the Data DHCP pool tonight and let you know.
This does seem backwards but I hope it works.
Still can't believe it but that worked! Thanks for your help jayh.