- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- How to set primary interface in failsafe ip tcpip ...
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
тАО03-17-2009 02:11 PM
тАО03-17-2009 02:11 PM
How to set primary interface in failsafe ip tcpip version 5.6
I've been searching the literature to try to figure out how to change this but have not found the exact command to do it. Anyone know the correct command to create/change the primary interface?
ALPHAD> IFCONFIG -A
IE0: flags=c43
*inet 172.20.66.165 netmask fffffe00 broadcast 172.20.67.255 ipmtu 1500
LO0: flags=100c89
inet 127.0.0.1 netmask ff000000 ipmtu 4096
TN0: flags=80
TN1: flags=80
WE0: flags=c43
Standby addresses:
*inet 172.20.66.165 netmask fffffe00 broadcast 172.20.67.255 (Active on A
LPHAD IE0)
thanks
Clark Powell
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-17-2009 04:18 PM
тАО03-17-2009 04:18 PM
Re: How to set primary interface in failsafe ip tcpip version 5.6
$ ifconfig ieo fail
$ ifconfig ieo -fail
You may consider assigning IE0 an WEO unique addresses with no failover then assign a third address as the "service" address configured for fail over between the two interfaces.
See http://h71000.www7.hp.com/openvms/journal/v2/articles/tcpip.html for Matt Muggeridge's OpenVMS Technical Journal reviewing failSAFE IP.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-17-2009 04:26 PM
тАО03-17-2009 04:26 PM
Re: How to set primary interface in failsafe ip tcpip version 5.6
http://h71000.www7.hp.com/doc/83final/6526/6526pro_006.html
and read and scroll down to the section on how to simulate a failure with the logical name:
TCPIP$FAILSAFE_FAILED_ifname
Check the failsafe log from the activity, too.
And as there have been various issues on various releases, load the UPDATE ECO (and the LAN ECO, if that's not included) and load the TCPIP ECO.
And if you're seeing something weird (and you're current on your ECO kits), ring up HP.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-17-2009 08:56 PM
тАО03-17-2009 08:56 PM
Re: How to set primary interface in failsafe ip tcpip version 5.6
>>$ ifconfig ieo fail
>>
>>$ ifconfig ieo -fail
I just want to point out that you should *not* issue this sequence of commands unless you really understand what goes on under the hood. As few appreciate the inner workings of TCP/IP, I regret documenting it.
The problem with these commands is that it they represent just one step in the sequence of failover/recovery. Most importantly, when you issue the "-fail", it does not recover static routes to that interface. You would need to do that manually, amongst other possible steps.
It's far, far, far, better to let failSAFE do the work. As Hoff described:
$ reply/enable ! so you can see the events
$ define/sys tcpip$failsafe_failed_ie0 1
$! wait for failover
$ deass/sys tcpip$failsafe_failed_ie0
If problems persist, and for future reference:
It would also have helped if you listed the output of:
$ ifconfig -av
Also, if you are using your own procedures to create your addresses (as opposed to using TCPIP$CONFIG), then it would help to see those too.
Cheers,
Matt.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-18-2009 11:05 AM
тАО03-18-2009 11:05 AM
Re: How to set primary interface in failsafe ip tcpip version 5.6
1.) why does this system have two "home interfaces" for the same ip address? That is, two interfaces with an "*." Isn't that paradoxical?
ALPHAD> ifconfig -av
IE0: flags=c43
*inet 172.20.66.165 netmask fffffe00 broadcast 172.20.67.255 ipmtu 1500 (Sta
ndby on ALPHAD)
HWaddr aa:00:04:00:0b:04
LO0: flags=100c89
inet 127.0.0.1 netmask ff000000 ipmtu 4096
TN0: flags=80
TN1: flags=80
WE0: flags=c43
Standby addresses:
*inet 172.20.66.165 netmask fffffe00 broadcast 172.20.67.255 (Active on A
LPHAD IE0)
HWaddr 00:18:fe:83:85:f1
These were created using tcpip$config.com
What I want is to have the interface go back to the 1000 MB interface as soon as it is functional again. My interpretation is that that is what a "home interface" is for, to be a prefered interface in the failsafe ip scheme. But, I have two home interfaces so I need to reduce this to one. But, I've only seen literature for adding a home interface and not for removing that quality from an interface.