Enabling Cloud SLA

This feature is supported in SonicOS 8.2.1 and later versions.

The Cloud SLA feature provides automated creation and periodic refresh of predefined SLA objects for popular SaaS applications. These SLA objects are retrieved from the backend database and kept up to date through scheduled synchronization. When enabled, the feature ensures that application‑specific latency, jitter, and packet‑loss thresholds are available for use in SLA‑based policies, unless a custom SLA object has been created for that application.

When the feature is disabled, no synchronization or automatic object creation occurs. Administrators can optionally purge previously created Cloud SLA objects that are not referenced by the configuration.

Key functionalities

• Automatically creates predefined SLA objects for popular SaaS applications based on backend data.

• Refreshes predefined SLA objects during device startup or every 24 hours.

• Uses predefined SLA values (latency, jitter, packet loss) unless a custom SLA object is configured for the application.

• Applies a distinct naming convention to predefined SLA objects to differentiate them from user‑defined objects.

• Performs sync retries if SLA class objects are not received:

  • Every minute for 5 attempts

  • Every hour for 5 attempts

• Logs a critical message if predefined SLA objects are still not received after all retry attempts.

• Applies the next fetch delay based on the server response, or uses a default 24‑hour delay if no response is available.

• Stops sync‑up and auto‑creation when the feature is disabled.

• Provides a purge function to delete unused predefined SLA objects.

• Uses the same API format as the botnet subsystem for backend communication.

To enable Cloud SLA

1. Navigate to Network | SDWAN > SLA Class Objects.
2. Turn on the Cloud SLA toggle button.

The predefined SLA objects are displayed.

• Click Sync to retrieve the latest version of the predefined SLA class objects from the cloud.

• Click Purge to delete all predefined SLA class objects. This action does not delete system‑generated or user‑created SLA class objects.

 

• The user cannot edit or delete any predefined SLA objects.

• When a predefined SLA object is updated in the backend, the change becomes visible on the firewall only after the next synchronization with the backend.

• The user cannot create a custom SLA object that uses the same name as any predefined SLA object.