- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- ProLiant Servers (ML,DL,SL)
- >
- Re: W2K3 Cluster Setup - Networking
Categories
Company
Local Language
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
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
Community
Resources
Forums
Blogs
- 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-03-2007 10:33 PM
тАО04-03-2007 10:33 PM
W2K3 Cluster Setup - Networking
How do people sugest setting up the networks? Dedicate 1 NIC to heartbeat only on 1 switch, using a sepearte IP range?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-04-2007 08:22 AM
тАО04-04-2007 08:22 AM
Re: W2K3 Cluster Setup - Networking
I would then configure the cluster to use the primary heartbeat nic first, secondary heartbeat nic second and the public interface third for heartbeat.
and yes I would make all 3 NIC/teams be on separate "networks" or vlans.
example:
public teamed interface: 10.96.100.x
heartbeat primary: 192.168.1.x
heartbeat secondary:192.168.2.x
You also want to make sure that the heartbeat and public nics are running across the separate switches
example:
switch A should have public A and primary heartbeat
switch B should have public B and secondary heartbeat
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-04-2007 09:35 AM
тАО04-04-2007 09:35 AM
Re: W2K3 Cluster Setup - Networking
You do not want to team your nic's for a single heartbeat connect, always opt for 2 separate heartbeats.
Steven
HP Master ASE, Storage, Servers, and Clustering
MCSE (NT 4.0, W2K, W2K3)
VCP (ESX2, Vi3, vSphere4, vSphere5, vSphere 6.x)
RHCE
NPP3 (Nutanix Platform Professional)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-04-2007 08:44 PM
тАО04-04-2007 08:44 PM
Re: W2K3 Cluster Setup - Networking
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-04-2007 11:15 PM
тАО04-04-2007 11:15 PM
Re: W2K3 Cluster Setup - Networking
With only 2 nics, simply use the first one for your public connection and second for your heartbeat.
If you must have redundant public connections, make both nics public and designate one or both as heartbeat in the cluster configuration. You only need to set the public IP address.
Steven
HP Master ASE, Storage, Servers, and Clustering
MCSE (NT 4.0, W2K, W2K3)
VCP (ESX2, Vi3, vSphere4, vSphere5, vSphere 6.x)
RHCE
NPP3 (Nutanix Platform Professional)