- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Migration to EMC Invista.
Operating System - HP-UX
1821587
Members
5020
Online
109633
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-03-2007 09:04 PM
тАО06-03-2007 09:04 PM
Migration to EMC Invista.
Hi
I have a problem with the migration from EMC Symmetrix to EMC Invista (virtualized) devices. This is the situation.
OS: HP-UX 11i v2
VxVM with DMP for multipathing.
The device in question (an example): c2t2d7
(with alternate path c4t2d7).
Using Invista, 2 additional paths are added, to the same LUN. These are c18t3d0 and c19t3d0.
However, DMP does not recognise these additional paths, while powerpath are well aware of them.
#powermt display nonvirtual dev=c18t3d0
Invista ID=CK200070400727
Logical device ID=60001440B0604774002029600E000145
NonVirtual Symmetrix ID=000xxxxxxxx
NonVirtual device ID=024F
NonVirtual device name=c2t2d7
state=alive; policy=ADaptive; priority=0; queued-IOs=0
==============================================================================
---------------- Host --------------- - Stor - -- I/O Path - -- Stats ---
### HW Path I/O Paths Interf. Mode State Q-IOs Errors
==============================================================================
18 0/0/6/1/0.146.0.1.0.3.0 c18t3d0 0D active alive 0 0
19 0/0/14/1/0.147.0.0.0.3.0 c19t3d0 0C active alive 0 0
Has anyone done this kind of migration before?
Is there a way that I can tell DMP to recognise the additional devices as paths to the same LUN?
Hope you can help.
I have a problem with the migration from EMC Symmetrix to EMC Invista (virtualized) devices. This is the situation.
OS: HP-UX 11i v2
VxVM with DMP for multipathing.
The device in question (an example): c2t2d7
(with alternate path c4t2d7).
Using Invista, 2 additional paths are added, to the same LUN. These are c18t3d0 and c19t3d0.
However, DMP does not recognise these additional paths, while powerpath are well aware of them.
#powermt display nonvirtual dev=c18t3d0
Invista ID=CK200070400727
Logical device ID=60001440B0604774002029600E000145
NonVirtual Symmetrix ID=000xxxxxxxx
NonVirtual device ID=024F
NonVirtual device name=c2t2d7
state=alive; policy=ADaptive; priority=0; queued-IOs=0
==============================================================================
---------------- Host --------------- - Stor - -- I/O Path - -- Stats ---
### HW Path I/O Paths Interf. Mode State Q-IOs Errors
==============================================================================
18 0/0/6/1/0.146.0.1.0.3.0 c18t3d0 0D active alive 0 0
19 0/0/14/1/0.147.0.0.0.3.0 c19t3d0 0C active alive 0 0
Has anyone done this kind of migration before?
Is there a way that I can tell DMP to recognise the additional devices as paths to the same LUN?
Hope you can help.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-05-2007 06:12 PM
тАО06-05-2007 06:12 PM
Re: Migration to EMC Invista.
Some more information:
I've done ioscan's, insf's, vxdctl enable's, powermt config's and all those nice commands that scans the buses.
The LUNs do not appear to be accessible via the Invista paths:
#diskinfo /dev/rdsk/c18t3d0
SCSI describe of /dev/rdsk/c18t3d0:
vendor: EMC
product id: Invista
type: direct access
size: 0 Kbytes
bytes per sector: 0
#dd if=/dev/rdsk/c18t3d0 of=/dev/null bs=8k
dd read error: No such device or address
0+0 records in
0+0 records out
#vxddladm listjbod
VID PID Opcode Page Code Page Offset SNO length Policy
==========================================================================
...
DGC ALL PIDs 18 131 8 16 Disk
EMC ALL PIDs 18 -1 36 12 Disk
The question is, though, should I be able to address the LUNs via the Invista paths at this stage? If so, where else can I check for connectivity issues?
Eagerly awaiting any response :-)
I've done ioscan's, insf's, vxdctl enable's, powermt config's and all those nice commands that scans the buses.
The LUNs do not appear to be accessible via the Invista paths:
#diskinfo /dev/rdsk/c18t3d0
SCSI describe of /dev/rdsk/c18t3d0:
vendor: EMC
product id: Invista
type: direct access
size: 0 Kbytes
bytes per sector: 0
#dd if=/dev/rdsk/c18t3d0 of=/dev/null bs=8k
dd read error: No such device or address
0+0 records in
0+0 records out
#vxddladm listjbod
VID PID Opcode Page Code Page Offset SNO length Policy
==========================================================================
...
DGC ALL PIDs 18 131 8 16 Disk
EMC ALL PIDs 18 -1 36 12 Disk
The question is, though, should I be able to address the LUNs via the Invista paths at this stage? If so, where else can I check for connectivity issues?
Eagerly awaiting any response :-)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-05-2007 11:53 PM
тАО06-05-2007 11:53 PM
Re: Migration to EMC Invista.
Yet more information:
The device was set as "Not ready" on the SAN. That was changed to "Ready" and I now have access to the device:
#dd if=/dev/rdsk/c18t3d0 of=/dev/null bs=8k
6520+0 records in
6520+0 records out
Still, DMP does not acknowledge the controller:
#vxdmpadm listctlr all
CTLR-NAME ENCLR-TYPE STATE ENCLR-NAME
=====================================================
c4 EMC ENABLED EMC0
c2 EMC ENABLED EMC0
How can I make VxVM see this device?
The device was set as "Not ready" on the SAN. That was changed to "Ready" and I now have access to the device:
#dd if=/dev/rdsk/c18t3d0 of=/dev/null bs=8k
6520+0 records in
6520+0 records out
Still, DMP does not acknowledge the controller:
#vxdmpadm listctlr all
CTLR-NAME ENCLR-TYPE STATE ENCLR-NAME
=====================================================
c4 EMC ENABLED EMC0
c2 EMC ENABLED EMC0
How can I make VxVM see this device?
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Learn About
News and Events
Support
© Copyright 2025 Hewlett Packard Enterprise Development LP