Title:
Force 4600c – Management VLAN and Transport VLAN Instability in Multi-Hop Chain
Body:
Hello Cambium Team,
We are deploying a network with Force 4600c radios configured in 7 consecutive hops (AP ↔ SM ↔ AP …). Routers are only at the first and last points.
Configuration:
-
Management VLAN ID: 2998 (enabled in the GUI)
-
Data VLAN ID: 1099 (used for transport and routing)
-
Both VLANs are added under Membership VLANs
-
Tested Management VLAN Access in two modes: Ethernet and Wireless, and also Ethernet only
-
Data VLAN set to Disabled (to avoid untagged traffic)
Symptoms:
-
From one end (BaseSL), sometimes only the AP IP is reachable but not the SM IP; sometimes the opposite.
-
ICMP ping in the Management VLAN shows intermittent timeouts.
-
In the Data VLAN, traffic sometimes drops for a few seconds and then recovers (“phantom cuts”).
-
The problem appears randomly on different hops.
Troubleshooting performed:
-
Removed VLAN 2998 from Membership VLANs, leaving only VLAN 1099.
-
Tested different Management VLAN Access modes (Ethernet only vs. Ethernet and Wireless).
-
Verified VLAN tagging in Membership VLANs → Show Details (SFP port set to Tagged).
-
Disabled the Data VLAN (leaving only VLAN IDs 1099 and 2998 in Membership).
-
Adjusted MTU/L2MTU on connected routers.
Questions:
-
Is there any known issue in Force 4600c firmware when carrying Management VLAN + Data VLAN across multiple hops?
-
What is the recommended configuration in the GUI for Management VLAN ID and Membership VLANs in multi-hop chains?
-
Should Management VLAN ID (2998) be set to “Ethernet only” and removed from Membership VLANs for stable operation?
We can provide Tech Support Files from the radios if needed.
Thank you for your guidance.