Admon Home » dell http://www.admon.org Linux System Administration Wed, 08 Feb 2012 10:24:20 +0000 en hourly 1 http://wordpress.org/?v=3.3.1 About CPU: The logical and physical cores http://www.admon.org/about-cpu-the-logical-and-physical-cores/ http://www.admon.org/about-cpu-the-logical-and-physical-cores/#comments Mon, 31 May 2010 09:52:01 +0000 joseph http://planet.admon.org/?p=605 This post will demonstrate a detailed method of enumerating processors in a running linux server. Before delving into the topic, some terms should be defined:

  • Physical Package: The physical package is a microprocessor. For each physical package, it plugs into a physical socket on a mainboard, and may contain one or more processor cores.
  • Processor Core: The circuitry that provides ability to decode and execute instructions. A processor core may contain one or more logical processors.
  • Logical Processor: The basic unit of processor hardware that allows the software executive in the operating system to dispatch a task or execute a thread context. Each logical processor can execute only one thread context at a time.
  • Hyper-Threading: A feature within the IA-32 family of processors, where each processor core provides the functionality of more than one logical processor.
  • Multi-Core Processor: A physical package that contains more than one processor core.

(The above definitions come from Intel’s website, it would be decent to identify what we’re talking.)

As we know, on a running Linux/UNIX system, a detailed information of CPU can be retrieved from /proc/cpuinfo, but how can we identify the logical processors and the physical cores smartly?  Basically, there are two rules that will help you achieve these info.

1. Any CPU with the same “core id” are hyperthreads in the same processor core, which means this process core has Hyper-Threading enabled.
2. The “physical id” identifies physical package. Any cpu with the same physical id are threads or cores in the same physical socket.

Let me take Dell PowerEdge 2950 as an example, we’re running Red Hat Enterprise Linux AS release 4 Update 7 on this server.

$ cat /proc/cpuinfo
processor       : 0
vendor_id       : GenuineIntel
cpu family      : 6
model           : 23
model name      : Intel(R) Xeon(R) CPU           E5405  @ 2.00GHz
stepping        : 10
cpu MHz         : 1995.005
cache size      : 6144 KB
physical id     : 0
siblings        : 4
core id         : 0
cpu cores       : 4
fpu             : yes
fpu_exception   : yes
cpuid level     : 13
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall nx lm pni monitor ds_cpl tm2 cx16 xtpr lahf_lm
bogomips        : 3992.87
clflush size    : 64
cache_alignment : 64
address sizes   : 38 bits physical, 48 bits virtual
power management:                                                                   

processor       : 1
vendor_id       : GenuineIntel
cpu family      : 6
model           : 23
model name      : Intel(R) Xeon(R) CPU           E5405  @ 2.00GHz
stepping        : 10
cpu MHz         : 1995.005
cache size      : 6144 KB
physical id     : 1
siblings        : 4
core id         : 4
cpu cores       : 4
fpu             : yes
fpu_exception   : yes
cpuid level     : 13
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall nx lm pni monitor ds_cpl tm2 cx16 xtpr lahf_lm
bogomips        : 3990.03
clflush size    : 64
cache_alignment : 64
address sizes   : 38 bits physical, 48 bits virtual
power management:                                                                   

processor       : 2
vendor_id       : GenuineIntel
cpu family      : 6
model           : 23
model name      : Intel(R) Xeon(R) CPU           E5405  @ 2.00GHz
stepping        : 10
cpu MHz         : 1995.005
cache size      : 6144 KB
physical id     : 0
siblings        : 4
core id         : 2
cpu cores       : 4
fpu             : yes
fpu_exception   : yes
cpuid level     : 13
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall nx lm pni monitor ds_cpl tm2 cx16 xtpr lahf_lm
bogomips        : 3990.01
clflush size    : 64
cache_alignment : 64
address sizes   : 38 bits physical, 48 bits virtual
power management:                                                                   

