0301-150 bosboot: Invalid or no boot device specified!

START SYSTEM BACKUP TO RMT 0 Mon Nov 23 16:37:49 EST 2009

rmt0 changed

/dev/ipldevice not found

 

0301-150 bosboot: Invalid or no boot device specified!

 

root@fundoo[/]: ls -l /dev/ipldevice

ls: 0653-341 The file /dev/ipldevice does not exist.

root@fundoo[/]:lslv -m hd5

hd5:N/A

LP    PP1  PV1               PP2  PV2               PP3  PV3

0001  0001 hdisk1            0001 hdisk0

root@fundoo[/]:lsvg -p rootvg

rootvg:

root@fundoo[/]:

root@fundoo[/]:ln /dev/hdisk0 /dev/ipldevice

root@fundoo[/]:bosboot -ad /dev/ipldevice

 

bosboot: Boot image is 21359 512 byte blocks.

mksysb : restore a single file

cd /
tctl -f /dev/rmt0 rewind
restore -xqd -s4 -f /dev/rmt0.1 ./etc/hosts.

Display the portion of TSM DB utilization per node

With this query you’ll create a list of all nodes, containing information from multiple tables:

– NODE_NAME = Name of the node
– TOTAL_GB = Total amount of data in use for the node, incl. COPYPOOL data (equal to q auditocc);
– TOTAL_FILES_STORED = Total amount of files in TSM stgpool for this node;
– PCT_FILE_STORED = The % of TSM DB utilization this client is responsible for, in relation to the entire TSM DB size;
– PLATFORM_NAME = Node’s platform as reported in the NODES table (q no f=d).

SELECT o.node_name as NODE_NAME, sum(cast(o.physical_mb/1024 as decimal (10,2))) as TOTAL_GB, sum(cast(o.num_files as decimal (10,0))) as TOTAL_FILES_STORED, dec(dec(sum(o.num_files))/(select dec(sum(num_files)) from occupancy)*100,7,4) as PCT_FILES_STORED, n.platform_name FROM occupancy o,nodes n WHERE o.node_name=n.node_name GROUP BY n.node_name, o.node_name, n.platform_name ORDER BY PCT_FILES_STORED DESC

 

eg

 

NODE_NAME: <>

TOTAL_GB: 146882.71

TOTAL_FILES_STORED: 103666236

PCT_FILES_STORED: 20.4574

PLATFORM_NAME: AIX

NODE_NAME: <>

TOTAL_GB: 4400.95

TOTAL_FILES_STORED: 20324052

PCT_FILES_STORED: 4.0107

PLATFORM_NAME: WinNT

EXPIRE INVENTORY BEGINNODEID=nn and ENDNODEID=nn (undocumented and unsupported parameters)

EXPIRE INVENTORY has two undocumented and unsupported parameters, BEGINNODEID=nn and ENDNODEID=nn where nn are decimal node numbers. These can be used to limit the amount of work the process does but please note, these parameters are UNSUPPORTED, you use them at your own risk.

The only really good reason to run a limited EXPIRE INVENTORY is if you’ve just deleted lots of data from a node and would like to get it deleted quickly from the database. The problem is that you need to find out the node number of the filespace you just deleted the data from.

The only way I know is to use undocumented SHOW commands. You need to start with the object number for the NODE table, then drill down the b-tree to find the Node number of the file space that you are after.
Start by using SHOW OBJDIR to find the node number of the Nodes table. This is normally 38.
Then use SHOW NODE 38 to see the top level tree structure of the NODE table.

SHOW NODE 38 

(SERVVM57)
<-    Subtree=<8344593>
  Record 9 (KeyLen=9, DataLen=4):

Then finally do a SHOW NODE number for the subtree that contains the node you are interest in.
In the SHOW NODE against the subkeys, the KEY is the NODE_NAME. Field 1 is the node number and field2 is PLATFORM_NAME.

SHOW NODE 8344593

 Key:  
->(SERVVM3V)<-
    Data: ->(00000134)(WinNT)(plus lots more fields..)

So from that you see the the client node that you are interested in, SERVVM3V has a node number of 134.
Roger Deschner has pointed out an error in the original text of this page ‘The node numbers you get out of the database with the SHOW NODE command are in hexadecimal. However, the node numbers you specify on the EXPIRE INVENTORY command must be decimal. You’ve got to convert them from hex to decimal yourself. To expire node SERVVM3V you must specify node number 308 (decimal), rather than 134 (hex)’.
So using the correct decimal number, to just expire data from that node you would use the command

EXPIRE INVENTORY BEGINNODEID=308 ENDNODEID=308

The EXPIRE INVENTORY process runs as an atomic transaction so if you need to cancel EXPIRE INVENTORY you should always use the CANCEL EXPIRATION command, as that will terminate the command cleanly and mark the transaction as complete. Next time you run the transaction, it will start up from where it left off. If you cancel with the ‘cancel process_number ‘ command or cancel using the GUI, TSM rolls back the transaction to the beginning, so next time you run the command it will start again from the beginning.

 

Ref: http://www.lascon.co.uk (nice job)

EMC LUN info gathering on AIX host

