HP NC326m HP ProLiant Essentials Intelligent Networking Pack - Windows Edition - Page 37

Using Virus Throttle, Configuring advanced networking features, Problem, Possible cause

Page 37 highlights

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 In a time-sensitive manner, identify the server. program or programs responsible for the OR "virus-like" behavior. A non-virus program is If the program or programs is/are unknown, exhibiting "virus-like" behavior treat as a virus. by making more connections If the program or programs is/are known, to more unknown hosts than then reconfigure the Virus Throttle the Virus Throttle Configuration parameters to not trigger on Configuration parameter such normal or expected activity settings. Configuring advanced networking features Problem Possible cause Possible solution All members of the team Degraded (Active Path) is a Ensure the echo node device is on the same IP currently have a yellow X failure condition of the Active subnet as the team. with a status of "Degraded Path Failover mechanism. If all If the echo node device is not on the same IP (Active Path)" and the team is members of the team have a subnet, reconfigure the echo node settings on degraded (yellow team icon). yellow X with a status of the Advanced Redundancy tab for the team to "Degraded (Active Path)," this a device that is on the same IP subnet. Retest means none of the members with these settings. were able to reach the echo node device. 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. The Automatic team type with This may be expected Active Path Failover enabled behavior based on the team does not detect an echo configured settings. node failure. 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. The INP license is installed This may be expected but you cannot enable Active behavior based on the Path Failover on the team. It configured settings. is disabled. 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

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43

Troubleshooting 37
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).
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.
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.
The Automatic team type with
Active Path Failover enabled
team does not detect an echo
node failure.
This may be expected
behavior based on the
configured settings.
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.
The INP license is installed
but you cannot enable Active
Path Failover on the team. It
is disabled.
This may be expected
behavior based on the
configured settings.
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.