Overview
This node integrates with the Mikrotik API, allowing users to perform various operations on Mikrotik devices. Specifically, the "disable" operation under the "Default" resource disables a specified interface or feature identified by an ID or named parameter. This is useful for network administrators who want to programmatically manage device configurations, such as disabling interfaces or services remotely.
Practical examples include:
- Disabling a specific network interface by its ID or name.
- Temporarily turning off certain features during maintenance windows.
- Automating network configuration changes in response to monitoring alerts.
Properties
| Name | Meaning |
|---|---|
| Host | The hostname or IP address of the Mikrotik device to connect to. |
| Ignore SSL Issues | Whether to ignore SSL certificate validation errors when connecting (true/false). |
| Id | The identifier or named parameter of the item to disable. Examples: *1, ether1. |
Output
The node outputs JSON data representing the result of the disable operation performed on the Mikrotik device. This typically includes confirmation of the action taken or details about the disabled entity. The output does not explicitly mention binary data handling, so it is assumed to be purely JSON-based.
Dependencies
- Requires an API key credential for authenticating with the Mikrotik API.
- Needs network access to the specified Mikrotik device host.
- Supports ignoring SSL certificate issues if configured.
- Uses internal client and operation resolver classes to handle API communication and operation execution.
Troubleshooting
- Connection failures: Ensure the Host property is correct and reachable from the n8n instance.
- SSL errors: If connecting over HTTPS and encountering SSL validation errors, enable "Ignore SSL Issues" to bypass certificate checks.
- Invalid ID: Providing an incorrect or non-existent ID/named parameter will cause the disable operation to fail; verify the ID format and existence on the device.
- Authentication errors: Confirm that the API key credential is valid and has sufficient permissions on the Mikrotik device.