IP failover policy of V3 series unified storage


During the system initialization, the system automatically adds all Ethernet ports and bond ports of clusters to the default failover group. An IP address fails over first to the port at the same position in the peer controller, then to ports at other positions in the peer controller, and last to ports in the local controller. It can float between various interface modules. Which port it floats to is related with the port location, not the port rate. Later versions will allow you to customize failover groups.

Other related questions:
How is IP failover configured for V3 series unified storage?
IP failover allows rapid service migration from the faulty port to another available port of the same type without interrupting host services and the process is transparent to users. After the faulty port recovers, it takes over its services again. For details about how to configure IP failover, see IP Address Failover Deployment Guide.

Quota tree function of V3 series unified storage
A quota tree is the root directory of a file system. Quota trees are special directories. The following distinguishes a quota tree from a common directory: 1. Quota trees can only be created, deleted, or renamed by administrators using the command-line interface (CLI) or graphical user interface (GUI). Only empty quota trees can be deleted. 2. Quota trees can be shared using protocols and cannot be renamed or deleted during sharing. 3. Administrators can manage quotas such as file quantity or capacity under the quota tree.

What's the logical port of V3 series unified storage?
Logical ports, used for file services' running, are created based on physical Ethernet ports, bond ports, or VLANs. If the parent port of a logical port running file services is faulty, an IP failover will be triggered and the services will automatically fail over to another available port based on the failover policy. If the owning controller of the logical port's current parent port is different from the file system's owning controller, the system will need to transfer I/Os between controllers, decreasing system performance.

RAID levels supported by unified storage systems
RAID policies (levels) supported by unified storage systems: 0, 1, 3, 5, 6, 10, 50

Rules for configuring the hot spare policy for OceanStor V3 unified storage systems
For OceanStor V300R001 storage systems, proper hot spare policies must be configured to ensure the reliability of the storage system. For details about planning the hot spare policy, see Planning the Capacity .

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