Layer 2 Authentication and Access Control · Topic 3 of 3

Multiple Methods, Configuring and Troubleshooting

JN0-650 study page on combining 802.1X, MAC RADIUS and captive portal on Junos switches, the order of methods, a full example and troubleshooting steps.

  • 4 min
In a nutshell
  • The default order of methods: 802.1X, MAC RADIUS, captive portal.
  • Combine methods on one interface; each failure moves to the next.
  • supplicant multiple lets several devices authenticate on one port.

What it is

Real access ports see different kinds of devices: laptops with 802.1X clients, printers with only a MAC address, guests with only a browser, and phones next to PCs. A Junos switch can enable several methods on the same port and tries them in a fixed order.

This page explains that order, shows a full configuration, and gives a troubleshooting routine you can apply to the whole chapter.

Port upEAPOL answered?802.1Xno EAPOLMAC RADIUSno matchCaptive portalno loginGuest VLAN

How it works

The order of methods

By default, the switch tries 802.1X first. If the device does not answer EAPOL, the switch tries MAC RADIUS. If that fails, captive portal is the last method, and if all fail, the guest VLAN or the deny behavior applies.

StepMethodNeeds from the device
1802.1XAn 802.1X supplicant
2MAC RADIUSOnly a MAC address
3Captive portalA browser and a user
4Guest VLAN or denyNothing

Two rules help with the exam. A device that does run 802.1X but fails the credentials is not silently retried through MAC RADIUS if mac-radius restrict is set. And the more secure the method, the earlier it is in the order.

Choosing the method for a device

DeviceBest fit
Managed laptop with a certificate802.1X
Printer, camera, badge readerMAC RADIUS
Visitor with a browserCaptive portal
Unknown deviceGuest VLAN with limited access
IP phone beside a PCsupplicant multiple, plus a voice VLAN

A combined configuration

set access radius-server 10.1.1.100 secret "<secret>"
set access profile AUTH-PROFILE authentication-order radius
set access profile AUTH-PROFILE radius authentication-server 10.1.1.100
set protocols dot1x authenticator authentication-profile-name AUTH-PROFILE
set protocols dot1x authenticator interface ge-0/0/5.0 supplicant multiple
set protocols dot1x authenticator interface ge-0/0/5.0 mac-radius
set protocols dot1x authenticator interface ge-0/0/5.0 guest-vlan GUEST
set protocols dot1x authenticator interface ge-0/0/5.0 server-fail vlan-name FALLBACK
set protocols dot1x authenticator interface ge-0/0/5.0 server-reject-vlan REJECT-VLAN

Every VLAN named here must exist on the switch. The port itself stays an ordinary access or trunk port, and RADIUS can change its VLAN dynamically after authentication.

Phone and PC on one port

A PC behind an IP phone is the typical case for supplicant multiple. The phone and the PC each authenticate separately, and each can end up in a different VLAN: the phone in the voice VLAN and the PC in a data VLAN. This relies on the voice VLAN feature covered in the IP Telephony chapter.

Monitoring

show dot1x interface
show dot1x interface ge-0/0/5.0 detail

For deeper analysis, enable tracing and read the log:

set protocols dot1x traceoptions file dot1x.trace
set protocols dot1x traceoptions flag all
show log dot1x.trace
Watch out

Tracing with flag all is verbose. Use it briefly on a test port and remove it afterward.

Troubleshooting routine

Link up?yesPort in dot1x config?yesServer reachable?yesSecret and client entry ok?yesVLAN exists?
SymptomLikely cause
Device never authenticatesInterface not under protocols dot1x authenticator, or the supplicant is disabled
Authentication times outRADIUS unreachable, wrong secret, or the switch is not a RADIUS client on the server
Success, but wrong VLANThe VLAN name or ID returned by RADIUS does not exist on the switch
Second device on the port blockedMode is single or single-secure; use multiple
Printer waits a long timeTimers: the switch waits for EAPOL replies before it tries MAC RADIUS
Everyone blocked during an outageserver-fail is at the default deny; configure a fallback
Guest VLAN never appliedA supplicant answers, or the guest VLAN does not exist
Exam tip

Work from the device toward the server: link, port configuration, reachability to RADIUS, secret and client entry, returned attributes, and the VLAN on the switch.

Common mistakes

Enabling several methods but one mode. A shared port needs multiple.

Naming a VLAN that does not exist. Fallback and dynamic VLANs fail silently.

Skipping the RADIUS client entry on the server. The most common cause of timeouts.

Putting captive portal first. The order is fixed: 802.1X, MAC RADIUS, then captive portal.

Testing only the happy path. Test an outage and a rejection as well.

What to remember for the exam

  • The default order of methods: 802.1X, MAC RADIUS, captive portal.
  • Combine methods on one interface; each failure moves to the next.
  • supplicant multiple lets several devices authenticate on one port.
  • Fallbacks: guest VLAN (no supplicant), server-reject VLAN (rejected), server-fail (no answer).
  • Verify with show dot1x interface and trace with protocols dot1x traceoptions.
  • Troubleshoot from link, to config, to RADIUS reachability, to secret, to attributes, to VLAN.

Check yourself

  • In what order does a Junos switch try authentication methods by default?

    802.1X, then MAC RADIUS, then captive portal.

  • Authentication succeeds but the port is in the wrong VLAN. What do you check?

    Whether the VLAN returned by RADIUS exists on the switch with the same name or ID.

  • A phone and a PC share a port and only one works. What setting is probably wrong?

    The supplicant mode; it should be multiple.

Topic 3 of 3 in Layer 2 Authentication and Access Control

Test yourself on Layer 2 Authentication and Access Control

The full Juniper JNCIP-ENT JN0-650 question bank has 858 questions, with timed practice exams and an explanation for every answer.

This study guide is independent and is not affiliated with, endorsed by, or sponsored by Juniper. Vendor names, certification names and exam codes are trademarks of their respective owners and are used for identification only.