01-14-2008 09:08 AM
We have two 6509s (12.2(17b)SXA) with WS-X6066-SLB-APC CSM modules running version 3.2(1)
Basically, what happened was the two modules sort of were not able to see each others so the standby one became active causing a collision.
Switch1 configs:
module ContentSwitchingModule 9
variable AGGREGATE_BACKUP_SF_STATE_TO_VS 1
!
ft group 10 vlan 53
priority 10
failover 3
preempt
Switch2 configs:
module ContentSwitchingModule 9
variable AGGREGATE_BACKUP_SF_STATE_TO_VS 1
!
ft group 10 vlan 53
priority 9
failover 3
preempt
Switch1#sh module contentSwitchingModule 9 ft detail
FT group 10, vlan 53
This box is active
priority 10, heartbeat 1, failover 3, preemption is on
total buffer count 6213, illegal state transitions 168448
receive buffers not committed 0, send buffers not committed 0
updates: sent 4, received 0, committed 0
coup msgs: sent 260, received 0
election msgs: sent 0, received 108
heartbeat msgs: sent 50503811, received 261
relinquish msgs: sent 0, received 131
conn replicate msgs: sent 0, received 0
conn refresh msgs: sent 0, received 0
conn reset msgs: sent 0, received 0
conn redundancy errors: msgs lost 0, msgs rejected 0
packets: total received 5384656, total dropped 0, duplicates 0
checksum failed 0, dumped 0, buffer unavailable 0
number of state updates in last 10 transfers:
0 0 0 0 0 0 0 0 0 0
Logs for Switch1
Jan 14 16:21:39.252: %CSM_SLB-4-REDUNDANCY_WARN: Module 9 FT warning: Active/Active Collision staying active
Jan 14 16:21:39.256: %CSM_SLB-4-TOPOLOGY: Module 9 warning: IP address conflict: ARP frame from 10.192.200.10 with MAC 00:0f:90:20:5d:93 received on VLAN 210
Switch2#sh mod contentSwitchingModule 9 ft detail
FT group 10, vlan 53
This box is in standby state
priority 9, heartbeat 1, failover 3, preemption is on
total buffer count 6213, illegal state transitions 0
receive buffers not committed 0, send buffers not committed 0
updates: sent 4, received 0, committed 0
coup msgs: sent 0, received 194
election msgs: sent 0, received 0
heartbeat msgs: sent 194, received 37692214
relinquish msgs: sent 97, received 0
conn replicate msgs: sent 0, received 0
conn refresh msgs: sent 0, received 0
conn reset msgs: sent 0, received 0
conn redundancy errors: msgs lost 0, msgs rejected 0
packets: total received 2016, total dropped 0, duplicates 0
checksum failed 0, dumped 0, buffer unavailable 0
number of state updates in last 10 transfers:
0 0 0 0 0 0 0 0 0 0
Logs for switch2
Jan 14 16:21:39.261: %CSM_SLB-6-REDUNDANCY_INFO: Module 9 FT info: State Transition Standby -> Active
Jan 14 16:21:39.265: %CSM_SLB-4-REDUNDANCY_WARN: Module 9 FT warning: Standby is Active now (no heartbeat from active unit)
Jan 14 16:21:39.269: %CSM_SLB-6-REDUNDANCY_INFO: Module 9 FT info: State Transition Active -> Standby
Is there any reason that will force the loss of heartbeats between the two switches?
Solved! Go to Solution.
01-23-2008 02:15 AM
you are running 3.2.1 which is very old.
You should consider an upgrade to a more recent version.
One possible explanation for your problem is this ddts :
CSCsk43903: CSM goes active-active over 828 days
Gilles.
01-22-2008 07:56 AM
First try rebooting the active/ Standby module to check if this fixes the prolem. Upgrading the standby has helped me fix the issue.
01-23-2008 02:15 AM
you are running 3.2.1 which is very old.
You should consider an upgrade to a more recent version.
One possible explanation for your problem is this ddts :
CSCsk43903: CSM goes active-active over 828 days
Gilles.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: