No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>

Reminder

To have a better experience, please upgrade your IE browser.

upgrade
MENU

l2vc between NE40E and Juniper is not established due to no ldp session

Publication Date:  2013-10-28 Views:  12 Downloads:  0
Issue Description
Problem was that l2vc did not established between NE40E
and J device in interAS mode of PWE3 L2VPN technology
. Customer tried
tagged and raw mode. Software version of NE40E is V600R003SPH003.
On NE40E we could see:
<Ne40E-PE2-NNov>dis mpls l2vc  291
 Total LDP VC : 1     0 up       1 down
  *client interface     : GigabitEthernet1/1/0.291
  Administrator PW     : no
  session state        : down
  AC status            : up
  VC state             : down
  Label state          : 0
  Token state          : 0
  VC ID                : 291
  VC type              : VLAN
  destination          : 83.x.x.x
  local VC label       : 7406         remote VC label      : 0
  control word         : disable
 
forwarding entry     : not exist

  local group ID       : 0
  manual fault         : not set
  active state         : inactive
  link state           : down
 
local VC MTU         : 1500         remote VC MTU        : 0

 
tunnel policy name   : --

  PW template name     : --
 
primary or secondary : primary

  load balance type    : flow
  Access-port          : false
  create time          : 0 days, 0 hours, 11 minutes, 45 seconds
  up time              : 0 days, 0 hours, 0 minutes, 0 seconds
  last change time     : 0 days, 0 hours, 11 minutes, 45 seconds
  VC last up time      : 0000/00/00 00:00:00
  VC total up time     : 0 days, 0 hours, 0 minutes, 0 seconds
  CKey                 : 516
  NKey                 : 618
  AdminPw interface    : --
  AdminPw link state   : --
  Diffserv Mode        : uniform
  Service Class        : --
  Color                : --
  DomainId             : --
  Domain Name          : --
<Ne40E-PE2-NNov>dis mpls l2vc 291
 Total LDP VC : 1     0 up       1 down
 
 *client interface     : GigabitEthernet1/1/0.291
  Administrator PW     : no
 
session state        : down

  AC status            : up
  VC state             : down
  Label state          : 0
  Token state          : 0
  VC ID                : 291
  VC type              : VLAN
  destination          : 83.x.x.x
  local VC label       : 7406         remote VC label      : 0
  control word         : disable
 
forwarding entry     : not exist

  local group ID       : 0
  manual fault         : not set
  active state         : inactive
  link state           : down
 
local VC MTU         : 1500         remote VC MTU        : 0

 
tunnel policy name   : --

  PW template name     : --
 
primary or secondary : primary

  load balance type    : flow
  Access-port          : false
  create time          : 0 days, 0 hours, 11 minutes, 45 seconds
  up time              : 0 days, 0 hours, 0 minutes, 0 seconds
  last change time     : 0 days, 0 hours, 11 minutes, 45 seconds
  VC last up time      : 0000/00/00 00:00:00
  VC total up time     : 0 days, 0 hours, 0 minutes, 0 seconds
  CKey                 : 516
  NKey                 : 618
  AdminPw interface    : --
  AdminPw link state   : --
  Diffserv Mode        : uniform
  Service Class        : --
  Color                : --
  DomainId             : --
  Domain Name          : --

From J device output was like below:
nnov-d1-hq_re0> show l2circuit connections neighbor 10.152.135.2
Layer-2 Circuit Connections:
 
Legend for connection status (St)
EI -- encapsulation invalid      NP -- interface h/w not present
MM -- mtu mismatch               Dn -- down
EM -- encapsulation mismatch     VC-Dn -- Virtual circuit Down
CM -- control-word mismatch      Up --
operational

VM -- vlan id mismatch           CF -- Call admission
control failure

OL -- no outgoing label          XX -- unknown
NC -- intf encaps not CCC/TCC
CB -- rcvd
cell-bundle size bad

 
Legend for interface status
Up -- operational
Dn -- down
Neighbor:
10.152.135.2

    Interface                 Type  St     Time last up          # Up trans
    ge-1/0/0.291(vc 291)      rmt   OL
