OpenManage Network Integration for SmartFabric Services User Guide Release 2.1 August 2021 Rev.
Notes, cautions, and warnings NOTE: A NOTE indicates important information that helps you make better use of your product. CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid the problem. WARNING: A WARNING indicates a potential for property damage, personal injury, or death. © 2021 Dell Inc. or its subsidiaries. All rights reserved. Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries.
Contents Chapter 1: About this guide........................................................................................................... 6 Text and Syntax Conventions.......................................................................................................................................... 6 Related Documents.............................................................................................................................................................
SmartFabric bulk configuration...................................................................................................................................... 74 Configuration notes.................................................................................................................................................... 75 Download and complete the bulk configuration template.................................................................................
Unable to register the vCenter in OMNI....................................................................................................................159 OMNI is unable to communicate with other devices.............................................................................................. 159 Timestamp not synchronized in OMNI....................................................................................................................... 159 Reset OMNI VM password...........................
1 About this guide This guide provides information regarding OpenManage Network Integration (OMNI) and the integration with different solutions. It covers the following details: ● ● ● ● ● Install and setup OMNI OMNI automation for SmartFabric instance OMNI automation for PowerEdge MX SmartFabric OMNI automation for NSX-T Lifecycle management This document may contain language that is not consistent with current guidelines of Dell Technologies.
Documentation Feedback Dell Technologies strives to provide accurate and comprehensive documentation and welcomes your suggestions and comments. You can provide feedback in the following ways: ● Online feedback form—Rate the documentation or provide your feedback on any of product documentation pages at www.dell.com/support. ● Email—Send your feedback to networkingpub.feedback@dell.com. Include the document title, release number, chapter title, and section title of the text corresponding to the feedback.
2 Change history The following table provides an overview of the changes to this guide from a previous OMNI release to the OMNI 2.1 release. For more information about the new features, see the respective sections. Table 2. New in 2.1 Revision Date Feature Description A00 2021–08-16 Bulk configuration Configure all types of networks, routing profiles, server profiles, and server interface profile for a SmartFabric instance in bulk.
Table 3. New in 2.0 (continued) Revision Date Feature Description compliance errors for the SmartFabric instance. OMNI Home page enhancement OMNI Home enhancement with an option to add different service instance separately. Support for onboarding unknown server discovered interfaces OMNI supports dynamic onboarding of unknown servers that are discovered by SmartFabric.
3 Overview of OMNI, SFS, VxRail, and PowerEdge MX This section provides an overview of Dell EMC OpenManage Network Integration (OMNI), SmartFabric Services (SFS), and integration of SFS with VxRail and PowerEdge MX. SmartFabric Services SmartFabric Services (SFS) is an automation framework that is built into Dell EMC SmartFabric OS10, to integrate converged and hyperconverged infrastructure systems. These solutions deliver autonomous fabric deployment, expansion, and life cycle management.
● ● ● ● ○ VxRail Manager automatically creates fabric policies for VxRail nodes. ○ SmartFabric automates all fabric functions. Integrated life cycle ○ Fabric creation, expansion, and maintenance follow the VxRail application model. ○ HCI fabric operations are fully managed through VxRail Manager or vCenter. Better infrastructure visibility ○ Tight integration between VxRail appliance and Dell EMC ON-Series PowerSwitches. Improved SLA ○ Fully validated software stack.
Key benefits ● Data center modernization ○ I/O aggregation. ○ Plug and play fabric deployment. ○ Single interface to manage all switches in the fabric. ● Lifecycle management ○ SmartFabric OS10 updates across the fabric. ○ Automated or manual rollback to last well-known state. ● Fabric automation ○ Physical topology compliance. ○ Server networking managed using templates. ○ Automated QoS assignment per VLAN. ○ Automated storage networking.
in OMNI. For the automation to work, register OMNI with the vCenter and ensure to start the respective OMNI vCenter automation services.
4 OpenManage Network Integration OpenManage Network Integration (OMNI) enables configuration of SmartFabric Services (SFS) that integrates with VMware vCenter for fabric automation of the physical network infrastructure corresponding to the virtual network operations within vCenter. OMNI also serves as a front-end management application for managing one or more service instances, enabling administrators to manage and operate one or more network fabrics that are deployed with SFS.
Maximum supported instances A single OMNI VM instance supports: Table 7. Number of supported instances Entities Number of instances supported by OMNI vCenter 10 SmartFabric instances 15 OME-Modular instances 2 NSX-T Manager 1 Install OMNI virtual appliance using vCenter This information describes how to deploy the OMNI appliance on a VMware ESXi hypervisor using the OMNI OVA file, and create a virtual machine (VM).
4. Select Local file, click Choose Files, select the OMNI ova file from a local source, and click Next. 5. Edit the virtual machine name and select a location for the VM, and click Next.
6. Select the destination compute resource, and click Next. 7. Review and verify the template details. You must acknowledge by ignoring the warnings clicking Next.
8. Accept the end-user license agreement (EULA), and click Next. 9. Select the VSAN datastore for the configuration and disk files, and click Next. 10. Select a destination network for each network source, and click Next. The VxRail Management Network must be assigned to the VxRail internal Management network. The default VLAN ID for this network is 3939.
the OMNI plug-in. If you are using a standalone generic ESXi host deployment, you can skip this step. NOTE: Ensure that the source and destination networks are mapped properly. Any misconfiguration may cause connectivity issue between vCenter and OMNI. 11. Click Finish to start creation of the VM.
Power on OMNI VM 1. Click Recent Tasks and scroll to the bottom of the window to view the status, and wait for the deployment to finish. 2. Select the OMNI VM you want to power on, and select Actions > Power > Power On.
3. Select Launch Web Console. Set up OMNI This information describes how to log in to the VM console, and also explains the OMNI vCenter setup. Log in to VM console Configure OMNI through the VM console after completing the authentication step. By default, the VM console automatically closes after 10 minutes, but can be customized. 1. Enter admin for both the default username and password. 2. If it is a first-time login, the system prompts for password change.
NOTE: The sudo password is the same as the password set for the admin user. NOTE: Root user is disabled by default. To set the password to enable root user, use the OMNI VM console CLI menu. You can only access root user through the console. Setup OMNI This information describes how to set up the OMNI appliance with the required network interface configurations. NOTE: The OMNI initial configuration setup can be performed using the vCenter OMNI VM console only.
2. Select Edit a connection, then click OK. CAUTION: Edit a connection menu displays edit option of Bridge interface docker0 and Veth interfaces, apart from ens160 and ens192. Do not modify any configuration of the docker0 or Veth interfaces as it can lead to OMNI appliance failure or unexpected OMNI behavior. 3. Select Wired connection 1, then click Edit. 4. Verify Ethernet (ens160) is connected to the vCenter reachable network, then change the Profile name to vCenter Server Network. 5.
NOTE: If you are using a stand-alone generic ESXi host deployment and if DHCP services are running on the Management network subnet, use the default IPv4 vCenter server network configuration which uses automatic IP address assignment using DHCP. During this scenario, set the IPv4 configuration to Automatic. 6. Click Show to the right of IPv4 configuration, then click Add. 7.
8. Select Ignore for the IPv6 configuration and click OK. You are now ready to continue configuration. NOTE: If you are not connecting the OMNI VM to a SmartFabric local-link, ignore this part as it not applicable and you are ready to activate the connection profile. 1. Select Wired connection 2, and click Edit.
2. Rename Profile name to VxRail Mgmt Network. NOTE: The VxRail Mgmt network (ens192) setting is relevant only for VxRail deployment with IPv6 autodiscovered instance. Configuring ens192 interface is not required for non-VxRail environment. 3. Select Disabled for the IPv4 configuration. 4. Select Link-Local for the IPv6 configuration.
5. Click Edit to the right of Routing, and click Add. 6. Enter the custom route as fde1:53ba:e9a0:cccc::/64, and click OK.
7. One custom route is now configured, click OK. 8. Click Back to activate the connection profiles. Activate connection profiles NOTE: To populate DNS entries automatically, deactivate and active each profile.
1. Select Activate a Connection, and click OK. NOTE: If you change while editing a connection, you must deactivate then activate the connection for the respective interface profile. 2. Select the vCenter Server Network profile, and click Deactivate. Repeat for VxRail Mgmt Network. 3. Select the vCenter Server Network profile, and click Activate. Repeat for VxRail Mgmt Network.
4. Click Back, select Set system hostname, and click OK. 5. Enter the hostname for OMNI, and click OK. NOTE: If you are setting the hostname of OMNI, ensure that you have the DNS entry for the hostname. 6. The hostname is now set. Click OK.
7. Click Back, and OK to exit the network management UI. 8. Enter a valid NTP Server IP address or hostname, and click Enter. 9. Enter n to not install the SSL certificate from remote server. When you enter n, the self-signed certificate that is created locally is installed. NOTE: To install a new certificate, see Generate and install SSL certificate. NOTE: If the NTP Server is not configured, the OMNI appliance VM synchronizes with the ESXi server time zone.
2. Log in to the ESXi server. 3. In the ESXi server, select Virtual Machines, and click Create / Register VM.
4. Select the creation type as Deploy a VM from an OVF or OVA file and click Next. 5. Enter a name for the VM and upload the OVA file from a local source, and click Next.
6. Select storage for VM configuration files and virtual disks and click Next. 7. Accept the EULA license agreement and click Next. 8. By default, OMNI VM OVA has dual NIC adapters. Use only one network if you deploy OMNI VM as an independent entity without vCenter. You can disable VxRail management network (ens192). Select the disk provisioning and power options, and click Next.
You can select Power on automatically checkbox to power on the VM after the installation. 9. Ready to complete page displays the summary of the settings that are configured so far. Review and verify the settings and click Finish to complete the installation. Set up OMNI To log in to the VM console and set up OMNI configurations: 1. Follow the steps provided in the section Set up OMNI to log in to the VM. 2. Configure Wired connection 1 (ens160) interface with the ESXi management IP address.
OMNI appliance console CLI menu This information describes the menus available to the admin SSH user through the console. Table 8. OMNI appliance console CLI menu Menu option Submenu option Description 1. Show version — Display OMNI virtual appliance and plugin version. 2. Interface configuration menu 0. Config Docker Private network Display default OMNI docker private network information. Also configure docker private network information. NOTE: OMNI default docker private subnet is 172.16.0.1/25.
Table 8. OMNI appliance console CLI menu (continued) Menu option Submenu option Description appliance management user interface to change log level of needed services. 7. Exit — 1. Change appliance password Change appliance admin user password. 2. Change root password Assign password of application root user; root user is disabled by default, and is required to set the password first to access the root user. Root user is only accessible using the vCenter OMNI VM console.
1. From the OMNI management menu, enter 4 to go to the Password/SSL configuration menu. 2. Enter 3 to generate self-signed SSL certificates. OMNI VM displays confirmation for replacing the existing certificate and key with the newly created certificates and keys. NOTE: If the OMNI stand-alone UI is open when generating a new self-signed SSL certificate, you must log out from OMNI stand-alone UI and log in again before you unregister and re-register the vCenter. 3.
4. Register the vCenter again using OMNI stand-alone UI. Log out and log in the vCenter again to apply the new SSL certificate. Refresh the browser to view the OMNI UI plug-in from the vCenter when you register or unregister OMNI appliance with vCenter 7.0. For older versions of vCenter, log out and log in to access the plug-in from the vCenter. Install SSL certificate from remote server To install SSL certificate from remote server: 1. Generate SSL certificate using a standard method in .pem or .
4. Enter 4 to install the certificate from remote server. Enter the remote SCP server IP address or hostname and login to the SCP server. Provide the path to the certificate and private key in the server. The files are copied to the OMNI VM. 5. Enter y to install the SSL certificate. NOTE: If the OMNI stand-alone UI is open when installing the new SSL certificate, you must log out from OMNI stand-alone UI and log in again before you unregister and re-register the vCenter. 6.
View and configure docker private network settings The internal docker system of the OMNI VM uses a private network to communicate with the docker components. In 2.1 release, the docker private network IP address is set to 172.16.0.1/25 by default. View and change the default configuration for the docker private network using OMNI console. View docker private network configuration 1. Log in to OMNI console. 2. From the OMNI management menu, enter 2 to go to the Interface configuration menu. 3.
4. OMNI console displays the current docker private subnet settings with an option to change the docker private network setting. You can ignore to change the setting by entering n. Change docker private network default settings When there is a conflict between the default docker private network and any other network to which OMNI is connected, OMNI cannot communicate with the devices in that network. To avoid the conflict, you can change the docker private network default settings in OMNI.
5 OMNI vCenter integration This section explains connections between the physical switch in SmartFabric mode and the servers (ESXi hosts) in the vCenter. It also explains how OMNI automates the configuration on the physical switches in SmartFabric mode based on the virtual networking on hosts. vSS and vDS port groups Leaf switches (in SmartFabric mode) that are part of a fabric are connected to server ports (VMNICs) physically.
For the server to communicate with the external network, the L2 uplink in the fabric must be configured with networks used by the vCenter port groups. In L3 personality, you can create the L2 uplink with the uplink type as Default. For more information about L2 default uplink configuration, see Create L2 uplink.
6 Access the OMNI stand-alone portal You can access OMNI as a stand-alone portal using the OMNI IP address. OMNI appliance page displays links to launch the OMNI Appliance Management portal, OMNI Fabric Management Portal, and OMNI Documentation. You can access the OMNI UI using the latest version of the browsers, such as: ● Google Chrome ● Mozilla Firefox Starting from release 2.0, OMNI provides more scalable and secure sign-on feature, when launching OMNI as a stand-alone user interface.
2. Enter the username and password for the OMNI VM and click Sign In. NOTE: Alternatively, you can also log in to Fabric Management portal directly using https:// OMNI_IP /delawareos10 with the configured IP address or FQDN. After successful authentication, OMNI Home page is displayed. Once you log in to the OMNI Fabric Management Portal with the username and password, OMNI Home page is displayed. From OMNI Home, you can: ● ● ● ● ● ● ● Edit OMNI address.
3. Edit the IPv4 address or FQDN of the OMNI. 4. Click Submit. The system displays the edit success message. Register vCenter with OMNI Starting from 2.0 release, you have to register the vCenter instance with OMNI using the UI. You can register up to 10 vCenters in a single OMNI VM. Limitation Before registering the vCenter, ensure that there is only one FQDN mapping for a vCenter IP address in the DNS entry. Multiple DNS entries for the same IP address sometimes lead to vCenter registration failure.
The system displays a vCenter registration successful message. When adding the vCenter instance, you can choose only to add the instance and not register. To do so, select False for Registered option. Selecting False adds the vCenter and no register the vCenter with OMNI. You can register later without entering the credentials again by changing the status. You can choose not to enable the automation services for the vCenter by selecting False for Automation option.
Unregister vCenter You can unregister a vCenter that is already registered with OMNI. When you unregister the vCenter, OMNI stops the automation services for that vCenter. NOTE: The unregister vCenter option is available only when OMNI is launched as a stand-alone UI. 1. Click OMNI Home > vCenter instance, 2. Click the status Registered for the vCenter you wanted to unregister. 3. Click Ok to unregister the OMNI from the vCenter. The system displays status change success message.
The system displays Maintenance mode change success message. Access OMNI plug-in from the vCenter This information describes how to access OMNI plug-in from the vCenter. After you register vCenter with OMNI, a shortcut is available from the vSphere Client left-pane within the menu drop-down and shortcuts view. Before you use the plug-in, you must set up an OMNI appliance in vSphere. Once you register OMNI with vCenter, the OMNI plug-in is available in the vCenter.
NOTE: SFS events feature is supported from SmartFabric OS10 version 10.5.2.2 and later. The system displays SmartFabric instance configuration success message. Add SmartFabric instance This information describes how to add SmartFabric instances in OMNI. You can add up to 15 SmartFabric instance in a single OMNI VM. Prerequisite Identify the master IP address of the switch in a SmartFabric cluster. To identify the master, use the show smartfabric cluster command in the OS10 switch CLI.
The system displays SmartFabric instance creation success message. SmartFabric page displays the following information: ● ● ● ● SmartFabric Instance—Displays the list of IP address or FQDN of the SmartFabric instance. SmartFabric Name—Displays the name of the SmartFabric. User Name—Displays the username for SmartFabric. Maintenance Mode—Displays the Maintenance mode of the SmartFabric. ○ Gray—Maintenance mode is Off or disabled. ○ Green—Maintenance mode is On or enabled.
Edit a SmartFabric To edit the configuration of the existing SmartFabric instance: 1. Select the SmartFabric instance from the list, and click Edit. 2. Update the configurations and click Submit. The system displays SmartFabric instance update success message. Delete a SmartFabric To remove a SmartFabric instance from OMNI. 1. Select the SmartFabric instance from the list and click Delete. 2. Click Delete to confirm. The system displays SmartFabric instance update success message.
3. Click Ok to confirm. The SmartFabric instance mode changes to In Service. OMNI support for vCenter Enhanced Linked mode Enhanced Linked mode (ELM) is a feature available in vCenter. Using ELM, you can link multiple vCenter appliances that are deployed across different location and have a global view of the inventory. OMNI appliance behavior when the vCenter or vCenters registered to OMNI are in ELM: ● You must register all the vCenters that are in ELM with OMNI.
Refresh button Click Refresh to update the host network inventory data and display updated contents. Physical adapter table Select a switch from the Host Network Inventory to view detailed information. The table is default-sorted by descending switch name to group physical adapters belonging to the same switch. ● ● ● ● ● Server Physical adapter—Name of the physical NIC. Logical switch—Name of switch the physical adapter is connected to. MAC address—AC address of the physical adapter.
● Switch tab—Includes name of switch, MTU in bytes of switch, physical adapters connected to the switch, and uplink ports on the switch. ● Port groups tab—Includes the name of port groups, and VLAN IDs for each port group. ● VMs tab—Includes the name of VMs of that host that is connected to a single virtual switch. View physical switch details Displays information about the onboard interface. This information displays only when there is a physical connection between the VxRail domains and OMNI.
● ● ● ● ● ● Admin Status—configured state of the physical interface Interface Status—current operations state of the physical switch port Auto Neg—negotiation status of the physical interface Current Speed—current operational speed of the physical interface MTU—maximum transmitting unit configured on the physical interface Native VLAN—untagged default VLAN for the physical switch Networks tab ● Network Name—name of the VLAN network ● Network ID—unique identifier of the fabric network ● VLAN—tagged VLAN of
OMNI Information You can view the links to documentation and end-user license agreement (EULA), and summary information about the OMNI VM. Select OMNI Home > OMNI Information to view the relationship information and the type of the relationship between the entities. Plugin Information Links has links to: ● Documentation—Access this link to see the documents that are uploaded at www.dell.com/support OpenManage Network Integration product page. ● EULA—Click the link to view the end-user license agreement.
NOTE: You can also access the Appliance Management UI directly from a browser. Open a browser, go to https:// OMNI_IP /omni with the IP address or FQDN that is configured during the initial setup. ● Logout—Manually terminate the login session using the Log out button in the upper right of the UI. ● Login session timeout—OMNI terminates an inactive login session after 15 minutes to prevent unauthorized access.
Manage OMNI essential and automation services Services menu displays all the management and vCenter automation services running on the OMNI appliance. By default, the web and database essential services start automatically after the initial setup. After adding the SmartFabric, OME-M, or NSX-T instances and registering the relevant vCenters, OMNI creates automation services for each vCenter instance.
Table 9. List of OMNI services (continued) Service Function States omni_events_celery_beat Service that periodically cleans the old events from the database. omni_events_celery_worker Worker service that process the events from the message queue and stores them in the database. omni_automation_app_celery_beat Service that periodically prunes unused networks on service instances and discovers how service instances are related to each other. omni_queue Service that runs the message queue.
After you start the service, OMNI starts monitoring the networking events for the registered vCenter. 3. The system displays start service success message. Stop vCenter automation services To stop the fabric automation services: 1. Select the relevant automation service that you want to stop, and click Stop. 2. The system displays stop service success message. To restart the fabric automation service, select the relevant automation service, and click Restart. Change log level 1.
The system displays set log level success message. 3. (Optional) Click Debug under log-level of each service to modify the log-level to Error. The system displays set log level success message. Download Support Bundle Support options are used for debugging. If there is an issue, download a support bundle containing all the logs that are found in OMNI using Download Support Bundle. Also change the log-level in OMNI to collect logs of different types.
7 SmartFabric management with OMNI This chapter explains how to manage SmartFabric components or entities using OMNI. The OMNI VM displays the list of manually created service instances, and the OMNI autodiscovered SmartFabric instances. For more information about the SmartFabric instances, see OMNI Fabric Management Portal.
OMNI feature support matrix This table lists the OMNI feature support matrix for SFS-VxRail and PowerEdge MX SmartFabric Services solutions. Table 10.
The Overview dashboard displays information regarding the following metrics: Device Status—Displays the status of the all the devices that are deployed in the SmartFabric instances along with the number of devices in each status. ● Green—Indicates that the devices are online. ● Red—Indicates that the devices are offline. Recent Fabric Events—Displays the recent fabric events that are generated by SFS. The events are displayed with the following information: ● Device—Service tag of the switch.
1. Select the SmartFabric instance > Summary > Fabric Nodes. You can view the list of spine and leaf nodes that are deployed in the fabric. Click Domain at any time to update the fabric details. 2. Click the Fabric ID to view the detailed information of the switch. The details include each switch status (online or offline), name, model, version, role, and IP address. Fabric ID—Displays the status of spine switches connected in the fabric. Rack—Displays the status of the leaf switches in each rack.
View fabric topology The Topology tab displays the graphical topology of the network fabric for the selected SmartFabric instance. You can also view the details of the switch in the fabric. Select the SmartFabric instance > Topology to view the graphical representation of the L3 leaf and spine topology. The topology view displays the switch icons with the hostname and the service tag information under each switch and the link connectivity between the switches.
Leaf Switches—Displays the list of all leafs in the fabric with ports, unused ports, breakout ports, and jump port information in categories. Click the arrow of the respective leaf switch category to view more information about the ports. Edit port configuration on a switch Edit the configurations such as auto negotiation or MTU of a port or multiple ports on a leaf or spine switch: CAUTION: Changing the interface configurations can potentially cause a disruption in service.
auto negotiation, admin status. If the configuration does not match the connected peer switch, it can lead to connectivity issues. 1. Select the SmartFabric instance > Switches. 2. Select the spine or leaf switch by clicking the arrow to view more information. 3. Select a category (All Ports or Unused Ports) and the port, and click Edit. 4. Edit the name, description, admin status, and MTU. 5. Click Edit.
Configure auto negotiation status You can enable or disable the auto negotiation on a single port or multiple ports. Auto negotiation option is not applicable for port channel interfaces. When you configure auto negotiation for a port channel interface, OMNI UI displays a warning message to clear the port interfaces from the selected list. To enable auto negotiation: 1. From All Ports, select a port or multiple ports and click Enable Auto Neg. 2. Click Yes to confirm.
To disable the ports, select a port or multiple ports, and click Disable Admin Status. The system displays the change status and update success message on completion. Dell Technologies recommends to: ● Enable the port status to operationally up before adding any devices to the port, if the port is disabled using the OMNI UI. NOTE: Devices that are connected to the disabled port are not discovered.
5. Select the Breakout Mode for the port from the list. 6. Click Submit. The system displays breakout port configured successful or failure message. To view the details of the breakout ports, select a port to view the properties of the port. Add a jump port You can configure one port per leaf switch as a jump port. You can select any available port that is not part of an uplink and ICL, and port connected to a server in SmartFabric deployment. To configure a jump port: 1.
The system displays jump port addition success message. Delete jump port 1. Select the leaf switch for which you want to delete the configured jump port. 2. Select the Jump port and click Delete. The system displays jump port deletion success message. SmartFabric bulk configuration With 2.1 release, you can configure a subset of configurations such as networks, server profiles, server interface profiles, routing profiles on a SmartFabric instance in bulk numbers.
Configuration notes The configuration notes that you should consider before using the bulk configuration feature: ● You cannot configure uplinks and associate the networks or routing profiles with uplinks using bulk configuration. You must create uplinks using OMNI UI, see Uplinks. ● You can add the networks or routing profiles that are created using bulk configuration to uplink. Use Edit networks option to associate the network or routing policies to uplink.
Table 11. General Purpose Networks tab Field Description NetworkId Enter the network ID for a general purpose network. This ID must be unique. For example, external-mgmt. NetworkName Enter the name of the network. Example, external-mgmt. Description Enter the description of the general purpose network. This is an optional field. VLAN Enter the VLAN ID for the general purpose network. The VLAN number can range from 1—3999 (excluding 3939).
Table 14. VLAN Networks tab Field Description NetworkId Enter the network ID for a L2 or L3 VLAN network. This ID must be unique. For example, network-500 NetworkName Enter the name of the L2 or L3 VLAN network. Description Enter the description of the L2 or L3 VLAN network. This is an optional field. VLAN Enter the VLAN ID for the L2 or L3 VLAN network. The VLAN number can range from 1—3999 (excluding 3939). IPAddressList Enter the IP address for the L3 VLAN network separated by comma.
Table 16. Server profiles tab (continued) Field Description BondingTechnology Enter the bonding technology. You can enter two values AutoDetect or LACP. For VxRail nodes, you must always set to Autodetect. UntaggedNetwork Enter the network ID that must be untagged to the server interface profile. Networks Enter the network ID that must be tagged to the server interface profile separated by comma. Static Routes tab—Displays the template to configure static routes in bulk.
3. Click Select File to choose the completed XLS worksheet containing the bulk SmartFabric configuration. 4. Click Validate to proceed with the validation. The system displays the validation check status of each template configuration tab. If validation check has errors, the errors are displayed at the top with the detailed information. You can change the configurations based on the error information provided and upload the file again to proceed.
5. Click Apply to apply the bulk configuration file. The system verifies the configurations and displays the verification details. 6. Click Complete to implement the bulk configuration on the SmartFabric instance. The system displays success message. Click Apply another configuration to apply another bulk configuration template.
Configure server interface profile Server Interfaces Profile page displays a list of Server Profile IDs and their respective onboard status. Select a profile to view details pertaining to that specific profile. You can view information including interface ID, fabric ID, native VLAN, and network name and VLAN ID (if applicable). From Server Interface, you can: ● ● ● ● ● Create a server interface profile. Edit a network in a server interface profile. Edit the ports in a server interface profile.
4. (Optional) Select Yes for the Static Onboarding Option, add Leaf Node and Interface (where the server interface is connected), select the routing protocol as None, and click Create. 5. (Optional) Select Yes for the Static Onboarding Option, select Leaf Node and Interface (where the server interface is connected), select eBGP. Enter the eBGP routing template by entering the name, peer ASN, description, and peer interface IP address, and click Create.
NOTE: In static onboarding, the eBGP or static route routing protocol option is used for NSX-T deployment.
6. (Optional) Select Yes for the Static Onboarding Option, select Leaf Node and Interface (where the server interface is connected), select Static Route, enter the Network Address and Next-Hop Address, then click Create. NOTE: You cannot delete any created server profile. 7. The system displays server profile and server interface creation successful messages. Create server interface with new server profile To create a server interface with new server profile: 1.
3. Select the Server Profile Id and Server Profile Bonding Type from the list, select the Untagged Network and Tagged network, enable or disable NIC Bonding, select Static Onboarding Option as No, and click Create. 4. (Optional) Select Yes for the Static Onboarding Option, add Leaf Node and Interface (where the server interface is connected), select the routing protocol as None, and click Create. 5.
entering the name, peer ASN, description, and peer interface IP address, and click Create. NOTE: In static onboarding, the eBGP or static route routing protocol option is used for NSX-T deployment. 6. (Optional) Select Yes for the Static Onboarding Option, select Leaf Node and Interface (where the server interface is connected), select Static Route, enter the Network Address and Next-Hop Address, then click Create. NOTE: You cannot delete any created server profile. 7.
NOTE: OMNI does not synchronize a statically onboarded interface when it is first added. For the synchronization to happen, a port-group change event on the vCenter must happen or a restart of the automation service for the specific vCenter and SmartFabric instance must occur. Edit networks and ports in a server interface profile You can edit the network and port configuration in a server interface profile. You can also view the detailed information of a server interface profile.
The system displays the server interface profile update success message. Delete a server interface profile You can delete a service interface profile from the SmartFabric instance: 1. Select the server interface profile from the displayed list and click Delete. 2. Click Delete to confirm.
3. Select the vCenter from the list, and click Next. 4. Select the relevant cluster, the ESXi host, or the VM NICs available on the ESXi host. ESXi Host Selection window displays the server profile status of the interfaces on the right. NOTE: You cannot select the VM NICs that are already part of a server interface profile in SmartFabric. 5. Click Next to complete the selection of the VM NICs.
6. The Interface Configuration screen displays the list of selected VM NICs. 7. (Optional) Click Edit icon available for each interface to edit the server profile information. Edit the NIC bonding configuration and Static Onboarding. If the static onboarding is No, select an Untagged Network and one or more Tagged Networks and click Update. NOTE: You cannot select same network for both untagged and tagged networks.
NOTE: You cannot edit the server profile that is already configured in the system. 8. Click Add Networks to associate the networks that are part of the fabric for all the server interface profile. Select the networks for Tagged Networks and Untagged Network from the list, and click Add. NOTE: Add networks overwrite the existing networks of all the server interface profiles. 9. Click Finish after all the configurations are complete. The system displays the server interface profile update success message.
Import SmartFabric discovered server interfaces Automate onboarding of server interface profile by importing profiles that are discovered by SFS. Starting from 2.0 release, you can onboard unknown servers using OMNI. When known servers are connected to the fabric, SFS discovers the servers automatically, and OMNI onboards the discovered servers as part of this workflow. SFS discovers the hosts or servers as known using the originator field in the Dell custom LLDP TLVs sent by the servers.
● (Optional) Select the Routing Protocol as None, and click Update. ● (Optional) Select the Routing Protocol as eBGP, enter the ASN and IP address, and click Update.
● (Optional) Select the Routing Protocol as Static Route, enter the Network Address and Next-Hop Address, and click Update. 4. Select one or multiple discovered interfaces, add the service profile and networks, and click Update. For more information about adding server profile and networks, see Add to Server Profile and Add networks sections. Add to Server Profile To add the discovered interfaces to a new or existing server profile: 1.
● Select New Server Profile—Enter the Server Profile Id and Bonding Type to associate the interface with the new server profile, and click Associate. 3. The system displays the server interface profile association success message. Add Networks To add the networks to the discovered interfaces: 1. Select one or more interfaces from the list, and click Add Networks. 2. Associate the networks with the discovered interfaces, and click Add. ● Select one or multiple networks for Tagged Networks.
To remove the interface from the server profile, select one or more interfaces from the list, and click Remove from Server Profile. Configure and manage uplinks Configure an uplink and manage the uplinks that are available in the SmartFabric instance. Using the Uplinks tab, you can: ● ● ● ● View the list of uplinks created in the SmartFabric instance. Create an uplink. Edit network and port configuration for an uplink. Delete a created uplink.
3. Enter the port configuration by selecting the rack to create the uplink on, select the interfaces, the LAG Mode (LACP or Static), then click Next. 4. Select the untagged network, the OMNI network, and Select Yes or No to integrate the networks that are created automatically in the fabric through vCenter on this uplink.
5. (Optional) Click Create Network to associate a network with the uplink. Enter the name of the network, optional description, and the VLAN number. 6. Click Finish to complete the L2 uplink creation. The system displays user uplink creation success message. Create L3 Uplink Create an L3 uplink of L3 VLAN or L3 routed interface types. Create L3 VLAN uplink 1. Select the SmartFabric instance > Uplink, and click Create. 2.
3. Select the Switch group (Leaf or Spine), select the rack to create the uplink on, select the interfaces, select LACP for the LAG mode, then click Next. Leaf: Spine: 4. Select UnTagged network, select the OMNI network, enter an optional description, select either eBGP or Static Route for the routing protocol, enter the routing policy information, then click Finish.
A route is associated with the nodes that are configured in the port configuration. The system displays uplink creation success message. Create L3 routed interface uplink 1. Select the SmartFabric Instance > Uplink, and click Create. 2. Select L3 routed interface, enter the Uplink name, and optional description, then click Next. 3. Select the Switch group (Leaf or Spine), the rack to create the uplink on, select the interfaces, then click Next.
Spine: 4. Enter the network profile information and routing policy information for the uplinks, then click Finish.
The system displays L3 routed uplink creation success message. Edit networks and ports in an uplink You can edit the network and port configuration for an uplink, and also view the detailed information of the uplink. Select the uplink from the displayed list to view the details of the uplink on the right.
1. Select the uplink from the list, and click Edit Networks. 2. Edit the Untagged Network associated with the uplink, and click Update. The system displays the uplink interface edit success message.
1. Select the fabric uplink from the list and click Edit Ports. 2. Edit the networks associated with uplink interfaces and click Update. The system displays the uplink interface edit success message. Delete an uplink You can delete a user-created uplink: 1. Select the uplink from the displayed list, and click Delete. 2. Click Delete to confirm. Configure networks and routing configuration You can set up networks and routing configuration.
Configure general purpose networks When you create a general purpose network, OMNI creates a VLAN network along with the VXLAN virtual network. In general purpose network, VXLAN network identifier (VNI) and VLAN ID are same and you can associate one VLAN with the VNI across the fabric. If you delete a VLAN network, it automatically deletes the associated VXLAN network.
Edit general purpose network You can edit the configuration of the Layer 2 general purpose network and change it to Layer 3 general purpose network. 1. Select a network from the list and click Edit. 2. Modify the Network Type.
3. Enter the Prefix, Gateway IP Address, IP address, then click Edit. 4. The system displays virtual network edits success message. Delete general purpose network When you delete a general purpose network, both the VLAN and the VXLAN networks are deleted from OMNI. To remove a general purpose network configuration: 1. Select the general purpose network, and click Delete. The system displays the list of the server interface profiles associated with the network. 2. Click Delete to confirm. 3.
The system displays network creation success message. Edit network 1. Select the Network ID from the list and click Edit. 2. Edit the configuration as required. 3. Click Edit. The system displays edit network success message. Delete network 1. Select the network ID to remove and click Delete. The system displays the list of uplinks associated with the network.
2. Click Delete to confirm. The system displays network deletion success message. Configure multirack L3 VLAN Starting from 2.0 release, OMNI allows you to configure L3 VLAN network for the racks to which the servers are connected. Using this feature, you can create a L3 VLAN network for each VLT pair (rack) with a different subnet. This network is used for NSX-T overlay to create VTEP networks. Create, edit, and delete multirack L3 VLAN networks from OMNI. With 2.
2. Click Delete to confirm. The system displays network deletion success message. Configure VLAN networks Create, edit, and delete L2 or L3 VLAN networks for SmartFabric. Create L2 VLAN or L3 VLAN network VLAN networks for L2 profile: 1. Click Networks > VLAN Networks. 2. Click Create. 3. Select the Network Type as Layer 2 VLAN Network is selected as the Network Type, enter the Network ID, Network Name, enter a number for the VLAN, enter an optional description, then click Create.
The system displays VLAN network creation success message. Edit network 1. Select a network ID from the list and click Edit. 2. Modify the configuration as necessary. 3. Click Edit.
The system displays edit network success message. Delete network 1. Select the VLAN network to remove and click Delete. 2. Click Delete to confirm. The system displays network deletion success message. Configure VxLAN network Create, edit, and delete L2 and L3 profile VXLAN network configurations through OMNI. The purpose of VXLAN network is to associate multiple L2 or L3 VLAN networks to a single VXLAN network. Whereas a general purpose network does not have the flexibility to extend the VXLAN network.
The system displays virtual network creation successful message. Virtual network for L3 profile: 1. Select the SmartFabric instance > Network. 2. Click Networks > VxLAN Networks. The page displays the list of the VXLAN networks that are configured in the SmartFabric instance. 3. Click Create. 4. Select Layer 3 as the Virtual Network Type. 5. Enter the text for Virtual Network Name, a value for the VxLAN VNI, the VLT VLAN ID, IP address, prefix, gateway IP address, and helper IP address. 6. Click Create.
The system displays virtual network creation successful message. View VxLAN network details The VxLAN networks display a list of mapped VLANs. Select a VxLAN network to view details pertaining to that specific network including network ID, VLAN ID, and network name. Associate multiple VLANs to a VxLAN network Using the steps, you can map multiple VLANs to a single VxLAN network. 1. Select a VxLAN network. 2. Click Create option available after the VxLAN details. 3.
1. Select a virtual network from the list and click Edit. 2. Modify the Virtual Network Type. 3. Enter the Prefix, Gateway IP Address, IP address. 4. Click Edit.
The system displays virtual network edits success message. Delete VxLAN network To delete a VXLAN network, first delete the mapped VLAN or VLANs if associated, and delete the virtual network. 1. Select the Virtual Network Name, select the Network to remove, then click Delete. 2. Click Delete to confirm. The system displays network deletion success message.
Configure Routes You can configure static routes and eBGP peer routes for a network. Configure static routes Configure static routes and associate the route to the switch. Create static route 1. 2. 3. 4. Click SmartFabric > Network > Routing Configuration. Select Static Routes. Click Create to add a new static route. Enter the relevant details and click Create. The system displays static route creation is successful. Add route to switch 1. Select Routing Configuration > Static Routes. 2.
3. Click Add Route to Switch. 4. Select the switch to map to this route. 5. Click Add. The system displays the route added success message. Delete route from switch 1. Select the route to delete, and click Delete Route. 2. Click Delete to confirm the removal of the route from the switch. The system displays route policy deletion success message. Static route details The static route details display a list of mapped routes.
Delete static route 1. Select the static route to delete and click Delete. 2. Click Delete to confirm. The system displays static route deletion is successful. Configure eBGP peer route You can configure eBGP peer routes for a network. Create eBGP route 1. Select the SmartFabric instance > Network > Routing Configuration. 2. Click eBGP Peer Configuration. 3. Click Create to add an eBGP peer route. 4. Enter the relevant details and click Create. The system displays eBGP peer route creation is successful.
2. Select the switch, then click Add. 3. The system displays the route to switch addition success message. View eBGP peer details The eBGP peer details display a list of mapped routes. Select an eBGP route to view details pertaining to that specific route including the switch ID. Delete eBGP route from switch 1. Select an eBGP route, then click Delete Route. 2. Click Delete to remove the route from the switch. The system displays route deletion success message.
● SNMP NOTE: This feature is supported from SmartFabric OS10.5.2.2 and later versions, and applicable for SFS L3 leaf and spine personality. Configure NTP server To configure an NTP server: 1. Select the SmartFabric instance > Global Settings > NTP. The page displays the list of the NTP servers that are already configured in the OMNI VM. 2. Click Add to configure an NTP server. 3. Enter the IP address or hostname of the NTP server and click Add. The system displays the configuration success message.
The system displays the configuration success message. To delete the configured servers, select the server from the list and click Delete All. This action deletes all the configured DNS servers that are available in the system. Configure SNMP server To configure or edit an SNMP server: 1. Select the SmartFabric instance > Global Settings > SNMP. The page displays the list of the SNMP servers that are already configured in the OMNI VM. 2. Click Add to configure an SNMP server. 3.
The system displays the configuration success message. To delete the configured servers, select a server from the list and click Delete. Configure syslog server To configure and edit a syslog server: 1. Select the SmartFabric instance > Global Settings > Syslog. The page displays the list of the syslog servers that are already configured in the OMNI VM. 2. Click Add to configure syslog server.
3. Enter the IP address of the syslog server and log level. 4. Click Add. The system displays the configuration success message. Edit syslog server You can edit the log level for the syslog server. 1. Select the server from the list and click Edit. 2. Edit the log level of the server and click Update. To delete the configured servers, select the server from the list and click Delete.
Edit fabric settings With 2.1 and later releases, you can edit default settings of a SmartFabric instance. Use the following procedure to edit the global fabric configuration settings: NOTE: Any changes to the default fabric settings reboot all the switches in the network fabric. 1. 2. 3. 4. 5. Click the SmartFabric instance for which you want to edit the global default fabric settings. Click Global Settings > Fabric Settings. Click Edit. Edit the values of the default settings. Click OK.
The system prompts for confirmation to continue. After you click OK, all the switches in the network fabric reload to apply the fabric setting changes. The changed settings are applied only after a reboot. Update default fabric, switch names, and descriptions SFS assigns unique names for the network fabric, racks, and switches automatically. With 2.1 and later releases, you can edit the default fabric and switch names, and descriptions of a SmartFabric instance.
6. Edit the name and description of the switches. 7. Click Finish. NOTE: If you change the switch name in the UI, the hostname on the switch CLI is also updated. View fabric events and compliance status Starting from 2.0 release, OMNI displays the list of fabric events and compliance checks for each SmartFabric instance. Download the events and compliance errors NOTE: This option is available only when OMNI is accessed as a stand-alone application.
View fabric events OMNI UI lists the events that are generated for each SmartFabric instance. This feature is supported from SmartFabric OS10.5.0.7 version and both on L2 and L3 personality. To view the latest events, select the SmartFabric instance > Serviceability > Fabric Events. The table lists the latest events with detailed information including switch name, service tag of the switch, severity, time, and the event message.
8 OMNI automation support for PowerEdge MX SmartFabric Starting from 2.0 release, OMNI manages fabric automation for ESXi hosts deployed within the Dell EMC PowerEdge MX solution when running SmartFabric Services. For any change to the port group configuration in vCenter, OMNI automatically associates the VLAN to the applicable host-connected ports on the switch.
1. Click OMNI Home > OME-M. 2. Click Create to create an OME-Modular service instance by adding the IP address or DNS name of the lead chassis. If the OME-Modular instance IP address is a virtual IP address, use the virtual IP address to create the instance. 3. Enter the OME-Modular IP address, name, username, and password. 4. Click Add. The system displays OME-Modular instance creation success message. OME-M page displays the list of the service instances available in the OMNI appliance.
The system displays OME-Modular instance edit success message. OME-M page displays the list of the service instances available in the OMNI appliance. Delete OME-Modular instance You can delete OME-Modular instance from OMNI. 1. Select the OME-Modular instance that you want to delete and click Delete. 2. Click Delete to confirm. The system displays OME-Modular instance delete success message.
You can also view the relationship information between the registered vCenter and the OME-Modular. For more information, see View relationship status. OMNI automation services for OME-Modular After you add an OME-Modular instance and register the respective vCenters, OMNI creates automation services for the added vCenter instances. You can view the vCenter automation services from OMNI Appliance Management UI. For more information, see here.
Table 19. OMNI automation scenarios (continued) Configuration scenarios OMNI automation action On removal of OMNI-created VLAN from an uplink in OMEModular During synchronization, OMNI adds the VLANs back to the corresponding uplink in OME-Modular. View OMNI-created VLANs in OME-Modular You can use OME-Modular console to view the configuration changes done by OMNI as part of automation.
9 OMNI automation support for NSX-T Starting from 2.0 release, OMNI manages fabric automation for NSX-T. NSX-T is a network virtualization product of VMware that programmatically creates, deletes, and restores software-based virtual networks. For more information about NSX-T, see VMware product documents. Prerequisites Ensure that the following prerequisites are met to support OMNI automation services for NSX-T: ● For OMNI 2.1 release, the SmartFabric OS10 version running on the PowerSwitches should be 10.
The system displays NSX-T instance creation success message. NSX-T page displays the following information: ● ● ● ● NSX-T Instance—Displays the list of IP address or FQDN of the NSX-T instance. NSX-T Name—Displays the name of the NSX-T. User Name—Displays the username for NSX-T. Maintenance Mode—Displays the Maintenance mode of the NSX-T instance. ○ Gray—Maintenance mode is Off or disabled. ○ Green—Maintenance mode is On or enabled. ● Config Status—Displays the status of the NSX-T configuration.
Enabling Maintenance mode prevents OMNI from configuring networks on the instance when there are changes in the vCenter port groups and disables the UI navigation for that instance. Edit NSX-T instance You can edit the name of the NSX-T instance. 1. Select the NSX-T instance that you want to edit and click Edit. 2. Enter the required details and click Submit. The system displays NSX-T instance edit success message. Delete NSX-T instance You can delete NSX-T instance from OMNI. 1.
As part of automation, OMNI does the following automation tasks: ● Creates host and edge overlay networks. OMNI notifies the creation of host and edge overlay NSX-T networks using UI alerts. You must configure the L3 properties of the overlay networks manually. NOTE: In NSX-T deployment, when you add a host to a new rack, you must update the L3 properties of the host overlay network for the new rack manually. ● Creates edge uplink networks with IP address configured.
Table 20. OMNI behavior (continued) Manual configuration Behavior Alert message Recommendation Create a routes policy for NSXT Tier-0 interface. If OMNI identifies an existing route policy with the same peer interface details and AS number, it uses the existing policy and does not create a route policy. — — If OMNI identifies a route policy that has the same name that OMNI wants to use, but contains a different peer ASN and interface IP address details, OMNI notifies the information as alerts.
2. Click Multi-Rack L3 VLAN to see the list of the NSX-T networks that are synchronized by OMNI. 3. Edit the host and edge overlay networks and assign IP address manually for host and edge overlay. To edit the Layer 3 settings, see Configure multi-rack L3 VLAN. Click Go to Server Interface to go to the Server Interface configuration of the SmartFabric instance. Configure server interface profiles and edit the networks from this page, see server interface profile.
10 Lifecycle management This chapter explains common lifecycle operations of upgrading the SmartFabric OS10 and OMNI appliance, replacing a switch, and backup and restoring the SmartFabric. NOTE: The Lifecycle management features are not supported on OME-Modular instances. For more information, see OMNI feature support matrix. Using Life Cycle Management menu, you can: ● ● ● ● Change SmartFabric password. Upgrade SmartFabric OS10 image. Replace a switch in a network fabric. Fabric backup and restore.
1. Select the SmartFabric instance > Life Cycle Management > Upgrade OS. 2. Click Upload to upload the .bin file. 3. Click Choose File to upload the file to OMNI. 4. Click Upload. The system displays the upload progress. Upgrade fabric Click the informational icon to see the current SmartFabric OS version.
1. Select the .bin image and click Upgrade Fabric. NOTE: Upgrade Fabric option upgrades all the switches in a network fabric. You cannot stop the upgrade after it is triggered. 2. Click Upgrade to confirm. Dell Technologies recommends you to take the backup configuration using Backup and Restore before initiating the upgrade. The system displays fabric upgrade success message. After you initiate the fabric upgrade, you can see the progress of the upgrade from this menu.
1. Identify the OS10 switch to be replaced and label each of the cables with the port numbers before disconnecting the cables. 2. Back up the following configurations from the faulty switch to configure the new switch with the same details: ● Hostname ● Management IP address ● DNS and NTP IP addresses if configured ● Spanning-tree mode NOTE: In SmartFabric Services mode, RPVST+ is enabled by default on the uplink interfaces. ● Other nonfabric commands 3.
10. After ensuring all the configurations are up and running, login to OMNI. From OMNI Home > SmartFabric instance > Life Cycle Management > Replace Switch to complete the switch replacement workflow. 11. Select the switch that you want to replace from the list, select the new switch, and click Replace. The system displays switch replace success message.
The system displays local repository configuration success message. Set a remote repository 1. 2. 3. 4. 5. 6. From Backup and Restore tab, click Set Repository. Select Remote. Select the protocol (FTP, SCP, or STFP) from the list. Enter the Hostname, Username, and Password details. (Optional) Enter the Repository Path details. Click Submit.
The system displays remote repository configuration success message. Edit repository You can edit the repository type that is already set: 1. From Backup and Restore tab, click Edit Repository. 2. Edit the repository type, enter the required details if prompted, and click Edit. NOTE: When you edit the repository from local to remote, the backup files from the local OMNI VM are transferred to the remote repository.
The backup file is stored as a JSON file. NOTE: The backup action stores SFS-applied configuration for the whole fabric. Any OS10 system configuration that is done on the individual switches directly has to be backed up using the OS10 CLI. For more information about how to backup the configuration, see Dell EMC SmartFabric OS10 User Guide. 5. The system displays backup completed success message. Download backup You can download a backup file from the OMNI stand-alone VM to the local system.
2. Enter the description and choose the file that you want to upload. 3. Click Upload. The system displays upload file success message. NOTE: OMNI displays error if the uploaded file is not in the JSON format. Restore from a backup file You can restore the configuration running on the SmartFabric using a backup file during unexpected error situation or disaster. CAUTION: Restore action is disruptive and cause connection downtime and traffic loss.
NOTE: The restore action reboots all the switches with the applied fabric settings. Any manual configuration that are performed directly on individual switches has to be restored manually using the OS10 CLI. For more information about how to restore the configuration, see Dell EMC SmartFabric OS10 User Guide. 3. (Optional) Click Get Diff to compare the current configuration with the configuration in the backup file.
2. 3. 4. 5. Save the following details: ● IP address or hostname of the SmartFabric instances that are manually added in the OMNI VM. ● IP address or FQDN information of all the vCenters that are registered with the OMNI VM. ● IP address or hostname of the OMNI VM. ● Details of the ens192 and ens160 interface settings. Unregister the vCenter from OMNI VM, see here. Shut down the older OMNI VM. Deploy the new OMNI VM using the latest OMNI OVA file, see Create OMNI virtual appliance.
3. Enter the SCP server IP address or hostname, username, and the path to the upgrade .zip file and password. 4. Verify all information, then enter Y to continue. 5. Verify the OMNI version. 6. After you upgrade OMNI, close the active OMNI browser. Open a new browser and log in to OMNI to see the new or upgraded UI changes. 7. Unregister and register the vCenter again using OMNI UI, see Register vCenter with OMNI. Before upgrading to OMNI from 1.3 to 2.
1. Go to vCenter and shut down the OMNI VM. 2. Click the Edit Settings menu from the OMNI VM page. 3. Change the Memory and Hard disk 1 settings. Set Memory to 8 GB and Hard disk to 80 GB. NOTE: When you upgrade OMNI VM using .ova file, you do not have to change these settings as it is installed automatically with the above configurations.
4. Power On the OMNI VM after setting the required configurations.
11 Troubleshooting Use the following information to troubleshoot some of the common problems that occur with vCenter and OMNI appliance connectivity, OMNI UI launch, SmartFabric instance configurations, and OMNI automation. Troubleshooting tools Use the following tools when you run into any issues or during troubleshooting. Logs and support data for troubleshooting You can generate a support bundle with error and debug logs using OMNI. These logs can help you to identify, diagnose, and debug problems.
a. From the OMNI management menu, enter 2 to go to the Interface configuration menu. b. Enter the selection as 1 to view the interfaces and press Enter.
c. Enter 2 to view the connection status. The status should be up and connected. Unable to add SmartFabric instance in OMNI Problem Not able to add the SmartFabric instance in OMNI. Causes ● SmartFabric instance is not reachable or is down. ● IP address of the SmartFabric instance is not the master node IP address. Resolution ● Ensure that the SmartFabric is reachable. To check the SmartFabric connectivity: 1. Log in as root user through the OMNI VM console. 2.
Resolution ● Check the relationship status between the vCenter and service instances. For more information, see Relationship information. If the relationship is not formed correctly, try the following: ○ Click Recalculate Relationship so that OMNI can recalculate the relationship between the entities manually. ○ Delete and reconfigure the SmartFabric instance and vCenter. ● Wait for 20 minutes. The self-correction monitor mechanism in OMNI should correct this issue within 20 minutes.
● Check if the OMNI essential services are running using Appliance management UI. If OMNI UI is not accessible, check the OMNI management service status on the OMNI VM console. To check the services status: 1. From the OMNI management menu, enter 3 to select the OMNI management service menu. 2. Enter 4 to restart all the database and web essential services. NOTE: To restart the automation services, go to OMNI Appliance Management UI and restart the services. 3.
Unable to register the vCenter in OMNI Problem Unable to register the vCenter in OMNI. Causes ● vCenter server network (ens160) is not assigned a correct port-group during deployment. ● IP addresses assigned to the OMNI interfaces (ens160 and ens192) exist on the same network as of docker default private network (172.16.0.0/25). ● DNS entries with two or more FQDN names for a vCenter IP address. Resolution ● Ensure that ens160 is connected to the vCenter server network properly during OMNI deployment.
1. From the OMNI management menu, enter 2 to go to the Interface configuration menu. 2. Enter 4 to view the NTP status. 3. If the NTP server is not configured to the correct data center, enter 5 to configure the NTP server, and enter the valid NTP server IP address or hostname.
Reset OMNI VM password To change the log-level from the OMNI console: 1. Reboot the VM from vCenter and select Advanced Options for Debian GNU/Linux. 2. Use the arrow keys to go to the line starting with linux and ending with ro quiet.
3. Append init=bin/bash after ro quiet. 4. Press Ctrl-X to boot into the shell with root access. 5. Remount the directory.
6. Change the password for admin using passwd admin. Enter the new password and confirm the password. 7. Reset the VM from vCenter and log in through the new password for the OMNI VM.
