Forum Discussion

Brian_Gibson_30's avatar
Brian_Gibson_30
Icon for Nimbostratus rankNimbostratus
May 23, 2016

disabling a blade in a Viprion expected behavior

Hey folks,

 

We have a blade in our Viprion chassis that rebooted earlier and we are concerned it will do it again.

 

If we mark the blade disabled, what happens to existing connections on the blade? Will the blade keep those connections up until they close?

 

2 Replies

  • nathe's avatar
    nathe
    Icon for Cirrocumulus rankCirrocumulus

    Brian, when you disable the blade i believe the interfaces are downed so traffic will cease to get to the guest itself and, I imagine, connections will drop. That's if the guest is single blade of course. If the guest is on multiple blades then if you've configured intra-cluster mirroring at a guest level and then virtual server connection mirroring then this should keep the connections up and running via the other blade. The VS used to have to be a fastL4 type, would need to confirm if this is still the case.

     

    If you have multiple hosts and the guest has a peer on a second host then, with inter-cluster mirroring, if the device fails over then the connections should, again, be persisted across the blades. Not sure if only fastl4 VSs are still required.

     

    Be good to get confirmation on that.

     

    Anyway, hope this helps,

     

    N

     

  • I would recommend that you plan for total loss of connections on the blade that is being disabled.

     

    Mirroring involves - Connection & Persistence Mirroring. For Viprion Systems, there is intra & inter cluster mirroring that adds another layer of complexity.

     

    Intra Clustering mirroring doesn't work for L7 traffic (10.x) Inter Clustering mirroring will only work when you have 2 chassis with identical number of blades in the identical slots.

     

    Given, the number of variables, I would say you should plan for total loss of connection on that blade.

     

    Link for Viprion Mirroring (10.x)