NEC Express5800-320La Configuration Guide

()

■■■■■■■

EXPRESS5800/320La/320La-R

Linux Network Operating

System Configuration

Guide

■■■■■■■

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.

The NEC Solutions (America), Inc. product(s) discussed in this document are warranted in accordance with the terms of the Warranty Statement accompanying each product. However, actual performance of each product is dependent upon factors such as system configuration, customer data, and operator control. Since implementation by customers of each product may vary, the suitability of specific product configurations and applications must be determined by the customer and is not warranted by NEC Solutions (America), Inc.

To allow for design and specification improvements, the information in this document is subject to change at any time, without notice. Reproduction of this document or portions thereof without prior written approval of NEC Solutions (America), Inc. is prohibited.

Trademarks

NEC ESMPRO is a trademark of NEC Corporation. Linux is a registered trademark of Linus Torvalds, Inc. Red Hat is a registered trademark of Red Hat, Inc.

All other trademarks belong to their respective owners.

PN: 455-01664-001 March 2003

NEC Solutions (America), Inc

10850 Gold Center Drive, Suite 200,

Rancho Cordova, CA 95670

Proprietary Notice and Liability Disclaimer Introduction

About This Guide......................................................................................................................1-2

Document Conventions.............................................................................................................1-2

How This Guide Is Organized...................................................................................................1-2

Related Documents....................................................................................................................1-3

Where to Go From Here............................................................................................................1-3

Configuring Linux

Overview ...................................................................................................................................2-2

Powering up the Server .............................................................................................................2-3

Configuring the Network Interface............................................................................................2-3

Onboard Integrated Network Interface Controllers ........................................................2-3

Adding Optional PCI Network Interface Controllers .....................................................2-6

Deleting Optional PCI Network Interface Controller Settings.......................................2-6

Confirming Information IP Addresses............................................................................2-7

Configuring Internal Disk Drives..............................................................................................2-8

Disk Administrator Tool (ftdiskadm)........................................................................................ 2-10

Confirming SCSI Disk Status.................................................................................................... 2-11

Setting SCSI Topology.............................................................................................................. 2-13

Starting SCSI Disk(s)................................................................................................................2-15

Stopping SCSI Disk(s) .............................................................................................................. 2-16

Adding Internal Disks................................................................................................................ 2-17

Replacing Internal Disk(s)......................................................................................................... 2-19

Replacing the Disk .................................................................................................................... 2-20

Reinstalling Linux..................................................................................................................... 2-22

ESMPRO Agent for Linux

NEC ESMPRO Agent ...............................................................................................................3-2

Required Software Modules......................................................................................................3-2

Installing the Agent...................................................................................................................3-2

Starting portmap..............................................................................................................3-2

Setting SNMP Service ....................................................................................................3-3

New Installation..............................................................................................................3-3

Updating the Agent.........................................................................................................3-4

Report Setting............................................................................................................................3-6

Setting Manager Reporting (SNMP)...............................................................................3-6

Base Settings...................................................................................................................3-7

Manager SNMP Trap Setting.................................................................................................... 3-8

Manager (TCP_IP In-Band) and Manager (TCP_IP Out-of-Band)...........................................3-8

Destination ID Settings...................................................................................................3-9

Scheduling Responses............................................................................................................... 3-10

Manager (TCP_IP In-Band)...................................................................................................... 3-10

Manager (TCP_IP Out-of-Band)............................................................................................... 3-11

Agent Events Setting................................................................................................................. 3-12

Syslog Events Setting................................................................................................................ 3-13

Agent Monitoring...................................................................................................................... 3-14

General Properties.....................................................................................................................3-15

Contents iii

CPU Properties..............................................................................................................3-16

File System Properties...................................................................................................3-17

LAN Properties..............................................................................................................3-18

Temperature Properties .................................................................................................3-19

Voltage Properties.........................................................................................................3-21

Watchdog Timer Properties...........................................................................................3-22

Shutdown Properties......................................................................................................3-23

ESMPRO Agent Considerations..............................................................................................3-24

Module Status Messages...............................................................................................3-24

Devices Not Supported..................................................................................................3-24

Monitoring with NEC ESMPRO Manager Version 3.7 or Before................................3-24

Display of the Ethernet Board Status ............................................................................3-24

Change of Installation States of CPU and PCI Modules...............................................3-24

LAN Monitoring Report................................................................................................3-24

Current Value of MTBF................................................................................................3-24

BIOS and Agent Temperature Monitoring....................................................................3-25

Memory Error Alarm.....................................................................................................3-25

Thresholds.....................................................................................................................3-25

Alerts.............................................................................................................................3-25

Warning Message about CPU Load..............................................................................3-26

Stopping of the Primary PCI Module by the Server Utility ..........................................3-26

Collection of Dump by the Server Utility .....................................................................3-26

Alert Report Device IDs..........................................................................................................3-27

Monitoring the ft Server

Introduction................................................................................................................................4-2

Express5800/ft Maintenance......................................................................................................4-3

Monitoring ft Server Using ESMPRO Manager........................................................................4-4

Starting the Data Viewer.................................................................................................4-5

CPU Modules..................................................................................................................4-6

PCI Modules..................................................................................................................4-12

SCSI Adapter.................................................................................................................4-20

BMC..............................................................................................................................4-23

Ethernet Board...............................................................................................................4-24

Monitoring ft Server Using ESMPRO Agent..........................................................................4-27

Starting ft Server Utility................................................................................................4-27

General ..........................................................................................................................4-27

CPU Modules................................................................................................................4-28

PCI Modules..................................................................................................................4-32

SCSI Adapter.................................................................................................................4-34

Ethernet Board...............................................................................................................4-35

BMC Firmware..............................................................................................................4-36

Index

iv Contents

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.

This guide also includes information on installing, configuring and using ESMPRO Agent on Express5800/320La systems that include the Linux Operating System.

For additional information, it is important to read the READ ME files and related documentation provided by the vendor of your network operating system.

Document Conventions

This guide uses the following text conventions. Notes have the following meaning:

Note: Notes give important inf orm ation abo ut the

material being described.

The notational conventions listed below are used throughout this guide.

Italic

Bold

Used for user command input, file names and keywords.

Used for system prompts and command definitions.

How This Guide Is Organized

This guide contains the following information:

! Chapter 1 Introduction — This chapter contains general information

about this guide and related documents.

! Chapter 2 Configuring Linux

information for configuring the Linux Operating System.

! Chapter 3 ESMPRO Agent for Linux — This chapter contains

information for installing, configuring and using ESMPRO Agent.

— This chapter contains supplemental

! Chapter 4 Monitoring the ft Server — This chapter contains

1-2 Introduction

information on using ESMPRO Manager and ESMPRO Agent to run the ft Server Utility.

Where to Go From Here

Where you go to continue your installation depends on how your system was shipped:

! If you are powering up your server for the first time go to Chapter 2 to

configure the Linux Operating System.

! If you are installing or configuring ESMPRO Agent for Linux, go to

Chapter 3.

! If you require information on the use of ESMPRO Manager or ESMPRO

Agent to run the ft Server Utility, go to Chapter 4.

Introduction 1-3

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.

2-2 Configuring Linux

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.) The following applications are loaded :

! apache ! sendmail ! bind ! NFS ! NEC ESMPRO Agent

Configuring the Network Interface

After initial power up of the server, the onboard integrated network interface controllers (NICs) and any installed network controller cards must be configured.

Onboard Integrated Network Interface Controllers

Each PCI module in your server includes a 10BASE-T/100BASE-TX network controller based on the Intel 82559 Fast Ethernet Network Interface. Perform the following steps to set a dual configuration for the onboard controllers:

1. Log on to the system as root.

2. Confirm that NIC information is displayed for slot 7. Type:

vndctl status

Slot 7 is the logical location of the onboard network controllers. The following screen displays.

--Virtual Network Status-virtual status config slot real(s)

slot real status link

1 left -

right -

2 left -

right -

3 left -

right -

4 left -

right -

5 left -

right -

6 left -

right -

7 left epro01.06 -

right epro09.06 -

Configuring Linux 2- 3

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.06 DOWN

Link encap:Ethernet HWaddr 00:00:4C:0F:F7:E0 BROADCAST SLAVE MTU:1500 Metric:1 RX packets:4938 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 Interrupt:15 Base address:0x8000

right epro09.06 DOWN

Link encap:Ethernet HWaddr 00:00:4C:0F:F7:E0 BROADCAST SLAVE MTU:1500 Metric:1 RX packets:11135 errors:0 dropped:0 overruns:0 frame:0 TX packets:4086 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 Interrupt:21 Base address:0x3000

