cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
6696
Views
5
Helpful
13
Replies

L2VPN EoMPLS status down on ME3600x

Marat Rafikov
Level 1
Level 1

Hi everyone!

we are have a problem with enabling vc on EoMPLS circuit on Cisco ME3600x. all configuration is the same and working, we are checked ping, traceroute, ping mpls ipv4, ping mpls pseudowire, every our trying was clear and well, but when we want to see a status of vc it is still Down. after i was entered the command "sh mpls l2 vc 1517 det"  after that we can see this

KAND_sw1#sh mpls l2 vc 1517 det
Local interface: Vl1517 up, line protocol up, Eth VLAN 1517 down
  Interworking type is Ethernet
  Destination address: 10.70.1.34, VC ID: 1517, VC status: down
    Last error: Local peer access circuit is down
    Output interface: Te0/2, imposed label stack {1126 1052}
    Preferred path: not configured 
    Default path: active
    Next hop: 10.70.2.66
  Create time: 01:06:23, last status change time: 00:00:06
    Last label FSM state change time: 00:26:48
  Signaling protocol: LDP, peer 10.70.1.34:0 up
    Targeted Hello: 10.70.1.2(LDP Id) -> 10.70.1.34, LDP is UP
    Graceful restart: not configured and not enabled
    Non stop routing: not configured and not enabled
    Status TLV support (local/remote)   : enabled/supported
      LDP route watch                   : enabled
      Label/status state machine        : established, LrdRru
      Last local dataplane   status rcvd: No fault
      Last BFD dataplane     status rcvd: Not sent
      Last BFD peer monitor  status rcvd: No fault
      Last local AC  circuit status rcvd: DOWN AC(rx/tx faults)
      Last local AC  circuit status sent: No fault
      Last local PW i/f circ status rcvd: No fault
      Last local LDP TLV     status sent: DOWN AC(rx/tx faults)
      Last remote LDP TLV    status rcvd: No fault
      Last remote LDP ADJ    status rcvd: No fault
    MPLS VC labels: local 1704, remote 1052
    Group ID: local 0, remote 0
    MTU: local 9212, remote 9212
    Remote interface description: SAG_LOIS
  Sequencing: receive disabled, send disabled
  Control Word: On (configured: autosense)
  Dataplane:
    SSM segment/switch IDs: 411116/21853 (used), PWID: 7
  VC statistics:
    transit packet totals: receive 3397, send 0
    transit byte totals:   receive 370620, send 0
    transit packet drops:  receive 0, seq error 0, send 0

can anybody to answer to me, what is the error mean "Last error: Local peer access circuit is down"? i cant find any solution for resolve this error in internet. i think a problem in ME3600x, but i cant understand what i need to do.

we are using Cisco ME3600x-24cx and Cisco ASR901.

please help to me

13 Replies 13

Hello mate !

Please, paste your configurations here.

 

The only thing that brings to my attention is this:   

 

"Last local AC  circuit status rcvd: DOWN AC(rx/tx faults)"

 

Have you checked the health of your local interface ?

 

cheers

hi
can you please tell me what kind of configuration you want to see?
and second, can you please explain to me which local interface i need to check?

"Local interface" - Interface used as the attached circuit, the one towards the LAN

About the configuration, you can paste all things related to the vpls section

 

cheers

in our cisco ME3600x local interface is interface VLAN 1517.

KAND_sw1#sh inter vl 1517
Vlan1517 is up, line protocol is up 
  Hardware is EtherSVI, address is 78da.6ead.7a40 (bia 78da.6ead.7a40)
  MTU 9212 bytes, BW 1000000 Kbit/sec, DLY 10 usec, 
     reliability 255/255, txload 1/255, rxload 1/255
  Encapsulation ARPA, loopback not set
  Keepalive not supported 
  ARP type: ARPA, ARP Timeout 04:00:00
  Last input 00:00:42, output 03:33:43, output hang never
  Last clearing of "show interface" counters never
  Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
  Queueing strategy: fifo
  Output queue: 0/40 (size/max)
  5 minute input rate 0 bits/sec, 0 packets/sec
  5 minute output rate 0 bits/sec, 0 packets/sec
     2955568 packets input, 189172880 bytes, 0 no buffer
     Received 0 broadcasts (0 IP multicasts)
     0 runts, 0 giants, 0 throttles 
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
     15 packets output, 1394 bytes, 0 underruns
     0 output errors, 6 interface resets
     0 unknown protocol drops
     0 output buffer failures, 0 output buffers swapped out
KAND_sw1#

about configuration. we are using a EoMPLS not VPLS, you can see my configuration on ME3600x 

interface Vlan1517
 mtu 9212
 no ip address
 xconnect 10.70.1.34 1517 encapsulation mpls
end

local interface on the ASR901 is gigabitethernet 0/2

SAG_rtr#sh inter gig 0/2
GigabitEthernet0/2 is up, line protocol is up (connected)
  Hardware is Gigabit Ethernet, address is 24e9.b3c0.5cca (bia 24e9.b3c0.5cca)
  Description: SAG_LOIS
  MTU 9212 bytes, BW 100000 Kbit/sec, DLY 10 usec, 
     reliability 255/255, txload 1/255, rxload 1/255
  Encapsulation ARPA, loopback not set
  Keepalive not set
  Full Duplex, 100Mbps, link type is auto, media type is RJ45
  output flow-control is unsupported, input flow-control is unsupported
  ARP type: ARPA, ARP Timeout 04:00:00
  Last input never, output never, output hang never
  Last clearing of "show interface" counters never
  Input queue: 0/200/2225/0 (size/max/drops/flushes); Total output drops: 0
  Queueing strategy: fifo
  Output queue: 0/40 (size/max)
  5 minute input rate 0 bits/sec, 0 packets/sec
  5 minute output rate 0 bits/sec, 0 packets/sec
     46077 packets input, 4060790 bytes, 0 no buffer
     Received 39204 broadcasts (0 IP multicasts)
     0 runts, 0 giants, 0 throttles 
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
     0 watchdog, 0 multicast, 0 pause input
     1678 packets output, 199898 bytes, 0 underruns
     0 output errors, 0 collisions, 1 interface resets
     0 unknown protocol drops
     0 babbles, 0 late collision, 0 deferred
     0 lost carrier, 0 no carrier, 0 pause output
     0 output buffer failures, 0 output buffers swapped out

 

configuration on this port is

SAG_rtr#sh run inter gig 0/2
Building configuration...

Current configuration : 274 bytes
!
interface GigabitEthernet0/2
 description SAG_LOIS
 mtu 9212
 no ip address
 negotiation auto
 ospfv3 mtu-ignore
 no keepalive
 service instance 1517 ethernet
  description SAG_LOIS
  encapsulation untagged
  xconnect 10.70.1.2 1517 encapsulation mpls
   mtu 9212
 !
end

as you can see all local interface is up and working, may be reason is not here?

I never saw a L2VPN using a SVI....

 

Try to create a pseudowire-class on both sides, and use the loopback f both as source address for this connection (of course, if the loopbacks are reachable between each other)

somethink like... (i dont have a router to test it now)

 

pseudowire-class EoMPLS   
 encapsulation mpls
 ip local interface loopback 0 

 

 

Then dont forget to add the pseudowire class in the xconnect (both sides)

 

xconnect 10.70.1.2 1517 pw-class EoMPLS

when i configure pw-class i cant add "ip local interface loo 0" on both side, because in my equipments does not present this command

in this time i have this configuration on the both side:

KAND_sw1#sh run | b pse
pseudowire-class eompls
 encapsulation mpls

!
interface GigabitEthernet0/2
 description SAG_LOIS
 mtu 9212
 no ip address
 negotiation auto
 ospfv3 mtu-ignore
 no keepalive
 service instance 1517 ethernet
  description SAG_LOIS
  encapsulation untagged
  xconnect 10.70.1.2 1517 encapsulation mpls pw-class eompls
 !
end

SAG_rtr#sh mpls l2 vc det
Local interface: Gi0/2 up, line protocol up, Ethernet:1517 up
  Destination address: 10.70.1.2, VC ID: 1517, VC status: down
    Last error: Remote peer access circuit is down
    Output interface: Vl11, imposed label stack {648 233}
    Preferred path: not configured  
    Default path: active
    Next hop: 10.70.1.214
  Create time: 00:06:09, last status change time: 00:00:12
    Last label FSM state change time: 00:05:44
  Signaling protocol: LDP, peer 10.70.1.2:0 up
    Targeted Hello: 10.70.1.34(LDP Id) -> 10.70.1.2, LDP is UP
    Graceful restart: not configured and not enabled
    Non stop routing: not configured and not enabled
    Status TLV support (local/remote)   : enabled/supported
      LDP route watch                   : enabled
      Label/status state machine        : established, LruRrd
      Last local dataplane   status rcvd: No fault
      Last BFD dataplane     status rcvd: Not sent
      Last BFD peer monitor  status rcvd: No fault
      Last local AC  circuit status rcvd: No fault
      Last local AC  circuit status sent: DOWN AC(rx/tx faults)
      Last local PW i/f circ status rcvd: No fault
      Last local LDP TLV     status sent: No fault
      Last remote LDP TLV    status rcvd: DOWN AC(rx/tx faults)
      Last remote LDP ADJ    status rcvd: No fault
    MPLS VC labels: local 1297, remote 233 
    Group ID: local 0, remote 0
    MTU: local 9212, remote 9212
    Remote interface description: 
  Sequencing: receive disabled, send disabled
  Control Word: On (configured: autosense)
  Dataplane:
    SSM segment/switch IDs: 98454/4245 (used), PWID: 1
  VC statistics:
    transit packet totals: receive 0, send 1157
    transit byte totals:   receive 0, send 97293
    transit packet drops:  receive 0, seq error 0, send 0

error is still present (((

i think your and my old configuration is same right, but a problem does not bound with configuration EoMPLS, i think a location of problem  is ME3600x, because in statistic of VC detail we are can see sent packets from ASR901, and not sent any packets from ME36600x

 

yeah.. forget it, that command is just for L2TPv3 (i forgot) ....

 

Try to make sure what is the best practice when using an interface vlan as the source, i never used it (maybe will lab it soon)

 

This status appears when the physical link is up/down or down/down, which is not your case !!

 

hope i could help

good luck

 

Vinit Jain
Cisco Employee
Cisco Employee

Hello Marat

Could you try to configure mpls ldp explicit-null on ASR901 side and see if that resolves the problem.

I would like to know what code are you running on both sides.

Please let me know if this helps.

Regards

Vinit

Thanks
--Vinit

bhnegi
Cisco Employee
Cisco Employee

Were you able to resolve this issue?

This message "Last error: Local peer access circuit is down" can be due to LDP having an error processing the PW during creation.

Can you try removing the xconnect and put it back on ME3600 int vlan 1517 and if it doesn't work try to clear ldp adjacency(clear mpls ldp nei 10.70.2.66). 

 If clearing the LDP neighbor does not work, then please collect debugs below.

sh mpls l2 vc 1517 det
sh mpls l2 vc 1517 det
sh mpls l2 vc 1517 det

show mpls l2 vc 1517 detail.

   show ssm seg id

   show ssm seg id det

  deb mpls l2transport vc eve

  deb mpls l2transport vc status event

  deb mpls l2transport vc ldp

 

Best Regards,

Bheem

 

Hi

same case here

I runn me3600x :
============================================

Cisco IOS Software, ME360x Software (ME360x-UNIVERSALK9-M), Version 15.5(3)S6a, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2017 by Cisco Systems, Inc.
Compiled Sun 30-Jul-17 13:00 by prod_rel_team

ROM: Bootstrap program is WHALES boot loader
BOOTLDR: ME360x Boot Loader (ME360X-HBOOT-M), Version 12.2 [sourdutt-loader_release_ledfix 100]

RIT-GI.PARIGI-ME3600-UPE-01 uptime is 2 weeks, 4 days, 13 hours, 21 minutes
System returned to ROM by power-on
System restarted at 22:42:49 WIB Mon Nov 13 2017
System image file is "flash:/me360x-universalk9-mz.155-3.S6a.bin"

===================================================

 

there is additional error like this :

nmpls_next_label_check: Label allocation Failed

 

does it have correlation between (nmpls_next_label_check: Label allocation Failed) and (Local peer access circuit is down)

 

 

zmtechnologie
Level 1
Level 1

I have the same problem please what is the solution.

Here Also the same error. Please any advise ? 

It means something is wrong at the local interface.

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: