Service Policy Configurations
Controller service policy is implemented by configuring service filters. A service filter specifies the policies that allow the controller to accept and process service announcements and queries of specified service types and from specified SDG Agent subnets. A subdomain can be associated with one or more service-filters. A service filter has the following components:
-
Network Mode. Either Traditional or Overlay, depending on the network mode.
-
Name. A unique name of the service filter.
-
Description (Optional).
-
Service Type. Service announcements and queries of the specified service type will be permitted by the service filter.
-
A set of Source SDG Agents. For each Source SDG Agent, the following are specified:
-
SDG Agent or IP address of the source agent. Service announcements will be accepted only from the specified SDG Agent
-
Service Layer. Whether the source agent is a local or a peer agent.
-
Symmetric or asymmetric IRB.
-
IPv4 and IPv6 Subnet and Mask of the SDG Agent, where applicable. Announcements will be accepted only when they originate from the specified subnet of the SDG Agent. These subnets pertain to the client VLANs, to which the Bonjour endpoints are connected.
-
Peer ID.
-
VNI ID.
If a service announcement is permitted by a service filter, the services being announced are accepted, and become eligible to be included in service response for any query that may match the same service filter.
Service announcements that do not match any service-filter are dropped.
-
-
A set of Query SDG Agents, each specifying:
-
SDG Agent or IP address of the source agent. Service announcements will be accepted only from the specified SDG Agent.
-
Service Layer. Whether the source agent is a local or a peer agent.
-
Symmetric or asymmetric IRB.
-
IPv4 and IPv6 Subnet and Mask of the SDG Agent, where applicable. Announcements will be accepted only when they originate from the specified subnet of the SDG Agent. These subnets pertain to the client VLANs, to which the Bonjour endpoints are connected.
-
Peer ID.
-
VNI ID.
If a query is accepted by the service filter, then a response is sent to the service querier with the details of those services instances that were previously accepted through the same service filter (in other words, originating from the source SDG Agents and subnets, as specified in the service filter).
Service queries that do not match any service filter are dropped.
-
In the domain hierarchy, multiple domains may be configured with service filters. When the controller receives a service query, the query may match with more than one service filter, in which case each matching service filter is processed, and the aggregated response is sent back.
Note |
To see what information is applicable in a particular scenario, see Configure Service Filters Using the GUI. |