We're currently using CA Spectrum for a fault management system. In 2017 we discovered that newer Cisco ISR's (ex. 4331, 4321, 4431) and ASR's (ex. 1006, 1002) are no longer supporting the CISCO-ENVMON-MIB on these devices running IOS-XE. How we discovered the change was we were missing SNMP traps or outages for Power Supplies, Fans, and Temperature for some of our managed customers. We contacted Cisco and they verified what we discovered and they informed us they're using the CISCO-ENTITY-MIB for these devices. We configured a few devices to send the Entity traps which is basically a one trap for everything trap that contains very limited information. Because we didn't like the Entity trap format and data we're currently testing syslog traps and only monitoring severity 0-3 syslog events. By configuring a few Syslog files in Spectrum we can filter unwanted syslog messages. In these files we simply add the "Facility" name we wish to ignore. We're looking for an online resource that list all the "Facility" names for IOS-XE along with their definition and type. Manually going through each IOS-XE (version 15.x and 16.x) Systems Message Guide is very time consuming and it really doesn't define the "Facility" name. For example: What does facility "IOSXE_PEM" mean and what type (Protocol, System, Environment, Software, Security, Hardware_Configuration, or Connection_Configuration) message is it? The attached PDF file explains the filter files we're creating. There are hundreds of "Facility" name, but we're hoping there is an easier way to get information about the "Facility" names.
XR-vm - CLI's
look for any process crash, review time stamp[if it is too old, then no immediate action needed]
verify if standby state is Ready and NSR-Ready
show proc cpu | exclude " 0%"
It's been a long standing ask for XR to support conditional route advertisements in BGP.
The expected option of using the
option in RPL currently can only be used at the default-inf...
On IOS-XR, Quality of Service has an extension to WRED (Weighted Random Early Detection) called Explicit Congestion Notification (ECN). ECN will mark packets instead of dropping them when the average queue length exceeds a specific threshold value. When c...
Technical Guide to Pre-Defined NAT.
In traditional NAT, due to the government regulations logging the CGN translations is mandatory and this is a huge cost incurrence. In Pre-defined NAT, the translations are known upfront, hence there is no nee...