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 the EtherExpress PROSet II utility to enable IPSec before you begin to install Intel Packet Protect.
Intel Packet Protect works with Intel adapters that are designed to offload CPU-intensive tasks to the adapter. This helps reduce the impact to network performance and CPU utilization. Network adapters that support the offload capabilities include the following:
Note: Intel Packet Protect also works with the following adapters, but security tasks will not offload to these adapters, and network performance will be affected.
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.
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 adapters in one system, note the following:
Install multiple adapters before installing Intel Packet Protect. If Intel Packet Protect is already installed and you are adding an additional adapter, you do not need to uninstall Intel Packet Protect. Add the adapter(s), load the drivers, and enable Intel Packet Protect on the new adapters using the PROSet II control panel.
Each system has only one security policy. This means that the same security settings will apply to all of the adapters in one system.
If you use at least one Intel PRO/100 S Server or Management Adapter in a system, Intel Packet Protect will be able to offload encryption and authentication tasks to that adapter.
If you need to add or remove an adapter from a team after you install Intel Packet Protect, you must uninstall Intel Packet Protect from that system, add or remove the necessary adapters, and then reinstall Intel Packet Protect.
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 with Windows NT operating system installed. If you set up Adapter Teaming for multiple adapters, keep the following in mind:
Configure Adapter Teaming before installing Intel Packet Protect.
Refer to the previous page to make sure all adapters in the team are either offload-enabled Intel adapters, or appear in the list of compatible Intel adapters on the previous page.
If you need to add or remove an adapter from a team after you install Intel Packet Protect, you must uninstall Intel Packet Protect from that system, add or remove the necessary adapters, and then re-install Intel Packet Protect.
Consider using high-speed adapters to limit upgrading.
You must configure the EtherExpress PROSet II utility to enable IPSec before you can install Intel Packet Protect.
Open PROSet II. You can open PROSet II from the Control Panel or by clicking the yellow key icon in your system tray.
In the left-side window, locate the Network Components folder.
Right-click on the name of the adapter that you wish to use.
Select Enable IPSec in the popup window.
You must reboot your system when prompted.
Copyright © 2000, 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.