作者: ring, 于 May 10th,2011
现在宝宝已经两个月了，现在的他看见熟悉的图画或者玩具就会呵呵的笑了。看着他无邪的笑容，油然而生的不止是责任，还有感动。
他出生的那些情景慢慢的开始淡忘了，但偶尔会联想，这个小家伙就是从我肚子里面出来的，生命真是一个奇迹啊。
总想把宝宝出生的情况记录一下，就算是流水帐，以后等他长大了，可以看看也挺好的。从哪儿说起呢？就从他出生前一个星期吧！
2011年3月3号，也是老公的生日。
下午和妈出去买东西，站在水果摊边，肚子一阵抽痛。晚上九点多，肚子一阵一阵的抽痛，没有经验的我们以为要生了，拎着大包小包直奔医院。难道小家伙真的想在这天给他爸爸一个惊喜么？
经过一番检查，医生说“回去吧，明天也未必生的出来”。被浇了一盆冷水的我们悻悻的回家等待。晚上，疼的频率渐渐慢下来了，一夜睡的很好。
接下来的几天，几乎不痛了。小家伙，难道是和爸爸妈妈先开个玩笑？
等待的日子也并不好过，又担心又着急。
2011年3月7号，终于熬到了产检的日子，也是医生给我们算的预产期。
早早的去排B超，找专家加号，就诊，检查。临近中午在我的要求下顺利的开出了住院单（医院的床位相当的紧张啊，因查出我有预激综合症才给开的）。总算有点眉目了，结果没有床位，让回去等，意料之中，谁让我们要坚持在妇保生呢。
2011年3月8号
老公早早去排床位，结果可想而知，可能老天也眷顾我们的幸苦，终于让他等到了临时出院的床位，虽然是六人间，也已经很幸运了。在这里也特别感谢一下老公，从怀孕到孕检都是很幸苦。打车赶去医院办理入院手续，看到病房里一个个刚出生的小宝宝，渴望快点见到我的宝贝。接下来，听宣教、抽血、胎监。凭心而论，妇保的医护还是很负责任的，再三叮嘱我要小心，不行了请护工陪我（老公回家拿住院的东西了）。胎心监护做下来有一点点V型下降，医生说一般没有问题，再复查一下，确实没有问题。到底是大病房，晚上的时间很不好过，此起彼伏的宝宝哭声，陪护人员来回的走动声，其他病友的说话声，更要命的是一股股脚臭味…幸亏我住的还是临门口的床。
2011年3月9号
早上六点多，睡意朦胧的我，被护士忙碌的工作吵醒，查体温，听胎心，其他病友护理，房间消毒。八点多医生查房，因预激我要求剖腹产，医生给我检查了一下，说预激不能作为剖腹产的条件，而宫颈管才消退百分之三十也暂时没有临产征兆，在时间上比较尴尬，建议我出院待产。天啊，好不容易住进来，这一出院更麻烦啊。我又和医生说了胎监V型下降，她说，那做个B超查一下脐带绕颈情况。郁闷，宝宝，什么时候见到你啊，看不到头了。
B超情况还好，胎心监护做完，医生说我的宫缩很强烈，问我有没有肚子疼，我说没有，只是感觉肚子很紧，腰部有点困，医生让我回去注意，看宫缩的频率。回到病房，我吃了一大碗面后开始数时间，刚开始还五六分钟紧一次，慢慢的变成七八分钟，小家伙，一定又在骗人了，算了，还是睡觉吧。
2011年3月10号
凌晨两点多，被一阵一阵的腹痛疼醒了，不想再无端的惊动医生，自己拿着手表数时间，差不多两三分钟疼一次了，老公去找医生。医生给听了胎心，说再观察半个小时。半个小时了，频率好像稳定了，再去找医生，医生为我做了检查，说，你收拾一下东西，准备去生吧。啊？这就要生了？悄悄的问了句“医生，我能不能生出来啊？”医生笑了一下，说“你要有信心”。唉，当初一直抱着生不出来就剖的念头，所以后期也没有怎么锻炼，这下可由不得自己了。
赶快回病房拿东西，晕，床上的垫巾居然还没有买，无奈，老公厚着脸皮把对床阿姨叫醒，借了两个。一个护工过来接我，把我推到三楼分娩室，看着“分娩室”三个赫然大字，又害怕又紧张。。而“男士止步”四个大字更是让我有一个人作战的感觉，太不人性了～进入待产室，我望了望墙上的时钟，四点了。
待产室是一个大屋子，里面好多床。晕，居然有人在睡觉，不知道什么情况。一位医生把我安排在了8床，让我自己上去，摸不着头脑的我，只能接受命令一样服从。过了一会，旁边九床来了一位产友，疼的又是打滚又是哭叫的，最终以要打无痛分娩被带走。暗暗庆幸自己的忍耐力还可以。每当阵痛来临，我就抓着床围栏，咬着牙挺过去。突然想起巧克力可以增加能量，从包里拿出一块吃。渐渐的，阵痛加剧，开始忍不住的哼哼了，越来越强烈了，终于忍不住向医生咨询无痛分娩，医生说，就是像剖腹产一样打麻药，有一定风险，听到风险二字，我退缩了，为了我的宝宝，再忍忍吧。（唉，那种疼痛真是无法形容，以至于在产后几天里我一想起宫缩两个字就全身疼。）终于忍不住了，我大叫，医生，我受不了了，给我打一针无痛吧，医生为我做了检查，之后有一个医生过来接我，我跟着她走进了“分娩室”，里面两个产床，其中一个正在输液，还不时的和医生说，医生我又疼了，快给我再推点麻药吧，那医生让我自己爬上去，我战战兢兢的问“是不是给我打针呀？”。医生说“你宫口开了七八公分了，不需要打无痛了”。
产床上的时光真是难熬啊，疼痛越来越厉害。我不时的问医生，什么时候生，医生说，这要看你自己了。不时的听到隔壁屋子里传来一阵一阵的啼哭声，又担心又渴望这时间快点结束。感觉当一个助产士也挺好，迎接一个个新生命的到来多么美好的事情。由于最后阶段我不会使劲，一直折腾了半个多小时，终于，努力，感觉肚子一下轻松了不少。
听到宝宝的啼哭声，不禁露出微笑，我想所有母亲在那一刻都会忘记所有疼痛会心微笑，医生抱过来，让我看了宝宝的性别，我的儿子，终于见到你了，之后的缝针阶段，我几乎是在宝宝的鼓励下完成的。他就在离我一米左右的小床上，小胳膊小腿挥舞着，我对医生说，我想看看他，医生把他的头面向我，呵呵，小家伙居然也看着我，任何的疼痛都抵不上他那好奇的眼神，又过了一会，一位医生把他放到我的胸口，天啊，绵绵的小皮肤和我那么亲近，我的宝贝，就在我的怀里。
产后住院时光过得很快，虽然浑身疼，哪哪都不舒服，但可能处于兴奋状态的我就是不想休息，没事做的时候，我就仔细的端详着他，小鼻子像我，眉毛像他爸爸，小脸那么稚嫩，眼神那么清澈……
现在两个月了，我的身体渐渐恢复，但还是感觉到很多事情力不从心。宝宝很乖，很可爱。睡着的时候白白的小脸，有时候却努的通红，哭的时候总是先叫唤两声，没人理才开始哭，有时候哭到连续了，让人心疼。深深的感觉了，做父母的真的很不容易，在孩子面前，我们就是他的支柱，这是怎样的一种责任感。有时候我会突然的产生一种愧疚，不能给他创造更好的环境，很心疼，宝宝好像很懂事一样，用同学的话讲皮实，很感动。虽然物质上不能拥有很多，但我们的孩子一定会很快乐，因为爸爸妈妈都很爱你，我们要快快乐乐的幸福生活：）。
作者: David, 于 May 6th,2011
I did not read this,but i’d like to put it here in case i need it.
Help for ipmitool:
ipmitool -h
ipmitool version 1.8.10.3
usage: ipmitool [options...] <command>
-h This help
-V Show version information
-v Verbose (can use multiple times)
-c Display output in comma separated format
-d N Specify a /dev/ipmiN device to use (default=0)
-I intf Interface to use
-H hostname Remote host name for LAN interface
-p port Remote RMCP port [default=623]
-U username Remote session username
-f file Read remote session password from file
-S sdr Use local file for remote SDR cache
-a Prompt for remote password
-e char Set SOL escape character
-C ciphersuite Cipher suite to be used by lanplus interface
-k key Use Kg key for IPMIv2 authentication
-L level Remote session privilege level [privilege levels:
CALLBACK, USER, OPERATOR, ADMINISTRATOR, OEM]
[default=ADMINISTRATOR]
Append a '+' to use name/privilege lookup in RAKP1
-A authtype Force use of auth type NONE, PASSWORD, MD2, MD5 or OEM
-P password Remote session password
-E Read password from IPMI_PASSWORD environment variable
-m address Set local IPMB address
-b channel Set destination channel for bridged request
-l lun Set destination lun for raw commands
-t address Bridge request to remote target address
-o oemtype Setup for OEM (use 'list' to see available OEM types)
-O seloem Use file for OEM SEL event descriptions
Interfaces:
open Linux OpenIPMI Interface [default]
imb Intel IMB Interface
lan IPMI v1.5 LAN Interface
lanplus IPMI v2.0 RMCP+ LAN Interface
Commands:
raw Send a RAW IPMI request and print response
i2c Send an I2C Master Write-Read command and print response
spd Print SPD info from remote I2C device
lan Configure LAN Channels
chassis Get chassis status and set power state
power Shortcut to chassis power commands
event Send pre-defined events to MC
mc Management Controller status and global enables
sdr Print Sensor Data Repository entries and readings
sensor Print detailed sensor information
fru Print built-in FRU and scan SDR for FRU locators
sel Print System Event Log (SEL)
pef Configure Platform Event Filtering (PEF)
sol Configure and connect IPMIv2.0 Serial-over-LAN
tsol Configure and connect with Tyan IPMIv1.5 Serial-over-LAN
isol Configure IPMIv1.5 Serial-over-LAN
user Configure Management Controller users
channel Configure Management Controller channels
session Print session information
sunoem OEM Commands for Sun servers
kontronoem OEM Commands for Kontron devices
picmg Run a PICMG/ATCA extended cmd
fwum Update IPMC using Kontron OEM Firmware Update Manager
firewall Configure Firmware Firewall
shell Launch interactive IPMI shell
exec Run list of commands from file
set Set runtime variable for shell and exec
hpm Update HPM components using PICMG HPM.1 file |
man for ipmitool:
man ipmitool
ipmitool(1) ipmitool(1)
NAME
ipmitool - utility for controlling IPMI-enabled devices
SYNOPSIS
ipmitool [-c|-h|-d N|-v|-V] -I open <command>
ipmitool [-c|-h|-v|-V] -I lan -H <hostname>
[-p <port>]
[-U <username>]
[-A <authtype>]
[-L <privlvl>]
[-a|-E|-P|-f <password>]
[-o <oemtype>]
[-O <sel oem>]
[-e <esc_char>]
<command>
ipmitool [-c|-h|-v|-V] -I lanplus -H <hostname>
[-p <port>]
[-U <username>]
[-L <privlvl>]
[-a|-E|-P|-f <password>]
[-o <oemtype>]
[-O <sel oem>]
[-C <ciphersuite>]
[-k <kg_key>]
[-e <esc_char>]
<command>
DESCRIPTION
This program lets you manage Intelligent Platform Management Interface (IPMI) functions of either the local system, via a kernel device
driver, or a remote system, using IPMI V1.5 and IPMI v2.0. These functions include printing FRU information, LAN configuration, sensor
readings, and remote chassis power control.
IPMI management of a local system interface requires a compatible IPMI kernel driver to be installed and configured. On Linux this
driver is called OpenIPMI and it is included in standard distributions. On Solaris this driver is called BMC and is inclued in Solaris
10. Management of a remote station requires the IPMI-over-LAN interface to be enabled and configured. Depending on the particular
requirements of each system it may be possible to enable the LAN interface using ipmitool over the system interface.
OPTIONS
-a Prompt for the remote server password.
-A <authtype>
Specify an authentication type to use during IPMIv1.5 lan session activation. Supported types are NONE, PASSWORD, MD2, MD5, or
OEM.
-c Present output in CSV (comma separated variable) format. This is not available with all commands.
-e <sol_escape_char>
Use supplied character for SOL session escape character. The default is to use ~ but this can conflict with ssh sessions.
-k <key>
Use supplied Kg key for IPMIv2 authentication. The default is not to use any Kg key.
-C <ciphersuite>
The remote server authentication, integrity, and encryption algorithms to use for IPMIv2 lanplus connections. See table 22-19
in the IPMIv2 specification. The default is 3 which specifies RAKP-HMAC-SHA1 authentication, HMAC-SHA1-96 integrity, and
AES-CBC-128 encryption algorightms.
-E The remote server password is specified by the environment variable IPMI_PASSWORD.
-f <password_file>
Specifies a file containing the remote server password. If this option is absent, or if password_file is empty, the password
will default to NULL.
-h Get basic usage help from the command line.
-H <address>
Remote server address, can be IP address or hostname. This option is required for lan and lanplus interfaces.
-I <interface>
Selects IPMI interface to use. Supported interfaces that are compiled in are visible in the usage help output.
-L <privlvl>
Force session privilege level. Can be CALLBACK, USER, OPERATOR, ADMINISTRATOR. Default is ADMINISTRATOR.
-m <local_address>
Set the local IPMB address. The default is 0x20 and there should be no need to change it for normal operation.
-o <oemtype>
Select OEM type to support. This usually involves minor hacks in place in the code to work around quirks in various BMCs from
various manufacturers. Use -o list to see a list of current supported OEM types.
-O <sel oem>
Open selected file and read OEM SEL event descriptions to be used during SEL listings. See examples in contrib dir for file
format.
-p <port>
Remote server UDP port to connect to. Default is 623.
-P <password>
Remote server password is specified on the command line. If supported it will be obscured in the process list. Note! Specify-
ing the password as a command line option is not recommended.
-S <sdr_cache_file>
Use local file for remote SDR cache. Using a local SDR cache can drastically increase performance for commands that require
knowledge of the entire SDR to perform their function. Local SDR cache from a remote system can be created with the sdr dump
command.
-t <target_address>
Bridge IPMI requests to the remote target address.
-U <username>
Remote server username, default is NULL user.
-d N Use device number N to specify the /dev/ipmiN (or /dev/ipmi/N or /dev/ipmidev/N) device to use for in-band BMC communication.
Used to target a specific BMC on a multi-node, multi-BMC system through the ipmi device driver interface. Default is 0.
-v Increase verbose output level. This option may be specified multiple times to increase the level of debug output. If given
three times you will get hexdumps of all incoming and outgoing packets.
-V Display version information.
If no password method is specified then ipmitool will prompt the user for a password. If no password is entered at the prompt, the
remote server password will default to NULL.
SECURITY
There are several security issues be be considered before enabling the IPMI LAN interface. A remote station has the ability to control
a system's power state as well as being able to gather certain platform information. To reduce vulnerability it is strongly advised
that the IPMI LAN interface only be enabled in 'trusted' environments where system security is not an issue or where there is a dedi-
cated secure 'management network'.
Further it is strongly advised that you should not enable IPMI for remote access without setting a password, and that that password
should not be the same as any other password on that system.
When an IPMI password is changed on a remote machine with the IPMIv1.5 lan interface the new password is sent across the network as
clear text. This could be observed and then used to attack the remote system. It is thus recommended that IPMI password management
only be done over IPMIv2.0 lanplus interface or the system interface on the local station.
For IPMI v1.5, the maximum password length is 16 characters. Passwords longer than 16 characters will be truncated.
For IPMI v2.0, the maximum password length is 20 characters; longer passwords are truncated.
COMMANDS
help This can be used to get command-line help on ipmitool commands. It may also be placed at the end of commands to get option
usage help.
ipmitool help
Commands:
raw Send a RAW IPMI request and print response
lan Configure LAN Channels
chassis Get chassis status and set power state
event Send events to MC
mc Management Controller status and global enables
sdr Print Sensor Data Repository entries and readings
sensor Print detailed sensor information
fru Print built-in FRU and scan for FRU locators
sel Print System Event Log (SEL)
pef Configure Platform Event Filtering (PEF)
sol Configure and connect IPMIv2.0 Serial-over-LAN
tsol Configure and connect Tyan IPMIv1.5 Serial-over-LAN
isol Configure Intel IPMIv1.5 Serial-over-LAN
user Configure Management Controller users
channel Configure Management Controller channels
session Print session information
sunoem Manage Sun OEM Extensions
exec Run list of commands from file
set Set runtime variable for shell and exec
ipmitool chassis help
Chassis Commands: status, power, identify, policy, restart_cause, poh, bootdev
ipmitool chassis power help
chassis power Commands: status, on, off, cycle, reset, diag, soft
bmc|mc
reset <warm|cold>
Instructs the BMC to perform a warm or cold reset.
guid Display the Management Controller Globally Unique IDentifier.
info
Displays information about the BMC hardware, including device revision, firmware revision, IPMI version supported, manu-
facturer ID, and information on additional device support.
getenables
Displays a list of the currently enabled options for the BMC.
setenables <option>=[on|off]
Enables or disables the given option. This command is only supported over the system interface according to the IPMI
specification. Currently supported values for option include:
recv_msg_intr
Receive Message Queue Interrupt
event_msg_intr
Event Message Buffer Full Interrupt
event_msg
Event Message Buffer
system_event_log
System Event Logging
oem0
OEM-Defined option #0
oem1
OEM-Defined option #1
oem2
OEM-Defined option #2
channel
authcap <channel number> <max priv>
Displays information about the authentication capabilities of the selected channel at the specified privilege level.
Possible privilege levels are:
1 Callback level
2 User level
3 Operator level
4 Administrator level
5 OEM Proprietary level
info [channel number]
Displays information about the selected channel. If no channel is given it will display information about the cur-
rently used channel:
> ipmitool channel info
Channel 0xf info:
Channel Medium Type : System Interface
Channel Protocol Type : KCS
Session Support : session-less
Active Session Count : 0
Protocol Vendor ID : 7154
getaccess <channel number> [<userid>]
Configure the given userid as the default on the given channel number. When the given channel is subsequently used, the
user is identified implicitly by the given userid.
setaccess <channel number> <userid> [<callin=on|off>]
[<ipmi=on|off>] [<link=on|off>] [<privilege=level>]
Configure user access information on the given channel for the given userid.
getciphers <ipmi|sol> [<channel>]
Displays the list of cipher suites supported for the given application (ipmi or sol) on the given channel.
chassis
status
Displays information regarding the high-level status of the system chassis and main power subsystem.
poh
This command will return the Power-On Hours counter.
identify <interval>
Control the front panel identify light. Default is 15. Use 0 to turn off.
restart_cause
Query the chassis for the cause of the last system restart.
policy
Set the chassis power policy in the event power failure.
list
Return supported policies.
always-on
Turn on when power is restored.
previous
Returned to previous state when power is restored.
always-off
Stay off after power is restored.
power
Performs a chassis control command to view and change the power state.
status
Show current chassis power status.
on
Power up chassis.
off
Power down chassis into soft off (S4/S5 state). WARNING: This command does not initiate a clean shutdown of the
operating system prior to powering down the system.
cycle
Provides a power off interval of at least 1 second. No action should occur if chassis power is in S4/S5 state,
but it is recommended to check power state first and only issue a power cycle command if the system power is on
or in lower sleep state than S4/S5.
reset
This command will perform a hard reset.
diag
Pulse a diagnostic interrupt (NMI) directly to the processor(s).
soft
Initiate a soft-shutdown of OS via ACPI. This can be done in a number of ways, commonly by simulating an
overtemperture or by simulating a power button press. It is necessary for there to be Operating System support
for ACPI and some sort of daemon watching for events for this soft power to work.
bootdev <device> [<clear-cmos=yes|no>]
Request the system to boot from an alternate boot device on next reboot. The clear-cmos option, if supplied, will
instruct the BIOS to clear its CMOS on the next reboot.
Currently supported values for <device> are:
none
Do not change boot device
pxe
Force PXE boot
disk
Force boot from BIOS default boot device
safe
Force boot from BIOS default boot device, request Safe Mode
diag
Force boot from diagnostic partition
cdrom
Force boot from CD/DVD
bios
Force boot into BIOS setup
event
<predefined event number>
Send a pre-defined event to the System Event Log. The following events are included as a means to test the functionality
of the System Event Log component of the BMC (an entry will be added each time the event n command is executed).
Currently supported values for n are:
1 Temperature: Upper Critical: Going High
2 Voltage Threshold: Lower Critical: Going Low
3 Memory: Correctable ECC Error Detected
NOTE: These pre-defined events will likely not produce "accurate" SEL records for a particular system because they will
not be correctly tied to a valid sensor number, but they are sufficient to verify correct operation of the SEL.
file <filename>
Event log records specified in filename will be added to the System Event Log.
The format of each line in the file is as follows:
<{EvM Revision} {Sensor Type} {Sensor Num} {Event Dir/Type} {Event Data 0} {Event Data 1} {Event Data 2}>[# COMMENT]
:
Note: The Event Dir/Type field is encoded with the event direction as the high bit (bit 7) and the event type as the low
7 bits.
e.g.:
0x4 0x2 0x60 0x1 0x52 0x0 0x0 # Voltage threshold: Lower Critical: Going Low
<sensorid> <state> [<eventdir>]
Generate a custom event based on existing sensor information. The optional event direction can be either assert or
deassert and defaults to assert. To get a list of possible states for a sensor supply a state of list on the command
line. Each sensor may be different but some states will have pre-defined shortcuts. For example:
> ipmitool -I open event p0.t_core
Finding sensor p0.t_core... ok
Sensor States:
lnr : Lower Non-Recoverable
lcr : Lower Critical
lnc : Lower Non-Critical
unc : Upper Non-Critical
ucr : Upper Critical
unr : Upper Non-Recoverable
> ipmitool -I open event ps0.prsnt
Finding sensor ps0.prsnt... ok
Sensor States:
Device Absent
Device Present
State State Shortcuts:
present absent
assert deassert
limit nolimit
fail nofail
yes no
on off
up down
exec <filename>
Execute ipmitool commands from filename. Each line is a complete command. The syntax of the commands are defined by the COM-
MANDS section in this manpage. Each line may have an optional comment at the end of the line, delimited with a '#' symbol.
e.g., a command file with two lines:
sdr list # get a list of sdr records
sel list # get a list of sel records
fru
print
This command will read all Field Replaceable Unit (FRU) inventory data and extract such information as serial number,
part number, asset tags, and short strings describing the chassis, board, or product.
i2c <i2caddr> <read bytes> [<write data>]
This will allow you to execute raw I2C commands with the Master Write-Read IPMI command.
isol
setup <baud rate>
Setup baud rate for Intel IPMI v1.5 Serial-over-LAN.
lan
These commands will allow you to configure IPMI LAN channels with network information so they can be used with the ipmitool lan
and lanplus interfaces. NOTE: To determine on which channel the LAN interface is located, issue the 'channel info number' com-
mand until you come across a valid 802.3 LAN channel. For example:
> ipmitool -I open channel info 1
Channel 0x1 info:
Channel Medium Type : 802.3 LAN
Channel Protocol Type : IPMB-1.0
Session Support : session-based
Active Session Count : 8
Protocol Vendor ID : 7154
print <channel>
Print the current configuration for the given channel.
set <channel> <parameter>
Set the given parameter on the given channel. Valid parameters are:
ipaddr <x.x.x.x>
Set the IP address for this channel.
netmask <x.x.x.x>
Set the netmask for this channel.
macaddr <xx:xx:xx:xx:xx:xx>
Set the MAC address for this channel.
defgw ipaddr <x.x.x.x>
Set the default gateway IP address.
defgw macaddr <xx:xx:xx:xx:xx:xx>
Set the default gateway MAC address.
bakgw ipaddr <x.x.x.x>
Set the backup gateway IP address.
bakgw macaddr <xx:xx:xx:xx:xx:xx>
Set the backup gateway MAC address.
password <pass>
Set the null user password.
snmp <community string>
Set the SNMP community string.
user
Enable user access mode for userid 1 (issue the 'user' command to display information about userids for a given
channel).
access <on|off>
Set LAN channel access mode.
ipsrc <source>
Set the IP address source:
none unspecified
static manually configured static IP address
dhcp address obtained by BMC running DHCP
bios address loaded by BIOS or system software
arp respond <on|off>
Set BMC generated ARP responses.
arp generate <on|off>
Set BMC generated gratuitous ARPs.
arp interval <seconds>
Set BMC generated gratuitous ARP interval.
vlan id <off|id>
Disable VLAN operation or enable VLAN and set the ID.
ID: value of the virtual lan identifier between 1 and 4094 inclusive.
vlan priority <priority>
Set the priority associated with VLAN frames.
ID: priority of the virtual lan frames between 0 and 7 inclusive.
auth <level,...> <type,...>
Set the valid authtypes for a given auth level.
Levels: callback, user, operator, admin
Types: none, md2, md5, password, oem
cipher_privs <privlist>
Correlates cipher suite numbers with the maximum privilege level that is allowed to use it. In this way, cipher
suites can restricted to users with a given privilege level, so that, for example, administrators are required to
use a stronger cipher suite than normal users.
The format of privlist is as follows. Each character represents a privilege level and the character position
identifies the cipher suite number. For example, the first character represents cipher suite 1 (cipher suite 0
is reserved), the second represents cipher suite 2, and so on. privlist must be 15 characters in length.
Characters used in privlist and their associated privilege levels are:
X Cipher Suite Unused
c CALLBACK
u USER
o OPERATOR
a ADMIN
O OEM
So, to set the maximum privilege for cipher suite 1 to USER and suite 2 to ADMIN, issue the following command:
> ipmitool -I interface lan set channel cipher_privs uaXXXXXXXXXXXXX
pef
info
This command will query the BMC and print information about the PEF supported features.
status
This command prints the current PEF status (the last SEL entry processed by the BMC, etc).
policy
This command lists the PEF policy table entries. Each policy entry describes an alert destination. A policy set is a
collection of table entries. PEF alert actions reference policy sets.
list
This command lists the PEF table entries. Each PEF entry relates a sensor event to an action. When PEF is active, each
platform event causes the BMC to scan this table for entries matching the event, and possible actions to be taken.
Actions are performed in priority order (higher criticality first).
raw <netfn> <cmd> [<data>]
This will allow you to execute raw IPMI commands. For example to query the POH counter with a raw command:
> ipmitool -v raw 0x0 0xf
RAW REQ (netfn=0x0 cmd=0xf data_len=0)
RAW RSP (5 bytes)
3c 72 0c 00 00
sdr
get <id> ... [<id>]
Prints information for sensor data records specified by sensor id.
info
This command will query the BMC for SDR information.
type <sensor type>
This command will display all records from the SDR of a specific type. Run with type list to see the list of available
types. For example to query for all Temperature sensors:
> ipmitool sdr type Temperature
Baseboard Temp | 30h | ok | 7.1 | 28 degrees C
FntPnl Amb Temp | 32h | ok | 12.1 | 24 degrees C
Processor1 Temp | 98h | ok | 3.1 | 57 degrees C
Processor2 Temp | 99h | ok | 3.2 | 53 degrees C
list | elist [<all|full|compact|event|mcloc|fru|generic>]
This command will read the Sensor Data Records (SDR) and extract sensor information of a given type, then query each
sensor and print its name, reading, and status. If invoked as elist then it will also print sensor number, entity id and
instance, and asserted discrete states.
The default output will only display full and compact sensor types, to see all sensors use the all type with this com-
mand.
Valid types are:
all
All SDR records (Sensor and Locator)
full
Full Sensor Record
compact
Compact Sensor Record
event
Event-Only Sensor Record
mcloc
Management Controller Locator Record
fru
FRU Locator Record
generic
Generic SDR records
entity <id>[.<instance>]
Displays all sensors associated with an entity. Get a list of valid entity ids on the target system by issuing the sdr
elist command. A list of all entity ids can be found in the IPMI specifications.
dump <file>
Dumps raw SDR data to a file. This data file can then be used as a local SDR cache of the remote managed system with the
-S <file> option on the ipmitool command line. This can greatly improve performance over system interface or remote LAN.
sel
NOTE: SEL entry-times are displayed as 'Pre-Init Time-stamp' if the SEL clock needs to be set. Ensure that the SEL clock is
accurate by invoking the sel time get and sel time set <time string> commands.
info
This command will query the BMC for information about the System Event Log (SEL) and its contents.
clear
This command will clear the contents of the SEL. It cannot be undone so be careful.
list | elist
When this command is invoked without arguments, the entire contents of the System Event Log are displayed. If invoked as
elist it will also use the Sensor Data Record entries to display the sensor ID for the sensor that caused each event.
Note this can take a long time over the system interface.
<count>|first <count>
Displays the first count (least-recent) entries in the SEL. If count is zero, all entries are displayed.
last <count>
Displays the last count (most-recent) entries in the SEL. If count is zero, all entries are displayed.
delete <number>
Delete a single event.
save <file>
Save SEL records to text file that can be fed back into the event file ipmitool command. This can be useful for testing
Event generation by building an appropriate Platform Event Message file based on existing events. Please see the help
for that command to view the format of this file.
writeraw <file>
Save SEL records to a file in raw, binary format. This file can be fed back to the sel readraw ipmitool command for
viewing.
readraw <file>
Read and display SEL records from a binary file. Such a file can be created using the sel writeraw ipmitool command.
time
get
Displays the SEL clock's current time.
set <time string>
Sets the SEL clock. Future SEL entries will use the time set by this command. <time string> is of the form
"MM/DD/YYYY HH:MM:SS". Note that hours are in 24-hour form. It is recommended that the SEL be cleared before
setting the time.
sensor
list
Lists sensors and thresholds in a wide table format.
get <id> ... [<id>]
Prints information for sensors specified by name.
thresh <id> <threshold> <setting>
This allows you to set a particular sensor threshold value. The sensor is specified by name.
Valid thresholds are:
unr Upper Non-Recoverable
ucr Upper Critical
unc Upper Non-Critical
lnc Lower Non-Critical
lcr Lower Critical
lnr Lower Non-Recoverable
thresh <id> lower <lnr> <lcr> <lnc>
This allows you to set all lower thresholds for a sensor at the same time. The sensor is specified by name and the
thresholds are listed in order of Lower Non-Recoverable, Lower Critical, and Lower Non-Critical.
thresh <id> upper <unc> <ucr> <unr>
This allows you to set all upper thresholds for a sensor at the same time. The sensor is specified by name and the
thresholds are listed in order of Upper Non-Critical, Upper Critical, and Upper Non-Recoverable.
session
info <active|all|id 0xnnnnnnnn|handle 0xnn>
Get information about the specified session(s). You may identify sessions by their id, by their handle number, by their
active status, or by using the keyword 'all' to specify all sessions.
shell
This command will launch an interactive shell which you can use to send multiple ipmitool commands to a BMC and see the
responses. This can be useful instead of running the full ipmitool command each time. Some commands will make use of a Sensor
Data Record cache and you will see marked improvement in speed if these commands are able to reuse the same cache in a shell
session. LAN sessions will send a periodic keepalive command to keep the IPMI session from timing out.
sol
info [<channel number>]
Retrieve information about the Serial-Over-LAN configuration on the specified channel. If no channel is given, it will
display SOL configuration data for the currently used channel.
set <parameter> <value> [<channel>]
Configure parameters for Serial Over Lan. If no channel is given, it will display SOL configuration data for the cur-
rently used channel. Configuration parameter updates are automatically guarded with the updates to the set-in-progress
parameter.
Valid parameters and values are:
set-in-progress
set-complete set-in-progress commit-write
enabled
true false
force-encryption
true false
force-authentication
true false
privilege-level
user operator admin oem
character-accumulate-level
Decimal number given in 5 milliseconds increments
character-send-threshold
Decimal number
retry-count
Decimal number. 0 indicates no retries after packet is transmitted.
retry-interval
Decimal number in 10 millisend increments. 0 indicates that retries should be sent back to back.
non-volatile-bit-rate
serial, 19.2, 38.4, 57.6, 115.2. Setting this value to serial indicates that the BMC should use the setting used
by the IPMI over serial channel.
volatile-bit-rate
serial, 19.2, 38.4, 57.6, 115.2. Setting this value to serial indiates that the BMC should use the setting used
by the IPMI over serial channel.
activate
Causes ipmitool to enter Serial Over LAN mode, and is only available when using the lanplus interface. An RMCP+ connec-
tion is made to the BMC, the terminal is set to raw mode, and user input is sent to the serial console on the remote
server. On exit,the the SOL payload mode is deactivated and the terminal is reset to its original settings.
Special escape sequences are provided to control the SOL session:
~. Terminate connection
~^Z Suspend ipmitool
~B Send break
~~ Send the escape character by typing it twice
~? Print the supported escape sequences
deactivate
Deactivates Serial Over LAN mode on the BMC. Exiting Serial Over LAN mode should automatically cause this command to be
sent to the BMC, but in the case of an unintentional exit from SOL mode, this command may be necessary to reset the state
of the BMC.
sunoem
led
These commands provide a way to get and set the status of LEDs on a Sun Microsystems server. Use 'sdr list generic' to
get a list of devices that are controllable LEDs. The ledtype parameter is optional and not necessary to provide on the
command line unless it is required by hardware.
get <sensorid> [<ledtype>]
Get status of a particular LED described by a Generic Device Locator record in the SDR. A sensorid of all will
get the status of all available LEDS.
set <sensorid> <ledmode> [<ledtype>]
Set status of a particular LED described by a Generic Device Locator record in the SDR. A sensorid of all will
set the status of all available LEDS to the specified ledmode and ledtype.
LED Mode is required for set operations:
OFF Off
ON Steady On
STANDBY 100ms on 2900ms off blink rate
SLOW 1HZ blink rate
FAST 4HZ blink rate
LED Type is optional:
OK2RM Ok to Remove
SERVICE Service Required
ACT Activity
LOCATE Locate
sshkey
set <userid> <keyfile>
This command will allow you to specify an SSH key to use for a particular user on the Service Processor. This
key will be used for CLI logins to the SP and not for IPMI sessions. View available users and their userids with
the 'user list' command.
del <userid>
This command will delete the SSH key for a specified userid.
tsol
This command allows Serial-over-LAN sessions to be established with Tyan IPMIv1.5 SMDC such as the M3289 or M3290. The default
command run with no arguments will establish default SOL session back to local IP address. Optional arguments may be supplied
in any order.
<ipaddr>
Send receiver IP address to SMDC which it will use to send serial traffic to. By default this detects the local IP
address and establishes two-way session.
port=NUM
Configure UDP port to receive serial traffic on. By default this is 6230.
ro|rw
Confiure SOL session as read-only or read-write. Sessions are read-write by default.
user
summary
Displays a summary of userid information, including maximum number of userids, the number of enabled users, and the num-
ber of fixed names defined.
list
Displays a list of user information for all defined userids.
set
name <userid> <username>
Sets the username associated with the given userid.
password <userid> [<password>]
Sets the password for the given userid. If no password is given, the password is cleared (set to the NULL pass-
word). Be careful when removing passwords from administrator-level accounts.
disable <userid>
Disables access to the BMC by the given userid.
enable <userid>
Enables access to the BMC by the given userid.
test <userid> <16|20> [<password>]
Determine whether a password has been stored as 16 or 20 bytes.
OPEN INTERFACE
The ipmitool open interface utilizes the OpenIPMI kernel device driver. This driver is present in all modern 2.4 and all 2.6 kernels
and it should be present in recent Linux distribution kernels. There are also IPMI driver kernel patches for different kernel versions
available from the OpenIPMI homepage.
The required kernel modules is different for 2.4 and 2.6 kernels. The following kernel modules must be loaded on a 2.4-based kernel in
order for ipmitool to work:
ipmi_msghandler
Incoming and outgoing message handler for IPMI interfaces.
ipmi_kcs_drv
An IPMI Keyboard Controler Style (KCS) interface driver for the message handler.
ipmi_devintf
Linux character device interface for the message handler.
The following kernel modules must be loaded on a 2.6-based kernel in order for ipmitool to work:
ipmi_msghandler
Incoming and outgoing message handler for IPMI interfaces.
ipmi_si
An IPMI system interface driver for the message handler. This module supports various IPMI system interfaces such as KCS, BT,
SMIC, and even SMBus in 2.6 kernels.
ipmi_devintf
Linux character device interface for the message handler.
Once the required modules are loaded there will be a dynamic character device entry that must exist at /dev/ipmi0. For systems that
use devfs or udev this will appear at /dev/ipmi/0.
To create the device node first determine what dynamic major number it was assigned by the kernel by looking in /proc/devices and
checking for the ipmidev entry. Usually if this is the first dynamic device it will be major number 254 and the minor number for the
first system interface is 0 so you would create the device entry with:
mknod /dev/ipmi0 c 254 0
ipmitool includes some sample initialization scripts that can perform this task automatically at start-up.
In order to have ipmitool use the OpenIPMI device interface you can specifiy it on the command line:
ipmitool -I open <command>
BMC INTERFACE
The ipmitool bmc interface utilizes the bmc device driver as provided by Solaris 10 and higher. In order to force ipmitool to make use
of this interface you can specify it on the command line:
ipmitool -I bmc <command>
The following files are associated with the bmc driver:
/platform/i86pc/kernel/drv/bmc
32-bit ELF kernel module for the bmc driver.
/platform/i86pc/kernel/drv/amd64/bmc
32-bit ELF kernel module for the bmc driver.
/platform/i86pc/kernel/drv/amd64/bmc
64-bit ELF kernel module for the bmc driver.
/dev/bmc
Character device node used to communicate with the bmc driver.
LIPMI INTERFACE
The ipmitool lipmi interface uses the Solaris 9 IPMI kernel device driver. It has been superceeded by the bmc interface on Solaris 10.
You can tell ipmitool to use this interface by specifying it on the command line.
ipmitool -I lipmi <expression>
LAN INTERFACE
The ipmitool lan interface communicates with the BMC over an Ethernet LAN connection using UDP under IPv4. UDP datagrams are formatted
to contain IPMI request/response messages with a IPMI session headers and RMCP headers.
IPMI-over-LAN uses version 1 of the Remote Management Control Protocol (RMCP) to support pre-OS and OS-absent management. RMCP is a
request-response protocol delivered using UDP datagrams to port 623.
The LAN interface is an authenticatiod multi-session connection; messages delivered to the BMC can (and should) be authenticated with a
challenge/response protocol with either straight password/key or MD5 message-digest algorithm. ipmitool will attempt to connect with
administrator privilege level as this is required to perform chassis power functions.
You can tell ipmitool to use the lan interface with the -I lan option:
ipmitool -I lan -H <hostname> [-U <username>] [-P <password>] <command>
A hostname must be given on the command line in order to use the lan interface with ipmitool. The password field is optional; if you
do not provide a password on the command line, ipmitool will attempt to connect without authentication. If you specify a password it
will use MD5 authentication if supported by the BMC and straight password/key otherwise, unless overridden with a command line option.
LANPLUS INTERFACE
Like the lan interface, the lanplus interface communicates with the BMC over an Ethernet LAN connection using UDP under IPv4. The dif-
ference is that the lanplus interface uses the RMCP+ protocol as described in the IMPI v2.0 specification. RMCP+ allows for improved
authentication and data integrity checks, as well as encryption and the ability to carry multiple types of payloads. Generic Serial
Over LAN support requires RMCP+, so the ipmitool sol activate command requires the use of the lanplus interface.
RMCP+ session establishment uses a symmetric challenge-response protocol called RAKP (Remote Authenticated Key-Exchange Protocol) which
allows the negotiation of many options. ipmitool does not yet allow the user to specify the value of every option, defaulting to the
most obvious settings marked as required in the v2.0 specification. Authentication and integrity HMACS are produced with SHA1, and
encryption is performed with AES-CBC-128. Role-level logins are not yet supported.
ipmitool must be linked with the OpenSSL library in order to perform the encryption functions and support the lanplus interface. If
the required packages are not found it will not be compiled in and supported.
You can tell ipmitool to use the lanplus interface with the -I lanplus option:
ipmitool -I lanplus -H <hostname> [-U <username>] [-P <password>] <command>
A hostname must be given on the command line in order to use the lan interface with ipmitool. With the exception of the -A and -C
options the rest of the command line options are identical to those available for the lan interface.
The -C option allows you specify the authentication, integrity, and encryption algorithms to use for for lanplus session based on the
cipher suite ID found in the IPMIv2.0 specification in table 22-19. The default cipher suite is 3 which specifies RAKP-HMAC-SHA1
authentication, HMAC-SHA1-96 integrity, and AES-CBC-128 encryption algorightms.
FREE INTERFACE
The ipmitool free interface utilizes the FreeIPMI libfreeipmi drivers.
You can tell ipmitool to use the FreeIPMI interface with the -I option:
ipmitool -I free <command>
EXAMPLES
Example 1: Listing remote sensors
> ipmitool -I lan -H 1.2.3.4 -f passfile sdr list
Baseboard 1.25V | 1.24 Volts | ok
Baseboard 2.5V | 2.49 Volts | ok
Baseboard 3.3V | 3.32 Volts | ok
Example 2: Displaying status of a remote sensor
> ipmitool -I lan -H 1.2.3.4 -f passfile sensor get "Baseboard 1.25V"
Locating sensor record...
Sensor ID : Baseboard 1.25V (0x10)
Sensor Type (Analog) : Voltage
Sensor Reading : 1.245 (+/- 0.039) Volts
Status : ok
Lower Non-Recoverable : na
Lower Critical : 1.078
Lower Non-Critical : 1.107
Upper Non-Critical : 1.382
Upper Critical : 1.431
Upper Non-Recoverable : na
Example 3: Displaying the power status of a remote chassis
> ipmitool -I lan -H 1.2.3.4 -f passfile chassis power status
Chassis Power is on
Example 4: Controlling the power on a remote chassis
> ipmitool -I lan -H 1.2.3.4 -f passfile chassis power on
Chassis Power Control: Up/On
AUTHOR
Duncan Laurie <duncan@iceblink.org>
SEE ALSO
IPMItool Homepage
http://ipmitool.sourceforge.net
Intelligent Platform Management Interface Specification
http://www.intel.com/design/servers/ipmi
OpenIPMI Homepage
http://openipmi.sourceforge.net
FreeIPMI Homepage
http://www.gnu.org/software/freeipmi/ |
作者: David, 于 May 6th,2011
#man lsscsi
lsscsi(8) LSSCSI lsscsi(8)
NAME
lsscsi - list SCSI devices (or hosts) and their attributes
SYNOPSIS
lsscsi [--classic|-c] [--device|-d] [--generic|-g] [--help|-h] [--hosts|-H] [--kname|-k] [--long|-l] [--verbose] [--version]
[<h:c:t:l>]
DESCRIPTION
Uses information in sysfs (linux kernels 2.6.0 and later) to list scsi devices (or hosts) currently attached to the system. Options can
be used to control the amount and form of information provided for each device.
If a <h:c:t:l> argument is given then it acts as a filter and only devices that match it are listed. The colons don't have to be
present, and '-', '*', '?' or missing arguments at the end are wildcards. '-' needs to stand alone or else it is taken as the beginning
of an option (e.g. '-:-:-:-' is illegal). '*' needs to be escaped from the shell. A leading '[' and trailing ']' are permitted (e.g.
'[1:0:0]' matches all luns on 1:0:0).
By default in this utility device node names (e.g. "/dev/sda" or "/dev/root_disk") are obtained by noting the major and minor numbers
for the listed device obtained from sysfs (e.g. the contents of /sys/block/sda/dev) and then looking for a match in the "/dev" direc-
tory. This "match by major and minor" will allow devices that have been given a different name by udev (for example) to be correctly
reported by this utility.
In some situations it may be useful to see the device node name that linux would produce by default, so the '--kname' option is pro-
vided. An example of where this may be useful is kernel error logs which tend to report disk error messages using the disk's default
kernel name.
--classic | -c
The output is similar to that obtained from 'cat /proc/scsi/scsi'
--device | -d
After outputting the (probable) scsi device name the the device node major and minor numbers are shown in brackets (e.g.
"/dev/sda[8:0]").
--generic | -g
Output the scsi generic device file name. Note that if the sg driver is a module it needs to be loaded otherwise '-' will appear
--help | -h
Output the usage message and exit
--hosts | -H
List the SCSI hosts currently attached to the system. If this option is not given then SCSI devices are listed
--kname | -k
Use linux default algorithm for naming devices (e.g. block major 8, minor 0 is "/dev/sda") rather than the "match by major and
minor" in the "/dev" directory as discussed above.
--long | -l
Output additional information for each SCSI device (host). Can be used multiple times for more output in which case the shorter
form is more convenient (e.g. '-lll'). When used three times (i.e. '-lll') outputs SCSI device (host) attributes one per line;
preceded by two spaces; in the form "<attribute_name>=<value>".
--verbose | -v
outputs directory names where information is found. Use twice for more output.
--version | -V
outputs version number information and exits
Information for this command is derived from the the sysfs file system whose mount point is found by examining the contents of
/proc/mounts . SCSI (pseudo) devices that have been detected by the SCSI mid level will be listed even if the required upper level
drivers (i.e. sd, sr, st, osst or ch) have not been loaded. If the appropriate upper level driver has not been loaded then the device
file name will appear as '-' rather than something like '/dev/st0'. Note that some devices (e.g. scanners and medium changers) do not
have a primary upper level driver and can only be accessed via a scsi generic (sg) device name.
AUTHOR
Written by Doug Gilbert
REPORTING BUGS
Report bugs to <dgilbert at interlog dot com>.
COPYRIGHT
Copyright © 2003-2005 Douglas Gilbert
This software is distributed under the GPL version 2. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR
PURPOSE.
SEE ALSO
lspci lsusb and systool The latter utility can be found in the sysfsutils package.
lsscsi-0.16 December 2005 lsscsi(8) |
作者: David, 于 May 3rd,2011
Reference for LSI MegaRAID command interface.
MegaCli64 -h
MegaCLI SAS RAID Management Tool Ver 8.00.23 May 17, 2010
(c)Copyright 2010, LSI Corporation, All Rights Reserved.
NOTE: The following options may be given at the end of any command below:
[-Silent] [-AppLogFile filename] [-NoLog] [-page[N]]
[-] is optional.
N - Number of lines per page.
MegaCli -v
MegaCli -help|-h|?
MegaCli -adpCount
MegaCli -AdpSetProp {CacheFlushInterval -val} | { RebuildRate -val}
| {PatrolReadRate -val} | {BgiRate -val} | {CCRate -val}
| {ReconRate -val} | {SpinupDriveCount -val} | {SpinupDelay -val}
| {CoercionMode -val} | {ClusterEnable -val} | {PredFailPollInterval -val}
| {BatWarnDsbl -val} | {EccBucketSize -val} | {EccBucketLeakRate -val}
| {AbortCCOnError -val} | AlarmEnbl | AlarmDsbl | AlarmSilence
| {SMARTCpyBkEnbl -val} | {SSDSMARTCpyBkEnbl -val} | NCQEnbl | NCQDsbl
| {MaintainPdFailHistoryEnbl -val} | {RstrHotSpareOnInsert -val}
| {EnblSpinDownUnConfigDrvs -val} | {EnblSSDPatrolRead -val}
| {DisableOCR -val} | {BootWithPinnedCache -val}
| AutoEnhancedImportEnbl | AutoEnhancedImportDsbl
| {ExposeEnclDevicesEnbl -val} | {SpinDownTime -val} -aN|-a0,1,2|-aALL
MegaCli -AdpSetProp -AutoDetectBackPlaneDsbl -val -aN|-a0,1,2|-aALL
val - 0=Enable Auto Detect of SGPIO and i2c SEP.
1=Disable Auto Detect of SGPIO.
2=Disable Auto Detect of i2c SEP.
3=Disable Auto Detect of SGPIO and i2c SEP.
MegaCli -AdpSetProp -CopyBackDsbl -val -aN|-a0,1,2|-aALL
val - 0=Enable Copyback.
1=Disable Copyback.
MegaCli -AdpSetProp -EnableJBOD -val -aN|-a0,1,2|-aALL
val - 0=Disable JBOD mode.
1=Enable JBOD mode.
MegaCli -AdpSetProp -DsblCacheBypass -val -aN|-a0,1,2|-aALL
val - 0=Enable Cache Bypass.
1=Disable Cache Bypass.
MegaCli -AdpSetProp -LoadBalanceMode -val -aN|-a0,1,2|-aALL
val - 0=Auto Load balance mode.
1=Disable Load balance mode.
MegaCli -AdpSetProp -UseFDEOnlyEncrypt -val -aN|-a0,1,2|-aALL
val - 0=FDE and controller encryption (if HW supports) is allowed.
1=Only support FDE encryption, disallow controller encryption.
MegaCli -AdpSetProp -PrCorrectUncfgdAreas -val -aN|-a0,1,2|-aALL
val - 0= Correcting Media error during PR is disabled.
1=Correcting Media error during PR is allowed.
MegaCli -AdpSetProp -DsblSpinDownHSP -val -aN|-a0,1,2|-aALL
val - 0= Spinning down the Hot Spare is enabled.
1=Spinning down the Hot Spare is disabled.
MegaCli -AdpGetProp CacheFlushInterval | RebuildRate | PatrolReadRate
| BgiRate | CCRate | ReconRate | SpinupDriveCount | SpinupDelay
| CoercionMode | ClusterEnable | PredFailPollInterval | BatWarnDsbl
| EccBucketSize | EccBucketLeakRate | EccBucketCount | AbortCCOnError
| AlarmDsply | SMARTCpyBkEnbl | SSDSMARTCpyBkEnbl | NCQDsply
| MaintainPdFailHistoryEnbl | RstrHotSpareOnInsert
| EnblSpinDownUnConfigDrvs | EnblSSDPatrolRead | DisableOCR
| BootWithPinnedCache | AutoEnhancedImportDsply | AutoDetectBackPlaneDsbl
| CopyBackDsbl | LoadBalanceMode | UseFDEOnlyEncrypt | WBSupport | EnableJBOD
| DsblCacheBypass | ExposeEnclDevicesEnbl | SpinDownTime
| PrCorrectUncfgdAreas -aN|-a0,1,2|-aALL
| DsblSpinDownHSP -aN|-a0,1,2|-aALL
MegaCli -AdpAllInfo -aN|-a0,1,2|-aALL
MegaCli -AdpGetTime -aN|-a0,1,2|-aALL
MegaCli -AdpSetTime yyyymmdd hh:mm:ss -aN
MegaCli -AdpSetVerify -f fileName -aN|-a0,1,2|-aALL
MegaCli -AdpBIOS -Enbl |-Dsbl | -SOE | -BE | EnblAutoSelectBootLd | DsblAutoSelectBootLd | -Dsply -aN|-a0,1,2|-aALL
MegaCli -AdpBootDrive {-Set {-Lx | -physdrv[E0:S0]}}|-Get -aN|-a0,1,2|-aALL
MegaCli -AdpAutoRbld -Enbl|-Dsbl|-Dsply -aN|-a0,1,2|-aALL
MegaCli -AdpCacheFlush -aN|-a0,1,2|-aALL
MegaCli -AdpPR -Dsbl|EnblAuto|EnblMan|Start|Stop|Info| SSDPatrolReadEnbl | SSDPatrolReadDsbl
|{SetDelay Val}|{-SetStartTime yyyymmdd hh}|{maxConcurrentPD Val} -aN|-a0,1,2|-aALL
MegaCli -AdpCcSched -Dsbl|-Info|{-ModeConc | -ModeSeq [-ExcludeLD -LN|-L0,1,2]
[-SetStartTime yyyymmdd hh ] [-SetDelay val ] } -aN|-a0,1,2|-aALL
MegaCli -AdpCcSched -SetStartTime yyyymmdd hh -aN|-a0,1,2|-aALL
MegaCli -AdpCcSched -SetDelay val -aN|-a0,1,2|-aALL
MegaCli -FwTermLog -BBUoff|BBUoffTemp|BBUon|BBUGet|Dsply|Clear -aN|-a0,1,2|-aALL
MegaCli -AdpAlILog -aN|-a0,1,2|-aALL
MegaCli -AdpDiag [val] -aN|-a0,1,2|-aALL
val - Time in second.
MegaCli -AdpShutDown -aN|-a0,1,2|-aALL
MegaCli -PDList -aN|-a0,1,2|-aALL
MegaCli -PDGetNum -aN|-a0,1,2|-aALL
MegaCli -pdInfo -PhysDrv[E0:S0,E1:S1,...] -aN|-a0,1,2|-aALL
MegaCli -PDOnline -PhysDrv[E0:S0,E1:S1,...] -aN|-a0,1,2|-aALL
MegaCli -PDOffline -PhysDrv[E0:S0,E1:S1,...] -aN|-a0,1,2|-aALL
MegaCli -PDMakeGood -PhysDrv[E0:S0,E1:S1,...] | [-Force] -aN|-a0,1,2|-aALL
MegaCli -PDMakeJBOD -PhysDrv[E0:S0,E1:S1,...] -aN|-a0,1,2|-aALL
MegaCli -PDHSP {-Set [-Dedicated [-ArrayN|-Array0,1,2...]] [-EnclAffinity] [-nonRevertible]}
|-Rmv -PhysDrv[E0:S0,E1:S1,...] -aN|-a0,1,2|-aALL
MegaCli -PDRbld -Start|-Stop|-ShowProg |-ProgDsply
-PhysDrv [E0:S0,E1:S1,...] -aN|-a0,1,2|-aALL
MegaCli -PDClear -Start|-Stop|-ShowProg |-ProgDsply
-PhysDrv [E0:S0,E1:S1,...] -aN|-a0,1,2|-aALL
MegaCli -PdLocate {[-start] | -stop} -physdrv[E0:S0,E1:S1,...] -aN|-a0,1,2|-aALL
MegaCli -PdMarkMissing -physdrv[E0:S0,E1:S1,...] -aN|-a0,1,2|-aALL
MegaCli -PdGetMissing -aN|-a0,1,2|-aALL
MegaCli -PdReplaceMissing -physdrv[E0:S0] -arrayA, -rowB -aN
MegaCli -PdPrpRmv [-UnDo] -physdrv[E0:S0] -aN|-a0,1,2|-aALL
MegaCli -EncInfo -aN|-a0,1,2|-aALL
MegaCli -EncStatus -aN|-a0,1,2|-aALL
MegaCli -PhyInfo -phyM -aN|-a0,1,2|-aALL
MegaCli -PdFwDownload [offline] {[-SataBridge] -PhysDrv[0:1,1:2,...] }|{EncdevId[devId1,devId2,...]} -f <filename> -aN|-a0,1,2|-aALL
MegaCli -LDInfo -Lx|-L0,1,2|-Lall -aN|-a0,1,2|-aALL
MegaCli -LDSetProp {-Name LdNamestring} | -RW|RO|Blocked | WT|WB [-Immediate] |RA|NORA|ADRA
| Cached|Direct | -EnDskCache|DisDskCache | CachedBadBBU|NoCachedBadBBU
-Lx|-L0,1,2|-Lall -aN|-a0,1,2|-aALL
MegaCli -LDGetProp -Cache | -Access | -Name | -DskCache -Lx|-L0,1,2|-LALL
-aN|-a0,1,2|-aALL
MegaCli -LDInit {-Start [-full]}|-Abort|-ShowProg|-ProgDsply -Lx|-L0,1,2|-LALL -aN|-a0,1,2|-aALL
MegaCli -LDCC {-Start [-force]}|-Abort|-ShowProg|-ProgDsply -Lx|-L0,1,2|-LALL -aN|-a0,1,2|-aALL
MegaCli -LDBI -Enbl|-Dsbl|-getSetting|-Abort|-ShowProg|-ProgDsply -Lx|-L0,1,2|-LALL -aN|-a0,1,2|-aALL
MegaCli -LDRecon {-Start -rX [{-Add | -Rmv} -Physdrv[E0:S0,...]]}|-ShowProg|-ProgDsply
-Lx -aN
MegaCli -LdPdInfo -aN|-a0,1,2|-aALL
MegaCli -LDGetNum -aN|-a0,1,2|-aALL
MegaCli -LDBBMClr -Lx|-L0,1,2,...|-Lall -aN|-a0,1,2|-aALL
MegaCli -getLdExpansionInfo -Lx|-L0,1,2|-Lall -aN|-a0,1,2|-aALL
MegaCli -LdExpansion -pN -dontExpandArray -Lx|-L0,1,2|-Lall -aN|-a0,1,2|-aALL
MegaCli -CfgLdAdd -rX[E0:S0,E1:S1,...] [WT|WB] [NORA|RA|ADRA] [Direct|Cached]
[CachedBadBBU|NoCachedBadBBU] [-szXXX [-szYYY ...]]
[-strpszM] [-Hsp[E0:S0,...]] [-AfterLdX] [-Force]|[FDE|CtrlBased] -aN
MegaCli -CfgCacheCadeAdd -Physdrv[E0:S0,...] {-Name LdNamestring} -aN|-a0,1,2|-aALL
MegaCli -CfgEachDskRaid0 [WT|WB] [NORA|RA|ADRA] [Direct|Cached]
[CachedBadBBU|NoCachedBadBBU] [-strpszM]|[FDE|CtrlBased] -aN|-a0,1,2|-aALL
MegaCli -CfgClr -aN|-a0,1,2|-aALL
MegaCli -CfgDsply -aN|-a0,1,2|-aALL
MegaCli -CfgLdDel -LX|-L0,2,5...|-LALL -aN|-a0,1,2|-aALL
MegaCli -CfgCacheCadeDel -LX|-L0,2,5...|-LALL -aN|-a0,1,2|-aALL
MegaCli -CfgFreeSpaceinfo -aN|-a0,1,2|-aALL
MegaCli -CfgSpanAdd -r10 -Array0[E0:S0,E1:S1] -Array1[E0:S0,E1:S1] [-ArrayX[E0:S0,E1:S1] ...]
[WT|WB] [NORA|RA|ADRA] [Direct|Cached] [CachedBadBBU|NoCachedBadBBU]
[-szXXX[-szYYY ...]][-strpszM][-AfterLdX][-Force]|[FDE|CtrlBased] -aN
MegaCli -CfgSpanAdd -r50 -Array0[E0:S0,E1:S1,E2:S2,...] -Array1[E0:S0,E1:S1,E2:S2,...]
[-ArrayX[E0:S0,E1:S1,E2:S2,...] ...] [WT|WB] [NORA|RA|ADRA] [Direct|Cached]
[CachedBadBBU|NoCachedBadBBU][-szXXX[-szYYY ...]][-strpszM][-AfterLdX][-Force]|
[FDE|CtrlBased] -aN
MegaCli -CfgAllFreeDrv -rX [-SATAOnly] [-SpanCount XXX] [WT|WB] [NORA|RA|ADRA]
[Direct|Cached] [CachedBadBBU|NoCachedBadBBU] [-strpszM]
[-HspCount XX [-HspType -Dedicated|-EnclAffinity|-nonRevertible]]|
[FDE|CtrlBased] -aN
MegaCli -CfgSave -f filename -aN
MegaCli -CfgRestore -f filename -aN
MegaCli -CfgForeign -Scan | [-SecurityKey sssssssssss] -aN|-a0,1,2|-aALL
MegaCli -CfgForeign -Dsply [x] | [-SecurityKey sssssssssss] -aN|-a0,1,2|-aALL
MegaCli -CfgForeign -Preview [x] | [-SecurityKey sssssssssss] -aN|-a0,1,2|-aALL
MegaCli -CfgForeign -Import [x] | [-SecurityKey sssssssssss] -aN|-a0,1,2|-aALL
MegaCli -CfgForeign -Clear [x]|[-SecurityKey sssssssssss] -aN|-a0,1,2|-aALL
x - index of foreign configurations. Optional. All by default.
MegaCli -AdpEventLog -GetEventLogInfo -aN|-a0,1,2|-aALL
MegaCli -AdpEventLog -GetEvents {-info -warning -critical -fatal} {-f <fileName>} -aN|-a0,1,2|-aALL
MegaCli -AdpEventLog -GetSinceShutdown {-info -warning -critical -fatal} {-f <fileName>} -aN|-a0,1,2|-aALL
MegaCli -AdpEventLog -GetSinceReboot {-info -warning -critical -fatal} {-f <fileName>} -aN|-a0,1,2|-aALL
MegaCli -AdpEventLog -IncludeDeleted {-info -warning -critical -fatal} {-f <fileName>} -aN|-a0,1,2|-aALL
MegaCli -AdpEventLog -GetLatest n {-info -warning -critical -fatal} {-f <fileName>} -aN|-a0,1,2|-aALL
MegaCli -AdpEventLog -GetCCIncon -f <fileName> -LX|-L0,2,5...|-LALL -aN|-a0,1,2|-aALL
MegaCli -AdpEventLog -Clear -aN|-a0,1,2|-aALL
MegaCli -AdpBbuCmd -aN|-a0,1,2|-aALL
MegaCli -AdpBbuCmd -GetBbuStatus -aN|-a0,1,2|-aALL
MegaCli -AdpBbuCmd -GetBbuCapacityInfo -aN|-a0,1,2|-aALL
MegaCli -AdpBbuCmd -GetBbuDesignInfo -aN|-a0,1,2|-aALL
MegaCli -AdpBbuCmd -GetBbuProperties -aN|-a0,1,2|-aALL
MegaCli -AdpBbuCmd -BbuLearn -aN|-a0,1,2|-aALL
MegaCli -AdpBbuCmd -BbuMfgSleep -aN|-a0,1,2|-aALL
MegaCli -AdpBbuCmd -BbuMfgSeal -aN|-a0,1,2|-aALL
MegaCli -AdpBbuCmd -SetBbuProperties -f <fileName> -aN|-a0,1,2|-aALL
MegaCli -AdpFacDefSet -aN
MegaCli -AdpFwFlash -f filename [-NoSigChk] [-NoVerChk] -aN|-a0,1,2|-aALL
MegaCli -AdpGetConnectorMode -ConnectorN|-Connector0,1|-ConnectorAll -aN|-a0,1,2|-aALL
MegaCli -AdpSetConnectorMode -Internal|-External|-Auto -ConnectorN|-Connector0,1|-ConnectorAll -aN|-a0,1,2|-aALL
MegaCli -PhyErrorCounters -aN|-a0,1,2|-aALL
MegaCli -DirectPdMapping -Enbl|-Dsbl|-Dsply -aN|-a0,1,2|-aALL
MegaCli -PDCpyBk -Start -PhysDrv[E0:S0,E1:S1] -aN|-a0,1,2|-aALL
MegaCli -PDCpyBk -Stop|-ShowProg|-ProgDsply -PhysDrv[E0:S0] -aN|-a0,1,2|-aALL
MegaCli -PDInstantSecureErase -PhysDrv[E0:S0,E1:S1,...] | [-Force] -aN|-a0,1,2|-aALL
MegaCli -LDMakeSecure -Lx|-L0,1,2,...|-Lall -aN|-a0,1,2|-aALL
MegaCli -DestroySecurityKey | [-Force] -aN
MegaCli -CreateSecurityKey -SecurityKey sssssssssss | [-Passphrase sssssssssss] |[-KeyID kkkkkkkkkkk] -aN
MegaCli -CreateSecurityKey useEKMS -aN
MegaCli -ChangeSecurityKey -OldSecurityKey sssssssssss | -SecurityKey sssssssssss|
[-Passphrase sssssssssss] | [-KeyID kkkkkkkkkkk] -aN
MegaCli -ChangeSecurityKey -SecurityKey sssssssssss|
[-Passphrase sssssssssss] | [-KeyID kkkkkkkkkkk] -aN
MegaCli -ChangeSecurityKey useEKMS -OldSecurityKey sssssssssss -aN
MegaCli -ChangeSecurityKey -useEKMS -aN
MegaCli -GetKeyID [-PhysDrv[E0:S0]] -aN
MegaCli -SetKeyID -KeyID kkkkkkkkkkk -aN
MegaCli -VerifySecurityKey -SecurityKey sssssssssss -aN
MegaCli -GetPreservedCacheList -aN|-a0,1,2|-aALL
MegaCli -DiscardPreservedCache -Lx|-L0,1,2|-Lall -force -aN|-a0,1,2|-aALL
sssssssssss - It must be between eight and thirty-two
characters and contain at least one number,
one lowercase letter, one uppercase
letter and one non-alphanumeric character.
kkkkkkkkkkk - Must be less than 256 characters.
MegaCli -ShowSummary [-f filename] -aN
MegaCli -ELF -GetFeatureActivationId -aN|-a0,1,2|-aALL
MegaCli -ELF -ControllerFeatures -aN|-a0,1,2|-aALL
MegaCli -ELF -Applykey key <-val> [Preview] -aN|-a0,1,2|-aALL
MegaCli -ELF -TransferToVault -aN|-a0,1,2|-aALL
MegaCli -ELF -DeactivateTrialKey -aN|-a0,1,2|-aALL
MegaCli -ELF -ReHostInfo -aN|-a0,1,2|-aALL
MegaCli -ELF -ReHostComplete -aN|-a0,1,2|-aALL
Note: The directly connected drives can be specified as [:S]
Wildcard '?' can be used to specify the enclosure ID for the drive in the
only enclosure without direct connected device or the direct connected
drives with no enclosure in the system.
Note:[-aALL] option assumes that the parameters specified are valid
for all the Adapters.
The following options may be given at the end of any command above:
[-Silent] [-AppLogFile filename] [-NoLog] [-page[N]]
[-] is optional.
N - Number of lines per page.
Exit Code: 0x00 |
作者: David, 于 February 27th,2011
为了提高Exadata网络的高可用性，Oracle Exadata Machine 的Privite InfiniBand Network 和Client Access Network(默认，你也可以采用非bonding方式)都采用了Ethernet bonding 方式。
什么是Ethernet bonding?
Ethernet bonding顾名思义，就是把多个网卡绑定在一个虚拟的逻辑设备上(只有逻辑设备会被分配IP)上以实现网络的高可用性和负载均衡的功能。我们这里介绍Linux下的Ethernet bonding。
Linux Ethernet bonding是被集成内核里面的，Linux bonding 系统提供七种不同的bonding 配置模式：
查看全文 Exadata – Linux Ethernet bonding
|
|
最新评论