HP 6125XLG R2306-HP 6125XLG Blade Switch Security Configuration Guide - Page 35

Setting the maximum number of RADIUS request transmission attempts

Page 35 highlights

To set the username format and the traffic statistics units for a RADIUS scheme: Step 1. Enter system view. 2. Enter RADIUS scheme view. 3. Set the format for usernames sent to the RADIUS servers. 4. (Optional.) Set the data flow and packet measurement units for traffic statistics. Command Remarks system-view N/A radius scheme radius-scheme-name N/A user-name-format { keep-original By default, the ISP domain name is | with-domain | without-domain } included in a username. data-flow-format { data { byte | giga-byte | kilo-byte | mega-byte } | packet { giga-packet | kilo-packet | mega-packet | one-packet } }* By default, traffic is counted in bytes and packets. The command does not apply to 802.1X and MAC users, for whom the switch does not support traffic accounting. Setting the maximum number of RADIUS request transmission attempts RADIUS uses UDP packets to transfer data. UDP communication is not reliable. To improve reliability, RADIUS uses a retransmission mechanism. If a NAS sends a RADIUS request to a RADIUS server but receives no response before 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 the RADIUS server response timeout timer, see "Setting RADIUS timers." To set the maximum number of RADIUS request transmission attempts: Step 1. Enter system view. 2. Enter RADIUS scheme view. 3. Set the maximum number of RADIUS request transmission attempts. Command system-view radius scheme radius-scheme-name retry retry-times Remarks N/A N/A The default setting is 3. Setting the status of RADIUS servers By setting the status of RADIUS servers to blocked or active, you can control the RADIUS servers with which the device communicates when the current servers are no longer available. In practice, you can specify one primary RADIUS server and multiple secondary RADIUS servers, with the secondary servers functioning as the backup of the primary servers. Typically, the device chooses servers based on these rules: • When the primary server is in active state, the device communicates with the primary server. If the primary server fails, the device changes the server's status to blocked, starts a quiet timer for the server, and tries to communicate with a secondary server in active state (a secondary server configured earlier has a higher priority). If the secondary server is unreachable, the device changes the server's status to blocked, starts a quiet timer for the server, and continues to check the next secondary server in active state. This search process continues until the device finds an available secondary server or has checked all secondary servers in active state. 26

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276

26
To set the username format and the traffic statistics units for a RADIUS scheme:
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
}
By default, the ISP domain name is
included in a username.
4.
(Optional.) Set the data flow
and packet measurement
units for traffic statistics.
data-flow-format
{
data
{
byte
|
giga-byte
|
kilo-byte
|
mega-byte
}
|
packet
{
giga-packet
|
kilo-packet
|
mega-packet
|
one-packet
} }*
By default, traffic is counted in
bytes and packets.
The command does not apply to
802.1X and MAC users, for whom
the switch does not support traffic
accounting.
Setting the maximum number of RADIUS request transmission attempts
RADIUS uses UDP packets to transfer data. UDP communication is not reliable. To improve reliability,
RADIUS uses a retransmission mechanism. If a NAS sends a RADIUS request to a RADIUS server but
receives no response before 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 the RADIUS server response timeout timer, see "
Setting RADIUS timers
."
To set the maximum number of RADIUS request transmission attempts:
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 maximum number of RADIUS
request transmission attempts.
retry
retry-times
The default setting is 3.
Setting the status of RADIUS servers
By setting the status of RADIUS servers to
blocked
or
active
, you can control the RADIUS servers with
which the device communicates when the current servers are no longer available. In practice, you can
specify one primary RADIUS server and multiple secondary RADIUS servers, with the secondary servers
functioning as the backup of the primary servers. Typically, the device chooses servers based on these
rules:
When the primary server is in
active
state, the device communicates with the primary server.
If the primary server fails, the device changes the server's status to
blocked
, starts a quiet timer for
the server, and tries to communicate with a secondary server in
active
state (a secondary server
configured earlier has a higher priority).
If the secondary server is unreachable, the device changes the server's status to
blocked
, starts a
quiet timer for the server, and continues to check the next secondary server in
active
state. This
search process continues until the device finds an available secondary server or has checked all
secondary servers in
active
state.