Você está na página 1de 32

ASGAUR

Search
Skip to content

Home
FAQ
Books
Usage Terms

Monthly Archives: July 2009


Uncategorized

Aix: Displaying the top 10 CPU / Memory


consuming processes
July 30, 2009 2 Comments
Displaying the top 10 CPU-consuming processes
# ps aux | head -1; ps aux | sort -rn +2 | head -10

Displaying number of processors in the system


# lsdev -Cc processor

Displaying the top 10 CPU-consuming processes


# ps aux | head -1 ; ps aux | sort -rn +3 | head

Displaying the top 10 memory-consuming processes using SZ


# ps -ealf | head -1 ; ps -ealf | sort -rn +9 | head

Displaying the processes in order of being penalized


# ps -eakl | head -1 ; ps -eakl | sort -rn +5

Displaying the processes in order of priority


# ps -eakl | sort -n +6 | head

Displaying the processes in order of nice value


# ps -eakl | sort -n +7

Displaying the processes in order of time


# ps vx | head -1 ; ps vx | grep -v PID | sort -rn +3 | head -10

Displaying the processes in order of real memory use


# ps vx | head -1 ; ps vx | grep -v PID | sort -rn +6 | head -10

Displaying the processes in order of I/O


# ps vx | head -1 ; ps vx | grep -v PID | sort -rn +4 | head -10

Displaying WLM classes


# ps -a -o pid,user,class,pcpu,pmem,args

Determining the PID of wait processes


# ps vg | head -1 ; ps vg | grep -w wait

Wait processes bound to CPUs


# ps -mo THREAD -p 516,774,1032,1290
Original post blogged on b2evolution.

Uncategorized

How To: Hide title bar or URL


usingJavascript
July 29, 2009 Leave a comment
Heres the test page, testframe.html:
<html>
<head>
<meta http-equiv=Content-Type content=text/html; charset=windows-1252>
<title>Test page</title>
<script language=JavaScript>
<!
function openWindowNew( windowURL, windowName) {
var windowFeatures=width=518,height=500,toolbar=0,location=0,scrollBars

return window.open( windowURL, windowName, windowFeatures ) ;


}
//>
</script>
</head>
<body>
<a href=# onClick=newWindow =
openWindowNew(frameset.html?+escape(http://www.myserver.com), Mywindowname);
newWindow.focus(); return false>Heres the link to myserver</a>
></html>
Heres the frame page, frameset.html:
<html>
<head>
<meta http-equiv=Content-Type content=text/html; charset=windows-1252>
<title>frame page</title>
</head>
<body>
<frameset onLoad=top.content.location=location.search.substring(1) rows=100%>
<frame name=content src=about:blank>
</frameset>
</body>
</html>
Original post blogged on b2evolution.

Uncategorized

Cognos: ReportNet Installation Procedure


July 29, 2009 Leave a comment
Pre Installation Requirements
The following Softwares must be installed and running before installing and configuring
Cognos ReportNet
Database (Oracle/DB2/SQL Server) for Content Store
Web Server (IIS/Apache)
Note: This document will focus on Oracle Database and Internet Information Services (IIS) Web
Server only.
Oracle

For creation of Content store, the database must support Unicode Character set. Ensure that
Oracle is installed with a Unicode Character set.
To check whether the installed Oracle database supports Unicode Character set, type the
following SQL Select * from NLS_DATABASE_PARAMETERS;
Create a user and grant Create & Drop privileges for the content store to the user account
Ensure the user account is granted CONNECT and RESOURCE roles.
IIS
Internet Information Services should be installed and running.
Installation
The steps guide the user to install Cognos ReportNet on a single computer. This installation takes
the default path of Cognos. The components that gets installed are
1. ReportNet Server
2. Content Manager
3. Dispatcher
Note: Components can be installed in different systems. For configuration of such installations
refer Cognos Documentation.
Post Installation Configuration
The following points must be taken care of before accessing the Cognos ReportNet tools and
must follow the same order.
1. Set-up of JDBC Client for Cognos Applications to Content store.
2. Set-up database connection properties.
3. Configure Web Server
Note: This document will focus on Oracle Database and Internet Information Services (IIS) Web
Server only.
Set-up of JDBC Client for Cognos Applications to access Content store
Cognos Applications interact with Content store only through JDBC Client. Hence ensure that
proprietary JDBC client of Oracle is made available in Cognos default libraries path. Follow the
below steps to ensure the same.
1. Rename the classes12.zip file to classes12.jar file (Note: Ensure that the file extension option
in explorer window is enabled)
2. Copy the classes12.zip file from Oracle home directory and paste the same under Cognos
Default location.
Set-up of Database Connection properties

ReportNet. Hence in order for Cognos applications to work, Cognos ReportNet needs to be
configured with Content Store. The following steps guide you to configure content store using
Cognos Configuration tool.
For all installations, the database server information must be provided to ensure that ReportNet
can connect to the database to use the content store.
Note: The following steps guide to configure only for Oracle Database. For other databases
please refer Cognos manual.
1. Open Cognos Configuration from Start -> Cognos ReportNet -> Cognos Configuration
2. Right Click on Content Store under Data Access-> Content Manager and Delete.
3. Right Click, Content manager, and then click New Resource, Database. The following
window shows the same.

4. Enter the Name, Type of Database and Click OK

5. Enter the Database Server name, Port Number and Service Name.

6. Enter the User Id and Password.

7. Save the configuration

8. Stop

the services.

9. Start

the services

Configure Web Server (IIS) The following virtual directory needs to be created Cognos
Applications to run over Web.
a) Alias Name: crn

Path: crn_locationwebcontent
Permission: Read
b) Alias Name: crn/cgi-bin
Path: crn_locationcgi-bin
Permission: Execute
c) Alias Name: crn/help
Permission: Read
Note: The names of the virtual directories presented in this document are default. The names can
be changed but cgi-bin and help names CANNOT be changed and must remain the same.
Test Installation and Configuration
Test the installation by starting the services using Cognos Configuration. Once started open
browser and type the following URL http://hostname/crn
The following Cognos Portal on the browser will ensure that your installation and configuration
is correct.

