systemA:~# lltstat -nvv
LLT node information:
Node State Link Status Address
* 0 systemA OPEN
ce4 UP 00:14:4F:44:88:51
ce10 UP 00:14:4F:67:6E:BB
1 systemB OPEN
ce4 UP 00:14:4F:67:5B:ED
ce10 DOWN 00:14:4F:44:88:1F
2020년 8월 31일 월요일
tsr log linux
Example
- To collect the system information data.
racadm supportassist collect -t Sysinfo
- To collect the filtered data.
racadm supportassist collect -t Debug –filter
- To collect the data and export to a NFS network share:
racadm supportassist collect -t SysInfo,TTYLog -l 10.94.161.103:/supportassist_share
- To collect the data and upload to the Dell support assist server.
racadm supportassist collect -t Sysinfo -upload
- To collect the data and export to a local share. This is allowed only from a remote or a local RACADM.
racadm supportassist collect -t ttylog -f tsr.zip
- To collect the data and export to a remote share as well as to the Dell support assist server.
racadm supportassist collect -t Debug -l //192.168.10.24/share -u myuser -p mypass -upload
- To export the last collected SupportAssist data, to a CIFS share
racadm supportassist exportlastcollection -l //192.168.10.24/share -u myuser -p mypass
- To export the collected SupportAssist data to a CIFS or NFS share. The default share details must be updated for this command to work.
racadm supportassist exportlastcollection
- To accept the End User License Agreement (EULA).
racadm supportassist accepteula
- To check the End User License Agreement (EULA) status.
racadm supportassist geteulastatus
- To register the iDRAC for SupportAssist features.
racadm supportassist register -pfname micheal -plname dell -pmnumber 9999988888 -panumber 8888899999 -pmailid micheal_dell@dell.com -sfname sourav -slname ganguly -smnumber 9999977777 -sanumber 7777799999 -smailid sourav_ganguly@dell.com -company dell -street1 bagmanetechpark -street2 cvramannagar -city bangalore -state karnataka -country india -zip 560093
- To upload the last collection to the Dell SupportAssist server.
racadm supportassist uploadlastcollection
- To expose the iSM installer to the host OS for the iSM installation.
racadm supportassist exposeisminstallertohostos
- To Schedule auto collection of SupportAssist data weekly.
racadm supportassist autocollectscheduler create -time 4:05am -dow sunday -rp weekly
- To schedule auto collection of the SupportAssist data monthly.
racadm supportassist autocollectscheduler create -time 7:55pm -dom 20 -rp monthly
- To schedule auto collection of the SupportAssist data quarterly.
racadm supportassist autocollectscheduler create -time 7:55am -wom 2 -dow monday -rp quarterly
- To view the auto collection data.
racadm supportassist autocollectscheduler view
- To clear the auto collection data.
racadm supportassist autocollectscheduler clear
2020년 8월 28일 금요일
2020년 6월 4일 목요일
How to use racadm to get raid rebuild percentage?
OpenManage CLI command. There is a CLI guid on the OpenManage Server Administrator support page. The command would be something like this:
omreport storage pdisk controller=0
linux 에서 tsr log 수집 방법
로그 수집
#racadm techsupreport collect -t SysInfo, TTYLog수행 대소문자 주의!!!!
진행상황 확인
racadm jobqueue view
100% 될 경우 파일로 다운
#racadm techsupreport export -f tsr_report.zip
2019년 4월 9일 화요일
Fixing Postfix permission issues on Linux
If you are receiving a message similar to…
Jan 15 22:12:36 ip-10-0-0-133 postfix/postdrop[8301]:warning: mail_queue_enter: create file maildrop/939392.8301: Permission denied
Jan 15 22:12:37 ip-10-0-0-133 postfix/postdrop[8302]:warning: mail_queue_enter: create file maildrop/8821.8302: Permission denied
Jan 15 22:12:37 ip-10-0-0-133 postfix/postdrop[8303]:warning: mail_queue_enter: create file maildrop/14290.8303: Permission denied
You probably have a permission issue with your Postfix installation. This is usually caused by a bad upgrade or maybe user error when moving or recovering mail folders.
This can easily be solved by running the following commands below as root.
/etc/init.d/postfix stop
killall -9 postdrop
chgrp -R postdrop /var/spool/postfix/public
chgrp -R postdrop /var/spool/postfix/maildrop
/usr/sbin/postfix set-permissions
postfix check
/etc/init.d/postfix start
This should work on just about any Linux distro.
2017년 7월 4일 화요일
scsi disk 삭제 방법
rhel 기준이며 잘안될때는 재기동이 짱입니다 ㅠㅠ
Procedure 1. Ensuring a Clean Device Removal
Close all users of the device and backup device data as needed.
Use umount to unmount any file systems that mounted the device.
Remove the device from any md and LVM volume using it. If the device is a member of an LVM Volume group, then it may be necessary to move data off the device using the pvmove command, then use the vgreducecommand to remove the physical volume, and (optionally) pvremove to remove the LVM metadata from the disk.
If the device uses multipathing, run multipath -l and note all the paths to the device. Afterwards, remove the multipathed device using multipath -f device.
Run blockdev –flushbufs device to flush any outstanding I/O to all paths to the device. This is particularly important for raw devices, where there is no umount or vgreduce operation to cause an I/O flush.
Remove any reference to the device's path-based name, like /dev/sd, /dev/disk/by-path or the major:minor number, in applications, scripts, or utilities on the system. This is important in ensuring that different devices added in the future will not be mistaken for the current device.
Finally, remove each path to the device from the SCSI subsystem. To do so, use the command echo 1 > /sys/block/device-name/device/delete where device-name may be sde, for example.
Another variation of this operation is echo 1 > /sys/class/scsi_device/h:c:t:l/device/delete, where h is the HBA number, c is the channel on the HBA, t is the SCSI target ID, and l is the LUN.
피드 구독하기:
글 (Atom)