Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

configuring IGESM for blade center

Hi,

Hi,

Is anybody can explain default config on the internal port connected to blade server.

interface GigabitEthernet0/1

description blade1

switchport access vlan 2

switchport trunk native vlan 2

switchport trunk allowed vlan 2-4094

switchport mode trunk

spanning-tree portfast trunk

spanning-tree bpdufilter enable.

I am bit confused that it is configured as trunk and access port as well.

please let me know how 2 NICS in the each blade server will behave, since each NIC connectd to differnt switch module.

thanks in advance..

Rgds,

Hi,

how we can configure internal ports connected to blade servers on IGESM

trunk or access ports?

can we change management vlan from 1 to 2

without any problem ? when we change management vlan what will happend to 2 management interface ports 15 and 16?.

Regards,

Rajesh

3 REPLIES
Silver

Re: configuring IGESM for blade center

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.

http://www.cisco.com/application/pdf/en/us/guest/products/ps6294/c1067/ccmigration_09186a00806491b4.pdf

New Member

Re: configuring IGESM for blade center

Hi,

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.

Regards:

Michal

New Member

Re: configuring IGESM for blade center

Hello Rajesh,

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.

185
Views
0
Helpful
3
Replies
CreatePlease login to create content