MAXDATA PLATINUM 9000-2R Server System Product Guide
Contents Important Safety Information 11 Important Safety Instructions................................................................................................................11 Wichtige Sicherheitshinweise ...............................................................................................................11 Important Safety Instructions Consignes de sécurité ...........................................................................11 Instrucciones de seguridad importantes .............
CMOS Clear .....................................................................................................................................47 BIOS Recovery Mode ..................................................................................................................... 48 BIOS Setup........................................................................................................................................... 49 Starting Setup .........................................................
Retry Interval....................................................................................................................................70 Baud Rate.........................................................................................................................................70 User Configuration Sub-task ............................................................................................................71 Enable User ...............................................................
Call Retries ...................................................................................................................................... 87 Terminal Mode Configuration.......................................................................................................... 87 Enable Terminal Mode .................................................................................................................... 87 Enable Line Editing................................................................
EFI Platform Diagnostic Tests .............................................................................................................102 Starting the Application..................................................................................................................102 Understanding the General User Interface ....................................................................................102 Understanding Basic Testing.......................................................................
4 Technical Reference 125 System Interconnection ......................................................................................................................126 User-Accessible Interconnects............................................................................................................127 Serial Port.......................................................................................................................................127 Video Port .....................................
Figures 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. Server System Front ......................................................................................................................13 Server System Front with Bezel Installed ......................................................................................
Tables 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. 10 Physical Specifications ...................................................................................................................13 Feature Summary ...........................................................................................................................14 SCSI Hard Drive LED Details..............
Important Safety Information Important Safety Instructions Read all caution and safety statements in this document before performing any of the instructions. Wichtige Sicherheitshinweise Lesen Sie zunächst sämtliche Warn- und Sicherheitshinweise in diesem Dokument, bevor Sie eine der Anweisungen ausführen. Important Safety Instructions Consignes de sécurité Lisez attention toutes les consignes de sécurité et les mises en garde indiquées dans ce document avant de suivre toute instruction.
Product EMC Compliance • CISPR 22 – Class A Emissions (International) • EN55022 – Class A Emissions (CENELEC Europe) • EN55024 – Immunity (CENELEC Europe) • EN61000–3–2 – Harmonics (CENELEC Europe) • EN61000–3–3 – Voltage Flicker (CENELEC Europe) • CE – EMC Directive 89/336/EEC (CENELEC Europe) Product Regulatory Compliance Markings The Server System MAXDATA PLATINUM 9000-2R may be marked with the following regulatory compliance markings.
1 System Description The MAXDATA Server System 9000-2R is a compact, high-density, rack mount server system with support for one to two Intel® Itanium® 2 processors and 16-GB DDR SDRAM memory. The scaleable architecture of the system supports Symmetric Multiprocessing (SMP) and a variety of operating systems. The server system supports several high availability features, such as hot-swap and redundant power supply modules, hot-swap and redundant fans for cooling, and hot-swap hard drives.
Table 2 provides a list and brief description of the features of the server system. Table 2.
External Chassis Features System controls and indicators are located in several places on the chassis as follows: • Chassis front: – Front panel: Front panel switches and LEDs – Peripheral bay: Hard drive LEDs – Power bay: Power Module LEDs and Power Supply LEDs • Chassis back panel: System ID LEDs and LAN port LEDs Each of these areas is discussed below. Chassis Front The following figure shows the front of the chassis with the snap-on bezel in place.
Front Panel The front panel is located at the right side of the server system, at the front of the chassis. The front control panel of the displays status lights for system status, hard drives, and power supplies. � � � ������� � � � ������� � � � �� ������� Figure 4. Front Panel Controls, Indicators, and Connectors Callout Control, Connector, Indicator Description A.
(continued) Callout Control, Connector, Indicator Description F. Hard Drive Fault LED (Amber) Indicates hard drive subsystem fault status. G, H. LAN1, LAN2 Status LEDs (Green) LED State Description Off Drive Missing Slot Empty, Online, Prepare for removal. On Inactive Drive Failed Blinking Inactive Drive Identity, Rebuild, Predictive Fail, Rebuild Interrupt or Rebuild on empty slot. Indicates LAN activity status.
Hot-swap Hard Drive Carrier The hot-swap hard drive carrier accepts 15,000-RPM and slower Ultra320 SCSI technology SCA-type hard drives. The peripheral bay supports Low Voltage Differential (LVD) SCSI disk drives only. SingleEnded (SE) SCSI devices are not supported in the peripheral bay. SE drives are only supported on the external SCSI connector. Hard drive carriers that accommodate 3.5-inch by 1.0-inch SCSI disk drives are required as part of the hot-swap implementation.
Removable Media Drive Bay ! CAUTION The DVD/CD-ROM drive cannot be hot-swapped. In order to add, remove or replace a DVD/CD-ROM drive, the system must be powered down, power sources unplugged and the top cover of the chassis must be removed to access the DVD/CD-ROM drive area. The slim-line DVD/CD-ROM drive is installed in a drive carrier that is inserted from the rear of the peripheral bay.
Power Supply Bay The power supply bay, shown below, is located in the lower front of the system. Redundant power status LED indicators are in the left portion of the power bay and three hot-swap power supply modules dock into the three bays on the right. ��� ��� ��� ����������� ������� � ������� � ������� Figure 8. Power Supply Bay A. Power status LEDs B.
A TP00304 Figure 9. AC Power Status LEDs LED Description AC1 (green) On - AC input #1 available. Off - AC input #1 unavailable or below voltage threshold to power up the system. AC2 (green) On - AC input #2 available. Off - AC input #2 unavailable or below voltage threshold to power up the system. ACR (green) On - redundant feature is available. Off - redundant feature is not available The power redundancy feature requires each of the following conditions be present.
Chassis Rear The figure below shows the rear of the system. � � � � � � � � � � � � � 1 2 � ������� Figure 10. Chassis Rear Features Callout Description A. Slot 2 Slot 3 PCI Slots Slot 1 100 MHz, 64-bit PCI-X slot, full length 100 MHz, 64-bit PCIX slot, full length 133 MHz, 64-bit PCIX slot, full length B. AC input power connectors (two) C. External SCSI connector1 D. System ID switch E. System ID LED (blue) F.
Internal Chassis Features ! WARNING Only qualified technical personnel should access any internal system component. Some exposed circuits exceed 240 VA and may cause injury if accidentally contacted.
Figure 12. Electronics Bay (sub-assembly removed) A. Processor pods (2 shown installed) B. Processors (2 shown installed) C.
Cooling Subsystem ! CAUTIONS The chassis top cover must be installed and closed for proper system cooling. Cooling components must be hot-swapped within a limited time period. This time period applies only to the time that the cooling component is removed from the system, not from the time of failure. The cooling subsystem consists of a hot-swap, redundant (5+1) system fan array installed in the fan bay.
The figure below shows the cooling subsystem layout with the airflow direction indicated. �� ��� ���� �� ��� ���� ��� ��� ����� ������� �� ��� ���� ���� ������ ���� ���� ���� ��� ���� ���� ��� ������� Figure 14. Cooling Subsystem Layout The server system supports only a fully populated system fan configuration. However, the system will continue to meet thermal specifications with either a system fan or a power supply failure.
NOTES Do not attempt to operate this system with less than a fully populated, six system fan configuration. To maintain adequate cooling for system components, the swap process must be completed in two-minutes. This period only applies to the time that the fan or power supply is removed from the system, not from the time of failure. A system fan failure is indicated by the corresponding fan LED and by the Cooling Fault LED on the front panel. The system fan LEDs are shown in the figure below.
Redundant AC Power Source Operation The power bay has two AC inlets, labeled AC1 and AC2, located at the rear of the chassis. AC1 is connected to the inputs of power supply module PS1. AC2 is connected to module PS2 and the redundant power module PS-Shared, through normally closed transfer switch contacts. • If AC1 input fails or exceeds the specified voltage range, AC2 will transfer power to the two modules located in the positions labled PS2 and PS-Shared.
2 Board Set Description This chapter highlights the main features of the board set.
Figure 16.
Main Board The main board connection layout is displayed in Figure 17.
� � � � � � � � � � � � � � � � � � � � � ������� Figure 17. Main Board Layout A. B. C. D. E. F. G. H. I. J. K. 32 Video connector COM2 connector Dual USB connector Dual gigabit Ethernet connector System ID LED System ID PB External SCSI connector VHDM 1 DIMM sockets 8, 4, 7, 3 from left to right DIMM sockets 6, 2, 5, 1 from left to right VHDM 0 L. M. N. O. P. Q. R. S. T. U.
Processor Sockets Each Intel® Itanium® 2 processor plugs into a 700-pin Zero Insertion Force (ZIF) socket. Each processor is powered by a 12 V power pod located adjacent to the processor on the main board. Attached to the top of each processor is a heat sink that dissipates thermal energy. Memory Subsystem The basic architecture of the memory subsystem is as follows: • The DIMMs reside on the main board, between the PCI riser assembly and the chassis.
NOTE The BIOS automatically detects, sizes, and initializes the memory array, depending on the type, size, and speed of the installed DIMMs. The BIOS reports memory size and allocation to the system through configuration registers. The system does not support mixed-sized DIMMs or DIMMs from different vendors within the same row. DIMMs must be populated in groups of four, referred to as a row. Row 1 consists of DIMM sockets 1-4 and row 2 consists of DIMM sockets 5-8.
IDE Controller The IDE controller is contained within the Intel® ICH4 (82801DA). The IDE controller is a multifunction device on the I/O board that acts as a PCI-based Fast IDE controller.
• Fault resilient booting • System management watchdog timer • Front panel system diagnostic-interrupt handling • Platform Management Interruption / System Diagnostic Interrupt status monitor • Event receiver • System interface to the IPMB (via system interface ports) • IPMI Management Controller Initialization Agent • Emergency Management Port interface • Serial/modem and LAN alerting The firmware for the BMC is field-upgradeable using the Firmware Update utility.
SCSI Backplane Board The SCSI backplane board connection layout is shown in Figure 20. The SCSI backplane board communicates with the main board via a 68-pin SCSI cable and to the Front Panel board via a 20-pin ribbon cable. It contains two industry standard 80-pin Single Connector Attachment (SCA)-2 connectors for hot-swap hard drives. Ultra320 or lower SCSI technology SCA type hard drives can be installed in this carrier. The backplane board accepts hard drives up to 15,000-RPM.
� � � � � � ������� Figure 20. SCSI Backplane Board Layout A. Power bay connector D. SCSI connector to main board B. SCSI drive 1 connector E. Front panel ribbon cable connector C. SCSI drive 2 connector F. Front panel power connector QLogic GEM359 SCSI Hot-swap Controller The QLogic GEM359 Hot-swap Controller resides on the SCSI backplane board.
Front Panel Board The front panel board connection layout is displayed in Figure 21.
3 Configuration Software and Utilities Utilities / Drivers on Resource CD The Resource CD included with your server system includes the following utilities and drivers that can be used to configure your system: • LSI Logic SCSI Driver for Linux (64-bit) and Microsoft® Windows® 2003 Server • Utilities: – FRUSDR Loader – EFI Platform Diagnostics – System Maintenance Utility (SMU) • SDRViewer • SELViewer • EFI Configuration Tool The Resource CD includes a menu driven program that can be used for the
Power-on Sequence and Power-on Self-Test (POST) Turning on the system causes POST to run and control to pass to the boot manager. From the boot manager, you can choose to invoke the Extensible Firmware Interface (EFI) Shell or you can choose to go to the Boot Maintenance menu. The system follows the steps below when you press the power button on the front control panel to power up the server: 1. The server fans start. 2. POST begins running. POST is stored in flash memory.
Table 4. Boot Maintenance Menu Options Option Description Boot from a File Automatically adds EFI applications as boot options or allows you to boot from a specific file. When you choose this option, the system searches for an EFI directory in all EFI System Partitions in the system. For each EFI directory that the system finds, it searches through that directory’s subdirectories for the first file that is an executable EFI application.
Table 4. Boot Maintenance Menu Options (continued) Option Description Manage BootNext Setting This feature allows you to select a boot option to use one time (the next boot operation). To manage boot next setting: • • • • • • Set Auto Boot Timeout At the menu, select Manage Boot Next Setting with the arrow key. Select the Option to boot next with the arrow key. Press to make this option the next boot option. Press to reset. Select Save to NVRAM. Select Exit to return to the Boot Manager.
The Extensible Firmware Interface (EFI) Shell The EFI shell application allows other EFI applications to be launched, EFI device drivers to be loaded, and operating systems to be booted. The combination of the EFI firmware and the EFI shell provides an environment that can be modified to easily adapt to many different hardware configurations. The EFI shell provides a set of basic commands used to manage files and EFI NVRAM shell and boot variables. A list of these basic commands is shown in Table 5.
Table 5.
Table 5. EFI Shell Commands (continued) Command Description stall microseconds Delays for the specified number of microseconds time [hh:mm:ss] Gets or sets the time type [-a] [-u] [-b] file Displays the contents of a file ver Displays version information vol fs [volume_label] Sets or displays a volume label CMOS Clear The CMOS must be cleared after the BIOS is updated. If using the automated System Update Package (SUP), the script will automatically clear the CMOS after the BIOS is updated.
8. Power down the server by pressing and holding the power button on the front control panel. To do so, hold down the power button for several seconds. 9. Unplug both power cords from the server. 10. Move the jumper at J5H3 from pins 2-3 to pins 1-2. 11. Install the chassis cover. See “Removing and Installing the Top Cover”. 12. Plug the power cords back in. 13. Power on the server by pressing and holding the power button on the front control panel.
BIOS Setup This section describes the BIOS Setup Utility, which is used to change the server configuration defaults. You can run the utility with or without an operating system present on the server. Setup stores most of the configuration values in battery-backed CMOS and the rest in flash memory. The values take effect when you boot the server. POST uses these values to configure the hardware.
Table 6. Setup Screen Navigation Press To ← Scroll left through the main menu screens. → Scroll right through the main menu screens. ENTER Select a sub-menu item or accept a drop-down choice. TAB Select a field within a value (for example, date field). F9 Select the default value. F10 Save your changes and exit Setup. ESC Go back to a previous screen. ↑ Scroll up through menu items or value lists. ↓ Scroll down through menu items or value lists.
Table 8. Processor Settings Submenu Items Menu Item Default Value Description Processor Retest [No] Yes If yes, BIOS clears historical processor status and retests all processors on the next boot. Processor POST speed setting Information Only Displays measured processor speed. Shows common operating processor speed. Processor 1 CPUID N/A Reports CPUID for Processor 1. Processor 1 L1 Cache Size N/A Reports L1 Cache Size for Processor 1.
Security Table 10 describes the menu items available on the Security screen. NOTE With the removal of legacy keyboard and mouse support, the legacy security core has been removed. Therefore, the security menu is brief as compared to other server products. The two-level password has been replaced with a single-level password. Table 10. BIOS Setup Security Screen Menu Items Menu Item Default Value Description Administrator Password Is [Not Installed] Clear Status only.
Table 12. Setup Console Redirection Sub Menu Items Sub Menu Item Default Value Description Serial Console Redirection [Disabled] Enabled When enabled, Console Redirection uses only COM2. Choosing “Disabled” completely disables Console Redirection. Serial Port No entry Hardcoded value is COM2 2F8 IRQ3. If console redirection is enabled, then the Base I/O address and IRQ selection of Serial Port B should match this serial port setting under the Console Redirection submenu.
Exit Table 13 describes the menu items available on the Exit screen. Default values appear in brackets. Table 13. BIOS Setup Exit Screen Menu Items 54 Menu Item Description Exit Saving Changes Lets you exit Setup with or without saving your changes in CMOS. Clicking on the menu item causes the system to prompt you for a Yes or No response. Yes Saves your changes and exits the utility. No Discards your changes and exits the utility.
LSI Logic SCSI Utility Launching the LSI SCSI Utility To launch the LSI SCSI utility from the Resource CD: 1. The utility will auto-run if the server is booted with the CD in the CD-ROM/DVD-ROM drive. Otherwise, choose Startup.nsh from the root of CD-ROM/DVD-ROM drive. 2. After the CD menu is launched, select Utility at the top of the Main menu screen. 3. Select EFI config tool from the drop-down selections 4. Select PCI Device from the top of the next screen that is displayed. 5.
Figure 22. LSI SCSI Utility Main Menu 4. Use the arrow keys to highlight <53C1030 Bus3 Dev1 Fnc1>; press to select this adapter. The screen clears and the following message is displayed: Scanning for devices… 5. Use the arrow keys to highlight Device Properties; press to view and change the device properties. As shown by Figure 23, the screen displayed shows a list of devices found on the internal channel. Information includes the SCSI IDs and associated settings. Figure 23.
6. Make appropriate changes to any options that are displayed by bright white type on the screen. 7. Press to return to the Adapter Properties menu. 8. Use the arrow keys to highlight RAID Properties; press to select RAID Properties. 9. Use the arrow keys to highlight Modify; press to select Modify. 10. Use the arrow keys to select Disk 0 press the <+> key in the Array Disk field to change the selection to “Yes.” 10.
The SMU core components are installed as part of the service partition software installation process and the remote SMU application is part of the Intel® Server Management installation. SMU files are copied to a directory specified during that installation process. It is also possible to run the local SMU application from a CD without installing a service partition. The SMU software consists of a user interface and core components.
Table 15. Keyboard Support for Local SMU Client (continued) Key Function key If a horizontal scroll bar is in the active pane, pressing scrolls the display left. key If a horizontal scroll bar is in the active pane, pressing scrolls the display right. key If a vertical scroll bar is in the active pane, pressing scrolls the display up. key If a vertical scroll bar is in the active pane, pressing scrolls the display down.
The About box contains an Advanced button that can be used to show version information for components related to the SMU application. See the example below. Figure 25. SMU Application About Box (Advanced button selected) Server Discovery The remote SMU application requires that the Intel® Server Management software be installed on the client system. When the ISM software is run, it performs a discovery of all servers that support tools available within ISM.
Figure 26. Service Partition Utilities The remote SMU application attempts to establish a socket connection to the server and uses the Service Partition Utilities services to execute the server-side SMU core components. If a connection is established, the application sends information to the SMU core components to request a session. If the connection fails, a dialog box is displayed to indicate an error condition. In the event of an error, you can attempt to restart the SMU from the ISM console.
After the session between the SMU application and the core components is established, the window below is displayed. The primary information pane at the right directs you to select an activity from the task pane at the left. Figure 27. SMU Home Local SMU Application The local SMU application and the core components exchange XML documents using a procedural interface. There is no socket connection between the application and the core components.
Running from the System Partition To run the SMU application from a service partition on which it has been installed, follow the steps below: 1. If an EFI shell prompt is available on the local console and the files on the system partition can be accessed, skip to step 3. 2. Reset the server and boot to the EFI shell. 3. Locate the file system (e.g. fs0:, fs1:) that contains the service partition software and change directory to \efi\service\smu. 4. Run smu.efi.
Sub-tasks can be made up of one or more screens, depending on the server management configuration settings you enabled. Buttons that are common to the server management configuration tasks are described in Table 16. Table 16. Common Buttons for Configuration Management Sub-tasks Button Description Save Causes the current values of the settings in the current sub-task to be stored in non-volatile memory on the server.
Default LAN Configuration Settings Set by the SMU The SMU automatically configures some server management firmware settings. These are not displayed on the screen above, but are listed below. Before these settings are set by the SMU, you must click through each LAN configuration screen by clicking the Next button until you reach the Save button on the final LAN configuration screen.
Host IP Address This edit box is for the logical or Internet address of the host. The IP address is required when DHCP is disabled. The IP address is entered as a dotted notation, such as 192.168.0.2. Subnet Mask The edit box is for the host’s subnet mask. The server uses this to decide if alert destinations are in the local subnet or in another subnet relative to the client console. The Subnet Mask is required when DHCP is disabled. The Subnet Mask is entered as a dotted notation, such as 255.255.0.0.
Automatically Resolve Backup Gateway MAC Address This check box allows you to specify whether the BMC should automatically attempt to resolve the MAC address of the backup gateway router. This box is checked by default unless the MAC address edit box appears to include a valid MAC address. If this box is not checked, you must provide the MAC address in the Backup Gateway MAC Address field. When the OK button is clicked, the firmware attempts to resolve the gateway MAC address.
Alert Settings Up to four LAN alert destinations can be configured. When one or more IP addresses are configured as alert destinations, this part of the screen shows those addresses, along with the following associated configuration settings: • Gateway IP address for the destination IP address. • Whether alert acknowledge is enabled for the alerts sent to this destination. • The number of times the alert will be retried. • The interval in milliseconds between retries.
Destination IP Address This edit box allows you to enter the IP address to which an alert is to be sent. The IP address is entered as a dotted notation, such as 192.168.0.2. The SMU does not check whether an IP address matches a previously entered address. Destination MAC Address This edit box is used to enter the MAC address of the destination machine to which the alert should be sent. This box is used when the destination IP address is outside the subnet that the server is on.
Serial Over LAN Configuration The Serial Over LAN screen is displayed after you click Next on the LAN Alert Configuration screen. The Serial Over LAN screen, shown in the following diagram, allows you to configure the operation of the serial over LAN capability of the BMC. The SMU sets up the SOL configuration such that SOL packets do not have to be authenticated. This enhances the performance of an SOL session. Figure 31.
User Configuration Sub-task The User Configuration sub-task provides a way to configure the user access to the LAN and Serial/ Modem channels. Up to four users are allowed. Some of the options presented in these screens depend on how the channels have been configured; therefore, the channels should be configured before you access these settings. Sessions allow a framework for user authentication and allow multiple IPMI messaging streams on a single channel.
Figure 33. Edit User Configuration After editing the user information, click OK to return to the User Configuration screen. Enable User This check box is used to enable you to attempt to have access to the available channels. Leaving the box unchecked disables the user, preventing that user from accessing the channels. Enter Username This edit box is used to enter an out-of-band username.
Note that if the Clear Password check box is checked, these two edit boxes are disabled. If a user password is currently set, the SMU user is not required to enter the current password before changing it. User Privilege Level for LAN Channels This combo box allows you to select the privilege level for LAN channel. The global privilege level set for LAN channel access takes precedence over the user privilege level.
Enable PEF This option is used to globally enable or disable platform event filtering. Enable SEL Event Messages for PEF Actions When this option is checked, each action triggered by a filter generates an event message for the action. This allows the occurrence of PEF-triggered events to be logged in the System Event Log if event logging is enabled. PEF Startup Delay This option is used to configure the time in seconds to delay platform event filtering after a system power up or reset.
Figure 35. Event Filter Settings If you click in one of the radio buttons and then click Edit, the Edit Event Filter Settings screen is displayed for the selected event filter. After completing this screen, click Next to move to the next screen to continue this sub-task. Edit Event Filter Settings The screen shown below is displayed after the Edit button is clicked on the Event Filters Settings screen. Figure 36.
Enable Alerts This check box causes an alert to be sent when an event associated with the selected event filter occurs. If the box is not checked, or if the global enable for alerts is not enabled, no alert is sent. Policy Number Associated With This Event Filter This drop-down box allows you to specify an alert policy number to be associated with the event filter. This setting is enabled only if the Enable Alerts box is checked; a valid policy number must be chosen if alerts are enabled.
Figure 37. Alert Policy Configuration After completing this screen, click Save to complete this sub-task. The settings shown for each table entry are: • Alert policy number • Status indicating whether the table entry is enabled or disabled. • Policy type determines how the firmware processes multiple entries that have the same policy number • Channel on which the alert corresponding to the table entry would be sent. • Destination IP address or phone number of the alert.
Edit Alert Policy Entry When you select an alert policy on the Alert Policy Configuration screen and then click the Edit button, you will see the Edit Alert Policy Entry screen, as shown below. Changes made on this screen apply to the alert policy selected when you clicked Edit. After you click OK on this screen, you are returned to the Alert Policy Configuration screen Figure 38. Edit Alert Policy Entry After completing this screen, click Ok to return to the Alert Policy Configuration screen.
• D: If the alert to the previous destination was successful, do not send an alert to the destination referenced in the current policy table entry. Instead, proceed to the next policy table entry that has the same policy number, but has a different channel destination. • E: If the alert to the previous destination was successful, do not send an alert to the destination referenced in the current policy table entry.
Default Serial/Modem Configuration Settings Set By the SMU The SMU sets some serial/modem configuration settings automatically. This information is listed below, but is not displayed on the screen. The list of these settings is given below. Before this information is set by the SMU, you must click through the remaining Serial/Modem Channel Configuration sub-task screens to click the Save button on the last screen. • Authentication type enables are enabled.
Privilege Level Limit This is the maximum privilege level that users can have on this channel. It restricts users of the channel to a set of BMC commands that can be issued at that privilege level. For example, if the channel privilege limit is configured with a maximum privilege level of Operator, and a user is configured to have Administrator privilege, that user can still only execute Operator level commands over this channel.
Modem Escape Sequence Enter the ASCII escape string to be sent to the modem before sending a command string. This string can be up to five characters long and is typically set to +++. If this field is left empty, the BMC uses +++. The modem escape sequence is not sent to the modem if DTR Hang-up is enabled on the initial Serial/Modem Channel Configuration Sub-task screen. Hang-up Sequence Enter the ASCII string that is sent to the modem to terminate the session.
Destination Dial Strings The screen shown below displays the current setting of each destination dial string available on the target platform. For the Server System MAXDATA PLATINUM 9000-2R, up to six dial strings can be configured. A dial string can be modified or cleared by selecting the corresponding radio button and then clicking on the Edit button. Figure 41. Destination Dial Settings After completing this screen, click Next to move to the next screen to continue this sub-task.
New/Edit Dial String The New/Edit Dial String screen is displayed when you click either New or Edit on the Destination Dial Strings screen. The New/Edit Dial String screen allows you to configure or change the settings related to dial string to which alerts are to be sent. The screen displayed either to configure a new dial string or to edit an existing dial string is the same, except that when editing an existing dial string, the current settings for that dial string are displayed.
Page Destination Configuration The Page Destination Configuration screen, shown below, is displayed when you click Next on the Destination Dial Strings screen. This screen allows you to configure the settings for each page destination that can be reached by sending a page through the serial/modem channel. Up to eight page destinations can be configured; the Dial String column displays Not Configured for any entry that has not been configured.
Page Blackout Interval The Page Blackout Interval determines the minimum number of minutes between pages. It provides a way to prevent back-to-back pages if a rapid series of events occurs. This parameter is entered in minutes; a value of 0 indicates no blackout. Enter a value between 0 and 255. Call Retry Interval This setting gives the number of seconds between call retries when a busy signal is detected. Enter a value between 0 and 255.
Data Bits This drop-down determines the number of data bits to use when transmitting page data. The choices are 7 or 8 data bits. Parity This drop-down determines the parity type that is used when transmitting the page data. The choices are None, Odd, or Even. Call Retries This edit box is the number of times to retry calling the destination specified by the destination dial string. A value of zero indicates no retries (the call is only made once). Enter a value between 0 and 7.
Enable Line Editing This check box enables or disables line editing during a terminal mode session if checked. Line editing is enabled with the box is checked. When line editing is enabled, echo should also be enabled. When line editing is enabled: • The or key can be used to delete the last character entered. • The key can be used to delete an entire line.
Power Configuration Sub-task The Power Configuration sub-task allows you to configure the power restore policy for the server. The power restore policy determines the action that the system takes when power is removed and then reapplied. This screen is shown below. Figure 46. Power Configuration After completing this screen, click Save to complete this sub-task. The selected radio button is the current setting.
SEL Viewer NOTE The SEL Viewer task is available only on the local version of the SMU. This task is not available when running the remote version of the SMU. The SEL Viewer task allows you to view the System Event Log. The SEL Viewer task supports the following: • Viewing the BMC SEL • Saving a log to a file • Viewing a saved log file • Viewing the SEL properties • Clearing the BMC SEL The SEL Viewer is started by clicking the SEL task in the task pane of the SMU.
Viewing Events in the SEL When the SEL Viewer is opened, the first page of events is loaded from the log and displayed. To view the remaining events you are provided with a series of buttons along the bottom of the screen. You can use the key to access the screen buttons.
Home Button The Home button displays the first segment of events. This button is disabled if the first event is displayed. End Button The End button displays the last segment of events. The number of events on this page varies based on the number of entries in the log; it may not fill the screen. This button is disabled if the last event is displayed. Previous Button This Previous button displays the prior segment of records. This button is disabled if the first event is displayed.
Save Log Button This allows you to save the currently loaded SEL to a file. The user can choose to save the SEL as the decoded event data or as hexadecimal format. A different file extension is used for each type. In each case, the SEL properties and the entire log are written to the file. The SEL properties are saved at the top of the file and are saved as verbose text.
Display as Hex Button This button is only visible when the SEL is displayed in verbose mode. This will change the event display to Hex mode. Display as Text Button This button is only visible when the SEL is displayed in Hex mode. This will change the event display to text mode. SDR Viewer The SDR task allows you to view the current system SDR records stored in the BMC. It also provides the interface to opening and saving SDR files, and to viewing the SDR properties.
The SDR tree retains its expanded/collapsed state for each of the branches until the SDRs are reloaded or until the application is exited. If the tree view goes beyond the size of the screen a vertical scroll bar is added to allow you to view all SDRs. Viewing SDRs SDR records can only be viewed one at a time. They are opened by clicking on the SDR in the SDR tree. No other actions are allowed once an SDR is opened for viewing.
The SDR type displays names in a single format: [SDR type hex] – [SDR type text] ([count of SDRs of this type]). Under certain circumstances, the type C0 format does not follow the rules defined above. When all the characters of the data portion of the record are printable ASCII characters, the data area is considered to be a string and is used for the display name instead of the format defined in the table. Close Button This button closes the current SDR window and returns you to the SDR selection screen.
The FRU Viewer allows you to view the current system FRUs on the target system. The FRU Viewer task supports the following: • Viewing the current system FRUs • Viewing the current system FRU properties. • Saving the selected FRU to a file • Viewing a saved FRU file When you select the view records sub-task from the FRU menu, it immediately retrieves the system FRUs. In order to discover the system FRUs, the viewer must first scan the system SDRs and search the records for FRU locations.
Figure 49. FRU Viewer Save To File Button This button allows you to save the currently displayed FRU to a file. If the save fails because the file cannot be created, this message is displayed: Unable to create save file If an error occurs while writing information to the file, this message is displayed: Error saving the FRU data to the file Open File Button This button allows you to load a currently saved FRU file.
Reload Button This will clear the currently loaded FRUs and refresh the FRUs from the system. This load procedure is identical to the load procedure when the viewer is opened. Help Button This displays the SMU context sensitive help for the FRU Viewer. Task Error Handling During the execution of a task, it is possible for errors to occur. These errors may be handled in different ways depending on the type of error. This chapter describes how error handling operates during SMU task execution.
Help Help for the Remote SMU Application Help for the remote SMU application is HTML-based. This means SMU help is displayed in a separate instance of a browser. See the figure below for a sample help screen. Figure 50. Remote SMU Help Window (browser based) ISM Front-end Help The front-end ISM help subsystem contains general information on the SMU. This help system does not provide details related to the screens displayed by the SMU.
If a help browser window was previously launched from the Contents task of the SMU application, then when a Help button on an SMU screen is clicked, the information pane is replaced with the context-sensitive help for the screen containing the Help button. Help for the Local SMU Application Help for the local SMU application appears in a modeless window on the client console. This means that when you want to return to the local SMU application, click on the application window to bring it to the foreground.
EFI Platform Diagnostic Tests EFI Platform Diagnostic Tests allow you to quickly assess the server’s hardware status, view test logs, and determine the server’s current configuration. You can run EFI Platform Diagnostic Tests from within the EFI environment. Starting the Application Use the following steps to setup and run tests. NOTE You can also run this utility from the Resource CD.
Understanding Basic Testing The Platform Test menu is set up in the order that is typically used: • Test Setup allows you to determine which tests to run and how thoroughly to test. • Run Test starts test execution and provides some indication of test progress. • View Results shows the results window and allows you to view and clear the test log. Enabling Tests For Execution To enable one or more tests for execution, select Test setup from the Platform Test menu.
Viewing System Information To view system information, use the arrow keys to highlight the menu item, and press the key. From the menu select the system information to be viewed. After pressing the key, you will see a scrollable information box that contains system information. Viewing the Test Log By default, the diagnostic software keeps the log file in efi\service\diagnostics\fielddiags.log. To view this file, use the arrow keys to highlight the Platform Test menu.
Installing the Files Follow these steps to install the service partition files onto a managed server whose operating system is already installed: 1. Insert the System Resource CD into the managed server’s CD-ROM drive. If you do so, follow the instructions included with the software package to install the service partition. 2. Boot the system into the EFI Shell; the EFI CD menu program launches automatically.
Console Redirection The BIOS supports redirection of video output and keyboard input via serial link. This section details the serial redirection scheme. For redirection over LAN (Serial over LAN or SOL), see the ISM online help. When console redirection is enabled, local (host server) keyboard input and video output are passed both to the local keyboard and video connections, and to the remote console via the serial link.
Keystroke Mappings During console redirection, the remote terminal sends keystrokes to the local server. The local server passes video back over this same link. For keys that have an ASCII mapping, such as and , the remote sends the ASCII character. For keys that do not have an ASCII mapping, such as and , the remote sends a string of characters, as defined in the tables below. The strings are based on the ANSI terminal standard.
Table 19. Non-ASCII Key Mappings (continued) Key Normal Shift Ctrl Alt Pg Down ^[[2J NS NS NS Up Arrow ^[[A NS NS NS Down Arrow ^[[B NS NS NS Right Arrow ^[[C NS NS NS Left Arrow ^[[D NS NS NS Tab (09h) NS NS NS NS = Not supported (xxh) = ASCII character xx Table 20.
Limitations Console redirection is a real-mode BIOS extension and has been modified to transition into EFI space. The transition is actually a parameter-passing exercise whereby the serial redirection scheme native to the EFI takes over using the settings established in BIOS Setup. Video is redirected by scanning for, and sending changes to, text video memory across the redirection channel. Therefore, console redirection cannot redirect video in graphics mode.
Console Configuration 1. Boot the console into the operating system. 2. Launch HyperTerminal by clicking on the Start button in the task bar. 3. Select Programs>Accessories>Communications and click HyperTerminal. 4. At the Connection Description window, enter guest for the name and click OK. 5. At the Connect To window, select the COM port of the console where the null modem is connected. In this example, it is COM1. 6.
Hardware Setup Hardware setup is dependent upon the type of connection mechanism being employed as follows: • For a direct connection, a null modem cable is needed to connect the local host to the target system • For a modem connection, the local host and target systems must both be connected to modems via serial cables Configuration Using System Maintenance Utility (SMU) Configuration of terminal mode requires proper configuration of the following: • The serial channel • User login information (user
Server Configuration 1. Run the SMU to configure the BMC. 2. In the Navigation Pane at the left side of the SMU, click Serial/Modem to go to the Serial/ Modem configuration menu. 3. At the Connection Mode box, pull down the menu and select Direct Connect Mode. 4. Select Always Available for the Access Mode. 5. Select Administrator for the Privilege Level Limit. 6. Select None for Flow Control. 7. Leave the Enable Data Terminal Ready box unselected. 8. Select 19200 for the Baud Rate. 9.
Console Configuration 1. Boot the console into the operating system. 2. Launch HyperTerminal by clicking the Start button in the task bar. 3. Select Programs>Accessories>Communications and click HyperTerminal. 4. At the Connection Description window, enter guest for the name and click OK. 5. At the Connect To window, select the COM port of the console that the null modem is connected. In this example, it is COM1. 6.
Terminal Mode Commands Input Restrictions Terminal mode messages are bound by the restrictions listed below.
Hex-ASCII Command Format Binary IPMI commands are sent and received as a series of case insensitive hex-ASCII pairs, where each is optionally separated from the preceding pair by a single character. The following is an example of a binary IPMI request message: [18 00 22] The software ID and LUN for the remote console are fixed and implied by the command. The SWID for messages to the remote console is always 47h, and the Logical Unit Number (LUN) is 00b.
Terminal Mode IPMI Message Bridging Terminal mode supports the ability to bridge IPMI messages to another interface when binary hexASCII IPMI commands are used. The message bridge is determined by the following: • The bridge field • Whether the message is a request or a response • The message direction with respect to the BMC and the LUN. Table 23 lists the supported BMC combinations for IPMI message bridging. No other combinations are supported.
Table 24. Terminal Mode Text Commands (continued) Command Switches Description SYS TMODE Used as a no-op confirm that Terminal Mode is active. BMC returns an OK response followed by TMODE. SYS SET BOOT XX YY ZZ AA BB Sets the boot flags to direct a boot to the specified device following the next IPMI command or action initiated reset or power-on. XX…BB represent five hex-ASCII encoded bytes, which are the boot flags parameter in the Boot Option Parameters. See Table 25 for information.
Table 24. Terminal Mode Text Commands (continued) Command Switches Description -N XX YY This command sets the non-volatile Terminal Mode Configuration. XX and YY represent hex-ASCII encodings for data bytes 1 and 2 as specified in Table 26. The BMC returns the same output as for SYS SET TCFG, above. SYS RESET Directs the BMC to perform an immediate system hard reset. SYS POWER OFF Directs the BMC to perform an immediate system power off.
Table 25. Boot Option Parameters Parameter # Parameter Data (non-volatile unless otherwise noted) Set In Progress (volatile) 0 Data 1 - This parameter is used to indicate when any of the following parameters are being updated, and when the updates are completed. The bit is primarily provided to alert software that some other software or utility is in the process of making changes to the data. The change shall take effect when the write occurs. [7:2] - Reserved [1:0] - 00b = Set complete.
Table 25. Boot Option Parameters (continued) Parameter # Parameter Data (non-volatile unless otherwise noted) Boot info acknowledge (semi-volatile)[1] 4 These flags are used to allow individual parties to track whether they have seen and handled the boot information. Applications that deal with boot information should check the boot info and clear their corresponding bit after consuming the boot options data. Data 1: Write Mask (Write-only: This field is returned as 00h when read.
Table 25. Boot Option Parameters (continued) Parameter # Parameter Data (non-volatile unless otherwise noted) Boot flags (semi-volatile)[1] (continued) 5 Data 3 [7] - 1b = Lock out (power off/ sleep request) via power button [6:5] - Firmware (BIOS) Verbosity (Directs what appears on POST display) 00b = System default 01b = Request quiet display 10b = Request verbose display 11b = reserved [4] - 1b = Force progress event traps.
Table 25. Boot Option Parameters (continued) Parameter # Parameter Data (non-volatile unless otherwise noted) Boot initiator info (semi-volatile)[1] 6 Address & Identity information for the party that initiated the boot. The party that initiates the boot writes this parameter and the boot info acknowledge parameter prior to issuing the command that causes the system power up, power cycle, or reset. This data is written by the remote console application, not the BMC. Boot Source Data 1- Channel Number.
Table 26.
4 Technical Reference Figure 52.
System Interconnection The table below lists the system connectors. The system connectors are used to connect to mains power, supply power, and signals throughout the board set, and to provide interface with external components. Table 27.
Table 27.
Video Port The main and front panel boards provide a video port interface with a standard VGA-compatible, 15-pin connector. Only one port is enabled at a time through auto detection of a connected monitor. Onboard video is supplied by an ATI Rage XL video controller with 8 MB of onboard video SDRAM. Table 29.
Ethernet Connector The main board provides a dual-RJ45 connector (JA4A1) for Ethernet connection. Below are definitions of the speed/status LEDs. • Speed LED: Yellow On, 1000-Mbps Ethernet • Speed LED: Green On, 100-Mbps Ethernet • Speed LED: Off, 10-Mbps Ethernet • Status LED: Green On, Ethernet link detected • Status LED: Off, Ethernet link not found • Status LED: Green Flashing, Ethernet data activity Table 31.
Table 31.
Ultra320 SCA-2 HDD Connector The SCSI backplane board provides two SCA-2 (80 pin) connectors for hot-swapping Ultra320 hard drives. These SCSI ports are controlled by SCSI port 1 of the LSI53C1030 LVDS controller component located on the main board. Table 32.
Table 32.
Table 33. External Ultra320 SCSI Connector Pinout (continued) Signal Name Pin +ATN Ultra320 SCSI Connector Pin Signal Name 21 55 -ATN GND 22 56 GND +BSY 23 57 -BSY +ACK 24 58 -ACK +RST 25 59 -RST +MSG 26 60 -MSG +SEL 27 61 -SEL +C/D 28 62 -C/D +REQ 29 63 -REQ +I/O 30 64 -I/O +DB(8) 31 65 -DB(8) +DB(9) 32 66 -DB(9) +DB(10) 33 67 -DB(10) +DB(11) 34 68 -DB(11) AC Power Input Two IEC320-C14 15A receptacles are provided at the rear of the server.
3. Power down the system by pressing and holding for several seconds the power button on the front of the chassis. After the server shuts down, unplug both AC power cords to remove standby power from the server. 4. Open the chassis and access the board with the appropriate jumper. Locate the configuration jumper blocks on the board. For specific jumper block locations, refer to the remaining sections in this chapter. 5. Move jumper to pins specified for the required setting.
POST Error Codes and Messages In order to indicate progress through BIOS POST, and in special cases where errors are encountered during BIOS POST, there are three common mechanisms that shall be employed by the server system BIOS. The first method is to display port 80/81 codes to an I2C adapter connected to the main board. The second common method is the use of beep codes, encoded beep sequences emitted by the PC speaker when an error is encountered.
Table 35.
Table 35.
Specific POST Code Modules SAL-A Module The SAL-A POST codes are defined in the following table. Table 36.
Table 36.
SAL-B Module Table 37. SAL-B POST Codes Code Number BSP, APs, Both Meaning Display 0x87FF BSP+APs First check point. Initialize cr.iva/ar.eflag/ar.cflg/cr.lrr0/ cr.lrr1/cr.ifa/cr.itir South 0x87FE BSP only And BSP+APs Initialize io_base address, CPU#, health, etc. for CPUs. Initialize min_state_area for all CPUs (cpu_data_ base+cpu_bspstore_base+cpu_health)cpu_data_base points to min state save area. TOM below and above 4G.
Table 37. SAL-B POST Codes (continued) Code Number BSP, APs, Both Meaning Display 0x07F5 BSP only Then hang, if not found or Information ERROR. SAL shadow bottom (PELoader + SAL_F) Find SAL_F page size. Align to next 32K boundary and save address and size. South 0x87F4 BSP only Search for addition information SAL_F module Initialize scratch buffer. South 0x07F4 BSP only Then hang, if not found. Else continue by saving in RAM. South 0x87F3 BSP only Cache flush after SAL shadowed.
Table 37. SAL-B POST Codes (continued) 142 Code Number BSP, APs, Both Meaning Display 0x87EA BSP+APs Cache flush shadow. South 0x07EA BSP + APs Hang on ERROR. South 0x87E9 BSP + APs PAL call for memory Test for SELF TEST(pal_mem_for_ test_25). South 0x07E9 BSP + APs Hang, if Memory ERROR. South 0x87E8 BSP + APs PAL call for PAL test (pal_test_proc_102) and save results. South 0x07E8 BSP + APs Hang, if late self test ERROR NOTE: this can be skipped by a build switch.
SAL-F Module Table 38. SAL-F POST Codes Code Value BSP, APs, Both Meaning Display 0x87BF BSP First check point. Check point in v6b00_83_ip2x. Update EBDA entry inside SST. Create EFI memory descriptor Update SST checksum. South 0x87BE BSP Check point near v6b00_83_5. Search FIT for ACPI module (SAL_ C_module_17) and get size, align, scratch buff size. South 0x07BE BSP Hang if ERROR. South 0x87BD BSP Load image by module type (sal_c_module_17). Use PELoader.
IA-32 Module The IA-32 POST codes all have the Most Significant Bit (MSB) cleared by the convention established above in this document. The IA-32 POST codes do not fall into the module definition for Itanium®based platforms. The codes shown here are consistent with the 7.0 AMI core. Table 39. IA-32 POST Codes Code Value Module Display 0x00D0 Power-on delay is starting. Next, the initialization code checksum will be verified.
Table 39. IA-32 POST Codes (continued) Code Value Module Display 0x0024 The configuration required before interrupt vector initialization has completed. Interrupt vector initialization is about to begin. South 0x0025 Interrupt vector initialization is done. Clearing the password if the POST DIAG switch is on. South 0x0027 Any initialization before setting video mode will be done next. South 0x0028 Initialization before setting the video mode is complete.
Table 39. IA-32 POST Codes (continued) Code Value Module Display 0x0082 The keyboard controller interface test completed. Write the command byte and initializing the circular buffer next. South 0x0083 The command byte was written and global data initialization has completed. Checking for a locked key next. South 0x0084 Locked key checking is over. Identify ATAPI devices.
Table 39. IA-32 POST Codes (continued) Code Value Module Display 0x00A9 Returned from adaptor ROM at E000h control. Performing any initialization required after the E000 option ROM had control next. South 0x00AA Initialization after E000 option ROM control has completed. Displaying the system configuration. South 0x00B1 Copying any runtime code to specific areas. South 0x0000 Code copying to specific areas is done. Pass control to EFI. South Table 40.
Recovery Port 80 Codes Table 42. Recovery POST Codes Code Value Module Display 0x8EC0 Recovery Process Started South 0x8EC1 Searching for Recovery Media South 0x8EC2 Loading Recovery File South 0x8EC3 Validating Recovery File South 0x8EC4 Unlocking Flash Devices South 0x8EC5 Erasing Flash Contents South 0x8EC6 Programming Flash Contents South 0x8EC7 Validating Flash Contents South 0x8EC8 Recovery Process Complete South 0xCEC1/ 0x8EC1 Recovery Reading error (display toggles).
Table 43.
Table 43. POST Error Messages and Codes (continued) Error Code Error Message Attributes Pause on Boot 8500 Multi-bit Error Detected Row1. Row mapped out. WARN/YELLOW_BLACK Yes 8501 Multi-bit Error Detected Row2. Row mapped out. WARN/YELLOW_BLACK Yes 8504 Persistent Single-bit Error Detected Row1. Row mapped out. WARN/YELLOW_BLACK Yes 8505 Persistent Single-bit Error Detected Row2. Row mapped out. WARN/YELLOW_BLACK Yes 8508 Memory Mismatch detected Row1. Row mapped out.
Table 45. POST Memory Beep Error Codes – Debug Port Encoding List Beep Code Debug port error code (lower byte of North I2C debug display) Meanings 3 CF9Fh No valid memory was found in the system 3 CF64h Mismatched DIMMs in a row, and no valid memory to boot Memory Test Failure No Memory Found in the System This indicates that the memory test has found no valid memory in the system. The system will not boot. An SEL log entry is made.
Safety Warnings WARNING: English (US) AVERTISSEMENT: Français WARNUNG: Deutsch AVVERTENZA: Italiano ADVERTENCIAS: Español MAXDATA PLATINUM 90002R Server System 153
WARNING: English (US) The power supply in this product contains no user-serviceable parts. There may be more than one supply in this product. Refer servicing only to qualified personnel. Do not attempt to modify or use the supplied AC power cord if it is not the exact type required. A product with more than one power supply will have a separate AC power cord for each supply. The power button on the system does not turn off system AC power.
WARNING: English (continued) For proper cooling and airflow, always reinstall the chassis covers before turning on the system. Operating the system without the covers in place can damage system parts. To install the covers: 1. Check first to make sure you have not left loose tools or parts inside the system. 2. Check that cables, add-in boards, and other components are properly installed. 3. Attach the covers to the chassis with the screws removed earlier, and tighten them firmly. 4.
AVERTISSEMENT: Français Le bloc d’alimentation de ce produit ne contient aucune pièce pouvant être réparée par l’utilisateur. Ce produit peut contenir plus d’un bloc d’alimentation. Veuillez contacter un technicien qualifié en cas de problème. Ne pas essayer d‘utiliser ni modifier le câble d‘alimentation CA fourni, s‘il ne correspond pas exactement au type requis. Le nombre de câbles d‘alimentation CA fournis correspond au nombre de blocs d‘alimentation du produit.
AVERTISSEMENT: Français (suite) Afin de permettre le refroidissement et l’aération du système, réinstallez toujours les panneaux du boîtier avant de mettre le système sous tension. Le fonctionnement du système en l’absence des panneaux risque d’endommager ses pièces. Pour installer les panneaux, procédez comme suit: 1. Assurez-vous de ne pas avoir oublié d’outils ou de pièces démontées dans le système. 2. Assurez-vous que les câbles, les cartes d’extension et les autres composants sont bien installés. 3.
WARNUNG: Deutsch Benutzer können am Netzgerät dieses Produkts keine Reparaturen vornehmen. Das Produkt enthält möglicherweise mehrere Netzgeräte. Wartungsarbeiten müssen von qualifizierten Technikern ausgeführt werden. Versuchen Sie nicht, das mitgelieferte Netzkabel zu ändern oder zu verwenden, wenn es sich nicht genau um den erforderlichen Typ handelt. Ein Produkt mit mehreren Netzgeräten hat für jedes Netzgerät ein eigenes Netzkabel.
WARNUNG: Deutsch (Fortsetzung) Zur ordnungsgemäßen Kühlung und Lüftung muß die Gehäuseabdeckung immer wieder vor dem Einschalten installiert werden. Ein Betrieb des Systems ohne angebrachte Abdeckung kann Ihrem System oder Teile darin beschädigen. Um die Abdeckung wieder anzubringen: 1. Vergewissern Sie sich, daß Sie keine Werkzeuge oder Teile im Innern des Systems zurückgelassen haben. 2. Überprüfen Sie alle Kabel, Zusatzkarten und andere Komponenten auf ordnungsgemäßen Sitz und Installation. 3.
AVVERTENZA: Italiano Rivolgersi ad un tecnico specializzato per la riparazione dei componenti dell’alimentazione di questo prodotto. È possibile che il prodotto disponga di più fonti di alimentazione. Non modificare o utilizzare il cavo di alimentazione in c.a. fornito dal produttore, se non corrisponde esattamente al tipo richiesto. Ad ogni fonte di alimentazione corrisponde un cavo di alimentazione in c.a. separato.
AVVERTENZA: Italiano (continua) Per il giusto flusso dell’aria e raffreddamento del sistema, rimettere sempre le coperture del telaio prima di riaccendere il sistema. Operare il sistema senza le coperture al loro proprio posto potrebbe danneggiare i componenti del sistema. Per rimettere le coperture del telaio: 1. Controllare prima che non si siano lasciati degli attrezzi o dei componenti dentro il sistema. 2.
ADVERTENCIAS: Español El usuario debe abstenerse de manipular los componentes de la fuente de alimentación de este producto, cuya reparación debe dejarse exclusivamente en manos de personal técnico especializado. Puede que este producto disponga de más de una fuente de alimentación. No intente modificar ni usar el cable de alimentación de corriente alterna, si no corresponde exactamente con el tipo requerido.
ADVERTENCIAS: Español (continúa) Para obtener un enfriamiento y un flujo de aire adecuados, reinstale siempre las tapas del chasis antes de poner en marcha el sistema. Si pone en funcionamiento el sistema sin las tapas bien colocadas puede dañar los componentes del sistema. Para instalar las tapas: 1. Asegúrese primero de no haber dejado herramientas o componentes sueltos dentro del sistema. 2. Compruebe que los cables, las placas adicionales y otros componentes se hayan instalado correctamente. 3.
