Anonymous_User Absent Member.
Absent Member.
2350 views

Server stops responding with Heavy Network Load.

Hi,

I have a customer who has a G4 HP proliant DL380

These have integrated NIC using the the HP / Broadcom driver
Q57. Can't remember the version but it is the Latest avaliable from HP.

Now when I am a big eDir Partition or run a Local Repair on the
Database. The server stops responding to the Network for a few minutes.
No errors, CPU may hit 100% (not always) so I can do things on the
server at this point but it may take a while to do such as load edit etc.

Server then comes back, still no errors reported.

I have the NIC forced at 100FD I just read a update from Andre Taubman
say they should be AUTO. AUTO. Can anyone tell me why.. (will try this
Monday)

Should I try the Broadcom Drivers instead?

Now I don't know if it is a Network problem. The server IP stats seem
ok with out packet loss.

Any help would be great.

Thanks

Pete
Labels (2)
0 Likes
6 Replies
Anonymous_User Absent Member.
Absent Member.

Re: Server stops responding with Heavy Network Load.

Well, your message completely lacking version and configuration
information. As we cannot guess what your system looks like (except for
the server model), we first need more information to proceed.
Most of all, we need the following:

- the netware version you are using
- the exact support pack version (please don't say the "latest", but
give us the version number)
- the HP Smartstart or CSP version installed on your server (if any) or
the driver versions for specific HP drivers you may have installed
- any other NetWare patches you may have installed

You actually save giving us these individual parts by posting the
complete server configuration which you get by executing the command
(use the exact syntax provided):

load config /all

and then post the resulting config.txt file here.

> I have the NIC forced at 100FD I just read a update from Andre
> Taubman say they should be AUTO. AUTO. Can anyone tell me why..
> (will try this Monday)


With very rare exceptions, all devices have robust NWAYS automatic
speed, duplex and flow control negoctiation and by leaving both card
and switch on AUTO, you will get correct and non conflicting settings.
However by forcing the settigns, you actually disable negociation and
it is not uncommon that you get conflicting configuration settings
between the server and your switch regarding duplex or flow control
settings (speed is generally not an issue). These incompatible setings
do generally not prevent your server from working, but often result in
serious performance degration or unexpected network blackouts.

--
Marcel Cox (using XanaNews 1.17.5.9)
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Server stops responding with Heavy Network Load.

Hi Marcel,

I was having a complete daze, sorry re:- lack of information.

(I will run a config tomorrow, when I get to the office)

The server is a HP DL380 G4
4 GB of Ram
2 x 76GB 10xRPM Raid 1 using 6i Internal board.

I believe 7.31 SSD from HP, although on the website it is 7.30 as the
latest. (will Confirm tomorrow)

The Network drivers are the 7.63 Version.

I have just seen that there is a 8.13 Version released on the 18th
August. (I will install these and try tomorrow)

It is Netware 6.5 SP3 With Most of the Latest patches.
which include
run sp 3 version of eDir 8.7.3.5
Cnmgrsp3
wsock6g
syscalls3a.
NW65os3a
tcp659j
n65nss3a
nw65sp3ncp
xvsft2


Thanks for the info the Duplex settings.

I know that the Switch has been configured for 100FD, (tested with a Lan
guy and a Fluke..)
I alway read it is better to just ensure that both are set to FULL 100
FD. (But I am no expert, )

So could there be problems if you know both the server and the Switch
are set the same setting i.e Forced 100 Full Duplex?

thanks Pete



Marcel Cox wrote:
> Well, your message completely lacking version and configuration
> information. As we cannot guess what your system looks like (except for
> the server model), we first need more information to proceed.
> Most of all, we need the following:
>
> - the netware version you are using
> - the exact support pack version (please don't say the "latest", but
> give us the version number)
> - the HP Smartstart or CSP version installed on your server (if any) or
> the driver versions for specific HP drivers you may have installed
> - any other NetWare patches you may have installed
>
> You actually save giving us these individual parts by posting the
> complete server configuration which you get by executing the command
> (use the exact syntax provided):
>
> load config /all
>
> and then post the resulting config.txt file here.
>
>
>>I have the NIC forced at 100FD I just read a update from Andre
>>Taubman say they should be AUTO. AUTO. Can anyone tell me why..
>>(will try this Monday)

>
>
> With very rare exceptions, all devices have robust NWAYS automatic
> speed, duplex and flow control negoctiation and by leaving both card
> and switch on AUTO, you will get correct and non conflicting settings.
> However by forcing the settigns, you actually disable negociation and
> it is not uncommon that you get conflicting configuration settings
> between the server and your switch regarding duplex or flow control
> settings (speed is generally not an issue). These incompatible setings
> do generally not prevent your server from working, but often result in
> serious performance degration or unexpected network blackouts.
>

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Server stops responding with Heavy Network Load.

Peter Norris wrote:

> So could there be problems if you know both the server and the Switch
> are set the same setting i.e Forced 100 Full Duplex?


Beside speed and duplex, most modern switches and nics also support
flow control. Also, never 100% trust the manual settings, but verify
the *actual* settings used. For the network adapter on the server side,
you can generally see the active settings in the LAN statistics for the
NIC. If your switch is managed, you will generally see the actual
switch settings for a port through the management interface.

Independently of this, are you sure your problem is network related at
all? You seem to indicate that the problem occurs when you do certain
NDS operations on the server. To see if you really have a network
problem, run a continous ping from a workstation to the server ( ping
-t server_address) and then do the operation on the server that usually
triggers the problem. See if ping packets are getting lost.

--
Marcel Cox (using XanaNews 1.17.5.9)
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Server stops responding with Heavy Network Load.

Hi Marcel,

Thanks for the update,

I am not sure that it is Network related. The server does not drop a
ping during normal day to day work. I have been running lots of pings
mainly so I know if it stops responding..

I rebuilt the server with No patches other than SP 3 Overlay. I did not
apply the HP SSD and still had the problems.. (so then added the
patches to bring up to date, incase I need to raise a call with Novell. etc)

When I do something like DS repair or add a partition the server will be
fine and all of a suddenly it is not on the network.

This happens with 2 servers built the same way. I also used the Disks
from one of the servers in a third servers hardware and still had the
problems

However the third server (same hardware and build) is now built (all
three servers are dedicated DS servers). I put this server on a
seperate hub, plugged into the same switch port I had previously had the
problem on. I also had my laptop on this seperate hub. The Hub was old
and the server was dropping a lot of packets. However the same DS
operations did NOT cause the server to stop responding on the NETWORK to
other servers or to my laptop

I have not yet tested the server plug directly into the Network to see
if it still has the issues seen on the other two servers.



Marcel Cox wrote:
> Peter Norris wrote:
>
>
>>So could there be problems if you know both the server and the Switch
>>are set the same setting i.e Forced 100 Full Duplex?

>
>
> Beside speed and duplex, most modern switches and nics also support
> flow control. Also, never 100% trust the manual settings, but verify
> the *actual* settings used. For the network adapter on the server side,
> you can generally see the active settings in the LAN statistics for the
> NIC. If your switch is managed, you will generally see the actual
> switch settings for a port through the management interface.
>
> Independently of this, are you sure your problem is network related at
> all? You seem to indicate that the problem occurs when you do certain
> NDS operations on the server. To see if you really have a network
> problem, run a continous ping from a workstation to the server ( ping
> -t server_address) and then do the operation on the server that usually
> triggers the problem. See if ping packets are getting lost.
>

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Server stops responding with Heavy Network Load.

>I alway read it is better to just ensure that both are set to FULL 100
FD. (But I am no expert, )

Wherever you read that is wrong. As Marcel confirms, Auto (or 100HD) is
an industry setting, but there is no industry standard for 100FD and it
should never be used.


>So could there be problems if you know both the server and the Switch

are set the same setting i.e Forced 100 Full Duplex?

Yes, there could, that's what we are saying.
--
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: Server stops responding with Heavy Network Load.

Thanks form the update Andrew,

Now I updated to COmpaq Nic drivers 8.56. This for now seems to have
resolved the problem for now. (I shall monitor.) (I also installed
TEAMING.... Although did some testing on a single nic and did not see the
problem so far.

I will attach the config.txt when I get home.

I have asked the customer to implement AUTO / AUTO for the Nics (This site
has 40ish servers all hard coded 100FD)

Thanks

Peter



> >I alway read it is better to just ensure that both are set to FULL 100

> FD. (But I am no expert, )
>
> Wherever you read that is wrong. As Marcel confirms, Auto (or 100HD) is
> an industry setting, but there is no industry standard for 100FD and it
> should never be used.
>
>
> >So could there be problems if you know both the server and the Switch

> are set the same setting i.e Forced 100 Full Duplex?
>
> Yes, there could, that's what we are saying.
> --
> 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.