OpenManage Network Integration for SmartFabric Services User Guide Release 2.0 December 2020 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. © 2020 Dell Inc. or its subsidiaries. All rights reserved. Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries.
Contents Chapter 1: Change history............................................................................................................. 5 Chapter 2: Overview of OMNI, SFS, VxRail, and PowerEdge MX.................................................... 7 Chapter 3: SmartFabric Services................................................................................................. 10 SFS for leaf and spine fabrics...........................................................................................
Chapter 9: OMNI support for SmartFabric instances................................................................... 90 OMNI feature support matrix..........................................................................................................................................91 View SmartFabric instance overview ...........................................................................................................................91 View node details..............................................
1 Change history The following table provides an overview of the changes to this guide from a previous OMNI release to the OMNI 2.0 release. For more information about the new features, see the respective sections. Table 1. New in 2.0 Revision Date Feature Description A00 2020–12-16 OMNI automation support for PowerEdge MX SmartFabric OMNI manages fabric automation for ESXi hosts deployed within the Dell EMC PowerEdge MX solution.
Table 1. New in 2.0 (continued) Revision 6 Date Change history Feature Description Configure docker private network settings View and configure docker private network settings on the OMNI appliance. Fabric compliance View fabric compliance status and the recommended action for each SmartFabric instance.
2 Overview of OMNI, SFS, VxRail, and PowerEdge MX Enterprises are adopting the power of automation to transform their IT operations, and enable a more agile and responsive infrastructure in their data center. Network operators must leverage the power of automation within and across their departmental functions, delivering integrated solutions which cater to cloud-based consumption models.
○ 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. ○ Protection from human-error due to predictable and repeatable HCI fabric experience.
● 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.
3 SmartFabric Services SFS offers plug and play data center network fabric deployment, expansion, and management of Dell EMC infrastructure as turnkey solutions. SFS is a component of SmartFabric OS10 that provides the framework to automatically deploy the network as a single logical entity which enables the integration of Dell EMC infrastructure solutions. SFS offers turnkey network solution for data center infrastructure using Dell EMC PowerSwitch and PowerEdge MX data center switches.
Enable SFS This information describes how to enable SmartFabric Services. To enable SFS on a switch from the SmartFabric OS10 command-line interface (CLI), use smartfabric l3fabric enable command and set a role. In SmartFabric mode, the two leaf or ToR switches are automatically configured as a VLT pair, and the VLT interconnect link (ICL) ports must be physically connected before enabling SFS.
In a single SFS domain, there is only one Master switch at any given time, and the rest of the leaf switches are designated as the backup. A new Master is elected from the backup switches when the Master fails to provide high-availability to the fabric. NOTE: Spine switches cannot be elected as a Master node within SFS. Master advertisement Once a Master is elected, it initiates all applications to automatically build the network fabric.
In a single rack deployment, VLT fabric shows two leaf switches and network fabric shows all the switches. The rack has a network fabric and the VLT fabric represent the same set of switches. In a multi rack deployment, each rack has a VLT fabric, and all the VLT fabrics and the spine switches together form the network fabric. Default fabric settings SFS automatically builds the network fabric using industry-standard Layer 2 and Layer 3 protocols.
Default client control traffic network SFS sets up a second overlay network that is called client control network for VxRail integrated solutions. When a VxRail node is discovered, it is automatically added as a tagged member of this network. SFS also enables the mDNS Avahi service on this network for master advertisement and fabric discovery by integrated solutions. The SFS Master virtual IP for VXLAN network is advertised.
Dynamic Discovery - Devices that support dynamic discovery send a Dell-specific LLDP TLV. Supported devices are automatically populated in the SFS UI and OMNI by MAC address, switch, and switch port number for onboarding to the fabric. Devices that do not send the Dell-specific LLDP TLV must be manually added to the fabric. Onboarding - Onboarding is the process of adding devices to the fabric through the creation of server interface profiles.
Table 5. SFS personality comparison (continued) SFS VxRail L2 single rack personality SFS L3 leaf and spine fabric personality stretched networks for single rack deployments. VLAN-based networks in a rack can be created through OMNI. Existing deployments when upgraded to SmartFabric OS10 10.5.0.5 continue to run in L2 mode. L3 fabric capabilities are not available. Migration from VxRail L2 personality to L3 fabric personality is not available with SmartFabric OS10 10.5.0.
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.
Table 7. Number of supported instances Entities Number of instances supported by OMNI vCenter 8 SmartFabric instances 15 OME-Modular instances 1 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). NOTE: The OMNI plug-in or SmartFabric Services user interface does not provide localization. When upgrading from older version to 2.
4. Select Local file, click Choose Files, select the OMNI ova file from a local source, and click Next. 5. Select a name and folder for the VM, and click Next.
6. Select the destination compute resource, and click Next. 7. Review and verify the template details, and click 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. Upgrade OMNI appliance This section explains how to upgrade the OMNI appliance in two ways. When upgrading OMNI VM from 1.3 to 2.0 version, you can install the OMNI .ova file using new installation or upgrade OMNI. Upgrade OMNI - new installation Follow the below steps when upgrading OMNI appliance from older version (1.1 or 1.2) to 1.3 and later versions. 1. Prerequisite 2. 3. 4. 5.
The display lists all the applications which can be upgraded along with the old and new versions. Upgrading requires restarting the services. 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.0 version using this upgrade workflow, change the hardware profiles for the VM. To change the hardware details, follow these steps: 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. Set up OMNI This information describes how to log in to the VM console, and also explains the OMNI vCenter setup.
1. Enter admin for both the default username and password. 2. If it is a first-time login, the system prompts for password change. After the passwords are successfully updated, self-signed certificates are created. You can change the certificates later with OMNI management menu options, see Generate and Install SSL certificate. NOTE: The sudo password is the same as the password set for the admin user. NOTE: Root user is disabled by default.
Network interface profile configuration 1. Select 0. Full Setup. 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. Change the IPv4 configuration from Automatic to Manual from the drop-down. 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.
6. Click Show to the right of IPv4 configuration, then click Add. 7. Set the Manual IPv4 address with subnet mask information, Gateway address, DNS servers, Search Domains, then click Edit to the right of Routing. NOTE: Ensure that the IPv4 address is set with subnet mask in the prefix-length (/xx) format.
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. NOTE: If you are setting the hostname of OMNI, ensure you have the DNS entry of the OMNI hostname. 5. Enter omni for the hostname, and click OK. 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/16.
Table 8. OMNI appliance console CLI menu (continued) Menu option Submenu option Description NOTE: Dell Technologies recommends using the OMNI 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.
1. From the OMNI management menu, select 4. Password/SSL configuration menu. 2. Enter the selection as 3. Generate self signed SSL certificates. OMNI VM displays confirmation for replacing the existing certificate and key with the newly created certificates and keys. 3. Unregister and register the vCenter again using OMNI UI to apply the new SSL certificate. NOTE: Refresh the browser to view the OMNI UI plug-in from the vCenter when you register or unregister OMNI appliance with vCenter 7.0.
Install SSL certificate from remote server To install SSL certificate from remote server: 1. Generate SSL certificate using a standard method in .pem or .crt formats. 2. Copy the generated files to the remote SCP server. 3. From the OMNI management menu, select 4. Password/SSL configuration menu. 4. Enter the selection as 4. Install SSL certificate from remote server to install the certificate. Enter the remote SCP server IP address or hostname and login to the SCP server.
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. 6. Unregister and register the vCenter again using OMNI UI to apply the newly installed SSL certificate. NOTE: 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.
2. From the OMNI management menu, select 2. Interface Configuration Menu. 3. Select 0. Config Docker Private network.
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.
4. Enter the private network IPv4 network address for docker in A.B.C.D format with subnet mask in prefix-length /xx format. 5. OMNI reboots automatically to implement the latest docker private network configuration.
5 OMNI vCenter integration This information describes the OMNI vCenter integration to automate vCenter PortGroup VLANs. vCenter VSS and DVS PortGroups When you configure PortGroups of a virtual standard switch (VSS) with VLANs and distributed virtual switch (DVS) with VLANs on the OMNI registered vCenter, the respective active and standby physical adapter interfaces are automatically configured by OMNI on the SmartFabric ServerInterfaces. This is shown as tasks on the registered vCenter tasks pane.
a. OMNI sets Network Originator to Manual when you create a network using OMNI UI. b. OMNI sets Network Originator to Auto when OMNI vCenter PortGroup automation creates a network. 4. Appends networks that are not created by the OMNI UI (all networks except the network that has Network Originator set to Manual) to SmartFabric uplink of the type Default or CreateOnly. OMNI automates network addition on one of the fabric uplinks.
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 UI, 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.
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. As an initial step, you must configure OMNI IP address or FQDN first to proceed with any other configuration in OMNI, see Configure OMNI.
2. Enter the IPv4 address or FQDN of the OMNI and click Submit. 3. The system displays the OMNI address details and also enables all other options in UI. 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 8 vCenters in a single OMNI VM. To register the vCenter with OMNI: 1. Go to OMNI Home > vCenter Instance. 2. Click Add to register the vCenter. 3.
5. 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.
1. Select the vCenter instance that you want to edit and click Edit. 2. Update the password and click Edit. Delete a vCenter instance To delete the vCenter configuration: 1. Select the vCenter instance that you want to delete and click Delete.
2. Click Delete to confirm the deletion. 3. The system displays deletion success message. Unregister vCenter To unregister the OMNI from vCenter: 1. Go to OMNI Home > vCenter instance, select the status information Registered of the vCenter you wanted to unregister. 2. Click Ok to unregister the OMNI from the vCenter. 3. The system displays status change success message.
The status and the Maintenance mode for the vCenter changes to Not Registered and Under Maintenance respectively. When you unregister the vCenter, OMNI stops the automation services for that vCenter. NOTE: When you unregister the vCenter, the OMNI plug-in is undeployed from vCenter. With vCenter 7.0, refresh the browser to see the change. For older versions of vCenter, log out and log in to see the changes.
1. Go to Home > vCenter Instance and click Under Maintenance for a specific vCenter instance. 2. Click Ok to confirm. The vCenter status changes to In Service and OMNI starts the automation service for the vCenter. 3. 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.
NOTE: This configuration is applicable only for VxRail deployment and not for PowerEdge MX environment. When you launch the OMNI plug-in from vCenter for the first time after registering, the autodiscovered SmartFabric instance is disabled. You must edit the instance and change the REST_USER password to proceed. Edit the autodiscovered SmartFabric instance for the REST_USER password to complete the configuration. 1. Go to the OMNI portal. 2.
MASTER-IPV4 : 10.11.180.8 PREFERRED-MASTER : true ---------------------------------------------------------2. Go to the OMNI portal. 3. From OMNI Home > SmartFabric, click Create to manually add the master IP address of the SmartFabric instance. 4. Enter the SmartFabric instance IP address, SmartFabric name, username, and password. 5. (Optional) Select Register for SFS events checkbox to retrieve the SFS events and display through OMNI. Click Add. 6.
NOTE: The compliance status feature is supported from SmartFabric OS10.5.2.2 version onwards. OMNI displays the compliance status information for the SmartFabric instance only if the version running on the switches is OS10.5.2.2 or later. If not, the compliance status is displayed as N/A. 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. 3.
1. Select the SmartFabric instance from the list and click Delete. 2. Click Delete to confirm. 3. The system displays SmartFabric instance update success message. SmartFabric Maintenance mode Enabling Maintenance mode prevents OMNI from configuring networks on SmartFabric when there are changes in the vCenter port groups and disables the UI navigation for that instance. The OMNI Home > SmartFabric page displays the mode of each SmartFabric instance added in the OMNI VM.
2. Click Ok to confirm. The SmartFabric instance mode changes to Under Maintenance. During Maintenance, the SmartFabric UI navigation is disabled and the automation services is stopped for the instance. Disable Maintenance mode To disable Maintenance Mode for a SmartFabric instance: 1. From OMNI Home > SmartFabric, click Under Maintenance for a specific SmartFabric instance. 2. Click Ok to confirm. The SmartFabric instance mode changes to In Service.
with vCenter. In this example, if vCenter2 does not have any host that is connected to SmartFabric instance added to OMNI, you can only register the vCenter and disable the automation. ● Dell Technologies recommends using stand-alone OMNI UI to unregister all the vCenters that are linked through ELM. Host network inventory You can view information about physical Dell EMC PowerSwitch infrastructure running SmartFabric OS10.
● 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. When you select a server physical adapter from the Host Network Inventory, the page also displays the information that is related to physical switch connected to the selected physical NIC.
● ● ● ● 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 the switch port View service instance and vCenter relationships Starting from 2.
OMNI Information You can view the links to documentation and end-user license agreement (EULA).
1. Click EULA to view the end-user license agreement. 2. Click Documentation to see the documents that are uploaded at www.dell.com/support OpenManage Network Integration product page. OMNI Appliance Management user interface From OMNI 1.3 release, a new UI—OMNI Appliance Management is introduced to manage all the system, web, and automation services running in the OMNI. After you create the OMNI virtual appliance and complete the virtual appliance setup, you can launch the OMNI appliance management UI.
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.
Table 10. List of OMNI services Service Function States omni_api Service serving REST APIs for OMNI Fabric Management interface. Can restart the services. omni_services Orchestration service that provides APIs to start, stop, and manage all OMNI services. omni_events_receiver Events receiver service receives events from the SFS and store in the message queue. omni_api_celery_worker Worker service that conducts fabric upgrades and vCenter re-registration when registration data is updated.
Click Refresh icon to update the data and display the updated contents. Start vCenter automation services To start the fabric automation services: 1. From the OMNI Appliance Management UI, click Services tab menu. 2. Select the automation service that you want to start, and click Start. After you start the service, OMNI starts monitoring the networking events for the registered vCenter. 3. The system displays start service success message.
2. (Optional) Click Error under log-level of each service to modify the log-level to Debug. 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.
Access the OMNI stand-alone portal
7 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. From OMNI Home > OME-M, 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. 2. Enter the OME-Modular IP address, name, username, and password. Click Add.
3. The system displays OME-Modular instance creation success message. OME-M page displays the list of the service instances available in the OMNI appliance. Disable OMNI automation for OME-Modular Disable automation for the OME-Modular instance by changing the mode from In Service to maintenance mode. To do so, click the mode In Service and agree to move the mode to Under Maintenance. Enabling Maintenance mode stops the automation service for that instance and also disables UI navigation for that instance.
2. Enter the required details and click Submit. 3. 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. 3. The system displays OME-Modular instance delete success message.
View OME-Modular instance To view the details of the OME-Modular instance, select the OME-Modular instance. OMNI displays a link to OME-Modular console, and you can launch the OME-Modular console by clicking the link. You can also view the relationship information between the registered vCenter and the OME-Modular. For more information, see View relationship status.
Table 11. OMNI automation scenarios (continued) Configuration scenarios OMNI automation action NOTE: In vCenter, trunk VLAN or private VLAN for port groups is not supported. ● OMNI associates the newly created vCenter VLAN to the SmartFabric Ethernet uplinks and related servers. NOTE: OMNI does not associate VLANs to the SmartFabric uplinks when there is more than one Ethernet uplink in the SmartFabric. Assign VLANs manually to the uplinks using the OME-Modular UI.
8 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: ● The SmartFabric OS10 version running on the PowerSwtiches should be 10.5.2.
2. Enter the NSX-T Manager cluster virtual IP address or FQDN, name, username, and password. Click Add. 3. The system displays NSX-T instance creation success message. NSX-T page displays the list of the instances available in the OMNI appliance. Disable OMNI automation for NSX-T Disable OMNI automation for the NSX-T instance by changing the mode from In Service to maintenance mode. To do so, click the mode In Service to change it to Under Maintenance.
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. 3. The system displays NSX-T instance edit success message. OME-M page displays the list of the service instances available in the OMNI appliance. Delete NSX-T instance You can delete NSX-T instance from OMNI. 1. Select the NSX-T instance that you want to delete and click Delete. 2. Click Delete to confirm. 3. The system displays NSX-T instance delete success message.
OMNI automation for NSX-T After you add the NSX-T Manager as an instance in OMNI, OMNI automation discovers the relationship between the entities such as NSX-T Manager, vCenter, and the SFS instance. NOTE: It may take few minutes to populate the relationship information and the related networks that are created by OMNI automation. As part of automation, OMNI: ● Creates host and edge overlay networks. ● Creates edge uplink networks.
In the left pane, under OMNI Home, select the NSX-T instance to view the list of networks that are created by OMNI automation. OMNI displays the vCenter information that is related to the specific NSX-T instance. You can click the vCenter to see the SmartFabric instances that are associated with that instance. When you click a SmartFabric instance, OMNI displays the list of networks that are synchronized from NSX-T and the server interface profiles that are tagged to the NSX-T networks.
Create edge peer routes Create edge peer routing IP address details for the uplinks, see Configure eBGP peer route.
9 OMNI support for SmartFabric instances 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 12.
The Overview dashboard displays information regarding the following metrics: Device Status—Displays the status of the all the devices that are deployed in the SFS 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.
From Fabric Nodes, view the list of spine and leaf nodes that are deployed in the fabric. Each switch includes status (online or offline), name, model, version, role, and IP address. Click Domain at any time to update the fabric details. 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. From the SmartFabric instance, select Topology to view the graphical representation of the fabric. The topology view displays the graphical icons of all the nodes and the link connectivity between the nodes. Each graphical node is represented with their service tag.
Manage switches in a fabric You can manage the spine and leaf switches available in a fabric. From Switches page: ● ● ● ● ● ● View the details of the switches and the ports in a fabric. Edit the interface details. Set the MTU value for the port. Manage the unused ports in the switches. Configure breakout ports in leaf switches. Configure jump port. View switch and port details View the details of the leaf and spine switches, and the list of all ports and unused ports available in each switch.
Spine Switches—Displays the list of all spine switches with ports information in categories. Click the arrow of the respective switch and category to view more about port information. 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.
2. Select the spine or leaf switch by clicking the arrow to view more information. 3. Select a port from All Ports category, and click Edit.
4. Edit the name, description, admin status, auto negotiation, and MTU, and click Edit. Configure auto negotiation status You can enable or disable the auto negotiation on a single port or multiple ports.
1. From All Ports, select a port or multiple ports and click Enable Auto Neg. 2. The system displays a warning message. Click Yes to confirm. 3. The system displays the stage-wise progress of the interface status. To disable auto negotiation: 1. From All Ports, select a port or multiple ports and click Disable Auto Neg. 2. The system displays the stage-wise progress of the interface status.
Set MTU value Set maximum transmitting unit (MTU) for the port. 1. Select a port or multiple ports and click Set MTU. 2. Enter the MTU value and click Set.
3. The system displays a warning message. Click Yes to confirm. 4. The system displays the action success or failure message. Manage unused switch ports You can view and manage the unused ports in the switches. To enable or disable unused ports: 1. 2. 3. 4. From the SmartFabric instance, select Switches. Select any spine or leaf switch by clicking the arrow to view the list of ports. Click Unused Ports category to view the list of unused ports available in the switch.
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.
3. From Breakout Port and Jump Port category, select a port that you want to breakout, and click Breakout port. NOTE: While configuring a breakout port, the existing configuration of the port is reset to default.
4. Select the Breakout Mode for the port from the list, and click Submit. 5. The system displays breakout port configured successful or failure message. View port-group properties Select a port to view properties on the right.
Add a jump port You can configure only one port in a 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. Select the leaf switch from the list, and select the Breakout Ports & Jump Port category.
2. Select the switch to view the properties, and click Jump Port.
3. Enter the Name of the new jump port, select the Interface Name, select the Untagged Network, then click Add. 4. 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. 3. The system displays jump port deletion success message. 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.
1. From SmartFabric instance, select Server Interface. 2. Click Create to create a server interface profile and provide server interface ID, then select Existing Server Profile. NOTE: You cannot configure duplicate server interface ID. When using MAC address to onboard server interface, enter MAC Address without ":", for example, f8f21e2d78e0. For onboarding ESXi host Interfaces for zero touch automation, use the ESXi host VM NIC physical adapter MAC address without ":". 3.
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.
4. Edit the Untagged Network and the Network configuration for the profile, and click Edit. 5. The system displays the server interface profile update success message. Edit ports on a server interface profile 1. Select the server interface ID from the list, and click Edit Ports. 2. Edit the Static Onboarding Option and the NIC Bonding configuration for the profile, and click Edit. 3. 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. To delete: 1. Select the server interface profile from the displayed list, and click Delete. 2. Click Delete to confirm. Import ESXi host profiles from vCenter Automate onboarding of server interface profile by importing: Use this feature to migrate the existing ESXi hosts that are already connected to the vCenter and ready to be onboarded on to the fabric.
2. Click Import from vCenter to launch the Onboarding ESXi Hosts wizard. 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. (Optional) If the static onboarding is Yes, select Leaf Node and Interface (where the server interface is connected), select the Routing Protocol. ● (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.
9. Click Finish after all the configurations are complete. 10. 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 the servers are connected to the fabric, SFS discovers the servers automatically, and OMNI onboards the discovered servers as part of this workflow.
2. Click Import from Fabric. Discovered Server Interface window appears with the list of discovered interfaces. NOTE: The interface that is already associated with a server interface profile is not listed in the discovery table. 3. Edit the server profile information of each interface using the Edit option available at the end of each row. 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.
● (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 one or more discovered interfaces, and click Add to Server Profile. 2. Select the server profile to which you want to add the discovered server interfaces. ● Select Existing Server Profile—Select the Server Profile Id to associate the interface with the existing server profile, and click Associate.
NOTE: Add networks overwrite the existing networks of all the server interface profiles. 3. The system displays the server interface networks addition success message. Remove from server profile 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.
Create L2 Uplink You can create an uplink by selecting the fabric with a unique name, and select the interfaces, and networks to create a user uplink. 1. Select the SmartFabric instance >Uplink, and click Create.
2. Enter the uplink port type as L2, a Name, an optional description, then click Next. 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. 7. The system displays user uplink creation success message.
1. Select the SmartFabric instance > Uplink, and click Create. 2. Select L3 for the uplink port type, select L3 VLAN, enter the name for the uplink, and optional description, then click Next. 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.
Spine: 130 OMNI support for SmartFabric instances
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. 5. 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.
Leaf: Spine: 132 OMNI support for SmartFabric instances
4. Enter the network profile information and routing policy information for the uplinks, then click Finish. 5. 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. 3. 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. 3. The system displays the uplink interface edit success message. Delete an uplink You can delete a user-created uplink. To delete: 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.
The OMNI vCenter PortGroup VLAN automation process does not add Manual networks to auto uplinks, and does not remove them from SmartFabric. Add Manual networks to uplinks using the OMNI portal if needed. The OMNI VLAN automation process uses Manual networks for ServerInterfaces. If you are using the VLANs for the OMNI registered vCenter PortGroup, it is not recommended to use the OMNI portal to create a network. OMNI automation manages those VLANs or networks by itself.
Create multi rack L3 VLAN 1. From SmartFabric instance, select Networks > Multi-Rack L3 Networks, and click Create. 2. Enter the network ID, name, VLAN number, IP addresses, description, gateway IP address, and helper addresses for each rack available in the SmartFabric cluster. Click Create. 3. The system displays VLAN network creation success message. Edit multi rack L3 VLAN configuration 1. Select a network ID from the list, and click Edit.
2. Modify the details, edit the configuration as necessary, and click Edit. 3. The system displays edit network success message. Delete multi rack L3 VLAN configuration 1. Select the VLAN network to remove, and click Delete.
2. Click Delete to confirm. 3. The system displays network deletion success message. 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 it is possible to associate one VLAN with the VNI across fabric. If you delete a VLAN network, it automatically deletes the associated VXLAN network.
2. Click Create to create a Layer 2 general purpose network. 3. Enter the network ID, name, VLAN ID, and description. Click Create. 4. The system displays virtual network creation successful message. View general purpose network The general purpose networks display the VLAN details of the specific network including network ID, network name, VLAN ID, QoS priority, and network type. Portgroups that are created on the vCenter are displayed under General Purpose Networks.
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 On deletion of general purpose network, both the VLAN and the VXLAN networks are deleted from OMNI.
1. Select the general purpose network, and click Delete. 2. Click Delete to confirm. 3. 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.
1. From SmartFabric instance, select Networks > VxLAN Networks. The page displays the list of the VXLAN networks that are configured in the SmartFabric instance. 2. 3. 4. 5. Click Create. Verify Layer 2 is selected as the Virtual Network Type. Enter the text for Virtual Network Name, a value for the VxLAN VNI, and the VLT VLAN ID. (Optional) Enter a description, and click Create. 6. The system displays virtual network creation successful message.
1. Select Network from the Network tab, then click Networks > VxLAN Networks. The page displays the list of the VXLAN networks that are configured in the SmartFabric instance. 2. Click Create. 3. Select Layer 3 as the Virtual Network Type. 4. Enter the text for Virtual Network Name, a value for the VxLAN VNI, the VLT VLAN ID, prefix, gateway IP address, and helper IP address. Click Create. 5. The system displays virtual network creation successful message.
Edit VxLAN network You can edit the configuration of VXLAN network: 1. Select a virtual network from the list, then click Edit. 2. Modify the Virtual Network Type.
3. Enter the Prefix, Gateway IP Address, IP address, then click Edit. 4. 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. 3. 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. Select Networks > VLAN Networks, and click Create.
2. 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. 3. The system displays VLAN network creation success message. VLAN networks for L3 profile: 1. Select Networks > VLAN Networks, and click Create. 2.
Edit network 1. Select a network ID from the list, and click Edit. 2. Modify the details, edit the configuration as necessary, and click Edit. 3. The system displays edit network success message.
Delete network 1. Select the VLAN network to remove, and click Delete. 2. Click Delete to confirm. 3. The system displays network deletion success message. Configure L3 routed interfaces This information explains how to create, edit, and delete Layer 3 routed interfaces. Create L3 routed interface To create an L3 routed interface: 1. Select Networks > Layer 3 Routed Interfaces, and click Create.
2. Enter the Network ID, Network Name, select the Prefix Length, select the IP Address, enter an optional description, then click Create. 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, and click Edit. 3. The system displays edit network success message. Delete network 1. Select the network ID to remove, and click Delete. 2. The system displays network deletion success message.
Configure Routes You can configure static routes and eBGP peer routes for a network. Configure static routes Create static route 1. Select Network > Routing Configuration. 2. Select Static Routes, and click Create to add a new static route. 3. Enter the relevant details and click Create. 4. The system displays static route creation is successful. Add route to switch 1. Select Routing Configuration > Static Routes.
2. Select a static route, and click Add Route to Switch. 3. Select the switch to map to this route, and click Add. 4. The system displays the route added success message. Static route details The static route details display a list of mapped routes. Select a static route to view details pertaining to that specific route including the switch ID. Delete static route 1. Select the static route to delete, and click Delete.
2. Click Delete to confirm. 3. The system displays static route deletion is successful. 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. 3. The system displays route policy deletion success message.
Configure eBGP peer route You can configure eBGP peer routes for a network. Create eBGP route 1. Select Network > Routing Configuration, and click eBGP Peer Configuration. 2. Click Create to add an eBGP peer route. 3. Enter the relevant details and click Create. 4. The system displays eBGP peer route creation is successful. Delete eBGP route 1. Select the eBGP route to delete, then click Delete.
2. Click Delete to confirm. 3. The system displays route policy deletion success message. Add eBGP route to switch 1. Select an eBGP route, then click Add Route to Switch.
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. 3. The system displays route deletion success message. Configure global settings for SmartFabric Starting from 2.0 release, OMNI allows you to configure SmartFabric switch services settings using the UI. You can configure the following services on the SmartFabric switches using OMNI: ● ● ● ● NTP DNS Syslog SNMP NOTE: This feature is supported from SmartFabric OS10.5.2.
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. 4. The system displays the configuration success message. To delete an NTP server, select an entry from the list and click Delete.
Configure DNS server To configure one or more DNS servers: 1. Select the SmartFabric instance > Global Settings > DNS. The page displays the list of the DNS servers that are already configured in the OMNI VM. 2. Click Add to configure one or more DNS servers. 3. To configure a single DNS server setting, enter the IP address of the DNS server and click Add. 4. To configure multiple servers at a time, enter the IP address of all the servers using + button.
5. The system displays the configuration success message. To delete the configured servers, 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. Enter the IP address of the SNMP server, community, SNMP version, and click Add. 4. The system displays the configuration success message. To delete the configured servers, 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, and click Add. 4. The system displays the configuration success message.
You can edit the log level for the syslog server. To edit: 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, click Delete.
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. You can download all the events and the compliance errors that are listed for each SmartFabric instance from stand-alone OMNI UI. Select the SmartFabric instance > Serviceability and click Download.
View fabric compliance status SFS validates the health of the cluster, topology role, underlay, overlay, network, server appliance discovery, uplink, policy, and VLT. SFS monitors the health in both the switch and the whole fabric levels. OMNI retrieves the fabric compliance status for the SFS instance and displays the noncompliance events with details. OMNI also recommends the actions to eliminate the compliance violations or misconfigurations. This feature is supported from OS10.5.2.
2. Click the information icon to view the recommended action for each compliance error. 3. (Optional) Click Clear All to clear all the existing compliance errors. After clearing all the errors, OMNI starts to retrieve the fabric compliance status for the SmartFabric instance immediately. Click Refresh to update the data and display the new compliance errors. You can also view the fabric events and the compliance errors in the SmartFabric instance overview dashboard.
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.
You can upgrade OS using the following steps: ● Upload the latest image in the OMNI VM. ● Upgrade fabric using the uploaded image. ● (Optional) Delete the image from the OMNI VM. Upload image Upload an OS10 image to the OMNI VM: 1. Select the SmartFabric instance > Life Cycle Management > Upgrade OS. 2. Click Upload to upload the .bin file. Upgrade fabric Click the informational icon to see the current SmartFabric OS version.
Upgrade the switches in a fabric with an OS10 image: 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. 3. The system displays fabric upgrade success message. SmartFabric automatically reboots when the upgrade is complete.
Delete image Delete the OS10 image uploaded in the OMNI VM: 1. Select the .bin image to delete and click Delete Image. 2. Click Delete to confirm. 3. The system displays delete image is success. Replace switch in a fabric You can replace the faulty OS10 switch in a SmartFabric. NOTE: This instruction is applicable for SmartFabric instance only. To replace a switch in MX, follow the instructions that are provided in the MX documents. For more information, see PowerEdge MX documents.
NOTE: Ensure that the ICL ports are connected to the other leaf switch which is already in SmartFabric Service mode. 6. Enable SmartFabric Services on the new switch and define the ICL ports. ● For L2 personality—Enable SmartFabric Services on the new switch, and define the breakouts, uplinks, interlink ports, plus any other parameters such as management VLAN, LACP, VLAN tagging, and so on.
● Upload or import the fabric backup file from the local or remote repository to the OMNI VM. ● Restore the fabric from a backup file. NOTE: The fabric backup and restore features are supported from the OS10.5.0.7 version. If the OS10 software version is less than 10.5.0.7, the system displays a message that backup is not supported for the software version and all the backup and restore functions are disabled.
Set a remote repository 1. From Backup and Restore tab, click Set Repository. 2. Select Remote. 3. Select the protocol (SCP or FTP) from the list. Enter the Hostname, Username, and Password details. (Optional) Enter the Repository Path details, and click Submit. 4. The system displays remote repository configuration success message. View repository View the repository details by clicking the information icon.
Edit repository You can edit the repository type that is already set. To do so: 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. If you change the repository from remote to local, they backup files are not transferred to local OMNI VM.
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. 3. 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.
The file is downloaded locally with the backup download success message. Delete backup You can delete a backup file from the OMNI VM. 1. Select Backup and Restore tab. 2. Select the backup file that you want to delete from the displayed list, and click Delete. 3. Click Delete to confirm. 4. The system displays backup deleted success message.
Upload backup You can upload a backup file from the local system to the OMNI VM. 1. From Backup and Restore tab, click Upload Backup. 2. Enter the description and choose the file that you want to upload, and click Upload. 3. 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.
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.
11 Troubleshooting Use the following information to troubleshoot some of the common problems that occur with the vCenter and OMNI appliance connectivity, OMNI UI launch, SmartFabric instance configurations, and OMNI automation. Logs and support data for troubleshooting You can generate support bundle with error and debug logs using OMNI. These logs can help to identify, diagnose, and debug problems. Dell Technologies recommends downloading the support bundle from OMNI Appliance Management UI.
1. From the OMNI management menu, select 2. Interface Configuration Menu.
2. Enter the selection as 1. Show Interfaces and press Enter.
3. Select 2. Show 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 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.
● Check the relationship status between the vCenter and service instances. For more information, see Relationship information. If the relationship is not formed correctly, delete and reconfigure the SmartFabric instance and vCenter. ● If the southbound interface is a general ESXi server, create a server interface profile manually. If there is no server profile, no relationship is created. For more information about creating server interface profile, see server interface.
3. Select 2. View OMNI management service status to view the list of registered vCenter managed by the OMNI VM. Confirm that all services are active. NOTE: View OMNI management service status is recommended for status validation and debugging purpose. Hence, the output does not show the port numbers. OMNI plug-in does not show service instance Problem OMNI plug-in does not show any service instance even though the service instance is added to OMNI.
● vCenter server network (ens160) is not assigned with correct port-group during deployment. ● IP addresses assigned to interfaces of OMNI are on the docker private network (172.16.0.0/16). Resolution ● Ensure that ens160 is connected to the vCenter server network properly during OMNI deployment. For more information, see Setup OMNI. ● Change the docker private network configuration, see Configure docker private network.
1. From the OMNI management menu, select 2. Interface Configuration Menu. 2. Select 4. Show NTP Status. 3. If the NTP server is not configured to the correct data center, select 5. Configure NTP Server, and enter the valid NTP server IP address or hostname.
Reset OMNI VM password To change the log-level from OMNI console: 1. Reboot the VM from vCenter, then 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.
