OFA: Trap Error

[tobyheywood]

Hi folks,

Got a strange for you today!

Hardware/Software - IBM eSeries xServer 342 (1Gb RAM, 18GB - Sys, 100GB - Vol1 with Ultrium LTO Drive) running NetWare 5.1 SP5.

Now my problem is this, ArcServe 7 loads without issue but when I try to load the Backup Agent for Open Files it comes up with the following error messages;

OFA: Trap Error 05/02, d0e63228=cc d2 d9 d0 8b 0c 91 ff a1 fc
OFA: Trap Error 05/00, d0e99308=68 23 32 e6 d0 e9 1e ce 26 2b
OFA: Trap Error 02/05
OFA: LOAD OFA /D to create diagnostic file
OFA: Backup Agent for Open Files did not load.

Has anyone experience this or similar problems when trying to run BAOF? Can anyone suggest anything I can try?

One last question (and this is a very big guess), would the trap error messages be cause by SNMP?

Thank you in advance for your time and help.

Regards Toby Heywood

 

[ARCserveGuru]

Hi there Toby,
You may want to consider an unload reload of the OFA, a reboot, or as a last resort a reinstall of the OFA but for this you must make sure all OFA related stuff is off of the server.

this occurs usually (after a period of working fine) when a new netware sp is installed but the exact cause I do not know of. All I know is the work around.

g

 

[tobyheywood]

Hi ARCserveGuru,

I've managed to track the cause down. It would appear that OFA does not like NSS Volumes (although I have in the past managed to get it working, I couldn't tell you how thought!).

I backed up the vol1 when all users were logged off, and then began the task of removing the NSS volume and reinstateing a Traditional volume instead.

This does appear to work allthough I'm not to happy that NSS is not supported in ArcServe 7.

Anyway, thank you for you prompt reply!

Whilst I was researching this issue I also found some interesting notes on how SMP can cause trap errors in arcserve and ofa (admittedly it did relate to earlier versions, but interesting nonetheless)

Regards Toby Heywood

 

[ArcserveFreek]

Hi,
You can subscribe to E-News of Arcserve and shortly there should be a patch to fix this problem.
As you suspected, Novell's sp5 is the cause for this problem.

Thanks
ArcserveFreek