On Sun, 24 Oct 1999, Brian Tao wrote:
nfs1> vif create single VIF_Subnet1 e1a e2a nfs1> vif create single VIF_Subnet2 e2b e1b nfs1> vif favor e1a nfs1> vif favor e2b nfs1> ifconfig VIF_Subnet1 10.35.8.1 netmask 255.255.255.128 partner 10.35.8.2 nfs1> ifconfig VIF_Subnet2 10.35.8.129 netmask 255.255.255.128 partner 10.35.8.130
I think it should be:
nfs1> ifconfig VIF_Subnet1 10.35.8.1 netmask 255.255.255.128 partner VIF_Subnet1 nfs1> ifconfig VIF_Subnet2 10.35.8.129 netmask 255.255.255.128 partner VIF_Subnet2
nfs2> vif create single VIF_Subnet1 e1a e2a nfs2> vif create single VIF_Subnet2 e2b e1b nfs2> vif favor e1a nfs2> vif favor e2b nfs2> ifconfig VIF_Subnet1 10.35.8.2 netmask 255.255.255.128 partner 10.35.8.1 nfs2> ifconfig VIF_Subnet2 10.35.8.130 netmask 255.255.255.128 partner 10.35.8.129
and:
nfs2> ifconfig VIF_Subnet1 10.35.8.2 netmask 255.255.255.128 partner VIF_Subnet1 nfs2> ifconfig VIF_Subnet2 10.35.8.130 netmask 255.255.255.128 partner VIF_Subnet2
This is because I think that you cannot use IP addreses with trunk interfaces. At least you couldn't do it last time I set up "multi" trunking on a new rev of DOT.
What characters are allowed in a VIF name?
I have no idea, but I'd skip underlines for legacy purposes. NACs try to resolve the NIC name on takeover i.e. they will try to look up VIF_Subnet2.your.domain. Underlines are not allowed in DNS as I remember.
Keep me posted on the results of your experiments.
Tom