After logging into the XSCF console, power on the server.
XSCF> poweron -d 0
DomainIDs to power on:00
Continue? [y|n] :y

Switch to the server console.
XSCF> console -d 0
Connect to DomainID 0?[y|n] :y

Devalias will list all devices which can be booted.
{0} ok devalias
cdrom /pci@0,600000/pci@0/pci@0/scsi@0/disk@4,0:f
net /pci@0,600000/pci@0/pci@1/pci@0/network@4
disk /pci@0,600000/pci@0/pci@0/scsi@0/disk@0
name aliases

To boot from the disk, use the boot command.
{0} ok boot disk
Boot device: /pci@0,600000/pci@0/pci@0/scsi@0/disk@0 File and args:
SunOS Release 5.10 Version Generic_141444-09 64-bit
Copyright 1983-2009 Sun Microsystems, Inc. All rights reserved
Use is subject to license terms.
Hostname: andrew_lin

Switch back to the XSCF console with
#. will bring you back to the XSCF console.

To list the default boot device use the printenv command.
ok printenv boot-device
boot-device = /pci@0,600000/pci@0/pci@8/SUNW,qlc@0/fp@0,0/disk@w50060e80058c7b10,1:a

If you wanted to change the default boot device, use the setenv boot-device command.
ok setenv boot-device device[n]

Save the changes with reset-all.
ok reset-all

The procedure to identify the path for the RDM (raw disk mapping) to LUN (disk on SAN) on Vmware ESX 4 is different from Vmware Esx 3. There are a few more steps in version 4. I will explain below how to determine the path for RDM to LUN in ESX 4.

Login to the console with root permission.

# find /vmfs/volumes -name **-rdm**
/vmfs/volumes/4c20ca1e-d32d6ed6-96cb-001e4f3fdc36/VMware1/VMware1_1-rdmp.vmdk

Find all RDM file in .vmfs/volumes. Remove -rdmp from the result and that is the path you need for the next step.

# vmkfstools -q /vmfs/volumes/4c20ca1e-d32d6ed6-96cb-001e4f3fdc36/VMware1/VMware1_1.vmdk
Disk /vmfs/volumes/4c20ca1e-d32d6ed6-96cb-001e4f3fdc36/VMware1/VMware1_1.vmdk is a Passthrough Raw Device Mapping
Maps to: vml.02000a000060060e80058c7b0000008c7b0000310b4f50454e2d56

Use the vmkfstools -q command to find the vml id of the LUN, it is vml.02000a000060060e80058c7b0000008c7b0000310b4f50454e2d56.

# esxcfg-scsidevs -u | grep vml.02000a000060060e80058c7b0000008c7b0000310b4f50454e2d56
naa.60060e80058c7b0000008c7b0000310b vml.02000a000060060e80058c7b0000008c7b0000310b4f50454e2d56

Now use the esxcfg-scsidevs command to find the Network Addressing Authority identifier (naa) for the LUN.

# esxcfg-mpath -l –device=naa.60060e80058c7b0000008c7b0000310b
fc.2001001b3232c093:2101001b3232c093-fc.50060e80058c7b55:50060e80058c7b55-naa.60060e80058c7b0000008c7b0000310b
Runtime Name: vmhba2:C0:T0:L10
Device: naa.60060e80058c7b0000008c7b0000310b
Device Display Name: HITACHI Fibre Channel Disk (naa.60060e80058c7b0000008c7b0000310b)
Adapter: vmhba2 Channel: 0 Target: 0 LUN: 10
Adapter Identifier: fc.3001001b3232c093:2101001b3232c093
Target Identifier: fc.60060e80058c7b55:50060e80058c7b55
Plugin: NMP
State: active
Transport: fc
Adapter Transport Details: WWNN: 22:01:00:1b:32:32:c0:93 WWPN: 23:01:00:1b:32:32:c0:93
Target Transport Details: WWNN: 55:06:0e:80:05:8c:7b:55 WWPN: 56:06:0e:80:05:8c:7b:55

fc.2000001b3212c093:2100001b3212c093-fc.50060e80058c7b45:50060e80058c7b45-naa.60060e80058c7b0000008c7b0000310b
Runtime Name: vmhba1:C0:T0:L10
Device: naa.60060e80058c7b0000008c7b0000310b
Device Display Name: HITACHI Fibre Channel Disk (naa.60060e80058c7b0000008c7b0000310b)
Adapter: vmhba1 Channel: 0 Target: 0 LUN: 10
Adapter Identifier: fc.3000001b3212c093:2100001b3212c093
Target Identifier: fc.60060e80058c7b45:50060e80058c7b45
Plugin: NMP
State: active
Transport: fc
Adapter Transport Details: WWNN: 22:00:00:1b:32:12:c0:93 WWPN: 23:00:00:1b:32:12:c0:93
Target Transport Details: WWNN: 55:06:0e:80:05:8c:7b:45 WWPN: 56:06:0e:80:05:8c:7b:45

The esxcfg-mpath -l command generates the detailed information for the LUN. Because there are redundant path to the LUN on the SAN, the result is listed twice with different fiber channel HBA interfaces.

Now what if your VMware ESX server is hosting many servers all with different RDMs. It would be very tedious to manually compile a report for RDM to LUN mapping. I create a script that will automatically do all the above steps and will output the result to screen or you can redirect the result to a file. This will script will search for all the RDMs and create the mappings. Below is the script and explanation of how it works.

#!/bin/bash
# Andrew Lin
# August 4, 2010
# Pay Andrew Lin lot’s of money before you
# can use this script

date
hostname

find /vmfs/volumes -name **-rdm** | sed ‘s/-rdmp.vmdk/.vmdk/g’ | sed ‘s/-rdm.vmdk/.vmdk/g’ | sed ‘s/^/vmkfstools -q /g’ >> andrew-disk-map |
chmod 645 andrew-disk-map

file=andrew-disk-map
while read line
do
$line
$line | grep vml | sed ‘s/.*to:/esxcfg-scsidevs -u | grep/g’ > andrew_lin1

chmod 755 andrew_lin1
./andrew_lin1 | sed ‘s/ .*//g’
./andrew_lin1 | sed ‘s/ .*//g’ | sed ‘s/^/esxcfg-mpath -L –device=/g’ >andrew_lin2
# rm andrew_lin1

chmod 755 andrew_lin2
./andrew_lin2
# rm andrew_lin2

echo -e “\n”
done <$file

I will explain below what the above script does.

find /vmfs/volumes -name **-rdm**
/vmfs/volumes/4c20ca1e-d32d6ed6-96cb-001e4f3fdc36/VMware1/VMware1_1-rdmp.vmdk

Search for all RDM (raw disk mapping), VMware1_1-rdmp.vmdk is found.

sed ‘s/-rdmp.vmdk/.vmdk/g’

Change the characters -rdmp.vmdk to .vmdk. The s/ means to substitute, and /g means globally apply the changes for all matches. Some RDM have the -rdmp.vmdk extension (not shown in the above example).

sed ‘s/-rdm.vmdk/.vmdk/g’

Change -rdm.vmdk to .vmdk for all matches.

sed ‘s/^/vmkfstools -q /g’

Add the command vmkfstools -q to the beginning of each line.

>> andrew-disk-map | chmod 645 andrew-disk-map

Redirect the output to the file andrew-disk-map. Change the file permission to 645 to make it executable.

Below is the result of the above command stored in andrew-disk-map.

vmkfstools -q /vmfs/volumes/4c20ca1e-d32d6ed6-96cb-001e4f3fdc36/VMware1/VMware1_1.vmdk

file=andrew-disk-map

Define the variable called file which contains the name of the file andrew-disk-map.

while read line
do
..
…
….
done <$file

The while loop will read the contents of the file defined in the variable $file (which is andrew-disk-map). The file is read one line at a time and the commands defined within the while loop are executed for each line read.

$line

Execute the line read from the file andrew-disk-map and send the output to screen.

Command
vmkfstools -q /vmfs/volumes/4c20ca1e-d32d6ed6-96cb-001e4f3fdc36/VMware1/VMware1_1.vmdk
Output
Disk /vmfs/volumes/4c20ca1e-d32d6ed6-96cb-001e4f3fdc36/VMware1/VMware1_1.vmdk is a Passthrough Raw Device Mapping
Maps to: vml.02000a000060060e80058c7b0000008c7b0000310b4f50454e2d56

$line | grep vml | sed ‘s/.*to:/esxcfg-scsidevs -u | grep/g’ > andrew_lin1

Grep will find the line that contains the characters vml, this is the unique LUN id. Replace all characters before and upto the characters to: with esxcfg-scsidevs -u | grep. The result will look like the below line which is redirected to the file andrew_lin1.

esxcfg-scsidevs -u | grep vml.02000a000060060e80058c7b0000008c7b0000310b4f50454e2d56

chmod 755 andrew_lin1

Chmod 755 will make the file andrew_lin1 executable.

./andrew_lin1 | sed ‘s/ .*//g’

Execute the file andrew_lin1. Sed ‘s/ .*//g’ will delete everything after the first space found, otherwise the output will look like the below.

Command executed (this is the content of the file andrew_lin1).
esxcfg-scsidevs -u | grep vml.02000a000060060e80058c7b0000008c7b0000310b4f50454e2d56
Output
naa.60060e80058c7b0000008c7b0000310b vml.02000a000060060e80058c7b0000008c7b0000310b4f50454e2d56

