- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Multiple NIC's and protocols
Operating System - OpenVMS
1753685
Members
5421
Online
108799
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
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
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
03-11-2005 02:47 AM
03-11-2005 02:47 AM
Experts - I have a question regarding installing multiple nic cards in an AS4100. Currently I am testing different products that assist in NIC failover.
One such product is Multinet's Pseudo device configuration. This configuration allows for a Pseudo device to be established which is linked to two cards. This option allows for outbound load balancing and failover if one card were to become unusable.
I will also be testing in the near future the native VMS LAN Failover option available in VMS 7.3-2.
One thing I noticed about the multinet option is that its I/P only. It does not include other protocols under the failover protection (assuming one is not using the DECnet over I/P feature). So items such as LAT, DECnet and so on are not covered.
Does anyone know if failSAFE IP operates in a similar way?
With native VMS LAN failover, a driver creates a LL device. So items such as DECnet and LAT can use the LL device name and bind to it. With multinet, there is no logical device to bind to outside of Multinet.
Besides LAT and DECnet, my specific issue has been using Availability Manager. While using the Multinet option I do not have a logical device, however, I still must tell AMDS to bind to a physical device (EIA). But AMDS does not like it at all. Communications are interrupted to the node and simple actions like FTP's or Telnet's to a node while AMDS is running are not reliable.
Anyone have experience using Availability Manager with Multinet Pseudo devices? Or with VMS Lan failover for that matter?
Thanks,
MC
One such product is Multinet's Pseudo device configuration. This configuration allows for a Pseudo device to be established which is linked to two cards. This option allows for outbound load balancing and failover if one card were to become unusable.
I will also be testing in the near future the native VMS LAN Failover option available in VMS 7.3-2.
One thing I noticed about the multinet option is that its I/P only. It does not include other protocols under the failover protection (assuming one is not using the DECnet over I/P feature). So items such as LAT, DECnet and so on are not covered.
Does anyone know if failSAFE IP operates in a similar way?
With native VMS LAN failover, a driver creates a LL device. So items such as DECnet and LAT can use the LL device name and bind to it. With multinet, there is no logical device to bind to outside of Multinet.
Besides LAT and DECnet, my specific issue has been using Availability Manager. While using the Multinet option I do not have a logical device, however, I still must tell AMDS to bind to a physical device (EIA). But AMDS does not like it at all. Communications are interrupted to the node and simple actions like FTP's or Telnet's to a node while AMDS is running are not reliable.
Anyone have experience using Availability Manager with Multinet Pseudo devices? Or with VMS Lan failover for that matter?
Thanks,
MC
It is what it is!
Solved! Go to Solution.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-11-2005 03:24 AM
03-11-2005 03:24 AM
Solution
MC,
LAN failover is an integral part of OpenVMS V7.3-2 (or higher), and as such - just works. All your network protocols will be bound to the LLA device and - as long as one of the failover devices in the set is o.k. - will work transparently. You can manually force a LAN device failover with LANCP> SET DEVICE/SWITCH LLA
FailSAFE IP only works for the TCPIP protocol. It will allow a TCPIP address to fail over to another NIC, if the first one fails. You can run other protocols on those NICs, but they will not fail over.
No problems with AMDS in either config.
Volker.
LAN failover is an integral part of OpenVMS V7.3-2 (or higher), and as such - just works. All your network protocols will be bound to the LLA device and - as long as one of the failover devices in the set is o.k. - will work transparently. You can manually force a LAN device failover with LANCP> SET DEVICE/SWITCH LLA
FailSAFE IP only works for the TCPIP protocol. It will allow a TCPIP address to fail over to another NIC, if the first one fails. You can run other protocols on those NICs, but they will not fail over.
No problems with AMDS in either config.
Volker.
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