SmartFabric Services for OpenManage Network Integration User Guide Release 1.
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 1 SmartFabric vCenter.....................................................................................................................4 2 SmartFabric Services................................................................................................................... 6 SFS for data center leaf and spine fabrics......................................................................................................................... 6 SFS initial setup........................................
1 SmartFabric vCenter 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.
• • Fully validated software stack recommendation • Protection from human-error due to predictable and repeatable HCI fabric experience Enhanced support experience • • World-class Dell EMC HCI and fabric services Fabric that is integrated into VxRail services and support experience Required components • Dell EMC PowerSwitches supporting SmartFabric Services • • • • • Leaf/ToR switches: 10 GbE — S4112F-ON, S4112T-ON, S4128F-ON, S4128T-ON, S4148F-ON, S4148T-ON; 25 GbE — S5212FON, S5224F-ON, S5248F-ON, a
2 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 network operating system that provides the framework to automatically deploy the network as a single logical entity which enables the integration of Dell EMC infrastructure solutions.
For complete information about configuring the out-of-band Management IP address and upgrading the switch operating system, see Dell EMC SmartFabric OS10 User Guide, Release 10.5.0. 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.
SFS Master SFS uses Keepalived protocol, running on VLAN 4000, to elect one in the fabric as a Master switch. Only a leaf switch can be elected as a Master. 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.
SFS domain or network fabric is interchangeable terminology, and the fabric consists of all switches directly connected to form a single logical network fabric. The L3 fabric is automatically assigned ID 100 and this ID cannot be changed. The fabric name and description are automatically assigned, but can be changed through the SFS user interface.
SFS sets up a second overlay network that is called client control network specifically 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. The VIP address is fde1:53ba:e9a0:cccc:0:5eff:fe00:1100 is fixed and not user configurable.
VxRail L2 single rack fabric Multi rack leaf and spine fabric All networks created during initialization, VxRail deployment and Day 2 operations are VLAN backed network with customer router acting as the gateway. Networks that are created during initialization and the ones created as part of VxRail deployment and vCenter integration are VxLAN stretched networks for single rack deployments. VLAN-based networks in a rack can be created through OMNI.
3 OpenManage Network Integration OpenManage Network Integration (OMNI) is a component 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 SFS instances, enabling administrators to manage and operate one or more network fabrics that are deployed with SFS.
OMNI virtual appliance creation This information describes how to deploy the OMNI appliance on a VMware ESXi hypervisor using the OMNI OVA file, then create a virtual machine (VM). NOTE: The OMNI portal or SmartFabric Services user interface does not provide localization. Download and install OVA 1. Download the OVA from OpenManage Network Integration support, then store the OVA image locally. 2.
5. Select the destination compute resource, then click Next. 6. Review and verify the template details, then click Next. 7. Accept the end-user license agreement (EULA), then click Next.
8. Select the VSAN datastore for the configuration and disk files, then click Next. 9. Select a destination network for each network source, then 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 vCenter Server network must be connected to the port group where the vCenter Server is reachable for deployment of the OMNI plug-in.
Power on OMNI VM 1. Scroll to the bottom of the window to view the status, and wait for the deployment to finish. 2. Select the OMNI VM, then select Actions > Power On. 3. Select Launch Web Console.
OMNI setup This information describes how to log in to the VM console, and also explains the OMNI vCenter setup. Log in to VM console You can configure OMNI through the VM console after you complete the authentication step. The VM console automatically closes after 10 minutes (default), and can be customized to meet your needs. 1. Enter admin for both the default username and password. 2. If this is a first-time login, change the password.
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. You can choose Automatic or Manual IP address configuration. 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, Gateway address, DNS servers, Search Domains, then click Edit to the right of Routing. 8. On IPv6 configuration, select Ignore for the IPv6 configuration, then click OK. NOTE: IPv6 configuration is only required for an in-band network.
You are now ready to continue configuration. NOTE: If you are not connecting the OMNI VM to a SmartFabric local-link, this section is not applicable and you are ready to activate the connection profile. 1. Select Wired connection 2, then click Edit. 2. Rename Profile name to VxRail Mgmt Network. 3. Select Disabled for the IPv4 configuration.
4. Select Link-Local for the IPv6 configuration. 5. Click Edit to the right of Routing, then click Add. 6. Enter the custom route as fde1:53ba:e9a0:cccc::/64, then 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, each profile must be deactivated, then activated. 1. Select Activate a Connection, then click OK. NOTE: If you make any changes while editing a connection, you must deactivate then activate the connection for the respective interface profile. 2. Select the vCenter Server Network profile, then click Deactivate; repeat for VxRail Mgmt Network. 3.
4. Click Back, then select Set system hostname, then 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, then click OK. 6. The hostname is now set; click OK. 7. Click Back, then OK to exit the network management UI. 8. Enter a valid NTP Server IP address or hostname, then click Enter. Go to the next section for the SSL certificate installation.
OMNI vCenter client plug-in registration This information describes how to register the vCenter plug-in, and SSL certificate management. SSL certificates have been automatically generated after the password is successfully updated. For more information, see Log into VM console. NOTE: Multiple OMNI instances cannot be mapped to a single vCenter instance.
5. The OMNI application server services start successful; press [enter] to continue. 6. Select 9. Logout. NOTE: You cannot register the same vCenter instance from another OMNI plug-in.
Unregister vCenter with OMNI 1. Select vCenter Server > Menu > OpenManage Network Integration > Service Instance, then select the specific Service Instance > Summary > vCenter Credentials. 2. Click Unregister. vCenter credential update of registered vCenter 1. Click Update to update the credentials of the existing vCenter. 2. Enter the required information to edit (user and vCenter fields are automatically populated), then click Update.
3. Update success; close the message.
4 OMNI virtual appliance management menu This information describes the menus available to the admin SSH user through the console. Table 3. OMNI virtual appliance management menu Menu option Submenu option 1. Show version 2. Interface configuration menu Description Display OMNI virtual appliance and plug-in version 1. Show interfaces Display OMNI network interface configuration 2. Show connection status Display OMNI network interface connection status 3.
Menu option Submenu option Description 4. Register/update OMNI vSphere client plug-in with vCenter 5. Password/SSL configuration Register OMNI with vCenter; enter OMNI IP/hostname, vCenter IP/hostname, vCenter administrator user (administrator @vsphere.local), and vCenter password. It is recommended that you use hostnames. 1. Change appliance password Change appliance admin user password 2.
5 Access to OMNI portal This information describes how to access SmartFabric vCenter through the vSphere Client. A shortcut is available from the vSphere Client left-pane within the menu dropdown and shortcuts view. Access OMNI portal using registered vCenter NOTE: Before you use the plug-in, you must set up a Dell EMC SmartFabric appliance in vSphere. Once you register OMNI with vCenter, an OMNI plug-in is available in the vCenter.
Once the vCenter registration steps are complete, you can log in to the OMNI UI using the OMNI stand-alone page. This information describes how to access the OMNI UI from a browser. 1. Open a browser session, go to https://OMNI_IP/delawareos10 with the IP configured during setup. 2. Enter the username and password for the OMNI VM, then click Sign In. Once the username and password are authenticated, the OMNI page displays.
6 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.
6. Delete unused networks from the SmartFabric. NOTE: A 'Default'/'CreateOnly' uplink can be configured on the SmartFabric through the OMNI Uplink configuration page. For more information, see OMNI SmartFabric management.
7 OMNI SmartFabric management This information provides details of how OMNI helps you manage SmartFabric OS10 with OMNI. Also explained is how you can add and configure SmartFabric instances that you want to manage using OMNI. Add SmartFabric instance This information describes how to add SmartFabric instances in OMNI. 1. Go to the OMNI portal. 2. Locate the Master IP of the SmartFabric cluster by logging into OS10 SmartFabric, then enable the switch.
Configure OMNI autodiscovered SmartFabric instance This information describes how to configure OMNI autodiscovered SmartFabric instances. If the OMNI virtual appliance is connected to a link-local network on SmartFabric (such as VxRail Management Network-VLAN 3939), find the SmartFabric IPv6 VIP autodiscovered by OMNI. For complete information about discovery, see mDNS service in SmartFabric Services.
Summary This information describes the selected fabric summary including fabric nodes, racks, and actions. Select the Service Instance to view details on each fabric. Click Domain at any time to update the fabric details. Fabric nodes This information describes the selected Spine structure which is arranged in racks. Select the Fabric ID to view the fabric details. Each Spine fabric has corresponding switches. Each switch includes status (online or offline), name, model, version, role, and IP.
Fabric actions You can do the following from the fabric actions: • • • Change SmartFabric password. Upload SmartFabric OS10 to OMNI VM. Delete SmartFabric OS10 image. • For more information about upload and delete SmartFabric OS10 image, see Upgrade SmartFabric OS. Replace switch on a network fabric. For complete information about replacing a switch, see Replace switch on network fabric. SmartFabric password change 1.
2. Mouse over a fabric to display switch details. 3. Select any switch to view the network information. Switches This information describes how to display fabric for all Spine and Leaf switches. Switch information includes destination interface and breakout profile. Select a switch to view details about the specific switch including breakout details and corresponding information about interface status, MTU, and type. 1. Select the Service Instance, then select Switches. 2.
4. Use the arrow to view the properties. 5. Select the interface/port-group to view properties on the right. Breakout port NOTE: The auto breakout feature is enabled by default in Spine switches. OMNI will not provide an option to break out Spine switches. 1. Select Breakout port, select the Breakout Mode from the drop-down, then click Submit.
2. Breakout port successfully configured; success/failure tooltip notification message displays. 3. Select the number of ports to view by page. Add jump port 1. Select the switch to view the Leaf switch properties and the current jump port, then click Jump Port. 2. Enter the Name of the new jump port, select the Interface Name, select the Untagged Network, then click Add. 3. Jump ports add success; success/failure tooltip notification message displays. Delete jump port 1.
2. Click Jump port, then click Delete. 3. Jump port delete success; success/failure tooltip notification message displays. Server interface This information describes how to configure a SmartFabric server interface profile. The Server Interfaces Profile List displays a list of Server Profile IDs and their respective onboard status. Select a profile to view details pertaining to that specific profile.
NOTE: System allows to 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 vmnic physical adapter MAC address without ":". 3. Select the Server Profile Bonding Type. 4. Select the Untagged Network, select the Network, then click Create. 5.
NOTE: Static onboarding option eBGP or Static route routing protocol used for NSX-T deployment. 7. (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. 8. Server Profile and Service Interface creation successful; close the messages. Edit profile 1.
3. The Service Interface Profile successfully updated; close the message. Delete profile 1. Select the Server Interface Profile from the display, then click Delete. 2. Click Delete to confirm removal of the Server Interface Profile. Uplink This information describes how to create, edit, or delete fabric uplinks. You can create uplinks on each fabric with available interfaces which are not part of an existing uplink, server connected ports, or part of a SmartFabric automation and jump port.
NOTE: If you delete an uplink, any unused networks and ports will be available for future use. L2 uplinks 1. Select the Service Instance, then select Uplink. Create user uplinks You can create an uplink by selecting the fabric with a unique user-given name, then select the interfaces and networks through the wizard interface to create a user uplink. 1. Select Uplink, then click Create. 2. Enter the Uplink Name, an optional description, then click Next. 3.
4. Select the untagged network, select the OMNI network, then click Finish. 5. User uplink creation successful; close the message. Edit user uplink 1. Select the User Uplink, then click Edit Networks. 2. Select the Untagged Network to edit, select the OMNI network, then click Update.
3. Click Edit Ports. 4. Verify the uplink interfaces, make changes as necessary, then click Update. 5. Editing of uplink interfaces successful; close the message. Delete user uplink NOTE: You can only delete user-created uplinks. Default system uplinks cannot be deleted. 1. Select the uplink to delete, then click Delete.
2. Click Delete. L3 uplinks L3 VLAN uplink 1. 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.
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 created associated with the nodes that are configured in the port configuration. Uplink creation success; close the message. L3 routed interface uplink 1. 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. 4. Enter the network profile information and routing policy information for the uplinks, then click Finish.
5. L3 routed uplink creation success; close the message. Network This information describes how to configure networks, and routing configuration. You can configure three types of networks including VxLAN networks (for L2 and L3 profiles), VLAN networks (for L2 and L3 profiles), and L3 routed interfaces (for L3 profiles only). NOTE: Networks that are created by the OMNI user interface are considered Manual.
2. Verify Layer 2 is selected as the Virtual Network Type, enter the Virtual Network Name, enter a value between 1 and 16777215 for the VxLAN VNI, enter a value between 1 and 4093 for the VLT VLAN ID, enter an optional description, then click Create. 3. Virtual network creation successful; close the message. 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.
Edit VxLAN network 1. Select the Virtual Network Name, then click Edit. 2. Modify the Virtual Network Type, then click Edit.
3. Modify the Prefix, Gateway IP Address, IP address, then click Edit. 4. Virtual network edits successful; close the message. Delete VxLAN network 1. Select the Virtual Network Name, select the Network, then click Edit on the right.
2. Click Delete to remove the network. 3. Delete network success; close the message. VLAN networks Create network 1. Select Networks > VLAN Networks, then click Create.
2. Verify Layer 2 VLAN Network is selected as the Network Type, enter the Network ID, Network Name, enter 1 to 4093 for the VLAN, enter an optional description, then click Create. 3. VLAN network created; close the message. Edit network 1. Select the Virtual Network Name, then click Edit. 2. Verify the Network Name, make changes as necessary, then click Edit.
3. Edit network success; close the message. Delete network 1. Select the VLAN network to remove, then click Delete. 2. Click Delete again. 3. Network delete success; close the message. L3 routed interfaces This information explains how to create and delete Layer 3 routed interfaces. Create network 1. Select Networks > Layer 3 Routed Interfaces, then 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. Network create successful; close the message. Edit network 1. Select the Network ID, then click Edit. 2. Make changes as necessary, then click Edit. 3. Network edit success; close the message. Delete network 1. Select the network to remove, then click Delete.
2. Delete network success; close the message. Routing configuration This information describes static routes, and eBGP peer configuration. NOTE: Creation of routes is only allowed in Uplinks or the Server Interface Profile. Delete static route 1. Select the static route to delete, then click Delete. 2. Click Delete Route. 3. Delete static route success; close the message. Static route details The static route details display a list of mapped routes.
Add route to switch 1. Select Routing Configuration > Static Routes, select a static route, then click Add Route to Switch. 2. Select the switch to map to this route, then click Add. 3. Route added to switch success; close the message. Delete route from switch 1. Select the route to delete, then click Delete Route.
2. Click Delete to remove the route from the switch. 3. Delete route policy successful; close the message. Delete eBGP route 1. Select the eBGP route to delete, then click Delete. 2. Delete route policy success; close the message. 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. Add eBGP route to switch 1. Select an eBGP route, then click Add Route to Switch.
2. Select the switch, then click Add. 3. Route switch add success; close the message. 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. Delete route success; close the message. Host network inventory This information describes how to view information about physical Dell EMC PowerSwitch infrastructure running SmartFabric OS10.
• • • • • Physical adapter — physical network adapter name Virtual switch — name of switch the physical adapter is connected to MAC address — MAC address of the physical adapter Physical switch — physical switch that is connected to the fabric Physical switch interface — physical switch port this server network adapter is wired to Logical switch Displays information about the logical switch that is connected to the selected physical adapter.
• VMs tab — includes the name of VMs of that host that is connected to a single virtual switch Physical switch 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 • • • 68 Network Name — name of the VLAN network Network ID — unique identifier of the fabric network
8 Network fabric management This information explains common operations including upgrading of the SmartFabric solution including VxRail nodes, SmartFabric OS10, SmartFabric vCenter appliance, and switch replacement. Topics: • • • Upgrade OMNI appliance Upgrade SmartFabric OS in switch Replace switch in a fabric Upgrade OMNI appliance This information explains how to upgrade the OMNI appliance. You must be in the OMNI VM Console to use these steps.
5. Select 4. Register/Update OMNI vSphere client plugin with vCenter to register the plug-in. 6. Enter the FQDN to use for registration, then repeat the steps to update the plug-in with the vCenter Server. Upgrade from OMNI 1.1 to OMNI 1.2 1. Unregister the OMNI 1.1 plug-in using the OMNI CLI option. 2. Shut down the OMNI 1.1 VM. 3. Deploy the OMNI 1.2 OVA, then register the OMNI plug-in with the vCenter (see OMNI vCenter client plug-in registration).
4. (Optional) Delete the OMNI 1.1 VM, if needed. Upgrade SmartFabric OS in switch This information describes how to upload an image to upgrade the fabric. For information about changing the SmartFabric password, upgrading the OS or replacing the switch, see Summary. NOTE: Fabric upgrade must be performed during OMNI maintenance mode (see OMNI maintenance mode). Upload image 1. Select Service Instance > Summary > Fabric Actions > Upgrade OS. 2. Click Upload to upload the .bin file. Upgrade fabric 1.
NOTE: Upgrade Fabric option upgrades all the switches in a network fabric. You cannot stop the upgrade after it is triggered. 2. Confirm the upgrade; click Upgrade. NOTE: Maintenance mode is a precautionary step during the SmartFabric upgrade. If you continue, the upgrade stops OMNI automatic VLAN configuration. 3. Fabric upgrade success; close the message. SmartFabric automatically reboots when the upgrade is complete.
2. Click Delete Image, then click Delete. 3. Once the image is deleted, a success message displays; close the window. Replace switch in a fabric You can replace an faulty OS10 switch in a SmartFabric environment. Follow the below instructions to replace a switch: 1. Identify the OS10 switch to be replaced and label each of the cables with the port numbers before disconnecting the cables. 2.
6. Enable SmartFabric Services on the new switch and define the ICL ports. You can use the smartfabric l3fabric enable role command to enable SmartFabric Services. Example: OS10# smartfabric l3fabric enable role LEAF vlti ethernet 1/1/29-1/1/30 For more information about enabling SmartFabric Services, see Dell EMC SmartFabric OS10 User Guide Release 10.5.0. 7. The new switch reboots and is placed in SmartFabric Services mode.
9 OMNI support This information describes how to access the OMNI support. Select Support to view the support options. OMNI maintenance mode Enable Maintenance Mode NOTE: It is recommended to enable Maintenance Mode before upgrading the network fabric. Enabling Maintenance Mode disables zero-touch automation for all SmartFabric instances. Enabling Maintenance Mode prevents OMNI from configuring networks on SmartFabrics when there are changes in the vCenter port groups. 1.
3. Maintenance Mode disabled; close the message. Support options Support options are used for debugging. If there is an issue, you can download a support bundle containing all the logs that are found on OMNI. You can also change the log-level of OMNI to collect logs of different types. When OMNI's log-level is set to ERROR only, error logs are recorded. When OMNI's log-level is set to DEBUG, error logs and logs with additional information is recorded.
Plugin information links You can view the User Guide, Release Notes, or end-user license agreement (EULA) to view or download.
10 Troubleshooting You can use the following information to troubleshoot the SmartFabric vCenter appliance connectivity, SmartFabric errors, and UI population errors. SmartFabric appliance connectivity Check the IP and DNS settings and connection status. 1. Select 2. Interface Configuration Menu. 2. Select 1. Show Interfaces (q to close view). 3. Select 2. Show Connection Status.
4. Issue a curl https request from the SmartFabric vCenter appliance console to the plug-in appliance IP configured on ens160. SmartFabric error Check ens192 has IPv6 link-local address that is enabled and is up. NOTE: Multiple fabric or vCenter registrations are shown in Status SmartFabric Management Service. 1. Select 2. Status OMNI Managment Service. All services must be active. If they are not all active, restart the service by selecting 4. Restart OMNI Management Service.
NTP server status 1. Select 2. Interface Configuration Menu. 2. Select 4. Show NTP Status. 3. Enter the Validate NTP Server IP address/host name. UI is not populated NOTE: If any IP address or SSL certificate changes on the SmartFabric VM, OMNI automation services can be restarted by enabling Maintenance mode, then disabling Maintenance mode (see OMNI support). Check the service status on the plug-in VM. 1. Select 4. Restart SmartFabric Management Service. 2. Select 2.
2. Select 5. Create Support Bundle to create a support bundle at /tmp/support-bundle.tar.gz on the SmartFabric OMNI VM. 3. From an external host, scp using admin to transfer the support bundle file out. SCP credentials for the SmartFabric appliance are the same as the SmartFabric appliance console password. By default, the username and password is admin/admin. NOTE: Recommendation is to set the log level change to DEBUG before creating the support bundle.
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. # mount / -re -o remount 6. Change the password for admin using passwd admin, then enter and confirm the new password. 7. Reset the VM from vCenter. You could log in through the new password for the SmartFabric VM. Missing networks on server interfaces If OMNI fails to create and associate the appropriate network on a server interface during automation, OMNI automation services can be restarted so that OMNI reconfigures the networks.
Index A access OMNI portal using registered vCenter 32 activate connection profiles 24 B image (continued) upload 71 J breakout port 41 jump port add 42 delete 42 C L create user uplinks 47 VxLAN network 54 L3 D default client control traffic network 9 client management network 9 fabric settings 9 delete user uplink 49 delete VxLAN network 57 domain or network fabric 8 download and install OMNI OVA 13 E eBGP add route to switch 64 delete route 64 delete route from switch 65 peer details 64 edit p
OMNI (continued) host inventory network 65 identification of vCenter ESXi host 34 log in to VM console 17 logical switch 66 maintenance mode 75 network 54 network interface profile configuration 17 overview 12 physical adapter table 65 portal access using OMNI appliance IP 32 power on VM 16 rack 38 server interface 43 setup 17 SmartFabric management 36 SmartFabric networks consolidation 34 summary 38 support 75 switches 40 topology 39 unable to resolve vCenter FQDN 83 unregister vCenter 28 upgrade appliance
VLANs reserved 9 VxLAN create network 54 delete network 57 edit network 56 network details 55 VxRail integrated solutions 10
