One useful feature of Drag-n-Vu™ that is often overlooked is the system configuration file. It’s true, a text-based configuration file is nothing unique or special, but the advantages they afford are many; they are an easy way to backup and restore system configuration, to view and edit system settings offline, and to transfer configuration to other units to ensure identical operation. The configuration files for Drag-n-Vu™ grant all these advantages and more.
Upon clicking the Download Configuration button in the GUI interface the user is presented with a browser pop-up containing the configuration in one continuous string. At first glance it appears a perplexing error code of arcane syntax and terminology, however the careful observer will note it is in fact a JSON formatted document, and once pasted into an appropriate text editor the JSON objects and arrays will be revealed.
The JSON structure, among its many features, allows easy viewing of large files in neatly organised sections, so you can easily see just the parts that you are interested in.
The JSON structure also allows partial configuration files to be uploaded. For example, if you wanted to synchronise the SNMP or TACACS configuration across all of your packet broker units, without changing the maps and filters you could easily do so. Simply download the configuration file from a correctly configured unit, edit it to contain only the chassis object and the relevant child objects then upload it in the usual way. The format is identical across all Drag-n-Vu™ models so this particular example could work across your entire suite of packet brokers.
The other great advantage of JSON is that it can be easily generated by machine, and coupled with secure HTTPS upload it forms an API by which it is possible to automate the configuration of a Drag-n-Vu™ unit. The possibilities are huge; with the right setup your packet brokers can become a dynamic part of a real time threat management system, or a key part of an automated test bed. Delving into the details of the API is out of scope here, but if you are interested in knowing more about it please contact us through the usual channels.