Data Domain HA External LAN Heartbeat Status not ok

           

   Article Number:     530134                                   Article Version: 4     Article Type:    Break Fix 
   

 


Product:

 

Data Domain

 

Issue:

 

 

-- External LAN Heartbeat Status not ok after HA failover, all the other status are OK.   
   
    HA Detailed Status     
      ------------------     
      HA System name:               hasystem.xxx.com     
      HA System Status:             highly available     
      Interconnect Status:          ok     
      Primary Heartbeat Status:      ok     
      External LAN Heartbeat Status: not ok     
      Hardware compatibility check: ok     
      Software Version Check:       ok
   
   
   
    Node ha9500a.xxx.com:     
              Role:          active     
              HA State:      online     
              Node Health: ok     
     
     
      Node ha9500b.xxx.com:     
              Role:          standby     
              HA State:      online     
              Node Health: ok     
     
     
      Mirroring Status:     
      Component Name   Status     
      --------------   ------     
      nvram            ok         
      registry         ok         
      sms              ok         
      ddboost          ok         
      cifs             ok         
      --------------   ------
   
   
     
                                                           

 

 

Resolution:

 

 

-- The status does not impact the HA failover function.    
    If the external heartbeat failed, ha still can be online state and it will not impact the ha failover.    
   
    -- It showed that HA didn't find any floating port settings after system booting up.   
    12/05 22:10:24 INFO: HA SEC HB:Inside load lfd IPs, num_ports:0     
      12/05 22:10:24 INFO: HA SEC HB:failed to find any floating IP port
   
   
    When there is no port found, ha sec heartbeat thread will exit, so even the floating ip was restored later,ha will not try to connect, and lead to the status not OK.   
     
                                                           

 

 

Notes:

 

 

-- The workaround is rebooting the standby node.   
   
    -- Recommend to upgrade DDOS to 6.1.2.20 or higher.