Smarter by Design.Simpler for Business
TR7Enterprise Application Delivery & Security Platform
What does Reload in the right-click menu do; how is it different from Disable / Enable?
Short answer
Reload restarts the running process of the vService from the beginning without changing its configuration: in HTTP and L7 TCP vServices the load balancing process is restarted, along with the AGS process if AGS is on, and in Network vServices the packet distribution service. During this, open connections drop in HTTP and L7 TCP vServices, the status briefly appears as in progress and the vService continues to receive traffic on its own; no confirmation is asked, Reload is inactive while the vService is disabled, and in a cluster setup it is applied on both devices. Disable, on the other hand, keeps the vService off until it is turned on with Enable and keeps the configuration; Enable runs the disabled vService again. Since saved changes are applied automatically, Reload is not needed for ordinary changes; to reload while keeping open connections, the lb service restart command in WEB-CLI is used.
How Does It Work?
- When Reload is selected, the status of the vService changes to in progress (accent color) and the running process is restarted from the beginning with the same configuration.
- When the process restarts, the vService continues to receive traffic on its own and the status becomes green (OK) again; client connections open at the moment of Reload drop in HTTP and L7 TCP vServices.
- In a cluster setup, the Reload command is sent both to the device where the operation is performed and to the peer device.
- Disable stops the vService and keeps it off; the status becomes gray (Disabled). Enable starts the vService again with the same configuration.
Comparison
| Reload | Disable | Enable | |
|---|---|---|---|
| What it does | Restarts the running process from the beginning with the same configuration | Stops the vService and keeps it off | Runs the disabled vService |
| Configuration | Does not change | Kept | Starts with the kept configuration |
| Open connections | Drop (HTTP and L7 TCP) | End | - |
| Traffic afterwards | Continues on its own | None until Enable | Starts |
| Confirmation | Not asked | Not asked | Not asked |
| While the vService is disabled | Inactive | - | Used |
| On multiple vServices | No, a single vService | Yes, from the list toolbar | Yes, from the list toolbar |
Reload, Disable and Enable in TR7
- Reload is located in the right-click menu of the vService list, in the ⋮ menu of the vService preview and in the ⋮ menu of the panel on the vService screen; the panel menu is described in the Panel header section. It does not exist in the WAF, AGS and Bot/DDoS vService lists.
- Disable and Enable are located in the same menus and in the Load Balancer vService List toolbar; the buttons in the toolbar are applied to multiple vServices (Can I enable, disable or delete multiple vServices at the same time?).
- Status transitions are tracked in the Status Logs tab in the vService panel.
- When changes are applied: When does a change I make take effect; does it go live as soon as I save it?
- To reload while keeping open connections: Can I restart a vService without interruption (soft / hard restart)?
- The difference between Disable and deleting: What is the difference between temporarily disabling a vService and deleting it?
Common Misconceptions
- "Reload is required for a change to be applied." A saved change is applied automatically; no additional Reload is required (The change I made does not seem to take effect; what should I check?).
- "Reload keeps open connections." The Reload in the interface restarts the process from the beginning and open connections drop in HTTP and L7 TCP vServices; to keep the connections,
lb service restartin WEB-CLI is used. - "Reload turns on a disabled vService." Reload is inactive while the vService is disabled; Enable is used.
- "In a cluster, Reload is applied on only one device." The Reload in the interface is sent to both devices.
How it is done in the documentation
