FortiGate-7060E Management Modules

FortiGate-7060E Management Modules

The FortiGate-7060E chassis includes two hot swappable management modules (shelf managers), located at the top of the chassis front panel. The management models operate in an active-passive redundant configuration. By default, when the system starts up the management module in slot MGT2 is active and the management module in slot MGT1 is passive. The active management module always has IPMB address 0x20 and the passive management module always has IPMB address 0x22.

The management modules are hot swappable. If you remove the passive management module, or if the passive management module fails, the chassis just keeps operating with the active management module. If you remove the active management module, or if the active management module fails, the passive management module becomes active. If you insert a new management module it quietly starts up and becomes passive. The active management module synchronizes the following data to the passive management module:

l Chassis state and chassis policy l LAN parameters for each LAN channel, including, the IP address, gateway IP address, channel enable status, local interface/non-local interface setting, and the session support flag. l The console connect feature status (enable or disable).

FortiGate-7060E management module front panel

The active management module communicates with module SMCs in the chassis, each of which is responsible for local management of one or more Field Replaceable Units (FRUs), including FIM and FPM modules, fan trays, and power supplies. Management communication within a chassis occurs over the Intelligent Platform Management Bus (IPMB).

The active management module includes LED indicators that report on the status of many of the chassis components, including fans trays and power supplies. You can also use the management module console ports to connect to the management module CLI and to the CLI of the modules in chassis slots 1 to 6.

Management Module LEDs

The active management module controls chassis power allocation, monitors chassis operating parameters, monitors and controls chassis cooling, and generates alarms if the chassis encounters problems. All FIM and FPM modules installed in the chassis communicate with the management module through the module’s IPMC.

Management modules are hot swappable. You can replace a management module by loosening its retention screws, then pulling it out of the chassis. When a management module is removed, the other management module continues providing management functions. If both management module are removed, chassis fans speed up to maximum speed.

When an FIM or FPM module detects the absence of a management module for more than 30 seconds, the module will go to Standalone Mode. In standalone mode the modules autonomously control their own power. When a management module becomes the active management module, it assumes control of chassis fans, and the FIM and FPM modules switch back to normal mode.

In normal mode, FIM and FPM module power on/off requires authorization from the active management module and the management module controls the power supplied by the chassis power systems to the modules.

Each module in the chassis includes its own module Shelf Manager Controller (SMC) Serial Debug Interface (SDI) or SMC SDI console that communicates with the management module SMC SDI. You can connect a serial cable to the active management module console ports to connect to the management module SMC SDI and to connect to each module’s SMC SDI console. You can also interact with the SMC SDI consoles using an Intelligent Platform Management Interface (IPMI) tool.

Management Module LEDs

The following table describes the management Module LED indicators:

FortiGate-7060E Management Module LEDs

LED                                   State Description
Status Off The management module is powered off or not initialized.
Solid Red The management module is not operating normally either because it is starting up or because it has failed.
Blinking Red The active management module cannot communicate with the passive management module.
Solid Green The management module has started up and is operating normally.
Blinking Green The management module is passive.

Management Module LEDs

LED State Description
Alarm Off No alarms
Red One or more analog sensors in the chassis or on a module in the chassis (other than PSUs) have surpassed a critical or non-recoverable (NR) threshold causing an alarm. When a critical threshold has been reached, it means that a condition has been detected that has surpassed an operating tolerance. For example, a temperature has increased above the allowed operating temperature range.
Amber One or more analog sensors in the chassis or on a module in the chassis (excluding PSUs) has surpassed a major or critical (CR) threshold. Any sensor, including sensors on PSUs, has generated an alert. Sensor alert criteria is defined per sensor. For analog sensors, alerts usually mean passing an upper critical (UC) or lower critical (LC) threshold. For other sensors, an alert could mean a flag bit is indicating an anomaly.
Temp Solid Green All temperature sensors indicated acceptable operating temperatures.
Blinking Green At least one temperature sensor is detecting a high temperature outside of the normal operating range. In this case an upper non-critical (UNC) temperature. The management module increases fan speed to increase cooling and reduce the temperature.
Blinking Red At least one temperature sensor is detecting a temperature outside of the acceptable operating range. In this case an upper critical (UC) temperature. The management module increases fan speed to the maximum level. This also indicates possible problems with the cooling system and could mean that the ambient temperature is too high. Also causes a major or critical (CR) alarm.
Solid Red At least one temperature sensor is detecting a temperature outside of the allowed operating range. In this case an upper non-recoverable (UNR) temperature. The management module increases fan speed to the maximum level. The temperature is high enough to potentially cause physical damage. Also causes a critical or non-recoverable (NR) alarm.

Management Module LEDs

LED                                   State Description
Power Solid Green Normal operation.
Blinking Green Chassis 12V disabled. This means that the administrator has entered commands into the management module CLI to power off the PSU main 12V outputs. All fans, FIM and FPM modules are completely powered off but the management module is still running.
Red Chassis 12V enabled but not OK. This means the management module has enabled the main 12V outputs for all chassis components, but the power OK (PWOK) signal of at least one PSU has not been sent. When a PSU is powering up, it would be normal for this LED to be red for a second (before PSU outputs are stabilized), but if LED remains red, it indicates a problem (such as a failed PSU). Management module or FIM or FPM module voltage sensors would most likely also trigger alarms if this happens since the PSUs may not be delivering enough power.
FAN (LEDs for each of three fan trays)

PSU (LEDs for each of four PSUs)

Off Fan tachometer sensors disabled. This could happen if the administrator disabled them from the management module CLI.
Green The fan tray is operating normally.
Blinking Red The fan tray is not working. Chassis cooling may be sufficient but redundancy is lost and the fan tray that is not working should be replaced.
Red A fan tachometer sensor in this fan tray has registered an alert because a critical or non-recoverable (NR) threshold has been crossed.
Off The PSU is not installed in the chassis.
Green The PSU is present and operating normally.
Blinking Red The PSU module is installed but no power is being delivered (not plugged in).
Red The PSU’s sensors have detected an alert condition. The PSU’s analog sensors crossed critical or non-recoverable (NR) thresholds, or the PSU Status Failure bit has been set.

About management module alarm levels

LED State Description
Console 1 and 2 Off This console port is not connected or is connected to the management module SMM CLI.
Green This console port is connected to this module host console in this chassis slot.
Amber This console port is connected to this module’s SMC console.

About management module alarm levels

Minor, major and critical alarms are defined based on both IPMI, ATCA, and Telco standards for naming alarms.

  • A minor alarm (also called an IPMI non-critical (NC) alarm) indicates that a temperature or a power level was detected by a sensor that is outside of the normal operating range but is not considered a problem. In the case of a minor temperature alarm the system could respond by increasing fan speed. A non-critical threshold can be an upper non-critical (UNC) threshold (for example, a high temperature or a high power level ) or a lower non-critical (UNC) threshold (for example, a low power level). l A major alarm (also called an IPMI critical or critical recoverable (CR) alarm) indicates a temperature or power level was detected by a sensor that is far enough outside of the normal operating range to require attention from the operator. It could also mean that the system itself cannot correct the alarm. For example, the cooling system cannot provide enough cooling to reduce the temperature. It could also mean that conditions are close to being outside of the allowed operating range. For example, the temperature is close to exceeding the allowed operating temperature. A critical threshold can also be an upper critical (UC) threshold (for example, a high temperature or a high power level ) or a lower critical (LC) threshold (for example, a low power level).
  • A critical alarm (also called an IPMI non-recoverable (NR) alarm) indicates a temperature or power level was detected by a sensor that is outside of the allowed operating range and could potentially cause physical damage.

You can use the management module CLI to get details about alarm sensors, thresholds, and the events that trigger alarms.

Using the console ports

The active management module includes two console ports named Console 1 and Console 2 that can be used to connect to any serial console in the chassis. This includes the management module CLI, the FortiOS CLIs (also called host CLIs) of the FIM and FPM modules in chassis slots 1 to 6 and all of the SMC SDI consoles in the chassis.

Each module, including the management modules, includes an SMC SDI console. These consoles are used for low level programming of the module using an IPMI tool and are disabled by default. You can enable serial access to individual module SMC SDI consoles from the management module SMC SDI CLI using the command serial set sdi enable <slot>. During normal operation you may want to access the management module SMC SDI CLI, you shouldn’t normally require access to individual module SMC SDI consoles.

Connecting to the FortiOS CLI of the FIM module in slot 1

By default when the chassis first starts up Console 1 is connected to the FortiOS CLI of the FIM module in slot 1 and Console 2 is disconnected.

The default settings for connecting to each console port are: Baud Rate (bps) 9600, Data bits 8, Parity None, Stop bits 1, and Flow Control None.

