Re: [j-nsp] question regarding multiple interfaces in vpls (vlan-tagswap used)
Simon
Just look at this:
http://www.juniper.net/techpubs/software/junos/junos90/mx-solutions-guide/one-vpls-instance-for-several-vlans.html#id-vpls-many-vlans
One VPLS Instance for Several VLANs
routing-instances {
customer-c1-v1-to-v1000 {
instance-type vpls;
vlan-id all; # Note the use of the VLAN id all statement
interface ge-1/0/0.1;
interface ge-2/0/0.1;
interface ge-3/0/0.1;
I am ot sure that's the solution but perhaps it can help
Regards
Alain
-Message d'origine-
De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] De la part de Simon Chen
Envoyé : mercredi 13 août 2008 06:32
À : Juniper Puck
Objet : [j-nsp] question regarding multiple interfaces in vpls (vlan-tagswap
used)
Hi all,
I am having problems with VPLS again, and would like to ask for your help.
Basically, I have multiple VPLS sites, each sites may host a few interfaces.
The configure looks like this:
interfaces {
ge-0/1/0 {
unit 0 {
encapsulation vlan-vpls;
vlan-id 513;
input-vlan-map pop;
output-vlan-map push;
}
unit 1 {
encapsulation vlan-vpls;
vlan-id 514;
input-vlan-map pop;
output-vlan-map push;
}
}
}
routing-instances {
VPLS.0 {
instance-type vpls;
interface ge-0/1/0.0; // doesn't work when both enabled
interface ge-0/1/0.1;
route-distinguisher :0;
vrf-target target::0;
protocols {
vpls {
site-range 40;
site PE.2 {
site-identifier 2;
}
}
}
}
}
This doesn't work though, unless I only enable one of the interfaces in the
VPLS interface for every site.
Can anyone explain what's going on here and how I can fix it?
Thanks a lot!
-Simon
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] Source Based Routing
From the CLI, use these commands: set vrouter trust-vr set sibr-routing enable set route source in-interface incoming_int 192.168.10.0/24 interface adsl_int gateway adsl_gw exit Where: inside_int is the interface on which the traffic will be received (e.g. ethernet2, trust, bgroup0, etc.) adsl_int is the outbound interface (in this case, it sounds like it will be an ADSL interface adsl_gw is the IP address of the next-hop on the outbound interface (I believe this part may be optional) The above will work if both are in the same VR. Because you have put them in separate VRs, I'm not sure whether that will work. -Jonathan On Wed, Aug 13, 2008 at 5:27 AM, SunnyDay [EMAIL PROTECTED] wrote: Hello I trying to configure source based routing on a ssg140. The ssg has 3 adsl lines 2 adsl cards and one bridged pppoe on an Ethernet. I have put the interfaces to the untrust-vr and local network to the trust-vr with the appropriate zones. I have 4 subnets 192.168.10.1 192.168.20.1 192.168.30.1 192.168.40.1. I have configured a default route to the trust-vr pointing the untrust-vr. At the untrust-vr I have source based routing e.g 192.168.10.0/24 to leave through adsl/1.but this does not seem to work. When I put the source based routing to the rust-vr traffic leaves for adsl/1 but internal traffic goes also. Anyone has worked with similar scenario icould use some help here. Thanks ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
[j-nsp] ERX and framed-ip
Hello All, I'm configuring an ERX310 in the lab for use as an LNS. I got to the point where users are able to connect, however I experience some strange behavior: If the user is assigned an ip address from the local pool then he is able to connect. When I try to assign an ip from the radius (framed-ip- address=100.100.100.1) then the user is unable to connect. Any Idea if I'm missing some configuration to allow allocation of IPs from the radius? 10x Amos Rosenboim [EMAIL PROTECTED] ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
[j-nsp] vpls ping control-plane-response
Does anyone know what control-plane-response in vpls ping cmd mean? VPLS ping in my scenario without that keyword works, but with it, it doesn't. [EMAIL PROTECTED] run ping vpls instance vpls destination-mac 00:00:07:00:00:01 source-ip 1.1.1.1 ! - re-0:vpls:ge-5/0/4.0 ! - re-0:vpls:ge-5/0/4.0 [EMAIL PROTECTED] run ping vpls instance vpls destination-mac 00:00:07:00:00:01 source-ip 1.1.1.1 control-plane-response . Thanks, Marlon ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] vpls ping control-plane-response
read the following kompella draft, i am pretty sure vpls ping operation is covered http://tools.ietf.org/html/draft-stokes-vkompella-l2vpn-vpls-oam-01 On Wed, Aug 13, 2008 at 2:24 PM, Marlon Duksa [EMAIL PROTECTED] wrote: Does anyone know what control-plane-response in vpls ping cmd mean? VPLS ping in my scenario without that keyword works, but with it, it doesn't. [EMAIL PROTECTED] run ping vpls instance vpls destination-mac 00:00:07:00:00:01 source-ip 1.1.1.1 ! - re-0:vpls:ge-5/0/4.0 ! - re-0:vpls:ge-5/0/4.0 [EMAIL PROTECTED] run ping vpls instance vpls destination-mac 00:00:07:00:00:01 source-ip 1.1.1.1 control-plane-response . Thanks, Marlon ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
