MDNS-AP + 9800 + Service policy location:site-tag = MIA

[Thomas Obbekaer Thomsen]

So behind the "cryptic" Title is the following scenario

APs in localmode, but since we need to "pick up" some wired mDNS services on sites, one AP at a site is configured as an mDNS-AP (with the proper VLAN and so on).

Great. - So far so good.

BUT then someone made a clear oversight (in my opinion).

Those mDNS services picked up by the mDNS AP (that are part of a site-tag of course) are not showing up with a site-tag in the mDNS cache of the 9800. This of course means that those services will be visible to everyone, everywhere.

Is there something I missed, or is this (unfortunately) the way it works ?

In the picture below (example) - the mDNS enabled AP is part of the 516 site (and of course wireless mDNS services are being picked up, and put in the mDNS cache with a site-tag). But someone forgot this when they where coding it. But it seems so obvious that this should be a thing.

I know of at least a couple of customers who would want this.

Or has this "oversight" been rectified in a later release ?

/Thomas

[Scott Fella]

Thomas,

This is something you just need to ope a TAC case for.  I don't think any of us would be able to answer that question.

[Thomas Obbekaer Thomsen]

Well since I don't know if this is a bug, or a missing feature, I don't want to just open a TAC case.

If its a bug, sure I'll open a case. But if it's just a "feature" that's not there, then it's a feature request (with all the work that goes into those things)

But I can't seem to find out if its a bug or a feature from documentation.

That is why I was asking the community if some of you knew

[patoberli]

In both cases a TAC would be the correct channel

Regarding the software, which version are you running? Then I could have a read in the release notes to see if something might have changed.