Important Files to look for


The following files are important to look for in case of any configuration problems
Crnserver.log (crnlogs)

log (crnconfiguration)
Potential Problems & Solutions
trying to initialize.
Problem 1: The database does not support Unicode Character Set
Solution 1:
1. Check whether the database installed supports UTF-8 Encoding. If not migrate to UTF8 from
the current Character set.
2. Re-install database with UTF 8 Encoding
Problem 2: The database connection parameters might be wrong
Solution 2: Ensure the database parameters furnished in Content manager is correct. Test the
same through the Client of RDBMS vendor.
Cognos BI is not available
Problem: The ReportNet service is stopped.
Solution: The ReportNet services should be started. Go to Cognos configuration and start the
services.
Problem: Insufficient Privileges
Solution: Ensure that the User to connect to Content Store has the Create and Drop Privileges
and Connect and Resource Roles .

Problem: Oracle 9i tables are not getting created.


DPR-ERR-2058 The dispatcher cannot service the request at this time. The dispatcher is still
initializing

Solution: In Cognos Connection in the Content Store node, ensure the Service Name Property
(the SID) is not fully qualified.
The JDBC Driver uses the SID, not the fully qualified name.
Problem: DPR-CMI-4007 An request to perform an active content manager election failed
Solution: Delete the existing content store connection and recreate the same.
Problem: Unable to log into Cognos Connection.
DPR-ERR-2058 The dispatcher cannot service the request at this time. The dispatcher is still
initializing
Solution: In this case, the problem was that the Content Manager host and port number were
accidentally modified and the port number was incorrect.
Problem: Tables are locked.
CM-SYS-5007 Content Manager build 1.1.162.0 failed to start! Review the Content Manager
log files and then contact your system administrator or customer support. CM-CFG-5063 A
Content Manager configuration error was detected while connecting to the content store.
Solution: The tables are locked due to previous improper configuration. Solution is to drop the
tables manually, save the configuration in Content manager and restart the services.

Problem: Unable to save the configuration in the Cognos Configuration

Solution: Read the below advisory notice from Cognos.


