This message was deleted.
# harvestera
adamant-kite-43734
07/26/2023, 2:04 PMThis message was deleted.
s
swift-eve-48927
07/26/2023, 5:06 PMI got it figured out. I’m testing this out on Proxmox and the NIC wasn’t set to allow vlan tagging, so the tagged storage packets weren’t going through. This brings up the question, why are vlan ids being forced on the Longhorn storage network setup? If it’s a dedicated NIC and Switch, it shouldn’t be needed.
r
red-king-19196
07/27/2023, 12:53 AMFor untagged traffic, we usually set the “VLAN ID” field to
1s
swift-eve-48927
07/27/2023, 1:24 AMThank you. I had tried setting to VLAN ID
1🙌 1
r
red-king-19196
07/27/2023, 1:28 AMcc @orange-policeman-97710
Do you have any insight into this? About the mandatory VLAN ID setting in the storage network.
o
orange-policeman-97710
07/27/2023, 2:05 AMIt's required to support untagged network. Could you help file an issue?
r
red-king-19196
07/27/2023, 8:03 AMThe corresponding issue has been created. @swift-eve-48927 feel free to add more details to it (or let me attach the link to this thread for the issue background). Thank you!
https://github.com/harvester/harvester/issues/4323
👍 1
red-king-19196
08/01/2023, 8:06 AMHi @swift-eve-48927, I’ve done some tests about it, and it seems there are no VLAN headers in the packets when the storage network’s VLAN ID is set to 1. FWIW, I use tcpdump to listen on the Harvester node’s network interface with the following command:
Copy code
$ tcpdump -i enp2s0 -nn -e vlans
swift-eve-48927
08/01/2023, 10:48 AMGood to know! I must have been experiencing a different problem when I had the ID set to
1r
red-king-19196
08/02/2023, 7:30 AMAnother guess: did you set the MTU size to a value other than the default 1500?
s
swift-eve-48927
08/02/2023, 10:14 AMNo, I left the field blank.
👌 1
24 Views