Interface Tables
- All Superinterfaces:
- org.opendaylight.yangtools.binding.Augmentable<Tables>,- org.opendaylight.yangtools.binding.BindingContract<org.opendaylight.yangtools.binding.DataContainer>,- org.opendaylight.yangtools.binding.BindingObject,- org.opendaylight.yangtools.binding.ChildOf<NetworkInstance>,- org.opendaylight.yangtools.binding.DataContainer,- org.opendaylight.yangtools.binding.DataObject
@Generated("mdsal-binding-generator")
public interface Tables
extends org.opendaylight.yangtools.binding.ChildOf<NetworkInstance>, org.opendaylight.yangtools.binding.Augmentable<Tables>
The routing tables that are managed by this network instance
 
This 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;
     }
   }
 }
 
 To create instances of this class use TablesBuilder.
- See Also:
- 
Field SummaryFieldsModifier and TypeFieldDescriptionstatic final @NonNull org.opendaylight.yangtools.yang.common.QNameYANG identifier of the statement represented by this class.
- 
Method SummaryModifier and TypeMethodDescriptionstatic booleanbindingEquals(@NonNull Tables thisObj, Object obj) Default implementation ofObject.equals(Object)contract for this interface.static intbindingHashCode(@NonNull Tables obj) Default implementation ofObject.hashCode()contract for this interface.static StringbindingToString(@NonNull Tables obj) Default implementation ofObject.toString()contract for this interface.getTable()Return table, ornullif it is not present.Return table, or an empty list if it is not present.Methods inherited from interface org.opendaylight.yangtools.binding.Augmentableaugmentation, augmentationOrElseThrow, augmentationOrElseThrow, augmentations
- 
Field Details- 
QNAMEstatic final @NonNull org.opendaylight.yangtools.yang.common.QName QNAMEYANG identifier of the statement represented by this class.
 
- 
- 
Method Details- 
implementedInterface- Specified by:
- implementedInterfacein interface- org.opendaylight.yangtools.binding.BindingContract<org.opendaylight.yangtools.binding.DataContainer>
- Specified by:
- implementedInterfacein interface- org.opendaylight.yangtools.binding.DataObject
 
- 
bindingHashCodeDefault implementation ofObject.hashCode()contract for this interface. Implementations of this interface are encouraged to defer to this method to get consistent hashing results across all implementations.- Parameters:
- obj- Object for which to generate hashCode() result.
- Returns:
- Hash code value of data modeled by this interface.
- Throws:
- NullPointerException- if- objis- null
 
- 
bindingEqualsDefault implementation ofObject.equals(Object)contract for this interface. Implementations of this interface are encouraged to defer to this method to get consistent equality results across all implementations.- Parameters:
- thisObj- Object acting as the receiver of equals invocation
- obj- Object acting as argument to equals invocation
- Returns:
- True if thisObj and obj are considered equal
- Throws:
- NullPointerException- if- thisObjis- null
 
- 
bindingToStringDefault implementation ofObject.toString()contract for this interface. Implementations of this interface are encouraged to defer to this method to get consistent string representations across all implementations.- Parameters:
- obj- Object for which to generate toString() result.
- Returns:
- Stringvalue of data modeled by this interface.
- Throws:
- NullPointerException- if- objis- null
 
- 
getTableReturn table, ornullif it is not present.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:
- Map<TableKey, Table>table, or- nullif it is not present.
 
- 
nonnullTableReturn table, or an empty list if it is not present.- Returns:
- Map<TableKey, Table>table, or an empty list if it is not present.
 
 
-