Esta página ainda não está disponível no idioma selecionado. Estamos trabalhando para adicionar mais opções de idiomas. Agradecemos sua compreensão.

Compute
Elastic Cloud Server
Huawei Cloud Flexus
Bare Metal Server
Auto Scaling
Image Management Service
Dedicated Host
FunctionGraph
Cloud Phone Host
Huawei Cloud EulerOS
Networking
Virtual Private Cloud
Elastic IP
Elastic Load Balance
NAT Gateway
Direct Connect
Virtual Private Network
VPC Endpoint
Cloud Connect
Enterprise Router
Enterprise Switch
Global Accelerator
Management & Governance
Cloud Eye
Identity and Access Management
Cloud Trace Service
Resource Formation Service
Tag Management Service
Log Tank Service
Config
OneAccess
Resource Access Manager
Simple Message Notification
Application Performance Management
Application Operations Management
Organizations
Optimization Advisor
IAM Identity Center
Cloud Operations Center
Resource Governance Center
Migration
Server Migration Service
Object Storage Migration Service
Cloud Data Migration
Migration Center
Cloud Ecosystem
KooGallery
Partner Center
User Support
My Account
Billing Center
Cost Center
Resource Center
Enterprise Management
Service Tickets
HUAWEI CLOUD (International) FAQs
ICP Filing
Support Plans
My Credentials
Customer Operation Capabilities
Partner Support Plans
Professional Services
Analytics
MapReduce Service
Data Lake Insight
CloudTable Service
Cloud Search Service
Data Lake Visualization
Data Ingestion Service
GaussDB(DWS)
DataArts Studio
Data Lake Factory
DataArts Lake Formation
IoT
IoT Device Access
Others
Product Pricing Details
System Permissions
Console Quick Start
Common FAQs
Instructions for Associating with a HUAWEI CLOUD Partner
Message Center
Security & Compliance
Security Technologies and Applications
Web Application Firewall
Host Security Service
Cloud Firewall
SecMaster
Anti-DDoS Service
Data Encryption Workshop
Database Security Service
Cloud Bastion Host
Data Security Center
Cloud Certificate Manager
Edge Security
Situation Awareness
Managed Threat Detection
Blockchain
Blockchain Service
Web3 Node Engine Service
Media Services
Media Processing Center
Video On Demand
Live
SparkRTC
MetaStudio
Storage
Object Storage Service
Elastic Volume Service
Cloud Backup and Recovery
Storage Disaster Recovery Service
Scalable File Service Turbo
Scalable File Service
Volume Backup Service
Cloud Server Backup Service
Data Express Service
Dedicated Distributed Storage Service
Containers
Cloud Container Engine
Software Repository for Container
Application Service Mesh
Ubiquitous Cloud Native Service
Cloud Container Instance
Databases
Relational Database Service
Document Database Service
Data Admin Service
Data Replication Service
GeminiDB
GaussDB
Distributed Database Middleware
Database and Application Migration UGO
TaurusDB
Middleware
Distributed Cache Service
API Gateway
Distributed Message Service for Kafka
Distributed Message Service for RabbitMQ
Distributed Message Service for RocketMQ
Cloud Service Engine
Multi-Site High Availability Service
EventGrid
Dedicated Cloud
Dedicated Computing Cluster
Business Applications
Workspace
ROMA Connect
Message & SMS
Domain Name Service
Edge Data Center Management
Meeting
AI
Face Recognition Service
Graph Engine Service
Content Moderation
Image Recognition
Optical Character Recognition
ModelArts
ImageSearch
Conversational Bot Service
Speech Interaction Service
Huawei HiLens
Video Intelligent Analysis Service
Developer Tools
SDK Developer Guide
API Request Signing Guide
Terraform
Koo Command Line Interface
Content Delivery & Edge Computing
Content Delivery Network
Intelligent EdgeFabric
CloudPond
Intelligent EdgeCloud
Solutions
SAP Cloud
High Performance Computing
Developer Services
ServiceStage
CodeArts
CodeArts PerfTest
CodeArts Req
CodeArts Pipeline
CodeArts Build
CodeArts Deploy
CodeArts Artifact
CodeArts TestPlan
CodeArts Check
CodeArts Repo
Cloud Application Engine
MacroVerse aPaaS
KooMessage
KooPhone
KooDrive
On this page

Show all

Help Center/ Auto Scaling/ User Guide (Kuala Lumpur Region)/ FAQs/ AS Group/ What Can I Do If the AS Group Fails to Be Enabled?

What Can I Do If the AS Group Fails to Be Enabled?

Updated on 2022-08-15 GMT+08:00

