11 - Channel (multicast flow) configuration and deploying information management.
15 - Common YANG models collection.
19 - South-bound NETCONF interface for BIER, it has implemented standard interface (ietf-bier).
20 If your BFR's NETCONF interface is Non-standard, you should add your own interface for driver.
24 - Adapter for different BIER south-bound NETCONF interfaces.
28 - Major processor function for BIER.
32 - BIER topology management.
40 - This feature contains all other features/bundles of BIER project. If you
41 install it, it provides all functions that the BIER project can support.
45 - This feature contains all models of BIER project, such as ietf-bier,
46 ietf-multicast-information and so on.
48 - **odl-bier-topomanager**
50 - This feature generates BIER's topology from network topology which discovered
53 - **odl-bier-topomanager-api**
55 - This feature provides all APIs about BIER topology.
57 - **odl-bier-topomanager-rest**
59 - This feature provides function of BIER topology management, such as configure
60 BIER domain, sub-domain, nodes, and user can invoke these RPCs via RESTCONF.
62 - **odl-bier-topomanager-ui**
64 - This feature can display bier-topo-manager's APIs on UIs (odl-mdsal-apidocs and
67 - **odl-bier-topomanager-cli**
69 - This feature provides Karaf commands for BIER topo-manager debugging, which is
70 useful for troubleshooting.
72 - **odl-bier-channel**
74 - This feature provides function about multicast flow information configuration
75 and deployment in BIER domain.
77 - **odl-bier-channel-api**
79 - This feature provides all APIs about multicast flow configuration and deployment.
81 - **odl-bier-channel-rest**
83 - This feature provides function of BIER multicast information management, such as configure
84 multicast, deploying BFIR and BFER in BIER domain, and user can invoke these RPCs via RESTCONF.
86 - **odl-bier-channel-ui**
88 - This feature can display bier-channel's APIs on UIs (odl-mdsal-apidocs and odl-dlux-yangui).
90 - **odl-bier-channel-cli**
92 - This feature provides Karaf commands for bier-channel debugging, which is useful for
95 - **odl-bier-service**
97 - This feature provides function which processing the result of BIER topo-mamager and BIER
98 channel-mamager, and invoking south-bound-interface for driver.
100 - **odl-bier-service-cli**
102 - This feature provides Karaf commands for bier-service debugging, which is useful for
105 - **odl-bier-adapter**
107 - This feature provides adapter for different BIER south-bound NETCONF
108 interfaces, so all BFRs in BIER domain with different NETCONF
109 configuration interfaces and they can operate normally together.
111 - **odl-bier-driver**
113 - This feature is south-bound NETCONF interface for BIER, it has implemented standard interface
114 (ietf-bier). If your BFR's NETCONF interface is Non-standard, you should add your own
115 interface for driver.
120 The sections below give details about the configuration settings for
121 the components that can be configured.
129 - bier/topomanager/api/src/main/yang/bier-topology-api.yang
133 - Load BIER topology, and list all topo-name in all BIER topologies.
135 - **configure-domain**
137 - Configure domain in given BIER topology.
139 - **configure-subdomain**
141 - Configure sub-domain in given BIER domain and topology.
145 - Configure node information in given topology, which defined in ietf-bier,
146 such as domains, sub-domains, bitstringlength, bfr-id, encapsulation-type, etc.
150 - Delete given domain in given topology.
152 - **delete-subdomain**
154 - Delete given sub-domain in given domain and topology.
158 - Delete given node which be assigned to given sub-domain and domain in
163 - Query given topology in BIER topology, and then display this
164 topology's detail, such as information of node and link.
168 - Query given nodes in given topology, and then display these nodes'
169 detail, such as information of node-name, router-id,
170 termination-point list, BIER domain and sub-domain list, etc.
174 - Query given link in given topology, and then display this link's detail.
178 - Query domain in given BIER topology, and then display the domain-id list.
180 - **query-subdomain**
182 - Query sub-domain in given domain and given topology, and then display
183 the sub-domain-id list.
185 - **query-subdomain-node**
187 - Query nodes which have been assigned to given sub-domain and domain in given
188 topology, and then display these nodes' details.
190 - **query-subdomain-link**
192 - Query links which have been assigned to given sub-domain and domain in given
193 topology, and then display these links' details.
196 Parameters Description
197 ^^^^^^^^^^^^^^^^^^^^^^
201 - BIER topology identifier.
205 - Node identifier in network topology.
209 - Node’s latitude, default value is 0.
213 - Node’s longitude, default value is 0.
217 - Termination point identifier.
221 - BIER domain identifier.
223 - **encapsulation-type**
225 - Base identity for BIER encapsulation. Default value is "bier-encapsulation-mpls".
227 - **bitstringlength**
229 - The bitstringlength type for imposition mode. It's value can be chosen from 64,
230 128, 256, 512, 1024, 2048, and 4096.
232 - The BitStringLength ("Imposition BitStringLength") and sub-domain ("Imposition
233 sub-domain") to use when it imposes (as a BFIR) a BIER encapsulation on a
234 particular set of packets.
238 - BIER bfr identifier. BFR-id is a number in the range [1, 65535].
240 - Bfr-id is unique within the sub-domain. A BFR-id is a small unstructured positive
241 integer. For instance, if a particular BIER sub-domain contains 1, 374 BFRs, each
242 one could be given a BFR-id in the range 1-1374.
244 - If a given BFR belongs to more than one sub-domain, it may (though it need not)
245 have a different BFR-id for each sub-domain.
247 - **ipv4-bfr-prefix**
249 - BIER BFR IPv4 prefix.
251 - A BFR's BFR-Prefix MUST be an IP address (either IPv4 or IPv6) of the BFR, and MUST be
252 unique and routable within the BIER domain. It is RECOMMENDED that the BFR-prefix be a
253 loopback address of the BFR. Two BFRs in the same BIER domain MUST NOT be assigned the
254 same BFR-Prefix. Note that a BFR in a given BIER domain has the same BFR-prefix in all
255 the sub-domains of that BIER domain.
257 - **ipv6-bfr-prefix**
259 - BIER BFR IPv6 prefix.
263 - Sub-domain identifier. Each sub-domain is identified by a sub-domain-id in the range [0, 255].
265 - A BIER domain may contain one or more sub-domains. Each BIER domain MUST contain at least one
266 sub-domain, the "default sub-domain" (also denoted "sub-domain zero"). If a BIER domain
267 contains more than one sub-domain, each BFR in the domain MUST be provisioned to know the set
268 of sub-domains to which it belongs.
272 - The IGP type. Enum type contains OSPF and ISIS.
276 - Multi-topology associated with BIER sub-domain.
278 - **bitstringlength**
280 - Disposition bitstringlength.
282 - The BitStringLengths ("Disposition BitStringLengths") that it will process when
283 (as a BFR or BFER) it receives packets from a particular sub-domain.
285 - **bier-mpls-label-base**
287 - BIER mpls-label, range in [0, 1048575].
289 - **bier-mpls-label-range-size**
291 - BIER mpls-label range size.
295 - The identifier of a link in the topology.
297 - A link is specific to a topology to which it belongs.
302 - Source node identifier, must be in same topology.
306 - Termination point within source node that terminates the link.
310 - Destination node identifier and must be in same topology.
314 - Termination point within destination node that terminates the link.
318 - The link delay, default value is 0.
322 - The number of packet loss on the link and default value is 0.
330 - bier/channel/api/src/main/yang/bier-channel-api.yang
334 - Display all channel's names in given BIER topology.
338 - Query specific channel in given topology and display this channel's information (multicast
339 flow information and related BFIR,BFER information).
343 - Create channel with multicast information in given BIER topology.
347 - Modify the channel's information which created above.
351 - Remove given channel in given topology.
355 - Deploy channel, and configure BFIR and BFERs about this multicast flow in given topology.
357 Parameters Description
358 ^^^^^^^^^^^^^^^^^^^^^^
362 - BIER topology identifier.
366 - BIER channel (multicast flow information) name.
370 - The IPv4 of multicast source. The value set to zero means that the receiver interests in
371 all source that relevant to one group.
375 - The IPv4 of multicast group.
379 - BIER domain identifier.
383 - BIER sub-domain identifier.
385 - **source-wildcard**
387 - The wildcard information of source, in the range [1, 32].
391 - The wildcard information of multi-cast group, in the range [1, 32].
395 - BFIR (Bit-Forwarding Ingress Router).
399 - The bfr-id of BRIR.
403 - BFER (Bit-Forwarding Egress Router).
407 - The bfr-id of BRER.
409 .. note:: For more information about BIER terminology, see `YANG Data Model for BIER Protocol <https://datatracker.ietf.org/doc/draft-ietf-bier-bier-yang/?include_text=1>`_.
412 Sample Configurations
413 ---------------------
415 1. Configure Domain And Sub-domain
416 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
418 1.1. Configure Domain
419 ^^^^^^^^^^^^^^^^^^^^^
421 **REST API** : *POST /restconf/operations/bier-topology-api:configure-domain*
429 "topo-id": " flow:1" ,
441 1.2. Configure Sub-domain
442 ^^^^^^^^^^^^^^^^^^^^^^^^^
444 **REST API** : *POST /restconf/operations/bier-topology-api:configure-subdomain*
452 "topo-id": " flow:1" ,
456 "sub-domain-id":" 0",
465 2. Configure BIER Node
466 ~~~~~~~~~~~~~~~~~~~~~~
468 **REST API** : *POST /restconf/operations/bier-topology-api:configure-node*
476 "topology-id": "flow:1",
477 "node-id": "openflow:3",
484 "sub-domain-id": "0",
488 "bitstringlength": "64-bit",
492 "bitstringlength": "64",
493 "bier-mpls-label-base": "56",
494 "bier-mpls-label-range-size": "100"
500 "encapsulation-type": "bier-encapsulation-mpls",
501 "bitstringlength": "64-bit",
503 "ipv4-bfr-prefix": "192.168.1.1/24",
504 "ipv6-bfr-prefix": "1030:0:0:0:C9B4:FF12:48AA:1A2B/60"
511 3. Query BIER Topology Information
512 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
517 **REST API** : *POST /restconf/operations/bier-topology-api:load-topology*
524 **REST API** : *POST /restconf/operations/bier-topology-api:query-topology*
539 **REST API** : *POST /restconf/operations/bier-topology-api:query-node*
547 "topo-id": " flow:1",
548 "node-id": "openflow:3"
555 **REST API** : *POST /restconf/operations/bier-topology-api:query-link*
563 "topo-id": " flow:1",
564 "node-id": "openflow:3"
571 **REST API** : *POST /restconf/operations/bier-topology-api:query-domain*
583 3.6. Query Sub-domain
584 ^^^^^^^^^^^^^^^^^^^^^
586 **REST API** : *POST /restconf/operations/bier-topology-api:query-subdomain*
594 "topo-id": " flow:1",
599 3.7. Query Sub-domain Node
600 ^^^^^^^^^^^^^^^^^^^^^^^^^^
602 **REST API** : *POST /restconf/operations/bier-topology-api:query-subdomain-node*
610 "topology-id": "flow:1",
616 3.8. Query Sub-domain Link
617 ^^^^^^^^^^^^^^^^^^^^^^^^^^
619 **REST API** : *POST /restconf/operations/bier-topology-api:query-subdomain-link*
627 "topology-id": "flow:1",
633 4. BIER Channel Configuration
634 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
636 4.1. Configure Channel
637 ^^^^^^^^^^^^^^^^^^^^^^
639 **REST API** : *POST /restconf/operations/bier-channel-api:add-channel*
647 "topology-id": "flow:1",
650 "dst-group": "224.1.1.1",
652 "sub-domain-id": "11",
653 "source-wildcard": "24",
654 "group-wildcard": "30"
661 **REST API** : *POST /restconf/operations/bier-channel-api:modify-channel*
669 "topology-id": "flow:1",
672 "dst-group": "225.1.1.1",
674 "sub-domain-id": "11",
675 "source-wildcard": "24",
676 "group-wildcard": "30"
683 **REST API** : *POST /restconf/operations/bier-channel-api:deploy-channel*
691 "topology-id": "flow:1",
692 "channel-name": "channel-1",
693 "ingress-node": "node1",
705 6. Query Channel Information
706 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
711 **REST API** : *POST /restconf/operations/bier-channel-api:get-channel*
719 "topology-id": "flow:1"
726 **REST API** : *POST /restconf/operations/bier-channel-api:query-channel*
734 "topology-id": "flow:1",
745 **REST API** : *POST /restconf/operations/bier-channel-api:remove-channel*
753 "topology-id": "flow:1",
754 "channel-name": "channel-1"
758 8. Delete BIER Topology Configuration
759 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
761 8.1. Delete BIER Node
762 ^^^^^^^^^^^^^^^^^^^^^
764 **REST API** : *POST /restconf/operations/bier-topology-api:delete-node*
773 "node-id": " openflow:3",
779 8.2. Delete Sub-domain
780 ^^^^^^^^^^^^^^^^^^^^^^
782 **REST API** : *POST /restconf/operations/bier-topology-api:delete-subdomian*
799 **REST API** : *POST /restconf/operations/bier-topology-api:delete-domian*