processor       : 3
vendor_id       : GenuineIntel
cpu family      : 6
model           : 23
model name      : Intel(R) Xeon(R) CPU           E5405  @ 2.00GHz
stepping        : 10
cpu MHz         : 1995.005
cache size      : 6144 KB
physical id     : 1
siblings        : 4
core id         : 6
cpu cores       : 4
fpu             : yes
fpu_exception   : yes
cpuid level     : 13
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall nx lm pni monitor ds_cpl tm2 cx16 xtpr lahf_lm
bogomips        : 3990.03
clflush size    : 64
cache_alignment : 64
address sizes   : 38 bits physical, 48 bits virtual
power management:                                                                   

processor       : 4
vendor_id       : GenuineIntel
cpu family      : 6
model           : 23
model name      : Intel(R) Xeon(R) CPU           E5405  @ 2.00GHz
stepping        : 10
cpu MHz         : 1995.005
cache size      : 6144 KB
physical id     : 0
siblings        : 4
core id         : 1
cpu cores       : 4
fpu             : yes
fpu_exception   : yes
cpuid level     : 13
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall nx lm pni monitor ds_cpl tm2 cx16 xtpr lahf_lm
bogomips        : 3989.99
clflush size    : 64
cache_alignment : 64
address sizes   : 38 bits physical, 48 bits virtual
power management:                                                                   

processor       : 5
vendor_id       : GenuineIntel
cpu family      : 6
model           : 23
model name      : Intel(R) Xeon(R) CPU           E5405  @ 2.00GHz
stepping        : 10
cpu MHz         : 1995.005
cache size      : 6144 KB
physical id     : 1
siblings        : 4
core id         : 5
cpu cores       : 4
fpu             : yes
fpu_exception   : yes
cpuid level     : 13
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall nx lm pni monitor ds_cpl tm2 cx16 xtpr lahf_lm
bogomips        : 3990.02
clflush size    : 64
cache_alignment : 64
address sizes   : 38 bits physical, 48 bits virtual
power management:                                                                   

processor       : 6
vendor_id       : GenuineIntel
cpu family      : 6
model           : 23
model name      : Intel(R) Xeon(R) CPU           E5405  @ 2.00GHz
stepping        : 10
cpu MHz         : 1995.005
cache size      : 6144 KB
physical id     : 0
siblings        : 4
core id         : 3
cpu cores       : 4
fpu             : yes
fpu_exception   : yes
cpuid level     : 13
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall nx lm pni monitor ds_cpl tm2 cx16 xtpr lahf_lm
bogomips        : 3990.01
clflush size    : 64
cache_alignment : 64
address sizes   : 38 bits physical, 48 bits virtual
power management:                                                                   

processor       : 7
vendor_id       : GenuineIntel
cpu family      : 6
model           : 23
model name      : Intel(R) Xeon(R) CPU           E5405  @ 2.00GHz
stepping        : 10
cpu MHz         : 1995.005
cache size      : 6144 KB
physical id     : 1
siblings        : 4
core id         : 7
cpu cores       : 4
fpu             : yes
fpu_exception   : yes
cpuid level     : 13
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall nx lm pni monitor ds_cpl tm2 cx16 xtpr lahf_lm
bogomips        : 3990.03
clflush size    : 64
cache_alignment : 64
address sizes   : 38 bits physical, 48 bits virtual
power management:

From the outputs, we can see that, there’re 8 processor-cores in 2 physical packages (in other words, there’re two quad-cores CPU on this server), and none of them has Hyper-Threading enabled. Here’s a quick explanation for some keywords that listed above:

  • The processor entry contains a unique identifier for this logical processor.
  • The physical id entry contains a unique identifier for each physical package.
  • The core id entry holds a unique identifier for each core.
  • The siblings entry lists the number of logical processors that exist on the same physical package.
  • The cpu cores entry contains the number of cores that exist on the same physical package.
  • The vendor id entry holds the string. GenuineIntel if the processor is an Intel processor, and AuthenticAMD if it’s an AMD processor.

