#3.5. Modeling Using SSH/COMMAND
Modeling also can be done by running commands on the remote device and interpreting the results. This provides an easier, more scalable, and more flexible way to gather information that may not be available through any other means.
Each built-in Zenoss modeling command plugin is differentiated by the platform on which it runs. To determine the platform for the device you want to model, run the uname command in a shell on the device.
To model a device using command plugins, first add the device to Zenoss by using the protocol "none," and then choose the plugins you want to apply:
Go to the Add Device page.
Set discover to a value of None.
After adding the device, navigate to the device and view its zProperties tab.
If necessary, set zCommandUsername and zCommandPassword to the user name and password of the device (or set up authentication by using RSA/DSA keys.)
Note
If using RSA keys for a device or device class, change the value of the zKeyPath zProperty to:
~/.ssh/id_rsaClick Edit next to zCollectorPlugins.
Click Add Fields for a complete list of command plugins.
Make sure zenoss.cmd.uname is positioned first on the left side.
Click the X next to plugins you wish to remove, and then drag remaining plugins to the left.
Remodel the device.
#3.5.1. Using Device Class to Monitor Devices Using SSH
The /Server/Cmd device class is an example configuration for modeling and monitoring devices using SSH. The zCollectorPlugins have been modified (see the section titled "Modeling Using SSH/Command"), and the device, file system, and Ethernet interface templates used to gather data over SSH have been created. You can use this device class as a reference for your own configuration; or, if you have a device that needs to be modeled or monitored via SSH/Command, you can place it in this device class to use the pre-configured templates and zProperties. You also must set the zCommandUsername and zCommandPassword zProperties to the appropriate SSH login information for each device.
