AWS Snowball Edge tidak lagi tersedia untuk pelanggan baru. Pelanggan baru harus AWS DataSync
Terjemahan disediakan oleh mesin penerjemah. Jika konten terjemahan yang diberikan bertentangan dengan versi bahasa Inggris aslinya, utamakan versi bahasa Inggris.
Mengganti node dalam cluster
Untuk mengganti node, Anda harus terlebih dahulu memesan penggantinya. Anda dapat memesan node pengganti dari konsol, AWS CLI, atau salah satu AWS SDK. Jika Anda memesan simpul pengganti dari konsol, Anda dapat memesan penggantian untuk tugas apa pun yang belum dibatalkan atau diselesaikan. Kemudian, Anda mengasosiasikan node yang tidak sehat dari cluster, menghubungkan node pengganti ke jaringan Anda dan membuka kunci cluster termasuk node pengganti, mengaitkan node pengganti dengan cluster, dan memulai ulang penyimpanan yang kompatibel dengan Amazon S3 di layanan Snowball Edge.
Untuk memesan simpul pengganti dari konsol
-
Masuk ke Konsol Manajemen AWS Snow Family
. -
Temukan dan pilih tugas untuk simpul yang dimiliki klaster yang Anda buat dari dasbor Tugas.
-
Untuk Tindakan, pilih Ganti simpul.
Dengan melakukan ini akan membuka langkah terakhir dari wizard pembuatan tugas, dengan semua pengaturan identik dengan bagaimana klaster awalnya dibuat.
-
Pilih Buat tugas.
Pengganti Snowball Edge Anda sekarang dalam perjalanan ke Anda. Gunakan prosedur berikut untuk menghapus node yang tidak sehat dari cluster.
Untuk menghapus node dari cluster
-
Matikan node yang akan dihapus. Untuk informasi selengkapnya, lihat Mematikan Tepi Bola Salju.
-
Gunakan
describe-clusterperintah untuk memastikan node yang tidak sehat tidak dapat dijangkau. Ini ditunjukkan oleh nilaiUNREACHABLEuntukStatenamaNetworkReachabilityobjek.snowballEdge describe-cluster --manifest-filepath/to/manifest/file.bin--unlock-codeunlock-code--endpoint https://ip-address-of-device-in-clustercontoh dari output
deskrip-cluster{ "ClusterId": "CID12345678-1234-1234-1234-123456789012", "Devices": [ { "DeviceId": "JID12345678-1234-1234-1234-123456789012", "UnlockStatus": { "State": "UNLOCKED" }, "ActiveNetworkInterface": { "IpAddress": "10.0.0.0" }, "ClusterAssociation": { "ClusterId": "CID12345678-1234-1234-1234-123456789012", "State": "ASSOCIATED" }, "NetworkReachability": { "State": "REACHABLE" }, "Tags": [] }, { "DeviceId": "JID12345678-1234-1234-1234-123456789013", "UnlockStatus": { "State": "UNLOCKED" }, "ActiveNetworkInterface": { "IpAddress": "10.0.0.1" }, "ClusterAssociation": { "ClusterId": "CID12345678-1234-1234-1234-123456789012", "State": "ASSOCIATED" }, "NetworkReachability": { "State": "REACHABLE" }, "Tags": [] }, { "DeviceId": "JID12345678-1234-1234-1234-123456789014", "ClusterAssociation": { "ClusterId": "CID12345678-1234-1234-1234-123456789012", "State": "ASSOCIATED" }, "NetworkReachability": { "State": "UNREACHABLE" } } ] } -
Gunakan
describe-serviceperintah untuk memastikan statuss3-snowlayanan adalahDEGRADED.snowballEdge describe-service --service-id s3-snow --device-ip-addressessnow-device-1-address snow-device-2-address--manifest-filepath/to/manifest/file.bin--unlock-codeunlock-code--endpoint https://snow-device-ip-addresscontoh keluaran perintah des
kribe-service{ "ServiceId": "s3-snow", "Autostart": true, "Status": { "State": "DEGRADED" }, "ServiceCapacities": [ { "Name": "S3 Storage", "Unit": "Byte", "Used": 38768180432, "Available": 82961231819568 } ], "Endpoints": [ { "Protocol": "https", "Port": 443, "Host": "10.0.0.10", "CertificateAssociation": { "CertificateArn": "arn:aws:snowball-device:::certificate/7Rg2lP9tQaHnW4sC6xUzF1vGyD3jB5kN8MwEiYpT" }, "Description" : "s3-snow bucket API endpoint (for s3control SDK)", "DeviceId": "JID-beta-207012320001-24-02-05-17-17-26", "Status": { "State": "ACTIVE" } }, { "Protocol": "https", "Port": 443, "Host": "10.0.0.11", "CertificateAssociation": { "CertificateArn": "arn:aws:snowball-device:::certificate/7Rg2lP9tQaHnW4sC6xUzF1vGyD3jB5kN8MwEiYpT" }, "Description": "Description" : "s3-snow object & bucket API endpoint (for s3api SDK)", "DeviceId": "JID-beta-207012320001-24-02-05-17-17-26", "Status": { "State": "ACTIVE" } }, { "Protocol": "https", "Port": 443, "Host": "10.0.0.12", "CertificateAssociation": { "CertificateArn": "arn:aws:snowball-device:::certificate/7Rg2lP9tQaHnW4sC6xUzF1vGyD3jB5kN8MwEiYpT" }, "Description": "Description" : "s3-snow bucket API endpoint (for s3control SDK)", "DeviceId": "JID-beta-207012240003-24-02-05-17-17-27", "Status": { "State": "ACTIVE" } }, { "Protocol": "https", "Port": 443, "Host": "10.0.0.13", "CertificateAssociation": { "CertificateArn": "arn:aws:snowball-device:::certificate/7Rg2lP9tQaHnW4sC6xUzF1vGyD3jB5kN8MwEiYpT" }, "Description": "Description" : "s3-snow object & bucket API endpoint (for s3api SDK)", "DeviceId": "JID-beta-207012320001-24-02-05-17-17-27", "Status": { "State": "ACTIVE" } } ] } -
Gunakan
disassociate-deviceperintah untuk memisahkan dan menghapus node yang tidak sehat dari cluster.snowballEdge disassociate-device --device-iddevice-id--manifest-filepath/to/manifest/file.bin--unlock-codeunlock-code--endpoint https://ip-address-of-unhealthy-devicecontoh keluaran perintah
disassociate-deviceDisassociating your Snowball Edge device from the cluster. Your Snowball Edge device will be disassociated from the cluster when it is in the "DISASSOCIATED" state. You can use the describe-cluster command to determine the state of your cluster. -
Gunakan
describe-clusterperintah lagi untuk memastikan node yang tidak sehat dipisahkan dari cluster.snowballEdge describe-cluster --manifest-filepath/to/manifest/file.bin--unlock-codeunlock-code--endpoint https:ip-address-of-healthy-devicecontoh
perintahdescribe-cluster yang menunjukkan node tidak terkait{ "ClusterId": "CID12345678-1234-1234-1234-123456789012", "Devices": [ { "DeviceId": "JID12345678-1234-1234-1234-123456789012", "UnlockStatus": { "State": "UNLOCKED" }, "ActiveNetworkInterface": { "IpAddress": "10.0.0.0" }, "ClusterAssociation": { "ClusterId": "CID12345678-1234-1234-1234-123456789012", "State": "ASSOCIATED" }, "NetworkReachability": { "State": "REACHABLE" }, "Tags": [] }, { "DeviceId": "JID12345678-1234-1234-1234-123456789013", "UnlockStatus": { "State": "UNLOCKED" }, "ActiveNetworkInterface": { "IpAddress": "10.0.0.1" }, "ClusterAssociation": { "ClusterId": "CID12345678-1234-1234-1234-123456789012", "State": "ASSOCIATED" }, "NetworkReachability": { "State": "REACHABLE" }, "Tags": [] }, { "DeviceId": "JID12345678-1234-1234-1234-123456789014", "ClusterAssociation": { "ClusterId": "CID12345678-1234-1234-1234-123456789012", "State": "DISASSOCIATED" } } ] } Matikan dan kembalikan perangkat yang tidak sehat ke AWS. Untuk informasi selengkapnya, lihat Mem atikan Tepi Bola Salju dan Mengembalikan Perangkat Tepi Bola Salju.
Saat perangkat pengganti tiba, gunakan prosedur berikut untuk menambahkannya ke cluster.
Untuk menambahkan perangkat pengganti
-
Posisikan perangkat pengganti untuk cluster sedemikian rupa sehingga Anda memiliki akses ke depan, belakang, dan atas semua perangkat.
-
Nyalakan node dan pastikan bahwa node terhubung ke jaringan internal yang sama dengan seluruh cluster. Untuk informasi selengkapnya, lihat Menghubungkan ke Jaringan Lokal Anda.
-
Gunakan
unlock-clusterperintah dan sertakan alamat IP dari node baru.snowballEdge unlock-cluster --manifest-filepath/to/manifest/file.bin--unlock-codeunlock-code--endpoint https://ip-address-of-cluster-device--device-ip-addressesnode-1-ip-address node-2-ip-address new-node-ip-addressKeadaan node baru akan
DEGRADEDsampai Anda mengaitkannya dengan cluster pada langkah berikutnya. -
Gunakan
associate-deviceperintah untuk mengaitkan node pengganti dengan cluster.snowballEdge associate-device --device-ip-addressnew-node-ip-addresscontoh dari keluaran
perintah perangkat asosiasiAssociating your Snowball Edge device with the cluster. Your Snowball Edge device will be associated with the cluster when it is in the ASSOCIATED state. You can use the describe-device command to determine the state of your devices. -
Gunakan
describe-clusterperintah untuk memastikan node baru dikaitkan dengan cluster.snowballEdge describe-cluster --manifest-filepath/to/manifest/file.bin--unlock-codeunlock-code--endpoint https://node-ip-addresscontoh dari kelu
aran perintah describe-cluster{ "ClusterId": "CID12345678-1234-1234-1234-123456789012", "Devices": [ { "DeviceId": "JID12345678-1234-1234-1234-123456789012", "UnlockStatus": { "State": "UNLOCKED" }, "ActiveNetworkInterface": { "IpAddress": "10.0.0.0" }, "ClusterAssociation": { "ClusterId": "CID12345678-1234-1234-1234-123456789012", "State": "ASSOCIATED" }, "NetworkReachability": { "State": "REACHABLE" }, "Tags": [] }, { "DeviceId": "JID-CID12345678-1234-1234-1234-123456789013", "UnlockStatus": { "State": "UNLOCKED" }, "ActiveNetworkInterface": { "IpAddress": "10.0.0.1" }, "ClusterAssociation": { "ClusterId": "CID12345678-1234-1234-1234-123456789012", "State": "ASSOCIATED" }, "NetworkReachability": { "State": "REACHABLE" }, "Tags": [] }, { "DeviceId": "JID-CID12345678-1234-1234-1234-123456789015", "UnlockStatus": { "State": "UNLOCKED" }, "ActiveNetworkInterface": { "IpAddress": "10.0.0.2" }, "ClusterAssociation": { "ClusterId": "CID12345678-1234-1234-1234-123456789012", "State": "ASSOCIATED" }, "NetworkReachability": { "State": "REACHABLE" }, "Tags": [] } } ] } -
Pada node baru, buat dua antarmuka jaringan virtual (VNI). Untuk informasi selengkapnya, lihat Memulai penyimpanan yang kompatibel dengan Amazon S3 di layanan Snowball Edge
-
Gunakan
stop-serviceperintah untuk menghentikan layanan s3-snow.snowballEdge stop-service --service-id s3-snow --device-ip-addressescluster-device-1-ip-address cluster-device-2-ip-address cluster-device-3-ip-address--manifest-filepath/to/manifest/file.bin--unlock-codeunlock-code--endpoint https://snow-device-ip-addresscontoh dari output
perintah stop-serviceStopping the AWS service on your Snowball Edge. You can determine the status of the AWS service using the describe-service command. -
Gunakan
start-serviceperintah untuk memulai layanan s3-snow setelah menambahkan node baru ke cluster.snowballEdge start-service --service-id s3-snow --device-ip-addressescluster-device-1-ip-address cluster-device-2-ip-address cluster-device-3-ip-address--virtual-network-interface-arns "device-1-vni-ip-address-a" "device-1-vni-ip-address-b" "device-2-vni-ip-address-a" "device-2-vni-ip-address-b" "device-3-vni-ip-address-a" "device-3-vni-ip-address-b" --manifest-filepath/to/manifest/file.bin--unlock-codeunlock-code--endpoint https://snow-device-ip-addresscontoh dari
outputperintah start-serviceStarting the AWS service on your Snowball Edge. You can determine the status of the AWS service using the describe-service command. -
Gunakan
describe-serviceperintah untuk memastikan layanan s3-snow dimulai.snowballEdge describe-service --service-id s3-snow --device-ip-addressessnow-device-1-address snow-device-2-address snow-device-3-address--manifest-filepath/to/manifest/file.bin--unlock-codeunlock-code--endpoint https://snow-device-ip-addresscontoh dari output
perintah descibe-service{ "ServiceId": "s3-snow", "Autostart": true, "Status": { "State": "ACTIVE" }, "ServiceCapacities": [{ "Name": "S3 Storage", "Unit": "Byte", "Used": 38768180432, "Available": 82961231819568 }], "Endpoints": [{ "Protocol": "https", "Port": 443, "Host": "10.0.0.10", "CertificateAssociation": { "CertificateArn": "arn:aws:snowball-device:::certificate/7Rg2lP9tQaHnW4sC6xUzF1vGyD3jB5kN8MwEiYpT" }, "Description": "s3-snow bucket API endpoint (for s3control SDK)", "DeviceId": "JID12345678-1234-1234-1234-123456789012", "Status": { "State": "ACTIVE" } }, { "Protocol": "https", "Port": 443, "Host": "10.0.0.11", "CertificateAssociation": { "CertificateArn": "arn:aws:snowball-device:::certificate/7Rg2lP9tQaHnW4sC6xUzF1vGyD3jB5kN8MwEiYpT" }, "Description": "s3-snow object & bucket API endpoint (for s3api SDK)", "DeviceId": "JID12345678-1234-1234-1234-123456789013", "Status": { "State": "ACTIVE" } }, { "Protocol": "https", "Port": 443, "Host": "10.0.0.12", "CertificateAssociation": { "CertificateArn": "arn:aws:snowball-device:::certificate/7Rg2lP9tQaHnW4sC6xUzF1vGyD3jB5kN8MwEiYpT" }, "Description": "s3-snow bucket API endpoint (for s3control SDK)", "DeviceId": "JID12345678-1234-1234-1234-123456789015", "Status": { "State": "ACTIVE" } }, { "Protocol": "https", "Port": 443, "Host": "10.0.0.13", "CertificateAssociation": { "CertificateArn": "arn:aws:snowball-device:::certificate/7Rg2lP9tQaHnW4sC6xUzF1vGyD3jB5kN8MwEiYpT" }, "Description": "s3-snow object & bucket API endpoint (for s3api SDK)", "DeviceId": "JID-beta-207012320001-24-02-05-17-17-27", "Status": { "State": "ACTIVE" } }, { "Protocol": "https", "Port": 443, "Host": "10.0.0.14", "CertificateAssociation": { "CertificateArn": "arn:aws:snowball-device:::certificate/7Rg2lP9tQaHnW4sC6xUzF1vGyD3jB5kN8MwEiYpT" }, "Description": "s3-snow bucket API endpoint (for s3control SDK)", "DeviceId": "JID-beta-207012240003-24-02-05-17-17-28", "Status": { "State": "ACTIVE" } }, { "Protocol": "https", "Port": 443, "Host": "10.0.0.15", "CertificateAssociation": { "CertificateArn": "arn:aws:snowball-device:::certificate/7Rg2lP9tQaHnW4sC6xUzF1vGyD3jB5kN8MwEiYpT" }, "Description": "s3-snow object & bucket API endpoint (for s3api SDK), "DeviceId": "JID-beta-207012320001-24-02-05-17-17-28", "Status": { "State": "ACTIVE" } } }] }