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

ME60 V800R010C10SPC500 Feature Description - System Management 01

This is ME60 V800R010C10SPC500 Feature Description - System Management
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).
SAID for Ping

SAID for Ping

Fault Cause

The failure to ping through a directly connected device often occurs on the network, causing services to be interrupted for a long time and fail to automatically recover. The ping process involves various IP forwarding phases. A ping failure may be caused by a hardware entry error, board fault, or subcard fault on the local device or a fault on an intermediate device or the peer device. Therefore, it is difficult to locate or demarcate the specific fault.

Definition

The ping service node is a specific SAID service node. This node performs link-heartbeat loopback detection to detect service faults, diagnoses each ping forwarding phase to locate or demarcate the fault, and takes corresponding recovery actions.

Principles

For details about the SAID framework and principles, see Basic SAID Functions. The ping service node undergoes four phases (fault detection, fault diagnosis, fault recovery, and service recovery determination) to implement automatic device diagnosis, fault information collection, and service recovery.

  • Fault detection

    The ping service node performs link-heartbeat loopback detection to detect service faults. Link-heartbeat loopback detection is classified as packet modification detection or packet loss detection.
    • Packet modification detection is to check whether the content of received heartbeat packets is the same as the content of sent heartbeat packets.

    • Packet loss detection is to check whether the difference between the number of received heartbeat packets and the number of sent heartbeat packets is within the permitted range.

    After detecting packet modification or loss, the SAID triggers a message and sends it to instruct the ping service node to diagnose the fault.
  • Fault diagnosis

    After receiving the triggered message in the fault detection state, the ping service node enters the diagnosis state for fault diagnosis.

    In the fault diagnosis state, the ping service node performs interface loopback detection to determine whether the local device is faulty. If yes, the node enters the fault recovery state. If not, the node generates an alarm (only a packet modification alarm) and returns to the fault detection state.

  • Fault recovery

    If a loopback detection fault occurs, the ping service node determines whether a counting error occurs on the associated subcard.
    • If a counting error occurs, the ping service node resets the subcard for service recovery. Then, the node enters the service recovery determination state and performs link-heartbeat loopback detection to determine whether services recover. If services recover, the node returns to the fault detection state. If services do not recover, the node returns to the fault recovery state and takes a secondary recovery action. (For a subcard reset, the secondary recovery action is board reset.)

    • If no counting error occurs, the ping service node resets the involved board for service recovery. After the board starts, the node enters the service recovery determination state and performs link-heartbeat loopback detection to determine whether services recover. If services recover, the node returns to the fault detection state. If services do not recover, the node remains in the service recovery determination state and periodically performs link-heartbeat loopback detection until services recover.

  • Service recovery determination

    After fault recovery is complete, the ping service node uses the fault packet template to send diagnostic packets. If a fault still exists, the node generates an alarm. If no fault exists, the node instructs the link heartbeat to return to the initiate state, and the node itself returns to the fault detection state.

Translation
Download
Updated: 2019-01-04

Document ID: EDOC1100059466

Views: 11647

Downloads: 7

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