- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- Disk Enclosures
- >
- XP512 - Command Device creation
Disk Enclosures
1753885
Members
7122
Online
108809
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
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
Go to solution
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
тАО11-21-2002 06:57 AM
тАО11-21-2002 06:57 AM
The documentation for performance Advisor for XP512 recommends that if I create a Command Device from an existing LUN, that I be on Offline mode.
Does that mean if I create a CU:LDEV of 50 MB using VSC then assign it to a Command Device, then I do not require the XP Array or the Server concerned to be in Offline Mode?
Thanks, ian Dennison
Does that mean if I create a CU:LDEV of 50 MB using VSC then assign it to a Command Device, then I do not require the XP Array or the Server concerned to be in Offline Mode?
Thanks, ian Dennison
Building a dumber user
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-21-2002 08:15 AM
тАО11-21-2002 08:15 AM
Solution
You are correct. If you are converting an existing LUN to a command device, you should be in offline mode, but if you use a new/unused LDEV and create a new LUN you can do it in online mode.
Good luck!
Good luck!
No matter where you go, there you are.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-21-2002 08:26 AM
тАО11-21-2002 08:26 AM
Re: XP512 - Command Device creation
Thanks Vincent, will charge on with it!
Message closed, Thanks Ian
Message closed, Thanks Ian
Building a dumber user
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-13-2003 07:47 PM
тАО07-13-2003 07:47 PM
Re: XP512 - Command Device creation
I am new to the forum but old to the product.
Just remember that when you add a NEW command device/or change an existing LDEV to command device, it will also take the port offline but for few seconds only (in both online and offline mode of lun management). Hosts connected to the port may time out. We have faced this problem.
The best practice is to map the new command device to one unused/not live/development port first, complete the configuration and then assign additional paths to the command device via which the production servers can see the command device. This way we are only assigning another path to existing command device (can be done online/offline) but not changing the command device mode.
In case a host has two HBA (with high availability software installed), create the command device on the first port where first HBA connected, complete the lun configuration and then assign another path to the same command device using second port where second HBA is connected.
Just remember that when you add a NEW command device/or change an existing LDEV to command device, it will also take the port offline but for few seconds only (in both online and offline mode of lun management). Hosts connected to the port may time out. We have faced this problem.
The best practice is to map the new command device to one unused/not live/development port first, complete the configuration and then assign additional paths to the command device via which the production servers can see the command device. This way we are only assigning another path to existing command device (can be done online/offline) but not changing the command device mode.
In case a host has two HBA (with high availability software installed), create the command device on the first port where first HBA connected, complete the lun configuration and then assign another path to the same command device using second port where second HBA is connected.
If what you're working for really matters, you'll give it all you've got.
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.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP