Skip navigation
Currently Being Moderated

4.3 Managing Devices and Device Attributes

VERSION 13  Click to view document history
Created on: Oct 27, 2010 1:32 PM by Zenoss API - Last Modified:  Oct 27, 2010 1:50 PM by Zenoss API

 3. Managing Devices and Device Attributes

Read the information and procedures in this section to learn about specific device management tasks, including:

 3.1. Clearing Heartbeat Events

If you have configured a device to send a recurring event that you have mapped to a heartbeat class, you can clear stale heartbeat events.

To clear the heartbeat events associated with a device:

  1. Navigate to the device in the device list.

  2. At the bottom of the device overview page, select Clear Heartbeats from (Action Menu).

    The Clear Heartbeats dialog appears.

  3. Click Submit to confirm the clear action.

    The system moves the heartbeat events for the device to event history and displays a confirmation message of the action.

 3.2. Pushing Configuration Changes to  Zenoss

When you make a configuration change, it is automatically propagated to all the remote collectors. If you think that your change has not been propagated correctly, then you can manually force a configuration "push" to the collectors.

To push configuration changes:

  1. Navigate to the device in the device list.

  2. At the bottom of the device overview page, select Push Changes from (Action Menu).

    The Push Changes dialog appears.

  3. Click Yes.

    The system pushes changes to the collectors and displays a confirmation message of the action.

 3.3. Locking Device Configuration

You can lock a device's configuration to prevent changes from being overwritten when remodeling the device. Two levels of locking are available. You can lock the configuration from deletion and updates, or solely from deletion.

Note

Device locking prevents changes and deletion due to remodeling. It does not prevent manual changes and deletion.

To edit lock selections for a device configuration:

  1. Navigate to the device in the device list.

  2. At the bottom of the device overview page, select Lock from (Action Menu).

    The Lock dialog appears.

     

    Figure 4.10. Edit (Configuration) Lock Dialog

    Edit (Configuration) Lock Dialog

  3. To send events when actions are blocked by a lock action, select the "Send an event..." option.

  4. Select the type of lock you want to implement or remove.

    The lock or unlock action is implemented on the device, and the system displays a confirmation message of the action.

 3.4. Renaming a Device

Because the system uses the manage IP to monitor a device, the device name may be different than its fully qualified domain name (FQDN). The device name must always be unique.

To rename a device:

  1. Navigate to the device in the device list.

  2. At the bottom of the device overview page, select Rename Device from (Action Menu).

    The Rename Device dialog appears.

  3. Enter the new name for the device, and then click Submit.

    The system renames the device and displays a confirmation message of the action.

 3.5. Remodeling a Device

Remodeling forces the system to re-collect all configuration information associated with a device. Normally, the system models devices every 720 minutes; however, if you want to remodel a device immediately, follow these steps:

  1. Navigate to the device in the device list.

  2. At the bottom of the device overview page, select Model Device from (Action Menu).

    The system remodels the device. A dialog appears that shows progress of the action.

 3.6. Resetting the Device Manage IP Address

You might want to reset the manage IP address if the IP address of a device has changed and you want to maintain the historical data at the original IP address. To reset the manage IP address of a device:

  1. Navigate to the device in the device list.

  2. At the bottom of the device overview page, select Reset/Change IP Address from (Action Menu).

    The Reset IP dialog appears.

     

    Figure 4.11. Reset IP Dialog

    Reset IP Dialog

  3. Enter the new IP address for the device, or leave the field blank to allow the IP address to be set by DNS.

  4. Click Save.

    The IP address for the device is reset.

 3.7. Resetting the Device Community

If the system is unable to monitor a device because its SNMP community has changed, you can re-discover the device community by using the list of community strings defined in the zSnmpCommunity configuration property.

  1. Navigate to the device in the device list.

  2. At the bottom of the device overview page, select Reset Community from (Action Menu).

    The community for the device is reset.

 3.8. Deleting a Device

To delete a device from the system:

  1. Navigate to the device in the device list.

  2. At the bottom of the device overview page, select Delete Device from (Action Menu).

    The Delete Device dialog appears.

     

    Figure 4.12. Delete Device

    Delete Device

  3. Optionally change the selections to delete current events or performance data for the device. By default, events and performance data are removed.

  4. Click Submit.

    The system removes the devices and associated data (if selected), and displays a confirmation message of the action.

 3.9. Dumping and Loading Devices Using XML

 Zenoss allows you to export a list of your devices to an XML file to import into another  Zenoss instance. From the command line, use the command:

zendevicedump -o mydevicelist.xml

This command writes the names of your devices (including their device classes, groups, systems) to a file named mydevicelist.xml.

To load these devices into another instance (or reload them into the same instance), while in the  Zenoss instance where you want the devices to be discovered, run the command:

zendeviceload -i mydevicelist.xml

The systems attempts to discover each of the devices in the XML file.

Comments (0)