HP Carrier-grade cc3300 Intel Server Management (ISM) Installation and User&am - Page 81

Table 8-1., Native Command Line Request to BMC, Table 8-2., Native Command Line Request from BMC

Get HP Carrier-grade cc3300 PDF manuals and user guides View all HP Carrier-grade cc3300 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 81 highlights

Each native command line message must be preceded with the left bracket start character and must be ended with a right bracket stop character and the configured input newline sequence. No input characters are accepted until the start character has been received. Native command line text commands are case sensitive, but hex-ASCII commands can use either upper or lower case letters for ASCII representations of hex digits. Native command line messages are limited to a maximum length of 122 characters. This includes the left and right brackets, but not control characters. The only characters allowed are standard printable ASCII characters. All other characters are treated as illegal, except the following special characters. If the BMC receives an illegal character it clears the message in progress and goes back to looking for the start character. Special Characters ESC-You can use the ESC character to delete an entire message prior to submission to the BMC. If line editing is enabled, and the ESC key is followed by an input newline sequence, the BMC responds by outputting an output newline sequence. Otherwise, following an ESC, the BMC goes back to looking for the start character. Special Character Handling-character Del or Backspace-Use the Del or Backspace key to delete the last character entered if the message has not yet been submitted to the BMC. Backslash Newline-Split long IPMI messages across multiple lines by using the line continuation backslash character followed immediately by an input newline sequence. Line continuation characters are supported for both text and hex-ASCII commands. Hex-ASCII Command Format Binary IPMI commands are sent and received as a series of case insensitive hex-ASCII pairs, where each is optionally separated from the preceding pair by a single space character. Following is an example of a binary IPMI request message: [18 00 22] The software ID and LUN for the remote console are fixed and implied by the command. The SWID for messages to the remote console is always 47h, and the Logical Unit Number (LUN) is 00b. Instead, there is a bridge field that is used to identify whether the message should be routed to the BMC's bridged message tracking or not. This data is described in the following tables. Table 8-1. Native Command Line Request to BMC Byte 1 2 3 4:N Explanation [7:2] - Net Function (even) [1:0] - Responder's LUN [7:2] - Requester's Sequence Number [1:0] - Bridge field Command Number Data Table 8-2. Native Command Line Request from BMC Byte Explanation

  • 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
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
Each native command line message must be preceded with the left bracket start character and must be
ended with a right bracket stop character and the configured input newline sequence. No input characters
are accepted until the start character has been received.
Native command line text commands are case sensitive, but hex-ASCII commands can use either upper or
lower case letters for ASCII representations of hex digits.
Native command line messages are limited to a maximum length of 122 characters. This includes the left
and right brackets, but not control characters.
The only characters allowed are standard printable ASCII characters. All other characters are treated as
illegal, except the following special characters. If the BMC receives an illegal character it clears the message
in progress and goes back to looking for the start character.
Special Characters
ESC—You can use the ESC character to delete an entire message prior to submission to the BMC. If line
editing is enabled, and the ESC key is followed by an input newline sequence, the BMC responds by
outputting an output newline sequence. Otherwise, following an ESC, the BMC goes back to looking for the
start character.
Special Character Handling—character
Del or Backspace—Use the Del or Backspace key to delete the last character entered if the message has not
yet been submitted to the BMC.
Backslash Newline—Split long IPMI messages across multiple lines by using the line continuation
backslash character followed immediately by an input newline sequence. Line continuation characters are
supported for both text and hex-ASCII commands.
Hex-ASCII Command Format
Binary IPMI commands are sent and received as a series of case insensitive hex-ASCII pairs, where each is
optionally separated from the preceding pair by a single space character. Following is an example of a binary
IPMI request message:
[18 00 22]<newline sequence>
The software ID and LUN for the remote console are fixed and implied by the command. The SWID for
messages to the remote console is always 47h, and the Logical Unit Number (LUN) is 00b. Instead, there is a
bridge field that is used to identify whether the message should be routed to the BMC’s bridged message
tracking or not. This data is described in the following tables.
Table 8-1.
Native Command Line Request to BMC
Byte
Explanation
1
[7:2] - Net Function (even)
[1:0] - Responder’s LUN
2
[7:2] - Requester’s Sequence Number
[1:0] - Bridge field
3
Command Number
4:N
Data
Table 8-2.
Native Command Line Request from BMC
Byte
Explanation