Fortigate 5144C CG

FortiGate-5144C Chassis Guide
FORTINET DOCUMENTLIBRARY
http://docs.fortinet.com
FORTINETVIDEOGUIDE
http://video.fortinet.com
FORTINETBLOG
https://blog.fortinet.com
CUSTOMERSERVICE&SUPPORT
https://support.fortinet.com
http://cookbook.fortinet.com/how-to-work-with-fortinet-support/
FORTIGATECOOKBOOK
http://cookbook.fortinet.com
FORTINETTRAININGSERVICES
http://www.fortinet.com/training
FORTIGUARDCENTER
http://www.fortiguard.com
ENDUSER LICENSE AGREEMENT

http://www.fortinet.com/doc/legal/EULA.pdf
FEEDBACK
Email: techdocs@fortinet.com
Thursday, June 16, 2016

FortiGate-5144C - Chassis Guide
10-520-246510-20160616
TABLEOFCONTENTS
FortiGate-5144C Chassis
FortiGate-5144C front panel
FortiGate-5144C back panel
Chassis hardware information
Shipping components
Accessories
Supported Fortinet ATCA boards
Power requirements
Physical description of the FortiGate-5144C chassis
FortiGate-5144C shelf managers
Connecting to the Shelf manager and shelf manager Ethernet channels
Shelf manager Ethernet connections to chassis slots (and boards)
Changing the shelf manager switch configuration to prevent Ethernet loops
Radial IPMB bus topology
Using the shelf manager CLI
Shelf Manager fan and power control
Telco alarms
Air Filter
Cooling fans, cooling air flow, and minimum clearance
FortiGate-5144C hardware procedures

Mounting the FortiGate-5144C chassis
Air flow
Inserting FortiGate-5000 series boards and RTM modules
Installing FortiController or FortiSwitch boards
Power connection and configuration

FortiGate-5144C chassis power level requirements
Connecting the FortiGate-5144C chassis to DC power and ground
Crimping guidelines
Connecting FortiGate-5144C power feeds to DC power
Connecting the FortiGate-5144C chassis to ground
FortiGate-5053B power supply shelf and PSU-5000B power supplies
Power requirement guidelines
Connecting a FortiGate-5144C chassis to the FortiGate-5053B power supply shelf
Connecting the FortiGate-5053B power supply shelf to ground
6
6
7
8
9
9
9
11
11
12
13
14
14
16
17
17
17
19
19
21
21
22
22
23
24
24
25
26
27
28
29
31
31
33
Turning on FortiGate-5144C chassis power
Shelf Manager CLI

Connecting to the shelf manager CLI using the shelf manager console port
Connecting to the shelf manager CLI from an Ethernet network
Changing the shelf manager root account password
Resetting a lost shelf manager password
The shelf manager command line interface agent (CLIA)
Using CLIA interactive mode
IPMB addresses, logical and physical slot numbers, and FRU ids
Change IP address of the primary Shelf Manager
Display the shelf manager firmware version
List all FRUs in the chassis
List all sensors on a FRU
List only sensors that are outside of established thresholds
Display sensor data for a FRU
Display the FRU information for a FRU
Change the speed for a fan tray
Display the contents of the system event log (sel)
Clear the system event log (sel)
Changing the shelf manager IP address and default gateway
Sensor types
CLI command Reference
activate/deactivate
alarm
board
clia
exit/quit
fans
fru
fruinfo
getlanconfig
getthreshold/threshold
help
minfanlevel
sel
sensor
sensordata
setthreshold
shmstatus
showunhealthy
switchover
terminate
34
35
35
36
37
37
38
38
38
40
40
41
41
41
41
41
41
41
41
42
43
43
43
44
44
46
46
46
47
47
48
49
51
54
54
56
56
57
58
59
59
60
user
version
Generating SNMP traps for shelf manager system events
Example SNMP configuration
Testing the configuration
SNMP trap details
Removing and inserting a fan tray
Setting up SNMP polling for the shelf manager
Using the shelf manager system event log (SEL)
Before you begin
Chassis Design Background
Alarm LEDs
Reading the SEL
Clearing SEL logs
Example IPMC log output
Example FRU log output
Example sensor log output
Sample sections of SEL Output
Regulatory notices, cautions and warnings

Federal Communication Commission (FCC) USA
Industry Canada Equipment Standard for Digital Equipment (ICES) Canada
Voluntary Control Council for Interference (VCCI) Japan
Bureau of Standards Metrology and Inspection (BSMI) Taiwan
China
European Conformity (CE) - EU
Environmental specifications
Safety
60
62
62
62
66
66
68
68
69
69
69
70
70
71
71
73
74
86
88
88
88
88
88
89
89
89
90
You can install up to 14 FortiGate-5000 series boards in the 14 slots of the FortiGate-5144C ATCA chassis. The
FortiGate-5144C is a 14U 19-inch rackmount ATCA chassis that contains four redundant hot swappable DC
power entry Modules (PEMs). The PEMs connect to -48V DC power and supply 400 W to each chassis front slot.
The FortiGate-5144C chassis also includes four hot swappable cooling fan trays that provide 450W of cooling
power per slot and a front replaceable air filter with redundant pressure sensors. If all 14 slots containFortiGate5001D boards, the FortiGate-5144C chassis provides a total of 28 FortiGate 40-gigabit Ethernet interfaces and
28 FortiGate 10-gigabit interfaces.
Using the dual dual star 40-gigabit fabric and 1-gigabit base backplane interfaces the FortiGate-5144C chassis
can support a wide range of different configurations. For example:
l
l
l
l
Up to 14 FortiGate-5001D boards in chassis slots 1 to 14, each board operating as a separate FortiGate firewall.
One or two FortiController-5913C boards in chassis slots 1 and 2 in a dual-star configuration to support a 100 Gbps
session-aware load balancing cluster (SLBC) that distributes traffic to up to 12 FortiGate-5001D boards (called
workers)installed in chassis slots 3 to 14.
One or two FortiController-5903C boards to support a 40 Gbps SLBC with up to 12 FortiGate-5001D workers.
One or two FortiController-5913C or FortiController-5903C boards in chassis slots 1 and 2 can also be used for
FortiGate-5144C fabric and base backplane switching and to support FGCP clustering.
In the future, the FortiGate-5144C will support using four FortiController-5913C or FortiController-5903C boards in
chassis slots 1 to 4 in a dual dual star SLBC with up to ten FortiGate-5001D workers.
Two FortiController-5103B boards can be installed in slots 1 and 2 to create an SLBC for FortiGate-5001D (or older)
workers. FortiController-5103B boards can also be used for fabric and base backplane switching and to support
FGCP clustering.
Two FortiController-5902D boards can be installed in slots 1 and 2 to support content clustering to load balance
traffic to multiple FortiGate-5001D workers.
The FortiGate-5144C chassis requires -48V DC power. If DC power is not available you can install a FortiGate5053B power supply shelf and PSU-5000B power supplies (purchased separately).

The following illustration shows the front of a FortiGate-5144C chassis containing two FortiController-5903C
boards are installed in slots 1 and 2 and 12 FortiGate-5001D boards installed in slots 3 to 14.
These components are also visible on the front of the FortiGate-5144C chassis:
l
l
l
The primary and secondary Shelf Managers. Fortinet ships theFortiGate-5144C chassis with the primary shelf
manager installed. You can purchase and install a secondary shelf manager for redundancy. The shelf manager
provides power allocation, cooling, alarms, shelf status, displays alarms and includes a telco alarm interface.
The location of the front-replaceable air filter frame and retention screws.
The location of hot swappable fan trays 1 and 2 (can be accessed by opening the top cover at the front of the
chassis).
The Electrostatic discharge (ESD) socket, used for connecting an ESD wrist band when working with the chassis.

Fortinet Technologies Inc.
Do not operate the FortiGate-5144C chassis with open slots on the front or back panel. For optimum
cooling performance and safety, each chassis slot must contain either a FortiGate-5000 series board or
an air baffle slot filler. For the same reason, all cooling fan trays and the air filter should be installed while
the chassis is operating. As well all four PEMs (two primary and two redundant) must be installed in the
back of the chassis.
Example FortiGate-5144C front panel

Fan Tray 1 (front)
Fan Tray 2 (front)
FortiController-5903C
boards
slots 1 and 2
FortiGate-5001D
boards
slots 4, 6, 8, 10,
12, and 14
FortiGate-5001D
boards
slots 3, 5, 7, 9,
11, and 13
Slot
numbers
Air filter
frame
ESD
socket
Primary Shelf Manager
Secondary Shelf Manager

The FortiGate-5144C chassis back panel includes access to hot swappable fan trays 3 and 4.
The FortiGate-5144C chassis back panel includes four -48V to -60 VDC power entry modules (PEMs). Fortinet
ships the FortiGate-5144C chassis with all four installed. The PEMs are divided into two power feeds. PEMs 1
and 2 make up feed A. PEMs 3 and 4 make up power feed B. To provide power to the chassis you must connect
the PEMs in feed A. To provide redundant power you can also connect the PEMs in feed B.

Each PEM has two power feeds (feed 1 and feed 2) that include a -48V/-60 VDC terminal (labeled -) and a RTN
terminal (labeled +). To connect a PEM, both of its feeds must be connected to DC power.
The back panel also contains 14 RTM slots numbered to correspond to the front panel slots. When the chassis is
shipped, these slots are covered by RTM air baffle slot covers.
The back panel includes the FortiGate-5144C chassis ground connector that must be connected to ground.
Example FortiGate-5144C chassis back panel

Fan Tray 4 (back)
Fan Tray 3 (back)
RTM
slot numbers
RTM
air baffle
slot covers
PEM 4
PEM 3
Feed B
Chassis PEM 2
ground
connector
PEM 1
Feed A

This section introduces FortiGate-5144C hardware components and accessories including power requirements
and FortiGate-5000 series boards that can be installed in the chassis.

Shipping components
The FortiGate-5144C chassis ships pre-assembled with the following components:
l
The 14U FortiGate-5144C chassis
One shelf manager installed in the front of the chassis
Four Power Entry Modules (PEMs) installed in the back of the chassis
One air filter installed behind the air intake bezel at the bottom of the chassis
Four cooling fans installed in the fan bays at the top of the chassis
13 front panel air baffle slot covers installed in the front panel slots
14 RTM air baffle slot covers installed in the RTM slots
Eight 4-ft. power cables with 8 AWG stranded wires and double-hole lugs: Black for -48VDC and red for RTN. These
cables should only be used to connect the FortiGate-5144C PEMs to a FortiGate-5053B power convertor shelf if
purchased with your FortiGate-5144C chassis
Rack mount template (labeled metal strips showing how to line up cage nuts with rack holes when installing the
chassis)
5 spare nuts and washers for the PEM power studs
20 cage nuts with M6 screws
1 Philips No.2 screw driver
1 flat (4mm) screw driver
1 socket wrench (10mm)
Cage nut installation tool
Accessories
l
Shelf Manager
Shelf FRU data module

You can install the following FortiGate-5000 series boards in a FortiGate-5144C chassis to provide security
services. The FortiGate-5144C chassis has been added to the FortiGate-5000 product family to support recent
and future FortiGate-5000 series boards with high power requirements. This includes the following:
ATCA board
Interfaces
Function
FortiGate-5001B
Front Panel: 8 x 10 Gbps

Fabric: 10 Gbps
FortiOS network security
FortiGate-5001C


Fabric: 10 Gbps
Heat
Power Used
Dissipation
(WDC)*
(BTU/hr)*
Max: 225
Ave: 187
Max: 225
Ave: 187
768
768
Heat
Power Used
Dissipation
(WDC)*
(BTU/hr)*
ATCA board
Interfaces
Function
FortiGate-5101C

Fabric: 10 Gbps
FortiGate-5001D
FortiSwitch-5203B
FortiController-5902D
FortiSwitch-5003B
FortiController-5103B
Max: 236
Ave: 197
Front Panel: 2 x 40 Gbps,

2 x 10 Gbps, or
split into 8 x 10 Gbps
Fabric: 40 Gbps or 10Gbps
Max: 226
Ave: 189

Fabric: 10 Gbps
Content clustering with

FortiGate-5001Bs
Max: 250
Ave: 210
Front Panel: 4 x 40 Gbps or

Fabric: 40 Gbps or 10 Gbps
Content clustering with

FortiGate-5001Ds
Max: 270
Ave: 223

Fabric: 10 Gbps
Backplane switching,
FGCP HA, and extended
load balancing (ELBC)
Max: 180
Ave: 150
Front Panel: 8 x 10 Gbps, or

8 x 1 Gbps
Session-aware load
balancing Clustering
(SLBC) and FGCP HA
Front Panel: 4 x 40 Gbps or

Session-aware Load
Balancing Clustering
(SLBC) and FGCP HA

or split into 20 x 10 Gbps
Session-aware Load
Balancing Clustering
(SLBC) and FGCPHA
Max: 255
Ave: 213
Max: 400
Ave: 250
Max: 400
Ave: 280
805
774
853
919
614
754
1360
955
*Approximate values, see product datasheets for official values.

Any Fortinet ATCA board can be installed in the FortiGate-5144C chassis including the following older models:
10
FortiGate-5001A
FortiCarrier-5001A
FortiGate-5005FA2
FortiGate-5001FA2
FortiGate-5001
FortiGate RTM-XB2
FortiGate RTM-XD2
FortiSwitch-5003A

Power requirements
The FortiGate-5144C is rated to draw up to 153A. Each of the four PEM feeds/terminals draws up to 39A with 48VDC input and 450W/slot (400W front and 50W RTM). If no RTM slots are used, the total current will be up to
138.5A and with up to 35A per feed with -48VDC input. (the draw from the 4 feeds may not be even.)
The FortiGate-5144C chassis is designed to be installed in a Telecom or data center or similar location that has
available -48VDC power fed from a listed circuit breaker (also called battery power or main DC power). Fortinet
expects that mostFortiGate-5144C customers will be installing their chassis in a location that is already equipped
with a -48VDC power system fed from a listed circuit breaker that provides power to existing networking or
telecom equipment. The FortiGate-5144C chassis is designed to be connected directly to this DC power system.
If DC power is not available you can use one or more FortiGate-5053B power converter shelves equipped with
PSU-5000B power supplies to convert AC to DC to supply DC power to the FortiGate-5144C chassis from an AC
source.
Physical description of the FortiGate-5144C chassis

The FortiGate-5144C chassis is a 14U chassis that can be installed in a standard 19-inch rack. The following
table describes the physical characteristics of the FortiGate-5144C chassis.
Dimensions (H x W x D)
24.44 x 19.06 x 21.63 in. (62.10 x 48.40 x 54.96 cm)
Shipping weight and size completely

assembled with packaging
165 lbs (75 kg) (36 x 31 x 27in) (91 x 78 x 69cm)
Chassis weight completely assembled with

shelf manager and air baffles
(13 front and 14 RTM) 108 lbs (50 kg)
PEM DC terminal torque
No more than 3.8 Nm (33.62 lbf.in)
Operating environment
Temperature (long term): 32 to 104F (0 to 40C)

Temperature (short term): 23 to 131F (-5 to 55C)
Relative humidity: 20 to 90% (Non-condensing)
Power consumption
Min: 150W, Max: 1000 W (Power consumed by an empty

chassis with four fans, one shelf manager and four PEMs
installed and operating with the fans running at full speed.)
Heat Dissipation
150W to 1000W (512 BTU/hr and max 3412 BTU/hr)
Power input
4x to 2 PEMs (2 per PEM) with 2x redundant PEMs -48 Vdc/60Vdc, 153A/122A
Overcurrent Protection
Each PEM includes 4 power channels. Each channel includes

its own 30 A fuse.
Cooling Capacity
450 W per slot (Front slot 400 W and RTM slot 50 W)

11
Protected Earth Test
EN60950-1, test current 25 A, resistance <100 mOhm
Hipot Test
EN60950-1, 1000 V

The FortiGate-5144C chassis includes one or two redundant hot-swappable shelf managers, located in the
dedicated shelf manager slots at the bottom of the front panel. The primary shelf manager is installed on the left
the secondary shelf manager (if present) is installed on the right. The secondary shelf manager is optional.
FortiGate-5144C shelf manager front panel

Out of Service (Red),
Active (Green),
Retention
RS-232
Screw
and Hot Swap (Blue) LEDs Serial
Hot Swap
Button
Fan Tray
Reset
LEDs
Button
Ethernet
Interface
Backplane
Ethernet Link LEDs
Telco Alarm
Interface
Alarm Cut Off

Button
Retention
Screw
Critical Alarm (Red)

Major Alarm (Red)
Minor Alarm (Amber)
Power OK (Green)
Fortinet ships the FortiGate-5144C chassis with the primary shelf manager installed. You can purchase a
secondary shelf manager for redundancy.
If your chassis has two shelf managers, they support redundant operation with automatic switchover. If both shelf
managers are operating normally, one acts as the active shelf manager and the other as the backup. You can
tell which shelf manager is active by the state of the shelf manager front panel ACT(Active) LED. This LED is solid
green for the active shelf manager and flashing green for the backup shelf manager.
The active shelf manager performs all shelf manager functions. The shelf managers monitor each other and if the
active shelf manager stops communicating (for example because it has failed or is restarting) the backup shelf
manager becomes the active shelf manager. When the failed or restarting former active shelf manager comes
back up it will detect that the other shelf manager is active and become the backup shelf manager. Also, if one
shelf manager fails or is removed the other will operate independently as the active shelf manager and the
chassis will continue to function normally.
The active Shelf Manager communicates with Intelligent Platform Management Controllers (IPMCs) in the
chassis, each of which is responsible for local management of one or more Field Replaceable Units (FRUs), such
as boards, fan trays or power entry modules. Management communication within a chassis occurs primarily over
the Intelligent Platform Management Bus (IPMB), which is implemented using radial bus technology.
The active shelf manager controls chassis power allocation, monitors chassis operating parameters, monitors
and controls chassis cooling, and generates alarms if the chassis encounters problems. The active shelf manager
also displays alarms and includes a telco alarm interface. All FortiGate-5000 boards installed in the chassis
communicate with the active Shelf Manager through the IPMCs.
12

The shelf managers are hot swappable. You remove a shelf manager by pressing and holding the hot swap
button. The hot swap LED starts blinking blue. When the hot swap LED turns solid blue you can loosen both
retention screws and remove the shelf manager from the chassis.
Connecting to the Shelf manager and shelf manager Ethernet channels