Dear Cognos Customer or Partner:
This is a product advisory regarding the expiry of the JCE Certificate in Cognos ReportNet and
Cognos Metrics Designer (Advisory Reference: ADVCRN04_0405).
In June and updaed in july, Cognos posted a product advisory on http://support.cognos.com to
notify Cognos ReportNet and Cognos Metrics Manager customers and partners of a potential
problem caused by the expiry of the JCE certificate in Suns Java Runtime Environment (JRE).
Recommended Action(s) To eliminate the potential for failure in Cognos ReportNet or Cognos
Metrics Designer operation, we recommend that you determine if your Cognos ReportNet or
Cognos Metrics Designer installation relies on JCE version 1.2.1 and if so, download and install
the updates for the product applicable to you. Please note that Cognos will not be liable for any
loss or damages arising from the failure to implement these recommended action(s). Customers
who have a current support contract can view the full JCE product advisory and download and
install the updates using their Cognos Support Web account login.
Problem: Database configuration of schema problem

Solution: Read the below below script and make fresh schema using it.

CREATE TABLESPACE TBS_content_store


DATAFILE '/abcd04/sso432/data/content_store_df.dbf'
SIZE 2048 M
AUTOEXTEND ON
;
CREATE TEMPORARY TABLESPACE TEMP TEMPFILE
'/abcd04/sso432/data/temp01.dbf' SIZE 2048M AUTOEXTEND ON NEXT 100M MAXSIZE
10240M
TABLESPACE GROUP ''
EXTENT MANAGEMENT LOCAL UNIFORM SIZE 1M;
CREATE USER content_store
IDENTIFIED BY content_store123
DEFAULT TABLESPACE TBS_content_store
TEMPORARY TABLESPACE temp
;
grant
grant
grant
grant
grant
grant
grant
grant

create session to content_store;


connect,resource to content_store;
create table to content_store;
create view to content_store;
create synonym,create public synonym to content_store;
create procedure to content_store;
create trigger to content_store;
create sequence to content_store;

Original post blogged on b2evolution.

Uncategorized

HP-UX: How to take Ignite Backup


July 28, 2009 Leave a comment
# make_tape_recovery -AvI -a /dev/rmt/0mn -x inc_entire=vg00
-x exclude=/oradata -x exclude=/oradb
Original post blogged on b2evolution.

Uncategorized

HP-UX: How can I retrieve the system serial


number
July 28, 2009 Leave a comment
cstm is installed with the OnlineDiagnostics / Support Tools Bundle on HP-UX 9000 systems:

# echo "sc product system;info;wait;il" | cstm | grep -i "system serial"


# echo "sel path systemninfolognexit"|cstm|grep "System Serial"
# SERIAL_NUMBER=$(echo "sc product system;info;wait;il" | cstm | grep -i
"system serial" | awk -F: '{print $2}') # echo $SERIAL_NUMBER
# getconf MACHINE_SERIAL

HP-UX 11i v2 on Itanium-based systems, use the machinfo command:


# machinfo | grep "machine serial"
Original post blogged on b2evolution.

Uncategorized

Aix: How to assign a specific PVID


July 28, 2009 Leave a comment
1) BACKUP old disk critical data.
# dd if=/dev/hdisk9 of=/tmp/hdisk9.save bs=4k count=1

If something were to go wrong and the head information got damaged


use the following to RECOVER the origional PVID and head information
TO RECOVER origional PVID:
# dd if=/tmp/hdisk9.save of=/dev/hdisk9 bs=4k count=1

2) Find the origional PVID. This might be seen with lspv importvg, or
varyonvg. Our example origional PVID is 0012a3e42bc908f3
# lqueryvg -Atp /dev/hdisk9
...
Physical: 0012a3e42bc908f3 2 0
00ffffffc9cc5f99 1 0
...

3) Verify that the disk sees an invalid PVID. The first 2 data fields
of offset 80 contain the PVID.
# lquerypv -h /dev/hdisk9 80 10
00000080 00001155 583CD4B0 00000000 00000000 |...UX<..........|
^^^^^^PVID^^^^^^^

4) Translate the ORIGIONAL PVID into the octal version. Take every 2
digits of the hex PVID and translate it to octal. This can be done
by hand, calculator, script, or web page.
00012a3e42bc908f3 -> 00 12 a3 e4 2b c9 08 f3
Octal version -> 000 022 243 344 053 311 010 363

5) Write the binary version of the PVID to a file by using the octal
values. Each octal char is lead with a backslash-Zero . Do
not use spaces or any other characters except for the final c to
keep from issuing a hard return.
# echo "000022243344053311010363c" >/tmp/oldpvid

6) Verify that the binary pvid was written correctly. The origional
hex PVID should be seen AND the final address should be 0000010
If EITHER of these is incorrect, try again, make sure there are no
spaces in the echo and the echo ends with a c.
# od -x /tmp/oldpvid
0000000 0012 a3e4 2bc9 08f3
0000010

7) Restore the PVID to the disk. You sould see 8 records in and out.
If there are more or less, restore the origional 4K block by using
the recovery method in step 1.
# cat /tmp/oldpvid | dd of=/dev/hdisk9 bs=1 seek=128
8+0 records in.
8+0 records out.

8) Verify that the PVID was written correctly


#lquerypv -h /dev/hdisk9 80 10
00000080 0012A3E4 2BC908F3 00000000 00000000 |....+...........|

9) Reconfigure the disk definitions on all systems attaching to that disk.


The ODM information for that drive will NOT be updated until the
disk is removed and reconfigured. Until that reconfigure commands
like `lspv` will still be incorrect.
Original post blogged on b2evolution.

Solaris

Solaris: How to Enable Native MPxIO fo


EMC / HP / IBM / NETAPP
July 21, 2009 Leave a comment
To enable MPxIO for storage devices, the appropriate information for device-type-scsioptionslist need to be added in the /kernel/drv/scsi_vhci.conf file.
1. Use a text editor to change the configuration file. For example:

# vi /kernel/drv/scsi_vhci.conf

2. For Solaris 8 and 9 perform the following steps:


a. Change the mpxio-disable parameter to the following:
mpxio-disable="no";

b. Verify that the load-balance and auto-failback parameters are set to the following values(the
default setting may vary depending on the patch level / OS version):
load-balance="none";
auto-failback="disable";

c. Add the following lines to cover all HP arrays:


device-type-scsi-options-list =
"HP HSV101", "symmetric-option",
"COMPAQ HSV111", "symmetric-option",
"HP HSV2", "symmetric-option",
"HP OPEN", "symmetric-option";
symmetric-option = 0x1000000;

NOTE:
Enter six spaces after HP and two spaces after COMPAQ.
3. For Solaris 10 (patch 118833-24 for SPARC, patch 118855-19 for x86), the scsi_vhci driver is
capable of detecting Asymmetric Logical Unit Access (ALUA) compliant devices advertised in
the Target Port Group Support (TPGS) field. The EVA 4000/6000/8000 and the EVA 3000/5000
V4 are ALUA compliant arrays. Add the following lines to cover all HP arrays:
device-type-scsi-options-list =
"HP OPEN", "symmetric-option";
symmetric-option = 0x1000000;NOTE:

Enter six spaces after HP.


4. Depending on the Solaris version, select one of the following options:
a. For Solaris 8 or 9run a reconfiguration reboot in order to activate the changes:
# reboot -- -r

b. For Solaris 10 (SPARC)run the stmsboot command and confirm the reboot:
# stmsboot e

c. For Solaris 10 (x86)reboot the system to load the new definition if you are configuring for
XP. Configuring for EVA does not require a reboot since definition has already been configured.
Original post blogged on b2evolution.

Uncategorized

Aix: Change Time Zone


July 20, 2009 Leave a comment
Stop xntp service if your server is an ntp client.
# stopsrc -s xntpd

Change time zone to IST CUT +5:30 using command

# chtz IST-5:30

Login/logout. nullify your drift file after taking a backup


# > /etc/ntp.drift

Set correct time using


# smitty date

Restart xntpd
# startsrc -s xntpd
Original post blogged on b2evolution.

Uncategorized

Zoning via CLI on Brocade switch


July 20, 2009 Leave a comment
Step by Step Procedure of Zoning via Cli.
1.Create a Zone Alias using AliCreate
SW0:admin> alicreate "SUNX4150_HBA0"

2.Add member to Alias using Aliadd


SW0:admin> aliadd "SUNX4150_HBA0","21:00:00:1b:32:13:a8:9f"

3.Create a Zone using ZoneCreate


SW0:admin> zonecreate "CX_424_SPB4_SUNX4150_HBA0"

4. Add membet to Zone using ZoneAdd


SW0:admin> zoneadd "CX_424_SPB4_SUNX4150_HBA0","CX_424_SPB4"

5.Add a Zone to Zone configuration CfgAdd.


SW0:admin> cfgadd "SAN_U2_SW0_Config","CX_424_SPB4_SUNX4150_HBA0"

6.Save the Configuration using CfgSave.


SW0:admin> cfgsave

7.Enable the Configuration using CfgEnable.


