This section discusses the various issues that you may encounter when configuring the scenarios and examples that are mentioned in this guide. A problem statement is given for each scenario, along with one or more possible solutions.
Problem | Scenario | Solution |
MX7116n FEMs are not discovered when creating a SmartFabric. | Two MX7000 chassis are connected in an MCM group with MX9116n FSEs and MX7116n FEMs. MX9116n FSEs are connected to Upstream switches. Upstream switches are connected to rack servers, and vCenter is deployed in this scenario. VMs are also deployed on the ESXi hosts MX Compute sleds and Rack servers. The Link Layer Discovery Protocol (LLDP) advertisements from the blade NICs may not be visible to the IOMs. Running the In the blade iDRAC, the NICs status shows as This issue may prevent MX7116n from being discovered when creating a SmartFabric. | When resolving the issue, consider the following:
|
Dropped packets between VMs for 15 seconds after the switch reboots | Two MX7000 chassis are connected in an MCM group with MX9116n FSEs and MX7116n FEMs. MX9116n FSEs are connected to Upstream switches. Upstream switches are connected to rack servers, and vCenter is deployed in this scenario. VMs are also deployed on the ESXi hosts MX Compute sleds and Rack servers. Verify that STP is enabled. Rebooting the MX9116n FSE on the MX7000 chassis while passing traffic between the VMs deployed on the MX compute sleds and the VMs that are deployed on rack servers causes three to five requested time outs and dropped packets for up to 15 seconds. | The issue is when one of the MX9116n FSE on MX7000 chassis becomes the Spanning Tree root when using the legacy Ethernet uplink type. To resolve this issue, make an upstream switch the STP Root, not the MX9116n FSE. In the topology mentioned here, the switch with the lower priority number increases the likelihood that the bridge to it becomes the STP Root. Run the commands mentioned in the Dell SmartFabric OS10 User Guide to make upstream switch the STP root. Find the relevant version of the User Guide in the OME-M and OS10 compatibility and documentation table. |
Not able to set QoS on a compute sled connected to MX9116n FSE or MX5108 | Scenario: I/O Modules MX9116n FSE or MX5108n is connected to MX740c compute sled with Intel XXV710 ethernet controller. IOMs are connected to upstream switches Running show lldp dcbx interface ethernet <node/slot/port> pfc detail command shows Remote willingness status is disabled on server facing ports. OS10# show lldp dcbx interface ethernet 1/1/1 pfc detail Interface ethernet1/1/15 Admin mode is on Admin is enabled, Priority list is 4,5,6,7 Remote is enabled, Priority list is 4,5,6,7 Remote Willing Status is disabled (Output Truncated) The NIC on the server that is attached to the switch is not configured to receive DCBx or any QoS configurations, which is what causes the Remote Willing Status is disabled message. Some server NICs will only receive a QoS configuration (scheduling, bandwidth, priority queues, etc.) from the switch they are attaching to. The drivers for these NICs do not support this configuration via software, but only from a peer via the DCBx protocol. | By default, the MX9116n FSE and MX5108n IOMs support the DCBx protocol and can be used to push their QoS configuration to the server NIC. The NIC must be configured to accept these QoS settings from the switch by setting their Remote Willing Status to Enable. In Full Switch mode, user can configure DCBx as mentioned in the Dell SmartFabric OS10 User Guide. Find the relevant version of the User Guide in the OME-M and OS10 compatibility and documentation table. In SmartFabric mode, DCBX configuration is tied to FCoE UPLINK and it will enable only after FCoE Uplink configured on this switch. Once DCBX configuration applied on switch side, it will push to remote end and remote end must accept this configuration by “Remote Willing Status Enabled”. |
Removing the management VLAN tag under Edit Uplinks removes the management VLAN | To reproduce the scenario with MX IOMs connected to Upstream switches:
| In Full Switch mode, user can create a VLAN, enable it and define as a Management VLAN in global configuration mode on switch. For more information on Configuring VLANs in Full Switch mode, find the relevant version of the User Guide in the OME-M and OS10 compatibility and documentation table. In SmartFabric mode, management VLAN 4020 will be created by default. Make sure not to add management VLAN by Add Network or remove tag on management VLAN. This removes the management VLAN itself. |