100% found this document useful (1 vote)
659 views113 pages

F5 Troubleshoot Docuemtn

The document provides guidance on troubleshooting why a virtual server may not be working as expected in F5 BIG-IP. It outlines steps like checking the virtual server's state, configuration such as listening port and IP address, associated profiles, and pool configuration. Network tools like connection table, packet captures, and connectivity tests can help identify where issues may occur in the processing flow.

Uploaded by

Farkhan Minhas
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
Download as pdf or txt
100% found this document useful (1 vote)
659 views113 pages

F5 Troubleshoot Docuemtn

The document provides guidance on troubleshooting why a virtual server may not be working as expected in F5 BIG-IP. It outlines steps like checking the virtual server's state, configuration such as listening port and IP address, associated profiles, and pool configuration. Network tools like connection table, packet captures, and connectivity tests can help identify where issues may occur in the processing flow.

Uploaded by

Farkhan Minhas
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
Download as pdf or txt
Download as pdf or txt
You are on page 1/ 113

Eric Mitchell

e.Mitchell@f5.com
Channel SE, Southeast, Mid-Atlantic and Federal US
401
301B 302 303 304
301A

201
3200
101
• Based on 11.4
• Multiple Choice
• Not Adaptive
• 80 questions in 90 minutes
• No command line engines
• View whole exhibit before you close them
• Manage Your Time
http://www.f5.com/pdf/certification/exams/Certification_Study_Guide_101.pdf
https://www.f5.com/pdf/certification/exams/Certification_Study_Guide_201_v2.pdf

https://devcentral.f5.com

https://ihealth.f5.com

https://www.linkedin.com/groups/85832
https://www.linkedin.com/groups/6711359/profile
https://www.linkedin.com/groups/6709915/profile
Objective 1.01
Given a connectivity-troubleshooting situation, consider the packet and
virtual server processing order

• Explain how a packet is processed once it arrives


at device (connection table, packet filters, etc.)

1. Existing connection in connection table


Objective 1.01
Given a connectivity-troubleshooting situation, consider the packet and
virtual server processing order

• Explain how a packet is processed once it arrives


at device (connection table, packet filters, etc.)

1. Existing connection in connection table


2. AFM/Packet filter rule
3. Virtual server
4. SNAT
5. NAT
6. Self-IP
7. Drop
Objective 1.01
Given a connectivity-troubleshooting situation, consider the packet and
virtual server processing order Order Destination Source Service port
1 <host address> <host address> <port>
• Explain how a virtual server processes a 2 <host address> <host address> *
request (most specific to least specific)? 3 <host address> <network address> <port>
4 <host address> <network address> *
5 <host address> * <port>
6 <host address> * *
Order Destination Service port
7 <network address> <host address> <port>
1 <host address> <port> 8 <network address> <host address> *
2 <host address> * 9 <network address> <network address> <port>
3 <network address> <port> 10 <network address> <network address> *
4 <network address> * 11 <network address> * <port>
5 * <port> 12 <network address> * *
6 * * 13 * <host address> <port>
14 * <host address> *
15 * <network address> <port>
16 * <network address> *
17 * * <port>
18 * * *
Objective 1.01
Given a connectivity-troubleshooting situation, consider the packet and
virtual server processing order
• Given a specific connectivity issue, isolate where the problem might be
according to the processing order
1. Specific IP address port with IP source of 10.30.1.0/24
10.0.33.199:80 Connect to: | Source IP
2. Specific IP address and specific port with IP source of 0.0.0.0/0
10.0.33.199:80
10.1.33.199:80 | 10.30.1.120
3. Specific IP address and all ports with IP source of 10.30.1.0/24
10.0.33.199:*
4. Specific IP address and all ports with IP source of 0.0.0.0/0 10.0.33.199:80 | 10.30.2.120
10.0.33.199:*
5. Network IP address and specific port with IP source of 0.0.0.0/0
10.0.33.0:443 netmask 255.255.255.0 10.0.33.199:443 | 17.64.223.120
6. Network IP address and all ports with IP source of 0.0.0.0/0
10.0.33.0:* netmask 255.255.255.0
10.0.33.196:443 | 10.30.1.120
7. All networks and specific port with IP source of 10.128.20.0/24
0.0.0.0:80 netmask 0.0.0.0
8. All networks and all ports with IP source of 0.0.0.0/0 74.125.21.106:80 | 10.128.20.100
0.0.0.0:* netmask 0.0.0.0
Objective 1.02
Identify the reason a virtual server is not working as expected

