Page 1 Express5800/ftServer: System Administrator’s Guide ® for the Linux Operating System NEC Corporation of America 456-01730-000...
Page 2 Software described in NEC (a) is the property of NEC and/or its licensees, (b) is furnished only under license, and (c) may be copied or used only as expressly permitted under the terms of the license.
Page 3: Table Of Contents
Installing and Updating So ftware on ftServer Systems Updating ftServer System Firmware Con guring Your ftServer System Managing Data Storage Devices Using the Express5800/ftServer Fault-Tolerant Express Builder 1-3 Network Management and Reporting Troubleshooting ftServer Systems Additional Documentation and Resources Red Hat Enterprise Linux...
Page 4 Related Information and Resources 5. Setting Up the ftServer System Setting Up Internal Disk Storage Internal Disk Storage Overview The Console Log and the /var/log/messages File Configuring Internal Disks Managing Partitions Express5800/ftServer: System Administrator’s Guide for the Linux Operating System...
Page 5 Contents Default Internal Disk Configuration for a Newly Installed System Checking the Current State of the Internal Disk Subsystem Storage Device Definition Setting Up RAID Arrays RAID Array Overview Creating a RAID-1 Array 5-10 Creating a RAID-0 Array 5-12 Creating and Mounting a File System 5-14 Checking the Current State of RAID 5-14...
Page 6 8-18 Testing Your SNMP Configuration 8-19 Managing ftServer Hardware Components 8-20 Example: Managing Hardware 8-21 Testing Ethernet Ports 8-23 Example: Testing Ethernet Ports 8-23 SNMP and MIBS 8-24 Device Enumeration 8-25 Express5800/ftServer: System Administrator’s Guide for the Linux Operating System...
Page 7 Contents ftServer System Operation State Management 8-25 SNMP Network Management Station Considerations 8-26 Initial SNMP Testing 8-27 Initial Testing of ftltrapsubagent 8-27 Initial Testing of ftlsubagent 8-29 Removing ftlSNMP 8-29 OpState:State Definitions 8-30 OpState:Reason Definitions 8-31 GET and SET Operations for ftlSNMP MIB Objects 8-32 SRA-ftLinux-MIB OID Values and Properties 8-32...
Page 8 Figure 7-1. ftServer Enclosures: Locations of Major Enumerated Devices (Front View) Figure 7-2. ftServer Enclosures: Locations of Major Enumerated Devices (Rear View) Figure 8-1. AgentX-Enabled Extensions and Subagents 8-17 Figure 8-2. Operational State Management on ftServer Systems 8-25 viii Express5800/ftServer: System Administrator’s Guide for the Linux Operating System...
Page 9 Tables Table 2-1. CD-ROMs Included With ftServer Systems Table 5-2. Ethernet Devices in ftServer CPU-I/O Enclosures 5-27 Table 7-1. Device Paths of ftServer Devices Table 8-1. Meaning of Duplex for ftServer System Components 8-26 Table 8-2. Operation State Values, Names, and Definitions 8-30 Table 8-3.
Page 10 Example 8-3. Traps That Can Occur for When Trap Filtering Is Off 8-40 Example 8-4. Traps That Can Occur When Trap Filtering Is On 8-41 Example 9-1. Possible Keyboard and Mouse Error Messages at Boot Time Express5800/ftServer: System Administrator’s Guide for the Linux Operating System...
Page 11: Preface
Preface The Express5800/ftServer: System Administrator’s Guide for the Linux Operating System documents tasks and information for system administrators of NECAM systems running a supported Linux distribution and ftControl system software sfor the Linux Operating System (Express Builder). This document is intended for system and network administrators using or migrating to...
Page 12 Although a prompt is sometimes shown at the beginning of a command line as it would appear on the screen, you do not type it. Express5800/ftServer: System Administrator’s Guide for the Linux Operating System...
Page 13: Getting Help
Any list or set of arguments can contain more than two elements. Brackets and braces are sometimes nested. Getting Help If your Express5800/ftServer system is covered by a service agreement, please contact NEC Corporation of America Technical Support (866-269-1239). Notices All regulatory notices are provided in the site planning guide for your system.
Page 14 Preface VTM is not available with Express5800/ftServer for Linux systems. Express Service Network is not available with Linux systems. Although this guide may document modem functionality, modems are not available for all systems. Ask your sales representative about modem availability.
Page 15: Introduction To Ftserver System Administration
Resources” ftServer systems running a supported Linux distribution together with Express5800/ftServer System Software for the Linux Operating System (Express Builder) operate as fault-tolerant servers. The supported server models are the Express5800/ ftServer Dual-Core and Quad-Core systems. Every Express5800/ftServer system uses...
Page 16: Ftserver System Terminology
Express Builder, use the versions of firmware and software that are supplied on the ExpressBuilder for Linux CD. Chapter 3 provides procedures for updating your system BIOS and Baseboard Management Controller (BMC) firmware. Express5800/ftServer: System Administrator’s Guide for the Linux Operating System...
Page 17: Con Guring Your Ftserver System
They include the Express Service Network package that provides support for Express Service Network access using an attached modem. This package allows the NEC Corporation of America Customer Support Center or your authorized NEC service representative to provide remote support for your system. Your system comes with Express Service Network installed.
Page 18: Red Hat Enterprise Linux
Sunsite Web page, University of North Carolina, provides well-ordered archives • and links to many resources: ftp://sunsite.unc.edu/pub/Linux/. Linux Administration Handbook, by Nemeth, Snyder, and Hein, copyright 2002, • Prentice Hall PTR, div. of Pearson Education, Inc.: Express5800/ftServer: System Administrator’s Guide for the Linux Operating System...
Page 19 Additional Documentation and Resources http://vig.prenhall.com/catalog/academic/product/0,4096,0130084662,00.html This volume is a reference manual for both system and network administration of the Linux operating system. It focuses on available (at time of publication) open source tools but incorporates in-depth knowledge of UNIX administration utilities and network management practices.
Page 20 Additional Documentation and Resources Express5800/ftServer: System Administrator’s Guide for the Linux Operating System...
Page 21: Installing The Operating System And Express5800/Ftserver System Software
‘‘Additional Documentation and Resources” The procedures described in this chapter are for a fresh installation or complete reinstallation of a supported Linux operating system and the Express5800/ftServer System Software for the Linux Operating System (Express Builder) on ftServer systems. Chapter 4 describes an upgrade procedure and system and package restoration procedures for upgrading a recent distribution to the current software distribution level.
Page 22: Installation Overview
Notes:Express5800/ftServer for the Linux Operating System, then see Chapter4 and, if necessary, Chapter If some time has elapsed since your Express5800/ftServer system was delivered, there may be updated documentation and software that may be useful to you. N O T E Firmware updates may require Express Builder updates.
Page 23: Boot Media
This section provides an overview of the default setup that is provided on initial installation or complete reinstallation of the Linux operating system distribution. It does not reflect installation of optional packages. Installing the Operating System and Express5800/ftServer System Software...
Page 24: Linux Version Information
The terms upper, top, lower, and bottom assume a rack (horizontal) installation. In pedestals, systems are rotated 90 degrees counterclockwise from their rack-mounted position, so upper becomes left, lower becomes middle or right, and bottom becomes right. Express5800/ftServer: System Administrator’s Guide for the Linux Operating System...
Page 25: Ethernet Default Con Guration
All internal drives used in mirrored RAID arrays in the internal hot-swap drive bays must have firmware that meets ftServer specifications. Do not update your internal drives with firmware from sources other than NEC Corporation of America. Contact your NEC Corporation of America Customer Support Center or your authorized NEC service representative for your internal SAS (SATA) drive support requirements.
Page 26: Default System Initialization And Run-Level Control
Always use the software packages that are provided with the Express Builder distribution, unless you have good reason to replace a package. Before updating a distribution package, use rpm Express5800/ftServer: System Administrator’s Guide for the Linux Operating System...
Page 27: Installation Interfaces
Supported Hardware and Firmware The Linux operating system combined with Express Builder can be installed only on supported Express5800/ftServer Dual-Core and Quad-Core systems. Do not attempt to install this software combination on an ftServer system that does not support it. Express Builder interfaces with ftServer firmware that has been tuned to support fault tolerance.
Page 28 During the installation, the two installed drives will be paired and configured using RAID-1 mirroring. A Linux boot partition, a swap partition, and a root partition will be installed on the paired drives. Express5800/ftServer: System Administrator’s Guide for the Linux Operating System...
Page 29: Initial Linux Operating System And Express Builder Installation Or Default Reinstallation
Initial Linux Operating System and Express Builder Installation or Default Reinstallation The User Guide (Setup) contains detail procedures to install the Linux operationg system and the ftControl Software. Installing the Operating System and Express5800/ftServer System Software...
Page 30: Avoiding Cd-Rom Mount Command Failure After Disabling Selinux
If the OS installation fails, whether or not Express Builder installed successfully, attempt to boot the system in rescue mode. Use the Red Hat Enterprise Linux CD-ROM #1 to boot in rescue mode. 2-14 Express5800/ftServer: System Administrator’s Guide for the Linux Operating System...
Page 31 You may need to remove and re-apply system power before you can reboot from the disk. If the disks are not detected and automounted, contact the NEC Corporation of America Customer Support Center or your authorized NEC service representative for assistance.
Page 32: Post-Installation Tasks And Considerations
2. In the graphical network configuration tool, specify the network hostname for your system. See the section on adding hosts in the Red Hat Enterprise Linux 4 System Administration Guide for detailed information about configuring networks. 2-16 Express5800/ftServer: System Administrator’s Guide for the Linux Operating System...
Page 33: Adding Fault-Tolerant Utilities To Path
If this happens, you can recover by power-cycling the system and booting again. This command is necessary for your Express5800/ftServer to be fault-tolerant. You can find additional information about the kickstart files in the Red Hat Linux OS system administration documentation.
Page 34: Additional Documentation And Resources
• http://www.gnu.org/software/grub/grub.en.html GRUB: GRand Unified Bootloader version 0.5, original documentation Web site: • http://www.uruk.org/orig-grub/ GRUB file system syntax and semantics document, by Eric Bolyn, primary author • of GRUB: http://www.uruk.org/orig-grub/filesystem.txt Express5800/ftServer: System Administrator’s Guide for the Linux Operating System 2-18...
Page 35: Updating Ftserver System Firmware
Make sure that the BIOS you intend to install is compatible with the Express Builder release level that you have (or that you will install immediately after performing the BIOS upgrade). Verify in the applicable version of the Release Notes: Express5800/ftServer for the Linux Operating System that the BIOS is compatible, and also that the Release Notes do not specify a different procedure or sequence for performing the BIOS update.
Page 36 Table 7-1 for a list of system device IDs). Express5800/ftServer BIOS updates are image files that you must transfer from removable media or download from a network-accessible archive. Take care when updating firmware. It is a necessary failover characteristic for the CPU-I/O enclosures to be paired in duplexed operation.
Page 37 To determine what model your system is, type the ftsmaint lsSystem command. The model is identified in the Description field. 5. Obtain the latest BIOS image for the Express5800/ftServer and copy it to the ftServer tmp folder. Updating ftServer System Firmware...
Page 38 Express5800/ftServer: System Administrator’s Guide for the Linux Operating System...
Page 39: Updating Bmc Firmware
11. If you now need to update the Linux operating system and Express Builder, place the Express Builder CD in the upper CD-ROM drive and reboot. See the Release Notes: Express5800/ftServer for the Linux Operating System and Chapter 2 operating system update procedures.
Page 40 Updating BMC Firmware 4. Obtain the latest BMC image for the Express5800/ftServer and copy it to the ftServer tmp folder. N O T E All ftServers running a supported Linux distribution and Express5800/ftServer system software for the Linux Operating System (Express Builder) use the same BMC firmware.
Page 41: Updating The Operating System And Express5800/Ftserver System Software
Operating System and Express5800/ftServer System Software This chapter documents how to upgrade the Linux operating system and the Express5800/ftServer System Software for the Linux Operating System (Express Builder). It discusses the following topics: ‘‘General Upgrade Considerations” ‘‘Upgrading or Restoring the Linux Operating System”...
Page 42: General Upgrade Considerations
4-3. Before upgrading the operating system software, check with the NEC Corporation of America Customer Support Center or your authorized NEC service representative to ensure that your ftServer system supports the new version. Upgrade the Express Builder, as described in ‘‘Upgrading or Restoring Express Builder’’on page...
Page 43: Upgrading Or Restoring The Linux Operating System
Before performing an upgrade to a system in use, perform a complete file system backup. Carefully read the current Release Notes: Express5800/ftServer for the Linux Operating System document at http://support.necam.com for this release. Distribution Release Notes may have been updated with information about restrictions or problems and workarounds, software updates, and document corrections not found in the Release Notes from earlier distribution CDs.
Page 44: Express5800/Ftserver Kernel Modules
These modules must be present for fault-tolerant operation. The following requirements must be met, to ensure that these modules will be rebuilt. Express5800/ftServer kernel modules are only built for SMP kernels. Make sure that you only use SMP kernels. The kernel-smp-devel package must be installed. The version of this package must match the version of the kernel-smp in use.
Page 45: Restoring The Linux Operating System
‘‘Creating a Backup System Disk’’ on page 4-7 for details. 2. Shut down the ftServer system with the command: # halt -p 3. See the User Guide (Setup) to ensure that your system is configured for reinstallation. Updating the Operating System and Express5800/ftServer System Software...
Page 46: Upgrading Or Restoring Express Builder
To ensure that Express Builder is performing correctly, you should either perform a complete Express Builder reinstallation or restore the system from backups. Carefully read the current Release Notes: Express5800/ftServer for the Linux Operating System document on http://support.necam.com. Distribution...
Page 47: Creating A Backup System Disk
4. After the system has booted, insert a spare disk in the bottom slot of the CPU-I/O enclosure whose power switch is not lit. 5. Perform the procedures described in ‘‘Manually Creating Partitions on Blank Disks and Adding to RAID-1 Arrays’’ on page 5-20. Updating the Operating System and Express5800/ftServer System Software...
Page 48: Recovering From A Failed Software Upgrade
See Chapter 3 for details. The system is now restored to the pre-upgrade state. Related Information and Resources Release Notes: Express5800/ftServer for the Linux Operating System Express5800/ftServer: System Administrator’s Guide for the Linux Operating System...
Page 49: Setting Up The Ftserver System
Often, the device is recognized and automatically supported, requiring no direct configuration. While the operating system may recognize legacy devices, Express5800/ftServer System Software for the Linux Operating System (Express Builder) does not support them as fault-tolerant devices.
Page 50: Setting Up Internal Disk Storage
The console messages are also in the system log (/var/log/messages). Tailing the messages file while configuring disks is very helpful. # tail -f /var/log/messages Express5800/ftServer: System Administrator’s Guide for the Linux Operating System...
Page 51: Configuring Internal Disks
Setting Up Internal Disk Storage Since some disk-configuration operations produce considerable console output, it can be helpful to log on to another session. Configuring Internal Disks The six internal storage disks are persistently named based on the slot that they occupy.
Page 52 5-20). Enter the q command to quit, or continue with other commands, as required. The following example creates a new partition table and adds a primary partition, sdb1, of type 0xfd on sdb. Express5800/ftServer: System Administrator’s Guide for the Linux Operating System...
Page 53 Setting Up Internal Disk Storage To create a new partition table and add a partition 1. If fdisk is not already running, enter the fdisk command. # fdisk /dev/sdb The number of cylinders for this disk is set to 17849. There is nothing wrong with that, but this is larger than 1024, and could in certain setups cause problems with: 1) software that runs at boot time (e.g., old versions of...
Page 54 Changed system type of partition 1 to fd (Linux RAID autodetect) Command (m for help): 10. Enter the w command to write the partition table to the disk and exit fdisk. Command (m for help): w Express5800/ftServer: System Administrator’s Guide for the Linux Operating System...
Page 55: Default Internal Disk Configuration For A Newly Installed System
Setting Up Internal Disk Storage Default Internal Disk Configuration for a Newly Installed System The Linux operating system is installed on the sda/sdd pair of SAS (SATA) disks. See User Guide (Setup) for configuration of internal disk. N O T E The RAID array is not deterministic.
Page 56: Storage Device Definition
RAID-1 devices, since the underlying devices must be fault tolerant. Each RAID array has a number (for example, /dev/md23) that must be unique among the running RAID arrays. The RAID array numbers are in the range 0 through 128. Express5800/ftServer: System Administrator’s Guide for the Linux Operating System...
Page 57: Creating A Raid-1 Array
Setting Up RAID Arrays Device files are created for the first 128 RAID arrays. Use the mknod command (see mknod(1)) to create additional device files as needed. The number is the minor device number, and it is also used in the name. The smaller numbers are used by the installer, so it is convenient to add new RAID arrays above 10.
Page 58 Although /proc/mdstat reports a resynchronization in progress, none is occurring and no disk I/O is involved. In this case, ignore the resynchronization information in /proc/mdstat. 5-10 Express5800/ftServer: System Administrator’s Guide for the Linux Operating System...
Page 59: Creating A Raid-0 Array
Setting Up RAID Arrays When the command completes, the RAID array is up and running. You can use the mdadm command to see the status of the new RAID array: # mdadm -Q --detail /dev/md20 /dev/md20: Version : 00.90.01 Creation Time : Wed Sep 28 15:20:08 2005 Raid Level : raid1 Array Size : 143371968 (136.73 GiB 146.81 GB) Device Size : 143371968 (136.73 GiB 146.81 GB)
Page 60 Working Devices : 2 Failed Devices : 0 Spare Devices : 0 Chunk Size : 64K Number Major Minor RaidDevice State active sync /dev/md20 active sync /dev/md21 UUID : f5762850:f7dd0c84:5c720b6b:b328ca20 Events : 0.1 5-12 Express5800/ftServer: System Administrator’s Guide for the Linux Operating System...
Page 61: Creating And Mounting A File System
Setting Up RAID Arrays To stop the device, use the mdadm command with the -S argument, as follows: mdadm -S /dev/md30 Creating and Mounting a File System The RAID arrays created in the preceding examples are raw disk block devices. You can mount a file system on the RAID array.
Page 62: Removing And Replacing Disks
For information about the recommended partnering confirmation for internal disks, see ‘‘Configuring Internal Disks’’ on page 5-3. This section discusses the following topics: ‘‘Disk Insertion” ‘‘Administering RAID Arrays” 5-14 Express5800/ftServer: System Administrator’s Guide for the Linux Operating System...
Page 63: Disk Insertion
Administering RAID Arrays Disk Insertion When you reinsert a pulled disk, the OSM storage plugin attempts to match it with an existing disk. If it finds a match, it hot-adds the mirror partitions on the inserted disk ‘‘Resynchronization’’ back into the existing RAID arrays and resynchronizes them (see on page 5-18).
Page 64: Errors And Faulty Mirrors
You cannot remove a mirror that is not faulty. Before a disk is pulled, all of the mirrors on it must be marked faulty (either by the operating system or with the mdadm -f command) and removed with the mdadm -r command before the system can 5-16 Express5800/ftServer: System Administrator’s Guide for the Linux Operating System...
Page 65: Resynchronization
Administering RAID Arrays completely remove the disk (the OSM storage plugin automates these tasks). This means that until all mirrors are removed, a replacement disk inserted in the same slot will not spin up. You can use the mdadm command to add a mirror into a running RAID array. The following example shows how to do this.
Page 66: Replacing A Failed Disk
The failed disk must belong to a RAID 1 on top of a disk, partition, or multipath. If the failed disk belongs to a RAID0 (even if that RAID0 is part of a RAID1), the blank disk will not be added to the RAID array. 5-18 Express5800/ftServer: System Administrator’s Guide for the Linux Operating System...
Page 67: Configuring Safe Mode
Administering RAID Arrays N O T E If the running member of the RAID array was a system disk, the bootloader (grub) is added to the newly-inserted disk. To replace a failed disk 1. While the system and RAID array are running, remove the failed disk. 2.
Page 68: Replacing Defective Disks Interactively
‘‘Removing a Faulty Mirror’’ on page 5-17. 2. Physically remove the disk. 3. Insert a spare disk in the slot previously occupied by the defective disk. The drive spins up automatically. 5-20 Express5800/ftServer: System Administrator’s Guide for the Linux Operating System...
Page 69 Administering RAID Arrays To verify that the spare disk is not in use Type the following commands and check the resulting output: # mdadm --detail --scan # swapon -s # cat /etc/mtab To zero the spare disk Perform one of the following procedures: Zero the spare disk’s RAID superblocks by typing a command such as the following for each partition on the spare disk (substitute the device node of the partition you wish to zero for sdb1 in this example):...
Page 70 1. Type the following command to determine which RAID-1 arrays the running disk belongs to: # mdadm --detail --scan ARRAY /dev/md2 level=raid1 num-devices=2 UUID=5ddb14c7:d5e0b2d6:ad80086d:8db2a245 devices=/dev/sda2 ARRAY /dev/md1 level=raid1 num-devices=2 UUID=3838df6e:60caf7e6:695d0f62:de94e821 devices=/dev/sda3 ARRAY /dev/md0 level=raid1 num-devices=2 UUID=3e4ad330:c8ee5dfc:f48bd88a:401ada25 devices=/dev/sda1 5-22 Express5800/ftServer: System Administrator’s Guide for the Linux Operating System...
Page 71: Example 5-4. Running Grub
Administering RAID Arrays 2. Add each partition on the spare disk to the RAID-1 array containing the corresponding partition on the running disk with commands like the following: # mdadm -a /dev/md0 /dev/sdd1 mdadm: hot added /dev/sdd1 # mdadm -a /dev/md1 /dev/sdd3 mdadm: hot added /dev/sdd3 # mdadm -a /dev/md2 /dev/sdd2 mdadm: hot added /dev/sdd2...
Page 72: Example 5-5. Pairing A Spare Internal Disk With The Running System Disk
Source disk partition 3 belongs to RAID 1 /dev/md1. Adding blank disk partition 3 to RAID 1 /dev/md1. mdadm: hot added /dev/sdd3 Waiting for resync to complete before grubbing /dev/sdd1. Grubbing /dev/sdd1 5-24 Express5800/ftServer: System Administrator’s Guide for the Linux Operating System...
Page 73: System Backup And Disaster Recovery
System Backup and Disaster Recovery System Backup and Disaster Recovery Your ftServer system provides many safeguards against losing data due to hardware failures. However, it cannot cover all contingencies, so it is still important to perform regular backups and enact a good disaster-recovery program. Ethernet Devices Network interface naming on ftServer systems running a supported Linux distribution together with Express Builder is different from that on other Linux systems.
Page 74: Table 5-2. Ethernet Devices In Ftserver Cpu-I/O Enclosures
CPU-1, I/O-11, PCI slot 10, eth080219 port 1 Ethernet PCI adapter CPU-1, I/O-11, PCI slot 11, eth080220 port 0 Ethernet PCI adapter CPU-1, I/O-11, PCI slot 11, eth080221 port 1 5-26 Express5800/ftServer: System Administrator’s Guide for the Linux Operating System...
Page 75: Monitoring And Configuring Channel-Bonding Interfaces
Ethernet Devices Monitoring and Configuring Channel-Bonding Interfaces By default, the physical Ethernet interfaces listed in Table 5-2 are bound together into two channel-bonding interfaces, called bond0 and bond1. The two channel-bonding interfaces are set to operate in active-backup mode (mode 1) with Dynamic Host Configuration Protocol (DHCP) enabled.
Page 76: Configuring Channel-Bonding Interfaces
(mode 1, active-backup mode), modify the options line in the /etc/modprob.d/ft-network.conf file so that mode=x, where x is the desired mode of operation. To activate configuration-file modifications, perform the preceding procedure. 5-28 Express5800/ftServer: System Administrator’s Guide for the Linux Operating System...
Page 77: Determining Interface Device Names
Ethernet Devices N O T E S 1. There must be at least one alias for an active bond in the /etc/modprobe.d/ft-network.conf file, or bonding cannot occur. 2. The /etc/modprobe.d directory should contain no more than one ft-network.conf file. Determining Interface Device Names When you add a PCI Ethernet adapter to a system, you must determine the device names of the physical interfaces on the adapter before you can configure it.
Page 78: Mac Addresses
Configure ftlSNMP to allow remote management of your ftServer system. See Chapter 8 for instructions. Disable hyperthreading. Information about video display settings is also included. 5-30 Express5800/ftServer: System Administrator’s Guide for the Linux Operating System...
Page 79: Disabling Hyperthreading
To disable hyperthreading, you enter the ftServer Setup utility. To disable hyperthreading 1. Turn on or restart your system. When the Express5800/ftServer logo screen appears, press F2 to enter your system’s BIOS setup utility. The BIOS setup utility’s Main menu appears after the system completes more of the POST (power-on self-test) process.
Page 80: Configuring The System Video Display
The following message does not indicate a problem with the system. The clock will be properly reset and you can safely ignore the message. Losing some ticks... checking if CPU frequency changed 5-32 Express5800/ftServer: System Administrator’s Guide for the Linux Operating System...
Page 81: Additional Documentation And Resources
Additional Documentation and Resources Additional Documentation and Resources Linux System Administrator’s Guide v0.8, Linux Documentation Project: http://www.ibiblio.org/pub/Linux/docs/linux-doc-project/system-admin-guide/ http://unthought.net/Software-RAID.HOWTO/ Managing RAID on Linux, Derek Vadala, O’Reilly & Associates, 2003: http://www.oreilly.com/catalog/mraidlinux/ Setting Up the ftServer System 5-33...
Page 82 Additional Documentation and Resources 5-34 Express5800/ftServer: System Administrator’s Guide for the Linux Operating System...
Page 83: Managing Data Storage Devices
Chapter 6 Managing Data Storage Devices This chapter discusses the following topics: ‘‘CD-ROM Drives” ‘‘USB Storage Devices” ‘‘Additional Resources” Chapter 5 explains basic storage device definition and the configuration and management of the internal disk drives embedded in CPU-I/O enclosures. This chapter briefly discusses other data storage devices that are included with or can be optionally attached to the system.
Page 84 You can also translate the name assigned by the udev command into the internal name. For example: # ls -l /dev/sd*usb brw-rw---- 1 root disk 8, 64 Oct 24 16:18 /dev/sd1usb Express5800/ftServer: System Administrator’s Guide for the Linux Operating System...
Page 85 USB Storage Devices Once you have the name assigned by the udev command (in this case, sd1usb), you can use udevinfo to find the internal name (in this case, sde): # udevinfo -q path -n /dev/sd1usb /block/sde For more information about the udevinfo command, see udevinfo(8). C A U T I O N C A U T I O N Before unplugging the device, make sure that it is not...
Page 86: Usb Floppy Drives
The following is an example of the /proc/scsi/scsi display for a solid-state device. Host: scsi5 Channel: 00 Id: 00 Lun: 00 Vendor: LEXAR Model: JUMPDRIVE SECURE Rev: 3000 Type: Direct-Access ANSI SCSI revision: 02 Express5800/ftServer: System Administrator’s Guide for the Linux Operating System...
Page 87: Additional Resources
Additional Resources The system log provides details about the device, including its size: scsi5 : SCSI emulation for USB Mass Storage devices Vendor: LEXAR Model: JUMPDRIVE SECURE Rev: 3000 Type: Direct-Access ANSI SCSI revision: 02 SCSI device sdaz: 506880 512-byte hdwr sectors (260 MB) Additional Resources Linux Allocated Devices, LANANA: http://www.lanana.org/docs/device-list/devices.txt...
Page 88 Additional Resources Express5800/ftServer: System Administrator’s Guide for the Linux Operating System...
Page 89: Using Ftserver Fault-Tolerant Utilities And Software
Express Service Network, that enables your ftServer system to interact with the Express Service Network. When you configure the Express Service Network, the NEC Corporation of America Customer Support Center or your authorized NEC service representative can receive alarm notifications when faults or other significant events occur on your system, and can remotely diagnose problems.
Page 90 This command removes from service the CPU element, I/O element, or CPU-I/O enclosure slot specified by path. No other devices are supported. When you bring down a device, the effect on the system is the same as physically removing CPU-0, I/O-10. Express5800/ftServer: System Administrator’s Guide for the Linux Operating System...
Page 91 The ftsmaint Command N O T E The ftsmaint bringDown command will not permit you to bring down a simplex device, because this would disable the system. ftsmaint bringUp path This command brings into service the CPU element, I/O element, or CPU-I/O enclosure slot specified by path.
Page 92 The th_name argument can take one of the following values: uf (upper fatal) uc (upper critical) unc (upper noncritical) lf (lower fatal) lc (lower critical) lnc (lower noncritical) Express5800/ftServer: System Administrator’s Guide for the Linux Operating System...
Page 93: Device Path Enumeration
The ftsmaint Command The opstates for the sensors are as follows: FATAL: above uf or below lf CRITICAL: above uc or below lc WARNING: above unc or below unc NORMAL: default ftsmaint -version This command returns the build number of the ftsmaint command on your system.
Page 94 PCI slots 9, 10, 11 10/9—10/11 Storage enclosure in top I/O element 10/40 Internal disk slot 1 (maps to sda) 10/40/1 Internal disk slot 2 (sdb) 10/40/2 Internal disk slot 3 (sdc) 10/40/3 10/120 Express5800/ftServer: System Administrator’s Guide for the Linux Operating System...
Page 95 The ftsmaint Command Table 7-1. Device Paths of ftServer Devices (Page 3 of 3) Location Device Path Bottom I/O Fan speed sensor 10/140 element Voltage sensors 10/150—10/162 Bottom I/O enclosure Mass storage controller 11/0 —EIDE controller —7c:00.0 SAS (SATA) controller 11/1 —SAS (SATA) controller —7c:01.0...
Page 96: Figure 7-1. Ftserver Enclosures: Locations Of Major Enumerated Devices
Internal disk drive 2, sdb 10/40/3 Internal disk drive 3, sdc CPU-1, I/O-11 11/40/1 Internal disk drive 1, sdd 11/40/2 Internal disk drive 2, sde 11/40/3 Internal disk drive 3, sdf Express5800/ftServer: System Administrator’s Guide for the Linux Operating System...
Page 97: Figure 7-2. Ftserver Enclosures: Locations Of Major Enumerated Devices
The ftsmaint Command Figure 7-2. ftServer Enclosures: Locations of Major Enumerated Devices (Rear View) asys077a Callout Device ID Component 10/9 Slot 1, low profile (PCI Slot - 9) 10/10 Slot 2, full height (PCI Slot - 10) 10/11 Slot 3, full height (PCI Slot - 11) 11/9 Slot 1, low profile (PCI Slot - 9) 11/10...
Page 98: Ftsmaint Examples
1GB DDR-2 DIMM ONLINE ONLINE MISSING EMPTY MISSING EMPTY MISSING EMPTY MISSING EMPTY MISSING EMPTY MISSING EMPTY 1/20 15 4 1 ONLINE ONLINE 1/20/130 Internal Temp NORMAL 1/20/150 +12V NORMAL 7-10 Express5800/ftServer: System Administrator’s Guide for the Linux Operating System...
Page 99 The ftsmaint Command 1/23 0 0 0 ONLINE ONLINE 1/23/130 Internal Temp NORMAL 1/23/150 +12V NORMAL 1/130 Ambient Air Temp NORMAL 1/140 Fan1 NORMAL 1/141 Fan2 NORMAL 1/150 +1.2V VTT NORMAL 1/151 +1.8V VDD NORMAL 1/152 +12V NORMAL AA-G90730 Combined CPU/IO ONLINE DUPLEX 10/0...
Page 100: Bringing System Components Down And Up
Bringing System Components Down and Up You can use the ftsmaint command to bring down and restart a fault-tolerant subsystem. After bringing up a system, it attempts to synchronize and duplex the corresponding components automatically. 7-12 Express5800/ftServer: System Administrator’s Guide for the Linux Operating System...
Page 101: Removing A Pci Adapter From Service And Bringing It Into Service
You must send the dump file to theNEC Corporation of America Customer Support Center or your authorized NEC service representative for analysis. Using ftServer Fault-Tolerant Utilities and Software...
Page 102 Kernel Memory Dump File Management It is important that you monitor and maintain the size of the /var/crash directory. Back up old crash dump data before deleting it. Express5800/320Ma: System Administrator’s Guide for the Linux Operating System (NR003L) 7-14...
Page 103: Simple Network Management Using Net-Snmp And Ftlsnmp
When installing the Express Builder, you have the option of installing ftlSNMP. If you chose not to install ftlSNMP at that time, you can install it later by rerunning the Express5800/ftServer System Software for the Linux Operating System (Express Builder) installation program and selecting to install ftlSNMP. Installing ftlSNMP this way will not reinstall packages already installed on the system, and therefore not affect unrelated configurations.
Page 104: Ftlsnmp Inventory
– Various startup, restart, and shutdown scripts – Man pages The ftlSNMP package is currently built against a particular Net-SNMP version. Review the Release Notes: Express5800/ftServer for the Linux Operating System for compatibility information. During most Express Builder upgrades, ftlSNMP is also upgraded. Install ftlSNMP upgrades with the provided installer or upgrade script.
Page 105: Manually Installing And Upgrading The Ftlsnmp Rpm
Installing and Configuring ftlSNMP The ftlSNMP package is preinstalled with the default Express Builder installation, and only requires configuration and deployment. Files in the ftlSNMP package are located in the following directories: /etc/opt/ft/snmp—Contains the fault-tolerant subagent configuration templates and the Net-SNMP master agent configuration template. /etc/opt/ft/snmp/scripts—Contains the start, stop, and restart scripts.
Page 106: Ftlsnmp Prerequisites
Use the information in the template files (for example, /etc/opt/ft/snmp/snmpd.conf.template) as a guide when editing the files. However, values of parameters to be set in these files are system-, network-, and SNMP-manager specific. Express5800/ftServer: System Administrator’s Guide for the Linux Operating System...
Page 107: The Snmpd.conf File
Installing and Configuring ftlSNMP The snmpd.conf File C A U T I O N C A U T I O N Use SNMPv3 when the manager and master agent are separated on a public network. The following is an example only. Failure to use SNMPv3 when communicating over a public network is a server and network security risk.
Page 108: Configuring Snmp To Start At System Initialization
Uncomment the right lines, then run the commands. Uncomment these lines in /etc/opt/ft/snmp/snmpd.conf: createUser admin MD5 your_passwd DES rwuser v3user group v3usergroup admin group v3usergroup v3user view v3view included .1.3.6.1 access v3usergroup "" authNoPriv exact v3view v3view v3view Express5800/ftServer: System Administrator’s Guide for the Linux Operating System...
Page 109 Installing and Configuring ftlSNMP Run the following commands each time SNMP is restarted (or write a script to manage this task): # snmpusm -v3 -u admin -n "" -l authNoPriv -a MD5 -A your_passwd localhost create v3user admin # snmpusm -v3 -u v3user -n "" -l authNoPriv -a MD5 -A your_passwd localhost passwd old_passwd new_passwd These commands clone an initial (template) SNMPv3 user, admin, as v3user,...
Page 110: Snmp Foundations And Concepts
There are few network administration tools available that readily support fault-tolerant capabilities of networked systems and devices. ftlSNMP allows Express5800/ftServer systems to be monitored and managed by any remote- networked system running SNMP-based network management software. Express5800/ftServer: System Administrator’s Guide for the Linux Operating System...
Page 111: Ftlsnmp Management Commands
The following commands are also available to deal with special situations. However, you should not normally use them except under the guidance of the NEC Corporation of America Customer Support Center or your authorized NEC service representative, as starting and stopping agents in untested order can have unforeseen consequences.
Page 112: The Basic Net-Snmp Commands
– The sum of received packets on interfaces (ifInUCastPkts.* + ifInNUCastPkts.*) – The sum of transmitted interface packets (ifOutUCastPkts.* + ifOutNUCastPkts.*) – The number of IP input packets (ipInReceives.0) – The number of IP output packets (ipOutRequests.0) 8-10 Express5800/ftServer: System Administrator’s Guide for the Linux Operating System...
Page 113: Mibs
SNMP Foundations and Concepts snmptranslate—This command converts object ID values into more easily understood forms. See snmptranslate(1). snmptable—This command repeatedly uses SNMP GETNEXT or GETBULK requests to get information on a network entity, which is specified as, and must be mapped by, a table.
Page 114: Some Objects Defined By Standard Mibs
SNMP agent or a subagent executes according to MIB definitions. Some Objects Defined by Standard MIBs For a practical implementation of SNMP, a number of objects simply must be defined. Some of these are introduced here. 8-12 Express5800/ftServer: System Administrator’s Guide for the Linux Operating System...
Page 115 SNMP Foundations and Concepts For UDP or TCP/IP communications and collection of statistical data about communications and communications channels, MIB-II defines some necessary objects. MIB-II defines these objects for querying: system interfaces icmp snmp The Net-SNMP implementation requires basic support of the Host Resources MIB. The objects defined in RFC1514 Host Resources MIB include: hrSystem hrStorage...
Page 116: Snmpv3 Support
SNMP communicates with. SNMP refines SNMPv2 definitions and adds important security features. Net-SNMP supports SNMPv1, SNMPv2, and SNMPv3 protocols. Because of the simple basic structure of 8-14 Express5800/ftServer: System Administrator’s Guide for the Linux Operating System...
Page 117: Extensions And Fault-Tolerant Snmp Operation
The Net-SNMP and ftlSNMP packages encourage deployment of distributed SNMP services on heterogeneous networks featuring both ftServer systems running a supported Linux distribution together with Express Builder, and Express5800/ftServer hosts running other supported operating systems. The Net-SNMP and ftlSNMP packages interact with and manage networked objects defined in MIB files.
Page 118: Installing Remote Network Management Services
# service snmpd start # service snmptrapd start The host SNMP manager now can execute commands managing a network-accessible Express5800/ftServer system running the Linux operating system and the Net-SNMP and ftlSNMP packages. To receive traps, configure the /etc/opt/ft/snmp/snmpd.conf file on the ftServer system, adding trapsink entries pointing to the host server running snmptrapd.
Page 119: Configuring Snmp For Remote Service Management
Installing Remote Network Management Services Configuring SNMP for Remote Service Management The procedure for configuring Net-SNMP is very similar to ‘‘Configuring SNMP for Service Management’’ on page 8-134, which describes enabling remote services by adding SNMP users and groups. If you are using a network management station, you may have some other procedure provided with your software.
Page 120: Verifying Traps
‘‘Testing Ethernet Ports” N O T E The sample command lines in the remainder of this chapter are for general guidance only. Some of the command-line details and command output shown—for 8-18 Express5800/ftServer: System Administrator’s Guide for the Linux Operating System...
Page 121: Testing Your Snmp Configuration
To walk the SRA-ftLinux-MIB file: # snmpwalk -v 1 -c public -t 120 localhost 1.3.6.1.4.1.458 # snmpwalk -v 2c -c public localhost 1.3.6.1.4.1.458 To walk the Express5800/ftServer ftcPcidevcnf table: # snmpwalk -v 2c -c public localhost 1.3.6.1.4.1.458.107.1.2.5.2.1 To walk the UCDAVIS MIB: # snmpwalk -v 2c -c public localhost .1.3.6.1.4.1.2021.2...
Page 122: Managing Ftserver Hardware Components
# snmpset -v 3 -t 40 -l authNoPriv -u v3user -A new_passwd localhost 1.3.6.1.4.1.458.107.1.2.1.3.3.1.14.1 s test To bring up an I/O element # snmpset -v 3 -t 40 -l authNoPriv -u v3user -A new_passwd localhost 1.3.6.1.4.1.458.107.1.2.1.3.3.1.12.1 s test 8-20 Express5800/ftServer: System Administrator’s Guide for the Linux Operating System...
Page 123: Example: Managing Hardware
Managing SNMP To control firmware burn (FWBURN) # snmpset -v 3 -t 40 -l authNoPriv -u v3user -A new_passwd localhost 1.3.6.1.4.1.458.107.1.2.1.2.3.1.15.1 s FWBURN Example: Managing Hardware In this example, only relevant portions of the ftsmaint command output are shown. The following example illustrates bringing a CPU-I/O enclosure down and then back Issue the following command to check the status of CPU element 0, I/O element 10: # /opt/ft/bin/ftsmaint ls 0 H/W Path...
Page 124 After a while, it is fully back up again: # /opt/ft/bin/ftsmaint ls 0 H/W Path Description : Combined CPU/IO State : ONLINE Op State : DUPLEX Reason : PRIMARY LED State : GREEN 8-22 Express5800/ftServer: System Administrator’s Guide for the Linux Operating System...
Page 125: Testing Ethernet Ports
‘‘Verifying Traps’’ on page 8-146) and to run snmpwalk on the SRA-ftLinux-MIB file before and after a fault insertion to verify object data changes. A diff of these two walks will reveal changes that Express5800/ftServer MIB objects return. Example: Testing Ethernet Ports The following example demonstrates how to test Ethernet ports.
Page 126: Snmp And Mibs
SRA-ftLinux-MIB file and dump that data to a file. Pull the cable, then run snmpwalk again and dump it to another file. Finally, run diff on the two files to see all Express5800/ftServer objects that have changed because of the fault insertion. You may want to put these commands into a shell script for easier testing.
Page 127: Device Enumeration
SNMP and MIBS Device Enumeration Table 7-1 for information on the enumeration of hardware components for ftServer systems running a supported Linux distribution together with Express Builder. ftServer System Operation State Management Figure 8-2 illustrates the operational states and state changes in an ftServer system. Figure 8-2.
Page 128: Snmp Network Management Station Considerations
Configure the SNMP NMS to avoid verbose OID (object ID) printouts that may clutter the display. The minimum part of the OID needs to be displayed to provide the object’s unique name. 8-26 Express5800/ftServer: System Administrator’s Guide for the Linux Operating System...
Page 129: Initial Snmp Testing
Initial SNMP Testing N O T E S 1. Net-SNMP and ftlSNMP do not require the SNMP NMS, and the package does not provide one. Choice, installation, and configuration of the SNMP NMS is your responsibility. 2. The SRA-ftLinux-MIB file is only useful for managing ftServer LInux-based systems.
Page 130 CPU-I/O enclosure. This term is typically returned if a diagnostic test is in progress, without regard to whether the test will succeed or fail. DIAGNOSTICS is a transient state. 8-28 Express5800/ftServer: System Administrator’s Guide for the Linux Operating System...
Page 131: Initial Testing Of Ftlsubagent
Initial SNMP Testing Use the following command to bring the CPU-I/O enclosure up again: # /opt/ft/bin/ftsmaint bringUp 11 # /opt/ft/bin/ftsmaint bringUp 1 Initial Testing of ftlsubagent Use the snmpwalk tool to perform a get next operation on a system where an SNMP master agent is running.
Page 132: Opstate:state Definitions
Board firmware code is being updated. FIRMWARE_UPDATE_COMPLETE Board firmware code is updated. OFFLINE The unit has been brought down. STOPPED The driver has stopped the component; the component is no longer running. 8-30 Express5800/ftServer: System Administrator’s Guide for the Linux Operating System...
Page 133: Opstate:reason Definitions
Initial SNMP Testing Table 8-2. Operation State Values, Names, and Definitions (Page 2 of 2) Value Operation State (OpState) Definition ONLINE The unit can be communicated with. SIMPLEX A component is online and has no partner; it is not safe to remove this component. Applies to components that can be partnered.
Page 134: Get And Set Operations For Ftlsnmp Mib Objects
You can grep through the SRA-ftLinux-MIB.txt file for information about OID values and properties or open it with an editor or browser to view and search for information. The default installation places SRA-ftLinux-MIB at /opt/ft/mibs/SRA-ftLinux-MIB.txt. 8-32 Express5800/ftServer: System Administrator’s Guide for the Linux Operating System...
Page 135: Trap Filtering
Trap Filtering Trap Filtering This section discusses the following topics: ‘‘Trap-Filtering Capability” ‘‘Activating and Deactivating Trap Filtering” ‘‘Trap-Filtering Examples” Trap-Filtering Capability ftlSNMP provides the ability to filter out transitional traps. Traps are messages that inform you about network events. Hardware components that go in and out of service trigger a number of traps that are seen at the management client.
Page 136: Trap-Filtering Examples
RFC1213-MIB::sysUpTime.0 = Timeticks: (11929) 0:01:59.29 SNMPv2-MIB::snmpTrapOID.0 = OID: SRA-ftLinux-MIB::ftcTrapGenericInformationTrap.0 SRA-ftLinux-MIB::ftcTrapDevicePathID.0 = STRING: "10" SRA-ftLinux-MIB::ftcTrapAlertType.0 = STRING: "OPSTATE_CHANGE" SRA-ftLinux-MIB::ftcTrapGenName.0 = STRING: "SIMPLEX" SRA-ftLinux-MIB::ftcTrapGenDetailInfo.0 = STRING: "PRIMARY" SRA-ftLinux-MIB::ftcTrapGenAction.0 = STRING: "UNKNOWN" SRA-ftLinux-MIB::ftcTrapGenEventTimeStampWithOffsetFromUTC.0 = STRING: "20051206134939.616628-300" 8-34 Express5800/ftServer: System Administrator’s Guide for the Linux Operating System...
Page 137 Trap Filtering RFC1213-MIB::sysUpTime.0 = Timeticks: (12030) 0:02:00.30 SNMPv2-MIB::snmpTrapOID.0 = OID: SRA-ftLinux-MIB::ftcTrapGenericInformationTrap.0 SRA-ftLinux-MIB::ftcTrapDevicePathID.0 = STRING: "10 40 1" SRA-ftLinux-MIB::ftcTrapAlertType.0 = STRING: "OPSTATE_CHANGE" SRA-ftLinux-MIB::ftcTrapGenName.0 = STRING: "SIMPLEX" SRA-ftLinux-MIB::ftcTrapGenDetailInfo.0 = STRING: "NONE" SRA-ftLinux-MIB::ftcTrapGenAction.0 = STRING: "UNKNOWN" SRA-ftLinux-MIB::ftcTrapGenEventTimeStampWithOffsetFromUTC.0 = STRING: "20051206134940.622184-300" RFC1213-MIB::sysUpTime.0 = Timeticks: (12130) 0:02:01.30 SNMPv2-MIB::snmpTrapOID.0 = OID: SRA-ftLinux-MIB::ftcTrapGenericInformationTrap.0 SRA-ftLinux-MIB::ftcTrapDevicePathID.0 = STRING: "11 40 1"...
Page 138 RFC1213-MIB::sysUpTime.0 = Timeticks: (17244) 0:02:52.44 SNMPv2-MIB::snmpTrapOID.0 = OID: SRA-ftLinux-MIB::ftcTrapGenericInformationTrap.0 SRA-ftLinux-MIB::ftcTrapDevicePathID.0 = STRING: "11 5" SRA-ftLinux-MIB::ftcTrapAlertType.0 = STRING: "OPSTATE_CHANGE" SRA-ftLinux-MIB::ftcTrapGenName.0 = STRING: "OFFLINE" SRA-ftLinux-MIB::ftcTrapGenDetailInfo.0 = STRING: "PARENT_EMPTY" SRA-ftLinux-MIB::ftcTrapGenAction.0 = STRING: "UNKNOWN" 8-36 Express5800/ftServer: System Administrator’s Guide for the Linux Operating System...
Page 139 Trap Filtering SRA-ftLinux-MIB::ftcTrapGenEventTimeStampWithOffsetFromUTC.0 = STRING: "20051206135032.759280-300" RFC1213-MIB::sysUpTime.0 = Timeticks: (18744) 0:03:07.44 SNMPv2-MIB::snmpTrapOID.0 = OID: SRA-ftLinux-MIB::ftcTrapGenericInformationTrap.0 SRA-ftLinux-MIB::ftcTrapDevicePathID.0 = STRING: "11 6" SRA-ftLinux-MIB::ftcTrapAlertType.0 = STRING: "OPSTATE_CHANGE" SRA-ftLinux-MIB::ftcTrapGenName.0 = STRING: "OFFLINE" SRA-ftLinux-MIB::ftcTrapGenDetailInfo.0 = STRING: "PARENT_EMPTY" SRA-ftLinux-MIB::ftcTrapGenAction.0 = STRING: "UNKNOWN" SRA-ftLinux-MIB::ftcTrapGenEventTimeStampWithOffsetFromUTC.0 = STRING: "20051206135047.759920-300" RFC1213-MIB::sysUpTime.0 = Timeticks: (20244) 0:03:22.44 SNMPv2-MIB::snmpTrapOID.0 = OID: SRA-ftLinux-MIB::ftcTrapGenericInformationTrap.0...
Page 140: Example 8-2. Traps That Can Occur For I/O Element 11 When Trap Filtering Is On
SRA-ftLinux-MIB::ftcTrapGenAction.0 = STRING: "UNKNOWN" SRA-ftLinux-MIB::ftcTrapGenEventTimeStampWithOffsetFromUTC.0 = STRING: "20051206141314.504766-300" RFC1213-MIB::sysUpTime.0 = Timeticks: (5546) 0:00:55.46 SNMPv2-MIB::snmpTrapOID.0 = OID: SRA-ftLinux-MIB::ftcTrapGenericInformationTrap.0 SRA-ftLinux-MIB::ftcTrapDevicePathID.0 = STRING: "11" SRA-ftLinux-MIB::ftcTrapAlertType.0 = STRING: "OPSTATE_CHANGE" SRA-ftLinux-MIB::ftcTrapGenName.0 = STRING: "OFFLINE" SRA-ftLinux-MIB::ftcTrapGenDetailInfo.0 = STRING: "NONE" 8-38 Express5800/ftServer: System Administrator’s Guide for the Linux Operating System...
Page 141 Trap Filtering SRA-ftLinux-MIB::ftcTrapGenAction.0 = STRING: "UNKNOWN" SRA-ftLinux-MIB::ftcTrapGenEventTimeStampWithOffsetFromUTC.0 = STRING: "20051206141315.508290-300" RFC1213-MIB::sysUpTime.0 = Timeticks: (5746) 0:00:57.46 SNMPv2-MIB::snmpTrapOID.0 = OID: SRA-ftLinux-MIB::ftcTrapGenericInformationTrap.0 SRA-ftLinux-MIB::ftcTrapDevicePathID.0 = STRING: "10 40 1" SRA-ftLinux-MIB::ftcTrapAlertType.0 = STRING: "OPSTATE_CHANGE" SRA-ftLinux-MIB::ftcTrapGenName.0 = STRING: "SIMPLEX" SRA-ftLinux-MIB::ftcTrapGenDetailInfo.0 = STRING: "NONE" SRA-ftLinux-MIB::ftcTrapGenAction.0 = STRING: "UNKNOWN" SRA-ftLinux-MIB::ftcTrapGenEventTimeStampWithOffsetFromUTC.0 = STRING: "20051206141317.514636-300"...
Page 142: Example 8-3. Traps That Can Occur For When Trap Filtering Is Off
Example 8-3. Traps That Can Occur for When Trap Filtering Is Off RFC1213-MIB::sysUpTime.0 = Timeticks: (461810) 1:16:58.10 SNMPv2-MIB::snmpTrapOID.0 = OID: SRA-ftLinux-MIB::ftcTrapGenericInformationTrap.0 SRA-ftLinux-MIB::ftcTrapDevicePathID.0 = STRING: "2 "SRA-ftLinux-MIB::ftcTrapAlertType.0 = STRING: "OPSTATE_CHANGE "SRA-ftLinux-MIB::ftcTrapGenName.0 = STRING: "DIAGNOSTICS "SRA-ftLinux-MIB::ftcTrapGenDetailInfo.0 = STRING: "NONE 8-40 Express5800/ftServer: System Administrator’s Guide for the Linux Operating System...
Page 143: Example 8-4. Traps That Can Occur When Trap Filtering Is On
Trap Filtering "SRA-ftLinux-MIB::ftcTrapGenAction.0 = STRING: "UNKNOWN "SRA-ftLinux-MIB::ftcTrapGenEventTimeStampWithOffsetFromUTC.0 = STRING: "20051207143640.794126-300" RFC1213-MIB::sysUpTime.0 = Timeticks: (466169) 1:17:41.69 SNMPv2-MIB::snmpTrapOID.0 = OID: SRA-ftLinux-MIB::ftcTrapGenericInformationTrap.0 SRA-ftLinux-MIB::ftcTrapDevicePathID.0 = STRING: "2 "SRA-ftLinux-MIB::ftcTrapAlertType.0 = STRING: "OPSTATE_CHANGE "SRA-ftLinux-MIB::ftcTrapGenName.0 = STRING: "INITIALIZING "SRA-ftLinux-MIB::ftcTrapGenDetailInfo.0 = STRING: "NONE "SRA-ftLinux-MIB::ftcTrapGenAction.0 = STRING: "UNKNOWN "SRA-ftLinux-MIB::ftcTrapGenEventTimeStampWithOffsetFromUTC.0 = STRING: "20051207143724.381849-300"...
Page 144 RFC1213-MIB::sysUpTime.0 = Timeticks: (10511) 0:01:45.11 SNMPv2-MIB::snmpTrapOID.0 = OID: SRA-ftLinux-MIB::ftcTrapGenericInformationTrap.0 SRA-ftLinux-MIB::ftcTrapDevicePathID.0 = STRING: "2 "SRA-ftLinux-MIB::ftcTrapAlertType.0 = STRING: "OPSTATE_CHANGE "SRA-ftLinux-MIB::ftcTrapGenName.0 = STRING: "DUPLEX "SRA-ftLinux-MIB::ftcTrapGenDetailInfo.0 = STRING: "SECONDARY "SRA-ftLinux-MIB::ftcTrapGenAction.0 = STRING: "UNKNOWN "SRA-ftLinux-MIB::ftcTrapGenEventTimeStampWithOffsetFromUTC.0 = STRING: "20051207144109.557164-300" 8-42 Express5800/ftServer: System Administrator’s Guide for the Linux Operating System...
Page 145: Troubleshooting Ftserver Systems
This chapter provides information that will help you use available ftServer system and Linux operating system features to diagnose system problems. In many cases, you will be able to identify the source of the problem. If you cannot, contact the NEC Corporation of America Customer Support Center or your authorized NEC service representative.
Page 146: Normal Boot Sequence
Later in the boot sequence, /etc/rc.sysinit runs. It finds and starts any RAID arrays in /etc/mdadm.conf that were not already started and that are required by mounts in /etc/fstab. Express5800/ftServer: System Administrator’s Guide for the Linux Operating System...
Page 147: Possible Boot Problems
System Boot Problems N O T E If a RAID array fails to start, the boot stops and enters a debug shell. This is almost always because of a configuration error in /etc/fstab or /etc/mdadm.conf. Exiting the shell forces a reboot. Depending on your system’s RAID configuration, you may see one or more error messages similar to the following: md: could not bd_claim sdar1...
Page 148: Grub Problem
4. Shutdown the system and eject the CD. Incorrect GRUB parameters can also cause problems in booting. Do not change the parameters from the defaults set when the operating system was installed. Express5800/ftServer: System Administrator’s Guide for the Linux Operating System...
Page 149: Raid Problem
System Boot Problems C A U T I O N C A U T I O N In particular, specifying the GRUB noapic option can make the operating system unbootable. RAID Problem If a RAID-1 array has one type 0xfd (Linux RAID autodetect) mirror and one 0x83 (Linux) mirror, at boot, the RAID array is started in degraded mode using the type 0xfd mirror, and the type 0x83 mirror is not automatically added.
Page 150: System Log Messages
Mar 15 07:15:07 ftlx ifup: SIOCSIFADDR: No such device Mar 15 07:15:51 ftlx kernel: Keyboard timed out[1] kernel: keyboard timed out[1] Mar 15 07:15:52 ftlx kernel: keyboard: Timeout - AT keyboard not present? (f4) Express5800/ftServer: System Administrator’s Guide for the Linux Operating System...
Page 151 Index Index- restoration, 4-3 clock, 5-33 backing up a system, 4-7, 5-26 configuring creating disk, 4-7 DNS resolution, 5-32 BIOS Ethernet devices, 2-5 changing settings of Setup program, 9-5 ftlSNMP, 8-2 firmware, 2-7, 3-1 IP adress for bond interfaces, 5-32 updating, 3-1 Linux operating system, 1-3 BMC firmware, 2-7...
Page 152 5-1 documentation, 1-4 hardware, 1-1 firmware, 3-1 RAID disk arrays, 1-1, 5-9 system administration, 1-1 file systems troubleshooting, 1-3, 9-1 availability, 5-9 RAID, 5-9 files and upgrade procedure, 4-2 Express5800/ftServer: System Administrator’s Guide for the Linux Operating System Index-2...
Page 153 Index overview, 2-2 ftsmaint command, 7-1 pre-installation checklist, 2-7 acSwitch, 7-2 remote network management bringDown path, 7-2 services, 8-16 bringUp path, 7-3 burnProm fw_file path, 7-3 clearMtbf path, 7-3 dump path, 7-3 jumpswitch, 3-4 examples, 7-10 ls path, 7-2 lsLong, 7-2 kernel memory dump file management, 7-13 lsPeriph, 7-2 lsVND, 7-2...
Page 154 5-4 creating and mounting a file storage allocation, 5-8 system, 5-14 supported SCSI disks, 5-2 problems, 9-5 system-console messages, 5-2 RAID-0, 5-9 SCSI subsystem RAID-1, 5-9 errors, 5-17 Index-4 Express5800/ftServer: System Administrator’s Guide for the Linux Operating System...
Page 155 Index serial ports normal sequence, 9-2 data rate, 2-6 problems, 9-1, 9-3 flow control, 2-6 devices setting up the Linux operating system, 2-3 controlling, 7-12 shells initialization, 2-6 debug, 9-3 log messages, 9-6 GRUB, 2-6 pedestal and rack orientation, 2-4 simplex, 8-31 system clock, 5-33 LED indicator, 8-28...
Page 156 6-3 solid-state, 6-4 storage, 6-1 UTC. See Coordinated Universal Time version operating system identification, 2-4 visual diagnostics, 9-1 VND (Virtual Network Devices), 5-28 group configuration, 5-28 default, 5-28 Index-6 Express5800/ftServer: System Administrator’s Guide for the Linux Operating System...

NEC Express5800/ftServer Administrator's Manual

Preface

1 Introduction to Ftserver System Administration

2 Installing the Operating System and Express5800/Ftserver System Software

3 Updating Ftserver System Firmware

4 Updating the Operating System and Express5800/Ftserver System Software

5 Setting up the Ftserver System

6 Managing Data Storage Devices

7 Using Ftserver Fault-Tolerant Utilities and Software

8 Simple Network Management Using Net-SNMP and Ftlsnmp

9 Troubleshooting Ftserver Systems

Quick Links

Troubleshooting

Need help?

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for NEC Express5800/ftServer

Summary of Contents for NEC Express5800/ftServer

Table of Contents