No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

Installation Guide

OceanStor 5000, 5000F, 6000, and 6000F V5 Series V500R007

This document is applicable to OceanStor 5110 V5, 5110F V5, 5300 V5, 5300F V5, 5500 V5, 5500F V5, 5600 V5, 5600F V5, 5800 V5, 5800F V5, 6800 V5, and 6800F V5 storage systems. It describes hardware installation of those storage systems for helping you easily and quickly finish the installation.
Rate and give feedback :
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Clearing the Controllers That Failed to Be Added

Clearing the Controllers That Failed to Be Added

If controller expansion fails, you must clear the controllers that failed to be added before expanding controllers again.

Prerequisites

  • You have completed the operations described in Rolling Back the Storage System.
  • You have removed the management network cables and PCIe cables of storage systems that have not been added to the cluster to isolate controllers.

  • This operation is only used to clear the controllers in an added controller enclosure. If OceanStor 6000 series storage systems are expanded from two to six controllers or two to eight controllers, you are advised to remove the new controllers from the original controller enclosure, follow instructions of this section to clear the controllers in the added controller enclosure, and perform controller expansion again.
  • You must perform Step 1 to Step 6 on each controller separately.

Procedure

  1. Log in to a controller that failed to be added via its serial port or management network port and check whether the following information is displayed in the CLI.

    Storage: minisystem>
    • If yes, the controller is in minisystem mode. Go to Step 2.
    • If no, the controller is not in minisystem mode. You must enter the minisystem mode before proceeding with Step 2. You can manually enter the minisystem mode as follows:
      • Run change user_mode current_mode user_mode=developer to enter the developer mode and then run minisystem to enter the minisystem mode.
        developer:/>minisystem 
        Storage: minisystem>
      • When the storage system is starting, System is not ready, Please wait(Ctrl+c to exit or Input minisystem to minisystem mode) is displayed on the CLI. Run minisystem to enter the minisystem mode.
        Authorized users only. All activities may be monitored and reported. 
        WARNING! The remote SSH server rejected X11 forwarding request. 
         
        WARNING: You have accessed the system. 
        You are required to have a personal authorisation from the system administrator before you use this computer. Unauthorised access to or misuse of this system is prohibited. 
         
        System is not ready, Please wait(Ctrl+c to exit or Input minisystem to minisystem mode).\minisystem     
    NOTE:

    If you cannot log in to a controller (for example, controller A) using the serial port or management network port, log in to another controller in the controller enclosure (for example, controller B) and run the sshtoremoteExt SlotId command in minisystem mode to log in to controller A. SlotId is controller A's slot number and its value ranges from 0 to N–1, where N indicates the total number of controllers after controller expansion. 2 U controller enclosures are used as an example. The slot IDs of controllers A and B in controller enclosure 0 are 0 and 1, those of controllers A and B in controller enclosure 1 are 2 and 3, and so are other slot IDs. 6 U controller enclosures are used as an example. The slot IDs of controllers A, B, C, and D in controller enclosure 0 are 0, 1, 2, and 3, and those of controllers A, B, C, and D in controller enclosure 1 are 4, 5, 6, and 7; and so are other slot IDs.

  2. Run bdm_diskbomlist.sh showdisk and check whether Valid of coffer disks (Slot ranges from 0 to 3 and ID is greater than 63) is Normal.

  3. Wait for 20 minutes and run bdm_diskbomlist.sh showdisk again to check whether Valid of the coffer disks is Normal.

  4. Run showsysstatus. The value of local node id is the ID of the current controller. Check whether the controller's status is normal.

    • If yes, perform Step 1 to Step 4 on each controller that failed to be added separately. If all controllers' status are normal, expand controllers again using the expansion tool.
    • If no, go to Step 5.

  5. Run sys.sh clearnode -d in minisystem mode. The system will clear information automatically. This process typically takes about 2 minutes and will not exceed 30 minutes.

    Check whether Clear node succeeded is returned.

    NOTE:
    • This operation will restore all services and configurations of the controller to the initial state.
    • This operation will initialize user passwords. For the default password of the system administrator, see OceanStor V5 Series V500R007 Security Configuration Guide.

  6. Observe the indicators to determine whether the controller is running properly and the coffer disks are normal. For the indicator meanings, see the Product Description of the corresponding product model.

    • If the controller and coffer disks are normal, return to Step 1 and perform the operations again.
    • If the controller or coffer disks are abnormal, go to Step 9.

  7. Repeat the preceding procedure on other controllers to clear their information.

    • For 5000/5000F series storage systems, after all controllers have been cleared, log in to any of them and run sys.sh resetengine -n to reset all controllers in the current controller enclosure. If the controller enclosure becomes normal after the controllers have been reset, go to Step 8.
    • For 6000/6000F series storage systems, if the new controller enclosure has four controllers, after all controllers have been cleared, log in to any of them and run sys.sh resetengine -n to reset all controllers in the current controller enclosure. If the controller enclosure becomes normal after the controllers have been reset, go to Step 8.
    • For 6000/6000F series storage systems, if the new controller enclosure has two controllers, after both controllers have been cleared, log in to any of them and run sys.sh resetengine -p to reset all controllers in the current controller enclosure. If the controller enclosure becomes normal after the controllers have been reset, go to Step 8.
    • If the controller enclosure fails to restore to normal, go to Step 9.

  8. Use the expansion tool to expand controllers again.

    • If the expansion is successful, no further action is required.
    • If expansion fails, go to Step 9.

  9. Collect system logs and contact technical support engineers for assistance.

    To collect system logs:

    • Log in to DeviceManager. If you can access the console, choose Settings > Export Data. Select All logs under System Log and click Log List. The system starts collecting logs.
    Figure 11-16 Exporting system logs

    • If Failed to start the system is displayed when you log in to DeviceManager, click Download Log to download system logs.
    Figure 11-17 Downloading logs

    • If a controller fails to be powered on, log in to the controller and enter the minisystem mode. Then run os_backup_info.sh to collect logs and access the log path to obtain the logs.

Translation
Download
Updated: 2019-07-11

Document ID: EDOC1000181531

Views: 93078

Downloads: 868

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next