- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- solaris 10 /proliant deployment issue
BladeSystem - General
1752650
Members
5696
Online
108788
Solutions
Forums
Categories
Company
Local Language
back
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
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
01-19-2010 02:23 AM
01-19-2010 02:23 AM
solaris 10 /proliant deployment issue
Foreword: I am posting to this thread because my problem resembles the one at http://forums13.itrc.hp.com/service/forums/questionanswer.do?admit=109447627+1263895165146+28353475&hpweb_printable=true&threadId=1347509
Strictly speaking, this is *not* a blade server issue (i am using dl380g6). In addition I had already treid to describe the problem at an early stage of the investigation at this link http://forums13.itrc.hp.com/service/forums/questionanswer.do?threadId=1343364&admit=109447627+1263894774100+28353475
Currently I have 2 dl3*0 G6 on the same network: dl360 g6 runs Solaris 10 U7, dl380g6 should:
1) load grub from it's local disk
2) continue to boot from the network using a PXE enabled broadcomm NIC.
The process fails at step 1:
grub> ifconfig
Probing pci nic...
[UNDI]
...
[UNDI]
No ethernet card found.
Error 12: Invalid device requested
(same error when using grub> dhcp ... )
However, when grub is loaded from the network using files served up by the dl360, then the dl380 boots up correctly.
A previous discussion on this thread, especially Brian Blackwell's post on september 4 2009, suggests that my problem might be related to not having adequate driver support for the Proliant. My case is however different becasue I am only using grub stage 1 and 2 from the client disk, and I am not sure if and how the patching process described by Brian Blackwell would be relevant to my case and how it can be done.
Strictly speaking, this is *not* a blade server issue (i am using dl380g6). In addition I had already treid to describe the problem at an early stage of the investigation at this link http://forums13.itrc.hp.com/service/forums/questionanswer.do?threadId=1343364&admit=109447627+1263894774100+28353475
Currently I have 2 dl3*0 G6 on the same network: dl360 g6 runs Solaris 10 U7, dl380g6 should:
1) load grub from it's local disk
2) continue to boot from the network using a PXE enabled broadcomm NIC.
The process fails at step 1:
grub> ifconfig
Probing pci nic...
[UNDI]
...
[UNDI]
No ethernet card found.
Error 12: Invalid device requested
(same error when using grub> dhcp ... )
However, when grub is loaded from the network using files served up by the dl360, then the dl380 boots up correctly.
A previous discussion on this thread, especially Brian Blackwell's post on september 4 2009, suggests that my problem might be related to not having adequate driver support for the Proliant. My case is however different becasue I am only using grub stage 1 and 2 from the client disk, and I am not sure if and how the patching process described by Brian Blackwell would be relevant to my case and how it can be done.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP