Task Reports
This document explains how diagnostic task reporting works on PE devices. The process is the same as for CE devices. It highlights the main features and concepts, along with a link to the detailed CE guide for step-by-step instructions.
The Task Report page enables tracking of diagnostic tests run on PE devices. It displays the test status, duration, and results, which is essential for troubleshooting and performance verification.
For detailed steps, see the CE Task Report. The user screens look the same on both PE and CE devices.
Link to CE Task Report Documentation: CE Task Report Document
Core Task Report Features
The table below outlines the primary fields available in the PE device’s Task Report table.
| Field | Description |
|---|---|
| Task Name | Identifier assigned to the diagnostic task at creation. |
| Target IP / Domain | The IP address or domain name being tested. |
| Ping | Indicates connectivity status. ✓ = success, × = failure. |
| TCPPing | Validates TCP port reachability. ✓ = open, × = closed/unreachable. |
| HTTPPing | Confirms HTTP port responsiveness. ✓ = responding, × = not responding. |
| Started | Timestamp when the task was initiated. |
| Completed | Timestamp when the task finished. |
| Action | Provides management options, including task deletion. |
Basic Task Workflow
The general workflow for managing tasks on a PE device is as follows:
- Accessing Tasks: Navigate to Login → PE Device → [Select PE Device] → Diagnostic → Task Report.
- Create a Task: Initiate a diagnostic task targeting an IP or domain.
- Wait for Report: Allow up to 5 minutes for the task report to populate.
- Review Results: Check connectivity and port responsiveness via Ping, TCPPing, and HTTPPing indicators.
- Filter Reports: Reports can be filtered by Task Name or Target IP/Domain using dropdown filters. This allows quick identification of specific diagnostic results.
- Delete a Task: Select the task, click Delete, and confirm the action. A success message will appear.
Important Notes for Users
- Task results are not generated instantly. It may take up to 5 minutes for the Task Report to update after a diagnostic task is created.
- Task names should be meaningful and unique so reports can be easily identified later.
- Ping, TCPPing, and HTTPPing results are independent checks. Even if Ping succeeds, TCP or HTTP checks may still fail due to port or service restrictions.
- Reports are device-specific. A task created on one PE device will not appear on another device.
- Deleted tasks cannot be recovered. Ensure you have reviewed results before deleting.
- Filtering helps quickly locate tasks. Use Task Name or Target IP/Domain filters instead of scrolling.
- Time shown is based on system time configuration. If timestamps look incorrect, confirm the device time sync configuration.
- Network security policies may block certain checks. TCP/HTTP failures do not always mean a device is offline.
- Use reports for troubleshooting validation. They help confirm connectivity issues before raising support or performing escalation.