Referring to the above table, ha0 defines the two NICs as a duplex NIC, listing them as a single NIC. The remainder of the table shows the set values of the two actual NICs.

5. Configure the NICs of the duplex slot 7. Type:

vndctl config 7

6. Activate the NIC interface of the duplex slot 7. Type:

vndctl up 7

2-4 Configuring Linux

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 real status link

1 left -

right -

2 left -

right -

3 left -

right -

4 left -

right -

5 left -

right -

6 left -

right -

7 left epro01.06 UP LINK

right epro09.06 UP 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.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.0 UP BROADCAST RUNNING 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.06 UP LINK

Link encap:Ethernet HWaddr 00:00:4C:0F:F7:E0 UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1 RX packets:4989 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 Interrupt:15 Base address:0x8000

right epro09.06 UP LINK

Link encap:Ethernet HWaddr 00:00:4C:0F:F7:E0 UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1 RX packets:11186 errors:0 dropped:0 overruns:0 frame:0 TX packets:4086 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 Interrupt:21 Base address:0x3000

Configuring Linux 2- 5

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. Refer to the system user’s guide for procedures on installing boards into the PCI modules. Power up and logon to the system as root and enter the following commands to configure the NICs.

2. Confirm that the server has recognized the added NICs. Note the slot

number of the added NICs. Type:

vndctl status

Note: An “n” in the commands in the next three steps

indicates the slot number (1 - 6) of the slot containing the optional NIC boards.

3. Add the NICs of slot n to the VND list. Type:

vndctl add n

4. Configure the NICs of the duplex slot n. Type:

vndctl config n

5. Activate the NICs of the duplex slot n. Type:

vndctl up n

Deleting Optional PCI Network Interface Controller Settings

Perform the following steps to delete NIC settings.

Note: An “n” in the commands of the next two steps

indicates the slot number (1 - 6) of the slot containing the optional NIC boards.

1. If the target NICs are active, deactivate them. Type:

vndctl down n

2. Delete the NICs of the specified slot number from the VND list. Delete the

NIC setting as well. Type:

vndctl del n

3. Confirm the status of the NICs deleted. Type:

vndctl status

2-6 Configuring Linux

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.0 UP BROADCAST RUNNING 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.06 UP LINK

right epro09.06 UP LINK

Configuring Linux 2- 7

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 duplex access channel is implemented by giving each group of drives separate channels from two PCI modules. Physical access channels for internal SCSI disks are set in dual configuration as shown in the below table. Dual channel access to all drives is available from either PCI module. Refer to the table below. The server also provides a single channel for general SCSI disks.

Channels for SCSI Disks

PCI1 – Channel1 – SCSI Slot 1, 2, 3 PCI1 – Channel2 – SCSI Slot 4, 5, 6 PCI2 – Channel1 – SCSI Slot 4, 5, 6 PCI2 – Channel2 – SCSI Slot 1, 2, 3

The table below shows the correlation between the SCSI disk slot numbers and device names. Use the device names to access the internal SCSI disks and perform operations.

Slot number Device name

1sda 2 scb 3sdc 4sdd 5sde 6sdf

IMPORTANT: When a disk is added or RAID is rebuilt, each disk e nters the

"RESYNCING" or "RECOVERY" state. While the disks are in this state, do not remove them, turn off the power, or restart the system. Wait until RESYNCING" or "RECOVERY" has completed. (You can confirm the current RAID status by executing ftdiskadm.) If you should accidentally reboot your system during the "RESYNCING" or "RECOVERY" state, the data on your disks has not been corrupted. After reboot, the "RESYNCING" of your disks restarts from the beginning. Yo ur server is not in a fault tolerant state until "RESYNCING" has completed.

2-8 Configuring Linux

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

SLOT1 SLOT2 SLOT3

Group 1 Group 2

SLOT4 SLOT5 SLOT6

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.

Configuring Linux 2- 9

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.

# ftdiskadm Command action

1 => SCSI 2 => RAID 3 => Environment

9 Quit Command: 2 Command action

1 Status(Raid)

2 Status(All Disks)

3 Repair Disk

4 New Disks

5 Remove Half Disk

6 Remove Full Disks

9 <= RETURN

Command:

...

2-10 Configuring Linux

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 -buspci(haddr)

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.0)

-- SYSTEM -slot name use serial tuple path 1 sda 7 #3BT2B1NQ000021369EYFb0t0l0 d1h0c0t0l0

234 sdd 7 #3BT2B0C300002135HRWGb1t0l0 d1h0c1t0l0

56-

-- EXTENSION-name use serial tuple path sdg 0 #0000924310220000 b3t0l0 d0h3c0t0l0

sdh 0 #0000924310220001 b3t0l1 d0h3c0t0l1 sdk 0 #0000924310220002 b3t0l2 d0h3c0t0l2

d1h1c1t0l0

d1h1c0t0l0

b2t0l0 d0h2c0t0l0 b2t0l1 d0h2c0t0l1 b2t0l2 d0h2c0t0l2

The "-- BUS --" area shows SCSI bus information.

bus: <SCSI BUS No.> pci: <PCI BUS No.>:<PCI SLOT No.>.<CHANNEL No.> (haddr): <hardware address> (See Table 3-1 for a listing of hardware ID addresses.)

The "-- SYSTEM --" area shows information on the standard internal SCSI disk.

The "-- EXTENSION --" area shows information on SCSI disks connected to an optional SCSI board installed in a PCI slot of a PCI module.

slot: <SCSI disk slot No.> name: <Device name> use: <Current use count> serial: #<serial number> tuple: <SCSI tuple> path: <SCSI path>

Configuring Linux 2- 11

The following are determined: <SCSI tuple> = b<BUS No.>t<TARGET No.>l<LUN> <SCSI path> = d<DOMAIN No.>H<HOST No.>c<CHANNEL

No.>t<TARGET No.>l<LUN> 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.

[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 /tmp DUPLEX (1)sda7 (4)sdd7

-------------------------------------------------------------

name: Software RAID device name partition: Mount point or swap. If neither mount point nor swap is displayed,

the RAID is configured, but it is not mounted as a file system. member: Information of the members making up the RAID. Information in the

following format is displayed for each member: (slot-number) name

If a member is in error state, the (F) mark is shown to right of the member. In this case, the RAID needs to be repaired.

status: Status information as shown below. DUPLEX:Normal state RESYNCING(X.X%): Synchronization in progress. DUPLEX is displayed

when synchronization is completed. RECOVERY(X.X%): Recovery in progress. A member for which "-" is

displayed in Column "member" is not installed yet. SIMPLEX: RAID installed in only one system. If two members are displayed

in the column "member," the member with "-" displayed is in standby state before the RECOVERY state. If only one member is displayed, the RAID needs to be repaired.

ERROR: No RAID members exist.

2-12 Configuring Linux

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.CHANNEL_NO > /proc/scsi/topo

where bn is the SCSI bus number format: Device format (Example: qla2300 or qla12160) PCI_BUS_NO: 01 for the left PCI, and 09 for the right PCI PCI_SLOT_NO: PCI slot number (00,01,02... from left) CHANNEL_NO: Channel number (The first channel number is 00.) If multiple channels exist for a single SCSI bus, a set of "format" and

"PCI_BUS_NO:PCI_SLOT_NO.CHANNEL_NO" must be specified listed for each channel.

3. If another SCSI bus exists on the same domain, repeat step 2.

4. Confirm the settings in the /proc/scsi/topo file, and then execute the

following command to save the topology:

ftdisk topology-save

Consequently, the topology setting is restored when the system restarts.

Note: To delete a topology setting item, execute "rm

/opt/nec/ftras/etc/scsi-topology.save," remove the topology file, restart the system, and then perform the procedure starting with step 1.

For example, when two Qlogic 2310F extension boards are mounted in slot #4 of each PCI module, you can execute the following commands:

echo ‘setdomain 2’>/proc/scsi/topo echo ‘bus 2 qla2300 01:03:00 qla2300 09:03:00’>/proc/scsi/topo cat /proc/scsi/topo

The following information displays.

Configuring Linux 2- 13

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.

2-14 Configuring Linux

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)

<<Confirm the started SCSI disk(s)>>

Notes:

1. To obtain a disk specification method list, enter '?'. An asterisk * can be specified for TARGET and LUN. A value 0 to (maximum disk

number of successfully started disks + overrun count) can be specified. For TARGET, the overrun count is the value specified in the environment variable FTDISKADM_TID_OVERRUN. For LUN, the overrun count is the value specified in the environment variable FTDISKADM_LUN_OVERRUN. To confirm/change the value, select [Environment] from each menu. There are other specification methods - for example, listing numeric values in brackets [ ] (e.g., [<num1>,<num2>]) and specifying a range of numeric values (e.g., [<num3><num5>]).

