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.
CslbcDfpValueThis textual convention defines valid ranges DFP values similar to slbDfpRealWeight object defined in CISCO-SLB-MIB. (0..65535) · Unsigned32 · hint d · DFP weight
This 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.
cslbcDfpCongestionAbateThreshold
1.3.6.1.4.1.9.9.689.1.2
CslbcDfpValueThis textual convention defines valid ranges DFP values similar to slbDfpRealWeight object defined in CISCO-SLB-MIB. (0..65535) · Unsigned32 · hint d · DFP weight
This 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.
This 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.
Table details
cslbcProcessorDfpValTable
1.3.6.1.4.1.9.9.689.1.4
Index: cslbcProcessorDfpValPhysicalIndex
This table lists the DFP status for each processor for which DFP weights are monitored.
cslbcProcessorDfpValPhysicalIndex
1.3.6.1.4.1.9.9.689.1.4.1.1
EntPhysicalIndexOrZeroThis textual convention is an extension of entPhysicalIndex. If non-zero, the object is an entPhysicalIndex. If zero, no appropriate entPhysicalIndex exists. Any additional semantics are object specific. (0..2147483647) · Integer32
This element contains the index of the physical entity or identifier of the processor for which the DFP value is maintained.
cslbcProcessorDfpValDescription
1.3.6.1.4.1.9.9.689.1.4.1.2
SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form.
To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279].
Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited.
The use of control codes should be avoided.
When it is necessary to represent a newline, the control code sequence CR LF should be used.
The use of leading or trailing white space should be avoided.
For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided.
For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding.
UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding.
Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416].
Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (0..255) · OCTET STRING · hint 255t
This element contains the description for the congestion configured on for processor.
cslbcProcessorDfpValDfpValue
1.3.6.1.4.1.9.9.689.1.4.1.3
CslbcDfpValueThis textual convention defines valid ranges DFP values similar to slbDfpRealWeight object defined in CISCO-SLB-MIB. (0..65535) · Unsigned32 · hint d
This object indicates DFP value for the processor.
Trap details
cslbcSlbDfpCongestionOnset
1.3.6.1.4.1.9.9.689.0.1
The server generates this notification when value of cslbcInstanceDfpValue object drops below the threshold indicated by the cslbcDfpCongestionOnsetThreshold object.
cslbcProcessorDfpValDescription
1.3.6.1.4.1.9.9.689.1.4.1.2
SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form.
To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279].
Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited.
The use of control codes should be avoided.
When it is necessary to represent a newline, the control code sequence CR LF should be used.
The use of leading or trailing white space should be avoided.
For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided.
For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding.
UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding.
Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416].
Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (0..255) · OCTET STRING · hint 255t
This element contains the description for the congestion configured on for processor.
cslbcProcessorDfpValDfpValue
1.3.6.1.4.1.9.9.689.1.4.1.3
CslbcDfpValueThis textual convention defines valid ranges DFP values similar to slbDfpRealWeight object defined in CISCO-SLB-MIB. (0..65535) · Unsigned32 · hint d
This object indicates DFP value for the processor.
This 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.
cslbcDfpCongestionOnsetThreshold
1.3.6.1.4.1.9.9.689.1.1
CslbcDfpValueThis textual convention defines valid ranges DFP values similar to slbDfpRealWeight object defined in CISCO-SLB-MIB. (0..65535) · Unsigned32 · hint d · DFP weight
This 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.
cslbcSlbDfpCongestionAbate
1.3.6.1.4.1.9.9.689.0.2
The server generates this notification when value of cslbcInstanceDfpValue object rises above the threshold indicated by the cslbcDfpCongestionAbateThreshold object.
cslbcProcessorDfpValDescription
1.3.6.1.4.1.9.9.689.1.4.1.2
SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form.
To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279].
Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited.
The use of control codes should be avoided.
When it is necessary to represent a newline, the control code sequence CR LF should be used.
The use of leading or trailing white space should be avoided.
For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided.
For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding.
UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding.
Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416].
Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (0..255) · OCTET STRING · hint 255t
This element contains the description for the congestion configured on for processor.
cslbcProcessorDfpValDfpValue
1.3.6.1.4.1.9.9.689.1.4.1.3
CslbcDfpValueThis textual convention defines valid ranges DFP values similar to slbDfpRealWeight object defined in CISCO-SLB-MIB. (0..65535) · Unsigned32 · hint d
This object indicates DFP value for the processor.
cslbcDfpCongestionAbateThreshold
1.3.6.1.4.1.9.9.689.1.2
CslbcDfpValueThis textual convention defines valid ranges DFP values similar to slbDfpRealWeight object defined in CISCO-SLB-MIB. (0..65535) · Unsigned32 · hint d · DFP weight
This 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.
This 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.