close

keyboard_arrow_left

Table of Contents Expand all

play_arrow Fast Track: Initial Installation
- Fast Track to Rack Installation and Power
- Onboard, Configure, and Monitor MX304
play_arrow Overview
play_arrow Site Planning, Preparation, and Specifications
play_arrow Initial Installation and Configuration
play_arrow Maintaining Components
play_arrow Contacting Customer Support and Returning the Chassis or Components
- Contact Customer Support and Returning the Chassis or Components
play_arrow Safety and Compliance Information

list Table of Contents

English

keyboard_arrow_right

Perform Initial Configuration on the MX304 Router

date_range 22-Nov-22

arrow_backward

arrow_forward

The router is shipped with the Junos operating system (OS) preinstalled and ready to be configured when the router is powered on. Two 16-MB internal NAND Flash memory devices are located on the baseboard for BIOS storage. The USB storage device can be inserted into the slot in the Routing Engine panel faceplate. The system also supports two M.2-based solid-state drive (SSD) slots. These two SSD devices act as the primary boot devices (sda and sdb). When the router boots, it first attempts to start the Junos OS image on the USB Flash memory drive if it detects one. If a USB flash drive is not inserted into the router, or the attempt otherwise fails, the router next tries the primary boot device, and then tries the secondary boot device.

The MX304 router ships with factory-default settings that enable some zero touch provisioning (ZTP) functions. These settings load as soon as you power on the switch. In our case we configure the router manually, so we remove the ZTP settings as part of our initial configuration.

When ZTP is not used you must perform the initial configuration of an MX304 router through the console port (CON) using the Junos OS command-line interface (CLI). If your MX304 has dual Routing-Engines, you should perform these steps on each Routing-Engine, being sure to specify a unique management IP address for the management interface on each Routing-Engine. See Configuring Junos OS for the First Time on a Device with Dual Routing Engines for information on how to use configuration groups to share a single configuration file between both Routing-Engines.

Have the following information ready before you begin the initial configuration:

The router's host and domain name
IP address and subnet mask for the management and loopback interfaces
IP address of a default gateway for the management network
IP address of a DNS server
The root user's password

This procedure connects the router to the network but does not enable it to forward traffic. For complete information about enabling the router to forward traffic, including examples, see the Junos OS configuration guides.

To configure the software:

Verify that the router is powered on.
Note:
You may see messages on the console relating to ZTP and DHCP. These messages stop once your remove the ZTP statements from the default configuration.
Configure your serial port for 9600 bps/8-N-1, and attach the cable to the CON port of the desired Routing-Engine. Log in as the “root” user. No password is needed.
```
FreeBSD/amd64 (Amnesiac) (ttyu0)

login: root
root@:~ # 
```
Start the CLI.
```
root@:~ # cli
root>
```
Enter configuration mode.
```
cli> configure
[edit]
root#
```

Set the root authentication password by entering either a plain text password, an encrypted password, or an SSH public key string (ECDSA, ED25519 or RSA).

content_copy zoom_out_map
[edit]
root# set system root-authentication plain-text-password
New password: password 
Retype new password: password 

content_copy zoom_out_map
[edit]
root# set system root-authentication encrypted-password encrypted-password

content_copy zoom_out_map
[edit]
root# set system root-authentication (ssh-ecdsa | ssh-ed25519 | ssh-rsa) public-key

Remove factory default configuration statements that relate to ZTP. After you commit these initial changes the ZTP process is stopped and the related console messages are no longer displayed.
```
[edit]
root@# delete system commit
root@# delete chassis auto-image-upgrade
root@# delete interfaces fxp0
```
Configure the IP address and prefix length for the router’s management Ethernet interface (fxp0). You also configure an IPv4 address on the loopback interface in this step. Having a routible IP address on the loopback interface is a best practice and is generally needed later, when routing protocols are configured.
```
[edit]
root# set interfaces fxp0 unit 0 family inet address address/prefix-length
root# set interfaces lo0 unit 0 family inet address address/32
```
Perform an initial commit to activate the modified configuration.
```
[edit]
root# commit
commit complete
[edit]
root# 
```
Configure the router's host name. If the name includes spaces, enclose the name in quotation marks (“ ”).
```
[edit]
root# set system host-name host-name
```
Configure the router’s domain name.
```
[edit]
root# set system domain-name domain-name
```
Configure the IP address of a DNS server.
```
[edit]
root@# set system name-server address 
```
Configure one or more static routes to remote subnets that have access to the management subnet. Without static routing, access to the management port is limited to devices attached to the management subnet. Static routing is needed to access the management interface from devices attached to remote subnets. For more information about static routes, see Configure Static Routes.
In our example we define a single default static route to provide management network reachability to all possible remote destinations.
```
[edit]
root# set routing-options static route 0.0.0.0/0 next-hop destination-IP retain no-readvertise
```
Configure the IP address of a backup router. The backup router is only used while the routing protocol is not running. The primary use of the backup router is to provide routing capability for the management port on the backup Routing-Engine. This is because the backup Routing-Engine does not run the routing protocol daemon (rpd).
In most cases the backup router is the same IP next hop as used for the management network's static routes. We again use a default route to provide the back up Routing-Engine with reachability for all possible remote destinations.
```
[edit]
root# set system backup-router address 
root# set system backup-router destination 0.0.0.0/0
```
Configure remote access for the root user over ssh. By default the root user is only able to log-in via the console port. The root-login allowstatement permits remote log-in for the root user.
```
[edit]
root# set system services ssh root-login allow
```

(Optional) Display the configuration to verify it's correct.

content_copy zoom_out_map
[edit]
root# show
system {
    host-name host-name;
    root-authentication {
        authentication-method (encripted-password | public-key);
    }
     services {
        ssh {
            root-login allow;
        }
    }
    domain-name domain-name;
    backup-router address destination 0.0.0.0/0;
    
    name-server {
        address;
    }
}
interfaces {
    fxp0 {
        unit 0 {
            family inet {
                address address/prefix-length;
            }
        }
    }
lo0 {
        unit 0 {
            family inet {
                address address/32;
            }
        }
    }
}
routing-options {
    static {
        route 0.0.0.0/0 next-hop destination-IP;
    }                                   
}

Commit the configuration to activate it on the router.
```
[edit]
root# commit
commit complete

[edit]
root@host-name# 
```
When you've finished configuring the router, exit configuration mode.
```
[edit]
root@host-name# exit
Exiting configuration mode

root@host-name> 
```
Congratulations. The initial configuration is complete. Remember to also configure the backup Routing Engine if your MX304 is equipped with redundant control planes. At this point you should be able to remotely access both of the Routing-Engines as the root user with ssh.

arrow_backward PREVIOUS Register Products—Mandatory to Validate SLAs

NEXT arrow_forward Routine Maintenance Procedures for MX304 Routers

MX304 Universal Routing Platform Hardware Guide

Perform Initial Configuration on the MX304 Router

Stay in touch

Helped me install or use the product
Accelerated my deployment

Discuss the product with a co-worker
Make a purchase inquiry

MX304 Universal Routing Platform Hardware Guide

Perform Initial Configuration on the MX304 Router

Related Documentation

Stay in touch