Replacing a Routing Engine on the SRX3600 Services Gateway

The Routing Engine is located in the rear slot labeled RE0 on the services gateway. Before you replace the Routing Engine, you must power off the services gateway.

1. Place an electrostatic bag or antistatic mat on a flat, stable surface.
2. Attach an ESD grounding strap to your bare wrist and connect the strap to one of the ESD points on the chassis. For more information about ESD, see Preventing Electrostatic Discharge Damage to the SRX3600 Services Gateway.
3. If you have not already done so, power off the services gateway by pressing the Power button on the front panel of the SFB for three to five seconds.

   The PWR LED blinks to show you that the services gateway is shutting down. Wait for the services gateway to shut down before you proceed to the next step.

4. Disconnect any cables connected to the AUX or USB ports.
5. Loosen the captive screws at each end of the Routing Engine faceplate.
6. Pull open the ejector handles to unseat the Routing Engine.
7. Grasp the Routing Engine by the ejector handles and slide it halfway out of the chassis.

   Figure 1: Removing a Routing Engine

   

8. Place one hand underneath the Routing Engine to support it and slide it completely out of the chassis.
9. Place the Routing Engine on the antistatic mat.
10. Carefully align the sides of the replacement Routing Engine with the guides inside the chassis.
11. Slide the Routing Engine into the slot until you feel resistance, and then press the Routing Engine's faceplate until it engages the connectors.
12. Press both of the ejector handles inward to seat the Routing Engine.
13. Tighten the captive screws on the left and right of the Routing Engine.

    Figure 2: Installing a Routing Engine

    

14. Reconnect cables that were previously attached to the AUX or USB ports.
15. Power on the services gateway by pressing the Power button on the front panel of the SFB for three to five seconds. Wait for the services gateway to start. The OK/FAIL LED on the Routing Engine faceplate should blink green, then light steadily. Note

    The Routing Engine might require several minutes to boot. If after this time the OK/FAIL LED is red, remove and reinstall the Routing Engine. If the OK/FAIL LED remains red, the Routing Engine is not functioning properly. Contact your customer support representative.

    To check the status of the Routing Engine:

    user@host> show chassis routing-engine

    For more information about using the CLI, see the CLI Explorer.

16. If the Routing Engine was replaced on one of the nodes in a chassis cluster, then you need to copy certificates and key pairs from the other node in the cluster:

    1. Start the shell interface as a root user on both nodes of the cluster.

    2. Verify the files in the /var/db/certs/common/key-pair folder of the source node (other node in the cluster) and destination node (node on which the Routing Engine was replaced) by using the following command:

       ls -la /var/db/certs/common/key-pair/

    3. If the same files exist on both nodes, back up the files on the destination node to a different location. For example:

       root@SRX-B% pwd
       
       /var/db/certs/common/key-pair
       
       root@SRX-B% ls -la
       
       total 8
       
       drwx------ 2 root wheel 512 Jan 22 15:09
       
       drwx------ 7 root wheel 512 Mar 26 2009
       
       -rw-r--r-- 1 root wheel 0 Jan 22 15:09 test
       
       root@SRX-B% mv test test.old
       
       root@SRX-B% ls -la
       
       total 8
       
       drwx------ 2 root wheel 512 Jan 22 15:10
       
       drwx------ 7 root wheel 512 Mar 26 2009
       
       -rw-r--r-- 1 root wheel 0 Jan 22 15:09 test.old
       
       root@SRX-B%

    4. Copy the files from the /var/db/certs/common/key-pair folder of the source node to the same folder on the destination node.

       Note

       Ensure that you use the correct node number for the destination node.

    5. On the destination node, use the ls –la command to verify that all files from the /var/db/certs/common/key-pair folder of the source node are copied.

    6. Repeat Step b through Step e for the /var/db/certs/common/local and /var/db/certs/common/certification-authority folders.

17. If the Routing Engine was replaced for SPCs that are in the CP SPU mode (dedicated CP/full CP mode) in a chassis cluster, you can verify the Extreme licensing status:Note

    The Extreme license must be installed on both nodes of a chassis cluster. Reboot both the nodes for the license to take effect.

    1. To check the installed licenses:

       show system license

       For example:

       root@srx> show system license

    2. To check if the SPU is functioning as a full CP rather than CP-Flow (an SPU/CP combo):

       show chassis hardware detail no-forwarding or show chassis fpc pic-status

       For example:

       • Before the license installation:

         root@srx> show chassis hardware detail no-forwarding

         After the license installation:

         root@srx> show chassis hardware detail no-forwarding
       • root@srx> show chassis fpc pic-status