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

eSight V300R010C00SPC200, 300, and 500 Operation Guide 09

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).
Storage Devices

Storage Devices

This topic describes how to resolve issues that may occur during storage management by using the eSight.

A Message Is Displayed Indicating Device Discovery Timeout During the N8500 Discovery

Question

When the N8500 storage system is being discovered, a message is displayed indicating device discovery timeout.

Answer

Required ports are not enabled or incorrect SSL method is used. Ensure that port 5988 or 5989 is enabled and select a correct SSL method to discover devices.

The Storage Device Menu Entrance Is Not Found After eSight Is Installed and Started

Question

After eSight is installed and started, the storage device menu entrance is not found.

Answer

The storage management components are optional and may not be installed together with eSight. Uninstall eSight and install the required storage components.

A Message Is Displayed Indicating a Failure to Obtain Information During the Storage Device Discovery

Question

When the SNMP parameters are correctly configured, a message is displayed indicating a failure to obtain information during the storage device discovery. The log indicates that a timeout error occurred.

Answer

On the menu bar, choose Resource > Common and choose Add Resource > Add Resource, configure Timeout Duration on the device discovery page.

How Can I Configure Parameters for HDP3500E

Question

Parameters must be configured when you add HDP3500E in eSight.

Answer

The parameters are described as follows:

  • SNMPv2c (default)
    • Port: 10161
    • Community: public/private
  • SNMPv3 (default)
    • Username: hdp3500e
    • Environment name: HDP3500E
    • Authentication protocol: HMAC-MD5
    • Authentication password: hdp3500e

How to Set Scheduled Export of Storage Information

Question

eSight enables information about Huawei storage devices to be exported as scheduled. You can enable or disable the scheduled export and set export time and path.

Answer

You can set scheduled export of storage information as follows:

In configuration file eSight installation directory\AppBase\app\com.huawei.esight.it.storageaccess\repository\as\com.huawei.esight.it.storageaccess.as.export-1.0-SNAPSHOT.jar\META-INF\timeExportConfig\ResExportCfg.xml, change the following parameter values:

  1. exswitch indicates the status of scheduled export. The configuration format is as follows:

    <exswitch>disable</exswitch>

    enable indicates that scheduled export is enabled. disable indicates that scheduled export is disabled. The default value is disable.

  2. extime indicates export time. The configuration format is as follows:

    <extime>16:30:00</extime>

    The time is in the 24-hour format. The time on eSight prevails. The default export time is 02:00.

  3. expath indicates the export path. The configuration format is as follows:

    <expath>E:\data</expath>

    The absolute path is supported. If no valid path is configured, storage information is exported to eSight installation directory\AppBase by default.

  4. After the configuration, restart the eSight process for the settings to take effect.

How to Set an Overcommitment Ratio

Question

eSight supports the customized setting of an overcommitment ratio.

Answer

You can set an overcommitment ratio as follows:

In configuration file eSight installation directory\AppBase\lib\base.common.lib\com.huawei.esight.it.storage.batchconfig.sdk-0.0.1-SNAPSHOT.jar\META-INF\oms\extension.x. Restart eSight for the settings to take effect, change the following parameter values:

thinlun ratio indicates an overcommitment ratio. Set the overcommitment ratio to 200%:

<extension point="esight.it.action.thinlun.overratio">

<thinlun ratio="200"></thinlun>

</extension>

How Can I Troubleshoot Report Data Collection Interruption

Question

Report data collection is interrupted after devices of high specifications are connected.

Answer

Report data collection is interrupted because the performance data collection tasks are beyond the capability of the system. Follow instructions in the following table to configure the performance data collection tasks of all connected devices.

Scenario

Number of Equivalent NEs

Collection Period

High configuration

  • CPU: octa-core, 2.5 GHz or higher
  • Memory: 32 GB or larger

Number of equivalent NEs ≥ 2000

1 hour or longer

500 ≤ Number of equivalent NEs ≤ 2000

30 minutes or longer

Number of equivalent NEs < 500

5 minutes or longer

Standard configuration

  • CPU: quad-core, 2.5 GHz or higher
  • Memory: 8 GB or larger

500 ≤ Number of equivalent NEs ≤ 1000

1 hour or longer

Number of equivalent NEs < 500

30 minutes or longer

NOTE:

