Re: [vpp-dev] MPLS L3VPN PING FAILED

薛欣颖 Wed, 24 May 2017 22:55:13 -0700

Hi Neale,

I forgot to say ,I neither created tunnel nor used LDP.I used the static 
command configuration.


Thanks,
xyxue
 
From: 薛欣颖
Date: 2017-05-25 13:36
To: nranns; vpp-dev
Subject: Re: [vpp-dev] MPLS L3VPN PING FAILED

Hi Neale,

The ping  still failed .Here is the specific information：
DBGvpp# show trace 
**** CLIB unknown format `%#' ****x label 0 eos 1024
17:23:38:439098: lookup-mpls-dst
     fib-index:0 hdr:[1023:85:0:eos] load-balance:29
17:23:38:439159: ip4-mpls-label-disposition
  disp:0
17:23:38:439198: lookup-ip4-dst
     fib-index:1 addr:63.1.94.231 load-balance:9
17:23:38:439325: ip4-drop
    IP6_HOP_BY_HOP_OPTIONS: 85.93.65.0 -> 63.1.94.231
      version 0, header length 0
      tos 0x3f, ttl 69, length 61781, checksum 0x0054 (should be 0xffff)
      fragment id 0x0002 offset 35320, flags CONGESTION
17:23:38:439391: error-drop
  ip4-input: ip4 adjacency drop

By the way , I didn't build tunnels.

Thanks,
xyxue


 
From: Neale Ranns (nranns)
Date: 2017-05-24 18:18
To: 薛欣颖; vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] MPLS L3VPN PING FAILED
Hi Xyxue,
 
The lookup was performed in FIB index 1– you must have used ‘set int ip table 
host-XXX YYY’ - but the route you added is in the default table.
 
If you want the routes in the same table as the interface do;
  Ip route add table YYY 192.168.3.0/24 via mpls-tunnel0 out-label 1023
 
Regards,
Neale
 
p.s. are you really constructing the L3VPN from a [full] mesh of MPLS tunnels, 
or is it LDP in the core?
 
 
 
From: <vpp-dev-boun...@lists.fd.io> on behalf of 薛欣颖 <xy...@fiberhome.com>
Date: Wednesday, 24 May 2017 at 09:09
To: "vpp-dev@lists.fd.io" <vpp-dev@lists.fd.io>
Subject: [vpp-dev] MPLS L3VPN PING FAILED
 
 
Hi guys,
 
I have the following configuration:
mpls tunnel add via 2.1.1.1 host-eth1 out-label 1024 
set int state mpls-tunnel0 up 
ip route add 192.168.3.0/24 via mpls-tunnel0 out-label 1023
 
Ping from CE to PE ,and the PE drop it.
 
That is the fib :
192.168.3.0/24
  unicast-ip4-chain
  [@0]: dpo-load-balance: [proto:ip4 index:34 buckets:1 uRPF:36 to:[15:1260]]
    [0] [@11]: mpls-label:[3]:[1023:255:0:eos]
        [@2]: mpls via 0.0.0.0  mpls-tunnel0: 
          stacked-on:
            [@5]: dpo-load-balance: [proto:mpls index:35 buckets:1 uRPF:-1 
to:[0:0] via:[15:1320]]
              [0] [@8]: mpls-label:[1]:[1024:255:0:neos]
                  [@1]: mpls via 2.1.1.1 host-eth1: 00037ffffffe0e1a0d0050438847
 
The following is the trace info:
00:17:54:791606: af-packet-input
  af_packet: hw_if_index 1 next-index 4                                         
                                                                                
                
    tpacket2_hdr:
      status 0x1 len 98 snaplen 98 mac 66 net 80
      sec 0x16645 nsec 0x34a33284 vlan 0
00:17:54:791899: ethernet-input
  IP4: 2c:53:4a:02:91:95 -> 00:50:43:00:02:02
00:17:54:791956: ip4-input
  ICMP: 192.168.2.10 -> 192.168.3.10
    tos 0x00, ttl 64, length 84, checksum 0x0886
    fragment id 0xabbe, flags DONT_FRAGMENT
  ICMP echo_request checksum 0xae6a
00:17:54:792005: ip4-lookup
  fib 1 dpo-idx 1 flow hash: 0x00000000
  ICMP: 192.168.2.10 -> 192.168.3.10
    tos 0x00, ttl 64, length 84, checksum 0x0886
    fragment id 0xabbe, flags DONT_FRAGMENT
  ICMP echo_request checksum 0xae6a
00:17:54:792062: ip4-drop
    ICMP: 192.168.2.10 -> 192.168.3.10
      tos 0x00, ttl 64, length 84, checksum 0x0886
      fragment id 0xabbe, flags DONT_FRAGMENT
    ICMP echo_request checksum 0xae6a
00:17:54:792110: error-drop
  ip4-input: ip4 adjacency drop
 
How can I solve the problem?
 
Thanks,
xyxue

_______________________________________________
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] MPLS L3VPN PING FAILED

Reply via email to