-
1
- #1
Hi Everyone,
We are having some issues with 1140e phones at a new site with DHCP and vlans.
The site has a CS1000 which is linked to another site which acts as the S2 if local CS1000 fails. The DHCP servers is a Windows 2008 R2 server and the switches are Cisco PoE models.
We have configured 2 separate VLANs for the phones and another for the PC's and we are using the DHCP option 191 to advertise the VLANs and option 128 (Nortel-i2004-A) to provide the S1 and S2 servers, ports and actions.
If we set the phone to be fully auto, with a voice vlan scope enabled and both DCHP options enabled. The phone waits on starting DHCP... Looking at the network diagnostic tools, it has correctly detected the voice VLAN and can see the correct advertisement options but it still has the PC VLAN address. However, the DHCP server lists the phone as having a lease in the Voice VLAN.
If we turn off the voice VLAN advertisement and disable the voice VLAN scope but leave the option 128 on, the phones work but are obviously in the wrong VLAN.
If I manually set the voice VLAN on the phone and have the voice VLAN scope enabled with the option 128 on, works correctly. The phone picks an address from the Voice VLAN and registers with the S1 server.
It seems to be an issue with either DHCP or the phones switching between the VLANs. The phone firmware doesn't seem to make a difference at it affects both phones out of the box and phones which have updated their firmware.
What is confusing us is we have copied the DHCP options from the sister site (except for the necessary change of VLAN number) where the phones register via DHCP correctly. On that site options 128 and 191 are advertised on the the data VLAN and the voice VLANs, suspect this isn't quite right.
Any ideas? Ideally I would like to just be able to plug in a phone and for it to work without any manual settings.
We are having some issues with 1140e phones at a new site with DHCP and vlans.
The site has a CS1000 which is linked to another site which acts as the S2 if local CS1000 fails. The DHCP servers is a Windows 2008 R2 server and the switches are Cisco PoE models.
We have configured 2 separate VLANs for the phones and another for the PC's and we are using the DHCP option 191 to advertise the VLANs and option 128 (Nortel-i2004-A) to provide the S1 and S2 servers, ports and actions.
If we set the phone to be fully auto, with a voice vlan scope enabled and both DCHP options enabled. The phone waits on starting DHCP... Looking at the network diagnostic tools, it has correctly detected the voice VLAN and can see the correct advertisement options but it still has the PC VLAN address. However, the DHCP server lists the phone as having a lease in the Voice VLAN.
If we turn off the voice VLAN advertisement and disable the voice VLAN scope but leave the option 128 on, the phones work but are obviously in the wrong VLAN.
If I manually set the voice VLAN on the phone and have the voice VLAN scope enabled with the option 128 on, works correctly. The phone picks an address from the Voice VLAN and registers with the S1 server.
It seems to be an issue with either DHCP or the phones switching between the VLANs. The phone firmware doesn't seem to make a difference at it affects both phones out of the box and phones which have updated their firmware.
What is confusing us is we have copied the DHCP options from the sister site (except for the necessary change of VLAN number) where the phones register via DHCP correctly. On that site options 128 and 191 are advertised on the the data VLAN and the voice VLANs, suspect this isn't quite right.
Any ideas? Ideally I would like to just be able to plug in a phone and for it to work without any manual settings.