VPLS is not supporting LDP for J-series at this time. Please use BGP
signaling for VPLS on J-series in 9.4-9.5.
Kind regards,
Truman Boyes
On 23/07/2009, at 7:46 AM, Tomasz Klicki wrote:
Hi there,
I'm trying to configure VPLS between two J2320 routers (Junos
9.5R2.7).
Topology looks like this:
PC1 (tagged vlan) --- J1 --- J2 --- J3 --- J4 --- PC2 (tagged vlan)
..but as you may presume not everything works correct.
Output from 'show vpls connections' on J1:
r...@j1> show vpls connections
Instance: vpls1
VPLS-id: 100
Neighbor Type St Time last up # Up
trans
192.168.5.4(vpls-id 100) rmt Up Jul 23 19:17:06
2009 1
Remote PE: 192.168.5.4, Negotiated control-word: No
Incoming label: 262145, Outgoing label: 262145
Local interface: lsi.1049344, Status: Up, Encapsulation: ETHERNET
Description: Intf - vpls vpls1 neighbor 192.168.5.4 vpls-id 100
Looks good, but no packet is passing from PC1 to PC2. Can anyone
tell me
what I do wrong? I'm not sure about configuration of encapsulation of
access ports for PC1 and PC2. Interface lsi.1049344 also looks strange
to me, it has no input/output packets:
r...@j1> show interfaces lsi.1049344
Logical interface lsi.1049344 (Index 73) (SNMP ifIndex 156)
Flags: Point-To-Point SNMP-Traps Encapsulation: LSI-NULL
Input packets : 0
Output packets: 0
Security: Zone: trust
Allowed host-inbound traffic : any-service bfd bgp dlsw dvmrp igmp
ldp msdp
nhrp ospf pgm pim rip router-discovery rsvp sap vrrp
Protocol vpls, MTU: 1496
Flags: None
========= Essential configuration from J1 =========
protocols {
rsvp {
interface ge-0/0/0.0;
interface ge-0/0/1.0;
}
mpls {
label-switched-path J1-to-J4 {
to 192.168.5.4;
no-cspf;
}
interface ge-0/0/0.0;
interface ge-0/0/1.0;
}
ospf {
traffic-engineering;
area 0.0.0.0 {
interface ge-0/0/0.0;
interface ge-0/0/1.0;
interface lo0.0;
}
}
ldp {
transport-address router-id;
interface ge-0/0/0.0;
interface ge-0/0/1.0;
interface lo0.0;
}
}
routing-instances {
vpls1 {
instance-type vpls;
interface ge-0/0/2.0;
protocols {
vpls {
no-tunnel-services;
vpls-id 100;
neighbor 192.168.5.4;
}
}
}
}
interfaces {
[...]
ge-0/0/2 {
description Access-port for PC1;
vlan-tagging;
encapsulation vlan-vpls;
unit 0 {
encapsulation vlan-vpls;
vlan-id 600;
}
}
lo0 {
unit 0 {
family inet {
address 192.168.5.1/32;
}
}
}
}
========= Essential configuration from J4 =========
interfaces {
[...]
ge-0/0/2 {
description Access-port for PC2;
vlan-tagging;
encapsulation vlan-vpls;
unit 0 {
encapsulation vlan-vpls;
vlan-id 600;
}
}
lo0 {
unit 0 {
family inet {
address 192.168.5.4/32;
}
}
}
}
routing-options {
static {
route 0.0.0.0/0 next-hop 213.135.51.1;
}
router-id 192.168.5.4;
}
protocols {
rsvp {
interface ge-0/0/0.0;
interface ge-0/0/1.0;
}
mpls {
label-switched-path J4-to-J1 {
to 192.168.5.1;
no-cspf;
}
interface ge-0/0/0.0;
interface ge-0/0/1.0;
}
ospf {
traffic-engineering;
area 0.0.0.0 {
interface ge-0/0/0.0;
interface ge-0/0/1.0;
interface lo0.0;
}
}
ldp {
transport-address router-id;
interface ge-0/0/0.0;
interface ge-0/0/1.0;
interface lo0.0;
}
}
routing-instances {
vpls1 {
instance-type vpls;
interface ge-0/0/2.0;
protocols {
vpls {
no-tunnel-services;
vpls-id 100;
neighbor 192.168.5.1;
}
}
}
}
--
(o_ Best regards,
//\ Tomasz Klicki
V_/_
_______________________________________________
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
