We have a mixture of Catalyst and Nexus switches and want to implement a safeguard in Cisco ACS in the form of a command authorisation set which prevents users from entering the command "switchport trunk allowed vlan x" without the "add" or "remove" keywords.
I am sure many readers of this understand what happens on a live trunk link when the allowed list is accidentally changed to just the vlan which you originally intended to just add.
The only problem I have is that for some strange reason, the Nexus will NOT allow you to configure a new trunk link with the "switchport trunk allowed vlan add x" syntax. For some reason you have to first configure it with something like "switchport trunk allowed vlan 10-100" and once an initial allowed list is configured, you can then use add / remove to modify the list.
This is obviously different to the way in which Catalysts work because you can do it either way. The strange thing is, the Nexus lets you enter the command with the "add" keyword, and doesnt even complain, but the configuration is NOT updated with the vlan.
We are running NX-OS 5.2(3a) and was wondering if this is a bug / issue which has been resolved in the 6.x release.
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 ...