[root@odcsxldm03 ~]# cfgadm -al -o show_SCSI_LUN | grep

c8::22120002ac00c375,400
disk
connected
c8::22120002ac00c375,401
disk
connected
c8::22120002ac00c375,402
disk
connected
c8::22120002ac00c375,403
disk
connected
c10::25710002ac00c375,400
disk
connected
c10::25710002ac00c375,401
disk
connected
c10::25710002ac00c375,402
disk
connected
c10::25710002ac00c375,403
disk
connected
c12::26120002ac00c375,400
disk
connected
c12::26120002ac00c375,401
disk
connected
c12::26120002ac00c375,402
disk
connected
c12::26120002ac00c375,403
disk
connected
c14::23110002ac00c375,400
disk
connected
c14::23110002ac00c375,401
disk
connected
c14::23110002ac00c375,402
disk
connected
c14::23110002ac00c375,403
disk
connected
c16::24720002ac00c375,400
disk
connected
c16::24720002ac00c375,401
disk
connected
c16::24720002ac00c375,402
disk
connected
c16::24720002ac00c375,403
disk
connected
c20::27110002ac00c375,400
disk
connected
c20::27110002ac00c375,401
disk
connected
c20::27110002ac00c375,402
disk
connected
c20::27110002ac00c375,403
disk
connected

-i "failing"
configured
configured
configured
configured
configured
configured
configured
configured
configured
configured
configured
configured
configured
configured
configured
configured
configured
configured
configured
configured
configured
configured
configured
configured

failing
failing
failing
failing
failing
failing
failing
failing
failing
failing
failing
failing
failing
failing
failing
failing
failing
failing
failing
failing
failing
failing
failing
failing

2215. c20t27110002AC00C375d400 <drive not available>

/pci@480/pci@1/pci@0/pci@a/SUNW,emlxs@0/fp@0,0/ssd@w27110002ac00c375,1
90
2216. c20t27110002AC00C375d401 <drive not available>
/pci@480/pci@1/pci@0/pci@a/SUNW,emlxs@0/fp@0,0/ssd@w27110002ac00c375,1
91
2217. c20t27110002AC00C375d402 <drive not available>
/pci@480/pci@1/pci@0/pci@a/SUNW,emlxs@0/fp@0,0/ssd@w27110002ac00c375,1
92
2218. c20t27110002AC00C375d403 <drive not available>
/pci@480/pci@1/pci@0/pci@a/SUNW,emlxs@0/fp@0,0/ssd@w27110002ac00c375,1
93
- boot IP is the original address on a network interface even when the
cluster is down
- service IP is a movable IP that will be added to a network interface when
a resource group becomes online. Clients normally should connect to service
IP. If a resource group fails over to another node, service IP will be moved
there
- persistent IP comes to life when cluster is up, but it does not move to
other nodes. As the name implies, it persists to remain on the node it
should be. Persistent IPs are usually defined for maintenance purpose by
HACMP admin.

Persistent IP is a node bound IP configured as an alias to network

interface. If one of the interface fails it gets configured on other
interface. This way node can still be accessed using this IP even if one of
the network interface fails. So it used for administration of nodes in HACMP
cluster.

HOTS documents to be reviewed by operation team for server/DB handover

HOTS documents to be shared with operations team with their access on the server
s
Testing is not required since HOTS documentation will be reviewed
HOTS documents are attached