Actions83
- Bills Actions
- Alerts Actions
- Alert Rules Actions
- ARP Actions
- Devices Actions
- Device Groups Actions
- Inventory Actions
- Locations Actions
- Logs Actions
- Poller Groups Actions
- Ports Actions
- Port Groups Actions
- Routing Actions
- Services Actions
- Switching Actions
Overview
This node integrates with the LibreNMS network monitoring system, specifically allowing users to create new port groups. Port groups in LibreNMS are collections of network ports grouped logically for easier management and monitoring. This operation is useful when organizing ports by function, location, or any custom criteria to simplify network administration.
Practical examples include:
- Creating a port group for all switch ports on a particular floor.
- Grouping ports that serve a specific department or service.
- Organizing ports by type (e.g., uplinks vs. access ports) for targeted monitoring.
Properties
| Name | Meaning |
|---|---|
| Group Name | The name assigned to the new port group. This is a required field. |
| Description | A textual description providing additional details about the port group. Optional. |
Output
The node outputs JSON data representing the newly created port group as returned by the LibreNMS API. This typically includes fields such as the group's unique identifier, name, description, and possibly metadata like creation timestamps.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to a LibreNMS instance.
- Needs an API authentication token configured in the node credentials to authorize requests.
- The base URL of the LibreNMS API must be correctly set in the credentials.
- Optionally supports skipping SSL certificate validation if configured.
Troubleshooting
- Authentication errors: Ensure the API token is valid and has sufficient permissions to create port groups.
- Invalid input: The "Group Name" property is mandatory; missing it will cause the request to fail.
- API connectivity issues: Verify the LibreNMS URL is reachable and correct, including protocol (http/https).
- SSL errors: If using self-signed certificates, enable the option to skip SSL certificate validation.
- Unexpected API responses: Check LibreNMS server logs for more details if the node returns errors not related to input or authentication.
Links and References
If you need further details on other operations or resources, feel free to ask!