- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- a question about MC/SG
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
Forums
Discussions
Discussions
Discussions
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
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
03-05-2003 12:44 AM
03-05-2003 12:44 AM
I ping the heardbeat ip address and don't receive the echo package.But I press the command "cmruncl -v" ,two node both run.I think that they should not start because there is a communication failure of heartbeat between the nodes.Why they can run normally?
Thanks
Weit
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-05-2003 01:03 AM
03-05-2003 01:03 AM
Re: a question about MC/SG
i guess there is an alternate heart beat configured. it is using that. check for any errors / logs in the syslog.
-balaji
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-05-2003 01:17 AM
03-05-2003 01:17 AM
Re: a question about MC/SG
# cmscancl >/tmp/cmscancl.out
# more /tmp/cmscancl.out
Regards ...
Armin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-05-2003 01:23 AM
03-05-2003 01:23 AM
Re: a question about MC/SG
How can I find the information about alternate
heartbeat?Where is the information configured?
Thanks for your helping.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-05-2003 01:25 AM
03-05-2003 01:25 AM
Re: a question about MC/SG
# more /etc/cmcluster/cmclconf.ascii
Regards ...
Armin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-05-2003 01:42 AM
03-05-2003 01:42 AM
Re: a question about MC/SG
-balaji
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-05-2003 01:50 AM
03-05-2003 01:50 AM
Re: a question about MC/SG
Look Armin,this is the detail of the cluster.ascii file.
CLUSTER_NAME cluster1
FIRST_CLUSTER_LOCK_VG /dev/vglock
NODE_NAME ssokeysa
NETWORK_INTERFACE lan0
HEARTBEAT_IP 15.79.48.187
NETWORK_INTERFACE lan2
NETWORK_INTERFACE lan1
HEARTBEAT_IP 192.1.1.1
FIRST_CLUSTER_LOCK_PV /dev/dsk/c6t0d0
NODE_NAME ssokeysb
NETWORK_INTERFACE lan0
HEARTBEAT_IP 15.79.48.188
NETWORK_INTERFACE lan2
NETWORK_INTERFACE lan1
HEARTBEAT_IP 192.1.1.2
FIRST_CLUSTER_LOCK_PV /dev/dsk/c11t0d0
HEARTBEAT_INTERVAL 1000000
NODE_TIMEOUT 5000000
AUTO_START_TIMEOUT 600000000
NETWORK_POLLING_INTERVAL 2000000
MAX_CONFIGURED_PACKAGES 2
VOLUME_GROUP /dev/vglock
VOLUME_GROUP /dev/vgdata
The IP 192.1.1.1 to IP 192.1.1.2 don't communicate each other.
Why the cluster can run OK?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-05-2003 02:02 AM
03-05-2003 02:02 AM
Re: a question about MC/SG
Please paste the network part in the formen and I will try to explain.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-05-2003 02:18 AM
03-05-2003 02:18 AM
Re: a question about MC/SG
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-05-2003 02:47 AM
03-05-2003 02:47 AM
Re: a question about MC/SG
Looking at your cluster.ascii file, you have the heartbeat going out on bothy lan cards, so even if the dedicated heartbeat lan does not work, a heartbeat is still getting through on the data lan.
Regards,
Hilary
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-05-2003 02:51 AM
03-05-2003 02:51 AM
Re: a question about MC/SG
in the following you can see that the lan connection between your nodes works fine on layer 2 (DLPI):
###### Checking REMOTE network connections (ssokeysb to ssokeysa) ######
------ lan0 on node ssokeysb to lan0 on node ssokeysa ------
PPA 0 link test to 0x00306E0AC052 -- OK
------ lan0 on node ssokeysb to lan1 on node ssokeysa ------
PPA 0 link test to 0x00306E21B56F (NO CONNECTION)
------ lan0 on node ssokeysb to lan2 on node ssokeysa ------
PPA 0 link test to 0x00306E21D516 -- OK
------ lan1 on node ssokeysb to lan0 on node ssokeysa ------
PPA 1 link test to 0x00306E0AC052 (NO CONNECTION)
------ lan1 on node ssokeysb to lan1 on node ssokeysa ------
PPA 1 link test to 0x00306E21B56F (NO CONNECTION)
------ lan1 on node ssokeysb to lan2 on node ssokeysa ------
PPA 1 link test to 0x00306E21D516 (NO CONNECTION)
------ lan2 on node ssokeysb to lan0 on node ssokeysa ------
PPA 2 link test to 0x00306E0AC052 -- OK
------ lan2 on node ssokeysb to lan1 on node ssokeysa ------
PPA 2 link test to 0x00306E21B56F (NO CONNECTION)
------ lan2 on node ssokeysb to lan2 on node ssokeysa ------
PPA 2 link test to 0x00306E21D516 -- OK
So if you are not able to ping (layer 3) between the nodes, please check the config of your switch/router/bridge between the nodes, if layer 3 (IP) is open.
In my mind and in view of MC/SG all works fine. MC/SG only check the lan on layer 2 and that seam to be ok.
Regards ...
Armin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-05-2003 04:45 PM
03-05-2003 04:45 PM
Re: a question about MC/SG
You can see the ssokeysa's lan1 to ssokeysb don't connect.
Thanks all of your help.I love this forum!:)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-05-2003 11:22 PM
03-05-2003 11:22 PM
SolutionNODE_NAME ssokeysa
NETWORK_INTERFACE lan0 HEARTBEAT_IP 15.79.48.187
NETWORK_INTERFACE lan1 HEARTBEAT_IP 192.1.1.1
NODE_NAME ssokeysb
NETWORK_INTERFACE lan0 HEARTBEAT_IP 15.79.48.188
NETWORK_INTERFACE lan1 HEARTBEAT_IP 192.1.1.2
If on one node lan0 fails the heartbeat only go by lan1, for MC/SG no problem. DLPI pings can only work in the same physical network, so only lan0 to lan0 and lan1 to lan1.
------ lan0 on node ssokeysb to lan0 on node ssokeysa ------
PPA 0 link test to 0x00306E0AC052 -- OK
lan0 seams to be fine!!!
------ lan1 on node ssokeysb to lan1 on node ssokeysa ------
PPA 1 link test to 0x00306E21B56F (NO CONNECTION)
lan1 seams to be broken connection.
But like I'd said,if one of both heartbeat connections is working fine, MC/SG will start and protect your datas by corruption.
Regards ...
Armin