The connection expired because the request remained in the request queue before the application picked it up. The connection expired because the response send rate was slower than the default of 150 bytes/sec. The connection expired while waiting for the HTTP Server API to drain the entity body on a Keep-Alive connection. I only use a pstn live and my polycom 501. The connection expired while waiting for the request entity body to arrive. 19:20:09.015 StunClient: nTestTout CM506004: STUN request to STUN server 64.69.76.23 has timed out used Transport: 192.168.0.102:5060 I dont use a voip provider. The connection expired while waiting for the HTTP Server API to parse the header. The connection expired while staying idle. The following table lists the default connection timeout limits Timer The URL group settings override the server session configurations, when set.The Server Session timeouts override the HTTP Server API-wide settings, when set.The HTTP Server API-wide defaults apply to all the HTTP Server API applications on the computer.The order of timeout enforcement is as follows: When the timers are not configured for a URL group or server session, the HTTP Server API default configurations apply. When the timers are configured HTTP Server API-wide, they apply to all the HTTP Server API applications on the computer and the settings persist when the service is restarted.įor more information about configuring timers, see Configuring the Application Specific Timeouts. The IdleConnection and HeaderWait timers can also be configured HTTP Server API-wide. The HTTP timeouts property is used to set all timeouts on an application-specific basis. Now, go through the capture and try to ascertain what device may be at fault, this will also tell you the mac/user involved and you can go check in access tracker what happened at the CPPM side.The HTTP Server API enables applications to set the server connection timeout limits on a server session or a URL group.
When there is a timeout what does the access tracker say, is it rejecting/ignoring an auth attempt.Īs you note it's happening all of the time, perhaps you can setup a packet capture for udp 1812/1813 and let it run for a while until you know there is at least one timeout according to the controller CLI. I presume that your CPPM is in a healthy state and not under and duress (what does the CPPM monitoring say?). Server Acct Rq Raw Rq PAP Rq CHAP Rq MSCHAP Rq MSCHAPv2 Rq Mismatch Rsp Bad Auth Acc Rej Acct Rsp Chal Ukn Rsp Tmout AvgRspTm Tot Rq Tot Rsp Rd Err Outstanding Auths Outstanding Requests Acc-RTTS Rq Acc-RTTS Rsp ExpAuthTm Uptime SEQĭoes_not_exist 0 0 1 0 0 0 0 0 0 0 0 0 0 4 0 1 0 0 0 0 0 0 5022 0:0:1 255/254Īs to why your server is timing out - that could be any number of things. You can see 4 messages 5 seconds apart, corresponds to 3 rexmt at 5 seconds (default of a new radius server) show aaa authentication-server radius does_not_existĬheck stats (7008-core) #show aaa authentication-server radius statistics Resulting log (7008-core) #show log errorlog 20 Now test it (7008-core) #aaa test-server pap does_not_exist no_such_user aaaaaaa (7008-core) ^ (RADIUS Server "does_not_exist") #key blah (7008-core) (config) #aaa authentication-server radius does_not_exist Timeout means the server did not respond, e.g.
0 kommentar(er)
