Operating System - HP-UX
1832279 Members
2202 Online
110041 Solutions
New Discussion

No failover when subnet is dropped

 
SOLVED
Go to solution
Bret Allibone
Advisor

No failover when subnet is dropped

Testing MC/ServiceGuard failover I tried to force a package switch from the primary node to the secondary node by disabling both ports on subnet "A".

Disabling port 1 syslog reported:
cmcld: lan3 failed
cmcld: Subnet "A" switched from lan3 to lan1
cmcld: lan3 switched to lan1

Disabling port 2 syslog reported:
cmcld: lan1 failed
cmcld: Subnet "A" down

This did not cause the package to switch.

Later, the package was active on the secondary node and I disabled subnet "B". This caused the package to switch.

The difference between subnet "A" and subnet "B" is, subnet "B" carries a heartbeat. This is not the only heartbeat as we have a subnet "C" which is a dedicated heartbeat.

I would like to configure MC/ServiceGuard to switch in the event of a subnet "A" failure. Will I need to configure it as a heartbeat interface or can it be done another way?

Bret.
Marmite is superior to Vegemite
12 REPLIES 12
Dietmar Konermann
Honored Contributor

Re: No failover when subnet is dropped

Bret,

You need to add the Subnet A to the package configuration (*.conf file) using the SUBNET statement.

Regards...
Dietmar.
"Logic is the beginning of wisdom; not the end." -- Spock (Star Trek VI: The Undiscovered Country)
Mark van Hassel
Respected Contributor

Re: No failover when subnet is dropped

Hi Bret,

Edit the package confgiuration file:

Enter the network subnet name that is to be monitored for this package.
# Repeat this line as necessary for additional subnet names. If any of
# the subnets defined goes down, the package will be switched to another
# node that is configured for this package and has all the defined subnets
# available.

SUBNET subnetA


HtH,

Mark

The surest sign that life exists elsewhere in the universe is that none of it has tried to contact us
Sanjay_6
Honored Contributor

Re: No failover when subnet is dropped

Hi Bret,

The package will switch if the subnet is lost only if the subnet is being monitored for that package.

subnet monitoring for that package is set in the package configuration file and the varaiable is

SUBNET a.b.c.d

here a.b.c.d is the subnet being monitored.

Hope this helps.

Regds
Bret Allibone
Advisor

Re: No failover when subnet is dropped

Thanks for the quick replies, but my package_name.conf file already has the subnet listed, see below:

PACKAGE_NAME pkg_name
FAILOVER_POLICY CONFIGURED_NODE
FAILBACK_POLICY MANUAL
NODE_NAME node1
NODE_NAME node2
RUN_SCRIPT pkg.cntl
RUN_SCRIPT_TIMEOUT NO_TIMEOUT
HALT_SCRIPT pkg.cntl
HALT_SCRIPT_TIMEOUT NO_TIMEOUT
SERVICE_NAME mcsg_service
SERVICE_FAIL_FAST_ENABLED NO
SERVICE_HALT_TIMEOUT 300
SUBNET bbb.bbb.bbb.bbb
SUBNET aaa.aaa.aaa.aaa
PKG_SWITCHING_ENABLED YES
NET_SWITCHING_ENABLED YES
NODE_FAIL_FAST_ENABLED NO

Is this configuration correct?

Bret.
Marmite is superior to Vegemite
Dietmar Konermann
Honored Contributor

Re: No failover when subnet is dropped

Should be OK.
Could you post a comlete cmviewconf output a long with an extract of your syslog.log, where the package was running?
"Logic is the beginning of wisdom; not the end." -- Spock (Star Trek VI: The Undiscovered Country)
Bret Allibone
Advisor

Re: No failover when subnet is dropped

cmviewconf attached, syslog to follow.

Bret.
Marmite is superior to Vegemite
Bret Allibone
Advisor

Re: No failover when subnet is dropped

syslog file attached.

Bret.
Marmite is superior to Vegemite
Dietmar Konermann
Honored Contributor
Solution

Re: No failover when subnet is dropped

Hi, Bret!

I see in your config:

Package information:

package ID 26625:
package name: pkg
...
package subnet: aag.aag.aag.aag


Only one "package subnet:" line... so maybe youd did not apply the configuration continaing both SUBNET lines?

Also strange is that Net A is listed... so you should have problems with Net B? Or did you accidently swap the naming?

Regards...
Dietmar.
"Logic is the beginning of wisdom; not the end." -- Spock (Star Trek VI: The Undiscovered Country)
Ashwani Kashyap
Honored Contributor

Re: No failover when subnet is dropped

I think your package is configured to run on a heartbeak network aaa.aaa.aaa.aaa.

I think it should run on a non heartbeat network bbb.bbb.bbb.bbb.

Try this , in your package conf file remove the entry for SUBNET bbb.bbb.bbb.bbb . Leave the entry for subnet a .

halt your cluster . reapply the package conf file , bring the cluster up and then try failing over .
Bret Allibone
Advisor

Re: No failover when subnet is dropped

Err, guys... I think I've found the problem. I have just done a cmcheckconf on the package configuration file and it produced the following output:

# cmcheckconf -P pkg.conf

Begin package verification...
Error: Adding subnets to package pkg is not allowed while the package is running
Error: Failed to modify package prod_pkg
cmcheckconf : Configuration check failed.

So I guess my problem will be fixed if I halt the package, cmcheckconf and cmapplyconf the package configuration file and run the package. Is that correct?

Bret.
Marmite is superior to Vegemite
Dietmar Konermann
Honored Contributor

Re: No failover when subnet is dropped

Correct. Cluster halt is NOT needed for this.
"Logic is the beginning of wisdom; not the end." -- Spock (Star Trek VI: The Undiscovered Country)
Bret Allibone
Advisor

Re: No failover when subnet is dropped

Marvellous. Thank you for all your help.

Bret.
Marmite is superior to Vegemite