Cisco ACE 4710 - Health Monitoring for Real Servers
Hi,
I have setup the following health probe to check for the existence of a specific web page. My intention is that when the web page is removed, the health check fails and the rserver status changes to 'out of service'. Unfortunately, when I remove the web page, I see the health check fail, and the rserver state change to 'PROBE-FAILED', however the rserver does not go 'out of service' and continues to respond to requests.
Can anyone see where I'am going wrong?
Health check probe config
probe http live_http_int
interval 15
passdetect interval 60
request method get url /loadbalancer/internal.html
expect status 199 201
open 10
RSERVER config
rserver host Server1
description Server1
ip address 10.10.10.1
conn-limit max 4000000 min 4000000
probe live_http_int
inservice
rserver host Server2
ip address 10.10.10.2
conn-limit max 4000000 min 4000000
probe live_http_int
inservice
Hi syannetwork,
I think you have to "force" the failed server to close the connection when it has failed. Otherwise it will still serve the available HTML pages.
Have a look at the "Configuring the ACE Action when a Server Fails" in the "Cisco Application Control Engine Module Server Load-Balancing Configuration Guide" and let me know if the following command helped:
conf t
serverfarm host ServerFarm
failaction purge
Have a good WE.
Cheers
LPL
Similar Messages
-
ACE 4710 health monitoring probe
New to ACE4710
Can someone please explain the effects.
Associate the probe with one of the following:
A real server.
A real server and then associate the real server with a server farm. You can associate a single probe or multiple probes with real servers within a server farm.
A server farm. All servers in the server farm receive probes of the associated probe types.Hi,
Here is the expected operation for each of those cases:
A real server.
If the server is not associated with any serverfarm, the status will not be probed (the rserver will be marked as INACTIVE)
A real server and then associate the real server with a server farm. You can associate a single probe or multiple probes with real servers within a server farm.
The probe will only be applied to that specific server
A server farm. All servers in the server farm receive probes of the associated probe types.
The probe will be applied to all the servers in the serverfarm.
Another thing to take into account is that (by default) if more than one probe is associated to a server (either directly or through a serverfarm), all the probes need to succeed to consider the server operational. You can also add the command "fail on all" to a serverfarm or rserver to change this behavior and only consider the server as down when all the probe fail
I hope this answers your question
Regards
Daniel -
Need help to Configure Cisco ACE 4710 Cluster Deployment
Dear Experts,
I'm newbie for Cisco ACE 4710, and still I'm in learning stage. Meanwhile I got chance at my work place to deploy a Cisco ACE 4710 cluster which should load balance the traffic between two Application Servers based on HTTP and HTTPS traffic. So I was looking for good deployment guide in Cisco SBA knowledge base then finall found this guide.
http://www.cisco.com/en/US/docs/solutions/SBA/February2013/Cisco_SBA_DC_AdvancedServer-LoadBalancingDeploymentGuide-Feb2013.pdf
This guide totally fine with my required deployment model. I have same deployment environment as this guide contains with ACE cluster that connects to two Cisco 3750X (Stack) switches. But I have some confusion places in this guide
This guide follow the "One-armed mode" as a deployment method. But when I go through it further I have noticed that they have configured server VLAN as a 10.4.49.0/24 (all servers reside in it) and Client side VIP also in same VLAN which is 10.4.49.100/24 (even NAT pool also).
My confusion is, as I have learned about Cisco ACE 4710 one-armed mode deployment method, it should has two VLAN segments, one for Client side which client request come and hit the VIP and then second one for Server side. which means besically two VLANs. So please be kind enough to go through above document then tell me where is wrong, what shoud I need to do for the best. Please this is an urgent, so need your help quickly.
Thanks....!
-Amal-Dear Kanwal,
I need quick help for you. Following are the Application LB requirements which I received from my clinet side.
Following detail required for configuring Oracle EBS Apps tier on HA:
LBR IP and Name required to configure EBS APPS Tier (i.e, ap1ebs & ap2ebs nodes)
Suggested IP and Name for LBR:
IP : 172.25.45.x [should be on same 172.25.45 subnet of ap1ebs & ap2ebs nodes]
ebiz.xxxx.lk [on port 80 for http protocol accessibility]
This LBR IP & name must be resolve and respond on DNS network
Server Farm detail for LBR Setup
Following detail will be use for configuring the LBR:
LBR IP and Name :
IP : 172.25.45.x [should be on same 172.25.45 subnet of ap1ebs & ap2ebs nodes]
ebiz.xxxx.lk [on port 80 for http protocol accessibility]
This LBR IP & name must be resolve and respond on DNS network
Server Farm Detail for LBR setup:
Server 1 (EBS App1 Node, ap1ebs):
IP : 172.25.45.19
Server Name: ap1ebs.xxxx.lk [ap1ebs hostname is an example, actual hostname will be use]
Protocol: http
Port: 8000
Server 2 (EBS App2 Node, ap2ebs):
IP : 172.25.45.20
Server Name: ap2ebs.xxxx.lk [ap2ebs hostname is an example, actual hostname will be use]
Protocol: http
Port: 8000
Since my client needs to access URL ebiz.xxxx.lk which should be resolved by IP 172.25.45.21 (virtual IP) via http (80) before they deploy the app on the two servers I just ran web service on both servers (Linux) and was trying to access http://172.25.45.21 it was working fine and gave me index.html page. Now after my client has deployed the application then when he tries to access the page http://172.25.45.21 he cannot see his main login page. But still my testing web servers are there on both servers when I type http://172.25.45.21 it will get index.html page, but not my client web login page. What can I do for this ?
Following are my latest config :
probe http Get-Method
description Check to url access /OA_HTML/OAInfo.jsp
interval 10
faildetect 2
passdetect interval 30
request method get url /OA_HTML/OAInfo.jsp
expect status 200 200
probe udp http-8000-iRDMI
description IRDMI (HTTP - 8000)
port 8000
probe http http-probe
description HTTP Probes
interval 10
faildetect 2
passdetect interval 30
passdetect count 2
request method get url /index.html
expect status 200 200
probe https https-probe
description HTTPS traffic
interval 10
faildetect 2
passdetect interval 30
passdetect count 2
ssl version all
request method get url /index.html
probe icmp icmp-probe
description ICMP PROBE FOR TO CHECK ICMP SERVICE
rserver host ebsapp1
description ebsapp1.xxxx.lk
ip address 172.25.45.19
conn-limit max 4000000 min 4000000
probe icmp-probe
probe http-probe
inservice
rserver host ebsapp2
description ebsapp2.xxxx.lk
ip address 172.25.45.20
conn-limit max 4000000 min 4000000
probe icmp-probe
probe http-probe
inservice
serverfarm host ebsppsvrfarm
description ebsapp server farm
failaction purge
predictor response app-req-to-resp samples 4
probe http-probe
probe icmp-probe
inband-health check log 5 reset 500
retcode 404 404 check log 1 reset 3
rserver ebsapp1 80
conn-limit max 4000000 min 4000000
probe icmp-probe
inservice
rserver ebsapp2 80
conn-limit max 4000000 min 4000000
probe icmp-probe
inservice
sticky http-cookie jsessionid HTTP-COOKIE
cookie insert browser-expire
replicate sticky
serverfarm ebsppsvrfarm
class-map type http loadbalance match-any default-compression-exclusion-mime-type
description DM generated classmap for default LB compression exclusion mime types.
2 match http url .*gif
3 match http url .*css
4 match http url .*js
5 match http url .*class
6 match http url .*jar
7 match http url .*cab
8 match http url .*txt
9 match http url .*ps
10 match http url .*vbs
11 match http url .*xsl
12 match http url .*xml
13 match http url .*pdf
14 match http url .*swf
15 match http url .*jpg
16 match http url .*jpeg
17 match http url .*jpe
18 match http url .*png
class-map match-all ebsapp-vip
2 match virtual-address 172.25.45.21 tcp eq www
class-map type management match-any remote_access
2 match protocol xml-https any
3 match protocol icmp any
4 match protocol telnet any
5 match protocol ssh any
6 match protocol http any
7 match protocol https any
8 match protocol snmp any
policy-map type management first-match remote_mgmt_allow_policy
class remote_access
permit
policy-map type loadbalance first-match ebsapp-vip-l7slb
class default-compression-exclusion-mime-type
serverfarm ebsppsvrfarm
class class-default
compress default-method deflate
sticky-serverfarm HTTP-COOKIE
policy-map multi-match int455
class ebsapp-vip
loadbalance vip inservice
loadbalance policy ebsapp-vip-l7slb
loadbalance vip icmp-reply active
nat dynamic 1 vlan 455
interface vlan 455
ip address 172.25.45.36 255.255.255.0
peer ip address 172.25.45.35 255.255.255.0
access-group input ALL
nat-pool 1 172.25.45.22 172.25.45.22 netmask 255.255.255.0 pat
service-policy input remote_mgmt_allow_policy
service-policy input int455
no shutdown
ft interface vlan 999
ip address 10.1.1.1 255.255.255.0
peer ip address 10.1.1.2 255.255.255.0
no shutdown
ft peer 1
heartbeat interval 300
heartbeat count 10
ft-interface vlan 999
ft group 1
peer 1
no preempt
priority 110
associate-context Admin
inservice
ip route 0.0.0.0 0.0.0.0 172.25.45.1
Hope you will reply me soon
Thanks....!
-Amal- -
TCP SYNSEEN with load balancing Cisco ACE 4710
I have a Cisco ACE 4710 load balancing the traffic to two proxy servers, the configuration is the same since December 2012, but yesterday it stated to show SYNSEEN in the show conn command, and the hosts cannot browse. I think that means that the three-way-handshake is not complete.
If I bypass the ACE the hosts can browse without problems.
I have tested with another ACE appliance and the same configuration but the behaviour is the same.
I need help as soon as possible,
thanks,
I've attached the Show conn, show conn detail and show run.Hi Cesar,
Thank you for your answer,
The issue was solved,
We were running an A3 software version, it seems to have a Bug so it doesn't show the NAT commands in the "show run", so when we made the configuration backup we didn't noticed it.
The ACE reloaded because an electrical failure so it losted the NAT config.
We just upgraded to an A4 version and also added a NAT/PAT to enable the communication between the Clients and the Proxy.
Regards, -
CISCO NAC deployment with ASA for internal servers (DMZ)
We have deployed cisco ASA for our clients access to DMZ servers few months ago. Now we want to integrate cisco NAC solution without removing ASA
from infrastructure. What will be the best deployment mode of cisco NAC so that clients can also pass through cisco ASA access list also for filtering before reaching to dmz servers.
what gateway clients will use. Plz help.
Should i use Virtual Gateway or Real Gateway for NAC. Client should first come to NAC(CAS) and then through ASA to reach DMZ servers.Hello,
This should work. Please review the attached PDF for more clarity on this topic: https://supportforums.cisco.com/docs/DOC-9102
HTH,
Faisal -
ACE 4710 eHealth monitoring of context
Hi,
Our eHeath people tell me they cannot stat anything in any of the contexts (excluding Admin) on the ACE, i can snmpwalk the various contexts using the '@context' suffix.
e.g. snmpwalk -c community@context2 10.1.1.1 .1.3.6.1.4.1.9.9.161
eHealth can only route to the Admin context.
Does anybody know if eHealth can access the ACE contexts in this fashion?
Thanks
ChrisHi,
Here is the expected operation for each of those cases:
A real server.
If the server is not associated with any serverfarm, the status will not be probed (the rserver will be marked as INACTIVE)
A real server and then associate the real server with a server farm. You can associate a single probe or multiple probes with real servers within a server farm.
The probe will only be applied to that specific server
A server farm. All servers in the server farm receive probes of the associated probe types.
The probe will be applied to all the servers in the serverfarm.
Another thing to take into account is that (by default) if more than one probe is associated to a server (either directly or through a serverfarm), all the probes need to succeed to consider the server operational. You can also add the command "fail on all" to a serverfarm or rserver to change this behavior and only consider the server as down when all the probe fail
I hope this answers your question
Regards
Daniel -
Cisco Network Assistant - Health Monitor Not Showing Bandwidth Utilization
Hello,
Ive setup a new network with 3x 2960 and 2x 3650 switches, trying to view the bandwidth utilization per switch in cisco network assistant in the health monitor unfortunatly it show 0%. I know there is alot of traffic passing through the switches, the other monitors are working correctly (temp, ram and cpu). Is there any special settings that are needed in the switch?
ThanksSrikanth Achanta,
Thanks for the help! Here is the output from putty.
XXX-Switch1#show controllers utilization
Port Receive Utilization Transmit Utilization
Gi0/1 0 0
Gi0/2 0 0
Gi0/3 0 0
Gi0/4 0 0
Gi0/5 0 0
Gi0/6 0 0
Gi0/7 0 0
Gi0/8 0 0
Gi0/9 0 0
Gi0/10 0 0
Gi0/11 0 0
Gi0/12 0 0
Gi0/13 0 0
Gi0/14 0 0
Gi0/15 0 0
Gi0/16 0 0
Gi0/17 0 0
Gi0/18 0 0
Gi0/19 0 0
Gi0/20 0 0
Gi0/21 0 0
Gi0/22 0 0
Gi0/23 0 0
Gi0/24 0 0
Gi1/1 0 0
Gi1/2 0 0
Gi1/3 0 0
Gi1/4 0 0
Te1/1 0 0
Te1/2 0 0
Total Ports : 30
Switch Receive Bandwidth Percentage Utilization : 0
Switch Transmit Bandwidth Percentage Utilization : 0
Switch Fabric Percentage Utilization : 0
XXX-Switch1#show interfaces | include packets
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
5934288 packets input, 546197579 bytes, 0 no buffer
308885 packets output, 112398123 bytes, 0 underruns
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
0 packets input, 0 bytes
0 input packets with dribble condition detected
0 packets output, 0 bytes, 0 underruns
5 minute input rate 471000 bits/sec, 109 packets/sec
5 minute output rate 191000 bits/sec, 104 packets/sec
315586906 packets input, 252876271812 bytes, 0 no buffer
0 input packets with dribble condition detected
267801306 packets output, 88017856802 bytes, 0 underruns
5 minute input rate 52000 bits/sec, 37 packets/sec
5 minute output rate 55000 bits/sec, 37 packets/sec
120529568 packets input, 27639696244 bytes, 0 no buffer
0 input packets with dribble condition detected
141742070 packets output, 32628299588 bytes, 0 underruns
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 1000 bits/sec, 1 packets/sec
5028 packets input, 468079 bytes, 0 no buffer
0 input packets with dribble condition detected
7868783 packets output, 893479978 bytes, 0 underruns
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 2000 bits/sec, 2 packets/sec
27290987 packets input, 25279841114 bytes, 0 no buffer
0 input packets with dribble condition detected
34291062 packets output, 16098960773 bytes, 0 underruns
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 1000 bits/sec, 2 packets/sec
3431939 packets input, 1615199699 bytes, 0 no buffer
0 input packets with dribble condition detected
20491634 packets output, 4044194406 bytes, 0 underruns
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 2000 bits/sec, 2 packets/sec
21992856 packets input, 7784577454 bytes, 0 no buffer
0 input packets with dribble condition detected
47483488 packets output, 32259133953 bytes, 0 underruns
5 minute input rate 4000 bits/sec, 2 packets/sec
5 minute output rate 4000 bits/sec, 3 packets/sec
17585313 packets input, 6353936617 bytes, 0 no buffer
0 input packets with dribble condition detected
40272645 packets output, 23412383942 bytes, 0 underruns
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
15684208 packets input, 5064927935 bytes, 0 no buffer
0 input packets with dribble condition detected
37918769 packets output, 18601560856 bytes, 0 underruns
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 1000 bits/sec, 1 packets/sec
3150289 packets input, 734752119 bytes, 0 no buffer
0 input packets with dribble condition detected
19003285 packets output, 2764534874 bytes, 0 underruns
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 1000 bits/sec, 1 packets/sec
9029922 packets input, 2596828776 bytes, 0 no buffer
0 input packets with dribble condition detected
26350637 packets output, 9197196784 bytes, 0 underruns
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
7064148 packets input, 2426044345 bytes, 0 no buffer
0 input packets with dribble condition detected
22569075 packets output, 8606781954 bytes, 0 underruns
5 minute input rate 2000 bits/sec, 1 packets/sec
5 minute output rate 6000 bits/sec, 3 packets/sec
17875471 packets input, 6103242910 bytes, 0 no buffer
0 input packets with dribble condition detected
36793666 packets output, 17156441845 bytes, 0 underruns
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
19264746 packets input, 8318993561 bytes, 0 no buffer
0 input packets with dribble condition detected
40577274 packets output, 20008103681 bytes, 0 underruns
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
0 packets input, 0 bytes, 0 no buffer
0 input packets with dribble condition detected
0 packets output, 0 bytes, 0 underruns
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
1073682 packets input, 524894617 bytes, 0 no buffer
0 input packets with dribble condition detected
1290197 packets output, 967649887 bytes, 0 underruns
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 2000 bits/sec, 2 packets/sec
1434841 packets input, 399859897 bytes, 0 no buffer
0 input packets with dribble condition detected
15034817 packets output, 1988146136 bytes, 0 underruns
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 31000 bits/sec, 1 packets/sec
18246575 packets input, 8048146812 bytes, 0 no buffer
0 input packets with dribble condition detected
34632744 packets output, 15331407257 bytes, 0 underruns
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
12575644 packets input, 3507267403 bytes, 0 no buffer
0 input packets with dribble condition detected
27415447 packets output, 13019686162 bytes, 0 underruns
5 minute input rate 9000 bits/sec, 1 packets/sec
5 minute output rate 60000 bits/sec, 2 packets/sec
16988554 packets input, 6347935146 bytes, 0 no buffer
0 input packets with dribble condition detected
40488073 packets output, 23658053615 bytes, 0 underruns
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 1000 bits/sec, 2 packets/sec
1775464 packets input, 456920432 bytes, 0 no buffer
0 input packets with dribble condition detected
5550312 packets output, 848939175 bytes, 0 underruns
5 minute input rate 74000 bits/sec, 62 packets/sec
5 minute output rate 276000 bits/sec, 66 packets/sec
38109701 packets input, 21483991198 bytes, 0 no buffer
0 input packets with dribble condition detected
53920463 packets output, 35745966772 bytes, 0 underruns
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 2000 bits/sec, 2 packets/sec
3905203 packets input, 1197213173 bytes, 0 no buffer
0 input packets with dribble condition detected
9322988 packets output, 3398916481 bytes, 0 underruns
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 1000 bits/sec, 1 packets/sec
31147644 packets input, 7922363688 bytes, 0 no buffer
0 input packets with dribble condition detected
64110078 packets output, 59004959626 bytes, 0 underruns
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
5916020 packets input, 2203139928 bytes, 0 no buffer
0 input packets with dribble condition detected
17783154 packets output, 6763038614 bytes, 0 underruns
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
0 packets input, 0 bytes, 0 no buffer
0 input packets with dribble condition detected
0 packets output, 0 bytes, 0 underruns
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
0 packets input, 0 bytes, 0 no buffer
0 input packets with dribble condition detected
0 packets output, 0 bytes, 0 underruns
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
0 packets input, 0 bytes, 0 no buffer
0 input packets with dribble condition detected
0 packets output, 0 bytes, 0 underruns
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
0 packets input, 0 bytes, 0 no buffer
0 input packets with dribble condition detected
0 packets output, 0 bytes, 0 underruns
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
0 packets input, 0 bytes, 0 no buffer
0 input packets with dribble condition detected
0 packets output, 0 bytes, 0 underruns
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
0 packets input, 0 bytes, 0 no buffer
0 input packets with dribble condition detected
0 packets output, 0 bytes, 0 underruns
XXX-Switch1#show interfaces | include line protocol
Vlan1 is up, line protocol is up
FastEthernet0 is down, line protocol is down
GigabitEthernet0/1 is up, line protocol is up (connected)
GigabitEthernet0/2 is up, line protocol is up (connected)
GigabitEthernet0/3 is up, line protocol is up (connected)
GigabitEthernet0/4 is up, line protocol is up (connected)
GigabitEthernet0/5 is up, line protocol is up (connected)
GigabitEthernet0/6 is up, line protocol is up (connected)
GigabitEthernet0/7 is up, line protocol is up (connected)
GigabitEthernet0/8 is up, line protocol is up (connected)
GigabitEthernet0/9 is up, line protocol is up (connected)
GigabitEthernet0/10 is up, line protocol is up (connected)
GigabitEthernet0/11 is up, line protocol is up (connected)
GigabitEthernet0/12 is up, line protocol is up (connected)
GigabitEthernet0/13 is up, line protocol is up (connected)
GigabitEthernet0/14 is down, line protocol is down (notconnect)
GigabitEthernet0/15 is down, line protocol is down (notconnect)
GigabitEthernet0/16 is up, line protocol is up (connected)
GigabitEthernet0/17 is up, line protocol is up (connected)
GigabitEthernet0/18 is up, line protocol is up (connected)
GigabitEthernet0/19 is up, line protocol is up (connected)
GigabitEthernet0/20 is up, line protocol is up (connected)
GigabitEthernet0/21 is up, line protocol is up (connected)
GigabitEthernet0/22 is up, line protocol is up (connected)
GigabitEthernet0/23 is up, line protocol is up (connected)
GigabitEthernet0/24 is down, line protocol is down (notconnect)
GigabitEthernet1/1 is down, line protocol is down (notconnect)
GigabitEthernet1/2 is down, line protocol is down (notconnect)
GigabitEthernet1/3 is down, line protocol is down (notconnect)
GigabitEthernet1/4 is down, line protocol is down (notconnect)
TenGigabitEthernet1/1 is down, line protocol is down (notconnect)
TenGigabitEthernet1/2 is down, line protocol is down (notconnect)
XXX-Switch1#show interfaces | include line errors
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 output errors, 2 interface resets
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 output errors, 0 collisions, 1 interface resets
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 output errors, 0 collisions, 1 interface resets
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 output errors, 0 collisions, 1 interface resets
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 output errors, 0 collisions, 1 interface resets
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 output errors, 0 collisions, 1 interface resets
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 output errors, 0 collisions, 1 interface resets
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 output errors, 0 collisions, 1 interface resets
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 output errors, 0 collisions, 1 interface resets
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 output errors, 0 collisions, 1 interface resets
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 output errors, 0 collisions, 1 interface resets
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 output errors, 0 collisions, 1 interface resets
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 output errors, 0 collisions, 1 interface resets
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 output errors, 0 collisions, 1 interface resets
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 output errors, 0 collisions, 1 interface resets
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 output errors, 0 collisions, 1 interface resets
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 output errors, 0 collisions, 1 interface resets
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 output errors, 0 collisions, 1 interface resets
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 output errors, 0 collisions, 1 interface resets
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 output errors, 0 collisions, 1 interface resets
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 output errors, 0 collisions, 1 interface resets
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 output errors, 0 collisions, 1 interface resets
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 output errors, 0 collisions, 1 interface resets
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 output errors, 0 collisions, 1 interface resets
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 output errors, 0 collisions, 1 interface resets
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 output errors, 0 collisions, 1 interface resets
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 output errors, 0 collisions, 0 interface resets
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 output errors, 0 collisions, 0 interface resets
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 output errors, 0 collisions, 0 interface resets
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 output errors, 0 collisions, 0 interface resets
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 output errors, 0 collisions, 0 interface resets
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 output errors, 0 collisions, 0 interface resets
Dave -
Biztalk Health Monitor for BTS 2010
Hi,
Just moving through the blogs on MSDn, I found out that BHM tool is now available for BTS 2010, my question is do we have to pay any more cost to run this snap in with our licensed Biztalk or not??
Regards,
Mandar DharmadhikariBizTalk Health Monitoring(BHM) Supports BizTalk 2010 and 2013 as well . See below link for more info
http://social.msdn.microsoft.com/Forums/en-US/59df885e-603a-47fa-a114-81b8c18f2ba0/biztalk-monitoring?forum=biztalkgeneral#32b2072c-c272-4081-911b-137db815504b
Thanks
Abhishek -
Guidelines for Health Monitoring for TimesTen
This document provides some guidance on monitoring the health of a TimesTen
datastore. Information is provided on monitoring the health of the
datastore itself, and on monitoring the health of replication.
There are two basic mechanisms for monitoring TimesTen:
1. Reactive - monitor for alerts either via SNMP traps (preferred) or
by scanning the Timesten daemon log (very difficult) and reacting
to problms as they occur.
2. Proactive - probe TimesTen periodically and react if problems, or
potential problems, are detected.
This document focusses on the second (proactive) approach.
First, some basic recommendations and guidelines relating to monitoring
TimesTen:
1. Monitoring should be implemented as a separate process which maintains
a persistent connection to TimesTen. Monitoring schemes (typically based
on scripts) that open a connection each time they check TimesTen impose
an unnecessary and undesireable loading on the system and are discouraged.
2. Many aspects of monitoring are 'stateful'. They require periodic
sampling of some metric maintained by TimesTen and comparing its
value with the previous sample. This is another reason why a separate
process with a persistent connection is desireable.
3. A good monitoring implementation will be configurable since the values
used for some of the chcks may depend on e.g. the TimesTen configuration
in use or the workload being handled.
MONITORING THE HEALTH OF A DATASTORE
====================================
At the simples level, this can be achieved by performing a simple SELECT
against one of the system tables. The recommended table to use is the
SYS.MONITOR table. If this SELECT returns within a short time then the
datastore can be considered basically healthy.
If the SELECT does not return within a short time then the datastroe is
stuck in a low level hang situation (incredibly unlikely and very serious).
More likely, the SELECT may return an error such as 994 or 846 indicating
that the datastore has crashed (again very unlikely, but possible).
A slightly more sophisticated version would also include an update to a
row in a dummy table. This would ensure that the datastore is also capable
of performing updates. This is important since if the filesystem holding
the trsnaction logs becomes full the datastore may start to refuse write
operations while still allowing reads.
Now, the SYS.MONITOR table contains many useful operational metrics. A more
sphisticated monitoring scheme could sample some of these metrics and
compute the delta between subsequent samples, raising an alert if the
delta exceeds some (configurable) threshold.
Some examples of metrics that could be handled in this way are:
PERM_IN_USE_SIZE and PERM_IN_USE_HIGH_WATER compared to PERM_ALLOCATED_SIZE
(to detect if datastore is in danger of becoming full).
TEMP_IN_USE_SIZE and TEMP_IN_USE_HIGH_WATER compared to TEMP_ALLOCATED_SIZE
(ditto for temp area).
XACT_ROLLBACKS - excessive rollbacks are a sign of excessive database
contention or application logic problems.
DEADLOCKS - as for XACT_ROLLBACKS.
LOCK_TIMEOUTS - excessive lock timeouts usually indicate high levels of
contention and/or application logic problems.
CMD_PREPARES & CMD_REPREPARES - it is very important for performance that
applications use parameterised SQL statements that they prepare just once
and then execute many times. If these metrics are continuously increasing
then this points to bad application programming which will be hurting
performance.
CMD_TEMP_INDEXES - if this value is increasing then the optimiser is
comntinually creating temporary indices to process certain queries. This
is usually a serious performance problem and indicates a missing index.
LOG_BUFFER_WAITS - of this value is increasing over timne this indicates
inadequate logging capacity. Yiou may need to increase the size of the
datastore log buffer (LogBuffSize) and log file size (LogFileSize). If that
does not alleviate the problem you may need to change your disk layout or
even obtain a higher performance storage subsystem.
LOG_FS_READS - this indicates an inefficieny in 'log snoop' processing as
performed by replication and the XLA/JMS API. To alleviate this you should
try increasing LogBuffSize and LogFileSize.
Checking these metrics is of course optional and not necessary for a basic
healthy/failed decision but if you do check them then you will detect more
subtle problems in advance and be able to take remedial action.
MONITORING THE HEALTH OF REPLICATION
====================================
This is a little more complex but is vital to achieve a robust and reliable
system. ideally, monitorting should be implemented at both datstores, the
active and the standby. There are many more failure modes possible for
a replicated system than for a standalone datastore and it is not possible
to ennumerate them all here. However the information provided here should
be sufficient to form the basis of a robist monitoring scheme.
Monitoring replication at the ACTIVE datastore
1. CALL ttDataStoreStatus() and check result set;
If no connections with type 'replication' exists, conclude that
replication agents are stopped, restart the agents and skip
next steps.
It is assumed here that the replication start policy is 'norestart'.
An alarm about unstable replication agents should be raised
if this is Nth restart in M seconds (N and M are configuration parameters).
The alarm can later be cleared when the agents stayed alive K
seconds (K is configuration parameter).
2. CALL ttReplicationStatus() and check result set;
This returns a row for every replication peer for this datastore.
If the pState is not 'start' for any peer, raise an alarm about paused or
stopped replication and skip rest of the steps.
It is assumed that master cannot help the fact that state is not
'start'. An operator may have stopped/paused the replication or
TimesTen stopped the replication because of fail threshold
strategy. In former case the operator hopefully starts the replication
sooner or later (of course, after that TimesTen may stop it again
because of the fail threshold strategy). In latter case the standby
side monitor process should recognise the fact and duplicate the data
store with setMasterRepStart-option which sets state back to 'start'.
If for any peer, lastMsg > MAX (MAX is a configuration parameter), raise
an alarm for potential communication problems.
Note that if replication is idle (nothing to replicate), or there is
very little replication traffic, the value for lastMsg may become as
high as 60 seconds without indicating any problem. The test logic
should cater for this (i.e. MAX must be > 60 seconds).
3. CALL ttBookmark();
Compute the holdLSN delta between the values from this call and the
previous call and if the delta is greater than maximum allowed
(configuration parameter), raise an alarm about standby
that is too far behind. Continue to next step.
Notice that maximum delta should be less than FAILTHRESHOLD * logSize.
4. CALL ttRepSyncSubscriberStatus(datastore, host);
This step is only needed if you are using RETURN RECEIPT or RETURN TWOSAFE
with the optional DISABLE RETURN feature.
If disabled is 1, raise an alarm for disabled return service.
Continue to next step. If RESUME RETURN policy is not enabled we could,
of course, try to enable return service again (especially when DURABLE
COMMIT is OFF).
There should be no reason to reject TimesTen own mechanisms that
control return service. Thus, no other actions for disabled return
service.
Monitoring replication at the STANDBY datastore
1. CALL ttDataStoreStatus();
If no connections with type 'replication' exists, conclude that
replication agents are stopped, restart the agents and skip
next steps.
It is assumed that replication start policy is 'norestart'.
An alarm about unstable replication agents should be raised
if this is Nth restart in M seconds (N and M are configuration parameters).
The alarm can later be cleared when the agents stayed alive K
seconds (K is configuration parameter).
2. Call SQLGetInfo(...,TT_REPLICATION_INVALID,...);
If the status is 1, this indicates that the active store has marked this store
as failed due to it being too far out of sync due to log FAILTHRESHOLD.
Start recovery actions by destroying the datastore and recreating via a
'duplicate' operation from the active.
3. Check 'timerecv' value for relevant row in TTREP.REPPEERS
If (timerecv - previous timerecv) > MAX (MAX is a configuration parameter),
raise an alarm for potential communication problems.
You can determine the correct row in TTREP.REPPEERS by first getting the
correct TT_STORE_ID value from TTREP.TTSTORES based on the values in
HOST_NAME and TT_STORE_NAME (you want the id corresponding to the active
store) and then using that to query TTREP.REPPEERS (you can use a join if
you like).
The recovery actions that should be taken in the event of a problem with
replication depend on several factors:
1. The application requirements
2. The type of replication configuration
3. The replication mode (asynchronous, return receipt or return twosafe)
that is in use
Consult the Timesten replication guide for information on detailed recovery
procedures for each combination.
================================ END ==================================The information in the forum article is the abridged text of a whitepaper I wrote recommending best practice for building a monitoring infrastructure for TimesTen. i.e. you write an 'application' in C, C++ or Java that performs these monitoring activities and run it continually in production against your datastores. Various aspects of the behaviour of the application could be controlled by configurable parameters; these are not TimesTen parameters but parameters defined and used by the monitoring application.
In the specific case you mentioned, the 'lastMsg' value returned by ttReplicationStatus is the number of seconds since the last message was received from that peer. The monitoring application would compare this against some meaningful threshold (maybe 30 seconds) and if lastMsg is > that value, raise an alarm. To allow flexibility, the value compared against )MAX) should be configurable.
Does that make sense?
Chris -
Disable SQL Monitoring for few servers
Hi Team,
I need to disable complete SQL Monitoring from all SQL servers except for a couple of servers.
For this I disabled the discovery "SQL Server Installation Seed" that is targeted on "Windows Server" class. Even after applying this override, I see that my objects are discovered in SQL server classes and I still get SQL server alerts
for all the SQL servers.
I am running SCOM 2012 SP1, so do I need to run "Remove-SCOMDisabledClassInstance"?
Also am I disabling the discovery for the correct class "Installation Seed"?
Thanks,
S K AgrawalHi Faizan,
Suppose you want to disable monitoring for a particular set of SQL servers. Here are the steps to be followed -
1) Create a group of these SQL servers.
2) Considering these are SQL server 2008, go to Authoring--> Object Discoveries.
3) Then disable the discovery for "Installation seed" class because that is targeted on "windows Server" class and is the base class for all other SQL Classes. You can do this by creating an override and disabling the discovery for the group created in Step
1.
4) Open a Operations Manager PowerShell window and run "Remove-SCOMDisabledClassInstance". You might get some error about RuleID and ObjectID. Don't worry about that and keep running "Remove-SCOMDisabledClassInstance" a few more times, finally you will get
a message of command completed successfully.
5) Then to confirm that discovery has been disabled, wait for few minutes and then go to Monitoring--> Discovered Inventory and change the target type to any of the SQL server 2008 class. You will not find the SQL servers from the group in the discovered
inventory.
To Re-enable the SQL monitoring, just remove the override MP or go to "installation seed" class for SQL server 2008. Open Override Summary, Click on Edit, and Remove the override where you have disabled the discovery.
I hope this helps.
Please mark this as Answer if this helped you. -
DSWP : activate monitoring for other servers
We have added some non-SAP servers and applications in our monitoring
solution.
When I setup the system monitoring (DSWP Tcode) and I try to add CCMS
alert for "other servers", these alerts are not display in the
monitoring. It works well for "other software components", but we need
to make a distinction between servers.before ur system is attached to load balancing, your both physical web servers should have a default peoplesoft login url, see you can access the web servers separately with that urls.
Thanks -
Battery Health monitor for iphone 4
hi i would just like to know if there is something that can measure the battery health of iphone 4 i did purchase accura because it appeared to show battery health in the ad on app store but it didn't
There's an app called 'iBackupBot' for windown and mac, by a company called iCopyBot. It has a free trial and allows you to measure the current battery capacity, they have a guide here.
It worked for me with an iPhone 5, iOS 6.1.4- you do have to quit itunes and unlock the device for it to work. -
Health Probe for Proxy Servers
We have 2 Microsoft ISA servers that are using the CSM's as loadbalancing. Does anyone have an example of a probe script that I could use as a template. Idealily we would want the script to either hit our external router or site.
Can you drop me a mail offline ([email protected]) and I can share what I have. Matthew
-
Https health monitor not working on ACE.
Hello Guys,
Hope you are all doing well, i need some help in setting up my https health monitor for real servers.
I am configuring it on ACE appliance 4710 but the probe appears failing.
The VIP is listening on port 443 and 8080, the cert is not uploaded to ACE but eventually it will be on ACE so SSL will terminate on ACE but not at the minute.
The user don't want to enable port 80 on server so will need https health probe configuring. Following is my config for https health probe but it is failing.
probe https SSDSD-ServerAvailability-443
interval 5
passdetect interval 5
ssl version all
request method head url //ssdsd/servlet/SDLogin
expect status 200 200
As per my knowledge https is also an http probe but encrypted. Please see the detailed output below and let me know if i am missing anything.
probe : SSDSD-ServerAvailability-443
type : HTTPS
state : ACTIVE
description :
port : 443 address : 0.0.0.0
addr type : - interval : 5 pass intvl : 5
pass count: 3 fail count: 3 recv timeout: 10
SSL version : All
SSL cipher : RSA_ANY
http method : HEAD
http url : //ssdsd/servlet/SDLogin
conn termination : GRACEFUL
expect offset : 0 , open timeout : 1
regex cache-len : 0
expect regex : -
send data : -
------------------ probe results ------------------
associations ip-address port porttype probes failed passed health
------------ ----------------------+----+--------+------+------+------+------
serverfarm : SSDSD_SF
real : SSDSD-AL2[0]
192.168.225.26 443 VIP 48611 1834 46777 FAILED
Socket state : CLOSED
No. Passed states : 1 No. Failed states : 2
No. Probes skipped : 1 Last status code : 302
No. Out of Sockets : 0 No. Internal error: 0
Last disconnect err : Received invalid status code
Last probe time : Mon Nov 11 04:05:10 2013
Last fail time : Mon Nov 11 02:10:00 2013
Last active time : Fri Nov 8 09:09:31 2013
192.168.225.26 8080 VIP 48613 48613 0 FAILED
Socket state : CLOSED
No. Passed states : 0 No. Failed states : 1
No. Probes skipped : 0 Last status code : 0
No. Out of Sockets : 0 No. Internal error: 0
Last disconnect err : Connection reset by server
Last probe time : Mon Nov 11 04:05:14 2013
Last fail time : Fri Nov 8 08:34:10 2013
Last active time : Never
real : SSDSD-AL3[0]
192.168.225.27 443 VIP 48612 1817 46795 FAILED
Socket state : CLOSED
No. Passed states : 1 No. Failed states : 2
No. Probes skipped : 0 Last status code : 302
No. Out of Sockets : 0 No. Internal error: 0
Last disconnect err : Received invalid status code
Last probe time : Mon Nov 11 04:05:10 2013
Last fail time : Mon Nov 11 02:10:00 2013
Last active time : Fri Nov 8 09:09:31 2013
192.168.225.27 8080 VIP 48613 48613 0 FAILED
Socket state : CLOSED
No. Passed states : 0 No. Failed states : 1
No. Probes skipped : 0 Last status code : 0
No. Out of Sockets : 0 No. Internal error: 0
Last disconnect err : Connection reset by server
Last probe time : Mon Nov 11 04:05:12 2013
Last fail time : Fri Nov 8 08:34:08 2013
Last active time : Never
PHH104-N3-ACE-1/N3#
I am confused with the last status code which shows 302 any help from your side will be a life line for me.
Regards,
Amjad Hashim.Hi Amjad,
I see the last disconnect err: "Received invalid status code" which means that ACE is not getting what is expected (code 200) for it to mark the server as passed.
Also, i see you have configured url "request method head url //ssdsd/servlet/SDLogin", why are you using two slashes "//", can you try with only one?
Also, if you configure probe on TCP PORT 443 does it pass? I see last disconnect err: connection reset by server as well and that could be due to the fact that service was there on server. Looks unlikely since above probes failed due to wrong status code which means that SSL handshake happened.
You can take a pcap on server as well as ACE to see what is going on. You might need to use private key to decrypt the captures if the failure is after SSL handshake has completed to see what status code server is sending. You can also use TCP 443 based probe as workaround till you can arrange pcaps and figure out what is wrong.
Regards,
Kanwal -
ACE 4710 - Monitoring Real Server Showing N/A
I recently installed a Cisco ACE 4710 version A4(2.0) into our test network. Load balancing across a number of web servers appears to be working ok and serving pages to users. However, when i tried to check the real time stats via device manager (Monitor> virtual contexts> context > Real servers) a number of fields specifically "current connections", "total conns", "failed conns" etc were showing N/A. Do I need to enable this somehow i.e. polling, if so how?
Hello Samson,
You may try to reboot the entire ACE 4710, probably during a maintenance window, some java process might have gotten stuck.
If the issue persists then open a TAC case since there are some software defects related to this behavior.
Jorge
Maybe you are looking for
-
Changing from "referenced" to "managed" library
I usually shoot RAW, so I didn't want an 80Gb iPhoto library, especially since I use Adobe Lightroom (far superior). I have however, started using iPhoto to keep track of a small library of JPGs exported from Lightroom (and stored on an external HDD)
-
Duplicating an actor in a video??
Hello, I've been trying to figure out the precise settings for being able to duplicate an actor in a video interacting with himself. I've tried asking around and have been able to narrow it down to this process: 1. import videos from the exact same
-
i don't understand why i cant log in to my fb account using mozilla but with googlechrome i am able to do that.. mozilla can load up the fb site but cannot log in to my fb account.. i am comfortable with using the mozilla as my browser.. pls help tha
-
Got a phishing TEXT to my phone from "ieappleoverstock.cc" saying I had won a MacBook! Came from a 161 number. How did they get my number? I discovered that many others got similar text to their phones from different numbers. What's going on? I live
-
It drives me crazy how albums in Aperture seem to show up in no particular order on my Apple TV 2. For instance, just loaded a new bunch of pictures and go to my Apple TV and I can't find them listed. I have thousands, so perhaps they are there, bu