rschroeder · NAM SME · ✭✭✭✭✭

I like that idea. However, being a control freak, I prefer to have my own test lab and prove things work there for myself. On the other hand, working for a non-profit with other things to buy than duplicate hardware and lab space, I've been without a test lab for several years. Not ideal, but somehow my team makes it work.

Your clients actually have more than 30,000 nodes they monitor and back up with NCM? Not elements, but "nodes?"

As I think on it, the Nexus firmware upgrade feature is concerning. In my environment, Nexus gear supports the data centers and our hospital infrastructure; leaving its firmware upgrades to a new product have me frowning. I realize there are at least two schools of thought: * Upgrade these critical devices manually to…

Agreed--I was dismayed when NCM 7.4 removed several key functions & flows that I relied on. To later learn one or more were moved to UDT, and would not show up in NCM again . . . well, that made me feel pretty badly. Having to buy another product, and manage it, and pay for a support contract for it, when I'd already had…

FWIW, we've experienced some significant issues with our WAN provider's Accedians. I'm not sure they're the future for us.

If this isn't feasible to do natively within Solarwinds products, you might use Google Earth or Google Maps to create that map and use it as a background for Solarwinds maps, placing your nodes on the Google map as desired.

I'm very much looking forward to the ASA compatibility/feature enhancements!

Beautiful! Thank you for all the work!

Please help the novices and go back a step: they'll want to know what systems need anti-virus connectors, how firewalls play roles in this, exactly how Solarwinds products (and which of those products) support AV Connectors, etc.

Our ACS was quite problematic, occasionally locking us out of TACACS due to bugs and crashes & hangs. TAC was never able to get it working to my satisfaction, and when they EOL'd it, many folks objected; there wasn't a TACACS replacement, so how could the product be going out of support? We moved to ISE, went through the…

Reviewed and updated 20200207. This process still works in Platform 2019.4 HF3. Rick Schroeder

For a few years I've been enjoying how the Cisco 4510's offer all this info in a simple CLI command: "show int link". Sadly, it doesn't work for Cisco stackable switches. But if you have a chassis, give it a shot. You can even filter it to include longer time periods of ports being down, like this: show int link | in weeks…

NCM works well with flat text files showing running or startup configs. With ACI . . . not so much.

Sorry I missed your great idea---and it IS a great one! This functionality was originally included with NCM. It was removed in version 7.4, and SW told me they were thinking of moving it to UDT. I don't have CAT Tools, but DO have the Engineer's Tool Set; I've not looked to see if the report is included there. But it would…

wfordham Numbers in columns, especially "small" numbers like 0-5, usually correlate with manufacturer's internal codes for status of devices or their components. For example, "0" may mean "up", "1" might mean "down", "2" might mean "unknown", "3" could mean "administratively disabled", "4" might mean "error disabled", etc.…

Like others, all six of my data centers have moved to ACI, effectively eliminating Solarwinds from being a player in their full support. The sooner I can show the organization that SW is fully, or even mostly, compatible with ACI, the sooner I'll stop fielding requests to replace Solarwinds with something that can do the…

Does your Kiwi CatTools solution have an option to also discover and display the late date/time that a port had link or showed activity? That's the crucial part I want, so I can repurpose patched ports that have not been used in months or years. The process I created on this page DOES provide that info. But it would be…

Sadness. I recommend you call Solarwinds Technical Support to confirm your hypothesis. They may be able to provide an alternate or work around.

I'm not sure why your options don't offer the ability to add a column for the Physical Interface. Perhaps it's because I created this with a slightly older version of NPM, but I doubt it. I trust SW to not remove that functionality. Instead, let's double-check your process from Step 1 of building a new Report. If you…

In my case, we don't own Kiwi Cat Tools. Hence my request to include this within a product we already own. Sadly, this same functionality used to be included with NCM, back in 7.2. SW told me it was intentionally removed, and they planned for it to be included in UDT--which I don't have. So I built this report and…

Nicely done. Even long-time SW users will benefit from this--we can't all do everything, or remember it all. Many thanks!

Hi steve.cabot​, I think you're close to the right area, just not zeroed in. You've set your Orion Object dropdown to "Interface", but it needs to be "Node": Setting it to Node and then searching for "Physical" should give you "Physical Interface" as one of your options: Swift Packets! Rick Schroeder

I think you need to be monitoring all the physical ports on a switch before you can generate this report and get useful information. For example, some folks don't buy licenses large enough to cover all their ports--they only manage/monitor uplink ports off of access switches. This prevents you from being able to get the…

That used to be the same situation for doing NetFlow on a Cisco 4510 version 7 chassis. You needed to buy an add-on module and install them to get NetFlow data out. When Version 8 chasses came out, Netflow was present by default on all hardware, but you need to upgrade the license on the chassis from LAN Base to IP Base…

This process still works with the current versions of Orion modules we're using (Rick Schroeder, 9/5/2016).

I recently resolved some problems after upgrading to NPM 12.2 by enabling TLS1.2 on all my APE's and the main instance of NPM. It's there, but you may have to work with Support to find the right registry keys to allow it.

Yes, please!

This particular topic became of great interest to me in late 2017 after upgrading from NPM 12.0 to 12.2. Due to various problems with the upgrade (later successfully addressed by Hot Fixes), poller drive space would be consumed by failed poller communication jobs, which resulted in poller failure due to loss of sufficient…

Maybe that buzz phrase of techno jargon will be part of a future release of a new Solarwinds Data Warehouse that will let us track and graph LONG-TERM trends over five or ten years. I know that info would be helpful for my job in planning appropriate WAN and Internet pipe sizes.