Forum Discussion

Tabish_Mirza_12's avatar
Tabish_Mirza_12
Icon for Nimbostratus rankNimbostratus
Oct 07, 2013

how to deploy F5 BIG-IP 4200 V HA Pair for Web Application

Hi, We have recently purchased pair of BIG-IP 4200V (LTM & ASM) for our https based web servers load balancing. Web servers are located in DMZ of firewall. Web serves wants to see original source IP of the clients. We would like to know what is the best way to deploy BIG-IP whether Inline-Routed Mode or One-Arm. If we have to deploy it in Inline-Routed Mode. Do we have to use two different IP subnet or same? one for external & one for internal.

 

21 Replies

  • By the way, here's some general notes around installations;

    Preparation & Design - Device

    •   Confirm support is in place
    •   Management NIC, TMM Interface and VLAN design and general numbering, tagging, trunking etc.
    •   TMOS Software selection
    •   Hostname
    •   Management service details (DNS, NTP etc.)
    •   Authentication methods, remote server details
    •   Configuration backup schedule and method
    •   Failover and mirroring methods and interfaces
    •   Security policies
    •   IP Addressing
    •   Routing requirements for management and TMM interfaces
    Services/Applications
    •   Other global settings
    •   NATting
    •   Service implementations;
    o   SSL Certificate requirements and parameters
    o   SSL Profile security requirements and parameters
    o   Compression requirements and parameters
    o   Caching requirements and parameters
    
  • Device Configuration

    •   Hypervisor stuff if VE – like what???
    •   Management network interface IP address and route via LCD or serial
    •   Licensing
    •   Provisioning
    •   Management IP, default account passwords, timezone, Hostname etc.
    •   Disk partitions, TMOS upgrades and hotfix installations
    •   Administrative Partitions
    •   Local user accounts, remote authentication and user roles
    •   local host file
    •   DNS, NTP, SNMP, SMTP, Logging, log rotation etc.
    •   Management tasks such as configuration backups and management routes, service failure actions and time zone
    •   Security (password policy, banners, timeouts, source address persistence)
    •   Physical Interfaces and Trunks
    •   VLANs, STP (not on the 2000s, 2200s, 4000s, or 4200v platforms) , LLDP
    •   Route Domains
    •   Self IPs, ARP and NDP
    •   LTM Routing
    •   Failover and Configsync etc.
    •   Global settings such as PMTUD, Auto Last Hop and L2 cache aging time
    
  • Services/Applications

    •   Nodes
    •   Health Monitors
    •   Pools
    •   S/NATs
    •   SSL Certificate installation
    •   Profiles;
    o   Persistence
    o   Protocol
    o   SSL
    o   HTTP
    o   HTTP Compression
    o   Web Acceleration
    •   iRules, Data Groups, iFiles
    •   Virtual Servers
    
  • We are managing the server through different interface. So you are suggesting to go for one-arm without using SNAT means change servers gateway to F5 floating IP & configured default route on F5 pointing DMZ interface IP. All will be in same subnet.

     

    Is it the best way to deploy it? Is it the recommended method by F5? We don't have any issue to change server IP's, mask & gateway. We are in the design phase. We don't want any issue or limitation after implementation.

     

    I know I am keep repeating the same question again & again but I wanna make sure that things go smooth so sorry for that

     

    Your kind help highly appropriate

     

    Many thanks indeed.

     

    Awaiting for your prompt response

     

  • That's exactly it although you are restricting yourself to using the F5s only with traffic flows that involve that DMZ.

     

    Don't forget that you can also load balance between the Web and Application servers.