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

Configuration Guide - Network Management and Monitoring

CloudEngine 12800 and 12800E V200R005C10

This document describes the configurations of Network Management and Monitoring, including SNMP, RMON, LLDP, NQA, Service Diagnosis, Mirroring, Packet Capture, sFlow, and NETCONF.
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).
Notification Capabilities

Notification Capabilities

Notification 1.0

The device uses NETCONF to report alarms or events to the NMS through notifications, facilitating device management by the NMS. You can perform the <create-subscription> operation to subscribe to device alarms or events. If the <rpc-reply> element returned by the device contains an <ok> element, the <create-subscription> operation is successful, and the device will proactively report its alarms or events through NETCONF to the NMS.

Capability ID

<capability>urn:ietf:params:netconf:capability:notification:1.0</capability>

1. Alarms or events can be subscribed to in either of the following modes: long-term subscription and subscription within a specified period.

  • Long-term subscription: After the subscription is successful, if the <startTime> element is specified in the subscription packet, the device sends the historical alarms or events to the NMS and then sends a <replayComplete> packet to notify the NMS that replay is complete. If a new alarm or events is generated on the device, the device also sends the alarm or events to the NMS. If the <startTime> element is not specified in the subscription packet, the device sends all generated alarms or events to the NMS. After a NETCONF session is terminated, the subscription is automatically canceled.

  • Subscription within a specified period: After the subscription is successful, the device sends the alarms or events that are generated from the start time to the end time and meet the filtering conditions to the NMS. Because the <startTime> element is specified in the subscription packet, the device sends historical alarms or events to the NMS and then sends a <replayComplete> packet to notify the NMS that the replay is complete. When the specified <stopTime> arrives, the NETCONF module sends a <notificationComplete> packet to notify the NMS that the subscription is terminated.

Historical alarms or events refer to alarms or events generated from the <startTime> specified in the subscription packet to when the user performs the subscription operation.

The format of the subscription packet sent by the device to the NMS is as follows. If <stopTime> is not specified, the subscription is a long-term one. If both <startTime> and <stopTime> are specified, the subscription is within a specified period.

Reply example

<rpc message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
  <create-subscription xmlns="urn:ietf:params:xml:ns:netconf:notification:1.0">
    <stream>NETCONF</stream>
    <filter type="subtree">
       <hwCPUUtilizationRisingAlarm xmlns="http://www.huawei.com/netconf/vrp/huawei-sem" />
    </filter>
    <startTime>2016-10-20T14:50:00Z</startTime>
    <stopTime>2016-10-23T06:22:04Z</stopTime>
  </create-subscription>
</rpc>

Response example

<rpc-reply message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
  <ok/>
</rpc-reply>
Table 3-11 Elements

Element

Description

Value Range

Mandatory

Restriction

stream

Event flow type

The value is an enumerated type and case-sensitive. The value is NETCONF, indicating that the NETCONF notification mechanism is used to report alarms or events.

N

N/A

filter

Alarm or event filter

The value is a string of characters in the format of < alarm name xmlns=name space of the alarm name/> or < event name xmlns=name space of the event name/>.

N

If no filter is specified, all alarms or events that can be reported through notifications are subscribed to.

startTime

Start time

The value is in the time format.

N

The start time must be earlier than the time when the subscription operation is performed.

stopTime

End time

The value is in the time format.

N

The end time must be later than the start time.

2. After the subscription is successful, the device encapsulates the alarm and event information into notification messages and sends them to the NMS. The format of a notification message is as follows:

<notification xmlns="urn:ietf:params:xml:ns:netconf:notification:1.0">
  <eventTime>2016-11-26T13:51:00Z</eventTime>
  <hwCPUUtilizationResume xmlns="http://www.huawei.com/netconf/vrp/huawei-sem">
  <TrapSeverity>0</TrapSeverity>
  <ProbableCause>0</ProbableCause>
  <EventType>0</EventType>
  <PhysicalIndex>0</PhysicalIndex>
  <PhysicalName>SimulateStringData</PhysicalName>
  <RelativeResource>SimulateStringData</RelativeResource>
  <UsageType>0</UsageType>
  <SubIndex>0</SubIndex>
  <CpuUsage>0</CpuUsage>
  <Unit>0</Unit>
  <CpuUsageThreshold>0</CpuUsageThreshold>
  </hwCPUUtilizationResume>
