CISCO-SLB-HEALTH-MON-MIB: View SNMP OID List / Download MIB

The probing function monitors the health of real servers. The SLB device actively probes real servers to determine if they are healthy. This table is for configuring the parameters of probes.

This entry provides the basic configuration of a probe of a particular name, served by a particular SLB entity. This entry may be of any probe type.

The name of the probe.

The type of probe.

Time between health checks. It is from the end of previous check to the beginning of the next check.

The number of consecutive retries without a successful probe before marking the real server as 'failed'.

Time before retrying a 'failed' real server to see if it has recovered yet.

Maximum time to wait for a reply from a real server before considering this probe attempt to have failed.

Maximum time to wait for a TCP SYN/ACK frame from the real server. This entry is only valid for probes employing TCP, such as SMTP and HTTP probes.

The type of address stored in cslbxProbeAlternateDestAddr.

The alternative destination IP address to be used with the probing packet. Probe frames are normally sent to a real server IP address. If the setting is not '0.0.0.0', probe frames are sent to the IP address given by this object. This entry is only valid with the following probes(cslbxProbeType value): icmpProbe, tcpProbe, dnsProbe, httpProbe, ftpProbe, telnetProbe, smtpProbe udpProbe, httpsProbe, ldapProbe, popProbe, imapProbe, radiusProbe, tacacsProbe, sipProbe, tftpProbe, fingerProbe, echoProbe.

The domain name string use with the DNS probe. (Only applicable to DNS probes.)

The request method type string to be used in the HTTP probe packets. (Only applicable to HTTP probes.)

The URI string in the HTTP request of HTTP probe packets. (Only applicable to HTTP probes.)

The row status is used by a management station to create or delete the row entry in cslbxProbeCfgTable following the RowStatus textual convention.

The name of the function to be executed. (Only applicable to scriptedProbe type.)

The argument parameters passed into the executable script. (Only applicable to scriptedProbe type.)

The port number to be used by the probe. The value of zero indicates the probe will use the default port number. The default port number can be 0 or the default port of that particular probe. This object is not applicable when cslbxProbeType is 'icmpProbe'.

This object is used for configuring the description of the probe.

This object specifies whether the probe destined to IP address specified in cslbxProbeAlternateDestAddr be routed using internal routing table or forced to use the known mac-address of the real-server/gateway that probe is associated with. The value 'routingTable' specifies that address be routed using internal routing table. The value 'transparent' specifies that the probe destined to cslbxProbeAlternateDestAddr is routed using the ip address of the real server or gateway this probe is associated with. This object is applicable only if cslbxProbeAlternateDestAddr is configured. Enumeration: 'routingTable': 3, 'other': 1, 'transparent': 2.

This object is used for configuring the transport layer protocol to send probe messages. The possible value(s) are : other: values other than mentioned below. This value can not be written. tcp : TCP is used as transport layer protocol. udp : UDP is used as transport layer protocol. This object can be set for the entries with following values of cslbxProbeType: sipProbe, echoProbe For other probes, this object can not be written and the value of this object is based on the cslbxProbeType. Enumeration: 'udp': 3, 'other': 1, 'tcp': 2.

This object specifies the number of successful probe responses that should be received before declaring a failed real server as pass. This object is used in conjunction with 'cslbxProbeFailedInterval'.

This object represents the probe priority. The priority value is in the decreasing order of the actual priority, i.e., lower the value higher the priority. Probes associated with critical services can be configured with highest priority such that the results of these probes can be used to trigger a state change in configuration.

This object represents the user name required for authentication. This object is applicable for following value of 'cslbxProbeType' : httpprobe, httpsProbe telnetProbe, ftpProbe, ldapProbe, imapProbe, popProbe, radiusProbe, tacacsProbe.

This object represents the password required for authentication. This object is applicable for following value of 'cslbxProbeType' : httpprobe, httpsProbe telnetProbe, ftpProbe, ldapProbe, imapProbe, popProbe, radiusProbe, tacacsProbe. This object returns zero length octet string when read.

