Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

Cisco ACI - Issues with discovery - Calling anyone who has Cisco ACI in their environments!!!

We have ACI setup on Solarwinds: 2 APICs, 4 leaf's and 4 spines.

As per the instructions on the 1 APIC node the poll for Cisco ACI is enabled and works fine.

The rest are also nodes on Solarwinds but do not have the Cisco ACI setting enabled.

The issue we have is with discovery, every 30 minutes (when a rediscovery takes place) the interfaces go into warning state which causes many alerts that makes the whole thing a bit pointless.

What seems to happen is that each time it does a discovery it fails to get all the interfaces which explains why the nodes go into warning.

This is also evident when I click on 'List Resources', I get a different amount of resources each time and usually they don't include the physical interfaces (usually just see port-channels or tunnels).

This issue is only on the leaf's and spines.

Is there anyone out there with ACI that doesn't have this issue and if so did you have this issue or have you done something extra that isn't in the instructions?

I'm wondering if it's a case of the wrong OID's being polled? The whole thing does take awhile so it seems like it's timing out.

FYI I have raised a support call but they think the issue is with Cisco, I'm not convinced but in the mean time if anyone has any advice I very much welcome it

Find more posts tagged with

Accepted answers

All comments

NightAngel07

I had a similar issue with some of our leafs not listing the interfaces when I did a "list resources". The work around for me is how I did the discovery process for the leafs as I typically just manually added the node from the main menu. To get the interfaces listed for each leaf having issues I did a network discovery on the OOB IP for each leaf and extended the SNMP timeout and retries. Once I did it this way I was able to add all the physical interfaces and logical ones. I don't monitor the logical ones since ACI just does its own thing with tunnels and vlans.

Settings>network discovery

I never had the warning issue though. Depending on the warning it could be related to ICMP and not the SNMP monitoring or ACI having an issue with a device on the leaf.

buckaholic27

I am having this issue as well. A monitored interface on leaf goes into warning state every 30 minutes, repeatedly.. I have this issue with multiple software versions of ACI. The interface stays up on ACI but Solarwinds will show the state as UNKONWN and trigger a warning alarm. Any help would be greatly appreciated.

BllackPython

Oh good not just us!

What has helped us massively reduce the events (although not pleased with this as a solution) is the following:

Go to Polling Settings in Orion (All Settings -> Polling Settings) and do these changes:

Set SNMP TIMEOUT to 10000 ms
Set SNMP RETRIES to 5

buckaholic27

Yes! It is very frustrating! We've changed lots of settings, worked with Cisco TAC, upgraded ACI firmware, still no luck! Thank you for the suggestion.

BllackPython

No problem, we went a different approach where we were asking Solarwinds to investigate (Although they did keep pointing us towards Cisco).

They found that Solarwinds would not always get a response so it would have to retry but with the timeout being 2.5 seconds it was showing as timing out, hence the settings change.

If you change the settings I'd be very interested in knowing if it resolved it for you

Good luck!