Showing posts with label Intel Remote Management Module. Show all posts
Showing posts with label Intel Remote Management Module. Show all posts

Friday, 11 January 2013

Intel Server Systems Remote Management Module 4 (RMM4) Display Resolution

Once the server with the RMM4 has been set up there is an important step that needs to happen to allow the RMM4 to establish a remote KVM over IP session:

image

Make sure the desktop display resolution after installing the graphics driver is set to 1440x900 or 1280x1024 before logging off the desktop the final time.

Otherwise the KVM over IP session will show a black screen after clicking the Launch Console button.

image

This is an especially important step for all servers with an RMM2/3/4!

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book

Windows Live Writer

Wednesday, 7 September 2011

One Reason For Having a Remote Management Module In All Servers

Among the many reasons, having an Intel Remote Management Module (RMM), Dell iDRAC Enterprise, HP iLO Advanced, and other add-in remote management module is the ability to have console KVM access to that box under virtually any condition.

Caveat: Obviously, no power or Internet means no access. :)

image

The above screenshot is a snip taken on our back shop’s desktop.

We are in the process of setting up a 2 node cluster on behalf of a client. Because we have Intel RMM3 modules in both nodes we are able to have both consoles running side-by-side so as to run _all_ configuration steps at the same time.

Thus, besides full remote management capabilities we have the ability to work on both systems without messing around with a physical KVM (the servers are just behind the shop desktop).

Having this ability reduces the possibility that a mistake would be made configuring the nodes as we can keep an eye on both systems simultaneously.

Once the OS configuration has been complete up to the domain join point, all of the cluster components will be loaded up in their boxes and delivered to our client site for the next phase of the cluster setup . . . all done remotely once the systems are fired up and the remote connection is tested.

Static IPs

Note that we request that all of our clients have at least one static IP address with our preference being for two (Certain ISP’s DHCP reservation for the IP are _not_ static IPs IMNSHO).

One IP is configured for their remote access. The other IP would be used for the RMM.

For this particular client we just got off the phone with Nucleus (our preferred DSL provider here in Alberta and BC) to add a third static IP address that the new standalone DC’s RMM will be plugged into.

Once we have finished the migration and the original SBS 2003 server has been decommissioned we will call Nucleus and release the IP associated with the original SBS server’s RMM2.

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book

*Our original iMac was stolen (previous blog post). We now have a new MacBook Pro courtesy of Vlad Mazek, owner of OWN.

Windows Live Writer

Thursday, 4 August 2011

Intel RMM3: Error Opening Video Socket Fix

Intel has released an update for the RMM3 module that is supposed to fix the error when trying to establish a remote KVM session.

The downloads for the Intel Server Board S3420GP series can be found here:

Note that the Intel Server Board S3420GPRX has a different firmware set than the Intel Server Board S3420GPLX.

There is also a catch in the BMC installation procedure that should be noted at step 3 of the BMC firmware Release Notes.TXT file:

=====================================================================
            INSTALLATION PROCEDURE
=====================================================================

  1. Copy the BMC_0124.ima, fwpiaupd.efi, ipmi.efi, upd_BMC.nsh files
     to a USB key, hard disk drive or floppy drive.
     All of these files must reside in the same directory.

  2. Boot to EFI and then run the upd_BMC.nsh script file to update the BMC FW.

     Using fwpiaupd.efi with your own command line parameters is not supported
     and doing so is at your own risk!

     *** If you have an Intel Remote Management Module 3 plugged into the baseboard ***
     *** then proceed to the next step otherwise go to step #4 and proceed ***

  3. Power off the system and cycle AC power


  4. Install latest available FRU/SDR package.
=====================================================================
                           KNOWN ISSUES/WORKAROUNDS
=====================================================================
  - Users of the KVM feature will need to update their client Java JRE to version
    1.6 (JRE 6) or later otherwise the KVM redirection application will not launch.
    The latest Java Runtime Environment (JRE) update can be downloaded from here:
    http://java.com/en/download/index.jsp

  - The following features are not supported in BMC FW :
    ∙ IPMI serial channel, COM port MUX switching and the terminal mode feature.
=====================================================================
                           ISSUES FIXED
=====================================================================

01.24
  -  Issue with Win7/IE8/Java 6 Update 22 through RMM3 connection/remote access.

Essentially it looks as though we are visiting most of our clients with RMM3 and RMM3LITE modules installed to run these updates to power cycle those boxes. Fortunately some have their servers hooked into a UPS or PDU that allows us to power cycle the A/C remotely!

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book

*Our original iMac was stolen (previous blog post). We now have a new MacBook Pro courtesy of Vlad Mazek, owner of OWN.

Windows Live Writer

Wednesday, 8 June 2011

Intel Remote Management Module 3 – Error Opening Video Socket

We have hit a problem with the KVM setup in Intel’s RMM3:

image

Socket Error

Error opening video socket

This particular server was set up here in the shop using the RMM3 connection plugged into our local network. We took the server to our client’s site, plugged everything in, and subsequently went to test connectivity via one of our shop systems.

The RMM3 site came up okay but when we went to start a KVM session the above error happened.

A call into Intel’s support line did not yield any positive results either.

The proper method to try and ground zero both the RMM3 module and the BMC can be found at the bottom of the following Intel Support page:

If you need to reset to factory defaults (e.g. invalid user name or password)

A reset can be done with the syscfg utility.  Download syscfg for for the 5500 series or for the S3420GP series

  • Unzip the file and copy the folder UEFI_SYSCFG_V501_B23\ preferably to an USB key

  • Boot the server and enter the BIOS

  • Go to the Boot Manager menu and select the option to boot to EFI shell and enter

  • In the EFI shell prompt, type fs0: (0 is the device containing the sysconfig utility e.g. USB pen)

  • Browse to the directory with the sysconfig utility

  • The path has to be defined by entering: set SYSCFG_PATH fs0:\<syscfg_efi> where syscfg_efi is the folder containing all the files from the sysconfig utility

  • The settings can be reset by entering: syscfg –rfs

Given the above, we will be leaving a small amount of space on any bootable USB flash drive permanently plugged into the server and formatting it FAT32 so that utilities like this can be accessed via the EFI shell.

A post on the Intel Communities Web site was the only result in our searching:

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book

*Our original iMac was stolen (previous blog post). We now have a new MacBook Pro courtesy of Vlad Mazek, owner of OWN.

Windows Live Writer