HP 6125G HP 6125G & 6125G/XG Blade Switches Security Configuration Gui - Page 34

Setting the supported RADIUS server type

Page 34 highlights

• For level switching authentication, the user-name-format keep-original and user-name-format without-domain commands produce the same results. They make sure usernames sent to the RADIUS server carry no ISP domain name. 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 } Optional. By default, the ISP domain name is included in a username. data-flow-format { data { byte | 4. Specify the unit for data flows giga-byte | kilo-byte | or packets sent to the RADIUS mega-byte } | packet servers. { 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. To set the RADIUS server type: Step 1. Enter system view. 2. Enter RADIUS scheme view. Command system-view radius scheme radius-scheme-name 3. Set the RADIUS server type. server-type { extended | standard } Remarks N/A N/A 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 24

  • 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
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285

24
For level switching authentication, the
user-name-format keep-original
and
user-name-format
without-domain
commands produce the same results. They make sure usernames sent to the
RADIUS server carry no ISP domain name.
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
}
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.
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