Run this Knowledge Script in your Nortel Communication Server 1000 IP Telephony environment to trigger NetIQ Vivinet Diagnostics to diagnose a call quality problem between two Nortel IP phones.
Configure this Action on the NortelCS_Alarms Knowledge Script. A Diagnosis is triggered when the Alarms script raises events for the following QoS alarms (SNMP traps): QOS0022, QOS0024, QOS0026, QOS0028, QOS0030, QOS0032, and QOS0034. The Diagnosis makes use of the RTCP-XT statistics included in the SNMP trap.
You must run this Action on a computer where Vivinet Diagnostics 2.0 (or later) is installed. In addition, you must have already configured Vivinet Diagnostics with the security information for accessing the Call and Signaling Servers. For more information, see the User Guide for Vivinet Diagnostics.
Only one Diagnosis can run at any time. If a second Action is triggered while a Diagnosis is already in progress, the second Action will complete, but indicate that it could not run the Diagnosis because another was already in progress. To see the status of the Action for any event, click the Action tab of the event.
When the Diagnosis has completed, the Action Knowledge Script raises an event that identifies the location of the Vivinet Diagnostics .dgv file, which contains the results of the Diagnosis. In addition, if the Web management server and Report agent are installed on the computer that is running the Action, you can enable the Use Report Agent settings parameter, which integrates the Diagnosis results with other reports generated by the Report agent. The results are then easily accessible from the Web management server Report Binder and from the Operator Console’s Extensions > Report Viewer function.
HINT:To allow this script to trigger a Diagnosis with Vivinet Diagnostics whenever a problem occurs, you need to disable or modify the “event collapsing” feature on the NortelCS_Alarms script. Event collapsing allows AppManager to suppress, or collapse, what it considers to be duplicate events. However, you will probably want Vivinet Diagnostics to diagnose a problem each time one occurs, even if it occurs between the same two targets. And you cannot do that if AppManager has collapsed all call quality events between the same targets into one event. Use the Advanced tab of the NortelCS_Alarms script to disable event collapsing, or at least to modify the 20-minute collapsing interval.
Set the following parameters as needed:
|
Parameter |
How to Set It |
|---|---|
|
Output folder prefix |
Enter a prefix for the output folder that is generated by the Diagnosis. The output folder then uses this prefix in the following naming convention: Prefix_JobID_Phone1_Phone2_DateTime. The default prefix is Diag. Phone1 and Phone2 are the IP addresses of the two Nortel phones being diagnosed. The ComputerName is the name of the computer being diagnosed. |
|
Use Report Agent settings? |
If set to yes, the diagnostic results are integrated into the AppManager Web management server (the Report Binder). The default is y. |
|
Full path to root of output folders |
Enter the full local or UNC path to the root of the directory in which you want to create the output folders. Make sure that the NetIQmc service (NetIQ AppManager Client Resource Monitor) is configured to run as a user that has access to the UNC path. The default setting of “local system” does not have access to the UNC path. Without access to the path, Vivinet Diagnostics will not be able to save a Diagnosis to the output folder. NOTE:This parameter is ignored if Use Report Agent settings is set to y. |
|
Event Notification |
|
|
Severity when diagnosis successful |
Enter a severity level, between 1 and 40, to indicate the importance of an event that is raised when the Diagnosis completes successfully. The default is 35. |
|
Severity when error encountered |
Enter a severity level, between 1 and 40, to indicate the importance of an event that is raised when an error prevents the Diagnosis from completing successfully. The default is 15. |