jamesatloop1

Go to manage agents from admin settings, hit add and then under connect you will see the download link. Install on the windows 10 box providing orion admin credentials and ip. If the port is open orion will see it.

Go to the connect an agent option and then download the msi, try a manual install. This is over port 17778. Ports 135, 145, 17777 are required for orion to client deployment.

Its not just about the ports my friend. Are you sure you have permissions to spit unicast packets across your network?

Not really sure what the question actually is here but go to manage reports and search for hardware, The sensor report is listed.

Delighted to hear it, well done you, you're a pro. Yah restart the services.

The upgrade stops the services and starts them again, main polling engine first, then the ape's. You know you can create your own mib templates for solarwinds npm for your devices dont you?

Upgrade to npm 12.3 beta and then go to settings, all sett.........

Go to settings, all seetings, then manage hardware sensors and correct the thresholds that are causing you issues. Dont think its a mib issue you have but i could be wrong.

Hi Bernie, Firstly you can monitor tcp connections by deploying the QoE packet sensor to the server from settings and QoE settings under product specific settings. Once the agent is deployed it will report back all protocols and ports along with latency to your orion. Secondly if you have SAM there is a template for…

I would create a new custom third party update. You can create your own updates manually as well. This way you dont have to use 15 exe's, just the one job.

Here you. Cisco ASA Active VPN Connections

Glad to hear, no problem.

stop services and delete solarwinds from c:\windows\tmp. Start services, leave for ten minutes and test again. It might not bee the maps either, it could be another chart on the view, i know i have had issues with other charts loading such as errors and discards struggling to produce and causing the page to stop loading…

Yes, it is a document update.

The only time i have seen this behavior is when the community string was entered into the device after discovery. Try re-adding the devices again manually and see what you get under list resources.

They are nice man!

When i do it i unmanage the device then mute alerts. I dont just mute alerts.

Yes your right. Glad to hear.

no, you?

Nope, i suggest you correct your dhcp and add your dns server. The NPM\IPAM integration is very poor.

era sure your welcome. mark as helpful\resolved or something, need the points.

1=up 2=down enjoy SELECT TOP (1000) [NeighborID] ,[NodeID] ,[NeighborIdentifier] ,[NeighborIPGUID] ,[NeighborIP] ,[ProtocolID] ,[ProtocolStatus] ,[IP_Address_Type] ,[IsDeleted] ,[IP_Version] ,[LastChange] ,[AutonomousSystem] FROM ['mydatabase'].[dbo].[NPM_RoutingNeighbor]

Solarwinds recommends a domain sa account with no restrictions hence the reason your having the issue to answer your first question. The second question is answered by converting the orion console from http to https. This can be done by editing the websites table in the database and running the configuration wizard.

You need to do an interface availability report. This shows you the downtime. custom chart, select interfaces instead of nodes, select specific objects, select the interfaces you want in your data source. When in the configuration page select add on the x axis and look for percentage availability, select hourly time…

There are many different answers to this question but it sound like that you are not using a domain admin credential that has access to all machines which is the recommended from solariwnds.

Because you are using a local admin account. You need to use a domain admin account.

Got to the esx on orion, edit node and test the snmp credential.

The only way is to edit the view and tick enable noc view near the bottom.

Run the permissions checker from the orion directory and then re-run the configuration wizard. swnetperfmon is actually a configuration file in the orion directory. If that fails run a repair on the installation of npm.

No but you can monitor the service. There is native integration between orion and webhelpdesk for SAM and NPM which is why there are not templates.