This object specifies how the connections need to be terminated. The possible value(s) are : graceful : follow graceful handshake for terminating connections. forced : send RST to terminate connections. This object is applicable only for TCP based probes. Enumeration: 'graceful': 1, 'forced': 2.

This object specifies whether to reuse the socket or not for the connection oriented probes. If set to 'true' same socket is re-used for multiple probes. If set to 'false' new socket will be created. This object is applicable only for TCP based probes.

This object represents the data to be sent for the appropriate probes. The possible value(s) are: ascii : ASCII data binary : binary data. This object is used in conjunction with object 'cslbxProbeSendData'. Enumeration: 'binary': 2, 'ascii': 1.

This object represents the data to be sent for the appropriate probes. This object is applicable for following value(s) of cslbxProbeType : echoProbe fingerProbe sipProbe tcpProbe udpProbe.

This object represents the state of the probe. When the probe is associated with a real server or server farm it will be active which is represented by value 'true'. When the probe is active and if the real server is administratively put into in-service, then the real server health monitoring will be started. When the probe is not associated with a real server or server farm it will be inactive which is represented by value 'false', so no health monitoring will be performed.

The probing function monitors the health of real servers. The SLB device actively probes real servers to determine if they are healthy. This table is for configuring the parameters of DNS probes. In a DNS probe, resolution of a specific domain name is requested, and the resulting IP address must match one of a list of 'expected IP addresses' configured for that probe. This table stores the list of expected IP addresses for each DNS probe.

The IP address in this entry is a valid response to a request for resolution of the domain name associated with the DNS probe in this entry.

The name of the DNS probe.

The type of address stored in cslbxDnsProbeIpAddress.

The IP address that may be expected in response to a DNS probe from a 'healthy' real DNS server.

The object used by a management station to create or delete the row entry in cslbxDnsProbeIpTable following the RowStatus textual convention.

The probing function monitors the health of real servers. The SLB device actively probes real servers to determine if they are healthy. This table is for configuring the parameters of HTTP probes. In particular, each HTTP probe request may be sent with a number of fixed HTTP headers. This table defines such fixed HTTP headers sent with HTTP probes.

This entry defines the HTTP header value of a particular HTTP header name sent with a particular HTTP probe, served by a particular SLB entity.

The name of the HTTP probe.

An HTTP header of this name is transmitted in the HTTP request sent by this probe.

The HTTP header value associated with the HTTP header name given by cslbxProbeHeaderFieldName.

The object used by a management station to create or delete the row entry in cslbxProbeHeaderTable following the RowStatus textual convention.

The probing function monitors the health of real servers. The SLB device actively probes real servers to determine if they are healthy. This table is for configuring the expect status codes returned by a server.

This entry provides the configuration of a range of expect status codes for a particular probe, served by a particular SLB entity.

The name of the probe.

The starting value of the expect status code range.

The ending value of the expect status code range.

The object used by a management station to create or delete the row entry in cslbxProbeExpectStatusCfgTable following the RowStatus textual convention.

This table is for configuring attributes applicable to HTTP and HTTPS probes. This table supports configuration of the probe attributes in addition to the HTTP attributes configured in cslbxProbeCfgTable. Following objects from cslbxProbeCfgTable are applicable to HTTP/HTTPS probe: cslbxProbeAlternateDestAddrType cslbxProbeAlternateDestAddr cslbxProbeRouteMethod cslbxProbeHttpRequestMethod cslbxProbeHttpRequestUrl cslbxProbePort cslbxProbeUserName cslbxProbePassword cslbxProbeInterval cslbxProbeRetries cslbxProbeFailedInterval cslbxProbeReceiveTimeout cslbxProbeTcpOpenTimeout cslbxProbeConnTermination cslbxProbePriority cslbxProbePassCount An HTTP probe establishes an HTTP connection to a real server and then sends an HTTP request and verifies the response. This table is applicable only for the instance value of cslbxProbeType 'httpProbe' or 'httpsProbe'.

An entry in HTTP Probe configuration table. An entry is created in the table when an entry is created in cslbxProbeCfgTable with cslbxProbeType 'httpProbe' or 'httpsProbe'. An entry is deleted from this table when corresponding entry (identified by the indices) is deleted from cslbxProbeCfgTable. Following objects are applicable to both HTTP and HTTPS Probes: cslbxProbeHTTPCfgVersion cslbxProbeHTTPCfgPersistence cslbxProbeHTTPCfgHashValid cslbxProbeHTTPCfgHashName Following objects are applicable only for HTTPS Probes: cslbxProbeHTTPCfgCipherSuite cslbxProbeHTTPCfgSslTlsVersion cslbxProbeHTTPCfgSslSessionReuse. The 'cslbxProbeName' refers to the probe which is created by adding an entry in 'cslbxProbeCfgTable' with cslbxProbeType 'httpProbe' or 'httpsProbe'.

This object represents HTTP version for the probe. The 'htpOneDotZero' specifies HTTP 1.0 protocol. The 'htpOneDotOne' specifies HTTP 1.1 protocol. Enumeration: 'httpOneDotZero': 1, 'httpOneDotOne': 2.

This object enables/disables persistence for HTTP(for both 1.0 and 1.1) probes. The pure HTTP/1.0 requires that a seperate TCP connection to be opened for each downloaded object. The persistence allows TCP connections to be re-used while requesting multiple objects without incurring a overhead of opening a new TCP connection.

This object enables the hash functionality. If set to 'true', the cslbxProbeHTTPCfgHashName is used. If set 'false' the value specified in cslbxProbeHTTPCfgHashName is not used.

This object specifies the hash value for the probe.

This object represents SSL Cipher suites to be used for HTTPS probes. The value 'rsa_any' is used for selecting a random cipher. The value 'rsaOther' specifies value other than those defined in the object. This value can not be written. Enumeration: 'rsaExportWithDes40CbcSha': 8, 'rsaExport1024WithRc456Sha': 11, 'rsaExport1024WithRc456Md5': 9, 'rsaWithRc4128Sha': 4, 'rsaExport1024WithDesCbcSha': 10, 'rsaWithRc4128Md5': 3, 'rsaExportWithRc440Md5': 7, 'rsaWithAes128CbcSha': 12, 'rsaOther': 1, 'rsaWith3desEdeCbcSha': 6, 'rsaAny': 2, 'rsaWithAes256cbcSha': 13, 'rsaWithdesCbcSha': 5.

This object represents the version of the SSL/TLS protocol. The possible value(s) are : other : Version not applicable. This value can not be set by the user. sslv2 : SSL Version 2.0. sslv3 : SSL Version 3.0. tlsv1 : TLS Version 1.0. all : All supported versions as reported in cslbxProbeHTTPSslTlsVersionSupported object. Enumeration: 'tlsv1': 4, 'all': 5, 'other': 1, 'sslv3': 3, 'sslv2': 2.

This object enables/disables reusing of the SSL Session ID. If set to 'true', SSL session ID will be reused. If set to 'false', SSL session ID will not be reused. In SSL, a new session ID is created every time the client and the SSL module go through a full key exchange and establish a new master secret key. Enabling this object allows the SSL module to reuse the master key on subsequent connections with the client, which can speed up the SSL negotiation process.

This object identifies the supported SSL/TLS versions. sslv3 - SSL version 3.0. tlsv1 - TLS version 1.0. Bits: 'tlsv1': 1, 'sslv3': 0.

This table is for configuring attributes applicable to SIP probes. The Session Initiation Protocol (SIP) is an ASCII-based, application-layer control protocol that can be used to establish, maintain, and terminate calls between two or more endpoints. SIP is an alternative protocol developed by the Internet Engineering Task Force (IETF) for multimedia conferencing over IP. This table supports configuration of the probe attributes in addition to the attributes configured in cslbxProbeCfgTable. Following objects from cslbxProbeCfgTable are applicable to SIP probe: cslbxProbeAlternateDestAddrType cslbxProbeAlternateDestAddr cslbxProbeRouteMethod cslbxProbePort cslbxProbeUserName cslbxProbePassword cslbxProbeInterval cslbxProbeRetries cslbxProbeFailedInterval cslbxProbeReceiveTimeout cslbxProbeTcpOpenTimeout cslbxProbeConnTermination cslbxProbeSocketReuse cslbxProbePassCount This table is applicable only if the value of cslbxProbeType is 'sipProbe'.

