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

Setting the username format and traffic statistics units

Page 43 highlights

Setting the username format and traffic statistics units A username is typically in the format userid@isp-name, where isp-name represents the user's ISP domain name. By default, the ISP domain name is included in a username. However, some HWTACACS servers do not recognize usernames that contain ISP domain names. In this case, you can configure the device to remove the domain name from each username to be sent. If you want two or more ISP domains to reference the same HWTACACS scheme, configure that HWTACACS scheme to keep the ISP domain name in usernames for domain identification. The device reports online user traffic statistics in accounting packets. The traffic measurement units are configurable, but they must be the same as configured on the HWTACACS accounting servers. To set the username format and traffic statistics units for an HWTACACS scheme: Step 1. Enter system view. 2. Enter HWTACACS scheme view. 3. Set the format of usernames sent to the HWTACACS servers. 4. (Optional.) Set the data flow and packet measurement units for traffic statistics. Command system-view hwtacacs scheme hwtacacs-scheme-name Remarks N/A N/A user-name-format { keep-original | By default, the ISP domain name with-domain | without-domain } is 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. Specifying the source IP address for outgoing HWTACACS packets The source IP address of HWTACACS packets that a NAS sends must match the IP address of the NAS configured on the HWTACACS server. An HWTACACS server identifies a NAS by IP address. Upon receiving an HWTACACS packet, an HWTACACS 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. The source address of outgoing HWTACACS packets is typically the IP address of an egress interface on the NAS to communicate with the HWTACACS server. In some cases, however, you must change the source IP address. For example, if the NAS is configured with the VRRP for stateful failover, the source IP address of outgoing HWTACACS packets can be the virtual IP address of the uplink VRRP group. You can specify the source IP address for outgoing HWTACACS packets in HWTACACS scheme view for a specific HWTACACS scheme, or in system view for all HWTACACS schemes whose servers are in a VPN or the public network. Before sending an HWTACACS packet, the NAS selects a source IP address in the following order: 1. The source IP address specified for the HWTACACS scheme. 2. The source IP address specified in system view for the VPN or public network, depending on where the HWTACACS server resides. 3. The IP address of the outbound interface specified by the route. To specify a source IP address for all HWTACACS schemes of a VPN or the public network: 34

  • 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

34
Setting the username format and traffic statistics units
A username is typically in the format
userid
@
isp-name
, where
isp-name
represents the user's ISP domain
name. By default, the ISP domain name is included in a username. However, some HWTACACS servers
do not recognize usernames that contain ISP domain names. In this case, you can configure the device
to remove the domain name from each username to be sent.
If you want two or more ISP domains to reference the same HWTACACS scheme, configure that
HWTACACS scheme to keep the ISP domain name in usernames for domain identification.
The device reports online user traffic statistics in accounting packets. The traffic measurement units are
configurable, but they must be the same as configured on the HWTACACS accounting servers.
To set the username format and traffic statistics units for an 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.
Set the format of usernames
sent to the HWTACACS
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.
Specifying the source IP address for outgoing HWTACACS packets
The source IP address of HWTACACS packets that a NAS sends must match the IP address of the NAS
configured on the HWTACACS server. An HWTACACS server identifies a NAS by IP address. Upon
receiving an HWTACACS packet, an HWTACACS 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.
The source address of outgoing HWTACACS packets is typically the IP address of an egress interface on
the NAS to communicate with the HWTACACS server. In some cases, however, you must change the
source IP address. For example, if the NAS is configured with the VRRP for stateful failover, the source IP
address of outgoing HWTACACS packets can be the virtual IP address of the uplink VRRP group.
You can specify the source IP address for outgoing HWTACACS packets in HWTACACS scheme view for
a specific HWTACACS scheme, or in system view for all HWTACACS schemes whose servers are in a
VPN or the public network.
Before sending an HWTACACS packet, the NAS selects a source IP address in the following order:
1.
The source IP address specified for the HWTACACS scheme.
2.
The source IP address specified in system view for the VPN or public network, depending on where
the HWTACACS server resides.
3.
The IP address of the outbound interface specified by the route.
To specify a source IP address for all HWTACACS schemes of a VPN or the public network: