You manage the bladecenter switch thru the management module on the bladeserver itself . Management does not occur thru the 4 uplinks 17,18,19,20 so it will always be vlan 1 for the management in the bladecenter switch. Just put a port into vlan 20 and connect it to the management port on the bladecenter. All other "server" traffic does indeed flow up thru those 4 ports on the igesm switches.
As others are implying, the internal ports, gi0/15 and 0/16 are in effect proxied ports for the IBM blade center MM.
The VLAN number you use, in practice, for management is irrelevant, just as long as you make the SVI the same vlan number you assign those two ports two....and make sure that VLAN number is different than the data plane...
This is covered in gross detail in the IBM IGESM implemenation guide
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 ...