Intel SE7525GP2 Product Specification - Page 116

Host to mBMC Communication Interface, 2.4.5, LAN Interface

Page 116 highlights

Platform Management Intel® Server Boards SE7320SP2 and SE7525GP2 5.2.4.4 Host to mBMC Communication Interface The host communicates with the mBMC via the System Management Bus (SMBus). The interface consists of three signals: ƒ SMBus clock signal (SCLH) ƒ SMBus data signal (SDAH) ƒ Optional SMBus alert signal (SMBAH). The signal notifies the host that the PC87431x has data to provide. The mBMC is a slave device on the bus. The host interface is designed to support polled operations. Host applications can optionally handle an SMBus alert interrupt if the mBMC is unable to respond immediately to a host request. In this case, "Not Ready" is indicated in one of two ways: ƒ The host interface bandwidth is limited by the bus clock and mBMC latency. To meet the device latency, the mBMC slows down the bus periodically by extending the SMBus clock low interval (SCLH). ƒ If the mBMC is in the middle of a LAN or peripheral device communication, or if a response to the host request is not yet ready, the mBMC does not acknowledge the device address ("NAK"). This forces the host software to stop and restart the session. For more information on read-write through SMBus, see the System Management Bus (SMBus) Specification 2.0. 5.2.4.5 LAN Interface The server board supports one DPC LAN interface via a UDP port 26Fh. The mBMC supports a maximum of one simultaneous session across all authenticated channels. The server board implements gratuitous ARP support according to the IPMI 1.5 Specification. The IPMI Specification v1.5 defines how IPMI messages, encapsulated in RMCP packet format, can be sent to and from the mBMC. This capability allows a remote console application to access the mBMC and perform the following operations: ƒ Chassis control, e.g., get chassis status, reset chassis, power-up chassis, power-down chassis ƒ Get system sensor readings ƒ Get and Set system boot options ƒ Get Field Replaceable Unit (FRU) information ƒ Get System Event Log (SEL) entries ƒ Get Sensor Data Records (SDR) ƒ Set Platform Event Filtering (PEF) ƒ Set LAN configurations 104 Revision 4.0

  • 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
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184

Platform Management
Intel® Server Boards SE7320SP2 and SE7525GP2
Revision 4.0
104
5.2.4.4
Host to mBMC Communication Interface
The host communicates with the mBMC via the System Management Bus (SMBus). The
interface consists of three signals:
SMBus clock signal (SCLH)
SMBus data signal (SDAH)
Optional SMBus alert signal (SMBAH). The signal notifies the host that the PC87431x
has data to provide.
The mBMC is a slave device on the bus. The host interface is designed to support polled
operations. Host applications can optionally handle an SMBus alert interrupt if the mBMC is
unable to respond immediately to a host request. In this case, “Not Ready” is indicated in one of
two ways:
The host interface bandwidth is limited by the bus clock and mBMC latency. To meet the
device latency, the mBMC slows down the bus periodically by extending the SMBus
clock low interval (SCLH).
If the mBMC is in the middle of a LAN or peripheral device communication, or if a
response to the host request is not yet ready, the mBMC does not acknowledge the
device address (“NAK”). This forces the host software to stop and restart the session.
For more information on read-write through SMBus, see the
System Management Bus
(SMBus)
Specification 2.0.
5.2.4.5
LAN Interface
The server board supports one DPC LAN interface via a UDP port 26Fh. The mBMC supports a
maximum of one simultaneous session across all authenticated channels. The server board
implements gratuitous ARP support according to the IPMI 1.5 Specification.
The IPMI Specification v1.5 defines how IPMI messages, encapsulated in RMCP packet format,
can be sent to and from the mBMC. This capability allows a remote console application to
access the mBMC and perform the following operations:
Chassis control, e.g., get chassis status, reset chassis, power-up chassis, power-down
chassis
Get system sensor readings
Get and Set system boot options
Get Field Replaceable Unit (FRU) information
Get System Event Log (SEL) entries
Get Sensor Data Records (SDR)
Set Platform Event Filtering (PEF)
Set LAN configurations