An entry in SIP Probe configuration table. An entry is created in the table when an entry is created in cslbxProbeCfgTable with cslbxProbeType 'sipProbe'. An entry is deleted from this table when corresponding entry (identified by the indices) is deleted from cslbxProbeCfgTable. The 'cslbxProbeName' refers to the probe which is created by adding an entry in 'cslbxProbeCfgTable' with cslbxProbeType 'sipProbe'.

This object represents the Registration address used in SIP protocol. Users in a SIP network are identified by unique SIP addresses. A SIP address is similar to an e-mail address and is in the format of 'sip:userID@gateway.com'. The userID can be either a user name or an E.164 address. An E.164 address is a telephone number with a string of decimal digits that uniquely indicates the public network termination point. The number contains the information necessary to route the call to this termination point.

This table is for configuring attributes applicable to FTP probes. This table supports configuration of the probe attributes in addition to the FTP attributes configured in cslbxProbeCfgTable. Following objects from cslbxProbeCfgTable are applicable to FTP probe: cslbxProbeAlternateDestAddrType cslbxProbeAlternateDestAddr cslbxProbeRouteMethod cslbxProbePort cslbxProbeUserName cslbxProbePassword cslbxProbeInterval cslbxProbeRetries cslbxProbeFailedInterval cslbxProbeReceiveTimeout cslbxProbeTcpOpenTimeout cslbxProbeConnTermination cslbxProbeSocketReuse cslbxProbePassCount This table is applicable only if the value of cslbxProbeType is 'ftpProbe'.

An entry in FTP Probe configuration table. Each entry represents the FTP request, File name and File type. An entry is created in the table when an entry is created in cslbxProbeCfgTable with cslbxProbeType 'ftpProbe'. An entry is deleted from this table when corresponding entry (identified by the indices) is deleted from cslbxProbeCfgTable. The 'cslbxProbeName' refers to the probe which is created by adding an entry in 'cslbxProbeCfgTable' with cslbxProbeType 'ftpProbe'.

This object identifies the FTP request to be used in FTP probe packets. The possible value(s) are: other : other than the values mentioned below. This value can not be written. ls : list files. get : Get request. put : Put request. Enumeration: 'put': 4, 'other': 1, 'ls': 2, 'get': 3.

The string representing the File Name used in FTP Probe.

This object specifies the type of the data transferred from/to in case of FTP requests. Enumeration: 'binary': 2, 'ascii': 1.

This table is for configuring attributes applicable to TFTP probes. This table supports configuration of the probe attributes in addition to the TFTP attributes configured in cslbxProbeCfgTable. Following objects from cslbxProbeCfgTable are applicable to TFTP probe: cslbxProbeAlternateDestAddrType cslbxProbeAlternateDestAddr cslbxProbePort cslbxProbeInterval cslbxProbeRetries cslbxProbeFailedInterval cslbxProbePassCount This table is applicable only if the value of cslbxProbeType is 'tftpProbe'.

An entry in TFTP Probe configuration table. Each entry represents the TFTP probe related parameters. An entry is created in the table when an entry is created in cslbxProbeCfgTable with cslbxProbeType 'tftpProbe'. An entry is deleted from this table when correspnding entry (identified by the indices) is deleted from cslbxProbeCfgTable. The 'cslbxProbeName' refers to the probe which is created by adding an entry in 'cslbxProbeCfgTable' with cslbxProbeType 'tftpProbe'.

This object identifies the TFTP request to be used in TFTP probe packets. The possible value(s) are: get : Get request. put : Put request. Enumeration: 'put': 2, 'get': 1.

The string representing the File Name used in TFTP Probe.

This object specifies the type of the data transferred from/to in case of FTP requests. Enumeration: 'binary': 2, 'ascii': 1.

