cancel
Showing results for 
Search instead for 
Did you mean: 
Create Post

NPM Monitor Cisco ACI

NPM Monitor Cisco ACI

Would like NPM to poll the API for the Cisco APIC controllers. to gather stats and information about ACI.

Tags (4)
25 Comments

This feature is required to support Cloud DC and Software defined Network. My Most of customer is evaluating other tools for This capability. Requesting Solarwinds Team to include this capability ASAP>

Level 7

Being a larger Solarwind customer we desperate to get the capability to monitor Cisco ACI to have end to end solarwind monitoring solution.

Level 9

Hello mtalas,

I responded to you directly (I'm not on here much), but in case you didn't get that and/or perhaps it'll help some other people here since I got it working, this is some general information... though you'll have to find the actual documentation/examples out there on your own.

So FWIW:

You can currently get the typical/standard NPM monitoring for Cisco ACI [hardware] using SNMP polling (I'm using v3) right now – At least for ACI 3.x for certain, this includes the Leafs, Spines, and APICs but I think 2.2 / 2.3 will as well.

To make that work though you need to do some prep on the ACI side of things - namely enabling SNMP in a few places (yes, there's more one spot), and additionally/separately you can set ACI to send SNMP Traps as well (or Syslog) to Orion.  The documentation out there is sparse but there are one or two documents that will get you there.  Note: The SNMP portions alone will get you the Leaf & Spines, like any other Cisco switch polled by NPM, but with ACI 3.x (maybe even 2.3 or 2.2) to get the APICs you need to define an OOB Management contract to allow Orion to query the APICs (assuming you're using out of fabric connections for OOBM [recommended]) - that part doesn't seem to be included in a lot of the info on the Internet and took me a bit to run across.  Basically Cisco changed the protocols allowed in by default, so you have to now explicitly allow in traffic to UDP 161 and you have to have your APICs entered in your Node Management Addresses section (likely only your leafs & spines are there).

It may not get all the hardware sensors or fields, but you can monitor general health & interfaces, and have alerts on them like normal.

Hope that helps.

Cheers,

-Marek

Level 9

For some reason I was getting an error repeatedly when trying to add an image to my post above, but here's a sample APIC in NPM:

acisamp.jpg

Level 8

We will be deploying ACI3.x soon, this would be a great feature

Level 20

It sounds like Marek​ has it working and it just takes some configuration on the Cisco side (Big surprise).

Dear Marek

Please provide details on Document and check point you have done in Cisco ACI side mentioned as below. we are using Cisco ACI 2.2.

1- Places in fabrics where we have to configure SNMP

2- One or 2 Document referred by you to configure SNMP

3- what is OOB Management Contract ? Where to configure

-----

"To make that work though you need to do some prep on the ACI side of things -

namely enabling SNMP in a few places (yes, there's more one spot), and

additionally/separately you can set ACI to send SNMP Traps as well (or Syslog)

to Orion.  The documentation out there is sparse but there are one or two

documents that will get you there.  Note: The SNMP portions alone will get you

the Leaf & Spines, like any other Cisco switch polled by NPM, but with ACI

3.x (maybe even 2.3 or 2.2) to get the APICs you need to define an OOB

Management contract to allow Orion to query the APICs (assuming you're using out

of fabric connections for OOBM [recommended]) - that part doesn't seem to be

included in a lot of the info on the Internet and took me a bit to run across.

Level 12

This is a thing and it's coming. SolarWinds needs to get ahead of this and be able to monitor it natively.

Need this feature ASAP, Please.

Level 10

We will be deploying ACI this July, and SDWAN Q1 next year. According to Cisco, ACI is being rapidly deployed at breakneck speed now that it's surpassed the "bleeding edge" and had some time to mature.  Hopefully full native support for these won't be as late as SIP support, which we've been waiting for for over a year now. It would be great if someone from SW would chime in here and give us an update.