Forum Discussion

7 Replies

  • Could someone please define HA timers value? For eg. Persistence connection transfer timer from one peer to another one. And so on.

     

    i do not think it is configurable. if i am not wrong, i understand data is synchronized to standby unit immediately.

     

  • Does it mean it is realtime?

     

    yes, that is what i understand. if you have a pair, you may run tcpdump on standby unit and could see packet there.

     

  • Perfect! That could be the best possible scenario to test this.

     

    Thanks for your help! Cheers!

     

  • My understanding was that there session table is what that is updated between the HA paired devices. The packet capture would not work as the floating IP would be hosted by the active device. Please correct me if that is wrong.

     

  • e.g.

     configuration
    
    root@(ve11a)(cfg-sync In Sync)(Active)(/Common)(tmos) list ltm virtual bar
    ltm virtual bar {
        destination 172.28.20.111:80
        ip-protocol tcp
        mask 255.255.255.255
        mirror enabled
        pool foo
        profiles {
            http { }
            tcp { }
        }
        source 0.0.0.0/0
        source-address-translation {
            type automap
        }
        vs-index 23
    }
    root@(ve11a)(cfg-sync In Sync)(Active)(/Common)(tmos) list ltm pool foo
    ltm pool foo {
        members {
            200.200.200.101:80 {
                address 200.200.200.101
            }
        }
    }
    
     traffic-group
    
    root@(ve11a)(cfg-sync In Sync)(Active)(/Common)(tmos) show cm traffic-group
    
    ---------------------------------------------------------
    CM::Traffic-Group
    Name                      Device          Status   Next
                                                       Active
    ---------------------------------------------------------
    traffic-group-1           ve11a.acme.com  active   false
    traffic-group-1           ve11b.acme.com  standby  false
    traffic-group-1           ve11c.acme.com  standby  true
    traffic-group-local-only  -               -        -
    
     active
    
    [root@ve11a:Active:In Sync] config  tcpdump -nni 0.0 port 80
    tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
    listening on 0.0, link-type EN10MB (Ethernet), capture size 96 bytes
    23:03:55.826879 IP 172.28.20.17.34059 > 172.28.20.111.80: S 62319:62319(0) win 5840 
    23:03:55.827020 IP 172.28.20.111.80 > 172.28.20.17.34059: S 3947983183:3947983183(0) ack 62320 win 4380 
    23:03:55.828778 IP 172.28.20.17.34059 > 172.28.20.111.80: . ack 1 win 5840
    23:03:55.828790 IP 172.28.20.17.34059 > 172.28.20.111.80: P 1:157(156) ack 1 win 5840
    23:03:55.828886 IP 200.200.200.14.34059 > 200.200.200.101.80: S 4138377900:4138377900(0) win 4380 
    23:03:55.828901 IP 172.28.20.111.80 > 172.28.20.17.34059: . ack 157 win 4536
    23:03:55.830747 IP 200.200.200.101.80 > 200.200.200.14.34059: S 3675627561:3675627561(0) ack 4138377901 win 5840 
    23:03:55.830793 IP 200.200.200.14.34059 > 200.200.200.101.80: . ack 1 win 4380
    23:03:55.830806 IP 200.200.200.14.34059 > 200.200.200.101.80: P 1:157(156) ack 1 win 4380
    23:03:55.833637 IP 200.200.200.101.80 > 200.200.200.14.34059: . ack 157 win 6432
    23:03:55.834892 IP 200.200.200.101.80 > 200.200.200.14.34059: P 1:244(243) ack 157 win 6432
    23:03:55.834948 IP 172.28.20.111.80 > 172.28.20.17.34059: P 1:244(243) ack 157 win 4536
    23:03:55.834953 IP 200.200.200.14.34059 > 200.200.200.101.80: . ack 244 win 4623
    23:03:55.836948 IP 172.28.20.17.34059 > 172.28.20.111.80: . ack 244 win 6432
    23:03:55.836964 IP 172.28.20.17.34059 > 172.28.20.111.80: F 157:157(0) ack 244 win 6432
    23:03:55.837011 IP 172.28.20.111.80 > 172.28.20.17.34059: . ack 158 win 4536
    23:03:55.837018 IP 200.200.200.14.34059 > 200.200.200.101.80: F 157:157(0) ack 244 win 4623
    23:03:55.838686 IP 200.200.200.101.80 > 200.200.200.14.34059: F 244:244(0) ack 158 win 6432
    23:03:55.838732 IP 200.200.200.14.34059 > 200.200.200.101.80: . ack 245 win 4623
    23:03:55.838740 IP 172.28.20.111.80 > 172.28.20.17.34059: F 244:244(0) ack 158 win 4536
    23:03:55.840642 IP 172.28.20.17.34059 > 172.28.20.111.80: . ack 245 win 6432
    
     standby
    
    [root@ve11c:Standby:In Sync] config  tcpdump -nni 0.0 port 80
    tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
    listening on 0.0, link-type EN10MB (Ethernet), capture size 96 bytes
    23:03:55.828927 IP 172.28.20.17.34059 > 172.28.20.111.80: S 62319:62319(0) win 5840 
    23:03:55.830911 IP 172.28.20.17.34059 > 172.28.20.111.80: . ack 3947983184 win 5840
    23:03:55.830940 IP 172.28.20.17.34059 > 172.28.20.111.80: P 0:156(156) ack 1 win 5840
    23:03:55.832920 IP 200.200.200.101.80 > 200.200.200.14.34059: S 3675627561:3675627561(0) ack 4138377901 win 5840 
    23:03:55.834772 IP 200.200.200.101.80 > 200.200.200.14.34059: . ack 157 win 6432
    23:03:55.836860 IP 200.200.200.101.80 > 200.200.200.14.34059: P 1:244(243) ack 157 win 6432
    23:03:55.838676 IP 172.28.20.17.34059 > 172.28.20.111.80: . ack 244 win 6432
    23:03:55.838698 IP 172.28.20.17.34059 > 172.28.20.111.80: F 156:156(0) ack 244 win 6432
    23:03:55.840649 IP 200.200.200.101.80 > 200.200.200.14.34059: F 244:244(0) ack 158 win 6432
    23:03:55.842863 IP 172.28.20.17.34059 > 172.28.20.111.80: . ack 245 win 6432