1. Parse current state
The tool extracts managed LAGs, member bindings, trunk VLANs, native/PVID values and VLAN inventory from the running configuration. Unsupported context is kept unmanaged.
OBSERVE → PLAN → VERIFY → ROLLBACK
Turn current device state into a minimal, risk-scored, reversible and verifiable network change plan.
Configuration parsing and verification run locally in your browser. V1.1 manages the tested LAG and trunk/VLAN domain only.
STEP 1 · OBSERVE
The loaded case is training data. Replace the running configuration before using the plan for a real change.
STEP 2 · INTENT
STEP 3 · PLAN
iBuild a plan to see the operational meaning of the detected drift and risk.
EXECUTION
STEP 4 · VERIFY
Paste the real output for each requested command. Missing evidence returns INCONCLUSIVE rather than a false PASS.
DOCUMENT
The document is generated from the same plan, risk factors, runbook, forward/rollback configuration and final verification decision.
Build a change plan to generate the MOP document.
The tool extracts managed LAGs, member bindings, trunk VLANs, native/PVID values and VLAN inventory from the running configuration. Unsupported context is kept unmanaged.
Select a real baseline device and ports, then declare aggregate ID, LACP/static mode, allowed VLANs and native VLAN. Conflicting member ownership and missing VLANs block execution.
State that is already correct is not reconfigured. Member, VLAN, native VLAN and description differences become deterministic forward actions and inverse rollback actions.
After execution, paste the requested show/display output back into the page. PASS requires positive evidence; incomplete evidence returns INCONCLUSIVE.
Member ownership conflicts, missing VLAN inventory, invalid port selection or invalid intent block configuration generation.
Post-change PASS requires sufficient CLI evidence. Missing or unsupported evidence is INCONCLUSIVE rather than assumed successful.
V1.1 automatically manages the platformized LAG and trunk/VLAN semantics only; BGP, OSPF, STP, QoS and other domains remain outside this tool.
Generated MOP and rollback output are engineering aids. Production execution should still follow vendor documentation, change approval, maintenance-window and site rollback procedures.
Production changes should minimize blast radius. The planner parses the managed current state and emits only the actions needed to reach the desired intent, plus the inverse rollback actions.
Flagship V1.1 manages the LAG and trunk/VLAN domains already implemented and tested in the V2 shared core. Other lines remain unmanaged context and are not automatically rewritten.
An aggregate that stays down, insufficient bundled members, trunk/native VLAN mismatch, unexpected aggregate members or new interface errors can trigger an automatic rollback recommendation.
No. Flagship V1.1 is a local browser-based planning, generation and verification tool. It does not log into devices, store credentials or automatically push configuration.
Automatic interface resolution is enabled only for baseline models in the Device Platform Catalog with explicit naming contracts. Outside verified scope, an engineer should confirm the interface rather than let the system guess.
Engineering content reviewed: 2026-09-05 · Scope: LAG + trunk/VLAN closed-loop change V1.1
Production execution should still be checked against the applicable vendor guide. Useful starting points include Cisco Catalyst 9200 documentation, Huawei Enterprise Switch documentation and Juniper EX Series documentation.
ENGINEERING WORKFLOW
Validate policy intent, then turn current device state and desired LAG/VLAN changes into a risk-scored, verifiable and reversible MOP.