| |||
| Cause | |||
| Device discovery for devices can be difficult when minimal information is available. | |||
| Answer | |||
| Device discovery on AIX. Starting with AIX 5.2 ML05 and AIX 5.3 ML01 there is an ability to log information via the alog utility for the cfg methods. Depending on the OS version and maintenance level the amount of detail that can be logged vary. One key thing is the verbosity level. If the level is high enough the SCSI id and LUN are reported as a discovered device. If an open is done on the device the SCIOSTART is used. echo "Create cfglog `date`"|alog -t cfg export CFGLOG="cmd,meth,lib,verbosity:9" cfgmgr -l alog -o -t cfg > /tmp/cfgmethod.log Send /tmp/cfgmethod.log to IBM support. To turn logging off: unset CFGLOG or exit |
My blog has moved,please visit the new site
IBM AIX/UNIX system storage administration ksh/perl scripting
Monday, April 13, 2009
Cfgmgr does not find a device
bosboot warning message
Problem:
On AIX 5.2 server, got warning message which means scary when building boot image on hdisk0.
aixserver:/root# bosboot -ad /dev/hdisk0
bosboot: Boot image is 24922 512 byte blocks.
***** ATTENTION *****
The boot image you just created might fail to boot because
the size exceeds the system limit. For information about
fixes or workarounds, see /usr/lpp/bos.sysmgt/README.
***** ATTENTION *****
aixserver:/root# oslevel -s
5200-10-06-0835
Solution:
Since the boot image is over the 12Mb line, you will see this warning.Check the system firmware level, this server is at SF240_284, which support boot image greater than 12MB. So we can ignore this warning message.
Older systems cannot handle a large boot image like this, but with the
latest system firmware and at your 5.2 ML 8 this server will boot up
fine, as you have the necessary APARs installed to boot from the larger
image.
You will still see this warning however when you run bosboot or if
mksysb runs bosboot, but you may ignore it. You may also see this on
other systems once the boot image has grown past 12Mb, such as with
adding new disks or adapters to the system.
# lsmcode
┌──────────────────────────────────────────────────────┐
│ │
│ Building Resource Database. │
│ Please stand by. │
└──────────────────────────────────────────────────────┘
DISPLAY MICROCODE LEVEL 802811
Determining Microcode levels.......
Please stand by.
DISPLAY MICROCODE LEVEL 802811
IBM,9117-570
The current permanent system firmware image is SF240_284
The current temporary system firmware image is SF240_284
The system is currently booted from the temporary firmware image.
Labels:
problem,
update boot
Subscribe to:
Posts (Atom)
Labels
- ACL (1)
- admin (2)
- AIX 5.3 (1)
- AIX 6.1 (3)
- Atape (1)
- backup (5)
- backupios (1)
- Best Practices (1)
- bosboot (1)
- cdrom (1)
- cfgmgr (1)
- commands (4)
- compatibility (1)
- console (1)
- device (2)
- dhcp (1)
- disk (1)
- DNS (2)
- Downloads (1)
- dump (1)
- Dynamic (1)
- error (1)
- errpt (1)
- ESS (1)
- etherchannel (1)
- Filesystem (7)
- firmware (2)
- Freeware (1)
- ftp (2)
- getty (1)
- GNU (1)
- HACMP (2)
- HEA (1)
- HMC (2)
- hostname (1)
- I/O (1)
- Installation (2)
- installp (2)
- IP alias (1)
- iptrace (1)
- iso (2)
- IVM.CLI (1)
- jfs (1)
- JFS to JFS2 conversion (1)
- jfs2 (2)
- kdb (1)
- kernel (1)
- LED (2)
- lifecycle (2)
- Live Partition Mobility (1)
- lofiadm (1)
- login (1)
- LPAR (1)
- lppchk (1)
- lsof (1)
- LV (1)
- lvm (3)
- memory (1)
- migration (4)
- mksysb (2)
- mkvdev (1)
- mkvgdata (1)
- mount (1)
- multibos (1)
- ndd (2)
- netstat (1)
- network (7)
- NFS (2)
- NIC (4)
- NIM (2)
- NPIV (1)
- ODM (2)
- openssh (1)
- oslevel (1)
- patching (1)
- Performance (4)
- Perl (2)
- Perl Module (2)
- permission (1)
- port (1)
- Power VM (1)
- Power5 (1)
- Power6 (1)
- printer (1)
- problem (17)
- process (4)
- RAID5 (1)
- Recovery (2)
- respawn (1)
- restore (1)
- routing (4)
- RSC (1)
- runq (1)
- savevg (1)
- scripts (4)
- SEA (1)
- security (5)
- sendmail (1)
- solaris (7)
- SSA (1)
- SSH (2)
- ssh-agent (1)
- storage (3)
- subnet (1)
- Sun Remote System Control (1)
- support (2)
- synchronize (1)
- TCPIP (5)
- telnet (2)
- time zone (1)
- topas (1)
- Total Storage (1)
- trace (2)
- tuning (1)
- uninstall (1)
- update (1)
- update boot (4)
- upgrade (3)
- users (2)
- Veritas Volume Manager (1)
- VG (1)
- VIOS (4)
- VMM (1)
- VxVM (1)
- wtmp (1)
Blog Archive
-
▼
2010
(14)
-
▼
March
(11)
- My blog has moved to aixmind.com, please visit my ...
- Command Respawning Too Rapidly From init, wtmp Fil...
- How to Apply ACL to New Files Automatically
- How to use netgroups with NFS without NIS
- mkvdev creating SEA adapter generates: 0514-040 Er...
- NIM installation and backup of the VIO server
- Backupios Fails with 0512-008 savevg
- Atape trace log files are filling my /var filesyst...
- IVM CLI Examples to set HEA Attributes on Power Sy...
- Why does the FTP option fail in my updates for HMC...
- NPIV FAQs for Vritual I/O Server Environment
-
▼
March
(11)
