About: http://openconfig.net/yang/interfaces#description

Facets (new session)
Description
Metadata
Settings
- owl:sameAs
- Inference Rule:

About: http://openconfig.net/yang/interfaces#description Goto Sponge NotDistinct Permalink

An Entity of Type : owl:DatatypeProperty, within Data Space : yang.eurecom.fr associated with source document(s)

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.

Attributes	Values
rdf:type	FunctionalProperty DatatypeProperty
rdfs:domain	http://openconfig.net/yang/interfaces#config http://openconfig.net/yang/interfaces#interface_common_config http://openconfig.net/yang/interfaces#interface_phys_config http://openconfig.net/yang/interfaces#state http://openconfig.net/yang/interfaces#subinterfaces_config
rdfs:range	xsd:string
rdfs:comment	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. Reference : RFC 2863: The Interfaces Group MIB - ifAlias

Faceted Search & Find service v1.16.120 as of Nov 11 2024

Alternative Linked Data Documents: ODE Content Formats:

RDF

ODATA

Microdata

About

OpenLink Virtuoso version 07.20.3240 as of Nov 11 2024, on Linux (x86_64-ubuntu_focal-linux-gnu), Single-Server Edition (252 GB total memory, 476 MB memory in use)
Data on this page belongs to its respective rights holders.
Virtuoso Faceted Browser Copyright © 2009-2025 OpenLink Software