HP ProLiant Essentials Intelligent Networking Pack Windows Edition User Manual

HP ProLiant Essentials Intelligent Networking Pack Windows Edition User Guide

Part Number 381655-00J March 2007 (Ninth Edition)

© Copyright 2007 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express

warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.

Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license.

Microsoft and Windows are U.S. registered trademarks of Microsoft Corporation. Windows Server 2003 is a trademark of Microsoft Corporation.

Audience assumptions

This document is for the person who installs, administers, and troubleshoots servers and storage systems. HP assumes you are qualified in the servicing of computer equipment and trained in recognizing hazards in products with hazardous energy levels.

Overview..................................................................................................................................... 4

HP ProLiant Essentials Intelligent Networking Pack Introduction........................................................................ 4

Intelligent Networking Pack licenses................................................................................................... 5

Using Virus Throttle ..................................................................................................................... 12

How Virus Throttle works.......................................................................................................................... 12

Installing Virus Throttle for Windows .......................................................................................................... 12

Monitoring Virus Throttle status.................................................................................................................. 13

Virus Throttle Status and Configuration Utility .............................................................................................. 16

Launching the Virus Throttle Status and Configuration Utility................................................................ 16

Configuring Virus Throttle parameters............................................................................................... 17

Using advanced networking features............................................................................................. 21

Configuring advanced features ................................................................................................................. 21

Configuring a Dual Channel team ................................................................................................... 23

Advanced Pack redundancy features .........................................................................................................25

Configuring Active Path Failover...................................................................................................... 27

Configuring Fast Path Failover......................................................................................................... 28

Configuring Router Path Failover ..................................................................................................... 29

Advanced Redundancy tab team members information....................................................................... 29

Configuring VLAN IDs.................................................................................................................... 30

Using discovery protocol ............................................................................................................. 32

About Cisco Discovery Protocol and Link Layer Discovery Protocol................................................................. 32

Configuring Discovery Protocols ...................................................................................................... 33

IGMP support............................................................................................................................. 35

Introduction to IGMP................................................................................................................................ 35

Troubleshooting.......................................................................................................................... 36

Potential solutions for INP configuration problems........................................................................................ 36

Installing an Intelligent Networking Pack license ................................................................................ 36

Using Virus Throttle........................................................................................................................ 37

Configuring advanced networking features....................................................................................... 37

Configuring Discovery Protocol ....................................................................................................... 39

Acronyms and abbreviations........................................................................................................ 41

Index......................................................................................................................................... 43

Contents 3

Overview

In this section

HP ProLiant Essentials Intelligent Networking Pack Introduction ...................................................................... 4

HP ProLiant Essentials Intelligent Networking Pack Introduction

The HP ProLiant Essentials Intelligent Networking Pack-Windows Edition is part of the ProLiant Essentials software family and is integrated with HP Systems Insight Manager (SIM), SmartStart, and HP Management agents.

The Intelligent Networking Pack (INP) provides advanced capabilities that allow servers to proactively adapt to networking infrastructure problems thus improving server availability and network performance. The Intelligent Networking Pack Windows Edition includes:

• Virus Throttle—a network packet-filtering feature that helps slow down the spread of viruses on your

system. Virus Throttle monitors all outbound connection requests and counts the number of unique connections. It detects abnormal ("virus-like") behavior in the requests, and slows down excessive connection requests to new hosts until you can determine if they are viral in nature and take action

• Advanced redundancy and teaming capabilities, including:

o Active Path Failover—an advanced redundancy feature that allows a ProLiant server to detect

blocked paths and to redirect data along an unblocked path to the core network.

o Fast Path Failover—an advanced redundancy feature that allows a ProLiant server to use the

quickest path to the core network (or the root bridge).

o Router Path Failover—an advanced redundancy feature that allows a ProLiant server to detect a

blocked path to a router and to redirect packets along an unblocked path to a router.

o Dual Channel Load Balancing—a special type of teaming that allows the creation of two teams,

called groups, inside of a single team. Each group is assigned one or more teamed ports and can be connected to a different switch to provide switch fault tolerance. Full inbound and outbound load balancing is provided across both groups. Should any group completely fail, caused by a failure of all teamed ports in the group or by a failure of the group's switch, the team remains available through the other group. Two types of Dual Channel Load Balancing teams can be configured: Switch-assisted Dual Channel Load Balancing teams and 802.3ad Dynamic Dual Channel Load Balancing teams.

o Dual Channel Network Fault Tolerance—a special type of teaming that allows the creation of two

teams, called groups, inside of a single team. All team members within each group are dynamically placed into a port-trunk/channel by dynamic Link Aggregation Control Protocol (LACP) agreement with the switch. A failure of a team member to synchronize joining a port-trunk or channel with the switch is treated as an error and that team member is considered failed. Dynamic Dual Channel Network Fault Tolerance (NFT) provides the safety of additional backup links between the server and hub/switch. Dynamic Dual Channel NFT is implemented with one channel team providing a primary adapter and another channel team providing a secondary,

Overview 4

backup adapter. During normal operations, if the adapters in the primary team fail, a link to one of the adapters in the secondary, backup team automatically takes over. Four types of Dual Channel NFT teams can be configured: Switch-assisted Dual Channel NFT teams, Switch-assisted Dual Channel NFT and Preference Order teams, 802.3ad Dynamic Dual Channel NFT teams, and 802.3ad Dynamic Dual Channel NFT and Preference Order teams.

NOTE: Dual Channel Network Fault Tolerance teaming capabilities are not supported on

systems running Windows® 2000.

• Cisco Discovery Protocol (CDP) support—a media- and protocol-independent network protocol that is

used to obtain protocol addresses of neighboring devices and discover the platform and other information of those devices.

• Link Layer Discovery Protocol (LLDP) support—a media- and protocol-independent network protocol

that is used to obtain protocol addresses of neighboring devices and discover the platform and other information of those devices.

• Internet Group Management Protocol (IGMP) support—IGMP is a session-layer (Layer-3) protocol

used to establish membership in a Multicast group. It can register a router to receive specific multicast traffic.

The INP features are included with the networking software (release 7.71 and higher). To enable the INP features, an INP license must be installed on the system. This user guide describes how to install these licenses on your system and how to configure the features.

For the latest driver, firmware, and documentation updates, go to HP Networking website (http://h18004.www1.hp.com/products/servers/networking/index.html

Intelligent Networking Pack licenses

Each server requires a separate INP license. When installed on the system, the license is "attached" to the server and cannot be revoked. The license will stay with that server for the life of the server. The license is associated with the server's serial number, so a change in the server's name or IP address will not invalidate the license. One INP license enables all INP features on the server.

Four categories of INP licenses are available. Each license offers full, unlimited functionality.

• Single license pack—Authorizes one licensed seat.

• Flexible Quantity license pack—Authorizes the set number of licensed seats ordered.

• Activation Key Agreement license pack—Allows you to authorize additional licensed seats under the

terms of a signed and implemented Activation Key Agreement (AKA) only.

Installing an Intelligent Networking Pack license

• Demo—Allows you to evaluate the features for a set number of seats and a set number of days

INP-Windows Edition licenses can be installed through the following:

• HP ProLiant Essentials Network License Manager, which can be launched through one of the

following:

o HP Network Configuration Utility (NCU) (release 7.71 and higher) o HP Virus Throttle for Windows Utility installation

• HP ProLiant Essentials Network License Manager (nalicense)

Overview 5

• HP ProLiant Essentials Network License Manager (vtlicense)

• HP Systems Insight Manager (SIM) License Manager Utility

Windows operating system requirements

Both the NCU and Virus Throttle utility require that the HP ProLiant system be running Microsoft®Windows® 2000, Microsoft Windows Server 2003, or Microsoft Windows Server 2003 x64.

Launching the license manager through the Network Configuration Utility

If the NCU software (release 7.71 and higher) is installed on your server, click License Manager on the NCU Main window to display the License Manager.

If the NCU software is not installed on your server, complete the following steps:

1. Go to the HP website (http://www.hp.com).

2. Click Software & Driver Downloads from the left menu bar.

3. Type the product name in the For product box and press Enter. For example, type NC370T.

4. Select your Operating System software.

5. Click HP ProLiant Networking Software.

6. Click download and save the HP SoftPaq (sp#####.exe) file to a directory on your hard drive. The

SoftPaq file is a self-extracting executable with a file name based on the SoftPaq number.

7. Click the SoftPaq file to extract the files and then open the cmponent.htm file.

8. Click the Network Teaming and Configuration link.

9. Install the component according to the directions. When the NCU is installed, the NCU tray icon

appears on the task bar of the Windows desktop.

Overview 6

10.

Click the NCU tray icon to display the NCU Main window.

11. Click License Manager to display the ProLiant Essentials Network License Manager. For information

on installing licenses refer to "About ProLiant Essentials Network License Manager (on page 8)."

Launching the license manager through the Virus Throttle installation

When you first install Virus Throttle the utility looks for a valid INP license on the system. If it does not find one, it automatically launches the ProLiant Essentials Network License Manager for you to enter a license key.

To install Virus Throttle and launch the ProLiant Essentials Network License Manager complete the following steps:

1. Go to the HP website (http://www.hp.com).

2. Click Software & Driver Downloads from the left menu bar.

3. Type the product name in the For product box and press Enter. For example, type NC370T.

4. Select your Operating System software.

5. Click HP ProLiant Networking Software.

6. Click download and save the HP SoftPaq (sp#####.exe) file to a directory on your hard drive. The

SoftPaq file is a self-extracting executable with a file name based on the SoftPaq number.

7. Click the SoftPaq file to extract the files and then open the cmponent.htm file.

Overview 7

Click the HP Virus Throttle link. If the utility does not identify a valid INP license on the system, the following message displays:

9. Click Yes to display the ProLiant Essentials Network License Manager. For information on installing

licenses refer to "About ProLiant Essentials Network License Manager (on page 8)."

NOTE: After the INP license is installed on the system, the Virus Throttle installation

automatically continues.

For additional information on Virus Throttle, refer to "Using Virus Throttle (on page 12)."

About ProLiant Essentials Network License Manager

The ProLiant Essentials Network License Manager allows you to enter new INP-Windows Edition licenses as well as view the status of other ProLiant Essentials licenses on your system.

Overview 8

The Currently installed licenses window displays the following information:

• Product Name—the name of the licensed networking product.

• Type—The license type.

o Single license pack—Authorizes one seat. Depending upon the type of product a seat may be a

single server (INP) or a single port (iSCSI Pack).

o Flexible quantity license pack—Authorizes a set number of seats ordered. o Activation Key Agreements (AKA) license pack—For use with signed and implemented (AKAs).

Allows you to activate additional seats under the terms of an existing AKA.

o Demo (For evaluation purposes only)—This trial license is provided for a set number of seats and

a set number of days.

• Seats Max—The total number of seats authorized for use by this key.

• Seats Used—The number of seats that are currently used.

• Days Max (Demo key only)—The total number of days authorized for use by this key.

• Days Left (Demo key only)—The number of days remaining for the license.

• License Key—The 25-digit license key string.

The Licensable devices window displays all devices that can be enabled. To enable or disable ports go to the NCU.

• Licensed and Unlicensed Devices—Enabled ports are displayed with a solid adapter icon and

disabled ports are displayed with a faded adapter icon.

• Non-port based licenses—When a non-port based license is selected in the Currently installed

licenses list, the Licensable devices list is disabled.

• License seat unavailable—If all seats for a given license have been used, a licensed port of the same

type must be disabled to make a license seat available to a different port or an additional license of the same product type with additional seats must be installed.

The following controls are available:

• Install License(s)—Opens the Install ProLiant Essentials License Key(s) dialog box.

• Export Licenses—Allows you to export currently installed licenses into a formatted license key file so

that you can easily move multiple licenses from one system to another.

• Close—Removes the License Manager dialog box from the screen.

• Help—Launches the License Manager Help file.

To install a license: You can install single or multiple license keys in the ProLiant Essentials Network License Manager window. To install a single license key:

Overview 9

From the ProLiant Essentials Network License Manager window, click Install License(s)… to display the Install ProLiant Essentials License Key(s) dialog box.

2. Select the Install a single license key option and enter the license key string. You may also copy the

license key from another source and paste it into the boxes.

3. Click Install. The license is displayed in the Currently installed licenses window.

To install multiple license keys from a key file:

1. From the ProLiant Essentials Network License Manager window, click Install License(s)….

2. Select the Install license keys from a file option and click Open License Key File....

3. Select the [filename].key file and click Open. A list of keys available for installation appears.

4. Select the license keys to install by clicking the check boxes. Selecting Invert selection reverses all

check box selections.

5. Click Install.

NOTE: HP recommends that you retain the license key for future reference. The key is needed

for technical support and future upgrades.

To export a license:

1. Click Export Licenses. The Save As dialog box appears.

2. Enter a license key filename called [filename].key and click Save. A text file is created.

3. Click Close. The NCU Main window appears.

Installing licenses using the nalicense

The HP ProLiant Essentials Network License Manager (nalicense), which ships with the NCU, is a Windows based command line utility and can be run at the command line of a Command Prompt window or from a Windows command file.

The nalicense command validates that the license is a proper INP license and if it is valid it adds it to the system. The nalicense command can also be used to display valid licenses on the system.

For information about the utility, refer to the HP ProLiant Essentials Network License Manager for Windows User Guide located on the HP website (http://www.hp.com

Overview 10

Installing licenses using vtlicense

The HP ProLiant Essentials Network License Manager (vtlicense), which ships with Virus Throttle, is a Windows-based command line utility that is run at a command line of a Command Prompt window or from a Windows command file.

The vtlicense command validates an INP license and then adds it to the system if it is valid. The vtlicense command also displays licenses currently installed on the system.

Installing licenses through HP Systems Insight Manager License Manager

HP recommends you use the SIM License Manager for concurrently installing and monitoring INP licenses on multiple servers. For information about SIM, go to the HP website (http://www.hp.com/go/hpsim

Overview 11

Using Virus Throttle

In this section

How Virus Throttle works......................................................................................................................... 12

Installing Virus Throttle for Windows......................................................................................................... 12

Monitoring Virus Throttle status ................................................................................................................ 13

Virus Throttle Status and Configuration Utility............................................................................................. 16

How Virus Throttle works

Viruses typically spread by connecting to as many different machines as possible. Virus Throttle is a network packet-filtering feature that monitors all outbound connection requests. Virus Throttle helps to stop the spread of viruses on your system by detecting abnormal "virus like" behavior in the requests. It slows down excessive connection requests to new hosts until you can determine if they are viral in nature and take action.

Virus Throttle allows the network infrastructure to stay up and running by slowing traffic on systems that exhibit high connection rates and frequent connections to new hosts.

When you install Virus Throttle on your system, the Virus Throttle network NDIS filter driver is inserted into all existing protocol-to-miniport bindings and all network traffic passes through it. Virus Throttle provides TCP and UDP support. The driver maintains a delay queue of connection requests for each instance of the network protocol stack and a list of known hosts that have established connections.

The driver examines all outbound connection requests and determines if the request is for a known host. If known, the request is passed down the protocol stack as a normal request. If unknown, the request is added to the delay queue. Periodically, the delay queue is examined and the oldest request is removed and passed down the protocol stack.

High and low water marks or pre-set thresholds are maintained for the delay queue and are used to determine when "virus-like" behavior is occurring or has stopped.

• High water mark—When the rate of connection requests exceeds the rate of the driver removing

them from the delay queue, a high water mark in the queue is exceeded and the driver indicates "virus-like" activity.

• Low water mark—When the rate of connection requests drops so that the number of queue entries

fall below a low water mark, the driver indicates that the "virus-like" activity has stopped.

When "virus-like" activity is detected or has stopped, Virus Throttle sends a Windows Management Instrumentation (WMI) event notification to the administrator. If HP Management agents are installed and configured correctly, a Simple Network Management Protocol (SNMP) trap warning is also sent to the administrator.

Installing Virus Throttle for Windows

To install Virus Throttle for Windows using the HP component pack executable file:

1. Go to the HP website (http://www.hp.com).

Using Virus Throttle 12

Click Software & Driver Downloads from the left menu bar.

3. Type the product name in the For product box and press Enter. For example, type NC370T.

4. Select an operating system.

5. Click HP Virus Throttle for Windows to download the HP Virus Throttle component pack

(cp######.exe) file. The component pack file is a self-extracting executable with a file name based on the component pack number.

6. Click the component pack executable file and follow the directions on the screen to install Virus

Throttle.

When installation is complete, the Virus Throttle tray icon appears in the Windows taskbar on the desktop. This icon is used to open the Virus Throttle Status and Configuration Utility.

To Install Virus Throttle for Windows using the HP cmponent.htm file:

1. Go to the HP website (http://www.hp.com).

2. Click Software & Driver Downloads from the left menu bar.

3. Type the product name in the For product box and press Enter. For example, type NC370T.

4. Select your Operating System software.

5. Click HP ProLiant Networking Software.

6. Click download and save the HP SoftPaq (sp#####.exe) file to a directory on your hard drive. The

SoftPaq file is a self-extracting executable with a file name based on the SoftPaq number.

7. Click the SoftPaq file to extract the files and then open the cmponent.htm file.

8. Click the HP Virus Throttle link. If a valid INP license is identified on the system, Virus Throttle

installation continues. If the utility does not identify a valid INP license on the system, the following message appears:

9. Click Yes to install a license key. The ProLiant Essentials Network License Manager appears. Refer to

"About ProLiant Essentials Network License Manager (on page 8)." After you install a license key on the system, the Virus Throttle installation continues automatically.

When installation is complete, the Virus Throttle tray icon appears in the Windows taskbar on the desktop. This icon is used to open the Virus Throttle Status and Configuration Utility.

Monitoring Virus Throttle status

The Status tab displays overall status, statistics, and delay queue information that has been captured since the Virus Throttle filter drivers were initialized. The filter drivers are initialized upon reboot and when any

Using Virus Throttle 13

configuration parameter is changed. Statistics and delay queue information can be viewed on the Status tab in either Aggregate (summary for all active instances of the Virus Throttle filter driver) or Individual (per instance) mode. The default setting is the Aggregate mode.

• Status. Displays the current state and the number of interfaces with virus-like activity since the Virus

Throttle filter drivers were initialized. The filter drivers are initialized upon reboot and when any configuration parameter is changed.

o No Virus-like activity is occurring. No virus-like activity is currently detected and none has been

detected since the filter drivers were initialized.

o Virus-like activity is not occurring, but has occurred in the past. No virus-like activity is currently

detected, but virus-like activity has been detected since the filter drivers were initialized.

o Virus-like activity is currently occurring! Virus-like activity is currently detected by at least one

instance of the filter drivers.

o Number of TCP Interfaces with Virus-Like Activity. The number of TCP interfaces that are currently

displaying virus-like activity.

• Number of UDP Interfaces with Virus-Like Activity. The number of UDP interfaces that are currently

displaying virus-like activity.

• TCP Statistics. Displays statistics on an aggregate or per-instance basis since the filter drivers were

initialized.

o Connection Establishing TCP Packets. Number of connection TCP packets seen since filter driver

initialization.

o TCP Packets Passed Without Delay. Number of connection TCP packets that were passed without

a delay because the target was a known host since filter driver initialization.

Using Virus Throttle 14

TCP Packets Placed on Queue. Number of connection TCP packets queued since filter driver initialization.

o TCP Packets Removed from Queue. Number of connection TCP packets removed from the delay

queue since filter driver initialization.

o Currently Queued TCP Packets. Number of connection TCP packets currently on the delay queue. o TCP Packets Dropped Due to Queue Overflow. Number of TCP packets that were dropped due to

the delay queue being full since filter driver initialization.

o Maximum TCP Packets on Queue. Maximum number of TCP packets on the queue since filter

driver initialization.

• Times TCP Virus-like Activity Seen. Number of times virus-like activity was detected since filter driver

initialization.

• UDP Statistics. Displays statistics on an aggregate or per-instance basis since the filter drivers were

initialized.

o Connection Establishing UDP Packets. Number of UDP connection packets seen since filter driver

initialization.

o UDP Packets Passed Without Delay. Number of UDP connection packets that were passed without

a delay because the target was a known host since filter driver initialization.

o UDP Packets Placed on Queue. Number of UDP connection packets queued since filter driver

initialization.

o UDP Packets Removed from Queue. Number of UDP connection packets removed from the delay

queue since filter driver initialization.

o Currently Queued UDP Packets. Number of UDP connection packets currently on the delay

queue.

o UDP Packets Dropped Due to Queue Overflow. Number of UDP packets that were dropped due

to the delay queue being full since filter driver initialization.

o Maximum UDP Packets on Queue. Maximum number of UDP packets on the queue since filter

driver initialization.

• Times UDP Virus-like Activity Seen. Number of times UDP virus-like activity was detected since filter

driver initialization.

• Information. Displays the current queue settings.

o TCP Delay Queue Size. The maximum number of TCP connection requests in the delay queue for

each instance.

o TCP Delay Queue High Water Mark. The number of TCP connection requests in the delay queue

where virus-like activity is indicated.

o TCP Delay Queue Low Water Mark. The number of TCP connection requests in the delay queue

below which virus-like activity is no longer indicated.

o UDP Delay Queue Size. The maximum number of UDP connection requests in the delay queue for

each instance.

o UDP Delay Queue High Water Mark. The number of UDP connection requests in the delay queue

where virus-like activity is indicated.

o UDP Delay Queue Low Water Mark. The number of UDP connection requests in the delay queue

below which virus-like activity is no longer indicated.

Controls

Using Virus Throttle 15

• Statistics Display Mode. Sets the type of values to be displayed.

o Aggregate. Displays a summary of all instances since driver initialization. o Individual. Displays values on a per-instance basis.

• License Manager. Opens the License Manager dialog box allowing you to add or view HP ProLiant

Essentials Network pack licenses.

• OK. Processes all changes made in the current session and closes the Virus Throttle Status and

Configuration Utility.

• Cancel. Cancels any selections made in the current session and closes the Virus Throttle Status and

Configuration Utility.

• Help. Launches the context-sensitive Help file.

Virus Throttle Status and Configuration Utility

The HP Virus Throttle Status and Configuration Utility allows you to view the status of "virus-like" activity and to configure parameters for the Virus Throttle filter driver.

When you first install Virus Throttle, the parameters for the filter driver are set to default settings. Any changes that you make to the Virus Throttle filter driver parameters are made to all active instances of the Virus Throttle filter driver.

When a new server adapter is installed on the system or a new team or VLAN is created, the Virus Throttle filter driver parameters for that interface are set to the default settings.

Each time the Virus Throttle Status and Configuration Utility is launched it looks for inconsistencies in the parameters for all the active instances of the filter driver. If one or more of the instances has inconsistent parameters, you are prompted to update the settings. For example, if the default parameters are changed

Launching the Virus Throttle Status and Configuration Utility

and then a new adapter is added, the parameters on the adapter will be inconsistent until the utility is run.

To launch the Virus Throttle Status and Configuration Utility complete the following steps:

1. Close the NCU (if it is open) because both utilities cannot be running at the same time.

2. Double-click the Virus Throttle tray icon located in the Windows taskbar. The Virus Throttle Status

and Configuration Utility verifies that the settings for all active instances of the filter driver are the same.

Using Virus Throttle 16

If no inconsistencies are detected in the filter driver parameters, the Status tab appears. The Status tab shows overall status, statistics, and delay queue information. Refer to "Monitoring Virus Throttle status."

If inconsistencies are found, the following message appears.

3. Click OK to display the Configuration tab. Update the current settings for all active instances of the

filter driver as needed. Refer to "Configuring Virus Throttle parameters (on page 17)."

Configuring Virus Throttle parameters

The Configuration tab shows the current delay queue and host settings and allows you to configure them for all active instances of the Virus Throttle filter driver. Parameters cannot be set for individual instances of the filter driver.

You can configure the following parameters:

• Delay Queue Size. Controls the maximum number of delayed TCP or UDP connection requests in the

queue for each instance of the filter driver. Requests over the queue size are dropped. The default setting is 200 delayed connection requests. The valid range is 1-1000.

Using Virus Throttle 17

• Delay Queue High Water Mark. Controls the number of TCP or UDP connection requests in the delay

queue at which "virus-like" activity is considered to be occurring for each instance of the filter driver. The default setting is 160 connection requests. The valid range is 1-Delay Queue Size.

• Delay Queue Low Water Mark. Controls the number of TCP or UDP connection requests in the delay

queue below which "virus-like" activity is considered to have stopped. The default setting is 100 connection requests. The valid range is 1-High Water Mark.

• Delay Period. Controls the rate at which TCP or UDP connection requests are removed from the

delay queue and passed down the protocol network stack. The default is 1 second. The valid range is 1-10 seconds.

• Host Working Set Size. Controls the number of known machines to which TCP or UDP connections

are established without delay. When a new connection is made, the oldest member of the working set is replaced with the new host. The default setting is 5 hosts. The valid range is 1-100.

• Address Lifetime (UDP). Number of timer intervals that an address will remain in the working set after

the last outbound UDP packet was sent to that address.

• Address Hint Lifetime (UDP). Number of timer intervals that an address is kept in the working set after

the last inbound UDP packet was received from that address.

• Max Slack (UDP).Maximum number of times new hosts are added to the working set per each timer

interval before adding to the delay queue.

The following controls are available:

• Restore Defaults—Restores all values to their default values.

• OK—Processes all changes made in the current session and closes the Virus Throttle Status and

Configuration Utility.

• Cancel—Cancels any selections made in the current session and closes the Virus Throttle Status and

Configuration Utility.

• Help. Launches the context-sensitive Help file.

How to configure Virus Throttle parameters

1. From the Configuration tab, modify the parameters as needed.

TCP and UDP options provide a selection for which protocol configuration settings are used.

Using Virus Throttle 18

The Keep Proportions option provides a way to keep the high and low water mark values at a preset percentage of the delay queue size for TCP and UDP outbound connection request. When Keep Proportions is not selected, the delay queue high and low water mark values can be changed. When Keep Proportions is selected, the delay queue high and low water mark values cannot be changed, and are automatically preset at 80% of the delay queue size for the high water mark and 50% of the delay queue size for the low water mark.

2. Click OK to save the settings. If you click Cancel and inconsistent settings needed to be changed, the

following message appears.

If you click Yes to this message, the utility closes and the inconsistent settings remain. If you click No, to this message the Configuration tab appears again.

Using Virus Throttle 19

When you click OK to process your changes, an informational message appears warning about a network interruption. Click Yes to start and stop the Virus Throttle instances so the new parameters can be read from the registry.

4. After the configuration is completed, a successful message appears. Click OK to close the Virus

Throttle Status and Configuration Utility.

Using Virus Throttle 20

Using advanced networking features

In this section

Configuring advanced features................................................................................................................ 21

Advanced Pack redundancy features........................................................................................................ 25

Configuring advanced features

With an INP-Windows Edition license installed on your system, you can enable six advanced teaming types:

• Switch-assisted Dual Channel Network Fault Tolerance

• Switch-assisted Dual Channel Network Fault Tolerance and Preference Order

• 802.3ad Dynamic Dual Channel Network Fault Tolerance

• 802.3ad Dynamic Dual Channel Network Fault Tolerance and Preference Order

• Switch-assisted Dual Channel Load Balancing

• 802.3ad Dynamic Dual Channel Load Balancing

You also can enable three advanced redundancy features:

• Active Path Failover

• Fast Path Failover.

• Router Path Failover

This section describes how to configure these advanced networking features through the NCU. You can also configure these features using the HP Network Adapter Scripting Utility. For information on how to use the scripting utility, refer to the HP Network Adapter Scripting Utility User Guide.

Advanced Pack teaming types The HP network adapter basic team types provide a selection of fault-tolerant and load-balancing

features, including Network Fault Tolerance (NFT), Transmit Load Balancing (TLB), and Switch-assisted Load Balancing (SLB).

Dual Channel Network Fault Tolerance

Dual Channel NFT provides the safety of additional backup-links between the server and hub/switch. It is implemented with one channel team providing a primary adapter and another channel team providing a secondary, backup adapter. During normal operations, if the adapters in the primary team fail, a link to one of the adapters in the secondary, backup team automatically takes over.

Four types of Dual Channel NFT teams can be configured:

• Switch-assisted Dual Channel NFT

• Switch-assisted Dual Channel NFT and Preference Order

• 802.3ad Dynamic Dual Channel NFT

• 802.3ad Dynamic Dual Channel NFT and Preference Order

Using advanced networking features 21

NOTE: Dual Channel Network Fault Tolerance teaming capabilities are not supported on

systems running Windows® 2000.

Switch-assisted Dual Channel NFT

Switch-assisted Dual Channel NFT requires a minimum of two adapters in a channel team and a minimum of one adapter per group. When you select Switch-assisted Dual Channel NFT, the Team Members window becomes team members grouping and displays two windows labeled Group 0 and Group 1.

Switch-assisted Dual Channel NFT and Preference Order Provides the same options as Switch-assisted Dual Channel Network Fault Tolerance except it offers the

additional option to select the priority order of the group (Group 0 or Group 1) used for the primary and secondary teams.

802.3ad Dynamic Dual Channel NFT

Dynamic Dual Channel NFT requires a minimum of two adapters in a channel team and a minimum of one adapter per group. All team members within each group are dynamically placed into a porttrunk/channel by dynamic LACP agreement with the switch. It provides the safety of additional backup links between the server and hub/switch. One channel team provides a primary adapter and another channel team provides a secondary, backup adapter. If the adapters in the primary team fail, a link to one of the adapters in the secondary, backup team automatically takes over.

802.3ad Dynamic Dual Channel NFT and Preference Order

Provides the same options as 802.3ad Dynamic Dual Channel NFT except it offers the additional option of setting the priority order of the adapters that are used in the primary and secondary teams.

Dual Channel Load Balancing Dual Channel Load Balancing allows the creation of two teams, called groups, inside of a single team.

Each group is assigned one or more teamed ports. Each group can also be connected to a different switch to provide switch fault tolerance. Full inbound and outbound load balancing is provided across both groups. Should any group completely fail, caused by a failure of all teamed ports in the group or by a failure of the group's switch, the team remains available through the other group.

Two types of Dual Channel Load Balancing teams can be configured:

• Switch-assisted Dual Channel Load Balancing teams

• 802.3ad Dynamic Dual Channel Load Balancing team

Switch-assisted Dual Channel Load Balancing teams The Switch-assisted Dual Channel Load Balancing team type allows you to define one group of team

members to be treated as a Switch-assisted Load Balancing (SLB) group to one switch, and a second group of team members to be treated as an SLB group to a second switch.

With Switch-assisted Dual Channel Load Balancing, all transmit packets are load balanced among all team members based on a load balancing algorithm in the teaming device driver. The receive packets are load balanced among all team members by both the switch and the team. If a failure of any team member occurs, the packets are load balanced among the remaining adapters.

There must be a minimum of two adapters in a Switch-assisted Dual Channel Load Balancing team with a minimum of one adapter in each group. Only Gigabit adapters can be used for Switch-assisted Dual Channel Load Balancing.

Using advanced networking features 22

Fast Path Failover, Active Path Failover, and Router Path Failover are available on Switch-assisted Dual Channel Load Balancing teams.

802.3ad Dynamic Dual Channel Load Balancing teams With 802.3ad Dynamic Dual Channel Load Balancing teams, team members are dynamically placed into

groups. All team members within each group are dynamically placed into a port trunk/channel by dynamic protocol agreement, Link Aggregation Control Protocol (LACP), with the switch. A failure of a team member to negotiate joining a port trunk or channel with the switch is treated as an error and that team member is considered failed.

All transmit packets are load balanced among all team members based on a load balancing algorithm in the teaming device driver. The receive packets are load balanced among all team members by the switch. If a failure of any team member occurs, the packets are load balanced among the remaining adapters.

There must be a minimum of two adapters in a dual channel team. Fast Path Failover, Active Path Failover, and Router Path Failover are available on 802.3ad Dynamic Dual Channel Load Balancing teams.

Configuring a Dual Channel team

To configure a Dual Channel team:

1. On the NCU Main window, select the team.

2. Click Properties. The Teaming Controls tab is displayed showing the team name, team type, transmit

load balancing method, and team members.

Using advanced networking features 23

A unique character string identifying this team displays in the Team Name box. This name displays as the device name in the Network and Dial-up Connections window and on the NCU Main window.

3. Select a Dual Channel team type from the Team Type Selection list.

Dual Channel team type options include:

o Switch-assisted Dual Channel Network Fault Tolerance o Switch-assisted Dual Channel Network Fault Tolerance and Preference Order o 802.3ad Dynamic Dual Channel Network Fault Tolerance o 802.3ad Dynamic Dual Channel Network Fault Tolerance and Preference Order o Switch-assisted Dual Channel Load Balancing or 802.3ad Dynamic Dual Channel Load Balancing

4. Select the Transmit Load Balancing Method for the team. Transmit Load Balancing methods include:

o Automatic (Recommended)—Default setting. Teaming driver selects the load balancing

mechanism based on the packet type.

o TCP Connection—Load balances transmitted TCP packets using the TCP connection information. o Destination IP Address—Load balances transmit IP packets using the last four bits of the

destination IP address.

o Destination MAC Address—Load balances transmit IP packets using the last four bits of the

destination MAC address.

o Round Robin—(Packet order not guaranteed). Load balances transmit packets among all team

members. A packet is sent on one team member, the next packet is sent out on the next team member, and so on. When the last team member is utilized, the rotation begins again.

5. If you select Switch-assisted Dual Channel Network Fault Tolerance or Switch-assisted Dual Channel

Load Balancing as the team type, the Team Members box is displayed with two sections labeled Group 0 and Group 1. Click the User Preference Order up and down arrows to assign the members to be in Group 0 and the members to be in Group 1. There must be a minimum of two adapters in a dual channel team with a minimum of one adapter in each group.

If you select 802.3ad Dynamic Dual Channel Network Fault Tolerance or 802.3ad Dynamic Dual Channel Load Balancing as the team type, the User Preference Order up and down arrows are disabled. Team members will be placed dynamically into groups.

If you select 802.3ad Dynamic Dual Channel Network Fault Tolerance and Preference Order you can select the preference order for the team.

If you select Switch-assisted Dual Channel Network Fault Tolerance and Preference Order, you can assign the members to be in Group 0 and the members to be in Group 1 and you can select the preference order for the group (Group 0 or Group 1)

Team Members information includes the following:

o Port Name—Displays the network adapter number, slot, and port location for the team member. o Status—Displays the status of the member within the context of the team. Not all status types

apply for every team type.

— Available—The team member is functioning normally. — Not Teamed—The adapter is not part of the team. The most likely cause is adding an

adapter to the team but not applying the change.

— Unknown—The team member's status could not be determined. — Wire Fault—The member does not have link.

Using advanced networking features 24

— Not Joined—The member cannot be joined in the team because it has an incompatible

setting. The most likely cause is changing a parameter for a team member using the local area connection property sheet.

— Degraded (Fast Path)—The team member and no other team members can receive Bridge

Protocol Data Units (BPDUs). Because all team members have equal Fast Path status, the team member is still in use by the team.

— Degraded (Active Path)—The team member and other team members cannot reach the echo

node. Because all team members have equal Active Path status, the team member is still in use by the team.

— Degraded (Rx Path)—The team member is not receiving packets, and no other team member

is receiving packets. Because all team members are equal, the team member is still in use by the team.

— Degraded (Multiple)—The team member has multiple degraded conditions. — Degraded (Router Path)—The team member and no other team members can receive router

protocol frames. Because all team members have equal router path status, the team member is still in use by the team.

— Failed (Active Path)—The member is not receiving replies from the configured echo node. — Failed (Split LAN:FP)—Team members are receiving BPDUs from different networks. — Failed (Fast Path)—No team member is receiving correct BPDUs. — Failed (LACP)—The team member failed to establish an LACP channel. — Failed (LACP Standby)—The team member has failed because the team has more members

than the switch supports in the LACP protocol. The port is blocked by the switch.

— Failed (Rx Path)—The team member is not receiving packets. — Failed (Tx Path)—A failure occurred while attempting to send a packet to the team member. — Failed (Multiple)—The team member has multiple failed conditions. — Failed (Router Path)—The team member is not receiving router protocol frames. — Failed (Split LAN: RP)—The team members are receiving router protocol frames from different

networks.

— Speed/Duplex—Displays the current speed/duplex setting of the team member.

6. Click OK to save all changes. The NCU Main window appears.

7. Click OK on the NCU Main window to apply changes.

Advanced Pack redundancy features

Basic redundancy features, standard with HP server adapter networking software, include link loss, transmit path validation, and receive path validation. These basic redundancy mechanisms monitor each teamed port for link, the ability to transmit a frame, and the ability to receive a frame.

Three advanced redundancy features, Active Path Failover, Fast Path Failover, and Router Path Failover are available through the INP. These features allow servers to proactively adapt to networking infrastructure problems.

These features are available for all team types except Switch assisted Load Balancing with Fault Tolerance (SLB) and 802.3ad Dynamic with Fault Tolerance teams.

Using advanced networking features 25

Active Path Failover

Active Path Failover allows a ProLiant server to predict and bypass failed network paths through use of a user assigned echo node. An echo node is a device on the network with which connectivity is required. Periodically, each team member transmits an Address Resolution Protocol (ARP) request packet to the echo node. If a response is not received from the echo node within a set timeout period, the team member is marked as failed.

If Active Path Failover is enabled, you must enter a valid IP address for the echo node. In addition, you can specify the MAC address of the echo node, which allows the echo node packets to be unicast to the echo node. If no Echo Node MAC address is provided, the echo node packets are broadcast.

Two types of echo node request probes are available:

• Community Address ARP-(Recommended) Community Address ARP is a newer method that uses a

standard ARP to test connectivity. It works for all devices designated as the echo node including routers, Hot Standby Routing Protocol (HSRP) devices, and Linux servers. If Community Address ARP is selected, you must enter the IP address to be used for the community probe. You can also configure the MAC address to be used, or use the default MAC address.

• Directed ARP-Directed ARP tests connectivity with the echo node device using a modified ARP frame.

This method works for most switches or servers that are designated as the echo node. It is not recommended for routers or Linux servers that are designated as the echo node.

Fast Path Failover

Fast Path Failover allows a ProLiant server to determine the fastest path to the core network (or the root bridge) in addition to detecting full connectivity loss. Fast Path Failover examines the path cost information contained in the Spanning Tree Bridge Protocol Data Unit (BPDU) frames and determines which switch is the best one to use for the team's primary port.

When configuring Fast Path Failover, you must select which Spanning Tree Protocol (STP) type to use. The two predominate STP types are as follows:

• IEEE 802.1D—Because IEEE 802.1D is VLAN unaware, it is not necessary to configure Fast Path

Failover to listen to VLAN.

• Cisco PVST+—Allows you to select the VLAN ID to be used for Fast Path Failover monitoring. (Refer

to "Configuring VLAN IDs.")

Router Path Failover

Router Redundancy Protocols (HSRP, VRRP) allow you to set up two or more routers into a single router group, which acts as a backup for a virtual router. At any given time, only one router is designated as the active router, which takes up the functionality of the router. If the active router fails, a second router or standby router assumes the role of the active router. If the standby router fails or becomes the active router, then another router is elected as the standby router.

The Router Path Failover ensures the team's connectivity to the active router. The router protocol, as selected by the user, defines the method used to select the active router by periodically exchanging multicast frames amongst routers in a router group. The NCU teaming software monitors these multicast frames to validate an active path to the active router in the router group.

When configuring Router Path Failover, you must select which router protocol to use. The two protocols available are as follows:

• HSRP—Cisco Hot Standby Router Protocol

• VRRP—Virtual Router Redundancy Protocol

Using advanced networking features 26

Configuring Active Path Failover

Active Path Failover is enabled through the Team Properties Advanced Redundancy tab. This feature is disabled if a valid INP license is not installed on the system.

To configure Active Path Failover for a team:

1. On the NCU Main window, select the team.

2. Click Properties to display the Team Properties window.

3. Select the Advanced Redundancy tab.

4. Select the Active Path Failover option to enable it. Active Path Failover allows a team member to

send a packet to a remote node (called the echo node) and receive a reply to determine that the team member sending the packet has a path to the node. The absence of a reply within the specified time period can be used to determine when a team member does not have a path to the echo node. The default setting is disabled. If Active Path Failover is enabled, you must enter a valid IP address for the echo node. Entering an Echo Node MAC address is optional.

5. Click the Echo Node Response Mechanism list and select the type of echo node request probe to be

sent.

o Community Address ARP-(Recommended) Tests connectivity using a standard ARP. This method

works for all devices designated as the echo node including routers, HSRP devices, and Linux servers. If Community Address ARP is selected, you must enter the IP address to be used for the community probe. You can also configure the MAC address to be used or use the MAC address default. The advantage of using Community Address ARP is that it works on all echo node types.

Using advanced networking features 27

Directed ARP-Tests connectivity with the echo node device using a modified ARP. This method works for most switches or servers that are designated as the echo node. It is not recommended for routers or Linux servers. The advantage of using Directed ARP is that less configuration of parameters is required.

6. In the Echo Node IP Address box type the IP address of the echo node.

7. Click the Echo Node Probe Interval list and select the interval at which packets are transferred to the

echo node. The default setting is 3 seconds.

8. (Optional) Type the MAC address of the echo node in the Echo Node MAC Address box. Providing

an echo node MAC address allows the echo node packets to be unicast to the echo node. If no echo node MAC address is provided, the echo node packets are broadcast.

9. In the Echo Node Probe Timeout box, select the maximum time to wait for a response from the echo

node before considering the team member failed. The default setting is 3 seconds. The timeout value must be less than or equal to the probe interval. If a larger value is entered for the timeout, it is automatically set to the probe interval when you click OK.

10. If Community Address ARP is the echo node response mechanism, type the IP address to be used in

the Community Probe IP Address box. This must be a valid and unique IP address on the same network as the team. All servers on the same network using this mechanism can have the same Community Probe IP address. This box is not used for Directed ARP probes.

11. Select the Use Default checkbox to use the default setting of 00-01-FA-FE-FE-FE or type the MAC

address in the Community Probe MAC Address box.

12. Click OK to save all changes and return to the NCU Main window. Or, click Cancel to ignore all

changes and return to the NCU Main window.

13. Click OK to apply the changes.

Configuring Fast Path Failover

Fast Path Failover is enabled through the Team Properties Advanced Redundancy tab. This feature is disabled if a valid INP license is not installed on the system.

To configure Fast Path Failover for a team:

1. On the NCU Main window, select the team.

2. Click Properties to display the Team Properties window.

3. Select the Advanced Redundancy tab.

4. Select the Fast Path Failover option. This allows the server to determine the fastest path to the core

network (root bridge).

5. Click the Spanning Tree Protocol and select the type.

o IEEE 802.1D—IEEE 802.1D MAC Layer Bridges is VLAN unaware so it is not necessary to

configure Fast Path Failover to listen to VLAN.

o Cisco PVST+—Cisco Per VLAN Spanning Tree Plus (Allows you to select the VLAN ID to be used

for Fast Path Failover monitoring.)

6. Click OK to save all changes and return to the NCU Main window. Or, click Cancel to ignore all

changes and return to the NCU Main window.

7. Click OK to apply the changes.

Using advanced networking features 28

Configuring Router Path Failover

Router Path Failover is enabled through the Team Properties Advanced Redundancy tab. This feature is disabled if a valid INP license is not installed on the system.

To configure Router Path Failover for a team:

1. On the NCU Main window, select the team.

2. Click Properties to display the Team Properties window.

3. Select the Advanced Redundancy tab.

4. Select the Router Path Failover option. This Router Redundancy Protocols (HSRP, VRRP) allow you to

set up two or more routers into a single router group, which acts as a backup for a virtual router.

5. Click the Router Protocol list and select the protocol type to monitor.

o HSRP-Cisco Hot Standby Router Protocol o VRRP-Virtual Router Redundancy Protocol

6. Type the router IP address in the Router IP Address box to identify the address of the router group

(also known as the virtual router IP address).

7. Click OK to save all changes and return to the NCU Main window. Or, click Cancel to ignore all

changes and return to the NCU Main window.

8. Click OK to apply the changes.

Advanced Redundancy tab team members information

Team Members window includes the following information:

• LAC. Displays the local area connection.

• Port Type. Displays the NC model number.

• Bus/Slot/Port. The bus, slot, and port location of the team member. A port location of 1 is not

reported and is left blank. The Team Members Bus/Slot/Port category changes to Bus/IO Bay/Port for HP BladeSystem servers.

• Status. Displays team member status: Refer to "Configuring a Dual Channel Load Balancing team".

• Router Path State. If Router Path is enabled, it displays the state: OK, Degraded, Failed, and Failed

(Split LAN); otherwise, the column is not displayed.

• Fast Path State. If Fast Path is enabled, it displays the state: OK, Degraded, Failed, and Failed (Split

LAN); otherwise, the column is not displayed.

• Active Path State. If Active Path is enabled, it displays the state: OK, Degraded, and Failed;

otherwise, the column is not displayed.

• User Ranking. Displays the current user ranking of the port when Network Fault Tolerance with

Preference Order or Transmit Load Balancing with Fault Tolerance and Preference Order is in use for the current team member; otherwise, the column is not displayed.

• Port/Path Cost. Displays the port/path cost for the port or "disconnected" if the adapter does not

have a link.

Using advanced networking features 29

Configuring VLAN IDs

If Active Path Failover, Fast Path Failover (with Cisco PVST+ set as the Spanning Tree Protocol), or Router Path Failover are configured for a team, you can select the VLAN ID for validation and monitoring.

Before creating and editing VLANs, you should be aware that:

• The NCU supports IEEE 802.1Q VLAN tagging only.

• The NCU supports a VLAN identifier range of 1 to 4094.

• Up to 64 VLANs can be defined for a team.

To create a VLAN for a team:

1. From the NCU Main window, select the team.

2. Click VLAN (802.1Q). The VLAN tab appears.

The VLAN tab shows all VLANs that currently exist for the team. The list includes both existing VLANs and new VLANs that have been created but that have not yet been applied. Newly created VLANs are applied by clicking OK on the Main window.

Using advanced networking features 30

To create a new VLAN, click Add. The VLAN properties input box appears.

4. Type a user-defined VLAN name. Every VLAN must have a name assigned to it. Duplicate names are

allowed if you want to use the same names for different VLAN IDs.

5. The next available VLAN ID appears in the VLAN ID box. Change the VLAN ID by either typing an

ID or by using the list to select a valid ID. A valid ID is any number that is not already being used for a VLAN defined on this team or adapter and that is in the range of 1-4094.

6. Click OK. The new VLAN is saved and the VLAN tab appears. The new VLAN you created appears

in the list on the VLAN tab.

7. Select from the following:

o Default/Native VLAN Id—Displays the VLAN ID to which all packets received without a VLAN

tag are sent. The "default" Default/Native VLAN is the lowest VLAN ID defined for the team at the time the team is created.

o Receive Path Validation VLAN Id—Allows you to select the VLAN on which receive path

validation frames will be transmitted. This control is enabled only when Receive Path Validation is enabled on the Team Settings tab. The default setting is the VLAN on the team with the lowest VLAN ID at the time the team is created.

o Active Path Failover VLAN Id—Allows you to select the VLAN ID to be used for the Active Path

Failover validation. This control is enabled only if Active Path Failover is configured for the team. The default setting is the VLAN on the team with the lowest VLAN ID at the time the team is created.

o Fast Path Failover VLAN Id—Allows you to select the VLAN ID to be used for the Fast Path

Failover monitoring. This control is enabled only if Fast Path Failover is configured for the team and Cisco PVST+ is set as the Spanning Tree Protocol. The default setting is the VLAN on the team with the lowest VLAN ID at the time the team is created.

o Router Path Failover VLAN Id—Allows you to select the VLAN ID to be used for Router Path

Failover monitoring. This control is enabled only if the Router Path Failover is configured for the team. Router Path Failover is not available for the following team types: Switch-assisted Load Balancing with Fault Tolerance (SLB) and 802.3ad Dynamic with Fault Tolerance.

8. Make any VLAN and VLAN ID changes then click OK. The new settings are saved and the NCU

Main window appears. Click OK on the Main window to apply the changes.

Using advanced networking features 31

Using discovery protocol

In this section

About Cisco Discovery Protocol and Link Layer Discovery Protocol ............................................................... 32

About Cisco Discovery Protocol and Link Layer Discovery Protocol

CDP and LLDP are layer two, neighbor device discovery protocols that run on all networking devices such as routers, access servers, bridges, and switches. Using CDP or LLDP, a device can advertise its existence to other devices and also receive information about neighboring devices on the same LAN or on the remote side of a WAN.

NOTE: LLDP is not supported on systems running Windows® 2000.

CDP and LLDP are media and protocol independent protocols that allow two systems to learn about each other even if they use different network layer protocols. CDP and LLDP obtain protocol addresses of neighboring devices and discover the platform of those devices including information about the interfaces a router uses. The HP NCU supports CDP Version 1, CDP Version 2, and LLDP.

The following information is provided by CDP Version 1, CDP Version 2 and LLDP:

• Protocol Type

• Device name

• Port ID

• Platform name of the device

• Type of device

The following information is provided only with CDP Version 2 and LLDP:

• VTP management domain name

• Native Vlan ID for untagged packets on the interface

• Duplex

Each team member configured for CDP or LLDP registers an address at which it can receive CDP or LLDP messages. The advertisements that come from network devices such as the switch will contain this information.

A network administrator can use the information from CDP or LLDP to build a basic picture of their network, which can be used to detect misconfigurations and troubleshooting problems on the network.

Using discovery protocol 32

Configuring Discovery Protocols

From the Discovery Protocols tab, you can configure CDP and LLDP settings for the selected team. These advanced teaming features are disabled unless a valid ProLiant Essentials Intelligent Networking Pack license is installed on the system. For more information on how to install a license, refer to "Installing an Intelligent Networking Pack license."

To access the Discovery Protocols tab for a team:

1. On the NCU main window, select a team.

2. Click Properties to display the Team Properties window.

3. Select the Discovery Protocols tab to display the Team Discovery Protocols tab.

4. In the Discovery Protocol Settings group select Enable CDPv1, Enable CDPv2, or LLDP to set the CDP

version or LLDP for which to listen.

5. Click OK to accept the settings and return to the NCU main window.

6. Click OK on the NCU main window to apply the settings.

Team Members—Team members are listed in order by Group ID and then by Team Member ID.

• LAC—The name of the local area connection.

• Port Type—NC model number of the port.

• Bus/Slot/Port. The bus, slot, and port location of the team member. A port location of 1 is not

reported and is left blank. The Team Members Bus/Slot/Port category changes to Bus/IO Bay/Port for HP BladeSystem servers.

Using discovery protocol 33

• Protocol Type—CDPv1, CDPv2, or LLDP

• Device ID—The device name.

• Port ID—The port on which the CDP or LLDP packet is sent.

• Platform—The hardware platform name of the device.

• Capabilities—The type of device.

o Unknown o Router o Transparent bridge o Source-routing bridge o Switch o Host o IGMP (Internet Group Management Protocol) Device o Repeater

• VTP Management Domain—The system's VTP management domain name. This is used to verify VTP

domain configuration in adjacent network nodes.

• Native Vlan ID—The VLAN for untagged packets on the interface. CDP or LLDP learns the native

VLAN for an interface. This is implemented only for interfaces that support the IEEE 8021Q protocol.

• Duplex—Current duplex mode of the team member: Unknown, Half, or Full.

The following controls are available:

• OK—Closes the window and returns the user to the Main window.

• Cancel—Closes the window and returns the user to the Main window.

• Help—Launches the context-sensitive NCU Help file.

Using discovery protocol 34

IGMP support

In this section

Introduction to IGMP............................................................................................................................... 35

Introduction to IGMP

Internet Group Management Protocol (IGMP) is used to register dynamic multicast group membership. It can register a router to receive specific multicast traffic. IGMP traffic will only be sent to those team members that are part of a multicast group.

When a server runs an application that wants to join a multicast group, the join message is sent out to the aggregation and only those ports in the multicast group. During a failover situation, the NCU will maintain connectivity with the multicast group and respond with IGMP reports.

The HP NCU supports IGMP in this release, but it does not require any user input in the NCU; therefore, no windows and controls exist.

IGMP support 35

Troubleshooting

In this section

Potential solutions for INP configuration problems ...................................................................................... 36

Potential solutions for INP configuration problems

This section provides possible solutions to problems that may occur during the configuration of INP features. The following tables provide steps to take before calling your service representative.

• Installing an Intelligent Networking Pack License—contains troubleshooting information about

installing an Intelligent Networking Pack license.

• Using Virus Throttle—contains troubleshooting information about using Virus Throttle.

• Configuring Advanced Networking Features—contains troubleshooting information about

configuring advanced networking features.

• Configuring Discovery Protocol—contains troubleshooting information about configuring discovery

protocols.

Installing an Intelligent Networking Pack license

Problem Possible cause Possible solution

The Intelligent Networking Pack license is installed but I cannot uninstall it.

This is correct behavior of ProLiant Essentials licensing.

After installed on the system, the license is "attached" to the server and cannot be revoked. The license stays with that server for the life of the server. The license is attached to the server serial number, so a change in server's name or IP address will not jeopardize the license.

N/A

Troubleshooting 36

Using Virus Throttle

Problem Possible cause Possible solution

The Virus Throttle Status and Configuration utility Status tab indicates that "virus-like" activity is occurring.

A virus has infected your server.

OR A non-virus program is

exhibiting "virus-like" behavior by making more connections to more unknown hosts than the Virus Throttle Configuration parameter settings.

In a time-sensitive manner, identify the program or programs responsible for the "virus-like" behavior.

If the program or programs is/are unknown, treat as a virus.

If the program or programs is/are known, then reconfigure the Virus Throttle Configuration parameters to not trigger on such normal or expected activity

Configuring advanced networking features

Problem Possible cause Possible solution

All members of the team currently have a yellow X with a status of "Degraded (Active Path)" and the team is degraded (yellow team icon).

The Automatic team type with Active Path Failover enabled team does not detect an echo node failure.

The INP license is installed but you cannot enable Active Path Failover on the team. It is disabled.

Degraded (Active Path) is a failure condition of the Active Path Failover mechanism. If all members of the team have a yellow X with a status of "Degraded (Active Path)," this means none of the members were able to reach the echo node device.

This may be expected behavior based on the configured settings.

Ensure the echo node device is on the same IP subnet as the team.

If the echo node device is not on the same IP subnet, reconfigure the echo node settings on the Advanced Redundancy tab for the team to a device that is on the same IP subnet. Retest with these settings.

If the echo node device is on the same IP subnet, can you ping the echo node? If no, check the echo node device to ensure it is operating and the IP information is correct.

If using VLANs, ensure the correct VLAN is chosen for the Active Path VLAN ID on the VLAN tab of the team.

Open the NCU and go to the Information tab for the team. Check the Current Mode.

If the current mode is 802.3ad Dynamic with Fault Tolerance, this is normal behavior to ignore the echo node mechanism. This mechanism will only be applicable if the automatic team type ends up in TLB (Transmit Load Balancing) mode.

Open the NCU and check to see if the team contains a 10/100 network adapter (NC31xx series). If so, remove the NC31xx series and apply changes before attempting to enable Active Path Failover. The NC31xx 10/100 adapters do not support the Active Path Failover mechanism.

Troubleshooting 37

Problem Possible cause Possible solution

The INP license is installed but you cannot enable Fast Path Failover on the team. It is disabled.

One or more members (but not all) of the team currently have a red X with a status of "Failed (Active Path)" and the team is degraded (yellow team icon).

The Active Path Mechanism is enabled and all adapters in the team show a yellow X with a status of "Degraded (Active Path)"; however, I can successfully ping the echo node device.

All members in the team show a yellow X with a status of "Degraded (Fast Path)"; however, the adapters are operating successfully.

When using the Fast Path mechanism with VLANS and PVST+, my adapters all show a yellow X with a status of "Degraded (Fast Path)"; however, the adapters are operating successfully.

When using the Router Path mechanism, all members in a team show a yellow X with a status of "Degraded (Router Path)"; however, all adapters are operating successfully.

This may be expected behavior based on the configured settings.

Failed (Active Path) is a failure condition of the Active Path Failover mechanism. If one or more members (but not all) of the team have a red X with a status of "Failed (Active Path)," this means those members did not receive a response from the echo node device during the last interval.

If using the Directed ARP method and the echo node device is a router or a Linux server, this is expected behavior.

The Spanning Tree Protocol may be disabled on the switches or the wrong protocol may be selected on the Advanced Redundancy tab of the team.

The Native VLAN of the switch may not match what is configured on the VLAN tab of the team in the Default/Native VLAN box.

The router protocol type or the router IP address may be set wrong.

The Default/Native VLAN ID and the Router Path VLAN ID do not match when the ports on the switch have not been tagged to any VLAN.

Open the NCU and go to the Information tab for the team. Check the Current Mode.

If the current team mode is 802.3ad Dynamic with Fault Tolerance or SLB (Switch-assisted Load Balancing), this is normal behavior. These team modes do not support Fast Path Failover.

First, ensure that there are no split LAN conditions possibly caused by an upstream link failure to the core network.

Second, if there are no split LAN conditions, go to the Advanced Redundancy tab for the team. Set the timers under Active Path Failover to a greater value. Possibly the timers are set too low for the network environment. Try doubling the current timers and retest with these settings.

Change the Active Path Mechanism to Community Address ARP. This newer method works with all devices as the echo node. It requires an additional IP address for the Community ARP; however, all servers on the network using this feature can use this address.

Ensure the Spanning Tree Protocol is running on the switches in the network.

Ensure the protocol selected on the Advanced Redundancy tab is the same protocol running on the switches in the network. Only PVST+ and 802.1D are supported.

Ensure the Native VLAN of the switch is the same as the Default/Native VLAN configured in the NCU on the VLAN tab of the team. For example, if the Native VLAN on the ports you are connected to is VLAN 20, then ensure the VLAN tab of the team is configured for VLAN 20 on the Default//Native VLAN box.

Ensure the Router Protocol setting is configured for the correct protocol and verify the Router IP Address entry.

Ensure that the Default VLAN ID and Router Path VLAN ID are the same in the NCU.

Troubleshooting 38

Problem Possible cause Possible solution

Unable to select VLAN ID for Active Path, Fast Path, and Router Path.

This may be expected behavior based on the configured settings.

Go to Advanced Redundancy Tab and enable the failover mechanism such as Active Path Failover or Fast Path Failover or Router Path Failover for which you are unable to set VLAN ID.

Open the NCU and go to the Information tab for the team. Check the Current Mode. If the current team mode is 802.3ad Dynamic with Fault Tolerance or SLB (Switch-assisted Load Balancing), this is normal behavior. These team modes do not support Fast Path Failover, Active Path Failover and Router Path Failover.

If you are unable to set the VLAN ID for fast path even though Fast Path has been selected in the Advanced Redundancy tab, then consider changing the Spanning Tree Protocol as Cisco PVST+.

Configuring Discovery Protocol

Problem Possible cause Possible solution

When using CDPv1 the information tab does not display the VTP management domain name for my devices.

The Discovery Protocol Settings group is disabled and I can't set the CDP or LLDP.

CDP or LLDP is enabled and CDP or LLDP frames are being transmitted by the network device but they are not being received by the team.

This is expected behavior when using CDPv1. This feature is only available with CDPv2.

This is expected behavior for licensable features.

When CDP or LLDP is first enabled, it may take 30 seconds to receive the first CDP or LLDP frame. It is possible that this delay occurred as the teaming driver attempted to register the CDP or LLDP multicast address with the miniport. This delay may have caused the team to fail to register the multicast address.

If this information is important to you, consider using CDPv2 instead.

Install a ProLiant Essentials Intelligent Networking Pack license key

Disable CDP or LLDP then re-enable it and verify that the team registers the address.

Troubleshooting 39

Problem Possible cause Possible solution

When using SLB, 802.3ad, and Dual-Channel teams some ports in my aggregation (trunk) do not have any information displayed.

Some network devices may only transmit a CDP or LLDP frame down a single port in a trunk. In that case, you should expect that the data from the port that is receiving the frame should represent all ports in that aggregation.

If two ports in an aggregation happen to contain different data (like different Device IDs) that may alert you to a network misconfiguration.

Map your network configuration using Discovery Protocol and verify the configuration is satisfactory.

Troubleshooting 40

Acronyms and abbreviations

ARP

Address Resolution Protocol

BPDU

Bridge Protocol Data Unit

CDP

Cisco Discovery Protocol

HSRP

Hot Standby Routing Protocol

IGMP

Internet Group Management Protocol

Internet Protocol

LACP

Link Aggregation Control Protocol

LAN

local-area network

LLDP

Link Layer Discovery Protocol

MAC

medium access control

NCU

Network Configuration Utility

NDIS

network driver interface specification

Acronyms and abbreviations 41

NFT

network fault tolerant

NIC

network interface controller

SIM

Systems Insight Manager

SLB

switch-assisted load balancing

SNMP

Simple Network Management Protocol

STP

Spanning Tree Protocol

TCP

Transmission Control Protocol

TLB

transmit load balancing

UDP

User Datagram Protocol

VLAN

virtual local-area network

WMI

Windows Management Instrumentation

Acronyms and abbreviations 42

Index

configuring a dual channel load balancing team 23 configuring active path failover 27 configuring fast path failover 28 configuring router path failover 29 configuring VLAN IDs 29

discovery protocol 32

IGMP support 35 installing virus throttle 12

ProLiant Essentials Intelligent Networking Pack 4

troubleshooting 36

Virus Throttle status and configuration utility 16 Virus Throttle, defined 12

Windows operating systems 6

Index 43

HP ProLiant Essentials Intelligent Networking Pack Windows Edition User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual

HP ProLiant Essentials Intelligent Networking Pack Windows Edition User Guide

Contents

Overview

HP ProLiant Essentials Intelligent Networking Pack Introduction

Intelligent Networking Pack licenses

Installing an Intelligent Networking Pack license

Windows operating system requirements

Launching the license manager through the Network Configuration Utility

Launching the license manager through the Virus Throttle installation

About ProLiant Essentials Network License Manager

Installing licenses using the nalicense

Installing licenses using vtlicense

Installing licenses through HP Systems Insight Manager License Manager

Using Virus Throttle

How Virus Throttle works

Installing Virus Throttle for Windows

Monitoring Virus Throttle status

Virus Throttle Status and Configuration Utility

Configuring Virus Throttle parameters

How to configure Virus Throttle parameters

Using advanced networking features

Configuring advanced features

Configuring a Dual Channel team

Advanced Pack redundancy features

Configuring Active Path Failover

Configuring Fast Path Failover

Configuring Router Path Failover

Advanced Redundancy tab team members information

Configuring VLAN IDs

Using discovery protocol

About Cisco Discovery Protocol and Link Layer Discovery Protocol

Configuring Discovery Protocols

IGMP support

Introduction to IGMP

Troubleshooting

Potential solutions for INP configuration problems

Installing an Intelligent Networking Pack license

Using Virus Throttle

Configuring advanced networking features

Configuring Discovery Protocol

Acronyms and abbreviations

Index