We are receiving an error when trying to use the network sonar discovery. "An error while processing results has occurred. See discovery log for more details."
Also tried to add the nodes by clicking the "results" tab and get the following error.
"ProvideFault failed, check fault information."
Despite the relatively maturity of monitoring and systems management as a discrete IT discipline, I am asked - year after year and job after job - to give an overview of what monitoring is.
This document was my attempt to address that question in a more structured form.
Originally intended as guide to help bring new team members (often fresh out of college or a technical program) up to speed with monitoring concepts quickly, this document (or portions of it) can serve as a good introduction for a variety of audiences.
Excerpt:
"If you have worked in the IT field for more than 15 minutes, the situation described above is neither unique nor rare, even if it is somewhat colorful. Systems crash unexpectedly, users make bizarre claims about how “the internet is slow”, and managers ask for historical statistics that leave you scratching your head wondering how to collect in a way that is meaningful and doesn’t consign you to the hell of hitting “refresh” and writing down numbers on a paper for half a day, just to get a baseline for a report.
The answer to all these challenges lies in effectively monitoring your environment – collecting statistics and/or checking for error conditions so that you can act or report effectively when needed."
If you find that you are running Windows 2008/2008 R2 and it is taking an inordinate time to start the Solarwinds services after a reboot, then you may want to check the MSMQ service and subsequent settings. In your Windows system log, look for event ID 7044. In that event you will see the following message: "The following service is taking more than 16 minutes to start and may have stopped responding: Message Queuing." If you see this issue on your polling engines, it will cause the polling engine to go red as the following Solarwinds services rely on MSMQ to start:
- Solarwinds Information Service
- Solarwinds Information Service V3
- Solarwinds Collector Data Processor
- Solarwinds Collector Polling Controller
To completely verify the issue, check out your Windows\System32\MSMQ\Storage. The default journal setting is 8GB. If the folder is 8GB, you have verified your problem. Furthermore, if the poller has only 8GB, that will explain why nothing can be accomplished on the server until this is complete, as MSMQ is trying to load all messages into RAM. See the following TechNet article to understand more and correct the problem at the domain level: https://technet.microsoft.com/en-us/library/cc733166(v=ws.10).aspx.
Loop1 Systems: SolarWinds Training and Professional Services
Hi,
Need someone's help to find ArubaS2500-24P-US CPU and Memory OID and Cisco Nexus (N7K-C7010) BGP peeringOID.
We will use the Aruba OID for our CPU and memory reporting while the Nexus OID will be used for alerting.
Thanks in advance.
Herbin
(With honor and response to Edgar Allen Network Admin)
Once upon a midnight backup, while my laptop I did pack up,
Finishing a Cisco stack, upstairs I’d finished upgrading.
While I called the Help Desk clearly, telling them my job was nearly
Finished, and I felt sincerely that I home would quickly wing.
I saw a little line a-scrolling, telling tales of packets rolling
Out my NIC, but it was polling no responses to its ping.
Yes it WAS in late October, and my project as a coder, 'twasn't like a souped-up motor
Made me think I’d lost my zing.
Seeing ping loss gave me sorrow, such that I could wish to borrow
Toolset tools highly bizzaro, tools to bring back everything.
For the packets out were ending with no Ack and were not sending
Me to bed while they were rending network woes I dare not sing.
And so I started up my browser, seeing soon a meme of Bowser
Hoped that Sha-Na-Na could wowzer fixes of most everything.
NPM did then reveal the information that would seal
My fate of sleeping without zeal--until I fixed that wayward Ping.
“Where did they go?” I pondered quickly (at 1 a.m. my brain is thickly
Scavenging for thoughts that slickly intuition hopes to cling).
“Back to basics” said the sage—what could I use that would assuage the problem?
Yes!--A bandwidth gauge--would reveal the bandwidth hog.
When applied upon the GBIC, quickly as a football flea-flick, it could tell me
News comedic, and I’d find HIM in the log.
All I had to do was wait and surf on Thwack and contemplate how
Packets soon would not be late, no longer victims to backlog.
Presently a message evil crossed my screen much like a weevil
Gliding just like E. Knievel crossed the Snake minus toupee.
There he was, the slowness-grower, making networks ever slower
Acting innocent, but “knower-NTA” could save the day!
Who would slow his colleagues’ browsing, packet sniffers then arousing
Corporate policy espousing CISSP’s away?
Slippery as collodion, streaming Nickelodeon,
‘Twas simply the custodian filling up the T1’s pipe.
Surreptitiously it listened, Netflow shined and then it glistened
Sundry packets as they christened music streams through teletype.
“Will he never stop that streaming?” (I imagined my boss screaming)
“Call the site and start blaspheming!” came his effervescent gripe.
And so between the packets I contrived to setup brackets that would
Put him in straight-jackets, stop his surfing at the door.
NPM and Damework Mini, QoE with footprint skinny,
UDT and its close kinny NTM I did implore.
Packet filters let me study all his traffic from his buddy ‘til
I left his PC bloody, dead and lifeless on the floor.
But I knew he’d soon be calling to the Help Desk, loudly bawling:
“All this slowness is appalling—I am feeling mighty sore!”
So I crafted memo quickly, taking care to not be prickly, showing
Him how network sickly streaming vids we do abhor
Entertainment that’s competing with our business traffic fleeting
Citrix and PC defeating flows that must not hit the floor.
But he never started calling—once his Manager was galling at the
News I shared—appalling!—how he stopped their network flow.
So the process bears repeating, using work for play is cheating,
And the WAN bandwidth-depleting, every person ought to know.
With the mystery abated, and the WAN bandwidth inflated back to
Normal COS (so weighted), homeward soon I knew I’d go.
“Thanks” (I thought) “for things Orion, and for pizza types Hawaiian!
And for Neo down in Zion! And my favorite Toolset tool.”
Never be without Orion or your Tool Set--you’ll be dyin’
For some thing to stop your cryin’, and you’ll feel just like a fool.
Now you know the road to glory, and it never need be gory.
I can end my network story, SolarWinds provides the tool.
(For your Halloween network entertainment)
Swift Packets!
Rick Schroeder
October 28, 2015
Hello,
I have migrated Orion to HTTPS. However, for security purposes we needed to sign the certificate to do so using the FQDN. Which means that the old URL of $servername is will pop up SSL warnings because it's not what my certificate is for, naturally. Is there a way to have Orion updated to move people to (URL example) https://$orionserver.FQDN instead of https://$orionserver ?
Example
Every URL in every alert contains $https://orionserver instead of orionserver.fqdn. Which means SSL warnings.
Does anyone use Solarwinds to monitor CATV Head-End, CATV Fiber Nodes or any cable system equipment? I have a long background in CATV systems, but have not been working in that industry for the past 8 years, but have been working with a wireless ISP managing their NOCC and SolarWinds. We are in the process of acquiring some cable systems and need to start thinking of what I can and cannot monitor from Solarwinds on these new sites.
Hi Guys,
I've recently started at a company and I have been tasked with improving the Solarwinds monitoring. I had experience with other monitoring tools but I'm relatively new to Solarwinds.
Currently we mainly use NPM and NCM but we only really look for ups and downs. We are monitoring switches, routers, phone systems and servers. I'd like to branch out with the monitoring and do more than ups and downs but I'm wondering if you helpful people can give me some guidance on what’s best to alert on? I'd like to create some new alerts but I'd rather not do it just for the sake of adding new alerts...
The alerts I'm thinking of adding are:
Is this a good start or can anyone else think of others things that would be added benefit to Solarwinds?
Ok I know there are posts regarding this out there but the site is still having searching issues and every time I search I get 0 results.
I need to try and create a report or query letting me know of any nodes configured as SNMP but are now failing. We did a group policy push to all servers recently and several of them it appears SNMP didn't restart. I am finding a handful today that haven't collected data in 2 weeks since the push. The CPU and Memory resources don't have any data in them since 10/16.
I will get into how ticked I am that an SNMP monitoring system doesn't alert out of the box when SNMP is failing later but right now I need to get some kind of grasp of how many of my nodes are affected.
Background:
Thousands of Meraki devices needed to be added to Solarwinds for my situation, and so the hunt began. First stop was Meraki for some help, which led me to this document: https://docs.meraki.com/download/attachments/13500458/ConfigurationGuide-Meraki-SolarwindsSNMP%20(2).pdf?version=1&modif… The document's instructions weren't for the implementation that I was looking for, and that document was all I could find in online. What I needed was to poll the devices directly instead of through the dashboard. When I followed Meraki's document for alerting, it wasn't what I was looking for. Passing relevant information to the alerts wasn't available, based on Meraki's instructions. Eventually, I accidentally stumbled upon the answer, and now looking back it seems so simple .
How-To Steps:
Results:
Here's a Meraki MX80 that's been added.
Here's an MR16 that's been added:
After the nodes have been added, I setup alerts and they'll be able to pull helpful information (Hostname, IP, Custom Properties, etc.) when an event happens.
Misc. Info:
Version info: NPM 11.0.1
Devices I've tested:
Firewalls
MX80
MX400
Wireless Access Points
MR16
MR18
Switches
MS22P
Current issues:
From the screenshots you can see that the Last Boot date isn't correct, however that isn't a pressing issue for me.
I hope this will help some of you, and feel free to ask questions.
I'll be adding updates as more info comes in, so feel free to post what you have run into.
Message was edited by: Naters
Hi All,
I am new to SolarWinds and currently working my way through some maintenance tasks.
One of the tasks is to track down and remove network interfaces from nodes that are in a down status that do not need to be monitored.
I've used a mixture of SQL from the report generation tool, and my own adjustments to come up with the following:
| SQL |
|---|
--This script is intended to track down all network interfaces that meet the following criteria: --Have a status of 'Down'. --And have not sent or received ANY data for the past 12 months. --The script then deletes the interfaces it finds from the 'interfaces' table using the interfaceid as the search term.
declare @Temporary_Holder TABLE (Number INT) --Declares temporary variable to hold the findings of the script.
insert into @Temporary_Holder --Specifies that all findings of the script will be temporarily stored in @Temporary_Holder
select Interfaces.InterfaceID AS InterfaceID
FROM (Nodes INNER JOIN Interfaces ON (Nodes.NodeID = Interfaces.NodeID)) INNER JOIN InterfaceTraffic ON (Interfaces.InterfaceID = InterfaceTraffic.InterfaceID AND InterfaceTraffic.NodeID = Nodes.NodeID)
WHERE ( DateTime BETWEEN 41707 AND 42073 ) AND ( ((NullIf(In_TotalBytes,-2)+NullIf(Out_TotalBytes,-2)) = 0) AND (Interfaces.Status = '2') )
GROUP BY Interfaces.InterfaceID --The above section finds all interfaces in a 'Down' state where no data has been sent or received for the last 12 months. --It also groups the findings by interfaceID for easier reading/processing.
select * from interfaces where interfaces.interfaceid in (select * from @Temporary_Holder) --Lists the findings of the script. Uncomment as required.
--delete from interfaces where interfaces.interfaceid in (select * from @Temporary_Holder) --Deletes the findings of the script. Uncomment as required. |
The script searches specifically for interfaces in a 'Down' state that have sent/received 0 data in the last 12 months and then either lists the results or deletes them as desired.
Now my question is, is this the correct way of doing things or is there a more suitable script or process in the GUI that can achieve the same result.
My concern is whether the interfaces need to be deleted from more than just the interfaces table for the change to take affect without causing ugly issues afterwards such as orphaned data in the database.
I do plan on running a full re-scan in SolarWinds after the script, on the basis that the interfaces will be found again but not 'checked' to report their status.
Any input welcome. The whole point of the task is to stop SolarWinds reporting issues with interfaces that are not in use.
Note: The number of interfaces is ~4-500, so while it could be done manually via the GUI I would rather avoid it.
Thanks,
-CRe
Due to security requirements, ICMP is being denied on the firewall that we have to get through. This has provide detrimental to our monitoring capability of a remote site. In fact, there are issues with snmp traps, but that is something I can clear up. Is there a way to monitor heartbeats across the WAN when ICMP has been blocked? Would an instance of SolarWinds at the remote site forwarding information on the heartbeats of the equipment there and forward the data to the SolarWinds instance at my location.
Thank you.
Robert
Wanted to get some thoughts/suggestions here as I have a case open with Support, but don't seem to be getting anywhere.
Our Orion database is about 277GB and we've only been using SolarWinds for about 3 months now. We've adjusted retention thresholds throughout (NPM, SAM, and etc), run maintenance jobs within SQL, run the SolarWinds Database Maintenance, but the database is still continuing to grow. These 2 tables are the largest culprits:
APM_DynamicEvidence_DetailData
APM_DynamicEvidence_Detail
Both of these tables are close to 90GB. SolarWinds Support pointed to the SAM retention thresholds, but after adjusting them down to keep only 5 days worth of data and running the maintenance/shrinking, we still haven't gained back any space. We are soon going to be out of disk space on this physical SQL server and I'm hoping to avoid that if possible.
Your help is greatly appreciated!
I noticed my main orion server/poller is unresponsive after reboot and MSMQ service is (60 min after windows started still "starting." The server is unresponsive, I cant get even RDP.
All I can do in this situation is (from console): start services from TaskManager, set MSMQ service to manual start, reboot. Uninstal MSMQ feature, delete whole MSMQ storage, install feature again and (for sure) run config wizard.
Obviously its not my favorite way of restarting Orion server.
Does anybody provide me some advice what should I look for?
Thanx a lot.
Orion Platform 2014.2.1, SAM 6.1.1, QoE 1.0, IPAM 4.2, NCM 7.3.2, NPM 11.0.1, Toolset 11.0.0, UDT 3.1.0, IVIM 1.10.0, VNQM 4.1 ; all @ 2008R2/ SQL 2012
Hello all -
We have recently been upgrading from 3900 series to 4300 series which runs IOS XE.
Somewhere along the way, the Machine type has become only 'Cisco' rather than 'Cisco 4331' as it use to show when we had the 3945's installed.
Looking at SNMP responses, it looks like maybe Orion was parsing the SysDesc to gather that information.
From 2921:
Name/OID: Cisco IOS Software, 2800 Software (C2800NM-ADVENTERPRISEK9-M), Version 12.4(24)T2, RELEASE SOFTWARE (fc2)
From 4331:
Cisco IOS Software, ISR Software (X86_64_LINUX_IOSD-UNIVERSALK9-M), Version 15.4(3)S1, RELEASE SOFTWARE (fc3)
In looking in the product mib, .1.3.6.1.4.1.9.1.2068 doesn't exist. I'm thinking that's a Cisco MIB update?
On 4/2, we upgraded SolarWinds. Now when I click on a APM: HardwareSensorDetailsURL in an alert, the link no longer works. I noticed that the port number now contains 80 (https://server name:80/Orion/View.aspx?NetObject=AHS:916) where before it was 443. When we switched over to use SSL a few months ago, I found a discussions where it said to run the following query (update websites set sslenabled = 1, port = 443 where servername = 'servername') which worked, but obviously it was not the correct way to retain the settings.
How should this really be done? I found a custom.config.txt file in the /inetpub/solarwinds/orion folder, but didn't find a custom.config file.
There are entries in the ConfigurationWizard.log.2 file that was ran on that day.
The IIS Manager shows the website setup with a port of 80 and a SSL port of 443.
In a process of creating better F5 loadbalancing support, we would like to know what reports for your F5s would you like to see created by default in a next version of NPM.
Thanks for your comments and feedback in advance!
Peter
Hi,
Is there any way to change this sql header in the Custom SQL alert ?
I need insert a little different sql.
Thanks