This table is for configuring attributes applicable to IMAP probe. This table supports configuration of the probe attributes in addition to the IMAP attributes configured in cslbxProbeCfgTable. Following objects from cslbxProbeCfgTable are applicable to IMAP probe: cslbxProbeAlternateDestAddrType cslbxProbeAlternateDestAddr cslbxProbeRouteMethod cslbxProbePort cslbxProbeUserName cslbxProbePassword cslbxProbeInterval cslbxProbeRetries cslbxProbeFailedInterval cslbxProbeReceiveTimeout cslbxProbeConnTermination cslbxProbePriority cslbxProbePassCount An IMAP probe initiates a IMAP session and then attempts to retrieve e-mail from the server and verifies the response. This table is applicable only if the value of cslbxProbeType is 'imapProbe'.

An entry in IMAP Probe configuration table. Each entry represents the IMAP probe related parameters. An entry is created in the table when an entry is created in cslbxProbeCfgTable with cslbxProbeType 'imapProbe'. An entry is deleted from this table when corresponding entry (identified by the indices) is deleted from cslbxProbeCfgTable. The 'cslbxProbeName' refers to the probe which is created by adding an entry in 'cslbxProbeCfgTable' with cslbxProbeType 'imapProbe'.

This object is used for configuring the IMAP Mailbox value.

This object is used for configuring the IMAP method. The value can be any IMAP method. Some of the example(s) are: FETCH, NOOP, STAT, RETR

An extension to the CISCO-SLB-EXT-MIB for SLB health monitoring probes. SLB: Server Load Balancing. Server load balancing provides for the balancing of packets and connections arriving at the SLB device across a number of other devices, such as real servers, firewalls, or caches. A system containing an SLB device typically exhibits higher performance, scalability, and reliability than any of the devices being load balanced. An SLB device determines how to handle incoming frames and connections according to the contents of incoming data and various configuration options. In determining how to handle incoming data, an SLB device may examine the data at any OSI layer, including Layer 7. This MIB includes information on the health monitoring probes that can be used for monitoring the health of real servers. Health checking provides the ability of the content switch to detect if a server is available for load balancing. Health probes used for health checking allow testing various application level functionality. The active probes are sent at regular intervals and the lack of a response can lead to a specific server or and entire group of servers being declared as not available. Following probes are based on TCP: http, https, smtp, telnet, ftp, tcp, script, ldap, tacacs, sip, echo, finger. Following probes are based on UDP: tftp, udp, sip, echo,. Acronyms and terms: SLB Server Load Balancing VIP Virtual Server IP address NAT Network Address Translation SF Serverfarm FT Fault Tolerance SSL Secure Sockets Layer TLS Transport Layer Security Server Farm : Contains cluster of Real Server Real Server : Real Servers are physical devices assigned to a server farm. Real servers provide services that are load balanced. Health Probe : The mechanisms to monitor the health of real servers or rservers. Virtual IP : The IP through which the real server is reached during load balancing. Probe Instance : An instance of the probe identified by cslbxProbeName. A probe instance is created for every probe association. For example: When a probe is associated with a real server a probe instance is created for that probe. Probe Port : This mechanism introduces the capability Inheritance for the probe instance to inherit the virtual ip address port or the the real server port (identified by cshMonServerfarmRealServerPort) when the probe port (identified by cslbxProbePort) is not configured. The precedence of inheritance is as follows 1. Probe's configured port 2. Real server port 3. Virtual ip address port 4. Probes default port identified by cslbxProbePort. Examples: Scenario 1: Probe's configured port = 100 Real server port = 200 Virtual ip address port = 300 Probe's default port = 80 Inherited port of the probe instance = 100 Scenario 2: Probe's configured port = not configured Real server port = 200 Virtual ip address port = 300 Probe's default port = 80 Inherited port of the probe instance = 200 Scenario 3: Probe's configured port = not configured Real server port = not configured Virtual ip address port = 300 Probe's default port = 80 Inherited port of the probe instance = 300 Scenario 4: Probe's configured port = not configured Real server port = not configured Virtual ip address port = not configured Probe's default port = 80 Inherited port of the probe instance = 80 Scenario 5: There can be scenarios wherein there may be multiple inherited ports for a probe instance. There are configurations where multiple virtual ip addresses with different ports share the same probe instance and the probe has no configured port or real server port attached. In that case the shared probe instance has multiple inherited ports. A typical scenario might be Probe's configured port = not configured Real server port = not configured Ports of the virtual ip addresses which shares the probe instance = 300,400 Probe's default port = 80 Inherited port of the probe instance = 300,400

