Bonjour Gateway and HiveOS 6.5r3 Honolulu.2530

  • 1
  • Question
  • Updated 2 years ago
Hi

After upgrading our HiveManager to Enterprise 6.6r3 and upgrading our AP's (AP120) to HiveOS 6.5r3 Honolulu.2530, our Bonjour Gateway isn't working anymore.

I tried to check the config but can't find anything wrong.

- Our AppleTV's are in VLAN 120 (wired)
- Our computers and iPads are in VLAN 130 and 131 (wireless via Aerohive)

- I defined a Bonjour Gateway OL_Bonjour with vlans 120, 130, 131. Traffic is allowed from vlan group OL_Bonjour_Vlan tot vlan group OL_Bonjour_Vlan.
- Vlan group OL_Bonjour_Vlan contains vlans 120, 130, 131

- I defined 6 DHCP Server and Relays:
vlan 120: mgt. 0.1 - 172.16.5.253
vlan 120: mgt. 0.1 - 172.16.5.252 (backup)

vlan 130: mgt. 0.2 - 172.16.7.253
vlan 130: mgt. 0.2 - 172.16.7.252 (backup)

vlan 131: mgt. 0.2 - 172.16.13.253
vlan 131: mgt. 0.2 - 172.16.13.252 (backup)

- On the primary Access Point, I set Bonjour Gateway priority to 100 with Realm Name OL_Bonjour. In the service section, I added the three DHCP Server and Relay objects (not the backup).

- On the second Access Point I added Bonjour Gateway priority 99, also with Realm Name OL_Bonjour. There I added the backup DHCP Server and Relay objects.

- I can ping all the interfaces created in DHCP Server and Relay.
- When I SSH to those interfaces, I see I'm connected to an Aerohive AP.


This is the output of Bonjour-gateway status:
Aerohive Networks Inc.
Copyright (C) 2006-2015
OL_HB_OLC_04#show bonjour-gateway status
Note: bonjour client only learning/registering aerohive special services
Running as bonjour gateway
Bonjour Gateway Status:Enabled
Realm Name: OL_Bonjour
Device priority: 100
My BDD: 172.16.1.193
Local mgt0: IP(172.16.1.193/22), VLAN(1) MAC(0019:770f:a080)
Total 3 Local Attached VLANs: 120 130 131 
Total Services: 431; Total Self-Services: 0; Published Times: 0
Total 0 Remote BDDs:
 
Bonjour VLAN range:   120       130-131 
When I connect with vlan 131, I can't see the Apple TV in vlan 120.

Some screenshots:
http://www.piustien.net/BonjourGateway.pdf

There you can see all the Bonjour traffic.

Hopefully someone can see what I do wrong.
Photo of Geert Huylebroeck

Geert Huylebroeck

  • 6 Posts
  • 0 Reply Likes

Posted 2 years ago

  • 1
Photo of Aaron Storey

Aaron Storey

  • 32 Posts
  • 8 Reply Likes
Have you tried disabling Bonjour Gateway on the individual AP via CLI and then re-enableing it? no bonjour-gateway enable followed by bonjour-gateway enable. I have found that sometimes this is necessary especially after updates. 
Photo of Brian Powers

Brian Powers, Champ

  • 396 Posts
  • 92 Reply Likes
The above output says that the AP sees 431 mDNS items.  Doing a "show bon service local" will show you those items.  The question seems to be is why are those entries not being propagated from one VLAN to another...  

What is the purpose of adding the DHCP servers and relay agents?  The AP itself should create a sub-interface on the needed VLANs to listen for the mDNS traffic on those VLANs.  I've never used manually created sub interfaces for the bonjour service to function properly. 

Do a "show bon vlan".  This should output the IP the device has on your respective VLANs.  Do they look correct?  I'd assume they do, otherwise you wouldn't see the mDNS on the VLANs to begin with.  

Your OL_Bonjour_VLAN object needs also contain all of the necessary VLANs.  A "show run | i OL_Bonjour_VLAN" on the BDD (172.16.1.193) will show you the pertinent info related to that object.  Do you see something like:

vlan-group OL_Bonjour_VLAN 120
vlan-group OL_Bonjour_VLAN 130
vlan-group OL_Bonjour_VLAN 131

-- Scratch that as Page 2 of your attached shows that that object does look to be configured correctly.

I wonder if VLAN 1 (your mgmt VLAN) needs to be included in any way.  Although it shouldn't, I would be curious as to what would happen if that VLAN was added to the OL_Bonjour_VLAN object...
Photo of J. Goodnough

J. Goodnough, Champ

  • 266 Posts
  • 32 Reply Likes
you'd probably pollute your management VLAN with bonjour advertisements, but then again I'm facing an intermittent failure to propagate as well...
Photo of Geert Huylebroeck

Geert Huylebroeck

  • 6 Posts
  • 0 Reply Likes
Hi

Thanks for helping. I did some tests:

OL_HB_OLC_01#show bon service local
Show Local Bonjour Gateway Service:
No.  VLAN Service-IP       Port  Type                             Name
====================================================================================
Total 0 services.
Show Self-Registered Service:
No.  VLAN Service-IP       Port  Type                             Name
====================================================================================
Total 0 services.


OL_HB_OLC_04#show bon service local
Show Local Bonjour Gateway Service:
No.  VLAN Service-IP       Port  Type                             Name
====================================================================================
Total 0 services.

Show Self-Registered Service:
No.  VLAN Service-IP       Port  Type                             Name
====================================================================================
Total 0 services.


OL_HB_OLC_01#show bon vlan
VLAN IP              Netmask  
OL_HB_OLC_04#show bon vlan
VLAN IP              Netmask 
When I ping from our DHCP server (172.16.1.253)

DHCP_Relay_Bonjour_Vlan120 mgt0.1
ping 172.16.5.253
No response
DHCP_Relay_Bonjour_Vlan120_BU mgt0.1
ping 172.16.5.252
Response
DHCP_Relay_Bonjour_Vlan130 mgt0.2
ping 172.16.7.253
Response
DHCP_Relay_Bonjour_Vlan130_BU mgt0.2
ping 172.16.7.252
Response
DHCP_Relay_Bonjour_Vlan131 mgt0.3
ping 172.16.13.253
Response
DHCP_Relay_Bonjour_Vlan131_BU mgt0.3
ping 172.16.13.252
Response
Photo of Brian Powers

Brian Powers, Champ

  • 396 Posts
  • 92 Reply Likes
Until the show bon vlan populated some information, I believe the AP does not have a fully working interface on said VLANs.  You should see the IP and the associated VLAN with that command.  As I've said before, I've not needed to create manually the sub interfaces as you did, so I'm not sure of the expected result as of that.  
Photo of Geert Huylebroeck

Geert Huylebroeck

  • 6 Posts
  • 0 Reply Likes
We reverted back to HiveOS 6.1r6a.1794  and now it works...