HP 3PAR InForm OS Common Criteria Administrator's Reference (QL226-96586, October 2012)

31 Documentation Errata

prior to pasting it into the setsshkey command. If the private key material is not

available on a given host, password authentication will still allow the user to connect. This

would be the same if the key was pre-pended with from= and access was attempted from

a different IP address even if the private key was available.

The Note following the setsys CLI command MgmtOldPorts parameter is missing the

“NOTE” identifier and also incorrectly includes the EventLogSize parameter within the

Note text (i.e., unintended text was included in the Note). The Note should indicate the

following (with allowances for formatting):

setsys CLI command MgmtOldPorts parameter (p. 333)

NOTE

The server must be restarted for changes made to the MgmtOldPorts parameter to take

effect.

Following the Note is the EventLogSize parameter description:

EventLogSize <value>

Sets the size of the event log. The default value is 3 MB. When the event log is full, older

events are deleted in order to retain this setting.

E-Class/F-Class Physical Planning Manual

This section incorrectly references the P10000 instead of the F-Class.

Common Criteria Evaluated Configuration (p. 17)

This section should include a Note that indicates the Service Processor is not part of the

evaluated configuration and refer the reader to the Common Criteria Administrator’s

Reference for more information.

Planning Network Access (p. 48)

This section indicates that there are three supported topologies – shared, split, and

private. This is incorrect – only shared and private are supported.

Supported Network Topologies (p. 48)

There is a Note at the top of the page containing three items. The second Note indicates

that when implementing HP 3PAR Remote Copy interfaces, the service processor should

not be assigned to the same subnet. This is incorrect. Remote Copy interfaces should

always be on a private network segment or VPN – they should never be implemented on a

shared segment or intermingled with administrative traffic.

Note, 2

item (p.50)