To recover the root password, perform the following steps:
1. Power off your switch by unplugging the power cord or turning off the power at the wall switch.
2. Insert one end of the Ethernet cable into the serial port on the management device and connect the other end to the console port at the back of the switch.
3. On the management device, start your asynchronous terminal emulation application (such as Microsoft Windows Hyperterminal) and select the appropriate COM port to use (for example, COM1).
4. Configure port settings as follows:
5. Power on your switch by plugging in the power cord or turning on the power at the wall switch.
6. When the following prompt appears, press the Spacebar to access the switch's bootstrap loader command prompt:
Hit [Enter] to boot immediately, or space bar for command prompt.
Booting [kernel] in 1 second...
7. At the following prompt, type boot -s to start up the system in single-user mode:
loader> boot -s
8. At the following prompt, type recovery to start the root password recovery procedure:
Enter the full pathname of the shell or recovery for root password recovery or RETURN for /bin/sh: recovery.
A series of messages describe consistency checks, mounting of filesystems, and initialization and checkout of management services. Then the Command Line Interface (CLI) prompt appears.
9. Enter configuration mode in the CLI:
user@switch> configure
10. Set the root password, for example:
user@switch# set system root-authentication plain-text-password
11. At the following prompt, enter the new root password, for example:
New password: juniper1
Re-type the new password:
12. At the second prompt, re-enter the new root password.
13. If you have finished configuring the network, commit the configuration.
root@switch#
commit
commit complete
14. Exit configuration mode in the CLI.
root@switch# exit
15. Exit operational mode in the CLI.
root@switch> exit
16. At the prompt, enter y to reboot the switch.
Reboot the system? [y/n] y
Junos OS automatically creates and maintains several routing tables. Each routing table is used for a specific purpose. In addition to these automatically created routing tables, you can create your own routing tables.
Each routing table populates a portion of the forwarding table. Thus, the forwarding table is partitioned based on routing tables. This allows for specific forwarding behavior for each routing table. For example, for VPNs, each VPN-based routing table has its own VPN-specific partition in the forwarding table. It is common for the routing software to maintain unicast routes and multicast routes in different routing tables. The policy considerations that would lead to create separate routing tables to manage the propagation of routing information.
Creating routing tables is optional. If you do not create any, Junos OS uses its default routing tables, which are as follows:
inet.0 and inet.2 are the default routing table used in the Junos devices.
The inet.0 routing table is the table used to store IPv4 unicast routes. The router interfaces and all routing protocols place information into this table by default.
Inet.2 table stores unicast routes that are used for multicast reverse-path-forwarding (RPF) lookup.
The default next-hop entry that is placed into a forwarding table for each valid route is 1.
The mpls.0 table is not actually a routing table but is instead a switching table. MPLS label values are stored in this table. We can view the mpls table using 'show route table mpls.0' command.
There are nine JUNOS software routing table. The JUNOS software provides multiple routing tables that are used to store routes for our network. Each table is represented within the output of the 'show route' command.
Preference value defines the believability of the individual protocol. All the routing protocols has its individual preference value. The lesser the preference value, the more it is believed in the routing table.
