Hi Folks,
I would like to know if the available ressource in web report named "Percent Errors (Transmitted + Received)" can be used in interface report or not? it's available but I'm wondering that will be used for SAM and not interface!
In the case it can be used for interface errors reporting, what's the calculation formula used to generate this output?
Regrads.
Salah
I have both NPM and UDT but I'm not sure which, if either, app can do the following. I want to build a report that can tell me the last time an interface or port saw any traffic. My ultimate goal is to use Orion to identify ports that should be placed in admin down status if they have been inactive for say, 30 days.
Has anyone done this? I would greatly appreciate any help. Thanks.
Is there a limit to the amount of custom properties you can setup on a node using SNMP before it starts to degrade the polling cycle?
This is how I was able to upgrade an Additional Poller running NPM 12.0 to NPM 12.0.1. Installs from system to system may very.
Step 1. Upgrade Core Orion Server Software first.
Step 2. Install NPM 12.0.1 Poller software
Step 3. Install NTA 4.2.1 Bundle
Step 4. Install NTA Hotfix 1
Step 5. Run Configuration Wizard
Step 6. Install NCM 7.5.1 poller software
Step 7. Install SAM 6.3 poller software
Step 8. Run Configuration Wizard
Step 9. Install SAM Hotfix 1
Step 10. Run Configuration Wizard
I was hoping Solarwinds could have updated the Additional Poller Bundle with the recent Core Software upgrade, but I am guessing I am too quick on the upgrade trigger.
I tried the (NEW) Orion Scalability Engine Installer, but I am unable to download .exe files.
Once upon a time there was a product called Fail Over Engine... This product was to allow companies a real disaster recovery option. The community that used it was less than pleased. Even though this product functioned (debatable) in a way which allowed IT monitoring architects check off a box that said a DR plan was implemented there was always an asterisk involved(This made the SolarWinds Subject Matter Expert (SME) a little uneasy- or at least me).
What could be done?! There must be a better solution... Well folks I am here today to tell you a little story of a SolarWinds evangelist who never gave up having faith in the company (SolarWinds) and the software (Orion and all Modules) he championed for the last 4 years of his 19 year IT career.... OK enough of all that.
Here's the deal. SolarWinds came out with HA for Orion and it is a marvel. I absolutely love* it and here is why (Notice the asterisk?.. Can't escape it yet but hot ******* is a great product. I'll explain a little later.)
1.) It installs ridiculously easy and configures just as easily. Creating Pools, sending HA alerts, and removing pools are a cinch.
2.) It allowed me to never have to install FOE again. (It was ok for its time but there were a bunch of configuration gotchas and seemed like every time myself or any of my coworkers installed it was a unique first time)
3.) Clean and very cool UI (I mean really cool and there is some Rubik's cube looking thing that turns as the page loads).
4.) Failing over happens very fast. I have run tests and 100% of the time it takes 4 minutesfor the other server in the pool to become fully active. NOTE:This applies to the Orion Core or the APEs
I am attaching a Visio diagram which shows my environment. NOTE: all of the IP Addresses and names have been changed to protect the innocent.
| HA Pool | HA VIP (non-routable) | Site 1 - Server 1 | Site 2 - Server 2 | URL / DNS Alias (Hosted on Netscalers) |
|---|---|---|---|---|
N / A | N / A | Additional Web Server (Active) swweb01.coolcompany.com | Additional Web Server (Active) swweb02.coolcompany.com | https://sw.coolcompany.com |
SWCORE01-HA-POOL | 10.70.70.10 | Orion Core-01HA01 (Active) 10.70.70.110 SWCORE01HA01.coolcompany.com | Orion Core-01HA02 (Passive for HA) 10.70.70.210 SWCORE01HA02.coolcompany.com https://swcore01ha02.coolcompany.com | Orion Core 01HA Alias (For Traps - auto-DNS Failover) SWCOREHA01.coolcompany.com |
SWAPE01-HA-POOL | 10.70.70.11 | APE-01HA01 (Active) 10.70.70.111
SWAPE01HA01.coolcompany.com | APE-01HA02 (Passive for HA) 10.70.70.211
SWAPE01HA02.coolcompany.com | SolarWinds APE 01HA Alias (For Traps - auto-DNS Failover) SWAPEHA01.coolcompany.com |
SWAPE02-HA-POOL | 10.70.70.12 | APE-02HA01 (Active) 10.70.70.112
SWAPE02HA01.coolcompany.com | APE-02HA02 (Passive for HA) 10.70.70.212
SWAPE02HA02.coolcompany.com | SolarWinds APE 02HA Alias (For Traps - auto-DNS Failover) SWAPEHA02.coolcompany.com |
SWAPE03-HA-POOL | 10.70.70.13 | APE-03HA01 (Active) 10.70.70.113
SWAPE03HA01.coolcompany.com | APE-03HA02 (Passive for HA) 10.70.70.213
SWAPE03HA02.coolcompany.com | SolarWinds APE 03HA Alias (For Traps - auto-DNS Failover) SWAPEHA03.coolcompany.com |
| N / A | N / A | (Active) SQLSOLARST101.coolcompany.com | (Passive for Log Shipping Fail Over) SQLSOLARST201.coolcompany.com | SQL Server Alias (For auto-DNS Failover and OrionDB Connection) SQLSOLAR01.coolcompany.com |
Up to this point the environment seems standard. There is one exception to this. The HA IP Addresses are non-routable (I requested a network that wasn't routable from my network engineers and they gave me the 10.70.70.0/24 network. I chose all the IP Addresses to sync up on the last 2 digits example. x.x.x.10(Virtual IP), x.x.x.110(Site 1); x.x.x.210(Site 2) . The IP Addresses are not in DNS and I created a secondary Interface on the node as SolarWinds_HA. I also tested this as an additional IP Address on the primary interface and it works too. Here is the configuration broken down for the Orion Core (if Site 1 is active)
| Server Name | SWCORE01HA01 (Active) | SWCORE01HA02 (Passive) |
| Interface 0 Primary IP Address | 10.12.15.72 | 10.19.72.121 |
| Interface 1 Primary IP Address | 10.70.70.110 | 10.70.70.210 |
Interface 1 Additional IP Address VIP Automatically Assigned via SolarWinds HA | 10.70.70.10 | The VIP is not assigned until it is active |
To sum this up we have been running this configuration for a few months and it works exceptionally well. We have placed a tick in the [HA across the WAN for Monitoring]. The only reservation management has is they would like to have this become a supported configuration. I trust SolarWinds is testing an HA over the WAN additonal solution but until it is available this works and works well!
Enjoy!
If you have any questions please feel free to reach out and I will help if I can.
-Philip
I've created a Transform Poller that is simply the addition of the values of two pollers. I run the test and the transformed values are displayed as I expect. I have added the poller to several nodes and its enabled. When I go to one of the nodes and click on the Transform Poller there isn't any data being collected. What am I missing? Why is it not collecting data? Currently the interval is set to 2 minutes.
One thing to note, I'm new to SolarWinds so as much detail as you can give would be appreciated.
The User Experience group wants to see how you've customized your Orion to create your own NOC view, or NOC views you like and are using from other products. What do you like about your NOC view? What challenges, frustrations or issues do you have with it?--Show us your NOC view either here OR email it directly to me at kellie.mecham@solarwinds.com and share your NOC view stories by August 10 and we'll award you 500 thwack points for sharing.
This articles is interesting: Polling - How much bandwidth does SolarWinds require for monitoring but is aimed at calculating the bandwidth consumption for device polling. It does not explain the required bandwidth between a SolarWinds Poller (main or additional) and it's SQL server.
Once the data is received at the poller level, is it a 1:1 scenario while being sent to the database server or is there more (or less) to it? How to is translate into consumption while being sent to the SQL server?
Does anybody can shed some light on this or refer me to some doc?
Cheers,
P.
Is there a way to deploy and utilize QoE for RHEL/CentOS 6/7?
How can I create view in NPM Load Balancing which only show Virtual Servers which begin with "BB" and don't have "redir" in the name?
my solarwinds server is totally crashed due to some hardware issue so m unable to deactivate license key. So how can i get the key deactivated from crashed server and use it in new server .new server is configured everything is done just key issue any help..
I have configured a couple of wireless heat maps.
My issue is that when I run the map I get the following error:
Automatic re-generation from 12/1/2015 11:15:59 AM was not successful. Try to generate in the Network Atlas manually and updated map will be visible here.
Last error message: 'There is no available engine to process the WirelessHeatMap generation.'
I am new to Solarwinds and have no idea what I am looking for.
Can someone send me in the right direction?
Thanks
Please expand on “Other” and why by adding a comment below.
Tell us your biggest pain point when troubleshooting IT issues, e.g. users complaining about slow or broken access to applications.
Select your biggest pain point from this list.
Of course any additional comment to this page would be great (e.g. second biggest, pain point not listed below...)
Orion Platform versions above NPM 10.6
Strongly recommended to have latest version of Orion
All of us know SolarWinds SLX license you can monitor up to 12000 Elements and beyond this you will need an Additional Polling Engine to monitor.
Use additional polling engines for 12000 or more monitored elements if you plan to monitor 12000 or more elements, Solarwidns recommends that you install additional polling engine on separate server to help distribute the work load.
What is Stackable Additional Polling Engine idea is ?
Its another engine on the existing system hardware you have , using full capacity of your current hardware . This engine will be stacked with your existing engine seamlessly running on the same hardware boosting the existing polling capacity of current host without any additional cost to maintain another system host.
Idea is exactly adding another stackable switch within existing chassis to add more capacity . So if your existing chassis can take it you can add more stack into .
With the latest version of SolarWinds NPM, you can now install up to three unique polling engines on a single polling server, sharing a single IP address. Stackable polling engines enable you to effectively triple the polling capacity of a single server so you can get benefit of available server hardware within the existing installed environment
Further it will help you to monitor more Elements ( Nodes/Volumes/Interfaces/Services ) without having any dedicated servers to be confirmed and manage so its less overhead for the I.T staff to manage .
Benefits :
No overhead to manage or arrange another system hardware just using existing Server hardware capacity (Very cost effective )
No management approval process waiting time for system deployment
No infrastructure change required
No troubleshooting and I.T management resources to dedicate for another hardware
No extra IP address needed to be allowed for the devices for the polling / Downloading the configuration with NCM - Less overhead
No downtime required during installation
No configuration wizard need to run
No services need to restart during this process on production environment
No FOE licenses per server to cover more elements for HA (Very cost effective )
Freedom to extend any Poller (Primary Polling Engine OR Existing Additional Polling Engine ) (Very cost effective )
Finally within few minutes you will be ready to polling more elements within the existing infrastructure without making a single change and wasting the time / resources / money.
How can i check my Server current hardware meeting this requirments
For more informaiton MINIMUM Hardware Requirments see below.
SolarWinds Orion server hardware requirements
How many Stackable Poller license I can have on the Single Server?
Up to three total polling engines may be installed on a single server (i.e. one primary NPM
polling engine with one or two additional polling engines on Primary Server or three additional polling engines on
the Additional polling server ).
Note: A stack requires only 1 IP address, regardless of the number of APEs
Can I install Stackable Poller on my existing Additional Polling Engine?
Yes 'Stackable Poller' extending capability on the Poller you can have multiple Stackable poller up to 3 on your existing Additional Poller It can be update by Smart Bundler
How can I update my Poller for Stackable Poller?
On the Poller it can be updated by Smart Bundler.
It means that by additional poller package downloadable from customer portal (not the Individual Downloads, but the Main Additional Poller Installer also called Smart Bundler).
How to install Stackable Poller on my Primary Polling Engine?
In this example I am assuming we are implementing Stackable Poller on the Main Poller (that has enough resources to tackle additional load)
As you are aware a single poller can tackle upto 12k elements
Also there is no special installer for Stackable Poller
You will need a license to be purchased as for Additional Polling Engine
You will go into your Customer Portal & download the Additional Poller Smart Bundler (not the Individual Downloads, but the Main Additional Poller Installer also called Smart Bundler)
Basically when you will run Additional Poller Smart Bundler this installer will say on the main poller that everything is already installed and ask you if you want extend license.
Now simply key in the license of the Additional Poller in the wizard
It will never install anything on main poller it only just update the license and will deploy the stack Engine seamlessly
So the customer has got extra capability to fully utilize his server hardware
Also after the license has been applied you can open the License Manager and you will see another entry in the Lincense Manager as following
On Primary Polling Engine it will take up to 2 MAX Additional Polling Engine license keys
On Additional Polling Engine it will looks like this
You will have the message "The machine has reached to license limit" after that therefor it will only be able to take up to 3 licenses.
So if I have have mutiple modules installed on the Primary Poller (do I have to install all the other modules as well , because Smart bundler will download say APE SAM , APE UDT , APE NPM)
When I will run the Smart Bundler on the Primary poller (it will not say that Primary Poller is already installed on this machine)
Yes, it will say on main that everything is installed and ask you if you want extend license so it will never install anything on main (as the required services are already installed and doesn't required any extra service to be installed ) , Just update license and deploy the stack Engine seamlessly the main propose and stack functionality .So it does make necessary changes required without installing any service or software that's how its by design to work .
If I will install Stackable Poller on my primary server it will increase the capacity to 24K elements to tackle?
It will ask you on main to add license key for additional poller (means 24k elements). Once you run it again, you can add another AP license (means 36k elements) and if you run it third time,
it will say This machine has reached its license limit . The same functionality is for Additional Poller installation and yes, Stackable poller
I have SLX Licenses why i still need the Additional Polling Engine license ?
The SLX license is based on throughput, not elements. This is a completely different type of license than our element tiers.
The NPM SL100 license is based on elements. The NPM SL100 is a hard limit of nodes, interfaces, and volumes. You can modify the polling intervals, but you cannot exceed 100 nodes, interfaces, and volumes.
With an NPM SLX most customers can manage about 12,000 elements at default polling intervals today. Many customers modify polling intervals and can manage many more elements because we do not cap the number of elements.
Our development team made multiple performance improvements and increased the throughput a SLX license and APE can poll. Over the last 5 years we’ve increased the throughput so that at default polling intervals a customer could go from monitoring 8,000 elements to 10,000 and now to around 12,000 elements. While I can’t commit to increasing this again in the future, we have a consistent track record of doing so.
Why this often gets over simplified to “SLX == unlimited”. For the vast majority of customers who purchase an SLX, the difference doesn’t matter because they are happy with the default polling intervals and don’t have near enough elements to run in to the throughput restriction.
For more details, please see the post below:
after upgrading to version 12 , we were facing the dependency issue
Is there a limit to the amount of custom properties you can setup on a node using SNMP before it starts to degrade the polling cycle?
Hopefully, someone else has run into this issue and can provide some direction. When we initially switched over to F5 to load balance our 2 additional websites, we were using a cookie based persistence and that didn't work well. Folks had to continuously clear their cookies and cache to access the website. We changed over to source-IP based persistence and things seem to be working better but we are now seeing regular occurrences of the login URL (https://CNAME) changing to https://CNAME/Orion/Login.aspx?sessionTimeout=Yes and folks being prompted to login rather than being logged in automatically. While our SolarWinds groups are set to disable the session timeout, I'm being told by my F5 admin that the F5 uses a persistence profile timeout value of 3600 seconds so I'm not sure how to get around this.
Can anyone provide a recommendation on how our F5 should be configured for our Additional websites so folks don't get prompted for login? Thanks for reading and any feedback you can provide.
Robert
What version of BIG-IP your F5s run?
Good morning.
I am having issues with network discovery. No matter what I do, it seem to always fail the network discovery. I am unsure if it's because of a timing issue, the fact that maybe it's a permission issue, or other. But if I leave the auto discovery over night, it always says not complete. Has anyone else had this issue? Or is it me? Is it a setting where it times out after a certain period of time?