system-config

asternos system config module description asternos yang model for aster nos system config include dns server setting yang tree diagram module asternos system config + rw system config + rw dns resolver \| + rw server \[address] \| + rw address inet\ ip address + rw hostname? string + rw clock \| + rw timezone? string \| + rw datetime? yang\ date and time + rw ssh max session? uint8 + rw telnet max session? uint8 rpcs + x show license \| + ro output \| + ro data? \<anydata> + x update license + x show supported timezones + ro output + ro data? \<anydata> resources resource list path access /system config read write /system config/dns resolver read write /system config/dns resolver/server read write /system config/dns resolver/server/address read write /system config/hostname read write /system config/clock read write /system config/clock/timezone read write /system config/clock/datetime read write /system config/ssh max session read write /system config/telnet max session read write detailed nodes /system config path /system config node type container description system level configurations access read write /system config/dns resolver path /system config/dns resolver node type container description configuration of the dns resolver access read write /system config/dns resolver/server path /system config/dns resolver/server node type list description list of the dns servers that the resolver should query access read write /system config/dns resolver/server/address path /system config/dns resolver/server/address node type leaf description the address of the dns server access read write data type constraints multiple constraints the ipv6 address type represents an ipv6 address in full, mixed, shortened, and shortened mixed notation the ipv6 address may include a zone index, separated by a % sign if a system uses zone names that are not represented in utf 8, then an implementation needs to use some mechanism to transform the local name into utf 8 the definition of such a mechanism is outside the scope of this document the zone index is used to disambiguate identical address values for link local addresses, the zone index will typically be the interface index number or the name of an interface if the zone index is not present, the default zone of the device will be used the canonical format of ipv6 addresses uses the textual representation defined in section 4 of rfc 5952 the canonical format for the zone index is the numerical format as described in section 11 2 of rfc 4007 the ipv4 address type represents an ipv4 address in dotted quad notation the ipv4 address may include a zone index, separated by a % sign if a system uses zone names that are not represented in utf 8, then an implementation needs to use some mechanism to transform the local name into utf 8 the definition of such a mechanism is outside the scope of this document the zone index is used to disambiguate identical address values for link local addresses, the zone index will typically be the interface index number or the name of an interface if the zone index is not present, the default zone of the device will be used the canonical format for the zone index is the numerical format mandatory yes /system config/hostname path /system config/hostname node type leaf description this system's network name access read write data type /system config/clock path /system config/clock node type container description system datetime and timezone settings access read write /system config/clock/timezone path /system config/clock/timezone node type leaf description timezone in iana format, e g , 'asia/shanghai', 'utc', 'america/new york' access read write data type /system config/clock/datetime path /system config/clock/datetime node type leaf description manual system time setting (used when ntp is disabled) access read write data type constraints the date and time type is a profile of the iso 8601 standard for representation of dates and times using the gregorian calendar the profile is defined by the date time production in section 5 6 of rfc 3339 the date and time type is compatible with the datetime xml schema type with the following notable exceptions (a) the date and time type does not allow negative years (b) the date and time time offset 00 00 indicates an unknown time zone (see rfc 3339) while 00 00 and +00 00 and z all represent the same time zone in datetime (c) the canonical format (see below) of data and time values differs from the canonical format used by the datetime xml schema type, which requires all times to be in utc using the time offset 'z' this type is not equivalent to the dateandtime textual convention of the smiv2 since rfc 3339 uses a different separator between full date and full time and provides higher resolution of time secfrac the canonical format for date and time values with a known time zone uses a numeric time zone offset that is calculated using the device's configured known offset to utc time a change of the device's offset to utc time will cause date and time values to change accordingly such changes might happen periodically in case a server follows automatically daylight saving time (dst) time zone offset changes the canonical format for date and time values with an unknown time zone (usually referring to the notion of local time) uses the time offset 00 00 /system config/ssh max session path /system config/ssh max session node type leaf description ssh max session of the system access read write data type constraints valid range 1 to 100 /system config/telnet max session path /system config/telnet max session node type leaf description ssh max session of the system access read write data type constraints valid range 1 to 100 rpcs show license path access /show license/output read write /show license/output/data read write /show license/output path /show license/output node type container description no description available access read write /show license/output/data path /show license/output/data node type anydata description license info access read write update license no nodes available in this section show supported timezones path access /show supported timezones/output read write /show supported timezones/output/data read write /show supported timezones/output path /show supported timezones/output node type container description no description available access read write /show supported timezones/output/data path /show supported timezones/output/data node type anydata description timezones info access read write