Dell PowerSwitch S4128F-ON EMC SmartFabric OS10 User Guide Release 10.5.0 - Page 124

Static onboarding for nonintegrated devices SmartFabric services support onboarding server on assigned ports instead of LLDP based discovery mechanism. SFS extent the server profile and server interface profile for you to provide onboarded interface. • All existing bonding modes is supported on statically onboarded server. • Wherever possible, STP is enabled on these ports. Since VXLAN does not support STP on access ports, this is not applicable for L3 Fabric. RPVST+ is enabled on Layer 3 VLAN networks. For the VXLAN type of network, no STP can be configured; 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. Backup and Restore of fabric state In specific scenarios where the fabric has a single switch or multiple switches, you can backup all the switch configuration to an external file. The backed up user configuration can be applied at any point to restore the old known stable state. This feature allows you to backup a known good state of the configuration to an external device. If the switch configuration goes bad, the old known good state can be restored. The Backup functionality allows you to backup all of the user configuration to a text file. If the configuration is in Layer3 LEAF and SPINE or Layer2 VxRail personality, REST endpoints are available that returns a text file containing all the user configuration that was done through the REST interfaces. The text file is in JSON format. The Restore functionality allows you to restore the last known good configuration. The REST POST end point is available that enables you to stream the backed-up configuration. After the restore is performed, database is wiped completely. The configuration is then restored from the input 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 OS10 Nodes. Also, the 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 will be encrypted using the SSL protocol. Table 20. HTTP Methods Functionalit HTTP Method y Backup GET URL https:/// redfish/v1/Dnv/Backup Payload Output is a text as stream and Content-Type is application/octet-stream Restore POST https:/// redfish/v1/Dnv/Restore Content-Type: application/ octet-stream and payload contains the text file (backedup file) Enable SmartFabric Services on the switches To create a L3 network fabric in a leaf and spine topology, enable the SFS in all the switches. After you enable SFS, a network fabric is created automatically with the default fabric settings. To enable the SFS: • Designate a role for the switch: Leaf or spine • Configure VLT interfaces for the leaf switches. To enable the SmartFabric Services in a switch from the OS10 CLI, use the smartfabric l3fabric enable command. For more information, see smartfabric l3fabric enable. After you enable the SFS on the switches and set a role, the system prompts for confirmation to reload and boots in the SFS mode. To apply the changes, confirm by typing Yes and the switch reloads in the SFS mode. 124 SmartFabric Services