Clear your switches properly! Failed “system archival” transfers are kept on the device even after running a zeroize.

Just a very quick one here as I recently came across some unknown configs in our archival backup server after configuring some refurbished switches for “system archival” and committing.

I found config backup files had been transferred which belonged to the previous owner!

The switches were zeroized prior to provisioning them on our network.

When using the system archival feature in Juniper and the transfer fails, the config is left in /var/transfer/config, files in here remain even after a “request system zeroize”. Once the switch is configured for system archival again then all files in that directory are pushed to the configured destination.

So, before selling or discarding any Juniper equipment, remember to check /var/transfer/config if System Archival has ever been used within your configuration.

Monitoring Virtual Chassis VCP Ports via SNMP with Juniper QFX (and EX!)

For some strange reason, the vcp-snmp-statistics statement is hidden on the Juniper QFX platform – (if anybody knows why, please do tell!). This means  your individual virtual chassis VCP port statistics aren’t exposed in it’s entirety, which is pretty awful as monitoring VCP port errors are vital in virtual-chassis setups.

{master:0}[edit]
ben@qfx0# set virtual-chassis vcp-sn
                                                  ^
syntax error.
ben@qfx0# set virtual-chassis vcp-sn
                                                  ^
syntax error.ben@qfx0# set virtual-chassis vcp-sn?
No valid completions
{master:0}[edit]
ben@qfx0# set virtual-chassis vcp-snmp-statistics

{master:0}[edit]
ben@qfx0#

After committing changes, you should see the following in the logs, and likewise see more ports listed in your monitoring software of choice i.e. LibreNMS, Solarwinds, Zabbix etc.

Dec 27 10:59:12  qfx0 vccpd[1797]: Member 0, interface vcp-255/0/53 came up
Dec 27 10:59:12  qfx0 vccpd[1797]: Member 0, interface vcp-255/0/52 came up