- play_arrow Fast Track: Initial Installation
- play_arrow System Overview and Specifications
- play_arrow Site Planning and Preparation
- play_arrow Maintain Components
- play_arrow Troubleshoot Hardware
- play_arrow Contact Customer Support and Return the Chassis or Components
- play_arrow Safety and Compliance Information
Configure Junos OS on the EX4400
Connect and Configure an EX4400 Switch by Using the CLI
There are two ways to connect and configure an EX4400 switch: one method is through the console by using the CLI and the other is by using the J-Web interface.
Starting in Junos OS Release 22.3R1, J-Web supports EX4400 switches.
This topic describes the CLI procedure.
Before you connect and configure an EX4400, set the following parameter values on the console server or PC:
Baud Rate—9600
Data—8
Flow Control—None
Parity—None
Stop Bits—1
DCD State—Disregard
Ensure that you have the following parts and tools available:
An Ethernet cable with an RJ-45 connector attached—not provided
An RJ-45 to DB-9 serial port adapter—not provided
A laptop or PC, with a serial port—not provided
Have the following information available before you configure custom settings for the switch:
Root password
IP address of the default gateway
IP address of the management port
IP address of a DNS server
(Optional) Hostname
(Optional) IP address of a backup router
(Optional) SNMP read community, location, and contact to configure SNMP parameters
(Optional) Static routes to remote subnets with access to the management port
(Optional) Static routes to remote prefixes with access to the management port
We ship the EX4400 switch with Junos OS preinstalled and ready to be configured when the switch is powered on. You must perform the initial configuration of the EX4400 through the console port (labeled CON) on the rear panel of the switch by using the command-line interface (CLI).
This procedure describes how to perform the initial configuration on the switch and to connect it to the network. For the complete information about enabling the switch to forward traffic, including examples, see the Junos OS configuration guides.
To perform the initial configuration on the switch and to connect it to the network:
You can now log in by using the CLI and continue configuring the switch.
To connect and configure an EX4400 switch by using the J-Web interface, see Connecting and Configuring an EX Series Switch (J-Web Procedure).
EX4400 Default Configuration
Each EX Series switch is programmed with a factory-default configuration that
contains the values set for each configuration parameter when the switch is shipped.
The default configuration file sets values for system parameters such as
syslog and commit, configures Ethernet
switching on all interfaces, enables IGMP snooping, and enables the LLDP and RSTP
protocols.
The factory-default configuration file has more interfaces for models that have more ports.
The
poestatement appears only in models with ports that support PoE-bt.
When you commit changes to the configuration, a new configuration file is created, which becomes the active configuration. You can always revert to the factory-default configuration. See Revert to the Factory-Default Configuration for the EX Series Switch.
The following is the factory-default configuration file for an EX4400-24P switch with 24 ports that support PoE-bt. The factory-default configuration file for the other EX4400 models is similar.
system {
commit {
factory-settings {
reset-chassis-lcd-menu;
reset-virtual-chassis-configuration;
}
}
services {
ssh;
netconf {
ssh;
rfc-compliant;
yang-compliant;
}
}
auto-snapshot;
syslog {
file interactive-commands {
interactive-commands any;
}
file messages {
any notice;
authorization info;
}
}
phone-home {
server https://redirect.juniper.net;
rfc-compliant;
}
## Warning: missing mandatory statement(s): 'root-authentication'
}
chassis {
redundancy {
graceful-switchover;
}
}
interfaces {
ge-0/0/0 {
unit 0 {
family ethernet-switching {
storm-control default;
}
}
}
ge-0/0/1 {
unit 0 {
family ethernet-switching {
storm-control default;
}
}
}
ge-0/0/2 {
unit 0 {
family ethernet-switching {
storm-control default;
}
}
}
ge-0/0/3 {
unit 0 {
family ethernet-switching {
storm-control default;
}
}
}
ge-0/0/4 {
unit 0 {
family ethernet-switching {
storm-control default;
}
}
}
ge-0/0/5 {
unit 0 {
family ethernet-switching {
storm-control default;
}
}
}
ge-0/0/6 {
unit 0 {
family ethernet-switching {
storm-control default;
}
}
}
ge-0/0/7 {
unit 0 {
family ethernet-switching {
storm-control default;
}
}
}
ge-0/0/8 {
unit 0 {
family ethernet-switching {
storm-control default;
}
}
}
ge-0/0/9 {
unit 0 {
family ethernet-switching {
storm-control default;
}
}
}
ge-0/0/10 {
unit 0 {
family ethernet-switching {
storm-control default;
}
}
}
ge-0/0/11 {
unit 0 {
family ethernet-switching {
storm-control default;
}
}
}
ge-0/0/12 {
unit 0 {
family ethernet-switching {
storm-control default;
}
}
}
ge-0/0/13 {
unit 0 {
family ethernet-switching {
storm-control default;
}
}
}
ge-0/0/14 {
unit 0 {
family ethernet-switching {
storm-control default;
}
}
}
ge-0/0/15 {
unit 0 {
family ethernet-switching {
storm-control default;
}
}
}
ge-0/0/16 {
unit 0 {
family ethernet-switching {
storm-control default;
}
}
}
ge-0/0/17 {
unit 0 {
family ethernet-switching {
storm-control default;
}
}
}
ge-0/0/18 {
unit 0 {
family ethernet-switching {
storm-control default;
}
}
}
ge-0/0/19 {
unit 0 {
family ethernet-switching {
storm-control default;
}
}
}
ge-0/0/20 {
unit 0 {
family ethernet-switching {
storm-control default;
}
}
}
ge-0/0/21 {
unit 0 {
family ethernet-switching {
storm-control default;
}
}
}
ge-0/0/22 {
unit 0 {
family ethernet-switching {
storm-control default;
}
}
}
ge-0/0/23 {
unit 0 {
family ethernet-switching {
storm-control default;
}
}
}
et-0/2/0 {
unit 0 {
family ethernet-switching {
storm-control default;
}
}
}
xe-0/2/0 {
unit 0 {
family ethernet-switching {
storm-control default;
}
}
}
et-0/2/1 {
unit 0 {
family ethernet-switching {
storm-control default;
}
}
}
xe-0/2/1 {
unit 0 {
family ethernet-switching {
storm-control default;
}
}
}
et-0/2/2 {
unit 0 {
family ethernet-switching {
storm-control default;
}
}
}
xe-0/2/2 {
unit 0 {
family ethernet-switching {
storm-control default;
}
}
}
et-0/2/3 {
unit 0 {
family ethernet-switching {
storm-control default;
}
}
}
xe-0/2/3 {
unit 0 {
family ethernet-switching {
storm-control default;
}
}
}
irb {
unit 0 {
family inet {
dhcp;
}
}
}
vme {
unit 0 {
family inet {
dhcp;
}
}
}
}
forwarding-options {
storm-control-profiles default {
all;
}
}
protocols {
lldp {
interface all;
}
lldp-med {
interface all;
}
igmp-snooping {
vlan default;
}
rstp {
interface all;
}
}
poe {
interface all;
}
vlans {
default {
vlan-id 1;
l3-interface irb.0;
}
}
Revert an EX4400 Switch to the Factory-Default Configuration
If the current active configuration on your switch fails, you can revert to the factory-default configuration. You can also roll back to a previous configuration, as described in Rolling Back Junos OS Configuration Changes.
If you have lost the root password, it is not necessary to revert to the factory-default configuration to reset it. See Recovering the Root Password on Switches.
The factory-default configuration contains the basic configuration settings for the switch. This is the first configuration of the switch and it is loaded when the switch is first powered on. For the factory-default configuration file for your switch, see the hardware documentation for your switch.
To revert a member switch of a Virtual Chassis to the factory-default configuration, disconnect the cables connected to the VCPs to avoid affecting Virtual Chassis configuration parameters (member ID, primary-role priority, and setting of VCP uplinks) on other members (see Disconnect a Fiber-Optic Cable).
You can revert to the factory-default configuration by using the request
system zeroize operational command or the load
factory-default configuration command. You can also use the
load factory-default command to revert to the factory-default
configuration file that contains all default settings except the root
password setting, which is retained.
We describe these procedures in the following sections:
After resetting the factory default configuration either through the CLI or Factory Reset/Port mode button, the previous host name of the device is not reset. The host name can only be changed by configuring a new hostname or rebooting the device.
- Revert to the Factory-Default Configuration by Using the request system zeroize Command
- Revert to the Factory-Default Configuration by Using the load factory-default Command
- Revert to the Factory-Default Configuration by Using the Factory Reset/Mode Button
Revert to the Factory-Default Configuration by Using the request system zeroize Command
The request system zeroize command is a standard Junos OS
operational mode command that removes all configuration information and
resets all key values. The operation unlinks all user-created data files,
including customized configuration and log files, from their directories.
The switch then reboots and reverts to the factory-default
configuration.
To completely erase user-created data so that it is unrecoverable, use the
request system zeroize media command.
Before issuing request system zeroize, use the request system snapshot command to back up the files currently used to run the switch
to a secondary device.
Revert to the Factory-Default Configuration by Using the load factory-default Command
The load factory-default command is a standard Junos OS
configuration command that replaces the current active configuration with
the factory-default configuration (except the root password setting, which
by default is not set but which you must set in order to commit the new
configuration in this procedure).
If you want to run the EZsetup script to complete the initial configuration
of the switch after you revert to the factory-default configuration, do not
use the load factory-default command. Instead, do the
reversion by using the request system zeroize command. If
you use the load factory-default command to revert to the
factory-default configuration, the configuration for the root password is
retained and the EZsetup script will not run.
To revert to the factory-default configuration by using the load
factory-default command:
If you use this procedure, you must delete the system commit factory
settings, set the root password, and commit the configuration. These
steps are not required when you revert to the factory-default
configuration by using request system zeroize. Also,
the auto-image-upgrade statement is not added to the
configuration when you use this procedure; it is added to the
configuration when you use request system zeroize.
[edit]user@switch#
load factory-default[edit]user@switch#
delete system commit factory-settings[edit]user@switch#
set system root-authentication plain-text-password[edit]user@switch#
commitCheck the member ID and primary-role priority with the
show virtual-chassiscommand and check to see whether there are remaining settings for uplink VCPs by using theshow virtual-chassis vc-portcommand.
Revert to the Factory-Default Configuration by Using the Factory Reset/Mode Button
To revert to the factory-default configuration by using the factory reset/mode button:
The Factory Reset/Mode button is enabled by default. You can disable the button using the CLI.
To disable the Factory Reset/Mode button, run the following commands:
[edit] user@switch#
set chassis config-button no-clear[edit] user@switch#
commit
To enable the Factory Reset/Mode button, run the following commands:
[edit] user@switch#
delete chassis config-button no-clear[edit] user@switch#
commit