• Determine the state of a virtual server (offline, enabled, etc.)?


Objective 1.02
Identify the reason a virtual server is not working as expected

• Determine the state of a virtual server (offline, enabled, etc.)?


Objective 1.02
Identify the reason a virtual server is not working as expected

• Determine the state of a virtual server (offline, enabled, etc.)?


Objective 1.02
Identify the reason a virtual server is not working as expected

• Determine if a virtual server is configured for the proper listening port


• Determine if a virtual server is configured with the proper IP address
configuration
Objective 1.02
Identify the reason a virtual server is not working as expected

• Determine if a virtual server is configured for the proper listening port


• Determine if a virtual server is configured with the proper IP address
configuration
Identify the reason a virtual server is not working as expected
• Determine if the virtual server is configured with the
appropriate profiles
Identify the reason a virtual server is not working as expected
• Determine if the virtual server is configured with the
appropriate profiles
Identify the reason a virtual server is not working as expected

• Determine if the pool configuration has an effect on virtual server state?


• Determine which tools to use in order to diagnose the issue?

• Virtual Server stats


• Pool/Pool member stats
• Logs
• Connection table
• Routing table
• Connectivity from LTM to pool member- ping/telnet/curl
• Packet captures
Identify the reason a virtual server is not working as expected
Identify the reason a virtual server is not working as expected
Identify the reason a virtual server is not working as expected

root@(bigip245)(tmos)# show sys conn ?


Properties:
"{" Optional delimiter
age Specifies the age, in seconds, of a connection
cs-client-addr Specifies the clientside remote address of the active connections
cs-client-port Specifies the clientside remote port of the active connections
cs-server-addr Specifies the clientside local address of the active connections
cs-server-port Specifies the clientside local port of the active connections
protocol Specifies the protocol used for specified connections (for example:
tcp, udp)
ss-client-addr Specifies the serverside local address of the active connections
ss-client-port Specifies the serverside local port of the active connections
ss-server-addr Specifies the serverside remote address of the active connections
ss-server-port Specifies the serverside remote port of the active connections
type Specifies the connnection type used for specified connections (for
example: any, mirror, self)
Identify the reason a virtual server is not working as expected

root@(bigip245)(cfg-sync Standalone)(Active)(/Common)(tmos)# show sys connection protocol tcp

Sys::Connections
10.128.10.1:55146 10.128.10.90:80 any6.any any6.any tcp 1 (tmm: 0) none
10.128.10.1:55450 10.128.10.90:80 10.128.20.245:55450 10.128.20.12:80 tcp 0 (tmm: 0) none
10.128.10.1:55476 10.128.10.90:80 10.128.20.245:55476 10.128.20.12:80 tcp 0 (tmm: 0) none
10.128.10.1:55458 10.128.10.90:80 10.128.20.245:55458 10.128.20.14:80 tcp 0 (tmm: 0) none
10.128.10.1:55126 10.128.10.90:80 any6.any any6.any tcp 2 (tmm: 0) none
10.128.10.1:55440 10.128.10.90:80 10.128.20.245:55440 10.128.20.14:80 tcp 0 (tmm: 0) none
10.128.10.1:55433 10.128.10.90:80 10.128.20.245:55433 10.128.20.12:80 tcp 0 (tmm: 1) none
10.128.10.1:55459 10.128.10.90:80 10.128.20.245:55459 10.128.20.14:80 tcp 0 (tmm: 1) none
10.128.10.1:55127 10.128.10.90:80 any6.any any6.any tcp 2 (tmm: 1) none
10.128.10.1:55441 10.128.10.90:80 10.128.20.245:55441 10.128.20.14:80 tcp 0 (tmm: 1) none
10.128.10.1:55449 10.128.10.90:80 10.128.20.245:55449 10.128.20.14:80 tcp 0 (tmm: 1) none
10.128.10.1:55117 10.128.10.90:80 any6.any any6.any tcp 1 (tmm: 1) none
10.128.10.1:55431 10.128.10.90:80 10.128.20.245:55431 10.128.20.11:80 tcp 0 (tmm: 1) none
10.128.10.1:55099 10.128.10.90:80 any6.any any6.any tcp 1 (tmm: 1) none
Identify the reason a virtual server is not working as expected
root@(bigip245)(cfg-sync Standalone)(Active)(/Common)(tmos)# show sys connection detail
10.128.10.1:56562 - 10.128.10.90:80 - 10.128.20.245:56562 - 10.128.20.12:80
---------------------------------------------------------------------------
TMM 0
Type any
Acceleration none
Protocol tcp
Idle Time 0
Idle Timeout 300
Unit ID 1
Lasthop /Common/client_vlan 00:50:56:c0:00:02
Virtual Path 10.128.10.90:80
Conn Id 0

