Hello, my name is Ted. I'm a senior engineer with DELL E MC and the Systems Management Group. Like to welcome you to our video about Oiv va dual home configuration, uh multi home networking configuration for OMIVV is specifically designed for implementations where connectivity between multiple management networks is required. Let me show you some common multi home configurations. In scenario one OMIVV is deployed in a network where in band management and out of band management are isolated and cannot communicate one with one another.
Scenario two is where Omivv is deployed in a network where there are two V centers each deployed in their own isolated network, each containing both in band and out of band management networks. Scenario three, all my VV is deployed in a network with two V centers 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.
Uh 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 gonna go ahead and uh configure this for a separate IDRE network. It's important to choose the VMX net three 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 oivv, I'm going to go ahead and power on my BM and we're gonna complete the configuration. I'm gonna bring up the remote console here logging in as admin, we can configure that network here. We can also see two E nine A.
We're going to leave this default as this is gonna be used for all of our connections. We can rename this connection to make it easier for us to recognize for a wired connection. Two. This is gonna be our out of band. We're going to configure this with any IP settings that we want. We're gonna keep this DH CP. 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 WEI 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 host name.
Once all your configurations are exactly how you need them, then you can proceed with further configuration and deployments using all IVV. Additional considerations for using multi hoed in OMIVV would be for OS deployment uh when initiating the OS deployment task, make sure that you select the nick or interface which belongs to your beast food network. Also SN MP traps. If OMIVV is configured with dual the configuration with vsphere and auto band networks, the SN MP trap destination set on your eye tracker C MC 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 is the read, only user will allow us to perform are normal network troubleshooting steps such as if config to verify these thinking of IP address is 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 my VV in a dual nick environment white paper.
Thank you so much for watching our video today. Hope you have a wonderful rest of your day.
