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 "TejasNms" node integrates with the Tejas Network Management System (NMS) API, specifically supporting operations on various network resources. The "Create Customer Service" operation under the "ONT" resource allows users to create a new customer service configuration on an Optical Network Terminal (ONT). This is useful in telecommunications and network management scenarios where automated provisioning and configuration of ONT services are required.
Typical use cases include:
- Automating the setup of customer connectivity services in fiber optic networks.
- Integrating with OSS/BSS systems to provision services dynamically.
- Managing bandwidth profiles and connectivity constraints programmatically.
For example, a network operator can use this node to create a new customer service with specific connectivity parameters, bandwidth profiles, and endpoint configurations without manual intervention.
Properties
| Name | Meaning |
|---|---|
| Connectivity Service | A collection defining the connectivity service details including: - Name: Multiple entries each with fields specifying key-value pairs for naming. - Connectivity Constraint: Defines service type constraints. - End Point: Multiple endpoints with detailed configurations such as: - Name (multiple key-value pairs) - Layer Protocol Name - NRP Carrier Ethernet Connectivity End Point Resource, which includes VLAN ID lists, CoS identifiers, and S VLAN ID lists. - Upstream Bandwidth Profile: UUID identifying the upstream bandwidth profile. - Downstream Bandwidth Profile: UUID identifying the downstream bandwidth profile. - Additional Information: Multiple key-value pairs for extra metadata. |
| Layer Protocol Name | String specifying the layer protocol name associated with the customer service. |
| Additional Information | Multiple key-value pairs allowing users to add extra metadata or custom information related to the customer service. |
| Direction | String indicating the direction of the service (e.g., upstream, downstream). |
Notes on Property Options:
- Many properties support multiple values and nested collections, allowing complex hierarchical data structures.
- VLAN IDs and CoS names can be specified in lists to define traffic handling and segmentation.
- Additional information fields provide flexibility for custom attributes.
Output
The node outputs JSON data representing the result of the "Create Customer Service" operation. This typically includes confirmation details from the TejasNms API about the created service, such as service identifiers, status, and any relevant metadata returned by the backend.
If the API supports binary data output (not indicated explicitly here), it would represent related artifacts or files; however, based on the static analysis, the output is primarily structured JSON reflecting the created customer service details.
Dependencies
- Requires an API key credential for authenticating with the TejasNms API.
- Depends on the external TejasNms API service being accessible and properly configured.
- Uses internal helper classes for HTTP requests, state management, and operation resolution within n8n.
- No additional environment variables are explicitly required beyond the API credentials.
Troubleshooting
- Authentication Errors: Ensure that the API key credential is correctly configured and has sufficient permissions.
- Invalid Property Values: Complex nested properties like VLAN IDs and bandwidth profiles must be correctly formatted; invalid or missing required fields may cause API errors.
- Network Issues: Connectivity problems to the TejasNms API endpoint will prevent execution; verify network access and endpoint URLs.
- API Limitations: The backend might reject requests if service types or protocol names are unsupported; validate inputs against the TejasNms API documentation.
- Empty or Missing Required Fields: Some collections require at least one entry; ensure mandatory fields are populated to avoid validation errors.
Links and References
- Tejas Network Management System (NMS) API Documentation (Replace with actual URL)
- n8n Documentation on Creating Custom Nodes
- General VLAN and Bandwidth Profile Concepts: Networking Basics
This summary is based solely on static code analysis and provided property definitions without runtime execution or dynamic import resolution.