Email Subscription Notifications Suspended Temporarily
We are in the process of making navigation in the Servers and Operating Systems forums simpler and more direct. While doing this, we have to temporarily suspend email notifications for subscriptions. If you are subscribed to one or more discussion boards or blogs in the community, please check them daily to see new content. Notifications will be turned back on in a few days. We apologize for any inconvenience this may cause. Thanks, Warren_Admin
Switches, Hubs, and Modems
Showing results for 
Search instead for 
Did you mean: 

Configuring an HP3500 to connect to an IBM BladeCenter H

Occasional Contributor

Configuring an HP3500 to connect to an IBM BladeCenter H

Configuring an HP3500 to connect to an IBM BladeCenter H:

BladeCenter H Type MT8852 Product ID: 88524XU S/N: 99B2005 With two each internal Cisco CIGESM modules, 20 port network switches; (16 ports (one for each blade) + 4 external ports) per switch module.

I'm trying to locate someone who has actually deployed an IBM BladeCenter with the internal Cisco switch modules in an HP Procurve environment.

The main issues seem to be Cisco's "native vlan" and the use of Vlan id #1 for management in the BladeCenter and our primary network which resides on Vlan id #1, along with 802.1q vlan tagging versus Cisco's trunking versus HP trunks versus Cisco Etherchannels.
Case Van Horsen
Frequent Advisor

Re: Configuring an HP3500 to connect to an IBM BladeCenter H

I haven't used the IBM Blade Center but I've done quite a bit with Cisco and Procurve. I'll start with a question or two.

1) Will the Cisco switch card be connected to a single Procurve switch?

2) Will you be running any Spanning Tree protocol on the link between the switches? (This is related to question #1.)

3) Does vlan 1 on the Cisco switch correspond to a different vlan on the HP switch? If so, can you change management on the Cisco switch card to use that vlan? (I know this is possible on all recent standalone Cisco switches.)

4) What VLANs are defined on both switches?

To define an aggregated link between the two switches, I would probably enable the LACP protocol on both ends:

trunk 1-4 trk1 lacp

int range gi0/1 - 4
channel-group 1 mode passive

In order to get VLAN tagged to work in any sane manner, you'll need to make the VLAN usage consistent on both switches. I normally do not use VLAN 1 for any purpose, on either brand of switch.