2. If the overrun value is 1 or more, the number of disks in accordance with the value fail to start.

Confirm the status after executing the command.

Configuring Linux 2- 15

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

<<Confirm the started SCSI disk(s)>>

Notes:

1. To obtain a disk specification method list, enter '?'. An asterisk * can be specified for TARGET, LUN, serial number, and device name. It is

applicable to all candidates. There are other specification methods for TARGET and LUN for example, listing numeric values in brackets [ ] (e.g., [<num1>,<num2>]) and specifying a range of numeric values (e.g., [<num3>-<num5>]).

2-16 Configuring Linux

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. The following is an example of configuring additional internal SCSI disks in slots 3 and 6 by using ftdiskadm:

# ftdiskadm Command action

1 => SCSI 2 => RAID 3 => Environment

9 Quit Command: 2 Command action

1 Status(Raid)

2 Status(All Disks)

3 Repair Disk

4 New Disks

5 Remove Half Disk

6 Remove Full Disks

9 <= RETURN Command: 4 [New Disks]

* Which SCSI SLOT? [1-6] 3 (see Note 1) * Input the LABEL [1-12 character(s)] extra (See Note 2) Making the disk partition table: SLOT=3 SIZE=17343(MB)

* How many partitions? [1-12] 3 (see Note 3)

* Input the SIZE of partition 1 [1- 16318(MB)] 1024

* Input the SIZE of partition 5 [1- 15295(MB)] 2048

partition 6 14271

* Are you sure to create it? [y/n ] y

Notes:

1. Specify a SCSI slot number with a disk inserted in the slot. At this time, another disk must also be inserted in the slot paired with the specified one.

2. Enter the disk label if necessary. If the disk is used as a single partition, the value entered as the disk label is used as is. If the disk is used divided into multiple partitions, "entered-valu e_ s<p artition-number>" is used. You can change the disk label later by using a command such as e2label.

3. Enter the number of partitions into which the disk is to be divided. Enter the size of each partition in MB units. The size of the last partition is the remaining area, which is automatically allocated. The partition number 1 is followed by 5, and the subsequent numbers are assigned in ascending order. Since a disk of a specified capacity is reserved for the last partition, only a value smaller than the actual disk capacity can be entered. The actual capacity of a partition varies slightly depending on the disk structure.

Finishing the above specification starts creating the RAID configuration. If no problems occur, the creation of the RAID configuration is completed. To confirm the RAID status, execute [Status Raid] in the above.

Configuring Linux 2- 17

Confirm the disk status (check if the disk(s) has been added normally).

Command action

1 Status(Raid) 2 Status(All Disks) 3 Repair Disk 4 New Disks 5 Remove Half Disk 6 Remove Full Disks

