[j-nsp] Problem to test VPLS between two Site
Hi ,
Wishes all are fine.
I am getting problem about testing of VPLS service (BGP and LDP based )
between two router and my VPLS tunnel is up but i can not reach local LAN.
i am little bit confused about testing between PC. May i need to connect direct
PC on ge-1/1/9 for test or need to connect switch or router on both router's
ge-1/1/9 interface for test ?
it would be nice please check my bellow configuration for further assistance
and how test my VPLS in both end ?
Here my Configuration:
## AGG-Router-1
ge-1/1/0 {
description with_MX-_ge-1/1/0;
unit 0 {
family inet {
address 103.x.x.33/30; /// p2p between two router
}
family mpls;
}
ge-1/1/9 {
encapsulation ethernet-vpls; // At present Local PC for test
unit 0 {
family vpls;
}
protocols {
mpls {
interface all;
}
routing-options {
rib inet.3 {
static {
route 103.x.x.34/32 next-table inet.0;
}
}
autonomous-system 58xxx;
}
group vpls-ge {
type internal;
local-address 103.x.x.33;
family l2vpn {
signaling;
}
neighbor 103.x.x.34;
}
ldp {
interface ge-1/1/0.0;
interface lo0.0;
}
community grn-com members target:1:1;
routing-instances {
green {
instance-type vpls;
interface ge-1/1/9.0;
route-distinguisher 103.x.x.33:33;
vrf-target target:1:1;
protocols {
vpls {
site-range 10;
no-tunnel-services;
site greenPE1 {
site-identifier 1;
}
}
}
}
}
## AGG-Router-2 ##
ge-1/1/0 {
description with_MX_ge-1/1/0;
unit 0 {
family inet {
address 103.x.x.34/30; /// p2p between two router
}
family mpls;
}
ge-1/1/9 {
encapsulation ethernet-vpls; // At present Local PC for test
unit 0 {
family vpls;
}
routing-options {
rib inet.3 {
static {
route 103.x.x.33/32 next-table inet.0;
}
}
autonomous-system 58xxx;
}
protocols {
mpls {
interface all;
}
group vpls-ge {
type internal;
local-address 103.x.x.34;
family l2vpn {
signaling;
}
neighbor 103.x.x.33;
}
ldp {
interface ge-1/1/0.0;
interface lo0.0;
}
}
community grn-com members target:1:1;
}
routing-instances {
green {
instance-type vpls;
interface ge-1/1/9.0;
route-distinguisher 103.x.x.34:34;
vrf-target target:1:1;
protocols {
vpls {
site-range 10;
no-tunnel-services;
site greenPE2 {
site-identifier 2;
}
}
}
}
}
Agg-Router-1 # show vpls connections
Instance: green
Local site: greenPE1 (1)
connection-site Type St Time last up # Up trans
2 rmt Up Jul 16 09:11:31 2013 1
Remote PE: 103.x.x.34, Negotiated control-word: No
Incoming label: 89, Outgoing label: 800016
Local interface: vt-1/0/10.1049858, Status: Up, Encapsulation: VPLS
Description: Intf - vpls green local site 1 remote site 2
AGG-01# run show interfaces vt* terse
Interface Admin Link Proto Local Remote
vt-1/0/10 up up
vt-1/1/10 up up
vt-1/1/10.1048832 up up vpls
AGG-01 # run show vpls statistics
VPLS statistics:
Instance: green
Local interface: ge-1/1/9.0, Index: 333
Broadcast packets: 1101
Broadcast bytes : 83916
Multicast packets: 1278
Multicast bytes : 111627
Flooded packets : 0
Flooded bytes : 0
Unicast packets : 0
Unicast bytes : 0
Current MAC count: 1 (Limit 1024)
Local interface: vt-1/1/10.1049090, Index: 334
Remote PE: 103.x.x.34
Broadcast packets: 0
Broadcast bytes : 0
Multicast packets: 0
Multicast bytes : 0
Flooded packets : 0
Flooded bytes : 0
Unicast packets : 0
Unicast bytes : 0
Current MAC count: 0
it would be nice please suggest based on this config how to test this layer 2
vpn using PC?
Regards
Jahangir Hossain
Re: [j-nsp] R: RE : multicast issue
- Original Message - From: david@orange.com To: dim0sal dim0...@hotmail.com Cc: juniper-nsp@puck.nether.net Sent: Tuesday, July 16, 2013 8:49 PM Subject: Re: [j-nsp] R: RE : multicast issue If you can't start/stop manually mcast streams you will never have stable counters and can't detect packet loss. This is not exactly true. What You can do with constantly running streams is to have a FW filter with specific term matching on chosen stream IP headers+count action, on both headend (HE) and tailend (TE). Then activate/deactivate this term as required. You have to have both HE and TE synced via common NTP source and perform commits at precise times (commit at if You do it manually). Assuming headend and tailed are same router models and You have no network loss, You MAY get some minuscule counter difference between HE/TE because time spent by Routing Engine doing commit slightly varies. What would be more important is to monitor whether this difference changes with time which indicates packet loss. HTH Thanks Alex ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] srx210 interesting difficulty with managed layer 3 setup .
Hello Georgios , Thank you . THis information is quite helpful . Twyl , JimL On Tue, 16 Jul 2013, Georgios Vlachos wrote: You have two options actually: L2circuit (Martini circuit) or VPLS (BGP based) over MPLS over GRE over IPsec! p.s. watch out for fragmentation issues due to the encapsulation overhead. -- +--+ | James W. Laferriere | SystemTechniques | Give me VMS | | NetworkSystem Engineer | 3237 Holden Road | Give me Linux | | bab...@baby-dragons.com | Fairbanks, AK. 99709 | only on AXP | +--+ ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
[j-nsp] replacing M5 RE-3.0 hard drive
I have a Juniper M5 whose hard drive just failed. The drive appears to be a Fujitsu MHT2030AT. Can I just simply swap in a new hard drive and partition it? Has anyone tried replacing it with a solid state equivalent and if so, what did you use? Antonio Querubin e-mail: t...@lavanauts.org xmpp: antonioqueru...@gmail.com ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] replacing M5 RE-3.0 hard drive
Yes, just make sure to use a 2,5 drive. SSD is fine, too. http://juniper.cluepon.net/index.php/Replacing_the_harddisk_with_solid_state_flash Am Mittwoch, den 17.07.2013, 09:42 -1000 schrieb Antonio Querubin: I have a Juniper M5 whose hard drive just failed. The drive appears to be a Fujitsu MHT2030AT. Can I just simply swap in a new hard drive and partition it? Has anyone tried replacing it with a solid state equivalent and if so, what did you use? Antonio Querubin e-mail: t...@lavanauts.org xmpp: antonioqueru...@gmail.com ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp signature.asc Description: This is a digitally signed message part ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] Problem to test VPLS between two Site
IIRC unless you disable local switching you need to add the interface to
the site config as well as to the instance.
On 7/17/13 1:30 AM, Md. Jahangir Hossain wrote:
Hi ,
Wishes all are fine.
I am getting problem about testing of VPLS service (BGP and LDP based )
between two router and my VPLS tunnel is up but i can not reach local LAN.
i am little bit confused about testing between PC. May i need to connect
direct PC on ge-1/1/9 for test or need to connect switch or router on both
router's ge-1/1/9 interface for test ?
it would be nice please check my bellow configuration for further assistance
and how test my VPLS in both end ?
Here my Configuration:
## AGG-Router-1
ge-1/1/0 {
description with_MX-_ge-1/1/0;
unit 0 {
family inet {
address 103.x.x.33/30;/// p2p between two router
}
family mpls;
}
ge-1/1/9 {
encapsulation ethernet-vpls; // At present Local PC for test
unit 0 {
family vpls;
}
protocols {
mpls {
interface all;
}
routing-options {
rib inet.3 {
static {
route 103.x.x.34/32 next-table inet.0;
}
}
autonomous-system 58xxx;
}
group vpls-ge {
type internal;
local-address 103.x.x.33;
family l2vpn {
signaling;
}
neighbor 103.x.x.34;
}
ldp {
interface ge-1/1/0.0;
interface lo0.0;
}
community grn-com members target:1:1;
routing-instances {
green {
instance-type vpls;
interface ge-1/1/9.0;
route-distinguisher 103.x.x.33:33;
vrf-target target:1:1;
protocols {
vpls {
site-range 10;
no-tunnel-services;
site greenPE1 {
site-identifier 1;
}
}
}
}
}
## AGG-Router-2 ##
ge-1/1/0 {
description with_MX_ge-1/1/0;
unit 0 {
family inet {
address 103.x.x.34/30; /// p2p between two router
}
family mpls;
}
ge-1/1/9 {
encapsulation ethernet-vpls; // At present Local PC for test
unit 0 {
family vpls;
}
routing-options {
rib inet.3 {
static {
route 103.x.x.33/32 next-table inet.0;
}
}
autonomous-system 58xxx;
}
protocols {
mpls {
interface all;
}
group vpls-ge {
type internal;
local-address 103.x.x.34;
family l2vpn {
signaling;
}
neighbor 103.x.x.33;
}
ldp {
interface ge-1/1/0.0;
interface lo0.0;
}
}
community grn-com members target:1:1;
}
routing-instances {
green {
instance-type vpls;
interface ge-1/1/9.0;
route-distinguisher 103.x.x.34:34;
vrf-target target:1:1;
protocols {
vpls {
site-range 10;
no-tunnel-services;
site greenPE2 {
site-identifier 2;
}
}
}
}
}
Agg-Router-1 # show vpls connections
Instance: green
Local site: greenPE1 (1)
connection-site Type St Time last up # Up trans
2 rmt Up Jul 16 09:11:31 2013 1
Remote PE: 103.x.x.34, Negotiated control-word: No
Incoming label: 89, Outgoing label: 800016
Local interface: vt-1/0/10.1049858, Status: Up, Encapsulation: VPLS
Description: Intf - vpls green local site 1 remote site 2
AGG-01# run show interfaces vt* terse
Interface Admin Link ProtoLocal Remote
vt-1/0/10 upup
vt-1/1/10 upup
vt-1/1/10.1048832 upup vpls
AGG-01 # run show vpls statistics
VPLS statistics:
Instance: green
Local interface: ge-1/1/9.0, Index: 333
Broadcast packets: 1101
Broadcast bytes : 83916
Multicast packets: 1278
Multicast bytes :111627
Flooded packets : 0
Flooded bytes: 0
Unicast packets : 0
Unicast bytes: 0
Current MAC count: 1 (Limit 1024)
Local interface: vt-1/1/10.1049090, Index: 334
Remote PE: 103.x.x.34
Broadcast packets: 0
Broadcast bytes : 0
Multicast packets: 0
Multicast bytes : 0
Flooded packets :
