Hi Pablo,
After the update of the code, the problem is resolved.
Thank you for your help.
Thanks,
Xyxue
From: Pablo Camarillo (pcamaril)
Date: 2017-12-21 06:56
To: 薛欣颖; vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] problem in delete the 'sr mpls steer'
Hi Xyxue,
I’m unable to reproduce the crash. What was your initial state before typing
that CLI?
_______ _ _ _____ ___
__/ __/ _ \ (_)__ | | / / _ \/ _ \
_/ _// // / / / _ \ | |/ / ___/ ___/
/_/ /____(_)_/\___/ |___/_/ /_/
DBGvpp#
DBGvpp#
DBGvpp#
DBGvpp# mpls table add 9
DBGvpp# mpls table add 0
DBGvpp# sr mpls policy add bsid 999 next 202 next 203 next 204
DBGvpp# sr mpls steer l3 23.1.1.1/24 via sr policy bsid 999
DBGvpp# sr mpls steer l3 23.1.1.1/24 via sr policy bsid 999 del
DBGvpp#
DBGvpp#
Thank you.
Cheers,
Pablo.
From: <vpp-dev-boun...@lists.fd.io> on behalf of 薛欣颖 <xy...@fiberhome.com>
Date: Wednesday, 20 December 2017 at 10:26
To: "vpp-dev@lists.fd.io" <vpp-dev@lists.fd.io>
Subject: [vpp-dev] problem in delete the 'sr mpls steer'
Hi guys,
I'm testing sr mpls. When I del the 'sr mpls steer' ,there is a 'signal
SIGABRT'. My configuration and more info is shown below:
configuration:
mpls table add 9
mpls table add 0
sr mpls policy add bsid 999 next 202 next 203 next 204
sr mpls steer l3 23.1.1.1/24 via sr policy bsid 999
sr mpls steer l3 23.1.1.1/24 via sr policy bsid 999 del
Program received signal SIGABRT, Aborted.
0x00002b69d0d5bc37 in __GI_raise (sig=sig@entry=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:56
56 ../nptl/sysdeps/unix/sysv/linux/raise.c: 没有那个文件或目录.
(gdb) bt
#0 0x00002b69d0d5bc37 in __GI_raise (sig=sig@entry=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:56
#1 0x00002b69d0d5f028 in __GI_abort () at abort.c:89
#2 0x0000000000405d2b in os_panic () at
/home/VPP/build-data/../src/vpp/vnet/main.c:294
#3 0x00002b69d0679b88 in debugger () at
/home/VPP/build-data/../src/vppinfra/error.c:84
#4 0x00002b69d0679f8f in _clib_error (how_to_die=2, function_name=0x0,
line_number=0, fmt=0x2b69d0301438 "%s:%d (%s) assertion `%s' fails")
at /home/VPP/build-data/../src/vppinfra/error.c:143
#5 0x00002b69d018ddfb in fib_table_get (index=1, proto=FIB_PROTOCOL_IP4) at
/home/VPP/build-data/../src/vnet/fib/fib_table.c:33
#6 0x00002b69d018e2df in fib_table_lookup_exact_match (fib_index=1,
prefix=0x2b69d22d6980) at /home/VPP/build-data/../src/vnet/fib/fib_table.c:98
#7 0x00002b69d018faf1 in fib_table_entry_delete (fib_index=1,
prefix=0x2b69d22d6980, source=FIB_SOURCE_SR) at
/home/VPP/build-data/../src/vnet/fib/fib_table.c:900
#8 0x00002b69d0079392 in sr_mpls_steering_policy (is_del=1, bsid=999,
sr_policy_index=4294967295, table_id=4294967295, prefix=0x2b69d22d6a70,
mask_width=24,
traffic_type=4 '\004') at
/home/VPP/build-data/../src/vnet/srmpls/sr_mpls_steering.c:112
#9 0x00002b69d007aa5b in sr_mpls_steer_policy_command_fn (vm=0x2b69cfbea800
<vlib_global_main>, input=0x2b69d22d6ec0, cmd=0x2b69d223561c)
at /home/VPP/build-data/../src/vnet/srmpls/sr_mpls_steering.c:356
VPP# show mpls fib
MPLS-VRF:9, fib_index 0
ip4-explicit-null:neos/21 fib:0 index:10 locks:2
...
MPLS-VRF:0, fib_index -1
ip4-explicit-null:neos/21 fib:1 index:16 locks:2
...
Does the wrong fib_index have an impact on this problem?
What could I do to slove the problem?
Thanks,
Xyxue
_______________________________________________
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev
