Mailing List Archive

7960 and 3550 Trunking/VLAN
In one of our remote offices, new phones are not coming up in the call
manager.
We have a 2651XM providing DHCP on VLAN 4 (the voice VLAN) and it's also
on VLAN 1, the data/server/pc VLAN.
Initial troubleshooting is showing:
1) DHCP Requests are making it to the router, but the phone isn't
finalizing the lease
2) Our Windows Server, which provides DHCP to the PCs (on VLAN 1) is
receiving the DHCP requests and providing an IP address for the 7960.
3) The 7960 gets a VLAN 1 Subnet IP address but it's in VLAN 4.

So both VLANS are getting the DHCP broadcast, but it looks like the
windows server is winning out.
VLAN 1 should not be receiving a DHCP broadcast.

This is how the phones port (Fa0/5) is configured on the 3550 switch:
interface FastEthernet0/5
description VLAN1+Aux4 w/Power
switchport mode access
switchport voice vlan 4
no ip address
spanning-tree portfast

I set "switchport access vlan 4" so that both the data and voice vlans
were on vlan 4.
Only then did it come up with the right DHCP address and register to the
CM.
After it comes up, you can switch back to VLAN 1 and it works fine.

This is happening with EVERY new phone I add. The existing phones are
totally happy and have been for several months. All phones on that
location are preconfigured before they are on location. These are the
first phones that were not preconfigured.

The 2651 does not have boothelper configured or anything like that.
It's very basic with a simple DHCP command.
ip dhcp excluded-address 10.24.4.0 10.24.4.255
ip dhcp excluded-address 10.24.6.0 10.24.7.255
!
ip dhcp pool DHCP-VOIP-VLAN4
network 10.24.4.0 255.255.252.0
dns-server 10.24.0.32 10.10.0.11 10.10.0.19
option 150 ip 10.8.4.10 10.8.4.11
default-router 10.24.4.1

The "no ip bootp server" command is set, but phones should use BootP,
not DHCP, right? The existing phones work just fine and get their IP
addresses just fine as well.

-=Vandy=-
7960 and 3550 Trunking/VLAN [ In reply to ]
In one of our remote offices, new phones are not coming up in the call
manager.
We have a 2651XM providing DHCP on VLAN 4 (the voice VLAN) and it's also
on VLAN 1, the data/server/pc VLAN.
Initial troubleshooting is showing:
1) DHCP Requests are making it to the router, but the phone isn't
finalizing the lease
2) Our Windows Server, which provides DHCP to the PCs (on VLAN 1) is
receiving the DHCP requests and providing an IP address for the 7960.
3) The 7960 gets a VLAN 1 Subnet IP address but it's in VLAN 4.

So both VLANS are getting the DHCP broadcast, but it looks like the
windows server is winning out.
VLAN 1 should not be receiving a DHCP broadcast.

This is how the phones port (Fa0/5) is configured on the 3550 switch:
interface FastEthernet0/5
description VLAN1+Aux4 w/Power
switchport mode access
switchport voice vlan 4
no ip address
spanning-tree portfast

I set "switchport access vlan 4" so that both the data and voice vlans
were on vlan 4.
Only then did it come up with the right DHCP address and register to the
CM.
After it comes up, you can switch back to VLAN 1 and it works fine.

This is happening with EVERY new phone I add. The existing phones are
totally happy and have been for several months. All phones on that
location are preconfigured before they are on location. These are the
first phones that were not preconfigured.

The 2651 does not have boothelper configured or anything like that.
It's very basic with a simple DHCP command.
ip dhcp excluded-address 10.24.4.0 10.24.4.255
ip dhcp excluded-address 10.24.6.0 10.24.7.255
!
ip dhcp pool DHCP-VOIP-VLAN4
network 10.24.4.0 255.255.252.0
dns-server 10.24.0.32 10.10.0.11 10.10.0.19
option 150 ip 10.8.4.10 10.8.4.11
default-router 10.24.4.1

The "no ip bootp server" command is set, but phones should use BootP,
not DHCP, right? The existing phones work just fine and get their IP
addresses just fine as well.

-=Vandy=-
RE: 7960 and 3550 Trunking/VLAN [ In reply to ]
I'm not sure but I think the phones have to get a new firmware update to send the right cdp packets to let the switch know they should be on a voice vlan.

scott

-----Original Message-----
From: Vandy Hamidi [mailto:vandy.hamidi@markettools.com]
Sent: Mon 3/15/2004 6:39 PM
To: cisco-voip@puck.nether.net
Cc:
Subject: [cisco-voip] 7960 and 3550 Trunking/VLAN



