Wireless Access

I upgraded my cable modem to a Netgear CM700 and my Aruba 7005 controller can no longer obtain a public IP from my ISP.  This was working on my old modem (a Motorola SB6120).

 

If I connect the same modem directly to a laptop, the laptop obtains a public IP OK.  I reboot the modem on each attempt (controller & laptop attempts) and have rebooted the controller several times.

 

I followed https://community.arubanetworks.com/t5/Command-of-the-Day/COTD-Connect-your-Aruba-Controller-to-a-Cable-Modem/m-p/951/highlight/true#M64 to get it set up in the first place.  Here's my relevant config:

 

 

vlan 100

interface vlan 100
  ip address dhcp-client
!

interface gigabitethernet 0/0/0
  switchport access vlan 100
!

interface vlan 100
  ip nat outside
!

# Route clients out the internet connection.
ip default-gateway import dhcp

 

It appears to do with the new modem assigning itself a management IP (192.168.100.20).  When I restart the modem, I get the following for about 30 seconds:

 

(Aruba7005) [mynode] (config) #show ip interface brief

Interface                   IP Address / IP Netmask        Admin   Protocol   VRRP-IP
vlan 1                     192.168.1.1 / 255.255.255.0     up      up
vlan 100                192.168.100.20 / 255.255.255.0     up      up
loopback                    unassigned / unassigned        up      up

DHCP is enabled on VLAN(s) 100

After the 30 seconds, it goes back to VLAN 100 being unassigned.

 

(Aruba7005) [mynode] (config) #show ip interface brief

Interface                   IP Address / IP Netmask        Admin   Protocol   VRRP-IP
vlan 1                     192.168.1.1 / 255.255.255.0     up      up
vlan 100                    unassigned / unassigned        up      up
loopback                    unassigned / unassigned        up      up

DHCP is enabled on VLAN(s) 100

The logs seem to pinpoint the problem (ignored DHCPREQUEST due to unknown subnet) but I'm not sure what they mean or how to resolve the problem.

 

May 21 00:46:45  fpapps[3359]: <399838> <3663> <WARN> |fpapps|  uplinkStateChangeCallback: intIfNum 1, ifType 3, event 6 usp 0/0/0
May 21 00:46:45  fpapps[3359]: <399838> <3663> <WARN> |fpapps|  uplinkStateChangeCallback: intIfNum 220, ifType 9, event 3 usp 0/4/2
May 21 00:46:45  fpapps[3359]: <399838> <3663> <WARN> |fpapps|  uplinkStateChangeCallback: intIfNum 220, ifType 9, event 6 usp 0/4/2
May 21 00:46:46  ntpwrap: getNtpSrvRouteAddr:304:connect() failed
May 21 00:46:51  fpapps[3359]: <399816> <3362> <ERRS> |fpapps|  ipmRouterIfCreate:: Entering with index 3 ifnum 220 ip 192.168.100.20 Current switchIpVlanId : 1
May 21 00:46:51  fpapps[3359]: <399816> <3362> <ERRS> |fpapps|  ipmRouterIfCreate:: Setting if_up to 1 within else...
May 21 00:47:01  fpapps[3359]: PAPI_Send: sendto DHCP Server failed: Connection refused Message Code 7007 Sequence Num is 9825
May 21 00:47:03  dhcpd: -> -> -> it is at dst_hmac_sha1_init : 1139
May 21 00:47:03  dhcpd: -> -> -> it is at dst_hmac_sha256_init : 1117
May 21 00:47:04  dhcpd[17922]: Vlan 100 entry already present
May 21 00:47:17  ntpwrap: ntpdPollingTimer:512 Upstream servers not reachable via local interface.
May 21 00:47:23  dhcpd: -> -> -> it is at dst_hmac_sha1_init : 1139
May 21 00:47:23  dhcpd: -> -> -> it is at dst_hmac_sha256_init : 1117
May 21 00:47:28  dhcpd[17999]: <299801> <17999> <DBUG> |dhcpd|  DHCPREQUEST for 192.168.100.20 from 00:0b:86:a8:a5:88 via eth1: ignored (unknown subnet).
May 21 00:47:30  dhcpd[17999]: Vlan 100 delete from database as IP became 0
May 21 00:47:30  fpapps[3359]: <399838> <3369> <WARN> |fpapps|  rtoCommonRouteDelete:1329: dest 0.0.0.0/0.0.0.0 not found in rto table
May 21 00:47:32  ntpwrap: getNtpSrvRouteAddr:304:connect() failed
May 21 00:47:32  ntpwrap: ntpdPollingTimer:512 Upstream servers not reachable via local interface.
May 21 00:47:43  dhcpd: -> -> -> it is at dst_hmac_sha1_init : 1139
May 21 00:47:43  dhcpd: -> -> -> it is at dst_hmac_sha256_init : 1117
May 21 00:47:47  ntpwrap: getNtpSrvRouteAddr:304:connect() failed

 

What do you get for interface config when you use the "show configuration effective /mm" command string?

Here's the relevant config.  Let me know if you need more.  I'm running 8.4.0.2 and it's mostly factory default except the interface config (as configured below).

 

# show configuration effective /mm/mynode

controller-ip vlan 1
controller-ipv6 vlan 1 address 2001::1
vlan 1
!
vlan 100
!
interface gigabitethernet 0/0/0
    description GE0/0/0
    switchport access vlan 100
    trusted
    trusted vlan 100
!
interface gigabitethernet 0/0/1
    description GE0/0/1
    trusted
    trusted vlan 1-4094
!
interface gigabitethernet 0/0/2
    trusted
    trusted vlan 1-4094
!
interface gigabitethernet 0/0/3
    trusted
    trusted vlan 1-4094
!
interface vlan 1
    ip address 192.168.1.1 255.255.255.0
    ip nat inside
    ipv6 address 2001::1/64
!
interface vlan 100
    ip address dhcp-client
    ip nat outside
!
ip default-gateway 73.158.246.1
!

service dhcp
ip dhcp pool local
    dns-server import
    default-router 192.168.1.1
    lease 1 0 0
    network 192.168.1.0 255.255.255.0
!

Is lldp enabled at the uplink to the isp router? Isp’s just allow some times one MAC address and with lldp enabled we see two Mac addresses in some cases.

not sure if this will break the DHCP in the way you saw, but it should be fixed up anyways. It appears your old modem was bridging through the ISP IP address range as you have a public ip here for def gw:

ip default-gateway 73.158.246.1

but the new modem, appears to be giving 192.168.100.20 which implies the new modem is doing it's own NAT, so delete the configured def gw 73.158.246.1 from the config and change it to "ip default-gateway import dhcp"

 

You probably dont need the ip nat outside on vlan 100, take it away for now and just leave the nat inside on vlan 1.

Thanks jgoff and Willem.  That default gateway was added manually by me after inspecting what the ISP gave when my laptop received a DHCP address.  I have since removed it and added "ip default-gateway import dhcp" as you suggested.

 

I also tried removing ip nat outside on vlan 100.  It didn't seem to help.  Other attempts I tried was to add a VLAN with 192.168.100.0/24 to get around the DHCP error, adding a DHCP pool of192.168.100.0/24, disabling DHCP altogether on the controller, disabling inter-VLAN routing on VLAN 100, and a few other things.  It changed some of the log messages but the end result was always the same.  The 0/0/0 interface would get a 192.168.100.20 IP for a few seconds and then go back to unassigned after.

 

I ended up giving up for now and connecting a cheap gigabit router to the modem and then putting the Aruba controller downstream.  I could try the LLDP in future but not really sure how to configure it.