- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- HPE EVA Storage
- >
- Controlling LUN queue depth throttling in VMware E...
Categories
Company
Local Language
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
Discussions
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
Community
Resources
Forums
Blogs
- 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
01-16-2015 03:17 AM - last edited on 01-18-2015 06:17 PM by Maiko-I
01-16-2015 03:17 AM - last edited on 01-18-2015 06:17 PM by Maiko-I
Controlling LUN queue depth throttling in VMware ESX / ESXi (1008113) with EVA4400
Hi,
I have a question about the kb Controlling LUN queue depth throttling in VMware ESX / ESXi (1008113).
I have to change these parameters on a HP EVA4400 storage because I found in vmkernel many messages of this type:
Analyzing the vmkernel.log host s1
2014-12-02T04: 03: 24.178Z CPU3: 1.33054 million) NMP: nmp_ThrottleLogForDevice: 2319: Cmd 0x2a (0x412401e1e0c0, 2951955) to dev "naa.6001438005df75c20000500004dd0000" on path "vmhba3: C0: T0: L17" Failed: H: 0x0 D: 0x28 P: 0x0 Possible sense data: 0x0 0x0 0x0. Act: NONE
2014-12-02T04: 03: 24.184Z CPU3: 2951958) NMP: nmp_ThrottleLogForDevice: 2319: Cmd 0x2a (0x412401e82080, 1330588) to dev "naa.6001438005df75c20000500005820000" on path "vmhba2: C0: T0: L13" Failed: H: 0x0 D: 0x28 P: 0x0 Possible sense data: 0x0 0x0 0x0. Act: NONE
2014-12-02T04: 03: 24.188Z cpu5: 1257171) NMP: nmp_ThrottleLogForDevice: 2319: Cmd 0x2a (0x4124401d0f80, 1.27284 million) to dev "naa.6001438005df75c200005000018a0000" on path "vmhba3: C0: T0: L21" Failed: H: 0x0 D: 0x28 P: 0x0 Possible sense data: 0x0 0x0 0x0. Act: NONE
2014-12-02T04: 03: 24.189Z cpu1: 1330592) ScsiDeviceIO: 2318: Cmd (0x4124001dbac0) 0x2a, CmdSN 0x8000002d world from 1,330,537 to dev "naa.6001438005df75c20000500005820000" failed H: 0x0 D: 0x28 P: 0x0 Possible sense data: 0x0 0x0 0x0.
Looking in HP I found this article
I would like to know if these parameters can be changed with the virtual machines running or whether it is better to put the hosts in maintenace mode.
Thank You
Greetings
P.S. This thread has been moved from General to Storage Area Networks (SAN) (Enterprise). - Hp Forum Moderator
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-18-2015 07:29 PM
01-18-2015 07:29 PM
Re: Controlling LUN queue depth throttling in VMware ESX / ESXi (1008113) with EVA4400
The Queue Depth settings take effect immediately. You do not need to reboot the ESX/ESXi host. Hence, ideally virtual machines can be running while you implement the changes.
Hope this helps!!
Regards
Zsal