50
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-7 will be allowed for VLAN Priorities. Please note that bits 3 and 4 of Parameter 21 are
considered reserved bits.
Parameter 25 (VLAN Destination Address) of the Set LAN Config Parameters IPMI command is not
supported and returns a completion code of 0x80 (parameter not supported) for any read/write of
parameter 25.
If the BMC IP address source is DHCP, then the following behavior is seen:
If the BMC is first configured for DHCP (prior to enabling VLAN), when VLAN is enabled,
the BMC performs a discovery on the new VLAN in order to obtain a new BMC IP address.
If the BMC is configured for DHCP (before disabling VLAN), when VLAN is disabled, the
BMC performs a discovery on the LAN in order to obtain a new BMC IP address.
If the BMC IP address source is Static, then the following behavior is seen:
If the BMC is first configured for static (prior to enabling VLAN), when VLAN is enabled, the
BMC has the same IP address that was configured before. It is left to the management
application to configure a different IP address if that is not suitable for VLAN.
If the BMC is configured for static (prior to disabling VLAN), when VLAN is disabled, the
BMC has the same IP address that was configured before. It is left to the management
application to configure a different IP address if that is not suitable for LAN.
4.4.3.11 Secure Shell (SSH)
Secure Shell (SSH) connections are supported for one SMASH-CLP session to the BMC.
4.4.3.12 Serial-over-LAN (SOL 2.0)
The BMC supports IPMI 2.0 SOL.
IPMI 2.0 introduced a standard serial-over-LAN feature. This is implemented as a standard payload type
(01h) over RMCP+.
Three commands are implemented for SOL 2.0 configuration:
1. Get SOL 2.0 Configuration Parameters and Set SOL 2.0 Configuration Parameters:
These commands are used to get and set the values of the SOL configuration parameters. The
parameters are implemented on a per-channel basis.
2. Activating SOL: This command is not accepted by the BMC. It is sent by the BMC when SOL is
activated to notify a remote client of the switch to SOL.
3. Activating a SOL session requires an existing IPMI-over-LAN session. If encryption is used, it
should be negotiated when the IPMI-over LAN session is established. SOL sessions are only
supported on serial port 1 (COM1).
4.4.3.13 Platform Event Filter (PEF)
The BMC includes the ability to generate a selectable action (e.g. a system power-off or reset) when a
match occurs to one of a configurable set of events. This capability is called Platform Event Filtering,
or PEF. One of the available PEF actions is to trigger the BMC to send a LAN alert to one or more
destinations.
The BMC supports 20 PEF filters. The first twelve entries in the PEF filter table are preconfigured (but
may be changed by the user). The remaining entries are left blank, and may be configured by the user.