VSX ClusterXL

[CyberBreaker]

Hi Guys, not sure if this output is normal when dealing in active standby VSX.

when I do "cphaprob state" in the VS0 it shows that it is active standby. But, when I enter a specific VS such as VS1 then I do "cphaprob state" it shows that this VS is in active active in both VSX gateways.

is this the normal scenario? Is this means the both VAX gateways forwards traffic in that VS?

thank you.

[HeikoAnkenbrand · Accepted solution]

In VS0 you should always see the status of the VSX ClusterXL. For example the following is normal for VSX LS:
GW1: active GW2: standby GW3: standby

The virtual systems VS1, VS2,... can have different status informations.
For example:
VS on GW1: active
VS on GW2: standby  (full session and tabel sync with the active VS gateway)
VS on GW3: backup   (no session and tabel sync with the active VS gateway)

Here a list with cluster states:

[HeikoAnkenbrand]

Here you find a cheat sheet with ClusterXL information:
R80.x - cheat sheet - ClusterXL

[CyberBreaker]

Hi @HeikoAnkenbrand , thanks for the feedback and help. But why mine is when I do cphaprob state in VS0 it shows that active/standby in each cluster members but when I go inside a specific VS then do cphaprob state, I can see active/active for both cluster members. 

What is the meaning of it? Thanks

[Magnus-Holmberg]

Am running some VSX in HA and all of the members are active/standby same with the VS atleast for R80.10 and up.
Same with VR that are active/standby, VSW complains if you do that command.

In VSLS it should show active / standby on all members when everything is OK.
The active will be on diff member depending what vs you check for.

Regards
Magnus

[CyberBreaker]

Hi @Magnus-Holmberg , which means my current status right now is abnormal. Is the Monitoring blade needs to be enabled for the clusterXL monitoring that will help for this? thanks

[Magnus-Holmberg]

For HA the standard should be Active / Standby. 
If there is something else there is an issue.

@HeikoAnkenbrand did post a list of all statuses 🙂

Regards
Magnus

[CyberBreaker]

Hi @Magnus-Holmberg , yup I saw @HeikoAnkenbrand's posts. Do you have any idea why my VS goes active/active in both cluster members? Thanks

[_Val_ · Accepted solution]

If you are running a bridge mode, it will be shown active-active, as it is supposed to be. 

Please share with us your "cphaprob stat" from VS0 and also "vsx stat -v" output, then we can be sure what's going on

[HeikoAnkenbrand]

Hi @CyberBreaker,

I agree with @_Val_.

In which mode do you use the VS?
- Bride mode a/a     (I think active/active)
- Bridge mode a/s

In the virtual system general properties page of the virtual system object, you can see the selected mode! Maybe a screenshot of this as well.

Can you send a screenshot of "cphaprob stat" in "vsenv 0"

[CyberBreaker]

Hi @_Val_ @HeikoAnkenbrand , sorry I forgot to include it in my first statement. Yes, my VSX' are running in bridge mode.

The cphaprob stat in VS0 states that FW1 is Active and FW2 is Standby. The cphaprob in VS1 and VS2 states that both FW1 and FW2 are Active.

So meaning, this scenario is normal?

Thanks

[_Val_]

yes, it is normal

[CyberBreaker]

Hi @_Val_ , thanks for the confirmation 😁.

[HeikoAnkenbrand]

@_Val_ was two seconds faster.
Yes, that's normal.

[CyberBreaker]

Thanks also @HeikoAnkenbrand for the help 😁

[_Val_]

lol, there is no competition here 🙂 

[CyberBreaker]

Hi @_Val_ just a follow up question. Even if the VS shows active/active, it will still follow the cluster role which is active/standby state, correct? So if I failover, the VS will now pass traffic to the new active VSX gateway, correct?

[_Val_]

The state is per VS. If a VS fails over, then yes, traffic will be handled as you say