Each shelf manager has an RS-232 serial port for connecting to the shelf manager console CLI. For information
about using this port, see Connecting to the shelf manager CLI using the shelf manager console port on page 35.
Each shelf manager also includes an Ethernet switch that connects the shelf manager front panel Ethernet
interface and the shelf manager base channel backplane Ethernet interface.The switch has two Ethernet
channels, ETH0 and ETH1:
l
ETH0 connects to the shelf manager Ethernet switch. This switch splits ETH0 into 2 independent channels. One
channel connects to both shelf manager front panel Ethernet interfaces and the other connects to the chassis
backplane base channel SH1.
ETH1 connects the Shelf manager directly to the chassis backplane base channel SH2.
Shelf Manager Ethernet switch and ETH0 and ETH1 architecture
The factory default shelf manager ETH0 port IP address is 192.168.0.2. You can change this IPaddress from the
shelf manager CLI. If your chassis has one shelf manager it will be installed in the primary shelf manager slot and
you can communicate with it by connecting the shelf manager's front panel Ethernet interface (ETH0) or to the B1
or B2 interface of a hub or switch board installed in chassis slot 1 or 2.
If your chassis has two shelf managers (one in the primary shelf manager slot and one in the secondary shelf
manager slot) either one of them can be the active shelf manager. From an external device you can only connect
to the active shelf manager. You should connect the front panel Ethernet interface (ETH0) of both shelf managers
to your network. That way, no matter which shelf manage is active you can still connect to the active shelf
manager using the shelf manager IP address (default 192.168.0.2). You can change the active Shelf Manager's
IP address from the shelf manager CLI. You can also connect to the active shelf manager from the B1 or B2
interface of a hub or switch board installed in chassis slot 1 or 2
You cannot connect to the backup shelf manager from an external device and you normally don't have to.
However, if you want to connect to the backup shelf manager you can log into the active shelf manager and then
Telnet to 192.168.1.3. This is the fixed internal IP address of the backup shelf manager and is normally only used
to allow communication between the active and backup shelf managers.

13
If a failover occurs the active shelf manager's IP address will be transferred to the new active shelf manager. The
new backup shelf manager will have the internal IP address of 192.168.1.3.
Shelf manager Ethernet connections to chassis slots (and boards)

The following diagram shows how the shelf managers connect to the chassis slots. Each shelf manager has two
connections to the chassis; one to each of the hub slots. ETH0 connects to SH1 of one chassis slot and ETH1
connects to SH2 of the other chassis slot.
Shelf Manager Ethernet cross-connections and connections to chassis slots
Changing the shelf manager switch configuration to prevent Ethernet loops

Because ETH0 connects to both shelf manager front panel Ethernet interface and to the chassis backplane base
channel via the shelf manager onboad Ethernet switch, it is possible to create an Ethernet loop if you connect the
14

shelf manager front panel interfaces and the B1 or B2 interface of a switch board in slot 1 or 2 to same network.
So connecting these interfaces to the same network is not recommended.
The most recent version of the shelf manager firmware (version 3.4.2.4G) is factory set to disable the connection
between the shelf manager switch and the backplane. This means that you must connect to the shelf manager
front panel Ethernet interface to manage the shelf manager. This also means that if you connect the shelf
manager front panel interfaces and the B1 or B2 backplane to the same network you will not get looping.
Firmware version 3.4.2.4G includes the ShMC_Eth_Switch_config command that can be used to change
the switch configuration. The command has four options:
l
l
get_EEPROM_config displays the current switch configuration.

set_default_EEPROM sets the switch to the default switch configuration. The default configuration enables
BOTH the front panel and the backplane interfaces.
disable_backplane_port disables the connection to the backplane. This option is factory set by Fortinet.
disable_front_panel_port disables the connection to the front panel Ethernet interface.
Entering these commands (except for get_EEPROM_config) reboots the shelf manager. If your chassis has
two shelf managers if you enter one of these commands to change the configuration you must enter the
command on each shelf manager. When you enter a command the active shelf manager reboots and while this is
happening the backup shelf manager becomes the active shelf manager.
FortiGate-5144Cshelf manager LEDs

LED
State
Description
FT1-4 OOS (Fan Tray 1-4 out

of service)
Off
Fan tray 1 to 4 is operating normally.
Red
Fan tray 1 to 4 is out of service.
Off
Normal Operation.
Red
Shelf manager software reboot or other failure.
Solid Green
Indicates that this is the active shelf manager.
Blinking Green
Indicates that this is the backup shelf manager.
Off
Normal operation.
Blinking Blue
The shelf manager is shutting down in preparation for being

removed from the chassis.
Blue
The shelf manager can be removed from the chassis.
Green
Backplane ethernet port 1 connected.
Blinking
Network activity on backplane ethernet port 1.
OOS (Out of Service)
ACT (Active)
H/S (Hot Swap)
LA2 (backplane port 1)

15
LED
State
Description
Amber
100 Mbit Link on backplane ethernet port 1.
Off
Green
Link on backplane ethernet port 0.
Blinking
Network activity on backplane ethernet port 0.
Amber
Off
Amber
100 Mbit link on Front Panel Ethernet Port 0.
Off
10 Mbit link on Front Panel Ethernet Port 0.
Green
Front Panel Ethernet Port 0 connected.
Blinking
Network activity on Front Panel Ethernet Port 0.
CRITICAL (Major Alarm)
Red
Critical alarm detected in chassis.
MAJOR (Major Alarm)
Red
Major alarm detected in chassis.
MINOR (Minor Alarm)
Amber
Minor alarm detected in chassis.
POWER OK
Green
Input power to the chassis is within limits.
LS2 (backplane port 1)
LA1 (backplane port 0)
LS1 (backplane port 0)
10/100 (Front panel ethernet

port)
L/A (Front panel ethernet

port)
FortiGate-5144Cshelf manager Buttons

Button
Description
H/S (Hot Swap)
Start the hot swap procedure. Push and the H/S LED blinks. Hold until H/S is solid
blue then remove shelf manager.
RST (Reset)
Reset the shelf manager.
CUTOFF (Telco Alarm

Cut Off)
Reset alarm contacts when alarm LEDs are blinking.

The FortiGate-5144C backplane includes a redundant dual star radial IPMB bus for higher reliability. Each shelf
manager provides 14 unique IPMB0-A and 14 unique IPMB0-B links to the 14 chassis slots. This means 28 IPMB
channels per shelf manager. The radial topology is shown below.
16

Using the shelf manager CLI

You can use the shelf manager command line interface (CLI) to communicate with the intelligent management
controllers of the chassis, with boards in the chassis, and with the shelf manager itself. The CLI is an IPMI-based
set of commands that can be accessed directly or through a higher-level management application or a script.
Using the CLI, you can access information about the current state of the chassis including current board
population, current sensor values, threshold settings, recent events, and overall chassis health.
To get started using the shelf manager CLI, see"Shelf Manager CLI" on page 35.
Shelf Manager fan and power control

The FortiGate-5144C shelf managers monitor the internal temperature of the chassis and adjust the operating
speed of the cooling fans as required.
When the chassis is first powered on all cooling fans run at full speed. Once the shelf manager is up and running,
the shelf manager reduces cooling fan speeds to maintain an optimum temperature in the chassis. If shelf
managers are not installed or not operating correctly the FortiGate-5144C chassis cooling fans always operate at
full speed.
Telco alarms
The Telco Alarm Interface is a standard DB-15 male Telco Form-c connector. The external dry relay Telco alarm
interface (48VDC) provides Telco form-c relay connections for minor, major and critical power faults. The cable
required to connect to the alarm interface is not supplied by Fortinet. To monitor alarms you should connect to
the telco alarm interface of the active shelf alarm panel, which by default is the one on the left.
The Telco alarm interface relay circuits are capable of carrying 60 VDC or 1 A with a max. rating of 30 VA. The
shelf alarm panel accepts timed pulse inputs for clearing minor and major alarm states. Reset is accomplished by
asserting a voltage differential from 3.3 V to 48 V for between 200 and 300 ms. The acceptance voltage range is
from 0 to 48 VDC continuous (handles up to 60 VDC at a 50% duty cycle). The current drawn by a reset input does
not exceed 12 mA.

17
The alarm LED reset button activates the alarm cutoff (ACO) state for major, minor, and user-defined alarms.
You cannot reset critical alarms with the alarm LED reset button.
When the ACO state is activated, active alarm LEDs blink and all of the alarm relays are deactivated. The alarm
reset button activates the ACO state but does not clear the alarm completely.
The telco alarm connector (DB-15 male)
Telco alarm connector pin assignment
18
Pin
Descrption
MinorReset+
MinorReset-
MajorReset+
MajorReset-
CriticalAlarm - NO
Critical Alarm NC
Critical Alarm COM
Minor Alarm NO
Minor Alarm NCT
10
Minor Alarm COM
11
Major Alarm NO
12
Major Alarm NC
13
Major Alarm COM
14
Power NO
15
Power COM

Air Filter
Air Filter
The FortiGate-5144C chassis includes a front replaceable air filter that removes dust from intake air and provides
static pressure to achieve uniform airflow. The filter must be installed for the chassis to operate normally. If the
air filter is not locked into place the air filter presence sensors cause an alarm.
The air filter should be inspected regularly. If dirty or damaged, the filter should be disposed of and replaced. The
air filter can be fragile and should be handled carefully.
To service the air filter you must loosen two the air filter frame retention screws at the bottom of the front of the
chassis. Tilt down the air filter frame and remove the air filter material.
Care should be taken when inserting an new air filter to prevent damage to the sensors. To insert a new filter,
slide it into the frame using the guides at each side of frame until the filter contacts springs at the back of the
chassis. Then tilt the frame up and tighten the retention screws.

The FortiGate-5144C chassis contains four hot-swappable cooling fans (fan 1 to fan 4) installed in the fan cabinet
at the top of the chassis. Two fans are access able from the front of the chassis and two from the back.
Fan tray locations (top view of chassis)
Fan 3
Fan 4
Fan 1
Fan 2
Right
Left
Back of Chassis
Front of Chassis
Front and back fan trays
!
!
Front Fan Tray

(Fan Trays 1 and 2)

Back Fan Tray

(Fan Trays 3 and 4)
19
To service the front fan trays (fan trays 1 and 2), open the front fan cabinet. The back fan trays (fan trays 3 and 4),
are accessible from the back of the chassis. The fan trays are hot swappable. You do not need to press a hot
swap switch to remove a fan. Just pull a fan out of the chassis and replace it. The shelf manager regulates the fan
speed by adjusting the DC voltage supplied to the fan trays.
FortiGate-5144C fan tray LEDs

LED
Description
H/S (Hot Swap)
Normally off. Blinking blue indicates that the fan is starting up.
Normally off. Blinking red indicates the fan is out of service and should be replaced.
ACT (Active)
Normally solid green. Indicates the fan is operating normally.
When installing the chassis, make sure there is enough clearance for effective cooling air flow. The following
diagram shows the cooling air flow through the chassis and the locations of the air filter and cooling fans. Make
sure the cooling air intake and warm air exhaust openings are not blocked by cables or rack construction because
this could result in cooling performance reduction and possible overheating and component damage.
Cooling air flow, fan locations, and required minimum air flow clearance
40 mm
Warm air
Exhaust
Fan
Fan
100 mm
60 mm
Back
Front
Cool air
Intake
Air Filter
600 mm
600 mm
20


This chapter describes how to mount the FortiGate-5144C chassis and how to install FortiGate-5000 boards in
the chassis.
Mount the FortiGate chassis in a rack before installing the FortiGate-5000 boards.
The FortiGate-5144C chassis must be mounted in a standard 19-inch rack. The chassis can be mounted in a 4post rack using the rack mount brackets in the standard front mounting position as they are installed the chassis
when it is shipped. If you choose to mount the chassis in a 2-post rack you need to move the rack mount brackets
to the mid mount position.
81.56 mm
Rack mount bracket standard

front mount position
181.56 mm
Rack mount bracket

mid-mount position
The chassis requires 14U of vertical space in the rack. You can use the rack mount template included with the
chassis to line up cage nuts with mounting holes before mounting the chassis.
If you install the FortiGate-5144C chassis in a closed or multi-unit rack assembly, the operating ambient
temperature of the rack environment may be greater than room ambient temperature. Make sure the operating
ambient temperature does not exceed the manufacturer's maximum rated ambient temperature.

21
The FortiGate-5144C chassis should not be operated as a free-standing appliance.
It is recommended that you mount the FortiGate-5144C chassis near the bottom of the rack to avoid making the
rack top-heavy and potentially falling over. If you are going to mount the chassis higher make sure the rack is well
anchored. Since the chassis is over 100 lbs use a lift to raise the chassis into position before mounting it.
Air flow
For rack installation, make sure that the amount of air flow required for safe operation of the FortiGate-5144C
chassis is not compromised. Make sure that the chassis ventilation openings at the top rear and the bottom front
are not blocked by cables or other components. The recommended minimum clearance at the front of the chassis
is 100 mm and the recommended clearance from the rear of the chassis is 60 mm. This results in a total footprint
of 600 mm from front to back. See Cooling fans, cooling air flow, and minimum clearance on page 19 for more
details.

You can insert FortiGate and FortiSwitch-5000 series boards into the front of the FortiGate-5144C chassis and
RTM modules into the back of the chassis. Arrange the boards and modules in slots as required for your
configuration. FortiGate-5000 series boards can be installed in any FortiGate-5144C front panel slots.
FortiController and FortiSwitch boards can only be installed in switch slots 1 and 2. FortiController boards can
also be installed in slots 3 and 4 for a dual dual star configuration. FortiGate-5000 series RTM modules can be
installed in any FortiGate-5144C RTM slot.
All FortiGate-5144C chassis are shipped with air baffle filler panels/cards on all but one front slot that include a
warning message to read the FortiGate-5000 documentation before installing your product. The temporary slot
fillers must be removed and all slots filled; either with FortiGate-5000 series boards or with air baffle slot fillers.
Air baffle slot fillers are similar to blank FortiGate-5000 boards and are required for proper cooling air flow.
All FortiGate-5000 series boards must be protected from static discharge and physical shock. Only
handle or work with these boards at a static-free workstation. Always wear a grounded electrostatic
discharge (ESD) preventive wrist strap when handling these boards.
Do not operate the FortiGate-5144C chassis with open slots on the front panel or rear panel. For
optimum cooling performance and safety, front panel slots must contain a FortiGate-5000 series module
or an air baffle slot filler and rear panel slots must either be covered or must contain a rear transition
module or slot filler.
To avoid damaging components, you should install RTM modules (such as the FortiGate-RTM-XD2
module) first before you install the corresponding FortiGate front panel board. If you have already
installed a FortiGate board, you should remove it before installing the RTM module.
To install FortiGate-5000 boards or RTM modules, see the documentation supplied with the board or module.
22


FortiController and FortiSwitch boards are always installed in chassis in slots 1 or 2 to provide fabric and base
backplane load balancing or switching. The dual dual-star 40-Gigabit switch fabric backplane is most often used
for data communication between boards in the chassis. Base backplane switching is usually used for sync and HA
heartbeat communication boards in the.
To install FortiController or FortiSwitch boards, see the documentation supplied with the board.

23

The FortiGate-5144C chassis is designed to be installed in a Telecom data center or similar location that has
available -48VDC power fed from a listed circuit breaker (also called battery power or main DC power). Fortinet
expects that most FortiGate-5144C customers will be installing their chassis in a location that is already equipped
with a -48VDC power system fed from a listed circuit breaker that provides power to existing networking or
Telecom equipment. The FortiGate-5144C chassis is designed to be connected directly to this DC power system.
The FortiGate-5144C is rated at 48VDC 156A with 4x feeds up to 39A/feed. For each feed, the provision can be
with one main breaker rated for 156A or more or four breakers rated at 40A. With a 20% margin, the main breaker
should be rated for 187A. The four breakers for each feed should be rated for at least 46.8A. For full redundancy,
a second set of identical breakers are needed for the second feed.
The current rating is reduced to 138A if no RTM slots are used.
If DC power is not available you can use the FortiGate-5053B power converter shelf to convert AC to DC to supply
DC power to the FortiGate-5144C chassis.
Fortinet supplies eight 4-ft. power cables with 8 AWG stranded wires and double-hole lugs: Black for -48VDC and
red for RTN. These cables should only be used to connect the FortiGate-5144C PEMs to a FortiGate-5053B
power convertor shelf if purchased with your FortiGate-5144C chassis. The double-hole lugs to be connected to
the FortiGate-5144C PEMs should be covered with the supplied clear PEM terminal protection covers before
energizing the power system. If the power cable length needs to be significantly longer than 4 ft., higher gauge
wires should be considered.
If you are connecting your chassis to a local DC power source, use cables that meet your local wiring codes. To
connect the wires to the FortiGate-5144C PEMs use 5/8-inch double-hole lugs with suitable for the DC cables
used, such as Thomas & Betts PN 54850BE.
Green 8 AWG wires are recommended for ground connections (not supplied with the chassis).

This section provides some basic guidelines for determining the power requirements of your FortiGate-5144C
chassis. Actual requirements may vary depending on your installation requirements. Contact Fortinet Support if
you need more information.
The base FortiGate-5144C chassis (empty, with four fan trays, one shelf manager, and four PEMs installed and
operating with the fans running at full speed) requires a maximum of 1000 W. Each chassis slot can supply up to
400 W. You can use these numbers to estimate the power requirement for a chassis configuration.
24

Example: power for a chassis with 5 boards

For example, the power requirement for a FortiGate-5144C chassis with FortiGate-5000 series boards in five
slots would be:
1000W + (400W * 5) = 3000W
Example: power for a fully-loaded chassis (14 boards)

The power requirement for a fully loaded FortiGate-5144C chassis with boards in all 14 slots would be:
1000W + (400W * 14) = 6600W

The chassis includes two redundant power feeds (Feed A and Feed B) which provide power to all chassis slots
and components. Each power feed includes two power entry modules (PEMs).
To power the chassis you need to connect the PEMs in Feed A to a -48VDC/-60VDC power source. For redundant
power you can also connect the PEMs in Feed B to a -48VDC/-60VDC power source.
Each PEM includes a Reverse Voltage LED that lights if you have reversed the polarity when connecting
power.
FortiGate-5144C power Feeds, PEMs, and ground connector
PEM 4
PEM 3
Feed B
Chassis PEM 2
ground
connector
PEM 1
Feed A
Each PEM includes two input feeds (feed 1 and feed 2). Each of these input feeds includes two -48VDC/-60 VDC
connectors (labeled -) and two return connectors (labeled +). Each input feed is a separate power channel that
includes its own 30A fuse. Each power channel provides power to a different set of chassis components. All
terminals of each input feed should be connected to a single -48VDC power source with a listed circuit breaker.

25
Power segmentation for Feed A and Feed B

