HP VPN Firewall Module Series - HP SECBLADEIII-CMW520-R3819 Release Notes

 Workaround: Manually modify the interface type configuration on the standby card.

HSD100621

 Symptom: After the attack defense settings configured at the CLI are removed from the Web

interface and then the SecBlade card is rebooted, the attack defense settings still take effect.

 Condition: This symptom can be seen after the attack defense settings configured at the CLI

are removed from the Web interface and then the SecBlade card is rebooted.

 Workaround: Remove the attack defense settings at the CLI.

HSD113033

 Symptom: The SecBlade card might reboot when a display command with a regular expression

(for example, display current-configuration | include .*.*.*/.) is executed to display a

configuration file that exceeds 100 KB.

 Condition: This symptom occurs if a display command with a regular expression (for example,

display current-configuration | include .*.*.*/.) is executed to display a configuration file that

exceeds 100 KB.

 Workaround: When the configuration file is larger than 100 KB, do not use any regular

expression, or use a regular expression that does not include "*" or includes few "*".

List of resolved problems

Resolved problems in R3819

201308300271

 Symptom: A PC running Win7 obtains an incorrect DNS server address from the DHCP server

on the SecBlade card.

 Condition: This symptom occurs if multiple DHCP address pools are configured, and the PC's

MAC address is bound to a static address pool on the SecBlade card.

201308290004

 Symptom: The SecBlade card unexpectedly reboots during a CRL acquisition operation.

 Condition: This symptom occurs if the CRL acquisition operation is performed when the

memory usage exceeds 95% because of large amounts of TCP and UDP traffic.

201309100016

 Symptom: The SecBlade card unexpectedly reboots when multiple voice NQA operations that

have the same source but different destinations are configured.

 Condition: This symptom occurs when multiple voice NQA operations that have the same

source but different destinations are configured.

201309040150

 Symptom: An inter-zone policy can never be matched.

 Condition: This symptom occurs if the following conditions exist:

 There are two inter-zone policies that have the same information except for their bound

content filtering policies.

 The inter-zone policy that can never be matched has a lower match priority.