Networking Automation Scripts

# CHAPTER 15

Networking Automation Scripts #

1. Introduction #

2. Learning Objectives #

• Write an automated ICMP ping sweep script to verify host connectivity.

• Utilize the nc (Netcat) utility inside a script to verify open TCP ports.

• Extract and evaluate HTTP status codes (e.g., 200 OK) using curl.

• Architect a unified, multi-layer network diagnostic dashboard script.

• Understand how to suppress verbose network command output during automation.

3. Layer 3 Automation (The Ping Sweep) #

*Important:* In a script, you must use -c 1 to limit the ping to a single pulse, and you must use -W 1 to limit the timeout to 1 second. If a server is offline, you don't want the script pausing for 10 seconds waiting for a response!

#!/bin/bash

# Define the cluster nodes
NODES=("192.168.1.10" "192.168.1.11" "192.168.1.12")

echo "Initiating Layer 3 Ping Sweep..."

for IP in "${NODES[@]}"; do
    # Ping once (-c 1), Timeout in 1 sec (-W 1), suppress output
    ping -c 1 -W 1 "$IP" > /dev/null 2>&1
    
    if [ $? -eq 0 ]; then
        echo "[ONLINE] Node $IP is responding."
    else
        echo "[OFFLINE] Node $IP is DOWN!"
    fi
done

4. Layer 4 Automation (Port Checks) #

#!/bin/bash

TARGET="192.168.1.50"
PORT=3306

echo "Verifying Database Port..."

# -z (Scan mode), -v (Verbose, which we redirect), -w 2 (Timeout 2 secs)
nc -z -w 2 "$TARGET" "$PORT" > /dev/null 2>&1

if [ $? -eq 0 ]; then
    echo "SUCCESS: Port $PORT on $TARGET is open and listening."
else
    echo "CRITICAL: Port $PORT on $TARGET is closed or blocked by firewall!"
fi

5. Layer 7 Automation (HTTP API Checks) #

#!/bin/bash

URL="https://example.com/api/health"

# -s (Silent), -o /dev/null (Discard the actual HTML page data)
# -w "%{http_code}" (Write out ONLY the 3-digit HTTP response code)
STATUS=$(curl -s -o /dev/null -w "%{http_code}" "$URL")

if [ "$STATUS" == "200" ]; then
    echo "API is Healthy (HTTP 200)."
else
    echo "API Failure! Returned HTTP Code: $STATUS"
fi

*(This 10-line script replaces thousands of dollars of commercial website monitoring software).*

6. Diagrams/Visual Suggestions #

• Top layer (Widest): Ping (Layer 3). "Is the machine turned on?"

• Middle layer: Netcat (Layer 4). "Is the firewall allowing traffic to the web port?"

• Bottom layer (Narrowest): Curl (Layer 7). "Is the web application actually returning healthy data?"

7. Best Practices #

• Implement Strict Timeouts: Network commands are historically dangerous in scripts because they "hang." If a script runs curl http://offline-server.com without a timeout flag, the script will literally freeze in the terminal for 2 minutes waiting for the network request to drop. Always enforce timeouts (curl --max-time 5, ping -W 1) to ensure scripts fail rapidly and continue execution.

8. Common Mistakes #

• Grepping for Ping output: Beginners often try to run ping and pipe the output into grep to look for the word "bytes from" to see if it succeeded. This is incredibly inefficient and error-prone depending on the operating system's exact ping string format. Always rely on the $? exit code (0 for success, 1 for failure) which is universally standardized across all Linux distributions.

9. Mini Project: Build a Full-Stack Uptime Monitor #

1. 1. nano uptime_monitor.sh

1. 2. Write the code:

#!/bin/bash

TARGET_IP="1.1.1.1" # Example target (Cloudflare DNS)
TARGET_PORT=443     # HTTPS port
TARGET_URL="https://1.1.1.1"

echo "=== INITIATING FULL-STACK DIAGNOSTIC ==="

# 1. Layer 3: ICMP Check
ping -c 1 -W 1 "$TARGET_IP" > /dev/null 2>&1
if [ $? -ne 0 ]; then
    echo "[FATAL] Server is totally offline. Aborting further tests."
    exit 1
fi
echo "[OK] Server is reachable (Ping successful)."

# 2. Layer 4: TCP Port Check
nc -z -w 2 "$TARGET_IP" "$TARGET_PORT" > /dev/null 2>&1
if [ $? -ne 0 ]; then
    echo "[FATAL] Firewall is blocking Port $TARGET_PORT. Aborting."
    exit 1
fi
echo "[OK] Port $TARGET_PORT is open and listening."

# 3. Layer 7: HTTP Application Check
HTTP_STATUS=$(curl -s -o /dev/null -w "%{http_code}" "$TARGET_URL")
if [ "$HTTP_STATUS" != "200" ] && [ "$HTTP_STATUS" != "301" ]; then
    echo "[ERROR] Web Application failure. HTTP Code: $HTTP_STATUS"
    exit 1
fi
echo "[OK] Application is responding with HTTP $HTTP_STATUS."

echo "=== DIAGNOSTIC COMPLETE: SERVER IS 100% HEALTHY ==="

10. Practice Exercises #

1. 1. Explain the operational difference between monitoring a web server via nc (Netcat) versus curl. Which tool would successfully detect if a web application developer accidentally broke the website's code resulting in a 500 Internal Server Error?

1. 2. Why is it an architectural requirement to include a timeout flag (e.g., -W 1) when writing automated network diagnostic scripts?

11. MCQs with Answers #

12. Interview Questions #

• Q: A developer complains that their automated deployment script freezes for exactly two minutes before reporting an error when attempting to download an asset via curl from a broken URL. Explain the mechanical network networking behavior causing this freeze, and provide the exact flag required to enforce a "Fail Fast" methodology in the script.

• Q: You are tasked with writing a Bash script to monitor a critical REST API. Walk me through the logical progression of troubleshooting steps your script should execute, starting from Layer 3 (Network) and ending at Layer 7 (Application).

• Q: Explain why a systems engineer should never parse the literal text output of the ping command using grep to determine success within a Bash script, and describe the mathematically superior alternative.

13. FAQs #

14. Summary #

15. Next Chapter Recommendation #