Changing the management VLAN does not require modifying the configured IP address even if the IP address is assigned by the chassis management module. The IP address of the current management VLAN is automatically copied by the switch when the new VLAN interface is created and designated as the management VLAN. To change the management VLAN, create an additional VLAN interface, and then enter the management command on that VLAN interface. The switch automatically copies the IP address.
I am currently working with cisco blade switches for HP blade servers p-class. At the begginging I has same problem with mapping ports, NICs to the switches. Ports from Gi0/1 - 16 are virtual and connecting to servers. Take a look at the link,download the tool and then You can see which NIC connectes to which switch on which port (http://h18023.www1.hp.com/support/files/serveroptions/us/download/23959.html).
The configuration you showed is incorrect, becouse only one port on blade switch connects to one NIC of a server. You dont need to create a trunk but access port. Look at the HP Ethernet Connectivity Mapper.
Managment Vlan for security purpose should be changed from 1 to another one. Port 15 and 16 are use for server connectivity (Gi0/1 - 16), not managment !
If You have further questions about this, dont hesitate to ask.
The defaults are set up this way because the management path needs to be isolated. The default configuration is to manage the management module through the management module's physical ports.
It is possible to enable management through the cisco CIGESMs, but you would need to make sure you understand the redpaper before doing that. The defaults are set up to be plug and play.
The issue is that the management module will proxy arp in order to make sure all the possible modules that can be used in this box can be used. The management module does an L2 rewrite as well in order to allow it to be managed from across the switch uplinks.
It is typically tougher to configure that sort of management setup, so we use vlan 2 to keep it separate.
Each nic on the blade server will connect to the corresponding switch - first nic goes to top CIGESM and the second nic goes to the bottom one.
Trunk or access configuration is done as usual "switchport mode [trunk | access]"
The management module does not care what vlan you are in as far as managing the switch, but using the management keyword on the switches changes the interface that the management module sees as the management vlan. The config will be copied from the former management vlan. The allowed vlan list will be opened up on the external uplinks as well to make sure that vlan is accessable to the network.
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 ...