ProLiant Servers (ML,DL,SL)
1823726
Members
3312
Online
109664
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-20-2001 04:00 PM
тАО02-20-2001 04:00 PM
cpu hog
A PROLIANT ML 370 with netware 5.1 upgraded from a Proliant 1600 Netware 4.11 with the Novell Wizard is having problems after a few hours. First users can't login anymore, then the server utilization is up to 70 %. Trying to down the server is impossible. The only way is to power off/on the server to restart.
It is installed with le latest drivers (NSSD 6.10A) annd CIM agents (Smartstart 4.90).
CAn you help me please ?
It is installed with le latest drivers (NSSD 6.10A) annd CIM agents (Smartstart 4.90).
CAn you help me please ?
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-02-2001 04:00 PM
тАО04-02-2001 04:00 PM
Re: cpu hog
Are you sure the drivers are updated from the NSSD 6.10A ? Try re-runing the NSSD again .
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-01-2001 04:00 PM
тАО05-01-2001 04:00 PM
Re: cpu hog
We are having similar problems with work station lockup requiring us to bring down the server by turning it off, i.. can't unload volumes etc. Here are the spews.
Server = Proliant ML370, purchased 7/2000, running Novel 5.1 & SP2A
Problem = SP2A installed 4/12/01. Work station lock up started 4/23/1. Lock up has occurred 4 times, 3 of which were when IS kept installing work station software from the network. We've updated NC and SCSI drivers. Novell has a patch, os5pt2a.exe 3/2/1, that we are going to try. My biggest concern right now is that we can't bring the server down without turning off. We've tried fconsole and ctl alt esc and system comes down to a point, but then no further. Had no problems with this prior to install of service pack 2a.
Will check status of NSSD and CIM. Any suggestions/help appreciated. thanks
Server = Proliant ML370, purchased 7/2000, running Novel 5.1 & SP2A
Problem = SP2A installed 4/12/01. Work station lock up started 4/23/1. Lock up has occurred 4 times, 3 of which were when IS kept installing work station software from the network. We've updated NC and SCSI drivers. Novell has a patch, os5pt2a.exe 3/2/1, that we are going to try. My biggest concern right now is that we can't bring the server down without turning off. We've tried fconsole and ctl alt esc and system comes down to a point, but then no further. Had no problems with this prior to install of service pack 2a.
Will check status of NSSD and CIM. Any suggestions/help appreciated. thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-23-2001 04:00 PM
тАО07-23-2001 04:00 PM
Re: cpu hog
Hi,
The fix for this problem is as follows:
- at the server console enter "set client file caching enabled = off"
- also add this command to the autoexec.ncf
- Install the "wsock3a" patch that is available from Novell.
regards,
John
The fix for this problem is as follows:
- at the server console enter "set client file caching enabled = off"
- also add this command to the autoexec.ncf
- Install the "wsock3a" patch that is available from Novell.
regards,
John
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Learn About
News and Events
Support
© Copyright 2025 Hewlett Packard Enterprise Development LP