Printer FriendlyEmail Article Link

VisionWorks Classic PM: How to identify services that are reporting error in VisionWorks Classic PM.

Objective/Summary

This shows how to identify services that are reporting errors in the PM Tests.   Errors will vary on the type of test being ran and the error that is occurring.  Some examples are: Ping Test - Unable to Resolve Target Address.  TWAMP Test - Arp Failed, Server TCP Connect Failed.

Environment/Versions

VisionWorks Classic PM: version 6.500 and later.

Procedure
  1. Identify Switch that has service(s) with problems.  In VisionWorks Classic PM, check the Collection Status window for switches with Yellow Alarm.


     
  2. Using the Summary Report, Choose the Switch found in step 1, Choose the Collection Type as needed, Using the pull-downs choose Metric of Frms/Pckts Sent IS NULL, Choose Interval of 5-mins.  To avoid seeing old alarms, modify the date time range to a recent value, span no more than 24 hours.


     
  3. Choose "Search".  This returns the services that have problem.  To see error that is happening for specific stream, highlight the service in the output, the graph and data below will report the specific error:

Notes

Note: If the collection error is at the switch level, all services that are built for the switch will show the error message.  This includes services that have "Service Active = No" which would normally not appear in the Performance Reports.   Some examples of error that are at the switch level is:

Stopped: Connect failed to host <IP Address> on port 7010. 
  (Can not connect to the STCLive probe)

Stopped: Maximum ESCOUT Test Sessions Reached.

Stopped: Login Failed.


Product : VW Controller PM Classic