Instant On - Wired

Hi everyone,

some weird issue with a 1930 switch and Avaya option 242.

We have 2 Vlans (actually more, but only these 2 are concerned), Data (1, all ports untagged) and Voice (22, all ports tagged, except the uplink to the Vlan 22 interface on the firewall).

DHCP for both Vlans is on our Windows server Vlan, relayed by a pfSense firewall.

Setup is quite standard: DHCP on Vlan 1 sends option 242 (L2Q=1,L2QVLAN=22) to put the Avaya phones in Vlan 22, where another option 242 sets the ip address of the Avaya server.

This all works normally on our HPE 1920S switches.

We had to add an additional switch, and since the 1920S is no longer available, decided on the 1930.

Any phone we connect to the 1930 in Vlan 1 gets an ip from the DHCP server , but the option 242 is not set, and the phone does not switch to Vlan 22.

Manually putting the phone in Vlan 22 works, so it does get the option 242 in the voice vlan.

Is there anything on the 1930 switch which would allow DHCP to work, but somehow prevent the option 242 to pass on the default Vlan?

Plug the same phone into an older switch, and it just works, plug it back into the 1930 and it stays in Vlan 1.

This issue is expanding, since we are deploying the 1930 (and in the future 1830) switches to all our sites, 15 in total.

Yesterday i've deployed Avaya J100 series phones in 3 more sites, with slightly different setup from our main site, where the original issue occurs.

Those sites do not use a DHCP relay, but Vlan1 DHCP is on the Windows server, and Vlan22 on the firewall (Ubiquity Edgerouter POE).

2 sites, with only HP switches, worked without a problem, the third, with an Aruba 1930, has an issue, similar to the one above.

Here the phone gets an IP + Vlan settings from Vlan1 DHCP, it switches to Vlan22 (this can also be confirmed on the switch port), but then fails to get a new IP from Vlan22 DHCP.

I've put a laptop in a port with Vlan22 untagged, and it gets an ip without a problem, so the DHCP works.

So at this time it looks like there is some issue when using multiple Vlans on a port and DHCP, when using an Aruba 1930 in combination with Avaya IP phones.

Hi everyone,

some weird issue with a 1930 switch and Avaya option 242.

We have 2 Vlans (actually more, but only these 2 are concerned), Data (1, all ports untagged) and Voice (22, all ports tagged, except the uplink to the Vlan 22 interface on the firewall).

DHCP for both Vlans is on our Windows server Vlan, relayed by a pfSense firewall.

Setup is quite standard: DHCP on Vlan 1 sends option 242 (L2Q=1,L2QVLAN=22) to put the Avaya phones in Vlan 22, where another option 242 sets the ip address of the Avaya server.

This all works normally on our HPE 1920S switches.

We had to add an additional switch, and since the 1920S is no longer available, decided on the 1930.

Any phone we connect to the 1930 in Vlan 1 gets an ip from the DHCP server , but the option 242 is not set, and the phone does not switch to Vlan 22.

Manually putting the phone in Vlan 22 works, so it does get the option 242 in the voice vlan.

Is there anything on the 1930 switch which would allow DHCP to work, but somehow prevent the option 242 to pass on the default Vlan?

Plug the same phone into an older switch, and it just works, plug it back into the 1930 and it stays in Vlan 1.

I have worked on the DHCP strings for J series phones at a couple of previous employers.  What DHCP strings do you have in Option 242 on each VLAN?

This issue is expanding, since we are deploying the 1930 (and in the future 1830) switches to all our sites, 15 in total.

Yesterday i've deployed Avaya J100 series phones in 3 more sites, with slightly different setup from our main site, where the original issue occurs.

Those sites do not use a DHCP relay, but Vlan1 DHCP is on the Windows server, and Vlan22 on the firewall (Ubiquity Edgerouter POE).

2 sites, with only HP switches, worked without a problem, the third, with an Aruba 1930, has an issue, similar to the one above.

Here the phone gets an IP + Vlan settings from Vlan1 DHCP, it switches to Vlan22 (this can also be confirmed on the switch port), but then fails to get a new IP from Vlan22 DHCP.

I've put a laptop in a port with Vlan22 untagged, and it gets an ip without a problem, so the DHCP works.

So at this time it looks like there is some issue when using multiple Vlans on a port and DHCP, when using an Aruba 1930 in combination with Avaya IP phones.

Hi everyone,