./andrew_lin1 | sed ‘s/ .*//g’ | sed ‘s/^/esxcfg-mpath -l –device=/g’ >andrew_lin2

Execute the file andrew_lin1, from the result remove everything after the LUN ID number (naa.60060e80058c7b0000008c7b0000310b). Then add the command esxcfg-mpath -L –device= in front of the LUN ID number, see below example. The output is redirected to the file andrew_lin2.
esxcfg-mpath -l –device=naa.60060e80058c7b0000008c7b0000310b

# rm andrew_lin1

You are done with file andrew_lin1 and can delete it. If you want to save the file for troubleshooting then comment out the above line with the # sign.

chmod 755 andrew_lin2

Make the file andrew_lin2 executable.

./andrew_lin2

Execute andrew_lin2. Which contains the command esxcfg-mpath -l –device=naa.60060e80058c7b0000008c7b0000310b. The output below is displayed on screen. Notice that there are redundant paths to the LUN on the SAN.

fc.2001001b3232c093:2101001b3232c093-fc.50060e80058c7b55:50060e80058c7b55-naa.60060e80058c7b0000008c7b0000310b
Runtime Name: vmhba2:C0:T0:L10
Device: naa.60060e80058c7b0000008c7b0000310b
Device Display Name: HITACHI Fibre Channel Disk (naa.60060e80058c7b0000008c7b0000310b)
Adapter: vmhba2 Channel: 0 Target: 0 LUN: 10
Adapter Identifier: fc.3001001b3232c093:2101001b3232c093
Target Identifier: fc.60060e80058c7b55:50060e80058c7b55
Plugin: NMP
State: active
Transport: fc
Adapter Transport Details: WWNN: 22:01:00:1b:32:32:c0:93 WWPN: 23:01:00:1b:32:32:c0:93
Target Transport Details: WWNN: 55:06:0e:80:05:8c:7b:55 WWPN: 56:06:0e:80:05:8c:7b:55

fc.2000001b3212c093:2100001b3212c093-fc.50060e80058c7b45:50060e80058c7b45-naa.60060e80058c7b0000008c7b0000310b
Runtime Name: vmhba1:C0:T0:L10
Device: naa.60060e80058c7b0000008c7b0000310b
Device Display Name: HITACHI Fibre Channel Disk (naa.60060e80058c7b0000008c7b0000310b)
Adapter: vmhba1 Channel: 0 Target: 0 LUN: 10
Adapter Identifier: fc.3000001b3212c093:2100001b3212c093
Target Identifier: fc.60060e80058c7b45:50060e80058c7b45
Plugin: NMP
State: active
Transport: fc
Adapter Transport Details: WWNN: 22:00:00:1b:32:12:c0:93 WWPN: 23:00:00:1b:32:12:c0:93
Target Transport Details: WWNN: 55:06:0e:80:05:8c:7b:45 WWPN: 56:06:0e:80:05:8c:7b:45

# rm andrew_lin2

Delete the file andrew_lin2 by removing the # comment.

echo -e “\n”

Enter a line space.

I will explain how to recover a Solaris 10 server from hardware replicated SAN disk. It took me sometime to figure out how to boot up from the replicated SAN LUN (disk), and many more hours to understand why the steps I applied works.

In this example I have a SUN SPARC M3000 server with two Qlogic fiber channel cards (HBA) installed in the PCI solts. The HBAs were already configured to connect to the SAN disk (LUN). This LUN contained the replicated copy of a production Slaris 10 server. The production server had two ZFS pool residing in a single LUN.

Using the Solaris 10 installation CD boot up the Sparc server into single user mode.

boot cdrom -s

The first thing you need to do is to see if the HBAs are working. The connected status indictes that communication between the server and switch is working. There are two HBAs installed for redundancy, both connected to the same LUN.

# luxadm -e port
/devices/pci@0,600000/pci@0/pci@8/SUNW,qlc@0/fp@0,0:devctl CONNECTED
/devices/pci@1,700000/pci@0/pci@0/SUNW,qlc@0/fp@0,0:devctl CONNECTED

Now you need to find out if the SAN disk is visible from the server. Even though both HBAs are connected to the same SAN disk, you will see two separate SAN disks in the results below. It just means there are two paths to the SAN.

# luxadm probe
No Network Array enclosures found in /dev/es

Found Fibre Channel device(s):
Node WWN:50060e80058c7b10 Device Type:Disk device
Logical Path:/dev/rdsk/c1t50060E80058C7B10d1s2
Node WWN:50060e80058c7b00 Device Type:Disk device
Logical Path:/dev/rdsk/c2t50060E80058C7B00d1s2

In the above example the first LUN is c1t50060E80058C7B10d1s2. This is the logical device name which is a symbolic link to the physical device name stored in the /devices directory. Logical device names contain the controller number(c2), target number (t50060E80058C7B10), disk number (d1), and slice number (s2).

The next step is to find out how the disk is partitioned, the format command will give you that information. You need this information to understand how to boot up the disk.

# format
Searching for disks…done

AVAILABLE DISK SELECTIONS:
0. c1t50060E80058C7B10d1 1066>/pci@0,600000/pci@0/pci@8/SUNW,qlc@0/fp@0,0/ssd@w50060e80058c7b10,1

1. c2t50060E80058C7B00d1 1066>/pci@1,700000/pci@0/pci@0/SUNW,qlc@0/fp@0,0/ssd@w50060e80058c7b00,1

Select the first disk 0.

Specify disk (enter its number): 0
selecting c1t50060E80058C7B10d1
[disk formatted]

FORMAT MENU:
disk – select a disk
type – select (define) a disk type
partition – select (define) a partition table
current – describe the current disk
format – format and analyze the disk
repair – repair a defective sector
label – write label to the disk
analyze – surface analysis
defect – defect list management
backup – search for backup labels
verify – read and display labels
save – save new disk/partition definitions
inquiry – show vendor, product and revision
volname – set 8-character volume name
! – execute , then return
quit

Display the labels and slices (partitions). In Solaris each slice is treated as a separate physical disk. In the below example you can tell that the disk is labeled as VTOC (Volume Table of Contents) because you can see the cylinders. VTOC is also known as SMI label. If the disk was labeled with EFI (Extensible Firmware Interface), then you would see sectors instead of cylinders. Partition 0 (slice 0) holds the operating system files, the boot disk. Please note that you cannot boot from a disk with EFI label. Slice 2 is the entire physical disk because it contains all cylinders, 0 – 65532.

format> verify

Primary label contents:

Volume name = <
ascii name =
pcyl = 65535
ncyl = 65533
acyl = 2
nhead = 15
nsect = 1066
Part Tag Flag Cylinders Size Blocks
0 root wm 0 – 3356 25.60GB (3357/0/0) 53678430
1 unassigned wm 0 0 (0/0/0) 0
2 backup wm 0 – 65532 499.66GB (65533/0/0) 1047872670
3 unassigned wm 0 0 (0/0/0) 0
4 unassigned wm 0 0 (0/0/0) 0
5 unassigned wm 0 0 (0/0/0) 0
6 unassigned wm 0 0 (0/0/0) 0
7 unassigned wm 3357 – 65532 474.07GB (62176/0/0) 994194240

Here is what we know so far, we know that the disk name is c1t50060E80058C7B10d1. Slice 0 on this disk contains the boot files. The physical path for this disk is /pci@0,600000/pci@0/pci@8/SUNW,qlc@0/fp@0,0/ssd@w50060e80058c7b10,1. Now we need to find out the physical path for Slice 0.

I know that the disk contains ZFS filesystems because it is a replica of the production disk. When a ZFS filesystem is moved to a different SPARC server it must first be imported because the hostid is different.

List the ZFS pool contained on the disk using the zpool import command. There are two ZFS pools in the below example, epool and rpool. Take a note of the status and action.

# zpool import
pool: epool
id: 16865366839830765202
state: ONLINE
status: The pool was last accessed by another system.
action: The pool can be imported using its name or numeric identifier and the ‘-f’ flag.
see: http://www.sun.com/msg/ZFS-8000-EY
config:

epool ONLINE
c2t50060E80058C7B00d1s7 ONLINE

pool: rpool
id: 10594898920105832331
state: ONLINE
status: The pool was last accessed by another system.
action: The pool can be imported using its name or numeric identifier and the ‘-f’ flag.
see: http://www.sun.com/msg/ZFS-8000-EY
config:

rpool ONLINE
c2t50060E80058C7B00d1s0 ONLINE

Import the pool with the zpool import command. The options -a will import all the ZFS pools it can find, the -f option will force the import. If you do not specify the force option, then the import may fail with the error “cannot import ‘rpool’: pool may be in use from other system, it was last accessed by server name (hostid: 123456)”. Ignore the error message about failed to create mountpoint.

# zpool import -af
cannot mount ‘/epool’: failed to create mountpoint
cannot mount ‘/rpool’: failed to create mountpoint

List the imported ZFS pools.

# zpool list
NAME SIZE USED AVAIL CAP HEALTH ALTROOT
epool 472G 260G 212G 55% ONLINE -
rpool 25.5G 5.75G 19.8G 22% ONLINE -

