This MIB contains the basic objects for managing a
Cisco Appliance Services Architecture (CASA) Entity. A
CASA Entity can be a Manager or a Forwarding Agent as
defined below. The basic objects included in this mib
are those to configure CASA, retrieve CASA's state and
information about the fixed affinity cache.
The following gives a list of definitions and a
description of how Service Managers and Forwarding
Agents interact. For a more detailed description, see
the Cisco Appliance Services Architecture (CASA)
document.
CASA is a protocol allowing software entities (called
Appliances, examples are web caches, firewalls, load
balancers) to control the behavior of network hardware
devices (called Forwarding Agents, examples are
switches or routers) by providing a set of rules used
to handle network traffic.
A Network Appliance (referred to as an Appliance) is
any subsystem whose purpose is to provide a specific
additional value-added service to the network device,
and could be implemented as a standalone box, a line
card or processor card, or a software subsystem.
Examples of Network Appliances would include Load
Balancers, WebCaches, and Firewalls.
An Appliance tells Fowarding Agents how to handle
packets based on their source and destination IP
addresses and ports, and IP protocol fields. This set
of information is called an Affinity.
A Service Manager is an Appliance that requests
packet flows from Forwarding Agents through CASA.
A Real Server is a physical computing engine or part
of that physical computing engine that offers one or
more application services to a set of clients in the
network.
A packet flow is a TCP connection or a sequence of UDP
packets between a client and a specific Real Server,
pertaining to a specific application. Flows are
represented by entries in the affinity cache tables.
The Service Manager requests packet flows from
Forwarding Agents by sending Affinities which contains
wildcards on some of the Affinity fields. Affinities
that contain wildcards in some of the fields are
called Wildcard Affinities. The Service Manager may
send the Forwarding Agent an Affinity containing
explicit values for each of the fields. These
Affinities are called Fixed Affinities.
Typically Wildcard Affinities are used to instruct the
Forwarding Agent to send packets received by the
Forwarding Agent, which match the Wildcard Affinity,
to the Service Manager. When the Service Manager
receives the matching packet, the Service Manager
typically will send the Forwarding Agent a Fixed
Affinity. The Forwarding Agent uses Fixed Affinities
to match packets coming from the network, execute any
processing required on that packet, and forward that
packet to a destination IP address (designated in the
Fixed Affinity) called the Dispatch Address.
When an IP packet arrives at the Forwarding Agent, the
Forwarding Agent attempts to match the packet with the
Fixed Affinities in the Fixed Affinity cache. If
there is no match, an attempt is made to match the
packet with the list of Wildcard Affinities. If there
is no match the packet is routed normally. If there is
a match with a Wildcard Affinity, the Forwarding Agent
sends the packet to the Service Manager who will send
the Forwarding Manager a Fixed Affinity which provides
information on how to process IP packets similar to
the one received by the Forwarding Agent. Processing
of such packets may include sending the packet to the
Service Manager. Such packets are called Interest
Packets. Alternatively a Tickle Packet may be sent to
the Service Manager which is an indication that a
matched packet has been received by the Forwarding
Agent.
Reference: Cisco Appliance Services Architecture (CASA)
document.
_______________________________________
( )
( N E T W O R K )
(_______________________________________)
| | |
+
|Service Manager|-+
+
++
| F. Agent | | F. Agent | | F. Agent |
+
| | |
___|_________________|______________|__
( )
( N E T W O R K )
(_______________________________________)
Parsed from file CISCO-CASA-MIB.mib
Module: CISCO-CASA-MIB
This MIB contains the basic objects for managing a
Cisco Appliance Services Architecture (CASA) Entity. A
CASA Entity can be a Manager or a Forwarding Agent as
defined below. The basic objects included in this mib
are those to configure CASA, retrieve CASA's state and
information about the fixed affinity cache.
The following gives a list of definitions and a
description of how Service Managers and Forwarding
Agents interact. For a more detailed description, see
the Cisco Appliance Services Architecture (CASA)
document.
CASA is a protocol allowing software entities (called
Appliances, examples are web caches, firewalls, load
balancers) to control the behavior of network hardware
devices (called Forwarding Agents, examples are
switches or routers) by providing a set of rules used
to handle network traffic.
A Network Appliance (referred to as an Appliance) is
any subsystem whose purpose is to provide a specific
additional value-added service to the network device,
and could be implemented as a standalone box, a line
card or processor card, or a software subsystem.
Examples of Network Appliances would include Load
Balancers, WebCaches, and Firewalls.
An Appliance tells Fowarding Agents how to handle
packets based on their source and destination IP
addresses and ports, and IP protocol fields. This set
of information is called an Affinity.
A Service Manager is an Appliance that requests
packet flows from Forwarding Agents through CASA.
A Real Server is a physical computing engine or part
of that physical computing engine that offers one or
more application services to a set of clients in the
network.
A packet flow is a TCP connection or a sequence of UDP
packets between a client and a specific Real Server,
pertaining to a specific application. Flows are
represented by entries in the affinity cache tables.
The Service Manager requests packet flows from
Forwarding Agents by sending Affinities which contains
wildcards on some of the Affinity fields. Affinities
that contain wildcards in some of the fields are
called Wildcard Affinities. The Service Manager may
send the Forwarding Agent an Affinity containing
explicit values for each of the fields. These
Affinities are called Fixed Affinities.
Typically Wildcard Affinities are used to instruct the
Forwarding Agent to send packets received by the
Forwarding Agent, which match the Wildcard Affinity,
to the Service Manager. When the Service Manager
receives the matching packet, the Service Manager
typically will send the Forwarding Agent a Fixed
Affinity. The Forwarding Agent uses Fixed Affinities
to match packets coming from the network, execute any
processing required on that packet, and forward that
packet to a destination IP address (designated in the
Fixed Affinity) called the Dispatch Address.
When an IP packet arrives at the Forwarding Agent, the
Forwarding Agent attempts to match the packet with the
Fixed Affinities in the Fixed Affinity cache. If
there is no match, an attempt is made to match the
packet with the list of Wildcard Affinities. If there
is no match the packet is routed normally. If there is
a match with a Wildcard Affinity, the Forwarding Agent
sends the packet to the Service Manager who will send
the Forwarding Manager a Fixed Affinity which provides
information on how to process IP packets similar to
the one received by the Forwarding Agent. Processing
of such packets may include sending the packet to the
Service Manager. Such packets are called Interest
Packets. Alternatively a Tickle Packet may be sent to
the Service Manager which is an indication that a
matched packet has been received by the Forwarding
Agent.
Reference: Cisco Appliance Services Architecture (CASA)
document.
_______________________________________
( )
( N E T W O R K )
(_______________________________________)
| | |
+
|Service Manager|-+
+
++
| F. Agent | | F. Agent | | F. Agent |
+
| | |
___|_________________|______________|__
( )
( N E T W O R K )
(_______________________________________)
Parsed from file CISCO-CASA-MIB.my.txt
Company: None
Module: CISCO-CASA-MIB
This MIB contains the basic objects for managing a
Cisco Appliance Services Architecture (CASA) Entity. A
CASA Entity can be a Manager or a Forwarding Agent as
defined below. The basic objects included in this mib
are those to configure CASA, retrieve CASA's state and
information about the fixed affinity cache.
The following gives a list of definitions and a
description of how Service Managers and Forwarding
Agents interact. For a more detailed description, see
the Cisco Appliance Services Architecture (CASA)
document.
CASA is a protocol allowing software entities (called
Appliances, examples are web caches, firewalls, load
balancers) to control the behavior of network hardware
devices (called Forwarding Agents, examples are
switches or routers) by providing a set of rules used
to handle network traffic.
A Network Appliance (referred to as an Appliance) is
any subsystem whose purpose is to provide a specific
additional value-added service to the network device,
and could be implemented as a standalone box, a line
card or processor card, or a software subsystem.
Examples of Network Appliances would include Load
Balancers, WebCaches, and Firewalls.
An Appliance tells Fowarding Agents how to handle
packets based on their source and destination IP
addresses and ports, and IP protocol fields. This set
of information is called an Affinity.
A Service Manager is an Appliance that requests
packet flows from Forwarding Agents through CASA.
A Real Server is a physical computing engine or part
of that physical computing engine that offers one or
more application services to a set of clients in the
network.
A packet flow is a TCP connection or a sequence of UDP
packets between a client and a specific Real Server,
pertaining to a specific application. Flows are
represented by entries in the affinity cache tables.
The Service Manager requests packet flows from
Forwarding Agents by sending Affinities which contains
wildcards on some of the Affinity fields. Affinities
that contain wildcards in some of the fields are
called Wildcard Affinities. The Service Manager may
send the Forwarding Agent an Affinity containing
explicit values for each of the fields. These
Affinities are called Fixed Affinities.
Typically Wildcard Affinities are used to instruct the
Forwarding Agent to send packets received by the
Forwarding Agent, which match the Wildcard Affinity,
to the Service Manager. When the Service Manager
receives the matching packet, the Service Manager
typically will send the Forwarding Agent a Fixed
Affinity. The Forwarding Agent uses Fixed Affinities
to match packets coming from the network, execute any
processing required on that packet, and forward that
packet to a destination IP address (designated in the
Fixed Affinity) called the Dispatch Address.
When an IP packet arrives at the Forwarding Agent, the
Forwarding Agent attempts to match the packet with the
Fixed Affinities in the Fixed Affinity cache. If
there is no match, an attempt is made to match the
packet with the list of Wildcard Affinities. If there
is no match the packet is routed normally. If there is
a match with a Wildcard Affinity, the Forwarding Agent
sends the packet to the Service Manager who will send
the Forwarding Manager a Fixed Affinity which provides
information on how to process IP packets similar to
the one received by the Forwarding Agent. Processing
of such packets may include sending the packet to the
Service Manager. Such packets are called Interest
Packets. Alternatively a Tickle Packet may be sent to
the Service Manager which is an indication that a
matched packet has been received by the Forwarding
Agent.
Reference: Cisco Appliance Services Architecture (CASA)
document.
_______________________________________
( )
( N E T W O R K )
(_______________________________________)
| | |
+
|Service Manager|-+
+
++
| F. Agent | | F. Agent | | F. Agent |
+
| | |
___|_________________|______________|__
( )
( N E T W O R K )
(_______________________________________)
ciscoCasaMIB MODULE-IDENTITY LAST-UPDATED "200209180000Z" 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: [email protected]" DESCRIPTION "This MIB contains the basic objects for managing a Cisco Appliance Services Architecture (CASA) Entity. A CASA Entity can be a Manager or a Forwarding Agent as defined below. The basic objects included in this mib are those to configure CASA, retrieve CASA's state and information about the fixed affinity cache. The following gives a list of definitions and a description of how Service Managers and Forwarding Agents interact. For a more detailed description, see the Cisco Appliance Services Architecture (CASA) document. CASA is a protocol allowing software entities (called Appliances, examples are web caches, firewalls, load balancers) to control the behavior of network hardware devices (called Forwarding Agents, examples are switches or routers) by providing a set of rules used to handle network traffic. A Network Appliance (referred to as an Appliance) is any subsystem whose purpose is to provide a specific additional value-added service to the network device, and could be implemented as a standalone box, a line card or processor card, or a software subsystem. Examples of Network Appliances would include Load Balancers, WebCaches, and Firewalls. An Appliance tells Fowarding Agents how to handle packets based on their source and destination IP addresses and ports, and IP protocol fields. This set of information is called an Affinity. A Service Manager is an Appliance that requests packet flows from Forwarding Agents through CASA. A Real Server is a physical computing engine or part of that physical computing engine that offers one or more application services to a set of clients in the network. A packet flow is a TCP connection or a sequence of UDP packets between a client and a specific Real Server, pertaining to a specific application. Flows are represented by entries in the affinity cache tables. The Service Manager requests packet flows from Forwarding Agents by sending Affinities which contains wildcards on some of the Affinity fields. Affinities that contain wildcards in some of the fields are called Wildcard Affinities. The Service Manager may send the Forwarding Agent an Affinity containing explicit values for each of the fields. These Affinities are called Fixed Affinities. Typically Wildcard Affinities are used to instruct the Forwarding Agent to send packets received by the Forwarding Agent, which match the Wildcard Affinity, to the Service Manager. When the Service Manager receives the matching packet, the Service Manager typically will send the Forwarding Agent a Fixed Affinity. The Forwarding Agent uses Fixed Affinities to match packets coming from the network, execute any processing required on that packet, and forward that packet to a destination IP address (designated in the Fixed Affinity) called the Dispatch Address. When an IP packet arrives at the Forwarding Agent, the Forwarding Agent attempts to match the packet with the Fixed Affinities in the Fixed Affinity cache. If there is no match, an attempt is made to match the packet with the list of Wildcard Affinities. If there is no match the packet is routed normally. If there is a match with a Wildcard Affinity, the Forwarding Agent sends the packet to the Service Manager who will send the Forwarding Manager a Fixed Affinity which provides information on how to process IP packets similar to the one received by the Forwarding Agent. Processing of such packets may include sending the packet to the Service Manager. Such packets are called Interest Packets. Alternatively a Tickle Packet may be sent to the Service Manager which is an indication that a matched packet has been received by the Forwarding Agent. Reference: Cisco Appliance Services Architecture (CASA) document. _______________________________________ ( ) ( N E T W O R K ) (_______________________________________) | | | + |Service Manager|-+ + ++ | F. Agent | | F. Agent | | F. Agent | + | | | ___|_________________|______________|__ ( ) ( N E T W O R K ) (_______________________________________)" REVISION "200209180000Z" DESCRIPTION "Initial version of this MIB module." ::= { ciscoMgmt 122 }
ciscoCasaMIB OBJECT IDENTIFIER ::= { ciscoMgmt 122 }
Vendor: Cisco
Module: CISCO-CASA-MIB
[Automatically extracted from oidview.com]
ciscoCasaMIB MODULE-IDENTITY LAST-UPDATED "200209180000Z" 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: [email protected]" DESCRIPTION "This MIB contains the basic objects for managing a Cisco Appliance Services Architecture (CASA) Entity. A CASA Entity can be a Manager or a Forwarding Agent as defined below. The basic objects included in this mib are those to configure CASA, retrieve CASA's state and information about the fixed affinity cache. The following gives a list of definitions and a description of how Service Managers and Forwarding Agents interact. For a more detailed description, see the Cisco Appliance Services Architecture (CASA) document. CASA is a protocol allowing software entities (called Appliances, examples are web caches, firewalls, load balancers) to control the behavior of network hardware devices (called Forwarding Agents, examples are switches or routers) by providing a set of rules used to handle network traffic. A Network Appliance (referred to as an Appliance) is any subsystem whose purpose is to provide a specific additional value-added service to the network device, and could be implemented as a standalone box, a line card or processor card, or a software subsystem. Examples of Network Appliances would include Load Balancers, WebCaches, and Firewalls. An Appliance tells Fowarding Agents how to handle packets based on their source and destination IP addresses and ports, and IP protocol fields. This set of information is called an Affinity. A Service Manager is an Appliance that requests packet flows from Forwarding Agents through CASA. A Real Server is a physical computing engine or part of that physical computing engine that offers one or more application services to a set of clients in the network. A packet flow is a TCP connection or a sequence of UDP packets between a client and a specific Real Server, pertaining to a specific application. Flows are represented by entries in the affinity cache tables. The Service Manager requests packet flows from Forwarding Agents by sending Affinities which contains wildcards on some of the Affinity fields. Affinities that contain wildcards in some of the fields are called Wildcard Affinities. The Service Manager may send the Forwarding Agent an Affinity containing explicit values for each of the fields. These Affinities are called Fixed Affinities. Typically Wildcard Affinities are used to instruct the Forwarding Agent to send packets received by the Forwarding Agent, which match the Wildcard Affinity, to the Service Manager. When the Service Manager receives the matching packet, the Service Manager typically will send the Forwarding Agent a Fixed Affinity. The Forwarding Agent uses Fixed Affinities to match packets coming from the network, execute any processing required on that packet, and forward that packet to a destination IP address (designated in the Fixed Affinity) called the Dispatch Address. When an IP packet arrives at the Forwarding Agent, the Forwarding Agent attempts to match the packet with the Fixed Affinities in the Fixed Affinity cache. If there is no match, an attempt is made to match the packet with the list of Wildcard Affinities. If there is no match the packet is routed normally. If there is a match with a Wildcard Affinity, the Forwarding Agent sends the packet to the Service Manager who will send the Forwarding Manager a Fixed Affinity which provides information on how to process IP packets similar to the one received by the Forwarding Agent. Processing of such packets may include sending the packet to the Service Manager. Such packets are called Interest Packets. Alternatively a Tickle Packet may be sent to the Service Manager which is an indication that a matched packet has been received by the Forwarding Agent. Reference: Cisco Appliance Services Architecture (CASA) document. _______________________________________ ( ) ( N E T W O R K ) (_______________________________________) | | | + |Service Manager|-+ + ++ | F. Agent | | F. Agent | | F. Agent | + | | | ___|_________________|______________|__ ( ) ( N E T W O R K ) (_______________________________________)" REVISION "200209180000Z" DESCRIPTION "Initial version of this MIB module." ::= { ciscoMgmt 122 }
ciscoCasaMIB MODULE-IDENTITY LAST-UPDATED "200209180000Z" 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: [email protected]" DESCRIPTION "This MIB contains the basic objects for managing a Cisco Appliance Services Architecture (CASA) Entity. A CASA Entity can be a Manager or a Forwarding Agent as defined below. The basic objects included in this mib are those to configure CASA, retrieve CASA's state and information about the fixed affinity cache. The following gives a list of definitions and a description of how Service Managers and Forwarding Agents interact. For a more detailed description, see the Cisco Appliance Services Architecture (CASA) document. CASA is a protocol allowing software entities (called Appliances, examples are web caches, firewalls, load balancers) to control the behavior of network hardware devices (called Forwarding Agents, examples are switches or routers) by providing a set of rules used to handle network traffic. A Network Appliance (referred to as an Appliance) is any subsystem whose purpose is to provide a specific additional value-added service to the network device, and could be implemented as a standalone box, a line card or processor card, or a software subsystem. Examples of Network Appliances would include Load Balancers, WebCaches, and Firewalls. An Appliance tells Fowarding Agents how to handle packets based on their source and destination IP addresses and ports, and IP protocol fields. This set of information is called an Affinity. A Service Manager is an Appliance that requests packet flows from Forwarding Agents through CASA. A Real Server is a physical computing engine or part of that physical computing engine that offers one or more application services to a set of clients in the network. A packet flow is a TCP connection or a sequence of UDP packets between a client and a specific Real Server, pertaining to a specific application. Flows are represented by entries in the affinity cache tables. The Service Manager requests packet flows from Forwarding Agents by sending Affinities which contains wildcards on some of the Affinity fields. Affinities that contain wildcards in some of the fields are called Wildcard Affinities. The Service Manager may send the Forwarding Agent an Affinity containing explicit values for each of the fields. These Affinities are called Fixed Affinities. Typically Wildcard Affinities are used to instruct the Forwarding Agent to send packets received by the Forwarding Agent, which match the Wildcard Affinity, to the Service Manager. When the Service Manager receives the matching packet, the Service Manager typically will send the Forwarding Agent a Fixed Affinity. The Forwarding Agent uses Fixed Affinities to match packets coming from the network, execute any processing required on that packet, and forward that packet to a destination IP address (designated in the Fixed Affinity) called the Dispatch Address. When an IP packet arrives at the Forwarding Agent, the Forwarding Agent attempts to match the packet with the Fixed Affinities in the Fixed Affinity cache. If there is no match, an attempt is made to match the packet with the list of Wildcard Affinities. If there is no match the packet is routed normally. If there is a match with a Wildcard Affinity, the Forwarding Agent sends the packet to the Service Manager who will send the Forwarding Manager a Fixed Affinity which provides information on how to process IP packets similar to the one received by the Forwarding Agent. Processing of such packets may include sending the packet to the Service Manager. Such packets are called Interest Packets. Alternatively a Tickle Packet may be sent to the Service Manager which is an indication that a matched packet has been received by the Forwarding Agent. Reference: Cisco Appliance Services Architecture (CASA) document. _______________________________________ ( ) ( N E T W O R K ) (_______________________________________) | | | + |Service Manager|-+ + ++ | F. Agent | | F. Agent | | F. Agent | + | | | ___|_________________|______________|__ ( ) ( N E T W O R K ) (_______________________________________)" REVISION "200209180000Z" DESCRIPTION "Initial version of this MIB module." ::= { ciscoMgmt 122 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.9.9.122.1 | ciscoCasaMIBObjects | 4 | 64 | None |
| 1.3.6.1.4.1.9.9.122.2 | ciscoCasaMIBNotificationPrefix | 2 | 2 | None |
| 1.3.6.1.4.1.9.9.122.3 | ciscoCasaMIBConformance | 2 | 9 | None |
To many brothers! Only 100 nearest brothers are shown.
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| ... | ||||
| 1.3.6.1.4.1.9.9.72 | ciscoCipCmpcMIB | 3 | 46 | This is the Management Information Base (MIB) module for objects used to manage the Cisco Multi-Path Channel (MPC) support on Cis… |
| 1.3.6.1.4.1.9.9.73 | ciscoCipTgMIB | 2 | 98 | This is the Management Information Base (MIB) module for objects used to manage Transmission Groups (TGs) in Cisco Mainframe Chan… |
| 1.3.6.1.4.1.9.9.74 | ciscoDlswExtMIB | 3 | 134 | The MIB module for management of Cisco specific Data Link Switching protocol enhancements. DLSw is described in RFC 1795 and RFC… |
| 1.3.6.1.4.1.9.9.76 | ciscoDlcSwitchMIB | 2 | 55 | This is the MIB module for objects used to manage FRAS sessions to the endstation. These objects are specific to downstream or end… |
| 1.3.6.1.4.1.9.9.77 | ciscoLecExtMIB | 3 | 12 | This MIB module is a Cisco extension to the ATM Forum's LANE Client MIB. |
| 1.3.6.1.4.1.9.9.78 | ciscoAtmSigDiagMIB | 2 | 58 | The MIB module to facilitate the diagnosis of failures of ATM Signalling requests. Through this MIB, an ATM device retains infor… |
| 1.3.6.1.4.1.9.9.80 | ciscoFtpClientMIB | 2 | 29 | The MIB module for invoking Internet File Transfer Protocol (FTP) operations for network management purposes. |
| 1.3.6.1.4.1.9.9.81 | ciscoBulkFileMIB | 3 | 63 | The MIB module for creating and deleting bulk files of SNMP data for file transfer. |
| 1.3.6.1.4.1.9.9.82 | ciscoStpExtensionsMIB | 3 | 300 | The MIB module for managing Cisco extensions to the 802.1D Spanning Tree Protocol (STP). |
| 1.3.6.1.4.1.9.9.83 | ciscoWredMIB | 2 | 26 | Cisco WRED MIB - Overview Cisco Weighted Random Early Detection/Drop is a method which avoids traffic congestion on an output int… |
| 1.3.6.1.4.1.9.9.84 | ciscoIpStatMIB | 2 | 34 | Cisco IP Statistics MIB - Overview This MIB incorporates objects to provide support for the Cisco IP statistics as implemented in… |
| 1.3.6.1.4.1.9.9.85 | ciscoCasIfMIB | 2 | 119 | Channel Associated Signal Interface MIB module. This MIB manages the generic CAS (Channel Associated Signal)or DS0 clear channel … |
| 1.3.6.1.4.1.9.9.86 | ciscoDspMgmtMIB | 4 | 141 | ciscoDspMgmtMIB MODULE-IDENTITY LAST-UPDATED "200008140000Z" ORGANIZATION "Cisco Systems, Inc." CONTACT-INFO " Cisco Systems Cu… |
| 1.3.6.1.4.1.9.9.87 | ciscoC2900MIB | 3 | 133 | The MIB module for Catalyst 2900 enterprise specific information |
| 1.3.6.1.4.1.9.9.88 | ciscoAtmExtMIB | 3 | 50 | ciscoAtmExtMIB MODULE-IDENTITY LAST-UPDATED "9706200000Z" ORGANIZATION "Cisco Systems, Inc." CONTACT-INFO " Cisco Systems Custo… |
| 1.3.6.1.4.1.9.9.89 | csCugMIB | 2 | 24 | This MIB module is for closed user group support (virtual private networks). |
| 1.3.6.1.4.1.9.9.91 | entitySensorMIB, ciscoEntitySensorMIB | 3 | 42 | The CISCO-ENTITY-SENSOR-MIB is used to monitor the values of sensors in the Entity-MIB (RFC 2037) entPhysicalTable. |
| 1.3.6.1.4.1.9.9.92 | ciscoEntityAssetMIB | 3 | 29 | Monitor the asset information of items in the ENTITY-MIB (RFC 2037) entPhysical table. |
| 1.3.6.1.4.1.9.9.94 | ciscoAtmPvcMIB | 2 | 19 | PVC's (Permanent Virtual Channel) can carry bridged PDUs (BPDUs) using the encapsulation method detailed in RFC1483. This is an alt… |
| 1.3.6.1.4.1.9.9.95 | ciscoAlpsMIB | 3 | 222 | The MIB module for Airline Protocol Support. ************************************************************** * … |
| 1.3.6.1.4.1.9.9.96 | ciscoConfigCopyMIB | 3 | 40 | This MIB facilitates writing of configuration files of an SNMP Agent running Cisco's IOS in the following ways: to and from the n… |
| 1.3.6.1.4.1.9.9.97 | ciscoSwitchEngineMIB | 3 | 385 | This MIB module defines management objects for Cisco Layer 2/3 switches. These devices may either have a single (central) switch… |
| 1.3.6.1.4.1.9.9.98 | ciscoPagpMIB | 2 | 52 | The MIB module for configuration of Fast Etherchannel and the operation of the Port Aggregation Protocol (PAgP). These features a… |
| 1.3.6.1.4.1.9.9.99 | ciscoLocalDirectorMIB | 3 | 88 | The MIB module to view information about LocalDirector. The Cisco LocalDirector is a device designed for the purpose of load balan… |
| 1.3.6.1.4.1.9.9.101 | ciscoSwitchCgmpMIB | 2 | 18 | Switch-side Cisco Group Management Protocol MIB for Layer 2 Switch devices. |
| 1.3.6.1.4.1.9.9.102 | ciscoMediaMailDialControlMIB | 2 | 63 | This MIB module enhances the IETF Dial Control MIB (RFC2128) for providing management of dial peers on both a circuit-switched te… |
| 1.3.6.1.4.1.9.9.103 | ciscoRmonConfigMIB | 3 | 123 | This module defines configuration extensions for some of the IETF RMON MIBs. The following terms are used throughout this MIB: A S… |
| 1.3.6.1.4.1.9.9.105 | ciscoC8500RedundancyMIB | 3 | 49 | This MIB allows management of redundancy of CPU and switch cards for the Catalyst 8540 switch, and other products with similar im… |
| 1.3.6.1.4.1.9.9.106 | ciscoHsrpMIB | 3 | 38 | ciscoHsrpMIB MODULE-IDENTITY LAST-UPDATED "9808030000Z" ORGANIZATION "Cisco Systems, Inc." CONTACT-INFO " Cisco Systems Custome… |
| 1.3.6.1.4.1.9.9.107 | ciscoHsrpExtMIB | 2 | 36 | ciscoHsrpExtMIB MODULE-IDENTITY LAST-UPDATED "9808030000Z" ORGANIZATION "Cisco Systems, Inc." CONTACT-INFO " Cisco Systems Cust… |
| 1.3.6.1.4.1.9.9.109 | ciscoProcessMIB | 3 | 187 | The MIB module to describe active system processes. |
| 1.3.6.1.4.1.9.9.110 | ciscoAtmSwitchFrRmMIB | 3 | 30 | This MIB module describes a set of objects used for switch Resource Management (RM) for Frame Relay/Frame based User-to-Network (… |
| 1.3.6.1.4.1.9.9.112 | ciscoAtmSwitchFrIwfMIB | 2 | 109 | A MIB module for managing Frame Relay to ATM interworking connections, and Frame Relay to Frame Relay switched connections via an… |
| 1.3.6.1.4.1.9.9.113 | ciscoCarMIB | 2 | 36 | Cisco CAR MIB - Overview Cisco Weighted Rate-limit, known as Commited Access Rate (CAR), is a traffic control method which uses a… |
| 1.3.6.1.4.1.9.9.114 | ciscoCableSpectrumMIB | 3 | 162 | This is the MIB Module for Cable Spectrum Management for DOCSIS-compliant Cable Modem Termination Systems (CMTS). Spectrum manage… |
| 1.3.6.1.4.1.9.9.115 | ciscoCasaFaMIB | 3 | 78 | This MIB module in conjunction with the CISCO-CASA-MIB, defines the SNMP management information base for managing the Cisco Appli… |
| 1.3.6.1.4.1.9.9.116 | ciscoDocsExtMIB | 3 | 235 | This is the MIB module for the Cisco specific extension objects of Data Over Cable Service, Radio Frequency interface. There is … |
| 1.3.6.1.4.1.9.9.117 | ciscoEntityFRUControlMIB | 3 | 147 | The CISCO-ENTITY-FRU-CONTROL-MIB is used to monitor and configure operational status of Field Replaceable Units (FRUs) and other … |
| 1.3.6.1.4.1.9.9.118 | ciscoUdldpMIB | 3 | 51 | Cisco Uni Direction Link Detection Protocol MIB |
| 1.3.6.1.4.1.9.9.120 | ciscoNetworkRegistrarMIB | 3 | 125 | MIB for Cisco Network Registrar (CNR). |
| 1.3.6.1.4.1.9.9.121 | ciscoAtmNetworkClockMIB | 3 | 53 | The MIB module for management of network clock distribution and the Network Clock Distribution Protocol (NCDP) in Cisco de… |
| 1.3.6.1.4.1.9.9.124 | ciscoCallResourcePoolMIB | 3 | 114 | The MIB module for call resource pool management. This MIB supports the resource pool manager feature of CISCO IOS. This feature … |
| 1.3.6.1.4.1.9.9.125 | ciscoWANRsrcPartMIB | 2 | 55 | The MIB module to manage resource partition objects. A resource partition is configured on a virtual interface (ifType value atmV… |
| 1.3.6.1.4.1.9.9.126 | ciscoSonetMIB | 3 | 136 | The MIB module to describe SONET/SDH interfaces objects. This is an extension to the standard SONET MIB(RFC 2558). |
| 1.3.6.1.4.1.9.9.128 | ciscoVlanIfTableRelationshipMIB | 1 | 12 | ciscoVlanIftableRelationshipMIB |
| 1.3.6.1.4.1.9.9.129 | ciscoAtmVirtualIfMIB | 2 | 139 | The MIB module to manage ATM Virtual interface objects. ATM virtual interfaces are configured on a physical line. |
| 1.3.6.1.4.1.9.9.130 | ciscoAdslDmtLineMIB | 3 | 72 | This MIB module serves as an enterprise-specific extension of the ADSL-LINE-MIB. The structure of this MIB module shadows the st… |
| 1.3.6.1.4.1.9.9.131 | ciscoSystemMIB | 3 | 57 | The systemGroup (see RFC 1907) provides a standard set of basic system information. This MIB module contains Cisco-defined exten… |
| 1.3.6.1.4.1.9.9.132 | ciscoDs3MIB | 2 | 140 | The MIB module to describe DS3 line objects. This is an extension to the standard DS3 MIB(RFC 2496). |
| 1.3.6.1.4.1.9.9.133 | ciscoAtmCellLayerMIB | 1 | 138 | The MIB module to describe ATM cell layer objects and statistics of a physical line. |
| 1.3.6.1.4.1.9.9.134 | ciscoClusterMIB | 3 | 49 | The MIB module for the management of a group of devices called a 'cluster'. A cluster comprises: 1. A command switch, which is a… |
| 1.3.6.1.4.1.9.9.135 | ciscoWirelessP2pBpiMIB | 3 | 66 | This is the MIB Module for the Baseline Privacy Interface (BPI) at Point to Point Wireless Radio Card. This is a specialization o… |
| 1.3.6.1.4.1.9.9.136 | ciscoWirelessIfMIB | 3 | 307 | This is the MIB Module for the Cisco Wireless Radio Point to Point interface specification. I) Relationship of the Cisco Wireless… |
| 1.3.6.1.4.1.9.9.137 | ciscoWirelessTextualConventions | 0 | 0 | This module defines textual conventions used in Cisco Wireless MIBs. |
| 1.3.6.1.4.1.9.9.138 | ciscoEntityAlarmMIB | 3 | 66 | This MIB module defines the managed objects that support the monitoring of alarms generated by physical entities contained by the… |
| 1.3.6.1.4.1.9.9.139 | ciscoEntityProvMIB | 3 | 13 | This MIB module defines the objects that support provisioning of 'container' class physical entities. Provisioning sets up a 'co… |
| 1.3.6.1.4.1.9.9.140 | ciscoCopsClientMIB | 3 | 43 | This MIB module is for configuration & statistic query of Common Open Policy Service(COPS) client feature on the Cisco device. C… |
| 1.3.6.1.4.1.9.9.141 | ciscoVSIControllerMIB | 2 | 21 | This MIB module is used for configuring ATM Capable Switch to be aware of VSI Controller information. Terminolgies used: VSI … |
| 1.3.6.1.4.1.9.9.144 | ciscoTransactionConnectionMIB | 2 | 66 | The MIB module for retrieving Cisco Transaction Connection configuration and status. Cisco Transaction Connection routes transac… |
| 1.3.6.1.4.1.9.9.145 | ciscoWanModuleMIB | 3 | 32 | The MIB to configure Connection Specific parameters and statistics related information in a Service Module. The Service Module(SM… |
| 1.3.6.1.4.1.9.9.146 | ciscoCallApplicationMIB | 2 | 548 | This MIB allows management of call applications on a network device. A 'call application' is a software module that processes cal… |
| 1.3.6.1.4.1.9.9.147 | ciscoFirewallMIB | 3 | 75 | MIB module for monitoring Cisco Firewalls. |
| 1.3.6.1.4.1.9.9.148 | ciscoBgpPolAcctMIB | 2 | 15 | BGP policy based accounting information |
| 1.3.6.1.4.1.9.9.149 | ciscoAdslLineCapMIB | 3 | 46 | This MIB module serves as an enterprise-specific extension of the ADSL-LINE-MIB. The structure of this MIB module shadows the st… |
| 1.3.6.1.4.1.9.9.150 | ciscoAAASessionMIB | 3 | 31 | This MIB module provides data for accounting sessions based on Authentication, Authorization, Accounting (AAA) protocols. Referenc… |
| 1.3.6.1.4.1.9.9.151 | ciscoL2L3IfConfigMIB | 2 | 11 | Interface switchport mode configuration management MIB. This MIB is used to monitor and control configuration of interface switch… |
| 1.3.6.1.4.1.9.9.152 | ciscoSipUaMIB | 4 | 504 | Cisco User Agent Session Initiation Protocol (SIP) MIB module. SIP is an application-layer signalling protocol for creating, mod… |
| 1.3.6.1.4.1.9.9.154 | ciscoIdslLineMIB | 3 | 148 | This MIB module describes IDSL (ISDN Digital Line Subscriber) line interfaces. The structure of this module resembles that of th… |
| 1.3.6.1.4.1.9.9.155 | ciscoSdslLineMIB | 3 | 170 | This MIB module describes all variations of the symmetric DSL line interfaces. The structure of this module resembles and mainta… |
| 1.3.6.1.4.1.9.9.156 | ciscoCcmMIB | 3 | 487 | The MIB Module for the management of a Cisco Unified Communications Manager (CUCM) application running with a Cisco Communication… |
| 1.3.6.1.4.1.9.9.157 | ciscoCdmaPdsnMIB | 3 | 984 | This MIB is to support the CDMA PDSN (Packet Data Serving Node) feature. A CDMA2000 network supports wireless data communication… |
| 1.3.6.1.4.1.9.9.158 | ciscoAAAClientMIB | 3 | 25 | This MIB module provides data for authentication method priority based on Authentication, Authorization, Accounting (AAA) protoco… |
| 1.3.6.1.4.1.9.9.159 | ciscoQosPolicyConfigMIB | 3 | 35 | This MIB module defines managed objects that support the policy source configuration of Quality of Service (QoS) on the device. T… |
| 1.3.6.1.4.1.9.9.160 | ciscoCircuitInterfaceMIB | 2 | 11 | The MIB module to configure the circuit description for an interface. The circuit description can be used to describe and identify… |
| 1.3.6.1.4.1.9.9.161 | ciscoSlbMIB | 3 | 279 | The MIB for managing Server Load Balancing Manager(s), such as the Cisco IOS SLB product. This MIB includes instrumentation for t… |
| 1.3.6.1.4.1.9.9.162 | ciscoVsiMasterMIB | 3 | 100 | This MIB module contains objects related to the master side of the Virtual Switch Interface protocol used for control of ATM swit… |
| 1.3.6.1.4.1.9.9.163 | ciscoCallTrackerMIB | 3 | 104 | CISCO-CALL-TRACKER-MIB |
| 1.3.6.1.4.1.9.9.164 | ciscoCallTrackerTCPMIB | 3 | 25 | This MIB module provides TCP service connection related data for tracking the progress and status of a call. This module extends t… |
| 1.3.6.1.4.1.9.9.165 | ciscoCallTrackerModemMIB | 3 | 97 | This MIB module provides modem call related data for tracking the progress and status of a call. This module extends tables defin… |
| 1.3.6.1.4.1.9.9.166 | ciscoCBQosMIB | 2 | 544 | Cisco Class-Based QoS MIB ********************************** Overview ********************************** This MIB provides read acc… |
| 1.3.6.1.4.1.9.9.167 | ciscoWirelessDocsIfMib | 3 | 140 | This is the MIB Module for MCNS compliant Radio Frequency (RF) interfaces in wireless point-to-multipoint subscriber units (SU) a… |
| 1.3.6.1.4.1.9.9.168 | ciscoNtpMIB | 3 | 87 | This MIB module defines a MIB which provides mechanisms to monitor an NTP server. The MIB is derived from the Technical Report #Ma… |
| 1.3.6.1.4.1.9.9.169 | ciscoWirelessDocsExtMIB | 3 | 99 | This MIB module defines Cisco-specific objects that add to the functionality defined in CISCO-WIRELESS-DOCS-IF-MIB. These objects … |
| 1.3.6.1.4.1.9.9.170 | ciscoWirelessPhyMIB | 2 | 112 | This is the MIB Module for the Cisco Wireless Radio Point to MultiPoint interface. |
| 1.3.6.1.4.1.9.9.171 | ciscoIpSecFlowMonitorMIB | 3 | 507 | This is a MIB Module for monitoring the structures in IPSec-based Virtual Private Networks. The MIB has been designed to be adopt… |
| 1.3.6.1.4.1.9.9.172 | ciscoIpSecPolMapMIB | 3 | 21 | The MIB module maps the IPSec entities created dynamically to the policy entities that caused them. This is an appendix to the IPS… |
| ... | ||||