State

Leafs

class NetworkInstances.NetworkInstance.Protocols.Protocol.Isis.Levels.Level.LinkStateDatabase.Lsp.Tlvs.Tlv.ExtendedIpv4Reachability.Prefixes.Prefix.Subtlvs.Subtlv.Ipv6SourceRouterId.State

Bases: Entity

Class Hierarchy: NetworkInstances NetworkInstance Protocols Protocol Isis Levels Level LinkStateDatabase Lsp Tlvs Tlv ExtendedIpv4Reachability Prefixes Prefix Subtlvs Subtlv Ipv6SourceRouterId State

This class represents state data.

State parameters of sub-TLV 12.

type

The type of subTLV being described. The type of subTLV is expressed as a canonical name

type: one of the below values: ISREACHABILITYSUBTLVSTYPE

ISREACHABILITYADMINGROUP

ISREACHABILITYLINKID

ISREACHABILITYIPV4INTERFACEADDRESS

ISREACHABILITYIPV4NEIGHBORADDRESS

ISREACHABILITYMAXLINKBANDWIDTH

ISREACHABILITYMAXRESERVABLEBANDWIDTH

ISREACHABILITYUNRESERVEDBANDWIDTH

ISREACHABILITYIPV6INTERFACEADDRESS

ISREACHABILITYIPV6NEIGHBORADDRESS

ISREACHABILITYEXTENDEDADMINGROUP

ISREACHABILITYTEDEFAULTMETRIC

ISREACHABILITYLINKATTRIBUTES

ISREACHABILITYLINKPROTECTIONTYPE

ISREACHABILITYBANDWIDTHCONSTRAINTS

ISREACHABILITYUNCONSTRAINEDLSP

ISREACHABILITYADJSID

ISREACHABILITYADJLANSID

ISREACHABILITYLINKDELAY

ISREACHABILITYMINMAXLINKDELAY

ISREACHABILITYLINKDELAYVARIATION

ISREACHABILITYLINKLOSS

ISREACHABILITYRESIDUALBANDWIDTH

ISREACHABILITYAVAILABLEBANDWIDTH

ISREACHABILITYUTILIZEDBANDWIDTH

IPREACHABILITYSUBTLVSTYPE

IPREACHABILITYTAG

IPREACHABILITYTAG64

IPREACHABILITYPREFIXSID

IPREACHABILITYPREFIXFLAGS

IPREACHABILITYIPV4ROUTERID

IPREACHABILITYIPV6ROUTERID

ROUTERCAPABILITYSUBTLVSTYPE

ROUTERCAPABILITYSRCAPABILITY

ROUTERCAPABILITYSRALGORITHM

config: False

router_id

IPv6 Source router ID address. In cases where the advertisement is an identifier for the advertising router (e.g., with the N-flag set in the Prefix Attribute Flags sub-TLV), it may be useful for other routers to know the source of the advertisement. When reachability advertisement is leaked from one level to another, Router ID advertised is always the Router ID of the IS-IS instance that originated the advertisement. This would be true even if the prefix had been learned from another protocol

type: str

pattern: ^(([0-9a-fA-F]{1,4}:){7}[0-9a-fA-F]{1,4}|([0-9a-fA-F]{1,4}:){1,7}:|([0-9a-fA-F]{1,4}:){1,6}:[0-9a-fA-F]{1,4}|([0-9a-fA-F]{1,4}:){1,5}(:[0-9a-fA-F]{1,4}){1,2}|([0-9a-fA-F]{1,4}:){1,4}(:[0-9a-fA-F]{1,4}){1,3}|([0-9a-fA-F]{1,4}:){1,3}(:[0-9a-fA-F]{1,4}){1,4}|([0-9a-fA-F]{1,4}:){1,2}(:[0-9a-fA-F]{1,4}){1,5}|[0-9a-fA-F]{1,4}:((:[0-9a-fA-F]{1,4}){1,6})|:((:[0-9a-fA-F]{1,4}){1,7}|:))$

config: False