02-15-2013 09:16 AM
I have a strange issue that I'm hoping I can get some help with. I am currently deploying Rap3s, and would like to use the Poe port for a VOIP phone deployment for a complete remote solution for our sales folks. The problem I'm having is that the shortel phone gets an IP on the right VLAN, but then simply reboots, and hangs on attempting to get dhcp again.
I plugged my laptop into the eth2 port, and I am indeed able to get the proper IP address, and traffic is flowing perfectly (I'm actually using it to type this up). DHCP is being handed out by an external server, and IP helper is configured for that VLAN on the controller (hence why I'm getting dhcp). I've confirmed that the IP address is being handed out by the correct server.
Is it possible that the DHCP options are being dropped somehow? When I plug in the same phone locally, it gets an IP on the same scope, but starts booting properly.
02-15-2013 09:27 AM
While the phone was booting, it got an IP of "192.168.x.60", but when I take a look at either DHCP servers, they do not have an IP address handed out for .60... Strange.
02-15-2013 10:55 AM
Does that phone expect to be on a trunk port or an access port?
Aruba Customer Engineering
Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base
02-19-2013 11:20 AM
one more thing, my network logs on the controller are filled with these:
<DBUG> |dhcpdwrap| DHCPDISCOVER from x:x:x:x:x:x via eth1: unknown network segment
These are all coming from any MAC behind the rap.