Second HiveOS VA's not showing up in HiveManager

  • 1
  • Question
  • Updated 5 years ago
  • Answered
I’ve started a deployment with two Bonjour Gateway HiveOS VA’s model (as described in page 7 of the Free Bonjour Gateway Configuration Guide)

The two HiveOS VA’s are connected to the hivemanager online (verified with the cli command “show capwap client”)

But only one is showing up in the devices list and in the bonjour gateway services realm list the other HiveOS VA is not appearing on the lists but is connected to the hive manger online.

Bg 01 (appearing cli output

BG01P#show capwap client
CAPWAP client: Enabled
CAPWAP transport mode: UDP
RUN state: Connected securely to the CAPWAP server
CAPWAP client IP: XX.XX.XX.XX
CAPWAP server IP: 198.46.53.222
HiveManager Primary Name:Bonjour-gateway.aerohive.com
HiveManager Backup Name:
CAPWAP Default Server Name:
Virtual HiveManager Name: hive_manager_name1
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
Keepalives lost/sent: 0/16
Event packet drop due to buffer shortage: 0
Event packet drop due to loss connection: 6

BG02 (the one that's not listed)

DBG02P#show capwap client
CAPWAP client: Enabled
CAPWAP transport mode: UDP
RUN state: Connected securely to the CAPWAP server
CAPWAP client IP: XX.XX.XX.XX
CAPWAP server IP: 198.46.53.222
HiveManager Primary Name:Bonjour-gateway.aerohive.com
HiveManager Backup Name:
CAPWAP Default Server Name:
Virtual HiveManager Name: hive_manager_name1
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
Keepalives lost/sent: 0/16
Event packet drop due to buffer shortage: 0
Event packet drop due to loss connection: 6

All the firewall rules in the firewall are configured and allowing connection to the aerohive cloud.

Regards,

Mixtape.
Photo of mixtape

mixtape

  • 2 Posts
  • 1 Reply Like
  • frustrated

Posted 5 years ago

  • 1
Photo of Emilio Maldonado

Emilio Maldonado

  • 37 Posts
  • 11 Reply Likes
When the two instances are up and running typically they are internally autoprovisioned to point to each other. Can you check if they are?
show roaming neighbor

If not, can you manually point both to each other using:
roaming neighbor include ip