Disk Enclosures
1751894 Members
5098 Online
108783 Solutions
New Discussion юеВ

Re: va7400 how to check how many servers are conneted

 
SOLVED
Go to solution
Johnson Punniyalingam
Honored Contributor

va7400 how to check how many servers are conneted

Hi All,

Can any one advice me, how to check how many servers are connected to the storage va7400,

Thanks,
Johnson
Problems are common to all, but attitude makes the difference
10 REPLIES 10
Torsten.
Acclaimed Contributor
Solution

Re: va7400 how to check how many servers are conneted

Try "armtopology " from commandview sdm.

Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
Johnson Punniyalingam
Honored Contributor

Re: va7400 how to check how many servers are conneted

Hi ,

Thanks for your reply,

armtopology ..?

how to get.? using armdsp -i.? You mean

Thx,
Johnson
Problems are common to all, but attitude makes the difference
Torsten.
Acclaimed Contributor

Re: va7400 how to check how many servers are conneted

No array id, sorry.

Syntax
armtopology [ ... ]
armtopology -?

To specify specific hosts, use the option. Use either the DNS
name or IP address of the hosts. Separate multiple HostNames with a space.
If no HostName options are specified, all hosts discovered on the subnet with
arrays will be displayed, provided they have Command View SDM installed.

Example output:

Host Host Node WWN Host Port WWN Product SerialNumber C RG LUN Device path
-------------------------------------------------------------------------------------
host1 50060b000005aed6 50060b000005aed7 A6188A 00USP1001064 1 1 1 \\.\PHYSICALDRIVE1
host2 50060b000005cde7 50060b000005cde8 A6188A 00USP1001064 2 2 0 /dev/rdsk/c0t0d0
host3 50060b000005fgh8 50060b000005fgh9 A6189A 00USP1001234 1 1 0 /dev/rdsk/c1t0d0
host3 50060b000005ijk6 50060b000005ijk7 A6189A 00USP1001234 2 2 1 /dev/rdsk/c2t0d1

Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
Johnson Punniyalingam
Honored Contributor

Re: va7400 how to check how many servers are conneted

Hi Torsten,

Once Thank you.., the armdsp command binarys are installed only at DWSHVR03

Please see below output can help me confirm that I suspect only DWHSVR03 only currently connected to the va7400,

my Goal its confirm the below mentioned server are connected to va7400

192.168.213.63 dwhsvr03 # Application server
192.168.213.62 dwhsvr02 # staging server
192.168.213.61 dwhsvr01 # datawarehouse server
192.168.213.65 dwhsvr07 # NEwStaging Server



/ > armtopology 192.168.213.63 192.168.213.62 192.168.213.61 192.168.213.65
Host Host Node WWN Host Port WWN Product Serial Number C RG LUN Device Host Device Path
----------------------------------------------------------------------------------------------------------------------
dwhsvr03 50060b000010753b 50060b000010753a A6189A 00SG216J0049 1 1 0 dwhsvr03 /dev/rscsi/c18t0d0
dwhsvr03 50060b000010753b 50060b000010753a A6189A 00SG216J0049 1 1 40 dwhsvr03 /dev/dsk/c17t5d0
dwhsvr03 50060b000010753b 50060b000010753a A6189A 00SG216J0049 2 2 32 dwhsvr03 /dev/dsk/c17t4d0
dwhsvr03 50060b000010753b 50060b000010753a A6189A 00SG216J0049 1 1 0 dwhsvr03 /dev/dsk/c17t0d0
dwhsvr03 50060b000010751b 50060b000010751a A6189A 00SG216J0049 1 1 0 dwhsvr03 /dev/rscsi/c6t0d0
dwhsvr03 50060b000010751b 50060b000010751a A6189A 00SG216J0049 1 1 40 dwhsvr03 /dev/dsk/c5t5d0
dwhsvr03 50060b000010751b 50060b000010751a A6189A 00SG216J0049 2 2 32 dwhsvr03 /dev/dsk/c5t4d0
dwhsvr03 50060b000010751b 50060b000010751a A6189A 00SG216J0049 1 1 0 dwhsvr03 /dev/dsk/c5t0d0
Problems are common to all, but attitude makes the difference
Johnson Punniyalingam
Honored Contributor

