nerdexam
Juniper

JN0-696 · Question #21

{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…

The correct answer is D. The ge-0/0/0 interface is configured. Before we enable the SRX chassis, we need delete the configuration under ge-0/0/0 /. ge-0/0/0 will be fxp0.

Troubleshooting High Availability

Question

{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?

Options

  • AThe cluster IDs do not match.
  • BThe configurations are not identical.
  • CThe fxp0 interface is not configured.
  • DThe ge-0/0/0 interface is configured.

How the community answered

(13 responses)
  • B
    8% (1)
  • C
    8% (1)
  • D
    85% (11)

Explanation

Before we enable the SRX chassis, we need delete the configuration under ge-0/0/0 /. ge-0/0/0 will be fxp0.

Topics

#chassis cluster#node status lost#fabric link#interface conflict

Community Discussion

No community discussion yet for this question.

Full JN0-696 Practice