Skip to content

Update Load Balancer Shell Standard.md #16

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Shnitselon wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Update Load Balancer Shell Standard.md #16

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
40 changes: 40 additions & 0 deletions Documentation/Load Balancer Shell Standard.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -466,3 +466,43 @@ An example for the "saved_artifact_info" input:

The artifact types supported by Load Balancer orchestration_restore command are "ftp", "tftp" and "filesystem".
The "requires_same_resource" restore rule for Load Balancer devices is always True.

## Typical Workflows

#### **Workflow 1** - *Save configuration*
1. In CloudShell Portal, reserve the **F5 BIG-IP LoadBalancer** resource.

2. Run the **Save** resource command.

3. In the command inputs field, enter the following information:
* **Folder Path**: For example, *tftp://ipaddress/shared folder*.
* **Configuration Type**: **Startup** or **Running**.
* **VRF Management Name**: Provide the VRF Management name, if relevant.

4. Click **Run**.

The Startup or Running configuration is saved to a file named *<ResourceName>-<startup/running-config>-<timestamp>*, which will be stored in the folder path you entered above.

#### **Workflow 2** - *Restore configuration*
1. In CloudShell Portal, reserve the **F5 BIG-IP LoadBalancer** resource.

2. Run the **Restore** resource command.

3. In the command inputs field, enter the following information:
* **Path**: (Mandatory) Enter the full path of the configuration file.
* **Restore Method**: (Optional) Possible values are **Override** or **Append**. If left empty, the **Override** method is used.
* **Configuration Type**: (Mandatory) Possible values are **Startup** or **Running**.
* **VRF Management Name**: (Optional) Provide the VRF Management name, if relevant.

4. Click **Run**.

#### **Workflow 3** - *Load firmware*
1. In CloudShell portal, reserve the **F5 BIG-IP LoadBalancer** resource.

2. Run the **Load Firmware** resource command.

3. In the command inputs field, enter the following information:
* **Path** (Mandatory). Enter the full path to the firmware file on the remote host, for example: *tftp://10.1.1.1/BIGIP12.SE1-smp-k8.bin*.
* **VRF Management Name** (Optional): Destination filename on the device itself, for example: *bootflash:/BIGIP12.SE1-smp-k8.bin*.

4. Click **Run**.