Re: va7400 how to check how many servers are conneted

My Goal is to check wether the said server are connected or not connected.?

Thanks,
Johnson
Problems are common to all, but attitude makes the difference
Torsten.
Acclaimed Contributor

Re: va7400 how to check how many servers are conneted

Do you get the same result if you run only "armtopology" without any host entries?

Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
Torsten.
Acclaimed Contributor

Re: va7400 how to check how many servers are conneted

To double check the results from each host, run "ioscan -fnCdisk" and look for "A6189A".

Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
Johnson Punniyalingam
Honored Contributor

Re: va7400 how to check how many servers are conneted

Please see the below output which run only


/ > armtopology
Host Host Node WWN Host Port WWN Product Serial Number C RG LUN Device Host Device Path
----------------------------------------------------------------------------------------------------------------------
dwhsvr03 50060b000010753b 50060b000010753a A6189A 00SG216J0049 1 1 0 dwhsvr03 /dev/rscsi/c18t0d0
dwhsvr03 50060b000010753b 50060b000010753a A6189A 00SG216J0049 1 1 40 dwhsvr03 /dev/dsk/c17t5d0
dwhsvr03 50060b000010753b 50060b000010753a A6189A 00SG216J0049 2 2 32 dwhsvr03 /dev/dsk/c17t4d0
dwhsvr03 50060b000010753b 50060b000010753a A6189A 00SG216J0049 1 1 0 dwhsvr03 /dev/dsk/c17t0d0
dwhsvr03 50060b000010751b 50060b000010751a A6189A 00SG216J0049 1 1 0 dwhsvr03 /dev/rscsi/c6t0d0
dwhsvr03 50060b000010751b 50060b000010751a A6189A 00SG216J0049 1 1 40 dwhsvr03 /dev/dsk/c5t5d0
dwhsvr03 50060b000010751b 50060b000010751a A6189A 00SG216J0049 2 2 32 dwhsvr03 /dev/dsk/c5t4d0
dwhsvr03 50060b000010751b 50060b000010751a A6189A 00SG216J0049 1 1 0 dwhsvr03 /dev/dsk/c5t0d0
Problems are common to all, but attitude makes the difference
Johnson Punniyalingam
Honored Contributor

Re: va7400 how to check how many servers are conneted

