Forum Discussion

rafaelbn_176840's avatar
rafaelbn_176840
Icon for Altocumulus rankAltocumulus
Nov 23, 2017

Viprion. Multiple blades and vCMP. Mirroring options.

Hello Devs! I read on the oficial training guide that when you use vCMP, you do the mirroring on a guest basis. That makes sense to me. But what if you have like a c2400 with 4x2150. Does the mir...
application delivery
LTM
TMOS
vcmp
viprion
  • Yann_Desmarest_'s avatar
    Yann_Desmarest_
    Apr 27, 2018

    Hello rafaelbn,

     

    If you configure Mirroring "within Cluster", it means that objects requiring mirroring (connection, persistence, apm, session tables, ...) will be synched between all blades configured for the Guest. This setting is for Mirroring only, it doesn't affect Sync and Failover features.

     

    It means that in case of a crash of blade 1 (hardware failure), your guest will continue to run on blade 2, then blade 3, etc.

     

    But be carreful, in case of a software failure (bug, memory leaks, ...), all blades can be affected. By experience, I recommand to run a Guest on 1 blade only and define a Sync/Failover cluster with another Guest on another Chassis.

     

    Hope it helps

     

    Yann

     

Yann_Desmarest's avatar
Yann_Desmarest
Icon for Cirrus rankCirrus

Hello rafaelbn,

 

If you configure Mirroring "within Cluster", it means that objects requiring mirroring (connection, persistence, apm, session tables, ...) will be synched between all blades configured for the Guest. This setting is for Mirroring only, it doesn't affect Sync and Failover features.

 

It means that in case of a crash of blade 1 (hardware failure), your guest will continue to run on blade 2, then blade 3, etc.

 

But be carreful, in case of a software failure (bug, memory leaks, ...), all blades can be affected. By experience, I recommand to run a Guest on 1 blade only and define a Sync/Failover cluster with another Guest on another Chassis.

 

Hope it helps

 

Yann

 

Yann_Desmarest's avatar
Yann_Desmarest
Icon for Cirrus rankCirrus
Apr 27, 2018

You are right.

 

You choose "within" so mirroring and session state is synched between all blades of the Guest but not with the Standby Unit.

 

You should change "min-up members" option to 1 to make sure that if blade 1 fails, you switch to blade 2.

 

The problem is that Mirroring still doesn't works with the Standby unit. The other issue is that Guest 1 will runs on blade 2 and Guest 2 runs on blade 1 which is not supported.

 

You should forget multi-bladed Guests and set Mirroring option to "between cluster", you will be in a supported scenario and Mirroring will works fine.

 

Hope it helps

 

Yann