There are some commands here to help identify these type of information quickly on a running Linux:

  1. Total amount of processors including the logical ones: 
    # cat /proc/cpuinfo | grep "processor"| wc -l
  2. Total amount of CPU package: 
    # cat /proc/cpuinfo | grep "physical id" | sort | uniq | wc -l
  3. How many cores for each CPU. (Here we should call CPU as physical package as we mentioned above): 
    # cat /proc/cpuinfo | grep "cpu cores" | wc -l
  4. For each physical CPU, the amount of Logical CPU (the logical CPU can be physical cores, soft cores like threaded, or both). 
    # cat /proc/cpuinfo | grep "siblings"

Finally, please note that the msg from /proc/cpuinfo depends on your operating systems, which means it’s not always right or up-to-date. If you faced any issues, please create a thread at our support forum, thanks!

]]> http://www.admon.org/about-cpu-the-logical-and-physical-cores/feed/ 2 Install Dell OMSA on Redhat Enterprise Linux http://www.admon.org/install-dell-omsa-on-redhat-enterprise-linux-45/ http://www.admon.org/install-dell-omsa-on-redhat-enterprise-linux-45/#comments Thu, 19 Nov 2009 05:33:34 +0000 joseph http://planet.admon.org/?p=453 Dell LogoHere we listed 3 ways on the installation of Dell OpenManage Server Administrator on a Redhat Enterprise Linux, you can follows these steps on CentOS or SLES 10, they would work well.

1, Install from RPM packages
Generally we need these RPM packages, you can search and download them from Google.com.

[root@storage cax]# ls
srvadmin-cm-6.1.0-648.i386.rpm       srvadmin-omcommon-6.1.0-648.i386.rpm
srvadmin-deng-6.1.0-648.i386.rpm     srvadmin-omhip-6.1.0-648.i386.rpm
srvadmin-hapi-6.1.0-648.i386.rpm     srvadmin-omilcore-6.1.0-648.i386.rpm
srvadmin-isvc-6.1.0-648.i386.rpm     srvadmin-syscheck-6.1.0-648.i386.rpm
srvadmin-omacore-6.1.0-648.i386.rpm
srvadmin-cm-6.1.0-648.i386.rpm

These packages can be used on both RHEL-4 and RHEL-5. After the downloading, let’s start the installation:

[root@storage cax]# uname -a
Linux storage.admon 2.6.9-78.ELsmp #1 SMP Wed Jul 9 15:46:26 EDT 2008 x86_64 x86_64 x86_64 GNU/Linux
[root@storage cax]# rpm -ivh srv*.rpm
Preparing...                ########################################### [100%]
1:srvadmin-omilcore      ########################################### [ 11%]
To start all installed services without a reboot,
enter the following command:  srvadmin-services.sh  start
2:srvadmin-syscheck      ########################################### [ 22%]
3:srvadmin-deng          ########################################### [ 33%]
4:srvadmin-hapi          ########################################### [ 44%]
5:srvadmin-omcommon      ########################################### [ 56%]
6:srvadmin-omacore       ########################################### [ 67%]
7:srvadmin-isvc          ########################################### [ 78%]
8:srvadmin-cm            ########################################### [ 89%]
9:srvadmin-omhip         ########################################### [100%]
[root@storage cax]#

Now, it’s ready for use! enjoy!

The following two steps are from Dell’s official website, and it’s officially supported by Dell!

2, Setup for usage with yum

The minimum required yum is 2.4.x, and it’s tested on RHEL5, CentOS, Scientific Linux, RHEL4+yum, SLES+yum. The version of yum distributed on CentOS 3 by default is very old (yum 2.0.8), so you need to upgrade to a 2.4.x version in order to use these repositories. The older version of yum does not support plugins or mirrorlists, which are required for these repos to work.

Set up this repository, type:

[root@storage cax]# wget -q -O - http://linux.dell.com/repo/hardware/OMSA_6.1/bootstrap.cgi | bash

Optional Install OpenManage Server Administrator:

[root@storage cax]# yum install srvadmin-all

