Configuring Junos OS on the SRX4200
SRX4200 Services Gateway Software Configuration Overview
The services gateway is shipped with Junos OS preinstalled and ready to be configured when the services gateway is powered on. If you are setting up the services gateway for the first time, use the CLI to perform the initial configuration.
SRX4200 Services Gateway Factory-Default Settings
Your services gateway comes configured with a factory-default configuration.
Table 1: Factory-Default Settings - Interfaces
Table 2: Factory-Default Settings - Services
NETCONF over SSH
Viewing Factory-Default Settings
To view the factory-default settings on your services gateway:
- Log in as the root user and provide your credentials.
- View the list of default config files:
user@host>file list /etc/config
- View the required default config file.
user@host> file show /etc/config/<config file name>
When you commit changes to the configuration, a new configuration file is created, which becomes the active configuration. If the current active configuration fails, you can use the load factory-default command to revert to the factory-default configuration.
Configuring the SRX4200 Services Gateway
This procedure explains how you can create an initial configuration using CLI commands to connect the services gateway to the network.
Before you can use J-Web to configure your services gateway, you must access the CLI to configure the root authentication.
- Connect the RJ-45 end of the DB9-to-RJ-45 cable into the CONSOLE port on your services gateway.
- Connect the other end of the cable to the serial port on the management device.
- Log in to the services gateway as root. When the services gateway is powered on with the factory-default configuration, you do not need to enter a password.
- At the (%) prompt, type cli to start the CLI
and press Enter. The prompt changes to an angle bracket (>) when you enter CLI operational mode.
- At the (>) prompt, type configure and press
Enter. The prompt changes from > to # when
you enter configuration mode.
Entering configuration mode
- Set the root authentication password by entering a cleartext
password, an encrypted password, or an SSH public key string (DSA
root# set system root-authentication plain-text-password
New password: password
Retype new password: password
- Configure the route for the management interface (optional,
required only if you do not connect the MGMT port directly to the
root# set routing-options static route <destination prefix> next-hop <gateway>
- Commit the configuration to activate it on the services
- Connect the MGMT port on the device to the Ethernet port on the management device using an RJ-45 cable.
an IP address on the 192.168.1.0/24 subnetwork for the management
device. By default, the management interface is configured with the
192.168.1.1/24 IP address. If you need to change the IP address, perform
the following steps or else proceed to 11.
Delete the default management interface IP address:
root# delete interface fxp0 unit 0 family inet address 192.168.1.1/24
Configure a new IP address for the management interface:
root# set interfaces fxp0 unit 0 family inet address address/prefix-length
Commit the configuration changes.
Configure an IP address for the management device. Ensure that the IP address is on the same subnetwork as the management interface (fxp0).
a Web browser from the management device and access the services gateway
using the URL https://192.168.1.1.
If you changed the management interface IP address in 10, then use the URL https://<management IP address> to access the services gateway.
As the system-generated certificate is not trusted by default, an alert is displayed. You can ignore this alert and proceed to access the services gateway.
The J-Web login page is displayed. This indicates that you have successfully completed the initial configuration and that your services gateway is ready for use.
To access the J-Web interface, your management device requires one of the following supported browsers:
Microsoft Internet Explorer version 9.0 or 10.0
Mozilla Firefox version 38 (or later)
- Log in as root and proceed with configuring the settings based on your requirements.