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.6 | ciscoTcpMIB | 3 | 20 | ciscoTcpMIB MODULE-IDENTITY LAST-UPDATED "200111120000Z" ORGANIZATION "Cisco Systems, Inc." CONTACT-INFO " Cisco Systems Custom… |
| 1.3.6.1.4.1.9.9.10 | ciscoFlashMIB | 2 | 164 | ciscoFlashMIB MODULE-IDENTITY LAST-UPDATED "200102211234Z" ORGANIZATION "Cisco Systems, Inc." CONTACT-INFO " Cisco Systems Cust… |
| 1.3.6.1.4.1.9.9.13 | ciscoEnvMonMIB | 4 | 68 | ciscoEnvMonMIB MODULE-IDENTITY LAST-UPDATED "200202040000Z" ORGANIZATION "Cisco Systems, Inc." CONTACT-INFO " Cisco Systems Cus… |
| 1.3.6.1.4.1.9.9.16 | ciscoPingMIB | 3 | 31 | ciscoPingMIB MODULE-IDENTITY LAST-UPDATED "200108280000Z" ORGANIZATION "Cisco Systems, Inc." CONTACT-INFO " Cisco Systems Custo… |
| 1.3.6.1.4.1.9.9.17 | ciscoVinesMIB | 2 | 188 | ciscoVinesMIB MODULE-IDENTITY LAST-UPDATED "9506070000Z" ORGANIZATION "Cisco Systems, Inc." CONTACT-INFO " Cisco Systems Custom… |
| 1.3.6.1.4.1.9.9.18 | ciscoIsdnuIfMIB | 3 | 29 | ciscoIsdnuIfMIB MODULE-IDENTITY LAST-UPDATED "9603180000Z" ORGANIZATION "Cisco Systems, Inc." CONTACT-INFO " Cisco Systems Cust… |
| 1.3.6.1.4.1.9.9.19 | ciscoSnapshotMIB | 2 | 28 | ciscoSnapshotMIB MODULE-IDENTITY LAST-UPDATED "9508150000Z" ORGANIZATION "Cisco Systems, Inc." CONTACT-INFO " Cisco Systems Cus… |
| 1.3.6.1.4.1.9.9.20 | channel | 2 | 169 | channel MODULE-IDENTITY LAST-UPDATED "9703260000Z" ORGANIZATION "cisco IBM engineering Working Group" CONTACT-INFO " Cisco Syst… |
| 1.3.6.1.4.1.9.9.22 | ciscoRptrMIB | 3 | 32 | ciscoRptrMIB MODULE-IDENTITY LAST-UPDATED "9512050000Z" ORGANIZATION "Cisco Systems, Inc." CONTACT-INFO " Cisco Systems Custome… |
| 1.3.6.1.4.1.9.9.23 | ciscoCdpMIB | 2 | 78 | ciscoCdpMIB MODULE-IDENTITY LAST-UPDATED "200111230000Z" ORGANIZATION "Cisco System Inc." CONTACT-INFO " Cisco Systems Customer… |
| 1.3.6.1.4.1.9.9.24 | ciscoDspuMIB | 2 | 150 | ciscoDspuMIB MODULE-IDENTITY LAST-UPDATED "9508150000Z" ORGANIZATION "Cisco Systems, Inc." CONTACT-INFO " Cisco Systems Custome… |
| 1.3.6.1.4.1.9.9.25 | ciscoImageMIB | 2 | 10 | ciscoImageMIB MODULE-IDENTITY LAST-UPDATED "9508150000Z" ORGANIZATION "Cisco Systems, Inc." CONTACT-INFO " Cisco Systems Custom… |
| 1.3.6.1.4.1.9.9.26 | ciscoIsdnMib | 3 | 34 | ciscoIsdnMib MODULE-IDENTITY LAST-UPDATED "200102090000Z" ORGANIZATION "Cisco Systems, Inc." CONTACT-INFO " Cisco Systems Custo… |
| 1.3.6.1.4.1.9.9.27 | ciscoCallHistoryMib | 2 | 40 | ciscoCallHistoryMib MODULE-IDENTITY LAST-UPDATED "9611190000Z" ORGANIZATION "Cisco Systems, Inc." CONTACT-INFO " Cisco Systems … |
| 1.3.6.1.4.1.9.9.28 | ciscoSnaSdllcMIB | 3 | 28 | ciscoSnaSdllcMIB MODULE-IDENTITY LAST-UPDATED "9812170000Z" ORGANIZATION "Cisco Systems, Inc." CONTACT-INFO " Cisco Systems Cus… |
| 1.3.6.1.4.1.9.9.29 | ciscoRsrbMIB | 3 | 45 | ciscoRsrbMIB MODULE-IDENTITY LAST-UPDATED "9508210000Z" ORGANIZATION "Cisco Systems, Inc." CONTACT-INFO " Cisco Systems Custome… |
| 1.3.6.1.4.1.9.9.30 | ciscoStunMIB | 3 | 41 | ciscoStunMIB MODULE-IDENTITY LAST-UPDATED "9508210000Z" ORGANIZATION "Cisco Systems, Inc." CONTACT-INFO " Cisco Systems Custome… |
| 1.3.6.1.4.1.9.9.31 | ciscoTcpOffloadMIB | 2 | 20 | ciscoTcpOffloadMIB MODULE-IDENTITY LAST-UPDATED "9503300000Z" ORGANIZATION "cisco IBM engineering Working Group" CONTACT-INFO "… |
| 1.3.6.1.4.1.9.9.32 | ciscoCipTcpIpMIB | 2 | 88 | ciscoCipTcpIpMIB MODULE-IDENTITY LAST-UPDATED "9508210000Z" ORGANIZATION "cisco IBM engineering Working Group" CONTACT-INFO " C… |
| 1.3.6.1.4.1.9.9.33 | ciscoCipCsnaMIB | 3 | 66 | |
| 1.3.6.1.4.1.9.9.34 | ciscoCipLanMIB | 2 | 24 | ciscoCipLanMIB MODULE-IDENTITY LAST-UPDATED "9504280000Z" ORGANIZATION "cisco IBM engineering Working Group" CONTACT-INFO " Cis… |
| 1.3.6.1.4.1.9.9.35 | ciscoBstunMIB | 3 | 71 | ciscoBstunMIB MODULE-IDENTITY LAST-UPDATED "200106190000Z" ORGANIZATION "Cisco Systems, Inc." CONTACT-INFO " Cisco Systems Cust… |
| 1.3.6.1.4.1.9.9.36 | ciscoBscMIB | 2 | 46 | ciscoBscMIB MODULE-IDENTITY LAST-UPDATED "9701250000Z" ORGANIZATION "Cisco Systems, Inc." CONTACT-INFO " Cisco Systems Customer… |
| 1.3.6.1.4.1.9.9.37 | ciscoQueueMIB | 3 | 23 | ciscoQueueMIB MODULE-IDENTITY LAST-UPDATED "9505310000Z" ORGANIZATION "Cisco Systems, Inc." CONTACT-INFO " Cisco Systems Custom… |
| 1.3.6.1.4.1.9.9.38 | ciscoLecsMIB | 2 | 77 | ciscoLecsMIB MODULE-IDENTITY LAST-UPDATED "9605291437Z" ORGANIZATION "Cisco System Inc." CONTACT-INFO " Cisco System Inc." DESC… |
| 1.3.6.1.4.1.9.9.39 | ciscoLesMIB | 2 | 82 | ciscoLesMIB MODULE-IDENTITY LAST-UPDATED "9603071030Z" ORGANIZATION "Cisco Systems Inc." CONTACT-INFO " Cisco Systems Inc." DES… |
| 1.3.6.1.4.1.9.9.40 | ciscoBusMIB | 2 | 37 | ciscoBusMIB MODULE-IDENTITY LAST-UPDATED "9509151702Z" ORGANIZATION "Cisco Systems Inc." CONTACT-INFO " Cisco Systems Inc." DES… |
| 1.3.6.1.4.1.9.9.41 | ciscoSyslogMIB | 3 | 49 | ciscoSyslogMIB MODULE-IDENTITY LAST-UPDATED "9508070000Z" ORGANIZATION "Cisco Systems, Inc." CONTACT-INFO " Cisco Systems Custo… |
| 1.3.6.1.4.1.9.9.42 | ciscoRttMonMIB | 3 | 816 | ciscoRttMonMIB MODULE-IDENTITY LAST-UPDATED "9903110000Z" ORGANIZATION "Cisco IBU Engineering Working Group" CONTACT-INFO "Cisc… |
| 1.3.6.1.4.1.9.9.43 | ciscoConfigManMIB | 3 | 75 | ciscoConfigManMIB MODULE-IDENTITY LAST-UPDATED "9511280000Z" ORGANIZATION "Cisco Systems, Inc." CONTACT-INFO " Cisco Systems Cu… |
| 1.3.6.1.4.1.9.9.44 | ciscoICsuDsuMIB | 4 | 70 | ciscoICsuDsuMIB MODULE-IDENTITY LAST-UPDATED "9601210000Z" ORGANIZATION "Cisco Systems, Inc." CONTACT-INFO " Cisco Systems Cust… |
| 1.3.6.1.4.1.9.9.45 | ciscoAtmIfPhysMIB | 2 | 39 | ciscoAtmIfPhysMIB MODULE-IDENTITY LAST-UPDATED "9609190000Z" ORGANIZATION "Cisco Systems, Inc." CONTACT-INFO " Cisco Systems Cu… |
| 1.3.6.1.4.1.9.9.46 | ciscoVtpMIB | 3 | 261 | ciscoVtpMIB MODULE-IDENTITY LAST-UPDATED "200402110000Z" ORGANIZATION "Cisco Systems, Inc." CONTACT-INFO "Cisco Systems Custome… |
| 1.3.6.1.4.1.9.9.47 | ciscoModemMgmtMIB | 3 | 112 | This MIB module provides modem call related data for tracking the progress and status of a call. |
| 1.3.6.1.4.1.9.9.48 | ciscoMemoryPoolMIB | 3 | 32 | MIB module for monitoring memory pools |
| 1.3.6.1.4.1.9.9.49 | ciscoFrameRelayMIB | 2 | 158 | ciscoFrameRelayMIB MODULE-IDENTITY LAST-UPDATED "200005220000Z" ORGANIZATION "Cisco Systems, Inc." CONTACT-INFO " Cisco Systems … |
| 1.3.6.1.4.1.9.9.50 | ciscoAtmServiceRegistryMIB | 2 | 14 | ciscoAtmServiceRegistryMIB MODULE-IDENTITY LAST-UPDATED "9602210000Z" ORGANIZATION "Cisco Systems, Inc." CONTACT-INFO " Cisco S… |
| 1.3.6.1.4.1.9.9.51 | ciscoAtmSwAddrMIB | 2 | 11 | ciscoAtmSwAddrMIB MODULE-IDENTITY LAST-UPDATED "9601100000Z" ORGANIZATION "Cisco Systems, Inc." CONTACT-INFO " Cisco Systems Cu… |
| 1.3.6.1.4.1.9.9.52 | ciscoIpEncryptionMIB | 3 | 51 | Used to manage the encryption feature. |
| 1.3.6.1.4.1.9.9.53 | ciscoVmpsMIB | 3 | 55 | The MIB module for the management of the VLAN Membership Policy Server. |
| 1.3.6.1.4.1.9.9.54 | ciscoTn3270ServerMIB | 3 | 105 | The MIB module for TN3270 Server. MIB description The PU and LU MIB are defined in RFC 1666. This MIB provides additional informa… |
| 1.3.6.1.4.1.9.9.55 | ciscoAsppMIB | 2 | 29 | The ASPP MIB provides the configuration and operational information on asynchronous polled protocols such as the asynchronous sec… |
| 1.3.6.1.4.1.9.9.56 | ciscoVlanBridgingMIB | 2 | 13 | A set of managed objects for optimizing access to bridging related data from RFC 1493. This MIB is modeled after portions of RFC… |
| 1.3.6.1.4.1.9.9.57 | ciscoCompressionServiceAdapterMIB | 2 | 19 | ciscoCompressionServiceAdapterMIB MODULE-IDENTITY LAST-UPDATED "9608150000Z" ORGANIZATION "Cisco Systems, Inc." CONTACT-INFO " … |
| 1.3.6.1.4.1.9.9.59 | ciscoStackMakerMIB | 2 | 15 | The MIB module for Cisco Systems' StackMaker. |
| 1.3.6.1.4.1.9.9.60 | ciscoAtmDualPhyMIB | 3 | 26 | ciscoAtmDualPhyMIB MODULE-IDENTITY LAST-UPDATED "9608300000Z" ORGANIZATION "Cisco Systems, Inc." CONTACT-INFO " Cisco Systems C… |
| 1.3.6.1.4.1.9.9.61 | ciscoAccessEnvMonMIB | 3 | 13 | ciscoAccessEnvMonMIB MODULE-IDENTITY LAST-UPDATED "9808050000Z" ORGANIZATION "Cisco Systems, Inc." CONTACT-INFO " Cisco Systems … |
| 1.3.6.1.4.1.9.9.62 | ciscoVoiceAnalogIfMIB | 2 | 90 | Analog Voice Interface MIB module. This MIB manages the E&M, FXO, FXS Interfaces in the router. |
| 1.3.6.1.4.1.9.9.63 | ciscoVoiceDialControlMIB | 3 | 377 | This MIB module enhances the IETF Dial Control MIB (RFC2128) by providing management of voice telephony peers on both a circuit-s… |
| 1.3.6.1.4.1.9.9.64 | ciscoVoiceInterfaceMIB | 2 | 24 | Common Voice Interface MIB module. The MIB module manages the common voice related parameters for both voice analog and ISDN inte… |