index
int64 0
4.08k
| text
stringlengths 34
4.9k
⌀ | url
stringclasses 38
values |
|---|---|---|
46
|
FortiGate-7040E System Management Module Fortinet Technologies Inc.
About SMM alarm levels
Minor, major, and critical alarms are defined based on both IPMI, ATCA, and Telco standards for naming alarms.
l 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).
l 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 SMM CLI to get details about alarm sensors, thresholds, and the events that trigger alarms.
Using the console ports
The SMM 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 SMM 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.
The FIMs, FPMs, and SMM, all have 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 SMC SDI consoles from the SMM SMC SDI CLI using the
command serial set sdi enable <slot>. During normal operation you may want to
access the SMM SMC SDI CLI, you shouldn't normally require access to individual FIM and
FPM SMC SDI consoles.
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 FIMs and FPMs 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.
l Press the button to cycle through the FIM and FPM FortiOS CLIs and disconnect this console.
l Press and hold the button to connect to the SMM 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 SMM SMC
SDI console or disconnected. Both console ports cannot be connected to the same CLI at the same time. If a console
FortiGate-7040E 6.4.2 System Guide 47
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/18bec63c-1a0a-11e9-9685-f8bc1258b856/fortigate-7040E-system-guide.pdf
|
47
|
FortiGate-7040E System Management Module Fortinet Technologies Inc.
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 SMM 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:
l Press Ctrl-T multiple times 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.
l Press Ctrl-R multiple times to cycle through the FIM and FPM module SMC SDI CLIs 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 Enter to enable the CLI and log in. The
default administrator account for accessing the FortiOS CLIs is admin with no password. The default administrator
account for the SMC SDI CLIs is admin/admin.
When your session is complete you can press Ctrl-T until the prompt shows you have disconnected from the console.
Connecting to the FortiOS CLI of the FIM in slot 1
Use the following steps to connect to the FortiOS CLI of the FIM in slot 1:
1. Using the console cable supplied with your FortiGate-7000, connect the SMM Console 1 port on the FortiGate7000 to the USB port on your management computer.
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. Example prompt:
<Switching to Console: FIM01 (9600)>
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 in slot 2
Use the following steps to connect to the FortiOS CLI of the FIM in slot 2:
1. Using the console cable supplied with your FortiGate-7000, connect the SMM Console 1 port on the FortiGate7000 to the USB port on your management computer.
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. Example prompt:
<Switching to Console: FIM02 (9600)>
FortiGate-7040E 6.4.2 System Guide 48
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/18bec63c-1a0a-11e9-9685-f8bc1258b856/fortigate-7040E-system-guide.pdf
|
48
|
FortiGate-7040E System Management Module Fortinet Technologies Inc.
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 SMC SDI CLI of the FPM in slot 3
Use the following steps to connect to the FortiOS CLI of the FPM in slot 3:
1. Using the console cable supplied with your FortiGate-7000, connect the SMM Console 1 port on the FortiGate7000 to the USB port on your management computer.
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. Press Ctrl-R to switch to the SMM SMC SDI CLI switching mode.
5. Repeat pressing Ctrl-R until you have connected to slot 3. Example prompt:
<Switching to Console: FIM03-MC (9600)>
6. 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.
7. You can begin entering commands at the admin@FPM03-MC # prompt.
8. When your session is complete, enter the exit command to log out.
Changing the SMM admin account password
Use the following procedure to change the SMM 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.
2. Use the command user set password <user-id> [<password>] to add a password for the admin
account. For example:
user set password 2 <password>
3. Enter and confirm a new password for the admin account.
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.
FortiGate-7040E 6.4.2 System Guide 49
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/18bec63c-1a0a-11e9-9685-f8bc1258b856/fortigate-7040E-system-guide.pdf
|
49
|
FortiGate-7040E System Management Module Fortinet Technologies Inc.
Connecting to the SMM using an IPMI tool
You can install an IPMI tool on a management computer and then use this tool to send IPMI commands over your
network to the SMM MGMT interface. The IPMI tool allows you to communicate with the SMM by entering
IPMI commands. The IPMI commands are the same as the CLI commands described in this chapter but include
parameters such as the MGMT interface IP address and SMM administrator username and password.
For example, you can use the following IPMI command to change the SMM MGMT interface IP address:
sudo ipmitool -I lanplus -H <mgmt-ip> -k gkey -U <username> -P <password> lan set 4 ipaddr
172.20.120.30
Use the following IPMI command to change the SMM password:
sudo ipmitool -I lanplus -H <mgmt-ip> -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 <mgmt-ip> -k gkey -U <username> -P <password0> -t 0x82 sensor
FortiGate-7040E chassis slots IPMB addresses
The following table lists the IPMB addresses of the FortiGate-7040E chassis slots.
Chassis slot number Name IPMB Address (FRUID)
SMM MGMT 0x20
3 FPM3 0x86
1 FIM1 0x82
2 FIM2 0x84
4 FPM4 0x88
You can use the IPMB address or chassis slot number to reference a chassis slot when entering commands in the SMM
CLI. For example, enter either of the following commands to display sensor readings for the FIM 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 4) or an IPMB address number (0x82 to 0x88)
Rebooting an FIM or FPM from the SMC SDI CLI
A common use of the SMC SDI CLI is being able to remotely reboot a FIM or FPM.
FortiGate-7040E 6.4.2 System Guide 50
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/18bec63c-1a0a-11e9-9685-f8bc1258b856/fortigate-7040E-system-guide.pdf
|
50
|
FortiGate-7040E System Management Module Fortinet Technologies Inc.
From any SMC SDI CLI use the following command to reboot the FPM in slot 3:
mc reset 3 warm
Use the following command to power off the FPM in slot 4:
fru deactivate 4
Use the following command to power on the FIM in slot 2 (IPMI address 0x84):
fru activate 0x84
Use the following IPMI command to reset the module SMC to reboot the FPM 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 FPM 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 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 FIM and FPM 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.
\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 Disabled
COM 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 comlog getinfo
fortinetoem comlog print
FortiGate-7040E 6.4.2 System Guide 51
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/18bec63c-1a0a-11e9-9685-f8bc1258b856/fortigate-7040E-system-guide.pdf
|
51
|
FortiGate-7040E System Management Module Fortinet Technologies Inc.
Description SMC CLI Commands IPMI commands
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 comlog setbaud
<speed>
System event log (SEL)
The SMC in each FIM and FPM generates system event log (SEL) messages that record system events as they occur.
All SEL messages are stored by individual FIM and FPM SMCs. They are also all collected and stored by the SMM
SMC. From the SMM you can use the following commands from the SMM 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 all parts of the chassis including the FIMs
and FPMs. Information includes the Sensor ID string, sensor type, sensor event/reading type, entity ID, entity instance,
FortiGate-7040E 6.4.2 System Guide 52
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/18bec63c-1a0a-11e9-9685-f8bc1258b856/fortigate-7040E-system-guide.pdf
|
52
|
FortiGate-7040E System Management Module Fortinet Technologies Inc.
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 SMM CLI operations
The following table lists many of the operations you can perform from the SMM CLI and the commands you use to
perform them.
Action SMC CLI Commands IPMI Commands
Log into the CLI. Ctrl-R N/A
Log out of the CLI.
Available on the
passive module.
exit (followed by Ctrl-R) 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
FortiGate-7040E 6.4.2 System Guide 53
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/18bec63c-1a0a-11e9-9685-f8bc1258b856/fortigate-7040E-system-guide.pdf
|
53
|
FortiGate-7040E System Management Module Fortinet Technologies Inc.
Action SMC CLI Commands IPMI Commands
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 [<channel-number>]
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 SMM
time. Available on
the passive module.
time get sel time get
Set the SMM time.
Available on the
passive module.
time set <yyy/mm/dd hh:mm:ss> sel time set <yyy/mm/dd
hh:mm:ss>
Synchronize all
module SMC times.
time sync N/A
List SMM 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 set name <user-id> <name> user set name <user-id> <name>
FortiGate-7040E 6.4.2 System Guide 54
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/18bec63c-1a0a-11e9-9685-f8bc1258b856/fortigate-7040E-system-guide.pdf
|
54
|
FortiGate-7040E System Management Module Fortinet Technologies Inc.
Action SMC CLI Commands IPMI Commands
user name. Available
on the passive
module.
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 SMM
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 default_sniff_
baud <speed>
N/A
Enable a console
connection from the
SMM to another
module.
serial set sdi enable <slot> N/A
Disable the console
connection between
the SMM and
another module.
Available on the
serial set sdi disable <slot> N/A
FortiGate-7040E 6.4.2 System Guide 55
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/18bec63c-1a0a-11e9-9685-f8bc1258b856/fortigate-7040E-system-guide.pdf
|
55
|
FortiGate-7040E System Management Module Fortinet Technologies Inc.
Action SMC CLI Commands IPMI Commands
passive module.
Cold or warm reset a
module.
mc reset <slot> cold
mc reset <slot> warm
mc reset cold
mc reset warm
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 <channel> ipaddr <ip>
[<netmask>]
lan set <channel> macaddr <mac>
lan set <channel> defgw ipaddr
<ip>
lan set <channel> defgw macaddr
<mac>
lan set <channel> kgkey <value>
lan set <channel> krkey <value>
lan set help
(use this command to display online help for
LAN settings)
Enable or disable all
LAN interfaces.
lan disable
lan enable
fortinetoem param set 0 1
fortinetoem param set 0 0
Set fan levels.
Change or switch the
active fan set.
fan_min_level <level>
fan_max_level <level>
fan_set_switch
<level> range is 0 - 20.
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
FortiGate-7040E 6.4.2 System Guide 56
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/18bec63c-1a0a-11e9-9685-f8bc1258b856/fortigate-7040E-system-guide.pdf
|
56
|
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).
Fiabilité de la mise à la terre - Fiabilité de la mise à la terre de l'équipement monté en rack doit être maintenue. Une
attention particulière devrait être accordée aux connexions d'alimentation autres que les connexions directes au circuit
de dérivation (par exemple de l'utilisation de bandes de puissance).
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 des accessoires listés ou commutateurs, processeurs, serveurs et
similaire blades ou cartes doivent être listé UL ou équivalent.
FortiGate-7040E 6.4.2 System Guide 57
Fortinet Technologies Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/18bec63c-1a0a-11e9-9685-f8bc1258b856/fortigate-7040E-system-guide.pdf
|
57
|
Cautions and warnings Fortinet Technologies Inc.
Refer to specific Product Model Data Sheet for Environmental Specifications (Operating Temperature, Storage
Temperature, Humidity, and Altitude).
Référez à la Fiche Technique de ce produit pour les caractéristiques environnementales (Température de
fonctionnement, température de stockage, humidité et l'altitude).
Safety
Moving parts - Hazardous moving parts. Keep away from moving fan blades.
Pièces mobiles - Pièces mobiles dangereuses. Se tenir éloigné des lames mobiles du ventilateur.
Warning: Equipment intended for installation in Restricted Access Location.
Avertissement: Le matériel est conçu pour être installé dans un endroit où l’accès est restreint.
Warning: A readily accessible disconnect device shall be incorporated in the building installation wiring.
Avertissement: Un dispositif de déconnexion facilement accessible doit être incorporé dans l'installation électrique du
bâtiment.
Battery - Risk of explosion if the battery is replaced by an incorrect type. Do not dispose of batteries in a fire. They may
explode. Dispose of used batteries according to your local regulations. IMPORTANT: Switzerland: Annex 4.10 of
SR814.013 applies to batteries.
Batterie - Risque d'explosion si la batterie est remplacée par un type incorrect. Ne jetez pas les batteries au feu. Ils
peuvent exploser. Jetez les piles usagées conformément aux réglementations locales. IMPORTANT: Suisse: l'annexe
4.10 de SR814.013 s’appliquent aux batteries.
警告
本電池如果更換不正確會有爆炸的危險
請依製造商說明書處理用過之電池
CAUTION:
There is a danger of explosion if a battery is incorrect replaced. Replace only with the same or equivalent type. Dispose
batteries of according to the manufacturer’s instructions. Disposing a battery into fire, a hot oven, mechanically
crushing, or cutting it can result in an explosion. Leaving a battery in an extremely hot environment can result in leakage
of flammable liquid, gas, or an explosion. If a battery is subjected to extremely low air pressure, it may result in leakage
of flammable liquid, gas, or an explosion.
WARNUNG:
Lithium-Batterie Achtung: Explosionsgefahr bei fehlerhafter Batteriewechsel. Ersetzen Sie nur den gleichen oder
gleichwertigen Typ. Batterien gemäß den Anweisungen des Herstellers entsorgen.
Beseitigung einer BATTERIE in Feuer oder einen heißen Ofen oder mechanisches Zerkleinern oder Schneiden einer
BATTERIE, die zu einer EXPLOSION führen kann.
Verlassen einer BATTERIE in einer extrem hohen Umgebungstemperatur, die zu einer EXPLOSION oder zum
Austreten von brennbarer Flüssigkeit oder Gas führen kann.
Eine BATTERIE, die einem extrem niedrigen Luftdruck ausgesetzt ist, der zu einer EXPLOSION oder zum Austreten
von brennbarer Flüssigkeit oder Gas führen kann.
CAUTION: Shock Hazard. Disconnect all power sources.
FortiGate-7040E 6.4.2 System Guide 58
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/18bec63c-1a0a-11e9-9685-f8bc1258b856/fortigate-7040E-system-guide.pdf
|
58
|
Cautions and warnings Fortinet Technologies Inc.
ATTENTION: Risque d'électrocution. Débranchez toutes les sources d'alimentation.
Grounding - To prevent damage to your equipment, connections that enter from outside the building should pass
through a lightning / surge protector, and be properly grounded. Use an electrostatic discharge workstation (ESD) and/or
wear an anti-static wrist strap while you work. In addition to the grounding terminal of the plug, on the back panel, there
is another, separate terminal for earthing.
Mise à la terre - Pour éviter d’endommager votre matériel, assurez-vous que les branchements qui entrent à partir de
l’extérieur du bâtiment passent par un parafoudre / parasurtenseur et sont correctement mis à la terre. Utilisez un poste
de travail de décharge électrostatique (ESD) et / ou portez un bracelet anti-statique lorsque vous travaillez. Ce produit
possède une borne de mise à la terre qui est prévu à l’arrière du produit, à ceci s’ajoute 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 # 6 AWG and the connection is to be installed by a qualified
service personnel.
Ce produit a une borne de mise à la terre séparé sur le dos de l'appareil, en plus de la borne de mise à la terre de la fiche
de raccordement. Cette borne de mise à la terre séparée doit être connecté en permanence à la terre avec un
conducteur vert avec la taille bande jaune de minimum # 6 AWG et la connexion doit être installé par un personnel
qualifié.
Caution: Slide/rail mounted equipment is not to be used as a shelf or a work space.
Attention: Un équipement monté sur bâti ne doit pas être utilisé sur une étagère ou dans un espace de travail.
Fiber optic transceiver must be rated 3.3V, 22mA max, Laser Class 1, UL certified component.
Le transceiver optique doit avoir les valeurs nominales de 3.3 V, maximum 22 mA, Laser Class 1, homologué UL
FortiGate-7040E 6.4.2 System Guide 59
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/18bec63c-1a0a-11e9-9685-f8bc1258b856/fortigate-7040E-system-guide.pdf
|
59
|
Regulatory notices
Federal Communication Commission (FCC) – USA
This device complies with Part 15 of FCC Rules. Operation is subject to the following two conditions:
(1) this device may not cause harmful interference, and
(2) this device must accept any interference received; including interference that may cause undesired operation.
This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to Part 15 of
the FCC Rules. These limits are designed to provide reasonable protection against harmful interference when the
equipment is operated in a commercial environment. This equipment generates, uses, and can radiate radio frequency
energy, and if it is not installed and used in accordance with the instruction manual, it may cause harmful interference to
radio communications. Operation of this equipment in a residential area is likely to cause harmful interference, in which
case the user will be required to correct the interference at his own expense.
WARNING: Any changes or modifications to this product not expressly approved by the party responsible for
compliance could void the user’s authority to operate the equipment.
Industry Canada Equipment Standard for Digital Equipment (ICES) –
Canada
CAN ICES-3 (A) / NMB-3 (A)
This digital apparatus does not exceed the Class A limits for radio noise emissions from digital apparatus set out in the
Radio Interference Regulations of the Canadian Department of Communications.
Cet appareil numérique n’émet pas de bruits radioélectriques dépassant les limites applicables aux appareils
numériques de la classe A prescrites dans le Règlement sur le brouillage radioélectrique édicte par le ministère des
Communications du Canada.
European Conformity (CE) - EU
This is a Class A product. In a domestic environment, this product may cause radio interference, in which case the user
may be required to take adequate measures.
FortiGate-7040E 6.4.2 System Guide 60
Fortinet Technologies Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/18bec63c-1a0a-11e9-9685-f8bc1258b856/fortigate-7040E-system-guide.pdf
|
60
|
Regulatory notices Fortinet Technologies Inc.
Voluntary Control Council for Interference (VCCI) – Japan
この装置は、クラスＡ機器です。この装置を住宅環境で使用すると電波妨害を引き起こすことがあります。この場合には使
用者が適切な対策を講ずるよう要求されることがあります。ＶＣＣＩ－Ａ
Product Safety Electrical Appliance & Material (PSE) – Japan
日本では電気用品安全法(PSE)の規定により、同梱している電源コードは本製品の専用電源コードとして利用し、他の製
品に使用しないでください。
Bureau of Standards Metrology and Inspection (BSMI) – Taiwan
The presence conditions of the restricted substance (BSMI RoHS table) are available at the link below:
限用物質含有情況表 (RoHS Table) 請到以下 網址下載：
https://www.fortinet.com/bsmi
此為甲類資訊技術設備，於居住環境中使用時，可能會造成射頻擾動，在此種情況下，使用者會被要求採取某
些適當的對策。
英屬蓋曼群島商防特網股份有限公司台灣分公司
地址：台北市內湖區行愛路176號2樓
電話：(02) 27961666
China
此为A级产品，在生活环境中，该产品可能会造成无线电干扰。这种情况下，可能需要用户对其采取切实可行的
措施。
FortiGate-7040E 6.4.2 System Guide 61
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/18bec63c-1a0a-11e9-9685-f8bc1258b856/fortigate-7040E-system-guide.pdf
|
61
|
Copyright© 2021 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 Fortinet’s
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 Fortinet’s 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.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/18bec63c-1a0a-11e9-9685-f8bc1258b856/fortigate-7040E-system-guide.pdf
|
0
|
FortiGate-7030E System Guide
FortiGate-7000E Series
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/496f257b-1a0a-11e9-9685-f8bc1258b856/fortigate-7030E-system-guide.pdf
|
1
|
FORTINET DOCUMENT LIBRARY
https://docs.fortinet.com
FORTINET VIDEO GUIDE
https://video.fortinet.com
FORTINET BLOG
https://blog.fortinet.com
CUSTOMER SERVICE & SUPPORT
https://support.fortinet.com
FORTINET TRAINING & CERTIFICATION PROGRAM
https://www.fortinet.com/support-and-training/training.html
NSE INSTITUTE
https://training.fortinet.com
FORTIGUARD CENTER
https://fortiguard.com/
END USER LICENSE AGREEMENT
https://www.fortinet.com/doc/legal/EULA.pdf
FEEDBACK
Email: techdoc@fortinet.com
April 13, 2020
FortiGate-7030E 6.2.3 System Guide
01-623-417498-20200413
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/496f257b-1a0a-11e9-9685-f8bc1258b856/fortigate-7030E-system-guide.pdf
|
2
|
TABLE OF CONTENTS
Change log 5
FortiGate-7030E chassis 6
FortiGate-7030E front panel 6
FIM modules 7
FPM-7620E 7
FortiGate-7030E back panel 7
Registering your FortiGate-7030E 8
FortiGate-7030E chassis schematic 8
Chassis hardware information 9
Shipping components 9
Optional accessories and replacement parts 10
Physical description of the FortiGate-7030E chassis 10
Cooling fans, cooling air flow, and minimum clearance 11
Cooling air flow and required minimum air flow clearance 12
Optional air filters 13
AC PSUs and supplying AC power to the chassis 13
Hot Swapping an AC PSU 14
DC PSUs and supplying DC power to the chassis 14
Crimping guidelines 16
Connecting a FortiGate-7030E PSU to DC power 16
Hot Swapping a DC PSU 17
Connecting the FortiGate-7030E chassis to ground 17
Turning on FortiGate-7030E chassis power 18
FortiGate-7030E hardware assembly and rack mounting 19
Installing optional accessories 19
Front mounting brackets 19
Left and right cable management brackets 19
Front cable management bracket (FortiGate-7030E-QSFP28 only) 20
Power cord clamps 20
Mounting the FortiGate-7030E chassis in a four-post rack 21
Mounting the FortiGate-7030E chassis in a two-post rack 21
Air flow 22
Inserting FIM and FPM modules 22
Getting started with FortiGate-7000 24
Multi VDOM mode 24
Confirming startup status 25
Setting up management connections 26
Adding a password to the admin administrator account 26
Changing data interface network settings 27
Resetting to factory defaults 27
Restarting the FortiGate-7030E 27
FortiGate-7030E System Guide 3
Fortinet Technologies Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/496f257b-1a0a-11e9-9685-f8bc1258b856/fortigate-7030E-system-guide.pdf
|
3
|
Fortinet Technologies Inc.
Managing individual FortiGate-7000 FIMs and FPMs 28
Special management port numbers 28
HA mode special management port numbers 29
Managing individual FIMs and FPMs from the CLI 29
Connecting to individual FIM and FPM CLIs of the secondary FortiGate-7000 in an
HA configuration 30
Firmware upgrades 31
Firmware upgrade basics 31
Verifying that a firmware upgrade is successful 31
Upgrading the firmware running on individual FIMs or FPMs 32
Upgrading FIM firmware 32
Upgrading FPM firmware 33
Installing FIM firmware from the BIOS after a reboot 34
Installing FPM firmware from the BIOS after a reboot 36
Synchronizing FIMs and FPMs after upgrading the primary FIM firmware from the BIOS 38
FortiGate-7030E System Management Module 39
System Management Module failure 40
System Management Module LEDs 40
About SMM alarm levels 42
Using the console ports 42
Connecting to the FortiOS CLI of the FIM module in slot 1 43
Connecting to the SMC SDI CLI of the FPM module in slot 3 44
Changing the SMM admin account password 44
Connecting to the SMM using an IPMI tool 45
FortiGate-7030E chassis slots IPMB addresses 45
Rebooting a chassis module from the SMC SDI CLI 45
Comlog 46
System event log (SEL) 47
Sensor data record (SDR) 47
Common SMM CLI operations 48
Cautions and warnings 52
Environmental specifications 52
Safety 53
Regulatory notices 55
Federal Communication Commission (FCC) – USA 55
Industry Canada Equipment Standard for Digital Equipment (ICES) – Canada 55
European Conformity (CE) - EU 55
Voluntary Control Council for Interference (VCCI) – Japan 56
Product Safety Electrical Appliance & Material (PSE) – Japan 56
Bureau of Standards Metrology and Inspection (BSMI) – Taiwan 56
China 56
FortiGate-7030E System Guide 4
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/496f257b-1a0a-11e9-9685-f8bc1258b856/fortigate-7030E-system-guide.pdf
|
4
|
Change log Fortinet Technologies Inc.
Change log
Date Change description
April 13, 2020 Updated console cable descriptions to reflect that the FortiGate-7030 is now shipped
with USB to RJ-45 RS-232 console cables. Other minor changes.
March 20, 2020 Renamed management module to System Management Module (SMM). Corrections
to Connecting to the SMM using an IPMI tool on page 45.
February 24, 2020 Corrections to the 4-post and 2-post rack mount diagrams.
February 21, 2020 Added DC terminal rings and information about included DC cables. See Optional
accessories and replacement parts on page 10 and DC PSUs and supplying DC power
to the chassis on page 14.
October 29, 2019 Misc changes.
October 23, 2019 New version of this document with fixes and changes throughout.
FortiGate-7030E System Guide 5
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/496f257b-1a0a-11e9-9685-f8bc1258b856/fortigate-7030E-system-guide.pdf
|
5
|
FortiGate-7030E chassis
The FortiGate-7030E is a 6U 19-inch rackmount 3-slot chassis with a 80Gbps fabric and 1Gbps base backplane
designed by Fortinet. The fabric backplane provides network data communication and the base backplane provides
management and synch communication among the chassis slots. Power is provided to the chassis using three hot
swappable 2+1 redundant 100-240 VAC, 50-60 Hz power supply units (PSUs). You can also optionally add a fourth PSU.
The FortiGate-7030E can also be equipped with DC PSUs allowing you to connect the chassis to -48V DC power.
FortiGate-7030E front panel
The FortiGate-7030E chassis is managed by a single System Management Module (SMM) that includes an Ethernet
connection as well as two switchable console ports that provide console connections to the modules in the chassis slots.
The SMM controls chassis cooling and power management and provides an interface for managing the modules
installed in the chassis. The standard configuration of the FortiGate-7030E includes one FIM (interface) module in
chassis slot 1 and two FPM (processing) modules in chassis slots 3 and 4. The front panel also includes a sealed blank
panel. Breaking the seal or removing the panel voids your warranty. Two versions of the FortiGate-7030E are available:
l FortiGate-7030E QSFP28 and includes one FIM-7920E and two FPM-7620Es
l FortiGate-7030E SFP10G and includes one FIM-7901E and two FPM-7620Es
FortiGate-7030E front panel (FortiGate-7030E-SFP10G model)
ESD
socket
FPM-7620E
slot 3
FPM-7620E
slot 4
FIM-7901E
slot 1
Blank panel
(do not
remove)
System Management Module
FortiGate-7030E 6.2.3 System Guide 6
Fortinet Technologies Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/496f257b-1a0a-11e9-9685-f8bc1258b856/fortigate-7030E-system-guide.pdf
|
6
|
FortiGate-7030E chassis Fortinet Technologies Inc.
Do not operate the FortiGate-7030E chassis with open slots on the front or back panel. For
optimum cooling performance and safety, each chassis slot must contain an FIM or FPM or
an FIM or FPM blank panel (also called a dummy card). For the same reason, all cooling fan
trays, power supplies or power supply slot covers must be installed while the chassis is
operating.
FIM modules
FIM modules are hot swappable interface modules that provide data and management interfaces, base backplane
switching and fabric backplane session-aware load balancing for the chassis. The FIM modules include an integrated
switch fabric and DP2 processors to load balance millions of data sessions over the chassis fabric backplane to FPM
processor modules. The following FIM modules are available for the FortiGate-7030E:
l The FIM-7901E includes thirty-two front panel 10GigE SFP+ fabric channel interfaces (A1 to A32). These interfaces
are connected to 10Gbps networks. These interfaces can also be configured to operate as Gigabit Ethernet
interfaces using SFP transceivers.
l The FIM-7920E includes four front panel 100GigE QSFP28 fabric channel interfaces (C1 to C4). These interfaces
can be connected to 100Gbps networks. Using a 100GBASE-SR4 QSFP28 or 40GBASE-SR4 QSFP+ transceiver,
each QSFP28 interface can also be split into four 10GBASE-SR interfaces and connected to 10Gbps networks.
FPM-7620E
The FPM-7620E is a hot swappable processor module that provides FortiOS firewalling and security services. FPMs in
the chassis function as workers, processing sessions load balanced to them by the FIMs. FPMs include multiple NP6
network processors and CP9 content processors to accelerate traffic.
FortiGate-7030E back panel
The FortiGate-7030E chassis back panel provides access to three hot swappable cooling fan trays and three hot
swappable AC or DC PSUs. A fourth slot is available for including a fourth power supply for additional redundancy. At
least two PSUs (PWR1 and PWR2) must be connected to power. PWR4 is a backup power supply. You can add a fourth
power supply to PWR3 to provide a second backup power supply. The back panel includes the FortiGate-7030E chassis
ground connector that must be connected to ground.
FortiGate-7030E 6.2.3 System Guide 7
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/496f257b-1a0a-11e9-9685-f8bc1258b856/fortigate-7030E-system-guide.pdf
|
7
|
FortiGate-7030E chassis Fortinet Technologies Inc.
FortiGate-7030E back panel
Fan Tray 3 Fan Tray 2 Fan Tray 1
Power
Supply 1
Power
Supply 2
Power
Supply 4
Power
Supply 3
(empty)
AC Rating
Label
AC Rating
Label
Chassis
Ground
Connector
Registering your FortiGate-7030E
FortiGate-7000 series products are registered according to the chassis serial number. You need to register your chassis
to receive Fortinet customer services such as product updates and customer support. You must also register your
product for FortiGuard services. Register your product by visiting https://support.fortinet.com. To register, enter your
contact information and the serial numbers of the Fortinet products that you or your organization have purchased.
FortiGate-7030E chassis schematic
The FortiGate-7030E chassis schematic below shows the communication channels between chassis components
including the System Management Module (MGMT), the FIM (called FIM1) and the FPMs (FPM3 and FPM4).
FortiGate-7030E 6.2.3 System Guide 8
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/496f257b-1a0a-11e9-9685-f8bc1258b856/fortigate-7030E-system-guide.pdf
|
8
|
FortiGate-7030E chassis Fortinet Technologies Inc.
IPMB
SERIAL
1G
IPMB
SERIAL
IPMB
SERIAL
IPMB
SERIAL
80G
80G
80G
80G
NP6 CP9
NP6 CP9
SMC SDI
SMC SDI
DP2 ISF
MGMT IPMB 0x20
FPM
FIM
FPM
FPM3 IPMB 0x86
FPM4 IPMB 0x88
FIM1 IPMB 0x82 PMB 0x82
SMC SDI
PMB 0x88
SMC SDI
Data
Interfaces
MGMT
1-4 M1 M2
Fabric Backplane
Base Backplane
1G
1G
1G
The SMM (MGMT), with Intelligent Platform Management Bus (IPMB) address 0x20) communicates with all modules in
the chassis over the base backplane. Each module, including the SMM includes a Shelf Management Controller (SMC).
These SMCs support IPMB communication between the SMM and the FIM and FPMs for storing and sharing sensor
data that the SMM uses to control chassis cooling and power distribution. The base backplane also supports serial
communications to allow console access from the SMM to all modules, and 1Gbps Ethernet communication for
management and heartbeat communication between modules.
FIM1 (IPMB address 0x82) is the FIM in slot 1. The interfaces of this module connect the chassis to data networks and
can be used for Ethernet management access to chassis components. The FIM includes DP2 processors that distribute
sessions over the Integrated Switch Fabric (ISF) to the NP6 processors in the FPMs. Data sessions are communicated
to the FPMs over the 80Gbps chassis fabric backplane.
FPM3 and FPM4 (IPMB addresses 0x86 and 0x88) are the FPM processor modules in slots 3 and 4. These worker
modules process sessions distributed to them by the FIM. FPMs include NP6 processors to offload sessions from the
FPM CPU and CP9 processors that accelerate content processing.
Chassis hardware information
This section introduces FortiGate-7030E hardware components and accessories including power requirements and
FIM and FPM modules that can be installed in the chassis.
Shipping components
The FortiGate-7030E chassis ships pre-assembled with the following components:
l The 6U FortiGate-7030E chassis
l One FIM module
l Two FPM modules
FortiGate-7030E 6.2.3 System Guide 9
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/496f257b-1a0a-11e9-9685-f8bc1258b856/fortigate-7030E-system-guide.pdf
|
9
|
FortiGate-7030E chassis Fortinet Technologies Inc.
l One System Management Module (SMM) in the front of the chassis. (The SMM is not field replacable. If it fails,
you must RMA the chassis. The chassis will continue to operate without a functioning SMM.)
l Three Power Supply Units (PSUs) installed in the back of the chassis
l Three cooling fan trays installed in the back of the chassis
l One protective front panel installed in the chassis to protect internal chassis components. This panel must be
removed before installing FIM and FPM modules.
l Three power cords with C15 power connectors
l Four power cord management clamps
l One set of 4-post rack mounting components
l One set of 2-post rack mounting components
l One pair of cable management side brackets
l Two front mounting brackets
l Twenty M4x6 flat-head screws
l Ten M4x8 large head pan-head screws
l Six rubber feet
l Two USB to RJ-45 RS-232 console cables
l One RJ-45 Ethernet cable
Optional accessories and replacement parts
The following optional accessories can be ordered separately:
SKU Description
FG-7030E-FAN FortiGate-7030E fan tray.
FG-7030E-PS-AC 1500W AC power supply units (PSUs) for the FortiGate-7030E.
FG-7030E-CHASSIS FortiGate-7030E chassis including 1x SMM, 3x fan trays, and 3x AC PSUs.
You can also order the following:
l Additional FIM and FPM modules
l Transceivers
l DC PSUs (Each PSU ships with a set of two 8 AWG DC power cables and six extra DC terminal rings. The cables
are 3 meters (9.84 ft.) long. You can use the DC terminal rings to make custom DC cables.)
l Air Filter kit
l FPM and FIM single slot cover trays to be installed in empty chassis slots
Physical description of the FortiGate-7030E chassis
The FortiGate-7030E chassis is a 6U chassis that can be installed in a standard 19-inch rack. The following table
describes the physical characteristics of the FortiGate-7030E chassis.
Dimensions (H x W x D) 10.4 x 17.3 x 25.6 in (264 x 440 x 650 mm)
Chassis weight completely assembled with
FIM and FPM modules installed
134.3 lbs (61 kg)
FortiGate-7030E 6.2.3 System Guide 10
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/496f257b-1a0a-11e9-9685-f8bc1258b856/fortigate-7030E-system-guide.pdf
|
10
|
FortiGate-7030E chassis Fortinet Technologies Inc.
Operating temperature 32 to 104°F (0 to 40°C)
Storage temperature -31 to 158°F (-35 to 70°C)
Relative humidity 10% to 90% non-condensing
Noise level 63db
Input voltage range 100 to 240 VAC (50 to 60 Hz)
Power support rating 1500W@240VAC and 1200W@120VAC
Supplied power supply units (PSUs) 3 (for 2+1 redundancy)
Max power supply units (PSUs) 4 (for 2+2 redundancy)
Max power consumption 1940W
Average power consumption 1390W
Max current 110V/15A
Heat dissipation 6619 BTU/hr
Joules/hr 6977 KJ/hr
Cooling fans, cooling air flow, and minimum clearance
The FortiGate-7030E chassis contains three hot swappable cooling fan trays installed in the back of the chassis. Each
fan tray includes two fans that operate together. The fan tray includes two LEDs, one for each fan. When these LEDs
are green both fans are operating normally. If one of the LEDs turns red or goes off, that fan is not working and the fan
tray should be replaced.
Fan trays are hot swappable. You can replace a failed fan tray while the chassis is operating. To replace a fan tray,
unscrew the four retention screws and use the handles to pull the fan tray out of the chassis. Then apply the fan outlet
cover to the outlet grill of the new fan tray. Install the new fan tray by sliding it into place. As you slide the new fan into
place it will power up and the fan outlet cover will fall off of the fan tray. Tighten the retention screws.
The other fan trays will continue to operate and cool the chassis as a fan tray is being removed and replaced. However
an open fan tray slot will result in less air flow through the chassis so do not delay installing the replacement fan tray.
The FortiGate-7030E System Management Module (SMM) monitors the internal temperature of the chassis and adjusts
the operating speed of the cooling fans as required. When the chassis is first powered on all cooling fans run at full
speed. Once the SMM is up and running, it reduces cooling fan speeds to maintain an optimum temperature in the
chassis. If the SMM is not installed or is not operating correctly, the FortiGate-7030E chassis cooling fans always
operate at full speed.
During normal operation, all fan trays are active. If cooling requirements increase, the fan speed will increase.
FortiGate-7030E 6.2.3 System Guide 11
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/496f257b-1a0a-11e9-9685-f8bc1258b856/fortigate-7030E-system-guide.pdf
|
11
|
FortiGate-7030E chassis Fortinet Technologies Inc.
Cooling fan tray and outlet cover
Retention
Screw
Fan Tray Outlet Cover
Fan
LED
Fan
LED
Retention
Screw
Retention
Screw
Retention
Screw
Outlet
Grill
Outlet
Grill
Cooling air flow and required minimum air flow clearance
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 fan trays. 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.
Most cool air enters the chassis through the chassis front panel and all warm air exhausts out the back. For optimal
cooling allow 100 mm of clearance at the front and back of the chassis and 50 mm of clearance at the sides. Under
these conditions 80% of cooling air comes from the front panel air intake and 20% from the left and right side panels
and 100% exits out the back. Side clearance is optional and chassis cooling will be sufficient if no side clearance is
available.
FortiGate-7030E 6.2.3 System Guide 12
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/496f257b-1a0a-11e9-9685-f8bc1258b856/fortigate-7030E-system-guide.pdf
|
12
|
FortiGate-7030E chassis Fortinet Technologies Inc.
FortiGate-7030E cooling air flow and minimum air flow clearance (chassis side view)
Cool air
Intake
Left and Right
Side Cool Air
Intakes
50 mm Clearance
(Optional) Warm Air
Exhaust
Front Back
Fan
Trays
100 mm 100 mm
650 mm
Optional air filters
You can purchase an optional NEBS compliant air filter kit that includes a front filter that fits over the front of the chassis
and two filters for the side cool air intakes. These filters are not required for normal operation but can be added if you
require air filtration.
The air filters should be inspected regularly. If dirty or damaged, the filters should be disposed of and replaced. The air
filters can be fragile and should be handled carefully.
AC PSUs and supplying AC power to the chassis
The FortiGate-7030E chassis back panel includes three hot swappable AC or DC power supply units (PSUs). At least
two PSUs (PWR1 and PWR2) must be connected to power. PWR4 is a backup power supply and provides 2+1
redundancy. You can add a fourth power supply to PWR3 to provide a second backup power supply and 2+2
redundancy. See FortiGate-7030E back panel on page 8 for locations of the PSUs.
All PSUs should be connected to AC power. To improve redundancy you can connect each power supply to a separate
power source.
Use a C15 Power cable, supplied with the chassis, to connect power to each PSU C16 power connector. C15/C16 power
connectors are used for high temperature environments and are rated up to 120°C.
FortiGate-7030E 6.2.3 System Guide 13
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/496f257b-1a0a-11e9-9685-f8bc1258b856/fortigate-7030E-system-guide.pdf
|
13
|
FortiGate-7030E chassis Fortinet Technologies Inc.
AC PSU showing C16 power connector
Latch
PSU
LED
C16
Power
Connector
The PSU LED indicates whether the PSU is operating correctly and connected to power. If this LED is not lit check to
make sure the PSU is connected to power. If the power connection is good then the PSU has failed and should be
replaced.
Hot Swapping an AC PSU
Follow these steps to safely hot swap an AC PSU.
You can hot swap a PSU without powering down the FortiGate-7030E as long as two PSUs
are connected to power and operating normally. If you need to hot swap one of two operating
PSUs, you must power down the chassis first.
1. Attach an ESD wrist strap to your wrist and to an ESD socket or to a bare metal surface on the chassis or frame.
2. Turn off the power being supplied to the power supply and disconnect the power cord.
3. Press the latch towards the handle until the PSU is detached then pull it out of the chassis.
4. Insert a replacement PSU into the chassis and slide it in until it locks into place.
5. Connect the PSU power terminals as described above.
6. Turn on power to the PSU.
7. Verify that the PSU status LED is solid green meaning that the PSU is powered up and operating normally.
DC PSUs and supplying DC power to the chassis
The DC version of the FortiGate-7030E chassis front panel comes with three hot swappable 48-72V to 12V 125A DC
PSUs. Each PSU has a Internal 60A/170VDC fast blow fuse on the DC line input.
At least two PSUs (power supplies 1 and 2) must be connected to power. The third power supply is a backup power
supply and provides 2+1 redundancy. A fourth power supply can be added to provide 3+1 redundancy. See FortiGate7030E back panel on page 8 for locations of the PSUs. The diagram shows AC PSUs, with a DC version of the chassis
the AC PSUs are replaced with DC PSUs.
FortiGate-7030E 6.2.3 System Guide 14
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/496f257b-1a0a-11e9-9685-f8bc1258b856/fortigate-7030E-system-guide.pdf
|
14
|
FortiGate-7030E chassis Fortinet Technologies Inc.
Each PSU is designed to be installed in a Telecom data center or similar location that has available -48VDC power fed
from a listed 40A circuit breaker. To improve redundancy you can connect each power supply to a separate power
circuit.
DC power cables are intended to be used only for in-rack wiring, must be routed away from sharp edges, and must be
adequately fixed to prevent excessive strain on the wires and terminals. Make sure DC terminal rings are securely and
safely fastened to the PSU terminals.
DC PSU (power connector cover removed)
Latch
LED
+ (Red)
Power
Connector
- (Black)
Power
Connector
DC terminals accept UL approved ring terminals for 8/M4 stud with ext ring diameter < 9.8 mm. DC cables must be a
minimum of 8 AWG. Each PSU ships with a set of two 8 AWG DC power cables and six extra DC terminal rings. The
cables are 3 meters (9.84 ft.) long. You can use the DC terminal rings to make custom DC cables.
PSU Power ratings
Max Inrush Current 50A
Max Inrush Current Duration 200ms
Input Voltage -40V to -72V
Input Current Average: 12.5A@48V for each PSU, Max: 44A
PSU LED States
State Description
Off DC power not connected.
Flashing Green The PSU is in standby mode, not supplying power to the chassis.
Green Normal Operation with DC power connected.
Amber Input voltage outside of normal operating range, PSU fan not operating, or output
voltage outside of normal operating range.
Flashing Amber Warning that power input or output is close to outside of normal operating range.
PSU should be replaced.
FortiGate-7030E 6.2.3 System Guide 15
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/496f257b-1a0a-11e9-9685-f8bc1258b856/fortigate-7030E-system-guide.pdf
|
15
|
FortiGate-7030E chassis Fortinet Technologies Inc.
Crimping guidelines
To connect the PSUs 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 UL approved ring terminals for 8/M4
studs with ext ring diameter < 9.8 mm. Use the following information to crimp and prepare these wires.
Do not crimp energized wires.
Follow these crimping guidelines:
l Strip the insulation from cable. Be careful not to nick cable strands which may later result in stands breaking.
l 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.
l 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.
l After crimping, remove all sharp edges, flash or burrs.
Connecting a FortiGate-7030E PSU to DC power
The following procedure describes how to connect a PSU to DC power. Repeat this procedure to connect each PSU.
DC Power
Source
-48VDC RTN + RTN
(red)
-48VDC
(black)
You need the following equipment to connect the primary FortiGate-7030E PSUs to DC power:
l An electrostatic discharge (ESD) preventive wrist strap with connection cord.
l One black 8 AWG stranded wire with attached UL approved ring terminal for 8/M4 studs with ext ring diameter <
9.8 mm.
l One red 8 AWG stranded wire with attached UL approved ring terminal for 8/M4 studs with ext ring diameter < 9.8
mm.
To connect a PSU to DC power
1. Attach the ESD wrist strap to your wrist and to an ESD socket or to a bare metal surface on the chassis or frame.
2. Make sure that the PSU and power cords are not energized.
3. Snap the clear plastic cover off of the PSU power terminals.
FortiGate-7030E 6.2.3 System Guide 16
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/496f257b-1a0a-11e9-9685-f8bc1258b856/fortigate-7030E-system-guide.pdf
|
16
|
FortiGate-7030E chassis Fortinet Technologies Inc.
4. Remove the first set of nuts and lock washers from the connectors on the PSU.
5. Connect the black -48V power wire from your DC power source to the connector on the PSU labeled - using the
ring terminal.
6. Connect the red RTN power wire from you RTN power source to the connector on the PSU labeled + using the
ring terminal.
7. Use the previously removed nuts and lock washers to secure the connectors. Do not apply torque of more than
3.8 Nm (33.62 lbf.in).
8. Snap the clear plastic cover over the PSU power terminals.
9. Make sure the power wires are secured using tie wraps if required.
10. If required, label the black wire -48V.
11. If required, label the red wire RTN.
12. Turn on power to the PSU.
13. Verify that the PSU status LED is solid green meaning that the PSU is powered up and operating normally.
Hot Swapping a DC PSU
Follow these steps to safely hot swap a DC PSU.
1. Attach an ESD wrist strap to your wrist and to an ESD socket or to a bare metal surface on the chassis or frame.
2. Turn off the power being supplied to the PSU.
3. Snap off the terminal cover and remove the wires from the PSU terminals.
4. Press the latch towards the handle until the PSU is detached then pull it out of the chassis.
5. Insert a replacement PSU into the chassis and slide it in until it locks into place.
6. Connect the PSU power terminals as described above.
7. Turn on power to the PSU.
8. Verify that the PSU status LED is solid green meaning that the PSU is powered up and operating normally.
Connecting the FortiGate-7030E chassis to ground
The FortiGate-7030E chassis includes a ground terminal on the rear the bottom of the FortiGate-7030E back panel. The
ground terminal provides two connectors to be used with a double-holed lug such as Thomas & Betts PN 54850BE. This
connector must be connected to a local ground connection.
You need the following equipment to connect the FortiGate-7030E chassis to ground:
l An electrostatic discharge (ESD) preventive wrist strap with connection cord.
l One green 6 AWG stranded wire with listed closed loop double-hole lug suitable for minimum 6 AWG copper wire,
such as Thomas & Betts PN 54850BE.
FortiGate-7030E 6.2.3 System Guide 17
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/496f257b-1a0a-11e9-9685-f8bc1258b856/fortigate-7030E-system-guide.pdf
|
17
|
FortiGate-7030E chassis Fortinet Technologies Inc.
To connect the FortiGate-7030E chassis to ground
Data Center
ground
connector
(Central office
ground system)
Chassis
Ground
Connector
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 chassis and ground wire are not energized.
3. Connect the green ground wire from the local ground to the ground connector on the FortiGate-7030E chassis.
4. Secure the ground wire to the chassis.
5. Optionally label the wire GND.
Turning on FortiGate-7030E chassis power
Connect AC power to PWR1, PWR2 and PWR4. Once the FortiGate-7030E chassis is connected to power the chassis
powers up. If the chassis is operating correctly, the LEDs on the PSUs and fans should be lit. As well, the LEDs on the
FortiGate-7030E SMM should be lit.
When the chassis first starts up you should also hear the cooling fans operating.
In addition, if any modules have been installed in the chassis they should power on and their front panel LEDs should
indicate that they are starting up and operating normally.
FortiGate-7030E 6.2.3 System Guide 18
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/496f257b-1a0a-11e9-9685-f8bc1258b856/fortigate-7030E-system-guide.pdf
|
18
|
FortiGate-7030E hardware assembly and rack mounting
The FortiGate-7030E chassis must be mounted in a standard 19-inch rack and requires 6U of vertical space in the rack.
This chapter describes how to attach accessories to the FortiGate-7030E chassis, how to install the chassis in a 4-post
or 2-post rack, and how to install FIM and FPM modules in the chassis front panel slots.
If you install the FortiGate-7030E 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.
The FortiGate-7030E chassis should not be operated as a free-standing appliance.
Install accessories before mounting the chassis in a rack. Install the modules after the chassis
is rack mounted.
Installing optional accessories
The following accessories are optional and not required for all configurations:
l Front mounting brackets
l Left and right cable management brackets
l Front cable management bracket
l Power cord clamps
Front mounting brackets
You need to install the front mounting brackets to mount the FortiGate-7030E in a four-post rack (see Mounting the
FortiGate-7030E chassis in a four-post rack on page 21). You also need to install the front mounting brackets to be able
to attach the left and right cable management brackets.
The front mounting brackets are not required to mount the FortiGate-7030E in a two-post rack (see Mounting the
FortiGate-7030E chassis in a two-post rack on page 21).
Left and right cable management brackets
You can optionally install the left and right cable management brackets to help manage the network cables connected
to FIM modules installed in the FortiGate-7030E. Install the left and right cable management brackets by attaching
them to the left and right front mounting brackets.
FortiGate-7030E 6.2.3 System Guide 19
Fortinet Technologies Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/496f257b-1a0a-11e9-9685-f8bc1258b856/fortigate-7030E-system-guide.pdf
|
19
|
FortiGate-7030E hardware assembly and rack mounting Fortinet Technologies Inc.
Installing FortiGate-7030E optional accessories
Front mounting
bracket
Front cable
management
bracket
(FIM-7920E only)
Left cable
management
bracket
Right cable
management
bracket
M4x8 large head
pan head screws
M4x8 large head
pan head screws
M4x8 flat-head
screws
M4x8 flat-head
screws
Front mounting
bracket
Power cord
clamp
Front cable management bracket (FortiGate-7030E-QSFP28 only)
The FIM-7920E module included with a FortiGate-7030E-QSFP28 ships with an optional front cable management
bracket that helps support the relatively large QSFP28 transceivers used with this module.
If you decide to use the front cable management bracket, install it by attaching it to the left and right cable management
brackets.
Power cord clamps
You can also install power cord clamps into the back of the chassis beside each PSU. Install the clamps by inserting
them into the holes adjacent each supply at the back of the chassis. Use the clamps to secure the AC power cords so
they are not accidentally disconnected.
FortiGate-7030E 6.2.3 System Guide 20
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/496f257b-1a0a-11e9-9685-f8bc1258b856/fortigate-7030E-system-guide.pdf
|
20
|
FortiGate-7030E hardware assembly and rack mounting Fortinet Technologies Inc.
Mounting the FortiGate-7030E chassis in a four-post rack
The FortiGate-7030E package includes an set of extendable brackets that you can use to mount the chassis in a 4-post
rack. Install the brackets to create a 4-post rack mount tray that the chassis will slide on to. Attach each side of the tray
to the 4-post rack using the front and back brackets as shown below. Make sure you install the tray with enough space
above it for the chassis. The length of the tray sides adjusts to match your rack.
Once the 4-post rack mount tray has been installed, slide the chassis onto the tray and secure it to the rack mount tray
as shown in the diagram.
Mounting the chassis in a four-post Rack
Secure the chassis
to the rack mount tray
Rack mount
screws not
provided M4x8 pan-head screw
with M4 washer (both sides of chassis)
Rack mount
screws not
provided
Attach the left
tray to the left
rack posts
Attach the right
tray to the right
rack posts
Rack mount
screws not
provided
Mounting the FortiGate-7030E chassis in a two-post rack
The FortiGate-7030E package includes two mid-mount trays and two mid-mount ears that you can use the mount the
chassis in a 2-post rack. As shown in the diagram, first attach the mid-mount trays to the rack making sure to leave
enough space above the trays for the chassis. Then attach the mid-mount ears to the chassis also as shown in the
diagram. Finally line up the mid-mount trays with the mid-mount ears so that the chassis is supported in the rack. Then
use screws to attach the mid-mount ears and the chassis to the rack.
FortiGate-7030E 6.2.3 System Guide 21
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/496f257b-1a0a-11e9-9685-f8bc1258b856/fortigate-7030E-system-guide.pdf
|
21
|
FortiGate-7030E hardware assembly and rack mounting Fortinet Technologies Inc.
Mounting the chassis in a 2-post rack
Left mid mount tray
(attach to the rack
first)
M4x8 flat head
screws
M4x8 flat head
screws
Right mid mount tray
(attach to the rack first)
Right mid mount
ear (attach to the
chassis)
Left mid mount ear
(Attach to the
chassis)
Air flow
For rack installation, make sure that the amount of air flow required for safe operation of the FortiGate-7030E chassis is
not compromised. Make sure that the chassis ventilation openings at the front and back 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 100 mm. This results in a total footprint of 850 mm from front to back.
Inserting FIM and FPM modules
All FortiGate-7030E chassis are shipped with a protective front panel installed in the chassis to protect internal chassis
components. This panel must be removed before you install FIM and FPM modules.
Insert FIM modules into chassis slot 1. Insert FPM modules into chassis slots 3 and 4.
Do not operate the FortiGate-7030E chassis with open slots on the front or back panel. For
optimum cooling performance and safety, each chassis slot must contain an FIM or FPM or
an FIM or FPM blank panel (also called a dummy card). For the same reason, all cooling fan
trays, power supplies or power supply slot covers must be installed while the chassis is
operating.
FortiGate-7030E 6.2.3 System Guide 22
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/496f257b-1a0a-11e9-9685-f8bc1258b856/fortigate-7030E-system-guide.pdf
|
22
|
FortiGate-7030E hardware assembly and rack mounting Fortinet Technologies Inc.
To insert FIM and FPM modules, see the guide supplied with the module.
FIM-7920E front panel
FIM-7920E
Power
Slider
Module
Lever
Secure
Screw
Module
Lever
Power
Slider
Secure
Screw
C1 to C4
100GigE Fabric Channel
QSFP28 Network
Interfaces (data)
M1 and M2 10GigE Base
Channel SFP+ Interfaces
(heartbeat and management)
MGMT1 - MGMT4
10/100/1000BASE-T Copper
Management Interface
Status, Alarm
HA, and Power
LEDS
USB
Power
Button
NMI
Button
You must carefully slide the module all the way into the chassis slot, close the module levers
to seat the module into the slot, and tighten the secure screws to make sure the module is
fully engaged with the backplane and secured. You must also make sure that the power
sliders are fully closed by gently pushing them down.
Installation Highlights:
1. Module levers must be closed.
2. Secure screws must be tightened.
3. Power sliders must be fully closed for the module to get power and start up.
If the module is not receiving power all LEDs remain off.
All FIM and FPM-7000 series modules must be protected from static discharge and physical
shock. Only handle or work with these boards at a static-free workstation. Always wear a
grounded electrostatic discharge (ESD) preventive wrist strap when handling these boards.
FortiGate-7030E 6.2.3 System Guide 23
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/496f257b-1a0a-11e9-9685-f8bc1258b856/fortigate-7030E-system-guide.pdf
|
23
|
Getting started with FortiGate-7000
Begin by installing your FortiGate-7000 chassis in a rack and installing FIM interface modules and FPM processing
modules in it. Then you can power on the chassis and all modules in the chassis will power up.
Whenever a chassis is first powered on, it takes about 5 minutes for all modules to start up and become completely
initialized and synchronized. During this time the chassis will not allow traffic to pass through and you may not be able to
log into the GUI, or if you manage to log in, the session could time out as the FortiGate-7000 continues negotiating.
Review the PSU, fan tray, System Management Module (SMM), FIM, and FPM LEDs to verify that everything is
operating normally. Wait until the chassis has completely started up and synchronized before making configuration
changes.
When the system has initialized, you have a few options for connecting to the FortiGate-7000 GUI or CLI:
l Log in to the GUI by connecting the MGMT1 interface of the FIM in slot 1 to your network. Then browse to
https://192.168.1.99.
l Log in to the CLI by connecting the MGMT1 interface of the FIM in slot 1 to your network. Then use an SSH client
to connect to 192.168.1.99 and use the same admin account to log in.
l Log in to the primary FIM CLI by connecting to the RJ-45 RS-232 Console 1 serial port on the FortiGate-7000 SMM
with settings: BPS: 9600, data bits: 8, parity: none, stop bits: 1, flow control: none.
The FortiGate-7000 ships with the following factory default configuration.
Option Default Configuration
Administrator Account User
Name
admin
Password (none) For security reasons you should add a password to the admin
account before connecting the FortiGate-7000 to your network.
MGMT1 IP/Netmask 192.168.1.99/24 (the MGMT1 interface is part of the mgmt redundant
interface that also includes MGMT2, MGMT3, and MGMT4).
All configuration changes must be made from the primary FIM GUI or CLI and not from the secondary FIM or the FPMs.
All other management communication (for example, SNMP queries, remote logging, and so on) use the management
aggregate interface and are handled by the primary FIM.
Multi VDOM mode
By default, when you first start up a FortiGate-7000F it is operating in Multi VDOM mode. The default Multi VDOM
configuration includes the root VDOM and a management VDOM named mgmt-vdom. The management interface
(mgmt) and the HA heartbeat interfaces (M1 and M2) are in mgmt-vdom and all of the data interfaces are in the root
VDOM.
FortiGate-7030E 6.2.3 System Guide 24
Fortinet Technologies Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/496f257b-1a0a-11e9-9685-f8bc1258b856/fortigate-7030E-system-guide.pdf
|
24
|
Getting started with FortiGate-7000 Fortinet Technologies Inc.
You cannot delete or rename mgmt-vdom. You also cannot remove interfaces from it or add interfaces to it. You can
however, configure other settings such as routing required for management communication, interface IP addresses,
and so on. You can also add VLANs to the interfaces in mgmt-vdom.
You can use the root VDOM for data traffic and you can also add more VDOMs as required, depending on your Multi
VDOM license.
Confirming startup status
Before verifying normal operation and making configuration changes and so on you should wait until the FortiGate-7000
is completely started up and synchronized. This can take a few minutes.
To confirm that the FortiGate-7000 is synchronized, go to Monitor > Configuration Sync Monitor. If the system is
synchronized, all of the FIMs and FPMs should be visible and their Configuration Status should be In Sync. The
Configuration Sync Monitor also indicates if any modules are not synchronized.
You can also view the Sensor Information dashboard widget to confirm that system temperatures are normal and that
all power supplies and fans are operating normally.
From the menu bar at the top of the GUI, you can click on the host name and pull down a list
of the FIMs and FPMs in the FortiGate-7000. From the list you can see the status of each
FIM or FPM, change the host name, or log into the GUI using the special management port
number.
From the CLI you can use the diagnose sys confsync status | grep in_sy command to view the
synchronization status of the FIMs and FPMs. If all of the FIMs and FPMs are synchronized, each output line should
include in_sync=1. If a line ends with in_sync=0, that FIM or FPM is not synchronized. The following example just
shows a few output lines:
diagnose sys confsync status | grep in_sy
FIM10E3E16000062, Slave, uptime=53740.68, priority=2, slot_id=2:2, idx=3, flag=0x10, in_sync=1
FIM04E3E16000010, Slave, uptime=53790.94, priority=3, slot_id=1:1, idx=0, flag=0x10, in_sync=1
FIM04E3E16000014, Master, uptime=53781.29, priority=1, slot_id=2:1, idx=1, flag=0x10, in_sync=1
FIM10E3E16000040, Slave, uptime=53707.36, priority=4, slot_id=1:2, idx=2, flag=0x10, in_sync=1
FPM20E3E16900234, Slave, uptime=53790.98, priority=16, slot_id=2:3, idx=4, flag=0x64, in_sync=1
FPM20E3E16900269, Slave, uptime=53783.67, priority=17, slot_id=2:4, idx=5, flag=0x64, in_sync=1
FPM20E3E17900113, Slave, uptime=53783.78, priority=116, slot_id=1:3, idx=6, flag=0x64, in_sync=1
FPM20E3E17900217, Slave, uptime=53784.11, priority=117, slot_id=1:4, idx=7, flag=0x64, in_sync=1
...
FortiGate-7030E 6.2.3 System Guide 25
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/496f257b-1a0a-11e9-9685-f8bc1258b856/fortigate-7030E-system-guide.pdf
|
25
|
Getting started with FortiGate-7000 Fortinet Technologies Inc.
Setting up management connections
When your FortiGate-7000 first starts up, the MGMT1 to MGMT4 interfaces of the FIM are part of a static 802.3
aggregate interface with a default IP address of 192.168.1.99. On the GUI or CLI the 802.3 aggregate interface is
named mgmt.
Example mgmt interface configuration
You can configure and manage your FortiGate-7030 by connecting an Ethernet cable to any of the MGMT1 - 4
interfaces of the FIM and logging into the GUI using HTTPS or the CLI using SSH. The default IP address is
192.168.1.99 and you can log in with the admin administrator account with no password.
For security reasons you should add a password to the admin account before connecting the
chassis to your network.
Adding a password to the admin administrator account
For security purposes one of the first things you should do is add a password to the admin account.
Depending on your firmware version, when you first log into the GUI you maybe presented with an option to change the
admin account password.
From the GUI, access the Global GUI and go to System > Administrators, edit the admin account, and select
Change Password.
From the CLI:
config global
config system admin
edit admin
FortiGate-7030E 6.2.3 System Guide 26
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/496f257b-1a0a-11e9-9685-f8bc1258b856/fortigate-7030E-system-guide.pdf
|
26
|
Getting started with FortiGate-7000 Fortinet Technologies Inc.
set password <new-password>
end
Changing data interface network settings
To change the IP address of any FortiGate-7030E data interface:
l From the GUI access the Global GUI and go to Network > Interfaces. Edit any interface to change its IP address
and other settings.
l From the CLI:
config system interface
edit <interface-name>
set ip <ip-address> <netmask>
end
Resetting to factory defaults
At any time during the configuration process, if you run into problems, you can reset the FortiGate-7030E to factory
defaults and start over. From the primary FIM CLI enter:
config global
execute factoryreset
Restarting the FortiGate-7030E
To restart all of the modules in a FortiGate-7030E, connect to the primary FIM CLI and enter the execute reboot
command. When you enter this command from the primary FIM, all of the modules restart.
To restart individual FIMs or FPMs, log in to the CLI of the module to restart and run the execute reboot command.
FortiGate-7030E 6.2.3 System Guide 27
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/496f257b-1a0a-11e9-9685-f8bc1258b856/fortigate-7030E-system-guide.pdf
|
27
|
Managing individual FortiGate-7000 FIMs and FPMs
You can manage individual FIMs and FPMs using special port numbers or the execute load-balance slot
manage command. You can also use the execute ha manage command to log in to the other FortiGate-7000 in an
HA configuration.
Special management port numbers
In some cases you may want to connect to individual FIMs or FPMs to view status information or perform a
maintenance task such as installing firmware or performing a restart. You can connect to the GUI or CLI of individual
FIMs or FPMs in a FortiGate-7000 using the mgmt interface IP address with a special port number.
To enable using the special management port numbers to connect to individual FIMs and
FPMs, the mgmt interface must be connected to a network, have a valid IP address, and have
management or administrative access enabled. To block access to the special management
port numbers, disconnect the mgmt interface from a network, configure the mgmt interface
with an invalid IP address, or disable management or administrative access for the mgmt
interface.
For example, if the mgmt interface IP address is 192.168.1.99, you can connect to the GUI of the FPM in slot 3 using
the mgmt interface IP address followed by the special port number, for example:
https://192.168.1.99:44303
The special port number (in this case 44303) is a combination of the service port (for HTTPS, the service port is 443) and
the slot number (in this example, 03).
You can view the special HTTPS management port number for and log in to the GUI of an FIM or FPM from the
Configuration Sync Monitor.
The following table lists the special port numbers to use to connect to each FortiGate-7000 slot using common
management protocols.
You can't change the special management port numbers. Changing configurable
management port numbers, for example the HTTPS management port (which you might
change to support SSL VPN), does not affect the special management port numbers.
FortiGate-7000 special management port numbers
Slot Number Slot Address HTTP
(80)
HTTPS (443) Telnet
(23)
SSH (22) SNMP (161)
3 FPM03 8003 44303 2303 2203 16103
FortiGate-7030E 6.2.3 System Guide 28
Fortinet Technologies Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/496f257b-1a0a-11e9-9685-f8bc1258b856/fortigate-7030E-system-guide.pdf
|
28
|
Managing individual FortiGate-7000 FIMs and FPMs Fortinet Technologies Inc.
Slot Number Slot Address HTTP
(80)
HTTPS (443) Telnet
(23)
SSH (22) SNMP (161)
1 FIM01 8001 44301 2301 2201 16101
4 FPM04 8004 44304 2304 2204 16104
For example, to connect to the GUI of the FIM in slot 2 using HTTPS you would browse to https://192.168.1.99:44302.
To verify which module you have logged into, the GUI header banner and the CLI prompt shows its hostname. The CLI
prompt also shows slot address in the format <hostname> [<slot address>] #.
Logging in to different modules allows you to use FortiView or Monitor GUI pages to view the activity of that module.
Even though you can log in to different modules, you can only make configuration changes from the primary FIM; which
is usually the FIM in slot 1.
HA mode special management port numbers
In HA mode, you use the same special port numbers to connect to FIMs and FPMs in chassis 1 (chassis ID = 1) and
different special port numbers to connect to FIMs and FPMs in chassis 2 (chassis ID = 2):
FortiGate-7000 HA special management port numbers
Chassis and
Slot Number
Slot Address HTTP
(80)
HTTPS (443) Telnet
(23)
SSH (22) SNMP (161)
Ch1 slot 3 FPM03 8005 44303 2303 2203 16103
Ch1 slot 1 FIM01 8003 44301 2301 2201 16101
Ch1 slot 4 FPM04 8004 44304 2304 2204 16104
Ch2 slot 3 FPM03 8005 44323 2323 2223 16123
Ch2 slot 1 FIM01 8003 44321 2321 2221 16121
Ch2 slot 4 FPM04 8004 44324 2324 2224 16124
Managing individual FIMs and FPMs from the CLI
From any CLI, you can use the execute load-balance slot manage <slot> command to log into the CLI of
different FIMs and FPMs. You can use this command to view the status or configuration of the module, restart the
module, or perform other operations. You should not change the configuration of individual FIMs or FPMs because this
can cause configuration synchronization errors.
<slot> is the slot number of the slot that you want to log in to.
After you log in to a different module in this way, you can't use the execute load-balance slot manage
command to log in to another module. Instead you must use the exit command to revert back to the CLI of the
FortiGate-7030E 6.2.3 System Guide 29
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/496f257b-1a0a-11e9-9685-f8bc1258b856/fortigate-7030E-system-guide.pdf
|
29
|
Managing individual FortiGate-7000 FIMs and FPMs Fortinet Technologies Inc.
component that you originally logged in to. Then you can use the execute load-balance slot manage
command to log into another module.
Connecting to individual FIM and FPM CLIs of the secondary
FortiGate-7000 in an HA configuration
From the primary FIM of the primary FortiGate-7000 in an HA configuration, you can use the following command to log
in to the primary FIM of the secondary FortiGate-7000:
execute ha manage <id>
Where <id> is the ID of the other FortiGate-7000 in the cluster. From the primary FortiGate-7000, use an ID of 0 to log
into the secondary FortiGate-7000. From the secondary FortiGate-7000, use an ID of 1 to log into the primary
FortiGate-7000. You can enter the ? to see the list of IDs that you can connect to.
After you have logged in, you can manage the secondary FortiGate-7000 from the primary FIM or you can use the
execute-load-balance slot manage command to connect to the CLIs of the other FIM and the FPMs in the
secondary FortiGate-7000.
FortiGate-7030E 6.2.3 System Guide 30
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/496f257b-1a0a-11e9-9685-f8bc1258b856/fortigate-7030E-system-guide.pdf
|
30
|
Firmware upgrades
In addition to introducing the basics of upgrading FortiGate-7030E firmware, this section describes how to:
l Upgrade the firmware running on individual FPCs.
l Upgrade the management board firmware from the BIOS and reset the configuration of all of the FPCs.
Firmware upgrade basics
All of the FIMs and FPMs in your FortiGate-7000 system run the same firmware image. You upgrade the firmware from
the primary FIM GUI or CLI just as you would any FortiGate product.
You can perform a graceful firmware upgrade of a FortiGate-7000 FGCP HA cluster by enabling uninterruptibleupgrade and session-pickup. A graceful firmware upgrade only causes minimal traffic interruption. For more
information about graceful HA upgrades, see HA cluster firmware upgrades.
Upgrading the firmware of a standalone FortiGate-7000, or FortiGate-7000 HA cluster with uninterrupableupgrade disabled interrupts traffic because the firmware running on the FIMs and FPMs upgrades in one step. These
firmware upgrades should be done during a quiet time because traffic will be interrupted during the upgrade process.
A firmware upgrade takes a few minutes, depending on the number of FIMs and FPMs in your FortiGate-7000 system.
Some firmware upgrades may take longer depending on factors such as the size of the configuration and whether an
upgrade of the DP2 processor is included.
Before beginning a firmware upgrade, Fortinet recommends that you perform the following tasks:
l Review the latest release notes for the firmware version that you are upgrading to.
l Verify the recommended upgrade path as documented in the release notes.
l Back up your FortiGate-7000 configuration.
Fortinet recommends that you review the services provided by your FortiGate-7000 before a
firmware upgrade and then again after the upgrade to make sure the services continues to
operate normally. For example, you might want to verify that you can successfully access an
important server used by your organization before the upgrade and make sure that you can
still reach the server after the upgrade, and performance is comparable. You can also take a
snapshot of key performance indicators (for example, number of sessions, CPU usage, and
memory usage) before the upgrade and verify that you see comparable performance after the
upgrade.
Verifying that a firmware upgrade is successful
After a FortiGate-7000 firmware upgrade, you should verify that all of the FIMs and FPMs have been successfully
upgraded to the new firmware version.
After the firmware upgrade appears to be complete:
FortiGate-7030E 6.2.3 System Guide 31
Fortinet Technologies Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/496f257b-1a0a-11e9-9685-f8bc1258b856/fortigate-7030E-system-guide.pdf
|
31
|
Firmware upgrades Fortinet Technologies Inc.
1. Log into the primary FIM and verify that it is running the expected firmware version.
You can verify the firmware version running on the primary FIM from the System Information dashboard widget or
by using the get system status command.
2. Confirm that the FortiGate-7000 is synchronized.
Go to Monitor > Configuration Sync Monitor to verify the configuration status of the FIMs and FPMs. You can
also use the diagnose sys confsync status | grep in_sy command to see if the FIMs and FPMs are
all synchronized. In the command output, in_sync=1 means the FIM or FPM is synchronized. In_sync=0
means the FIM or FPM is not synchronized, which could indicated the FIM or FPM is running a different firmware
build than the primary FIM.
3. Optionally, you can also log into the other FIM and FPMs, and in the same way confirm that they are also running
the expected firmware version and are synchronized.
Upgrading the firmware running on individual FIMs or FPMs
You can install firmware on individual FIMs or FPMs by logging into the FIM or FPM GUI or CLI. You can also setup a
console connection to the FortiGate-7000 front panel SMM and install firmware on individual FIMs or FPMs from a
TFTP server after interrupting the FIM or FPM boot up sequence from the BIOS.
Normally you wouldn't need to upgrade the firmware on individual FIMs or FPMs because the FortiGate-7000 keeps the
firmware on all of the FIMs and FPMs synchronized. However, FIM or FPM firmware may go out of sync in the following
situations:
l Communication issues during a normal FortiGate-7000 firmware upgrade.
l Installing a replacement FIM or FPM that is running a different firmware version.
l Installing firmware on or formatting an FIM or FPM from the BIOS.
To verify the firmware versions on each FIM or FPM you can check individual FIM and FPM GUIs or enter the get
system status command from each FIM or FPM CLI. You can also use the diagnose sys confsync status
| grep in_sy command to see if the FIMs and FPMs are all synchronized. In the command output, in_sync=1
means the FIM or FPM is synchronized. In_sync=0 means the FIM or FPM is not synchronized, which could indicated
the FIM or FPM is running a different firmware build than the primary FIM.
The procedures in this section work for FIMs or FPMs in a standalone FortiGate-7000. These procedures also work for
FIMs or FPMs in the primary FortiGate-7000 in an HA configuration. To upgrade firmware on an FIM or FPM in the
secondary FortiGate-7000 in an HA configuration, you should either remove the secondary FortiGate-7000 from the HA
configuration or cause a failover so that the secondary FortiGate-7000 becomes the primary FortiGate-7000.
In general, if you need to update both FIMs and FPMs in the same FortiGate-7000, you should update the FIMs first as
the FPMs can only communicate through FIM interfaces.
Upgrading FIM firmware
Use the following procedure to upgrade the firmware running on a single FIM. For this procedure to work, you must
connect at least one of the FIM MGMT interfaces to a network. You must also be able to log in to the FIM GUI or CLI
from that MGMT interface. If you perform the firmware upgrade from the CLI, the FIM must be able to communicate
with an FTP or TFTP server.
During the upgrade, the FIM will not be able to process traffic. However, the other FIM and the FPMs should continue to
operate normally.
FortiGate-7030E 6.2.3 System Guide 32
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/496f257b-1a0a-11e9-9685-f8bc1258b856/fortigate-7030E-system-guide.pdf
|
32
|
Firmware upgrades Fortinet Technologies Inc.
1. Log into the FIM GUI or CLI and perform a normal firmware upgrade.
You may need to use the special port number to log in to the FIM in slot two (for example, browse to
https://192.168.1.99:44302).
2. Once the FIM restarts, verify that the new firmware has been installed.
You can do this from the FIM GUI dashboard or from the FIM CLI using the get system status command.
3. Verify that the configuration has been synchronized to the upgraded FIM. The following command output shows
the synchronization status of a FortiGate-7040E. The field in_sync=1 indicates that the configurations of the
FIMs and FPMs are synchronized.
diagnose sys confsync status | grep in_sy
FIM10E3E16000040, Slave, uptime=346.99, priority=2, slot_id=1:2, idx=1, flag=0x0, in_sync=1
FIM04E3E16000010, Master, uptime=69398.91, priority=1, slot_id=1:1, idx=0, flag=0x0, in_sync=1
FPM20E3E17900217, Slave, uptime=69387.74, priority=20, slot_id=1:4, idx=2, flag=0x64, in_sync=1
FPM20E3E17900217, Slave, uptime=69387.74, priority=20, slot_id=1:4, idx=2, flag=0x4, in_sync=1
FIM04E3E16000010, Master, uptime=69398.91, priority=1, slot_id=1:1, idx=0, flag=0x0, in_sync=1
FIM10E3E16000040, Slave, uptime=346.99, priority=2, slot_id=1:2, idx=1, flag=0x0, in_sync=1
FIM04E3E16000010, Master, uptime=69398.91, priority=1, slot_id=1:1, idx=0, flag=0x0, in_sync=1
FIM10E3E16000040, Slave, uptime=346.99, priority=2, slot_id=1:2, idx=1, flag=0x0, in_sync=1
FPM20E3E17900217, Slave, uptime=69387.74, priority=20, slot_id=1:4, idx=2, flag=0x64, in_sync=1
FIMs and FPMs that are missing or that show in_sync=0 are not synchronized. To synchronize an FIM or FPM
that is not synchronized, log into the CLI of the FIM or FPM and restart it using the execute reboot
command.If this does not solve the problem, contact Fortinet Support at https://support.fortinet.com.
The example output also shows that the uptime of the FIM in slot 2 is lower than the uptime of the other modules,
indicating that the FIM in slot 2 has recently restarted.
If you enter the diagnose sys confsync status | grep in_sy command before the FIM has
completely restarted, it will not appear in the command output. As well, the Configuration Sync Monitor will
temporarily show that it is not synchronized.
Upgrading FPM firmware
Use the following procedure to upgrade the firmware running on an individual FPM. To perform the upgrade, you must
enter a command from the primary FIM CLI to allow ELBC communication with the FPM. Then you can just log in to the
FPM GUI or CLI and perform the firmware upgrade.
During this procedure, the FPM will not be able to process traffic. However, the other FPMs and the FIMs should
continue to operate normally.
After verifying that the FPM is running the right firmware, you must log back into the primary FIM CLI and return the
FPM to normal operation.
1. Log in to the primary FIM CLI and enter the following command:
diagnose load-balance switch set-compatible <slot> enable elbc
Where <slot> is the number of the FortiGate-7000 slot containing the FPM to be upgraded.
2. Log in to the FPM GUI or CLI using its special port number (for example, for the FPM in slot 3, browse to
https://192.168.1.99:44303 to connect to the GUI) and perform a normal firmware upgrade of the FPM.
3. After the FPM restarts, verify that the new firmware has been installed.
You can do this from the FPM GUI dashboard or from the FPM CLI using the get system status command.
4. Verify that the configuration has been synchronized. The following command output shows the sync status of a
FortiGate-7040E. The field in_sync=1 indicates that the configurations of the FIMs and FPMs are synchronized.
FortiGate-7030E 6.2.3 System Guide 33
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/496f257b-1a0a-11e9-9685-f8bc1258b856/fortigate-7030E-system-guide.pdf
|
33
|
Firmware upgrades Fortinet Technologies Inc.
diagnose sys confsync status | grep in_sy
FIM10E3E16000040, Slave, uptime=69346.99, priority=2, slot_id=1:2, idx=1, flag=0x0, in_sync=1
FIM04E3E16000010, Master, uptime=69398.91, priority=1, slot_id=1:1, idx=0, flag=0x0, in_sync=1
FPM20E3E17900217, Slave, uptime=387.74, priority=20, slot_id=1:4, idx=2, flag=0x64, in_sync=1
FPM20E3E17900217, Slave, uptime=387.74, priority=20, slot_id=1:4, idx=2, flag=0x4, in_sync=1
FIM04E3E16000010, Master, uptime=69398.91, priority=1, slot_id=1:1, idx=0, flag=0x0, in_sync=1
FIM10E3E16000040, Slave, uptime=69346.99, priority=2, slot_id=1:2, idx=1, flag=0x0, in_sync=1
FIM04E3E16000010, Master, uptime=69398.91, priority=1, slot_id=1:1, idx=0, flag=0x0, in_sync=1
FIM10E3E16000040, Slave, uptime=69346.99, priority=2, slot_id=1:2, idx=1, flag=0x0, in_sync=1
FPM20E3E17900217, Slave, uptime=387.74, priority=20, slot_id=1:4, idx=2, flag=0x64, in_sync=1
FIMs and FPMs that are missing or that show in_sync=0 are not synchronized. To synchronize an FIM or FPM
that is not synchronized, log into the CLI of the FIM or FPM and restart it using the execute reboot command.
If this does not solve the problem, contact Fortinet Support at https://support.fortinet.com.
The command output also shows that the uptime of the FPM in slot 4 is lower than the uptime of the other
modules, indicating that the FPM in slot 4 has recently restarted.
If you enter the diagnose sys confsync status | grep in_sy command before the FIM has
completely restarted, it will not appear in the command output. As well, the Configuration Sync Monitor will
temporarily show that it is not synchronized.
5. Once the FPM is operating normally, log back in to the primary FIM CLI and enter the following command to reset
the FPM to normal operation:
diagnose load-balance switch set-compatible <slot> disable
Configuration synchronization errors will occur if you do not reset the FPM to normal operation.
Installing FIM firmware from the BIOS after a reboot
Use the following procedure to upload firmware from a TFTP server to an FIM. The procedure involves creating a
connection between the TFTP server and one of the FIM MGMT interfaces. You don't have to use a MGMT interface on
the FIM that you are upgrading.
This procedure also involves connecting to the FIM CLI using a FortiGate-7000 front panel System Management
Module console port. From the console session, the procedure describes how to restart the FIM, interrupting the boot
process, and follow FIM BIOS prompts to install the firmware.
During this procedure, the FIM will not be able to process traffic. However, the other FIM and the FPMs should continue
to operate normally.
1. Set up a TFTP server and copy the firmware file to the TFTP server default folder.
2. Set up your network to allow traffic between the TFTP server and one of the FIM MGMT interfaces.
If the MGMT interface you are using is one of the MGMT interfaces connected as a LAG to a switch, you must
shutdown or disconnect all of the other interfaces that are part of the LAG from the switch. This includes MGMT
interfaces from both FIMs.
3. Using the console cable supplied with your FortiGate-7000, connect the SMM Console 1 port on the FortiGate7000 to the USB port on your management computer.
4. 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.
5. Press Ctrl-T to enter console switch mode.
6. Repeat pressing Ctrl-T until you have connected to the FIM to be updated. Example prompt for the FIM in slot 2:
<Switching to Console: FIM02 (9600)>
FortiGate-7030E 6.2.3 System Guide 34
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/496f257b-1a0a-11e9-9685-f8bc1258b856/fortigate-7030E-system-guide.pdf
|
34
|
Firmware upgrades Fortinet Technologies Inc.
7. Optionally log in to the FIM's CLI.
8. Reboot the FIM.
You can do this using the execute reboot command from the CLI or by pressing the power switch on the FIM
front panel.
9. When the FIM starts up, follow the boot process in the terminal session, and press any key when prompted to
interrupt the boot process.
10. To set up the TFTP configuration, press C.
11. Use the BIOS menu to set the following. Change settings only if required.
[P]: Set image download port: MGMT1 (the connected MGMT interface.)
[D]: Set DHCP mode: Disabled
[I]: Set local IP address: The IP address of the MGMT interface that you want to use to connect to the
TFTP server. This address must not be the same as the FortiGate-7000 management IP address and cannot
conflict with other addresses on your network.
[S]: Set local Subnet Mask: Set as required for your network.
[G]: Set local gateway: Set as required for your network.
[V]: Local VLAN ID: Should be set to <none>. (use -1 to set the Local VLAN ID to <none>.)
[T]: Set remote TFTP server IP address: The IP address of the TFTP server.
[F]: Set firmware image file name: The name of the firmware image file that you want to install.
12. To quit this menu, press Q.
13. To review the configuration, press R.
To make corrections, press C and make the changes as required. When the configuration is correct, proceed to the
next step.
14. To start the TFTP transfer, press T.
The firmware image is uploaded from the TFTP server and installed on the FIM. The FIM then restarts with its
configuration reset to factory defaults. After restarting, the FIM configuration is synchronized to match the
configuration of the primary FIM. The FIM restarts again and can start processing traffic.
15. Once the FIM restarts, verify that the correct firmware is installed.
You can do this from the FIM GUI dashboard or from the FPM CLI using the get system status command.
16. Verify that the configuration has been synchronized.
The following command output shows the sync status of a FortiGate-7040E. The field in_sync=1 indicates that
the configurations of the FIMs and FPMs are synchronized.
diagnose sys confsync status | grep in_sy
FIM10E3E16000040, Slave, uptime=346.99, priority=2, slot_id=1:2, idx=1, flag=0x0, in_sync=1
FIM04E3E16000010, Master, uptime=69398.91, priority=1, slot_id=1:1, idx=0, flag=0x0, in_sync=1
FPM20E3E17900217, Slave, uptime=69387.74, priority=20, slot_id=1:4, idx=2, flag=0x64, in_sync=1
FPM20E3E17900217, Slave, uptime=69387.74, priority=20, slot_id=1:4, idx=2, flag=0x4, in_sync=1
FIM04E3E16000010, Master, uptime=69398.91, priority=1, slot_id=1:1, idx=0, flag=0x0, in_sync=1
FIM10E3E16000040, Slave, uptime=346.99, priority=2, slot_id=1:2, idx=1, flag=0x0, in_sync=1
FIM04E3E16000010, Master, uptime=69398.91, priority=1, slot_id=1:1, idx=0, flag=0x0, in_sync=1
FIM10E3E16000040, Slave, uptime=346.99, priority=2, slot_id=1:2, idx=1, flag=0x0, in_sync=1
FPM20E3E17900217, Slave, uptime=69387.74, priority=20, slot_id=1:4, idx=2, flag=0x64, in_sync=1
FIMs and FPMs that are missing or that show in_sync=0 are not synchronized. To synchronize an FIM or FPM
that is not synchronized, log into the CLI of the FIM or FPM and restart it using the execute reboot command.
If this does not solve the problem, contact Fortinet Support at https://support.fortinet.com.
The command output also shows that the uptime of the FIM in slot 2 is lower than the uptime of the other modules,
indicating that the FIM in slot 2 has recently restarted.
FortiGate-7030E 6.2.3 System Guide 35
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/496f257b-1a0a-11e9-9685-f8bc1258b856/fortigate-7030E-system-guide.pdf
|
35
|
Firmware upgrades Fortinet Technologies Inc.
If you enter the diagnose sys confsync status | grep in_sy command before the FIM has
restarted, it will not appear in the command output. As well, the Configuration Sync Monitor will temporarily show
that it is not synchronized.
Installing FPM firmware from the BIOS after a reboot
Use the following procedure to upload firmware from a TFTP server to an FPM. To perform the upgrade, you must enter
a command from the primary FIM CLI to allow the FPM BIOS to communicate through an FIM MGMT interface. The
procedure involves creating a connection between the TFTP server and one of the FIM MGMT interfaces.
This procedure also involves connecting to the FPM CLI using a FortiGate-7000 front panel SMM console port,
rebooting the FPM, interrupting the boot from the console session, and following FPM BIOS prompts to install the
firmware.
During this procedure, the FPM will not be able to process traffic. However, the other FPMs and the FIMs should
continue to operate normally.
After you verify that the FPM is running the right firmware, you must log back in to the primary FIM CLI and return the
FPM to normal operation.
1. Set up a TFTP server and copy the firmware file into the TFTP server default folder.
2. Log into to the primary FIM CLI and enter the following command:
diagnose load-balance switch set-compatible <slot> enable bios
Where <slot> is the number of the FortiGate-7000 slot containing the FPM to be upgraded.
3. Set up your network to allow traffic between the TFTP server and a MGMT interface of one of the FIMs.
You can use any MGMT interface of either of the FIMs. When you set up the FPM TFTP settings below, you select
the FIM that can connect to the TFTP server. If the MGMT interface you are using is one of the MGMT interfaces
connected as a LAG to a switch, you must shutdown or disconnect all of the other interfaces that are part of the
LAG from the switch. This includes MGMT interfaces from both FIMs
4. Using the console cable supplied with your FortiGate-7000, connect the SMM Console 1 port on the FortiGate7000 to the USB port on your management computer.
5. 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.
6. Press Ctrl-T to enter console switch mode.
7. Repeat pressing Ctrl-T until you have connected to the module to be updated. Example prompt:
<Switching to Console: FPM03 (9600)>
8. Optionally log into the FPM's CLI.
9. Reboot the FPM.
You can do this using the execute reboot command from the FPM's CLI or by pressing the power switch on the
FPM front panel.
10. When the FPM starts up, follow the boot process in the terminal session and press any key when prompted to
interrupt the boot process.
11. To set up the TFTP configuration, press C.
12. Use the BIOS menu to set the following. Change settings only if required.
[P]: Set image download port: FIM01 (the FIM that can communicate with the TFTP server).
[D]: Set DHCP mode: Disabled.
FortiGate-7030E 6.2.3 System Guide 36
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/496f257b-1a0a-11e9-9685-f8bc1258b856/fortigate-7030E-system-guide.pdf
|
36
|
Firmware upgrades Fortinet Technologies Inc.
[I]: Set local IP address: The IP address of the MGMT interface of the selected FIM that you want to
use to connect to the TFTP server. This address must not be the same as the FortiGate-7000 management IP
address and cannot conflict with other addresses on your network.
[S]: Set local Subnet Mask: Set as required for your network.
[G]: Set local gateway: Set as required for your network.
[V]: Local VLAN ID: Should be set to <none>. (use -1 to set the Local VLAN ID to <none>.)
[T]: Set remote TFTP server IP address: The IP address of the TFTP server.
[F]: Set firmware image file name: The name of the firmware image file that you want to install.
13. To quit this menu, press Q.
14. To review the configuration, press R.
To make corrections, press C and make the changes as required. When the configuration is correct proceed to the
next step.
15. To start the TFTP transfer, press T.
The firmware image is uploaded from the TFTP server and installed on the FPM. The FPM then restarts with its
configuration reset to factory defaults. After restarting, the FPM configuration is synchronized to match the
configuration of the primary FPM. The FPM restarts again and can start processing traffic.
16. Once the FPM restarts, verify that the correct firmware is installed.
You can do this from the FPM GUI dashboard or from the FPM CLI using the get system status command.
17. Verify that the configuration has been synchronized.
The following command output shows the sync status of a FortiGate-7040E. The field in_sync=1 indicates that
the configurations of the FIMs and FPMs are synchronized.
diagnose sys confsync status | grep in_sy
FIM10E3E16000040, Slave, uptime=69346.99, priority=2, slot_id=1:2, idx=1, flag=0x0, in_sync=1
FIM04E3E16000010, Master, uptime=69398.91, priority=1, slot_id=1:1, idx=0, flag=0x0, in_sync=1
FPM20E3E17900217, Slave, uptime=387.74, priority=20, slot_id=1:4, idx=2, flag=0x64, in_sync=1
FPM20E3E17900217, Slave, uptime=387.74, priority=20, slot_id=1:4, idx=2, flag=0x4, in_sync=1
FIM04E3E16000010, Master, uptime=69398.91, priority=1, slot_id=1:1, idx=0, flag=0x0, in_sync=1
FIM10E3E16000040, Slave, uptime=69346.99, priority=2, slot_id=1:2, idx=1, flag=0x0, in_sync=1
FIM04E3E16000010, Master, uptime=69398.91, priority=1, slot_id=1:1, idx=0, flag=0x0, in_sync=1
FIM10E3E16000040, Slave, uptime=69346.99, priority=2, slot_id=1:2, idx=1, flag=0x0, in_sync=1
FPM20E3E17900217, Slave, uptime=387.74, priority=20, slot_id=1:4, idx=2, flag=0x64, in_sync=1
FIMs and FPMs that are missing or that show in_sync=0 are not synchronized. To synchronize an FIM or FPM
that is not synchronized, log into the CLI of the FIM or FPM and restart it using the execute reboot command .
If this does not solve the problem, contact Fortinet Support at https://support.fortinet.com.
The command output also shows that the uptime of the FPM in slot 4 is lower than the uptime of the other
modules, indicating that the FPM in slot 4 has recently restarted.
If you enter the diagnose sys confsync status | grep in_sy command before the FPM has
restarted, it will not appear in the command output. As well, the Configuration Sync Monitor will temporarily show
that it is not synchronized.
18. Once the FPM is operating normally, log back in to the primary FIM CLI and enter the following command to reset
the FPM to normal operation:
diagnose load-balance switch set-compatible <slot> disable
Configuration synchronization errors will occur if you do not reset the FPM to normal operation.
FortiGate-7030E 6.2.3 System Guide 37
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/496f257b-1a0a-11e9-9685-f8bc1258b856/fortigate-7030E-system-guide.pdf
|
37
|
Firmware upgrades Fortinet Technologies Inc.
Synchronizing FIMs and FPMs after upgrading the primary FIM
firmware from the BIOS
After you install firmware on the primary FIM from the BIOS after a reboot, the firmware version and configuration of the
primary FIM will most likely be not be synchronized with the other FIMs and FPMs. You can verify this from the primary
FIM CLI using the diagnose sys confsync status | grep in_sy command. The in_sync=0 entries in
the following example output show that the management board (serial number ending in 10) is not synchronized with
the other FIM and the FPMs shown in the example.
diagnose sys confsync status | grep in_sy
FIM10E3E16000040, Slave, uptime=69346.99, priority=2, slot_id=1:2, idx=1, flag=0x0, in_sync=0
FIM04E3E16000010, Master, uptime=69398.91, priority=1, slot_id=1:1, idx=0, flag=0x0, in_sync=1
FPM20E3E17900217, Slave, uptime=69387.74, priority=20, slot_id=1:4, idx=2, flag=0x64, in_sync=0
FIM04E3E16000010, Master, uptime=69398.91, priority=1, slot_id=1:1, idx=0, flag=0x0, in_sync=1
...
You can also verify synchronization status from the primary FIM Configuration Sync Monitor.
To re-synchronize the FortiGate-7000, which has the effect of resetting the other FIM and the FPMs, re-install firmware
on the primary FIM.
You can also manually install firmware on each individual FIM and FPM from the BIOS after a
reboot. This manual process is just as effective as installing the firmware for a second time on
the primary FIM to trigger synchronization to the FIM and the FPMs, but takes much longer.
1. Log into the primary FIM GUI.
2. Install a firmware build on the primary FIM from the GUI or CLI. The firmware build you install on the primary FIM
can either be the same firmware build or a different one.
Installing firmware synchronizes the firmware build and configuration from the primary FIM to the other FIM and
the FPMs.
3. Check the synchronization status from the Configuration Sync Monitor or using the diagnose sys confsync
status | grep in_sy command. The following example ForGate-7040E shows that the primary FIM is
synchronized with the other FIM and all of the FPMs because each line includes in_sync=1:
diagnose sys confsync status | grep in_sy
FIM10E3E16000040, Slave, uptime=69346.99, priority=2, slot_id=1:2, idx=1, flag=0x0, in_sync=1
FIM04E3E16000010, Master, uptime=69398.91, priority=1, slot_id=1:1, idx=0, flag=0x0, in_sync=1
FPM20E3E17900217, Slave, uptime=69387.74, priority=20, slot_id=1:4, idx=2, flag=0x64, in_sync=1
FPM20E3E17900217, Slave, uptime=69387.74, priority=20, slot_id=1:4, idx=2, flag=0x4, in_sync=1
FIM04E3E16000010, Master, uptime=69398.91, priority=1, slot_id=1:1, idx=0, flag=0x0, in_sync=1
FIM10E3E16000040, Slave, uptime=69346.99, priority=2, slot_id=1:2, idx=1, flag=0x0, in_sync=1
FIM04E3E16000010, Master, uptime=69398.91, priority=1, slot_id=1:1, idx=0, flag=0x0, in_sync=1
FIM10E3E16000040, Slave, uptime=69346.99, priority=2, slot_id=1:2, idx=1, flag=0x0, in_sync=1
FPM20E3E17900217, Slave, uptime=69387.74, priority=20, slot_id=1:4, idx=2, flag=0x64, in_sync=1
FortiGate-7030E 6.2.3 System Guide 38
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/496f257b-1a0a-11e9-9685-f8bc1258b856/fortigate-7030E-system-guide.pdf
|
38
|
FortiGate-7030E System Management Module
The FortiGate-7030E chassis includes a System Management Module (SMM) or shelf manager, located at the top right
of the chassis front panel. The SMM is factory installed and configured and is not field replaceable.
FortiGate-7030E SMM front panel
Status, Alarm,
Temp, Power
LEDs
Fan and PSU
(power supply)
LEDs
MGMT Ethernet
Interface
Console 1
Connection
LEDs
H8S Mode
LED
H8S Mode
Select Button
Console 2
Connection
LEDs
Retention
Screw
Retention
Screw
Console 1 RJ-45
RS-232
Serial Interface
Console 1 Connection
Change Button
Console 2 Connection
Change Button
Console 2 RJ-45
RS-232
Serial Interface
The SMM 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 SMM includes LED indicators that report on the status of many of the chassis components, including fan trays and
power supplies. You can also use the SMM console ports to connect to the SMM CLI and to the CLI of the modules in
chassis slots 1 to 6.
The SMM 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 SMM through the module's IPMB. FIM and FPM module power on/off requires authorization
from the SMM and the SMM 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 SMM SMC SDI. You can connect a serial cable to the SMM console ports
to connect to the SMM 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.
FortiGate-7030E 6.2.3 System Guide 39
Fortinet Technologies Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/496f257b-1a0a-11e9-9685-f8bc1258b856/fortigate-7030E-system-guide.pdf
|
39
|
FortiGate-7030E System Management Module Fortinet Technologies Inc.
System Management Module failure
If the SSM fails, you should RMA the chassis. The chassis and the modules in it will continue to operate with no
functioning SMM until you can replace the chassis. If there is no functioning SMM, the chassis fans operate at
maximum speed and the FIM and FPM modules in the chassis switch to standalone mode and manage their own
power.
System Management Module LEDs
The following table describes the SMM LED indicators:
FortiGate-7030E SMM LEDs
LED State Description
Status Off The SMM is powered off or not initialized.
Solid red The SMM is not operating normally either because it is
starting up or because it has failed.
Solid green The SMM has started up and is operating normally.
Blinking green The SMM is passive.
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 SMM
increases fan speed to increase cooling and reduce the
temperature.
FortiGate-7030E 6.2.3 System Guide 40
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/496f257b-1a0a-11e9-9685-f8bc1258b856/fortigate-7030E-system-guide.pdf
|
40
|
FortiGate-7030E System Management Module Fortinet Technologies Inc.
LED State Description
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 SMM 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 SMM 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.
Power Solid green Normal operation.
Blinking green Chassis 12V disabled. This means that the administrator has
entered commands into the SMM CLI to power off the PSU
main 12V outputs. All fans, FIM and FPM modules are
completely powered off but the SMM is still running.
Red Chassis 12V enabled but not OK. This means the SMM 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). SMM 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)
Off Fan tachometer sensors disabled. This could happen if the
administrator disabled them from the SMM 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.
FortiGate-7030E 6.2.3 System Guide 41
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/496f257b-1a0a-11e9-9685-f8bc1258b856/fortigate-7030E-system-guide.pdf
|
41
|
FortiGate-7030E System Management Module Fortinet Technologies Inc.
LED State Description
PSU (LEDs for each of four
PSUs)
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.
Console 1 and 2 Off This console port is not connected or is connected to the
SMM 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 SMM alarm levels
Minor, major and critical alarms are defined based on both IPMI, ATCA, and Telco standards for naming alarms.
l 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).
l 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 SMM CLI to get details about alarm sensors, thresholds, and the events that trigger alarms.
Using the console ports
The SMM 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 SMM 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.
FortiGate-7030E 6.2.3 System Guide 42
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/496f257b-1a0a-11e9-9685-f8bc1258b856/fortigate-7030E-system-guide.pdf
|
42
|
FortiGate-7030E System Management Module Fortinet Technologies Inc.
Each module, including the SMM, 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 SMM SMC SDI CLI
using the command serial set sdi enable <slot>. During normal operation you
may want to access the SMM SMC SDI CLI, you shouldn't normally require access to
individual module SMC SDI consoles.
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.
l Press the button to cycle through the FIM and FPM module FortiOS CLIs and disconnect this console.
l Press and hold the button to connect to the SMM 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 SMM 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 SMM 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:
l Press Ctrl-T multiple times 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.
l Press Ctrl-R multiple times to cycle through the FIM and FPM module SMC SDI CLIs 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 Enter to enable the CLI and log in. The
default administrator account for accessing the FortiOS CLIs is admin with no password. The default administrator
account for the SMC SDI CLIs is admin/admin.
When your session is complete you can press Ctrl-T until the prompt shows you have disconnected from the console.
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. Using the console cable supplied with your FortiGate-7000, connect the SMM Console 1 port on the FortiGate7000 to the USB port on your management computer.
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. Example prompt:
FortiGate-7030E 6.2.3 System Guide 43
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/496f257b-1a0a-11e9-9685-f8bc1258b856/fortigate-7030E-system-guide.pdf
|
43
|
FortiGate-7030E System Management Module Fortinet Technologies Inc.
<Switching to Console: FIM01 (9600)>
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 SMC SDI CLI of the FPM module in slot 3
Use the following steps to connect to the System Management Module SMC SDI CLI:
1. Using the console cable supplied with your FortiGate-7000, connect the SMM Console 1 port on the FortiGate7000 to the USB port on your management computer.
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. Press Ctrl-R to switch to the SMM SMC SDI CLI switching mode.
5. Repeat pressing Ctrl-R until you have connected to slot 3. Example prompt:
<Switching to Console: FIM03-MC (9600)>
6. 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.
7. You can begin entering commands at the admin@FPM03-MC # prompt.
8. When your session is complete, enter the exit command to log out.
Changing the SMM admin account password
Use the following procedure to change the SMM 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.
2. Use the command user set password <user-id> [<password>] to add a password for the admin
account. For example:
user set password 2 <password>
3. Enter and confirm a new password for the admin account.
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.
FortiGate-7030E 6.2.3 System Guide 44
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/496f257b-1a0a-11e9-9685-f8bc1258b856/fortigate-7030E-system-guide.pdf
|
44
|
FortiGate-7030E System Management Module Fortinet Technologies Inc.
Connecting to the SMM using an IPMI tool
You can install an IPMI tool on a management computer and then use this tool to send IPMI commands over your
network to the SMM MGMT interface. The IPMI tool allows you to communicate with the SMM by entering
IPMI commands. The IPMI commands are the same as the CLI commands described in this chapter but include
parameters such as the MGMT interface IP address and SMM administrator username and password.
For example, you can use the following IPMI command to change the SMM MGMT interface IP address:
sudo ipmitool -I lanplus -H <mgmt-ip> -k gkey -U <username> -P <password> lan set 4 ipaddr
172.20.120.30
Use the following IPMI command to change the SMM password:
sudo ipmitool -I lanplus -H <mgmt-ip> -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 <mgmt-ip> -k gkey -U <username> -P <password0> -t 0x82 sensor
FortiGate-7030E chassis slots IPMB addresses
The following table lists the IPMB addresses of the FortiGate-7030E chassis slots.
Chassis slot number Name IPMB Address (FRUID)
SMM MGMT 0x20
3 FPM3 0x86
1 FIM1 0x82
4 FPM4 0x88
You can use the IPMB address or chassis slot number to reference a chassis slot when entering commands in the SMM
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, 3, or 4) or an IPMB address number (0x82, 0x86, or 0x88)
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
FortiGate-7030E 6.2.3 System Guide 45
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/496f257b-1a0a-11e9-9685-f8bc1258b856/fortigate-7030E-system-guide.pdf
|
45
|
FortiGate-7030E System Management Module Fortinet Technologies Inc.
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.
\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 Disabled
COM 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 comlog getinfo
fortinetoem comlog print
Clear a module's comlog. Either comlog clear [reset_loc]
[chip_erase]
fortinetoem comlog clear
FortiGate-7030E 6.2.3 System Guide 46
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/496f257b-1a0a-11e9-9685-f8bc1258b856/fortigate-7030E-system-guide.pdf
|
46
|
FortiGate-7030E System Management Module Fortinet Technologies Inc.
Description SMC CLI Commands IPMI commands
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.
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 comlog setbaud
<speed>
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 SMM
SMC. From the SMM you can use the following commands from the active or passive SMM 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
FortiGate-7030E 6.2.3 System Guide 47
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/496f257b-1a0a-11e9-9685-f8bc1258b856/fortigate-7030E-system-guide.pdf
|
47
|
FortiGate-7030E System Management Module Fortinet Technologies Inc.
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 SMM CLI operations
The following table lists many of the operations you can perform from the SMM CLI and the commands you use to
perform them.
Action SMC CLI Commands IPMI Commands
Log into the CLI. Ctrl-R N/A
Log out of the CLI.
Available on the
passive module.
exit (followed by Ctrl-R) 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
Display status, power status N/A
FortiGate-7030E 6.2.3 System Guide 48
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/496f257b-1a0a-11e9-9685-f8bc1258b856/fortigate-7030E-system-guide.pdf
|
48
|
FortiGate-7030E System Management Module Fortinet Technologies Inc.
Action SMC CLI Commands IPMI Commands
budget and hot swap
state for all modules.
Available on the
passive module.
List the IPMI
channels.
channel list channel info [<channel-number>]
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 SMM
time. Available on
the passive module.
time get sel time get
Set the SMM time.
Available on the
passive module.
time set <yyy/mm/dd hh:mm:ss> sel time set <yyy/mm/dd
hh:mm:ss>
Synchronize all
module SMC times.
time sync N/A
List SMM 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
user set name <user-id> <name> user set name <user-id> <name>
FortiGate-7030E 6.2.3 System Guide 49
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/496f257b-1a0a-11e9-9685-f8bc1258b856/fortigate-7030E-system-guide.pdf
|
49
|
FortiGate-7030E System Management Module Fortinet Technologies Inc.
Action SMC CLI Commands IPMI Commands
on the passive
module.
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 SMM
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 default_sniff_
baud <speed>
N/A
Enable a console
connection from the
SMM to another
module.
serial set sdi enable <slot> N/A
Disable the console
connection between
the SMM and
another module.
Available on the
passive module.
serial set sdi disable <slot> N/A
FortiGate-7030E 6.2.3 System Guide 50
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/496f257b-1a0a-11e9-9685-f8bc1258b856/fortigate-7030E-system-guide.pdf
|
50
|
FortiGate-7030E System Management Module Fortinet Technologies Inc.
Action SMC CLI Commands IPMI Commands
Cold or warm reset a
module.
mc reset <slot> cold
mc reset <slot> warm
mc reset cold
mc reset warm
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 <channel> ipaddr <ip>
[<netmask>]
lan set <channel> macaddr <mac>
lan set <channel> defgw ipaddr
<ip>
lan set <channel> defgw macaddr
<mac>
lan set <channel> kgkey <value>
lan set <channel> krkey <value>
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
FortiGate-7030E 6.2.3 System Guide 51
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/496f257b-1a0a-11e9-9685-f8bc1258b856/fortigate-7030E-system-guide.pdf
|
51
|
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).
Fiabilité de la mise à la terre - Fiabilité de la mise à la terre de l'équipement monté en rack doit être maintenue. Une
attention particulière devrait être accordée aux connexions d'alimentation autres que les connexions directes au circuit
de dérivation (par exemple de l'utilisation de bandes de puissance).
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 des accessoires listés ou commutateurs, processeurs, serveurs et
similaire blades ou cartes doivent être listé UL ou équivalent.
FortiGate-7030E 6.2.3 System Guide 52
Fortinet Technologies Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/496f257b-1a0a-11e9-9685-f8bc1258b856/fortigate-7030E-system-guide.pdf
|
52
|
Cautions and warnings Fortinet Technologies Inc.
Refer to specific Product Model Data Sheet for Environmental Specifications (Operating Temperature, Storage
Temperature, Humidity, and Altitude).
Référez à la Fiche Technique de ce produit pour les caractéristiques environnementales (Température de
fonctionnement, température de stockage, humidité et l'altitude).
Safety
Moving parts - Hazardous moving parts. Keep away from moving fan blades.
Pièces mobiles - Pièces mobiles dangereuses. Se tenir éloigné des lames mobiles du ventilateur.
Warning: Equipment intended for installation in Restricted Access Location.
Avertissement: Le matériel est conçu pour être installé dans un endroit où l’accès est restreint.
Warning: A readily accessible disconnect device shall be incorporated in the building installation wiring.
Avertissement: Un dispositif de déconnexion facilement accessible doit être incorporé dans l'installation électrique du
bâtiment.
Battery - Risk of explosion if the battery is replaced by an incorrect type. Do not dispose of batteries in a fire. They may
explode. Dispose of used batteries according to your local regulations. IMPORTANT: Switzerland: Annex 4.10 of
SR814.013 applies to batteries.
Batterie - Risque d'explosion si la batterie est remplacée par un type incorrect. Ne jetez pas les batteries au feu. Ils
peuvent exploser. Jetez les piles usagées conformément aux réglementations locales. IMPORTANT: Suisse: l'annexe
4.10 de SR814.013 s’appliquent aux batteries.
警告
本電池如果更換不正確會有爆炸的危險
請依製造商說明書處理用過之電池
CAUTION:
There is a danger of explosion if a battery is incorrect replaced. Replace only with the same or equivalent type. Dispose
batteries of according to the manufacturer’s instructions. Disposing a battery into fire, a hot oven, mechanically
crushing, or cutting it can result in an explosion. Leaving a battery in an extremely hot environment can result in leakage
of flammable liquid, gas, or an explosion. If a battery is subjected to extremely low air pressure, it may result in leakage
of flammable liquid, gas, or an explosion.
WARNUNG:
Lithium-Batterie Achtung: Explosionsgefahr bei fehlerhafter Batteriewechsel. Ersetzen Sie nur den gleichen oder
gleichwertigen Typ. Batterien gemäß den Anweisungen des Herstellers entsorgen.
Beseitigung einer BATTERIE in Feuer oder einen heißen Ofen oder mechanisches Zerkleinern oder Schneiden einer
BATTERIE, die zu einer EXPLOSION führen kann.
Verlassen einer BATTERIE in einer extrem hohen Umgebungstemperatur, die zu einer EXPLOSION oder zum
Austreten von brennbarer Flüssigkeit oder Gas führen kann.
Eine BATTERIE, die einem extrem niedrigen Luftdruck ausgesetzt ist, der zu einer EXPLOSION oder zum Austreten
von brennbarer Flüssigkeit oder Gas führen kann.
CAUTION: Shock Hazard. Disconnect all power sources.
FortiGate-7030E 6.2.3 System Guide 53
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/496f257b-1a0a-11e9-9685-f8bc1258b856/fortigate-7030E-system-guide.pdf
|
53
|
Cautions and warnings Fortinet Technologies Inc.
ATTENTION: Risque d'électrocution. Débranchez toutes les sources d'alimentation.
Grounding - To prevent damage to your equipment, connections that enter from outside the building should pass
through a lightning / surge protector, and be properly grounded. Use an electrostatic discharge workstation (ESD) and/or
wear an anti-static wrist strap while you work. In addition to the grounding terminal of the plug, on the back panel, there
is another, separate terminal for earthing.
Mise à la terre - Pour éviter d’endommager votre matériel, assurez-vous que les branchements qui entrent à partir de
l’extérieur du bâtiment passent par un parafoudre / parasurtenseur et sont correctement mis à la terre. Utilisez un poste
de travail de décharge électrostatique (ESD) et / ou portez un bracelet anti-statique lorsque vous travaillez. Ce produit
possède une borne de mise à la terre qui est prévu à l’arrière du produit, à ceci s’ajoute 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 # 6 AWG and the connection is to be installed by a qualified
service personnel.
Ce produit a une borne de mise à la terre séparé sur le dos de l'appareil, en plus de la borne de mise à la terre de la fiche
de raccordement. Cette borne de mise à la terre séparée doit être connecté en permanence à la terre avec un
conducteur vert avec la taille bande jaune de minimum # 6 AWG et la connexion doit être installé par un personnel
qualifié.
Caution: Slide/rail mounted equipment is not to be used as a shelf or a work space.
Attention: Un équipement monté sur bâti ne doit pas être utilisé sur une étagère ou dans un espace de travail.
Fiber optic transceiver must be rated 3.3V, 22mA max, Laser Class 1, UL certified component.
Le transceiver optique doit avoir les valeurs nominales de 3.3 V, maximum 22 mA, Laser Class 1, homologué UL
FortiGate-7030E 6.2.3 System Guide 54
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/496f257b-1a0a-11e9-9685-f8bc1258b856/fortigate-7030E-system-guide.pdf
|
54
|
Regulatory notices
Federal Communication Commission (FCC) – USA
This device complies with Part 15 of FCC Rules. Operation is subject to the following two conditions:
(1) this device may not cause harmful interference, and
(2) this device must accept any interference received; including interference that may cause undesired operation.
This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to Part 15 of
the FCC Rules. These limits are designed to provide reasonable protection against harmful interference when the
equipment is operated in a commercial environment. This equipment generates, uses, and can radiate radio frequency
energy, and if it is not installed and used in accordance with the instruction manual, it may cause harmful interference to
radio communications. Operation of this equipment in a residential area is likely to cause harmful interference, in which
case the user will be required to correct the interference at his own expense.
WARNING: Any changes or modifications to this product not expressly approved by the party responsible for
compliance could void the user’s authority to operate the equipment.
Industry Canada Equipment Standard for Digital Equipment (ICES) –
Canada
CAN ICES-3 (A) / NMB-3 (A)
This digital apparatus does not exceed the Class A limits for radio noise emissions from digital apparatus set out in the
Radio Interference Regulations of the Canadian Department of Communications.
Cet appareil numérique n’émet pas de bruits radioélectriques dépassant les limites applicables aux appareils
numériques de la classe A prescrites dans le Règlement sur le brouillage radioélectrique édicte par le ministère des
Communications du Canada.
European Conformity (CE) - EU
This is a Class A product. In a domestic environment, this product may cause radio interference, in which case the user
may be required to take adequate measures.
FortiGate-7030E 6.2.3 System Guide 55
Fortinet Technologies Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/496f257b-1a0a-11e9-9685-f8bc1258b856/fortigate-7030E-system-guide.pdf
|
55
|
Regulatory notices Fortinet Technologies Inc.
Voluntary Control Council for Interference (VCCI) – Japan
この装置は、クラスＡ機器です。この装置を住宅環境で使用すると電波妨害を引き起こすことがあります。この場合には使
用者が適切な対策を講ずるよう要求されることがあります。ＶＣＣＩ－Ａ
Product Safety Electrical Appliance & Material (PSE) – Japan
日本では電気用品安全法(PSE)の規定により、同梱している電源コードは本製品の専用電源コードとして利用し、他の製
品に使用しないでください。
Bureau of Standards Metrology and Inspection (BSMI) – Taiwan
The presence conditions of the restricted substance (BSMI RoHS table) are available at the link below:
限用物質含有情況表 (RoHS Table) 請到以下 網址下載：
https://www.fortinet.com/bsmi
此為甲類資訊技術設備，於居住環境中使用時，可能會造成射頻擾動，在此種情況下，使用者會被要求採取某
些適當的對策。
英屬蓋曼群島商防特網股份有限公司台灣分公司
地址：台北市內湖區行愛路176號2樓
電話：(02) 27961666
China
此为A级产品，在生活环境中，该产品可能会造成无线电干扰。这种情况下，可能需要用户对其采取切实可行的
措施。
FortiGate-7030E 6.2.3 System Guide 56
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/496f257b-1a0a-11e9-9685-f8bc1258b856/fortigate-7030E-system-guide.pdf
|
56
|
Copyright© 2020 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 Fortinet’s
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 Fortinet’s 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.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/496f257b-1a0a-11e9-9685-f8bc1258b856/fortigate-7030E-system-guide.pdf
|
0
|
Administrator’s
Pocket Consultant
William R. Stanek
Author and Series Editor
Active
Directory ®
|
https://ptgmedia.pearsoncmg.com/images/9780735626485/samplepages/9780735626485.pdf
|
1
|
PUBLISHED BY
Microsoft Press
A Division of Microsoft Corporation
One Microsoft Way
Redmond, Washington 98052-6399
Copyright © 2009 by William Stanek
All rights reserved. No part of the contents of this book may be reproduced or transmitted in any
form or by any means without the written permission of the publisher.
Library of Congress Control Number: 2008940460
Printed and bound in the United States of America.
1 2 3 4 5 6 7 8 9 QWE 4 3 2 1 0 9
Distributed in Canada by H.B. Fenn and Company Ltd.
A CIP catalogue record for this book is available from the British Library.
Microsoft Press books are available through booksellers and distributors worldwide. For further
infor mation about international editions, contact your local Microsoft Corporation office or contact
Microsoft Press International directly at fax (425) 936-7329. Visit our Web site at www.microsoft.
com/mspress. Send comments to mspinput@microsoft.com.
Microsoft, Microsoft Press, Active Directory, Internet Explorer, MS, Windows, Windows NT,
Windows PowerShell, Windows Server, and Windows Vista are either registered trademarks or
trademarks of the Microsoft group of companies. Other product and company names mentioned
herein may be the trademarks of their respective owners.
The example companies, organizations, products, domain names, e-mail addresses, logos,
people, places, and events depicted herein are fictitious. No association with any real company,
organization, product, domain name, e-mail address, logo, person, place, or event is intended or
should be inferred.
This book expresses the author’s views and opinions. The information contained in this book is
provided without any express, statutory, or implied warranties. Neither the authors, Microsoft
Corporation, nor its resellers, or distributors will be held liable for any damages caused or alleged
to be caused either directly or indirectly by this book.
Acquisitions Editor: Martin DelRe
Developmental Editor: Karen Szall
Project Editor: Maria Gargiulo
Editorial Production: ICC Macmillan, Inc.
Technical Reviewer: Randy Muller; Technical Review services provided by Content
Master, a member of CM Group, Ltd.
Cover: Tom Draper Design
Body Part No. X15-25190
|
https://ptgmedia.pearsoncmg.com/images/9780735626485/samplepages/9780735626485.pdf
|
2
|
Contents at a Glance
Introduction xv
PART I IMPLEMENTING ACTIVE DIRECTORY
CHAPTER 1 Overview of Active Directory 3
CHAPTER 2 Installing New Forests, Domain Trees,
and Child Domains 29
CHAPTER 3 Deploying Writable Domain Controllers 73
CHAPTER 4 Deploying Read-Only Domain Controllers 105
PART II MANAGING ACTIVE DIRECTORY INFRASTRUCTURE
CHAPTER 5 Configuring, Maintaining, and Troubleshooting
Global Catalog Servers 139
CHAPTER 6 Configuring, Maintaining, and Troubleshooting
Operations Masters 167
CHAPTER 7 Managing Active Directory Sites, Subnets,
and Replication 189
PART III MAINTAINING AND RECOVERING ACTIVE DIRECTORY
CHAPTER 8 Managing Trusts and Authentication 227
CHAPTER 9 Maintaining and Recovering Active Directory 259
APPENDIX A Active Directory Utilities Reference 295
Index 321
|
https://ptgmedia.pearsoncmg.com/images/9780735626485/samplepages/9780735626485.pdf
|
3
| null |
https://ptgmedia.pearsoncmg.com/images/9780735626485/samplepages/9780735626485.pdf
|
4
|
v
What do you think of this book? We want to hear from you!
Microsoft is interested in hearing your feedback so we can continually improve our
books and learning resources for you. To participate in a brief online survey, please visit:
microsoft.com/learning/booksurvey
Contents
Introduction xv
PART I IMPLEMENTING ACTIVE DIRECTORY
Chapter 1 Overview of Active Directory 3
Understanding Directory Services . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Introducing Active Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Active Directory Domains 5
DNS Domains 6
Domain Controllers 8
Active Directory Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Active Directory Schema 12
Active Directory Components 14
Managing Active Directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Working with Active Directory 23
Active Directory Administration Tools 23
Chapter 2 Installing New Forests, Domain Trees,
and Child Domains 29
Preparing for Active Directory Installation . . . . . . . . . . . . . . . . . . . 29
Working with Directory Containers and Partitions 30
Establishing or Modifying Your Directory
Infrastructure 31
Establishing Functional Levels 36
Deploying Windows Server 2008 40
Creating Forests, Domain Trees, and Child Domains . . . . . . . . . . . 41
Installing the AD DS Binaries 41
Creating New Forests 42
|
https://ptgmedia.pearsoncmg.com/images/9780735626485/samplepages/9780735626485.pdf
|
5
|
vi Contents
Creating New Domain Trees 59
Creating New Child Domains 66
Chapter 3 Deploying Writable Domain Controllers 73
Preparing to Deploy or Decommission Domain Controllers . . . . 73
Adding Writable Domain Controllers . . . . . . . . . . . . . . . . . . . . . . . . 74
Installing Additional Writable Domain Controllers 75
Adding Writable Domain Controllers Using
Replication 76
Adding Writable Domain Controllers Using
Installation Media 83
Adding Writable Domain Controllers Using
Answer Files or the Command Line 85
Decommissioning Domain Controllers ....................... 88
Preparing to Remove Domain Controllers 88
Removing Additional Domain Controllers 90
Removing the Last Domain Controller 94
Removing Domain Controllers Using Answer
Files or the Command Line 95
Forcing the Removal of Domain Controllers . . . . . . . . . . . . . . . . . . 97
Restarting a Domain Controller in Directory
Services Restore Mode 97
Performing Forced Removal of Domain Controllers 99
Cleaning Up Metadata in the Active Directory Forest 102
Chapter 4 Deploying Read-Only Domain Controllers 105
Preparing to Deploy Read-Only Domain Controllers . . . . . . . . . 106
Adding RODCs to Domains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Adding RODCs Using Replication 109
Adding RODCs Using Answer Files or the
Command Line 115
Using Staged Installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Stage 1: Creating the RODC Account and
Preparing for Installation 120
Stage 2: Attaching the RODC and Finalizing
Installation 121
|
https://ptgmedia.pearsoncmg.com/images/9780735626485/samplepages/9780735626485.pdf
|
6
|
Contents vii
Performing Staged Installations Using the
Command Line or Answer Files 123
Decommissioning RODCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Setting Password Replication Policy . . . . . . . . . . . . . . . . . . . . . . . . 127
Password Replication Policy Essentials 127
Allowing and Denying Accounts 130
Managing Credentials on RODCs 132
Identifying Allowed or Denied Accounts 133
Resetting Credentials 134
Delegating Administrative Permissions 135
PART II MANAGING ACTIVE DIRECTORY
INFRASTRUCTURE
Chapter 5 Configuring, Maintaining, and Troubleshooting
Global Catalog Servers 139
Working with Global Catalog Servers ....................... 140
Deploying Global Catalog Servers . . . . . . . . . . . . . . . . . . . . . . . . . 141
Adding Global Catalog Servers 141
Monitoring and Verifying Global Catalog Promotion 143
Identifying Global Catalog Servers 149
Restoring Global Catalog Servers 150
Removing Global Catalog Servers 151
Controlling SRV Record Registration 152
Managing and Maintaining Universal Group
Membership Caching. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Universal Group Membership Caching Essentials 152
Enabling Universal Group Membership Caching 153
Monitoring and Troubleshooting Universal
Group Membership Caching 155
Managing and Maintaining Replication Attributes . . . . . . . . . . . 158
Understanding Global Catalog Search and
the Partial Attribute Set 158
Designating Replication Attributes 159
Monitoring and Troubleshooting Replication
Attributes 163
|
https://ptgmedia.pearsoncmg.com/images/9780735626485/samplepages/9780735626485.pdf
|
7
|
viii Contents
Managing and Maintaining Name Suffixes . . . . . . . . . . . . . . . . . . 163
Configuring User Principal Name Suffixes 164
Configuring Name Suffix Routing 165
Chapter 6 Configuring, Maintaining, and Troubleshooting
Operations Masters 167
Operations Master Essentials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
Introducing Operations Masters 168
Identifying Operations Masters 169
Planning for Operations Masters 169
Changing Operations Masters 170
Working with Operations Masters . . . . . . . . . . . . . . . . . . . . . . . . . 171
Managing Domain Naming Masters 172
Managing Infrastructure Masters 173
Managing PDC Emulators 175
Managing Relative ID Masters 177
Managing Schema Masters 180
Maintaining Operations Masters . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
Preparing Standby Operations Masters 181
Decommissioning Operations Masters 183
Reducing Operations Master Workload 183
Seizing Operations Master Roles 185
Troubleshooting Operations Masters 187
Chapter 7 Managing Active Directory Sites, Subnets,
and Replication 189
Implementing Sites and Subnets . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
Working with Sites 190
Setting Site Boundaries 190
Replication Essentials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
The Replication Model 191
Replication with Multiple Sites 192
SYSVOL Replication 193
Essential Services for Replication 193
|
https://ptgmedia.pearsoncmg.com/images/9780735626485/samplepages/9780735626485.pdf
|
8
|
Contents ix
Intrasite Versus Intersite Replication . . . . . . . . . . . . . . . . . . . . . . . . 194
Intrasite Replication 194
Intersite Replication 195
Developing Your Site Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
Mapping Your Network Structure 197
Designing Your Sites 198
Designing Your Intersite Replication Topology 198
Configuring Sites and Subnets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
Creating Sites 200
Creating Subnets 202
Adding Domain Controllers to Sites 203
Ensuring Clients Find Domain Controllers 205
Configuring Site Links and Intersite Replication . . . . . . . . . . . . . . 206
Understanding Site Links 206
Creating Site Links 208
Configuring Link Replication Schedules 210
Bridging Sites 212
Locating and Designating Bridgehead Servers 213
Locating ISTGs 216
Optimizing Site Link Configurations 217
Monitoring, Verifying, and Troubleshooting Replication . . . . . . 218
Monitoring Replication 218
Troubleshooting Replication 219
Generating Replication Topology 222
Verifying and Forcing Replication 222
PART III MAINTAINING AND RECOVERING ACTIVE
DIRECTORY
Chapter 8 Managing Trusts and Authentication 227
Active Directory Authentication and Trusts. . . . . . . . . . . . . . . . . . 227
Trust Essentials 227
Authentication Essentials 229
Authentication Across Domain Boundaries 232
Authentication Across Forest Boundaries 232
|
https://ptgmedia.pearsoncmg.com/images/9780735626485/samplepages/9780735626485.pdf
|
9
|
x Contents
Working with Domain and Forest Trusts . . . . . . . . . . . . . . . . . . . . 233
Examining Trusts 234
Establishing Trusts 236
Creating External Trusts 240
Creating Shortcut Trusts 244
Creating Forest Trusts 247
Creating Realm Trusts 251
Removing Manually Created Trusts 253
Verifying and Troubleshooting Trusts 254
Configuring Selective Authentication . . . . . . . . . . . . . . . . . . . . . . . 255
Enabling or Disabling Selective Authentication
for External Trusts 256
Enabling or Disabling Selective Authentication
for Forest Trusts 256
Granting the Allowed To Authenticate Permission 257
Chapter 9 Maintaining and Recovering Active Directory 259
Protecting Objects from Accidental Deletion . . . . . . . . . . . . . . . . 259
Starting and Stopping Active Directory Domain Services . . . . . 260
Setting the Functional Level of Domains and Forests . . . . . . . . . 261
Configuring Deleted Item Retention . . . . . . . . . . . . . . . . . . . . . . . 262
Configuring the Windows Time Service . . . . . . . . . . . . . . . . . . . . . 263
Understanding Windows Time 264
Working with W32tm 265
Checking the Windows Time Configuration 266
Configuring an Authoritative Time Source 268
Troubleshooting Windows Time Services 269
Configuring Windows Time Settings in Group Policy 269
Backing Up and Recovering Active Directory . . . . . . . . . . . . . . . . 277
Active Directory Backup and Recovery Essentials 278
Backing Up and Restoring the System State 280
Performing a Nonauthoritative Restore of
Active Directory 281
Performing an Authoritative Restore of Active
Directory 282
|
https://ptgmedia.pearsoncmg.com/images/9780735626485/samplepages/9780735626485.pdf
|
10
|
Contents xi
Restoring Sysvol Data 285
Recovering by Installing a New Domain Controller 286
Maintaining the Directory Database . . . . . . . . . . . . . . . . . . . . . . . 286
Understanding Directory Database Operations 287
Checking for Free Space in the Directory Database 287
Performing Offline Defragmentation 288
Moving the Directory Database 290
Appendix A Active Directory Utilities Reference 295
Index 321
What do you think of this book? We want to hear from you!
Microsoft is interested in hearing your feedback so we can continually improve our
books and learning resources for you. To participate in a brief online survey, please visit:
microsoft.com/learning/booksurvey
|
https://ptgmedia.pearsoncmg.com/images/9780735626485/samplepages/9780735626485.pdf
|
11
| null |
https://ptgmedia.pearsoncmg.com/images/9780735626485/samplepages/9780735626485.pdf
|
12
|
xiii
Acknowledgments
You know you’ve been at this thing called writing a long time when people ask
how many books you’ve written and you just have no idea. For many years, my
bio stated that I was the author of more than 25 books. Several times my publishers
have asked me to update the bio with a more precise number, so around number 61
I started counting to keep everyone happy. That was about five, six, seven years ago,
so I’m now getting close to 100 or thereabouts. ;-)
For me, it’s always been about the craft of writing. I love writing, and I love challenging projects most of all. The challenge in writing a day-to-day administrator’s
guide to Active Directory is that there’s so much I’d like to cover, but pocket consultants aren’t meant to be all-in-one references. Pocket consultants are meant to be
portable and readable—the kind of book you use to solve problems and get the job
done wherever you might be. With that in mind, I have to continually make sure I
focus on the core of Active Directory administration. The result is the book you hold
in your hand, which I hope you’ll agree is one of the best practical, portable guides
to Active Directory.
As I’ve stated in the three dozen or so pocket consultants I’ve written, the team
at Microsoft Press is topnotch. Maria Gargiulo was instrumental throughout the
writing process. She helped ensure that I had what I needed to write the book and
was my primary contact at Microsoft. Martin DelRe was the acquisitions editor
for the project. He believed in the book from the beginning and was really great
to work with. Completing and publishing the book wouldn’t have been possible
without their help!
Unfortunately for the writer (but fortunately for readers), writing is only one
part of the publishing process. Next came editing and author review. I must say,
Microsoft Press has the most thorough editorial and technical review process I’ve
seen anywhere—and I’ve written a lot of books for many different publishers. John
Pierce managed the editorial process. He helped me stay on track and on schedule.
Randy Muller was the technical editor for the book. As copyeditor, Shannon Leavitt
also did a good job. Thank you so much!
I would like to thank Chris Nelson for his help during this project. Chris is terrific
to work with and always willing to help any way he can. Thanks also to everyone else
at Microsoft who has helped at many points of my writing career and been there
when I needed them the most.
Thanks also to Studio B, The Salkind Agency, and my agent Neil Salkind.
Hopefully, I haven’t forgotten anyone, but if I have, it was an oversight. Honest. ;-)
|
https://ptgmedia.pearsoncmg.com/images/9780735626485/samplepages/9780735626485.pdf
|
13
| null |
https://ptgmedia.pearsoncmg.com/images/9780735626485/samplepages/9780735626485.pdf
|
14
|
xv
Introduction
Active Directory Administrator’s Pocket Consultant is designed to be a concise
and compulsively usable resource for Windows administrators. This is the
readable resource guide you’ll want on your desk or in your pocket at all times. The
book discusses everything you need to perform the core administrative tasks for
Active Directory. Because the focus is on providing you with the maximum value in
a pocket-sized guide, you don’t have to wade through hundreds of pages of extraneous information to find what you’re looking for. Instead, you’ll find exactly what
you need to get the job done.
In short, the book is designed to be the one resource you consult whenever
you have questions regarding Active Directory administration. To this end, the
book concentrates on daily administration procedures, frequently performed
tasks, documented examples, and options that are representative but not necessarily inclusive. One of the goals is to keep the content so concise that the book
remains compact and easy to navigate while ensuring that the book is packed with
as much information as possible—making it a valuable resource. Thus, instead of
a hefty thousand-page tome or a lightweight hundred-page quick reference, you
get a valuable resource guide that can help you efficiently perform common tasks,
solve problems, and implement such advanced administration areas as establishing
cross-forest trusts, optimizing intersite replication, changing domain design, and
troubleshooting.
Who Is This Book For?
Active Directory Administrator’s Pocket Consultant covers Active Directory for small,
medium, and large organizations. The book is designed for:
N Current Windows and network administrators
N Support staff who maintain Windows networks
N Accomplished users who have some administrator responsibilities
N Administrators transferring from other platforms
To pack in as much information as possible, I had to assume that you have basic
networking skills and a basic understanding of Windows, and that Windows is
already installed on your systems. With this in mind, I don’t devote entire chapters
to understanding Windows architecture, installing Windows, or Windows networking. I do, however, provide complete details on the components of Active Directory
networks and how you can use these components. I cover installing domain controllers, configuring Active Directory sites, and much more.
|
https://ptgmedia.pearsoncmg.com/images/9780735626485/samplepages/9780735626485.pdf
|
15
|
xvi Introduction
I also assume that you are fairly familiar with Windows commands and procedures as well as the Windows user interface. If you need help learning Windows
basics, you should read the Windows documentation.
How Is This Book Organized?
Active Directory Administrator’s Pocket Consultant is designed to be used in the daily
administration of Active Directory, and as such, the book is organized by job-related
tasks rather than by features. Speed and ease of reference are essential parts of
this hands-on guide. The book has an expanded table of contents and an extensive
index for finding answers to problems quickly. Many other quick-reference features
have been added as well. These features include quick step-by-step instructions,
lists, tables with fast facts, and extensive cross-references. The book is organized
into both parts and chapters.
Active Directory is an extensible directory service that enables you to manage
network resources efficiently. Part I, “Implementing Active Directory,” reviews the
fundamental tasks you need for Active Directory administration. Chapter 1 provides an overview of tools, techniques, and concepts related to Active Directory.
Chapter 2 discusses installing forests, domain trees, and child domains. Updates to
Active Directory for Windows Server 2008 Release 2 (R2) are discussed in Chapter 1
and Chapter 2 as well. Chapter 3 details techniques for deploying writable domain
controllers and the tasks you’ll need to perform to set up domain controllers. Chapter 4
covers the deployment of read-only domain controllers. Together, these chapters
provide the detailed information you need to configure domains and forests,
whether you are deploying Active Directory Domain Services for the first time or
extending your existing infrastructure.
Part II, “Managing Active Directory Infrastructure,” discusses the core tools and
techniques you’ll use to manage Active Directory. In addition to their standard roles,
domain controllers can also act as global catalog servers and operations masters.
Chapter 5 explores techniques for configuring, maintaining, and troubleshooting
global catalog servers. Chapter 6 examines how you manage operations masters.
Chapter 7 describes your work with Active Directory sites, subnets, and replication.
You’ll learn the essentials for creating sites and associating subnets with sites. You’ll
also learn advanced techniques for managing site links and replication.
Part III, “Maintaining and Recovering Active Directory,” discusses the administrative tasks you’ll use to maintain Active Directory. Chapter 8 describes how to
manage trusts and authentication. You’ll learn how Active Directory authentication
works within domains, across domain boundaries, and across forest boundaries.
You’ll also learn how trusts are used and established. Chapter 9 provides techniques
you can use to maintain, monitor, and troubleshoot Active Directory infrastructure.
In addition to learning techniques for backing up and recovering Active Directory,
you’ll also learn how to perform essential maintenance tasks and how to configure
related options and services, including Windows Time service.
|
https://ptgmedia.pearsoncmg.com/images/9780735626485/samplepages/9780735626485.pdf
|
16
|
Introduction xvii
Finally, Appendix A provides a quick reference for command-line utilities you’ll
use when working with Active Directory.
Conventions Used in This Book
I’ve used a variety of elements to help keep the text clear and easy to follow. You’ll
find code terms and listings in monospace type, except when I tell you to actually type a command. In that case, the command appears in bold type. When I
introduce and define a new term, I put it in italics.
Other conventions include:
N Notes To provide details on a point that needs emphasis
N Best Practices To examine the best technique to use when working with
advanced configuration and administration concepts
N Cautions To warn you of potential problems you should look out for
N Real World To provide real-world advice for advanced topics
N Security Alerts To point out important security issues
N Tips To offer helpful hints or additional information
I truly hope you find that Active Directory Administrator’s Pocket Consultant
provides everything you need to perform essential Active Directory administrative
tasks as quickly and efficiently as possible. You’re welcome to send your thoughts to
me at williamstanek@aol.com. Thank you.
Find Additional Content Online
As new or updated material becomes available that complements your book, it will
be posted online on the Microsoft Press Online Windows Server and Client Web site.
The type of material you might find includes updates to book content, articles, links
to companion content, errata, sample chapters, and more. This Web site is available
at www.microsoft.com/learning/books/online/serverclient and is updated periodically.
Support
Every effort has been made to ensure the accuracy of this book. Microsoft Press
provides corrections for books through the World Wide Web at the following
address:
http://www.microsoft.com/mspress/support
|
https://ptgmedia.pearsoncmg.com/images/9780735626485/samplepages/9780735626485.pdf
|
17
|
xviii Introduction
If you have comments, questions, or ideas about this book, please send them to
Microsoft Press, using either of the following methods:
Postal mail:
Microsoft Press
Attn: Editor, Active Directory Administrator’s Pocket Consultant
One Microsoft Way
Redmond, WA 98052-6399
E-mail:
mspinput@microsoft.com
Please note that product support isn’t offered through these addresses. For
support information, visit Microsoft’s Web site at http://support.microsoft.com.
|
https://ptgmedia.pearsoncmg.com/images/9780735626485/samplepages/9780735626485.pdf
|
18
|
73
CHAPTER 3
Deploying Writable
Domain Controllers
N Preparing to Deploy or Decommission Domain Controllers 73
N Adding Writable Domain Controllers 74
N Decommissioning Domain Controllers 88
N Forcing the Removal of Domain Controllers 97
I
n this chapter, I provide tips and techniques for adding and removing writable
domain controllers. After setting up the initial domain controller in a domain,
you deploy additional domain controllers to increase fault tolerance and improve
operational efficiency. Just as you establish a server as a domain controller by
installing Active Directory Domain Services (AD DS), you decommission a domain
controller by removing AD DS. The decommissioned domain controller can then
be taken out of service, or it can act as a server.
Preparing to Deploy or Decommission Domain
Controllers
Before deploying or decommissioning domain controllers, you should create a
plan that lists any prerequisites, necessary postmodification changes, and overall impact on your network. Create your plan by reviewing “Preparing for Active
Directory Installation” in Chapter 2, ”Installing New Forests, Domain Trees, and
Child Domains.”
Domain controllers host the Active Directory database and handle related
operations. Active Directory uses a multimaster replication model that creates
a distributed environment where no single domain controller is authoritative
with regard to logon and authentication requests. This model allows any domain
controller to be used for logon and authentication. It also allows you to make
changes to standard directory information without regard to which domain
controller you
|
https://ptgmedia.pearsoncmg.com/images/9780735626485/samplepages/9780735626485.pdf
|
19
|
74 CHAPTER 3 Deploying Writable Domain Controllers
Domain controllers also can have special roles as operations masters and global
catalog servers. As discussed in Chapter 5, “Managing Operations Masters,” operations masters perform tasks that can be performed only by a single authoritative
domain controller. Global catalog servers store partial replicas of data from all domains in a forest to facilitate directory searches for resources in other domains and
to determine membership in universal groups.
When you establish the first domain controller in a forest, the domain controller
hosts the forestwide and domainwide operations master roles and also acts as the
global catalog server for the domain. When you establish the first domain controller
in a domain, the domain controller hosts the domainwide operations master roles
and also acts as the global catalog server for the domain.
Every domain in the enterprise should have at least two domain controllers. If a
domain has only one domain controller, you could lose the entire domain and all
related accounts if disaster strikes. Although you may be able to recover the domain
from a backup, you will have significant problems until the restore is completed. For
example, users may not be able to log on to the domain or obtain authenticated
access to domain resources.
Every site should have at least one domain controller. If a domain controller is
not available in a site, computers in the site will perform logon and authentication
activities with domain controllers in another site, which could significantly affect
response times.
Every site should have a global catalog server. If a global catalog server is not
available in a site, computers in the site will query a global catalog server in another
site when searching for resources in other domains in the forest. Global catalog
servers are also used during logon and authentication because they store universal
group membership information for all domains in the forest. If a global catalog
server isn’t available in the site and the universal group membership has not been
previously cached, the domain controller responding to a user’s logon or authentication request will need to obtain the required information from a global catalog
server in another site.
Adding Writable Domain Controllers
You establish a server as a domain controller by installing the necessary binaries
for the Active Directory Domain Services (AD DS) and then configuring the services
using the Active Directory Domain Services Installation Wizard (Dcpromo.exe). If
you are deploying Windows Server 2008 for the first time in a Windows Server 2003
or Windows Server 2000 forest, you must prepare Active Directory as discussed in
“Deploying Windows Server 2008” in Chapter 2.
|
https://ptgmedia.pearsoncmg.com/images/9780735626485/samplepages/9780735626485.pdf
|
20
|
Deploying Writable Domain Controllers CHAPTER 3 75
Installing Additional Writable Domain Controllers
Any computer running Windows Server 2008 can act as a domain controller. Essentially, domain controllers are database servers with extensive directory, application,
and replication features. Because of this, the hardware you choose for the domain
controllers should be fairly robust. You’ll want to look carefully at the server’s processor, memory, and hard disk configuration.
In many cases, you’ll want to install domain controllers on hardware with
multiple, fast processors. This will help ensure the domain controller can efficiently
handle replication requests and topology generation. When you install the second
domain controller in a forest, the Knowledge Consistency Checker (KCC) begins
running on every domain controller. Not only does the KCC generate replication
topology, it also dynamically handles changes and failures within the topology. By
default, the KCC recalculates the replication topology every 15 minutes. As the complexity of the replication topology increases, so does processing power required for
this calculation. You’ll need to monitor processor usage and upgrade as necessary.
In addition to running standard processes, domain controllers must run processes related to storage engine operations, knowledge consistency checking,
replication, and garbage collection. Most domain controllers should have at least 2
gigabytes (GB) of RAM as a recommended starting point for full server installations
and 1 GB of RAM for core server installations. You’ll need to monitor memory usage
and upgrade as necessary.
With regard to hard disks, you’ll want to closely examine fault tolerance and
storage capacity needs. Domain controllers should use fault-tolerant drives to
protect against hardware failure of the system volume and any other volumes used
by Active Directory. I recommend using a redundant array of independent disks
(RAID), RAID 1 for system volumes and RAID 5 for data. Hardware RAID is preferable
to software RAID. Storage capacity needs depend on the number of objects related
to users, computers, groups, and resources that are stored in the Active Directory
database. Each storage volume should have ample free disk space at all times to
ensure proper operational efficiency.
When you add a domain controller to an existing domain, you should consider
whether you want to perform an installation from media rather than creating the
domain controller from scratch. With either technique, you will need to log on to
the local machine using either the local Administrator account or an account that
has administrator privileges on the local machine. Then start the installation. You
also will be required to provide the credentials for an account that is a member of
the Domain Admins group in the domain of which the domain controller will be
a part. Because you will be given the opportunity to join the domain controller to
the domain if necessary, it is not necessary for the server to be a member of the
domain.
|
https://ptgmedia.pearsoncmg.com/images/9780735626485/samplepages/9780735626485.pdf
|
21
|
76 CHAPTER 3 Deploying Writable Domain Controllers
Adding Writable Domain Controllers Using Replication
You can add a writable domain controller to an existing domain by completing the
following steps:
1. Check the TCP/IP configuration of the server. The server must have a valid IP
address and must have properly configured DNS settings.
NOTE Domain controllers that also act as DNS servers should not have dynamic
IP addresses, to ensure reliable DNS operations. Otherwise, the server can have a
static IP address or a dynamic IP address assigned by a DHCP server.
2. Install the Active Directory binaries by entering the following command at
an elevated command prompt: servermanagercmd –install adds-domaincontroller. This installs the AD DS binaries, which enables the Active Directory Domain Services role on the server.
3. Before starting an Active Directory installation, you should examine local accounts to determine whether you need to take special steps to preserve any
local accounts. You should also check for encrypted files and folders using the
EFSInfo utility. At a command prompt, enter efsinfo /s:DriveDesignator /i |
find “: Encrypted” where DriveDesignator is the drive designator of the
volume to search, such as C:.
CAUTION Domain controllers do not have local accounts or separate cryptographic keys. Making a server a domain controller deletes all local accounts and
all certificates and cryptographic keys from the server. Any encrypted data on the
server, including data stored using the Encrypting File System (EFS), must be decrypted before Active Directory is installed, or it will be permanently inaccessible.
4. Start the Active Directory Domain Services Installation Wizard by clicking
Start, typing dcpromo in the Search box, and pressing Enter.
5. By default, the wizard uses Basic Installation mode. If you want to install from
media as discussed in “Adding Writable Domain Controllers Using Installation
Media,” later in this chapter, or choose the source domain controller for replication, select the Use Advanced Installation Mode check box before clicking
Next to continue.
6. If the Operating System Compatibility page is displayed, review the warning
about the default security settings for Windows Server 2008 domain controllers and then click Next.
7. On the Choose A Deployment Configuration page, shown in Figure 3-1, select Existing Forest and then select Add A Domain Controller To An Existing
Domain. By choosing this option, you specify that you are adding a domain
controller to an existing domain in the Active Directory forest.
|
https://ptgmedia.pearsoncmg.com/images/9780735626485/samplepages/9780735626485.pdf
|
22
|
Deploying Writable Domain Controllers CHAPTER 3 77
FIGURE 3-1 Specify that you want to add a domain controller to the domain.
8. When you click Next, you see the Network Credentials page, shown in
Figure 3-2. In the field provided, type the full DNS name of any domain in
the forest where you plan to install the domain controller. Preferably, this
should be the name of the forest root domain, such as cpandl.com. If you are
logged on to a domain in this forest and have the appropriate permissions,
you can use your current logged-on credentials to perform the installation.
Otherwise, select Alternate Credentials, click Set, type the user name and
password for an enterprise administrator account in the previously specified
domain, and then click OK.
|
https://ptgmedia.pearsoncmg.com/images/9780735626485/samplepages/9780735626485.pdf
|
23
|
78 CHAPTER 3 Deploying Writable Domain Controllers
FIGURE 3-2 Set the network credentials.
9. When you click Next, the wizard validates the domain name you provided
and then lists all domains in the related forest. On the Select A Domain page,
shown in Figure 3-3, select the domain to which the domain controller will be
added and then click Next.
FIGURE 3-3 Select the target domain.
|
https://ptgmedia.pearsoncmg.com/images/9780735626485/samplepages/9780735626485.pdf
|
24
|
Deploying Writable Domain Controllers CHAPTER 3 79
10. When you click Next, the wizard determines the available Active Directory
sites. On the Select A Site page, you’ll see a list of available sites. If there is a
site that corresponds to the IP address of the server you are promoting, select the Use The Site That Corresponds To The IP Address check box to place
the new domain controller in this site. If you want to place the new domain
controller in a different site or there isn’t an available subnet for the current
IP address, select the site in which you want to locate the domain controller.
11. When you click Next, the wizard examines the DNS configuration and attempts to determine whether any authoritative DNS servers are available. It
then displays the Additional Domain Controller Options page, shown in Figure 3-4. As permitted, select additional installation options for the domain
controller and then click Next.
FIGURE 3-4 Specify the additional installation options.
12. If you choose to let the wizard install the DNS Server service, note the following:
a. The DNS Server service will be installed, and the domain controller will
also act as a DNS server. A primary DNS zone will be created as an Active
Directory–integrated zone with the same name as the new domain you
are setting up. The wizard will also update the server’s TCP/IP configuration so that its primary DNS server is set to itself.
b. During installation of the operating system, Windows Setup installs and
configures IPv4 and IPv6 if networking components were detected. If
|
https://ptgmedia.pearsoncmg.com/images/9780735626485/samplepages/9780735626485.pdf
|
25
|
80 CHAPTER 3 Deploying Writable Domain Controllers
you’ve configured dynamic IPv4, IPv6, or both addresses, you’ll see a
warning. Click Yes to ignore the warning and continue.
c. If you want to modify the TCP/IP configuration, click No to return to the
Additional Domain Controller Options page and then make the appropriate changes to the system configuration before clicking Next to
continue. If you configure a static IPv4 address but do not configure a
static IPv6 address, you’ll also see the warning. To ignore the warning
and continue with the installation, click Yes.
NOTE At a minimum, you should configure a static IPv4 address before continuing.
Click Start, type ncpa.cpl in the Search box, and then press Enter. In Network Connections, double-click Local Area Connection. In Local Area Connection Properties,
click Properties and then double-click Internet Protocol Version 4 (TCP/IPv4), make
any necessary changes, and then click OK. If you also want to configure a static IPv6
address, double-click Internet Protocol Version 6 (TCP/IPv6), make any necessary
changes, and then click OK. If you decide not to configure a static IPv6 address, you
may need to make changes to DNS records later if your organization starts using
IPv6 addresses.
d. The wizard next attempts to register a delegation for the DNS server
with an authoritative parent zone. If you are integrating with an existing
DNS infrastructure, you should manually create a delegation to the DNS
server and then click Yes to continue. Otherwise, you can ignore this
warning and click Yes to continue.
13. If you choose to not let the wizard install the DNS Server service, the wizard
next attempts to register a delegation for the DNS server with an authoritative parent zone. If the wizard cannot create a delegation for the DNS server,
it displays a warning message to indicate that you must create the delegation
manually. Click No to return to the Additional Domain Controller Options
page so you can select and install DNS Server services. To continue without
installing DNS Server services, click Yes. Keep in mind that you’ll then need to
manually configure the required DNS settings, including SRV and A resource
records.
14. If you selected Use Advanced Installation Mode, the Install From Media page
is displayed, as shown in Figure 3-5. You can provide the location of installation media to be used to create the domain controller and configure AD
DS, or you can have all of the replication done over the network. Even if you
install from media, some data will be replicated over the network from a
source domain controller. For more information about installing from media,
see “Adding Writable Domain Controllers Using Installation Media.”
|
https://ptgmedia.pearsoncmg.com/images/9780735626485/samplepages/9780735626485.pdf
|
26
|
Deploying Writable Domain Controllers CHAPTER 3 81
FIGURE 3-5 Set the installation mode.
15. If you selected Use Advanced Installation Mode, the Source Domain Controller page is displayed. Select Any Writable Domain Controller or select This
Specific Domain Controller to specify a source domain controller for replication. Then click Next. If you choose to install from media, only changes since
the media was created will be replicated from this source domain controller.
If you choose not to install from media, all data will be replicated from this
source domain controller.
16. On the Location For Database, Log Files, And SYSVOL page, shown in
Figure 3-6, select a location to store the Active Directory database folder,
log folder, and SYSVOL folder. The default location for the database and
log folders is a subfolder of %SystemRoot%\NTDS. The default location for
the SYSVOL folder is %SystemRoot%\Sysvol. You’ll get better performance
if the database folder and log folder are on two separate volumes, each on
a separate disk. Placement of the SYSVOL is less critical, and you can accept
the default in most cases. Although you can change the storage locations
later, the process is lengthy and complex.
|
https://ptgmedia.pearsoncmg.com/images/9780735626485/samplepages/9780735626485.pdf
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.