Actions taken if the number of nodes exceeds the upper limit during the adding of a secondary node

8

This fault occurs if the model of the storage device is not detected, or the number of nodes in the license file is incorrect or exceeds the specifications. To rectify the fault, ensure the following:
- That the storage device is correctly connected.
Log in to the storage device as user support and check whether disk array information exists in Internet Small Computer Systems Interface (iSCSI).
- That the number of nodes for each network attached storage (NAS) feature in the license file is consistent with that of configured nodes.
The number of nodes for each NAS feature must be equal to or larger than that of configured nodes.
- That the number of configured nodes does not exceed that of the nodes mapping to the storage device in the specifications list.

Other related questions:
Actions taken if the hardware is inconsistent with the standard configuration during the adding of a secondary node
The file engine configuration varies depending on the device model. If an incorrect configuration is selected, the configuration fails. Use the correct controller module or CPU/memory.

Actions taken if a file engine node works incorrectly
If a file engine node is working incorrectly, perform the following procedure: 1. Ensure that heartbeat connections and heartbeat switches are working correctly. 2. Ensure that the faulty node is correctly started up.

Maximum number of nodes in an OceanStor 9000 V100R001C01 cluster
Maximum number of nodes in an OceanStor 9000 V100R001C01 cluster: 288

Query the active node of the OpenStack controller node during eBackup installation
To query the active node of the OpenStack controller node, do as follows: 1. Log in to the OpenStack reverse proxy in SSH mode. 2. Run the su-root command and enter the password of user root as prompted to switch to user root. 3. Run the source set_env command, select openstack environment variable (keystone v3), and enter the password to import environment variables. 4. Run the cps template-instance-list --service cps cps-server command. In the command output, the node whose status is active is the active node of the controller node.

When you set an intelligent analysis alarm linkage action, the system displays a message indicating that the number of devices exceeds the upper limit.
As restricted by the VCN3000 platform, a maximum of four cameras can be selected for an alarm linkage action.

If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top