Before you install Intel® Packet Protect, install the network adapters on your servers and clients that will use Intel Packet Protect. Intel Packet Protect only operates with adapters that are configured to use Intel drivers. You must also configure PROSet II to enable IPSec before you begin to install Intel Packet Protect.
Intel Packet Protect works with Intel network adapters that are designed to offload CPU-intensive tasks to the adapter. This helps reduce the impact to network performance and CPU utilization.
The following Intel network adapters support offload capabilities:
Note: Intel Packet Protect also works with the following network adapters, but because encryption and authentication tasks will not offload to the adapter, system processor usage will be higher and actual transmission throughput may be lower:
Install Intel adapters for the servers and clients that use Intel Packet Protect.
Refer to the Installation Guide that came with the adapters for information about installation.
After installation, verify network access for each system that will use Intel Packet Protect by checking the Link and Activity LEDs on the adapter. You can also double-click Network Neighborhood on a system's desktop to verify that other areas of the network are visible.
NOTE: This procedure is necessary only when running Windows NT.
Close all running applications.
Open the control panel and select "Services".
Stop "Intel Policy Agent".
Open Network Properties and select the Adapters tab.
Click the Add button. Enter the path to the new Intel network driver software, and click "Continue".
Close the Network Properties window.
Configure the new adapter's network settings.
Close the Network Properties window and select reboot when the option is given.
NOTE: If communication fails after installing an additional network adapter, see the instructions in the Troubleshooting section.
After you install adapters in the systems that will use Intel Packet Protect, configure them, as necessary, before you install Intel Packet Protect. For example, you might install multiple adapters on a server. Then you might team those adapters together to take advantage of adapter fault tolerance or adaptive load balancing.
If you install multiple Intel network adapters in one system, note the following:
Any, all or none of the adapters may be configured to run with Intel Packet Protect.
Only Intel PRO/100 S adapters are capable of offloading encryption and authentication tasks.
Each system has only one security policy. This means that the same security settings will apply to all of the adapters in one system which are IPSec-enabled.
If you uninstall Intel Packet Protect, you lose all of your customized information, including rules and security actions. When you reinstall Intel Packet Protect, you will only have the single Default Rule in your System Policy.
Adapter Teaming and Intel Packet Protect work together only for systems running Windows NT, and only with Intel PRO/100 Server Adapters. You may have combinations of teamed and non-teamed adapters running Intel Packet Protect.
Note: If you team a PRO/100 S adapter (capable of hardware offloading) with an adapter that does not have this capability, the resulting team will not offload.
Before you can install Intel Packet Protect, you must configure PROSet II to
enable IPSec. This option also allows Intel Packet Protect to operate on the
adapter. If you have more than one adapter, you must enable IPSec on each
adapter which is going to use Intel Packet Protect. |
|||||
Follow these steps to enable IP Security:
If you decide to turn off the IPSec option for an adapter, Intel Packet Protect will be disabled on that adapter. |
|
Open the PROSet II control panel utility
Click the Advanced tab.
Click on the IPSec Server Mode option. Set it to Enabled.
Click OK.
More information on IPSec Server Mode is available in PROSet online help.
Copyright © 2001, Intel Corporation. All rights reserved.
Intel Corporation assumes no responsibility for errors or omissions in this document. Nor does Intel make any commitment to update the information contained herein.
* Other product and corporate names may be trademarks of other companies and are used only for explanation and to the owners' benefit, without intent to infringe.