Comments
-
Craig, This is exactally what User Experience Monitors do. You can use a "pre-caned" template or even create your own. Ryan
-
There are no limitations on nested maps. As an example I have World -> North America -> Texas -> Travis County -> Austin -> Capital Building -> second Floor -> rack 2 If there is a map with no members it should show grey (as there is nothing up or down)
-
Go to your Orion server and use the Limitation builder, this will allow you to do exactaly what you are looking for
-
Simply use the license manager to "park" your license from your old server. Install version 10 on your new server and activate the liscence. then run the configuration wizard pointing to your database housing the 9.5.1 DB and the configuration wizard will then upgrade the DB to version 10. You may have to ensure the nodes…
-
Do the engine ID's in your Engines Table Coincide with the EngineID's referenced in your nodes table? If there are any negitave integers or "rogue' engine Id's this behavior can occur.
-
Can you provide the MIB you are using and possibly a screenshot so I can understand your issue better?
-
I would: #1release the license #2 Change the name #3 run the configuration wizard #4 Add the license
-
Looking into this, was probably just a version change oversight. Nothing changed in that package between the RC and GA. But I will look into resolving this, thanks for bringing it to our attention.
-
your best bet is to start a support case, the error is pretty generic in addition running and uploading your diags will help as well Please run Solarwinds Diags (start/programs/solarwinds orion/Documentation and support/solarwinds diagnostics then upload the .zip file created using our secure website…
-
I recommend starting a case with support for this issue, they should be able to assist.
-
Try these: SSID: ${SQL: select Rogue_SSID from NPM_NV_WL_REPORT_Rogues_V where npmnodeid = ${NPMNodeID}} MAC Address: ${SQL: select Rogue_MACAddress from NPM_NV_WL_REPORT_Rogues_V where npmnodeid = ${NPMNodeID}}
-
similar to the "views by device type"?
-
are your poller and database times synched?
-
This is due to a scheduled maintenance task you have set up. to check this go to your IPmonitor web console - > configuration -> scheduled mainenance Tasks and there you will see the tasks you have configured
-
Default is Blank. This is due to what is critical on your network in response time may be different than that of another users environment. This is by design
-
Use the view APM_reportsandalertsdata instead of the tables
-
Unfortunatly this cannot be done over SNMP currently and that is the real limitation
-
#1 Create a Custom SQL alert #2 Set up your trigger query for NODES #3 paste the following into the white box: inner join AlertStatus on Nodes.Caption = AlertStatus.ObjectName where AlertStatus.Acknowledged <> 0 and acknowledgedtime > DATEADD(mi, -5, GETDATE()) #4 do not trigger until... set to 0 seconds #5 reset condition…
-
stop all services, rename your existing swnetperfmon.cfg file to .old run a repair on Orion and allow the configuration wizard to run.
-
ensure you are accessing all views the same way ex: http://servername/orion/etc/etc or http://10.1.1.1/orion/etc/etc/ if you switch between ip and hostname you will be required to login
-
I am assuming you are using a query similar to: select * from nodes where MachineType like '%2911' Seems to work fine for me. have you opened a support ticket?
-
Simply turning it off and back on should force an update. However, if that doesn't work, stopping and restarting the manager service should accomplish this.
-
Not exactly following what you are trying to filter by here...What do you mean by "tag"? There are applications which are made up of components and you can filter by either of these. Doing Application.Tag would be telling the software to look in the Application Table, Tag Column Which does not exist. Ryan
-
Daily on update there will be a LEM internal even that states wether the threat feed was updated successfully, if your receive this even then threat feeds are working and you just aren't being attacked by a known threat
-
Simply run the command regsvr32 c:\Program Files\SolarWinds\Orion\SWAlertActions8.dll and regsvr32 c:\Program Files\SolarWinds\Orion\SWAlertEngine8.dll See if that changes anything for you
-
Please submit this as a support case as it may be a bug and we would like to look into this further