This article provides information on how to allow NSM connectivity to a chassis cluster via a consistent Primary IP address for SNMP and SSH connectivity.

• SRX cluster.
• NSM connectivity via fxp0 IP addresses of each individual node.
• The requirement is to reach the Primary Cluster member via a consistent IP address (that is, use the same IP address to manage the cluster; irrespective of which node becomes the primary).

In addition to configuring a consistent primary-only IP address on both of the cluster members, configure an independent IP addresses for each node. Use the preferred tag on the independent IP addresses.

For example:

node0 {
     host-name Node0;
     backup-router 172.22.146.1 destination 172.22.135.0/24;
}
interfaces {
    fxp0 {
        unit 0 {
            family inet {
                address 172.22.146.155/24 {
                    preferred;
                }
address 172.22.146.154/24 {
    master-only;
}
        }
    }
    }
}
}
node1 {
     host-name Node1;
     backup-router 172.22.146.1 destination 172.22.135.0/24;
}
interfaces {
     fxp0 {
         unit 0 {
             family inet {
                 address 172.22.146.156/24 {
                 preferred;
             }
address 172.22.146.154/24 {
    master-only;
}
         }
     }
}
}
}

system {
system {

• Node0 will always connect to NSM by using the 172.22.146.155 preferred IP address.
• Node1 will always connect to NSM by using the 172.22.146.156 preferred IP address.
• The Primary cluster member is always accessible via the primary-only 172.22.146.154 IP address.

2021-03-24: Updated the article terminology to align with Juniper's Inclusion & Diversity initiatives.