"Logger Screen - Interrupt assignment: 4"

OK, one of my branch servers running Netware 6.0 SP3 has a weird message on the Logger Screen.  When I Remote Console into it and check the Logger Screen, I find the text "Interrupt assignment: 4" repeatedly scrolling the whole screen.

I'm not even sure where to begin looking.

And, the reason why it's not on SP5 right now, was because after attempting to apply it, my DOS clients in that branch were unable to login.  I had no choice but to rollback.  But, this is a whole other issue in and of itself.

Anyway, back to the issue at hand.  An excerpt from the Health.log

<HR NOSHADE ALIGN=RIGHT>
Tuesday,  7-05-2005   2:04 pm
Disk Throughput on server FS2051A03 was in a BAD State
Current Value - 0
Peak Value - 7275
Max Value - N/A
<HR NOSHADE ALIGN=RIGHT>
Tuesday,  7-05-2005   2:04 pm
Disk Throughput on server FS2051A03 has returned to the GOOD State
Current Value - 4
Peak Value - 7275
Max Value - N/A
<HR NOSHADE ALIGN=RIGHT>
Tuesday,  7-05-2005   2:04 pm
Disk Throughput on server FS2051A03 was in a SUSPECT State
Current Value - 0
Peak Value - 7275
Max Value - N/A
<HR NOSHADE ALIGN=RIGHT>
Tuesday,  7-05-2005   2:04 pm
Disk Throughput on server FS2051A03 has returned to the GOOD State
Current Value - 6
Peak Value - 7275
Max Value - N/A
<HR NOSHADE ALIGN=RIGHT>
Tuesday,  7-05-2005   2:05 pm
Disk Throughput on server FS2051A03 was in a SUSPECT State
Current Value - 0
Peak Value - 7275
Max Value - N/A
<HR NOSHADE ALIGN=RIGHT>
Tuesday,  7-05-2005   2:05 pm
Disk Throughput on server FS2051A03 has returned to the GOOD State
Current Value - 3
Peak Value - 7275
Max Value - N/A
<HR NOSHADE ALIGN=RIGHT>
Tuesday,  7-05-2005   2:05 pm
Disk Throughput on server FS2051A03 was in a BAD State
Current Value - 0
Peak Value - 7275
Max Value - N/A
<HR NOSHADE ALIGN=RIGHT>
Tuesday,  7-05-2005   2:05 pm
Disk Throughput on server FS2051A03 has returned to the GOOD State
Current Value - 13
Peak Value - 7275
Max Value - N/A
<HR NOSHADE ALIGN=RIGHT>
Tuesday,  7-05-2005   2:06 pm
Disk Throughput on server FS2051A03 was in a BAD State
Current Value - 0
Peak Value - 7275
Max Value - N/A
<HR NOSHADE ALIGN=RIGHT>
Tuesday,  7-05-2005   2:06 pm
Disk Throughput on server FS2051A03 has returned to the GOOD State
Current Value - 3
Peak Value - 7275
Max Value - N/A
<HR NOSHADE ALIGN=RIGHT>
Tuesday,  7-05-2005   2:07 pm
CPU Utilization-0 on server FS2051A03 has returned to the GOOD State
Current Value - 100
Peak Value - 100
Max Value - 100
Current SUSPECT threshold = More than  85 and Critical threshold = More than  95
<HR NOSHADE ALIGN=RIGHT>
Tuesday,  7-05-2005   2:07 pm
CPU Utilization-0 on server FS2051A03 was in a SUSPECT State
Current Value - 100
Peak Value - 100
Max Value - 100
Current SUSPECT threshold = More than  85 and Critical threshold = More than  95
<HR NOSHADE ALIGN=RIGHT>
Tuesday,  7-05-2005   2:07 pm
CPU Utilization-0 on server FS2051A03 has returned to the GOOD State
Current Value - 100
Peak Value - 100
Max Value - 100
Current SUSPECT threshold = More than  85 and Critical threshold = More than  95
<HR NOSHADE ALIGN=RIGHT>
Tuesday,  7-05-2005   2:08 pm
CPU Utilization-0 on server FS2051A03 was in a SUSPECT State
Current Value - 100
Peak Value - 100
Max Value - 100
Current SUSPECT threshold = More than  85 and Critical threshold = More than  95
<HR NOSHADE ALIGN=RIGHT>
Tuesday,  7-05-2005   2:08 pm
CPU Utilization-0 on server FS2051A03 was in a BAD State
Current Value - 100
Peak Value - 100
Max Value - 100
Current SUSPECT threshold = More than  85 and Critical threshold = More than  95
<HR NOSHADE ALIGN=RIGHT>
Tuesday,  7-05-2005   2:09 pm
CPU Utilization-0 on server FS2051A03 has returned to the GOOD State
Current Value - 0
Peak Value - 100
Max Value - 100
Current SUSPECT threshold = More than  85 and Critical threshold = More than  95
<HR NOSHADE ALIGN=RIGHT>
Wednesday,  7-06-2005   8:45 am
Disk Throughput on server FS2051A03 was in a SUSPECT State
Current Value - 0
Peak Value - 7275
Max Value - N/A
<HR NOSHADE ALIGN=RIGHT>
Wednesday,  7-06-2005   8:45 am
Disk Throughput on server FS2051A03 has returned to the GOOD State
Current Value - 6
Peak Value - 7275
Max Value - N/A
<HR NOSHADE ALIGN=RIGHT>
Wednesday,  7-06-2005   8:46 am
CPU Utilization-0 on server FS2051A03 was in a SUSPECT State
Current Value - 13
Peak Value - 100
Max Value - 100
Current SUSPECT threshold = More than  85 and Critical threshold = More than  95
<HR NOSHADE ALIGN=RIGHT>
Wednesday,  7-06-2005   8:46 am
CPU Utilization-0 on server FS2051A03 has returned to the GOOD State
Current Value - 1
Peak Value - 100
Max Value - 100
Current SUSPECT threshold = More than  85 and Critical threshold = More than  95
<HR NOSHADE ALIGN=RIGHT>
Wednesday,  7-06-2005   8:50 am
CPU Utilization-0 on server FS2051A03 was in a SUSPECT State
Current Value - 41
Peak Value - 100
Max Value - 100
Current SUSPECT threshold = More than  85 and Critical threshold = More than  95
<HR NOSHADE ALIGN=RIGHT>
Wednesday,  7-06-2005   8:50 am
CPU Utilization-0 on server FS2051A03 has returned to the GOOD State
Current Value - 100
Peak Value - 100
Max Value - 100
Current SUSPECT threshold = More than  85 and Critical threshold = More than  95
<HR NOSHADE ALIGN=RIGHT>
Wednesday,  7-06-2005   8:50 am
CPU Utilization-0 on server FS2051A03 was in a SUSPECT State
Current Value - 55
Peak Value - 100
Max Value - 100
Current SUSPECT threshold = More than  85 and Critical threshold = More than  95
<HR NOSHADE ALIGN=RIGHT>
Wednesday,  7-06-2005   8:50 am
CPU Utilization-0 on server FS2051A03 has returned to the GOOD State
Current Value - 50
Peak Value - 100
Max Value - 100
Current SUSPECT threshold = More than  85 and Critical threshold = More than  95
<HR NOSHADE ALIGN=RIGHT>
Wednesday,  7-06-2005   8:55 am
CPU Utilization-0 on server FS2051A03 was in a SUSPECT State
Current Value - 93
Peak Value - 100
Max Value - 100
Current SUSPECT threshold = More than  85 and Critical threshold = More than  95
<HR NOSHADE ALIGN=RIGHT>
Wednesday,  7-06-2005   8:55 am
CPU Utilization-0 on server FS2051A03 has returned to the GOOD State
Current Value - 57
Peak Value - 100
Max Value - 100
Current SUSPECT threshold = More than  85 and Critical threshold = More than  95
<HR NOSHADE ALIGN=RIGHT>
Wednesday,  7-06-2005   8:58 am
CPU Utilization-0 on server FS2051A03 was in a SUSPECT State
Current Value - 90
Peak Value - 100
Max Value - 100
Current SUSPECT threshold = More than  85 and Critical threshold = More than  95
<HR NOSHADE ALIGN=RIGHT>
Wednesday,  7-06-2005   9:00 am
CPU Utilization-0 on server FS2051A03 has returned to the GOOD State
Current Value - 100
Peak Value - 100
Max Value - 100
Current SUSPECT threshold = More than  85 and Critical threshold = More than  95
<HR NOSHADE ALIGN=RIGHT>
Wednesday,  7-06-2005   9:00 am
CPU Utilization-0 on server FS2051A03 was in a SUSPECT State
Current Value - 84
Peak Value - 100
Max Value - 100
Current SUSPECT threshold = More than  85 and Critical threshold = More than  95
<HR NOSHADE ALIGN=RIGHT>
Wednesday,  7-06-2005   9:01 am
CPU Utilization-0 on server FS2051A03 has returned to the GOOD State
Current Value - 90
Peak Value - 100
Max Value - 100
Current SUSPECT threshold = More than  85 and Critical threshold = More than  95
<HR NOSHADE ALIGN=RIGHT>
Wednesday,  7-06-2005   9:01 am
CPU Utilization-0 on server FS2051A03 was in a SUSPECT State
Current Value - 86
Peak Value - 100
Max Value - 100
Current SUSPECT threshold = More than  85 and Critical threshold = More than  95
<HR NOSHADE ALIGN=RIGHT>
Wednesday,  7-06-2005   9:01 am
CPU Utilization-0 on server FS2051A03 has returned to the GOOD State
Current Value - 55
Peak Value - 100
Max Value - 100
Current SUSPECT threshold = More than  85 and Critical threshold = More than  95
<HR NOSHADE ALIGN=RIGHT>
Wednesday,  7-06-2005   9:02 am
CPU Utilization-0 on server FS2051A03 was in a SUSPECT State
Current Value - 91
Peak Value - 100
Max Value - 100
Current SUSPECT threshold = More than  85 and Critical threshold = More than  95
<HR NOSHADE ALIGN=RIGHT>
Wednesday,  7-06-2005   9:02 am
CPU Utilization-0 on server FS2051A03 has returned to the GOOD State
Current Value - 100
Peak Value - 100
Max Value - 100
Current SUSPECT threshold = More than  85 and Critical threshold = More than  95
<HR NOSHADE ALIGN=RIGHT>
Wednesday,  7-06-2005   9:02 am
CPU Utilization-0 on server FS2051A03 was in a SUSPECT State
Current Value - 85
Peak Value - 100
Max Value - 100
Current SUSPECT threshold = More than  85 and Critical threshold = More than  95
<HR NOSHADE ALIGN=RIGHT>
Wednesday,  7-06-2005   9:02 am
CPU Utilization-0 on server FS2051A03 has returned to the GOOD State
Current Value - 100
Peak Value - 100
Max Value - 100
Current SUSPECT threshold = More than  85 and Critical threshold = More than  95
<HR NOSHADE ALIGN=RIGHT>
Wednesday,  7-06-2005   9:02 am
CPU Utilization-0 on server FS2051A03 was in a SUSPECT State
Current Value - 53
Peak Value - 100
Max Value - 100
Current SUSPECT threshold = More than  85 and Critical threshold = More than  95
<HR NOSHADE ALIGN=RIGHT>
Wednesday,  7-06-2005   9:02 am
CPU Utilization-0 on server FS2051A03 has returned to the GOOD State
Current Value - 100
Peak Value - 100
Max Value - 100
Current SUSPECT threshold = More than  85 and Critical threshold = More than  95
<HR NOSHADE ALIGN=RIGHT>
Wednesday,  7-06-2005   9:02 am
CPU Utilization-0 on server FS2051A03 was in a SUSPECT State
Current Value - 77
Peak Value - 100
Max Value - 100
Current SUSPECT threshold = More than  85 and Critical threshold = More than  95
<HR NOSHADE ALIGN=RIGHT>
Wednesday,  7-06-2005   9:02 am
CPU Utilization-0 on server FS2051A03 has returned to the GOOD State
Current Value - 80
Peak Value - 100
Max Value - 100
Current SUSPECT threshold = More than  85 and Critical threshold = More than  95
<HR NOSHADE ALIGN=RIGHT>
Wednesday,  7-06-2005   9:03 am
CPU Utilization-0 on server FS2051A03 was in a SUSPECT State
Current Value - 84
Peak Value - 100
Max Value - 100
Current SUSPECT threshold = More than  85 and Critical threshold = More than  95
<HR NOSHADE ALIGN=RIGHT>
Wednesday,  7-06-2005   9:04 am
CPU Utilization-0 on server FS2051A03 has returned to the GOOD State
Current Value - 75
Peak Value - 100
Max Value - 100
Current SUSPECT threshold = More than  85 and Critical threshold = More than  95
<HR NOSHADE ALIGN=RIGHT>
Wednesday,  7-06-2005   9:06 am
CPU Utilization-0 on server FS2051A03 was in a SUSPECT State
Current Value - 100
Peak Value - 100
Max Value - 100
Current SUSPECT threshold = More than  85 and Critical threshold = More than  95
<HR NOSHADE ALIGN=RIGHT>
Wednesday,  7-06-2005   9:06 am
CPU Utilization-0 on server FS2051A03 was in a BAD State
Current Value - 100
Peak Value - 100
Max Value - 100
Current SUSPECT threshold = More than  85 and Critical threshold = More than  95
<HR NOSHADE ALIGN=RIGHT>
Wednesday,  7-06-2005   9:07 am
CPU Utilization-0 on server FS2051A03 was in a SUSPECT State
Current Value - 6
Peak Value - 100
Max Value - 100
Current SUSPECT threshold = More than  85 and Critical threshold = More than  95
<HR NOSHADE ALIGN=RIGHT>
Wednesday,  7-06-2005   9:07 am
CPU Utilization-0 on server FS2051A03 has returned to the GOOD State
Current Value - 100
Peak Value - 100
Max Value - 100
Current SUSPECT threshold = More than  85 and Critical threshold = More than  95
<HR NOSHADE ALIGN=RIGHT>
Wednesday,  7-06-2005   9:07 am
CPU Utilization-0 on server FS2051A03 was in a SUSPECT State
Current Value - 100
Peak Value - 100
Max Value - 100
Current SUSPECT threshold = More than  85 and Critical threshold = More than  95
<HR NOSHADE ALIGN=RIGHT>
Wednesday,  7-06-2005   9:07 am
Disk Throughput on server FS2051A03 was in a SUSPECT State
Current Value - 0
Peak Value - 7275
Max Value - N/A
<HR NOSHADE ALIGN=RIGHT>
Wednesday,  7-06-2005   9:07 am
CPU Utilization-0 on server FS2051A03 was in a BAD State
Current Value - 100
Peak Value - 100
Max Value - 100
Current SUSPECT threshold = More than  85 and Critical threshold = More than  95
<HR NOSHADE ALIGN=RIGHT>
Wednesday,  7-06-2005   9:07 am
Disk Throughput on server FS2051A03 has returned to the GOOD State
Current Value - 13
Peak Value - 7275
Max Value - N/A
<HR NOSHADE ALIGN=RIGHT>
Wednesday,  7-06-2005   9:08 am
Disk Throughput on server FS2051A03 was in a SUSPECT State
Current Value - 0
Peak Value - 7275
Max Value - N/A
<HR NOSHADE ALIGN=RIGHT>
Wednesday,  7-06-2005   9:08 am
Disk Throughput on server FS2051A03 has returned to the GOOD State
Current Value - 5
Peak Value - 7275
Max Value - N/A
<HR NOSHADE ALIGN=RIGHT>
Wednesday,  7-06-2005   9:09 am
Disk Throughput on server FS2051A03 was in a BAD State
Current Value - 0
Peak Value - 7275
Max Value - N/A
<HR NOSHADE ALIGN=RIGHT>
Wednesday,  7-06-2005   9:09 am
Disk Throughput on server FS2051A03 has returned to the GOOD State
Current Value - 4
Peak Value - 7275
Max Value - N/A
<HR NOSHADE ALIGN=RIGHT>
Wednesday,  7-06-2005   9:10 am
CPU Utilization-0 on server FS2051A03 has returned to the GOOD State
Current Value - 100
Peak Value - 100
Max Value - 100
Current SUSPECT threshold = More than  85 and Critical threshold = More than  95
<HR NOSHADE ALIGN=RIGHT>
Wednesday,  7-06-2005   9:10 am
CPU Utilization-0 on server FS2051A03 was in a SUSPECT State
Current Value - 100
Peak Value - 100
Max Value - 100
Current SUSPECT threshold = More than  85 and Critical threshold = More than  95
<HR NOSHADE ALIGN=RIGHT>
Wednesday,  7-06-2005   9:10 am
CPU Utilization-0 on server FS2051A03 was in a BAD State
Current Value - 100
Peak Value - 100
Max Value - 100
Current SUSPECT threshold = More than  85 and Critical threshold = More than  95
<HR NOSHADE ALIGN=RIGHT>
Wednesday,  7-06-2005   9:11 am
Disk Throughput on server FS2051A03 was in a BAD State
Current Value - 0
Peak Value - 7275
Max Value - N/A
<HR NOSHADE ALIGN=RIGHT>
Wednesday,  7-06-2005   9:11 am
Disk Throughput on server FS2051A03 has returned to the GOOD State
Current Value - 3
Peak Value - 7275
Max Value - N/A
<HR NOSHADE ALIGN=RIGHT>
Wednesday,  7-06-2005   9:13 am
Disk Throughput on server FS2051A03 was in a SUSPECT State
Current Value - 0
Peak Value - 7275
Max Value - N/A
<HR NOSHADE ALIGN=RIGHT>
Wednesday,  7-06-2005   9:13 am
Disk Throughput on server FS2051A03 has returned to the GOOD State
Current Value - 2
Peak Value - 7275
Max Value - N/A
<HR NOSHADE ALIGN=RIGHT>
Wednesday,  7-06-2005   9:13 am
Disk Throughput on server FS2051A03 was in a BAD State
Current Value - 0
Peak Value - 7275
Max Value - N/A
<HR NOSHADE ALIGN=RIGHT>
Wednesday,  7-06-2005   9:13 am
Disk Throughput on server FS2051A03 has returned to the GOOD State
Current Value - 6
Peak Value - 7275
Max Value - N/A
<HR NOSHADE ALIGN=RIGHT>
Wednesday,  7-06-2005   9:14 am
Disk Throughput on server FS2051A03 was in a BAD State
Current Value - 0
Peak Value - 7275
Max Value - N/A
<HR NOSHADE ALIGN=RIGHT>
Wednesday,  7-06-2005   9:14 am
CPU Utilization-0 on server FS2051A03 has returned to the GOOD State
Current Value - 100
Peak Value - 100
Max Value - 100
Current SUSPECT threshold = More than  85 and Critical threshold = More than  95
<HR NOSHADE ALIGN=RIGHT>
Wednesday,  7-06-2005   9:14 am
Disk Throughput on server FS2051A03 has returned to the GOOD State
Current Value - 9
Peak Value - 7275
Max Value - N/A
<HR NOSHADE ALIGN=RIGHT>
Wednesday,  7-06-2005   9:14 am
CPU Utilization-0 on server FS2051A03 was in a SUSPECT State
Current Value - 100
Peak Value - 100
Max Value - 100
Current SUSPECT threshold = More than  85 and Critical threshold = More than  95
<HR NOSHADE ALIGN=RIGHT>
Wednesday,  7-06-2005   9:15 am
CPU Utilization-0 on server FS2051A03 was in a BAD State
Current Value - 100
Peak Value - 100
Max Value - 100
Current SUSPECT threshold = More than  85 and Critical threshold = More than  95
<HR NOSHADE ALIGN=RIGHT>
Wednesday,  7-06-2005   9:15 am
Disk Throughput on server FS2051A03 was in a SUSPECT State
Current Value - 0
Peak Value - 7275
Max Value - N/A
<HR NOSHADE ALIGN=RIGHT>
Wednesday,  7-06-2005   9:15 am
Disk Throughput on server FS2051A03 has returned to the GOOD State
Current Value - 4
Peak Value - 7275
Max Value - N/A
<HR NOSHADE ALIGN=RIGHT>
Wednesday,  7-06-2005   9:16 am
Disk Throughput on server FS2051A03 was in a BAD State
Current Value - 0
Peak Value - 7275
Max Value - N/A
<HR NOSHADE ALIGN=RIGHT>
Wednesday,  7-06-2005   9:16 am
Disk Throughput on server FS2051A03 has returned to the GOOD State
Current Value - 6
Peak Value - 7275
Max Value - N/A
<HR NOSHADE ALIGN=RIGHT>
Wednesday,  7-06-2005   9:16 am
Disk Throughput on server FS2051A03 was in a SUSPECT State
Current Value - 0
Peak Value - 7275
Max Value - N/A
<HR NOSHADE ALIGN=RIGHT>
Wednesday,  7-06-2005   9:17 am
Disk Throughput on server FS2051A03 has returned to the GOOD State
Current Value - 4
Peak Value - 7275
Max Value - N/A
<HR NOSHADE ALIGN=RIGHT>
Wednesday,  7-06-2005   9:17 am
Disk Throughput on server FS2051A03 was in a BAD State
Current Value - 0
Peak Value - 7275
Max Value - N/A
<HR NOSHADE ALIGN=RIGHT>
Wednesday,  7-06-2005   9:17 am
Disk Throughput on server FS2051A03 has returned to the GOOD State
Current Value - 7
Peak Value - 7275
Max Value - N/A
<HR NOSHADE ALIGN=RIGHT>
Wednesday,  7-06-2005   9:17 am
Disk Throughput on server FS2051A03 was in a SUSPECT State
Current Value - 0
Peak Value - 7275
Max Value - N/A
<HR NOSHADE ALIGN=RIGHT>
Wednesday,  7-06-2005   9:17 am
Disk Throughput on server FS2051A03 has returned to the GOOD State
Current Value - 4
Peak Value - 7275
Max Value - N/A
<HR NOSHADE ALIGN=RIGHT>
Wednesday,  7-06-2005   9:21 am
CPU Utilization-0 on server FS2051A03 has returned to the GOOD State
Current Value - 100
Peak Value - 100
Max Value - 100
Current SUSPECT threshold = More than  85 and Critical threshold = More than  95
<HR NOSHADE ALIGN=RIGHT>
Wednesday,  7-06-2005   9:22 am
CPU Utilization-0 on server FS2051A03 was in a SUSPECT State
Current Value - 100
Peak Value - 100
Max Value - 100
Current SUSPECT threshold = More than  85 and Critical threshold = More than  95
<HR NOSHADE ALIGN=RIGHT>
Wednesday,  7-06-2005   9:22 am
CPU Utilization-0 on server FS2051A03 has returned to the GOOD State
Current Value - 78
Peak Value - 100
Max Value - 100
Current SUSPECT threshold = More than  85 and Critical threshold = More than  95
<HR NOSHADE ALIGN=RIGHT>
Wednesday,  7-06-2005   9:22 am
CPU Utilization-0 on server FS2051A03 was in a SUSPECT State
Current Value - 100
Peak Value - 100
Max Value - 100
Current SUSPECT threshold = More than  85 and Critical threshold = More than  95
<HR NOSHADE ALIGN=RIGHT>
Wednesday,  7-06-2005   9:22 am
CPU Utilization-0 on server FS2051A03 was in a BAD State
Current Value - 100
Peak Value - 100
Max Value - 100
Current SUSPECT threshold = More than  85 and Critical threshold = More than  95
<HR NOSHADE ALIGN=RIGHT>
Wednesday,  7-06-2005   9:23 am
CPU Utilization-0 on server FS2051A03 has returned to the GOOD State
Current Value - 0
Peak Value - 100
Max Value - 100
Current SUSPECT threshold = More than  85 and Critical threshold = More than  95
<HR NOSHADE ALIGN=RIGHT>
Wednesday,  7-06-2005   3:20 pm
LAN Traffic on server FS2051A03 was in a BAD State
Current Value - 0
Peak Value - 11921
Max Value - N/A
<HR NOSHADE ALIGN=RIGHT>
Wednesday,  7-06-2005   3:20 pm
LAN Traffic on server FS2051A03 has returned to the GOOD State
Current Value - 1
Peak Value - 11921
Max Value - N/A
<HR NOSHADE ALIGN=RIGHT>
Wednesday,  7-06-2005   3:20 pm
LAN Traffic on server FS2051A03 was in a BAD State
Current Value - 0
Peak Value - 11921
Max Value - N/A
<HR NOSHADE ALIGN=RIGHT>
Wednesday,  7-06-2005   3:20 pm
LAN Traffic on server FS2051A03 has returned to the GOOD State
Current Value - 1
Peak Value - 11921
Max Value - N/A
<HR NOSHADE ALIGN=RIGHT>
Wednesday,  7-06-2005   3:20 pm
LAN Traffic on server FS2051A03 was in a BAD State
Current Value - 0
Peak Value - 11921
Max Value - N/A
<HR NOSHADE ALIGN=RIGHT>
Wednesday,  7-06-2005   3:20 pm
LAN Traffic on server FS2051A03 has returned to the GOOD State
Current Value - 1
Peak Value - 11921
Max Value - N/A

