Network Engineer’s Guide to Linux

Network Engineer’s Guide to Linux

You know networking cold. Here’s how Linux maps to what you already know.

The Mental Shift

Cisco World Linux World Key Difference

IOS CLI

Bash shell

No ? help, use man and --help

show running-config

Config files in /etc/

Text files, not a running state

copy run start

Changes are immediate (mostly)

Some services need restart

NVRAM

/etc/ directory

Persistent by default

Interfaces (Gi0/0)

Devices (eth0, ens33)

Predictable naming in RHEL 9

VLANs

Network namespaces

Different isolation model

ACLs

firewalld / nftables

Zone-based, not interface-based

SNMP

journalctl + Prometheus

Pull vs push monitoring

NTP

chronyd

Same protocol, different daemon

DHCP relay

dhcrelay

Similar concept

Command Translation

Cisco Linux

show ip interface brief

ip -4 -br addr show

show ip route

ip route show

show arp

ip neigh show

show interfaces

ip -s link show

ping 10.0.0.1

ping -c 4 10.0.0.1

traceroute 10.0.0.1

traceroute 10.0.0.1

show mac address-table

bridge fdb show

show tcp brief

ss -tn

show ntp status

chronyc tracking

debug ip packet

tcpdump -i eth0

Your Advantages

  1. Chapters 5, 8, 19 (SSH, Networking, Firewall) are mostly review

  2. Troubleshooting mindset translates directly — same OSI model, same methodology

  3. DNS/DHCP/NTP — you understand the protocols, just learn the Linux daemons

  4. Security — ACL thinking maps to firewalld zones