¶ 🧭 Network Qualification – RobotViabilityTask
This document describes the complete Legacy Network Qualification process, using viability robots (RobotViabilityTask), to prepare and later execute TR-069 robots.
¶ 🎯 Qualification Objective
The Network Qualification aims to:
- Identify active equipment in the legacy base
- Map router/AP models
- Verify remote access to the CPE WAN/Internet interface via WEB ports
- Evaluate automation viability
- Generate inputs for automated device import
¶ 🔁 Process Overview
- Create RobotViabilityTask automation
- Run the qualification
- Analyze results
- Process logs and consolidate data for TR-069 robot execution
¶ ⚙️ 1️⃣ Create Automation – RobotViabilityTask
Qualification starts by registering a new RobotViabilityTask in the portal.
¶ 🔧 Automation Parameters
| Field | Description |
|---|---|
| Name | Qualification identifier (e.g.: QUALIFICACAO_REDE_70K). |
| Port list | WEB ports separated by commas (e.g.: 80,443,8080). |
| Random Task Order | Executes PPPoE users in random order, avoiding always testing in the same sequence. |
| Rediscover clients | Allows reprocessing already qualified clients. |
| Select city | Selects cities where qualification will run. |
| Threads | Number of parallel tasks (recommended maximum 10). |
| Fault tolerance | Limit of minor faults (known faults – recommended maximum 100). |
| Start date | Set start date and time considering the browser time zone. |
| End date | Deadline for task completion. |
¶ 📊 2️⃣ Qualification Results
After execution, the results screen displays:
- Total executed tasks
- Successful tasks
- Failed or errored tasks
- Interrupted tasks
- Scheduling information
- Result charts
- Table of identified equipment models and quantities
- Logs grouped by return type
¶ 🧾 3️⃣ Grouped Log Messages
| Status | Log Message | Scenario Description | Recommended Action | Responsible |
|---|---|---|---|---|
| ❌ Error | Error getting client IP. Client_IP Possible down |
Robot could not obtain a valid IP from Radius query. Client possibly offline or without active PPPoE session. | Send affected PPPoE list to the ISP for validation. | ISP |
| ❌ Error | No open ports found for this IP |
Client has active IP, but none of the configured WEB ports are externally accessible. | Check firewall, NAT, CGNAT, or blocking policies. | ISP |
| ⚠️ Warning | Unable to correctly identify AP through webpage |
Equipment accessible, but model not recognized by the qualifier. | Open a request to INT6 for new model homologation. | INT6 |
| ✅ Success | Router found |
Equipment successfully identified and compatible with existing qualifiers. | Confirm model and credentials and prepare for TR-069 robots. | INT6 + ISP |
¶ 🛠️ 4️⃣ Working with Results
After Network Qualification execution, result analysis is mandatory before any automation.
¶ 📥 Accessing the results file
- Go to System → Automations
- Select the executed qualification
- Click Download CSV
The file is provided in CSV/XLSX format, containing full execution details.
¶ 📂 Results file structure
| Tab | Content | Practical Use |
|---|---|---|
| Tasks | Complete log of all executed tasks. | Main base for general analysis and consolidation. |
| Error getting client IP | Clients without active IP. | Send list to ISP. |
| No open ports found | Inaccessible WEB ports. | Firewall/NAT adjustment. |
| Unable to correctly identify | Unrecognized model. | INT6 homologation. |
| Router found | Valid equipment. | TR-069 execution. |
| Internal errors | Unexpected failures. | Specific analysis. |
¶ 🔎 How to use the file in practice
- Analyze the Tasks tab
- Handle errors with the ISP and INT6
- Validate identified models
- Consolidate eligible clients
When necessary, the ISP may run new qualification tasks after performing adjustments.
¶ 🚦 Process continuation rule
Only after processing and consolidating results:
When approximately 40% of the network is qualified, the process may advance to TR-069 robot execution.