https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# harvester
a
This message was deleted.
b
So far the inactive ones are in a private natted network that has HAProxy floating the gateway between two devices. DHCP works, Nat works, all the vms connected get IPs and get get out to the internet, so I have no idea of what's causing the check to fail.
It's not really a big deal, but I'd love to find out how to get those to show green.
😅
m
We have this too sometimes... I was always wondering why it is not shown active while still completly functional
I just checked... currently everything is showing correctly for us but I know for a fact that in the summer non of the VMNetworks were Active but were working just fine... but this was after our DC moved to a new server room and there were some weird Network Issues ... especially with incompatible cableling and wrong firmware versions of the SFP modules but apparently after they switched the wrond cables those issues went away, alongside our problems with AutoNeg
b
I just have no idea how it evaluates it being active or not. ¯\_(ツ)_/¯
h
Hm maybe the gateway? I can’t remember - can you check the route section of the VM Network.
b
Even when I set the route to the gateway manually (instead of DHCP) it still shows up inactive.
Oh and when switching from DHCP (automatic) to manual, it populates it correctly.
s
I have all of mine with route mode set to 
manual
, and still one is incorrectly showing as 
inactive
on the list page, but 
active
when I click into that network.
b
I'm pretty sure that's the 
State
and not the 
Route Connectivity
on the page
s
Could be right. Anyway - nodes on Harvester can connect to that VLAN so it's active is some way 😉
4 Views
Open in Slack
PreviousNext
Powered by