Troubleshooting

The following provides troubleshooting information for this configuration.

• If an instance is created but no IP address is assigned, a virtual network interface failed to be created. The failure could be due to the DHCP server not being accessible. These errors do not display in the GUI, but you can view them in the output of a CLI command.

• Use snowballedge describe-device to get interface and service information.

• Direct console connections to the instances are not supported. You can connect via SSH.

• After registering the image, OpsHub stops populating the AMI list. Close and open OpsHub to refresh the AMI list.

• To reset the network configuration, physical access is required to set all interfaces to 0.0.0.0.

• Disable and start the services to generate certificates. If the default gateway was changed and the Snowball Edge was restarted, it is most likely that the Snowball Edge services regenerated certificates.

• You cannot stop the S3 connector, but you can stop the service using the following commands:

  snowballedge describe-service --service-id s3-snow

  snowballedge stop-service --service-id s3-snow

• To view the DNI and VNI information, run snowballedge describe-direct-network-interfaces. The following shows example output for this command:

  {
   "DirectNetworkInterfaces" : [ {
  …
   {
      "DirectNetworkInterfaceArn" : "arn:aws:snowball-device:::interface/s.ni-77777777777",
      "PhysicalNetworkInterfaceId" : "s.ni-654321",
      "InstanceId" : "s.i-123456",
      "Driver" : "ixgbevf",
      "MacAddress" : "5e:12:37:b8:db:0b"
    } ]
  }