State¶
Leafs
-
class
NetworkInstances.NetworkInstance.Protocols.Protocol.Isis.Levels.Level.LinkStateDatabase.Lsp.Tlvs.Tlv.MtIpv4Reachability.Prefixes.Prefix.Subtlvs.Subtlv.Ipv4SourceRouterId.State¶ Bases:
EntityClass Hierarchy:
NetworkInstancesNetworkInstanceProtocolsProtocolIsisLevelsLevelLinkStateDatabaseLspTlvsTlvMtIpv4ReachabilityPrefixesPrefixSubtlvsSubtlvIpv4SourceRouterIdStateThis class represents state data.
State parameters of sub-TLV 11.
-
type¶ The type of subTLV being described. The type of subTLV is expressed as a canonical name
type: one of the below values:
ISREACHABILITYSUBTLVSTYPEISREACHABILITYIPV4INTERFACEADDRESSISREACHABILITYIPV4NEIGHBORADDRESSISREACHABILITYMAXLINKBANDWIDTHISREACHABILITYMAXRESERVABLEBANDWIDTHISREACHABILITYUNRESERVEDBANDWIDTHISREACHABILITYIPV6INTERFACEADDRESSISREACHABILITYIPV6NEIGHBORADDRESSISREACHABILITYEXTENDEDADMINGROUPISREACHABILITYLINKPROTECTIONTYPEISREACHABILITYBANDWIDTHCONSTRAINTSISREACHABILITYUNCONSTRAINEDLSPISREACHABILITYLINKDELAYVARIATIONISREACHABILITYRESIDUALBANDWIDTHISREACHABILITYAVAILABLEBANDWIDTHconfig: False
-
router_id¶ IPv4 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-9]|[1-9][0-9]|1[0-9][0-9]|2[0-4][0-9]|25[0-5])\.){3}([0-9]|[1-9][0-9]|1[0-9][0-9]|2[0-4][0-9]|25[0-5])$config: False
-