What problem does it solve? Chassis clusters on Proxmox VE fail silently: the hypervisor substitutes Linux bridges for physical control and fabric links, so clusters form and report healthy while passing no traffic, with nothing logged. This Skill pins the hypervisor-to-Junos seam — bridge and VLAN design, NIC-to-interface mapping, cluster bootstrap, and a validation sequence that catches silent filtering instead of trusting a green status line. ## Core Features & Use Cases - Hypervisor network design: Build a portless, VLAN-aware bridge at MTU 9000 with one VLAN per function, and enforce the load-bearing bridge port flags (learning on, isolation off, neighbour suppression off). - NIC mapping and bootstrap: Map virtual NICs to Junos interfaces (net0→fxp0, net1→em0, shift-by-two for ge- interfaces), configure cluster-id, fab interfaces, reth interfaces, redundancy groups, and static per-node fxp0 addressing under groups. - Failure diagnosis: Symptom-to-cause tables for the anti-spoof trap (per-NIC firewall discarding reth virtual MACs), undersized fabric segments, RG1 hold state, and one-way blackholes from node asymmetry. - Use Case: A two-node vSRX cluster reports all reths Up but passes no traffic. Use this Skill to check the per-NIC firewall setting and the bridge forwarding table for the 00:10:db virtual MACs, identifying the anti-spoof rule as the cause. ## Quick Start Use the srx-chassis-cluster-proxmox skill to plan, build, and validate a two-node vSRX chassis cluster on my Proxmox VE host, starting by checking whether a jumbo-capable bridge exists for the fabric segment.
