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

FusionAccess V100R006C20 Alarm Handling 05 (FusionSphere 6.3.1)

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).
1003006 WI Works in Emergency Mode

1003006 WI Works in Emergency Mode

Description

When a user enters the username and password on the WI for login, the WI performs user authentication on the AD server. This alarm is generated when the authentication fails due to an AD server fault or network exception and the user enters the emergency mode. When the authentication becomes normal, the alarm must be cleared manually.

Attribute

Alarm ID

Alarm Severity

Auto Clear

1003006(1002009)

Critical

No

Parameters

Name

Meaning

Alarm ID

Identifies an alarm. Each alarm is uniquely identified by an alarm ID and an alarm name.

Alarm Severity

Indicates the severity of an alarm. Value:

  • Critical: indicates that a fault affecting services provided by the system occurs. You need to rectify the fault immediately. If a device or resource is faulty, rectify it immediately even if the fault occurs during non-working hours.
  • Major: indicates that a fault affecting the service quality of the system occurs. You need to rectify the fault immediately. If the service quality of a device or resource is degraded, rectify it immediately during working hours.
  • Minor: indicates a fault that does not affect service quality. To prevent more serious faults, this type of alarm needs to be observed or handled if necessary.
  • Warning: indicates a fault that may affect service quality. This type of alarm must be handled based on the error type.

Alarm Name

Identifies an alarm. Each alarm is uniquely identified by an alarm ID and an alarm name.

Object Type

Specifies the type of the object for which the alarm is generated.

Alarm Object Name

Specifies the name of the object for which the alarm is generated.

Component Type

(This parameter exists only in FusionManager.)

Specifies the type of the component for which the alarm is generated.

Generation Time

Specifies the time when the alarm is generated.

Clear Time

Specifies the time when the alarm is cleared.

Clear Mode

Specifies whether the alarm is manually or automatically cleared.

Operation

Specifies the operation that can be performed on the alarm.

Value: Manually Clear Alarm

Impact on the System

When the user enters the emergency mode:

  • The user cannot use the following WI functions: (forcibly) restarting VMs, using the self-help console, logging in to pool VMs, and change passwords.
  • User login takes a long time.

Possible Causes

  • The time difference between the WI and the AD exceeds 5 minutes.
  • A network fault occurs between the WI and the AD.
  • The AD server is abnormal.

Procedure

Check whether the times of the WI and AD servers are the same.

  1. Log in to the WI and AD servers independently to view the time. If the time difference is within 5 minutes, see 1000017 Communication Between the System and the NTP Server Is Abnormal.

    NOTE:
    • WI server: Log in to the Linux server as user gandalf and run the date command.
    • AD server: If the AD server runs Windows, log in to the AD server using a domain account. Choose Start > Run, enter cmd. Run time on the CLI that is displayed to view the time. If the AD server runs Linux, log in to the server as user gandalf and run the date command.

  2. Clear the alarm manually. Log in to the WI server to view whether the alarm still exists?

    • If yes, go to Step 3.
    • If no, no further operation is required.

Check the network connection between the WI and AD servers.

  1. Log in to the WI server as user gandalf, and check whether the AD server network connection is normal.

    Run ping IP address of the AD server on the CLI to check whether the network is normal.

    • If yes, go to Step 6.
    • If no, go to Step 4.

      The communication is normal if the command output is as follows:

      Pinging 192.168.90.102 with 32 bytes of data: 
       
      Reply from 192.168.90.102: bytes=32 time<1ms TTL=128 
      Reply from 192.168.90.102: bytes=32 time<1ms TTL=128 
      Reply from 192.168.90.102: bytes=32 time<1ms TTL=128 
      Reply from 192.168.90.102: bytes=32 time<1ms TTL=128 
           (Note: The IP addresses are only examples. Use the actual IP addresses.)

  2. Locate and rectify the network fault.
  3. Clear the alarm manually. Log in to the WI server to view whether the alarm still exists?

    • If yes, go to Step 6.
    • If no, no further operation is required.

Check the AD server port.

  1. Check the type of the AD server OS.

    • If the OS is Windows, go to Step 7.
    • If the OS is Linux, go to Step 8.

  2. Log in to the AD server using an existing domain account, and check whether TCP port 445 is available.

    • Choose Start > Run, enter cmd, and click OK to enter the command-line interface.
    • Enter netstat -ano|findstr port. Check whether the status of the port is LISTENING.
    • If yes, go to Step 11.
    • If no, go to Step 9.

  3. Log in to the AD server as user gandalf, and check whether TCP port 445 is available. Run the shell command netstat -an | grep 445 to check whether the status of port 445 is listening.

  4. Locate and rectify the TCP port fault.
  5. Clear the alarm manually. Log in to the WI server to view whether the alarm still exists?

    • If yes, go to Step 11.
    • If no, no further operation is required.

Check whether the AD server is faulty.

  1. Check the type of the AD server OS.

    • If the OS is Windows, go to Step 12.
    • If the OS is Linux, go to Step 20.

  2. Log in to the AD server using the domain account, choose Start > Administrative Tools > Services to open the service list, as shown in Figure 36-1. Check whether the Active Directory Domain Services is running properly.

    • If yes, go to Step 13.
    • If no, contact Huawei technical support.
    Figure 36-1 Active Directory Domain Services

  3. Create a domain user on the AD server. The account name is ADTest.

    For details, see Service Provisioning > Creating VM Users > Creating a Domain User in the FusionAccess Desktop Solution V100R006C20 Windows Desktop Management Guide.

  4. Manually clear the alarm, and login to a VM through WI, then check whether the domain user is created successfully.

  5. After 5 to 10 minutes, choose Start > Administrative Tools > Active Directory Users and Computers.
  6. Right-click the domain name, and choose Refresh. Click the organization unit (OU) to which the ADTest account belongs, and check whether the ADTest account is displayed in the right pane.

  7. Right-click the ADTest account, and choose Delete.

    After this step, go to Step 19.

  8. Restart the AD server.
  9. Manually clear the alarm, and login to a VM through WI, then check whether the alarm still exists.

    • If yes, contact Huawei technical support.
    • If no, no further operation is required.

  10. Log in to the ITA server as user gandalf and run sudo service samba-ad status to view whether the status of samba-ad is normal.

    • If yes, contact Huawei technical support.
    • If no, go to Step 21.

  11. Run sudo service samba-ad restart to restart samba-ad. Two minutes after successful restart, choose FusionManager > Monitoring or FusionAccess > Alarm to check whether the alarm still exists.

    • If yes, contact Huawei technical support.
    • If no, no further operation is required.

Related Information

None

Download
Updated: 2019-03-01

Document ID: EDOC1100010511

Views: 19664

Downloads: 11

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