10-02-2014 04:52 AM - edited 10-02-2014 05:01 AM
It is first time I use this Instant AP/Virtual Controller, only used physical controllers before...
I have 2 loaner units from Aruba partner, the RAP109. I configured first one as the Master and powered up the second one with statically assigned IP(same subnet as master). But the Second one doesnot seem even try to join the controller (it show "i am master now" in console after booting up).
Do I need to convert them to IAP first? I thought that model is by default running as virtual controller...
The master is running 18.104.22.168-22.214.171.124_45704 and the second AP is running 126.96.36.199-188.8.131.52_39461. I thought the second AP should join Controller and upgrade the firmware. So do I need to manually upgrade firmware first?
I used IP from the same subnet as the management IP of AP as the virtual controller IP. Will this work OR I need to use a IP from different subnet?
10-02-2014 10:42 AM
10-02-2014 11:35 AM
I think I could do that but the other issue will be: how do I get the firmware...thay are loaners.
Can I download firmware from the master AP itself via TFTP?
10-03-2014 11:29 AM - edited 10-03-2014 12:56 PM
Got both AP onto the same version now (factory reset second AP after the upgrade). It seems like the second AP is running as slave now but somehow the second AP doesnot show on the virtual controller UI page.
From console, it does seem like the second AP detects the master and switched it to slave and then send following.
<<<<< Welcome to the Access Point >>>>>
User: asap_send_elected_master: sent successfully
process `snmpd_sap' is using obsolete setsockopt SO_BSDCOMPAT
wait for stm to initialize over
asap_send_elected_master: sent successfully
Tried to disable auto-join on virtual controller and manually add the second AP but still not managable...
Then nothing else showing on console...Please help!!!