The notification is generated when probes socket usage exceeds or equals 90% atleast 100 times in one minute. The object cshMonSocketOverusageCount represents the number of times the probes socket usage exceeded 90 percentage in that minute.

The notification is generated when the probes socket usage becomes normal i.e the socket usage does not exceed 90% 100 or more times in that minute and after cshMonSocketOveruse notification is generated. The object cshMonSocketOverusageCount represents the number of times the probes socket usage exceeded 90 percentage in that minute.

This table provides the statistics of a probe applied to a real server. This will address probes configured under a serverfarm and also under a real server. Deprecated because of the change in index requirement.

Each entry provides the probe related stats for a real server. In the following cases one or more entries get created: 1. An entry gets created when an entry is created in the cesRealServerProbeTable. 2. When an entry is created in cslbxServerFarmProbeTable (identified by INDEX cslbxServerFarmProbeFarmName), then entries are created in this table with as many entries in cesServerFarmRserverTable (identified by INDEX slbServerFarmName) for the same server farm. 3. When an entry is created in cesServerFarmRserverTable (identified by INDEX slbServerFarmName), then entries are created in this table with as many entries in cslbxServerFarmProbeTable (identified by INDEX cslbxServerFarmProbeFarmName) for the same server farm. In the following cases one or more entries get deleted: 1. An entry gets deleted when an entry is deleted from the cesRealServerProbeTable. 2. When an entry is deleted from cslbxServerFarmProbeTable (identified by INDEX cslbxServerFarmProbeFarmName), then entries are deleted from this table with as many entries in cesServerFarmRserverTable (identified by INDEX slbServerFarmName) for the same server farm. 3. When an entry is deleted from cesServerFarmRserverTable (identified by INDEX slbServerFarmName), then entries are deleted from this table with as many entries in cslbxServerFarmProbeTable (identified by INDEX cslbxServerFarmProbeFarmName) for the same server farm.

This object identifies the name (unique identifier) of the real server. This value must correspond to an entry in cesServerFarmRserverTable (identified by INDEX cesRserverName) or cesRealServerProbeTable (identified by INDEX cesRserverName).

The port number of the real server. The value zero specifies that port number is not used in conjunction with real server IP Address. This value must correspond to an entry in cesServerFarmRserverTable (identified by INDEX cesServerFarmRserverPort) or cesRealServerProbeTable (identified by INDEX cesServerFarmRserverPort).

The number of probes passed for this real server. The probe is identified as pass if the real server returns a valid response.

The number of probes failed for this real server. The probe is identified as failed if the real server fails to provide a valid response for a specified number of retries.

The health monitor state of the probe for this real server.

This table provides the accumulated statistics for each probe type.

An entry in the cshMonProbeTypeStatsTable. 1. The entries in the table are created when the system boots up. 2. There is no use case where the entries gets deleted. The 'slbEntity'is used in identifying the module in which configuration is applied. The 'cslbxProbeType' identifies the type of the probe.

This object identifies the number of probes sent to the real servers.

This object identifies the number of passed probes. The probe is identified as pass if the real server returns a valid response.

This object identifies the number of probes that received connection errors while trying to connect to the real server.

This object identifies the number of probes that received TCP RST.

This object identifies the number of probes that suffered receive timeouts.

This object identifies the number of probes failed due to internal errors. Internal errors are unexpected errors during configuration, scheduling or processing a probe.

This object identifies the number of failed probes. The probe is identified as failed if the real server fails to provide a valid response for a specified number of retries.

This object identifies the number of probes whose connections were refused by the real servers.

This object identifies the number of probes that received timeout while trying to open a connection to the real server.

This object identifies the number of probes that are currently using a socket in the system.

