Network tools to manage TCP/IP and Fibre Channel networks

Abdul Wahab Junaid

3 years ago

Network Tools to Manage TCP/IP and Fibre Channel Networks

Introduction

Effective network management depends heavily on knowing the right tool for the job — whether that’s confirming basic reachability, capturing packets for deep analysis, or checking the health of a Fibre Channel fabric. This article catalogs the essential tools for managing TCP/IP and Fibre Channel networks, with practical usage examples for each.

TCP/IP Network Tools

1. ping — Basic Reachability Testing

ping -c 4 8.8.8.8
ping6 2001:4860:4860::8888

ping -c 4 8.8.8.8
ping6 2001:4860:4860::8888

Sends ICMP Echo Requests and measures round-trip time and packet loss. It’s the first tool to reach for in almost any connectivity issue.

2. traceroute / tracert — Path Discovery

traceroute 8.8.8.8       # Linux/macOS
tracert 8.8.8.8           # Windows

traceroute 8.8.8.8       # Linux/macOS
tracert 8.8.8.8           # Windows

Shows every router hop between source and destination by sending packets with incrementing TTL values and recording which hop generates the “TTL exceeded” response at each step.

3. mtr — Combined Ping + Traceroute

mtr 8.8.8.8
mtr -rw 8.8.8.8   # report mode, wide output — good for logging/sharing

mtr 8.8.8.8
mtr -rw 8.8.8.8   # report mode, wide output — good for logging/sharing

Continuously re-probes every hop, making it far better than a one-shot traceroute for spotting intermittent loss at a specific hop.

4. dig / nslookup — DNS Diagnostics

dig example.com
dig example.com MX
dig -x 8.8.8.8            # reverse lookup
dig example.com @1.1.1.1  # query a specific resolver

dig example.com
dig example.com MX
dig -x 8.8.8.8            # reverse lookup
dig example.com @1.1.1.1  # query a specific resolver

5. ss / netstat — Socket and Connection Inspection

ss -tulnp        # listening TCP/UDP sockets with process info
ss -s             # summary statistics
netstat -rn       # routing table (legacy)

ss -tulnp        # listening TCP/UDP sockets with process info
ss -s             # summary statistics
netstat -rn       # routing table (legacy)

6. tcpdump — Packet Capture

sudo tcpdump -i eth0 -w capture.pcap
sudo tcpdump -i eth0 host 10.0.0.5 and port 443
sudo tcpdump -i eth0 'tcp[tcpflags] & tcp-syn != 0'

sudo tcpdump -i eth0 -w capture.pcap
sudo tcpdump -i eth0 host 10.0.0.5 and port 443
sudo tcpdump -i eth0 'tcp[tcpflags] & tcp-syn != 0'

Captures raw packets for offline or live analysis — indispensable for anything beyond surface-level troubleshooting.

7. Wireshark — Graphical Packet Analysis

Wireshark opens .pcap files (including ones captured by tcpdump) and provides deep protocol dissection, filtering, and visualization. Common filters:

tcp.port == 443
ip.addr == 10.0.0.5
tcp.flags.syn == 1
dns

tcp.port == 443
ip.addr == 10.0.0.5
tcp.flags.syn == 1
dns

8. nmap — Port Scanning and Discovery

nmap 192.168.1.0/24            # discover live hosts on a subnet
nmap -sV -p 1-1000 10.0.0.5    # version detection on common ports
nmap -A 10.0.0.5                # aggressive scan: OS detection, scripts, traceroute

nmap 192.168.1.0/24            # discover live hosts on a subnet
nmap -sV -p 1-1000 10.0.0.5    # version detection on common ports
nmap -A 10.0.0.5                # aggressive scan: OS detection, scripts, traceroute

9. iperf3 — Throughput Testing

# On the server
iperf3 -s

# On the client
iperf3 -c 10.0.0.5 -t 30

# On the server
iperf3 -s

# On the client
iperf3 -c 10.0.0.5 -t 30

Measures actual achievable throughput between two hosts — essential for validating whether a link is really delivering its rated bandwidth.

10. arp / ip neigh — Address Resolution Table

ip neigh show
arp -a          # legacy

ip neigh show
arp -a          # legacy

11. netcat (nc) — Swiss-Army Knife for TCP/UDP

nc -zv 10.0.0.5 443       # test if a port is open
nc -l -p 9999               # listen on a port
echo "test" | nc -u 10.0.0.5 514   # send a UDP packet

nc -zv 10.0.0.5 443       # test if a port is open
nc -l -p 9999               # listen on a port
echo "test" | nc -u 10.0.0.5 514   # send a UDP packet

12. SNMP Tools — Device Monitoring

snmpwalk -v2c -c public 10.0.0.1
snmpget -v2c -c public 10.0.0.1 1.3.6.1.2.1.1.1.0

snmpwalk -v2c -c public 10.0.0.1
snmpget -v2c -c public 10.0.0.1 1.3.6.1.2.1.1.1.0

