wouldn't this effect my customers ability to communicate with the 2 remote
sites which he wants on the same VLAN?
-----Original Message-----
From: Nisar Ali [mailto:nisar@juniper.net]
Sent: Monday, April 16, 2001 3:17 PM
To: juniper-nsp@puck.nether.net
Cc: juniper-nsp@puck.nether.net
Subject: Re: [j-nsp] VLAN-CCC Problem
Hi:
You can not use the same IFL for two different connections.
Create another one like ge-0/1/0.889(and vlanid 889) between vpn3-to-vpn2(or
for 3 to 1).
nisar
On Mon, Apr 16, 2001 at 02:46:58PM -0400, Owens, Shane (EPIK.ORL) wrote:
> We are trying to implement a VLAN-CCC connections from a single logical
> interface and are having problems with the config check. the scenario is
we
> have router a with a customer that wants a vlan connection to a customer
on
> router b and c. We have doing traffic engineering between these routers
and
> have LSP's built between each router. When we build the CCC connection
we
> get the following error.
> [edit protocols connections remote-interface-switch vpn3-to-vpn2]
> CCC: Connection vpn3-to-vpn2 error failed to add circuit 0 (duplicate?)
>
> here is the applicable config portions that's loaded currently.
>
> ge-0/1/0 {
> vlan-tagging;
> gigether-options {
> loopback;
> }
> unit 888 {
> encapsulation vlan-ccc;
> vlan-id 888;
> }
>
> mpls {
> traffic-engineering bgp-igp;
> traceoptions {
> file mpls.log size 10k files 5;
> flag all;
> }
> label-switched-path 3-to-1 {
> to 1.1.1.1;
> no-cspf;
> }
> label-switched-path 3-to-2 {
> to 2.2.2.1;
> no-cspf;
> }
> interface all;
>
> connections {
> remote-interface-switch vpn3-to-vpn1 {
> interface ge-0/1/0.888;
> transmit-lsp 3-to-1;
> receive-lsp 1-to-3;
> }
> remote-interface-switch vpn3-to-vpn2 {
> interface ge-0/1/0.888;
> transmit-lsp 3-to-2;
> receive-lsp 2-to-3;
> }
> }
>
>
> Any suggestions or comments on if this is even possible are appreciated.
>
>
>
>
> Shane Owens
>
>
>
This archive was generated by hypermail 2b29 : Mon Aug 05 2002 - 10:42:42 EDT