We have two masters on our network, accessible from any building in the WAN. It keeps finding the master IP address ending in .48, but I need it on .50. When I log onto either, it doesn't show up in the Installation page. It only shows up in the Monitoring > All Access Points as "down" status. I have the option to clear it, but that doesn't allow it to come up on a reboot.
Starting watchdog process...
Getting an IP address...
ag7100_ring_alloc Allocated 4800 at 0x803cc000
ag7100_ring_alloc Allocated 3024 at 0x86951000
AG7100: cfg1 0xf cfg2 0x7014
ATHRF1: Port 0, Neg Success
ATHRF1: unit 0 phy addr 0 ATHRF1: reg0 3100
AG7100: unit 0 phy is up...RGMii 1000Mbps full duplex
AG7100: pll reg 0x18050010: 0x110000 AG7100: cfg_1: 0x1ff0000
AG7100: cfg_2: 0x3ff
AG7100: cfg_3: 0x18001ff
AG7100: cfg_4: 0xffff
AG7100: cfg_5: 0xfffef
AG7100: done cfg2 0x7215 ifctl 0x0 miictrl 0x22
Writing 4
10.1.100.143 255.255.0.0 10.1.255.254
Running ADP...Done. Master is 10.1.10.48
ath_hal: 0.9.17.1 (AR5416, AR9380, REGOPS_FUNC, PRIVATE_DIAG, WRITE_EEPROM, 11D)
ath_rate_atheros: Copyright (c) 2001-2005 Atheros Communications, Inc, All Rights Reserved
ath_rate_atheros: Aruba Networks Rate Control Algorithm
ath_dfs: Version 2.0.0
Copyright (c) 2005-2006 Atheros Communications, Inc. All Rights Reserved
ath_spectrum: Version 2.0.0
Copyright (c) 2005-2006 Atheros Communications, Inc. All Rights Reserved
ath_dev: Copyright (c) 2001-2007 Atheros Communications, Inc, All Rights Reserved
ath_pci: 0.9.4.5 (Atheros/multi-bss)
ath_pci: cannot reserve PCI memory region
ath_ahb: 0.9.4.5 (Atheros/multi-bss)
Starting FIPS KAT ... Failed FIPS KAT.
AP rebooted Fri Dec 31 16:05:21 PST 1999; SAPD: Reboot after successful image upgrade
shutting down watchdog process (nanny will restart it)...
Is this enough of the boot log?