Wednesday, 24 July 2019

Big IP administration:--



  1. Big IP is default deny system, configure listener to permit certain traffic
    1. port lock down exception, port allowed by default
      1. UDP 53 (DNS)  161 (SNMP) 520 (RIP)
      2. TCP 22 (SSH) 53 (DNS) 161 (SNMP traps) 443 (SSL Web)  4303 (iQuery language)

 

    1. Traffic policy  type
      1. traffic group local : static ip (non fialover ) 
      2. traffic group-1 (default) : regular rule for floating IP (failover ip)
  1. Full proxy architecture
  2. It acts like end-point and originator of protocol.
    1. Connection between client and big ip is independent of server and big ip
    2. It has its own tcp connection behavior such as buffering, retransmit and tcp option.
    3. It optimizes every connection uniquely irrespective of destination or originator
    4. Actively participate in application it delivers
    5. It act like centralized device offloading time consuming and resource intensive function from application server e.g.  ssl encryption, compression, encryption and caching.
    6. System can be configured to inspect, accept, reject or modify packet based on known attack signature.

 

The big-IP system

            |

            |

           V

 Two function area

1: TMOS : application deliver system

  • Real time os
  • High performance hardware
  • Ssl compression

 

2: Linux : administration  ( GUI / TMSH* / CLI )    * TMOS Shell

 

Set of independent module run on TMOS

LTM, GTM, AAM, AFM, APM, ASM, CGNAT, PEM

No comments:

Post a Comment

Why do many Palo Alto engineers open a TAC case immediately… without checking anything first?

A production issue happens. Application team says “network issue.” Users say “firewall problem.” And within minutes someone says: “Let’s ope...