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

NETCONF YANG API Reference

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

NETCONF YANG API Reference
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).
NETCONF Notifications

NETCONF Notifications

The NETCONF protocol defines an event notification mechanism to allow the NETCONF server to notify the client of a specific event. The following description is referenced from RFC 5277. For details, see the RFC recommendations.

This memo defines a mechanism whereby the NETCONF client indicates interest in receiving event notifications from a NETCONF server by creating a subscription to receive event notifications.  The NETCONF server replies to indicate whether the subscription request was successful and, if it was successful, begins sending the event notifications to the NETCONF client as the events occur within the system. These event notifications will continue to be sent until either the NETCONF session is terminated or the subscription terminates for some other reason. The event notification subscription allows a number of options to enable the NETCONF client to specify which events are of interest. These are specified when the subscription is created.  Note that a subscription cannot be modified once created.

create-subscription

The server must send create-subscription messages so that the client can receive notification messages by the server. An example is as follows:

<netconf:rpc message-id="101" xmlns:netconf="urn:ietf:params:xml:ns:netconf:base:1.0"> 
 <create-subscription xmlns="urn:ietf:params:xml:ns:netconf:notification:1.0"> 
 </create-subscription>  
</netconf:rpc>

A simple subscription message is created, and no notification message is filtered. For more information, see RFC 5277.

Supported Notification Messages

Table 2-4 lists supported notification messages. For message formats, see YANG files.

Table 2-4 Notification list

No.

Notification Event Name

YANG File

Description

1

interface-event

huawei-interfaces.yang

The interface status changes.

2

alarm-notification

ietf-alarms.yang

Alarm information.

Translation
Download
Updated: 2019-03-06

Document ID: EDOC1100022096

Views: 8519

Downloads: 69

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