Hello, my name is Ted. I'm a senior engineer with Dell EMC in the Systems Management Group.
I'd like to welcome you to our video about OMIVV dual home configuration.
Multi-home networking configuration for OMIVV is specifically designed
for implementations where connectivity between multiple management networks is
required. I'm going to show you some common multi-home configurations.
In scenario 1 OMIVV is deployed in a network where in band management
and out of band management are isolated and cannot communicate with one another.
Scenario two is where OMIVV is deployed in a network where there are two vCenters,
each deployed in their own isolated network each containing both
in-band and out-of-band management networks.
Scenario three: OMIVV is deployed in a network with two vCenters where they're each deployed
in their own isolated in-band network and all out-of-band management is on a third network.
Scenario four: OMIVV is deployed in a network
where a single in-band management network exists and two out-of-band management networks exist.
Scenario five: OMIVV is deployed in a network where in-band and out-of-band management
are isolated from the public internet.
When configuring OMIVV for multiple network connections it's best to add
the extra network connection while the VM is turned off. We're going to go ahead and
configure this for a separate iDRAC network.
It's important to choose the VMXNET 3 adapter as this is the only one supported in OMIVV,
and i'm going to confirm the MAC address of these
so we know which adapter is which when we configure OMIVV.
I'm going to go ahead and power on my VM and we're going to complete the configuration.
I'm going to bring up the remote console here.
Logging in as admin we can configure that network.
Here we can also see '2E:9A'. We're going to leave this default as this is going to be used
for all of our connections. We can rename this connection to make it easier for us to recognize.
For our wired connection 2 this is going to be our out of band.
We're going to configure this with any IP settings that we want. We're going to keep this DHCP
however we do need to choose routes and use this connection only for resources on its network.
It's also important to not have additional gateways on the out-of-band management
as multiple gateways could cause an issue for us on the appliance.
Now that we've configured our networks we can proceed with registering.
To confirm our configuration, from the web UI under 'Appliance Management'
we can also view the networks that we're connected to for in-band and management networks
as well as our DNS configuration and our hostname. Once all your configurations are exactly how you
need them, then you can proceed with further configuration and deployments using OMIVV.
Additional considerations for using multihomed in OMIVV would be for OS deployment. When
initiating the OS deployment task make sure that you select the NIC or interface which belongs to
your vSphere network. Also SNMP traps, if OMIVV is configured with dual net configuration with
vSphere and out-of-band networks, the SNMP trap destination set on your iDRAC or CMC
will have to be the appliance IP which belongs to the out-of-band management network.
It's also important to note that when troubleshooting logging in as the read-only user
will allow us to perform our normal network troubleshooting steps, such as ifconfig
to verify these. Pinging of IP addresses on the network or checking our route configuration
to make sure that our routes are properly configured.
All the information that I've gone over today is also available in our Deploying and
Configuring OMIVV in a Dual NIC Environment white paper. Thank you so much for watching
our video today, hope you have a wonderful rest of your day.