We run WebNS 5.00b37 on 8 CSS' managed in-band with management interfaces disabled and boot-config IP left to the default value of 126.96.36.199.
Traps received on our SNMP trap collector show the CSS boot-config IP as the trap source. This makes the SNMP trap logs somewhat useless, since all traps apear to originate from the same 188.8.131.52 device. I thought of changing the boot-config IP to a valid (routable) IP, which would basically act as a loopback IP. Would this work? I also found references to WebNS 5.03, which now has a "snmp trap source" command to apparently fix my problem. This version also now has TACACS capabilities. Unfortunately, I cannot find this version on the Cisco software centre. Any idea where it is kept?
This document will provide screenshots to outline the steps to setup
TACACS+ configuration to ACI and also the configuration required on
Cisco ACS server. Please find the official Cisco guide for configuring
TACACS+ Authentication to ACI:
Is it supported or NOT supported? It's a frequently asked question.
Before APIC, release 2.3(1f), transit routing was not supported within a
single L3Out profile. In APIC, release 2.3(1f) and later, you can
configure transit routing with a single L3Out pr...
Cisco Documents are usually accurate, but when it came to the document
on Cisco APIC Signature-Based Transactions it was slightly off the mark.
This document is for those novices to API like me who cant seem to
figure out how to go about performing signat...