White Papers
Table Of Contents
- 1 Introduction
- 1 Introduction
- 1.1
- 1.1
- 1.1
- 1.1 Audience
- 1.1 Audience
- 1.1 Audience
- 1.1
- 1.1
- 1.1
- 1.1
- 1.1
- 1.1
- 1.1
- 1.1
- 1.1
- 1.1
- 1.1
- 1.1
- 1.1
- 1.1
- 1.1
- 1.1
- 1.1
- 1.1
- 1.1
- 1.1
- 1.1
- 1.1
- 1.1
- 1.1
- 1.2 Applicable scenario to configure dual-NIC
- 1.2 Applicable scenario to configure dual-NIC
- 1.2 Applicable scenario to configure dual-NIC
- 1.3 Possible Multi-NIC configuration
- 1.3 Possible Multi-NIC configuration
- 1.3 Possible Multi-NIC configuration
- 1
- 1
- 1
- 1
- 1
- 1
- 1
- 1
- 1
- 1
- 1
- 1
- 1
- 1
- 1
- 1
- 1
- 1
- 1
- 1
- 1
- 1
- 1
- 1
- 1
- 1
- 1
- 1
- 1
- 1
- 1
- 1
- 1
- 2 Configure dual-NIC in OMIVV
- 2 Configure dual-NIC in OMIVV
- 2 Configure dual-NIC in OMIVV
- 2.1 Configure dual-NIC with multiple subnets
- 2.1 Configure dual-NIC with multiple subnets
- 2.1 Configure dual-NIC with multiple subnets
- 1.1
- 1.1
- 1.1
- 1.1
- 1.1
- 1.1
- 2.2 Configure dual-NIC managed with FQDN on both the network with different DNS
- 2.2 Configure dual-NIC managed with FQDN on both the network with different DNS
- 2.2 Configure dual-NIC managed with FQDN on both the network with different DNS
- 1
- 1
- 1
- 1
- 1
- 1
- 1
- 1
- 1
- 3 Change in area in OMIVV due to dual-NIC configuration
- 3 Change in area in OMIVV due to dual-NIC configuration
- 3 Change in area in OMIVV due to dual-NIC configuration
- 4 Network Port information
- 4.1 OMIVV to in-band network
- 4.1 OMIVV to in-band network
- 4.1 OMIVV to in-band network
- 4.2 OMIVV to out-of-band network
- 4.2 OMIVV to out-of-band network
- 4.2 OMIVV to out-of-band network
- 1.1
- 1.1
- 4.3 OMIVV to Internet
- 4.3 OMIVV to Internet
- 1.1
- 1.1
- 1.1
- 4.3 OMIVV to Internet
- 4.3 OMIVV to Internet
- 4.3 OMIVV to Internet
- 5 Conclusion
- 6 Technical support and resources
17 Deploying and configuring OMIVV in a dual-NIC environment
Figure 16: Routing table
2.2 Configure dual-NIC managed with FQDN on both the network with
different DNS
This section describes the dual-NIC configuration, where both vSphere and out-of-band are managed by FQDN
using IP. However, CentOS allows you to configure maximum three DNS server primary, secondary, and
ternary. The CentOS reaches the second DNS server, only when the first DNS server is down or and not
reachable and the same applies to third DNS server.
In general, DNS server will send some invalid default IP when it cannot resolve the FQDN. In such cases,
OMIVV will consider it as FQDN resolved IP and try to process the invalid IP.
To avoid such problems and continue managing with FQDN from different isolated networks, there must be a
common DNS sever which is configured to synchronize with the DNS servers from both vSphere management
and Out of Band management networks.
This can be done by configuring the forwarder DNS server of both, so that, when the DNS is not able to resolve
the FQDN it forwards the request to the forwarder DNS server and try to get the actual IP.
Figure 17: Dual-NIC configuration, where both vSphere and out-of-band are managed by FQDN using IP