Ethernet Interface configuration on ES80

[Ziggy Filek]

I have 4 NICs on an ES80. One is configured as WE0. $TCPIP SHOW INTERFACE just shows this one:
TCPIP> show interface we
Packets
Interface IP_Addr Network mask Receive Send MTU

WE0 10.171.2.7 255.255.255.0 299903 345728 1500
TCPIP>

How do I configure another one to be used as failSAFE IP? Do I need to plug it into network first?
When I use the approach as described in the Chapter 5 of the TCPIP Services for OpenVMS Management nothing seems to work as advertised.
When I go
TCPIP> set interface WE1 /HOST=10.171.2.7
the show interface command and the "show interface we" give different outputs:
TCPIP> show interface
Packets
Interface IP_Addr Network mask Receive Send MTU

LO0 127.0.0.1 255.0.0.0 96198 96198 4096
WE0 10.171.2.7 255.255.255.0 300603 346593 1500
WE1 0 0 1500
TCPIP> show interface we
Packets
Interface IP_Addr Network mask Receive Send MTU

WE0 10.171.2.7 255.255.255.0 300637 346617 1500
TCPIP>
I'd appreciate step-by-step instructions, if possible, since I already read the manual, to no avail.

Thanks!
Ziggy

[Andy Bustamante]

Before you configure an interface in TCPIP, particularly for failSAFE IP, you should make the physical connection and ensure the Alphaserver and the networking equipment agree on the speed and duplex. This will require either setting the appropriate console value or using LANCP to define and set.

Once that's out of the way, you use

@sys$manager:tcpip$config

Follow the menu to configure the interface and the failSAFE IP. Make sure to enable the failSAFE IP service, I believe that's under Options Components.

Ideally, you'll want to connect each interface to a diffent switch. You can configure each interface with it's own address and have the failSAFE migrate a the address to one of the available interfaces. LAN failover (see the System Manger's Manual) is also an option. Besides the manual, see http://h71000.www7.hp.com/openvms/journal/v2/articles/tcpip.html for for an excellent write up and planning options.

Andy

[David B Sneddon]

Have you tried doing the configuration via

@SYS$MANAGER:TCPIP$CONFIG

If so, did you encounter any problems?

Dave

[Ziggy Filek]

Thank you guys: I'm closing this thread since I need to open another one with a more precise description of the problem.