Buy or Renew
Buy or Renew
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
1414
Views
0
Helpful
4
Replies

EoMPLS xconnect vc up success but not ping to end host

chang eun KIM
Level 1
Level 1

‎08-08-2016 09:52 AM

I configured as below.

vc is up. but not able to ping to end host.

Between ME3600X, I put "mpls ip and mpls label protocol ldp"

Is there any additional configuration?

L2 -- me3600 -- c7600 -- c7600 --me3600 --L2
pseudowire-class eompls
 encapsulation mpls
interface GigabitEthernet0/11
 description test mpls
 no switchport
 mtu 1538
 no ip address
 xconnect 192.168.19.21 800 encapsulation mpls pw-class eompls
ASCSE_ESWA01#sh mpls l2transport vc detail
Local interface: Gi0/2 up, line protocol up, Ethernet up
  Destination address: 192.168.19.21, VC ID: 800, VC status: up
    Output interface: Po10, imposed label stack {882 182}
    Preferred path: not configured  
    Default path: active
    Next hop: 192.168.83.1
  Create time: 00:04:07, last status change time: 00:02:50
    Last label FSM state change time: 00:02:50
  Signaling protocol: LDP, peer 192.168.19.21:0 up
    Targeted Hello: 192.168.8.21(LDP Id) -> 192.168.19.21, 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, LruRru
      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: No fault
      Last local PW i/f circ status rcvd: No fault
      Last local LDP TLV     status sent: No fault
      Last remote LDP TLV    status rcvd: No fault
      Last remote LDP ADJ    status rcvd: No fault
    MPLS VC labels: local 584, remote 182 
    Group ID: local 0, remote 0
    MTU: local 1538, remote 1538
    Remote interface description: test mpls
  Sequencing: receive disabled, send disabled
  Control Word: On (configured: autosense)
  Dataplane:
    SSM segment/switch IDs: 20572/4184 (used), PWID: 3
  VC statistics:
    transit packet totals: receive 0, send 1347
    transit byte totals:   receive 0, send 111349
    transit packet drops:  receive 0, seq error 0, send 0
pseudowire-class eompls
 encapsulation mpls
interface GigabitEthernet0/11
 description test mpls
 no switchport
 mtu 1538
 no ip address
 xconnect 192.168.8.21 800 encapsulation mpls pw-class eompls
KSC_ESWE01#sh mpls l2transport vc 800 detail 
Local interface: Gi0/11 up, line protocol up, Ethernet up
  Destination address: 192.168.8.21, VC ID: 800, VC status: up
    Output interface: Po3, imposed label stack {746 584}
    Preferred path: not configured  
    Default path: active
    Next hop: 192.168.195.1
  Create time: 00:02:03, last status change time: 00:02:03
    Last label FSM state change time: 00:02:03
  Signaling protocol: LDP, peer 192.168.8.21:0 up
    Targeted Hello: 192.168.19.21(LDP Id) -> 192.168.8.21, 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, LruRru
      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: No fault
      Last local PW i/f circ status rcvd: No fault
      Last local LDP TLV     status sent: No fault
      Last remote LDP TLV    status rcvd: No fault
      Last remote LDP ADJ    status rcvd: No fault
    MPLS VC labels: local 182, remote 584 
    Group ID: local 0, remote 0
    MTU: local 1538, remote 1538
    Remote interface description: ### ASWA05T24_G1/0/26 ###
  Sequencing: receive disabled, send disabled
  Control Word: On (configured: autosense)
  Dataplane:
    SSM segment/switch IDs: 20574/4188 (used), PWID: 3
  VC statistics:
    transit packet totals: receive 0, send 109
    transit byte totals:   receive 0, send 7987
    transit packet drops:  receive 0, seq error 0, send 0

Labels:
Preview file
61 KB
0 Helpful
4 Replies 4

Cristian Nilsson
Level 1
Level 1

‎08-09-2016 05:37 AM

Hello,

Does it go trough if you adjust the size? 

Example from Windows: ping -l 32 <ip> (this should be 32 by default thou).

Or IOS ping: <ip> size 32 (100 by default if not mistaken).

//Cristian

0 Helpful

chang eun KIM
Level 1
Level 1
In response to Cristian Nilsson

‎08-09-2016 09:00 PM

Not able to ping with small size(36)

I doubt the below status

No receive packets on each other.

VC statistics:
    transit packet totals: receive 0, send 109
    transit byte totals:   receive 0, send 7987
    transit packet drops:  receive 0, seq error 0, send 0
0 Helpful

Victor Acevedo
Cisco Employee
Cisco Employee
In response to chang eun KIM

‎08-10-2016 05:17 AM

Hey Chang,

Can you paste the interface configurations from your L2 devices - interfaces G1/0/11 and G1/0/2. Are these configured for trunk interfaces? 

If these are configured as trunks and we have SVI 83 configured, then we need to make sure that our Attachment Circuit (G0/11 and G0/2 on the PE's) are configured for subinterfaces for this Vlan or configure them as trunks as well and put the xconnect configs on the SVI (if you have Sup2T or WAN cards for the latter solution)

Thx,

Vic 

0 Helpful

chang eun KIM
Level 1
Level 1
In response to Victor Acevedo

‎08-13-2016 10:37 PM

cleared, Problem is that VC path is different.

After make same route, it works fine.

Thanks for your concern,

0 Helpful
Customers Also Viewed These Support Documents