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

Setting HWTACACS timers, Command, Remarks, Server response timeout timer, response-timeout, blocked

Page 44 highlights

Step 1. Enter system view. 2. Specify a source IP address for outgoing HWTACACS packets. Command system-view hwtacacs nas-ip { ipv4-address | ipv6 ipv6-address } [ vpn-instance vpn-instance-name ] Remarks N/A By default, the IP address of the HWTACACS packet outbound interface is used as the source IP address. To specify a source IP address for a specific HWTACACS scheme: Step 1. Enter system view. 2. Enter HWTACACS scheme view. 3. Specify a source IP address for outgoing HWTACACS packets. Command system-view hwtacacs scheme hwtacacs-scheme-name nas-ip { ipv4-address | ipv6 ipv6-address } Remarks N/A N/A By default, the device uses the IP address specified by the hwtacacs nas-ip command in system view as the source IP address. If no IP address is specified, the device uses the IP address of the HWTACACS packet outbound interface as the source IP address. Setting HWTACACS timers The device uses the following timers to control the communication with an HWTACACS server: • Server response timeout timer (response-timeout)-Defines the HWTACACS server response timeout timer. The device starts this timer immediately after an HWTACACS authentication, authorization, or accounting request is sent. If the device does not receive a response from the server after the timer expires, it sets the server to blocked and sends the request to another HWTACACS server. • Real-time accounting timer (realtime-accounting)-Defines the interval for the device to send real-time accounting updates to the HWTACACS accounting server for online users. To implement real-time accounting, the device must periodically send real-time accounting packets for online users to the accounting server. • Server quiet timer (quiet)-Defines the duration to keep an unreachable server in blocked state. If a server is not reachable, the device changes the server's status to blocked, starts this timer for the server, and tries to communicate with another server in active state. After the server quiet timer expires, the device changes the status of the server back to active. The status of HWTACACS servers controls the HWTACACS servers with which the device communicates when the current servers are no longer available. You can specify one primary HWTACACS server and multiple secondary HWTACACS servers, with the secondary servers functioning as the backup of the primary servers. Typically, the device chooses servers based on the following 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 35

  • 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

35
Step
Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Specify a source IP address
for outgoing HWTACACS
packets.
hwtacacs nas-ip
{
ipv4-address
|
ipv6
ipv6-address
}
[
vpn-instance
vpn-instance-name
]
By default, the IP address of the
HWTACACS packet outbound
interface is used as the source IP
address.
To specify a source IP address for a specific HWTACACS scheme:
Step
Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Enter HWTACACS
scheme view.
hwtacacs scheme
hwtacacs-scheme-name
N/A
3.
Specify a source IP
address for outgoing
HWTACACS packets.
nas-ip
{
ipv4-address
|
ipv6
ipv6-address
}
By default, the device uses the IP address
specified by the
hwtacacs nas-ip
command in system view as the source IP
address. If no IP address is specified, the
device uses the IP address of the
HWTACACS packet outbound interface as
the source IP address.
Setting HWTACACS timers
The device uses the following timers to control the communication with an HWTACACS server:
Server response timeout timer
(
response-timeout
)—Defines the HWTACACS server response
timeout timer. The device starts this timer immediately after an HWTACACS authentication,
authorization, or accounting request is sent. If the device does not receive a response from the
server after the timer expires, it sets the server to
blocked
and sends the request to another
HWTACACS server.
Real-time accounting timer
(
realtime-accounting
)—Defines the interval for the device to send
real-time accounting updates to the HWTACACS accounting server for online users. To implement
real-time accounting, the device must periodically send real-time accounting packets for online
users to the accounting server.
Server quiet timer
(
quiet
)—Defines the duration to keep an unreachable server in
blocked
state. If
a server is not reachable, the device changes the server's status to
blocked
, starts this timer for the
server, and tries to communicate with another server in
active
state. After the server quiet timer
expires, the device changes the status of the server back to
active
.
The status of HWTACACS servers controls the HWTACACS servers with which the device communicates
when the current servers are no longer available. You can specify one primary HWTACACS server and
multiple secondary HWTACACS servers, with the secondary servers functioning as the backup of the
primary servers. Typically, the device chooses servers based on the following 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