Juniper CLI Basics

Start the CLI
% cli <- Equivalent to enable command of cisco devices.

Go to configuration mode
> configure

Set a new root password
# set system root-authentication plain-text-password
Note: Juniper always require local root authentication.

Save the new configuration
# commit

Exit to operational mode
# exit configuration-mode

Reload
> request system reboot

IOS vs Junos CLI modes
IOS has three main CLI mode
1. User
2. Exec mode
3. Configuration mode and its hierarchy (sub-config, interface, etc)

Junos has unix shell and two main CLI modes.
1. Operation mode
2. Configuration mode

Juniper System Services

#set system services?

NTP – Network Time Protocol

Deals with service of time
Stratum – mathematically measurement your accuracy of your clock
Up to 15 synchronization(sync 1 – 2 – 3 )  if more than 15 no one can sync to us.
Steps > 128ms > sync
>1,000 seconds X
Boot server – at boot  1,000
Server – normal sync 128

In other vendors you will see Ntp Master command serve the time. In junos no master. Client only. Ability to make md5 secure time services.

SNMP – Simple Network Management Protocol

#set system services ntp ?
Server – with authority realtime
Peer – no authority

#run ping time.nist.gov
#run ping inet4 time.nist.gov
#set system services ntp server time.nist.gov
Verify: #run show system uptime
#run set date ?
# run set date 198.60.73.8
Verify: #run show system uptime
#show | compare
# run show ntp status
#set snmp community CBTnuggets read-only clients 10.10.100.0/23
#set snmp trap-group nuggetNOC target 10.10.100.0

SYSLOG
#set system syslog (Host out from ip address Syslog server)
(Console Via console cable)
(File send and save)
#set system syslog console any emergency
#set system syslog host 10.10.100.101 any notice
#set system syslog file messages any any
# set syslog file auth-info authorization info
#set system syslog file interactive-commands any
#set syslog file config-changes change-log info

-Every single entry will have Time stamp is important – so we need to configure NTP
-Host
-Process ID
-Message code

Juniper Network Configuration

% – (Main) Type CLI to start
> – (User Mode)
#- (Configure Mode)
>Configure

#set system ? (list we have)

Changing Password

#set system r ?

#set system root-authentication ?

#set system root-authentication plain-text-password

( New password: ********  It will ask you to a new password)

            Verify #show system root authentication

            Encrypted-Password automatically

Changing Host-name

#set system host-name (Hostname)

Verify

#show | compare

 – (Current)

+ (added of changed)

Setting time-zone

#set system time-zone ?

  (It will give us a list of location)

#set system time-zone America/New_york

Setting Management

#set system ?

#set system services ssh

Verify : #show | Compare

Adding IP on Management Interface (out of bound management)

#set interfaces me0 (verify the interface)

#set interface me0 unit family inet address 1.1.1.1/24 (that will give you out of bound management)

Static Routing

#set routing-options static route 0.0.0.0/0 next-hop 1.1.1.254 retain no-readvertised (only for management. It has limitation)

Verify : #show | Compare

#commit

#exit

> –  Show interfaces me0

Juniper Network Overview

Robust, Modular and Scalable

• Junos OS functionality is compartmentalized into multiple software processes.
• The Junos kernel is based on FreeBSD UNIX operationg system, which is an open-source software system

Single Source Code Base

• All platforms running the Junos OS use the same software source code base within their platform-specific images.

Separate Control and Forwarding Planes

• Routing Engine (RE) is the brain of the platform; It is responsible for performing protocol updates and system management.
• The RE is based on an x86 or PowerPC architecture, depending on the specific platform running the Junos OS.
• RE maintains: Routing tables, Bridging table and Primary forward table and connects to the packet forwarding engine (PFE) through internal link.

Maintains Routing Engine Intelligence

• The RE handles all protocol processes in addition to other software processes that control the device’s interface, the chassis components, system management, and user access to the device.

Control and Monitors Chassis

• The RE Provide the CLI in additional to the J-Web Gui.

Manages Packet Forwarding Engine

• The RE controls the PFE by providing accurate, up-to-date Layer 2 and Layer 3 forwarding tables and by downloading microcode and managing software processes that resides in the PFE’s microcode.

Keyboard Shortcut