- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Ignite from secondary Lan
Operating System - HP-UX
1752328
Members
5619
Online
108786
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
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
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
02-09-2004 11:51 AM
02-09-2004 11:51 AM
Ignite from secondary Lan
I have an L3000 server that has 2 nic's, 1x 10/100 + 1x 1Gb. The server is set up using the 10/100 as primary Lan. Using ignite I can configure clients on the 10/100 network, however I cannot configure clients on the Gb network.
I require the L3000 to carry out "make_network_recovery" from the Gb network. With the aim to store the images on the L3000 and then cut these images to an ignite tape/CD/DVD. I am not able to change the primary Lan as the server acts as a management server for ITO, NNM, DP for hosts on the 10/100 network.
I have tried altering the IP address in the "instl_adm -d" as per previous posts, but this has to do with booting a client server to the ignite server to start a network recovery.
I require the L3000 to carry out "make_network_recovery" from the Gb network. With the aim to store the images on the L3000 and then cut these images to an ignite tape/CD/DVD. I am not able to change the primary Lan as the server acts as a management server for ITO, NNM, DP for hosts on the 10/100 network.
I have tried altering the IP address in the "instl_adm -d" as per previous posts, but this has to do with booting a client server to the ignite server to start a network recovery.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-09-2004 12:06 PM
02-09-2004 12:06 PM
Re: Ignite from secondary Lan
There is no problem doing this.
The only thing you can not do is boot off the GB LAN.
Ignite requires the clients boot off the built in lan card.
You can boot of built in and carry the transfer out on the GB LAN.
instl_adm -d > file
Edit the file to set your speeds 1000BT Autonegotiate stuff like that.
instl_adm -f file
You are done.
So long as you boot the client off the built in, the rest of the transfer will take place at GB speeds on the GB Lan.
See man instl_adm for more details.
make_net_recovery only requires a valid NFS mount on the target server to work.
Do not change the primary LAN.
Please post your make_net_recvoery script and the /etc/exports file on the target server.
If you are having trouble, I can recommend changes and this should work for you.
SEP
The only thing you can not do is boot off the GB LAN.
Ignite requires the clients boot off the built in lan card.
You can boot of built in and carry the transfer out on the GB LAN.
instl_adm -d > file
Edit the file to set your speeds 1000BT Autonegotiate stuff like that.
instl_adm -f file
You are done.
So long as you boot the client off the built in, the rest of the transfer will take place at GB speeds on the GB Lan.
See man instl_adm for more details.
make_net_recovery only requires a valid NFS mount on the target server to work.
Do not change the primary LAN.
Please post your make_net_recvoery script and the /etc/exports file on the target server.
If you are having trouble, I can recommend changes and this should work for you.
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
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