This can be a result of incomplete configuration. When configuring an interface or interface group with the ifconfig command, nfo needs to be included to have Network FailOver (NFO) enabled for the specific interface. Make sure the information is also included in the RC files of the storage systems.
For example: ifconfig vif1 `hostname`-vif11 netmask 255.255.255.0 nfo partner vif1 mtusize 1500 If there are VLANs on top of Virtual Interface Groups (VIFs), NFO can be enabled on the VLANs directly or on the main VIF. If NFO is enabled on the main VIF, it has to be assigned with an IP, even if it is a generic one, only for Data ONTAP to notice the UP to DOWN transition. If the main VIF does not have an IP assigned, it is not recognized as UP in ifconfig -A.
This can be a result of incomplete configuration. When configuring an interface or interface group with the ifconfig command, nfo needs to be included to have Network FailOver (NFO) enabled for the specific interface.
Sorry, but that is wrong. "partner XXX not in use" simply means that there was no failover, so partner interface is inactive on this filer. NFO is something rather different and enables failover in case on network connectivity loss. It is unrelated to this question.
Again in the same subject the "network management interface"
I have encountered a behaviour that disturb me.
at the network level I have implemented a trunk named vif0 based on e0a and e0b ports.
Above this vif0 I have created a vlan id=53 with the following command :" vlan create vif0 53"
From this point I have 2 interfaces.
In front of the filer physical interface I managed the port swtich in order to be a trunked ports. I have the default_vlan and the vlan-53 configured on my swich router. the routing operation is enable on the switch-router.
next are the commands used to configure vif0 and vif0-53 :