Handling Process
We analized configs from J device:
neighbor 10.152.135.2
{

    interface ge-1/0/0.291 {
       
virtual-circuit-id 291;

        mtu 1500;
   
}

}
>show configuration interfaces
ge-1/0/0.291

description "test xconnect";
encapsulation
vlan-ccc;

vlan-id 291;



 and NE40E:
mpls l2vpn
  mpls l2vpn no-request-message
peer 83.x.x.x

 
interface
GigabitEthernet1/1/0.291

 vlan-type dot1q 291
 description **MPLS L2VC TEST TO XXX**
 mpls l2vc 83.x.x.x 291

<Ne40E-PE2-NNov>dis mpls l2vc 291
 Total LDP VC : 1     0 up       1 down
 
 *client interface     : GigabitEthernet1/1/0.291
  Administrator PW     : no
  session state        : down
  AC status            : up
  VC state             : down
  Label state          : 0
  Token state          : 0
  VC ID                : 291
  VC type              : VLAN
  destination          : 83.x.x.x
  local VC label       : 7406         remote VC label      : 0
  control word         : disable
  forwarding entry     : not exist
  local group ID       : 0
  manual fault         : not set
  active state         : inactive
  link state           : down
  local VC MTU         : 1500         remote VC MTU        : 0
  tunnel policy name   : --
  PW template name     : --
  primary or secondary : primary
  load balance type    : flow
  Access-port          : false
  create time          : 0 days, 0 hours, 11 minutes, 45 seconds
  up time              : 0 days, 0 hours, 0 minutes, 0 seconds
  last change time     : 0 days, 0 hours, 11 minutes, 45 seconds
  VC last up time      : 0000/00/00 00:00:00
  VC total up time     : 0 days, 0 hours, 0 minutes, 0 seconds
  CKey                 : 516
  NKey                 : 618
  AdminPw interface    : --
  AdminPw link state   : --
  Diffserv Mode        : uniform
  Service Class        : --
  Color                : --
  DomainId             : --
  Domain Name          : --

We can see that there is no any remote PE VC information.
Martini L2VPN need mpls remote seesion to negotiate the VC information, so we think some configuration was missed.
Root Cause
There is no remote ldp session in config of NE40E, related to J device:
mpls l2vpn
#
mpls
ldp
#
#
 mpls ldp remote-peer ne40e-bryansk-1
 remote-ip
10.132.135.1
#
 mpls ldp remote-peer ne40e-bryansk-2
 remote-ip
10.132.135.2
#
 mpls ldp remote-peer ne40e-kaluga-1
 remote-ip
10.140.135.1
...........................................................
Solution
After we add  
mpls ldp remote-peer J device
remote-ip
83.x.x.x


in configuration, LDP session was going to Operational state

<Ne40E-PE2-NNov>dis mpls ldp session
 
 LDP Session(s) in Public Network 
Codes: LAM(Label Advertisement Mode), SsnAge Unit(DDDD:HH:MM)
 
A '*' before a session means the session is being deleted.

 ------------------------------------------------------------------------------
 PeerID           Status      LAM  SsnRole  SsnAge      KASent/Rcv
 ------------------------------------------------------------------------------
 83.x.x.x:0     Operational DU   Active   0007:10:14  42778/42778

and l2vc was UP:

<Ne40E-PE2-NNov>dis mpls l2vc 291
 Total LDP VC : 1     0 up       1 down
 
 *client interface     : GigabitEthernet1/1/0.291
  Administrator PW     : no
  session state        : up
  AC status            : up
 
VC state             : up
  Label state          : 0
  Token state          : 0
  VC ID                : 291
  VC type              : vlan
 
destination          : 83.x.x.x

So, problem was resolved.
Suggestions
Check all milestones of L2VPN connection sequentially, so, you could fast find
root cause.

END