Configuring Junos OS on the OCX1100
OCX1100 Default Configuration
Each OCX1100 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 following default configuration file is for an OCX1100 switch:
NoteInterfaces ge-0/0/1 through ge-0/0/48 are SFP+ port interfaces.
Interfaces ge-0/0/49 through ge-0/0/54 are QSFP+ port interfaces.
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.
system {
commit {
factory-settings {
reset-virtual-chassis-configuration;
reset-chassis-lcd-menu;
}
}
processes {
app-engine-virtual-machine-management-service {
}
}
}
xe-0/0/1 {
unit 0 {
family inet {
dhcp {
vendor-id Juniper-ocx1100-48sx
}
}
}
}
xe-0/0/2 {
unit 0 {
family inet {
dhcp {
vendor-id Juniper-ocx1100-48sx
}
}
}
}
xe-0/0/3 {
unit 0 {
family inet {
dhcp {
vendor-id Juniper-ocx1100-48sx
}
}
}
}
xe-0/0/4 {
unit 0 {
family inet {
dhcp {
vendor-id Juniper-ocx1100-48sx
}
}
}
}
xe-0/0/5 {
unit 0 {
family inet {
dhcp {
vendor-id Juniper-ocx1100-48sx
}
}
}
}
xe-0/0/6 {
unit 0 {
family inet {
dhcp {
vendor-id Juniper-ocx1100-48sx
}
}
}
}
xe-0/0/7 {
unit 0 {
family inet {
dhcp {
vendor-id Juniper-ocx1100-48sx
}
}
}
}
xe-0/0/8 {
unit 0 {
family inet {
dhcp {
vendor-id Juniper-ocx1100-48sx
}
}
}
}
xe-0/0/9 {
unit 0 {
family inet {
dhcp {
vendor-id Juniper-ocx1100-48sx
}
}
}
}
xe-0/0/10 {
unit 0 {
family inet {
dhcp {
vendor-id Juniper-ocx1100-48sx
}
}
}
}
xe-0/0/11 {
unit 0 {
family inet {
dhcp {
vendor-id Juniper-ocx1100-48sx
}
}
}
}
xe-0/0/12 {
unit 0 {
family inet {
dhcp {
vendor-id Juniper-ocx1100-48sx
}
}
}
}
xe-0/0/13 {
unit 0 {
family inet {
dhcp {
vendor-id Juniper-ocx1100-48sx
}
}
}
}
xe-0/0/14 {
unit 0 {
family inet {
dhcp {
vendor-id Juniper-ocx1100-48sx
}
}
}
}
xe-0/0/15 {
unit 0 {
family inet {
dhcp {
vendor-id Juniper-ocx1100-48sx
}
}
}
}
xe-0/0/16 {
unit 0 {
family inet {
dhcp {
vendor-id Juniper-ocx1100-48sx
}
}
}
}
xe-0/0/17 {
unit 0 {
family inet {
dhcp {
vendor-id Juniper-ocx1100-48sx
}
}
}
}
xe-0/0/18 {
unit 0 {
family inet {
dhcp {
vendor-id Juniper-ocx1100-48sx
}
}
}
}
xe-0/0/19 {
unit 0 {
family inet {
dhcp {
vendor-id Juniper-ocx1100-48sx
}
}
}
}
xe-0/0/20 {
unit 0 {
family inet {
dhcp {
vendor-id Juniper-ocx1100-48sx
}
}
}
}
xe-0/0/21 {
unit 0 {
family inet {
dhcp {
vendor-id Juniper-ocx1100-48sx
}
}
}
}
xe-0/0/22 {
unit 0 {
family inet {
dhcp {
vendor-id Juniper-ocx1100-48sx
}
}
}
}
xe-0/0/23 {
unit 0 {
family inet {
dhcp {
vendor-id Juniper-ocx1100-48sx
}
}
}
}
xe-0/0/24 {
unit 0 {
family inet {
dhcp {
vendor-id Juniper-ocx1100-48sx
}
}
}
}
xe-0/0/25 {
unit 0 {
family inet {
dhcp {
vendor-id Juniper-ocx1100-48sx
}
}
}
}
xe-0/0/26 {
unit 0 {
family inet {
dhcp {
vendor-id Juniper-ocx1100-48sx
}
}
}
}
xe-0/0/27 {
unit 0 {
family inet {
dhcp {
vendor-id Juniper-ocx1100-48sx
}
}
}
}
xe-0/0/28 {
unit 0 {
family inet {
dhcp {
vendor-id Juniper-ocx1100-48sx
}
}
}
}
xe-0/0/29 {
unit 0 {
family inet {
dhcp {
vendor-id Juniper-ocx1100-48sx
}
}
}
}
xe-0/0/30 {
unit 0 {
family inet {
dhcp {
vendor-id Juniper-ocx1100-48sx
}
}
}
}
xe-0/0/31 {
unit 0 {
family inet {
dhcp {
vendor-id Juniper-ocx1100-48sx
}
}
}
}
xe-0/0/32 {
unit 0 {
family inet {
dhcp {
vendor-id Juniper-ocx1100-48sx
}
}
}
}
xe-0/0/33 {
unit 0 {
family inet {
dhcp {
vendor-id Juniper-ocx1100-48sx
}
}
}
}
xe-0/0/34 {
unit 0 {
family inet {
dhcp {
vendor-id Juniper-ocx1100-48sx
}
}
}
}
xe-0/0/35 {
unit 0 {
family inet {
dhcp {
vendor-id Juniper-ocx1100-48sx
}
}
}
}
xe-0/0/36 {
unit 0 {
family inet {
dhcp {
vendor-id Juniper-ocx1100-48sx
}
}
}
}
xe-0/0/37 {
unit 0 {
family inet {
dhcp {
vendor-id Juniper-ocx1100-48sx
}
}
}
}
xe-0/0/38 {
unit 0 {
family inet {
dhcp {
vendor-id Juniper-ocx1100-48sx
}
}
}
}
xe-0/0/39 {
unit 0 {
family inet {
dhcp {
vendor-id Juniper-ocx1100-48sx
}
}
}
}
xe-0/0/40 {
unit 0 {
family inet {
dhcp {
vendor-id Juniper-ocx1100-48sx
}
}
}
}
xe-0/0/41 {
unit 0 {
family inet {
dhcp {
vendor-id Juniper-ocx1100-48sx
}
}
}
}
xe-0/0/42 {
unit 0 {
family inet {
dhcp {
vendor-id Juniper-ocx1100-48sx
}
}
}
}
xe-0/0/43 {
unit 0 {
family inet {
dhcp {
vendor-id Juniper-ocx1100-48sx
}
}
}
}
xe-0/0/44 {
unit 0 {
family inet {
dhcp {
vendor-id Juniper-ocx1100-48sx
}
}
}
}
xe-0/0/45 {
unit 0 {
family inet {
dhcp {
vendor-id Juniper-ocx1100-48sx
}
}
}
}
xe-0/0/46 {
unit 0 {
family inet {
dhcp {
vendor-id Juniper-ocx1100-48sx
}
}
}
}
xe-0/0/47 {
unit 0 {
family inet {
dhcp {
vendor-id Juniper-ocx1100-48sx
}
}
}
}
xe-0/0/48 {
unit 0 {
family inet {
dhcp {
vendor-id Juniper-ocx1100-48sx
}
}
}
}
et-0/0/49 {
unit 0 {
family inet {
dhcp {
vendor-id Juniper-ocx1100-48sx
}
}
}
}
et-0/0/50 {
unit 0 {
family inet {
dhcp {
vendor-id Juniper-ocx1100-48sx
}
}
}
}
et-0/0/51 {
unit 0 {
family inet {
dhcp {
vendor-id Juniper-ocx1100-48sx
}
}
}
}
et-0/0/52 {
unit 0 {
family inet {
dhcp {
vendor-id Juniper-ocx1100-48sx
}
}
}
}
et-0/0/53 {
unit 0 {
family inet {
dhcp {
vendor-id Juniper-ocx1100-48sx
}
}
}
}
et-0/0/54 {
unit 0 {
family inet {
dhcp {
vendor-id Juniper-ocx1100-48sx
}
}
}
}
}
Connecting and Configuring an OCX1100 Switch (CLI Procedure)
You can connect and configure an OCX1100 switch through the
console by using the CLI.
Before you begin connecting and configuring
an OCX1100 switch, set the following parameter values on the console
server or PC:
Baud rate—115,200
Flow control—None
Data—8
Parity—None
Stop bits—1
DCD state—Disregard
To connect and configure the switch from the console:
- Connect the console port on the rear panel of the switch
to a laptop or PC by using the RJ-45 to DB-9 serial port adapter.
See OCX1100 Switches Hardware Overview.
You can also use the Mini-USB Type-B console port to connect to a
laptop or PC. See Connecting an OCX1100 Switch to a Management Console by Using the Mini-USB Type-B Console Port.
- Log in as root. There is no password. If the software
booted before you connected to the console port, press the Enter key
for the prompt to appear.
- Start the CLI.
- Enter configuration mode.
- Specify a password for the root administration user account.
[edit]
root@# set system root-authentication plain-text-password
New password: password
Retype new password: password
- (Optional) Configure the name of the switch. If the name
includes spaces, enclose the name in quotation marks (“ ”).
[edit]
root@# set system host-name host-name
- Configure the default gateway.
[edit]
root@# set routing-options static route default
next-hop address
- Configure the IP address and prefix length for the switch
management interface.
[edit]
root@# set interfaces em0 unit 0 family inet
address address/prefix-length
- (Optional) Configure the static routes to remote prefixes
with access to the management port.
[edit]
root@# set routing-options static route remote-prefix next-hop destination-ip retain no-readvertise
- Enable ssh service.
root# set system services ssh root-login allow
- Commit the configuration.