The FIM and FPM modules use the standard FortiOS CLI. The SMC SDI CLIs are described in this chapter. You can use the console connection change buttons to select the CLI that each console port is connected to.

  • Press the button to cycle through the FIM and FPM module FortiOS CLIs and disconnect this console.
  • Press and hold the button to connect to the management module SMC SDI CLI. You can also cycle through each module’s SMC SDI CLI if they are enabled.

The console’s LEDs indicate what it is connected to. If no LED is lit the console is either connected to the management module SMC SDI console or disconnected. Both console ports cannot be connected to the same CLI at the same time. If a console button press would cause a conflict that module is skipped. If one of the console ports is disconnected then the other console port can connect to any CLI.

If you connect a PC to one of the management module console ports with a serial cable and open a terminal session you begin by pressing Ctrl-T to enable console switching mode, then you can do the following:

  • Press Ctrl-T to cycle through the FIM and FPM module FortiOS CLIs (the new destination is displayed in the terminal window). If you press Ctrl-T after connecting to the FPM module in slot 6 the console is disconnected. Press Ctrl-T again to start over again at slot 1.
  • Press Ctrl-R to connect to the management module SMC SDI CLI. You can also cycle through each module’s SMC SDI CLI if they are enabled (the new destination is displayed in the terminal window). After cycling through all of the enabled SMC SDI CLIs the next press of Ctrl-R disconnects the console port.

Once the console port is connected to the CLI that you want to use, press Ctrl-G to enable the CLI. When your session is complete you can press Ctrl-G to disable the CLI.

Connecting to the FortiOS CLI of the FIM module in slot 1

Use the following steps to connect to the FortiOS CLI of the FIM module in slot 1:

  1. Connect the console cable supplied with your chassis to Console 1 and to your PC or other device RS-232 console port.
  2. Start a terminal emulation program on the management computer. Use these settings: Baud Rate (bps) 9600, Data bits 8, Parity None, Stop bits 1, and Flow Control None
  3. Press Ctrl-T to enter console switch mode.
  4. Repeat pressing Ctrl-T until you have connected to slot 1.
  5. Login with an administrator name and password.

The default is admin with no password.

For security reasons, it is strongly recommended that you change the password. 6. When your session is complete, enter the exit command to log out.

Connecting to the FortiOS CLI of the FIM module in slot 2

Use the following steps to connect to the FortiOS CLI of the FIM module in slot 2:

Connecting to the management module SMC SDI CLI

  1. Connect the console cable supplied with your chassis to Console 1 and to your PC or other device RS-232 console port.
  2. Start a terminal emulation program on the management computer. Use these settings: Baud Rate (bps) 9600, Data bits 8, Parity None, Stop bits 1, and Flow Control None
  3. Press Ctrl-T to enter console switch mode.
  4. Repeat pressing Ctrl-T until you have connected to slot 2.
  5. Login with an administrator name and password.

The default is admin with no password.

For security reasons, it is strongly recommended that you change the password.

  1. When your session is complete, enter the exit command to log out.

Connecting to the management module SMC SDI CLI

Use the following steps to connect to the management module SMC SDI CLI:

  1. Connect the console cable supplied with your chassis to Console 1 and to your PC or other device RS-232 console port.
  2. Start a terminal emulation program on the management computer. Use these settings: Baud Rate (bps) 9600, Data bits 8, Parity None, Stop bits 1, and Flow Control None Use the console change button or Ctrl-R to switch to the management module SMC SDI CLI.
  3. Press Ctrl-G to connect to the CLI.
  4. Login with an administrator name and password.

The default administrator name and password are admin/admin.

For security reasons, it is strongly recommended that you change the password.

  1. You can begin entering commands at the #
  2. When your session is complete, enter the exit command to log out.
  3. Optionally press Ctrl-G to disable the CLI.

Changing the management module admin account password

Use the following procedure to change the management module admin account password.

  1. Enter the following command to show all users and their user IDs. user list

The output should show that the admin user has a user ID of 2.

  1. Use the command user set password <user-id> [<password>] to add a password for the admin account. For example:

user set password 2 <password>

  1. Enter and confirm a new password for the admin

The password should be between 5 and 20 characters long and should include a combination of upper and lower case letters and numbers.

You can change the admin account password at any time.

Connecting to the management module using an IPMI tool

Connecting to the management module using an IPMI tool

You can install a remote IPMI tool on a management computer and then use this IPMI tool to start an IPMI session with the management module. You can use one of the console ports or the MGMT port to connect with the IPMI tool.

The IPMI commands are the same as the CLI commands described in this chapter but they have to be prefixed as shown in the following example that changes the MGMT interface IP address to 172.20.120.30 over a serial connection:

sudo ipmitool -I serial-terminal -D /dev/ttyS1:9600 -U <username> -P <password> lan set 4 ipaddr 172.20.120.30

Here is the same command over an Ethernet connection:

sudo ipmitool -I lanplus -H 10.160.19.30 -k gkey -U <username> -P <password> lan set 4 ipaddr 172.20.120.30

Use the following IPMI commands to change the management module password:

First from a console port connection:

sudo ipmitool -I serial-terminal -D /dev/ttyS1:9600 -U <username> -P <password> user set password 2 <password> And from an Ethernet connection:

sudo ipmitool -I lanplus -H 10.160.19.30 -k gkey -U <username> -P <password> user set password 2 <password>

To perform an operation on a module according to its chassis slot include the -t <slot> parameter in the IPMI command. For example, to list the sensors on the FIM module in chassis slot 2 (0x82), use the following IPMI command:

sudo ipmitool -I lanplus -H 10.160.19.30 -k gkey -U <username> -P <password0> -t 0x82 sensor

FortiGate-7060E chassis slots IPMB addresses

The following table lists the IPMB addresses of the FortiGate-7060E chassis slots.

Chassis slot number Name IPMB Address (FRUID)
Management module 1 MGMT1 if active 0x20, if passive (the default) 0x22
Management module 2 MGMT2 if active (the default) 0x20, if passive 0x22
5 FPM5 0x8A
3 FPM3 0x86
1 FIM1 0x82
2 FIM2 0x84

Rebooting a chassis module from the SMC SDI CLI

Chassis slot number Name IPMB Address (FRUID)
4 FPM4 0x88
6 FPM6 0x8C

You can use the IPMB address or chassis slot number to reference a chassis slot when entering commands in the shelf manager CLI. For example, enter either of the following commands to display sensor readings for the FIM module in slot 2:

sensor 0x84 sensor 2

When command syntax descriptions in this chapter include the <slot> variable you can replace it with a slot number (1 to 6) or an IPMB address number (0x82 to 0x8C)

Rebooting a chassis module from the SMC SDI CLI

A common use of the SMC SDI CLI is being able to remotely reboot a FIM or FPM module.

From any SMC SDI CLI use the following command to reboot the module in slot 3:

mc reset 3 warm

Use the following command to power off the module in slot 4:

fru deactivate 4

Use the following command to power on the FIM module in slot 2 (IPMI address 0x84):

fru activate 0x84

Use the following IPMI command to reset the module SMC to reboot the module in slot 3:

sudo ipmitool -I lanplus -H 10.160.19.30 -k gkey -U admin -P admin -t 0x86 mc reset warm Use the following IPMI command to power off the module in slot 4:

sudo ipmitool -I lanplus -H 10.160.19.30 -k gkey -U admin -P admin -t 0x88 picmg deactivate 0

Use the following IPMI command to power on the FIM module in slot 2 (IPMI address 0x84):

sudo ipmitool -I lanplus -H 10.160.19.30 -k gkey -U admin -P admin -t 0x84 picmg activate 0

Comlog

All module SMCs include a comlog system for writing and saving console log messages. When enabled, the comlog saves log messages in a local comlog file. Log messages include all local host console messages including BIOS boot up messages. In the comlog these messages include the following headers:

Header Cause
\n— COMLOG SYSTEM BOOT: YYYY/MM/DD hh:mm:ss —\n The module is starting up after being powered on or reset.

Comlog

Header Cause
\n— COMLOG DISABLED: YYYY/MM/DD hh:mm:ss —\n Logging is disabled.
\n— COMLOG ENABLED: YYYY/MM/DD hh:mm:ss —\n Logging is enabled
\n— COMLOG TIME: YYYY/MM/DD hh:mm:ss —\n This message is written every hour when the module is powered on and logging is enabled.

The following comlog-related CLI commands are available:

Description SMC CLI Commands IPMI commands
Display comlog information. Available on the passive module. comlog getinfo

Status

COM

Disabled Speed 9600
Storage Size 0x00400000
Log Start 0x00000000
Log End 0x00000C37
Log Size 3127 Bytes
Display a module’s comlog. Available on the passive module. comlog getinfo <slot> comlog print <slot> fortinetoem fortinetoem comlog comlog getinfo print
Clear a module’s comlog. Either by resetting the a comlog start location in flash (reset_loc) or erasing all of the flash storage (chip_erase). Available on the passive module. comlog clear [reset_loc] [chip_erase] fortinetoem comlog clear
Disable a module’s comlog. Available on the passive module. comlog disable fortinetoem comlog clear
Enable comlog. Available on the passive module. comlog enable fortinetoem comlog clear
Set comlog baud rate.

<speed> can be 9600, 19200, 38400,57600, 115200, or expressed as level 1 to 4. Available on the passive module.

comlog setbaud <speed> fortinetoem <speed> comlog setbaud

System event log (SEL)

System event log (SEL)

The SMC in each module generates system event log (SEL) messages that record system events as they occur. All SEL messages are stored by individual FIM and FPM module SMCs. They are also all collected and stored by the management module SMC. From the management module you can use the following commands from the active or passive management module to view and clear SEL messages.

Operation SMC CLI Commands IPMI Commands
Display the local SEL for a module. sel <slot> sel list sel elist -v sel list
Clear the local SEL. sel clear sel clear
Get SEL information. N/A sel info
Get SEL time time get sel time get
Set SEL time time set <yyyy/mm/dd hh:mm:ss> sel time set

Sensor data record (SDR)

The sensor data record (SDR) contains static information about the sensors in each chassis module. Information includes the Sensor ID string, sensor type, sensor event/reading type, entity id, entity instance, sensor unit, reading linearization parameters, sensor thresholds, and so on. The following commands display information stored in the SDR.

Operation SMC CLI Commands IPMI Commands
Display current local sensor values and sensor SDRs or sensor thresholds for a module. Available on the passive module. sensor <slot> sensor_thresholds <slot> sensor sensor hexlist sdr list sdr elist -v sdr list

(-v required when using the Windows command prompt)

Set Sensor thresholds N/A sensor thres help

(use this command to display online help for setting sensor thresholds)

Common management module CLI operations

Common management module CLI operations

The following table lists many of the operations you can perform from the management module CLI and the commands you use to perform them. Only a subset of these commands are available on the passive management module as indicated below. Also, the <slot> option is not available on the passive module.

Action SMC CLI Commands IPMI Commands
Log into the CLI. Ctrl-G N/A
Log out of the CLI. Available on the passive module. exit (followed by Ctrl-G) N/A
Display all commands. Available on the passive module. help help
Display information about all SMC firmware in the chassis. info mc info
Display SMC device ID, Build

Date/Number, SMC

firmware information, address info, entity map for the device in the slot. Available on the passive module.

info <slot> N/A
Switching active management module. The active management module becomes passive and the passive becomes active. Available on the passive module. smm_switch N/A
Display status, power budget and hot swap state for all modules. Available on the passive module. status N/A
List the IPMI channels. channel list channel info [<channelnumber>]

Common management module CLI operations

Action SMC CLI Commands IPMI Commands
Change the SDI

verbosity level. <level> can be:

0: Alerts + Errors

1: Alerts + Errors +

Verbose + Low-Level

Errors

2: Alerts + Errors +

Verbose + Low-Level

Errors + PI traffic

3: Alerts + Errors +

Verbose + Low-Level

Errors + PI traffic +

IPMB traffic + LAN

Interface traffic

4: Same as 3

verbose <level> N/A
Display the management module time. Available on the passive module. time get sel time get
Set the management module time. Available on the passive module. time set <yyy/mm/dd hh:m m:ss> sel time hh:mm:ss> set <yyy/mm/dd
Synchronize all module SMC times. time sync N/A
List management module user accounts. Available on the passive module. user list user list [<channel number>]
Disable a user account. Available on the passive module. user disable <user-id> user disable <user-id>
Enable a user account. Available on the passive module. user enable <user-id> user enable <user-id>
Set a user account user name. Available on the passive module. user set name <user-id> <name> user set name <user-id> <name>

Common management module CLI operations

Action SMC CLI Commands IPMI Commands
Set a user account password. Available on the passive module. user set password <user-id> <password> user set password <user-id> <password>
Set the privilege level that a user account has for a specified session-based IPMI <channel>. If a <channel> is not specified the privilege level is set for all IPMI channels. Available on the passive module. user priv <user-id> {callback

| user | operator | administrator | no_access}

[<channel>]