NOTE: OMSA will not install on unsupported systems. If you receive a message at install that the system is not supported, it is likely that your system is not supported, and the install will fail. This is most common on Dell SC-class systems, as OMSA is completely unsupported on these systems.

3, Set up for usage with up2date

Follow these instructions for use with up2date on RHEL4:

Set up this repository:

[root@storage cax]# wget -q -O - http://linux.dell.com/repo/hardware/OMSA_6.1/bootstrap.cgi | bash

Optional Install OpenManage Server Administrator:

[root@storage cax]# up2date -i srvadmin-all

NOTE: OMSA will not install on unsupported systems. If you receive a message at install that the system is not supported, it is likely that your system is not supported, and the install will fail. This is most common on SC-class systems, as OMSA is completely unsupported on these systems.

]]> http://www.admon.org/install-dell-omsa-on-redhat-enterprise-linux-45/feed/ 1 Using MegaCli set disk to HotSpare mode in linux http://www.admon.org/using-megacli-set-disk-to-hotspare-mode-in-linux/ http://www.admon.org/using-megacli-set-disk-to-hotspare-mode-in-linux/#comments Tue, 08 Sep 2009 07:54:17 +0000 joseph http://blog.admon.org/?p=44

When one of the disks failed in Dell MD1000, the hotspare disk will change its role into online mode, and you need to replace  the bad disk with a good one. So a question comes, how can I set the new disk into hotspare mode.

With the help of MegaCli, it’s quite easy, just a single command like this:

# MegaCli -PDHSP -set -PhysDrv[A:B] -aC

A:  it’s Enclosure Number

B: It’s Slot NUmber

C: It’s Array ID

Here is an example:

Find out the issued disk by this command:

# /usr/sbin/MegaCli -PDList -a1|grep "Firmware state: Unconfigured(good)" -B12

Enclosure Number: 1
Slot Number: 255
Device Id: 32
Sequence Number: 1
Media Error Count: 0
Other Error Count: 1
Predictive Failure Count: 0
Last Predictive Failure Event Seq Number: 0
Raw Size: 0MB [0x0 Sectors]
Non Coerced Size: 9007199254740480MB [0xfffffffffff00000 Sectors]
Coerced Size: 0MB [0x0 Sectors]
Firmware state: Unconfigured(good)
–

Enclosure Number: 2
Slot Number: 8
Device Id: 33
Sequence Number: 1
Media Error Count: 0
Other Error Count: 0
Predictive Failure Count: 0
Last Predictive Failure Event Seq Number: 0
Raw Size: 381469MB [0x2e90edd0 Sectors]
Non Coerced Size: 380957MB [0x2e80edd0 Sectors]
Coerced Size: 380928MB [0x2e800000 Sectors]
Firmware state: Unconfigured(good)

Here, “Slot Number: 255″ meas the entire disk cube, just simply pass it. so your command is something like this:

# /usr/sbin/MegaCli -PDHSP -set -PhysDrv[2:8] -a1

Set Physical Drive at EnclId-2 SlotId-4 as Hot Spare Success.

]]> http://www.admon.org/using-megacli-set-disk-to-hotspare-mode-in-linux/feed/ 2 Dell PE2950 LCD Message explained http://www.admon.org/dell-pe2950-lcd-message-explained/ http://www.admon.org/dell-pe2950-lcd-message-explained/#comments Sun, 12 Jul 2009 17:35:18 +0000 joseph http://planet.admon.org/?p=537 Dell PowerEdge 2950 control dashboard LCD provides status messages to signify when its physical system is operating well or when needs some attention. The LCD lights blue to indicate a normal operating condition, and lights amber to indicate an error condition.

The LCD scrolls a message that includes a status code followed by descriptive text. The following section lists the LCD status messages that can occur and the probable cause for each message. The LCD messages refer to events recorded in the System Event Log (SEL). For information on the SEL and configuring system management settings, see the systems management documentation.

NOTE: If your system fails to boot, press the System ID button for at least five seconds until an error code appears on the LCD. Record the code, then check it here or see Getting Help on Dell.com.

