[f-nsp] Multi Trunking separate VLANs between 2 switches

Pritesh Patel (CW) priteshp at Brocade.com
Fri Mar 19 16:59:46 EDT 2010


No It won't create loop.
You have to tag ports first then create a trunk.

Vlan 10
Tag e 1/5 to 1/8
Vlan 11
Tag e1/5 to 1/8

Then create a trunk group.
Older codes require you to do port /vlan config first before you deploy trunk Then

Trunk ports ..
Deploy

Thanks,
Pritesh




From: foundry-nsp-bounces at puck.nether.net [mailto:foundry-nsp-bounces at puck.nether.net] On Behalf Of Gary H
Sent: Friday, March 19, 2010 1:54 PM
To: foundry-nsp at puck.nether.net
Subject: Re: [f-nsp] Multi Trunking separate VLANs between 2 switches

Port typo corrected in group1

SWITCH A TRUNK Group1
e1/1 to 1/4
e2/1 to 2/4

SWITCH B TRUNK Group1
e1/1 to 1/4
e2/1 to 2/4


On Fri, Mar 19, 2010 at 4:49 PM, Gary H <ciscovoiper at gmail.com<mailto:ciscovoiper at gmail.com>> wrote:
I can't find an example of multi trunking VLANs between two switches to maximize Group1 and Group2 8GB trunk per vlan. Think this will work? (proper syntax not used) Is the Group2 trunk going to require tagged trunk ports and as a result, carry all the VLANs and then create a loop?

VLAN 1 (default vlan) contains dual mode ports, but trunk shouldn't need dual mode

SWITCH A TRUNK Group1
e1/2 to 1/4
e2/1 to 2/4

SWITCH B TRUNK Group1
e1/2 to 1/4
e2/1 to 2/4


VLAN 2 contains tagged ports and untagged ports and IP Subnet voice traffic

SWITCH A TRUNK Group2
e1/5 to 1/8
e2/5 to 2/8

SWITCH B TRUNK Group2
e1/5 to 1/8
e2/5 to 2/8

Thank you
Gary

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/foundry-nsp/attachments/20100319/0a79454e/attachment.html>


More information about the foundry-nsp mailing list