VSX VSLS: Interface active check

Marcovb — Thu, 14 Oct 2021 08:03:01 GMT

Hi all,

I have an issue in VSX. I wonder what's the logic behind this, and maybe you could help me out.

I have an R80.40 VSX cluster (jumbo 120) running in VSLS mode. For the sake of argument I have the following simplified example, in my real setup there are a few more VS'es:

VS0 uses interfaces Mgmt for DMI and bond0 for sync
VS1 only uses bond1 as a VLAN trunk, multiple VLAN interfaces are created here
VS2 only uses bond2 as a VLAN trunk, multiple VLAN interfaces are created here

- bond1 is currently shutdown (on the adjecent switch) because VS1 will not be put into production yet. We can't enable this interface.
- bond2 is currently active and VS2 is handling traffic.

Now the issue: cphaprob stat shows Active(!)/Down on VS2 because bond1 is down. (interface active check)

When I check "cphaprob -a if" on VS2, I don't see any mention of bond1 here, as expected. Why does this VS suffer from the fact that an interface for a different VS is down?

As a workaround, could I use the discntd.if file to circumvent this? Its only temporarily since bond1 will be enabled in a few weeks. I read somewhere else that using this file in VSX is not recommended.

I hope someone can shed some light on this.

Regards,
Marco

Re: VSX VSLS: Interface active check

Chris_Atkinson — Thu, 14 Oct 2021 11:22:09 GMT

Have a look at reference PRJ-30284 resolved in JHF T125.

Re: VSX VSLS: Interface active check

Marcovb — Thu, 14 Oct 2021 11:25:16 GMT

Hi Chris,

Thanks for your answer, and wow - I did not realize this could have been a bug, I was thinking this was somehow a design choice. Thanks a lot for pointing this out, will upgrade right away.

topic Re: VSX VSLS: Interface active check in Firewall and Security Management

VSX VSLS: Interface active check

Re: VSX VSLS: Interface active check

Re: VSX VSLS: Interface active check