- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: TCP/IP and "Round Robin" issues
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
тАО02-17-2006 06:02 AM
тАО02-17-2006 06:02 AM
TCP/IP and "Round Robin" issues
I use the terms "UCX" and "TCP/IP Services for OpenVMS" interchangeably, mostly for reasons of brevity.
I've been asking this question everywhere I can and, to date, no one has been able to come up with an answer.
Our site recently migrated to UCX (from Multinet), mostly at our application vendor's request. So far, "faster is better", with one very serious limitation.
(Apologies if the forum scrambles the format of this...)
Consider:
$ ucx sho int
Packets
Interface IP_Addr Network mask Receive Send MTU
LO0 127.0.0.1 255.0.0.0 5288801 5288801 4096
WE0 xxx.xx.xx.205 255.255.255.0 3346932877 3543180500 1500
WE1 xxx.xx.xx.206 255.255.255.0 2596612243 2567812743 1500
If WE1 loses IP Connectivity due to a down-stream issue, UCX will never detect this so long as the interface still has a physical link and, because of "round robin" routing of outbound packets destined for the xxx.xx.xx/24 subnet, production effectively goes down as connectivity to the network falls to less than 40% reliability.
Any thoughts as to how to fix this?
The only way to restore production that I've found to date has been to manually reduce the routing table from this:
$ ucx show route
DYNAMIC
Type Destination Gateway
AN 0.0.0.0 xxx.xx.xx.1
AH 127.0.0.1 127.0.0.1
AN xxx.xx.xx.0/24 xxx.xx.xx.205
AN xxx.xx.xx.0/24 xxx.xx.xx.206
AH xxx.xx.xx.205 xxx.xx.xx.205
AH xxx.xx.xx.206 xxx.xx.xx.206
...to this:
$ ucx show route
DYNAMIC
Type Destination Gateway
AN 0.0.0.0 xxx.xx.xx.1
AH 127.0.0.1 127.0.0.1
...provided the default route is still associated with a working interface.
UCX Engineering is stumped as is support, and no one in the vmsnet.networks.tcp-ip.ucx or comp.os.vms newsgroups has come up with anything useful.
Any ideas anyone may have will be tremendously helpful.
Thanx much.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-17-2006 07:36 AM
тАО02-17-2006 07:36 AM
Re: TCP/IP and "Round Robin" issues
regards Kalle
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-17-2006 04:11 PM
тАО02-17-2006 04:11 PM
Re: TCP/IP and "Round Robin" issues
Thanx for your reply, though. All input is appreciated and welcome.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-17-2006 11:41 PM
тАО02-17-2006 11:41 PM
Re: TCP/IP and "Round Robin" issues
welcome to the OpenVMS ITRC forum !
Regarding the 'detectability' of the problem: wouldn't a PING some-dest-addr drop to about 50% packet loss in such a situation ?
FailsafeIP just monitors the 'bytes received' counters of each interface, so unless one of the interfaces stops receiving packets, this won't help.
Volker.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-19-2006 08:02 PM
тАО02-19-2006 08:02 PM
Re: TCP/IP and "Round Robin" issues
just came across TCPIP> HELP ROUTE
...
12. To change existing network route 206.98.17 using interface device tu0 and gateway 206.98.17.45 to use device tu1 and
gateway 206.98.17.162, enter the following command:
TCPIP> route change -net 206.98.17 206.98.17.162 -olddev tu0 -dev tu1 \
-oldgateway 206.98.17.45
Would a similar command be worth to try in your scenario ?
Volker.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-20-2006 01:38 AM
тАО02-20-2006 01:38 AM
Re: TCP/IP and "Round Robin" issues
We're looking for something that completely sidesteps any need for manual intervention ("lights out, unattended").
Thanx for replying. I appreciate all the input I can get.
D.J.D.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-20-2006 07:29 PM
тАО02-20-2006 07:29 PM
Re: TCP/IP and "Round Robin" issues
if you're looking for a 'configuration option' to automatically take care of this problem, this may not be possible.
My last 2 comments were trying to suggest procedures to be able to 'detect' the problem and trying to 'fix' it, manually or within an appropriate DCL procedure.
Using FailsafeIP and creating each interface's IP address with a failover address on the other interface may also provide the mechanism to easily fail over the IP address of the 'failing' interface (if you can detect that one) to the 'working' interface (using the TCPIP$FAILSAFE_FAILED_int logical).
Volker.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-21-2006 12:13 PM
тАО02-21-2006 12:13 PM
Re: TCP/IP and "Round Robin" issues
I certainly appreciate the input.
As you can imagine, this is rather a thorn in our side. We made this change because the vendor was convinced it would solve the high interrupt service demand tyime we were seeing with Multinet. At least Multinet could survive the loss of an interface (other than the default route) without bringing production down.