Tagged vs Trunk

User avatar
nasked
Member
 
Posts: 38
Joined: Thu Sep 10, 2015 1:00 pm
Location: Spain
Has thanked: 2 times
Been thanked: 3 times

Tagged vs Trunk

Thu Oct 19, 2017 9:13 am

Hi:


Switch A -------- Switch B

I have a doubt with Trunk and Tag.

When I check the trunk box and in dialog box show 0-4095, I understand that is the same "trunk allow vlan all" in a cisco switch.

When I check the trunk box and write a few vlans (Ej: 102-109) I understand only this vlans are inside trunk, and rest of vlans dead in switch. (Switch A)

Also I can tagged each vlan...in each switch. At first it seems the same procedure as creating a trunk with the same vlans. I read in internet, diference between trunk and tagg, trunk gives better switch performance.

The first impression on the netonix is that trunk/vlan dialog box is to save having to dial one by one every vlan in tag mode. :D


I use a different management vlan in each switch, Ej Switch A management Vlan 102, Swtich B management Vlan 103. Switch B Management Vlan is declared inside trunk port in switch A, and declared in first line in switch B. Is correct?

last question, how can i renew ARP table by CLI? (No rebooting switch)

Thanks

User avatar
mike99
Associate
Associate
 
Posts: 837
Joined: Tue Nov 25, 2014 10:53 am
Location: Quebec, Canada
Has thanked: 95 times
Been thanked: 245 times

Re: Tagged vs Trunk

Thu Oct 19, 2017 10:25 am

Right, trunk = allow all = all VLAN include in the list are tagged. A single VLAN can optionnaly be untaged on the trunk, This vlan is the native native one (pvid).

For the MAC, I'm not sure but the MAC table (ARP table are layer 3) should refresh fast enough to not be problematic.

Return to General Discussion

Who is online

Users browsing this forum: Bing [Bot] and 99 guests