The repetition of the LAN Traffic, Disk Throughput, etc. from Good to Bad throughout the day is weird.

CPU Utilization is still in single digit percentage values.

What other information can I provide?
LVL 3
djhathAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

PsiCopCommented:
Hmmmm...sounds like a hardware issue, possibly an IRQ conflict.

Verify that the the rollback of the SP didn't change any switches on drivers, especially in STARTUP.NCF.
ShineOnCommented:
Is this all day long, 24-7, or just during high LAN activity hoursm or what?

The IRQ thing... would interrupt assignment 4 have a direct correlation to IRQ4?  Wouldn't that be a COM port?  

Does the server have a SmartUPS attached with Powerchute software loaded?  I've seen funky things happen with AIOCOMx before...

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
djhathAuthor Commented:
PsiCop:

I still have other Netware servers as SP3, so I will compare STARTUP.NCF's of one of those with the server I rolled back.

ShineOn:

It's an all day long item. I had seen it before, but wasn't sure what to make of it, and ultimately got pulled in different directions before I tripped across it again.
CompTIA Security+

Learn the essential functions of CompTIA Security+, which establishes the core knowledge required of any cybersecurity role and leads professionals into intermediate-level cybersecurity jobs.

djhathAuthor Commented:
Forgot to answer ShineOn's question - all of our Netware servers have a SmartUPS with the Powerchute software.

