02.10.2013 Views

FTOS Configuration Guide for the C-Series - Force10 Networks

FTOS Configuration Guide for the C-Series - Force10 Networks

FTOS Configuration Guide for the C-Series - Force10 Networks

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Figure 474 RADIUS Frame Format<br />

Code Identifier Length Message-Au<strong>the</strong>nticator<br />

Attribute<br />

Range: 1-4<br />

Codes: 1: Access-Request<br />

2: Access-Accept<br />

3: Access-Reject<br />

11: Access-Challenge<br />

The au<strong>the</strong>ntication process involves three devices:<br />

• The device attempting to access <strong>the</strong> network is <strong>the</strong> supplicant. The supplicant is not allowed to<br />

communicate on <strong>the</strong> network until <strong>the</strong> port is authorized by <strong>the</strong> au<strong>the</strong>nticator. It can only communicate<br />

with <strong>the</strong> au<strong>the</strong>nticator in response to 802.1X requests.<br />

• The device with which <strong>the</strong> supplicant communicates is <strong>the</strong> au<strong>the</strong>nticator. The au<strong>the</strong>nicator is <strong>the</strong> gate<br />

keeper of <strong>the</strong> network. It translates and <strong>for</strong>wards requests and responses between <strong>the</strong> au<strong>the</strong>ntication<br />

server and <strong>the</strong> supplicant. The au<strong>the</strong>nticator also changes <strong>the</strong> status of <strong>the</strong> port based on <strong>the</strong> results of<br />

<strong>the</strong> au<strong>the</strong>ntication process. The <strong>Force10</strong> switch is <strong>the</strong> au<strong>the</strong>nticator.<br />

• The au<strong>the</strong>ntication-server selects <strong>the</strong> au<strong>the</strong>ntication method, verifies <strong>the</strong> in<strong>for</strong>mation provided by <strong>the</strong><br />

supplicant, and grants it network access privileges.<br />

Ports can be in one of two states:<br />

• Ports are in an unauthorized state by default. In this state, non-802.1X traffic cannot be <strong>for</strong>warded in<br />

or out of <strong>the</strong> port.<br />

• The au<strong>the</strong>nticator changes <strong>the</strong> port state to authorized if <strong>the</strong> server can au<strong>the</strong>nticate <strong>the</strong> supplicant. In<br />

this state, network traffic can be <strong>for</strong>warded normally.<br />

Note: The <strong>Force10</strong> switches place 802.1X-enabled ports in <strong>the</strong> unathorized state by default.<br />

The Port-au<strong>the</strong>ntication Process<br />

The au<strong>the</strong>ntication process begins when <strong>the</strong> au<strong>the</strong>nticator senses that a link status has changed from down<br />

to up:<br />

1. When <strong>the</strong> au<strong>the</strong>nticator senses a link state change, it requests that <strong>the</strong> supplicant identify itself using an<br />

EAP Identity Request Frame.<br />

2. The supplicant responds with its identity in an EAP Response Identity frame.<br />

Type<br />

(79)<br />

EAP-Message Attribute<br />

Length EAP-Method Data<br />

(Supplicant Requested Credentials)<br />

3. The au<strong>the</strong>nticator decapsulates <strong>the</strong> EAP Response from <strong>the</strong> EAPOL frame, encapulates it in a<br />

RADIUS Access-Request frame, and <strong>for</strong>wards <strong>the</strong> frame to <strong>the</strong> au<strong>the</strong>ntication server.<br />

fnC0034mp<br />

<strong>FTOS</strong> <strong>Configuration</strong> <strong>Guide</strong>, version 7.7.1.0 675

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!