...
...
Figure 6.1 Single Independent Appliance as a DNS Server<place for figure>
Drawio |
---|
border | 1 |
---|
baseUrl | https://infoblox-docs.atlassian.net/wiki |
---|
diagramName | 6.1 |
---|
zoom | 1 |
---|
pageId | 22250680 |
---|
custContentId | 7083283 |
---|
lbox | 1 |
---|
contentVer | 1 |
---|
revision | 4 |
---|
|
Using primary and secondary name servers provides DNS protocol redundancy, and configuring two DHCP servers as DHCP failover peers provides DHCP protocol redundancy. However, you can only have hardware redundancy if you deploy appliances in an HA (high availability) pair. Should the active node in an HA pair fail, the passive node becomes active and begins serving data, as shown in Figure 6.2. For more information about HA pairs, see About HA Pairs.
Figure 6.2 Independent HA Pair
<place for figure>
Drawio |
---|
border | 1 |
---|
baseUrl | https://infoblox-docs.atlassian.net/wiki |
---|
diagramName | 6.2 |
---|
zoom | 1 |
---|
pageId | 22250680 |
---|
custContentId | 7935518 |
---|
lbox | 1 |
---|
contentVer | 1 |
---|
revision | 1 |
---|
|
Anchor |
---|
| System Manager GUI |
---|
| System Manager GUI |
---|
|
System Manager GUI When you deploy an independent appliance, you use System Manager to manage the appliance. Though other chapters in this guide contain information that assumes a Grid deployment and describes the Grid Manager GUI, most of the configuration procedures are applicable to an independent appliance, with the following differences:
...