The number of NEs includes the number of all connected storage devices and hosts.

How to Handle the Problem that Data of a Storage Device Is Not Properly Displayed

Question

In eSight, if the names of different measurement objects of a storage device are the same, data of the storage device is not properly displayed.

Answer

Currently, eSight does not support the scenario where different measurement objects of a storage device are the same. If the data of a storage device is not properly displayed, check that the name of each storage pool, LUN, front host port, hard disk, and controller of the storage device in DeviceManager is unique, and refresh the storage device in eSight.

What Can I Do If UDS Cannot Be Connected to eSight

Question

What can I do if UDS cannot be connected to eSight?

Answer

The possible cause is that port 28443 is not opened. You are advised to open port 28443 on the firewall.

How Can I Troubleshoot Storage Components (Storage Pools, File Systems, and LUNs) That Do Not Have Performance Data

Question

How can I troubleshoot storage components (storage pools, file systems, and LUNs) that do not have performance data?

Answer

Check whether the storage components have duplicate names (case-insensitive). If some storage components have duplicate names, change their names and refresh them on eSight.

Zone Information Cannot Be Viewed After Brocade Switches Are Added in eSight

Question

After Brocade switches are added in eSight, the zone information can be viewed in the switch management software but not in eSight.

Answer

Ensure that zones have been added to ZoneSet.

How Can I View the FOS Version of a Brocade Switch

Question

How can I view the FOS version of a Brocade switch?

Answer

Go to the CLI and run the telnet default port command to view the FOS version of a Brocade switch. The switch IP address uses the default port.

How Can I View the Port Link Status of Fibre Channel Switches and Alarms

Question

The performance indicators of eSight do not contain bit error rate. You can check the threshold alarm of signal loss to view the bit error rate of Fibre Channel switch ports.

Answer

  1. On the main menu, choose Performance > Monitoring Template.
  2. In the left navigation tree, choose Storage > FC Switches.
  3. Click Creat.
  4. On the page that is displayed, click Add Indicator.

  5. Select all performance indicators of Fibre Channel switches and set alarm thresholds.
  6. Remove and reinsert optical fibers and choose Fault > Current Alarms to view alarms.

  7. Check the device bit error rate.

NOTE:

When the bit error rate enc out increases, the signal loss alarm is reported. That is, this alarm is reported after you remove and reinsert optical fibers.

Brocade Switches Cannot Be Added to eSight

Question

eSight access the Brocade switch management software Brocade Network Advisor to manage Brocade switches. Before using eSight to manage Brocade switches, you need to connect eSight to Brocade Network Advisor. Apply for this software by submitting an order to Brocade or purchase it from Huawei.

Answer

You can download the trial version of Brocade Network Advisor from the Brocade official website. The software name is shown in following red square.

How Can I Configure the Alarm Trap for Brocade Switches

Question

To ensure that eSight can receive the alarms reported by a Brocade switch, you must manually add the eSight trap information to the Brocade switch. The following describes the procedure.

Answer

  1. Run the Web Tools of the Brocade switch and choose Manage > Switch Admin.
  2. In the Switch Administration dialog box that is displayed, click the SNMP tab. For SNMv2 alarm reporting, configure the SNMPv1 CommunityTrap Recipient list.

  3. Add the eSight IP address to the Recipient option in the SNMPv1 CommunityTrap Recipient list and click Apply.
    NOTE:

    If southbound and northbound services are separated for eSight , the eSight IP address here refers to the southbound IP address.

How Do I Do If eSight Fails to Discover Storage Devices or Hosts

This chapter describes the Windows host function. If the current version is V300R010C00SPC500, this function is not supported. If a patch version later than V300R010C00SPC500 is installed on V300R010C00SPC500, this function is not supported.

Question

When eSight discovers storage devices or hosts, the following failure messages are displayed.

  • If eSight fails to discover storage devices, the following messages may be displayed:
    • The user name or password is incorrect.
    • The device has been managed.
    • Failed to obtain the device information.
    • Exceeded the license limit.
  • If eSight fails to discover hosts, the following messages may be displayed:
    • Communication error. Check whether the network connection is normal.
    • The object already exists.
    • eSight fails to connect to the host. Possible causes are as follows:
  1. The operating system type is incorrect.
  2. The host denies the connection setup request.
  3. Other network problems exist.

Answer

