F5 Certified BIG-IP Administrator jobs description

A F5 Certified BIG-IP Administrator manages preexisting BIG-IP installations and preliminary fault isolations. They must have the ability to make necessary configuration changes and modify BIG-IP objects. They are also responsible for application delivery networks (ADNs) and for conducting routine management and troubleshooting of F5 Traffic Management Operating System (TMOS) devices.

Job Description

The primary responsibility of a F5 Certified BIG-IP Administrator is to identify BIG-IP Traffic Processing Objects. They assist in managing load balance traffic and viewing statistics and logs. They further configure virtual servers and pools and monitor BIG-IP configuration states and files. Certified Administrators must have a proper understanding of traffic management shell hierarchical structures and their navigation.

Administrators are responsible for shutting down and restarting BIG-IP Systems. They are also responsible for loading and saving system configurations. They further must save and replicate configuration data and oversee its transition onto a BIG-IP System. F5 Certified BIG-IP Administrators must additionally map IP addresses with NATs and resolve routing issues with SNATs. They should have the ability to create a SNAT auto map within a virtual server and manage pools and their members as well as node statuses.

Administrators must monitor both timeout and interval settings. They should know how to use network maps and understand profile types and dependencies. Certified Administrators also must introduce source address affinity persistence and cookie persistence, and they must manage object states and handle SSL offloads and re-encryptions.

Certified Administrator manage logs, and they introduce high-speed logging as well. They are further responsible for High-Speed Logging Filters and HSL Configuration Objects. Administrators should have an understanding of how to use TCPDUMP on BIG-IP Systems. F5 Certified BIG IP Administrators further define user roles and administrative partitions. They must also recognize iRules components and trigger iRules with events.