- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- Nic order on blades C-Class
BladeSystem - General
1748224
Members
4552
Online
108759
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
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
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
тАО03-27-2007 12:35 AM
тАО03-27-2007 12:35 AM
Nic order on blades C-Class
When installing with RDP. It seems that the nic on which PXE is enable becomes "Local Area Connection 5" instead of the first one. This has consequences for the scripts which works fine on other systems.
Anybody an idea on how to solve/by-pass this issues.
Thx
Daniel
Anybody an idea on how to solve/by-pass this issues.
Thx
Daniel
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-27-2007 11:03 AM
тАО03-27-2007 11:03 AM
Re: Nic order on blades C-Class
Are you deploying an image to this blade?
If so, it can be a byproduct of image deployment. If the image source had LAC 5, you might see LAC 5 on the image target. Or if the image source and target have different NICs or the NICs get enumerated differently, the NIC's on the image target could be recognized as new NICs and will use new LAC #'s.
I'm not too familiar with it but could netsh help you rename the LACs? For Example:
netsh interface>set interface ?
Usage set interface [name = ] IfName
[ [admin = ] ENABLED|DISABLED
[connect = ] CONNECTED|DISCONNECTED
[newname = ] NewName ]
Sets interface parameters.
IfName - the name of the interface
admin - whether the interface should be enabled (non-LAN only).
connect - whether to connect the interface (non-LAN only).
newname - new name for the interface (LAN only).
Notes:
- At least one option other than the name must be specified.
- If connect = CONNECTED is specified, then the interface
is automatically enabled even if the admin = DISABLED
option is specified.
netsh interface>
If so, it can be a byproduct of image deployment. If the image source had LAC 5, you might see LAC 5 on the image target. Or if the image source and target have different NICs or the NICs get enumerated differently, the NIC's on the image target could be recognized as new NICs and will use new LAC #'s.
I'm not too familiar with it but could netsh help you rename the LACs? For Example:
netsh interface>set interface ?
Usage set interface [name = ] IfName
[ [admin = ] ENABLED|DISABLED
[connect = ] CONNECTED|DISCONNECTED
[newname = ] NewName ]
Sets interface parameters.
IfName - the name of the interface
admin - whether the interface should be enabled (non-LAN only).
connect - whether to connect the interface (non-LAN only).
newname - new name for the interface (LAN only).
Notes:
- At least one option other than the name must be specified.
- If connect = CONNECTED is specified, then the interface
is automatically enabled even if the admin = DISABLED
option is specified.
netsh interface>
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-27-2007 12:50 PM
тАО03-27-2007 12:50 PM
Re: Nic order on blades C-Class
I have the same issue too.
We are running linux and deploying with kickstart. If the blade server has a mezz card in there for two additional nics. Those nics are seen as eth2 and eth3 during pxe but as soon as kickstart begins, it thinks the nics in the mezz card are eth0 and eth1. Because the different nics connect to different interconnects, we weren't able to kickstart them as it's trying to kick with eth2 that mac address is not in the dhcp/pxe server.
Why does pxe boot and kickstart see the nics in different order?
We are running linux and deploying with kickstart. If the blade server has a mezz card in there for two additional nics. Those nics are seen as eth2 and eth3 during pxe but as soon as kickstart begins, it thinks the nics in the mezz card are eth0 and eth1. Because the different nics connect to different interconnects, we weren't able to kickstart them as it's trying to kick with eth2 that mac address is not in the dhcp/pxe server.
Why does pxe boot and kickstart see the nics in different order?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-27-2007 04:52 PM
тАО03-27-2007 04:52 PM
Re: Nic order on blades C-Class
I want to install the servers unattended. Installing through image is not an option due to the differences.
Daniel
Daniel
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