Actions21
- Alarm Retrieval Actions
- ONT Actions
- Detect ONT State
- Add ONT Using The Serial Number
- Get ONT Using ONT's serial number
- Update Customer ID on ONT
- Get Upstream Bandwidth Profile
- Get Downstream Bandwidth Profile
- Create Customer Service
- Get Service
- Delete Customer Service
- Deactivate and Delete ONT
- Deactivate and Delete Endpoint
- Add UNI in Multiple Services
- Set State
- Change Speed Profile
- Factory Reset
- Add subscriber service
- Enable Wi-Fi
- Set SSID and WiFi password
- Delete WiFi Config
- Modify ONT's Node Edge Point
Overview
The node "TejasNms" provides an interface to interact with the Tejas Network Management System (NMS) API. Specifically, for the resource "ONT" and operation "Delete WiFi Config," it allows users to delete the WiFi configuration of a specified Optical Network Terminal (ONT) device by its serial number. This is useful in network management scenarios where administrators need to remotely reset or remove WiFi settings on ONT devices, for example, when decommissioning devices or troubleshooting connectivity issues.
Properties
| Name | Meaning |
|---|---|
| Serial Number | The unique serial number identifier of the ONT device whose WiFi configuration will be deleted. This is a required string input. |
Output
The node outputs JSON data representing the result of the delete WiFi config operation on the specified ONT device. The exact structure depends on the API response but typically includes status information indicating success or failure of the deletion request. There is no indication that binary data is output by this node.
Dependencies
- Requires an API key credential to authenticate with the Tejas NMS API.
- Depends on the Tejas NMS backend service being accessible.
- Uses internal HTTP client utilities to send requests to the Tejas NMS API.
- No additional environment variables are explicitly required beyond the API credentials.
Troubleshooting
- Common Issues:
- Invalid or missing serial number: The operation requires a valid serial number; ensure it is correctly provided.
- Authentication failures: Ensure the API key credential is valid and has sufficient permissions.
- Network connectivity problems: Verify that the node can reach the Tejas NMS API endpoint.
- Error Messages:
- Errors related to authentication usually indicate invalid or expired credentials.
- Errors about resource not found may mean the serial number does not correspond to any known ONT device.
- Timeout or connection errors suggest network issues or API unavailability.
Links and References
- Tejas Network Management System API documentation (refer to official vendor resources).
- n8n documentation on creating and using custom nodes with API integrations.