I have a stack of 2 2960S switches that are dedicated for the storage net, only between SAN and blade system.
I have configured fastethernet0 (management interface) for static ip 192.168.163.25 which is then connected to my core data switch, so i can manage the storage switch.
So here is the issue: if there is nothing connected to that stack at all, except the management int the switch pings and i can telnet to it.
However, if i boot the stack with all storage network uplinks and downlinks connected the management int does not ping and i have no access to the switch. As soon as i unplug the last cable, the management interface starts to ping and i can telnet in. Then i can plug all the cables and everything works fine, until i reboot the switch again.
I did today and it worked, i can also connect to this mgmt inf if i plug my laptop directly to the same switch where i plug the mgmt connection to 2960s. However, if im on a different switch i can not ping it, access it, but i can any other device on the same net, switch.
The Management port is not a routed port. It's not even a switch port. It's purely for management/OoBM. You can't connect F0 into another switch's switchport and hope to be able to access to it because it can't.
I see this question was never answered, and I've never seen a satisfactory answer although it's a very useful feature if you can get it to work.
Well today I finally got my switch management ports working with AAA/TACACS+ and vty ACLs
The actual problem which needs to be solved is getting the management port to use a gateway - a static IP is only useful if your management station is on the same segment, so that's quite limited.
The problem with DHCP is that the basic config can have strange behaviour - for instance in my environment I could get an IP and a gateway in a standard lease, but I couldn't initially get it to pick up a fixed IP in a reservation.
My DHCP server was recording a 48-digit hex string in the mac address field - which turned out to be a hex dump of the default Client-ID, one of the various optional parameters in the "ip address dhcp ..." interface command:
Switch#sh dhcp lease Temp IP addr: 192.168.25.99 for peer on Interface: FastEthernet0 Temp sub net mask: 255.255.255.0 DHCP Lease server: 192.168.4.6, state: 5 Bound DHCP transaction id: 1037 Lease: 604800 secs, Renewal: 302400 secs, Rebind: 529200 secs Temp default-gateway addr: 192.168.25.1 Next timer fires after: 3d11h Retry count: 0 Client-ID: cisco-5067.aeff.b739-Fa0 Client-ID hex dump: 636973636F2D353036372E616566662E 623733392D466130 Hostname: Switch
Once I configured my management port like this:
interface FastEthernet0 ip address dhcp client-id FastEthernet0 hostname Switch no routing dynamic
...I was able to use the interface mac address to create a DHCP reservation that registered properly.
In order to get my AAA/TACACS+ working, I provided the following:
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 ...