Author: RunThor

After un-stacking a Cisco switch in my IBM blade center I can no longer ping the management IP I had configured on my management VLAN. The only item I see that changed is that the Bladecenter AMM added a internal Ethernet management port. There has been some discussion on reddit. Prior to un-stacking this VLAN interface was working.

I still haven’t found a resolution that would explain why this isn’t working or how to allow access over the current management VLAN. If possible I would like to keep L3 routing off on the switch.

As far as testing I have configured an access port and truck port native to the management VLAN. I connected a laptop with a static IP within the management VLAN range to these ports and was not able to ping or access the swith. When the switch is connected it does pass traffic, as expected, on all ports/VLANs. However I was still unable to ping or SSH the switch directly.

For testing purposes:

I have configured an access port and truck port native to the management VLAN, I’ve configured a laptop with a IP in the management VLAN to connect to these test ports.

I’ve devices on other VLAN are able to connect and pass traffic though this switch.

The switch its self cannot ping other devices when using no source, the FE interface as source, or the management VLAN IP as the source.

I’ve removed the management VLAN IP, and configured the FastEthernet port with the management VLAN IP.

I suspect this doesn’t work as I cannot set a VLAN onto the FastEthernet port

I’ve removed the default gateway with, and without, the VLAN ID configured and with the FasEthernet port configured.