quote:Originally posted by jp.senior@bell.caHello, I was wondering if anybody has had any issues upgrading from Orion version 7.Is this a transparent process? Will our settings be migrated? Is any data lost?I appreciate any responses,JP
quote:Originally posted by SJHawkinsGuysForgive me if I'm being foolish, but I've found no documentation anywhere regarding the upgrade procedure - you know in terms of install alongside/over the top, remove v7 first / what backups to take where etc?I can take reasonable guesses at this, but I'd prefer some guidelines to save me getting it wrong.CheersStuart Hawkins
This is a bit late of a reply, but I had no troubles doing this upgrade. This is information for anybody who may be searching older posts.
Upgraded 7.8.5 to 8.1 Last Friday and installed the Hotfixes to my primary poller. All went well. There were some issues. I have a Seperate SQL Server, a primary poller, and a secondary poller.The Min RQ's call for .net 2.0 or higher, so I installed .net 3.0. As it turned out with both 2.0 and 3.0 installed only 2.0 is used by ORION.
Following the upgrade, my Syslog service began bouncing, Support suggested a .net 2.0 repair and a re-run of the config wizard to reinstall the syslog service. This fixed the issue on my primary poller. A few hours later my secondary poller began doing a similar thing. I performed the same steps and in the end, I continue to have the same problem.
I had to go and change older nodes back to SNMPv1, evidently after the upgrade the default version used is v2c. Not a major issue.
One problem I am experiencing at the moment and wait on this Monday morning for Support to contact me, I was previously recieving Syslog events from PIX and Cisco FWSM devices. I am no longer seeing these events in Syslog viewer. I ran wireshark and have confirmed that the syslog event are making it to this syslog server.
As for my Trap reciever, I am recieving this in the event log
Do not know why this is occuring, but will touch base with Support.
I haven't had time to check into this, however one of my user's has noticed that the Web refresh rate seems to take longer. (not the frequency, the refresh time)
I do not have Cirrus, but would like to add a config Icon to my node details screen, can anyone assist me? Would be nice to have the current config and startup config, as well as a means to write the config to a TFTP Server.
I also would like to a ssh icon to the node details screen.
Anyone know how to add the ChassisID? I have configured the device and the custom MIB poller, however I can't get the macro to get the info.Perhaps some a step-by-step would help.
Has anyone found a solution to getting the IP Address Mgt working yet? I have created a url shortcut to my Toolkit Web site from the IP Address Management tool. Suely someone has better intregated this that could lend assistance. Do not know when that SW Rep "asd "will have the time to complete this project. One would think that with all the interest in this that they could make it a higher priority!!
Been working with Support for a few days and have what is thought to be a solution to my issue.
1. No problems with Orion itself, but with Syslog.
2. Syslog service bouncing with Windows events 1003,1004,1104,1103,1102, and SW Log 1018, 1002,1003, and 0
3. Removed .net 3.0 and 2.0, reinstalled .net 2.0, re-applied hotfixes to primary poller. still had issue. Removed "reg Expression" entries in syslog rulesets. no more events in primary poller event logs, syslog service stopped bouncing. Reinstalled syslog service via config wizard
Reporting queued error: faulting application SyslogService.exe, version 8.1.2715.19414, faulting module kernel32.dll, version 5.2.3790.4062, fault address 0x0000bee7.
5. Applied hotfix #4, wait to see if syslog service continues to bounce. Looks good thus far
It appears that the use of reg expressions in the DNShostname and/or Message tabs in syslog is broken in this version.