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


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


Configuration Guide - Device Management

S7700 and S9700 V200R013C00

This document describes the configurations of Device Management, including device status query, hardware management, CSS, SVF, PoE, OPS, OIDS, energy-saving management, information center, fault management, NTP, synchronous ethernet, PTP.
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).
Understanding OIDS

Understanding OIDS

The OIDS function consists of the OIDS monitoring function and the OIDS diagnosis function. The OIDS monitoring function provides information about the switch running status, enabling you to quickly detect service faults. The OIDS diagnosis function enables you to quickly locate and rectify faults.

OIDS Data Collection Dimensions

After the OIDS monitoring function is enabled, the switch periodically collects and saves performance indicator data based on diagnosis types, diagnosis objects, and diagnosis object attributes. OIDS defines different diagnosis types, as shown in Figure 7-1. Each diagnosis type contains different diagnosis objects, and each diagnosis object contains different diagnosis object attributes.

Figure 7-1  OIDS data collection dimensions

For example, in Table 7-1, the diagnosis type MCAST contains three diagnosis objects: IPMC, IPMC_VLAN, and Hash_Conflict. The diagnosis object IPMC contains a diagnosis object attribute IPMC_Usage, the diagnosis object IPMC_VLAN contains a diagnosis object attribute IPMC_VLAN_Usage, and the diagnosis object Hash_Conflict contains a diagnosis object attribute Occur_Times. IPMC_Usage indicates the usage of IPMC entries on an LPU, IPMC_VLAN_Usage indicates the usage of IPMC_VLAN entries on an LPU, and Occur_Times indicates the number of hash collisions during entry delivery.

Table 7-1  MCAST diagnosis type











The switch currently supports the following diagnosis types: ACL, ARP, CPU, CPU-CHAN, DHCPv4, DHCPv6, FIBv4, FIBv6, Flash, L3table, MAC, MCAST, Memory, MPLS, NAC, ND, NHP, Port, and TEMP. For details about the diagnosis objects and diagnosis object attributes supported by each diagnosis type, see Appendix 1: OIDS Monitoring and Diagnosis Items Supported by the Switch.

OIDS Process

Figure 7-2 shows the OIDS process after the OIDS monitoring and diagnosis functions are enabled:
  1. The switch periodically collects diagnosis object attribute data based on diagnosis types, diagnosis objects, and diagnosis object attributes and records the data in database files.

  2. The OIDS module sends key performance indicator (KPI) data to service modules based on the collected diagnosis object attribute data. Service modules then determine whether the data is within the normal range.

    KPIs relate to the running status of the switch at any given time. Currently, all diagnosis object attributes on the switch are KPIs.

  3. Service modules compare the KPI data with the defined threshold range to determine whether to generate an event. For details about the events supported by each diagnosis type, see Appendix 2: OIDS Events Supported by the Switch.

    • If a service module generates an event, it sends the event information to the OIDS module, and the process goes to step 4.
    • If no service module generates any event, service modules perform no further operations and the process ends.
  4. The OIDS module records the event in the database and determines whether to trigger OIDS diagnosis.

    • If OIDS diagnosis is triggered, the OIDS module specifies a service module to perform diagnosis, and the process goes to step 5.
    • If OIDS diagnosis is not triggered, the OIDS module performs no further operations and the process ends.
  5. The service module performs OIDS diagnosis and sends the diagnosis result to the OIDS module.

  6. The OIDS module records the diagnosis result in the database.

Figure 7-2  OIDS process

OIDS Database File Storage

After the OIDS function is enabled, the switch saves the collected data and fault diagnosis results to SQLite database files named oids.db in the flash:/oids folder on the active MPU. When you query OIDS data, the switch reads the OIDS database files stored on the active MPU. For a dual-MPU or cluster switch, the switch cannot read OIDS database files on the standby MPU. This means that, if an active/standby MPU switchover occurs, you cannot query the OIDS database files on the current standby MPU. In this case, save the OIDS database files on the standby MPU to the flash:/oids/gather folder on the active MPU. You can then perform queries as normal.

OIDS will age the database files in the flash:/oids folder (excluding the database files in the flash:/oids/gather folder). The aged files are renamed YYYY-MM-DD.HH-MM-SS_oids.db, for example, 2018-03-27.04-26-57_oids.db. A maximum of six database files can be saved in the flash:/oids folder. Each database file occupies about 20 MB to 25 MB storage space. When saving data, OIDS checks the remaining space of the flash memory. If the remaining space is less than 30 MB, OIDS deletes the oldest database files to make space for the new ones.

Association Between OIDS and OPS

The devices that support both OIDS and OPS support association between OIDS and OPS. The implementation of association between OIDS and OPS is different from that of traditional OIDS. When OIDS is associated with OPS, the OIDS events supported by the device can be generated by the OIDS monitoring function or OIDS filter. The OIDS events to be monitored can be defined using the OPS event subscription function. For details about the OIDS events supported by the device, meaning and causes of the events, see Appendix 2: OIDS Events Supported by the Switch. The OPS action execution module performs a corresponding action on the monitored OIDS event to implement a user-defined function. In association between OIDS and OPS, the OPS function is implemented based on the OPS APIs (including OIDS event subscription, writing back event execution result to OIDS, and obtaining environment variables) supported by association between OIDS and OPS. The events to be monitored and actions to be executed can be defined using Python scripts based on OPS APIs Supported by a Device.

Updated: 2019-04-20

Document ID: EDOC1100065738

Views: 40987

Downloads: 37

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