I wanted to control from which location and ssid where posture for user happens.
Location 01 --> posture should not happen. there is ISE reachability regardless of the same. As this is an MPLS location using Windows NPS.
Location 02 --> posture should happen this is a coporate location.
What is happening --> when a user connects to SSID in location 1. he gets authenticated using NPS but the posture agent kicks in as ISE is reachable and start's doing posture. this scenario i dont want where he has to go do posture as he is in a different location.
is there any possible way to restrict this that posture shouldnt happen regardless its reachable from other location?
I am confused about RADIUS groups, for Dot1X I would like to add my RADIUS servers by IP to ISE group, like this:aaa group server radius ISE
server <ip_address_1> auth-port 1812 acct-port 1813
server <ip_address_2> auth-port 1812 acct-port 1...
Hii have ASA5555-X with firepower modulei use ASDM for manage ASA and use FMC(18.104.22.168) for manage FIREPOWER(use inline mode for asa traffic to firepower)i have a web server in DMZi config Decrypt-Known key method for outbound traffic that access to my web...
I'm in a temporary configuration with two Nexus VPC switch pairs serving the inside network of my ASA 5520. Call the switch NX01 02 03 04. NX01 02 are a VPC pair and 03 04 are a pair. There are four real addresses and one HSRP VIP - say VIP 10.100.10...
Hello All,Here is our deployment, DC1 has a PAN and 2 PSN nodes. DC2 also has a PAN and 2 PSN nodes. Both the PAN nodes also hold the MNT roles. We are on ISE 2.7 with patch 5. We are having issues with logging, when the primary PAN fails...