for emcdisk in $(lsdev -C -cdisk -Fname|grep hdiskpower)
do
emcsize=$(bootinfo -s $emcdisk)
echo ${emcdisk} ${emcsize}
done

figures are in MB

Hdiskpower no and size size

./emcinfo.sh | tr -s ‘ ‘ ‘;’ | cut -d’;’ -f1
./emcinfo.sh | tr -s ‘ ‘ ‘;’ | cut -d’;’ -f2

File system size –
df -mI | tr -s ‘ ‘ ‘;’ | cut -d’;’ -f6
df -mI | tr -s ‘ ‘ ‘;’ | cut -d’;’ -f3
df -mI | tr -s ‘ ‘ ‘;’ | cut -d’;’ -f4

AIX FTP Accesses to a Log File

You can do this relatively simply be doing the following:

1. Add the following line to /etc/syslog.conf.

daemon.debug /tmp/daemon.log

2. Create the log file and restart the syslog daemon.

# touch /tmp/daemon.log # refresh -s syslogd

3. Now you must modify your inetd.conf through SMIT. Using smit inetdconf you will add the -l and the -d option.

Now all of the syslog messages from ftpd and other daemons will now appear in the file /tmp/daemon.log.

Creating NMON graphs

Here’s how: (I’ve tested this with Nmon version 9f, which you can download here):

• Run nmon -f for a while. This will create nmon output files *.nmon in your current directory.
• Make sure you’ve downloaded rrdtool.
• Install rrdtool by unpacking it in /usr/local/bin.
• Make sure directory /usr/local/bin is in your $PATH: export PATH=”$PATH:/usr/local/bin”
• Create a directory for the output of the graphs: mkdir output
• Run the nmon2rrdv9 tool (found in the nmon download):
  ./nmon2rrdv9 -f [nmon output file] -d ./output -x
• In directory output an index.html and several gif files will be created. By accessing index.html in a web browser, you can view the graphs.

TSM Web admin GUI on server 5.5 / 5.4

Since TSM (IBM Backup Solution) version 5.3, the old web Admin GUI has been replaced by a servlet called the ISC console. Now, generally everyone dislikes ISC, cause it’s slow, and uses quite some resources. One can, however, restore the old admin GUI in 5.3 :

IBM has made the old gui available for download. The site contains an installation procedure as well.

It really works w/ 5.4 server and used to work very well on 5.5 at my previous site.

Register HBAs w/ CLARiiON systems

Microsoft Windows
To register the host’s HBAs with the storage system, start the Navisphere Agent as follows:
1. On the Windows host, right click My Computer and select Manage.
2. Click Services and Applications and then click Services.
3. Find EMC Navisphere Agent service.
4. If already started, stop the EMC Navisphere Agent service.
5. Start the EMC Navisphere Agent service.
AIX
To register the host’s HBAs with the storage system, on the AIX host, stop and start the Navisphere Agent. For example:

# rc.agent stop
# rc.agent start

HP-UX
To register the host’s HBAs with the storage system, on the HP-UX host, stop and start the Navisphere Agent. For example:

# /sbin/init.d/agent stop
# /sbin/init.d/agent start

Linux
To register the host’s HBAs with the storage system, on the Linux host, stop and start the Navisphere Agent. For example:

# /etc/init.d/naviagent stop
# /etc/init.d/naviagent start

NetWare
To register the host’s HBAs with the storage system, on the NetWare host, restart the Navisphere Agent. In the NetWare server console screen, enter:

sys:\emc\agent\navagent.nlm -f
sys:\emc\agent\agent.cfg

Solaris
To register the host’s HBAs with the storage system, on the Solaris host, stop and start the Navisphere Agent. For example:

# /etc/init.d/agent stop
# /etc/init.d/agent start

VMware ESX server 2.5.0 and later
To register the host’s HBAs with the storage system, on the VMware host, stop and start the Navisphere Agent. For example:

# /etc/init.d/agent stop
# /etc/init.d/agent start

Resetting an unknown root password

1. Insert the product media for the same version and level as the current installation into the appropriate drive.
2. Power on the machine.
3. When the screen of icons appears, or when you hear a double beep, press the F1 key repeatedly until the System Management Services menu appears.
4. Select Multiboot.
5. Select Install From.
6. Select the device that holds the product media and then select Install.
7. Select the AIX version icon.
8. Define your current system as the system console by pressing the F1 key and then press Enter.
9. Select the number of your preferred language and press Enter.
10. Choose Start Maintenance Mode for System Recovery by typing 3 and press Enter.
11. Select Access a Root Volume Group. A message displays explaining that you will not be able to return to the Installation menus without rebooting if you change the root volume group at this point.
12. Type 0 and press Enter.
13. Type the number of the appropriate volume group from the list and press Enter.
14. Select Access this Volume Group and start a shell by typing 1 and press Enter.
15. At the # (number sign) prompt, type the passwd command at the command line prompt to reset the root password. For example:

    # passwd
    Changing password for "root"
    root's New password: 
    Enter the new password again:

16. To write everything from the buffer to the hard disk and reboot the system, type the following:

    sync;sync;sync;reboot