Back to Contents Page

Back to Using IT Assistant

Configuration Management

Dell OpenManage™ IT Assistant User's Guide

	AC Failover Switch Settings		Memory Error Counter Reset
	Alert Threshold Settings (For All Instrumented Systems)		MIF and SMS MIF Mapping on Remote Systems
	CIM, DMI, and SNMP Information		Polling Intervals
	RACs		Power Button Settings
	Event Detection		Remote Flash BIOS
	Hardware Features and System Properties		Remote Restart and Shutdown
	Import and Export of Server Settings		Server Alert Actions
	KVM Management Console Launch		Status Attributes
	KVM Trap Configuration		User Setup for Systems and RACs
	Managed Network Switch Console Launch		Wakeup On LAN
	Managed Network Switch Discovery		Known Issues
	Managed Network Switch Trap Configuration

AC Failover Switch Settings

NOTE: You can access these settings only if a system is equipped with an AC failover switch. If the AC Failover Switch entry does not appear in step 3, a failover switch is not present.

To configure the switching behavior between two redundant power sources in the event of a power interruption on a supported server, perform the following steps:

1. In the IT Assistant navigation tree, expand the Views branch and click Systems.
   
   
2. In the systems window, click a server in the system tree.
   
   
3. In the status tree, click AC Power Switch.
   
   Status for the AC Power Switch appears to the right of the status tree. Overall status of the AC power switch, its attributes, and its attribute values display under General Status. Overall status for the individual power sources (power cords), their attributes, and their attribute values display under Individual Element Status. The following is a list of the AC Power Switch attributes and the possible values for each:

• AC Redundancy Status (under General Status)
  
  This attribute is closely associated with the Redundancy Mode attribute and is calculated based on the current Redundancy Mode setting. Changing the Redundancy Mode setting changes the AC Redundancy Status. This attribute can assume the following values:
  
  
  • Unknown
    
    Indicates that system instrumentation is not reporting a value for this attribute.
    
    
  • Full
    
    Indicates that a power source redundancy is enabled and that a redundant power source is available; indicates that both power cords are plugged into the AC switch and have power. If the value of AC Redundancy Status is Full, no status indicator appears for this attribute.
    
    
  • Lost
    
    Indicates that the redundant power source is not available because one of the power cords connected to the AC Power Switch does not have power. A critical status indicator appears to the left of the attribute name; this status propagates up to the AC Redundancy Status (under General Status) and to the AC Power Switch global status (shown in the status tree).
    
    

    NOTE: If you intentionally leave only one power cord active and connected to the AC power switch, you can change the resulting critical status indicator back to normal by setting AC Redundancy Mode to Non-Redundant. This changes AC Redundancy Status to Not Redundant and returns the status to normal (no indicator).

• Not Redundant
  
  Indicates that only one power cord has power, but this state is intentional. Setting AC Redundancy Mode to Non-Redundant changes AC Redundancy Status to this value. At this time the status is returned to normal and a status icon does not appear on the left.

NOTE: In step 4, the edit () icon appears only if the system supports configurable AC Redundancy Mode and if AC Redundancy Status is not Full.

4. Click the icon to the left of AC Redundancy Mode to set the value. If an icon is not displayed, you are finished with this procedure.
   
   
5. In the Edit Attribute dialog box, select Redundant or Non-redundant.
   
   Redundant indicates that both power cords are expected to be enabled and plugged into active power sources. Non-redundant indicates that only one power cord is expected to be enabled and plugged into an active power source.
   
   
6. Click OK.

NOTE: In step 7, the icon appears only if the system supports configurable AC Source Configuration Mode and if AC Redundancy Mode is set to Redundant.

7. Click the icon to the left of AC Source Configuration Mode to set the value. 
   
   
8. In the Edit Attribute dialog box, select one of the four available modes.
   
   The following list describes the behavior of each mode:

• Input Source Line 1, Upon Redundancy Restoration, Return to Line 1
  
  If the server is using power source Line 1, and Line 1 experiences a power interruption, the server switches to power source Line 2. If and when power is restored to Line 1, the server switches back to Line 1.
  
  
• Input Source Line 1, Upon Redundancy Restoration, Remain on Line 2
  
  If the server is using power source Line 1, and Line 1 experiences a power interruption, the server switches to power source Line 2. The server remains on Line 2 even if power is restored to Line 1.
  
  
• Input Source Line 2, Upon Redundancy Restoration, Remain on Line 1
  
  If the server is using power source Line 2, and Line 2 experiences a power interruption, the server switches to power source Line 1. The server remains on Line 1 even if power is restored to Line 2.

9. Click OK.

• Status (under Individual Element Status)
  
  Indicates the operational status of the power source, usually OK or Lost.
  
  
• Name (under Individual Element Status)
  
  Indicates the power source designation.
  
  
• Active Source (under Individual Element Status)
  
  Indicates the utilization status of the power source. The following are the possible values:
  
  
  • AC Power Cord Is Enabled, Has Power, And Is The Active Source
    
    Indicates that the power cord is enabled, plugged into the active power source, and is used as the current active source.
    
    
  • AC Power Cord Is Enabled And Has Power
    
    Indicates that this power cord is enabled and is plugged into the active power source.
    
    
  • Enabled
    
    Indicates that the power cord is enabled and can be, but is not currently, used as an active power source.

Alert Threshold Settings (For All Instrumented Systems)

To view the alert thresholds for temperature, fan, and voltage probes on a system, storage enclosure, or Dell Remote Assistant Card, perform the following steps:

1. In the IT Assistant navigation tree, expand the Views branch and click Systems.
   
   
2. In the systems window, click a system in the system tree, then click the Status tab.

The left pane of the Status tab displays the status tree. Probe types, such as Fan Probes and Voltage Probes, display below the root entries; the root entries that can contain probe entries are Main System Chassis, DRAC II, and Disk Storage.

3. Click a probe type.

Probes of the selected type display in the right pane of the Status tab. Status and threshold values display in a gauge to the right.

