Discovery - Fortinet FortiAP & FortiManager Troubleshooting
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-05-2022 02:44 PM
Trying to run Discovery on some FortiAPs and a FortiManager. I have added the MIB files to ServiceNow from the devices. Port 161 & 162 are open on the firewall but are being shown as "filtered" when I run nmap from the mid server.
When I run Discovery on Fortinet APs IP address I'm not getting passed the 1st stage
Any troubleshooting help is appreciated
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-23-2024 02:07 AM
Here are some steps you can take to troubleshoot and resolve the issue:
1. Verify SNMP Configuration: Ensure that the SNMP configuration on the FortiAPs and FortiManager is correct and matches the configuration in ServiceNow.
2. Check MID Server: Make sure that the MID Server is up and running and has the necessary capabilities to run Discovery.
3. Test Connectivity: Use the "Test Connection" feature in ServiceNow to verify that the MID Server can connect to the FortiAPs and FortiManager.
4. Check Firewall Rules: Even though ports 161
If you want to know any information about Service Now . Visit to https://nowkb.com/home
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-29-2024 06:56 AM
Do you have a pattern for discovering Fortimanager? We added the Sys OID to the OID table and ended up using the PDU Classifier just to get the devices into the CMDB.