1.4.1

3.0.16.11.h

3.0.10.15.b (r57573) (or subsequent release) 3.0.12.10 (or subsequent release)

08.07.03.06

1.4

3.0.16.11.g

3.0.10.15.b (r57573) (or subsequent release) 3.0.12.10 (or subsequent release)

08.07.03.05

1.3.2

3.0.16.11.e

3.0.10.15.b (r57573) (or

subsequent release) 3.0.12.10

(or subsequent release)

08.07.02.03

1.3.1

3.0.16.11.d

3.0.10.15.b (r57573) (or subsequent release) 3.0.12.10 (or subsequent release)

08.07.02.02

1.3

3.0.16.11.b

3.0.10.15.b (r57573) (or subsequent release) 3.0.12.10 (or subsequent release)

08.07.02.02

1.2.1

3.0.16.11.a

3.0.10.15.b (r57573) (or subsequent release) 3.0.12.10 (or subsequent release)

08.07.01.09

1.2

3.0.16.11

3.0.10.15.b (r57573) (or subsequent release) 3.0.12.10 (or subsequent release)

08.07.01.08

1.1.3

3.0.14.12.c

3.0.10.15.b (r57573) (or subsequent release) 3.0.12.10 (or subsequent release)

08.05.02.03

1.1.2

3.0.14.12.b

3.0.10.15.b (r57573) (or subsequent release) 3.0.12.10 (or subsequent release)

08.05.02.03

1.1.1

3.0.14.12.a

3.0.10.15.b (r57573) (or subsequent release) 3.0.12.10 (or subsequent release)

08.05.02.03

1.0.1

3.0.9.15.a

3.0.6.11.b (r489888) (or subsequent release) 3.0.12.10 (or subsequent release)

08.02.01.05

Intel CPU Microcode

SRV_C_89

Intel RC

p2.93

Intel CPU Reference Code

1.08

Intel QuickPath Interconnect (QPI) Reference Code

1.85

Intel Memory Reference Code (MRC)

2.12

7087299

iSCSI Function Support Added as of Software Release 1.3

Enhancement:

After pressing "F2" to access the BIOS Setup menu, you can select BOOT --> Option ROM Enable --> Kawela iSCSI Feature.

You can now toggle the iSCSI setting from the default Disabled to Enabled. When enabled, BIOS will automatically disable the onboard network controller’s PXE option ROM, and BIOS will run the iSCSI option ROM first.

Note - Option ROM runtime code for iSCSI is about 40k. After iSCSI is enabled, inserting many other PCIe devices with option ROM might trigger a warning message about the ROM size.

Note - Oracle VM 3.0 SERVER INSTALL/BOOT over iSCSI is not supported as of Software Release 1.3.2

7049067

Link Speed of the Sun Storage 6 Gb SAS ExpressModule HBA Is Reduced to Gen1 Speed When the HBA Is Hot-Plugged

Issue:

The Sun Storage 6 Gb SAS ExpressModule Host Bus Adapter (HBA) (SGX-SAS6-EM-Z) will reduce its link speed to 2.5GT/s when hot-plugged on the Sun Blade X6270 M2 Server Module.

Affected Hardware:

• Sun Blade X6270 M2 Server Module
• Sun Storage 6 Gb SAS ExpressModule HBA (SGX-SAS6-EM-Z)

Fix Available:

Fixed in Software Release 1.2.1.

6898588

Using <CTRL-N> With the REM HBA Option Card Installed Might Bypass Network Boot and REM HBA Option ROM Load

Issue:

If the Sun Storage 6 Gb SAS RAID Expansion Module (REM) Host Bus Adapter (HBA) (SGX-SAS6-REM-Z) option card is installed in the system, and <CTRL-N> is used on the serial console to initiate a network boot, the network boot might not be initiated, and the Option ROM for the REM HBA option card might not be loaded.

Affected Hardware and Software:

• Sun Storage 6 Gb SAS REM HBA (SGX-SAS6-REM-Z) option card
• Software releases 1.0.1 and 1.1.1

Workaround:

Do one of the following:

