Hello [log in to unmask]

re: QCTerm And Disconnects

Can you send me a nmlg file of the disconnects... it would be
interesting to use this as an example/case-study of what the TCP
timers are doing.

On my machine I am using:

[1  ]     Retransmission Interval Lower Bound (Secs)
[180  ]   Maximum Time to Wait For Remote Response (Sec)
[4  ]     Initial Retransmission Interval (Secs)
[6  ]     Maximum Retransmissions per Packet

If I continued to see problems my next change would be:

[1  ]     Retransmission Interval Lower Bound (Secs)
[300  ]   Maximum Time to Wait For Remote Response (Sec)  *
[4  ]     Initial Retransmission Interval (Secs)
[7  ]     Maximum Retransmissions per Packet              *

At the same time I would be pursuing the problem with my "IT" staff
who supports the routers/modems/wan-links to determine why the packet
loss is so high.

The configuration of the nm-logging to look at this data should be:

           Class    Console Disk
Subsystem  Name     Logging Logging  Event


SUB0003    CLAS0001  [Y]     [Y]     Serious internal error
Network    CLAS0002  [Y]     [Y]     Internal error/operator attention
Transport  CLAS0003  [N]     [Y]     Non-critical errors
           CLAS0004  [Y]     [Y]     Nodal messages (start/stop)
           CLAS0005  [N]     [Y]     Informative messages
           CLAS0006  [N]     [Y]     Statistical information

If you need to make changes, follow it up with a ":switchnmlog update"
and then duplicate the problem and ":switchnmlog"

plz send the nmlg file in store-to-disk format.

Regards,

James Hofmeister
[log in to unmask]
Hewlett Packard
Worldwide Technology Network Expert Center
P.S. My Ideals are my own, not necessarily my employers.

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *