Intel S1200RP Technical Product Specification - Page 70

Address Resolution Protocol ARP, Internet Control Message Protocol ICMP, Virtual Local Area Network

Page 70 highlights

Platform Management Functional Overview Intel® Server Board S1200V3RP  User should always set the hostname starting from block selector 1 after the last Update is complete. If the user skips block selector 1 while setting the hostname, the BMC will record the hostname as NULL, because the first block contains NULL data.  This scheme effectively does not allow a user to make a partial Hostname change. Any Hostname change needs to start from Block 1.  Byte 64 ( Block Selector 04h byte 16) is always ignored and set to NULL by BMC which effectively means we can set only 63 bytes.  User is responsible for keeping track of the Set series of commands and Local Memory contents. While BMC firmware is in Set Hostname in Progress (Update not complete), the firmware continues using the Previous Hostname for DHCP purposes. 6.11.4 Address Resolution Protocol (ARP) The BMC can receive and respond to ARP requests on BMC NICs. Gratuitous ARPs are supported, and disabled by default. 6.11.5 Internet Control Message Protocol (ICMP) The BMC supports the following ICMP message types targeting the BMC over integrated NICs:  Echo request (ping): The BMC sends an Echo Reply.  Destination unreachable: If message is associated with an active socket connection within the BMC, the BMC closes the socket. 6.11.6 Virtual Local Area Network (VLAN) The BMC supports VLAN as defined by IPMI 2.0 specifications. VLAN is supported internally by the BMC, not through switches. VLAN provides a way of grouping a set of systems together so that they form a logical network. This feature can be used to set up a management VLAN where only devices which are members of the VLAN will receive packets related to management and members of the VLAN will be isolated from any other network traffic. Note that VLAN does not change the behavior of the host network setting, and it only affects the BMC LAN communication. LAN configuration options are now supported (by means of the Set LAN Config Parameters command, parameters 20 and 21) that allow support for 802.1Q VLAN (Layer 2). This allows VLAN headers/packets to be used for IPMI LAN sessions. VLAN IDs are entered and enabled by means of parameter 20 of the Set LAN Config Parameters IPMI command. When a VLAN ID is configured and enabled, the BMC only accepts packets with that VLAN tag/ID. Conversely, all BMC generated LAN packets on the channel include the given VLAN tag/ID. Valid VLAN IDs are 1 through 4094, and VLAN IDs of 0 and 4095 are reserved, per the 802.1Q VLAN specification. Only one VLAN can be enabled at any point in time on a LAN channel. If an existing VLAN is enabled, it must first be disabled prior to configuring a new VLAN on the same LAN channel. Parameter 21 (VLAN Priority) of the Set LAN Config Parameters IPMI command is now implemented and a range from 0 to 7 will be allowed for VLAN Priorities. Note that bits 3 and 4 of Parameter 21 are considered Reserved bits. 58 Revision 1.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
  • 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

Platform Management Functional Overview
Intel® Server Board S1200V3RP
User should always set the hostname starting from block selector 1 after the last
Update
is complete
. If the user skips block selector 1 while setting the hostname, the BMC will
record the hostname as
NULL
, because the first block contains NULL data.
This scheme effectively does not allow a user to make a partial Hostname change. Any
Hostname change needs to start from Block 1.
Byte 64 ( Block Selector 04h byte 16) is always ignored and set to NULL by BMC which
effectively means we can set only 63 bytes.
User is responsible for keeping track of the Set series of commands and Local Memory
contents.
While BMC firmware is in
Set Hostname in Progress
(Update not complete), the firmware
continues using the Previous Hostname for DHCP purposes.
6.11.4
Address Resolution Protocol (ARP)
The BMC can receive and respond to ARP requests on BMC NICs. Gratuitous ARPs are
supported, and disabled by default.
6.11.5
Internet Control Message Protocol (ICMP)
The BMC supports the following ICMP message types targeting the BMC over integrated NICs:
Echo request (ping): The BMC sends an Echo Reply.
Destination unreachable: If message is associated with an active socket connection
within the BMC, the BMC closes the socket.
6.11.6
Virtual Local Area Network (VLAN)
The BMC supports VLAN as defined by IPMI 2.0 specifications. VLAN is supported internally by
the BMC, not through switches. VLAN provides a way of grouping a set of systems together so
that they form a logical network. This feature can be used to set up a management VLAN where
only devices which are members of the VLAN will receive packets related to management and
members of the VLAN will be isolated from any other network traffic. Note that VLAN does not
change the behavior of the host network setting, and it only affects the BMC LAN
communication.
LAN configuration options are now supported (by means of the
Set LAN Config Parameters
command, parameters 20 and 21) that allow support for 802.1Q VLAN (Layer 2). This allows
VLAN headers/packets to be used for IPMI LAN sessions. VLAN IDs are entered and enabled
by means of parameter 20 of the
Set LAN Config Parameters
IPMI command. When a VLAN ID
is configured and enabled, the BMC only accepts packets with that VLAN tag/ID. Conversely, all
BMC generated LAN packets on the channel include the given VLAN tag/ID. Valid VLAN IDs
are 1 through 4094, and VLAN IDs of 0 and 4095 are reserved, per the 802.1Q VLAN
specification. Only one VLAN can be enabled at any point in time on a LAN channel. If an
existing VLAN is enabled, it must first be disabled prior to configuring a new VLAN on the same
LAN channel.
Parameter 21 (VLAN Priority) of the
Set LAN Config Parameters
IPMI command is now
implemented and a range from 0 to 7 will be allowed for VLAN Priorities. Note that bits 3 and 4
of Parameter 21 are considered Reserved bits.
Revision 1.0
58