Sponsored Content
Full Discussion: V880 and T3 array issue
Operating Systems Solaris V880 and T3 array issue Post 302242178 by mjl927 on Wednesday 1st of October 2008 10:10:44 AM
Old 10-01-2008
V880 and T3 array issue

We're trying to install a third T3 array onto our V880. The other two T3's are connected to a qlogic fibre card. We can see this connection fine when we do a luxadm probe -p command. The full device paths are shown etc. ie: the first T3's logical name is c2t1d0 and the second one is c3t1d0.

For the third T3 array we installed another qlogic card. When we booted up the server though, the new cards device path can be seen however it will not complete the path down to the array. We cannot get the new array to appear on a CxTxDx logical path. We've tried reconfigure reboots and running devfsadm several times.

Doing a cfgadm -al allows us to see that the first two arrays show up on C2 and C3 as type disk. The new card shows up with a connection on C4 but the type shows up as unknown. It seems that we need to somehow get this connection to appear as disk.

We're pretty sure that the card, the cables and the array came from a working situation so I'm hesitant at this point to call any of these things "bad" yet. Any suggestions are welcome.
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Dynamic Array Issue

Could one of you, please, provide some input regarding my problem below and it is as follows: I have 2 files that I need to make sure are identical before processing: First, I sort both files Second, I do a diff file1 file2 > File 3 This provides me with the difference. Now, I need to... (6 Replies)
Discussion started by: ddedic
6 Replies

2. Solaris

T3 Disc Array Connected to V880

Hello, I have a T3 array connected to a V880 running Solaris 9. There are two volumes currently configured: v1 and v2. There are two file systems on the box: /a1 and /a2. I'm getting ready to re-build volume v1 to add a hot spare. But because I did not set the array up originally I want... (1 Reply)
Discussion started by: agcodba
1 Replies

3. Shell Programming and Scripting

Scripting array issue

Hi guys, I'm a scripting noob in need of some help :) I am creating a script that checks the filesystems and will alert based upon if the percent full is greater than the threshold set. The problem that I am having is that when I set the 'filesystem' variable, all of the output is treated as... (12 Replies)
Discussion started by: tank126
12 Replies

4. Shell Programming and Scripting

Array usage issue with AWk

Hi friends, I m trying to write small script in awk alone. And I have tried below logic for one of my automation - taking the first column of the file in array and will read in for loop for each time when i grep the array value in the same file I should get complete output whichever is matching... (3 Replies)
Discussion started by: Shahul
3 Replies

5. Shell Programming and Scripting

Issue with array in shell

So i have used arrays for a while now but I just notice in one of my arrays when using an array with 9+ items in it that after running a for loop on the array it was replacing the first array with what ever was last and I cant figure out why. Here is my code. #!/bin/bash vm=( 0 1 2 3 4 5 6... (3 Replies)
Discussion started by: snptuning
3 Replies

6. Programming

Javascript issue: array.push

I have a code snippet here that is supposed to vary values of certain parameter values: <script type="text/javascript"> // dynamic array of which its ultimate size is unknown // an array of arrays, each consisting of one variation var variations = ; // parameters of how to create a... (0 Replies)
Discussion started by: figaro
0 Replies

7. Shell Programming and Scripting

Array Issue In Bash

Hi, I have the following code which is giving error mentioned below. Please can you support on this. Also suggest how can we access all the items against single vasservicename in circlename array,i.e, vasservicename say MTSTV will be available to all circles which are mentioned in the array... (2 Replies)
Discussion started by: siramitsharma
2 Replies

8. Shell Programming and Scripting

Issue with the incorrect number of array elements

Hello , I have a file : RestartSession.txt with the below contents : Backup p203pcrw01_OS_Weekly Failed full 10/11/2015 10:00:07 PM 1444572007 10/11/2015 10:26:23 PM 1444573583 0:00 0:26 18.76 1 08 0 0 0 2 2 180668 ... (4 Replies)
Discussion started by: rahul2662
4 Replies

9. Linux

Issue in inserting null string in array

I am getting some values from a file and putting them in an array..but the null strings are not getting passed to the array. So during printing the elements ,the null string is not showing in the output. during array size calculation it is also excluding null.Please let me know how to do it. # cat... (2 Replies)
Discussion started by: millan
2 Replies

10. Shell Programming and Scripting

awk array next issue

Hi, Here's an example of what I my issue, a file list.txt, which looks like: a b c d e I have been trying to use the following code to simply print the list using awk and next: awk 'FNR==NR{a=$1;next}{print a}' list.txt this give no output, even though I would expect it to type out... (5 Replies)
Discussion started by: hexy
5 Replies
sasmgr(1M)																sasmgr(1M)

NAME
sasmgr - utility to manage HP-UX Serial Attached SCSI (SAS) Mass Storage I/O cards / HBAs SYNOPSIS
lun_dsf} phy_id} phy_id} sasaddr} rvol_id | lun_dsf} lun_dsf} phy_id} phy_id} offset} sasaddr} phy_id} phy_id} sasaddr} DESCRIPTION
is a common diagnostic tool used for all Serial Attached SCSI (SAS) I/O cards / Host Bus Adapters (HBAs). requires the use of a device file to indicate the interface over which the requested command needs to be performed. Options recognizes the following command-line options: Suppresses the warning messages and continues executing the command. Provides a brief description of what the command does. Displays information for persistent device files (see intro(7)). If the command also displays hardware path information, then it shows the hardware path corresponding to the persistent device file. For example, if you use this option with the command and the and qualifiers, will print information for the persistent device files and display the corresponding lun hardware paths. Describes the command's qualifiers. A command is defined by a set of qualifiers which must be specified after the command name. Each qualifier is proceeded by the option. Some qualifiers can take one or more values and are given as ={x | y} where qualifier_name can take either the value x or y. Provides verbose information. For example, if you use this option with the command and qualifiers and will print additional header information. Commands recognizes the following commands. A command is defined by a set of qualifiers. Qualifiers are specified with the option. All keywords are case-sensitive. One of the following sets of qualifiers must be specified with the command: This set of qualifiers is used to create a RAID volume with the specified RAID level, volume size and physical disks. The value specified for the qualifier determines the RAID level for the volume. For example, specifies that a RAID1 volume should be created. The qualifier defines or specifies the enclosure and bay of each physical disk of the RAID volume. If the physical disks in a RAID volume are different sizes, then some disk space will be wasted. Volume expansion is not supported; once a volume has been created, its size cannot be increased. If the qualifier is not specified, then the volume is created with a maximum possible size based on the size of the physical disks specified. If the qualifier is not specified, then the default of 20% will be used for the volume. If the option is not specified, displays a warning message before continuing the command. Otherwise, it suppresses the warning and executes the command. This command requires superuser privileges. Refer to the section below. This set of qualifiers is used to add a global spare disk. The global spare disk is used whenever a physical disk in any RAID volume on the Core I/O card / HBA fails. The qual- ifier defines or specifies the enclosure and bay of the global spare disk. The size of the disk specified should be greater than the size of at least one of the physical disks in the volume. If the option is not specified, displays a warning message before continuing the command. Otherwise, it suppresses the warning message and continues executing the command. This command requires superuser privileges. Refer to the section below. The following qualifier must be specified with the command: Resets the specified target device. This is a destructive operation. If the option is not specified with this command, displays a warning message before continuing. Otherwise, it sup- presses the warning message and executes the command. When the command is run without qualifiers, it clears statistics of the SAS I/O card / HBA represented by device_file. The following qualifiers are specified with the command: Clears all statistics for the SAS I/O card / HBA, all PHYs, all ports, and all targets. Clears statistics for all PHYs or a specific PHY. Clears statistics for a port to which the specified PHY belongs to or clears statistics for all ports. Clears statistics for a specific target or all targets. One of the following sets of qualifiers must be specified with the command: This set of qualifiers is used to delete the RAID volume given by the volume ID. The volume ID can be obtained from the command using the qualifier. If a volume ID of is specified, then all the RAID volumes will be deleted. If the option is not specified, displays a warning message before continuing the command. Otherwise, it suppresses the warning message and continues executing the command. This command requires superuser privileges. Refer to the section below. This set of qualifiers is used to delete the Core I/O card / HBA spare disk. If the option is not specified, displays a warning message before continuing the command. Otherwise, it suppresses the warning message and continues executing the command. This command requires superuser privileges. Refer to the section below. Disables the SAS I/O card / HBA. This is a destructive operation. The SAS I/O card / HBA will become offline, all current I/Os will be aborted, and new I/Os will fail. An enable operation must be performed in order to bring the SAS I/O card / HBA back online. If the option is not specified with this command, displays a warning message before continuing. Otherwise, it suppresses the warning message and executes the command. The following qualifiers must be specified with the command: Updates the firmware on a SAS disk. The command will update disk firmware for regular physical disks, as well as those that are part of a RAID volume. The qualifier takes the name of the file containing the new disk firmware. The qualifier takes the enclosure and bay of the disk for which the firmware update is to be done. If the option is not specified, displays a warning message before continuing the command. Otherwise, it suppresses the warning message and continues executing the command. Updates the firmware on the specified enclosure. The qualifier takes the name of the file containing the new firmware. The qualifier takes the enclosure device file for which the firmware update is to be done. If the option is not specified, displays a warning message before continuing the command. Otherwise, it suppresses the warning message and continues executing the command. Updates the firmware on the specified HBA. The qualifier takes the name of the file containing the new firmware. If the option is not specified, displays a warning message before continuing the command. Otherwise, it suppresses the warning message and continues executing the command. This command requires superuser privileges. Refer to the section below. NOTE: If the firmware is being downgraded to a lower version, an incompatible older version of the firmware may get rejected. This typically happens if the downgraded version of firmware is very old compared to the current one on the card. Enables the SAS I/O card / HBA and brings it back online. This command causes the driver to initialize the SAS I/O card / HBA. When the command is run without qualifiers, it returns information about the SAS I/O card / HBA represented by device_file. The following qualifiers are specified with the command: Shows hardware path and SAS address information for a specific lun or all luns. If the option and the qualifier are specified with this command, then it displays persistent device file information. Shows lun location information for the lun specified with the qualifier. If the option and the qualifier are specified with this command, then it displays persistent device file information with the lun location information. Shows PCI ID information for the SAS I/O card / HBA. Shows information about all PHYs or a specific PHY. Shows information about a port to which the specified PHY belongs or provides information about all ports. Shows RAID configuration information for the Core I/O card / HBA. If the option is specified with this command, then it displays persistent device file information. Displays the contents of a specific PCI config space or MMIO register or all PCI config spaces or MMIO registers. PCI config space or MMIO register type is specified with the qualifier. If is not specified, then the command assumes a default register type of MMIO. Issues a SMP command. The file_name must contain the SMP request frame. Shows the SMP initiator SAS address to send SMP requests. Shows information about a specific target or all targets. Shows vital product data information for the SAS I/O card / HBA. When the command is run without qualifiers, it shows statistics about the SAS I/O card / HBA represented by device_file. The following qualifiers are specified with the command: Shows statistics for all PHYs or a specific PHY. Shows statistics for a port to which the specified PHY belongs to or provides statistics for all ports. Shows statistics for a specific target or all targets. The following qualifiers must be specified with the command: Allows the lun_dsf specified with to be associated with a new SAS target, which is specified with the qualifier. The lun_dsf must be the legacy device file and the new_hw_path must be the legacy hardware path. This command does not allow a persistent device file or the new style hardware path to be specified with the and qualifiers. For persistent device files, please use the command. See io_redirect_dsf(1M) for more information. This command is typically intended for replacing a bad drive. This operation must not be used while there are outstanding I/O requests to the lun_dsf or to any LUNs under the new_hw_path. If the option is not specified, displays a warning message before proceeding. Otherwise, it suppresses the warning message and executes the command. Allows the lun_dsf specified with to be associated with a new SAS target, which is specified with the qualifier. The lun_dsf must be the legacy device file. This command does not allow persistent device files to be specified with the and qualifiers. For persistent device files, please use the command. See io_redirect_dsf(1M) for more information. This command is typically intended for replacing a bad drive. This operation must not be used while there are outstanding I/O requests to the new lun_dsf. If the option is not specified, displays a warning message before proceeding. Otherwise, it suppresses the warning message and executes the command. Allows the HW path specified with to be associated with a new SAS target, which is specified with the qualifier. The and the must be the legacy hard- ware paths. This command does not allow the new style hardware paths to be specified with the and qualifiers. For persistent lun hardware paths, please use the command. See io_redirect_dsf(1M) for more information. This command is typically intended for replacing a bad drive. This operation must not be used while there are outstanding I/O requests to any LUNs under the If the option is not specified, displays a warning message before proceeding. Otherwise, it suppresses the warning message and executes the command. Resets the SAS I/O card / HBA and performs a complete re-initialization. This is a destructive operation. Some I/Os can be aborted by this command. If the option is not specified with this command, displays a warning message before continuing. Otherwise, it suppresses the warning message and executes the command. One of the following sets of qualifiers must be specified with the command: This set of qualifiers is used to turn on or off the locate LED for the specified lun. If it is a RAID device lun, then this command turns on or off the LOCATE LED for all the physical disks that are part of the RAID volume. This set of qualifiers is used to change the state of the volume based on the value specified by the qualifier and the volume specified by If the option is not specified, displays a warning message before proceeding with the operation. Otherwise, it sup- presses the warning message and continues executing the command. This set of qualifiers is used to change the rebuild rate of the volume specified by based on the rate specified by the If the option is not specified, displays a warning message before proceeding with the operation. Otherwise, it sup- presses the warning message and continues executing the command. Security Restrictions requires either superuser privilege or and privileges for RAID configurations. See privileges(5) for more information about privileged access on systems that support fine-grained privileges. EXAMPLES
Display all PHY statistics of the SAS I/O card / HBA whose device file is Display all RAID volume information of the Core I/O card / HBA whose device file is Clear statistics for a port with PHY ID 1 of the SAS I/O card / HBA whose device file is Forcefully issue disable request to the SAS I/O card / HBA whose device file is Add a RAID volume with size 34000 (MB), level 1 (RAID1), and enc_bay 1:4,1:5 to the Core I/O card / HBA whose device file is Add a spare disk to the Core I/O card / HBA whose device file is Delete a RAID volume with volume ID 4 to the Core I/O card / HBA whose device file is Delete the Core I/O card / HBA Spare on the HBA whose device file is Change the state to ACTIVE for the RAID volume with volume id 3. Change the rebuild rate to 20% for the RAID volume with volume id 3. Update the firmware on the specified HBA. AUTHOR
was developed by HP. SEE ALSO
privileges(5), intro(7). at sasmgr(1M)
All times are GMT -4. The time now is 01:59 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy