The first thing to check is whether or not your system is being bombarded
by lack of heartbeat signals from your dtc's.

Type:


:linkcontrol @;status=all
Linkname: DTSLINK   Linktype: IEEE8023  Linkstate: CONNECTED
Physical Path:              56/56
Current Station Address:    08-00-09-98-18-D3
Default Station Address:    08-00-09-98-18-D3
Current Receive Filter:     broad(1) any(0) k_pckts(1) x_pckts(0)
Current Multicast Addresses:
  09-00-09-00-00-01  09-00-09-00-00-02  09-00-09-00-00-03
  09-00-09-00-00-04
Transmits no error         2472  Receives no error         7375
Transmit byte count      332989  Receive byte count      951822
Transmits error               0  Receives error               0
Transmits deferred            1  Carrier losses               0
Transmits 1 retry             0  CRC errors                   0
Transmits >1 retry            0  Frame losses                 0
Trans 16 collisions           0  Whole byte errors            0
Trans late collision          0  Size range errors            0
802 chip restarts             0  Receives dropped             0
Heartbeat losses              0  Receives broadcast        6605
                                  Receives multicast           0

You should see Heartbeat losses of 0 or very close to 0.

If that's not the problem, perhaps one or more of your nmconfig parameters
needs tuning via nmmgr.

You should also realize that by moving away from your earlier HARDWARE
telnet solution - to a software-based telnet or VTMGR, you are incurring
CPU overhead that you did NOT incur while utilizing the DTC72 TAC.




At 08:54 PM 2002-01-14, Harpreet Singh Chana wrote:
>Hi all,
>
>Six months ago I have added my 9000/968RX DTC/72 + enabled the TCP/IP.
>Previously it was running with DTC/72 with telnet. Still some of the users
>are using Telnet and some one TCP/IP. There was no performance issue with
>telnet. Right now I have more than 200 users with the TCP/IP and system
>performance is dam slow. During the Glance I am not getting any abnormal
>results. Like CPU/MEM/DISK high usage's.
>
>Can some one help me how I can check my N/W collisions, What should the
>minimum ping response time from the system, or TCP/IP really making the N/W
>connectivity very Slow. Customer is on Ver 5.5 with pp7.
>
>Where I can check the error log files of N/W ? or any other suggestions..
>
>With Warm Regards
>
>Harpreet Singh Chana
>TCS/1C
>Ph. (O)+ 968 - 671215
>Mobile  + 968 - 9473245
>Mina Al Fahal
>OMAN
>
>* To join/leave the list, search archives, change list settings, *
>* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

---------------------------------------------------------------------------
Gilles Schipper
GSA Inc.
HP System Administration Specialists
300 John Street, Box 87651   Thornhill, ON Canada L3T 7R4
Voice: 905.889.3000     Fax: 905.889.3001
Internet:  [log in to unmask]
---------------------------------------------------------------------------

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