Server Utilization and response time issues

We have recently migrated 2 servers from Netware4.11 SP9 to new IBM 345's running Netware 5.1 SP6.  We have IP and IPX configured.  The issue is that the server utilization freezes in 40% area with one processor at 100% and the other low if not zero.  All 3rd party software, NAV, Tivoli, etc. were pulled and no change.  We have moved back to the 4.11 servers.  Any ideas?
DanUditisAsked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
PsiCopConnect With a Mentor Commented:
Ugh. Well, I wouldn't have moved the servers back to NetWare v4.11. I hope you didn't muck up NDS - for that matter, HOW did you move back to v4.11? Just bring up the old boxes and shut down the new ones? If you did that, then no worries about NDS.

We're running NetWare v6.x on IBM 345s, and had NetWare v5.1 SP5 on them before that. No problems like this. I suspect that NetWare v5.1's install auto-detected the wrong multi-CPU architecture. Post the contents of C:\NWSERVER\STARTUP.NCF on here, if you would. You need to be using PSM14 for those babies.
0
 
DanUditisAuthor Commented:
PsiCop, thanks.  we did just power up the other severs, no NDS issues.  Here's the startup.ncf data:

load acpidrv.psm
load idecd.cdm
load scsihd.cdm
load ideata.ham slot=10005
load ipsraid.ham slot =2
0
 
PsiCopCommented:
Yeah, replace ACPIDRV.PSM with MPS14.PSM.
0
Learn to develop an Android App

Want to increase your earning potential in 2018? Pad your resume with app building experience. Learn how with this hands-on course.

 
PsiCopCommented:
We've had problems with ACPIDRV.PSM in IBM machines.
0
 
PsiCopCommented:
FYI, NetWare v5.1's days a supported version are numbered. I dunno if there will be another SP for it, but if there is, you can expect it to be the last one. I wouldn't be surprised is NetWare v5.1 is EOLed or near EOL in the next 12 months. Novell is putting all their efforts into NetWare v6.5 and v7 (aka Open Enterprise Server).
0
 
DanUditisAuthor Commented:
Here's Novell's response:
Novell believes the root cause to this problem is that the settings:

Enable File Compression
Client File Caching Enabled

were set to ON, when they should have been set to OFF (Novell TID  http://support.novell.com/cgi-bin/search/searchtid.cgi?/10086113.htm <---High Util and NW51SP6).

We actually backed off to SP5 and the issue did not reoccur.  We also have test SP6 servers that we could not recreate the issue when we changed the settings as Novell recommended.  We were able to recreate it when the settings were 'ON'.  

As a follow up, an incident was opened up with Veritas. There are 2 options that Veritas recommended in resolving the High CPU Utilization issue.  
 
The first option, that is highly recommended, would be to upgrade to MP7 or FP7 depending on what version of Netback is being run.  This has the latest Open File Manager (OFM) driver available, which is version 9.2.
 
The second option is to replace the current OFM drivers with version 9.101.
 
There is a known issue with the old driver version of OFM [Version 90.01] causing high CPU utilization.  This was addressed in the 9.101 version and later.
0
 
PsiCopCommented:
Cool. Thanks for posting that.

If the Answer you Accepted is not the right answer, and you found the right solution on your own, you can always ask a Moderator to refund your points.
0
All Courses

From novice to tech pro — start learning today.