To refresh the view to obtain the most recent status, click Refresh View.

CIM, DMI, and SNMP Information

NOTE: The following are important points about management protocols: IT Assistant supports the following protocols only on the indicated systems and only when those systems are running the specified instrumentation: Simple Network Management Protocol (SNMP) — Supported on Dell servers instrumented with either the Dell Hardware Instrumentation Package (HIP) or Dell OpenManage Server Administrator. Common Information Model (CIM) — Supported on Dell servers instrumented with either Dell OpenManage Server Agent 4.0 and later or Server Administrator; supported on Dell client systems instrumented with Dell OpenManage Client Instrumentation 6.0 and later. Desktop Management Interface (DMI) — Supported on Dell servers instrumented with Dell OpenManage Server Agent 4.0 through 4.3 or Server Administrator; supported on Dell client systems instrumented with Dell OpenManage Client Instrumentation 6.1; limited DMI management might be possible on systems with non-Dell instrumentation if they are DMI 2.0-compliant. To discover systems running Microsoft® Windows® XP Professional and Dell OpenManage Client Instrumentation 7.0, you must install the IT Assistant services on a system running Windows 2000 Service Pack 2 (SP2) or Windows Server 2003. The Details tab of the systems window appears only for properly instrumented systems. IT Assistant communicates with Dell SNMP instrumentation agents using precompiled MIB file information that describes the data retrieved by these agents. IT Assistant cannot retrieve MIB data for SNMP agents for which it does not have precompiled information.

To view information reported from CIM, DMI, or SNMP instrumentation, perform the following steps:

1. In the IT Assistant navigation tree, expand the Views branch and click Systems.
   
   
2. In the systems window, click a system in the system tree.
   
   
3. Click the Details tab.
   

   Headings for each type of instrumentation present on the selected system (CIM, DMI, SNMP) appear in a scrollable list box in the Details tab. If a system is not instrumented for one of these protocols, no branch for that protocol appears in the list box.

4. In the Details tab list box, click the headings (CIM, DMI, SNMP) to expand them into a tree structure that shows the instrumented items for the selected system.

The CIM, DMI, or SNMP information appears as it is structured in the CIM Model Object Format (MOF) files, DMI MIF files, or SNMP Management Information Base (MIB) files that define the instrumentation on the selected managed system. When you click an item in the list box, such as a DMI attribute, the right-hand and lower panes of the Details tab display additional detail about that item.

NOTE: The system tree currently browses MIB files to a branch depth of three. It collapses MIB definitions deeper than three branches.

RACs

Remote access controllers (RACs) comprise four unique hardware devices: the Dell OpenManage Remote Assistant Card (DRAC II), Dell Remote Access Card (DRAC III), Dell Remote Access Card III/XT ( DRAC III/XT), Embedded Remote Access (ERA), Embedded Remote Access Option (ERA/O), and Embedded Remote Access/MC (ERA/MC). Your system may or may not be equipped with one of these RACs depending on the model and configuration.

NOTE: Setting some RAC attributes requires the RAC to reset. DRAC II and DRAC III can require from 2 to 2 1/2  minutes to reset, during which time IT Assistant disallows further input. A progress bar appears during the reset.

NOTE: IT Assistant discovers RACs (DRAC II, DRAC III, DRAC III/XT, ERA, ERA/O, and ERA/MC) and enables you to connect to them to perform remote access management of their host server. IT Assistant can also configure properties for users, modem, network, and alerting for DRAC II and DRAC III. Configuration of these properties is not currently supported for DRAC III/XT, ERA, and ERA/O.

To configure the RAC on a server system, perform the following steps:

1. On the IT Assistant navigation tree, expand the Configuration branch and click Remote Access Hardware.
   
   
2. In the lower pane of the remote access hardware window, click a system in which you want to configure a DRAC, DRAC II, or DRAC III.
   
   If you have not yet logged in to this system during this IT Assistant session, a dialog box appears and prompts you for a valid user name and password for the system.
   
   
3. Enter a user name (default is root) and password (default is calvin) and then click OK.
   
   
4. In the upper pane of the remote access hardware window, set the required configuration information for the DRAC, DRAC II, or DRAC III installed in the currently selected system.
   
   In the upper left corner of the remote access hardware window, above the Network tab, IT Assistant displays the name of the currently selected system and the type of remote access hardware installed in that system. For example, if the currently selected system is named SERVER1 and it is equipped with a DRAC III, the remote access hardware window displays SERVER1: DRAC III in the upper-left corner. See what type of remote access hardware is installed on the currently selected system, then see "Remote Access Hardware" for information on the valid settings for that type of hardware.
   
   
5. Click Save.

NOTE: The following supplemental information is provided for your convenience; it does not relate directly to IT Assistant. However, after you configure the DRAC through IT Assistant, you must perform these tasks so that the DRAC can communicate.

Configuring a Modem Used by DRAC or ESM

To support the Dell PowerEdge 4100 and 4200 systems with embedded server management (ESM) and the PowerEdge 2100 and 2200 systems with DRAC, you must configure the U.S. Robotics Sportster 28.8 (or higher) or a compatible data/fax external modem connected to the DRAC to communicate with the Dell OpenManage Remote Assistant console application program or the DRAC II Web Console. To configure the modem hardware, set the modem switches as shown in Table 1.

NOTE: To ensure proper initialization of the modem, always connect the modem to its power source and turn it on before you turn on the system.

Table 1. Modem Switch Settings for U.S. Robotics Sportster for DRAC or ESM

Configuring a Modem Used by Dell Remote Assistant Server Service

If you are using the U.S. Robotics Sportster 28.8 (or higher) or a compatible data/fax external modem on a management station to connect to a system equipped with ESM (PowerEdge 4100, 4200) or a DRAC (PowerEdge 2100, 2200), the switch settings of the dial-out modem are the same as those shown in Table 1.

