Forum Discussion
LTM show sys ha-mirror command
- Jan 17, 2017
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
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
One final point; the Primary and Secondary are referring to the primary and secondary mirroring IP addresses:
tmsh modify cm device lc.kinch.net mirror-ip 1.1.1.1 mirror-secondary-ip 2.2.2.2
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] connected connected 0 0 2 0 0 0 0
traffic-group-1 [0.1] connected connected 0 0 2 0 0 0 0
traffic-group-1 [0.2] connected connected 0 0 2 0 0 0 0
traffic-group-1 [0.3] connected connected 0 0 2 0 0 0 0
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com