[j-nsp] L2VPN debugging...

Hoogen hoogen82 at gmail.com
Mon Feb 15 12:30:16 EST 2010


Hi Nilesh,

I do have that configuration on all routers. I actually do have another
L3VPN configured between the same routers R4 and R6 which is working fine..

[edit]
lab at r4# run show bgp summary
Groups: 3 Peers: 5 Down peers: 0
Table          Tot Paths  Act Paths Suppressed    History Damp State
 Pending
inet.0                 0          0          0          0          0
 0
bgp.l3vpn.0           35         35          0          0          0
 0
bgp.l2vpn.0            1          1          0          0          0
 0
Peer               AS      InPkt     OutPkt    OutQ   Flaps Last Up/Dwn
State|#Active/Received/Damped...
172.16.0.6      65010       4318       4431       0       1    20:41:58
Establ
  vpna-1.inet.0: 11/11/0
10.0.2.9        65001       2924       2947       0       1    20:40:08
Establ
  inet.0: 0/0/0
  bgp.l3vpn.0: 24/24/0
*  vpna-1.inet.0: 12/12/0 <--- vpna is a L3 VPN routes that I receive from
R5..Customer is able to see all these routes.*
  bgp.l2vpn.0: 1/1/0
*  vpnc-1.l2vpn.0: 1/1/0 <-- vpnc routes that I receive from R5..*
10.0.3.3        65000       5417       5408       0       0  1d 8:31:44
Establ
  inet.0: 0/0/0
10.0.6.1        65000       4318       5409       0       0  1d 8:31:37
Establ
  inet.0: 0/0/0
10.0.6.2        65000       4319       5409       0       0  1d 8:31:33
Establ
  inet.0: 0/0/0

[edit]
lab at r4#

Hi Phil
These are the route table output

lab at r4# run show route table vpnc

vpnc-1.l2vpn.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

10.0.3.4:1:1:1/96
                   *[L2VPN/170/-101] 17:12:27, metric2 1
                      Indirect
*10.0.9.6:2:2:1/96                <---------Receiving the R6 loopback..*
                   *[BGP/170] 00:06:18, localpref 100, from 10.0.2.9
                      AS path: (65001) I
                    > via t1-2/0/0.0, label-switched-path r4-r6

[edit]
lab at r4#

lab at r6# run show route table vpnc

vpnc-1.l2vpn.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

*10.0.3.4:1:1:1/96                <--------Receiving the R4 loopback.. *
                   *[BGP/170] 00:07:30, localpref 100, from 10.0.3.5
                      AS path: (65000) I
                    > to 10.0.8.6 via ge-0/0/2.0
10.0.9.6:2:2:1/96
                   *[L2VPN/170/-101] 11:24:44, metric2 1
                      Indirect

[edit]
lab at r6#


Hi Aditya,

Yeah I was trying to see all the traces I can get by turning on and off the
vpnc instance. But I couldn't comprehend why the vpn doesn't come up.. To me
it looks like the control plane is up but the data plane is down...:(

lab at r4# run show l2vpn connections
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: vpnc-1
Local site: c1 (1)
    connection-site           Type  St     Time last up          # Up trans
    2                         rmt   VC-Dn  -----                          0
      Local interface: ge-0/0/2.600, Status: Up, Encapsulation: VLAN
      Remote PE: 10.0.9.6, Negotiated control-word: Yes (Null)
      Incoming label: 800003, Outgoing label: 800004

[edit]
lab at r4#

Thanks,
Hoogen


More information about the juniper-nsp mailing list