- For SNMP configurations on managed or standalone FortiSwitch, refer to the following documents:
Configuring SNMP
SNMP
- Ping the SNMP server from the FortiSwitch to verify connectivity.
- Run the command 'diagnose sniffer packet any 'port 161 or 162' 4 0 a' to check if the FortiSwitch is receiving SNMP requests from the server.
diagnose sniffer packet any 'port 161 or 162' 4 0 a
interfaces=[any]
filters=[port 161 or 162]
YYYY-MM-DD HH:MM:SS cpu0 in 172.24.X.Y.52353 -> 172.26.Y.Z.161: udp 99
YYYY-MM-DD HH:MM:SS internal in 172.24.X.Y.52353 -> 172.26.Y.Z.161: udp 99
YYYY-MM-DD HH:MM:SS cpu0 in 172.24.X.Y.52353 -> 172.26.0.Y.Z: udp 99
YYYY-MM-DD HH:MM:SS internal in 172.24.X.Y.52353 -> 172.26.Y.Z.161: udp 99
- If the output shows that the switch is receiving SNMP requests but not responding, SNMP is likely either not enabled on the FortiWwitch or there is a misconfiguration. Ensure SNMP is enabled under ‘config system snmp sysinfo’ and ‘config system snmp community’:
config system snmp sysinfo
set status enable
config system snmp community
set status {enable | disable}
- If the issue persists, enable the following debug commands and initiate traffic from the SNMP server:
diagnose debug application snmpd -1
diagnose debug enable
Disable the debug by executing 'diagnose debug reset'.
The above outputs will help to find out the root cause of the issue.
|
