() Linux Network Operating System Configuration Guide EXPRESS5800/320La/320La-R ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Proprietary Notice and Liability Disclaimer The information disclosed in this document, including all designs and related materials, is the valuable property of NEC Solutions (America), Inc. and/or its licensors. NEC Solutions (America), Inc. and/or its licensors, as appropriate, reserve all patent, copyright and other proprietary rights to this document, including all design, manufacturing, reproduction, use, and sales rights thereto, except to the extent said rights are expressly granted to others.
Contents Proprietary Notice and Liability Disclaimer Introduction About This Guide ...................................................................................................................... 1-2 Document Conventions ............................................................................................................. 1-2 How This Guide Is Organized ................................................................................................... 1-2 Related Documents......................
CPU Properties ..............................................................................................................3-16 File System Properties...................................................................................................3-17 LAN Properties..............................................................................................................3-18 Temperature Properties .................................................................................................
1 Introduction ! About this Guide ! Document Conventions ! How this Guide is Organized ! Related Documents ! Where to go from here
About This Guide This guide contains supplemental instructions needed to install and configure the Red Hat Linux® Network Operating System. This document is intended to complement the more detailed procedural documents available from the vendor of the network operating system. This document is not intended as the central source of installation and configuration information for your system.
Related Documents In addition to this guide, the following system documentation is included with your server either as electronic files on EXPRESSBUILDER or as paper copy shipped with your server. ! System Release Notes Release Notes provide you with the latest information about your system. This information was not available at the time your configuration guide was developed.
2 Configuring Linux ! Overview ! Powering up the Server ! Configuring the Network Interface ! Configuring Internal Disk Drives
Overview This chapter contains supplemental instructions needed to configure hardware and software used with the Linux Operating System. This information is intended to supplement the more detailed Linux procedural documents available from RED HAT, Inc. This information is not intended to be the central source of installation and configuration information for your system. Note: Read the System Release Notes for the latest system information before attempting to install Red Hat Linux on your system.
Powering up the Server After completing the system installation, power up the server. After POST (Power-On Self-Test), the server's self-diagnostic program completes, the preinstalled Linux operating system loads. The login prompt is displayed. Logon the system with root. (For the password, see "Administrator (root) password" provided with the server.
3. Add the NICs of slot 7 to the VND list. Type: vndctl add 7 4. Confirm the status. Type: vndctl status 7 --Virtual Network Status-virtual status config slot real(s) ha0 OKAY yes 7 *epro01.06 epro09.06 Link encap:Ethernet HWaddr 00:00:4C:0F:F7:E0 BROADCAST MASTER MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 slot real status link 7 left epro01.
7. Confirm the status. Type: vndctl status --Virtual Network Status-virtual status config slot real(s) ha0 OKAY yes 7 epro01.06 *epro09.06 slot 1 2 3 4 5 6 7 real status link left right left right left right left right left right left right left epro01.06 UP right epro09.06 UP LINK LINK 8. Confirm that IP addresses and other information are set as specified. Type: vndctl status 7 --Virtual Network Status-virtual status config slot real(s) ha0 OKAY yes 7 epro01.06 *epro09.
Adding Optional PCI Network Interface Controllers Optional PCI network interface controllers (NICs) are added to your server in pairs (one controller to each PCI module) to ensure total system redundancy and mirroring. Perform the following steps to configure added 100BASE-TX, 1000BASE-TX, and 1000BASE-SX NICs. 1. Power down the server and install the network interface controller boards into the same location within each PCI module.
Confirming Information IP Addresses To confirm NIC IP addresses, enter the following command. Type: vndctl status n where n indicates the slot number (1 - 7) of the slot containing the optional NIC boards. --Virtual Network Status-virtual status config slot real(s) ha0 OKAY yes 7 epro01.06 *epro09.06 Link encap:Ethernet HWaddr 00:00:4C:0F:F7:E0 inet addr:192.168.8.10 Bcast:192.168.255.255 Mask:255.255.0.
Configuring Internal Disk Drives The hard disk drive storage bays can house up to six hard disk drives, which when mirrored results into three logical drives. The physical disk drive slots are numbered 1 to 6 (left to right), but the SCSI ID is numbered 0, 1, 2, 0, 1, 2. When mirrored into two pair of three logical disk drives, the first mirrored pair consists of hard disks 1 and 4 (SCSI ID 0), the other two disk mirrored pairs are hard disks 2 and 5 (SCSI ID 1) and hard disks 3 and 6 (SCSI ID 2).
A server configured as RAID Level 1 with disks in the paired slots is shown in the Figure below. ! SLOT1 - SLOT4 ! SLOT2 - SLOT5 ! SLOT3 - SLOT6 Slots for mirroring SLOT4 SLOT1 SLOT5 SLOT2 SLOT6 SLOT3 Group 1 Group 2 Note: Paired hard disk drives in a RAID Level 1 configuration must have the same capacity and the same logical structure. Using the ftdiskadm utility to manage your disks and disk partitions, ensures these rules.
Disk Administrator Tool (ftdiskadm) The disk administrator tool (ftdiskadm) confirms internal SCSI disk status or set RAID configurations. Use ftdiskadm to perform the following functions: ! Confirm the status of all the internal SCSI disks ! Confirm RAID status of internal SCSI disks ! Recover RAID of internal SCSI disks ! Add internal SCSI disks ! Remove internal SCSI disks. A ftdiskadm display sample is shown below.
Confirming SCSI Disk Status Use the ftdiskadm command to confirm SCSI disk status. The following is a display sample when [Status(All Disks)] of [=> RAID] is executed: [SCSI DISK STATUS] -- BUS -bu pci(haddr) s 0 01:05.00(10.5.0) 09:05.01(11.5.1) 1 01:05.01(10.5.1) 09:05.00(11.5.0) 2 01:02.00(10.2.0) 3 09:02.00(11.2.
The following are determined: = btl = dHctl The tuple and path first displayed for a device, correspond to the primary path used to access the device. NOTE: If an extension SCSI board is mounted in a PCI slot, topology setting is necessary. To confirm the software RAID, execute [Status(Raid)]. A RAID status display sample is shown below.
Setting SCSI Topology If an extension SCSI board (FC board) is mounted in a PCI slot, topology setting is necessary. Take the following steps to set topology: 1. Choose the domain numbers to be set from the /proc/scsi/scsi and /proc/scsi/topo files, and execute the following command on the shell: echo setdomain dn > /proc/scsi/topo where dn is the domain number. 2. Choose a SCSI bus number not used yet, and execute the following command on the shell: echo bus bn format PCI_BUS_NO:PCI_SLOT_NO.
Domain 0 Domain 1 Host 01:05 Channel 0 connects to Bus 0 Device b0t8l0 ( ) Channel 1 connects to Bus 1 Device b1t8l0 ( ) Host 09:05 Channel 1 connects to Bus 0 Device b0t8l0 ( ) Channel 0 connects to Bus 1 Device b1t8l0 ( ) Domain 2 Host 01:03 Channel 0 connects to Bus 2 Host 09:03 Channel 0 connects to Bus 2 ftdisk topology-save For more information, consult the man-pages of scsi and scsi-topology.
Starting SCSI Disk(s) Use ftdiskadm to start a SCSI disk(s) in manual mode. The following is an example of starting a SCSI disk(s): Command action 1 => SCSI 2 => RAID 3 => Environment 9 Quit Command: 1 Command action 1 Status(All Disks) 2 Status(System Disks) 3 Status(Extended Disks) 4 Bring Up 5 Bring Down 9 <= RETURN Command: 4 [Bring Up] * Which disk(s)? ['?' for help] => (10.1)t0l* (see Note: 1) ftdisk: ERROR(1): Bringing up reached timeout! (see Note 2) <> Notes: 1.
Stopping SCSI Disk(s) Use ftdiskadm to stop a SCSI disk(s) in manual mode. The following is an example of stopping a SCSI disk(s): Command action 1 => SCSI 2 => RAID 3 => Environment 9 Quit Command: 1 Command action 1 Status(All Disks) 2 Status(System Disks) 3 Status(Extended Disks) 4 Bring Up 5 Bring Down 9 <= RETURN Command: 5 [Bring Down] * Which disk(s)? ['?' for help] => (10.1)t0l5 (see Note 1) f* Bring down: '(10.1)t0l5 [d0h2c0t0l5]' [y/n] y <> Notes: 1.
Adding Internal Disks Internal SCSI disks are mounted in slots 1 and 4 in standard configuration. You can mount additional internal SCSI disks in paired slots 2 and 5, and paired slots 3 and 6. Note: Be sure to add internal SCSI disks in pairs. Use ftdiskadm to configure additional internal SCSI disks.
Confirm the disk status (check if the disk(s) has been added normally).
Replacing Internal Disk(s) If an internal SCSI disk problem occurs, take the following steps to replace the disk: 1. Execute [Remove half disk] of [=>RAID] of ftdiskadm to disconnect the RAID of the disk to be specified with the slot number and disconnect the disk from the system. 2. Remove the disk from the system, and insert a new disk. 3. Execute [Repair Disk] of ftdiskadm to restore the RAID.
[Status(Raid)]] ---------------------------------------------------------------------------------name partition label status member md0 /boot /boot DUPLEX (1)sda1 (4)sdd1 md1 /usr /usr DUPLEX (1)sda5 (4)sdd5 md2 /home /home DUPLEX (1)sda10 (4)sdd10 md3 /var /var DUPLEX (1)sda6 (4)sdd6 md4 / / DUPLEX (1)sda8 (4)sdd8 md5 /tmp /tmp DUPLEX (1)sda9 (4)sdd9 md6 /swap DUPLEX (1)sda7 (4)sdd7 md7 extra_s1 SIMPLEX (3)sdc1 (6)sdf1 md8 extra_s5 SIMPLEX (3)sdc5 (6)sdf5 md9 extra_s6 SIMPLEX (3)sdc6 (6)sdf6 --------------
[Status(Raid)] ---------------------------------------------------------------------------------name partitio label status member n md0 /boot /boot DUPLEX (1)sda1 (4)sdd1 md1 /usr /usr DUPLEX (1)sda5 (4)sdd5 md2 /home /home DUPLEX (1)sda10 (4)sdd10 md3 /var /var DUPLEX (1)sda6 (4)sdd6 md4 / / DUPLEX (1)sda8 (4)sdd8 md5 /tmp /tmp DUPLEX (1)sda9 (4)sdd9 md6 /swap DUPLEX (1)sda7 (4)sdd7 md7 extra_s1 SIMPLEX -(3)sdc1 (6)sdf1 md8 extra_s5 SIMPLEX -(3)sdc5 (6)sdf5 md9 extra_s6 RECOVERY(1.
Reinstalling Linux Before starting reinstallation, remove all the peripheral equipment, added SCSI boards, and NICs. Carry out the reinstallation with two internal SCSI disks inserted in slots 1 and 4. Choosing wrong slots or a wrong number of disks results in an installation failure. In this case, perform the installation procedure again.
Perform the following steps to reinstall Linux: 1. Insert the install disk into the floppy disk drive, and insert backup CDROM1 into the CD-ROM drive immediately after turning on the power. Installation starts. A message is displayed after a short time. 2. Remove backup CD-ROM1 and insert backup CD-ROM2 according to the message. 3. Press Enter. The message "Congratulation! Install Complete" is displayed at completion of the installation. 4. Press Enter. Backup CD-ROM2 is ejected and rebooting starts.
3 ESMPRO Agent for Linux ! NEC ESMPRO Agent ! Required Software Modules ! Installing the Agent ! Report Setting ! Agent Monitoring ! ESMPRO Agent Considerations ! Alert Report Device IDs
NEC ESMPRO Agent NEC ESMPRO Agent is a utility that serves as an agent between the server and NEC ESMPRO Manager (management PC). Using the agent, you can set and reset values for a number of parameters and also establish threshold limits for your server. Required Software Modules Agent for Linux requires installation of the following software modules.
Setting SNMP Service The SNMP service needs to be set for using NEC ESMPRO Agent. IMPORTANT: If reinstalling the ucd-snmp package after installing NEC ESMPRO Agent, you need to reinstall NEC ESMPRO Agent. To monitor the SNMP service from NEC ESMPRO Manager, change the SNMP environment setting file (/etc/snmp/snmpd.conf), and set the community right level to [READ WRITE] or higher.
Selecting "3" terminates operation without installing NEC ESMPRO Agent. A message is displayed prompting you to enter the directory where NEC ESMPRO Agent is to be installed. ESMPRO_SA_DIR==> 7. Specify an arbitrary directory. If you do not specify any directory and press , NEC ESMPRO Agent is installed in the following directory: /opt/nec/esmpro_sa IMPORTANT: When installing NEC ESMPRO Agent in a desired directory, specify the directory with a full path name starting with /. Do not specify only /.
6. Select "1" from the menu. Selecting "3" terminates operation without installing NEC ESMPRO Agent. The following menu is displayed: 1) Rebuild data 2) Keep Current Setting 3) Exit 7. Select "2" for to install updated NEC ESMPRO Agent while keeping the current settings. Select "1" to install updated NEC ESMPRO Agent after clearing all the current settings. Selecting "3" terminates operation without installing NEC ESMPRO Agent. 8. Restart the system.
Report Setting The Agent monitors events it detects internally or from the Linux event logs. To configure the Agent to respond to events, you perform the following basic activities using selections from the Report Setting menu. ! Enable the event reporting methods you want to use (Base Setting). ! Define a list of report destinations (Destination ID Setting). ! Select the events you want the Agent to monitor (Agents Events Setting and Syslog Events Setting). Setting Manager Reporting (SNMP) 1.
Base Settings The Agent can respond to an event using any of the three methods selected in the Base Setting menu, but only if the method is enabled and configured. The report contents include a detailed message, support method, and the alert type. Manager - Select this setting to use SNMP as the reporting method to send alerts to the Manager. For this method to work you must specify the manager console’s IP address as an SNMP trap destination.
Manager SNMP Trap Setting When you select Manager (SNMP) from the Base Setting menu, the SNMP Trap Setting menu displays. To allow the Agent to send alerts to the manager, you must include the manager’s IP address in the Agent’s list of SNMP trap destinations. Trap Destination IP - Specifies the manager console’s IP address as a SNMP trap destination. Select Add or Remove to change, add or delete the IP addresses.
Destination ID Settings Once you have established the Base Setting method, you are returned to the Report Setting menu. Selecting the Destination ID Setting displays the Destination ID Setting menu. To specify how the Agent responds to a particular event, you associate one or more destination IDs with the event number. When the Agent detects that event, assuming the Agent has been set to monitor that event number, the Agent performs the action specified by the method that the destination ID is based on.
Scheduling Responses You can schedule which hours of the day a particular destination ID is active. For example, you can set the agent to respond to the same alert type by displaying a message during regular working hours. Selecting Schedule from the ID Setting menu above displays the Schedule menu. A schedule can be set for each destination ID. In the schedule set a report retry interval which is usually set in the range of 1 to 30 minutes.
IP Address – The address or name of the remote manager. Make sure the remote manager is not also specified as the trap destination on the SNMP service. If a duplicate is made, more than one alert will be reported. Port Number – The port number used for communication between sockets. The same port number must be set for both the agent and the remote manager. The default value is 31134.
Agent Events Setting The Agent Events Setting menu lets you configure internal events generated by the Agent. Selecting Agents Events Setting at the Report Setting menu displays the Agent Events Setting menu. Source: The origin of a particular Agent event. Event ID: The destination ID of a particular Agent event. Source: The origin of a particular Agent event. Event ID: The destination ID of a particular Agent event. Action after Report: Select the action to be taken when this event occurs.
Destination ID List: Highlight the method of reporting to be used should this selected event occur. Then tab to Add and press ENTER to add the selected method to the Report to: list. Report to: Lists the active method of reporting an event. Syslog Events Setting The Syslog Events Setting menu lets you configure internal events generated by the operating system. Selecting Syslog Events Setting at the Report Setting menu displays the Syslog Events Setting menu.
! Shutdown – The system is systematically shut down. ! Reboot - The system is rebooted. Destination ID List: Highlight the method of reporting to be used should this selected event occur. Then tab to Add and press ENTER to add the selected method to the Report to: list. Report to: Lists the active method of reporting an event. Agent Monitoring Selecting ESMagntconf at the ESMPRO/ServerAgent menu displays the Agent Properties menu.
General Properties Enable the ESMPRO Manager to modify SNMP Setting - Indicates whether the Manager can modify server parameters via SNMP. A check enables Manager modifications; no check disallows Manager changes. Enable Remote Shutdown/Reboot - Specifies whether the Manager can perform a remote shutdown or reboot. A check gives the Manager permission. No check denies the Manager permission. Note: Also, enable “Shutdown Delay” in the “Base Setting” window of the “Alert Manager Report Setting Utility (.
CPU Properties Sample Interval - This is the CPU load monitoring cycle. It defines how often the CPU load is sampled. In the example to the right, if the CPU load is sampled every 10 seconds, you are collecting six data points every minute. Utilization Rate - CPU load is measured for the time period shown in this field. In the example on the right, CPU load is sampled every 10 seconds and computed over a period of 1 minute.
File System Properties Alert messages are generated when the amount of used disk space exceeds the fatal and warning limits defined on the File System tab. Sample Interval - Indicates how often the drive is monitored. The range is 1 to 3600 seconds. Drive - Thresholds displayed in this window apply to this drive. Disable threshold - When this bullet is indicated, the drive is not monitored. No fatal or warning alerts are generated.
Fatal Reset - When Enable Threshold (ratio of used capacity) is indicated, the Agent status is reset from Abnormal to Warning when the amount of used disk space falls below this value. When Enable Threshold (amount of free bytes) is indicated, the Agent status is reset when the amount of free space rises above this value. Warning Limit - When this limit is exceeded, a warning alert message is generated and the status of the Agent changes from normal to warning.
Network Hardware Error Percentage - The percentage of network hardware errors that were detected during the Sampling Interval. Hardware errors can include packet collisions due to alignment errors or FCS errors. Errors may also occur when the network cables are not securely fastened or the HUB power is not turned on. Transmission Retry Percentage - The number of collision errors as a percentage of all transmitted packets during the Sampling Interval.
Fatal High Limit > Fatal High Reset > Warning High Limit > Warning High Reset The high temperature limit can range from 30°C to 70°C (86°F to 160°F). Warning high/report - (warning high limit) When the temperature exceeds this value, a warning alert message is generated and the status of the Agent changes to warning.
Voltage Properties Voltages sensors measure the operating voltages of processors located in the CPU modules and option boards located within the PCI modules. Voltage Sensor - The name of the voltage sensor. Upper Fatal - The high voltage limit that triggers a fatal alert. Upper Warning - The high voltage limit that triggers a warning alert. Lower Fatal - The low voltage limit that triggers a fatal alert. Lower Warning - The low voltage limit that triggers a warning alert.
Watchdog Timer Properties Monitor OS Stall (Server) - When this item is checked, the watch dog timer on the mother board in the Agent sends a message to ESMPRO Manager when it detects that the operating system in the Agent is hung. Note: Your computer must be restarted before this setting takes effect. Monitor System Hangs (SMB) - Check this box to enable the watch dog timer to monitor the Agent.
Action After Timeout – None- No action is taken. Hard Reset – The system is rebooted. Power Cycle – The system is powered OFF, then immediately powered ON to clear an abnormal condition (Ex: hung operating system). Power Down (default) – The system is shutdown completely and powered off. Shutdown Properties Shutdown Properties when enabled allows the Agent to monitor operating system shutdown for errors. Timeout – The maximum amount of time the operating system should take to complete a shutdown.
ESMPRO Agent Considerations Module Status Messages A message indicating the change of module status may be sent twice. Devices Not Supported Monitoring of the SCSI enclosures, SCSI electronics, SCSI slots, and SCSI buses is not supported. "Unknown" is displayed for unsupported devices displayed in the data viewer. Disk failures reported to the ESMPRO Manager are confirmed using the alert viewer. Monitoring with NEC ESMPRO Manager Version 3.
BIOS and Agent Temperature Monitoring Temperature sensor enabling and temperature monitoring may be set by ESMPRO Agent or the BIOS Setup Utility. Temperature monitoring parameters set in either utility are automatically set in the other utility. IMPORTANT: If the OS has ACPI functionality, the thresholds of the temperature set in the BIOS are managed by the ACPI function of the OS. In this case, temperature threshold values set in NEC ESMPRO Agent are independent of values set in BIOS.
Warning Message about CPU Load When NEC ESMPRO Agent detects that it cannot get performance information from the OS because of temporarily insufficient system resources or a high load rate, NEC ESMPRO Agent registers the following syslog message Source: ESMCpuPerf Type: Information Event ID: 9005 Explanation: System performance information cannot be obtained. (Code=xxxx) If NEC ESMPRO Agent cannot get performance information, it processes the load rate as 0%.
Alert Report Device IDs Alert report Device IDs for the NEC Express5800/ft server are listed in the following table. Table 3-1.
4 Monitoring the ft Server ! Introduction ! Express5800/ft Maintenance ! Monitoring ft Server Using ESMPRO Manager ! Monitoring ft Server using ESMPRO Agent
Introduction ESMPRO provides several unique maintenance functions for the Express5800/ft Server. These include switching system modules Off and On and updating firmware in the Express5800/ft Server. Many maintenance functions may be executed in the online state in which the system continues normal operation. They may be executed at the managed ft server or from the ESMPRO management console.
Express5800/ft Maintenance Express5800/ft series maintenance can be performed in two ways; one is to use ESMPRO Manager for remote maintenance and the other is to use the ft Server Utility located on the managed Express5800/ft server.
Monitoring ft Server Using ESMPRO Manager The Data Viewer lets you check hardware and software features on servers monitored by ESMPRO Manager. The left pane of the Data Viewer display contains a directory of categories for the server or desktop. Click on + to expand the directory and - to contract it. Highlighting a category displays information in the right pane. In the tree view you may see one of three major folders labeled (ESMPRO MIB), (DMI) and (FTServer).
Starting the Data Viewer To start the Data Viewer: 1. From the ESMPRO Manager Operation Window, select your ft Server Agent icon. 2. Select any one of the following: ! Data Viewer from the Tools menu ! Data Viewer icon in the toolbar ! Data Viewer from the Command menu (displays when you right click on the server or desktop icon).
CPU Modules Your ft server includes two CPU modules that you may monitor using the Data Viewer. When you select a CPU module, five folder icons display: General, Maintenance, Update, CPU, and DIMM. General Selecting the General folder Data Viewer displays the CPU module General screen. The General screen displays information about the CPU module selected.
Update Select the Update folder. Data Viewer displays the CPU module Update screen. The Update display screen allows the device identification information of the CPU modules to be viewed and the firmware of the CPU modules to be updated. Firmware Update This function is not supported remotely. Jump Switch This function is not supported remotely.
Maintenance Select the Maintenance folder. Data Viewer displays the CPU module Maintenance screen. Bring Up/Bring Down: Using the Maintenance screen you can bring the selected CPU module up or down. When a module is brought down (stopped), firmware in this module may be updated or this module can safely be removed from your server. If one CPU module is down or removed, the system continues normal operation using the companion CPU module. Note: In the following procedure CPU module 1 will be brought down.
Dump Button: Pressing the Dump button copies current memory contents to a log file. Information in this log file may be used during troubleshooting procedures. Procedure: 1. In Data Viewer, select the General folder of CPU module 1. The General screen displays. 2. Check the current state of the Status display located at the bottom of this screen. A green Status display indicates the CPU module is up; a gray Status display indicates the CPU module is down.
CPU Select the CPU folder. Data Viewer displays the CPU module CPU screen. The CPU screen displays information about the selected CPU processor. This information includes CPU processor specifications, CPU core and level2 cache information and current CPU processor status. CPU Information: Specifications on the selected CPU.
DIMM Select the DIMM folder. Data Viewer displays the DIMM screen. The DIMM screen displays information about a specific memory DIMM located in the selected CPU module. This information includes DIMM specifications and information about the DIMM manufacturer. DIMM Error Correction Code (ECC) information is also included in this display screen. ECC Information: ESMPRO monitors and logs correctable, intermittent, and uncorrectable DIMM errors within predetermined thresholds you set.
PCI Modules Your ft server includes two PCI modules that you may monitor using the Data Viewer. Each PCI module contains four PCI adapter card slots and three embedded adapters (LAN, SCSI disk, and BMC). When you select a PCI module, seven folder icons display: General, Update, Maintenance, PCI Slot, SCSI Adapter, BMC and Ethernet Board. General Select the General folder. Data Viewer displays the PCI module General screen. The General screen displays technical information about the selected PCI module.
Update Select the Update folder. Data Viewer displays the PCI module Update screen. The Update screen displays technical information about the selected Prom located in the selected PCI Module.
Maintenance Select the Maintenance folder. Data Viewer displays the PCI module Maintenance screen. Bring Up/Bring Down: Using the Maintenance screen you can bring the selected PCI module up or down. When a module is brought down (stopped), firmware in this module may be updated or this module can safely be removed from your server. If one PCI module is down or removed, the system continues normal operation using the companion PCI module. Note: In the following procedure PCI module 1 will be brought down.
MTBF Information: The MTBF (Mean-Time-Between-Failures) information of a component can be viewed or cleared (initialized). Your server manages the MTBF of each component. If a fault occurs in a component, the module calculates the MTBF of the component again. If the calculated value is lower than the pre-defined threshold, the system performs one of the following predefined three functions: ! Use Threshold: MTBF is calculated when a fault occurs.
PCI Slots General Select the General folder. Data Viewer displays the PCI Slot General screen. The General screen displays technical information about the PCI adapter located in the selected PCI slot. Status: Status of this PCI adapter in this PCI slot. The color of this display indicates the current status of the adapter in this PCI slot as compared to the predefined threshold values set for this adapter.
Maintenance Select the Maintenance folder. Data Viewer displays the PCI slot Maintenance screen. Bring Up Demand: Bringing up individual slots with in the PCI module is not currently supported.
PCI Device General Select the General folder. Data Viewer displays the PCI Device General screen. The General screen displays a summary of technical information about the selected PCI device connected to the PCI adapter located in the selected PCI slot.
Detail Select the Detail folder. Data Viewer displays the PCI Device Detail screen. The Detail screen displays detailed technical information about the selected PCI device connected to the PCI adapter located in the selected PCI slot.
SCSI Adapter General Select the General folder. Data Viewer displays the SCSI Adapter General screen. The SCSI adapter is located within the selected PCI module. The General screen displays information pertaining to the selected SCSI adapter’s serial number, firmware release, and ROMBIOS revision. The current status of the adapter is also displayed. Status: Status of this SCSI adapter located within the selected PCI module.
Update Select the Update folder. Data Viewer displays the SCSI adapter Update screen. Firmware update of individual SCSI adapters is not currently supported.
Maintenance Select the Maintenance folder. Data Viewer displays the SCSI adapter Maintenance screen. Bring Up/Bring Down: Not currently supported. MTBF Information: The MTBF (Mean-Time-Between-Failures) information of a component can be viewed or cleared (initialized). Your server manages the MTBF of each component. If a fault occurs in a component, the module calculates the MTBF of the component again.
BMC The General screen displays technical information pertaining to the BMC in the selected PCI module.
Ethernet Board General Select the General folder. Data Viewer displays the Ethernet board General screen. The Ethernet board screen displays summary technical information pertaining to the selected Ethernet board. The current status of the adapter is also displayed. Status: Status of this Ethernet board located in the selected PCI module. The color of this display indicates the current status of the SCSI adapter as compared to the set threshold values. Green: Selected Ethernet board is up.
Detail The Detailed Ethernet board screen displays detail technical information pertaining to the selected Ethernet board.
Maintenance Select the Maintenance folder. Data Viewer displays the Ethernet board Maintenance screen. Bring Up/Bring Down: Not currently supported. MTBF Information: The MTBF (Mean-Time-Between-Failures) information of a component can be viewed or cleared (initialized). Your server manages the MTBF of each component. If a fault occurs in a component, the module calculates the MTBF of the component again.
Monitoring ft Server using ESMPRO Agent NEC Express5800/ft series maintenance is administered in two ways; one is to use NEC ESMPRO Manager for remote maintenance and the other is to use the NEC ESMPRO Agent ft server utility on the NEC Express5800/ft series for local maintenance. This section provides procedures on using the ft server utility to perform local maintenance on your ft server. Starting ft Server Utility 1. Log in the system as a root-authorized user. 2.
CPU Modules Your server includes two CPU modules that you may monitor using the ft Server Utility. When you select a CPU module, six CPU maintenance functions are displayed: MTBF Clear, Start/Stop, Module Diagnostic, Firmware Update, Board Switch and Dump. Module Diagnostic and Board Switch are not supported. This section provides procedures for viewing and using these functions. MTBF Information Clear The MTBF (Mean-Time-Between-Failures) information of a CPU Module may be cleared (initialized).
Start/Stop Using the ft Server Utility you can bring the selected CPU module up or down. When a module is brought down (stopped), firmware in this module may be updated or this module can safely be removed from your server. If one CPU module is down or removed, the system continues normal operation using the companion CPU module. Note: In the following procedure CPU module 1 will be brought down. Procedure 1. Select the CPU module #1 using the ft Server Utility. See above screen. 2.
CPU Module Diagnostic CPU Module Diagnostic is not supported. Firmware Update To update the firmware of a CPU module, the firmware image file of the updated firmware must previously be stored on the hard drive in the ft server. During the firmware update procedure you specify the absolute path of the firmware image. The CPU module requiring the firmware update is brought down (stopped) prior to beginning the update. The companion CPU module continues operation.
5. Enter the directory in which the updated firmware image is located (Step 1). After you have entered the absolute path of the firmware image, click on the Execute button to update the firmware. The “Firmware update completed” screen displays when the update has completed. CAUTION At this point in the firmware update procedure, each CPU module may be at different revision levels. Perform Step 6 immediately after confirmation that the firmware update has completed in Step 5. 6.
Procedure 1. In the ft server utility, select CPU Module #1. The above screen displays. 2. In the Dump section of the display, select whether you want to perform the memory dump with the CPU module up or down. IF you are performing the memory dump with the CPU module down, bring down the CPU module by performing the steps in Bring Up/Bring Down above. 3. Click on Execute button. The memory dump is stored as %SystemRoot%\memory.dmp on the server. The dump operation is reported as an alert by ESMPRO.
Note: A disabled component with the MTBF lower than the threshold, can be forcibly enabled by clearing the MTBF. Procedure: To clear the MTBF information of the PCI module, click on the MTBF button displayed in the ft Server Utility PCI module screen. Start/Stop Using the ft Server Utility you can bring the selected PCI module up or down. When a module is brought down (stopped), this module can safely be removed from your server.
Diagnostics Information PCI Module Diagnostic is not supported. SCSI Adapter MTBF Information Clear The MTBF (Mean-Time-Between-Failures) information of a PCI Module may be cleared (initialized). Your server manages the MTBF of each component. Each time a fault occurs in a component in a PCI module, the module recalculates the MTBF of the component.
Ethernet Board MTBF Information Clear The MTBF (Mean-Time-Between-Failures) information of a PCI Module may be cleared (initialized). Your server manages the MTBF of each component. Each time a fault occurs in a component in a PCI module, the module recalculates the MTBF of the component. If the calculated value is lower than the pre-defined threshold, the system performs one of the following predefined three functions: ! Use Threshold: MTBF is calculated when a fault occurs.
BMC Firmware The firmware located on the base management controller (BMC) can be updated using the BMC firmware update utility. The screen below displays when the BMC folder in the ft server utility is selected. Note: To update the BMC firmware, an image of the firmware image file must previously be stored on the server. During the firmware update procedure you specify the absolute path of the firmware image on the server as the firmware location. Firmware Update Procedure 1.
4. Select BMC FW update Property Setting. The BMC FW Update Property Setting screen displays. 5. Enter the directory in which the updated firmware image is located (Step 1 into the Data File Path. Other optional parameters may also be entered at this time. 6. Down arrow to Data save and exit. Press Enter. The BMC FW Update Tool screen displays. 7. Select BMC FW Update Command and press Enter. The Firmware update completed screen displays when the BMC firmware has been updated. 8.
10. Selecting Configuration in the above menu displays the Configuration Menu as shown below. 11. Select New or Change to configure System Management parameters. Refer to the Management Workstation Application (MWA) Setup and Configuration Guide included with your system for more information on configuring System Management.
Index A L About this guide, 1-2 Agent CPU tab, 3-16 for Linux, 3-14 General tab, 3-15 LAN tab, 3-18 settings, Linux, 3-14 Temperature tab, 3-19 Voltage tab, 3-21 Watch Dog Timer (WDT) tab, 3-22 Linux agent event setting, 3-12 syslog events setting, 3-13 C Conventions document, 1-2 CPU load threshold setting from the Linux Agent, 3-16 CPU Module monitoring with data viewer, 4-6 monitoring with ft server utility, 4-28 D Data Viewer accessing from ESMPRO Manager, 4-5 ft Server monitoring, 4-4 Dialog box
xx
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ 455-01664-001
