Forum Discussion
jan_de_wachter_
Nimbostratus
NimbostratusLTM show sys ha-mirror command
Hi,
We are facing persistence mirroring problems (persistency is not mirrored) and opened a case with F5.
I had to do following command: tmsh show sys ha-mirror
Giving following result:
--...
Greetings, This seems a newer and not very well documented command, so I took a few minutes to see how this works. I don't think mirroring will work for you based on what you've shown and my testing. Here are the results:
I initially had the "closed" status as well. I set up mirroring and it did not work. I then realized there were no mirroring addresses defined in my CM config. To check:
tmsh list cm device mirror-ip cm device lc.one.test.net { mirror-ip 10.12.23.120 } cm device lc.two.testnet { mirror-ip 10.12.23.121 }Then the status changed to the following:
---------------------------------------------------------------------------------------------------------------- Sys::HA Mirror Status ---------------------------------------------------------------------------------------------------------------- Traffic Group TMM Primary Secondary Aborts Overflows Errors Buffered L4 Mirror L7 Mirror L7 Failed ---------------------------------------------------------------------------------------------------------------- traffic-group-1 [0.0] delay closed 0 0 7 0 0 0 0 traffic-group-1 [0.1] delay closed 0 0 7 0 0 0 0Still no mirroring occurring. I then realized that each LTM had a different number of CPUs. So I corrected that and finally mirroring began to work:
show sys connection type mirror Sys::Connections 10.12.23.139:55523 10.12.23.137:22 10.12.23.121:55523 10.12.23.27:22 tcp 1 (tmm: 1) none Total records returned: 1------------------------------------------------------------------------------------------------------------------ Sys::HA Mirror Status ------------------------------------------------------------------------------------------------------------------ Traffic Group TMM Primary Secondary Aborts Overflows Errors Buffered L4 Mirror L7 Mirror L7 Failed ------------------------------------------------------------------------------------------------------------------ traffic-group-1 [0.0] connected closed 0 0 2 0 0 0 0 traffic-group-1 [0.1] connected closed 0 0 2 0 0 0 0 traffic-group-1 [0.2] connected closed 0 0 2 0 0 0 0 traffic-group-1 [0.3] connected closed 0 0 2 0 0 0 0
Greetings, This seems a newer and not very well documented command, so I took a few minutes to see how this works. I don't think mirroring will work for you based on what you've shown and my testing. Here are the results:
I initially had the "closed" status as well. I set up mirroring and it did not work. I then realized there were no mirroring addresses defined in my CM config. To check:
tmsh list cm device mirror-ip
cm device lc.one.test.net {
mirror-ip 10.12.23.120
}
cm device lc.two.testnet {
mirror-ip 10.12.23.121
}
Then the status changed to the following:
----------------------------------------------------------------------------------------------------------------
Sys::HA Mirror Status
----------------------------------------------------------------------------------------------------------------
Traffic Group TMM Primary Secondary Aborts Overflows Errors Buffered L4 Mirror L7 Mirror L7 Failed
----------------------------------------------------------------------------------------------------------------
traffic-group-1 [0.0] delay closed 0 0 7 0 0 0 0
traffic-group-1 [0.1] delay closed 0 0 7 0 0 0 0
Still no mirroring occurring. I then realized that each LTM had a different number of CPUs. So I corrected that and finally mirroring began to work:
show sys connection type mirror
Sys::Connections
10.12.23.139:55523 10.12.23.137:22 10.12.23.121:55523 10.12.23.27:22 tcp 1 (tmm: 1) none
Total records returned: 1
------------------------------------------------------------------------------------------------------------------
Sys::HA Mirror Status
------------------------------------------------------------------------------------------------------------------
Traffic Group TMM Primary Secondary Aborts Overflows Errors Buffered L4 Mirror L7 Mirror L7 Failed
------------------------------------------------------------------------------------------------------------------
traffic-group-1 [0.0] connected closed 0 0 2 0 0 0 0
traffic-group-1 [0.1] connected closed 0 0 2 0 0 0 0
traffic-group-1 [0.2] connected closed 0 0 2 0 0 0 0
traffic-group-1 [0.3] connected closed 0 0 2 0 0 0 0
jan_de_wachter_Nimbostratus
NimbostratusKevin,
Thanks for your reaction.
I controlled our settings, and think I am still missing something, but I dont kvow what 🙂
[HFL5801@f5mechl1-test:/S1-green-P:Active:In Sync] ~ tmsh list cm device mirror-ip
cm device f5mechl1-test.msnet.railb.be {
mirror-ip 192.168.1.24
}
cm device f5mechl2-test.msnet.railb.be {
mirror-ip 192.168.1.25
}
[HFL5801@f5mechl1-test:/S1-green-P:Active:In Sync] ~ tmsh show sys ha-mirror
----------------------------------------------------------------------------------------------------------------
Sys::HA Mirror Status
----------------------------------------------------------------------------------------------------------------
Traffic Group TMM Primary Secondary Aborts Overflows Errors Buffered L4 Mirror L7 Mirror L7 Failed
----------------------------------------------------------------------------------------------------------------
traffic-group-1 [0.0] closed closed 0 0 0 0 0 0 0
On my standby F5:
[HFL5801@f5mechl2-test:/S1-green-P:Standby:In Sync] ~ tmsh list cm device mirror-ip
cm device f5mechl1-test.msnet.railb.be {
mirror-ip 192.168.1.24
}
cm device f5mechl2-test.msnet.railb.be {
mirror-ip 192.168.1.25
}
[HFL5801@f5mechl2-test:/S1-green-P:Standby:In Sync] ~ tmsh show sys ha-mirror
----------------------------------------------------------------------------------------------------------------
Sys::HA Mirror Status
----------------------------------------------------------------------------------------------------------------
Traffic Group TMM Primary Secondary Aborts Overflows Errors Buffered L4 Mirror L7 Mirror L7 Failed
----------------------------------------------------------------------------------------------------------------
traffic-group-1 [0.0] closed closed 0 0 2 0 0 0 0
The addresses specified are the non-floating self-ip of the common partition. Is this sufficient, or do we need to specify also the self-ip addresses of the other partitions?
Thanks !