12-06-2010 01:16 AM - edited 03-01-2019 02:22 PM
Hi All
I went through the support files and found such kind of log messages during peak hours as below,
2010-07-11 11:55:47 | INFO | CPU #000 | Started filtering packets of type 'TCP Non-SYN' received on interface # 0. Reason: Started filtering due to attack detection
2010-07-11 12:00:35 | INFO | CPU #000 | Started filtering packets of type 'TCP No-SYN + RST' received on interface # 0. Reason: Started filtering due to attack detection
2010-07-11 13:07:25 | INFO | CPU #000 | Stopped filtering packets of type 'TCP No-SYN + RST' received on interface # 0. Reason: Stopped filtering for an administrative pause
Basically those logs mean that SCE detect attacks and then in order to protect itself, it put those attack traffic in filter, one hour later, SCE remove the flows from filter and check again, if attack persist, SCE put attack traffic in filter again.
Could we decrease the time for filtering traffic ? like 10 minutes ?
Solved! Go to Solution.
12-06-2010 06:20 AM
configure
interface LineCard 0
sanity-checks attack-filter times filtering-cyclemax-attack-time
To verify:
sh interface LineCard 0 attack-filter current-attacks
Regards
Shelley.
12-08-2010 02:09 PM
Example
SCE#>show interface LineCard 0 sanity-checks attack-filter times
Filtering cycle: 3600 seconds.
Max attack time: 86400 seconds.
When such attack is detected and the system is in some kind of shortage it will start filtering that specific type for the "Filtering cycle" value seconds after this time it will stop for certain amount of time in order to test whether the attack is still on and whether we are still in shortage, if both conditions are still stand it will start filter again for another "Filtering cycle" seconds period of time
Assuming the attack and the shortage condition will still stand cycle after cycle after cycle we will stop filtering upon "Max Attack Time" seconds even if the attack and the shortage are still there.
Regards
Shelley
Please mark complete and rate if question has been answered.
12-06-2010 06:20 AM
configure
interface LineCard 0
sanity-checks attack-filter times filtering-cyclemax-attack-time
To verify:
sh interface LineCard 0 attack-filter current-attacks
Regards
Shelley.
12-06-2010 07:28 PM
Thanks a lot !
Could you explain what is max-attack-time ?
12-08-2010 02:09 PM
Example
SCE#>show interface LineCard 0 sanity-checks attack-filter times
Filtering cycle: 3600 seconds.
Max attack time: 86400 seconds.
When such attack is detected and the system is in some kind of shortage it will start filtering that specific type for the "Filtering cycle" value seconds after this time it will stop for certain amount of time in order to test whether the attack is still on and whether we are still in shortage, if both conditions are still stand it will start filter again for another "Filtering cycle" seconds period of time
Assuming the attack and the shortage condition will still stand cycle after cycle after cycle we will stop filtering upon "Max Attack Time" seconds even if the attack and the shortage are still there.
Regards
Shelley
Please mark complete and rate if question has been answered.
12-08-2010 05:56 PM
Thanks !
Will the system start filtering all traffic or traffic on specific CPU when only one CPU is in shortage ?
What it will do if the system is in some kind of shortage and no attack is detected ?
Is the shortage include cpu , memory and the others ? the threshold is 80% or 90% or others ?
Regards
Jack
12-08-2010 06:13 PM
The SCE will monitor all resources momory or CPU and any resource when taxed will trigger sanity check attack filter.
Shelley.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide