Network Engineer
Your switch or firewall does not need an endpoint agent. A virtual network agent in the runtime connects to an authorized device over SSH, SNMP or its vendor API.
Device inventory
Read model, software version, uptime and interfaces with the configured protocol. Choose the correct device type and firmware-specific commands.
Switching & routing
Inspect interface counters, VLANs, neighbours and routing tables. Compare observations across devices without confusing cached data with a current read.
Firewall diagnosis
Review permitted status, policy and session information for Fortinet or Palo Alto through supported SSH/API operations.
Wireless & controllers
Use the configured UniFi or other controller integration to investigate access-point and client state where its API and privileges allow it.
SSH, SNMP & API
Use SNMP for telemetry, SSH/Netmiko for supported CLI commands and vendor APIs for structured operations; credentials remain in runtime integrations.
Coordinated investigation
Combine server and network results in a goal. Keep the target device explicit and distinguish a configuration proposal from an applied change.
Workflow
Connect
Bind the virtual agent to a specific address and approved integration.
Collect
Query read-only status through the supported protocol.
Correlate
Compare interface, routing or policy evidence with endpoint results.
Verify
Validate a permitted change and preserve a configuration backup where available.
Example prompts
@core01 show interface errors, VLAN membership and uplink status. Read-only checks only.
@forti01 inspect device status and permitted session information for the affected subnet.
@web01 @core01 compare the server route with the switch interface state and explain the evidence.
Evidence
- Target device and protocol
- CLI or structured API results
- Before/after observations
- Any unsupported commands or privilege restrictions
Prerequisites
- Network reachability from the runtime/collector to the management address.
- A supported SSH device type, SNMP credential or vendor API integration.
- Vendor-appropriate privileges and a defined change/rollback policy.
Boundaries
Cisco, Arista, Fortinet, Palo Alto and UniFi are integration targets, not a claim that every model, firmware or command is certified. Remote devices behind NAT need a routed path or collector; the portal demo does not create one.