HP Moonshot 1500 Chassis User Manual Page 94

  • Download
  • Add to my manuals
  • Print
  • Page
    / 189
  • Table of contents
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 93
Table 59 SOL configuration parameters
Parameter Data (non-volatile unless otherwise noted)
1
#Parameter
Data 1 - This parameter is used to indicate when any of the following parameters
are being updated, and when the updates are completed. The bit is primarily
0Set In Progress (volatile)
provided to alert software that some other software or utility is in the process of
making changes to the data.
An implementation can also elect to provide a rollback feature that uses this
information to decide whether to roll back to the previous configuration
information, or to accept the configuration change.
If used, the roll back restores all parameters to their previous state. Otherwise,
the change takes effect when the write occurs.
Reserved[7:2]
Set complete. If a system reset or transition to powered
down state occurs while set in progress is active, the MC
00b =[1:0]
goes to the set complete state. If rollback is implemented,
going directly to set complete without first doing a commit
write causes any pending write data to be discarded.
Set in progress. This flag indicates that some utility or
other software is presently doing writes to parameter data.
01b =
It is a notification flag only, it is not a resource lock. The
MC does not provide any interlock mechanism that would
prevent other software from writing parameter data.
Commit write (optional). This is only used if a rollback is
implemented. The MC saves the data that has been written
10b =
since the last time it was set in progress and then goes to
the set in progress state. An error completion code will
be returned if this option is not supported.
Reserved11b =
Byte 1:1SOL enable
Reserved[7:1]
SOL enable. This controls whether the SOL payload type
can be activated. Whether an SOL stream can be
[0]
established is also dependent on the access mode and
authentication settings for the corresponding LAN channel.
The enabled/disabled state and access mode settings for
the serial/modem channel have no effect on SOL.
Enable SOL payload1b =
Disable SOL payload0b =
Byte 1: SOL authentication enable2SOL authentication
Force SOL payload encryption[7]
Force encryption. If the cipher suite for the session supports
encryption, this setting forces the use of encryption for all
SOL payload data.
1b:
Encryption controlled by remote console. Whether SOL
packets are encrypted or not is selected by the remote
0b:
console at the time the payload is activated (using the
activate payload command) and can be changed
during operation via the suspend/resume payload
encryption command.
Force SOL payload authentication[6]
94 Command specification
Page view 93
1 2 ... 89 90 91 92 93 94 95 96 97 98 99 ... 188 189

Comments to this Manuals

No comments