If eSight fails to discover a storage device, perform the following operations to locate the fault:

  • Access a device through the REST protocol.
    • Check whether the storage device is supported by eSight.
    • Check whether the network between eSight and the storage device is connected and whether the management port on the storage device is enabled.
    • Check whether the user name and password are correct.
  • Access a device through the SMI-S protocol.
    • Check whether the storage device is supported by eSight.
    • Check whether the network between eSight and the storage device is connected and whether the SMI-S protocol port is enabled.
    • Check whether the SMI-S protocol parameters are correctly set for the storage device.

If eSight fails to discover a host, perform the following operations to locate the fault:

  • Access the host in agent mode.
    • Check whether the host is supported by eSight.
    • Check whether the network between eSight and the host is connected.
    • Check whether port 43156 is enabled on the host.
    • Check whether eSight and the agent are mapped.
    • Check whether the agent is run as the administrator.
  • Access the host in agentless mode.
    • Check whether the host is supported by eSight.
    • Check whether the network between eSight and the host is connected.
    • For a Linux host, check whether the root user can directly log in to the host.
    • If the host runs Windows, you need to preconfigure the WMI before the access.

What Can I Do If Performance Data of an FC Switch Cannot Be Properly Displayed

Question

A user has manually created a performance task in the FC switch port and selected performance counter. After the configuration is saved, no performance data is displayed.

Answer

Data of some performance indicators can be displayed after the following indicators are selected:

  1. To view data of Rate, you must select Rate, Receive Rate, Send Rate, Total Link Resets, Tx Link Resets, and Rx Link Resets.
  2. To view Send Rate, you must select Send Rate, Total Link Resets, Tx Link Resets, and Rx Link Resets.
  3. To view Receive Rate, you must select Receive Rate, Total Link Resets, Tx Link Resets, and Rx Link Resets.

How Do I Troubleshoot Invalid or Slow Reporting of Messages from Storage Device Components

Symptom

After the information about storage device components is changed, it takes a long time for the eSight components to update the information or the eSight components do not update the information at all.

Possible Causes

  • The communication between the management network ports of the eSight and storage device is abnormal.
  • The eSight default ports are shielded by a firewall.
  • The storage device report slowly.

Procedure

  • Cause 1: The communication between the management network ports of the eSight and storage device is abnormal.
    1. On the maintenance terminal, run the ping command on the CLI to check whether the network link can be pinged. The destination address is the management network IP address of the storage device.
    2. Reinsert or replace network cables. Then run the ping command on the CLI to check whether the network link can be pinged. The destination address is the management network IP address of the storage device.
      • If yes, go to d.
      • If no, go to c.
    3. Contact the network administrator to troubleshoot the network and go to d.
    4. On the eSight, check whether the storage device status is updated.
      • If yes, no further action is required.
      • If yes, go to Cause 2.
  • Cause 2: The NSM default ports are shielded by a firewall.
    1. Check whether a firewall is enabled on the maintenance terminal.
      • If yes, go to b.
      • If no, go to e.
    2. On the firewall management interface, check whether any of the NSM default ports have been added to the firewall exception list.

      The default NSM port numbers range from 8000 to 8090 and 8100 to 8190 and include 7890 and 8901.

      • If yes, go to c.
      • If no, go to e.
    3. Add any of the NSM default ports to the firewall exception list.
    4. On the eSight, check whether the storage device status is updated.
      • If yes, no further action is required.
      • If no, go to e.
    5. Go to the list of the devices of the specific type and click Refresh.
    6. After devices are refreshed, check whether the device component information is updated.
      • If yes, no further action is required.
      • If no, go to g.
    7. Keep the fault environment intact and contact technical support engineers.
  • Cause 3: The storage device report slowly.
    1. Check whether any of the storage device have finished the report.
      • If yes, no further action is required.
      • If no, go to b.
    2. Go to the list of the devices of the specific type and click Refresh, to synchronize the device information.

eSight Reports User Account Lockout When Discovering a Storage Device

Symptom

After discovering a device, the eSight reports "The user account has been locked. Please try later.".

Possible Causes

  1. An incorrect user name or password has been used to scan for devices.
  2. The device is discovered, but the user's password for logging in to the device is changed.

Procedure

  1. If an administrator attempts to discover a device using an incorrect user name or password, the device locks the user name for 15 minutes. In that case, the administrator has to wait 15 minutes until the device unlocks the user account. The administrator can then enter the correct user name and password to discover the device.
  2. A password change on the device also leads to user account lockout. In that case, choose Resource > Storage Subnet to find the device and clicks Settings > Protocol Parameters to change the user account, password, and SSL.

    NOTE:

    Then wait 15 minutes for the device to unlock the user account.

Why Is a Storage Device Offline After Being Discovered Based on the SNMP Protocol

Symptom

Storage devices and Fibre Channel switches are online after being discovered based on the SNMP protocol. However, after a period, those devices are displayed to be offline on the ISM. Actually, they do not go offline.

Possible Causes

The network speed is slow. As a result, pinging device times out every five minutes and devices are set to the offline state.

Procedure

  1. Choose Resource > Storage Subnet.
  2. Click the name of the device. The page showing details about the device is displayed.
  3. In the navigation tree, choose Settings > Protocol Parameters.
  4. Set Timeout to 10 seconds.
  5. Click Test.

    • If the test result is positive, click Apply. No further operation is required.
    • If the test result is negative, add 10 seconds to the value of Timeout and go to Step 5.

Report Diagrams Cannot Be Properly Displayed in SUSE

Symptom

Report diagrams are displayed as small squares, as shown in Figure 10-37.

Figure 10-37 Report diagrams are displayed as small squares

Possible Causes

Fonts required for the display of report diagrams are not installed in the SUSE operating system.

Procedure

  1. Check whether the available software source is configured for the system. If yes, go to Step 2. If no, go to Step 3.

    • For a SUSE 11 operating system, run the zypper ls and zypper refresh commands in sequence. Figure 10-38 shows the command outputs. If a message is displayed stating "All repositories have been refreshed", the available software source is configured. If no such a message is displayed, the software source is not configured.
      Figure 10-38 Checking the available software source of SUSE 11

    • For a SUSE 10 operating system, run the zypper sl and zypper refresh commands in sequence. Figure 10-39 shows the command outputs. If a message is displayed stating "All system sources have been refreshed", the available software source is configured. If no such a message is displayed, the software source is not configured.
      Figure 10-39 Checking the available software source of SUSE 10

  2. Install the local software source.

    • For a SUSE 11 operating system
      1. Upload the ISO file of SUSE Enterprise Linux 11.1 to the target server, as shown in Figure 10-40.
        Figure 10-40 Viewing the uploaded ISO file

      2. Go to the /etc/zypp/repos.d directory and update configuration file suse11.1.repo, as shown in Figure 10-41.
        [suse11.1] 
        name=suse11.1 
        enabled=1 
        autorefresh=0 
        baseurl=iso:///?iso=SLES-11-SP1-DVD-x86_64-GM-DVD1.iso&url=file:///src/ 
        path=/ 
        type=yast2 
        keeppackages=0     
        Figure 10-41 Configuration file
        NOTE:
        • Replace SLES-11-SP1-DVD-x86_64-GM-DVD1.iso&url and /src/ with the name of the ISO file name and ISO file path in baseurl=iso:///?iso=SLES-11-SP1-DVD-x86_64-GM-DVD1.iso&url=file:///src/.
        • If SUSE-Linux-Enterprise-Server-11-SP1 11.1.1-1.152.repo supplied with the system is invalid, you can delete it.
    • For a SUSE 10 operating system
      1. Mount the ISO to a local directory and run the mount –t iso9660 –o loop /home/iso/SLES-10-SP2-DVD-x86_64-GM-DVD1.iso /mnt/source/ command.
        Figure 10-42 Mount the ISO to a local directory

      2. Run the zypper sa "iso:///?iso=SLES-10-SP2-DVD-x86_64-GM-DVD1.iso&url=dir:///home/iso/" command to add the zypper source.
        Figure 10-43 Adding the zypper source

        NOTE:

        home/iso/ is the actual ISO file path.

  3. Install other languages.

    1. Use SSH to log in to the operating system.
    2. Run the yast command to configure language support.

      If the system supports a GUI-based interface, you can start yast2. The configuration steps using yast2 are the same as those in yast.

      1. Choose system > language, as shown in Figure 10-44.
        Figure 10-44 yast2 GUI-based interface

      2. Select the languages that you want to add from Secondary Languages.
        Figure 10-45 Selecting the languages that you want to add

      3. Click OK. The system automatically starts installing the language package.
        Figure 10-46 Installing the language package

      4. After the installation, choose Quit to exit yast.
        Figure 10-47 Installation succeeded

  4. After the installation is complete, restart the eSight service for the configuration to take effect.

