- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- network card link status issues
Operating System - Linux
1752584
Members
4339
Online
108788
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
тАО04-08-2010 06:58 AM
тАО04-08-2010 06:58 AM
Hi,
I wonder if the behavior i have is an issue with the c3000 blade switch, the RedHat configuration or something on the SG configuration.
I have a two node cluster in SG (Redhat 5), each node is on a Bl460c blade and the blade is loaded on a C3000 chasis. The networking is provided by the standard HP switching present on the C3000 starter kit.
Everytime the network status in one node changes, the other node "sees" the changes.
Example: if i stop networking on node1 then on node2 you can see entries in /var/log/messages about link status changes for eth0,eth1,eth2,eth3.
if you start networking on node1 then again you will read about link status changed on node2.
I remember I read something about disabling link status reporting on the C3000 switches but i have not found that article again.
My theory is that this particular configuration (sg,c3000,virtual switch) is present, then the link status of the physical port changes according to what is being done by the underlying OS (ifdown ethX, ifup ethX). However this "link status" is propagated to all virtual ports being addressed to that physical port so each blade will "see" a link status change and SG will "think" there has been a massive network failure.
I have Windows machines running directly on other blades on the same chassis but have not seen the same behavior. Maybe Windows is not so sensitive as Linux is.
is this normal in configurations with C3000 switches or do i need to do something additional so the "status" of the link is not shared among nodes/virtual nodes?
i am actually not sure if this has to be psoted in SG or C3000 forums, so i post here first.
thanks,
I wonder if the behavior i have is an issue with the c3000 blade switch, the RedHat configuration or something on the SG configuration.
I have a two node cluster in SG (Redhat 5), each node is on a Bl460c blade and the blade is loaded on a C3000 chasis. The networking is provided by the standard HP switching present on the C3000 starter kit.
Everytime the network status in one node changes, the other node "sees" the changes.
Example: if i stop networking on node1 then on node2 you can see entries in /var/log/messages about link status changes for eth0,eth1,eth2,eth3.
if you start networking on node1 then again you will read about link status changed on node2.
I remember I read something about disabling link status reporting on the C3000 switches but i have not found that article again.
My theory is that this particular configuration (sg,c3000,virtual switch) is present, then the link status of the physical port changes according to what is being done by the underlying OS (ifdown ethX, ifup ethX). However this "link status" is propagated to all virtual ports being addressed to that physical port so each blade will "see" a link status change and SG will "think" there has been a massive network failure.
I have Windows machines running directly on other blades on the same chassis but have not seen the same behavior. Maybe Windows is not so sensitive as Linux is.
is this normal in configurations with C3000 switches or do i need to do something additional so the "status" of the link is not shared among nodes/virtual nodes?
i am actually not sure if this has to be psoted in SG or C3000 forums, so i post here first.
thanks,
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-09-2010 06:10 AM
тАО04-09-2010 06:10 AM
Solution
I would recommend posting this to the C3000 and Linux forums. Posting to multiple forums is OK as long as you indicate that is what you are doing.
I could not tell if the replicated status is seen only be SG or by the OS as well.
If it is seen by the OS, then it does not sound like an SG problem. If it is not seen by the OS then a useful piece of information is that SG uses MII in monitoring the network.
I could not tell if the replicated status is seen only be SG or by the OS as well.
If it is seen by the OS, then it does not sound like an SG problem. If it is not seen by the OS then a useful piece of information is that SG uses MII in monitoring the network.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-09-2010 06:26 AM
тАО04-09-2010 06:26 AM
Re: network card link status issues
MII....hmmm interesting.
Will do some checks and repost to C3000 forum. Many thanks for the advice!
Will do some checks and repost to C3000 forum. Many thanks for the advice!
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