10-23-2019 09:48 AM
Hi there,
Just setting up some 2960x switches and trying to get a basic admin connection to these just via the normal switchports while we set things up (management port fa0 goes into first normal gigabit switchport gi1/0/1 to allow SSH from all parts of the L2 domain shared between switches, no routing). I've done this with all the switches without issue so far but one of them is being very odd, the management interface fa0 is configured and works when directly connected using a laptop, or when fa0 is connected to a normal switchport of another switch and I have my laptop connected to any of the other switches. Just that the management interface does not work (in or out) when connected to switchports of the same switch, it seems this one switch drops packets from/to this MAC for reasons I can't fathom. Sadly I can't just bounce it in case it's a random glitch as there are active users.
I can't see an issue with the arp table, mac table and CDP says it's connected as expected, I just can't ping or SSH to it. The swtich also can't ping anything so it seems the interface is left high and dry when connected to its own switch. I've dropped the mac and arp tables and it's made no difference, shut no shut too. The switch is also connected via fibre to another building and any attempts to connect to the management interface from the other building fails in the same way (though SSH to other switches pass through it fine). For some reason this switch does not want to ethernet route the MAC address for its own management interface, but is happy to do so for others?
All L2 is working fine and everyone can connect to everything, except this particular MAC can't get 'packed switched' via this particular switch for some reason. Can I change the MAC of the management interface? Can I set a manual MAC/port association? Is there some lockout/blacklist of management ports that might have triggered?
Does anyone have any ideas as to how this might be happening/how to address it or even how I might begin to troubleshoot the behaviour?
The VLAN 1 and fa0 configs are identical between the switches,
10-23-2019 10:42 AM
Hello
Make sure you don’t have ip routing enabled by mistake and the management vlan has the correct addressing -subnetmask etc and the switch idoesn’t have a management plane policys
sh ip route
sh management-interface
sh run
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide