We are now ready to use vash, the command line interface to VACM, to connect to our Nexxus. By default Nexxus creates an administrative account with username blum and password frub. It is generally a good idea to change these defaults right away.
[zacs@denial]$ vash -c localhost -u blum -p frub NEXXUS_READY
To rename the administrative account, send the following ipc command. For the purpose of this example, the blum account will be renamed to zsprackett.
vash$ ipc localhost nexxus:admin_rename:blum:zsprackett NEXXUS:8:JOB_STARTED NEXXUS:8:JOB_COMPLETED
Changing the password is accomplished as follows. The default password will be changed to `p4ssw0rd`.
vash$ ipc localhost nexxus:admin_chg_password:frub:p4ssw0rd NEXXUS:10:JOB_STARTED NEXXUS:10:JOB_COMPLETED
Next create a group named webservers. All managed nodes must be members of a group.
vash$ ipc localhost nexxus:group_add:webservers NEXXUS:12:JOB_STARTED NEXXUS:12:JOB_COMPLETED
It is important to add the administrative user to the newly created group. VACM users can only manage nodes in groups to which they belong.
vash$ ipc localhost nexxus:group_add_admin:webservers:zsprackett NEXXUS:14:JOB_STARTED NEXXUS:14:JOB_COMPLETED
At this point it is safe to tell VACM about the nodes to be managed. In this example the managed node will be named www. Our example adds the newly created node to the group webservers. It is also worth mentioning that the name assigned to a managed node under VACM does not have to correspond to the nodes DNS hostname.
vash$ ipc localhost nexxus:node_add:www:webservers NEXXUS:16:JOB_STARTED NEXXUS:16:JOB_COMPLETED
Certain modules rely on global variables. The most important of these seems to be the IP_ADDRESS variable. The IP_ADDRESS variable can be set as follows.
vash$ ipc localhost nexxus:set_var:www:ip_address:192.168.1.1 NEXXUS:17:JOB_STARTED NEXXUS:17:JOB_COMPLETED