Interface Tables
-
- All Superinterfaces:
org.opendaylight.yangtools.yang.binding.Augmentable<Tables>
,org.opendaylight.yangtools.yang.binding.BindingObject
,org.opendaylight.yangtools.yang.binding.ChildOf<NetworkInstance>
,org.opendaylight.yangtools.yang.binding.DataContainer
,org.opendaylight.yangtools.yang.binding.DataObject
public interface Tables extends org.opendaylight.yangtools.yang.binding.ChildOf<NetworkInstance>, org.opendaylight.yangtools.yang.binding.Augmentable<Tables>
The routing tables that are managed by this network instanceThis class represents the following YANG schema fragment defined in module openconfig-network-instance
container tables { list table { key table-name; leaf table-name { type leafref { path ../config/table-name; } } container config { uses table-config; } container state { config false; uses table-config; } } }
The schema path to identify an instance is openconfig-network-instance/network-instance-top/network-instances/network-instance/tablesTo create instances of this class use
TablesBuilder
.- See Also:
TablesBuilder
-
-
Field Summary
Fields Modifier and Type Field Description static @NonNull org.opendaylight.yangtools.yang.common.QName
QNAME
-
Method Summary
All Methods Instance Methods Abstract Methods Default Methods Modifier and Type Method Description @Nullable List<Table>
getTable()
A network instance manages one or more forwarding or routing tables.default Class<Tables>
implementedInterface()
default @NonNull List<Table>
nonnullTable()
-
-
-
Method Detail
-
implementedInterface
default Class<Tables> implementedInterface()
- Specified by:
implementedInterface
in interfaceorg.opendaylight.yangtools.yang.binding.DataContainer
- Specified by:
implementedInterface
in interfaceorg.opendaylight.yangtools.yang.binding.DataObject
-
getTable
@Nullable List<Table> getTable()
A network instance manages one or more forwarding or routing tables. These may reflect the Layer 2 forwarding information base, the Layer 3 routing information base of the MPLS LFIB. Protocols may be explictly associated with a particular table into which they populate entries. Multiple protocols may install entries into a single table, or there may be a 1:1 relationship between a routing protocol and a table .The import-policy and export-policy lists are used to specify how routes leak between different tables within the same forwarding instance.- Returns:
java.util.List
table
, ornull
if not present
-
-