Hi,
I have configured a 3200XM controller that I want my AP-125 to talk to. Instead of going the DHCP route, I decided to just assign the AP a static IP and it seems to connect to the controller. The AP shows up in the AP list but it only shows a status of "up" for about 20-30 seconds after it is rebooted. After that, it shows a "down" status and does not recover unless I log in to the AP CLI and give it a reboot.
On the CLI I see:
eth1: 1Gbs Full duplex, port 0, queue 0
shutting down watchdog process (nanny will restart it)...
ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
bonding: bond0: link status definitely up for interface eth1.
bonding: bond0: making interface eth1 the new active one.
<<<<< Welcome to the Access Point >>>>>
~ # cert_cap=1
vap aruba000 vlan is 0. discovering tunnel vlan
vap aruba100 vlan is 0. discovering tunnel vlan
bonding: bond0: releasing active interface eth1
bonding: bond0: now running without any active interface !
ADDRCONF(NETDEV_UP): eth1: link is not ready
ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
eth1: Link down
ADDRCONF(NETDEV_UP): eth1: link is not ready
eth1: 1Gbs Full duplex, port 0, queue 0
ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
I am only connecting the ETH1 interface on the AP to the second port on the controller. I don't understand why it goes from:
eth1: link becomes ready <<I assume this is when it is shown as the "up" status on the controller
to a few lines later:
releasing active interface eth1
Why is it releasing the interface?
Thanks
#3200