common used snmp oid fortigate mib core

CORE:

Traps:

.1.3.6.1.4.1.12356.100.1.3.0.101
Indicates that the CPU usage has exceeded the configured threshold.

.1.3.6.1.4.1.12356.100.1.3.0.102
Indicates memory usage has exceeded the configured threshold.

.1.3.6.1.4.1.12356.100.1.3.0.103
Log disk usage has exceeded the configured threshold.

config vdom

edit “vdom name”

config system interface

edit “interface name” (lookup via “show” when in ‘config system interface’ mode)

set secondary-IP {enable | disable}

config secondaryip

edit 1 (or any other number)

set ip <ipv4-classnet-host>

set allowaccess {ping | https | ssh | snmp | http | telnet | fgfm | auto-ipsec}

2 Comments
Nov, 10, 2016
Angelo Schalley
Fortigate/Fortinet, Networking, security

Troubleshooting examples for debugging a Fortigate :

Reverse path check, iprobe, policy check, etc …

DNS port only :

diag debug reset
diag debug flow filter clear
diag debug flow filter port 53
diag debug flow show console enable
diag debug flow show iprope enable
diag debug flow show function-name enable
diag debug console timestamp enable
diag debug enable
diag debug flow trace start 1000

Category Archives: Fortigate/Fortinet

common used snmp oid fortigate mib core

configure secondary ip address on a Fortigate command line

Troubleshooting FortiGate command line check debugging trace sniffer

Troubleshooting examples for debugging a Fortigate :

DNS port only :

Categories