CTRON-RATE-POLICING-MIB.mib object view, vendor Enterasys-Networks-Inc

Introduction

Most network devices and programs ship with so-called MIB files to describe the parameters and meanings (i.e.: friendly names) which are available for monitoring via SNMP.
ActiveXperts Network Monitor 2024 can import vendor-specific MIB files, so it can be used to monitor specific OID's (Object Identifiers). This way, you can monitor your devices, computers, etc. by selecting your relevant OID's by name.

ActiveXperts Network Monitor 2024 can import MIB file CTRON-RATE-POLICING-MIB and use it to monitor vendor specific OID's.

CTRON-RATE-POLICING-MIB file content

Object view of CTRON-RATE-POLICING-MIB:

Scalar Object
ctRatePolicingAdminStatus	.1.3.6.1.4.1.52.4.1.2.14.7.1.1
Allows the rate policing feature to be globally enabled/disabled. A value of disable(2), functionally supersedes the ctRatePolicingRuleStatus of individual entries in the ctRatePolicingConfigTable, but does not change their actual values.
ctRatePolicingConfigLastChange	.1.3.6.1.4.1.52.4.1.2.14.7.1.2
The value of sysUpTime the last time anything in the ctRatePolicingConfigTable changed.
ctRatePolicingConfigEntry	.1.3.6.1.4.1.52.4.1.2.14.7.1.3.1
Describes a particular entry of ctRatePolicingConfigTable.
Tabular Object
ctRatePolicingResourceIndex	.1.3.6.1.4.1.52.4.1.2.14.7.1.3.1.1
This specifies a unique resource available for configuring a rate policing rule on this port. Each port has a limited number of resources available for rate policing. This index simply provides a mechanism for uniquely addressing each of these resources.
ctRatePolicingActionsAllowed	.1.3.6.1.4.1.52.4.1.2.14.7.1.3.1.2
This specifies the valid policing actions that may be taken for this port upon exceeding the threshold specified in ctRatePolicingThreshHold.
ctRatePolicingAction	.1.3.6.1.4.1.52.4.1.2.14.7.1.3.1.3
This is the action to be taken if the rate limit is exceeded. This value must be a valid action as specified by the corresponding ctRatePolicingActionsAllowed object. Also, no more than one action may be specified. Attempts to set this value outside of the aforementioned guidelines will fail.
ctRatePolicingThreshHoldMin	.1.3.6.1.4.1.52.4.1.2.14.7.1.3.1.4
The minimum rate limit value for this entry in kB per second.
ctRatePolicingThreshHold	.1.3.6.1.4.1.52.4.1.2.14.7.1.3.1.5
The rate limit value for this entry in kB per second. If the rate is exceeded the defined action in ctRatePolicingAction will be enforced. This value may not be set below the minimum rate specified in ctRatePolicingThreshHoldMin.
ctRatePolicingPriorityList	.1.3.6.1.4.1.52.4.1.2.14.7.1.3.1.6
This specifies the list of priorities to which this rule applies.
ctRatePolicingRuleStatus	.1.3.6.1.4.1.52.4.1.2.14.7.1.3.1.7
This object provides both control and status for the associated conceptual row in the table. The value of active(1) indicates that device is actively applying the rate policing rule defined by the other leaves in this row. All other read-write leaves in this row have an effective value of read-only while the row is in the active state. The value of disabled(2) indicates that this row is essentially an available resource which MAY be configured and activated.
ctRatePolicingActionsTaken	.1.3.6.1.4.1.52.4.1.2.14.7.1.3.1.8
This object counts the number of times the ctRatePolicingAction has been enforced for this particular entry.
ctRatePolicingDirectionsAllowed	.1.3.6.1.4.1.52.4.1.2.14.7.1.3.1.9
This specifies the valid policing directions that may be taken for this port.
ctRatePolicingDirection	.1.3.6.1.4.1.52.4.1.2.14.7.1.3.1.10
This specifies the direction of the traffic flow that will be limited.
Table
ctRatePolicingConfigTable	.1.3.6.1.4.1.52.4.1.2.14.7.1.3
This table allows configuration of rate policing rules on this device. Their are a limited number of resources available for rate policing, and this directly limits the number of rate policing rules that may be configured on each port. As a result this table does not support dynamic row creation, rather, all possible rows exist in either an active or disabled state. A manager application should not, however, infer that this configuration is necessarily fixed during the lifetime of the managed entity. The allocation of resources could theoretically be shifted. For example port 20 could have 3 resources and at some point suddenly have 4 or 2. Any such change would of course cause the value of ctRatePolicingConfigLastChange to change. At this time their is no defined mechanism to move these resources and there very likely never will be. This is merely a warning that manager applications should not count on this.
Object Identifier
ctRatePolicing	.1.3.6.1.4.1.52.4.1.2.14.7
The Enterasys Rate Policing MIB module allows the user to set maximum ingress rates on a per port, per priority basis.
ctRatePolicingObjects	.1.3.6.1.4.1.52.4.1.2.14.7.1
ctRatePolicingConformance	.1.3.6.1.4.1.52.4.1.2.14.7.2
ctRatePolicingGroups	.1.3.6.1.4.1.52.4.1.2.14.7.2.1
ctRatePolicingCompliances	.1.3.6.1.4.1.52.4.1.2.14.7.2.2
Group
ctRatePolicingConfigGroup	.1.3.6.1.4.1.52.4.1.2.14.7.2.1.1
A collection of objects providing device level control and status information for rate policing.