Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
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
FEEDBACK
Email: techdocs@fortinet.com
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
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
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
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
FortiGate-5144C Chassis
FortiGate-5144C Chassis
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).
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.
FortiGate-5144C Chassis
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.
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
FortiGate-5144C Chassis
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.
RTM
slot numbers
RTM
air baffle
slot covers
PEM 4
PEM 3
Feed B
Chassis PEM 2
ground
connector
PEM 1
Feed A
FortiGate-5144C Chassis
Shipping components
The FortiGate-5144C chassis ships pre-assembled with the following components:
l
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
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)
Accessories
l
Shelf Manager
ATCA board
Interfaces
Function
FortiGate-5001B
FortiGate-5001C
Heat
Power Used
Dissipation
(WDC)*
(BTU/hr)*
Max: 225
Ave: 187
Max: 225
Ave: 187
768
768
FortiGate-5144C Chassis
Heat
Power Used
Dissipation
(WDC)*
(BTU/hr)*
ATCA board
Interfaces
Function
FortiGate-5101C
FortiGate-5001D
FortiSwitch-5203B
FortiController-5902D
FortiSwitch-5003B
FortiController-5103B
FortiController-5903C
FortiController-5913C
Max: 236
Ave: 197
Max: 226
Ave: 189
Max: 250
Ave: 210
Max: 270
Ave: 223
Backplane switching,
FGCP HA, and extended
load balancing (ELBC)
Max: 180
Ave: 150
Session-aware load
balancing Clustering
(SLBC) and FGCP HA
Session-aware Load
Balancing Clustering
(SLBC) and FGCP HA
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
10
FortiGate-5001A
FortiCarrier-5001A
FortiGate-5005FA2
FortiGate-5001FA2
FortiGate-5001
FortiGate RTM-XB2
FortiGate RTM-XD2
FortiSwitch-5003A
FortiGate-5144C Chassis
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.
Operating environment
Power consumption
Heat Dissipation
Power input
Overcurrent Protection
Cooling Capacity
11
FortiGate-5144C Chassis
Hipot Test
EN60950-1, 1000 V
Hot Swap
Button
Fan Tray
Reset
LEDs
Button
Ethernet
Interface
Backplane
Ethernet Link LEDs
Telco Alarm
Interface
Retention
Screw
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
FortiGate-5144C Chassis
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.
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.
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
FortiGate-5144C Chassis
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.
14
FortiGate-5144C Chassis
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
disable_backplane_port disables the connection to the backplane. This option is factory set by Fortinet.
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.
State
Description
Off
Red
Off
Normal Operation.
Red
Solid Green
Blinking Green
Off
Normal operation.
Blinking Blue
Blue
Green
Blinking
ACT (Active)
15
LED
FortiGate-5144C Chassis
State
Description
Amber
Off
Green
Blinking
Amber
Off
Amber
Off
Green
Blinking
Red
Red
Amber
POWER OK
Green
Description
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)
16
FortiGate-5144C Chassis
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
FortiGate-5144C Chassis
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.
18
Pin
Descrption
MinorReset+
MinorReset-
MajorReset+
MajorReset-
CriticalAlarm - NO
Critical Alarm NC
Minor Alarm NO
10
11
Major Alarm NO
12
Major Alarm NC
13
14
Power NO
15
Power COM
FortiGate-5144C Chassis
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.
Fan 3
Fan 4
Fan 1
Fan 2
Right
Left
Back of Chassis
Front of Chassis
Front and back fan trays
!
!
19
FortiGate-5144C Chassis
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.
Description
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)
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
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
181.56 mm
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
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.
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
23
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).
24
Each PEM includes a Reverse Voltage LED that lights if you have reversed the polarity when connecting
power.
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
Input Feed
Channel
Physical Component
Logical Slot
Slot 1, Slot 2
Slot 3, Slot 4
Slot 9, Slot 7
Slot 5, Slot 6
Slot 5, Slot 3
Slot 1
Slot 8, Slot 9
Slot 2, Slot 4
Slot 6, Slot 8
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.
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.
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
State
Description
ACTIVE
Solid Green
Normal operation.
Off
Normal Operation.
Solid Red
Out of Service.
Off
Normal operation.
Blinking Blue
Blue
Off
Normal operation
Solid Red
27
LED
State
Description
Off
Normal operation.
Red
You need the following equipment to connect the primary FortiGate-5144C PEMs to DC power:
l
l
28
Chassis
Ground
Connector
(green)
Data Center
ground
connector
(Central office
ground system)
Edge
Controller
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
Edge
Controller
FortiGate-5053B
power supply
shelf
FortiGate-5053B-LC
power supply
shelf
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.
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
require one FortiGate-5053B power supply shelf connected to power feed A (PEM 1 and PEM 2). The power
supply shelf would include three PSU-5000B units and produce a total of 8175W. You can add a fourth 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 three or four power supplies.
If you are using high-line AC power, one PSU-5000B produces 2725W. Powering a chassis with 14 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 three PSU-5000B units and produce a total of 8175W. You can add a fourth 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 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.
31
The FortiGate-5053B power converter shelf should not be connected to AC power until specified in the
following procedure.
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, 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).
6. Install previously removed nuts and washers to secure the connectors.
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).
11. Install previously removed nuts and washers to secure the connectors.
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
33
Shelf ground
connector
Data Center
ground
connector
(Central office
ground system)
34
Connecting to the shelf manager CLI using the shelf manager console port
Connecting to the shelf manager CLI using a serial port and setting up passwords
IPMB addresses, logical and physical slot numbers, and FRU ids
Sensor types
Connecting to the shelf manager CLI using the shelf manager console port
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
Fortinet
RJ-45 RS232
to 9-pin
Console
Cable
To PC
RS-232
Console
Port
36
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.
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
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>
IPMB addresses, logical and physical slot numbers, and FRU ids
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
IPMB addresses, logical and physical slot numbers, and FRU ids
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
10
08
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
FRU name
PEM1 (B1)
20 FRU 9
10
PEM1 (B2)
20 FRU 10
10
82
41
84
42
86
43
88
44
8A
45
8C
46
8E
47
90
48
92
49
94
4A
96
4B
98
4C
9A
4D
9C
4E
<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
40
To display a complete list of all information enter version with no other parameters.
41
You can use the clia setlanconfig command to modify the shelf manager LAN configuration.
# clia setlanconfig
Pigeon Point Shelf Manager Command Line Interpreter
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
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
C0-FF for OEM reserved sensors (F0 is the hot swap sensor and F1 is the IPMB link sensor).
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
Pigeon Point Shelf Manager Command Line Interpreter
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
Pigeon Point Shelf Manager Command Line Interpreter
43
alarm
clia alarm [clear | info| minor | major | critical]
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
Pigeon Point Shelf Manager Command Line Interpreter
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
board
clia board [-v] [<physical-slot-address>]
44
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.
Description
M0
Not Installed
M1
Inactive
M2
Activation Request
M3
Activation in Progress
M4
FRU Active
M5
Deactivation Request
M6
Deactivation in Progress
45
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
Current Level
46
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.
fruinfo
clia fruinfo [-v] [-x]<addr> <fru_id>
=
=
=
=
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
= 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>.
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.
IP Address: 192.168.0.2
The following command also displays the IP address associated with channel 1:
# clia getlanconfig 1 3
Pigeon Point Shelf Manager Command Line Interpreter
IP Address: 192.168.0.2
48
The following command displays the subnet mask associated with channel 1:
# clia getlanconfig 1 subnet_mask
Pigeon Point Shelf Manager Command Line Interpreter
Subnet Mask: 255.255.255.0
The following command also displays the subnet mask associated with channel 1:
# clia getlanconfig 1 6
Pigeon Point Shelf Manager Command Line Interpreter
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
Pigeon Point Shelf Manager Command Line Interpreter
Default Gateway Address: 192.168.0.1
The following command also displays the default gateway IP address associated with channel 1:
# clia getlanconfig 1 12
Pigeon Point Shelf Manager Command Line Interpreter
Default Gateway Address: 192.168.0.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
Sensor number, sensor name and the LUN by which the sensor can be accessed
49
Upper Non-Recoverable Threshold, Raw Data: 0xb3 Processed data: 1.754200 Volts
90: LUN: 0, Sensor # 5 ("CPU2 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
Upper Non-Recoverable Threshold, Raw Data: 0xb3 Processed data: 1.754200 Volts
90: LUN: 0, Sensor # 6 ("+5.0V")
Type: Threshold (0x01), "Voltage" (0x02)
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")
Type: Threshold (0x01), "Voltage" (0x02)
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")
Type: Threshold (0x01), "Voltage" (0x02)
Lower Non-Critical Threshold, Raw Data: 0xbd Processed data: 2.305800 Volts
Lower Critical Threshold, Raw Data: 0xb5 Processed data: 2.208200 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 Critical Threshold, Raw Data: 0xe6 Processed data: 2.806000 Volts
Upper Non-Recoverable Threshold, Raw Data: 0xee Processed data: 2.903600 Volts
90: LUN: 0, Sensor # 9 ("+2.5V CPU 2")
Type: Threshold (0x01), "Voltage" (0x02)
Lower Non-Critical Threshold, Raw Data: 0xbd Processed data: 2.305800 Volts
Lower Critical Threshold, Raw Data: 0xb5 Processed data: 2.208200 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 Critical Threshold, Raw Data: 0xe6 Processed data: 2.806000 Volts
Upper Non-Recoverable Threshold, Raw Data: 0xee Processed data: 2.903600 Volts
90: LUN: 0, Sensor # 10 ("+1.2V 1")
Type: Threshold (0x01), "Voltage" (0x02)
Lower Non-Critical Threshold, Raw Data: 0x76 Processed data: 1.156400 Volts
Lower Critical Threshold, Raw Data: 0x71 Processed data: 1.107400 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
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
# clia help
Pigeon Point Shelf Manager Command Line Interpreter
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
53
Enter the following command to display more information about the fruinfo command:
# clia help fruinfo
Pigeon Point Shelf Manager Command Line Interpreter
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
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
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;
(asserted): HotSwap: FRU 0 M7->M4,
from:(0x86,0,0) indicates the event comes from physical slot 6 of a FortiGate chassis.
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
Pigeon Point Shelf Manager Command Line Interpreter
86: LUN: 0, Sensor # 12 ("TEMP1")
Type: Threshold (0x01), "Temperature" (0x01)
Upper Non-Critical Threshold, Raw Data: 0x28 Processed data: 40.000000 degrees C
55
Upper Critical Threshold, Raw Data: 0x32 Processed data: 50.000000 degrees C
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
(asserted): 0xA3 0x00 0x88
0x021E: Event: at Aug 6 10:39:56
(asserted): 0xA3 0x00 0x88
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
The Entity ID, Entity Instance of the related entity (the FRU device ID if the sensor is associated with a FRU)
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
Sensor number, sensor name (device ID string from the SDR) and the LUN by which the sensor can be accessed.
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
Pigeon Point Shelf Manager Command Line Interpreter
8890: LUN: 0, Sensor # 13 ("CPU Board Temp")
Type: Threshold (0x01), "Temperature" (0x01)
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>
57
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
Pigeon Point Shelf Manager Command Line Interpreter
9c: LUN: 0, Sensor # 2 ("emulated temp")
Type: Threshold (0x01), "Temperature" (0x01)
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
shmstatus
clia shmstatus [-v]
58
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
Pigeon Point Shelf Manager Command Line Interpreter
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
Unexpected deactivation
The following information is shown for each FRU considered to have a problem:
l
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
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.
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.
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
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
<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
Pigeon Point Shelf Manager Command Line Interpreter
1: ""
Channels 0-15 Privilege level: "Administrator"
Flags: "IPMI Messaging"
clia user add 9 "user_1" 0x40 4 "my-password"
Pigeon Point Shelf Manager Command Line Interpreter
User 9 added successfuly
clia user
Pigeon Point Shelf Manager Command Line Interpreter
1: ""
Channels 0-15 Privilege level: "Administrator"
Flags: "IPMI Messaging"
9: "user_1"
Channels 0-15 Privilege level: "Administrator"
Flags: "IPMI Messaging"
Deleting user accounts
For example, enter the following command to delete user account 23:
clia user delete 23
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
Where <user_id> is the user account user ID and <new_user_name> is the new user name.
61
For example, enter the following command to change the user name of user account 2 to new-name:
clia user name 2 new-name
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
62
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
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).
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.
64
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.
<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.
<sensor_type> is the type of sensor. FF means any sensor, F0 means hot swap. See Sensor types on page 43.
<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).
clia setpefconfig event_filter 11 80 1 5 02 96 FF FF FF FF FF FF 0 0 0 0 0 0 0 0 0
65
Add filter entry 20 for the FRUs at IPMB address 20 (PEMs, Fans, etc)
clia setpefconfig event_filter 20 80 1 5 02 20 FF FF FF FF FF FF 0 0 0 0 0 0 0 0 0
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.
66
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 28 = Sensor Device byte = Identifies the instance of the device that holds the sensor that generated the event
67
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
When inserted, there are 4 state changes and 4 SNMP traps sent.
68
clia
clia
clia
clia
ipmc
fru
sensor
sel
69
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
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
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
Pigeon Point Shelf Manager Command Line Interpreter
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.
70
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.
71
ID: 0x00
Previous: M6 (Deactivation In Progress), Last
ID: 0x00
Previous: M4 (Active), Last State Change
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
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
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
China
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.
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.
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.