JN0-106 ยท Interfaces and system services
NTP, SNMP and syslog
Configuring time synchronization, SNMP community and traps basics, and system logging facilities, severity levels and destinations.
Key points
- NTP: set system ntp server <address> configures a time source.
- set date ntp <server>: operational, syncs the clock once, no commit.
- SNMP community: defines access (read-only by default), can be limited by client lists.
- trap-groups with targets send notifications.
- Syslog: under [edit system syslog], each destination (console, file, host, user) takes facility and severity pairs; a severity logs that level and everything more serious.
Practice questions
Under which configuration hierarchy are system log destinations defined?
- [edit system logging]
- [edit services syslog]
- [edit routing-options syslog]
- [edit system syslog]
Show answer
Answer: D. [edit system syslog]
Syslog destinations such as file, host, console and user are configured under system syslog.
Which statements are correct?
- A trap-group can list targets that receive notifications
- An SNMP community is read-write by default
- set date ntp needs a commit to take effect
- An SNMP community is read-only unless configured otherwise
- NTP servers are configured under [edit system ntp]
Show answer
Answer: A. A trap-group can list targets that receive notifications, D. An SNMP community is read-only unless configured otherwise, E. NTP servers are configured under [edit system ntp]
Read-only is the default community authorization, NTP lives under system ntp, and trap-groups list targets. set date ntp is an operational command that acts immediately.
True or false: a syslog severity of warning also logs error, critical, alert and emergency messages.
Show answer
Answer: True
True. A severity covers that level and everything more severe. People often assume it matches only the exact level.
Practice 8 questions on this topic in Bitzu
Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.
