Cluster states is ready

[memory_kai]

Ready State Can occur in following scenarios:
1. When a cluster is upgraded from one version of
VPN-1 to another, and the cluster members have
different versions of VPN-1, the members with a
new version have the ready state and the
members with the previous version have the
active state.
2. Before a cluster member becomes active, it
sends a message to the rest of the cluster, and
then expects to receive confirmations from the
other cluster members agreeing that it will
become active. In the period of time before it
receives the confirmations, the machine is in the
ready state.


the two modules have same version, the version is R70(Secureplatform+Hp 380G5), When i'm run "cphaprob stat" command, The output one modules cluster states is active ,but another modules's state is Ready, the two modules Cluster mode:New High Availability is (Primary up ) ; no at the active up mode

I think, tow modules to deem itself is Active , So one module will not receive confirmations from the other cluster members agreeing ,So how can I definition the module's Cluster priority in $FWDIR/CONF/CPHA.CONF

Thinks

[serlud]

Originally Posted by memory_kai

Ready State Can occur in following scenarios:
1. When a cluster is upgraded from one version of
VPN-1 to another, and the cluster members have
different versions of VPN-1, the members with a
new version have the ready state and the
members with the previous version have the
active state.
2. Before a cluster member becomes active, it
sends a message to the rest of the cluster, and
then expects to receive confirmations from the
other cluster members agreeing that it will
become active. In the period of time before it
receives the confirmations, the machine is in the
ready state.


the two modules have same version, the version is R70(Secureplatform+Hp 380G5), When i'm run "cphaprob stat" command, The output one modules cluster states is active ,but another modules's state is Ready, the two modules Cluster mode:New High Availability is (Primary up ) ; no at the active up mode

I think, tow modules to deem itself is Active , So one module will not receive confirmations from the other cluster members agreeing ,So how can I definition the module's Cluster priority in $FWDIR/CONF/CPHA.CONF

Thinks

You can simple change module's Cluster priority in SmartDashboar -> edit Cluster Object > Cluster members > increase or decrease Priority..

[memory_kai]

I'm do it, but in the monitor , the gaterway's states still Ready

and i'm edit the Maintain current active Cluster Member to Swith to higher priority Cluster Member but do not change the states


hao can i debug the cluster informations

Thanks

[Thorpuse]

This means either that SIC states aren't set correctly, or there's an incompatibility in the versions of the cluster members. Check on both cluster members and in the dashboard that all objects have been updated correctly, and that all versions, patches and hotfixes are equal.

[alienbaby]

I believe I've seen this when the topology config had an error. I had typo'd the third octet in one of the ip addresses.

[n1troboy]

did you ever find a solution for this?

[sass99]

i've had same situation then on one of the cluster members CoreXL was enabled but not on second one or ammount of cores allocated to FWD is different on members;You can check it via cpconfig or even using "fw ctl multik stat" .
Br,
alec

[plamy]

Ready is seen when using VRRP + R70, or another hot standby config. This is new in R70. It simply means that it is working and set to take over if needed.

-Pierre