Release Notes for Zenoss Ser-
vice Dynamics Version 4.1.1
4
• invalidationworkers -- Specifies the number of invalidation workers that should process configuration
changes. The default value is 1. May need to be raised if your database comprises more than 5000 devices,
or if your configuration experiences a high rate of change (such as frequent addition or removal of templates,
or frequent configuration property changes).
To determine if you need to increase the number of invalidation workers, run the following command:
$ sudo rabbitmqctl list_queues -p /zenoss
Look at the number of messages in the "invalidations" queues. If these are greater than 0 for any length of
time, then consider adding invalidation workers.
• invalidationchunksize -- Specifies the number of changes that will be sent to the workers at one time. The
default value is 100. This value likely does not need to be changed.
• invalidationlimit -- Specifies the number of changes each worker will process before it shuts down and is
replaced by a new worker. The default value is 5000. This value likely does not need to be changed.
• identifier -- Specifies the name by which the hub will be known. This allows workers to communicate with
the hub by using specific queues. The default value is HubName:HubPort. This value does not need to be
changed.
Note
This feature requires ZenPacks.zenoss.EnterpriseCollector-1.1.4.
1.1.5. Audit Logging
Enhancements to the audit log feature, which maintains logged information in a format optimized for searching
and reporting. Along with various defect fixes, these include:
• Extended audit capabilities, including auditing of logouts and VMware
• Command that can be run by users and shell scripts to audit actions:
zensendaudit 'Running script zenfixcatalog to fully reindex the catalog'
• Python scripts and zendmd can do this also:
from Products.ZenMessaging.audit import auditComment
auditComment("Manually fixed the catalog in zendmd")
1.1.6. Nexus7K ZenPack
Enhancements to the Nexus7K ZenPack, including:
• Modeling where only the default VDC is enabled
• Modeling using NX-OS firmware 5.2(1)
• Modeling and monitoring of loopback interfaces
• Corrections to modeling of MTU size of network interfaces and interface ranges for VLANs.
1.1.7. zenping
In Versions 4.0.x and 4.1, zenping introduced event suppression, which occurs when a resource is detected as
down, and another resource (along its traceroute, or gateway) is also down. This allows users to focus efforts
on the primary cause of a ping down event.
In Version 4.1.1, zenping:
• Relies on a subprocess (nmap) to handle batch pinging devices. Time-critical tasks are no longer handled
in-process.
• Uses nmap to provide traceroute information. nmap implements an efficient "reverse traceroute" method
that allows zenping to capture the network topology quickly and frequently.
• Will traceroute every --traceroute-interval pingCycles (1 time every 5 minutes).
(69 pages)
Manymanuals.com
Manymanuals.de
Manymanuals.fr
Manymanuals.it
Manymanuals.pl
Manymanuals.cz
Manymanuals.es
Manymanuals-pt.com
Commentaires sur ces manuels