David
I have a Support Call open, in regards to Media errors, and the Symantec
Engineer said the following.....
Simon,
Tcp tuning parameters changes the wait time for a port which is in a
TIME_WAIT state. A port will stay in this state for 4 minutes by default.
Decreasing this time allows the port to be closed sooner rather than later
allowing the port to be re-opened or stay as listening if need be. I noticed
VMD (the volume manager daemon process) in TIME_WAIT state. If NetBackup VMD
is timing out when trying to write to the next media or when trying to write
header information, this could possibly cause problems.
NOTE: For more information see Microsoft article # Q120642 at the following
URL:
TCP/IP and NBT Configuration Parameters for Windows 2000 or Windows NT
http://support.microsoft.com/default.aspx?scid=kb;en-us;120642
I think this is the same link Steve sent, but does any of this help answer
your Q - For the record, I have NOT implemented this yet, as I have made one
major change and want to review this before applying any other fix straight
away (otherwise applying multiple fixes at the same time, means I have no
trackable method of knowing what fixed the root problem).
Regards
Simon Weaver
3rd Line Technical Support
Windows Domain Administrator
EADS Astrium Limited, B23AA IM (DCS)
Anchorage Road, Portsmouth, PO3 5PU
Email: Simon.Weaver at Astrium-eads.net
-----Original Message-----
From: Clooney, David [mailto:david.clooney at bankofamerica.com]
Sent: 30 October 2006 10:44
To: veritas-bu at mailman.eng.auburn.edu
Subject: [Veritas-bu] CLOSE_WAIT
Hi All
Scenario :
Master server Solaris 8
Media server windows 2000
Over the past weekend we encountered a whole bunch of 219's on jobs using a
particular media server, a netstat on the media server provided the below
snapshot. The CLOSE_WAIT entries seemed to hang around for ages,
additionally hogging sockets. On the master server everything was plodding
along as usual.
Q1. can anyone explain why these sockets on the media server do not close
fully and hang around for quite sometime ? If indeed the master server has
not
finalised comms, what (on the master) would be keeping the socket open
between the two.
Q2. Does anyone know the default setting for the maximum number of
simultaneous tcp connections on windows 2000?
Q3. If I was to add the registry key to tcp parameters "TcpNumConnections" ,
what guidelines could I follow to determine the number of connections ?
Q4. Not so long ago on the same windows media server I added the registry
key to tcp parameters "TcpTimedWaitDelay" in order to clear TIME_WAIT more
quickly. Are there any known issues with windows 2000 and tcp
connections that I'm not aware off ?
Much appreciated
David Clooney
TCP media_server:bpcd media_server:795 ESTABLISHED
TCP media_server:bpcd media_server:834 ESTABLISHED
TCP media_server:bpcd media_server:868 CLOSE_WAIT
TCP media_server:bpcd media_server:991 CLOSE_WAIT
TCP media_server:bpcd master_server:551 CLOSE_WAIT
TCP media_server:bpcd master_server:562 CLOSE_WAIT
TCP media_server:bpcd master_server:591 CLOSE_WAIT
TCP media_server:bpcd master_server:610 CLOSE_WAIT
TCP media_server:bpcd master_server:645 CLOSE_WAIT
TCP media_server:bpcd master_server:696 CLOSE_WAIT
TCP media_server:bpcd master_server:768 CLOSE_WAIT
TCP media_server:bpcd master_server:807 CLOSE_WAIT
TCP media_server:bpcd master_server:829 CLOSE_WAIT
TCP media_server:bpcd master_server:830 CLOSE_WAIT
TCP media_server:bpcd master_server:867 CLOSE_WAIT
TCP media_server:bpcd master_server:904 CLOSE_WAIT
TCP media_server:bpcd master_server:919 ESTABLISHED
TCP media_server:bpcd master_server:976 ESTABLISHED
TCP media_server:bpcd master_server:982 CLOSE_WAIT
TCP media_server:bpcd master_server:1008 ESTABLISHED
TCP media_server:bpcd master_server:1023 ESTABLISHED
Notice to recipient:
The information in this internet e-mail and any attachments is confidential
and may be privileged. It is intended solely for the addressee. If you are
not the intended addressee please notify the sender immediately by
telephone. If you are not the intended recipient, any disclosure, copying,
distribution or any action taken or omitted to be taken in reliance on it,
is prohibited and may be unlawful.
When addressed to external clients any opinions or advice contained in this
internet e-mail are subject to the terms and conditions expressed in any
applicable governing terms of business or client engagement letter issued by
the pertinent Bank of America group entity.
If this email originates from the U.K. please note that Bank of America,
N.A., London Branch and Banc of America Securities Limited are authorised
and regulated by the Financial Services Authority.
_______________________________________________
Veritas-bu maillist - Veritas-bu at mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
This email (including any attachments) may contain confidential and/or
privileged information or information otherwise protected from disclosure. If
you are not the intended recipient, please notify the sender immediately, do
not copy this message or any attachments and do not use it for any purpose or
disclose its content to any person, but delete this message and any attachments
from your system. Astrium disclaims any and all liability if this email
transmission was virus corrupted, altered or falsified.
---------------------------------------------------------------------
Astrium Limited, Registered in England and Wales No. 2449259
Registered Office: Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England
|