- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Re: fail to discover & registering target server
Operating System - Linux
1752781
Members
5862
Online
108789
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
тАО12-23-2006 05:59 AM
тАО12-23-2006 05:59 AM
fail to discover & registering target server
Hello.
I am tring to build control tower server for Demo.
Everything is looking good , but when i am trying to discover & register new target server its boot from pxe - but i dont see it registered.
I look at Components Manager.
3. From Control Tower, you can monitor the registration progress by selecting Admin>Components>Components Manager. Successfully registered components appear on the Components Manager page with a green
component status icon. After a component appears on the Components Manager page with the green component status icon, the component is fully registered and ready to be managed or deployed by ControlTower.
I am sending a print screen of the target server.
maybe someone have some ideas what the problem is.
Thanks in Advance.
Shalom Klemer
I am tring to build control tower server for Demo.
Everything is looking good , but when i am trying to discover & register new target server its boot from pxe - but i dont see it registered.
I look at Components Manager.
3. From Control Tower, you can monitor the registration progress by selecting Admin>Components>Components Manager. Successfully registered components appear on the Components Manager page with a green
component status icon. After a component appears on the Components Manager page with the green component status icon, the component is fully registered and ready to be managed or deployed by ControlTower.
I am sending a print screen of the target server.
maybe someone have some ideas what the problem is.
Thanks in Advance.
Shalom Klemer
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-25-2006 11:03 PM
тАО12-25-2006 11:03 PM
Re: fail to discover & registering target server
Shalom Shalom,
I've always wanted to post that.
Can you tell me the OS of the system.
If its HP-UX, feel free to use the email form in my profile or call the main switchboard at NDS Jerusalem and ask for Shmuel Protter.
You should take the time to assign points to people that try to help you.
http://forums1.itrc.hp.com/service/forums/pageList.do?userId=BR844495&listType=unassigned&forumId=1
SEP
aka
Shmuel Protter
NDS Jerusalem
I've always wanted to post that.
Can you tell me the OS of the system.
If its HP-UX, feel free to use the email form in my profile or call the main switchboard at NDS Jerusalem and ask for Shmuel Protter.
You should take the time to assign points to people that try to help you.
http://forums1.itrc.hp.com/service/forums/pageList.do?userId=BR844495&listType=unassigned&forumId=1
SEP
aka
Shmuel Protter
NDS Jerusalem
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-02-2007 05:07 AM
тАО01-02-2007 05:07 AM
Re: fail to discover & registering target server
Hello Shalom, let me explain how the registration process works with ControlTower.
1. The Control Tower has one network interface (NIC) that is designated as the "Management Network" (it does not have to be dedicated, but recommended). That NIC is connected to the HP Blade Enclosure which has NIC1 of all Blade Servers setup in a VLAN (or hardwired in the same network subnet). This is true if the Control Tower is a DL360 or Blade Server. Note that the iLO (and iLO2) and OA (Onboard Administrator) should also be in the same "Management Network", but not mandatory. If the iLO/OA is required to be outside the "Management Network", they must have their IP's set prior to registration and if they change at any time, the blade should be deleted and re-registered.
2. Now all of the Blade Servers must be PXE booted to begin the registration process. The easiest two methods are to just dis-engage the hard drive from the Blade Server, or use the SUV adapter with a monitor and keyboard and hit the "F12" key when prompted to force a PXE boot. THIS IS A ONE TIME PROCESS, AFTER SUCCESSFULL REGISTRATION THE BOOT ORDER IS MODIFIED BY CONTROL TOWER TO ATTEMPT TO PXE BOOT EVERY TIME ! (if there are no PXE requests, the blade will move to the next device in the boot order)
You should get into the web GUI and observe the DHCP IP leases handed out by Control Tower (System, Network, DHCP Leases). Note there are IP's for the Blade Server NIC's and the iLO's, and once they are registered their status goes 'Permanent'.
If you are still unable to get Blade Servers and/or Enclosures to register, check the 'Events' log to see if there is a reason/description for this failure. (top right area of web GUI)
Also something to note... the Enclosure and Blade Server must have a serial number programmed from the factory for proper registration with Control Tower (you must also give the Rack a name in the Control Tower GUI).
Robert
1. The Control Tower has one network interface (NIC) that is designated as the "Management Network" (it does not have to be dedicated, but recommended). That NIC is connected to the HP Blade Enclosure which has NIC1 of all Blade Servers setup in a VLAN (or hardwired in the same network subnet). This is true if the Control Tower is a DL360 or Blade Server. Note that the iLO (and iLO2) and OA (Onboard Administrator) should also be in the same "Management Network", but not mandatory. If the iLO/OA is required to be outside the "Management Network", they must have their IP's set prior to registration and if they change at any time, the blade should be deleted and re-registered.
2. Now all of the Blade Servers must be PXE booted to begin the registration process. The easiest two methods are to just dis-engage the hard drive from the Blade Server, or use the SUV adapter with a monitor and keyboard and hit the "F12" key when prompted to force a PXE boot. THIS IS A ONE TIME PROCESS, AFTER SUCCESSFULL REGISTRATION THE BOOT ORDER IS MODIFIED BY CONTROL TOWER TO ATTEMPT TO PXE BOOT EVERY TIME ! (if there are no PXE requests, the blade will move to the next device in the boot order)
You should get into the web GUI and observe the DHCP IP leases handed out by Control Tower (System, Network, DHCP Leases). Note there are IP's for the Blade Server NIC's and the iLO's, and once they are registered their status goes 'Permanent'.
If you are still unable to get Blade Servers and/or Enclosures to register, check the 'Events' log to see if there is a reason/description for this failure. (top right area of web GUI)
Also something to note... the Enclosure and Blade Server must have a serial number programmed from the factory for proper registration with Control Tower (you must also give the Rack a name in the Control Tower GUI).
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