HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- Blade server network problem.
BladeSystem - General
1827452
Members
4163
Online
109965
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
Forums
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
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
09-24-2007 06:55 PM
09-24-2007 06:55 PM
Blade server network problem.
I had a c class blade enclosure with 4 nos of bl 460 servers.
I had installed win2k3 server on all the blades.But am not able to establish between the blades.
What to do for that?
Moreover i want login to switch.The switch which came along ieth the enclosure is not having the management port.
What to do for that?
Thanx to all for helping!
Br,
Prasanth.
I had installed win2k3 server on all the blades.But am not able to establish between the blades.
What to do for that?
Moreover i want login to switch.The switch which came along ieth the enclosure is not having the management port.
What to do for that?
Thanx to all for helping!
Br,
Prasanth.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-24-2007 07:16 PM
09-24-2007 07:16 PM
Re: Blade server network problem.
Hi,
One more Information, there two gigabit cards in the bl 460 server.I had done the teaming for the two cards and the ip was given to that teamed adapter.While we are pinging from one of the server to the other blades its showing requested timeout.Self pinging is working fine from each server and the drivers are cinfigured correctly.
RGDS,
pRASANTH
One more Information, there two gigabit cards in the bl 460 server.I had done the teaming for the two cards and the ip was given to that teamed adapter.While we are pinging from one of the server to the other blades its showing requested timeout.Self pinging is working fine from each server and the drivers are cinfigured correctly.
RGDS,
pRASANTH
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-24-2007 07:59 PM
09-24-2007 07:59 PM
Re: Blade server network problem.
Hi Prasanth,
How did you build the servers ? I know on earlier blades when cloned with RDP, that the MAC address of the network team got cloned to all of the servers. Therefore things got confused when pinging between them.
The solution was to break, then recreate the team.
Check whether this is your problem by looking at the MAC address of the team in the output of ipconfig /all
Hope this helps,
Regards,
Rob
How did you build the servers ? I know on earlier blades when cloned with RDP, that the MAC address of the network team got cloned to all of the servers. Therefore things got confused when pinging between them.
The solution was to break, then recreate the team.
Check whether this is your problem by looking at the MAC address of the team in the output of ipconfig /all
Hope this helps,
Regards,
Rob
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-02-2007 05:54 AM
10-02-2007 05:54 AM
Re: Blade server network problem.
I can confirm that if you create a NIC Team using HP Networking software the MAC address gets cloned. This is due to the MAC address being stored in the registry, which gets cloned with RDP (even if properly sysprep'd).
You could break the team and reform it, or there is a simpler one step process you can take. If you open up the HP Network Configuration Utility, and then go to properties on the Network Team, there is a tab called "Settings" which will show your current MAC address. If you click 'Restore Default' it will change the MAC address of your NIC Team from the cloned MAC to the MAC of one of your internal NICs.
You could break the team and reform it, or there is a simpler one step process you can take. If you open up the HP Network Configuration Utility, and then go to properties on the Network Team, there is a tab called "Settings" which will show your current MAC address. If you click 'Restore Default' it will change the MAC address of your NIC Team from the cloned MAC to the MAC of one of your internal NICs.
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.
Company
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP