5. Properties and Templates
5.1. Configuration Properties
5.1.5. Network Configuration Properties
To view and edit network configuration properties, select Infrastructure, and then select Networks. The Networks page appears, listing networks by IP address.
Figure 5.6. Networks
You can view and change network configuration property values and inheritance selections. From the Display list of options, select Configuration Properties.
Properties and Templates
Table 5.3. Network Configuration Properties
Property Name Property Type Description
zAutoDiscover Boolean Specifies whether zendisc should perform auto-discovery on this network. (When performing network discovery, this property specifies whether the system should discover devices and subnet- works on the network.)
zDefaultNetworkTree lines A network subnet is automatically created for each modeled de- vice, based on that device's subnet mask setting. To create high- er-level subnets automatically from the discovery and model- ing processes, add the specific subnet mask breakpoints. For ex- ample: 8, 16. If you then model a device with, for example, an IP address of 192.168.0.1, and a subnet mask of 255.255.255.0 (corresponding to a /24 subnet), device discovery will create a 192.0.0.0/8 network containing 192.168.0.0/16, containing 192.168.0.0/24, containing your device.
zDrawMapLinks Boolean Calculating network links "on the fly" is resource-intensive. If you have a large number of devices that have been assigned lo- cations, then drawing those map links may take a long time. You can use this property to prevent the system from drawing links for specific networks (for example, a local network comprising many devices that you know does not span multiple locations).
zIcon string Use to specify device icons that appear on the device status page, Dashboard, and network map.
zPingFailThresh int Specifies the number of pings sent without being returned before zendisc removes the device.
zPreferSnmpNaming Boolean Specifies that when network discovery occurs, it uses the device name comes from SNMP rather than reverse DNS.
zSnmpStrictDiscovery Boolean Specifies that if SNMP does not exist on the device during net- work discovery, ignore the device.
5.2. Templates
The system stores performance configuration data in templates. Templates contain other objects that define where and how to obtain performance data, thresholds for that data, and data graphs.
You can define a template anywhere in the device class hierarchy, or on an individual device. Templates are divided among three types:
• Device • Component • Interface
5.2.1. Copying Templates
You can create a template by copying an existing template. To copy a template, use the copy/override action. 1. Navigate to the template you want to copy.
Properties and Templates
2. From the Action menu, select Copy / Override Template. The Copy / Override dialog appears.
3. Select the template to override, and then click Submit. The listed template indicates that it is now locally defined.
5.2.2. Renaming Templates
To rename an existing template:
1. Select Advanced, and then select Monitoring Templates.
2. Expand the organizer containing the template to be renamed, and then class containing the template. 3. From the Action menu, select View and Edit Details.
The Edit Template Details dialog appears. 4. Enter a new name in the Name field. 5. Click Submit.
5.2.3. Template Binding
The determination of which templates apply to what objects is called binding. Templates are bound in different ways, depending on the objects to which they are bound.
5.2.3.1. Device Templates
Device templates are applied to devices, one to each device. The system employs a single rule to bind device templates to devices: the value of the zDeviceTemplates property. For most device classes, this is "Device."
Common device templates are: • Device • MySQL • Apache • Active Directory • MSExchangeIS • MSSQLServer • IIS
For the Server/Linux/MySQL device class, the zDeviceTemplates property might contain, for example, "Device" and "MySQL." The system would collect CPU and memory information by using the Device template, and MySQL- specific metrics by using the MySQL template.
5.2.3.1.1. Binding Templates
Properties and Templates
1. From the devices list, select a device class or device. 2.
Select Bind Templates from (Action Menu). The Bind Templates dialog appears.
Figure 5.7. Bind Templates
3. Move templates between the Available and Selected lists using the arrows. 4. Click Save.
5.2.3.1.2. Resetting Bindings
Resetting template bindings removes all locally bound templates and uses the default template values. To reset bindings for a selected device or device class:
1.
Select Reset Bindings from (Action Menu). The Reset Template Bindings dialog appears. 2. Click Reset Bindings to confirm the action.
5.2.3.2. Component Templates
Component templates are named exactly according to the name of the underlying class that represents a component. For example, the FileSystem template is applied to file systems. Component templates can be applied multiple times to each device, depending on how many of the device's components match the template. Configuration properties do not control the application of component templates.
Note
Component templates should not be manually bound. Common component templates are:
• FileSystem, HardDisk, IPService, OSProcess, WinService • Fan, PowerSupply, TemperatureSensor
Properties and Templates
• LTMVirtualServer, VPNTunnel
5.2.3.3. Interface Templates
Interface templates are applied to network interfaces by using a special type of binding. Instead of using the name of the underlying class, the system looks for a template with the same name as the interface type. You can find this type in the details information for any network interface.
If Zenoss Core cannot locate a template that matches the interface type, then it uses the ethernetCsmacd template.
5.2.4. Examples
5.2.4.1. Example: Defining Templates in the Device Hierarchy
You add a new device at /Devices/Server/Linux named Example1Server. You have not edited the value of its zDe- viceTemplates property, so it inherits the value of "Device" from the root device class (/Devices). Zenoss Core looks to see if there is a template named Device defined on Example1Server itself. There is not, so it checks /Devices/Serv- er/Linux. There is a template named Device defined for that device class, so that template is used for Example1Server. (There also is a template named Device defined at the root level (/Devices), but the system does not use this one because the template at /Devices/Server/Linux overrides it.)