SRX5400 Chassis

The firewall chassis is a rigid sheet metal structure that houses all the other components (see Figure 1, Figure 2, and Figure 3). The chassis measures 8.71 in. (22.1 cm) high, 17.45 in. (44.3 cm) wide, and 24.5 in. (62.2 cm) deep (from the front to the rear of the chassis). The chassis installs in standard 800-mm (or larger) enclosed cabinets, 19-in. equipment racks, or telco open-frame racks. Up to five firewalls can be installed in one standard (48 U) rack if the rack can handle their combined weight, which can be greater than 1100 lb (500 kg). See SRX5400 Firewall Physical Specifications for physical specifications for the SRX5400 Firewall.

Figure 1: Front View of a Fully Configured Firewall Chassis

Figure 2: Rear View of an AC-Powered Firewall Chassis

Figure 3: Rear View of a Fully Configured DC-Powered Firewall Chassis

Table 1 summarizes the physical specifications for the firewall chassis.

The midplane is located toward the rear of the chassis and forms the rear of the card cage. MPCs, SPCs, and SCB install into the midplane from the front of the chassis, and the power supplies install into the midplane from the rear of the chassis. The cooling system components also connect to the midplane.

The midplane performs the following major functions:

• Data path—Data packets are transferred across the midplane between the MPCs and SPCs through the fabric ASICs on the SCB.

• Power distribution—The power supplies are connected to the midplane, which distributes power to all the firewall components.

• Signal path—The midplane provides the signal path to the MPCs, SCB, SPCs, Routing Engine, and other system components for monitoring and control of the system.

The enhanced midplane supports Junos OS Release 15.1X49-D10. It provides greater per-slot fabric performance and signal integrity, along with error-free high speed data transfer, and it reduces cross-talk. The midplane supports link speeds up to 10 Gbps and is not field replaceable.

The craft interface shows you status and troubleshooting information at a glance and lets you perform many system control functions. It is hot-insertable and hot-removable. The craft interface is located on the front of the firewall above the upper fan tray.

Figure 4 shows the front panel of the craft interface and Table 2 describes the components on the front panel.

Figure 4: Front Panel of the Craft Interface

Two large alarm LEDs are located at the upper right of the craft interface. The circular red LED lights to indicate a major alarm condition that can result in a system shutdown. The triangular yellow LED lights to indicate a less severe minor alarm condition that requires monitoring or maintenance. Both LEDs can be lit simultaneously. A condition that causes an LED to light also activates the corresponding alarm relay contact on the craft interface.

To deactivate the major and minor alarms, press the button labeled ACO/LT (for “alarm cutoff/lamp test”), which is located to the right of the alarm LEDs. Deactivating an alarm turns off both LEDs and deactivates the device attached to the corresponding alarm relay contact on the craft interface.

Table 3 describes the alarm LEDs and alarm cutoff button in more detail.

Table 3: Alarm LEDs and Alarm Cutoff/Lamp Test Button

Shape	Label	Color	State	Description
	Major Alarm	Red	On steadily	Critical alarm LED—Indicates a critical condition that can cause the device to stop functioning. Possible causes include component removal, failure, or overheating.
	Minor Alarm	Yellow	On steadily	Warning alarm LED—Indicates a serious but nonfatal error condition, such as a maintenance alert or a significant increase in component temperature.
	ACO/LT	–	–	Alarm cutoff/lamp test button—Deactivates major and minor alarms. Causes all LEDs on the craft interface to light (for testing) when pressed and held.

The host subsystem has three LEDs, located on the upper left of the craft interface, that indicate its status. The LEDs labeled RE0 show the status of the Routing Engine and SCB in slot 0 . The LEDs labeled RE1 are disabled and have no function. Table 4 describes the functions of the host subsystem LEDs.

Each power supply has two LEDs on the craft interface that indicate its status. The LEDs, labeled 0 through 3, are located near the middle of the craft interface next to the PEM label. Table 5 describes the functions of the power supply LEDs on the craft interface.

Each slot in the card cage has a pair of LEDs on the craft interface that indicates the status of the card installed in it. The card LEDs are located along the bottom edge of the craft interface and are labeled 0 for the bottom slot reserved for the SCB and 0/1, 1, and 2 for the remaining slots.Table 6 describes the functions of the OK and Fail LEDs.

The fan tray LED are located near the middle of the craft interface. Table 7 describes the functions of the fan tray LEDs.

The craft interface has a row of Online/Offline buttons along its lower edge. Each button corresponds to one slot in the card cage. The Online/Offline buttons are only supported for slots containing MPC interface cards. You can install MPCs into slots:

• SRX5400–Any slot except bottom slot 0

• SRX5600–Any slot except bottom slots 0 or 1

