cancel
Showing results for 
Search instead for 
Did you mean: 
Create Post

Experiences with 8.1 running on 64-bit OS

I'm considering moving my ORION instance from a 32-bit and leveraging the 8.1 ability to run on 64-bit OS.  Does anyone have any experience with this to date?  I know its early in the release, but any feedback would be greatly appreciated.

Tags (1)
0 Kudos
18 Replies
Level 9

While we're discussing 64 bit- BUMP for any updates on the x64 bit version of the Orion Event Log forwarder..

0 Kudos

It's something we're considering for the future, but it's not imminent. 

0 Kudos

 We've had Orion 8.1 running on x64 2003 for a few weeks without any major issues.

 A couple of days ago the syslog service chewed through about 2GB of ram and really slowed the box down.

Process had to be killed rather than restarted but we've not seen any problems since.

 We're using an external SQL server so it's just Orion on the box.

 We have had problems running the toolset on the box though as the launcher just crashes on startup.



 

0 Kudos

 We have had problems running the toolset on the box though as the launcher just crashes on startup.



Thanks for the feedback. Also, I don't believe the Toolset is yet supported on x64. 😞

0 Kudos

To bring this back-


We have a few servers in production running 2003 x64 Enterprise with SQL 2005 x64 Enterprise...one in particular is loaded with 16GB of RAM. Now, I don't know enough about memory allocation and SQL server etc as I would like but still, something doesn't seem right here.


 We had a "process" that would lock users at the same time every day...upon doing some research, it was found to be caused by something with the x64. Once it was disabled, the users did not get locked up...BUT now the memory being reported by Orion is all weird. It is showing only 180MB of memory being used by SQL Server and only 400MB being in use total. Now I don't know enough about memory allocation and SQL Server etc- but still, as soon as we made the change, something went weird. It's almost like SQL is not reporting memory usage...


I don't remember exactly what the change was, but I will try to find it.

0 Kudos

What we changed was to allow locked pages into memory- as seen here:


http://support.microsoft.com/default.aspx?scid=kb;EN-US;918483


After doing so, the reported memory on this server changed dramatically. Just FYI-

0 Kudos

Thanks Jrutski. Are you looking at Windows Task Manager? I've seen issues in the past where Task Manager doesn't accurately represent memory usage for SQL instances, particularly if you have the instance configured to use more than 2GB of RAM.

0 Kudos
Level 13

I'm curious about this as well.
0 Kudos

BUMP...


There seems to be a number of folks on the forum who are now running v8.1. Has anyone yet tried v8.1 with the 64-bit version of Win 2003? If so, would you please share your experiences?


Thanks. 🙂

0 Kudos

I installed 8.1 today on 2003 x64 dual core sun x4100. The install went pretty smooth, with the exception of the SQL.   I needed to install the 64 bit application.  I am currently monitoring 93 nodes and 849 interfaces.  No issues at this point, and it seems to be running fast, at least faster than the old crappy dell server.

 

Also, I installed Cirrus and the engineers tool set with no issues so far too.

0 Kudos

I installed 8.1 today on 2003 x64 dual core sun x4100. The install went pretty smooth, with the exception of the SQL.   I needed to install the 64 bit application.  I am currently monitoring 93 nodes and 849 interfaces.  No issues at this point, and it seems to be running fast, at least faster than the old crappy dell server.



Thanks for the feedback. With regard to your statement about SQL, I assume this is due to the fact that you are running your DB on the same server..? I imagine it wouldn't matter if your DB was housed on a different server..?

0 Kudos

 Yes, I am running the database on the same box until our new SQL server is ready.

 One other thing, I noticed today that almost all of my nodes were taking packet loss.  I looked at all the obvious stuff, then determined that it must be something with the Orion server.  I rebooted, once it was back up, I couldn't login to the System Manager, I kept getting an error "cannot connect to database"  I was able to see the database from Database manager and SQL Management Studio.  I re-ran the Config wizard, and all seems ok again. I'm not sure what caused this.  I guess this is even more reason to move the SQL database to my new server.

 
 

0 Kudos

Thanks for the feedback. 🙂

0 Kudos

UPDATE:

 I think I found the cause of the packet loss I had the other day.  I fired up Cirrus on the same server as the Orion (x64) and I saw the packet loss once again.  As far as I can tell, the cirrus application is not supported on x64.  I uninstalled cirrus, since unistalling I have had a ton of problems. 

 
1. I wasn't able to connect to the local sql database.

2. Once I re-ran the config manager, I could not launch map maker, (out-of-memory error)

3. SNMP Trap service will not fire up, I get a Microsoft error 2:

 

I am in the process of re-installing Orion.
 

0 Kudos

SolarWinds,


Any thoughts on this?

0 Kudos

 Many issues here-

What permissions do you have for the DB?  Is this the new remote SQL you set-up?

Cirrus is not supported on a 64bit OS so it's good that you removed it-

http://www.solarwinds.net/support/Cirrus/docs/ReleaseNotes/releaseNotes.htm

Not sure about the Map Maker not opening- my guess would be a missing .dll- What is the exact error message?

The Orion reinstall may help- you might want to attempt an Add/Remove - > Repair  as well.

0 Kudos

I too am about to upgrade my Orion server to a 64bit OS & a separate 64bit MS SQL2005 DB server.

I will also be running a new - second polling engine (actually my old Orion server minus the DB & Webserver), but this is a 32bit server.
Will this be compatible, or will I need to upgrade my second polling engine to 64bit as well?

0 Kudos

NG,

 It should work fine.

0 Kudos