In one of our remote offices, new phones are not coming up in the call
manager.
We have a 2651XM providing DHCP on VLAN 4 (the voice VLAN) and it's also
on VLAN 1, the data/server/pc VLAN.
Initial troubleshooting is showing:
1) DHCP Requests are making it to the router, but the phone isn't
finalizing the lease
2) Our Windows Server, which provides DHCP to the PCs (on VLAN 1) is
receiving the DHCP requests and providing an IP address for the 7960.
3) The 7960 gets a VLAN 1 Subnet IP address but it's in VLAN 4.

So both VLANS are getting the DHCP broadcast, but it looks like the
windows server is winning out.
VLAN 1 should not be receiving a DHCP broadcast.

This is how the phones port (Fa0/5) is configured on the 3550 switch:
interface FastEthernet0/5
description VLAN1+Aux4 w/Power
switchport mode access
switchport voice vlan 4
no ip address
spanning-tree portfast

I set "switchport access vlan 4" so that both the data and voice vlans
were on vlan 4.
Only then did it come up with the right DHCP address and register to the
CM.
After it comes up, you can switch back to VLAN 1 and it works fine.

This is happening with EVERY new phone I add. The existing phones are
totally happy and have been for several months. All phones on that
location are preconfigured before they are on location. These are the
first phones that were not preconfigured.

The 2651 does not have boothelper configured or anything like that.
It's very basic with a simple DHCP command.
ip dhcp excluded-address 10.24.4.0 10.24.4.255
ip dhcp excluded-address 10.24.6.0 10.24.7.255
!
ip dhcp pool DHCP-VOIP-VLAN4
network 10.24.4.0 255.255.252.0
dns-server 10.24.0.32 10.10.0.11 10.10.0.19
option 150 ip 10.8.4.10 10.8.4.11
default-router 10.24.4.1

The "no ip bootp server" command is set, but phones should use BootP,
not DHCP, right? The existing phones work just fine and get their IP
addresses just fine as well.

-=Vandy=-



_______________________________________________
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
RE: 7960 and 3550 Trunking/VLAN [ In reply to ]
You might be running into this bug CSCed44601 if your running Skinny or
Sip.

Scott

-----Original Message-----
From: Vandy Hamidi [mailto:vandy.hamidi@markettools.com]
Sent: Monday, March 15, 2004 6:18 PM
To: cisco-voip@puck.nether.net
Subject: [cisco-voip] 7960 and 3550 Trunking/VLAN

In one of our remote offices, new phones are not coming up in the call
manager.
We have a 2651XM providing DHCP on VLAN 4 (the voice VLAN) and it's also
on VLAN 1, the data/server/pc VLAN.
Initial troubleshooting is showing:
1) DHCP Requests are making it to the router, but the phone isn't
finalizing the lease
2) Our Windows Server, which provides DHCP to the PCs (on VLAN 1) is
receiving the DHCP requests and providing an IP address for the 7960.
3) The 7960 gets a VLAN 1 Subnet IP address but it's in VLAN 4.

So both VLANS are getting the DHCP broadcast, but it looks like the
windows server is winning out.
VLAN 1 should not be receiving a DHCP broadcast.

This is how the phones port (Fa0/5) is configured on the 3550 switch:
interface FastEthernet0/5
description VLAN1+Aux4 w/Power
switchport mode access
switchport voice vlan 4
no ip address
spanning-tree portfast

I set "switchport access vlan 4" so that both the data and voice vlans
were on vlan 4.
Only then did it come up with the right DHCP address and register to the
CM.
After it comes up, you can switch back to VLAN 1 and it works fine.

This is happening with EVERY new phone I add. The existing phones are
totally happy and have been for several months. All phones on that
location are preconfigured before they are on location. These are the
first phones that were not preconfigured.

The 2651 does not have boothelper configured or anything like that.
It's very basic with a simple DHCP command.
ip dhcp excluded-address 10.24.4.0 10.24.4.255
ip dhcp excluded-address 10.24.6.0 10.24.7.255
!
ip dhcp pool DHCP-VOIP-VLAN4
network 10.24.4.0 255.255.252.0
dns-server 10.24.0.32 10.10.0.11 10.10.0.19
option 150 ip 10.8.4.10 10.8.4.11
default-router 10.24.4.1

The "no ip bootp server" command is set, but phones should use BootP,
not DHCP, right? The existing phones work just fine and get their IP
addresses just fine as well.

-=Vandy=-



_______________________________________________
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip