Skip to Content.

rare-users - Re: [gn4-3-wp6-t1-wb-RARE] new features

Subject: RARE user and assistance email list

List archive


Re: [gn4-3-wp6-t1-wb-RARE] new features


Chronological Thread 
  • From: Tim Chown <>
  • To: "" <>
  • Cc: "" <>, "" <>
  • Subject: Re: [gn4-3-wp6-t1-wb-RARE] new features
  • Date: Mon, 8 Feb 2021 11:32:44 +0000
  • Accept-language: en-GB, en-US
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=jisc.ac.uk; dmarc=pass action=none header.from=jisc.ac.uk; dkim=pass header.d=jisc.ac.uk; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=iD5+ZPeW/btS/zHfT1BPuTNAp8wyYyq3+0i0lTyOKUI=; b=J3RfJhvtmFJZWDB0bsikTmyK9zSwk0vu7rcPKLMENxAaz6YC+B42HLkzfdLs26k6gRysMV9pRzZIftvyMFGTPnZ+w0beYJ4WBZgyrKGtN5wOiib1TIDweyS7BfGZ5PCNXwl11bGu1aEjevjmKurK6yrqsPV+VzgjWU4ujAL/tCsTB297GwIyENqzTVf54iQMpv6cK7FDTQ974LTCsbScglZBbxj+17yb4Ll/VuMR5IbVrQSkbClAXzPyHS2R8hFVvw5oIWNhXJOcHU8MoQ2N71XI3svfPj7X6vtjKiyx9KxyTt1RYVJ/ACoY6XeL+DR2puGnxgwbNmj5wBuOF+KwlA==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=COatmGxzyuuXMc3/YSnR8JWuckQ/u4zH7otYMWCb2pRernBFtFC3Tj3sODqP+AvcZJduw8NGMhIepI8VysTH8MVu4HU/NbBN5bGBLi8p5iITS0SpYZEDyMg8l3g9qxGJ9rLwnRIZBiQgH3bON+hR7RMt2v2ceZoIh/lL7eFpcDu+cZvAeh/g2iSn4PxN0hC8sH3IShVH2GBP3CoGsTxqaZBQGHcAwG6N1IahMQh8SawhR9xoyYYqIHqOROwmJjovdH2LPauJLuMURzjXM5Z8UyXibLIu9h4qZv6r9pTBLfj/R74n6mYVcyfm2NGhsuOYHIA+1mK8xV+MgVVQ5NA2Cw==
  • Authentication-results: lists.geant.org; dkim=none (message not signed) header.d=none;lists.geant.org; dmarc=none action=none header.from=jisc.ac.uk;

The question with multicast of course comes back to use cases.

It’s fantastic the bier support is now there, but what use cases might we
apply it to for the R&E domain? There’s not exactly a lot of content out
there. There’s been a recent push in the IETF to deprecate inter-domain
traditional ASM (which I was a draft author on) and to promote AMT
(“multicast to the grandma”), but less so with bier (so far!). Are there use
cases we could look at?

Tim

> On 6 Feb 2021, at 11:46, Frédéric LOUI <> wrote:
>
> Don’t be too fast !
>
> Let me some times to activate multicast on our homenet peering and
> And I need a bit of time to cook and prepare popcorn
>
> for the movie you’ll stream via BIER multicast domain. :)
>
> PS: Joke aside, congratulation ! IMHO this is a great achievement and it
> was a disruptive move as lots of the code moved to the egress pipeline.
>
> À bientôt,
> -- Frederic
>
>
>
>
>> Le 6 févr. 2021 à 10:52, mc36 <> a écrit :
>>
>> hi,
>> please find attached the latest test runs with dpdk and bmv2.
>> the news is that bmv2 got the bier support... tbh it was (1) a
>> small change as the bigger part of the work was already done
>> with the egress pipe usage in p4 code and the export of computed
>> forwarding tables for preparation to the dpdk code...
>> so for now, nothing left but to proceed to the tofino...
>> regards,
>> cs
>>
>> 1:
>> https://github.com/frederic-loui/RARE/commit/849110305e52fd2544b405012f589e656fae4eb8
>>
>>
>> On 2/5/21 7:31 PM, mc36 wrote:
>>> hi,
>>> please find attached the fresh test runs with dpdk.
>>> news that it finally got the full bier support. (at the end of the list)
>>> the rosetta stone here is that i call it core support when i test the
>>> pure bier replication, no header strip nor imposition. i call it ingress
>>> when the packet arrives as raw ip and it get encapped to bier (tv headend)
>>> i call it egress when the packet arrives in bier ad put out as raw ip (to
>>> stb)
>>> and i also test mixed mode when the i test egress and core at the same
>>> time.
>>> (i dont test mixed ingress as it's just a simple raw ip multicasting
>>> which already tested:)
>>> the tests are clickable as usual, so you can spot the regular things:
>>> - all the tests are dual
>>> - on the raw ip side i mostly use pim (but it could be igmp/mldp also)
>>> - i test the number of replications happened (pings expecting 400% as
>>> result)
>>> - also test if it happens outsode of the freetr itself (sho inter summ
>>> before and after,
>>> Â the diff must be far below the transmitted amount of traffic)
>>> - in some tests i involve igp or bgp to have reachability and/or bier
>>> idx/base set
>>> all these means that for now the api from freertr is stable so i can
>>> start adding
>>> these to bmv2 then the tofino. i asked vlad @ barefoot if he have some
>>> good idea
>>> on how to do that well, got an unexpected answer that he dunno, but
>>> mentioned a wotk
>>> which i was able to find, but didn't won a price here, so i'll proceed as
>>> i tought initially:
>>> a constant replication list populating all the possible receivers in the
>>> ingress path,
>>> and anding the packet's bier bitmap against the current replica's
>>> copyhere bitmap in egress.
>>> regards,
>>> cs
>>> https://community.intel.com/t5/Intel-Connectivity-Research/best-practices-to-replicate-BIER-packets/m-p/1252259/thread-id/2043
>>> On 2/5/21 1:08 PM, Tim Chown wrote:
>>>> Great, thank you.
>>>>
>>>>> On 5 Feb 2021, at 11:12, mc36 <> wrote:
>>>>>
>>>>> hi,
>>>>>
>>>>> here we go... the dataplane features i marked will be out soon for p4,
>>>>> and mostly all are here in the dpdk code...
>>>>>
>>>>>
>>>>>
>>>>> in dataplane only featuers:
>>>>>
>>>>> RFC 8279 (was draft-ietf-bier-architecture) Multicast Using Bit Index
>>>>> Explicit Replication (BIER)
>>>>>
>>>>> RFC 8296 (was draft-ietf-bier-mpls-encapsulation) Encapsulation for Bit
>>>>> Index Explicit Replication (BIER) in MPLS and Non-MPLS Networks
>>>>>
>>>>>
>>>>>
>>>>> control plane only features:
>>>>>
>>>>> RFC 8401 (was draft-ietf-bier-isis-extensions) Bit Index Explicit
>>>>> Replication (BIER) Support via IS-IS
>>>>>
>>>>> RFC 8444 (was draft-ietf-bier-ospf-bier-extensions) OSPFv2 Extensions
>>>>> for Bit Index Explicit Replication (BIER)
>>>>>
>>>>> draft-ietf-bier-pim-signaling-11 PIM Signaling Through BIER Core <---
>>>>> also have dataplane needs, which also available
>>>>>
>>>>> draft-ietf-bier-evpn-04Â EVPN BUM Using BIERÂ <--- only available in
>>>>> software forwarding at the moment!
>>>>>
>>>>>
>>>>> regrads,
>>>>> cs
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On 2/5/21 12:04 PM, Tim Chown wrote:
>>>>>> Hi,
>>>>>> This all looks very encouraging!
>>>>>> Can we say anything about compliance with or which parts of the IETF
>>>>>> bier RFC and drafts the implementation supports?
>>>>>> (As per https://datatracker.ietf.org/wg/bier/documents/ which lists
>>>>>> the 5 RFCs and the many drafts)
>>>>>> Tim
>>>>>>> On 4 Feb 2021, at 20:22, mc36 <> wrote:
>>>>>>>
>>>>>>> hi,
>>>>>>> the bier core (phase 1, we can say:) feature just arrived to the
>>>>>>> p4emu (dpdk, libpcap) dataplane....
>>>>>>> i need to do some housekeeping around it like adding the test cases
>>>>>>> for it and so on but i'm sure
>>>>>>> that it works as i use it extensively on my homenet... back in time
>>>>>>> kifu deployed a probe network
>>>>>>> to test it's mpls core.. there was not such a software that suited
>>>>>>> our needs so i added the missing
>>>>>>> pieces to freertr so now it can do a so called 'mesh tracker'. it can
>>>>>>> operate in unicast or multicast.
>>>>>>> it does only 2 thing: periodically fetches the peer list, and sends
>>>>>>> reports to the peers...
>>>>>>> the output is pretty self-explanatiory (1) a connectivity matrix.. in
>>>>>>> my case it all goes over
>>>>>>> bier (2) according to the local mroute and mldp tables...
>>>>>>> as every packet hold's the info where it wants to get itself
>>>>>>> replicated, the uplink of the
>>>>>>> tester knows nothing about the existence of the s,g groups (3).. this
>>>>>>> is what we call stateless!
>>>>>>> the only thing it knows is the bier bitmaps (4) computed by the igp
>>>>>>> in my case...
>>>>>>> as you can see, there were only hw switched packets, the freertr
>>>>>>> itselt did not get involved
>>>>>>> in the replication at all... hereby i would like to note that those
>>>>>>> hairpins (5) are all
>>>>>>> macsec-ed interfaces here as they're bridged toward the vpn tunnels
>>>>>>> to my other sites...
>>>>>>> for those who are skeptical about the mtracker thingy, you can spot
>>>>>>> in (1) that some peers had
>>>>>>> 130 reports while others just 10, this is because on the first try
>>>>>>> the flooding did not worked
>>>>>>> on hairpins as you can see on the failed (6) mtracker output, only my
>>>>>>> internal nodes had connectivity....
>>>>>>> regards,
>>>>>>> cs
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> 1:
>>>>>>> mchome-evpn#show mtracker
>>>>>>> name group                    port totalÂ
>>>>>>> reach bidir changed
>>>>>>> l2v  10.11.12.13              5499 9     9Â
>>>>>>> Â Â Â Â 9Â Â Â Â Â 01:15:39
>>>>>>> v4Â Â Â 10.11.12.13Â Â Â Â Â Â Â Â Â Â Â Â Â Â 5499Â 13Â Â Â Â
>>>>>>> 13Â Â Â Â 13Â Â Â Â 01:16:12
>>>>>>> v4m  232.197.91.25            5488 13    13 Â
>>>>>>> Â Â 13Â Â Â Â 00:07:52
>>>>>>> v4v  10.11.12.13              5499 11    11Â
>>>>>>> Â Â Â 11Â Â Â Â 01:16:12
>>>>>>> v6Â Â Â 2001:db8:1234:1234::1234Â 5499Â 13Â Â Â Â 13Â Â Â Â 13Â
>>>>>>> Â Â Â 01:16:12
>>>>>>> v6m  ff09::232:197:91:25      5488 13    13   Â
>>>>>>> 13Â Â Â Â 00:08:26
>>>>>>> v6v  2001:db8:1234:1234::1234 5499 11    11    11 Â
>>>>>>> Â Â 01:16:12
>>>>>>>
>>>>>>> mchome-evpn#show mtracker v4m
>>>>>>> name=v4m, round=133, group=232.197.91.25
>>>>>>> port=5488, timer=33333/6, source=ifc loopback0
>>>>>>> changes=15, ago=00:08:01, at=2021-02-04 21:04:22
>>>>>>> peer#0: ip=10.1.11.199, state=up, changes=1, ago=01:16:21,
>>>>>>> at=2021-02-04 19:56:02, reports=130, last=00:00:22
>>>>>>> peer#1: ip=10.1.11.254, state=up, changes=1, ago=01:16:55,
>>>>>>> at=2021-02-04 19:55:28, reports=132, last=00:00:32
>>>>>>> peer#2: ip=10.1.11.255, state=up, changes=1, ago=01:16:55,
>>>>>>> at=2021-02-04 19:55:28, reports=-9, last=00:00:14
>>>>>>> peer#3: ip=10.4.4.254, state=up, changes=3, ago=00:08:01,
>>>>>>> at=2021-02-04 21:04:22, reports=12, last=00:00:18
>>>>>>> peer#4: ip=10.10.10.10, state=up, changes=1, ago=01:16:55,
>>>>>>> at=2021-02-04 19:55:28, reports=132, last=00:00:16
>>>>>>> peer#5: ip=10.10.10.19, state=up, changes=1, ago=00:08:01,
>>>>>>> at=2021-02-04 21:04:22, reports=9, last=00:00:16
>>>>>>> peer#6: ip=10.10.10.21, state=up, changes=1, ago=00:08:01,
>>>>>>> at=2021-02-04 21:04:22, reports=9, last=00:00:30
>>>>>>> peer#7: ip=10.10.10.26, state=up, changes=1, ago=00:08:01,
>>>>>>> at=2021-02-04 21:04:22, reports=10, last=00:00:07
>>>>>>> peer#8: ip=10.10.10.190, state=up, changes=1, ago=00:08:01,
>>>>>>> at=2021-02-04 21:04:22, reports=9, last=00:00:32
>>>>>>> peer#9: ip=10.10.10.222, state=up, changes=1, ago=01:16:55,
>>>>>>> at=2021-02-04 19:55:28, reports=133, last=00:00:11
>>>>>>> peer#10: ip=10.10.10.224, state=up, changes=1, ago=00:08:01,
>>>>>>> at=2021-02-04 21:04:22, reports=9, last=00:00:24
>>>>>>> peer#11: ip=10.10.10.225, state=up, changes=1, ago=00:08:01,
>>>>>>> at=2021-02-04 21:04:22, reports=9, last=00:00:24
>>>>>>> peer#12: ip=10.10.10.226, state=up, changes=1, ago=00:08:01,
>>>>>>> at=2021-02-04 21:04:22, reports=9, last=00:00:24
>>>>>>>
>>>>>>> \Â Â 0Â 1Â 2Â 3Â 4Â 5Â 6Â 7Â 8Â 9Â 10Â 11Â 12
>>>>>>> 0Â Â \Â +Â +Â +Â +Â +Â +Â +Â +Â +Â +Â Â +Â Â +
>>>>>>> 1Â Â +Â \Â +Â +Â +Â +Â +Â +Â +Â +Â +Â Â +Â Â +
>>>>>>> 2Â Â +Â +Â \Â +Â +Â +Â +Â +Â +Â +Â +Â Â +Â Â +
>>>>>>> 3Â Â +Â +Â +Â \Â +Â +Â +Â +Â +Â +Â +Â Â +Â Â +
>>>>>>> 4Â Â +Â +Â +Â +Â \Â +Â +Â +Â +Â +Â +Â Â +Â Â +
>>>>>>> 5Â Â +Â +Â +Â +Â +Â \Â +Â +Â +Â +Â +Â Â +Â Â +
>>>>>>> 6Â Â +Â +Â +Â +Â +Â +Â \Â +Â +Â +Â +Â Â +Â Â +
>>>>>>> 7Â Â +Â +Â +Â +Â +Â +Â +Â \Â +Â +Â +Â Â +Â Â +
>>>>>>> 8Â Â +Â +Â +Â +Â +Â +Â +Â +Â \Â +Â +Â Â +Â Â +
>>>>>>> 9Â Â +Â +Â +Â +Â +Â +Â +Â +Â +Â \Â +Â Â +Â Â +
>>>>>>> 10Â +Â +Â +Â +Â +Â +Â +Â +Â +Â +Â \Â Â +Â Â +
>>>>>>> 11Â +Â +Â +Â +Â +Â +Â +Â +Â +Â +Â +Â Â \Â Â +
>>>>>>> 12Â +Â +Â +Â +Â +Â +Â +Â +Â +Â +Â +Â Â +Â Â \
>>>>>>>
>>>>>>> mchome-evpn#show mtracker v6m
>>>>>>> name=v6m, round=133, group=ff09::232:197:91:25
>>>>>>> port=5488, timer=33333/6, source=ifc loopback0
>>>>>>> changes=13, ago=00:08:36, at=2021-02-04 21:03:48
>>>>>>> peer#0: ip=2001:db8:1101::10, state=up, changes=1, ago=01:16:57,
>>>>>>> at=2021-02-04 19:55:28, reports=132, last=00:00:12
>>>>>>> peer#1: ip=2001:db8:1101::19, state=up, changes=1, ago=00:08:36,
>>>>>>> at=2021-02-04 21:03:48, reports=10, last=00:00:18
>>>>>>> peer#2: ip=2001:db8:1101::21, state=up, changes=1, ago=00:08:36,
>>>>>>> at=2021-02-04 21:03:48, reports=10, last=00:00:32
>>>>>>> peer#3: ip=2001:db8:1101::26, state=up, changes=1, ago=00:08:36,
>>>>>>> at=2021-02-04 21:03:48, reports=10, last=00:00:32
>>>>>>> peer#4: ip=2001:db8:1101::190, state=up, changes=1, ago=00:08:36,
>>>>>>> at=2021-02-04 21:03:48, reports=10, last=00:00:21
>>>>>>> peer#5: ip=2001:db8:1101::4254, state=up, changes=1, ago=00:08:36,
>>>>>>> at=2021-02-04 21:03:48, reports=10, last=00:00:20
>>>>>>> peer#6: ip=2001:db8:1101::222:222, state=up, changes=1, ago=01:16:57,
>>>>>>> at=2021-02-04 19:55:28, reports=132, last=00:00:13
>>>>>>> peer#7: ip=2001:db8:1101::224:224, state=up, changes=1, ago=00:08:36,
>>>>>>> at=2021-02-04 21:03:48, reports=10, last=00:00:26
>>>>>>> peer#8: ip=2001:db8:1101::225:225, state=up, changes=1, ago=00:08:36,
>>>>>>> at=2021-02-04 21:03:48, reports=10, last=00:00:26
>>>>>>> peer#9: ip=2001:db8:1101::226:226, state=up, changes=1, ago=00:08:36,
>>>>>>> at=2021-02-04 21:03:48, reports=10, last=00:00:26
>>>>>>> peer#10: ip=2001:db8:1101::252:199, state=up, changes=1,
>>>>>>> ago=01:16:23, at=2021-02-04 19:56:02, reports=130, last=00:00:24
>>>>>>> peer#11: ip=2001:db8:1101::252:254, state=up, changes=1,
>>>>>>> ago=01:16:57, at=2021-02-04 19:55:28, reports=129, last=00:00:00
>>>>>>> peer#12: ip=2001:db8:1101::252:255, state=up, changes=1,
>>>>>>> ago=01:16:57, at=2021-02-04 19:55:28, reports=-9, last=00:00:16
>>>>>>>
>>>>>>> \Â Â 0Â 1Â 2Â 3Â 4Â 5Â 6Â 7Â 8Â 9Â 10Â 11Â 12
>>>>>>> 0Â Â \Â +Â +Â +Â +Â +Â +Â +Â +Â +Â +Â Â +Â Â +
>>>>>>> 1Â Â +Â \Â +Â +Â +Â +Â +Â +Â +Â +Â +Â Â +Â Â +
>>>>>>> 2Â Â +Â +Â \Â +Â +Â +Â +Â +Â +Â +Â +Â Â +Â Â +
>>>>>>> 3Â Â +Â +Â +Â \Â +Â +Â +Â +Â +Â +Â +Â Â +Â Â +
>>>>>>> 4Â Â +Â +Â +Â +Â \Â +Â +Â +Â +Â +Â +Â Â +Â Â +
>>>>>>> 5Â Â +Â +Â +Â +Â +Â \Â +Â +Â +Â +Â +Â Â +Â Â +
>>>>>>> 6Â Â +Â +Â +Â +Â +Â +Â \Â +Â +Â +Â +Â Â +Â Â +
>>>>>>> 7Â Â +Â +Â +Â +Â +Â +Â +Â \Â +Â +Â +Â Â +Â Â +
>>>>>>> 8Â Â +Â +Â +Â +Â +Â +Â +Â +Â \Â +Â +Â Â +Â Â +
>>>>>>> 9Â Â +Â +Â +Â +Â +Â +Â +Â +Â +Â \Â +Â Â +Â Â +
>>>>>>> 10Â +Â +Â +Â +Â +Â +Â +Â +Â +Â +Â \Â Â +Â Â +
>>>>>>> 11Â +Â +Â +Â +Â +Â +Â +Â +Â +Â +Â +Â Â \Â Â +
>>>>>>> 12Â +Â +Â +Â +Â +Â +Â +Â +Â +Â +Â +Â Â +Â Â \
>>>>>>>
>>>>>>> mchome-evpn#
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> 2:
>>>>>>> mchome-evpn#show ipv4 mroute inet
>>>>>>> source       group         interface  upstreamÂ
>>>>>>> Â Â Â targets
>>>>>>> 10.1.11.199Â Â 232.197.91.25Â ethernet12Â 10.1.1.117Â Â local
>>>>>>> 10.1.11.254Â Â 232.197.91.25Â ethernet12Â 10.1.1.117Â Â local
>>>>>>> 10.1.11.255Â Â 232.197.91.25Â loopback0Â Â 10.1.11.255Â local bier
>>>>>>> 10.4.4.254Â Â Â 232.197.91.25Â ethernet12Â 10.1.1.117Â Â local
>>>>>>> 10.10.10.10Â Â 232.197.91.25Â ethernet12Â 10.1.1.117Â Â local
>>>>>>> 10.10.10.19Â Â 232.197.91.25Â ethernet12Â 10.1.1.117Â Â local
>>>>>>> 10.10.10.21Â Â 232.197.91.25Â ethernet12Â 10.1.1.117Â Â local
>>>>>>> 10.10.10.26Â Â 232.197.91.25Â ethernet12Â 10.1.1.117Â Â local
>>>>>>> 10.10.10.190Â 232.197.91.25Â ethernet12Â 10.1.1.117Â Â local
>>>>>>> 10.10.10.222Â 232.197.91.25Â ethernet12Â 10.1.1.117Â Â local
>>>>>>> 10.10.10.224Â 232.197.91.25Â ethernet12Â 10.1.1.117Â Â local
>>>>>>> 10.10.10.225Â 232.197.91.25Â ethernet12Â 10.1.1.117Â Â local
>>>>>>> 10.10.10.226Â 232.197.91.25Â ethernet12Â 10.1.1.117Â Â local
>>>>>>>
>>>>>>> mchome-evpn#show ipv4 ldp inet mpdatabase
>>>>>>> type root opaque uplink peers
>>>>>>>
>>>>>>> mchome-evpn#
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> 3:
>>>>>>> mchome#show ipv4 mroute inet
>>>>>>> source group interface upstream targets
>>>>>>>
>>>>>>> mchome#show ipv4 ldp inet mpdatabase
>>>>>>> type root opaque uplink peers
>>>>>>>
>>>>>>> mchome#show ipv4 mroute inet
>>>>>>> source group interface upstream targets
>>>>>>>
>>>>>>> mchome#
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> 4:
>>>>>>> mchome#show mpls forwarding | include bier
>>>>>>> 616945  inet:4  null         null         Â
>>>>>>>    unlabelled bier    0+272135
>>>>>>> 616946  inet:4  null         null         Â
>>>>>>>    unlabelled bier    0+0
>>>>>>> 1048221 inet:6  null         null          Â
>>>>>>>   unlabelled bier    0+364782
>>>>>>> 1048222 inet:6  null         null          Â
>>>>>>>   unlabelled bier    0+0
>>>>>>>
>>>>>>> mchome#show mpls forwarding 616945
>>>>>>> category         value
>>>>>>> label            616945
>>>>>>> key              18-lsrp bier
>>>>>>> working          true
>>>>>>> forwarder        inet:4
>>>>>>> interface        null
>>>>>>> nexthop          null
>>>>>>> remote label     unlabelled
>>>>>>> need local       false
>>>>>>> bier base        616945
>>>>>>> bier bsl         3-256
>>>>>>> bier si          0
>>>>>>> bier sis         0
>>>>>>> bier idx         10
>>>>>>> bier idx2Â Â Â Â Â Â Â Â 0
>>>>>>> bier local       00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>>>>>>> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 02 00
>>>>>>> bier peer        10.1.1.173 bundle1.176 lab=203046 00 00
>>>>>>> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20 01 00 00 00 00 00
>>>>>>> 00 00 00 00 00 00 00
>>>>>>> bier peer        10.1.1.125 bundle1.182 lab=689174 00 00
>>>>>>> 00 00 00 00 00 43 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>>>>>>> 00 00 00 00 00 00 00
>>>>>>> bier peer        10.1.1.122 bundle1.186 lab=893418 00 00
>>>>>>> 00 00 00 00 00 80 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>>>>>>> 00 00 00 01 80 00 00
>>>>>>> bier peer        10.1.1.94 bundle1.189 lab=213418 00 00 00
>>>>>>> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>>>>>>> 00 00 00 08 00 00
>>>>>>> bier peer        10.1.1.74 bundle1.196 lab=302713 00 00 00
>>>>>>> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 80 00 00 00
>>>>>>> 00 00 00 00 00 00
>>>>>>> bier peer        10.5.1.53 bundle1.199 lab=940285 00 00 00
>>>>>>> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 22
>>>>>>> 00 00 00 40 00 00
>>>>>>> bier peer        10.18.1.1 hairpin72.15 lab=951037 00 00
>>>>>>> 00 00 00 00 00 00 00 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>>>>>>> 00 00 00 00 00 00 00
>>>>>>> bier peer        10.18.1.9 hairpin82.23 lab=455475 00 00
>>>>>>> 00 00 00 02 00 00 60 08 00 00 00 00 00 00 00 00 00 00 70 00 00 40 00
>>>>>>> 00 00 01 c4 00 00 00
>>>>>>> bier peer        10.18.1.246 hairpin92.33 lab=413818 00 00
>>>>>>> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>>>>>>> 00 40 80 00 00 00 00
>>>>>>> bier peer        10.2.1.6 sdn901 lab=389133 00 00 00 00 00
>>>>>>> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>>>>>>> 02 00 00 00
>>>>>>> bier peer        10.1.1.118 sdn902 lab=132866 00 00 00 00
>>>>>>> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>>>>>>> 00 00 20 00 00
>>>>>>> pwe iface        null
>>>>>>> pwe del          0
>>>>>>> pwe add          n/a
>>>>>>> counter          tx=0(0) rx=0(0) drp=0(0)
>>>>>>> hardware counter tx=0(0) rx=272135(1965) drp=0(0)
>>>>>>>
>>>>>>> mchome#
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> 5:
>>>>>>> mchome#show macsec ha72.15
>>>>>>> category value
>>>>>>> seq      14234
>>>>>>> win      null
>>>>>>> pack     14234+3495     4352+4385     0+0
>>>>>>> byte     1754603+637918 335878+798764 0+0
>>>>>>>
>>>>>>> mchome#
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> 6:
>>>>>>> services>show mtracker
>>>>>>> 2021-02-04 21:05:07
>>>>>>> name group                    port totalÂ
>>>>>>> reach bidir changed
>>>>>>> l2v  10.11.12.13              5499 9     9Â
>>>>>>> Â Â Â Â 9Â Â Â Â Â 01:08:27
>>>>>>> v4Â Â Â 10.11.12.13Â Â Â Â Â Â Â Â Â Â Â Â Â Â 5499Â 13Â Â Â Â
>>>>>>> 13Â Â Â Â 13Â Â Â Â 01:09:07
>>>>>>> v4m  232.197.91.25            5488 13    5 Â
>>>>>>> Â Â Â 5Â Â Â Â Â 01:06:54
>>>>>>> v4v  10.11.12.13              5499 11    11Â
>>>>>>> Â Â Â 11Â Â Â Â 01:09:34
>>>>>>> v6Â Â Â 2001:db8:1234:1234::1234Â 5499Â 13Â Â Â Â 13Â Â Â Â 13Â
>>>>>>> Â Â Â 01:09:34
>>>>>>> v6m  ff09::232:197:91:25      5488 13    5    Â
>>>>>>> 5Â Â Â Â Â 01:06:47
>>>>>>> v6v  2001:db8:1234:1234::1234 5499 11    11    11 Â
>>>>>>> Â Â 01:09:05
>>>>>>>
>>>>>>> services>show mtracker v4m
>>>>>>> 2021-02-04 21:05:10
>>>>>>> name=v4m, round=122, group=232.197.91.25
>>>>>>> port=5488, timer=33333/6, source=ifc loopback0
>>>>>>> changes=21, ago=01:06:56, at=2021-02-04 19:58:13
>>>>>>> peer#0: ip=10.1.11.199, state=up, changes=1, ago=01:10:50,
>>>>>>> at=2021-02-04 19:54:20, reports=121, last=00:00:22
>>>>>>> peer#1: ip=10.1.11.254, state=up, changes=1, ago=01:10:50,
>>>>>>> at=2021-02-04 19:54:20, reports=121, last=00:00:31
>>>>>>> peer#2: ip=10.1.11.255, state=up, changes=1, ago=01:09:10,
>>>>>>> at=2021-02-04 19:56:00, reports=120, last=00:00:14
>>>>>>> peer#3: ip=10.4.4.254, state=down, changes=2, ago=01:06:56,
>>>>>>> at=2021-02-04 19:58:13, reports=2, last=01:06:58
>>>>>>> peer#4: ip=10.10.10.10, state=up, changes=1, ago=01:10:50,
>>>>>>> at=2021-02-04 19:54:20, reports=-9, last=00:00:16
>>>>>>> peer#5: ip=10.10.10.19, state=down, changes=2, ago=01:06:56,
>>>>>>> at=2021-02-04 19:58:13, reports=2, last=01:06:56
>>>>>>> peer#6: ip=10.10.10.21, state=down, changes=2, ago=01:06:56,
>>>>>>> at=2021-02-04 19:58:13, reports=2, last=01:07:10
>>>>>>> peer#7: ip=10.10.10.26, state=down, changes=2, ago=01:06:56,
>>>>>>> at=2021-02-04 19:58:13, reports=2, last=01:07:20
>>>>>>> peer#8: ip=10.10.10.190, state=down, changes=2, ago=01:06:56,
>>>>>>> at=2021-02-04 19:58:13, reports=2, last=01:07:12
>>>>>>> peer#9: ip=10.10.10.222, state=up, changes=1, ago=01:10:50,
>>>>>>> at=2021-02-04 19:54:20, reports=123, last=00:00:11
>>>>>>> peer#10: ip=10.10.10.224, state=down, changes=2, ago=01:06:56,
>>>>>>> at=2021-02-04 19:58:13, reports=2, last=01:07:26
>>>>>>> peer#11: ip=10.10.10.225, state=down, changes=2, ago=01:06:56,
>>>>>>> at=2021-02-04 19:58:13, reports=2, last=01:07:26
>>>>>>> peer#12: ip=10.10.10.226, state=down, changes=2, ago=01:06:56,
>>>>>>> at=2021-02-04 19:58:13, reports=2, last=01:07:26
>>>>>>>
>>>>>>> \Â Â 0Â 1Â 2Â 3Â 4Â 5Â 6Â 7Â 8Â 9Â 10Â 11Â 12
>>>>>>> 0Â Â \Â +Â +Â -Â +Â -Â -Â -Â -Â +Â -Â Â -Â Â -
>>>>>>> 1Â Â +Â \Â +Â -Â +Â -Â -Â -Â -Â +Â -Â Â -Â Â -
>>>>>>> 2Â Â +Â +Â \Â -Â +Â -Â -Â -Â -Â +Â -Â Â -Â Â -
>>>>>>> 3Â Â -Â -Â -Â \Â -Â -Â -Â -Â -Â -Â -Â Â -Â Â -
>>>>>>> 4Â Â +Â +Â +Â -Â \Â -Â -Â -Â -Â +Â -Â Â -Â Â -
>>>>>>> 5Â Â -Â -Â -Â -Â -Â \Â -Â -Â -Â -Â -Â Â -Â Â -
>>>>>>> 6Â Â -Â -Â -Â -Â -Â -Â \Â -Â -Â -Â -Â Â -Â Â -
>>>>>>> 7Â Â -Â -Â -Â -Â -Â -Â -Â \Â -Â -Â -Â Â -Â Â -
>>>>>>> 8Â Â -Â -Â -Â -Â -Â -Â -Â -Â \Â -Â -Â Â -Â Â -
>>>>>>> 9Â Â +Â +Â +Â -Â +Â -Â -Â -Â -Â \Â -Â Â -Â Â -
>>>>>>> 10Â -Â -Â -Â -Â -Â -Â -Â -Â -Â -Â \Â Â -Â Â -
>>>>>>> 11Â -Â -Â -Â -Â -Â -Â -Â -Â -Â -Â -Â Â \Â Â -
>>>>>>> 12Â -Â -Â -Â -Â -Â -Â -Â -Â -Â -Â -Â Â -Â Â \
>>>>>>>
>>>>>>> services>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> as seemingly there is an interest in the bier progress so here is
>>>>>>>> the current state,
>>>>>>>> the api messages are seems to be allright and react to the changes
>>>>>>>> (i cleared the peer)
>>>>>>>> now the p4emu (dpdk) to consume these and replicate the packets
>>>>>>>> accordingly....
>>>>>>>> regards,
>>>>>>>> cs
>>>>>>>> sid#show logging | include bier
>>>>>>>> 2021-02-04 16:33:59.797 debug
>>>>>>>> serv.servP4lang.sendLine:servP4lang.java:560 tx: bierlabloc4_add 2
>>>>>>>> 56298 252905 0 0 0 0 0 0 0 2
>>>>>>>> 2021-02-04 16:34:02.248 debug
>>>>>>>> serv.servP4lang.sendLine:servP4lang.java:560 tx: bierlabel4_add 2
>>>>>>>> 56298 252905 1 1 4244 540419 0 0 0 0 0 0 0 4
>>>>>>>> 2021-02-04 16:34:02.249 debug
>>>>>>>> serv.servP4lang.sendLine:servP4lang.java:560 tx: bierlabel4_add 2
>>>>>>>> 56298 252905 2 2 50978 761055 0 0 0 0 0 0 0 8
>>>>>>>> 2021-02-04 16:34:02.249 debug
>>>>>>>> serv.servP4lang.sendLine:servP4lang.java:560 tx: bierlabel4_add 2
>>>>>>>> 56298 252905 3 3 62714 800735 0 0 0 0 0 0 0 16
>>>>>>>> 2021-02-04 16:34:02.249 debug
>>>>>>>> serv.servP4lang.sendLine:servP4lang.java:560 tx: bierlabloc4_mod 2
>>>>>>>> 56298 252905 0 0 0 0 0 0 0 2
>>>>>>>> 2021-02-04 16:34:32.685 debug
>>>>>>>> serv.servP4lang.sendLine:servP4lang.java:560 tx: bierlabel4_del 2
>>>>>>>> 56298 252905 1 1 4244 540419 0 0 0 0 0 0 0 4
>>>>>>>> 2021-02-04 16:34:32.686 debug
>>>>>>>> serv.servP4lang.sendLine:servP4lang.java:560 tx: bierlabel4_mod 2
>>>>>>>> 56298 252905 2 2 50978 761055 0 0 0 0 0 0 0 8
>>>>>>>> 2021-02-04 16:34:32.686 debug
>>>>>>>> serv.servP4lang.sendLine:servP4lang.java:560 tx: bierlabel4_mod 2
>>>>>>>> 56298 252905 3 3 62714 800735 0 0 0 0 0 0 0 16
>>>>>>>> 2021-02-04 16:34:32.686 debug
>>>>>>>> serv.servP4lang.sendLine:servP4lang.java:560 tx: bierlabloc4_mod 2
>>>>>>>> 56298 252905 0 0 0 0 0 0 0 2
>>>>>>>> 2021-02-04 16:34:35.694 debug
>>>>>>>> serv.servP4lang.sendLine:servP4lang.java:560 tx: bierlabel4_add 2
>>>>>>>> 56298 252905 1 1 4244 540419 0 0 0 0 0 0 0 4
>>>>>>>> 2021-02-04 16:34:35.694 debug
>>>>>>>> serv.servP4lang.sendLine:servP4lang.java:560 tx: bierlabel4_mod 2
>>>>>>>> 56298 252905 2 2 50978 761055 0 0 0 0 0 0 0 8
>>>>>>>> 2021-02-04 16:34:35.694 debug
>>>>>>>> serv.servP4lang.sendLine:servP4lang.java:560 tx: bierlabel4_mod 2
>>>>>>>> 56298 252905 3 3 62714 800735 0 0 0 0 0 0 0 16
>>>>>>>> 2021-02-04 16:34:35.695 debug
>>>>>>>> serv.servP4lang.sendLine:servP4lang.java:560 tx: bierlabloc4_mod 2
>>>>>>>> 56298 252905 0 0 0 0 0 0 0 2
>>>>>>>> sid#
>>>>>>>> sid#show mpls forwarding 252905
>>>>>>>> category     Â
>>>>>>>>    value
>>>>>>>> label      Â
>>>>>>>>      252905
>>>>>>>> key      Â
>>>>>>>> Â Â Â Â Â Â ÂÂ
>>>>>>>> 22-bgp bier
>>>>>>>> working     Â
>>>>>>>>     true
>>>>>>>> forwarder     Â
>>>>>>>>   v2:4
>>>>>>>> interface     Â
>>>>>>>>   null
>>>>>>>> nexthop     Â
>>>>>>>>     null
>>>>>>>> remote label     unlabelled
>>>>>>>> need local     Â
>>>>>>>>  false
>>>>>>>> bier base     Â
>>>>>>>>   252905
>>>>>>>> bier bsl     Â
>>>>>>>>    3-256
>>>>>>>> bier si     Â
>>>>>>>>     0
>>>>>>>> bier sis     Â
>>>>>>>>    0
>>>>>>>> bier idx     Â
>>>>>>>>    2
>>>>>>>> bier idx2Â Â Â Â Â Â
>>>>>>>>   0
>>>>>>>> bier local     Â
>>>>>>>>  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>>>>>>>> 00 00 00 00 00 00 00 00 00 00 00 00 02
>>>>>>>> bier peer     Â
>>>>>>>>   1.1.1.2 sdn1 lab=540419 00 00 00 00 00
>>>>>>>> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>>>>>>>> 00 00 00 04
>>>>>>>> bier peer     Â
>>>>>>>>   1.1.1.6 sdn2 lab=761055 00 00 00 00 00
>>>>>>>> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>>>>>>>> 00 00 00 08
>>>>>>>> bier peer     Â
>>>>>>>>   1.1.1.10 sdn3 lab=800735 00 00 00 00
>>>>>>>> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>>>>>>>> 00 00 00 00 10
>>>>>>>> pwe iface     Â
>>>>>>>>   null
>>>>>>>> pwe del     Â
>>>>>>>>     0
>>>>>>>> pwe add     Â
>>>>>>>>     n/a
>>>>>>>> counter     Â
>>>>>>>>     tx=0(0) rx=0(0) drp=0(0)
>>>>>>>> hardware counter null
>>>>>>>> sid#
>>>>
>> <rtrp4lang-bmv2-.csv><rtrp4lang-bmv2-.html><rtrp4lang-dpdk-.csv><rtrp4lang-dpdk-.html>
>
>




Archive powered by MHonArc 2.6.19.

Top of Page