Reference record for OID 1.3.6.1.4.1.9.9.693
- Parent
- 1.3.6.1.4.1.9.9 (ciscoMgmt)
- Node code
- 693
- Node name
- ciscoServiceControlAttackMIB
- Numeric OID
- 1.3.6.1.4.1.9.9.693
- Type
- OBJECT IDENTIFIER
- ASN.1 notation
-
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) cisco(9) ciscoMgmt(9) ciscoServiceControlAttackMIB(693)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) cisco(9) ciscoMgmt(9) ciscoServiceControlAttackMIB(693)}
- {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) cisco(9) ciscoMgmt(9) ciscoServiceControlAttackMIB(693)}
- {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) cisco(9) ciscoMgmt(9) ciscoServiceControlAttackMIB(693)}
- {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) cisco(9) ciscoMgmt(9) ciscoServiceControlAttackMIB(693)}
- {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) cisco(9) ciscoMgmt(9) ciscoServiceControlAttackMIB(693)}
- IRI notation
- /iso/identified-organization/dod/internet/private/enterprise/cisco/ciscoMgmt/ciscoServiceControlAttackMIB
- /iso/identified-organization/dod/internet/private/enterprises/cisco/ciscoMgmt/ciscoServiceControlAttackMIB
- /iso/org/dod/internet/private/enterprise/cisco/ciscoMgmt/ciscoServiceControlAttackMIB
- /iso/org/dod/internet/private/enterprises/cisco/ciscoMgmt/ciscoServiceControlAttackMIB
- /iso/iso-identified-organization/dod/internet/private/enterprise/cisco/ciscoMgmt/ciscoServiceControlAttackMIB
- /iso/iso-identified-organization/dod/internet/private/enterprises/cisco/ciscoMgmt/ciscoServiceControlAttackMIB
- IRI from OID Repository
- /ISO/Identified-Organization/6/1/4/1/9/9/693
Descriptions may differ between sources. The primary description is shown first.
Primary description: Circitor
This MIB provides data related to different types of
attacks detected by a service control entity.
A service control entity is a network device which monitors and
controls traffic. The service control entity is used as a
platform for different service control applications which may
perform monitoring operations beyond packet counting and delve
deeper into the contents of network traffic. It provides
programmable stateful inspection of bidirectional
traffic flows and maps these flows with user/subscriber
ownership.
An attack is a malicious network activity with certain traffic
characteristics and which is targeted on a certain network
entity. An attack can be identified by its type, direction,
source address, destination address and ports.
Once an attack is detected, an attack filter is activated based
on the type of the attack and corresponding actions are taken
in
the monitored network - this is referred to as attack start.
For example the attack filter can drop the attacking traffic.
When the attack detector identifies that the attack
characteristics are no longer exist, it ends the mitigation
action - what is referred to as attack end. The attack
mitigation action is also referred to as attack filtering in
this MIB.
The time duration of attack filtering between attack start to
attack end along with the direction (upstream, downstream) is
also maintained by the service control entity. Attack
filtering
can be applied from the subscriber side to the network side, in
the upstream direction. The downstream attack filtering is
done
from the network side to the subscriber side.
This MIB also defines notifications generated by the service
control entity when an attack is detected on a monitored
network.
Parsed from file CISCO-SERVICE-CONTROL-ATTACK-MIB.mib
Module: CISCO-SERVICE-CONTROL-ATTACK-MIB
attacks detected by a service control entity.
A service control entity is a network device which monitors and
controls traffic. The service control entity is used as a
platform for different service control applications which may
perform monitoring operations beyond packet counting and delve
deeper into the contents of network traffic. It provides
programmable stateful inspection of bidirectional
traffic flows and maps these flows with user/subscriber
ownership.
An attack is a malicious network activity with certain traffic
characteristics and which is targeted on a certain network
entity. An attack can be identified by its type, direction,
source address, destination address and ports.
Once an attack is detected, an attack filter is activated based
on the type of the attack and corresponding actions are taken
in
the monitored network - this is referred to as attack start.
For example the attack filter can drop the attacking traffic.
When the attack detector identifies that the attack
characteristics are no longer exist, it ends the mitigation
action - what is referred to as attack end. The attack
mitigation action is also referred to as attack filtering in
this MIB.
The time duration of attack filtering between attack start to
attack end along with the direction (upstream, downstream) is
also maintained by the service control entity. Attack
filtering
can be applied from the subscriber side to the network side, in
the upstream direction. The downstream attack filtering is
done
from the network side to the subscriber side.
This MIB also defines notifications generated by the service
control entity when an attack is detected on a monitored
network.
Parsed from file CISCO-SERVICE-CONTROL-ATTACK-MIB.mib
Module: CISCO-SERVICE-CONTROL-ATTACK-MIB
Alternative description: Cisco
This MIB provides data related to different types of
attacks detected by a service control entity.
A service control entity is a network device which monitors and
controls traffic. The service control entity is used as a
platform for different service control applications which may
perform monitoring operations beyond packet counting and delve
deeper into the contents of network traffic. It provides
programmable stateful inspection of bidirectional
traffic flows and maps these flows with user/subscriber
ownership.
An attack is a malicious network activity with certain traffic
characteristics and which is targeted on a certain network
entity. An attack can be identified by its type, direction,
source address, destination address and ports.
Once an attack is detected, an attack filter is activated based
on the type of the attack and corresponding actions are taken
in
the monitored network - this is referred to as attack start.
For example the attack filter can drop the attacking traffic.
When the attack detector identifies that the attack
characteristics are no longer exist, it ends the mitigation
action - what is referred to as attack end. The attack
mitigation action is also referred to as attack filtering in
this MIB.
The time duration of attack filtering between attack start to
attack end along with the direction (upstream, downstream) is
also maintained by the service control entity. Attack
filtering
can be applied from the subscriber side to the network side, in
the upstream direction. The downstream attack filtering is
done
from the network side to the subscriber side.
This MIB also defines notifications generated by the service
control entity when an attack is detected on a monitored
network.
attacks detected by a service control entity.
A service control entity is a network device which monitors and
controls traffic. The service control entity is used as a
platform for different service control applications which may
perform monitoring operations beyond packet counting and delve
deeper into the contents of network traffic. It provides
programmable stateful inspection of bidirectional
traffic flows and maps these flows with user/subscriber
ownership.
An attack is a malicious network activity with certain traffic
characteristics and which is targeted on a certain network
entity. An attack can be identified by its type, direction,
source address, destination address and ports.
Once an attack is detected, an attack filter is activated based
on the type of the attack and corresponding actions are taken
in
the monitored network - this is referred to as attack start.
For example the attack filter can drop the attacking traffic.
When the attack detector identifies that the attack
characteristics are no longer exist, it ends the mitigation
action - what is referred to as attack end. The attack
mitigation action is also referred to as attack filtering in
this MIB.
The time duration of attack filtering between attack start to
attack end along with the direction (upstream, downstream) is
also maintained by the service control entity. Attack
filtering
can be applied from the subscriber side to the network side, in
the upstream direction. The downstream attack filtering is
done
from the network side to the subscriber side.
This MIB also defines notifications generated by the service
control entity when an attack is detected on a monitored
network.
Alternative description: MIBdepot
This MIB provides data related to different types of
attacks detected by a service control entity.
A service control entity is a network device which monitors and
controls traffic. The service control entity is used as a
platform for different service control applications which may
perform monitoring operations beyond packet counting and delve
deeper into the contents of network traffic. It provides
programmable stateful inspection of bidirectional
traffic flows and maps these flows with user/subscriber
ownership.
An attack is a malicious network activity with certain traffic
characteristics and which is targeted on a certain network
entity. An attack can be identified by its type, direction,
source address, destination address and ports.
Once an attack is detected, an attack filter is activated based
on the type of the attack and corresponding actions are taken
in
the monitored network - this is referred to as attack start.
For example the attack filter can drop the attacking traffic.
When the attack detector identifies that the attack
characteristics are no longer exist, it ends the mitigation
action - what is referred to as attack end. The attack
mitigation action is also referred to as attack filtering in
this MIB.
The time duration of attack filtering between attack start to
attack end along with the direction (upstream, downstream) is
also maintained by the service control entity. Attack
filtering
can be applied from the subscriber side to the network side, in
the upstream direction. The downstream attack filtering is
done
from the network side to the subscriber side.
This MIB also defines notifications generated by the service
control entity when an attack is detected on a monitored
network.
Parsed from file CISCO-SERVICE-CONTROL-ATTACK-MIB.my.txt
Company: None
Module: CISCO-SERVICE-CONTROL-ATTACK-MIB
attacks detected by a service control entity.
A service control entity is a network device which monitors and
controls traffic. The service control entity is used as a
platform for different service control applications which may
perform monitoring operations beyond packet counting and delve
deeper into the contents of network traffic. It provides
programmable stateful inspection of bidirectional
traffic flows and maps these flows with user/subscriber
ownership.
An attack is a malicious network activity with certain traffic
characteristics and which is targeted on a certain network
entity. An attack can be identified by its type, direction,
source address, destination address and ports.
Once an attack is detected, an attack filter is activated based
on the type of the attack and corresponding actions are taken
in
the monitored network - this is referred to as attack start.
For example the attack filter can drop the attacking traffic.
When the attack detector identifies that the attack
characteristics are no longer exist, it ends the mitigation
action - what is referred to as attack end. The attack
mitigation action is also referred to as attack filtering in
this MIB.
The time duration of attack filtering between attack start to
attack end along with the direction (upstream, downstream) is
also maintained by the service control entity. Attack
filtering
can be applied from the subscriber side to the network side, in
the upstream direction. The downstream attack filtering is
done
from the network side to the subscriber side.
This MIB also defines notifications generated by the service
control entity when an attack is detected on a monitored
network.
Parsed from file CISCO-SERVICE-CONTROL-ATTACK-MIB.my.txt
Company: None
Module: CISCO-SERVICE-CONTROL-ATTACK-MIB
Information from Circitor
ciscoServiceControlAttackMIB MODULE-IDENTITY
LAST-UPDATED "200905050000Z"
ORGANIZATION "Cisco Systems, Inc."
CONTACT-INFO
"Cisco Systems
Customer Service
Postal: 170 W Tasman Drive
San Jose, CA 95134
USA
Tel: +1 800 553-NETS
E-mail: cs-excelsior-dev@cisco.com"
DESCRIPTION
"This MIB provides data related to different types of
attacks detected by a service control entity.
A service control entity is a network device which monitors and
controls traffic. The service control entity is used as a
platform for different service control applications which may
perform monitoring operations beyond packet counting and delve
deeper into the contents of network traffic. It provides
programmable stateful inspection of bidirectional
traffic flows and maps these flows with user/subscriber
ownership.
An attack is a malicious network activity with certain traffic
characteristics and which is targeted on a certain network
entity. An attack can be identified by its type, direction,
source address, destination address and ports.
Once an attack is detected, an attack filter is activated based
on the type of the attack and corresponding actions are taken
in
the monitored network - this is referred to as attack start.
For example the attack filter can drop the attacking traffic.
When the attack detector identifies that the attack
characteristics are no longer exist, it ends the mitigation
action - what is referred to as attack end. The attack
mitigation action is also referred to as attack filtering in
this MIB.
The time duration of attack filtering between attack start to
attack end along with the direction (upstream, downstream) is
also maintained by the service control entity. Attack
filtering
can be applied from the subscriber side to the network side, in
the upstream direction. The downstream attack filtering is
done
from the network side to the subscriber side.
This MIB also defines notifications generated by the service
control entity when an attack is detected on a monitored
network."
REVISION "200905050000Z"
DESCRIPTION
"Initial version of this MIB module."
::= { ciscoMgmt 693 }
Information from Cisco SMIv1
ciscoServiceControlAttackMIB OBJECT IDENTIFIER ::= { ciscoMgmt 693 }
Information from OID Repository
Information from MIBdepot
ciscoServiceControlAttackMIB MODULE-IDENTITY
LAST-UPDATED "200905050000Z"
ORGANIZATION "Cisco Systems, Inc."
CONTACT-INFO
"Cisco Systems
Customer Service
Postal: 170 W Tasman Drive
San Jose, CA 95134
USA
Tel: +1 800 553-NETS
E-mail: cs-excelsior-dev@cisco.com"
DESCRIPTION
"This MIB provides data related to different types of
attacks detected by a service control entity.
A service control entity is a network device which monitors and
controls traffic. The service control entity is used as a
platform for different service control applications which may
perform monitoring operations beyond packet counting and delve
deeper into the contents of network traffic. It provides
programmable stateful inspection of bidirectional
traffic flows and maps these flows with user/subscriber
ownership.
An attack is a malicious network activity with certain traffic
characteristics and which is targeted on a certain network
entity. An attack can be identified by its type, direction,
source address, destination address and ports.
Once an attack is detected, an attack filter is activated based
on the type of the attack and corresponding actions are taken
in
the monitored network - this is referred to as attack start.
For example the attack filter can drop the attacking traffic.
When the attack detector identifies that the attack
characteristics are no longer exist, it ends the mitigation
action - what is referred to as attack end. The attack
mitigation action is also referred to as attack filtering in
this MIB.
The time duration of attack filtering between attack start to
attack end along with the direction (upstream, downstream) is
also maintained by the service control entity. Attack
filtering
can be applied from the subscriber side to the network side, in
the upstream direction. The downstream attack filtering is
done
from the network side to the subscriber side.
This MIB also defines notifications generated by the service
control entity when an attack is detected on a monitored
network."
REVISION "200905050000Z"
DESCRIPTION
"Initial version of this MIB module."
::= { ciscoMgmt 693 }
Information from Cisco
ciscoServiceControlAttackMIB MODULE-IDENTITY
LAST-UPDATED "201308160000Z"
ORGANIZATION "Cisco Systems, Inc."
CONTACT-INFO
"Cisco Systems
Customer Service
Postal: 170 W Tasman Drive
San Jose, CA 95134
USA
Tel: +1 800 553-NETS
E-mail: cs-excelsior-dev@cisco.com"
DESCRIPTION
"This MIB provides data related to different types of
attacks detected by a service control entity.
A service control entity is a network device which monitors and
controls traffic. The service control entity is used as a
platform for different service control applications which may
perform monitoring operations beyond packet counting and delve
deeper into the contents of network traffic. It provides
programmable stateful inspection of bidirectional
traffic flows and maps these flows with user/subscriber
ownership.
An attack is a malicious network activity with certain traffic
characteristics and which is targeted on a certain network
entity. An attack can be identified by its type, direction,
source address, destination address and ports.
Once an attack is detected, an attack filter is activated based
on the type of the attack and corresponding actions are taken
in
the monitored network - this is referred to as attack start.
For example the attack filter can drop the attacking traffic.
When the attack detector identifies that the attack
characteristics are no longer exist, it ends the mitigation
action - what is referred to as attack end. The attack
mitigation action is also referred to as attack filtering in
this MIB.
The time duration of attack filtering between attack start to
attack end along with the direction (upstream, downstream) is
also maintained by the service control entity. Attack
filtering
can be applied from the subscriber side to the network side, in
the upstream direction. The downstream attack filtering is
done
from the network side to the subscriber side.
This MIB also defines notifications generated by the service
control entity when an attack is detected on a monitored
network."
REVISION "201308160000Z"
DESCRIPTION
"Updates to support traps for global attacks. For this
1. A new trap is introduced: cscaGlobalAttackFilterChange.
2. A new object is introduced: cscaGlobalAtackType to describe
the type of global attack.
3. A 3 groups are introduced:
a. cscaMIBNotificationGroupRev1, deprecating
cscaMIBNotificationGroup.
b. cscaFilterObjectGroupRev1, deprecating
cscaFilterObjectGroup.
c. cscaMIBNotifControlGroupRev1, deprecating
cscaMIBNotifControlGroup
4. A new compliance is introduced:
cscaMIBComplianceRev1, deprecating cscaMIBCompliance."
REVISION "200905050000Z"
DESCRIPTION
"Initial version of this MIB module."
::= { ciscoMgmt 693 }
First Registration Authority (inferred from ancestor 1.3.6.1.4.1.9)
Current Registration Authority (inferred from ancestor 1.3.6.1.4.1.9)
Direct children (3)
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.9.9.693.0 | ciscoServiceControlAttackMIBNotifs | 2 | 2 | |
| 1.3.6.1.4.1.9.9.693.1 | ciscoServiceControlAttackMIBObjects | 3 | 38 | |
| 1.3.6.1.4.1.9.9.693.2 | ciscoServiceControlAttackMIBConform | 2 | 12 |
Siblings (645)
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.9.9.809 | ciscoWebExMeetingMIB | 3 | 58 | Cisco WebEx Collaboration Host is a software-only system, with hardware independence a key goal. To that end, it will be designed … |
| 1.3.6.1.4.1.9.9.810 | ciscoOtvMIB | 3 | 129 | This MIB module is for configuration & statistic query of Overlay Transport Virtualization (OTV) functionality on Cisco routers a… |
| 1.3.6.1.4.1.9.9.811 | ciscoVlanIfTableRelationshipMIB | 1 | 12 | |
| 1.3.6.1.4.1.9.9.812 | ciscoLptsMIB | 3 | 22 | The MIB module for Local Packet Transport Services(LPTS) related information like the flows and the policer values related to var… |
| 1.3.6.1.4.1.9.9.813 | ciscoPfcExtMIB | 3 | 27 | This MIB module defines management objects for monitoring information of Priority-based Flow Control. The following terms are used… |
| 1.3.6.1.4.1.9.9.814 | ciscoLivedataMIB | 3 | 57 | Cisco LiveData is the next generation reporting product for Cisco Unified Contact Center Enterprise (CCE). Cisco LiveData provid… |
| 1.3.6.1.4.1.9.9.816 | ciscoVpnLicUsageMonitorMIB | 2 | 60 | Acronyms and Definitions The following acronyms and terms are used in this document: IPSec: Secure IP Protocol VPN: Virtual Priva… |
| 1.3.6.1.4.1.9.9.817 | ciscoWanCellExtMIB | 3 | 81 | This MIB module is an extension of CISCO-WAN-3G-MIB.my, and it provides network management support for Cisco cellular WAN 4G/LTE p… |
| 1.3.6.1.4.1.9.9.818 | ciscoNatCgnExtMIB | 3 | 69 | This MIB module extends the IETF draft NAT MIB available at http://tools.ietf.org/html/draft-ietf-behave-nat-mib-11 The extension… |
| 1.3.6.1.4.1.9.9.819 | ciscoWpanMIB | 3 | 25 | This MIB module defines management objects for configuration and monitoring of Wireless Personal Area Network (WPAN). Personal Are… |
| 1.3.6.1.4.1.9.9.820 | ciscoNetworkVirtualizationOverlayMIB | 3 | 61 | This MIB module is for managing Network Virtualization Overlay functionality on Cisco devices. The following terms are used throu… |
| 1.3.6.1.4.1.9.9.821 | ciscoCableIronBusStatMIB | 3 | 22 | This is the MIB module for Cable Iron Bus Statistics for DOCSIS-compliant Cable Modem Termination Systems (CMTS). The Statistics … |
| 1.3.6.1.4.1.9.9.822 | ciscoDtiExtMIB | 3 | 12 | This MIB module provides the trap objects necessary to monitor the DOCSIS Timing Interface devices. |
| 1.3.6.1.4.1.9.9.824 | ciscoQpLbgMIB | 3 | 74 | This MIB module represents the Qam-Partition (QP) and Load Balance Group (LBG) parameters in the headend and it is supported by … |
| 1.3.6.1.4.1.9.9.825 | ciscoLispExtMIB | 3 | 77 | This MIB is an extension to the IETF LISP-MIB module defined in RFC 7052. It contains Cisco defined managed objects and traps to … |
| 1.3.6.1.4.1.9.9.827 | ciscoUspMIB | 3 | 80 | The MIB Module for the management of the Cisco Unified SIP Proxy (CUSP) service. CUSP is a Session Initiation Protocol (SIP) prox… |
| 1.3.6.1.4.1.9.9.828 | ciscoOpticalMIB | 3 | 176 | This MIB module defines the managed objects for physical layer characteristics of optical interfaces and performance statistics o… |
| 1.3.6.1.4.1.9.9.829 | ciscoSslvpnMIB | 3 | 53 | This MIB module defines management objects for configuration and monitoring of the Cisco secure gateway that implements SSLVPN. Gl… |
| 1.3.6.1.4.1.9.9.831 | ciscoSmartLicMIB | 3 | 78 | The MIB module for managing licenses on the system. The licensing mechanism provides flexibility to enforce licensing for various… |
| 1.3.6.1.4.1.9.9.942 | ciscoVqeSMIB | 3 | 57 | This MIB module defines a set of objects for monitoring the Visual Quality Experience Server (VQE-S) operational status. VQE-S re… |
| 1.3.6.1.4.1.9.9.957 | ciscoCdmaPdsnCrpMIB | 2 | 29 | This MIB is to support the Closed RP feature of CDMA PDSN that supports wireless data communication through 3G CDMA radio access … |
| 1.3.6.1.4.1.9.9.969 | ciscoVqeToolsMIB | 3 | 16 | This MIB module defines a set of objects for monitoring the VQE Client Channel Configuration Delivery Server (VCDS) operational s… |
| 1.3.6.1.4.1.9.9.995 | ciscoSipCallsMIB | 2 | 49 | The Cisco Session Initiation Protocol (SIP) Calls MIB module is designed to provide protocol-specific information on SIP calls wh… |
| 1.3.6.1.4.1.9.9.997 | cCdmaAhdlcMIB | 3 | 42 | This MIB module provides details concerning AHDLC engine state, performance, configuration and notification. An AHDLC channel hand… |
| 1.3.6.1.4.1.9.9.1300 | ciscoItpDsmrMIB | 3 | 168 | The MIB for providing information about Distributed Short Message Routing for Short Message Service Center. This MIB will provid… |
| 1.3.6.1.4.1.9.9.1301 | ciscoItpDsmrSmppMIB | 3 | 50 | The MIB for providing information about Distributed Short Message Routing delivery using Short Message Peer-to-Peer protocol. Acr… |
| 1.3.6.1.4.1.9.9.1302 | ciscoItpDsmrUcpMIB | 3 | 44 | The MIB for providing information about Distributed Short Message Routing delivery using Universal Computer Protocol. Acronyms an… |
| 1.3.6.1.4.1.9.9.3228 | ciscoDot11CsMgrMIB | 2 | 17 | This MIB is intended to be implemented on IEEE 802.11 Wireless LAN management devices for Access Points and Wireless Bridges part… |
| 1.3.6.1.4.1.9.9.3333 | ciscoDot11AntennaMIB | 2 | 11 | This MIB is intended to be implemented on 802.11 Access Points and Wireless Bridges to provide information about the antennas con… |
| 1.3.6.1.4.1.9.9.8888 | ciscoAnnouncementMIB | 3 | 34 | This MIB defines the objects for announcement system supported on media gateway. With announcement system setup, media gateway wi… |
| 1.3.6.1.4.1.9.9.9399 | ciscoIfLoopbackMIB | 2 | 13 | The MIB module to configure the loopback on certain interfaces in ifTable with ifType ds1/e1, ds3/e3, ds0 etc. |
| 1.3.6.1.4.1.9.9.9968 | ciscoIfCallServiceMIB | 3 | 16 | The MIB is used to manage call service state for interfaces on media gateway. |
| 1.3.6.1.4.1.9.9.9992 | ciscoGprsIsgsnMIB | 2 | 19 | The MIB Module for managing the General Packet Radio Service(GPRS) iSGSN protocol on Servicing GPRS Support Node (SGSN). In the Al… |
| 1.3.6.1.4.1.9.9.9993 | ciscoGprsL2rlyMIB | 3 | 45 | The MIB Module for managing the General Packet Radio Service(GPRS) L2RLY related information on Servicing GPRS Support Node(SGSN)… |
| 1.3.6.1.4.1.9.9.9997 | ciscoGtpDirectorMIB | 3 | 35 | |
| 1.3.6.1.4.1.9.9.9999 | ciscoAal5ExtMIB, ciscoAtmConnInfoMIB, ciscoDs0CrossConnectMIB, ciscoFiberChannelTunnelMIB | 3 | 145 | The MIB module for providing the parameters configured on an ATM interface. Terminologies used: SVC : Switched Virtual Channel SPV… |
| 1.3.6.1.4.1.9.9.99990 | ciscoImageCheckMIB | 2 | 22 | Initial version of Image Check MIB. |
| 1.3.6.1.4.1.9.9.99996 | ciscoWanATMPrefRouteMIB | 3 | 18 | This MIB facilitates the maintenance of preferred routes configuration. |
| 1.3.6.1.4.1.9.9.99997 | ciscoFcPmMIB | 3 | 78 | This MIB module defines 24 hour error statistics for Fibre Channel (FC) and FICON interfaces collected every 15 minutes. Based o… |
| 1.3.6.1.4.1.9.9.99998 | ciscoWanAtmPartyMIB | 3 | 23 | A management station can use this MIB to provision, manage or delete one or more 'parties' on an ATM point-to-multipoint Soft PVC… |
| 1.3.6.1.4.1.9.9.99999 | ciscoMpoaExtMIB, ciscoWanAtmCugMIB, ciscoAuthorizationStatsMibModule | 4 | 52 | This MIB module is intended for the management of 'Closed User Group(CUG)' in Cisco ATM switches. This MIB definition is based up… |
| 1.3.6.1.4.1.9.9.193999 | ciscoLwappDhcpMIB | 1 | 23 | ciscoLwappDhcpMIB MODULE-IDENTITY LAST-UPDATED "200604051150Z" ORGANIZATION "Cisco Systems Inc." CONTACT-INFO " Cisco Systems, … |
| 1.3.6.1.4.1.9.9.199995 | ciscoLwappDot11ClientRmMIB | 3 | 54 | ciscoLwappDot11ClientRmMIB MODULE-IDENTITY LAST-UPDATED "200604110000Z" ORGANIZATION "Cisco Systems Inc." CONTACT-INFO " Cisco … |
| 1.3.6.1.4.1.9.9.300576 | ciscoVoiceCard | 3 | 13 | The MIB module to configure voice-card specific parameters such as codec complexity in voice- enabled cisco routers. |
| 1.3.6.1.4.1.9.9.999999 | ciscoFipsStatsMIB | 3 | 11 | The Federal Information Processing Standards (FIPS) power-up self-test status MIB module |