As most of us start learning Juniper after getting bit expert with Cisco IOS, and always try to find some relation between two, at least me always does, it gives me couple of advantage knowing that particular thing can be done in both and easy to remember. As this post is just a Intro to Junos OS so I will not get deeper just keep it simple.
Like Cisco IOS when we access it through Console or telnet it gives us the prompt with > sign which means user mode where we run some Show commands and than in order to proceed more verification and configuration command we have to get in to user privilege mode and than in global.
Junos OS start with something called shell mode which looks like unix shell command line. And you have to type cli to get into Junos CLI.
root@% cli
root>
And when you get into Junos CLI prompt end with > which means its is operational mode. In this mode you cannot do configuration but you can perform some verification tasks. Unlike Cisco, Juniper provide help from any mode, with help along with command you looking to know more.
root> ?
Possible completions:
clear Clear information in the system
configure Manipulate software configuration information
file Perform file operations
help Provide help information
monitor Show real-time debugging information
mtrace Trace multicast path from source to receiver
op Invoke an operation script
ping Ping remote target
quit Exit the management session
request Make system-level requests
restart Restart software process
set Set CLI properties, date/time, craft interface message
show Show system information
ssh Start secure shell on another host
start Start shell
telnet Telnet to another host
test Perform diagnostic debugging
traceroute Trace route to remote ho
Possible completions:
clear Clear information in the system
configure Manipulate software configuration information
file Perform file operations
help Provide help information
monitor Show real-time debugging information
mtrace Trace multicast path from source to receiver
op Invoke an operation script
ping Ping remote target
quit Exit the management session
request Make system-level requests
restart Restart software process
set Set CLI properties, date/time, craft interface message
show Show system information
ssh Start secure shell on another host
start Start shell
telnet Telnet to another host
test Perform diagnostic debugging
traceroute Trace route to remote ho
root> help topic ospf route-type-community
Configuring OSPF Domain IDs for VPNs
For most OSPF or OSPFv3 configurations involving Layer 3 VPNs, you do not need to configure an OSPF domain ID. However, for a Layer 3 VPN connecting multiple OSPF or OSPFv3 domains, configuring domain IDs can help you control LSA translation (for Type 3 and Type 5 LSAs) between the OSPF domains and back-door paths. The default domain ID is 0.0.0.0. Each VPN routing table in a PE router associated with an OSPF or OSPFv3 instance is configured with the same OSPF domain ID.
In order to perform some configuration you have to get into configuration mode by typing configure.
root> configure
Entering configuration mode
[edit]
root#
Entering configuration mode
[edit]
root#
# mean you are in configuration mode. From here you can go further configure particular setting. For that you dig in to the particular setting and than configure or sitting at top level of the hierarchy and give full path in the command line.
Lets say you want to set new user name one way doing is to execute command from the top level.
root# set system login user lab1 class operator authentication
[edit]
Below another user account is created but first getting into to system login and than creating user.
[edit]
root# edit system login
[edit system login]
root# set user lab2 class operator
[edit system login]
root# set user lab2 authentication plain-text-password
[edit]
Below another user account is created but first getting into to system login and than creating user.
[edit]
root# edit system login
[edit system login]
root# set user lab2 class operator
[edit system login]
root# set user lab2 authentication plain-text-password
This is how Junos has it OS operating in all of it platforms, in hierarchical order.