Home > Storage > PowerStore > Databases and Data Analytics > Dell PowerStore Metro Node with Oracle > Vendor and model name of metro node devices
Metro node virtual volumes are created with vendor name EMC and device model name Invista.
To identify metro node virtual volumes exposed to a database server, use the information in the remainder of this section.
To query the WWNs of the metro node virtual volumes on Oracle Linux 7, run one of the following commands.
multipath -ll | grep Invista
multipath -ll <multipath-device-alias> | grep Invista
lsscsi --scsi_id -g | grep Invista
/usr/lib/udev/scsi_id --page=0x83 --whitelisted --device=<device>
Example:
[ ~]# multipath -ll | grep Invista
ora_asm_redo_002 (360001440000000106000956e7780d726) dm-1 EMC ,Invista
.
.
.
[ ~]# multipath -ll ora_asm_crs_001 | grep Invista
ora_asm_crs_001 (360001440000000106000956e7780d6db) dm-3 EMC ,Invista
Note: multipath -ll (without the ‘grep Invista’ filter) displays both the WWN and LUN ID of the device.
[ ~]# lsscsi --scsi_id -g | grep Invista
[15:0:0:11] disk EMC Invista 4000 /dev/sde 360001440000000106000956e7780d6db /dev/sg4
.
.
.
[ ~]# /usr/lib/udev/scsi_id --page=0x83 --whitelisted /dev/sde
360001440000000106000956e7780d6db
WWNs and LUN IDs of metro node virtual volumes can be derived multiple different ways through Unisphere for metro node or through vplexcli. One method for each interface is shown below:
Unisphere for metro node:
Vplexcli:
service@director-1-1-a:~> vplexcli
Trying ::1...
Connected to localhost.
Escape character is '^]'.
VPlexcli:/>
cd /clusters/<cluster-name>/exports/storage-views/<storage-view-of-database-server>
ls -ft virtual-volumes
VPlexcli:> cd /clusters/cluster-1/exports/storage-views/r730xd-1
VPlexcli:/clusters/cluster-1/exports/storage-views/r730xd-1> ls -ft virtual-volumes
/clusters/cluster-1/exports/storage-views/r730xd-1:
Name Value
--------------- --------------------------------------------------------------------
virtual-volumes [(11,ORA_CRS_1,nnnnnnn:60001440000000106000956e7780d6db,20G),
(21,ORA_DB1_DATA_001, nnnnnnn:60001440000000106000956e7780d6e4,250G),
(22,ORA_DB1_DATA_002, nnnnnnn:60001440000000106000956e7780d6ed,250G),
.
.
.