IBM HS40 Setup Guide - Page 51

Troubleshooting SOL, Management module indicates that blade server does not support SOL

Page 51 highlights

Chapter 6. Troubleshooting SOL This section contains some troubleshooting hints and tips to assist you in solving problems that you might be experiencing with Serial over LAN operation. Go to http://www.ibm.com/systems/support/ for the latest information about solving problems with SOL. Information in this section relates to the following topics: Note: If you are using management channel auto discovery (MCAD), replace references to I/O-module bay 1 in the following procedures with the I/O module bay number that is actually being used (see the BladeCenter Advanced Management Module User's Guide for additional information about MCAD). v "Management module indicates that blade server does not support SOL" v "Blade server shows SOL status of Not Ready" on page 46 v "SOL session opens and drops" on page 47 v "Trouble entering SOL commands or receiving double prompts" on page 48 v "Garbage characters in an SOL session" on page 48 Management module indicates that blade server does not support SOL If the management module SOL configuration page indicates that a blade server does not support SOL, check the following items: v Make sure that blade server type that you are using supports SOL. For example, the Type 8678 blade server does not support SOL and this is a normal message for this blade server type. v The management module has not completed its communication sequence with each of the blade servers in the BladeCenter unit. This condition commonly occurs immediately after power has been applied to the BladeCenter unit or after an management module reset. Allow 5 minutes after power application or a management module reset to make sure that all blade servers have been scanned. v Turn off the blade server, remove it from the BladeCenter unit, reinstall it, and turn it back on. v Move the blade server to a different blade bay. v Update the blade server service processor firmware (BMC or ISMP firmware). Latest firmware is available from http://www.ibm.com/systems/support/. Install the update by following the instructions that come with the update. See the Management Module User's Guide for additional information. v Try a different management module. If the BladeCenter unit contains a standby management module, switch control to it and wait 5 minutes for the management module to fully establish communications with all blade servers. v Update the management module firmware. Latest firmware is available from http://www.ibm.com/systems/support/. Install the update by following the instructions that come with the update. See the Management Module User's Guide for additional information. v There might be a problem with the blade server system board. © Copyright IBM Corp. 2009 45

  • 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

Chapter 6. Troubleshooting SOL
This section contains some troubleshooting hints and tips to assist you in solving
problems that you might be experiencing with Serial over LAN operation. Go to
http://www.ibm.com/systems/support/ for the latest information about solving
problems with SOL. Information in this section relates to the following topics:
Note:
If you are using management channel auto discovery (MCAD), replace
references to I/O-module bay 1 in the following procedures with the I/O module
bay number that is actually being used (see the
BladeCenter Advanced Management
Module User's Guide
for additional information about MCAD).
v
“Management module indicates that blade server does not support SOL”
v
“Blade server shows SOL status of Not Ready” on page 46
v
“SOL session opens and drops” on page 47
v
“Trouble entering SOL commands or receiving double prompts” on page 48
v
“Garbage characters in an SOL session” on page 48
Management module indicates that blade server does not support SOL
If the management module SOL configuration page indicates that a blade server
does not support SOL, check the following items:
v
Make sure that blade server type that you are using supports SOL. For example,
the Type 8678 blade server does not support SOL and this is a normal message
for this blade server type.
v
The management module has not completed its communication sequence with
each of the blade servers in the BladeCenter unit. This condition commonly
occurs immediately after power has been applied to the BladeCenter unit or
after an management module reset. Allow 5 minutes after power application or a
management module reset to make sure that all blade servers have been
scanned.
v
Turn off the blade server, remove it from the BladeCenter unit, reinstall it, and
turn it back on.
v
Move the blade server to a different blade bay.
v
Update the blade server service processor firmware (BMC or ISMP firmware).
Latest firmware is available from http://www.ibm.com/systems/support/.
Install the update by following the instructions that come with the update. See
the
Management Module User's Guide
for additional information.
v
Try a different management module. If the BladeCenter unit contains a standby
management module, switch control to it and wait 5 minutes for the
management module to fully establish communications with all blade servers.
v
Update the management module firmware. Latest firmware is available from
http://www.ibm.com/systems/support/. Install the update by following the
instructions that come with the update. See the
Management Module User's Guide
for additional information.
v
There might be a problem with the blade server system board.
© Copyright IBM Corp. 2009
45