- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- ProLiant Servers (ML,DL,SL)
- >
- DL380 G4 server : proper setup for onboard NIC por...
ProLiant Servers (ML,DL,SL)
1748211
Members
5034
Online
108759
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
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
тАО01-25-2006 11:41 AM
тАО01-25-2006 11:41 AM
DL380 G4 server : proper setup for onboard NIC ports in cluster
WE have a pair of new DL380G4 servers and are having Wondows 2003 cluster failover issues.. I can elaborate with OS details later. On the hardware side:
using nic port 1 to the public lan
using nic port 2 for the private/heartbeat link
The system admins tell me every time they faiover the "cluster" to the other node.. they can no longer ping or contact the cluster ( via cluster name or ip.... Again I can qualify further.. My basic need is to assure the on mother board NIC ports can do this..
using nic port 1 to the public lan
using nic port 2 for the private/heartbeat link
The system admins tell me every time they faiover the "cluster" to the other node.. they can no longer ping or contact the cluster ( via cluster name or ip.... Again I can qualify further.. My basic need is to assure the on mother board NIC ports can do this..
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-27-2006 07:00 AM
тАО01-27-2006 07:00 AM
Re: DL380 G4 server : proper setup for onboard NIC ports in cluster
Hi,
Are you using a simple cross-over RJ45 link for the keepalive (heartbeat) link. This is the easiest way to do it and avoids lan interference.
Brian
Are you using a simple cross-over RJ45 link for the keepalive (heartbeat) link. This is the easiest way to do it and avoids lan interference.
Brian
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-27-2006 08:22 AM
тАО01-27-2006 08:22 AM
Re: DL380 G4 server : proper setup for onboard NIC ports in cluster
Hi,
in the cluster administrator, ensure the Private network is set for Internal Cluster communication only, and the public LAN is used for both internal and external communciation. Then set the priority so that the private network is first priority for internal communication.
Also, go to the properties of the private NICs and disable things like Client for Microsoft Networks or any other services, apart from TCP/IP and HP Network Configuration Utility.
Is network communication permanently down after failing over resources? Or does it return after a while (if so, how long?)
Regards,
Stephen
in the cluster administrator, ensure the Private network is set for Internal Cluster communication only, and the public LAN is used for both internal and external communciation. Then set the priority so that the private network is first priority for internal communication.
Also, go to the properties of the private NICs and disable things like Client for Microsoft Networks or any other services, apart from TCP/IP and HP Network Configuration Utility.
Is network communication permanently down after failing over resources? Or does it return after a while (if so, how long?)
Regards,
Stephen
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