Hi,
I think Jacob is right; the problem arose because you had used tcc encap. You
can see my attached files. Hope it useful for you.
Regards,
Muhammad Teguh Pribadi
"Bourgeois, Jacob (Jake)** CTR **" <[EMAIL PROTECTED]> wrote:
Hi,
Your use of tcc encaps on the interfaces is probably the issue. Since
you've told l2vpn that your encaps is for vlan, you should be using vlan-ccc
for interface encaps. TCC is usually used for FR to ATM, ATM to Eth, etc.
I could be wrong here but give it a shot.
LDP vs RSVP tunnels. L2vpn is kompella, so mp-bgp is setting up parameters
on control plane, should just use any tunnel as long as there is an entry in
inet.3 for the remote pe router-id, regardless of signaling used.
HTHs
Jake Bourgeois
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Telmo Javier Di
Leva
Sent: Wednesday, February 07, 2007 2:32 PM
To: [email protected]
Subject: [j-nsp] L2VPN config sample!
Dears all....
I'm contacting you, because, we are trying to configure an L2VPN on a JM20.
Basically the configuration is the following:
Pe2> show configuration routing-instances L2VPN
instance-type l2vpn;
interface ge-1/1/0.195;
route-distinguisher 18747:5555555555;
vrf-target target:18747:5555555555;
protocols {
l2vpn {
encapsulation-type ethernet-vlan;
site US {
site-identifier 2;
interface ge-1/1/0.195 {
remote-site-id 1;
}
}
}
}
JM20x2>
Pe1> show configuration routing-instances L2VPN
instance-type l2vpn;
interface ge-0/2/0.195;
route-distinguisher 18747:5555555555;
vrf-target target:18747:5555555555;
protocols {
l2vpn {
traceoptions {
file VPLS.log;
flag all;
}
encapsulation-type ethernet-vlan;
site AR {
site-identifier 1;
interface ge-0/2/0.195 {
remote-site-id 2;
}
}
}
}
The encapsulation for the interfaces are TCC:
> show configuration interfaces ge-0/2/0.195
encapsulation vlan-tcc;
vlan-id 195;
In both routers the BGP configuration have family l2vpn unicast whit
junos 7.0R2.7.
In addition between every router we have 2 packet over sonet interfaces
stm1, and the route table for l2vpn is the following:
Pe1> show route table l2vpn
L2VPN.l2vpn.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)
Restart Complete
+ = Active Route, - = Last Active, * = Both
18747:4294967295:1:1/96
*[L2VPN/7] 00:17:20
Discard
Pe2>> show route table L2VPN
L2VPN.l2vpn.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
18747:4294967295:2:1/96
*[L2VPN/7] 00:17:57
Discard
Can sombody help me? whats wrong in the configuration?
All examples on Juniper Site use TE whit RSVP, and we are using LDP to
exchange labels.
Best Regards.
_______________________________________________
juniper-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/juniper-nsp
_______________________________________________
juniper-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/juniper-nsp
---------------------------------
Never miss an email again!
Yahoo! Toolbar alerts you the instant new Mail arrives. Check it out.[EMAIL PROTECTED] show |no-more
version 8.0R2.8;
system {
host-name PE1;
root-authentication {
encrypted-password "$1$W0fMH2sY$0IcZSuNoZ.C/D9bT2MOaZ0"; ## SECRET-DATA
}
login {
user lab {
uid 1000;
class super-user;
authentication {
encrypted-password "$1$pNct5zLJ$qH3NVNErnIJaKLhJajerA/"; ##
SECRET-DATA
}
}
}
services {
telnet;
}
syslog {
user * {
any emergency;
}
file messages {
any notice;
authorization info;
}
}
}
interfaces {
ge-1/0/0 {
vlan-tagging;
encapsulation vlan-ccc;
unit 0 {
encapsulation vlan-ccc;
vlan-id 520;
}
}
so-1/1/0 {
unit 0 {
family inet {
address 10.10.10.1/30;
}
family mpls;
}
}
lo0 {
unit 0 {
family inet {
address 1.1.1.1/32;
}
}
}
}
routing-options {
router-id 1.1.1.1;
autonomous-system 65000;
}
protocols {
mpls {
interface so-1/1/0.0;
}
bgp {
group IBGP {
type internal;
neighbor 2.2.2.2 {
local-address 1.1.1.1;
family l2vpn {
signaling;
}
}
}
}
ospf {
area 0.0.0.0 {
interface lo0.0;
interface so-1/1/0.0;
}
}
ldp {
interface so-1/1/0.0;
interface lo0.0;
}
}
routing-instances {
Test {
instance-type l2vpn;
interface ge-1/0/0.0;
route-distinguisher 65000:1;
vrf-target target:65000:1;
protocols {
l2vpn {
encapsulation-type ethernet-vlan;
no-control-word;
site SATU {
site-identifier 1;
interface ge-1/0/0.0 {
remote-site-id 2;
}
}
}
}
}
}
[edit]
[EMAIL PROTECTED] show l2vpn
^
syntax error.
[EMAIL PROTECTED] run show l2vpn connections extensive
Layer-2 VPN connections:
Legend for connection status (St)
EI -- encapsulation invalid NC -- interface encapsulation not CCC/TCC/VPLS
EM -- encapsulation mismatch WE -- interface and instance encaps not same
VC-Dn -- Virtual circuit down NP -- interface hardware not present
CM -- control-word mismatch -> -- only outbound connection is up
CN -- circuit not provisioned <- -- only inbound connection is up
OR -- out of range Up -- operational
OL -- no outgoing label Dn -- down
LD -- local site signaled down CF -- call admission control failure
RD -- remote site signaled down SC -- local and remote site ID collision
LN -- local site not designated LM -- local site ID not minimum designated
RN -- remote site not designated RM -- remote site ID not minimum designated
XX -- unknown connection status IL -- no incoming label
Legend for interface status
Up -- operational
Dn -- down
Instance: Test
Local site: SATU (1)
Number of local interfaces: 1
Number of local interfaces up: 1
ge-1/0/0.0 2
800000 1 2 100
status-vector: 80
connection-site Type St Time last up # Up trans
2 rmt Up Jan 30 09:45:22 2007 1
Local interface: ge-1/0/0.0, Status: Up, Encapsulation: VLAN
Remote PE: 2.2.2.2, Negotiated control-word: No
Incoming label: 800001, Outgoing label: 800000
Time Event Interface/Lbl/PE
Jan 30 09:45:22 2007 status update timer
Jan 30 09:45:21 2007 PE route changed
Jan 30 09:45:21 2007 Out lbl Update 800000
Jan 30 09:45:21 2007 In lbl Update 800001
Jan 30 09:45:21 2007 loc intf up ge-1/0/0.0
[edit]
[EMAIL PROTECTED]
[edit]
[EMAIL PROTECTED] quit
Exiting configuration mode
[EMAIL PROTECTED] show | no-more
version 7.6R2.6;
system {
host-name PE2;
root-authentication {
encrypted-password "$1$W0fMH2sY$0IcZSuNoZ.C/D9bT2MOaZ0"; ## SECRET-DATA
}
login {
user lab {
uid 1000;
class super-user;
authentication {
encrypted-password "$1$pNct5zLJ$qH3NVNErnIJaKLhJajerA/"; ##
SECRET-DATA
}
}
}
services {
telnet;
}
syslog {
user * {
any emergency;
}
file messages {
any notice;
authorization info;
}
}
}
interfaces {
fe-0/3/0 {
vlan-tagging;
encapsulation vlan-ccc;
unit 0 {
encapsulation vlan-ccc;
vlan-id 520;
}
}
so-1/3/0 {
unit 0 {
family inet {
address 10.10.10.2/30;
}
family mpls;
}
}
lo0 {
unit 0 {
family inet {
address 2.2.2.2/32;
}
}
}
}
routing-options {
router-id 2.2.2.2;
autonomous-system 65000;
}
protocols {
mpls {
interface so-1/3/0.0;
}
bgp {
group IBGP {
type internal;
neighbor 1.1.1.1 {
local-address 2.2.2.2;
family l2vpn {
signaling;
}
}
}
}
ospf {
area 0.0.0.0 {
interface lo0.0;
interface so-1/3/0.0;
}
}
ldp {
interface so-1/3/0.0;
interface lo0.0;
}
}
routing-instances {
Test {
instance-type l2vpn;
interface fe-0/3/0.0;
route-distinguisher 65000:1;
vrf-target target:65000:1;
protocols {
l2vpn {
encapsulation-type ethernet-vlan;
no-control-word;
site DUA {
site-identifier 2;
interface fe-0/3/0.0 {
remote-site-id 1;
}
}
}
}
}
}
[edit]
[EMAIL PROTECTED] show l2vp
^
syntax error.
[EMAIL PROTECTED] run show l2vpn connections ?
Possible completions:
<[Enter]> Execute this command
brief Display one-line version of output
down Display nonoperational connections
extensive Display connection status and history
history Display connection history
instance Name of Layer 2 VPN instance
local-site Name or ID of Layer 2 VPN local site
logical-router Name of logical router, or 'all'
remote-site ID of Layer 2 VPN remote site
status Display connection and circuit status (default)
summary Display summary output
up Display operational connections
up-down Display both non- and operational connections (default)
| Pipe through a command
[edit]
[EMAIL PROTECTED] run show l2vpn connections extensive
Layer-2 VPN connections:
Legend for connection status (St)
EI -- encapsulation invalid NC -- interface encapsulation not CCC/TCC/VPLS
EM -- encapsulation mismatch WE -- interface and instance encaps not same
VC-Dn -- Virtual circuit down NP -- interface hardware not present
CM -- control-word mismatch -> -- only outbound connection is up
CN -- circuit not provisioned <- -- only inbound connection is up
OR -- out of range Up -- operational
OL -- no outgoing label Dn -- down
LD -- local site signaled down CF -- call admission control failure
RD -- remote site signaled down SC -- local and remote site ID collision
LN -- local site not designated LM -- local site ID not minimum designated
RN -- remote site not designated RM -- remote site ID not minimum designated
XX -- unknown connection status IL -- no incoming label
Legend for interface status
Up -- operational
Dn -- down
Instance: Test
Local site: DUA (2)
Number of local interfaces: 1
Number of local interfaces up: 1
fe-0/3/0.0 1
800000 1 1 100
status-vector: 0
connection-site Type St Time last up # Up trans
1 rmt Up Jan 30 09:45:12 2007 1
Local interface: fe-0/3/0.0, Status: Up, Encapsulation: VLAN
Remote PE: 1.1.1.1, Negotiated control-word: No
Incoming label: 800000, Outgoing label: 800001
Time Event Interface/Lbl/PE
Jan 30 09:45:12 2007 status update timer
Jan 30 09:45:10 2007 PE route changed
Jan 30 09:45:10 2007 Out lbl Update 800001
Jan 30 09:45:10 2007 In lbl Update 800000
Jan 30 09:45:10 2007 loc intf up fe-0/3/0.0
[edit]
[EMAIL PROTECTED] quit
Exiting configuration mode
_______________________________________________
juniper-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/juniper-nsp
