to learn it, I did some test:
- apply two xiq account: a trail pilot account and a free connect account
- add and config an ap in xiq connect account;
- export xiq connect viq(eg. vhm-connect);
- import viq(eg. vhm-connect) to xiq pilot account;Now, the ap is on two xiq account's inventory.
- reboot the ap, it will on board the xiq connect account. that was as my expect.
- delete it from the xiq connect's inventory, and reboot the ap.
The ap can not on board the xiq pilot's viq. I check the xiq pilot's inventory status. but weired, the ap's light is white, and here is the result of `show capwap client`:
AH-2a1440#show capwap client
CAPWAP client: Enabled
CAPWAP transport mode: UDP
RUN state: Connected securely to the CAPWAP server
CAPWAP client IP: 192.168.9.216
CAPWAP server IP: 188.8.131.52
HiveManager Primary Name:ia-gcp-cws-3.extremecloudiq.com
HiveManager Backup Name: ia-gcp-cwm.extremecloudiq.com
CAPWAP Default Server Name: redirector.aerohive.com
Virtual HiveManager Name:
Server destination Port: 12222
CAPWAP send event: Enabled
CAPWAP DTLS state: Enabled
CAPWAP DTLS negotiation: Enabled
DTLS next connect status: Enable
DTLS always accept bootstrap passphrase: Enabled
DTLS session status: Connected
DTLS key type: passphrase
DTLS session cut interval: 5 seconds
DTLS handshake wait interval: 60 seconds
DTLS Max retry count: 3
DTLS authorize failed: 0
DTLS reconnect count: 0
Discovery interval: 5 seconds
Heartbeat interval: 30 seconds
Max discovery interval: 10 seconds
Neighbor dead interval:105 seconds
Silent interval: 15 seconds
Wait join interval: 60 seconds
Discovery count: 0
Max discovery count: 3
Retransmit count: 0
Max retransmit count: 2
Primary server tries: 0
Backup server tries: 0
Keepalives lost/sent: 0/71
Event packet drop due to buffer shortage: 0
Event packet drop due to loss connection: 4
then there some question:
- what about the relationship between the foreign viq and local viq within the same xiq account?
- how to transmit this ap from one account to another, may I keep the old vhm and transmit it a new xiq account?
- doesn't the white light indicated ap have been connected to the xiq?
Best answer by Sam Pirok
You shouldn’t be able to have one serial number in two inventories at the same time. Attempting to add an AP to a second inventory while it is currently registered to a different inventory (regardless of whether the AP is currently connected to that instance or not) will produce the error stating the device is already in use by another VIQ instance. Even when moving over an export from one instance to the other, if you don’t remove the AP serial numbers from the first inventory before uploading the export, you should get errors about the APs not being added because they are already in use. If you have the AP showing in both inventories right now, I’d recommend opening a support case as that is not intended behavior.
For the serial number you provided, I’m not seeing any redirector records at all for that device currently. Typically when an AP is not connected to a VIQ instance it will:
- Send out a layer 2 broadcast looking for any on premises VIQ instances within the same subnet as the AP. If it finds one, it will connect to that instance and end the process there.
- If it doesn’t find an on premises instance in the same subnet, it will reach out to the redirector to see where it is registered to currently. The redirector will tell the AP which VIQ instance to connect to, and the AP will reach out to that address to start the CAPWAP process. There can only ever be one redirector record for each device. When you remove the AP from your inventory, that updates the redirector as well so it knows that the AP is no longer bound to the original instance.
I’m also assuming both of your instances are hosted online. If you’re moving an AP from a cloud based XIQ instance to an on-premises instance, it’s possible you could have the serial number in both places but the AP should be going to the on premises instance first after it sends that layer 2 broadcast. If it finds an on premises instance to connect to, it won’t contact the redirector at all.