Comments
-
Agree with @"GunnyM" here. The issue is PURELY on Solarwinds here to improve their security and supported SSH ciphers. This SSH issue is not exclusive to Fortigate as well for NCM; other vendors are doing the same and NCM will become obsolete until they fix this.
-
Solarwinds support needs to rethink their deployment schedule. Waiting 6 months is not an option here. Working this as a sub release outside of their other fixes they have planned for 2024.1 should be done ASAP. The amount of time numerous customers have complained about this and seeing more and more Vendors doing the same…
-
- resolving ip hostnames via DNS monitoring verses PTR dns lookups. Might have use case with mulitple domain/forrest that requires manual created PTR records in DNS to resolve. IPAM can monitor the DNS servers and Zones....therefore being able to see the A record and IP address. IPAM should be able to use these in the…
-
Jason, I would be fine with any API additions as long as its added into NPM. I don't think customers would appreciate needed to buy another module for this Individual device polling would be a plus but I'd be happy just to get orchestrator properly monitored. From Orch, a lot of date points are already there and SWINDS can…
-
Rest API for monitoring nodes is going to be required. For SDWAN products like Silver Peak, API is going to be the only way to integrate their orchestrator with NPM. Silver Peak will NOT add SNMP support for this (I've asked to the top levels ). SNMP monitoring of the SilverPeak appliances offers very little information.…
-
Running NCM 7.7 and its reporting our Juniper EX4200s incorrectly. The EOS link is referring to a EOL for EX4200-48P and EX4200-24P.......but all of our devices are EX4200-48px or EX4200-24px. The PX is NOT EOL and it seems like this should be a very simple fix for the SWINDs team to address. Maybe its best to pull the OID…
