26 Posts
0
375
N2000 and N4064 Trunk issue
N4064 is the core switch with all VLANs. Core switch has a LAG set to trunk to N2000 switch and the lag is a member of all VLANs. The ports the core are attached to on the N2000 are a LAG set to general. For reasons beyond me, if I change the LAG on the N2000 series to trunk, I loose all management access to the switch. No CLI or Web UI. Interface is not pingable. All other traffic appears to be flow as normal. The LAG is a member of all VLANs on the N2000. Any suggestions?
djhurt1
26 Posts
0
May 31st, 2022 09:00
I've figured this out. Purely overlooking on my part. While I set the Vlans in question to tagged under the Lag while it was in general mode, when changing it to trunk it reverted them to forbidden in the trunk. I consoled into the switch and went through the config one by one and discovered this. Setting them back to tagged resolved the issue.
DELL-Young E
Moderator
Moderator
•
3.6K Posts
0
May 24th, 2022 22:00
Hi,
"
A Trunk connection allows multiple tagged frames across the connection. On some switches it will only allow tagged frames. On others it will allow 1 VLAN to pass untagged frames, this VLAN is the native VLAN.
A General connection can send and receive tagged traffic for multiple VLANs. Untagged traffic may also be sent via several untagged VLANs. However returning untagged traffic will only be received by the PVID and therefore will not be forwarded to a specific VLAN.
In most cases you will want to try using Trunk mode first. But sometimes when connecting different model switches together Trunk mode may not work, in which case you would then use General mode."
https://dell.to/3MOwbi5
Here is a quick overview of General mode and it's configuration.
https://dell.to/3wLeMl1
Here is a short blog someone put together with some of the same information
It should be either trunk to trunk(end to end ) or general to general(end to end)
We should not use trunk (source) to general(destination) =>end to end