• Use the Oracle ILOM Remote Console and press F12 to initiate a network boot.
• If using the serial console, use <CTRL-E> to get to the BIOS Boot Device Priority menu, and then move the desired PXE adapter (network boot device) to the top of the Boot Device Priority list. The PXE adapter will then be used as the boot device.
• Press <CTRL-N> during, or after, the time SGX-SAS6-REM-Z Option ROM code is running. The Option ROM code is running when the following banner is displayed: LSI Corporation MPT SAS2 BIOS. Copyright 2000-2010 LSI Corporation.

Fix Available:

This issue is resolved in Software Release 1.2.

6979993

Do Not Disable Redirection After BIOS Post

Issue:

If Redirection After BIOS Post is disabled in the BIOS Setup Utility, BIOS will fail during boot.

Affected Hardware and Software:

• Sun Blade X6270 M2 Server Module
• All releases through software 1.3

Workaround:

To enable redirection after BIOS POST:

1. Enter the BIOS Setup Utility.
2. Select Advanced > Remote Access Configuration.
3. Enable Redirection After BIOS POST.
4. Press F10 to save your settings and exit the BIOS Setup Utility.
5. Reboot the system.

Fix Available:

This issue is resolved in Software Release 1.4.

1586126

Fault Reported for Non-Existent NEM

Issue:

In a powered-off Sun Blade 6000 Modular System, the amber Service Required LED for a network express module (NEM) reports an erroneous fault condition. When the Sun Blade 6000 Modular System that has a Sun Blade X6270 M2 or X6270 M3 server module (blade) installed is powered off, the amber Service Required LED might be illuminated for one of the NEMs (NEM0 or NEM1) even when there is no NEM installed in the chassis. In this case, ILOM reports a fault.fruid.corrupt message.

Affected Hardware and Software:

Sun Blade X6270 Server Module

Supplemental Software Software Releases 1.0, 1.1, 1.2, 1.4, 2.0, 2.0.1, 2.1, 2.3, 2.4

Workaround:

Power on the chassis. After the chassis is powered on, the Service Required LED for the NEM is extinguished and the system recognizes that no NEM is present.

7084903

SLES 11 SP1 Does Not Find the Sun Blade 6000 Virtualized 40 GbE NEM Device After Hot-Plugging That NEM on Sun Blade X6270 M2 Server Module

Issue:

After hot-plugging the Sun Blade 6000 Virtualized 40 GbE Network Express Module (NEM) on the Sun Blade X6270 M2 Server Module, the system cannot find the NEM when running the SUSE Linux Exterprise Server 11 SP1 operating system.

Affected Hardware and Operating System:

• Sun Blade X6270 M2 Server Module
• Sun Blade 6000 Virtualized 40 GbE Network Express Module (7100090)
• Pass-Thru PCIe 2.0 Fabric Expansion Module (7100633)
• SUSE Linux Enterprise Server 11 SP 1 (SLES 11 SP1)

Workaround:

Use software release 1.3.2 and later firmware and the new version of the Pass-Thru PCIe 2.0 Fabric Expansion Module 7100633 (new PCA part number is 7041199).

7082742

Sun Blade 6000 Ethernet Switched NEM 24p 10 GbE Missing in hostdiags Information

Issue:

When using Oracle ILOM on a Sun Blade X6270 Server Module with two Sun Blade 6000 Ethernet Switched Network Express Module (NEM) 24p 10GbE and a Sun Dual 10 GbE PCIe 2.0 Fabric Expansion Module (FEM), hostdiags information shows only NEM0 is ACTIVE, while NEM1 is NOT ACTIVE.

Affected Hardware:

• Sun Blade X6270 M2 Server Module
• Sun Blade 6000 Ethernet Switched Network Express Module 24p 10GbE (X2073A)
• Sun Dual 10 GbE PCIe 2.0 Fabric Expansion Module (4871A-Z-N)

Workaround:

No workaround is available. The Fabric Expansion Module (FEM) is seen as a PCIe device attached on the root port. NEM1 is shown as NOT ACTIVE in the hostdiags information, which means that no FEM is on the root port even though two NEMs are populated in the system.

No CR Number

Server Module REM Might Hang When Inserted Into a Chassis With SAS-1 Devices

Issue:

If the Sun Blade X6270 M2 Server Module is inserted into a Sun Blade 6000 Modular System chassis that has SAS-1 Network Express Modules (NEMs), or SAS-1 NEMs and a Sun Blade 6000 Disk Module, the server module’s SAS-2 RAID Expansion Module (REM) might hang.

Affected Hardware and Firmware:

• Sun Blade X6270 M2 Server Module
• Sun Blade 6000 Disk Module
• Sun Blade 6000 Multi-Fabric Network Express Module
• Sun Blade 6000 Virtualized Multi-Fabric 10GbE Network Express Module
• Sun Blade 6000 Multi-Fabric 10GbE Network Express Module
• Sun Blade 6000 Disk Module Firmware Version 5.04.03

Workaround:

To prevent this problem, you need to upgrade the firmware of your SAS-1 components (SAS-NEMs and disk modules) to a firmware version that supports SAS-1/SAS-2 coexistence. This upgrade must be done before you insert the Sun Blade X6270 M2 Server Module into the chassis. At a minimum, all SAS expanders for SAS-1 NEMs and Sun Blade 6000 Disk Modules must be upgraded to firmware revision 5.04.03 to allow SAS-1/SAS-2 device coexistence in the Sun Blade 6000 Modular System chassis. See the SAS-1/SAS-2 Compatibility Upgrade Guide for details on obtaining the firmware and performing the upgrade.

6931323

LED That Monitors Activity of Intel 32GB SSD and Seagate 500GB HDD Does Not Work Correctly

Issue:

The Intel 32GB solid state drive (SSD) and Seagate 500GB hard disk drive (HDD) green Activity LED does not light and remain illuminated when there is no disk activity. The LED blinks when there is disk activity, but does not remain lit when the disk is idle.

Affected Hardware:

• Sun Blade X6270 M2 Server Module
• Sun Blade 6000 Disk Module

Workaround:

No workaround is available.

6879222

1GB Ethernet Controller Fails to Link at 1Gb/s With 100m Cable in Virtualized Multi-Fabric 10GbE NEM

Issue:

On-board Ethernet devices might experience an occasional failure to establish a connection at 1Gb/s, and might automatically establish a connection at 100 Mb/s instead.

Affected Hardware:

• Sun Blade X6270 M2 Server Module
• Sun Blade 6000 Disk Module

Workaround:

Use an Ethernet cable 66 meters or shorter. Alternatively, you can force the Ethernet link to 100Mb/s.

7049051

When Using Oracle Linux 6, Hot-Swap Replacement of Host Bus Adapters (HBAs) With Converged Network Adapter (CNA) Will Fail

Issue:

When using Oracle Linux 6, a hot-swap operation will fail when replacing a StorageTek Dual 8Gb FC Dual GbE HBA, ExpressModule, Emulex (SG-XPCIEFCGBE-E8-N) or StorageTek Dual 8Gb FC Dual GbE HBA, ExpressModule, QLogic (SG-XPCIEFCGBE-Q8-N) with a Sun Storage 10GbE FCoE ExpressModule Converged Network Adapter (SG-XEMFCOE2-Q-SR/SG-XEMFCOE2-Q-TA) on the Sun Blade X6270 M2 Server Module.

Affected Hardware and Operating System:

• Sun Blade X6270 M2 Server Module
• StorageTek Dual 8Gb FC Dual GbE HBA, Express Module, Emulex (SG-XPCIEFCGBE-E8-N)
• StorageTek Dual 8Gb FC Dual GbE HBA, Express Module, QLogic (SG-XPCIEFCGBE-Q8-N)
• Sun Storage 10GbE FCoE ExpressModule Converged Network Adapter (SG-XEMFCOE2-Q-SR/SG-XEMFCOE2-Q-TA)
• Oracle Linux 6

Workaround:

No workaround is available. A reboot of the system will load the Express Module card correctly.

6942287

PXE Boot Might Fail After Running Pc-Check Diagnostics

Issue:

When attempting to PXE boot immediately after running Pc-Check diagnostics software, the boot attempt might fail with a message similar to the following:

Intel(R) Boot Agent GE v1.3.31
Copyright (C) 1997-2009, Intel Corporation
PXE-EC8: !PXE structure was not found in UNDI driver code segment. PXE-M0F: Exiting Intel Boot Agent.

Affected Hardware:

• Sun Blade X6270 M2 Server Module
• Sun Blade 6000 Disk Module

Workaround:

Run Pc-Check diagnostics again, then reboot the system.

6978869

Operating System Might Hang After Running Pc-Check Diagnostics

Issue:

After running Pc-Check diagnostics software, if you attempt to install or boot an operating system, the operating system install or boot might hang.

Affected Hardware:

• Sun Blade X6270 M2 Server Module

Workaround:

Reboot the system after running Pc-Check diagnostics and before trying to install or boot an operating system.

6928567

Unable to Launch Oracle ILOM 3.0.x Remote Console Using JRE 1.6.0 U14, U15, or U16

Issue:

If you try to launch the Oracle ILOM 3.0.x Remote Console via the web using some builds of Java Runtime Environment (JRE), the system returns the error Unable to Launch the Application.

Affected Operating Systems and Firmware:

• All operating systems running Oracle ILOM 3.0 with JRE 1.6.0, U14, U15, or U16.

Workaround:

Upgrade to JRE 1.6.0 U17 or later.

6923903

SP Restore Is Partially Successful and Reports an Error in the Log

Issue:

If the serial console is in use, properties related to the serial console cannot be restored and you will receive messages such as the following:

Config restore: Unable to restore property ’/SP/serial/host/commitpending’

Config restore: Unable to restore property ’/SP/serial/external’

Because such properties could not be restored, this is a partial failure and, therefore, results in the above message about the partial failure. This is not a defect.

Affected Operating Systems and Firmware:

• All operating systems running Oracle ILOM 3.0.x

Workaround:

Log out of the serial console and try to run restore again.

7090903

iSCSI Boot Is Not Supported on Oracle VM 3.0

Issue:

The iSCSI target does not display during installation of Oracle VM 3.0

Affected Software:

• Oracle VM 3.0

Workaround:

There is currently no workaround. Oracle VM 3.0 does not support iSCSI boot.

6929991

“EHCI BIOS handoff failed” Message Appears

Issue:

The "EHCI BIOS handoff failed" message appears in VMware ESX 4.0 Update 1. The failure message appears in the dmesg output.

Affected Software:

• VMware ESX 4.0 Update 1

Workaround:

This message can be safely ignored. It does not cause any functional problems.

7095810

and

7123117

Hot-Unplugging HBA ExpressModule Causes Kernel Panic

Hot-Unplugging NEM Causes Kernel Panic

Issue:

When running Oracle VM 3.0.1 or 3.0.2, a system kernel panic might occur when you hot-unplug one of these components:

• StorageTek Dual 8Gb FC Dual GbE HBA, ExpressModule, QLogic
• StorageTek Dual 8Gb FC Dual GbE HBA, ExpressModule, Emulex
• Quad Port (4x) Gigabit Ethernet Network Express Module
• Sun Blade 6000 Virtualized 40 GbE Network Express Module

Affected Hardware and Software:

• StorageTek Dual 8Gb FC Dual GbE HBA, ExpressModule, QLogic (SG-XPCIEFCGBE-Q8-Z)
• StorageTek Dual 8Gb FC Dual GbE HBA, ExpressModule, Emulex (SG-XPCIEFCGBE-E8-Z)
• Quad Port (x4) Gigabit Ethernet Network Express Module (7284A-Z)
• Sun Blade 6000 Virtualized 40 GbE Network Express Module (7100090)
• Oracle VM 3.0.1 or 3.0.2

Workaround:

No workaround is available. Do not attempt the hot-unplug operation.

6927196

Oracle VM Manager 2.2 Install Fails on 6-Core CPU Configurations

Issue:

When installing Oracle VM Manager 2.2 on a Sun Blade X6270 M2 Server Module with 6-core processors (CPUs), the install might fail and exit with the message Database is not available.

Affected Hardware and Software:

• Sun Blade X6270 M2 Server Module
• Oracle VM Manager 2.2

Workaround:

To resolve this issue, see the patch and installation instructions at: http://oss.oracle.com/oraclevm/manager/patch

6779112

Misleading Status for Power Supplies Is Reported by VMware Health Status Screen

Issue:

The VMware Virtual Infrastructure client Health Status screen under the Power component reports the server power supplies in an Off-Line Disabled state and 0 watts, even though the power supplies are on-line and enabled.

Affected Software:

• VMware ESX 4.0 Update 1

Workaround:

To view the correct power status while in the VMware Virtual Infrastructure client Health Status screen, click on the Other component from the list of available options and view the blade n VPS (where n is the blade number).

6900741

Local Storage Drive Is Not Seen After Installing VMware ESXi 4.0 Update 1

Issue:

If the Sun Blade X6270 M2 Server Module has a local storage drive attached to a Sun Blade RAID 0/1 RAID Expansion Module (X4607A-Z), the local storage drive is not seen by the system after installing VMware ESXi 4.0 Update 1.

Affected Software:

• VMware ESXi 4.0 Update 1

Workaround:

After completing the ESXi installation, follow these steps to add the local storage drive to the storage inventory:

1. Add the ESXi host to the data center of your choice using the Virtual Infrastructure Client.
2. Select the ESXi host added in Step 1, then click the Configuration tab.
3. In the hardware box (in the upper left of the display), select Storage.
4. In the upper right part of the display, click the Add Storage... link.
5. Ensure that the Disk/LUN Storage Type is selected, then click Next.
6. Highlight the vmhba entry that corresponds to the local storage drive, then click Next.
7. Select the Use free space entry, then click Next.
8. Create a Datastore Name (for example, local_storage), then click Next.
9. Adjust the Maximum file size, if needed, then click Next.
10. Verify the proposed disk layout, then click Finish.

The local VMFS datastore should now be available for use.

7157040

Oracle Solaris 11 Panics at Reboot on a Sun Storage 10 GbE FCoE ExpressModule Converged Network Adapter Configuration

Issue:

Oracle Solaris 11 has high failure rate of kernel panic at reboot when the host is connected to a Fibre Channel over Ethernet (FCoE) switch with fibre channel storage through a Sun Storage 10 GbE FCoE ExpressModule Converged Network Adapter (SG-XPCIEFCOE2-Q-SR/SG-XPCIEFCOE2-Q-TA) configuration.

"qlge:ql_quiesce+fb ()" is seen in the call trace.

Affected Operating System:

• Oracle Solaris 11 11/11

Workaround:

A workaround is not available. Although there is a kernel panic at reboot, the system can still boot up successfully.

7009052

DDR3 DIMMs Displayed as Unknown Type in Oracle Solaris 10

Issue:

If you use the prtdiag command in Oracle Solaris 10, the DDR3 DIMM will be displayed as unknown type. This is purely a display issue with no functional impact.

Affected Operating Systems:

• Oracle Solaris 10 10/09
• Oracle Solaris 10 9/10

Workaround:

A workaround is not yet available. The problem will be resolved in a future Oracle Solaris release.

7076583

RHEL 5.6 Fails to Allocate Memory Space When SR-IOV Function Is Enabled on Intel 82576 NIC

Issue:

To support the SR-IOV function, you must first enable SR-IOV support and ARI support functions in the Advanced Menu of the BIOS Setup Utility options.

Affected Operating System:

• Red Hat Enterprise Linux (RHEL) 5.0 or above

Workaround:

Enable SR-IOV support and ARI support features in the Advanced Menu of the BIOS Setup Utility options.

6940552

CPU Power-State Cannot Be Capped On Host Reboots If Hard Cap Is Enabled

Issue:

Oracle ILOM Power Management limits might not be honored when booting in Oracle Linux 5.5 or in Red Hat Enterprise Linux (RHEL) 5.5.

Affected Operating Systems:

• Oracle Linux 5.5
• Red Hat Linux (RHEL) 5.5

Workaround:

Using Oracle ILOM, disable then reenable Power Limiting using the following steps:

1. Select the Power Management tab.
2. Select the Limit tab
3. Next to the Power Limiting option, uncheck Enabled.
4. Click Save.
5. Next to the Power Limiting option, check Enabled.
6. Click Save.

6907462

SLES 11 Logs Error Messages About Loading EHCA Driver

Issue:

When using the SUSE Linux Enterprise Server 11 (SLES 11) operating system, if the OFED package group is installed, the system generates benign error messages about loading the Infiniband EHCA driver. The errors are logged because the supported Infiniband IO device does not use the EHCA driver.

Affected Operating System:

SUSE Linux Enterprise Server 11 (SLES 11)

Workaround:

Supported Infiniband devices use the mlx4_core device driver. Ignore the error messages about the EHCA driver or disable attempts to automatically load the EHCA driver by editing the configuration file /etc/infiniband/openib.conf to change EHCA_LOAD=yes to EHCA_LOAD=no.

6914173

