Method used to troubleshoot the failure of scanning for LUNs

2

Method used to troubleshoot the failure of scanning for LUNs:
1. Ensure that the network connection is correct.
2. On iSCSI networks, ensure that networks are normal and ping packets are not lost.
3. On Fibre Channel networks, ensure that the rate of ports on the host and array complies with the negotiated one.
4. Check whether configurations on the host and array are correct, including the mapping and initiator configurations.
5. On iSCSI networks, if the version of the host initiator is early, update the initiator software.
6. Check whether the array enters the DFT mode.
7. After the AIX host connects to Fibre Channel cables, to scan for LUNs successfully, you need to restart the host.
8. In SUSE 10 and SUSE 10 SP1, to scan for LUNs successfully, you need to update the iSCSI initiator.
9. If you encounter any other faults, contact technical support engineers.

Other related questions:
Method used to scan for mapped LUNs in the VMware ESX operating system
In the VMware ESX operating system, you scan for mapped LUNs as follows: Use the vSphere Client to log in to the VMware ESX host. In vSphere Client, click the Configuration tab. Select Storage in the Hardware area. In the View area of the right function pane, click Datastores. In the lower function pane, click Add Storage. The Add Storage dialog box is displayed. Scan for LUNs as prompted in the Add Storage dialog box.

Dealing with the failure to scan wavelengths using the OMCA
The board hardware may be faulty. You are advised to replace the OMCA board.

Troubleshoot call failures
If an intra-office call fails, perform the following steps: Step 1 Check whether the corresponding intra-office prefix is configured. For example, if the called number is 4000, at least one of prefixes 4, 40, 400, and 4000 with the call attribute being intra-office is configured. Step 2 Check whether the called number is registered. Step 3 Check whether call forwarding unconditional (CFU) is configured for the called number and whether the forward-to number is unreachable. Check whether the do not disturb (DND) is configured for the called number. Step 4 Check whether the address from which the calling number initiates the call is different from the registration address. Step 5 Run the show license command to check whether a temporary license is used and whether this license has expired. If an inter-office call fails, perform the following steps: Step 1 Run the show tkc office no x command to check the interconnection trunk status. The variable x indicates the office route number of the trunk. The trunk is functional if its status is displayed as IDLE. Step 2 Check whether the prefix is correctly associated with other relevant parameters. When you configure the prefix, you also need to configure the corresponding office route selection code, which needs to be associated with an office route. The office route needs to be associated with a trunk. Step 3 Check whether the calling number has the corresponding call rights. Step 4 Check whether the calling number is correct. Ensure that the calling number is the number allocated by the carrier in the case of connection to the carrier network. Step 5 Capture signaling messages and check whether the local end or peer end disconnects the call. If the local end disconnects the call, check the call disconnection time and the call setup request time. Maybe the peer end does not respond to the call setup request within the required time, causing call disconnection upon timeout. For the call disconnection causes, rectify the fault according to actual situations.

Method used to format a LUN on the storage
1. The LUN must be formatted after the LUN is created on the storage device. 2. After the LUN is created on the storage device, it is automatically formatted on the storage device without manual intervention. 3. The used LUNs cannot be formatted manually.

Revelations of troubleshooting-SSH login failure
If logging to the SSH server through STelnet fails, check the following configuration: 1. Check whether the SSH service is enabled on the SSH server. 2. Check whether the access protocol is correctly configured in the VTY user interface view. 3. Check whether an RSA public key is configured on the SSH server. 4. Check whether an SSH user is configured on the SSH server. 5. Check whether the number of login users on the SSH server reaches the upper limit. 6. Check whether an ACL is bound to the VTY user interface of the SSH server. 7. Check the SSH version on the SSH client and server. 8. Check whether first-time authentication is enabled on the SSH client.

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