Hi
Is that SR for 11.5 ?if YES why is it RC1?
/SJA
That's correct - it's an RC for the SR. No additional features, but quite a few fixes outside of what has been released in HF format.
Hi
well that's the first time I see RC for service release ...but we had a lot of change in that 11.5
best of luck
we really like to hear some positive vibes
rob.hock i looked in the zip file but no PDF on whats been fixed .. can you share that
We do not have RN's published yet, but we'll have them in the near future.
I was planning on upgrading to 11.5.1 tomorrow but I now see that 11.5.2 is in RC. Should I hold off and wait for 11.5.2 to go GA?
If it helps inform your maintenance window- it will likely be a matter of a few weeks before 11.5.2 GA.
rob.hock thanks! I am currently on 11.0.1, are there enough issues with 11.5.1 to where I should hold off until 11.5.2?
If you were looking to upgrade immediately, 11.5.2 RC has a superset of bug fixes / enhancements compared to 11.5.1.
RCs are fully supported in production.
Looking forward to GA and release notes.
rob.hock We are planning Solarwinds upgrades for June. Currently, we should get to the 11.5.x upgrade by mid-June. Do you think that 11.5.2 will hit GA by then?
There is indeed a high-probability of GA by mid-June. Unfortunately our legal-types do not allow us to confirm precise timeframes.
In contrast to that question, any known new issues with the RC thus far?
I thought upgrading to 11.5.2 or the new RC fixed most of these problems with 11.5.1 without having to mess with hotfixes or workarounds?
Folks,
I upgraded to 11.5.2 but it did not fix my alerts problem. Specifically, SW is constantly sending alert for a hardware issue that was resolved over a month ago. By the way, we tried already acknowledging the alert, but it does not stop the emails (about every 15 - 20 minutes). Also, disabling and re-enabling the hardware alert does not correct the issue either.
Needless to say, our NOC team is quite tired of getting the same obsolete email over and over... over a hundred each day. I can't blame them, since I get copies of every one of those emails. So, my inbox gets flooded too.
Thanks for the update
Hope for some good news...
Let us know anyone that does the release candidate if it resolves a bunch of stuff... I'm sitting on Orion Platform 2014.2.1, SAM 6.1.1, QoE 1.0, NCM 7.3.2, NPM 11.0.1, NTA 4.1.0, IVIM 1.10.0 for now until I hear a little more good news... 11.5.2 sounded like a huge improvement over 11.5.1 for sure!
I foolishly upgraded to 11.5.2 today as it's out of RC but alerting has totally gone wonky for me. "Scope of alert" seems to be horribly broken. We've got 50+ alerts on nodes that don't have a problem. For example the alert triggered because the node had -2% packet loss?! Clearing the alert just triggers it again immediately. Time to open another ticket...
C'mon Solarwinds. Years ago the software releases were bullet proof. You're adding loads of really cool and useful features but it's so damn buggy all the time.
I said release candidate above because I think there's a post 11.5.2 RC out there called some higher number...
Given what all the problems we've seen since v11.5, I am wondering if the RC process itself needs tweaking as well. After all, the RC process is supposed to identify and address bugs and other issues before the product goes GA. By the way, syncopix is right, we did not see nearly as many major problems with previous releases.
As for me, I did not see the alert problems in my lab server. Maybe it was because my lab server has a small number of nodes being managed. So, my testing of the RC's may be limited by the devices (and/or device types) that I am able to add to the lab vs the production servers. However, I cannot afford to purchase a unlimited licenses for my lab, like those we have in production. I don't think I am alone in this predicament, am I?
While on the subject, these bugs have put me and my teammates in a difficult position. We persuaded our managers to invest heavily in many SolarWinds products, praising their features and reliability. In the past few months, I have been giving only apologies, excuses which is starting to get old with my users -- and with me as well.
By the way, as syncopix stated, c'mon SolarWinds. We need your developers to ensure the GA releases are solid. I am not asking for perfection -- just not so many and major bugs.
Before jumping to 11.5.2 RC1 I was assured that it was supported in a production environment. The first support guy I talked to didn't really want to help me because I was on an RC. I am still kicking myself as I still have 5 tickets open since upgrading to it and it's sucking up a ton of my time.
FYI, I think I've narrowed this down to any alert that uses a threshold as a trigger condition. e.g. percent packet loss warning/critical threshold, CPU load warning/critical threshold, memory used warning/critical threshold. These were working beautifully in NPM 11.5.1 and 11.5 but are totally broken in 11.5.2. Seems to be constantly triggering these alerts. Somehow it's even triggering these alerts on nodes that aren't polled (they're "External") and reporting a critical CPU threshold of -2%!
Like mr.e, I'll be having to give more apologies and excuses to managers tomorrow morning. Ironically, today I was convincing them why they should approve our renewal...
</moanfest>
Hi syncopix,
Did you get your threshold issue in 11.5.2 fixed? We updated yesterday and we are seeing a small subset of nodes where they are triggering when tho ${N=SwisEntity;M=CpuLoadThreshold.IsLevel2State} is reported as false in the message.
Jon.
As jmiddleton mentioned above we recently upgraded to NPM 11.5.2.
My team uses the NOC view quite heavily and we have it on a big screen 24/7.
This is filtered to only include devices by a Node Custom Property, however since this release it seems to have stopped filtering and includes everything in our SolarWinds instance.
Some panels allow an extra filter to be added, so where possible I have just edited the individual panels, however not all of them allow this so are essentially useless.
Anyone else seeing this?
