- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- Re: Configuring an HP3500 to connect to an IBM Bla...
Switches, Hubs, and Modems
1753394
Members
7280
Online
108792
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-31-2008 05:59 AM
03-31-2008 05:59 AM
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.
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.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-01-2008 07:23 AM
04-01-2008 07:23 AM
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:
HP:
trunk 1-4 trk1 lacp
Cisco:
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.
casevh
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:
HP:
trunk 1-4 trk1 lacp
Cisco:
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.
casevh
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP