Avaya IP Phones not picking the designated voice VLAN

[abdulwahabavaya]

We are facing an issue for Avaya IP Phones VLAN detection. Customer has multiple (100+ VLANs Data and Voice). When a phone is connected, it should get the respective voice VLAN according to the DHCP Option 242 defined individually for each department/floor. In our scenario, the phones are taking the default voice VLAN.
They have Windows DHCP Server and below is the sample of DHCP Option 242 Configuration for one department:

Data Scope (VLAN 20)
Option 242 String: "L2Q=1,L2QVLAN=30,VLANTEST=60"

Voice Scope (VLAN 30)
Option 242 String: "MCIPADD=<CM's IP>,MCPORT=1719,HTTPSRVR=<AADS's IP>,TLSSRVR=<AADS's IP>,VLANTEST=60"

Can someone guide me, if there's something wrong with this setup? Because we try to factory reset the phones and they still get the default voice vlan which has been changed from the network team. It was one single voice vlan throughout the company but now each department/floor has their own voice vlan. The phone models that we are using are 9600 Series IP Phones and J100 Series SIP Phones.

 

[dialtonebone]

Hi - do you have LLDP enabled on your L2 bridge/data switch? If so, is it advertising a voice VLAN to the phones? There is a great chance the phone is picking up the LLDP values before it even gets to the DHCP steps.

 

[Abdul Wahab Waheed]

Hi - do you have LLDP enabled on your L2 bridge/data switch? If so, is it advertising a voice VLAN to the phones? There is a great chance the phone is picking up the LLDP values before it even gets to the DHCP steps.

As per the customer's network team they have LLDP enabled. As they have mix of switches vendor so they have mix of LLDP and CDP enabled, depending on the switch. But I will check again with them. If it's advertising, then what do they have to do? Disable it?

 

[dialtonebone]

As per the customer's network team they have LLDP enabled. As they have mix of switches vendor so they have mix of LLDP and CDP enabled, depending on the switch. But I will check again with them. If it's advertising, then what do they have to do? Disable it?

At minimum, they need to stop advertising the voice VLAN via the LLDP protocol.
Ideally, they reprogram it per port (just like they are likely doing anyways with the per port VLAN programming) to advertise the correct VLAN. Then you get to skip 1 DHCP step.

Keep the two scopes of course (voice and data) but having LLDP help can speed boot up time and takes the first network's DHCP out of the scenario.