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.249 | ciscoEnhancedImageMIB | 2 | 44 | Initial version of the MIB. This MIB has Image table containing the following information related to the running IOS image 1. Enti… |
| 1.3.6.1.4.1.9.9.252 | cTapMIB | 3 | 80 | This module manages Cisco's intercept feature. |
| 1.3.6.1.4.1.9.9.253 | ciscoItpXuaMIB | 3 | 250 | The MIB for MTP3 User Adaptation (M3UA) and SCCP User Adaptation (SUA) for Cisco's IP Transfer Point (ITP) implementation. The Cis… |
| 1.3.6.1.4.1.9.9.254 | ciscoSlbExtMIB | 3 | 425 | The extended MIB for managing Server Load Balancing Manager(s). This MIB extends the SLB management functionality in the CISCO-SL… |
| 1.3.6.1.4.1.9.9.255 | ciscoFabricMcastMIB | 3 | 30 | Fabric Multicast Resource MIB module. This MIB module is used for managing/tracking the fabric multicast resource related informa… |
| 1.3.6.1.4.1.9.9.256 | ciscoFabricMcastApplMIB | 3 | 16 | Fabric multicast resource MIB module. This MIB module is used for managing/tracking the fabric multicast resource application rel… |
| 1.3.6.1.4.1.9.9.257 | ciscoFabricHfrMIB | 3 | 90 | Cisco Enhanced Benes fabric MIB module. This MIB module is used for managing/tracking the Ehanced Benes Fabric entities and/or fa… |
| 1.3.6.1.4.1.9.9.259 | ciscoPsaMicrocodeMIB | 3 | 24 | Cisco PSA Microcode MIB - Overview The PSA is the Packet Switching ASIC used in module like engine 2(E2) line cards in GSR for IP … |
| 1.3.6.1.4.1.9.9.260 | ciscoSsgMIB | 3 | 218 | The MIB Module manages Service Selection Gateway(SSG) devices. Service Selection Gateway(SSG) is a switching solution for service… |
| 1.3.6.1.4.1.9.9.261 | ciscoPtopoExtnMIB | 2 | 18 | This MIB module contains extensions to the PTOPO-MIB that provide support to distinguish between bidirectional and unidirectional… |
| 1.3.6.1.4.1.9.9.262 | ciscoVoaMIB | 2 | 14 | This MIB module defines objects to configure and manage the Variable Optical Attenuator (VOA) modules. VOA modules are typically … |
| 1.3.6.1.4.1.9.9.263 | ciscoIgmpSnoopingMIB | 3 | 286 | The MIB module for IGMP Snooping feature. Internet Group Management Protocol (IGMP) is the protocol used by IPv4 end hosts to ind… |
| 1.3.6.1.4.1.9.9.264 | ciscoOpticalMonitorMIB | 3 | 72 | This MIB module defines objects to monitor optical characteristics and set corresponding thresholds on the optical interfaces in … |
| 1.3.6.1.4.1.9.9.265 | ciscoEntityPfeMib | 3 | 58 | The Packet Forwarding Engine technology are Cisco developed Network Processors, which accelerates certain features in order to pr… |
| 1.3.6.1.4.1.9.9.268 | ciscoWlanVlanMIB | 3 | 41 | This MIB module provides network management support for device VLAN configuration on IEEE 802.11 wireless LAN. ACRONYMS AES Advanced… |
| 1.3.6.1.4.1.9.9.269 | ciscoTBridgeDevIfMIB | 2 | 20 | This MIB module provides network management support for configuration and status information of devices supporting transparent br… |
| 1.3.6.1.4.1.9.9.270 | ciscoSyslogEventExtMIB | 2 | 21 | This MIB module extends the Cisco Syslog MIB and provides network management support to handle and process Syslog messages as devi… |
| 1.3.6.1.4.1.9.9.271 | ciscoL2DevMonMIB | 3 | 24 | This MIB module is for monitoring of active layer 2 devices by hot standby layer 2 devices and the configuration of hot standby s… |
| 1.3.6.1.4.1.9.9.272 | ciscoDot11IfMIB | 3 | 212 | This MIB module provides network management support for Cisco IEEE 802.11 Wireless LAN type device (Access Point) radio interface… |
| 1.3.6.1.4.1.9.9.273 | ciscoDot11AssociationMIB | 2 | 91 | This MIB module provides network management information on IEEE 802.11 wireless device association management and data packet for… |
| 1.3.6.1.4.1.9.9.275 | ciscoBcpMIB | 2 | 25 | This MIB module describes the Managed Objects for of Bridge Control Protocol (RFC2878). This MIB is influenced by RFC1474. |
| 1.3.6.1.4.1.9.9.276 | ciscoIfExtensionMIB | 3 | 143 | A MIB module for extending the IF-MIB (RFC2863) to add objects which provide additional information about interfaces not availabl… |
| 1.3.6.1.4.1.9.9.277 | ciscoDdpIappMIB | 3 | 22 | This MIB module describes the management support for the Inter-Access Point Protocol (IAPP). IAPP is a Cisco propriety Data Deli… |
| 1.3.6.1.4.1.9.9.278 | ciscoIpProtocolMIB | 3 | 63 | The MIB module is for management of information to support packet filtering on IP protocols. The cippfIpProfileTable allows users… |
| 1.3.6.1.4.1.9.9.279 | ciscoAtmQosMIB | 3 | 67 | The MIB is created to provide ATM QoS information in these areas: 1. Traffic shaping on a per-VC basis 2. Traffic shaping on a pe… |
| 1.3.6.1.4.1.9.9.280 | ciscoOutageMIB | 3 | 75 | This MIB module describes, stores, and reports outage related information generated by individual hardware and software component… |
| 1.3.6.1.4.1.9.9.281 | ciscoFabricC12kMIB | 3 | 135 | Cisco Fabric MIB module for c12000 series of routers. This MIB module is used for managing/tracking the c12000 fabric entities an… |
| 1.3.6.1.4.1.9.9.282 | ciscoVsanMIB | 2 | 104 | The MIB module for the management of the Virtual Storage Networks (VSANs) within the frame work of Cisco's VSAN Architecture. T… |
| 1.3.6.1.4.1.9.9.284 | ciscoFcRouteMIB | 2 | 55 | The MIB module for configuring and displaying FC (Fibre Channel) Route Information. |
| 1.3.6.1.4.1.9.9.285 | ciscoPortChannelMIB | 2 | 40 | The MIB module for management of Port Channel ports. In addition to this MIB, CISCO-FC-FE-MIB and interface mib (rfc2863) will al… |
| 1.3.6.1.4.1.9.9.286 | ciscoWwnmgrMIB | 2 | 38 | The World Wide Name (WWN) in the fibre channel networking technology is equivalent to the MAC address in Ethernet. There are six … |
| 1.3.6.1.4.1.9.9.287 | ciscoFspfMIB | 4 | 95 | Fabric Shortest Path First (FSPF) MIB. |
| 1.3.6.1.4.1.9.9.288 | ciscoRadiusMIB | 3 | 91 | MIB module for monitoring and configuring authentication and logging services using RADIUS (Remote Authentication Dial In User Se… |
| 1.3.6.1.4.1.9.9.289 | ciscoFcFeMIB | 2 | 315 | This is the Cisco fibre element management MIB module. It covers: - Cisco extension to the interface MIB ( IF-MIB ) - Contains all… |
| 1.3.6.1.4.1.9.9.290 | ciscoVirtualNwIfMIB | 2 | 22 | The MIB module for management of virtual network interfaces to VSAN and VLAN. |
| 1.3.6.1.4.1.9.9.292 | ciscoRscnMIB | 2 | 67 | The MIB module for the management of the Fibre Channel's Registered State Change Notification (RSCN) functionality, which is spec… |
| 1.3.6.1.4.1.9.9.293 | ciscoNsMIB | 2 | 67 | The MIB module for the management of the Cisco Name Server which realizes the FC-GS3 requirements for Name Server (NS). |
| 1.3.6.1.4.1.9.9.294 | ciscoZsMIB | 2 | 254 | The MIB module for the management of zoning within the framework of Cisco's Zoning Server (ZS) Archi- tecture which realizes the … |
| 1.3.6.1.4.1.9.9.295 | ciscoFcPingMIB | 2 | 37 | The MIB module for the management of the Fibre Channel Ping functionality. |
| 1.3.6.1.4.1.9.9.296 | ciscoFcTraceRouteMIB | 2 | 31 | The MIB module for the management of the Fibre Channel Trace Route functionality. |
| 1.3.6.1.4.1.9.9.297 | ciscoFcsMIB | 2 | 122 | The MIB module for the management of a Fabric Configuration Server (FCS). An FCS is defined by the FC-GS3 standard. This MIB ena… |
| 1.3.6.1.4.1.9.9.299 | ciscoExtScsiMIB | 2 | 68 | The Cisco extension to CISCO-SCSI-MIB which is a copy of the Internet draft, the SCSI-MIB, from the IETF. Glossary of terms used i… |
| 1.3.6.1.4.1.9.9.300 | ciscoCallHomeMIB | 3 | 324 | The MIB module for the management of Call Home feature within the framework of Cisco's Call Home architecture. Customers deployin… |
| 1.3.6.1.4.1.9.9.301 | ciscoSyslogExtMIB | 2 | 44 | MIB module for configuring and monitoring System Log related management parameters as defined by RFC 3164. |
| 1.3.6.1.4.1.9.9.302 | ciscoDmMIB | 2 | 85 | The MIB module for the domain management functionality defined by the Fibre Channel standards (FC-SW2). For the purposes of this … |
| 1.3.6.1.4.1.9.9.305 | ciscoSystemExtMIB | 3 | 112 | MIB module for monitoring High Availability, SNMP SET errors and bandwidths. This mib module also provides the information on co… |
| 1.3.6.1.4.1.9.9.309 | ciscoIPIfMIB | 3 | 40 | The MIB module for configuring IP characteristics of the interfaces of a device. |
| 1.3.6.1.4.1.9.9.311 | ciscoEpmNotificationMIB | 3 | 48 | Notifications directly from hardware and software and processed notifications from various management applications can be furthe… |
| 1.3.6.1.4.1.9.9.312 | ciscoDataCollectionMIB | 3 | 84 | The MIB module allows a management application to select a set of MIB object instances whose values need to be collected on a per… |
| 1.3.6.1.4.1.9.9.313 | ciscoL2ControlMIB | 3 | 113 | The CISCO-L2-CONTROL-MIB is used to control some layer 2 functions, including MAC limit function and unicast flooding. This devi… |