</notification>
3. After alarms or events are reported to the NMS, the NETCONF module sends a subscription completion packet to the NMS.
  • After historical alarms or events are reported to the NMS, the NETCONF module sends a replayComplete packet to the NMS. The format of the replayComplete packet is as follows:

    <notification xmlns="urn:ietf:params:xml:ns:netconf:notification:1.0">
      <eventTime>2016-11-29T11:57:15Z</eventTime>
      <replayComplete xmlns="urn:ietf:params:xml:ns:netconf:notification:1.0" />
    </notification>
  • When the <stopTime> specified in the subscription packet arrives, the NETCONF module sends a notification message to notify the NMS that the subscription is terminated. The format of the notificationComplete packet is as follows:

    <notification xmlns="urn:ietf:params:xml:ns:netconf:notification:1.0">
      <eventTime>2016-11-29T11:57:25Z</eventTime>
      <notificationComplete xmlns="urn:ietf:params:xml:ns:netconf:notification:1.0" />
    </notification>
    Table 3-12 Elements

    Element

    Description

    Value Range

    Mandatory

    Restriction

    replayComplete

    After historical alarms or events are reported to the NMS, the NETCONF module sends a replayComplete packet to the NMS.

    N/A

    N

    N/A

    notificationComplete

    When the <stopTime> specified in the subscription packet arrives, the NETCONF module sends a notificationComplete packet to notify the NMS that the subscription is terminated.

    N/A

    N

    N/A

Notification 2.0

Notification 1.0 cannot meet flexibility requirements. To modify a subscription, you need to disable the connection and start a new subscription connection. Notification 2.0 optimized the subscription mechanism. It supports subscription modification, deletion, and ending, configuration-based subscription, subscription query, and subscription information authorization on the NACM.

Capability ID

<capability>urn:ietf:params:netconf:capability:notification:2.0</capability>
Notification 2.0 supports the following subscription operations:
  • <establish-subcription>: creating a dynamic subscription
  • <modify-subscription>: modifying a dynamic subscription
  • <delete-subscription>: deleting a dynamic subscription
  • <kill-subscription>: ending a dynamic subscription
Create a subscription and allow specified alarms to be reported.
  • RPC request
    <rpc message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
     <establish-subcription xmlns="urn:ietf:params:xml:ns:netconf:notification:2.0">
      <filter type="subtree">
       <hwCPUUtilizationRisingAlarm xmlns="http://www.huawei.com/netconf/vrp/huawei-sem" />
       <hwCPUUtilizationResume xmlns="http://www.huawei.com/netconf/vrp/huawei-sem" />
       <hwStorageUtilizationRisingAlarm xmlns="http://www.huawei.com/netconf/vrp/huawei-sem" />
      </filter>
     </establish-subcription>
    </rpc>
  • RPC reply
    <rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
      <subscription-result xmlns="urn:ietf:params:xml:ns:yang:ietf-subscribed-notifications">ok</subscription-result>
      <identifier xmlns="urn:ietf:params:xml:ns:yang:ietf-subscribed-notifications">1</identifier>
    </rpc-reply>
Notifications on the following subscription status changes are supported.
  • subscription-terminated: A subscription is terminated.
  • subscription-suspended: A subscription is suspended.
  • subscription-resumed: A subscription wakes up.
  • notification-complete: A notification is sent.
  • replay-complete: Replay is complete.
A subscription is suspended, and a notification message is reported.
<notification xmlns="urn:ietf:params:xml:ns:netconf:notification:2.0">
  <subscription-suspended xmlns="urn:ietf:params:xml:ns:netconf:notification:2.0">
    <identifier>52</identifier>
    <error-id>3</error-id>
    <filter-failure>Lack of resource</filter-failure>
  </subscription-suspended>
</notification>
Translation
Download
Updated: 2019-04-20

Document ID: EDOC1100075344

Views: 23199

Downloads: 23

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