Dell OpenManage Remote Assistant and the DRAC II Web Console can communicate with only one configured modem at a time. When Dell OpenManage Remote Assistant starts, it shows the available communication ports as Enabled if DRAC is selected.

If no modems are configured within the operating system, the enabled communications ports cannot be used for modem communication.

Enabled direct-connect communication ports require a null modem cable for direct communication between the ESM (PowerEdge 4100, 4200) or DRAC (PowerEdge 2100, 2200) system and the management station.

To set up remote communication through a modem, perform the following steps:

1. If you have not already done so, go to the Modems control panel and install the desired modem. Click the Start button, point to Settings, click Control Panel, then click Modems.
   
   
2. In the Dell OpenManage Remote Assistant console application program, select New Sessions from the File menu.
   
   
3. In the Managed Server Address Book dialog box, click Configure.
   
   
4. In the Edit Connection dialog box, highlight the connection entry corresponding to the modem to be used.
   
   
5. Click Enable.

Event Detection

NOTE: IT Assistant supports this feature for client systems only. Server systems always generate events.

To selectively disable event detection, perform the following steps:

1. On the IT Assistant navigation tree, expand the Configuration branch and click System Configuration.
   
   
2. In the lower pane of the system configuration window, click the system for which you want to disable event detection.
   
   
3. In the upper pane of the system configuration window, click the Client Polling tab.
   
   
4. Deselect the event categories (SMART Drive, Environmental Monitors, Chassis Intrusion, Hard Disk Threshold, or ECC Single Bit) that  you want to disable for the selected system.
   
   
5. Click Save.

NOTE: Certain items may be grayed-out depending on the types of event detection supported by the client system's instrumentation.

Hardware Features and System Properties

NOTE: You can change hardware features and system properties using a process called system management BIOS (SMBIOS) configuration. IT Assistant supports SMBIOS configuration through DMI and CIM on client systems and through CIM, DMI, or SNMP on server systems.  IT Assistant supports SMBIOS configuration on client systems that meet the following requirements: System is equipped with an SMBIOS. Client systems with this BIOS have the SMBIOS Supported? DMI attribute set to True. You can check the value of this attribute in the Dell Configuration Group of the Details tab in the systems window. System is instrumented with Client Instrumentation 5.0 or later for configuration through DMI and with Client Instrumentation 6.1 for configuration through CIM. IT Assistant supports SMBIOS configuration on PowerEdge systems instrumented with Dell OpenManage Server Agent 4.2 or greater. Some configuration settings you specify using this feature may not be legal on some systems. Client systems running Dell OpenManage Client Instrumentation 5.x ignore illegal settings. Client systems running Dell OpenManage Client Instrumentation 6.x and servers running Dell OpenManage Server Agent 4.2 or greater generate errors if they detect illegal settings.

To view, set, or disable a system configuration setting for the local system or a remote system in the network, perform the following steps:

1. On the IT Assistant navigation tree, expand the Configuration branch and click System Configuration.
   
   
2. In the lower pane of the system configuration window, click a system.

NOTE: In step 3, you may be prompted to enter user authentication information; the type of user authentication you must enter depends on the managed node to which you are connecting. The following are the four possibilities and the type of authentication you must enter for each: If the managed node is a server communicating through DMI or SNMP, enter a valid instrumentation user name and password for that system. If the managed node is a client system communicating through DMI, enter a valid BIOS setup password for that system. This is the system password established through the system's BIOS setup program. If the managed node is a server or client system communicating through CIM, enter valid Windows domain credentials (a valid Windows operating system user name and password) for that system. The user name you enter must have administrative rights to set system configuration options. If the managed node is the local system (the system running IT Assistant) and is communicating through CIM, leave the User Name and Password fields blank; do not provide any authentication and click OK.

3. If prompted, enter your user authentication information for the selected system.
   
   

The tabs in the upper pane of the system configuration window contain groups of system settings. 

4. Click the appropriate tab and adjust the system settings in that group to the desired value. See "System Configuration" for information on the available system options and settings.

Import and Export of Server Settings

NOTE: The following are imporatant points about importing and exporting server settings: Do not import server settings into a system with a model designation that is different from that of the system from which they were exported. For example, do not export settings from a Dell PowerEdge™ 4600 and import them into a PowerEdge 2450. Furthermore, when you attempt to import these settings to the dissimilar system, IT Assistant does not inform you that the settings will not be applied. IT Assistant will allow you to perform the steps required to import the settings, but it does not actually apply the settings, possibly leaving you with the impression that they were. Do not export and import server settings between systems with the same model designation if the systems have significantly different hardware configurations. For example, do not export and import settings between systems with different processor speeds.

To create or load a file that contains alert threshold settings, local server actions settings, and remote access hardware settings, perform the following steps:

1. On the IT Assistant navigation tree, expand the Configuration branch and click Import Server Settings or Export Server Settings.
   
   
2. In the lower pane of the import server settings window or the export server settings window (depending on the action you selected in step 1), click a server system.
   
   
3. If prompted, enter a valid user name and password for the selected server system.
   
   
4. In the upper pane of the window, click Import or Export.
   
   
5. In the Import Settings (or Export Settings) dialog box, browse for the settings file that you want to import to the selected server, or specify a file name and location of the file to which you want to export the selected server's settings.

Settings files are generated as text (.txt) files.

6. Click Save to export, or click Open to import the file.

KVM Management Console Launch

IT Assistant enables you to launch the management console for Dell's Digital Console, which is a digital keyboard/video/mouse (KVM) switch. The KVM management console software must be installed on the the system on which you intend to run IT Assistant.

To launch the KVM management console, perform the following steps:

1. If not already installed, install the KVM management console software on the system on which you intend to run IT Assistant.
   
   The KVM management console software is located on the applications CD that came with the KVM. See your KVM switch documentation for instructions for installing the software.
   
   
2. Start IT Assistant.
   
   You may start IT Assistant from either a local interface installation or by opening a Web-served interface in Internet Explorer. See "Locally Installed and Web-Served Interfaces" for information on the differences between the two start-up methods.
   
   
3. In the IT Assistant navigation tree, expand the Management branch and click Digital KVM Management.
   
   The KVM management console starts in a separate browser window. If the KVM management console software is not present on the system running IT Assistant, IT Assistant generates an error message.

KVM Trap Configuration

You can configure your IT Assistant environment so that IT Assistant receives SNMP traps generated by Dell's Digital Console, which is a digital keyboard/video/mouse (KVM) switch. 

To enable IT Assistant to receive traps from this KVM switch, perform the following steps:

1. Launch the KVM management console using IT Assistant or the console's own recommended method.
   
   
2. Use the KVM management console to designate the management station as the destination for KVM traps.
   
   See the documentation that came with the KVM switch for information on how to set the management station as the destination IP address for traps generated by the switch.

When finished, all IT Assistant interfaces, whether local or Web-served, can receive traps from the KVM switch. The IT Assistant event management system recognizes these traps and enables you to use them to customize your event management environment.

NOTE: To configure an action to perform when the event management system receives an SNMP trap, you must first configure a filter to monitor the systems that might generate that trap. IT Assistant does not discover digital KVMs, so to configure a filter to monitor for a digital KVM trap, you must check Select All under Select Source Nodes in the Filter Configuration dialog box.

Managed Network Switch Console Launch

To launch the management console for a discovered managed network switch, perform the following steps:

1. In the IT Assistant navigation tree, expand the Views branch and click Home.
   
   
2. In the home window, click Network Switches. 
   
   The systems window opens and displays the system tree with the Network Switches branch expanded.
   
   
3. Click a managed switch in the system tree, and then click the Status tab.
   
   
4. Click Remote Connect.
   
   A new window opens and loads the management console interface for the switch.

NOTE: When you launch the PowerConnect™ Console (switch management console) from IT Assistant, the graphic display that represents the current status of the switch ports may not load properly. To correct this problem, enable the Java console in Internet Explorer by performing the following steps: On Internet Explorer menu bar, click Tools, and then click Internet Options. In the Internet Options dialog box, click the Advanced tab and scroll to the Microsoft VM section. Click the check box next to Java console enabled (requires restart) and then click OK. Restart Internet Explorer. The graphic PowerConnect Console display now loads correctly.

Managed Network Switch Discovery

Some managed network switches have a feature called a "host table." For IT Assistant to discover such switches properly, you must register the IP address of the management station in the switch's host table. Otherwise, IT Assistant discovers the switch as an unclassified system and lists it in the Unclassified group in the home window and in the system tree.

If a managed network switch is being discovered as an unclassified system, it is probably because the management station is not registered in the host table. See the documentation that came with your managed network switch to determine if the switch has a host table, and if so, how to register an IP address in it. Ensure that you know the IP address of the management station before you proceed; this is the address that you must register.

If your managed switch does not have a host table, IT Assistant discovers it automatically as a network switch and lists it in the proper group in the home window and in the system tree. 

Managed Network Switch Trap Configuration

Before IT Assistant can receive traps from a managed network switch, you must register the management station as a trap destination using the managed switch's management console. If IT Assistant has properly discovered the switch and listed it in the Network Switches group in the home window and in the system tree, you can use IT Assistant to launch the switch's management console. You can then use the documentation that came with your managed switch to assist you in setting an IP address as a trap destination. Ensure that you know the IP address of the management station before you proceed; this is the address that you must set as a destination.

If IT Assistant is not properly discovering your managed network switch (such as listing its IP address as an unclassified system), you may need to configure discovery for the switch. 

Memory Error Counter Reset

NOTE: For servers, this section applies only to systems instrumented with Server Administrator 1.1 or earlier. Later versions of Server Administrator report failure modes for memory elements. Memory element failure modes report different information than a numeric error count; they do not represent a quantity that can be reset. See "Failure Mode Reporting for Server Memory Elements."

NOTE: Before resetting a managed system's memory error counter using the following procedure, you must first reset the system event log (SEL) through the managed system's instrumentation using Server Administrator. See the Server Administrator User's Guide for information about resetting the SEL.

To reset the memory error counter for a system's memory elements, perform the following steps:

1. In the IT Assistant navigation tree, expand the Views branch and click Systems.
   
   
2. In the systems window, click a system in the system tree, then click the Status tab.
   
   
3. In the status tree, click Memory.
   
   The right pane of the Status tab displays memory status information for each memory element installed on the currently selected system. ECC Correction Count and ECC Multi-bit Error Count is always zero or greater for a memory element. An edit ()  icon appears to the left of Status.
   
   
4. Click the icon to reset the counters for the memory element.
   
   

   NOTE: If Status is Critical for a memory element, the icon also appears to the left of Size. You may click either icon to reset the counters.

5. If prompted, enter a valid user name and password for the selected server and click OK.
   
   
6. When prompted, confirm that you want to reset the memory error counters for the memory element.

MIF and SMS MIF Mapping on Remote Systems

NOTE: IT Assistant supports this feature for client systems only.

To enable MIF mapping on a remote system, perform the following steps:

1. On the IT Assistant navigation tree, expand the Management branch and click Export Data.
   
   
2. In the lower pane of the export data window, select the system(s) on which you want to enable mapping.
   
   
3. Select the type of mapping that you want to enable on the selected remote system(s) from the Mapping Type pull-down menu.
   
   
4. Select the DMI components you want to map for the selected systems from the Categories list box.
   
   

   NOTE: The eight most commonly mapped DMI attributes are listed at the bottom of the Categories list box for your convenience. You must scroll to the bottom of the list to see and select these attributes.

5. If SMS is installed and you want to automatically map the component(s) for the remote system(s) at regular intervals, click the Auto mapping enabled check box and then specify a time in the Every and After controls.
   
   
6. Specify the name and directory to which you want to save the mapped MIF file in the File Name and File Location fields.
   
   
7. Click Save.

NOTE: For each system selected, IT Assistant may take several minutes to perform the mapping enablement process.

Polling Intervals

NOTE: IT Assistant supports this feature for client systems only.

IT Assistant enables you to set the intervals at which the Dell OpenManage Client Instrumentation installed on a client system polls the system for status. The client instrumentation then makes that status available to the IT Assistant browser-based user interface during the next discovery cycle.

To set polling intervals for a remote client system, perform the following steps:

1. On the IT Assistant navigation tree, expand the Configuration branch and click System Configuration.
   
   
2. In the system configuration window, click a desktop system name in the list located in the lower pane of window.
   
   
3. Click the Client Polling tab and set each polling option to the desired interval.
   
   See "System Configuration Window" for a description of the available options and settings.

See "Setting Discovery Preferences" for information on setting system discovery options.

Power Button Settings

NOTE: This feature is supported on certain Dell PowerEdge systems only. If Power Button Status does not appear in step 5, a configurable power button is not present on the selected system.

To enable or disable the external hardware power button on the main chassis of a Dell PowerEdge system, perform the following steps:

1. In the IT Assistant navigation tree, expand the Views branch and click Systems.
   
   
2. In the systems window, click a system in the system tree.
   
   
3. Click the Status tab.
   
   
4. In the status tree, click Main System Chassis.
   
   
5. In the right pane of the Status tab, under General Status, click the eraser ()  icon by Power Button Status.
   
   
6. In the Edit Attribute dialog box, select Enabled or Disabled.
   
   Enabled makes it possible for someone at the remote system to turn off power to the system by pressing the external power button. Disabled deactivates the external power button.
   
   
7. Click OK.

NOTE: If you use IT Assistant to set the Power Button feature to Enabled or Disabled in on a PowerEdge 2500 system might fail if the Power Button Override feature is changed manually in the BIOS. To resolve this issue, perform the following steps: 1. Manually set the Power Button Override feature to Disabled through the system's BIOS. 2. Using IT Assistant, set the Power Button feature to Enabled, even if it is already set to Enabled. 3. Set the Power Button feature to the configuration you want.

Remote Flash BIOS

NOTICE: Do not flash the BIOS on the management station. Doing so yields unpredictable and possibly destructive results.

  Please review the following important points before attempting this procedure:

• If the remote system becomes inactive while you are performing a flash BIOS update, the update does not occur.
  
  
• Flashing the BIOS on client (nonserver) systems automatically shuts down and restarts the system. On servers, you are prompted to confirm whether you want to shut down and restart the system.
  
  
• To prevent data loss on client systems, it is recommended that you send a broadcast message to the affected client systems before performing the BIOS update. If you are flashing a server, it is recommended that you send a broadcast message to clients stating that you intend to update the server BIOS and that the server will be unavailable for connection.
  
  
• Dell recommends that you perform BIOS updates during periods of low network traffic.
  
  
• Dell recommends that you flash the BIOS on server systems one system at a time. Flashing several server systems at the same time may not always be successful.
  
  
• If you remotely flash the BIOS on a server system running Novell® NetWare®, the system may reboot when you perform the NetWare DOWN command.
  
  
• You cannot flash all BIOS versions using the remote flash BIOS feature in IT Assistant. If a system is equipped with an older BIOS version that cannot be flashed remotely, you must update the BIOS locally on that system to a version that can be flashed remotely and then rediscover that system. Then you can use IT Assistant to remotely flash that system's BIOS. 

Prerequisites

To perform the steps in the following procedures, you must obtain a flash BIOS update file appropriate for the systems you want to flash, and then create a header (*.hdr) file. Flash BIOS update files are available from the Dell | Support website at support.dell.com as executable (*.exe) files. You can generate the header file  from the executable file by entering the following command:

<filename.exe> -writehdrfile

where filename is the name of the flash BIOS update file. The .hdr file must reside in your file system rather than on a diskette to optimize the load time.

Task Flow

IT Assistant offers two methods for performing remote flash BIOS updates on remote server and client systems. You perform the same basic tasks for both methods:

• Specify a BIOS update file.
  
  
• Specify the systems that you want to update.
  
  
• Start the update.
  
  
• Confirm the update.

The following subsections describe each method.

UDP Method

NOTE: In this method, remote flash BIOS communication occurs over ports 11487 User Datagram Protocol (UDP) and 11489 Transmission Control Protocol/Internet Protocol (TCP/IP). You must enable these ports for communication to occur between the management station and the system being flashed.

To perform a remote flash BIOS update using the UDP method, perform the following steps:

1. For inactive client systems, run the Wakeup On LAN process on the system(s) that you want to update (servers do not support Wakeup On LAN).

NOTE: Wait until the target system(s) reboot to the operating system before proceeding to the next step.

2. On the IT Assistant navigation tree, expand the Management branch and click Flash BIOS.
   
   
3. In the flash BIOS window, clear (deselect) the Use DCOM when possible check box.
   
   
4. Click Browse and specify the BIOS update file you want to use (flash BIOS update files typically have a .hdr extension).

The BIOS Version to Flash field automatically displays the BIOS version number for the specified file. The lower pane of the flash BIOS window displays a list of systems for which the flash BIOS file you specified is applicable.

5. In the lower pane of the flash BIOS window, click the system(s) that you want to update.
   
   
6. If prompted, enter a valid user name and password for the selected system(s).
   

NOTE: Server systems require passwords; client systems do not.

7. Click Update to begin the remote flash BIOS update process.

NOTE: For each system selected, IT Assistant may take several minutes to perform the update.

DCOM Method

NOTES: To use this method, the following criteria must be met: The systems to be flashed must be client systems running Client Instrumentation 6.0 or higher. The IT Assistant services must be installed on a system running a Microsoft Internet Information Server (IIS); this is Microsoft's Web and File Transmission Protocol (FTP) server. If IT Assistant integrates with the IIS Web server, the http:// method is automatically supported for transfer of the BIOS file. If you want to set up IT Assistant to use the ftp:// method of transfer, see the readme file. In addition, you must supply the proper username and password either when you install the services (through the custom configuration option) or after you install the services (through the configservices utility) for Windows domain-level authentication. The legacy (UDP) method is also supported for Client Instrumentation 6.0 and higher. However, IT Assistant does not automatically attempt the UDP method if the DCOM method fails. You must clear (deselect) the Use DCOM when possible check box and try again to force IT Assistant to use the UDP method.

To perform a remote flash BIOS update using the DCOM method, perform the following steps:

1. For inactive client systems, run the Wakeup On LAN process on the system(s) that you want to update.

NOTE: Wait until the client system reboots to the operating system before proceeding to the next step.

2. On the IT Assistant navigation tree, expand the Management branch and click Flash BIOS.
   
   
3. In the flash BIOS window, select Use DCOM when possible.
   
   
4. Click Browse and specify the BIOS update file you want to use (flash BIOS update files typically have a .hdr extension).

The BIOS Version to Flash field automatically displays the BIOS version number for the specified file. The lower pane of the flash BIOS window displays a list of systems for which the flash BIOS file you specified is applicable.

5. In the lower pane of the flash BIOS window, click the system(s) that you want to update.
   
   
6. If prompted, enter a valid user name and password for the selected system(s).
   

NOTE: Server systems require passwords; client systems do not.

7. Click Update to begin the remote flash BIOS update process.

NOTE: For each system selected, IT Assistant may take several minutes to perform the update.

Advanced Configuration for Remote Flash BIOS Using DCOM

Configuring ftp Protocol Instead of http Protocol for DCOM Flashing

IT Assistant 6.3 provides a feature to remotely update the BIOS on client systems running Client Instrumentation 6.0 or greater using Microsoft's DCOM technology. This feature can use either the http protocol or the ftp protocol to send the BIOS update file to the client system. If you perform the following tasks during installation, the http protocol is configured for DCOM flash by default:

• You choose to install the IT Assistant services on a system that has a Web server installed.
  
  
• You also choose to configure DCOM security during the installation.

If the system on which you are installing the IT Assistant services does not have a Web server, you can configure an ftp server to be used during DCOM flash. To use an ftp server, perform the following steps (the ftp server must be running on the management station when performing this procedure):

