CISCO-SLB-DFP-MIB
AI MIB Summary
The CISCO-SLB-DFP-MIB monitors real server congestion on Cisco Content Switching Modules (CSM) by calculating a composite DFP weight derived from active binding counts, CPU utilization, and memory consumption. It triggers SNMP notifications when the calculated weight falls below a configurable threshold, indicating that server response times are degrading due to resource saturation.
This MIB reports the congestion status of the real server. A server can be in congested state due to high memory consumption, high CPU utilization or high number of clients being served by it. Congestion can cause delay in server response time. DFP (Dynamic Feedback Protocol) weight values are used as a metric to monitor the congestion of the server.
This MIB generates notifications when congestion state is detected on the real server. DFP weight is calculated as follows
BindingWeight=(Maxbindings-numberOfBindings)/Maxbindings
CPUMemWeight=(cpu + mem)/32
Weight = BindingWeight*CPUMemWeight*dfp_max_weight
Here,
- Maxbindings is the maximum number of bindings allowed on the
server.
- dfp_max_weight is the maximum possible value of DFP weight
(24).
- numberOfBindings is the number of mobile bindings currently
present with the server.
The DFP weight at which congestion is detected is configurable. If the DFP weight of the system falls below this value, then the system is treated as congested and notification is generated.
Main OID:
ciscoSlbDfpMIB.1.3.6.1.4.1.9.9.689
16
Objects
Active
Status
6
Dependencies
Imported Objects
Objects
16 total| Object Name |
|---|
ciscoSlbDfpMIBThis MIB reports the congestion status of the real server.
A server can be in congested state due to high memory
consumption, high CPU utilization or high number of clients
being served by it. Congestion can cause delay in server
response time.
DFP (Dynamic Feedback Protocol) weight values are used as a
metric to monitor the congestion of the server.
This MIB generates notifications when congestion state
is detected on the real server.
DFP weight is calculated as follows
BindingWeight=(Maxbindings-numberOfBindings)/Maxbindings
CPUMemWeight=(cpu + mem)/32
Weight = BindingWeight*CPUMemWeight*dfp_max_weight
Here,
- Maxbindings is the maximum number of bindings allowed on the
server.
- dfp_max_weight is the maximum possible value of DFP weight
(24).
- numberOfBindings is the number of mobile bindings currently
present with the server.
The DFP weight at which congestion is detected is configurable.
If the DFP weight of the system falls below this value, then
the system is treated as congested and notification is
generated. MODULE-IDENTITY .1.3.6.1.4.1.9.9.689 |
ciscoSlbDfpMIBNotifs OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.689.0 |
cslbcSlbDfpCongestionOnsetThe server generates this notification when value of
cslbcInstanceDfpValue object drops below the threshold
indicated
by the cslbcDfpCongestionOnsetThreshold object. NOTIFICATION-TYPE .1.3.6.1.4.1.9.9.689.0.1 |
cslbcSlbDfpCongestionAbateThe server generates this notification when value of
cslbcInstanceDfpValue object rises above the threshold
indicated
by the cslbcDfpCongestionAbateThreshold object. NOTIFICATION-TYPE .1.3.6.1.4.1.9.9.689.0.2 |
ciscoSlbDfpMIBObjects OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.689.1 |
cslbcDfpCongestionOnsetThresholdThis object specifes when congestion occurs. When the DFP
level of the system drops below this value, the system is
marked as congested. This value is same for all the
processors.rw CslbcDfpValue UNITS "DFP weight" .1.3.6.1.4.1.9.9.689.1.1 |
cslbcDfpCongestionAbateThresholdThis object specifies when decongestion occurs. When the DFP
level of the system rises above this value, the system is
marked as decongested. This value is same for all processors.rw CslbcDfpValue UNITS "DFP weight" .1.3.6.1.4.1.9.9.689.1.2 |
cslbcDfpCongestionThresholdTypeThis object specifies the action taken when the congestion
threshold is reached.
The valid congestion action type are
o reject - Incoming registration requests will be rejected when
this congestion type is configured.
o abort - Registration request being processed will be aborted
when this congestion type is configured.
o redirect - Incoming registration requests will be redirected
to another Home Agent when this congestion type is configured.
o drop - Existing idle mobile IP bindings will be dropped when
this congestion type is configured.
A mobile IP binding is a record present with the server that
associates the home address given to the mobile node by its
home network with the care of address granted to it by the
foreign network while it is roaming.
The Home Agent is a real server that maintains mobile
bindings.ro Enumeration .1.3.6.1.4.1.9.9.689.1.3 |
cslbcProcessorDfpValTableThis table lists the DFP status for each processor for which
DFP weights are monitored. SEQUENCE OF CslbcProcessorDfpValEntry .1.3.6.1.4.1.9.9.689.1.4 |
cslbcProcessorDfpValEntryThe entry contains DFP value for one processor.
A row is added to this table when congestion needs to be
monitored on a processor. Row is deleted when congestion no
longer needs to be monitored. CslbcProcessorDfpValEntry .1.3.6.1.4.1.9.9.689.1.4.1 |
cslbcProcessorDfpValPhysicalIndexThis element contains the index of the physical entity or
identifier of the processor for which the DFP value is
maintained. EntPhysicalIndexOrZero (CISCO-TC) .1.3.6.1.4.1.9.9.689.1.4.1.1 |
cslbcProcessorDfpValDescriptionThis element contains the description for the congestion
configured on for processor.ro SnmpAdminString (SNMP-FRAMEWORK-MIB) .1.3.6.1.4.1.9.9.689.1.4.1.2 |
cslbcProcessorDfpValDfpValueThis object indicates DFP value for the processor.ro CslbcDfpValue .1.3.6.1.4.1.9.9.689.1.4.1.3 |
ciscoSlbDfpMIBConform OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.689.2 |
ciscoSlbDfpMIBCompliances OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.689.2.1 |
ciscoSlbDfpMIBGroups OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.689.2.2 |