docs: Clarify why nodes must be started for device config tools

This commit is contained in:
YueGuobin 2026-06-14 13:41:04 +08:00
parent 9f3a6a7e58
commit 754eab9609
No known key found for this signature in database

View File

@ -213,7 +213,7 @@ Both JWT tokens and API keys work for MCP and REST API endpoints interchangeably
| `device_command_run` | Run read-only show commands on devices. Supports Jinja2 `template` + `vars` |
| `vpcs_config_set` | Configure VPCS devices (IP, gateway, etc.) |
Requires nodes to be started first. Device type is auto-detected from the node's `device_type:<type>` tag.
The tool connects to each device's console via telnet/SSH. Nodes must be in the `started` state (use `node_start` or `node_start_all`). Device type is auto-detected from the node's `device_type:<type>` tag in GNS3.
#### Jinja2 Template Mode