Re: FWSM Global Service Policy change tcp connection timeout

From: Peter Hauck (pahauck@gmail.com)
Date: Wed Jul 02 2008 - 04:56:42 ART


Patrick,

You forgot to mention turning them in a virtual context and then
reconfiguring the discombobulator.

reboot fixed it.

Pete

On 02/07/2008, at 11:28 AM, Patrick Galligan wrote:

> class-map blah
> match your flow
>
> policy-map global_policy
> class blah
> set connection timeout 0
>
> I've not tried this myself, just hit ? under the class configuration
> within the policy map to see what was available.
>
> Hope that helps....
>
> Networking Geek #21217
>
> On Wed, Jul 2, 2008 at 4:35 AM, Lee Reade <lee.reade@binternet.com>
> wrote:
>> Hi,
>>
>>
>>
>> I have an issue with an old database server that creates tcp
>> connections via
>> a FWSM, and expects these sessions to never idle out, since the
>> FWSM has a
>> default timeout of 60 mins for tcp we are having some issues with
>> connectivity. I want to config a class-map to match this specifc
>> flow and
>> set the tcp connection timeout to 0.
>>
>>
>>
>> Can anyone advise how to ensure that the other traffic will use the
>> FWSM
>> default settings? Would I just config the class-default and set the
>> connections in there? Or will they automatically pick them up?
>>
>>
>>
>> I will be applying this service-policy as global and not to a
>> specific
>> interface.
>>
>>
>>
>> I've checked on CCO but the config guide doesn't mention this, and
>> I just
>> need some clarification.
>>
>>
>>
>> Thanks very much,
>>
>>
>>
>> LR
>>
>>
>> _______________________________________________________________________
>> Subscription information may be found at:
>> http://www.groupstudy.com/list/CCIELab.html
>
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html



This archive was generated by hypermail 2.1.4 : Mon Aug 04 2008 - 06:11:53 ART