Networking: SmartFabric OS10 - fabric services reports a server interface missing

The following error is seen in the fabric compliance pane:

SFS UI interface:

 

Switch validation error:
 

S4112-1# show smartfabric validation-errors 
ErrorKey         : 7XXXXXX: Internal-Err(Server Not Discovered): test-profile:e4434b69e6a8
MessageID        :
Description      :
EEMI             : NVFH0168~~test-profile~~e4434b69e6a8
Category         :
Subcategory      :
Severity         : SEVERITY_2
Recommended Action:Check Lldp
Timestamp        : 1709754863
<<snipit>>
S4112-1#

This may be caused by any of the following:

1. Post upgrading to VxRail 7.0.450 to 8.0.2xx as part of the SmartFabric Services Decoupling. The custom port level LLDP information is no longer sent by the host. This may result in LLDP information no longer being sent to the switch resulting in compliance errors.
   1. This is a VxRail-centric customized LLDP process.
2. Non-VxRail environments if LLDP was enabled with the server interface deployed as dynamic, then LLDP service was disabled on the host for any reason.
3. OMNI or vCenter import of a VMNIC that is not physically connected to switch.

As shown in LLDP neighbor output we do not see remote chassis ID with the MAC address ending in e6a8 that the dynamic profile is assigned:

S4112-1# show lldp neighbors
Loc PortID          Rem Host Name        Rem Port Id                    Rem Chassis Id
--------------------------------------------------------------------------------------
ethernet1/1/1       S4112-2              ethernet1/1/1                 88:6f:d4:ba:e9:37
ethernet1/1/2       S4112-2              ethernet1/1/2                 88:6f:d4:ba:e9:37
ethernet1/1/13:2    PowerEdge R640       JXXXXXX NIC.Integrated.1-1-1  4c:d9:8f:34:8d:3e
<<snipit>>
S4112-1#

This is resolved with one of four methods.

1. Delete unused server interface profiles that are confirmed no longer needed. 
   • This could be due to a NIC change or profiles being created for ports not directly connected to the SmartFabric Services (SFS) enabled switch.
2. Enabling LLDP that matches the dynamic MAC address in the server profile. In VMware environments this would be enabling LLDP on the virtual switch with "transmit" or "both".  
   • Caution: Caution should be used when enabling LLDP. If the LLDP neighbor is different than the current configured dynamic MAC address in the server profile it may result in the current dynamic, sticky configuration to become unconfigured. This can result in defaulted configuration on the switch port.
3. If the profile is dynamic with interface details; Must either delete profile or static assign to unused port as static, then back to original intended port.
   • This causes an outage while vlans are removed until reapplied as expected when the profile is edited while host is passing traffic.
4. Migrate the dynamic interface profile to Static for the port that it is meant for. In the screenshots below, the profile is listed as dynamic without interface details. The profile must be edited to change the onboarding type to static.

    We change Static onboarding to yes and assign leaf node and interface that it is expected too:
 


    After the change, the onboard type will change to static and the interface name should be populated with the interface that was configured.

  

See the SmartFabric Services guide in the SmartFabric OS10 Documentation or the OpenManage Network Integration (OMNI) user guide for more details.
OS10 Documentation
OMNI Documentation