Here is the STARUP.NCF file of the server that had SP5 installed on it, but later rolled back:

LOAD MPS14.PSM
LOAD IDECD.CDM
LOAD SCSIHD.CDM
LOAD DELLSEP.CDM
LOAD NWASPI.CDM
LOAD IDEATA.HAM PORT=170 INT=F
LOAD PEDGE3.HAM SLOT=1
LOAD ADPT160M.HAM SLOT=301
LOAD ADPT160M.HAM SLOT=302

Here is a server with Netware 6 SP3 that hasn't been touched.

LOAD MPS14.PSM
LOAD IDECD.CDM
LOAD SCSIHD.CDM
LOAD NWASPI.CDM
LOAD IDEATA.HAM PORT=170 INT=F
LOAD PEDGE3.HAM SLOT=1
LOAD LSIMPTNW.HAM SLOT=10010
elf_binCommented:
Dude, the interrupt is chocking your disk throughput!  Check what IRQ PCI slots 1, 301, 302 are using, move 'em about (well you can't move the motherboard based one).  Why don't you take off all the's not essential (like try it without the UPS), that'll isolate what's generating the interrupt.
Otherwise, if it was finer with SP5, I'd put the HDD drivers from SP5 on.

Good luck.
djhathAuthor Commented:
Haven't had a chance to pick this one back up until now...

The powerchute software is indicating that it can't communicate with the UPS.  

I unloaded the Powerchute NLM and it stopped.  

ShineOn shines again.

That solves the immediate problem.  Now, I need to get down to that branch to investigate further.
djhathAuthor Commented:
This was something stupidly simple.  The serial cable from the UPS to the server was plugged into COM2 instead of COM1.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Novell Netware

From novice to tech pro — start learning today.