ns4 A configuration management tool
Download

ns4 Ranking & Summary

ns4 Tags

management configuration node configuration management automated backup node configuration backup

ns4 Description

A configuration management tool ns4 is a configuration management software which allows the automated backup of node configurations. Commands are defined within a configuration file, and when they are executed, the output is sent to a series of FTP servers for archiving. As well as archiving configurations, it allows scripts to be run on nodes; this allows configurations to be applied en masse and allows conditional logic so different bits of scripts are run on different nodes. What's New in This Release: Within this release I have decided to add an optional ‘file’ argument to the ‘-d’ parameter which allows you to use this in preference to the transports defined within the configuration file. By using the “” tag we can use the following syntax to maintain the structure that would be used with transports: · $ ns4 -ad “//.txt” · The “-x” parameter has been added to ns4 which allows you to verify connectivity to nodes. This works exactly the same as using the “-d” paramter without any commands defined within the configuration. I decided to add this new parameter as you could be adding a new node to the configuration and you don’t want to run all the commands every time you are testing it. · The main feature which has been added to ns4 is a simple snmp poller. Although technically this feature belongs in it’s own program it was relatively trivial to add to ns4. The reason why it fits well is because ns4 provides the framework to define nodes so you have all the information you need within the configuration file. This will only work on nodes which don’t have a proxy defined as you need direct access from ns4. At the moment ns4 will poll the OIDs which are defined within the configuration file every 60 seconds. Within the node options we need to define two new attributes: “snmp_community” and “snmp_oids”. These should be defined as follows: container: node: · - {id: “R1″, address: “172.16.0.101″} options: · snmp_community: “PUBLIC” snmp_oids: · - {id: “Free Mem”, oid: “1.3.6.1.4.1.9.9.48.1.1.1.6.1″} · - {id: “CPU”, oid: “1.3.6.1.4.1.9.9.109.1.1.1.1.7.1″} Once the OIDs have been defined within the configuration file we can then run ns4 with the following command line: · $ ns4 -n R1 -p “.txt” · The logfile paramter after the “-p” parameter is optional and supports dynamic tags.

ns4 Related Software