Eric Radman : a Journal

Juniper EX Configuration

I never write about my experience maintaining or configuring network switches, mainly because the options provided for declaring configuration are not impressive. Most proprietary switches provide a CLI for interactive use, but no means of applying this configuration apart from vendor-specific protocols.

JunOS is proprietary, but provides a far better story:

  1. A sandboxed FreeBSD 11 userland with modern SSH protocols
  2. Tools for loading, merging and displaying the diff of a configuration

The following are notes on configuring the Juniper EX2300-C for my home/office using rset(1).

USB console

Juniper switches can be accessed using a USB cable since have a built-in UART

uslcom0 at uhub0 port 4 configuration 1 interface 0 "Silicon Labs CP2104 USB to UART Bridge Controller" rev 2.00/1.00 addr 8
ucom0 at uslcom0 portno 0

To switch output to the USB console run

set system ports auxiliary port-type mini-usb

Manual configuration can now be handled from my from my OpenBSD router using

cu -l cuaU0

Configuring SSH

The next step is to establish network access using a management interface

set interfaces me0 unit 0 family inet address
set routing-options static route next-hop

Set accepted cypers

set system services ssh hostkey-algorithm ssh-ed25519

Add users

set system login user eradman class super-user
set system login user eradman authentication ssh-ed25519 "ssh-ed25519 key..."

Once we have settled on a network design we can bring up a layer 3 interface and assign an IP address that is accessible on a VLAN instead

set interfaces irb unit 80 description wired-network
set interfaces irb unit 80 family inet address

Upgrading JunOS

> show version
> request system software add reboot

Or if there isn't enough space

> request system software add force unlink no-copy

Remote Sequential Execution Tool

Enabling root login provides access to the Unix shell over SSH, which will allow us to use rset(1) to configure the switch!

set system root-authentication ssh-ed25519 "ssh-ed25519 key..."
set system services ssh root-login deny-password

Now that we have SSH access to the JunOS/FreeBSD userland we can add a route entry

# routes.pln juniper/

Change the default connecting user to root

# ssh_config
  User root

Define a simple label to test connectivity

# ex2300-c.pln

Run using

rset -F ssh_config -x ping

Now we can write down commands to run using the Juniper cli tool

# ex2300-c.pln
    cli <<-!!
    load set juniper/ex2300-c
    show | compare

# vim:noexpandtab:syntax=sh:ts=4

Trunking to an OpenBSD Router

First we'll define the vlans on the switch

# juniper/ex2300-c

set vlans vlan80 description wired
set vlans vlan80 vlan-id 80
set vlans vlan80 l3-interface irb.80

set vlans vlan81 description wireless
set vlans vlan81 vlan-id 81
set vlans vlan81 l3-interface irb.81

Set interfaces to trunk mode to accept 802.1q frames

edit interfaces ge-0/0/0
  set description "Uplink to router"
  edit unit 0 family ethernet-switching
    set interface-mode trunk
    set vlan members vlan80
    set vlan members vlan81

On the OpenBSD host ensure the physical interface is up and define the VLANs

# hostname.em0
# hostname.vlan0
parent em0 vnetid 80
# hostname.vlan1
parent em0 vnetid 81

To install these using rset(1), I often use a shell loop and set a variable to indicate the network needs to be reconfigured

# apu4d2.pln
    let changed=0
    for interface in em0 vlan0 vlan1
        ./rinstall -m 640 apu4d2/hostname.$interface /etc/hostname.$interface && changed=1
    [ $changed -ge 0 ] && sh /etc/netstart

# vim:noexpandtab:syntax=sh:ts=4

Aggregate Links

Tagged or untagged interfaces may be set up for redundancy

set interfaces ge-0/0/10 ether-options 802.3ad ae0
set interfaces ge-0/0/11 ether-options 802.3ad ae0

edit interfaces ae0
  description "apu4d2 em0,em1"
  aggregated-ether-options lacp active
  edit unit 0 family ethernet-switching
      set interface-mode access
      set vlan members vlan80

On the OpenBSD host, configure an aggregate interface and it's members. There is some mismatched terminology here, since trunkport on OpenBSD implements LACP, not VLAN tagging.

# /etc/hostname.aggr0
trunkport em0
trunkport em1

# /etc/hostname.em0

# /etc/hostname.em1


JunOS is far more adaptable to configuration management than most switches since you stage your changes before committing. Another feature is the ability to clear a section using delete in order to ensure you have redefined an entire category

delete poe
set poe interface ge-0/0/6
set poe interface ge-0/0/7

Multicast DNS

Now that we have a home network with multiple VLANs it would be useful to restore service discovery for configuring printers. We can do this by enabling a Bonjour route reflector

# apu4d2.pln
  pkg_add avahi

    ./rsub -r '#enable-reflector=.+' -l 'enable-reflector=yes' /etc/avahi/avahi-daemon.conf
    ./rsub -r '#deny-interfaces.+' -l 'deny-interfaces=em0' /etc/avahi/avahi-daemon.conf
    rcctl enable messagebus avahi_daemon

To test, watch for multicast traffic

apu4d2$ doas tcpdump -n -i vlan0 dst

Random Advice has everything you need to assemble tidy cabling. These products are a joy to use:

Last updated on May 13, 2021