04-28-2021 09:12 AM
to learn it, I did some test:
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: 34.67.130.71
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:
Solved! Go to Solution.
04-28-2021 03:09 PM
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:
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.
04-28-2021 02:16 PM
Hi, sam
I mean, when export viq from the first xiq instance, and import it to the second xiq instance.
then the first xiq’s viq info will go and mix with the second xiq instance?
04-28-2021 01:02 PM
Hi there, thanks for sharing that output. Based on the run state saying “Connected securely to the CAPWAP server” and the white LED light you’re seeing on the AP, that indicates the AP does indeed think it’s connected somewhere. Likely there is some old registration/configuration holding the AP to your original Connect account. I’d recommend going through the steps outlined in this guide to manually connect your AP to the new Pilot instance: https://extremeportal.force.com/ExtrArticleDetail?an=000057794&q=capwap%20troubleshooting
I’m not sure what you’re asking when you say “what about the relationship between the foreign viq and local viq within the same xiq account?”, could you clarify for me?