[f-nsp] Trunck config between cisco vss & mlx

[Jake Mertel]

Hello Harry,

This is pretty straight forward. On the Cisco side of things, your config would look something like this:

int gig 1/0/1
switchport trunk encap dot1q
switchport mode trunk
switchport trunk allowed vlan 10
switchport trunk allowed vlan add 20
switchport trunk allowed vlan add 30

The Foundry side is a bit different - Instead of "putting a VLAN on the interface" you would "put the interface in the VLAN".

vlan 10
tag eth 1/1
vlan 20
tag eth 1/1
vlan 30
tag eth 1/1

Connecting port gi1/0/1 of the fictional Cisco device with port eth1/1 of the fictional Foundry device would allow traffic in VLANs 10, 20, and 30 to pass. Of course, the eth 1/1 interface cannot have any kind of L3 config on it.

I hope this points you in the right direction.

--Jake

From: foundry-nsp [mailto:foundry-nsp-bounces at puck.nether.net] On Behalf Of Hambi, Harry
Sent: Wednesday, April 24, 2013 5:28 AM
To: foundry-nsp at puck.nether.net
Subject: [f-nsp] Trunck config between cisco vss & mlx

Hi all,
trying to configure 802.1q truck between cisco 6500 vss & brocade MLX..all docs i've seen show truck between 6500 and FI1500

Rgds
Harry

Harry Hambi.  BEng(Hons)  Miet. Rsgb.
Portfolio Delivery Line, Networks and Communications


Harry Hambi
Harry.Hambi at atos.net<mailto:Harry.Hambi at atos.net>
Siemens IT Solutions and Services Limited
Sir William Siemens Square
Frimley, Surrey GU16 8QD
harry.hambi at atos.net<mailto:harry.hambi at atos.net>
uk.atos.net
[cid:image002.gif at 01CE40BD.4364A8F0]
This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/foundry-nsp/attachments/20130424/e42997e1/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.gif
Type: image/gif
Size: 78 bytes
Desc: image001.gif
URL: <https://puck.nether.net/pipermail/foundry-nsp/attachments/20130424/e42997e1/attachment.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.gif
Type: image/gif
Size: 816 bytes
Desc: image002.gif
URL: <https://puck.nether.net/pipermail/foundry-nsp/attachments/20130424/e42997e1/attachment-0001.gif>