Faults May Fail to Be Located if Logs Are Printed Too Quickly

Symptom

If more than 100 devices are managed and the system is running for over two weeks, some error logs are overwritten. As a result, faults may fail to be located.

Possible Causes

If a system manages a large number of devices, background tasks, such as device polling and component updating, generate a lot of logs.

Fault Diagnosis

By default, eSight prints error logs or logs of higher levels. Therefore, the system's reliability is not adversely affected by the log printing. This problem only affects the locating of component faults.

Procedure

  1. After this problem occurs, export all logs. For details about how to export logs, see the eSight Maintenance Guide.

Discovery of Devices by IP Address Segment Takes a Long Period of Time

Symptom

The discovery of devices by IP address segment takes a long period of time. For example, if the IP address segment contains 100 IP addresses and two discovery protocols are selected, it takes three hours to discover 10 or several more devices; if the IP address segment contains 254 IP addresses and one discovery protocol is selected, it takes one hour.

Possible Causes

The device discovery is implemented in single thread and serial mode. Therefore, if the number of devices that need to be discovered is large, the discovery takes a long period of time.

Fault Diagnosis

This problem adversely affects user experience.

Procedure

  1. Clicking Add Resource to add devices one by one can improve the user experience.
  2. If you use the Auto Discovery function, enter an IP address segment that contains a small number of IP addresses and use one discovery protocol.

No Data Is Unavailable in the Statistical Object Lists of Storage Devices

Symptom

Storage devices have historical performance statistics and they are normal. However, the statistics are not displayed in the statistical object lists of storage devices.

Choose Performance Management > Monitoring Settings.

In the left navigation tree, click and view statistical objects, as shown in Figure 10-48.

Figure 10-48 No statistics are displayed.

Possible Causes

Historical performance statistics of storage devices are read from performance files. The performance file generation requires a long period. If the collection period is short, the historical performance statistics cannot be displayed in a timely manner.

Fault Diagnosis

None.

Procedure

  1. None.

How Can I Troubleshoot the Unavailability of the Device Management Function Caused by Outdated JRE of Broswer

Symptom

On the eSight interface, the device management function is unavailable when you click Device Manager on broswer or later.

NOTE:

This problem does not occur if Internet Explorer 1.6.0_20 or later is used. For security purposes, you are advised to use JRE 1.7.0_51(7u51) or later.

Possible Causes

By default, broswer mask insecure JRE plug-ins. As a result, the device management function becomes unavailable after you click Device Manager.

Fault Diagnosis

If you are prompted with a message indicating that there is no proper plug-in when using the device management function, perform the following steps to check the version of the current JRE.

  1. Go to the operating system command-line mode and run java -version to view the JRE version.
  2. Open broswer and choose Add-ons Manager > Plugins to check whether JRE is loaded to broswer.

Procedure

  1. Log in to http://www.oracle.com and download JRE1.7.0_51(7u51).
  2. Install JRE on the client.
  3. Check whether JRE is activated.

    1. Go to the operating system command-line mode and run java –version to view the JRE version.
    2. Choose Start > Control Panel and click Java. The page for Java settings is displayed.
    3. Click the Java tab and View. On the User and System tab pages, select the newly installed JRE and select Enable.
    4. Open broswer and choose Add-ons Manager > Plugins to check whether JRE is activated.

What Can I Do If the Device Names on the eSight Are Different From Those on the Report Interface

Symptom

On the eSight, the name of a storage device is changed. When users check the storage device on the report interface, the name of the storage device on the report interface is different from that on the network management interface.

Possible Causes

After the storage device is discovered on the network management system (eSight), the report function does not synchronize the storage device. After the name of the storage device is modified on the network management interface, the name of the storage device on the report interface is different from that on the network management interface.

Fault Diagnosis

None

Procedure

  1. After the eSight discovers the storage device and the storage device is synchronized on the report interface, you can modify the name of the storage device.

What Can I Do If No Data Is Displayed When A Storage Report or Performance Statistics Is Checked

Symptom