The following lines will should each error in a two-line mode, the first line indicates the appeared Error code and Text, and the second line is a case explaination.

N/A – SYSTEM NAME
Causes: A 62-character string that can be defined by the user in the System Setup program. The SYSTEM NAME displays under the following conditions:
* The system is powered on.
* The power is off and active POST errors are displayed.

E1000 – FAILSAFE, Call Support
Causes: SORRY

E1114 – Temp Ambient
Causes: Ambient system temperature is out of acceptable range.

E1116 – Temp Memory
Causes: Memory has exceeded acceptable temperature and has been disabled to prevent damage to the components.

E12nn – xx PwrGd
Causes: Specified voltage regulator has failed.

E1210 – CMOS Batt
Causes: CMOS battery is missing, or the voltage is out of acceptable range.

E1211 – ROMB Batt
Causes: RAID battery is either missing, bad, or unable to recharge due to thermal issues.

E1229 – CPU # VCORE
Causes: Processor # VCORE voltage regulator has failed.

E1310 – RPM Fan ##
Causes: RPM of specified cooling fan is out of acceptable operating range.

E1313 – Fan Redundancy
Causes: The system is no longer fan-redundant. Another fan failure will put the system at risk of over-heating.

E1410 – CPU # IERR
Causes: Specified microprocessor is reporting an internal error.

E1414 – CPU # Thermtrip
Causes: Specified microprocessor is out of acceptable temperature range and has halted operation.

E1418 – CPU # Presence
Causes: Specified processor is missing or bad, and the system is in an unsupported configuration.

E141C – CPU Mismatch
Causes: Processors are in a configuration unsupported by Dell.

E141F – CPU Protocol
Causes: The system BIOS has reported a processor protocol error.

E1420 – CPU Bus PERR
Causes: The system BIOS has reported a processor bus parity error.

E1421 – CPU Init
Causes: The system BIOS has reported a processor initialization error.

E1422 – CPU Machine Chk
Causes: The system BIOS has reported a machine check error.

E1610 – PS # Missing
Causes: No power is available from the specified power supply; specified power supply is improperly installed or faulty.

E1614 – PS # Status
Causes: No power is available from the specified power supply; specified power supply is improperly installed or faulty.

E1618 – PS # Predictive
Causes: Power supply voltage is out of acceptable range; specified power supply is improperly installed or faulty.

E161C – PS # Input Lost
Causes: Power source for specified power supply is unavailable, or out of acceptable range.

E1620 – PS # Input Range
Causes: Power source for specified power supply is unavailable, or out of acceptable range.

E1624 – PS Redundancy
Causes: The power supply subsystem is no longer redundant. If the last supply fails, the system will go down.

E1710 – I/O Channel Chk
Causes: The system BIOS has reported an I/O channel check.

E1711 – PCI PERR B## D## F## PCI PERR Slot #
Causes: The system BIOS has reported a PCI parity error on a component that resides in PCI configuration space at bus ##, device ##, function ##. The system BIOS has reported a PCI parity error on a component that resides in the specified PCI slot.

E1712 – PCI SERR B## D## F## PCI SERR Slot #
Causes: The system BIOS has reported a PCI system error on a component that resides in PCI configuration space at bus ##, device ##, function ##. The system BIOS has reported a PCI system error on a component that resides in the specified slot.

E1714 – Unknown Err
Causes: The system BIOS has determined that there has been an error in the system, but is unable to determine its origin.

E171F – PCIE Fatal Err B## D## F## PCIE Fatal Err Slot #
Causes: The system BIOS has reported a PCIe fatal error on a component that resides in PCI configuration space at bus ##, device ##, function ##.
The system BIOS has reported a PCIe fatal error on a component that resides in the specified slot.

E1810 – HDD ## Fault
Causes: The SAS subsystem has determined that hard drive ## has experienced a fault.

E1811 – HDD ## Rbld Abrt
Causes: The specified hard drive has experienced a rebuild abort.

