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 integration with the TejasNms API, allowing users to perform various operations on network management resources. Specifically, for the resource ONT and operation Deactivate and Delete Endpoint, this node enables deactivating and deleting an endpoint associated with an Optical Network Terminal (ONT). This is useful in scenarios where a network administrator needs to remove or deactivate endpoints from the network managed by TejasNms, such as when decommissioning devices or cleaning up unused network elements.
Practical examples include:
- Deactivating and removing an ONT endpoint that is no longer in use.
- Automating cleanup of endpoints during network maintenance or reconfiguration.
- Integrating with workflows that manage lifecycle events of network devices.
Properties
| Name | Meaning |
|---|---|
| Connectivity Service | The identifier or name of the connectivity service under which the ONT endpoint exists. |
| UUID | The unique identifier of the ONT endpoint to be deactivated and deleted. |
Output
The node outputs JSON data representing the result of the deactivate and delete operation on the ONT endpoint. This typically includes confirmation of success or failure, status messages, and any relevant metadata returned by the TejasNms API.
If the node supports binary data output, it would relate to any files or raw data returned by the API, but based on the provided code and context, the primary output is structured JSON reflecting the operation's outcome.
Dependencies
- Requires an active connection to the TejasNms API via an API key credential configured in n8n.
- Uses internal HTTP client utilities to communicate with the TejasNms backend.
- Depends on the TejasNms API being accessible and properly authenticated.
- No additional external services are indicated beyond the TejasNms API.
Troubleshooting
- Authentication errors: If the API key or credentials are invalid or expired, the node will fail to authenticate. Ensure the API key credential is correctly set up and has necessary permissions.
- Invalid UUID or Connectivity Service: Providing incorrect or non-existent UUIDs or connectivity service names will cause the operation to fail. Verify these values before execution.
- Network issues: Connectivity problems between n8n and the TejasNms API can cause timeouts or request failures. Check network access and API availability.
- API errors: The TejasNms API may return error messages if the endpoint cannot be deactivated or deleted due to state or policy restrictions. Review API response messages for details.
Links and References
- TejasNms API Documentation (Replace with actual URL if available)
- n8n Documentation on Creating Custom Nodes
- General information on Optical Network Terminals (ONTs): ONT Wikipedia