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

 Condition: This symptom occurs if the Layer-3 subinterface or Layer-3 aggregate

subinterface are created before the two cards enter synchronization state.

 Workaround: Configure the two cards to enter synchronization state, and then create

the Layer-3 subinterface or Layer-3 aggregate subinterface.

HSD110063

 Symptom: When configuration synchronization is enabled between the active and

standby SecBlade cards, new physical interface type configuration on the active card

cannot be synchronized to the standby card.

 Condition: This symptom can be seen when configuration synchronization is enabled

between the active and standby SecBlade cards.

 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 R3819P05

201403140300

 Symptom: The SecBlade card unexpectedly reboots.

 Condition: This symptom can be seen when IPsec requires the CPU to generate a

random number during SA negotiation.

Resolved problems in R3819P01

201401140211

 Symptom: The SecBlade card fails to start up.

 Condition: This symptom occurs when the card is tested in an ESS (Environment Stress

Screen) low temperature lab.