In some application scenarios, one controller of a dual-controller storage system fails to be logged in to because its network cable is disconnected or the IP address of the controller is lost. Therefore, the information on the controller cannot be viewed. Onsite engineers can access the controller by using the serial port. In this case, the controller is remotely accessed by using the heartbeat IP address.
The peer controller can be accessed by using the heartbeat IP address in debug mode. Run the rcp command to replicate the files on the two controllers and log in to the peer controller by using the SSH tool. To replicate the backup_info.zip file in the /tmp directory from controller A to controller B, run the rcp 192.168.2.11:/tmp/backup_info.zip /tmp/ command. To replicate the ST9SPCS03C021.01.01.215.T02.tgz file in the /OSM/update directory from controller B to the /OSM/update directory of controller A, run the rcp /OSM/updata/ST9SPCS03C021.01.01.215.T02.tgz 192.168.2.10:/OSM/update command. Type yes and press Enter, and then type the password of user admin according to the prompt. The files start to be replicated. Run the ssh 192.168.2.11 command to view the status of controller B from controller A.
During remote maintenance, the management IP address of the peer controller cannot be pinged through.
Huawei Symantec V1000, S2000, S5000, S6800E, and S2600 storage devices all have two controllers. The heartbeat IP addresses exist between two controllers to monitor controller status. The default heartbeat IP addresses of controllers A and B are 192.168.2.10 and 192.168.2.11. Run the ifconfig command to check whether the heartbeat IP address is configured on port bond0.