Re: [j-nsp] vSRX Cluster ip-monitoring secondary address

In that case, you build a LAG on node0 that goes to a LAG on the switch, and a LAG on node1 that goes to a separate LAG on the switch. Is that the setup you're having issues with? e.g. (assuming a 2-member EX switch on the other end for simplicity's sake): |= - ge-0/0/0 <---> ge-0/0

Re: [j-nsp] vSRX Cluster ip-monitoring secondary address

This is very delayed, but are you connecting up the reth members to a LAG? e.g. reth0 members are: - srx1: ge-0/0/0 - srx2: ge-1/0/0 srx1 ge-0/0/0 <---> ge-a/b/c / \ reth0 aeX some switch (or MC-LAG setup) \

Re: [j-nsp] vSRX Cluster ip-monitoring secondary address

hi all, I managed to resolve this issue as being down to the arp replies not being deterministic from the switch port-channel facing the secondary SRX cluster node1. i.e they would use the incorrect physical interface from the port-channel list, where the arp's are sourced from the lowest physica

[j-nsp] vSRX Cluster ip-monitoring secondary address

I'm confused on where to physically or logically assign this address. I have declared my secondary address in the ip-monitoring stanza but the connected Router is receiving quite a few ARPs from this address because it's trying to ICMP for IP-monitoring purposes Issue is where do I expect the