Anonymous_User Absent Member.
Absent Member.
2805 views

High Utlization

Fresh NW65SP4a + n65nss4b, BM38SP4

Compaq Proliant ML370, dual P3 733MHz, 2048MB memory

All configured as per Craig Johnson's installation sequence notes for NW65.
Utilization hangs about 99% and 100% on 'Novell BorderManager FastCache
Current Activity' screen, under monitor.nlm reports as 50%.
Labels (2)
0 Likes
35 Replies
Anonymous_User Absent Member.
Absent Member.

Re: High Utlization

garbage,

> Fresh NW65SP4a + n65nss4b, BM38SP4
>
> Compaq Proliant ML370, dual P3 733MHz, 2048MB memory
>
> All configured as per Craig Johnson's installation sequence notes for NW65.
> Utilization hangs about 99% and 100% on 'Novell BorderManager FastCache
> Current Activity' screen, under monitor.nlm reports as 50%.


In monitor goto Kernel -> Busiest threads. What threads are at top ?

Also goto https://server ip:8009 , Profile/Debug, profile utilization by
NLM - what NLMs are at the top ?


--
Hamish Speirs
Novell Support Forums Volunteer Sysop.

http://haitch.net

(Please, no email unless requested. Unsolicited support emails will
probably be ignored)
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: High Utlization

> In monitor goto Kernel -> Busiest threads. What threads are at top ?

httpexpThread28 740,242
httpexpThread29 739,411
httpexpThread31 737,853
httpexpThread30 724,477
httpexpThread7 724,150
Server 29 70,060
Server 00:17 69,436
OS Allocated Bus Interrupt 5,044

> Also goto https://server ip:8009 , Profile/Debug, profile utilization by
> NLM - what NLMs are at the top ?


Processor 1: IDLE Thread BFA22240 Ready to run / running SERVER.NLM 49.4 %
httpexpThread29 8BCBA380 Wait for interrupt HTTPSTK.NLM 9.9 %

> garbage,
>
> > Fresh NW65SP4a + n65nss4b, BM38SP4
> >
> > Compaq Proliant ML370, dual P3 733MHz, 2048MB memory
> >
> > All configured as per Craig Johnson's installation sequence notes for NW65.
> > Utilization hangs about 99% and 100% on 'Novell BorderManager FastCache
> > Current Activity' screen, under monitor.nlm reports as 50%.

>
> In monitor goto Kernel -> Busiest threads. What threads are at top ?
>
> Also goto https://server ip:8009 , Profile/Debug, profile utilization by
> NLM - what NLMs are at the top ?
>
>
> --
> Hamish Speirs
> Novell Support Forums Volunteer Sysop.
>
> http://haitch.net
>
> (Please, no email unless requested. Unsolicited support emails will
> probably be ignored)


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: High Utlization

These figures cannot have been taken when the CPU was at 100%, they show
it as nearly 50% idle. Let us know what it says when the problem is
occurring.
--
Andrew C Taubman
Novell Support Forums Volunteer SysOp
http://support.novell.com/forums
(Sorry, support is not provided via e-mail)

Opinions expressed above are not
necessarily those of Novell Inc.
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: High Utlization

Andrew, as I said, Utilization hangs about 99% and 100% on 'Novell
BorderManager FastCache Current Activity' screen, under monitor.nlm reports
as 50%. Is this cosmetic?

> These figures cannot have been taken when the CPU was at 100%, they show
> it as nearly 50% idle. Let us know what it says when the problem is
> occurring.
> --
> Andrew C Taubman
> Novell Support Forums Volunteer SysOp
> http://support.novell.com/forums
> (Sorry, support is not provided via e-mail)
>
> Opinions expressed above are not
> necessarily those of Novell Inc.


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: High Utlization

That is normal if you have 2 CPUs and one is 100% and the other 0%,
monitor averages them.

What you show here looks like only one CPU's worth, can you give us the
whole screen?
--
Andrew C Taubman
Novell Support Forums Volunteer SysOp
http://support.novell.com/forums
(Sorry, support is not provided via e-mail)

Opinions expressed above are not
necessarily those of Novell Inc.
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: High Utlization

Processor 1: IDLE Thread BFA22240 Ready to run / running SERVER.NLM 48.8 %
httpexpThread30 8BD65300 Yielded CPU HTTPSTK.NLM 38.5 %
Health Monitor Slow 8A9F13E0 Delayed PORTAL.NLM 11.0 %
Server 00:18 8AC8E180 Waiting for work SERVER.NLM 0.6 %
Server 01:26 8571C400 Waiting for work SERVER.NLM 0.6 %

> That is normal if you have 2 CPUs and one is 100% and the other 0%,
> monitor averages them.
>
> What you show here looks like only one CPU's worth, can you give us the
> whole screen?
> --
> Andrew C Taubman
> Novell Support Forums Volunteer SysOp
> http://support.novell.com/forums
> (Sorry, support is not provided via e-mail)
>
> Opinions expressed above are not
> necessarily those of Novell Inc.


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: High Utlization

Again, I only see figures here for one CPU, and it shows as 50% idle. I
thonk you are looking at the NRM screen "Profile/Debug info". What
Hamish was asking is for you to go to that screen, _then_ click on the
link "Profile CPU execution by NLM". That will tell you what thread is
using which CPU when it hits 100%.
--
Andrew C Taubman
Novell Support Forums Volunteer SysOp
http://support.novell.com/forums
(Sorry, support is not provided via e-mail)

Opinions expressed above are not
necessarily those of Novell Inc.
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: High Utlization

SERVER.NLM NetWare Server Operating System 42.6 % 14.4 % 85.6 %
DS.NLM Novell eDirectory Version 8.7.3.7 SMP 32.4 % 100.0 % 0.0 %
LSL.NLM Novell NetWare Link Support Layer 10.6 % 0.0 % 100.0 %
LIBNSS.NLM Generic Library used by NSS (Build 197 MP) 4.5 % 100.0 % 0.0 %
COMN.NSS NSS Common Support Layer (COMN) (Build 2915 MP) 2.9 % 100.0 %
0.0 %
PORTAL.NLM CPR - Novell Remote Manager NLM 1.4 % 100.0 % 0.0 %
NSS.NLM NSS (Novell Storage Services) (Build 1027 MP) 1.0 % 100.0 % 0.0 %
MSM.NLM Novell Multi-Processor Media Support Module 0.8 % 0.0 % 100.0 %
LOADER.NLM NetWare OS Loader 0.2 % 100.0 % 0.0 %
CPQARRAY.HAM HP Disk Array Controller Host Adapter Module 0.2 % 100.0
% 0.0 %
CONNMGR.NLM NetWare Connection Manager NLM 0.2 % 100.0 % 0.0 %
LFS.NLM NetWare Logical File System NLM 0.2 % 100.0 % 0.0 %
NWSA.NSS NSS NetWare Semantic Agent (NWSA) (Build 1363 MP) 0.2 % 100.0
% 0.0 %
DSLOADER.NLM Novell eDirectory Version 8.7.3 Loader SMP 0.2 % 100.0 % 0.0 %
NETLIB.NLM Novell TCPIP NETLIB Module 0.2 % 100.0 % 0.0 %
TCP.NLM Novell TCP/IP Stack - Transport module (NULL encryption) 0.2 %
0.0 % 100.0 %
MONDATA.NLM NetWare 5.x/6.x Monitor MIB 0.2 % 100.0 % 0.0 %

> Again, I only see figures here for one CPU, and it shows as 50% idle. I
> thonk you are looking at the NRM screen "Profile/Debug info". What
> Hamish was asking is for you to go to that screen, _then_ click on the
> link "Profile CPU execution by NLM". That will tell you what thread is
> using which CPU when it hits 100%.
> --
> Andrew C Taubman
> Novell Support Forums Volunteer SysOp
> http://support.novell.com/forums
> (Sorry, support is not provided via e-mail)
>
> Opinions expressed above are not
> necessarily those of Novell Inc.


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: High Utlization

