- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: Logical name timeout on OVMS8.3?
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
Discussions
Discussions
Forums
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
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
тАО05-11-2009 12:42 AM
тАО05-11-2009 12:42 AM
Logical name timeout on OVMS8.3?
I can, for example, do dir dev1 or dir dev2, also dir logname and they all work. If the actual physical connection to dev1 or dev2 goes away, I can still do a successful dir logname and see the contents of the remaining device. But, it takes about 30s for the logical name to drop through the list and hit the "online" device.
Is there any way (SYSGEN parameter?) to make this faster - much faster?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-11-2009 12:53 AM
тАО05-11-2009 12:53 AM
Re: Logical name timeout on OVMS8.3?
what happens to DIR dev1: if the 'actual physical connection' to that device goes away ? What kind of disks are these ? What do you do them ?
Is there an error message regarding dev1: in DIR logname, if that device is 'offline' ?
Volker.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-11-2009 01:39 AM
тАО05-11-2009 01:39 AM
Re: Logical name timeout on OVMS8.3?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-11-2009 01:45 AM
тАО05-11-2009 01:45 AM
Re: Logical name timeout on OVMS8.3?
does the DIR nfs1:[000000] fail immediately or after around 20 seconds ? What kind of error is reported ?
This has nothing to do with logical names. This may involve a NFS-related timeout mechanism.
Volker.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-11-2009 01:46 AM
тАО05-11-2009 01:46 AM
Re: Logical name timeout on OVMS8.3?
It is, from memory, an NFS related timeout - perhaps I need to find an NFS parameter so that it "fails" faster?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-11-2009 01:51 AM
тАО05-11-2009 01:51 AM
Re: Logical name timeout on OVMS8.3?
read $ TCPIP HELP MOUNT
This may give parameters, which could be 'tweaked'...
Volker.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-11-2009 01:54 AM
тАО05-11-2009 01:54 AM
Re: Logical name timeout on OVMS8.3?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-11-2009 02:41 AM
тАО05-11-2009 02:41 AM
Re: Logical name timeout on OVMS8.3?
At my site it took about 15 seconds when retry was 4. When retry was 1 it took 4 seconds.
Strange but tcptrace shows 5 retrans when retry is 1.
Wim
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-11-2009 04:12 AM
тАО05-11-2009 04:12 AM
Re: Logical name timeout on OVMS8.3?
There appear to be no other parameters I can set, OVMS is a client for NFS services, so the server parameters seem unlikely. Looked at ACP and RMS parameters in SYSGEN to see if something there was set to 30s, couldn't find anything. Certainly, when a $dir fails, I get an RMS and ACP error which leads me down that path, but it seems to lead nowhere....sigh.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-11-2009 05:04 AM
тАО05-11-2009 05:04 AM
Re: Logical name timeout on OVMS8.3?
again, this timeout has nothing to do with Logical names, RMS, F11BXQP etc. so there are no knobs in OpenVMS itself to be turned. If the device would be a failed SCSI disk, the DIR command would actually hang, until the disk aborts mount-verification (after MVTIMEOUT seconds).
You would need to research and study the NFS timeout mechanisms e.g. using tcpdump and some tests to figure out, which timers may influence this behaviour.
Volker.