This MIB module provides management of voice tone
signal as static injected tone for Land Mobile Radio
The tone signal includes tone, pause, guard/idle tone.
User can configure a sequence of tone and pause to
be played out before any voice sample is played out.
These tones are used to wake up the radio and
select the radio channel. During the voice playout,
a configured guard tone will be mixed with the voice
to keep the radio active. For some radio systems,
there is no need for the guard tone, but a configured
idle tone is needed to inform the radio that the
channel is idle. It is possible that the radio system
will generate guard/idle tone. In that case,
the IOS can instruct the DSP to filter out the radio
generated guard/idle tone by enabling digital filter.
Digital filter is able to filter out either 1950HZ or
2175HZ tone.
Parsed from file CISCO-VOICE-LMR-MIB.mib
Module: CISCO-VOICE-LMR-MIB
This MIB module provides management of voice tone
signal as static injected tone for Land Mobile Radio
The tone signal includes tone, pause, guard/idle tone.
User can configure a sequence of tone and pause to
be played out before any voice sample is played out.
These tones are used to wake up the radio and
select the radio channel. During the voice playout,
a configured guard tone will be mixed with the voice
to keep the radio active. For some radio systems,
there is no need for the guard tone, but a configured
idle tone is needed to inform the radio that the
channel is idle. It is possible that the radio system
will generate guard/idle tone. In that case,
the IOS can instruct the DSP to filter out the radio
generated guard/idle tone by enabling digital filter.
Digital filter is able to filter out either 1950HZ or
2175HZ tone.
Parsed from file CISCO-VOICE-LMR-MIB.my.txt
Company: None
Module: CISCO-VOICE-LMR-MIB
Cisco Embedded Resource Manager (ERM) MIB.
The Embedded Resource Manager (ERM) is a framework which
helps in effectively managing resources such as cpu, memory,
buffers, etc. There are two important scenarios where the ERM
framework would be useful:
1. Resource Depletion
- how to gracefully handle a situation where the system
runs out of a finite resource.
2. Resource Separation
- how to share resources fairly between different entities
in the system such that activity of one entity does not
adversely affect others.
The ERM framework has the following entities:
1. Resource Owner
Resource Owner (RO) provides resources to one or more
resource users. Example: cpu, memory and buffer.
The resource owner doesn't mean the physical resource.
For example, 'memory' resource owner would actually
mean the memory manager rather than the physical memory.
2. Resource User Type
Resource User Type (RUT) is a template which defines
a set of resource owners from where resources can be
obtained by any of the resource users instantiated from
the resource user type.
3. Resource User
Resource User (RU) is a logical entity or application
that consumes one or more resources. Resource users are
instantiated from the Resource User Type. Resource user
can also be called as 'instance of a resource user type'.
A resource user registers with a resource user type and
thus it is indirectly registered with all resource owners
defined by the resource user type.
4. Resource User Group
Resource User Group (RG) is a logical entity which contains
group of resource users. It would hence forth be referred
as Resource Group. In some cases (for example, multiple
users with same name), user may want to set threshold value
for sum of resource utilized by a group of resource users.
In such case, those resource users can be grouped/added
under a resource group. Then, user can apply a resource
policy to the resource group.
5. Resource Usage Monitor
This is also called as Resource Monitor (RM). The resource
monitor is a logical entity or application that monitors
resource owner, resource user, resource policy and resource
owner <-> resource user relationship. When any applied
resource policy is violated, all resource monitors
monitoring the resource policy will be notified and the
resource monitor can take appropriate action based on the
resource owner and resource user attributes.
The ERM framework allows three types of thresholding:
1) System Global Thresholding
When total utilization of a resource exceeds the applied
global rising threshold value, all resource users which
consume resources from the concerned resource owner are
notified to take appropriate action. The notification
order is determined by priority of the resource users.
Resource users with a lower priority are notified first,
so as to enable lower priority resource users to reduce its
resource consumption prior to any higher priority resource
users. This order prevents higher priority resource
users to start freeing up their resource, thereby not
affecting their performance.
2) User Local Thresholding
When utilization of a resource by a specific resource user
exceeds the applied user local rising threshold value,
a notification is sent *only* to the concerned resource
user. The user local thresholding method can be used to
prevent a resource user from monopolizing any available
resources.
3) Per User Global Thresholding
When total utilization of a resource exceeds the applied
per user global rising threshold value, a notification
is sent *only* to the concerned resource user. Each
resource user can have its own per user global threshold
value (per resource owner). Per User Global Thresholding
is similar to System Global Thresholding, except that
notification for Per User Global Threshold violation is
sent only to the corresponding resource user. The main
purpose of the Per User Global Thresholding is that a
resource user can take preventive actions based on the
global resource utilization of a resource.
The Embedded Resource Manager (ERM) framework allows applying
and monitoring threshold limit for usage of resources such as
cpu, memory, buffer, etc. Exceeding any applied rising
threshold value will trigger an 'up' notification to relevant
resource user(s) and resource monitor(s) based on the type
of violated resource policy. After the 'up' notification,
if the utilization goes below the falling threshold value,
a 'down' notification will be sent to the resource user(s)
and resource monitor(s). The 'up' and 'down' notifications
do not mean the SNMP notifications/traps. Rising threshold
value and falling threshold value should be different to
avoid flapping.
The ERM framework enables configuration of resource policy
in which rising/falling threshold values for a set of
resource owners can be specified. There are two types of
resource policies which can be configured.
1) Global Resource Policy
There can be only one global resource policy applied
in the system at any point of time, though multiple
global resource policies can be configured. On violation
of a applied global resource policy, all resource users
(which consume resources from the concerned resource owner)
and resource monitors (which watch the concerned
resource owner) will be notified to take appropriate
action.
2) Local Resource Policy
The local resource policy is configured for a specific
resource user type. This policy can be applied for a
resource user (or group) of the same resource user type.
A local resource policy can be applied for more than one
resource users (or groups). Both user local thresholding
and per user global thresholding can be configured under
a local resource policy. On violation of any local resource
policy, only those resource users on which the violated
resource policy was applied, will be notified in order to
take appropriate action.
Whenever a resource is consumed, current utilization of the
resource will be compared against the applied rising
threshold value. The ERM framework provides a mechanism
to send notifications to resource user(s) and resource
monitor(s) whenever resource utilization exceeds any applied
rising threshold value or falls below any applied falling
threshold value. In such situations, the resource user(s)
can take appropriate corrective action (for example, limiting
or avoiding resource consumption). Thus, the ERM framework
helps in preventing catastrophic system failures caused by
high levels of resource depletion. The ERM framework can be
extended to all kinds of resources (for example, incoming
control plane packets) that need to be managed.
The ERM MIB module facilitates the following operations:
1. Getting information about all the above mentioned
ERM entities available in a managed system.
2. Creating/modifying/removing a resource policy.
3. Creating/modifying/removing a threshold configuration
for a particular resource policy.
4. Creating/removing a resource group.
5. Adding/removing a resource user to/from a particular
resource group.
6. Applying global resource policy.
7. Applying local resource policy for a resource user or
resource group.
ciscoVoiceLmrMIB MODULE-IDENTITY LAST-UPDATED "200410140000Z" 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 provides management of voice tone signal as static injected tone for Land Mobile Radio The tone signal includes tone, pause, guard/idle tone. User can configure a sequence of tone and pause to be played out before any voice sample is played out. These tones are used to wake up the radio and select the radio channel. During the voice playout, a configured guard tone will be mixed with the voice to keep the radio active. For some radio systems, there is no need for the guard tone, but a configured idle tone is needed to inform the radio that the channel is idle. It is possible that the radio system will generate guard/idle tone. In that case, the IOS can instruct the DSP to filter out the radio generated guard/idle tone by enabling digital filter. Digital filter is able to filter out either 1950HZ or 2175HZ tone. " REVISION "200410140000Z" DESCRIPTION "the initial version of the MIB." ::= { ciscoMgmt 510 }
ciscoVoiceLmrMIB OBJECT IDENTIFIER ::= { ciscoMgmt 510 }
Vendor: Cisco
Module: CISCO-ERM-MIB
[Automatically extracted from oidview.com]
ciscoVoiceLmrMIB MODULE-IDENTITY LAST-UPDATED "200410140000Z" 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 provides management of voice tone signal as static injected tone for Land Mobile Radio The tone signal includes tone, pause, guard/idle tone. User can configure a sequence of tone and pause to be played out before any voice sample is played out. These tones are used to wake up the radio and select the radio channel. During the voice playout, a configured guard tone will be mixed with the voice to keep the radio active. For some radio systems, there is no need for the guard tone, but a configured idle tone is needed to inform the radio that the channel is idle. It is possible that the radio system will generate guard/idle tone. In that case, the IOS can instruct the DSP to filter out the radio generated guard/idle tone by enabling digital filter. Digital filter is able to filter out either 1950HZ or 2175HZ tone. " REVISION "200410140000Z" DESCRIPTION "the initial version of the MIB." ::= { ciscoMgmt 510 }
ciscoErmMIB MODULE-IDENTITY LAST-UPDATED "200602110000Z" ORGANIZATION "Cisco Systems, Inc." CONTACT-INFO "Cisco Systems Customer Service Postal: 170 West Tasman Drive San Jose, California 95134-1706 E-mail: [email protected]" DESCRIPTION "Cisco Embedded Resource Manager (ERM) MIB. The Embedded Resource Manager (ERM) is a framework which helps in effectively managing resources such as cpu, memory, buffers, etc. There are two important scenarios where the ERM framework would be useful: 1. Resource Depletion - how to gracefully handle a situation where the system runs out of a finite resource. 2. Resource Separation - how to share resources fairly between different entities in the system such that activity of one entity does not adversely affect others. The ERM framework has the following entities: 1. Resource Owner Resource Owner (RO) provides resources to one or more resource users. Example: cpu, memory and buffer. The resource owner doesn't mean the physical resource. For example, 'memory' resource owner would actually mean the memory manager rather than the physical memory. 2. Resource User Type Resource User Type (RUT) is a template which defines a set of resource owners from where resources can be obtained by any of the resource users instantiated from the resource user type. 3. Resource User Resource User (RU) is a logical entity or application that consumes one or more resources. Resource users are instantiated from the Resource User Type. Resource user can also be called as 'instance of a resource user type'. A resource user registers with a resource user type and thus it is indirectly registered with all resource owners defined by the resource user type. 4. Resource User Group Resource User Group (RG) is a logical entity which contains group of resource users. It would hence forth be referred as Resource Group. In some cases (for example, multiple users with same name), user may want to set threshold value for sum of resource utilized by a group of resource users. In such case, those resource users can be grouped/added under a resource group. Then, user can apply a resource policy to the resource group. 5. Resource Usage Monitor This is also called as Resource Monitor (RM). The resource monitor is a logical entity or application that monitors resource owner, resource user, resource policy and resource owner <-> resource user relationship. When any applied resource policy is violated, all resource monitors monitoring the resource policy will be notified and the resource monitor can take appropriate action based on the resource owner and resource user attributes. The ERM framework allows three types of thresholding: 1) System Global Thresholding When total utilization of a resource exceeds the applied global rising threshold value, all resource users which consume resources from the concerned resource owner are notified to take appropriate action. The notification order is determined by priority of the resource users. Resource users with a lower priority are notified first, so as to enable lower priority resource users to reduce its resource consumption prior to any higher priority resource users. This order prevents higher priority resource users to start freeing up their resource, thereby not affecting their performance. 2) User Local Thresholding When utilization of a resource by a specific resource user exceeds the applied user local rising threshold value, a notification is sent *only* to the concerned resource user. The user local thresholding method can be used to prevent a resource user from monopolizing any available resources. 3) Per User Global Thresholding When total utilization of a resource exceeds the applied per user global rising threshold value, a notification is sent *only* to the concerned resource user. Each resource user can have its own per user global threshold value (per resource owner). Per User Global Thresholding is similar to System Global Thresholding, except that notification for Per User Global Threshold violation is sent only to the corresponding resource user. The main purpose of the Per User Global Thresholding is that a resource user can take preventive actions based on the global resource utilization of a resource. The Embedded Resource Manager (ERM) framework allows applying and monitoring threshold limit for usage of resources such as cpu, memory, buffer, etc. Exceeding any applied rising threshold value will trigger an 'up' notification to relevant resource user(s) and resource monitor(s) based on the type of violated resource policy. After the 'up' notification, if the utilization goes below the falling threshold value, a 'down' notification will be sent to the resource user(s) and resource monitor(s). The 'up' and 'down' notifications do not mean the SNMP notifications/traps. Rising threshold value and falling threshold value should be different to avoid flapping. The ERM framework enables configuration of resource policy in which rising/falling threshold values for a set of resource owners can be specified. There are two types of resource policies which can be configured. 1) Global Resource Policy There can be only one global resource policy applied in the system at any point of time, though multiple global resource policies can be configured. On violation of a applied global resource policy, all resource users (which consume resources from the concerned resource owner) and resource monitors (which watch the concerned resource owner) will be notified to take appropriate action. 2) Local Resource Policy The local resource policy is configured for a specific resource user type. This policy can be applied for a resource user (or group) of the same resource user type. A local resource policy can be applied for more than one resource users (or groups). Both user local thresholding and per user global thresholding can be configured under a local resource policy. On violation of any local resource policy, only those resource users on which the violated resource policy was applied, will be notified in order to take appropriate action. Whenever a resource is consumed, current utilization of the resource will be compared against the applied rising threshold value. The ERM framework provides a mechanism to send notifications to resource user(s) and resource monitor(s) whenever resource utilization exceeds any applied rising threshold value or falls below any applied falling threshold value. In such situations, the resource user(s) can take appropriate corrective action (for example, limiting or avoiding resource consumption). Thus, the ERM framework helps in preventing catastrophic system failures caused by high levels of resource depletion. The ERM framework can be extended to all kinds of resources (for example, incoming control plane packets) that need to be managed. The ERM MIB module facilitates the following operations: 1. Getting information about all the above mentioned ERM entities available in a managed system. 2. Creating/modifying/removing a resource policy. 3. Creating/modifying/removing a threshold configuration for a particular resource policy. 4. Creating/removing a resource group. 5. Adding/removing a resource user to/from a particular resource group. 6. Applying global resource policy. 7. Applying local resource policy for a resource user or resource group." REVISION "200602110000Z" DESCRIPTION "Initial version of Cisco ERM MIB module." ::= { ciscoMgmt 510 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.9.9.510.0 | ciscoErmMIBNotifs | 2 | 2 | None |
| 1.3.6.1.4.1.9.9.510.1 | ciscoErmMIBObjects, cvlMIBObjects | 5 | 157 | None |
| 1.3.6.1.4.1.9.9.510.2 | ciscoErmMIBConform, cvlMIBConformance | 2 | 14 | 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.460 | ciscoTpcMIB | 3 | 24 | The MIB module for Third Party Copy(TPC): Third Party Copy derives its name from the fact that there are three entities involved … |
| 1.3.6.1.4.1.9.9.461 | ciscoEtherCfmMIB | 3 | 39 | This MIB module defines the managed objects and notifications for Ethernet Connectivity Fault Management (CFM). CFM is an end-to-e… |
| 1.3.6.1.4.1.9.9.463 | ciscoSanTapMIB | 3 | 30 | MIB module to provide information about the SanTap service configuration. SanTap is a fibre channel switch based capability that p… |
| 1.3.6.1.4.1.9.9.466 | ciscoEthernetAccessMIB | 2 | 20 | The tables defined by this MIB module contain a collection of managed objects that are general in nature and apply to an edge dev… |
| 1.3.6.1.4.1.9.9.467 | ciscoCryptoAcceleratorMIB | 3 | 107 | The MIB module for monitoring the identity, status, activity and faults of crypto accelerator (CA) modules used in devices implem… |
| 1.3.6.1.4.1.9.9.468 | ciscoContextMappingMIB | 2 | 35 | A single SNMP agent sometimes needs to support multiple instances of the same MIB module, and does so through the use of multiple… |
| 1.3.6.1.4.1.9.9.470 | ciscoEnhancedSlbMIB | 3 | 106 | The MIB for managing Server Load Balancing Manager(s), and products supporting Server Load Balancing(SLB) features. This MIB exten… |
| 1.3.6.1.4.1.9.9.471 | ciscoFlexLinksMIB | 3 | 36 | This MIB module is for configuration and status query of Flex Links feature on the Cisco device. Flex Links are a pair of Layer 2… |
| 1.3.6.1.4.1.9.9.472 | ciscoModuleVirtualizationMIB | 3 | 35 | This MIB provides a way to create virtual contexts, and managing them. A virtual context is logical partition of a physical devi… |
| 1.3.6.1.4.1.9.9.473 | ciscoCcaMIB | 3 | 200 | The Cisco Contact Center Applications (CCCA) Management Information Base (MIB) module defines management instrumentation for appl… |
| 1.3.6.1.4.1.9.9.474 | ciscoFilterGroupMIB | 3 | 55 | The MIB module is for creating and configuring object groups to support packet filtering and access control on IP and other proto… |
| 1.3.6.1.4.1.9.9.479 | ciscoCableWidebandMIB | 3 | 77 | This is the MIB module for the support of Channel Bonding Protocol for the Cable Modem Termination System (CMTS). Wideband DOCSIS… |
| 1.3.6.1.4.1.9.9.480 | ciscoL4L7moduleResourceLimitMIB | 4 | 100 | The MIB module for managing resource classes and configuring limits(max/min) to different resources. The resource referenced in … |
| 1.3.6.1.4.1.9.9.482 | ciscoInterfaceTopNExtMIB | 3 | 16 | This MIB module is an extension to INTERFACETOPN-MIB. It provides additional management information for sorting device interfaces. |
| 1.3.6.1.4.1.9.9.483 | ciscoIpRanBackHaulMIB | 3 | 248 | This MIB provides information on the IP-RAN traffic from cell site to aggregation site in the following situations. In an GSM en… |
| 1.3.6.1.4.1.9.9.484 | ciscoNacNadMIB | 3 | 157 | This MIB module is for the configuration of a Network Access Device (NAD) on the Cisco Network Admission Control (NAC) system. End… |
| 1.3.6.1.4.1.9.9.485 | ciscoRttMonTCMIB | 0 | 0 | This MIB contains textual conventions used by CISCO-RTTMON-MIB, CISCO-RTTMON-RTP-MIB and CISCO-RTTMON-ICMP-MIB, but they are not … |
| 1.3.6.1.4.1.9.9.486 | ciscoRttMonIcmpMIB | 3 | 7 | An extension to the CISCO-RTTMON-MIB for ICMP operations. The ICMP Jitter operation provides capability to measure metrics such a… |
| 1.3.6.1.4.1.9.9.487 | ciscoRttMonRtpMIB | 3 | 8 | An extension to the CISCO-RTTMON-MIB for Cisco IP SLA RTP operation, Real-Time Transport Protocol(RFC 1889). This operation provi… |
| 1.3.6.1.4.1.9.9.488 | ciscoFirewallTc | 0 | 0 | This MIB module defines textual conventions that are commonly used in modeling management information pertaining to configuration… |
| 1.3.6.1.4.1.9.9.490 | ciscoNetintMIB | 3 | 11 | This MIB module is for Network Interrupt information on Cisco device. |
| 1.3.6.1.4.1.9.9.491 | ciscoUnifiedFirewallMIB | 3 | 235 | Overview of Cisco Firewall MIB ============================== This MIB Module models status and performance statistics pertaining … |
| 1.3.6.1.4.1.9.9.492 | ciscoCefMIB | 3 | 192 | Cisco Express Forwarding (CEF) describes a high speed switching mechanism that a router uses to forward packets from the inbound … |
| 1.3.6.1.4.1.9.9.493 | ciscoCefTextualConventions | 0 | 0 | ciscoCeftextualConventions |
| 1.3.6.1.4.1.9.9.494 | ciscoEntityRedunTcMIB | 0 | 0 | This module defines the textual conventions used within Cisco Entity Redundancy MIBs. |
| 1.3.6.1.4.1.9.9.495 | ciscoPsdClientMIB | 3 | 44 | This MIB module manages the client side functionality of the Persistent Storage Device(PSD). This MIB instrumentation is for conf… |
| 1.3.6.1.4.1.9.9.497 | cGgsnSAMIB | 3 | 247 | This MIB module manages the service-aware feature of Gateway GPRS Support Node (GGSN). This MIB is an enhancement of the CISCO-GG… |
| 1.3.6.1.4.1.9.9.498 | ciscoEntityRedunMIB | 3 | 93 | This management information module supports configuration, control and monitoring of redundancy protection for various kinds of c… |
| 1.3.6.1.4.1.9.9.500 | ciscoStackWiseMIB | 3 | 111 | This MIB module contain a collection of managed objects that apply to network devices supporting the Cisco StackWise(TM) technolo… |
| 1.3.6.1.4.1.9.9.504 | ciscoSwitchMulticastMIB | 3 | 108 | This MIB module defines management objects for the Multicast Switching features on Cisco Layer 2/3 devices. Definition of some of … |
| 1.3.6.1.4.1.9.9.505 | cpkiMIB | 3 | 44 | A networking device may provide several security services and protocols like SSL, SSH, IPSec/IKE etc. which need identities … |
| 1.3.6.1.4.1.9.9.507 | ciscoPolicyGroupMIB | 3 | 35 | The MIB module is for configuration of policy and policy group. A policy group can be described as a set of entities identified b… |
| 1.3.6.1.4.1.9.9.508 | ciscoSlbHealthMonMIB | 3 | 62 | An extension to the CISCO-SLB-EXT-MIB for SLB health monitoring probes. SLB: Server Load Balancing. Server load balancing provides… |
| 1.3.6.1.4.1.9.9.509 | ciscoWdsInfoMIB | 3 | 141 | This MIB is intended to be implemented on all Cisco network entities that provide Wireless Domain Services (WDS). The WDS provide… |
| 1.3.6.1.4.1.9.9.511 | ciscoCbpTargetTCMIB | 0 | 0 | This MIB module defines Textual Conventions for representing targets which have class based policy mappings. A target can be any … |
| 1.3.6.1.4.1.9.9.512 | ciscoLwappWlanMIB | 3 | 249 | This MIB is intended to be implemented on all those devices operating as Central Controllers (CC) that terminate the Light Weigh… |
| 1.3.6.1.4.1.9.9.513 | ciscoLwappApMIB | 4 | 386 | This MIB is intended to be implemented on all those devices operating as Central Controllers (CC) that terminate the Light Weight… |
| 1.3.6.1.4.1.9.9.514 | ciscoLwappTextualConventions | 0 | 0 | This module defines textual conventions used throughout the Cisco enterprise MIBs designed for implementation on Central Controlle… |
| 1.3.6.1.4.1.9.9.515 | ciscoLwappWebAuthMIB | 4 | 43 | This MIB is intended to be implemented on all those devices operating as Central controllers, that terminate the Light Weight Acc… |
| 1.3.6.1.4.1.9.9.516 | ciscoLwappLinkTestMIB | 3 | 57 | This MIB is intended to be implemented on all those devices operating as Central controllers, that terminate the Light Weight Acc… |
| 1.3.6.1.4.1.9.9.517 | ciscoLwappReapMIB | 3 | 63 | This MIB is intended to be implemented on all those devices operating as Central Controllers (CC) that terminate the Light Weight… |
| 1.3.6.1.4.1.9.9.518 | ciscoLwappMfpMIB | 4 | 64 | This MIB is intended to be implemented on all those devices operating as Central Controllers (CC) that terminate the Light Weight… |
| 1.3.6.1.4.1.9.9.519 | ciscoLwappIdsMIB | 3 | 28 | This MIB is intended to be implemented on all those devices operating as Central Controllers (CC) that terminate the Light Weight… |
| 1.3.6.1.4.1.9.9.520 | ciscoLwappCcxRmMIB | 3 | 45 | This MIB is intended to be implemented on all those devices operating as Central controllers, that terminate the Light Weight Acc… |
| 1.3.6.1.4.1.9.9.521 | ciscoLwappWlanSecurityMIB | 3 | 51 | This MIB is intended to be implemented on all those devices operating as Central controllers, that terminate the Light Weight Acc… |
| 1.3.6.1.4.1.9.9.522 | ciscoLwappDot11ClientCalibMIB | 3 | 50 | This MIB is intended to be implemented on all those devices operating as Central controllers, that terminate the Light Weight Acc… |
| 1.3.6.1.4.1.9.9.523 | ciscoLwappClRoamMIB | 3 | 61 | This MIB is intended to be implemented on all those devices operating as Central controllers, that terminate the Light Weight Acc… |
| 1.3.6.1.4.1.9.9.524 | ciscoLwappQosMIB | 3 | 119 | This MIB is intended to be implemented on all those devices operating as Central controllers, that terminate the Light Weight Acc… |
| 1.3.6.1.4.1.9.9.525 | ciscoLwappTsmMIB | 3 | 57 | This MIB is intended to be implemented on all those devices operating as Central controllers, that terminate the Light Weight Acc… |
| 1.3.6.1.4.1.9.9.529 | ciscoItpMsuRatesMIB | 3 | 61 | This MIB provides information used to manage the number of MTP3 MSUs transmitted and received per processor. Many of the higher … |
| 1.3.6.1.4.1.9.9.530 | ciscoNacTcMIB | 0 | 0 | This module defines the textual conventions for Cisco Network Admission Control(NAC) system. The Cisco Network Admission Control … |
| 1.3.6.1.4.1.9.9.532 | ciscoNATExtMIB | 3 | 13 | This MIB is an extension to the NAT-MIB. This MIB module includes objects for providing the NAT related statistics. Acronyms: NAT… |
| 1.3.6.1.4.1.9.9.533 | ciscoCbpTargetMIB | 3 | 25 | This MIB module defines the managed objects for representing targets which have class-based policy mappings. A target can be any… |
| 1.3.6.1.4.1.9.9.543 | ciscoLicenseMgmtMIB | 3 | 131 | The MIB module for managing licenses on the system. The licensing mechanism provides flexibility to enforce licensing for various… |
| 1.3.6.1.4.1.9.9.548 | ciscoErrDisableMIB | 3 | 43 | This MIB module provides the ability for a Network Management Station (NMS) to configure and monitor the error-disable feature vi… |
| ... | ||||