Your First Commands
Now that you have devices connected, let's run some commands. Inishi's Command Terminal accepts natural language queries — just type what you want to know.
Opening the Command Terminal
- Click Command Terminal in the sidebar (or press
Cmd+K/Ctrl+K) - Select a site to scope your queries (optional but recommended)
- Start typing!
Read-Only Queries (No Approval Needed)
These queries gather information without making changes. They run immediately.
Show Interface Status
"Show me the interfaces on router-01"Returns:
Interface Status Protocol Description
GigabitEthernet0/0 up up WAN Link
GigabitEthernet0/1 up up LAN
Loopback0 up up ManagementCheck BGP Neighbors
"What's the BGP status on all routers?"View Routing Table
"Show the routing table for router-01"Get Device Logs
"Show me the last 50 log entries on switch-01"Multi-Device Queries
"Show interface errors on all devices in NYC"Inishi will query all devices in the NYC site and aggregate the results.
Diagnostic Queries (AI Analysis)
These queries use AI to analyze device state and provide insights.
Troubleshooting
"Why is the BGP neighbor 10.0.0.2 down on router-01?"Inishi will:
- Gather relevant state (BGP, interfaces, logs)
- Analyze the data
- Identify the root cause
- Suggest next steps
Health Checks
"Are there any issues on router-01?"Comparison
"Compare the running config to startup config on router-01"Configuration Changes (Approval Required)
When you ask Inishi to make changes, it shows you the exact commands first.
Example: Shutdown an Interface
"Shut down interface GigabitEthernet0/1 on router-01"Inishi responds:
Proposed commands for router-01:
configure terminal
interface GigabitEthernet0/1
shutdown
end
Impact: Interface GigabitEthernet0/1 will stop forwarding traffic.
[Approve] [Reject] [Edit]Click Approve to execute, or Reject to cancel.
⚠️
Configuration changes require write access. By default, new accounts start in read-only mode. Contact support to enable write access when you're ready.
Tips for Better Queries
Be Specific
# Good
"Show the BGP neighbors on router-nyc-01"
# Less specific (works but slower)
"Show BGP"Use Device Names
# Good
"Check interface errors on switch-01"
# Also works (queries all devices)
"Check interface errors"Ask Follow-Up Questions
After a query, ask follow-up questions for more detail:
> "Show interfaces on router-01"
[results displayed]
> "Why is GigabitEthernet0/1 down?"
[AI analysis]Keyboard Shortcuts
| Shortcut | Action |
|---|---|
Cmd+K / Ctrl+K | Open Command Terminal |
↑ / ↓ | Navigate command history |
Esc | Close terminal |
Enter | Submit query |
Example Session
> "What devices are in the NYC site?"
Found 3 devices in NYC:
- router-nyc-01 (10.0.0.1) - Cisco IOS
- switch-nyc-01 (10.0.0.2) - Arista EOS
- fw-nyc-01 (10.0.0.3) - Juniper Junos
> "Show the interfaces on router-nyc-01"
Interface Status Protocol
GigabitEthernet0/0 up up
GigabitEthernet0/1 down down
Loopback0 up up
> "Why is GigabitEthernet0/1 down?"
Analysis:
Interface GigabitEthernet0/1 is administratively down.
Evidence:
- show run int Gi0/1: "shutdown" command present
- No physical layer errors
The interface was likely shut down intentionally.
To bring it up, remove the shutdown command.
> "Bring up GigabitEthernet0/1"
Proposed commands for router-nyc-01:
configure terminal
interface GigabitEthernet0/1
no shutdown
end
[Approve] [Reject]Next Steps
- Network Automation Without Ansible — How Inishi compares to traditional tools
- Cisco BGP Troubleshooting — Deep dive on BGP diagnostics
- Supported Vendors — Full platform compatibility