GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- lan configuration on MC/SG
Operating System - HP-UX
1845515
Members
2522
Online
110244
Solutions
This widget could not be displayed.
This widget could not be displayed.
This widget could not be displayed.
This widget could not be displayed.
This widget could not be displayed.
This widget could not be displayed.
This widget could not be displayed.
Forums
Categories
This widget could not be displayed.
Company
This widget could not be displayed.
Local Language
This widget could not be displayed.
back
This widget could not be displayed.
This widget could not be displayed.
This widget could not be displayed.
back
This widget could not be displayed.
This widget could not be displayed.
This widget could not be displayed.
Blogs
Information
This widget could not be displayed.
This widget could not be displayed.
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
- This widget could not be displayed.This widget could not be displayed.This widget could not be displayed.This widget could not be displayed.This widget could not be displayed.This widget could not be displayed.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-21-2004 12:43 AM
05-21-2004 12:43 AM
lan configuration on MC/SG
I try to configure three nodes in a cluster with a different number of lan cards (1 node 8 lan cards the others two with 5 lan cards), but cmapplyconf
fails.
Is it mandatory to have all nodes of the cluster with the same number of lan cards?
thanks
fails.
Is it mandatory to have all nodes of the cluster with the same number of lan cards?
thanks
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-21-2004 12:51 AM
05-21-2004 12:51 AM
Re: lan configuration on MC/SG
No, thats nor required.
But you should only use lans-subnets as heartbeat ALL systems are in.
I.e.:
NODE_NAME system1
NETWORK_INTERFACE lan2
HEARTBEAT_IP 192.1.2.3
NETWORK_INTERFACE lan0
HEARTBEAT_IP 10.99.99.18
NETWORK_INTERFACE lan1
STATIONARY_IP 10.254.254.10
For your 8 lan system there should be minimum 3 STATIONARY_IP entries and max. 5 HEARTBEAT_IP entries.
ANY HEARTIP_IP need to be available on every SG node.
So:
Use HARTBEAT_IP only for subnets ALL your systems are conencted to, the rest you have to configure as "STATIONARY_IP".
PS: Thats in the file /etc/cmcluster/cmclconf.ascii.
But you should only use lans-subnets as heartbeat ALL systems are in.
I.e.:
NODE_NAME system1
NETWORK_INTERFACE lan2
HEARTBEAT_IP 192.1.2.3
NETWORK_INTERFACE lan0
HEARTBEAT_IP 10.99.99.18
NETWORK_INTERFACE lan1
STATIONARY_IP 10.254.254.10
For your 8 lan system there should be minimum 3 STATIONARY_IP entries and max. 5 HEARTBEAT_IP entries.
ANY HEARTIP_IP need to be available on every SG node.
So:
Use HARTBEAT_IP only for subnets ALL your systems are conencted to, the rest you have to configure as "STATIONARY_IP".
PS: Thats in the file /etc/cmcluster/cmclconf.ascii.
Working together
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-21-2004 12:54 AM
05-21-2004 12:54 AM
Re: lan configuration on MC/SG
No - its not mandatory to have all nodes of the cluster with the same number of lan cards.
What error message do you get with cmapplyconf? Is it the same when you cmcheckconf? run it with -v
Rgds...Geoff
What error message do you get with cmapplyconf? Is it the same when you cmcheckconf? run it with -v
Rgds...Geoff
Proverbs 3:5,6 Trust in the Lord with all your heart and lean not on your own understanding; in all your ways acknowledge him, and he will make all your paths straight.
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 2026 Hewlett Packard Enterprise Development LP