9 <= RETURN Command: 1 [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 RESYNC(9

.3%) md8 extra_s5 RESYNC (3)sdc5 (6)sdf5 md9 extra_s6 RESYNC (3)sdc6 (6)sdf6

-------------------------------------------------------------------------------

Command action

1 Status(Raid) 2 Status(All Disks) 3 Repair Disk 4 New Disks 5 Remove Half Disk 6 Remove Full Disks 9 <= RETURN

Command:

(3)sdc1 (6)sdf1

2-18 Configuring Linux

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.

The following shows an example of processing from disk #3 removal to RAID restoration:

# ftdisk adm

Command action

Command: 2 Command action

1 => SCSI 2 => RAID 3 => Environment 9 Quit

1 Status(Raid) 2 Status(All Disks) 3 Repair Disk 4 New Disks 5 Remove Half Disk 6 Remove Full Disks

9 <= RETURN Command: 5 [Remove Half Disk]

* Which SCSI SLOT? [1-6] 3 mdctl: set /dev/sdc6 faulty in /dev/md9 mdctl: hot removed /dev/sdc6 mdctl: set /dev/sdc1 faulty in /dev/md7 mdctl: hot removed /dev/sdc1 mdctl: set /dev/sdc5 faulty in /dev/md8 mdctl: hot removed /dev/sdc5

Command action

1 Status(Raid)

2 Status(All Disks)

3 Repair Disk

4 New Disks

5 Remove Half Disk

6 Remove Full Disks

9 <= RETURN Command: 1

<<<Confirm that the disk has been removed>>>

Configuring Linux 2- 19

[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

----------------------------------------------------------------------------------

Command action

1 Status(Raid) 2 Status(All Disks) 3 Repair Disk 4 New Disks 5 Remove Half Disk 6 Remove Full Disks 9 <= RETURN

The following is an example of restoring (repairing) RAID (Step 3 of this procedure).

Command action

1 Status(Raid) 2 Status(All Disks) 3 Repair Disk 4 New Disks 5 Remove Half Disk 6 Remove Full Disks

9 <= RETURN Command: 3 [Repair Disk]

* Which SCSI SLOT? [1-6] 3 mdctl: hot added /dev/sdc6 mdctl: hot added /dev/sdc1 mdctl: hot added /dev/sdc5

Command action

1 Status(Raid)

2 Status(All Disks)

3 Repair Disk

4 New Disks

5 Remove Half Disk

6 Remove Full Disks

9 <= RETURN Command: 1

2-20 Configuring Linux

[Status(Raid)]

---------------------------------------------------------------------------------name partitionlabel 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 RECOVERY(1.0%)-(3)sdc6 (6)sdf6

---------------------------------------------------------------------------------Command action

1 Status(Raid) 2 Status(All Disks) 3 Repair Disk 4 New Disks 5 Remove Half Disk 6 Remove Full Disks 9 <= RETURN

Command: 9

Configuring Linux 2- 21

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.

Prerequisites: Install disk, backup CD-ROM1, and backup CD-ROM2

IMPORTANT: The Fail LED indicators located on the front of the CPU and

PCI modules, light red during the reinstallation of Linux. In this instance, the red LEDs do not indicate module failure. When the Linux reinstallation is complete and each module is placed in dual configuration mode, the Fail LEDs go off. Refer to Chapter 1 of your system User’s Guide for more information on CPU and PCI module LED indicator states.

The installation process of FT-Linux is based on an unattended installation of Linux, also called kickstart. The process is driven by the kickstart file, ks.cfg, located on the installation floppy. If you need to modify the default partitioning, the language supported, or the packages installed, please edit this file and change the parameters accordingly. For more information consult “The Official Red Hat Linux Customization Guide, Red Hat Linux 7.1,” detailing all parameters of the files.

IMPORTANT: Be sure to o nly append to the %Post section of the kickstart file,

as all customization concerning the installation of the fault-tolerant modules is performed here. Do not modify these commands or the fault tolerance of your system is not guaranteed.

When modifying partitioning during installation, be sure to declare only mirror partitions and of a different size. If you do not use mirror partitions, the fault tolerance of your system is not guaranteed. A known bug in the Anaconda installer mixes up the raid volumes if you declare same size partitions. Use a slightly different size. For example, if you want to create two mirrored 1GB partitions to mount on /mount1 and /mount2, do not use:

part raid.m1a --size 1024 --ondisk sda part raid.m1b --size 1024 --ondisk sdb part raid.m2a --size 1024 --ondisk sda part raid.m2b --size 1024 --ondisk sdb raid /mount1 --level 1 --device md0 raid.m1a raid.m1b raid /mount2 --level 1 --device md1 raid.m2a raid.m2b

Use:

part raid.m1a --size 1024 --ondisk sda part raid.m1b --size 1024 --ondisk sdb part raid.m2a --size 1000 --ondisk sda part raid.m2b --size 1000 --ondisk sdb raid /mount1 --level 1 --device md0 raid.m1a raid.m1b raid /mount2 --level 1 --device md1 raid.m2a raid.m2b

Do not attempt to configure X. The X server is currently not supported. You can however install X packages to support X clients.

2-22 Configuring Linux

+ 72 hidden pages

NEC Express5800-320La Configuration Guide

Specifications and Main Features

Frequently Asked Questions

User Manual

Proprietary Notice and Liability Disclaimer

Contents

Introduction

About This Guide

Document Conventions

How This Guide Is Organized

Related Documents

Where to Go From Here

Configuring Linux

Overview

Powering up the Server

Configuring the Network Interface

Onboard Integrated Network Interface Controllers

Adding Optional PCI Network Interface Controllers

Deleting Optional PCI Network Interface Controller Settings

Confirming Information IP Addresses

Configuring Internal Disk Drives

Disk Administrator Tool (ftdiskadm)

Reinstalling Linux