|
|
1 |
(% class="row" %) |
|
|
2 |
((( |
|
|
3 |
(% class="col-xs-12 col-sm-7 test-report-content" %) |
|
|
4 |
((( |
|
|
5 |
---- |
|
|
6 |
|
|
|
7 |
NETCONF provides a mechanism for devices to send event notifications to a subscriber, allowing monitoring changes in network state or configuration. One test run has been executed between H3C AD-WAN as a NETCONF client and Ribbon NPT-2100 as a NETCONF server. The H3C NETCONF client subscribed to the configuration/alarm/event of the Ribbon NETCONF server. We then validated the correct subscription by following the received notification, where multiple notifications, including some triggered by the IGP (IS-IS), were observed. |
|
|
8 |
The test steps are as follows |
|
|
9 |
*. Establish and verify the NETCONF session between the NETCONF server and client |
|
|
10 |
*. Subscribe from the NETCONF client to the server's event stream |
|
|
11 |
*. Monitor the NETCONF client for incoming notifications from the server |
|
|
12 |
|
|
|
13 |
[[Figure 68: NETCONF Event Notifications' Subscription>>image:433488189341040641_SDN-10-1-V1.png||alt="Figure 68" width="550"]] |
|
|
14 |
|
|
|
15 |
(% id="prev-next-links" %) |
|
|
16 |
|[[< Previous>>doc:Multipath Information Signaling]]|[[Next ~>>>doc:NETCONF L2L3 VPN Services Provisioning]] |
|
|
17 |
))) |
|
|
18 |
|
|
|
19 |
(% class="col-xs-12 col-sm-5 test-report-sidebar" %) |
|
|
20 |
((( |
|
|
21 |
{{box}} |
|
|
22 |
{{include reference="Main.Multi-Vendor MPLS & SDN Interoperability Test Report 2025.Sidebar Nav"/}} |
|
|
23 |
{{/box}} |
|
|
24 |
))) |
|
|
25 |
))) |
