IBM Service Console (SVCCON) Utility (C) Copyright International Business Machines Corporation 2006. All rights reserved. US Government Users Restricted Rights - Use, duplication, or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Note: Before using this information and the product it supports, read the general information in "Notices and trademarks” in this document. 1.0 Overview For diagnostic purposes, The IBM Service Console Utility provides a quick way to capture hardware diagnostic (BMC) logs stored in NVRAM of your server by using a laptop or client system. The captured log is saved as an ASCII file type and contains the log's hexidecimal data. The captured log file may then be emailed to IBM Service and Support personnel for interpretation and diagostic purposes. An Ethernet connection between the laptop/client system and server being diagnosed is required. 1.2 Limitations At minimum, the server being diagnosed must have A/C power present, and maybe in either a powered down and powered up state. 2.0 Installation and setup instructions The Service Console utility is a stand alone executable file that maybe downloaded and run from any removable media or fixed media device. As the utility is run on a laptop or client system, NO code installation is required on the server being diagnosed. 2.1 Step by step instructions for this installation Download the Service Console executable file to any removable media or fixed media device. 2.2 Other instructions or troubleshooting tips As ethernet network connectivity is needed between, the laptop/client and the server, the following items should be verified prior to running the service console utility: 1) The Server’s BMC controller shares the network interface with the onboard NIC port 1. By default, the BMC network interface is enabled and set to the following IP settings: IP – 10.1.1.97 Subnet Mask – 255.255.255.000 These settings can be verified or set in F1 setup under Advanced Setup->Baseboard Management Controller(BMC) Settings-> BMC Network Configuration To run the application, attach the laptop/client to ethernet port 1 on the server. Make sure the laptop/client is configured with the same subnet mask (255.255.255.0) and different host IP address such as 10.1.1.100. Check that the laptop/client ethernet Link light is illuminated. Open a DOS command prompt and check the connection between the laptop/client and the Server’s BMC with the following command: Ping 10.1.1.97 Once the Ping is successful proceed to Section 3.0 run and configure the Service Console utility. *Note - By default configuration the ping command will not work on the e325, e326, and 326m. 3.0 Configuration information To run the Service Console utility, go to the directory to which utility was downloaded and double click with the right mouse button to start the utility. A GUI task window should then be displayed: 3.1 Define configuration settings The task window opens displaying three text input panels: 1) IP Address 2) User name: 3) Password: The factory default IP address (10.1.1.97), User name (USERID), and Password (PASSW0RD) used by the BMC are displayed. If necessary, these values may be changed to match any configured BMC values. Note that the Logon control button is shown as active, with the Dump SEL and Clear SEL buttons grayed out. Located below the Dump SEL and Clear SEL buttons is the status panel which provides information related to the Logon, Dump SEL and Clear SEL button tasks. To logon to the BMC click the Logon button. 3.2 Hardware status and run information A successful login to the BMC will be noted by the Dump SEL and Clear SEL buttons becoming active and the word "Connected" appearing in the status panel. The Logon button will also change to "Disconnect" If you were unable to logon to the BMC see section 2.2 for troubleshooting tips. To retrieve the BMC System Event Log (SEL), click the Dump SEL task button. A file dialog window will opened allowing the name and location of the saved file to be specified. Clicking the Save button in the file dialog window will save the BMC SEL to the specified file. The file will be saved as ASCII text and contains a date, time, sensor number, a parser error code and the 16 bytes of raw hex log data. A sample output file is shown below: 1= Thu Jan 01 00:00:10 1970, #1 svc02006F09a 01 00 02 0A 00 00 00 20 00 04 09 01 6F 00 FF FF 2= Thu Jan 01 00:02:08 1970, #1 svc02006F09d 02 00 02 80 00 00 00 20 00 04 09 01 EF 00 FF FF 3= Fri Nov 11 13:40:42 2005, #128 svc02036F13a 03 00 02 5A 9F 74 43 20 00 04 13 80 6F 03 FF FF 4= Fri Nov 11 13:48:55 2005, #1 svc02006F09a 04 00 02 47 A1 74 43 20 00 04 09 01 6F 00 FF FF 5= Fri Nov 11 13:49:41 2005, #1 svc02006F09d 05 00 02 75 A1 74 43 20 00 04 09 01 EF 00 FF FF 6= Fri Nov 11 14:03:09 2005, #1 svc02006F09a 06 00 02 9D A4 74 43 20 00 04 09 01 6F 00 FF FF 7= Fri Nov 11 14:03:15 2005, #1 svc02006F09d 07 00 02 A3 A4 74 43 20 00 04 09 01 EF 00 FF FF 8= Fri Nov 11 14:24:48 2005, #1 svc02006F09a 08 00 02 B0 A9 74 43 20 00 04 09 01 6F 00 FF FF 9= Thu Jan 01 00:00:10 1970, #1 svc02006F09a 09 00 02 0A 00 00 00 20 00 04 09 01 6F 00 FF FF 10= Thu Jan 01 00:00:12 1970, #1 svc02006F09d 0A 00 02 0C 00 00 00 20 00 04 09 01 EF 00 FF FF 11= Fri Nov 11 14:29:46 2005, #128 svc02036F13a 0B 00 02 DA AA 74 43 20 00 04 13 80 6F 03 FF FF Since the saved log file contains raw hex data, it is of little value for debug and must be emailed to IBM service and support for interpretation and diagostic purposes. ********************** NOTE TO SERVICE **************************** * BMC logs are interpretated via a BMC log parser found on LUZ. * * When uploading to LUZ, be sure to specify the log type as * * RSA/ISMP. * ******************************************************************* Once the log file is saved the BMC log may be cleared by pressing the Clear SEL button. It is also a good idea to disconnect from the BMC when you have completed all your tasks as to properly close out the network session on the BMC 4.0 Unattended mode This utility does not support unattended mode. 5.0 Web information and support phone numbers You can download new and updated files for IBM eServer xSeries products from http://www.ibm.com/support/. For a list of supported operating systems on legacy (non-shipping) controllers, see http://www.ibm.com/servers/eserver/serverproven/compat/us/. You can receive hardware service through IBM Services or through your IBM reseller, if your reseller is authorized by IBM to provide warranty service. See http://www.ibm.com/planetwide/ for support telephone numbers, or in the U.S. and Canada, call 1-800-IBM-SERV (1-800-426-7378). In the U.S. and Canada, hardware service and support is available 24 hours a day, 7 days a week. In the U.K., these services are available Monday through Friday, from 9 a.m. to 6 p.m. 6.0 Notices and trademarks The following terms are trademarks of International Business Machines Corporation in the United States, other countries, or both: Active PCI OS/2 WARP IBM Predictive Failure Analysis Netfinity ServeRAID Netfinity Manager ServerGuide OS/2 UNIX is a registered of The Open Group in the United States and other countries. Microsoft, Windows, and Windows NT are of Microsoft Corporation in the United States, other countries, or both. Linux is a trademark of Linus Torvalds in the United States, other countries, or both. Java and all Java-based trademarks and logos are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. 7.0 Disclaimer THIS DOCUMENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. IBM DISCLAIMS ALL WARRANTIES, WHETHER EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE AND MERCHANTABILITY WITH RESPECT TO THE INFORMATION IN THIS DOCUMENT. BY FURNISHING THIS DOCUMENT, IBM GRANTS NO LICENSES TO ANY PATENTS OR COPYRIGHTS. S OF FITNESS FOR A PARTICULAR PURPOSE AND MERCHANTABILITY WITH RESPECT TO THE INFORMATION IN THIS DOCUMENT. BY FURNISHING THIS DOCUMENT, IBM GRANTS NO LICENSES TO ANY PATENTS OR COPYRIGHTS.