AydanOS v3.1

Official Operator Instructions & Command Reference

Management Philosophy

AydanOS utilizes a Three-Plane Architecture. Changes are staged in the Candidate Config, analyzed for impact in the Staged FIB, and then physically committed to the Forwarding Plane.

Hierarchical CLI: Commands are context-sensitive. Access higher privileges via configure terminal.
Stochasticity: Real-world jitter and convergence delays are simulated. Outputs may vary based on link health.
Flow Persistence: Sessions are "sticky" and will not move to new paths until they time out or are flushed.

Command Reference

Exec Mode Global View

show ip route - Displays the active forwarding information base (FIB).

show ip route staged - Previews path election based on candidate changes.

trace [destination_ip] - Executes a stochastic flow-hashed traceroute.

show diff - Compares candidate-config against running-config.

configure terminal - Enters Global Configuration Mode.

Config Mode Control Plane Edits

hostname [name] - Sets the system identity.

interface [id] - Enters sub-interface configuration mode (e.g., interface wan1).

ip route [cidr] [next-hop] [interface] [metric] - Stages a static route.

no ip route [cidr] - Removes a staged or active route from the RIB.

commit confirmed [seconds] - Applies config with a safety rollback timer.

Chaos Ops Troubleshooting & Stress

set limit [interface] [gbps] - Hardware-level ingress traffic shaping.

attack [interface] - Injects a high-volume (120G) volumetric DDoS flow.

clear sessions - Flushes the Flow Table to force session re-hashing.

clear bgp - Manually resets BGP state machines to clear flaps.

discard - Purges the candidate buffer and stays in current mode.