Manually Provisioning a SteelHead-c for AWS Marketplace
While the Riverbed Cloud Portal makes it easy to provision SteelHead-c, some customers may want to manually deploy their SteelHead-c virtual appliances. You might want to do this if:
• you are provisioning SteelHead-c virtual appliances in the AWS GovCloud (US) region.
• you are provisioning SteelHead-c virtual appliances in the AWS in China region.
• you have multiple AWS accounts and need SteelHead-c in more than one of them.
• you are provisioning CCX-SUB-PERF-TIER model series SteelHead-c virtual appliances.
This section includes these topics:
Before you begin
Riverbed Support needs to grant you access to the Riverbed AMIs. Ensure that your Riverbed Support representative has this information so that they can enable your AWS account with permission to view and launch the appropriate private AMIs.
Note: If you have multiple accounts, ensure you provide the ID for the account associated with the region where you want to run your SteelHead-c virtual appliances
Your Riverbed AMIs will be accessible under your EC2 dashboard > Images > AMIs > Private AMIs.
• AWS account ID
• AWS regions where you want to run your SteelHead-c virtual appliances
• SteelHead-c RiOS versions you want to run
Launching a SteelHead-c for AWS Marketplace
This section describes how to create a SteelHead-c for AWS Marketplace virtual appliance and start it.
To complete this process you must provide an Amazon Machine Image (AMI), security group, key pair, and one-time token. Have this information at hand before beginning the process.
To create a SteelHead-c for AWS Marketplace
1. Log in to your AWS account.
2. Navigate to the EC2 dashboard.
3. Select AMIs in the Images section of the navigation pane.
4. Select Public Images from the drop-down menu to the left of the search bar.
7. Click Next: Configure Instance Details.
8. Expand the Advanced Details section.
9. Under User Data, select As Text and enter this information into the text field:
ds=/dev/xvdq
appname=MarketplaceDeployedSteelHead
lshost=cloudportal.riverbed.com
rvbd_dshost=cloudportal.riverbed.com
lott=XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX
where:
ds - The device node in which the SteelHead-c expects the data store EBS volume to appear. Due to changes in EC2 architecture, set this to /dev/xvdq.
appname - Name of the SteelHead-c.
lshost -Fully qualified domain name of the licensing server. This name is usually the Riverbed Cloud Portal.
rvbd_dshost - Fully qualified domain name of the discovery server. This name is usually the Riverbed Cloud Portal.
lott - One-Time Token used to redeem the license. You obtain this token from the SteelHead-c license on the Riverbed Cloud Portal. You can also provide the One-Time Token after you launch the SteelHead-c.
10. Click Next: Add Storage.
11. Click Next: Tag Instance.
12. (Optional) Add tags. You might find tags useful if you want to group resources together, for example.
13. Click Next: Configure Security Group.
14. Choose a security group for the virtual appliance.
To connect the SteelHead-c, the Discovery Agent, and the client-side SteelHead, configure the security group so that:
– The SteelHead-c allows UDP connections coming in from the Discovery Agent on port 7801 to 7850.
– The SteelHead-c allows TCP connections coming in from the client-side SteelHead on ports 7800, 7810-7850 for optimization. The SteelHead-c allows CLI and UI access on ports 22, 80, and 443.
– The configuration allows TCP connections from the SteelHead-c and the client-side SteelHead.
15. Click Review and Launch.
16. Review the instance details.
17. Click Launch to launch the virtual appliance.
18. Add and configure a data store disk. This volume is in addition to the root volume.
– Navigate to Volumes in AWS Console.
– Click Create Volume.
– Under Volume Type, choose Magnetic unless the SteelHead-c model you are deploying requires a solid state drive (SSD).
– Under Availability zone, choose the zone where the SteelHead-c resides.
– After the volume is created, select it.
– Select Actions in AWS Console, then click Attach Volume.
– Under Instance, select the instance-id of SteelHead-c.
– Under Device, enter /dev/xvdq and Click Attach.
Connecting to the SteelHead-c management console
After you connect to the SteelHead-c management console for the first time, the SteelHead-c loads the attached volumes and starts. You might have to wait for a few minutes for the management console to display.
To connect to the SteelHead-c Management Console
1. Log in to your AWS account.
2. Navigate to the EC2 dashboard.
3. Select Instances in the Instances section of the navigation pane.
4. Click Connect.
5. In the Connect to Your Instance dialog box, select a connection method and follow the instructions in the dialog box.
6. Log in to the SteelHead-c Management Console using your username and password. For first-time login, use admin for the username and the SteelHead-c instance ID for the password.
After deployment and licensing, the SteelHead-c appears in the Riverbed Cloud Portal with a name based on the ID of its management volume.
Upgrading the RiOS software version
This section provides instructions for upgrading the RiOS software on instances that have been manually deployed.
Note: The SteelHead-c IP addresses will change. Ensure that you update any rules or configurations that depend on it such as fixed-target rules on on-premise SteelHeads that peer your SteelHead-c, on-premise firewall configurations, or AWS security group configurations.
To upgrade RiOS software on a SteelHead-c virtual appliance
1. Download the new image from the Riverbed Support site.
2. Log in to your SteelHead-c Management Console and navigate to Administration > Maintenance: Software Upgrade.
3. Under the Install Upgrade section, choose From Local File.
4. Click Choose File and use the file browser to select the image file you downloaded.
5. Optionally select Schedule Upgrade for Later and choose a date and time to automatically perform the installation.
6. Click Install.
The SteelHead-c IP addresses change after you complete this step. As mentioned in the above note, ensure you update any configurations that depend on these IP addresses.