0% found this document useful (0 votes)
35 views2 pages

F5 CLI Troubleshooting Guide

Uploaded by

himansupanda625
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
35 views2 pages

F5 CLI Troubleshooting Guide

Uploaded by

himansupanda625
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

F5 Device Troubleshooting CLI Commands

Network

Commands Explanation
#tmsh list sys management-ip Shows system management IP
address
Root# netstat –nr/-r Route table of F5 with default
gateway
# tmsh list net self-allow Port lockdown - the default
supported protocols and services
#nslookup [Link] check system is able to resolve
# dig [Link] names
([Link])#show interface <interface_key> Display the current status of a
# tmsh show net interface specific interface
([Link])#show interface Display the current status of all
interfaces.
config # tmsh list net interface media-active vendor SFP device serial number
serial
config # tmsh list net interface all-properties All interface details
(tmos)# list net interface media-capabilities Display the valid media types for a
specific interface. 100TX-
HD,1000T-FD
Config# ifconfig eth0 Interface eth0 details
Config# ping --help Ping command options
(tmos)# ping -I [Link] [Link] PING [Link]
([Link]) from
[Link] : 56(84) bytes of
data
Config# telnet [Link] 80 Command to server for port 80
Get / http/1.1 service confirmation
Config# curl [Link] Html content from server
TCPDUMP
tcpdump -ni /<partition_name>/<vlan_name> when you run tcpdump on a
VLAN that resides in a non-
default partition, you must specify
the path to the VLAN object in
the tcpdump syntax
tmsh show /sys hardware |grep–ipva To determine whether your
platform contains a PVA chip
mergecap -a file1 file2 file3 file4 -w combined_file After all tcpdump processes are
completed, combine them into a
single file
tcpdump -ni<interface_number> tcpdump on a hardware switch
interface, it is rate-limited to 200
packets per second
tcpdump -ni 0.0 captures traffic from all VLANs in
all route domains when you invoke
it from the default route domain
tcpdump –i /common/internal –c 30 30 packets capture on internal
VLAN
tcpdump –i internal / 1.2 / eth0 by default it captures starting/firs
t96 bytes of a packet
tcpdump –i internal –s0 not restricting packet size for
capture, will capture full packet
tcpdump –i internal –nn -nn means no name resolution in
capture output
tcpdump –i 0.0 –w /var/tmp/[Link] capture all interface traffic and
write it to a file a given location
tcpdump –i 0.0 –s0 arp –nn will capture ARP protocol packets
only
tcpdump –i 0.0:p host [Link] –nn :p peer side when SNAT is used
we want to see server side
communication of the same host
with NAT address as well
tcpdump –i 0.0:p host [Link] –nn and not tcp exclude tcp port 443 packet
port 443 communication, and net
[Link]/24 IP in the network
[Link]/24

You might also like