PEM
Input Feed
Channel
Physical Component
Logical Slot
Slot 1, Slot 2
Slot 13, Slot 11
Slot 3, Slot 4
Slot 9, Slot 7
Slot 5, Slot 6
Slot 5, Slot 3
Slot 7, Fan Tray 1, Fan Tray 2, Shelf Manager 1
Slot 1
Slot 8, Slot 9
Slot 2, Slot 4
Slot 10, Slot 11
Slot 6, Slot 8
Slot 13, Slot 14
Slot 12, Slot 14
Slot 12, Fan Tray 3, Fan Tray 4, Shelf Manager 2
Slot 10
1
PEM 1/3
2
1
PEM 2/4
2
To connect the FortiGate-5144C PEMs to DC power you must use power connectors and wires that comply with
the local electrical wiring code and the requirements of the facility in which you are installing the FortiGate-5144C
chassis.
The PEMs are hot-swappable, which means if both power feeds are connected you can remove and replace a
defective PEM while the chassis is operating. It is not necessary to notify the software or reset the system power
to remove a PEM. You can add, remove, or replace a second PEM without interrupting FortiGate-5144C
operation.
Crimping guidelines
To connect the PEMs to data center power you should use 8 AWG or larger wires depending on the wire length
and the power requirements of your chassis. The ends of these wires must be fitted with 5/8-inch double-hole
lugs suitable the DC cables used, such as Thomas & Betts PN 54850BE. Use the following information to crimp
and prepare these wires.
Do not crimp energized wires.
Follow these crimping guidelines:

l
l
26
Strip the insulation from cable. Be careful not to nick cable strands which may later result in stands breaking
Cable end should be clean: wire brush or clean with emery cloth if necessary. Insert cable into connector until it
stops. The insertion length must approximate the stripped length of cable
Insert connector in die and compress between the markings beginning near the tongue of the connector. Using the
wrong installing die may result in a defective connection.
After crimping, remove all sharp edges, flash or burrs.


The following procedure describes how to connect the PEMs in a FortiGate-5144C power feed to DC power.
Repeat this procedure to connect each power feed.
Eight DC cables are required for the PEMs in a feed (and all terminals of each polarity should be used).
The supplied clear terminal protection covers must be installed on all PEMs before they are energized.
Connecting Feed A PEM1 and PEM2 or Feed B PEM3 and PEM4 to DC power
DC Power
Source
-48VDC
connector
Terminal
Cover
Reverse
Active, OOS,
and H/S LEDs Voltage LEDs
Fuse LEDs
(channels
5 to 8)
RTN
connector
Terminal
Cover
FortiGate-5144C PEM LEDs

LED
State
Description
ACTIVE
Solid Green
Normal operation.
Off
Normal Operation.
Solid Red
Out of Service.
Off
Normal operation.
Blinking Blue
The PEM is shutting down in preparation for being removed

from the chassis.
Blue
The PEM can be removed from the chassis.
Off
Normal operation
Solid Red
Feed input voltage polarity reversed.
H/S (Hot Swap)
REV. VOLT FEED 1 REV. VOLT

FEED 2 (Reverse Voltage for feed
1 and feed 2)

27
LED
State
Description
FUSE MONITOR CH1 to CH8

(Fuses for power channels 1 to 8)
Off
Normal operation.
Red
One or both fuses blown or absent.
You need the following equipment to connect the primary FortiGate-5144C PEMs to DC power:
l
l
An electrostatic discharge (ESD) preventive wrist strap with connection cord.

Four black 8 AWG stranded wires labeled -48V with attached 5/8-inch listed closed loop double-hole lugs suitable
for the DC cables used, such as Thomas & Betts PN 54850BE.
Four red 8 AWG stranded wires labeled RTN with attached 5/8-inch listed closed loop double-hole lugs suitable for
he DC cables used, such as Thomas & Betts PN 54850BE.
To connect the PEMs in a power feed to DC power

1. Attach the ESD wrist strap to your wrist and to an ESD socket or to a bare metal surface on the chassis or frame.
2. Make sure that the PEMs and power cords are not energized.
3. Remove the PEM terminal covers.
4. Remove the first set of nuts and lock washers from the connectors on each PEM.
5. Connect black -48V power wires from the DC power source to the connectors on the PEMs labeled - using doublehole lugs. Install each double-hole lug vertically. Do not apply torque of more than 3.8 Nm (33.62 lbf.in).
6. Connect red RTN power wires from your locations RTN terminal to the connectors on the PEMs labeled + using
double-hole lugs. Install each double-hole lug vertically. Do not apply torque of more than 3.8 Nm (33.62 lbf.in).
7. Install previously removed nuts and washers to secure the connectors.
8. Make sure the power wires are secured using tie wraps if required.
9. If required, label the black wires -48V.
10. If required, label the red wires RTN.
11. Install the PEM terminal covers.

The FortiGate-5144C chassis includes a ground terminal on the rear the bottom of the FortiGate-5144C back
panel. The ground terminal provides two connectors to be used with a double-holed lug such as Thomas & Betts
PN 54850BE. This connector must be connected to a local ground connection.
You need the following equipment to connect the FortiGate-5144C chassis to ground:
l
l
28

One green 8 AWG stranded wire with listed closed loop double-hole lug suitable for minimum 8 AWG copper wire,
such as Thomas & Betts PN 54850BE.

Connecting a FortiGate-5144C chassis to ground
Chassis
Ground
Connector
(green)
Data Center
ground
connector
(Central office
ground system)
To connect the FortiGate-5144C chassis to ground

2. Make sure that the chassis and ground wire are not energized.
3. Connect the green ground wire from the local ground to the ground connector on the FortiGate-5144C chassis.
4. Secure the ground wire to the chassis.
5. Optionally label the wire GND.

If DC power is not available at your location, you can use the FortiGate-5053B 1U 19-inch rack mount power
supply shelf with PSU-5000B hot swappable power supplies to convert AC power to DC power. These
components are not supplied with the FortiGate-5144C chassis and must be purchased separately.
FortiGate-5053B power supply shelf with four PSU-5000B power supplies
Edge
Controller
PSU-5000B hot swappable

Power Supplies (4)
In addition to adding multiple FortiGate-5053B power supply shelves for additional power, you can also pair a
FortiGate-5053B with a FortiGate-5053B-LC power supply shelf. The LC unit can also include up to four PSU but
does not include an edge controller. Instead, both FortiGate-5053B power supply shelves are managed by one
edge controller.

29
FortiGate-5053B and 5053B-LC power supply shelves

Power Supplies (4)
Edge
Controller
FortiGate-5053B
power supply
shelf
FortiGate-5053B-LC
power supply
shelf

Power Supplies (4)
You can install multiple power supply shelves and multiple power supplies to provide additional power and for
redundancy.
For more information about the FortiGate-5053B power supply shelf see the FortiGate-5053B Power Supply
Shelf Guide.
As already stated, Fortinet supplies eight 4-ft. power cables with 8 AWG stranded wires and double-hole lugs:
Black for -48VDC and red for RTN. These cables should be used to connect the FortiGate-5144C PEMs to a
FortiGate-5053B power supply shelf. If the power cable length needs to be significantly longer than 4 ft., higher
gauge wires should be used.
The FortiGate-5053B power supply shelf can include up to four PSU-5000B power supplies. The power supply
shelf can be connected to high line AC input (186-240VAC) or low line AC input (100-185VAC).
l
When connected to high-line AC input, a single power supply can provide 2725W of DC power and a fully populated
FortiGate-5053B power supply shelf can provide up to 10.9KW of DC power and 8175W of DC power with 3+1
redundancy with an output voltage of 54 VDC.
When connected to low-line AC input a single power supply can provide 1200W of DC power and a fully populated
FortiGate-5053B power supply shelf can provide up to 4800W of DC power and 3600W of DC power with 3+1
redundancy with an output voltage of 54 VDC.
When connected to low-line AC power a minimum of 6 PSU-5000B power supplies are required to power a fully
loaded FortiGate-5144C chassis (that can require up to 6600W). Fortinet recommends the following low-line AC
power configurations to provide power to a FortiGate-5144C chassis:
l
30
Two FortiGate-5053B power supply shelves with a total of 8 PSU-5000Bs. One power supply shelf connects to
chassis power Feed A and the other to Feed B providing 6+2 redundancy.
A FortiGate-5053B and a FortiGate-5053B-L with a total of 8 PSU-5000Bs. One power supply shelf connects to
chassis Feed A and the other to Feed B providing 6+2 redundancy.
Two sets of a FortiGate-5053B and a FortiGate-5053B-L power supply shelves with a total 16 PSU-5000Bs powered
from 2 different AC power feeds and connected to both Feed A and Feed B to provide added redundancy.

Power requirement guidelines

This section provides some basic guidelines for determining the power requirements of your FortiGate-5144C
chassis. Using these power requirements you can decide how many power supplies and power supply shelves you
need. Actual requirements may vary depending on your installation requirements. Contact Fortinet Support if you
need more information.
The base FortiGate-5144C chassis (empty, with four fans, one shelf manager, two shelf alarm modules and two
PEMs installed and operating with the fans running at full speed) requires a maximum of 1000 W. Each chassis
slot can supply up to 400 W. You can use these numbers to estimate the power requirement for a chassis
configuration.
Example: power for a chassis with 5 boards

For example, the power requirement for a FortiGate-5144C chassis with FortiGate-5000 series boards in five
slots would be:
1000W + (400W * 5) = 3000W
If you are using high-line AC power, one PSU-5000B produces 2725W. Powering a chassis with 5 boards would
require one FortiGate-5053B power supply shelf connected to power feed A (PEM 1 and PEM 2). The power
supply shelf would include two PSU-5000B units and produce a total of 5450W. You can add one more power
supply for redundancy. If you want completely redundant power for the chassis you can connect a second
FortiGate-5053B unit to power feed B (PEM 3 and PEM 4) and include two or three power supplies.
If you are using low-line AC power, one PSU-5000B produces 1200W. Powering a chassis with 5 boards would
supply shelf would include three PSU-5000B units and produce a total of 8175W. You can add a fourth power
FortiGate-5053B unit to power feed B (PEM 3 and PEM 4) and include three or four power supplies.
Example: power for a fully-loaded chassis (14 boards)

The power requirement for a fully loaded FortiGate-5144C chassis with boards in all 14 slots would be:
1000W + (400W * 14) = 6600W
If you are using high-line AC power, one PSU-5000B produces 2725W. Powering a chassis with 14 boards would
supply shelf would include three PSU-5000B units and produce a total of 8175W. You can add a fourth power
FortiGate-5053B unit to power feed B (PEM 3 and PEM 4) and include three or four power supplies.
A FortiGate-5053B with four low-line AC power PSU-5000Bs would produce a total of 4800W which is not enough
power for a fully-loaded chassis. As described above you would require at least two low-line power supply shelves
and 8 power supplies.
Connecting a FortiGate-5144C chassis to the FortiGate-5053B power supply shelf

To use a FortiGate-5053B power supply shelf with the FortiGate-5144C chassis you need to make DC power
connections between the primary FortiGate-5144C PEMs and the FortiGate-5053B power supply shelf. You also
need to the connect the FortiGate-5144C chassis and the FortiGate-5053B power supply shelf to ground.

31
Connecting a FortiGate-5144C chassis to a single FortiGate-5053B power supply shelf

The following procedure describes how to connect power to the primary FortiGate-5144C PEMs using the
FortiGate-5053B power supply shelf. You can repeat this procedure to connect the backup PEMs to a second
FortiGate-5053B power supply shelf.
You need the following equipment:
l
l

Four black 8 AWG stranded wires labeled -48V with attached Listed closed loop double-hole lugs suitable for
minimum 8 AWG copper wire (supplied by Fortinet), such as Thomas & Betts PN 54850BE.
Four red 8 AWG stranded wires labeled RTN with attached Listed closed loop double-hole lugs suitable for
minimum 8 AWG copper wire, such as Thomas & Betts PN 54850BE.
A FortiGate-5053B power supply shelf containing the required number of PSU-5000B power supplies and mounted
in a rack near the FortiGate-5144C chassis.
To connect the FortiGate-5144C chassis to a FortiGate-5053B power supply shelf
The FortiGate-5053B power converter shelf should not be connected to AC power until specified in the
following procedure.
2. Make sure that the PEMs, power supply shelf and DC power cable are not energized.
3. Remove the first set of nuts and lock washers from both connectors on the back of the FortiGate-5053B power
supply shelf.
4. Connect four black -48V power wires to the connectors labeled NEG on the back of the FortiGate-5053B power
supply shelf using the double-hole lug. Install each double-hole lug either horizontally or vertically. Do not apply
torque of more than 3.8 Nm (33.62 lbf.in).
5. Connect four red RTN power wires to the connectors labeled POS on the back of the FortiGate-5053B power
supply shelf using the double-hole lug. Install each double-hole lug either horizontally or vertically. Do not apply
torque of more than 3.8 Nm (33.62 lbf.in).
7. Cover the connectors with the connector covers on the back of the power supply shelf.
8. Select remove the first set of nuts and lock washers from the primary PEM connectors.
9. Connect the four black -48V power wires from the power supply shelf to the connectors on the primary FortiGate5144C PEMs labeled - using the double-hole lug. Install each double-hole lug vertically. Do not apply torque of
more than 3.8 Nm (33.62 lbf.in).
10. Connect four red RTN power wires from the power supply shelf to the connectors on the primary FortiGate-5144C
PEMs labeled + using the double-hole lug. Install each double-hole lug vertically. Do not apply torque of more than
3.8 Nm (33.62 lbf.in).
32

Eight DC cables are required for the primary PEMs (and all terminals of each polarity should be used).
The lugs that connect to the FortiGate-5144C PEMs connect to one wire. The lugs that connect to the
FortiGate-5053B power supply shelf connect to 2 wires allowing you to connect two wires to each
FortiGate-5053B connector. If for any reason any of the PEM terminals are not used the unused
terminals need to be covered with insulated material (or wrapped with electrical tape) as the exposed
terminals are a shock hazard.
12. Make sure the power wires are secured to the chassis using tie wraps if required.
13. If required, label the black wires -48V.
14. If required, label the red wires RTN.
15. Install the PEM terminal covers.
16. Connect the FortiGate-5053B power supply shelf to AC power.
Only connect the power supplies that are installed in the FortiGate-5053B to AC power. For example, if your
FortiGate-5053 includes two power supplies, the power supplies will be installed in slots 1 and 2. In this case you
should only connect AC connectors 1 and 2 to AC power. If your power supply shelf contains four power supplies,
connect all four AC in connectors to AC power.
Connecting Feed A PEM1 and PEM2 or Feed B PEM3 and PEM4 a FortiGate-5053B
Red + to
FortiGate-5053B
POS
Black -48 VDC to
FortiGate-5053B
NEG
Terminal
Cover
Connecting the FortiGate-5053B power supply shelf to ground

The FortiGate-5053B power supply shelf includes a ground terminal on the center of the back panel. The ground
terminal provides two connectors to be used with a double-holed lug such as Thomas & Betts PN 54850BE. This
connector must be connected to ground.
You need the following equipment to connect the FortiGate-5053B unit to ground:
l
l

One green 8 AWG stranded wire with listed closed loop double-hole lug suitable for minimum 8 AWG copper wire,
such as Thomas & Betts PN 54850BE.

33
Connecting a FortiGate-5053B power supply shelf to ground
Shelf ground
connector
Data Center
ground
connector
(Central office
ground system)
To connect the FortiGate-5053B power supply shelf to ground

2. Make sure that the shelf and ground wire are not energized.
3. Connect the green ground wire from the site ground terminal to the ground connector on the power supply shelf.
4. Secure the ground wire as required.
5. Optionally label the wire GND.

If you are using a power supply shelf, connect the power supply shelf to AC power and verify that it is operating
correctly.
If you are using local DC power, turn on the power to the chassis according to the requirements of your local DC
power system.
Once the FortiGate-5144C chassis is connected to DC power the chassis powers up. If the chassis is operating
correctly, the LEDs on the connected PEM(s) and fans should be lit. As well, the LEDs on the FortiGate-5144C
shelf manager and shelf alarm modules should be lit.
When the chassis first starts up you should also hear the cooling fans operating.
In addition, if any FortiGate-5000 series boards have been installed in the chassis they should power on and their
front panel LEDs should indicate that they are starting up and operating normally.
34

Shelf Manager CLI
Shelf Manager CLI

You can use the shelf manager command line interface (CLI) to communicate with the intelligent management
controllers of the chassis, with boards in the chassis, and with the shelf manager itself. The CLI is an IPMI-based
set of commands that can be accessed directly or through a higher-level management application or a script.
Using the CLI, you can access information about the current state of the chassis including current board
population, current sensor values, threshold settings, recent events, and overall chassis health.
The Shelf Manager communicates inside the chassis with Intelligent Platform Management Controllers (IPMCs),
each of which is responsible for local management of one or more Field Replaceable Units (FRUs), such as
boards, fan trays or power entry modules. Management communication within a chassis occurs primarily over the
Intelligent Platform Management Bus (IPMB), which is implemented using radial bus technology.
The shelf manager CLI can be used to communicate with the intelligent management controllers of the shelf,
with boards, and with the Shelf Manager itself. The CLI is an IPMI-based set of commands. The Intelligent
Platform Management Interface specification (IPMI spec) can be found at
http://www.intel.com/design/servers/ipmi/spec.htm.
PICMG 3.0 specifications (developed by the PCI Industrial Computer Manufacturers Group) define extensions to
the IPMI specification. These specifications can be ordered from http://www.picmg.org.
This chapter contains the following sections:
l
Connecting to the shelf manager CLI using a serial port and setting up passwords
Basic shelf manager CLI Commands
Sensor types
Shelf manager CLI commands
You can connect to the shelf manager CLI by connecting the console cable supplied with your chassis to a
management PC console port and to the shelf manager serial port on the shelf manager front panel.

35
Shelf Manager CLI
Connecting to a shelf manager serial port

FortiGate-5144C
Shelf Manager
Fortinet
RJ-45 RS232
to 9-pin
Console
Cable
To PC
RS-232
Console
Port
To connect to the shelf manager CLI

1. Connect a standard CAT5 RJ-45 Ethernet cable to the shelf manager Console port.
2. Connect the console cable supplied with your chassis to your PC or other device RS-232 console port.
3. Start a terminal emulation program (for example, HyperTerminal) on the management computer. Use these
settings:
Baud Rate (bps) 9600 or 115200
Data bits 8
Parity None
Stop bits 1
Flow Control None
4. Press enter to connect to the CLI.
5. At the login prompt enter root as the user name with no password.
For security reasons, it is strongly recommended that you add a password for the root account.
6. When you log into the shelf manager CLI you are logging into a Linux shell as root. You can begin entering
commands at the # prompt.

You can connect to the shelf manager CLI by connecting the shelf manager front panel front panel Ethernet
interface to a network. If your chassis has two shelf managers, connect both of them to the same Ethernet
network. Connect to the CLI by using Telnet to connect to the shelf manager IP address. The default shelf
manager IP address is 192.168.0.2. If your chassis has two shelf managers, the active shelf manager is the only
one that you can connect to. At the login prompt enter root as the user name with no password. For security
reasons, it is strongly recommended that you add a password for the root account. When you log into the shelf
manager CLI you are logging into a Linux shell as root. You can begin entering commands at the # prompt.
You can also connect to the shelf manager CLI through the chassis backplane but this
requires a shelf manager configuration change (see Changing the shelf manager
switch configuration to prevent Ethernet loops on page 14).
36

Shelf Manager CLI

Use the following procedure to change the shelf manager root account password.
To add or change the shelf manager root account password

