Juniper SRX5400, Hardware Manual

Page: 319 / 394

NOTE: The command output must indicate that the node priority is set
to a non-zero value, and that the cluster contains a primary node and a
secondary node.
12.
Initiate Redundancy Group (RG) failover to the upgraded node, manually, so that it
is assigned to all RGs as a primary node.
For RG0, issue the following command:
admin@cluster> request chassis cluster failover redundancy-group 0 node 1
For RG1, issue the following command:
admin@cluster> request chassis cluster failover redundancy-group 1 node 1
Verify that all RGs are failed over by issuing the following command:
admin@cluster>
show chassis cluster status
13.
Verify the operations of the upgraded secondary node by performing the following:
•
To ensure all FPC’s are online, issue the following command:
admin@cluster> show chassis fpc pic-status
•
To ensure all RG’s are upgraded and the node priority is set to a non-zero value,
issue the following command:
admin@cluster> show chassis cluster status
•
To ensure that the upgraded primary node receives and transmits data, issue the
following command:
admin@cluster> monitor interface traffic
• To ensure sessions are created and deleted on the upgraded node, issue the
following command:
admin@cluster> show security monitoring
14.
Repeat Step 1 through 12 for the primary node.
15.
To ensure that the ISHU process is completed successfully, check the status of the
cluster by issuing the following command:
admin@cluster> show chassis cluster status
Monitor Failure codes:
CS Cold Sync monitoring FL Fabric Connection monitoring
GR GRES monitoring HW Hardware monitoring
IF Interface monitoring IP IP monitoring
LB Loopback monitoring MB Mbuf monitoring
NH Nexthop monitoring NP NPC monitoring
SP SPU monitoring SM Schedule monitoring
CF Config Sync monitoring
293 Copyright © 2017, Juniper Networks, Inc.
Chapter 29: Replacing Host Subsystem Components