NAM-1 in C6509 with SUP720: Access to switch failed
This is my problem. When I try "Setup > Switch Parameters > Switch Information" on the NAM web interface, I get the following...
Performing SNMP test from NAM (127.0.0.91) to switch (127.0.0.21)
Access to the switch failed. This may be due to the switch's SNMP access control list is enabled.
Check if your switch's SNMP access control list is enabled and make sure
that the NAM's IP address is included in the access control list.
I've checked communities and changed the ACL to allow snmp from 127.0.0.91 (as stated in the Config Note) and even removed the ACL (temporarily) before I noticed that my switch actually uses 127.0.0.51 (as it is equipped with a SUP720 in slot 5 and a redundant one in slot 6) and not 127.0.0.21.
When I look at the tech info of the NAM, it does bind the rmond to 127.0.0.51, but in the "switch address" section it says 127.0.0.21.
Re: NAM-1 in C6509 with SUP720: Access to switch failed
Yes I do have a management vlan configured and the vlan interface does have an IP address and is active.
I opened a case with Cisco last Tuesday, but still no reply :(
I applied the patch (2) for NAM 3.4(1a) software and used the new "supervisor address" command to set the supervisors address. This works, but now all SNMP traffic passes over the management VLAN in stead of over the 127.0.0.0 (EOBC) network. Not very secure...
Question We run asr9001 with XR 6.1.3, and we have a very long delay to
login w/ SSH 1 or 2 to the device compare to IOS device. After
investigation, the there is 1s delay between the client KEXDH_INIT and
the server (XR) KEXDH_REPLY. After debug ssh serv...
Introduction The purpose of this document is to demonstrate the Open
Shortest Path First (OSPF) behavior when the V-bit (Virtual-link bit) is
present in a non-backbone area. The V-bit is signaled in Type-1 LSA only
if the router is the endpoint of one or ...
Hi, I am seeing quite a few issues with patch install and wanted to
share my experience and workaround to this. Login to admin via CLI, then
access root with the “shell” command Issue “df –h” and you’ll probably
see the following directory full or nearly ...