For enhanced security you should use the following steps to add a password for the shelf manager root account.
1. At the # prompt enter the following Linux command to add a password for the root account:
# passwd
2. Enter and confirm a new password for the root account.
The password should be between 5 and 8 characters long and should include a combination of upper and lower
case letters and numbers.
You can use the passwd command to change the root account password at any time.
After setting up your own accounts, you can also use the passwd command to remove the root account. Enter
the passwd command and when prompted for a password, press enter to add a blank password.
Resetting a lost shelf manager password

In the shelf manager root account password becomes lost you can reset the password to its factory default using
the password_reset U-Boot variable. Setting this variable to y and rebooting the shelf manager, removes the
password and you can add a new one.
1. Connect to the shelf manager CLI using the shelf manger console port.
2. Cycle the Shelf Manager power.
You can do this by partially removing and then re-inserting the shelf manager to cycle its power or by cycling the
power to the chassis.
3. Interrupt the boot when the following line or a similar line appears on the console:
Hit any key to stop autoboot: 0
A prompt similar to shMM # or shmm500 appears.
4. Enter the following commands to set the reset_password U-Boot variable and save the change:
shmm500 setenv password_reset y
shmm500 saveenv
5. Enter one of the following commands to reboot the shelf manager:
shmm500 boot
or
shMM # run bootcmd
Output similar to the following appears as the shelf manager reboots:
/etc/rc: hostname demo
/etc/rc: Restoring password file to factory default
6. Enter the following command to add a new password for the root account:
# passwd

37
Shelf Manager CLI

Once you have logged into the shelf manager CLI you use the Command Line Interface Agent (CLIA) to enter
shelf manager commands. Usually you do this from the Linux command line by entering clia followed by the
required CLIA command verb and parameters. The CLIA executable connects to the main Shelf Manager
software process, passes the command information to it and retrieves the results.
For example, you can enter the following command to list the most commonly used CLIA commands:
clia help
You can also the help command to get more information about specific CLIA commands. For example, use the
following command display help for the shelf pwrreorder command:
clia help shelf pwrreorder
Pigeon Point Shelf Manager Command Line Interpreter
Change the order of FRU Activation and Power Descriptors
instead of <addr> <fru_id> user may use:
board <N>
shm <N>
power_supply <N> (valid in 2.x systems only)
fan_tray <N>
PwrReorder <addr1> <fru_id1> before/after <addr2> <fru_id2>
Using CLIA interactive mode

You can also enter clia without parameters to enter interactive mode. In the interactive mode, the shelf
manager CLI issues a prompt to the terminal, accepts user input as the next command with parameters,
executes that command and shows the results on the terminal, until you enter the command exit or quit. For
example:
# clia
CLI> version
Pigeon Point Shelf Manager ver. 2.5.1
Pigeon Point is a trademark of Pigeon Point Systems.
Copyright (c) 2002-2006 Pigeon Point Systems
Build date/time: Nov 3 2006 09:43:12
All rights reserved#
The shelf manager manages the chassis over the Intelligent Platform Management Bus (IPMB). All of the chassis
slots have IPMB addresses (as well as hardware addresses) on this bus. When you enter shelf manager CLI
commands you indicate chassis slot numbers according to their IPMB addresses. The IPMB and hardware
addresses are in hexadecimal format.
38

Shelf Manager CLI
FortiGate-5144C chassis slot addresses

Node Node Node Node Node Node Hub Hub Node Node Node Node Node Node
Physical
slot
Logical
slot
Hardware
address
(Hex)
IPMB
address
(Hex)
10
11
12
13
14
13
11
10
12
14
4D
4B
49
47
45
43
41
42
44
46
48
4A
4C
4E
9A
96
92
8E
8A
86
82
84
88
8C
90
94
98
9C
Boards installed in chassis slots are called field replaceable units (FRUs). Many CLI commands also require
referencing a FRU. In most cases if a board is installed in a slot the slot will have one FRU with an ID of FRU 0.
However, if a FortiGate-5001A board is installed in a slot with an AMC module, this slot has two FRUs (FRU 0
and FRU 1).
For example, a FortiGate-5001A board with an AMC module is installed in logical slot 4, then at IPMB address
88, there will be FRU 0 (the FortiGate-5001A board) and FRU 1 (the AMC module).
FortiGate-5144C chassis component FRU names, IPMB addresses, and hardware addresses
FRU name
IPMB address (hex)
Hardware Address (hex)
SHMC left (left shelf manager)
10
08
SHMC right (right shelf manager)
12
09
SFRU1
20 FRU 1
10
SFRU2
20 FRU 2
10
Fan Tray 1
20 FRU 3
10
Fan Tray 2
20 FRU 4
10
Fan Tray 3
20 FRU 5
10
Fan Tray 4
20 FRU 6
10
PEM1 (A1)
20 FRU 7
10
PEM1 (A2)
20 FRU 8
10

39
Shelf Manager CLI
FRU name
IPMB address (hex)
Hardware Address (hex)
PEM1 (B1)
20 FRU 9
10
PEM1 (B2)
20 FRU 10
10
ATCA logical slot 1
82
41
ATCA logical slot 2
84
42
ATCA logical slot 3
86
43
ATCA logical slot 4
88
44
ATCA logical slot 5
8A
45
ATCA logical slot 6
8C
46
ATCA logical slot 7
8E
47
ATCA logical slot 8
90
48
ATCA logical slot 9
92
49
ATCA logical slot 10
94
4A
96
4B
98
4C
9A
4D
9C
4E

The default IP address of the primary shelf manager is 192.168.0.2. Use the following command to change this
IP address.
# clia setlanconfig <channel> ip <ip_address>
<channel> is the shelf manager channel and can be 1 or 2. <ip_address> is the new IP address in dotted
decimal notation. For example:
# clia setlanconfig 1 ip 192.168.0.2
Display the shelf manager firmware version

# clia version
40

Shelf Manager CLI
To display a complete list of all information enter version with no other parameters.

# clia fru
List all sensors on a FRU

# clia sensor <IPMB_address>
List only sensors that are outside of established thresholds

# clia sensor -t
Display sensor data for a FRU

# clia sensordata <IPMB_address> <sensor_number>
Display the FRU information for a FRU

# clia fruinfo <IPMB_address> <FRU_id>
Change the speed for a fan tray

# clia setfanlevel <IPMB-address> <FRU_id> <speed>
<speed> can be from 0 to 14.
Display the contents of the system event log (sel)

# clia sel
Clear the system event log (sel)

# clia sel clear

41
Shelf Manager CLI

You can configure the shelf manager IP address and gateway so that you can use telnet or ssh to access the
Shelf Manager instead of the serial console port. You can view the current LAN configuration with the following
command:
# clia getlanconfig 1
Authentication Type Support: 0x15 (None MD5 Straight Password/Key )
Authentication Type Enables:
Callback level: 0x00
User level: 0x15 ("None" "MD5" "Straight Password/Key" )
Operator level: 0x15 ("None" "MD5" "Straight Password/Key" )
Administrator level: 0x15 ("None" "MD5" "Straight Password/Key" )
OEM level: 0x00
IP Address: 192.168.0.2
IP Address Source: Static Address (Manually Configured) (0x01)
MAC Address: 00:50:c2:3f:f0:9a
Subnet Mask: 255.255.255.0
IPv4 Header Parameters: 0x40:0x40:0x10
Primary RMCP Port Number: 0x026f
Secondary RMCP Port Number: 0x0298
BMC-generated ARP Control: 0x02
Enable BMC-generated ARP Response
Gratuitous ARP Interval: 2.0 seconds
Default Gateway Address: 192.168.0.1
Default Gateway MAC Address: 00:09:0f:09:32:03
Backup Gateway Address: 0.0.0.0
Backup Gateway MAC Address: N/A
Community String: "public"
Number of Destinations: 16
Destination Type:
DST Type # 2, Type: Unacknowledged PET Trap Destination (0x00), ACK Timeout / Retry
Interval: 0 seconds,
Retries: 0
Destination Address:
DST Addresses # 2, Address Format: IPv4 IP Address followed by DIX ethernet / 802.3 MAC
Address (0x00) Gateway: Default (0x00), Alerting IP: 192.168.182.86, Alerting MAC:
00:09:0f:09:32:03
You can use the clia setlanconfig command to modify the shelf manager LAN configuration.
# clia setlanconfig
Error: too few parameters
Sets the LAN settings
parameter:
2 or "auth_enables"
3 or "ip"
6 or "subnet_mask"
7 or "ipv4_hdr_param"
10 or "arp_control"
11 or "arp_interval"
12 or "dft_gw_ip"
14 or "backup_gw_ip"
42

Shelf Manager CLI
Sensor types
16 or "community"
18 or "destination_type"
19 or "destination_address"
setlanconfig <channel number> <parameter number> | parameter name <parameters ...>
To change the IP address, subnet mask, default gateway, enter the following commands:
# clia setlanconfig 1 12 x.x.x.x
Sensor types
Access to monitoring information, such as temperatures and voltages, fan status, etc., is provided by the IPMI
Sensor Module. Instead of providing direct access to the monitoring hardware, IPMI provides access by
abstracted sensor commands implemented using a management controller. This approach isolates software
from changes in the platform management hardware implementation.
Sensors are classified according to the type of readings they provide and/or the type of events they generate. A
sensor can return either an analog or discrete reading. Sensor events can be discrete or threshold-based. The
different event types, sensor types, and monitored entities are represented using numeric codes (in hexadecimal)
defined in the IPMI specification.
Example of sensor type:
l
01 for temperature sensor
02 for voltage sensor
C0-FF for OEM reserved sensors (F0 is the hot swap sensor and F1 is the IPMB link sensor).

THis section describes many of the commonly used shelf manager CLI commands in alphabetical order.
activate/deactivate
clia activate <IPMB-address> <FRU-id>
clia deactivate <IPMB-address> <FRU-id>
Use these commands to activate and deactivate a specified FRU. After you enter the deactivate command to
deactivate a FortiGate board the boards IPM or hot swap LED changes to blue and the board will no longer be
accessible. The board is ready to be hot-swapped.
For example, to deactivate a board in physical slot 11 of a chassis (IPMB address 90, logical slot 8), enter:
# clia deactivate 90 0
Command issued via IPMB, status = 0 (0x0)
Command executed successfully
You can re-activate this deactivated board with the following command:
# clia activate 90 0

43
Shelf Manager CLI
Command issued via IPMB, status = 0 (0x0)

Command executed successfully
alarm
clia alarm [clear | info| minor | major | critical]
This command provides access to the TELCO alarm outputs.

Enter clia alarm without parameters to view the current status of TELCO alarm outputs:
# clia alarm
alarm mask: 0x00
Alarm mask 0x00 means no alarm.
Clearing alarms
Enter clia alarm clear to clear the minor and major alarm outputs. By default, critical alarm outputs can be
cleared because the shelfman.conf file contains the following lines:
# ALLOW_CLEARING_CRITICAL_ALARM: This parameter of boolean type enables the
# ability to clear the critical alarm condition without the alarm cutoff
# button. Default is FALSE.
#
ALLOW_CLEARING_CRITICAL_ALARM = TRUE
If you change ALLOW_CLEARING_CRITICAL_ALARM to FALSE the clia alarm clear command does
not clear critical alarms.
Enter clia alarm info to display information about the last alarm that occurred:
# clia alarm info
Last saved alarm information:
Alarm mask: 0x00
Alarm date/time: Sun Jun 8 21:56:47 2009
Alarm source: Schroff Carrier
Alarm reason: Cooling state alert
Clearing the alarm changes the information displayed by the clia alarm command but not the
information displayed by the clia alarm info command
Setting alarm output

Use minor, major and critical to set the corresponding alarm output. These actions are cumulative; that is, after
the commands clia alarm minor and clia alarm major, both minor and major alarms will be set.
board
clia board [-v] [<physical-slot-address>]
44

Shelf Manager CLI
Enter clia board without any parameters to view information about each IPM controller and about each
additional FRU controlled by these controllers.
This command is different from most of the rest of the commands because its works with ATCA boards and takes
as arguments physical slot numbers, instead of IPM controller addresses and FRU device IDs.
This makes this command easier to use when boards may not include an IPM controller and therefore, are not
easily addressable using the IPMB address FRU device ID pair.
Viewing information about a board

Enter the following command to view information about a particular board, for example the board in physical slot
11 (logical slot 8, IPMB address 90):
# clia board 11
Physical Slot # 11
90: Entity: (0xa0, 0x60) Maximum FRU device ID: 0x00
PICMG Version 2.1
Hot Swap State: M4 (Active), Previous: M3 (Activation In Process), Last State Change
Cause: Normal State
Change (0x0)
90: FRU # 0
Entity: (0xa0, 0x60)
Cause: Normal State
Change (0x0)
Device ID String: "FG5005A"
Add v to the command to display more information (verbose).

The command output includes the hot swap state. M4 is the normal hot swap state.
The following table lists the FRU states defined in the PICMG 3.0 specification as follows:
PICMG FRU states

FRU state
Description
M0
Not Installed
M1
Inactive
M2
Activation Request
M3
Activation in Progress
M4
FRU Active
M5
Deactivation Request
M6
Deactivation in Progress

45
Shelf Manager CLI
FRU state
Description
M7
Communication Lost
clia
clia
Start the CLI interactive mode. Using the interactive mode you can enter commands without including the clia
prefix. bd say something about the prompt changing.
exit/quit
exit
quit
If you start the CLI interactive mode by entering clia without any parameters you can enter exit or quit to
exit interactive mode.
fans
clia fans [-v] [<IPMB_address> [<FRU_device_ID> ] ]
Display information about the specified fan FRU. If <FRU_device_ID> is omitted, the command displays
information about all fan FRUs controlled by the IPM controller at the specified address. If <IPMB_address> is
also omitted, the command displays information about all fan FRUs known to the shelf manager. The command
displays the following information for each fan:
l
IPMB address and FRU device ID
Current Level
Minimum Speed Level
Maximum Speed Level

# clia fans
20: FRU # 6
Current Level: 30
Minimum Speed Level: 0, Maximum Speed Level: 0 Dynamic minimum fan level: 30
20: FRU # 5
Current Level: 30
20: FRU # 4
Current Level: 30
20: FRU # 3
Current Level: 30
46

Shelf Manager CLI
fru
clia fru [-v] [<IPMB_address> [id=<fru_device_id> | type=<site_type>]] | [type=<site_type>
[/<site_number>]]
This command displays information about a specific FRU. If <FRU_device_ID> is omitted, the command
shows information about all FRUs controlled by the IPM controller at the specified address. If <IPMB_
address> is also omitted, the command displays information about all FRUs known to the shelf manager.
Display information for a specific FRU

Enter this command with an IPMB address that refers to a physical slot to display information similar to that
displayed by the clia board command (see board on page 44). For example, to display information about the
board in physical slot11 (logical slot 8, IPMB address 90) enter:
# clia fru 90
90: FRU # 0
Entity: (0xa0, 0x60)
Hot Swap State: M4 (Active), Previous: M4 (Active), Last State Change Cause: Normal
State Change (0x0)
Device ID String: "FG5005A"
fruinfo
clia fruinfo [-v] [-x]<addr> <fru_id>
This command displays FRU Information in a user-friendly format.

For example to display FRU information for fan tray 0:
# clia fruinfo 20 3
20: FRU # 3, FRU Info
Common Header:
Format Version = 1
Board Info Area:
Version
= 1
Language Code
Mfg Date/Time
Board Manufacturer
Board Product Name
Shelf
Board Serial Number
Board Part Number
FRU Programmer File ID
Product Info Area:
Version
= 1
Language Code
Manufacturer Name
Product Name

=
=
=
=
25
Oct 9 14:02:00 2014 (9873482 minutes since 1996)
Comtel Electronics GmbH
Fan Tray Controller Board for ATCA CO14G4 14 Slot
= 0701800C0001437131
= 370-07018
= 401-0706X(Rev1)
= 25
= Comtel Electronics GmbH
= Fan Unit for ATCA CO14G4 14 Slot Shelf
47
Shelf Manager CLI
Product Part / Model#

