The LACP timing which should be used on this .
- Possible values are fast, slow and a
- positive number of milliseconds. By default slow is
- used. When configured to be fast LACP heartbeats are
- requested at a rate of once per second causing connectivity
- problems to be detected more quickly. In slow mode,
- heartbeats are requested at a rate of once every 30 seconds.
-
- Users may manually set a heartbeat transmission rate to increase
- the fault detection speed further. When manually set, OVS expects
- the partner switch to be configured with the same transmission
- rate. Manually setting lacp-time to something other
- than fast or slow is not supported by the
- LACP specification.
+ By default slow is used. When configured to be
+ fast LACP heartbeats are requested at a rate of once
+ per second causing connectivity problems to be detected more
+ quickly. In slow mode, heartbeats are requested at a
+ rate of once every 30 seconds.
false.
-
+ Hypervisors may sometimes have more than one interface associated
+ with a given , only one of
+ which is actually in use at a given time. For example, in some
+ circumstances XenServer has both a ``tap'' and a ``vif'' interface
+ for a single , but only
+ uses one of them at a time. A hypervisor that behaves this way must
+ mark the currently in use interface active and the
+ others inactive. A hypervisor that never has more than
+ one interface for a given
+ may mark that interface active or omit entirely.
+
+ During VM migration, a given might transiently be marked active on
+ two different hypervisors. That is, active means that
+ this is the active
+ instance within a single hypervisor, not in a broader scope.
+