OK, now next time the high util happens, click on the % figure in the
top thread, where 42.6% is on your list. That will break down the
threads within server.nlm that are contributing most to the util.

The 32.4% for DS seems high too, is that always like that? If so there
may be an underlying DS problem, like continuous syncing going on.
--
Andrew C Taubman
Novell Support Forums Volunteer SysOp
http://support.novell.com/forums
(Sorry, support is not provided via e-mail)

Opinions expressed above are not
necessarily those of Novell Inc.
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: High Utlization

> OK, now next time the high util happens, click on the % figure in the
> top thread, where 42.6% is on your list. That will break down the
> threads within server.nlm that are contributing most to the util.


Count Address Nearest Symbol Execution Time
080 0021ACB0 SERVER.NLM|SchedProcessorIdleLoop 16.3 %
055 BF8BC530 LSL.NLM|LSLPollProcedure 11.2 %
027 0035E5D0 SERVER.NLM|DirectCallPollProcedures 5.5 %
023 00208FA8 SERVER.NLM|CallRegisteredPollingRoutines 4.7 %
020 0021A680 SERVER.NLM|_SchedGetReadyThread 4.1 %
010 0022592C SERVER.NLM|MpkSystemWork 2.0 %
009 F5359938 USERLIB.NLM|Disable 1.8 %
006 00208EC4 SERVER.NLM|kResumePoll 1.2 %
004 00013DCA LOADER.NLM|ASMPOPFD 0.8 %
004 00225890 SERVER.NLM|InitProcessorSystemWork 0.8 %
003 BF8C01A0 LSL.NLM|LSLSMPSendProcedure 0.6 %
001 0010B000 LOADER.NLM|kSpinLockDisable 0.2 %
001 833E2B40 MSM.NLM|MSMAESProcedure 0.2 %

>
> The 32.4% for DS seems high too, is that always like that? If so there
> may be an underlying DS problem, like continuous syncing going on.
> --
> Andrew C Taubman
> Novell Support Forums Volunteer SysOp
> http://support.novell.com/forums
> (Sorry, support is not provided via e-mail)
>
> Opinions expressed above are not
> necessarily those of Novell Inc.


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: High Utlization

That shows 16% of the 42% is idle time, so again the server or CPU
cannot be at 100% util. Was this done while the problem was occcurring?

Did you check into DS sync, as I asked? Is it always using ~30% of CPU?
--
Andrew C Taubman
Novell Support Forums Volunteer SysOp
http://support.novell.com/forums
(Sorry, support is not provided via e-mail)

Opinions expressed above are not
necessarily those of Novell Inc.
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: High Utlization

> OK, now next time the high util happens, click on the % figure in the
> top thread, where 42.6% is on your list. That will break down the
> threads within server.nlm that are contributing most to the util.


Count Address Nearest Symbol Execution Time
083 0021ACB0 SERVER.NLM|SchedProcessorIdleLoop 16.8 %
023 00360423 SERVER.NLM|LStrCmp 4.7 %
021 00208FA8 SERVER.NLM|CallRegisteredPollingRoutines 4.3 %
021 0035E5D0 SERVER.NLM|DirectCallPollProcedures 4.3 %
017 002A2BB8 SERVER.NLM|UnImportPublicSymbol 3.4 %
012 002A2340 SERVER.NLM|ImportPublicSymbol 2.4 %
011 0021A680 SERVER.NLM|_SchedGetReadyThread 2.2 %
008 00208EC4 SERVER.NLM|kResumePoll 1.6 %
008 0022592C SERVER.NLM|MpkSystemWork 1.6 %
002 00225890 SERVER.NLM|InitProcessorSystemWork 0.4 %
002 0026A254 SERVER.NLM|TryCollapsingCacheBlockControl 0.4 %
002 002D8E08 SERVER.NLM|OutputToString 0.4 %
001 00207908 SERVER.NLM|kMutexUnlock 0.2 %
001 00214A78 SERVER.NLM|GetNextFastQueElement 0.2 %
001 00216A18 SERVER.NLM|kRWReadLock 0.2 %
001 00298F2C SERVER.NLM|FindPublicRecord 0.2 %
001 002D846C SERVER.NLM|sprintfWithPointer 0.2 %
001 0032B680 SERVER.NLM|TrackTcoLocksInitial 0.2 %
001 0035FBA0 SERVER.NLM|CMoveFast 0.2 %
001 00360403 SERVER.NLM|CStrCmp 0.2 %


