- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- ProLiant BL460c G1 Drivers\Firmware
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
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
06-10-2016 11:03 AM
06-10-2016 11:03 AM
ProLiant BL460c G1 Drivers\Firmware
Hi All,
Im having issues with a ProLiant BL460c G1 which are connected storage via iSCSI (D2200sb Storage Blade). On the ESXi host (ESXi 5.0 U3) im seeing “Lost access to volume ***** due to connectivity issues. Recovery attempt is in progress and outcome will be reported shortly".
Im presuming this is a driver and\or firmware issue with the NC373i Integrated Multifunction Gigabit Server Adapter. Could someone assist me in finding compatible drivers and firmware so that i can test to see if this resolves the issue.
Current versions:
~ # ethtool -i vmnic0
driver: bnx2
version: 2.2.5j.v50.3
firmware-version: bc 4.4.1
bus-info: 0000:03:00.0
~ # ethtool -i vmnic1
driver: bnx2
version: 2.2.5j.v50.3
firmware-version: bc 4.4.1
bus-info: 0000:07:00.0
~ # ethtool -i vmnic2
driver: bnx2
version: 2.2.5j.v50.3
firmware-version: bc 5.2.2
bus-info: 0000:10:00.0
~ # ethtool -i vmnic3
driver: bnx2
version: 2.2.5j.v50.3
firmware-version: bc 5.2.2
bus-info: 0000:10:00.1
~ # vmkchdev -l |grep vmnic0
000:003:00.0 14e4:16ac 103c:703b vmkernel vmnic0
~ # vmkchdev -l |grep vmnic1
000:007:00.0 14e4:16ac 103c:703b vmkernel vmnic1
~ # vmkchdev -l |grep vmnic2
000:016:00.0 14e4:163a 103c:171d vmkernel vmnic2
~ # vmkchdev -l |grep vmnic3
000:016:00.1 14e4:163a 103c:171d vmkernel vmnic3