SN2700 MLAG Bug ?

Hi,

we encountered a problem with our 2x2700 Stack that some machines were not pingable anymore and it seems the log showed the following errors.

switch1:

Nov 26 10:06:39 d10-mx4 mlagd[7691]: TID 140383926970112: [mlagd.WARNING]: [STP_MANAGER.NOTICE] Block BPDU TX on interface [29010]

Nov 26 10:06:39 d10-mx4 mlagd[7691]: TID 140383926970112: [mlagd.WARNING]: [STP_MANAGER.NOTICE] Block BPDU TX on interface [29011]

Nov 26 10:06:39 d10-mx4 mlagd[7691]: TID 140383926970112: [mlagd.WARNING]: [STP_MANAGER.NOTICE] Block BPDU TX on interface [29012]

Nov 26 10:06:39 d10-mx4 mlagd[7691]: TID 140383926970112: [mlagd.WARNING]: [STP_MANAGER.NOTICE] Block BPDU TX on interface [29013]

Nov 26 10:06:39 d10-mx4 mlagd[7691]: TID 140383926970112: [mlagd.WARNING]: [STP_MANAGER.NOTICE] Block BPDU TX on interface [29014]

Nov 26 10:06:39 d10-mx4 mlagd[7691]: TID 140383926970112: [mlagd.WARNING]: [STP_MANAGER.NOTICE] Block BPDU TX on interface [29015]

Nov 26 10:06:39 d10-mx4 mlagd[7691]: TID 140383926970112: [mlagd.WARNING]: [STP_MANAGER.NOTICE] Block BPDU TX on interface [29016]

Switch 2:

Nov 26 10:23:04 d10-mx5 mlagd[7775]: TID 140152136709888: [mlagd.NOTICE]: [MLAG_MAC_SYNC_PEER_MANAGER.NOTICE] Need to mark the MACs as DENY, cnt:0 < record_num:81

Nov 26 10:23:04 d10-mx5 mlagd[7775]: TID 140152136709888: [mlagd.NOTICE]: [MLAG_MAC_SYNC_PEER_MANAGER.NOTICE] Failed to grow the pool size, err -12

Nov 26 10:23:04 d10-mx5 mlagd[7775]: TID 140152136709888: [mlagd.NOTICE]: [MLAG_MAC_SYNC_PEER_MANAGER.NOTICE] Need to mark the MACs as DENY, cnt:0 < record_num:81

Nov 26 10:23:04 d10-mx5 mlagd[7775]: TID 140152136709888: [mlagd.NOTICE]: [MLAG_MAC_SYNC_PEER_MANAGER.NOTICE] Failed to grow the pool size, err -12

Nov 26 10:23:04 d10-mx5 mlagd[7775]: TID 140152136709888: [mlagd.NOTICE]: [MLAG_MAC_SYNC_PEER_MANAGER.NOTICE] Need to mark the MACs as DENY, cnt:0 < record_num:81

Nov 26 10:23:04 d10-mx5 mlagd[7775]: TID 140152136709888: [mlagd.NOTICE]: [MLAG_MAC_SYNC_PEER_MANAGER.NOTICE] Failed to grow the pool size, err -12

Nov 26 10:23:04 d10-mx5 mlagd[7775]: TID 140152136709888: [mlagd.NOTICE]: [MLAG_MAC_SYNC_PEER_MANAGER.NOTICE] Need to mark the MACs as DENY, cnt:0 < record_num:81

Nov 26 10:23:04 d10-mx5 mlagd[7775]: TID 140152136709888: [mlagd.NOTICE]: [MLAG_MAC_SYNC_PEER_MANAGER.NOTICE] Failed to grow the pool size, err -12

Nov 26 10:23:04 d10-mx5 mlagd[7775]: TID 140152136709888: [mlagd.NOTICE]: [MLAG_MAC_SYNC_PEER_MANAGER.NOTICE] Need to mark the MACs as DENY, cnt:0 < record_num:81

Nov 26 10:23:04 d10-mx5 mlagd[7775]: TID 140152136709888: [mlagd.NOTICE]: [MLAG_MAC_SYNC_PEER_MANAGER.NOTICE] Failed to grow the pool size, err -12

Nov 26 10:23:04 d10-mx5 mlagd[7775]: TID 140152136709888: [mlagd.NOTICE]: [MLAG_MAC_SYNC_PEER_MANAGER.NOTICE] Need to mark the MACs as DENY, cnt:0 < record_num:81

Nov 26 10:23:04 d10-mx5 mlagd[7775]: TID 140152136709888: [mlagd.NOTICE]: [MLAG_MAC_SYNC_PEER_MANAGER.NOTICE] Failed to grow the pool size, err -12

Nov 26 10:23:04 d10-mx5 mlagd[7775]: TID 140152136709888: [mlagd.NOTICE]: [MLAG_MAC_SYNC_PEER_MANAGER.NOTICE] Need to mark the MACs as DENY, cnt:0 < record_num:81

Nov 26 10:23:04 d10-mx5 mlagd[7775]: TID 140152136709888: [mlagd.NOTICE]: [MLAG_MAC_SYNC_PEER_MANAGER.NOTICE] Failed to grow the pool size, err -12

Nov 26 10:23:04 d10-mx5 mlagd[7775]: TID 140152136709888: [mlagd.NOTICE]: [MLAG_MAC_SYNC_PEER_MANAGER.NOTICE] Need to mark the MACs as DENY, cnt:0 < record_num:81

Nov 26 10:23:04 d10-mx5 mlagd[7775]: TID 140152136709888: [mlagd.NOTICE]: [MLAG_MAC_SYNC_PEER_MANAGER.NOTICE] Failed to grow the pool size, err -12

Nov 26 10:23:04 d10-mx5 mlagd[7775]: TID 140152136709888: [mlagd.NOTICE]: [MLAG_MAC_SYNC_PEER_MANAGER.NOTICE] Need to mark the MACs as DENY, cnt:0 < record_num:81

Nov 26 10:23:04 d10-mx5 mlagd[7775]: TID 140152136709888: [mlagd.NOTICE]: [MLAG_MAC_SYNC_PEER_MANAGER.NOTICE] Failed to grow the pool size, err -12

Nov 26 10:23:04 d10-mx5 mlagd[7775]: TID 140152136709888: [mlagd.NOTICE]: [MLAG_MAC_SYNC_PEER_MANAGER.NOTICE] Need to mark the MACs as DENY, cnt:0 < record_num:81

We evacuated all vmware hosts on the switch and updates 3.8.2004 to 3.8.2008 but id like to know the source of the problem…