SW0:admin> cfgenable "SAN_U2_SW0_Config"

Note : Always use single initiator Zone which typically include one storage and one host wwpn.
Original post blogged on b2evolution.

Uncategorized

Sun StorEdge 3510 configuration


July 17, 2009 Leave a comment
root@Sun440 # sccli
sccli: selected device /dev/rdsk/c4t40d0s2 [SUN StorEdge 3510 SN#04D208]
sccli>

usage: sccli [options] device [command]


Valid options:
-d disk, disk=cXtYdZ
select LVD single-bus JBOD enclosure containing specified disk
-h, help, usage
display valid commands
-l, list
display a list of attached StorEdge 3000 Family devices
-n, no
assume a no response to any prompts
-o, oob
use an out-of-band (network) connection to the specified device
-v, version
display program version information
-w <password>, password <password>
specify the password for the array controller
-y, yes
assume a yes response to any prompts
Valid commands:abort clone <disk-dest>
abort the clone operation of destinate disk
abort create <ld>
abort offline creating logical drive
abort expand <ld>
abort offline expanding logical drive
abort media-check [<ld-list>] [<disk-list>]
abort disk(s) checking media
abort parity-check <ld>
abort logical drive check parity
abort rebuild <ld>
abort rebuilding logical drive
about

display program version and copyright info


add disk <ld> <disk-list>
add disks to logical drive
check media <ld> [<priority>][continuous]
check media on all member disks of specified LD
check parity <ld> [check-only] [verbose]
check parity on specified logical drive
clear events
clear the event log
clone <source-disk> <dest-disk>
copy a drive in ld and replace upon completion
configure channel <ch> {host|drive|RCCOM|DRV+RCC} [{pid|sid} <target-list>] [--reset]
configure a host or drive channel
configure global-spare <disk>
configure a disk as a global spare
configure local-spare <disk> <logical-drive>
configure a disk as a local spare for a specific logical drive
configure network-interface lan0 [options]
set network interface parameters
configure partition <partition-id> [<size> | delete]
configure a logical drive/volume partition of the specified size
create host-wwn-name <wwn> <name> [{head |tail}]
assign a symbolic name to a host WWPN
create logical-drive <raid-level> <disk-list> [<options>]
create a logical disk device
create logical-volume <ld-list> [primary|secondary] [write-back|write-through]
create a logical volume over the specified LDs
delete host-wwn-name [<wwn> | <name>]
delete a Host-ID/WWN name assignment
delete logical-drive <ld-list>
delete one or more logical drives
delete logical-volume <lv-list>
delete one or more logical volumes
download controller-configuration [-b|--build] <file>
download array controller binary configuration
download controller-firmware [--reset] <firmware> [<bootrecord>]
download array controller firmware (optionally w/ hard reset)
download disk-firmware <filename> <product-id>
download disk drive firmware to internal drives
download nvram [-r] <file>
download array controller binary nvram
download pld-hardware <filename>
download enclosure PLD hardware
download safte-firmware <filename>
download enclosure SAFTE firmware
download sata-path-controller-firmware <file>

download sata path controller firmware


download sata-router-firmware [-r|--reset] <file>
download sata router firmware
download ses-firmware <filename>
download enclosure SES firmware
exit
exit the program
expand {<ld>|<lv>} <size> [online|offline]
expand a logical drive or logical volume
fail {primary|secondary}
fail a controller in a redundant controller pair
help
display help for commands
map <partition> <ch>.<tgt>.<lun> [<wwpn> | <host-id>]
map an LD or LV partition to a host channel/target/lun
mute
silence the enclosure alarm
password <word>
specifies the array controller password
quit
exit the program
rebuild <ld>
rebuild a logical drive
reset controller
reset the array controller
reset nvram
restore nvram to factory defaults
scan disk <disk-list>
scan SCSI drives
select
specify a storage device to monitor or configure
set auto-write-through-trigger <param> <value>
set peripheral device configuration
set cache-parameters [<mode>] [<optimization>] [sync-period <s>]
set controller cache parameters
set controller-date <month> <day> <HH:MM:SS> [[cc]yy] [TimeZone]
set controller current date and time
set controller-name <string>
set the controller name
set controller-password <string>
set the controller password
set disk-array <param> <value>
set disk array parameters
set drive-parameters <param> <value>
set drive-side interface parameters
set host-parameters <param> <value>

set host channel parameters


set inter-controller-link {upper|lower} channel <ch> [dis]connected
enable/disable per-channel inter-controller-link
set led disk <ch>.<id> { on | off }
set led state for drive slot in RAID enclosure
set led disk <diskname> { on | off }
set led state for drive in JBOD enclosure
set led slot <slot> { on | off }
set led state for slot in specified JBOD enclosure
set logical-drive <ld> assignment {primary|secondary}
change the logical drive cache policy
set logical-drive <ld> write-policy {write-back|write-through|default}
change the logical drive cache policy
set logical-drive <ld> status good
change failed NRAID/RAID 0 logical drive status to good
set logical-drive <ld> status degraded
change failed RAID 1/3/5 logical drive status to degraded
set logical-volume <lv> <param> <value>
set a logical volume
set protocol inactivity-timeout <s>
set telnet inactivity timeout period
set protocol <protocol-name> { enabled | disabled }
set network protocol status
set rs232-configuration <port> <speed>
set the RS232 interface baud rate
set unique-identifier <value>
set the subsystems 5-digit hexadecimal serial number
show access-mode
display the access mode
show auto-write-through-trigger
display peripheral device configuration
show battery-status [-u | --update]
display status of backup battery
show bypass device ses-channel <ch> loop <loopa|loopb>
displays the target IDs on a specified loop that are currently bypassed
show bypass sfp ses-channel <ch> loop <loopa|loopb>
displays the target IDs on a specified loop that are currently bypassed
show bypass raid
displays raid drive channel bypass status
show cache-parameters
display cache policy
show channels
display channel configuration
show clone
display the status of disk(s) cloning
show configuration [--xml | -x] [<filename>]

display the devices configuration or save to file


show controller-date
display the controller date and time
show controller-name
display controller name
show disks
display info for array disks.
show disk-array
display the disk array parameters
show drive-parameters
display drive parameters
show enclosure-status
display the status of internal chassis components
show events [last <n>] [-v | --verbose]
display the controller event log.
show frus
display FRU-ID information
show host-parameters
display host i/o parameters
show host-wwn-names
display host-wwn/name list
show inquiry-data
display SCSI INQUIRY data for selected device.
show inter-controller-link {upper|lower} channel <ch>
display status of inter-controller link on specified channel
show ip-address
display the controllers IP network address
show led-status disk <ch>.<id>
show led state for drive slot in RAID enclosure
show led-status disk <diskname>
show led state for drive in JBOD enclosure
show led-status slot <slot>
show led state for slot in specified JBOD enclosure
show logical-drives [<logical-drive-list>]
display logical drives
show logical-volumes [<logical-volume-list>]
display logical volumes
show loop-map channel <ch>
display the fibre channel loop positional map for a given channel
show lun-maps
display lun maps for host channels
show media-check
display the status of disk(s) checking media
show network-parameters
display controller network parameters
show partitions [ { logical-volume <lv> | logical-drive <ld> }]

display partitions of logical drives or logical volumes


show peripheral-device-status
display peripheral device status
show persistent-events [from <date>] [to <date>]
display all or a set of persistent event log within a certain time
show port-wwns
display host channel FC Port Name WWNs
show protocol
display all network protocols information
show redundancy-mode
display redundancy status
show redundant-controller-configuration
display redundant controller configuration
show rs232-configuration
display serial port configuration
show safte-devices
display information of SAF-TE devices
show sata-mux
show sata mux board information on all drives
show sata-router
show all sata routers connected to specified device
show ses-devices
display status of SES devices
show shutdown-status
display controller shutdown status
show stripe-size-list [raid-level]
display valid stripe size list for specified raid level
show unique-identifier
display subsystem 5-digit unique identifier
shutdown controller
shut down controller (prepare for power off)
shutdown logical-drive <ld>
shut down (force offline) a logical drive
unconfigure {local-spare|global-spare} <disk> [<logical-drive>]
unconfigure a local or global spare drive
unfail
restore (deassert) a failed controller
unmap partition <ch>.<id>.<lun> [ <wwpn> | <host-wwn-name> ]
unmap the specified partition LUN for all (or one) host(s)
unmap partition <partition-id> [<channel>]
unmap a partition from all (or just specified) channel(s)
upload controller-configuration <file>
upload array controller binary configuration
upload nvram <file>

Você também pode gostar