This post is more than 5 years old
20 Posts
0
40855
August 21st, 2012 14:00
PowerConnect 6248P DHCP problems on VLAN
Hello,
I have a powerconnect 6248P.
It has several VLANS, but recently, we have been having issues with our phones. Regardless if the VLAN is native or a trunk and its traffic tagged. Some phones are unable to get an IP address. The following error message appears in the buffer log;
DHCP client message received on port 1/0/17 VLAN 40 from client 00:04:f2:31:aa:e4 has giaddr set to local address 192.168.4.1. Dropping.
The switch is the router as well for several of the VLANS. It seems only the phones are having issues.
Please advise.
No Events found!
HH2011
20 Posts
1
August 23rd, 2012 16:00
Flash was bad.
Power cycled the switch that night after hours, it never came back up. I had to push the firmware via xmodem but I was getting some driver errors and the switch would not boot to an operational status.
Replacement switch arrived and all those issues went away :)
DELL-Willy M
802 Posts
0
August 21st, 2012 15:00
I would start with making sure you have the current version of firmware on the switch.
Firmware download version 3.3.4.1 released 7/25/12
www.dell.com/.../powerconnect-6248p
Are your phones set up on a Voice VLAN? If so be aware the Voice VLAN feature can only be used by IP phones that support LLDP-MED, e.g. 4610SW Avaya phones.
Here is a white paper on the set up of Voice VLAN on the 6200 switches.
www.dell.com/.../pwcnt_voice_VLAN_support.pdf
Are you using the IP helper command to relay DHCP on the switch?
For DHCP you want to use the IP helper command.
Example
To relay DHCP packets received on any interface to two
DHCP servers, 10.1.1.1 and 10.1.2.1, use the following
commands:
console#config
console(config)#ip helper-address 10.1.1.1 dhcp
console(config)#ip helper-address 10.1.2.1 dhcp
Hope this helps,
Keep us updated if you can.
HH2011
20 Posts
0
August 21st, 2012 15:00
The switch is configured to forward the DHCP requests to a defined server as well.
HH2011
20 Posts
0
August 21st, 2012 16:00
Yes I am using the IP helper command.
No I am not using the built in voice vlan feature. I have PBXs and other Voice devices on that segment.
I am most certainly not on the latest firmware, I will see about applying it some time this week.
The strange thing is, that other phones work, while a handful are experiencing this problem. For example, my phone operates as expected. It pulls an IP via DHCP on the same physical port, that the other phone gets the error message I posted earlier.
DELL-Willy M
802 Posts
1
August 21st, 2012 17:00
Did the phones with the issue pull an IP normally at some time? Did this just start happening recently? Is it a certain brand or phone manufacturer that is having the errors?
Sounds like a firmware update would be good at this time.
HH2011
20 Posts
0
August 21st, 2012 17:00
Ok, I am thinking something is amiss with the software or hardware.
Switch is locked up right now. I was copying the running config and it locked up on me.
Can not access it via HTML, TELNET or Serial.
It's still functioning though, but I am going to have to cold boot it here after hours.
HH2011
20 Posts
0
August 21st, 2012 17:00
It seems to be randomly happening to certain phones.
It can be a new phone, never provisioned before, or I can move an end point to a different physical location, and when it comes back up, this happens.
DELL-Willy M
802 Posts
1
August 23rd, 2012 17:00
It's good to here you have resolved the issues you were having.
Thanks for updating the Post and creating a great environment for customers to find solutions.