NOTE: If the services gateway only has one SPC installed, you must make sure that the full-cp-key
license that enables large central point mode is not installed. If the license is installed when you
upgrade from a single SPC to multiple SPCs, it changes the mode of the SPC in the lowest numbered
slot from combo mode to large central point. After that change, the run time objects (RTOs) do not
synchronize properly between the two devices in the cluster, and you incur network downtime
while the devices discard their existing RTOs and rebuild their RTO tables.
To install SPCs in an SRX3600 Services Gateway cluster without incurring downtime:
1. Use the console port on the routing engine to establish a command-line interface (CLI) session with
one of the devices in the cluster.
2. Use the show chassis cluster status command to determine which services gateway is currently primary,
and which services gateway is secondary, within the cluster.
3. If the device with which you established the CLI session in Step 2 is not the secondary node in the
cluster, use the console port on the device that is the secondary node to establish a CLI session.
4. If the services gateway has only one SPC installed in it, in the CLI session for the secondary services
gateway, use the show system license command to make sure the device does not have the full-cp-key
license installed:
5. If the services gateway has only one SPC installed and the full-cp-key license is also installed, record
the identifier of the full-cp-key license from the command output of the previous step. Then use the
following command to remove the license:
admin@node1_device> request system license delete identifier
6. In the CLI session for the secondary services gateway, use the request system power off command to
shut down the services gateway.
7. Wait for the secondary services gateway to completely shut down.
8. Install the new SPC or SPCs in the powered-off services gateway using the procedure in “Installing
CFM Cards in the SRX3600 Services Gateway” on page 125.
9. Power on the secondary services gateway and wait for it to finish starting.
10. Reestablish the CLI session with the secondary node device.
129
To Next Page
Loading...
Need help?
General