Product Version
Product Serial Number
Asset Tag
FRU Programmer File ID
= 401-07065/66
= A
= 0701800C0001437131
=
=
getlanconfig
clia getlanconfig <channel> [[<parameter_name> [<additional_parameters>]] | [<parameter_
number> [<additional_parameters>]]
This command displays the LAN configuration parameters on the specified <channel>. You can enter a
<parameter_name> or the corresponding <parameter_number> number to display information for a
configuration parameter. The following table lists some commonly used <parameter_names> and
<parameter_numbers>.
Displaying all configuration parameters for a channel

If you do not include a <parameter_name> or <parameter_number> all configuration parameters for the
specified channel are displayed. See Change IP address of the primary Shelf Manager on page 40 for an example
of using this command to display the shelf manager LAN configuration.
Commonly used getlanconfig parameter name and parameter numbers

<parameter_ <parameter_
Description
name>
number>
ip
subnet_mask
dft_gw_mac
13
A string value that contains the IP address assigned to the LAN channel in dotted
decimal notation. For example, 192.168.0.2.
A string value that contains the subnet mask assigned to the LAN channel in dotted
decimal notation. For example, 255.255.255.0.
A string value that contains the MAC address of the default gateway as 6
hexadecimal byte values delimited by : symbols. For example, 00 : 1A : a0
: 2F : BC : C6.
Displaying specific parameters for a channel

Enter the following command to display the IP address associated with channel 1:
# clia getlanconfig 1 ip
IP Address: 192.168.0.2
The following command also displays the IP address associated with channel 1:
# clia getlanconfig 1 3
IP Address: 192.168.0.2
48

Shelf Manager CLI
The following command displays the subnet mask associated with channel 1:
# clia getlanconfig 1 subnet_mask
Subnet Mask: 255.255.255.0
The following command also displays the subnet mask associated with channel 1:
Subnet Mask: 255.255.255.0
The following command displays the default gateway IP address associated with channel 1:
# clia getlanconfig 1 dft_gw_ip
The following command also displays the default gateway IP address associated with channel 1:
getthreshold/threshold
clia getthreshold [<IPMB-address> [<sensor-name> | [<lun>:]<sensor-number>]]
clia threshold [<IPMB-address> [<sensor-name> | [<lun>:]<sensor-number>]]
This command displays the current threshold values for the supported thresholds of the specified sensor(s). The
sensor must be a threshold-based sensor. Both raw and processed values are displayed. The following attributes
for each sensor are also displayed:
l
IPMB address of the owning IPM controller
Sensor number, sensor name and the LUN by which the sensor can be accessed
The Sensor type and Event/reading type code
Display threshold sensor values for a physical slot

For example, to display the values for threshold sensors on physical slot 411(in this example, a FortiGate5005FA2), enter the following command:
# clia threshold 90
90: LUN: 0, Sensor # 4 ("CPU1 Voltage")
Type: Threshold (0x01), "Voltage" (0x02)
Lower Non-Critical Threshold, Raw Data: 0x6c Processed data: 1.058400 Volts
Lower Critical Threshold, Raw Data: 0x67 Processed data: 1.009400 Volts
Lower Non-Recoverable Threshold, Raw Data: 0x61 Processed data: 0.950600 Volts
Upper Non-Critical Threshold, Raw Data: 0xa9 Processed data: 1.656200 Volts
Upper Critical Threshold, Raw Data: 0xae Processed data: 1.705200 Volts

49
Shelf Manager CLI
Upper Non-Recoverable Threshold, Raw Data: 0xb3 Processed data: 1.754200 Volts
90: LUN: 0, Sensor # 5 ("CPU2 Voltage")
Lower Non-Critical Threshold, Raw Data: 0x6c Processed data: 1.058400 Volts
Lower Non-Recoverable Threshold, Raw Data: 0x61 Processed data: 0.950600 Volts
Upper Non-Critical Threshold, Raw Data: 0xa9 Processed data: 1.656200 Volts
Upper Critical Threshold, Raw Data: 0xae Processed data: 1.705200 Volts
Upper Non-Recoverable Threshold, Raw Data: 0xb3 Processed data: 1.754200 Volts
90: LUN: 0, Sensor # 6 ("+5.0V")
Lower Non-Critical Threshold, Raw Data: 0xbe Processed data: 4.655000 Volts
Lower Critical Threshold, Raw Data: 0xb8 Processed data: 4.508000 Volts
Lower Non-Recoverable Threshold, Raw Data: 0xb0 Processed data: 4.312000 Volts
Upper Non-Critical Threshold, Raw Data: 0xdb Processed data: 5.365500 Volts
Upper Critical Threshold, Raw Data: 0xe1 Processed data: 5.512500 Volts
Upper Non-Recoverable Threshold, Raw Data: 0xe9 Processed data: 5.708500 Volts
90: LUN: 0, Sensor # 7 ("+3.3V")
Lower Non-Critical Threshold, Raw Data: 0xc0 Processed data: 3.110400 Volts
Lower Critical Threshold, Raw Data: 0xba Processed data: 3.013200 Volts
Lower Non-Recoverable Threshold, Raw Data: 0xb4 Processed data: 2.916000 Volts
Upper Non-Critical Threshold, Raw Data: 0xd9 Processed data: 3.515400 Volts
Upper Critical Threshold, Raw Data: 0xdf Processed data: 3.612600 Volts
Upper Non-Recoverable Threshold, Raw Data: 0xe5 Processed data: 3.709800 Volts
90: LUN: 0, Sensor # 8 ("+2.5V CPU 1")
Lower Non-Critical Threshold, Raw Data: 0xbd Processed data: 2.305800 Volts
Lower Non-Recoverable Threshold, Raw Data: 0xad Processed data: 2.110600 Volts
Upper Non-Critical Threshold, Raw Data: 0xde Processed data: 2.708400 Volts
Upper Non-Recoverable Threshold, Raw Data: 0xee Processed data: 2.903600 Volts
90: LUN: 0, Sensor # 9 ("+2.5V CPU 2")
Lower Non-Critical Threshold, Raw Data: 0xbd Processed data: 2.305800 Volts
Lower Non-Recoverable Threshold, Raw Data: 0xad Processed data: 2.110600 Volts
Upper Non-Critical Threshold, Raw Data: 0xde Processed data: 2.708400 Volts
Upper Non-Recoverable Threshold, Raw Data: 0xee Processed data: 2.903600 Volts
90: LUN: 0, Sensor # 10 ("+1.2V 1")
Lower Non-Critical Threshold, Raw Data: 0x76 Processed data: 1.156400 Volts
Lower Non-Recoverable Threshold, Raw Data: 0x6c Processed data: 1.058400 Volts
Upper Non-Critical Threshold, Raw Data: 0x80 Processed data: 1.254400 Volts
Upper Critical Threshold, Raw Data: 0x85 Processed data: 1.303400 Volts
Upper Non-Recoverable Threshold, Raw Data: 0x8a Processed data: 1.352400 Volts
90: LUN: 0, Sensor # 11 ("+1.2V 2")
50

Shelf Manager CLI

Lower Non-Critical Threshold, Raw Data: 0x76 Processed data: 1.156400 Volts
Lower Non-Recoverable Threshold, Raw Data: 0x6c Processed data: 1.058400 Volts
Upper Non-Critical Threshold, Raw Data: 0x80 Processed data: 1.254400 Volts
Upper Critical Threshold, Raw Data: 0x85 Processed data: 1.303400 Volts
Upper Non-Recoverable Threshold, Raw Data: 0x8a Processed data: 1.352400 Volts
90: LUN: 0, Sensor # 12 ("Incoming Air-Flo")
Type: Threshold (0x01), "Temperature" (0x01)
Upper Non-Critical Threshold, Raw Data: 0x28 Processed data: 40.000000 degrees C
Upper Critical Threshold, Raw Data: 0x2d Processed data: 45.000000 degrees C
Upper Non-Recoverable Threshold, Raw Data: 0x32 Processed data: 50.000000 degrees C
90: LUN: 0, Sensor # 13 ("CPU Board Temp")
Upper Non-Critical Threshold, Raw Data: 0x4b Processed data: 75.000000 degrees C
Upper Critical Threshold, Raw Data: 0x51 Processed data: 81.000000 degrees C
90: LUN: 0, Sensor # 14 ("CPU1 Temp")
90: LUN: 0, Sensor # 15 ("CPU2 Temp")
Display threshold sensor values for a specific sensor

Enter the following command to display the threshold for sensor 13, which for the FortiGate-5005FA2 is the CPU
board temperature:
# clia threshold 90 13
You can also enter the name of the sensor in quotes:

# clia threshold 90 "CPU Board Temp"
help
clia help [<command> [<sub_command>] ]
This command displays help information about supported commands and their syntax. Enter the command with
no parameters to display all commands:

51
Shelf Manager CLI
# clia help
Command Line Interface command set:
Parameters are case insensitive
In general:
IPMB address is hexadecimal ALWAYS.
All other numbers may be either decimal and hexadecimal (0x notation required for
hexadecimal notation)
-v turns on verbose output
activate <addr> <fru_id>
alarm <alarm status/action>
amcgetlanconf <address> [amc <N> | <fru_id> ] <channel number> <parameter number> | <parameter name>
amcgetsolconf <address> [amc <N> | <fru-id> ] <channel number> <parameter number> | <parameter name>
amcportstate [-v] <ipmc> [amc <N> | <fru_id> ]
amcsetlanconf <address> [amc <N> | <fru-id> ] <channel number> <parameter number> | parameter name <parameters ...>
amcsetsolconf <address> [amc <N> | <fru-id> ] <channel number> <parameter number> | parameter name <parameters ...>
axie sequencing
board [slot_number]
boardreset <slot number>
busres force <res>
busres info [<res>]
busres lock <res>
busres query [-v] <res> [<target> [noupdate]]
busres release <res>
busres sendbusfree <res> <target>
busres setowner <res> <target>
busres unlock <res>
deactivate <addr> <fru_id>
debuglevel [<mask> [<console mask>] ]
dhcp <restart> | <status>
exit
fans <addr> <fru id>
firewall [<info [[[[<channel>]:<LUN>]:<NetFn>]:<command>] | <[all]>> | <stop> | <start>]
fru [<addr> [id=<fru_id> | type=<site_type>]] | [type=<site_type> [/<site_number>]]
frucontrol <addr> <fru_id> <command>
frudata [<addr>] [<fru id>] [<block number>]
frudata shm <N> [<block number>]
frudata <addr> <fru id> <byte offset> <byte_1> [byte2 .. [byte_16]]
frudatar <addr> <fru id> <file name>
frudataw [-s|-d|-p|-l] <addr> <fru id> <file name>
frudataw <-s|-d|-p|-l> -c <addr> <fru id>
fruinfo <addr> <fru_id>
getbootdev <addr> [<fru-id> | <amc-addr>]
getconfigparam [<parameter name>]
getfanlevel <addr> <fru_id>
getfanpolicy [<addr> [<fru_id>]] [-s <addr>|site_type [<fru_id>|site_number]]
getfruledstate [-v] [<addr> [<fru_id> [<LedId>|ALL]]]
gethysteresis [<addr> [[lun: ]<sensor id> | <sensor name> ] ]
gethysteresis [<addr> -f <fru id> ]
52

Shelf Manager CLI
gethysteresis [<addr> -f amc <amc number> ]

getipmbstate <addr> [<link>]
getlanconf <address> <channel number> <parameter number> | <parameter name>
getlanconfig <channel number> <parameter number> | <parameter name>
getpefconfig <parameter name> | <parameter number> [<set selector>]
getsensoreventenable [<addr> [[lun: ]<sensor_id> | <sensor name> ] ]
getsensoreventenable [<addr> -f <fru id> ]
getsensoreventenable [<addr> -f amc <amc number> ]
getsolconf <address> <channel number> <parameter number> | <parameter name>
getthreshold [<addr> [[lun: ]<sensor id> | <sensor name> ] ]
getthreshold [<addr> -f <fru id> ]
getthreshold [<addr> -f amc <amc number> ]
help [<command>]
ipmc [-v] [-x] [<addr>]
localaddress
minfanlevel <addr> <fru_id> <min fan level>
minfanlevel [<min fan level>]
ping <addr> <count>
ping2 <addr> <count>
ping3 <addr> <fru-id> <count>
poll
quit
sel [clear] [<addr> [<number of items> [<number of first item>] ] ]
sel info [<addr>]
sendamc <addr> <amc> [<lun>:]<netfn> <command> [<parameters ...>]
sendcmd <addr> [<lun>:]<netfn> <command> [<parameters ...>]
sensor [<addr> [[lun: ]<sensor id> | <sensor name> ] ]
sensor [<addr> -f <fru id> ]
sensor [<addr> -f amc <amc number> ]
sensordata [-t] [-d <state>] [<addr> [[lun: ]<sensor id> | <sensor name> ] ]
sensordata [-t] [-d <state>] [<addr> -f <fru id> ]
sensordata [-t] [-d <state>] [<addr> -f amc <amc number> ]
sensorread <addr> [lun: ]<sensor id>
session [<-v>]
setbootdev <addr> <fru-id | amc-addr> <boot-device>
setcommandpolicy <Enable|Disable> <NetFn> <CMD> [<channel>] [<LUN>]
setextracted <addr> <fru_id>
setfanlevel <addr> <fru_id> <state>
setfanpolicy <addr> <fru_id> <ENABLE | DISABLE [timeout]> [-s <addr> | site_type <fru_id> |
site_number]
setfruledstate <addr> <fru_id> <LedId> | ALL <LedOp | tail> [LedColor]
setfunctionpolicy <EnableDisableMask> <NetFn> <CMD> [<channel>] [<LUN>]
sethysteresis <addr> [lun: ]<sensor_id> | <sensor name> pos | neg <value>
setipmbstate <addr> A | B [<link>] 0|1
setlanconf <address> <channel number> <parameter number> | parameter name <parameters ...>
setlanconfig <channel number> <parameter number> | parameter name <parameters ...>
setlocked <addr> <fru_id> <value>
setpefconfig <parameter name> | <parameter number> [<set selector>] <parameters ...>
setpowerlevel <addr> <fru_id> [<pwr_lvl> | OFF] [Copy]
setsensordata <addr> [lun: ]<sensor_id> | <sensor name> [reading [-r] <value> ]
[assertion <mask> ] [deassertion <mask> ]
[event_data <b1> <b2> <b3> | event_data_no_offset <b1> <b2> <b3>]
setsensoreventenable <addr> [lun: ]<sensor_id> | <sensor name> global [assertion_events
[deassertion_events]]
setsolconf <a>

53
Shelf Manager CLI
Displaying more information about a command

Enter the following command to display more information about the threshold command:
# clia help threshold
IPM Sentry Shelf Manager Command Line Interpreter
Shows the threshold of the specified sensor
instead of <addr> user may use:
board <N>
shm <N>
to access the sensor on the specified board
getthreshold board 21 "IPMB LINK"
getthreshold 20 8
threshold [<addr> [[lun: ]<sensor id> | <sensor name> ] ]
Enter the following command to display more information about the fruinfo command:
# clia help fruinfo
Display the FRU Info of the dedicated FRU in the readable format
instead of <addr> <fru_id> user may use:
power_supply <N> (valid in 2.x systems only)
fan_tray <N>
board <N>
shm <N>
to access the FRU on the specified board
fruinfo board 21 8
fruinfo power_supply 4
fruinfo <addr> <fru_id>
minfanlevel
clia minfanlevel [<level>]
This command displays or temporarily sets the minimum fan level. The minimum fan level will return to the
default setting when the chassis power is cycled or the shelf manager reboots. Under normal conditions, the
cooling management algorithm gradually decreases the level for the fans in the chassis while thermal conditions
stay normal. The cooling management algorithm will not try to decrease the fan level below the minimum level
specified by the configuration parameter MIN_FAN_LEVEL or by this command. The minimum fan level affects
only the automatic management of the fan level by the cooling management facility.
Enter the command with no parameters to display the current minimum fan level.
Enter the command with an integer to temporarily set the minimum fan level (until the next chassis power cycle or
shelf manager reboot).
sel
clia sel [-v] [<IPMB-address> [<record-count> [starting-entry]]]
clia sel clear [<IPMB-address>]
clia sel info [<IPMB-address>]
The System Event Log (SEL) is useful for troubleshooting as shown in the examples below.
54

Shelf Manager CLI
You can also use the Linux command cat /tmp/messages to view shelf manager system log
messages. This information can be useful for diagnosing system problems. This information can also
help Fortinet Support diagnose shelf manager system problems.
The sel command shows the contents of the SEL on the specified IPM Controller (at IPMB address 20h by
default). The optional <record-count> indicates how many records from the record number <startingentry> in the SEL are displayed. The optional parameter <starting-entry> is the entry number of the first
SEL record to print, relative to the beginning of the SEL. Both <record-count> and <starting-entry>
must be within the range of 1 to the total number of records in the SEL. The default value of the optional
parameter <starting-entry> is 1. The <starting-entry> is independent of the RecordID field of the
SEL record.
The command displays the following information fields for each SEL record:
l
Record ID
Record type (currently only events are supported, for which the word Event is shown
Timestamp (for timestamped records)
Source address parameters: IPMB address, LUN and channel number
Type and number of the sensor that generated the event
Event/reading type code
3 bytes of event data, in raw and processed (if available) formats.
The command sel clear clears the SEL on the specified IPM Controller (at IPMB address 20h by default). The
-v option makes the command output more user-readable.
The following example messages show that the hot swap state of FRU 0 at address 0x86 (a FortiGate-5000
series board in physical slot 6) has been M7 (communication lost) for 11 seconds. The first message indicates
when the board went from the M4 state (active) to the M7 state (communication lost) and the second message
shows when the board went from the M7 state back to the M4 state.
0x0332: Event: at Aug 5 11:07:18 2009;
(asserted): HotSwap: FRU 0 M4->M7,
0x0333: Event: at Aug 5 11:07:29 2009;
from:(0x86,0,0); sensor:(0xf0,0); event:0x6f

Cause=0x4
Cause=0x4
from:(0x86,0,0) indicates the event comes from physical slot 6 of a FortiGate chassis.
sensor:(0xf0,0) indicates a hot swap sensor.
The following example messages show that the upper non-critical threshold (0x28 = 40) of the temperature
sensor number 12 on slot 6 has been reached for two seconds.
0x0386: Event: at Aug 5 16:16:12 2009; from:(0x86,0,0); sensor:(0x01,12); event:0x1
(asserted): "Upper Non-Critical", Threshold: 0x28, Reading: 0x28
0x0387: Event: at Aug 5 16:16:14 2009; from:(0x86,0,0); sensor:(0x01,12); event:0x1
(deasserted): "Upper Non-Critical", Threshold: 0x28, Reading: 0x27
You can use the threshold command to check the threshold values of these sensors.
# clia threshold 86 12
86: LUN: 0, Sensor # 12 ("TEMP1")
Upper Non-Critical Threshold, Raw Data: 0x28 Processed data: 40.000000 degrees C

55
Shelf Manager CLI
Upper Non-Recoverable Threshold, Raw Data: 0x3c Processed data: 60.000000 degrees C
The first two SEL lines below indicate a problem (last hex number is not 0x88) for the IPMB link (sensor F1) on
slot 9 and 10. The problem has cleared quickly because the last two lines show last hex number is 0x88.
0x0219: Event: at Aug 6 10:39:54
(asserted): 0xA2 0x00 0x89
0x021A: Event: at Aug 6 10:39:55
(asserted): 0xA2 0x00 0x8F
0x021C: Event: at Aug 6 10:39:55
0x021E: Event: at Aug 6 10:39:56
2009; from:(0x88,0,0); sensor:(0xf1,1); event:0x6f

2009; from:(0x8c,0,0); sensor:(0xf1,1); event:0x6f
sensor
clia sensor [-v] [<IPMB-address> [<sensor-name> | [<lun>:]<sensor-number>]]
This command displays information about specific sensor(s). The target sensor is selected by its IPM controllers
IPMB address and by sensor number or by sensor name. If neither sensor name nor sensor number is specified,
information about all sensors on the specified IPM controller is displayed. If no parameters are specified,
information about all known sensors is displayed.
The following information is shown for each sensor in standard mode (non verbose mode):
l
l
IPMB address of the owning IPM controller

Sensor number, sensor name (device ID string from the Sensor Data Records (SDRs)) and the LUN by which the
sensor can be accessed
The sensor type and event/reading type code
The Entity ID, Entity Instance of the related entity (the FRU device ID if the sensor is associated with a FRU)
Example for slot 11 and sensor 13:

# clia sensor 90 13
Belongs to entity: (0x3, 96) [FRU # 0]
# clia sensor 8890 "CPU Board Temp"
Belongs to entity: (0x3, 96) [FRU # 0]
sensordata
clia sensordata [-v] [-t] [<IPMB-address> [<sensor-name> | [<lun>:]<sensor-number>]]
This command displays the actual value of the specified sensor or sensors (for a threshold based sensor) or the
currently asserted states (for a discrete sensor). The target sensor is selected by entering the IPM controllers
IPMB address and the sensor number or the sensor name. If you do not include the sensor name or number, the
command displays the values of all sensors on the specified IPM controller. If you do not enter any parameters,
the command displays values of all known sensors.
56

Shelf Manager CLI
The following information is displayed for each sensor:

l
IPMB address of the owning IPM controller.
Sensor number, sensor name (device ID string from the SDR) and the LUN by which the sensor can be accessed.
The sensor type and event/reading type code.
The sensor value (for threshold-based sensors) or the mask of currently asserted states (for discrete sensors) in raw
form.
The threshold crossing status, in hexadecimal format and with decoding.
Use -t to displayed information only for threshold-based sensors, that have at least one of their thresholds
crossed.
Example for physical slot 411(logical slot 48and IPMB address 90) and sensor 13, a temperature sensor:
# clia sensordata 90 13
Status: 0xc0
All event messages enabled from this sensor
Sensor scanning enabled
Initial update completed
Raw data: 44 (0x2c)
Processed data: 44.000000 degrees C
Status: 0x00
setthreshold
setthreshold <IPMB-address> <sensor-name> <threshold-type> [-r] <value>
setthreshold <IPMB-address> [<lun>:]<sensor-number> <threshold-type> [-r] <value>
Where <IPMB-address> can be board <board-number> or shm <shelf-manager-number>.

<threshold-type> can be:
upper_non_recoverable (can be abbreviated to unr)
upper_critical (can be abbreviated to uc)
upper_non_critical (can be abbreviated to unc)
lower_non_recoverable (can be abbreviated to lnr)
lower_critical (can be abbreviated to lc)
lower_non_critical (can be abbreviated to lnc)
By default, the target value is specified in real units (for example, in Volts for voltage sensors or in Celsius
degrees for temperature sensors). Option r means that a raw value is used instead (usually a byte-size quantity,
converted according to sensor-specific rules).
Using this command you can qualify the sensor number with the logical unit number (LUN) if the target controller
supports sensors on multiple LUNs. <lun> can take the value 0, 1 or 3. (LUN 2 is reserved.) If the LUN is
omitted, the command applies to the sensor with the specified sensor number on the lowest LUN. (For example,
if the command specifies sensor 3 without explicit LUN qualification, and the target controller exposes sensor 3
on LUN 1 and another sensor 3 on LUN 3, the command is applied to the sensor 3 on LUN 1.)

57
Shelf Manager CLI
This command can also be issued on the backup Shelf Manager; in that case, threshold values can only be set for
sensors that are local to the backup Shelf Manager.
Use the following example to set the upper non-critical threshold value for the temperature sensor emulated
temp on IPM controller 9Chto 99 degrees Celsius.
# clia threshold 9c 2
9c: LUN: 0, Sensor # 2 ("emulated temp")
Lower Non-Critical Threshold, Raw Data: 0x03, Processed Data:
3.000000 degrees C
Lower Critical Threshold, Raw Data: 0x14, Processed Data:
20.000000 degrees C
Lower Non-Recoverable Threshold, Raw Data: 0xfb, Processed
Data: -5.000000 degrees C
Upper Non-Critical Threshold, Raw Data: 0x46, Processed Data:
70.000000 degrees C
Upper Critical Threshold, Raw Data: 0x50, Processed Data:
80.000000 degrees C
Upper Non-Recoverable Threshold, Raw Data: 0x5a, Processed
Data: 90.000000 degrees C
# clia setthreshold 9c 0:2 unc 99

Threshold set successfully
# clia threshold 9c 0:2

889c: LUN: 0, Sensor # 2 ("emulated temp")
Lower Non-Critical Threshold, Raw Data: 0x03, Processed Data:
3.000000 degrees C
Lower Critical Threshold, Raw Data: 0x14, Processed Data:
20.000000 degrees C
Lower Non-Recoverable Threshold, Raw Data: 0xfb, Processed
Data: -5.000000 degrees C
Upper Non-Critical Threshold, Raw Data: 0x63, Processed Data:
99.000000 degrees C
Upper Critical Threshold, Raw Data: 0x50, Processed Data:
80.000000 degrees C
Upper Non-Recoverable Threshold, Raw Data: 0x5a, Processed
Data: 90.000000 degrees C
shmstatus
clia shmstatus [-v]
58

Shelf Manager CLI
This command displays the Shelf Manager status in redundant configurations: Active or Backup. In verbose mode
(using -v) the command displays more information including the status of the Shelf FRU Info, status of the
Remote Management Control Protocol (RMCP) interface, and state of the backup Shelf Manager (if the Shelf
Manager being queried is the active one).
The command output includes a Ready For Operation flag that shows Yes:
For the active Shelf Manager if the active shelf manger finds valid shelf FRU information and successfully
initializes its RMCP interface.
For the backup Shelf Manager if the backup shelf manager successfully receives redundancy state information
from the active Shelf Manager.
Example verbose mode output for an active shelf manager:
# clia shmstatus -v
Host: "Active"
Ready For Operation: Yes
Detailed State Flags: "Shelf FRU Found" "Backup Healthy" "Initial Update Sent" "RMCP Up"
showunhealthy
clia showunhealthy
This command displays the list of FRUs that appear to have a problem. In the PICMG 3.0 context, problems are
defined as FRUs for which the cause of the last hot swap state change is one of the following:
l
Communication Lost
Communication lost due to local failure
Unexpected deactivation
If no FRUs have a problem, the command displays

There are no unhealthy components in the shelf.
The following information is shown for each FRU considered to have a problem:
l
IPMB address and FRU device ID
Current Hot Swap state
Previous hot swap state
Cause of the last state change.
switchover
clia switchover [-force]
If a chassis has two shelf managers, you can enter this command to switch the active shelf manager to running as
the backup shelf manager and the backup shelf manager to switch to running as the active shelf manager. You
can enter this command from the active or backup shelf manger. When you enter the command the shelf
managers negotiate a smooth switchover.
If you enter this command from the backup shelf manager you can include -force to force the switchover without
any negotiation. The backup shelf manager immediately becomes the active shelf manager and the active shelf
manager reboots and starts up as the backup shelf manager.

59
Shelf Manager CLI
terminate
clia terminate [-reboot]
This command terminates the Shelf Manager and reboots the ShMM. Including -reboot does not change the
command.
clia terminate [-reboot]
This command terminates the Shelf Manager. If you include -reboot the ShMM unconditionally reboots. If you do
not include -reboot, the command terminates the Shelf Manager without rebooting the ShMM.
user
clia user [add | delete | enable | name | passwd | channel]
clia user [-v] [<user_id>]
Use this command to add, delete, modify and display RMCP user accounts for a shelf manager.
Display all user accounts

Enter the following command to display user account information:
clia user -v
1: ""
Channels 0-15 Privilege level: "Administrator"
Flags: "IPMI Messaging"
7: "TEST1" Disabled
Channels 0-15 Privilege level: "NO ACCESS"
Include -v to display disabled user accounts. For each user account the command displays:
l
User ID
User name
Channel access information for each IPMI channel: the maximum privilege level of that user account on that
channel, and channel access flags. If the channel access information is the same for several channels, the output
displays the information for the channel number range.
Adding a user account

Use the following command syntax to add a user account:
user add <user_id> <user_name> <channel_access_flags> <privilege_level> <password>
This command adds a new RMCP user account to the shelf manager. The command also sets the same
maximum privilege level and channel access flags for all channels. Where:
l
<user_id> is a valid user ID
<user_name> is a user name (truncated to the 16 characters without notice)
60
<channel_access_flags> is the first byte of the SetUserInfo commands (only bits 4,5,6 are meaningful)
l
bit 6 enables IPMI messaging
l
bit 5 enables link authentication
bit 4 restricts the user to callback

Shelf Manager CLI
<privilege_level> is the user account privilege level
<password> is the user account password (truncated to the 16 characters without notice).
For example, add a user account with user ID 9, user name user_1, administrator privilege level, and password
my-password.
clia user
1: ""
clia user add 9 "user_1" 0x40 4 "my-password"
User 9 added successfuly
clia user
1: ""
9: "user_1"
Deleting user accounts
Use the following command syntax to delete user accounts:

clia user delete <user_id>
For example, enter the following command to delete user account 23:
clia user delete 23
Disabling and enabling user accounts

Use the following command syntax to disable and enable user accounts.
clia user enable <user_id> {1 | 0}
Where 1 enables the user account and 2 disables the user account.
User accounts are enabled when you add them. You can use the command clia user -v to display enabled
user accounts. When you use the clia user-v command, entries for disabled user accounts include
Disabled. If you dont include -v the command only displays enabled user accounts.
For example, enter the following command to disable user account 34:
clia user enable 34 0
Changing a user account user name

Use the following command syntax to change a user account user name:
clia user name <user_id> <new_user_name>
Where <user_id> is the user account user ID and <new_user_name> is the new user name.

61
Shelf Manager CLI
For example, enter the following command to change the user name of user account 2 to new-name:
clia user name 2 new-name
Changing a user account password

Use the following command syntax to change a user account password:
clia user passwd <user_id> <new_password>
Where <user_id> is the user account ID and <new_password> is the new password.
For example, enter the following command to change the user name of user account 6 to NEW-password:
clia user password 6 NEW-password
version
clia version
This command displays version information for the Shelf Manager software.
# clia version
Pigeon Point Shelf Manager ver. 3.4.2.4

Pigeon Point and the stylized lighthouse logo are trademarks of Pigeon Point Systems.
Copyright (c) 2002-2015 Pigeon Point Systems
All rights reserved
Build date/time: May 21 2015 08:58:21
Carrier: HPDL/COMTEL-G4
Carrier subtype: 0; subversion: 0
Cooling management: Default
Carrier Product ID: Comtel G4 ShMC Radial Rev0.3
Chassis Product ID: Comtel G4 CO14 Radial IPMB Rev 0.11
#

This section describes how to configure the shelf manager to send SNMP traps when a component of a chassis or
a board in a chassis fails or encounters a problem (for example, a temperature sensor exceeds its range). This
section describes how to configure the shelf manager to send traps when a chassis FRU changes its FRU state.
FRU state changes are listed in board on page 44.
Example SNMP configuration

This section describes how to configure a FortiGate-5000 series chassis shelf manager to send SNMP traps to an
SNMP manager. The shelf manger IP address is 172.20.120.150 and the SNMP manager IP address is
172.20.120.11. The SNMP manager does not require MIBs or any special configuration to receive traps from the
shelf manager.
62

Shelf Manager CLI
Example SNMP network configuration
FortiGate-5000
F
tiG t 5000 series
i
Chassis
Shelf Manager
IP: 172.20.120.150
SNMP Manager
IP: 172.20.120.11
MAC: 00:1A:A0:2F:BC:C6
For this example, the FortiGate-5000 series chassis is a FortiGate-5144C chassis with a FortiSwitch-5000 series
board in logical slot 1, FortiGate-5000 series boards in logical slots 6, 8, 10, and 11. The same settings will work
for a FortiGate-5140, FortiGate-5060 or FortiGate-5050 chassis after making adjustments for the slot numbers.
To configure the shelf manager to send SNMP traps you must configure shelf manager Platform Event Filtering
(PEF) to provide a mechanism for sending SNMP traps. To configure PEF you add an event filter table that sets
the events that trigger an action and the action to take. The events can be a FRU state change or a sensor alert.
The action to take is to send an SNMP trap to the SNMP server.
When a PEF triggers an alert, the shelf manager uses an Alert Policy to determine the action to take. An alert
policy is a collection of one or more alert destinations. You can create multiple alert policies and configure
multiple destinations for each policy. This section describes how to create one alert policy, called alert policy
number 5. The alert policy number is used in an Event Filter Entry to select the alert policy to use when an alert
filter matches an event.
The combination of event filter entry and alert destination are used to select a given Alert String from a set of
strings kept in the PEF configuration parameters. This enables different strings to be sent based on what event
filter was matched and where the alert is being sent.
This example configuration of an Event filter table, Alert Policy table and Alert String table sends alerts following
FRU state changes. The alerts which will be sent from the shelf manager will be SNMP traps whose format is
defined in the Platform Event Trap Format specification. The example is for alert channel 1 which is the Eth0
interface of shelf manager number 1.

63
Shelf Manager CLI
The basic requirements for configuring SNMP traps are the same for all shelf manager firmware versions.
However, some more recent versions of the shelf manager firmware support more options (for example, you can
set the Platform Event Trap (PET) Format to different levels only on some shelf manager firmware releases).
To configure the shelf manager LAN alert destination

1. Log into the shelf manager CLI.
2. Set alert type for channel 1 and destination number 2. This command sets the alert type to 0 0 0 which means an
unacknowledged PET trap, with 0 timeout and 0 retry count:
# clia setlanconfig 1 destination_type 2 0 0 0
3. Set the destination IP and MAC address, which is the IP and MAC address of the SNMP server.
# clia setlanconfig 1 destination_address 2 0 172.20.120.11 00:1A:A0:2F:BC:C6
The SNMP server can be on a different subnet. If it is on a different subnet, the MAC address in the
command should be the MAC address of the gateway that the shelf manager connects through to reach
the SNMP server.
To set the community name used in PET traps

1. Use the following command to set the community name used in PET traps. This can be any community name, the
default is public.
# clia setlanconfig 1 16 <community_name>
2. For example, use the following command to set the community name to MyCommunity
# clia setlanconfig 1 16 MyCommunity
3. You can enter the following command to confirm that the community name has been changed:
# clia getlanconfig 1
Authentication Type Support: 0x17 (None MD2 MD5 Straight Password/Key )
Authentication Type Enables:
.
.
.
Backup Gateway MAC Address: N/
Community String: "MyCommunity"
Number of Destinations: 16
.
.
.
To configure the PEF event filter table

1. Enable PEF and enter a PEF control flag:
# clia setpefconfig control 1
This command sets an 8-bit value, entered in hexadecimal and treated as a bit mask, that represents control flags
for PEF. The control value 1 enables the PEF.
2. Enable alert actions:
# clia setpefconfig action_control 1
3. An 8-bit value entered in hexadecimal and treated as a bit mask. Setting action_control to 1 enables alert actions.
64

Shelf Manager CLI
4. Delay PEF and delay alerts for 60 seconds after the system powers up:
# clia setpefconfig startup_delay 60
# clia setpefconfig alert_startup_delay 60
5. Add event filter entries. The syntax of the command is:
# clia setpefconfig event_filter <entry_number> <flter_configuration> <filter_
action> <alert_policy_number> <severity> <IPMB_address> <channel> <sensor_type>
<sensor_number> <event_type> <event_offset> 0 0 0 0 0 0 0 0 0
Each event filter command adds or edits and event filter table entry. Each entry consists of a <entry_number> and
a <filter_action> followed by 19 numeric values, in hexadecimal, encoded according to the definition in table 15-2
of the IPMI specification version 1.5 (http://download.intel.com/design/servers/ipmi/IPMIv1_5rev1_1.pdf).
l
<entry_number> is the filter entry number. Each entry must have a different number. Adding a second entry with
the same number overwrites the first entry with that number.
<filter_configuration> In this example the filter configuration is ways set to 80 to enable the filter.
<filter_action> In this example the filter action is ways set to 1 to set the action to alert.
<alert_policy_number> In this example the alert policy number is 5.
<severity> In this example the severity is 02 which means information level messages and higher can trigger
traps. Normally you would set severity to 08 for non-critical conditions, 10 for critical conditions, or 20 for nonrecoverable conditions to limit the number of traps sent.
<IPMB_address> is the IPMB address of the FRU for which the alert is generated. See IPMB addresses, logical
and physical slot numbers, and FRU ids on page 38.
<channel> is the channel to match. FF means any channel.
<sensor_type> is the type of sensor. FF means any sensor, F0 means hot swap. See Sensor types on page 43.
<sensor_number> is the number of the sensor. FF means any sensor.
<event_type> is the event or reading type. FF means any event type.
<event_offset> is the event offset mask. FF FF means any event offset mask.
0 0 0 0 0 0 0 0 0 are additional settings to add granularity and boolean logic for selecting particluar events.
In this example they are all set to 0 which means they have no effect.
Add filter entry 1 for the FortiSwitch board in logical slot 1. The filter entry uses filter configuration 80, sets the
action to alert (1), references alert policy 5, sets the severity level to 02, is for IPMB address 82 (the first hub slot),
any channel (FF), is for the hot swap sensor (F0), is for any sensor number (FF), any sensor offset (FF), any event
type (FF), and any event offset (FF).
clia setpefconfig event_filter 1 80 1 5 02 82 FF F0 FF FF FF FF 0 0 0 0 0 0 0 0 0
Add filter entry 6 for the FortiGate-5005FA2 board in logical slot 6. The filter entry uses filter configuration 80,
sets the action to alert (1), references alert policy 5, sets the severity level to 02, is for IPMB address 8C (physical
slot 10 in a 5144C chassis), any channel (FF), is for any sensor (FF), is for any sensor number (FF), any sensor
offset (FF), any event type (FF), and any event offset (FF).
clia setpefconfig event_filter 6 80 1 5 02 8C FF FF FF FF FF FF 0 0 0 0 0 0 0 0 0
Add filter entry 8 for the FortiGate board in logical slot 8. The filter entry uses filter configuration 80, sets the
action to alert (1), references alert policy 5, sets the severity level to 02, is for IPMB address 90 (physical slot 10 in
a FortiGate-5144C chassis), any channel (FF), is for the hot swap sensor (F0), is for any sensor number (FF), any
sensor offset (FF), any event type (FF), and any event offset (FF)
clia setpefconfig event_filter 6 80 1 5 02 8C FF FF FF FF FF FF 0 0 0 0 0 0 0 0 0
Add filter entry 10 for the FortiGate board in logical slot 10 (IPMB address 94).
clia setpefconfig event_filter 10 80 1 5 02 94 FF FF FF FF FF FF 0 0 0 0 0 0 0 0 0
Add filter entry 11 for the FortiGate board in logical slot 11 (IPMB address 96).

65
Shelf Manager CLI
Add filter entry 20 for the FRUs at IPMB address 20 (PEMs, Fans, etc)
To configure the alert policy and string tables

1. Set alert policy table entry 8 with alert policy number 5, policy enabled, alert always sent, destination channel 1,
destination address 2 and alert string selector 7
clia setpefconfig alert_policy 8 5 8 1 2 7
2. Set the alert string selector 7 equal to test alert message.
clia setpefconfig alert_string 7 test alert message
Testing the configuration

A simple test of the configuration to make sure the SNMP manager can receive traps. Since in most cases in this
example the event filter is set for any channel and any sensor any simple state change should trigger a trap. The
following steps show to enter a command to deactivate selected FRUs which will result in a trap being sent.
The format of SNMP traps produced by the shelf manager is specified in the IPMI Platform Event Trap Format
Specification v1.0 document (http://download.intel.com/design/servers/ipmi/PET100.pdf).
Enter the following command to view the state of PEM 1 in a FortiGate-5000 series chassis.
# clia fru 20 7
0: FRU # 7
Entity: (0x15, 0x60)
Hot Swap State: M4 (Active), Previous: M3 (Activation In Process), Last State
Change Cause: Normal State Change (0x0)
Device ID String: "PEMA1"
Enter the following command to deactivate this PEM:
# clia deactivate 20 7
Enter the following command to display the system event log.

# clia sel
0x0001: Event: at Jul
event:0x6f(asserted):
8 17:12:21 2008; from:(0x20,0,0);

HotSwap: FRU 7 M4->M6, Cause=0x1
8 17:12:21 2008; from:(0x20,0,0);
0xC4 0x01 0x00
8 17:12:21 2008; from:(0x20,0,0);
HotSwap: FRU 7 M6->M1, Cause=0x0
8 17:12:21 2008; from:(0x20,0,0);
0xC4 0x01 0x00
sensor:(0xf0,9);
sensor:(0x12,133);
sensor:(0xf0,9);
sensor:(0x12,133);
The event log shows two state changes: M4 -> M6 -> M1 Two SNMP traps are generated.
Enter the following command to re-activate this PEM:
# clia activate 20 7
As PEM B is activating, there are three state changes (M1 -> M2 -> M3 -> M4) and three traps sent.
SNMP trap details

The trap below could be sent when PEM B state changes from M4 to M6. The important trap fields are the
specific trap field (in red below) and the variable bindings fields (in blue). Byte 2 of the specific trap field shows the
sensor type (f0 = hot swap) and the 4th byte is the event offset (06 = assertion to state 6= M6).
66

Shelf Manager CLI
The variable bindings fields which are in bold in the trace below are the following bytes:
l
Byte 26 = Event Source Type = Class of device or type of software that originated the event
Byte 27 = Event Severity
Byte 28 = Sensor Device byte = Identifies the instance of the device that holds the sensor that generated the event
Byte 29 = Sensor Number
Sensor number 9 is the hot swap sensor for PEM B:

# clia sensor 20 9
20: LUN: 0, Sensor # 9 ("FRU 7 HOT_SWAP")
Type: Discrete (0x6f), "Hot Swap" (0xf0)
Belongs to entity: (0xa, 97) [FRU # 7]
No. Time Source Destination Protocol Info
1 17:11:21.469567 192.168.181.66 192.168.182.86 SNMP trap
Frame 1 (177 bytes on wire, 177 bytes captured)
Ethernet II, Src: RapidCit_5f:cc:97 (00:e0:16:5f:cc:97), Dst: Vmware_3c:55:c0
(00:0c:29:3c:55:c0)
Destination: Vmware_3c:55:c0 (00:0c:29:3c:55:c0)
Source: RapidCit_5f:cc:97 (00:e0:16:5f:cc:97)
Type: IP (0x0800)
Internet Protocol, Src: 192.168.181.66 (192.168.181.66), Dst: 192.168.182.86
(192.168.182.86)
User Datagram Protocol, Src Port: 1024 (1024), Dst Port: snmptrap (162)
Simple Network Management Protocol
version: version-1 (0)
community: public
data: trap (4)
trap
enterprise: 1.3.6.1.4.1.3183.1.1 (SNMPv2-SMI::enterprises.3183.1.1)
agent-addr: internet (0)
internet: 192.168.181.66 (192.168.181.66)
generic-trap: enterpriseSpecific (6)
specific-trap: 15757062
time-stamp: 1975765011
variable-bindings: 1 item
Item
name: 1.3.6.1.4.1.3183.1.1.1 (SNMPv2-SMI::enterprises.3183.1.1.1)
valueType: value (0)
value: simple (4294967295)
simple: string-value (1)
Value: Hex-STRING: 54 FA FC B6 41 50 11 DD 00 80 00 50 C2 3F F0 9A 00 4F
13 C8 C3 75 00 00 20 20 02 20 09 00 00 A6 14 07 00 00 00 00 00 19 0A
40 00 00 00 00 80 53 01 74 65 73 74 20 61 6C 65 72 74 20 6D 65 73 73
61 67 65 00 C1
Packet bytes :
0000 00 0c 29 3c 55 c0 00 e0 16 5f cc 97 08 00 45 00 ..)<U...._....E.
0010 00 a3 00 00 40 00 3e 11 4f 60 c0 a8 b5 42 c0 a8 ....@.>.O`...B..
0020 b6 56 04 00 00 a2 00 8f 6a 28 30 81 84 02 01 00 .V......j(0.....
0030 04 06 70 75 62 6c 69 63 a4 77 06 09 2b 06 01 04 ..public.w..+...
0040 01 98 6f 01 01 40 04 c0 a8 b5 42 02 01 06 02 04 ..o..@....B.....
0050 00 f0 6f 06 43 04 75 c3 c8 13 30 55 30 53 06 0a ..o.C.u...0U0S..
0060 2b 06 01 04 01 98 6f 01 01 01 04 45 54 fa fc b6 +.....o....ET...
0070 41 50 11 dd 00 80 00 50 c2 3f f0 9a 00 4f 13 c8 AP.....P.?...O..
0080 c3 75 00 00 20 20 02 20 09 00 00 a6 14 07 00 00 .u.. . ........
0090 00 00 00 19 0a 40 00 00 00 00 80 53 01 74 65 73 .....@.....S.tes
00a0 74 20 61 6c 65 72 74 20 6d 65 73 73 61 67 65 00 t alert message.

67
Shelf Manager CLI
00b0 c1
Some releases of the Shelf Manager allow selecting between three PET formats. The values are defined as
follows:
0 = the default IPMI format defined by IPMI Platform Event Trap Format v1.0 specification.
1 = plain text format; all the event details are sent as plain ASCII text in a single variable.
2 = multi-variable format; each event field is encoded as a separate variable
Removing and inserting a fan tray

You could also test traps by removing and then inserting fan tray 1.Removing a fan tray causes a state change
(M4 -> M7) and a SNMP trapis sent with byte 4 of specific trap field = 07. Byte 29 of variable binding fields equal
to 06 = FRU 4 hot swap sensor.
# clia fru 20 4
20: FRU # 4
Entity: (0x1e, 0x61)
Cause: Normal State Change (0x0)
Device ID String: "Fan Tray 1"
# clia sensor 20 6
Belongs to entity: (0x1e, 97) [FRU # 4]
When inserted, there are 4 state changes and 4 SNMP traps sent.

To allow an SNMP manager to poll (monitor) the shelf manager you need to change the community strings in the
shelf manager SNMP configuration file (snmpd.conf). Change them to the community strings used by your
organization or SNMP manager. Once you change the community strings in the configuration file you must also
restart the shelf manager snmpd process.
To change the shelf manager SNMP community strings

1. Log into the shelf manager CLI.
2. Use the vi editor to edit the snmp.conf file. Enter the command:
vi snmpd.conf
3. Scroll down to the part of the file that is similar to the following:
# First, map "public" community name (COMMUNITY) into a security name
# (local and mynetwork, depending on where the request is coming from):
#
# sec.name source community
com2sec local localhost yourwritecommunity
com2sec mynetwork default yourreadcommunity
4. Change yourwritecommunity and yourreadcommunity to your write and read community strings.
5. enter :wq to save the file and quit the vi editor.
68

Shelf Manager CLI
To restart the shelf manager snmpd process

1. Enter the following command to list all processes running on the shelf manager:
ps
2. Search the output for a line that contains snmpd -c /etc/snmpd.conf. For example:
930 root 2264 S snmpd -c /etc/snmpd.conf
3. Enter the following command to stop this process:
kill -9 930
In this example, the ID of the process to be stopped is 930. On your shelf manager the process ID will most likely
be different.
4. Enter the following command to restart the snmpd process:
# daemon -f snmpd -c /etc/snmpd.conf
5. To confirm that the process has restarted enter the ps command again and confirm that the snmpd process is in
the list.
6. Use an SNMP manager or any tool that can send SNMP queries (for example iReasoning or Wireshark) to verify
that the shelf manager can respond to SNMP polling requests using the configured community strings.

The chassis system event log (SEL) records all system events and this section describes how to read and interpret
the SEL.
Before you begin

Before going further in this section, you should log into your active shelf manager and enter the following
commands. This will be a good reference for what you physically have in your system and will help with
understanding other areas of this section.
#
#
#
#
clia
clia
clia
clia
ipmc
fru
sensor
sel
Chassis Design Background

All the devices in an ATCA chassis are controlled and monitored through an Intelligent Platform Management
Controllers (IPMC). Each shelf manager and all ATCA boards have their own physical IPMC chip and are
assigned an IPMC address. Their unique address is assigned based on what chassis slot they are physically
inserted into. Additionally, there is a reserved logical chassis IPMC address of 20 hex which is created and
controlled by the active shelf manager.
l
Shelf Manager slot 1 = IPMC address 10
Shelf Manager slot 2 = IPMC address 12
ATCA slot 1 = IPMC address 82
ATCA slot 14 = IPMC address 9C
Logical IPMC from Active Shelf Manager = IPMC address 20

The IPMC connects to and monitors the readings on various sensors located on devices in the system. These
devices are typically called FRUs. The term FRU generally refers to any removable or field replaceable component,

69
Shelf Manager CLI
but in a more technical view can be any unique device in the system even if it is not removable, such as a
backplane.
l
FortiGate-5001A in ATCA slot 1 = (IPMC 82) FRU 0
Shelf Manager in SM slot 1 = (IPMC 10) FRU 0
Shelf Manager in SM slot 2 = (IPMC 12) FRU 0
All the other FRU devices that make up a chassis are referenced through the logical IPMC address 20.
Fan Tray 1 = (IPMC 20) FRU 3
Fan Tray 2 = (IPMC 20) FRU 4
PEM1 (A1) = (IPMC 20) FRU 7
See IPMB addresses, logical and physical slot numbers, and FRU ids on page 38 for a complete list.
The sensors on the various FRUs report back to their respective IPMC. Sensors connected to chassis FRU
devices like the fan trays or power entry modules can report back their sensor readings through either IPMC
10h/12h or through the Logical 20h address, but not both. Sensors on ATCA boards always report back through
their respective blade IPMC address.
l
Backup battery voltage sensor on SM1 = (IPMC 10) Sensor #6
RPM of fan 1 of 2 in Fan Tray 0 = (IPMC 10) Sensor #7
RPM of fan 2 of 2 in Fan Tray 2 = (IPMC 10) Sensor #14
Physical presence of Fan Tray 2 = (IPMC 20) Sensor #14
Chassis center exhaust temperature = (IPMC 20) sensor #120
Slot 1 FG-5005FA2 ambient incoming temp = (IPMC 82) Sensor #12
You can check the IPMB bus state (if the bus it in failure, nothing works). A backup bus exists so there are 2 IPMB
buses handled by the active shelf manager (and not one bus per shelf manager). Use the following command to
check the IPMB bus state:
# clia getipmbstate 10
10: Link: 0, LUN: 0, Sensor # 1 ("IPMB LINK")
Bus Status: 0x8 (IPMB-A Enabled, IPMB-B Enabled)
IPMB A State: 0x08 (LocalControl, No failure)
IPMB B State: 0x08 (LocalControl, No failure)
Alarm LEDs
Alarms are also reported by LEDs on the chassis shelf alarm panel or shelf manager. FRUs such as fan trays and
PEMs also have alarm LEDs. So for example, if a FAN goes into an alarm state, the alarm LED located on the
FAN turns to RED.
Reading the SEL

Every time an event occurs in a chassis, the respective IPMC controller sends notification to the shelf manager
that the event has happened and an entry is added to the SEL. The log entry that is created depends on the
sensor that triggered the event and the type of data that the sensor reads.
All events are logged, this includes normal system events as well as alarms and critical events. For example,
insertion a board generate a number of event log messages because the board is now present, has notified the
shelf manager that its ready to work, that its received the command to power up into operational mode, and that
70

Shelf Manager CLI
its now active in the chassis. This is seen as clustered entries in the SEL where the same IPMC moves from M0M1 all the way up to M3-M4, where M4 is fully operating.
Alarm events such as fans starting to spin at slower rates due to age, or dips in the -48VDC power input or even
blown fuses are also added to the SEL.
The following example event log entry records that the rear fan in Fan Tray 1 (middle fan tray) is spinning below
the required RPM rate.
0x018D: Event: at Jan 1 00:02:15 1970; from:(0x10,0,0); sensor:(0x04,10); event:0x1
(asserted): "Upper Critical", Threshold: 0xff, Reading: 0xff
Where:
l
l
l
0x018D The event ID, every new event increments by 1h. So the next event in the log file will be tagged with
0x018E. You can use this to keep track of what line you are on in the file.
Event: at Jan 1 00:02:15 1970; The date and time that the event occurred.
from:(0x10,0,0); In this string, 0x10 is the IPMC controller to which the sensor is attached. In this message its
referencing an event monitored by the shelf manager in slot #1.
sensor:(0x04,10); The first part 0x04 can be ignored, the 10 shows the ID of the Sensor that generated the
alarm.
event:0x1(asserted): Sensors show when an event is triggered because of something going wrong, but also
when they return to normal. In this case, asserted is the key point, meaning that the sensor has observed that the
device has gone outside the bounds or thresholds that have been set for it. Had this contained deasserted it would
mean the device has returned to its normal operating mode.
Upper Critical", Threshold: ss a reference to the specific threshold level that the device exceeded. Some
events like thermal events could have multiple threshold levels. The first event could simply notify the shelf
manager that its getting too hot, to which the shelf manager would then notify the fans in the system to speed up to
help cool the board better, at which point the sensor would deassert the event. Another, higher level thermal event
could notify the shelf manager that the board has now exceeded its maximum thermal operating limit, to which the
shelf manager would tell it to deactivate and shut down.
Reading: 0xff represents a raw value sent with the event, typically for more technical troubleshooting review by
the manufacturer. Data is rarely published for these values.
Reviewing the SEL messages from the IPMC, FRU and Sensor commands will show you exactly what devices are
in your chassis, what the FRU IDs are for the devices that connect to them, and all the sensor numbers that each
of these devices contain. You should be able to no identify the vast majority of both good and bad events that
have happened to your chassis and blades.
For more advanced users you can try using v after many of the Shelf Manager commands or running the
sensordata, Threshold, and Fruinfo commands to get more detailed information on each sensor and
FRU device.
Clearing SEL logs

Use the following command to clear SEL logs:
# clia sel clear
Example IPMC log output

clia ipmc

71
Shelf Manager CLI
10: Entity: (0xf0, 0x60) Maximum FRU device ID: 0x00

PICMG Version 2.3
Device ID: 0x07, Revision: 0, Firmware: 3.40 (ver 3.4.0), IPMI ver 2.0
20: Entity: (0xf0, 0x1) Maximum FRU device ID: 0x0a
PICMG Version 2.3
Device ID: 0x07, Revision: 0, Firmware: 3.40 (ver 3.4.0), IPMI ver 2.0
Hot Swap State: M7 (Communication Lost), Previous: M4 (Active), Last State Change
Cause: Unknown (0xf)
8a: Entity: (0xa0, 0x60) Maximum FRU device
Hot Swap State: M7 (Communication Lost),
State Change Cause: Unknown (0xf)
8c: Entity: (0xa0, 0x60) Maximum FRU device
Hot Swap State: M7 (Communication Lost),
ID: 0x00
Previous: M6 (Deactivation In Progress), Last
ID: 0x00
Previous: M4 (Active), Last State Change
8e: Entity: (0xa0, 0x60) Maximum FRU device ID: 0x00

Hot Swap State: M7 (Communication Lost), Previous: M5 (Deactivation Request), Last
9a: Entity: (0xa0, 0x60) Maximum FRU device ID: 0x00
Hot Swap State: M7 (Communication Lost), Previous: M5 (Deactivation Request), Last
9c: Entity: (0xa0, 0x60) Maximum FRU device ID: 0x00
72

Shelf Manager CLI
Example FRU log output

# clia fru
10: FRU # 0
Entity: (0xf0, 0x60)
Device ID String: "Carrier_FRU"
20: FRU # 0
Entity: (0xf0, 0x1)
Device ID String: "PPS BMC"
20: FRU # 1
Device ID String: "ShelfFRU1"
20: FRU # 2
Device ID String: "ShelfFRU2"
20: FRU # 3
Device ID String: "FanTray1"
20: FRU # 4
20: FRU # 5
20: FRU # 6
20: FRU # 7

73
Shelf Manager CLI

20: FRU # 8
20: FRU # 9
Device ID String: "PEMB1"
20: FRU # 10
Device ID String: "PEMB2"
Example sensor log output

# clia sensordata

Belongs to entity (0xf0, 96): [FRU # 0]
10: LUN: 0, Sensor # 1 ("IPMB LINK")
Type: Discrete (0x6f), "IPMB Link" (0xf1)
10: LUN: 0, Sensor # 2 ("Local Temp")
10: LUN: 0, Sensor # 3 ("IPMB CROSS LINK")
10: LUN: 0, Sensor # 128 ("HWRI State")
Type: Discrete (0x6f), "OEM reserved" (0xde)
10: LUN: 0, Sensor # 129 ("Reboot Reason")
Type: Discrete (0x6f), "OEM reserved" (0xdd)
10: LUN: 0, Sensor # 230 ("Eth Switch Link2")
Type: Discrete (0x6f), "Entity Presence" (0x25)
74

Shelf Manager CLI

10: LUN: 0, Sensor # 234 ("I2C Switch Ch1 i")
10: LUN: 0, Sensor # 240 ("Shelf BP ID")
Type: Discrete (0x6f), "OEM reserved" (0xd6)
10: LUN: 0, Sensor # 250 ("SDR Rev 0.21 HPD")
# clia sensor 20
20: LUN: 3, Sensor # 0 ("HPI Sys Event")
Type: Discrete (0x6f), "OEM reserved" (0xdb)

75
Shelf Manager CLI

Belongs to entity (0x1e, 96): [FRU # 3]
Belongs to entity (0x15, 96): [FRU # 7]
20: LUN: 0, Sensor # 12 ("IPMB LINK 1")
76

Shelf Manager CLI

20: LUN: 0, Sensor # 119 ("TelcoAlarmInput")
Type: Discrete (0x6f), "TELCO Alarm Input" (0xf4)
20: LUN: 0, Sensor # 131 ("TELCO Alarms")
Type: Discrete (0x6f), "OEM reserved" (0xdf)
20: LUN: 0, Sensor # 132 ("BMC Watchdog")
Type: Discrete (0x6f), "Watchdog 2" (0x23)
20: LUN: 0, Sensor # 133 ("SYSTEM EVENT")

77
Shelf Manager CLI
Type: Discrete (0x6f), "System Event" (0x12)

20: LUN: 0, Sensor # 135 ("FT Oper.Status")
Type: Discrete (0x0b), "Management Subsystem Health" (0x28)
20: LUN: 0, Sensor # 136 ("Cooling State")
Type: Discrete (0x07), "Management Subsystem Health" (0x28)
20: LUN: 0, Sensor # 137 ("Fans State")
Type: Discrete (0x07), "Management Subsystem Health" (0x28)
20: LUN: 0, Sensor # 138 ("SHM Redundancy")
Type: Discrete (0x0b), "Management Subsystem Health" (0x28)
20: LUN: 1, Sensor # 141 ("FT1 Power Good")
20: LUN: 1, Sensor # 142 ("FT1 Feed1 Power ")
20: LUN: 1, Sensor # 144 ("FT1 Feed1 Fuse P")
20: LUN: 1, Sensor # 146 ("FT1 FW Rev")
20: LUN: 1, Sensor # 147 ("FT1 AUX Rev")
78

Shelf Manager CLI

20: LUN: 0, Sensor # 160 ("PEM A1 Temperatu")
20: LUN: 0, Sensor # 161 ("PEM A1 FuseFeed1")

79
Shelf Manager CLI

20: LUN: 0, Sensor # 165 ("PEM A1 In1_4 48V")
20: LUN: 0, Sensor # 166 ("PEM A1 Rev.In1_4")
80

Shelf Manager CLI

20: LUN: 0, Sensor # 179 ("PEM A1 Presence")
20: LUN: 0, Sensor # 180 ("PEM A1 Temperatu")
20: LUN: 0, Sensor # 200 ("PEM B1 Temperatu")

81
Shelf Manager CLI

20: LUN: 0, Sensor # 201 ("PEM B1 FuseFeed1")
20: LUN: 0, Sensor # 205 ("PEM B1 In1_4 48V")
20: LUN: 0, Sensor # 206 ("PEM B1 Rev.In1_4")
20: LUN: 0, Sensor # 218 ("Intake Temperatu")
20: LUN: 0, Sensor # 219 ("PEM B1 Presence")
20: LUN: 0, Sensor # 220 ("PEM B2 Temperatu")
82

Shelf Manager CLI

20: LUN: 1, Sensor # 225 ("FT1 Presence")

83
Shelf Manager CLI

20: LUN: 1, Sensor # 232 ("AirFilter Presen")
20: LUN: 0, Sensor # 235 ("FAN1 Exhaust Tem")
20: LUN: 1, Sensor # 238 ("FT1 ESTD")
20: LUN: 0, Sensor # 240 ("FAN1 RPM")
Type: Threshold (0x01), "Fan" (0x04)
84

Shelf Manager CLI

20: LUN: 1, Sensor # 242 ("FT1 INIT")
20: LUN: 1, Sensor # 244 ("FT1 WDT STAT")
20: LUN: 1, Sensor # 246 ("FT1 WDT RES")

85
Shelf Manager CLI

20: LUN: 1, Sensor # 248 ("FT1 COMM LOST")
20: LUN: 0, Sensor # 250 ("SDR Rev 07.G HPD")
20: LUN: 1, Sensor # 252 ("FT1 PWM POL")
Sample sections of SEL Output

The active shelf manager moving from M0 to M4 state (active and working):
0x0285: Event: at Jan 1 00:01:46 1970;
0x0286: Event: at Jan 1 00:01:51 1970;
0x0287: Event: at Jan 1 00:01:51 1970;
86

Cause=0x0
Cause=0x2
Cause=0x1

Shelf Manager CLI
0x0288: Event: at Jan 1 00:01:52 1970; from:(0x20,0,0); sensor:(0xf0,0); event:0x6f

(asserted): HotSwap: FRU 0 M3->M4, Cause=0x0
Fan #2 in middle Fan Tray is spinning slower than required:

0x018D: Event: at Jan 1 00:02:15 1970; from:(0x10,0,0); sensor:(0x04,10); event:0x1
(asserted): "Upper Critical", Threshold: 0xff, Reading: 0xff
A low voltage warning on the backup battery on shelf manager 1:

0x022C: Event: at Jan 1 23:09:06 2010; from:(0x10,0,0); sensor:(0x02,6); event:0x1
(asserted): "Lower Critical", Threshold: 0xb3, Reading: 0x99
The board in ATCA slot 4 has exceeded the incoming air temperature limit:
0x0080: Event: at Jan 1 00:25:25 1970; from:(0x8e,0,0); sensor:(0x01,12); event:0x1
(asserted): "Upper Critical", 0x09 0xFF 0xFF
The board in ATCA slot 4 has exceeded the CPU board temperature limit:
0x0081: Event: at Jan 1 00:30:40 1970; from:(0x8e,0,0); sensor:(0x01,13); event:0x1
(asserted): "Upper Critical", 0x09 0xFF 0xFF

87
Regulatory notices, cautions and warnings

Federal Communication Commission (FCC) USA
This device complies with Part 15 of FCC Rules. Operation is subject to the following two conditions:
(1) this device may not cause harmful interference, and
(2) this device must accept any interference received; including interference that may cause undesired operation.
This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to Part
15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference
when the equipment is operated in a commercial environment. This equipment generates, uses, and can radiate
radio frequency energy, and if it is not installed and used in accordance with the instruction manual, it may cause
harmful interference to radio communications. Operation of this equipment in a residential area is likely to cause
harmful interference, in which case the user will be required to correct the interference at his own expense.
WARNING: Any changes or modifications to this product not expressly approved by the party responsible for
compliance could void the users authority to operate the equipment
Industry Canada Equipment Standard for Digital Equipment (ICES) Canada

CAN ICES-3 (A) / NMB-3 (A)
This digital apparatus does not exceed the Class A limits for radio noise emissions from digital apparatus set out
in the Radio Interference Regulations of the Canadian Department of Communications.
Le prsent appareil numrique nemet pas de bruits radiolectriques dpassant les limites applicables aux
appareils numeriques de la classe A prscrites dans le Rglement sur le brouillage radiolectrique dicte par le
ministre des Communications du Canada.
Voluntary Control Council for Interference (VCCI) Japan
Bureau of Standards Metrology and Inspection (BSMI) Taiwan
China
European Conformity (CE) - EU

This is a Class A product. In a domestic environment, this product may cause radio interference, in which case
the user may be required to take adequate measures.
Environmental specifications
Operating Temperature If this device is installed in a closed or multi-unit rack assembly, the racks ambient
temperature may be greater than the rooms ambient temperature. Make sure the rack environment is
compatible with the manufacturers maximum rated ambient temperature (Tma).
Temprature ambiante leve Si cet appareil est install dans un cabinet ferm, la temprature ambiante
du cabinet peut tre suprieure la temprature ambiante de la pice. Assurez- vous que lenvironnement dans
le cabinet est compatible avec la temprature ambiante maximale du fabricant (Tma).
Air flow For rack installation, make sure that the amount of air flow required for safe operation of the
equipment is not compromised. For free-standing installation, make sure that the appliance has at least 2 inches
(5 cm) of clearance on each side to allow for adequate air flow and cooling.
Ventilation Pour une installation dans un cabinet, assurez-vous que la ventilation ncessaire au
fonctionnement de lquipement nest pas compromise. Pour une installation autonome, assurez-vous que
lappareil dispose dau moins 2 pouces (5 cm) de dgagement de chaque ct pour permettre lcoulement de
lair et un refroidissement adquat.
Circuit overloading To avoid overloading, use the ratings on the label. Consider the equipments connection
to the supply circuit and the effect that circuit overloading might have on current protection and supply wiring.
For redundant power sources, connect each to an IEC/UL Listed power source whose output rating is greater than
or equal to the equipment.
Surtension Pour viter de surcharger le circuit dalimentation, rfrez-vous aux notes sur ltiquette de
lquipement . Envisagez leffet que la surtension du circuit pourrait avoir sur la protection de surtension et le
cblage dalimentation .
Considration approprie du marquage de la plaque signaltique doit tre utilise lorsqu'il est question de cette
proccupation. Pour les sources d'alimentation redondantes, connectez chacun une source d'alimentation Mis
CEI / UL dont la cote de rendement est suprieur ou gal l'quipement.
Reliable earthing Make sure all rack-mounted equipment is grounded. This includes supply connections (e .g .
power strips), not only direct connections to the branch circuit.
Mise la terre Assurez-vous que tout lquipement est mis la terre . Ceci comprend les connexions
dalimentation (par exemple, les barres dalimentation) en plus des connexions directes au circuit de drivation.
Interference If possible, use Shielded Twisted Pair (STP) Ethernet cables instead of Unshielded Twisted Pair
(UTP).
Interfrence Si possible, utilisez des cbles Ethernet de paire torsade blinde (STP) plutt que de paire
torsade non blinde (UTP).
Mechanical loading To avoid personal injury or damage to the appliance, Fortinet recommends that 2 or
more people together install the appliance into the rack. Balance the equipment to avoid uneven mechanical
loading and tipping. Do not place heavy objects on the appliance.
Installation Pour viter des blessures ou des dommages lappareil, Fortinet recommande que deux
personnes ou plus installent ensemble cet quipement dans un cabinet. Linstallation du matriel lintrieur de
la baie doit tre effectue de faon viter toute situation dangereuse lie une installation non conforme . Ne
placez pas dobjets lourds sur lappareil, celui-ci ntant pas conu pour soutenir un poids additionnel.
Blade Carriers, Cards and Modems must be Listed Accessories or Switch, Processor, Carrier and similar blades or
cards should be UL Listed or Equivalent.
Serveur-blades, cartes et modems doivent tre Listed Accessories ou Commutateurs, Processeurs, Serveurs
et similaire blades ou cartes doivent tre UL Listed or quivalent.
Refer to specific Product Model Data Sheet for Environmental Specifications (Operating Temperature, Storage
Temperature, Humidity, and Altitude)
Safety
Moving parts Hazardous moving parts. Keep away from moving fan blades.
Pices mobiles Pices mobiles dangerouses. Se tenir loign des pales de ventilateurs mobiles.
Do not install this equipment in a home or public area accessible to the general population. When installed in
schools, this equipment must be installed in a location where access is restricted to trained personnel.
Dans les coles, ce matriel doit tre install en lieu sr, de faon le rendre accessible seulement aux
personnels qualifies.
For DC installations, a readily accessible UL Listed disconnect device (e.g. circuit breaker) with over current
protection suitable for local code must be incorporated in the building installation wiring. Equipment is intended
for installation in Restricted Access Location. For your safety, qualified service personnel must permanently
connect the earthing terminal to the ground using a green-with-yellow conductor, minimum size #8AWG.
En cas dalimentation en courant continu (DC en anglais), un dispositif facilement accessible de dconnexion UL
(par exemple, disjoncteur) avec protection contre les surintensits adapt la rglementation locale doit tre
incorpor dans linstallation lectrique du btiment. La borne de mise la terre doit tre en permanence relie au
conducteur rayure verte et jaune de taille minimum #8AWG. Seul un technicien qualifi est autoris effectuer
le raccordement.
Caution: Disconnect power supply cords before servicing

Attention: Dbranchez les cordons de la source dalimentation avant tout entretien.
Grounding To prevent damage to your equipment, connections that enter from outside the building should
pass through a lightning / surge protector, and be properly grounded. Use an electrostatic discharge workstation
(ESD) and/or wear an anti-static wrist strap while you work. In addition to the grounding terminal of the plug, on
the back panel, there is another, separate terminal for earthing.
Mise la terre Pour viter dendommager votre matriel, assurez-vous que les branchements qui entrent
partir de lextrieur du btiment passent par un parafoudre / parasurtenseur et sont correctement mis la terre.
Utilisez un poste de travail de dcharge lectrostatique (ESD) et / ou portez un bracelet anti-statique lorsque vous
travaillez. Ce produit possde une borne de mise la terre qui est prvu larrire du produit, ceci sajoute la
mise la terre de la prise.
This product has a separate protective earthing terminal provided on the back of the product in addition to the
grounding terminal of the attachment plug. This separate protective earthing terminal must be permanently
connected to earth with a green with yellow stripe conductor minimum size # 8AWG and the connection is to be
installed by qualified service personnel.
Ce produit possde une borne de mise la terre qui est prvu larrire du produit, ceci sajoute la mise la
terre de la prise. Cette sparation protge la borne de mise la terre qui doit tre en permanence relie au
conducteur rayure verte et jaune de taille minimum #8AWG. Seul un technicien qualifi est autoris effectuer
le raccordement.
Caution: Double pole/neutral fusing

Attention: fusion bipolaire/neutre.
Turning off all power switches may not turn off all power to the FortiGate-5000 series equipment. Some circuitry
in the FortiGate-5000 series equipment may continue to operate even though all power switches are off.
FortiGate-5000 equipment must be protected by a readily accessible disconnect device or circuit breaker that can
be used for product power down emergencies.
Many FortiGate-5000 components are hot swappable and can be installed or removed while the power is on. But
some of the procedures in this document may require power to be turned off and completely disconnected.
Follow all instructions in the procedures in this document that describe disconnecting FortiGate-5000 series
equipment from power sources, telecommunications links and networks before installing, or removing FortiGate5000 series components, or performing other maintenance tasks. Failure to follow the instructions in this
document can result in personal injury or equipment damage.
Install FortiGate-5000 series chassis at the lower positions of a rack to avoid making the rack top-heavy and
unstable.
Do not insert metal objects or tools into open chassis slots.
Electrostatic discharge (ESD) can damage FortiGate-5000 series equipment. Only perform the procedures
described in this document from an ESD workstation. If no such station is available, you can provide some ESD
protection by wearing an anti-static wrist strap and attaching it to an ESD connector such as the ESD sockets
provided on FortiGate-5000 series chassis.
Make sure all FortiGate-5000 series components have reliable grounding. Fortinet recommends direct
connections to the building ground.
If you install a FortiGate-5000 series component in a closed or multi-unit rack assembly, the operating ambient
temperature of the rack environment may be greater than room ambient. Make sure the operating ambient
temperature does not exceed Fortinets maximum rated ambient temperature.
Installing FortiGate-5000 series equipment in a rack should be such that the amount of airflow
required for safe operation of the equipment is not compromised. See Cooling fans, cooling air flow,
and minimum clearance on page 25 for details.
FortiGate-5000 series equipment shall be installed and connected to an electrical supply source in accordance
with the applicable codes and regulations for the location in which it is installed. Particular attention shall be paid
to use of correct wire type and size to comply with the applicable codes and regulations for the
installation/location. Connection of the supply wiring to the terminal block on the equipment may be
accomplished using Listed wire compression lugs, for example, Pressure Terminal Connector made by Ideal
Industries Inc. or equivalent which is suitable for AWG-8. Particular attention shall be given to use of the
appropriate compression tool specified by the compression lug manufacturer, if one is specified.
Install FortiGate-5000 series equipment located in a restricted access location where only crafts personnel are
allowed access.
WARNING: The intra-building ports, Gigabit Ethernet, RJ-45 10/100/1000 Base-T Ethernet, and RS-232 Serial
ports of any FortiGate, FortiSwitch, and FortiController 5000 Series Boards, including Shelf-Manager of the
equipment or subassembly is suitable for connection to intrabuilding or unexposed wiring or cabling only. The
intrabuilding port(s) of the equipment or subassembly MUST NOT be metallically connected to interfaces that
connect to the OSP or its wiring. These interfaces are designed for use as intra-building interfaces only (Type 2 or
Type 4 ports as described in GR-1089-CORE, Issue 6) and require isolation from the exposed OSP cabling. The
addition of Primary Protectors is not sufficient protection in order to connect these interfaces metallically to OSP
wiring.
FortiGate-5000 series chassis shall be installed and connected to the common bonding network.
FortiGate-5000 series chassis are suitable for installation in the Central Office and NEC.
The battery returns of FortiGate-5000 series chassis shall be connected as DC-I.
All bare grounding connection points to FortiGate-5000 series chassis shall be cleaned and coated with an antioxidant solution before connections are made.
All surfaces on FortiGate-5000 series chassis that are un-plated shall be brought to a bright finish and treated
with and anti-oxidant solution before connections is made.
All non-conductive surfaces on FortiGate-5000 series chassis shall be removed from all threads and connection
points to ensure electrical continuity.
Unambiguous reference to service documentation for instructions for replacement of fuses replaceable only by
service personnel.
Copyright 2016 Fortinet, Inc. All rights reserved. Fortinet, FortiGate, FortiCare and FortiGuard, and certain other marks are registered trademarks of Fortinet,
Inc., in the U.S. and other jurisdictions, and other Fortinet names herein may also be registered and/or common law trademarks of Fortinet. All other product or company
names may be trademarks of their respective owners. Performance and other metrics contained herein were attained in internal lab tests under ideal conditions, and
actual performance and other results may vary. Network variables, different network environments and other conditions may affect performance results. Nothing herein
represents any binding commitment by Fortinet, and Fortinet disclaims all warranties, whether express or implied, except to the extent Fortinet enters a binding written
contract, signed by Fortinets General Counsel, with a purchaser that expressly warrants that the identified product will perform according to certain expressly-identified
performance metrics and, in such event, only the specific performance metrics expressly identified in such binding written contract shall be binding on Fortinet. For
absolute clarity, any such warranty will be limited to performance in the same ideal conditions as in Fortinets internal lab tests. In no event does Fortinet make any
commitment related to future deliverables, features, or development, and circumstances may change such that any forward-looking statements herein are not accurate.
Fortinet disclaims in full any covenants, representations,and guarantees pursuant hereto, whether express or implied. Fortinet reserves the right to change, modify,
transfer, or otherwise revise this publication without notice, and the most current version of the publication shall be applicable.

Fortigate 5144C CG

Enviado por

Dados do documento

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Fortigate 5144C CG

Enviado por

Direitos autorais:

Formatos disponíveis

FortiGate-5144C Chassis Guide

ENDUSER LICENSE AGREEMENT

Thursday, June 16, 2016

FortiGate-5144C hardware procedures

Power connection and configuration

Turning on FortiGate-5144C chassis power

Shelf Manager CLI

Regulatory notices, cautions and warnings

FortiGate-5144C front panel

FortiGate-5144C front panel

FortiGate-5144C Chassis Guide

FortiGate-5144C back panel

Example FortiGate-5144C front panel

Fan Tray 2 (front)

Primary Shelf Manager

Secondary Shelf Manager

FortiGate-5144C back panel

FortiGate-5144C Chassis Guide

Chassis hardware information

Example FortiGate-5144C chassis back panel

Fan Tray 3 (back)

Chassis hardware information

FortiGate-5144C Chassis Guide

Chassis hardware information

The 14U FortiGate-5144C chassis

One shelf manager installed in the front of the chassis

14 RTM air baffle slot covers installed in the RTM slots

5 spare nuts and washers for the PEM power studs

20 cage nuts with M6 screws

1 Philips No.2 screw driver

1 flat (4mm) screw driver

1 socket wrench (10mm)

Cage nut installation tool

Supported Fortinet ATCA boards

Shelf FRU data module

Supported Fortinet ATCA boards

Front Panel: 8 x 10 Gbps

FortiOS network security

FortiGate-5144C Chassis Guide

Front Panel: 2 x 10 Gbps

FortiOS network security

Chassis hardware information

Front Panel: 4 x 10 Gbps

FortiOS network security

Front Panel: 2 x 40 Gbps,

FortiOS network security

Front Panel: 8 x 10 Gbps

Content clustering with

Front Panel: 4 x 40 Gbps or

Content clustering with

Front Panel: 8 x 10 Gbps

Front Panel: 8 x 10 Gbps, or

Front Panel: 4 x 40 Gbps or

Front Panel: 2 x 100 Gbps

*Approximate values, see product datasheets for official values.

FortiGate-5144C Chassis Guide

Chassis hardware information

Physical description of the FortiGate-5144C chassis

24.44 x 19.06 x 21.63 in. (62.10 x 48.40 x 54.96 cm)

Shipping weight and size completely

165 lbs (75 kg) (36 x 31 x 27in) (91 x 78 x 69cm)

Chassis weight completely assembled with

(13 front and 14 RTM) 108 lbs (50 kg)