Guide à l'aide de la documentation d'Avaya pour les VLAN
Guide à l'aide de la documentation d'Avaya pour les VLAN
Hello everyone, I'm here seeking guidance on this setup. I'm attempting to use VLAN 2 to establish a separate network, but so far I'm limited to connecting through my PF-Sense Hyper-V VM's LAN port. By assigning NICs to VLAN 2 and getting IP addresses from PF-Sense, it seems to work. Now I'm puzzled about how to route both untagged traffic and VLAN 2 through port 9 to another switch, like the Dell PowerConnect 2724. After that, I plan to direct untagged traffic to those ports and assign VLAN 2 to a few ports (23 and 24). I've reviewed basic trunking guides but am unsure if they apply here, especially since I'm still getting comfortable with VLANs. I can also use the CLI if needed. Appreciate any help!
It seems you're looking for guidance on switching from untagAll to tagAll, which configures the port as a trunk port. This approach should be mirrored on devices like the Dell switch. Let me know if you'd like further clarification!
The issue arises because setting the port to 'tagall' disables untagging, which affects all connected ports. VLAN 1 should remain untagged to ensure proper communication across ports.
I might be mistaken, but I only have a simple grasp of VLANs. From what I know, trunk ports typically can't carry non-tagged traffic. You'll need to create two VLANs and apply tags in sequence for this setup to function. VLAN 1 should be tagged with 1, while VLAN 2 should be tagged with 2. This way the trunk port can pass the tag information between switches.
Configure the first switch's VLAN1 as untagged (already completed) and VLAN2 as tagged on port 9, linking it to the Dell powerconnect. On the powerconnect, set VLAN1 untagged and VLAN2 tagged on the port connected to the first switch, while VLAN2 should be untagged on ports 23 and 24.
Not accurate. Trunk ports are simply labeled ports but will still allow untagged traffic referred to as native VLAN. You can stop this by marking native VLAN traffic on the exit and will internally discard untagged data. This aligns with standard security measures to avoid using VLAN 1 entirely.
I believe I handled everything correctly, and everything is working as intended. Appreciate your support.