This table provides the statistics of a probe applied to a real server. This will address probes configured under a serverfarm and also under a real server.

Each entry provides the probe related stats for a real server. Please refer to 'probe port inheritance' explained in this MODULE-IDENTITY description. In the following cases one or more entries get created: 1. When an entry is created in cesRealServerProbeTable, then an equal number of entries are created in this table for each inherited port associated with each probe instance. 2. When an entry is created in cslbxServerFarmProbeTable (identified by INDEX cslbxServerFarmProbeFarmName), then entries are created in this table with as many entries in cesServerFarmRserverTable (identified by INDEX slbServerFarmName) for the same server farm multiplied by the number of inherited ports associated with each probe instance. 3. When an entry is created in cesServerFarmRserverTable (identified by INDEX slbServerFarmName), then entries are created in this table with as many entries in cslbxServerFarmProbeTable (identified by INDEX cslbxServerFarmProbeFarmName) for the same server farm multiplied by the number of inherited ports associated with each probe instance. In the following cases one or more entries get deleted: 1. When an entry gets deleted from the cesRealServerProbeTable, then an equal number of entries are deleted in this table for each inherited port associated with each probe instance. 2. When an entry is deleted from cslbxServerFarmProbeTable (identified by INDEX cslbxServerFarmProbeFarmName), then entries are deleted from this table with as many entries in cesServerFarmRserverTable (identified by INDEX slbServerFarmName) for the same server farm multiplied by the number of inherited ports associated with each probe instance. 3. When an entry is deleted from cesServerFarmRserverTable (identified by INDEX slbServerFarmName), then entries are deleted from this table with as many entries in cslbxServerFarmProbeTable (identified by INDEX cslbxServerFarmProbeFarmName) for the same server farm multiplied by the number of inherited ports associated with each probe instance.

This object identifies the name (unique identifier) of the real server. This value must correspond to an entry in cesServerFarmRserverTable (identified by INDEX cesRserverName) or cesRealServerProbeTable (identified by INDEX cesRserverName).

This object identifies the port number of the real server. The value zero specifies that port number is not used in conjunction with real server ip address. This value must correspond to an entry in cesServerFarmRserverTable (identified by INDEX cesServerFarmRserverPort) or cesRealServerProbeTable (identified by INDEX cesServerFarmRserverPort).

This object identifies the port number which is inherited by the probe instance. Please refer to probe port inheritance concept explained in this MODULE-IDENTITY description.

This object identifies the number of probes passed for this real server. The probe is identified as pass if the real server returns a valid response.

This object identifies the number of probes failed for this real server. The probe is identified as failed if the real server fails to provide a valid response for a specified number of retries.

This object identifies the health monitor state of the probe for this real server.

This object indicates the date and time of the last probe.

This object indicates the last date and time that the probe's state transitioned to 'active'.

This object indicates the last date and time that the probes's state transitioned to 'failed'.

This object indentifies the type of the inherited port for this probe instance.

This object identifies the number of times the probes socket usage exceeded 90% in that minute.

The compliance statement for entities which implement the Cisco SLB Health monitoring MIB.

The compliance statement for entities which implement the Cisco SLB Health monitoring MIB.

The compliance statement for entities which implement the Cisco SLB Health monitoring MIB.

The compliance statement for entities which implement the Cisco SLB Health monitoring MIB.

The second revision of the collection of SLB server health probe objects.

The collection of objects to configure probes in an SLB device.

A collection of objects providing information specific to SIP Probes.

A collection of objects providing information specific to FTP Probes.

A collection of objects providing information specific to both HTTP and HTTPS Probes.

A collection of objects providing information specific to HTTPS Probes.

A collection of objects providing information specific to TFTP Probes.

A collection of objects providing information specific to IMAP Probes.

The collection of objects to configure scripted probes in an SLB device.

A collection of objects providing information specific to HTTPS Probes.

The third revision of the collection of SLB server health probe objects.

Group of objects providing statistics of a probe applied to a real server.

Group of objects providing statistics of a probe applied to a real server.

Group of objects providing statistics per probe type.

Group of notification objects.

A collection of objects providing healthmon notifications.