EasyManuals Logo
Home>HP>Switch>3600 v2 Series

HP 3600 v2 Series Configuration Guide

HP 3600 v2 Series
449 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Page #39 background imageLoading...
Page #39 background image
26
Step Command Remarks
1. Enter system view.
system-view N/A
2. Enter RADIUS scheme view.
radius scheme
radius-scheme-name
N/A
3. Set the format for usernames
sent to the RADIUS servers.
user-name-format { keep-original
| with-domain | without-domain }
Optional.
By default, the ISP domain name is
included in a username.
4. Specify the unit for data flows
or packets sent to the RADIUS
servers.
data-flow-format { data { byte |
giga-byte | kilo-byte |
mega-byte } | packet
{ giga-packet | kilo-packet |
mega-packet | one-packet } }*
Optional.
The default unit is byte for data
flows and is one-packet for data
packets.
Setting the supported RADIUS server type
The supported RADIUS server type determines the type of the RADIUS protocol that the switch uses to
communicate with the RADIUS server. It can be standard or extended:
• Standard—Uses the standard RADIUS protocol, compliant to RFC 2865 and RFC 2866 or later.
• Extended—Uses the proprietary RADIUS protocol of HP.
When the RADIUS server runs on IMC, you must set the RADIUS server type to extended. When the
RADIUS server runs third-party RADIUS server software, either RADIUS server type applies. For the switch
to function as a RADIUS server to authenticate login users, you must set the RADIUS server type to
standard.
To set the RADIUS server type:
Step Command Remarks
1. Enter system view.
system-view N/A
2. Enter RADIUS scheme view.
radius scheme
radius-scheme-name
N/A
3. Set the RADIUS server type.
server-type { extended |
standard }
Optional.
The default RADIUS server type is
standard.
NOTE:
Changing the RADIUS server type restores the unit for data flows and that for packets that are sent to the
RADIUS server to the defaults.
Setting the maximum number of RADIUS request transmission attempts
Because RADIUS uses UDP packets to transfer data, the communication process is not reliable. RADIUS
uses a retransmission mechanism to improve the reliability. If a NAS sends a RADIUS request to a
RADIUS server but receives no response after the response timeout timer (defined by the timer
response-timeout command) expires, it retransmits the request. If the number of transmission attempts
exceeds the specified limit but it still receives no response, it tries to communicate with other RADIUS
servers in active state. If no other servers are in active state at the time, it considers the authentication or
accounting attempt a failure. For more information about RADIUS server states, see "Setting the status of
RA
DIUS servers."

Table of Contents

Other manuals for HP 3600 v2 Series

Questions and Answers:

Question and Answer IconNeed help?

Do you have a question about the HP 3600 v2 Series and is the answer not in the manual?

HP 3600 v2 Series Specifications

General IconGeneral
BrandHP
Model3600 v2 Series
CategorySwitch
LanguageEnglish

Related product manuals