As an Juniper expert, please provide the CLI commands for checking wired 802.1x for…
- User
As an Juniper expert, please provide the CLI commands for checking wired 802.1x for troubleshooting mac address, user login, configuration for ports on EX switches
Assistant
Of course. As a Juniper expert, here is a comprehensive guide to the CLI commands for troubleshooting wired 802.1X on EX series switches.
This guide is structured to follow a logical troubleshooting methodology, starting with broad checks and narrowing down to specific issues.
802.1X Troubleshooting Methodology
The key players in 802.1X are:
- Supplicant: The client device (e.g., a laptop) trying to connect.
- Authenticator: The Juniper EX switch port.
- Authentication Server: The RADIUS server (e.g., Cisco ISE, ClearPass, NPS).
Troubleshooting involves checking the state and communication between these three components.
1. High-Level 802.1X Status (The "50,000 Foot View")
These commands give you a quick overview of the 802.1X health across the entire switch.
show dot1x interfaceThis is your primary starting point. It shows the status of all interfaces configured for 802.1X.
user@EX-switch> show dot1x interface 802.1X Information: Interface Role State MAC address User ge-0/0/0.0 Authenticator Authenticated 00:1C:73:00:11:22 j-doe ge-0/0/1.0 Authenticator Connecting 00:1C:73:00:33:44 N/A ge-0/0/2.0 Authenticator Held 00:1C:73:00:55:66 N/A ge-0/0/3.0 Authenticator Disabled N/A N/AKey
Statecolumn values:- Authenticated: Success! The supplicant has been authenticated by the RADIUS server.
- Connecting: The switch is actively trying to authenticate the supplicant (EAPOL frames are being exchanged). If it's stuck here, there's likely a problem with the supplicant's configuration or the RADIUS server.
- Held: The supplicant failed authentication (e.g., bad password). The switch places the port in a "held" state for a configured period (
quiet-period) before retrying. - Disabled: 802.1X is configured but administratively disabled on the port.
2. Checking the Configuration for a Specific Port
If an interface isn't behaving as expected, verify its configuration.
show configuration interfaces <interface-name>Check the specific interface configuration to ensure dot1x is applied.
user@EX-switch> show configuration interfaces ge-0/0/1 description "User Access Port"; unit 0 { family ethernet-switching { port-mode access; vlan { members data-vlan; } } }show configuration protocols dot1xCheck the global and interface-specific 802.1X protocol settings.
user@EX-switch> show configuration protocols dot1x authenticator { authentication-profile-name radius-auth-profile; # Points to RADIUS config interface { ge-0/0/0.0 { supplicant multiple; # Allows multiple supplicants retries 3; guest-vlan guest; # Fallback VLAN if auth fails server-fail vlan-name voice; # Fallback if RADIUS is unreachable } ge-0/0/1.0 { supplicant single; reauthentication 1800; # Re-authenticate every 30 mins } all; # Default settings for all other interfaces } }show configuration accessVerify the RADIUS server profile is correctly configured.
user@EX-switch> show configuration access profile radius-auth-profile { authentication-order radius; radius { authentication-server [ 10.10.10.100 10.10.10.101 ]; secret "$9$3yqChtkoSOTdJik279A"; ## SECRET-DATA } }
3. Troubleshooting a Specific MAC Address
This is a common task when a user reports their device cannot connect.
Step 1: Find the interface the MAC address is on.
user@EX-switch> show ethernet-switching table | match 00:1C:73:00:33:44 Ethernet-switching table: 2 entries, 2 learned VLAN MAC address Type Age Interfaces data-vlan * Flood - All-members data-vlan 00:1c:73:00:33:44 Learn 0 ge-0/0/1.0Result: The MAC is on interface
ge-0/0/1.0.Step 2: Get detailed dot1x information for that interface. This command is the most valuable for deep-diving into a single port's state.
user@EX-switch> show dot1x interface detail ge-0/0/1.0 ge-0/0/1.0 Role: Authenticator Administrative-state: Auto Supplicant-mode: Single Number of retries: 3 Quiet-period: 60 seconds Server-timeout: 30 seconds Mac-Radius: Enabled Mac-Radius-restrict: Disabled Re-authentication: Enabled Configured Re-authentication interval: 1800 seconds Guest-vlan: guest PAE state: Connecting <-- Current state machine position Backend-state: Idle <-- RADIUS communication state Authentication statistics: EAPOL frames received: 15 EAPOL frames transmitted: 12 EAP Start packets: 4 EAP Logoff packets: 0 EAP-Success packets: 0 <-- No success packets received EAP-Failure packets: 3 <-- Failure packets received! Supplicant: 00:1C:73:00:33:44 Operational state: Connecting Backend state: Idle Authentication method: EAP-MD5 Last EAP-Failure received: EAP-Failure (code 4) from authenticatorAnalysis of this output:
- The port is stuck in the
Connectingstate. - It has received 3
EAP-Failurepackets. This indicates the RADIUS server is actively rejecting the authentication attempt. - The problem is not switch connectivity to RADIUS, but rather the credentials or policy on the RADIUS server for this supplicant/MAC.
4. Troubleshooting a Specific User Login
If a user is being authenticated by username (e.g., PEAP), you can check their status directly.
show dot1x authenticator user <username>This command is useful if the user successfully authenticated and you need to find where they are connected.
user@EX-switch> show dot1x authenticator user j-doe Authenticator User MAC Address Interface VLAN State PAE j-doe 00:1C:73:00:11:22 ge-0/0/0.0 data-vlan AuthenticatedIf this command returns no output: The user has either not attempted to log in, or their authentication has failed. In this case, you must pivot to troubleshooting by MAC address (as above) and checking the RADIUS server logs for that specific username to see the reason for failure (e.g., incorrect password, certificate issue, expired account).
5. Verifying RADIUS Server Connectivity
If multiple clients are failing, the problem could be between the switch (Authenticator) and the RADIUS server.
show dot1x radius-serversCheck statistics for communication with the RADIUS servers.
user@EX-switch> show dot1x radius-servers Radius-Server Address Port Status Requests Responses Timeouts Malformed 10.10.10.100 10.10.10.100 1812 Up 50 47 3 0 10.10.10.101 10.10.10.101 1812 Up 0 0 0 0- A high number of
Timeoutsis a red flag. It indicates the switch is sending requests, but the RADIUS server isn't responding. Check for network connectivity (ping, traceroute), firewalls, and ensure the switch is defined as a valid RADIUS client on the server with the correct shared secret.
test aaaThis is an excellent tool to test the entire authentication chain without needing a physical client.
# Test a user authentication against the RADIUS server user@EX-switch> test aaa user j-doe password <password>The output will tell you if the authentication was a success or failure, confirming that the switch, RADIUS server, and user credentials are all working correctly.
6. Advanced Troubleshooting with Traceoptions
When all else fails,
traceoptionsprovides a verbose log of the entire 802.1X and RADIUS exchange.Warning: Use this only for active troubleshooting, as it can be CPU-intensive.
Step 1: Configure traceoptions.
# In configuration mode set protocols dot1x traceoptions file dot1x-log size 10m files 3 set protocols dot1x traceoptions flag all # You might also want to trace the RADIUS process itself set access traceoptions file radius-log size 10m files 3 set access traceoptions flag all commitStep 2: Re-run the test (e.g., unplug/replug the client).
Step 3: View the log file.
user@EX-switch> show log dot1x-log # Look for EAPOL start, request, response, and success/failure packets # You will see the entire EAP conversation user@EX-switch> show log radius-log # Look for RADIUS Access-Request, Access-Challenge, and Access-Accept/Reject packetsStep 4: Deactivate traceoptions when finished.
# In configuration mode deactivate protocols dot1x traceoptions deactivate access traceoptions commit
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.