Searched refs:Failover (Results 1 – 9 of 9) sorted by relevance
| /openbmc/bmcweb/redfish-core/include/generated/enums/ |
| H A D | redundancy.hpp | 10 Failover, enumerator
19 {RedundancyType::Failover, "Failover"},
|
| /openbmc/qemu/docs/ |
| H A D | COLO-FT.txt | 51 | | | |Failover| | | |Failover| | | |
99 Checkpoint/Failover Controller:
241 6. Failover test
242 You can kill one of the VMs and Failover on the surviving VM:
244 If you killed the Secondary, then follow "Primary Failover". After that,
247 If you killed the Primary, then follow "Secondary Failover". After that,
250 == Primary Failover ==
262 == Secondary Failover ==
|
| H A D | block-replication.txt | 222 After Failover:
|
| /openbmc/linux/Documentation/devicetree/bindings/net/dsa/ |
| H A D | brcm,sf2.yaml | 70 description: if present indicates that the switch supports Failover Control
|
| /openbmc/intel-ipmi-oem/ |
| H A D | ipmi-allowlist.conf | 337 0x3e:0x40:0x7f7f //<Intel Managed Data Region>:<Set Get LAN Failover>
|
| /openbmc/qemu/qapi/ |
| H A D | net.json | 959 # negotiation. Failover primary devices which were hidden (not
|
| /openbmc/linux/drivers/net/ |
| H A D | Kconfig | 629 tristate "Failover driver"
|
| /openbmc/linux/Documentation/networking/ |
| H A D | bonding.rst | 98 13.1 Link Establishment and Failover Delays
2604 13.1 Link Establishment and Failover Delays
2637 Failover may be delayed via the downdelay bonding module option.
|
| /openbmc/ipmitool/contrib/ |
| H A D | oem_ibm_sel_map | 2 …umber","Failed Memory Card","Spare Memory Card","0x00","Memory Mirrored Failover Occurred - System…
|