netconfcentral logo

Notifications

Notification Abstract
adjacency-state-change This notification is sent when an ISIS adjacency moves to Up state or to Down state.
alarm-inventory-changed This notification is used to report that the list of possible alarms has changed. This can happen when for example if a new software module is installed, or a new physical card is inserted
alarm-notification This notification is used to report a state change for an alarm. The same notification is used for reporting a newly raised alarm, a cleared alarm or changing the text and/or severity of an existing alarm.
area-mismatch This notification is sent when the system receives a Hello PDU from an IS that does not share any area address. The notification generation must be throttled with at least a 5 second gap.
attempt-to-exceed-max-sequence This notification is sent when the system wraps the 32-bit sequence counter of an LSP.
authentication-failure This notification is sent when the system receives a PDU with the wrong authentication information. The notification generation must be throttled with at least a 5 second gap.
authentication-type-failure This notification is sent when the system receives a PDU with the wrong authentication type field. The notification generation must be throttled with at least a 5 second gap.
b4-address-change-limit-policy-violation Generates notifications when a B4 unsuccessfully attempts to change IPv6 address in a time shorter than the value of b4-address-change-limit. Notifications are rate-limited (notify-interval).
bfr-id-collision BFR ID received in the controlplane that caused BFR ID collision.
bfr-zero Invalid value associated with prefix
bier-te-notification This notification is sent when a condition changes in BIER TE.
bind-lne-name-failed Indicates an error in the association of an interface to an LNE. Only generated after success is initially returned when bind-lne-name is set.
bind-ni-name-failed Indicates an error in the association of an interface to an NI. Only generated after success is initially returned when bind-ni-name is set. Note: some errors may need to be reported for multiple associations, e.g., a single error may need to be reported...
certificate-expiration A notification indicating that a configured certificate is either about to expire or has already expired. When to send notifications is an implementation specific decision, but it is RECOMMENDED that a notification be sent once a month for 3 months, then...
corrupted-lsp-detected This notification is sent when we find that an LSP that was stored in memory has become corrupted.
database-overload This notification is sent when an ISIS instance overload condition changes.
defect-cleared-notification Upon defect cleared is met, this notification is sent
defect-condition-notification Upon the defect condition is met, this notification is sent
dot1agCfmFaultAlarm A MEP has a persistent defect condition. A notification (fault alarm) is sent to the management entity with the OID of the MEP that has detected the fault. Whenever a MEP has a persistent defect, it may or may not generate a Fault Alarm to warn the syste...
execution Notification event for an execution performed on a target object.
globals-notif Notification messages for Global TE.
hardware-state-change A hardware-state-change notification is generated when the value of /hardware-state/last-change changes.
hardware-state-change A hardware-state-change notification is generated when the value of /hardware/last-change changes in the operational state.
hardware-state-change A hardware-state-change notification is generated when the value of /hardware/last-change changes in the operational state.
hardware-state-oper-disabled A hardware-state-oper-disabled notification signifies that a component has transitioned into the 'disabled' state.
hardware-state-oper-disabled A hardware-state-oper-disabled notification signifies that a component has transitioned into the 'disabled' state.
hardware-state-oper-disabled A hardware-state-oper-disabled notification signifies that a component has transitioned into the 'disabled' state.
hardware-state-oper-enabled A hardware-state-oper-enabled notification signifies that a component has transitioned into the 'enabled' state.
hardware-state-oper-enabled A hardware-state-oper-enabled notification signifies that a component has transitioned into the 'enabled' state.
hardware-state-oper-enabled A hardware-state-oper-enabled notification signifies that a component has transitioned into the 'enabled' state.
id-len-mismatch This notification is sent when we receive a PDU with a different value for the System ID length. The notification generation must be throttled with at least a 5 second gap.
if-config-error This notification is sent when interface config error is detected.
if-rx-bad-packet This notification is sent when an OSPF packet that cannot be parsed is received on an OSPF interface.
if-state-change This notification is sent when an interface state change is detected.
if-state-change This notification is sent when an interface state change is detected.
interfaces-notif Notification messages for TE interfaces.
l2vpn-state-change-notification L2VPN and constituents state change notification
l3-link-event Notification event for L3 link
l3-link-event Notification event for L3 link
l3-node-event Notification event for L3 node
l3-node-event Notification event for L3 node
l3-prefix-event Notification event for L3 prefix
l3-prefix-event Notification event for L3 prefix
lag-notification Notification for BFD over LAG session state change. An implementation may rate-limit notifications, e.g. when asession is continuously changing state.
linkDown A linkDown trap signifies that the SNMP entity, acting in an agent role, has detected that the ifOperStatus object for one of its communication links is about to enter the down state from some other state (but not from the notPresent state). This other s...
linkDown object-1 object-2 object-3
linkUp A linkUp trap signifies that the SNMP entity, acting in an agent role, has detected that the ifOperStatus object for one of its communication links left the down state and transitioned into some other state (but not into the notPresent state). This other...
linkUp object-1 object-2 object-3
lsdb-approaching-overflow This notification is sent when the number of LSAs in the router's link state database has exceeded ninety percent of the ext-lsdb-limit.
lsdb-overflow This notification is sent when the number of LSAs in the router's link state database has exceeded ext-lsdb-limit.
lsp-error-detected This notification is sent when the system receives a LSP with a parse error. The notification generation must be throttled with at least a 5 second gap.
lsp-generation This notification is sent when a LSP is regenerated. The notification generation must be throttled with at least a 5 second gap.
lsp-received This notification is sent when a LSP is received. The notification generation must be throttled with at least a 5 second gap.
lsp-too-large This notification is sent when we attempt to propagate an LSP that is larger than the dataLinkBlockSize for the circuit. The notification generation must be throttled with at least a 5 second gap.
max-area-addresses-mismatch This notification is sent when we receive a PDU with a different value for the Maximum Area Addresses. The notification generation must be throttled with at least a 5 second gap.
mpls-ldp-fec-event Notification event for a change of FEC status.
mpls-ldp-hello-adjacency-event Notification event for a change of LDP adjacency operational status.
mpls-ldp-peer-event Notification event for a change of LDP peer operational status.
mpls-mldp-fec-event Notification event for a change of FEC status.
mpls-notification Notification for BFD over MPLS FEC session state change. An implementation may rate-limit notifications, e.g. when asession is continuously changing state.
mpls-te-notification Notification for BFD over MPLS-TE session state change. An implementation may rate-limit notifications, e.g. when asession is continuously changing state.
multihop-notification Notification for BFD multi-hop session state change. An implementation may rate-limit notifications, e.g. when asession is continuously changing state.
nat-instance-event Notifications must be generated when notify-addresses-usage and/or notify-ports-usage threshold are reached.
nat-pool-event Notifications must be generated when the defined high/low threshold is reached. Related configuration parameters must be provided to trigger the notifications.
nbr-restart-helper-status-change This notification is sent when a neighbor restart helper status change is detected.
nbr-state-change This notification is sent when neighbor state change is detected.
netconf-capability-change Generated when the NETCONF server detects that the server capabilities have changed. Indicates which capabilities have been added, deleted, and/or modified. The manner in which a server capability is changed is outside the scope of this document.
netconf-config-change Generated when the NETCONF server detects that the <running> or <startup> configuration datastore has been changed by a management session. The notification summarizes the edits that have been detected. The server MAY choose to also generate this notific...
netconf-confirmed-commit Generated when a NETCONF server detects that a confirmed-commit event has occurred. Indicates the event and the current state of the confirmed-commit procedure in progress.
netconf-scheduled-message Indicates that a scheduled message was received.
netconf-session-end Generated when a NETCONF server detects that a NETCONF session has terminated. A server MAY optionally generate this event for non-NETCONF management sessions. Indicates the identity of the user that owned the session, and why the session was terminated.
netconf-session-start Generated when a NETCONF server detects that a NETCONF session has started. A server MAY generate this event for non-NETCONF management sessions. Indicates the identity of the user that started the session.
nexthop-resolution-status-change Nexthop resolution status (resolved/unresolved) notification.
non-threshold-event This notification is sent when a local or remote non-threshold crossing event is detected.
notificationComplete This notification is sent to signal the end of a notification subscription. It is sent in the case that stopTime was specified during the creation of the subscription..
notifications dhcpv6 notification module
nssa-translator-status-change This notification is sent when there is a change in the router's role in translating OSPF NSSA LSAs to OSPF AS-External LSAs.
operator-action This notification is used to report that an operator acted upon an alarm.
opt-if-och-central-frequency-change A change of Central Frequency has been detected.
opt-if-och-min-tca A min output TCA notification.
opt-if-och-mode-change A change of Mode Template has been detected.
own-lsp-purge This notification is sent when the system receives a PDU with its own system ID and zero age.
pcep-session-down This notification is sent when the value of '/pcep/peers/peer/sessions/session/state' leaves the 'session-up' state.
pcep-session-local-overload This notification is sent when the local PCEP entity enters overload state for a peer.
pcep-session-local-overload-clear This notification is sent when the local PCEP entity leaves overload state for a peer.
pcep-session-peer-overload This notification is sent when a peer enters overload state.
pcep-session-peer-overload-clear This notification is sent when a peer leaves overload state.
pcep-session-up This notification is sent when the value of '/pcep/peers/peer/sessions/session/state' enters the 'session-up' state.
pim-interface-event Notification event for interface.
pim-interface-event Notification event for interface.
pim-neighbor-event Notification event for neighbor.
pim-neighbor-event Notification event for neighbor.
pim-rp-event Notification event for RP.
pim-rp-event Notification event for RP.
pim-rp-event Notification event for RP.
poe-port-notification Port event notification when the notification switch is on.
poe-power-notification power event notification when the notification switch is on.
protocols-supported-mismatch This notification is sent when the system receives a non pseudonode LSP that has no matching protocol supported. The notification generation must be throttled with at least a 5 second gap.
push-change-update This notification contains an on-change push update. This notification shall only be sent to the receivers of a subscription; it does not constitute a general-purpose notification.
push-update This notification contains a push update, containing data subscribed to via a subscription. This notification is sent for periodic updates, for a periodic subscription. It can also be used for synchronization updates of an on-change subscription. This no...
rejected-adjacency This notification is sent when the system receives a Hello PDU from an IS but does not establish an adjacency for some reason. The notification generation must be throttled with at least a 5 second gap.
replay-completed This notification is sent to indicate that all of the replay notifications have been sent. It must not be sent for any other reason.
replayComplete This notification is sent to signal the end of a replay portion of a subscription.
restart-status-change This notification is sent when the graceful restart state for the router has changed.
route-change Route change notification.
sadb_acquire A IPsec SA is required
sadb_bad-spi .....
sadb_expire .....
segment-routing-global-sid-collision This notification is sent when a new mapping is learned , containing mapping where the SID is already used. The notification generation must be throttled with at least a 5 second gap.
segment-routing-global-srgb-collision This notification is sent when received SRGB blocks from a router conflict.
segment-routing-index-out-of-range This notification is sent when a binding is received, containing a segment index which is out of the local configured ranges. The notification generation must be throttled with at least a 5 second gap.
sequence-number-skipped This notification is sent when the system receives a PDU with its own system ID and different contents. The system has to reissue the LSP with a higher sequence number.
singlehop-notification Notification for BFD single-hop session state change. An implementation may rate-limit notifications, e.g. when asession is continuously changing state.
softwire-algorithm-instance-event Notifications for MAP-E or MAP-T.
softwire-br-event Notifications for BR.
softwire-ce-event CE notification
spdb_expire A SPD entry has expired
srv6-locator-status-event Notification event for a change of SRv6 locator operational status.
srv6-sid-collision-event Notification event for an SRv6 SID collision - i.e., attempt to bind an already bound SID to a new context
sub-domain-id-collision Sub domain ID received in the controlplane that caused Sub domain ID collision
subscription-completed This notification is sent to indicate that a subscription has finished passing event records.
subscription-modified This notification indicates that a subscription has been modified. Notification messages sent from this point on will conform to the modified terms of the subscription. For completeness, this state change notification includes both modified and non-m...
subscription-resumed This notification indicates that a subscription that had previously been suspended has resumed. Notifications will once again be sent.
subscription-started This notification indicates that a subscription has started and notifications are beginning to be sent. This notification shall only be sent to receivers of a subscription; it does not constitute a general-purpose notification.
subscription-suspended This notification indicates that a suspension of the subscription by the publisher has occurred. No further notifications will be sent until the subscription resumes. This notification shall only be sent to receivers of a subscription; it does not consti...
subscription-terminated This notification indicates that a subscription has been terminated.
sysCapabilityChange Generated when a <capability> is added or deleted.
sysConfigChange Generated when the <running> configuration is changed.
sysConfirmedCommit Generated when a confirmed-commit event occurs.
sysSessionEnd Generated when a management session is terminated.
sysSessionStart Generated when a new management session is started.
sysStartup Generated when the system restarts. Used for logging purposes, since no sessions are actually active when the system restarts.
termination-point-event Notification event for L3 termination point
termination-point-event Notification event for L3 termination point
threshold-event This notification is sent when a local or remote threshold crossing event is detected.
toastDone Indicates that the toast in progress has completed.
tunnels-notif Notification messages for TE tunnels.
version-skew This notification is sent when the system receives a PDU with a different protocol version number. The notification generation must be throttled with at least a 5 second gap.
vrrp-new-master-event Notification event for a change of VRRP new master.
vrrp-protocol-error-event Notification event for a VRRP protocol error.
vrrp-virtual-router-error-event Notification event for an error happened on a virtual router.
yang-library-change Generated when the set of modules and submodules supported by the server has changed.
yang-library-change Generated when the set of modules and submodules supported by the server has changed.
yang-library-change Generated when the set of modules and submodules supported by the server has changed.
yang-library-update Generated when any YANG library information on the server has changed.