Comments
-
I would add that logic to your alert trigger condition instead of the alert suppression.
-
Dan, It sounds like you have NPM + an additional poller. Is that correct? If so have you installed IPSLA on both the main and additional poller? Also, what operation(s) are running on the routers? Jeff
-
The Polling Engine for IPAM is purely to make sure Core is running on the same version across the platform. Outside of doing that update, there is no functionality that exist on an APE for IPAM.
-
Are you sure your config is right on the router? I think that means the server isn't seeing any netflow data.
-
Our DB is around 200GB and it takes about 10 minutes to get through the Netflow setup.
-
If you have the MIBs you can open a case with support and they will have them added to the MIB-DB. I'd recommend checking out this post too; Jeff
-
I would like to see this also.
-
Paul, I set this up a long time ago so I would have to go back and look, but we didn't have to leave it open for it to work. Let me know if you have any questions or you need me to dig out my notes. Jeff
-
I've changed system names in our production environment and it didn't affect anything. I wouldn't think you would have any problems.
-
After you create an alert you can use the copy feature to create new alerts. That will copy all of your trigger actions. Then you can just modify as needed.
-
What model PowerConnect? We poll several of them and them seem to gives us more info than that.
-
Butch, The first step is to verify that the MIBs are not already in our MIB library. You can do this by browsing or search the MIB library using the Universal Device Poller. If the MIBs you're interested in are not in the library, you can get them added by following the steps in this KB article.…
-
-is this recommended? Yes & No. Best practice would be to evaluate the product on a test server, but that doesn't allow you to see the full integration with your other products. If you do decide to evaluate in your production environment I recommend you take a backup of your current database. You'll also want to make sure…
-
This should get you going;
-
It is a bundle of NPM & NTA. http://www.solarwinds.com/lp/network-bandwidth-analyzer-pack.aspx Jeff
-
You can remove the ports from being monitored under the manage ports section on the settings page.
-
This would be out of the box functionality in Network Configuration Manager (NCM)
-
Can you provide a screen shot of your trigger condition?
-
Have you seen this document which helps guide you through the UCS/SolarWinds Orion setup? Let me know if that doesn't help. Jeff
-
You'll need SAM in order to get hardware health of your servers. NPM only covers hardware health of network devices. If you want to use the UnDP within NPM to monitor your server hardware you should be able to get the desired monitors setup. Jeff
-
Can I assume that you have configured CBQoS on the router in question? Have you told NTA to poll for CBQoS data?
-
We have posted a fix in the customer portal to address this issue. Please let me know if you have any questions or issues with the HF.
-
This thread should help; Fast Polling Jeff
-
This would be a great enhancement to Orion! We have something similar in other products and would probably stop using them if this was a feature. I just keep waiting for this to show up in Atlas.
-
Donald, We have two different Orion deployments with the following; Deployment 1 Orion - 10K elements Orion Polling Engine - 10K elements Orion Polling Engine - 10K elements DB Server Deployment 2 Orion - 10K+ elements EOC/NCM - Same server DB Server Let me know if you have any questions on how this is working for us.
-
Are you logged in as an Admin? You should see a '/Reports' in that drop down.
-
Can you verify that the syslog service on the Orion NPM server is running?
-
You can create a group for those devices and report on the group availability for your overall status. Then you can report individually for each device. This will require that you're on NPM 10.1. HTH
-
Josh, One of the great things about NCM is that the product is not device or vendor specific. In the case of your future purchase of Nexus devices, since NXOS, has some different commands than traditional IOS a new device template might need to be created and applied to your evaluation. The device templates are super easy…
-
What version on NPM are you running?