Keep Alive burst configuration ATA 122

Hi Guys,
Sorry if this is not posted in the correct place, if it is not please advise me and i will move it. I am hoping this is very quick question but basically i have got some ATAs that when plugging in a sounder (bell) or a Cordless analogue phone every 60 seconds or so the osunder makes a noise and the the phone basically thinks it is making a call. done a bit of research and i think this is due to the keep alive burst. Wondered if anybody knew how i can turn this off or extend it to maximum length. I have logged into the cisco and i dont seem to have many options so not sure if this is due to me lookinhg in wrong place or the fact it hasnt a different configuration file.
The ATA are being used on the BT IPVS system.
if somebody could please reply would appreciate it.
thank you

Hi Mateus,
As you can see in the output:-
Aug 01 20:35:02 [IKEv1]Group = DefaultRAGroup, IP = 197.217.68.99, PHASE 1 COMPLETED
Phase 1 is getting completed and QM FSM error indicates the issue with transform-set and/or crypto access-list .
Please try using ESP-3DES and ESP-SHA-HMAC for transform set and let us know how it fares.
You might as well try using PAP as authentication.
Regards,
Dinesh Moudgil
P.S. Please rate helpful posts.

Similar Messages

LB configuration - Keep Alive.

I need to help configure proper load balancing between 2 building modules of Portal server.
SetUp:
Server A - Portal 1,Access Manager 1 , Directory 1
Server B - Portal 2, Access Manager 2, Directory 2
Logical Architecture.
-------- Server A
User Request -------------------->LB ------------>
------ Server B
I need to configure LB in a way that It has keep Alive info for Server A and B.I think there is a configuration required in some xml/property file so that If lets say server A goes down...the LB will automatically direct the next request to server B.
Can somebody point me in the right direction?
Thanks.

