Forum Discussion

Peter_Calder_71's avatar
Peter_Calder_71
Icon for Nimbostratus rankNimbostratus
Jan 16, 2013

b config sync all causes active peer to go standby then active?

Hi guys,

 

What we have is a pair of D62s running BIGIP v9.3.1 40.2 in an active/standby configuration.

 

When running a b config sync all from the command line, the active load balancer appears to go standby for about 30 seconds and then returns to active.

 

While this is happening, connections appear to be dropping (even those with connection mirroring).

 

However: a config sync from the web UI doesn't appear to cause the same issue.

 

Because this is a production system, I'm not game to try a b config sync min to see if there is any difference.

 

Has anyone else had the same issue?

 

Cheers,

 

Peter

 

3 Replies

  • is there anything suspicious in /var/log/ltm during that time?
  • Ok looked at the LTM log and am now more confused.

    
    Jan 14 14:00:04 loadbalancer01 b[4679]: 010a0043:5: The configuration was successfully loaded.
    Jan 14 14:00:04 sccp bcm56xxd[237]: 012c0015:6: Link: 1.2 is DOWN
    Jan 14 14:00:04 sccp bcm56xxd[237]: 012c0015:6: Link: 1.1 is DOWN
    Jan 14 14:00:04 sccp bcm56xxd[237]: 012c0015:6: Link: 1.4 is DOWN
    Jan 14 14:00:04 sccp bcm56xxd[237]: 012c0015:6: Link: 1.3 is DOWN
    Jan 14 14:00:04 sccp bcm56xxd[237]: 012c0015:6: Link: 1.5 is DOWN
    Jan 14 14:00:04 loadbalancer01 lacpd[988]: 01160010:6: Link 1.2 removed from aggregation
    Jan 14 14:00:04 loadbalancer01 lacpd[988]: 01160010:6: Link 1.3 removed from aggregation
    Jan 14 14:00:08 tmm tmm[931]: 01340002:3: HA Connection with peer 192.168.0.2:12267 lost.
    Jan 14 14:00:08 sccp bcm56xxd[237]: 012c0015:6: Link: 1.2 is UP
    Jan 14 14:00:08 sccp bcm56xxd[237]: 012c0015:6: Link: 1.1 is UP
    Jan 14 14:00:08 sccp bcm56xxd[237]: 012c0015:6: Link: 1.4 is UP
    Jan 14 14:00:08 sccp bcm56xxd[237]: 012c0015:6: Link: 1.3 is UP
    Jan 14 14:00:08 tmm tmm[931]: 01340002:3: HA Connection with peer 10.254.1.83:12266 lost.
    Jan 14 14:00:08 sccp bcm56xxd[237]: 012c0015:6: Link: 1.5 is UP
    Jan 14 14:00:08 loadbalancer01 lacpd[988]: 01160009:6: Link 1.2 added to aggregation
    Jan 14 14:00:08 loadbalancer01 lacpd[988]: 01160009:6: Link 1.3 added to aggregation
    Jan 14 14:00:09 tmm tmm[931]: 01340001:3: HA Connection with peer 192.168.0.2:12306 established.
    Jan 14 14:00:09 tmm tmm[931]: 01340001:3: HA Connection with peer 10.254.1.83:12307 established.
    Jan 14 14:00:34 loadbalancer01 sod[998]: 01140029:5: HA vlan_fs Vlan2 fails action is failover.
    Jan 14 14:00:34 loadbalancer01 sod[998]: 010c0026:5: Failover condition, active attempting to go standby.
    Jan 14 14:00:41 loadbalancer01 sod[998]: 01140030:5: HA vlan_fs Vlan2 is now responding.
    Jan 14 14:00:41 tmm tmm[931]: 01340002:3: HA Connection with peer 10.254.1.83:12307 lost.
    Jan 14 14:00:41 tmm tmm[931]: 01340002:3: HA Connection with peer 192.168.0.2:12306 lost.
    Jan 14 14:00:42 tmm tmm[931]: 01340001:3: HA Connection with peer 10.254.1.83:12308 established.
    Jan 14 14:00:43 tmm tmm[931]: 01340001:3: HA Connection with peer 192.168.0.2:12309 established.
    Jan 14 14:00:43 loadbalancer01 b: Completed config sync all operation
    Jan 14 14:00:48 loadbalancer01 sod[998]: 010c0018:5: Standby
    Jan 14 14:01:10 loadbalancer01 sod[998]: 010c0019:5: Active
    

    I've never seen that happen when doing a b load before...
  • do you set tmm interface to auto negotiate or fixed speed?