A set of FRINX augmentations for aclunit
frinx-acl-extension
frinx-openconfig-acl
A set of FRINX augmentations for bgpunit
frinx-openconfig-network-instance
A set of FRINX augmentations for configurationunit
frinx-configuration-metadata
A set of FRINX augmentations for ioscdpunit
frinx-cdp
A set of FRINX augmentations for iosinterfaceunit
frinx-openconfig-if-ip
frinx-openconfig-interfaces
frinx-openconfig-vlan
A set of FRINX augmentations for iosnetworkinstanceunit
frinx-openconfig-network-instance
A set of FRINX augmentations for lldpunit
frinx-openconfig-lldp
A set of FRINX augmentations for localroutingunit
frinx-openconfig-network-instance
A set of FRINX augmentations for mplsunit
frinx-openconfig-network-instance
frinx-cisco-mpls-te-extension
A set of FRINX augmentations for ospfunit
frinx-openconfig-network-instance
A set of FRINX augmentations for platformunit
frinx-openconfig-platform
A set of FRINX augmentations for ribunit
frinx-openconfig-rib-bgp
A set of FRINX augmentations for routingpolicyunit
frinx-openconfig-routing-policy
frinx-openconfig-bgp-policy
A set of FRINX augmentations for ioscliinitializerunit
A set of FRINX augmentations for aclunit
frinx-acl-extension
frinx-openconfig-acl
A set of FRINX augmentations for bgpunit
frinx-openconfig-network-instance
frinx-bgp-extension
A set of FRINX augmentations for configurationunit
frinx-configuration-metadata
A set of FRINX augmentations for evpnunit
frinx-evpn
A set of FRINX augmentations for hsrpunit
frinx-hsrp
A set of FRINX augmentations for iosxrbfdunit
A set of FRINX augmentations for iosxrinterfaceunit
frinx-cisco-if-extension
frinx-openconfig-if-aggregate
frinx-oam
frinx-bfd
frinx-if-ethernet-extension
frinx-openconfig-if-ethernet
frinx-damping
frinx-openconfig-if-ip
frinx-openconfig-interfaces
frinx-openconfig-vlan
A set of FRINX augmentations for iosxrisisunit
frinx-openconfig-network-instance
frinx-isis-extension
A set of FRINX augmentations for iosxrlacpunit
A set of FRINX augmentations for iosxrnetflowunit
frinx-netflow
A set of FRINX augmentations for iosxrnetworkinstanceunit
frinx-openconfig-network-instance
A set of FRINX augmentations for iosxroamunit
frinx-oam
A set of FRINX augmentations for lldpunit
frinx-openconfig-lldp
A set of FRINX augmentations for loggingunit
frinx-logging
A set of FRINX augmentations for lrunit
frinx-openconfig-network-instance
A set of FRINX augmentations for mplsunit
frinx-openconfig-network-instance
frinx-cisco-mpls-te-extension
A set of FRINX augmentations for ospfunit
frinx-bfd-extension
frinx-openconfig-network-instance
frinx-cisco-ospf-extension
A set of FRINX augmentations for ospfv3unit
frinx-openconfig-network-instance
frinx-ospfv3
A set of FRINX augmentations for routingpolicyunit
frinx-openconfig-routing-policy
frinx-openconfig-bgp-policy
A set of FRINX augmentations for snmpunit
frinx-snmp
A set of FRINX augmentations for xrplatformunit
frinx-openconfig-platform
A set of FRINX augmentations for xrqosunit
frinx-openconfig-qos
A set of FRINX augmentations for iosxrcliinitializerunit
A set of FRINX augmentations for brocadecdpunit
A set of FRINX augmentations for brocadecliinitializerunit
A set of FRINX augmentations for brocadeinterfaceunit
frinx-openconfig-if-ethernet
frinx-openconfig-if-ip
frinx-openconfig-interfaces
frinx-openconfig-vlan
A set of FRINX augmentations for brocadeisisunit
frinx-openconfig-network-instance
A set of FRINX augmentations for brocadenetworkinstanceunit
frinx-openconfig-network-instance
A set of FRINX augmentations for brocadestpunit
frinx-stp
A set of FRINX augmentations for configurationunit
frinx-configuration-metadata
A set of FRINX augmentations for aclunit
frinx-openconfig-acl
A set of FRINX augmentations for configurationunit
frinx-configuration-metadata
A set of FRINX augmentations for junosinterfaceunit
frinx-openconfig-if-ip
frinx-openconfig-interfaces
frinx-openconfig-vlan
A set of FRINX augmentations for junosnetworkinstanceunit
frinx-openconfig-network-instance
frinx-juniper-pf-interfaces-extension
A set of FRINX augmentations for ospfunit
frinx-bfd-extension
frinx-openconfig-network-instance
A set of FRINX augmentations for routingpolicyunit
frinx-openconfig-routing-policy
frinx-openconfig-ospf-policy
frinx-openconfig-network-instance-policy
A set of FRINX augmentations for junoscliinitializerunit
A set of FRINX augmentations for configurationunit
frinx-configuration-metadata
A set of FRINX augmentations for nexuscliinitializerunit
A set of FRINX augmentations for nexusinterfaceunit
frinx-cisco-if-extension
frinx-openconfig-if-ethernet
frinx-openconfig-if-ip
frinx-openconfig-interfaces
frinx-openconfig-vlan
A set of FRINX augmentations for nexuslldpunit
frinx-openconfig-lldp
A set of FRINX augmentations for configurationunit
frinx-configuration-metadata
A set of FRINX augmentations for noscliinitializerunit
A set of FRINX augmentations for noscliinterfaceunit
frinx-openconfig-if-aggregate
frinx-l3ipvlan
frinx-openconfig-if-ethernet
frinx-openconfig-if-ip
frinx-openconfig-interfaces
frinx-openconfig-vlan
A set of FRINX augmentations for nosnetworkinstanceunit
frinx-openconfig-network-instance
A set of FRINX augmentations for platformunit
frinx-openconfig-platform
A set of FRINX augmentations for routingpolicyunit
frinx-openconfig-routing-policy
frinx-openconfig-bgp-policy
A set of FRINX augmentations for vrpclibgpunit
frinx-openconfig-network-instance
A set of FRINX augmentations for vrpcliinitializerunit
A set of FRINX augmentations for vrpcliinterfaceunit
frinx-openconfig-if-ip
frinx-openconfig-interfaces
frinx-openconfig-vlan
A set of FRINX augmentations for vrpnetworkinstanceunit
frinx-openconfig-network-instance
A set of FRINX augmentations for aclunit
frinx-openconfig-acl
A set of FRINX augmentations for bfdunit
A set of FRINX augmentations for bgpunit
frinx-openconfig-network-instance
A set of FRINX augmentations for configmetadataunit
frinx-configuration-metadata
A set of FRINX augmentations for interfacesunit
frinx-openconfig-if-aggregate
frinx-bfd
frinx-openconfig-if-ethernet
frinx-damping
frinx-openconfig-if-ip
frinx-openconfig-interfaces
A set of FRINX augmentations for lacpunit
A set of FRINX augmentations for mplsunit
frinx-openconfig-network-instance
A set of FRINX augmentations for networkunit
frinx-openconfig-network-instance
A set of FRINX augmentations for ospfunit
frinx-openconfig-network-instance
A set of FRINX augmentations for policyunit
frinx-openconfig-network-instance
frinx-juniper-pf-interfaces-extension
A set of FRINX augmentations for snmpunit
frinx-snmp
A set of FRINX augmentations for aclunit
frinx-openconfig-acl
A set of FRINX augmentations for configmetadataunit
frinx-configuration-metadata
A set of FRINX augmentations for interfacesunit
frinx-openconfig-if-ip
frinx-openconfig-interfaces
frinx-openconfig-vlan
A set of FRINX augmentations for networkunit
frinx-openconfig-network-instance
A set of FRINX augmentations for probesunit
frinx-openconfig-probes
A set of FRINX augmentations for configmetadataunit
frinx-configuration-metadata
A set of FRINX augmentations for ospfunit
frinx-openconfig-network-instance
A set of FRINX augmentations for routingunit
frinx-openconfig-routing-policy
frinx-openconfig-bgp-policy
A set of FRINX augmentations for bgpunit
frinx-openconfig-network-instance
A set of FRINX augmentations for cdpunit
frinx-cdp
A set of FRINX augmentations for configmetadataunit
frinx-configuration-metadata
A set of FRINX augmentations for isisunit
frinx-openconfig-network-instance
A set of FRINX augmentations for lldpunit
frinx-openconfig-lldp
A set of FRINX augmentations for lrunit
frinx-openconfig-network-instance
A set of FRINX augmentations for platformunit
frinx-openconfig-platform
A set of FRINX augmentations for routingunit
frinx-openconfig-routing-policy
frinx-openconfig-bgp-policy
A set of FRINX augmentations for evpnunit
frinx-evpn
A set of FRINX augmentations for isisunit
frinx-openconfig-network-instance
frinx-isis-extension
A set of FRINX augmentations for interfacesunit
frinx-cisco-if-extension
frinx-openconfig-if-aggregate
frinx-openconfig-if-ethernet
frinx-damping
frinx-openconfig-if-ip
frinx-openconfig-interfaces
frinx-openconfig-vlan
A set of FRINX augmentations for loggingunit
frinx-logging
A set of FRINX augmentations for bgpunit
frinx-openconfig-network-instance
A set of FRINX augmentations for networkunit
frinx-openconfig-network-instance
Extension to Acces Control List (ACL) implementation based on OpenConfig
frinx-openconfig-acl
frinx-openconfig-inet-types
network-topology
frinx-uniconfig-topology
yang-ext
description:
Hop count represented in inclusive range as
type: string
description:
ICMP message type
type: union
type: uint8
type: enumeration
Bidirectional Forwarding Detection (BFD) implementation based on OpenConfig interfaces
ietf-inet-types
frinx-openconfig-interfaces
frinx-openconfig-if-aggregate
iana-if-type
network-topology
frinx-uniconfig-topology
yang-ext
Extension to Bidirectional Forwarding Detection (BFD) implementation based on OpenConfig
frinx-openconfig-bfd
frinx-openconfig-inet-types
frinx-openconfig-network-instance
frinx-bfd
yang-ext
network-topology
frinx-uniconfig-topology
MISSING description!
frinx-openconfig-network-instance
frinx-openconfig-routing-policy
yang-ext
network-topology
frinx-uniconfig-topology
Extended connection-point local parameters to allow for untagged vlan endpoints
frinx-openconfig-network-instance
yang-ext
network-topology
frinx-openconfig-network-instance-types
frinx-uniconfig-topology
Set of augments needed to OpenConfig interfaces models, containing BROCADE specific features.
frinx-openconfig-interfaces
network-topology
frinx-uniconfig-topology
yang-ext
Extended interface parameters with BROCADE specific in policy-forwarding
frinx-openconfig-network-instance
yang-ext
network-topology
frinx-openconfig-network-instance-types
frinx-uniconfig-topology
This module defines configuration and operational state data for the CDP protocol. Based on openconfig LLDP
frinx-openconfig-lldp
network-topology
frinx-uniconfig-topology
description:
Top-level container for CDP configuration and state data
nodetype: container (rw)
description:
Configuration data
nodetype: container (rw)
description:
System level state of the LLDP protocol.
nodetype: leaf (rw)
type: boolean
description:
System level hello timer for the LLDP protocol.
nodetype: leaf (rw)
type: uint64
units: seconds
description:
Indicates whether the local system should suppress the
advertisement of particular TLVs with the LLDP PDUs that it
transmits. Where a TLV type is specified within this list, it
should not be included in any LLDP PDU transmitted by the
local agent.
nodetype: leaf-list (rw)
type: identityref
description:
The system name field shall contain an alpha-numeric string
that indicates the system's administratively assigned name.
The system name should be the system's fully qualified domain
name. If implementations support IETF RFC 3418, the sysName
object should be used for this field.
nodetype: leaf (rw)
type: string
description:
The system description field shall contain an alpha-numeric
string that is the textual description of the network entity.
The system description should include the full name and
version identification of the system's hardware type,
software operating system, and networking software. If
implementations support IETF RFC 3418, the sysDescr object
should be used for this field.
nodetype: leaf (rw)
type: string
description:
The Chassis ID is a mandatory TLV which identifies the
chassis component of the endpoint identifier associated with
the transmitting LLDP agent
nodetype: leaf (rw)
type: string
description:
This field identifies the format and source of the chassis
identifier string. It is an enumerator defined by the
LldpChassisIdSubtype object from IEEE 802.1AB MIB.
nodetype: leaf (rw)
type: oc-lldp-types:chassis-id-type
description:
Operational state data
nodetype: container (ro)
description:
System level state of the LLDP protocol.
nodetype: leaf (ro)
type: boolean
description:
System level hello timer for the LLDP protocol.
nodetype: leaf (ro)
type: uint64
units: seconds
description:
Indicates whether the local system should suppress the
advertisement of particular TLVs with the LLDP PDUs that it
transmits. Where a TLV type is specified within this list, it
should not be included in any LLDP PDU transmitted by the
local agent.
nodetype: leaf-list (ro)
type: identityref
description:
The system name field shall contain an alpha-numeric string
that indicates the system's administratively assigned name.
The system name should be the system's fully qualified domain
name. If implementations support IETF RFC 3418, the sysName
object should be used for this field.
nodetype: leaf (ro)
type: string
description:
The system description field shall contain an alpha-numeric
string that is the textual description of the network entity.
The system description should include the full name and
version identification of the system's hardware type,
software operating system, and networking software. If
implementations support IETF RFC 3418, the sysDescr object
should be used for this field.
nodetype: leaf (ro)
type: string
description:
The Chassis ID is a mandatory TLV which identifies the
chassis component of the endpoint identifier associated with
the transmitting LLDP agent
nodetype: leaf (ro)
type: string
description:
This field identifies the format and source of the chassis
identifier string. It is an enumerator defined by the
LldpChassisIdSubtype object from IEEE 802.1AB MIB.
nodetype: leaf (ro)
type: oc-lldp-types:chassis-id-type
description:
Global LLDP counters
nodetype: container (ro)
description:
The number of lldp frames received.
nodetype: leaf (ro)
type: yang:counter64
description:
The number of frames transmitted out.
nodetype: leaf (ro)
type: yang:counter64
description:
The number of LLDP frames received with errors.
nodetype: leaf (ro)
type: yang:counter64
description:
The number of LLDP frames received and discarded.
nodetype: leaf (ro)
type: yang:counter64
description:
The number of TLV frames received and discarded.
nodetype: leaf (ro)
type: yang:counter64
description:
The number of frames received with unknown TLV.
nodetype: leaf (ro)
type: yang:counter64
description:
Indicates the last time the counters were
cleared.
nodetype: leaf (ro)
type: yang:date-and-time
description:
The number of valid TLVs received.
nodetype: leaf (ro)
type: yang:counter64
description:
The number of entries aged out due to timeout.
nodetype: leaf (ro)
type: yang:counter64
description:
Enclosing container
nodetype: container (rw)
description:
List of interfaces on which LLDP is enabled / available
frinx-device-type:
ios
frinx-supported-versions:
12any,15any
frinx-implemented-reader:
io.frinx.cli.unit.ios.cdp.handler.InterfaceReader
frinx-implemented-reader-details:
CDP_INTER_LINE:
(?<id>\S+)\s+is .+line protocol.*
SH_CDP_INTER:
show cdp interface
frinx-implemented-writer:
MISSING WRITER
frinx-device-type:
xr
frinx-supported-versions:
6
frinx-implemented-reader:
io.frinx.unitopo.unit.xr6.cdp.InterfaceReader
frinx-implemented-writer:
MISSING WRITER
nodetype: list (rw)
list keys: [name]
description:
Reference to the list key
nodetype: leaf (list key) (rw)
type: leafref
description:
Configuration data for LLDP on each interface
frinx-device-type:
ios
frinx-supported-versions:
12any,15any
frinx-implemented-reader:
io.frinx.cli.unit.ios.cdp.handler.InterfaceConfigReader
frinx-implemented-writer:
MISSING WRITER
frinx-device-type:
xr
frinx-supported-versions:
6
frinx-implemented-reader:
io.frinx.unitopo.unit.xr6.cdp.InterfaceConfigReader
frinx-implemented-writer:
MISSING WRITER
nodetype: container (rw)
description:
Reference to the LLDP Ethernet interface
nodetype: leaf (rw)
type: oc-if:base-interface-ref
description:
Enable or disable the LLDP protocol on the interface.
nodetype: leaf (rw)
type: boolean
description:
Operational state data
nodetype: container (ro)
description:
Reference to the LLDP Ethernet interface
nodetype: leaf (ro)
type: oc-if:base-interface-ref
description:
Enable or disable the LLDP protocol on the interface.
nodetype: leaf (ro)
type: boolean
description:
LLDP counters on each interface
nodetype: container (ro)
description:
The number of lldp frames received.
nodetype: leaf (ro)
type: yang:counter64
description:
The number of frames transmitted out.
nodetype: leaf (ro)
type: yang:counter64
description:
The number of LLDP frames received with errors.
nodetype: leaf (ro)
type: yang:counter64
description:
The number of LLDP frames received and discarded.
nodetype: leaf (ro)
type: yang:counter64
description:
The number of TLV frames received and discarded.
nodetype: leaf (ro)
type: yang:counter64
description:
The number of frames received with unknown TLV.
nodetype: leaf (ro)
type: yang:counter64
description:
Indicates the last time the counters were
cleared.
nodetype: leaf (ro)
type: yang:date-and-time
description:
The number of frame transmit errors on the
interface.
nodetype: leaf (ro)
type: yang:counter64
description:
Enclosing container for list of LLDP neighbors on an
interface
nodetype: container (ro)
description:
List of LLDP neighbors
frinx-device-type:
ios
frinx-supported-versions:
12any,15any
frinx-implemented-reader:
io.frinx.cli.unit.ios.cdp.handler.NeighborReader
frinx-implemented-reader-details:
CDP_NEIGHBOR_LINE:
Device ID: (?<id>[\S]+)
SH_CDP_NEIGH:
show cdp neighbors %s detail | include Device ID|Interface
frinx-implemented-writer:
MISSING WRITER
frinx-device-type:
xr
frinx-supported-versions:
6
frinx-implemented-reader:
io.frinx.unitopo.unit.xr6.cdp.NeighborReader
frinx-implemented-writer:
MISSING WRITER
nodetype: list (ro)
list keys: [id]
description:
nodetype: leaf (list key) (ro)
type: leafref
description:
Configuration data
nodetype: container (ro)
description:
Operational state data
frinx-device-type:
ios
frinx-supported-versions:
12any,15any
frinx-implemented-reader:
io.frinx.cli.unit.ios.cdp.handler.NeighborStateReader
frinx-implemented-reader-details:
CDP_NEIGH_PORT_LINE:
.*Port ID \(outgoing port\): (?<remotePort>.+).*
frinx-implemented-writer:
MISSING WRITER
frinx-device-type:
xr
frinx-supported-versions:
6
frinx-implemented-reader:
io.frinx.unitopo.unit.xr6.cdp.NeighborStateReader
frinx-implemented-writer:
MISSING WRITER
nodetype: container (ro)
description:
The system name field shall contain an alpha-numeric string
that indicates the system's administratively assigned name.
The system name should be the system's fully qualified domain
name. If implementations support IETF RFC 3418, the sysName
object should be used for this field.
nodetype: leaf (ro)
type: string
description:
The system description field shall contain an alpha-numeric
string that is the textual description of the network entity.
The system description should include the full name and
version identification of the system's hardware type,
software operating system, and networking software. If
implementations support IETF RFC 3418, the sysDescr object
should be used for this field.
nodetype: leaf (ro)
type: string
description:
The Chassis ID is a mandatory TLV which identifies the
chassis component of the endpoint identifier associated with
the transmitting LLDP agent
nodetype: leaf (ro)
type: string
description:
This field identifies the format and source of the chassis
identifier string. It is an enumerator defined by the
LldpChassisIdSubtype object from IEEE 802.1AB MIB.
nodetype: leaf (ro)
type: oc-lldp-types:chassis-id-type
description:
System generated identifier for the neighbor on the
interface.
nodetype: leaf (ro)
type: string
description:
Age since discovery
nodetype: leaf (ro)
type: uint64
units: seconds
description:
Seconds since last update received.
nodetype: leaf (ro)
type: int64
description:
The Port ID is a mandatory TLV which identifies the port
component of the endpoint identifier associated with the
transmitting LLDP agent. If the specified port is an IEEE
802.3 Repeater port, then this TLV is optional.
nodetype: leaf (ro)
type: string
description:
This field identifies the format and source of the port
identifier string. It is an enumerator defined by the
PtopoPortIdType object from RFC2922.
nodetype: leaf (ro)
type: oc-lldp-types:port-id-type
description:
The binary string containing the actual port identifier for
the port which this LLDP PDU was transmitted. The source and
format of this field is defined by PtopoPortId from
RFC2922.
nodetype: leaf (ro)
type: string
description:
The Management Address is a mandatory TLV which identifies a
network address associated with the local LLDP agent, which
can be used to reach the agent on the port identified in the
Port ID TLV.
nodetype: leaf (ro)
type: string
description:
The enumerated value for the network address type
identified in this TLV. This enumeration is defined in the
'Assigned Numbers' RFC [RFC3232] and the
ianaAddressFamilyNumbers object.
nodetype: leaf (ro)
type: string
description:
Enclosing container for list of custom TLVs from a
neighbor
nodetype: container (ro)
description:
List of custom LLDP TLVs from a neighbor
nodetype: list (ro)
list keys: [type] [oui] [oui-subtype]
description:
Reference to type list key
nodetype: leaf (list key) (ro)
type: leafref
description:
Reference to oui list key
nodetype: leaf (list key) (ro)
type: leafref
description:
Reference to oui-subtype list key
nodetype: leaf (list key) (ro)
type: leafref
description:
Configuration data
nodetype: container (ro)
description:
Operational state data
nodetype: container (ro)
description:
The integer value identifying the type of information
contained in the value field.
nodetype: leaf (ro)
type: int32
description:
The organizationally unique identifier field shall contain
the organization's OUI as defined in Clause 9 of IEEE Std
802. The high-order octet is 0 and the low-order 3 octets
are the SMI Network Management Private Enterprise Code of
the Vendor in network byte order, as defined in the
'Assigned Numbers' RFC [RFC3232].
nodetype: leaf (ro)
type: string
description:
The organizationally defined subtype field shall contain a
unique subtype value assigned by the defining organization.
nodetype: leaf (ro)
type: string
description:
A variable-length octet-string containing the
instance-specific information for this TLV.
nodetype: leaf (ro)
type: binary
description:
Enclosing container for list of LLDP capabilities
nodetype: container (ro)
description:
List of LLDP system capabilities advertised by the
neighbor
nodetype: list (ro)
list keys: [name]
description:
Reference to capabilities list key
nodetype: leaf (list key) (ro)
type: leafref
description:
Configuration data for LLDP capabilities
nodetype: container (ro)
description:
Operational state data for LLDP capabilities
nodetype: container (ro)
description:
Name of the system capability advertised by the neighbor.
Capabilities are represented in a bitmap that defines the
primary functions of the system. The capabilities are
defined in IEEE 802.1AB.
nodetype: leaf (ro)
type: identityref
description:
Indicates whether the corresponding system capability is
enabled on the neighbor.
nodetype: leaf (ro)
type: boolean
Set of augments needed to OpenConfig interfaces models, containing CISCO specific features.
frinx-openconfig-interfaces
network-topology
frinx-uniconfig-topology
yang-ext
description:
Base identity for RPF check config
description:
Base identity for RPF check config
base identity: RPF_ALLOW_CONFIG_BASE
description:
Base identity for RPF check config
base identity: RPF_ALLOW_CONFIG_BASE
Set of augments needed to OpenConfig mpls models, containing CISCO specific features.
frinx-openconfig-network-instance
frinx-openconfig-network-instance-types
yang-ext
network-topology
frinx-uniconfig-topology
MISSING description!
frinx-openconfig-network-instance
frinx-openconfig-ospf-types
network-topology
frinx-uniconfig-topology
Extended interface parameters with CISCO specific in policy-forwarding
frinx-openconfig-network-instance
frinx-openconfig-network-instance-types
yang-ext
network-topology
frinx-uniconfig-topology
Represents metadata about device configuration.
network-topology
yang-ext
frinx-device-type:
junos
frinx-supported-versions:
173
frinx-implemented-reader:
io.frinx.unitopo.unit.junos17.configmetadata.handler.ConfigMetadataReader
frinx-implemented-writer:
MISSING WRITER
frinx-device-type:
junos
frinx-supported-versions:
14any
frinx-implemented-reader:
io.frinx.cli.unit.junos.conf.handler.ConfigMetadataReader
frinx-implemented-reader-details:
DATE_REGEX:
^## Last commit: (?<timestamp>.*)
PATTERN:
^## Last commit: (?<timestamp>.*)
SHOW_LAST_COMMIT_TIME:
show configuration | match "^## Last commit:"
frinx-implemented-writer:
MISSING WRITER
frinx-device-type:
nos
frinx-supported-versions:
any
frinx-implemented-reader:
io.frinx.cli.unit.dasan.conf.handler.ConfigMetadataReader
frinx-implemented-reader-details:
SHOW_RUNNING_CONFIG:
show running-config
frinx-implemented-writer:
MISSING WRITER
frinx-device-type:
ios
frinx-supported-versions:
12any,15any
frinx-implemented-reader:
io.frinx.cli.unit.ios.conf.handler.ConfigMetadataReader
frinx-implemented-reader-details:
DATE_REGEX:
\*(?<time>.+): (?<config>.+) Configured from (?<device>.+) by (?<user>.+).*
PATTERN:
\*(?<time>.+): (?<config>.+) Configured from (?<device>.+) by (?<user>.+).*
SHOW_LAST_COMMIT_TIME:
show history all | include Configured from
frinx-implemented-writer:
MISSING WRITER
frinx-device-type:
xr
frinx-supported-versions:
66
frinx-implemented-reader:
io.frinx.unitopo.unit.xr66.configmetadata.ConfigMetadataReader
frinx-implemented-writer:
MISSING WRITER
frinx-device-type:
nexus
frinx-supported-versions:
any
frinx-implemented-reader:
io.frinx.cli.unit.nexus.conf.handler.ConfigMetadataReader
frinx-implemented-reader-details:
DATE_REGEX:
(?<time>\d.+) (?<device>.+) (?<config>%.+): Configured from (?<user>.+).*
PATTERN:
(?<time>\d.+) (?<device>.+) (?<config>%.+): Configured from (?<user>.+).*
SHOW_LAST_COMMIT_TIME:
show logging | include "Configured from"
frinx-implemented-writer:
MISSING WRITER
frinx-device-type:
junos
frinx-supported-versions:
182
frinx-implemented-reader:
io.frinx.unitopo.unit.junos18.configmetadata.handler.ConfigMetadataReader
frinx-implemented-writer:
MISSING WRITER
frinx-device-type:
ironware
frinx-supported-versions:
any
frinx-implemented-reader:
io.frinx.cli.unit.brocade.conf.handler.ConfigMetadataReader
frinx-implemented-reader-details:
SHOW_RUNNING_CONFIG:
show running-config
frinx-implemented-writer:
MISSING WRITER
frinx-device-type:
xr
frinx-supported-versions:
6
frinx-implemented-reader:
io.frinx.unitopo.unit.xr6.configmetadata.ConfigMetadataReader
frinx-implemented-reader-details:
RECORD_TYPE_COMMIT:
commit
frinx-implemented-writer:
MISSING WRITER
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.conf.handler.ConfigMetadataReader
frinx-implemented-reader-details:
DATE_REGEX:
\s*.+\s{2,}.+\s{2,}.+\s{2,}.+\s{2,}.+\s{3,}(?<time>.+)\s*
PATTERN:
\s*.+\s{2,}.+\s{2,}.+\s{2,}.+\s{2,}.+\s{3,}(?<time>.+)\s*
SHOW_LAST_COMMIT_TIME:
show configuration commit list | utility egrep "^1 "
frinx-implemented-writer:
MISSING WRITER
nodetype: container (ro)
description:
Unique fingerprint of last configuration.
nodetype: leaf (ro)
type: string
Damping implementation based on OpenConfig interfaces
frinx-openconfig-interfaces
network-topology
frinx-uniconfig-topology
yang-ext
Set of augments needed to OpenConfig vlan models, containing dasan specific features.
frinx-openconfig-network-instance
network-topology
frinx-uniconfig-topology
Event types
description:
A base identity which can be extended to indicate different
types of events supported by a device.
description:
Link status event generated for link UP and DOWN changes.
base identity: EVENT_TYPE
This module defines configuration and operational state data for network Interface control EVPN
ietf-yang-types
frinx-openconfig-interfaces
frinx-evpn-types
network-topology
frinx-uniconfig-topology
description:
Top level configuration containers for EVPN data
frinx-device-type:
xr
frinx-supported-versions:
701
frinx-implemented-reader:
io.frinx.unitopo.unit.xr66.evpn.EvpnReader
frinx-implemented-writer:
io.frinx.unitopo.unit.xr66.evpn.EvpnWriter
nodetype: container (rw)
description:
Config container for evpn container
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.evpn.handler.EvpnConfigReader
frinx-implemented-reader-details:
COST_OUT:
cost-out
SH_EVPN:
show running-config evpn | utility egrep '^ cost\-out|^ startup\-cost\-in'
START_COST_IN:
startup\-cost\-in (?<value>[0-9]+)
frinx-implemented-writer:
io.frinx.cli.unit.iosxr.evpn.handler.EvpnConfigWriter
frinx-implemented-writer-details:
CMD_DELETE_EVPN:
no evpn
T_WRITE_EVPN:
evpn
{% if $cost_out != TRUE %}no {% endif %}cost-out
{% if $create == TRUE %}{% if $startup_cost_in %}startup-cost-in {$startup_cost_in}
{% endif %}{% else %}{% if $startup_cost_in %}startup-cost-in {$startup_cost_in}
{% elseIf $old_startup_cost_in %}no startup-cost-in {$old_startup_cost_in}
{% endif %}{% endif %}root
frinx-device-type:
xr
frinx-supported-versions:
701
frinx-implemented-reader:
MISSING READER
frinx-implemented-writer:
io.frinx.unitopo.unit.xr66.evpn.EvpnWriter
nodetype: container (rw)
description:
Is EVPN enabled
nodetype: leaf (rw)
type: boolean
description:
Is cost-out set
nodetype: leaf (rw)
type: boolean
description:
startup-cost-in value in seconds.
nodetype: leaf (rw)
type: uint32
description:
Groups of EVPN
nodetype: container (rw)
description:
List of EVPN groups, keyed by group id
frinx-device-type:
xr
frinx-supported-versions:
701
frinx-implemented-reader:
io.frinx.unitopo.unit.xr66.evpn.handler.group.EvpnGroupListReader
frinx-implemented-writer:
io.frinx.unitopo.unit.xr66.evpn.handler.group.EvpnGroupListWriter
nodetype: list (rw)
list keys: [id]
description:
References the configured group id for this EVPN group
nodetype: leaf (list key) (rw)
type: leafref
description:
Configuration data for the EVPN group
frinx-device-type:
xr
frinx-supported-versions:
701
frinx-implemented-reader:
MISSING READER
frinx-implemented-writer:
io.frinx.unitopo.unit.xr66.evpn.handler.group.EvpnGroupListWriter
nodetype: container (rw)
description:
Id of EVPN group
nodetype: leaf (rw)
type: uint32
description:
Core interfaces of EVPN group
nodetype: container (rw)
description:
List of interfaces
frinx-device-type:
xr
frinx-supported-versions:
701
frinx-implemented-reader:
io.frinx.unitopo.unit.xr66.evpn.handler.group.coreifc.EvpnGroupCoreInterfaceListReader
nodetype: list (rw)
list keys: [name]
description:
Reference to the list key
nodetype: leaf (list key) (rw)
type: leafref
description:
Configuration data for EVPN on each interface
frinx-device-type:
xr
frinx-supported-versions:
701
frinx-implemented-reader:
io.frinx.unitopo.unit.xr66.evpn.handler.group.coreifc.EvpnGroupCoreInterfaceListReader
frinx-implemented-writer:
io.frinx.unitopo.unit.xr66.evpn.handler.group.coreifc.EvpnGroupCoreInterfaceConfigWriter
nodetype: container (rw)
description:
Reference to the EVPN interface
nodetype: leaf (rw)
type: oc-if:base-interface-ref
description:
Interfaces of EVPN
nodetype: container (rw)
description:
List of interfaces
frinx-device-type:
xr
frinx-supported-versions:
701
frinx-implemented-reader:
io.frinx.unitopo.unit.xr66.evpn.handler.ifc.EvpnInterfaceListReader
frinx-implemented-writer:
io.frinx.unitopo.unit.xr66.evpn.handler.ifc.EvpnInterfaceListWriter
nodetype: list (rw)
list keys: [name]
description:
Reference to the list key
nodetype: leaf (list key) (rw)
type: leafref
description:
Configuration data for EVPN on each interface
frinx-device-type:
xr
frinx-supported-versions:
701
frinx-implemented-reader:
io.frinx.unitopo.unit.xr66.evpn.handler.ifc.EvpnInterfaceListReader
frinx-implemented-writer:
io.frinx.unitopo.unit.xr66.evpn.handler.ifc.EvpnInterfaceListWriter
nodetype: container (rw)
description:
Reference to the EVPN interface
nodetype: leaf (rw)
type: oc-if:base-interface-ref
description:
Ethernet segment of EVPN interfaces
nodetype: container (rw)
frinx-device-type:
xr
frinx-supported-versions:
701
frinx-implemented-reader:
io.frinx.unitopo.unit.xr66.evpn.handler.ifc.es.EvpnEthernetSegmentConfigReader
frinx-implemented-writer:
io.frinx.unitopo.unit.xr66.evpn.handler.ifc.es.EvpnEthernetSegmentConfigWriter
nodetype: container (rw)
description:
Identifier of ethernet segment.
nodetype: leaf (rw)
type: evpn-types:ethernet-segment-identifier
description:
Load balance mode of ethernet segment
nodetype: leaf (rw)
type: identityref
description:
BGP route target of ethernet segment
nodetype: leaf (rw)
type: yang:mac-address
description:
Core isolation group of interface
nodetype: container (rw)
description:
Config data of core isolation group
frinx-device-type:
xr
frinx-supported-versions:
701
frinx-implemented-reader:
io.frinx.unitopo.unit.xr66.evpn.handler.ifc.core.isolation.group.EvpnCoreIsolationGroupConfigReader
frinx-implemented-writer:
io.frinx.unitopo.unit.xr66.evpn.handler.ifc.core.isolation.group.EvpnCoreIsolationGroupConfigWriter
nodetype: container (rw)
description:
BGP route target of ethernet segment
nodetype: leaf (rw)
type: uint32
This module defines types related to EVPN configurations
description:
ethernet segment identifier
type: string
description:
Base identity for ethernet segment load balance mode.
description:
Port active mode
base identity: ES-LB-MODE
description:
Single active mode
base identity: ES-LB-MODE
This module defines configuration and operational state data for network Interface control HSRP
network-topology
frinx-uniconfig-topology
frinx-openconfig-types
description:
Top level enclosing container for HSRP model config and operational state data
nodetype: container (rw)
description:
Global config data for HSRPs
nodetype: container (rw)
description:
Interface list entries variables enclosing container
nodetype: container (rw)
description:
List of interfaces
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.hsrp.handler.HsrpInterfaceReader
frinx-implemented-reader-details:
IFACE_LINE:
interface (?<id>[\S]+)
SH_IFACES:
show running-config router hsrp | include ^ interface
frinx-implemented-writer:
MISSING WRITER
nodetype: list (rw)
list keys: [interface-id]
description:
reference to the interface-id data
nodetype: leaf (list key) (rw)
type: leafref
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.hsrp.handler.HsrpInterfaceConfigReader
frinx-implemented-reader-details:
HSRP_DELAY_LINE:
hsrp delay minimum (?<minDelay>[0-9]+) reload (?<relDelay>[0-9]+)
SH_HSRP_INTERFACE:
show running-config router hsrp interface %s
frinx-implemented-writer:
io.frinx.cli.unit.iosxr.hsrp.handler.HsrpInterfaceConfigWriter
nodetype: container (rw)
description:
The interface-id of the interface-list set
nodetype: leaf (rw)
type: string
description:
Minimum delay on every interface up event.
nodetype: leaf (rw)
type: uint32
description:
Reload delay for first interface up event.
nodetype: leaf (rw)
type: uint32
description:
List of HSRP groups, keyed by address-family, virtual router id
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.hsrp.handler.HsrpGroupReader
frinx-implemented-reader-details:
FAMILY_LINE:
\s*address-family (?<type>[^\n].*)
GROUP_LINE:
\s*hsrp (?<groupNumber>[0-9]+).*
SH_GROUPS:
show running-config router hsrp interface %s address-family %s | include ^ hsrp
SH_HSRP_INTERFACE:
show running-config router hsrp interface %s | include address-family
frinx-implemented-writer:
MISSING WRITER
nodetype: list (rw)
list keys: [address-family] [virtual-router-id]
description:
The prefix contained within the Extended Prefix LSA is an IPv4 unicast prefix
nodetype: leaf (list key) (rw)
type: leafref
description:
References the configured virtual router id for this HSRP group
nodetype: leaf (list key) (rw)
type: leafref
description:
Configuration data for the HSRP group
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.hsrp.handler.HsrpGroupConfigReader
frinx-implemented-reader-details:
GROUP_LINE:
\s*hsrp (?<groupNumber>[0-9]+) version (?<version>[0-9]+)
HSRP_LINE:
\s*hsrp (?<hsrp>[0-9]+)
PRIORITY_LINE:
\s*priority (?<priority>[0-9]+)
SH_GROUP:
show running-config router hsrp interface %s address-family %s %s
SH_GROUPS:
show running-config router hsrp interface %s address-family %s | include ^ *hsrp %s
frinx-implemented-writer:
io.frinx.cli.unit.iosxr.hsrp.handler.HsrpGroupConfigWriter
nodetype: container (rw)
description:
The address family of the prefix contained in the Extended Prefix LSA
nodetype: leaf (rw)
type: identityref
description:
Set the virtual router id for use by the HSRP group.
This usually also determines the virtual MAC address that is generated
for the HSRP group
nodetype: leaf (rw)
type: uint32
description:
Version of HSRP
nodetype: leaf (rw)
type: uint8
description:
Priority level
nodetype: leaf (rw)
type: uint8
Set of augments needed to OpenConfig interfaces models, containing LAG specific features.
frinx-openconfig-interfaces
frinx-openconfig-if-aggregate
frinx-openconfig-if-ethernet
iana-if-type
ietf-yang-types
network-topology
frinx-uniconfig-topology
yang-ext
Set of augments needed to OpenConfig interfaces models, containing ethernet specific features.
frinx-openconfig-interfaces
iana-if-type
network-topology
frinx-uniconfig-topology
yang-ext
MISSING description!
frinx-openconfig-network-instance
frinx-openconfig-routing-policy
network-topology
frinx-uniconfig-topology
yang-ext
frinx-openconfig-isis-types
frinx-openconfig-isis
description:
Isis internal level
type: enumeration
Set of augments needed to OpenConfig interfaces models, containing Juniper specific features.
frinx-openconfig-interfaces
frinx-openconfig-if-aggregate
iana-if-type
network-topology
frinx-uniconfig-topology
yang-ext
Set of augments needed to OpenConfig interfaces models, containing JUNOS specific features.
frinx-openconfig-interfaces
network-topology
frinx-uniconfig-topology
type: enumeration
Extended interface parameters with Juniper specific in policy-forwarding
frinx-openconfig-network-instance
frinx-openconfig-network-instance-types
yang-ext
network-topology
frinx-uniconfig-topology
Set of augments needed to OpenConfig interfaces models, containing Juniper specific features.
frinx-openconfig-probes
network-topology
frinx-uniconfig-topology
Set of augments needed to OpenConfig interfaces models, containing L3VLAN specific features.
frinx-openconfig-interfaces
iana-if-type
network-topology
frinx-uniconfig-topology
yang-ext
LACP LAG member implementation based on OpenConfig lacp and interfaces
frinx-openconfig-interfaces
frinx-openconfig-lacp
yang-ext
frinx-openconfig-if-ethernet
iana-if-type
network-topology
frinx-uniconfig-topology
This module is a extension of static route, to specify address-family contraint.
frinx-local-routing-types
network-topology
frinx-uniconfig-topology
frinx-openconfig-network-instance
frinx-openconfig-local-routing
yang-ext
description:
Address family contraint for static route.
nodetype: leaf (rw)
type: identityref
This module contains general type definitions for using in local-routing YANG model.
description:
Base identify type for AFI/SAFI
description:
Base identify type for IPv4 multicast address family
base identity: AFI_SAFI_TYPE
description:
Base identify type for IPv6 unicast address family
base identity: AFI_SAFI_TYPE
description:
Base identify type for IPv6 multicast address family
base identity: AFI_SAFI_TYPE
description:
Base identify type for IPv4 Unicast address family
base identity: AFI_SAFI_TYPE
System logging (syslog) implementation based on OpenConfig
frinx-openconfig-interfaces
frinx-event-types
network-topology
frinx-uniconfig-topology
description:
Enclosing container for logging data.
nodetype: container (rw)
description:
Configuration and operational state relating logging
on interfaces.
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.logging.handler.LoggingInterfacesReader
frinx-implemented-reader-details:
SH_RUN_INTERFACE_LOGGING:
show running-config | utility egrep "^interface|^ logging events link-status"
frinx-implemented-writer:
MISSING WRITER
frinx-device-type:
xr
frinx-supported-versions:
translate
frinx-implemented-reader:
io.frinx.unitopo.unit.xr66.logging.handler.LoggingInterfacesReader
frinx-implemented-writer:
MISSING WRITER
nodetype: container (rw)
description:
Configuration and operationals state relating to the
relationship between interfaces and logging.
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.logging.handler.LoggingInterfacesReader
frinx-implemented-reader-details:
SH_RUN_INTERFACE_LOGGING:
show running-config | utility egrep "^interface|^ logging events link-status"
frinx-implemented-writer:
MISSING WRITER
frinx-device-type:
xr
frinx-supported-versions:
translate
frinx-implemented-reader:
io.frinx.unitopo.unit.xr66.logging.handler.LoggingInterfacesReader
nodetype: list (rw)
list keys: [interface-id]
description:
A reference to the unique identifier for the interface
being referenced by the logging.
nodetype: leaf (list key) (rw)
type: leafref
description:
Configuration parameters relating to an interface to
logging binding.
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.logging.handler.LoggingInterfacesReader
frinx-implemented-reader-details:
SH_RUN_INTERFACE_LOGGING:
show running-config | utility egrep "^interface|^ logging events link-status"
frinx-implemented-writer:
io.frinx.cli.unit.iosxr.logging.handler.LoggingInterfaceConfigWriter
frinx-implemented-writer-details:
LOGGING_COMMAND:
logging events link-status
NO_LOGGING_COMMAND:
no logging events link-status
frinx-device-type:
xr
frinx-supported-versions:
translate
frinx-implemented-reader:
io.frinx.unitopo.unit.xr66.logging.handler.LoggingInterfacesReader
frinx-implemented-writer:
io.frinx.unitopo.unit.xr66.logging.handler.LoggingInterfacesConfigWriter
nodetype: container (rw)
description:
A unique identifier for the interface.
nodetype: leaf (rw)
type: oc-if:interface-id
description:
Event which triggers logging.
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.logging.handler.LoggingInterfacesReader
frinx-implemented-reader-details:
SH_RUN_INTERFACE_LOGGING:
show running-config | utility egrep "^interface|^ logging events link-status"
frinx-implemented-writer:
io.frinx.cli.unit.iosxr.logging.handler.LoggingInterfaceConfigWriter
frinx-implemented-writer-details:
LOGGING_COMMAND:
logging events link-status
NO_LOGGING_COMMAND:
no logging events link-status
frinx-device-type:
xr
frinx-supported-versions:
translate
frinx-implemented-reader:
io.frinx.unitopo.unit.xr66.logging.handler.LoggingInterfacesReader
frinx-implemented-writer:
io.frinx.unitopo.unit.xr66.logging.handler.LoggingInterfacesConfigWriter
nodetype: list (rw)
list keys: [event-name]
nodetype: leaf (list key) (rw)
type: identityref
description:
Operational state parameters relating to an interface to
logging binding.
nodetype: container (ro)
description:
A unique identifier for the interface.
nodetype: leaf (ro)
type: oc-if:interface-id
description:
Event which triggers logging.
nodetype: list (ro)
list keys: [event-name]
nodetype: leaf (list key) (ro)
type: identityref
description:
Reference to an interface or subinterface
nodetype: container (rw)
description:
Configured reference to interface / subinterface
nodetype: container (rw)
description:
Reference to a base interface. If a reference to a
subinterface is required, this leaf must be specified
to indicate the base interface.
nodetype: leaf (rw)
type: leafref
description:
Reference to a subinterface -- this requires the base
interface to be specified using the interface leaf in
this container. If only a reference to a base interface
is requuired, this leaf should not be set.
nodetype: leaf (rw)
type: leafref
description:
Operational state for interface-ref
nodetype: container (ro)
description:
Reference to a base interface. If a reference to a
subinterface is required, this leaf must be specified
to indicate the base interface.
nodetype: leaf (ro)
type: leafref
description:
Reference to a subinterface -- this requires the base
interface to be specified using the interface leaf in
this container. If only a reference to a base interface
is requuired, this leaf should not be set.
nodetype: leaf (ro)
type: leafref
Set of augments needed to OpenConfig mpls models, containing additional features.
frinx-openconfig-network-instance
frinx-openconfig-network-instance-types
yang-ext
network-topology
frinx-uniconfig-topology
Set of augments needed to OpenConfig mpls models, containing additional features.
frinx-openconfig-network-instance
frinx-openconfig-network-instance-types
yang-ext
network-topology
frinx-uniconfig-topology
This module defines configuration and operational state data for NetFlow.
frinx-openconfig-interfaces
network-topology
frinx-uniconfig-topology
description:
Base identity for types of NetFlow
description:
MPLS based NetFlow
base identity: NETFLOW_TYPE
description:
IPv4 based NetFlow
base identity: NETFLOW_TYPE
description:
IPv6 based NetFlow
base identity: NETFLOW_TYPE
description:
Top level enclosing container for NetFlow model config
and operational state data
nodetype: container (rw)
description:
Global config data for NetFlow
nodetype: container (rw)
description:
Global operational state data for NetFlow
nodetype: container (ro)
description:
Enclosing container for the list of interfaces on which
NetFlow is set
nodetype: container (rw)
description:
List of interfaces on which NetFlow is set
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.netflow.handler.NetflowInterfaceReader
frinx-implemented-reader-details:
CONTAINS_NETFLOW:
flow .+ monitor \S+( sampler .+)? (ingress|egress)
IFACE_LINE:
interface (?<name>.+)
SH_IFACES:
show running-config interface
frinx-implemented-writer:
MISSING WRITER
nodetype: list (rw)
list keys: [id]
description:
Reference to the interface id list key
nodetype: leaf (list key) (rw)
type: leafref
description:
Configuration for NetFlow per-interface data
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.netflow.handler.NetflowInterfaceConfigReader
frinx-implemented-writer:
MISSING WRITER
nodetype: container (rw)
description:
User-defined identifier for the interface -- a common
convention could be '
nodetype: leaf (rw)
type: oc-if:interface-id
description:
Operational state for NetFlow per-interface data
nodetype: container (ro)
description:
User-defined identifier for the interface -- a common
convention could be '
nodetype: leaf (ro)
type: oc-if:interface-id
description:
Enclosing container the list of ingress flows on the
interface
nodetype: container (rw)
description:
List of ingress NetFlow flows on the interface
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.netflow.handler.IngressFlowReader
frinx-implemented-reader-details:
FLOW_LINE:
flow (?<type>.+) monitor \S+( sampler .+)? ingress
SH_NETFLOW_INTF:
show running-config interface %s | include ingress
frinx-implemented-writer:
MISSING WRITER
nodetype: list (rw)
list keys: [netflow-type]
description:
Reference to type list key
nodetype: leaf (list key) (rw)
type: leafref
description:
Configuration data
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.netflow.handler.IngressFlowConfigReader
frinx-implemented-reader-details:
FLOW_MONITOR:
flow (?<type>.+) monitor (?<monitorName>\S+)( sampler (?<samplerName>.+))? ingress
SH_SINGLE_INTERFACE_FLOW_CFG:
show running-config interface %s | include flow %s monitor
frinx-implemented-writer:
io.frinx.cli.unit.iosxr.netflow.handler.IngressFlowConfigWriter
frinx-implemented-writer-details:
FLOW_CMD_WITHOUT_SAMPLER:
flow %s monitor %s ingress
FLOW_CMD_WITH_SAMPLER:
flow %s monitor %s sampler %s ingress
NO_FLOW_CMD:
no flow %s monitor %s ingress
nodetype: container (rw)
description:
NetFlow type
nodetype: leaf (rw)
type: identityref
description:
Flow monitor map name
nodetype: leaf (rw)
type: string
description:
Sampler map name
nodetype: leaf (rw)
type: string
description:
Operational state data for interface ingress NetFlow flows
nodetype: container (ro)
description:
NetFlow type
nodetype: leaf (ro)
type: identityref
description:
Flow monitor map name
nodetype: leaf (ro)
type: string
description:
Sampler map name
nodetype: leaf (ro)
type: string
description:
Enclosing container the list of egress flows on the
interface
nodetype: container (rw)
description:
List of egress NetFlow flows on the interface
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.netflow.handler.EgressFlowReader
frinx-implemented-reader-details:
FLOW_LINE:
flow (?<type>.+) monitor \S+( sampler .+)? egress
SH_NETFLOW_INTF:
show running-config interface %s | include egress
frinx-implemented-writer:
MISSING WRITER
nodetype: list (rw)
list keys: [netflow-type]
description:
Reference to type list key
nodetype: leaf (list key) (rw)
type: leafref
description:
Configuration data
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.netflow.handler.EgressFlowConfigReader
frinx-implemented-reader-details:
FLOW_MONITOR:
flow (?<type>.+) monitor (?<monitorName>\S+)( sampler (?<samplerName>.+))? egress
SH_SINGLE_INTERFACE_FLOW_CFG:
show running-config interface %s | include flow %s monitor
frinx-implemented-writer:
io.frinx.cli.unit.iosxr.netflow.handler.EgressFlowConfigWriter
frinx-implemented-writer-details:
FLOW_CMD_WITHOUT_SAMPLER:
flow %s monitor %s egress
FLOW_CMD_WITH_SAMPLER:
flow %s monitor %s sampler %s egress
NO_FLOW_CMD:
no flow %s monitor %s egress
nodetype: container (rw)
description:
NetFlow type
nodetype: leaf (rw)
type: identityref
description:
Flow monitor map name
nodetype: leaf (rw)
type: string
description:
Sampler map name
nodetype: leaf (rw)
type: string
description:
Operational state data for interface egress NetFlow flows
nodetype: container (ro)
description:
NetFlow type
nodetype: leaf (ro)
type: identityref
description:
Flow monitor map name
nodetype: leaf (ro)
type: string
description:
Sampler map name
nodetype: leaf (ro)
type: string
This module defines configuration and operational state data for ethernet OAM
frinx-openconfig-interfaces
frinx-oam-types
network-topology
frinx-uniconfig-topology
yang-ext
description:
Top level configuration container for ethernet OAM data
nodetype: container (rw)
description:
Ethernet connectivity fault management. Also includes
options that are associated with specific interfaces, such
as maintenance endpoint domains.
nodetype: container (rw)
description:
Configuration for ethernet CFM
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.oam.handler.CfmConfigReader
frinx-implemented-reader-details:
CFM_LINE:
ethernet cfm
SH_CFM:
show running-config ethernet cfm
frinx-implemented-writer:
io.frinx.cli.unit.iosxr.oam.handler.CfmConfigWriter
frinx-implemented-writer-details:
CREATE_TEMPLATE:
ethernet cfm
root
DELETE_TEMPLATE:
no ethernet cfm
nodetype: container (rw)
description:
Is ethernet CFM enabled
nodetype: leaf (rw)
type: boolean
description:
Domain-specific global configuration
nodetype: container (rw)
description:
Configuration for a particular Maintenance
Domain
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.oam.handler.domain.CfmDomainReader
frinx-implemented-reader-details:
CFM_DOMAIN_LINE:
domain (?<domain>\S+) .*
SH_CFM_DOMAIN:
show running-config ethernet cfm | include ^ domain
frinx-implemented-writer:
MISSING WRITER
nodetype: list (rw)
list keys: [domain-name]
description:
Maintenance Domain
nodetype: leaf (list key) (rw)
type: leafref
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.oam.handler.domain.CfmDomainConfigReader
frinx-implemented-reader-details:
CFM_DOMAIN_LINE:
domain (?<domain>\S+) level (?<level>\d)
SH_CFM_DOMAIN:
show running-config ethernet cfm | include ^ domain %s
frinx-implemented-writer:
io.frinx.cli.unit.iosxr.oam.handler.domain.CfmDomainConfigWriter
frinx-implemented-writer-details:
CREATE_TEMPLATE:
ethernet cfm
domain {$domain}{% if ($config.level) %} level {$config.level.value}{% endif %}
root
DELETE_TEMPLATE:
ethernet cfm
no domain {$domain}
root
nodetype: container (rw)
description:
Maintenance Domain
nodetype: leaf (rw)
type: string
description:
Maintenance Domain Level
nodetype: leaf (rw)
type: oam-types:domain-level
description:
MA-Specific configuration
nodetype: container (rw)
description:
Configuration for a particular MA
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.oam.handler.domain.CfmMaReader
frinx-implemented-reader-details:
CFM_DOMAIN_SERVICE_LINE:
service (?<service>\S+) down-meps
SH_CFM_DOMAIN_SERVICE:
show running-config ethernet cfm domain %s level %d | include ^ {2}service
frinx-implemented-writer:
MISSING WRITER
nodetype: list (rw)
list keys: [ma-name]
description:
MA name
nodetype: leaf (list key) (rw)
type: leafref
description:
Configuration for MA
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.oam.handler.domain.CfmMaConfigReader
frinx-implemented-reader-details:
CONTINUITY_CHECK_LINE:
continuity-check interval (?<interval>\S+) loss-threshold (?<threshold>\d)
CROSSCHECK_MEPID_LINE:
mep-id (?<id>\d+)
EFD_LINE:
efd
SH_CFM_DOMAIN_SERVICE:
show running-config ethernet cfm domain %s level %d service %s down-meps
frinx-implemented-writer:
io.frinx.cli.unit.iosxr.oam.handler.domain.CfmMaConfigWriter
frinx-implemented-writer-details:
CREATE_TEMPLATE:
ethernet cfm
domain {$domain.domain_name} level {$domain.level.value}
service {$config.ma_name} down-meps
{% if ($config.continuity_check_interval) %}continuity-check interval {$config.continuity_check_interval.name} loss-threshold {$config.continuity_check_loss_threshold}
{% else %}no continuity-check interval
{% endif %}{% loop in $removed_crosscheck as $mep_id %}no mep crosscheck mep-id {$mep_id}
{% onEmpty %}{% endloop %}{% loop in $added_crosscheck as $mep_id %}mep crosscheck mep-id {$mep_id}
{% onEmpty %}{% endloop %}{% if $is_efd == TRUE %}{% else %}no {% endif %}efd
root
DELETE_TEMPLATE:
ethernet cfm
domain {$domain.domain_name} level {$domain.level.value}
no service {$config.ma_name}
root
nodetype: container (rw)
description:
MA name
nodetype: leaf (rw)
type: string
description:
Continuity Check Message Interval
nodetype: leaf (rw)
type: oam-types:ccm-interval
description:
Continuity Check Message Loss Threshold
nodetype: leaf (rw)
type: uint32
description:
Crosscheck MEP ID
nodetype: leaf-list (rw)
type: uint16
description:
Enable EFD to bring down ports when MEPs detect errors
nodetype: leaf (rw)
type: boolean
This module defines types related to ethernet OAM configurations
description:
Continuity check message interval
type: enumeration
description:
Maintenance Domain Level
type: uint8
This module defines configuration and operational state data for network access control lists (i.e., filters, rules, etc.). ACLs are organized into ACL sets, with each set containing one or more ACL entries. ACL sets are identified by a unique name, while each entry within a set is assigned a sequence-id that determines the order in which the ACL rules are applied to a packet.
Individual ACL rules specify match criteria based on fields in the packet, along with an action that defines how matching packets should be handled. Entries have a type that indicates the type of match criteria, e.g., MAC layer, IPv4, IPv6, etc.
frinx-openconfig-packet-match
frinx-openconfig-interfaces
frinx-openconfig-yang-types
frinx-openconfig-extensions
network-topology
frinx-uniconfig-topology
description:
Base identity for actions in the forwarding category
description:
Drop packet without sending any ICMP error message
base identity: FORWARDING_ACTION
description:
Accept the packet
base identity: FORWARDING_ACTION
description:
Drop the packet and send an ICMP error message to the source
base identity: FORWARDING_ACTION
description:
Base identity for types of ACL sets
description:
MAC-layer ACLs
base identity: ACL_TYPE
description:
IP-layer ACLs with IPv6 addresses
base identity: ACL_TYPE
description:
Mixed-mode ACL that specifies L2 and L3 protocol
fields. This ACL type is not implemented by many
routing/switching devices.
base identity: ACL_TYPE
description:
IP-layer ACLs with IPv4 addresses
base identity: ACL_TYPE
description:
Base identity for system to indicate how it is able to report
counters
description:
ACL counters are aggregated over all interfaces, and reported
only per ACL entry
base identity: ACL_COUNTER_CAPABILITY
description:
ACL counters are available and reported only per interface
base identity: ACL_COUNTER_CAPABILITY
description:
ACL counters are reported per interface, and also aggregated
and reported per ACL entry.
base identity: ACL_COUNTER_CAPABILITY
description:
Base identity for defining the destination for logging
actions
description:
Log the packet in Syslog
base identity: LOG_ACTION
description:
No logging
base identity: LOG_ACTION
description:
Top level enclosing container for ACL model config
and operational state data
frinx-device-type:
junos
frinx-supported-versions:
173
frinx-device-type:
junos
frinx-supported-versions:
182
nodetype: container (rw)
description:
Global config data for ACLs
nodetype: container (rw)
description:
Global operational state data for ACLs
nodetype: container (ro)
description:
System reported indication of how ACL counters are reported
by the target
nodetype: leaf (ro)
type: identityref
description:
Access list entries variables enclosing container
nodetype: container (rw)
description:
List of ACL sets, each comprising of a list of ACL
entries
frinx-device-type:
ios
frinx-supported-versions:
12any,15any
frinx-implemented-reader:
io.frinx.cli.unit.ios.unit.acl.handler.AclSetReader
frinx-implemented-reader-details:
ACL_LINE:
(?<type>.+) access-list (extended )?(?<name>.+)
SH_ACCESS_LISTS:
show running-config | include access-list
frinx-implemented-writer:
io.frinx.cli.unit.ios.unit.acl.handler.AclSetConfigWriter
frinx-implemented-writer-details:
ACL_IPV4:
configure terminal
ip access-list extended {$aclName}
end
ACL_IPV4_DELETE:
configure terminal
no ip access-list extended {$aclName}
end
ACL_IPV6:
configure terminal
ipv6 access-list {$aclName}
end
ACL_IPV6_DELETE:
configure terminal
no ipv6 access-list {$aclName}
end
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.unit.acl.handler.AclSetReader
frinx-implemented-reader-details:
ACL_LINE:
(?<type>ipv4|ipv6) access-list (?<name>.+)
SH_ACCESS_LISTS:
show running-config | include access-list
frinx-implemented-writer:
MISSING WRITER
nodetype: list (rw)
description:
Reference to the name list key
nodetype: leaf (list key) (rw)
type: string
description:
Reference to the type list key
nodetype: leaf (list key) (rw)
type: leafref
description:
Access list config
frinx-device-type:
ios
frinx-supported-versions:
12any,15any
frinx-implemented-reader:
io.frinx.cli.unit.ios.unit.acl.handler.AclSetConfigReader
frinx-implemented-writer:
MISSING WRITER
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.unit.acl.handler.AclSetConfigReader
frinx-implemented-writer:
MISSING WRITER
nodetype: container (rw)
description:
The name of the access-list set
nodetype: leaf (rw)
type: string
description:
The type determines the fields allowed in the ACL entries
belonging to the ACL set (e.g., IPv4, IPv6, etc.)
nodetype: leaf (rw)
type: identityref
description:
Description, or comment, for the ACL set
nodetype: leaf (rw)
type: string
description:
Access list state information
nodetype: container (ro)
description:
The name of the access-list set
nodetype: leaf (ro)
type: string
description:
The type determines the fields allowed in the ACL entries
belonging to the ACL set (e.g., IPv4, IPv6, etc.)
nodetype: leaf (ro)
type: identityref
description:
Description, or comment, for the ACL set
nodetype: leaf (ro)
type: string
description:
Access list entries container
nodetype: container (rw)
description:
List of ACL entries comprising an ACL set
frinx-device-type:
ios
frinx-supported-versions:
12any,15any
frinx-implemented-reader:
io.frinx.cli.unit.ios.unit.acl.handler.AclEntryReader
frinx-implemented-reader-details:
IPV6_SEQUENCE_PATTERN:
^.*sequence (?<sequenceId>\d+)$
IP_SEQUENCE_PATTERN:
^\s*(?<sequenceId>\d+) (?!remark).*
SH_ACCESS_LISTS_IPV4:
show ip access-lists %s
SH_ACCESS_LISTS_IPV6:
show ipv6 access-list %s
frinx-implemented-writer:
io.frinx.cli.unit.ios.unit.acl.handler.AclEntryWriter
frinx-implemented-writer-details:
ACL_DELETE:
configure terminal
ip access-list extended {$aclName}
no {$aclSeqId}
end
ACL_ICMP_ENTRY:
configure terminal
ip access-list extended {$aclName}
{$aclSeqId} {$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclDstAddr} {$aclIcmpMsgType} {$aclTtl}
end
ACL_ICMP_IP6_ENTRY:
configure terminal
ipv6 access-list {$aclName}
{$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclDstAddr} {$aclIcmpMsgType} {$aclTtl} {$aclSeqId}
end
ACL_IP6_DELETE:
configure terminal
ipv6 access-list {$aclName}
no sequence {$aclSeqId}
end
ACL_IP6_ENTRY:
configure terminal
ipv6 access-list {$aclName}
{$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclDstAddr} {$aclTtl} {$aclSeqId}
end
ACL_IP_ENTRY:
configure terminal
ip access-list extended {$aclName}
{$aclSeqId} {$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclDstAddr} {$aclTtl}
end
ACL_TCP_ENTRY:
configure terminal
ip access-list extended {$aclName}
{$aclSeqId} {$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclSrcPort} {$aclDstAddr} {$aclDstPort} {$aclTtl}
end
ACL_TCP_IP6_ENTRY:
configure terminal
ipv6 access-list {$aclName}
{$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclSrcPort} {$aclDstAddr} {$aclDstPort} {$aclTtl} {$aclSeqId}
end
ANY:
any
DESTINATION_ADDRESS_AND_DESTINATION_ADDRESS_WILDCARDED_TOGETHER_ERROR:
destination-address and destination-address-wildcarded cannot be defined in ACL together
DESTINATION_ADDRESS_WILDCARDED_MISSING_FIELDS_ERROR:
destination-address-wildcarded must contain address and wildcard-mask
NONE_DESTINATION_ADDRESS_OR_DESTINATION_ADDRESS_WILDCARDED_ERROR:
destination-address or destination-address-wildcarded must be defined in ACL
NONE_SOURCE_ADDRESS_OR_SOURCE_ADDRESS_WILDCARDED_ERROR:
source-address or source-address-wildcarded must be defined in ACL
RANGE_SEPARATOR:
..
SOURCE_ADDRESS_AND_SOURCE_ADDRESS_WILDCARDED_TOGETHER_ERROR:
source-address and source-address-wildcarded cannot be defined in ACL together
SOURCE_ADDRESS_WILDCARDED_MISSING_FIELDS_ERROR:
source-address-wildcarded must contain address and wildcard-mask
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.unit.acl.handler.AclEntryReader
frinx-implemented-reader-details:
SEQUENCE_PATTERN:
^\s*(?<sequenceId>\d+) (?!remark).*
SH_ACCESS_LISTS_IPV4:
show running-config ipv4 access-list %s
SH_ACCESS_LISTS_IPV6:
show running-config ipv6 access-list %s
frinx-implemented-writer:
io.frinx.cli.unit.iosxr.unit.acl.handler.AclEntryWriter
frinx-implemented-writer-details:
ACL_DELETE:
{$type} access-list {$aclName}
no {$aclSeqId}
root
ACL_ICMP_ENTRY:
{$type} access-list {$aclName}
{$aclSeqId} {$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclDstAddr} {$aclIcmpMsgType} {$aclTtl}
root
ACL_IP_ENTRY:
{$type} access-list {$aclName}
{$aclSeqId} {$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclDstAddr} {$aclTtl}
root
ACL_TCP_ENTRY:
{$type} access-list {$aclName}
{$aclSeqId} {$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclSrcPort} {$aclDstAddr} {$aclDstPort} {$aclTtl}
root
ANY:
any
DESTINATION_ADDRESS_AND_DESTINATION_ADDRESS_WILDCARDED_TOGETHER_ERROR:
destination-address and destination-address-wildcarded cannot be defined in ACL together
DESTINATION_ADDRESS_WILDCARDED_MISSING_FIELDS_ERROR:
destination-address-wildcarded must contain address and wildcard-mask
NONE_DESTINATION_ADDRESS_OR_DESTINATION_ADDRESS_WILDCARDED_ERROR:
destination-address or destination-address-wildcarded must be defined in ACL
NONE_SOURCE_ADDRESS_OR_SOURCE_ADDRESS_WILDCARDED_ERROR:
source-address or source-address-wildcarded must be defined in ACL
RANGE_SEPARATOR:
..
SOURCE_ADDRESS_AND_SOURCE_ADDRESS_WILDCARDED_TOGETHER_ERROR:
source-address and source-address-wildcarded cannot be defined in ACL together
SOURCE_ADDRESS_WILDCARDED_MISSING_FIELDS_ERROR:
source-address-wildcarded must contain address and wildcard-mask
nodetype: list (rw)
list keys: [sequence-id]
description:
references the list key
nodetype: leaf (list key) (rw)
type: leafref
description:
Access list entries config
frinx-device-type:
ios
frinx-supported-versions:
12any,15any
frinx-implemented-reader:
io.frinx.cli.unit.ios.unit.acl.handler.AclEntryReader
frinx-implemented-reader-details:
IPV6_SEQUENCE_PATTERN:
^.*sequence (?<sequenceId>\d+)$
IP_SEQUENCE_PATTERN:
^\s*(?<sequenceId>\d+) (?!remark).*
SH_ACCESS_LISTS_IPV4:
show ip access-lists %s
SH_ACCESS_LISTS_IPV6:
show ipv6 access-list %s
frinx-implemented-writer:
io.frinx.cli.unit.ios.unit.acl.handler.AclEntryWriter
frinx-implemented-writer-details:
ACL_DELETE:
configure terminal
ip access-list extended {$aclName}
no {$aclSeqId}
end
ACL_ICMP_ENTRY:
configure terminal
ip access-list extended {$aclName}
{$aclSeqId} {$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclDstAddr} {$aclIcmpMsgType} {$aclTtl}
end
ACL_ICMP_IP6_ENTRY:
configure terminal
ipv6 access-list {$aclName}
{$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclDstAddr} {$aclIcmpMsgType} {$aclTtl} {$aclSeqId}
end
ACL_IP6_DELETE:
configure terminal
ipv6 access-list {$aclName}
no sequence {$aclSeqId}
end
ACL_IP6_ENTRY:
configure terminal
ipv6 access-list {$aclName}
{$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclDstAddr} {$aclTtl} {$aclSeqId}
end
ACL_IP_ENTRY:
configure terminal
ip access-list extended {$aclName}
{$aclSeqId} {$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclDstAddr} {$aclTtl}
end
ACL_TCP_ENTRY:
configure terminal
ip access-list extended {$aclName}
{$aclSeqId} {$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclSrcPort} {$aclDstAddr} {$aclDstPort} {$aclTtl}
end
ACL_TCP_IP6_ENTRY:
configure terminal
ipv6 access-list {$aclName}
{$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclSrcPort} {$aclDstAddr} {$aclDstPort} {$aclTtl} {$aclSeqId}
end
ANY:
any
DESTINATION_ADDRESS_AND_DESTINATION_ADDRESS_WILDCARDED_TOGETHER_ERROR:
destination-address and destination-address-wildcarded cannot be defined in ACL together
DESTINATION_ADDRESS_WILDCARDED_MISSING_FIELDS_ERROR:
destination-address-wildcarded must contain address and wildcard-mask
NONE_DESTINATION_ADDRESS_OR_DESTINATION_ADDRESS_WILDCARDED_ERROR:
destination-address or destination-address-wildcarded must be defined in ACL
NONE_SOURCE_ADDRESS_OR_SOURCE_ADDRESS_WILDCARDED_ERROR:
source-address or source-address-wildcarded must be defined in ACL
RANGE_SEPARATOR:
..
SOURCE_ADDRESS_AND_SOURCE_ADDRESS_WILDCARDED_TOGETHER_ERROR:
source-address and source-address-wildcarded cannot be defined in ACL together
SOURCE_ADDRESS_WILDCARDED_MISSING_FIELDS_ERROR:
source-address-wildcarded must contain address and wildcard-mask
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.unit.acl.handler.AclEntryReader
frinx-implemented-reader-details:
SEQUENCE_PATTERN:
^\s*(?<sequenceId>\d+) (?!remark).*
SH_ACCESS_LISTS_IPV4:
show running-config ipv4 access-list %s
SH_ACCESS_LISTS_IPV6:
show running-config ipv6 access-list %s
frinx-implemented-writer:
io.frinx.cli.unit.iosxr.unit.acl.handler.AclEntryWriter
frinx-implemented-writer-details:
ACL_DELETE:
{$type} access-list {$aclName}
no {$aclSeqId}
root
ACL_ICMP_ENTRY:
{$type} access-list {$aclName}
{$aclSeqId} {$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclDstAddr} {$aclIcmpMsgType} {$aclTtl}
root
ACL_IP_ENTRY:
{$type} access-list {$aclName}
{$aclSeqId} {$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclDstAddr} {$aclTtl}
root
ACL_TCP_ENTRY:
{$type} access-list {$aclName}
{$aclSeqId} {$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclSrcPort} {$aclDstAddr} {$aclDstPort} {$aclTtl}
root
ANY:
any
DESTINATION_ADDRESS_AND_DESTINATION_ADDRESS_WILDCARDED_TOGETHER_ERROR:
destination-address and destination-address-wildcarded cannot be defined in ACL together
DESTINATION_ADDRESS_WILDCARDED_MISSING_FIELDS_ERROR:
destination-address-wildcarded must contain address and wildcard-mask
NONE_DESTINATION_ADDRESS_OR_DESTINATION_ADDRESS_WILDCARDED_ERROR:
destination-address or destination-address-wildcarded must be defined in ACL
NONE_SOURCE_ADDRESS_OR_SOURCE_ADDRESS_WILDCARDED_ERROR:
source-address or source-address-wildcarded must be defined in ACL
RANGE_SEPARATOR:
..
SOURCE_ADDRESS_AND_SOURCE_ADDRESS_WILDCARDED_TOGETHER_ERROR:
source-address and source-address-wildcarded cannot be defined in ACL together
SOURCE_ADDRESS_WILDCARDED_MISSING_FIELDS_ERROR:
source-address-wildcarded must contain address and wildcard-mask
nodetype: container (rw)
description:
The sequence id determines the order in which ACL entries
are applied. The sequence id must be unique for each entry
in an ACL set. Target devices should apply the ACL entry
rules in the order determined by sequence id, rather than
the relying only on order in the list.
nodetype: leaf (rw)
type: uint32
description:
A user-defined description, or comment, for this Access List
Entry.
nodetype: leaf (rw)
type: string
description:
terminal name
nodetype: leaf (rw)
type: string
description:
State information for ACL entries
nodetype: container (ro)
description:
The sequence id determines the order in which ACL entries
are applied. The sequence id must be unique for each entry
in an ACL set. Target devices should apply the ACL entry
rules in the order determined by sequence id, rather than
the relying only on order in the list.
nodetype: leaf (ro)
type: uint32
description:
A user-defined description, or comment, for this Access List
Entry.
nodetype: leaf (ro)
type: string
description:
Count of the number of packets matching the current ACL
entry.
An implementation should provide this counter on a
per-interface per-ACL-entry if possible.
If an implementation only supports ACL counters per entry
(i.e., not broken out per interface), then the value
should be equal to the aggregate count across all interfaces.
An implementation that provides counters per entry per
interface is not required to also provide an aggregate count,
e.g., per entry -- the user is expected to be able implement
the required aggregation if such a count is needed.
nodetype: leaf (ro)
type: oc-yang:counter64
description:
Count of the number of octets (bytes) matching the current
ACL entry.
An implementation should provide this counter on a
per-interface per-ACL-entry if possible.
If an implementation only supports ACL counters per entry
(i.e., not broken out per interface), then the value
should be equal to the aggregate count across all interfaces.
An implementation that provides counters per entry per
interface is not required to also provide an aggregate count,
e.g., per entry -- the user is expected to be able implement
the required aggregation if such a count is needed.
nodetype: leaf (ro)
type: oc-yang:counter64
description:
Ethernet header fields
nodetype: container (rw)
description:
Configuration data
nodetype: container (rw)
description:
Source IEEE 802 MAC address.
nodetype: leaf (rw)
type: oc-yang:mac-address
description:
Source IEEE 802 MAC address mask.
nodetype: leaf (rw)
type: oc-yang:mac-address
description:
Destination IEEE 802 MAC address.
nodetype: leaf (rw)
type: oc-yang:mac-address
description:
Destination IEEE 802 MAC address mask.
nodetype: leaf (rw)
type: oc-yang:mac-address
description:
Ethertype field to match in Ethernet packets
nodetype: leaf (rw)
type: oc-pkt-match-types:ethertype-type
description:
State Information.
nodetype: container (ro)
description:
Source IEEE 802 MAC address.
nodetype: leaf (ro)
type: oc-yang:mac-address
description:
Source IEEE 802 MAC address mask.
nodetype: leaf (ro)
type: oc-yang:mac-address
description:
Destination IEEE 802 MAC address.
nodetype: leaf (ro)
type: oc-yang:mac-address
description:
Destination IEEE 802 MAC address mask.
nodetype: leaf (ro)
type: oc-yang:mac-address
description:
Ethertype field to match in Ethernet packets
nodetype: leaf (ro)
type: oc-pkt-match-types:ethertype-type
description:
Top level container for IPv4 match field data
frinx-device-type:
ios
frinx-supported-versions:
12any,15any
frinx-implemented-reader:
io.frinx.cli.unit.ios.unit.acl.handler.AclEntryReader
frinx-implemented-reader-details:
IPV6_SEQUENCE_PATTERN:
^.*sequence (?<sequenceId>\d+)$
IP_SEQUENCE_PATTERN:
^\s*(?<sequenceId>\d+) (?!remark).*
SH_ACCESS_LISTS_IPV4:
show ip access-lists %s
SH_ACCESS_LISTS_IPV6:
show ipv6 access-list %s
frinx-implemented-writer:
io.frinx.cli.unit.ios.unit.acl.handler.AclEntryWriter
frinx-implemented-writer-details:
ACL_DELETE:
configure terminal
ip access-list extended {$aclName}
no {$aclSeqId}
end
ACL_ICMP_ENTRY:
configure terminal
ip access-list extended {$aclName}
{$aclSeqId} {$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclDstAddr} {$aclIcmpMsgType} {$aclTtl}
end
ACL_ICMP_IP6_ENTRY:
configure terminal
ipv6 access-list {$aclName}
{$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclDstAddr} {$aclIcmpMsgType} {$aclTtl} {$aclSeqId}
end
ACL_IP6_DELETE:
configure terminal
ipv6 access-list {$aclName}
no sequence {$aclSeqId}
end
ACL_IP6_ENTRY:
configure terminal
ipv6 access-list {$aclName}
{$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclDstAddr} {$aclTtl} {$aclSeqId}
end
ACL_IP_ENTRY:
configure terminal
ip access-list extended {$aclName}
{$aclSeqId} {$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclDstAddr} {$aclTtl}
end
ACL_TCP_ENTRY:
configure terminal
ip access-list extended {$aclName}
{$aclSeqId} {$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclSrcPort} {$aclDstAddr} {$aclDstPort} {$aclTtl}
end
ACL_TCP_IP6_ENTRY:
configure terminal
ipv6 access-list {$aclName}
{$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclSrcPort} {$aclDstAddr} {$aclDstPort} {$aclTtl} {$aclSeqId}
end
ANY:
any
DESTINATION_ADDRESS_AND_DESTINATION_ADDRESS_WILDCARDED_TOGETHER_ERROR:
destination-address and destination-address-wildcarded cannot be defined in ACL together
DESTINATION_ADDRESS_WILDCARDED_MISSING_FIELDS_ERROR:
destination-address-wildcarded must contain address and wildcard-mask
NONE_DESTINATION_ADDRESS_OR_DESTINATION_ADDRESS_WILDCARDED_ERROR:
destination-address or destination-address-wildcarded must be defined in ACL
NONE_SOURCE_ADDRESS_OR_SOURCE_ADDRESS_WILDCARDED_ERROR:
source-address or source-address-wildcarded must be defined in ACL
RANGE_SEPARATOR:
..
SOURCE_ADDRESS_AND_SOURCE_ADDRESS_WILDCARDED_TOGETHER_ERROR:
source-address and source-address-wildcarded cannot be defined in ACL together
SOURCE_ADDRESS_WILDCARDED_MISSING_FIELDS_ERROR:
source-address-wildcarded must contain address and wildcard-mask
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.unit.acl.handler.AclEntryReader
frinx-implemented-reader-details:
SEQUENCE_PATTERN:
^\s*(?<sequenceId>\d+) (?!remark).*
SH_ACCESS_LISTS_IPV4:
show running-config ipv4 access-list %s
SH_ACCESS_LISTS_IPV6:
show running-config ipv6 access-list %s
frinx-implemented-writer:
io.frinx.cli.unit.iosxr.unit.acl.handler.AclEntryWriter
frinx-implemented-writer-details:
ACL_DELETE:
{$type} access-list {$aclName}
no {$aclSeqId}
root
ACL_ICMP_ENTRY:
{$type} access-list {$aclName}
{$aclSeqId} {$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclDstAddr} {$aclIcmpMsgType} {$aclTtl}
root
ACL_IP_ENTRY:
{$type} access-list {$aclName}
{$aclSeqId} {$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclDstAddr} {$aclTtl}
root
ACL_TCP_ENTRY:
{$type} access-list {$aclName}
{$aclSeqId} {$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclSrcPort} {$aclDstAddr} {$aclDstPort} {$aclTtl}
root
ANY:
any
DESTINATION_ADDRESS_AND_DESTINATION_ADDRESS_WILDCARDED_TOGETHER_ERROR:
destination-address and destination-address-wildcarded cannot be defined in ACL together
DESTINATION_ADDRESS_WILDCARDED_MISSING_FIELDS_ERROR:
destination-address-wildcarded must contain address and wildcard-mask
NONE_DESTINATION_ADDRESS_OR_DESTINATION_ADDRESS_WILDCARDED_ERROR:
destination-address or destination-address-wildcarded must be defined in ACL
NONE_SOURCE_ADDRESS_OR_SOURCE_ADDRESS_WILDCARDED_ERROR:
source-address or source-address-wildcarded must be defined in ACL
RANGE_SEPARATOR:
..
SOURCE_ADDRESS_AND_SOURCE_ADDRESS_WILDCARDED_TOGETHER_ERROR:
source-address and source-address-wildcarded cannot be defined in ACL together
SOURCE_ADDRESS_WILDCARDED_MISSING_FIELDS_ERROR:
source-address-wildcarded must contain address and wildcard-mask
nodetype: container (rw)
description:
Configuration data for IPv4 match fields
frinx-device-type:
ios
frinx-supported-versions:
12any,15any
frinx-implemented-reader:
io.frinx.cli.unit.ios.unit.acl.handler.AclEntryReader
frinx-implemented-reader-details:
IPV6_SEQUENCE_PATTERN:
^.*sequence (?<sequenceId>\d+)$
IP_SEQUENCE_PATTERN:
^\s*(?<sequenceId>\d+) (?!remark).*
SH_ACCESS_LISTS_IPV4:
show ip access-lists %s
SH_ACCESS_LISTS_IPV6:
show ipv6 access-list %s
frinx-implemented-writer:
io.frinx.cli.unit.ios.unit.acl.handler.AclEntryWriter
frinx-implemented-writer-details:
ACL_DELETE:
configure terminal
ip access-list extended {$aclName}
no {$aclSeqId}
end
ACL_ICMP_ENTRY:
configure terminal
ip access-list extended {$aclName}
{$aclSeqId} {$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclDstAddr} {$aclIcmpMsgType} {$aclTtl}
end
ACL_ICMP_IP6_ENTRY:
configure terminal
ipv6 access-list {$aclName}
{$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclDstAddr} {$aclIcmpMsgType} {$aclTtl} {$aclSeqId}
end
ACL_IP6_DELETE:
configure terminal
ipv6 access-list {$aclName}
no sequence {$aclSeqId}
end
ACL_IP6_ENTRY:
configure terminal
ipv6 access-list {$aclName}
{$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclDstAddr} {$aclTtl} {$aclSeqId}
end
ACL_IP_ENTRY:
configure terminal
ip access-list extended {$aclName}
{$aclSeqId} {$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclDstAddr} {$aclTtl}
end
ACL_TCP_ENTRY:
configure terminal
ip access-list extended {$aclName}
{$aclSeqId} {$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclSrcPort} {$aclDstAddr} {$aclDstPort} {$aclTtl}
end
ACL_TCP_IP6_ENTRY:
configure terminal
ipv6 access-list {$aclName}
{$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclSrcPort} {$aclDstAddr} {$aclDstPort} {$aclTtl} {$aclSeqId}
end
ANY:
any
DESTINATION_ADDRESS_AND_DESTINATION_ADDRESS_WILDCARDED_TOGETHER_ERROR:
destination-address and destination-address-wildcarded cannot be defined in ACL together
DESTINATION_ADDRESS_WILDCARDED_MISSING_FIELDS_ERROR:
destination-address-wildcarded must contain address and wildcard-mask
NONE_DESTINATION_ADDRESS_OR_DESTINATION_ADDRESS_WILDCARDED_ERROR:
destination-address or destination-address-wildcarded must be defined in ACL
NONE_SOURCE_ADDRESS_OR_SOURCE_ADDRESS_WILDCARDED_ERROR:
source-address or source-address-wildcarded must be defined in ACL
RANGE_SEPARATOR:
..
SOURCE_ADDRESS_AND_SOURCE_ADDRESS_WILDCARDED_TOGETHER_ERROR:
source-address and source-address-wildcarded cannot be defined in ACL together
SOURCE_ADDRESS_WILDCARDED_MISSING_FIELDS_ERROR:
source-address-wildcarded must contain address and wildcard-mask
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.unit.acl.handler.AclEntryReader
frinx-implemented-reader-details:
SEQUENCE_PATTERN:
^\s*(?<sequenceId>\d+) (?!remark).*
SH_ACCESS_LISTS_IPV4:
show running-config ipv4 access-list %s
SH_ACCESS_LISTS_IPV6:
show running-config ipv6 access-list %s
frinx-implemented-writer:
io.frinx.cli.unit.iosxr.unit.acl.handler.AclEntryWriter
frinx-implemented-writer-details:
ACL_DELETE:
{$type} access-list {$aclName}
no {$aclSeqId}
root
ACL_ICMP_ENTRY:
{$type} access-list {$aclName}
{$aclSeqId} {$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclDstAddr} {$aclIcmpMsgType} {$aclTtl}
root
ACL_IP_ENTRY:
{$type} access-list {$aclName}
{$aclSeqId} {$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclDstAddr} {$aclTtl}
root
ACL_TCP_ENTRY:
{$type} access-list {$aclName}
{$aclSeqId} {$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclSrcPort} {$aclDstAddr} {$aclDstPort} {$aclTtl}
root
ANY:
any
DESTINATION_ADDRESS_AND_DESTINATION_ADDRESS_WILDCARDED_TOGETHER_ERROR:
destination-address and destination-address-wildcarded cannot be defined in ACL together
DESTINATION_ADDRESS_WILDCARDED_MISSING_FIELDS_ERROR:
destination-address-wildcarded must contain address and wildcard-mask
NONE_DESTINATION_ADDRESS_OR_DESTINATION_ADDRESS_WILDCARDED_ERROR:
destination-address or destination-address-wildcarded must be defined in ACL
NONE_SOURCE_ADDRESS_OR_SOURCE_ADDRESS_WILDCARDED_ERROR:
source-address or source-address-wildcarded must be defined in ACL
RANGE_SEPARATOR:
..
SOURCE_ADDRESS_AND_SOURCE_ADDRESS_WILDCARDED_TOGETHER_ERROR:
source-address and source-address-wildcarded cannot be defined in ACL together
SOURCE_ADDRESS_WILDCARDED_MISSING_FIELDS_ERROR:
source-address-wildcarded must contain address and wildcard-mask
nodetype: container (rw)
description:
Source IPv4 address prefix.
nodetype: leaf (rw)
type: oc-inet:ipv4-prefix
description:
Destination IPv4 address prefix.
nodetype: leaf (rw)
type: oc-inet:ipv4-prefix
description:
Value of diffserv codepoint.
nodetype: leaf (rw)
type: oc-inet:dscp
description:
The protocol carried in the IP packet, expressed either
as its IP protocol number, or by a defined identity.
nodetype: leaf (rw)
type: oc-pkt-match-types:ip-protocol-type
description:
The IP packet's hop limit -- known as TTL (in hops) in
IPv4 packets, and hop limit in IPv6
nodetype: leaf (rw)
type: uint8
frinx-device-type:
ios
frinx-supported-versions:
12any,15any
frinx-implemented-reader:
MISSING READER
frinx-implemented-writer:
io.frinx.cli.unit.ios.unit.acl.handler.AclEntryWriter
frinx-implemented-writer-details:
ACL_DELETE:
configure terminal
ip access-list extended {$aclName}
no {$aclSeqId}
end
ACL_ICMP_ENTRY:
configure terminal
ip access-list extended {$aclName}
{$aclSeqId} {$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclDstAddr} {$aclIcmpMsgType} {$aclTtl}
end
ACL_ICMP_IP6_ENTRY:
configure terminal
ipv6 access-list {$aclName}
{$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclDstAddr} {$aclIcmpMsgType} {$aclTtl} {$aclSeqId}
end
ACL_IP6_DELETE:
configure terminal
ipv6 access-list {$aclName}
no sequence {$aclSeqId}
end
ACL_IP6_ENTRY:
configure terminal
ipv6 access-list {$aclName}
{$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclDstAddr} {$aclTtl} {$aclSeqId}
end
ACL_IP_ENTRY:
configure terminal
ip access-list extended {$aclName}
{$aclSeqId} {$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclDstAddr} {$aclTtl}
end
ACL_TCP_ENTRY:
configure terminal
ip access-list extended {$aclName}
{$aclSeqId} {$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclSrcPort} {$aclDstAddr} {$aclDstPort} {$aclTtl}
end
ACL_TCP_IP6_ENTRY:
configure terminal
ipv6 access-list {$aclName}
{$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclSrcPort} {$aclDstAddr} {$aclDstPort} {$aclTtl} {$aclSeqId}
end
ANY:
any
DESTINATION_ADDRESS_AND_DESTINATION_ADDRESS_WILDCARDED_TOGETHER_ERROR:
destination-address and destination-address-wildcarded cannot be defined in ACL together
DESTINATION_ADDRESS_WILDCARDED_MISSING_FIELDS_ERROR:
destination-address-wildcarded must contain address and wildcard-mask
NONE_DESTINATION_ADDRESS_OR_DESTINATION_ADDRESS_WILDCARDED_ERROR:
destination-address or destination-address-wildcarded must be defined in ACL
NONE_SOURCE_ADDRESS_OR_SOURCE_ADDRESS_WILDCARDED_ERROR:
source-address or source-address-wildcarded must be defined in ACL
RANGE_SEPARATOR:
..
SOURCE_ADDRESS_AND_SOURCE_ADDRESS_WILDCARDED_TOGETHER_ERROR:
source-address and source-address-wildcarded cannot be defined in ACL together
SOURCE_ADDRESS_WILDCARDED_MISSING_FIELDS_ERROR:
source-address-wildcarded must contain address and wildcard-mask
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
MISSING READER
frinx-implemented-writer:
io.frinx.cli.unit.iosxr.unit.acl.handler.AclEntryWriter
frinx-implemented-writer-details:
ACL_DELETE:
{$type} access-list {$aclName}
no {$aclSeqId}
root
ACL_ICMP_ENTRY:
{$type} access-list {$aclName}
{$aclSeqId} {$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclDstAddr} {$aclIcmpMsgType} {$aclTtl}
root
ACL_IP_ENTRY:
{$type} access-list {$aclName}
{$aclSeqId} {$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclDstAddr} {$aclTtl}
root
ACL_TCP_ENTRY:
{$type} access-list {$aclName}
{$aclSeqId} {$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclSrcPort} {$aclDstAddr} {$aclDstPort} {$aclTtl}
root
ANY:
any
DESTINATION_ADDRESS_AND_DESTINATION_ADDRESS_WILDCARDED_TOGETHER_ERROR:
destination-address and destination-address-wildcarded cannot be defined in ACL together
DESTINATION_ADDRESS_WILDCARDED_MISSING_FIELDS_ERROR:
destination-address-wildcarded must contain address and wildcard-mask
NONE_DESTINATION_ADDRESS_OR_DESTINATION_ADDRESS_WILDCARDED_ERROR:
destination-address or destination-address-wildcarded must be defined in ACL
NONE_SOURCE_ADDRESS_OR_SOURCE_ADDRESS_WILDCARDED_ERROR:
source-address or source-address-wildcarded must be defined in ACL
RANGE_SEPARATOR:
..
SOURCE_ADDRESS_AND_SOURCE_ADDRESS_WILDCARDED_TOGETHER_ERROR:
source-address and source-address-wildcarded cannot be defined in ACL together
SOURCE_ADDRESS_WILDCARDED_MISSING_FIELDS_ERROR:
source-address-wildcarded must contain address and wildcard-mask
nodetype: container (rw)
description:
IPv4 address.
nodetype: leaf (rw)
type: oc-inet:ipv4-address
description:
IPv4 wildcard mask.
nodetype: leaf (rw)
type: oc-inet:ipv4-address
frinx-device-type:
ios
frinx-supported-versions:
12any,15any
frinx-implemented-reader:
MISSING READER
frinx-implemented-writer:
io.frinx.cli.unit.ios.unit.acl.handler.AclEntryWriter
frinx-implemented-writer-details:
ACL_DELETE:
configure terminal
ip access-list extended {$aclName}
no {$aclSeqId}
end
ACL_ICMP_ENTRY:
configure terminal
ip access-list extended {$aclName}
{$aclSeqId} {$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclDstAddr} {$aclIcmpMsgType} {$aclTtl}
end
ACL_ICMP_IP6_ENTRY:
configure terminal
ipv6 access-list {$aclName}
{$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclDstAddr} {$aclIcmpMsgType} {$aclTtl} {$aclSeqId}
end
ACL_IP6_DELETE:
configure terminal
ipv6 access-list {$aclName}
no sequence {$aclSeqId}
end
ACL_IP6_ENTRY:
configure terminal
ipv6 access-list {$aclName}
{$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclDstAddr} {$aclTtl} {$aclSeqId}
end
ACL_IP_ENTRY:
configure terminal
ip access-list extended {$aclName}
{$aclSeqId} {$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclDstAddr} {$aclTtl}
end
ACL_TCP_ENTRY:
configure terminal
ip access-list extended {$aclName}
{$aclSeqId} {$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclSrcPort} {$aclDstAddr} {$aclDstPort} {$aclTtl}
end
ACL_TCP_IP6_ENTRY:
configure terminal
ipv6 access-list {$aclName}
{$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclSrcPort} {$aclDstAddr} {$aclDstPort} {$aclTtl} {$aclSeqId}
end
ANY:
any
DESTINATION_ADDRESS_AND_DESTINATION_ADDRESS_WILDCARDED_TOGETHER_ERROR:
destination-address and destination-address-wildcarded cannot be defined in ACL together
DESTINATION_ADDRESS_WILDCARDED_MISSING_FIELDS_ERROR:
destination-address-wildcarded must contain address and wildcard-mask
NONE_DESTINATION_ADDRESS_OR_DESTINATION_ADDRESS_WILDCARDED_ERROR:
destination-address or destination-address-wildcarded must be defined in ACL
NONE_SOURCE_ADDRESS_OR_SOURCE_ADDRESS_WILDCARDED_ERROR:
source-address or source-address-wildcarded must be defined in ACL
RANGE_SEPARATOR:
..
SOURCE_ADDRESS_AND_SOURCE_ADDRESS_WILDCARDED_TOGETHER_ERROR:
source-address and source-address-wildcarded cannot be defined in ACL together
SOURCE_ADDRESS_WILDCARDED_MISSING_FIELDS_ERROR:
source-address-wildcarded must contain address and wildcard-mask
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
MISSING READER
frinx-implemented-writer:
io.frinx.cli.unit.iosxr.unit.acl.handler.AclEntryWriter
frinx-implemented-writer-details:
ACL_DELETE:
{$type} access-list {$aclName}
no {$aclSeqId}
root
ACL_ICMP_ENTRY:
{$type} access-list {$aclName}
{$aclSeqId} {$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclDstAddr} {$aclIcmpMsgType} {$aclTtl}
root
ACL_IP_ENTRY:
{$type} access-list {$aclName}
{$aclSeqId} {$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclDstAddr} {$aclTtl}
root
ACL_TCP_ENTRY:
{$type} access-list {$aclName}
{$aclSeqId} {$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclSrcPort} {$aclDstAddr} {$aclDstPort} {$aclTtl}
root
ANY:
any
DESTINATION_ADDRESS_AND_DESTINATION_ADDRESS_WILDCARDED_TOGETHER_ERROR:
destination-address and destination-address-wildcarded cannot be defined in ACL together
DESTINATION_ADDRESS_WILDCARDED_MISSING_FIELDS_ERROR:
destination-address-wildcarded must contain address and wildcard-mask
NONE_DESTINATION_ADDRESS_OR_DESTINATION_ADDRESS_WILDCARDED_ERROR:
destination-address or destination-address-wildcarded must be defined in ACL
NONE_SOURCE_ADDRESS_OR_SOURCE_ADDRESS_WILDCARDED_ERROR:
source-address or source-address-wildcarded must be defined in ACL
RANGE_SEPARATOR:
..
SOURCE_ADDRESS_AND_SOURCE_ADDRESS_WILDCARDED_TOGETHER_ERROR:
source-address and source-address-wildcarded cannot be defined in ACL together
SOURCE_ADDRESS_WILDCARDED_MISSING_FIELDS_ERROR:
source-address-wildcarded must contain address and wildcard-mask
nodetype: container (rw)
description:
IPv4 address.
nodetype: leaf (rw)
type: oc-inet:ipv4-address
description:
IPv4 wildcard mask.
nodetype: leaf (rw)
type: oc-inet:ipv4-address
description:
The IP packet's hop range (TTL)
nodetype: leaf (rw)
type: hop-range
description:
State information for IPv4 match fields
nodetype: container (ro)
description:
Source IPv4 address prefix.
nodetype: leaf (ro)
type: oc-inet:ipv4-prefix
description:
Destination IPv4 address prefix.
nodetype: leaf (ro)
type: oc-inet:ipv4-prefix
description:
Value of diffserv codepoint.
nodetype: leaf (ro)
type: oc-inet:dscp
description:
The protocol carried in the IP packet, expressed either
as its IP protocol number, or by a defined identity.
nodetype: leaf (ro)
type: oc-pkt-match-types:ip-protocol-type
description:
The IP packet's hop limit -- known as TTL (in hops) in
IPv4 packets, and hop limit in IPv6
nodetype: leaf (ro)
type: uint8
description:
Top-level container for IPv6 match field data
frinx-device-type:
ios
frinx-supported-versions:
12any,15any
frinx-implemented-reader:
io.frinx.cli.unit.ios.unit.acl.handler.AclEntryReader
frinx-implemented-reader-details:
IPV6_SEQUENCE_PATTERN:
^.*sequence (?<sequenceId>\d+)$
IP_SEQUENCE_PATTERN:
^\s*(?<sequenceId>\d+) (?!remark).*
SH_ACCESS_LISTS_IPV4:
show ip access-lists %s
SH_ACCESS_LISTS_IPV6:
show ipv6 access-list %s
frinx-implemented-writer:
io.frinx.cli.unit.ios.unit.acl.handler.AclEntryWriter
frinx-implemented-writer-details:
ACL_DELETE:
configure terminal
ip access-list extended {$aclName}
no {$aclSeqId}
end
ACL_ICMP_ENTRY:
configure terminal
ip access-list extended {$aclName}
{$aclSeqId} {$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclDstAddr} {$aclIcmpMsgType} {$aclTtl}
end
ACL_ICMP_IP6_ENTRY:
configure terminal
ipv6 access-list {$aclName}
{$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclDstAddr} {$aclIcmpMsgType} {$aclTtl} {$aclSeqId}
end
ACL_IP6_DELETE:
configure terminal
ipv6 access-list {$aclName}
no sequence {$aclSeqId}
end
ACL_IP6_ENTRY:
configure terminal
ipv6 access-list {$aclName}
{$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclDstAddr} {$aclTtl} {$aclSeqId}
end
ACL_IP_ENTRY:
configure terminal
ip access-list extended {$aclName}
{$aclSeqId} {$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclDstAddr} {$aclTtl}
end
ACL_TCP_ENTRY:
configure terminal
ip access-list extended {$aclName}
{$aclSeqId} {$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclSrcPort} {$aclDstAddr} {$aclDstPort} {$aclTtl}
end
ACL_TCP_IP6_ENTRY:
configure terminal
ipv6 access-list {$aclName}
{$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclSrcPort} {$aclDstAddr} {$aclDstPort} {$aclTtl} {$aclSeqId}
end
ANY:
any
DESTINATION_ADDRESS_AND_DESTINATION_ADDRESS_WILDCARDED_TOGETHER_ERROR:
destination-address and destination-address-wildcarded cannot be defined in ACL together
DESTINATION_ADDRESS_WILDCARDED_MISSING_FIELDS_ERROR:
destination-address-wildcarded must contain address and wildcard-mask
NONE_DESTINATION_ADDRESS_OR_DESTINATION_ADDRESS_WILDCARDED_ERROR:
destination-address or destination-address-wildcarded must be defined in ACL
NONE_SOURCE_ADDRESS_OR_SOURCE_ADDRESS_WILDCARDED_ERROR:
source-address or source-address-wildcarded must be defined in ACL
RANGE_SEPARATOR:
..
SOURCE_ADDRESS_AND_SOURCE_ADDRESS_WILDCARDED_TOGETHER_ERROR:
source-address and source-address-wildcarded cannot be defined in ACL together
SOURCE_ADDRESS_WILDCARDED_MISSING_FIELDS_ERROR:
source-address-wildcarded must contain address and wildcard-mask
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.unit.acl.handler.AclEntryReader
frinx-implemented-reader-details:
SEQUENCE_PATTERN:
^\s*(?<sequenceId>\d+) (?!remark).*
SH_ACCESS_LISTS_IPV4:
show running-config ipv4 access-list %s
SH_ACCESS_LISTS_IPV6:
show running-config ipv6 access-list %s
frinx-implemented-writer:
io.frinx.cli.unit.iosxr.unit.acl.handler.AclEntryWriter
frinx-implemented-writer-details:
ACL_DELETE:
{$type} access-list {$aclName}
no {$aclSeqId}
root
ACL_ICMP_ENTRY:
{$type} access-list {$aclName}
{$aclSeqId} {$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclDstAddr} {$aclIcmpMsgType} {$aclTtl}
root
ACL_IP_ENTRY:
{$type} access-list {$aclName}
{$aclSeqId} {$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclDstAddr} {$aclTtl}
root
ACL_TCP_ENTRY:
{$type} access-list {$aclName}
{$aclSeqId} {$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclSrcPort} {$aclDstAddr} {$aclDstPort} {$aclTtl}
root
ANY:
any
DESTINATION_ADDRESS_AND_DESTINATION_ADDRESS_WILDCARDED_TOGETHER_ERROR:
destination-address and destination-address-wildcarded cannot be defined in ACL together
DESTINATION_ADDRESS_WILDCARDED_MISSING_FIELDS_ERROR:
destination-address-wildcarded must contain address and wildcard-mask
NONE_DESTINATION_ADDRESS_OR_DESTINATION_ADDRESS_WILDCARDED_ERROR:
destination-address or destination-address-wildcarded must be defined in ACL
NONE_SOURCE_ADDRESS_OR_SOURCE_ADDRESS_WILDCARDED_ERROR:
source-address or source-address-wildcarded must be defined in ACL
RANGE_SEPARATOR:
..
SOURCE_ADDRESS_AND_SOURCE_ADDRESS_WILDCARDED_TOGETHER_ERROR:
source-address and source-address-wildcarded cannot be defined in ACL together
SOURCE_ADDRESS_WILDCARDED_MISSING_FIELDS_ERROR:
source-address-wildcarded must contain address and wildcard-mask
nodetype: container (rw)
description:
Configuration data for IPv6 match fields
frinx-device-type:
ios
frinx-supported-versions:
12any,15any
frinx-implemented-reader:
io.frinx.cli.unit.ios.unit.acl.handler.AclEntryReader
frinx-implemented-reader-details:
IPV6_SEQUENCE_PATTERN:
^.*sequence (?<sequenceId>\d+)$
IP_SEQUENCE_PATTERN:
^\s*(?<sequenceId>\d+) (?!remark).*
SH_ACCESS_LISTS_IPV4:
show ip access-lists %s
SH_ACCESS_LISTS_IPV6:
show ipv6 access-list %s
frinx-implemented-writer:
io.frinx.cli.unit.ios.unit.acl.handler.AclEntryWriter
frinx-implemented-writer-details:
ACL_DELETE:
configure terminal
ip access-list extended {$aclName}
no {$aclSeqId}
end
ACL_ICMP_ENTRY:
configure terminal
ip access-list extended {$aclName}
{$aclSeqId} {$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclDstAddr} {$aclIcmpMsgType} {$aclTtl}
end
ACL_ICMP_IP6_ENTRY:
configure terminal
ipv6 access-list {$aclName}
{$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclDstAddr} {$aclIcmpMsgType} {$aclTtl} {$aclSeqId}
end
ACL_IP6_DELETE:
configure terminal
ipv6 access-list {$aclName}
no sequence {$aclSeqId}
end
ACL_IP6_ENTRY:
configure terminal
ipv6 access-list {$aclName}
{$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclDstAddr} {$aclTtl} {$aclSeqId}
end
ACL_IP_ENTRY:
configure terminal
ip access-list extended {$aclName}
{$aclSeqId} {$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclDstAddr} {$aclTtl}
end
ACL_TCP_ENTRY:
configure terminal
ip access-list extended {$aclName}
{$aclSeqId} {$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclSrcPort} {$aclDstAddr} {$aclDstPort} {$aclTtl}
end
ACL_TCP_IP6_ENTRY:
configure terminal
ipv6 access-list {$aclName}
{$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclSrcPort} {$aclDstAddr} {$aclDstPort} {$aclTtl} {$aclSeqId}
end
ANY:
any
DESTINATION_ADDRESS_AND_DESTINATION_ADDRESS_WILDCARDED_TOGETHER_ERROR:
destination-address and destination-address-wildcarded cannot be defined in ACL together
DESTINATION_ADDRESS_WILDCARDED_MISSING_FIELDS_ERROR:
destination-address-wildcarded must contain address and wildcard-mask
NONE_DESTINATION_ADDRESS_OR_DESTINATION_ADDRESS_WILDCARDED_ERROR:
destination-address or destination-address-wildcarded must be defined in ACL
NONE_SOURCE_ADDRESS_OR_SOURCE_ADDRESS_WILDCARDED_ERROR:
source-address or source-address-wildcarded must be defined in ACL
RANGE_SEPARATOR:
..
SOURCE_ADDRESS_AND_SOURCE_ADDRESS_WILDCARDED_TOGETHER_ERROR:
source-address and source-address-wildcarded cannot be defined in ACL together
SOURCE_ADDRESS_WILDCARDED_MISSING_FIELDS_ERROR:
source-address-wildcarded must contain address and wildcard-mask
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.unit.acl.handler.AclEntryReader
frinx-implemented-reader-details:
SEQUENCE_PATTERN:
^\s*(?<sequenceId>\d+) (?!remark).*
SH_ACCESS_LISTS_IPV4:
show running-config ipv4 access-list %s
SH_ACCESS_LISTS_IPV6:
show running-config ipv6 access-list %s
frinx-implemented-writer:
io.frinx.cli.unit.iosxr.unit.acl.handler.AclEntryWriter
frinx-implemented-writer-details:
ACL_DELETE:
{$type} access-list {$aclName}
no {$aclSeqId}
root
ACL_ICMP_ENTRY:
{$type} access-list {$aclName}
{$aclSeqId} {$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclDstAddr} {$aclIcmpMsgType} {$aclTtl}
root
ACL_IP_ENTRY:
{$type} access-list {$aclName}
{$aclSeqId} {$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclDstAddr} {$aclTtl}
root
ACL_TCP_ENTRY:
{$type} access-list {$aclName}
{$aclSeqId} {$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclSrcPort} {$aclDstAddr} {$aclDstPort} {$aclTtl}
root
ANY:
any
DESTINATION_ADDRESS_AND_DESTINATION_ADDRESS_WILDCARDED_TOGETHER_ERROR:
destination-address and destination-address-wildcarded cannot be defined in ACL together
DESTINATION_ADDRESS_WILDCARDED_MISSING_FIELDS_ERROR:
destination-address-wildcarded must contain address and wildcard-mask
NONE_DESTINATION_ADDRESS_OR_DESTINATION_ADDRESS_WILDCARDED_ERROR:
destination-address or destination-address-wildcarded must be defined in ACL
NONE_SOURCE_ADDRESS_OR_SOURCE_ADDRESS_WILDCARDED_ERROR:
source-address or source-address-wildcarded must be defined in ACL
RANGE_SEPARATOR:
..
SOURCE_ADDRESS_AND_SOURCE_ADDRESS_WILDCARDED_TOGETHER_ERROR:
source-address and source-address-wildcarded cannot be defined in ACL together
SOURCE_ADDRESS_WILDCARDED_MISSING_FIELDS_ERROR:
source-address-wildcarded must contain address and wildcard-mask
nodetype: container (rw)
description:
Source IPv6 address prefix.
nodetype: leaf (rw)
type: oc-inet:ipv6-prefix
description:
Source IPv6 Flow label.
nodetype: leaf (rw)
type: oc-inet:ipv6-flow-label
description:
Destination IPv6 address prefix.
nodetype: leaf (rw)
type: oc-inet:ipv6-prefix
description:
Destination IPv6 Flow label.
nodetype: leaf (rw)
type: oc-inet:ipv6-flow-label
description:
Value of diffserv codepoint.
nodetype: leaf (rw)
type: oc-inet:dscp
description:
The protocol carried in the IP packet, expressed either
as its IP protocol number, or by a defined identity.
nodetype: leaf (rw)
type: oc-pkt-match-types:ip-protocol-type
description:
The IP packet's hop limit -- known as TTL (in hops) in
IPv4 packets, and hop limit in IPv6
nodetype: leaf (rw)
type: uint8
frinx-device-type:
ios
frinx-supported-versions:
12any,15any
frinx-implemented-reader:
MISSING READER
frinx-implemented-writer:
io.frinx.cli.unit.ios.unit.acl.handler.AclEntryWriter
frinx-implemented-writer-details:
ACL_DELETE:
configure terminal
ip access-list extended {$aclName}
no {$aclSeqId}
end
ACL_ICMP_ENTRY:
configure terminal
ip access-list extended {$aclName}
{$aclSeqId} {$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclDstAddr} {$aclIcmpMsgType} {$aclTtl}
end
ACL_ICMP_IP6_ENTRY:
configure terminal
ipv6 access-list {$aclName}
{$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclDstAddr} {$aclIcmpMsgType} {$aclTtl} {$aclSeqId}
end
ACL_IP6_DELETE:
configure terminal
ipv6 access-list {$aclName}
no sequence {$aclSeqId}
end
ACL_IP6_ENTRY:
configure terminal
ipv6 access-list {$aclName}
{$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclDstAddr} {$aclTtl} {$aclSeqId}
end
ACL_IP_ENTRY:
configure terminal
ip access-list extended {$aclName}
{$aclSeqId} {$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclDstAddr} {$aclTtl}
end
ACL_TCP_ENTRY:
configure terminal
ip access-list extended {$aclName}
{$aclSeqId} {$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclSrcPort} {$aclDstAddr} {$aclDstPort} {$aclTtl}
end
ACL_TCP_IP6_ENTRY:
configure terminal
ipv6 access-list {$aclName}
{$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclSrcPort} {$aclDstAddr} {$aclDstPort} {$aclTtl} {$aclSeqId}
end
ANY:
any
DESTINATION_ADDRESS_AND_DESTINATION_ADDRESS_WILDCARDED_TOGETHER_ERROR:
destination-address and destination-address-wildcarded cannot be defined in ACL together
DESTINATION_ADDRESS_WILDCARDED_MISSING_FIELDS_ERROR:
destination-address-wildcarded must contain address and wildcard-mask
NONE_DESTINATION_ADDRESS_OR_DESTINATION_ADDRESS_WILDCARDED_ERROR:
destination-address or destination-address-wildcarded must be defined in ACL
NONE_SOURCE_ADDRESS_OR_SOURCE_ADDRESS_WILDCARDED_ERROR:
source-address or source-address-wildcarded must be defined in ACL
RANGE_SEPARATOR:
..
SOURCE_ADDRESS_AND_SOURCE_ADDRESS_WILDCARDED_TOGETHER_ERROR:
source-address and source-address-wildcarded cannot be defined in ACL together
SOURCE_ADDRESS_WILDCARDED_MISSING_FIELDS_ERROR:
source-address-wildcarded must contain address and wildcard-mask
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
MISSING READER
frinx-implemented-writer:
io.frinx.cli.unit.iosxr.unit.acl.handler.AclEntryWriter
frinx-implemented-writer-details:
ACL_DELETE:
{$type} access-list {$aclName}
no {$aclSeqId}
root
ACL_ICMP_ENTRY:
{$type} access-list {$aclName}
{$aclSeqId} {$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclDstAddr} {$aclIcmpMsgType} {$aclTtl}
root
ACL_IP_ENTRY:
{$type} access-list {$aclName}
{$aclSeqId} {$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclDstAddr} {$aclTtl}
root
ACL_TCP_ENTRY:
{$type} access-list {$aclName}
{$aclSeqId} {$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclSrcPort} {$aclDstAddr} {$aclDstPort} {$aclTtl}
root
ANY:
any
DESTINATION_ADDRESS_AND_DESTINATION_ADDRESS_WILDCARDED_TOGETHER_ERROR:
destination-address and destination-address-wildcarded cannot be defined in ACL together
DESTINATION_ADDRESS_WILDCARDED_MISSING_FIELDS_ERROR:
destination-address-wildcarded must contain address and wildcard-mask
NONE_DESTINATION_ADDRESS_OR_DESTINATION_ADDRESS_WILDCARDED_ERROR:
destination-address or destination-address-wildcarded must be defined in ACL
NONE_SOURCE_ADDRESS_OR_SOURCE_ADDRESS_WILDCARDED_ERROR:
source-address or source-address-wildcarded must be defined in ACL
RANGE_SEPARATOR:
..
SOURCE_ADDRESS_AND_SOURCE_ADDRESS_WILDCARDED_TOGETHER_ERROR:
source-address and source-address-wildcarded cannot be defined in ACL together
SOURCE_ADDRESS_WILDCARDED_MISSING_FIELDS_ERROR:
source-address-wildcarded must contain address and wildcard-mask
nodetype: container (rw)
description:
IPv6 address.
nodetype: leaf (rw)
type: oc-inet:ipv6-address
description:
IPv6 wildcard mask.
nodetype: leaf (rw)
type: oc-inet:ipv6-address
frinx-device-type:
ios
frinx-supported-versions:
12any,15any
frinx-implemented-reader:
MISSING READER
frinx-implemented-writer:
io.frinx.cli.unit.ios.unit.acl.handler.AclEntryWriter
frinx-implemented-writer-details:
ACL_DELETE:
configure terminal
ip access-list extended {$aclName}
no {$aclSeqId}
end
ACL_ICMP_ENTRY:
configure terminal
ip access-list extended {$aclName}
{$aclSeqId} {$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclDstAddr} {$aclIcmpMsgType} {$aclTtl}
end
ACL_ICMP_IP6_ENTRY:
configure terminal
ipv6 access-list {$aclName}
{$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclDstAddr} {$aclIcmpMsgType} {$aclTtl} {$aclSeqId}
end
ACL_IP6_DELETE:
configure terminal
ipv6 access-list {$aclName}
no sequence {$aclSeqId}
end
ACL_IP6_ENTRY:
configure terminal
ipv6 access-list {$aclName}
{$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclDstAddr} {$aclTtl} {$aclSeqId}
end
ACL_IP_ENTRY:
configure terminal
ip access-list extended {$aclName}
{$aclSeqId} {$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclDstAddr} {$aclTtl}
end
ACL_TCP_ENTRY:
configure terminal
ip access-list extended {$aclName}
{$aclSeqId} {$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclSrcPort} {$aclDstAddr} {$aclDstPort} {$aclTtl}
end
ACL_TCP_IP6_ENTRY:
configure terminal
ipv6 access-list {$aclName}
{$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclSrcPort} {$aclDstAddr} {$aclDstPort} {$aclTtl} {$aclSeqId}
end
ANY:
any
DESTINATION_ADDRESS_AND_DESTINATION_ADDRESS_WILDCARDED_TOGETHER_ERROR:
destination-address and destination-address-wildcarded cannot be defined in ACL together
DESTINATION_ADDRESS_WILDCARDED_MISSING_FIELDS_ERROR:
destination-address-wildcarded must contain address and wildcard-mask
NONE_DESTINATION_ADDRESS_OR_DESTINATION_ADDRESS_WILDCARDED_ERROR:
destination-address or destination-address-wildcarded must be defined in ACL
NONE_SOURCE_ADDRESS_OR_SOURCE_ADDRESS_WILDCARDED_ERROR:
source-address or source-address-wildcarded must be defined in ACL
RANGE_SEPARATOR:
..
SOURCE_ADDRESS_AND_SOURCE_ADDRESS_WILDCARDED_TOGETHER_ERROR:
source-address and source-address-wildcarded cannot be defined in ACL together
SOURCE_ADDRESS_WILDCARDED_MISSING_FIELDS_ERROR:
source-address-wildcarded must contain address and wildcard-mask
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
MISSING READER
frinx-implemented-writer:
io.frinx.cli.unit.iosxr.unit.acl.handler.AclEntryWriter
frinx-implemented-writer-details:
ACL_DELETE:
{$type} access-list {$aclName}
no {$aclSeqId}
root
ACL_ICMP_ENTRY:
{$type} access-list {$aclName}
{$aclSeqId} {$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclDstAddr} {$aclIcmpMsgType} {$aclTtl}
root
ACL_IP_ENTRY:
{$type} access-list {$aclName}
{$aclSeqId} {$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclDstAddr} {$aclTtl}
root
ACL_TCP_ENTRY:
{$type} access-list {$aclName}
{$aclSeqId} {$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclSrcPort} {$aclDstAddr} {$aclDstPort} {$aclTtl}
root
ANY:
any
DESTINATION_ADDRESS_AND_DESTINATION_ADDRESS_WILDCARDED_TOGETHER_ERROR:
destination-address and destination-address-wildcarded cannot be defined in ACL together
DESTINATION_ADDRESS_WILDCARDED_MISSING_FIELDS_ERROR:
destination-address-wildcarded must contain address and wildcard-mask
NONE_DESTINATION_ADDRESS_OR_DESTINATION_ADDRESS_WILDCARDED_ERROR:
destination-address or destination-address-wildcarded must be defined in ACL
NONE_SOURCE_ADDRESS_OR_SOURCE_ADDRESS_WILDCARDED_ERROR:
source-address or source-address-wildcarded must be defined in ACL
RANGE_SEPARATOR:
..
SOURCE_ADDRESS_AND_SOURCE_ADDRESS_WILDCARDED_TOGETHER_ERROR:
source-address and source-address-wildcarded cannot be defined in ACL together
SOURCE_ADDRESS_WILDCARDED_MISSING_FIELDS_ERROR:
source-address-wildcarded must contain address and wildcard-mask
nodetype: container (rw)
description:
IPv6 address.
nodetype: leaf (rw)
type: oc-inet:ipv6-address
description:
IPv6 wildcard mask.
nodetype: leaf (rw)
type: oc-inet:ipv6-address
description:
The IP packet's hop range (TTL)
nodetype: leaf (rw)
type: hop-range
description:
Operational state data for IPv6 match fields
nodetype: container (ro)
description:
Source IPv6 address prefix.
nodetype: leaf (ro)
type: oc-inet:ipv6-prefix
description:
Source IPv6 Flow label.
nodetype: leaf (ro)
type: oc-inet:ipv6-flow-label
description:
Destination IPv6 address prefix.
nodetype: leaf (ro)
type: oc-inet:ipv6-prefix
description:
Destination IPv6 Flow label.
nodetype: leaf (ro)
type: oc-inet:ipv6-flow-label
description:
Value of diffserv codepoint.
nodetype: leaf (ro)
type: oc-inet:dscp
description:
The protocol carried in the IP packet, expressed either
as its IP protocol number, or by a defined identity.
nodetype: leaf (ro)
type: oc-pkt-match-types:ip-protocol-type
description:
The IP packet's hop limit -- known as TTL (in hops) in
IPv4 packets, and hop limit in IPv6
nodetype: leaf (ro)
type: uint8
description:
Transport fields container
frinx-device-type:
ios
frinx-supported-versions:
12any,15any
frinx-implemented-reader:
io.frinx.cli.unit.ios.unit.acl.handler.AclEntryReader
frinx-implemented-reader-details:
IPV6_SEQUENCE_PATTERN:
^.*sequence (?<sequenceId>\d+)$
IP_SEQUENCE_PATTERN:
^\s*(?<sequenceId>\d+) (?!remark).*
SH_ACCESS_LISTS_IPV4:
show ip access-lists %s
SH_ACCESS_LISTS_IPV6:
show ipv6 access-list %s
frinx-implemented-writer:
io.frinx.cli.unit.ios.unit.acl.handler.AclEntryWriter
frinx-implemented-writer-details:
ACL_DELETE:
configure terminal
ip access-list extended {$aclName}
no {$aclSeqId}
end
ACL_ICMP_ENTRY:
configure terminal
ip access-list extended {$aclName}
{$aclSeqId} {$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclDstAddr} {$aclIcmpMsgType} {$aclTtl}
end
ACL_ICMP_IP6_ENTRY:
configure terminal
ipv6 access-list {$aclName}
{$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclDstAddr} {$aclIcmpMsgType} {$aclTtl} {$aclSeqId}
end
ACL_IP6_DELETE:
configure terminal
ipv6 access-list {$aclName}
no sequence {$aclSeqId}
end
ACL_IP6_ENTRY:
configure terminal
ipv6 access-list {$aclName}
{$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclDstAddr} {$aclTtl} {$aclSeqId}
end
ACL_IP_ENTRY:
configure terminal
ip access-list extended {$aclName}
{$aclSeqId} {$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclDstAddr} {$aclTtl}
end
ACL_TCP_ENTRY:
configure terminal
ip access-list extended {$aclName}
{$aclSeqId} {$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclSrcPort} {$aclDstAddr} {$aclDstPort} {$aclTtl}
end
ACL_TCP_IP6_ENTRY:
configure terminal
ipv6 access-list {$aclName}
{$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclSrcPort} {$aclDstAddr} {$aclDstPort} {$aclTtl} {$aclSeqId}
end
ANY:
any
DESTINATION_ADDRESS_AND_DESTINATION_ADDRESS_WILDCARDED_TOGETHER_ERROR:
destination-address and destination-address-wildcarded cannot be defined in ACL together
DESTINATION_ADDRESS_WILDCARDED_MISSING_FIELDS_ERROR:
destination-address-wildcarded must contain address and wildcard-mask
NONE_DESTINATION_ADDRESS_OR_DESTINATION_ADDRESS_WILDCARDED_ERROR:
destination-address or destination-address-wildcarded must be defined in ACL
NONE_SOURCE_ADDRESS_OR_SOURCE_ADDRESS_WILDCARDED_ERROR:
source-address or source-address-wildcarded must be defined in ACL
RANGE_SEPARATOR:
..
SOURCE_ADDRESS_AND_SOURCE_ADDRESS_WILDCARDED_TOGETHER_ERROR:
source-address and source-address-wildcarded cannot be defined in ACL together
SOURCE_ADDRESS_WILDCARDED_MISSING_FIELDS_ERROR:
source-address-wildcarded must contain address and wildcard-mask
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.unit.acl.handler.AclEntryReader
frinx-implemented-reader-details:
SEQUENCE_PATTERN:
^\s*(?<sequenceId>\d+) (?!remark).*
SH_ACCESS_LISTS_IPV4:
show running-config ipv4 access-list %s
SH_ACCESS_LISTS_IPV6:
show running-config ipv6 access-list %s
frinx-implemented-writer:
io.frinx.cli.unit.iosxr.unit.acl.handler.AclEntryWriter
frinx-implemented-writer-details:
ACL_DELETE:
{$type} access-list {$aclName}
no {$aclSeqId}
root
ACL_ICMP_ENTRY:
{$type} access-list {$aclName}
{$aclSeqId} {$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclDstAddr} {$aclIcmpMsgType} {$aclTtl}
root
ACL_IP_ENTRY:
{$type} access-list {$aclName}
{$aclSeqId} {$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclDstAddr} {$aclTtl}
root
ACL_TCP_ENTRY:
{$type} access-list {$aclName}
{$aclSeqId} {$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclSrcPort} {$aclDstAddr} {$aclDstPort} {$aclTtl}
root
ANY:
any
DESTINATION_ADDRESS_AND_DESTINATION_ADDRESS_WILDCARDED_TOGETHER_ERROR:
destination-address and destination-address-wildcarded cannot be defined in ACL together
DESTINATION_ADDRESS_WILDCARDED_MISSING_FIELDS_ERROR:
destination-address-wildcarded must contain address and wildcard-mask
NONE_DESTINATION_ADDRESS_OR_DESTINATION_ADDRESS_WILDCARDED_ERROR:
destination-address or destination-address-wildcarded must be defined in ACL
NONE_SOURCE_ADDRESS_OR_SOURCE_ADDRESS_WILDCARDED_ERROR:
source-address or source-address-wildcarded must be defined in ACL
RANGE_SEPARATOR:
..
SOURCE_ADDRESS_AND_SOURCE_ADDRESS_WILDCARDED_TOGETHER_ERROR:
source-address and source-address-wildcarded cannot be defined in ACL together
SOURCE_ADDRESS_WILDCARDED_MISSING_FIELDS_ERROR:
source-address-wildcarded must contain address and wildcard-mask
nodetype: container (rw)
description:
Configuration data
frinx-device-type:
ios
frinx-supported-versions:
12any,15any
frinx-implemented-reader:
io.frinx.cli.unit.ios.unit.acl.handler.AclEntryReader
frinx-implemented-reader-details:
IPV6_SEQUENCE_PATTERN:
^.*sequence (?<sequenceId>\d+)$
IP_SEQUENCE_PATTERN:
^\s*(?<sequenceId>\d+) (?!remark).*
SH_ACCESS_LISTS_IPV4:
show ip access-lists %s
SH_ACCESS_LISTS_IPV6:
show ipv6 access-list %s
frinx-implemented-writer:
io.frinx.cli.unit.ios.unit.acl.handler.AclEntryWriter
frinx-implemented-writer-details:
ACL_DELETE:
configure terminal
ip access-list extended {$aclName}
no {$aclSeqId}
end
ACL_ICMP_ENTRY:
configure terminal
ip access-list extended {$aclName}
{$aclSeqId} {$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclDstAddr} {$aclIcmpMsgType} {$aclTtl}
end
ACL_ICMP_IP6_ENTRY:
configure terminal
ipv6 access-list {$aclName}
{$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclDstAddr} {$aclIcmpMsgType} {$aclTtl} {$aclSeqId}
end
ACL_IP6_DELETE:
configure terminal
ipv6 access-list {$aclName}
no sequence {$aclSeqId}
end
ACL_IP6_ENTRY:
configure terminal
ipv6 access-list {$aclName}
{$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclDstAddr} {$aclTtl} {$aclSeqId}
end
ACL_IP_ENTRY:
configure terminal
ip access-list extended {$aclName}
{$aclSeqId} {$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclDstAddr} {$aclTtl}
end
ACL_TCP_ENTRY:
configure terminal
ip access-list extended {$aclName}
{$aclSeqId} {$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclSrcPort} {$aclDstAddr} {$aclDstPort} {$aclTtl}
end
ACL_TCP_IP6_ENTRY:
configure terminal
ipv6 access-list {$aclName}
{$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclSrcPort} {$aclDstAddr} {$aclDstPort} {$aclTtl} {$aclSeqId}
end
ANY:
any
DESTINATION_ADDRESS_AND_DESTINATION_ADDRESS_WILDCARDED_TOGETHER_ERROR:
destination-address and destination-address-wildcarded cannot be defined in ACL together
DESTINATION_ADDRESS_WILDCARDED_MISSING_FIELDS_ERROR:
destination-address-wildcarded must contain address and wildcard-mask
NONE_DESTINATION_ADDRESS_OR_DESTINATION_ADDRESS_WILDCARDED_ERROR:
destination-address or destination-address-wildcarded must be defined in ACL
NONE_SOURCE_ADDRESS_OR_SOURCE_ADDRESS_WILDCARDED_ERROR:
source-address or source-address-wildcarded must be defined in ACL
RANGE_SEPARATOR:
..
SOURCE_ADDRESS_AND_SOURCE_ADDRESS_WILDCARDED_TOGETHER_ERROR:
source-address and source-address-wildcarded cannot be defined in ACL together
SOURCE_ADDRESS_WILDCARDED_MISSING_FIELDS_ERROR:
source-address-wildcarded must contain address and wildcard-mask
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.unit.acl.handler.AclEntryReader
frinx-implemented-reader-details:
SEQUENCE_PATTERN:
^\s*(?<sequenceId>\d+) (?!remark).*
SH_ACCESS_LISTS_IPV4:
show running-config ipv4 access-list %s
SH_ACCESS_LISTS_IPV6:
show running-config ipv6 access-list %s
frinx-implemented-writer:
io.frinx.cli.unit.iosxr.unit.acl.handler.AclEntryWriter
frinx-implemented-writer-details:
ACL_DELETE:
{$type} access-list {$aclName}
no {$aclSeqId}
root
ACL_ICMP_ENTRY:
{$type} access-list {$aclName}
{$aclSeqId} {$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclDstAddr} {$aclIcmpMsgType} {$aclTtl}
root
ACL_IP_ENTRY:
{$type} access-list {$aclName}
{$aclSeqId} {$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclDstAddr} {$aclTtl}
root
ACL_TCP_ENTRY:
{$type} access-list {$aclName}
{$aclSeqId} {$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclSrcPort} {$aclDstAddr} {$aclDstPort} {$aclTtl}
root
ANY:
any
DESTINATION_ADDRESS_AND_DESTINATION_ADDRESS_WILDCARDED_TOGETHER_ERROR:
destination-address and destination-address-wildcarded cannot be defined in ACL together
DESTINATION_ADDRESS_WILDCARDED_MISSING_FIELDS_ERROR:
destination-address-wildcarded must contain address and wildcard-mask
NONE_DESTINATION_ADDRESS_OR_DESTINATION_ADDRESS_WILDCARDED_ERROR:
destination-address or destination-address-wildcarded must be defined in ACL
NONE_SOURCE_ADDRESS_OR_SOURCE_ADDRESS_WILDCARDED_ERROR:
source-address or source-address-wildcarded must be defined in ACL
RANGE_SEPARATOR:
..
SOURCE_ADDRESS_AND_SOURCE_ADDRESS_WILDCARDED_TOGETHER_ERROR:
source-address and source-address-wildcarded cannot be defined in ACL together
SOURCE_ADDRESS_WILDCARDED_MISSING_FIELDS_ERROR:
source-address-wildcarded must contain address and wildcard-mask
nodetype: container (rw)
description:
Source port or range
nodetype: leaf (rw)
type: oc-pkt-match-types:port-num-range
description:
Destination port or range
nodetype: leaf (rw)
type: oc-pkt-match-types:port-num-range
description:
List of TCP flags to match
nodetype: leaf-list (rw)
type: identityref
description:
Source port represented by name.
nodetype: leaf (rw)
type: string
description:
Destination port represented by name.
nodetype: leaf (rw)
type: string
description:
State data
nodetype: container (ro)
description:
Source port or range
nodetype: leaf (ro)
type: oc-pkt-match-types:port-num-range
description:
Destination port or range
nodetype: leaf (ro)
type: oc-pkt-match-types:port-num-range
description:
List of TCP flags to match
nodetype: leaf-list (ro)
type: identityref
description:
Input interface container
nodetype: container (rw)
description:
Config data
nodetype: container (rw)
description:
State information
nodetype: container (ro)
description:
Reference to an interface or subinterface
nodetype: container (rw)
description:
Configured reference to interface / subinterface
nodetype: container (rw)
description:
Reference to a base interface. If a reference to a
subinterface is required, this leaf must be specified
to indicate the base interface.
nodetype: leaf (rw)
type: leafref
description:
Reference to a subinterface -- this requires the base
interface to be specified using the interface leaf in
this container. If only a reference to a base interface
is requuired, this leaf should not be set.
nodetype: leaf (rw)
type: leafref
description:
Operational state for interface-ref
nodetype: container (ro)
description:
Reference to a base interface. If a reference to a
subinterface is required, this leaf must be specified
to indicate the base interface.
nodetype: leaf (ro)
type: leafref
description:
Reference to a subinterface -- this requires the base
interface to be specified using the interface leaf in
this container. If only a reference to a base interface
is requuired, this leaf should not be set.
nodetype: leaf (ro)
type: leafref
description:
Enclosing container for list of ACL actions associated
with an entry
frinx-device-type:
ios
frinx-supported-versions:
12any,15any
frinx-implemented-reader:
io.frinx.cli.unit.ios.unit.acl.handler.AclEntryReader
frinx-implemented-reader-details:
IPV6_SEQUENCE_PATTERN:
^.*sequence (?<sequenceId>\d+)$
IP_SEQUENCE_PATTERN:
^\s*(?<sequenceId>\d+) (?!remark).*
SH_ACCESS_LISTS_IPV4:
show ip access-lists %s
SH_ACCESS_LISTS_IPV6:
show ipv6 access-list %s
frinx-implemented-writer:
io.frinx.cli.unit.ios.unit.acl.handler.AclEntryWriter
frinx-implemented-writer-details:
ACL_DELETE:
configure terminal
ip access-list extended {$aclName}
no {$aclSeqId}
end
ACL_ICMP_ENTRY:
configure terminal
ip access-list extended {$aclName}
{$aclSeqId} {$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclDstAddr} {$aclIcmpMsgType} {$aclTtl}
end
ACL_ICMP_IP6_ENTRY:
configure terminal
ipv6 access-list {$aclName}
{$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclDstAddr} {$aclIcmpMsgType} {$aclTtl} {$aclSeqId}
end
ACL_IP6_DELETE:
configure terminal
ipv6 access-list {$aclName}
no sequence {$aclSeqId}
end
ACL_IP6_ENTRY:
configure terminal
ipv6 access-list {$aclName}
{$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclDstAddr} {$aclTtl} {$aclSeqId}
end
ACL_IP_ENTRY:
configure terminal
ip access-list extended {$aclName}
{$aclSeqId} {$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclDstAddr} {$aclTtl}
end
ACL_TCP_ENTRY:
configure terminal
ip access-list extended {$aclName}
{$aclSeqId} {$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclSrcPort} {$aclDstAddr} {$aclDstPort} {$aclTtl}
end
ACL_TCP_IP6_ENTRY:
configure terminal
ipv6 access-list {$aclName}
{$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclSrcPort} {$aclDstAddr} {$aclDstPort} {$aclTtl} {$aclSeqId}
end
ANY:
any
DESTINATION_ADDRESS_AND_DESTINATION_ADDRESS_WILDCARDED_TOGETHER_ERROR:
destination-address and destination-address-wildcarded cannot be defined in ACL together
DESTINATION_ADDRESS_WILDCARDED_MISSING_FIELDS_ERROR:
destination-address-wildcarded must contain address and wildcard-mask
NONE_DESTINATION_ADDRESS_OR_DESTINATION_ADDRESS_WILDCARDED_ERROR:
destination-address or destination-address-wildcarded must be defined in ACL
NONE_SOURCE_ADDRESS_OR_SOURCE_ADDRESS_WILDCARDED_ERROR:
source-address or source-address-wildcarded must be defined in ACL
RANGE_SEPARATOR:
..
SOURCE_ADDRESS_AND_SOURCE_ADDRESS_WILDCARDED_TOGETHER_ERROR:
source-address and source-address-wildcarded cannot be defined in ACL together
SOURCE_ADDRESS_WILDCARDED_MISSING_FIELDS_ERROR:
source-address-wildcarded must contain address and wildcard-mask
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.unit.acl.handler.AclEntryReader
frinx-implemented-reader-details:
SEQUENCE_PATTERN:
^\s*(?<sequenceId>\d+) (?!remark).*
SH_ACCESS_LISTS_IPV4:
show running-config ipv4 access-list %s
SH_ACCESS_LISTS_IPV6:
show running-config ipv6 access-list %s
frinx-implemented-writer:
io.frinx.cli.unit.iosxr.unit.acl.handler.AclEntryWriter
frinx-implemented-writer-details:
ACL_DELETE:
{$type} access-list {$aclName}
no {$aclSeqId}
root
ACL_ICMP_ENTRY:
{$type} access-list {$aclName}
{$aclSeqId} {$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclDstAddr} {$aclIcmpMsgType} {$aclTtl}
root
ACL_IP_ENTRY:
{$type} access-list {$aclName}
{$aclSeqId} {$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclDstAddr} {$aclTtl}
root
ACL_TCP_ENTRY:
{$type} access-list {$aclName}
{$aclSeqId} {$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclSrcPort} {$aclDstAddr} {$aclDstPort} {$aclTtl}
root
ANY:
any
DESTINATION_ADDRESS_AND_DESTINATION_ADDRESS_WILDCARDED_TOGETHER_ERROR:
destination-address and destination-address-wildcarded cannot be defined in ACL together
DESTINATION_ADDRESS_WILDCARDED_MISSING_FIELDS_ERROR:
destination-address-wildcarded must contain address and wildcard-mask
NONE_DESTINATION_ADDRESS_OR_DESTINATION_ADDRESS_WILDCARDED_ERROR:
destination-address or destination-address-wildcarded must be defined in ACL
NONE_SOURCE_ADDRESS_OR_SOURCE_ADDRESS_WILDCARDED_ERROR:
source-address or source-address-wildcarded must be defined in ACL
RANGE_SEPARATOR:
..
SOURCE_ADDRESS_AND_SOURCE_ADDRESS_WILDCARDED_TOGETHER_ERROR:
source-address and source-address-wildcarded cannot be defined in ACL together
SOURCE_ADDRESS_WILDCARDED_MISSING_FIELDS_ERROR:
source-address-wildcarded must contain address and wildcard-mask
nodetype: container (rw)
description:
Config data for ACL actions
frinx-device-type:
ios
frinx-supported-versions:
12any,15any
frinx-implemented-reader:
io.frinx.cli.unit.ios.unit.acl.handler.AclEntryReader
frinx-implemented-reader-details:
IPV6_SEQUENCE_PATTERN:
^.*sequence (?<sequenceId>\d+)$
IP_SEQUENCE_PATTERN:
^\s*(?<sequenceId>\d+) (?!remark).*
SH_ACCESS_LISTS_IPV4:
show ip access-lists %s
SH_ACCESS_LISTS_IPV6:
show ipv6 access-list %s
frinx-implemented-writer:
io.frinx.cli.unit.ios.unit.acl.handler.AclEntryWriter
frinx-implemented-writer-details:
ACL_DELETE:
configure terminal
ip access-list extended {$aclName}
no {$aclSeqId}
end
ACL_ICMP_ENTRY:
configure terminal
ip access-list extended {$aclName}
{$aclSeqId} {$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclDstAddr} {$aclIcmpMsgType} {$aclTtl}
end
ACL_ICMP_IP6_ENTRY:
configure terminal
ipv6 access-list {$aclName}
{$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclDstAddr} {$aclIcmpMsgType} {$aclTtl} {$aclSeqId}
end
ACL_IP6_DELETE:
configure terminal
ipv6 access-list {$aclName}
no sequence {$aclSeqId}
end
ACL_IP6_ENTRY:
configure terminal
ipv6 access-list {$aclName}
{$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclDstAddr} {$aclTtl} {$aclSeqId}
end
ACL_IP_ENTRY:
configure terminal
ip access-list extended {$aclName}
{$aclSeqId} {$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclDstAddr} {$aclTtl}
end
ACL_TCP_ENTRY:
configure terminal
ip access-list extended {$aclName}
{$aclSeqId} {$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclSrcPort} {$aclDstAddr} {$aclDstPort} {$aclTtl}
end
ACL_TCP_IP6_ENTRY:
configure terminal
ipv6 access-list {$aclName}
{$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclSrcPort} {$aclDstAddr} {$aclDstPort} {$aclTtl} {$aclSeqId}
end
ANY:
any
DESTINATION_ADDRESS_AND_DESTINATION_ADDRESS_WILDCARDED_TOGETHER_ERROR:
destination-address and destination-address-wildcarded cannot be defined in ACL together
DESTINATION_ADDRESS_WILDCARDED_MISSING_FIELDS_ERROR:
destination-address-wildcarded must contain address and wildcard-mask
NONE_DESTINATION_ADDRESS_OR_DESTINATION_ADDRESS_WILDCARDED_ERROR:
destination-address or destination-address-wildcarded must be defined in ACL
NONE_SOURCE_ADDRESS_OR_SOURCE_ADDRESS_WILDCARDED_ERROR:
source-address or source-address-wildcarded must be defined in ACL
RANGE_SEPARATOR:
..
SOURCE_ADDRESS_AND_SOURCE_ADDRESS_WILDCARDED_TOGETHER_ERROR:
source-address and source-address-wildcarded cannot be defined in ACL together
SOURCE_ADDRESS_WILDCARDED_MISSING_FIELDS_ERROR:
source-address-wildcarded must contain address and wildcard-mask
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.unit.acl.handler.AclEntryReader
frinx-implemented-reader-details:
SEQUENCE_PATTERN:
^\s*(?<sequenceId>\d+) (?!remark).*
SH_ACCESS_LISTS_IPV4:
show running-config ipv4 access-list %s
SH_ACCESS_LISTS_IPV6:
show running-config ipv6 access-list %s
frinx-implemented-writer:
io.frinx.cli.unit.iosxr.unit.acl.handler.AclEntryWriter
frinx-implemented-writer-details:
ACL_DELETE:
{$type} access-list {$aclName}
no {$aclSeqId}
root
ACL_ICMP_ENTRY:
{$type} access-list {$aclName}
{$aclSeqId} {$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclDstAddr} {$aclIcmpMsgType} {$aclTtl}
root
ACL_IP_ENTRY:
{$type} access-list {$aclName}
{$aclSeqId} {$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclDstAddr} {$aclTtl}
root
ACL_TCP_ENTRY:
{$type} access-list {$aclName}
{$aclSeqId} {$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclSrcPort} {$aclDstAddr} {$aclDstPort} {$aclTtl}
root
ANY:
any
DESTINATION_ADDRESS_AND_DESTINATION_ADDRESS_WILDCARDED_TOGETHER_ERROR:
destination-address and destination-address-wildcarded cannot be defined in ACL together
DESTINATION_ADDRESS_WILDCARDED_MISSING_FIELDS_ERROR:
destination-address-wildcarded must contain address and wildcard-mask
NONE_DESTINATION_ADDRESS_OR_DESTINATION_ADDRESS_WILDCARDED_ERROR:
destination-address or destination-address-wildcarded must be defined in ACL
NONE_SOURCE_ADDRESS_OR_SOURCE_ADDRESS_WILDCARDED_ERROR:
source-address or source-address-wildcarded must be defined in ACL
RANGE_SEPARATOR:
..
SOURCE_ADDRESS_AND_SOURCE_ADDRESS_WILDCARDED_TOGETHER_ERROR:
source-address and source-address-wildcarded cannot be defined in ACL together
SOURCE_ADDRESS_WILDCARDED_MISSING_FIELDS_ERROR:
source-address-wildcarded must contain address and wildcard-mask
nodetype: container (rw)
description:
Specifies the forwarding action. One forwarding action
must be specified for each ACL entry
nodetype: leaf (rw)
type: identityref
description:
Specifies the log action and destination for
matched packets. The default is not to log the
packet.
nodetype: leaf (rw)
type: identityref
description:
action instance name
nodetype: leaf (rw)
type: string
description:
State information for ACL actions
nodetype: container (ro)
description:
Specifies the forwarding action. One forwarding action
must be specified for each ACL entry
nodetype: leaf (ro)
type: identityref
description:
Specifies the log action and destination for
matched packets. The default is not to log the
packet.
nodetype: leaf (ro)
type: identityref
frinx-device-type:
ios
frinx-supported-versions:
12any,15any
frinx-implemented-reader:
io.frinx.cli.unit.ios.unit.acl.handler.AclEntryReader
frinx-implemented-reader-details:
IPV6_SEQUENCE_PATTERN:
^.*sequence (?<sequenceId>\d+)$
IP_SEQUENCE_PATTERN:
^\s*(?<sequenceId>\d+) (?!remark).*
SH_ACCESS_LISTS_IPV4:
show ip access-lists %s
SH_ACCESS_LISTS_IPV6:
show ipv6 access-list %s
frinx-implemented-writer:
io.frinx.cli.unit.ios.unit.acl.handler.AclEntryWriter
frinx-implemented-writer-details:
ACL_DELETE:
configure terminal
ip access-list extended {$aclName}
no {$aclSeqId}
end
ACL_ICMP_ENTRY:
configure terminal
ip access-list extended {$aclName}
{$aclSeqId} {$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclDstAddr} {$aclIcmpMsgType} {$aclTtl}
end
ACL_ICMP_IP6_ENTRY:
configure terminal
ipv6 access-list {$aclName}
{$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclDstAddr} {$aclIcmpMsgType} {$aclTtl} {$aclSeqId}
end
ACL_IP6_DELETE:
configure terminal
ipv6 access-list {$aclName}
no sequence {$aclSeqId}
end
ACL_IP6_ENTRY:
configure terminal
ipv6 access-list {$aclName}
{$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclDstAddr} {$aclTtl} {$aclSeqId}
end
ACL_IP_ENTRY:
configure terminal
ip access-list extended {$aclName}
{$aclSeqId} {$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclDstAddr} {$aclTtl}
end
ACL_TCP_ENTRY:
configure terminal
ip access-list extended {$aclName}
{$aclSeqId} {$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclSrcPort} {$aclDstAddr} {$aclDstPort} {$aclTtl}
end
ACL_TCP_IP6_ENTRY:
configure terminal
ipv6 access-list {$aclName}
{$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclSrcPort} {$aclDstAddr} {$aclDstPort} {$aclTtl} {$aclSeqId}
end
ANY:
any
DESTINATION_ADDRESS_AND_DESTINATION_ADDRESS_WILDCARDED_TOGETHER_ERROR:
destination-address and destination-address-wildcarded cannot be defined in ACL together
DESTINATION_ADDRESS_WILDCARDED_MISSING_FIELDS_ERROR:
destination-address-wildcarded must contain address and wildcard-mask
NONE_DESTINATION_ADDRESS_OR_DESTINATION_ADDRESS_WILDCARDED_ERROR:
destination-address or destination-address-wildcarded must be defined in ACL
NONE_SOURCE_ADDRESS_OR_SOURCE_ADDRESS_WILDCARDED_ERROR:
source-address or source-address-wildcarded must be defined in ACL
RANGE_SEPARATOR:
..
SOURCE_ADDRESS_AND_SOURCE_ADDRESS_WILDCARDED_TOGETHER_ERROR:
source-address and source-address-wildcarded cannot be defined in ACL together
SOURCE_ADDRESS_WILDCARDED_MISSING_FIELDS_ERROR:
source-address-wildcarded must contain address and wildcard-mask
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.unit.acl.handler.AclEntryReader
frinx-implemented-reader-details:
SEQUENCE_PATTERN:
^\s*(?<sequenceId>\d+) (?!remark).*
SH_ACCESS_LISTS_IPV4:
show running-config ipv4 access-list %s
SH_ACCESS_LISTS_IPV6:
show running-config ipv6 access-list %s
frinx-implemented-writer:
io.frinx.cli.unit.iosxr.unit.acl.handler.AclEntryWriter
frinx-implemented-writer-details:
ACL_DELETE:
{$type} access-list {$aclName}
no {$aclSeqId}
root
ACL_ICMP_ENTRY:
{$type} access-list {$aclName}
{$aclSeqId} {$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclDstAddr} {$aclIcmpMsgType} {$aclTtl}
root
ACL_IP_ENTRY:
{$type} access-list {$aclName}
{$aclSeqId} {$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclDstAddr} {$aclTtl}
root
ACL_TCP_ENTRY:
{$type} access-list {$aclName}
{$aclSeqId} {$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclSrcPort} {$aclDstAddr} {$aclDstPort} {$aclTtl}
root
ANY:
any
DESTINATION_ADDRESS_AND_DESTINATION_ADDRESS_WILDCARDED_TOGETHER_ERROR:
destination-address and destination-address-wildcarded cannot be defined in ACL together
DESTINATION_ADDRESS_WILDCARDED_MISSING_FIELDS_ERROR:
destination-address-wildcarded must contain address and wildcard-mask
NONE_DESTINATION_ADDRESS_OR_DESTINATION_ADDRESS_WILDCARDED_ERROR:
destination-address or destination-address-wildcarded must be defined in ACL
NONE_SOURCE_ADDRESS_OR_SOURCE_ADDRESS_WILDCARDED_ERROR:
source-address or source-address-wildcarded must be defined in ACL
RANGE_SEPARATOR:
..
SOURCE_ADDRESS_AND_SOURCE_ADDRESS_WILDCARDED_TOGETHER_ERROR:
source-address and source-address-wildcarded cannot be defined in ACL together
SOURCE_ADDRESS_WILDCARDED_MISSING_FIELDS_ERROR:
source-address-wildcarded must contain address and wildcard-mask
nodetype: container (rw)
frinx-device-type:
ios
frinx-supported-versions:
12any,15any
frinx-implemented-reader:
io.frinx.cli.unit.ios.unit.acl.handler.AclEntryReader
frinx-implemented-reader-details:
IPV6_SEQUENCE_PATTERN:
^.*sequence (?<sequenceId>\d+)$
IP_SEQUENCE_PATTERN:
^\s*(?<sequenceId>\d+) (?!remark).*
SH_ACCESS_LISTS_IPV4:
show ip access-lists %s
SH_ACCESS_LISTS_IPV6:
show ipv6 access-list %s
frinx-implemented-writer:
io.frinx.cli.unit.ios.unit.acl.handler.AclEntryWriter
frinx-implemented-writer-details:
ACL_DELETE:
configure terminal
ip access-list extended {$aclName}
no {$aclSeqId}
end
ACL_ICMP_ENTRY:
configure terminal
ip access-list extended {$aclName}
{$aclSeqId} {$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclDstAddr} {$aclIcmpMsgType} {$aclTtl}
end
ACL_ICMP_IP6_ENTRY:
configure terminal
ipv6 access-list {$aclName}
{$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclDstAddr} {$aclIcmpMsgType} {$aclTtl} {$aclSeqId}
end
ACL_IP6_DELETE:
configure terminal
ipv6 access-list {$aclName}
no sequence {$aclSeqId}
end
ACL_IP6_ENTRY:
configure terminal
ipv6 access-list {$aclName}
{$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclDstAddr} {$aclTtl} {$aclSeqId}
end
ACL_IP_ENTRY:
configure terminal
ip access-list extended {$aclName}
{$aclSeqId} {$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclDstAddr} {$aclTtl}
end
ACL_TCP_ENTRY:
configure terminal
ip access-list extended {$aclName}
{$aclSeqId} {$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclSrcPort} {$aclDstAddr} {$aclDstPort} {$aclTtl}
end
ACL_TCP_IP6_ENTRY:
configure terminal
ipv6 access-list {$aclName}
{$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclSrcPort} {$aclDstAddr} {$aclDstPort} {$aclTtl} {$aclSeqId}
end
ANY:
any
DESTINATION_ADDRESS_AND_DESTINATION_ADDRESS_WILDCARDED_TOGETHER_ERROR:
destination-address and destination-address-wildcarded cannot be defined in ACL together
DESTINATION_ADDRESS_WILDCARDED_MISSING_FIELDS_ERROR:
destination-address-wildcarded must contain address and wildcard-mask
NONE_DESTINATION_ADDRESS_OR_DESTINATION_ADDRESS_WILDCARDED_ERROR:
destination-address or destination-address-wildcarded must be defined in ACL
NONE_SOURCE_ADDRESS_OR_SOURCE_ADDRESS_WILDCARDED_ERROR:
source-address or source-address-wildcarded must be defined in ACL
RANGE_SEPARATOR:
..
SOURCE_ADDRESS_AND_SOURCE_ADDRESS_WILDCARDED_TOGETHER_ERROR:
source-address and source-address-wildcarded cannot be defined in ACL together
SOURCE_ADDRESS_WILDCARDED_MISSING_FIELDS_ERROR:
source-address-wildcarded must contain address and wildcard-mask
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.unit.acl.handler.AclEntryReader
frinx-implemented-reader-details:
SEQUENCE_PATTERN:
^\s*(?<sequenceId>\d+) (?!remark).*
SH_ACCESS_LISTS_IPV4:
show running-config ipv4 access-list %s
SH_ACCESS_LISTS_IPV6:
show running-config ipv6 access-list %s
frinx-implemented-writer:
io.frinx.cli.unit.iosxr.unit.acl.handler.AclEntryWriter
frinx-implemented-writer-details:
ACL_DELETE:
{$type} access-list {$aclName}
no {$aclSeqId}
root
ACL_ICMP_ENTRY:
{$type} access-list {$aclName}
{$aclSeqId} {$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclDstAddr} {$aclIcmpMsgType} {$aclTtl}
root
ACL_IP_ENTRY:
{$type} access-list {$aclName}
{$aclSeqId} {$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclDstAddr} {$aclTtl}
root
ACL_TCP_ENTRY:
{$type} access-list {$aclName}
{$aclSeqId} {$aclFwdAction} {$aclProtocol} {$aclSrcAddr} {$aclSrcPort} {$aclDstAddr} {$aclDstPort} {$aclTtl}
root
ANY:
any
DESTINATION_ADDRESS_AND_DESTINATION_ADDRESS_WILDCARDED_TOGETHER_ERROR:
destination-address and destination-address-wildcarded cannot be defined in ACL together
DESTINATION_ADDRESS_WILDCARDED_MISSING_FIELDS_ERROR:
destination-address-wildcarded must contain address and wildcard-mask
NONE_DESTINATION_ADDRESS_OR_DESTINATION_ADDRESS_WILDCARDED_ERROR:
destination-address or destination-address-wildcarded must be defined in ACL
NONE_SOURCE_ADDRESS_OR_SOURCE_ADDRESS_WILDCARDED_ERROR:
source-address or source-address-wildcarded must be defined in ACL
RANGE_SEPARATOR:
..
SOURCE_ADDRESS_AND_SOURCE_ADDRESS_WILDCARDED_TOGETHER_ERROR:
source-address and source-address-wildcarded cannot be defined in ACL together
SOURCE_ADDRESS_WILDCARDED_MISSING_FIELDS_ERROR:
source-address-wildcarded must contain address and wildcard-mask
nodetype: container (rw)
description:
ICMP message type
nodetype: leaf (rw)
type: icmp-msg-type
description:
Enclosing container for the list of interfaces on which
ACLs are set
frinx-device-type:
junos
frinx-supported-versions:
173
frinx-device-type:
junos
frinx-supported-versions:
182
nodetype: container (rw)
description:
List of interfaces on which ACLs are set
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.unit.acl.handler.AclInterfaceReader
frinx-implemented-reader-details:
IFACE_LINE:
interface (?<name>.+)
SH_IFACES:
show running-config interface
frinx-implemented-writer:
MISSING WRITER
frinx-device-type:
junos
frinx-supported-versions:
14any
frinx-implemented-reader:
io.frinx.cli.unit.junos.unit.acl.handler.AclInterfaceReader
frinx-implemented-reader-details:
IFACE_LINE:
set interfaces (?<ifcname>\S+) unit (?<unit>\S+) family inet filter (input|output) (?<filter>\S+)
SH_IFACES:
show configuration interfaces | display set
frinx-implemented-writer:
io.frinx.cli.unit.junos.unit.acl.handler.AclInterfaceWriter
frinx-device-type:
ios
frinx-supported-versions:
12any,15any
frinx-implemented-reader:
io.frinx.cli.unit.ios.unit.acl.handler.AclInterfaceReader
frinx-implemented-reader-details:
IFACE_LINE:
interface (?<name>.+)
SH_RUN:
show running-config
frinx-implemented-writer:
MISSING WRITER
frinx-device-type:
junos
frinx-supported-versions:
173
frinx-implemented-reader:
io.frinx.unitopo.unit.junos.acl.handler.AclInterfaceReader
frinx-device-type:
junos
frinx-supported-versions:
182
frinx-implemented-reader:
io.frinx.unitopo.unit.junos18.acl.handler.AclInterfaceReader
frinx-implemented-reader-details:
INTERFACE_ID_PATTERN:
(?<interface>[^\.]+)\.(?<unit>.*)
frinx-implemented-writer:
io.frinx.unitopo.unit.junos18.acl.handler.AclInterfaceWriter
nodetype: list (rw)
list keys: [id]
description:
Reference to the interface id list key
nodetype: leaf (list key) (rw)
type: leafref
description:
Configuration for ACL per-interface data
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.unit.acl.handler.AclInterfaceConfigReader
frinx-implemented-writer:
MISSING WRITER
frinx-device-type:
junos
frinx-supported-versions:
14any
frinx-implemented-reader:
io.frinx.cli.unit.junos.unit.acl.handler.AclInterfaceConfigReader
frinx-device-type:
ios
frinx-supported-versions:
12any,15any
frinx-implemented-reader:
io.frinx.cli.unit.ios.unit.acl.handler.AclInterfaceConfigReader
frinx-implemented-writer:
MISSING WRITER
frinx-device-type:
junos
frinx-supported-versions:
173
frinx-implemented-reader:
io.frinx.unitopo.unit.junos.acl.handler.AclInterfaceConfigReader
frinx-implemented-writer:
MISSING WRITER
frinx-device-type:
junos
frinx-supported-versions:
182
frinx-implemented-reader:
io.frinx.unitopo.unit.junos18.acl.handler.AclInterfaceConfigReader
nodetype: container (rw)
description:
User-defined identifier for the interface -- a common
convention could be '
nodetype: leaf (rw)
type: oc-if:interface-id
description:
Operational state for ACL per-interface data
nodetype: container (ro)
description:
User-defined identifier for the interface -- a common
convention could be '
nodetype: leaf (ro)
type: oc-if:interface-id
description:
Reference to an interface or subinterface
nodetype: container (rw)
description:
Configured reference to interface / subinterface
nodetype: container (rw)
description:
Reference to a base interface. If a reference to a
subinterface is required, this leaf must be specified
to indicate the base interface.
nodetype: leaf (rw)
type: leafref
description:
Reference to a subinterface -- this requires the base
interface to be specified using the interface leaf in
this container. If only a reference to a base interface
is requuired, this leaf should not be set.
nodetype: leaf (rw)
type: leafref
description:
Operational state for interface-ref
nodetype: container (ro)
description:
Reference to a base interface. If a reference to a
subinterface is required, this leaf must be specified
to indicate the base interface.
nodetype: leaf (ro)
type: leafref
description:
Reference to a subinterface -- this requires the base
interface to be specified using the interface leaf in
this container. If only a reference to a base interface
is requuired, this leaf should not be set.
nodetype: leaf (ro)
type: leafref
description:
Enclosing container the list of ingress ACLs on the
interface
frinx-device-type:
junos
frinx-supported-versions:
14any
frinx-device-type:
junos
frinx-supported-versions:
173
frinx-device-type:
junos
frinx-supported-versions:
182
nodetype: container (rw)
description:
List of ingress ACLs on the interface
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.unit.acl.handler.IngressAclSetReader
frinx-implemented-reader-details:
ALL_INGRESS_ACLS_LINE:
(?<type>.+) access-group (?<name>.+) ingress.*
SH_ACL_INTF:
show running-config interface %s
frinx-implemented-writer:
MISSING WRITER
frinx-device-type:
junos
frinx-supported-versions:
14any
frinx-implemented-reader:
io.frinx.cli.unit.junos.unit.acl.handler.IngressAclSetReader
frinx-implemented-reader-details:
IFACE_FILTER_LINE:
set interfaces (?<ifcname>\S+) unit (?<unit>\S+) family inet filter input (?<filter>\S+)
SH_IFACE_FILTERS:
show configuration interfaces %s unit %s family inet filter input | display set
frinx-device-type:
ios
frinx-supported-versions:
12any,15any
frinx-implemented-reader:
io.frinx.cli.unit.ios.unit.acl.handler.IngressAclSetReader
frinx-implemented-reader-details:
IPV4_INGRESS_ACLS_LINE:
\s*ip access-group (?<name>.+) in.*
IPV6_INGRESS_ACLS_LINE:
\s*ipv6 traffic-filter (?<name>.+) in.*
SH_ACL_INTF:
show running-config interface %s
frinx-implemented-writer:
MISSING WRITER
frinx-device-type:
junos
frinx-supported-versions:
173
frinx-implemented-reader:
io.frinx.unitopo.unit.junos.acl.handler.IngressAclSetReader
frinx-device-type:
junos
frinx-supported-versions:
182
frinx-implemented-reader:
io.frinx.unitopo.unit.junos18.acl.handler.IngressAclSetReader
nodetype: list (rw)
description:
Reference to set name list key
nodetype: leaf (list key) (rw)
type: leafref
description:
Reference to type list key
nodetype: leaf (list key) (rw)
type: leafref
description:
Configuration data
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.unit.acl.handler.IngressAclSetConfigReader
frinx-implemented-reader-details:
SH_ACL_INTF:
show running-config interface %s
frinx-implemented-writer:
io.frinx.cli.unit.iosxr.unit.acl.handler.IngressAclSetConfigWriter
frinx-device-type:
junos
frinx-supported-versions:
14any
frinx-implemented-reader:
io.frinx.cli.unit.junos.unit.acl.handler.IngressAclSetConfigReader
frinx-implemented-writer:
io.frinx.cli.unit.junos.unit.acl.handler.IngressAclSetConfigWriter
frinx-implemented-writer-details:
CREATE_TEMPLATE:
set interfaces %s unit %s family inet filter input %s
DELETE_TEMPLATE:
delete interfaces %s unit %s family inet filter input %s
frinx-device-type:
ios
frinx-supported-versions:
12any,15any
frinx-implemented-reader:
io.frinx.cli.unit.ios.unit.acl.handler.IngressAclSetConfigReader
frinx-implemented-writer:
io.frinx.cli.unit.ios.unit.acl.handler.IngressAclSetConfigWriter
frinx-device-type:
junos
frinx-supported-versions:
173
frinx-implemented-reader:
io.frinx.unitopo.unit.junos.acl.handler.IngressAclSetConfigReader
frinx-implemented-writer:
io.frinx.unitopo.unit.junos.acl.handler.IngressAclSetConfigWriter
frinx-device-type:
junos
frinx-supported-versions:
182
frinx-implemented-reader:
io.frinx.unitopo.unit.junos18.acl.handler.IngressAclSetConfigReader
frinx-implemented-writer:
io.frinx.unitopo.unit.junos18.acl.handler.IngressAclSetConfigWriter
nodetype: container (rw)
description:
Reference to the ACL set name applied on ingress
nodetype: leaf (rw)
type: string
description:
The type determines the fields allowed in the ACL entries
belonging to the ACL set (e.g., IPv4, IPv6, etc.)
nodetype: leaf (rw)
type: identityref
description:
Operational state data for interface ingress ACLs
nodetype: container (ro)
description:
Reference to the ACL set name applied on ingress
nodetype: leaf (ro)
type: string
description:
The type determines the fields allowed in the ACL entries
belonging to the ACL set (e.g., IPv4, IPv6, etc.)
nodetype: leaf (ro)
type: identityref
description:
Enclosing container for list of references to ACLs
nodetype: container (ro)
description:
List of ACL entries assigned to an interface
nodetype: list (ro)
list keys: [sequence-id]
description:
Reference to per-interface acl entry key
nodetype: leaf (list key) (ro)
type: leafref
description:
Operational state data for per-interface ACL entries
nodetype: container (ro)
description:
Reference to an entry in the ACL set applied to an
interface
nodetype: leaf (ro)
type: leafref
description:
Count of the number of packets matching the current ACL
entry.
An implementation should provide this counter on a
per-interface per-ACL-entry if possible.
If an implementation only supports ACL counters per entry
(i.e., not broken out per interface), then the value
should be equal to the aggregate count across all interfaces.
An implementation that provides counters per entry per
interface is not required to also provide an aggregate count,
e.g., per entry -- the user is expected to be able implement
the required aggregation if such a count is needed.
nodetype: leaf (ro)
type: oc-yang:counter64
description:
Count of the number of octets (bytes) matching the current
ACL entry.
An implementation should provide this counter on a
per-interface per-ACL-entry if possible.
If an implementation only supports ACL counters per entry
(i.e., not broken out per interface), then the value
should be equal to the aggregate count across all interfaces.
An implementation that provides counters per entry per
interface is not required to also provide an aggregate count,
e.g., per entry -- the user is expected to be able implement
the required aggregation if such a count is needed.
nodetype: leaf (ro)
type: oc-yang:counter64
description:
Enclosing container the list of egress ACLs on the
interface
frinx-device-type:
junos
frinx-supported-versions:
173
frinx-device-type:
junos
frinx-supported-versions:
182
nodetype: container (rw)
description:
List of egress ACLs on the interface
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.unit.acl.handler.EgressAclSetReader
frinx-implemented-reader-details:
ALL_EGRESS_ACLS_LINE:
(?<type>.+) access-group (?<name>.+) egress.*
SH_ACL_INTF:
show running-config interface %s
frinx-implemented-writer:
MISSING WRITER
frinx-device-type:
ios
frinx-supported-versions:
12any,15any
frinx-implemented-reader:
io.frinx.cli.unit.ios.unit.acl.handler.EgressAclSetReader
frinx-implemented-reader-details:
IPV4_EGRESS_ACLS_LINE:
\s*ip access-group (?<name>.+) out.*
IPV6_EGRESS_ACLS_LINE:
\s*ipv6 traffic-filter (?<name>.+) out.*
SH_ACL_INTF:
show running-config interface %s
frinx-implemented-writer:
MISSING WRITER
frinx-device-type:
junos
frinx-supported-versions:
173
frinx-implemented-reader:
io.frinx.unitopo.unit.junos.acl.handler.EgressAclSetReader
frinx-device-type:
junos
frinx-supported-versions:
182
frinx-implemented-reader:
io.frinx.unitopo.unit.junos18.acl.handler.EgressAclSetReader
nodetype: list (rw)
description:
Reference to set name list key
nodetype: leaf (list key) (rw)
type: leafref
description:
Reference to type list key
nodetype: leaf (list key) (rw)
type: leafref
description:
Configuration data
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.unit.acl.handler.EgressAclSetConfigReader
frinx-implemented-reader-details:
SH_ACL_INTF:
show running-config interface %s
frinx-implemented-writer:
io.frinx.cli.unit.iosxr.unit.acl.handler.EgressAclSetConfigWriter
frinx-device-type:
ios
frinx-supported-versions:
12any,15any
frinx-implemented-reader:
io.frinx.cli.unit.ios.unit.acl.handler.EgressAclSetConfigReader
frinx-implemented-writer:
io.frinx.cli.unit.ios.unit.acl.handler.EgressAclSetConfigWriter
frinx-device-type:
junos
frinx-supported-versions:
173
frinx-implemented-reader:
io.frinx.unitopo.unit.junos.acl.handler.EgressAclSetConfigReader
frinx-implemented-writer:
io.frinx.unitopo.unit.junos.acl.handler.EgressAclSetConfigWriter
frinx-device-type:
junos
frinx-supported-versions:
182
frinx-implemented-reader:
io.frinx.unitopo.unit.junos18.acl.handler.EgressAclSetConfigReader
frinx-implemented-writer:
io.frinx.unitopo.unit.junos18.acl.handler.EgressAclSetConfigWriter
nodetype: container (rw)
description:
Reference to the ACL set name applied on egress
nodetype: leaf (rw)
type: string
description:
The type determines the fields allowed in the ACL entries
belonging to the ACL set (e.g., IPv4, IPv6, etc.)
nodetype: leaf (rw)
type: identityref
description:
Operational state data for interface egress ACLs
nodetype: container (ro)
description:
Reference to the ACL set name applied on egress
nodetype: leaf (ro)
type: string
description:
The type determines the fields allowed in the ACL entries
belonging to the ACL set (e.g., IPv4, IPv6, etc.)
nodetype: leaf (ro)
type: identityref
description:
Enclosing container for list of references to ACLs
nodetype: container (ro)
description:
List of ACL entries assigned to an interface
nodetype: list (ro)
list keys: [sequence-id]
description:
Reference to per-interface acl entry key
nodetype: leaf (list key) (ro)
type: leafref
description:
Operational state data for per-interface ACL entries
nodetype: container (ro)
description:
Reference to an entry in the ACL set applied to an
interface
nodetype: leaf (ro)
type: leafref
description:
Count of the number of packets matching the current ACL
entry.
An implementation should provide this counter on a
per-interface per-ACL-entry if possible.
If an implementation only supports ACL counters per entry
(i.e., not broken out per interface), then the value
should be equal to the aggregate count across all interfaces.
An implementation that provides counters per entry per
interface is not required to also provide an aggregate count,
e.g., per entry -- the user is expected to be able implement
the required aggregation if such a count is needed.
nodetype: leaf (ro)
type: oc-yang:counter64
description:
Count of the number of octets (bytes) matching the current
ACL entry.
An implementation should provide this counter on a
per-interface per-ACL-entry if possible.
If an implementation only supports ACL counters per entry
(i.e., not broken out per interface), then the value
should be equal to the aggregate count across all interfaces.
An implementation that provides counters per entry per
interface is not required to also provide an aggregate count,
e.g., per entry -- the user is expected to be able implement
the required aggregation if such a count is needed.
nodetype: leaf (ro)
type: oc-yang:counter64
An OpenConfig model of Bi-Directional Forwarding Detection (BFD) configuration and operational state.
frinx-openconfig-extensions
frinx-openconfig-types
frinx-openconfig-interfaces
frinx-openconfig-inet-types
frinx-openconfig-network-instance
frinx-openconfig-policy-types
network-topology
frinx-uniconfig-topology
description:
Diagnostic codes defined by BFD. These typically indicate the
reason for a change of session state.
type: enumeration
description:
The state of the BFD session according to the system referred
to by the context of the leaf.
type: enumeration
description:
Configuration and operational state parameters for BFD.
nodetype: container (rw)
description:
Interfaces on which BFD sessions are to be enabled.
nodetype: container (rw)
description:
Per-interface configuration and state parameters for BFD.
nodetype: list (rw)
list keys: [id]
description:
A reference to an identifier for the interface on which
BFD is enabled.
nodetype: leaf (list key) (rw)
type: leafref
description:
Configuration parameters for BFD on the specified
interface.
nodetype: container (rw)
description:
A unique identifier for the interface.
nodetype: leaf (rw)
type: string
description:
When this leaf is set to true then the BFD session is enabled
on the specified interface - if it is set to false, it is
administratively disabled.
nodetype: leaf (rw)
type: boolean
description:
The source IP address to be used for BFD sessions over this
interface.
nodetype: leaf (rw)
type: oc-inet:ip-address
description:
The minimum interval between transmission of BFD control
packets that the operator desires. This value is advertised to
the peer, however the actual interval used is specified by
taking the maximum of desired-minimum-tx-interval and the
value of the remote required-minimum-receive interval value.
This value is specified as an integer number of microseconds.
nodetype: leaf (rw)
type: uint32
units: microseconds
description:
The minimum interval between received BFD control packets that
this system should support. This value is advertised to the
remote peer to indicate the maximum frequency (i.e., minimum
inter-packet interval) between BFD control packets that is
acceptable to the local system.
nodetype: leaf (rw)
type: uint32
units: microseconds
description:
The number of packets that must be missed to declare this
session as down. The detection interval for the BFD session
is calculated by multiplying the value of the negotiated
transmission interval by this value.
nodetype: leaf (rw)
type: uint16
description:
When this leaf is set to true - BFD will be enabled on
each member interface of the aggregated Ethernet bundle.
nodetype: leaf (rw)
type: boolean
description:
The IP address used by the remote system for this BFD session.
nodetype: leaf (rw)
type: oc-inet:ip-address
description:
Operational state parameters for BFD on the specified
interface.
nodetype: container (ro)
description:
A unique identifier for the interface.
nodetype: leaf (ro)
type: string
description:
When this leaf is set to true then the BFD session is enabled
on the specified interface - if it is set to false, it is
administratively disabled.
nodetype: leaf (ro)
type: boolean
description:
The source IP address to be used for BFD sessions over this
interface.
nodetype: leaf (ro)
type: oc-inet:ip-address
description:
The minimum interval between transmission of BFD control
packets that the operator desires. This value is advertised to
the peer, however the actual interval used is specified by
taking the maximum of desired-minimum-tx-interval and the
value of the remote required-minimum-receive interval value.
This value is specified as an integer number of microseconds.
nodetype: leaf (ro)
type: uint32
units: microseconds
description:
The minimum interval between received BFD control packets that
this system should support. This value is advertised to the
remote peer to indicate the maximum frequency (i.e., minimum
inter-packet interval) between BFD control packets that is
acceptable to the local system.
nodetype: leaf (ro)
type: uint32
units: microseconds
description:
The number of packets that must be missed to declare this
session as down. The detection interval for the BFD session
is calculated by multiplying the value of the negotiated
transmission interval by this value.
nodetype: leaf (ro)
type: uint16
description:
When this leaf is set to true - BFD will be enabled on
each member interface of the aggregated Ethernet bundle.
nodetype: leaf (ro)
type: boolean
description:
Reference to an interface or subinterface
nodetype: container (rw)
description:
Configured reference to interface / subinterface
nodetype: container (rw)
description:
Reference to a base interface. If a reference to a
subinterface is required, this leaf must be specified
to indicate the base interface.
nodetype: leaf (rw)
type: leafref
description:
Reference to a subinterface -- this requires the base
interface to be specified using the interface leaf in
this container. If only a reference to a base interface
is requuired, this leaf should not be set.
nodetype: leaf (rw)
type: leafref
description:
Operational state for interface-ref
nodetype: container (ro)
description:
Reference to a base interface. If a reference to a
subinterface is required, this leaf must be specified
to indicate the base interface.
nodetype: leaf (ro)
type: leafref
description:
Reference to a subinterface -- this requires the base
interface to be specified using the interface leaf in
this container. If only a reference to a base interface
is requuired, this leaf should not be set.
nodetype: leaf (ro)
type: leafref
description:
Parameters relating to micro-BFD sessions associated
with the interface.
nodetype: container (rw)
description:
This list contains configuration and state parameters
relating to micro-BFD session.
nodetype: list (rw)
list keys: [member-interface]
description:
A reference to the member interface of the link
aggregate.
nodetype: leaf (list key) (rw)
type: leafref
description:
Configuration parameters for the micro-BFD session.
nodetype: container (rw)
description:
The local IP address used by the system for the micro-BFD session
specified.
nodetype: leaf (rw)
type: oc-inet:ip-address
description:
The remote IP destination that should be used by the system for
the micro-BFD session specified.
nodetype: leaf (rw)
type: oc-inet:ip-address
description:
Reference to a member link of the aggregate interface being
described.
nodetype: leaf (rw)
type: leafref
description:
Operational state parameters for the micro-BFD session.
nodetype: container (ro)
description:
The local IP address used by the system for the micro-BFD session
specified.
nodetype: leaf (ro)
type: oc-inet:ip-address
description:
The remote IP destination that should be used by the system for
the micro-BFD session specified.
nodetype: leaf (ro)
type: oc-inet:ip-address
description:
Reference to a member link of the aggregate interface being
described.
nodetype: leaf (ro)
type: leafref
description:
The state of the BFD session perceived by the local system.
nodetype: leaf (ro)
type: bfd-session-state
description:
The reported state of the BFD session according to the remote
system. This state reflects the last state reported in a BFD
control packet.
nodetype: leaf (ro)
type: bfd-session-state
description:
The time of the last transition of the BFD session out of
the UP state, expressed as the number of nanoseconds since
the Unix epoch.
nodetype: leaf (ro)
type: oc-types:timeticks64
description:
The number of times that the BFD session has transitioned
out of the UP state.
nodetype: leaf (ro)
type: uint64
description:
A unique identifier used by the local system to identify this
BFD session.
nodetype: leaf (ro)
type: string
description:
A unique identified used by the remote system to identify this
BFD session.
nodetype: leaf (ro)
type: string
description:
The local BFD diagnostic code indicating the most recent
reason for failure of this BFD session.
nodetype: leaf (ro)
type: bfd-diagnostic-code
description:
The remote BFD diagnostic code indicating the remote system's
reason for failure of the BFD session
nodetype: leaf (ro)
type: bfd-diagnostic-code
description:
The value of the minimum receive interval that was specified
in the most recent BFD control packet received from the peer.
nodetype: leaf (ro)
type: uint32
description:
This leaf is set to true when the remote system has requested
demand mode be run for this session.
nodetype: leaf (ro)
type: boolean
description:
This leaf is set to true when the remote system has specified
that authentication is present for the BFD session.
nodetype: leaf (ro)
type: boolean
description:
This leaf is set to true when the remote system has specified
that the hardware implementing this BFD session is independent
of the control plane's liveliness.
nodetype: leaf (ro)
type: boolean
description:
Operational state parameters specifically relating to
asynchronous mode of BFD.
nodetype: container (ro)
description:
The date and time at which the last BFD packet
was transmitted for this session, expressed as the number
of nanoseconds since the Unix Epoch (January 1, 1970,
00:00 UTC).
nodetype: leaf (ro)
type: uint64
description:
The date and time at which the last BFD packet
was received for this session, expressed as the number
of nanoseconds since the Unix Epoch (January 1, 1970,
00:00 UTC).
nodetype: leaf (ro)
type: uint64
description:
The number of packets that have been transmitted
by the local system.
nodetype: leaf (ro)
type: uint64
description:
The number of packets that have been received by the
local system from the remote neighbour.
nodetype: leaf (ro)
type: uint64
description:
The number of times that the adjacency with the neighbor
has transitioned into the up state.
nodetype: leaf (ro)
type: uint64
description:
Parameters relating to the BFD peers which are seen
over this interface.
nodetype: container (rw)
description:
Parameters relating to the BFD peer specified by the
remote address.
nodetype: list (ro)
list keys: [local-discriminator]
description:
The local discriminator, which is unique for the
session on the system.
nodetype: leaf (list key) (ro)
type: leafref
description:
Operational state parameters for the BFD session.
nodetype: container (ro)
description:
The IP address used by the local system for this BFD session.
nodetype: leaf (ro)
type: oc-inet:ip-address
description:
The IP address used by the remote system for this BFD session.
nodetype: leaf (ro)
type: oc-inet:ip-address
description:
Indicates the set of protocols that currently use
this BFD session for liveliness detection.
nodetype: leaf-list (ro)
type: identityref
description:
The state of the BFD session perceived by the local system.
nodetype: leaf (ro)
type: bfd-session-state
description:
The reported state of the BFD session according to the remote
system. This state reflects the last state reported in a BFD
control packet.
nodetype: leaf (ro)
type: bfd-session-state
description:
The time of the last transition of the BFD session out of
the UP state, expressed as the number of nanoseconds since
the Unix epoch.
nodetype: leaf (ro)
type: oc-types:timeticks64
description:
The number of times that the BFD session has transitioned
out of the UP state.
nodetype: leaf (ro)
type: uint64
description:
A unique identifier used by the local system to identify this
BFD session.
nodetype: leaf (ro)
type: string
description:
A unique identified used by the remote system to identify this
BFD session.
nodetype: leaf (ro)
type: string
description:
The local BFD diagnostic code indicating the most recent
reason for failure of this BFD session.
nodetype: leaf (ro)
type: bfd-diagnostic-code
description:
The remote BFD diagnostic code indicating the remote system's
reason for failure of the BFD session
nodetype: leaf (ro)
type: bfd-diagnostic-code
description:
The value of the minimum receive interval that was specified
in the most recent BFD control packet received from the peer.
nodetype: leaf (ro)
type: uint32
description:
This leaf is set to true when the remote system has requested
demand mode be run for this session.
nodetype: leaf (ro)
type: boolean
description:
This leaf is set to true when the remote system has specified
that authentication is present for the BFD session.
nodetype: leaf (ro)
type: boolean
description:
This leaf is set to true when the remote system has specified
that the hardware implementing this BFD session is independent
of the control plane's liveliness.
nodetype: leaf (ro)
type: boolean
description:
Operational state parameters specifically relating to the
echo mode of BFD.
nodetype: container (ro)
description:
This leaf is set to true when echo mode is running between
the local and remote system. When it is set to false, solely
asynchronous mode is active.
nodetype: leaf (ro)
type: boolean
description:
The date and time at which the last BFD packet
was transmitted for this session, expressed as the number
of nanoseconds since the Unix Epoch (January 1, 1970,
00:00 UTC).
nodetype: leaf (ro)
type: uint64
description:
The date and time at which the last BFD packet
was received for this session, expressed as the number
of nanoseconds since the Unix Epoch (January 1, 1970,
00:00 UTC).
nodetype: leaf (ro)
type: uint64
description:
The number of packets that have been transmitted
by the local system.
nodetype: leaf (ro)
type: uint64
description:
The number of packets that have been received by the
local system from the remote neighbour.
nodetype: leaf (ro)
type: uint64
description:
The number of times that the adjacency with the neighbor
has transitioned into the up state.
nodetype: leaf (ro)
type: uint64
description:
Operational state parameters specifically relating to
asynchronous mode of BFD.
nodetype: container (ro)
description:
The date and time at which the last BFD packet
was transmitted for this session, expressed as the number
of nanoseconds since the Unix Epoch (January 1, 1970,
00:00 UTC).
nodetype: leaf (ro)
type: uint64
description:
The date and time at which the last BFD packet
was received for this session, expressed as the number
of nanoseconds since the Unix Epoch (January 1, 1970,
00:00 UTC).
nodetype: leaf (ro)
type: uint64
description:
The number of packets that have been transmitted
by the local system.
nodetype: leaf (ro)
type: uint64
description:
The number of packets that have been received by the
local system from the remote neighbour.
nodetype: leaf (ro)
type: uint64
description:
The number of times that the adjacency with the neighbor
has transitioned into the up state.
nodetype: leaf (ro)
type: uint64
This sub-module contains groupings that are specific to the peer-group context of the OpenConfig BGP module.
frinx-openconfig-extensions
frinx-openconfig-routing-policy
This module contains data definitions for BGP routing policy. It augments the base routing-policy module with BGP-specific options for conditions and actions.
frinx-openconfig-inet-types
frinx-openconfig-routing-policy
frinx-openconfig-policy-types
frinx-openconfig-bgp-types
frinx-openconfig-extensions
network-topology
frinx-uniconfig-topology
description:
type definition for specifying next-hop in policy actions
type: union
type: oc-inet:ip-address
type: enumeration
description:
Type definition for options when setting the community
attribute in a policy action
type: enumeration
description:
Type definition for specifying how the BGP MED can
be set in BGP policy actions. The three choices are to set
the MED directly, increment/decrement using +/- notation,
and setting it to the IGP cost (predefined value).
type: union
type: string
type: uint32
type: enumeration
This module contains general data definitions for use in BGP policy. It can be imported by modules that make use of BGP attributes
frinx-openconfig-types
frinx-openconfig-inet-types
frinx-openconfig-extensions
description:
Type definition for extended community attributes. In the case that
common communities are utilised, they are represented as a string
of the form:
- <2b AS>:<4b value> per RFC4360 section 3.1
- <4b IPv4>:<2b value> per RFC4360 section 3.2
- <4b AS>:<2b value> per RFC5668 section 2.
- route-target:<2b AS>:<4b value> per RFC4360 section 4
- route-target:<4b IPv4>:<2b value> per RFC4360 section 4
- route-origin:<2b ASN>:<4b value> per RFC4360 section 5
- route-origin:<4b IPv4>:<2b value> per RFC4360 section 5
type: union
type: string
type: string
type: string
type: string
type: string
type: string
type: string
type: string
type: string
description:
Defines the types of BGP AS path segments.
type: enumeration
description:
Set of options for configuring how private AS path numbers
are removed from advertisements
type: identityref
description:
Type definition for communities specified as regular
expression patterns
type: oc-types:std-regexp
description:
type describing variations of community attributes:
STANDARD: standard BGP community [rfc1997]
EXTENDED: extended BGP community [rfc4360]
BOTH: both standard and extended community
type: enumeration
description:
Union type for route reflector cluster ids:
option 1: 4-byte number
option 2: IP address
type: union
type: uint32
type: oc-inet:ipv4-address
description:
A type definition utilised to define the extended community in a
context where the system is receiving the extended community from
an external source, such that the value may be unknown. In the case
that the received extended community is unknown it is defined to be
a 8-octet quantity formatted according to RFC4360:
Type Field: 1 or 2 octets.
Value Field: Remaining octets.
The high-order octet of the type field is encoded such that bit 0
indicates whether the extended community type is IANA assigned;
and bit 1 indicates whether the extended community is transitive.
The remaining bits of the high-order type field must be interpreted
to determine whether the low-order type field should be parsed,
or whether the entire remainder of the extended community is a
value.
type: union
type: bgp-ext-community-type
type: binary
description:
Type definition for standard commmunity attributes represented as
a integer value, or a string of the form N:M where N and M are
integers between 0 and 65535.
type: union
type: uint32
type: string
description:
Labels a peer or peer group as explicitly internal or
external
type: enumeration
description:
Type to describe the direction of NLRI transmission
type: enumeration
description:
Type definition for well-known IETF community attribute
values
type: identityref
description:
Type definition for standard BGP origin attribute
type: enumeration
description:
Reserved communities within the standard community space
defined by RFC1997. These communities must fall within the
range 0x00000000 to 0xFFFFFFFF
description:
An autonomous system receiving NLRI tagged with this community
is advised not to readvertise the NLRI to external bi-lateral
peer autonomous systems. An AS may also filter received NLRI
from bilateral peer sessions when they are tagged with this
community value
base identity: BGP_WELL_KNOWN_STD_COMMUNITY
description:
All NLRI received carrying this community must not be
advertised to external BGP peers - including over confederation
sub-AS boundaries. This community has a value of 0xFFFFFF03.
base identity: BGP_WELL_KNOWN_STD_COMMUNITY
description:
Do not export NLRI received carrying this community outside
the bounds of this autonomous system, or this confederation if
the local autonomous system is a confederation member AS. This
community has a value of 0xFFFFFF01.
base identity: BGP_WELL_KNOWN_STD_COMMUNITY
description:
All NLRI received carrying this community must not be
advertised to other BGP peers. This community has a value of
0xFFFFFF02.
base identity: BGP_WELL_KNOWN_STD_COMMUNITY
description:
Base identity for a BGP capability
description:
BGP add-paths
base identity: BGP_CAPABILITY
description:
The BGP route-refresh functionality
base identity: BGP_CAPABILITY
description:
Multi-protocol extensions to BGP
base identity: BGP_CAPABILITY
description:
4-byte (32-bit) AS number functionality
base identity: BGP_CAPABILITY
description:
Graceful restart functionality
base identity: BGP_CAPABILITY
description:
Base identity for options for removing private autonomous
system numbers from the AS_PATH attribute
description:
Strip all private autonmous system numbers from the AS_PATH.
This action is performed regardless of the other content of the
AS_PATH attribute, and for all instances of private AS numbers
within that attribute.
base identity: REMOVE_PRIVATE_AS_OPTION
description:
Replace all instances of private autonomous system numbers in
the AS_PATH with the local BGP speaker's autonomous system
number. This action is performed regardless of the other
content of the AS_PATH attribute, and for all instances of
private AS number within that attribute.
base identity: REMOVE_PRIVATE_AS_OPTION
description:
Base identity type for AFI,SAFI tuples for BGP-4
description:
Multicast IPv6 MPLS L3VPN (AFI,SAFI = 2,129)
base identity: AFI_SAFI_TYPE
description:
Unicast IPv4 MPLS L3VPN (AFI,SAFI = 1,128)
base identity: AFI_SAFI_TYPE
description:
Multicast IPv4 MPLS L3VPN (AFI,SAFI = 1,129)
base identity: AFI_SAFI_TYPE
description:
IPv6 unicast (AFI,SAFI = 2,1)
base identity: AFI_SAFI_TYPE
description:
Labeled IPv4 unicast (AFI,SAFI = 1,4)
base identity: AFI_SAFI_TYPE
description:
Labeled IPv6 unicast (AFI,SAFI = 2,4)
base identity: AFI_SAFI_TYPE
description:
BGP MPLS Based Ethernet VPN (AFI,SAFI = 25,70)
base identity: AFI_SAFI_TYPE
description:
BGP-signalled VPLS (AFI,SAFI = 25,65)
base identity: AFI_SAFI_TYPE
description:
IPv4 unicast (AFI,SAFI = 1,1)
base identity: AFI_SAFI_TYPE
description:
Unicast IPv6 MPLS L3VPN (AFI,SAFI = 2,128)
base identity: AFI_SAFI_TYPE
This module provides extensions to the YANG language to allow OpenConfig specific functionality and meta-data to be defined.
Model for managing aggregated (aka bundle, LAG) interfaces.
frinx-openconfig-interfaces
frinx-openconfig-if-ethernet
iana-if-type
frinx-openconfig-extensions
network-topology
frinx-uniconfig-topology
description:
Type to define the lag-type, i.e., how the LAG is
defined and managed
type: enumeration
Model for managing Ethernet interfaces -- augments the IETF YANG model for interfaces described by RFC 7223
frinx-openconfig-interfaces
iana-if-type
ietf-yang-types
frinx-openconfig-extensions
network-topology
frinx-uniconfig-topology
description:
base type to specify available Ethernet link
speeds
description:
100 GBps Ethernet
base identity: ETHERNET_SPEED
description:
25 GBps Ethernet
base identity: ETHERNET_SPEED
description:
1 GBps Ethernet
base identity: ETHERNET_SPEED
description:
10 GBps Ethernet
base identity: ETHERNET_SPEED
description:
10 Mbps Ethernet
base identity: ETHERNET_SPEED
description:
40 GBps Ethernet
base identity: ETHERNET_SPEED
description:
Interface speed is unknown. Systems may report
speed UNKNOWN when an interface is down or unpopuplated (e.g.,
pluggable not present).
base identity: ETHERNET_SPEED
description:
50 GBps Ethernet
base identity: ETHERNET_SPEED
description:
100 Mbps Ethernet
base identity: ETHERNET_SPEED
Model for managing IP interfaces.
This model reuses most of the IETF YANG model for IP management described by RFC 7277. The primary differences are in the structure of configuration and state data.
ietf-inet-types
frinx-openconfig-interfaces
frinx-openconfig-vlan
ietf-yang-types
frinx-openconfig-extensions
network-topology
frinx-uniconfig-topology
description:
The origin of a neighbor entry.
type: enumeration
description:
The origin of an address.
type: enumeration
This module adds extensions to the base IP configuration and operational state model to support additional use cases.
frinx-openconfig-interfaces
frinx-openconfig-if-ip
frinx-openconfig-extensions
network-topology
frinx-uniconfig-topology
This module contains a set of Internet address related types for use in OpenConfig modules.
Portions of this code were derived from IETF RFC 6021. Please reproduce this note if possible.
IETF code is subject to the following copyright and license: Copyright (c) IETF Trust and the persons identified as authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust’s Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info).
frinx-openconfig-extensions
description:
An IPv4 prefix represented in dotted quad notation followed by
a slash and a CIDR mask (0 <= mask <= 32).
type: string
description:
An IPv6 prefix represented in full, shortened, or mixed
shortened format followed by a slash and CIDR mask (0 <= mask <=
128).
type: string
description:
An ASCII-encoded Uniform Resource Locator (URL) as defined
in RFC 3986, section 1.1.3
type: string
description:
An IPv4 or IPv6 prefix.
type: union
type: ipv4-prefix
type: ipv6-prefix
description:
A numeric identifier for an autonomous system (AS). An AS is a
single domain, under common administrative control, which forms
a unit of routing policy. Autonomous systems can be assigned a
2-byte identifier, or a 4-byte identifier which may have public
or private scope. Private ASNs are assigned from dedicated
ranges. Public ASNs are assigned from ranges allocated by IANA
to the regional internet registries (RIRs).
type: uint32
description:
An ASCII-encoded Uniform Resource Identifier (URI) as defined
in RFC 3986.
type: string
description:
A 16-bit port number used by a transport protocol such as TCP
or UDP.
type: uint16
description:
A differentiated services code point (DSCP) marking within the
IP header.
type: uint8
description:
An IPv4 or IPv6 address with no prefix specified.
type: union
type: ipv4-address
type: ipv6-address
description:
An IPv6 address represented as either a full address; shortened
or mixed-shortened formats.
type: string
description:
An IPv4 address in dotted quad notation.
type: string
description:
The IPv6 flow-label is a 20-bit value within the IPv6 header
which is optionally used by the source of the IPv6 packet to
label sets of packets for which special handling may be
required.
type: uint32
Model for managing network interfaces and subinterfaces. This module also defines convenience types / groupings for other models to create references to interfaces:
base-interface-ref (type) - reference to a base interface interface-ref (grouping) - container for reference to a interface + subinterface interface-ref-state (grouping) - container for read-only (opstate) reference to interface + subinterface
This model reuses data items defined in the IETF YANG model for interfaces described by RFC 7223 with an alternate structure (particularly for operational state data) and and with additional configuration items.
ietf-interfaces
ietf-yang-types
frinx-openconfig-extensions
network-topology
frinx-uniconfig-topology
yang-ext
description:
User-defined identifier for an interface, generally used to
name a interface reference. The id can be arbitrary but a
useful convention is to use a combination of base interface
name and subinterface index.
type: string
description:
Reusable type for by-name reference to a base interface.
This type may be used in cases where ability to reference
a subinterface is not required.
type: leafref
description:
Top level container for interfaces, including configuration
and state data.
nodetype: container (rw)
description:
The list of named interfaces on the device.
frinx-device-type:
ironware
frinx-supported-versions:
any
frinx-implemented-reader:
io.frinx.cli.unit.brocade.ifc.handler.InterfaceReader
frinx-implemented-reader-details:
IFC_CFG_LINE:
interface (?<id>.+)[.\s]*
IFC_OPER_LINE:
^(?<id>\d+/\d+)\s+.*
SH_INTERFACE:
show running-config interface | include interface
SH_OPER_INTERFACES:
show interface brief
frinx-implemented-writer:
MISSING WRITER
frinx-device-type:
vrp
frinx-supported-versions:
any
frinx-implemented-reader:
io.frinx.cli.unit.huawei.ifc.handler.InterfaceReader
frinx-implemented-reader-details:
INTERFACE_ID_LINE:
(?<id>[^\s^(]+)(\(10G\))*\s+(?<ipAddr>[^\s]+)\s+(?<status>[^\s]+)\s+(?<protocol>[^\s]+)\s+(?<vpn>[^\s]+)\s*
SH_INTERFACE:
display ip interface brief
SUBINTERFACE_NAME:
(?<ifcId>.+)[.](?<subifcIndex>[0-9]+)
frinx-device-type:
junos
frinx-supported-versions:
182
frinx-implemented-reader:
io.frinx.unitopo.unit.junos18.interfaces.handler.InterfaceReader
frinx-device-type:
xr
frinx-supported-versions:
interface
frinx-implemented-reader:
io.frinx.unitopo.unit.xr66.interfaces.handler.InterfaceReader
frinx-device-type:
ios
frinx-supported-versions:
12any,15any
frinx-implemented-reader:
io.frinx.cli.unit.ios.ifc.handler.InterfaceReader
frinx-implemented-reader-details:
INTERFACE_ID_LINE:
interface (?<id>\S+)
SH_INTERFACE:
show running-config | include ^interface
SUBINTERFACE_NAME:
(?<ifcId>.+)[.](?<subifcIndex>[0-9]+)
frinx-implemented-writer:
MISSING WRITER
frinx-device-type:
junos
frinx-supported-versions:
14any
frinx-implemented-reader:
io.frinx.cli.unit.junos.ifc.handler.InterfaceReader
frinx-implemented-reader-details:
INTERFACE_ID_LINE:
set interfaces (?<id>[\S]+) .*
SHOW_INTERFACES:
show configuration interfaces | display set
SUBINTERFACE_ID_LINE:
set interfaces (?<id>[\S]+ unit [0-9]+).*
SUBINTERFACE_NAME:
(?<ifcId>[\S]+) unit (?<subifcIndex>[0-9]+)
frinx-implemented-writer:
MISSING WRITER
frinx-device-type:
nos
frinx-supported-versions:
any
frinx-implemented-reader:
io.frinx.cli.unit.dasan.ifc.handler.InterfaceReader
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.ifc.handler.InterfaceReader
frinx-implemented-reader-details:
INTERFACE_ID_LINE:
interface (?<id>[\S]+)
SH_RUN_INTERFACE:
show running-config interface | include ^interface
SUBINTERFACE_NAME:
(?<ifcId>.+)[.](?<subifcIndex>[0-9]+)
frinx-implemented-writer:
MISSING WRITER
frinx-device-type:
junos
frinx-supported-versions:
173
frinx-implemented-reader:
io.frinx.unitopo.unit.junos.interfaces.handler.InterfaceReader
frinx-implemented-writer:
io.frinx.unitopo.unit.junos.interfaces.handler.InterfaceWriter
frinx-device-type:
nexus
frinx-supported-versions:
any
frinx-implemented-reader:
io.frinx.cli.unit.nexus.ifc.handler.InterfaceReader
frinx-implemented-reader-details:
INTERFACE_ID_LINE:
interface (?<id>[\S]+)
SH_RUN_INTERFACE:
show running-config interface | include ^interface
SUBINTERFACE_NAME:
(?<ifcId>.+)[.](?<subifcIndex>[0-9]+)
frinx-implemented-writer:
MISSING WRITER
nodetype: list (rw)
list keys: [name]
description:
References the configured name of the interface
nodetype: leaf (list key) (rw)
type: leafref
description:
Configurable items at the global, physical interface
level
frinx-device-type:
ironware
frinx-supported-versions:
any
frinx-implemented-reader:
io.frinx.cli.unit.brocade.ifc.handler.InterfaceConfigReader
frinx-implemented-reader-details:
DESCR_LINE:
\s*port-name (?<desc>.+)
MTU_LINE:
\s*mtu (?<mtu>.+)$
PRIORITY_FORCE_LINE:
\s*priority force
PRIORITY_LINE:
\s*priority (?<priority>[0-7]{1})
SHUTDOWN_LINE:
enable
SH_SINGLE_INTERFACE_CFG:
show running-config interface {$ifcType} {$ifcNumber}
frinx-implemented-writer:
io.frinx.cli.unit.brocade.ifc.handler.InterfaceConfigWriter
frinx-implemented-writer-details:
DELETE_TEMPLATE:
configure terminal
no interface {$data.name}
end
PRIORITY_TEMPLATE:
{$priority|update(priority,priority `$priority.priority`
,priority 0
)}{% if ($update) %}{% if (!$forced) %}no {% endif %}priority force
{% endif %}
WRITE_TEMPLATE:
configure terminal
interface {$data.name}
{$data|update(mtu,mtu `$data.mtu`
,no mtu
)}{$data|update(description,port-name `$data.description`
,no port-name
)}{% if ($enabled) %}enable
{% else %}disable
{% endif %}{$priority}end
frinx-device-type:
vrp
frinx-supported-versions:
any
frinx-implemented-reader:
io.frinx.cli.unit.huawei.ifc.handler.InterfaceConfigReader
frinx-implemented-reader-details:
DESCR_LINE:
\s*description (?<desc>.+)\s*
MTU_LINE:
\s*mtu (?<mtu>.+)\s*
SHUTDOWN_LINE:
undo shutdown
SH_SINGLE_INTERFACE_CFG:
display current-configuration interface %s
frinx-implemented-writer:
io.frinx.cli.unit.huawei.ifc.handler.InterfaceConfigWriter
frinx-implemented-writer-details:
DELETE_TEMPLATE:
system-view
undo interface ${data.name}
commit
return
WRITE_TEMPLATE:
system-view
interface ${data.name}
{$data|update(mtu,mtu `$data.mtu`
,undo mtu
)}{$data|update(description,description `$data.description`
,undo description
)}{% if ($enabled) %}no shutdown
{% else %}shutdown
{% endif %}commit
return
frinx-device-type:
junos
frinx-supported-versions:
182
frinx-implemented-reader:
io.frinx.unitopo.unit.junos18.interfaces.handler.InterfaceConfigReader
frinx-implemented-writer:
io.frinx.unitopo.unit.junos18.interfaces.handler.InterfaceConfigWriter
frinx-device-type:
xr
frinx-supported-versions:
interface
frinx-implemented-reader:
io.frinx.unitopo.unit.xr66.interfaces.handler.InterfaceConfigReader
frinx-implemented-writer:
io.frinx.unitopo.unit.xr66.interfaces.handler.InterfaceConfigWriter
frinx-device-type:
ios
frinx-supported-versions:
12any,15any
frinx-implemented-reader:
io.frinx.cli.unit.ios.ifc.handler.InterfaceConfigReader
frinx-implemented-reader-details:
DESCR_LINE:
\s*description (?<desc>.+)
MTU_LINE:
\s*mtu (?<mtu>.+)$
SHUTDOWN_LINE:
shutdown
SH_SINGLE_INTERFACE_CFG:
show running-config interface %s
frinx-implemented-writer:
io.frinx.cli.unit.ios.ifc.handler.InterfaceConfigWriter
frinx-implemented-writer-details:
DELETE_TEMPLATE:
configure terminal
no interface {$data.name}
end
WRITE_TEMPLATE:
configure terminal
interface {$data.name}
{$data|update(mtu,mtu `$data.mtu`
,no mtu
)}{$data|update(description,description `$data.description`
,no description
)}{% if ($enabled) %}no shutdown
{% else %}shutdown
{% endif %}end
frinx-device-type:
junos
frinx-supported-versions:
14any
frinx-implemented-reader:
io.frinx.cli.unit.junos.ifc.handler.InterfaceConfigReader
frinx-implemented-reader-details:
DESCRIPTION_LINE:
set interfaces (?<id>\S+) description (?<desc>.*)
SHUTDOWN_LINE:
set interfaces (?<id>\S+) disable
SH_SINGLE_INTERFACE_CFG:
show configuration interfaces %s | display set
frinx-implemented-writer:
io.frinx.cli.unit.junos.ifc.handler.InterfaceConfigWriter
frinx-implemented-writer-details:
DELETE_TEMPLATE:
delete interfaces {$data.name}
WRITE_TEMPLATE:
edit interfaces {$data.name}
{$data|update(description,set description `$data.description`
,delete description
)}{% if ($enabled == TRUE) %}delete disable
{% elseIf ($enabled == FALSE) %}set disable
{% endif %}exit
frinx-device-type:
nos
frinx-supported-versions:
any
frinx-implemented-reader:
io.frinx.cli.unit.dasan.ifc.handler.InterfaceConfigReader
frinx-implemented-writer:
io.frinx.cli.unit.dasan.ifc.handler.InterfaceConfigWriter
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.ifc.handler.InterfaceConfigReader
frinx-implemented-reader-details:
DESCR_LINE:
\s*description (?<desc>.+)
MTU_LINE:
\s*mtu (?<mtu>.+)$
SHUTDOWN_LINE:
shutdown
SH_SINGLE_INTERFACE_CFG:
show running-config interface %s
frinx-implemented-writer:
io.frinx.cli.unit.iosxr.ifc.handler.InterfaceConfigWriter
frinx-implemented-writer-details:
DELETE_TEMPLATE:
no interface {$data.name}
WRITE_TEMPLATE:
interface {$data.name}
{$data|update(mtu,mtu `$data.mtu`
,no mtu
)}{$data|update(description,description `$data.description`
,no description
)}{% if ($enabled) %}no shutdown
{% else %}shutdown
{% endif %}root
frinx-device-type:
junos
frinx-supported-versions:
173
frinx-implemented-reader:
io.frinx.unitopo.unit.junos.interfaces.handler.InterfaceConfigReader
frinx-implemented-writer:
io.frinx.unitopo.unit.junos.interfaces.handler.InterfaceConfigWriter
frinx-device-type:
nexus
frinx-supported-versions:
any
frinx-implemented-reader:
io.frinx.cli.unit.nexus.ifc.handler.InterfaceConfigReader
frinx-implemented-reader-details:
DESCR_LINE:
\s*description (?<desc>.+)
MTU_LINE:
\s*mtu (?<mtu>.+)$
SHUTDOWN_LINE:
shutdown
SH_SINGLE_INTERFACE_CFG:
show running-config interface %s
frinx-implemented-writer:
io.frinx.cli.unit.nexus.ifc.handler.InterfaceConfigWriter
frinx-implemented-writer-details:
DELETE_TEMPLATE:
no interface {$data.name}
WRITE_TEMPLATE:
interface {$data.name}
{$data|update(mtu,mtu `$data.mtu`
,no mtu
)}{$data|update(description,description `$data.description`
,no description
)}{% if ($enabled) %}no shutdown
{% else %}shutdown
{% endif %}root
nodetype: container (rw)
description:
[adapted from IETF interfaces model (RFC 7223)]
The type of the interface.
When an interface entry is created, a server MAY
initialize the type leaf with a valid value, e.g., if it
is possible to derive the type from the name of the
interface.
If a client tries to set the type of an interface to a
value that can never be used by the system, e.g., if the
type is not supported or if the type does not match the
name of the interface, the server MUST reject the request.
A NETCONF server MUST reply with an rpc-error with the
error-tag 'invalid-value' in this case.
nodetype: leaf (rw)
type: identityref
description:
Set the max transmission unit size in octets
for the physical interface. If this is not set, the mtu is
set to the operational default -- e.g., 1514 bytes on an
Ethernet interface.
nodetype: leaf (rw)
type: uint16
description:
[adapted from IETF interfaces model (RFC 7223)]
The name of the interface.
A device MAY restrict the allowed values for this leaf,
possibly depending on the type of the interface.
For system-controlled interfaces, this leaf is the
device-specific name of the interface. The 'config false'
list interfaces/interface[name]/state contains the currently
existing interfaces on the device.
If a client tries to create configuration for a
system-controlled interface that is not present in the
corresponding state list, the server MAY reject
the request if the implementation does not support
pre-provisioning of interfaces or if the name refers to
an interface that can never exist in the system. A
NETCONF server MUST reply with an rpc-error with the
error-tag 'invalid-value' in this case.
The IETF model in RFC 7223 provides YANG features for the
following (i.e., pre-provisioning and arbitrary-names),
however they are omitted here:
If the device supports pre-provisioning of interface
configuration, the 'pre-provisioning' feature is
advertised.
If the device allows arbitrarily named user-controlled
interfaces, the 'arbitrary-names' feature is advertised.
When a configured user-controlled interface is created by
the system, it is instantiated with the same name in the
/interfaces/interface[name]/state list.
nodetype: leaf (rw)
type: string
description:
[adapted from IETF interfaces model (RFC 7223)]
A textual description of the interface.
A server implementation MAY map this leaf to the ifAlias
MIB object. Such an implementation needs to use some
mechanism to handle the differences in size and characters
allowed between this leaf and ifAlias. The definition of
such a mechanism is outside the scope of this document.
Since ifAlias is defined to be stored in non-volatile
storage, the MIB implementation MUST map ifAlias to the
value of 'description' in the persistently stored
datastore.
Specifically, if the device supports ':startup', when
ifAlias is read the device MUST return the value of
'description' in the 'startup' datastore, and when it is
written, it MUST be written to the 'running' and 'startup'
datastores. Note that it is up to the implementation to
decide whether to modify this single leaf in 'startup' or
perform an implicit copy-config from 'running' to
'startup'.
If the device does not support ':startup', ifAlias MUST
be mapped to the 'description' leaf in the 'running'
datastore.
nodetype: leaf (rw)
type: string
description:
[adapted from IETF interfaces model (RFC 7223)]
This leaf contains the configured, desired state of the
interface.
Systems that implement the IF-MIB use the value of this
leaf in the 'running' datastore to set
IF-MIB.ifAdminStatus to 'up' or 'down' after an ifEntry
has been initialized, as described in RFC 2863.
Changes in this leaf in the 'running' datastore are
reflected in ifAdminStatus, but if ifAdminStatus is
changed over SNMP, this leaf is not affected.
nodetype: leaf (rw)
type: boolean
description:
Optionally set the tag protocol identifier field (TPID) that
is accepted on the VLAN
nodetype: leaf (rw)
type: identityref
description:
The priority index
nodetype: leaf (rw)
type: uint8
description:
This forces the configured priority when
determining the priority relative to other priority values of incoming packets.
nodetype: leaf (rw)
type: boolean
description:
Operational state data at the global interface level
frinx-device-type:
ios
frinx-supported-versions:
12any,15any
frinx-implemented-reader:
io.frinx.cli.unit.ios.ifc.handler.InterfaceStateReader
frinx-implemented-reader-details:
DESCR_LINE:
\s*Description: (?<desc>.+)
MTU_LINE:
\s*MTU (?<mtu>.+) bytes.*$
SH_SINGLE_INTERFACE:
show interface %s
STATUS_LINE:
(?<id>.+)[.\s]* (?<admin>up|down).*, line protocol is (?<oper>up|down).*
frinx-implemented-writer:
MISSING WRITER
frinx-device-type:
vrp
frinx-supported-versions:
any
frinx-implemented-reader:
io.frinx.cli.unit.huawei.ifc.handler.InterfaceStateReader
frinx-implemented-reader-details:
ADMIN_STATUS_LINE:
(?<id>\S+) current state : (?<admin>UP|DOWN).*
DESCR_LINE:
\s*Description: (?<desc>.+)\s*
DISPLAY_SINGLE_INTERFACE:
display inter %s
MTU_LINE:
.*The Maximum Transmit Unit is (?<mtu>.+).*$
OPER_STATUS_LINE:
\s*Line protocol current state : (?<oper>UP|DOWN).*
frinx-implemented-writer:
MISSING WRITER
frinx-device-type:
nos
frinx-supported-versions:
any
frinx-implemented-reader:
io.frinx.cli.unit.dasan.ifc.handler.InterfaceStateReader
frinx-implemented-writer:
MISSING WRITER
nodetype: container (ro)
description:
[adapted from IETF interfaces model (RFC 7223)]
The type of the interface.
When an interface entry is created, a server MAY
initialize the type leaf with a valid value, e.g., if it
is possible to derive the type from the name of the
interface.
If a client tries to set the type of an interface to a
value that can never be used by the system, e.g., if the
type is not supported or if the type does not match the
name of the interface, the server MUST reject the request.
A NETCONF server MUST reply with an rpc-error with the
error-tag 'invalid-value' in this case.
nodetype: leaf (ro)
type: identityref
description:
Set the max transmission unit size in octets
for the physical interface. If this is not set, the mtu is
set to the operational default -- e.g., 1514 bytes on an
Ethernet interface.
nodetype: leaf (ro)
type: uint16
description:
[adapted from IETF interfaces model (RFC 7223)]
The name of the interface.
A device MAY restrict the allowed values for this leaf,
possibly depending on the type of the interface.
For system-controlled interfaces, this leaf is the
device-specific name of the interface. The 'config false'
list interfaces/interface[name]/state contains the currently
existing interfaces on the device.
If a client tries to create configuration for a
system-controlled interface that is not present in the
corresponding state list, the server MAY reject
the request if the implementation does not support
pre-provisioning of interfaces or if the name refers to
an interface that can never exist in the system. A
NETCONF server MUST reply with an rpc-error with the
error-tag 'invalid-value' in this case.
The IETF model in RFC 7223 provides YANG features for the
following (i.e., pre-provisioning and arbitrary-names),
however they are omitted here:
If the device supports pre-provisioning of interface
configuration, the 'pre-provisioning' feature is
advertised.
If the device allows arbitrarily named user-controlled
interfaces, the 'arbitrary-names' feature is advertised.
When a configured user-controlled interface is created by
the system, it is instantiated with the same name in the
/interfaces/interface[name]/state list.
nodetype: leaf (ro)
type: string
description:
[adapted from IETF interfaces model (RFC 7223)]
A textual description of the interface.
A server implementation MAY map this leaf to the ifAlias
MIB object. Such an implementation needs to use some
mechanism to handle the differences in size and characters
allowed between this leaf and ifAlias. The definition of
such a mechanism is outside the scope of this document.
Since ifAlias is defined to be stored in non-volatile
storage, the MIB implementation MUST map ifAlias to the
value of 'description' in the persistently stored
datastore.
Specifically, if the device supports ':startup', when
ifAlias is read the device MUST return the value of
'description' in the 'startup' datastore, and when it is
written, it MUST be written to the 'running' and 'startup'
datastores. Note that it is up to the implementation to
decide whether to modify this single leaf in 'startup' or
perform an implicit copy-config from 'running' to
'startup'.
If the device does not support ':startup', ifAlias MUST
be mapped to the 'description' leaf in the 'running'
datastore.
nodetype: leaf (ro)
type: string
description:
[adapted from IETF interfaces model (RFC 7223)]
This leaf contains the configured, desired state of the
interface.
Systems that implement the IF-MIB use the value of this
leaf in the 'running' datastore to set
IF-MIB.ifAdminStatus to 'up' or 'down' after an ifEntry
has been initialized, as described in RFC 2863.
Changes in this leaf in the 'running' datastore are
reflected in ifAdminStatus, but if ifAdminStatus is
changed over SNMP, this leaf is not affected.
nodetype: leaf (ro)
type: boolean
description:
System assigned number for each interface. Corresponds to
ifIndex object in SNMP Interface MIB
nodetype: leaf (ro)
type: uint32
description:
[adapted from IETF interfaces model (RFC 7223)]
The desired state of the interface. In RFC 7223 this leaf
has the same read semantics as ifAdminStatus. Here, it
reflects the administrative state as set by enabling or
disabling the interface.
nodetype: leaf (ro)
type: enumeration
description:
[adapted from IETF interfaces model (RFC 7223)]
The current operational state of the interface.
This leaf has the same semantics as ifOperStatus.
nodetype: leaf (ro)
type: enumeration
description:
Date and time of the last state change of the interface
(e.g., up-to-down transition). This corresponds to the
ifLastChange object in the standard interface MIB.
nodetype: leaf (ro)
type: yang:timeticks
description:
A collection of interface-related statistics objects.
nodetype: container (ro)
description:
[adapted from IETF interfaces model (RFC 7223)]
The total number of octets received on the interface,
including framing characters.
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and at
other times as indicated by the value of
'discontinuity-time'.
nodetype: leaf (ro)
type: yang:counter64
description:
[adapted from IETF interfaces model (RFC 7223)]
The number of packets, delivered by this sub-layer to a
higher (sub-)layer, that were not addressed to a
multicast or broadcast address at this sub-layer.
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and at
other times as indicated by the value of
'discontinuity-time'.
nodetype: leaf (ro)
type: yang:counter64
description:
[adapted from IETF interfaces model (RFC 7223)]
The number of packets, delivered by this sub-layer to a
higher (sub-)layer, that were addressed to a broadcast
address at this sub-layer.
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and at
other times as indicated by the value of
'discontinuity-time'.
nodetype: leaf (ro)
type: yang:counter64
description:
[adapted from IETF interfaces model (RFC 7223)]
The number of packets, delivered by this sub-layer to a
higher (sub-)layer, that were addressed to a multicast
address at this sub-layer. For a MAC-layer protocol,
this includes both Group and Functional addresses.
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and at
other times as indicated by the value of
'discontinuity-time'.
nodetype: leaf (ro)
type: yang:counter64
description:
[adapted from IETF interfaces model (RFC 7223)]
Changed the counter type to counter64.
The number of inbound packets that were chosen to be
discarded even though no errors had been detected to
prevent their being deliverable to a higher-layer
protocol. One possible reason for discarding such a
packet could be to free up buffer space.
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and at
other times as indicated by the value of
'discontinuity-time'.
nodetype: leaf (ro)
type: yang:counter64
description:
[adapted from IETF interfaces model (RFC 7223)]
Changed the counter type to counter64.
For packet-oriented interfaces, the number of inbound
packets that contained errors preventing them from being
deliverable to a higher-layer protocol. For character-
oriented or fixed-length interfaces, the number of
inbound transmission units that contained errors
preventing them from being deliverable to a higher-layer
protocol.
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and at
other times as indicated by the value of
'discontinuity-time'.
nodetype: leaf (ro)
type: yang:counter64
description:
[adapted from IETF interfaces model (RFC 7223)]
Changed the counter type to counter64.
For packet-oriented interfaces, the number of packets
received via the interface that were discarded because
of an unknown or unsupported protocol. For
character-oriented or fixed-length interfaces that
support protocol multiplexing, the number of
transmission units received via the interface that were
discarded because of an unknown or unsupported protocol.
For any interface that does not support protocol
multiplexing, this counter is not present.
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and at
other times as indicated by the value of
'discontinuity-time'.
nodetype: leaf (ro)
type: yang:counter32
description:
[adapted from IETF interfaces model (RFC 7223)]
Changed the counter type to counter64.
The total number of octets transmitted out of the
interface, including framing characters.
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and at
other times as indicated by the value of
'discontinuity-time'.
nodetype: leaf (ro)
type: yang:counter64
description:
[adapted from IETF interfaces model (RFC 7223)]
The total number of packets that higher-level protocols
requested be transmitted, and that were not addressed
to a multicast or broadcast address at this sub-layer,
including those that were discarded or not sent.
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and at
other times as indicated by the value of
'discontinuity-time'.
nodetype: leaf (ro)
type: yang:counter64
description:
[adapted from IETF interfaces model (RFC 7223)]
The total number of packets that higher-level protocols
requested be transmitted, and that were addressed to a
broadcast address at this sub-layer, including those
that were discarded or not sent.
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and at
other times as indicated by the value of
'discontinuity-time'.
nodetype: leaf (ro)
type: yang:counter64
description:
[adapted from IETF interfaces model (RFC 7223)]
Changed the counter type to counter64.
The total number of packets that higher-level protocols
requested be transmitted, and that were addressed to a
multicast address at this sub-layer, including those
that were discarded or not sent. For a MAC-layer
protocol, this includes both Group and Functional
addresses.
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and at
other times as indicated by the value of
'discontinuity-time'.
nodetype: leaf (ro)
type: yang:counter64
description:
[adapted from IETF interfaces model (RFC 7223)]
Changed the counter type to counter64.
The number of outbound packets that were chosen to be
discarded even though no errors had been detected to
prevent their being transmitted. One possible reason
for discarding such a packet could be to free up buffer
space.
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and at
other times as indicated by the value of
'discontinuity-time'.
nodetype: leaf (ro)
type: yang:counter64
description:
[adapted from IETF interfaces model (RFC 7223)]
Changed the counter type to counter64.
For packet-oriented interfaces, the number of outbound
packets that could not be transmitted because of errors.
For character-oriented or fixed-length interfaces, the
number of outbound transmission units that could not be
transmitted because of errors.
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and at
other times as indicated by the value of
'discontinuity-time'.
nodetype: leaf (ro)
type: yang:counter64
description:
Indicates the last time the interface counters were
cleared.
nodetype: leaf (ro)
type: yang:date-and-time
description:
Optionally set the tag protocol identifier field (TPID) that
is accepted on the VLAN
nodetype: leaf (ro)
type: identityref
description:
References the hardware port in the device inventory
nodetype: leaf (ro)
type: leafref
description:
For a channelized interface, list of references to the
physical channels (lanes) corresponding to the interface.
nodetype: leaf-list (ro)
type: leafref
description:
Top-level container for hold-time settings to enable
dampening advertisements of interface transitions.
frinx-device-type:
junos
frinx-supported-versions:
173
nodetype: container (rw)
description:
Configuration data for interface hold-time settings.
frinx-device-type:
junos
frinx-supported-versions:
173
frinx-implemented-reader:
io.frinx.unitopo.unit.junos.interfaces.handler.InterfaceHoldTimeConfigReader
frinx-implemented-writer:
io.frinx.unitopo.unit.junos.interfaces.handler.InterfaceHoldTimeConfigWriter
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.ifc.handler.HoldTimeConfigReader
frinx-implemented-reader-details:
CARRIER_DELAY_LINE:
carrier-delay up (?<up>\d+) down (?<down>\d+)
frinx-implemented-writer:
io.frinx.cli.unit.iosxr.ifc.handler.HoldTimeConfigWriter
frinx-implemented-writer-details:
CARRIER_DELAY_COMMAND_TEMPLATE:
carrier-delay %s %s
nodetype: container (rw)
description:
Dampens advertisement when the interface
transitions from down to up. A zero value means dampening
is turned off, i.e., immediate notification.
nodetype: leaf (rw)
type: uint32
units: milliseconds
description:
Dampens advertisement when the interface transitions from
up to down. A zero value means dampening is turned off,
i.e., immediate notification.
nodetype: leaf (rw)
type: uint32
units: milliseconds
description:
Operational state data for interface hold-time.
nodetype: container (ro)
description:
Dampens advertisement when the interface
transitions from down to up. A zero value means dampening
is turned off, i.e., immediate notification.
nodetype: leaf (ro)
type: uint32
units: milliseconds
description:
Dampens advertisement when the interface transitions from
up to down. A zero value means dampening is turned off,
i.e., immediate notification.
nodetype: leaf (ro)
type: uint32
units: milliseconds
description:
Enclosing container for the list of subinterfaces associated
with a physical interface
frinx-device-type:
junos
frinx-supported-versions:
182
frinx-device-type:
junos
frinx-supported-versions:
173
nodetype: container (rw)
description:
The list of subinterfaces (logical interfaces) associated
with a physical interface
frinx-device-type:
ironware
frinx-supported-versions:
any
frinx-implemented-reader:
io.frinx.cli.unit.brocade.ifc.handler.subifc.SubinterfaceReader
frinx-implemented-writer:
MISSING WRITER
frinx-device-type:
vrp
frinx-supported-versions:
any
frinx-implemented-reader:
io.frinx.cli.unit.huawei.ifc.handler.subifc.SubinterfaceReader
frinx-device-type:
junos
frinx-supported-versions:
182
frinx-implemented-reader:
io.frinx.unitopo.unit.junos18.interfaces.handler.subinterfaces.SubinterfaceReader
frinx-device-type:
xr
frinx-supported-versions:
interface
frinx-implemented-reader:
io.frinx.unitopo.unit.xr66.interfaces.handler.subifc.SubinterfaceReader
frinx-device-type:
ios
frinx-supported-versions:
12any,15any
frinx-implemented-reader:
io.frinx.cli.unit.ios.ifc.handler.subifc.SubinterfaceReader
frinx-implemented-reader-details:
SEPARATOR:
.
SUBINTERFACE_NAME:
(?<ifcId>.+)[.](?<subifcIndex>[0-9]+)
frinx-implemented-writer:
MISSING WRITER
frinx-device-type:
junos
frinx-supported-versions:
14any
frinx-implemented-reader:
io.frinx.cli.unit.junos.ifc.handler.subifc.SubinterfaceReader
frinx-implemented-reader-details:
SEPARATOR:
unit
frinx-implemented-writer:
MISSING WRITER
frinx-device-type:
nos
frinx-supported-versions:
any
frinx-implemented-reader:
io.frinx.cli.unit.dasan.ifc.handler.subifc.SubinterfaceReader
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.ifc.handler.subifc.SubinterfaceReader
frinx-implemented-reader-details:
SEPARATOR:
.
SUBINTERFACE_NAME:
(?<ifcId>.+)[.](?<subifcIndex>[0-9]+)
frinx-implemented-writer:
MISSING WRITER
frinx-device-type:
junos
frinx-supported-versions:
173
frinx-implemented-reader:
io.frinx.unitopo.unit.junos.interfaces.handler.subinterfaces.SubinterfaceReader
frinx-device-type:
nexus
frinx-supported-versions:
any
frinx-implemented-reader:
io.frinx.cli.unit.nexus.ifc.handler.subifc.SubinterfaceReader
frinx-implemented-reader-details:
SEPARATOR:
.
frinx-implemented-writer:
MISSING WRITER
nodetype: list (rw)
list keys: [index]
description:
The index number of the subinterface -- used to address
the logical interface
nodetype: leaf (list key) (rw)
type: leafref
description:
Configurable items at the subinterface level
frinx-device-type:
ironware
frinx-supported-versions:
any
frinx-implemented-reader:
io.frinx.cli.unit.brocade.ifc.handler.subifc.SubinterfaceConfigReader
frinx-implemented-writer:
MISSING WRITER
frinx-device-type:
vrp
frinx-supported-versions:
any
frinx-implemented-reader:
io.frinx.cli.unit.huawei.ifc.handler.subifc.SubinterfaceConfigReader
frinx-device-type:
junos
frinx-supported-versions:
182
frinx-implemented-reader:
io.frinx.unitopo.unit.junos18.interfaces.handler.subinterfaces.SubinterfaceConfigReader
frinx-implemented-writer:
io.frinx.unitopo.unit.junos18.interfaces.handler.subinterfaces.SubinterfaceConfigWriter
frinx-device-type:
xr
frinx-supported-versions:
interface
frinx-implemented-reader:
io.frinx.unitopo.unit.xr66.interfaces.handler.subifc.SubinterfaceConfigReader
frinx-implemented-writer:
io.frinx.unitopo.unit.xr66.interfaces.handler.subifc.SubinterfaceConfigWriter
frinx-device-type:
ios
frinx-supported-versions:
12any,15any
frinx-implemented-reader:
io.frinx.cli.unit.ios.ifc.handler.subifc.SubinterfaceConfigReader
frinx-implemented-writer:
io.frinx.cli.unit.ios.ifc.handler.subifc.SubinterfaceConfigWriter
frinx-implemented-writer-details:
DELETE_TEMPLATE:
configure terminal
no interface {$name}
end
UPDATE_TEMPLATE:
configure terminal
interface {$name}
{$data|update(description,description `$data.description`
,no description
)}{% if ($enabled) %}no shutdown
{% else %}shutdown
{% endif %}end
frinx-device-type:
junos
frinx-supported-versions:
14any
frinx-implemented-reader:
io.frinx.cli.unit.junos.ifc.handler.subifc.SubinterfaceConfigReader
frinx-implemented-reader-details:
SUBIF_DESCRIPTION_LINE:
set interfaces (?<ifcId>\S+) unit (?<subifcIndex>[0-9]+) description (?<desc>.*)
SUBIF_DISABLE_LINE:
set interfaces (?<ifcId>\S+) unit (?<subifcIndex>[0-9]+) disable
frinx-implemented-writer:
io.frinx.cli.unit.junos.ifc.handler.subifc.SubinterfaceConfigWriter
frinx-implemented-writer-details:
DELETE_TEMPLATE:
delete interfaces {$name}
UPDATE_TEMPLATE:
{$data|update(description,set interfaces `$name` description `$data.description`
,delete interfaces `$name` description
)}{% if ($enabled && $enabled == TRUE) %}delete interfaces {$name} disable{% elseIf (!$enabled) %}set interfaces {$name} disable{% endif %}
frinx-device-type:
nos
frinx-supported-versions:
any
frinx-implemented-reader:
io.frinx.cli.unit.dasan.ifc.handler.subifc.SubinterfaceConfigReader
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.ifc.handler.subifc.SubinterfaceConfigReader
frinx-implemented-writer:
io.frinx.cli.unit.iosxr.ifc.handler.subifc.SubinterfaceConfigWriter
frinx-implemented-writer-details:
DELETE_TEMPLATE:
no interface {$name}
UPDATE_TEMPLATE:
interface {$name}
{$data|update(description,description `$data.description`
,no description
)}{% if ($enabled) %}no shutdown
{% else %}shutdown
{% endif %}root
frinx-device-type:
junos
frinx-supported-versions:
173
frinx-implemented-reader:
io.frinx.unitopo.unit.junos.interfaces.handler.subinterfaces.SubinterfaceConfigReader
frinx-implemented-writer:
io.frinx.unitopo.unit.junos.interfaces.handler.subinterfaces.SubinterfaceConfigWriter
frinx-device-type:
nexus
frinx-supported-versions:
any
frinx-implemented-reader:
io.frinx.cli.unit.nexus.ifc.handler.subifc.SubinterfaceConfigReader
frinx-implemented-writer:
io.frinx.cli.unit.nexus.ifc.handler.subifc.SubinterfaceConfigWriter
frinx-implemented-writer-details:
DELETE_TEMPLATE:
no interface {$name}
UPDATE_TEMPLATE:
interface {$name}
{$data|update(description,description `$data.description`
,no description
)}{% if ($enabled) %}no shutdown
{% else %}shutdown
{% endif %}root
nodetype: container (rw)
description:
The index of the subinterface, or logical interface number.
On systems with no support for subinterfaces, or not using
subinterfaces, this value should default to 0, i.e., the
default subinterface.
nodetype: leaf (rw)
type: uint32
description:
[adapted from IETF interfaces model (RFC 7223)]
The name of the interface.
A device MAY restrict the allowed values for this leaf,
possibly depending on the type of the interface.
For system-controlled interfaces, this leaf is the
device-specific name of the interface. The 'config false'
list interfaces/interface[name]/state contains the currently
existing interfaces on the device.
If a client tries to create configuration for a
system-controlled interface that is not present in the
corresponding state list, the server MAY reject
the request if the implementation does not support
pre-provisioning of interfaces or if the name refers to
an interface that can never exist in the system. A
NETCONF server MUST reply with an rpc-error with the
error-tag 'invalid-value' in this case.
The IETF model in RFC 7223 provides YANG features for the
following (i.e., pre-provisioning and arbitrary-names),
however they are omitted here:
If the device supports pre-provisioning of interface
configuration, the 'pre-provisioning' feature is
advertised.
If the device allows arbitrarily named user-controlled
interfaces, the 'arbitrary-names' feature is advertised.
When a configured user-controlled interface is created by
the system, it is instantiated with the same name in the
/interfaces/interface[name]/state list.
nodetype: leaf (rw)
type: string
description:
[adapted from IETF interfaces model (RFC 7223)]
A textual description of the interface.
A server implementation MAY map this leaf to the ifAlias
MIB object. Such an implementation needs to use some
mechanism to handle the differences in size and characters
allowed between this leaf and ifAlias. The definition of
such a mechanism is outside the scope of this document.
Since ifAlias is defined to be stored in non-volatile
storage, the MIB implementation MUST map ifAlias to the
value of 'description' in the persistently stored
datastore.
Specifically, if the device supports ':startup', when
ifAlias is read the device MUST return the value of
'description' in the 'startup' datastore, and when it is
written, it MUST be written to the 'running' and 'startup'
datastores. Note that it is up to the implementation to
decide whether to modify this single leaf in 'startup' or
perform an implicit copy-config from 'running' to
'startup'.
If the device does not support ':startup', ifAlias MUST
be mapped to the 'description' leaf in the 'running'
datastore.
nodetype: leaf (rw)
type: string
description:
[adapted from IETF interfaces model (RFC 7223)]
This leaf contains the configured, desired state of the
interface.
Systems that implement the IF-MIB use the value of this
leaf in the 'running' datastore to set
IF-MIB.ifAdminStatus to 'up' or 'down' after an ifEntry
has been initialized, as described in RFC 2863.
Changes in this leaf in the 'running' datastore are
reflected in ifAdminStatus, but if ifAdminStatus is
changed over SNMP, this leaf is not affected.
nodetype: leaf (rw)
type: boolean
description:
The rpm type of the subinterface
nodetype: leaf (rw)
type: rpm-types
description:
Operational state data for logical interfaces
frinx-device-type:
ios
frinx-supported-versions:
12any,15any
frinx-implemented-reader:
io.frinx.cli.unit.ios.ifc.handler.subifc.SubinterfaceStateReader
frinx-implemented-writer:
MISSING WRITER
frinx-device-type:
vrp
frinx-supported-versions:
any
frinx-implemented-reader:
io.frinx.cli.unit.huawei.ifc.handler.subifc.SubinterfaceStateReader
frinx-implemented-writer:
MISSING WRITER
nodetype: container (ro)
description:
The index of the subinterface, or logical interface number.
On systems with no support for subinterfaces, or not using
subinterfaces, this value should default to 0, i.e., the
default subinterface.
nodetype: leaf (ro)
type: uint32
description:
[adapted from IETF interfaces model (RFC 7223)]
The name of the interface.
A device MAY restrict the allowed values for this leaf,
possibly depending on the type of the interface.
For system-controlled interfaces, this leaf is the
device-specific name of the interface. The 'config false'
list interfaces/interface[name]/state contains the currently
existing interfaces on the device.
If a client tries to create configuration for a
system-controlled interface that is not present in the
corresponding state list, the server MAY reject
the request if the implementation does not support
pre-provisioning of interfaces or if the name refers to
an interface that can never exist in the system. A
NETCONF server MUST reply with an rpc-error with the
error-tag 'invalid-value' in this case.
The IETF model in RFC 7223 provides YANG features for the
following (i.e., pre-provisioning and arbitrary-names),
however they are omitted here:
If the device supports pre-provisioning of interface
configuration, the 'pre-provisioning' feature is
advertised.
If the device allows arbitrarily named user-controlled
interfaces, the 'arbitrary-names' feature is advertised.
When a configured user-controlled interface is created by
the system, it is instantiated with the same name in the
/interfaces/interface[name]/state list.
nodetype: leaf (ro)
type: string
description:
[adapted from IETF interfaces model (RFC 7223)]
A textual description of the interface.
A server implementation MAY map this leaf to the ifAlias
MIB object. Such an implementation needs to use some
mechanism to handle the differences in size and characters
allowed between this leaf and ifAlias. The definition of
such a mechanism is outside the scope of this document.
Since ifAlias is defined to be stored in non-volatile
storage, the MIB implementation MUST map ifAlias to the
value of 'description' in the persistently stored
datastore.
Specifically, if the device supports ':startup', when
ifAlias is read the device MUST return the value of
'description' in the 'startup' datastore, and when it is
written, it MUST be written to the 'running' and 'startup'
datastores. Note that it is up to the implementation to
decide whether to modify this single leaf in 'startup' or
perform an implicit copy-config from 'running' to
'startup'.
If the device does not support ':startup', ifAlias MUST
be mapped to the 'description' leaf in the 'running'
datastore.
nodetype: leaf (ro)
type: string
description:
[adapted from IETF interfaces model (RFC 7223)]
This leaf contains the configured, desired state of the
interface.
Systems that implement the IF-MIB use the value of this
leaf in the 'running' datastore to set
IF-MIB.ifAdminStatus to 'up' or 'down' after an ifEntry
has been initialized, as described in RFC 2863.
Changes in this leaf in the 'running' datastore are
reflected in ifAdminStatus, but if ifAdminStatus is
changed over SNMP, this leaf is not affected.
nodetype: leaf (ro)
type: boolean
description:
System assigned number for each interface. Corresponds to
ifIndex object in SNMP Interface MIB
nodetype: leaf (ro)
type: uint32
description:
[adapted from IETF interfaces model (RFC 7223)]
The desired state of the interface. In RFC 7223 this leaf
has the same read semantics as ifAdminStatus. Here, it
reflects the administrative state as set by enabling or
disabling the interface.
nodetype: leaf (ro)
type: enumeration
description:
[adapted from IETF interfaces model (RFC 7223)]
The current operational state of the interface.
This leaf has the same semantics as ifOperStatus.
nodetype: leaf (ro)
type: enumeration
description:
Date and time of the last state change of the interface
(e.g., up-to-down transition). This corresponds to the
ifLastChange object in the standard interface MIB.
nodetype: leaf (ro)
type: yang:timeticks
description:
A collection of interface-related statistics objects.
nodetype: container (ro)
description:
[adapted from IETF interfaces model (RFC 7223)]
The total number of octets received on the interface,
including framing characters.
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and at
other times as indicated by the value of
'discontinuity-time'.
nodetype: leaf (ro)
type: yang:counter64
description:
[adapted from IETF interfaces model (RFC 7223)]
The number of packets, delivered by this sub-layer to a
higher (sub-)layer, that were not addressed to a
multicast or broadcast address at this sub-layer.
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and at
other times as indicated by the value of
'discontinuity-time'.
nodetype: leaf (ro)
type: yang:counter64
description:
[adapted from IETF interfaces model (RFC 7223)]
The number of packets, delivered by this sub-layer to a
higher (sub-)layer, that were addressed to a broadcast
address at this sub-layer.
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and at
other times as indicated by the value of
'discontinuity-time'.
nodetype: leaf (ro)
type: yang:counter64
description:
[adapted from IETF interfaces model (RFC 7223)]
The number of packets, delivered by this sub-layer to a
higher (sub-)layer, that were addressed to a multicast
address at this sub-layer. For a MAC-layer protocol,
this includes both Group and Functional addresses.
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and at
other times as indicated by the value of
'discontinuity-time'.
nodetype: leaf (ro)
type: yang:counter64
description:
[adapted from IETF interfaces model (RFC 7223)]
Changed the counter type to counter64.
The number of inbound packets that were chosen to be
discarded even though no errors had been detected to
prevent their being deliverable to a higher-layer
protocol. One possible reason for discarding such a
packet could be to free up buffer space.
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and at
other times as indicated by the value of
'discontinuity-time'.
nodetype: leaf (ro)
type: yang:counter64
description:
[adapted from IETF interfaces model (RFC 7223)]
Changed the counter type to counter64.
For packet-oriented interfaces, the number of inbound
packets that contained errors preventing them from being
deliverable to a higher-layer protocol. For character-
oriented or fixed-length interfaces, the number of
inbound transmission units that contained errors
preventing them from being deliverable to a higher-layer
protocol.
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and at
other times as indicated by the value of
'discontinuity-time'.
nodetype: leaf (ro)
type: yang:counter64
description:
[adapted from IETF interfaces model (RFC 7223)]
Changed the counter type to counter64.
For packet-oriented interfaces, the number of packets
received via the interface that were discarded because
of an unknown or unsupported protocol. For
character-oriented or fixed-length interfaces that
support protocol multiplexing, the number of
transmission units received via the interface that were
discarded because of an unknown or unsupported protocol.
For any interface that does not support protocol
multiplexing, this counter is not present.
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and at
other times as indicated by the value of
'discontinuity-time'.
nodetype: leaf (ro)
type: yang:counter32
description:
[adapted from IETF interfaces model (RFC 7223)]
Changed the counter type to counter64.
The total number of octets transmitted out of the
interface, including framing characters.
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and at
other times as indicated by the value of
'discontinuity-time'.
nodetype: leaf (ro)
type: yang:counter64
description:
[adapted from IETF interfaces model (RFC 7223)]
The total number of packets that higher-level protocols
requested be transmitted, and that were not addressed
to a multicast or broadcast address at this sub-layer,
including those that were discarded or not sent.
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and at
other times as indicated by the value of
'discontinuity-time'.
nodetype: leaf (ro)
type: yang:counter64
description:
[adapted from IETF interfaces model (RFC 7223)]
The total number of packets that higher-level protocols
requested be transmitted, and that were addressed to a
broadcast address at this sub-layer, including those
that were discarded or not sent.
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and at
other times as indicated by the value of
'discontinuity-time'.
nodetype: leaf (ro)
type: yang:counter64
description:
[adapted from IETF interfaces model (RFC 7223)]
Changed the counter type to counter64.
The total number of packets that higher-level protocols
requested be transmitted, and that were addressed to a
multicast address at this sub-layer, including those
that were discarded or not sent. For a MAC-layer
protocol, this includes both Group and Functional
addresses.
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and at
other times as indicated by the value of
'discontinuity-time'.
nodetype: leaf (ro)
type: yang:counter64
description:
[adapted from IETF interfaces model (RFC 7223)]
Changed the counter type to counter64.
The number of outbound packets that were chosen to be
discarded even though no errors had been detected to
prevent their being transmitted. One possible reason
for discarding such a packet could be to free up buffer
space.
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and at
other times as indicated by the value of
'discontinuity-time'.
nodetype: leaf (ro)
type: yang:counter64
description:
[adapted from IETF interfaces model (RFC 7223)]
Changed the counter type to counter64.
For packet-oriented interfaces, the number of outbound
packets that could not be transmitted because of errors.
For character-oriented or fixed-length interfaces, the
number of outbound transmission units that could not be
transmitted because of errors.
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and at
other times as indicated by the value of
'discontinuity-time'.
nodetype: leaf (ro)
type: yang:counter64
description:
Indicates the last time the interface counters were
cleared.
nodetype: leaf (ro)
type: yang:date-and-time
description:
Enclosing container for VLAN interface-specific
data on subinterfaces
frinx-device-type:
junos
frinx-supported-versions:
182
nodetype: container (rw)
description:
Configuration parameters for VLANs
frinx-device-type:
ios
frinx-supported-versions:
12any,15any
frinx-implemented-reader:
io.frinx.cli.unit.ios.ifc.handler.subifc.SubinterfaceVlanConfigReader
frinx-implemented-reader-details:
VLAN_TAG_LINE:
encapsulation dot1Q (?<tag>[0-9]+)
frinx-implemented-writer:
io.frinx.cli.unit.ios.ifc.handler.subifc.SubinterfaceVlanConfigWriter
frinx-implemented-writer-details:
DELETE_TEMPLATE:
configure terminal
interface %s
no encapsulation dot1Q %s
end
WRITE_TEMPLATE:
configure terminal
interface %s
encapsulation dot1Q %s
end
frinx-device-type:
vrp
frinx-supported-versions:
any
frinx-device-type:
junos
frinx-supported-versions:
182
frinx-implemented-reader:
io.frinx.unitopo.unit.junos18.interfaces.handler.subinterfaces.SubinterfaceVlanConfigReader
frinx-implemented-reader-details:
QINQID_PATTERN:
(?<outer>\d+)\.(?<inner>\d+)
TAGGED_VLAN_PATTERN:
0x8100:(?<vlanid>\d+)
VLAN_PROTOCOL_ID:
0x8100
frinx-implemented-writer:
io.frinx.unitopo.unit.junos18.interfaces.handler.subinterfaces.SubinterfaceVlanConfigWriter
frinx-device-type:
xr
frinx-supported-versions:
interface
frinx-implemented-reader:
io.frinx.unitopo.unit.xr66.interfaces.handler.subifc.vlan.SubinterfaceVlanConfigReader
frinx-implemented-writer:
io.frinx.unitopo.unit.xr66.interfaces.handler.subifc.vlan.SubinterfaceVlanConfigWriter
frinx-device-type:
junos
frinx-supported-versions:
14any
frinx-implemented-reader:
io.frinx.cli.unit.junos.ifc.handler.subifc.SubinterfaceVlanConfigReader
frinx-implemented-reader-details:
VLAN_TAG_LINE:
set interfaces (?<ifcId>.+) unit (?<subifcIndex>[0-9]+) vlan-id (?<tag>[0-9]+)
frinx-implemented-writer:
io.frinx.cli.unit.junos.ifc.handler.subifc.SubinterfaceVlanConfigWriter
frinx-implemented-writer-details:
DELETE_TEMPLATE:
delete interfaces %s vlan-id
WRITE_TEMPLATE:
set interfaces %s vlan-id %s
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.ifc.handler.subifc.SubinterfaceVlanConfigReader
frinx-implemented-reader-details:
VLAN_TAG_LINE:
encapsulation dot1q (?<tag>[0-9]+)
frinx-implemented-writer:
io.frinx.cli.unit.iosxr.ifc.handler.subifc.SubinterfaceVlanConfigWriter
frinx-implemented-writer-details:
DELETE_TEMPLATE:
interface %s
no encapsulation dot1q %s
root
WRITE_TEMPLATE:
interface %s
encapsulation dot1q %s
root
frinx-device-type:
nexus
frinx-supported-versions:
any
frinx-implemented-reader:
io.frinx.cli.unit.nexus.ifc.handler.subifc.SubinterfaceVlanConfigReader
frinx-implemented-reader-details:
VLAN_TAG_LINE:
encapsulation dot1q (?<tag>[0-9]+)
frinx-implemented-writer:
io.frinx.cli.unit.nexus.ifc.handler.subifc.SubinterfaceVlanConfigWriter
frinx-implemented-writer-details:
DELETE_TEMPLATE:
interface %s
no encapsulation dot1q %s
root
WRITE_TEMPLATE:
interface %s
encapsulation dot1q %s
root
nodetype: container (rw)
description:
VLAN id for the subinterface -- specified inline for the
case of a local VLAN. The id is scoped to the
subinterface, and could be repeated on different
subinterfaces.
nodetype: leaf (rw)
type: union
type: oc-vlan-types:vlan-id
type: oc-vlan-types:qinq-id
description:
State variables for VLANs
nodetype: container (ro)
description:
VLAN id for the subinterface -- specified inline for the
case of a local VLAN. The id is scoped to the
subinterface, and could be repeated on different
subinterfaces.
nodetype: leaf (ro)
type: union
type: oc-vlan-types:vlan-id
type: oc-vlan-types:qinq-id
description:
Parameters for the IPv4 address family.
frinx-device-type:
junos
frinx-supported-versions:
182
frinx-device-type:
junos
frinx-supported-versions:
173
nodetype: container (rw)
description:
Enclosing container for address list
frinx-device-type:
junos
frinx-supported-versions:
182
frinx-device-type:
junos
frinx-supported-versions:
173
nodetype: container (rw)
description:
The list of configured IPv4 addresses on the interface.
frinx-device-type:
ironware
frinx-supported-versions:
any
frinx-implemented-reader:
io.frinx.cli.unit.brocade.ifc.handler.subifc.ip4.Ipv4AddressReader
frinx-implemented-reader-details:
INTERFACE_IP_LINE:
ip address (?<ip>[^/]+)/(?<prefix>[0-9]+)
SH_INTERFACE_IP:
show running-config interface {$ifcType} {$ifcNumber} | include ip address
frinx-implemented-writer:
MISSING WRITER
frinx-device-type:
vrp
frinx-supported-versions:
any
frinx-implemented-reader:
io.frinx.cli.unit.huawei.ifc.handler.subifc.ip4.Ipv4AddressReader
frinx-implemented-reader-details:
DISPLAY_IP_INT_BRIEF:
display ip int brief %s
INTERFACE_IP_LINE:
(?<id>[^\s]+)\s+(?<ip>[^/]+)/(?<prefix>[0-9]+)\s+(?<status>[^\s]+)\s+(?<protocol>[^\s]+)\s+(?<vpn>[^\s]+)\s*
frinx-device-type:
junos
frinx-supported-versions:
182
frinx-implemented-reader:
io.frinx.unitopo.unit.junos18.interfaces.handler.subinterfaces.SubinterfaceAddressReader
frinx-device-type:
xr
frinx-supported-versions:
interface
frinx-implemented-reader:
io.frinx.unitopo.unit.xr66.interfaces.handler.subifc.Ipv4AddressReader
frinx-device-type:
ios
frinx-supported-versions:
12any,15any
frinx-implemented-reader:
io.frinx.cli.unit.ios.ifc.handler.subifc.ip4.Ipv4AddressReader
frinx-implemented-reader-details:
INTERFACE_IP_LINE:
ip address (?<ip>\S+) (?<prefix>\S+)
SH_INTERFACE_IP:
show running-config interface %s | include ^ ip address
frinx-implemented-writer:
MISSING WRITER
frinx-device-type:
junos
frinx-supported-versions:
14any
frinx-implemented-reader:
io.frinx.cli.unit.junos.ifc.handler.subifc.ip4.Ipv4AddressReader
frinx-implemented-reader-details:
INTERFACE_IP_LINE:
set interfaces (?<ifcId>.+) unit (?<subifcIndex>[0-9]+) family inet address (?<ip>[^/]+)/(?<prefix>[0-9]+)
SH_RUN_INT_IP:
show configuration interfaces %s | display set | match " inet address "
frinx-implemented-writer:
MISSING WRITER
frinx-device-type:
nos
frinx-supported-versions:
any
frinx-implemented-reader:
io.frinx.cli.unit.dasan.ifc.handler.subifc.ip4.Ipv4AddressReader
frinx-implemented-reader-details:
DISPLAY_IP_INT_BRIEF:
show running-config interface %s
INTERFACE_IP_LINE:
^\s*ip address (?<ip>[^/]+)/(?<prefix>[0-9]+)
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.ifc.handler.subifc.ip4.Ipv4AddressReader
frinx-implemented-reader-details:
INTERFACE_IP_LINE:
ipv4 address (?<ip>\S+) (?<prefix>\S+)
SH_RUN_INT_IP:
show running-config interface %s | include ^ ipv4 address
frinx-implemented-writer:
MISSING WRITER
frinx-device-type:
junos
frinx-supported-versions:
173
frinx-implemented-reader:
io.frinx.unitopo.unit.junos.interfaces.handler.subinterfaces.SubinterfaceAddressReader
frinx-device-type:
nexus
frinx-supported-versions:
any
frinx-implemented-reader:
io.frinx.cli.unit.nexus.ifc.handler.subifc.ipv4.Ipv4AddressReader
frinx-implemented-reader-details:
INTERFACE_IP_LINE:
ip address (?<ip>\S+)/(?<prefix>\S+)
SH_RUN_INT_IP:
show running-config interface %s | include ^ ip address
frinx-implemented-writer:
MISSING WRITER
nodetype: list (rw)
list keys: [ip]
description:
References the configured IP address
nodetype: leaf (list key) (rw)
type: leafref
description:
Configuration data for each configured IPv4
address on the interface
frinx-device-type:
ironware
frinx-supported-versions:
any
frinx-implemented-reader:
io.frinx.cli.unit.brocade.ifc.handler.subifc.ip4.Ipv4ConfigReader
frinx-implemented-writer:
io.frinx.cli.unit.brocade.ifc.handler.subifc.ip4.Ipv4ConfigWriter
frinx-implemented-writer-details:
WRITE_TEMPLATE:
configure terminal
interface {$name}
{% if ($delete) %}no {% endif %}ip address {$ip} {$netmask}
end
frinx-device-type:
vrp
frinx-supported-versions:
any
frinx-implemented-reader:
io.frinx.cli.unit.huawei.ifc.handler.subifc.ip4.Ipv4ConfigReader
frinx-implemented-writer:
io.frinx.cli.unit.huawei.ifc.handler.subifc.ip4.Ipv4ConfigWriter
frinx-implemented-writer-details:
TEMPLATE:
system-view
interface {$name}
{% if {$delete} %}undo ip address
{% else %}ip address {$config.ip.value} {$config.prefix_length}
{% endif %}commit
return
frinx-device-type:
junos
frinx-supported-versions:
182
frinx-implemented-reader:
io.frinx.unitopo.unit.junos18.interfaces.handler.subinterfaces.SubinterfaceAddressConfigReader
frinx-implemented-writer:
io.frinx.unitopo.unit.junos18.interfaces.handler.subinterfaces.SubinterfaceAddressConfigWriter
frinx-device-type:
xr
frinx-supported-versions:
interface
frinx-implemented-reader:
io.frinx.unitopo.unit.xr66.interfaces.handler.subifc.Ipv4ConfigReader
frinx-implemented-writer:
io.frinx.unitopo.unit.xr66.interfaces.handler.subifc.Ipv4ConfigWriter
frinx-device-type:
ios
frinx-supported-versions:
12any,15any
frinx-implemented-reader:
io.frinx.cli.unit.ios.ifc.handler.subifc.ip4.Ipv4ConfigReader
frinx-implemented-writer:
io.frinx.cli.unit.ios.ifc.handler.subifc.ip4.Ipv4ConfigWriter
frinx-implemented-writer-details:
TEMPLATE:
configure terminal
interface {$name}
{% if ($delete) %} no ip address
{% else %} ip address {$ip} {$netmask}
{% endif %}end
frinx-device-type:
junos
frinx-supported-versions:
14any
frinx-implemented-reader:
io.frinx.cli.unit.junos.ifc.handler.subifc.ip4.Ipv4ConfigReader
frinx-implemented-writer:
io.frinx.cli.unit.junos.ifc.handler.subifc.ip4.Ipv4ConfigWriter
frinx-implemented-writer-details:
TEMPLATE:
{% if($delete) %}delete{% else %}set{% endif %} interfaces {$name} family inet address {$config.ip.value}/{$config.prefix_length}
frinx-device-type:
nos
frinx-supported-versions:
any
frinx-implemented-reader:
io.frinx.cli.unit.dasan.ifc.handler.subifc.ip4.Ipv4AddressConfigReader
frinx-implemented-writer:
io.frinx.cli.unit.dasan.ifc.handler.subifc.ip4.Ipv4AddressConfigWriter
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.ifc.handler.subifc.ip4.Ipv4ConfigReader
frinx-implemented-writer:
io.frinx.cli.unit.iosxr.ifc.handler.subifc.ip4.Ipv4ConfigWriter
frinx-implemented-writer-details:
TEMPLATE:
interface {$name}
{% if ($delete) %}no ipv4 address
{% else %}ipv4 address {$ip} {$netmask}
{% endif %}root
frinx-device-type:
junos
frinx-supported-versions:
173
frinx-implemented-reader:
io.frinx.unitopo.unit.junos.interfaces.handler.subinterfaces.SubinterfaceAddressConfigReader
frinx-implemented-writer:
io.frinx.unitopo.unit.junos.interfaces.handler.subinterfaces.SubinterfaceAddressConfigWriter
frinx-device-type:
nexus
frinx-supported-versions:
any
frinx-implemented-reader:
io.frinx.cli.unit.nexus.ifc.handler.subifc.ipv4.Ipv4ConfigReader
frinx-implemented-writer:
io.frinx.cli.unit.nexus.ifc.handler.subifc.ipv4.Ipv4ConfigWriter
frinx-implemented-writer-details:
TEMPLATE:
interface {$name}
{% if($delete) %} no{% endif %} ip address {$config.ip.value}/{$config.prefix_length}
root
nodetype: container (rw)
description:
[adapted from IETF IP model RFC 7277]
The IPv4 address on the interface.
nodetype: leaf (rw)
type: inet:ipv4-address-no-zone
description:
[adapted from IETF IP model RFC 7277]
The length of the subnet prefix.
nodetype: leaf (rw)
type: uint8
description:
Operational state data for each IPv4 address
configured on the interface
nodetype: container (ro)
description:
[adapted from IETF IP model RFC 7277]
The IPv4 address on the interface.
nodetype: leaf (ro)
type: inet:ipv4-address-no-zone
description:
[adapted from IETF IP model RFC 7277]
The length of the subnet prefix.
nodetype: leaf (ro)
type: uint8
description:
The origin of this address, e.g., statically configured,
assigned by DHCP, etc..
nodetype: leaf (ro)
type: ip-address-origin
description:
Enclosing container for VRRP groups handled by this
IP interface
frinx-device-type:
junos
frinx-supported-versions:
182
nodetype: container (rw)
description:
List of VRRP groups, keyed by virtual router id
frinx-device-type:
junos
frinx-supported-versions:
182
frinx-implemented-reader:
io.frinx.unitopo.unit.junos18.interfaces.handler.subinterfaces.SubinterfaceVrrpGroupReader
nodetype: list (rw)
list keys: [virtual-router-id]
description:
References the configured virtual router id for this
VRRP group
nodetype: leaf (list key) (rw)
type: leafref
description:
Configuration data for the VRRP group
frinx-device-type:
junos
frinx-supported-versions:
182
frinx-implemented-reader:
io.frinx.unitopo.unit.junos18.interfaces.handler.subinterfaces.SubinterfaceVrrpGroupConfigReader
frinx-implemented-writer:
io.frinx.unitopo.unit.junos18.interfaces.handler.subinterfaces.SubinterfaceVrrpGroupConfigWriter
nodetype: container (rw)
description:
Set the virtual router id for use by the VRRP group. This
usually also determines the virtual MAC address that is
generated for the VRRP group
nodetype: leaf (rw)
type: uint8
description:
Configure one or more virtual addresses for the
VRRP group
nodetype: leaf-list (rw)
type: inet:ip-address
description:
Specifies the sending VRRP interface's priority
for the virtual router. Higher values equal higher
priority
nodetype: leaf (rw)
type: uint8
description:
When set to true, enables preemption by a higher
priority backup router of a lower priority master router
nodetype: leaf (rw)
type: boolean
description:
Set the delay the higher priority router waits
before preempting
nodetype: leaf (rw)
type: uint16
description:
Configure whether packets destined for
virtual addresses are accepted even when the virtual
address is not owned by the router interface
nodetype: leaf (rw)
type: boolean
description:
Sets the interval between successive VRRP
advertisements -- RFC 5798 defines this as a 12-bit
value expressed as 0.1 seconds, with default 100, i.e.,
1 second. Several implementation express this in units of
seconds
nodetype: leaf (rw)
type: uint16
units: centiseconds
description:
Operational state data for the VRRP group
nodetype: container (ro)
description:
Set the virtual router id for use by the VRRP group. This
usually also determines the virtual MAC address that is
generated for the VRRP group
nodetype: leaf (ro)
type: uint8
description:
Configure one or more virtual addresses for the
VRRP group
nodetype: leaf-list (ro)
type: inet:ip-address
description:
Specifies the sending VRRP interface's priority
for the virtual router. Higher values equal higher
priority
nodetype: leaf (ro)
type: uint8
description:
When set to true, enables preemption by a higher
priority backup router of a lower priority master router
nodetype: leaf (ro)
type: boolean
description:
Set the delay the higher priority router waits
before preempting
nodetype: leaf (ro)
type: uint16
description:
Configure whether packets destined for
virtual addresses are accepted even when the virtual
address is not owned by the router interface
nodetype: leaf (ro)
type: boolean
description:
Sets the interval between successive VRRP
advertisements -- RFC 5798 defines this as a 12-bit
value expressed as 0.1 seconds, with default 100, i.e.,
1 second. Several implementation express this in units of
seconds
nodetype: leaf (ro)
type: uint16
units: centiseconds
description:
Operational value of the priority for the
interface in the VRRP group
nodetype: leaf (ro)
type: uint8
description:
Top-level container for VRRP interface tracking
nodetype: container (rw)
description:
Configuration data for VRRP interface tracking
nodetype: container (rw)
description:
Sets an interface that should be
tracked for up/down events to dynamically change the
priority state of the VRRP group, and potentially
change the mastership if the tracked interface going
down lowers the priority sufficiently
nodetype: leaf (rw)
type: leafref
description:
Set the value to subtract from priority when
the tracked interface goes down
nodetype: leaf (rw)
type: uint8
description:
Operational state data for VRRP interface tracking
nodetype: container (ro)
description:
Sets an interface that should be
tracked for up/down events to dynamically change the
priority state of the VRRP group, and potentially
change the mastership if the tracked interface going
down lowers the priority sufficiently
nodetype: leaf (ro)
type: leafref
description:
Set the value to subtract from priority when
the tracked interface goes down
nodetype: leaf (ro)
type: uint8
description:
Enclosing container for neighbor list
nodetype: container (rw)
description:
A list of mappings from IPv4 addresses to
link-layer addresses.
Entries in this list are used as static entries in the
ARP Cache.
nodetype: list (rw)
list keys: [ip]
description:
References the configured IP address
nodetype: leaf (list key) (rw)
type: leafref
description:
Configuration data for each configured IPv4
address on the interface
nodetype: container (rw)
description:
The IPv4 address of the neighbor node.
nodetype: leaf (rw)
type: inet:ipv4-address-no-zone
description:
The link-layer address of the neighbor node.
nodetype: leaf (rw)
type: yang:phys-address
description:
Operational state data for each IPv4 address
configured on the interface
nodetype: container (ro)
description:
The IPv4 address of the neighbor node.
nodetype: leaf (ro)
type: inet:ipv4-address-no-zone
description:
The link-layer address of the neighbor node.
nodetype: leaf (ro)
type: yang:phys-address
description:
The origin of this neighbor entry, static or dynamic.
nodetype: leaf (ro)
type: neighbor-origin
description:
Top-level container for setting unnumbered interfaces.
Includes reference the interface that provides the
address information
nodetype: container (rw)
description:
Configuration data for unnumbered interface
nodetype: container (rw)
description:
Indicates that the subinterface is unnumbered. By default
the subinterface is numbered, i.e., expected to have an
IP address configuration.
nodetype: leaf (rw)
type: boolean
description:
Operational state data for unnumbered interfaces
nodetype: container (ro)
description:
Indicates that the subinterface is unnumbered. By default
the subinterface is numbered, i.e., expected to have an
IP address configuration.
nodetype: leaf (ro)
type: boolean
description:
Reference to an interface or subinterface
nodetype: container (rw)
description:
Configured reference to interface / subinterface
nodetype: container (rw)
description:
Reference to a base interface. If a reference to a
subinterface is required, this leaf must be specified
to indicate the base interface.
nodetype: leaf (rw)
type: leafref
description:
Reference to a subinterface -- this requires the base
interface to be specified using the interface leaf in
this container. If only a reference to a base interface
is requuired, this leaf should not be set.
nodetype: leaf (rw)
type: leafref
description:
Operational state for interface-ref
nodetype: container (ro)
description:
Reference to a base interface. If a reference to a
subinterface is required, this leaf must be specified
to indicate the base interface.
nodetype: leaf (ro)
type: leafref
description:
Reference to a subinterface -- this requires the base
interface to be specified using the interface leaf in
this container. If only a reference to a base interface
is requuired, this leaf should not be set.
nodetype: leaf (ro)
type: leafref
description:
Top-level IPv4 configuration data for the interface
frinx-device-type:
xr
frinx-supported-versions:
interface
frinx-implemented-reader:
io.frinx.unitopo.unit.xr66.interfaces.handler.subifc.ipv4.Ipv4MtuConfigReader
frinx-implemented-writer:
io.frinx.unitopo.unit.xr66.interfaces.handler.subifc.ipv4.Ipv4MtuConfigWriter
nodetype: container (rw)
description:
Controls whether IPv4 is enabled or disabled on this
interface. When IPv4 is enabled, this interface is
connected to an IPv4 stack, and the interface can send
and receive IPv4 packets.
nodetype: leaf (rw)
type: boolean
description:
The size, in octets, of the largest IPv4 packet that the
interface will send and receive.
The server may restrict the allowed values for this leaf,
depending on the interface's type.
If this leaf is not configured, the operationally used MTU
depends on the interface's type.
nodetype: leaf (rw)
type: uint16
units: octets
description:
Top level IPv4 operational state data
nodetype: container (ro)
description:
Controls whether IPv4 is enabled or disabled on this
interface. When IPv4 is enabled, this interface is
connected to an IPv4 stack, and the interface can send
and receive IPv4 packets.
nodetype: leaf (ro)
type: boolean
description:
The size, in octets, of the largest IPv4 packet that the
interface will send and receive.
The server may restrict the allowed values for this leaf,
depending on the interface's type.
If this leaf is not configured, the operationally used MTU
depends on the interface's type.
nodetype: leaf (ro)
type: uint16
units: octets
description:
Parameters for the IPv6 address family.
nodetype: container (rw)
description:
Enclosing container for address list
nodetype: container (rw)
description:
The list of configured IPv6 addresses on the interface.
frinx-device-type:
ironware
frinx-supported-versions:
any
frinx-implemented-reader:
io.frinx.cli.unit.brocade.ifc.handler.subifc.ip6.Ipv6AddressReader
frinx-implemented-reader-details:
IPV6_LOCAL_ADDRESS:
ipv6 address (?<ipv6local>fe80:[^\\s]+)/(?<prefix>[0-9]|[1-9][0-9]|1[0-1][0-9]|12[0-8])
IPV6_UNICAST_ADDRESS:
ipv6 address (?!(fe80:))(?<ipv6unicast>[^\\s]+)/(?<prefix>[0-9]|[1-9][0-9]|1[0-1][0-9]|12[0-8])
SH_INTERFACE_IP:
show running-config interface {$ifcType} {$ifcNumber} | include ipv6
frinx-implemented-writer:
MISSING WRITER
frinx-device-type:
ios
frinx-supported-versions:
12any,15any
frinx-implemented-reader:
io.frinx.cli.unit.ios.ifc.handler.subifc.ip6.Ipv6AddressReader
frinx-implemented-reader-details:
IPV6_LOCAL_ADDRESS:
ipv6 address (?<ipv6local>[^\s]+) link-local
IPV6_UNICAST_ADDRESS:
ipv6 address (?<ipv6unicast>[a-fA-F0-9:]+)/(?<prefix>[\d]+)
SH_INTERFACE_IP:
show running-config interface %s | include ^ ipv6 address
frinx-implemented-writer:
MISSING WRITER
frinx-device-type:
nexus
frinx-supported-versions:
any
frinx-implemented-reader:
io.frinx.cli.unit.nexus.ifc.handler.subifc.ipv6.Ipv6AddressReader
frinx-implemented-reader-details:
INTERFACE_IP_LINE:
ipv6 address (?<ipv6local>\S+)/(?<prefix>\S+)
SH_INTERFACE_IP:
show running-config interface %s | include ^ ipv6 address
frinx-implemented-writer:
MISSING WRITER
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.ifc.handler.subifc.ip6.Ipv6AddressReader
frinx-implemented-reader-details:
IPV6_LOCAL_ADDRESS:
ipv6 address (?<ipv6local>[^\s]+) link-local
IPV6_UNICAST_ADDRESS:
ipv6 address (?<ipv6unicast>[a-fA-F0-9:]+)/(?<prefix>[\d]+)
SH_INTERFACE_IP:
show running-config interface %s | include ^ ipv6 address
frinx-implemented-writer:
MISSING WRITER
nodetype: list (rw)
list keys: [ip]
description:
References the configured IP address
nodetype: leaf (list key) (rw)
type: leafref
description:
Configuration data for each IPv6 address on
the interface
frinx-device-type:
ironware
frinx-supported-versions:
any
frinx-implemented-reader:
io.frinx.cli.unit.brocade.ifc.handler.subifc.ip6.Ipv6ConfigReader
frinx-implemented-reader-details:
IPV6_UNICAST_ADDRESS:
ipv6 address (?!(fe80:))(?<ip>[^\\s]+)/(?<prefix>[0-9]|[1-9][0-9]|1[0-1][0-9]|12[0-8])
frinx-implemented-writer:
MISSING WRITER
frinx-device-type:
ios
frinx-supported-versions:
12any,15any
frinx-implemented-reader:
io.frinx.cli.unit.ios.ifc.handler.subifc.ip6.Ipv6ConfigReader
frinx-implemented-reader-details:
IPV6_UNICAST_ADDRESS:
ipv6 address (?<ip>[a-fA-F0-9:]+)/(?<prefix>[\d]+)
frinx-implemented-writer:
io.frinx.cli.unit.ios.ifc.handler.subifc.ip6.Ipv6ConfigWriter
frinx-implemented-writer-details:
WRITE_TEMPLATE:
configure terminal
interface ${name}
{% if($delete) %}no {% endif %}ipv6 address ${address}
end
frinx-device-type:
nexus
frinx-supported-versions:
any
frinx-implemented-reader:
io.frinx.cli.unit.nexus.ifc.handler.subifc.ipv6.Ipv6ConfigReader
frinx-implemented-reader-details:
INTERFACE_IP_LINE:
ipv6 address (?<ip>\S+)/(?<prefix>\S+)
frinx-implemented-writer:
io.frinx.cli.unit.nexus.ifc.handler.subifc.ipv6.Ipv6ConfigWriter
frinx-implemented-writer-details:
WRITE_TEMPLATE:
interface {$name}
{% if($delete) %}no {% endif %}ipv6 address {$data.ip.value}/{$data.prefix_length}
root
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.ifc.handler.subifc.ip6.Ipv6ConfigReader
frinx-implemented-writer:
io.frinx.cli.unit.iosxr.ifc.handler.subifc.ip6.Ipv6ConfigWriter
frinx-implemented-writer-details:
DELETE_TEMPLATE:
interface {$name}
no ipv6 address
root
MISSING_IP_ADDRESS_MSG:
Missing IP address
MISSING_PREFIX_LENGTH_MSG:
Missing prefix length
WRITE_TEMPLATE:
interface {$name}
ipv6 address {$data.ip.value}/{$data.prefix_length}
root
nodetype: container (rw)
description:
[adapted from IETF IP model RFC 7277]
The IPv6 address on the interface.
nodetype: leaf (rw)
type: inet:ipv6-address-no-zone
description:
[adapted from IETF IP model RFC 7277]
The length of the subnet prefix.
nodetype: leaf (rw)
type: uint8
description:
State data for each IPv6 address on the
interface
nodetype: container (ro)
description:
[adapted from IETF IP model RFC 7277]
The IPv6 address on the interface.
nodetype: leaf (ro)
type: inet:ipv6-address-no-zone
description:
[adapted from IETF IP model RFC 7277]
The length of the subnet prefix.
nodetype: leaf (ro)
type: uint8
description:
[adapted from IETF IP model RFC 7277]
The origin of this address, e.g., static, dhcp, etc.
nodetype: leaf (ro)
type: ip-address-origin
description:
[adapted from IETF IP model RFC 7277]
The status of an address. Most of the states correspond
to states from the IPv6 Stateless Address
Autoconfiguration protocol.
nodetype: leaf (ro)
type: enumeration
description:
Enclosing container for VRRP groups handled by this
IP interface
nodetype: container (rw)
description:
List of VRRP groups, keyed by virtual router id
nodetype: list (rw)
list keys: [virtual-router-id]
description:
References the configured virtual router id for this
VRRP group
nodetype: leaf (list key) (rw)
type: leafref
description:
Configuration data for the VRRP group
nodetype: container (rw)
description:
Set the virtual router id for use by the VRRP group. This
usually also determines the virtual MAC address that is
generated for the VRRP group
nodetype: leaf (rw)
type: uint8
description:
Configure one or more virtual addresses for the
VRRP group
nodetype: leaf-list (rw)
type: inet:ip-address
description:
Specifies the sending VRRP interface's priority
for the virtual router. Higher values equal higher
priority
nodetype: leaf (rw)
type: uint8
description:
When set to true, enables preemption by a higher
priority backup router of a lower priority master router
nodetype: leaf (rw)
type: boolean
description:
Set the delay the higher priority router waits
before preempting
nodetype: leaf (rw)
type: uint16
description:
Configure whether packets destined for
virtual addresses are accepted even when the virtual
address is not owned by the router interface
nodetype: leaf (rw)
type: boolean
description:
Sets the interval between successive VRRP
advertisements -- RFC 5798 defines this as a 12-bit
value expressed as 0.1 seconds, with default 100, i.e.,
1 second. Several implementation express this in units of
seconds
nodetype: leaf (rw)
type: uint16
units: centiseconds
description:
For VRRP on IPv6 interfaces, sets the virtual link local
address
nodetype: leaf (rw)
type: inet:ip-address
description:
Operational state data for the VRRP group
nodetype: container (ro)
description:
Set the virtual router id for use by the VRRP group. This
usually also determines the virtual MAC address that is
generated for the VRRP group
nodetype: leaf (ro)
type: uint8
description:
Configure one or more virtual addresses for the
VRRP group
nodetype: leaf-list (ro)
type: inet:ip-address
description:
Specifies the sending VRRP interface's priority
for the virtual router. Higher values equal higher
priority
nodetype: leaf (ro)
type: uint8
description:
When set to true, enables preemption by a higher
priority backup router of a lower priority master router
nodetype: leaf (ro)
type: boolean
description:
Set the delay the higher priority router waits
before preempting
nodetype: leaf (ro)
type: uint16
description:
Configure whether packets destined for
virtual addresses are accepted even when the virtual
address is not owned by the router interface
nodetype: leaf (ro)
type: boolean
description:
Sets the interval between successive VRRP
advertisements -- RFC 5798 defines this as a 12-bit
value expressed as 0.1 seconds, with default 100, i.e.,
1 second. Several implementation express this in units of
seconds
nodetype: leaf (ro)
type: uint16
units: centiseconds
description:
Operational value of the priority for the
interface in the VRRP group
nodetype: leaf (ro)
type: uint8
description:
For VRRP on IPv6 interfaces, sets the virtual link local
address
nodetype: leaf (ro)
type: inet:ip-address
description:
Top-level container for VRRP interface tracking
nodetype: container (rw)
description:
Configuration data for VRRP interface tracking
nodetype: container (rw)
description:
Sets an interface that should be
tracked for up/down events to dynamically change the
priority state of the VRRP group, and potentially
change the mastership if the tracked interface going
down lowers the priority sufficiently
nodetype: leaf (rw)
type: leafref
description:
Set the value to subtract from priority when
the tracked interface goes down
nodetype: leaf (rw)
type: uint8
description:
Operational state data for VRRP interface tracking
nodetype: container (ro)
description:
Sets an interface that should be
tracked for up/down events to dynamically change the
priority state of the VRRP group, and potentially
change the mastership if the tracked interface going
down lowers the priority sufficiently
nodetype: leaf (ro)
type: leafref
description:
Set the value to subtract from priority when
the tracked interface goes down
nodetype: leaf (ro)
type: uint8
description:
Configuration and operational state parameters relating to
router advertisements.
nodetype: container (rw)
description:
Configuration parameters relating to router advertisements
for IPv6.
frinx-device-type:
nexus
frinx-supported-versions:
any
frinx-implemented-reader:
io.frinx.cli.unit.nexus.ifc.handler.subifc.ipv6.Ipv6AdvertisementConfigReader
frinx-implemented-reader-details:
IPV6_ADVERTISEMENT_ENABLED:
\s*ipv6 nd suppress-ra.*
SH_SINGLE_SUB_INTERFACE_CFG:
show running-config interface %s
frinx-implemented-writer:
io.frinx.cli.unit.nexus.ifc.handler.subifc.ipv6.Ipv6AdvertisementConfigWriter
frinx-implemented-writer-details:
IPV6_ND_SUPPRESS:
ipv6 nd suppress-ra
NO_IPV6_ND_SUPPRESS:
no ipv6 nd suppress-ra
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.ifc.handler.subifc.ip6.Ipv6AdvertisementConfigReader
frinx-implemented-reader-details:
IPV6_ADVERTISEMENT_ENABLED:
\s*ipv6 nd suppress-ra.*
SH_SINGLE_SUB_INTERFACE_CFG:
show running-config interface %s
frinx-implemented-writer:
io.frinx.cli.unit.iosxr.ifc.handler.subifc.ip6.Ipv6AdvertisementConfigWriter
frinx-implemented-writer-details:
IPV6_ND_SUPPRESS:
ipv6 nd suppress-ra
NO_IPV6_ND_SUPPRESS:
no ipv6 nd suppress-ra
nodetype: container (rw)
description:
The interval between periodic router advertisement neighbor
discovery messages sent on this interface expressed in
seconds.
nodetype: leaf (rw)
type: uint32
units: seconds
description:
The lifetime advertised in the router advertisement neighbor
discovery message on this interface.
nodetype: leaf (rw)
type: uint32
units: seconds
description:
When set to true, router advertisement neighbor discovery
messages are not transmitted on this interface.
nodetype: leaf (rw)
type: boolean
description:
Operational state parameters relating to router
advertisements for IPv6.
nodetype: container (ro)
description:
The interval between periodic router advertisement neighbor
discovery messages sent on this interface expressed in
seconds.
nodetype: leaf (ro)
type: uint32
units: seconds
description:
The lifetime advertised in the router advertisement neighbor
discovery message on this interface.
nodetype: leaf (ro)
type: uint32
units: seconds
description:
When set to true, router advertisement neighbor discovery
messages are not transmitted on this interface.
nodetype: leaf (ro)
type: boolean
description:
Enclosing container for list of IPv6 neighbors
nodetype: container (rw)
description:
List of IPv6 neighbors
nodetype: list (rw)
list keys: [ip]
description:
References the configured IP neighbor address
nodetype: leaf (list key) (rw)
type: leafref
description:
Configuration data for each IPv6 address on
the interface
nodetype: container (rw)
description:
[adapted from IETF IP model RFC 7277]
The IPv6 address of the neighbor node.
nodetype: leaf (rw)
type: inet:ipv6-address-no-zone
description:
[adapted from IETF IP model RFC 7277]
The link-layer address of the neighbor node.
nodetype: leaf (rw)
type: yang:phys-address
description:
State data for each IPv6 address on the
interface
nodetype: container (ro)
description:
[adapted from IETF IP model RFC 7277]
The IPv6 address of the neighbor node.
nodetype: leaf (ro)
type: inet:ipv6-address-no-zone
description:
[adapted from IETF IP model RFC 7277]
The link-layer address of the neighbor node.
nodetype: leaf (ro)
type: yang:phys-address
description:
[adapted from IETF IP model RFC 7277]
The origin of this neighbor entry.
nodetype: leaf (ro)
type: neighbor-origin
description:
[adapted from IETF IP model RFC 7277]
Indicates that the neighbor node acts as a router.
nodetype: leaf (ro)
type: empty
description:
[adapted from IETF IP model RFC 7277]
The Neighbor Unreachability Detection state of this
entry.
nodetype: leaf (ro)
type: enumeration
description:
Top-level container for setting unnumbered interfaces.
Includes reference the interface that provides the
address information
nodetype: container (rw)
description:
Configuration data for unnumbered interface
nodetype: container (rw)
description:
Indicates that the subinterface is unnumbered. By default
the subinterface is numbered, i.e., expected to have an
IP address configuration.
nodetype: leaf (rw)
type: boolean
description:
Operational state data for unnumbered interfaces
nodetype: container (ro)
description:
Indicates that the subinterface is unnumbered. By default
the subinterface is numbered, i.e., expected to have an
IP address configuration.
nodetype: leaf (ro)
type: boolean
description:
Reference to an interface or subinterface
nodetype: container (rw)
description:
Configured reference to interface / subinterface
nodetype: container (rw)
description:
Reference to a base interface. If a reference to a
subinterface is required, this leaf must be specified
to indicate the base interface.
nodetype: leaf (rw)
type: leafref
description:
Reference to a subinterface -- this requires the base
interface to be specified using the interface leaf in
this container. If only a reference to a base interface
is requuired, this leaf should not be set.
nodetype: leaf (rw)
type: leafref
description:
Operational state for interface-ref
nodetype: container (ro)
description:
Reference to a base interface. If a reference to a
subinterface is required, this leaf must be specified
to indicate the base interface.
nodetype: leaf (ro)
type: leafref
description:
Reference to a subinterface -- this requires the base
interface to be specified using the interface leaf in
this container. If only a reference to a base interface
is requuired, this leaf should not be set.
nodetype: leaf (ro)
type: leafref
description:
Top-level config data for the IPv6 interface
nodetype: container (rw)
description:
[adapted from IETF IP model RFC 7277]
Controls whether IPv6 is enabled or disabled on this
interface. When IPv6 is enabled, this interface is
connected to an IPv6 stack, and the interface can send
and receive IPv6 packets.
nodetype: leaf (rw)
type: boolean
description:
[adapted from IETF IP model RFC 7277]
The size, in octets, of the largest IPv6 packet that the
interface will send and receive.
The server may restrict the allowed values for this leaf,
depending on the interface's type.
If this leaf is not configured, the operationally used MTU
depends on the interface's type.
nodetype: leaf (rw)
type: uint32
units: octets
description:
[adapted from IETF IP model RFC 7277]
The number of consecutive Neighbor Solicitation messages
sent while performing Duplicate Address Detection on a
tentative address. A value of zero indicates that
Duplicate Address Detection is not performed on
tentative addresses. A value of one indicates a single
transmission with no follow-up retransmissions.
nodetype: leaf (rw)
type: uint32
description:
Top-level operational state data for the IPv6 interface
nodetype: container (ro)
description:
[adapted from IETF IP model RFC 7277]
Controls whether IPv6 is enabled or disabled on this
interface. When IPv6 is enabled, this interface is
connected to an IPv6 stack, and the interface can send
and receive IPv6 packets.
nodetype: leaf (ro)
type: boolean
description:
[adapted from IETF IP model RFC 7277]
The size, in octets, of the largest IPv6 packet that the
interface will send and receive.
The server may restrict the allowed values for this leaf,
depending on the interface's type.
If this leaf is not configured, the operationally used MTU
depends on the interface's type.
nodetype: leaf (ro)
type: uint32
units: octets
description:
[adapted from IETF IP model RFC 7277]
The number of consecutive Neighbor Solicitation messages
sent while performing Duplicate Address Detection on a
tentative address. A value of zero indicates that
Duplicate Address Detection is not performed on
tentative addresses. A value of one indicates a single
transmission with no follow-up retransmissions.
nodetype: leaf (ro)
type: uint32
description:
Top-level container for IPv6 autoconf
nodetype: container (rw)
description:
[adapted from IETF IP model RFC 7277]
Parameters to control the autoconfiguration of IPv6
addresses, as described in RFC 4862.
nodetype: container (rw)
description:
[adapted from IETF IP model RFC 7277]
If enabled, the host creates global addresses as
described in RFC 4862.
nodetype: leaf (rw)
type: boolean
description:
[adapted from IETF IP model RFC 7277]
If enabled, the host creates temporary addresses as
described in RFC 4941.
nodetype: leaf (rw)
type: boolean
description:
[adapted from IETF IP model RFC 7277]
The time period during which the temporary address
is valid.
nodetype: leaf (rw)
type: uint32
units: seconds
description:
[adapted from IETF IP model RFC 7277]
The time period during which the temporary address is
preferred.
nodetype: leaf (rw)
type: uint32
units: seconds
description:
Operational state data
nodetype: container (ro)
description:
[adapted from IETF IP model RFC 7277]
If enabled, the host creates global addresses as
described in RFC 4862.
nodetype: leaf (ro)
type: boolean
description:
[adapted from IETF IP model RFC 7277]
If enabled, the host creates temporary addresses as
described in RFC 4941.
nodetype: leaf (ro)
type: boolean
description:
[adapted from IETF IP model RFC 7277]
The time period during which the temporary address
is valid.
nodetype: leaf (ro)
type: uint32
units: seconds
description:
[adapted from IETF IP model RFC 7277]
The time period during which the temporary address is
preferred.
nodetype: leaf (ro)
type: uint32
units: seconds
description:
Configure Address Resolution Protocol
nodetype: container (rw)
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.ifc.handler.subifc.SubinterfaceArpConfigReader
frinx-implemented-reader-details:
CACHE_TIMEOUT_LINE:
arp timeout (?<timeout>\d+)
frinx-implemented-writer:
io.frinx.cli.unit.iosxr.ifc.handler.subifc.SubinterfaceArpConfigWriter
frinx-implemented-writer-details:
CREATE_TEMPLATE:
interface {$name}
arp timeout {$config.cache_timeout}
root
DELETE_TEMPLATE:
interface {$name}
no arp timeout
root
nodetype: container (rw)
description:
The number of seconds that an entry remains in the ARP cache
nodetype: leaf (rw)
type: uint32
units: seconds
description:
Enclosing container for statistics interface-specific
data.
frinx-device-type:
xr
frinx-supported-versions:
interface
nodetype: container (rw)
description:
Configuration parameters for statistics
frinx-device-type:
xr
frinx-supported-versions:
interface
frinx-implemented-reader:
io.frinx.unitopo.unit.xr66.interfaces.handler.subifc.SubinterfaceStatisticsConfigReader
frinx-implemented-writer:
io.frinx.unitopo.unit.xr66.interfaces.handler.subifc.SubinterfaceStatisticsConfigWriter
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.ifc.handler.subifc.SubinterfaceStatisticsConfigReader
frinx-implemented-reader-details:
LOAD_INTERVAL:
\s*load-interval (?<loadInterval>\d+)\s*
frinx-implemented-writer:
io.frinx.cli.unit.iosxr.ifc.handler.subifc.SubinterfaceStatisticsConfigWriter
frinx-implemented-writer-details:
CREATE_TEMPLATE:
interface {$name}
load-interval {$config.load_interval}
root
DELETE_TEMPLATE:
interface {$name}
no load-interval
root
nodetype: container (rw)
description:
Specify interval for load calculation for an
interface.
0 disables load calculation, otherwise some
multiple of 30 between 30 and 600.
nodetype: leaf (rw)
type: uint32
description:
State variables for statistics
nodetype: container (ro)
description:
Specify interval for load calculation for an
interface.
0 disables load calculation, otherwise some
multiple of 30 between 30 and 600.
nodetype: leaf (ro)
type: uint32
description:
Top-level container for hold-time settings to enable
dampening advertisements of interface transitions.
frinx-device-type:
xr
frinx-supported-versions:
interface
nodetype: container (rw)
description:
Configuration data for interface hold-time settings.
frinx-device-type:
xr
frinx-supported-versions:
interface
frinx-implemented-reader:
io.frinx.unitopo.unit.xr66.interfaces.handler.subifc.holdtime.HoldTimeConfigReader
frinx-implemented-writer:
io.frinx.unitopo.unit.xr66.interfaces.handler.subifc.holdtime.HoldTimeConfigWriter
nodetype: container (rw)
description:
Dampens advertisement when the interface
transitions from down to up. A zero value means dampening
is turned off, i.e., immediate notification.
nodetype: leaf (rw)
type: uint32
units: milliseconds
description:
Dampens advertisement when the interface transitions from
up to down. A zero value means dampening is turned off,
i.e., immediate notification.
nodetype: leaf (rw)
type: uint32
units: milliseconds
description:
Operational state data for interface hold-time.
nodetype: container (ro)
description:
Dampens advertisement when the interface
transitions from down to up. A zero value means dampening
is turned off, i.e., immediate notification.
nodetype: leaf (ro)
type: uint32
units: milliseconds
description:
Dampens advertisement when the interface transitions from
up to down. A zero value means dampening is turned off,
i.e., immediate notification.
nodetype: leaf (ro)
type: uint32
units: milliseconds
description:
CFM interface configuration
nodetype: container (rw)
description:
Configuration for ethernet CFM
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.ifc.handler.subifc.cfm.CfmConfigReader
frinx-implemented-reader-details:
CFM_ENABLED:
ethernet cfm
frinx-implemented-writer:
io.frinx.cli.unit.iosxr.ifc.handler.subifc.cfm.CfmConfigWriter
frinx-implemented-writer-details:
CREATE_TEMPLATE:
interface {$name}
ethernet cfm
root
DELETE_TEMPLATE:
interface {$name}
no ethernet cfm
root
nodetype: container (rw)
description:
Is ethernet CFM enabled
nodetype: leaf (rw)
type: boolean
description:
Domain-specific interface configuration
nodetype: container (rw)
description:
Configuration for a particular Maintenance Domain
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.ifc.handler.subifc.cfm.CfmDomainReader
frinx-implemented-reader-details:
MEP_DOMAIN_LINE:
mep domain (?<domain>\S+) .*
SH_INTERFACE_CFM:
show running-config interface %s ethernet cfm
SQUASHED_CFM_DOMAIN_LINE:
^domain (?<domain>\S+) service (?<service>\S+) mep-id (?<mepid>\d+) (\s*cos (?<cos>\d+))?.*
frinx-implemented-writer:
io.frinx.cli.unit.iosxr.ifc.handler.subifc.cfm.CfmDomainWriter
frinx-implemented-writer-details:
CREATE_TEMPLATE:
interface {$ifc}
ethernet cfm
mep domain {$domain.domain_name} service {$mep.ma_name} mep-id {$mep.mep_id}
{% if $mep.cos %}cos {$mep.cos}
{% else %}no cos
{% endif %}root
DELETE_TEMPLATE:
interface {$ifc}
ethernet cfm
no mep domain {$domain.domain_name}
root
nodetype: list (rw)
list keys: [domain-name]
description:
Maintenance Domain
nodetype: leaf (list key) (rw)
type: leafref
description:
Configuration for Maintenance Domain
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.ifc.handler.subifc.cfm.CfmDomainReader
frinx-implemented-reader-details:
MEP_DOMAIN_LINE:
mep domain (?<domain>\S+) .*
SH_INTERFACE_CFM:
show running-config interface %s ethernet cfm
SQUASHED_CFM_DOMAIN_LINE:
^domain (?<domain>\S+) service (?<service>\S+) mep-id (?<mepid>\d+) (\s*cos (?<cos>\d+))?.*
frinx-implemented-writer:
io.frinx.cli.unit.iosxr.ifc.handler.subifc.cfm.CfmDomainWriter
frinx-implemented-writer-details:
CREATE_TEMPLATE:
interface {$ifc}
ethernet cfm
mep domain {$domain.domain_name} service {$mep.ma_name} mep-id {$mep.mep_id}
{% if $mep.cos %}cos {$mep.cos}
{% else %}no cos
{% endif %}root
DELETE_TEMPLATE:
interface {$ifc}
ethernet cfm
no mep domain {$domain.domain_name}
root
nodetype: container (rw)
description:
Maintenance Domain
nodetype: leaf (rw)
type: string
description:
MEP configuration
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.ifc.handler.subifc.cfm.CfmDomainReader
frinx-implemented-reader-details:
MEP_DOMAIN_LINE:
mep domain (?<domain>\S+) .*
SH_INTERFACE_CFM:
show running-config interface %s ethernet cfm
SQUASHED_CFM_DOMAIN_LINE:
^domain (?<domain>\S+) service (?<service>\S+) mep-id (?<mepid>\d+) (\s*cos (?<cos>\d+))?.*
frinx-implemented-writer:
io.frinx.cli.unit.iosxr.ifc.handler.subifc.cfm.CfmDomainWriter
frinx-implemented-writer-details:
CREATE_TEMPLATE:
interface {$ifc}
ethernet cfm
mep domain {$domain.domain_name} service {$mep.ma_name} mep-id {$mep.mep_id}
{% if $mep.cos %}cos {$mep.cos}
{% else %}no cos
{% endif %}root
DELETE_TEMPLATE:
interface {$ifc}
ethernet cfm
no mep domain {$domain.domain_name}
root
nodetype: container (rw)
description:
configuration for MEP
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.ifc.handler.subifc.cfm.CfmDomainReader
frinx-implemented-reader-details:
MEP_DOMAIN_LINE:
mep domain (?<domain>\S+) .*
SH_INTERFACE_CFM:
show running-config interface %s ethernet cfm
SQUASHED_CFM_DOMAIN_LINE:
^domain (?<domain>\S+) service (?<service>\S+) mep-id (?<mepid>\d+) (\s*cos (?<cos>\d+))?.*
frinx-implemented-writer:
io.frinx.cli.unit.iosxr.ifc.handler.subifc.cfm.CfmDomainWriter
frinx-implemented-writer-details:
CREATE_TEMPLATE:
interface {$ifc}
ethernet cfm
mep domain {$domain.domain_name} service {$mep.ma_name} mep-id {$mep.mep_id}
{% if $mep.cos %}cos {$mep.cos}
{% else %}no cos
{% endif %}root
DELETE_TEMPLATE:
interface {$ifc}
ethernet cfm
no mep domain {$domain.domain_name}
root
nodetype: container (rw)
description:
MA name
nodetype: leaf (rw)
type: string
description:
MEP ID
nodetype: leaf (rw)
type: uint16
description:
Ethernet CoS
nodetype: leaf (rw)
type: uint8
description:
Top-level container for ethernet configuration
and state
frinx-device-type:
xr
frinx-supported-versions:
interface
frinx-device-type:
junos
frinx-supported-versions:
173
frinx-device-type:
nos
frinx-supported-versions:
any
nodetype: container (rw)
description:
Configuration data for ethernet interfaces
frinx-device-type:
ironware
frinx-supported-versions:
any
frinx-implemented-reader:
io.frinx.cli.unit.brocade.ifc.handler.ethernet.EthernetConfigReader
frinx-implemented-reader-details:
GIG_DEFAULT:
gig-default neg-off
GIG_DEFAULT_AUTO:
gig-default auto-gig
frinx-implemented-writer:
io.frinx.cli.unit.brocade.ifc.handler.ethernet.EthernetConfigWriter
frinx-implemented-writer-details:
WRITE_TEMPLATE:
{% if ($before == null) %}{% if ($autoNegotiate == true) %}configure terminal
interface {$ifcName}
gig-default auto-gig
end{% endif %}{% if ($autoNegotiate == false) %}configure terminal
interface {$ifcName}
gig-default neg-off
end{% endif %}{% endif %}{% if ($before == true) %}{% if ($autoNegotiate == false) %}configure terminal
interface {$ifcName}
gig-default neg-off
end{% endif %}{% if ($autoNegotiate == null) %}configure terminal
interface {$ifcName}
no gig-default auto-gig
end{% endif %}{% endif %}{% if ($before == false) %}{% if ($autoNegotiate == true) %}configure terminal
interface {$ifcName}
gig-default auto-gig
end{% endif %}{% if ($autoNegotiate == null) %}configure terminal
interface {$ifcName}
no gig-default neg-off
end{% endif %}{% endif %}
frinx-device-type:
xr
frinx-supported-versions:
interface
frinx-implemented-reader:
io.frinx.unitopo.unit.xr66.interfaces.handler.ethernet.EthernetConfigReader
frinx-implemented-writer:
io.frinx.unitopo.unit.xr66.interfaces.handler.ethernet.EthernetConfigWriter
frinx-device-type:
nos
frinx-supported-versions:
any
frinx-implemented-reader:
io.frinx.cli.unit.dasan.ifc.handler.ethernet.EthernetConfigReader
frinx-implemented-writer:
io.frinx.cli.unit.dasan.ifc.handler.ethernet.EthernetConfigWriter
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.ifc.handler.ethernet.EthernetConfigReader
frinx-implemented-reader-details:
AGGREGATE_IFC_NAME:
Bundle-Ether
BUNDLE_ID_LINE:
\s*bundle id (?<id>\d+).*
LACP_MODE_LINE:
\s*bundle id (?<id>\d+) mode (?<mode>active|passive).*
LACP_PERIOD_LINE:
\s*lacp period short.*
frinx-implemented-writer:
io.frinx.cli.unit.iosxr.ifc.handler.ethernet.EthernetConfigWriter
frinx-implemented-writer-details:
IFC_ETHERNET_CONFIG_TEMPLATE:
interface {$ifc_name}
{% if ($bundle_id) %}bundle id {$bundle_id} mode{% if ($lacp_aug.lacp_mode == ACTIVE) %} active{% elseIf ($lacp_aug.lacp_mode == PASSIVE) %} passive{% else %} on{% endif %}
{% else %}no bundle id
{% endif %}{% if ($lacp_aug.interval == FAST) %}lacp period short{% else %}no lacp period short{% endif %}
root
LACP_OPERATION_MODE_TEMPLATE:
mode{% if ($lacp_aug.lacp_mode == ACTIVE) %} active{% elseIf ($lacp_aug.lacp_mode == PASSIVE) %} passive{% else %} on{% endif %}
LACP_PERIOD_TEMPLATE:
{% if ($lacp_aug.interval == FAST) %}lacp period short{% else %}no lacp period short{% endif %}
frinx-device-type:
junos
frinx-supported-versions:
173
frinx-device-type:
nexus
frinx-supported-versions:
any
frinx-implemented-reader:
io.frinx.cli.unit.nexus.ifc.handler.ethernet.EthernetConfigReader
frinx-implemented-reader-details:
AGGREGATE_IFC_NAME:
Ethernet
CHANNEL_GROUP_LINE:
\s*channel-group (?<aggregate>\d+).*
LACP_MODE_LINE:
\s*channel-group (?<aggregate>\d+) mode (?<mode>active|passive).*
frinx-implemented-writer:
io.frinx.cli.unit.nexus.ifc.handler.ethernet.EthernetConfigWriter
frinx-implemented-writer-details:
IFC_ETHERNET_CONFIG_TEMPLATE:
interface {$ifc_name}
{% if ($aggregate_id) %}channel-group {$aggregate_id}{% if ($lacp_aug.lacp_mode) %} mode{% if ($lacp_aug.lacp_mode == ACTIVE) %} active{% elseIf ($lacp_aug.lacp_mode == PASSIVE) %} passive{% endif %}{% endif %}
{% else %}no channel-group
{% endif %}root
LACP_OPERATION_MODE_TEMPLATE:
mode{% if ($lacp_aug.lacp_mode == ACTIVE) %} active{% elseIf ($lacp_aug.lacp_mode == PASSIVE) %} passive{% endif %}
nodetype: container (rw)
description:
Assigns a MAC address to the Ethernet interface. If not
specified, the corresponding operational state leaf is
expected to show the system-assigned MAC address.
nodetype: leaf (rw)
type: yang:mac-address
description:
Set to TRUE to request the interface to auto-negotiate
transmission parameters with its peer interface. When
set to FALSE, the transmission parameters are specified
manually.
nodetype: leaf (rw)
type: boolean
description:
When auto-negotiate is TRUE, this optionally sets the
duplex mode that will be advertised to the peer. If
unspecified, the interface should negotiate the duplex mode
directly (typically full-duplex). When auto-negotiate is
FALSE, this sets the duplex mode on the interface directly.
nodetype: leaf (rw)
type: enumeration
description:
When auto-negotiate is TRUE, this optionally sets the
port-speed mode that will be advertised to the peer for
negotiation. If unspecified, it is expected that the
interface will select the highest speed available based on
negotiation. When auto-negotiate is set to FALSE, sets the
link speed to a fixed value -- supported values are defined
by ETHERNET_SPEED identities
nodetype: leaf (rw)
type: identityref
description:
Enable or disable flow control for this interface.
Ethernet flow control is a mechanism by which a receiver
may send PAUSE frames to a sender to stop transmission for
a specified time.
This setting should override auto-negotiated flow control
settings. If left unspecified, and auto-negotiate is TRUE,
flow control mode is negotiated with the peer interface.
nodetype: leaf (rw)
type: boolean
description:
Specify the logical aggregate interface to which
this interface belongs
nodetype: leaf (rw)
type: leafref
description:
Member port of LACP has key value. All member ports in one aggregator have same key
values. To make the aggregator consisted of specified member ports, configure the
different key value with the key value of another port.
nodetype: leaf (rw)
type: uint16
description:
Set the period between LACP messages -- uses
the lacp-period-type enumeration.
nodetype: leaf (rw)
type: oc-lacp:lacp-period-type
description:
ACTIVE is to initiate the transmission of LACP packets.
PASSIVE is to wait for peer to initiate the transmission of
LACP packets.
nodetype: leaf (rw)
type: oc-lacp:lacp-activity-type
description:
State variables for Ethernet interfaces
nodetype: container (ro)
description:
Assigns a MAC address to the Ethernet interface. If not
specified, the corresponding operational state leaf is
expected to show the system-assigned MAC address.
nodetype: leaf (ro)
type: yang:mac-address
description:
Set to TRUE to request the interface to auto-negotiate
transmission parameters with its peer interface. When
set to FALSE, the transmission parameters are specified
manually.
nodetype: leaf (ro)
type: boolean
description:
When auto-negotiate is TRUE, this optionally sets the
duplex mode that will be advertised to the peer. If
unspecified, the interface should negotiate the duplex mode
directly (typically full-duplex). When auto-negotiate is
FALSE, this sets the duplex mode on the interface directly.
nodetype: leaf (ro)
type: enumeration
description:
When auto-negotiate is TRUE, this optionally sets the
port-speed mode that will be advertised to the peer for
negotiation. If unspecified, it is expected that the
interface will select the highest speed available based on
negotiation. When auto-negotiate is set to FALSE, sets the
link speed to a fixed value -- supported values are defined
by ETHERNET_SPEED identities
nodetype: leaf (ro)
type: identityref
description:
Enable or disable flow control for this interface.
Ethernet flow control is a mechanism by which a receiver
may send PAUSE frames to a sender to stop transmission for
a specified time.
This setting should override auto-negotiated flow control
settings. If left unspecified, and auto-negotiate is TRUE,
flow control mode is negotiated with the peer interface.
nodetype: leaf (ro)
type: boolean
description:
Represenets the 'burned-in', or system-assigned, MAC
address for the Ethernet interface.
nodetype: leaf (ro)
type: yang:mac-address
description:
Reports the effective speed of the interface, e.g., the
negotiated speed if auto-negotiate is enabled
nodetype: leaf (ro)
type: uint32
units: Mbps
description:
When auto-negotiate is set to TRUE, and the interface has
completed auto-negotiation with the remote peer, this value
shows the duplex mode that has been negotiated.
nodetype: leaf (ro)
type: enumeration
description:
When auto-negotiate is set to TRUE, and the interface has
completed auto-negotiation with the remote peer, this value
shows the interface speed that has been negotiated.
nodetype: leaf (ro)
type: identityref
description:
Ethernet interface counters
nodetype: container (ro)
description:
MAC layer control frames received on the interface
nodetype: leaf (ro)
type: yang:counter64
description:
MAC layer PAUSE frames received on the interface
nodetype: leaf (ro)
type: yang:counter64
description:
Number of oversize frames received on the interface
nodetype: leaf (ro)
type: yang:counter64
description:
Number of jabber frames received on the
interface. Jabber frames are typically defined as oversize
frames which also have a bad CRC. Implementations may use
slightly different definitions of what constitutes a jabber
frame. Often indicative of a NIC hardware problem.
nodetype: leaf (ro)
type: yang:counter64
description:
Number of fragment frames received on the interface.
nodetype: leaf (ro)
type: yang:counter64
description:
Number of 802.1q tagged frames received on the interface
nodetype: leaf (ro)
type: yang:counter64
description:
Number of receive error events due to FCS/CRC check
failure
nodetype: leaf (ro)
type: yang:counter64
description:
MAC layer control frames sent on the interface
nodetype: leaf (ro)
type: yang:counter64
description:
MAC layer PAUSE frames sent on the interface
nodetype: leaf (ro)
type: yang:counter64
description:
Number of 802.1q tagged frames sent on the interface
nodetype: leaf (ro)
type: yang:counter64
description:
Specify the logical aggregate interface to which
this interface belongs
nodetype: leaf (ro)
type: leafref
description:
Member port of LACP has key value. All member ports in one aggregator have same key
values. To make the aggregator consisted of specified member ports, configure the
different key value with the key value of another port.
nodetype: leaf (ro)
type: uint16
description:
Enclosing container for VLAN interface-specific
data on Ethernet interfaces. These are for standard
L2, switched-style VLANs.
frinx-device-type:
nos
frinx-supported-versions:
any
nodetype: container (rw)
description:
Configuration parameters for VLANs
frinx-device-type:
ironware
frinx-supported-versions:
any
frinx-implemented-reader:
io.frinx.cli.unit.brocade.ifc.handler.switchedvlan.SwitchedVlanConfigReader
frinx-implemented-writer:
io.frinx.cli.unit.brocade.ifc.handler.switchedvlan.SwitchedVlanConfigWriter
frinx-device-type:
nos
frinx-supported-versions:
any
frinx-implemented-reader:
io.frinx.cli.unit.dasan.ifc.handler.ethernet.vlanmember.PhysicalPortVlanMemberConfigReader
frinx-implemented-reader-details:
SHOW_VLAN_ADD:
show running-config bridge | include ^ vlan add
VLAN_ADD_LINE_PATTERN:
vlan add (?<ids>\S+)\s+(?<ports>\S+)\s+(?<vlanmode>(un)?tagged)
frinx-implemented-writer:
io.frinx.cli.unit.dasan.ifc.handler.ethernet.vlanmember.PhysicalPortVlanMemberConfigWriter
frinx-implemented-writer-details:
ADD_NATIVE_CMD_FORMAT:
vlan add %s %s untagged
ADD_TRUNK_CMD_FORMAT:
vlan add %s %s tagged
DELETE_CMD_FORMAT:
vlan del %s %s
nodetype: container (rw)
description:
Set the interface to access or trunk mode for
VLANs
nodetype: leaf (rw)
type: oc-vlan-types:vlan-mode-type
description:
Set the native VLAN id for untagged frames arriving on
a trunk interface. Tagged frames sent on an interface
configured with a native VLAN should have their tags
stripped prior to transmission. This configuration is only
valid on a trunk interface.
nodetype: leaf (rw)
type: oc-vlan-types:vlan-id
description:
Assign the access vlan to the access port.
nodetype: leaf (rw)
type: oc-vlan-types:vlan-id
description:
Specify VLANs, or ranges thereof, that the interface may
carry when in trunk mode. If not specified, all VLANs are
allowed on the interface. Ranges are specified in the form
x..y, where x
nodetype: leaf-list (rw)
type: union
type: oc-vlan-types:vlan-id
type: oc-vlan-types:vlan-range
description:
State variables for VLANs
nodetype: container (ro)
description:
Set the interface to access or trunk mode for
VLANs
nodetype: leaf (ro)
type: oc-vlan-types:vlan-mode-type
description:
Set the native VLAN id for untagged frames arriving on
a trunk interface. Tagged frames sent on an interface
configured with a native VLAN should have their tags
stripped prior to transmission. This configuration is only
valid on a trunk interface.
nodetype: leaf (ro)
type: oc-vlan-types:vlan-id
description:
Assign the access vlan to the access port.
nodetype: leaf (ro)
type: oc-vlan-types:vlan-id
description:
Specify VLANs, or ranges thereof, that the interface may
carry when in trunk mode. If not specified, all VLANs are
allowed on the interface. Ranges are specified in the form
x..y, where x
nodetype: leaf-list (ro)
type: union
type: oc-vlan-types:vlan-id
type: oc-vlan-types:vlan-range
description:
Options for logical interfaces representing
aggregates
frinx-device-type:
xr
frinx-supported-versions:
interface
frinx-device-type:
junos
frinx-supported-versions:
173
frinx-device-type:
nos
frinx-supported-versions:
any
nodetype: container (rw)
description:
Configuration variables for logical aggregate /
LAG interfaces
frinx-device-type:
xr
frinx-supported-versions:
interface
frinx-implemented-reader:
io.frinx.unitopo.unit.xr66.interfaces.handler.aggregate.AggregateConfigReader
frinx-implemented-writer:
io.frinx.unitopo.unit.xr66.interfaces.handler.aggregate.AggregateConfigWriter
frinx-device-type:
junos
frinx-supported-versions:
173
frinx-implemented-reader:
io.frinx.unitopo.unit.junos.interfaces.handler.lag.aggregate.InterfaceAggregationConfigReader
frinx-implemented-writer:
io.frinx.unitopo.unit.junos.interfaces.handler.lag.aggregate.InterfaceAggregationConfigWriter
frinx-device-type:
nos
frinx-supported-versions:
any
frinx-implemented-reader:
io.frinx.cli.unit.dasan.ifc.handler.lacp.BundleEtherLacpConfigReader
frinx-implemented-writer:
io.frinx.cli.unit.dasan.ifc.handler.lacp.BundleEtherLacpConfigWriter
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.ifc.handler.aggregate.AggregateConfigReader
frinx-implemented-reader-details:
BUNDLE_MINIMUM_LINKS_LINE:
\s*bundle minimum-active links (?<minLinks>\d+).*
frinx-implemented-writer:
io.frinx.cli.unit.iosxr.ifc.handler.aggregate.AggregateConfigWriter
nodetype: container (rw)
description:
Sets the type of LAG, i.e., how it is
configured / maintained
nodetype: leaf (rw)
type: aggregation-type
description:
Specifies the mininum number of member
interfaces that must be active for the aggregate interface
to be available
nodetype: leaf (rw)
type: uint16
description:
Assigns a MAC address to the Ethernet interface. If not
specified, the corresponding operational state leaf is
expected to show the system-assigned MAC address.
nodetype: leaf (rw)
type: yang:mac-address
description:
The MAC address portion of the node's System ID. This is
combined with the system priority to construct the 8-octet
system-id
nodetype: leaf (rw)
type: yang:mac-address
description:
Link speed of individual interface that joins the AE
nodetype: leaf (rw)
type: enumeration
description:
Operational state variables for logical
aggregate / LAG interfaces
nodetype: container (ro)
description:
Sets the type of LAG, i.e., how it is
configured / maintained
nodetype: leaf (ro)
type: aggregation-type
description:
Specifies the mininum number of member
interfaces that must be active for the aggregate interface
to be available
nodetype: leaf (ro)
type: uint16
description:
Reports effective speed of the aggregate interface,
based on speed of active member interfaces
nodetype: leaf (ro)
type: uint32
units: Mbps
description:
List of current member interfaces for the aggregate,
expressed as references to existing interfaces
nodetype: leaf-list (ro)
type: oc-if:base-interface-ref
description:
Enclosing container for BFD interface-ipv4-specific
data.
frinx-device-type:
junos
frinx-supported-versions:
173
nodetype: container (rw)
description:
Configuration parameters for BFD ipv4
frinx-device-type:
junos
frinx-supported-versions:
173
frinx-implemented-reader:
io.frinx.unitopo.unit.junos.interfaces.handler.lag.aggregate.InterfaceAggregationBfdConfigReader
frinx-implemented-writer:
io.frinx.unitopo.unit.junos.interfaces.handler.lag.aggregate.InterfaceAggregationBfdConfigWriter
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.ifc.handler.aggregate.bfd.BfdConfigReader
frinx-implemented-reader-details:
BFD_DESTINATION:
\s*bfd address-family ipv4 destination (?<destination>[\d.]+)\s*
BFD_FAST_DETECT:
\s*bfd address-family ipv4 fast-detect\s*
BFD_MINIMUM_INTERVAL:
\s*bfd address-family ipv4 minimum-interval (?<minInterval>\d+)\s*
BFD_MODE_ITEF:
\s*bfd mode ietf\s*
BFD_MULTIPLIER:
\s*bfd address-family ipv4 multiplier (?<multiplier>\d+)\s*
frinx-implemented-writer:
io.frinx.cli.unit.iosxr.ifc.handler.aggregate.bfd.BfdConfigWriter
nodetype: container (rw)
description:
Ipv4 source address for BFD sessions.
By default, IP address of interface with BFD session is used.
nodetype: leaf (rw)
type: inet:ipv4-address
description:
Ipv4 destination address for BFD sessions
nodetype: leaf (rw)
type: inet:ipv4-address
description:
Detection multiplier for BFD sessions
nodetype: leaf (rw)
type: uint32
description:
Interval for sending BFD packets (in milliseconds)
nodetype: leaf (rw)
type: uint32
units: milliseconds
description:
Interval for receiving BFD packets (in milliseconds)
nodetype: leaf (rw)
type: uint32
units: milliseconds
description:
State variables for BFD
nodetype: container (ro)
description:
Ipv4 source address for BFD sessions.
By default, IP address of interface with BFD session is used.
nodetype: leaf (ro)
type: inet:ipv4-address
description:
Ipv4 destination address for BFD sessions
nodetype: leaf (ro)
type: inet:ipv4-address
description:
Detection multiplier for BFD sessions
nodetype: leaf (ro)
type: uint32
description:
Interval for sending BFD packets (in milliseconds)
nodetype: leaf (ro)
type: uint32
units: milliseconds
description:
Interval for receiving BFD packets (in milliseconds)
nodetype: leaf (ro)
type: uint32
units: milliseconds
description:
Enclosing container for BFD interface-ipv6-specific
data.
nodetype: container (rw)
description:
Configuration parameters for BFD ipv6
nodetype: container (rw)
description:
Ipv6 destination address for BFD sessions
nodetype: leaf (rw)
type: inet:ipv6-address
description:
Detection multiplier for BFD sessions
nodetype: leaf (rw)
type: uint32
description:
Interval for sending BFD packets (in milliseconds)
nodetype: leaf (rw)
type: uint32
units: milliseconds
description:
Enclosing container for VLAN interface-specific
data on Ethernet interfaces. These are for standard
L2, switched-style VLANs.
frinx-device-type:
nos
frinx-supported-versions:
any
nodetype: container (rw)
description:
Configuration parameters for VLANs
frinx-device-type:
nos
frinx-supported-versions:
any
frinx-implemented-reader:
io.frinx.cli.unit.dasan.ifc.handler.ethernet.vlanmember.TrunkPortVlanMemberConfigReader
frinx-implemented-reader-details:
PORT_NAME_PATTERN:
Trunk(?<portid>.*)$
SHOW_VLAN_ADD:
show running-config bridge | include ^ vlan add
VLAN_ADD_LINE_PATTERN:
vlan add (?<ids>\S+)\s+(?<ports>\S+)\s+(?<vlanmode>(un)?tagged)
frinx-implemented-writer:
io.frinx.cli.unit.dasan.ifc.handler.ethernet.vlanmember.TrunkPortVlanMemberConfigWriter
frinx-implemented-writer-details:
ADD_NATIVE_CMD_FORMAT:
vlan add %s t/%s untagged
ADD_TRUNK_CMD_FORMAT:
vlan add %s t/%s tagged
DELETE_CMD_FORMAT:
vlan del %s t/%s
nodetype: container (rw)
description:
Set the interface to access or trunk mode for
VLANs
nodetype: leaf (rw)
type: oc-vlan-types:vlan-mode-type
description:
Set the native VLAN id for untagged frames arriving on
a trunk interface. Tagged frames sent on an interface
configured with a native VLAN should have their tags
stripped prior to transmission. This configuration is only
valid on a trunk interface.
nodetype: leaf (rw)
type: oc-vlan-types:vlan-id
description:
Assign the access vlan to the access port.
nodetype: leaf (rw)
type: oc-vlan-types:vlan-id
description:
Specify VLANs, or ranges thereof, that the interface may
carry when in trunk mode. If not specified, all VLANs are
allowed on the interface. Ranges are specified in the form
x..y, where x
nodetype: leaf-list (rw)
type: union
type: oc-vlan-types:vlan-id
type: oc-vlan-types:vlan-range
description:
State variables for VLANs
nodetype: container (ro)
description:
Set the interface to access or trunk mode for
VLANs
nodetype: leaf (ro)
type: oc-vlan-types:vlan-mode-type
description:
Set the native VLAN id for untagged frames arriving on
a trunk interface. Tagged frames sent on an interface
configured with a native VLAN should have their tags
stripped prior to transmission. This configuration is only
valid on a trunk interface.
nodetype: leaf (ro)
type: oc-vlan-types:vlan-id
description:
Assign the access vlan to the access port.
nodetype: leaf (ro)
type: oc-vlan-types:vlan-id
description:
Specify VLANs, or ranges thereof, that the interface may
carry when in trunk mode. If not specified, all VLANs are
allowed on the interface. Ranges are specified in the form
x..y, where x
nodetype: leaf-list (ro)
type: union
type: oc-vlan-types:vlan-id
type: oc-vlan-types:vlan-range
description:
Top-level container for routed vlan interfaces. These
logical interfaces are also known as SVI (switched virtual
interface), IRB (integrated routing and bridging), RVI
(routed VLAN interface)
nodetype: container (rw)
description:
Configuration data for routed vlan interfaces
frinx-device-type:
ironware
frinx-supported-versions:
any
frinx-implemented-reader:
io.frinx.cli.unit.brocade.ifc.handler.switchedvlan.def.RoutedVlanConfigReader
frinx-implemented-reader-details:
ROUTER_IFC:
ve \S+
frinx-implemented-writer:
io.frinx.cli.unit.brocade.ifc.handler.switchedvlan.def.RoutedVlanConfigWriter
frinx-implemented-writer-details:
WRITE_TEMPLATE:
configure terminal
{$data|update(vlan,vlan `$data.vlan.uint16`
router-interface `$ifc`
,vlan `$before.vlan.uint16`
no router-interface `$ifc`
,true)}end
nodetype: container (rw)
description:
References the VLAN for which this IP interface
provides routing services -- similar to a switch virtual
interface (SVI), or integrated routing and bridging interface
(IRB) in some implementations.
nodetype: leaf (rw)
type: union
type: uint16
type: string
description:
Operational state data
nodetype: container (ro)
description:
References the VLAN for which this IP interface
provides routing services -- similar to a switch virtual
interface (SVI), or integrated routing and bridging interface
(IRB) in some implementations.
nodetype: leaf (ro)
type: union
type: uint16
type: string
description:
Parameters for the IPv4 address family.
nodetype: container (rw)
description:
Enclosing container for address list
nodetype: container (rw)
description:
The list of configured IPv4 addresses on the interface.
nodetype: list (rw)
list keys: [ip]
description:
References the configured IP address
nodetype: leaf (list key) (rw)
type: leafref
description:
Configuration data for each configured IPv4
address on the interface
nodetype: container (rw)
description:
[adapted from IETF IP model RFC 7277]
The IPv4 address on the interface.
nodetype: leaf (rw)
type: inet:ipv4-address-no-zone
description:
[adapted from IETF IP model RFC 7277]
The length of the subnet prefix.
nodetype: leaf (rw)
type: uint8
description:
Operational state data for each IPv4 address
configured on the interface
nodetype: container (ro)
description:
[adapted from IETF IP model RFC 7277]
The IPv4 address on the interface.
nodetype: leaf (ro)
type: inet:ipv4-address-no-zone
description:
[adapted from IETF IP model RFC 7277]
The length of the subnet prefix.
nodetype: leaf (ro)
type: uint8
description:
The origin of this address, e.g., statically configured,
assigned by DHCP, etc..
nodetype: leaf (ro)
type: ip-address-origin
description:
Enclosing container for VRRP groups handled by this
IP interface
nodetype: container (rw)
description:
List of VRRP groups, keyed by virtual router id
nodetype: list (rw)
list keys: [virtual-router-id]
description:
References the configured virtual router id for this
VRRP group
nodetype: leaf (list key) (rw)
type: leafref
description:
Configuration data for the VRRP group
nodetype: container (rw)
description:
Set the virtual router id for use by the VRRP group. This
usually also determines the virtual MAC address that is
generated for the VRRP group
nodetype: leaf (rw)
type: uint8
description:
Configure one or more virtual addresses for the
VRRP group
nodetype: leaf-list (rw)
type: inet:ip-address
description:
Specifies the sending VRRP interface's priority
for the virtual router. Higher values equal higher
priority
nodetype: leaf (rw)
type: uint8
description:
When set to true, enables preemption by a higher
priority backup router of a lower priority master router
nodetype: leaf (rw)
type: boolean
description:
Set the delay the higher priority router waits
before preempting
nodetype: leaf (rw)
type: uint16
description:
Configure whether packets destined for
virtual addresses are accepted even when the virtual
address is not owned by the router interface
nodetype: leaf (rw)
type: boolean
description:
Sets the interval between successive VRRP
advertisements -- RFC 5798 defines this as a 12-bit
value expressed as 0.1 seconds, with default 100, i.e.,
1 second. Several implementation express this in units of
seconds
nodetype: leaf (rw)
type: uint16
units: centiseconds
description:
Operational state data for the VRRP group
nodetype: container (ro)
description:
Set the virtual router id for use by the VRRP group. This
usually also determines the virtual MAC address that is
generated for the VRRP group
nodetype: leaf (ro)
type: uint8
description:
Configure one or more virtual addresses for the
VRRP group
nodetype: leaf-list (ro)
type: inet:ip-address
description:
Specifies the sending VRRP interface's priority
for the virtual router. Higher values equal higher
priority
nodetype: leaf (ro)
type: uint8
description:
When set to true, enables preemption by a higher
priority backup router of a lower priority master router
nodetype: leaf (ro)
type: boolean
description:
Set the delay the higher priority router waits
before preempting
nodetype: leaf (ro)
type: uint16
description:
Configure whether packets destined for
virtual addresses are accepted even when the virtual
address is not owned by the router interface
nodetype: leaf (ro)
type: boolean
description:
Sets the interval between successive VRRP
advertisements -- RFC 5798 defines this as a 12-bit
value expressed as 0.1 seconds, with default 100, i.e.,
1 second. Several implementation express this in units of
seconds
nodetype: leaf (ro)
type: uint16
units: centiseconds
description:
Operational value of the priority for the
interface in the VRRP group
nodetype: leaf (ro)
type: uint8
description:
Top-level container for VRRP interface tracking
nodetype: container (rw)
description:
Configuration data for VRRP interface tracking
nodetype: container (rw)
description:
Sets an interface that should be
tracked for up/down events to dynamically change the
priority state of the VRRP group, and potentially
change the mastership if the tracked interface going
down lowers the priority sufficiently
nodetype: leaf (rw)
type: leafref
description:
Set the value to subtract from priority when
the tracked interface goes down
nodetype: leaf (rw)
type: uint8
description:
Operational state data for VRRP interface tracking
nodetype: container (ro)
description:
Sets an interface that should be
tracked for up/down events to dynamically change the
priority state of the VRRP group, and potentially
change the mastership if the tracked interface going
down lowers the priority sufficiently
nodetype: leaf (ro)
type: leafref
description:
Set the value to subtract from priority when
the tracked interface goes down
nodetype: leaf (ro)
type: uint8
description:
Enclosing container for neighbor list
nodetype: container (rw)
description:
A list of mappings from IPv4 addresses to
link-layer addresses.
Entries in this list are used as static entries in the
ARP Cache.
nodetype: list (rw)
list keys: [ip]
description:
References the configured IP address
nodetype: leaf (list key) (rw)
type: leafref
description:
Configuration data for each configured IPv4
address on the interface
nodetype: container (rw)
description:
The IPv4 address of the neighbor node.
nodetype: leaf (rw)
type: inet:ipv4-address-no-zone
description:
The link-layer address of the neighbor node.
nodetype: leaf (rw)
type: yang:phys-address
description:
Operational state data for each IPv4 address
configured on the interface
nodetype: container (ro)
description:
The IPv4 address of the neighbor node.
nodetype: leaf (ro)
type: inet:ipv4-address-no-zone
description:
The link-layer address of the neighbor node.
nodetype: leaf (ro)
type: yang:phys-address
description:
The origin of this neighbor entry, static or dynamic.
nodetype: leaf (ro)
type: neighbor-origin
description:
Top-level container for setting unnumbered interfaces.
Includes reference the interface that provides the
address information
nodetype: container (rw)
description:
Configuration data for unnumbered interface
nodetype: container (rw)
description:
Indicates that the subinterface is unnumbered. By default
the subinterface is numbered, i.e., expected to have an
IP address configuration.
nodetype: leaf (rw)
type: boolean
description:
Operational state data for unnumbered interfaces
nodetype: container (ro)
description:
Indicates that the subinterface is unnumbered. By default
the subinterface is numbered, i.e., expected to have an
IP address configuration.
nodetype: leaf (ro)
type: boolean
description:
Reference to an interface or subinterface
nodetype: container (rw)
description:
Configured reference to interface / subinterface
nodetype: container (rw)
description:
Reference to a base interface. If a reference to a
subinterface is required, this leaf must be specified
to indicate the base interface.
nodetype: leaf (rw)
type: leafref
description:
Reference to a subinterface -- this requires the base
interface to be specified using the interface leaf in
this container. If only a reference to a base interface
is requuired, this leaf should not be set.
nodetype: leaf (rw)
type: leafref
description:
Operational state for interface-ref
nodetype: container (ro)
description:
Reference to a base interface. If a reference to a
subinterface is required, this leaf must be specified
to indicate the base interface.
nodetype: leaf (ro)
type: leafref
description:
Reference to a subinterface -- this requires the base
interface to be specified using the interface leaf in
this container. If only a reference to a base interface
is requuired, this leaf should not be set.
nodetype: leaf (ro)
type: leafref
description:
Top-level IPv4 configuration data for the interface
nodetype: container (rw)
description:
Controls whether IPv4 is enabled or disabled on this
interface. When IPv4 is enabled, this interface is
connected to an IPv4 stack, and the interface can send
and receive IPv4 packets.
nodetype: leaf (rw)
type: boolean
description:
The size, in octets, of the largest IPv4 packet that the
interface will send and receive.
The server may restrict the allowed values for this leaf,
depending on the interface's type.
If this leaf is not configured, the operationally used MTU
depends on the interface's type.
nodetype: leaf (rw)
type: uint16
units: octets
description:
Top level IPv4 operational state data
nodetype: container (ro)
description:
Controls whether IPv4 is enabled or disabled on this
interface. When IPv4 is enabled, this interface is
connected to an IPv4 stack, and the interface can send
and receive IPv4 packets.
nodetype: leaf (ro)
type: boolean
description:
The size, in octets, of the largest IPv4 packet that the
interface will send and receive.
The server may restrict the allowed values for this leaf,
depending on the interface's type.
If this leaf is not configured, the operationally used MTU
depends on the interface's type.
nodetype: leaf (ro)
type: uint16
units: octets
description:
Parameters for the IPv6 address family.
nodetype: container (rw)
description:
Enclosing container for address list
nodetype: container (rw)
description:
The list of configured IPv6 addresses on the interface.
nodetype: list (rw)
list keys: [ip]
description:
References the configured IP address
nodetype: leaf (list key) (rw)
type: leafref
description:
Configuration data for each IPv6 address on
the interface
nodetype: container (rw)
description:
[adapted from IETF IP model RFC 7277]
The IPv6 address on the interface.
nodetype: leaf (rw)
type: inet:ipv6-address-no-zone
description:
[adapted from IETF IP model RFC 7277]
The length of the subnet prefix.
nodetype: leaf (rw)
type: uint8
description:
State data for each IPv6 address on the
interface
nodetype: container (ro)
description:
[adapted from IETF IP model RFC 7277]
The IPv6 address on the interface.
nodetype: leaf (ro)
type: inet:ipv6-address-no-zone
description:
[adapted from IETF IP model RFC 7277]
The length of the subnet prefix.
nodetype: leaf (ro)
type: uint8
description:
[adapted from IETF IP model RFC 7277]
The origin of this address, e.g., static, dhcp, etc.
nodetype: leaf (ro)
type: ip-address-origin
description:
[adapted from IETF IP model RFC 7277]
The status of an address. Most of the states correspond
to states from the IPv6 Stateless Address
Autoconfiguration protocol.
nodetype: leaf (ro)
type: enumeration
description:
Enclosing container for VRRP groups handled by this
IP interface
nodetype: container (rw)
description:
List of VRRP groups, keyed by virtual router id
nodetype: list (rw)
list keys: [virtual-router-id]
description:
References the configured virtual router id for this
VRRP group
nodetype: leaf (list key) (rw)
type: leafref
description:
Configuration data for the VRRP group
nodetype: container (rw)
description:
Set the virtual router id for use by the VRRP group. This
usually also determines the virtual MAC address that is
generated for the VRRP group
nodetype: leaf (rw)
type: uint8
description:
Configure one or more virtual addresses for the
VRRP group
nodetype: leaf-list (rw)
type: inet:ip-address
description:
Specifies the sending VRRP interface's priority
for the virtual router. Higher values equal higher
priority
nodetype: leaf (rw)
type: uint8
description:
When set to true, enables preemption by a higher
priority backup router of a lower priority master router
nodetype: leaf (rw)
type: boolean
description:
Set the delay the higher priority router waits
before preempting
nodetype: leaf (rw)
type: uint16
description:
Configure whether packets destined for
virtual addresses are accepted even when the virtual
address is not owned by the router interface
nodetype: leaf (rw)
type: boolean
description:
Sets the interval between successive VRRP
advertisements -- RFC 5798 defines this as a 12-bit
value expressed as 0.1 seconds, with default 100, i.e.,
1 second. Several implementation express this in units of
seconds
nodetype: leaf (rw)
type: uint16
units: centiseconds
description:
For VRRP on IPv6 interfaces, sets the virtual link local
address
nodetype: leaf (rw)
type: inet:ip-address
description:
Operational state data for the VRRP group
nodetype: container (ro)
description:
Set the virtual router id for use by the VRRP group. This
usually also determines the virtual MAC address that is
generated for the VRRP group
nodetype: leaf (ro)
type: uint8
description:
Configure one or more virtual addresses for the
VRRP group
nodetype: leaf-list (ro)
type: inet:ip-address
description:
Specifies the sending VRRP interface's priority
for the virtual router. Higher values equal higher
priority
nodetype: leaf (ro)
type: uint8
description:
When set to true, enables preemption by a higher
priority backup router of a lower priority master router
nodetype: leaf (ro)
type: boolean
description:
Set the delay the higher priority router waits
before preempting
nodetype: leaf (ro)
type: uint16
description:
Configure whether packets destined for
virtual addresses are accepted even when the virtual
address is not owned by the router interface
nodetype: leaf (ro)
type: boolean
description:
Sets the interval between successive VRRP
advertisements -- RFC 5798 defines this as a 12-bit
value expressed as 0.1 seconds, with default 100, i.e.,
1 second. Several implementation express this in units of
seconds
nodetype: leaf (ro)
type: uint16
units: centiseconds
description:
Operational value of the priority for the
interface in the VRRP group
nodetype: leaf (ro)
type: uint8
description:
For VRRP on IPv6 interfaces, sets the virtual link local
address
nodetype: leaf (ro)
type: inet:ip-address
description:
Top-level container for VRRP interface tracking
nodetype: container (rw)
description:
Configuration data for VRRP interface tracking
nodetype: container (rw)
description:
Sets an interface that should be
tracked for up/down events to dynamically change the
priority state of the VRRP group, and potentially
change the mastership if the tracked interface going
down lowers the priority sufficiently
nodetype: leaf (rw)
type: leafref
description:
Set the value to subtract from priority when
the tracked interface goes down
nodetype: leaf (rw)
type: uint8
description:
Operational state data for VRRP interface tracking
nodetype: container (ro)
description:
Sets an interface that should be
tracked for up/down events to dynamically change the
priority state of the VRRP group, and potentially
change the mastership if the tracked interface going
down lowers the priority sufficiently
nodetype: leaf (ro)
type: leafref
description:
Set the value to subtract from priority when
the tracked interface goes down
nodetype: leaf (ro)
type: uint8
description:
Configuration and operational state parameters relating to
router advertisements.
nodetype: container (rw)
description:
Configuration parameters relating to router advertisements
for IPv6.
nodetype: container (rw)
description:
The interval between periodic router advertisement neighbor
discovery messages sent on this interface expressed in
seconds.
nodetype: leaf (rw)
type: uint32
units: seconds
description:
The lifetime advertised in the router advertisement neighbor
discovery message on this interface.
nodetype: leaf (rw)
type: uint32
units: seconds
description:
When set to true, router advertisement neighbor discovery
messages are not transmitted on this interface.
nodetype: leaf (rw)
type: boolean
description:
Operational state parameters relating to router
advertisements for IPv6.
nodetype: container (ro)
description:
The interval between periodic router advertisement neighbor
discovery messages sent on this interface expressed in
seconds.
nodetype: leaf (ro)
type: uint32
units: seconds
description:
The lifetime advertised in the router advertisement neighbor
discovery message on this interface.
nodetype: leaf (ro)
type: uint32
units: seconds
description:
When set to true, router advertisement neighbor discovery
messages are not transmitted on this interface.
nodetype: leaf (ro)
type: boolean
description:
Enclosing container for list of IPv6 neighbors
nodetype: container (rw)
description:
List of IPv6 neighbors
nodetype: list (rw)
list keys: [ip]
description:
References the configured IP neighbor address
nodetype: leaf (list key) (rw)
type: leafref
description:
Configuration data for each IPv6 address on
the interface
nodetype: container (rw)
description:
[adapted from IETF IP model RFC 7277]
The IPv6 address of the neighbor node.
nodetype: leaf (rw)
type: inet:ipv6-address-no-zone
description:
[adapted from IETF IP model RFC 7277]
The link-layer address of the neighbor node.
nodetype: leaf (rw)
type: yang:phys-address
description:
State data for each IPv6 address on the
interface
nodetype: container (ro)
description:
[adapted from IETF IP model RFC 7277]
The IPv6 address of the neighbor node.
nodetype: leaf (ro)
type: inet:ipv6-address-no-zone
description:
[adapted from IETF IP model RFC 7277]
The link-layer address of the neighbor node.
nodetype: leaf (ro)
type: yang:phys-address
description:
[adapted from IETF IP model RFC 7277]
The origin of this neighbor entry.
nodetype: leaf (ro)
type: neighbor-origin
description:
[adapted from IETF IP model RFC 7277]
Indicates that the neighbor node acts as a router.
nodetype: leaf (ro)
type: empty
description:
[adapted from IETF IP model RFC 7277]
The Neighbor Unreachability Detection state of this
entry.
nodetype: leaf (ro)
type: enumeration
description:
Top-level container for setting unnumbered interfaces.
Includes reference the interface that provides the
address information
nodetype: container (rw)
description:
Configuration data for unnumbered interface
nodetype: container (rw)
description:
Indicates that the subinterface is unnumbered. By default
the subinterface is numbered, i.e., expected to have an
IP address configuration.
nodetype: leaf (rw)
type: boolean
description:
Operational state data for unnumbered interfaces
nodetype: container (ro)
description:
Indicates that the subinterface is unnumbered. By default
the subinterface is numbered, i.e., expected to have an
IP address configuration.
nodetype: leaf (ro)
type: boolean
description:
Reference to an interface or subinterface
nodetype: container (rw)
description:
Configured reference to interface / subinterface
nodetype: container (rw)
description:
Reference to a base interface. If a reference to a
subinterface is required, this leaf must be specified
to indicate the base interface.
nodetype: leaf (rw)
type: leafref
description:
Reference to a subinterface -- this requires the base
interface to be specified using the interface leaf in
this container. If only a reference to a base interface
is requuired, this leaf should not be set.
nodetype: leaf (rw)
type: leafref
description:
Operational state for interface-ref
nodetype: container (ro)
description:
Reference to a base interface. If a reference to a
subinterface is required, this leaf must be specified
to indicate the base interface.
nodetype: leaf (ro)
type: leafref
description:
Reference to a subinterface -- this requires the base
interface to be specified using the interface leaf in
this container. If only a reference to a base interface
is requuired, this leaf should not be set.
nodetype: leaf (ro)
type: leafref
description:
Top-level config data for the IPv6 interface
nodetype: container (rw)
description:
[adapted from IETF IP model RFC 7277]
Controls whether IPv6 is enabled or disabled on this
interface. When IPv6 is enabled, this interface is
connected to an IPv6 stack, and the interface can send
and receive IPv6 packets.
nodetype: leaf (rw)
type: boolean
description:
[adapted from IETF IP model RFC 7277]
The size, in octets, of the largest IPv6 packet that the
interface will send and receive.
The server may restrict the allowed values for this leaf,
depending on the interface's type.
If this leaf is not configured, the operationally used MTU
depends on the interface's type.
nodetype: leaf (rw)
type: uint32
units: octets
description:
[adapted from IETF IP model RFC 7277]
The number of consecutive Neighbor Solicitation messages
sent while performing Duplicate Address Detection on a
tentative address. A value of zero indicates that
Duplicate Address Detection is not performed on
tentative addresses. A value of one indicates a single
transmission with no follow-up retransmissions.
nodetype: leaf (rw)
type: uint32
description:
Top-level operational state data for the IPv6 interface
nodetype: container (ro)
description:
[adapted from IETF IP model RFC 7277]
Controls whether IPv6 is enabled or disabled on this
interface. When IPv6 is enabled, this interface is
connected to an IPv6 stack, and the interface can send
and receive IPv6 packets.
nodetype: leaf (ro)
type: boolean
description:
[adapted from IETF IP model RFC 7277]
The size, in octets, of the largest IPv6 packet that the
interface will send and receive.
The server may restrict the allowed values for this leaf,
depending on the interface's type.
If this leaf is not configured, the operationally used MTU
depends on the interface's type.
nodetype: leaf (ro)
type: uint32
units: octets
description:
[adapted from IETF IP model RFC 7277]
The number of consecutive Neighbor Solicitation messages
sent while performing Duplicate Address Detection on a
tentative address. A value of zero indicates that
Duplicate Address Detection is not performed on
tentative addresses. A value of one indicates a single
transmission with no follow-up retransmissions.
nodetype: leaf (ro)
type: uint32
description:
Configuration for L3 VLAN interface
frinx-device-type:
nos
frinx-supported-versions:
any
nodetype: container (rw)
description:
Configuration parameters for vlan interface
frinx-device-type:
nos
frinx-supported-versions:
any
frinx-implemented-reader:
io.frinx.cli.unit.dasan.ifc.handler.l3ipvlan.L3ipvlanConfigReader
frinx-implemented-reader-details:
NO_IP_REDIRECTS_LINE:
^\s*no ip redirects$
SH_SINGLE_INTERFACE_CFG:
show running-config interface %s
frinx-implemented-writer:
io.frinx.cli.unit.dasan.ifc.handler.l3ipvlan.L3ipvlanConfigWriter
nodetype: container (rw)
description:
Specify 'ip redirects' for vlan interface.
nodetype: leaf (rw)
type: boolean
description:
State variables for vlan interface
nodetype: container (ro)
description:
Specify 'ip redirects' for vlan interface.
nodetype: leaf (ro)
type: boolean
description:
Configure Address Resolution Protocol
nodetype: container (rw)
nodetype: container (rw)
description:
The number of seconds that an entry remains in the ARP cache
nodetype: leaf (rw)
type: uint32
units: seconds
description:
Enclosing container for damping interface-specific
data.
frinx-device-type:
junos
frinx-supported-versions:
173
nodetype: container (rw)
description:
Configuration parameters for damping
frinx-device-type:
xr
frinx-supported-versions:
interface
frinx-implemented-reader:
io.frinx.unitopo.unit.xr66.interfaces.handler.InterfaceDampingConfigReader
frinx-implemented-writer:
io.frinx.unitopo.unit.xr66.interfaces.handler.InterfaceDampingConfigWriter
frinx-device-type:
junos
frinx-supported-versions:
173
frinx-implemented-reader:
io.frinx.unitopo.unit.junos.interfaces.handler.InterfaceDampingConfigReader
frinx-implemented-writer:
io.frinx.unitopo.unit.junos.interfaces.handler.InterfaceDampingConfigWriter
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.ifc.handler.InterfaceDampingConfigReader
frinx-implemented-reader-details:
DAMPING_ENABLED:
\s*dampening.*
DAMPING_REUSE:
\s*dampening (?<halfLife>\d+).*
FULL_DAMPING_CONFIG:
\s*dampening (?<halfLife>\d+) (?<reuse>\d+) (?<suppress>\d+) (?<maxSuppress>\d+).*
frinx-implemented-writer:
io.frinx.cli.unit.iosxr.ifc.handler.InterfaceDampingConfigWriter
frinx-implemented-writer-details:
DEFAULT_DAMPENING_COMMAND:
dampening
NO_DAMPENING:
no dampening
nodetype: container (rw)
description:
Desired state of damping
nodetype: leaf (rw)
type: boolean
description:
Decay half life (in minutes).
Must be less than the max-suppress value.
nodetype: leaf (rw)
type: uint32
units: minutes
description:
Reuse threshold — Arbitrary value below which
a suppressed route can be used again.
nodetype: leaf (rw)
type: uint32
description:
Suppress threshold — Arbitrary value above which
a route can no longer be used or included in advertisements.
Must be greater than the reuse threshold.
nodetype: leaf (rw)
type: uint32
description:
Max suppress time (in minutes)
nodetype: leaf (rw)
type: uint32
units: minutes
description:
State variables for damping
nodetype: container (ro)
description:
Desired state of damping
nodetype: leaf (ro)
type: boolean
description:
Decay half life (in minutes).
Must be less than the max-suppress value.
nodetype: leaf (ro)
type: uint32
units: minutes
description:
Reuse threshold — Arbitrary value below which
a suppressed route can be used again.
nodetype: leaf (ro)
type: uint32
description:
Suppress threshold — Arbitrary value above which
a route can no longer be used or included in advertisements.
Must be greater than the reuse threshold.
nodetype: leaf (ro)
type: uint32
description:
Max suppress time (in minutes)
nodetype: leaf (ro)
type: uint32
units: minutes
description:
Enclosing container for statistics interface-specific
data.
nodetype: container (rw)
description:
Configuration parameters for statistics
frinx-device-type:
xr
frinx-supported-versions:
interface
frinx-implemented-reader:
io.frinx.unitopo.unit.xr66.interfaces.handler.InterfaceStatisticsConfigReader
frinx-implemented-writer:
io.frinx.unitopo.unit.xr66.interfaces.handler.InterfaceStatisticsConfigWriter
frinx-device-type:
nexus
frinx-supported-versions:
any
frinx-implemented-reader:
io.frinx.cli.unit.nexus.ifc.handler.InterfaceStatisticsConfigReader
frinx-implemented-reader-details:
LOAD_INTERVAL:
\s*load-interval counter 1 (?<loadInterval>\d+)\s*
frinx-implemented-writer:
io.frinx.cli.unit.nexus.ifc.handler.InterfaceStatisticsConfigWriter
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.ifc.handler.InterfaceStatisticsConfigReader
frinx-implemented-reader-details:
LOAD_INTERVAL:
\s*load-interval (?<loadInterval>\d+)\s*
frinx-implemented-writer:
io.frinx.cli.unit.iosxr.ifc.handler.InterfaceStatisticsConfigWriter
nodetype: container (rw)
description:
Specify interval for load calculation for an
interface.
0 disables load calculation, otherwise some
multiple of 30 between 30 and 600.
nodetype: leaf (rw)
type: uint32
description:
State variables for statistics
nodetype: container (ro)
description:
Specify interval for load calculation for an
interface.
0 disables load calculation, otherwise some
multiple of 30 between 30 and 600.
nodetype: leaf (ro)
type: uint32
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.ifc.handler.verify.RpfCheckReader
frinx-implemented-reader-details:
ALL_INGRESS_ACLS_LINE:
(?<type>.+) verify unicast source reachable-via (?<config>(any|rx))( ?(?<allowConfig>.*))?
SH_RPF_INTF:
show running-config interface %s | include verify unicast source reachable-via
frinx-implemented-writer:
MISSING WRITER
nodetype: container (rw)
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.ifc.handler.verify.RpfCheckReader
frinx-implemented-reader-details:
ALL_INGRESS_ACLS_LINE:
(?<type>.+) verify unicast source reachable-via (?<config>(any|rx))( ?(?<allowConfig>.*))?
SH_RPF_INTF:
show running-config interface %s | include verify unicast source reachable-via
frinx-implemented-writer:
io.frinx.cli.unit.iosxr.ifc.handler.verify.RpfCheckIpv4Writer
nodetype: container (rw)
nodetype: leaf (rw)
type: enumeration
nodetype: leaf-list (rw)
type: identityref
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.ifc.handler.verify.RpfCheckReader
frinx-implemented-reader-details:
ALL_INGRESS_ACLS_LINE:
(?<type>.+) verify unicast source reachable-via (?<config>(any|rx))( ?(?<allowConfig>.*))?
SH_RPF_INTF:
show running-config interface %s | include verify unicast source reachable-via
frinx-implemented-writer:
io.frinx.cli.unit.iosxr.ifc.handler.verify.RpfCheckIpv6Writer
nodetype: container (rw)
nodetype: leaf (rw)
type: enumeration
nodetype: leaf-list (rw)
type: identityref
description:
CFM interface configuration
nodetype: container (rw)
description:
Configuration for ethernet CFM
nodetype: container (rw)
description:
Is ethernet CFM enabled
nodetype: leaf (rw)
type: boolean
description:
Domain-specific interface configuration
nodetype: container (rw)
description:
Configuration for a particular Maintenance Domain
nodetype: list (rw)
list keys: [domain-name]
description:
Maintenance Domain
nodetype: leaf (list key) (rw)
type: leafref
description:
Configuration for Maintenance Domain
nodetype: container (rw)
description:
Maintenance Domain
nodetype: leaf (rw)
type: string
description:
MEP configuration
nodetype: container (rw)
description:
configuration for MEP
nodetype: container (rw)
description:
MA name
nodetype: leaf (rw)
type: string
description:
MEP ID
nodetype: leaf (rw)
type: uint16
description:
Ethernet CoS
nodetype: leaf (rw)
type: uint8
This module describes YANG model for ISIS Routing
frinx-openconfig-isis-types
frinx-openconfig-extensions
frinx-openconfig-mpls-types
This module contains general LSDB type definitions for use in ISIS YANG model.
frinx-openconfig-extensions
description:
Base identity for an ISIS SUB-TLV type.
description:
Base identity for an ISIS TLV 135, 235, 236, 237 SUB-TLV
type.
base identity: ISIS_SUBTLV_TYPE
description:
Base identity for an ISIS TLV 22, 23, 222, 223, 141 SUB-TLV
type.
base identity: ISIS_SUBTLV_TYPE
description:
Base identity for an ISIS TLV 242 SUB-TLV type.
base identity: ISIS_SUBTLV_TYPE
description:
Base identity for an ISIS TLV type.
description:
ISIS TLV 1. Intermediate System to Intermediate System Intra-
Domain Routeing Exchange Protocol for use in Conjunction with
the Protocol for Providing the Connectionless-mode Network
Service (ISO 8473), International Standard 10589: 2002, Second
Edition, 2002.
base identity: ISIS_TLV_TYPE
description:
ISIS TLV 232. IPv6 Interface Address TLV that maps directly to
the IP Interface Address TLV in [RFC1195]. We necessarily modify
the contents to be 0-15 16-octet IPv6 interface addresses
instead of 0-63 4-octet IPv4 interface addresses
base identity: ISIS_TLV_TYPE
description:
ISIS TLV 13. If an IS generates a purge, it SHOULD include
this TLV in the purge with its own system ID. If an IS
receives a purge that does not include this TLV, then it SHOULD
add this TLV with both its own system ID and the system ID of
the IS from which it received the purge. This allows ISs
receiving purges to log the system ID of the originator, or the
upstream source of the purge.
base identity: ISIS_TLV_TYPE
description:
ISIS TLV 237. TLV is aligned with IPv6 Reachability TLV type
236 beside an additional two bytes in front to indicate MT
membership.
base identity: ISIS_TLV_TYPE
description:
ISIS TLV 236. The IPv6 Reachability TLV describes network
reachability through the specification of a routing prefix,
metric information, a bit to indicate if the prefix is being
advertised down from a higher level, a bit to indicate if the
prefix is being distributed from another routing protocol, and
OPTIONALLY the existence of Sub-TLVs to allow for later
extension.
base identity: ISIS_TLV_TYPE
description:
ISIS TLV 23. Identical in format to TLV 22 and included in
Original LSPs or Extended LSPs. Regardless of the type of LSP
in which the TLVs appear, the information pertains to the
neighbor relationship between the Originating System and the IS
identified in the TLV
base identity: ISIS_TLV_TYPE
description:
ISIS TLV 24. IS-Alias TLV which extension-capable ISs to
recognize the Originating System of an Extended LSP set. It
identifies the Normal system-id of the Originating System
base identity: ISIS_TLV_TYPE
description:
ISIS TLV 139. IPv6 Shared Risk Link Group
base identity: ISIS_TLV_TYPE
description:
ISIS TLV 134. Traffic Engineering router ID TLV that contains
the 4-octet router ID of the router originating the LSP
base identity: ISIS_TLV_TYPE
description:
ISIS TLV 14. The maximum MTU that the advertising system can
receive, expressed in bytes.
base identity: ISIS_TLV_TYPE
description:
ISIS TLV 229. This MT TLV can advertise up to 127 MTs. It is
announced in IIHs and LSP fragment 0, and can occur multiple
times. The resulting MT set SHOULD be the union of all the MT
TLV occurrences in the packet. Any other IS-IS PDU occurrence of
this TLV MUST be ignored. Lack of MT TLV in hellos and fragment
zero LSPs MUST be interpreted as participation of the
advertising interface or router in MT ID #0 only. If a router
advertises MT TLV, it has to advertise all the MTs it
participates in, specifically including topology ID #0 also.
base identity: ISIS_TLV_TYPE
description:
ISIS TLV 223. Is is identical in format to TLV 222. In the
event that there is a need to advertise in Extended LSPs such
information associated with neighbors of the Originating System,
it is necessary to define new TLVs to carry the sub-TLV
information.
base identity: ISIS_TLV_TYPE
description:
ISIS TLV 137. The Dynamic hostname TLV is optional. This TLV
may be present in any fragment of a non-pseudonode LSP. The
value field identifies the symbolic name of the router
originating the LSP. This symbolic name can be the FQDN for the
router, it can be a subset of the FQDN, or it can be any string
operators want to use for the router.
base identity: ISIS_TLV_TYPE
description:
ISIS TLV 132. The IP address of one or more interfaces
corresponding to the SNPAs enabled on this Intermediate system
(i.e., one or more IP addresses of this router). This is
permitted to appear multiple times, and in an LSP with any LSP
number.
base identity: ISIS_TLV_TYPE
description:
ISIS TLV 140. The IPv6 TE Router ID TLV contains a 16-octet
IPv6 address. A stable global IPv6 address MUST be used, so that
the router ID provides a routable address, regardless of the
state of a node's interfaces. If a router does not implement
traffic engineering, it MAY include or omit the IPv6 TE Router
ID TLV. If a router implements traffic engineering for IPv6, it
MUST include this TLV in its LSP. This TLV MUST NOT be included
more than once in an LSP.
base identity: ISIS_TLV_TYPE
description:
ISIS TLV 7. An Instance Identifier (IID) to uniquely
identify an IS-IS instance. When the IID = 0, the list of
supported ITIDs MUST NOT be present. An IID-TLV with IID = 0
MUST NOT appear in an SNP or LSP. When the TLV appears (with a
non-zero IID) in an SNP or LSP, exactly one ITID. MUST be
present indicating the topology with which the PDU is
associated. If no ITIDs or multiple ITIDs are present or the
IID is zero, then the PDU MUST be ignored
base identity: ISIS_TLV_TYPE
description:
ISIS TLV 235. TLV is aligned with extended IP reachability TLV
type 135 beside an additional two bytes in front to indicate MT
membership
base identity: ISIS_TLV_TYPE
description:
ISIS TLV 135. Extended IP reachability TLV that provides for a
32-bit metric and adds one bit to indicate that a prefix has
been redistributed _down_ in the hierarchy
base identity: ISIS_TLV_TYPE
description:
ISIS TLV 129. TLV defines the set Network Layer Protocol
Identifiers for Network Layer protocols that this Intermediate
System is capable of relaying
base identity: ISIS_TLV_TYPE
description:
ISIS TLV 130. TLV defines IP addresses outside the routing
domain reachable via interfaces on this Intermediate system.
This is permitted to appear multiple times, and in an LSP with
any LSP number. However, this field must not appear in
pseudonode LSPs
base identity: ISIS_TLV_TYPE
description:
ISIS TLV 222. TLV is aligned with extended IS reachability TLV
type 22 beside an additional two bytes in front at the beginning
of the TLV that. indicate MT membership.
base identity: ISIS_TLV_TYPE
description:
ISIS TLV 128. TLV defines IP addresses within the routing
domain reachable directly via one or more interfaces on this
Intermediate system
base identity: ISIS_TLV_TYPE
description:
ISIS TLV 242. IS-IS TLV named CAPABILITY, formed of multiple
sub-TLVs, which allows a router to announce its capabilities
within an IS-IS level or the entire routing domain.
base identity: ISIS_TLV_TYPE
description:
ISIS TLV 22. An extended IS reachability TLV that has a
different data structure to TLV 2 that introduces the use of
sub-TLV object-group.
base identity: ISIS_TLV_TYPE
description:
ISIS TLV 10.Intermediate System to Intermediate System Intra-
Domain Routeing Exchange Protocol for use in Conjunction with
the Protocol for Providing the Connectionless-mode Network
Service (ISO 8473) International Standard 10589: 2002, Second
Edition, 2002.
base identity: ISIS_TLV_TYPE
description:
ISIS TLV 2. Intermediate System to Intermediate System Intra-
Domain Routeing Exchange Protocol for use in Conjunction with
the Protocol for Providing the Connectionless-mode Network
Service (ISO 8473), International Standard 10589: 2002, Second
Edition, 2002.
base identity: ISIS_TLV_TYPE
description:
ISIS TLV 138. IPv4 Shared Risk Link Group TLV
base identity: ISIS_TLV_TYPE
This module contains data definitions for ISIS routing policy. It augments the base routing-policy module with BGP-specific options for conditions and actions.
frinx-openconfig-routing-policy
frinx-openconfig-extensions
frinx-openconfig-isis-types
This module contains general data definitions for use in ISIS YANG model.
frinx-openconfig-extensions
description:
This type defines the state of the interface.
type: enumeration
description:
This type defines ISIS narrow metric.
type: uint8
description:
This type defines the ISIS area address.
type: string
description:
This type defines ISIS level types
type: enumeration
description:
This type defines ISIS metric type
type: enumeration
description:
This type defines ISIS hello padding type
type: enumeration
description:
This type defines ISIS metric styles
type: enumeration
description:
This type defines ISIS wide metric.
type: uint32
description:
This type defines ISIS level.
type: uint8
description:
This type defines ISIS interface types
type: enumeration
description:
This type defines interface circuit ID.
type: uint32
description:
This type defines OSI NET address. A NET should should be in
the form xx.yyyy.yyyy.yyyy.00 with up to 9 sets of yyyy.
type: string
description:
This type defines ISIS adaptive timer types
type: enumeration
description:
This type defines Subnetwork Point of Attachment format.
type: string
description:
This type defines ISIS system id using pattern, system id looks
like : 0143.0438.AeF0
type: string
description:
This type defines ISIS LSP ID. ISIS LSP ID type should be in
the form of xxxx.xxxx.xxxx.xx-xx
type: string
description:
Base identify type for triggers that reset Overload Bit
description:
Base identity type for resetting Overload Bit when BGP has converged.
base identity: OVERLOAD_RESET_TRIGGER_TYPE
description:
Base identity type for resetting Overload Bit when system resources have
been restored.
base identity: OVERLOAD_RESET_TRIGGER_TYPE
description:
Base identify type for SAFI
description:
Base identify type for IPv4 Unicast address family
base identity: SAFI_TYPE
description:
Base identify type for IPv6 multicast address family
base identity: SAFI_TYPE
description:
Base identify type for multi-topology
description:
Base identify type for AFI/SAFI
description:
Base identify type for IPv4 multicast address family
base identity: AFI_SAFI_TYPE
description:
Base identify type for IPv6 unicast address family
base identity: AFI_SAFI_TYPE
description:
Base identify type for IPv6 multicast address family
base identity: AFI_SAFI_TYPE
description:
Base identify type for IPv4 Unicast address family
base identity: AFI_SAFI_TYPE
description:
Base identify type for AFI
description:
Base identify type for IPv4 address family
base identity: AFI_TYPE
description:
Base identify type for IPv6 address family
base identity: AFI_TYPE
This module describes configuration and operational state data for Link Aggregation Control Protocol (LACP) for managing aggregate interfaces. It works in conjunction with the OpenConfig interfaces and aggregate interfaces models.
frinx-openconfig-interfaces
frinx-openconfig-yang-types
frinx-openconfig-extensions
network-topology
frinx-uniconfig-topology
description:
Type of timeout used, short or long, by LACP participants
type: enumeration
description:
Describes the LACP membership type, active or passive, of the
interface in the aggregate
type: enumeration
description:
Indicates LACP synchronization state of participant
type: enumeration
description:
Defines the period options for the time between sending
LACP messages
type: enumeration
description:
Configuration and operational state data for LACP protocol
operation on the aggregate interface
nodetype: container (rw)
description:
Configuration data for LACP
nodetype: container (rw)
description:
Sytem priority used by the node on this LAG interface.
Lower value is higher priority for determining which node
is the controlling system.
nodetype: leaf (rw)
type: uint16
description:
Operational state data for LACP
nodetype: container (ro)
description:
Sytem priority used by the node on this LAG interface.
Lower value is higher priority for determining which node
is the controlling system.
nodetype: leaf (ro)
type: uint16
description:
Enclosing container for the list of LACP-enabled
interfaces
nodetype: container (rw)
description:
List of aggregate interfaces managed by LACP
nodetype: list (rw)
list keys: [name]
description:
Reference to the list key
nodetype: leaf (list key) (rw)
type: leafref
description:
Configuration data for each LACP aggregate interface
nodetype: container (rw)
description:
Reference to the interface on which LACP should be
configured. The type of the target interface must be
ieee8023adLag
nodetype: leaf (rw)
type: oc-if:base-interface-ref
description:
The MAC address portion of the node's System ID. This is
combined with the system priority to construct the 8-octet
system-id
nodetype: leaf (rw)
type: oc-yang:mac-address
description:
Sytem priority used by the node on this LAG interface.
Lower value is higher priority for determining which node
is the controlling system.
nodetype: leaf (rw)
type: uint16
description:
Indicates participant is active or passive
nodetype: leaf (rw)
type: lacp-activity-type
description:
Set the period between LACP messages -- uses
the lacp-period-type enumeration.
nodetype: leaf (rw)
type: lacp-period-type
description:
Operational state data for each LACP aggregate
interface
nodetype: container (ro)
description:
Reference to the interface on which LACP should be
configured. The type of the target interface must be
ieee8023adLag
nodetype: leaf (ro)
type: oc-if:base-interface-ref
description:
The MAC address portion of the node's System ID. This is
combined with the system priority to construct the 8-octet
system-id
nodetype: leaf (ro)
type: oc-yang:mac-address
description:
Sytem priority used by the node on this LAG interface.
Lower value is higher priority for determining which node
is the controlling system.
nodetype: leaf (ro)
type: uint16
description:
Indicates participant is active or passive
nodetype: leaf (ro)
type: lacp-activity-type
description:
Set the period between LACP messages -- uses
the lacp-period-type enumeration.
nodetype: leaf (ro)
type: lacp-period-type
description:
Enclosing container for the list of members interfaces of
the aggregate. This list is considered operational state
only so is labeled config false and has no config container
nodetype: container (rw)
description:
List of member interfaces and their associated status for
a LACP-controlled aggregate interface. Member list is not
configurable here -- each interface indicates items
its participation in the LAG.
nodetype: list (rw)
list keys: [interface]
description:
Reference to aggregate member interface
nodetype: leaf (list key) (rw)
type: leafref
description:
Indiviudal configuration of mode and period type per member interface
nodetype: container (rw)
description:
Reference to interface member of the LACP aggregate
nodetype: leaf (rw)
type: oc-if:base-interface-ref
description:
Indicates participant is active or passive
nodetype: leaf (rw)
type: lacp-activity-type
description:
Set the period between LACP messages -- uses
the lacp-period-type enumeration.
nodetype: leaf (rw)
type: lacp-period-type
description:
Operational state data for aggregate members
nodetype: container (ro)
description:
The timeout type (short or long) used by the
participant
nodetype: leaf (ro)
type: lacp-timeout-type
description:
Indicates whether the participant is in-sync or
out-of-sync
nodetype: leaf (ro)
type: lacp-synchronization-type
description:
A true value indicates that the participant will allow
the link to be used as part of the aggregate. A false
value indicates the link should be used as an individual
link
nodetype: leaf (ro)
type: boolean
description:
If true, the participant is collecting incoming frames
on the link, otherwise false
nodetype: leaf (ro)
type: boolean
description:
When true, the participant is distributing outgoing
frames; when false, distribution is disabled
nodetype: leaf (ro)
type: boolean
description:
MAC address that defines the local system ID for the
aggregate interface
nodetype: leaf (ro)
type: oc-yang:mac-address
description:
Current operational value of the key for the aggregate
interface
nodetype: leaf (ro)
type: uint16
description:
MAC address representing the protocol partner's interface
system ID
nodetype: leaf (ro)
type: oc-yang:mac-address
description:
Operational value of the protocol partner's key
nodetype: leaf (ro)
type: uint16
description:
Port number of the local (actor) aggregation member
nodetype: leaf (ro)
type: uint16
description:
Port number of the partner (remote) port for this member
port
nodetype: leaf (ro)
type: uint16
description:
Indicates participant is active or passive
nodetype: leaf (ro)
type: lacp-activity-type
description:
Set the period between LACP messages -- uses
the lacp-period-type enumeration.
nodetype: leaf (ro)
type: lacp-period-type
description:
LACP protocol counters
nodetype: container (ro)
description:
Number of LACPDUs received
nodetype: leaf (ro)
type: oc-yang:counter64
description:
Number of LACPDUs transmitted
nodetype: leaf (ro)
type: oc-yang:counter64
description:
Number of LACPDU receive packet errors
nodetype: leaf (ro)
type: oc-yang:counter64
description:
Number of LACPDU transmit packet errors
nodetype: leaf (ro)
type: oc-yang:counter64
description:
Number of LACPDU unknown packet errors
nodetype: leaf (ro)
type: oc-yang:counter64
description:
Number of LACPDU illegal packet errors
nodetype: leaf (ro)
type: oc-yang:counter64
This module defines configuration and operational state data for the LLDP protocol.
frinx-openconfig-lldp-types
frinx-openconfig-interfaces
ietf-yang-types
frinx-openconfig-extensions
network-topology
frinx-uniconfig-topology
description:
Top-level container for LLDP configuration and state data
nodetype: container (rw)
description:
Configuration data
frinx-device-type:
ios
frinx-supported-versions:
12any,15any
frinx-implemented-reader:
io.frinx.cli.unit.ios.lldp.handler.LldpConfigReader
frinx-implemented-reader-details:
DOMAINNAME_PATTERN:
(ip )?domain name (?<name>.+)
HOSTNAME_PATTERN:
hostname (?<name>.+)
SHOW_HOSTNAME:
show running-config | include ^hostname|^ip domain name
frinx-implemented-writer:
MISSING WRITER
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.ios.lldp.handler.LldpConfigReader
frinx-implemented-reader-details:
DOMAINNAME_PATTERN:
(ip )?domain name (?<name>.+)
HOSTNAME_PATTERN:
hostname (?<name>.+)
SHOW_HOSTNAME:
show running-config | include ^hostname|^ip domain name
frinx-implemented-writer:
MISSING WRITER
frinx-device-type:
nexus
frinx-supported-versions:
any
frinx-implemented-reader:
io.frinx.cli.unit.nexus.lldp.handler.LldpConfigReader
frinx-implemented-reader-details:
DOMAINNAME_PATTERN:
ip domain-name (?<name>.+)
HOSTNAME_PATTERN:
switchname (?<name>.+)
SHOW_HOSTNAME:
show running-config | include ^switchname|^ip
frinx-implemented-writer:
MISSING WRITER
nodetype: container (rw)
description:
System level state of the LLDP protocol.
nodetype: leaf (rw)
type: boolean
description:
System level hello timer for the LLDP protocol.
nodetype: leaf (rw)
type: uint64
units: seconds
description:
Indicates whether the local system should suppress the
advertisement of particular TLVs with the LLDP PDUs that it
transmits. Where a TLV type is specified within this list, it
should not be included in any LLDP PDU transmitted by the
local agent.
nodetype: leaf-list (rw)
type: identityref
description:
The system name field shall contain an alpha-numeric string
that indicates the system's administratively assigned name.
The system name should be the system's fully qualified domain
name. If implementations support IETF RFC 3418, the sysName
object should be used for this field.
nodetype: leaf (rw)
type: string
description:
The system description field shall contain an alpha-numeric
string that is the textual description of the network entity.
The system description should include the full name and
version identification of the system's hardware type,
software operating system, and networking software. If
implementations support IETF RFC 3418, the sysDescr object
should be used for this field.
nodetype: leaf (rw)
type: string
description:
The Chassis ID is a mandatory TLV which identifies the
chassis component of the endpoint identifier associated with
the transmitting LLDP agent
nodetype: leaf (rw)
type: string
description:
This field identifies the format and source of the chassis
identifier string. It is an enumerator defined by the
LldpChassisIdSubtype object from IEEE 802.1AB MIB.
nodetype: leaf (rw)
type: oc-lldp-types:chassis-id-type
description:
Operational state data
nodetype: container (ro)
description:
System level state of the LLDP protocol.
nodetype: leaf (ro)
type: boolean
description:
System level hello timer for the LLDP protocol.
nodetype: leaf (ro)
type: uint64
units: seconds
description:
Indicates whether the local system should suppress the
advertisement of particular TLVs with the LLDP PDUs that it
transmits. Where a TLV type is specified within this list, it
should not be included in any LLDP PDU transmitted by the
local agent.
nodetype: leaf-list (ro)
type: identityref
description:
The system name field shall contain an alpha-numeric string
that indicates the system's administratively assigned name.
The system name should be the system's fully qualified domain
name. If implementations support IETF RFC 3418, the sysName
object should be used for this field.
nodetype: leaf (ro)
type: string
description:
The system description field shall contain an alpha-numeric
string that is the textual description of the network entity.
The system description should include the full name and
version identification of the system's hardware type,
software operating system, and networking software. If
implementations support IETF RFC 3418, the sysDescr object
should be used for this field.
nodetype: leaf (ro)
type: string
description:
The Chassis ID is a mandatory TLV which identifies the
chassis component of the endpoint identifier associated with
the transmitting LLDP agent
nodetype: leaf (ro)
type: string
description:
This field identifies the format and source of the chassis
identifier string. It is an enumerator defined by the
LldpChassisIdSubtype object from IEEE 802.1AB MIB.
nodetype: leaf (ro)
type: oc-lldp-types:chassis-id-type
description:
Global LLDP counters
nodetype: container (ro)
description:
The number of lldp frames received.
nodetype: leaf (ro)
type: yang:counter64
description:
The number of frames transmitted out.
nodetype: leaf (ro)
type: yang:counter64
description:
The number of LLDP frames received with errors.
nodetype: leaf (ro)
type: yang:counter64
description:
The number of LLDP frames received and discarded.
nodetype: leaf (ro)
type: yang:counter64
description:
The number of TLV frames received and discarded.
nodetype: leaf (ro)
type: yang:counter64
description:
The number of frames received with unknown TLV.
nodetype: leaf (ro)
type: yang:counter64
description:
Indicates the last time the counters were
cleared.
nodetype: leaf (ro)
type: yang:date-and-time
description:
The number of valid TLVs received.
nodetype: leaf (ro)
type: yang:counter64
description:
The number of entries aged out due to timeout.
nodetype: leaf (ro)
type: yang:counter64
description:
Enclosing container
nodetype: container (rw)
description:
List of interfaces on which LLDP is enabled / available
frinx-device-type:
xr
frinx-supported-versions:
6
frinx-implemented-reader:
io.frinx.unitopo.unit.xr6.lldp.InterfaceReader
frinx-implemented-writer:
MISSING WRITER
frinx-device-type:
ios
frinx-supported-versions:
12any,15any
frinx-implemented-reader:
io.frinx.cli.unit.ios.lldp.handler.InterfaceReader
frinx-implemented-reader-details:
INTERFACE_PATTERN:
(?<interface>^[\S&&[^:]]+):
SHOW_LLDP_INTERFACE:
show lldp interface
frinx-implemented-writer:
MISSING WRITER
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.ios.lldp.handler.InterfaceReader
frinx-implemented-reader-details:
INTERFACE_PATTERN:
(?<interface>^[\S&&[^:]]+):
SHOW_LLDP_INTERFACE:
show lldp interface
frinx-implemented-writer:
MISSING WRITER
frinx-device-type:
nexus
frinx-supported-versions:
any
frinx-implemented-reader:
io.frinx.cli.unit.nexus.lldp.handler.InterfaceReader
frinx-implemented-reader-details:
INTERFACE_PATTERN:
Interface Information: (?<interface>.+) Enable.+
SHOW_LLDP_INTERFACE:
show lldp all
frinx-implemented-writer:
MISSING WRITER
nodetype: list (rw)
list keys: [name]
description:
Reference to the list key
nodetype: leaf (list key) (rw)
type: leafref
description:
Configuration data for LLDP on each interface
frinx-device-type:
xr
frinx-supported-versions:
6
frinx-implemented-reader:
io.frinx.unitopo.unit.xr6.lldp.InterfaceConfigReader
frinx-implemented-writer:
MISSING WRITER
frinx-device-type:
ios
frinx-supported-versions:
12any,15any
frinx-implemented-reader:
io.frinx.cli.unit.ios.lldp.handler.InterfaceConfigReader
frinx-implemented-writer:
MISSING WRITER
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.ios.lldp.handler.InterfaceConfigReader
frinx-implemented-writer:
MISSING WRITER
frinx-device-type:
nexus
frinx-supported-versions:
any
frinx-implemented-reader:
io.frinx.cli.unit.ios.lldp.handler.InterfaceConfigReader
frinx-implemented-writer:
MISSING WRITER
nodetype: container (rw)
description:
Reference to the LLDP Ethernet interface
nodetype: leaf (rw)
type: oc-if:base-interface-ref
description:
Enable or disable the LLDP protocol on the interface.
nodetype: leaf (rw)
type: boolean
description:
Operational state data
nodetype: container (ro)
description:
Reference to the LLDP Ethernet interface
nodetype: leaf (ro)
type: oc-if:base-interface-ref
description:
Enable or disable the LLDP protocol on the interface.
nodetype: leaf (ro)
type: boolean
description:
LLDP counters on each interface
nodetype: container (ro)
description:
The number of lldp frames received.
nodetype: leaf (ro)
type: yang:counter64
description:
The number of frames transmitted out.
nodetype: leaf (ro)
type: yang:counter64
description:
The number of LLDP frames received with errors.
nodetype: leaf (ro)
type: yang:counter64
description:
The number of LLDP frames received and discarded.
nodetype: leaf (ro)
type: yang:counter64
description:
The number of TLV frames received and discarded.
nodetype: leaf (ro)
type: yang:counter64
description:
The number of frames received with unknown TLV.
nodetype: leaf (ro)
type: yang:counter64
description:
Indicates the last time the counters were
cleared.
nodetype: leaf (ro)
type: yang:date-and-time
description:
The number of frame transmit errors on the
interface.
nodetype: leaf (ro)
type: yang:counter64
description:
Enclosing container for list of LLDP neighbors on an
interface
nodetype: container (ro)
description:
List of LLDP neighbors
frinx-device-type:
xr
frinx-supported-versions:
6
frinx-implemented-reader:
io.frinx.unitopo.unit.xr6.lldp.NeighborReader
frinx-implemented-writer:
MISSING WRITER
frinx-device-type:
ios
frinx-supported-versions:
12any,15any
frinx-implemented-reader:
io.frinx.cli.unit.ios.lldp.handler.NeighborReader
frinx-implemented-reader-details:
CHASSIS:
Chassis id: (?<chassis>.+)
KEY_FORMAT:
%s Port:%s
PORT:
Port id: (?<portId>.+)
SHOW_LLDP_NEIGHBOR:
show lldp neighbors %s detail
frinx-implemented-writer:
MISSING WRITER
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.ios.lldp.handler.NeighborReader
frinx-implemented-reader-details:
CHASSIS:
Chassis id: (?<chassis>.+)
KEY_FORMAT:
%s Port:%s
PORT:
Port id: (?<portId>.+)
SHOW_LLDP_NEIGHBOR:
show lldp neighbors %s detail
frinx-implemented-writer:
MISSING WRITER
frinx-device-type:
nexus
frinx-supported-versions:
any
frinx-implemented-reader:
io.frinx.cli.unit.nexus.lldp.handler.NeighborReader
frinx-implemented-reader-details:
CHASSIS:
Chassis id: (?<chassis>.+)
KEY_FORMAT:
%s Port:%s
PORT:
Port id: (?<portId>.+)
SHOW_LLDP_NEIGHBOR:
show lldp neighbors interface %s detail
frinx-implemented-writer:
MISSING WRITER
nodetype: list (ro)
list keys: [id]
description:
nodetype: leaf (list key) (ro)
type: leafref
description:
Configuration data
nodetype: container (ro)
description:
Operational state data
frinx-device-type:
xr
frinx-supported-versions:
6
frinx-implemented-reader:
io.frinx.unitopo.unit.xr6.lldp.NeighborStateReader
frinx-implemented-writer:
MISSING WRITER
frinx-device-type:
ios
frinx-supported-versions:
12any,15any
frinx-implemented-reader:
io.frinx.cli.unit.ios.lldp.handler.NeighborStateReader
frinx-implemented-reader-details:
DESCR:
System Description:\s*\r?\n(?<descr>.+?)\r?\n\r?\n
IP:
(IP|IPv4 address): (?<ip>\S+)
IPV6:
(IPV6|IPv6 address): (?<ip>\S+)
NAME:
System Name: (?<name>\S+)
PORT_DESC:
Port Description: (?<portDescr>.+)
SEPARATOR:
----------
frinx-implemented-writer:
MISSING WRITER
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.ios.lldp.handler.NeighborStateReader
frinx-implemented-reader-details:
DESCR:
System Description:\s*\r?\n(?<descr>.+?)\r?\n\r?\n
IP:
(IP|IPv4 address): (?<ip>\S+)
IPV6:
(IPV6|IPv6 address): (?<ip>\S+)
NAME:
System Name: (?<name>\S+)
PORT_DESC:
Port Description: (?<portDescr>.+)
SEPARATOR:
----------
frinx-implemented-writer:
MISSING WRITER
frinx-device-type:
nexus
frinx-supported-versions:
any
frinx-implemented-reader:
io.frinx.cli.unit.ios.lldp.handler.NeighborStateReader
frinx-implemented-reader-details:
DESCR:
System Description:\s*\r?\n(?<descr>.+?)\r?\n\r?\n
IP:
(IP|IPv4 address): (?<ip>\S+)
IPV6:
(IPV6|IPv6 address): (?<ip>\S+)
NAME:
System Name: (?<name>\S+)
PORT_DESC:
Port Description: (?<portDescr>.+)
SEPARATOR:
----------
frinx-implemented-writer:
MISSING WRITER
nodetype: container (ro)
description:
The system name field shall contain an alpha-numeric string
that indicates the system's administratively assigned name.
The system name should be the system's fully qualified domain
name. If implementations support IETF RFC 3418, the sysName
object should be used for this field.
nodetype: leaf (ro)
type: string
description:
The system description field shall contain an alpha-numeric
string that is the textual description of the network entity.
The system description should include the full name and
version identification of the system's hardware type,
software operating system, and networking software. If
implementations support IETF RFC 3418, the sysDescr object
should be used for this field.
nodetype: leaf (ro)
type: string
description:
The Chassis ID is a mandatory TLV which identifies the
chassis component of the endpoint identifier associated with
the transmitting LLDP agent
nodetype: leaf (ro)
type: string
description:
This field identifies the format and source of the chassis
identifier string. It is an enumerator defined by the
LldpChassisIdSubtype object from IEEE 802.1AB MIB.
nodetype: leaf (ro)
type: oc-lldp-types:chassis-id-type
description:
System generated identifier for the neighbor on the
interface.
nodetype: leaf (ro)
type: string
description:
Age since discovery
nodetype: leaf (ro)
type: uint64
units: seconds
description:
Seconds since last update received.
nodetype: leaf (ro)
type: int64
description:
The Port ID is a mandatory TLV which identifies the port
component of the endpoint identifier associated with the
transmitting LLDP agent. If the specified port is an IEEE
802.3 Repeater port, then this TLV is optional.
nodetype: leaf (ro)
type: string
description:
This field identifies the format and source of the port
identifier string. It is an enumerator defined by the
PtopoPortIdType object from RFC2922.
nodetype: leaf (ro)
type: oc-lldp-types:port-id-type
description:
The binary string containing the actual port identifier for
the port which this LLDP PDU was transmitted. The source and
format of this field is defined by PtopoPortId from
RFC2922.
nodetype: leaf (ro)
type: string
description:
The Management Address is a mandatory TLV which identifies a
network address associated with the local LLDP agent, which
can be used to reach the agent on the port identified in the
Port ID TLV.
nodetype: leaf (ro)
type: string
description:
The enumerated value for the network address type
identified in this TLV. This enumeration is defined in the
'Assigned Numbers' RFC [RFC3232] and the
ianaAddressFamilyNumbers object.
nodetype: leaf (ro)
type: string
description:
Enclosing container for list of custom TLVs from a
neighbor
nodetype: container (ro)
description:
List of custom LLDP TLVs from a neighbor
nodetype: list (ro)
list keys: [type] [oui] [oui-subtype]
description:
Reference to type list key
nodetype: leaf (list key) (ro)
type: leafref
description:
Reference to oui list key
nodetype: leaf (list key) (ro)
type: leafref
description:
Reference to oui-subtype list key
nodetype: leaf (list key) (ro)
type: leafref
description:
Configuration data
nodetype: container (ro)
description:
Operational state data
nodetype: container (ro)
description:
The integer value identifying the type of information
contained in the value field.
nodetype: leaf (ro)
type: int32
description:
The organizationally unique identifier field shall contain
the organization's OUI as defined in Clause 9 of IEEE Std
802. The high-order octet is 0 and the low-order 3 octets
are the SMI Network Management Private Enterprise Code of
the Vendor in network byte order, as defined in the
'Assigned Numbers' RFC [RFC3232].
nodetype: leaf (ro)
type: string
description:
The organizationally defined subtype field shall contain a
unique subtype value assigned by the defining organization.
nodetype: leaf (ro)
type: string
description:
A variable-length octet-string containing the
instance-specific information for this TLV.
nodetype: leaf (ro)
type: binary
description:
Enclosing container for list of LLDP capabilities
nodetype: container (ro)
description:
List of LLDP system capabilities advertised by the
neighbor
nodetype: list (ro)
list keys: [name]
description:
Reference to capabilities list key
nodetype: leaf (list key) (ro)
type: leafref
description:
Configuration data for LLDP capabilities
nodetype: container (ro)
description:
Operational state data for LLDP capabilities
nodetype: container (ro)
description:
Name of the system capability advertised by the neighbor.
Capabilities are represented in a bitmap that defines the
primary functions of the system. The capabilities are
defined in IEEE 802.1AB.
nodetype: leaf (ro)
type: identityref
description:
Indicates whether the corresponding system capability is
enabled on the neighbor.
nodetype: leaf (ro)
type: boolean
This module defines types related to the LLDP protocol model.
frinx-openconfig-extensions
description:
Type definition with enumerations describing the source of
the chassis identifier
type: enumeration
description:
Type definition with enumerations describing the basis of
the port identifier
type: enumeration
description:
A base identity which describes the TLVs in LLDP
description:
The assigned name (sysName or hostname) of the device
which is transmitting the LLDP PDU
base identity: LLDP_TLV
description:
The description of the port that is associated with
the interface on which the LLDP agent is transmitting
base identity: LLDP_TLV
description:
The description (sysDescr) of the device which is
transmitting the LLDP PDU
base identity: LLDP_TLV
description:
The chassis identifier of the device associated with
the transmitting LLDP agent
base identity: LLDP_TLV
description:
The address associated with the device transmitting the
LLDP PDU which can be used for higher-layer network
management
base identity: LLDP_TLV
description:
The port identifier associated with the interface
on with the LLDP agent is transmitting
base identity: LLDP_TLV
description:
The primary functions of the device transmitting the
LLDP PDU and their administrative status
base identity: LLDP_TLV
description:
Base identity for standard LLDP system capabilities.
The system capabilities field contains a bit-map of the
capabilities that define the primary function(s) of
the system. A system may advertise more than one capability.
description:
MAC bridge capability; bit position 3
base identity: LLDP_SYSTEM_CAPABILITY
description:
Two-port MAC Relay (TPMR) capability; bit position 11
base identity: LLDP_SYSTEM_CAPABILITY
description:
Repeater capability; bit position 2
base identity: LLDP_SYSTEM_CAPABILITY
description:
DOCSIS cable device; bit position 7
base identity: LLDP_SYSTEM_CAPABILITY
description:
S-VLAN component of a VLAN Bridge; bit position 10
base identity: LLDP_SYSTEM_CAPABILITY
description:
Telephone capability; bit position 6
base identity: LLDP_SYSTEM_CAPABILITY
description:
Other capability not specified; bit position 1
base identity: LLDP_SYSTEM_CAPABILITY
description:
Router; bit position 5
base identity: LLDP_SYSTEM_CAPABILITY
description:
C-VLAN component of a VLAN Bridge; bit position 9
base identity: LLDP_SYSTEM_CAPABILITY
description:
Station only capability, for devices that implement only an
end station capability, and for which none of the other
capabilities apply; bit position 8
base identity: LLDP_SYSTEM_CAPABILITY
description:
WLAN access point capability; bit position 4
base identity: LLDP_SYSTEM_CAPABILITY
This module describes configuration and operational state data for routes that are locally generated, i.e., not created by dynamic routing protocols. These include static routes, locally created aggregate routes for reducing the number of constituent routes that must be advertised, summary routes for IGPs, etc.
This model expresses locally generated routes as generically as possible, avoiding configuration of protocol-specific attributes at the time of route creation. This is primarily to avoid assumptions about how underlying router implementations handle route attributes in various routing table data structures they maintain. Hence, the definition of locally generated routes essentially creates 'bare' routes that do not have any protocol- specific attributes.
When protocol-specific attributes must be attached to a route (e.g., communities on a locally defined route meant to be advertised via BGP), the attributes should be attached via a protocol-specific policy after importing the route into the protocol for distribution (again via routing policy).
frinx-openconfig-inet-types
frinx-openconfig-policy-types
frinx-openconfig-extensions
frinx-openconfig-interfaces
description:
Pre-defined next-hop designation for locally generated
routes
type: identityref
description:
A base identity type of local defined next-hops
description:
Discard traffic for the corresponding destination
base identity: LOCAL_DEFINED_NEXT_HOP
description:
Treat traffic towards addresses within the specified
next-hop prefix as though they are connected to a local
link. When the LOCAL_LINK next-hop type is specified,
an interface must also be specified such that
the local system can determine which link to trigger
link-layer address discovery against
base identity: LOCAL_DEFINED_NEXT_HOP
Configuration related to constrained-path LSPs and traffic engineering. These definitions are not specific to a particular signaling protocol or mechanism (see related submodules for signaling protocol-specific configuration).
frinx-openconfig-inet-types
frinx-openconfig-mpls-rsvp
frinx-openconfig-mpls-types
frinx-openconfig-types
frinx-openconfig-yang-types
frinx-openconfig-extensions
description:
Enumerated bype for specifying how the SRLG is flooded
type: enumeration
description:
enumerated type for specifying loose or strict
paths
type: enumeration
description:
type to indicate the CSPF selection policy when
multiple equal cost paths are available
type: enumeration
description:
union type for setting the LSP TE metric to a
static value, or to track the IGP metric
type: union
type: enumeration
type: uint32
description:
enumerated type for specifying whether bandwidth is
explicitly specified or automatically computed
type: enumeration
Configuration of Label Distribution Protocol global and LSP- specific parameters for IGP-congruent LSPs. This model reuses data items defined in the IETF YANG model for LDP described by draft-ietf-mpls-ldp-yang-04, YANG Data Model for MPLS LDP, following an alternate structure. Portions of this code were derived from draft-ietf-mpls-ldp-yang-04. Please reproduce this note if possible. IETF code is subject to the following copyright and license: Copyright (c) IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info).
frinx-openconfig-extensions
frinx-openconfig-inet-types
frinx-openconfig-interfaces
frinx-openconfig-yang-types
frinx-openconfig-types
description:
enumerated type for specifying LDP AFIs
type: enumeration
description:
enumerated type for specifying LDP adjacencies
type: enumeration
Configuration for RSVP-TE signaling, including global protocol parameters and LSP-specific configuration for constrained-path LSPs
frinx-openconfig-inet-types
frinx-openconfig-mpls-types
frinx-openconfig-yang-types
frinx-openconfig-types
frinx-openconfig-extensions
frinx-openconfig-interfaces
General types for MPLS / TE data model
frinx-openconfig-extensions
description:
Values of the MPLS Traffic Class (formerly known as
Experimental, EXP) bits
type: uint8
description:
defines the tunnel type for the LSP
type: enumeration
description:
type for MPLS label value encoding
type: union
type: uint32
type: enumeration
description:
Bandwidth values expressed in kilobits per second
type: uint64
units: Kbps
description:
Bandwidth values expressed in megabits per second
type: uint64
units: Mbps
description:
Bandwidth values expressed in gigabits per second
type: uint64
units: Gbps
description:
base identity for protection type
description:
node and link protection are both desired
base identity: PROTECTION_TYPE
description:
no protection is desired
base identity: PROTECTION_TYPE
description:
link protection is desired
base identity: PROTECTION_TYPE
description:
base identity for supported MPLS signaling
protocols
description:
Segment routing
base identity: PATH_SETUP_PROTOCOL
description:
LDP - RFC 5036
base identity: PATH_SETUP_PROTOCOL
description:
RSVP-TE signaling protocol
base identity: PATH_SETUP_PROTOCOL
description:
base identity for supported path computation
mechanisms
description:
constrained-path LSP in which the path is
explicitly specified as a collection of strict or/and loose
hops
base identity: PATH_COMPUTATION_METHOD
description:
indicates a constrained-path LSP in which the
path is computed by the local LER
base identity: PATH_COMPUTATION_METHOD
description:
Constrained-path LSP in which the path is
obtained by querying an external source, such as a PCE server.
In the case that an LSP is defined to be externally queried, it may
also have associated explicit definitions (which are provided to the
external source to aid computation); and the path that is returned by
the external source is not required to provide a wholly resolved
path back to the originating system - that is to say, some local
computation may also be required
base identity: PATH_COMPUTATION_METHOD
description:
Base identity for tunnel administrative status
description:
LSP is administratively down
base identity: TUNNEL_ADMIN_STATUS
description:
LSP is administratively up
base identity: TUNNEL_ADMIN_STATUS
description:
Base identity from which specific tunnel types are
derived.
description:
TE point-to-point tunnel type.
base identity: TUNNEL_TYPE
description:
TE point-to-multipoint tunnel type.
base identity: TUNNEL_TYPE
description:
Base identity from which specific null-label types are
derived.
description:
Explicit null label is used.
base identity: NULL_LABEL_TYPE
description:
Implicit null label is used.
base identity: NULL_LABEL_TYPE
description:
Base identity for LSP operational status
description:
LSP is operationally down or out of service
base identity: LSP_OPER_STATUS
description:
LSP is operationally active and available
for traffic.
base identity: LSP_OPER_STATUS
description:
Base identity for types of LSP metric specification
description:
The metric specified for the LSPs to which this identity refers
is specified as a relative value to the IGP metric cost to the
LSP's tail-end.
base identity: LSP_METRIC_TYPE
description:
The metric for for the LSPs to which this identity refers is
not specified explicitly - but rather inherited from the IGP
cost directly
base identity: LSP_METRIC_TYPE
description:
The metric specified for the LSPs to which this identity refers
is specified as an absolute value
base identity: LSP_METRIC_TYPE
description:
Base identity for describing the role of
label switched path at the current node
description:
Label switched path is an ingress (headend)
LSP
base identity: LSP_ROLE
description:
Label switched path is an egress (tailend)
LSP
base identity: LSP_ROLE
description:
Label switched path is a transit LSP
base identity: LSP_ROLE
This module contains groupings which specifically relate to Layer 2 network instance configuration and operational state parameters.
frinx-openconfig-extensions
frinx-openconfig-interfaces
ietf-yang-types
This module contains groupings which specifically relate to Layer 2 network instance configuration and operational state parameters.
frinx-openconfig-extensions
frinx-openconfig-types
This module defines routing policy statements (conditions and actions) for the network instance model. These statements are generally added to the routing policy model.
frinx-openconfig-extensions
frinx-openconfig-routing-policy
frinx-openconfig-policy-types
network-topology
frinx-uniconfig-topology
Types associated with a network instance
frinx-openconfig-extensions
description:
A route distinguisher value
type: union
type: string
type: string
type: string
description:
The signalling protocol that should be used to diseminate
entries within a forwarding instance
description:
Use BGP-based signalling and autodiscovery for VPLS instances
as per RFC4761
base identity: SIGNALLING_PROTOCOL
description:
Use LDP-based setup for signalling. Where the instance is
a point-to-point service this refers to RFC4447 ('Martini')
setup. Where the service is an L2VSI, or L2L3 instance it
refers to RFC4762 LDP-signalled VPLS instances
base identity: SIGNALLING_PROTOCOL
description:
Use BGP-based Ethernet VPN (RFC7432) based signalling for
the network instance
base identity: SIGNALLING_PROTOCOL
description:
Base identity to be used to express types of label allocation
strategies to be used within a network instance
description:
A single label is to be used for the instance
base identity: LABEL_ALLOCATION_MODE
description:
A label is to be allocated per prefix entry in the RIB for the
network instance
base identity: LABEL_ALLOCATION_MODE
description:
A label is to be allocated per nexthop entry in the RIB for
the network instance
base identity: LABEL_ALLOCATION_MODE
description:
Specification of the type of endpoint that is being associated
with a network instance
description:
A local interface which is being associated with the endpoint
base identity: ENDPOINT_TYPE
description:
A remote interface which is being associated with the
endpoint
base identity: ENDPOINT_TYPE
description:
On the wire encapsulations that can be used when
differentiating network instances
description:
Use MPLS labels to distinguish network instances on the wire
base identity: ENCAPSULATION
description:
Use VXLAN (RFC7348) VNIs to distinguish network instances on
the wire
base identity: ENCAPSULATION
description:
A base identity which can be extended to indicate different
types of network instance supported by a device.
description:
A private Layer 2 only switch instance which is formed of
one or more L2 forwarding tables
base identity: NETWORK_INSTANCE_TYPE
description:
A private Layer 3 only routing instance which is formed of
one or more RIBs
base identity: NETWORK_INSTANCE_TYPE
description:
A special routing instance which acts as the 'default' or
'global' routing instance for a network device.
base identity: NETWORK_INSTANCE_TYPE
description:
A private Layer 2 and Layer 2 forwarding instance
base identity: NETWORK_INSTANCE_TYPE
description:
A private Layer 2 only forwarding instance which acts as
a point to point connection between two endpoints
base identity: NETWORK_INSTANCE_TYPE
This module defines extensions to the OpenConfig policy model to add extensions for OSPF. This module is intended to be generic for both OSPFv2 and OSPFv3.
frinx-openconfig-routing-policy
frinx-openconfig-extensions
frinx-openconfig-ospf-types
network-topology
frinx-uniconfig-topology
Type definitions for OSPF
ietf-yang-types
frinx-openconfig-extensions
description:
A common type that can be utilised to express an OSPF metric
type: uint16
description:
An identifier for an area with OSPF version 2 or 3. This value
is expressed as either a dotted-quad, or a unsigned 32-bit
number
type: union
type: uint32
type: yang:dotted-quad
description:
A common type used to express the type of segment identifier that is
used in LSDB entries relating to segment routing
type: enumeration
description:
This identity is used as the base for TLVs within the Grace LSA
description:
This sub-TLV describes the period for which adjacencies should be
maintained with the restarting system
base identity: GRACE_LSA_TLV_TYPES
description:
This sub-TLV describes the reason for the OSPF restart of the system
that is restarting
base identity: GRACE_LSA_TLV_TYPES
description:
This sub-TLV specifies the restarting system's IP address on the
interface via which it is advertising the Grace LSA
base identity: GRACE_LSA_TLV_TYPES
description:
Sub-TLV types carried in the SID/Label Binding Sub-TLV of
the Extended Prefix Sub-TLV
description:
This sub-TLV indicates a binding between an SR SID and an
MPLS label and must be present in the sub-TLV
base identity: OSPFV2_EXTENDED_PREFIX_SID_LABEL_BINDING_SUBTLV_TYPE
description:
This sub-TLV indicates the cost of the ERO path being
advertised in the SID/Label TLV
base identity: OSPFV2_EXTENDED_PREFIX_SID_LABEL_BINDING_SUBTLV_TYPE
description:
This sub-TLV indicates the path associated with an ERO
being advertised in the SID/Label TLV
base identity: OSPFV2_EXTENDED_PREFIX_SID_LABEL_BINDING_SUBTLV_TYPE
description:
Sub-TLVs of the Extended Link TLV for OSPFv2
description:
The extended link sub-TLV indicates an Adjacency SID
base identity: OSPFV2_EXTENDED_LINK_SUBTLV_TYPE
description:
OSPFv2 Router Link Types as per the IANA registry defined in
RFC2740
description:
The link is a virtual connection to another router
base identity: OSPFV2_ROUTER_LINK_TYPE
description:
The link is a connection to a transit network
base identity: OSPFV2_ROUTER_LINK_TYPE
description:
The link is a point-to-point connection to another router
base identity: OSPFV2_ROUTER_LINK_TYPE
description:
The link is a connection to a stub network
base identity: OSPFV2_ROUTER_LINK_TYPE
description:
Triggers which cause the maximum metric to be set for
entities advertised in OSPF
description:
Set the maximum metric when the system boots.
base identity: MAX_METRIC_TRIGGER
description:
This identity is the based used for the type field for sub-TLVs of the
Link TLV of the OSPF Traffic Engineering Opaque LSA
description:
The OSPF-TE Local IP specifies a list of the interface addresses of the
local system corresponding to the traffic engineering link.
base identity: OSPF_TE_LINK_TLV_TYPE
description:
The OSPF-TE Maximum Bandwidth specifies the maximum bandwidth of the
link that it is associated with.
base identity: OSPF_TE_LINK_TLV_TYPE
description:
The OSPF-TE administrative group indicates the administrative group
that the is assigned to the interface
base identity: OSPF_TE_LINK_TLV_TYPE
description:
The OSPF-TE Link Type sub-TLV appears exactly once per OSPF-TE Link
and describes the type of the link
base identity: OSPF_TE_LINK_TLV_TYPE
description:
The OSPF-TE Metric specifies the link metric for traffic engineering
purposes
base identity: OSPF_TE_LINK_TLV_TYPE
description:
The OSPF-TE unreserved bandwidth indicates the amount of bandwidth
at each priority level that is currently not reserved
base identity: OSPF_TE_LINK_TLV_TYPE
description:
The OSPF-TE Maximum Reservable Bandwidth specifies the maximum
bandwidth that may be reserved on the link in bytes per second
base identity: OSPF_TE_LINK_TLV_TYPE
description:
The OSPF-TE Remote IP specifies a list of IP addresses of the remote
neighbors associated with the traffic engineering link.
base identity: OSPF_TE_LINK_TLV_TYPE
description:
The OSPF-TE Link ID sub-TLV appears exactly once per OSPF-TE link and
identifies the remote end of the link.
base identity: OSPF_TE_LINK_TLV_TYPE
description:
Base identity for an OSPF LSA type. This identity is intended
to be used across both OSPFv2 and OSPFv3. Identity values that
correspond to only one OSPF version are marked as such.
description:
Type 10 - OSPFV2_AREA_SCOPE_OPAQUE_LSA. This LSA type is used
in OSPFv2 to distribute arbitrary information via the OSPF
protocol. The contents is specific to the application defining
the Opaque Type specified within the LSDB. LSAs with Type 10 have
a scope of the area that they are transmitted within.
base identity: OSPF_LSA_TYPE
description:
Type 1 - ROUTER_LSA. An LSA originated by each router within
the area describing the state and cost of the router's links
in the area.
base identity: OSPF_LSA_TYPE
description:
Type 5 - AS_EXTERNAL_LSA. This LSA type is used to describe
destinations external to the autonomous system, and is
originated by an AS boundary router (ASBR).
base identity: OSPF_LSA_TYPE
description:
Type 9 - OSPFV2_LINK_SCOPE_OPAQUE_LSA. This LSA type is used
in OSPFv2 to distribute arbitrary information via the OSPF
protocol. The contents is specific to the application defining
the Opaque Type specified within the LSDB. LSAs with Type 9 have
a scope of the link that they are being transmitted on (and the
associated network or subnetwork).
base identity: OSPF_LSA_TYPE
description:
Type 4 - SUMMARY_ASBR_LSA. An LSA originated by an area border
router describing inter-area destinations. This LSA type is used
when the destination is an AS boundary router.
base identity: OSPF_LSA_TYPE
description:
Type 7 - NSSA_AS_EXTERNAL_LSA. This LSA type is used by
systems within a not-so-stubby-area (NSSA) to inject external
prefixes into the LSDB. They are translated to Type 5 LSAs
at an ABR device.
base identity: OSPF_LSA_TYPE
description:
Type 2 - NETWORK_LSA. An LSA originated for each broadcast and
non-broadcast multiple access (NBMA) in the area. This LSA is
originated by the designated router.
base identity: OSPF_LSA_TYPE
description:
Type 3 - SUMMARY_IP_NETWORK_LSA. An LSA originated by area
border routers describing inter-area destinations. This LSA type
is used when the destination is an IP network
base identity: OSPF_LSA_TYPE
description:
Type 11 - OSPFV2_AS_SCOPE_OPAQUE_LSA. This LSA type is used
in OSPFv2 to distribute arbitrary information via the OSPF
protocol. The contents is specific to the application defining
the Opaque Type specified within the LSDB. LSAs with Type 11
have a scope of the autonomous system that they are transmitted
within.
base identity: OSPF_LSA_TYPE
description:
The state of an adjacency between the local system and a remote
device
description:
An adjacency with the remote system is being formed. The local
system is currently transmitting empty database description
packets in order to establish the master/slave relationship for
the adjacency.
base identity: OSPF_NEIGHBOR_STATE
description:
The local system is sending Link State Request packets to the
remote system in order to receive the more recently LSAs that
were discovered during the Exchange phase of the procedure
establishing the adjacency.
base identity: OSPF_NEIGHBOR_STATE
description:
Utilised for neighbors that are attached to NBMA networks, it
indicates that no information has been recently received from
the neighbor but that Hello packets should be directly sent
to that neighbor.
base identity: OSPF_NEIGHBOR_STATE
description:
The local and remote systems are currently exchanging database
description packets in order to determine which elements of
their local LSDBs are out of date.
base identity: OSPF_NEIGHBOR_STATE
description:
The initial state of a neighbor, indicating that no recent
information has been received from the neighbor.
base identity: OSPF_NEIGHBOR_STATE
description:
Indicates that a Hello packet has been received from the
neighbor but bi-directional communication has not yet been
established. That is to say that the local Router ID does
not appear in the list of neighbors in the remote system's
Hello packet.
base identity: OSPF_NEIGHBOR_STATE
description:
The neighboring routers are fully adjacent such that both
LSDBs are synchronized. The adjacency will appear in Router and
Network LSAs
base identity: OSPF_NEIGHBOR_STATE
description:
Communication between the local and remote system is
bi-directional such that the local system's Router ID is listed
in the received remote system's Hello packet.
base identity: OSPF_NEIGHBOR_STATE
description:
The types of segment included within an ERO Path described
within the SID/Label binding sub-TLV
description:
The segment is specified as an IPv4 address
base identity: OSPFV2_EXTPREFIX_BINDING_ERO_PATH_SEGMENT_TYPE
description:
The segment is specified as an unnumbered interface of
a remote system
base identity: OSPFV2_EXTPREFIX_BINDING_ERO_PATH_SEGMENT_TYPE
description:
This identity is used as a base for the algorithms that can be
supported for segment routing and are advertised by a system in the RI
LSA
description:
The standard shortest path algorithm based on link metric, with the
requirement that all nodes along the path honor the SPF decision. That
is to say that the SPF decision cannot be altered by local policy at
the node
base identity: SR_ALGORITHM
description:
The standard shortest path algorithm based on link metric,
as used by the OSPF protocol
base identity: SR_ALGORITHM
description:
This identity is used as the base for the TLVs within the Router
Information LSA
description:
The algorithms that are supported for segment routing by the
advertising system
base identity: RI_LSA_TLV_TYPES
description:
Functional capabilities of the advertising system
base identity: RI_LSA_TLV_TYPES
description:
Operator-defined administrative tags associated with the advertising
system
base identity: RI_LSA_TLV_TYPES
description:
Informational capabilities of the advertising system
base identity: RI_LSA_TLV_TYPES
description:
SID or Label ranges for use with segment routing when forwarding to
the advertising system
base identity: RI_LSA_TLV_TYPES
description:
Sub-TLVs of the OSPFv2 Extended Prefix LSA as defined by
RFC7684
description:
The TLV describes a Segment Routing Prefix Segment Identifier
associated with a prefix
base identity: OSPFV2_EXTENDED_PREFIX_SUBTLV_TYPE
description:
The TLV describes a binding of a SID to a path to the prefix,
which may have associated path characteristics
base identity: OSPFV2_EXTENDED_PREFIX_SUBTLV_TYPE
description:
The attributes being described relate to a range of prefixes
base identity: OSPFV2_EXTENDED_PREFIX_SUBTLV_TYPE
description:
This identity is the base used for opaque LSA types. The values
that extend this base are those that are described in the IANA
OSPF Opaque Link-State Advertisements (LSA) Option Types registry
description:
Grace LSAs are announced by a system undergoing graceful-restart.
A system that is attempting an OSPF graceful restart announces
Grace-LSAs with a specified grace period, indicating the intention
to have completed an restart within the specified period.
base identity: OSPF_OPAQUE_LSA_TYPE
description:
The Traffic Engineering LSA. This type is used only with area-scope
Opaque LSAs - and is used to describe routers, point-to-point links
and connections to multi-access networks for traffic engineering
purposes.
base identity: OSPF_OPAQUE_LSA_TYPE
description:
The Router Information LSA is used by an OSPFv2 system to announce
optional capabilities of the local system, over and above those that
are included within the OSPF hello message field. The flooding scope
of the LSA can be link-, area-, or AS-wide (i.e., the LSA type can
be 9, 10 or 11).
base identity: OSPF_OPAQUE_LSA_TYPE
description:
The Extended Prefix LSA is used in OSPFv2 to carry a set of attributes
that are to be associated with a prefix that is advertised in OSPF. The
attributes are carried as one or more TLV tuples. The flooding scope
of the LSA can be link-, area-, or AS-wide as specified by the
advertising system. The flooding scope of the LSA may exceed the scope
of the corresponding prefix.
base identity: OSPF_OPAQUE_LSA_TYPE
description:
The Extended Link LSA is used in OSPFv2 to carry a set of attributes
that are to be associated with a link that is advertised in OSPF. The
link attributes are carried as one or more TLV tuples. The flooding
scope of the link LSA is area-local - i.e., it is carried in a Type 10
opaque LSA.
base identity: OSPF_OPAQUE_LSA_TYPE
description:
Entities that may optionally be included when advertising
the maximum metric.
description:
Include OSPF Type 2 external routes when advertising
the maximum metric.
base identity: MAX_METRIC_INCLUDE
description:
Include stub networks when advertising the maximum metric.
base identity: MAX_METRIC_INCLUDE
description:
This identity is used as a base for the sub-TLVs of the Segment
Routing SID/Label Range TLV
description:
A range of SID/Label values used by the local system
base identity: OSPF_RI_SR_SID_LABEL_TLV_TYPES
description:
Types of network that OSPF should consider attached to an
interface
description:
A interface that connects two routers.
base identity: OSPF_NETWORK_TYPE
description:
An interface that supports >2 attached routers which has the
ability to address all connected systems via a single
(broadcast) address.
base identity: OSPF_NETWORK_TYPE
description:
An interface that supports >2 attached rotuers which does not
have the ability to address all connected systems with a
broadcast address.
base identity: OSPF_NETWORK_TYPE
description:
Sub-types of the router LSA
description:
The LSA represents a point-to-point connection to another
router
base identity: ROUTER_LSA_TYPES
description:
The LSA represents a connection to a transit network
base identity: ROUTER_LSA_TYPES
description:
The LSA represents a connection to a stub network
base identity: ROUTER_LSA_TYPES
description:
The LSA represents a virtual link connection
base identity: ROUTER_LSA_TYPES
description:
This identity is the base used for the type field of TLVs that are
included within the Traffic Engineering Opaque LSA.
description:
A single link within a traffic engineering topology. A set of sub-TLVs
are carried within this attribute to indicate traffic engineering
characteristics of the link.
base identity: OSPF_TE_LSA_TLV_TYPE
description:
Attributes associated with the local link by the system.
base identity: OSPF_TE_LSA_TLV_TYPE
description:
A stable IPv6 address of the advertising router that is always
reachable if the node has connectivity. This TLV is used only with
OSPFv3
base identity: OSPF_TE_LSA_TLV_TYPE
description:
Attributes associted with the local system
base identity: OSPF_TE_LSA_TLV_TYPE
description:
Attributes associated with the local optical node. A set of sub-TLVs
are carried within this TLV which are used within the GMPLS control
plane when using OSPF
base identity: OSPF_TE_LSA_TLV_TYPE
description:
A stable IP address of the advertising router that is always reachable
if the node has connectivity.
base identity: OSPF_TE_LSA_TLV_TYPE
description:
This identity forms the base for sub-TLVs of the Node Attribute TLV
of the Traffic Engineering LSA
description:
The Node Attribute Sub-TLV contains a list of the IPv6 addresses of
the local system
base identity: TE_NODE_ATTRIBUTE_TLV_TYPE
description:
The Node Attribute Sub-TLV contains a list of the IPv4 addresses of
the local system
base identity: TE_NODE_ATTRIBUTE_TLV_TYPE
An OpenConfig model for the Open Shortest Path First (OSPF) version 2 link-state database (LSDB)
ietf-yang-types
ietf-inet-types
frinx-openconfig-types
frinx-openconfig-extensions
frinx-openconfig-ospf-types
This module defines data related to packet header fields used in matching operations, for example in ACLs. When a field is omitted from a match expression, the effect is a wildcard ('any') for that field.
frinx-openconfig-inet-types
frinx-openconfig-yang-types
frinx-openconfig-packet-match-types
frinx-openconfig-extensions
This module defines common types for use in models requiring data definitions related to packet matches.
frinx-openconfig-inet-types
frinx-openconfig-extensions
description:
Port numbers may be represented as a single value,
an inclusive range as
type: union
type: string
type: oc-inet:port-number
type: enumeration
description:
The Ethertype value may be expressed as a 16-bit number in
hexadecimal notation, or using a type defined by the
ETHERTYPE identity
type: union
type: uint16
type: identityref
description:
The IP protocol number may be expressed as a valid protocol
number (integer) or using a protocol type defined by the
IP_PROTOCOL identity
type: union
type: uint8
type: identityref
description:
Base identity for commonly used IP protocols used in
packet header matches
description:
Authentication header, e.g., for IPSEC (51)
base identity: IP_PROTOCOL
description:
Generic Routing Encapsulation (47)
base identity: IP_PROTOCOL
description:
User Datagram Protocol (17)
base identity: IP_PROTOCOL
description:
Protocol Independent Multicast (103)
base identity: IP_PROTOCOL
description:
Transmission Control Protocol (6)
base identity: IP_PROTOCOL
description:
Resource Reservation Protocol (46)
base identity: IP_PROTOCOL
description:
Layer Two Tunneling Protocol v.3 (115)
base identity: IP_PROTOCOL
description:
Internet Group Membership Protocol (2)
base identity: IP_PROTOCOL
description:
Internet Control Message Protocol (1)
base identity: IP_PROTOCOL
description:
Common TCP flags used in packet header matches
description:
TCP FIN flag
base identity: TCP_FLAGS
description:
TCP RST flag
base identity: TCP_FLAGS
description:
TCP ECN-Echo flag. If the SYN flag is set, indicates that
the TCP peer is ECN-capable, otherwise indicates that a
packet with Congestion Experienced flag in the IP header
is set
base identity: TCP_FLAGS
description:
TCP urgent flag
base identity: TCP_FLAGS
description:
TCP SYN flag
base identity: TCP_FLAGS
description:
TCP Congestion Window Reduced flag
base identity: TCP_FLAGS
description:
TCP ACK flag
base identity: TCP_FLAGS
description:
TCP push flag
base identity: TCP_FLAGS
description:
Base identity for commonly used Ethertype values used
in packet header matches on Ethernet frames. The Ethertype
indicates which protocol is encapsulated in the Ethernet
payload.
description:
RDMA over Converged Ethernet (0x8915)
base identity: ETHERTYPE
description:
IPv4 protocol (0x0800)
base identity: ETHERTYPE
description:
IPv6 protocol (0x86DD)
base identity: ETHERTYPE
description:
Address resolution protocol (0x0806)
base identity: ETHERTYPE
description:
VLAN-tagged frame (as defined by IEEE 802.1q) (0x8100). Note
that this value is also used to represent Shortest Path
Bridging (IEEE 801.1aq) frames.
base identity: ETHERTYPE
description:
Link Layer Discovery Protocol (0x88CC)
base identity: ETHERTYPE
description:
MPLS unicast (0x8847)
base identity: ETHERTYPE
This module defines configuration and operational state data relating to policy-based forwarding. Policy-based forwarding is utilised when a system chooses how to forward packets (including applying data-plane operations such as encapsulation or decapsulation) based on policies other than destination L2 or L3 header. Typically, systems may implement:
- IP policy-based routing, where routing may be done based on the source plus destination of an IP packet; information within the L4 header; or some combination of both. - Encapsulation or decapsulation based on certain policy information - for example, matching particular IP destinations and decapsulating GRE headers. - Class-based selection of egress routes - such as class-based selection of an egress MPLS path.
The policies that are defined in this model are applied to a particular ingress context of a network element (e.g., interface) and are defined to apply following other interface policy such as QoS classification and access control lists.
This module defines:
- policy-forwarding | |--- policies | |-- policy | |-- [match criteria] How packets are defined to | | match policy. | |-- [forwarding-action] How packets matching should | be forwarded. |--- interfaces | |-- interfaces | | -- apply-forwarding-policy Forwarding policy to | used on the interface. |--- path-selection-groups |-- path-selection-group A group of forwarding resources that are grouped for purposes of next-hop selection.
A forwarding-policy specifies the match criteria that it intends to use to determine the packets that it reroutes - this may consist of a number of criteria, such as DSCP. The action of the policy results in a forwarding action being applied to matching packets. For example, decapsulating the packet from a GRE header. In order to enact the policy based on particular interfaces - the forwarding-policy is applied to an interface via referencing it within an 'apply-forwarding-policy' statement associated with an interface.
In some cases (e.g., Class-Based Tunnel Selection) the forwarding action does not resolve to a single egress action, and rather normal forwarding rules are to be applied but considering a subset of forwarding resources. In these cases, a path-selection-group can be created, referencing the subset of forwarding paths that should be used for the egress selection. In the case that a subset of MPLS LSPs are eligible for, say, DSCP 46 marked packets, a path-selection-group is created, referencing the subset of LSPs. The forwarding action of the corresponding policy is set to PATH_GROUP and references the configured group of LSPs.
frinx-openconfig-extensions
This module defines a data model for representing a system component inventory, which can include hardware or software elements arranged in an arbitrary structure. The primary relationship supported by the model is containment, e.g., components containing subcomponents.
It is expected that this model reflects every field replacable unit on the device at a minimum (i.e., additional information may be supplied about non-replacable components).
Every element in the inventory is termed a 'component' with each component expected to have a unique name and type, and optionally a unique system-assigned identifier and FRU number. The uniqueness is guaranteed by the system within the device.
Components may have properties defined by the system that are modeled as a list of key-value pairs. These may or may not be user-configurable. The model provides a flag for the system to optionally indicate which properties are user configurable.
Each component also has a list of 'subcomponents' which are references to other components. Appearance in a list of subcomponents indicates a containment relationship as described above. For example, a linecard component may have a list of references to port components that reside on the linecard.
This schema is generic to allow devices to express their own platform-specific structure. It may be augmented by additional component type-specific schemas that provide a common structure for well-known component types. In these cases, the system is expected to populate the common component schema, and may optionally also represent the component and its properties in the generic structure.
The properties for each component may include dynamic values, e.g., in the 'state' part of the schema. For example, a CPU component may report its utilization, temperature, or other physical properties. The intent is to capture all platform- specific physical data in one location, including inventory (presence or absence of a component) and state (physical attributes or status).
frinx-openconfig-platform-types
frinx-openconfig-interfaces
frinx-openconfig-extensions
network-topology
frinx-uniconfig-topology
description:
Enclosing container for the components in the system.
nodetype: container (rw)
description:
List of components, keyed by component name.
frinx-device-type:
ios
frinx-supported-versions:
12any,15any
frinx-implemented-reader:
io.frinx.cli.unit.platform.handler.ComponentReader
frinx-implemented-reader-details:
LINE:
\s*(?<index>\d+)\s+(?<ports>\d+)\s+(?<type>.+)\s+(?<model>\S+)\s+(?<serial>\S+)\s*
LINE_HW_SW_FW:
\s*(?<index>\d+)\s+(?<macs>.+)\s+(?<hw>\S+)\s+(?<fw>\S+)\s+(?<sw>\S+)\s+(?<status>\S+)\s*
SEPARATOR:
^\s+Mod\s+
SH_MODULE:
show module
frinx-implemented-writer:
MISSING WRITER
frinx-device-type:
xr
frinx-supported-versions:
6
frinx-implemented-reader:
io.frinx.unitopo.unit.xr6.platform.handler.ComponentReader
frinx-implemented-reader-details:
LINE_CARD_PATTERN:
.*Line Card.*
frinx-implemented-writer:
MISSING WRITER
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.platform.handler.XrOsComponentReader
frinx-implemented-reader-details:
LINE:
\s*NAME: "(?<name>[^"]+)"\s*, DESCR: "(?<descr>[^"]+)"\s*, PID: (?<pid>[^,]*)\s*, VID: (?<vid>[^,]*)\s*, SN: ?(?<sn>\S*)\s*
SH_MODULE:
show inventory all
frinx-implemented-writer:
MISSING WRITER
frinx-device-type:
vrp
frinx-supported-versions:
any
frinx-implemented-reader:
io.frinx.cli.unit.huawei.platform.handler.ComponentReader
frinx-implemented-reader-details:
LINE:
^BoardType=(?<type>\S+)$\s*^BarCode=(?<sn>.+)$\s*^Item=(?<item>.*)$\s*^Description=(?<descr>.*)$\s*^Manufactured=(?<date>.*)$\s*^VendorName=(?<vendor>.*)$\s*^?(IssueNumber=)?(?<issue>.*)$?\s*^CLEICode=(?<clei>.*)$\s*^BOM=(?<bom>.*)$\s*
SH_MODULE:
display elabel
frinx-implemented-writer:
MISSING WRITER
nodetype: list (rw)
list keys: [name]
description:
References the component name
nodetype: leaf (list key) (rw)
type: leafref
description:
Configuration data for each component
frinx-device-type:
ios
frinx-supported-versions:
12any,15any
frinx-implemented-reader:
io.frinx.cli.unit.platform.handler.ComponentConfigReader
frinx-implemented-writer:
MISSING WRITER
frinx-device-type:
xr
frinx-supported-versions:
6
frinx-implemented-reader:
io.frinx.unitopo.unit.xr6.platform.handler.ComponentConfigReader
frinx-implemented-writer:
MISSING WRITER
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.platform.handler.XrOsComponentConfigReader
frinx-implemented-writer:
MISSING WRITER
frinx-device-type:
vrp
frinx-supported-versions:
any
frinx-implemented-reader:
io.frinx.cli.unit.huawei.platform.handler.ComponentConfigReader
frinx-implemented-writer:
MISSING WRITER
nodetype: container (rw)
description:
Device name for the component -- this will not be a
configurable parameter on many implementations
nodetype: leaf (rw)
type: string
description:
Operational state data for each component
frinx-device-type:
ios
frinx-supported-versions:
12any,15any
frinx-implemented-reader:
io.frinx.cli.unit.platform.handler.ComponentStateReader
frinx-implemented-reader-details:
ID_COMP:
Cisco\s(?<id>.+)\sSoftware,.*
LINE_SW:
^(?<name>.+), Version (?<version>.+),\s.*
SH_MODULE_SINGLE:
show module %s
SH_MODULE_VERSION:
show version
frinx-implemented-writer:
MISSING WRITER
frinx-device-type:
xr
frinx-supported-versions:
6
frinx-implemented-reader:
io.frinx.unitopo.unit.xr6.platform.handler.ComponentStateReader
frinx-implemented-writer:
MISSING WRITER
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.platform.handler.XrOsComponentStateReader
frinx-implemented-reader-details:
ID_COMP:
Cisco\s(?<id>.+)\sSoftware,.*
SH_MODULE_VERSION:
show version
VERSION:
.*Version (?<version>.+)
frinx-implemented-writer:
MISSING WRITER
frinx-device-type:
vrp
frinx-supported-versions:
any
frinx-implemented-reader:
io.frinx.cli.unit.huawei.platform.handler.ComponentStateReader
frinx-implemented-reader-details:
ID_COMP:
Huawei\s(?<id>.+)\sSoftware
LINE_SW:
.+, Version (?<version>.+)
SH_VERSION:
display version
frinx-implemented-writer:
MISSING WRITER
nodetype: container (ro)
description:
Device name for the component -- this will not be a
configurable parameter on many implementations
nodetype: leaf (ro)
type: string
description:
Type of component as identified by the system
nodetype: leaf (ro)
type: union
type: identityref
type: identityref
description:
Unique identifier assigned by the system for the
component
nodetype: leaf (ro)
type: string
description:
System-supplied description of the component
nodetype: leaf (ro)
type: string
description:
System-supplied identifier for the manufacturer of the
component. This data is particularly useful when a
component manufacturer is different than the overall
device vendor.
nodetype: leaf (ro)
type: string
description:
System-defined version string for a hardware, firmware,
or software component.
nodetype: leaf (ro)
type: string
description:
For hardware components, this is the hardware revision of
the component.
nodetype: leaf (ro)
type: string
description:
For hardware components, this is the version of associated
firmware that is running on the component, if applicable.
nodetype: leaf (ro)
type: string
description:
For software components such as operating system or other
software module, this is the version of the currently
running software.
nodetype: leaf (ro)
type: string
description:
System-assigned serial number of the component.
nodetype: leaf (ro)
type: string
description:
System-assigned part number for the component. This should
be present in particular if the component is also an FRU
(field replaceable unit)
nodetype: leaf (ro)
type: string
description:
If true, this component is removable or is a field
replaceable unit
nodetype: leaf (ro)
type: boolean
description:
Temperature in degrees Celsius of the component. Values include
the instantaneous, average, minimum, and maximum statistics. If
avg/min/max statistics are not supported, the target is expected
to just supply the instant value
nodetype: container (ro)
description:
The instantaneous value of the statistic.
nodetype: leaf (ro)
type: decimal64
units: celsius
description:
The arithmetic mean value of the statistic over the
sampling period.
nodetype: leaf (ro)
type: decimal64
units: celsius
description:
The minimum value of the statistic over the sampling
period
nodetype: leaf (ro)
type: decimal64
units: celsius
description:
The maximum value of the statistic over the sampling
period
nodetype: leaf (ro)
type: decimal64
units: celsius
description:
A value of true indicates the alarm has been raised or
asserted. The value should be false when the alarm is
cleared.
nodetype: leaf (ro)
type: boolean
description:
The threshold value that was crossed for this alarm.
nodetype: leaf (ro)
type: uint32
description:
For components that have associated memory, these values
report information about available and utilized memory.
nodetype: container (ro)
description:
The available memory physically installed, or logically
allocated to the component.
nodetype: leaf (ro)
type: uint64
units: bytes
description:
The memory currently in use by processes running on
the component, not considering reserved memory that is
not available for use.
nodetype: leaf (ro)
type: uint64
units: bytes
description:
Power allocated by the system for the component.
nodetype: leaf (ro)
type: uint32
units: watts
description:
Actual power used by the component.
nodetype: leaf (ro)
type: uint32
units: watts
description:
Enclosing container
nodetype: container (rw)
description:
List of system properties for the component
nodetype: list (rw)
list keys: [name]
description:
Reference to the property name.
nodetype: leaf (list key) (rw)
type: leafref
description:
Configuration data for each property
nodetype: container (rw)
description:
System-supplied name of the property -- this is typically
non-configurable
nodetype: leaf (rw)
type: string
description:
Property values can take on a variety of types. Signed and
unsigned integer types may be provided in smaller sizes,
e.g., int8, uint16, etc.
nodetype: leaf (rw)
type: union
type: string
type: int64
type: uint64
type: decimal64
description:
Operational state data for each property
nodetype: container (ro)
description:
System-supplied name of the property -- this is typically
non-configurable
nodetype: leaf (ro)
type: string
description:
Property values can take on a variety of types. Signed and
unsigned integer types may be provided in smaller sizes,
e.g., int8, uint16, etc.
nodetype: leaf (ro)
type: union
type: string
type: int64
type: uint64
type: decimal64
description:
Indication whether the property is user-configurable
nodetype: leaf (ro)
type: boolean
description:
Enclosing container for subcomponent references
nodetype: container (rw)
description:
List of subcomponent references
nodetype: list (rw)
list keys: [name]
description:
Reference to the name list key
nodetype: leaf (list key) (rw)
type: leafref
description:
Configuration data
nodetype: container (rw)
description:
Reference to the name of the subcomponent
nodetype: leaf (rw)
type: string
description:
Operational state data
nodetype: container (ro)
description:
Reference to the name of the subcomponent
nodetype: leaf (ro)
type: string
description:
Data for chassis components
nodetype: container (rw)
description:
Configuration data for chassis components
nodetype: container (rw)
description:
Operational state data for chassis components
nodetype: container (ro)
description:
Data for physical port components
nodetype: container (rw)
description:
Configuration data for physical port components
nodetype: container (rw)
description:
Operational state data for physical port components
nodetype: container (ro)
description:
Data for power supply components
nodetype: container (rw)
description:
Configuration data for power supply components
nodetype: container (rw)
description:
Operational state data for power supply components
nodetype: container (ro)
description:
Data for fan components
nodetype: container (rw)
description:
Configuration data for fan components
nodetype: container (rw)
description:
Operational state data for fan components
nodetype: container (ro)
description:
Data for fabric components
nodetype: container (rw)
description:
Configuration data for fabric components
nodetype: container (rw)
description:
Operational state data for fabric components
nodetype: container (ro)
description:
Data for storage components
nodetype: container (rw)
description:
Configuration data for storage components
nodetype: container (rw)
description:
Operational state data for storage components
nodetype: container (ro)
description:
Data for cpu components
nodetype: container (rw)
description:
Configuration data for cpu components
nodetype: container (rw)
description:
Operational state data for cpu components
nodetype: container (ro)
description:
Data for chip components, such as ASIC, NPUs, etc.
nodetype: container (rw)
description:
Configuration data for chip components
nodetype: container (rw)
description:
Operational state data for chip components
nodetype: container (ro)
description:
Data for backplane components
nodetype: container (rw)
description:
Configuration data for backplane components
nodetype: container (rw)
description:
Operational state data for backplane components
nodetype: container (ro)
description:
Top-level container for client port transceiver data
nodetype: container (rw)
description:
Configuration data for client port transceivers
nodetype: container (rw)
description:
Turns power on / off to the transceiver -- provides a means
to power on/off the transceiver (in the case of SFP, SFP+,
QSFP,...) or enable high-power mode (in the case of CFP,
CFP2, CFP4) and is optionally supported (device can choose to
always enable). True = power on / high power, False =
powered off
nodetype: leaf (rw)
type: boolean
description:
Indicates the type of optical transceiver used on this
port. If the client port is built into the device and not
pluggable, then non-pluggable is the corresponding state. If
a device port supports multiple form factors (e.g. QSFP28
and QSFP+, then the value of the transceiver installed shall
be reported. If no transceiver is present, then the value of
the highest rate form factor shall be reported
(QSFP28, for example).
The form factor is included in configuration data to allow
pre-configuring a device with the expected type of
transceiver ahead of deployment. The corresponding state
leaf should reflect the actual transceiver type plugged into
the system.
nodetype: leaf (rw)
type: identityref
description:
The Ethernet PMD is a property of the optical transceiver
used on the port, indicating the type of physical connection.
It is included in configuration data to allow pre-configuring
a port/transceiver with the expected PMD. The actual PMD is
indicated by the ethernet-pmd state leaf.
nodetype: leaf (rw)
type: identityref
description:
Operational state data for client port transceivers
nodetype: container (ro)
description:
Turns power on / off to the transceiver -- provides a means
to power on/off the transceiver (in the case of SFP, SFP+,
QSFP,...) or enable high-power mode (in the case of CFP,
CFP2, CFP4) and is optionally supported (device can choose to
always enable). True = power on / high power, False =
powered off
nodetype: leaf (ro)
type: boolean
description:
Indicates the type of optical transceiver used on this
port. If the client port is built into the device and not
pluggable, then non-pluggable is the corresponding state. If
a device port supports multiple form factors (e.g. QSFP28
and QSFP+, then the value of the transceiver installed shall
be reported. If no transceiver is present, then the value of
the highest rate form factor shall be reported
(QSFP28, for example).
The form factor is included in configuration data to allow
pre-configuring a device with the expected type of
transceiver ahead of deployment. The corresponding state
leaf should reflect the actual transceiver type plugged into
the system.
nodetype: leaf (ro)
type: identityref
description:
The Ethernet PMD is a property of the optical transceiver
used on the port, indicating the type of physical connection.
It is included in configuration data to allow pre-configuring
a port/transceiver with the expected PMD. The actual PMD is
indicated by the ethernet-pmd state leaf.
nodetype: leaf (ro)
type: identityref
description:
Indicates whether a transceiver is present in
the specified client port.
nodetype: leaf (ro)
type: enumeration
description:
Indicates the type of optical transceiver used on this
port. If the client port is built into the device and not
pluggable, then non-pluggable is the corresponding state. If
a device port supports multiple form factors (e.g. QSFP28
and QSFP+, then the value of the transceiver installed shall
be reported. If no transceiver is present, then the value of
the highest rate form factor shall be reported
(QSFP28, for example).
nodetype: leaf (ro)
type: identityref
description:
Connector type used on this port
nodetype: leaf (ro)
type: identityref
description:
Internally measured temperature in degrees Celsius. MSA
valid range is between -40 and +125C. Accuracy shall be
better than +/- 3 degC over the whole temperature range.
nodetype: leaf (ro)
type: int16
description:
Full name of transceiver vendor. 16-octet field that
contains ASCII characters, left-aligned and padded on the
right with ASCII spaces (20h)
nodetype: leaf (ro)
type: string
description:
Transceiver vendor's part number. 16-octet field that
contains ASCII characters, left-aligned and padded on the
right with ASCII spaces (20h). If part number is undefined,
all 16 octets = 0h
nodetype: leaf (ro)
type: string
description:
Transceiver vendor's revision number. 2-octet field that
contains ASCII characters, left-aligned and padded on the
right with ASCII spaces (20h)
nodetype: leaf (ro)
type: string
description:
Ethernet PMD (physical medium dependent sublayer) that the
transceiver supports. The SFF/QSFP MSAs have registers for
this and CFP MSA has similar.
nodetype: leaf (ro)
type: identityref
description:
SONET/SDH application code supported by the port
nodetype: leaf (ro)
type: identityref
description:
OTN application code supported by the port
nodetype: leaf (ro)
type: identityref
description:
Transceiver serial number. 16-octet field that contains
ASCII characters, left-aligned and padded on the right with
ASCII spaces (20h). If part serial number is undefined, all
16 octets = 0h
nodetype: leaf (ro)
type: string
description:
Representation of the transceiver date code, typically
stored as YYMMDD. The time portion of the value is
undefined and not intended to be read.
nodetype: leaf (ro)
type: oc-yang:date-and-time
description:
Indicates if a fault condition exists in the transceiver
nodetype: leaf (ro)
type: boolean
description:
The output optical power of a physical channel in units
of 0.01dBm, which may be associated with individual
physical channels, or an aggregate of multiple physical
channels (i.e., for the overall transceiver). For an
aggregate, this may be a measurement from a photodetector
or a a calculation performed on the device by summing up
all of the related individual physical channels.
Values include the instantaneous, average, minimum, and
maximum statistics. If avg/min/max statistics are not
supported, the target is expected to just supply the
instant value
nodetype: container (ro)
description:
The instantaneous value of the statistic.
nodetype: leaf (ro)
type: decimal64
units: dBm
description:
The arithmetic mean value of the statistic over the
sampling period.
nodetype: leaf (ro)
type: decimal64
units: dBm
description:
The minimum value of the statistic over the sampling
period
nodetype: leaf (ro)
type: decimal64
units: dBm
description:
The maximum value of the statistic over the sampling
period
nodetype: leaf (ro)
type: decimal64
units: dBm
description:
The input optical power of a physical channel in units
of 0.01dBm, which may be associated with individual
physical channels, or an aggregate of multiple physical
channels (i.e., for the overall transceiver). For an
aggregate, this may be a measurement from a photodetector
or a a calculation performed on the device by summing up
all of the related individual physical channels.
Values include the instantaneous, average, minimum, and
maximum statistics. If avg/min/max statistics are not
supported, the target is expected to just supply the
instant value
nodetype: container (ro)
description:
The instantaneous value of the statistic.
nodetype: leaf (ro)
type: decimal64
units: dBm
description:
The arithmetic mean value of the statistic over the
sampling period.
nodetype: leaf (ro)
type: decimal64
units: dBm
description:
The minimum value of the statistic over the sampling
period
nodetype: leaf (ro)
type: decimal64
units: dBm
description:
The maximum value of the statistic over the sampling
period
nodetype: leaf (ro)
type: decimal64
units: dBm
description:
The current applied by the system to the transmit laser to
achieve the output power. The current is expressed in mA
with up to two decimal precision. Values include the
instantaneous, average, minimum, and maximum statistics.
If avg/min/max statistics are not supported, the target is
expected to just supply the instant value
nodetype: container (ro)
description:
The instantaneous value of the statistic.
nodetype: leaf (ro)
type: decimal64
units: mA
description:
The arithmetic mean value of the statistic over the
sampling period.
nodetype: leaf (ro)
type: decimal64
units: mA
description:
The minimum value of the statistic over the sampling
period
nodetype: leaf (ro)
type: decimal64
units: mA
description:
The maximum value of the statistic over the sampling
period
nodetype: leaf (ro)
type: decimal64
units: mA
description:
Enclosing container for client channels
nodetype: container (rw)
description:
List of client channels, keyed by index within a physical
client port. A physical port with a single channel would
have a single zero-indexed element
nodetype: list (rw)
list keys: [index]
description:
Reference to the index number of the channel
nodetype: leaf (list key) (rw)
type: leafref
description:
Configuration data for physical channels
nodetype: container (rw)
description:
Index of the physical channnel or lane within a physical
client port
nodetype: leaf (rw)
type: uint16
description:
Text description for the client physical channel
nodetype: leaf (rw)
type: string
description:
Enable (true) or disable (false) the transmit label for the
channel
nodetype: leaf (rw)
type: boolean
description:
Target output optical power level of the optical channel,
expressed in increments of 0.01 dBm (decibel-milliwats)
nodetype: leaf (rw)
type: decimal64
units: dBm
description:
Operational state data for channels
nodetype: container (ro)
description:
Index of the physical channnel or lane within a physical
client port
nodetype: leaf (ro)
type: uint16
description:
Text description for the client physical channel
nodetype: leaf (ro)
type: string
description:
Enable (true) or disable (false) the transmit label for the
channel
nodetype: leaf (ro)
type: boolean
description:
Target output optical power level of the optical channel,
expressed in increments of 0.01 dBm (decibel-milliwats)
nodetype: leaf (ro)
type: decimal64
units: dBm
description:
The frequency in MHz of the individual physical channel
(e.g. ITU C50 - 195.0THz and would be reported as
195,000,000 MHz in this model). This attribute is not
configurable on most client ports.
nodetype: leaf (ro)
type: oc-opt-types:frequency-type
description:
The output optical power of a physical channel in units
of 0.01dBm, which may be associated with individual
physical channels, or an aggregate of multiple physical
channels (i.e., for the overall transceiver). For an
aggregate, this may be a measurement from a photodetector
or a a calculation performed on the device by summing up
all of the related individual physical channels.
Values include the instantaneous, average, minimum, and
maximum statistics. If avg/min/max statistics are not
supported, the target is expected to just supply the
instant value
nodetype: container (ro)
description:
The instantaneous value of the statistic.
nodetype: leaf (ro)
type: decimal64
units: dBm
description:
The arithmetic mean value of the statistic over the
sampling period.
nodetype: leaf (ro)
type: decimal64
units: dBm
description:
The minimum value of the statistic over the sampling
period
nodetype: leaf (ro)
type: decimal64
units: dBm
description:
The maximum value of the statistic over the sampling
period
nodetype: leaf (ro)
type: decimal64
units: dBm
description:
The input optical power of a physical channel in units
of 0.01dBm, which may be associated with individual
physical channels, or an aggregate of multiple physical
channels (i.e., for the overall transceiver). For an
aggregate, this may be a measurement from a photodetector
or a a calculation performed on the device by summing up
all of the related individual physical channels.
Values include the instantaneous, average, minimum, and
maximum statistics. If avg/min/max statistics are not
supported, the target is expected to just supply the
instant value
nodetype: container (ro)
description:
The instantaneous value of the statistic.
nodetype: leaf (ro)
type: decimal64
units: dBm
description:
The arithmetic mean value of the statistic over the
sampling period.
nodetype: leaf (ro)
type: decimal64
units: dBm
description:
The minimum value of the statistic over the sampling
period
nodetype: leaf (ro)
type: decimal64
units: dBm
description:
The maximum value of the statistic over the sampling
period
nodetype: leaf (ro)
type: decimal64
units: dBm
description:
The current applied by the system to the transmit laser to
achieve the output power. The current is expressed in mA
with up to two decimal precision. Values include the
instantaneous, average, minimum, and maximum statistics.
If avg/min/max statistics are not supported, the target is
expected to just supply the instant value
nodetype: container (ro)
description:
The instantaneous value of the statistic.
nodetype: leaf (ro)
type: decimal64
units: mA
description:
The arithmetic mean value of the statistic over the
sampling period.
nodetype: leaf (ro)
type: decimal64
units: mA
description:
The minimum value of the statistic over the sampling
period
nodetype: leaf (ro)
type: decimal64
units: mA
description:
The maximum value of the statistic over the sampling
period
nodetype: leaf (ro)
type: decimal64
units: mA
description:
Top-level container for linecard data
nodetype: container (rw)
description:
Configuration data for linecards
nodetype: container (rw)
description:
Enable or disable power to the linecard
nodetype: leaf (rw)
type: oc-platform-types:component-power-type
description:
Operational state data for linecards
nodetype: container (ro)
description:
Enable or disable power to the linecard
nodetype: leaf (ro)
type: oc-platform-types:component-power-type
description:
Identifier for the slot or chassis position in which the
linecard is installed
nodetype: leaf (ro)
type: string
description:
Top-level container for port breakout data
nodetype: container (rw)
description:
Configuration data for port breakout
nodetype: container (rw)
description:
Sets the number of channels to 'breakout' on a port
capable of channelization
nodetype: leaf (rw)
type: uint8
description:
Sets the channel speed on each channel -- the
supported values are defined by the
ETHERNET_SPEED identity
nodetype: leaf (rw)
type: identityref
description:
Operational state data for port breakout
nodetype: container (ro)
description:
Sets the number of channels to 'breakout' on a port
capable of channelization
nodetype: leaf (ro)
type: uint8
description:
Sets the channel speed on each channel -- the
supported values are defined by the
ETHERNET_SPEED identity
nodetype: leaf (ro)
type: identityref
This module defines data related to LINECARD components in the frinx-openconfig-platform model
frinx-openconfig-platform
frinx-openconfig-platform-types
frinx-openconfig-extensions
network-topology
frinx-uniconfig-topology
This module defines data related to PORT components in the frinx-openconfig-platform model
frinx-openconfig-platform
frinx-openconfig-if-ethernet
frinx-openconfig-extensions
network-topology
frinx-uniconfig-topology
This module defines configuration and operational state data for transceivers (i.e., pluggable optics). The module should be used in conjunction with the platform model where other physical entity data are represented.
In the platform model, a component of type=TRANSCEIVER is expected to be a subcomponent of a PORT component. This module defines a concrete schema for the associated data for components with type=TRANSCEIVER.
frinx-openconfig-platform
frinx-openconfig-interfaces
frinx-openconfig-transport-types
frinx-openconfig-types
frinx-openconfig-extensions
frinx-openconfig-yang-types
network-topology
frinx-uniconfig-topology
This module defines data types (e.g., YANG identities) to support the OpenConfig component inventory model.
frinx-openconfig-extensions
description:
A generic type reflecting whether a hardware component
is powered on or off
type: enumeration
description:
Base identity for hardware related components in a managed
device. Derived identities are partially based on contents
of the IANA Entity MIB.
description:
Linecard component, typically inserted into a chassis slot
base identity: OPENCONFIG_HARDWARE_COMPONENT
description:
Replaceable hardware module, e.g., a daughtercard
base identity: OPENCONFIG_HARDWARE_COMPONENT
description:
Processing unit, e.g., a management processor
base identity: OPENCONFIG_HARDWARE_COMPONENT
description:
Pluggable module present in a port
base identity: OPENCONFIG_HARDWARE_COMPONENT
description:
Chassis component, typically with multiple slots / shelves
base identity: OPENCONFIG_HARDWARE_COMPONENT
description:
Cooling fan, or could be some other heat-reduction component
base identity: OPENCONFIG_HARDWARE_COMPONENT
description:
Backplane component for aggregating traffic, typically
contained in a chassis component
base identity: OPENCONFIG_HARDWARE_COMPONENT
description:
Physical sensor, e.g., a temperature sensor in a chassis
base identity: OPENCONFIG_HARDWARE_COMPONENT
description:
Physical port, e.g., for attaching pluggables and networking
cables
base identity: OPENCONFIG_HARDWARE_COMPONENT
description:
Component that is supplying power to the device
base identity: OPENCONFIG_HARDWARE_COMPONENT
description:
Base identity for software-related components in a managed
device
description:
Operating system running on a component
base identity: OPENCONFIG_SOFTWARE_COMPONENT
This module contains general data definitions for use in routing policy. It can be imported by modules that contain protocol- specific policy conditions and actions.
ietf-yang-types
frinx-openconfig-extensions
description:
Options that govern the behavior of a match statement. The
default behavior is ANY, i.e., the given value matches any
of the members of the defined set. Note this type is a
restricted version of the match-set-options-type.
type: enumeration
description:
Options that govern the behavior of a match statement. The
default behavior is ANY, i.e., the given value matches any
of the members of the defined set
type: enumeration
description:
type for expressing route tags on a local system,
including IS-IS and OSPF; may be expressed as either decimal or
hexidecimal integer
type: union
type: uint32
type: yang:hex-string
description:
base type for supported comparison operators on route
attributes
description:
<= comparison
base identity: ATTRIBUTE_COMPARISON
description:
== comparison
base identity: ATTRIBUTE_COMPARISON
description:
>= comparison
base identity: ATTRIBUTE_COMPARISON
description:
Base type for protocols which can install prefixes into the
RIB
description:
IS-IS
base identity: INSTALL_PROTOCOL_TYPE
description:
BGP
base identity: INSTALL_PROTOCOL_TYPE
description:
Locally defined aggregate route
base identity: INSTALL_PROTOCOL_TYPE
description:
Locally-installed static route
base identity: INSTALL_PROTOCOL_TYPE
description:
A directly connected route
base identity: INSTALL_PROTOCOL_TYPE
description:
OSPFv2
base identity: INSTALL_PROTOCOL_TYPE
description:
OSPFv3
base identity: INSTALL_PROTOCOL_TYPE
This module defines configuration and operational state data for the probes. A probe consists on a group of tests, each test being a source-destination pair to poll. The destination can be either IP Address (and eventually port) or URL, depending on the nature of the test. The test can send ICMP, UDP, TCP, or HTTP requests. Each test groups a list of test items, the test results being an overall view or average of the items list. However, the test preserves only a limited set of history items, whose length can be controlled using the history-size.
ietf-yang-types
frinx-openconfig-types
frinx-openconfig-extensions
frinx-openconfig-inet-types
frinx-openconfig-probes-types
network-topology
frinx-uniconfig-topology
description:
The container containing the list of probes.
nodetype: container (rw)
description:
List of probes configured.
frinx-device-type:
junos
frinx-supported-versions:
182
frinx-implemented-reader:
io.frinx.unitopo.unit.junos18.probes.handler.ProbeReader
nodetype: list (rw)
list keys: [name]
description:
Reference to the list key
nodetype: leaf (list key) (rw)
type: leafref
description:
Configuration data for the probes.
frinx-device-type:
junos
frinx-supported-versions:
182
frinx-implemented-reader:
io.frinx.unitopo.unit.junos18.probes.handler.ProbeConfigReader
frinx-implemented-writer:
io.frinx.unitopo.unit.junos18.probes.handler.ProbeConfigWriter
nodetype: container (rw)
description:
The name of the probe.
nodetype: leaf (rw)
type: string
description:
Whether the probe is enabled.
nodetype: leaf (rw)
type: boolean
default: true
description:
Define the probe is delegate-probes or not
nodetype: leaf (rw)
type: boolean
description:
Operational state data
nodetype: container (ro)
description:
The name of the probe.
nodetype: leaf (ro)
type: string
description:
Whether the probe is enabled.
nodetype: leaf (ro)
type: boolean
default: true
description:
The tests associated to be executed for the probe.
frinx-device-type:
junos
frinx-supported-versions:
182
nodetype: container (rw)
description:
List of tests associated with this probe.
frinx-device-type:
junos
frinx-supported-versions:
182
frinx-implemented-reader:
io.frinx.unitopo.unit.junos18.probes.handler.test.ProbeTestReader
nodetype: list (rw)
list keys: [name]
description:
Reference to the list key
nodetype: leaf (list key) (rw)
type: leafref
description:
Configuration data for the test of this probe.
frinx-device-type:
junos
frinx-supported-versions:
182
frinx-implemented-reader:
io.frinx.unitopo.unit.junos18.probes.handler.test.ProbeTestConfigReader
frinx-implemented-writer:
io.frinx.unitopo.unit.junos18.probes.handler.test.ProbeTestConfigWriter
nodetype: container (rw)
description:
The name of the test probe
nodetype: leaf (rw)
type: string
description:
Whether the test is enabled.
nodetype: leaf (rw)
type: boolean
default: true
description:
The type of the probe test.
nodetype: leaf (rw)
type: oc-probes-types:test-type
description:
The number of probes per test.
nodetype: leaf (rw)
type: yang:counter64
description:
Time between two consecutive probes.
nodetype: leaf (rw)
type: yang:counter64
description:
Source address used when probing, either IPv4 or IPv6.
nodetype: leaf (rw)
type: oc-inet:ip-address
description:
The number of history entries stored.
nodetype: leaf (rw)
type: yang:counter64
description:
Source number used.
nodetype: leaf (rw)
type: oc-inet:port-number
description:
DSCP code points
nodetype: leaf (rw)
type: oc-inet:dscp
description:
Define the interface that adds a timestamp to RPM probe messages.
nodetype: leaf (rw)
type: string
description:
Operational state data
nodetype: container (ro)
description:
The name of the test probe
nodetype: leaf (ro)
type: string
description:
Whether the test is enabled.
nodetype: leaf (ro)
type: boolean
default: true
description:
The type of the probe test.
nodetype: leaf (ro)
type: oc-probes-types:test-type
description:
The number of probes per test.
nodetype: leaf (ro)
type: yang:counter64
description:
Time between two consecutive probes.
nodetype: leaf (ro)
type: yang:counter64
description:
Source address used when probing, either IPv4 or IPv6.
nodetype: leaf (ro)
type: oc-inet:ip-address
description:
The number of history entries stored.
nodetype: leaf (ro)
type: yang:counter64
description:
Source number used.
nodetype: leaf (ro)
type: oc-inet:port-number
description:
DSCP code points
nodetype: leaf (ro)
type: oc-inet:dscp
description:
The target configuration of the test.
The nature of the target depends on the probe type:
for HTTP probes we need to provide an URL to poll,
while ICMP probes require an IP address to monitor.
frinx-device-type:
junos
frinx-supported-versions:
182
nodetype: container (rw)
description:
Configuration data for the test target.
frinx-device-type:
junos
frinx-supported-versions:
182
frinx-implemented-reader:
io.frinx.unitopo.unit.junos18.probes.handler.test.ProbeTargetConfigReader
frinx-implemented-writer:
io.frinx.unitopo.unit.junos18.probes.handler.test.ProbeTargetConfigWriter
nodetype: container (rw)
description:
IP address of the target, either IPv4 or IPv6.
nodetype: leaf (rw)
type: oc-inet:ip-address
description:
Destination port.
nodetype: leaf (rw)
type: oc-inet:port-number
description:
Target URL to probe.
nodetype: leaf (rw)
type: oc-inet:url
description:
Operational data for the test target.
nodetype: container (ro)
description:
IP address of the target, either IPv4 or IPv6.
nodetype: leaf (ro)
type: oc-inet:ip-address
description:
Destination port.
nodetype: leaf (ro)
type: oc-inet:port-number
description:
Target URL to probe.
nodetype: leaf (ro)
type: oc-inet:url
description:
Contains the results of the tests.
nodetype: container (rw)
description:
Results of this test: operational data only
nodetype: container (ro)
description:
The test timestamp.
This is not the timestamp when the test
was actually executed nither when it finished.
Should be the timestamp when the test has been scheduled.
It may not be the same with start-timestamp.
nodetype: leaf (ro)
type: oc-types:timeticks64
description:
The timestamp when the test started.
nodetype: leaf (ro)
type: oc-types:timeticks64
description:
The timestamp when the test finished.
nodetype: leaf (ro)
type: oc-types:timeticks64
description:
The duration of the test, in microseconds.
nodetype: leaf (ro)
type: yang:counter64
description:
Whether the test failed or succeeded.
nodetype: leaf (ro)
type: boolean
description:
Number of test probes sent.
nodetype: leaf (ro)
type: yang:counter64
description:
Number of test probes received.
nodetype: leaf (ro)
type: yang:counter64
description:
The loss percentage.
nodetype: leaf (ro)
type: oc-types:percentage
description:
The round trip jitter, in microseconds.
nodetype: leaf (ro)
type: yang:counter64
description:
The minimum delay recorded during the test, in microseconds.
nodetype: leaf (ro)
type: yang:counter64
description:
The maximum delay recorded during the test, in microseconds.
nodetype: leaf (ro)
type: yang:counter64
description:
The average delay recorded during the test, in microseconds.
nodetype: leaf (ro)
type: yang:counter64
description:
The standard deviation of the delay of the test.
nodetype: leaf (ro)
type: yang:counter64
description:
Historical data of the tests.
nodetype: container (ro)
description:
The list of items in the probe history.
The length depends on the history size.
nodetype: container (ro)
description:
List of history items.
nodetype: list (ro)
list keys: [id]
description:
Reference to the history entry ID.
nodetype: leaf (list key) (ro)
type: leafref
description:
A history item of the probe results: operational data only.
nodetype: container (ro)
description:
The test item ID.
nodetype: leaf (ro)
type: yang:counter64
description:
The test timestamp.
This is not the timestamp when the test
was actually executed nither when it finished.
Should be the timestamp when the test has been scheduled.
It may not be the same with start-timestamp.
nodetype: leaf (ro)
type: oc-types:timeticks64
description:
The timestamp when the test started.
nodetype: leaf (ro)
type: oc-types:timeticks64
description:
The timestamp when the test finished.
nodetype: leaf (ro)
type: oc-types:timeticks64
description:
The duration of the test, in microseconds.
nodetype: leaf (ro)
type: yang:counter64
description:
Whether the test failed or succeeded.
nodetype: leaf (ro)
type: boolean
description:
Number of test probes sent.
nodetype: leaf (ro)
type: yang:counter64
description:
Number of test probes received.
nodetype: leaf (ro)
type: yang:counter64
description:
The loss percentage.
nodetype: leaf (ro)
type: oc-types:percentage
description:
The round trip jitter, in microseconds.
nodetype: leaf (ro)
type: yang:counter64
description:
The minimum delay recorded during the test, in microseconds.
nodetype: leaf (ro)
type: yang:counter64
description:
The maximum delay recorded during the test, in microseconds.
nodetype: leaf (ro)
type: yang:counter64
description:
The average delay recorded during the test, in microseconds.
nodetype: leaf (ro)
type: yang:counter64
description:
The standard deviation of the delay of the test.
nodetype: leaf (ro)
type: yang:counter64
This module defines types related to the probes.
frinx-openconfig-extensions
description:
Type definition with enumerations describing the basis of
the probe test type identifier
type: enumeration
This submodule defines data related to quality-of-service configuration and operational state associated with interfaces.
frinx-openconfig-extensions
frinx-openconfig-interfaces
frinx-openconfig-yang-types
This module defines types and identities used in OpenConfig models related to quality-of-service (QoS)
frinx-openconfig-extensions
description:
Type definition for different queueing behaviours that
are available to a scheduler.
type: enumeration
description:
Base identity to describe supported QoS scheduler types.
description:
Token bucket scheduler with two buckets, one filled at the
committed information rate (CIR) in bps, and the second filled
at the peak information rate (PIR) in bps when the first
bucket is full. The first bucket depth is
the committed burst size (bytes), and the second is the
excess burst size (bytes). Traffic is categorized in three
colors as follows: traffic that falls within the
the CIR is conforming, traffic that is greater than the CIR
but less than the PIR is exceeding, and traffic that is
greater than PIR is violating.
base identity: QOS_SCHEDULER_TYPE
description:
Token bucket scheduler with a single rate (committed information
rate) and two colors (conforming and exceeding). The scheduler
behavior is governed by two parameters, the CIR which
determines the rate of token fill (bps) and the committed
burst size (depth of the token bucket in bytes).
base identity: QOS_SCHEDULER_TYPE
description:
Base identity for supported queue types, primarily
defined by their drop behavior / strategy
description:
Queue management based on a variant of RED in which the packet
drop probability is based on its traffic class.
base identity: QOS_QUEUE_TYPE
description:
When the queue is filled to capacity, newly arriving packets
are discarded until there is room in the queue to accept new
traffic. Packets are not differentiated, i.e., all packets
are treated identically.
base identity: QOS_QUEUE_TYPE
description:
Queue management based on Random Early Detection (RED). RED
drops packets based on a drop probability that is based on the
average queue length, and settings of mininum and maximum
queue thresholds. On ECN-capable devices, packets may be
marked instead of dropped to signal congestion to the
sender.
base identity: QOS_QUEUE_TYPE
This submodule contains structural data definitions for BGP routing tables.
ietf-inet-types
frinx-openconfig-extensions
frinx-openconfig-policy-types
Defines additional data nodes for the OpenConfig BGP RIB model. These items reflect extensions that are desirable features but are not currently supported in a majority of BGP implementations.
frinx-openconfig-rib-bgp
frinx-openconfig-extensions
frinx-openconfig-rib-bgp-types
network-topology
frinx-uniconfig-topology
Defines identity and type defintions associated with the OpenConfig BGP RIB modules
frinx-openconfig-extensions
description:
Base identity for indicating reason a route was was not
selected by BGP route selection algorithm
description:
Route was sent by a peer with a higher BGP Identifier value,
or router id
base identity: BGP_NOT_SELECTED_BESTPATH
description:
Route has a higher origin type, i.e., IGP origin is preferred
over EGP or incomplete
base identity: BGP_NOT_SELECTED_BESTPATH
description:
Route has a higher MED, or metric, attribute than the current
best path
base identity: BGP_NOT_SELECTED_BESTPATH
description:
Route has a longer AS path attribute than current best path
base identity: BGP_NOT_SELECTED_BESTPATH
description:
Route has a lower localpref attribute than current best path
base identity: BGP_NOT_SELECTED_BESTPATH
description:
Route was sent by a peer with a higher IP address
base identity: BGP_NOT_SELECTED_BESTPATH
description:
Route has a higher interior cost to the next hop.
base identity: BGP_NOT_SELECTED_BESTPATH
description:
Route source is via IGP, rather than EGP.
base identity: BGP_NOT_SELECTED_BESTPATH
description:
Base identity for reason code for routes that are rejected
due to policy
description:
Route was rejected after apply import policies
base identity: BGP_NOT_SELECTED_POLICY
description:
Base identity for reason code for routes that are rejected as
invalid. Some derived entities are based on BMP v3
description:
Route was invalid due to AS_PATH loop
base identity: INVALID_ROUTE_REASON
description:
Route was invalid due to a loop in the AS_CONFED_SEQUENCE or
AS_CONFED_SET attributes
base identity: INVALID_ROUTE_REASON
description:
Route was invalid due to ORIGINATOR_ID, e.g., update has
local router as originator
base identity: INVALID_ROUTE_REASON
description:
Route was invalid due to CLUSTER_LIST loop
base identity: INVALID_ROUTE_REASON
This module describes a YANG model for routing policy configuration. It is a limited subset of all of the policy configuration parameters available in the variety of vendor implementations, but supports widely used constructs for managing how routes are imported, exported, and modified across different routing protocols. This module is intended to be used in conjunction with routing protocol configuration models (e.g., BGP) defined in other modules.
Route policy expression:
Policies are expressed as a set of top-level policy definitions, each of which consists of a sequence of policy statements. Policy statements consist of simple condition-action tuples. Conditions may include mutiple match or comparison operations, and similarly actions may be multitude of changes to route attributes or a final disposition of accepting or rejecting the route.
Route policy evaluation:
Policy definitions are referenced in routing protocol configurations using import and export configuration statements. The arguments are members of an ordered list of named policy definitions which comprise a policy chain, and optionally, an explicit default policy action (i.e., reject or accept).
Evaluation of each policy definition proceeds by evaluating its corresponding individual policy statements in order. When a condition statement in a policy statement is satisfied, the corresponding action statement is executed. If the action statement has either accept-route or reject-route actions, policy evaluation of the current policy definition stops, and no further policy definitions in the chain are evaluated.
If the condition is not satisfied, then evaluation proceeds to the next policy statement. If none of the policy statement conditions are satisfied, then evaluation of the current policy definition stops, and the next policy definition in the chain is evaluated. When the end of the policy chain is reached, the default route disposition action is performed (i.e., reject-route unless an an alternate default action is specified for the chain).
Policy 'subroutines' (or nested policies) are supported by allowing policy statement conditions to reference another policy definition which applies conditions and actions from the referenced policy before returning to the calling policy statement and resuming evaluation. If the called policy results in an accept-route (either explicit or by default), then the subroutine returns an effective true value to the calling policy. Similarly, a reject-route action returns false. If the subroutine returns true, the calling policy continues to evaluate the remaining conditions (using a modified route if the subroutine performed any changes to the route).
frinx-openconfig-inet-types
frinx-openconfig-interfaces
frinx-openconfig-policy-types
frinx-openconfig-extensions
network-topology
frinx-uniconfig-topology
description:
Type used to specify route disposition in
a policy chain
type: enumeration
description:
Type used to specify route disposition in
a policy chain
type: enumeration
description:
Top-level container for all routing policy configuration
frinx-device-type:
vrp
frinx-supported-versions:
any
frinx-device-type:
xr
frinx-supported-versions:
6
nodetype: container (rw)
description:
Predefined sets of attributes used in policy match
statements
frinx-device-type:
vrp
frinx-supported-versions:
any
frinx-device-type:
xr
frinx-supported-versions:
6
nodetype: container (rw)
description:
Enclosing container
nodetype: container (rw)
description:
List of the defined prefix sets
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.routing.policy.handler.prefix.PrefixSetReader
frinx-implemented-reader-details:
ID_PATTERN:
prefix-set (?<id>\S+)
SH_ALL_PREFIX_SETS:
show running-config | include ^prefix-set
frinx-implemented-writer:
MISSING WRITER
nodetype: list (rw)
list keys: [name]
description:
Reference to prefix name list key
nodetype: leaf (list key) (rw)
type: leafref
description:
Configuration data for prefix sets
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.routing.policy.handler.prefix.PrefixSetConfigReader
frinx-implemented-writer:
io.frinx.cli.unit.iosxr.routing.policy.handler.prefix.PrefixSetConfigWriter
frinx-implemented-writer-details:
TEMPLATE:
prefix-set {$config.name}
end-set
nodetype: container (rw)
description:
name / label of the prefix set -- this is used to
reference the set in match conditions
nodetype: leaf (rw)
type: string
description:
Indicates the mode of the prefix set, in terms of which
address families (IPv4, IPv6, or both) are present. The
mode provides a hint, but the device must validate that all
prefixes are of the indicated type, and is expected to
reject the configuration if there is a discrepancy. The
MIXED mode may not be supported on devices that require
prefix sets to be of only one address family.
nodetype: leaf (rw)
type: enumeration
description:
Operational state data
nodetype: container (ro)
description:
name / label of the prefix set -- this is used to
reference the set in match conditions
nodetype: leaf (ro)
type: string
description:
Indicates the mode of the prefix set, in terms of which
address families (IPv4, IPv6, or both) are present. The
mode provides a hint, but the device must validate that all
prefixes are of the indicated type, and is expected to
reject the configuration if there is a discrepancy. The
MIXED mode may not be supported on devices that require
prefix sets to be of only one address family.
nodetype: leaf (ro)
type: enumeration
description:
Enclosing container for the list of prefixes in a policy
prefix list
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
MISSING READER
frinx-implemented-writer:
io.frinx.cli.unit.iosxr.routing.policy.handler.prefix.PrefixesWriter
frinx-implemented-writer-details:
TEMPLATE:
prefix-set {$name}
{% loop in $prefixes as $p %}
{$p.prefix}{% if ($p.ge) %} ge {$p.ge}{% endif %}{% if ($p.le) %} le {$p.le}{% endif %}{% divider %},
{% onEmpty %}{% endloop %}
end-set
nodetype: container (rw)
description:
List of prefixes in the prefix set
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.routing.policy.handler.prefix.PrefixReader
frinx-implemented-reader-details:
EQ_PATTERN:
.*eq (?<value>[0-9]+)\s*.*
EXACT_MASK_LENGTH:
exact
GE_PATTERN:
.*ge (?<value>[0-9]+)\s*.*
LE_PATTERN:
.*le (?<value>[0-9]+)\s*.*
MASK_LENGTH_RANGE_PATTERN:
%s..%s
PREFIX_PATTERN:
\s+(?<network>[0-9a-f.:]+)/?(?<mask>[0-9]*)?\s*(?<modifiers>.*)\s*
SH_PREFIX_SET:
show running-config prefix-set %s
frinx-implemented-writer:
io.frinx.cli.unit.iosxr.routing.policy.handler.prefix.PrefixesWriter
frinx-implemented-writer-details:
TEMPLATE:
prefix-set {$name}
{% loop in $prefixes as $p %}
{$p.prefix}{% if ($p.ge) %} ge {$p.ge}{% endif %}{% if ($p.le) %} le {$p.le}{% endif %}{% divider %},
{% onEmpty %}{% endloop %}
end-set
nodetype: list (rw)
list keys: [ip-prefix] [masklength-range]
description:
Reference to the ip-prefix list key.
nodetype: leaf (list key) (rw)
type: leafref
description:
Reference to the masklength-range list key
nodetype: leaf (list key) (rw)
type: leafref
description:
Configuration data for prefix definition
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.routing.policy.handler.prefix.PrefixConfigReader
frinx-implemented-writer:
io.frinx.cli.unit.iosxr.routing.policy.handler.prefix.PrefixesWriter
frinx-implemented-writer-details:
TEMPLATE:
prefix-set {$name}
{% loop in $prefixes as $p %}
{$p.prefix}{% if ($p.ge) %} ge {$p.ge}{% endif %}{% if ($p.le) %} le {$p.le}{% endif %}{% divider %},
{% onEmpty %}{% endloop %}
end-set
nodetype: container (rw)
description:
The prefix member in CIDR notation -- while the
prefix may be either IPv4 or IPv6, most
implementations require all members of the prefix set
to be the same address family. Mixing address types in
the same prefix set is likely to cause an error.
nodetype: leaf (rw)
type: oc-inet:ip-prefix
description:
Defines a range for the masklength, or 'exact' if
the prefix has an exact length.
Example: 10.3.192.0/21 through 10.3.192.0/24 would be
expressed as prefix: 10.3.192.0/21,
masklength-range: 21..24.
Example: 10.3.192.0/21 would be expressed as
prefix: 10.3.192.0/21,
masklength-range: exact
nodetype: leaf (rw)
type: string
description:
Operational state data for prefix definition
nodetype: container (ro)
description:
The prefix member in CIDR notation -- while the
prefix may be either IPv4 or IPv6, most
implementations require all members of the prefix set
to be the same address family. Mixing address types in
the same prefix set is likely to cause an error.
nodetype: leaf (ro)
type: oc-inet:ip-prefix
description:
Defines a range for the masklength, or 'exact' if
the prefix has an exact length.
Example: 10.3.192.0/21 through 10.3.192.0/24 would be
expressed as prefix: 10.3.192.0/21,
masklength-range: 21..24.
Example: 10.3.192.0/21 would be expressed as
prefix: 10.3.192.0/21,
masklength-range: exact
nodetype: leaf (ro)
type: string
description:
Enclosing container for the list of neighbor set
definitions
nodetype: container (rw)
description:
List of defined neighbor sets for use in policies.
nodetype: list (rw)
list keys: [name]
description:
Reference to the neighbor set name list key.
nodetype: leaf (list key) (rw)
type: leafref
description:
Configuration data for neighbor sets.
nodetype: container (rw)
description:
name / label of the neighbor set -- this is used to
reference the set in match conditions
nodetype: leaf (rw)
type: string
description:
List of IP addresses in the neighbor set
nodetype: leaf-list (rw)
type: oc-inet:ip-address
description:
Operational state data for neighbor sets.
nodetype: container (ro)
description:
name / label of the neighbor set -- this is used to
reference the set in match conditions
nodetype: leaf (ro)
type: string
description:
List of IP addresses in the neighbor set
nodetype: leaf-list (ro)
type: oc-inet:ip-address
description:
Enclosing container for the list of tag sets.
nodetype: container (rw)
description:
List of tag set definitions.
nodetype: list (rw)
list keys: [name]
description:
Reference to the tag set name list key
nodetype: leaf (list key) (rw)
type: leafref
description:
Configuration data for tag sets
nodetype: container (rw)
description:
name / label of the tag set -- this is used to reference
the set in match conditions
nodetype: leaf (rw)
type: string
description:
Value of the tag set member
nodetype: leaf-list (rw)
type: oc-pol-types:tag-type
description:
Operational state data for tag sets
nodetype: container (ro)
description:
name / label of the tag set -- this is used to reference
the set in match conditions
nodetype: leaf (ro)
type: string
description:
Value of the tag set member
nodetype: leaf-list (ro)
type: oc-pol-types:tag-type
description:
BGP-related set definitions for policy match conditions
frinx-device-type:
vrp
frinx-supported-versions:
any
frinx-device-type:
xr
frinx-supported-versions:
6
nodetype: container (rw)
description:
Enclosing container for list of defined BGP community sets
nodetype: container (rw)
description:
List of defined BGP community sets
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.routing.policy.handler.community.CommunitySetReader
frinx-implemented-reader-details:
ID_PATTERN:
community-set (?<id>\S+)
SH_ALL_PREFIX_SETS:
show running-config | include ^community-set
frinx-implemented-writer:
MISSING WRITER
nodetype: list (rw)
list keys: [community-set-name]
description:
Reference to list key
nodetype: leaf (list key) (rw)
type: leafref
description:
Configuration data for BGP community sets
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.routing.policy.handler.community.CommunitySetConfigReader
frinx-implemented-reader-details:
AS_PATH_PATTERN:
\s+(?<communityRule>[^,]+),?
NO_ADVERTISE:
no-advertise
NO_EXPORT:
no-export
SH_AS_PATH_SET:
show running-config community-set %s
frinx-implemented-writer:
io.frinx.cli.unit.iosxr.routing.policy.handler.community.CommunitySetConfigWriter
frinx-implemented-writer-details:
TEMPLATE:
community-set {$config.community_set_name}
end-set
nodetype: container (rw)
description:
name / label of the community set -- this is used to
reference the set in match conditions
nodetype: leaf (rw)
type: string
description:
members of the community set
nodetype: leaf-list (rw)
type: union
type: identityref
type: oc-bgp-types:bgp-std-community-type
type: oc-bgp-types:bgp-community-regexp-type
description:
Operational state data for BGP community sets
nodetype: container (ro)
description:
name / label of the community set -- this is used to
reference the set in match conditions
nodetype: leaf (ro)
type: string
description:
members of the community set
nodetype: leaf-list (ro)
type: union
type: identityref
type: oc-bgp-types:bgp-std-community-type
type: oc-bgp-types:bgp-community-regexp-type
description:
Enclosing container for list of extended BGP community
sets
frinx-device-type:
vrp
frinx-supported-versions:
any
frinx-device-type:
xr
frinx-supported-versions:
6
nodetype: container (rw)
description:
List of defined extended BGP community sets
frinx-device-type:
vrp
frinx-supported-versions:
any
frinx-implemented-reader:
io.frinx.cli.unit.huawei.routing.policy.handler.ExtCommunitySetReader
frinx-implemented-reader-details:
DISPLAY_VRF_CONFIG:
display current-configuration configuration vpn-instance %s
ROUTE_TARGET_EXPORT_SET:
-route-target-export-set
ROUTE_TARGET_IMPORT_SET:
-route-target-import-set
RT:
rt
VRF_ID_ROUTE_TARGET:
(?<vrf>\S*)-route-target-(?<direction>import|export)-set
VRF_ID_ROUTE_TARGET_EXPORT:
vpn-target (?<rt>[\S].*) export-extcommunity
VRF_ID_ROUTE_TARGET_IMPORT:
vpn-target (?<rt>[\S].*) import-extcommunity
frinx-device-type:
xr
frinx-supported-versions:
6
frinx-implemented-reader:
io.frinx.unitopo.unit.xr6.routing.policy.handlers.ExtCommunitySetReader
frinx-implemented-reader-details:
ROUTE_TARGET_EXPORT_SET:
-route-target-export-set
ROUTE_TARGET_IMPORT_SET:
-route-target-import-set
frinx-device-type:
ios
frinx-supported-versions:
12any,15any
frinx-implemented-reader:
io.frinx.cli.unit.ios.routing.policy.handlers.ExtCommunitySetReader
frinx-implemented-reader-details:
ROUTE_TARGET_EXPORT_SET:
-route-target-export-set
ROUTE_TARGET_IMPORT_SET:
-route-target-import-set
SH_RUN_VRF_ID:
show running-config | include ^ip vrf|^ route-target
VRF_ID_ROUTE_TARGET:
(?<vrf>\S*)-route-target-(?<direction>import|export)-set
VRF_ID_ROUTE_TARGET_EXPORT:
route-target export (?<rt>[\S].*)
VRF_ID_ROUTE_TARGET_IMPORT:
route-target import (?<rt>[\S].*)
frinx-implemented-writer:
MISSING WRITER
nodetype: list (rw)
list keys: [ext-community-set-name]
description:
Reference to list key
nodetype: leaf (list key) (rw)
type: leafref
description:
Configuration data for extended BGP community sets
frinx-device-type:
vrp
frinx-supported-versions:
any
frinx-implemented-reader:
MISSING READER
frinx-implemented-writer:
io.frinx.cli.unit.huawei.routing.policy.handler.ExtCommunitySetConfigWriter
frinx-implemented-writer-details:
WRITE_TEMPLATE_2:
system-view
ip vpn-instance {$vrf}
ipv4-family
{% loop in $config.ext_community_member as $community %}
undo vpn-target {$community.bgp_ext_community_type.string} {$direction}
{% onEmpty %}{% endloop %}commit
return
frinx-device-type:
xr
frinx-supported-versions:
6
frinx-implemented-reader:
MISSING READER
frinx-implemented-writer:
io.frinx.unitopo.unit.xr6.routing.policy.handlers.ExtCommunitySetConfigWriter
frinx-device-type:
ios
frinx-supported-versions:
12any,15any
frinx-implemented-reader:
MISSING READER
frinx-implemented-writer:
io.frinx.cli.unit.ios.routing.policy.handlers.ExtCommunitySetConfigWriter
frinx-implemented-writer-details:
WRITE_TEMPLATE_2:
configure terminal
ip vrf {$vrf}
{% loop in $config.ext_community_member as $community %}
no route-target {$direction} {$community.bgp_ext_community_type.string}
{% onEmpty %}{% endloop %}end
nodetype: container (rw)
description:
name / label of the extended community set -- this is
used to reference the set in match conditions
nodetype: leaf (rw)
type: string
description:
members of the extended community set
nodetype: leaf-list (rw)
type: union
type: oc-bgp-types:bgp-ext-community-type
type: oc-bgp-types:bgp-community-regexp-type
description:
Operational state data for extended BGP community sets
nodetype: container (ro)
description:
name / label of the extended community set -- this is
used to reference the set in match conditions
nodetype: leaf (ro)
type: string
description:
members of the extended community set
nodetype: leaf-list (ro)
type: union
type: oc-bgp-types:bgp-ext-community-type
type: oc-bgp-types:bgp-community-regexp-type
description:
Enclosing container for list of define AS path sets
nodetype: container (rw)
description:
List of defined AS path sets
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.routing.policy.handler.aspath.AsPathSetReader
frinx-implemented-reader-details:
ID_PATTERN:
as-path-set (?<id>\S+)
SH_ALL_PREFIX_SETS:
show running-config | include ^as-path-set
frinx-implemented-writer:
MISSING WRITER
nodetype: list (rw)
list keys: [as-path-set-name]
description:
Reference to list key
nodetype: leaf (list key) (rw)
type: leafref
description:
Configuration data for AS path sets
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.routing.policy.handler.aspath.AsPathSetConfigReader
frinx-implemented-reader-details:
AS_PATH_PATTERN:
\s+(?<asPathRule>.+?),?\s*
SH_AS_PATH_SET:
show running-config as-path-set %s
frinx-implemented-writer:
io.frinx.cli.unit.iosxr.routing.policy.handler.aspath.AsPathSetConfigWriter
frinx-implemented-writer-details:
DELETE_TEMPLATE:
no as-path-set {$config.as_path_set_name}
TEMPLATE:
as-path-set {$config.as_path_set_name}
{% loop in $config.as_path_set_member as $m %}
{$m}{% divider %},
{% onEmpty %}{% endloop %}
end-set
nodetype: container (rw)
description:
name of the AS path set -- this is used to reference
the set in match conditions
nodetype: leaf (rw)
type: string
description:
AS path expression -- list of ASes in the set
nodetype: leaf-list (rw)
type: string
description:
Operational state data for AS path sets
nodetype: container (ro)
description:
name of the AS path set -- this is used to reference
the set in match conditions
nodetype: leaf (ro)
type: string
description:
AS path expression -- list of ASes in the set
nodetype: leaf-list (ro)
type: string
description:
Enclosing container for the list of top-level policy
definitions
nodetype: container (rw)
description:
List of top-level policy definitions, keyed by unique
name. These policy definitions are expected to be
referenced (by name) in policy chains specified in import
or export configuration statements.
frinx-device-type:
junos
frinx-supported-versions:
14any
frinx-implemented-reader:
io.frinx.cli.unit.junos.routing.policy.handler.policy.PolicyListReader
frinx-implemented-reader-details:
NAME_PATTERN:
policy\-statement\s+(?<name>\S+)\s+.*
SH_POLICY_STATEMENT:
show configuration policy-options
frinx-implemented-writer:
MISSING WRITER
frinx-device-type:
xr
frinx-supported-versions:
66
frinx-implemented-reader:
io.frinx.unitopo.unit.xr66.routing.policy.handlers.policy.PolicyDefinitionReader
frinx-implemented-writer:
MISSING WRITER
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.routing.policy.handler.policy.PolicyReader
frinx-implemented-reader-details:
ID_PATTERN:
route-policy (?<id>\S+)
SH_ALL_POLICY:
show running-config | include ^route-policy
frinx-implemented-writer:
MISSING WRITER
nodetype: list (rw)
list keys: [name]
description:
Reference to the list key
nodetype: leaf (list key) (rw)
type: leafref
description:
Configuration data for policy defintions
frinx-device-type:
junos
frinx-supported-versions:
14any
frinx-implemented-reader:
io.frinx.cli.unit.junos.routing.policy.handler.policy.PolicyConfigReader
frinx-implemented-writer:
io.frinx.cli.unit.junos.routing.policy.handler.policy.PolicyConfigWriter
frinx-implemented-writer-details:
SH_WRITE_POLICY_STATEMENT:
%s policy-options policy-statement %s
VERB_DEL:
delete
VERB_SET:
set
frinx-device-type:
xr
frinx-supported-versions:
66
frinx-implemented-reader:
io.frinx.unitopo.unit.xr66.routing.policy.handlers.policy.PolicyDefinitionConfigReader
frinx-implemented-writer:
io.frinx.unitopo.unit.xr66.routing.policy.handlers.policy.PolicyDefinitionConfigWriter
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.routing.policy.handler.policy.PolicyConfigReader
frinx-implemented-writer:
io.frinx.cli.unit.iosxr.routing.policy.handler.policy.PolicyConfigWriter
frinx-implemented-writer-details:
TEMPLATE:
route-policy {$config.name}
end-policy
nodetype: container (rw)
description:
Name of the top-level policy definition -- this name
is used in references to the current policy
nodetype: leaf (rw)
type: string
description:
Operational state data for policy definitions
nodetype: container (ro)
description:
Name of the top-level policy definition -- this name
is used in references to the current policy
nodetype: leaf (ro)
type: string
description:
Enclosing container for policy statements
frinx-device-type:
xr
frinx-supported-versions:
66
frinx-implemented-reader:
io.frinx.unitopo.unit.xr66.routing.policy.handlers.policy.StatementsReader
frinx-implemented-writer:
io.frinx.unitopo.unit.xr66.routing.policy.handlers.policy.StatementsWriter
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.routing.policy.handler.policy.StatementsReader
frinx-implemented-reader-details:
SH_PREFIX_SET:
show running-config route-policy %s
frinx-implemented-writer:
io.frinx.cli.unit.iosxr.routing.policy.handler.policy.StatementsWriter
nodetype: container (rw)
description:
Policy statements group conditions and actions
within a policy definition. They are evaluated in
the order specified (see the description of policy
evaluation at the top of this module.
frinx-device-type:
junos
frinx-supported-versions:
14any
frinx-implemented-reader:
io.frinx.cli.unit.junos.routing.policy.handler.policy.StatementListReader
frinx-implemented-reader-details:
NAME_PATTERN:
term\s+(?<name>\S+)\s+.*
SH_POLICY_TERM:
show configuration policy-options policy-statement %s
frinx-implemented-writer:
MISSING WRITER
frinx-device-type:
xr
frinx-supported-versions:
66
frinx-implemented-reader:
io.frinx.unitopo.unit.xr66.routing.policy.handlers.policy.StatementsReader
frinx-implemented-writer:
io.frinx.unitopo.unit.xr66.routing.policy.handlers.policy.StatementsWriter
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.routing.policy.handler.policy.StatementsReader
frinx-implemented-reader-details:
SH_PREFIX_SET:
show running-config route-policy %s
frinx-implemented-writer:
io.frinx.cli.unit.iosxr.routing.policy.handler.policy.StatementsWriter
nodetype: list (rw)
list keys: [name]
description:
Reference to list key
nodetype: leaf (list key) (rw)
type: leafref
description:
Configuration data for policy statements
frinx-device-type:
junos
frinx-supported-versions:
14any
frinx-implemented-reader:
io.frinx.cli.unit.junos.routing.policy.handler.policy.StatementConfigReader
frinx-implemented-writer:
io.frinx.cli.unit.junos.routing.policy.handler.policy.StatementConfigWriter
frinx-implemented-writer-details:
SH_DELETE_TERM:
delete policy-options policy-statement %s term %s
frinx-device-type:
xr
frinx-supported-versions:
66
frinx-implemented-reader:
io.frinx.unitopo.unit.xr66.routing.policy.handlers.policy.StatementsReader
frinx-implemented-writer:
io.frinx.unitopo.unit.xr66.routing.policy.handlers.policy.StatementsWriter
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.routing.policy.handler.policy.StatementsReader
frinx-implemented-reader-details:
SH_PREFIX_SET:
show running-config route-policy %s
frinx-implemented-writer:
io.frinx.cli.unit.iosxr.routing.policy.handler.policy.StatementsWriter
nodetype: container (rw)
description:
name of the policy statement
nodetype: leaf (rw)
type: string
description:
Operational state data for policy statements
nodetype: container (ro)
description:
name of the policy statement
nodetype: leaf (ro)
type: string
description:
Condition statements for the current policy statement
frinx-device-type:
xr
frinx-supported-versions:
66
frinx-implemented-reader:
io.frinx.unitopo.unit.xr66.routing.policy.handlers.policy.StatementsReader
frinx-implemented-writer:
io.frinx.unitopo.unit.xr66.routing.policy.handlers.policy.StatementsWriter
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.routing.policy.handler.policy.StatementsReader
frinx-implemented-reader-details:
SH_PREFIX_SET:
show running-config route-policy %s
frinx-implemented-writer:
io.frinx.cli.unit.iosxr.routing.policy.handler.policy.StatementsWriter
nodetype: container (rw)
description:
Configuration data for policy conditions
frinx-device-type:
xr
frinx-supported-versions:
66
frinx-implemented-reader:
io.frinx.unitopo.unit.xr66.routing.policy.handlers.policy.StatementsReader
frinx-implemented-writer:
io.frinx.unitopo.unit.xr66.routing.policy.handlers.policy.StatementsWriter
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.routing.policy.handler.policy.StatementsReader
frinx-implemented-reader-details:
SH_PREFIX_SET:
show running-config route-policy %s
frinx-implemented-writer:
io.frinx.cli.unit.iosxr.routing.policy.handler.policy.StatementsWriter
nodetype: container (rw)
description:
Applies the statements from the specified policy
definition and then returns control the current
policy statement. Note that the called policy may
itself call other policies (subject to
implementation limitations). This is intended to
provide a policy 'subroutine' capability. The
called policy should contain an explicit or a
default route disposition that returns an
effective true (accept-route) or false
(reject-route), otherwise the behavior may be
ambiguous and implementation dependent
nodetype: leaf (rw)
type: leafref
description:
Condition to check the protocol / method used to install
the route into the local routing table
nodetype: leaf (rw)
type: identityref
description:
Operational state data for policy conditions
nodetype: container (ro)
description:
Applies the statements from the specified policy
definition and then returns control the current
policy statement. Note that the called policy may
itself call other policies (subject to
implementation limitations). This is intended to
provide a policy 'subroutine' capability. The
called policy should contain an explicit or a
default route disposition that returns an
effective true (accept-route) or false
(reject-route), otherwise the behavior may be
ambiguous and implementation dependent
nodetype: leaf (ro)
type: leafref
description:
Condition to check the protocol / method used to install
the route into the local routing table
nodetype: leaf (ro)
type: identityref
description:
Top-level container for interface match conditions
nodetype: container (rw)
description:
Configuration data for interface match conditions
nodetype: container (rw)
description:
Reference to a base interface. If a reference to a
subinterface is required, this leaf must be specified
to indicate the base interface.
nodetype: leaf (rw)
type: leafref
description:
Reference to a subinterface -- this requires the base
interface to be specified using the interface leaf in
this container. If only a reference to a base interface
is requuired, this leaf should not be set.
nodetype: leaf (rw)
type: leafref
description:
Operational state data for interface match conditions
nodetype: container (ro)
description:
Reference to a base interface. If a reference to a
subinterface is required, this leaf must be specified
to indicate the base interface.
nodetype: leaf (ro)
type: leafref
description:
Reference to a subinterface -- this requires the base
interface to be specified using the interface leaf in
this container. If only a reference to a base interface
is requuired, this leaf should not be set.
nodetype: leaf (ro)
type: leafref
description:
Match a referenced prefix-set according to the logic
defined in the match-set-options leaf
frinx-device-type:
xr
frinx-supported-versions:
66
frinx-implemented-reader:
io.frinx.unitopo.unit.xr66.routing.policy.handlers.policy.StatementsReader
frinx-implemented-writer:
io.frinx.unitopo.unit.xr66.routing.policy.handlers.policy.StatementsWriter
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.routing.policy.handler.policy.StatementsReader
frinx-implemented-reader-details:
SH_PREFIX_SET:
show running-config route-policy %s
frinx-implemented-writer:
io.frinx.cli.unit.iosxr.routing.policy.handler.policy.StatementsWriter
nodetype: container (rw)
description:
Configuration data for a prefix-set condition
frinx-device-type:
xr
frinx-supported-versions:
66
frinx-implemented-reader:
io.frinx.unitopo.unit.xr66.routing.policy.handlers.policy.StatementsReader
frinx-implemented-writer:
io.frinx.unitopo.unit.xr66.routing.policy.handlers.policy.StatementsWriter
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.routing.policy.handler.policy.StatementsReader
frinx-implemented-reader-details:
SH_PREFIX_SET:
show running-config route-policy %s
frinx-implemented-writer:
io.frinx.cli.unit.iosxr.routing.policy.handler.policy.StatementsWriter
nodetype: container (rw)
description:
References a defined prefix set
nodetype: leaf (rw)
type: leafref
description:
Optional parameter that governs the behaviour of the
match operation. This leaf only supports matching on ANY
member of the set or inverting the match. Matching on ALL is
not supported
nodetype: leaf (rw)
type: oc-pol-types:match-set-options-restricted-type
description:
Operational state data for a prefix-set condition
nodetype: container (ro)
description:
References a defined prefix set
nodetype: leaf (ro)
type: leafref
description:
Optional parameter that governs the behaviour of the
match operation. This leaf only supports matching on ANY
member of the set or inverting the match. Matching on ALL is
not supported
nodetype: leaf (ro)
type: oc-pol-types:match-set-options-restricted-type
description:
Match a referenced neighbor set according to the logic
defined in the match-set-options-leaf
nodetype: container (rw)
description:
Configuration data
nodetype: container (rw)
description:
References a defined neighbor set
nodetype: leaf (rw)
type: leafref
description:
Optional parameter that governs the behaviour of the
match operation. This leaf only supports matching on ANY
member of the set or inverting the match. Matching on ALL is
not supported
nodetype: leaf (rw)
type: oc-pol-types:match-set-options-restricted-type
description:
Operational state data
nodetype: container (ro)
description:
References a defined neighbor set
nodetype: leaf (ro)
type: leafref
description:
Optional parameter that governs the behaviour of the
match operation. This leaf only supports matching on ANY
member of the set or inverting the match. Matching on ALL is
not supported
nodetype: leaf (ro)
type: oc-pol-types:match-set-options-restricted-type
description:
Match a referenced tag set according to the logic defined
in the match-options-set leaf
nodetype: container (rw)
description:
Configuration data for tag-set conditions
nodetype: container (rw)
description:
References a defined tag set
nodetype: leaf (rw)
type: leafref
description:
Optional parameter that governs the behaviour of the
match operation. This leaf only supports matching on ANY
member of the set or inverting the match. Matching on ALL is
not supported
nodetype: leaf (rw)
type: oc-pol-types:match-set-options-restricted-type
description:
Operational state data tag-set conditions
nodetype: container (ro)
description:
References a defined tag set
nodetype: leaf (ro)
type: leafref
description:
Optional parameter that governs the behaviour of the
match operation. This leaf only supports matching on ANY
member of the set or inverting the match. Matching on ALL is
not supported
nodetype: leaf (ro)
type: oc-pol-types:match-set-options-restricted-type
description:
Top-level container
frinx-device-type:
xr
frinx-supported-versions:
66
frinx-implemented-reader:
io.frinx.unitopo.unit.xr66.routing.policy.handlers.policy.StatementsReader
frinx-implemented-writer:
io.frinx.unitopo.unit.xr66.routing.policy.handlers.policy.StatementsWriter
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.routing.policy.handler.policy.StatementsReader
frinx-implemented-reader-details:
SH_PREFIX_SET:
show running-config route-policy %s
frinx-implemented-writer:
io.frinx.cli.unit.iosxr.routing.policy.handler.policy.StatementsWriter
nodetype: container (rw)
description:
Configuration data for BGP-specific policy conditions
frinx-device-type:
xr
frinx-supported-versions:
66
frinx-implemented-reader:
io.frinx.unitopo.unit.xr66.routing.policy.handlers.policy.StatementsReader
frinx-implemented-writer:
io.frinx.unitopo.unit.xr66.routing.policy.handlers.policy.StatementsWriter
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.routing.policy.handler.policy.StatementsReader
frinx-implemented-reader-details:
SH_PREFIX_SET:
show running-config route-policy %s
frinx-implemented-writer:
io.frinx.cli.unit.iosxr.routing.policy.handler.policy.StatementsWriter
nodetype: container (rw)
description:
Condition to check if the received MED value is equal to
the specified value
nodetype: leaf (rw)
type: uint32
description:
Condition to check if the route origin is equal to the
specified value
nodetype: leaf (rw)
type: oc-bgp-types:bgp-origin-attr-type
description:
List of next hop addresses to check for in the route
update
nodetype: leaf-list (rw)
type: oc-inet:ip-address
description:
List of address families which the NLRI may be
within
nodetype: leaf-list (rw)
type: identityref
description:
Condition to check if the local pref attribute is equal to
the specified value
nodetype: leaf (rw)
type: uint32
description:
Condition to check the route type in the route update
nodetype: leaf (rw)
type: enumeration
description:
Operational state data for BGP-specific policy
conditions
nodetype: container (ro)
description:
Condition to check if the received MED value is equal to
the specified value
nodetype: leaf (ro)
type: uint32
description:
Condition to check if the route origin is equal to the
specified value
nodetype: leaf (ro)
type: oc-bgp-types:bgp-origin-attr-type
description:
List of next hop addresses to check for in the route
update
nodetype: leaf-list (ro)
type: oc-inet:ip-address
description:
List of address families which the NLRI may be
within
nodetype: leaf-list (ro)
type: identityref
description:
Condition to check if the local pref attribute is equal to
the specified value
nodetype: leaf (ro)
type: uint32
description:
Condition to check the route type in the route update
nodetype: leaf (ro)
type: enumeration
description:
Value and comparison operations for conditions based on the
number of communities in the route update
nodetype: container (rw)
description:
Configuration data for community count condition
nodetype: container (rw)
description:
type of comparison to be performed
nodetype: leaf (rw)
type: identityref
description:
value to compare with the community count
nodetype: leaf (rw)
type: uint32
description:
Operational state data for community count condition
nodetype: container (ro)
description:
type of comparison to be performed
nodetype: leaf (ro)
type: identityref
description:
value to compare with the community count
nodetype: leaf (ro)
type: uint32
description:
Value and comparison operations for conditions based on the
length of the AS path in the route update
frinx-device-type:
xr
frinx-supported-versions:
66
frinx-implemented-reader:
io.frinx.unitopo.unit.xr66.routing.policy.handlers.policy.StatementsReader
frinx-implemented-writer:
io.frinx.unitopo.unit.xr66.routing.policy.handlers.policy.StatementsWriter
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.routing.policy.handler.policy.StatementsReader
frinx-implemented-reader-details:
SH_PREFIX_SET:
show running-config route-policy %s
frinx-implemented-writer:
io.frinx.cli.unit.iosxr.routing.policy.handler.policy.StatementsWriter
nodetype: container (rw)
description:
Configuration data for AS path length condition
frinx-device-type:
xr
frinx-supported-versions:
66
frinx-implemented-reader:
io.frinx.unitopo.unit.xr66.routing.policy.handlers.policy.StatementsReader
frinx-implemented-writer:
io.frinx.unitopo.unit.xr66.routing.policy.handlers.policy.StatementsWriter
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.routing.policy.handler.policy.StatementsReader
frinx-implemented-reader-details:
SH_PREFIX_SET:
show running-config route-policy %s
frinx-implemented-writer:
io.frinx.cli.unit.iosxr.routing.policy.handler.policy.StatementsWriter
nodetype: container (rw)
description:
type of comparison to be performed
nodetype: leaf (rw)
type: identityref
description:
value to compare with the community count
nodetype: leaf (rw)
type: uint32
description:
Operational state data for AS path length condition
nodetype: container (ro)
description:
type of comparison to be performed
nodetype: leaf (ro)
type: identityref
description:
value to compare with the community count
nodetype: leaf (ro)
type: uint32
description:
Top-level container for match conditions on communities.
Match a referenced community-set according to the logic
defined in the match-set-options leaf
frinx-device-type:
xr
frinx-supported-versions:
66
frinx-implemented-reader:
io.frinx.unitopo.unit.xr66.routing.policy.handlers.policy.StatementsReader
frinx-implemented-writer:
io.frinx.unitopo.unit.xr66.routing.policy.handlers.policy.StatementsWriter
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.routing.policy.handler.policy.StatementsReader
frinx-implemented-reader-details:
SH_PREFIX_SET:
show running-config route-policy %s
frinx-implemented-writer:
io.frinx.cli.unit.iosxr.routing.policy.handler.policy.StatementsWriter
nodetype: container (rw)
description:
Configuration data for match conditions on communities
frinx-device-type:
xr
frinx-supported-versions:
66
frinx-implemented-reader:
io.frinx.unitopo.unit.xr66.routing.policy.handlers.policy.StatementsReader
frinx-implemented-writer:
io.frinx.unitopo.unit.xr66.routing.policy.handlers.policy.StatementsWriter
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.routing.policy.handler.policy.StatementsReader
frinx-implemented-reader-details:
SH_PREFIX_SET:
show running-config route-policy %s
frinx-implemented-writer:
io.frinx.cli.unit.iosxr.routing.policy.handler.policy.StatementsWriter
nodetype: container (rw)
description:
References a defined community set
nodetype: leaf (rw)
type: leafref
description:
Optional parameter that governs the behaviour of the
match operation
nodetype: leaf (rw)
type: oc-pol-types:match-set-options-type
description:
Operational state data
nodetype: container (ro)
description:
References a defined community set
nodetype: leaf (ro)
type: leafref
description:
Optional parameter that governs the behaviour of the
match operation
nodetype: leaf (ro)
type: oc-pol-types:match-set-options-type
description:
Match a referenced extended community-set according to the
logic defined in the match-set-options leaf
nodetype: container (rw)
description:
Configuration data for match conditions on extended
communities
nodetype: container (rw)
description:
References a defined extended community set
nodetype: leaf (rw)
type: leafref
description:
Optional parameter that governs the behaviour of the
match operation
nodetype: leaf (rw)
type: oc-pol-types:match-set-options-type
description:
Operational state data for match conditions on extended
communities
nodetype: container (ro)
description:
References a defined extended community set
nodetype: leaf (ro)
type: leafref
description:
Optional parameter that governs the behaviour of the
match operation
nodetype: leaf (ro)
type: oc-pol-types:match-set-options-type
description:
Match a referenced as-path set according to the logic
defined in the match-set-options leaf
frinx-device-type:
xr
frinx-supported-versions:
66
frinx-implemented-reader:
io.frinx.unitopo.unit.xr66.routing.policy.handlers.policy.StatementsReader
frinx-implemented-writer:
io.frinx.unitopo.unit.xr66.routing.policy.handlers.policy.StatementsWriter
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.routing.policy.handler.policy.StatementsReader
frinx-implemented-reader-details:
SH_PREFIX_SET:
show running-config route-policy %s
frinx-implemented-writer:
io.frinx.cli.unit.iosxr.routing.policy.handler.policy.StatementsWriter
nodetype: container (rw)
description:
Configuration data for match conditions on AS path set
frinx-device-type:
xr
frinx-supported-versions:
66
frinx-implemented-reader:
io.frinx.unitopo.unit.xr66.routing.policy.handlers.policy.StatementsReader
frinx-implemented-writer:
io.frinx.unitopo.unit.xr66.routing.policy.handlers.policy.StatementsWriter
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.routing.policy.handler.policy.StatementsReader
frinx-implemented-reader-details:
SH_PREFIX_SET:
show running-config route-policy %s
frinx-implemented-writer:
io.frinx.cli.unit.iosxr.routing.policy.handler.policy.StatementsWriter
nodetype: container (rw)
description:
References a defined AS path set
nodetype: leaf (rw)
type: leafref
description:
Optional parameter that governs the behaviour of the
match operation
nodetype: leaf (rw)
type: oc-pol-types:match-set-options-type
description:
Operational state data for match conditions on AS
path set
nodetype: container (ro)
description:
References a defined AS path set
nodetype: leaf (ro)
type: leafref
description:
Optional parameter that governs the behaviour of the
match operation
nodetype: leaf (ro)
type: oc-pol-types:match-set-options-type
description:
Match conditions specific to OSPF
nodetype: container (rw)
description:
Configuration parameters relating to OSPF match conditions
nodetype: container (rw)
description:
Match prefixes which are within a particular OSPF area
nodetype: leaf (rw)
type: oc-ospf-types:ospf-area-identifier
description:
Operational state parameters relating to OSPF match conditions
nodetype: container (ro)
description:
Match prefixes which are within a particular OSPF area
nodetype: leaf (ro)
type: oc-ospf-types:ospf-area-identifier
description:
Top-level container for protocol instance match condition
in policy statements. The protocol instance is referenced
by an identifier and name
nodetype: container (rw)
description:
Configuration data for policy matching on protocol
instance
frinx-device-type:
junos
frinx-supported-versions:
14any
frinx-implemented-reader:
io.frinx.cli.unit.junos.routing.policy.handler.conditions.protocol.ProtocolConfigReader
frinx-implemented-reader-details:
INSTANCE_NAME_PARTEN:
instance\s+(?<name>\S+);
PROTOCOL_TYPE_PARTEN:
protocol\s+(?<type>\S+);
SH_INSTANCE_NAME:
show configuration policy-options policy-statement %s term %s from instance
SH_PROTOCOL_TYPE:
show configuration policy-options policy-statement %s term %s from protocol
frinx-implemented-writer:
io.frinx.cli.unit.junos.routing.policy.handler.conditions.protocol.ProtocolConfigWriter
frinx-implemented-writer-details:
SH_WRITE_INSTANCE_NAME:
%s policy-options policy-statement %s term %s from instance %s
SH_WRITE_PROTOCOL_TYPE:
%s policy-options policy-statement %s term %s from protocol %s
VERB_DEL:
delete
VERB_SET:
set
nodetype: container (rw)
description:
The identifier (protocol type) of the
protocol instance to match on in the local network
instance.
nodetype: leaf (rw)
type: identityref
description:
The name of the protocol instance to match
on in the local network instance
nodetype: leaf (rw)
type: string
description:
Operational state data for policy matching on protocol instance
nodetype: container (ro)
description:
The identifier (protocol type) of the
protocol instance to match on in the local network
instance.
nodetype: leaf (ro)
type: identityref
description:
The name of the protocol instance to match
on in the local network instance
nodetype: leaf (ro)
type: string
description:
Match conditions relating to the IS-IS protocol
nodetype: container (rw)
description:
Configuration parameters relating to IS-IS match
conditions
nodetype: container (rw)
description:
Match the level that the IS-IS prefix is within. This can
be used in the case that import or export policies refer
to an IS-IS instance that has multiple levels configured
within it
nodetype: leaf (rw)
type: isis-types:level-number
description:
Operational state parameters relating to IS-IS match
conditions
nodetype: container (ro)
description:
Match the level that the IS-IS prefix is within. This can
be used in the case that import or export policies refer
to an IS-IS instance that has multiple levels configured
within it
nodetype: leaf (ro)
type: isis-types:level-number
description:
Top-level container for policy action statements
frinx-device-type:
xr
frinx-supported-versions:
66
frinx-implemented-reader:
io.frinx.unitopo.unit.xr66.routing.policy.handlers.policy.StatementsReader
frinx-implemented-writer:
io.frinx.unitopo.unit.xr66.routing.policy.handlers.policy.StatementsWriter
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.routing.policy.handler.policy.StatementsReader
frinx-implemented-reader-details:
SH_PREFIX_SET:
show running-config route-policy %s
frinx-implemented-writer:
io.frinx.cli.unit.iosxr.routing.policy.handler.policy.StatementsWriter
nodetype: container (rw)
description:
Configuration data for policy actions
frinx-device-type:
junos
frinx-supported-versions:
14any
frinx-implemented-reader:
io.frinx.cli.unit.junos.routing.policy.handler.actions.ActionsConfigReader
frinx-implemented-reader-details:
ACTION_PARTEN:
(?<action>\S+);
SH_SHOW_ACTION:
show configuration policy-options policy-statement %s term %s then
frinx-implemented-writer:
io.frinx.cli.unit.junos.routing.policy.handler.actions.ActionsConfigWriter
frinx-implemented-writer-details:
SH_WRITE_POLICY_RESULT:
%s policy-options policy-statement %s term %s then %s
VERB_DEL:
delete
VERB_SET:
set
frinx-device-type:
xr
frinx-supported-versions:
66
frinx-implemented-reader:
io.frinx.unitopo.unit.xr66.routing.policy.handlers.policy.StatementsReader
frinx-implemented-writer:
io.frinx.unitopo.unit.xr66.routing.policy.handlers.policy.StatementsWriter
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.routing.policy.handler.policy.StatementsReader
frinx-implemented-reader-details:
SH_PREFIX_SET:
show running-config route-policy %s
frinx-implemented-writer:
io.frinx.cli.unit.iosxr.routing.policy.handler.policy.StatementsWriter
nodetype: container (rw)
description:
Select the final disposition for the route, either
accept or reject.
nodetype: leaf (rw)
type: policy-result-type
description:
Operational state data for policy actions
nodetype: container (ro)
description:
Select the final disposition for the route, either
accept or reject.
nodetype: leaf (ro)
type: policy-result-type
description:
Top-level container for BGP-specific actions
frinx-device-type:
xr
frinx-supported-versions:
66
frinx-implemented-reader:
io.frinx.unitopo.unit.xr66.routing.policy.handlers.policy.StatementsReader
frinx-implemented-writer:
io.frinx.unitopo.unit.xr66.routing.policy.handlers.policy.StatementsWriter
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.routing.policy.handler.policy.StatementsReader
frinx-implemented-reader-details:
SH_PREFIX_SET:
show running-config route-policy %s
frinx-implemented-writer:
io.frinx.cli.unit.iosxr.routing.policy.handler.policy.StatementsWriter
nodetype: container (rw)
description:
Configuration data for BGP-specific actions
frinx-device-type:
xr
frinx-supported-versions:
66
frinx-implemented-reader:
io.frinx.unitopo.unit.xr66.routing.policy.handlers.policy.StatementsReader
frinx-implemented-writer:
io.frinx.unitopo.unit.xr66.routing.policy.handlers.policy.StatementsWriter
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.routing.policy.handler.policy.StatementsReader
frinx-implemented-reader-details:
SH_PREFIX_SET:
show running-config route-policy %s
frinx-implemented-writer:
io.frinx.cli.unit.iosxr.routing.policy.handler.policy.StatementsWriter
nodetype: container (rw)
description:
set the origin attribute to the specified
value
nodetype: leaf (rw)
type: oc-bgp-types:bgp-origin-attr-type
description:
set the local pref attribute on the route
update
nodetype: leaf (rw)
type: uint32
description:
set the next-hop attribute in the route update
nodetype: leaf (rw)
type: bgp-next-hop-type
description:
set the med metric attribute in the route
update
nodetype: leaf (rw)
type: bgp-set-med-type
description:
Operational state data for BGP-specific actions
nodetype: container (ro)
description:
set the origin attribute to the specified
value
nodetype: leaf (ro)
type: oc-bgp-types:bgp-origin-attr-type
description:
set the local pref attribute on the route
update
nodetype: leaf (ro)
type: uint32
description:
set the next-hop attribute in the route update
nodetype: leaf (ro)
type: bgp-next-hop-type
description:
set the med metric attribute in the route
update
nodetype: leaf (ro)
type: bgp-set-med-type
description:
Action to prepend the specified AS number to the AS-path a
specified number of times
frinx-device-type:
xr
frinx-supported-versions:
66
frinx-implemented-reader:
io.frinx.unitopo.unit.xr66.routing.policy.handlers.policy.StatementsReader
frinx-implemented-writer:
io.frinx.unitopo.unit.xr66.routing.policy.handlers.policy.StatementsWriter
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.routing.policy.handler.policy.StatementsReader
frinx-implemented-reader-details:
SH_PREFIX_SET:
show running-config route-policy %s
frinx-implemented-writer:
io.frinx.cli.unit.iosxr.routing.policy.handler.policy.StatementsWriter
nodetype: container (rw)
description:
Configuration data for the AS path prepend action
frinx-device-type:
xr
frinx-supported-versions:
66
frinx-implemented-reader:
io.frinx.unitopo.unit.xr66.routing.policy.handlers.policy.StatementsReader
frinx-implemented-writer:
io.frinx.unitopo.unit.xr66.routing.policy.handlers.policy.StatementsWriter
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.routing.policy.handler.policy.StatementsReader
frinx-implemented-reader-details:
SH_PREFIX_SET:
show running-config route-policy %s
frinx-implemented-writer:
io.frinx.cli.unit.iosxr.routing.policy.handler.policy.StatementsWriter
nodetype: container (rw)
description:
Number of times to prepend the value specified in the asn
leaf to the AS path. If no value is specified by the asn
leaf, the local AS number of the system is used. The value
should be between 1 and the maximum supported by the
implementation.
nodetype: leaf (rw)
type: uint8
description:
The AS number to prepend to the AS path. If this leaf is
not specified and repeat-n is set, then the local AS
number will be used for prepending.
nodetype: leaf (rw)
type: oc-inet:as-number
description:
Operational state data for the AS path prepend action
nodetype: container (ro)
description:
Number of times to prepend the value specified in the asn
leaf to the AS path. If no value is specified by the asn
leaf, the local AS number of the system is used. The value
should be between 1 and the maximum supported by the
implementation.
nodetype: leaf (ro)
type: uint8
description:
The AS number to prepend to the AS path. If this leaf is
not specified and repeat-n is set, then the local AS
number will be used for prepending.
nodetype: leaf (ro)
type: oc-inet:as-number
description:
Action to set the community attributes of the route, along
with options to modify how the community is modified.
Communities may be set using an inline list OR
reference to an existing defined set (not both).
frinx-device-type:
xr
frinx-supported-versions:
66
frinx-implemented-reader:
io.frinx.unitopo.unit.xr66.routing.policy.handlers.policy.StatementsReader
frinx-implemented-writer:
io.frinx.unitopo.unit.xr66.routing.policy.handlers.policy.StatementsWriter
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.routing.policy.handler.policy.StatementsReader
frinx-implemented-reader-details:
SH_PREFIX_SET:
show running-config route-policy %s
frinx-implemented-writer:
io.frinx.cli.unit.iosxr.routing.policy.handler.policy.StatementsWriter
nodetype: container (rw)
description:
Configuration data for the set-community action
frinx-device-type:
xr
frinx-supported-versions:
66
frinx-implemented-reader:
io.frinx.unitopo.unit.xr66.routing.policy.handlers.policy.StatementsReader
frinx-implemented-writer:
io.frinx.unitopo.unit.xr66.routing.policy.handlers.policy.StatementsWriter
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.routing.policy.handler.policy.StatementsReader
frinx-implemented-reader-details:
SH_PREFIX_SET:
show running-config route-policy %s
frinx-implemented-writer:
io.frinx.cli.unit.iosxr.routing.policy.handler.policy.StatementsWriter
nodetype: container (rw)
description:
Indicates the method used to specify the extended
communities for the set-ext-community action
nodetype: leaf (rw)
type: enumeration
description:
Options for modifying the community attribute with
the specified values. These options apply to both
methods of setting the community attribute.
nodetype: leaf (rw)
type: bgp-set-community-option-type
description:
Operational state data for the set-community action
nodetype: container (ro)
description:
Indicates the method used to specify the extended
communities for the set-ext-community action
nodetype: leaf (ro)
type: enumeration
description:
Options for modifying the community attribute with
the specified values. These options apply to both
methods of setting the community attribute.
nodetype: leaf (ro)
type: bgp-set-community-option-type
description:
Set the community values for the action inline with
a list.
frinx-device-type:
xr
frinx-supported-versions:
66
frinx-implemented-reader:
io.frinx.unitopo.unit.xr66.routing.policy.handlers.policy.StatementsReader
frinx-implemented-writer:
io.frinx.unitopo.unit.xr66.routing.policy.handlers.policy.StatementsWriter
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.routing.policy.handler.policy.StatementsReader
frinx-implemented-reader-details:
SH_PREFIX_SET:
show running-config route-policy %s
frinx-implemented-writer:
io.frinx.cli.unit.iosxr.routing.policy.handler.policy.StatementsWriter
nodetype: container (rw)
description:
Configuration data or inline specification of set-community
action
frinx-device-type:
xr
frinx-supported-versions:
66
frinx-implemented-reader:
io.frinx.unitopo.unit.xr66.routing.policy.handlers.policy.StatementsReader
frinx-implemented-writer:
io.frinx.unitopo.unit.xr66.routing.policy.handlers.policy.StatementsWriter
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.routing.policy.handler.policy.StatementsReader
frinx-implemented-reader-details:
SH_PREFIX_SET:
show running-config route-policy %s
frinx-implemented-writer:
io.frinx.cli.unit.iosxr.routing.policy.handler.policy.StatementsWriter
nodetype: container (rw)
description:
Set the community values for the update inline with
a list.
nodetype: leaf-list (rw)
type: union
type: oc-bgp-types:bgp-std-community-type
type: identityref
description:
Operational state data or inline specification of
set-community action
nodetype: container (ro)
description:
Set the community values for the update inline with
a list.
nodetype: leaf-list (ro)
type: union
type: oc-bgp-types:bgp-std-community-type
type: identityref
description:
Provide a reference to a defined community set for the
set-community action
frinx-device-type:
xr
frinx-supported-versions:
66
frinx-implemented-reader:
io.frinx.unitopo.unit.xr66.routing.policy.handlers.policy.StatementsReader
frinx-implemented-writer:
io.frinx.unitopo.unit.xr66.routing.policy.handlers.policy.StatementsWriter
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.routing.policy.handler.policy.StatementsReader
frinx-implemented-reader-details:
SH_PREFIX_SET:
show running-config route-policy %s
frinx-implemented-writer:
io.frinx.cli.unit.iosxr.routing.policy.handler.policy.StatementsWriter
nodetype: container (rw)
description:
Configuration data for referening a community-set in the
set-community action
frinx-device-type:
xr
frinx-supported-versions:
66
frinx-implemented-reader:
io.frinx.unitopo.unit.xr66.routing.policy.handlers.policy.StatementsReader
frinx-implemented-writer:
io.frinx.unitopo.unit.xr66.routing.policy.handlers.policy.StatementsWriter
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.routing.policy.handler.policy.StatementsReader
frinx-implemented-reader-details:
SH_PREFIX_SET:
show running-config route-policy %s
frinx-implemented-writer:
io.frinx.cli.unit.iosxr.routing.policy.handler.policy.StatementsWriter
nodetype: container (rw)
description:
References a defined community set by name
nodetype: leaf (rw)
type: leafref
description:
Operational state data for referening a community-set
in the set-community action
nodetype: container (ro)
description:
References a defined community set by name
nodetype: leaf (ro)
type: leafref
description:
Action to set the extended community attributes of the
route, along with options to modify how the community is
modified. Extended communities may be set using an inline
list OR a reference to an existing defined set (but not
both).
nodetype: container (rw)
description:
Configuration data for the set-ext-community action
nodetype: container (rw)
description:
Indicates the method used to specify the extended
communities for the set-ext-community action
nodetype: leaf (rw)
type: enumeration
description:
Options for modifying the community attribute with
the specified values. These options apply to both
methods of setting the community attribute.
nodetype: leaf (rw)
type: bgp-set-community-option-type
description:
Operational state data for the set-ext-community action
nodetype: container (ro)
description:
Indicates the method used to specify the extended
communities for the set-ext-community action
nodetype: leaf (ro)
type: enumeration
description:
Options for modifying the community attribute with
the specified values. These options apply to both
methods of setting the community attribute.
nodetype: leaf (ro)
type: bgp-set-community-option-type
description:
Set the extended community values for the action inline with
a list.
nodetype: container (rw)
description:
Configuration data or inline specification of
set-ext-community action
nodetype: container (rw)
description:
Set the extended community values for the update inline
with a list.
nodetype: leaf-list (rw)
type: union
type: oc-bgp-types:bgp-ext-community-type
type: identityref
description:
Operational state data or inline specification of
set-ext-community action
nodetype: container (ro)
description:
Set the extended community values for the update inline
with a list.
nodetype: leaf-list (ro)
type: union
type: oc-bgp-types:bgp-ext-community-type
type: identityref
description:
Provide a reference to an extended community set for the
set-ext-community action
nodetype: container (rw)
description:
Configuration data for referening an extended
community-set in the set-ext-community action
nodetype: container (rw)
description:
References a defined extended community set by
name
nodetype: leaf (rw)
type: leafref
description:
Operational state data for referening an extended
community-set in the set-ext-community action
nodetype: container (ro)
description:
References a defined extended community set by
name
nodetype: leaf (ro)
type: leafref
description:
Actions specific to OSPF
nodetype: container (rw)
description:
Configuration parameters for OSPF actions
nodetype: container (rw)
description:
Set the area for the matched route. This action is typically
used when importing prefixes into OSPF, such that a route can
be imported into a specific area within the instance.
nodetype: leaf (rw)
type: oc-ospf-types:ospf-area-identifier
description:
Operational state parameters for OSPF actions
nodetype: container (ro)
description:
Set the area for the matched route. This action is typically
used when importing prefixes into OSPF, such that a route can
be imported into a specific area within the instance.
nodetype: leaf (ro)
type: oc-ospf-types:ospf-area-identifier
description:
Configuration and state parameters relating to manipulating
the OSPF metric
nodetype: container (rw)
description:
Configuration parameters relating to setting the OSPF metric
frinx-device-type:
junos
frinx-supported-versions:
14any
frinx-implemented-reader:
io.frinx.cli.unit.junos.routing.policy.handler.actions.ospf.actions.SetMetricConfigReader
frinx-implemented-reader-details:
ACTION_METRIC_PARTEN:
(?<value>\S+);
SH_ACTION_METRIC:
show configuration policy-options policy-statement %s term %s then metric
frinx-implemented-writer:
io.frinx.cli.unit.junos.routing.policy.handler.actions.ospf.actions.SetMetricConfigWriter
frinx-implemented-writer-details:
SH_DELETE_ACTION_METRIC:
delete policy-options policy-statement %s term %s then metric
SH_WRITE_ACTION_METRIC:
set policy-options policy-statement %s term %s then metric %s
nodetype: container (rw)
description:
Specify the type of metric which is to be set by the policy
nodetype: leaf (rw)
type: enumeration
description:
Set the metric of the routes matching the policy to the value
specified by this leaf.
nodetype: leaf (rw)
type: oc-ospf-types:ospf-metric
description:
Operational state parameters relating to setting the OSPF
metric
nodetype: container (ro)
description:
Specify the type of metric which is to be set by the policy
nodetype: leaf (ro)
type: enumeration
description:
Set the metric of the routes matching the policy to the value
specified by this leaf.
nodetype: leaf (ro)
type: oc-ospf-types:ospf-metric
description:
Actions that can be performed by IS-IS within a policy
nodetype: container (rw)
description:
Configuration parameters relating to IS-IS actions
nodetype: container (rw)
description:
Set the level that a prefix is to be imported into.
nodetype: leaf (rw)
type: isis-types:level-number
description:
Set the type of metric that is to be specified when the
set metric leaf is specified
nodetype: leaf (rw)
type: isis-types:level-number
description:
Set the metric of the IS-IS prefix
nodetype: leaf (rw)
type: isis-types:wide-metric
description:
Operational state associated with IS-IS actions
nodetype: container (ro)
description:
Set the level that a prefix is to be imported into.
nodetype: leaf (ro)
type: isis-types:level-number
description:
Set the type of metric that is to be specified when the
set metric leaf is specified
nodetype: leaf (ro)
type: isis-types:level-number
description:
Set the metric of the IS-IS prefix
nodetype: leaf (ro)
type: isis-types:wide-metric
This module contains general type definitions and identities for optical transport models.
frinx-openconfig-platform-types
frinx-openconfig-extensions
description:
Loopback modes for transponder logical channels
type: enumeration
description:
Type for optical spectrum frequency values
type: uint64
units: MHz
description:
Administrative state modes for
logical channels in the transponder model.
type: enumeration
description:
Base identity for identifying the type of pluggable optic
transceiver (i.e,. form factor) used in a port.
description:
1/2 C form-factor pluggable, that can support up to a
200 Gb/s signal with 10x10G, 4x25G, or 8x25G physical
channels
base identity: TRANSCEIVER_FORM_FACTOR_TYPE
description:
QSFP pluggable optic with support for up to 4x28G physical
channels
base identity: TRANSCEIVER_FORM_FACTOR_TYPE
description:
OriginalQuad Small Form-factor Pluggable transceiver that can
support 4x1G physical channels. Not commonly used.
base identity: TRANSCEIVER_FORM_FACTOR_TYPE
description:
1/4 C form-factor pluggable, that can support up to a
100 Gb/s signal with 10x10G or 4x25G physical channels
base identity: TRANSCEIVER_FORM_FACTOR_TYPE
description:
Small form-factor pluggable transceiver supporting up to
10 Gb/s signal
base identity: TRANSCEIVER_FORM_FACTOR_TYPE
description:
Enhanced small form-factor pluggable transceiver supporting
up to 16 Gb/s signals, including 10 GbE and OTU2
base identity: TRANSCEIVER_FORM_FACTOR_TYPE
description:
Cisco CPAK transceiver supporting 100 Gb/s.
base identity: TRANSCEIVER_FORM_FACTOR_TYPE
description:
Represents a port that does not require a pluggable optic,
e.g., with on-board optics like COBO
base identity: TRANSCEIVER_FORM_FACTOR_TYPE
description:
Represents a transceiver form factor not otherwise listed
base identity: TRANSCEIVER_FORM_FACTOR_TYPE
description:
CFP2 analog coherent optics transceiver, supporting
100 Gb, 200Gb, and 250 Gb/s signal.
base identity: TRANSCEIVER_FORM_FACTOR_TYPE
description:
10 Gigabit small form factor pluggable transceiver supporting
10 GbE using a XAUI inerface and 4 data channels.
base identity: TRANSCEIVER_FORM_FACTOR_TYPE
description:
10 Gigabit small form factor pluggable transceiver supporting
10 GbE and OTU2
base identity: TRANSCEIVER_FORM_FACTOR_TYPE
description:
Quad Small Form-factor Pluggable transceiver that can support
up to 4x10G physical channels.
base identity: TRANSCEIVER_FORM_FACTOR_TYPE
description:
C form-factor pluggable, that can support up to a
100 Gb/s signal with 10x10G or 4x25G physical channels
base identity: TRANSCEIVER_FORM_FACTOR_TYPE
description:
Rate of tributary signal _- identities will typically reflect
rounded bit rate.
description:
400G tributary signal rate
base identity: TRIBUTARY_RATE_CLASS_TYPE
description:
40G tributary signal rate
base identity: TRIBUTARY_RATE_CLASS_TYPE
description:
200G tributary signal rate
base identity: TRIBUTARY_RATE_CLASS_TYPE
description:
150G tributary signal rate
base identity: TRIBUTARY_RATE_CLASS_TYPE
description:
250G tributary signal rate
base identity: TRIBUTARY_RATE_CLASS_TYPE
description:
10G tributary signal rate
base identity: TRIBUTARY_RATE_CLASS_TYPE
description:
2.5G tributary signal rate
base identity: TRIBUTARY_RATE_CLASS_TYPE
description:
1G tributary signal rate
base identity: TRIBUTARY_RATE_CLASS_TYPE
description:
300G tributary signal rate
base identity: TRIBUTARY_RATE_CLASS_TYPE
description:
100G tributary signal rate
base identity: TRIBUTARY_RATE_CLASS_TYPE
description:
Ethernet compliance codes (PMD) supported by transceivers
description:
Ethernet compliance code: 40GBASE_SR4
base identity: ETHERNET_PMD_TYPE
description:
Ethernet compliance code: 10GBASE_LRM
base identity: ETHERNET_PMD_TYPE
description:
Ethernet compliance code: 100G_AOC
base identity: ETHERNET_PMD_TYPE
description:
Ethernet compliance code: 40GBASE_PSM4
base identity: ETHERNET_PMD_TYPE
description:
Ethernet compliance code: 10GBASE_SR
base identity: ETHERNET_PMD_TYPE
description:
Ethernet compliance code: 100GBASE_SR4
base identity: ETHERNET_PMD_TYPE
description:
Ethernet compliance code: undefined
base identity: ETHERNET_PMD_TYPE
description:
Ethernet compliance code: 100GBASE_ER4
base identity: ETHERNET_PMD_TYPE
description:
Ethernet compliance code: 100G_ACC
base identity: ETHERNET_PMD_TYPE
description:
Ethernet compliance code: 40GBASE_LR4
base identity: ETHERNET_PMD_TYPE
description:
Ethernet compliance code: 10GBASE_ZR
base identity: ETHERNET_PMD_TYPE
description:
Ethernet compliance code: 4x10GBASE_SR
base identity: ETHERNET_PMD_TYPE
description:
Ethernet compliance code: 10GBASE_ER
base identity: ETHERNET_PMD_TYPE
description:
Ethernet compliance code: 100GBASE_CR4
base identity: ETHERNET_PMD_TYPE
description:
Ethernet compliance code: 40GBASE_ER4
base identity: ETHERNET_PMD_TYPE
description:
Ethernet compliance code: 10GBASE_LR
base identity: ETHERNET_PMD_TYPE
description:
Ethernet compliance code: 100GBASE_SR10
base identity: ETHERNET_PMD_TYPE
description:
Ethernet compliance code: 4x10GBASE_LR
base identity: ETHERNET_PMD_TYPE
description:
Ethernet compliance code: 100GBASE_LR4
base identity: ETHERNET_PMD_TYPE
description:
Ethernet compliance code: 100GBASE_CLR4
base identity: ETHERNET_PMD_TYPE
description:
Ethernet compliance code: 100GBASE_CWDM4
base identity: ETHERNET_PMD_TYPE
description:
Ethernet compliance code: 100GBASE_PSM4
base identity: ETHERNET_PMD_TYPE
description:
Ethernet compliance code: 40GBASE_CR4
base identity: ETHERNET_PMD_TYPE
description:
Base identity for protocol framing used by tributary
signals.
description:
OTU 2e protocol
base identity: TRIBUTARY_PROTOCOL_TYPE
description:
ODU 2e protocol
base identity: TRIBUTARY_PROTOCOL_TYPE
description:
OC 768 protocol
base identity: TRIBUTARY_PROTOCOL_TYPE
description:
ODU Cn protocol
base identity: TRIBUTARY_PROTOCOL_TYPE
description:
10G Ethernet WAN protocol
base identity: TRIBUTARY_PROTOCOL_TYPE
description:
STM 16 protocol
base identity: TRIBUTARY_PROTOCOL_TYPE
description:
OTU Cn protocol
base identity: TRIBUTARY_PROTOCOL_TYPE
description:
1G Ethernet protocol
base identity: TRIBUTARY_PROTOCOL_TYPE
description:
100G Ethernet protocol
base identity: TRIBUTARY_PROTOCOL_TYPE
description:
OTU 3 protocol
base identity: TRIBUTARY_PROTOCOL_TYPE
description:
OTU 2 protocol
base identity: TRIBUTARY_PROTOCOL_TYPE
description:
OTU4 signal protocol (112G) for transporting
100GE signal
base identity: TRIBUTARY_PROTOCOL_TYPE
description:
STM 256 protocol
base identity: TRIBUTARY_PROTOCOL_TYPE
description:
10G Ethernet LAN protocol
base identity: TRIBUTARY_PROTOCOL_TYPE
description:
OC48 protocol
base identity: TRIBUTARY_PROTOCOL_TYPE
description:
OC 192 (9.6GB) port protocol
base identity: TRIBUTARY_PROTOCOL_TYPE
description:
40G Ethernet port protocol
base identity: TRIBUTARY_PROTOCOL_TYPE
description:
100G MLG protocol
base identity: TRIBUTARY_PROTOCOL_TYPE
description:
ODU 3 protocol
base identity: TRIBUTARY_PROTOCOL_TYPE
description:
ODU 2 protocol
base identity: TRIBUTARY_PROTOCOL_TYPE
description:
ODU 4 protocol
base identity: TRIBUTARY_PROTOCOL_TYPE
description:
STM 64 protocol
base identity: TRIBUTARY_PROTOCOL_TYPE
description:
OTU 1e protocol
base identity: TRIBUTARY_PROTOCOL_TYPE
description:
Type of protocol framing used on the logical channel or
tributary
description:
OTN protocol framing
base identity: LOGICAL_ELEMENT_PROTOCOL_TYPE
description:
Ethernet protocol framing
base identity: LOGICAL_ELEMENT_PROTOCOL_TYPE
description:
Type of optical fiber connector
description:
LC type fiber connector
base identity: FIBER_CONNECTOR_TYPE
description:
SC type fiber connector
base identity: FIBER_CONNECTOR_TYPE
description:
MPO (multi-fiber push-on/pull-off) type fiber connector
1x12 fibers
base identity: FIBER_CONNECTOR_TYPE
description:
Supported OTN application codes
description:
OTN application code: P1S1_2D2
base identity: OTN_APPLICATION_CODE
description:
OTN application code: undefined
base identity: OTN_APPLICATION_CODE
description:
OTN application code: P1L1_2D2
base identity: OTN_APPLICATION_CODE
description:
OTN application code: P1L1_2D1
base identity: OTN_APPLICATION_CODE
description:
Supported SONET/SDH application codes
description:
SONET/SDH application code: undefined
base identity: SONET_APPLICATION_CODE
description:
SONET/SDH application code: VSR2000_3R2
base identity: SONET_APPLICATION_CODE
description:
SONET/SDH application code: VSR2000_3R3
base identity: SONET_APPLICATION_CODE
description:
SONET/SDH application code: VSR2000_3R5
base identity: SONET_APPLICATION_CODE
This module contains a set of general type definitions that are used across OpenConfig models. It can be imported by modules that make use of these types.
frinx-openconfig-extensions
description:
This type is based on the timeticks type defined in
RFC 6991, but with 64-bit width. It represents the time,
modulo 2^64, in hundredths of a second between two epochs.
type: uint64
description:
This type is indicative of a password that is used within
a routing protocol which can be returned in plain text to the
NMS by the local system. Such passwords are typically stored
as encrypted strings. Since the encryption used is generally
well known, it is possible to extract the original value from
the string - and hence this format is not considered secure.
Leaves specified with this type should not be modified by
the system, and should be returned to the end-user in plain
text. This type exists to differentiate passwords, which
may be sensitive, from other string leaves. It could, for
example, be used by the NMS to censor this data when
viewed by particular users.
type: string
type: string
description:
An IEEE 32-bit floating point number. The format of this number
is of the form:
1-bit sign
8-bit exponent
24-bit fraction
The floating point value is calculated using:
(-1)**S * 2**(Exponent-127) * (1+Fraction)
type: binary
description:
This type definition is a placeholder for a standard
definition of a regular expression that can be utilised in
OpenConfig models. Further discussion is required to
consider the type of regular expressions that are to be
supported. An initial proposal is POSIX compatible.
type: string
type: string
description:
This type is indicative of a password that is used within
a routing protocol which can be returned in plain text or
encrypted form to the NMS by the local system. Only one of them
can be used, the encrypted one is recommended. There is used
'Encrypted[
type: union
type: encrypted-string
type: plain-string
description:
Integer indicating a percentage value
type: uint8
description:
A base identity for all address families
description:
The 802.3 Ethernet address family
base identity: ADDRESS_FAMILY
description:
The MPLS address family
base identity: ADDRESS_FAMILY
description:
The IPv4 address family
base identity: ADDRESS_FAMILY
description:
The IPv6 address family
base identity: ADDRESS_FAMILY
This module defines configuration and state variables for VLANs, in addition to VLAN parameters associated with interfaces
frinx-openconfig-vlan-types
frinx-openconfig-interfaces
frinx-openconfig-if-ethernet
frinx-openconfig-if-aggregate
iana-if-type
frinx-openconfig-extensions
network-topology
frinx-uniconfig-topology
This module defines configuration and state variables for VLANs, in addition to VLAN parameters associated with interfaces
frinx-openconfig-extensions
description:
VLAN interface mode (trunk or access)
type: enumeration
description:
A type definition representing a range of double-tagged/QinQ
VLAN identifiers. The format of a QinQ VLAN-ID range can be
specified in three formats. Where the range is outer VLAN IDs
the range is specified as x..y.z. In this case outer VLAN
identifiers meeting the criteria x <= outer-vlan-id <= y are
accepted iff the inner VLAN-ID is equal to y - or any inner-tag
if the wildcard is specified. Alternatively the range can be
specified as x.y..z. In this case only VLANs with an
outer-vlan-id qual to x are accepted (x may again be the
wildcard). Inner VLANs are accepted if they meet the inequality
y <= inner-vlan-id <= z.
type: union
type: string
type: string
description:
Reference to a VLAN by name or id
type: union
type: vlan-id
type: string
description:
Type definition representing a single-tagged VLAN
type: uint16
description:
Type definition representing a single double-tagged/QinQ VLAN
identifier. The format of a QinQ VLAN-ID is x.y where X is the
'outer' VLAN identifier, and y is the 'inner' VLAN identifier.
Both x and y must be valid VLAN IDs (1 <= vlan-id <= 4094)
with the exception that y may be equal to a wildcard (*). In
cases where y is set to the wildcard, this represents all inner
VLAN identifiers where the outer VLAN identifier is equal to
x
type: string
description:
Type definition representing a range of single-tagged
VLANs. A range is specified as x..y where x and y are
valid VLAN IDs (1 <= vlan-id <= 4094). The range is
assumed to be inclusive, such that any VLAN-ID matching
x <= VLAN-ID <= y falls within the range.
type: string
description:
Base identity for TPID values that can override the VLAN
ethertype value
description:
Alternate TPID value
base identity: TPID_TYPES
description:
TPID value for 802.1ad provider bridging, Q-in-Q,
or stacked VLANs
base identity: TPID_TYPES
description:
Alternate TPID value
base identity: TPID_TYPES
description:
Default TPID value for 802.1q single-tagged VLANs.
base identity: TPID_TYPES
This module contains a set of extension types to the YANG builtin types that are used across multiple OpenConfig models.
Portions of this code were derived from IETF RFC 6021. Please reproduce this note if possible.
IETF code is subject to the following copyright and license: Copyright (c) IETF Trust and the persons identified as authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust’s Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info).
frinx-openconfig-extensions
description:
A date and time, expressed in the format described in RFC3339.
That is to say:
YYYY-MM-DDTHH:MM:SSZ+-hh:mm
where YYYY is the year, MM is the month expressed as a two-digit
month (zero padding if required), DD is the day of the month,
expressed as a two digit value. T is the literal character 'T',
HH is the hour of the day expressed as a two digit number, using
the 24-hour clock, MM is the minute of the hour expressed as a
two digit number. Z is the literal character 'Z', followed by a
timezone offset expressed in hours (hh) and minutes (mm), both
expressed as two digit numbers. The time offset is specified as
a positive or negative offset to UTC using the '+' or '-'
character preceding the offset.
Optionally, fractional seconds can be expressed after the minute
of the hour as a decimal number of unspecified precision
reflecting fractions of a second.
type: string
description:
A string consisting of a hexadecimal characters.
type: string
description:
A 64-bit counter. A counter value is a monotonically increasing
value which is used to express a count of a number of
occurrences of a particular event or entity. When a counter64
reaches its maximum value, 2^64-1, it loops to zero.
Discontinuities in a counter are generally triggered only when
the counter is reset to zero, through operator or system
intervention.
type: uint64
description:
An IEEE 802 MAC address
type: string
description:
A physical layer address, expressed as a series of pairs of
hexadecimal digits.
type: string
description:
A gauge value may increase or decrease - and reflects a value
at a particular point in time. If the value of the variable
being modeled using the gauge exceeds its maximum - 2^64-1 in
this case - the gauge is set to its maximum value.
type: uint64
description:
An unsigned 32-bit integer expressed as a dotted quad. The
format is four octets written as decimal numbers separated
with a period character.
type: string
description:
A 32-bit counter. A counter value is a monotonically increasing
value which is used to express a count of a number of
occurrences of a particular event or entity. When the counter
reaches its maximum value, in this case 2^32-1, it wraps to 0.
Discontinuities in the counter are generally triggered only when
the counter is reset to zero.
type: uint32
MISSING description!
frinx-openconfig-network-instance
frinx-openconfig-routing-policy
yang-ext
network-topology
frinx-uniconfig-topology
An OpenConfig model for Open Shortest Path First (OSPF) version 3
frinx-openconfig-network-instance
yang-ext
frinx-ospfv3-types
network-topology
frinx-uniconfig-topology
Type definitions for OSPFv3
description:
Active mode of stub-router
description:
Advertise LSAs with V6-bit cleared
base identity: STUB_ROUTER_MODE
description:
Advertise LSAs with R-bit cleared
base identity: STUB_ROUTER_MODE
description:
Advertise LSAs with maximum metric
base identity: STUB_ROUTER_MODE
Set of augments needed to OpenConfig QoS models.
frinx-openconfig-qos
yang-ext
network-topology
frinx-uniconfig-topology
type: union
type: uint32
type: qos-group-range
type: string
description:
Precedence values.
type: union
type: uint8
type: string
SNMP interfaces implementation based on OpenConfig interfaces
frinx-openconfig-interfaces
frinx-event-types
network-topology
frinx-uniconfig-topology
description:
Enclosing container for snmp interface-specific
data.
frinx-device-type:
junos
frinx-supported-versions:
173
nodetype: container (rw)
description:
Configuration and operational state relating SNMP
on interfaces.
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.snmp.handler.SnmpInterfacesReader
frinx-implemented-reader-details:
INTERFACE_ID:
.*interface (?<id>\S+)\s*.*?(?<linkupDisable>notification linkupdown disable)?
SH_RUN_SNM_IFCS:
show running-config snmp-server | utility egrep "^snmp-server interface|^ notification linkupdown disable"
frinx-implemented-writer:
MISSING WRITER
frinx-device-type:
junos
frinx-supported-versions:
173
nodetype: container (rw)
description:
Configuration and operationals state relating to the
relationship between interfaces and SNMP.
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.snmp.handler.SnmpInterfacesReader
frinx-implemented-reader-details:
INTERFACE_ID:
.*interface (?<id>\S+)\s*.*?(?<linkupDisable>notification linkupdown disable)?
SH_RUN_SNM_IFCS:
show running-config snmp-server | utility egrep "^snmp-server interface|^ notification linkupdown disable"
frinx-implemented-writer:
MISSING WRITER
frinx-device-type:
junos
frinx-supported-versions:
173
frinx-implemented-reader:
io.frinx.unitopo.unit.junos.snmp.handler.SnmpInterfaceReader
nodetype: list (rw)
list keys: [interface-id]
description:
A reference to the unique identifier for the interface
being referenced by the SNMP.
nodetype: leaf (list key) (rw)
type: leafref
description:
Configuration parameters relating to an interface to
SNMP binding.
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.snmp.handler.SnmpInterfacesReader
frinx-implemented-reader-details:
INTERFACE_ID:
.*interface (?<id>\S+)\s*.*?(?<linkupDisable>notification linkupdown disable)?
SH_RUN_SNM_IFCS:
show running-config snmp-server | utility egrep "^snmp-server interface|^ notification linkupdown disable"
frinx-implemented-writer:
io.frinx.cli.unit.iosxr.snmp.handler.InterfaceConfigWriter
frinx-implemented-writer-details:
SNMP_IFC_TEMPLATE:
snmp-server interface {$config.interface_id.value}
{% if ($enable_linkup) %}?
no {% endif %}notification linkupdown disable
root
SNMP_IFC_TEMPLATE_DELETE:
no snmp-server interface {$config.interface_id.value}
frinx-device-type:
junos
frinx-supported-versions:
173
frinx-implemented-reader:
io.frinx.unitopo.unit.junos.snmp.handler.SnmpConfigReader
frinx-implemented-writer:
io.frinx.unitopo.unit.junos.snmp.handler.SnmpConfigWriter
nodetype: container (rw)
description:
A unique identifier for the interface.
nodetype: leaf (rw)
type: oc-if:interface-id
description:
Event which triggers SNMP trap.
frinx-device-type:
ios-xr
frinx-supported-versions:
4any,5any,6any
frinx-implemented-reader:
io.frinx.cli.unit.iosxr.snmp.handler.SnmpInterfacesReader
frinx-implemented-reader-details:
INTERFACE_ID:
.*interface (?<id>\S+)\s*.*?(?<linkupDisable>notification linkupdown disable)?
SH_RUN_SNM_IFCS:
show running-config snmp-server | utility egrep "^snmp-server interface|^ notification linkupdown disable"
frinx-implemented-writer:
io.frinx.cli.unit.iosxr.snmp.handler.InterfaceConfigWriter
frinx-implemented-writer-details:
SNMP_IFC_TEMPLATE:
snmp-server interface {$config.interface_id.value}
{% if ($enable_linkup) %}?
no {% endif %}notification linkupdown disable
root
SNMP_IFC_TEMPLATE_DELETE:
no snmp-server interface {$config.interface_id.value}
frinx-device-type:
junos
frinx-supported-versions:
173
frinx-implemented-reader:
MISSING READER
frinx-implemented-writer:
io.frinx.unitopo.unit.junos.snmp.handler.SnmpConfigWriter
nodetype: list (rw)
list keys: [event-name]
nodetype: leaf (list key) (rw)
type: identityref
nodetype: leaf (rw)
type: boolean
description:
Operational state parameters relating to an interface to
SNMP binding.
nodetype: container (ro)
description:
A unique identifier for the interface.
nodetype: leaf (ro)
type: oc-if:interface-id
description:
Event which triggers SNMP trap.
nodetype: list (ro)
list keys: [event-name]
nodetype: leaf (list key) (ro)
type: identityref
nodetype: leaf (ro)
type: boolean
STP interfaces implementation based on OpenConfig interfaces
frinx-openconfig-interfaces
frinx-openconfig-lldp
network-topology
frinx-uniconfig-topology
description:
Enclosing container for stp interface-specific
data.
nodetype: container (rw)
description:
Enclosing container
nodetype: container (rw)
description:
List of interfaces on which LLDP is enabled / available
frinx-device-type:
ironware
frinx-supported-versions:
any
frinx-implemented-reader:
io.frinx.cli.unit.brocade.stp.handler.StpInterfaceReader
frinx-implemented-reader-details:
ETHERNET_LINE:
interface (?<id>.+\d+)(?<spt> no spanning-tree)?
NEWLINE:
STP_INTERFACES:
show running-config interface | include interface ethernet | no spanning-tree
frinx-implemented-writer:
MISSING WRITER
nodetype: list (rw)
list keys: [name]
description:
Reference to the list key
nodetype: leaf (list key) (rw)
type: leafref
description:
Configuration data for LLDP on each interface
frinx-device-type:
ironware
frinx-supported-versions:
any
frinx-implemented-reader:
io.frinx.cli.unit.brocade.stp.handler.StpInterfaceConfigReader
frinx-implemented-writer:
io.frinx.cli.unit.brocade.stp.handler.StpInterfaceConfigWriter
frinx-implemented-writer-details:
WRITE_TEMPLATE:
configure terminal
interface {$data.name}
{% if ($delete) %}no {% endif %}spanning-tree
end
nodetype: container (rw)
description:
Reference to the LLDP Ethernet interface
nodetype: leaf (rw)
type: oc-if:base-interface-ref
description:
Enable or disable the LLDP protocol on the interface.
nodetype: leaf (rw)
type: boolean
description:
Operational state data
nodetype: container (ro)
description:
Reference to the LLDP Ethernet interface
nodetype: leaf (ro)
type: oc-if:base-interface-ref
description:
Enable or disable the LLDP protocol on the interface.
nodetype: leaf (ro)
type: boolean
description:
LLDP counters on each interface
nodetype: container (ro)
description:
The number of lldp frames received.
nodetype: leaf (ro)
type: yang:counter64
description:
The number of frames transmitted out.
nodetype: leaf (ro)
type: yang:counter64
description:
The number of LLDP frames received with errors.
nodetype: leaf (ro)
type: yang:counter64
description:
The number of LLDP frames received and discarded.
nodetype: leaf (ro)
type: yang:counter64
description:
The number of TLV frames received and discarded.
nodetype: leaf (ro)
type: yang:counter64
description:
The number of frames received with unknown TLV.
nodetype: leaf (ro)
type: yang:counter64
description:
Indicates the last time the counters were
cleared.
nodetype: leaf (ro)
type: yang:date-and-time
description:
The number of frame transmit errors on the
interface.
nodetype: leaf (ro)
type: yang:counter64
description:
Enclosing container for list of LLDP neighbors on an
interface
nodetype: container (ro)
description:
List of LLDP neighbors
nodetype: list (ro)
list keys: [id]
description:
nodetype: leaf (list key) (ro)
type: leafref
description:
Configuration data
nodetype: container (ro)
description:
Operational state data
nodetype: container (ro)
description:
The system name field shall contain an alpha-numeric string
that indicates the system's administratively assigned name.
The system name should be the system's fully qualified domain
name. If implementations support IETF RFC 3418, the sysName
object should be used for this field.
nodetype: leaf (ro)
type: string
description:
The system description field shall contain an alpha-numeric
string that is the textual description of the network entity.
The system description should include the full name and
version identification of the system's hardware type,
software operating system, and networking software. If
implementations support IETF RFC 3418, the sysDescr object
should be used for this field.
nodetype: leaf (ro)
type: string
description:
The Chassis ID is a mandatory TLV which identifies the
chassis component of the endpoint identifier associated with
the transmitting LLDP agent
nodetype: leaf (ro)
type: string
description:
This field identifies the format and source of the chassis
identifier string. It is an enumerator defined by the
LldpChassisIdSubtype object from IEEE 802.1AB MIB.
nodetype: leaf (ro)
type: oc-lldp-types:chassis-id-type
description:
System generated identifier for the neighbor on the
interface.
nodetype: leaf (ro)
type: string
description:
Age since discovery
nodetype: leaf (ro)
type: uint64
units: seconds
description:
Seconds since last update received.
nodetype: leaf (ro)
type: int64
description:
The Port ID is a mandatory TLV which identifies the port
component of the endpoint identifier associated with the
transmitting LLDP agent. If the specified port is an IEEE
802.3 Repeater port, then this TLV is optional.
nodetype: leaf (ro)
type: string
description:
This field identifies the format and source of the port
identifier string. It is an enumerator defined by the
PtopoPortIdType object from RFC2922.
nodetype: leaf (ro)
type: oc-lldp-types:port-id-type
description:
The binary string containing the actual port identifier for
the port which this LLDP PDU was transmitted. The source and
format of this field is defined by PtopoPortId from
RFC2922.
nodetype: leaf (ro)
type: string
description:
The Management Address is a mandatory TLV which identifies a
network address associated with the local LLDP agent, which
can be used to reach the agent on the port identified in the
Port ID TLV.
nodetype: leaf (ro)
type: string
description:
The enumerated value for the network address type
identified in this TLV. This enumeration is defined in the
'Assigned Numbers' RFC [RFC3232] and the
ianaAddressFamilyNumbers object.
nodetype: leaf (ro)
type: string
description:
Enclosing container for list of custom TLVs from a
neighbor
nodetype: container (ro)
description:
List of custom LLDP TLVs from a neighbor
nodetype: list (ro)
list keys: [type] [oui] [oui-subtype]
description:
Reference to type list key
nodetype: leaf (list key) (ro)
type: leafref
description:
Reference to oui list key
nodetype: leaf (list key) (ro)
type: leafref
description:
Reference to oui-subtype list key
nodetype: leaf (list key) (ro)
type: leafref
description:
Configuration data
nodetype: container (ro)
description:
Operational state data
nodetype: container (ro)
description:
The integer value identifying the type of information
contained in the value field.
nodetype: leaf (ro)
type: int32
description:
The organizationally unique identifier field shall contain
the organization's OUI as defined in Clause 9 of IEEE Std
802. The high-order octet is 0 and the low-order 3 octets
are the SMI Network Management Private Enterprise Code of
the Vendor in network byte order, as defined in the
'Assigned Numbers' RFC [RFC3232].
nodetype: leaf (ro)
type: string
description:
The organizationally defined subtype field shall contain a
unique subtype value assigned by the defining organization.
nodetype: leaf (ro)
type: string
description:
A variable-length octet-string containing the
instance-specific information for this TLV.
nodetype: leaf (ro)
type: binary
description:
Enclosing container for list of LLDP capabilities
nodetype: container (ro)
description:
List of LLDP system capabilities advertised by the
neighbor
nodetype: list (ro)
list keys: [name]
description:
Reference to capabilities list key
nodetype: leaf (list key) (ro)
type: leafref
description:
Configuration data for LLDP capabilities
nodetype: container (ro)
description:
Operational state data for LLDP capabilities
nodetype: container (ro)
description:
Name of the system capability advertised by the neighbor.
Capabilities are represented in a bitmap that defines the
primary functions of the system. The capabilities are
defined in IEEE 802.1AB.
nodetype: leaf (ro)
type: identityref
description:
Indicates whether the corresponding system capability is
enabled on the neighbor.
nodetype: leaf (ro)
type: boolean
MISSING description!
network-topology
yang-ext