Centralized forwarding is enabled, and the terminals' gateway is on the AC.
On-site feedback indicates that the Bonjour gateway function on the AC is being used, but the smart terminal (the accessed terminal) and the client (accessing terminal) cannot discover each other when separated by three layers..
Based on the feedback, the network's connectivity was checked and on-site testing was conducted on the smart terminal and client with no issues pinging across three layers, confirming that the network's connectivity is not an issue.
A check was performed on the site's configuration, but no obvious issues were identified.
The Bonjour debug was enabled on the device, revealing persistent error messages in the debug logs.
*Mar 16 14:35:29:064 2020 H3C BONJOUR/7/EVENT: Question _hap._tcp.local didn't match policy.
Upon checking the output of display bonjour active-service-type, it was discovered that the "hap" service type was not present. This raised suspicions that the smart terminal was using the "hap" service type, but our configuration did not support it, resulting in it being unable to function.
Check the hap configuration in the bonjour active service type, so consider adding this service type in a custom way.
Add a custom service type.
bonjour service type hap tcp description Philips
Activate this service type
bonjour activate service type user-defined hap
After configuring these two commands, the fault is resolved
Check the display bonjour service to see the type of hap in the service type.
Global status: Enabled
Bonjour service-mode: custom
Total number of discarded query packets:263095
Total number of discarded response packets:72635
Total number of bonjour services: 14
Instance name Service type Protocol VLAN TTL IP
Canon a http TCP 10 255 10.10.10.1
Canon a ipp TCP 10 255 10.10.10.1
Canon a printer TCP 10 255 10.10.10.1
09CE76@b raop TCP 4 120 192.168.100.1
bbb hap TCP 5 120 192.168.1.1