When a storage report or performance statistics is checked on the network management interface, no data is displayed.

Possible Causes

  • The performance monitoring function of the storage device is not enabled.
  • The time gap between the storage device and eSight server exceeds seven days. As a result, the report fails to obtain performance data.

Fault Diagnosis

Rectify the fault based on the causes.

Procedure

  • The performance monitoring function of the storage device is not enabled.

    A Huawei storage device is used as an example. The operation procedure is as follows:

    1. On the menu bar, choose Resource > Storage Subnet.
    2. In the navigation tree, choose Storage > Storage Device. The Huawei Storage page is displayed.
    3. In the function pane, click Device Management.
    4. Enable the performance monitoring function, ensure that performance files of the storage device can be generated properly. For details, see the OceanStor DeviceManager Online Help.

      You can perform the following operations to enable the performance monitoring function for 5800 V3:

      1. On OceanStor DeviceManager, choose Settings > Performance Monitoring Settings.
      2. On the Performance Monitoring Settings page, select Parameter Settings.
      3. Select Save monitoring data on the device and set the performance monitoring status to Enabled.

  • The time gap between the storage device and eSight server exceeds seven days. As a result, the report fails to obtain performance data.
    1. Change the storage device time to make it consistent with the eSight server time. For details, see the OceanStor DeviceManager Online Help.

      You can perform the following operations to change the time of 5800 V3:

      1. On OceanStor DeviceManager, choose Settings > Basic Information.
      2. On the Basic Information page, select Device Time.
      3. Select Manual and click Modify.
      4. Set the system time to make it consistent with the eSight time.

Failed to Obtain Storage Device Details

Symptom

A storage device has been successfully added but its details cannot be obtained.

Possible Causes

  • An SQL Server database in eSight identifies all IQNs as case-insensitive. In this case, case-sensitive IQNs of iSCSI initiators on the storage device are identified as the same, so the unique initiator identifiers consisting of these case-insensitive IQNs conflict in the database. As a result, storage device details cannot be obtained.
  • Some IQNs of iSCSI host initiators are long and the length of unique initiator identifiers consisting of these IQNs exceeds 255 characters (the upper limit of string length in eSight). As a result, the unique initiator identifiers cannot be stored into the database and therefore storage device details cannot be obtained.

Procedure

  • Cause 1: An SQL Server database in eSight identifies all IQNs as case-insensitive. In this case, case-sensitive IQNs of iSCSI initiators on the storage device are identified as the same, so the unique initiator identifiers consisting of these case-insensitive IQNs conflict in the database. As a result, storage device details cannot be obtained.
    1. Check whether any IQNs of the iSCSI initiators are the same in the storage device when being identified in case-insensitive way.
    2. Modify the initiator IQNs and ensure that the IQNs are different when being identified in case-insensitive way.
    3. Rediscover or refresh the storage device and check whether its details can be obtained.
      • If yes, no further action is required.
      • If no, go to 4.
    4. Collect related information and contact technical support engineers for further handling.
  • Cause 2: Some IQNs of iSCSI host initiators are long and the length of unique initiator identifiers consisting of these IQNs exceeds 255 characters (the upper limit of string length in eSight). As a result, the unique initiator identifiers cannot be stored into the database and therefore storage device details cannot be obtained.
    1. Check whether the length of any IQN of an iSCSI initiator exceeds 190 characters.
      • If yes, go to 2.
      • If no, go to 4.
    2. Modify the initiator IQN and ensure that the IQN length is smaller than 190 characters.
    3. Rediscover or refresh the storage device and check whether its details can be obtained.
      • If yes, no further action is required.
      • If no, go to 4.
    4. Collect related information and contact technical support engineers for further handling.

Disk Space Is Insufficient After the Report Component Is Installed

Symptom

After the report component is installed, space of the disk used by eSight is consumed quickly. The disk space may be used up.

Possible Causes

  • The configured disk capacity is small.
  • Many devices are connected, and a large amount of report data is generated.

Procedure

  • Cause 1: The configured disk capacity is small.
    1. Expand the capacity of the disk used by eSight.
  • Cause 2: Many devices are connected.
    1. Expand the capacity of the disk used by eSight and reserve sufficient space for the report component based on the network element (NE) scale.

      NE Scale

      Memory

      Disk

      0 to 500

      2 GB

      50 GB

      500 to 2000

      4 GB

      200 GB

      2000 to 5000

      8 GB

      500 GB

      5000 to 20000

      16 GB

      2000 GB

