notificationLimit

PEAKFLOW-SP-MIB · .1.3.6.1.4.1.9694.1.4.3.0.17
MIB view Table view

Object

notification obsolete 
Too many alerts have been generated by this Peakflow
SP leader.  Alerts will be temporarily suppressed.
For more information about alerts that are being generated,
please go to the Alerts page in the leader's UI.

Context

MIB
PEAKFLOW-SP-MIB
OID
.1.3.6.1.4.1.9694.1.4.3.0.17
Type
notification
Status
obsolete
Parent
peakflowSPTrapsEnumerate
Siblings
61

Syntax

No syntax metadata recorded.

Values & Constraints

No enumerated values or constraints recorded.

Related Objects

Sibling Objects
ObjectTypeSyntaxOID
flowDown
Flow data has not been received from a Flow transmitting router
notification-.1.3.6.1.4.1.9694.1.4.3.0.1
bgpInstability
The BGP session with this router is exhibiting instability
notification-.1.3.6.1.4.1.9694.1.4.3.0.10
bgpInstabilityDone
The BGP instability associated with this router has ended
notification-.1.3.6.1.4.1.9694.1.4.3.0.11
bgpTrap
A BGP event matching this trap definition has occurred.
notification-.1.3.6.1.4.1.9694.1.4.3.0.12
interfaceUsage
The interface exceeded the configured traffic rate threshold.
notification-.1.3.6.1.4.1.9694.1.4.3.0.13
interfaceUsageDone
The interface is now within configured traffic thresholds
notification-.1.3.6.1.4.1.9694.1.4.3.0.14
autoclassifyStart obsolete
Autoclassification started on this Peakflow SP leader.
notification-.1.3.6.1.4.1.9694.1.4.3.0.15
configChange
Configuration updated from this Peakflow SP leader.
notification-.1.3.6.1.4.1.9694.1.4.3.0.16
reportDone obsolete
The indicated report is finished and available for viewing at the listed URL.
notification-.1.3.6.1.4.1.9694.1.4.3.0.18
bgpHijack
A BGP announcement was seen for a prefix that is part of the configured local address space.
notification-.1.3.6.1.4.1.9694.1.4.3.0.19
flowUp
Flow data has resumed from a router which previously was not forwarding Flow data
notification-.1.3.6.1.4.1.9694.1.4.3.0.2
managedObjectUsage
The managed object exceeded the configured traffic rate threshold.
notification-.1.3.6.1.4.1.9694.1.4.3.0.20
managedObjectUsageDone
The manged object is no longer exceeding the traffic rate threshold.
notification-.1.3.6.1.4.1.9694.1.4.3.0.21
hardwareFailure
A hardware failure has been detected on an SP device.
notification-.1.3.6.1.4.1.9694.1.4.3.0.22
hardwareFailureDone
A hardware failure is no longer detected on an SP device.
notification-.1.3.6.1.4.1.9694.1.4.3.0.23
fingerprintFeedback
Feedback received regarding a shared fingerprint.
notification-.1.3.6.1.4.1.9694.1.4.3.0.24
fingerprintReceive
A shared fingerprint was received.
notification-.1.3.6.1.4.1.9694.1.4.3.0.25
dnsBaseline
An excessive number of queries for a domain name detected.
notification-.1.3.6.1.4.1.9694.1.4.3.0.26
dnsBaselineDone
Query count for domain name has returned to normal levels.
notification-.1.3.6.1.4.1.9694.1.4.3.0.27
alertScript
Alert script has been executed
notification-.1.3.6.1.4.1.9694.1.4.3.0.28
mitigationDone
Mitigation has completed
notification-.1.3.6.1.4.1.9694.1.4.3.0.29
snmpDown
SNMP requests are not being answered by the router
notification-.1.3.6.1.4.1.9694.1.4.3.0.3
mitigationTMSStart deprecated
TMS Mitigation has started
notification-.1.3.6.1.4.1.9694.1.4.3.0.30
mitigationThirdPartyStart
Third Party Mitigation has started
notification-.1.3.6.1.4.1.9694.1.4.3.0.31
mitigationBlackholeStart
Blackhole Mitigation has started
notification-.1.3.6.1.4.1.9694.1.4.3.0.32
mitigationFlowspecStart
Flowspec Mitigation has started
notification-.1.3.6.1.4.1.9694.1.4.3.0.33
spcommFailure
An SP internal communication failure has occurred.
notification-.1.3.6.1.4.1.9694.1.4.3.0.34
spcommFailureDone
An SP internal communication failure has ended.
notification-.1.3.6.1.4.1.9694.1.4.3.0.35
greDown
The GRE tunnel is down
notification-.1.3.6.1.4.1.9694.1.4.3.0.36
greDownDone
The GRE tunnel is back up
notification-.1.3.6.1.4.1.9694.1.4.3.0.37
deviceSystemError
An SP device system error alert has started.
notification-.1.3.6.1.4.1.9694.1.4.3.0.38
deviceSystemErrorDone
An SP device system error alert has ended.
notification-.1.3.6.1.4.1.9694.1.4.3.0.39
snmpUp
SNMP requests are again being answered by the router
notification-.1.3.6.1.4.1.9694.1.4.3.0.4
fingerprintUsage
The fingerprint exceeded the configured traffic rate threshold.
notification-.1.3.6.1.4.1.9694.1.4.3.0.40
fingerprintUsageDone
The fingerprint is no longer exceeding the traffic rate threshold.
notification-.1.3.6.1.4.1.9694.1.4.3.0.41
serviceUsage
The service exceeded the configured traffic rate threshold.
notification-.1.3.6.1.4.1.9694.1.4.3.0.42
serviceUsageDone
The service is no longer exceeding the traffic rate threshold.
notification-.1.3.6.1.4.1.9694.1.4.3.0.43
dosNetworkProfiledAlert
The managed object exceeded network and/or country baseline thresholds.
notification-.1.3.6.1.4.1.9694.1.4.3.0.44
dosNetworkProfiledAlertDone
The managed object is no longer exceeding the network and/or country baseline thresholds.
notification-.1.3.6.1.4.1.9694.1.4.3.0.45
dosHostDetectionAlert
A Host alert was started after one or more signatures exceeded their thresholds.
notification-.1.3.6.1.4.1.9694.1.4.3.0.46
dosHostDetectionAlertDone
The Host alert ended and is no longer exceeding signature thresholds.
notification-.1.3.6.1.4.1.9694.1.4.3.0.47
routingFailover
A routing failover event occurred on a collector.
notification-.1.3.6.1.4.1.9694.1.4.3.0.48
routingFailoverInterfaceDownAlert
One or more interfaces involved in routing failover for a collector are down. The spRoutingFailoverInterfaces object documents the list of interfaces that are down.
notification-.1.3.6.1.4.1.9694.1.4.3.0.49
bgpDown
The BGP session with the router has transitioned down
notification-.1.3.6.1.4.1.9694.1.4.3.0.5
routingFailoverInterfaceDownAlertDone
A previously started alert for down routing failover interfaces has finished.
notification-.1.3.6.1.4.1.9694.1.4.3.0.50
trafficAutoMitigation
Traffic has been seen by a TMS for a Managed Object which has been configured for traffic-based auto-mitigation.
notification-.1.3.6.1.4.1.9694.1.4.3.0.51
cloudSignalingMitigationRequest
A cloud signaling mitigation request has been seen and an alert created.
notification-.1.3.6.1.4.1.9694.1.4.3.0.52
licenseError
An SP Deployment License error alert has started.
notification-.1.3.6.1.4.1.9694.1.4.3.0.53
licenseErrorDone
An SP Deployment License error alert has ended.
notification-.1.3.6.1.4.1.9694.1.4.3.0.54
cloudSignalingFault
A cloud signaling fault was detected.
notification-.1.3.6.1.4.1.9694.1.4.3.0.55
cloudSignalingFaultDone
A cloud signaling fault is no longer detected.
notification-.1.3.6.1.4.1.9694.1.4.3.0.56
mitigationTMSStartV2
TMS Mitigation has started
notification-.1.3.6.1.4.1.9694.1.4.3.0.57
aifTemplatesUpdated
AIF Templates have been updated
notification-.1.3.6.1.4.1.9694.1.4.3.0.58
smartThresholdAlert
A Smart Threshold alert was started after one or more signatures exceeded their thresholds.
notification-.1.3.6.1.4.1.9694.1.4.3.0.59
bgpUp
The BGP session with the router has transitioned up
notification-.1.3.6.1.4.1.9694.1.4.3.0.6
smartThresholdAlertDone
The Smart Threshold alert ended and is no longer exceeding signature thresholds.
notification-.1.3.6.1.4.1.9694.1.4.3.0.60
mitigationOrchestrationAlert
A mitigation was moved by Mitigation Orchestration.
notification-.1.3.6.1.4.1.9694.1.4.3.0.61
sightlineSignalingAlert
A Sightline Signaling Request was received.
notification-.1.3.6.1.4.1.9694.1.4.3.0.62
collectorDown
The SP device is down. Heartbeats are missing.
notification-.1.3.6.1.4.1.9694.1.4.3.0.7
collectorUp
The SP device is up. Heartbeats have resumed.
notification-.1.3.6.1.4.1.9694.1.4.3.0.8
collectorStart obsolete
The SP device is started. Heartbeats have been received.
notification-.1.3.6.1.4.1.9694.1.4.3.0.9
Notification Objects
ObjectTypeSyntaxOID
spAlertID
The id of the alert
scalarSNMPv2-SMIUnsigned32.1.3.6.1.4.1.9694.1.4.1.18
spCollector
SP Device name
scalarOctetString.1.3.6.1.4.1.9694.1.4.1.1