- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- SLES 9 install via ICLE on a bl460c Blade
Operating System - Linux
1756701
Members
3255
Online
108852
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
06-27-2007 07:00 AM
06-27-2007 07:00 AM
SLES 9 install via ICLE on a bl460c Blade
We are attempting to install SLES 9.3 on a bl460c using Insight Control Linux Edition 1.6. The install task advises us that eth1 must be used for network installs on a bl460c.
Our problem is that eth0 is the only accessible NIC on this Blade. What is the reason for this restriction and is a workaround available?
Thanks,
Our problem is that eth0 is the only accessible NIC on this Blade. What is the reason for this restriction and is a workaround available?
Thanks,
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-16-2007 04:21 AM
07-16-2007 04:21 AM
Re: SLES 9 install via ICLE on a bl460c Blade
Hi Neil, sorry for the delayed response.
You are correct that ICLE "advises" the use of eth1 for provision tasks on that specific HP Blade Server (note: advises and not mandatory). The reason is that eth1 is the NIC that is connected to the ICLE "Management Network", hence eth1 is the NIC that can get back to the ICLE hard drive which is where the OS bits are stored for use during the Suse SLES native installer. You can use any available NIC you desire, it must simply have connectivity back to where the OS bits are stored on the ICLE hard drive. The ramdisk that the blade is booted to enumerates eth1 to be that NIC. So, we advise the use of that NIC.
Robert
You are correct that ICLE "advises" the use of eth1 for provision tasks on that specific HP Blade Server (note: advises and not mandatory). The reason is that eth1 is the NIC that is connected to the ICLE "Management Network", hence eth1 is the NIC that can get back to the ICLE hard drive which is where the OS bits are stored for use during the Suse SLES native installer. You can use any available NIC you desire, it must simply have connectivity back to where the OS bits are stored on the ICLE hard drive. The ramdisk that the blade is booted to enumerates eth1 to be that NIC. So, we advise the use of that NIC.
Robert
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