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

Specifying the source IP address for outgoing RADIUS packets, communicate with any server.

Page 36 highlights

If the quiet timer of a server expires or you manually set the server to the active state, the status of the server changes back to active, but the device does not check the server again during the authentication or accounting process. If no server is found reachable during one search process, the device considers the authentication or accounting attempt a failure. • If you remove an authentication or accounting server in use, the communication of the device with the server soon times out, and the device looks for a server in active state by first checking the primary server, and then checking secondary servers in the order they are configured. • When the primary server and secondary servers are all in blocked state, the device does not communicate with any server. • If one server is in active state and all the others are in blocked state, the device only tries to communicate with the server in active state, even if the server is unavailable. • If the status of a RADIUS server changes automatically, the device changes the status of this server accordingly in all RADIUS schemes in which this server is specified. By default, the device sets the status of all RADIUS servers to active. In some cases, however, you must change the status of a server. For example, if a server fails, you can change the status of the server to blocked to avoid communication attempts to the server. To set the status of RADIUS servers: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter RADIUS scheme view. radius scheme radius-scheme-name N/A • Set the status of the primary RADIUS authentication server: state primary authentication { active | block } • Set the status of the primary RADIUS Configure at least one command. accounting server: state primary accounting { active | By default, every server block } specified in a RADIUS scheme • Set the status of a secondary RADIUS is in active state. 3. Set the RADIUS server status. authentication server: state secondary authentication The configured server status cannot be saved to any [ ip-address [ port-number | configuration file, and can vpn-instance vpn-instance-name ] * ] only be viewed by using the { active | block } display radius scheme • Set the status of a secondary RADIUS accounting server: command. After the device restarts, all servers are state secondary accounting restored to the active state. [ ip-address [ port-number | vpn-instance vpn-instance-name ] * ] { active | block } Specifying the source IP address for outgoing RADIUS packets The source IP address of RADIUS packets that a NAS sends must match the IP address of the NAS configured on the RADIUS server. A RADIUS server identifies a NAS by its IP address. Upon receiving a RADIUS packet, a RADIUS server checks whether the source IP address of the packet is the IP address of a managed NAS. If yes, the server processes the packet. If not, the server drops the packet. 27

  • 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

27
If the quiet timer of a server expires or you manually set the server to the
active
state, the status of
the server changes back to
active
, but the device does not check the server again during the
authentication or accounting process.
If no server is found reachable during one search process, the device considers the authentication
or accounting attempt a failure.
If you remove an authentication or accounting server in use, the communication of the device with
the server soon times out, and the device looks for a server in
active
state by first checking the
primary server, and then checking secondary servers in the order they are configured.
When the primary server and secondary servers are all in
blocked
state, the device does not
communicate with any server.
If one server is in
active
state and all the others are in
blocked
state, the device only tries to
communicate with the server in
active
state, even if the server is unavailable.
If the status of a RADIUS server changes automatically, the device changes the status of this server
accordingly in all RADIUS schemes in which this server is specified.
By default, the device sets the status of all RADIUS servers to
active
. In some cases, however, you must
change the status of a server. For example, if a server fails, you can change the status of the server to
blocked
to avoid communication attempts to the server.
To set the status of RADIUS servers:
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 status.
Set the status of the primary RADIUS
authentication server:
state
primary
authentication
{
active
|
block
}
Set the status of the primary RADIUS
accounting server:
state
primary
accounting
{
active
|
block
}
Set the status of a secondary RADIUS
authentication server:
state
secondary
authentication
[
ip-address
[
port-number
|
vpn-instance
vpn-instance-name
] *
]
{
active
|
block
}
Set the status of a secondary RADIUS
accounting server:
state
secondary
accounting
[
ip-address
[
port-number
|
vpn-instance
vpn-instance-name
] *
]
{
active
|
block
}
Configure at least one
command.
By default,
every server
specified in a RADIUS scheme
is in
active
state.
The configured server status
cannot be saved to any
configuration file, and can
only be viewed by using the
display radius scheme
command. After the device
restarts, all servers are
restored to the
active
state.
Specifying the source IP address for outgoing RADIUS packets
The source IP address of RADIUS packets that a NAS sends must match the IP address of the NAS
configured on the RADIUS server. A RADIUS server identifies a NAS by its IP address. Upon receiving a
RADIUS packet, a RADIUS server checks whether the source IP address of the packet is the IP address of
a managed NAS. If yes, the server processes the packet. If not, the server drops the packet.