For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

boneyard's avatar
boneyard
Icon for MVP rankMVP
Mar 26, 2012

intra / inter network (conection) mirroring on viprion

when reading the Viprion configuration guide it says that F5 advises to use intra (within cluster) network mirroring and that this is mutually exclusive from inter network (between clusters) mirroring.

 

 

i can understand part of the logic for a Viprion cluster with 2+ active slots. but when using just 1 slot is inter not the only logical choice? assuming you have two Viprion clusters in active / standby setup. or is it wise to just keep it at intra for when the 2nd slot is used?

 

 

i hope that at some point both options will be possible, i feel currently it is an annoying choice to make.

 

 

BTW: does anyone know the tmsh command to switch between intra (Within Cluster) and inter (Between Clusters) network mirroring?

 

 

config
design

5 Replies

  • Josh_41258's avatar
    Josh_41258
    Icon for Nimbostratus rankNimbostratus
    Apr 02, 2012
    I'm curious as well.. unfortunately, it is my observation that VIPRION is not adequately supported like the rest of the BIG-IP line. This is especially true for v11 + VIPRION.
  • Scott_Cracknell's avatar
    Scott_Cracknell
    Icon for Nimbostratus rankNimbostratus
    Mar 28, 2017

    I have just implemented this on my Viprion pair. I am running 12.1.1 with HF2.

     

    The tmsh command to implement this is as follows: modify sys db statemirror.clustermirroring value between

     

    [the default value is within]

     

    Use the following command to display the current value: list sys db statemirror.clustermirroring

     

  • Gregory_Thiell's avatar
    Gregory_Thiell
    Icon for Employee rankEmployee
    Mar 16, 2018

    Piotr Lewandowski - Yes, the network mirroring option "Within Cluster" / "Between Clusters" applies to vCMP guests.

     

    Note that:

     

    • "Within Cluster" is irrelevant for vCMP guests running on a single blade.
    • "Between Clusters" is irrelevant for standalone vCMP guests.
  • rafaelbn's avatar
    rafaelbn
    Icon for Cirrostratus rankCirrostratus
    May 20, 2018

    Hello guys!

    I know this thread is old, but I'm leaving my findings here as a reference.

    I was able to double-check this thing on production environment. We had 2 2400 VIPRION chassis running vCMP. On the chassis, the sys db was configured with between:

    root@(NDCLPBIPPRD01)(cfg-sync Standalone)(/S1-green-P:Active)(/Common)(tmos) list sys db statemirror.clustermirroring
sys db statemirror.clustermirroring {
    value "between"
}

    But the vCMP was the default with within:

    root@(NDCLPBIPPRD-SAS01)(cfg-sync In Sync)(/S1-green-P:Active)(/Common)(tmos) list sys db statemirror.clustermirroring
sys db statemirror.clustermirroring {
    value "within"
}

    As expected, the connection mirroring was not happening between the vCMPs.

    root@(NDCLPBIPPRD-SAS02)(cfg-sync In Sync)(/S1-green-P:Standby)(/Common)(tmos) show sys connection type mirror
Sys::Connections
Total records returned: 0

    When I changed the sys db to mirror between and synced both vCMPs, everything worked like it supposed to.

    root@(NDCLPBIPPRD-SAS01)(cfg-sync In Sync)(/S1-green-P:Active)(/Common)(tmos) modify sys db statemirror.clustermirroring value between
root@(NDCLPBIPPRD-SAS01)(cfg-sync In Sync)(/S1-green-P:Active)(/Common)(tmos)
root@(NDCLPBIPPRD-SAS01)(cfg-sync Changes Pending)(/S1-green-P:Active)(/Common)(tmos)
root@(NDCLPBIPPRD-SAS01)(cfg-sync Changes Pending)(/S1-green-P:Active)(/Common)(tmos) run cm config-sync to-group DG-SAS

root@(NDCLPBIPPRD-SAS02)(cfg-sync In Sync)(/S1-green-P:Standby)(/Common)(tmos) show sys connection type mirror
Sys::Connections
10.29.11.110:36600  10.29.4.10:636      10.29.11.110:36600  10.29.4.10:636      tcp  2  (slot/tmm: 1/0)  none
10.29.11.39:28641   172.21.0.245:111    10.29.11.39:28641   172.21.0.245:111    tcp  2  (slot/tmm: 1/0)  none
10.29.11.76:41594   172.25.36.52:1521   10.29.11.76:41594   172.25.36.52:1521   tcp  2  (slot/tmm: 1/0)  none
10.29.11.70:29523   10.29.11.36:6882    10.29.11.70:29523   10.29.11.36:6882    tcp  2  (slot/tmm: 1/0)  none
10.29.11.48:36323   172.21.0.246:111    10.29.11.48:36323   172.21.0.246:111    tcp  2  (slot/tmm: 1/0)  none
10.29.11.76:22708   172.25.36.49:1521   10.29.11.76:22708   172.25.36.49:1521   tcp  2  (slot/tmm: 1/0)  none
10.29.11.44:21629   172.21.0.247:111    10.29.11.44:21629   172.21.0.247:111    tcp  2  (slot/tmm: 1/0)  none

    So... Long history short, sys db statemirror.clustermirroring is per chassis AND per vCMP.

    Hope this helps!

    Cheers! Rafael