Thanks to visit codestin.com
Credit goes to www.scribd.com

Scribd
Upload
208 views2 pages

Basic Commands Fortianalyzer

The document lists commands for getting system information, server information, testing connections, and troubleshooting communication between FortiGate and FortiAnalyzer devices. Some key commands include: - "show system interface" and "show system route" to get network interface and routing information - "diagnose system print certificate" and "diagnose system print cpuinfo" to get certificate and CPU information - "exec log fortianalyzer test-connectivity" and "diag test app fortilogd 99" to test connectivity to FortiAnalyzer - "diagnose debug enable" and "diagnose debug application oftpd 8 <fgt ip>" used together to troubleshoot communication issues

Uploaded by

Bryan Nepomuceno
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
208 views2 pages

Basic Commands Fortianalyzer

The document lists commands for getting system information, server information, testing connections, and troubleshooting communication between FortiGate and FortiAnalyzer devices. Some key commands include: - "show system interface" and "show system route" to get network interface and routing information - "diagnose system print certificate" and "diagnose system print cpuinfo" to get certificate and CPU information - "exec log fortianalyzer test-connectivity" and "diag test app fortilogd 99" to test connectivity to FortiAnalyzer - "diagnose debug enable" and "diagnose debug application oftpd 8 <fgt ip>" used together to troubleshoot communication issues

Uploaded by

Bryan Nepomuceno
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

Basic Commands

# get system status


# show system interface
# show system dns
# show system ntp
# get system ntp
# show system route
#get system performance

Commands server information


# diagnose system print certificate (print ipsec certificate)
# diagnose system print cpuinfo (print cpu information)
# diagnose system print df (print system disk space usage)
# diagnose system print hosts (print the static table lookup for hosts names)
# diagnose system print loadavg (print average load of the system)
# diagnose system print netstat (print network statistics)
# # diagnose system print partition (print partition information system)
# diagnose system print system route

# diagnose system raid status


# diagnose system raid hwinfo
# diagnose system disk info
# diagnose system raid
# diagnose dvm adom list
# diagnose dvm device list (register e unregister)

Test connection
# exec log fortianalyzer test-connectivity
#diag test app fortilogd 99

# diagnose test application oftpd 8 <FGT IP> ( Fortianalyzer receiving logs)

You can use the following commands at the same time to troubleshooting communication

# diagnose debug enable


# diagnose debug application oftpd 8 <fgt ip>

Run the following commands fortigate


# dignose log test
On FGT , the cli commands diagnose test application miglogd 6 (display statistic for the
miglogd process)

You can use the following commands at the same time to troubleshoot

communication issues: Step one:


Run the following command on FortiAnalyzer:

# diagnose debug enable


# diagnose debug application oftpd 8 <FortiGate_IP>

Run the following command on FortiGate:

# diagnose log test

Review the output shown on the slide.

Se o FortiAnalyzer ficar indisponível para o FortiGate por qualquer


motivo, o FortiGate usa seu processo miglogd para armazenar os logs.

Há um valor máximo para o tamanho do cache e o processo miglogd


descartará os logs em cache. Quando a conexão entre os dois
dispositivos é restaurada, o processo miglogd começa a enviar os logs
em cache para o FortiAnalyzer.

Os Raw logs são compactados e salvos em um arquivo de log nos discos


FortiAnalyzer. Eventualmente.

quando o arquivo de log atinge um tamanho específico, é arquivado.

Os logs na fase compactada são conhecidos como logs de arquivo.

Os logs na fase compactada são conhecidos como archive logs.


Esses logs são considerados offline e não oferecem suporte analítico
imediato.

You might also like