DWSHVR01
=========
/ > ioscan -fnC disk |grep -i A6189A
disk 3 0/8/0/0.1.16.0.0.0.0 sdisk CLAIMED DEVICE HP A6189A
disk 4 0/8/0/0.1.16.0.0.0.1 sdisk CLAIMED DEVICE HP A6189A
disk 5 0/8/0/0.1.16.0.0.0.2 sdisk CLAIMED DEVICE HP A6189A
disk 6 0/8/0/0.1.16.0.0.0.3 sdisk CLAIMED DEVICE HP A6189A
disk 7 0/8/0/0.1.16.0.0.0.4 sdisk CLAIMED DEVICE HP A6189A
disk 8 0/8/0/0.1.16.0.0.0.5 sdisk CLAIMED DEVICE HP A6189A
disk 16 0/8/0/0.1.16.0.0.0.6 sdisk CLAIMED DEVICE HP A6189A
disk 9 0/8/0/0.1.16.0.0.1.2 sdisk CLAIMED DEVICE HP A6189A
disk 10 0/8/0/0.1.16.0.0.1.3 sdisk CLAIMED DEVICE HP A6189A
disk 11 0/8/0/0.1.16.0.0.1.4 sdisk CLAIMED DEVICE HP A6189A
disk 14 0/8/0/0.1.16.0.0.1.5 sdisk CLAIMED DEVICE HP A6189A
disk 12 0/8/0/0.1.16.0.0.2.0 sdisk CLAIMED DEVICE HP A6189A
disk 13 0/8/0/0.1.16.0.0.2.1 sdisk CLAIMED DEVICE HP A6189A
disk 58 0/8/0/0.1.16.0.0.2.2 sdisk CLAIMED DEVICE HP A6189A
disk 120 0/8/0/0.1.16.0.0.3.0 sdisk CLAIMED DEVICE HP A6189A
disk 121 0/8/0/0.1.16.0.0.3.3 sdisk CLAIMED DEVICE HP A6189A
disk 123 0/8/0/0.1.16.0.0.6.0 sdisk CLAIMED DEVICE HP A6189A
disk 41 0/12/0/0.1.16.0.0.0.0 sdisk CLAIMED DEVICE HP A6189A
disk 42 0/12/0/0.1.16.0.0.0.1 sdisk CLAIMED DEVICE HP A6189A
disk 44 0/12/0/0.1.16.0.0.0.2 sdisk CLAIMED DEVICE HP A6189A
disk 45 0/12/0/0.1.16.0.0.0.3 sdisk CLAIMED DEVICE HP A6189A
disk 47 0/12/0/0.1.16.0.0.0.4 sdisk CLAIMED DEVICE HP A6189A
disk 48 0/12/0/0.1.16.0.0.0.5 sdisk CLAIMED DEVICE HP A6189A
disk 18 0/12/0/0.1.16.0.0.0.6 sdisk CLAIMED DEVICE HP A6189A
disk 49 0/12/0/0.1.16.0.0.1.2 sdisk CLAIMED DEVICE HP A6189A
disk 50 0/12/0/0.1.16.0.0.1.3 sdisk CLAIMED DEVICE HP A6189A
disk 51 0/12/0/0.1.16.0.0.1.4 sdisk CLAIMED DEVICE HP A6189A
disk 52 0/12/0/0.1.16.0.0.1.5 sdisk CLAIMED DEVICE HP A6189A
disk 53 0/12/0/0.1.16.0.0.2.0 sdisk CLAIMED DEVICE HP A6189A
disk 54 0/12/0/0.1.16.0.0.2.1 sdisk CLAIMED DEVICE HP A6189A
disk 56 0/12/0/0.1.16.0.0.2.2 sdisk CLAIMED DEVICE HP A6189A
disk 124 0/12/0/0.1.16.0.0.3.0 sdisk CLAIMED DEVICE HP A6189A
disk 125 0/12/0/0.1.16.0.0.3.3 sdisk CLAIMED DEVICE HP A6189A
disk 126 0/12/0/0.1.16.0.0.6.0 sdisk CLAIMED DEVICE HP A6189A
disk 87 1/2/0/0.2.0.0.0.0.0 sdisk CLAIMED DEVICE HP A6189A
disk 88 1/2/0/0.2.0.0.0.0.1 sdisk CLAIMED DEVICE HP A6189A
disk 89 1/2/0/0.2.0.0.0.0.2 sdisk CLAIMED DEVICE HP A6189A
disk 90 1/2/0/0.2.0.0.0.0.3 sdisk CLAIMED DEVICE HP A6189A
disk 91 1/2/0/0.2.0.0.0.0.4 sdisk CLAIMED DEVICE HP A6189A
disk 92 1/2/0/0.2.0.0.0.0.5 sdisk CLAIMED DEVICE HP A6189A
disk 93 1/2/0/0.2.0.0.0.0.6 sdisk CLAIMED DEVICE HP A6189A
disk 94 1/2/0/0.2.0.0.0.1.2 sdisk CLAIMED DEVICE HP A6189A
disk 95 1/2/0/0.2.0.0.0.1.3 sdisk CLAIMED DEVICE HP A6189A
disk 96 1/2/0/0.2.0.0.0.1.4 sdisk CLAIMED DEVICE HP A6189A
disk 97 1/2/0/0.2.0.0.0.1.5 sdisk CLAIMED DEVICE HP A6189A
disk 98 1/2/0/0.2.0.0.0.2.0 sdisk CLAIMED DEVICE HP A6189A
disk 99 1/2/0/0.2.0.0.0.2.1 sdisk CLAIMED DEVICE HP A6189A
disk 100 1/2/0/0.2.0.0.0.2.2 sdisk CLAIMED DEVICE HP A6189A
disk 115 1/2/0/0.2.0.0.0.3.0 sdisk CLAIMED DEVICE HP A6189A
disk 116 1/2/0/0.2.0.0.0.3.3 sdisk CLAIMED DEVICE HP A6189A
disk 117 1/2/0/0.2.0.0.0.6.0 sdisk CLAIMED DEVICE HP A6189A
disk 101 1/4/0/0.2.0.0.0.0.0 sdisk CLAIMED DEVICE HP A6189A
disk 102 1/4/0/0.2.0.0.0.0.1 sdisk CLAIMED DEVICE HP A6189A
disk 103 1/4/0/0.2.0.0.0.0.2 sdisk CLAIMED DEVICE HP A6189A
disk 104 1/4/0/0.2.0.0.0.0.3 sdisk CLAIMED DEVICE HP A6189A
disk 105 1/4/0/0.2.0.0.0.0.4 sdisk CLAIMED DEVICE HP A6189A
disk 106 1/4/0/0.2.0.0.0.0.5 sdisk CLAIMED DEVICE HP A6189A
disk 107 1/4/0/0.2.0.0.0.0.6 sdisk CLAIMED DEVICE HP A6189A
disk 108 1/4/0/0.2.0.0.0.1.2 sdisk CLAIMED DEVICE HP A6189A
disk 109 1/4/0/0.2.0.0.0.1.3 sdisk CLAIMED DEVICE HP A6189A
disk 110 1/4/0/0.2.0.0.0.1.4 sdisk CLAIMED DEVICE HP A6189A
disk 111 1/4/0/0.2.0.0.0.1.5 sdisk CLAIMED DEVICE HP A6189A
disk 112 1/4/0/0.2.0.0.0.2.0 sdisk CLAIMED DEVICE HP A6189A
disk 113 1/4/0/0.2.0.0.0.2.1 sdisk CLAIMED DEVICE HP A6189A
disk 114 1/4/0/0.2.0.0.0.2.2 sdisk CLAIMED DEVICE HP A6189A
disk 118 1/4/0/0.2.0.0.0.3.0 sdisk CLAIMED DEVICE HP A6189A
disk 119 1/4/0/0.2.0.0.0.3.3 sdisk CLAIMED DEVICE HP A6189A
disk 122 1/4/0/0.2.0.0.0.6.0 sdisk CLAIMED DEVICE HP A6189A

=========================================================================
DWSHVR02 - not connected
====================================================================
DWSHV07
=======
/ > ioscan -fnC disk |grep -i A6189A
disk 3 0/4/0/0.1.16.0.0.0.0 sdisk CLAIMED DEVICE HP A6189A
disk 5 0/4/0/0.1.16.0.0.3.1 sdisk CLAIMED DEVICE HP A6189A
disk 10 0/4/0/0.1.16.0.0.3.2 sdisk CLAIMED DEVICE HP A6189A
disk 18 0/7/0/0.2.0.0.0.0.0 sdisk CLAIMED DEVICE HP A6189A
disk 20 0/7/0/0.2.0.0.0.3.1 sdisk CLAIMED DEVICE HP A6189A
disk 21 0/7/0/0.2.0.0.0.3.2 sdisk CLAIMED DEVICE HP A6189A

==========================================================================================
DWSHVR03
==========
/ > ioscan -fnC disk |grep -i A6189A
disk 3 0/4/0/0.1.16.0.0.0.0 sdisk CLAIMED DEVICE HP A6189A
disk 6 0/4/0/0.1.16.0.0.4.0 sdisk CLAIMED DEVICE HP A6189A
disk 7 0/4/0/0.1.16.0.0.5.0 sdisk CLAIMED DEVICE HP A6189A
disk 12 0/7/0/0.2.0.0.0.0.0 sdisk CLAIMED DEVICE HP A6189A
disk 13 0/7/0/0.2.0.0.0.4.0 sdisk CLAIMED DEVICE HP A6189A
disk 14 0/7/0/0.2.0.0.0.5.0 sdisk CLAIMED DEVICE HP A6189A

The ioscan -fnC disk --> output for DWHSVR07 and DWSVR03 looks similar, ..?

DWSHVR03 --> is the server which we have Installed armdsp binary's are Installed.

Thanks,
Johnson
Problems are common to all, but attitude makes the difference