CISCO-SERVICE-CONTROLLER-MIB

        This MIB module defines objects describing traffic controllers
used by a service control entity.
        
A service control entity is a network device which monitors and
controls traffic. The service control enitity is used as a
platform for different service control applications which may
perform monitoring operations beyond packet counting and delve
deeper into the contents of network traffic, such as deep packet
inspection.
It provides programmable stateful inspection of bidirectional
traffic flows, maps these flows to users or subscribers, and can
control traffic flow according to different attributes.
        
A service control entity traffic controller can act as a rather
simple policer or implement more complicated logic in
controlling traffic, up to actual applicative attributes of the
traffic itself.
        
The global service controller is a controller component
implemented by the service control entity, which acts as a
rather simple policer for traffic transiting through the service
control entity. A global service controller may be configured
per service control entity interface with a configurable
bandwidth limitation. The controller is responsible for the
enforcement of the bandwith limitation configured in the service
control entity.
        
Aggregative global controller is a mechanism that allows 
dynamic bandwidth allocation between two global controllers
that reside on the same direction of two links. Regularly, a
global controller is configured per physical port.
When aggregative global controller is configured, the relevant 
per-port global controllers are configured dynamically and 
automatically by the aggregative global controller mechanism.
        
Primary bandwidth controller controls the total of subscriber
traffic and manage the number of bandwidth controller. 
Its main properties are committed information rate, 
peak information rate, and relative priority.
    
Source file
CISCO-SERVICE-CONTROLLER-MIB
Last revised
Identity
ciscoServiceControllerMIB
Base OID
1.3.6.1.4.1.9.9.667
Imported Objects
CISCO-SMI ciscoMgmt
ENTITY-MIB entPhysicalIndex
SNMP-FRAMEWORK-MIB SnmpAdminString
SNMPv2-CONF MODULE-COMPLIANCE (no object page) OBJECT-GROUP (no object page)
SNMPv2-SMI Gauge32 MODULE-IDENTITY (no object page) OBJECT-TYPE (no object page) Unsigned32
Net-SNMP examples using the cisco MIB directory Show commands

These commands use the standard Observium installation path and load the selected MIB variant before the RFC and Net-SNMP directories.

Translate the module identity
/usr/bin/snmptranslate -Pud -Ir -On -m 'CISCO-SERVICE-CONTROLLER-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'CISCO-SERVICE-CONTROLLER-MIB::ciscoServiceControllerMIB'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'CISCO-SERVICE-CONTROLLER-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'CISCO-SERVICE-CONTROLLER-MIB::ciscoServiceControllerMIB'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (28)
.1.3.6.1.4.1.9.9.667
.1.3.6.1.4.1.9.9.667.0
.1.3.6.1.4.1.9.9.667.0.1
.1.3.6.1.4.1.9.9.667.0.1.1
Unsigned32
.1.3.6.1.4.1.9.9.667.0.1.1.1
.1.3.6.1.4.1.9.9.667.0.1.1.2
OctetString
.1.3.6.1.4.1.9.9.667.0.1.1.3
Enumeration
.1.3.6.1.4.1.9.9.667.0.1.1.4
Unsigned32
.1.3.6.1.4.1.9.9.667.0.1.1.5
percentUnsigned32
.1.3.6.1.4.1.9.9.667.0.1.1.6
.1.3.6.1.4.1.9.9.667.0.2
.1.3.6.1.4.1.9.9.667.0.2.1
Enumeration
.1.3.6.1.4.1.9.9.667.0.2.1.1
Unsigned32
.1.3.6.1.4.1.9.9.667.0.2.1.2
.1.3.6.1.4.1.9.9.667.0.2.1.3
.1.3.6.1.4.1.9.9.667.0.2.1.4
.1.3.6.1.4.1.9.9.667.0.3
.1.3.6.1.4.1.9.9.667.0.3.1
Unsigned32
.1.3.6.1.4.1.9.9.667.0.3.1.1
Enumeration
.1.3.6.1.4.1.9.9.667.0.3.1.2
Unsigned32
.1.3.6.1.4.1.9.9.667.0.3.1.3
.1.3.6.1.4.1.9.9.667.0.3.1.4
.1.3.6.1.4.1.9.9.667.0.3.1.5
.1.3.6.1.4.1.9.9.667.0.3.1.6
Unsigned32
.1.3.6.1.4.1.9.9.667.0.3.1.7
.1.3.6.1.4.1.9.9.667.1
.1.3.6.1.4.1.9.9.667.1.1
.1.3.6.1.4.1.9.9.667.1.2
Dependencies (8) 5 direct · 3 transitive Show tree and compile order Hide dependency details

Each imported module is resolved in the importing module's source directory first, then through the normal default-variant rules.

Dependency tree
Compliance Statements (2)

OID .1.3.6.1.4.1.9.9.667.1.1.1
The compliance statement for SNMP entities that implement
version 1 of the Cisco Service Controller MIB.
Required groups

OID .1.3.6.1.4.1.9.9.667.1.1.2
This compliance statement specifies the minimal requirements an
implementation must meet in order to claim full compliance with
the definition of the CISCO-SERVICE-CONTROLLER-MIB.
Required groups
Object refinements
ObjectAccessSyntaxDescription
cscAggregativeGlobalControllersLimit readonly
Write access is not required.
cscAggregativeGlobalControllersRate readonly
Write access is not required.
cscAggregativeGlobalControllersLinkEnforcedRate readonly
Write access is not required.
cscAggregativeGlobalControllersCommittedInformationRate readonly
Write access is not required.
cscAggregativeGlobalControllersPeakInformationRate readonly
Write access is not required.
cscAggregativeGlobalControllersAssuranceLevel readonly
Write access is not required.