Skip to main content

CCIE-LAB-QOS

Control Plane Policy

1) control-plane host

a) service-policy input
 
!
class-map match-all UDP-FLOOD
 match access-group 101
!
policy-map UDP-FLOOD-PM
 class UDP-FLOOD
  police rate 16000 bps
   conform-action drop
!
control-plane
 service-policy input UDP-FLOOD-PM
!

b) service-policy type queue-threshold input

only for some protocols:
 
R2(config-cmap)#match protocol ?
  bgp     Border Gateway Protocol
  dns     Domain Name Server lookup
  ftp     File Transfer Protocol
  http    World Wide Web traffic
  igmp    Internet Group Management Protocol
  snmp    Simple Network Management Protocol
  ssh     Secure Shell Protocol
  syslog  Syslog Server
  telnet  Telnet
  tftp    Trivial File Transfer Protocol

R2(config-cmap)#
class type queue-threshold HTTP-CM
match protocol http
!
policy-map type queue-threshold HTTP-PM
  class HTTP-CM
    queue-limit 10

 c) service-policy type port-filter input
 
class-map type port-filter TASK1-1-closed-ports
 match closed-ports
!
policy-map type port-filter TASK1-1-closed-ports-PM
 class TASK1-1-closed-ports
   drop
!
control-plane host
 service-policy type port-filter input TASK1-1-closed-ports-PM
!
R2#sh control-plane host open-ports
Active internet connections (servers and established)
Prot               Local Address             Foreign Address                  Service    State
 tcp                        *:23                         *:0                   Telnet   LISTEN
 tcp                       *:179                         *:0                      BGP   LISTEN

R2#

2) control-plane cef-exception

For non-IP traffic:
 
policy-map TASK1-2-block-non-IP
 class class-default
  police rate 100 pps
!
control-plane cef-exception
 service-policy input TASK1-2-block-non-IP
!

3) control-plane transit

For packets/traffic which transit the device:
 
class-map match-all TASK1-4-frag
 match access-group 103
!
policy-map TASK1-4-frag-PM
 class TASK1-4-frag
  police rate 1000000 pps
!
control-plane transit
 service-policy input TASK1-4-frag-PM

Comments

Post a Comment

Popular posts from this blog

What should you know about HA 'override enabled' setting on Fortigate?

High availability is mandatory in most of today's network designs. Only very small companies or branches can run their business without redundancy. When you have Fortigate firewall in your network you have many options to increase network availability. You can use Fortigate Clustering Protocol ( FGCP ) or Virtual Router Redundancy Protocol ( VRRP ). FGCP has two modes: 'override' disabled (default) and 'override' enabled . I'm not going to explain how to set up HA as you can find many resources on Fortinet websites: https://cookbook.fortinet.com/high-availability-two-fortigates-56/ https://cookbook.fortinet.com/high-availability-with-fgcp-56/ Let's recap what is the main difference between them. The default HA setting is 'override' disabled and this is an order of selection an active unit: 1) number of monitored interfaces - when both units have the same number of working (up) interfaces check next parameter 2) HA uptime - an ...
8 comments
Read more

FortiGate and GRE tunnel

Recently I worked on one project where a client requested to re-route web traffic to the GRE tunnel to perform traffic inspection. I would like to share with you what is required if you configure it on FortiGate. We need a new GRE interface and policy base routing (PBR) to change the route for specific source IPs. Of course you need firewall policies to permit the traffic. Let's start with GRE interface. Unfortunately you can't configure it using the GUI, only CLI is the option: config system gre-tunnel edit "gre1" set interface "port1" set local-gw 55.55.55.55 set remote-gw 44.44.44.44 next end When the end peer is Cisco router, you need to set the IP for the GRE interface: config system interface edit gre1 set ip 192.168.10.10 255.255.255.255 set remote-ip192.168.10.20 end In next step we need to fix routing. We need the alternate path via GRE but to keep the route in the active routing table you need to set the same AD (adminis...
Post a Comment
Read more

Inpection of asymmetric sessions on FortiGate

There is one feature available on FortiGate, and I think you should know it, as it modifies a bit what we know about stateful firewalls. In past every packet was treated individually and you had to create policies in both directions. With stateful firewalls we can track connections, and by checking couple of attributes, we can treat them as part of the same session. For example when you initiate connection from a host1 to host2, the returning connection from host2 to host1 will be treated as part of the same connection (session). They have to have the same source/destination and destination/source IPs, port numbers and interfaces.There is an exception from this rule and FortiGate in some specific cases can accept connections on port which was not used in the initial connection. Let me explain how it works on the below example:      The host1 has a default gateway on R1 (10.0.1.2), but you may notice that it is not the optimal path to host2 subnet. When we analyze ...
1 comment
Read more