CPU Usage of Oracle Processes Is High

Symptom

In a SUSE+Oracle environment, after devices are connected, CPU usage of multiple Oracle processes is high or even reaches 100%.

Possible Causes

In a big data environment, the amount of Oracle database query data is large. If the configured sga capacity is small, the data buffer is too small to be sufficient for queries. As a result, query data has to wait.

Procedure

  1. Connect to the Oracle database.
  2. Modify sga configurations based on the memory configurations. It is recommended that the sga capacity be 50% of the physical memory.

    For example, run the following command to set the sga capacity to 20 GB:

    alter system set sga_max_size=20480M scope=spfile;

    alter system set sga_target=20480M scope=spfile;

  3. Run the following command to restart the Oracle database for the configurations to take effect:

    shutdown immediate;

    startup;

What Can I Do If a Device Cannot Be Detected or Its Information Cannot Be Obtained

Question

On eSight, a device cannot be detected or its information cannot be obtained by user admin or root.

Answer

  1. On the login page of storage device management software such as DeviceManager or ISM, check whether user admin or user root is locked.
  2. Create an administrator account used for connecting the storage device to eSight. In this section, DeviceManager is used to show how to create an administrator account. For details about how to create the account on other device management software, see related product documentations.
    NOTE:

    Because accounts admin and root are prone to be attacked and locked due to misoperations, you need to create an administrator account on the storage device dedicated to connecting to eSight and keep the account safe.

    1. Log in to DeviceManager.
    2. Click Settings.
    3. Click Permission Settings.
    4. Click User Management.
    5. Click Add to add an administrator account. You are advised to set the account name to eSignt_xx.
  3. Use the created account on the device to communicate with eSight.

How Do I Do If Device Alarms Are Not Reported Because eSight Does Not Detect the Reset Operation Event of the Huawei Enterprise Storage Controller

Question

After the controller of the OcenStor V3 or OcenStor V5 devices is reset, no alarm is reported to eSight. As a result, some storage devices are disconnected from eSight.

Answer

The reset event of the controller of OceanStor V3 and OceanStor V5 devices is completed in a short period of time. eSight delays 2 minutes to collect alarms. As a result, alarms cannot be reported. To solve this problem, perform the following operations:

  1. Log in to the DeviceManager and choose Settings > Alarm Settings. The Event Notification Management tab page is displayed.
  2. Search for the event ID 0x100F00CF0040. Select Trap Notification.

    Figure 10-49 Setting the event notification

JDK Parameter Setting Tool

This command line tool can dynamically decrypt MD5.

Format

  • Linux operating system: it_common_MD5config.sh
  • Windows operating system: it_common_MD5config.bat

Path

Linux operating system: eSight installation directory/AppBase/tools/MD5Config/it_common_MD5config.sh

Windows operating system: eSight installation directory/AppBase/tools/MD5Config/it_common_MD5config.bat

Restart eSight for the configuration to take effect.

Prerequisites

None

Example

Linux Operating System

  1. Log in to the operating system as the ossuser user and run the following command:
    NOTE:
    • In a two-node cluster, you need to perform this operation only on the active server.
    • In the Veritas HA system scenario, switch to the root user to perform the operation.

    cd eSight installation directory/AppBase/tools/MD5Config/

  2. Run the ./it_common_MD5config.sh command.
  3. Restart the eSight process.
Windows Operating System
  1. Run the it_common_MD5config.bat command as the administrator user.
  2. Restart the eSight process.

Configuring a Threshold Alarm

Threshold alarms of a device need to be checked during live network O&M. Storage network analysis enables you to intuitively view threshold alarms of devices on topologies, facilitating troubleshooting.

Context

When viewing threshold alarms, you can set threshold alarms for devices based on site requirements to facilitate specific analysis.

Procedure

  1. Choose Performance > Monitoring Settings. The Monitoring Settings page is displayed.
  2. In the navigation tree, select the device type for which you want to set a threshold alarm.

    The preset collection task template is displayed on the right.

  3. Click to edit the preset template.
  4. Set indicator thresholds.
  5. Wait for one collection period, go to the storage network analysis page, and view the threshold alarms.

How Do I Configure Users to Access the Storage System in SSO Mode on eSight

On eSight, users can directly access the storage system configured with the same CAS server in SSO mode.

Prerequisites

  • You have obtained the IP address of the storage device.
  • The device has been configured. For details, see the chapter about CAS server configuration in the device document.

Context

  • Single Sign-On (SSO) is a part of identity management. The SSO allows a user to access protected resources of different applications on the same server after the user logs in to any of the applications. In other words, after passing the security verification of an application, the user does not need to log in to other applications for verification when accessing protected resources of these applications.
  • Central Authentication Service (CAS) is a web page SSO protocol. Through this protocol, the user only needs to provide the credential (such as the user name and password) once to access multiple applications.

Procedure

  1. Log in to eSight and add Huawei storage devices. For details, see Adding a Single Huawei Storage Device.
  2. Add IP addresses to the whitelist.

    1. Stop eSight. For details, see "Common Operations and Configuration > Common eSight Operations > Starting and Stopping the eSight Server" in the eSight Maintenance Guide.
    2. Log in to eSight.
      • In the Windows operating system, log in to the eSight as the Administrator user.
      • In the Linux operating system, log in to eSight as the ossuser user.
      • In a two-node cluster, log in to the active server as the ossuser user.
    3. Open the eSight installation directory/AppBase/etc/oms.sso/sso.xml file.
    4. Add client-trusted-ip. Use commas (,) to separate multiple IP addresses.

      The IP address refers to the IP address of the storage device. The following is an example:

      <param name="client-trusted-ip">10.10.10.70,10.10.10.80</param>

  3. Set the SSO switch.

    1. Open the eSight installation directory/AppBase/etc/esight.storage/config.xml file.
    2. Ensure that devicemanager.ssologin is set to true.
      <param name="devicemanager.ssologin">true</param>
      NOTE:

      If devicemanager.ssologin is set to false, you can access the DeviceManager without login.

    3. Restart eSight. For details, see "Common Operations and Configuration > Common eSight Operations > Starting and Stopping the eSight Server" in the eSight Maintenance Guide.

  4. Obtain the SSO certificate file ca.crt of the CAS server from eSight installation directory/AppBase/etc/certificate/application/ca.
  5. Import the obtained SSO certificate to the storage system.

    1. Enter https://XXX.XXX.XXX.XXX:8088 in the address box of a browser, press Enter, and log in to the DeviceManager.
      NOTE:

      In the information, XXX.XXX.XXX.XXX indicates the IP address of the management network port of a storage system.

    2. Choose Settings > Storage Settings > Value-added Service Settings > Credential Management.
    3. In the Certificate Management area, select the certificate and click Import and Activate.

      The Import and Activate dialog box is displayed.

    4. Set certificate parameters. Table 10-43 describes related parameters.
      Table 10-43 Parameters for adding a certificate

      Parameter

      Description

      CA Certificate File

      SSO certificate file.

    5. Click OK.

      A dialog box is displayed, indicating that risks exist.

    6. Select "I have read and understand the consequences associated with performing this operation" in the dialog box and click OK.

      The Success dialog box is displayed.

    7. Click OK.

      The imported certificate is displayed in the certificate list.

  6. Configure the CAS server on the storage device.

    1. Log in to the DeviceManager.
    2. Choose Settings > Permission Settings > CAS Server Settings.
    3. Configure the CAS server.
      1. Select Enable.
      2. Enter the address and port number of the CAS server.
        NOTE:
        • The IP address of the CAS server is the IP address of the eSight server.
          • If eSight is deployed in the multi-subnet management scenario, use the eSight server IP address on the same network segment as that of the storage system.
          • If eSight is deployed in the southbound and northbound isolation scenario, use the southbound IP address.
        • The default port number is 31942.
      3. Click Save.

        The Success dialog box is displayed, indicating that the operation is successful.

      4. Click OK.
      5. (Optional) Click Test to check whether the configured CAS server is available.

  7. Go to the SSO page.

    1. Log in to eSight.
    2. Choose Resource > Storage Subnet from the menu bar.
    3. In the navigation tree, choose Storage > Storage Device.
    4. Click in the Operation column in the information display area to go to the corresponding SSO page.

Translation
Download
Updated: 2019-09-12

Document ID: EDOC1100044378

Views: 82348

Downloads: 403

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