- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: NFS packet analysis when RPC timed out
Operating System - HP-UX
1748204
Members
4021
Online
108759
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
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
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
тАО08-27-2010 03:58 AM
тАО08-27-2010 03:58 AM
NFS packet analysis when RPC timed out
sometimes nfs RPC: timed out like;
syslog.log:
Aug 27 00:39:55 kpotp1 vmunix: Secuve TOS 2.0 (V2.0.60.8)
Aug 27 00:47:51 kpotp1 vmunix: NFS lookup failed for server kpo: RPC: Timed out
Aug 27 00:54:53 kpotp1 vmunix: Secuve TOS 2.0 (V2.0.60.8)
Aug 27 00:57:00 kpotp1 above message repeats 3 times
Aug 27 00:47:52 kpotp1 vmunix: NFS lookup failed for server kpo: RPC: Timed out
So, I asked customer nettle output on both sides(server & client, bith system are HP-UX).
I analyzed that packet using wireshark tool and send you it.
Problem time: Aug 27 00:47:51
From packet data below, I saw no packet sent to server from 00:47.44.335293 to 00:47:49:105362,
Server also didnтАЩt get any packet during same time.
Is my analysis right? And if so, what happened on client side? nfs itself hang?
HP-UX 11.23.
Client(source IP:xxx, dst IP: yyy) side:
37838 2010-08-27 00:47:44.334910 xxx yyy NFS V3 GETATTR Call (Reply In 37839), FH:0xbfd7e16b
37840 2010-08-27 00:47:44.335066 xxx yyy NFS V3 GETATTR Call (Reply In 37843), FH:0xbfd7e57b
37845 2010-08-27 00:47:44.335293 xxx yyy NFS V3 GETATTR Call (Reply In 37847), FH:0xbfd7e16b
38081 2010-08-27 00:47:49.105362 xxx yyy NFS V3 GETATTR Call (Reply In 38082), FH:0xbfd7f5e8
38096 2010-08-27 00:47:49.574216 xxx yyy NFS V3 FSSTAT Call (Reply In 38101), FH:0xbfd7402a
38099 2010-08-27 00:47:49.574429 xxx yyy NFS V3 FSSTAT Call (Reply In 38100), FH:0xbfd7402a
Server(source IP: yyy, dst ip: xxx) side:
20161 2010-08-27 00:47:44.336959 yyy xxx NFS V3 GETATTR Reply (Call In 20160) Directory mode:0775 uid:104 gid:20
20164 2010-08-27 00:47:44.337125 yyy xxx NFS V3 GETATTR Reply (Call In 20162) Directory mode:0777 uid:104 gid:20
20167 2010-08-27 00:47:44.337331 yyy xxx NFS V3 GETATTR Reply (Call In 20166) Directory mode:0775 uid:104 gid:20
44611 2010-08-27 00:47:49.107417 yyy xxx NFS V3 GETATTR Reply (Call In 44610) Directory mode:0775 uid:104 gid:20
47930 2010-08-27 00:47:49.576476 yyy xxx NFS V3 FSSTAT Reply (Call In 47929)
47931 2010-08-27 00:47:49.576496 yyy xxx NFS V3 FSSTAT Reply (Call In 47924)
syslog.log:
Aug 27 00:39:55 kpotp1 vmunix: Secuve TOS 2.0 (V2.0.60.8)
Aug 27 00:47:51 kpotp1 vmunix: NFS lookup failed for server kpo: RPC: Timed out
Aug 27 00:54:53 kpotp1 vmunix: Secuve TOS 2.0 (V2.0.60.8)
Aug 27 00:57:00 kpotp1 above message repeats 3 times
Aug 27 00:47:52 kpotp1 vmunix: NFS lookup failed for server kpo: RPC: Timed out
So, I asked customer nettle output on both sides(server & client, bith system are HP-UX).
I analyzed that packet using wireshark tool and send you it.
Problem time: Aug 27 00:47:51
From packet data below, I saw no packet sent to server from 00:47.44.335293 to 00:47:49:105362,
Server also didnтАЩt get any packet during same time.
Is my analysis right? And if so, what happened on client side? nfs itself hang?
HP-UX 11.23.
Client(source IP:xxx, dst IP: yyy) side:
37838 2010-08-27 00:47:44.334910 xxx yyy NFS V3 GETATTR Call (Reply In 37839), FH:0xbfd7e16b
37840 2010-08-27 00:47:44.335066 xxx yyy NFS V3 GETATTR Call (Reply In 37843), FH:0xbfd7e57b
37845 2010-08-27 00:47:44.335293 xxx yyy NFS V3 GETATTR Call (Reply In 37847), FH:0xbfd7e16b
38081 2010-08-27 00:47:49.105362 xxx yyy NFS V3 GETATTR Call (Reply In 38082), FH:0xbfd7f5e8
38096 2010-08-27 00:47:49.574216 xxx yyy NFS V3 FSSTAT Call (Reply In 38101), FH:0xbfd7402a
38099 2010-08-27 00:47:49.574429 xxx yyy NFS V3 FSSTAT Call (Reply In 38100), FH:0xbfd7402a
Server(source IP: yyy, dst ip: xxx) side:
20161 2010-08-27 00:47:44.336959 yyy xxx NFS V3 GETATTR Reply (Call In 20160) Directory mode:0775 uid:104 gid:20
20164 2010-08-27 00:47:44.337125 yyy xxx NFS V3 GETATTR Reply (Call In 20162) Directory mode:0777 uid:104 gid:20
20167 2010-08-27 00:47:44.337331 yyy xxx NFS V3 GETATTR Reply (Call In 20166) Directory mode:0775 uid:104 gid:20
44611 2010-08-27 00:47:49.107417 yyy xxx NFS V3 GETATTR Reply (Call In 44610) Directory mode:0775 uid:104 gid:20
47930 2010-08-27 00:47:49.576476 yyy xxx NFS V3 FSSTAT Reply (Call In 47929)
47931 2010-08-27 00:47:49.576496 yyy xxx NFS V3 FSSTAT Reply (Call In 47924)
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-27-2010 08:50 AM
тАО08-27-2010 08:50 AM
Re: NFS packet analysis when RPC timed out
Reply in and Call in comments tend to prove that both system see both in packets
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-27-2010 04:25 PM
тАО08-27-2010 04:25 PM
Re: NFS packet analysis when RPC timed out
Thank you for your reply.
My curious is why no packets from 00:47.44.335293 to 00:47:49:105362 during about 5 seconds.
Regards
My curious is why no packets from 00:47.44.335293 to 00:47:49:105362 during about 5 seconds.
Regards
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP