HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Delay in response after VLAN migration
Operating System - OpenVMS
1827808
Members
2136
Online
109969
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
Forums
Discussions
Discussions
Discussions
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
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
05-30-2007 04:36 AM
05-30-2007 04:36 AM
Customer recently migrated from WAN to VLAN. Because of a security issue they, also, introduced a "tunnel". Their shop runs a shop floor application from PC's, where the application and files are on an Alpha and the database (Oracle) is on a Sun server. The Alpha is a 4100 running OpenVMS 7.1-1H2, UCX V4.2 ECO 5 and has an EW_DE500 ethernet card with line speed 100 and full duplex off. They are now experiencing delays and are asking about MTU (maximum transfer Unit?) detection and discovery and possibly turning it off. The user has Unix and Windows experience.
I'm not familiar with MTU. Is there such a thing in this ethernet/ucx environment? Is there a counter that might reflect their "delay" problem. There are no waits or drops in "ucx show comm /mem" and nothing jumps out at me in "anal/sys show lan/dev=ewa". They are not running DECNET.
Thanks in advance for any/all responses.
I'm not familiar with MTU. Is there such a thing in this ethernet/ucx environment? Is there a counter that might reflect their "delay" problem. There are no waits or drops in "ucx show comm /mem" and nothing jumps out at me in "anal/sys show lan/dev=ewa". They are not running DECNET.
Thanks in advance for any/all responses.
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-30-2007 05:29 AM
05-30-2007 05:29 AM
Re: Delay in response after VLAN migration
If possible, I'd push for a full duplex connection.
That said, the VPN tunnel may introduce addtional overhead and split packets comming from the Alpha. See
UCX> help set protocol/mtu
The VPN documenation should have a recommended maximum MTU.
Another option is to upgrade UCX to TCPIP. You should be able to run 5.0a, possibly 5.1. TCPIP provides better performance for IP traffic.
Andy
That said, the VPN tunnel may introduce addtional overhead and split packets comming from the Alpha. See
UCX> help set protocol/mtu
The VPN documenation should have a recommended maximum MTU.
Another option is to upgrade UCX to TCPIP. You should be able to run 5.0a, possibly 5.1. TCPIP provides better performance for IP traffic.
Andy
If you don't have time to do it right, when will you have time to do it over? Reach me at first_name + "." + last_name at sysmanager net
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-30-2007 05:30 AM
05-30-2007 05:30 AM
Solution
My understanding is that with some (all) VLAN implementations, as packets are routed through the virtual pipe, they are encapsulated in an outer package that contributes numerous bytes to their size. IP implementations recongnize hardware configurations and by default try to be efficient and create packets that are already at the maximum size supported by the hardware. So, once the size is exceeded (with the addition of the VLAN's overhead) the packets have to be fragmented in order to transfer - and then re-assembled on the other end. I'm not a UCX user so I can't tell you how to (I'm sure someone else reading here can) alter the MTU (yes, the maximum transfer unit which for ethernet is ~1500 bytes) but, I can tell that using MultiNet in similar situations I've had success lowering the MTU from 1500 to 1300 to curb the need for packet fragmentation and re-assembly.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-30-2007 07:07 AM
05-30-2007 07:07 AM
Re: Delay in response after VLAN migration
Needed the MTU option, thanks.
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.
Company
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP