This is a new setup of Cisco access switches (2960S, 2960X IOS with 15.2(2)E9, but mostly C1000 with IOS 15.2(7)E*), with a Cisco ISE 3.0 as authentication server for 802.1X, config style is to be IBNS 2.0.
Switches will want to do radius server dead detection and this all seems to be on a good path.
Task at hand:
We'd like to be alerted when a switch detects "all AAA servers down" and starts to handle the "critical" or Inaccessible Authentication Bypass branch in the IBNS 2.0 policy.
SNMP-poll state of given radius servers with SNMP, raise alert if all are considered "dead" by the switch.
... OR ...
SNMP-poll state of given radius server group, raise alert if the entire group is shown as "dead".
The bad news:
SNMP trap ingestion and alerting on syslog parsing are (currently) no options with the given monitoring/alerting construct - so we'll need to rely on polling.
- CISCO-RADIUS-MIB (220.127.116.11.18.104.22.168.288)
- CISCO-RADIUS-EXT-MIB (22.214.171.124.126.96.36.199.736)
- CISCO-AAA-SERVER-MIB (188.8.131.52.184.108.40.206.56) ... 220.127.116.11.18.104.22.168.22.214.171.124.1.25 seemed such good idea at first.
- CISCO-AUTH-FRAMEWORK-MIB (126.96.36.199.188.8.131.52.656)
... but 1. - 3. don't seem to be populated by the SNMP agent on the switch, and 4. doesn't seem to hold any info about the auth servers and their state.
[EDIT after research]
Indeed, Cisco's own feature navigator confirms that C1000 and 2960S/X, from the MIBs listed above, support CISCO-AUTH-FRAMEWORK-MIB only.
[/EDIT after research]
Current AAA and SNMP config of the device is (sanitized)
aaa group server radius CUST-ISE-RADIUS server name CUST-ISE1-HOSTNAME01 server name CUST-ISE2-HOSTNAME01 ip radius source-interface <SrcIf> radius server CUST-ISE1-HOSTNAME01 address ipv4 <ip> auth-port 1812 acct-port 1813 timeout 1 automate-tester username ... <plus some more> key 7 <key> radius server CUST-ISE1-HOSTNAME01 address ipv4 <ip> auth-port 1812 acct-port 1813 timeout 1 automate-tester username ... <plus some more> key 7 <key> [...] snmp-server community <ourcommunity> RO <OurReadOnlyACL> snmp-server trap-source Loopback0 snmp-server source-interface informs Loopback0 snmp-server location <somewhere> snmp-server contact <us, of course> snmp-server enable traps cpu threshold snmp-server enable traps envmon fan shutdown supply temperature status snmp-server host 184.108.40.206 <ourTrapCommunity>
- Is there another branch of the (Cisco's) MIB tree you might know about, where we'd be able to determine if a switch believes the given (set of) radius server(s) dead or up?
- is there a way to enable support for AAA-MIB, or its non-experimental equivalent? (.220.127.116.11.9.10 .* is "Cisco Experimental", and CISCO-AAA-SERVER-MIB is part thereof).
Thanks for your hints and pointers