Using Virus Throttle; Configuring Advanced Networking Features - HP NC320m - PCI Express Gigabit Server Adapter User Manual

Proliant essentials intelligent networking pack windows edition
Hide thumbs Also See for NC320m - PCI Express Gigabit Server Adapter:
Table of Contents

Advertisement

Using Virus Throttle

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

Configuring advanced networking features

Problem
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.
Possible cause
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.
Possible cause
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.
This may be expected
behavior based on the
configured settings.
Possible solution
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
Possible solution
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

Advertisement

Table of Contents
loading

Table of Contents