aaswi

It is recommended to upgrade to the latest version to correct this. Certain conditions much match for the ignore list to work properly. Such EngineID (of the poller), IP address, and Caption. The list only triggers an "ignore" if all of those conditions are true.

do a sh version and verify your license base. LAN-Base will not support netflow according to Cisco. IP-Base is required. other items to check: - be sure the device is being monitored by npm (including the interface) and it is actively being managed. - be sure the configs point to the orion server as the netflow collector.…

to reiterate what Rob stated above: it has has determined that it takes roughly the same amount of resources to complete a single (1) WMI poll as it does to complete five (5) SNMP polls.

This is somewhat a misnomer from SWI. It is actually not a poller for ipam. The IPAM poller executable is used to update the Orion Core services on any additional poller(s) in your environment. It does not extend “poller” functionality of ipam. 

Actually this might be a good FR for the Engineers Toolset. I could have used this quite a bit in previous roles. Especially along side WAN killer.

configuration generator?

Fortigate 200d. SysobjectID: 1.3.6.1.4.1.12356.101.1.2005 Using the device studio pulled the Fortigate 300 MIB file for the device. Which resulted in some unsupported OIDs for the following elements: vpntunstatus, vpntuntable, etc. Specifically OID 1.3.6.1.4.1.12356.9.x

Enterasys Wireless AP's. will provide snmpwalk and OID's soon.

Here are more popular asa ncm exclusions done properly.

This can be done using the built in UDT whitelist feature. When building the whitelist you can define mac addresses even with wild card characters. Example: ab.cd.ef.*. This will force UDT to ignore your defined vendor OUI and only look at the rest. If UDT finds systems that do not match it will be identified as rogue.…

Can we get a "Big Fun Cisco UCS Brainstorm" also? 

make sure you verify the cdr ftp file path is exact and correct on your call managers.

APE's provide scalability for the Polling Engine piece of the application. Orion is comprised of many working parts, some of which have limitations, especially considering this is an active polling solution. Scalability comes in the form of the type of elements you are monitoring. I've seen a single instance of Orion with…

I found that the solution presented here does solve this problem. Issue can manifest itself by crashing when trying to add a node as well. Simple uninstall of any existing c++ redist. thru add/remove and reinstall of 2012/2013 x64 and x86 (no reboot required) will solve the issue. 

yes you have to have the engineers toolset installed and the integration piece installed. Then reference this link: Enable SSH Putty on Orion Node page

Cisco 3750 Stack - Physical Entity ConfigMgmt Report

Are you guys referring to running UDT standalone? According to the Solarwinds published scalability KB, UDT can poll up to 100k ports per poller. Scalability Engine Guidelines for SolarWinds Orion Products - SolarWinds Worldwide, LLC. Help and Support

I would recommend placing the orion database also into aws. Here are port requirements for all SolarWinds products. SolarWinds Port Requirements

please be sure snmp is enabled and contains the same string as the previous devices.

While I'd be the first to admit, Orion monitoring capabilities for UCS are limited. There are several undp's floating around on thwack that can provide more specialized information. These have to be imported via the undp utility. Chassis: Cisco UCS Chassis Slot Information.UnDP Cisco UCS Chassis Inventory with Status.UnDP…

For now NTA is leveraged as a tool to identify traffic that is out of the ordinary when utilization crosses a threshold off an interface. The alerting and utilization would actually come from NPM, where you would combine current NTA info or historical details to provide insight into the bandwidth usage on the network.

see updated thread: Adding an ASA with multiple context firewall in NCM

According to NCM 7.8 release notes, multiple context from ASA devices are handled individually. "Support for multiple VDCs Cisco Nexus series switches provide support for virtual device contexts (VDCs). Each VDC runs as a separate logical entity within the switch. To add a Cisco Nexus device with multiple VDCs to NCM,…