![Banner image](https://cdn-prod.scdn6.secure.raxcdn.com/static/media/667a5dd4-5812-4b88-a8e9-93e893042e36.jpeg?_cb=1637296164.116175)
OMNI Bulk Configuration Spreadsheet Part 2 of 2
Wed, 01 Dec 2021 19:07:54 -0000
|Read Time: 0 minutes
In part 2 of the Bulk Configuration blog, we will cover the creation of several server interface profiles using the Bulk Configuration spreadsheet.
Note: See the OMNI User Guide on the Dell EMC OpenManage Network Integration for VMware vCenter website for more details on other configuration options with the Bulk Configuration spreadsheet.
Gather server information
In this section, we will gather the MAC addresses associated with the vmnics of the ESXi hosts. OMNI requires the MAC address of the vmnics to facilitate automation for additional network creation. Once the initial server profiles are created, you can update or modify the interfaces using the server interface profiles, or through the configuration of the vDS in vCenter. OMNI monitors the vDS port group information and applies any changes made to port-groups on the physical network using the MAC addresses associated with the vmnics of the ESXi hosts.
There are two methods that can be used to gather the vmnic MAC addresses:
- Use the show lldp neighbors command on the switch CLI
- Use the ESXi Direct Console User Interface (DCUI)
Show LLDP neighbors
This section covers the use of the switch CLI to get the required MAC addresses.
- From the CLI of the SFS switch, enter the show lldp neighbors command to get the MAC address for the correct server.
- Run the same command on each leaf switch to gather all MAC addresses associated with the required ESXi servers.
In this example, there is one connection to each leaf switch for the single ESXi host, esxi01. It is connected to ethernet 1/1/21 in the figure above.ESXi01 - NIC1
Leaf1A
b0262825e0e1
- NIC2
Leaf1B
b0262825e0e0
ESXi DCUI
Alternately, you can use the DCUI to get the details on the network adapters.
- Go to the specific server DCUI.
- Select the Configure Management Network option.
- Select Network Adapters.
Note: If the full MAC is not visible, enter D to view the full details.
ESXi01 - NIC1 | b0262825e0e1 |
- NIC2 | b0262825e0e0 |
Create server interface profiles
Now that all the MAC addresses have been gathered, enter the information into the Bulk Configuration spreadsheet. In this example, we are applying the previously created networks to a single ESXi server. For details, refer to Bulk Config Spreadsheet Part 1.
- Open the Bulk Configuration spreadsheet.
- Go to the ServerInterface tab.
- Enter the MAC address as the InterfaceId.
- Set the NICBonded type. This example uses False.
- Set a server profile name, ESXi.
- Set the Bonding Technology, AutoDetect.
- Set the Network Tagging. This example will set both networks 100 and 200 as tagged.
Note: The server interface profile uses the NetworkID field to set the tagging. Refer to the appropriate network tab in the spreadsheet or go to the OMNI UI to get the correct NetworkID. If there are existing networks associated with these interfaces, they must be included in the spreadsheet, as the spreadsheet will override the existing configuration on those interfaces.
- Save the spreadsheet. You can now upload the spreadsheet to create the server interface profiles and set the correct network tagging on the switch interfaces.
- From the OMNI UI, click the Bulk Configuration tab.
- Upload the spreadsheet and select Validate.
- Click Apply.
Note: If the networks from the Bulk Config Spreadsheet Part 1 blog are still in the spreadsheet, OMNI will revalidate those sections of the spreadsheet.
Validate the configuration
The final step will be to validate the configuration on the Fabric. This can be done in one of two ways:
- Use the Server Interface tab in the OMNI UI.
- Use the MAC addresses to locate the correct server profiles. When the specific MAC address is selected, the associated networking configurations can be seen.
The changes made in this example are highlighted with the red boxes.
- Use the switch CLI.
- Use the show virtual network vlan command to verify General Purpose networks.
The network changes specified in the Bulk Configuration spreadsheet can be seen below, highlighted in yellow.
S5248-Leaf1A# show virtual-network vlan
Vlan Virtual Network Interface
-------------------------------------------------
100 100 port-channel1000, ethernet1/1/21
1811 1811 port-channel1, port-channel1000, ethernet1/1/21, ethernet1/1/22
3939 3939 port-channel1000
4091 4091 port-channel1000
-----------Output Truncated----------------------
- Use the show vlan command to verify VLAN networks.
S5248-Leaf1A# show vlan
Codes: * - Default VLAN, M - Management VLAN, R - Remote Port Mirroring VLANs,
@ - Attached to Virtual Network, P - Primary, C - Community, I - Isolated
Q: A - Access (Untagged), T - Tagged
NUM Status Description Q Ports
200 Active database-01 T Eth1/1/21
T Po1000
4000 Active vlan4000 T Po97-98,1000
4002 Active vlan4002 A Po97
4003 Active vlan4003 A Po98
* 4089 Active vlan4089 A Po1000
4090 Active vlan4090 T Po1000
4094 Active T Po1000