H3c-technologies H3C SecPath F1000-E Manual de usuario Pagina 201
- Pagina / 273
- Tabla de contenidos
- SOLUCIÓN DE PROBLEMAS
- MARCADORES
Valorado. / 5. Basado en revisión del cliente
191
Configuring the IP address of the security policy server
The core of the H3C EAD solution is integration and cooperation, and the security policy server is the
management and control center. Using a collection of software, the security policy server provides
functions such as user management, security policy management, security status assessment, security
cooperation control, and security event audit.
The NAS checks the validity of received control packets and accepts only control packets from known
servers. To use a security policy server that is independent of the AAA servers, you must configure the IP
address of the security policy server on the NAS. To implement all EAD functions, configure both the IP
address of the IMC security policy server and that of the IMC Platform on the NAS.
To configure the IP address of the security policy server for a scheme:
Ste
p
Command
Remarks
1. Enter system view.
system-view N/A
2. Enter RADIUS scheme
view.
radius scheme radius-scheme-name N/A
3. Specify a security policy
server.
security-policy-server ip-address
No security policy server is
specified by default.
NOTE:
You can specify up to eight security policy servers for a RADIUS scheme.
Configuring interpretation of RADIUS class attribute as CAR parameters
According to RFC 2865, a RADIUS server assigns the RADIUS class attribute (attribute 25) to a RADIUS
client. However, the RFC only requires the RADIUS client to send the attribute to the accounting server on
an "as is" basis. It does not require the RADIUS client to interpret the attribute. Some RADIUS servers use
the class attribute to deliver the assigned committed access rate (CAR) parameters. In this case, the
access devices must interpret the attribute to implement user-based traffic monitoring and controlling. To
support such applications, configure the access devices to interpret the class attribute as the CAR
parameters.
To configure the firewall to interpret the RADIUS class attribute as CAR parameters:
Ste
p
Command
Remarks
1. Enter system view.
system-view N/A
2. Enter RADIUS scheme view.
radius scheme
radius-scheme-name
N/A
3. Interpret the class attribute as
CAR parameters.
attribute 25 car
By default, RADIUS attribute 25 is not
interpreted as CAR parameters.
NOTE:
W
hether
interpretation of RADIUS class attribute as CAR parameters is supported depends on two factors:
• Whether the firewall supports CAR parameters assignment.
• Whether the RADIUS server supports assigning CAR parameters through the class attribute.
Enabling the trap function for RADIUS
With the trap function, a NAS sends a trap message when either of the following events occurs:
- Preface 3
- Obtaining documentation 4
- Technical support 5
- Documentation feedback 5
- Contents 6
- Configuring ACLs 11
- Match order 12
- ACL rule numbering 13
- IPv4 ACL acceleration 13
- Configuration task list 14
- Creating an ACL 14
- Configuring a basic ACL rule 15
- Configuring ACL acceleration 21
- ACL configuration example 21
- Creating a time range 22
- Defining an ACL 22
- ACL configuration task list 25
- Configuring a basic ACL 26
- Configuring an advanced ACL 27
- Copying an ACL 30
- Configuring security zones 34
- Zone configuration task list 35
- Creating a zone 35
- Configuring a zone member 36
- Zone ID Display the zone ID 37
- Zone configuration example 38
- Configuration consideration 39
- HTTP configuration example 45
- Creating a basic ACL 46
- HTTPS configuration example 49
- Creating a PKI domain 50
- Generating an RSA key pair 51
- Adding a local user 53
- Address resource overview 55
- Exporting configuration 62
- Exporting configurations 68
- Importing configurations 69
- Interzone policy overview 73
- Enable Syslog 93
- Function 93
- Managing sessions 95
- 3. Click Apply 98
- Clearing sessions 108
- Overview 109
- Network requirements 110
- Configuring the host 110
- Configuring the SecPath 110
- Configuration guidelines 112
- Configuring ASPF 113
- ASPF configuration example 114
- Configuration procedure 115
- Verifying the configuration 120
- Authentication client 123
- Access device 123
- Portal server 123
- Security policy server 123
- Portal authentication mode 124
- Configuration prerequisites 127
- Logging off portal users 136
- SecPathHost 138
- RADIUS server 138
- { Name: newpt 147
- { IP address: 192.168.0.111 147
- { Key: portal 147
- { Port number: 50100 147
- Configuration considerations 153
- Troubleshooting portal 158
- Configuring AAA 159
- Client/server model 160
- RADIUS packet format 162
- Extended RADIUS attributes 164
- HWTACACS 165
- Domain-based user management 167
- AAA across VPNs 168
- Protocols and standards 169
- RADIUS attributes 169
- Configuring AAA at the CLI 172
- Configuring AAA schemes 174
- Command 176
- Remarks 176
- Configuring SecPath 189
- Creating a RADIUS scheme 192
- Creating an HWTACACS scheme 204
- Configuring HWTACACS server 205
- Item Descri 207
- Telnet user 209
- HWTACACS server 209
- 10.1.1.1/24 209
- Creating an ISP domain 219
- AAA configuration examples 226
- $enab1$ pass1 1 239
- $enab2$ pass2 2 239
- $enab3$ pass3 3 239
- Troubleshooting AAA 254
- Troubleshooting HWTACACS 256
- Configuring password control 257
- { Digits 0 to 9 259
- Configuring FIPS 268
- FIPS self-tests 269
- Conditional self-tests 270
- Triggering a self-test 270
- Task Command 271
- A C D E F I L O P S T V Z 272
Relacionado con productos y manuales para La Seguridad H3c-technologies H3C SecPath F1000-E
(234 paginas)
(17 paginas)© 2020, manymanuals.es. Todos los derechos reservados | 0.058 s |
Manymanuals.com
Manymanuals.de
Manymanuals.fr
Manymanuals.it
Manymanuals.pl
Manymanuals.cz
Manymanuals.es
Manymanuals-pt.com
Comentarios a estos manuales