2.2 MARCO TEÓRICO REFERENCIAL
2.2.2 La terminación de los contratos de trabajo en el Ecuador
Displays the layer 7 stick tables. For example, if a layer 7 VIP is created using RDP cookie persistence, a stick table will be used. The related VIP is then available in the drop-down as shown below:
NOTES:
Stick tables are used when either source IP persistence or RDP cookie persistence is used with layer 7 Virtual ServicesGraphing
From v7.5 graphs are automatically configured when new Virtual and Real Servers are defined. There is no need to initialize graphs as in previous versions.
Graphs – Load Balanced Services
Graphs for the configured Virtual & Real Servers can be accessed either from the System Overview using the appropriate graph icon that appears next to each VIP and RIP or from the drop-down available in the WUI under Reports > Graphing.
Using the System Overview
The graph is displayed by clicking the relevant blue icon that's displayed next to each VIP / RIP:
When this method is used, the daily connection graph (i.e. the last 24 hrs) is displayed for the particular VIP or RIP:
Clicking anyway within this graph opens the complete list of graphs for the VIP / RIP in question. This is the same as selecting the VIP / RIP in the Reports menu as explained below.
Using the Reports Menu
When selected, a drop-down similar to the following is displayed:
N.B. As VIPs & RIPs are added or removed, these are automatically added / removed from the drop-down list When selected in this way, a complete list of graphs is displayed for the VIP / RIP selected as shown below:
Graphs – Appliance Specific
Appliance specific graphs are available for the following statistics:
•
Network Throughout•
Load Average•
Memory Usage•
Disk UsageThe first three graphs listed above are displayed in the System Overview. All four graphs can be accessed using the WUI option: Reports > Graphing.
As shown above, daily graphs for Total NIC Throughput, System Load Average and Memory Usage are displayed by default in the System Overview. Clicking anyway within these graph opens the full list of related graphs. This is the same as selecting the graph in the Reports menu as explained below.
Using the Reports Menu
When selected, a drop-down including the following options is displayed:
Selecting one of these options results in a series of graphs for various periods including hourly, daily, weekly, monthly and yearly.
Graph Options
A number of graph options are available. To change the settings:
Statistics can be enabled (default) by selecting On
Statistics can be disabled by selecting Off
Statistics can be cleared by selecting DeleteAdvanced Configuration Settings
Set Data Collector Interval Time – Specified in seconds. Change the interval for which data is recorded by the collector. This is a global value and will effect all collectors. Should only be changed if you have been told to do so by support.
WARNING – Changing this value will reset the RRD database files and you will loose all your previous data!! Set Data Collector Timeout – Timeout for collector when querying the various services. Value in Seconds. Do not change unless advised to do so by support.
Set Collector Process Threads – Number of collector process threads to use for reading stats. Do not change unless advised to do so by support.
Enable Collector Logging – Enable logging for collectd. Warning this is incredibly verbose and should only be used for debugging.
SNMP Reporting
Native SNMP support can be enabled on the appliance. This is a simple case of enabling the SNMP service: service snmpd start
chkconfig snmpd on
('chkconfig snmpd on' forces snmpd to start on appliance reboot)
SNMP for Layer 4 Based Services
The root OID for Layer 4 based services is: 1.3.6.1.4.1.8225.4711 You can test if everything works by running the command shown below:
[root@lbmaster ~]# snmpwalk -c public -v 2c -m LVS-MIB localhost 1.3.6.1.4.1.8225.4711 LVS-MIB::lvsVersion.0 = STRING: "1.2.0" LVS-MIB::lvsNumServices.0 = INTEGER: 2 LVS-MIB::lvsHashTableSize.0 = INTEGER: 4096 LVS-MIB::lvsTcpTimeOut.0 = INTEGER: 900 LVS-MIB::lvsTcpFinTimeOut.0 = INTEGER: 120 LVS-MIB::lvsUdpTimeOut.0 = INTEGER: 300 LVS-MIB::lvsDaemonState.0 = INTEGER: none(0) …
etc.
N.B. LVS-MIB.txt and other MIB files are available on the appliance in /usr/share/snmp/mibs/ You can also use all the usual MIB II counters and gauges such as network and CPU etc.
Monitoring Layer 4 RIPs using SNMP
To list the Virtual Services use the command shown below:
[root@lbmaster ~]# snmpwalk -c public -v 2c -m LVS-MIB localhost 1.3.6.1.4.1.8225.4711.17.1.4 LVS-MIB::lvsServiceAddr.1 = IpAddress: 192.168.110.194
To list the Real Servers use the command shown below:
[root@lbmaster ~]# snmpwalk -c public -v 2c -m LVS-MIB localhost 1.3.6.1.4.1.8225.4711.18.1.3 LVS-MIB::lvsRealServerAddr.2.1 = IpAddress: 10.0.0.101
LVS-MIB::lvsRealServerAddr.2.2 = IpAddress: 10.0.0.100
This indicates that all servers are passing their health-check. If the check fails, that server will be omitted from the list as shown below:
[root@lbmaster ~]# snmpwalk -c public -v 2c -m LVS-MIB localhost 1.3.6.1.4.1.8225.4711.18.1.3 LVS-MIB::lvsRealServerAddr.2.1 = IpAddress: 10.0.0.100
SNMP for Layer 7 Based Services
The root OID for Layer 7 front-end services is: 1.3.6.1.4.1.29385.106.1.0 The root OID for Layer 7 back-end services is: 1.3.6.1.4.1.29385.106.1.1 Front end stats are returned by invoking:
[root@lbmaster ~]# snmpwalk -c public -v 2c localhost 1.3.6.1.4.1.29385.106.1.0 SNMPv2-SMI::enterprises.29385.106.1.0.0.1.0 = STRING: "stats"
SNMPv2-SMI::enterprises.29385.106.1.0.1.1.0 = STRING: "FRONTEND" SNMPv2-SMI::enterprises.29385.106.1.0.2.1.0 = "" SNMPv2-SMI::enterprises.29385.106.1.0.3.1.0 = "" SNMPv2-SMI::enterprises.29385.106.1.0.4.1.0 = STRING: "0" SNMPv2-SMI::enterprises.29385.106.1.0.5.1.0 = STRING: "0" SNMPv2-SMI::enterprises.29385.106.1.0.6.1.0 = STRING: "2000" … etc.
Back end stats are returned by invoking:
[root@lbmaster ~]# snmpwalk -c public -v 2c localhost 1.3.6.1.4.1.29385.106.1.1 SNMPv2-SMI::enterprises.29385.106.1.1.0.1.0 = STRING: "stats"
SNMPv2-SMI::enterprises.29385.106.1.1.1.1.0 = STRING: "BACKEND" SNMPv2-SMI::enterprises.29385.106.1.1.2.1.0 = STRING: "0" SNMPv2-SMI::enterprises.29385.106.1.1.3.1.0 = STRING: "0" SNMPv2-SMI::enterprises.29385.106.1.1.4.1.0 = STRING: "0" SNMPv2-SMI::enterprises.29385.106.1.1.5.1.0 = STRING: "0" SNMPv2-SMI::enterprises.29385.106.1.1.6.1.0 = STRING: "2000" SNMPv2-SMI::enterprises.29385.106.1.1.7.1.0 = STRING: "0" SNMPv2-SMI::enterprises.29385.106.1.1.8.1.0 = STRING: "0" … etc.
Monitoring Layer 7 RIPs using SNMP
To list the Real Servers use the command shown below:
[root@lbmaster ~]# snmpwalk -c public -v 2c localhost 1.3.6.1.4.1.29385.106.1.2.1 SNMPv2-SMI::enterprises.29385.106.1.2.1.1.1 = STRING: "backup"
SNMPv2-SMI::enterprises.29385.106.1.2.1.1.2 = STRING: "IIS1" SNMPv2-SMI::enterprises.29385.106.1.2.1.1.3 = STRING: "IIS2" SNMPv2-SMI::enterprises.29385.106.1.2.1.2.1 = STRING: "backup" SNMPv2-SMI::enterprises.29385.106.1.2.1.2.2 = STRING: "RDP1" SNMPv2-SMI::enterprises.29385.106.1.2.1.2.3 = STRING: "RDP2"
To get the health status of each of these Real Servers use the command shown below: [root@lbmaster ~]# snmpwalk -c public -v 2c localhost 1.3.6.1.4.1.29385.106.1.2.17 SNMPv2-SMI::enterprises.29385.106.1.2.17.1.1 = STRING: "no check"
SNMPv2-SMI::enterprises.29385.106.1.2.17.1.2 = STRING: "UP" SNMPv2-SMI::enterprises.29385.106.1.2.17.1.3 = STRING: "DOWN" SNMPv2-SMI::enterprises.29385.106.1.2.17.2.1 = STRING: "no check" SNMPv2-SMI::enterprises.29385.106.1.2.17.2.2 = STRING: "DOWN" SNMPv2-SMI::enterprises.29385.106.1.2.17.2.3 = STRING: "DOWN"
Configuring Email Alerts
Email alerts can be configured for Layer 4 Virtual Services. This enables emails to be sent when Real Servers fail there health-checks and are removed from the table, and also when they subsequently start to pass checks and are re-added to the table. Settings can be configured globally that apply to all VIPs or individually to each VIP.
Email alerts for Layer 7 services is not currently directly supported, but it is possible to install tools such as the opensource utility Logwatch and configure this to monitor logs and send out alerts as required. For more details on using this please contact our support team: [email protected]
Global Alerts
To configure global email alerts:
In the WUI, open Cluster Configuration > Layer 4 Advanced Configuration
Enter an appropriate email address in the Email Alert Source Address field e.g. [email protected]
Enter an appropriate email address in the Email Alert Destination Address field e.g. [email protected]
Click UpdateN.B. Make sure that you also configure an SMTP smart host using the WUI option: Local Configuration > Physical Advanced configuration > Smart Host. This will be auto-configured (if a DNS server has already been defined) to the MX record of the destination address domain name.
VIP Level Alerts
To configure VIP level email alerts:
In the WUI, open Cluster Configuration > Layer 4 Advanced Configuration
Enter an appropriate email address in the Email Alert Source Address fielde.g. [email protected]
In the WUI, open Cluster Configuration > Layer 4 Virtual Service and click [Modify] next to the VIP to be configured
Enter an appropriate email address in the Email Alert Destination Address field e.g. [email protected]
Click UpdateN.B. Make sure that you also configure an SMTP smart host using the WUI option: Local Configuration > Physical Advanced configuration > Smart Host. This will be auto-configured (if a DNS server has already been defined) to the MX record of the destination address domain name.