VSX Internal Network Communication cluster nodes are on differente subnets

[FtW64]

Hello,

I have a very strange configuration on my VSX VSLS cluster (R80.20). On two of the VLANs on VS1, the VSX Internal Network Communication IP addresses are not on the same subnet. We initially configured 10.15.80.0/20 when we set up the VSX cluster (to allow for 1024 VLANs per VS, but this is irrelevant).

For example:

• cluster member 1, interface eth3-02.523, the IP address is 10.15.82.1 (/28)
• cluster member 2, interface eth3-02.523, the IP address is 10.15.82.34 (/28)

and:

• cluster member 1, interface bond1.3061, the IP address is 10.15.83.65 (/28)
• cluster member 2, interface bond1.3061, the IP address is 10.15.82.2 (/28) -- this one 'collides' with eth3-02.523!

I opened a TAC case and TAC is telling me that there is no issue and I can safely leave the situation as is. Yet I feel uncomfortable with this inconsistency.

Has anyone else seen this issue before?

What could have caused it?

Would it help if I run "vsx_util change_private_net" again? I.e., would that 'renumber' all interfaces consistently?

-Frank

[_Val_ · Accepted solution]

TAC is correct, you can safely ignore this. The addresses are not used for any communication but internal provisioning.