What's New
| • | NSR-177: It is now possible to customize the NetWorker log scan limit from BMC TrueSight Operations Management. |
Changes and Improvements
| • | The Sudo configuration in the sudoers file must be modified for Solaris, HP-UX, AIX and Linux to prevent EMC NetWorker Monitoring commands failures (see Security Requirements). |
| • | The KM has been improved to better perform in large environments. |
| • | EMC NetWorker Monitoring has been improved to support all PATROL Agent v10+ versions as well as BMC TrueSight Operations Management v10.x. |
Fixed Issues
| • | The KM has been improved to avoid intermittent crashes of the PATROL Agent on NetWorker v7.x. |
| • | The Microsoft Cluster active node was not properly detected when the monitoring solution was operating in multi-node monitoring mode. |
| • | Invalid alarms were triggered on the Login Status attribute (EMC NetWorker KM)when the monitoring solution was unable to check the active node. |
| • | The status report file of EMC NetWorker Monitoring is now suffixed with the Agent port number to avoid overwriting it when multiple virtual Agents are used. |
| • | On Windows systems, if the PATROL Agent installation path contained spaces, scripts calls and output redirection commands failed. |
| • | Upon new installations, EMC NetWorker Monitoring was not always able to perform a full discovery after a login configuration. |
|
