{"id":176,"date":"2026-10-15T00:00:00","date_gmt":"2026-10-14T20:30:00","guid":{"rendered":"https:\/\/www.anynet.ir\/blog\/%d9%be%db%8c%d8%a7%d8%af%d9%87%d8%b3%d8%a7%d8%b2%db%8c-%d8%a7%d8%b9%d9%84%d8%a7%d9%86%d9%87%d8%a7%db%8c-%d8%b1%d9%88%db%8c%d8%af%d8%a7%d8%af-event-notifications-%d8%af%d8%b1-cisco-crosswork-network-2\/"},"modified":"2026-10-18T18:16:16","modified_gmt":"2026-10-18T14:46:16","slug":"%d9%be%db%8c%d8%a7%d8%af%d9%87%d8%b3%d8%a7%d8%b2%db%8c-%d8%a7%d8%b9%d9%84%d8%a7%d9%86%d9%87%d8%a7%db%8c-%d8%b1%d9%88%db%8c%d8%af%d8%a7%d8%af-event-notifications-%d8%af%d8%b1-cisco-crosswork-network-2","status":"publish","type":"post","link":"https:\/\/www.anynet.ir\/blog\/en\/%d9%be%db%8c%d8%a7%d8%af%d9%87%d8%b3%d8%a7%d8%b2%db%8c-%d8%a7%d8%b9%d9%84%d8%a7%d9%86%d9%87%d8%a7%db%8c-%d8%b1%d9%88%db%8c%d8%af%d8%a7%d8%af-event-notifications-%d8%af%d8%b1-cisco-crosswork-network-2\/","title":{"rendered":"Implementing Event Notifications in Crosswork Network Controller"},"content":{"rendered":"<div><\/div>\n<div>\n<div><\/div>\n<\/div>\n<div>\n<div>\n<div>\n<p><strong style=\"color: rgb(26, 26, 26)\">Crosswork Network Controller<\/strong> provides a wide range of notification capabilities to integrate with external OSS systems providing those latest with real-time updates on alarms, topology changes, service degradation, and other events across different functional areas of the product.<\/p>\n<p>This article only focuses on the Element Management Function area (which ties to the Essential license tier or the product)<br \/>\nIn this area, Crosswork Network Controller supports the following notification types and protocols:<\/p>\n<ul>\n<li><strong style=\"color: rgb(26, 26, 26)\">RESTCONF<\/strong>: Alarms, inventory, and topology<sup>*1<\/sup><\/li>\n<li><strong style=\"color: rgb(26, 26, 26)\">Kafka<\/strong>: Alarms, Inventory, Performance, and Audits<\/li>\n<li><strong style=\"color: rgb(26, 26, 26)\">TRAP<\/strong>: Alarms only<\/li>\n<li><strong style=\"color: rgb(26, 26, 26)\">SYSLOG<\/strong>: Alarms only<\/li>\n<\/ul>\n<p>This tutorial provides a high-level overview of how these notifications work and how to use them without going into execution details. It assumes reader is already experienced with basic Crosswork Network Controller API concepts and usage.<\/p>\n<p>This tutorial was developed using Crosswork Network Controller release 7.2 as a reference.<br \/>\nMore details are available online on <a href=\"https:\/\/developer.cisco.com\/docs\/crosswork\/network-controller\/api-reference-overview\/\" style=\"color: rgb(0, 102, 204)\">Cisco DevNet<\/a><\/p>\n<p><strong style=\"color: rgb(26, 26, 26)\"><sup>*1<\/sup><\/strong>: Although the topology APIs are implemented as part of the Crosswork Optimization Engine feature set, they are considered part of the Element Management Function area.<\/p>\n<h2 style=\"color: rgb(26, 26, 26); font-weight: 700\">1. RESTCONF Notifications \u2014 Alarms and Inventory<\/h2>\n<p>The first set of RESTCONF notification APIs focuses on alarms and inventory. These notifications allow OSS to track real-time changes such as creation, update or deletion of alarms, nodes, modules and other model objects.<\/p>\n<p>These APIs support both connectionless and connection-oriented (WebSocket-based) notifications.<br \/>\nDifferent endpoints are available for connectionless and connection-oriented notification subscriptions.<br \/>\nFor connection-oriented notifications, filters can be defined in the resource endpoint itself.<br \/>\nFor connectionless notifications, filters must be defined in the POST payload.<\/p>\n<h3 style=\"color: rgb(26, 26, 26); font-weight: 700\">1.1 Subscription Resource Endpoints<\/h3>\n<p><strong style=\"color: rgb(26, 26, 26)\"><em>NOTE:<\/em><\/strong> Base URL:<\/p>\n<pre><code><span>https:\/\/<span>{<\/span><span>{<\/span>server_ip<span>}<\/span><span>}<\/span>:30603\/crosswork\/notification\n<\/span><\/code><\/pre>\n<p>Different resource paths are available for subscriptions, depending on whether the connectionless or connection-oriented method is used:<\/p>\n<p><strong style=\"color: rgb(26, 26, 26)\">Connection-oriented:<\/strong><\/p>\n<pre><code><span>\/restconf\/streams\/v2\/alarm.xml <span>(<\/span>XML encoding<span>)<\/span>\n<\/span><span>\/restconf\/streams\/v2\/alarm.json <span>(<\/span>JSON encoding<span>)<\/span>\n<\/span><span>\/restconf\/streams\/v1\/inventory.xml <span>(<\/span>XML encoding<span>)<\/span>\n<\/span><span>\/restconf\/streams\/v1\/inventory.json <span>(<\/span>JSON encoding<span>)<\/span>\n<\/span><\/code><\/pre>\n<p><strong style=\"color: rgb(26, 26, 26)\">Connectionless:<\/strong><\/p>\n<pre><code><span>\/restconf\/data\/v2\/notifications:subscription\n<\/span><\/code><\/pre>\n<h3 style=\"color: rgb(26, 26, 26); font-weight: 700\">1.2 Connection-Oriented Client Subscriptions<\/h3>\n<p>Connection-oriented clients can subscribe using one of the resource endpoints shown above (XML or JSON).<\/p>\n<ul>\n<li>Filters can be appended to the subscription endpoint using the following syntax:<\/li>\n<\/ul>\n<pre><code><span>\/restconf\/streams\/v2\/alarm?<span>{<\/span>filterType<span>}<\/span><span>=<\/span><span>{<\/span>filterValue<span>}<\/span>\n<\/span><span>\/restconf\/streams\/v1\/inventory?<span>{<\/span>filterType<span>}<\/span><span>=<\/span><span>{<\/span>filterValue<span>}<\/span>\n<\/span><\/code><\/pre>\n<ul>\n<li>Once a connection is established, clients receive push notifications from the EMF notification system until they disconnect.<\/li>\n<li>The server sends heartbeat messages to the client every 60 seconds when there are no notifications to forward.<\/li>\n<\/ul>\n<h3 style=\"color: rgb(26, 26, 26); font-weight: 700\">1.3 Connectionless Client Subscriptions<\/h3>\n<p>A connectionless subscription requires a payload that defines the following:<\/p>\n<ul>\n<li>The destination endpoint<\/li>\n<li>The topic name (alarm or inventory)<\/li>\n<li>The encoding (JSON or XML)<\/li>\n<li>Filters<\/li>\n<\/ul>\n<p>The EMF notification system then sends notifications to registered endpoints using POST requests. The notification content is included in each POST payload.<br \/>\nConnectionless subscriptions are stateless, so no connection is maintained. The EMF notification system sends push notifications until the subscription is deleted.<\/p>\n<ul>\n<li>Filters are included in the POST payload using the following format:<\/li>\n<\/ul>\n<pre><code><span><span>\"ietf-restconf:notification.filters\"<\/span><span>:<\/span> <span>[<\/span>\n<\/span><span> <span>{<\/span>\n<\/span><span> <span>\"ietf-restconf:notification.key\"<\/span><span>:<\/span> <span>\"filterType\"<\/span>,\n<\/span><span> <span>\"ietf-restconf:notification.value\"<\/span><span>:<\/span> <span>\"filterValue\"<\/span>\n<\/span><span> <span>}<\/span>\n<\/span><span><span>]<\/span>\n<\/span><\/code><\/pre>\n<h3 style=\"color: rgb(26, 26, 26); font-weight: 700\">1.4 Connection-Oriented and Connectionless Filters<\/h3>\n<p>Subscriptions support the following filter types:<\/p>\n<ul>\n<li>productFamily<\/li>\n<li>productType<\/li>\n<li>severity<\/li>\n<li>deviceUUID<\/li>\n<\/ul>\n<p>Multiple filter types and values are supported.<\/p>\n<pre><code><span>\/restconf\/streams\/v2\/alarm.json?productType<span>=<\/span>Cisco NCS <span>5501<\/span>, Cisco ASR <span>9904<\/span> Router<span>&amp;<\/span><span>severity<\/span><span>=<\/span>critical,major\n<\/span><span>\/restconf\/streams\/v1\/inventory.json?productType<span>=<\/span>Cisco NCS <span>5501<\/span>, Cisco ASR <span>9904<\/span> Router\n<\/span><\/code><\/pre>\n<p><strong style=\"color: rgb(26, 26, 26)\">Connection-Oriented Example<\/strong><\/p>\n<pre><code><span><span>{<\/span>\n<\/span><span> <span>\"ietf-restconf:notification.client-url\"<\/span><span>:<\/span> <span>\"http:\/\/10.58.234.211:7070\/notifications\"<\/span>,\n<\/span><span> <span>\"ietf-restconf:notification.topic\"<\/span><span>:<\/span> <span>\"alarm\"<\/span>,\n<\/span><span> <span>\"ietf-restconf:notification.format\"<\/span><span>:<\/span> <span>\"json\"<\/span>,\n<\/span><span> <span>\"ietf-restconf:notification.filters\"<\/span><span>:<\/span> <span>[<\/span>\n<\/span><span> <span>{<\/span>\n<\/span><span> <span>\"etf-restconf:notification.key\"<\/span><span>:<\/span> <span>\"productType\"<\/span>,\n<\/span><span> <span>\"etf-restconf:notification.value\"<\/span><span>:<\/span> <span>\"Cisco NCS 5501,Cisco ASR 9904 Router\"<\/span>\n<\/span><span> <span>}<\/span>,\n<\/span><span> <span>{<\/span>\n<\/span><span> <span>\"etf-restconf:notification.key\"<\/span><span>:<\/span> <span>\"severity\"<\/span>,\n<\/span><span> <span>\"etf-restconf:notification.value\"<\/span><span>:<\/span> <span>\"critical,major\"<\/span>\n<\/span><span> <span>}<\/span>\n<\/span><span> <span>]<\/span>\n<\/span><span><span>}<\/span>\n<\/span><\/code><\/pre>\n<p><strong style=\"color: rgb(26, 26, 26)\">Connectionless Example<\/strong><\/p>\n<p><strong style=\"color: rgb(26, 26, 26)\"><em>NOTE:<\/em><\/strong> For connectionless subscriptions, the topic can only be <code>alarm<\/code> or <code>inventory<\/code>.<\/p>\n<h3 style=\"color: rgb(26, 26, 26); font-weight: 700\">1.5 RESTCONF Alarm and Inventory Notification Examples<\/h3>\n<pre><code><span><span>{<\/span>\n<\/span><span> <span>\"ietf-restconf:notification.notification\"<\/span><span>:<\/span> <span>{<\/span>\n<\/span><span> <span>\"ietf-restconf:notification.topic\"<\/span><span>:<\/span> <span>\"alarm\"<\/span>,\n<\/span><span> <span>\"ietf-restconf:notification.time-of-update\"<\/span><span>:<\/span> <span>\"2025-12-09 16:58:18.284\"<\/span>,\n<\/span><span> <span>\"ietf-restconf:notification.time-of-update-iso8601\"<\/span><span>:<\/span> <span>\"2025-12-09T16:58:18.373+01:00\"<\/span>,\n<\/span><span> <span>\"ietf-restconf:notification.operation\"<\/span><span>:<\/span> <span>\"modify\"<\/span>,\n<\/span><span> <span>\"alm.alarm\"<\/span><span>:<\/span> <span>{<\/span>\n<\/span><span> <span>\"alm.alarm-identifier\"<\/span><span>:<\/span> <span>{<\/span>\n<\/span><span> <span>\"alm.event-identifier\"<\/span><span>:<\/span> <span>\"0aa3f125-0170-4690-b034-5d8c095972c4\"<\/span>,\n<\/span><span> <span>\"alm.resource-object-ref\"<\/span><span>:<\/span> <span>\"MD=CISCO_EMS!ND=Palinuro-29\"<\/span>,\n<\/span><span> <span>\"alm.probable-cause\"<\/span><span>:<\/span> <span>\"SECURITY-SSHD-4-INFO_FAILURE\"<\/span>\n<\/span><span> <span>}<\/span>,\n<\/span><span> <span>\"alm.uuid\"<\/span><span>:<\/span> <span>\"0aa3f125-0170-4690-b034-5d8c095972c4\"<\/span>,\n<\/span><span> <span>\"alm.type\"<\/span><span>:<\/span> <span>\"device\"<\/span>,\n<\/span><span> <span>\"alm.perceived-severity\"<\/span><span>:<\/span> <span>\"cleared\"<\/span>,\n<\/span><span> <span>\"alm.description\"<\/span><span>:<\/span> <span>\"Successfully authenticated user 'epnm' from '10.58.29.231' on 'vty1'(cipher 'aes128-ctr', mac 'hmac-sha1') <span title=\"\\n\">\\n<\/span>\"<\/span>,\n<\/span><span> <span>\"alm.category\"<\/span><span>:<\/span> <span>\"Security\"<\/span>,\n<\/span><span> <span>\"alm.source-object-ref\"<\/span><span>:<\/span> <span>\"MD=CISCO_EMS!ND=Palinuro-29\"<\/span>,\n<\/span><span> <span>\"alm.source-object-name\"<\/span><span>:<\/span> <span>\"\"<\/span>,\n<\/span><span> <span>\"alm.source-object-id\"<\/span><span>:<\/span> <span>0<\/span>,\n<\/span><span> <span>\"alm.node-ref\"<\/span><span>:<\/span> <span>\"Palinuro-29\"<\/span>,\n<\/span><span> <span>\"alm.business-key\"<\/span><span>:<\/span> <span>\"10.58.244.29:10.58.29.231:SECURITY-SSHD##SubAlarm@_1\"<\/span>,\n<\/span><span> <span>\"alm.cause-type\"<\/span><span>:<\/span> <span>\"cause-unknown\"<\/span>,\n<\/span><span> <span>\"alm.ack-state\"<\/span><span>:<\/span> <span>\"unacknowledged\"<\/span>,\n<\/span><span> <span>\"alm.remote-interface-ip-address\"<\/span><span>:<\/span> <span>\"10.58.244.29\"<\/span>,\n<\/span><span> <span>\"alm.system-received-time\"<\/span><span>:<\/span> <span>\"2025-11-23 12:34:49.000\"<\/span>,\n<\/span><span> <span>\"alm.system-received-time-iso8601\"<\/span><span>:<\/span> <span>\"2025-11-23T12:34:49.000+01:00\"<\/span>,\n<\/span><span> <span>\"alm.system-update-time\"<\/span><span>:<\/span> <span>\"2025-12-09 16:58:18.284\"<\/span>,\n<\/span><span> <span>\"alm.system-update-time-iso8601\"<\/span><span>:<\/span> <span>\"2025-12-09T16:58:18.284+01:00\"<\/span>,\n<\/span><span> <span>\"alm.probable-cause\"<\/span><span>:<\/span> <span>\"SECURITY-SSHD-4-INFO_FAILURE\"<\/span>,\n<\/span><span> <span>\"alm.service-affecting\"<\/span><span>:<\/span> <span>\"service-affecting-unknown\"<\/span>,\n<\/span><span> <span>\"alm.service-impacting\"<\/span><span>:<\/span> <span>\"service-impacting-unknown\"<\/span>,\n<\/span><span> <span>\"alm.owner\"<\/span><span>:<\/span> <span>\"\"<\/span>,\n<\/span><span> <span>\"alm.root-cause-alarm-identifier\"<\/span><span>:<\/span> <span>{<\/span>\n<\/span><span> <span>\"alm.event-identifier\"<\/span><span>:<\/span> <span>0<\/span>\n<\/span><span> <span>}<\/span>,\n<\/span><span> <span>\"alm.user-defined-fields\"<\/span><span>:<\/span> <span>\"\"<\/span>\n<\/span><span> <span>}<\/span>\n<\/span><span> <span>}<\/span>\n<\/span><span><span>}<\/span>\n<\/span><\/code><\/pre>\n<p><strong style=\"color: rgb(26, 26, 26)\">Device Alarm Notification<\/strong><\/p>\n<pre><code><span><span>{<\/span>\n<\/span><span> <span>\"ietf-restconf:notification.notification\"<\/span><span>:<\/span> <span>{<\/span>\n<\/span><span> <span>\"ietf-restconf:notification.topic\"<\/span><span>:<\/span> <span>\"alarm\"<\/span>,\n<\/span><span> <span>\"ietf-restconf:notification.time-of-update\"<\/span><span>:<\/span> <span>\"2025-12-09 16:56:56.736\"<\/span>,\n<\/span><span> <span>\"ietf-restconf:notification.time-of-update-iso8601\"<\/span><span>:<\/span> <span>\"2025-12-09T16:56:57.073+01:00\"<\/span>,\n<\/span><span> <span>\"ietf-restconf:notification.operation\"<\/span><span>:<\/span> <span>\"modify\"<\/span>,\n<\/span><span> <span>\"alm.alarm\"<\/span><span>:<\/span> <span>{<\/span>\n<\/span><span> <span>\"alm.alarm-identifier\"<\/span><span>:<\/span> <span>{<\/span>\n<\/span><span> <span>\"alm.event-identifier\"<\/span><span>:<\/span> <span>\"45c44fd6-3313-416f-b584-e5e643880121\"<\/span>,\n<\/span><span> <span>\"alm.resource-object-ref\"<\/span><span>:<\/span> <span>\"MD=CISCO_EMS!OS=optima-csm-1\"<\/span>,\n<\/span><span> <span>\"alm.probable-cause\"<\/span><span>:<\/span> <span>\"CSM-POLICY-BW-EXCEEDED\"<\/span>\n<\/span><span> <span>}<\/span>,\n<\/span><span> <span>\"alm.uuid\"<\/span><span>:<\/span> <span>\"45c44fd6-3313-416f-b584-e5e643880121\"<\/span>,\n<\/span><span> <span>\"alm.type\"<\/span><span>:<\/span> <span>\"system\"<\/span>,\n<\/span><span> <span>\"alm.perceived-severity\"<\/span><span>:<\/span> <span>\"cleared\"<\/span>,\n<\/span><span> <span>\"alm.description\"<\/span><span>:<\/span> <span>\"Traffic no longer exceeds policy bandwidth\"<\/span>,\n<\/span><span> <span>\"alm.category\"<\/span><span>:<\/span> <span>\"System\"<\/span>,\n<\/span><span> <span>\"alm.source-object-ref\"<\/span><span>:<\/span> <span>\"MD=CISCO_EMS!OS=optima-csm-1\"<\/span>,\n<\/span><span> <span>\"alm.source-object-name\"<\/span><span>:<\/span> <span>\"capp-coe\"<\/span>,\n<\/span><span> <span>\"alm.source-object-id\"<\/span><span>:<\/span> <span>0<\/span>,\n<\/span><span> <span>\"alm.node-ref\"<\/span><span>:<\/span> <span>\"optima-csm-1\"<\/span>,\n<\/span><span> <span>\"alm.business-key\"<\/span><span>:<\/span> <span>\"capp-coe-CSM-POLICY-BW-EXCEEDED##SubAlarm@_261\"<\/span>,\n<\/span><span> <span>\"alm.cause-type\"<\/span><span>:<\/span> <span>\"cause-unknown\"<\/span>,\n<\/span><span> <span>\"alm.ack-state\"<\/span><span>:<\/span> <span>\"unacknowledged\"<\/span>,\n<\/span><span> <span>\"alm.remote-interface-ip-address\"<\/span><span>:<\/span> <span>\"optima-csm-1\"<\/span>,\n<\/span><span> <span>\"alm.system-received-time\"<\/span><span>:<\/span> <span>\"2025-12-07 11:26:17.779\"<\/span>,\n<\/span><span> <span>\"alm.system-received-time-iso8601\"<\/span><span>:<\/span> <span>\"2025-12-07T11:26:17.779+01:00\"<\/span>,\n<\/span><span> <span>\"alm.system-update-time\"<\/span><span>:<\/span> <span>\"2025-12-09 16:56:56.736\"<\/span>,\n<\/span><span> <span>\"alm.system-update-time-iso8601\"<\/span><span>:<\/span> <span>\"2025-12-09T16:56:56.736+01:00\"<\/span>,\n<\/span><span> <span>\"alm.probable-cause\"<\/span><span>:<\/span> <span>\"CSM-POLICY-BW-EXCEEDED\"<\/span>,\n<\/span><span> <span>\"alm.service-affecting\"<\/span><span>:<\/span> <span>\"service-affecting-unknown\"<\/span>,\n<\/span><span> <span>\"alm.service-impacting\"<\/span><span>:<\/span> <span>\"service-impacting-unknown\"<\/span>,\n<\/span><span> <span>\"alm.owner\"<\/span><span>:<\/span> <span>\"\"<\/span>,\n<\/span><span> <span>\"alm.root-cause-alarm-identifier\"<\/span><span>:<\/span> <span>{<\/span>\n<\/span><span> <span>\"alm.event-identifier\"<\/span><span>:<\/span> <span>0<\/span>\n<\/span><span> <span>}<\/span>,\n<\/span><span> <span>\"alm.user-defined-fields\"<\/span><span>:<\/span> <span>\"\"<\/span>\n<\/span><span> <span>}<\/span>\n<\/span><span> <span>}<\/span>\n<\/span><span><span>}<\/span>\n<\/span><\/code><\/pre>\n<p><strong style=\"color: rgb(26, 26, 26)\">System Alarm Notification<\/strong><\/p>\n<pre><code><span><span>{<\/span>\n<\/span><span> <span>\"ietf-restconf:notification.notification\"<\/span><span>:<\/span> <span>{<\/span>\n<\/span><span> <span>\"ietf-restconf:notification.topic\"<\/span><span>:<\/span> <span>\"alarm\"<\/span>,\n<\/span><span> <span>\"ietf-restconf:notification.time-of-update\"<\/span><span>:<\/span> <span>\"2025-12-09 16:53:34.860\"<\/span>,\n<\/span><span> <span>\"ietf-restconf:notification.time-of-update-iso8601\"<\/span><span>:<\/span> <span>\"2025-12-09T16:53:37.315+01:00\"<\/span>,\n<\/span><span> <span>\"ietf-restconf:notification.operation\"<\/span><span>:<\/span> <span>\"modify\"<\/span>,\n<\/span><span> <span>\"alm.alarm\"<\/span><span>:<\/span> <span>{<\/span>\n<\/span><span> <span>\"alm.alarm-identifier\"<\/span><span>:<\/span> <span>{<\/span>\n<\/span><span> <span>\"alm.event-identifier\"<\/span><span>:<\/span> <span>\"c423d213-8bc7-4827-a97b-df1cf96b31f5\"<\/span>,\n<\/span><span> <span>\"alm.resource-object-ref\"<\/span><span>:<\/span> <span>\"MD=CISCO_EMS!ND=10.58.244.141-PceProviderHttpAlarm\"<\/span>,\n<\/span><span> <span>\"alm.probable-cause\"<\/span><span>:<\/span> <span>\"PceProviderHttpAlarm\"<\/span>\n<\/span><span> <span>}<\/span>,\n<\/span><span> <span>\"alm.uuid\"<\/span><span>:<\/span> <span>\"c423d213-8bc7-4827-a97b-df1cf96b31f5\"<\/span>,\n<\/span><span> <span>\"alm.type\"<\/span><span>:<\/span> <span>\"network\"<\/span>,\n<\/span><span> <span>\"alm.perceived-severity\"<\/span><span>:<\/span> <span>\"critical\"<\/span>,\n<\/span><span> <span>\"alm.description\"<\/span><span>:<\/span> <span>\"SR-PCE 'sr-pce-141' with Host IP 10.58.244.141 for HTTP setting is disconnected.\"<\/span>,\n<\/span><span> <span>\"alm.category\"<\/span><span>:<\/span> <span>\"Network\"<\/span>,\n<\/span><span> <span>\"alm.source-object-ref\"<\/span><span>:<\/span> <span>\"MD=CISCO_EMS!ND=10.58.244.141-PceProviderHttpAlarm\"<\/span>,\n<\/span><span> <span>\"alm.source-object-name\"<\/span><span>:<\/span> <span>\"SR-PCE [sr-pce-141]\"<\/span>,\n<\/span><span> <span>\"alm.source-object-id\"<\/span><span>:<\/span> <span>0<\/span>,\n<\/span><span> <span>\"alm.node-ref\"<\/span><span>:<\/span> <span>\"10.58.244.141-PceProviderHttpAlarm\"<\/span>,\n<\/span><span> <span>\"alm.business-key\"<\/span><span>:<\/span> <span>\"http#d9d8f23-0e6d-46f3-afed-af950d9a00ce-PceProviderHttpAlarm##SubAlarm@_282\"<\/span>,\n<\/span><span> <span>\"alm.cause-type\"<\/span><span>:<\/span> <span>\"cause-unknown\"<\/span>,\n<\/span><span> <span>\"alm.ack-state\"<\/span><span>:<\/span> <span>\"unacknowledged\"<\/span>,\n<\/span><span> <span>\"alm.remote-interface-ip-address\"<\/span><span>:<\/span> <span>\"10.58.244.141-PceProviderHttpAlarm\"<\/span>,\n<\/span><span> <span>\"alm.system-received-time\"<\/span><span>:<\/span> <span>\"2025-12-09 16:53:34.860\"<\/span>,\n<\/span><span> <span>\"alm.system-received-time-iso8601\"<\/span><span>:<\/span> <span>\"2025-12-09T16:53:34.860+01:00\"<\/span>,\n<\/span><span> <span>\"alm.system-update-time\"<\/span><span>:<\/span> <span>\"2025-12-09 16:53:34.860\"<\/span>,\n<\/span><span> <span>\"alm.system-update-time-iso8601\"<\/span><span>:<\/span> <span>\"2025-12-09T16:53:34.860+01:00\"<\/span>,\n<\/span><span> <span>\"alm.probable-cause\"<\/span><span>:<\/span> <span>\"PceProviderHttpAlarm\"<\/span>,\n<\/span><span> <span>\"alm.service-affecting\"<\/span><span>:<\/span> <span>\"service-affecting-unknown\"<\/span>,\n<\/span><span> <span>\"alm.service-impacting\"<\/span><span>:<\/span> <span>\"service-impacting-unknown\"<\/span>,\n<\/span><span> <span>\"alm.owner\"<\/span><span>:<\/span> <span>\"\"<\/span>,\n<\/span><span> <span>\"alm.root-cause-alarm-identifier\"<\/span><span>:<\/span> <span>{<\/span>\n<\/span><span> <span>\"alm.event-identifier\"<\/span><span>:<\/span> <span>0<\/span>\n<\/span><span> <span>}<\/span>,\n<\/span><span> <span>\"alm.user-defined-fields\"<\/span><span>:<\/span> <span>\"\"<\/span>\n<\/span><span> <span>}<\/span>\n<\/span><span> <span>}<\/span>\n<\/span><span><span>}<\/span>\n<\/span><\/code><\/pre>\n<p><strong style=\"color: rgb(26, 26, 26)\">Network Alarm Notification<\/strong><\/p>\n<pre><code><span><span>{<\/span>\n<\/span><span> <span>\"ietf-restconf:notification.notification\"<\/span><span>:<\/span> <span>{<\/span>\n<\/span><span> <span>\"ietf-restconf:notification.topic\"<\/span><span>:<\/span> <span>\"inventory\"<\/span>,\n<\/span><span> <span>\"ietf-restconf:notification.time-of-update\"<\/span><span>:<\/span> <span>\"2024-08-20 08:50:55.583\"<\/span>,\n<\/span><span> <span>\"ietf-restconf:notification.time-of-update-iso8601\"<\/span><span>:<\/span> <span>\"2024-08-20T08:50:57.174Z\"<\/span>,\n<\/span><span> <span>\"ietf-restconf:notification.operation\"<\/span><span>:<\/span> <span>\"create\"<\/span>,\n<\/span><span> <span>\"eq.module\"<\/span><span>:<\/span> <span>{<\/span>\n<\/span><span> <span>\"fdtn.description\"<\/span><span>:<\/span> <span>\"Cisco 8000 Series 32x400G QSFPDD 1RU Fixed System w\/HBM\"<\/span>,\n<\/span><span> <span>\"fdtn.name\"<\/span><span>:<\/span> <span>\"Rack 0-Chassis IDPROM\"<\/span>,\n<\/span><span> <span>\"eq.connectors\"<\/span><span>:<\/span> <span>\"\"<\/span>,\n<\/span><span> <span>\"eq.contained-equipment-recurse\"<\/span><span>:<\/span> <span>\"\"<\/span>,\n<\/span><span> <span>\"eq.containing-equipment\"<\/span><span>:<\/span> <span>\"MD=CISCO_EMS!ND=Battipaglia-54!EQ=name=Rack 0;partnumber=68-7325-05\"<\/span>,\n<\/span><span> <span>\"eq.ent-physical-id\"<\/span><span>:<\/span> <span>8384519<\/span>,\n<\/span><span> <span>\"eq.equipment-type\"<\/span><span>:<\/span> <span>\"MODULE\"<\/span>,\n<\/span><span> <span>\"eq.fdn\"<\/span><span>:<\/span> <span>\"MD=CISCO_EMS!ND=Battipaglia-54!EQ=name=Rack 0-Chassis IDPROM;partnumber=N\/A\"<\/span>,\n<\/span><span> <span>\"eq.hardware-version\"<\/span><span>:<\/span> <span>\"V03\"<\/span>,\n<\/span><span> <span>\"eq.is-field-replaceable-unit\"<\/span><span>:<\/span> <span>\"FALSE\"<\/span>,\n<\/span><span> <span>\"eq.is-physically-present\"<\/span><span>:<\/span> true,\n<\/span><span> <span>\"eq.is-reporting-alarms-allowed\"<\/span><span>:<\/span> <span>\"UNKNOWN\"<\/span>,\n<\/span><span> <span>\"eq.manufactured-date\"<\/span><span>:<\/span> <span>\"2022-11-26T08:50:15Z\"<\/span>,\n<\/span><span> <span>\"eq.manufacturer\"<\/span><span>:<\/span> <span>\"Cisco Systems, Inc.\"<\/span>,\n<\/span><span> <span>\"eq.operational-state-code\"<\/span><span>:<\/span> <span>\"Unknown\"<\/span>,\n<\/span><span> <span>\"eq.product-id\"<\/span><span>:<\/span> <span>\"8201-32FH\"<\/span>,\n<\/span><span> <span>\"eq.serial-number\"<\/span><span>:<\/span> <span>\"FLM26480A7V\"<\/span>,\n<\/span><span> <span>\"eq.service-state\"<\/span><span>:<\/span> <span>\"UNKNOWN\"<\/span>,\n<\/span><span> <span>\"eq.vendor-equipment-type\"<\/span><span>:<\/span> <span>\"cevModuleCommonCards\"<\/span>\n<\/span><span> <span>}<\/span>\n<\/span><span> <span>}<\/span>\n<\/span><span><span>}<\/span>\n<\/span><\/code><\/pre>\n<p><strong style=\"color: rgb(26, 26, 26)\">Device Inventory Notification<\/strong><\/p>\n<h3 style=\"color: rgb(26, 26, 26); font-weight: 700\">1.6 Testing Clients<\/h3>\n<p>Connection-oriented and connectionless test clients are available on <a href=\"https:\/\/github.com\/CiscoDevNet\/Crosswork-SDK\/blob\/main\/Notification-client\/7.2\/bin\/\" style=\"color: rgb(0, 102, 204)\">GitHub<\/a><\/p>\n<p><img decoding=\"async\" src=\"https:\/\/www.anynet.ir\/blog\/wp-content\/uploads\/2026\/10\/sec1_08-1792047147.webp\" alt=\"Notification test client example\"><\/p>\n<h3 style=\"color: rgb(26, 26, 26); font-weight: 700\">1.7 Limitations on RESTCONF Alarms<\/h3>\n<ul>\n<li>RESTCONF subscriptions support only the following filter types:\n<ul>\n<li>productFamily<\/li>\n<li>productType<\/li>\n<li>severity<\/li>\n<li>deviceUUID<\/li>\n<\/ul>\n<\/li>\n<li>Currently, there are no options for filtering device alarm notifications separately from system or network alarm notifications.<\/li>\n<li>To receive only device alarms, use the productFamily filter with the following syntax:\n<pre><code><span>\/restconf\/streams\/v2\/alarm.json?productFamily<span>=<\/span>Routers,Switch\n<\/span><\/code><\/pre>\n<\/li>\n<li>At the time of writing, there is no known workaround for filtering only system or network alarms.<\/li>\n<\/ul>\n<h2 style=\"color: rgb(26, 26, 26); font-weight: 700\">2. RESTCONF Notifications \u2014 Topology<\/h2>\n<p>A different set of RESTCONF APIs focuses on Topology notifications. Although the topology APIs are implemented as part of the Crosswork Optimization Engine feature set, topology is considered part of the Element Management Function area. These notifications allow you to track real-time changes such as creation, update or deletion of nodes, links, interfaces, and LSPs in your network.<\/p>\n<p>Topology notifications include:<\/p>\n<ul>\n<li>L2 and L3 Topology Event notifications<\/li>\n<li>L3 Termination Point Event notifications<\/li>\n<li>L3 Link Event notifications<\/li>\n<li>Node Event notifications<\/li>\n<li>SR Policy Change Event notifications<\/li>\n<li>Performance Metrics notifications<\/li>\n<\/ul>\n<p><strong style=\"color: rgb(26, 26, 26)\"><em>NOTE:<\/em><\/strong> Notification models are based on IETF models.<\/p>\n<h3 style=\"color: rgb(26, 26, 26); font-weight: 700\">2.1 Topology Subscription Process<\/h3>\n<p><strong style=\"color: rgb(26, 26, 26)\"><em>NOTE:<\/em><\/strong> Base URL:<\/p>\n<pre><code><span>https:\/\/<span>{<\/span><span>{<\/span>server_ip<span>}<\/span><span>}<\/span>:30603\/crosswork\/nbi\/topology\/v3\/restconf\n<\/span><\/code><\/pre>\n<p>The subscription process consists of two steps:<\/p>\n<ul>\n<li>Create a notification stream:<\/li>\n<\/ul>\n<pre><code><span>\/operations\/sal-remote:create-notification-stream\n<\/span><\/code><\/pre>\n<p>This returns a subscription UUID.<\/p>\n<ul>\n<li>Listen for notifications using the returned UUID.<\/li>\n<\/ul>\n<pre><code><span>\/streams\/json\/urn:uuid:<span>{<\/span><span>{<\/span>subscription_uuid<span>}<\/span><span>}<\/span>\n<\/span><\/code><\/pre>\n<p>It\u2019s also possible to list all created notification streams:<\/p>\n<pre><code><span>\/data\/ietf-restconf-monitoring:restconf-state\/streams\n<\/span><\/code><\/pre>\n<h3 style=\"color: rgb(26, 26, 26); font-weight: 700\">2.2 Topology Subscription Options<\/h3>\n<p>Crosswork Network Controller provides different types of topology notifications. Users can subscribe to one or more by adding the appropriate options to the <code>notifications<\/code> list in the request body:<\/p>\n<pre><code><span><span>\"notifications\"<\/span><span>:<\/span> <span>[<\/span>\n<\/span><span> <span>\"(urn:ietf:params:xml:ns:yang:ietf-l3-unicast-topology-state?revision=2018-02-26)l3-node-event\"<\/span>,\n<\/span><span> <span>\"(urn:ietf:params:xml:ns:yang:ietf-l3-unicast-topology-state?revision=2018-02-26)l3-link-event\"<\/span>,\n<\/span><span> <span>\"(urn:ietf:params:xml:ns:yang:ietf-l3-unicast-topology-state?revision=2018-02-26)l3-prefix-event\"<\/span>,\n<\/span><span> <span>\"(urn:ietf:params:xml:ns:yang:ietf-l3-unicast-topology-state?revision=2018-02-26)termination-point-event\"<\/span>,\n<\/span><span> <span>\"(urn:ietf:params:xml:ns:yang:ietf-l2-topology-state?revision=2020-11-15)l2-link-event\"<\/span>\n<\/span><span><span>]<\/span>\n<\/span><\/code><\/pre>\n<h3 style=\"color: rgb(26, 26, 26); font-weight: 700\">2.3 RESTCONF Topology Notification Examples<\/h3>\n<pre><code><span><span>{<\/span>\n<\/span><span> <span>\"ietf-restconf:notification\"<\/span><span>:<\/span> <span>{<\/span>\n<\/span><span> <span>\"event-time\"<\/span><span>:<\/span> <span>\"2026-10-06T16:27:01.532695836+02:00\"<\/span>,\n<\/span><span> <span>\"ietf-l2-topology-state:l2-link-event\"<\/span><span>:<\/span> <span>{<\/span>\n<\/span><span> <span>\"event-type\"<\/span><span>:<\/span> <span>\"removal\"<\/span>,\n<\/span><span> <span>\"l2-link-attributes\"<\/span><span>:<\/span> <span>{<\/span>\n<\/span><span> <span>\"name\"<\/span><span>:<\/span> <span>\"GigabitEthernet0\/0\/0\/8: Torre-125: GigabitEthernet0\/0\/2: ETHERNET\"<\/span>\n<\/span><span> <span>}<\/span>,\n<\/span><span> <span>\"network-ref\"<\/span><span>:<\/span> <span>\"Default-network\"<\/span>,\n<\/span><span> <span>\"link-ref\"<\/span><span>:<\/span> <span>\"Napoli-45: GigabitEthernet0\/0\/0\/8: Torre-125: GigabitEthernet0\/0\/2: ETHERNET\"<\/span>\n<\/span><span> <span>}<\/span>\n<\/span><span> <span>}<\/span>\n<\/span><span><span>}<\/span>\n<\/span><\/code><\/pre>\n<p><strong style=\"color: rgb(26, 26, 26)\">L2 Link Notification<\/strong><\/p>\n<pre><code><span><span>{<\/span>\n<\/span><span> <span>\"ietf-restconf:notification\"<\/span><span>:<\/span> <span>{<\/span>\n<\/span><span> <span>\"event-time\"<\/span><span>:<\/span> <span>\"2026-09-24T13:42:49.637648645+02:00\"<\/span>,\n<\/span><span> <span>\"ietf-l3-unicast-topology-state:l3-link-event\"<\/span><span>:<\/span> <span>{<\/span>\n<\/span><span> <span>\"l3-link-attributes\"<\/span><span>:<\/span> <span>{<\/span>\n<\/span><span> <span>\"name\"<\/span><span>:<\/span> <span>\"Torre-125: GigabitEthernet0\/0\/2: Napoli-45: GigabitEthernet0\/0\/0\/8: ISIS_IPV4_L2\"<\/span>,\n<\/span><span> <span>\"metric2\"<\/span><span>:<\/span> <span>\"10\"<\/span>,\n<\/span><span> <span>\"metric1\"<\/span><span>:<\/span> <span>\"10\"<\/span>,\n<\/span><span> <span>\"ietf-sr-mpls-topology-state:sr-mpls\"<\/span><span>:<\/span> <span>{<\/span>\n<\/span><span> <span>\"advertise-protection\"<\/span><span>:<\/span> <span>\"dual\"<\/span>,\n<\/span><span> <span>\"sids\"<\/span><span>:<\/span> <span>[<\/span>\n<\/span><span> <span>{<\/span> <span>..<\/span>. <span>}<\/span>,\n<\/span><span> <span>{<\/span> <span>..<\/span>. <span>}<\/span>\n<\/span><span> <span>]<\/span>,\n<\/span><span> <span>\"information-source\"<\/span><span>:<\/span> <span>\"isis\"<\/span>\n<\/span><span> <span>}<\/span>,\n<\/span><span> <span>\"cisco-crosswork-l3-te-topology:l3-link-attributes\"<\/span><span>:<\/span> <span>{<\/span>\n<\/span><span> <span>\"domain-id\"<\/span><span>:<\/span> <span>\"200\"<\/span>,\n<\/span><span> <span>\"max-bandwidth-kbps\"<\/span><span>:<\/span> <span>\"1000000\"<\/span>\n<\/span><span> <span>}<\/span>,\n<\/span><span> <span>\"cisco-crosswork-isis-topology:isis-link-attributes\"<\/span><span>:<\/span> <span>{<\/span>\n<\/span><span> <span>\"level\"<\/span><span>:<\/span> <span>2<\/span>,\n<\/span><span> <span>\"net\"<\/span><span>:<\/span> <span>{<\/span>\n<\/span><span> <span>\"system-id\"<\/span><span>:<\/span> <span>\"0000.0000.1250\"<\/span>\n<\/span><span> <span>}<\/span>\n<\/span><span> <span>}<\/span>\n<\/span><span> <span>}<\/span>,\n<\/span><span> <span>\"l3-unicast-topology\"<\/span><span>:<\/span> <span>{<\/span>\n<\/span><span> <span>\"cisco-crosswork-isis-topology:isis\"<\/span><span>:<\/span> <span>{<\/span><span>}<\/span>\n<\/span><span> <span>}<\/span>,\n<\/span><span> <span>\"link-ref\"<\/span><span>:<\/span> <span>\"Torre-125: GigabitEthernet0\/0\/2: Napoli-45: GigabitEthernet0\/0\/0\/8: ISIS_IPV4_L2\"<\/span>,\n<\/span><span> <span>\"l3-event-type\"<\/span><span>:<\/span> <span>\"remove\"<\/span>,\n<\/span><span> <span>\"network-ref\"<\/span><span>:<\/span> <span>\"Default-network\"<\/span>\n<\/span><span> <span>}<\/span>\n<\/span><span> <span>}<\/span>\n<\/span><span><span>}<\/span>\n<\/span><\/code><\/pre>\n<p><strong style=\"color: rgb(26, 26, 26)\">L3 Link Notification<\/strong><\/p>\n<pre><code><span><span>{<\/span>\n<\/span><span> <span>\"ietf-restconf:notification\"<\/span><span>:<\/span> <span>{<\/span>\n<\/span><span> <span>\"event-time\"<\/span><span>:<\/span> <span>\"2026-10-06T16:27:03.445010607+02:00\"<\/span>,\n<\/span><span> <span>\"ietf-l3-unicast-topology-state:l3-node-event\"<\/span><span>:<\/span> <span>{<\/span>\n<\/span><span> <span>\"l3-node-attributes\"<\/span><span>:<\/span> <span>{<\/span>\n<\/span><span> <span>\"name\"<\/span><span>:<\/span> <span>\"Torre-125\"<\/span>,\n<\/span><span> <span>\"cisco-crosswork-l3-te-topology:ipv6-router-id\"<\/span><span>:<\/span> <span>[<\/span> <span>..<\/span>. <span>]<\/span>,\n<\/span><span> <span>\"router-id\"<\/span><span>:<\/span> <span>[<\/span> <span>..<\/span>. <span>]<\/span>,\n<\/span><span> <span>\"ietf-sr-mpls-topology-state:sr-mpls\"<\/span><span>:<\/span> <span>{<\/span> <span>..<\/span>. <span>}<\/span>,\n<\/span><span> <span>\"cisco-crosswork-isis-topology:isis-node-attributes\"<\/span><span>:<\/span> <span>[<\/span> <span>..<\/span>. <span>]<\/span>,\n<\/span><span> <span>\"prefix\"<\/span><span>:<\/span> <span>[<\/span> <span>..<\/span>. <span>]<\/span>\n<\/span><span> <span>}<\/span>,\n<\/span><span> <span>\"l3-unicast-topology\"<\/span><span>:<\/span> <span>{<\/span>\n<\/span><span> <span>\"cisco-crosswork-srv6-topology-state:srv6\"<\/span><span>:<\/span> <span>{<\/span><span>}<\/span>,\n<\/span><span> <span>\"cisco-crosswork-isis-topology:isis\"<\/span><span>:<\/span> <span>{<\/span><span>}<\/span>\n<\/span><span> <span>}<\/span>,\n<\/span><span> <span>\"l3-event-type\"<\/span><span>:<\/span> <span>\"update\"<\/span>,\n<\/span><span> <span>\"node-ref\"<\/span><span>:<\/span> <span>\"Torre-125\"<\/span>,\n<\/span><span> <span>\"network-ref\"<\/span><span>:<\/span> <span>\"Default-network\"<\/span>\n<\/span><span> <span>}<\/span>\n<\/span><span> <span>}<\/span>\n<\/span><span><span>}<\/span>\n<\/span><\/code><\/pre>\n<p><strong style=\"color: rgb(26, 26, 26)\">L3 Node Notification<\/strong><\/p>\n<pre><code><span><span>{<\/span>\n<\/span><span> <span>\"ietf-restconf:notification\"<\/span><span>:<\/span> <span>{<\/span>\n<\/span><span> <span>\"event-time\"<\/span><span>:<\/span> <span>\"2026-10-06T16:27:02.161627238+02:00\"<\/span>,\n<\/span><span> <span>\"ietf-l3-unicast-topology-state:termination-point-event\"<\/span><span>:<\/span> <span>{<\/span>\n<\/span><span> <span>\"tp-ref\"<\/span><span>:<\/span> <span>\"GigabitEthernet0\/0\/8\"<\/span>,\n<\/span><span> <span>\"l3-termination-point-attributes\"<\/span><span>:<\/span> <span>{<\/span>\n<\/span><span> <span>\"ip-address\"<\/span><span>:<\/span> <span>[<\/span>\n<\/span><span> <span>\"2.45.125.45\"<\/span>\n<\/span><span> <span>]<\/span>\n<\/span><span> <span>}<\/span>,\n<\/span><span> <span>\"l3-event-type\"<\/span><span>:<\/span> <span>\"update\"<\/span>,\n<\/span><span> <span>\"node-ref\"<\/span><span>:<\/span> <span>\"Napoli-45\"<\/span>,\n<\/span><span> <span>\"network-ref\"<\/span><span>:<\/span> <span>\"Default-network\"<\/span>\n<\/span><span> <span>}<\/span>\n<\/span><span> <span>}<\/span>\n<\/span><span><span>}<\/span>\n<\/span><\/code><\/pre>\n<p><strong style=\"color: rgb(26, 26, 26)\">Termination Point Notification<\/strong><\/p>\n<h2 style=\"color: rgb(26, 26, 26); font-weight: 700\">3. Kafka Notifications<\/h2>\n<p>Crosswork Network Controller also provides a Kafka notification system, with the following subscription types:<\/p>\n<ul>\n<li>Alarm<\/li>\n<li>Inventory_Changes<\/li>\n<li>System_Audit<\/li>\n<li>Device_Performance_Monitoring<\/li>\n<li>Network_Performance_Monitoring<\/li>\n<li>Service_Health_Monitoring<\/li>\n<\/ul>\n<p>Kafka notifications use a subscription process comprising two steps:<\/p>\n<ol>\n<li>Define a Kafka destination<\/li>\n<li>Create a producer subscription<\/li>\n<\/ol>\n<h3 style=\"color: rgb(26, 26, 26); font-weight: 700\">3.1 Kafka Destination Definition<\/h3>\n<p>The most practical way to define a Kafka destination is through the Crosswork Network Controller GUI rather than the API (<a href=\"https:\/\/developer.cisco.com\/docs\/crosswork\/network-controller\/create-data-destination\/\" style=\"color: rgb(0, 102, 204)\">Cisco DevNet<\/a> provides more details about the available API).<\/p>\n<p>The Data Destination form is available under the Administration menu. In general, a destination can serve multiple Crosswork Network Controller applications and use cases (<a href=\"https:\/\/www.cisco.com\/c\/en\/us\/td\/docs\/cloud-systems-management\/crosswork-infrastructure\/7-2\/AdminGuide\/b-cisco-crosswork-admin-guide-7-2\/g-crosswork-data-gateway\/c-external-data-destination.html\" style=\"color: rgb(0, 102, 204)\">Crosswork Network Controller 7.2 Admin Guide<\/a> provides more details).<\/p>\n<p>When filling in the form, note the mandatory <strong style=\"color: rgb(26, 26, 26)\">Data Source<\/strong> parameter. It specifies whether Crosswork Network Controller uses the destination to stream application-generated data, raw data collected by its collector (Data Gateway), or both.<\/p>\n<p>In this case, select either <strong style=\"color: rgb(26, 26, 26)\">Application<\/strong> or <strong style=\"color: rgb(26, 26, 26)\">Any<\/strong>.<\/p>\n<p><img decoding=\"async\" src=\"https:\/\/www.anynet.ir\/blog\/wp-content\/uploads\/2026\/10\/sec3_01-1792047143.webp\" alt=\"Kafka destination data source selection\"><\/p>\n<p><strong style=\"color: rgb(26, 26, 26)\">Data Source Selection<\/strong><\/p>\n<h3 style=\"color: rgb(26, 26, 26); font-weight: 700\">3.2 Kafka Subscription Resource Endpoint<\/h3>\n<p><strong style=\"color: rgb(26, 26, 26)\"><em>NOTE:<\/em><\/strong> Base URL:<\/p>\n<pre><code><span>https:\/\/<span>{<\/span><span>{<\/span>server_ip<span>}<\/span><span>}<\/span>:30603\/crosswork\/notification\/v2\n<\/span><\/code><\/pre>\n<p>Use the following endpoint to create Kafka subscriptions:<\/p>\n<pre><code><span>\/subscription\n<\/span><\/code><\/pre>\n<p>The POST request requires a payload with the following fields:<\/p>\n<ul>\n<li><strong style=\"color: rgb(26, 26, 26)\">destinationName<\/strong>: Destination name as defined in the GUI<\/li>\n<li><strong style=\"color: rgb(26, 26, 26)\">destinationType<\/strong>: Kafka or gRPC*<\/li>\n<li><strong style=\"color: rgb(26, 26, 26)\">filter<\/strong>: This applies to inventory only; see below for details.<\/li>\n<li><strong style=\"color: rgb(26, 26, 26)\">topicName<\/strong>: Kafka topic name<\/li>\n<li><strong style=\"color: rgb(26, 26, 26)\">subscriptionDataType<\/strong>: One from\n<ul>\n<li>Inventory_Changes<\/li>\n<li>Alarm<\/li>\n<li>System_Audit<\/li>\n<li>Device_Performance_Monitoring<\/li>\n<li>Network_Performance_Monitoring<\/li>\n<li>Service_Health_Monitoring<\/li>\n<\/ul>\n<\/li>\n<li><strong style=\"color: rgb(26, 26, 26)\">subscriptionData<\/strong>: This applies to device, network, or service health PM only; see below for details.<\/li>\n<\/ul>\n<p><strong style=\"color: rgb(26, 26, 26)\"><em>NOTE:<\/em><\/strong> For gRPC, only Device_Performance_Monitoring and Network_Performance_Monitoring are supported.<\/p>\n<h3 style=\"color: rgb(26, 26, 26); font-weight: 700\"><strong style=\"color: rgb(26, 26, 26)\">filter<\/strong> Parameter<\/h3>\n<p>The optional Kafka <strong style=\"color: rgb(26, 26, 26)\">filter<\/strong> parameter can be used to filter inventory notifications.<\/p>\n<p>It can be set to one from:<\/p>\n<ul>\n<li>productFamily (Ex. Routers)<\/li>\n<li>productSeries (Ex. Cisco 8000 Series Routers)<\/li>\n<li>productType (Ex. Cisco 8201-32FH Router)<\/li>\n<\/ul>\n<p>Multiple values can be provided as a comma-separated list. If no filter is required, leave this field empty.<\/p>\n<h3 style=\"color: rgb(26, 26, 26); font-weight: 700\"><strong style=\"color: rgb(26, 26, 26)\">subscriptionData<\/strong> Parameter<\/h3>\n<p>The Kafka <strong style=\"color: rgb(26, 26, 26)\">subscriptionData<\/strong> (<strong style=\"color: rgb(26, 26, 26)\">Mandatory<\/strong>) parameter identifies which set of PM data to stream. Its value depends on the selected <strong style=\"color: rgb(26, 26, 26)\">subscriptionDataType<\/strong>.<\/p>\n<p>For <strong style=\"color: rgb(26, 26, 26)\">Device_Performance_Monitoring<\/strong>, <code>subscriptionData<\/code> is based on the policy type and policy name enabled in the Performance Policy list.<\/p>\n<ul>\n<li>Example: <code>policy_type=OpticalSFP, policy_instance=OPT_PM<\/code><\/li>\n<\/ul>\n<p>For <strong style=\"color: rgb(26, 26, 26)\">Network_Performance_Monitoring<\/strong> users can select one from:<\/p>\n<ul>\n<li>SR_PM_Interface<\/li>\n<li>SR_PM_Policy<\/li>\n<\/ul>\n<p>For <strong style=\"color: rgb(26, 26, 26)\">Service_Health_Monitoring<\/strong>, users can select one from:<\/p>\n<ul>\n<li>Y1731_Probes<\/li>\n<li>PCA_Probes<\/li>\n<\/ul>\n<p><strong style=\"color: rgb(26, 26, 26)\"><em>NOTE_1:<\/em><\/strong> Only one subscription per topic is allowed.<\/p>\n<p><strong style=\"color: rgb(26, 26, 26)\"><em>NOTE_2:<\/em><\/strong> Crosswork Network Controller uses <strong style=\"color: rgb(26, 26, 26)\">JSON<\/strong> encoding for alarm and inventory notifications, and <strong style=\"color: rgb(26, 26, 26)\">GPBKV<\/strong> for PM.<\/p>\n<blockquote>\n<p><strong style=\"color: rgb(26, 26, 26)\">Important:<\/strong> Unlike inventory subscriptions, alarm subscriptions do not support API-based filters that can be applied <strong style=\"color: rgb(26, 26, 26)\">contextually<\/strong> when this API call is made. As soon as a subscription is created, Crosswork Network Controller immediately streams all device, system, and network alarms and events to the Kafka destination.<\/p>\n<p>To apply a filter, users need to configure a <strong style=\"color: rgb(26, 26, 26)\">Notification Policy<\/strong>. This can be created through the GUI (described later) or the API. As a best practice, configure and validate the notification policy in a lab using the GUI, then apply it in production through the API when creating the subscription. This helps avoid placing an unnecessary load on the target Kafka cluster.<\/p>\n<\/blockquote>\n<h3 style=\"color: rgb(26, 26, 26); font-weight: 700\">3.3 Payload Examples<\/h3>\n<pre><code><span><span>{<\/span>\n<\/span><span> <span>\"destinationName\"<\/span><span>:<\/span> <span>\"external_kafka\"<\/span>,\n<\/span><span> <span>\"destinationType\"<\/span><span>:<\/span> <span>\"Kafka\"<\/span>,\n<\/span><span> <span>\"filter\"<\/span><span>:<\/span> null,\n<\/span><span> <span>\"topicName\"<\/span><span>:<\/span> <span>\"alarm_topic\"<\/span>,\n<\/span><span> <span>\"subscriptionData\"<\/span><span>:<\/span> null,\n<\/span><span> <span>\"subscriptionDataType\"<\/span><span>:<\/span> <span>\"Alarm\"<\/span>\n<\/span><span><span>}<\/span>\n<\/span><\/code><\/pre>\n<p><strong style=\"color: rgb(26, 26, 26)\">Alarm Subscription Payload<\/strong><\/p>\n<pre><code><span><span>{<\/span>\n<\/span><span> <span>\"destinationName\"<\/span><span>:<\/span> <span>\"external_kafka\"<\/span>,\n<\/span><span> <span>\"destinationType\"<\/span><span>:<\/span> <span>\"Kafka\"<\/span>,\n<\/span><span> <span>\"filter\"<\/span><span>:<\/span> null,\n<\/span><span> <span>\"topicName\"<\/span><span>:<\/span> <span>\"DPM_topic\"<\/span>\n<\/span><span> <span>\"subscriptionData\"<\/span><span>:<\/span> <span>\"policy_type=OpticalSFP, policy_instance=Optical SFP\"<\/span>,\n<\/span><span> <span>\"subscriptionDataType\"<\/span><span>:<\/span> <span>\"Device_Performance_Monitoring\"<\/span>,\n<\/span><span><span>}<\/span>\n<\/span><\/code><\/pre>\n<p><strong style=\"color: rgb(26, 26, 26)\">Device PM Subscription Payload<\/strong><\/p>\n<h3 style=\"color: rgb(26, 26, 26); font-weight: 700\">3.4 Kafka Notification Examples<\/h3>\n<p><strong style=\"color: rgb(26, 26, 26)\"><em>NOTE:<\/em><\/strong> For alarm and inventory notification examples, see Section 1.5; the examples are the same.<\/p>\n<pre><code><span><span>$be6a6904<\/span>-ce07-41e9-ad7a-8030ba9018cc?\n<\/span><span>?0???2MgmtEth0\/RSP0\/CPU0\/0??%-\n<\/span><span>?0???2TenGigE0\/0\/0\/0??%-\n<\/span><span>?0???2TenGigE0\/0\/0\/1??%-\n<\/span><span>?0???2TenGigE0\/0\/0\/2??%-\n<\/span><span>?0???2TenGigE0\/0\/0\/3??%-\n<\/span><span>?0???2TenGigE0\/0\/0\/4??%-\n<\/span><span>?0???2TenGigE0\/0\/0\/5??%-\n<\/span><span>?0???2TenGigE0\/0\/0\/6??%-\n<\/span><span>?0???2TenGigE0\/0\/0\/7??%-\n<\/span><span>?0???2TenGigE0\/0\/0\/8??%-\n<\/span><span>?0???2TenGigE0\/0\/0\/9??%-\n<\/span><span>?0???2TenGigE0\/0\/0\/10??%-\n<\/span><span>?0???2TenGigE0\/0\/0\/11??%-\n<\/span><span>?0???2TenGigE0\/0\/0\/12??%-\n<\/span><span>?0???2TenGigE0\/0\/0\/13??%-\n<\/span><span>?0???2TenGigE0\/0\/0\/14??%-\n<\/span><span>?0???2TenGigE0\/0\/0\/15??%-\n<\/span><span>?0???2TenGigE0\/0\/0\/16??%-\n<\/span><span>?0???2TenGigE0\/0\/0\/17??%-\n<\/span><span>?0???2TenGigE0\/0\/0\/18??%-\n<\/span><span>?0???2TenGigE0\/0\/0\/19??%-\n<\/span><span>?0???2HundredGigE0\/0\/1\/0??%-\n<\/span><span>?0???2HundredGigE0\/0\/1\/1??%-\n<\/span><span>?0???2FourHundredGigE0\/1\/0\/0??%-\n<\/span><span>?0???2FourHundredGigE0\/1\/0\/1??%-\n<\/span><\/code><\/pre>\n<p><strong style=\"color: rgb(26, 26, 26)\">Device PM Notification &#8211; GPBKV Encoded<\/strong><\/p>\n<p>Protocol message definition files are available on <a href=\"https:\/\/github.com\/CiscoDevNet\/Crosswork-SDK\/tree\/main\/EMS\/DPM\/Proto\" style=\"color: rgb(0, 102, 204)\">GitHub<\/a>.<\/p>\n<pre><code><span>??t?<span>{<\/span><span>\"AuditNotification\"<\/span>:<span>{<\/span><span>\"deviceIP\"<\/span><span>:<\/span><span>\"N\/A\"<\/span>,<span>\"clientIP\"<\/span><span>:<\/span><span>\"10.58.234.123\"<\/span>,<span>\"description\"<\/span><span>:<\/span><span>\"Logout successful\"<\/span>,<span>\"source\"<\/span><span>:<\/span><span>\"AAA\"<\/span>,<span>\"creationtime\"<\/span>:1725891947116,<span>\"userName\"<\/span><span>:<\/span><span>\"nmartino\"<\/span><span>}<\/span><span>}<\/span>\n<\/span><\/code><\/pre>\n<p><strong style=\"color: rgb(26, 26, 26)\">System Audit Notification<\/strong><\/p>\n<h2 style=\"color: rgb(26, 26, 26); font-weight: 700\">4. Notification Policies<\/h2>\n<p>Crosswork Network Controller provides Notification Policies to create new notification streams or filter existing ones.<\/p>\n<p>More specifically, Notification Policies can:<\/p>\n<ul>\n<li>Filter existing Kafka alarm notification streams<\/li>\n<li>Create new TRAP or SYSLOG notifications streams for Device alarms, System and Network events<\/li>\n<\/ul>\n<p><strong style=\"color: rgb(26, 26, 26)\"><em>NOTE:<\/em><\/strong> Multiple policies can be applied to the same Kafka stream.<\/p>\n<p>Two different types of notification policies can be created:<\/p>\n<ul>\n<li>System or network events<\/li>\n<li>Device alarms and events<\/li>\n<\/ul>\n<p><img decoding=\"async\" src=\"https:\/\/www.anynet.ir\/blog\/wp-content\/uploads\/2026\/10\/sec4_01-1792047140.webp\" alt=\"Notification policy options\"><\/p>\n<p><strong style=\"color: rgb(26, 26, 26)\">Notification Policies Options<\/strong><\/p>\n<h3 style=\"color: rgb(26, 26, 26); font-weight: 700\">4.1 System and Network Events Filters<\/h3>\n<p>When creating system or network event streams, users can apply filters in the Criteria section or use <code>*<\/code> to include all events.<\/p>\n<p>Criteria can be used to filter system events. Online help is available to assist with defining criteria.<\/p>\n<p><img decoding=\"async\" src=\"https:\/\/www.anynet.ir\/blog\/wp-content\/uploads\/2026\/10\/sec4_02-1792047136.webp\" alt=\"System and network event filter criteria\"><\/p>\n<p>Following system filters are available:<\/p>\n<ul>\n<li>Severity<\/li>\n<li>EventType<\/li>\n<li>Category<\/li>\n<li>Source<\/li>\n<li>GeneratedBy<\/li>\n<\/ul>\n<p>Only Severity (0\u20136) and Category (System, Network, and Audit) values are documented.<br \/>\nA partial list of system events is available and can be provided offline (contact me via email).<\/p>\n<h3 style=\"color: rgb(26, 26, 26); font-weight: 700\">4.2 Device Alarms and Events Filters<\/h3>\n<p>When creating device alarm and event streams, users can apply filters based on severity, alarm name, and alarm category.<\/p>\n<p><img decoding=\"async\" src=\"https:\/\/www.anynet.ir\/blog\/wp-content\/uploads\/2026\/10\/sec4_03-1792047148.webp\" alt=\"Device alarm and event filter criteria\"><\/p>\n<blockquote>\n<p><strong style=\"color: rgb(26, 26, 26)\">Important:<\/strong> When applied to an existing Kafka stream, a System Notification Policy will not filter out Device alarms. Sameway, a Device Notification Policy will not filter out System or Network events. Filtering device alarms separately from system or network alarms is possible but requires additional work.<\/p>\n<p>To receive only device alarms:<\/p>\n<ul>\n<li>Create a System\/Network Notification Policy with the criterion \u201cseverity=0.\u201d<\/li>\n<\/ul>\n<p>To receive only system and network alarms:<\/p>\n<ul>\n<li>Create a Device Alarm Notification Policy and select the alarm name \u201cODUK-1-AIS-PM.\u201d<\/li>\n<\/ul>\n<\/blockquote>\n<h3 style=\"color: rgb(26, 26, 26); font-weight: 700\">4.3 Notification Receivers<\/h3>\n<p>Notification receivers can be defined during notification policy creation or configured in advance under <strong style=\"color: rgb(26, 26, 26)\">Settings &gt; Notification Destination<\/strong>.<\/p>\n<p><img decoding=\"async\" src=\"https:\/\/www.anynet.ir\/blog\/wp-content\/uploads\/2026\/10\/sec4_04-1792047137.webp\" alt=\"Notification receiver settings\"><\/p>\n<h2 style=\"color: rgb(26, 26, 26); font-weight: 700\">5. TRAP Notifications<\/h2>\n<p>Crosswork Network Controller can also send device, system, and network alarms and events as SNMP TRAP notifications by using the Notification Policy workflow and the same filtering criteria described in the previous section.<\/p>\n<p>More details:<\/p>\n<ul>\n<li>Audit events are included in the system and network category<\/li>\n<li>It supports both SNMPv2 and SNMPv3<\/li>\n<li>Messages are formatted using CISCO-EPM-NOTIFICATION-MIB.<\/li>\n<\/ul>\n<p><strong style=\"color: rgb(26, 26, 26)\"><em>NOTE:<\/em><\/strong> The MIB implementation differs between device alarms and system, network, or audit events (see the next two sections for details).<\/p>\n<p>This notification process comprises two steps:<\/p>\n<ul>\n<li>Define a TRAP receiver (omitted for brevity; see the <a href=\"https:\/\/www.cisco.com\/c\/en\/us\/td\/docs\/cloud-systems-management\/crosswork-infrastructure\/7-2\/AdminGuide\/b-cisco-crosswork-admin-guide-7-2\/system-settings-and-notifications-chapter-reference\/system-settings-and-notifications.html\" style=\"color: rgb(0, 102, 204)\">Crosswork Network Controller 7.2 Admin Guide<\/a> for details).<\/li>\n<li>Create a Notification Policy, as described above.<\/li>\n<\/ul>\n<h3 style=\"color: rgb(26, 26, 26); font-weight: 700\">5.1 Device TRAP Notifications Examples and MIB Implementation<\/h3>\n<pre><code><span>.1.3.6.1.2.1.1.3.0<span>=<\/span><span>137336973<\/span>\n<\/span><span>.1.3.6.1.6.3.1.1.4.1.0<span>=<\/span>.1.3.6.1.4.1.9.9.311.0.2\n<\/span><span>.1.3.6.1.4.1.9.9.311.1.1.2.1.2.0<span>=<\/span><span>\"1.0\"<\/span>\n<\/span><span>.1.3.6.1.4.1.9.9.311.1.1.2.1.3.0<span>=<\/span><span>1788608530<\/span>\n<\/span><span>.1.3.6.1.4.1.9.9.311.1.1.2.1.4.0<span>=<\/span><span>1788608733<\/span>\n<\/span><span>.1.3.6.1.4.1.9.9.311.1.1.2.1.5.0<span>=<\/span><span>\"c387a038-4dfc-4281-92aa-61146b38e17e\"<\/span>\n<\/span><span>.1.3.6.1.4.1.9.9.311.1.1.2.1.6.0<span>=<\/span><span>3<\/span>\n<\/span><span>.1.3.6.1.4.1.9.9.311.1.1.2.1.7.0<span>=<\/span><span>\"3, CLEARED\"<\/span>\n<\/span><span>.1.3.6.1.4.1.9.9.311.1.1.2.1.8.0<span>=<\/span><span>2<\/span>\n<\/span><span>.1.3.6.1.4.1.9.9.311.1.1.2.1.9.0<span>=<\/span>-1\n<\/span><span>.1.3.6.1.4.1.9.9.311.1.1.2.1.10.0<span>=<\/span><span>\"-1, LINK_DOWN\"<\/span>\n<\/span><span>.1.3.6.1.4.1.9.9.311.1.1.2.1.11.0<span>=<\/span><span>1<\/span>\n<\/span><span>.1.3.6.1.4.1.9.9.311.1.1.2.1.12.0<span>=<\/span><span>\"10.244.171.44\"<\/span>\n<\/span><span>.1.3.6.1.4.1.9.9.311.1.1.2.1.13.0<span>=<\/span><span>\"Switches and Routers\"<\/span>\n<\/span><span>.1.3.6.1.4.1.9.9.311.1.1.2.1.14.0<span>=<\/span><span>1<\/span>\n<\/span><span>.1.3.6.1.4.1.9.9.311.1.1.2.1.15.0<span>=<\/span><span>\"10.58.238.196\"<\/span>\n<\/span><span>.1.3.6.1.4.1.9.9.311.1.1.2.1.16.0<span>=<\/span><span>\"Port 'Null0' (Description: 'Not available') is up on device '10.58.238.196'.\"<\/span>\n<\/span><span>.1.3.6.1.4.1.9.9.311.1.1.2.1.17.0<span>=<\/span><span>5<\/span>\n<\/span><span>.1.3.6.1.4.1.9.9.311.1.1.2.1.18.0<span>=<\/span><span>\"5, CLEARED\"<\/span>\n<\/span><span>.1.3.6.1.4.1.9.9.311.1.1.2.1.19.0<span>=<\/span><span>0<\/span>\n<\/span><span>.1.3.6.1.4.1.9.9.311.1.1.2.1.20.0<span>=<\/span><span>\"\"<\/span>\n<\/span><span>.1.3.6.1.4.1.9.9.311.1.1.2.1.21.0<span>=<\/span><span>\"srcObjectDisplayName=,rootCauseId=0,hostName=10.58.238.196,serviceImpacting=0,\u2026\u2026..\n<\/span><\/span><span><span>.1.3.6.1.4.1.9.9.311.1.1.2.1.22.0=\"<\/span>\"\n<\/span><span>.1.3.6.1.4.1.9.9.311.1.1.2.1.23.0<span>=<\/span><span>\"\"<\/span>\n<\/span><span>.1.3.6.1.4.1.9.9.311.1.1.2.1.24.0<span>=<\/span><span>2<\/span>\n<\/span><span>.1.3.6.1.4.1.9.9.311.1.1.2.1.25.0<span>=<\/span><span>0<\/span>\n<\/span><span>.1.3.6.1.4.1.9.9.311.1.1.2.1.26.0<span>=<\/span><span>\"\"<\/span>\n<\/span><span>.1.3.6.1.4.1.9.9.311.1.1.2.1.27.0<span>=<\/span><span>\"\"<\/span>\n<\/span><span>.1.3.6.1.4.1.9.9.311.1.1.2.1.28.0<span>=<\/span><span>\"\"<\/span>\n<\/span><span>.1.3.6.1.4.1.9.9.311.1.1.2.1.29.0<span>=<\/span><span>\"c387a038-4dfc-4281-92aa-61146b38e17e\"<\/span>\n<\/span><\/code><\/pre>\n<p><strong style=\"color: rgb(26, 26, 26)\">Device TRAP Example<\/strong><\/p>\n<h3 style=\"color: rgb(26, 26, 26); font-weight: 700\">Device TRAP &#8211; MIB Implementation<\/h3>\n<div style=\"max-width: 100%\" class=\"table-responsive\">\n<table class=\"english-numbers\">\n<thead>\n<tr>\n<th>SNMP Varbind<\/th>\n<th>Data Type*1<\/th>\n<th>Varbind OID<\/th>\n<th>Description<\/th>\n<th>Examples<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>cenAlarmVersion<\/td>\n<td>SnmpAdminString*2<\/td>\n<td>.1.3.6.1.4.9.9.31 1.1.1.2.1.2<\/td>\n<td>The release version of this MIB<\/td>\n<td>1.0<\/td>\n<\/tr>\n<tr>\n<td>cenAlarmTimestamp<\/td>\n<td>Timestamp<\/td>\n<td>.1.3.6.1.4.9.9.31 1.1.1.2.1.3<\/td>\n<td>The time when the alarm was raised<\/td>\n<td>1523608787<\/td>\n<\/tr>\n<tr>\n<td>cenAlarmUpdatedTimestamp<\/td>\n<td>Timestamp<\/td>\n<td>.1.3.6.1.4.9.9.31 1.1.1.2.1.4<\/td>\n<td>Last update time<\/td>\n<td>1523608788<\/td>\n<\/tr>\n<tr>\n<td>cenAlarmInstanceID<\/td>\n<td>SnmpAdminString<\/td>\n<td>.1.3.6.1.4.9.9.31 1.1.1.2.1.5<\/td>\n<td>The unique alarm instance ID<\/td>\n<td>c2afd3c1-d4e5-46db-84b2- 86d0d43f2056<\/td>\n<\/tr>\n<tr>\n<td>cenAlarmStatus<\/td>\n<td>Integer<\/td>\n<td>.1.3.6.1.4.9.9.31 1.1.1.2.1.6<\/td>\n<td>The alarm status indicates the status of the alarm in integer value. 2 = ACTIVE, 3 = CLEARED<\/td>\n<td>2<\/td>\n<\/tr>\n<tr>\n<td>cenAlarmStatusDefinition<\/td>\n<td>SnmpAdminString<\/td>\n<td>.1.3.6.1.4.9.9.31 1.1.1.2.1.7<\/td>\n<td>The short description of the status of the alarm. The string is formatted in &#8216;<integer>,<alarmstatus description=\"\">\u2019.<\/alarmstatus><\/integer><\/td>\n<td>2, ACTIVE<\/td>\n<\/tr>\n<tr>\n<td>cenAlarmType*1<\/td>\n<td>Integer<\/td>\n<td>.1.3.6.1.4.9.9.31 1.1.1.2.1.8<\/td>\n<td>\u2022 1 \u2013 unknown \u2022 2 \u2013 direct \u2022 3 \u2013 indirect \u2022 4 \u2013 mixed<\/td>\n<td>Hardcoded as 2<\/td>\n<\/tr>\n<tr>\n<td>cenAlarmCategory<\/td>\n<td>Integer<\/td>\n<td>.1.3.6.1.4.9.9.31 1.1.1.2.1.9<\/td>\n<td>Not Used \u2013 Instead, use cenAlarmCategoryDefinition<\/td>\n<td>&#8211;<\/td>\n<\/tr>\n<tr>\n<td>cenAlarmCategoryDefinition*2<\/td>\n<td>SnmpAdminString<\/td>\n<td>.1.3.6.1.4.9.9.31 1.1.1.2.1.10<\/td>\n<td>The short description of the category. The string is formatted in &#8216;<integer>,<alarmcategory description=\"\">\u2019 Integer should not be considered CNC Event Type<\/alarmcategory><\/integer><\/td>\n<td>&#8220;LINK_DOWN&#8221;, &#8220;LINK_UP&#8221;<\/td>\n<\/tr>\n<tr>\n<td>cenAlarmServerAddressType<\/td>\n<td>InetAddressType<\/td>\n<td>.1.3.6.1.4.9.9.31 1.1.1.2.1.11<\/td>\n<td>The type of Internet address by which the server is reachable. 0 = unknown, 1 = IPv4, 2 = IPv6<\/td>\n<td>1<\/td>\n<\/tr>\n<tr>\n<td>cenAlarmServerAddress*3<\/td>\n<td>InetAddress<\/td>\n<td>.1.3.6.1.4.9.9.31 1.1.1.2.1.12<\/td>\n<td>CNC alarm forwarding K8s pod, internal IP address<\/td>\n<td>10.244.251.122<\/td>\n<\/tr>\n<tr>\n<td>cenAlarmManagedObjectClass<\/td>\n<td>SnmpAdminString<\/td>\n<td>.1.3.6.1.4.9.9.31 1.1.1.2.1.13<\/td>\n<td>CNC Alarm category<\/td>\n<td>\u201cSwitches and Routers\u201d, \u201cBGP\u201d<\/td>\n<\/tr>\n<tr>\n<td>cenAlarmManagedObjectAddressType<\/td>\n<td>InetAddressType<\/td>\n<td>.1.3.6.1.4.9.9.31 1.1.1.2.1.14<\/td>\n<td>The type of Internet address by which the managed object (device) is reachable. 0 = unknown, 1 = IPv4, 2 = IPv6<\/td>\n<td>1<\/td>\n<\/tr>\n<tr>\n<td>cenAlarmManagedObjectAddress<\/td>\n<td>InetAddress<\/td>\n<td>.1.3.6.1.4.9.9.31 1.1.1.2.1.15<\/td>\n<td>The IP Address or the DNS name of the Managed Object (device)<\/td>\n<td>172.30.9.121<\/td>\n<\/tr>\n<tr>\n<td>cenAlarmDescription<\/td>\n<td>OctetString<\/td>\n<td>.1.3.6.1.4.9.9.31 1.1.1.2.1.16<\/td>\n<td>A detailed description of the alarm<\/td>\n<td>Check notes<\/td>\n<\/tr>\n<tr>\n<td>cenAlarmSeverity<\/td>\n<td>Integer<\/td>\n<td>.1.3.6.1.4.9.9.31 1.1.1.2.1.17<\/td>\n<td>\u2022 0 &#8211; CRITICAL \u2022 1 &#8211; MAJOR \u2022 2 &#8211; MINOR \u2022 3 &#8211; WARNING \u2022 4 &#8211; CLEARED \u2022 5 &#8211; INFO<\/td>\n<td>4<\/td>\n<\/tr>\n<tr>\n<td>cenAlarmSeverityDefinition<\/td>\n<td>SnmpAdminString<\/td>\n<td>.1.3.6.1.4.9.9.31 1.1.1.2.1.18<\/td>\n<td>The short description of the severity of the alarm generated. The string is formatted in &#8216;<integer>,<alarmseverity description=\"\">&#8216;<\/alarmseverity><\/integer><\/td>\n<td>4, CLEARED<\/td>\n<\/tr>\n<tr>\n<td>cenAlarmTriageValue<\/td>\n<td>Integer<\/td>\n<td>.1.3.6.1.4.9.9.31 1.1.1.2.1.19<\/td>\n<td>Not Used<\/td>\n<td>&#8211;<\/td>\n<\/tr>\n<tr>\n<td>cenEventIDList<\/td>\n<td>OctetString<\/td>\n<td>.1.3.6.1.4.9.9.31 1.1.1.2.1.20<\/td>\n<td>Not Used<\/td>\n<td>&#8211;<\/td>\n<\/tr>\n<tr>\n<td>cenUserMessage1<\/td>\n<td>SnmpAdminString<\/td>\n<td>.1.3.6.1.4.9.9.31 1.1.1.2.1.21<\/td>\n<td>Information about the alarm<\/td>\n<td>Check notes<\/td>\n<\/tr>\n<tr>\n<td>cenUserMessage2<\/td>\n<td>SnmpAdminString<\/td>\n<td>.1.3.6.1.4.9.9.31 1.1.1.2.1.22<\/td>\n<td>Not Used<\/td>\n<td>&#8211;<\/td>\n<\/tr>\n<tr>\n<td>cenUserMessage3<\/td>\n<td>SnmpAdminString<\/td>\n<td>.1.3.6.1.4.9.9.31 1.1.1.2.1.23<\/td>\n<td>Not Used<\/td>\n<td>&#8211;<\/td>\n<\/tr>\n<tr>\n<td>cenAlarmMode<\/td>\n<td>Integer<\/td>\n<td>.1.3.6.1.4.9.9.31 1.1.1.2.1.24<\/td>\n<td>\u2022 1 \u2013 unknown: When the value for this attribute could not be determined. \u2022 2 \u2013 alert: Denotes an alarm generated by a set of events where all events are reported by polling of managed objects and\/or listening to SNMP notifications. \u2022 3 \u2013 event: Denotes an event generated by polling of managed objects and\/or listening to SNMP notifications.<\/td>\n<td>2,3<\/td>\n<\/tr>\n<tr>\n<td>cenPartitionNumber<\/td>\n<td>Integer<\/td>\n<td>.1.3.6.1.4.9.9.31 1.1.1.2.1.25<\/td>\n<td>Not Used<\/td>\n<td>&#8211;<\/td>\n<\/tr>\n<tr>\n<td>cenPartitionName<\/td>\n<td>SnmpAdminString<\/td>\n<td>.1.3.6.1.4.9.9.31 1.1.1.2.1.26<\/td>\n<td>Not Used<\/td>\n<td>&#8211;<\/td>\n<\/tr>\n<tr>\n<td>cenCustomerIdentification<\/td>\n<td>SnmpAdminString<\/td>\n<td>.1.3.6.1.4.9.9.31 1.1.1.2.1.27<\/td>\n<td>Not Used<\/td>\n<td>&#8211;<\/td>\n<\/tr>\n<tr>\n<td>cenCustomerRevision<\/td>\n<td>SnmpAdminString<\/td>\n<td>.1.3.6.1.4.9.9.31 1.1.1.2.1.28<\/td>\n<td>Not Used<\/td>\n<td>&#8211;<\/td>\n<\/tr>\n<tr>\n<td>cenAlertID<\/td>\n<td>SnmpAdminString<\/td>\n<td>.1.3.6.1.4.9.9.31 1.1.1.2.1.29<\/td>\n<td>In an event-based notification, this attribute contains the alert ID to which the generated event was rolled up. In an alert-based notification, the cenAlarmInstanceId and cenAlertID are identical.<\/td>\n<td>c2afd3c1-d4e5-46db-84b2- 86d0d43f2056<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<h3 style=\"color: rgb(26, 26, 26); font-weight: 700\">5.2 System and Network TRAP Notifications Examples and MIB Implementation<\/h3>\n<pre><code><span>.1.3.6.1.2.1.1.3.0<span>=<\/span><span>152911250<\/span>\n<\/span><span>.1.3.6.1.6.3.1.1.4.1.0<span>=<\/span>.1.3.6.1.4.1.9.9.311.0.2\n<\/span><span>.1.3.6.1.4.1.9.9.311.1.1.2.1.2.0<span>=<\/span><span>\"1.0\"<\/span>\n<\/span><span>.1.3.6.1.4.1.9.9.311.1.1.2.1.3.0<span>=<\/span><span>1788764475<\/span>\n<\/span><span>.1.3.6.1.4.1.9.9.311.1.1.2.1.4.0<span>=<\/span><span>1788764475<\/span>\n<\/span><span>.1.3.6.1.4.1.9.9.311.1.1.2.1.5.0<span>=<\/span><span>\"0669e1d3-6981-4c6c-826c-b5fe583ae266\"<\/span>\n<\/span><span>.1.3.6.1.4.1.9.9.311.1.1.2.1.6.0<span>=<\/span><span>2<\/span>\n<\/span><span>.1.3.6.1.4.1.9.9.311.1.1.2.1.7.0<span>=<\/span><span>\"2, ACTIVE\"<\/span>\n<\/span><span>.1.3.6.1.4.1.9.9.311.1.1.2.1.8.0<span>=<\/span><span>2<\/span>\n<\/span><span>.1.3.6.1.4.1.9.9.311.1.1.2.1.9.0<span>=<\/span>-1\n<\/span><span>.1.3.6.1.4.1.9.9.311.1.1.2.1.10.0<span>=<\/span><span>\"-1, 1000\"<\/span>\n<\/span><span>.1.3.6.1.4.1.9.9.311.1.1.2.1.11.0<span>=<\/span><span>1<\/span>\n<\/span><span>.1.3.6.1.4.1.9.9.311.1.1.2.1.12.0<span>=<\/span><span>\"10.244.171.44\"<\/span>\n<\/span><span>.1.3.6.1.4.1.9.9.311.1.1.2.1.13.0<span>=<\/span><span>\"capp-infra:DLM\"<\/span>\n<\/span><span>.1.3.6.1.4.1.9.9.311.1.1.2.1.14.0<span>=<\/span><span>1<\/span>\n<\/span><span>.1.3.6.1.4.1.9.9.311.1.1.2.1.15.0<span>=<\/span><span>\"robot-dlminvmgr-7896b9d7df-n5blp\"<\/span>\n<\/span><span>.1.3.6.1.4.1.9.9.311.1.1.2.1.16.0<span>=<\/span><span>\"[Device: 10.58.234.44] [snmp]ErrorType ConnectionError,Invalid SNMP credentials or Wrong SNMP \u2026..\n<\/span><\/span><span><span>.1.3.6.1.4.1.9.9.311.1.1.2.1.17.0=2\n<\/span><\/span><span><span>.1.3.6.1.4.1.9.9.311.1.1.2.1.18.0=\"<\/span><span>2<\/span>, MAJOR<span>\"\n<\/span><\/span><span><span>.1.3.6.1.4.1.9.9.311.1.1.2.1.19.0=0\n<\/span><\/span><span><span>.1.3.6.1.4.1.9.9.311.1.1.2.1.20.0=\"<\/span>\"\n<\/span><span>.1.3.6.1.4.1.9.9.311.1.1.2.1.21.0<span>=<\/span><span>\"srcObjectDisplayName=Device &lt;no host&gt; (443d497e-986f-47ff-9cc5-75bc404358b5),hostname\u2026\u2026\n<\/span><\/span><span><span>.1.3.6.1.4.1.9.9.311.1.1.2.1.22.0=\"<\/span>Device <span>&lt;<\/span>no host<span>&gt;<\/span> <span>(<\/span>443d497e-986f-47ff-9cc5-75bc404358b5<span>)<\/span><span>\"\n<\/span><\/span><span><span>.1.3.6.1.4.1.9.9.311.1.1.2.1.23.0=\"<\/span>\"\n<\/span><span>.1.3.6.1.4.1.9.9.311.1.1.2.1.24.0<span>=<\/span><span>3<\/span>\n<\/span><span>.1.3.6.1.4.1.9.9.311.1.1.2.1.25.0<span>=<\/span><span>0<\/span>\n<\/span><span>.1.3.6.1.4.1.9.9.311.1.1.2.1.26.0<span>=<\/span><span>\"\"<\/span>\n<\/span><span>.1.3.6.1.4.1.9.9.311.1.1.2.1.27.0<span>=<\/span><span>\"\"<\/span>\n<\/span><span>.1.3.6.1.4.1.9.9.311.1.1.2.1.28.0<span>=<\/span><span>\"\"<\/span>\n<\/span><span>.1.3.6.1.4.1.9.9.311.1.1.2.1.29.0<span>=<\/span>\"bb6310d7-ca8f-48b8-bf0b-bc2f1\n<\/span><\/code><\/pre>\n<p><strong style=\"color: rgb(26, 26, 26)\">System TRAP Example<\/strong><\/p>\n<h3 style=\"color: rgb(26, 26, 26); font-weight: 700\">System and Network TRAP &#8211; MIB Implementation<\/h3>\n<div style=\"max-width: 100%\" class=\"table-responsive\">\n<table class=\"english-numbers\">\n<thead>\n<tr>\n<th>SNMP Varbind<\/th>\n<th>Event Field*1<\/th>\n<th>Varbind OID<\/th>\n<th>Description<\/th>\n<th>Examples<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>cenAlarmVersion<\/td>\n<td>&#8211;<\/td>\n<td>.1.3.6.1.4.9.9.31 1.1.1.2.1.2<\/td>\n<td>The release version of this MIB<\/td>\n<td>1.0<\/td>\n<\/tr>\n<tr>\n<td>cenAlarmTimestamp<\/td>\n<td>Timestamp<\/td>\n<td>.1.3.6.1.4.9.9.31 1.1.1.2.1.3<\/td>\n<td>The time when the alarm was raised<\/td>\n<td>1523608787<\/td>\n<\/tr>\n<tr>\n<td>cenAlarmUpdatedTimestamp<\/td>\n<td>Timestamp<\/td>\n<td>.1.3.6.1.4.9.9.31 1.1.1.2.1.4<\/td>\n<td>Last update time<\/td>\n<td>1523608788<\/td>\n<\/tr>\n<tr>\n<td>cenAlarmInstanceID<\/td>\n<td>AlarmId<\/td>\n<td>.1.3.6.1.4.9.9.31 1.1.1.2.1.5<\/td>\n<td>The Unique Alarm Instance ID<\/td>\n<td>57e3ef70-1597<\/td>\n<\/tr>\n<tr>\n<td>cenAlarmStatus<\/td>\n<td>Alarm Status<\/td>\n<td>.1.3.6.1.4.9.9.31 1.1.1.2.1.6<\/td>\n<td>The alarm status indicates the status of the alarm in integer value. 2 = ACTIVE, 3 = CLEARED<\/td>\n<td>2<\/td>\n<\/tr>\n<tr>\n<td>cenAlarmStatusDefinition<\/td>\n<td>Alarm Status Definition<\/td>\n<td>.1.3.6.1.4.9.9.31 1.1.1.2.1.7<\/td>\n<td>The short description of the status of the alarm. The string is formatted in &#8216;<integer>,<alarmstatus description=\"\">\u2019.<\/alarmstatus><\/integer><\/td>\n<td>2, ACTIVE<\/td>\n<\/tr>\n<tr>\n<td>cenAlarmType<\/td>\n<td>&#8211;<\/td>\n<td>.1.3.6.1.4.9.9.31 1.1.1.2.1.8<\/td>\n<td>\u2022 1 \u2013 unknown \u2022 2 \u2013 direct \u2022 3 \u2013 indirect \u2022 4 \u2013 mixed<\/td>\n<td>Hardcoded as 2<\/td>\n<\/tr>\n<tr>\n<td>cenAlarmCategory<\/td>\n<td>Category<\/td>\n<td>.1.3.6.1.4.9.9.31 1.1.1.2.1.9<\/td>\n<td>Not Used \u2013 Instead, use cenAlarmCategoryDefinition<\/td>\n<td>&#8211;<\/td>\n<\/tr>\n<tr>\n<td>cenAlarmCategoryDefinition<\/td>\n<td>Category Definition<\/td>\n<td>.1.3.6.1.4.9.9.31 1.1.1.2.1.10<\/td>\n<td>A short description of the event category. The string is formatted in &#8216;&lt;integer, eventCategory description&gt; Integer should not be considered<\/td>\n<td>1002 AUDIT_LOG, L2LinkAlarm, SrPolicyEvent<\/td>\n<\/tr>\n<tr>\n<td>cenAlarmServerAddressType<\/td>\n<td>Address Type<\/td>\n<td>.1.3.6.1.4.9.9.31 1.1.1.2.1.11<\/td>\n<td>The Internet address type of the CNC cluster node. 1 = IPv4, 2 = IPv6<\/td>\n<td>1<\/td>\n<\/tr>\n<tr>\n<td>cenAlarmServerAddress<\/td>\n<td>Address<\/td>\n<td>.1.3.6.1.4.9.9.31 1.1.1.2.1.12<\/td>\n<td>CNC alarm forwarding K8s pod, internal IP address<\/td>\n<td>10.244.251.122<\/td>\n<\/tr>\n<tr>\n<td>cenAlarmManagedObjectClass<\/td>\n<td>OriginAppId<\/td>\n<td>.1.3.6.1.4.9.9.31 1.1.1.2.1.13<\/td>\n<td>System: OriginAppId of the application that generated the event. Network Audit<\/td>\n<td>capp-infra Audit, Network<\/td>\n<\/tr>\n<tr>\n<td>cenAlarmManagedObjectAddressType<\/td>\n<td>Internet address type<\/td>\n<td>.1.3.6.1.4.9.9.31 1.1.1.2.1.14<\/td>\n<td>The type of Internet address by which the managed object (device) is reachable. 0 = unknown, 1 = IPv4, 2 = IPv6<\/td>\n<td>1<\/td>\n<\/tr>\n<tr>\n<td>cenAlarmManagedObjectAddress<\/td>\n<td>Service<\/td>\n<td>.1.3.6.1.4.9.9.31 1.1.1.2.1.15<\/td>\n<td>System: CNC Pod Name Network: &lt;PCE_IP&gt;-L3InterfaceAlarm Audit: Client IP address<\/td>\n<td>Check notes*1<\/td>\n<\/tr>\n<tr>\n<td>cenAlarmDescription<\/td>\n<td>Description<\/td>\n<td>.1.3.6.1.4.9.9.31 1.1.1.2.1.16<\/td>\n<td>A detailed description of the event.<\/td>\n<td>Check notes*2<\/td>\n<\/tr>\n<tr>\n<td>cenAlarmSeverity<\/td>\n<td>Severity<\/td>\n<td>.1.3.6.1.4.9.9.31 1.1.1.2.1.17<\/td>\n<td>\u2022 2 &#8211; CRITICAL \u2022 3 &#8211; MAJOR \u2022 4 &#8211; WARNING \u2022 5 &#8211; MINOR \u2022 6 &#8211; INFORMATION \u2022 7 &#8211; CLEARED<\/td>\n<td>5<\/td>\n<\/tr>\n<tr>\n<td>cenAlarmSeverityDefinition<\/td>\n<td>Severity Definition<\/td>\n<td>.1.3.6.1.4.9.9.31 1.1.1.2.1.18<\/td>\n<td>A short description of the event severity. The string is formatted in &#8216;&lt;integer, eventSeverity description&gt;<\/td>\n<td>3, MAJOR<\/td>\n<\/tr>\n<tr>\n<td>cenAlarmTriageValue<\/td>\n<td>.1.3.6.1.4.9.9.31 1.1.1.2.1.19<\/td>\n<td>Not Used<\/td>\n<td>&#8211;<\/td>\n<\/tr>\n<tr>\n<td>cenEventIDList<\/td>\n<td>.1.3.6.1.4.9.9.31 1.1.1.2.1.20<\/td>\n<td>Not Used<\/td>\n<td>&#8211;<\/td>\n<\/tr>\n<tr>\n<td>cenUserMessage1<\/td>\n<td>ObjectDescription, ObjectId<\/td>\n<td>.1.3.6.1.4.9.9.31 1.1.1.2.1.21<\/td>\n<td>Information about the event ObjectDescription, ObjectId. The string uses the format &#8216;&lt;ObjectDescription=xx, ObjectId=xx&gt;&#8217;.<\/td>\n<td>Check notes<\/td>\n<\/tr>\n<tr>\n<td>cenUserMessage2*1<\/td>\n<td>OriginServiceId<\/td>\n<td>.1.3.6.1.4.9.9.31 1.1.1.2.1.22<\/td>\n<td>System: Information about the event&#8217;s OriginServiceId (CNC Location) Network and Audit events: Empty<\/td>\n<td>Check notes<\/td>\n<\/tr>\n<tr>\n<td>cenUserMessage3<\/td>\n<td>.1.3.6.1.4.9.9.31 1.1.1.2.1.23<\/td>\n<td>Not Used<\/td>\n<td>&#8211;<\/td>\n<\/tr>\n<tr>\n<td>cenAlarmMode<\/td>\n<td>.1.3.6.1.4.9.9.31 1.1.1.2.1.24<\/td>\n<td>\u2022 1 \u2013 unknown \u2022 2 \u2013 alert \u2022 3 \u2013 event<\/td>\n<td>3<\/td>\n<\/tr>\n<tr>\n<td>cenPartitionNumber<\/td>\n<td>.1.3.6.1.4.9.9.31 1.1.1.2.1.25<\/td>\n<td>Not Used<\/td>\n<td>&#8211;<\/td>\n<\/tr>\n<tr>\n<td>cenPartitionName<\/td>\n<td>.1.3.6.1.4.9.9.31 1.1.1.2.1.26<\/td>\n<td>Not Used<\/td>\n<td>&#8211;<\/td>\n<\/tr>\n<tr>\n<td>cenCustomerIdentification<\/td>\n<td>.1.3.6.1.4.9.9.31 1.1.1.2.1.27<\/td>\n<td>Not Used<\/td>\n<td>&#8211;<\/td>\n<\/tr>\n<tr>\n<td>cenCustomerRevision<\/td>\n<td>.1.3.6.1.4.9.9.31 1.1.1.2.1.28<\/td>\n<td>Not Used<\/td>\n<td>&#8211;<\/td>\n<\/tr>\n<tr>\n<td>cenAlertID*1<\/td>\n<td>EventId<\/td>\n<td>.1.3.6.1.4.9.9.31 1.1.1.2.1.29<\/td>\n<td>Event ID of the generated event<\/td>\n<td>9f19e5a9-a64c<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<h2 style=\"color: rgb(26, 26, 26); font-weight: 700\">6. SYSLOG Notifications<\/h2>\n<p>Crosswork Network Controller also supports sending device, system, network and audit events through SYSLOG.<\/p>\n<p>SYSLOG format:<\/p>\n<pre><code><span><span>&lt;<\/span>pri<span>&gt;<\/span><span>&lt;<\/span>v<span>&gt;<\/span> <span>&lt;<\/span>stamp<span>&gt;<\/span> <span>&lt;<\/span>vip<span>&gt;<\/span> <span>&lt;<\/span>app<span>&gt;<\/span> <span>&lt;<\/span>PID<span>&gt;<\/span> <span>&lt;<\/span>Message ID<span>&gt;<\/span> <span>&lt;<\/span>Structure Data<span>&gt;<\/span> <span>&lt;<\/span>Message<span>&gt;<\/span>\n<\/span><\/code><\/pre>\n<p>As with TRAP notifications, SYSLOG setup comprises two steps:<\/p>\n<ul>\n<li>Define a SYSLOG receiver (omitted for brevity; see the <a href=\"https:\/\/www.cisco.com\/c\/en\/us\/td\/docs\/cloud-systems-management\/crosswork-infrastructure\/7-2\/AdminGuide\/b-cisco-crosswork-admin-guide-7-2\/system-settings-and-notifications-chapter-reference\/system-settings-and-notifications.html\" style=\"color: rgb(0, 102, 204)\">Crosswork Network Controller 7.2 Admin Guide<\/a> for details).<\/li>\n<li>Create a notification policy, as described above.<\/li>\n<\/ul>\n<h3 style=\"color: rgb(26, 26, 26); font-weight: 700\">6.1 Device SYSLOG Notifications Examples<\/h3>\n<pre><code><span><span># tcpdump -vni ens160 udp port 514<\/span>\n<\/span><span>Facility unknown <span>(<\/span><span>25<\/span><span>)<\/span> <span>(<\/span><span>25<\/span><span>)<\/span>, Severity alert <span>(<\/span><span>1<\/span><span>)<\/span>\n<\/span><span>Msg: <span>1<\/span> <span>2026<\/span>-09-01T12:05:40.000Z <span>10.58<\/span>.234.78 Wired Switch - e6fdba2a-2b3a-46ba-8f31-86e8fefbdd37 LINK_DOWN:10.58.238.196:If:Null0-LINK_DOWN <span>'Port '<\/span>Null0<span>' (Description: '<\/span>Not available<span>') is down on device '<\/span><span>10.58<\/span>.238.196<span>'.'<\/span>\n<\/span><\/code><\/pre>\n<p>tcpdump decodes PRI into facility and severity values.<\/p>\n<p>PRI = Facility \u00d7 8 + Severity <a href=\"https:\/\/datatracker.ietf.org\/doc\/html\/rfc5424#section-6.2.1\" style=\"color: rgb(0, 102, 204)\">RFC 5424 6.2.1<\/a><\/p>\n<p>To display PRI and version, use:<\/p>\n<pre><code><span><span># tcpdump -ni ens160 -s 0 -A 'udp port 514'<\/span>\n<\/span><span><span>&lt;<\/span><span>20<\/span><span><span>5<\/span>&gt;<\/span><span>1<\/span> <span>2026<\/span>-09-01T12:05:40.000Z <span>10.58<\/span>.234.78 Wired Switch - e6fdba2a-2b3a-46ba-8f31-86e8fefbdd37 LINK_DOWN:10.58.238.196:If:Null0-LINK_DOWN <span>'Port '<\/span>Null0<span>' (Description: '<\/span>Not available<span>') is up on device '<\/span><span>10.58<\/span>.238.196<span>'.'<\/span>\n<\/span><\/code><\/pre>\n<table class=\"english-numbers\">\n<thead>\n<tr>\n<th>Parameter<\/th>\n<th>Value<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>PRI<\/td>\n<td>205<\/td>\n<\/tr>\n<tr>\n<td>Version<\/td>\n<td>1<\/td>\n<\/tr>\n<tr>\n<td>Stamp<\/td>\n<td>2026-09-01T12:05.000Z<\/td>\n<\/tr>\n<tr>\n<td>VIP<\/td>\n<td>10.58.234.78<\/td>\n<\/tr>\n<tr>\n<td>App<\/td>\n<td>Wired Switch<\/td>\n<\/tr>\n<tr>\n<td>PID<\/td>\n<td>&#8211;<\/td>\n<\/tr>\n<tr>\n<td>Message ID<\/td>\n<td>e6fdba2a-2b3a-46ba-8f31-86e8fefbdd37<\/td>\n<\/tr>\n<tr>\n<td>Structured Data<\/td>\n<td>LINK_DOWN.58.238.196:If<\/td>\n<\/tr>\n<tr>\n<td>Message<\/td>\n<td>&#8216;Port &#8216;Null0&#8217; (Description: &#8216;Not available&#8217;) is up on device &#8216;10.58.238.196&#8217;.&#8217;<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h3 style=\"color: rgb(26, 26, 26); font-weight: 700\">6.2 System SYSLOG Notifications Examples<\/h3>\n<pre><code><span><span>&lt;<\/span><span>2<\/span><span><span>6<\/span>&gt;<\/span><span>1<\/span> <span>2026<\/span>-09-01T14:39:38.136Z <span>10.58<\/span>.234.78 Device <span>&lt;<\/span>no host<span>&gt;<\/span> <span>(<\/span>0603b4d4-511c-475d-b908-9f2697769676<span>)<\/span>-capp-infra:DLM - b8b8703a-a908-4a4b-b2af-bd46ffd93e95 RobotNodeData<span>[<\/span>0603b4d4-511c-475d-b908-9f2697769676<span>]<\/span>-1000-1000 <span>'[Device: 10.58.234.44] [snmp]ErrorType ConnectionError,Invalid SNMP credentials or Wrong SNMP connectivity details [ssh]Error 10.58.234.44: SSH2 authentication failure: SSH_MSG_USERAUTH_FAILURE;'<\/span>\n<\/span><\/code><\/pre>\n<table class=\"english-numbers\">\n<thead>\n<tr>\n<th>Parameter<\/th>\n<th>Value<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>PRI<\/td>\n<td>26<\/td>\n<\/tr>\n<tr>\n<td>Version<\/td>\n<td>1<\/td>\n<\/tr>\n<tr>\n<td>Stamp<\/td>\n<td>2026-09-01T14:39.136Z<\/td>\n<\/tr>\n<tr>\n<td>VIP<\/td>\n<td>10.58.234.78<\/td>\n<\/tr>\n<tr>\n<td>App<\/td>\n<td>Device <no host=\"\"> (0603b4d4-511c-475d-b908-9f2697769676)-capp-infra<\/no><\/td>\n<\/tr>\n<tr>\n<td>PID<\/td>\n<td>&#8211;<\/td>\n<\/tr>\n<tr>\n<td>Message ID<\/td>\n<td>b8b8703a-a908-4a4b-b2af-bd46ffd93e95<\/td>\n<\/tr>\n<tr>\n<td>Structured Data<\/td>\n<td>RobotNodeData[0603b4d4-511c-475d-b908-9f2697769676]-1000-1000<\/td>\n<\/tr>\n<tr>\n<td>Message<\/td>\n<td>&#8216;[Device: 10.58.234.44] [snmp]ErrorType ConnectionError,Invalid SNMP credentials or Wrong SNMP connectivity details [ssh]Error 10.58.234.44: SSH2 authentication failure: SSH_MSG_USERAUTH_FAILURE;&#8217;<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2 style=\"color: rgb(26, 26, 26); font-weight: 700\">7. Notification Options Matrix<\/h2>\n<table class=\"english-numbers\">\n<thead>\n<tr>\n<th>RESTCONF<\/th>\n<th>Kafka<\/th>\n<th>TRAP<\/th>\n<th>SYSLOG<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Sends device alarms<\/td>\n<td>\u2705<\/td>\n<td>\u2705<\/td>\n<td>\u2705<\/td>\n<td>\u2705<\/td>\n<\/tr>\n<tr>\n<td>Sends system alarms<\/td>\n<td>\u2705<\/td>\n<td>\u2705<\/td>\n<td>\u2705<\/td>\n<td>\u2705<\/td>\n<\/tr>\n<tr>\n<td>Also sends events<\/td>\n<td>\u274c<\/td>\n<td>\u274c<\/td>\n<td>\u2705<\/td>\n<td>\u2705<\/td>\n<\/tr>\n<tr>\n<td>Sends only device or system alarms<\/td>\n<td>\u274c*1<\/td>\n<td>\u274c*1<\/td>\n<td>\u2705<\/td>\n<td>\u2705<\/td>\n<\/tr>\n<tr>\n<td>Filters by device alarm severity<\/td>\n<td>\u2705<\/td>\n<td>\u2705<\/td>\n<td>\u2705<\/td>\n<td>\u2705<\/td>\n<\/tr>\n<tr>\n<td>Filters by device alarm name or category<\/td>\n<td>\u274c<\/td>\n<td>\u2705<\/td>\n<td>\u2705<\/td>\n<td>\u2705<\/td>\n<\/tr>\n<tr>\n<td>Filters by device groups<\/td>\n<td>\u274c*2<\/td>\n<td>\u2705<\/td>\n<td>\u2705<\/td>\n<td>\u2705<\/td>\n<\/tr>\n<tr>\n<td>Sends inventory notifications<\/td>\n<td>\u2705<\/td>\n<td>\u2705<\/td>\n<td>\u274c<\/td>\n<td>\u274c<\/td>\n<\/tr>\n<tr>\n<td>Sends PM notifications<\/td>\n<td>\u274c<\/td>\n<td>\u2705<\/td>\n<td>\u274c<\/td>\n<td>\u274c<\/td>\n<\/tr>\n<tr>\n<td>Sends audit notifications<\/td>\n<td>\u274c<\/td>\n<td>\u2705<\/td>\n<td>\u2705<\/td>\n<td>\u2705<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>*1 A workaround is available to stream device alarms only. For system alarms, a partial workaround is available for Kafka only.<\/p>\n<p>*2 The workaround is to filter by device <code>productFamily<\/code>, <code>productType<\/code>, or <code>deviceUUID<\/code>.<\/p>\n<\/div>\n<\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":"<p>Crosswork Network Controller provides a wide range of notification capabilities to integrate with external OSS systems providing those latest with real-time updates on alarms,\u2026<\/p>\n","protected":false},"author":1,"featured_media":174,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[69],"tags":[],"class_list":["post-176","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-iosxr-en-en"],"_links":{"self":[{"href":"https:\/\/www.anynet.ir\/blog\/wp-json\/wp\/v2\/posts\/176","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.anynet.ir\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.anynet.ir\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.anynet.ir\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.anynet.ir\/blog\/wp-json\/wp\/v2\/comments?post=176"}],"version-history":[{"count":1,"href":"https:\/\/www.anynet.ir\/blog\/wp-json\/wp\/v2\/posts\/176\/revisions"}],"predecessor-version":[{"id":178,"href":"https:\/\/www.anynet.ir\/blog\/wp-json\/wp\/v2\/posts\/176\/revisions\/178"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.anynet.ir\/blog\/wp-json\/wp\/v2\/media\/174"}],"wp:attachment":[{"href":"https:\/\/www.anynet.ir\/blog\/wp-json\/wp\/v2\/media?parent=176"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.anynet.ir\/blog\/wp-json\/wp\/v2\/categories?post=176"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.anynet.ir\/blog\/wp-json\/wp\/v2\/tags?post=176"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}