• SRX5800–Any slot except center slots 0 or 1

To take an MPC offline using the Online/Offline buttons:

1. Press and hold the corresponding card’s Online/Offline button on slot 1 on the craft interface. The green OK/FAIL LED next to the button begins to blink. Hold until both the button’s LED and the MPC’s LED are off.

2. Issue the CLI show chassis fpc command to check the status of installed MPCs. As shown in the sample output, the value Offline in the column labeled State indicates that the MPC in slot 1 is now offline:

   content_copy zoom_out_map

   user@host> show chassis fpc
   
   Slot State            (C)  Total  Interrupt      DRAM (MB) Heap     Buffer
     0  Online            35      4          0       1024       13         25
     1  Online            47      3          0       1024       13         25
     2  Online            37      8          0       2048       18         14
    

   An MPC can also be taken offline via CLI command:

   content_copy zoom_out_map

   user@host> request chassis fpc slot 2 offline
   node0:
   --------------------------------------------------------------------------
   Offline initiated, use "show chassis fpc" to verify
   
   {primary:node0}
   

   content_copy zoom_out_map

   user@host> show chassis fpc
   node0:
   --------------------------------------------------------------------------
                        Temp  CPU Utilization (%)   Memory    Utilization (%)
   Slot State            (C)  Total  Interrupt      DRAM (MB) Heap     Buffer
     0  Online            35      7          0       1024       13         25
     1  Online            46      4          0       1024       13         25
     2  Offline         ---Offlined by cli command---
   
   After pushing MPC online button:
   

   content_copy zoom_out_map

   user@host> show chassis fpc
                        Temp  CPU Utilization (%)   Memory    Utilization (%)
   Slot State            (C)  Total  Interrupt      DRAM (MB) Heap     Buffer
     0  Online            34      5          0       1024       13         25
     1  Online            46      3          0       1024       13         25
     2  Offline         ---Offlined by button press---

To bring an MPC back online using the Online/Offline buttons:

1. Press and hold the corresponding card’s Online/Offline button on slot 1 on the craft interface. The green OK/FAIL LED next to the button and the MPC’s LED begins to blink. Hold until both the button’s LED and the MPC’s LED are green and steady.

2. Issue the CLI show chassis fpc command to check the status of installed MPCs. As shown in the sample output, the value Online in the column labeled State indicates that the MPC in slot 1 is functioning normally:

   Verify if the MPC is offline:

   content_copy zoom_out_map

   user@host> show chassis fpc
   node0:
   --------------------------------------------------------------------------
                        Temp  CPU Utilization (%)   Memory    Utilization (%)
   Slot State            (C)  Total  Interrupt      DRAM (MB) Heap     Buffer
     0  Online            37     23          0       2048       19         14
     1  Offline         ---Offlined by cli command---
     2  Online            49     37          0       1024       14         25
   

   The command output indicates the MPC is offline.

   Bring the MPC online for the first time by using the following CLI command:

   content_copy zoom_out_map

   user@host> request chassis fpc slot 1 online
   node0:
   --------------------------------------------------------------------------
   Online initiated, use "show chassis fpc" to verify
   
   

   Verify that the MPC is online:

   content_copy zoom_out_map

   user@host> request chassis fpc slot 1 online
   node 0
   node0:
   --------------------------------------------------------------------------
   FPC 1 already online
   

   The command output indicates the MPC is online.

   Confirm that the MPC in the chassis is online:

   content_copy zoom_out_map

   user@host> show chassis fpc
   node0:
   --------------------------------------------------------------------------
                        Temp  CPU Utilization (%)   Memory    Utilization (%)
   Slot State            (C)  Total  Interrupt      DRAM (MB) Heap     Buffer
     0  Online            37      6          0       2048       19         14
     1  Online            44     11          0       1024       23         29
     2  Online            49     22          0       1024       14         25
   

The craft interface has two alarm relay contacts for connecting the device to external alarm devices (see Figure 5). Whenever a system condition triggers either the major or minor alarm on the craft interface, the alarm relay contacts are also activated. The alarm relay contacts are located on the upper right of the craft interface.

Figure 5: Alarm Relay Contacts

The alarm relay contacts consist of two sets of connectors, one set for each of the two alarms (major and minor). For each alarm color there are three connectors. Table 8 describes the functions of the connectors.

Table 9 shows the electrical specifications for the alarm relay contacts.

Figure 6 shows an example wiring diagram for a simple alarm reporting device. In this case the device is a 12-volt light bulb that illuminates when the device encounters a condition that activates the major alarm LED and relay contacts. The alarm relay contacts can also be used to activate other devices such as bells or buzzers.

Figure 6: Example Alarm Reporting Device