- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- make_net_recovery slow
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-24-2006 07:28 AM
01-24-2006 07:28 AM
make_net_recovery slow
NFS server uni-rx4640-03 not responding still trying
NFS server uni-rx4640-03 not responding still trying
NFS server uni-rx4640-03 ok
--- being displayed. A ping between the 2 servers looks good ---
ping uni-rx2620-01
PING uni-rx2620-01.unilab.digex.com: 64 byte packets
64 bytes from 10.209.83.229: icmp_seq=0. time=0. ms
64 bytes from 10.209.83.229: icmp_seq=1. time=0. ms
64 bytes from 10.209.83.229: icmp_seq=2. time=0. ms
----uni-rx2620-01.unilab.digex.com PING Statistics----
3 packets transmitted, 3 packets received, 0% packet loss
round-trip (ms) min/avg/max = 0/0/0
.
Any idea why so slow and why the NFS messages?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-24-2006 07:54 AM
01-24-2006 07:54 AM
Re: make_net_recovery slow
You can try to re-export the NFS filesystem one more time
exportfs -a
You can check if this would help.
Rgds
HGN
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-24-2006 08:06 AM
01-24-2006 08:06 AM
Re: make_net_recovery slow
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-24-2006 12:03 PM
01-24-2006 12:03 PM
Re: make_net_recovery slow
It looks like the connection between NFS server and client is getting dropped and come up after sometime.
First of all , it is required to ensure you have latest NFS RPC patches installed on both servers.
Check the patch status using
# show-patches -a
Do you see any errors in syslog,dmesg on both servers?
Are these server on the same subnet?
Is there any firewall in between them?
When you see this erro, run these command
at server
# nfsstat -s
# mount -v
# netstat -s
run these command at client using
# rpcinfo -u
# rpcinfo -s
# rpcinfo -p
I see you started giving points to the replies for your questions which is good.
Maybe you can assign points for earlier replies later!!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-25-2006 03:34 AM
01-25-2006 03:34 AM
Re: make_net_recovery slow
# nfsstat -s --- shows all zeros (0)
# mount -v
/dev/vg00/lvol3 on / type vxfs ioerror=mwdisable,delaylog,dev=40000003 on Wed Jan 25 10:56:28 2006
/dev/vg00/lvol1 on /stand type vxfs ioerror=mwdisable,log,tranflush,dev=40000001 on Wed Jan 25 10:56:30 2006
/dev/vg00/lvol8 on /var type vxfs ioerror=mwdisable,delaylog,dev=40000008 on Wed Jan 25 10:56:43 2006
/dev/vg00/lvol7 on /usr type vxfs ioerror=mwdisable,delaylog,dev=40000007 on Wed Jan 25 10:56:43 2006
/dev/vg00/lvol4 on /tmp type vxfs ioerror=mwdisable,delaylog,dev=40000004 on Wed Jan 25 10:56:43 2006
/dev/vg00/lvol6 on /opt type vxfs ioerror=mwdisable,delaylog,dev=40000006 on Wed Jan 25 10:56:43 2006
/dev/vg00/lvol5 on /home type vxfs ioerror=mwdisable,delaylog,dev=40000005 on Wed Jan 25 10:56:43 2006
uni-rx4640-03:/var/opt/ignite/clients on /var/opt/ignite/recovery/client_mnt type nfs rsize=32768,wsize=32768,NFSv3,dev=63000001 on Wed Jan 25 11:28:27 2006
uni-rx4640-03:/var/opt/ignite/recovery/archives/uni-rx2620-01 on /var/opt/ignite/recovery/arch_mnt type nfs rsize=32768,wsize=32768,NFSv3,dev=63000002 on Wed Jan 25 11:28:58 2006
# netstat -s
tcp:
8960 packets sent
7380 data packets (6785683 bytes)
1407 data packets (1862840 bytes) retransmitted
1579 ack-only packets (545 delayed)
1 URG only packet
0 window probe packets
0 window update packets
1870 control packets
10506 packets received
6212 acks (for 7457000 bytes)
1339 duplicate acks
0 acks for unsent data
4514 packets (2300370 bytes) received in-sequence
0 completely duplicate packets (0 bytes)
0 packets with some dup, data (0 bytes duped)
0 out of order packets (0 bytes)
0 packets (0 bytes) of data after window
0 window probes
544 window update packets
1 packet received after close
0 segments discarded for bad checksum
0 bad TCP segments dropped due to state change
488 connection requests
460 connection accepts
948 connections established (including accepts)
945 connections closed (including 23 drops)
22 embryonic connections dropped
4483 segments updated rtt (of 4483 attempts)
299 retransmit timeouts
0 connections dropped by rexmit timeout
0 persist timeouts
0 keepalive timeouts
0 keepalive probes sent
0 connections dropped by keepalive
0 connect requests dropped due to full queue
22 connect requests dropped due to no listener
0 suspect connect requests dropped due to aging
0 suspect connect requests dropped due to rate
udp:
0 incomplete headers
0 bad checksums
0 socket overflows
ip:
4706 total packets received
0 bad IP headers
0 fragments received
0 fragments dropped (dup or out of space)
0 fragments dropped after timeout
0 packets forwarded
0 packets not forwardable
icmp:
5 calls to generate an ICMP error message
0 ICMP messages dropped
Output histogram:
echo reply: 5
destination unreachable: 0
source quench: 0
routing redirect: 0
echo: 0
time exceeded: 0
parameter problem: 0
time stamp: 0
time stamp reply: 0
address mask request: 0
address mask reply: 0
0 bad ICMP messages
Input histogram:
echo reply: 10
destination unreachable: 2
source quench: 0
routing redirect: 0
echo: 5
time exceeded: 0
parameter problem: 0
time stamp request: 0
time stamp reply: 0
address mask request: 0
address mask reply: 0
5 responses sent
igmp:
0 messages received
0 messages received with too few bytes
0 messages received with bad checksum
0 membership queries received
0 membership queries received with incorrect fields(s)
0 membership reports received
0 membership reports received with incorrect field(s)
0 membership reports received for groups to which this host belongs
0 membership reports sent
# rpcinfo -u uni-rx4640-03 nfs
program 100003 version 2 ready and waiting
program 100003 version 3 ready and waiting
# rpcinfo -p uni-rx4640-03
program vers proto port service
100000 4 tcp 111 rpcbind
100000 3 tcp 111 rpcbind
100000 2 tcp 111 rpcbind
100000 4 udp 111 rpcbind
100000 3 udp 111 rpcbind
100000 2 udp 111 rpcbind
100024 1 tcp 49152 status
100024 1 udp 49153 status
100021 1 tcp 49153 nlockmgr
100021 1 udp 49156 nlockmgr
100021 3 tcp 49154 nlockmgr
100021 3 udp 49157 nlockmgr
100021 4 tcp 49155 nlockmgr
100021 4 udp 49158 nlockmgr
100020 1 udp 4045 llockmgr
100020 1 tcp 4045 llockmgr
100021 2 tcp 49156 nlockmgr
100068 2 udp 49162 cmsd
100068 3 udp 49162 cmsd
100068 4 udp 49162 cmsd
100068 5 udp 49162 cmsd
100083 1 tcp 49157 ttdbserver
100005 1 udp 49201 mountd
100005 3 udp 49201 mountd
100005 1 tcp 49196 mountd
100005 3 tcp 49196 mountd
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100003 2 tcp 2049 nfs
100003 3 tcp 2049 nfs
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-25-2006 01:41 PM
01-25-2006 01:41 PM
Re: make_net_recovery slow
There are so many aspects one should check at network and nfs(itself) level.
I would advise to go through Dave Olker's NFS white paper. He is well known NFS Guru.
http://www.docs.hp.com/en/1435/NFSPerformanceTuninginHP-UX11.0and11iSystems.pdf
This would help you to check every aspect and find the cause of the issue.
Since the installed OS version is pretty much latest, I would suspect the cause like
incorrect network card speed settings ( half or full duplex) etc.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-27-2006 01:08 AM
01-27-2006 01:08 AM
Re: make_net_recovery slow
What is your network setting
lanadmin -x 0?
Is it the same on your switch
Modify the ignite settings with
instl_adm -f
fe
instl_adm â d > /tmp/cfg
add the following entry to /tmp/cfg
_hp_lanadmin_args=â -X 100FDâ
instl_adm â f > /tmp/cfg
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-27-2006 01:49 AM
01-27-2006 01:49 AM
Re: make_net_recovery slow
This also happens when I try to scp from one of the servers to another unrelated server. I've even tried it on a couple different NIC cards on my server. I'll call support
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-16-2006 06:49 AM
03-16-2006 06:49 AM