Hi
I know its a big release Sw should not be shy to use "next gen" release...
Bugs are part software dev. And I understand that.
any chance to see that 11.5.1
I'm not fan of hot fixes.
thanks sja
An update to the Orion core just posted this morning, fixing a few issues. You should see it in your customer portal.
But I'm going to say that SolarWinds upgrades are uncharacteristically solid, unless you are seeing a VERY specific kind of bug.
My habit has been to always install the updates as soon as I could get a change window, unless I had a compelling reason NOT to do so. Not the other way around.
jbiggley - confirm or deny?
ommm
hot fix no thanks :-)
yes most upgrade are okay from 10.x to 10.7 great .
from 10.7 to now 11.x solarwinds not to many bugs but too long to fix some....
11.5 is big change expect some bugs part of the game...
sja , call Support - they can ease your mind here. I had an engineer walk me through the possibilities of what the update would fix vs. the current issues that I would experience with update.
For me it is waiting for these hot fixes. So I get the fix via the new version that I want; as well as the Bug Fix to eliminate extra alerts.
Known BUG ->Specifically one of the issues has to do with Node Deletion causing the re-triggering of the alert on that node, EVERY Duration of the check of status....
- so you re-add the node/interface - acknowledge the alert - then delete interface/node again / Making sure the alert is not triggered on the node when you delete it.
But this is minor for most - for me, and the amount of cooks in the kitchen this currently would not be a good known bug to walk into.
Maybe you are the only cook and can swerve this fly on the windshield.
Regardless - Talk to support as they can tell you exactly what you want to know and formulate a plan of action to get where you need to go.
I'm on 10.6 because our 10.4.2 -> 10.6 was a nightmare. We need to get back on the upgrades here but 11.5 is just too big/troublesome for me to consider. I'm going to 11.0.1 this year but even that has 8+ hot fixes. I mean come on where is 11.0.2?
We've had a lot of problems w/11.5, and after all our back and forth w/SW tech support, two problems remain. The first one seems its integration with UDT, which is affecting both of our SolarWinds instances. When I click the View UDT Job Status link, I get the following error:
Could not find any resources appropriate for the specified culture or the neutral culture. Make sure "SolarWinds.Orion.Core.Strings.Resources2.resources" was correctly embedded or linked into assembly "SolarWinds.Orion.Core.Strings" at compile time, or that all the
The second one is affecting onlyone of our SolarWinds instances, where the Service Alert v2 service fails to install during the Config Wizard. The SW techs I worked with were unable to fix either issue, so both cases have been escalated to SW developers. Needless to say, I am far from happy w/NPM v11.5.
Sorry to hear that newkidd2
Please update when it resolved
/sja
I thanks everybody for sharing and updating.
Like I wrote before I hope to see that SR 11.5.1 soon...
There are too many negative feedbacks from "old heands"
/SJA
We have the UDT Job status issue as well...no resolution to that case yet.
Update: We just received a case update that the UDT Job Status issue is resolved in the UDT 3.2.1 RC1 release which is out in the customer portal. I would prefer this to be a production hotfix versus upgrading the entire module to a RC.
All,
I'm curious, do we have any SolarWinds Orion "noobies" that have installed NPM 11.5 and SAM 6.2 together from scratch in a brand new environment, for the very first time?? Are we seeing upgrade issues, or product issues?
Dwyane
I kinda did this on a single node temp install, just to check the upgrade/install process/steps and to check out any new functionality. Here's what I did, in a nutshell:
I installed all our "current" product versions (at that time):
NPM: 10.7
NCM: 7.2.2
SAM: 6.1.1
IPAM: 4.1
UDT: 3.0.2
Then I performed the upgrades to get us to "the versions we want to go to":
NPM 11.0.1
IPAM 4.2, then IPAM 4.3
UDT 3.1 then UDT 3.2
NCM 7.3.2
Note: I didn't apply any hotfixes to these as they were not really needed.
Then NPM 11.5 RC2 and SAM 6.2.0 RC1 came out before my eval version license closed it down.. I went ahead and upgraded to them
My notes are:
- NPM 11.5 RC2: went ok
- SAM 6.2.0 RC1: went ok, install crashed once, restarted and then ok
*Update*: CORRECTION: I actually installed NPM 11.5 and SAM 6.2 NON RC versions shortly after they were released. I summarized my sloppy notes too much . I noted the RC's were out, then the actual versions were released so I just wrote in that area I had reserved for them.
After that I manually added a few nodes and checked out the new functionality. I didn't run a "test" set of procedures to check out functionality and I didn't even turn on alerting or anything, just played with the web alert GUI, etc. The system stayed "up" until the license ran out (no obvious service crashes).
I then went onto Thwack and looked around for any NPM 11.5 issues. I found a few posts, so I decided to wait as we're not in a hurry to upgrade and we just went to 11.0.1.
"Noobies" or not just think if we didn't had thwack to share bad or good experience....
mmmm..just read the release notes look fine great features ..some bug fix "I take it"
Run the upgrate AND very big https://m.youtube.com/watch?v=g6GuEswXOXo
Homer Dohhs!
That's funny stuff! I was only asking the question because if these are just upgrade issues, I might be able to build a new environment and migrate the data (maybe). But since these issues appear to be a bigger than that, I'm going to stay with my original plan, and wait on 11.5.1+. I can certainly appreciate the efforts the dev and support teams have invested, I'm sure we'll see fixes for every issue soon. I'm in no hurry.
D
Ok so not so Noob, but we have nice shiny infrastructure that shuth is currently installing Dev/PPT environments on.
Orion Platform 2015.1.0, SAM 6.2.0, QoE 2.0, IPAM 4.3, NCM 7.3.2, NPM 11.5, NTA 4.1.0, WPM 2.2.0, IVIM 2.0.0, VNQM 4.2 [EOC will come online later]
He's hit an issue or two as we have an APE - SAM played a not so nice game since the HotFix executable was already installed on the Primary, thus on the APE it complained it couldn't install SAM due to version mismatch.
At present that has the potential to hurt those whom increase APEs with SAM included over time.
I'll let him add the gory details if he wants to.....
:-)
Support is telling us that we need to get to NPM 11.5 to get Aruba wireless polling fixed, and to UDT 3.2.1 to get some of the UDT issues fixed
I have no SAM.
fitzy141 Many thanks for the clarification.
By the way, we just ran into another problem w/the alerts. This one has to do w/alerts based on Universal Device Pollers. Somehow, the link between the alerts and the UDPs is very messed up now. It is very hard to explain, but suffice to say that the SW tech said this is definitely a problem that they have to escalate to the engineers.
NOTE: In hindsight, I really wish that the NPM developers had kept the legacy alerts as option -- just like they did with the Report Writer. That would have given them chance to deal w/the alert problems without so much pressure nor frustration from SW customers.
We are planning an upgrade from 10.6.1 in early June. I'm hoping all these issues are fixed or I might stay one version behind at 11.0.1.
yeah my upgrade from 11.0.1 to 11.5 just tank! Here is my Case # 784008 Created: Upgrading to NPM 11.5 and cannot continue install. Still no response from Solarwinds support. I am getting this configuration wizard error stating multiple instances are running and there is an active running on the additional webserver. I have not even started to upgrade the additional webserver. Very irritating must say!
Alright my issue is resolved! Solarwinds tech needed to go the database and delete the orphaned instance. he went to the database below netperfmon queiered the settings with the commands below and found the orphaned instance settings SELECT TOP 1000 * FROM [dbo].[Settings] select * FROM Settings WHERE SettingsID LIKE 'CW-ActiveInstance-%'
This really was a big change... I'm actually not surprised there are some issues... moving and rewriting the entire alert system isn't a trivial change. I'm not sorry I waited to upgrade. I want a couple of the new features but SAM 6.1.0, NPM 10.7, NTA 3.11.0, IVIM 1.9.0 is running rock solid for me right now. I've been prepping for all of the NTA4 changes and had to get someone to agree to pay for the additional VM's which delayed things for me a little as well. I'm really wanting the new flow database but with so many of our teams dependent on the alerts now that I've gotten rid of most of my other monitor tools and replaced with NPM... I have to be really careful. Please keep us updated on your experience with 11.5.
The SW tech folks recommended for me to apply hotfix #4, to deal w/all the problems we have with the alerts -- and other issues -- since our upgrade to v11.5. I don't have much to lose since my alerts are not working well right now.
By the way, the hotfix #4 takes a bit more effort than I hoped..., quite a bit of files to backup (manually) from several directories, especially on the core NPM server, and also running a SQL script (for deleting orphaned alert history). I told the SW tech that I'd really like to see hotfixes that are "dummy proof", just run an executable that backs up all your files automatically and the runs applies the hotfix. Also, the "dummy proof" hotfix should have an uninstall that brings reverts back, in case hotfix does not work. The SW tech agreed and told me they're working on doing that for hotfixes but cannot tell me when that'll happen.
Anyway, I will apply hotfix 4 this weekend and let you all know. Of course, I will backup my database first..Have a great weekend, everyone!!!
yea i have a ticket open for something trivial and i am playing chase with the tech ..and i have other issues I want to open tickets about but not happy with the support i am getting with one open and everytime i have to do something i need to go back and reapply the hotfixes for the other issues
I'm going to say that overall most things are solid - at least new interfaces and whatnot, but 11 -> 11.5 has been had a ton of minor bugs. So yes, NPM/SAM were never broken, but left with caveats in every scenario. "It works generally, but if you do *this* then *this* breaks", or "this doesn't do this". I haven't seen things like this in a long time, and I respect how much effort goes into getting things this smooth, but a mountain of minor bugs can be pretty troublesome, especially when I can't quantify if they are my environment and what I am doing vs solarwinds updates. Considering that I find solarwinds in general performs as a "slow to release, but stable releases" company, having a bunch of minor bugs when you release huge and important features tends to feel like it sucks a bit.
Time for the all-encompassing car analogy: it's like getting a brand new tesla with all the nice perks that come with that, only to find out that if you do cruise control at >60mph the speaker system will stop functioning.
Well "i see dummy proofing"
Its other word to SR :-)
Fingers crossed for you newkidd2. I have a separate instance as a trap receiver/forwarder and they have put the leaking trap receiver fix in there as well: Case #762541 - "Traps will not forward from NPM 11.5"
ecklerwr1, for what it's worth - I was running a NPM v10.7 with NTA v4.0.3 ok (except a minor issue with the FSDb where is doesn't purge correctly after x days but does a bit longer instead)
If you can ensure you have enough storage space on the FSDb then you should be fine [cosmetic defect if you call that for storage management only] and get the new NTA functionality.
The above is fixed under NTA 4.1 - but that requires NPM 11.0 - which also worked ok in my experience.In both situations your fine to leave your SAM v6.1
Doh!! Easter Sunday and thought I'd try my luck.
Shut down all services. ok
From the HF notes created a batch file to copy everything being updated. - ok
Start the installer - Fine
Clicks continue - Fails:
Scratches head - isn't that the whole point of applying the patch?
Please - can we revert out of these .exe HFs - or supply the included files separately.
I understand that it's continuous improvement and will become easy click, auto backup and install - however:
At present it looks like there is always issues and We have to manually backup our files anyway.
** Edit **
Used 7-Zip and extracted out the files.
There is another folder though with System.dll I don't see any reference to being replaced anywhere.
Otherwise the other 13 already backed up have been replaced.
Now monitoring for the trap forwarder to remain low memory usage...
On/off trap service that bug is "legacy" from the npm 11 ....
soon ...I just can't wait to kiwisyslog new release !!! offloading all my trap to kiwisyslog
https://thwack.solarwinds.com/community/solarwinds-community/product-blog/blog/2014/01/20/what-are-we-working-on-for-kiwi-syslog-after-94
I quite sure that your that if your npm trap service " could say thanks buddy"
IT will after that trap offload
squinsey wrote:
Please Solarwinds, and rob.hock, we need a batch file or installer for these hot fixes. Misplacing these files is causing a lot of additional issues for people. I spent 5 hours on a Webex with a tech trying to straighten out dll versions. We finally gave up, and I had to completely rebuild my main poller.
I know you want to want to get fixes out ASAP, but with inaccurate read.txt, and many duplicate dll's the process is to error prone.
I tried to apply NPM hotfixes #1 and #4 yesterday (per recommendations from SW tech support), but it did not go well at all. Read and weep...
So, I am back to square one -- with the same problems w/the alerts and w/o hotfixes. I added another note to the case, asking the developer for a true fix that does not require so much work. I cannot afford to have my main monitoring system down for hours and hours again, especially if the work is fruitless.
PS: I am getting flashbacks of the Nightmare of Elm Street movies. Just when you thought everything was OK, Freddy would resurface and start the nightmare all over again...
hi newkidd2
I hear the pain....not a good way to spend the holidays
Is there away to roll back in your case to the old release ?
I have a 24/7 ISP that run and much depends on Solarwinds software I won't like to be in that jem.
I hope support has now enough data to SR.
sja, I don't think I can roll back to 11.01. This new version made a lot of changes to the SQL database. So, reverting would also require restoring the SQL database that's almost 1 month old. That's not an easy thing to do, especially since I'd also have to restore the NTA database from 30 days ago. I think my only option at this time is to continue working w/the SW developers and hope for the best.
By the way, I already got word from the developers... They want to work w/me (in real time) on re-installing hot fix 4 once again -- this since they say suspect files were copied in the wrong directories. I doubt it very much, since I was very careful, especially since I run into this problem many times since v11.5. Anyway, I'll have to see what happens when I get to work w/the developers via Go To Meeting. I really hope that this nightmare is over soon, and that this experience is helpful to others in this forum.
Oh no! I was hoping it was just me. Perhaps my post earlier was still being moderated when you started things.
I ripped their directory locations into a batch file that I attached to the thread so I didn't get into trouble by misdirecting files.
Batch went through without error doing the file backups and patching/overrides, and HF4 has intern resolved my issue for the traps.
Just going through things now with support to clarify things so I can get an understanding/resolve this Core Setup mismatch Will update when I get something.
so question as I just got an email to install hotfix 4 to address some problems , so question is 1-3 rolled up in 4 or do I need to do these other ones as well ? and is this hotfix worth the effort
Hmm... copying files via a batch file...That's an interesting idea... Thanks, squinsey!!!
You know, what you're describing sounds a lot like what I asked the SW folks for them to incorporate onto their hotfixes. The current HF process very much prone to errors - especially when multiple servers also multiple directories are involved.
Anyway, I think I'll try that next time, instead of manually copying files. Of course, I will think thrice before upgrading... From now on, I'm going back to waiting a couple of months after new releases -- and learning from others' good and bad experiences. No more living in the bleeding edge.... Sorry, SW folks..., I'm just a bit tired of feeling like a guinea pig.
Now that I think of it..., Where the name guinea pig come from? Those cute little rodents look nothing like pigs!!!
Yes sir- HF4 is cumulative.
1-3 are indeed rolled up into HF4 as part of 13 files to replace (which rolled out fine for me after extracting them per above and deploying via batch file per readme notes so I didn't stuff up locations)As for are they worth it. Hmmmm depends on what your something trivial was Re: 11.5.1 on the way? Just not brave enough to that 11.5.0..
fitzy141,
From what I understand...,
I hope this helps.
Yer I do the batch way so I can do a test, then allow the T1 server guys to deploy patches etc overnight during the approved change window.
They then only need to give me a call if there is an bigger issue, as I've already gone through this kind of pain.
Keep us posted guys... my upgrade decisions are seriously based on your experience with this o.O! I really appreciate all of your comments and updates. I really appreciate the info about NPM v10.7 with NTA v4.0.3 squinsey!!! I may try 11.0 NPM with NTA 4.1 and leave SAM at 6.1. For now that sounds like possibly the safest bet until some of this other stuff gets sorted! It sounds like sticking at 11.0 might be ok.
I hope someone from solarwinds PM will come with some "officel"updates....
What's Up /Down with NPM 11.5 SAM 6.2
Are there any combination that are not playing well togther ?
Will sure help to clear up some rumour?
There are no systemic integration issues between modules at present. Apologies for the HF deployment issues- certainly that many manual steps isn't ideal, but our goal is to release urgent fixes as quickly as possible. In the future we're looking at a easier deployment option for Hotfixes, which should be ready shortly along with SR.
sja,
I noticed that SolarWinds posted NPM v11.5.1 on my Customer Portal, although I did not see any announcements about it in Thwack. I wonder why no announcement was posted in Thwack about it. Anyway, the URL for the Release Notes for NPM v11.5.1 is shown below:
SolarWinds Network Performance Monitor Release Notes
By the way, my SW instances are finally stable, after a lot of work and many meetings w/SW tech support. So, I am not planning to install this new version yet. I will wait a few weeks, to see others' experiences with this new release. What about you? Are you planning to go for the update or will you wait as well? Just curious...
are trying to say that I'm a chicken ?
So yes you're probably right...
I just push a new polling engine and NCM to my 11.1 setup.
I think ... we will "move up" when NCM will have the same alert engine.
Well, given what we've been through with v11.5.., I much rather be a than a .
Yep. Sorry to say, but so much broke with 11.5 that I'm not really willing to risk breaking more with 11.5.1. Someone else can guinea pig this one (h/t to newkidd2 lol)
mmmm do I need to change the thread title to "is 11.5.2 is on the way? I just not brave enough to 11.5.1"
I hoped that we can close that thread and move on.....
We upgraded from 11.0.1 to 11.5.1 with zero issues. Completely painless process. Thank you SolarWinds!
We have been holding off on upgrades waiting for 11.5.1. We got our major issue with MSMQ backing up resolved (not entirely sure it was related to the upgrade to 11.5) and now our installation is pretty stable. We need to install the UDT (v.3.2.2) upgrade as well to fix the many issues with v.3.2.
