IBM recommended *AUTO to us when we called them about bumping up to a gig
connection on the 6509 we put in. It worked with no trouble.
"Jones, John
\(US\)"
<John.Jones@xxxxx To
l.com> "Midrange Systems Technical
Sent by: Discussion"
midrange-l-bounce <midrange-l@xxxxxxxxxxxx>
s+chadb=wheeling- cc
nisshin.com@midra
nge.com Subject
RE: Intermittent network failure
04/03/2007 12:38
PM
Please respond to
Midrange Systems
Technical
Discussion
<midrange-l@midra
nge.com>
With Cisco gear our network guys have always recommended we
hard-configure the lines.
Since you're running Gb .. Are you using Jumbo frames (>1496)? Maybe
eliminate them if you are.
Otherwise I'd suggest running a communications trace or putting a
sniffer on the network.
--
John A. Jones, CISSP
Americas Information Security Officer
Jones Lang LaSalle, Inc.
V: +1-630-455-2787 F: +1-312-601-1782
john.jones@xxxxxxxxxx
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[
mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Haase, Justin C.
Sent: Tuesday, April 03, 2007 11:30 AM
To: Midrange Systems Technical Discussion
Subject: RE: Intermittent network failure
*AUTO/*AUTO on all gig. You must've missed my posts in the archive. ;)
Justin C. Haase
Solution Manager - Technical Services
Kingland Systems Corporation
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[
mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Roger Vicker, CCP
Sent: Tuesday, April 03, 2007 11:26 AM
To: Midrange Systems Technical Discussion
Subject: Re: Intermittent network failure
Jerry,
Interesting... Every other post I have from the archive says that both
ends should be hard configured because the negotiations don't go
smoothly.
I understand the power savings warning, but in this case where it can
and does hit several PCs at the same time if they are actually working
at the wrong point in time I doubt if it is related.
Thanks.
Roger
On 4/3/2007 9:57 AM, Jerry Draper wrote:
We had a similar problem except that it wasn't CA dropping it was the
i5
itself. We were configured at 100MB on the 400 and *auto on the
switch.
IBM had us apply a series of microcode ptf's to the ethernet adapter.
They recommended to put the i5 at *auto and the switch at *auto.
No problems since.
Jerry
PS: Beware that power saving options can cause emulation drops so I
leave "turn off disks" and "standby" at never.
J
Roger Vicker, CCP wrote:
Before I spend $2000 for new switches (probably Netgear's Prosafe
Smart
Switch series) has anyone got any diagnostic hints on this problem.
Model 800 at V5R3 with a Gigabit card (configured as 1G *FULL) to a
SMC
6624M stacked switch's Gigabit port (configured as Auto-1000, the
only
Gigabit option). XP Pro PCs running Client Access Express (CAE)
connected to the stack's 10/100 ports. New Cat5e patch cable tested
with
a medium-range network cable tester and installed for the Gigabit
connection.
Every day at least once, any CAE session that is actively talking at
the
wrong instant (not just sitting on a screen but sending/receiving)
will
fail. The system doesn't log anything to Qsysopr and in fact thinks
the
session is still valid. The CAE session seems to freeze for about
5-10
seconds then goes black and thinks it is disconnected. If you tell
the
CAE session to connect it gives an error that the device name is in
use.
The only solution is to wait until the TCP timeout expires (5
minutes)
or to use another session to DSCJOB the interactive job attached to
the
session.
The switch's event log shows nothing. The port counters show zero for
any of the bad things like drops and errors.
It can hit multiple PCs at the same time if they are at an active
send/receive function.
The time of day that it happens is not really predictable. Although
it
seems to cluster. Might hit for 5 minutes in the morning and not
again
till quiting time. It seems to only effect emulation (only protocol
that
is heavily used, no streaming audio/video...) but is not limited to
IBM
CAE as I am using Rumba and I get hit too. The one difference with
Rumba
(which does all communications through a single Engine) is that other
sessions on the PC will usually go in to *DSC status automatically.
Just
the unlucky session that was talking at the wrong moment is left
fully
active on the system. The Rumba Engine reports a communications error
and shuts down. Once the falsely active session is cleared all the
Rumba
sessions and Engine connect like normal.
Thanks.
Roger Vicker, CCP
--
*** Vicker Programming and Service *** Have bits will byte ***
www.vicker.com *** You can love humans if you don't know them too well.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at
http://archive.midrange.com/midrange-l.
CONFIDENTIALITY NOTICE: This e-mail communication, including
attachments, is covered by the Electronic Communications Privacy Act, 18
U.S.C. 2510-2521, is confidential, and may be legally privileged. If
you are not the intended recipient or believe you received this
communication in error, please reply to the sender indicating that fact
and delete the copy you received. In addition, retention,
dissemination, distribution, copying, or otherwise use of the
information contained in this communication is strictly prohibited.
Thank you.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
http://archive.midrange.com/midrange-l.
This email is for the use of the intended recipient(s) only. If you have
received this email in error, please notify the sender immediately and then
delete it. If you are not the intended recipient, you must not keep, use,
disclose, copy or distribute this email without the author's prior
permission. We have taken precautions to minimize the risk of transmitting
software viruses, but we advise you to carry out your own virus checks on
any attachment to this message. We cannot accept liability for any loss or
damage caused by software viruses. The information contained in this
communication may be confidential and may be subject to the attorney-client
privilege. If you are the intended recipient and you do not wish to receive
similar electronic messages from us in the future then please respond to
the sender to this effect.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
http://archive.midrange.com/midrange-l.
_____________________________________________________________________________
Scanned by IBM Email Security Management Services powered by MessageLabs.
For more information please visit
http://www.ers.ibm.com
_____________________________________________________________________________
ForwardSourceID:NT00068F52
midrange.com
