We've transitioned to a new documentation portal to serve you better. Access the latest content by clicking here.
This article describes the process of setting up a Snowball Edge device.
Ensure that you have the following information that Druva provides after delivering the Snowball Edge device:
Note: WinSCP is required only when the {{phoenix}} EC2 instance requires a software update.
On the AWS Snowball resources page, navigate to the Snowball Edge Client section.
Download the AWS Snowball Edge client installation package for your operating system.
After downloading, install the Snowball Edge Client on the resources that you want to connect with the Snowball Edge device.
Download the AWS CLI by using the instructions given on the Installing the AWS Command Line Interface page.
Note: This activation token for the seeding device is saved on the Cloud and can be accessed from the Manage > Activation Tokens page if required.
In the New Seeding Device dialog box, click Done.
Note: In the case of DHCP, you will know you are properly connected to the network when the IP address is displayed in the Connection tab. In the case of STATIC, you will need to enter these fields manually on the LCD.
ping
command from the Snowball Client CLI with the IP address of the Snowball Edge device to ensure that it is connected.Note: As an example, we are using the values of Snowball Edge IP address as 172.x.x.10 and the EC2 IP address as 172.x.x.45.
snowballEdge unlock-device --endpoint https://Snowball_Edge_IP_address --manifest-file path/to/manifest/file --unlock-code 29-character_unlock_code
snowballEdge unlock-device --endpoint
https://172.x.x.10
--manifest-file JID7fa3b0c4-xxxx-xxxx-9bd3-5fb0136e4bae_manifest.bin
--unlock-code 89faf-xxxxx-xxxxx-f892c-9c141
snowballEdge describe-device --endpoint https://Snowball_Edge_IP_address --manifest-file path/to/manifest/file --unlock-code 29-character_unlock_code
snowballEdge describe-device --endpoint https://172.x.x.10 --manifest-file JID7fa3b0c4-xxxx-xxxx-9bd3-5fb0136e4bae_manifest.bin
--unlock-code 89faf-xxxxx-xxxxx-f892c-9c141
Note: The message“State” : “UNLOCKED”
appears as part of the output upon the success of the unlock operation. Note the value of thePhysicalNetworkInterfaceId
field associated with the IP address of the Snowball Edge device.
If the message“State” : “UNLOCKED”
does not appear, wait for some time as the unlocking process might take some time. Alternatively, you can verify the manifest file and unlock codes and check if the LCD display on the AWS Snowball Edge device's front indicates that the device is ready for use.
snowballEdge describe-service --endpoint https://Snowball_Edge_IP_address --manifest-file path/to/manifest/file --unlock-code 29-character unlock code --service-id s3
snowballEdge describe-service --endpoint https://172.x.x.10
--manifest-file JID7fa3b0c4-xxxx-xxxx-9bd3-5fb0136e4bae_manifest.bin
--unlock-code 89faf-xxxxx-xxxxx-f892c-9c141
--service-id s3
snowballEdge describe-service --endpoint https://Snowball_Edge_IP_address --manifest-file path/to/manifest/file --unlock-code 29-character unlock code --service-id ec2
snowballEdge describe-service --endpoint https://172.x.x.10
--manifest-file JID7fa3b0c4-xxxx-xxxx-9bd3-5fb0136e4bae_manifest.bin
--unlock-code 89faf-xxxxx-xxxxx-f892c-9c141
--service-id ec2
Note: This command returns a status value for a service. It also includes state information that might be helpful in resolving issues you encounter with the service. These states are as follows:
ACTIVE: The service is running and available for use.
ACTIVATING: The service is starting up, but it is not yet available for use.
DEACTIVATING: The service is in the process of shutting down.
INACTIVE: The service is not running and is not available for use.
Ensure that the output states the status of the services as ACTIVE. If the state does not appear as ACTIVE, contact Support.
--physical-network-interface-id
field as the one that you noted in Step 2.
snowballEdge create-virtual-network-interface --physical-network-interface-id physical network configuration ID --ip-address-assignment DHCP --endpoint https://Snowball_Edge_IP_address --manifest-file path/to/manifest/file --unlock-code 29-character unlock code
snowballEdge create-virtual-network-interface --physical-network-interface-id snow.ni-81c83c258386c98fc --ip-address-assignment DHCP --endpoint https://172.x.x.10
--manifest-file JID7fa3b0c4-xxxx-xxxx-9bd3-5fb0136e4bae_manifest.bin
--unlock-code 89faf-xxxxx-xxxxx-f892c-9c141
snowballEdge create-virtual-network-interface --physical-network-interface-id physical network configuration ID --ip-address-assignment STATIC --static-ip-address-configuration IpAddress=EC2_IP_address,Netmask=netmask --endpoint https://Snowball_Edge_IP_address --manifest-file path/to/manifest/file --unlock-code 29-character unlock code
snowballEdge create-virtual-network-interface --physical-network-interface-id snow.ni-abcd1234 --ip-address-assignment STATIC --static-ip-address-configuration IpAddress=172.x.x.45,Netmask=255.xxx.xxx.x --endpoint https://172.x.x.10
--manifest-file JID7fa3b0c4-xxxx-xxxx-9bd3-5fb0136e4bae_manifest.bin
--unlock-code 89faf-xxxxx-xxxxx-f892c-9c141
snowballEdge list-access-keys --endpoint https://Snowball_Edge_IP_address --manifest-file path/to/manifest/file --unlock-code 29-character unlock code
snowballEdge list-access-keys --endpoint https://172.x.x.10
--manifest-file JID7fa3b0c4-xxxx-xxxx-9bd3-5fb0136e4bae_manifest.bin
--unlock-code 89faf-xxxxx-xxxxx-f892c-9c141
snowballEdge get-secret-access-key --endpoint https://Snowball_Edge_IP_address --manifest-file path/to/manifest/file --unlock-code 29-character unlock code --access-key-id access key
snowballEdge get-secret-access-key --endpoint https://172.x.x.10 --manifest-file JID7fa3b0c4-xxxx-xxxx-9bd3-5fb0136e4bae_manifest.bin --unlock-code 89faf-xxxxx-xxxxx-f892c-9c141 --access-key-id 2OEYMELHRKVSOE5xxxx
aws configure --profile profile_name
aws configure --profile sb2
aws ec2 describe-images --endpoint http://Snowball_Edge_IP_address:8008 --profile
profile_name
aws ec2 describe-images --endpoint http://172.x.x.10:8008 --profile sb2
aws ec2 run-instances --image-id ImageId --count 1 --endpoint http://Snowball_Edge_IP_address:8008 --instance-type sbe1.4xlarge --profile profile_name
aws ec2 run-instances --image-id snow.ami-7xxxxx03 --count 1 --endpoint http://172.x.x.10:8008 --instance-type sbe1.4xlarge --profile sb2
aws ec2 describe-instances --endpoint http://Snowball_Edge_IP_address:8008 --profile profile_name
aws ec2 describe-instances --endpoint http://172.x.x.10:8008 --profile sb2
State
field in the output should appear as the following example.
Note the value of the InstanceId
field."State": {
"Code": 16,
"Name": "running"
}
Note: It takes a few minutes for the status to change from Pending to Running.
aws ec2 describe-addresses --endpoint http://Snowball_Edge_IP_address:8008 --profile profile_name
aws ec2 describe-addresses --endpoint http://172.x.x.10:8008 --profile sb2
{
"Addresses": [
{
"PublicIp": "172.x.x.45"
]
}
aws ec2 associate-address --public-ip PublicIp(EC2_IP_address) --instance-id InstanceId --endpoint http://Snowball_Edge_ip_address:8008 --profile profile_name
aws ec2 associate-address --public-ip 172.x.x.45 --instance-id "snow.i-84e798xxxxxd16d4b" --endpoint http://172.x.x.10:8008 --profile sb2
ssh -i keyProvidedbyDruva root@EC2_IP_address
ssh -i local_xyz.pub root@172.x.x.45
Activate the seeding device (EC2 instance) by running the following command. The value of <SnowballID> can be obtained from the AWS Snowball Edge page.
PhoenixActivate activate_snowball --token ActivationToken --snowball_access_key AccessKey --snowball_secret_key SecretKey --snowball_ip SnowballIP --snowball_id SnowballId --type SnowballSeeding --region snowball
Example:PhoenixActivate activate_snowball --token 13603-228-2497-bba520f69b97a8ac9249844xxxxxx13f91101182c4f6bc8b2e2c7c58578e8 --snowball_access_key 2OEYMELHRKVSOE5xxxx --snowball_secret_key 19GxxxxxxmXCAbGLxxxxxHwybQzxxxxxidgVaI --snowball_ip 172.x.x.10 --snowball_id JID7fa3b0c4-xxxx-xxxx-9bd3-5fb0136e4bae --type SnowballSeeding --region snowball
The Snowball Edge device is now set up, unlocked, and activated as a seeding device.