HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- how to config a dual-network cluster
Operating System - HP-UX
1829103
Members
2861
Online
109986
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
Forums
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
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
05-08-2003 04:15 AM
05-08-2003 04:15 AM
A server have two 10/100M network interface adapters connected to two switches separately to make network high available.
What steps should I follow on these two network adapters,and how to bind a single IP address on them.
many thanks
What steps should I follow on these two network adapters,and how to bind a single IP address on them.
many thanks
fred
Solved! Go to Solution.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-08-2003 04:39 AM
05-08-2003 04:39 AM
Solution
A. Configure basic NIC failover
1. In and MC/SG configuration you may have two NIC cards which connect
to the SAME LAN IP SEGMENT (or a "bridged network")! If one NIC card
fails, MC/SG automatically switches to the other one with the SAME
IP ADDRESS.
2. Set up both NIC card hardware on same LAN segment, or on the bridged
networks. Connect network cables. Verify blinking light.
Only configure the PRIMARY NIC card in /etc/rc.config.d/netconf.
2'. vi .rhosts
make sure that your own hostname is in your .rhosts.
You really have two choices here:
a. Put all node names in .rhosts.
b. Put all node names in:
/etc/cmcluster/cmclnodelist
3. cd /etc/cmcluster
cmquerycl -C gbo330-d.ascii -n gbo330-d
Query the node "gbo330-d" and create a configuration file,
"gbo330-d.ascii". The cluster name will be "cluster1". It
will only have one node in it and no LVs. No packages have
been created yet.
Verify that he got all the LAN cards, and that the primary
and failover NIC cards are listed in the comments as "bridged".
cp gbo330-d.ascii gbo330-d.ascii.orig
vi gbo330-d.ascii
Change the cluster name to "gbo330-d".
Put the heartbeat on both LANs (10BT and 100BT).
cmcheckconf -C gbo330-d.ascii
Verify the cluster configuration file is correct.
cmapplyconf -C gbo330-d.ascii
Verify (compile) and create "cluster binary configuration file",
/etc/cmcluster/cmclconfig, and distributes it to all nodes.
cmviewcl
cmruncl
Run the cluster. Since we have only created the one node, the
cluster will be initiated on node "gbo330-d".
cmviewcl
1. In and MC/SG configuration you may have two NIC cards which connect
to the SAME LAN IP SEGMENT (or a "bridged network")! If one NIC card
fails, MC/SG automatically switches to the other one with the SAME
IP ADDRESS.
2. Set up both NIC card hardware on same LAN segment, or on the bridged
networks. Connect network cables. Verify blinking light.
Only configure the PRIMARY NIC card in /etc/rc.config.d/netconf.
2'. vi .rhosts
make sure that your own hostname is in your .rhosts.
You really have two choices here:
a. Put all node names in .rhosts.
b. Put all node names in:
/etc/cmcluster/cmclnodelist
3. cd /etc/cmcluster
cmquerycl -C gbo330-d.ascii -n gbo330-d
Query the node "gbo330-d" and create a configuration file,
"gbo330-d.ascii". The cluster name will be "cluster1". It
will only have one node in it and no LVs. No packages have
been created yet.
Verify that he got all the LAN cards, and that the primary
and failover NIC cards are listed in the comments as "bridged".
cp gbo330-d.ascii gbo330-d.ascii.orig
vi gbo330-d.ascii
Change the cluster name to "gbo330-d".
Put the heartbeat on both LANs (10BT and 100BT).
cmcheckconf -C gbo330-d.ascii
Verify the cluster configuration file is correct.
cmapplyconf -C gbo330-d.ascii
Verify (compile) and create "cluster binary configuration file",
/etc/cmcluster/cmclconfig, and distributes it to all nodes.
cmviewcl
cmruncl
Run the cluster. Since we have only created the one node, the
cluster will be initiated on node "gbo330-d".
cmviewcl
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.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP