- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- Issue with LOM channel after firmware and driver u...
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
03-26-2014 11:59 AM
03-26-2014 11:59 AM
Issue with LOM channel after firmware and driver update
Nick had an issue:
***********
Hi all,
I have a really weird issue after updating the firmware and drivers on a BL460c G7 in a c3000 running VMware 5.1
The BL460c g7 has the embedded NC553i and Mezzanine card NC532M, connected via VC-Flex 10 modules.
After updating the firmware and drivers to match the VMware recipe document we are unable to perform a vMotion or VMKping to 1 channel of the embedded LOM (LOM1:b). If we change the vMotion network to LOM:1:c) VMKping works.
Has anyone ever seen anything like this before?
*************
Nick did resolve the issue:
***********
This turned out to be a problem with the online firmware flash of the Emulex CNA. Despite both the online and offline SPP’s saying the firmware had been done, and ESX seeing the correct firmware, we noticed that the PXE boot code portion had not been updated for some reason. We re-applied the Emulex firmware offline, and after this the PXE BOOT banner showed the correct version, and our original issue with LOM1:B not working cleared.
************
Comments?