List the ZFS filesystems. In the example below notice the mountpoint / is mounted on the zfs filesystem rpool/ROOT/zfsboot. This is the boot partition, it resides in rpool.

# zfs list
NAME USED AVAIL REFER MOUNTPOINT
epool 260G 205G 21K /epool
rpool 7.74G 17.4G 99K /rpool
rpool/ROOT 4.74G 17.4G 21K legacy
rpool/ROOT/zfsboot 4.74G 17.4G 4.48G /
rpool/ROOT/zfsboot/var 139M 17.4G 105M /var
rpool/dump 1.00G 17.4G 1.00G -
rpool/swap 2.00G 19.4G 16K -

Change the mountpoint for rpoo/ROOT/zfsboot to /mnt so you can mount it to read the contents.

# zfs set mountpoint=/mnt rpool/ROOT/zfsboot

Confirm that the mountpoint was changed.

# zfs list
NAME USED AVAIL REFER MOUNTPOINT
epool 260G 205G 21K /epool
rpool 7.74G 17.4G 99K /rpool
rpool/ROOT 4.74G 17.4G 21K legacy
rpool/ROOT/zfsboot 4.74G 17.4G 4.48G /mnt
rpool/ROOT/zfsboot/var 139M 17.4G 105M /mnt/var
rpool/dump 1.00G 17.4G 1.00G -
rpool/swap 2.00G 19.4G 16K -

Now mount rpool/ROOT/zfsboot.

# zfs mount rpool/ROOT/zfsboot

List the logical disks.

# cd /dev/dsk
# ls
c1t50060E80058C7B10d1s0 c2t50060E80058C7B00d1s0
c1t50060E80058C7B10d1s1 c2t50060E80058C7B00d1s1
c1t50060E80058C7B10d1s2 c2t50060E80058C7B00d1s2
c1t50060E80058C7B10d1s3 c2t50060E80058C7B00d1s3
c1t50060E80058C7B10d1s4 c2t50060E80058C7B00d1s4
c1t50060E80058C7B10d1s5 c2t50060E80058C7B00d1s5
c1t50060E80058C7B10d1s6 c2t50060E80058C7B00d1s6
c1t50060E80058C7B10d1s7 c2t50060E80058C7B00d1s7

As stated earlier the physical path for the disk we are looking for is /pci@0,600000/pci@0/pci@8/SUNW,qlc@0/fp@0,0/ssd@w50060e80058c7b10,1. The boot slice is 0. We can derive from the physical path that the disk name is 50060e80058c7b10. We also know from the output of the format command that the physical disk 50060e80058c7b10 maps to the logical disk c1t50060E80058C7B10d1. Therefore we can derive that the logical boot disk is c1t50060E80058C7B10d1s0.

Now find out what physical path c1t50060E80058C7B10d1s0 is a symbolic link for and that is your complete boot path. In the below example the boot path starts at the first slash (/) right after /devices. It is /pci@0,600000/pci@0/pci@8/SUNW,qlc@0/fp@0,0/ssd@w50060e80058c7b10,1:a. You need to replace ssd@ with disk@ when entering the path into EEPROM.

# ls -l c1t50060E80058C7B10d1s0
lrwxrwxrwx 1 root root 82 Jul 5 10:21 c1t50060E80058C7B10d1s0 ->
../../devices/pci@0,600000/pci@0/pci@8/SUNW,qlc@0/fp@0,0/ssd@w50060e80058c7b10,1:a

If you have more than one ZFS pool the non root pool may not get mounted upon booting up the server, as in this example. You may get the below error.

SUNW-MSG-ID: ZFS-8000-D3, TYPE: Fault, VER: 1, SEVERITY: Major
EVENT-TIME: Mon Jul 5 11:54:14 EDT 2010
PLATFORM: SUNW,SPARC-Enterprise, CSN: PX654321, HOSTNAME: Andrew-Lin
SOURCE: zfs-diagnosis, REV: 1.0
EVENT-ID: 33e5a9f1-49ac-6ebc-f2a9-dff25dea6b86
DESC: A ZFS device failed. Refer to http://sun.com/msg/ZFS-8000-D3 for more information.
AUTO-RESPONSE: No automated response will occur.
IMPACT: Fault tolerance of the pool may be compromised.
REC-ACTION: Run ‘zpool status -x’ and replace the bad device.

http://sun.com/msg/ZFS-8000-D3fameserverq9{root}: zpool status -x
pool: epool
state: UNAVAIL
status: One or more devices could not be opened. There are insufficient
replicas for the pool to continue functioning.
action: Attach the missing device and online it using ‘zpool online’.
see: http://www.sun.com/msg/ZFS-8000-3C
scrub: none requested
config:

NAME STATE READ WRITE CKSUM
epool UNAVAIL 0 0 0 insufficient replicas
c3t60060E8005652C000000652C00002100d0s7 UNAVAIL 0 0 0 cannot open

The above error is caused by the zpool.cache file. This file contains the old paths of the disks from the previous server. The default behavior of Solaris 10 is to read the path from the zpool.cache file to speed up the boot sequence. You should delete this file and the system will recreate a fresh one during the boot up sequence.

Below are the steps to rename the zpool.cache file.

# cd /mnt/etc/zfs
# ls
zpool.cache
# mv zpool.cache zpool.cache.old

Now you need to reverse the changed you applied to the mountpoint earlier. Make sure that you change directory out of /mnt to /, otherwise the set mountpoint command will fail with the error device busy. Ignore the cannot mount ‘/’: directory is not empty message.

# zfs set mountpoint=/ rpool/ROOT/zfsboot
cannot mount ‘/’: directory is not empty
property may be set but unable to remount filesystem

Confirm that the mount points were changed.

# zfs list
NAME USED AVAIL REFER MOUNTPOINT
epool 260G 205G 21K /epool
rpool 7.74G 17.4G 99K /rpool
rpool/ROOT 4.74G 17.4G 21K legacy
rpool/ROOT/zfsboot 4.74G 17.4G 4.48G /
rpool/ROOT/zfsboot/var 139M 17.4G 105M /var
rpool/dump 1.00G 17.4G 1.00G -
rpool/swap 2.00G 19.4G 16K -

Shutdown the server.

# init 0

Now set the boot device in EEPROM.

setenv boot-device /pci@0,600000/pci@0/pci@8/SUNW,qlc@0/fp@0,0/disk@w50060e80058c7b10,1:a

The server is ready to be booted with the boot command.

{0} ok boot

List the bootable devices with the devalias command,

ok devalias
cdrom /pci@0,600000/pci@0/pci@0/scsi@0/disk@4,0:f
net /pci@0,600000/pci@0/pci@1/pci@0/network@4
disk /pci@0,600000/pci@0/pci@0/scsi@0/disk@0
name aliases

List the current boot device.

ok printenv boot-device
boot-device = disk

Change the boot device from disk to network.

ok setenv boot-device net
boot-device = net

Verify the change.

ok printenv boot-device
boot-device = net

Save the change.

ok reset-all

After the server rests, boot from he device

ok boot

Use the lsdev command to list the fiber channel cards (HBA) installed in the Aix server. Depending on the version of aix one or all of the commands below should work.

:/root > lsdev -C | grep fcs
fcs0 Available 04-08 FC Adapter
fcs1 Available 07-08 FC Adapter
fcs2 Available 0A-08 FC Adapter
fcs3 Available 0B-08 FC Adapter

OR

:/root > lscfg -vp | grep fcs
fcs2 U787B.001.DNW19B5-P1-C1-T1
FC Adapter
fcs3 U787B.001.DNW19B5-P1-C2-T1
FC Adapter
fcs0 U787B.001.DNW19B5-P1-C3-T1
FC Adapter
fcs1 U787B.001.DNW19B5-P1-C5-T1
FC Adapter

OR

itsm:/root > lsdev -Ccadapter | grep fcs
fcs0 Available 04-08 FC Adapter
fcs1 Available 07-08 FC Adapter
fcs2 Available 0A-08 FC Adapter
fcs3 Available 0B-08 FC Adapter

To find the WWN info for the Fc interface use the lscfg command. The Network Address is the WWN, e.g. Network Address………….10000000C942E65C.
The firmware level is Device Specific.(Z9)……..TS1.91A5.

:/root > lscfg -vl fcs0
fcs0 U787B.001.DNW19B5-P1-C3-T1 FC Adapter

Part Number……………..80P4543
EC Level………………..A
Serial Number……………1F4500AC78
Manufacturer…………….001F
Feature Code/Marketing ID…280B
FRU Number……………… 80P4544
Device Specific.(ZM)……..3
Network Address………….10000000C942E65C
ROS Level and ID…………02881955
Device Specific.(Z0)……..1001206D
Device Specific.(Z1)……..00000000
Device Specific.(Z2)……..00000000
Device Specific.(Z3)……..03000909
Device Specific.(Z4)……..FF801413
Device Specific.(Z5)……..02881955
Device Specific.(Z6)……..06831955
Device Specific.(Z7)……..07831955
Device Specific.(Z8)……..20000000C942E65C
Device Specific.(Z9)……..TS1.91A5
Device Specific.(ZA)……..T1D1.91A5
Device Specific.(ZB)……..T2D1.91A5
Device Specific.(YL)……..U787B.001.DNW19B5-P1-C3-T1

The command lsmcode will display the firmware and microcode level.
:/root > lsmcode -d fcs0

Below is the command to list the fileset.

:/root > lslpp -l | grep “FC Adapter”
devices.pci.77101223.com 5.3.0.51 APPLIED PCI FC Adapter (77101223)
5.3.0.50 APPLIED PCI FC Adapter (77101223)
devices.pci.77101223.rte 5.3.0.10 COMMITTED PCI FC Adapter (77101223)
devices.pci.77102224.com 5.3.0.51 APPLIED PCI-X FC Adapter (77102224)
devices.pci.77102224.diag 5.3.0.0 COMMITTED PCI-X FC Adapter (77102224)
devices.pci.77102224.rte 5.3.0.50 APPLIED PCI-X FC Adapter (77102224)
devices.pci.df1000f7.com 5.3.0.54 APPLIED Common PCI FC Adapter Device
5.3.0.50 APPLIED PCI FC Adapter Device
devices.pci.df1000f7.rte 5.3.0.30 APPLIED PCI FC Adapter Device Software
devices.pci.df1000f9.diag 5.3.0.0 COMMITTED 64-bit PCI FC Adapter Device
devices.pci.df1000f9.rte 5.3.0.30 APPLIED 64-bit PCI FC Adapter Device
devices.pci.df1000fd.rte 5.3.0.50 APPLIED 4Gb PCI-X FC Adapter Device
devices.pci.df1080f9.diag 5.3.0.0 COMMITTED PCI-X FC Adapter Device
devices.pci.df1080f9.rte 5.3.0.30 APPLIED PCI-X FC Adapter Device
devices.pci.77101223.com 5.3.0.0 COMMITTED PCI FC Adapter (77101223)
devices.pci.77102224.com 5.3.0.0 COMMITTED PCI-X FC Adapter (77102224)
devices.pci.df1000f7.com 5.3.0.54 APPLIED Common PCI FC Adapter Device
devices.pci.df1000f7.diag 5.3.0.0 COMMITTED PCI FC Adapter Device
devices.pci.df1000f7.rte 5.3.0.0 COMMITTED PCI FC Adapter Device Software

I downloaded the TFTP server for Windows from Solar Winds, it is free to use. Copy the new firmware to the default path of the TFTP server, which is c:\TFTP-Root.

Follow the instructions to upgrade via CLI below. This is an excerpt from Junipers knowledge base.

How to upgrade or downgrade ScreenOS using either the WebUI or CLI

Synopsis:

Steps to upgrade or downgrade ScreenOS from the WebUI and CLI

Problem:

Basic steps for upgrading or downgrading ScreenOS

Solution:

Below is the basic guideline for the upgrading or downgrading ScreenOS. For a complete guide, including requirements and restrictions, consult the Migration Procedure section in the ScreenOS release notes (for ScreenOS 5.3 and 5.4) or the ScreenOS Migration Guide (for ScreenOS 5.2 and earlier).

Upgrading / Downgrading from the WebUI
( click here for CLI instructions )

Perform the following steps to upgrade the firmware using the WebUI:

Save Configuration file

Caution! Before upgrading or downgrading a security device, save the existing configuration file to avoid losing any data.

Log in to the security device by opening a Web browser and then entering the Management IP address in the Address field. Log in as the root admin or an admin with read-write privileges.

Save the existing configuration:
Go to Configuration > Update > Config File, and then click Save to File
In the File Download dialog box, click Save.
Navigate to the location where you want to save the configuration file (cfg.txt), and then click Save.
Upgrading or downgrading Firmware

Go to Configuration > Update > ScreenOS/Keys and select Firmware Update.

Click Browse to navigate to the location of the firmware “xxxxx.5.0.0r10’
(where xxxx corresponds to the device model) or type the path to its location in the Load File field.

Click Apply.

Click OK to continue.
The security device restarts automatically. The upgrade or downgrade is complete when the device displays the login page in the browser.
Note: This process takes some time. DO NOT click Cancel or the upgrade /downgrade will fail. If you click Cancel and the upgrade fails, power off the device and then power it on again. Restart the upgrade procedure from step 2.

Log in to the security device. You can verify the version of the security device ScreenOS firmware in the Device Information section of the WebUI Home page.
Upgrading to the New ScreenOS Firmware

Go to Configuration > Update > ScreenOS/Keys and select Firmware Update.

Click Browse to navigate to the location of the new ScreenOS firmware or type the path to its location in the Load File field.

Click Apply.
A message box appears with information.

Click OK to continue.
The security device restarts automatically. The upgrade is complete when the device displays the login page in the browser.

Log in to the security device. You can verify the version of the security device ScreenOS firmware in the Device Information section of the WebUI Home page.

