Solution when an ISM login failure occurs

1

Solution when an ISM login failure occurs:
1. Ensure that the user name and password are correct. Check whether a login to the storage array using SSH is successful.
2. Check whether there is firewall that shields the ISM port. Check whether a login to the storage array through direct connection is successful.
3. Check whether there are problems related to flash card I/O errors of S2600 storage arrays. If yes, contact Huawei technical support engineers.
4. Check whether there are multiple logins to the S2600 R1 storage array. If yes, log out and log in again.
5. Uninstall ISM currently being used, download ISM on the storage array, and log in to ISM again.
6. If you encounter any other faults, contact Huawei technical support engineers.

Other related questions:
Solution when a disk failure occurs
Solution when a disk failure occurs: Troubleshooting: 1. If the disk is not removed and inserted, collect the S.M.A.R.T information of the disk and send the information to the R&D for analysis. 2. Apply for spare parts and replace the faulty disk.

Failed to log in to the web management system of the IAD
To rectify the fault when you fail to log in to the web management system of the IAD, perform the following steps: Step 1 Verify that the IP address is reachable and that there is no firewall between the PC and the IAD. Step 2 Ensure that the IAD version is V300R001C07 or later. In versions earlier than V300R001C07, web access is not supported excluding IAD 208E V300R001C03. Step 3 Run the system soft-parameter http-switch on command to enable web access. The IAD104H supports this command.

Failure to log in to ISM
Uninstall ISM from the management terminal and install it again.

Problem and solution when disk isolation occurs
You can perform the following operations when disk isolation occurs: The following causes may result in disk isolation: Bit error Reinserting disks repeatedly Disk power connection problem 1. Bit error Check the bit error of back-end SAS disks. Search keywords err inc and disable disk phy in the SES log. Note: phy:9 phymon***disable disk phy in the log shows that disk phy 9 is isolated. That is, the disk in slot 9 is isolated (phy0 to phy23 corresponds to disk 0 to 23). Troubleshooting 1. Before removing a faulty disk, collect S.M.A.R.T. information. 2. If conditions permit, insert the isolated disk to other slots to check whether isolation is caused by the disk or the slot. If isolation is caused by the disk, apply for disk replacement. If isolation is caused by the slot, check whether the slot has any foreign objects. Check the bit error on Fibre Channel disks. Search keyword lcv that is Fibre Channel bit errors in the SES log. If HD 0 and lcv ffff are displayed, the information indicates that a large quantity of bit errors are produced in slot 0 and cause disk isolation. The back-end Fibre Channel bit errors can spread from the port to the disk. If a Fibre Channel disk is isolated, check whether bit errors occur on the port by using the following methods: Check on the ISM. Enter fc allinfo in MML mode. Note: If any information displayed is not 0, bit errors exist. If bit errors are detected on the port, verify whether bit error are generated in the link. For details about how to verify, see the troubleshooting cases for a single link failure of the Fibre Channel enclosure disk caused by bit errors. Troubleshooting: If only one disk fails, verify the failure by using the above method. If a link fails, replace the optical module and optical cables and verify the failure. If a link does not fail, use the same method as one carried out on the SAS disk. If multiple disks are faulty, refer to the troubleshooting cases for a single link failure of the Fibre Channel enclosure disk caused by bit errors. 2. Reinserting disks repeatedly Note: A drive can isolate the disk from other ones if intermittent disconnections occur on the disk. Reinserting disks repeatedly may lead to disk isolation. Verify whether the disk is reinserted many times within a short period. If such a case exists, reinserting disk may result in disk isolation. Troubleshooting: Reinsert the disk. 3. Disk power connection problem Note: If the disk enclosure is affected by violent shaking, disk power may be insecurely connected and the disk is isolated. Troubleshooting: Contact R&D engineers for further analysis.

What are the common causes of the failure to initiate a SiteCall?
Common causes of the failure to initiate a SiteCall: An endpoint can initiate a SiteCall only after registering with the GK server through the allocated account and password. Log in to the web interface, choose System > Admin > Call > H.323, and set the following parameters: Register on GK: Select Enable. GK IP: Enter the GK/SC address. (The management platform can be the MCU's built-in web interface or SMC1.0/2.0.) Site number: Enter the site ID allocated by the platform. User name: The value must be the same as that specified on the management platform. Password: The value must be the same as that specified on the management platform. HUAWEI GK: Select Enable.

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