ProCurve 800, Руководство по настройке

Страница: 52 / 406

1-40
Overview of the ProCurve NAC 800
Deployment Methods
• Mirroring deployment
–
Port 1
—to any port in your production network, determining the
location just as you would for any RADIUS server
– Port 2 —to a port that can receive mirrored DHCP traffic
Unless your network devices support remote mirroring, this port
should be on the same switch to which the DHCP server connects.
2. Give the NAC 800 an IP address in the appropriate VLAN.
3. On the authenticators (switch, APs, and so forth), specify the NAC 800’s
IP address as one of the RADIUS servers.
4. Determine the source of credentials and take any steps necessary to allow
the NAC 800 to access this source:
• NAC 800’s local database —ProCurve Networking recommends
that you always use IDM to configure the local database.
See “Configure Authentication to the NAC 800’s Local Database” on
page 4-14 of Chapter 4: “Configuring the RADIUS Server—Integrated
with ProCurve Identity Driven Manager.”
• Proxy RADIUS server —Add the NAC 800 to the proxy server’s
client list.
Set up the NAC 800 as described in “Configure Authentication to a
Proxy RADIUS Server” on page 4-30 of Chapter 4: “Configuring the
RADIUS Server—Integrated with ProCurve Identity Driven Manager”
or “Configure Authentication to a Proxy RADIUS Server” on page 5-23
of Chapter 5: “Configuring the RADIUS Server—Without Identity
Driven Manager.”
• Active Directory (AD), OpenLDAP, or eDirectory —In the
NAC 800’s Web browser interface, bind it to the directory.
If using IDM, see “Configure Authentication to a Windows Domain”
on page 4-16 or “Configure Authentication to an LDAP Server” on page
4-20 of Chapter 4: “Configuring the RADIUS Server—Integrated with
ProCurve Identity Driven Manager.”
If not using IDM, see “Configure Authentication to a Windows
Domain” on page 5-10 or “Configure Authentication to an LDAP
Server” on page 5-14 of Chapter 5: “Configuring the RADIUS
Server—Without Identity Driven Manager.”