- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- Server Management - Systems Insight Manager
- >
- Re: Gbe2 "Unknown Rack ID and Enclosure Informatio...
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
03-30-2005 07:19 PM
03-30-2005 07:19 PM
Gbe2 "Unknown Rack ID and Enclosure Information"
I have solved it once (i think), connect to the Serial Port back at the Management Module and Choose submenu S=RACK and reenter the Serial Number of the Blade Enclosure and apply. Restart Manangement Module and it worked that time. Tried on other Blade Enclosures but no success. How is it possible to change this information
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-31-2005 11:43 PM
03-31-2005 11:43 PM
Re: Gbe2 "Unknown Rack ID and Enclosure Information"
These are all critical pieces, especially the pmm firmware all being at 2.10 and the interconnect switch image being newer.
I noticed on ours that the interconnect switches with the latest firmware image and the power management module firmware all being at 2.10 that it all works fine. I would also make sure your ILO's are all at 1.70.
Are you seeing any chksum or other weird errors on the enclosure for it's serial number? That caused us some issues and was resolved by replacing the signal backplane in the enclosure.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-31-2005 11:58 PM
03-31-2005 11:58 PM
Re: Gbe2 "Unknown Rack ID and Enclosure Information"
I attached the firmware image for the rack infrastructure. You can download the latest ILO from support and drivers at.
http://h18023.www1.hp.com/support/files/server/us/winroms.html
The ILO and rack infrastructure are absolutely critical that they are running at the latest out there. I know because I have been working for 3 months with the HP engineers in Houston on are various issues.
Once the ILo is at 1.70 go into the ILO, go to the BLP class tab, and rack view. This will not work unless all of your enclosure firmware is at 2.10 and your ILO's are all at 1.70. Once that is set then you go into the details link on the enclosure of the blade ILO you are in and name the rack, and the enclosure. You can configure the rack name from any blade ILO in the rack, but you have to go into an ILO that is physically located in the enclosure you want to rename to rename each enclosure. If you have 4 blade enclosure you will need to go inot 4 seperate blade ILO's to correctly rename all the enclosures. What I do is name them Rack1 for the first blade rack, then the first enclosure is A, the second enclosure is B, and so on.
Hope this helps
Hope this helps
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-01-2005 12:47 AM
04-01-2005 12:47 AM
Re: Gbe2 "Unknown Rack ID and Enclosure Information"
I have upgraded every component in this Blade Solution to "Latest and Greatest".
But it hasn´t changed status, but I tried a solution that worked, very strange.
Unscrew the serial port plastic kit from the Management Module and connect a PC/Server to it and check the Serial Number
(E=Serial Number). Then it reports the correct serial number, but I changed it to exactly the same, just made some kind of change in the Management module, then it WORKED.So "ReEnter" the Blade Enclosure Serial Number and then reset all Management Modules. You have to do this one module then reset all management modules.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-01-2005 01:09 AM
04-01-2005 01:09 AM
Re: Gbe2 "Unknown Rack ID and Enclosure Information"
I have seen tons of very odd issues such as this with the HP blade systems and we are actually looking at the IBM bladecenters now just to get a feel for their solution, because we are feed up with the HP systems unreliability lately. The fears we had when they bought compaq are all to real now.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-16-2005 12:55 AM
09-16-2005 12:55 AM
Re: Gbe2 "Unknown Rack ID and Enclosure Information"
The reason changing the serial number worked is because the serial number you changed made a change in the signal backplane of the neclosure. Changes to the signal backplane trigger an interrupt in the switch to make it re-read the enclosure data. You can easily do this remotely by going into iLO and changing the rack or enclosure name and then changing it right back.
This should not ever need to be done, however. Make sure you have the latest GbE2 firmware and the latest enclosure firmware (coincidentally, they are both at version 2.20 right now).