Performance

[Fuad_1]

Users were experiencing performance in connections although when I check the heath in the server (CPU, Memory) it was looking fine to me.

[Michael Tully]

First you may wish to look at the NIC card performance, like is it running as full or half duplex. It should be full duplex.
e.g. assuming lan card 0
# lanadmin -x 0
Have a look at the lost and collision packets in the interactive screens.
# lanadmin

Is there high disk IO ? glance is a good place to have it, or use something like 'sar -d 5 5'

[Fuad_1]

LanCard is performing at full duplex, io is normal. When a user/developer telnet to the server, it takes a while and it gives the login screen, or some time it gives time out.

[Steven E. Protter]

Here is a performance data collection script. If it not networking, these scripts will help.

Also, make sure your switch settings are correct. Autonegotiate for 1000 BT explicit for slower cards.

SEP

[Michael Tully]

I get the impression that the problem seems to be connection related and not really performance related. You should probably check how the connection is made, i.e. DNS for the server lookup from the workstation, are they on different subnets, routing etc.

[Fuad_1]

Now, users can connect to the server through front end application or directly, but they disconnected after some time.

[Norman_21]

Fuad,

What is in your /var/adm/syslog/syslog.log file.
Is there any changes in the /etc/resolv.conf

DO this :

#insf -d /dev/telm
#insf -d /dev/tels

This will re-install the device driver for the telent. Also, it might be a telnet patch problem.
Check to see if you have the following patch:
PHNE_26096

Good luck.

[Fuad_1]

I can not see any clue in syslog file, also resolv.conf is not exit in this serve, or other servers. I don't think is telnet problem, as it's new server with HPUX11.11i, and other servers are new with same spec's.

[Norman_21]

Check to see if you have duplicate IP address in the network!
I just guessed that the /etc/resolv.conf could delay the login prompt if it's not configured properly but since it's not there then the Server doesn't need it. It's only for DNS resolution.

[Mohanasundaram_2]

Hai
check ur /etc/nsswitch.conf file how it is resolv the hosts.if it resolving through DNS servers first,check ur DNS server is working properly,or check ur /etc/hosts.

Mohan

[Fuad_1]

Hi,

No DNS is used for resolving. Below is the contents of /etc/nsswitch.conf

hosts: files
aliases: files

[Sanjay_6]

Hi,

This could be related the reverse lookup problem that is faced by users telnetting to the system. If you are facing the same problem if you telnet from your workstation, then put your ip address with some xyz hostname in the /etc/hosts file and then telnet to the system. If your connection is faster this time, then this points in the direction of reverse ip lookup problem.

http://www1.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000064209194

Hope this helps.

Regds

[Norman_21]

Fuad,

How about if you copy new configuration files from the following:

#mv /etc/nsswitch.conf /tmp
#cp /ust/newconfig/etc/nsswitch.files /etc/nsswitch.conf

I wonder why you have /etc/nsswitch file
I don't think the /etc/hosts needs it!

Just a thought!

[Fuad_1]

Thanks all. The problem was with the link used between the storage box and the DR one.