user priv <user id> <privilege level> [<channel number>]
View a summary of users. N/A user summary
User test command. N/A user test
Display the management module

serial interface settings. Available on the passive module.

serial print N/A
Set the SDI baud rate. Available on the passive module. serial set sdi baud <speed> N/A
Set the sniff baud rate when the console is disabled. Available on the passive module. serial set sdi baud <speed> default_sniff_ N/A
Enable a console connection from the management module to another module. serial set sdi enable <slot> N/A
Disable the console connection between the management module and another module. Available on the passive module. serial set sdi disable <slot> N/A
Cold or warm reset a module. mc reset <slot> mc reset <slot> cold warm mc reset cold mc reset warm

Common management module CLI operations

Action SMC CLI Commands IPMI Commands
Run a module self test. N/A mc selftest
Power on a module. fru activate <slot> [<fruid>] picmg activate
Power off a module. fru deactivate <slot> [<fruid>] picmg deactivate
Reset a module. fru reset <slot> [<fruid>] picmg reset
Power cycle the chassis N/A chassis power cycle
Get chassis sttatus N/A chassis status
Display the LAN configuration. Available on the passive module. lan print <channel >
Set LAN configuration.

The kgkey and krkey options are used for RCMP+.

lan set [<netmas lan set <mac> lan set

<ip> lan set macaddr lan set <value> lan set <value>

<channel> k>] <channel>

<channel>

<channel>

<mac>

<channel>

<channel>

ipaddr <ip> macaddr defgw ipaddr defgw kgkey krkey lan set help

(use this command to display online help for LAN settings)

Enable or disable all LAN interfaces. lan enable lan disable fortinetoem param set 0 1 fortinetoem param set 0 0
Set fan levels. Change or switch the active fan set. fan_min_level <0-30> fan_max_level <0-30> fan_set_switch N/A
Change LED settings. N/A picmg led set help

(use this command to display online help for LED settings)

Display HPM.1 status. N/A hpm check
Run an HPM.1 upgrade. N/A hpm upgrade <.img> hpm upgrade <.img> all activate

 

Cautions and Warnings

Environmental Specifications

Rack Mount Instructions – The following or similar rack-mount instructions are included with the installation instructions:

Instructions de montage en rack – Les instructions de montage en rack suivantes ou similaires sont incluses avec les instructions d’installation:

Elevated Operating Ambient – If installed in a closed or multi-unit rack assembly, the operating ambient temperature of the rack environment may be greater than room ambient. Therefore, consideration should be given to installing the equipment in an environment compatible with the maximum ambient temperature (Tma) specified by the manufacturer.

Température ambiante élevée – S’il est installé dans un rack fermé ou à unités multiples, la température ambiante de fonctionnement de l’environnement du rack peut être supérieure à la température ambiante de la pièce. Par conséquent, il est important d’installer le matériel dans un environnement respectant la température ambiante maximale (Tma) stipulée par le fabricant.

Reduced Air Flow – Installation of the equipment in a rack should be such that the amount of air flow required for safe operation of the equipment is not compromised.

Ventilation réduite – Installation de l’équipement dans un rack doit être telle que la quantité de flux d’air nécessaire au bon fonctionnement de l’équipement n’est pas compromise.

Mechanical Loading – Mounting of the equipment in the rack should be such that a hazardous condition is not achieved due to uneven mechanical loading.

Chargement Mécanique – Montage de l’équipement dans le rack doit être telle qu’une situation dangereuse n’est pas lié à un chargement mécanique inégal.

Circuit Overloading – Consideration should be given to the connection of the equipment to the supply circuit and the effect that overloading of the circuits might have on overcurrent protection and supply wiring. Appropriate consideration of equipment nameplate ratings should be used when addressing this concern.

Surtension – Il convient de prendre l’ensemble des précautions nécessaires lors du branchement de l’équipement au circuit d’alimentation et être particulièrement attentif aux effets de la suralimentation sur le dispositif assurant une protection contre les courts-circuits et le câblage. Ainsi, il est recommandé de tenir compte du numéro d’identification de l’équipement.

Reliable Earthing – Reliable earthing of rack-mounted equipment should be maintained. Particular attention should be given to supply connections other than direct connections to the branch circuit (e.g. use of power strips).

 


Having trouble configuring your Fortinet hardware or have some questions you need answered? Ask your questions in the comments below!!! Want someone else to deal with it for you? Get some consulting from Fortinet GURU!

Leave a Reply

Name *
Email *
Website