GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: ignite error
Operating System - HP-UX
1850938
Members
2380
Online
104056
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Knowledge Base
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Forums
Discussions
back
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
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
11-22-2005 08:14 AM
11-22-2005 08:14 AM
ignite error
Hello all:
i met problem when i add new server on ignite server. it display "could not determine if the IUX server supports archive for the hp-ux release of the system ,make_net_recovery may not work properly."
i check the old case, some one said it was tfptd issue, i check my server and client it is ok.
however it worked before, now i want to set up a dedicate backup network, and transfer all backup to use this backup network, for example. client aaa use 172 subnet before, i set up 192 subnet for backup network, and setup server aaa on 192 to aaam. and add aaam to ignite server , then meet this problem .
i don't think it relate this.
anyone has good idea?
i met problem when i add new server on ignite server. it display "could not determine if the IUX server supports archive for the hp-ux release of the system ,make_net_recovery may not work properly."
i check the old case, some one said it was tfptd issue, i check my server and client it is ok.
however it worked before, now i want to set up a dedicate backup network, and transfer all backup to use this backup network, for example. client aaa use 172 subnet before, i set up 192 subnet for backup network, and setup server aaa on 192 to aaam. and add aaam to ignite server , then meet this problem .
i don't think it relate this.
anyone has good idea?
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-22-2005 09:10 AM
11-22-2005 09:10 AM
Re: ignite error
do i need change hostname and system name by instl_adm ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-22-2005 10:00 AM
11-22-2005 10:00 AM
Re: ignite error
Shalom dongming,
I possibily interpret that you have tried to set up the new network on the same network as the old one.
Primer
host1:
ip:192.168.0.1
netmask:255.255.255.0
network is 192.168.0 host portion of the address is 1.
Under HP-UX you can not have two NIC cards operating on the same network at the same time. Usually even trying this will crash networking. Please review and if need be correct your network configuration.
Suuplement(fishing expedition):
What is the OS of the new system?
Is there a Core-Os of the new systems Os swcopy'ed to the Ignite Server.
New system and old:
swverify \*
# make sure something has not gone corrupt on us.
swlist -l product | grep -i Ignite
bdf /var there is a space requirement.
SEP
I possibily interpret that you have tried to set up the new network on the same network as the old one.
Primer
host1:
ip:192.168.0.1
netmask:255.255.255.0
network is 192.168.0 host portion of the address is 1.
Under HP-UX you can not have two NIC cards operating on the same network at the same time. Usually even trying this will crash networking. Please review and if need be correct your network configuration.
Suuplement(fishing expedition):
What is the OS of the new system?
Is there a Core-Os of the new systems Os swcopy'ed to the Ignite Server.
New system and old:
swverify \*
# make sure something has not gone corrupt on us.
swlist -l product | grep -i Ignite
bdf /var there is a space requirement.
SEP
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
11-23-2005 02:43 AM
11-23-2005 02:43 AM
Re: ignite error
Hi Sep,
thanks very much for your response.
that 's true, there are mutilple nic on ignite server, but not on same sunnet.
hostA, 172.168.1.1
192.168.1.1
what i want to do is, i set up dedicate network for backup on subnet 192.168.1.0
for all servers and let backup traffic on this subnet.
i don't know how to configure this on ignite server, so i aliase ip, such as hostAm 192.168.1.1 , and same for other servers. and then add this name to ignite server, then the problem happened.
is there other way that don't need aliase,and i configure directly ?
thanks
thanks very much for your response.
that 's true, there are mutilple nic on ignite server, but not on same sunnet.
hostA, 172.168.1.1
192.168.1.1
what i want to do is, i set up dedicate network for backup on subnet 192.168.1.0
for all servers and let backup traffic on this subnet.
i don't know how to configure this on ignite server, so i aliase ip, such as hostAm 192.168.1.1 , and same for other servers. and then add this name to ignite server, then the problem happened.
is there other way that don't need aliase,and i configure directly ?
thanks
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 2026 Hewlett Packard Enterprise Development LP