Saucepan

User Tools

Site Tools

Trace: • traffic_generator • userid • zone_rename • install_gitolite • grid_join • wireshark • ping • ssh • colour • install_ubuntu20.04
infoblox_nios:high_availability

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
infoblox_nios:high_availability [2025/12/09 13:23] – [NSX] bstaffordinfoblox_nios:high_availability [2025/12/15 15:30] (current) – bstafford
Line 6: Line 6:
 General blog article [[https://blogs.infoblox.com/company/power-of-three-for-low-cost-ha-business-continuity/|here]] on using a standalone appliance and a HA pair. General blog article [[https://blogs.infoblox.com/company/power-of-three-for-low-cost-ha-business-continuity/|here]] on using a standalone appliance and a HA pair.
  
 +===== Changing HA Pair Types =====
 +Cutting over from HA physical to HA virtual. When I cut the passive to vNIOS, it did not change the Member Type to Virtual NIOS. After I cut the second member of the HA pair, the Member Type changed to Virtual NIOS without intervention.
 ===== DFP ===== ===== DFP =====
 When using DFP, NIOS uses the LAN1 port to establish DoT on TCP-443 to Infoblox Anycast. This is true EVEN IF THE NIOS is HA. NIOS will not use the HA VIP for TCP-443. However, any plaintext queries will come from the HA VIP. When using DFP, NIOS uses the LAN1 port to establish DoT on TCP-443 to Infoblox Anycast. This is true EVEN IF THE NIOS is HA. NIOS will not use the HA VIP for TCP-443. However, any plaintext queries will come from the HA VIP.
infoblox_nios/high_availability.1765286581.txt.gz · Last modified: by bstafford