E1812 – HDD ## Removed
Causes: The specified hard drive has been removed from the system.

E1913 – CPU & Firmware Mismatch
Causes: The BMC firmware does not support the CPU.

E1A11 – PCI Rsr Config
Causes: PCI risers are not configured correctly; some invalid configurations may prevent the system from powering on.

E1A12 – PCI Rsr Missing
Causes: One or all of the PCI risers is missing, preventing the system from powering on.

E1A14 – SAS Cable A
Causes: SAS cable A is missing or bad.

E1A15 – SAS Cable B
Causes: SAS cable B is missing or bad.

E2010 – No Memory
Causes: No memory is installed in the system.

E2011 – Mem Config Err
Causes: Memory detected, but is not configurable. Error detected during memory configuration.

E2012 – Unusable Memory
Causes: Memory is configured, but not usable. Memory subsystem failure.

E2013 – Shadow BIOS Fail
Causes: The system BIOS failed to copy its flash image into memory.

E2014 – CMOS Fail
Causes: CMOS failure. CMOS RAM not functioning properly.

E2015 – DMA Controller
Causes: DMA controller failure.

E2016 – Int Controller
Causes: Interrupt controller failure.

E2017 – Timer Fail
Causes: Timer refresh failure.

E2018 – Prog Timer
Causes: Programmable interval timer error.

E2019 – Parity Error
Causes: Parity error.

E201A – SIO Err
Causes: SIO failure.

E201B – Kybd Controller
Causes: Keyboard controller failure.

E201C – SMI Init
Causes: System management interrupt (SMI) initialization failure.

E201D – Shutdown Test
Causes: BIOS shutdown test failure.

E201E – POST Mem Test
Causes: BIOS POST memory test failure.

E201F – DRAC Config
Causes: Dell remote access controller (DRAC) configuration failure.

E2020 – CPU Config
Causes: CPU configuration failure.

E2021 – Memory Population
Causes: Incorrect memory configuration. Memory population order incorrect.

E2022 – POST Fail
Causes: General failure after video.

E2110 – MBE Crd # DIMM ## & ##
Causes: One of the DIMMs in the set implicated by “## & ##” has had a memory multi-bit error (MBE). If no memory card is present, the “Crd #” string is left out of the message.

E2111 – SBE Log Disable Crd # DIMM ##
Causes: The system BIOS has disabled memory single-bit error (SBE) logging, and will not resume logging further SBEs until the system is rebooted. “##” represents the DIMM implicated by the BIOS. If no memory riser card is present, the “Crd #” string is left out of the message.

E2112 – Mem Spare Crd # DIMM ##
Causes: The system BIOS has spared the memory because it has determined that the memory had too many errors. “## & ##” represents the DIMM pair implicated by the BIOS. If no memory card is present, the “Crd #” string is left out of the message.

E2113 – Mem Mirror Crd # DIMM ## & ##
Causes: The system BIOS has disabled memory mirroring because it has determined that one half of the mirror has had too many errors. “## & ##” represents the DIMM pair implicated by the BIOS. If no memory card is present, the “Crd #” string is left out of the message.

E2118 – Fatal NB Mem CRC
Causes: One of the connections in the Fully Buffered DIMM (FBD) memory subsystem link on the Northbound side has failed.

E2119 – Fatal SB Mem CRC
Causes: One of the connections in the FBD memory subsystem link on the Southbound side has failed.

I1910 – Intrusion
Causes: System cover has been removed.

I1911 – >3 ERRs Chk Log
Causes: LCD overflow message. A maximum of three error messages can display sequentially on the LCD. The fourth message displays as the standard overflow message.

I1912 – SEL Full
Causes: System Event Log is full of events, and is unable to log any more events.

W1228 – ROMB Batt < 24hr
Causes: Warns predictively that the RAID battery has less than 24 hours of charge left.

Please note that, more details are always available at Dell’s official support website. You can also submit a request for help at our hardware forum.

]]> http://www.admon.org/dell-pe2950-lcd-message-explained/feed/ 6