Concept Guide

● The bonding can be static or LACP.
● All existing bonding modes are supported on a statically onboarded server.
● VXLAN does not support STP on access ports and it is not applicable for L3 Fabric. For the VXLAN type of network, you
cannot configure STP; the network topology must remain loop free.
● All existing network types are allowed to be onboarded on statically onboarded servers.
● Since onboarding is static, when server is moved there is no support for moving the configurations along with the server.
● The port-role for the statically onboarded server is EndHost or GenericEndHost.
● When the server profile or server interface profile is deleted, all the impacted interfaces are brought to default configuration.
Server profile and server interface profile
Server profile and server interface profiles are logical entities of SFS. You configure these entities when onboarding a server to
the fabric.
Server interface profile represents the server NIC ports that are connected to the leaf switches. For a server interface profile,
a server interface ID must be configured using the MAC address of the server NIC port. SFS uses the server interface ID to
identify the server NIC port and configure the required networks on the server NIC ports.
Server profile is a list of server interface profiles with a common bonding type. Supported bonding types are AutoDetect and
LACP. You can configure a server profile using SFS UI, see Server onboarding. To view the server profiles available on the SFS,
see Manage server profiles.
Fabric back up and restore
You can backup the SFS configuration to an external device, and restore the fabric to a good state using the backed-up
configuration during a failure or error.
The backup functionality allows you to backup all the user configuration to a text file in JSON format. The REST endpoints are
available that returns a text file containing all the user configuration that was done through the REST interfaces.
The restore functionality allows you to restore the fabric to a last known good configuration. The REST endpoint is available that
enables you to stream the backed-up configuration. The restore action wipes the data completely and restores the configuration
on the switches from the backup file. The restore functionality is followed by mastership switchover. For the successful restore
operation to occur, the restore activity should be applied to the same set of switches in the fabric. Also, the SFS personality
should be the same when the backup was performed.
The backup and restore endpoints are accessible only for the users with sysadmin role. The REST payload is encrypted using
the SSL protocol.
You can also restore the configuration for a fabric from SFS UI, see Restore.
Table 3. HTTP Methods
Functionality HTTP Method URL Payload
Backup GET https://<ip-address>/
redfish/v1/Dnv/Backup
Output is a text as stream and
Content-Type is application or
octet-stream.
Restore POST https://<ip-address>/
redfish/v1/Dnv/Restore
Content-Type: application or
octet-stream and payload
contains the backup file.
10 SFS fundamentals