Used to query device statistics (interface counters, CPU, memory) from routers, switches, and other SNMP-enabled equipment.

TCP/IP Tools Comparison Table

Tool	Layer Focus	Best For
ping	Network	Basic reachability
traceroute/mtr	Network	Path and hop-by-hop loss
dig/nslookup	Application	DNS troubleshooting
ss/netstat	Transport	Local socket/connection state
tcpdump/Wireshark	All layers	Deep packet inspection
nmap	Transport/Application	Port scanning, service discovery
iperf3	Transport	Throughput/bandwidth testing
snmpwalk	Application	Device health monitoring

Fibre Channel Management Tools

1. Switch CLI Tools (Cisco MDS / Brocade)

# Cisco MDS
show interface fc1/1
show flogi database
show fcns database
show zoneset active

# Brocade
switchshow
nsshow
zoneshow

# Cisco MDS
show interface fc1/1
show flogi database
show fcns database
show zoneset active

# Brocade
switchshow
nsshow
zoneshow

flogi database / nsshow show which devices have logged into the fabric.
fcns database is the fabric-wide name server, mapping WWNs to FC IDs.

2. Host-Side Multipath Tools (Linux)

multipath -ll              # show multipath device status
systool -c fc_host -v      # show FC host adapter details
cat /sys/class/fc_host/host0/port_state

multipath -ll              # show multipath device status
systool -c fc_host -v      # show FC host adapter details
cat /sys/class/fc_host/host0/port_state

3. HBA Vendor Utilities

Most HBA vendors (Broadcom/Emulex, Marvell/QLogic) provide CLI or GUI utilities for firmware updates, WWN inspection, and diagnostics:

# QLogic example
qaucli -pr fc-hba -g

# QLogic example
qaucli -pr fc-hba -g

4. SAN Fabric Monitoring Platforms

Enterprise environments typically use dedicated monitoring platforms (e.g., Cisco DCNM, Broadcom SANnav) that aggregate fabric-wide health, port errors, and performance trending across many switches — far more practical than checking each switch individually at scale.

5. Fibre Channel Analyzers

For deep protocol-level troubleshooting, dedicated FC analyzers (hardware taps or software-based) capture and decode FC frames, similar in spirit to Wireshark for Ethernet, but purpose-built for FC’s frame structure and flow control mechanisms.

Fibre Channel Tools Comparison Table

Tool/Command	Purpose
`switchshow` / `show interface`	Port status, link state, SFP details
`zoneshow` / `show zoneset active`	Zoning configuration and status
`nsshow` / `show fcns database`	Name server — devices registered in the fabric
`multipath -ll`	Host-side path health and load balancing
Vendor HBA CLI	Adapter-level diagnostics and firmware
DCNM / SANnav	Fabric-wide monitoring and alerting

Python for Network Automation

import subprocess
import json

def get_interface_status(interfaces):
    results = {}
    for iface in interfaces:
        r = subprocess.run(["ip", "-j", "addr", "show", iface],
                            capture_output=True, text=True)
        try:
            data = json.loads(r.stdout)
            results[iface] = "UP" if data and "UP" in data[0].get("flags", []) else "DOWN"
        except (json.JSONDecodeError, IndexError):
            results[iface] = "UNKNOWN"
    return results

status = get_interface_status(["eth0", "eth1"])
print(status)

import subprocess
import json

def get_interface_status(interfaces):
    results = {}
    for iface in interfaces:
        r = subprocess.run(["ip", "-j", "addr", "show", iface],
                            capture_output=True, text=True)
        try:
            data = json.loads(r.stdout)
            results[iface] = "UP" if data and "UP" in data[0].get("flags", []) else "DOWN"
        except (json.JSONDecodeError, IndexError):
            results[iface] = "UNKNOWN"
    return results

status = get_interface_status(["eth0", "eth1"])
print(status)

Using ip -j (JSON output) makes it straightforward to build simple automation and monitoring scripts around native Linux networking commands without fragile text parsing.

Best Practices

Always capture a baseline (iperf3, mtr report) of a healthy network so you have something to compare against when things go wrong.
Use tcpdump to capture, then analyze offline with Wireshark — capturing directly in Wireshark on a busy production interface can itself introduce load.
Automate routine health checks (interface status, error counters) rather than checking manually every time.
Standardize on consistent zoning and naming conventions in Fibre Channel fabrics to make CLI output easier to interpret quickly under pressure.
Keep SNMP community strings and any monitoring credentials properly secured — treat them as sensitive credentials, not defaults.
Know your tools before an incident — the middle of an outage is not the time to be learning tcpdump filter syntax for the first time.

Conclusion

Whether you’re chasing down a flaky Ethernet link or a congested Fibre Channel fabric, having the right tool — and knowing exactly what it tells you — turns a stressful outage into a methodical diagnosis. Building fluency with this toolkit, from ping all the way to fabric-level CLI commands, is one of the highest-leverage skills a network professional can develop.