> The 32.4% for DS seems high too, is that always like that? If so there
> may be an underlying DS problem, like continuous syncing going on.
> --
> Andrew C Taubman
> Novell Support Forums Volunteer SysOp
> http://support.novell.com/forums
> (Sorry, support is not provided via e-mail)
>
> Opinions expressed above are not
> necessarily those of Novell Inc.


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: High Utlization

> That shows 16% of the 42% is idle time, so again the server or CPU
> cannot be at 100% util. Was this done while the problem was occcurring?


Under the 'BorderManager FastCache Current Activity' screen, the server
sits at 100%, sometimes, it will go down to 99%, hence this is why
monitor.nlm reports 50%.

Execution Profile Data by NLM
NLM Name NLM Description Execution Time Processor 0 Processor 1
SERVER.NLM NetWare Server Operating System 49.6 % 36.1 % 63.9 %
LIBNSS.NLM Generic Library used by NSS (Build 197 MP) 15.2 % 100.0 % 0.0 %
LSL.NLM Novell NetWare Link Support Layer 14.4 % 0.0 % 100.0 %
COMN.NSS NSS Common Support Layer (COMN) (Build 2915 MP) 7.9 % 100.0 %
0.0 %
PORTAL.NLM CPR - Novell Remote Manager NLM 3.3 % 93.8 % 6.3 %
NSS.NLM NSS (Novell Storage Services) (Build 1027 MP) 3.0 % 100.0 % 0.0 %
MSM.NLM Novell Multi-Processor Media Support Module 1.4 % 0.0 % 100.0 %
NWSA.NSS NSS NetWare Semantic Agent (NWSA) (Build 1363 MP) 1.0 % 100.0
% 0.0 %
CONNMGR.NLM NetWare Connection Manager NLM 0.4 % 100.0 % 0.0 %
ACLCHECK.NLM Novell ACL Check NLM PXY071 0.4 % 100.0 % 0.0 %
LOADER.NLM NetWare OS Loader 0.2 % 100.0 % 0.0 %
LFS.NLM NetWare Logical File System NLM 0.2 % 100.0 % 0.0 %
MANAGE.NSS NSS Management Functions (Build 687 MP) 0.2 % 100.0 % 0.0 %
TCP.NLM Novell TCP/IP Stack - Transport module (NULL encryption) 0.2 %
100.0 % 0.0 %
PROXY.NLM Novell Internet Proxy Server NLM PXY071 0.2 % 100.0 % 0.0 %

>
> Did you check into DS sync, as I asked? Is it always using ~30% of CPU?


How is this done?

> --
> Andrew C Taubman
> Novell Support Forums Volunteer SysOp
> http://support.novell.com/forums
> (Sorry, support is not provided via e-mail)
>
> Opinions expressed above are not
> necessarily those of Novell Inc.


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: High Utlization

Well, I have no idea what that BM screen is reporting then. It does not
seem to truly reflect overall server usage, maybe you need to ask about
it in the BM forum.

Please load dsrepair on the Master of Root and run a Report Sync Status,
and a Timesync check, from the first menu. Post that part of
dsrepair.log here.

You can also turn on dstrace on this server:

set dstrace=1
set dstrace=+s
set dstrace=+in

and look at the dstrace screen, if you see the same objects syncing over
and over, or errors in red,, there might be a problem. You can capture
this info to a file with:

set ttf=on

let the trace run for a while, then do

set ttf=off

and the output will be in sys:system/dstrace.old
--
Andrew C Taubman
Novell Support Forums Volunteer SysOp
http://support.novell.com/forums
(Sorry, support is not provided via e-mail)

Opinions expressed above are not
necessarily those of Novell Inc.
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.