cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
434
Views
0
Helpful
2
Replies

CSM Sticky replication - how do you know if it is working?

CCC4046_2
Level 1
Level 1

I have two CSMs in a fault tolerant configuration.

If I do a "show module csm 2 conn" on the passive CSM, I can see the connections replicated between the CSMs.

However if I do a "show module csm 2 sticky" on the passive CSM, I cannot see the sticky data in the table. Is this normal, or is the replication not working?

I know I tested it in the lab, and I can't remember if I could ever see the sticky information in the passive CSM.

The config is below:

module ContentSwitchingModule 2

ft group 1 vlan 3089

priority 160 alt 150

heartbeat-time 1

failover 5

preempt

!

vlan 403 client

ip address 10.12.3.250 255.255.255.0 alt 10.12.3.249 255.255.255.0

gateway 10.12.3.1

!

vlan 404 server

ip address 10.12.3.250 255.255.255.0 alt 10.12.3.249 255.255.255.0

!

probe PB_FIN_PRD http

recover 6

request method get url /local/SRV_Avail.html

expect status 200 299

interval 5

retries 6

failed 30

port 8007

!

probe PB_FIN_TST http

recover 6

request method get url /local/SRV_Avail.html

expect status 200 299

interval 5

retries 6

failed 30

port 8001

!

serverfarm FIN_WEB_PRD

nat server

no nat client

real 10.12.3.5

health probe PB_FIN_PRD

inservice

real 10.12.3.6

health probe PB_FIN_PRD

inservice

!

serverfarm FIN_WEB_TST

nat server

no nat client

real 10.12.3.9

health probe PB_FIN_TST

inservice

!

sticky 1 netmask 255.255.255.255 timeout 30

!

sticky 2 netmask 255.255.255.255 timeout 30

!

vserver FIN_VSERVR_PRD

virtual 10.12.3.101 any

serverfarm FIN_WEB_PRD

sticky 30 group 1

replicate csrp sticky

replicate csrp connection

persistent rebalance

inservice

!

vserver FIN_VSERVR_TST

virtual 10.12.3.102 any

serverfarm FIN_WEB_TST

sticky 30 group 2

replicate csrp sticky

replicate csrp connection

persistent rebalance

inservice

2 Replies 2

CCC4046_2
Level 1
Level 1

Figured it out myself. I found that the sticky replication stopped after I did a config synch. This appears to be related to a known bug. I upgraded the code and it is now working.

Which CSM version you have? We have CSM V3.2. Will it have the same bug? Thx.