Hi Paul,
We don’t have lisp control message tracing. But it may very well be that the
new pcap tracer is enough.
Florin
> On Jan 30, 2019, at 11:49 AM, Paul Vinciguerra
> wrote:
>
> Hi Florin,
>
> Is lisp control message tracing needed, or is it better to use the new
> wireshark extension
Hi Florin,
Is lisp control message tracing needed, or is it better to use the new
wireshark extensions?
On Wed, Jan 30, 2019 at 1:23 PM Florin Coras wrote:
> Yosvany,
>
> The trace you provided shows that the packet was processed okay and then
> dropped. Do you see any lisp errors if you do “sh
Yosvany,
The trace you provided shows that the packet was processed okay and then
dropped. Do you see any lisp errors if you do “show error” or in syslog?
It may turn out to be that we don’t have a parser for some record in the
map-reply. Note that testing has been done exclusively with ODL Li
VPP are delete LISP map reply from cisco router as LISP MR/MS when VPP are
making Map-Request to good EID.
The problem is when vni map to iid is differents that 0.
When response map-reply is native forward, VPP work fine.
When response is good VPP dont show the result on one eid-table remote.
