Foundry has a slightly different take on making a service 'transparent' (at least from what I was used to with JNPR). To make it transparent, you change the tag-type to something that won't be used by the customer (Foundry TAC recommended 9100) and then make the port untagged in the VLL definition. So in your config below, looks like you should just need to set 'tag-type 9100 ethe 1/20' and be on your way. I believe the tag-type 9100 is related to a Metro Ethernet Forum recommendation regarding how QinQ should be handled (per 802.3ad). I was able to get this working using XMR4 and a T640, so hopefully your J-series acts the same.
HTH, David 2009/4/14 Brad Fleming <[email protected]>: > Hello all, > I'm new to the list but haven't found an answer to my question in the > archives. If the topic has already been covered, my apologies. > I'm attempting to build an MPLS VLL using the following gear: > 1) Foundry / Brocade NetIron XMR running IronWare 4.0.00a > 2) Juniper J-6350 running JunOS 9.4R1.8 (Enhanced Services) > I'm having problems getting the VLL to pass both tagged and untagged > traffic. For now, I'd be happy just getting untagged traffic across the link > and tackle the multiple VLAN tags later. Little victories, if you will! > :D Both devices claim the service is up but traffic does not dump out the > other side. > I'm 99.9% sure I'm missing something basic but I don't have a good > configuration example for this setup. > Any help or insight would be GREATLY appreciated! Thanks in advance! > -brad fleming > -- > Brad Fleming > Network Engineer > Kansas Research and Education Network > Office: 785-856-9800 x.222 > Moblie: 785-865-7231 > NOC: 866-984-3662 > > > > Here's a couple show commands: > tel...@fake-ksu(config-mpls-vll-test)#show mpls vll > Name VC-ID Vll-peer End-point State > Tunnel-LSP > test 2 164.113.199.108 untag e 1/20 UP tnl0 > > tel...@fake-ksu(config-mpls-vll-test)# > brad# run show l2circuit connections extensive > Layer-2 Circuit Connections: > <<<deleted legend for brevity>>> > Neighbor: 164.113.199.103 > Interface Type St Time last up # Up trans > ge-0/0/1.0(vc 2) rmt Up Apr 15 05:11:58 2009 1 > Remote PE: 164.113.199.103, Negotiated control-word: No > Incoming label: 299776, Outgoing label: 800000 > Local interface: ge-0/0/1.0, Status: Up, Encapsulation: ETHERNET > Connection History: > <<<deleted history for brevity>>> > > > Here's the pertinent config from both devices: > ------XMR: > ! > router mpls > ! > mpls-interface e1/1 > ldp-enable > ! > vll test 2 raw-mode > vll-mtu 9178 > vll-peer 164.113.199.108 > untag e 1/20 > ! > end of MPLS configuration > -------J-6350: > interfaces { > ge-0/0/0 { > description "link to NetIron"; > enable; > mtu 9192; > unit 0 { > family inet { > address 164.113.192.130/30; > } > family mpls; > } > } > ge-0/0/1 { > description "MPLS-enabled Drop Port -- to CE"; > mtu 9192; > encapsulation ethernet-ccc; > unit 0 { > } > } > } > lo0 { > description loopback; > unit 0 { > family inet { > address 164.113.199.108/32; > } > } > } > } > protocols { > mpls { > interface all; > } > ospf { > traffic-engineering; > area 0.0.0.0 { > interface ge-0/0/0.0; > interface lo0.0; > interface ge-0/0/1.0 { > disable; > } > } > } > ldp { > interface ge-0/0/0.0; > interface ge-0/0/1.0 { > disable; > } > interface all; > } > l2circuit { > neighbor 164.113.199.103 { > interface ge-0/0/1.0 { > virtual-circuit-id 2; > mtu 9178; > } > } > } > } > > _______________________________________________ > foundry-nsp mailing list > [email protected] > http://puck.nether.net/mailman/listinfo/foundry-nsp > _______________________________________________ foundry-nsp mailing list [email protected] http://puck.nether.net/mailman/listinfo/foundry-nsp