Do you need the SSO session created on Server A to failover to Server B or is it ok that the user has to reauthenticate if Server A goes down?
In any case you can either configure the LB for s.c. active cookie based persistence (LB is inserting it's own cookie) or s.c. passive cookie based persistence (LB is using a predefined cookie). I guess this is what you mean by 'keep-alive info' - correct?
Of course this does only work if no SSL is used or if SSL is terminated at the LB.
If SSL is used the only solution is to use client-IP based persistence.
All the above is only needed to prevent cross-talk between AM instances.
-Bernhard

HFM Web Sever Configuration--Keep Alive and Session Time Out Optimal Config

We recently implemented an HFM 9.3.1 environment. We are using Windows 2003 Enterprise SP2 servers with IIS6. We have two HFM Web servers connecting to an application cluster with two application servers in the cluster. We were getting some errors when trying to unlock HFM cells in Workspace, but we were able to perform the functions fine on the application using the WIN32 client.
I opened a ticket with support and they recommended modifying the subcontext.properties file located in %HYPERION_HOME%\deployments\WebLogic9\servers\Workspace\webapps\workspace\conf. They recommended changing the following settings:
#KeepAliveInterval=30
#SessionTimeout=60
From what I understand, these settings are for the communication between the HFM Web Servers and the application cluster servers. I'm wondering how changing these settings may affect our environment. Are there negative effects and/or trade-offs for changing these settings? Is there a recommended threshold or maximum value?

Hi Dinesh,
This cannot be achieved without development enhancements to some standard SAP framework component, to introduce a "keep-alive" concept. If you are using a CMS for CTI or email integration, you need to ensure it supports keeping the communications session alive also.
Sincerely,
Glenn
Glenn Abel
Covington Creative
www.covingtoncreative.com

Weblogic proxy plugin closes keep-alive connections to clients randomly

In short we have following arhitecture:
clients ---> wl proxy plugin 1 ----> weblogic 1
clients ---> wl proxy plugin 2 ----> weblogic 2
Beacuse of the application/installation specific requirements, we are not using failover, one wl proxy always forwards requests to one weblogic (simple configuration).
Application is TR-069 protocol based (SOAP over HTTP) so it very much relays on persistence TCP connections (Connection: keep-alive). This TCP persistence has to work correctly in order that TR-069 messages are exchanged in required order, otherwise we have a error on application layer.
Here and there we've noticed applications errors which suggest that we have some problems in TCP connection between the client and the weblogic server. After sniffing, we've noticed that weblogic proxy plugin (Apache) randomly, or because of some other reason we do not know, decides to close TCP connection to client, even app on weblogic did not request so ???
As a result, client opens new connection to the server with new TR-069 session and it gets bounced beacuse it allready has one open on weblogic server.
We've sniffed, traced everything we could, we were searching for patterns in time, etc... but we can not find the reason why proxy plugin decides to close the connection to the client (not to the weblogic server).
Trace (replaced sensitive information):
Thu Apr 29 15:05:50 2010 <958012725463463784> URL::parseHeaders: CompleteStatusLine set to [HTTP/1.1 200 OK]
Thu Apr 29 15:05:50 2010 <958012725463463784> URL::parseHeaders: StatusLine set to [200 OK]
Thu Apr 29 15:05:50 2010 <958012725463463784> parsed all headers OK
Thu Apr 29 15:05:50 2010 <958012725463463784> sendResponse() : r->status = '200'
Thu Apr 29 15:05:50 2010 <958012725463463784> canRecycle: conn=1 status=200 isKA=1 clen=545 isCTE=0
Thu Apr 29 15:05:50 2010 <958012725463463784> closeConn: pooling for '$IP$/$PORT$'
Thu Apr 29 15:05:50 2010 <958012725463463784> request [$URL$] processed successfully..................
!!!! Now it closes the TCP connection and inserts "Connection: close" HTTP header !!!
WL proxy plugin conf params are:
WebLogicCluster $IP$:$PORT$
DynamicServerList OFF
KeepAliveTimeout 90
MaxKeepAliveRequests 0
KeepAliveSecs 55
Apache worker configuration is:
<IfModule mpm_worker_module>
PidFile var/run/httpd-worker.pid
LockFile var/run/accept-worker.lock
StartServers 2
MinSpareThreads 25
MaxSpareThreads 75
ThreadLimit 200
ThreadsPerChild 200
MaxClients 2000
MaxRequestsPerChild 0
AcceptMutex pthread
</IfModule>
Why weblogic proxy plugin ignores Keep-alive directive and decides to close connection to the client by itself?
Any help?

If a WebLogic Server instance listed in either the WebLogicCluster parameter or a dynamic cluster list returned from WebLogic Server fails, the failed server is marked as "bad" and the plug-in attempts to connect to the next server in the list.
MaxSkipTime sets the amount of time after which the plug-in will retry the server marked as "bad." The plug-in attempts to connect to a new server in the list each time a unique request is received (that is, a request without a cookie).
Note: The MaxSkips parameter has been deprecated as the MaxSkipTime parameter.
See also here: http://download-llnw.oracle.com/docs/cd/E13222_01/wls/docs81/plugins/plugin_params.html
You said the problem arises under significant load. Maybe, it is wise to tune the number file descriptor's on your operating system. HTTP connections are nothing more than TCP sockets on the operating system. All modern operating systems treat sockets as a specialized form of file access and use data structures called file descriptors to track open sockets and files for an operating system process. To control resource usage for processes on the machine, the operating system restricts the number of open file descriptors per process. You should be aware that all TCP connections that have been gracefully closed by an application will go into what is known as the TIME_WAIT state before being discarded by the operating system.
On most unix systems you can use netstat -a | grep TIME_WAIT | wc -l to detemine the number of socket in time_wait state. You have to check with your system adminstrator how to tune the tcp_time_wait_interval. On solaris you can use: /usr/sbin/ndd -set /dev/tcp tcp_time_wait_interval 60000

Changing Default "Keep Alive" & " Max Processing Time" values in SMICM

Dear Experts
As you aware the default values in SMICM --> Go to --> Services The default values "Keep Alive" & " Max Processing Time" of services like HTTP & HTTPS is 30 sec & 60 seconds respectively.
Every times when we restart application server - we are increasing the time values manually. once we restart they will be reset to original 30 & 60 sec respectively.
I want to make customozed values permanently which should not be lost even after restart of application server.
Please Help
Regards
PR

If you have not set the PROCTIMEOUT parameter, TIMEOUT (or icm/keepalive_timeout) defines both the processing timeout and the keepalive timeout. Also, as of release 6.40, the keepalive timeout is limited to a maximum of 30 seconds.
In a system where the default timeout settings of 30 seconds for the keepalive timeout and the processing timeout are not sufficient because of long-running applications, we recommend that you set the TIMEOUT and PROCTIMEOUT parameters for the relevant services so that you can configure them independently of each other. In addition, we recommend that you do not set the TIMEOUT value higher than necessary, for example, to the usual default value of 30 seconds.
We recommend, for example, the following settings:
icm/server_port_0 = PROT=HTTP,PORT=1080,TIMEOUT=30,PROCTIMEOUT=600
to allow a maximum processing time of 10 minutes.
Thanks,
Tanuj

Is it best practice to use a dedicated link between NX7K pair for keep-alive?

I have been using dedicated physical 10G link between pair of NX7k for keep-alive. Is it a best practice? It seems a waste of 10G ports because keep-alives does not need that much bandwidth.
I'm thinking just configure a dedicated VLAN interface in the default VRF, and have it routed through other devices (fir example 6509 core switches) for keep-alive. Has anyone done that before? The goal is not to use dedicated 10G ports for keep-alive.
Thanks a lot.

gwhuang5398 wrote:I have been using dedicated physical 10G link between pair of NX7k for keep-alive. Is it a best practice? It seems a waste of 10G ports because keep-alives does not need that much bandwidth.I'm thinking just configure a dedicated VLAN interface in the default VRF, and have it routed through other devices (fir example 6509 core switches) for keep-alive. Has anyone done that before? The goal is not to use dedicated 10G ports for keep-alive.Thanks a lot.
I agree that using a Tengig port for this purpose is not efficient. The whole idea of peer-keepalive is to have a way to avoid split brain scenarios in case of peer-link failure. For this reason the peer-keepalives should never cross the peer-link as it defeats the original purpose I just cited. Following are some viable options:
You can use the N7K management ports for peer-keepalive functionality. If you have redundant supervisors then make sure you use an external switch (OOB switch for example) to patch the management ports.
You can use dedicated interfaces just like you are doing right now but that would make more sense if you had Gig ports in my opinion.
You can run peer-keepalives inband but you need to make sure this traffic is never routed over the peer-link. It is considered a good practice to use a dedicated VRF for this purpose.
Atif

Keep alive script for HTTPS service with GET method

Hello,
I tried to implement a keep alive to services that support HTPS connections. Ive created a script that opens a tcp connection on port 443 and tries to do a GET of a test web page. This web page only displays OK.
In a resumed form I used the following script commands:
Socket connect host 192.168.136.134 port 443 tcp
Socket send ${SOCKET} GET /teste.template\n\n
Socket waitfor ${SOCKET} 200 2000
Socket disconnect ${SOCKET} graceful
I was unable to receive the expected 200 response and received a message saying string not found, I used the socket inspect command to inspect the sockets internal data buffer and the result was nothing, it seemed empty.
I tried the same operation using a linux machine that has IP connectivity with the Webservers and I was successful.
In the same CSS I have services configured to respond to HTTP sessions. I tried the following script and everything went well
Socket connect host 192.168.136.151 port 80 tcp
Socket send ${SOCKET} HEAD /index.html\n\n
Socket waitfor ${SOCKET} 200 2000
Socket disconnect ${SOCKET} graceful
When I issued the socket inspect command I could in fact see the sockets internal data buffer content.
The CSS is running WebNS 5.0 build 66
Can someone give me a help?
Thanks,
Ricardo Lourenço

Hello,
There is no direct no direct link between TCP and SSL.
So, in spite of having success with the TCP port 443 connection the CSS will not be able to negotiate de security parameters necessary to establish the SSL session.
This was the reason for not having success through the use of the socket commands, as i refered in my original message.
Thanks for your collaboration,
Ricardo Lourenço

How to Keep Alive a specific HFM application

My PRD landscape has 2-3 applications. Whenever any application loads for the first time in the memory, it takes quite some time before it is loaded. Once the application is loaded, the response times are pretty quick and acceptable.
During specific parts of the day / month, a specific application becomes active. During this time, other applications may or may not be used, but one specific application is definitely used. I want to keep this application's cubes loaded in the RAM, so that response times are quick, whenever the user needs it - whether for the first time or otherwise.
How to keep alive a specific application's cubes alive and loaded in RAM? I am not looking for general solution like setting the "FM Service" to Automatic (currently it is set Manual) - setting this to Automatic, will affect all applications. However, I am looking for a specific application at a specific period of time.
I am ok with a custom solution if required. Let me know, what are my options.

I think you are looking for an inappropriate solution to your problem. Most HFM applications take a few seconds to start up. If your application takes such a long time to start up you really need to examine the root cause. Start by removing the Sub NoInput and Sub Input routines in your rules to see if this is the reason the application takes so long to start.
If the removal of those routines does not significantly change the startup time, look through the event logs for possible causes. It is possible you have a connection problem with the Oracle database for example, or you have an environment configuration problem where the HFM application servers have a very slow connection to the database server, or possibly the database server performs poorly.
I strongly suggest you investigate these root casues first before trying to make HFM behave in a non-standard way. Certainly you can start the HFM Management Service, which will start all of your HFM applications and keep them all up and running. This approach does not allow the applications to shut down on their own though. Only use this if you have exchausted your investigations (as I suggsted above).
--Chris

Keep-alive message bridge connection

Hi,
I have setup messaging bridge between WLS 10.3.0.0 and a JBoss Messaging queque, after about 4 hours of inactivity in a queue bridge was disconneted, is there any way to configure keep-alive connection in WLS bridge ?
Thanks,
Lukasz

You can try to set the IdleTimeMaximum setting on your bridge configuration to a very large number. It specifies the maximum amount of time, in seconds, that a messaging bridge instance remains idle.
In “asynchronous” mode, this is the longest amount of time a messaging bridge instance stays idle before it checks the sanity of its connection to the source. In “synchronous” mode, this is the amount of time the messaging bridge can block on a receive call if no transaction is involved.
-Dongbo

Keep alive mgs duration of wlc and ap , minimum bandwidth requried to register ap to wlc from remotely

what is the keep alive duration between cisco 1142 ap and 5508 wlc . Can we able to increase it .
How much bandwidth minimum required to register an ap which is in remote brach .

AP heart can be configured on WLC. Wireless>> Access Points>> Global Configuration>> High Availability>>
H REAP WAN Considerations:
http://www.cisco.com/en/US/products/ps10315/products_tech_note09186a0080736123.shtml#WAN

Disabling Keep Alive

We are using GWT with Glassfish and Sun Web server. We're encountering occassional problems causing the servlet to fail with "Client did not send xxxx bytes" exception.
I read in another post elsewhere that people have solved this problem in Glassfish-Apache configuration with the following settings:
SetEnv force-proxy-request-1.0 1
SetEnv proxy-nokeepalive 1
Can someone tell me what is the equivalent setting in Sun Webserver?
Thanks

Try "set-reverse-proxy-prop"
[http://docs.sun.com/app/docs/doc/820-2204/set-reverse-proxy-prop-1?l=en&a=view|http://docs.sun.com/app/docs/doc/820-2204/set-reverse-proxy-prop-1?l=en&a=view]
* use-keep-alive Indicates whether the HTTP client should attempt to use persistent connections. The default value is true.
* keep-alive-timeout The maximum number of seconds to keep a persistent connection open. The default value is 29.
* always-use-keep-alive Indicates whether the HTTP client can reuse the existing persistent connections for all types of requests. The default value is false, indicating that persistent connections will not be reused for non-GET requests or for requests with a body.
* protocol The HTTP protocol version string. By default, the HTTP client uses either HTTP/1.0 or HTTP/1.1 based on the contents of the HTTP request. In general, you should not use the protocol parameter unless you encounter specific protocol interoperability problems.
...So, probably this will work for you:
set-reverse-proxy-prop use-keep-alive=false protocol="HTTP/1.0"

IPSec Tunnel - Keep alives

Hi All,
Have just configured an IPSec VPN peered with a Fortigate 610B. The issue i am having is that the line-protocol keeps going down due to inactivity on the tunnel.
I have keep alives configured as you will see below, however they dont appear to be working...
Any suggestions would be appreciated.
crypto isakmp policy 1
encr 3des
authentication pre-share
group 2
crypto isakmp key <password> address y.y.y.y
crypto isakmp keepalive 10
crypto ipsec transform-set 3DES-SHA-HMAC esp-3des esp-sha-hmac
crypto ipsec profile Crypto-01
set transform-set 3DES-SHA-HMAC
interface Tunnel1
ip address 10.255.255.5 255.255.255.252
keepalive 5 3
tunnel source x.x.x.x
tunnel destination y.y.y.y
tunnel mode ipsec ipv4
tunnel protection ipsec profile Crypto-01
service-policy output p-map01
CLEC-C2811-VPNC#sh interfaces tunnel 1
Tunnel1 is up, line protocol is down
Hardware is Tunnel
Internet address is 10.255.255.5/30
MTU 1514 bytes, BW 9 Kbit, DLY 500000 usec,
     reliability 255/255, txload 1/255, rxload 1/255
Encapsulation TUNNEL, loopback not set
Keepalive set (5 sec), retries 3
Tunnel source x.x.x.x, destination y.y.y.y
Tunnel protocol/transport IPSEC/IP
Tunnel TTL 255
Fast tunneling enabled
Tunnel transmit bandwidth 8000 (kbps)
Tunnel receive bandwidth 8000 (kbps)
Tunnel protection via IPSec (profile "Crypto-01")
Last input never, output never, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 1
Queueing strategy: fifo
Output queue: 0/0 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
     172 packets input, 17949 bytes, 0 no buffer
     Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
     118 packets output, 10052 bytes, 0 underruns
     0 output errors, 0 collisions, 0 interface resets
     0 output buffer failures, 0 output buffers swapped out

Remove the keep alive config from the tunnel, I have found that keepalives only work on default GRE tunnel mode/encapsulation.
Sent from Cisco Technical Support iPad App

Safari Keep-Alive via Profile Manager

Greetings Community!
Does anybody know of a way to issue a keep-alive to Safari via profile manager so it always stays open and that if it somehow closes it will automatically re-open?

Worked it out!
I also host a couple of personal websites and these were configured to use the IP of the server; removed this and set it to use the "Any" option and profile manager started working as expected. Not done a full test of the entire thing to see if anything else is broken but this has me moving on from here!

TCP KEEP ALIVE

Hello we have a problem with TCP/IP keep settings.
We have an apllication that after a while (2 hours) doesnt keep its connection,And after that we are taking of timeouts and disconnection from this application.We saw some threads that there a registery TCP/KEEP ALIVE,we already change this registery but
it doesnt help still.Could it be any other solution?Or advice?

I want to configure it to a lower value so that the connection is not closed by routers/firewalls assuming the connection to be idle.For all TCP clients and servers?
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\KeepAliveTime 30000 30 seconds is an absurdly low value. Routers and firewalls will typically close connections after an hour, if at all. So setting it to 30 minutes should be adequate. Setting it as low as you have only exposes you to more network problems: if someone has a cable out for 30 seconds you will get disconnected, even if the cable was put back after 31 seconds and even if your application doesn't actually exchange data every 30 seconds. Don't do this.
Is there a standard way in which the keep alive time can be configured on all OS platforms? No.
If not, is this a standard way of changing keep alive time for java applications on windows?The registry keys might differ from version to version. It's a Windows question, not a Java question.
Is it necessary that the machine be restarted on changing keep alive time or is there a specific time by which the new keep alive time would be picked up during run time or on restarting the java application?Another Windows question.
But I would review your requirement. More likely you should be building application pings into the applications that actually need them.

GF3.0 - Enabling HTTP keep-alive?

In GF 2.0, there's a handy-dandy tab on the HTTP Listener configs for enabling and configuring HTTP keep-alives. In GF 3.0, there is not.
I've been combing various sites and blogs and docs and have been unable to find any information on enabling HTTP keep-alives. Some data I've found seems to suggest that raising the Max Connections and Timeout values for the listener to values greater than 1 implicitly enables keep-alives, but if I test the server with AB it shows zero keep-alive requests.
Any help that anyone could provide would be greatly appreciated.

[glassfish@appserver ~]$ asadmin get -m \*keep-alive.\*count
Enter admin user name> admin
Enter admin password for user "admin">
Command get executed successfully.
[glassfish@appserver ~]$ asadmin get "server\*keep-alive.\*"
Enter admin user name> admin
Enter admin password for user "admin">
com.sun.enterprise.admin.cli.CommandException: remote failure: Dotted name path server\*keep-alive.\* not found.
Command get failed.

Keep Alive burst configuration ATA 122

Similar Messages

Maybe you are looking for