First check to see if vxconfigd is running:
# ps -ef | grep vxconfigd
If it is not running, then enter the following to start it:
# vxconfigd
If it is running, then reset it with the following command:
# vxconfigd -k
While trying to start the vxconfigd daemon, it is possible to get error messages like these: cannot open /dev/vx/config or enable volboot file not loaded. In this case, bring up vxvm manually as follows:
# vxiod set 10
# vxconfigd -m disable
# vxdctl init
# vxdctl initdmp (Use this if Dynamic Multi-pathing (DMP) certified arrays are being used.)
# vxdctl enable
v880没办法进ok prompt了
你在rsc下输入bootmode reset_nvram 把nvram参数恢复出场值，然后用reset应该屏幕会有显示。
想进ok，可以在rsc下输入break。应该能进。
如果你的系统中有vxrelocd在跑，那么这个是正常的，当有的subdisk出现问题时，vxrelocd优先使用spare disk上的空间来替代这个subdisk。如果你希望全盘替换的情况，那么要修改/etc/init.d/vxvm-recover，把默认启动的daemon改为vxsparecheck。
看CPU温度的是哪个命令?
Document ID: ID49123 Synopsis: How to find Temperature Range on Sun Blade [TM] Sun Fire[TM] systems
--------------------------------------------------------------------------------
Keyword(s):Sun Fire V880/ V480r/ V280r, Sun Blade 1000/2000 /100/150, cpu temp
Description Top
Document Body Top
The way to find out what the temperature range is on Sun Blade Desktop or a Sun Fire entry level server is to use a command.
#prtpicl -v -c temperature-sensor
This will look at the fru info on the CPU and display it to the screen.
The temps are different from system to system, and CPU to CPU.
The info in the fru id is set at manufacturing, and can varies from CPU speed to CPU type. It should not be assumed that there is a default temp for all CPUs.
Example:
# prtpicl -v -c temperature-sensor
CPU0_DIE_TEMPERATURE_SENSOR (temperature-sensor, 3a00000579)
SVC_FRU (3a000006ebTBL)
| (3a0000058dH) |
SVC_PHYSICAL_DEVICE (3a00000678TBL)
| (3a000005a1H) |
SVC_PARENT (3a000005ebTBL)
| (3a0000049dH) |
SVC_TS_OVERTEMP_LED (3a000005b8TBL)
| (3a000004e1H) |
:HighShutdownThreshold 95
:HighWarningThreshold 93
:LowShutdownThreshold -10
:LowWarningThreshold 0
:Temperature 59
:FaultInformation NO_FAULT
:State OK
:_class temperature-sensor
:name CPU0_DIE_TEMPERATURE_SENSOR
CPU1_DIE_TEMPERATURE_SENSOR (temperature-sensor, 3a00000583)
SVC_FRU (3a000006eeTBL)
| (3a00000592H) |
SVC_PHYSICAL_DEVICE (3a0000067bTBL)
| (3a000005a6H) |
SVC_PARENT (3a000005eeTBL)
| (3a000004a2H) |
SVC_TS_OVERTEMP_LED (3a000005bbTBL)
| (3a000004e1H) |
:HighShutdownThreshold 95
:HighWarningThreshold 93
:LowShutdownThreshold -10
:LowWarningThreshold 0
:Temperature 57
:FaultInformation NO_FAULT
:State OK
:_class temperature-sensor
:name CPU1_DIE_TEMPERATURE_SENSOR
From the example above:
The "Temperature 57" is the temp. that the CPU is at, at this current time.
The "HighShutdownThreshold 95" is the temp. at which the system will shut itself down.
The "HighWarningThreshold 93" is the temp. at which the system will start to send warnings out to the console.
Note that all temps are in degrees centigrade.
keywords: Sun Fire V880/ V480r/ V280r , Sun Blade 1000/2000 /100/150 , cpu temp
怎样查看系统的登陆日志
PS1="`/usr/ucb/whoami`@`hostname`:"'[$PWD]'
# history
#USER_IP=`who -u am i 2>/dev/null| awk '{print $NF}'|sed -e 's/[()]//g'`
USER_IP=`who am i |awk '{print $6}' |sed -e 's/[()]//g' 2> /dev/null`
if [ "$USER_IP" = "" ]
then
USER_IP=`hostname`
fi
if [ ! -d /tmp/.hist ]
then
mkdir /tmp/.hist
chmod 777 /tmp/.hist
fi
if [ ! -d /tmp/.hist/${LOGNAME} ]
then
mkdir /tmp/.hist/${LOGNAME}
chmod 300 /tmp/.hist/${LOGNAME}
fi
HISTSIZE=4096
export HISTSIZE
DT=`date "+%Y%m%d_%H%M%S"`
#HISTFILE="/tmp/.hist/${LOGNAME}/${USER_IP}.hist.$DT"
HISTFILE="/tmp/.hist/${LOGNAME}/`echo ${USER_IP} |sed -e 's/\./_/g'`"
touch $HISTFILE
if [ -f $HISTFILE ];then
echo "user login time `date`" >> $HISTFILE
echo "USER_IP ${USER_IP}" >> $HISTFILE
fi
chmod 600 /tmp/.hist/${LOGNAME}/*.hist* 2>/dev/null
加入到/etc/profile就可以了
详细记录了所有操作
如果是solaris9 或者10 可以用preap $PID将对应的僵死进程给杀掉。
同网段双IP的系统，向外访问时使用哪个作为源地址？
It will use the first entry of your routing table (netstat -nr) if you don't have fancy things such as ipmultipathing and load balancing setup.
可不可以在CRONTAB 里实现当文件系统利用率达到90%,就自动把里面的文件删除!
#!/bin/sh
USAGE=`df -k /data|grep /data|awk '{print $5}'|tr -d %`
[ $USAGE -ge 90 ] && rm -rf /data/*
Solaris8如何恢复到正常状态
There is a tedious method you can try, but I can NOT guarantee it will get your system back.
ok boot cdrom -s
# mount /dev/dsk/c0t0d0s0 /a
# cd /a
# mkdir ./created.files ./changed.files
# find . -ctime -2 -print (or -3, -4, depends on which day you did the installation)
# find . -mtime -2 -print
Check the files found by the above commands carefully.
Move those created during the interrupted installation to the directory /a/created.files.
For files changed by the interrupted installation, if they are needed by the system,
save a copy of them to the directory /a/changed.files,
and then open it see if you can change the content back.
Reboot the system.
Good luck on repairing your system.
光纤盘修复引导区
这可能是服务器没有将wwn number改正过来，需要人为的使用下列命令输入正确的wwn number：
{a} ok probe-fcal-all
/sbus@3,0/SUNW,socal@d,10000/sf@1,0
Port#0 received soc-status=14 loop 1 is OFFLINE
Port#0 received soc-status=14 loop 1 is OFFLINE
/sbus@3,0/SUNW,socal@d,10000/sf@0,0
Port#0 received soc-status=14 loop 0 is ONLINE
WWN 2005080020add6e8 Loopid 1
WWN 2100002037a86b1a Loopid ef
LUN 0 Disk SEAGATE ST318203FSUN18G 034A0036K429
{a} ok printenv diag-device
diag-device =/sbus@3,0/SUNW,socal@d,10000/sf@0,0/ssd@w2100002037a86b0e,0
{a} ok printenv boot-device
boot-device =/sbus@3,0/SUNW,socal@d,10000/sf@0,0/ssd@w2100002037a86b1a,0
{a} ok boot
Boot device: /sbus@3,0/SUNW,socal@d,10000/sf@0,0/ssd@w2100002037a86b0e,0 File and args:
Invalid wwn number 21000020 37a86b0e
Can't open boot device
{a} ok setenv diag-device /sbus@3,0/SUNW,socal@d,10000/sf@0,0/ssd@w2100002037a86b1a,0
diag-device = /sbus@3,0/SUNW,socal@d,10000/sf@0,0/ssd@w2100002037a86b1a,0
{a} ok printenv diag-device
diag-device = /sbus@3,0/SUNW,socal@d,10000/sf@0,0/ssd@w2100002037a86b1a,0
{a} ok boot
Boot device: /sbus@3,0/SUNW,socal@d,10000/sf@0,0/ssd@w2100002037a86b1a,0 File and args:
Loading ufs-file-system package 1.4 04 Aug 1995 13:02:54.
FCode UFS Reader 1.11 97/07/10 16:19:15.
Loading: /platform/SUNW,Ultra-Enterprise/ufsboot
Loading: /platform/sun4u/ufsboot
SunOS Release 5.7 Version Generic_106541-08 64-bit [UNIX(R) System V Release 4.0]
Copyright (c) 1983-1999, Sun Microsystems, Inc.
configuring network interfaces: hme0.
Hostname: SHSH-MAIL01.cnmobile.net
The system is coming up. Please wait.
checking ufs filesystems
Solaris使用virtual memory system, 64位连续地址空间, 包括物理内存和硬盘上的虚拟内存,提供简单memory programming model,
64位virtual memory space与实际物理内存的对应关系,由CPU上的内存控制器MMU管理, 应用无需知道, 允许应用的进程按连续的地址空间编成, 可超过物理内存大小, 一部分在较慢的硬盘上, 所有空闲内存都作为文件的buffer, 改善性能,
所以,对某个应用的进程来说,其代码段/数据段/堆栈段所分配的virtual memory 可能被影射到物理内存或硬盘上的虚拟内存(swap),就整个机器来说,你所能看到内存和swap都在用,
其中Swap space用于backing store内存pages, 如内存短缺, 则内存page页被拷贝到硬盘swap上,并释放内存, 传统Unix需要swap对应所有的内存页,即如运行的进程被分配8MB内存, 则需在swap上保留同样大小的内存空间, 尽管内存此时并未短缺,也要占用, 所以实际往往swap设置的是内存的2倍,
所以不管如何,你得内存和硬盘swap总是在用的,不会出现内存用光,而swap再用的情况,其原则是:
1. 如空闲内存小于lotsfree(1/64内存大小)时,进程堆栈开始从内存中被page out, 送回硬盘swap, 所占内存被扫描为空内存给其它进程用, 而swap上的空间被占用,而不是被保留,
2. 如空闲内存继续减小, 扫描空内存的速度加快,从100pages/s(100*8KB/s) 向8192pags/s(64MB/s)的速度变化,
3. 如空闲内存继续减小到desfree(1/2 lotsfree)时, 运行的进程不光其堆栈被page out, 其程序代码段开始被swap out, 扔回硬盘的swap上, 所占内存被扫描为空内存给其它进程用,
所以当内存短缺时, 机器会因运行的进程被公平的扔出和读入,逼近底线而越来越慢,而不会内存用光, 具体你的机器的配置可用netstat -k看, 如:
# netstat -k
...
system_pages:
physmem 63284 nalloc 11786054 nfree 11708436 nalloc_calls 5350 nfree_calls 4502
kernelbase 268435456 econtig 285212672 freemem 15428 availrmem 55955 lotsfree 977
cachefree 977 desfree 488 minfree 244 fastscan 8192 slowscan 100 nscan 0
desscan 25 pp_kernel 6089 pagesfree 15428 pageslocked 6579 pagestotal 62534
...
即对一512MB内存的服务器:
lotsfree: 977 pages, ~8MB, 1/64 physical memory
Desfree: 488 pages, ~4MB,
minfree: 244 pages, ~2MB,
“/pci@1f,0” 0 “pci”
“/pci@1f,0/pci@1,1/ide@3/sd@2,0” 2 “sd” (CD-ROM)
“/pci@1f,0/pci@1,1/ide@3/dad@0,0” 0 “dad” (disk)
“/pci@1f,0/pci@1,1/ebus@1” 0 “ebus” (extended bus)
“/pci@1f,0/pci@1,1/ebus@1/fdthree@14,3023f0” 0 “fd” (floppy disk)
“/pci@1f,0/pci@1,1/ebus@1/su@14,3062f8” 1 “su” (mouse)
“/pci@1f,0/pci@1,1/ebus@1/se@14,400000” 0 “se” (serial ports A and B)
“/pci@1f,0/pci@1,1/ebus@1/su@14,3083f8” 0 “su” (keyboard)
“/pci@1f,0/pci@1,1/ebus@1/ecpp@14,3043bc” 0 “ecpp” (extended
capability parallel port)
“/pci@1f,0/pci@1,1/ebus@1/SUNW,CS4231@14,200000” 0 “audiocs” (crystal
semiconductor)
“/pci@1f,0/pci@1,1/ebus@1/power@14,724000” 0 “power” (power management
bus)
“/pci@1f,0/pci@1,1/network@1,1” 0 “hme” (Fast-Ethernet)
“/pci@1f,0/pci@1,1/SUNW,m64B@2” 0 “m64” (color memory frame buffer)
“/pci@1f,0/pci@1” 1 “simba” (pci bus A controller)
“/options” 0 “options”
“/pseudo” 0 “pseudo”
solaris里如何锁定用户在他自己的目录里？
You need to use restricted shell. Setup user's shell as /usr/bin/rksh or /usr/lib/rsh. The side effect is that the user can't cd into the subdirectories inside his/her home directory either.
1.创建资源组:
# scrgadm -a -g rg_name -h big1 big2
要创建多个资源组命令相同，rg_name变一下就可以了
2.注册资源逻辑主机：
# scrgadm -a -L -g rg_name -l big 切记逻辑主机资源名称不能和物理主机名称相同
3.注册存储资源类型：
# scrgadm –a –t SUNW.HAStoragePlus
4.注册存储资源：
# scrgadm -a -j rs_name -g rg_name -t SUNW.HAStoragePlus \
-x GlobalDevicePaths=dg_name \ （这个资源需要拉起的磁盘组）
-x FilesystemMountPoints=/export/home/data (这个资源需要拉起的时候需要mount的文件系统，有多个的话中间用“，”隔开)
如何统计一个目录下符合某一条件的文件的总个数和总的大小？
find . -name "tcp*.c" | xargs du -k |awk '{sum +=$1} END{print sum}'
关于3800主机时间变快的问题
升级firmware或在/etc/system里设置set tod_broken=1
grep某个目录(含子目录)寻找某个特定的字符串使用方法
grep hello `find /usr/local`
请教一个恢复RAID5 的问题
(1) Disksuite有一个配置文件/etc/lvm/md.tab，手工将RAID的建立过程记录于该文件中并备份到它处
(2) OS崩溃后，重新安装OS及Disksuite
(3) 重新生成metadb
(4) 将备份的md.tab文件传至/etc/lvm下
(5) 检查/etc/lvm/md.tab文件的语法
# metainit -n -a
(6) 建立/etc/lvm/md.tab中所有的RAID
# metainit -a
(7) 完成后，可直接挂接文件系统，原数据仍然存在
( 注意事项
1) 对于MIRROR，需要手工加入sub_mir2，执行
# metattach d20 d22，
2) 对于RAID5，需用-k选项，否则会初始化RAID5，丢失数据
# metainit d10 -r dev_name1 dev_name2 dev_name3 -k -o 3
-o 3: 组成RAID5的设备数量
系统配置
目的
本文档描述了对Solaris 操作系统进行配置、监控、弱点评估已经如何使系统变得更加文档可靠的方面的内容。同时，也可以作为一个配置标准或审计基线。在系统排错过程中，对配置细节层面的详细理解和掌握是非常重要的。通过使用Jumpstart和Solaris Security Toolkit，可以自动化安装，并且方便的配置系统安全性和可靠性。
安装Solaris 8
使用如下文件系统安装Solaris 8
（见P4的表）
swap分区应该等于系统内存的两倍。使用下列命令来确定系统的内存数量：
/usr/platform/sun4u/prtdiag –v
Volume Manager的具体配置超出本文的讨论范围，不再赘述。
安装补丁集(Patch Cluster)
安装最新的推荐补丁和安全补丁是十分必要的，可以从获得。最后找到所以硬件的补丁。
# cd /tmp
# unzip 8_recommended.zip
# cd 8_recommend
# ./install_cluster
# /usr/sbin/shudown –i6 –g0 –y
配置DNS客户端
# vi /etc/nsswitch.conf
host: files dns
# vi /etc/resolv.conf
domain domain.com
nameserver 192.168.1.105
nameserver 192.168.1.106
search domain.com
配置默认路由
运行时配置：(重启后无效)
# route add net default 192.168.1.1 1
最后一个“1”指定跳数。默认路由的跳数应该设定为1，因为服务器最先找的是网卡。
重启后生效的配置：
# vi /etc/defaultroute
192.168.1.1
在/etc/hosts中添加FQAN
# vi /etc/hosts
192.168.1.101 sunsrv01.domain.com sunsrv01 loghost
在/etc/hosts中添加完全的有资格的域名(Fully qualified domain name),可以避免sendmail报错。(我的无资格的域名是未知的(主机名)；等待重试， My unqualified host name (hostname)unknown; sleeping for retry)
添加多个IP地址
5
# vi /etc/hosts
192.168.1.15 projqa
192.168.1.16 projdev
# vi hostname.eri0:1
projqa
# vi hostname.eri0:2
projdev
# ifconfig eri0:1 plumb
# ifconfig eri0:1 inet 192.168.1.15 broadcast 192.168.1.255 netmask 255.255.255.0 –
trailers
# ifconfig eri0:1 up
# ifconfig eri0:2 plumb
# ifconfig eri0:2 inet 192.168.1.16 broadcast 192.168.1.255 netmask 255.255.255.0 –
trailers
# ifconfig eri0:2 up
# ifconfig -a
lo0: flags=1000849
inet 127.0.0.1 netmask ff000000
eri0: flags=1000863
inet 192.168.1.14 netmask ffffff00 broadcast 192.168.1.255
ether 0:3:ba:b:3:f5
eri0:1: flags=1000863
inet 192.168.1.15 netmask ffffff00 broadcast 192.168.1.255
eri0:2: flags=1000863
inet 192.168.1.16 netmask ffffff00 broadcast 192.168.1.255
可以通过在服务器网卡和交换机两端都配置使用100兆全双工模式通讯，避免自动协商过程。
确定可用的网卡：
# ifconfig –a
配置服务器开机时使用：
hme:
# ndd -set /dev/hme instance 0
# ndd -set /dev/hme adv_100fdx_cap 1
# ndd -set /dev/hme adv_autoneg_cap 0
qfe:
# ndd -set /dev/qfe instance 0
# ndd -set /dev/qfe adv_100fdx_cap 1
# ndd -set /dev/qfe adv_autoneg_cap 0
eri:
# ndd -set /dev/eri instance 0
# ndd -set /dev/eri adv_100fdx_cap 1
# ndd -set /dev/eri adv_autoneg_cap 0
ce:
# ndd -set /dev/ce instance 0
# ndd -set /dev/ce link_master 0
# ndd -set /dev/ce adv_1000fdx_cap 0
# ndd -set /dev/ce adv_1000hdx_cap 0
# ndd -set /dev/ce adv_100fdx_cap 1
# ndd -set /dev/ce adv_100hdx_cap 0
# ndd -set /dev/ce adv_10fdx_cap 0
# ndd -set /dev/ce adv_10hdx_cap 0
# ndd -set /dev/ce adv_autoneg_cap 0
配置重启后生效(注意：一定要确定网卡正确安装在服务器上)
hme, qfe & eri:
# vi /etc/system (ensure there are no blank lines)
* Force hme into 100 Mbps full duplex mode
set hme:hme_adv_100fdx_cap=1
* Don't negotiate operation mode with the network hub
set hme:hme_adv_autoneg_cap=0
* Force qfe into 100 Mbps full duplex mode
set qfe:qfe_adv_100fdx_cap=1
* Don't negotiate operation mode with the network hub
set qfe:qfe_adv_autoneg_cap=0
* Force eri into 100 Mbps full duplex mode
set eri:adv_100fdx_cap=1
* Don't negotiate operation mode with the network hub
set eri:adv_autoneg_cap=0
ce:
# vi /etc/rc2.d/S99net-tune
#!/sbin/sh
# Set NIC to 100 Mbps full duplex
ndd -set /dev/ce instance 0
ndd -set /dev/ce link_master 0
ndd -set /dev/ce adv_1000fdx_cap 0
ndd -set /dev/ce adv_1000hdx_cap 0
ndd -set /dev/ce adv_100fdx_cap 1
ndd -set /dev/ce adv_100hdx_cap 0
ndd -set /dev/ce adv_10fdx_cap 0
ndd -set /dev/ce adv_10hdx_cap 0
ndd -set /dev/ce adv_autoneg_cap 0
exit 0
# chmod 700 /etc/rc2.d/S99net-tune
确认配置参数：
hme, qfe and eri:
# ifconfig -a
ce:
# netstat -k ce0 | grep link_speed
link_speed 100 link_duplex 2 link_asmpause 0 link_pause 0
link_speed - speed in Mbps
link_duplex - 1 half duplex, 2 full duplex, 0 down
请问solaris 8 下如何创建一个500G的文件系统?
newfs -i 11992 -f 8192 /dev/rdsk/*
Cannot create /var/adm/utmpx
SOLUTION SUMMARY:
With a Solaris software CD in the cdrom drive.
#1. boot cdrom -s
#2. mount /dev/dsk/c0t0d0s0 /a
#3. ls -l /a/devices/pseudo/sys*
If there is NO MATCH - this is the key that the kernel patch
install is the culprit. Proceed to step 4.
If there IS a match - then it is likely that something else
is responsible for the NO BOOT issue. For example,
/etc/vfstab was recently edited and the mount of /var is incorrect.
#4. Get the "postpatch" script from the 106541-05 directory. It might
still be on the hard drive, or it can be moved on to the system via
ftp. 106541-07 uses the identical postpatch script and it
can be used as an alternative to the -05 postpatch script.
#5. #ROOTDIR=/a
#export ROOTDIR
#chmod 755 postpatch
#./postpatch
#6. ls -l /a/devices/pseudo/sys*
should now see the devices:
sysmsg@0:msglog and sysmsg@0:sysmsg
#7. #cd /
#umount /a
reboot
Note: To ftp the postpatch script from a server on the network, just
use the ip address of that server. #ftp ip_address
If additional network configuration is needed to accomplish the ftp,
reference InfoDoc 19086 How to access the network from a "boot cdrom -s"
environment.
The postpatch script is shown here for reference:
#! /bin/sh
#
# This is for the remote console. It checks for existence
# of the new device nodes, and creates them if necessary. This
# code emulates what would otherwise occur in SUNWcsd/postinstall,
# it is a requirement that this code run before the reconfiguration
# reboot.
#
# ensures an entry is in /etc/name_to_major
if [ -f $ROOTDIR/kernel/drv/sysmsg ]; then
/usr/sbin/add_drv -n -b $ROOTDIR sysmsg
else
exit 0
fi
devnode=$ROOTDIR/devices/pseudo/sysmsg@0:sysmsg
grep sysmsg $ROOTDIR/etc/name_to_major >/dev/null 2>&1
if [ "$?" = "0" ]; then
major_sysmsg=`grep sysmsg \
$ROOTDIR/etc/name_to_major | nawk '{ print $2 }'`
else
exit -1
fi
rm -f $devnode
mknod $devnode c $major_sysmsg 0
chmod 0600 $devnode
chown root:sys $devnode
devnode=../devices/pseudo/sysmsg@0:sysmsg
devlink=sysmsg
( cd $ROOTDIR/dev ; \
rm -f $devlink ; ln -s $devnode $devlink )
devnode=$ROOTDIR/devices/pseudo/sysmsg@0:msglog
grep sysmsg $ROOTDIR/etc/name_to_major >/dev/null 2>&1
if [ "$?" = "0" ]; then
major_sysmsg=`grep sysmsg \
$ROOTDIR/etc/name_to_major | nawk '{ print $2 }'`
else
exit -1
fi
rm -f $devnode
mknod $devnode c $major_sysmsg 1
chmod 0600 $devnode
chown root:sys $devnode
devnode=../devices/pseudo/sysmsg@0:msglog
devlink=msglog
( cd $ROOTDIR/dev ; \
rm -f $devlink ; ln -s $devnode $devlink )
exit 0
APPLIES TO: Operating Systems, Operating Systems/Solaris, Operating Systems/Solaris/Solaris 7, OS Install/Boot, OS Install/Boot/System Boot, AFO Vertical Team Docs, AFO Vertical Team Docs/Install/Boot, AFO Vertical Team Docs/Kernel
ATTACHMENTS:
PS1='[${UNAME}@${PWD}]'; export PS1
sol 10 系统下怎么查看磁盘的block size
fstyp -v /dev/rdsk/cxtxdxsx |grep -i bsize
What to do when you have lost the Netra[TM] X1 LOM Password
If you do not know your lom password and are unable to log in to the lom prompt, you can telnet and login as root on the console.
If you do not know your lom password and are unable to log in to the lom prompt, and you can not log in to the box due to:
* Not knowing the IP address or the host name.
* The system is not configured to allow root logons from non-system console.
If you still remember the root password and IP address of the machine and it is configured to allow root login from non-system consoles.
1. Apply power to the system.
2. In order to get the system to boot, use the power switch on the
rear of the machine to start the automatic boot process.
3. Once the system has had a few minutes to boot to UNIX, telnet
or rlogin to the system as the root user
from another machine on the network.
4. Once logged in, edit the /platform/sun4u/kernel/drv/lom.conf
file and modify the line that reads 'serial_security=1' to read
'serial_security=0'. Write the modified file and then reboot the
machine - issue an 'init 6' or 'reboot' command.
5. As the system boots it will examine this file as part of the
boot process and will disable the security
passwords setup in the LOM processor, allowing access to the LOM
without passwords.
6. On the LOM/Console port, issue the '#.' escape sequence to
access the LOM, and use the 'usershow'
command to list the users that have been configured.
7. Use the 'userdel' command to delete
the users and their passwords.
8. The system is now configured without serial security, to issue
the 'console' command to get back to the system console.
9. Edit the /platform/sun4u/kernel/drv/lom.conf file and modify
the line that reads 'serial_security=0' to read 'serial_security=1'
to re-enable the security checks following the next system reboot.
o If you cannot remember the system root password, or the system
is not configured to allow root logons from non-system consoles, or
you do not know the IP address of the machine, you must use another
machine to overcome the problem. Locate another X1 that does not have
the security problem above, you will need to make some modifications
to this machines setup and then remove the boot drive from this
machine and temporarily place it in the problem machine.
1. Having located another X1, make sure that the following
configurations are correct :
+ The root password is known.
+ The machine is configured to allow root login from non-system
consoles. Edit the /etc/default/login file on the machine and insert
a '#' at the start of the line that reads 'CONSOLE=/dev/console'.
+ Edit the /platform/sun4u/kernel/drv/lom.conf file and modify the
line that reads 'serial_security=1' to read 'serial_security=0'.
2. Power down this machine using 'init 5'.
3. Remove the top cover of the machine and remove the Boot disk
drive.
4. Remove the boot disk drive from the problem machine.
5. Replace it with the boot disk you prepared in the other
machine.
6. Boot the machine and follow the process above from step 6.
7. Once the LOM passwords have been removed at step 7 above, you
may shut the system down and replace the original disk drive.
Keywords: netra, x1, lom, lost, password, passwords
在Solaris下如何能够比较快的将LKM文件列出来，不知道有什么比较好的方法能够实现这个要求，
find /kernel -type f
怎么配置邮件客户端?solaris做为客户端
1.remove the /etc/mail/submit.cf
2.write the mailhost to /etc/hosts, just like:
10.10.10.11 aserver mailhost
SunCluster3.1中的Quorum设备如何重置？
先reset一下看看，如果不行需要重新指定：
# scconf -c -q reset
重新指定一个新的把原来删掉即可：
# scconf -a -q globaldev=d4
# scconf -r -q globaldev=d5
或者用scsetup交互式命令指定和删除也可以！
如何拷贝SYMBOL LINK FILE
assuming the 2 new file systems are mounted on /mnt/sapmnt, /mnt/sap -
#(cd /; tar -cf - sapmnt) | ( cd /mnt; tar -xf -)
#(cd /usr; tar -cf - sap) | (cd /mnt; tar -xf -)
then, umount /sapmnt, /usr/sap, /mnt/sapmnt, /mnt/sap, and mount the 2 new file systems on /sapmnt, /usr/sap respectively
如何修改stack size?
ulimit -a
core file size (blocks) unlimited
data seg size (kbytes) unlimited
file size (blocks) unlimited
open files 1024
pipe size (512 bytes) 10
stack size (kbytes) 8192
cpu time (seconds) unlimited
max user processes 29995
virtual memory (kbytes) unlimited