Projects › Arista EOS Out-of-Band Management in a Management VRF
Arista EOS Out-of-Band Management in a Management VRF
An audit at Tessera Cloud found that LEAF-01, an Arista server leaf, has its Management1 port in the same routing table as production traffic, a guessable enable password and only a shared admin login. Fix all three: rename the switch to the standard, put Management1 in a management VRF on the OOB network (172.16.100.0/24, where the NOC jump host sits), set a proper enable password and create a named admin account.
Difficulty: intermediate · Time: about 40 minutes
Why it matters
Out-of-band management is only out-of-band if it has its own routing table. In the default VRF, the management subnet is a connected route that production traffic can be routed into, and a default route out of Management1 would attract data-plane traffic too. A management VRF keeps the two apart, which is why EOS and most data-centre designs use one.
Technologies
- Arista EOS
- Out-of-Band Management
- VRFs
- Device Hardening
- Credential Hardening
Related projects
- Edge Security Zone & DMZ Inspection with FortiGate
- Layer 2 Defense: DHCP Snooping, DAI, and IP Source Guard
- Zero-Trust 802.1X Port Authentication & Dynamic VLANs with Cisco ISE
- Enterprise Cyber Attack & Defense: Mitigating L2/L3 Exploits
- IPv6 First-Hop Security for a Campus Rollout: RA Guard and DHCPv6 Guard
- Enterprise Device Administration: Centralized TACACS+ with Cisco ISE
- Zero Trust Network Access (ZTNA): Micro-Segmentation via Zscaler ZPA
- Next-Gen Firewall Deep Packet Inspection: SSL/TLS & IPS with FortiGate