In a campus rollout, Cisco ISE holds live user sessions and security group tags while the Secure Firewall Management Center needs that context for its access rules. pxGrid brokers the exchange through a trusted controller. Which role does the Management Center take in this pxGrid exchange?
Select an answer to reveal the explanation.
Short Explanation
You can think of the Management Center as a listener: it joins pxGrid as a client and subscribes to ISE’s Session Directory and SXP topics. That way, it gets live session details and security group tag updates without having to request each piece individually.
Full Explanation
pxGrid is a publish-subscribe fabric with a controller brokering trusted applications. In this design, Cisco ISE provides the controller and publishes topics; the Secure Firewall Management Center joins as a client and subscribes to the Session Directory and SXP topics. Session Directory provides user session data, while SXP provides security group tag mappings for identity context in access control rules. Subscribing only to Session Directory leaves the tag requirement unmet. eStreamer sends connection event data outward, such as to a SIEM, rather than bringing the required user and tag context into the Management Center. Nightly imports of static objects do not provide live updates. Certificate trust, pxGrid version, and identity source settings in ISE must be configured correctly for the topics to flow.