PCIEHP Hot-Plug Default Driver Is Not Supported by SLES 10 SP3

Issue:

SUSE Linux Enterprise Server 10 SP3 (SLES 10 SP3) has disabled interrupts on the PCI Express root ports. As a result, pciehp hot-plug does not function properly with default driver options. This can result in USB devices being inadvertently disabled when hot-plug actions are attempted.

Affected Operating System:

• SUSE Linux Enterprise Server 10 SP3 (SLES 10 SP3)

Workaround:

You must load the pciehp driver with the following parameter:

pciehp_poll_mode=1

For example:

modprobe pciehp pciehp_poll_mode=1

6908037

Infiniband Driver Unable to Use MSI-X Interrupts in SLES 10 SP3

Issue:

The Infiniband driver mlx4_core in SUSE Linux Enterprise Server 10 SP 3 (SLES 10 SP3 ) cannot use MSI-X interrupts on systems with a high number of processors (CPUs).

Affected Operating System:

• SUSE Linux Enterprise Server 10 SP3 (SLES 10 SP3)

Workaround:

Load Infiniband driver with MSI-X interrupts disabled, using one of the following methods:

• Type the following command to load the driver with MSI-X interrupts disabled: modprobe mlx4_core msi_x=0
• Add the following line to the file /etc/modprobe.conf.local so that mlx4_core will never use MSI(X) when the driver is loaded: options mlx4_core msi_x=0

6915768

During a Reboot of the System, a Kernel Panic Might Occur

Issue:

During a warm reboot of the system, you might see an intermittent kernel panic __cpufreq_governor.

Affected Operating Systems:

• Oracle Linux 5.4
• Red Hat Enterprise Linux (RHEL) 5.4

Workaround:

A patch has been issued to fix this issue. You can download the patch at:

https://bugzilla.redhat.com/attachment.cgi?id=336296&action=diff

6914898

Certain Express Modules Are Not Supported for Hot-Plug Operations

Issue:

With Windows Server 2008 SP2 and 2008 R2, certain Express Modules are not currently supported for hot-plug operations. The following Express Modules cannot be hot-plugged:

• SG-XPCIE2FCGBE-Q-Z - Sun StorageTek Dual 4Gb FC Dual GbE HBA, QLogic
• SG-XPCIE2FCGBE-E-Z - Sun StorageTek Dual 4Gb FC Dual GbE HBA, Emulex
• SG-XPCIEFCGBE-Q8-Z - StorageTek Dual 8Gb FC Dual GbE HBA, QLogic
• SG-XPCIEFCGBE-E8-Z - StorageTek Dual 8Gb FC Dual GbE HBA, Emulex
• X7284A-Z - Sun Quad GbE Express Module

Affected Operating Systems:

• Windows Server 2008 SP2, 64-bit
• Windows Server 2008 R2, 64-bit

Workaround:

Insert the affected module(s) and reboot the system in order for them to be recognized.

6879304

System Event Log Warning Messages Are Generated When Power Is Being Limited by Oracle ILOM Power Management

Issue:

When power is being limited by the Oracle ILOM Power Management feature, Windows Server 2008 R2 operating system will generate warning messages in the System Event Log informing the user that the processor(s) are being restricted. Example Event: The Speed of Processor xx in group x is being limited by system firmware. The processor has been in this reduced performance state for xxxx seconds since last report.

Affected Operating System:

• Windows Server 2008 R2

Workaround:

None needed. These are expected events and are not indicative of a problem.

6977546

SW 1.0.1 Product Documentation Lists Incorrect BIOS Version

Issue:

The incorrect BIOS version number (08.04.01) is listed in the Sun Blade X6270 M2 Server Module product documentation for Software Release 1.0.1.

Workaround:

Documentation has been corrected to show 08.02.01.05 as the BIOS version for Software Release 1.0.1 of the Sun Blade X6270 M2 Server Module.

No CR number

Documented HBA Is Not Yet Available

Issue:

The following host bus adapter (HBA) is listed as an available option in the Sun Blade X6270 M2 Server Module Installation Guide for Windows Operating Systems:

• Sun Storage 6 Gb SAS RAID ExpressModule Host Bus Adapter (HBA) (SGX-SAS6-R-EM-Z)

The HBA listed above is not yet available in the Sun Blade X6270 M2 Server Module.