[j-nsp] Re : Re: Re : juniper - cisco l2circuit problem
hritter at videotron.ca
hritter at videotron.ca
Wed May 30 08:24:57 EDT 2007
Atanas,
You do not need an OSM+/SIP400/SIP600/ES20 if you put the xconnect on the physical interface or logical subinterface but you absolutely need one of these modules if you configure the xconnect on the SVI interface (aka vlan interface).
Cheers,
----- Message d'origine -----
De: Atanas Yankov <xdsgrrr at consultcommerce.com>
Date: Mercredi, Mai 30, 2007 6:06 am
Objet: Re: [j-nsp] Re : juniper - cisco l2circuit problem
À: juniper-nsp at puck.nether.net
> Its Wrong you don't need to OSM modules on SUP720 u can use xconnect
> vlan100 , the problem is was on Juniper side it cannot receive vlan
> interface for attachment circuit :))
>
> On Fri, 2007-04-06 at 02:17 +0000, hritter at videotron.ca wrote:
> > Christian,
> >
> > If you want to use EoMPLS xconnect on a SVI (to allow for
> local switching as well) then you need a OSM+/SIP400/SIP600/ES20
> as the core facing interface. Without one of these modules, you
> can only configure the xconnext on a sub-interface or main interface.
> >
> > Hope this helps,
> >
> > ----- Message d'origine -----
> > De: Christian Malo
> > Date: Jeudi, Avril 5, 2007 2:57 pm
> > Objet: [j-nsp] juniper - cisco l2circuit problem
> > À: juniper-nsp at puck.nether.net
> >
> > > I setup a basic l2circuit between a sup720 and an m20.
> > >
> > > Here's the IOS config and output
> > >
> > > interface GigabitEthernet1/2
> > > description blahblah
> > > switchport
> > > switchport trunk encapsulation dot1q
> > > switchport trunk allowed vlan 1,100,127
> > > switchport mode trunk
> > >
> > > interface Vlan100
> > > no ip address
> > > xconnect X.X.Y.110 803 encapsulation mpls
> > >
> > > Local interface: Vl100 up, line protocol up, Eth VLAN 100 up
> > > Destination address: X.X.Y.110, VC ID: 803, VC status: down
> > > Output interface: none, imposed label stack {794085}
> > > Preferred path: not configured
> > > Default path: active
> > > Next hop: Invalid ADDR
> > > Create time: 00:12:29, last status change time: 00:03:35
> > > Signaling protocol: LDP, peer X.X.Y.110:0 up
> > > MPLS VC labels: local 38, remote 794085
> > > Group ID: local 0, remote 0
> > > MTU: local 1500, remote 1500
> > > Remote interface description:
> > > Sequencing: receive disabled, send disabled
> > > VC statistics:
> > > packet totals: receive 0, send 0
> > > byte totals: receive 0, send 0
> > > packet drops: receive 0, send 0
> > >
> > >
> > > JunOS config and output
> > >
> > > unit 518 {
> > > description "blahblah";
> > > encapsulation vlan-ccc;
> > > vlan-id 518;
> > > }
> > >
> > > neighbor X.X.Y.125 {
> > > interface ge-0/3/0.518 {
> > > virtual-circuit-id 803;
> > > description "blahblah";
> > > no-control-word;
> > > }
> > > }
> > >
> > > Interface Type St Time last up
> > > # Up trans
> > > ge-0/3/0.518(vc 803) rmt Up Apr 5 14:39:41 2007
> > > 1
> > > Local interface: ge-0/3/0.518, Status: Up, Encapsulation: VLAN
> > > Remote PE: X.X.Y.125, Negotiated control-word: No
> > > Incoming label: 794085, Outgoing label: 38
> > > Time Event
> > > Interface/Lbl/PE Apr 5 14:39:41 2007 status update timer
> > > Apr 5 14:39:39 2007 PE route changed
> > > Apr 5 14:39:39 2007 Out lbl Update
> > > 38
> > > Apr 5 14:39:39 2007 In lbl Update
> > > 794085 Apr 5 14:39:39 2007 loc intf up
> > > ge-0/3/0.518
> > >
> > >
> > >
> > > LDP session comes up ... it works with ethernet-vlan
> > > configurations but
> > > the second I try on vlan interfaces, I get that
> > >
> > >
> > >
> > > thanks for the help.
> > >
> > >
> > > -chris
> > > _______________________________________________
> > > juniper-nsp mailing list juniper-nsp at puck.nether.net
> > > https://puck.nether.net/mailman/listinfo/juniper-nsp
> > >
> > _______________________________________________
> > juniper-nsp mailing list juniper-nsp at puck.nether.net
> > https://puck.nether.net/mailman/listinfo/juniper-nsp
>
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>
More information about the juniper-nsp
mailing list