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
Parsed from file CISCO-SLB-HEALTH-MON-MIB.mib
Module: CISCO-SLB-HEALTH-MON-MIB
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
Parsed from file CISCO-SLB-HEALTH-MON-MIB.my.txt
Company: None
Module: CISCO-SLB-HEALTH-MON-MIB
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
ciscoSlbHealthMonMIB MODULE-IDENTITY LAST-UPDATED "200806260000Z" ORGANIZATION "Cisco Systems, Inc." CONTACT-INFO "Cisco Systems Customer Service Postal: 170 W. Tasman Drive San Jose, CA 95134 USA Tel: +1 800 553-NETS E-mail: [email protected]" DESCRIPTION "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" REVISION "200806260000Z" DESCRIPTION "-Added CiscoProbeInheritedPortType TEXTUAL-CONVENTION. -Deprecated cshMonSfarmRealProbeStatsTable. -Added cshMonServerfarmRealProbeStatsTable. -Added cshMonProbeTypeStatsTable. -Added the following notifications ciscoSlbHealthMonSocketOveruse ciscoSlbHealthMonSocketNormaluse -Added cshMonSocketOverusageCount notification object. -Deprecated cshMonSfarmrealserverProbeStatsGroup OBJECT-GROUP. -Deprecated ciscoSlbHealthMonMIBComplianceRev2 MODULE-COMPLIANCE. -Added the following OBJECT-GROUP's cshMonSfarmrealserverProbeStatsGroupRev1 cshMonProbeTypeStatsGroup cshMonNotifObjectsGroup -Added cshMonNotifGroup NOTIFICATION-GROUP. -Added ciscoSlbHealthMonMIBComplianceRev3 MODULE-COMPLIANCE." REVISION "200803110000Z" DESCRIPTION "- Added CiscoProbeHealthMonState TEXTUAL-CONVENTION. - Added cslbxProbeState to the cslbxProbeCfgTable. - Added cshMonSfarmRealProbeStatsTable. - Deprecated cslbHealthMonServerProbesGroup object group. - Deprecated ciscoSlbHealthMonMIBComplianceRev1 compliance statement. - Added cslbHealthMonServerProbesGroupRev1 OBJECT-GROUP. - Added ciscoSlbHealthMonMIBComplianceRev2 MODULE-COMPLIANCE." REVISION "200611140000Z" DESCRIPTION "- Added following object in cslbxProbeHTTPCfgTable cslbxProbeHTTPSslTlsVersionSupported. - Added 'all' enum in cslbxProbeHTTPCfgSslTlsVersion object. - Added 'rtspProbe' and 'snmpProbe' in SlbProbeType TEXTUAL CONVENTION - Added following group cslbHealthMonHTTPSProbesGroupRev1. - Added following in Compliance/Conformance ciscoSlbHealthMonMIBComplianceRev1." REVISION "200601180000Z" DESCRIPTION "Initial version of this MIB module. SlbProbeType : New enums(value 10-20) added. - Following tables were originally defined in CISCO-SLB-EXT-MIB cslbxProbeCfgTable cslbxDnsProbeIpTable cslbxProbeHeaderCfgTable cslbxProbeExpectStatusCfgTable - Added following objects in cslbxProbeCfgTable cslbxProbeDescription cslbxProbeProtocolType cslbxProbeRouteMethod cslbxProbeUserName cslbxProbePassword cslbxProbePassCount cslbxProbePriority cslbxProbeConnTermination cslbxProbeSocketReuse cslbxProbeSendDataType cslbxProbeSendData - defined following tables cslbxProbeHTTPCfgTable cslbxProbeSIPCfgTable cslbxProbeFTPCfgTable cslbxProbeTFTPCfgTable cslbxProbeIMAPCfgTable - Added UNITS clause for the following objects cslbxProbeReceiveTimeout cslbxProbeTcpOpenTimeout." ::= { ciscoMgmt 508 }
ciscoSlbHealthMonMIB OBJECT IDENTIFIER ::= { ciscoMgmt 508 }
Vendor: Cisco
Module: CISCO-SLB-HEALTH-MON-MIB
[Automatically extracted from oidview.com]
ciscoSlbHealthMonMIB MODULE-IDENTITY LAST-UPDATED "200806260000Z" ORGANIZATION "Cisco Systems, Inc." CONTACT-INFO "Cisco Systems Customer Service Postal: 170 W. Tasman Drive San Jose, CA 95134 USA Tel: +1 800 553-NETS E-mail: [email protected]" DESCRIPTION "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" REVISION "200806260000Z" DESCRIPTION "-Added CiscoProbeInheritedPortType TEXTUAL-CONVENTION. -Deprecated cshMonSfarmRealProbeStatsTable. -Added cshMonServerfarmRealProbeStatsTable. -Added cshMonProbeTypeStatsTable. -Added the following notifications ciscoSlbHealthMonSocketOveruse ciscoSlbHealthMonSocketNormaluse -Added cshMonSocketOverusageCount notification object. -Deprecated cshMonSfarmrealserverProbeStatsGroup OBJECT-GROUP. -Deprecated ciscoSlbHealthMonMIBComplianceRev2 MODULE-COMPLIANCE. -Added the following OBJECT-GROUP's cshMonSfarmrealserverProbeStatsGroupRev1 cshMonProbeTypeStatsGroup cshMonNotifObjectsGroup -Added cshMonNotifGroup NOTIFICATION-GROUP. -Added ciscoSlbHealthMonMIBComplianceRev3 MODULE-COMPLIANCE." REVISION "200803110000Z" DESCRIPTION "- Added CiscoProbeHealthMonState TEXTUAL-CONVENTION. - Added cslbxProbeState to the cslbxProbeCfgTable. - Added cshMonSfarmRealProbeStatsTable. - Deprecated cslbHealthMonServerProbesGroup object group. - Deprecated ciscoSlbHealthMonMIBComplianceRev1 compliance statement. - Added cslbHealthMonServerProbesGroupRev1 OBJECT-GROUP. - Added ciscoSlbHealthMonMIBComplianceRev2 MODULE-COMPLIANCE." REVISION "200611140000Z" DESCRIPTION "- Added following object in cslbxProbeHTTPCfgTable cslbxProbeHTTPSslTlsVersionSupported. - Added 'all' enum in cslbxProbeHTTPCfgSslTlsVersion object. - Added 'rtspProbe' and 'snmpProbe' in SlbProbeType TEXTUAL CONVENTION - Added following group cslbHealthMonHTTPSProbesGroupRev1. - Added following in Compliance/Conformance ciscoSlbHealthMonMIBComplianceRev1." REVISION "200601180000Z" DESCRIPTION "Initial version of this MIB module. SlbProbeType : New enums(value 10-20) added. - Following tables were originally defined in CISCO-SLB-EXT-MIB cslbxProbeCfgTable cslbxDnsProbeIpTable cslbxProbeHeaderCfgTable cslbxProbeExpectStatusCfgTable - Added following objects in cslbxProbeCfgTable cslbxProbeDescription cslbxProbeProtocolType cslbxProbeRouteMethod cslbxProbeUserName cslbxProbePassword cslbxProbePassCount cslbxProbePriority cslbxProbeConnTermination cslbxProbeSocketReuse cslbxProbeSendDataType cslbxProbeSendData - defined following tables cslbxProbeHTTPCfgTable cslbxProbeSIPCfgTable cslbxProbeFTPCfgTable cslbxProbeTFTPCfgTable cslbxProbeIMAPCfgTable - Added UNITS clause for the following objects cslbxProbeReceiveTimeout cslbxProbeTcpOpenTimeout." ::= { ciscoMgmt 508 }
ciscoSlbHealthMonMIB MODULE-IDENTITY LAST-UPDATED "200806260000Z" ORGANIZATION "Cisco Systems, Inc." CONTACT-INFO "Cisco Systems Customer Service Postal: 170 W. Tasman Drive San Jose, CA 95134 USA Tel: +1 800 553-NETS E-mail: [email protected]" DESCRIPTION "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" REVISION "200806260000Z" DESCRIPTION "-Added CiscoProbeInheritedPortType TEXTUAL-CONVENTION. -Deprecated cshMonSfarmRealProbeStatsTable. -Added cshMonServerfarmRealProbeStatsTable. -Added cshMonProbeTypeStatsTable. -Added the following notifications ciscoSlbHealthMonSocketOveruse ciscoSlbHealthMonSocketNormaluse -Added cshMonSocketOverusageCount notification object. -Deprecated cshMonSfarmrealserverProbeStatsGroup OBJECT-GROUP. -Deprecated ciscoSlbHealthMonMIBComplianceRev2 MODULE-COMPLIANCE. -Added the following OBJECT-GROUP's cshMonSfarmrealserverProbeStatsGroupRev1 cshMonProbeTypeStatsGroup cshMonNotifObjectsGroup -Added cshMonNotifGroup NOTIFICATION-GROUP. -Added ciscoSlbHealthMonMIBComplianceRev3 MODULE-COMPLIANCE." REVISION "200803110000Z" DESCRIPTION "- Added CiscoProbeHealthMonState TEXTUAL-CONVENTION. - Added cslbxProbeState to the cslbxProbeCfgTable. - Added cshMonSfarmRealProbeStatsTable. - Deprecated cslbHealthMonServerProbesGroup object group. - Deprecated ciscoSlbHealthMonMIBComplianceRev1 compliance statement. - Added cslbHealthMonServerProbesGroupRev1 OBJECT-GROUP. - Added ciscoSlbHealthMonMIBComplianceRev2 MODULE-COMPLIANCE." REVISION "200611140000Z" DESCRIPTION "- Added following object in cslbxProbeHTTPCfgTable cslbxProbeHTTPSslTlsVersionSupported. - Added 'all' enum in cslbxProbeHTTPCfgSslTlsVersion object. - Added 'rtspProbe' and 'snmpProbe' in SlbProbeType TEXTUAL CONVENTION - Added following group cslbHealthMonHTTPSProbesGroupRev1. - Added following in Compliance/Conformance ciscoSlbHealthMonMIBComplianceRev1." REVISION "200601180000Z" DESCRIPTION "Initial version of this MIB module. SlbProbeType : New enums(value 10-20) added. - Following tables were originally defined in CISCO-SLB-EXT-MIB cslbxProbeCfgTable cslbxDnsProbeIpTable cslbxProbeHeaderCfgTable cslbxProbeExpectStatusCfgTable - Added following objects in cslbxProbeCfgTable cslbxProbeDescription cslbxProbeProtocolType cslbxProbeRouteMethod cslbxProbeUserName cslbxProbePassword cslbxProbePassCount cslbxProbePriority cslbxProbeConnTermination cslbxProbeSocketReuse cslbxProbeSendDataType cslbxProbeSendData - defined following tables cslbxProbeHTTPCfgTable cslbxProbeSIPCfgTable cslbxProbeFTPCfgTable cslbxProbeTFTPCfgTable cslbxProbeIMAPCfgTable - Added UNITS clause for the following objects cslbxProbeReceiveTimeout cslbxProbeTcpOpenTimeout." ::= { ciscoMgmt 508 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.9.9.508.0 | ciscoSlbHealthMonMIBNotifs | 2 | 2 | None |
| 1.3.6.1.4.1.9.9.508.1 | ciscoSlbHealthMonMIBObjects | 2 | 35 | None |
| 1.3.6.1.4.1.9.9.508.2 | ciscoSlbHealthMonMIBConformance | 2 | 22 | None |
To many brothers! Only 100 nearest brothers are shown.
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| ... | ||||
| 1.3.6.1.4.1.9.9.458 | ciscoApplianceRedundancyMIB | 3 | 47 | This mib defines the SNMP objects to report the status of High Availability (HA) functionality in Cisco network management applia… |
| 1.3.6.1.4.1.9.9.459 | ciscoBitsClockMIB | 3 | 21 | This MIB provides information on Building Integrated Timing Supply(BITS) clocking sources and modes of operations. It is used to… |
| 1.3.6.1.4.1.9.9.460 | ciscoTpcMIB | 3 | 24 | The MIB module for Third Party Copy(TPC): Third Party Copy derives its name from the fact that there are three entities involved … |
| 1.3.6.1.4.1.9.9.461 | ciscoEtherCfmMIB | 3 | 39 | This MIB module defines the managed objects and notifications for Ethernet Connectivity Fault Management (CFM). CFM is an end-to-e… |
| 1.3.6.1.4.1.9.9.463 | ciscoSanTapMIB | 3 | 30 | MIB module to provide information about the SanTap service configuration. SanTap is a fibre channel switch based capability that p… |
| 1.3.6.1.4.1.9.9.466 | ciscoEthernetAccessMIB | 2 | 20 | The tables defined by this MIB module contain a collection of managed objects that are general in nature and apply to an edge dev… |
| 1.3.6.1.4.1.9.9.467 | ciscoCryptoAcceleratorMIB | 3 | 107 | The MIB module for monitoring the identity, status, activity and faults of crypto accelerator (CA) modules used in devices implem… |
| 1.3.6.1.4.1.9.9.468 | ciscoContextMappingMIB | 2 | 35 | A single SNMP agent sometimes needs to support multiple instances of the same MIB module, and does so through the use of multiple… |
| 1.3.6.1.4.1.9.9.470 | ciscoEnhancedSlbMIB | 3 | 106 | The MIB for managing Server Load Balancing Manager(s), and products supporting Server Load Balancing(SLB) features. This MIB exten… |
| 1.3.6.1.4.1.9.9.471 | ciscoFlexLinksMIB | 3 | 36 | This MIB module is for configuration and status query of Flex Links feature on the Cisco device. Flex Links are a pair of Layer 2… |
| 1.3.6.1.4.1.9.9.472 | ciscoModuleVirtualizationMIB | 3 | 35 | This MIB provides a way to create virtual contexts, and managing them. A virtual context is logical partition of a physical devi… |
| 1.3.6.1.4.1.9.9.473 | ciscoCcaMIB | 3 | 200 | The Cisco Contact Center Applications (CCCA) Management Information Base (MIB) module defines management instrumentation for appl… |
| 1.3.6.1.4.1.9.9.474 | ciscoFilterGroupMIB | 3 | 55 | The MIB module is for creating and configuring object groups to support packet filtering and access control on IP and other proto… |
| 1.3.6.1.4.1.9.9.479 | ciscoCableWidebandMIB | 3 | 77 | This is the MIB module for the support of Channel Bonding Protocol for the Cable Modem Termination System (CMTS). Wideband DOCSIS… |
| 1.3.6.1.4.1.9.9.480 | ciscoL4L7moduleResourceLimitMIB | 4 | 100 | The MIB module for managing resource classes and configuring limits(max/min) to different resources. The resource referenced in … |
| 1.3.6.1.4.1.9.9.482 | ciscoInterfaceTopNExtMIB | 3 | 16 | This MIB module is an extension to INTERFACETOPN-MIB. It provides additional management information for sorting device interfaces. |
| 1.3.6.1.4.1.9.9.483 | ciscoIpRanBackHaulMIB | 3 | 248 | This MIB provides information on the IP-RAN traffic from cell site to aggregation site in the following situations. In an GSM en… |
| 1.3.6.1.4.1.9.9.484 | ciscoNacNadMIB | 3 | 157 | This MIB module is for the configuration of a Network Access Device (NAD) on the Cisco Network Admission Control (NAC) system. End… |
| 1.3.6.1.4.1.9.9.485 | ciscoRttMonTCMIB | 0 | 0 | This MIB contains textual conventions used by CISCO-RTTMON-MIB, CISCO-RTTMON-RTP-MIB and CISCO-RTTMON-ICMP-MIB, but they are not … |
| 1.3.6.1.4.1.9.9.486 | ciscoRttMonIcmpMIB | 3 | 7 | An extension to the CISCO-RTTMON-MIB for ICMP operations. The ICMP Jitter operation provides capability to measure metrics such a… |
| 1.3.6.1.4.1.9.9.487 | ciscoRttMonRtpMIB | 3 | 8 | An extension to the CISCO-RTTMON-MIB for Cisco IP SLA RTP operation, Real-Time Transport Protocol(RFC 1889). This operation provi… |
| 1.3.6.1.4.1.9.9.488 | ciscoFirewallTc | 0 | 0 | This MIB module defines textual conventions that are commonly used in modeling management information pertaining to configuration… |
| 1.3.6.1.4.1.9.9.490 | ciscoNetintMIB | 3 | 11 | This MIB module is for Network Interrupt information on Cisco device. |
| 1.3.6.1.4.1.9.9.491 | ciscoUnifiedFirewallMIB | 3 | 235 | Overview of Cisco Firewall MIB ============================== This MIB Module models status and performance statistics pertaining … |
| 1.3.6.1.4.1.9.9.492 | ciscoCefMIB | 3 | 192 | Cisco Express Forwarding (CEF) describes a high speed switching mechanism that a router uses to forward packets from the inbound … |
| 1.3.6.1.4.1.9.9.493 | ciscoCefTextualConventions | 0 | 0 | ciscoCeftextualConventions |
| 1.3.6.1.4.1.9.9.494 | ciscoEntityRedunTcMIB | 0 | 0 | This module defines the textual conventions used within Cisco Entity Redundancy MIBs. |
| 1.3.6.1.4.1.9.9.495 | ciscoPsdClientMIB | 3 | 44 | This MIB module manages the client side functionality of the Persistent Storage Device(PSD). This MIB instrumentation is for conf… |
| 1.3.6.1.4.1.9.9.497 | cGgsnSAMIB | 3 | 247 | This MIB module manages the service-aware feature of Gateway GPRS Support Node (GGSN). This MIB is an enhancement of the CISCO-GG… |
| 1.3.6.1.4.1.9.9.498 | ciscoEntityRedunMIB | 3 | 93 | This management information module supports configuration, control and monitoring of redundancy protection for various kinds of c… |
| 1.3.6.1.4.1.9.9.500 | ciscoStackWiseMIB | 3 | 111 | This MIB module contain a collection of managed objects that apply to network devices supporting the Cisco StackWise(TM) technolo… |
| 1.3.6.1.4.1.9.9.504 | ciscoSwitchMulticastMIB | 3 | 108 | This MIB module defines management objects for the Multicast Switching features on Cisco Layer 2/3 devices. Definition of some of … |
| 1.3.6.1.4.1.9.9.505 | cpkiMIB | 3 | 44 | A networking device may provide several security services and protocols like SSL, SSH, IPSec/IKE etc. which need identities … |
| 1.3.6.1.4.1.9.9.507 | ciscoPolicyGroupMIB | 3 | 35 | The MIB module is for configuration of policy and policy group. A policy group can be described as a set of entities identified b… |
| 1.3.6.1.4.1.9.9.509 | ciscoWdsInfoMIB | 3 | 141 | This MIB is intended to be implemented on all Cisco network entities that provide Wireless Domain Services (WDS). The WDS provide… |
| 1.3.6.1.4.1.9.9.510 | ciscoErmMIB, ciscoVoiceLmrMIB | 3 | 176 | This MIB module provides management of voice tone signal as static injected tone for Land Mobile Radio The tone signal includes … |
| 1.3.6.1.4.1.9.9.511 | ciscoCbpTargetTCMIB | 0 | 0 | This MIB module defines Textual Conventions for representing targets which have class based policy mappings. A target can be any … |
| 1.3.6.1.4.1.9.9.512 | ciscoLwappWlanMIB | 3 | 249 | This MIB is intended to be implemented on all those devices operating as Central Controllers (CC) that terminate the Light Weigh… |
| 1.3.6.1.4.1.9.9.513 | ciscoLwappApMIB | 4 | 386 | This MIB is intended to be implemented on all those devices operating as Central Controllers (CC) that terminate the Light Weight… |
| 1.3.6.1.4.1.9.9.514 | ciscoLwappTextualConventions | 0 | 0 | This module defines textual conventions used throughout the Cisco enterprise MIBs designed for implementation on Central Controlle… |
| 1.3.6.1.4.1.9.9.515 | ciscoLwappWebAuthMIB | 4 | 43 | This MIB is intended to be implemented on all those devices operating as Central controllers, that terminate the Light Weight Acc… |
| 1.3.6.1.4.1.9.9.516 | ciscoLwappLinkTestMIB | 3 | 57 | This MIB is intended to be implemented on all those devices operating as Central controllers, that terminate the Light Weight Acc… |
| 1.3.6.1.4.1.9.9.517 | ciscoLwappReapMIB | 3 | 63 | This MIB is intended to be implemented on all those devices operating as Central Controllers (CC) that terminate the Light Weight… |
| 1.3.6.1.4.1.9.9.518 | ciscoLwappMfpMIB | 4 | 64 | This MIB is intended to be implemented on all those devices operating as Central Controllers (CC) that terminate the Light Weight… |
| 1.3.6.1.4.1.9.9.519 | ciscoLwappIdsMIB | 3 | 28 | This MIB is intended to be implemented on all those devices operating as Central Controllers (CC) that terminate the Light Weight… |
| 1.3.6.1.4.1.9.9.520 | ciscoLwappCcxRmMIB | 3 | 45 | This MIB is intended to be implemented on all those devices operating as Central controllers, that terminate the Light Weight Acc… |
| 1.3.6.1.4.1.9.9.521 | ciscoLwappWlanSecurityMIB | 3 | 51 | This MIB is intended to be implemented on all those devices operating as Central controllers, that terminate the Light Weight Acc… |
| 1.3.6.1.4.1.9.9.522 | ciscoLwappDot11ClientCalibMIB | 3 | 50 | This MIB is intended to be implemented on all those devices operating as Central controllers, that terminate the Light Weight Acc… |
| 1.3.6.1.4.1.9.9.523 | ciscoLwappClRoamMIB | 3 | 61 | This MIB is intended to be implemented on all those devices operating as Central controllers, that terminate the Light Weight Acc… |
| 1.3.6.1.4.1.9.9.524 | ciscoLwappQosMIB | 3 | 119 | This MIB is intended to be implemented on all those devices operating as Central controllers, that terminate the Light Weight Acc… |
| 1.3.6.1.4.1.9.9.525 | ciscoLwappTsmMIB | 3 | 57 | This MIB is intended to be implemented on all those devices operating as Central controllers, that terminate the Light Weight Acc… |
| 1.3.6.1.4.1.9.9.529 | ciscoItpMsuRatesMIB | 3 | 61 | This MIB provides information used to manage the number of MTP3 MSUs transmitted and received per processor. Many of the higher … |
| 1.3.6.1.4.1.9.9.530 | ciscoNacTcMIB | 0 | 0 | This module defines the textual conventions for Cisco Network Admission Control(NAC) system. The Cisco Network Admission Control … |
| 1.3.6.1.4.1.9.9.532 | ciscoNATExtMIB | 3 | 13 | This MIB is an extension to the NAT-MIB. This MIB module includes objects for providing the NAT related statistics. Acronyms: NAT… |
| 1.3.6.1.4.1.9.9.533 | ciscoCbpTargetMIB | 3 | 25 | This MIB module defines the managed objects for representing targets which have class-based policy mappings. A target can be any… |
| 1.3.6.1.4.1.9.9.543 | ciscoLicenseMgmtMIB | 3 | 131 | The MIB module for managing licenses on the system. The licensing mechanism provides flexibility to enforce licensing for various… |
| 1.3.6.1.4.1.9.9.548 | ciscoErrDisableMIB | 3 | 43 | This MIB module provides the ability for a Network Management Station (NMS) to configure and monitor the error-disable feature vi… |
| ... | ||||