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.743 | ciscoCdstvCsStatsMIB | 3 | 83 | This MIB module defines objects describing the caching and streaming statistics objects that facilitate the management of the Cis… |
| 1.3.6.1.4.1.9.9.744 | ciscoIpslaVideoMIB | 3 | 73 | IP SLA is a capability which utilizes active monitoring for network performance. It can be used for network troubleshooting, net… |
| 1.3.6.1.4.1.9.9.745 | ciscoEntitySensorExtMIB | 3 | 21 | This MIB is extension to ENTITY-SENSOR-MIB(RFC 3433). This MIB also defines the notifications applicable for sensors reported in … |
| 1.3.6.1.4.1.9.9.748 | ciscoIpAddressPoolMIB | 3 | 96 | This MIB modules defines objects that describe common aspects of IP address pools. IP Address Pool Manager ======================= … |
| 1.3.6.1.4.1.9.9.749 | ciscoCdstvBwmgrMIB | 3 | 21 | This MIB module defines Bandwidth Manager configuration objects that facilitate the management of the Cisco Content Delivery Syst… |
| 1.3.6.1.4.1.9.9.750 | ciscoCdstvIngestTuningMIB | 3 | 18 | This MIB module defines ingest tuning configuration objects that facilitate the management of the Cisco Content Delivery System f… |
| 1.3.6.1.4.1.9.9.751 | ciscoCdstvAuthmgrMIB | 3 | 25 | This MIB module defines objects that describe the configuration of the authentication manager for the Cisco Content Delivery Syst… |
| 1.3.6.1.4.1.9.9.753 | ciscoVideoSessionMIB | 3 | 145 | This MIB module complements the CISCO-VOICE-DIAL-CONTROL-MIB, which provides voice telephony peer information, by providing manag… |
| 1.3.6.1.4.1.9.9.754 | ciscoCdstvServerMIB | 3 | 82 | This MIB module defines server configuration that faciliate the management of the Cisco Content Delivery System for TV (CDS-TV) … |
| 1.3.6.1.4.1.9.9.755 | ciscoCdstvIsaMIB | 3 | 145 | This MIB module defines ISA configuration objects that faciliate the management of the Cisco Content Delivery System for TV (CDS-… |
| 1.3.6.1.4.1.9.9.756 | ciscoEntityPerformanceMIB | 3 | 56 | This MIB module defines managed objects that facilitate to monitor performance of any physical entity, which are listed in the EN… |
| 1.3.6.1.4.1.9.9.757 | ciscoSbcStatsMIB | 3 | 106 | The main purpose of this MIB is to define the statistics information for Session Border Controller application. This MIB categori… |
| 1.3.6.1.4.1.9.9.758 | ciscoTelepresenceExchangeSystemMIB | 3 | 173 | The main purpose of this MIB is to provide product component level configuration, status, statistics, events, and alarm notificat… |
| 1.3.6.1.4.1.9.9.759 | ciscoGdoiMIB | 3 | 213 | This MIB module defines objects for managing the GDOI protocol. Copyright (c) The IETF Trust (2010). This version of this MIB mo… |
| 1.3.6.1.4.1.9.9.760 | ciscoPtpMIB | 3 | 182 | The MIB module for PTPv2 (IEEE1588 - 2008) Overview of PTPv2 (IEEE 1588-2008) This IEEE standard defines a protocol enabling prec… |
| 1.3.6.1.4.1.9.9.761 | ciscoNetsyncMIB | 3 | 104 | The Synchronous Ethernet (SyncE) MIB is defined for monitoring network synchronization based on ITU-T G.781 clock selection. Sync… |
| 1.3.6.1.4.1.9.9.762 | ciscoWanOptimizationMIB | 3 | 302 | This MIB is for managing Wide Area Network (WAN) Optimization systems. The objective of WAN optimization system is to reduce as m… |
| 1.3.6.1.4.1.9.9.763 | ciscoVideoTc | 0 | 0 | This MIB module defines a collection of common video-related textual conventions to be used in Cisco MIBS for video-capable produ… |
| 1.3.6.1.4.1.9.9.764 | ciscoUbeMIB | 2 | 12 | This MIB describes objects used for managing Cisco Unified Border Element (CUBE). The Cisco Unified Border Element (CUBE) is a Ci… |
| 1.3.6.1.4.1.9.9.765 | ciscoFlowCloneMIB | 3 | 44 | This MIB module defines objects that manages flow cloning feature. A flow cloning can be described as a hardware or software enti… |
| 1.3.6.1.4.1.9.9.766 | ciscoIpslaVideoProfileMIB | 3 | 29 | IP SLA is a capability which utilizes active monitoring for network performance. It can be used for network troubleshooting, net… |
| 1.3.6.1.4.1.9.9.767 | ciscoLwappDot11ClientRmMIB | 3 | 64 | This MIB is intended to be implemented on all those devices operating as Central controllers, that terminate the Light Weight Acc… |
| 1.3.6.1.4.1.9.9.768 | ciscoEntitySensorHistoryMIB | 2 | 20 | This MIB module defines objects that describe collections and measurement information for each sensor supporting historical data … |
| 1.3.6.1.4.1.9.9.769 | ciscoMediaQualityMIB | 3 | 214 | This MIB module enhances the DIAL-CONTROL-MIB (RFC2128) by providing call information and voice and video quality statistics of c… |
| 1.3.6.1.4.1.9.9.770 | ciscoTcpMetricsMIB | 4 | 22 | This MIB module defines objects that describe the quality metrics of TCP streams. GLOSSARY ============ Flow Monitor - a hardware o… |
| 1.3.6.1.4.1.9.9.771 | ciscoMediaMetricsMIB | 4 | 38 | This MIB module defines objects that describe the quality metrics of Media streams. GLOSSARY ============ Flow Monitor - a hardware… |
| 1.3.6.1.4.1.9.9.772 | ciscoPfrMIB | 3 | 303 | This MIB module defines objects that describe Performance Routing (PfR). Standard routing protocols base routing decisions on re… |
| 1.3.6.1.4.1.9.9.773 | ciscoSwitchRateLimiterMIB | 3 | 28 | This MIB module defines management objects for the Switch Rate Limiter features on Cisco Layer 2 and Layer 3 devices. Rate limits … |
| 1.3.6.1.4.1.9.9.774 | ciscoVdcMIB | 3 | 90 | CISCO-VDC-MIB |
| 1.3.6.1.4.1.9.9.775 | ciscoSelectiveVrfDownloadMIB | 3 | 41 | This MIB module defines objects describing selective VRF download. The selective VRF download feature makes a best effort to dow… |
| 1.3.6.1.4.1.9.9.776 | ciscoNetflowLiteMIB | 3 | 56 | This MIB provides a method to configure Netflow-lite feature and get information in these areas: 1. Exporter config information a… |
| 1.3.6.1.4.1.9.9.777 | ciscoDsgIfExtMIB | 3 | 15 | A MIB module for extending the DSG-IF-MIB (ITU-T J.128 10/2008) to add objects which provide additional management information ab… |
| 1.3.6.1.4.1.9.9.779 | ciscoPmonMIB | 3 | 14 | ciscoPmonMIB MODULE-IDENTITY LAST-UPDATED "201201030000Z" ORGANIZATION "Cisco Systems, Inc." CONTACT-INFO "Cisco Systems Custom… |
| 1.3.6.1.4.1.9.9.782 | ciscoSubscriberIdentityTcMIB | 0 | 0 | This MIB module defines textual conventions describing subscriber session identities. A subscriber session identity consists of … |
| 1.3.6.1.4.1.9.9.783 | ciscoDynamicTemplateTcMIB | 0 | 0 | This MIB module defines textual conventions used by the CISCO-DYNAMIC-TEMPLATE-MIB and MIB modules that use and expand on dynamic… |
| 1.3.6.1.4.1.9.9.784 | ciscoDynamicTemplateMIB | 3 | 152 | This MIB defines objects that describe dynamic templates. A dynamic template is a set of configuration attributes that a system … |
| 1.3.6.1.4.1.9.9.785 | ciscoSubscriberSessionTcMIB | 0 | 0 | This MIB module defines textual conventions describing subscriber sessions. |
| 1.3.6.1.4.1.9.9.786 | ciscoSubscriberSessionMIB | 3 | 187 | This MIB defines objects describing subscriber sessions, or more specifically, subscriber sessions terminated by a RAS. A subscr… |
| 1.3.6.1.4.1.9.9.789 | ciscoFlowMetadataMIB | 3 | 30 | The MIB module for managing Cisco medianet flow metadata. Metadata, in the simplest form, is data that qualifies other data. Flow… |
| 1.3.6.1.4.1.9.9.790 | ciscoSwitchCefMIB | 3 | 33 | This MIB module defines management objects for the CEF features on Cisco Layer 2 and Layer 3 devices. Definition of some of the t… |
| 1.3.6.1.4.1.9.9.791 | ciscoAppNavMIB | 2 | 51 | ciscoAppNavMIB MODULE-IDENTITY LAST-UPDATED "201206070000Z" ORGANIZATION "Cisco Systems, Inc." CONTACT-INFO "Cisco Systems Cust… |
| 1.3.6.1.4.1.9.9.793 | ciscoMspMIB | 3 | 54 | Objective of media services proxy is to provide media services to end-points and its flows identified by a set of protocols. Medi… |
| 1.3.6.1.4.1.9.9.798 | ciscoLocalAuthUserMIB | 3 | 40 | This MIB module defines objects describing users authenticated locally by a Network Access Server (NAS). + | | | … |
| 1.3.6.1.4.1.9.9.800 | ciscoMediatraceMIB | 3 | 191 | Mediatrace helps to isolate and troubleshoot network degradation problems by enabling a network administrator to discover an Inte… |
| 1.3.6.1.4.1.9.9.801 | ciscoFabricPathTopologyMIB | 3 | 40 | This MIB module defines managed objects that facilitate the management of Cisco's FabricPath Topology technology. |
| 1.3.6.1.4.1.9.9.803 | ciscoSwitchFabricMIB | 3 | 30 | This MIB module defined managed objects that facilitates the management of switching fabric information in a Cisco switch. |
| 1.3.6.1.4.1.9.9.804 | ciscoHardwareIpVerifyMIB | 3 | 13 | This MIB module defines management objects for configuration and monitoring of the Intrusion Detection System (IDS) that checks f… |
| 1.3.6.1.4.1.9.9.806 | ciscoL2natMIB | 2 | 80 | Network Address Translation (NAT) involves translating the source and or destination IP addresses of packets as they traverse fro… |
| 1.3.6.1.4.1.9.9.807 | ciscoVpcMIB | 3 | 73 | This MIB module defines MIB objects which provide management information for configuring and monitoring of Virtual Port Channel(V… |
| 1.3.6.1.4.1.9.9.808 | ciscoACLMIB | 2 | 87 | This MIB module defines objects that describe Cisco Access Control Lists (ACL). This MIB describes different objects that enable … |