symptom:
The domain name cannot be resolved because the capacity is full. As a result, the OAM-P maintenance commands cannot be delivered.
Diagnosis:
The OAM-P module fails to deliver the maintenance commands. After the dig oamp.service.com command is executed, the domain name fails to be resolved.
Cause:
The 3AZ floating address is configured as a domain name. When the DNS service is abnormal, the maintenance commands delivered by OAM-P fail to be authenticated and fail to access the database through the domain name.
Solution:
Use PuTTY to log in to an OAM node.
Run the vim /etc/hosts command to open the /etc/hosts file and configure the domain name and IP address resolution relationships of the OAM-P, OAM-GaussDB, and OAM-U components. That is, add the following three lines:
192.168.1.1 oamp.service.com
192.168.1.1 oamu.service.com
192.168.1.1 oamgs.service.com
The preceding IP address (192.168.1.1) is the storage IP address of the current OAM node.
Use PuTTY to log in to the other OAM node and switch the active nodes of the OAM-P, OAM-GaussDB, and OAM-U components to the peer node. If the current node is the standby node, no operation is required. The commands are as follows:
Querying the active/standby OAM-P: sudo -u oam sh /opt/dfv/oam/oam-p/ha/tools/getHAStatus.sh
Switching the active/standby OAM-P: sudo -u oam sh /opt/dfv/oam/oam-p/ha/tools/switchHA.sh
Querying the active/standy OAM-GaussDB: sh /opt/dfv/oam/oam-u/oam-gaussdb/ha/tools/getHAStatus.sh
Switching the active/standby OMA-GaussDB: sh /opt/dfv/oam/oam-u/oam-gaussdb/ha/tools/switchHA.sh
Querying the active/standby OAM-U: sh /opt/dfv/oam/oam-u/ha/tools/getHAStatus.sh
Switching the active/standby OAM-U: sh /opt/dfv/oam/oam-u/ha/tools/switchHA.sh
Log in to the OAM node in 1 and run the diagnose commands to restore storage pool services.
After the DNS service is restored, delete the domain name and IP address configured in 2.+
Check After Recovery:
Run the dig oamp.service.com command. An IP address is resolved.
