“When Cisco announced the End-of-Life for the ACE module, thousands of enterprise datacenters panicked. Converting ACE TCL scripts to F5 tmsh was an art form.”

In late 2014 at Wipro, I led the migration of over 300 production load-balanced applications from legacy Cisco ACE 4710 hardware modules to F5 BIG-IP LTM (Local Traffic Manager) appliances.

The Architectural Shift

Cisco ACE used a rigid, probe-based load-balancing logic configured via CLI parameter maps. F5 BIG-IP introduced event-driven TCL scripting (iRules) and modular profile objects.

• Cisco ACE: Probe-based health checks, rigid stickiness tables, parameter-map syntax.
• F5 BIG-IP LTM: Full-proxy architecture, modular ClientSSL/ServerSSL profiles, custom iRules.

[!IMPORTANT] Cisco ACE was a packet-filtering load balancer. F5 BIG-IP is a Full Proxy—it terminates client TCP connections independently from backend server TCP connections.

Script Syntax Translation

Converting Cisco ACE parameter maps required translating syntax logic into F5 tmsh commands:

# # Cisco ACE Parameter Map (Legacy)
parameter-map type regex HTTP_HEADER_REWRITE
  match header Host header-value ".*\.olddomain\.com"
!
action-list type modify http ACT_REWRITE
  ssl header-rewrite

Translated to F5 iRule:

# # F5 BIG-IP iRule Equivalent
when HTTP_REQUEST {
    if { [HTTP::host] ends_with "olddomain.com" } {
        HTTP::redirect "https://newdomain.com[HTTP::uri]"
    }
}

The Verdict

Key Takeaway

Full-Proxy Architectures Require Deep TCP Inspection.

Moving from legacy hardware load balancers to F5 BIG-IP LTM requires understanding full-proxy TCP behavior. Always validate SSL profile ciphers and TCP idle timeouts before cutting over DNS VIPs.