- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - VMware
- >
- HPE Custom ISO 6.5 update 1, 3Par issues
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
Forums
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
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
08-29-2017 02:31 AM
08-29-2017 02:31 AM
Hi
Just installed two BL460c Gen9 with the HPE Custom ISO ESXi 6.5 update 1.
Hosts are connected to StoreServ 7200 and 8200 thru VirtualFabric module and 16Gbps Brocade switches. When volumes are presented from either StoreServ the boot process takes extremely long time to complete, more than 40 minutes. If no volumes are presented the boot will take about two minutes as normal.
The boot process shows satp_alua loaded successfully for several minutes before switching to nfs4client loaded successfully and stays there for at least 15 minutes before boot continues.
This behavior occours both when default Path Policy for MRU is loaded during first boot but also after default path policy is changed to values that HPE recommend (RoundRobin, IOPS=1 etc.).
Existing hosts installed with ESXi 6.0 are not affected.
Any ideas?
Solved! Go to Solution.
- Tags:
- 3PAR
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-30-2017 05:25 AM
08-30-2017 05:25 AM
SolutionI was able to narrow down the possible source of problem: RDM's used for Microsoft Clustering and came across this article that solved the problem.