HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Ignite Server
Operating System - HP-UX
1834089
Members
2484
Online
110063
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
06-01-2002 07:17 AM
06-01-2002 07:17 AM
Ignite Server
When I create the network recovery archive for a V client, the following message is display:
"client" is not network bootable. See the man page for make_boot_tape for information on the archive you create.
Why aren't V servers network bootable and what is the fix for this?
Thanks
"client" is not network bootable. See the man page for make_boot_tape for information on the archive you create.
Why aren't V servers network bootable and what is the fix for this?
Thanks
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-02-2002 12:29 PM
06-02-2002 12:29 PM
Re: Ignite Server
Hi,
We had V2200 server and it is written in an HP document that V class servers cannot boot thro network. It didnt use to boot from tape drives also but later on HP solved the problem by releasing a new firmware. I dont know whether a new firmware has been released for network booting. Check out with HP.
Hi pls go thro this document
http://support2.itrc.hp.com/service/cki/docDisplay.do?docId=200000024626492
Piyush
We had V2200 server and it is written in an HP document that V class servers cannot boot thro network. It didnt use to boot from tape drives also but later on HP solved the problem by releasing a new firmware. I dont know whether a new firmware has been released for network booting. Check out with HP.
Hi pls go thro this document
http://support2.itrc.hp.com/service/cki/docDisplay.do?docId=200000024626492
Piyush
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-10-2002 06:38 AM
06-10-2002 06:38 AM
Re: Ignite Server
Hello,
you can find to /opt/ignite/share/doc/release_note informations about network bootable servers. This information is this one :
4.3 Networking Issues
======================
* Ignite-UX HP network interface support matrix.
The only interfaces supported for doing a network boot from a
server are the built-in ethernet (10-Base-T, and 100-Base-T)
on all S700's and the A, D, K, N, and R-class S800's. All other
interfaces that are supported can only be used when the system
is booted using the "bootsys" command, or booted from an
Ignite-UX tape or CD-ROM (see bootsys(1m) and make_boot_tape(1M)).
Type | SW prod * | driver | amount of support | Notes
-------------+-------------+--------+-------------------+--------
10-base-T | core-OS | lan2 | full, with netboot| 7
10-base-T | core-OS | lan3 | full | 7
PCI 4 Port | J4254AA | btlan | may work | 2
EISA 100BT | J2781AA_APZ | btlan0 | full | 1
HPPB 100BT | J2760AA_APZ | btlan1 | full | 1,7
PCI 100BT | 10.20-ACE | btlan3 | full, with netboot| 7
HSC/GSC 100BT| J3621AA_APZ | btlan4 | full | 7
PCI 100BT | B5509BA_APZ | btlan5 | reported to work | 2
EISA 100VG | J2695AA_APZ | vglan0 | may work | 2
EISA FDDI | J2648AA_APZ | fddi0 | full - see note | 1,3
HPPB FDDI | J2157A_APZ | fddi | full |
735/755 FDDI | A2665A_APZ | fddi2 | full |
HSC/GSC FDDI | J3702AA_APZ | fddi3 | may work | 2
EISA token | J2165A_APZ | token | reported to work | 2,4
HPPB token | J2166A_APZ | token2 | may work | 2
712 token | A4011B_APZ | token3 | may work | 2
ATM | | | None | 5,6
PCI Gigabit | J1642AA | gelan | full |
Hope this answer your question.
Regards
Fabrice
you can find to /opt/ignite/share/doc/release_note informations about network bootable servers. This information is this one :
4.3 Networking Issues
======================
* Ignite-UX HP network interface support matrix.
The only interfaces supported for doing a network boot from a
server are the built-in ethernet (10-Base-T, and 100-Base-T)
on all S700's and the A, D, K, N, and R-class S800's. All other
interfaces that are supported can only be used when the system
is booted using the "bootsys" command, or booted from an
Ignite-UX tape or CD-ROM (see bootsys(1m) and make_boot_tape(1M)).
Type | SW prod * | driver | amount of support | Notes
-------------+-------------+--------+-------------------+--------
10-base-T | core-OS | lan2 | full, with netboot| 7
10-base-T | core-OS | lan3 | full | 7
PCI 4 Port | J4254AA | btlan | may work | 2
EISA 100BT | J2781AA_APZ | btlan0 | full | 1
HPPB 100BT | J2760AA_APZ | btlan1 | full | 1,7
PCI 100BT | 10.20-ACE | btlan3 | full, with netboot| 7
HSC/GSC 100BT| J3621AA_APZ | btlan4 | full | 7
PCI 100BT | B5509BA_APZ | btlan5 | reported to work | 2
EISA 100VG | J2695AA_APZ | vglan0 | may work | 2
EISA FDDI | J2648AA_APZ | fddi0 | full - see note | 1,3
HPPB FDDI | J2157A_APZ | fddi | full |
735/755 FDDI | A2665A_APZ | fddi2 | full |
HSC/GSC FDDI | J3702AA_APZ | fddi3 | may work | 2
EISA token | J2165A_APZ | token | reported to work | 2,4
HPPB token | J2166A_APZ | token2 | may work | 2
712 token | A4011B_APZ | token3 | may work | 2
ATM | | | None | 5,6
PCI Gigabit | J1642AA | gelan | full |
Hope this answer your question.
Regards
Fabrice
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
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP