Intel S1200RP Technical Product Specification - Page 67

Systems Management Architecture for Server Hardware - Command Line Protocol SMASH

Page 67 highlights

Intel® Server Board S1200V3RP Platform Management Functional Overview configured by Router Advertisements from the local router. The IP, Prefix, and Gateway are read-only parameters to the BMC user in this mode.  Stateless auto-config: The Prefix and Gateway are configured by the router through Router Advertisements. The BMC derives its IP in two parts: the upper network portion comes from the router and the lower unique portion comes from the BMC's channel MAC address. The 6-byte MAC address is converted into an 8-byte value per the EUI64* standard. For example, a MAC value of 00:15:17:FE:2F:62 converts into a EUI-64 value of 215:17ff:fefe:2f62. If the BMC receives a Router Advertisement from a router at IP 1:2:3:4::1 with a prefix of 64, it would then generate for itself an IP of 1:2:3:4:215:17ff:fefe:2f62. The IP, Prefix, and Gateway are read-only parameters to the BMC user in this mode. IPv6 can be used with the BMC's Web Console, JViewer* (remote KVM and Media), and Systems Management Architecture for Server Hardware - Command Line Protocol (SMASHCLP) interface (ssh). There is no standard yet on how IPMI RMCP or RMCP+ should operate over IPv6 so that is not currently supported. 6.11.3.4 LAN Failover The BMC FW provides a LAN failover capability so that the failure of the system HW associated with one LAN link will result in traffic being rerouted to an alternate link. This functionality is configurable using IPMI methods as well as the BMC's Embedded UI, allowing for user to specify the physical LAN links constitute the redundant network paths or physical LAN links constitute different network paths. BMC supports only an all or nothing approach - that is, all interfaces bonded together, or none are bonded together. The LAN Failover feature applies only to BMC LAN traffic. It bonds all available Ethernet devices but only one is active at a time. When enabled, if the active connection's leash is lost, one of the secondary connections is automatically configured so that it has the same IP address. Traffic immediately resumes on the new active connection. The LAN Failover enable/disable command may be sent at any time. After it has been enabled, standard IPMI commands for setting channel configuration that specify a LAN channel other than the first will return an error code. 6.11.3.5 BMC IP Address Configuration Enabling the BMC's network interfaces requires using the Set LAN Configuration Parameter command to configure LAN configuration parameter 4, IP Address Source. The BMC supports this parameter as follows:  1h, static address (manually configured): Supported on all management NICs. This is the BMC's default value.  2h, address obtained by BMC running DHCP: Supported only on embedded management NICs. IP Address Source value 4h, address obtained by BMC running other address assignment protocol, is not supported on any management NIC. Attempting to set an unsupported IP address source value has no effect, and the BMC returns error code 0xCC, Invalid data field-in request. Note that values 0h and 3h are no longer supported, and will return a 0xCC error completion code. Revision 1.0 55

  • 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
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262

Intel® Server Board S1200V3RP
Platform Management Functional Overview
configured by Router Advertisements from the local router. The IP, Prefix, and Gateway
are read-only parameters to the BMC user in this mode.
Stateless auto-config
: The Prefix and Gateway are configured by the router through
Router Advertisements. The BMC derives its IP in two parts: the upper network portion
comes from the router and the lower unique portion comes from the BMC’s channel
MAC address. The 6-byte MAC address is converted into an 8-byte value per the EUI-
64* standard. For example, a MAC value of
00:15:17:FE:2F:62
converts into a EUI-64
value of
215:17ff:fefe:2f62
. If the BMC receives a Router Advertisement from a router at
IP
1:2:3:4::1
with a prefix of 64, it would then generate for itself an IP of
1:2:3:4:215:17ff:fefe:2f62
. The IP, Prefix, and Gateway are read-only parameters to the
BMC user in this mode.
IPv6 can be used with the BMC’s Web Console, JViewer* (remote KVM and Media), and
Systems Management Architecture for Server Hardware – Command Line Protocol (SMASH-
CLP) interface (ssh). There is no standard yet on how IPMI RMCP or RMCP+ should operate
over IPv6 so that is not currently supported.
6.11.3.4
LAN Failover
The BMC FW provides a LAN failover capability so that the failure of the system HW associated
with one LAN link will result in traffic being rerouted to an alternate link. This functionality is
configurable using IPMI methods as well as the BMC’s Embedded UI, allowing for user to
specify the physical LAN links constitute the redundant network paths or physical LAN links
constitute different network paths. BMC supports only an
all or nothing
approach – that is, all
interfaces bonded together, or none are bonded together.
The LAN Failover feature applies only to BMC LAN traffic. It bonds all available Ethernet
devices but only one is active at a time. When enabled, if the active connection’s leash is lost,
one of the secondary connections is automatically configured so that it has the same IP address.
Traffic immediately resumes on the new active connection.
The LAN Failover enable/disable command may be sent at any time. After it has been enabled,
standard IPMI commands for setting channel configuration that specify a LAN channel other
than the first will return an error code.
6.11.3.5
BMC IP Address Configuration
Enabling the BMC’s network interfaces requires using the
Set LAN Configuration Parameter
command to configure LAN configuration parameter 4,
IP Address Source
. The BMC supports
this parameter as follows:
1h, static address (manually configured): Supported on all management NICs. This is
the BMC’s default value.
2h, address obtained by BMC running DHCP: Supported only on embedded
management NICs.
IP Address Source value 4h, address obtained by BMC running other address assignment
protocol, is not supported on any management NIC.
Attempting to set an unsupported IP address source value has no effect, and the BMC returns
error code 0xCC, Invalid data field-in request. Note that values 0h and 3h are no longer
supported, and will return a 0xCC error completion code.
Revision 1.0
55