Lightboard Lessons: Intro to VIPRION

The F5 BIG-IP platform has tremendous flexibility, offering virtual editions and a line of appliances and chassis. In this episode of Lightboard Lessons, we’ll introduce the chassis platform, which w...
Published May 24, 2017
Version 1.0
application delivery
BIG-IP
lbl
viprion
dragonflymr's avatar
dragonflymr
Icon for Cirrostratus rankCirrostratus
May 29, 2017

Hi,

 

Nice article, but a bit basic :-)

 

If possible I would like to such topics to be considered:

 

  • How exactly DAG works, especially depending on mode, how it is related to other components like HSB or TMM
  • What is packet flow depending on VLAN and interface configuration - you mentioned difference between connecting interface from one blade and connecting interfaces from all blades as trunk. How then traffic flow looks like considering LACP hashing (guess it will direct traffic to given interface in the trunk), then DAG, HSB, backplane, TMM etc. How traffic is distributed in case of multi blade vHost.
  • VLAN config - mentioned best practice was to create trunk and include interfaces from all blades, then use trunk when configuring VLAN. Other possible option is create VLAN containing interfaces from all blades - if I am not wrong - is that useful config ot not at all?
  • HA - what is the reason that HA can be only configured between vHosts running on different Viprions, not between vHosts running on one Viprion - sure not best HA but I am still curious why not possible
  • Very interesting topic for me is what are limitation when using different hardware when creating DSC. What exactly will not work when next device is different hardware (like preferred is Viprion and next s appliance or VE). If I am not wrong mirroring will not work?
  • Not directly related but still... what subsystems are not used when PVA is enabled, what is exatct flow of packets in this case, related to PVA mode.

Piotr