© Copyright 2006 Fortinet Incorporated. All rights reserved.
Products mentioned in this document are trademarks or registered trade-
marks of their respective holders.
Regulatory Compliance
FCC Class A Part 15 CSA/CUS
25 September 2006
Checking the Package Contents
Connecting
Planning the Configuration
Ethernet Cables:
Orange - Crossover
Grey - Straight-through
Documentation
FortiAnalyzer-4000
Copyright 2006 Fortinet Incorporated. All rights reserved.
Trademarks
Products mentioned in this document are trademarks.
Power Cable
Back
Front
Power
Connection
UID
Ethernet Connections
Serial Connection
Null-Modem Cable
(RS-232)
Q u i c k S t a r t G u i d e
Power
Connection
UID
Straight-through Ethernet cable connects
to hub or switch on the network
Null modem cable connects
to serial port on management computer
Place the FortiAnalyzer unit on a stable surface. It requires 1.5 inches (3.75 cm) clearance
on each side to allow for cooling.
Make sure the power is not plugged into the wall before connecting the power cable.
The Status light flashes while the unit is starting up and remains lit when the system is up
and running.
•
•
•
Connect the FortiAnalyzer unit to a power outlet and to the network hub or switch.
FortiAnalyzer-4000
05-30003-0240-20060925
Connector
Type
Speed
Protocol
Description
Ports 1 and 2
RJ-45
10/100Base-T
Ethernet
Connection to the network
CONSOLE
DB-9
9600 bps
RS-232 serial Connection to the management computer. Provides
access to the command line interface (CLI).
You can add the FortiAnalyzer unit to your local FortiGate network to receive log messages
from your local FortiGate units, or connect the FortiAnalyzer unit to the FortiGate units re-
motely using FortiManager. To connect the FortiAnalyzer unit to the FortiGate units remotely,
you must configure the DNS server and the default gateway.
To manage the FortiAnalyzer unit, you can use a computer within the local network or over
the Internet.
Factory Defaults
Administrator Account
User name:
admin
Password:
(none)
Port 1
IP:
192.168.1.99
Netmask:
255.255.255.0
Management Access:
ping, https, http, ssh
Port 2
IP:
192.168.2.99
Netmask:
255.255.255.0
Management Access:
ping, https, http, ssh
