{1 3 6 1 4 1 9 9 362 0 2}
Descriptions may differ between sources. The primary description is shown first.
Source file: Download CISCO-PORT-STORM-CONTROL-MIB.mib
Publisher path: Mibs; 24,942 bytes
Source file: Download CISCO-PORT-STORM-CONTROL-MIB.my · Publisher's file
Copy from Netdisco; File: cisco/CISCO-PORT-STORM-CONTROL-MIB.my; 24,221 bytes
Vendor MIB copy from the Netdisco archive.
Related source files and packages:
Source file: Download CISCO-PORT-STORM-CONTROL-MIB · Publisher's file
Copy from Observium Community; File: cisco/CISCO-PORT-STORM-CONTROL-MIB; 24,221 bytes
Vendor MIB copy from the Observium Community archive. Cisco support.
Related source files and packages:
Source file: Download CISCO-PORT-STORM-CONTROL-MIB.my · Publisher's file
Publisher path: cisco/cisco-mibs/main/v2/CISCO-PORT-STORM-CONTROL-MIB.my; 24,221 bytes
Source file: Download CISCO-PORT-STORM-CONTROL-MIB.my.txt
File: cisco/CISCO-PORT-STORM-CONTROL-MIB.my.txt; 24,942 bytes
This notification is sent by the implementation when a storm event occurs on an interface with respect to a particular traffic type. cpscEventRev1 deprecates cpscEvent to make it RFC 2578 compliant. According to section 8.5 of RFC 2578, the next to last sub-identifier in the name of any newly-defined notification must have the value zero.
Status in source: unspecified.
Names: cpscEventRev1
{
"smi_kind": "TRAP-TYPE",
"definition": [
"cpscEventRev1",
"TRAP-TYPE",
"ENTERPRISE",
"ciscoPortStormControlMIB",
"VARIABLES",
"{",
"cpscStatus",
"}",
"DESCRIPTION",
"\"This notification is sent by the implementation when a storm event occurs on an interface with respect to a particular traffic type. cpscEventRev1 deprecates cpscEvent to make it RFC 2578 compliant. According to section 8.5 of RFC 2578, the next to last sub-identifier in the name of any newly-defined notification must have the value zero.\"",
"::=",
"2"
],
"syntax_tree": [
[
"objectIdentifier",
[
"ciscoPortStormControlMIB"
]
],
[
"VarTypes",
[
"cpscStatus"
]
],
[
"DESCRIPTION",
"This notification is sent by the implementation when a storm event occurs on an interface with respect to a particular traffic type. cpscEventRev1 deprecates cpscEvent to make it RFC 2578 compliant. According to section 8.5 of RFC 2578, the next to last sub-identifier in the name of any newly-defined notification must have the value zero."
],
null
]
}Module: CISCO-PORT-STORM-CONTROL-MIB
cpscEventRev1 TRAP-TYPE
-- Reverse mappable trap
ENTERPRISE ciscoPortStormControlMIB
VARIABLES {
cpscStatus }
-- Status
-- mandatory
DESCRIPTION
"This notification is sent by the implementation when
a storm event occurs on an interface with respect to
a particular traffic type.
cpscEventRev1 deprecates cpscEvent to make it RFC 2578
compliant. According to section 8.5 of RFC 2578, the next
to last sub-identifier in the name of any newly-defined
notification must have the value zero."
::= 2{'IF-MIB': ['ifIndex'], 'RFC-1212': ['OBJECT-TYPE'], 'RFC-1215': ['TRAP-TYPE'], 'CISCO-SMI': ['ciscoMgmt'], 'RFC1155-SMI': ['Counter'], 'SNMPv2-TC-v1': ['TruthValue', 'TimeStamp']}Downloaded: 2026-10-19T00:18:20.981938+00:00.
Module: CISCO-PORT-STORM-CONTROL-MIB
cpscEventRev1 TRAP-TYPE
-- Reverse mappable trap
ENTERPRISE ciscoPortStormControlMIB
VARIABLES {
cpscStatus }
-- Status
-- mandatory
DESCRIPTION
"This notification is sent by the implementation when
a storm event occurs on an interface with respect to
a particular traffic type.
cpscEventRev1 deprecates cpscEvent to make it RFC 2578
compliant. According to section 8.5 of RFC 2578, the next
to last sub-identifier in the name of any newly-defined
notification must have the value zero."
::= 2{'IF-MIB': ['ifIndex'], 'RFC-1212': ['OBJECT-TYPE'], 'RFC-1215': ['TRAP-TYPE'], 'CISCO-SMI': ['ciscoMgmt'], 'RFC1155-SMI': ['Counter'], 'SNMPv2-TC-v1': ['TruthValue', 'TimeStamp']}Archived: 2026-10-19T00:22:08.405094+00:00.
cpscEventRev1 NOTIFICATION-TYPE
OBJECTS { cpscStatus }
STATUS current
DESCRIPTION
"This notification is sent by the implementation when
a storm event occurs on an interface with respect to
a particular traffic type.
cpscEventRev1 deprecates cpscEvent to make it RFC 2578
compliant. According to section 8.5 of RFC 2578, the next
to last sub-identifier in the name of any newly-defined
notification must have the value zero."
::= { ciscoPortStormControlMIBNotifs 2 }
cpscEventRev1 NOTIFICATION-TYPE
OBJECTS { cpscStatus }
STATUS current
DESCRIPTION
"This notification is sent by the implementation when
a storm event occurs on an interface with respect to
a particular traffic type.
cpscEventRev1 deprecates cpscEvent to make it RFC 2578
compliant. According to section 8.5 of RFC 2578, the next
to last sub-identifier in the name of any newly-defined
notification must have the value zero."
::= { ciscoPortStormControlMIBNotifs 2 }
cpscEventRev1 NOTIFICATION-TYPE
OBJECTS { cpscStatus }
STATUS current
DESCRIPTION
"This notification is sent by the implementation when
a storm event occurs on an interface with respect to
a particular traffic type.
cpscEventRev1 deprecates cpscEvent to make it RFC 2578
compliant. According to section 8.5 of RFC 2578, the next
to last sub-identifier in the name of any newly-defined
notification must have the value zero."
::= { ciscoPortStormControlMIBNotifs 2 }
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.9.9.362.0.1 | cpscNotificationsPrefix | 2 | 3 |