VSX Virtual Systems Issue

[xLadyMorgana]

Hi All, 

I'm building a new VSX in our environment and noticed that when creating virtual systems, they are not being created with HA and keep giving the 'HA module not started' when running the cphaprob stat command. i can't seem to figure out how to turn this on. Does anyone have any insight on this? I do have a TAC case open but figured I'd try to get some knowledge here as well.

This VSX cluster does have VSLS enabled. 

[PhoneBoy]

Have you installed policy to the VS in question?
Also what version/JHF is this?

[xLadyMorgana]

This is on R81.20 take 84. 

The policy actually keeps failing to push on the VS due to updatable object issue saying the package is missing on the gateway. I'm thinking this might be something related to DNS, as I've seen this error before due to a DNS issue.

I will say tho also, shouldnt the Virtual systems be automatically created with HA? regardless of a DNS issue.

[PhoneBoy · Accepted solution]

HA status is, at least partially, a function of the installed policy.
No policy, no HA.

[xLadyMorgana]

Thank you PhoneBoy. I definitely did not realize that the HA would show as not started if there was no policy. 

[xLadyMorgana]

Just to keep this thread up to date. it looks like the team who configured the switch side of things had changed the native vlan from the default, which is not supported. once that was changed back to default, we were able to push policy. 

[Chris_Atkinson]

sk120684 documents this when working with Bonds.

[JozkoMrkvicka]

As already mentioned, you have to install policy after VS creation.

If you have troubles with policy installation for existing policy package, try to create new policy package with any-any-any-drop rule as the only rule and install it on newly created VS.

[xLadyMorgana]

We did try this and still failed. I will need to dig deeper internally once again and see if the networking side of things is configured properly. Thank you