ClientSide ServerSide
Client Addr 10.128.10.1:56562 10.128.20.245:56562
Server Addr 10.128.10.90:80 10.128.20.12:80
Bits In 1.9K 704
Bits Out 704 1.6K
Packets In 3 2
Packets Out 2 3
Identify the reason a virtual server is not working as expected

Curl http://www.mysitename.com
http://curl.haxx.se/ Curl http://10.128.20.11
[root@bigip249] config # curl -i 10.128.20.11
HTTP/1.1 200 OK
Date: Wed, 06 Aug 2014 20:05:13 GMT
Server: Apache/2.2.22 (Ubuntu)
X-Powered-By: PHP/5.4.9-4ubuntu2.2
Vary: Accept-Encoding
Content-Length: 3819
Connection: close
Content-Type: text/html

<html>
<head>
<TITLE>Using virtual server 10.128.20.11 and pool member 10.128.20.11 (Node
#1)</TITLE>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii" />
<script language="javascript">
…………………
</script>
Identify the reason a virtual server is not working as expected
tcpdump
• tcpdump -w - writes output to a file
• tcpdump -i - to listen on a specific interface or vlan
• tcpdump -n – don’t do DNS lookup, -nn - don’t do DNS lookup or port lookup.
• tcpdump -s0 - capture whole packet
• Tcpdump –X – output in ASCII/Hex

Best Practice
• Listen on VLAN vs interface
• Filter down as much as possible
• Write to file if device is busy or lots of data to capture

• More on TCPDUMP in Objective 3.01


Identify the reason a virtual server is not working as expected
• Explain the difference between the virtual servers
status definitions

Unavailable Disabled The pool member(s) connection limit has been reached

Unavailable Enabled The pool member(s) connection limit has been reached
Unknown Enabled The children pool member(s) either don't have service checking enabled, or service
check results are not available yet
Unknown Disabled The children pool member(s) either don't have service checking enabled, or service
check results are not available yet
Offline Disabled The children pool member(s) are down
Available Enabled The virtual server is available

Offline Enabled The children pool member(s) are down

Available Disabled The virtual server is available


Identify the reason a pool member has been marked down by health monitors

• Discuss the effects of health monitors on the status of pool


members/nodes
Identify the reason a pool member has been marked down by health monitors

• Discuss the effects of health monitors on the status of pool


members/nodes
Identify the reason a pool member has been marked down by health monitors

• Determine the state and availability of the pool member/node in


question
show ltm pool p80_pool members {all} Connection Queue Pool Pool and members
Number of connections queued now 0 0
--------------------------------------------------------------------- Number of connections serviced 0 0
Ltm::Pool: p80_pool Queue head entry age (ms) 0 0
--------------------------------------------------------------------- Maximum queue entry age ever (ms) 0 0
Status Maximum queue entry age recently (ms) 0 0
Availability : available Average queue entry age (ms) 0 0
State : enabled
Reason : The pool is available --------------------------------------------------------------
Monitor : custom_http_monitor and | Ltm::Pool Member: 10.128.20.11:80
/Common/custom_tcp_monitor --------------------------------------------------------------
Minimum Active Members : 0 | Status
Current Active Members : 3 | Availability : available
Total Requests : 0 | State : enabled
Current Sessions : 0 | Reason : Pool member is available
| Monitor : custom_http_monitor and
Traffic ServerSide /Common/custom_tcp_monitor (pool monitor)
Bits In 0 | Monitor Status : up
Bits Out 0 | Session Status : enabled
Packets In 0 | Pool Name : p80_pool
Identify the reason a pool member has been marked down by health monitors

• Verify the pool member/node Ratio configuration?


Identify the reason a pool member has been marked down by health monitors

• Verify the pool member/node Ratio configuration?


• Verify the pool member/node connection configuration and count
Objective 1.04
Identify a pool member not in the active priority group
• What is a priority group

Server Pools
Running WWW1 and WWW2
Activation < 4
PG PG PG PG PG PG PG PG PG PG
100 100 100 100 100 90 80 70 25 1

A A A A A A A
web1_pool Servers web2_pool Servers
Objective 1.04
Identify a pool member not in the active priority group
Identify a pool member not in the active priority group
• Explain the concept of “persistence”?
Identify a pool member not in the active priority group

• Explain the concept of “persistence”?


• Verify the type of persistence profile assigned to the virtual server in question
• Validate the expected persistence behavior?
• Differentiate between fallback and primary persistence?
Identify a pool member not in the active priority group

• Use the appropriate tool to troubleshoot persistence


Objective 1.05
Identify traffic diverted due to persistence record
Objective 1.06
Identify the current configured state of the pool member

• Identify the current configured state of the pool member


Objective 1.07
Identify a persistence issue

• What is the behavior?


• Is persistence already configured?
• Does it need to be?
• What type will solve the application issue more effectively?
Perform an End User Diagnostic per F5 documentation and collect the output

• Reboot an F5 platform into the EUD

1. Attach a USB CDROM drive containing the bootable system CD. As the system boots up, the
EUD starts.

2. Attach a USB mass storage device drive with the EUD boot image loaded. As the system boots
up, the EUD starts.

3. While the system is booting, select the End User Diagnostics option from the boot menu.

To determine EUD Version


eud_info
Perform an End User Diagnostic per F5 documentation and collect the output

• Reboot an F5 platform into the EUD


The EUD menu options for most F5 Networks systems
When you start the EUD, the following menu displays:

1 System Report
2 Sensor Report
3 SFP/XFP Report
4 LED Test
5
|
V
18 Run all Tests (Non User Intervention, Uses Normal Ram Test)
19 * Run all Tests (User Intervention Required, Uses Quick Ram Test)
20 * Display Test Report Log
21 * Quit EUD and Reboot the System
Select a Menu item # -
Perform an End User Diagnostic per F5 documentation and collect the output

• Download output from the unit an EUD was run on


• Interpret the output from an EUD and determine if the test passed or failed
• Text file named eud.log in the /shared/log/ directory on the host file system.

• Completed test with 0 errors.


Objective 2.02
Interpret the LCD Warning Messages

• Locate the LCD on an F5 Platform


Objective 2.02
Interpret the LCD Warning Messages

• Locate the LCD on an F5 Platform


• Correlate the LCD message to message in the corresponding log file
• Identify which tasks the buttons on the LCD perform
Configure the management port using the LCD:
1. On the LCD, press the X button
LCD Warning: Critical: 9d Blocking Dos Attack 2. Arrow to System and press the  button
3. Arrow to Management and press the 
Local Traffic Log: sweeper_update: aggressive button
mode activated. 372313/438016 pages 4. Set the Mgmt IP, Mgmt Mask, and Mgmt
Gateway options
5. When finished, arrow to Commit and press
the  button
https://support.f5.com/kb/en-us/products/big-ip_ltm/manuals/product/platform-b5000/2.html?sr=54998935
Identify a possible hardware issue within the log files

• Indicate which logs would contain debugging information

• LTM - /var/log/ltm local0


• EM - /var/log/em local1
• GTM - /var/log/gtm local2
• ASM - /var/log/asm local3
• iControl - /var/log/ltm local4
• Packet Filter - /var/log/pktfilter local5
• HTTPD Errors - /var/log/httpd/httpd_errors local6
• Boot Process - /var/log/boot.log local7
Beginning in BIG-IP 11.4.0, you can also use the platform_check command to collect the SMART test data
from the drive. The disk portion of the command output indicates a Pass or Fail status for the drive and logs
detailed information to the /var/log/platform_check file
Identify a possible hardware issue within the log files

• Indicate which logs would contain debugging information


• Given a log file, determine the nature of a hardware issue
• Given a possible issue, determine which log file entries to review
• System events - messages are based on Linux events, and are not specific to the BIG-IP
system.

• Packet filter events – messages that result from the implementation of packet filters and
packet-filter rules.

• Local traffic events - messages pertain specifically to the local traffic management
system.

• Audit events - are those that the BIG-IP system logs as a result of changes to the BIG-IP
system configuration. Logging audit events is optional.
Force an active unit to standby under the appropriate circumstances

A S
Understand the relationship between interfaces, trunks, VLANs and their
status/statistics
Cisco vs F5

Port Channel Trunking

Trunking VLAN Tagging


Objective 2.05
Understand the relationship between interfaces, trunks, VLANs and their
status/statistics
Recognize when a packet capture is needed within the context of a
performance issue

• Tcpdump command
reference (partial)

&& || ! Alternate notations


Recognize when a packet capture is needed within the context of a
performance issue

• BIG-IP is a full proxy. Two tcpdumps (one on each side of the proxy) are often needed.
• Can by done be open two SSH sessions, or running the dumps in background (&)
• When a tcpdump is required, always make it as specific a possible
• Limit it to the appropriate interfaces/VLANs and hosts/ports
system# tcpdump –i external –eXs 0 host 10.10.10.10 and port 80

system# tcpdump –i (1.1, f5_trunk1, external, 0.0) –eXs 0 –w /var/tmp/dump.cap &


system# tcpdump –i (1.1, f5_trunk1, internal, 0.0) –eXs 0 –w /var/tmp/dump2.cap &
system# fg
ctl+c
system# fg
ctl+c

SOL4714: Performing a packet trace and providing the results to F5 Technical Support
Perform a packet capture within the context of a performance issue
• Tcpdump command reference (partial)
Perform a packet capture within the context of a performance issue
• Tcpdump command reference (partial)

&& || ! Alternate notations


Perform a packet capture within the context of a performance issue

• Determine an appropriate location to take the capture


• Determine the appropriate time to take capture
• Determine an appropriate tool to use
• Ensure the packet capture tool has the capacity to capture (driver/tap)
• Narrow the scope/context of information being gathered
• Given a scenario, determine whether a packet capture is appropriate
Objective 3.02
Use BIG-IP tools in order to identify potential performance issues

• Differentiate between performance issue types (i.e. Latency, Congestion,


broken content)

Latency describes the time delay experienced while a data packet moves from one point to another,
usually caused by physical distance and high round-trip times.

Latency can also be introduced by compute-intensive processing such as SSL handshaking, bulk
encryption/decryption, and TCP session management.

Network congestion occurs a node or network is processing so much data that its level of service
deteriorates.

Broken content is information that can not be accessed on the server due to many different issues such
as path changes, application changes, etc..
Objective 3.02
Use BIG-IP tools in order to identify potential performance issues

• Differentiate between performance issue types (i.e. Latency,


Congestion, broken content)
• Establish the frequency of a given issue (random, continuous, isolated,
intermittent, repetitive intervals)
Objective 3.02
Use BIG-IP tools in order to identify potential
performance issues
• Explain how to get performance statistics
in addition to the those shown in the
dashboard (Overview - Performance)
• You can review System performance on:
• Memory Used
• System CPU Usage
• Active Connections
• Total New Connections
• Throughput(bits)
• Throughput(packets)
• TMM Client-side Throughput
• TMM Server-side Throughput
• HTTP Requests
• RAM Cache Utilization
• SSL Transactions
• And more ……….
Objective 3.02
Use BIG-IP tools in order to identify potential performance issues
• Explain how to get performance statistics in addition to the those shown
in the dashboard (Overview - Performance)
• You can use tmsh:
• show /sys performance all-stats
Objective 3.02
Use BIG-IP tools in order to identify potential performance issues
• Explain how to get performance statistics in addition to the those shown
in the dashboard (Overview - Performance)
• From the Linux prompt:
• top
• bigtop
Verify remote connectivity to the box in order to determine the cause of a
management connectivity issue
• Isolate potential causes of basic network connectivity issues, given
scenarios related to: client configuration, client network access, device
network access, network topologies
• Apply connectivity troubleshooting tools (i.e. ping, traceroute, http/https
availability, remote shell access, network based console access) in the
appropriate situation
Verify remote connectivity to the box in order to determine the cause of a
management connectivity issue
• You can check the management port settings through the GUI
Check and interpret port lockdown settings and packet filters in order to
determine the cause of a management connectivity issue
• Given a scenario, review port lockdown settings on the Self-IP to
determine the cause of the issue
• Describe appropriate use cases for the use of port lockdown
Check and interpret port lockdown settings and packet filters in order to
determine the cause of a management connectivity issue

Allow Default ports


ospf:any
tcp:domain (53)
tcp:f5-iquery (4353)
tcp:https (443)
tcp:snmp (161)
tcp:ssh (22)
udp:520
udp:cap (1026 - for network failover)
udp:domain (53)
udp:f5-iquery (4353)
udp:snmp (161)

Mirroring and network failover use TCP port 1028. 1028 is not included
in the “default” list but is secretly allow with the BIG-IP failover partner
Check and interpret port lockdown settings and packet filters in order to
determine the cause of a management connectivity issue
• Describe appropriate use cases for the use of port lockdown
Objective 4.02
Check and interpret port lockdown settings and packet filters in order to
determine the cause of a management connectivity issue
• Determine whether a filter is enabled
• Interpret a packet filter rule list in a given situation
Objective 4.02
Check and interpret port lockdown settings and packet filters in order to
determine the cause of a management connectivity issue
• Determine whether a filter is enabled
• Interpret a packet filter rule list in a given situation
Objective 4.02
Check and interpret port lockdown settings and packet filters in order to
determine the cause of a management connectivity issue
• Determine whether a filter is enabled
• Interpret a packet filter rule list in a given situation
Given the use of a remote authentication server, verify proper DNS and NTP
settings in order to diagnose a connectivity issue
• Given a suspected DNS issue, use appropriate tools
to verify proper settings
Given the use of a remote authentication server, verify proper DNS and NTP
settings in order to diagnose a connectivity issue
• Given a suspected DNS issue, use appropriate tools
to verify proper settings
• Given a suspected DNS issue, use appropriate tools
to verify DNS response
nslookup example:
nslookup www.google.com
Server: 8.8.8.8
Address: 8.8.8.8#53
Non-authoritative answer:
Name: www.google.com
Address: 216.58.192.68

Dig Example:
; <<>> DiG 9.9.5 <<>> www.google.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 33323
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
Identify the appropriate supporting components and severity levels for an F5 support
ticket

• Identify the necessary components for all support cases (Qkview uploaded to iHealth/ or
attached to case, serial number of device, problem description, other supporting data)
• Identify severity levels and the associated response times

SEVERITY 1 - 1-hour response

SEVERITY 2 - 1-hour response

SEVERITY 3 - 4-business hour response

SEVERITY 4 - 24-hour response


Given an issue, determine the appropriate severity according to F5 guidelines

Support Response
Case Severity Condition Description
Time
All network traffic has ceased, causing a
Severity 1 Site Down 1 Hour
critical impact to your business.
Primary unit has failed resulting; Site is at
Severity 2 Site at Risk 1 Hour
risk of going down.
Performance Network traffic is extremely slow; significant
Impaired impact to your business.
Severity 3 --------- 4 Business Hours
Performance Network traffic is partially functional; some
Degraded applications to be un-reachable.

Questions regarding configurations "how


General to". Troubleshooting non-critical issue.
Severity 4 Next Business Day
Assistance Request for functionality that is not part the
current product feature set.
Field Data Required Opening a Support Case
Name The technical contact for this case
Contact Cell (Mobile) phone or Desk phone
F5 Serial # Required to obtain assistance
F5 Product Platform – i.e., 2000, 4000, 5250, Viprion, VE, etc
F5 Version Version (and any hot fixes already applied)

Business Impact The criticality of this issue on your business

Provide as complete a problem statement as possible:


• What has happened?
• Are there error messages? What are they?
Description • When did the issue happen, where did it happen?
• What changes have occurred in the configuration?
• What changes have occurred in the network?
• Is the issue happening on other F5 appliances?
Instructions to
If you are able to replicate, please provide step-by-step instructions
replicate
Is it possible to access this unit directly?
Remote Access
Is it possible to access this unit via a WebEX session?
Information
https://ihealth.f5.com
Provide quantitative and relevant information appropriate for a given issue

• Distinguish between qualitative/quantitative statements in order to assemble an accurate


problem description
• Distinguish between relevant/irrelevant information in order to assemble an accurate problem
description

Quantitative observations are observations that can be precisely measured. (i.e. There is
taking an additional 20 seconds per connection over the connection times this morning.)

Qualitative observations have more to do with characteristics of what is being observed.


(i.e. It seems to be taking longer to connect than it did this morning.)
Review the network map in order to determine the status of objects
• Explain the status icons of objects on the map
• Explain what virtual servers, pools, nodes and pool members are
Use the dashboard to gauge the current running status of the system
• Interpret each of the statistic types displayed by the dashboard
• Given a situation, predict the appropriate dashboard statistics
Review log files and identify possible events

• Given log file snippets,


describe an event sequence
• Given log file snippets, identify
critical events
Use iApps Analytics to gauge the current running status of application services

• Explain the purpose of iApps Analytics


• Describe how to capture application statistics
Use iApps Analytics to gauge the current running status of application services
• Describe how to capture application statistics
Use iApps Analytics to gauge the current running status
of application services
• Explain the purpose of iApps Analytics
• Describe how to capture application statistics
• Given a current running status, recognize significant statistics
Response Code Example
Latency per URL

Latency per Pool Member


Create and restore a UCS archive under the appropriate circumstances

• Discuss scenarios in which restoring a UCS archive is appropriate


• Discuss the tasks involved in successfully restoring a UCS archive
Create and restore a UCS archive under the appropriate circumstances

• Discuss scenarios in which restoring a UCS archive is appropriate


• Discuss the tasks involved in successfully restoring a UCS archive

tmsh load sys ucs [ucs file name e.g. /var/local/ucs/filename.ucs ] no-license
Create and restore a UCS archive under the appropriate circumstances

• Discuss scenarios in which restoring a UCS archive is appropriate


• Discuss the tasks involved in successfully restoring a UCS archive
• Given a scenario, discuss when it is appropriate to create a UCS archive
Objective 7.02
Identify which high-level tasks can be automated using BIG-IQ
Objective 7.02
Identify which high-level tasks can be automated using BIG-IQ
Objective 7.02
Identify which high-level tasks can be automated using BIG-IQ
Objective 7.03
Manage software images
Objective 7.03
Manage software images
Objective 7.03
Manage software images
Given an HA pair, describe the appropriate strategy for deploying a new software image

• Given an HA pair, describe the appropriate strategy for deploying a new software image
• Describe the potential impact of booting a device into another volume
• Discuss common issues related to the migration of a device to a new software version

#
# Licensing Information
#
Licensed date : 20160617
License start : 20160616
License end : 20160802
Service check date : 20160522
#
# Platform Information
#
Registration Key : NHQRP-YWHGO-WFQJK-YAZTM-FHJYBFE
Licensed version : 11.5.3
Given an HA pair, describe the appropriate strategy for deploying a new software image

• Given an HA pair, describe the appropriate strategy for deploying a new software image
• Describe the potential impact of booting a device into another volume
• Discuss common issues related to the migration of a device to a new software version
Unit A Active Unit B Standby

1.1 11.1.0 11.1.0 1.1


Active Volume Active Volume
1.2 11.2.0
11.1.0 11.1.0
11.2.0 1.2

1.3 1.3
Objective 7.05
Understand the processes of licensing, license reactivation, and license modification (add-ons)
• Understand the processes of licensing, license reactivation, and license modification (add-ons)
Objective 7.05
Objective 7.05
Objective 7.06
Identify which modules are licensed and/or provisioned

• Identify which modules are licensed and/or provisioned


Objective 7.07
Explain how to create a user
• Explain how to create a user
Objective 7.08
Explain how to modify user properties

• Explain how to modify user properties


Modify and manage virtual servers

• Given a proposed virtual server configuration change, outline the scope of the change and for
which connections those changes will affect (active connections, new connections, persisted
sessions)
• Given a description of an application, identify the correct virtual server configured for it
(HTTP/HTTPS, TCP/UDP, VLANs enabled, route-domain)
• Given a situation where a virtual server configuration change did not appear to immediately take
effect, determine why
Modify and manage pools

• Distinguish between disabling a member and


forcing it down
• Determine use cases for disabling a member
• Determine use cases for forcing down a
member
• Given a situation where a pool member has
been disabled but still appears to be receiving
traffic, determine the cause
• Articulate the characteristics of a pool member
that has been disabled or forced offline (Such
as for new connections, persisted connections,
etc.)

You might also like