We've only released one update to v9, and that is SP1. It is included with the update bundled next to the main v9 installer.
Bryan, probably a little late for your upgrade - however we didn't have any issues with our alerts or maps. As long as you have a database backup, and copy of the Maps/Reports folder I think you will be OK.
I shutdown all the pollers and upgraded the primary SLX server first - then did the pollers. Just had the normal issue of the install starting all the services - and having to shut them down again so I could upgrade the pollers (I wish there was an install option to leave the services down).
We made the choice a long time ago to run the database in simple mode (i.e. no transaction logs). We found this took the pressure off the database server - but obviously has a recovery trade-off (i.e. we can only recover to the last backup if required).
Dave.
Thanks Dave....I did what you suggested. Here are some thoughts :
Support items
Glad to hear your upgrade went OK.
I don't think you waited long enough for the Universal Device Poller to load - ours takes anywhere from 13-15 minutes with 15K elements - which is a very similar size to yourself (and 174meg of memory once loaded) - development is working on this for the next service pack.
Node details do take longer than 8.5.1 - not quite sure why, but it's not something I have reported as I don't have any hard numbers (and I didn't see anyone else making a similar comment).
I opened a ticket for the UnDP issue and loading of the node details. I launched UnDP on one of my pollers and after an hour it still isn't loaded. Loading of node details takes between 70-80 seconds on my system. Everything else (like interfaces, etc) load in 1-2 seconds.
Node management on the web site is nice to have although I find it pretty slow to work with. It could just be my system so I'll have to have support gotomeeting and see what's going on.BB
70 or 80 seconds - wow, we aren't in the same ballpark. When I said ours were slower, I estimate that typically the node details screen took 2-3 seconds under 8.5.1, and 5-6 seconds under 9.0 (but I can't back the old numbers up with hard data). Any of the other screens (i.e. interfaces) seem to be unchanged in performance terms from the previous release.
For the UnDP poller loading, does the process show memory growth during this hour? Process memory growth may actually show that it's still loading and not stalled or hung.
I'm be interested to see the result of both issues.
On another v9 observation...
The way MapMaker now expands the list of devices (once a vendor is selected) is very annoying. For a large list of Cisco devices it can take several minutes for the list to populate. I can see that for some users this may make the inital load faster - but it's bad news for the larger installations.
The web loading seem excessive slow with even the login page.
Has it got to do with the UDP issue that will be fixed in SP2?
savell:70 or 80 seconds - wow, we aren't in the same ballpark. When I said ours were slower, I estimate that typically the node details screen took 2-3 seconds under 8.5.1, and 5-6 seconds under 9.0 (but I can't back the old numbers up with hard data). Any of the other screens (i.e. interfaces) seem to be unchanged in performance terms from the previous release. For the UnDP poller loading, does the process show memory growth during this hour? Process memory growth may actually show that it's still loading and not stalled or hung. I'm be interested to see the result of both issues. On another v9 observation... The way MapMaker now expands the list of devices (once a vendor is selected) is very annoying. For a large list of Cisco devices it can take several minutes for the list to populate. I can see that for some users this may make the inital load faster - but it's bad news for the larger installations. Dave.
Web Site - only node details seems to be affected. Interfaces, etc load up in 1-3 seconds. We did find a large amount of "white" space in the DB leftover from a previous running of NetFlow. The DB was up to 140GB with only 7GB actually used. We ran a shrink and got it down to 37GB.
UnDP - Yes I do see the memory usage grow as it's loading but still takes a very long time to load.
MapMaker - I think this was changed in V8.5...I hate it too. BB
I think we have identified the issue...fixing it I'm not sure. It seems that after I removed the custom mib gauges/charts for node details the node details paged loads in like 3-5 seconds. I'm not sure of the conflict from custom mib poller to UnDP but something isn't right. I sent support the files so hopefully something can turn up. UnDP does load in about 2 minutes now which seems to be faster than before.
BB
I upgraded my SL2000 server last week.The upgrade took 30 minutes and went without a hitch.The website has been running fine since the upgrade.
The issue I have is the links to the charts no longer work in report scheduler.I am e-mailing out charts of connected VPN users, but the new asp.net URL format no longer allows me to retrieve the chart with Report Scheduler and mail it out weekly:
Previous to the upgrade the URL looked like this:http://orion-sl2000/NetPerfMon/ViewChart.asp?Chart=CustomOIDChart&NetObject=N:2515&CustomPollerID={FBB9360E-A013-4EEF-8A9A-5EFB690BC559}&SubsetColor=FF0000&RYSubsetColor=0&Period=Last%207%20Days&SampleSize=15M&Title=VPN+users+%2D+last+7+days&ReBuild=TRUE&FontSize=Medium&Width=640&Height=0
The URL now looks like this:http://orion-sl2000/Orion/Controls/ChartImagePipe.aspx?ChartID=customChart$ctl01$chart_Base&KxRx=0x09556but no chart is displayed.
This is a show-stopper for my SLX upgrade. If I can't e-mail charts, there is no way I can upgrade to V9.
This will be fixed in the next service pack. There will be a new URL for charts that (like the old one) supplies all of the parameters needed to generate the chart instead of using ChartImagePipe.aspx and relying on the asp.net session.
I have no seen this issue any where else, so I think I'm just doing something wrong. We got a new server for Orion so I decided to just install the new version 9. The install went fairly smoothly. The only issue I'm really seeing now is that I had a number of reports that I created and had published to the website. None of these reports show up any longer. (Yes, I moved them from the old server! :)) If I open report writer on the server all of the reports (canned and custom) are there. If I open a custom report that doesn't show up on the web site everything looks as it should. The box is checked that says to publish to the web. I've stopped and started resources on the server and I've even rebooted the server and I cannot get the reports to show up on the web.
What am I doing wrong?
spandey: I've stopped and started resources on the server and I've even rebooted the server and I cannot get the reports to show up on the web. What am I doing wrong?
I've stopped and started resources on the server and I've even rebooted the server and I cannot get the reports to show up on the web.
Have you tried to manually copy the file:C:\Program Files\SolarWinds\Orion\OrionReportWriter.Schema to the webserver?
I had not tried to manually copy the schema so I did try it and still nothing. None of the custom reports are publishing to the web. If I recreate the report they do publish but that's going to become pretty tedious.
spandy, have you tried this? http://thwack.com/forums/p/2048/7307.aspx#7307
jtimes: spandy, have you tried this? http://thwack.com/forums/p/2048/7307.aspx#7307
John - Yes. I've done that as well. As you said in your post, it's become almost second nature since you have to do it every upgrade. I've never had this happen before though. I've also noticed that my alerting is no longer working. I thought it was just a real quiet weekend. Whoops.
I've also noticed that my alerting is no longer working.
Okay, ignore that comment. I figured out alerting. The problem was between the chair and the keyboard.
problems with V9 Upgrade... initially had issues with the DB permissions, etc - this was sorted by reading this thread and removing the registry entries under SOFTWARE\SolarWinds.Net\ConfigurationWizard\ConfiguredModules\
This allowed the ConfigurationWizard to get past the DB config but we then this an issue when trying to install the Universal Device Poller it comes back with a message advising:
An error occured configuring SolarWinds Universal Device Poller: Unable to determine Job Engine Location. Please check the ConfigurationWizard.log file for details.
After repairing, running SP1, repairing, etc, etc - decided to install and configure without the Universal Device Poller - this at least allowed me to finish the upgrade, etc and get Orion back up and running.
Support case# 53629 and have been in discussions with Support regarding this issue - will post update as and when...
Sarah,
It could be that the solarwinds_website user lacks permission to see the report files you copied. To check this, open the file properties in Explorer and look at the security tab. Compare the settings for a file that does show up on the website with the settings for one that doesn't.
tdanner: Sarah, It could be that the solarwinds_website user lacks permission to see the report files you copied. To check this, open the file properties in Explorer and look at the security tab. Compare the settings for a file that does show up on the website with the settings for one that doesn't.
Tim - I've been in contact with SW support. I've checked permissions for the solarwinds_website user as well as the iusr_(machine name) user. I have also re-run the website configuration wizard to recreate the COM+ object. I've cleared website cache and restarted IIS on the webserver. I'm working to schedule a GoTo meeting for hopefully tomorrow. I'll post what I find out. It looks like I'm having some issues with alerting as well. Thanks!! :)