SolarWinds has Product Upgrade Advisor website which helps users to validate compatibility of product versions.https://customerportal.solarwinds.com/support/product-upgrade-advisor
Do you use that prior any product upgrade?
SolarWinds has Product Upgrade Advisor website which helps users to validate compatibility of product versions.https://customerportal.solarwinds.com/support/product-upgrade-advisor
Do you use that prior any product upgrade?
I have been working on some dashboards with some UnDPs that are 0 or 1. I'd really like to just display a graphic showing a pic of a light switch On or Off, or maybe a Green or Red light. Does something like that exist and I've just missed it?
And how about a vertical gauge that looks like a thermometer?
Hi All,
Since the release of NPM 12.0.1 we have an exciting new feature - High Availability - in Orion platform. The only minor downside is that it does require HA cluster to be sitting in the same subnet. Oops... For some minor, for other major. What do you do when you have two sites and you cannot stretch subnet easily due to architectural constraints?
Well, I have been digging this for the past several weeks. FoE is not being sold anymore. It may well be supported, but you certainly cannot buy it if you are a new customer. I have started FoE thread here, which has great insights, although now it is not relevant anymore. At the moment it seems like there is a gap for smooth inter-site fail-over solution and I hope this will be plugged soon. As of now SolarWinds offers Active-Active approach (you can find PDF about it in FoE thread as well or just get it here directly).
At first I though that maintaining two instances manually will be a huge pain and massive overhead for engineers and this was stopping me from accepting this idea. However, thinking further and after consulting with SolarWinds support I have realised that we do not need to. Here is what I came up with:
(1)
First - you do need to purchase another additional set of licenses that you have got already (this is the most painful step). To soften this a bit - contact your SolarWinds re-seller partner (or SolarWinds directly) and ask for 50% discount. This is known as "Disaster Recovery License" and is being offered upon request
(2)
Deploy live environment as normal, add all nodes, configure settings, alerts, etc - as usual practise, nothing fancy here
(3)
Deploy exact copy of your live environment at the DR site, use Disaster Recovery License and point it to "empty" database. By "empty" I mean that you do not need to populate it with any assets, just install fresh deployment and leave it as it. You don't even need to configure any settings, views, etc - just vanilla setup (cold standby so to speak)
Now, you will have an Active-Active setup (although not quite Active-Active as initially suggested by SolarWinds in the above PDF. I would rather call it Active-Reserved, because at the DR site you do not add any devices and you do not configure it)
DR considerations:
SolarWinds kit at the DR site will just sit there and do nothing until DR is invoked. We have Database AG in place (mirror formally). So, in the event of main site failure SQL will fail over to mirror copy at DR site. Because we already have SolarWinds deployed at DR - all what will be left to do is to run configuration wizard and re-point DR deployment from empty db to mirror copy of live db at the DR site. Recovery process should last as long as it takes for the configuration wizard to complete its magic (haven't measured it yet, but it will depend on number of module, hardware kit, etc. I anticipate under 2 hour). Well, not instant fail-over as with HA - but good enough, providing that monitoring by itself is not business critical tool and in the event of site fail-over monitoring definitely is not on the list of priorities for the business to worry about, unless you are managed monitoring solutions provider (which I hope you are not, as otherwise 2 hours recovery may be a "killer").
If you do not have SQL AG, then simply ensure you backup your SQL at live site and transfer your backup over to DR site on a regular bases. No need to recover, but fresh backup should be available in the event of DR to restore DB at the DR site
To "complicate" things further (or I would better say to safeguard and increase availability) - we also plan to create HA cluster for application layer (new feature) at both sites, therefore protecting from local app server failures. Although HA at DR might be a bit excessive - we would like to keep things as closely mirrored as possible between DR and LIVE sites
And, yet another thing - NTA server. You can have it on same APP box (which is not recommended, although fully supported), or you can have a separate box. In the event of DR you simply recover NTA DB from backup at DR site and then you should be able to switch to DR box as well
Grey areas:
Final say:
Once again, after digging through many different options - this one seems the most appealing, with virtually no overhead for Engineers on a day-to-day running - which is key to not overload them. Running Active-Active and managing all changes manually at both ends is way too much - sorry, no, sorry
Diagrams:
Normal operation
Site failover:
I have created Custom Table for a view and run a SQL query for the result.
Here when I tried to enable 'Details Page Link', it show error (NODENAME - 'Details Page Link' data presenter requires 'db|DetailsUrl' field(s) to be present within the datasource).
Concurrent Connections by Virtual Server.
This looks like it would be very helpful to understand LB volume and as upgrades happen it would be very interesting to see if this and or other LB statistics change..
Creating dependencies using groups is a long and tedious process. The problem with groups is that it already uses dynamic queries to define the members using CP. So why even use the groups - just use CPs. Group structures are not changeable, other than deleting and creating it. Plus some other issues with groups, such as groups not being updated properly because of subscription errors. And limitation on number of groups. If someone has 2000 sites, then creating those 2000x2 groups (parent, and child) is not practical.
It's a lot easier to use properly structured custom properties. This is the process I came up with, along with the SQL code (I'm sure SQL gurus out there can optimize this).
1) Create CP called SiteID. Tag it with unique Site identifier (001, 002, etc).
2) Create CP called Layer. Tag it with WAN for all WAN routers (for other devices you can use LAN, Firewall, Switch, etc)
a) The alert will look for the CP "WAN" withina SiteID and get the satus of the WAN node. This will serve to define a dependency.
3) The key to the code is the row_number (very similar to the rank) which returns the row of the returned dataset. The full custom SQL alert is:
Select Nodes.caption, nodes.nodeid From nodes (Base code that SolarWinds Alert gives you)
Where (nodes.status=2) and
(
(nodes.layer not like 'WAN') and
(
((select status from (select row_number() over (order by nodeid) as rownumber, status from nodes nn where (nodes.siteid=nn.siteid) and nn.layer = 'WAN') as foo where foo.rownumber=1) is null) or
((select status from (select row_number() over (order by nodeid) as rownumber, status from nodes nn where (nodes.siteid=nn.siteid) and nn.layer = 'WAN') as foo where foo.rownumber=1) =1 )
)
or
(
((select status from (select row_number() over (order by nodeid) as rownumber, status from nodes nn where (nodes.siteid=nn.siteid) and nn.layer = 'WAN') as foo where foo.rownumber=2) is null) or
((select status from (select row_number() over (order by nodeid) as rownumber, status from nodes nn where (nodes.siteid=nn.siteid) and nn.layer = 'WAN') as foo where foo.rownumber=2) =1 )
)
or
(nodes.layer like 'WAN' or nodes.layer is null)
)
4) For testing. I created 4 nodes. Node1=8.8.8.8(WAN) Node2=8.8.8.1(WAN') Node3=8.8.8.2(non-WAN1) Node4=8.8.8.3 (Non-WAN2). Then change the state of the nodes (8.8.8.8 is always up, anything else will be down).
The script can be expanded using OR to check for 3 more more WAN routers.
Thanks
Amit
What version of BIG-IP your F5s run?
What percentage of all your switch ports approximately comes from stacked and standalone switches?
There has been over 1 million of Cisco ASAs built and deployed around the world in a past years (good job Cisco!). As not supporting SNMP protocol properly, they often complicate our lives when configured to be Default gateways, not allowing products like SolarWinds User Device Tracker to monitor what's behind. Do you use your ASAs as a Default gateways too? If so, what percentage of your network they route?
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...)
When adding new nodes to NPM, do you use Network Sonar or you add your nodes directly?
Do you have a need to detect rogue APs connected to your network?
Which of the following is your highest priority feature provided by your MDM solution?
Feel free to add more options in comments and vote for them using Like button!
am trying to add action to send me sms when alert triggered , i tried note pager pro but unfortunately carriers in my region don't support sms protocols (SMTP, SNNP ...) so i need help to have any other way to do that plzzz
Good afternoon.
So I have installed all apps on a new box, built a new, shiny SQL clustered environment to ensure that things stay up. I am looking to get funding for failover with solarwinds too.
The thing is, I have the following problems:
- New NPM 12 is REALLY slow. I mean almost like old man trying to write a birthday card slow.
- I don't think it's the spec of the machine, or what the machine has on (in terms of applications and nodes) It has five solarwinds applications on:
- NPM
- NCM
- IPAM
- WPM
- SAM
It is the following spec VM running in VMware 5.5, but an upgrade is on the way (these are gen 9 hp's) I checked with solarwinds and for our licensing, this would be perfectly fine spec. Baring in mind, the SQL servers are exactly the same spec of machine.
- 16gb ram
- 4 cores (3ghz)
- Windows server 21k12
- These are attached to fast storage (it is on the same storage as the SQL databases)
I type in the IP address (xxx.xxx.xxx.xxx) and it literally just freezes. it sits there and it's 'waiting' I have tried IE, firefox and chrome (I even wanted to get Opera out.) and it just sits there waiting for the bus. The only address that does work is xxx.xxx.xxx.xxx/Orion/admin. I have checked our older soalrwinds and have copied the exact same IIS settings to make sure it's not that (though we were using old software, hence the new build and not an upgrade). I have ensured that all services and solarwinds services are running, done a reboot, rolled back a snapshot and re-installed and it is still doing the same results.
There are only three nodes that are added to this server (SQL and solarwinds itself) Am I missing something inside IIS (I am not an expert of IIS.) that stops me from connecting to this via the ip address and not from an account itself?
The weekend I thought to run some auto discoveries (because that's the clever thing to do) ran them the weekend. Checked Sunday afternoon (as some changes were being implemented on the afternoon and I was on call) and nothing was added. I thought that was a little weird so this morning I tried adding a couple of nodes manually as I then have control over what I see and both tests failed. So I had a look at the SNMP settings (I did a GPO to change all of the SNMP settings) as you can kinda see (I removed the IP addresses) the strings are the same (as well as the IP address') as the old server. I know my GPO has worked as the old solarwinds has not emailed about any nodes have stopped responding.
Which is why I am thinking, it might be the networking rules, but that can also be dismissed as I can ping to the two nodes from my new box.
Below is a screenshot from my two boxes. One is fine (the old solarwinds), but the other isn't (new). Would anyone have any ideas about this?:
Hi all.
We are new to Solarwinds and have just started using the product, and require a UDP that can access the hardware info of Fujitsu servers such as Primergies, Prime Powers, Celsius Workstations etc - to find HW faults, faulty disks etc. There's plenty on the site for Dell etc but not for Fujitsu. Can anyone help please?
Thanks.
Anthony
(siemens healthcare)