- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- BL460c G6 NC532i issue with Virtual Connect 3.10
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
02-23-2011 01:07 PM
02-23-2011 01:07 PM
BL460c G6 NC532i issue with Virtual Connect 3.10
Jean-denis is working a problem:
************************
Hi
Some BL460c G6 servers were added to an existing enclosure configured with 2 VC-Enet modules in Interconnec tBay#1 and #2 (VC firmware 3.10).
Interconnect Bay#3 and #4 contains VC-FC 24 port 8G modules
One of the Bl460c G6 servers is reporting FF-FF-FF-FF-FF-FF mac addresses for his embedded Nics within OA.
Within VCEM customer sees the following:
"This mezzanine device does not have rear I/O connectivity"
Is that meaning there is an hardware issue with the NC532i embedded NICs on the concerned server or am I missing something
******************************
Monty replied:
************************
An Onboard Administrator (OA) show all will have more information on this issue – in particular, I believe it will show that the OA is reporting that server blade is degraded due to a Device Identification Error, plus the active OA syslog might have a message indicating that such an error was discovered on the embedded NIC on that server.
The OA report of device MAC or WWN is based on reading the FRU eeprom for each device. If one of the FRU eeprom is unreadable, the OA protects the server and interconnects by disabling the ports on those corresponding interconnect modules.
************************
Any other comments or help for Jean-denis?