system-config

AsterNOS YANG Model for Aster NOS system config.

Include DNS server setting.

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