{hold:node0}
user@host1> show chassis cluster status
Cluster ID. 1
Node Priority Status Preempt Manual failover
Redundancy group: 0 , Failover count: 0
node0 1 hold no no
node1 0 lost n/a n/a
{hold:node0}
user@host1> show configuration | no-more
system {
host-name host1;
root-authentication {
encrypted-password “$1$KI99zGk6$MbYFuBbpLffu9tn2.sI7l1”; ## SECRET-DATA
}
name-server {

172.16.10.100;
}
services {
ssh;
telnet;
web-management {
http;
}}
syslog {
user * {
any emergency;
}
file messages {
any any;
authorization info;
}
file interactive-commands {
interactive-commands any;
}}}
interfaces {
ge-0/0/0 {
unit 0 {
family inet {
address 10.210.14.131/26;
}}}
ge-0/0/8 {
unit 0 {
family inet {
address 172.16.1.1/24;
}}}
ge-0/0/9 {
unit 0 {
family inet {
address 172.16.10.1/24;
}}}}
security {
policies {
default-policy {

permit-all;
}}
zones {
functional-zone management {
interfaces {
ge-0/0/0.0;
}
host-inbound-traffic {
system-services {
ssh;
telnet;
ping;
traceroute;
http;
snmp;
}}}
security-zone Trust {
host-inbound-traffic {
system-services {
any-service;
}}
interfaces {
ge-0/0/9.0;
}}
security-zone Untrust {
host-inbound-traffic {
system-services {
any-service;
}}
interfaces {
ge-0/0/8.0;
}}}}
—————-
{hold:node1}
user@host2> show chassis cluster status
Cluster ID. 1
Node Priority Status Preempt Manual failover
Redundancy group: 0 , Failover count: 0
node0 0 lost n/a n/a

node1 1 hold no no
{hold:node1}
user@host2> show configuration | no-more
system {
host-name host2;
root-authentication {
encrypted-password “$1$KI99zGk6$MbYFuBbpLffu9tn2.sI7l1”; ## SECRET-DATA
}
name-server {
172.16.10.100;
}
services {
ssh;
telnet;
web-management {
http;
}}
syslog {
user * {
any emergency;
}
file messages {
any any;
authorization info;
}
file interactive-commands {
interactive-commands any;
}}}
interfaces {
ge-0/0/0 {
unit 0 {
family inet {
address 10.210.14.132/26;
}}}
ge-0/0/8 {
unit 0 {
family inet {
address 172.16.1.1/24;
}}}
ge-0/0/9 {
unit 0 {

family inet {
address 172.16.10.1/24;
}}}}
security {
policies {
default-policy {
permit-all;
}}
zones {
functional-zone management {
interfaces {
ge-0/0/0.0;
}
host-inbound-traffic {
system-services {
ssh;
telnet;
ping;
traceroute;
http;
snmp;
}}}
security-zone Trust {
host-inbound-traffic {
system-services {
any-service;
}}
interfaces {
ge-0/0/9.0;
}}
security-zone Untrust {
host-inbound-traffic {
system-services {
any-service;
}}
interfaces {
ge-0/0/8.0;
}}

}}
A user attempted to form a chassis cluster on an SRX240; however, the cluster did not form. While
investigating the problem, you see the output shown in the Above. What is causing the problem?

Click the Exhibit button.

There is an existing chassis cluster connected to the corporate network 192.168.1.0/24. You are
asked to connect another department to this VLAN. To achieve this, you add a new chassis cluster to
the network. After connecting to the network, the cluster experiences traffic problems. You have
verified that the addresses and VLAN IDs are configured correctly. Referring to the exhibit, which
configuration would resolve this problem?

— Exhibit —
{primary:node0}
user@host> show configuration chassis | display inheritance
cluster {
redundancy-group 1 {
node 0 priority 200;
node 1 priority 100;
interface-monitor {
ge-0/0/12 weight 255;
ge-5/0/12 weight 255;
}}}
— Exhibit —
A customer reports that their SRX failover is not working as expected. They expected node1 to
become the primary node for the control plane when interface ge-0/0/12 failed. However, when ge-
0/0/12 failed, node0 remained the primary node. They send you the output shown in the exhibit.
What is causing this problem?