[MUSIC] Welcome to the initial configuration tasks module. By the end of this module, you should be able to explain how to list and perform initial configuration tasks. Refer to your platform specific documentation and follow the safety guidelines when connecting power and powering on your device, running Junos OS. If a Junos OS devices powered on, and power to that system is interrupted, the device automatically powers on when the power is restored. In other words, no manual intervention is required for the system to reboot. Junos OS is a multitasking environment. To ensure file system integrity, you should always gracefully shut down platforms running Junos OS. Although unlikely, failure to gracefully shut down the system could possibly leave it unable to boot. As shown in this example, you can use the request system halt command to gracefully shut down Junos OS. This command provides options that enable you to schedule the shutdown in a specified number of minutes, or at an exact time. To specify the media from which the next boot up operation uses, and to log a message to the console in to the messages file. For Junos devices that offer redundant routing engines, you can halt both routing engines simultaneously using the request system, halt both routing engines command. For EX series switches participating in a virtual chassis, where multiple switches function as a single virtual device. You can halt all participating members simultaneously with the request system, halt all members command. All platforms running Junos OS are shipped with a factory default configuration. All factory default configurations allow access using the root account. The root account does not include a password by default. Setting a root password is required before activating any changes to the configuration file. All factory default configurations also includes system logging, which tracks system events and writes those events to predefined log files, such as the messages file. Factory default configurations can vary from one platform family to another, or even between the different models within the same platform family. All platforms running Junos OS are designed for a specific roles within a network environment. And their factory default configurations are created with those specific roles in mind. One example is the EX series switches that are designed to operate as layer two switches right out of the box, to meet this default operational requirement. The associated factory default configurations have all interfaces configured for layer two operations. And also include protocol configuration, such as the Rapid Spanning Tree Protocol or RSTP and the Link Layer Discovery Protocol, or LLDP, commonly used on switches. Other platforms do not have these same default operational requirements. And so do not include those configuration parameters in their factory default configurations. Under certain conditions, you might want to return a device running Junos OS to its factory default configuration. You can overwrite the candidate configuration while in configuration mode using the load factory-default command. Junos OS does not permit you to save the configuration until you configure root authentication information. Do not forget to issue a commit command to activate your changes. When you receive a device running Junos OS from the factory. Junos OS is preinstalled once you power on the device, it is ready to be configured. When the initial configuration is performed, the route authentication must be included. In addition to route authentication, we also recommend that you configure a few additional items such as host name. system time, system services for remote access like telnet or SSH, and a management interface and a static route for management traffic. Junos OS enforces password restrictions. All passwords are required to be no less than six characters and must include a change of case, digits or punctuation. Remember when you receive a platform running Junos OS from the factory, the root password is not set. To log into the CLI for the first time you must log in through the console port using the root user name with no password. When configured, the console login displays the host name of the device. When no host name is configured or if a factory default configuration is loaded, the word amnesiac is displayed in place of the host name. When you log in as the root user, you are placed at the UNIX shell. You must start the CLI by typing the CLI command. When you exit the CLI, you return to the UNIX shell. For security reasons make sure you also log out of the shell using the exit command. After starting the CLI you enter operational mode, you can make changes to the configuration only in the configuration mode. Enter configuration mode by entering configure at the operational mode prompt. The example shows how to use the CLI to configure the host name and the root password. As displayed a check is made when the root password is entered to ensure that it has been entered correctly. In the event that the entered passwords do not match, an error is generated. The change is not accepted and the password needs to be re entered. The example uses the plaintext authentication option. Unlike the software from some vendors, Junos OS never actually displays the password in its plain text format, but rather encrypts actually hashes the password for you. You can see the encrypted password by viewing the relevant configuration part. Because you cannot retrieve the passwords by looking at the configuration file, you should keep the configured passwords in a secure location. If you do forget the password and cannot log in, you can perform the Junos OS root password recovery process. The example shows how to use the CLI to enable SSH access to a device running Junos OS. You can enable the Telnet, FTP or web management services similarly. When connecting to a device running Junos OS using one of these access protocols, use the same user logins defined under the edit system log in hierarchy. This example shows how to use the CLI to configure the time settings. You can configure the current date and time information along with the proper time zone for the device. The default time zone on Junos OS devices is UTC or GMT. When you define the local time on a Junos OS device, you must account for the time difference between the defined time zone and the default time zone. Once the time zone is changed and committed, the local time is adjusted accordingly to account for the difference. If you do not want to make the necessary adjustments, you can simply set the systems time after the defined time zone parameter has been committed. Instead of setting the local time on each network device in your network, consider implementing Network Time Protocol or NTP using the basic NTP configuration as shown in this example. This example shows how to use the CLI to configure a management interface and a static route for management traffic. Note that it is highly discouraged to use a default static route for management traffic, you should be as specific as possible. You can also use the no-readvertised option for the static route used for management traffic. The no-readvertised option marks the route ineligible for readvertisement through routing policy. Note that the static route defined for management traffic or any other traffic is only available when the system's routing protocol process or RPD is running. When Junos OS devices boot, the RPD is not running. Therefore, the system has no static or default routes. To allow the device to boot and to ensure that it is reachable over the network during RPD failure, you can figure a backup router. Which is a router or gateway device that is directly connected to the local system that is on the same subnet. To configure a backup router running IPv4, include the backup router statement at the edit system hierarchy level. In this sample configuration hosts on the 10.0.1.0/24 subnets are reachable through the backup router. If the destination statement is omitted, then all hosts are reachable through the backup router. To eliminate the risk of installing a default route in the forwarding table. You should always include the destination option, specifying an address that is reachable through the backup router. Specify the address in the format network or mask length, as shown in the example, so that the entire network is reachable through the backup router. When the routing protocols start, the address of the backup router is removed from the local routing and forwarding tables. To have the address remain in these tables configure a static route for the desired destination prefix with the backup router as the next top and the retain option as shown. Once you complete your initial configuration, use the commit command to apply your changes. You can include the and-quit option as shown to return to operational mode. In the example, you see that once the configuration changes are activated and the user returns to operational mode, the configured host name is displayed. This displayed host name is a sure sign that the active configuration has changed. [MUSIC]
