show running-config on an Arista EOS switch produces the same kind of everything-at-once dump as any other vendor's CLI: VLANs, port-channels, BGP peering, and every credential the switch holds sit in one paste. Before that goes into a TAC case or an AI chat asking about a flapping MLAG peer, it's worth knowing exactly what's in there.
What an Arista EOS Config Actually Contains
username admin secret— a type-5 (or stronger) hashed local user passwordsnmp-server communitystrings, sometimes scoped read-write- BGP
neighbor ... passwordvalues (MD5-based, reversible with the right tooling for older ciphers) tacacs-server keyandradius-server host ... keyshared secrets- MLAG
peer-addressandlocal-interfaceconfiguration, occasionally paired with a shared secret in the peering setup enable secretfor privileged EXEC access
Before and After
The same TACACS+ key or BGP neighbor password always maps to the same token throughout the sanitized output, so relationships between peers, VLANs, and port-channels stay readable — only the literal credential is replaced.
Steps
- Install ScrubForge from the Chrome Web Store (free)
- Run
show running-configon your Arista switch - Paste the output into ScrubForge
- Review the sanitized result — secrets, community strings, and neighbor passwords are tokenized, structure is untouched
- Copy and share, or continue in ScrubForge's built-in AI chat
Why Local Processing Matters
An MLAG shared secret or a TACACS+ key pasted into a support ticket or a shared chat log sits there indefinitely. ScrubForge sanitizes entirely inside the browser tab — nothing is uploaded before you decide to share it.