‎03-04-2019 09:35 PM
‎03-05-2019 01:52 PM
Yeah. So it should be the ethernet address of the AP acting as the BDD. I don't believe it augments that MAC any per VLAN. But if you SSH into one AP (unless you know which AP is acting as your BDD then SSH into it).
If not the BDD run this command:
show bonjour status
Look for "My BDD: <IP>"
Then SSH into that BDD IP. This is the IP of the AP that will have the interfaces on the VLANs. Once in that AP, do a:
show interface
This will show you the interface(s) that exist on the AP. If you see eth0, eth0.1, eth0.2, etc., then it does create sub interfaces for each VLAN and you'd need to reserve a unique MAC per VLAN.
Note you probably want to set priority for this AP to always be your BDD if you reserve IP for it in your DHCP scope. You can edit the AP individually and adjust it's BDD priority value under Optional Settings and Bonjour Gateway Configuration (HM Classic). Higher number takes precedence I believe.
‎03-05-2019 01:44 PM
Thank you for the clarification. Is it possible to find what the Mac address would be on the Vlans? I would prefer to make reservations.
‎03-05-2019 12:36 PM
Darrell,
If you think about what it is doing, it makes sense. Bonjour is Apples version of mDNS. DNS is IP. IP shows up in layer 3 of the OSI model. So the AP acting as the bonjour listener (BDD in Aerohive's terms) would have to have Layer 3 (IP) access to each VLAN to be able to redistribute the traffic from one VLAN to another.
‎03-04-2019 09:43 PM
This would be expected, the APs need to have an IP address on any VLAN that they need to host the Bonjour service for. Otherwise they won't be able to advertise the service on that VLAN.
‎03-04-2019 09:40 PM
This is referring to the Bonjour gateway. I am sorry I did not include that.