This MIB module is for Access Control Lists(ACLs) configuration
of Quality of Service (QoS) as well as Security feature on the
Cisco Catalyst 5000/6000 series switch running CatOS. It also
provides QoS configuration and statistics information.
Configuration information available through this MIB includes
Security and QoS ACL configuration for IP, IPX and Layer 2
traffic, QoS and Security configuration parameters.
Statistics available through this MIB includes QoS statistics
for Layer 3 traffic. In addition, detailed, flow-specific
statistics are also available.
This MIB module is applied in conjunction with
CISCO-QOS-POLICY-CONFIG-MIB. The configuration information
available through this MIB takes effect throughout the device
when the value of qosPrOperPolicySource object in
CISCO-QOS-POLICY-CONFIG-MIB is 'local' or applies to a specific
interface when the value of qosPrIfOperPolicySource object
in CISCO-QOS-POLICY-CONFIG-MIB which associates with that
interface is 'local' while the value of qosPrOperPolicySource is
not 'local'.
The following terms are used throughout this MIB:
ACE stands for Access Control Entry. An ACL consists of an
ordered set of ACEs. ACE is a filter which is used to
identify flows with certain characteristics. It includes
fields such as ingress/egress ports, L2(layer 2) addresses,
L3(layer 3) addresses, TCP/UDP port numbers, etc.
QoS ACE and Security ACE are very similar to each other
but the actions of the ACEs are different.
Security ACEs are compared to each packet, and each ACE
specifies whether packets that match with it are either
forwarded or dropped.
ESP: Enscrypted Security Payload.
QoS is the method which attempts to ensure that the network
requirements of different applications can be met by giving
preferential forwarding treatment to some traffic. It is
usually consisted of these steps: classification, policing,
output scheduling, marking and shaping. Classification
identifies the traffic. Policing checks if the traffic
conformed to a specified criteria. Output scheduling,
marking and shaping control how the traffic is transmitted
to the next hop.
A flow is a non-specific term for a microflow or an
aggregate flow.
Microflow is a single instance of an application to
application flow of packets which is identified by source
address, source port, destination address, destination port
and protocol id.
Aggregate flow is a collection of microflows that are
treated together as one for the purpose of QoS.
DSCP (Differentiated Services Code Point) is the six most
significant bits of the ToS field in a IP packet header.
DSCP Mutation: the previous hop(s) and the following hop(s)
of a device may reside in a different QoS domain. A QoS
domain refers to the set of QoS rules and conventions
adopted by an administrative entity. For instance, a set
of DSCP values may have a different meaning in different
domains. DSCP mutation allows a DSCP set to be mutated or
transformed in order to maintain semantic compatibility
between adjacent domains. The mutation is done via mapping
tables which maps the old DSCP value from one domain to a
new DSCP value in the other domain.
IP precedence is the three most significant bits of the ToS
field in a IP packet header.
Cos (Class of Service) is the three bits in the layer 2
header that indicates user priority value assigned to this
packet.
Trust state is a parameter configured at a physical
interface or an ACL to determine a DSCP value assigned to
a packet for QoS purpose.
In profile packet is a packet that does not cause the
committed access rate of the packet's flow to be exceeded.
Out of profile packet is a packet that cause the committed
access rate of the packet's flow to be exceeded.
To accomplish classification, the user defines an ACL describing
the specification of a traffic flow then attaches this ACL to a
physical interface or a vlan. When a packet arrives at an
interface, depending on the configured trust state at that
interface, it can either be matched against an ACL if the trust
state is not trusted or get a DSCP assigned and go directly to
output scheduling. In the former case, when the packet matches
an ACE in the attached ACL, the next step will be policing. At
the end of classification process, a packet has a DSCP value
assigned. In some platform (e.g. Catalyst 4000) that does not
support ACL configuration, classification is accomplished by
matching the Cos value of incoming packet.
A packet can be policed at microflow or aggregate flow level.
Policing is done using the token bucket algorithm.
At the end of policing process, if packet does not cause the
flow to exceed the normal rate, it will continue to the next
step. Otherwise, the packet is dropped or assigned a 'policed'
DSCP value. Some platforms support multi-rate policing. When
packet causes the flow to exceed the normal rate but not the
excess rate, it is assigned a 'policed' DSCP value. When packet
causes the flow to exceed excess rate, it is either dropped or
has a 'policed' DSCP value assigned. After policing process,
the next step is output scheduling.
Output scheduling is the process of assigning a packet to
a queue and a threshold according to the packet's Cos value.
To get its Cos value, a DSCP to Cos mapping will be performed.
This MIB also defines 'Security ACLs' which some devices support
as a mean to enforce security. Security ACLs, attached at an
ingress interface, are compared to each packet arriving at that
interface. If the packet matches an ACE in the ACLs, it is
either permitted to go through the device or blocked and
dropped or redirected to another interface.
Parsed from file CISCO-CATOS-ACL-QOS-MIB.mib
Module: CISCO-CATOS-ACL-QOS-MIB
This MIB module is for Access Control Lists(ACLs) configuration
of Quality of Service (QoS) as well as Security feature on the
Cisco Catalyst 5000/6000 series switch running CatOS. It also
provides QoS configuration and statistics information.
Configuration information available through this MIB includes
Security and QoS ACL configuration for IP, IPX and Layer 2
traffic, QoS and Security configuration parameters.
Statistics available through this MIB includes QoS statistics
for Layer 3 traffic. In addition, detailed, flow-specific
statistics are also available.
This MIB module is applied in conjunction with
CISCO-QOS-POLICY-CONFIG-MIB. The configuration information
available through this MIB takes effect throughout the device
when the value of qosPrOperPolicySource object in
CISCO-QOS-POLICY-CONFIG-MIB is 'local' or applies to a specific
interface when the value of qosPrIfOperPolicySource object
in CISCO-QOS-POLICY-CONFIG-MIB which associates with that
interface is 'local' while the value of qosPrOperPolicySource is
not 'local'.
The following terms are used throughout this MIB:
ACE stands for Access Control Entry. An ACL consists of an
ordered set of ACEs. ACE is a filter which is used to
identify flows with certain characteristics. It includes
fields such as ingress/egress ports, L2(layer 2) addresses,
L3(layer 3) addresses, TCP/UDP port numbers, etc.
QoS ACE and Security ACE are very similar to each other
but the actions of the ACEs are different.
Security ACEs are compared to each packet, and each ACE
specifies whether packets that match with it are either
forwarded or dropped.
ESP: Enscrypted Security Payload.
QoS is the method which attempts to ensure that the network
requirements of different applications can be met by giving
preferential forwarding treatment to some traffic. It is
usually consisted of these steps: classification, policing,
output scheduling, marking and shaping. Classification
identifies the traffic. Policing checks if the traffic
conformed to a specified criteria. Output scheduling,
marking and shaping control how the traffic is transmitted
to the next hop.
A flow is a non-specific term for a microflow or an
aggregate flow.
Microflow is a single instance of an application to
application flow of packets which is identified by source
address, source port, destination address, destination port
and protocol id.
Aggregate flow is a collection of microflows that are
treated together as one for the purpose of QoS.
DSCP (Differentiated Services Code Point) is the six most
significant bits of the ToS field in a IP packet header.
DSCP Mutation: the previous hop(s) and the following hop(s)
of a device may reside in a different QoS domain. A QoS
domain refers to the set of QoS rules and conventions
adopted by an administrative entity. For instance, a set
of DSCP values may have a different meaning in different
domains. DSCP mutation allows a DSCP set to be mutated or
transformed in order to maintain semantic compatibility
between adjacent domains. The mutation is done via mapping
tables which maps the old DSCP value from one domain to a
new DSCP value in the other domain.
IP precedence is the three most significant bits of the ToS
field in a IP packet header.
Cos (Class of Service) is the three bits in the layer 2
header that indicates user priority value assigned to this
packet.
Trust state is a parameter configured at a physical
interface or an ACL to determine a DSCP value assigned to
a packet for QoS purpose.
In profile packet is a packet that does not cause the
committed access rate of the packet's flow to be exceeded.
Out of profile packet is a packet that cause the committed
access rate of the packet's flow to be exceeded.
To accomplish classification, the user defines an ACL describing
the specification of a traffic flow then attaches this ACL to a
physical interface or a vlan. When a packet arrives at an
interface, depending on the configured trust state at that
interface, it can either be matched against an ACL if the trust
state is not trusted or get a DSCP assigned and go directly to
output scheduling. In the former case, when the packet matches
an ACE in the attached ACL, the next step will be policing. At
the end of classification process, a packet has a DSCP value
assigned. In some platform (e.g. Catalyst 4000) that does not
support ACL configuration, classification is accomplished by
matching the Cos value of incoming packet.
A packet can be policed at microflow or aggregate flow level.
Policing is done using the token bucket algorithm.
At the end of policing process, if packet does not cause the
flow to exceed the normal rate, it will continue to the next
step. Otherwise, the packet is dropped or assigned a 'policed'
DSCP value. Some platforms support multi-rate policing. When
packet causes the flow to exceed the normal rate but not the
excess rate, it is assigned a 'policed' DSCP value. When packet
causes the flow to exceed excess rate, it is either dropped or
has a 'policed' DSCP value assigned. After policing process,
the next step is output scheduling.
Output scheduling is the process of assigning a packet to
a queue and a threshold according to the packet's Cos value.
To get its Cos value, a DSCP to Cos mapping will be performed.
This MIB also defines 'Security ACLs' which some devices support
as a mean to enforce security. Security ACLs, attached at an
ingress interface, are compared to each packet arriving at that
interface. If the packet matches an ACE in the ACLs, it is
either permitted to go through the device or blocked and
dropped or redirected to another interface.
Parsed from file CISCO-CATOS-ACL-QOS-MIB.my.txt
Company: None
Module: CISCO-CATOS-ACL-QOS-MIB
This MIB module is for Access Control Lists(ACLs) configuration
of Quality of Service (QoS) as well as Security feature on the
Cisco Catalyst 5000/6000 series switch running CatOS. It also
provides QoS configuration and statistics information.
Configuration information available through this MIB includes
Security and QoS ACL configuration for IP, IPX and Layer 2
traffic, QoS and Security configuration parameters.
Statistics available through this MIB includes QoS statistics
for Layer 3 traffic. In addition, detailed, flow-specific
statistics are also available.
This MIB module is applied in conjunction with
CISCO-QOS-POLICY-CONFIG-MIB. The configuration information
available through this MIB takes effect throughout the device
when the value of qosPrOperPolicySource object in
CISCO-QOS-POLICY-CONFIG-MIB is 'local' or applies to a specific
interface when the value of qosPrIfOperPolicySource object
in CISCO-QOS-POLICY-CONFIG-MIB which associates with that
interface is 'local' while the value of qosPrOperPolicySource is
not 'local'.
The following terms are used throughout this MIB:
ACE stands for Access Control Entry. An ACL consists of an
ordered set of ACEs. ACE is a filter which is used to
identify flows with certain characteristics. It includes
fields such as ingress/egress ports, L2(layer 2) addresses,
L3(layer 3) addresses, TCP/UDP port numbers, etc.
QoS ACE and Security ACE are very similar to each other
but the actions of the ACEs are different.
Security ACEs are compared to each packet, and each ACE
specifies whether packets that match with it are either
forwarded or dropped.
ESP: Enscrypted Security Payload.
QoS is the method which attempts to ensure that the network
requirements of different applications can be met by giving
preferential forwarding treatment to some traffic. It is
usually consisted of these steps: classification, policing,
output scheduling, marking and shaping. Classification
identifies the traffic. Policing checks if the traffic
conformed to a specified criteria. Output scheduling,
marking and shaping control how the traffic is transmitted
to the next hop.
A flow is a non-specific term for a microflow or an
aggregate flow.
Microflow is a single instance of an application to
application flow of packets which is identified by source
address, source port, destination address, destination port
and protocol id.
Aggregate flow is a collection of microflows that are
treated together as one for the purpose of QoS.
DSCP (Differentiated Services Code Point) is the six most
significant bits of the ToS field in a IP packet header.
DSCP Mutation: the previous hop(s) and the following hop(s)
of a device may reside in a different QoS domain. A QoS
domain refers to the set of QoS rules and conventions
adopted by an administrative entity. For instance, a set
of DSCP values may have a different meaning in different
domains. DSCP mutation allows a DSCP set to be mutated or
transformed in order to maintain semantic compatibility
between adjacent domains. The mutation is done via mapping
tables which maps the old DSCP value from one domain to a
new DSCP value in the other domain.
IP precedence is the three most significant bits of the ToS
field in a IP packet header.
Cos (Class of Service) is the three bits in the layer 2
header that indicates user priority value assigned to this
packet.
Trust state is a parameter configured at a physical
interface or an ACL to determine a DSCP value assigned to
a packet for QoS purpose.
In profile packet is a packet that does not cause the
committed access rate of the packet's flow to be exceeded.
Out of profile packet is a packet that cause the committed
access rate of the packet's flow to be exceeded.
To accomplish classification, the user defines an ACL describing
the specification of a traffic flow then attaches this ACL to a
physical interface or a vlan. When a packet arrives at an
interface, depending on the configured trust state at that
interface, it can either be matched against an ACL if the trust
state is not trusted or get a DSCP assigned and go directly to
output scheduling. In the former case, when the packet matches
an ACE in the attached ACL, the next step will be policing. At
the end of classification process, a packet has a DSCP value
assigned. In some platform (e.g. Catalyst 4000) that does not
support ACL configuration, classification is accomplished by
matching the Cos value of incoming packet.
A packet can be policed at microflow or aggregate flow level.
Policing is done using the token bucket algorithm.
At the end of policing process, if packet does not cause the
flow to exceed the normal rate, it will continue to the next
step. Otherwise, the packet is dropped or assigned a 'policed'
DSCP value. Some platforms support multi-rate policing. When
packet causes the flow to exceed the normal rate but not the
excess rate, it is assigned a 'policed' DSCP value. When packet
causes the flow to exceed excess rate, it is either dropped or
has a 'policed' DSCP value assigned. After policing process,
the next step is output scheduling.
Output scheduling is the process of assigning a packet to
a queue and a threshold according to the packet's Cos value.
To get its Cos value, a DSCP to Cos mapping will be performed.
This MIB also defines 'Security ACLs' which some devices support
as a mean to enforce security. Security ACLs, attached at an
ingress interface, are compared to each packet arriving at that
interface. If the packet matches an ACE in the ACLs, it is
either permitted to go through the device or blocked and
dropped or redirected to another interface.
ciscoCatOSAclQosMIB MODULE-IDENTITY LAST-UPDATED "200711020000Z" 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 module is for Access Control Lists(ACLs) configuration of Quality of Service (QoS) as well as Security feature on the Cisco Catalyst 5000/6000 series switch running CatOS. It also provides QoS configuration and statistics information. Configuration information available through this MIB includes Security and QoS ACL configuration for IP, IPX and Layer 2 traffic, QoS and Security configuration parameters. Statistics available through this MIB includes QoS statistics for Layer 3 traffic. In addition, detailed, flow-specific statistics are also available. This MIB module is applied in conjunction with CISCO-QOS-POLICY-CONFIG-MIB. The configuration information available through this MIB takes effect throughout the device when the value of qosPrOperPolicySource object in CISCO-QOS-POLICY-CONFIG-MIB is 'local' or applies to a specific interface when the value of qosPrIfOperPolicySource object in CISCO-QOS-POLICY-CONFIG-MIB which associates with that interface is 'local' while the value of qosPrOperPolicySource is not 'local'. The following terms are used throughout this MIB: ACE stands for Access Control Entry. An ACL consists of an ordered set of ACEs. ACE is a filter which is used to identify flows with certain characteristics. It includes fields such as ingress/egress ports, L2(layer 2) addresses, L3(layer 3) addresses, TCP/UDP port numbers, etc. QoS ACE and Security ACE are very similar to each other but the actions of the ACEs are different. Security ACEs are compared to each packet, and each ACE specifies whether packets that match with it are either forwarded or dropped. ESP: Enscrypted Security Payload. QoS is the method which attempts to ensure that the network requirements of different applications can be met by giving preferential forwarding treatment to some traffic. It is usually consisted of these steps: classification, policing, output scheduling, marking and shaping. Classification identifies the traffic. Policing checks if the traffic conformed to a specified criteria. Output scheduling, marking and shaping control how the traffic is transmitted to the next hop. A flow is a non-specific term for a microflow or an aggregate flow. Microflow is a single instance of an application to application flow of packets which is identified by source address, source port, destination address, destination port and protocol id. Aggregate flow is a collection of microflows that are treated together as one for the purpose of QoS. DSCP (Differentiated Services Code Point) is the six most significant bits of the ToS field in a IP packet header. DSCP Mutation: the previous hop(s) and the following hop(s) of a device may reside in a different QoS domain. A QoS domain refers to the set of QoS rules and conventions adopted by an administrative entity. For instance, a set of DSCP values may have a different meaning in different domains. DSCP mutation allows a DSCP set to be mutated or transformed in order to maintain semantic compatibility between adjacent domains. The mutation is done via mapping tables which maps the old DSCP value from one domain to a new DSCP value in the other domain. IP precedence is the three most significant bits of the ToS field in a IP packet header. Cos (Class of Service) is the three bits in the layer 2 header that indicates user priority value assigned to this packet. Trust state is a parameter configured at a physical interface or an ACL to determine a DSCP value assigned to a packet for QoS purpose. In profile packet is a packet that does not cause the committed access rate of the packet's flow to be exceeded. Out of profile packet is a packet that cause the committed access rate of the packet's flow to be exceeded. To accomplish classification, the user defines an ACL describing the specification of a traffic flow then attaches this ACL to a physical interface or a vlan. When a packet arrives at an interface, depending on the configured trust state at that interface, it can either be matched against an ACL if the trust state is not trusted or get a DSCP assigned and go directly to output scheduling. In the former case, when the packet matches an ACE in the attached ACL, the next step will be policing. At the end of classification process, a packet has a DSCP value assigned. In some platform (e.g. Catalyst 4000) that does not support ACL configuration, classification is accomplished by matching the Cos value of incoming packet. A packet can be policed at microflow or aggregate flow level. Policing is done using the token bucket algorithm. At the end of policing process, if packet does not cause the flow to exceed the normal rate, it will continue to the next step. Otherwise, the packet is dropped or assigned a 'policed' DSCP value. Some platforms support multi-rate policing. When packet causes the flow to exceed the normal rate but not the excess rate, it is assigned a 'policed' DSCP value. When packet causes the flow to exceed excess rate, it is either dropped or has a 'policed' DSCP value assigned. After policing process, the next step is output scheduling. Output scheduling is the process of assigning a packet to a queue and a threshold according to the packet's Cos value. To get its Cos value, a DSCP to Cos mapping will be performed. This MIB also defines 'Security ACLs' which some devices support as a mean to enforce security. Security ACLs, attached at an ingress interface, are compared to each packet arriving at that interface. If the packet matches an ACE in the ACLs, it is either permitted to go through the device or blocked and dropped or redirected to another interface." REVISION "200711020000Z" DESCRIPTION "Add the following groups: caqDownloadClassifierGroup, caqIpOperClassifierGroup, caqSecurityDownloadAclInfoGroup, caqSecurityDownloadIpAceGroup, caqIfDownloadAclMapGroup, caqIfIpPhoneMapGroup, caqArpLoggingSourceGroup, caqIpAceTypeGroup." REVISION "200607150000Z" DESCRIPTION "Add 'include' enumeration value for caqSecurityAction. Add caqQosL3StatsRateGroup, caqQosL3StatsPeakGroup, caqAggPolicerOctetsRateGroup, caqAggPolicerPacketsRateGroup, caqAggPolicerOctetsPeakGroup, caqAggPolicerPacketsPeakGroup, caqQosPortRateGroup, caqQosPortPeakGroup, caqSecurityActionDnldAceGroup." REVISION "200507260000Z" DESCRIPTION "Add 'matchEapoudp' and 'matchUrlRedirect' enum value for caqIpProtocolMatchCriteria object." REVISION "200405260000Z" DESCRIPTION "Add the following groups to support ACL hit count configuration and statistics: caqAclFeatureGroup caqAclHitCountGroup Add the following groups to support additional matching criteria for MAC ACE and MAC packet classify feature on VLAN: caqMacAceExtGroup. caqMacPktClassifyVlanGroup." REVISION "200311260000Z" DESCRIPTION "Add the following objects to support group name for source and destination fields in caqIpAceTable: caqIpAceSrcGroup caqIpAceDestGroup." REVISION "200310280000Z" DESCRIPTION "Add caqIfSecurityAclConfigGroup to support port ACL." REVISION "200309300000Z" DESCRIPTION "Add the dhcpSnooping bit for caqSecurityRateLimitFeatures object. Fix a typo in the DESCRIPTION clause for caqSecurityAction object." REVISION "200307010000Z" DESCRIPTION "Deprecate caqSecurityRedirectPortList object and add caqSecurityRedirect2kPortList to support up to 2048 bridge ports." REVISION "200303050000Z" DESCRIPTION "Add the following objects and tables: caqClassifierMapDirection, caqIpAceSecurityId, caqDscpRewriteEnabled, caqAggPolicerOctets, caqAggPolicerNRExceedOctets, caqAggPolicerERExceedOctets, caqDscpMutationMapTable, caqVlanMutationIdMapTable, caqQosDefaultActionTable." REVISION "200210100000Z" DESCRIPTION "Add the caqLoggingGroup, caqArpInspGroup and caqSecurityRateLimitGroup to support security ACL logging, security ACL features rate limit and ARP Inspection device configuration." REVISION "200201170000Z" DESCRIPTION "Add the caqIfTrustDeviceGroup and caqQosExcessBurstGroup to support Qos information on excess burst size and trusted device configuration." REVISION "200110180000Z" DESCRIPTION "Add the caqPbfObjects group and modify the caqSecurityActionTable to support policy based forwarding." REVISION "200102150000Z" DESCRIPTION "Add the following objects: caqAggPolicerName, caqAggPolicerPackets, caqAggPolicerNRExceedPackets, caqAggPolicerERExceedPackets." REVISION "200102070000Z" DESCRIPTION "Initial version of this MIB module." ::= { ciscoMgmt 179 }
ciscoCatOSAclQosMIB OBJECT IDENTIFIER ::= { ciscoMgmt 179 }
Vendor: Cisco
Module: CISCO-CATOS-ACL-QOS-MIB
[Automatically extracted from oidview.com]
ciscoCatOSAclQosMIB MODULE-IDENTITY LAST-UPDATED "200711020000Z" 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 module is for Access Control Lists(ACLs) configuration of Quality of Service (QoS) as well as Security feature on the Cisco Catalyst 5000/6000 series switch running CatOS. It also provides QoS configuration and statistics information. Configuration information available through this MIB includes Security and QoS ACL configuration for IP, IPX and Layer 2 traffic, QoS and Security configuration parameters. Statistics available through this MIB includes QoS statistics for Layer 3 traffic. In addition, detailed, flow-specific statistics are also available. This MIB module is applied in conjunction with CISCO-QOS-POLICY-CONFIG-MIB. The configuration information available through this MIB takes effect throughout the device when the value of qosPrOperPolicySource object in CISCO-QOS-POLICY-CONFIG-MIB is 'local' or applies to a specific interface when the value of qosPrIfOperPolicySource object in CISCO-QOS-POLICY-CONFIG-MIB which associates with that interface is 'local' while the value of qosPrOperPolicySource is not 'local'. The following terms are used throughout this MIB: ACE stands for Access Control Entry. An ACL consists of an ordered set of ACEs. ACE is a filter which is used to identify flows with certain characteristics. It includes fields such as ingress/egress ports, L2(layer 2) addresses, L3(layer 3) addresses, TCP/UDP port numbers, etc. QoS ACE and Security ACE are very similar to each other but the actions of the ACEs are different. Security ACEs are compared to each packet, and each ACE specifies whether packets that match with it are either forwarded or dropped. ESP: Enscrypted Security Payload. QoS is the method which attempts to ensure that the network requirements of different applications can be met by giving preferential forwarding treatment to some traffic. It is usually consisted of these steps: classification, policing, output scheduling, marking and shaping. Classification identifies the traffic. Policing checks if the traffic conformed to a specified criteria. Output scheduling, marking and shaping control how the traffic is transmitted to the next hop. A flow is a non-specific term for a microflow or an aggregate flow. Microflow is a single instance of an application to application flow of packets which is identified by source address, source port, destination address, destination port and protocol id. Aggregate flow is a collection of microflows that are treated together as one for the purpose of QoS. DSCP (Differentiated Services Code Point) is the six most significant bits of the ToS field in a IP packet header. DSCP Mutation: the previous hop(s) and the following hop(s) of a device may reside in a different QoS domain. A QoS domain refers to the set of QoS rules and conventions adopted by an administrative entity. For instance, a set of DSCP values may have a different meaning in different domains. DSCP mutation allows a DSCP set to be mutated or transformed in order to maintain semantic compatibility between adjacent domains. The mutation is done via mapping tables which maps the old DSCP value from one domain to a new DSCP value in the other domain. IP precedence is the three most significant bits of the ToS field in a IP packet header. Cos (Class of Service) is the three bits in the layer 2 header that indicates user priority value assigned to this packet. Trust state is a parameter configured at a physical interface or an ACL to determine a DSCP value assigned to a packet for QoS purpose. In profile packet is a packet that does not cause the committed access rate of the packet's flow to be exceeded. Out of profile packet is a packet that cause the committed access rate of the packet's flow to be exceeded. To accomplish classification, the user defines an ACL describing the specification of a traffic flow then attaches this ACL to a physical interface or a vlan. When a packet arrives at an interface, depending on the configured trust state at that interface, it can either be matched against an ACL if the trust state is not trusted or get a DSCP assigned and go directly to output scheduling. In the former case, when the packet matches an ACE in the attached ACL, the next step will be policing. At the end of classification process, a packet has a DSCP value assigned. In some platform (e.g. Catalyst 4000) that does not support ACL configuration, classification is accomplished by matching the Cos value of incoming packet. A packet can be policed at microflow or aggregate flow level. Policing is done using the token bucket algorithm. At the end of policing process, if packet does not cause the flow to exceed the normal rate, it will continue to the next step. Otherwise, the packet is dropped or assigned a 'policed' DSCP value. Some platforms support multi-rate policing. When packet causes the flow to exceed the normal rate but not the excess rate, it is assigned a 'policed' DSCP value. When packet causes the flow to exceed excess rate, it is either dropped or has a 'policed' DSCP value assigned. After policing process, the next step is output scheduling. Output scheduling is the process of assigning a packet to a queue and a threshold according to the packet's Cos value. To get its Cos value, a DSCP to Cos mapping will be performed. This MIB also defines 'Security ACLs' which some devices support as a mean to enforce security. Security ACLs, attached at an ingress interface, are compared to each packet arriving at that interface. If the packet matches an ACE in the ACLs, it is either permitted to go through the device or blocked and dropped or redirected to another interface." REVISION "200711020000Z" DESCRIPTION "Add the following groups: caqDownloadClassifierGroup, caqIpOperClassifierGroup, caqSecurityDownloadAclInfoGroup, caqSecurityDownloadIpAceGroup, caqIfDownloadAclMapGroup, caqIfIpPhoneMapGroup, caqArpLoggingSourceGroup, caqIpAceTypeGroup." REVISION "200607150000Z" DESCRIPTION "Add 'include' enumeration value for caqSecurityAction. Add caqQosL3StatsRateGroup, caqQosL3StatsPeakGroup, caqAggPolicerOctetsRateGroup, caqAggPolicerPacketsRateGroup, caqAggPolicerOctetsPeakGroup, caqAggPolicerPacketsPeakGroup, caqQosPortRateGroup, caqQosPortPeakGroup, caqSecurityActionDnldAceGroup." REVISION "200507260000Z" DESCRIPTION "Add 'matchEapoudp' and 'matchUrlRedirect' enum value for caqIpProtocolMatchCriteria object." REVISION "200405260000Z" DESCRIPTION "Add the following groups to support ACL hit count configuration and statistics: caqAclFeatureGroup caqAclHitCountGroup Add the following groups to support additional matching criteria for MAC ACE and MAC packet classify feature on VLAN: caqMacAceExtGroup. caqMacPktClassifyVlanGroup." REVISION "200311260000Z" DESCRIPTION "Add the following objects to support group name for source and destination fields in caqIpAceTable: caqIpAceSrcGroup caqIpAceDestGroup." REVISION "200310280000Z" DESCRIPTION "Add caqIfSecurityAclConfigGroup to support port ACL." REVISION "200309300000Z" DESCRIPTION "Add the dhcpSnooping bit for caqSecurityRateLimitFeatures object. Fix a typo in the DESCRIPTION clause for caqSecurityAction object." REVISION "200307010000Z" DESCRIPTION "Deprecate caqSecurityRedirectPortList object and add caqSecurityRedirect2kPortList to support up to 2048 bridge ports." REVISION "200303050000Z" DESCRIPTION "Add the following objects and tables: caqClassifierMapDirection, caqIpAceSecurityId, caqDscpRewriteEnabled, caqAggPolicerOctets, caqAggPolicerNRExceedOctets, caqAggPolicerERExceedOctets, caqDscpMutationMapTable, caqVlanMutationIdMapTable, caqQosDefaultActionTable." REVISION "200210100000Z" DESCRIPTION "Add the caqLoggingGroup, caqArpInspGroup and caqSecurityRateLimitGroup to support security ACL logging, security ACL features rate limit and ARP Inspection device configuration." REVISION "200201170000Z" DESCRIPTION "Add the caqIfTrustDeviceGroup and caqQosExcessBurstGroup to support Qos information on excess burst size and trusted device configuration." REVISION "200110180000Z" DESCRIPTION "Add the caqPbfObjects group and modify the caqSecurityActionTable to support policy based forwarding." REVISION "200102150000Z" DESCRIPTION "Add the following objects: caqAggPolicerName, caqAggPolicerPackets, caqAggPolicerNRExceedPackets, caqAggPolicerERExceedPackets." REVISION "200102070000Z" DESCRIPTION "Initial version of this MIB module." ::= { ciscoMgmt 179 }
ciscoCatOSAclQosMIB MODULE-IDENTITY LAST-UPDATED "200711020000Z" 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 module is for Access Control Lists(ACLs) configuration of Quality of Service (QoS) as well as Security feature on the Cisco Catalyst 5000/6000 series switch running CatOS. It also provides QoS configuration and statistics information. Configuration information available through this MIB includes Security and QoS ACL configuration for IP, IPX and Layer 2 traffic, QoS and Security configuration parameters. Statistics available through this MIB includes QoS statistics for Layer 3 traffic. In addition, detailed, flow-specific statistics are also available. This MIB module is applied in conjunction with CISCO-QOS-POLICY-CONFIG-MIB. The configuration information available through this MIB takes effect throughout the device when the value of qosPrOperPolicySource object in CISCO-QOS-POLICY-CONFIG-MIB is 'local' or applies to a specific interface when the value of qosPrIfOperPolicySource object in CISCO-QOS-POLICY-CONFIG-MIB which associates with that interface is 'local' while the value of qosPrOperPolicySource is not 'local'. The following terms are used throughout this MIB: ACE stands for Access Control Entry. An ACL consists of an ordered set of ACEs. ACE is a filter which is used to identify flows with certain characteristics. It includes fields such as ingress/egress ports, L2(layer 2) addresses, L3(layer 3) addresses, TCP/UDP port numbers, etc. QoS ACE and Security ACE are very similar to each other but the actions of the ACEs are different. Security ACEs are compared to each packet, and each ACE specifies whether packets that match with it are either forwarded or dropped. ESP: Enscrypted Security Payload. QoS is the method which attempts to ensure that the network requirements of different applications can be met by giving preferential forwarding treatment to some traffic. It is usually consisted of these steps: classification, policing, output scheduling, marking and shaping. Classification identifies the traffic. Policing checks if the traffic conformed to a specified criteria. Output scheduling, marking and shaping control how the traffic is transmitted to the next hop. A flow is a non-specific term for a microflow or an aggregate flow. Microflow is a single instance of an application to application flow of packets which is identified by source address, source port, destination address, destination port and protocol id. Aggregate flow is a collection of microflows that are treated together as one for the purpose of QoS. DSCP (Differentiated Services Code Point) is the six most significant bits of the ToS field in a IP packet header. DSCP Mutation: the previous hop(s) and the following hop(s) of a device may reside in a different QoS domain. A QoS domain refers to the set of QoS rules and conventions adopted by an administrative entity. For instance, a set of DSCP values may have a different meaning in different domains. DSCP mutation allows a DSCP set to be mutated or transformed in order to maintain semantic compatibility between adjacent domains. The mutation is done via mapping tables which maps the old DSCP value from one domain to a new DSCP value in the other domain. IP precedence is the three most significant bits of the ToS field in a IP packet header. Cos (Class of Service) is the three bits in the layer 2 header that indicates user priority value assigned to this packet. Trust state is a parameter configured at a physical interface or an ACL to determine a DSCP value assigned to a packet for QoS purpose. In profile packet is a packet that does not cause the committed access rate of the packet's flow to be exceeded. Out of profile packet is a packet that cause the committed access rate of the packet's flow to be exceeded. To accomplish classification, the user defines an ACL describing the specification of a traffic flow then attaches this ACL to a physical interface or a vlan. When a packet arrives at an interface, depending on the configured trust state at that interface, it can either be matched against an ACL if the trust state is not trusted or get a DSCP assigned and go directly to output scheduling. In the former case, when the packet matches an ACE in the attached ACL, the next step will be policing. At the end of classification process, a packet has a DSCP value assigned. In some platform (e.g. Catalyst 4000) that does not support ACL configuration, classification is accomplished by matching the Cos value of incoming packet. A packet can be policed at microflow or aggregate flow level. Policing is done using the token bucket algorithm. At the end of policing process, if packet does not cause the flow to exceed the normal rate, it will continue to the next step. Otherwise, the packet is dropped or assigned a 'policed' DSCP value. Some platforms support multi-rate policing. When packet causes the flow to exceed the normal rate but not the excess rate, it is assigned a 'policed' DSCP value. When packet causes the flow to exceed excess rate, it is either dropped or has a 'policed' DSCP value assigned. After policing process, the next step is output scheduling. Output scheduling is the process of assigning a packet to a queue and a threshold according to the packet's Cos value. To get its Cos value, a DSCP to Cos mapping will be performed. This MIB also defines 'Security ACLs' which some devices support as a mean to enforce security. Security ACLs, attached at an ingress interface, are compared to each packet arriving at that interface. If the packet matches an ACE in the ACLs, it is either permitted to go through the device or blocked and dropped or redirected to another interface." REVISION "200711020000Z" DESCRIPTION "Add the following groups: caqDownloadClassifierGroup, caqIpOperClassifierGroup, caqSecurityDownloadAclInfoGroup, caqSecurityDownloadIpAceGroup, caqIfDownloadAclMapGroup, caqIfIpPhoneMapGroup, caqArpLoggingSourceGroup, caqIpAceTypeGroup." REVISION "200607150000Z" DESCRIPTION "Add 'include' enumeration value for caqSecurityAction. Add caqQosL3StatsRateGroup, caqQosL3StatsPeakGroup, caqAggPolicerOctetsRateGroup, caqAggPolicerPacketsRateGroup, caqAggPolicerOctetsPeakGroup, caqAggPolicerPacketsPeakGroup, caqQosPortRateGroup, caqQosPortPeakGroup, caqSecurityActionDnldAceGroup." REVISION "200507260000Z" DESCRIPTION "Add 'matchEapoudp' and 'matchUrlRedirect' enum value for caqIpProtocolMatchCriteria object." REVISION "200405260000Z" DESCRIPTION "Add the following groups to support ACL hit count configuration and statistics: caqAclFeatureGroup caqAclHitCountGroup Add the following groups to support additional matching criteria for MAC ACE and MAC packet classify feature on VLAN: caqMacAceExtGroup. caqMacPktClassifyVlanGroup." REVISION "200311260000Z" DESCRIPTION "Add the following objects to support group name for source and destination fields in caqIpAceTable: caqIpAceSrcGroup caqIpAceDestGroup." REVISION "200310280000Z" DESCRIPTION "Add caqIfSecurityAclConfigGroup to support port ACL." REVISION "200309300000Z" DESCRIPTION "Add the dhcpSnooping bit for caqSecurityRateLimitFeatures object. Fix a typo in the DESCRIPTION clause for caqSecurityAction object." REVISION "200307010000Z" DESCRIPTION "Deprecate caqSecurityRedirectPortList object and add caqSecurityRedirect2kPortList to support up to 2048 bridge ports." REVISION "200303050000Z" DESCRIPTION "Add the following objects and tables: caqClassifierMapDirection, caqIpAceSecurityId, caqDscpRewriteEnabled, caqAggPolicerOctets, caqAggPolicerNRExceedOctets, caqAggPolicerERExceedOctets, caqDscpMutationMapTable, caqVlanMutationIdMapTable, caqQosDefaultActionTable." REVISION "200210100000Z" DESCRIPTION "Add the caqLoggingGroup, caqArpInspGroup and caqSecurityRateLimitGroup to support security ACL logging, security ACL features rate limit and ARP Inspection device configuration." REVISION "200201170000Z" DESCRIPTION "Add the caqIfTrustDeviceGroup and caqQosExcessBurstGroup to support Qos information on excess burst size and trusted device configuration." REVISION "200110180000Z" DESCRIPTION "Add the caqPbfObjects group and modify the caqSecurityActionTable to support policy based forwarding." REVISION "200102150000Z" DESCRIPTION "Add the following objects: caqAggPolicerName, caqAggPolicerPackets, caqAggPolicerNRExceedPackets, caqAggPolicerERExceedPackets." REVISION "200102070000Z" DESCRIPTION "Initial version of this MIB module." ::= { ciscoMgmt 179 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.9.9.179.1 | ciscoCatOSAclQosMIBObjects | 10 | 405 | None |
| 1.3.6.1.4.1.9.9.179.2 | caqMIBNotifications | 0 | 0 | None |
| 1.3.6.1.4.1.9.9.179.3 | caqMIBConformance | 2 | 62 | 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.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… |
| 1.3.6.1.4.1.9.9.173 | ciscoPrivateVlanMIB | 2 | 56 | The MIB module to support Private VLAN feature on Cisco's switching devices. |
| 1.3.6.1.4.1.9.9.174 | ciscoMobileIpMIB | 3 | 533 | An extension to the IETF MIB module defined in RFC-2006 for managing Mobile IP implementations. Mobile IP introduces the followin… |
| 1.3.6.1.4.1.9.9.175 | ciscoIfLinkConfigMIB | 2 | 15 | The MIB module for configuration of bulk distribution (de-multiplexing of traffic from higher-bandwidth to lower-bandwidth interf… |
| 1.3.6.1.4.1.9.9.176 | ciscoRFMIB | 3 | 117 | This MIB provides configuration control and status for the Redundancy Framework (RF) subsystem. RF provides a mechanism for logic… |
| 1.3.6.1.4.1.9.9.177 | ciscoSaaApmMIB | 3 | 38 | Acronyms and Terms: SAA - Service Assurance Agent APM - Application Performance Monitoring A MIB for controlling SAA APM. APM provi… |
| 1.3.6.1.4.1.9.9.178 | ciscoContentEngineMIB | 3 | 263 | The MIB module for the Cisco Content Engine from Cisco Systems, Inc. |
| 1.3.6.1.4.1.9.9.180 | ciscoWirelessRfMetricsMIB | 5 | 99 | This is the MIB Module for the Cisco Wireless Radio Point to MultiPoint interface specification. |
| 1.3.6.1.4.1.9.9.181 | ciscoWirelessLinkMetricsMIB | 4 | 141 | This is the MIB Module for the Cisco Wireless Radio Point to MultiPoint interface link metrics specification. Glossary The followin… |
| 1.3.6.1.4.1.9.9.183 | ciscoGprsAccPtMIB | 3 | 338 | This MIB module supports access point configuration for GGSN in a GPRS system. GPRS [1] is a GSM network providing mobile wireles… |
| 1.3.6.1.4.1.9.9.184 | ciscoPimMIB | 3 | 36 | This MIB module defines the cisco specific variables for Protocol Independent Multicast (PIM) management. These definitions are a… |
| 1.3.6.1.4.1.9.9.185 | ciscoBertMIB | 2 | 46 | The MIB module to configure and perform Bit Error Rate Testing (BERT) on DS3, DS1/E1 and DS0/DS0Bundle interfaces. Bit error rate… |
| 1.3.6.1.4.1.9.9.187 | ciscoBgp4MIB | 4 | 137 | An extension to the IETF BGP4 MIB module defined in RFC 1657. Following is the terminology associated with Border Gateway Protocol… |
| 1.3.6.1.4.1.9.9.188 | cGtpMIB | 3 | 248 | This MIB module manages the GPRS Tunnelling Protocol (GTP) on GGSN and SGSN. GPRS provides wireless access to packet data network… |
| 1.3.6.1.4.1.9.9.189 | ciscoPortQosMIB | 3 | 114 | Cisco PORT QOS MIB - Overview This MIB module is for the management of Cisco's per port rate-limiting and traffic shaping on L3 sw… |
| 1.3.6.1.4.1.9.9.190 | ciscoVoiceAppsMIB | 3 | 40 | The MIB Module for the management of Cisco Voice Applications. This MIB is designed to work in conjunction with the SYSAPPL-MIB … |
| 1.3.6.1.4.1.9.9.191 | ciscoIpUplinkRedirectMIB | 3 | 11 | This MIB module is for the configuration of Cisco IP Uplink Redirect feature. |
| 1.3.6.1.4.1.9.9.192 | ciscoGprsChargingMIB | 3 | 315 | This MIB module manages the charging related function on the GGSN node of a GPRS system. The following diagram illustrates a simp… |
| 1.3.6.1.4.1.9.9.194 | ciscoPppoeMIB | 3 | 89 | Cisco PPPoE sessions management MIB Module. |
| 1.3.6.1.4.1.9.9.195 | ciscoEntityExtMIB | 3 | 64 | This MIB is an extension of the ENTITY-MIB specified in RFC2737. This MIB module contains Cisco-defined extensions to the entit… |
| 1.3.6.1.4.1.9.9.197 | ciscoDistDirMIB | 3 | 123 | Cisco Distributed Director MIB. The Cisco Distributed Director provides global Internet scalability and increased performance as … |
| 1.3.6.1.4.1.9.9.198 | ciscoRfSupMIB | 3 | 58 | This MIB was designed to complement the CISCO-RF-MIB by providing additional optional status and configuration control for redund… |
| 1.3.6.1.4.1.9.9.199 | ciscoSmFileDownloadMIB | 3 | 23 | The MIB module for downloading files to the Service Modules specifically designed for an architecture containing a controller car… |
| 1.3.6.1.4.1.9.9.201 | ciscoSwitchUsageMIB | 3 | 15 | This MIB defines objects related to statistics for the usage of switch fabric. The switch fabric is used by the incoming packets … |
| 1.3.6.1.4.1.9.9.202 | ciscoOscpMIB | 3 | 52 | The MIB module for managing the Cisco Optical Supervisory Channel Protocol (OSCP). The OSCP is used to determine and maintain wav… |
| 1.3.6.1.4.1.9.9.204 | ciscoXdslLineMIB | 2 | 32 | The tables defined by this MIB module contain a collection of managed objects that are general in nature and apply to different t… |
| 1.3.6.1.4.1.9.9.215 | ciscoMacNotificationMIB | 3 | 72 | This MIB module is for configuration of the MAC notification feature. MAC notification is a mechanism to inform monitoring device… |
| 1.3.6.1.4.1.9.9.216 | ciscoContentNetworkMIB | 3 | 34 | This MIB module defines objects for Content Network devices. A Content Network is a collection of devices that optimizes the deli… |
| 1.3.6.1.4.1.9.9.217 | ciscoCat6kCrossbarMIB | 3 | 210 | The Catalyst 6000 Crossbar MIB provides instrumentation for configuration and operation of the crossbar switching fabric module, … |
| 1.3.6.1.4.1.9.9.218 | ciscoIfThresholdMIB | 3 | 65 | ciscoIfthresholdMIB |
| 1.3.6.1.4.1.9.9.219 | ciscoVoiceDnisMIB | 3 | 24 | The MIB module provides management support for Dialer Number Information Service (DNIS) mapping. A DNIS entry is associated with… |
| 1.3.6.1.4.1.9.9.220 | ciscoPaeMIB | 3 | 231 | Cisco Port Access Entity (PAE) module for managing IEEE Std 802.1x. This MIB provides Port Access Entity information that are eith… |
| 1.3.6.1.4.1.9.9.221 | ciscoEnhancedMemPoolMIB | 3 | 87 | New MIB module for monitoring the memory pools of all physical entities on a managed system. |
| 1.3.6.1.4.1.9.9.222 | ciscoEnhancedWredMIB | 3 | 70 | Cisco WRED MIB - Overview Cisco Weighted Random Early Detection/Drop (WRED) is a method which avoids traffic congestion on an outp… |
| 1.3.6.1.4.1.9.9.223 | ciscoWanNcdpMIB | 3 | 58 | This MIB module is intended for the management of network clock distribution and the Network Clock Distribution Protocol (NCDP) i… |
| 1.3.6.1.4.1.9.9.224 | ciscoDevExcepReportMIB | 3 | 29 | This mib defines the SNMP objects to report exceptions to north-bound NMS. The devices implementing this MIB monitor the status of… |
| 1.3.6.1.4.1.9.9.225 | ciscoLagMIB | 3 | 56 | Cisco Link Aggregation module for managing IEEE Std 802.3ad. This MIB provides Link Aggregation information that are either exclud… |
| 1.3.6.1.4.1.9.9.226 | ciscoNDEMIB | 4 | 17 | The Netflow Data Export (NDE) MIB provides instrumentation for configuration and operation of the Netflow Data Export feature. A … |
| 1.3.6.1.4.1.9.9.227 | ciscoItpAclMIB | 3 | 45 | The MIB for managing access lists that control messages transported over Signalling System No. 7 (SS7) Network via Cisco IP Trans… |
| 1.3.6.1.4.1.9.9.228 | ciscoItpRtMIB | 3 | 47 | This MIB is for managing information required to route messages transported over Signalling System No. 7 (SS7) Network via Cisco … |
| 1.3.6.1.4.1.9.9.229 | ciscoDs1ExtMIB | 2 | 129 | The MIB module to describe DS1/E1 interface objects. This is an extension to the standard DS1/E1 MIB (RFC 2495). Unless mentioned… |
| ... | ||||