LOG_ALERT email for non-reudundant node management LIF - why?

[jmalone]

I'm getting LOG_ALERT emails from a dual-node FAS-2552 system nagging me about a non-redundandt port, but that port is the node management LIF for node 02 which (as I understand it) is not intended to be failed over. Curiously, I never get these about node 01.

Is there an actual problem that I need to fix? Or is there a way to just make the alert go away?

TOASTER::network interface> show -instance -lif TOASTER-02_mgmt1

                    Vserver Name: TOASTER
          Logical Interface Name: TOASTER-02_mgmt1
                            Role: node-mgmt
                   Data Protocol: -
                       Home Node: TOASTER-02
                       Home Port: e0M
                    Current Node: TOASTER-02
                    Current Port: e0M
              Operational Status: up
                 Extended Status: -
                         Is Home: true
                 Network Address: 10.2.1.111
                         Netmask: 255.255.255.0
             Bits in the Netmask: 24
                 IPv4 Link Local: -
                     Subnet Name: MGMTnet
           Administrative Status: up
                 Failover Policy: local-only
                 Firewall Policy: mgmt
                     Auto Revert: true
   Fully Qualified DNS Zone Name: none
         DNS Query Listen Enable: false
             Failover Group Name: Default Network
                        FCP WWPN: -
                  Address family: ipv4
                         Comment: -
                  IPspace of LIF: Default
  Is Dynamic DNS Update Enabled?: -

TOASTER::network interface> show -instance -lif TOASTER-01_mgmt1

                    Vserver Name: TOASTER
          Logical Interface Name: TOASTER-01_mgmt1
                            Role: node-mgmt
                   Data Protocol: -
                       Home Node: TOASTER-01
                       Home Port: e0M
                    Current Node: TOASTER-01
                    Current Port: e0M
              Operational Status: up
                 Extended Status: -
                         Is Home: true
                 Network Address: 10.2.1.121
                         Netmask: 255.255.255.0
             Bits in the Netmask: 24
                 IPv4 Link Local: -
                     Subnet Name: MGMTnet
           Administrative Status: up
                 Failover Policy: local-only
                 Firewall Policy: mgmt
                     Auto Revert: true
   Fully Qualified DNS Zone Name: none
         DNS Query Listen Enable: false
             Failover Group Name: Default Network
                        FCP WWPN: -
                  Address family: ipv4
                         Comment: -
                  IPspace of LIF: Default
  Is Dynamic DNS Update Enabled?: -

[andris · Accepted solution]

Actually, the node management LIF can fail over - but it's restricted to other ports on the same node. (failover policy = local-only).

You might want to look at your "Default Network" failover group's membership to see why node2 is unhappy but node1 is OK.

If you truly do not want the node-mgmt LIF to fail over to another port other than e0M, you can set the failover policy of the node-mgmt LIF to "disabled" (a tip from @Overz)

::> network interface modify -vserver svm_name -lif lif_name -failover-policy disabled