some weird issue with a 1930 switch and Avaya option 242.

We have 2 Vlans (actually more, but only these 2 are concerned), Data (1, all ports untagged) and Voice (22, all ports tagged, except the uplink to the Vlan 22 interface on the firewall).

DHCP for both Vlans is on our Windows server Vlan, relayed by a pfSense firewall.

Setup is quite standard: DHCP on Vlan 1 sends option 242 (L2Q=1,L2QVLAN=22) to put the Avaya phones in Vlan 22, where another option 242 sets the ip address of the Avaya server.

This all works normally on our HPE 1920S switches.

We had to add an additional switch, and since the 1920S is no longer available, decided on the 1930.

Any phone we connect to the 1930 in Vlan 1 gets an ip from the DHCP server , but the option 242 is not set, and the phone does not switch to Vlan 22.

Manually putting the phone in Vlan 22 works, so it does get the option 242 in the voice vlan.

Is there anything on the 1930 switch which would allow DHCP to work, but somehow prevent the option 242 to pass on the default Vlan?

Plug the same phone into an older switch, and it just works, plug it back into the 1930 and it stays in Vlan 1.

in vlan1: L2Q=1,L2QVLAN=22,VLANTEST=0

in 22: MCIPADD=10.245.0.97,MCPORT=1719,HTTPSRVR=10.245.0.97

I've done some more testing, and now things are getting even more bizar. I enabled port mirroring and did some capturing with wireshark, which showed me that the option 242 is coming through on all the switches, 1930's included.

The phone that was plugged while i was capturing, got set up perfectly, even when connected on the Aruba. Later i moved it to another port, configured exactly the same, and it wouldn't get out of the Data vlan anymore, even on an HP switch.

So I'm starting to wonder if it's the phones themselves that are acting up, but I can't find any consistency in the behaviour, especially at our main site. First it appeared that it only worked on the HP switches, but now i have had successes and failures on both types. 

I'm beginning to think I may have to check on the Avaya server, to make sure it's not setting any options that override what i send by DHCP. And that that's maybe the reason why i can get a phone configured after a factory reset, but it won't work anymore when moving to a different port, which has the exact same Vlan configuration.

I have worked on the DHCP strings for J series phones at a couple of previous employers.  What DHCP strings do you have in Option 242 on each VLAN?

This issue is expanding, since we are deploying the 1930 (and in the future 1830) switches to all our sites, 15 in total.

Yesterday i've deployed Avaya J100 series phones in 3 more sites, with slightly different setup from our main site, where the original issue occurs.

Those sites do not use a DHCP relay, but Vlan1 DHCP is on the Windows server, and Vlan22 on the firewall (Ubiquity Edgerouter POE).

2 sites, with only HP switches, worked without a problem, the third, with an Aruba 1930, has an issue, similar to the one above.

Here the phone gets an IP + Vlan settings from Vlan1 DHCP, it switches to Vlan22 (this can also be confirmed on the switch port), but then fails to get a new IP from Vlan22 DHCP.

I've put a laptop in a port with Vlan22 untagged, and it gets an ip without a problem, so the DHCP works.

So at this time it looks like there is some issue when using multiple Vlans on a port and DHCP, when using an Aruba 1930 in combination with Avaya IP phones.

Hi everyone,

some weird issue with a 1930 switch and Avaya option 242.

We have 2 Vlans (actually more, but only these 2 are concerned), Data (1, all ports untagged) and Voice (22, all ports tagged, except the uplink to the Vlan 22 interface on the firewall).

DHCP for both Vlans is on our Windows server Vlan, relayed by a pfSense firewall.

Setup is quite standard: DHCP on Vlan 1 sends option 242 (L2Q=1,L2QVLAN=22) to put the Avaya phones in Vlan 22, where another option 242 sets the ip address of the Avaya server.

This all works normally on our HPE 1920S switches.

We had to add an additional switch, and since the 1920S is no longer available, decided on the 1930.

Any phone we connect to the 1930 in Vlan 1 gets an ip from the DHCP server , but the option 242 is not set, and the phone does not switch to Vlan 22.

Manually putting the phone in Vlan 22 works, so it does get the option 242 in the voice vlan.

Is there anything on the 1930 switch which would allow DHCP to work, but somehow prevent the option 242 to pass on the default Vlan?

Plug the same phone into an older switch, and it just works, plug it back into the 1930 and it stays in Vlan 1.