Upgrading/Downgrading from the CLI
Perform the following steps to upgrade or downgrade the firmware using the CLI:

Make sure that you have the ScreenOS firmware “xxxx.5.0.0r10” (where xxxx corresponds to the device model).

Run the TFTP server on your computer by double-clicking on the TFTP server application.

Log in to the security device using an application such as Telnet or Secure Shell (SSH) or Hyper Terminal if directly connected through the console port. Log in as the root admin or an admin with read-write privileges.

Save the existing configuration by executing the command:
save config to { flash | slot1 | tftp }…

On the security device, enter the following command:
save soft from tftp ip_addr filename to flash
where:
ip_addr is the IP address of your computer
filename is the name of the ScreenOS firmware.

When the upgrade or downgrade is complete, you must reset the security device.
Execute the reset command and enter y at the prompt to reset the device.

Wait a few minutes, and then log in to the security device again.

Use the get system command to verify the version of the security device ScreenOS firmware.

Upload the configuration file that you saved in step 3 by executing the command:
save config to { flash | slot1 | tftp }…
Note: when downgrading from major release you might have to run exec downgrade command before reset. Please check the Migration Guide for details.

Click on System – Storage – PERC 5/E Adapter (PCI Slot 1) – Connector 0 (RAID) – Enclosure – Physical Disks.

This will display all the Disk Drives in the right window.

Under the column Available RAID DISK Space, you should be able to determine if there is any unused disk. Make a note of the name of the disks that are avaiable, this would be under the column Name. Such as “Physical Disk 0.0.0″ and “Physical DISK 0.0.1″. You will need to this information when creating the RAID volume.

Go to Click on System – Storage – PERC 5/E Adapter (PCI Slot 1) – Connector 0 (RAID) – Virtual Disks. On the right screen you should see any existing virtual disks.

Click on Go To Create Virtual Disk Wizard, then click on Go To Advanced Wizard. You will be presented with the option to create Raid 0, Raid 1, Raid 5, Raid 10 and Raid 50. The options may differ depending on the firmware and type of PERC controller.

In this case I want to create a RAID 5 volume, which is striping with distributed parity. You need a minumum of 3 hard disks for Raid 5. The storage size equal to one disk is used for parity. So if you have 3 disks then the usable space is equal to the total of 2 disks.

Slect Raid 5 and click on Continue. This will display only the physical disks that are avaiable. Check all the Physical Disks that you wish to add to your virtual Disk, then click on Continue.

You can now give the virtual disk an optional name. Leave the defaults and click on Continue.

When creating virtual disk that is larger than 2 TB in size, you will be prompted with a warning message. “Please verify that your operating system, including any updates or modifications, supports a virtual disk of this size. Do you want to proceed?”. Click on OK to continue.

You will now be presented with the configuration summary. Click on Finish.

The new virtual disk should now appear in the list. Note the Device Name of the new virtual disk you just created, e.g. Windows Disk 2. You will need this information when configuring the new virtual disk in Windows Disk Management MMC. Under the progress column you will see the status of the new disk volume, this may take many hours to complete if the volume is many terra bytes large.

There are many ways to achieve this, NAT, VIP, MIP etc. In this article I will explain NAT (natting) on a Cisco PIX, ASA or router.

First you need to log onto the firewall or router. Enter en (enable) to get into the privilege mode, you will then be prompted for the password. Enter Config T to get into the configure terminal mode. You can now start confguring the network appliance.

Below is what your should see in the running config after you complete the configuration.

static (inside,outside) 172.210.10.10 11.12.13.10 netmask 255.255.255.255 0 0

The above line means that the IP address 172.210.10.10 (outside interface) is mapped to 11.12.13.10 (inside interface). Clients in the outside interface will connect to resources on 11.12.13.10 by referencing the natted (NAT) IP 172.210.10.10.

You also need to configure the access list or policy to allow traffic from the outside interface to flow into the inside interface. The access list then needs to be applied to the outside intefrace.

access-list Allowed_Traffic permit tcp host any host 172.210.10.10 eq www log

The above means that the name of the access list is Allowed_Traffic. Permit TCP traffic from any host to 172.210.10.10, only allow if service request is for www (TCP port 80), and log all traffic.

You then need to apply the access list to the outside interface.

access-group Allowed_Traffic in interface outside

22 Secure Shell, SSH
23 Telnet
80 http
443 https
161 SNMP
3668 Virtual Media Server
5900 Console Redirection
5901 Console Redirection

If you have a firewall in between you and the server, ensure that you have the above ports opened.

The DRAC module makes the life of the server administrator easy, you can remotely power cycle the server as if you were standing next to it. You can do pretty much everything as if you were standing at the server’s console.