The possible causes and solutions are as follows:

  • Issue description: Insufficient ECS, EVS disk or EIP quota.

    Possible cause: insufficient quota

    Handling method: Increase the quota or delete unnecessary resources, and then enable the AS group.

  • Issue description: The VPC or subnet does not exist.

    Possible cause: The VPC service encounters an exception or resources have been deleted.

    Handling method: Wait until the VPC service recovers, or modify parameters of the VPC and subnet in the AS group, and then enable the AS group.

  • Issue description: The ELB listener or backend ECS group does not exist, and the load balancer is unavailable.

    Possible cause: The ELB service encounters an exception or resources have been deleted.

    Handling method: Wait until the ELB service recovers, or modify load balance parameters in the AS group, and then enable the AS group.

  • Issue description: The number of backend ECSs that you add to the ELB listener exceeds the upper limit.

    Possible cause: If classical load balancer is used by an AS group, instances added to the AS group are automatically added to the ELB listener. A maximum of 300 backend ECSs can be added to an ELB listener.

    Handling method: Remove the backend ECSs that are both not required and not in the AS group from the listener. Then enable the AS group.

  • Issue description: The image used by the AS configuration, the flavor, or the key pair does not exist.

    Possible cause: Resources have been deleted.

    Handling method: Change the AS configuration for the AS group and then enable the AS group.

  • Issue description: The notification subject configured for your lifecycle hook does not exist.

    Possible cause: The AS group adds a lifecycle hook, while its configured notification subject has been deleted before the scaling action starts. If the notification subject is deleted after the scaling action starts, an AS group exception will occur in the next scaling action.

    Handling method: Change the notification subject used by the lifecycle hook or delete the lifecycle hook. Then enable the AS group.

  • Issue description: The subnet you select does not have enough private IP addresses.

    Possible cause: Private IP addresses in the subnet used by the AS group have been used up.

    Handling method: Modify the subnet information and enable the AS group.

  • Issue description: The ECS resources of this type in the selected AZ have been sold out.

    Possible cause: ECSs of this type have been sold out or are not supported in the AZ selected for the AS group. ECSs of this type are the ECS flavor selected in the AS configuration.

    Handling method: Change the AS configuration for the AS group and then enable the AS group. If there is no instance in the AS group, you can also change the AZ for the AS group and then enable the AS group.

  • Issue description: The selected specifications and the disk do not match.

    Possible cause: The ECS type in the AS configuration does not match the disk type, leading to the ECS creation failure.

    Handling method: Change the AS configuration for the AS group and then enable the AS group.

  • Issue description: The selected specifications and the image do not match.

    Possible cause: The ECS type in the AS configuration does not match the image, leading to the ECS creation failure.

    Handling method: Change the AS configuration for the AS group and then enable the AS group.

  • Issue description: Storage resources of this type have been sold out in the selected AZ.

    Possible cause: Storage resources of this type have been sold out or are not supported in the AZ selected for the AS group. Storage resources of this type refer to the system and data disk types selected for the AS configuration.

    Handling method: Change the AS configuration for the AS group and then enable the AS group. If there is no instance in the AS group, you can also change the AZ for the AS group and then enable the AS group.

  • Issue description: The shared bandwidth defined in the AS configuration does not exist.

    Possible cause: Resources have been deleted.

    Handling method: Use a newly purchased or an existing shared bandwidth to create an AS configuration. Then change the AS configuration for the AS group and enable the AS group.

  • Issue description: The number of EIPs bound to the shared bandwidth specified in the AS configuration exceeds the limit.

    Possible cause: A maximum of 20 EIPs can be bounded to a shared bandwidth.

    Handling method: Apply for a higher EIP quota, remove unnecessary EIPs from the shared bandwidth, or change another AS configuration for the AS group. Then enable the AS group.

  • Issue description: The DeH selected in your AS configuration does not exist. Change the AS configuration.

    Possible cause: Resources have been deleted.

    Handling method: Use a newly purchased or an existing DeH to create an AS configuration. Then change the AS configuration for the AS group and enable the AS group.

  • Issue description: No DeH is available. Ensure that there are available DeH resources.

    Handling method: Rectify the DeH fault and restore the DeH to the available state, or enable the automatic placement attribute for the DeH, and then enable the AS group again. You can also use a newly purchased DeH to create an AS configuration, change the AS configuration for the AS group, and enable the AS group.

  • Issue description: The DeH selected in your AS configuration does not have sufficient capacity.

    Handling method: You can delete unnecessary ECSs from the DeH and enable the AS group again. You can also use a newly purchased DeH to create an AS configuration, change the AS configuration for the AS group, and enable the AS group.

  • Issue description: No DeH is available in the AZ selected for your AS group.

    Handling method: Purchase a DeH in the AZ, use it to create an AS configuration, change the AS configuration for the AS group, and enable the AS group. If there is no instance in the AS group, change the AZ for the AS group and then enable the AS group.

  • Issue description: The DeH selected in your AS configuration does not support this type of ECS. Change the AS configuration.

    Handling method: Select the ECS specifications supported by the DeH, create an AS configuration, change the AS configuration for the AS group, and then enable the AS group again.

  • Issue description: A system error has occurred.

    Possible cause: An error has occurred in the AS service, peripheral service, or network.

    Handling method: Try again later or contact technical support.

  • Issue description: The specification defined in the AS configuration is unavailable.

    Handling method: Change specifications by creating an AS configuration as prompted by the error message and use this AS configuration for the AS group. Then enable the AS group.

  • Issue description: The selected AS configuration cannot be used by the AS group.

    Handling method: Create an AS configuration as prompted by the error message and use this AS configuration for the AS group. Then enable the AS group.

  • Issue description: AS group expansion fails.

    Possible cause: Your account is in arrears or the balance is insufficient.

    Handling method: Top up your account and enable the AS group.

Usamos cookies para aprimorar nosso site e sua experiência. Ao continuar a navegar em nosso site, você aceita nossa política de cookies. Saiba mais

Feedback

Feedback

Feedback

0/500

Selected Content

Submit selected content with the feedback