1. In the IT Assistant configuration directory, open the dconfig.ini file using a text editor. 
   
   
2. Locate the [DCOM_BIOS_FLASH] section. 
   
   
3. Set USE_FTP to 1.
   
   
4. Set FTP_VIRT_ROOT to the root published by the ftp server (for Microsoft's ftp server, this can be done under the Computer Management application).
   
   Example: /BIOSFlashCabs 
   
   
5. Set FTP_DIRECTORY to the actual directory where IT Assistant can store the packaged cab file containing the BIOS image for the client.
   
   Example: C:\mycabfiles 
   
   
6. Save the dconfig.ini file and restart the IT Assistant services.

Forcing DCOM Use for BIOS Flash (Requires Client Support for DCOM)

If DCOM is configured and you not want others to use the legacy method of flash BIOS, IT Assistant allows you to force DCOM to always be selected and to be used for those systems that support it. Doing so prevents the legacy method from being used for those systems. However, for systems that do not support flash BIOS using DCOM, the legacy method is still available.

To force DCOM to be used for those clients that support it, perform the following steps:

1. In the IT Assistant configuration directory, open the dconfig.ini file using a text editor.
   
   
2. Locate the [DCOM_BIOS_FLASH] section.
   
   
3. Set ALWAYS_USE_DCOM to 1.
   
   
4. Save the dconfig.ini file and restart the IT Assistant services.
   
   
5. The Use DCOM when possible checkbox in the user interface should now be grayed-out and selected.

Confirming the BIOS Update

You can confirm the update by viewing the remote flash BIOS update attributes on the Details tab of the systems window for the selected remote system. To access these attributes, open the systems window, click Details, click the plus (+) sign next to Dell Systems MIF component, and then click the plus sign next to Dell Remote Flash BIOS Settings group. The following attributes give information about the latest flash BIOS update:

• Support — Shows whether this system supports remote flash BIOS updates
  
  
• Last BIOS Update — Displays date and time of last update
  
  
• Completion Code — States whether an update operation has been performed

NOTE: If you specify multiple systems to receive a flash BIOS update and the IT Assistant services are installed on one of those systems, the flash BIOS process stops after the management station is flashed. To ensure that all of the systems you specify are flashed, It is recommended that you flash the IT management station first, then flash the other systems.

Remote Restart and Shutdown

NOTE: IT Assistant supports this feature for servers and for client systems equipped with an SMBIOS only. Systems with this BIOS have the SMBIOS Supported? attribute set to True in the Dell Configuration Group of the Details tab in the systems window.

To remotely restart and shut down systems, perform the following steps:

1. On the IT Assistant navigation tree, expand the Management branch and click Shutdown.
   
   
2. In the lower pane of the shutdown window, click the system(s) you want to remotely restart or shut down.
   
   
3. If prompted, enter a valid user name and password for the selected system(s).
   
   
4. In the upper pane of the Shutdown window, select the type of shutdown action you want to perform: Reset System, Power Cycle, or Power Off.
   
   
5. If you want to shut down the operating system on the remote system(s) first, click Shut down OS first.
   
   
6. Click Shutdown.

NOTE: If the instrumentation on the remote system(s) does not support a shutdown action, that action is grayed-out and cannot be selected.

NOTE: After issuing a Remote Shutdown command to a PowerEdge 6400 system running Windows 2000, the system might restart instead of shutting down.

Server Alert Actions

NOTE: The actions you configure in this procedure are triggered by the event-monitoring devices on a Dell PowerEdge system, some of which are configurable. These actions are initiated by the managed server, occur on the managed server, and are separate from actions configured through the IT Assistant event management system. Actions configured through the event management system are initiated on the management station.

To configure alert response actions for a server system, perform the following steps:

1. On the IT Assistant navigation tree, expand the Management branch and click Server Alert Actions.
   
   
2. In the lower pane of the server alert actions window, select the system(s) for which you want to configure alert response actions.
   
   
3. If prompted, enter a valid user name and password for the selected system(s).
   
   
4. In the upper pane of the server actions window, click the alert for which you want to configure an action, then click Configure Action.
   
   
5. In the Configure Action dialog box, choose the action you want the server to initiate or specify the application you want to run on receiving the alert.
   
   If you choose to execute an application on receiving the alert, perform these additional steps.

NOTE: The feature described in the following steps is enabled only if the client system's instrumentation supports it. These steps enable you to execute the application on the managed system as a specific user. This is useful if only that user has the right to execute the application.

1. Click Advanced.
   
   
2. In the Application Information dialog box, enter domain and login information for the system on which the application resides.
   
   
3. Click OK.

6. In the Action on Hung Server Detection group, click the action you want to take when a server hangs (becomes unresponsive).
   
   
7. Set Reset System Timer to the desired interval.
   
   This control is grayed-out if the server's instrumentation does not support this feature.
   
   
8. Choose an alert severity level required for flashing the fault light-emitting diode (LED) from the Flash fault LED at this severity level drop-down menu.
   
   This LED is located on the front of Dell servers and helps you to locate which server in a rack generated the alert.

9. Click Save.

Status Attributes

NOTES: One of the capabilities of this feature is to enable you to change the alert threshold settings on a server. Dell recommends that you use the server's default alert threshold settings. If the defaults must be changed, ensure that it is done by a qualified system administrator familiar with the server being modified. The Thermal Shutdown Severity alert threshold, available on some servers, pertains to overheating only. No event is generated and the system is not shut down by the server's ESM if the temperature drops below the set temperature range

IT Assistant enables you to change some status attribute values on both client and server systems. Clients support only informational changes, such as system location or the primary user's phone number. Servers support a much wider range of settable status attributes, many of which are the alert thresholds used by the ESM, such as the maximum current allowable from a power supply, or the minimum voltage allowable for the primary processor.

To set a system's status attributes, perform the following steps:

1. In the IT Assistant navigation tree, expand the Views branch and click Systems.

2. In the systems window, click a system in the system tree, then click the Status tab.

The probe types display below the Main System Chassis entry in the left pane of the Status tab.

3. In the status tree, click a system component, such as Main System Chassis, Fan Probes or Voltage Probes.

If you click a component of which the server has several, the individual components of the selected type display in the right pane of the Status tab. For example, servers support a probe on every fan, so the right pane of the Status tab may display CPU Fan 1, CPU Fan 2, Hard Drive Fan 1, and so on.

An (eraser) icon appears to the left of the user-editable attribute settings. If the component is an environmental probe, the current reading on the probe and current alert threshold values display in a gauge to the right.

4. Click the  icon.
   
   
5. If prompted, enter a valid user name and password for the selected server and click OK.
   
   
6. In the Edit Attribute dialog box, enter new attribute values or choose to use a default (if available), and then click OK.

The new attribute value(s) display in the right pane of the Status tab. If the component you selected was an environmental probe, the gauge to the right reflects the changed threshold values.

To refresh the view to obtain the most recent status, click Refresh View.

To reset all alert threshold attributes (if any)  to their factory defaults, click Reset Thresholds.

User Setup for Systems and RACs

NOTES: IT Assistant supports this feature for properly-instrumented systems and the following RACs: DRAC II and DRAC III. All users that you add to a system can access that system's management instrumentation and change a variety of system and instrumentation settings. If you add a user to a server system equipped with remote access hardware, you can optionally give that user permission to use the DRAC II or DRAC III as well. Users that can access only management instrumentation are called "instrumentation users." Users that can also access a DRAC II or DRAC III are called "DRAC II users" and "DRAC III users," respectively. Client Instrumentation 7.0 communicates using CIM only. CIM users are based on the managed system's operating system; IT Assistant does not offer a way to configure users when CIM is the only protocol used to communicate with the managed system. Therefore, IT Assistant does not offer the system user setup feature for client systems instrumented with Client Instrumentation 7.0. DRAC II users can remotely access a DRAC II through the DRAC II Web Console or the Dell OpenManage Remote Assistant Console, which are interfaces available in the Dell OpenManage Remote Assistant product. DRAC III users can remotely access a DRAC III through a Web browser or VT100 cable. A DRAC or DRAC III user can remotely power off, reset, or gracefully shut down a properly equipped system using the console redirection feature of the DRAC II or DRAC III (see your DRAC II or DRAC III documentation for information on this feature). DRAC II (not DRAC III) user names are added to the firmware on the DRAC II itself and to the managed node instrumentation. If you install a DRAC II in another system, or if you remove the DRAC II for a time, the list of users stored in the DRAC II firmware and in the host system's instrumentation may become unsynchronized. IT Assistant synchronizes these two lists by deleting unrecognized users from the DRAC II firmware.

IT Assistant enables you to set up IT Assistant users and passwords on servers, client systems, and the DRAC II and DRAC III RACs. Server and client systems must be equipped with a systems management basic input/output system (SMBIOS). Client systems support only one user and one password. Server systems can support multiple users, each with their respective passwords.

NOTE: Passwords for client (nonserver) systems are stored in the BIOS.

To add a user, perform the following steps:

1. In the IT Assistant navigation tree, expand the Views branch and click Systems.
   
   
2. In the systems window, click a system in the system tree.
   
   
3. Click the Users tab, then click Add.
   
   
4. If you have not yet logged in to this system with root access during this IT Assistant session, a dialog box appears with the name root in the User Name field; type the root password (default is calvin) into the Password field and click OK.
   
   

   NOTES: The user root cannot be deleted. If you have not already done so, Dell recommends that you change the default password. User root is logged out when you exit IT Assistant.

5. In the Add User/Edit User dialog box, enter the new user name and password, then re-enter the password to verify it; do not click OK yet.

NOTE: If you want to add this user as only an instrumentation user, proceed to step 6. If you want to add this user as a DRAC II or DRAC III user, skip step 6 and proceed to either "Configuring a DRAC II User" or "Configuring a DRAC III User."

6. Leave all remaining information fields (if any) blank and click OK.
   
   The Username list box displays the new user along with any other users configured for the currently selected system. 

Configuring a DRAC II User

NOTES: This procedure assumes you have completed steps 1 through 5 of the previous procedure. If this is not the case, do so now. The user root is not a DRAC II user by default. Adding a DRAC II user may take up to 2 minutes to take effect.

1. In the Add User dialog box, select Configure DRAC User.
   
   This activates the remaining controls in the dialog box.
   
   
2. Provide the required DRAC II user and pager information in the remaining controls.
   
   See "Add User/Edit User Dialog Box Controls for a System Equipped With a DRAC II" for information on valid values for each control.
   
   
3. Click Test to send a page.
   
   If the test is unsuccessful, verify your configuration information and repeat step 2 until you conduct a successful test.
   
   
4. Click OK.
   
   The Username list box displays the new user along with any other instrumentation, DRAC II, and DRAC III users for the selected system. A small telephone icon to the left of a user name indicates that the user is a DRAC II user; a peripheral card icon indicates a DRAC III user.

To change user information after setup, see "Editing Existing User Information."

Configuring a DRAC III User

NOTES: This procedure assumes you have completed steps 1 through step 5 of the first procedure. If this is not the case, do so now. The user root is a DRAC III user by default.

1. In the Add User dialog box, select Enable DRAC III User.
   
   This activates the DRAC III User tab.
   
   
2. Click the DRAC III User tab and provide the required DRAC III user information. See "Add User/Edit User Dialog Box Controls for a System Equipped With a DRAC III" for information on valid values for each control on the DRAC III User tab.
   
   
3. On the DRAC III User tab, click the test buttons (Test Numeric Page, Test e-mail Page, Test Alpha Page) to send a page for each type of paging you configured.
   
   If the test is unsuccessful, verify your configuration information for that type of paging and repeat step 3 until you conduct a successful test.
   
   
4. Click OK.
   
   The Username list box displays the new user along with any other instrumentation, DRAC, and DRAC III users for the selected system. A small  peripheral card icon to the left of a user name indicates that the user is a DRAC III user.

To change user information after setup, see "Editing Existing User Information."

Editing Existing User Information

To edit information for an existing user, perform the following steps.

NOTE: IT Assistant enables the edit feature for Dell server systems equipped with a DRAC II or DRAC III only.

1. In the IT Assistant navigation tree, expand the Views branch and click Systems.
   
   
2. In the systems window, click a system in the system tree.
   
   
3. Click the Users tab.
   
   
4. Click a user name in the Username list box (located in the lower pane of the window).
   
   
5. Click Edit, Delete, or Change Password, depending on the action you want to perform.
   
   If you are not logged in to the selected system, you are prompted to enter a valid user name (default is root) and password (default is calvin). 
   
   
6. In the dialog box that appears, enter the appropriate new user information and click OK.

To delete a user, perform the following steps:

1. In the IT Assistant navigation tree, expand the Views branch and click Systems.
   
   
2. In the systems window, click a system in the system tree.
   
   
3. Click the Users tab.
   
   
4. Click a user name in the Username list box (located in the lower pane of the window).
   
   
5. Click Delete.
   
   
6. Click Yes.
   
   This removes the user from the DRAC or DRAC III firmware and from the IT Assistant data repository.

Wakeup On LAN

NOTE: IT Assistant supports this feature on client systems that have a Wakeup On LAN-compatible NIC only.

To wake up one or more remote systems, perform the following steps:

1. On the IT Assistant navigation tree, expand the Management branch and click Wakeup On LAN.
   
   
2. In the lower pane of the Wakeup On LAN window, select the system(s) that you want to wake up.
   
   
3. In the upper pane of the Wakeup On LAN window, click Wakeup.

NOTE: IT Assistant may take several minutes to perform the Wakeup On LAN process.

Known Issues

• If you use the UDP method for remote flash BIOS, and if you have switches and routers between the managed nodes and the management station, the action may fail because the switches and routers may block the UDP packets. Switches and routers must be configured properly to allow UDP packets across.
  
  
• Flashing the BIOS on client systems with dual NICs may not work if the NICs are attached to different subnets.
  
  
• If you issue a Test Page command when configuring a DRAC II, you may receive either of the following messages:
  
  The user configuration failed.
  
  Unable to update the DRAC user configuration.
  
  IT Assistant executes the command even if you receive either of these messages.
  
  
• "Server Alert Actions" describes how to configure managed servers to broadcast a message if they generate an alert. For the broadcast message to be delivered to the target system (the system that you want to receive the message), ensure that the following requirements have been met:
  
  
  • The server has been set to Broadcast Message through IT Assistant.
    
    
  • A session has been established from the target system to the server.
    
    
  • The messenger service is running on the target system.
    
    

  The following are limitations of broadcasting a message:
  
  

  • The broadcast message does not pass through a network router. The pop-up message box appears only if the target system belongs to the same subnet as the managed server.
    
    
  • All broadcast message information is lost when a server is rebooted.
    
    
• BIOS flashing of clients running Client Instrumentation 6.0 or greater using Microsoft Distributed Common Object Model (DCOM) is not supported on systems running Windows 9x or Windows Millennium Edition (Me) because of the differences in DCOM security between client and server operating systems. Remote BIOS flashing of these systems using DCOM is not tested and therefore is not supported. The Microsoft Knowledge Base article "Q165101 - HOWTO Use a Windows 95, Windows 98, or Windows Me Computer as a DCOM Server" may provide a workaround for this. Contact Microsoft for more information.

Back to Contents Page

Back to Using IT Assistant