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.


Alarm Handling

AR100, AR120, AR160, AR1200, AR2200, AR3200, and AR3600 V300R003

This document provides the trap description, attributes, parameters, impact on the system, possible causes, procedures, and references. This document provides a complete set of traps, through which intended readers are kept of the running status of the device so as to locate faults.

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).
PKI_1. hwPKIGetCrlFailScep

PKI_1. hwPKIGetCrlFailScep


PKI/4/PKIGETCRLFAILSCEP: OID [OID] get crl unsuccessfully with SCEP. (CrlUrl=[CrlUrl])

Failed to obtain the CRL using SCEP.


Alarm ID Alarm Severity Alarm Type Warning communicationsAlarm


Name Meaning
OID Indicates the MIB object ID of the alarm.
CrlUrl CRL distribution point (CDP) URL

Impact on the System

The local certificate may be unavailable.

Possible Causes

The device failed to exchange with the CRL distribution point (CDP).


  1. Run the ping command to check whether a reachable route exists between the device and CA server.

    • If so, go to step 2.
    • If not, check the route and link to ensure that there is a reachable route between the device and CA server.

  2. Check whether PKI configurations of the device and CA server are correct, including the CRL URL, CA name, challenge password used in SCEP certificate application, and CA certificate digital fingerprint.

    • If not, ensure that PKI configurations are correct.
    • If so, go to step 3.

  3. Collect alarm and configuration information, and contact technical support personnel.
Updated: 2019-03-06

Document ID: EDOC1100041475

Views: 100997

Downloads: 61

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Previous Next