- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- Gbe2c communication problems
BladeSystem - General
1753641
Members
5294
Online
108798
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
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
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
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
тАО09-19-2007 09:16 PM
тАО09-19-2007 09:16 PM
Dear,
I have a problem with my 2 Gbe2c in my HP C 7000.
Each switch is unable to ping the other.
Every blade (w2k3 or esx 3.0.1; NIC teaming is configured in active/active) is able to ping just one of the 2 switch.
It is a big problem for Virtual infrastructure.
For the moment, i only use half of my nics, the second gbe2c is not in use because of my problem.
I configure UFD to disable internal ports when my uplink 21 fail.
I flash it both to V2.0 (image and boot) with no better results.
Uplink to 2 core network HP on port 21 (or 21 and 22 in a cross configuration), but it still the same.
I enabled port 17 and 18 for trunk 1. These ports was disabled y default, strange ? and no more results.
What I' ve done bad ? where i fail ?
Thanks for your help.
I have a problem with my 2 Gbe2c in my HP C 7000.
Each switch is unable to ping the other.
Every blade (w2k3 or esx 3.0.1; NIC teaming is configured in active/active) is able to ping just one of the 2 switch.
It is a big problem for Virtual infrastructure.
For the moment, i only use half of my nics, the second gbe2c is not in use because of my problem.
I configure UFD to disable internal ports when my uplink 21 fail.
I flash it both to V2.0 (image and boot) with no better results.
Uplink to 2 core network HP on port 21 (or 21 and 22 in a cross configuration), but it still the same.
I enabled port 17 and 18 for trunk 1. These ports was disabled y default, strange ? and no more results.
What I' ve done bad ? where i fail ?
Thanks for your help.
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-20-2007 09:48 AM
тАО09-20-2007 09:48 AM
Solution
I have seen this behavior before. It usually happens because of the way the GBE2c management interface connects to the Onboard Administrator instead of going out the standard uplinks.
It is normal behavior for the 2 gbe2cs in an enclosure to not be able to ping each other. This is just a function of how they connect to the Onboard Administrator in an out-of-band fashion.
When servers or external devices can't ping one of the gbe2c switches, it is usually due to that switch being the root for the network. When a switch is the root, it forwards BPDU's out every 2 seconds and uses the same MAC address as its source to send out the uplinks as the one used by the management IP (sent out the OA port). This causes a problem. You can view the spanning tree config on a gbe2c by issuing the following command:
/i/l2/stp
compare the current root MAC Address with the switch's MAC address from here:
/i/sys/gen
If they are the same, that is your problem.
3 ways to correct this:
1) ensure some other switch is the spanning tree root bridge of your network(s). Lowest STP Bridge Priority will become the root
2) Instead of using the management interfaces that connect to the OA (Interface 256), disable that interface and put your IP address on Interface 1 in the desired VLAN
3) Put the OA port in a VLAN that is not configured on the GBE2
It is normal behavior for the 2 gbe2cs in an enclosure to not be able to ping each other. This is just a function of how they connect to the Onboard Administrator in an out-of-band fashion.
When servers or external devices can't ping one of the gbe2c switches, it is usually due to that switch being the root for the network. When a switch is the root, it forwards BPDU's out every 2 seconds and uses the same MAC address as its source to send out the uplinks as the one used by the management IP (sent out the OA port). This causes a problem. You can view the spanning tree config on a gbe2c by issuing the following command:
/i/l2/stp
compare the current root MAC Address with the switch's MAC address from here:
/i/sys/gen
If they are the same, that is your problem.
3 ways to correct this:
1) ensure some other switch is the spanning tree root bridge of your network(s). Lowest STP Bridge Priority will become the root
2) Instead of using the management interfaces that connect to the OA (Interface 256), disable that interface and put your IP address on Interface 1 in the desired VLAN
3) Put the OA port in a VLAN that is not configured on the GBE2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-20-2007 08:32 PM
тАО09-20-2007 08:32 PM
Re: Gbe2c communication problems
Thanks for you interest HEM.
Gbe2c's are not root bridge of RSTP. I verify with your commands and mac address are differents.
I'm using EBIPA (OA firmware 1.30) for configuring management IP of Gbe2c and it's true that is on interface 256 on VLAN 4095. :-/
I will try to configure static IP address on my Gbe2c on interface 1 VLAN 1.
It's difficult for us to change OA VLAN
Gbe2c's are not root bridge of RSTP. I verify with your commands and mac address are differents.
I'm using EBIPA (OA firmware 1.30) for configuring management IP of Gbe2c and it's true that is on interface 256 on VLAN 4095. :-/
I will try to configure static IP address on my Gbe2c on interface 1 VLAN 1.
It's difficult for us to change OA VLAN
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-23-2007 07:55 PM
тАО09-23-2007 07:55 PM
Re: Gbe2c communication problems
The results:
I have disabled UFD, keeping RSTP.
In each Gbe2c, I have disabled interface 256 that hold the IP configured through EBIPA in VLAN 4095.
I also disabled GW 4 to enable GW 1 but it don't work.
Then i put a static IP and GW in interface 1 (=> VLAN 1).
It seems to work fine without EBIPA !!
Thanks a lot for your help.
I have disabled UFD, keeping RSTP.
In each Gbe2c, I have disabled interface 256 that hold the IP configured through EBIPA in VLAN 4095.
I also disabled GW 4 to enable GW 1 but it don't work.
Then i put a static IP and GW in interface 1 (=> VLAN 1).
It seems to work fine without EBIPA !!
Thanks a lot for your help.
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