- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Can't set my Ignite Client to do 100FDX... anyothe...
Categories
Company
Local Language
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
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
Community
Resources
Forums
Blogs
- 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
тАО07-09-2008 07:39 AM
тАО07-09-2008 07:39 AM
I can Ignite alright but since our switch is set to 100FDX and I can't have the below at all work to plumb the client's lan to 100FDX -- my ignite is agonizingly slow. I can't boot accross the LAN using this card.
My INSTALLFS and WINSTALLFS are correct:
iux01# head IINSTALLFS
# instl_adm defaults:
# NOTE: Manual additions between the lines containing "instl_adm defaults"
# and "end instl_adm defaults" will not be preserved.
server="192.168.1.77"
netmask[]="0xffffff00"
route_gateway[0]="192.168.1.1"
route_destination[0]="default"
( lan[].driver == "btlan" | lan[].driver ~ "gelan" )
{
_hp_lanadmin_args="-X 100FD"
[ /opt/ignite/boot/Rel_B.11.23 ]
root@thptem1b # head -20 IINSTALLFS
# instl_adm defaults:
# NOTE: Manual additions between the lines containing "instl_adm defaults"
# and "end instl_adm defaults" will not be preserved.
server="192.168.1.77"
netmask[]="0xffffff00"
route_gateway[0]="192.168.1.1"
route_destination[0]="default"
( lan[].driver == "btlan" | lan[].driver ~ "gelan" )
{
_hp_lanadmin_args="-X 100FD"
}
env_vars += "TZ=PST8PDT"
# end instl_adm defaults.
# head WINSTALLFS
# instl_adm defaults:
# NOTE: Manual additions between the lines containing "instl_adm defaults"
# and "end instl_adm defaults" will not be preserved.
server="150.234.120.91"
netmask[]="0xffffff00"
route_gateway[0]="150.234.120.3"
route_destination[0]="default"
( lan[].driver == "btlan" | lan[].driver ~ "gelan" )
{
_hp_lanadmin_args="-X 100FD"
[ /opt/ignite/boot/Rel_B.11.23 ]
root@thptem1b # head -20 WINSTALLFS
# instl_adm defaults:
# NOTE: Manual additions between the lines containing "instl_adm defaults"
# and "end instl_adm defaults" will not be preserved.
server="150.234.120.91"
netmask[]="0xffffff00"
route_gateway[0]="150.234.120.3"
route_destination[0]="default"
( lan[].driver == "btlan" | lan[].driver ~ "gelan" )
{
_hp_lanadmin_args="-X 100FD"
}
env_vars += "TZ=PST8PDT"
# end instl_adm defaults.
I can't move the drop to the CoreIO lan.
Is there another trick to say tweak the client's config file so that on plumb up of the client's lan -- it invokes lanadmin? Maybe drop to a comand line on Ignite-UX?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-09-2008 07:45 AM
тАО07-09-2008 07:45 AM
Re: Can't set my Ignite Client to do 100FDX... anyother clues?
Can you paste in 'ioscan -funC lan'. And verify the lan drivers for new patches?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-09-2008 07:50 AM
тАО07-09-2008 07:50 AM
Re: Can't set my Ignite Client to do 100FDX... anyother clues?
Here it is, I am using lan1
# ioscan -funC lan
Class I H/W Path Driver S/W State H/W Type Description
==================================================================
lan 0 0/0/0/0 btlan CLAIMED INTERFACE HP PCI 10/100Base-TX Core
/dev/diag/lan0 /dev/ether0 /dev/lan0
lan 1 0/5/0/0 btlan CLAIMED INTERFACE HP A5230A/B5509BA PCI 10/100Base-TX Addon
/dev/diag/lan1 /dev/ether1 /dev/lan1
lan 2 1/12/0/0 btlan CLAIMED INTERFACE HP A5230A/B5509BA PCI 10/100Base-TX Addon
/dev/diag/lan2 /dev/ether2 /dev/lan2
And here's the snippet of the client's install log: (Notice, there's no even lanadmin attempts by the IUX to plumb lan1 to 100FDX)..
======= 07/08/08 21:47:35 EDT HP-UX Installation Initialization. (Tue Jul 08
21:47:35 EDT 2008)
@(#) Ignite-UX Revision C.6.7.79
@(#) install/init (opt) $Revision: 10.412 $
* Scanning system for IO devices...
* Querying disk device: 0/8/0/0.5.136.0.7.15.3 ...
* Querying disk device: 0/8/0/0.5.136.0.7.15.5 ...
* Querying disk device: 1/2/0/0.6.136.0.7.15.3 ...
* Querying disk device: 1/2/0/0.6.136.0.7.15.5 ...
NOTE: Default (boot) source does not appear to be a valid (or complete)
install source, switching source to Network
* Setting keyboard language.
* Could not get DHCP information. No host specific network defaults
will be supplied. (dhcpclient returned: 9)
* Bringing up Network (lan1)
add net default: gateway 192.168.1.1
* NFS mounting clients directory.
* Using client directory: /var/opt/ignite/clients/0x00306E21D5C6
* Checking configuration for consistency...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-09-2008 07:53 AM
тАО07-09-2008 07:53 AM
Re: Can't set my Ignite Client to do 100FDX... anyother clues?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-09-2008 07:53 AM
тАО07-09-2008 07:53 AM
SolutionI had a lot of Google hits with "+100FD +Ignite +site:itrc.hp.com". Here's one:
http://forums12.itrc.hp.com/service/forums/questionanswer.do?admit=109447627+1215618680335+28353475&threadId=883526
Pete
Pete
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-09-2008 07:58 AM
тАО07-09-2008 07:58 AM
Re: Can't set my Ignite Client to do 100FDX... anyother clues?
I think this tracks my reading in IUX. That lan settings will only work if it is an LAN boot. So I guess the thread suggests that I need to rehash my boot tape then...
Ok will try sir.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-09-2008 12:26 PM
тАО07-09-2008 12:26 PM
Re: Can't set my Ignite Client to do 100FDX... anyother clues?
Here is a link that might be helpful:
http://docs.hp.com/en/B2355-90772/ch08s01.html
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-09-2008 12:37 PM
тАО07-09-2008 12:37 PM
Re: Can't set my Ignite Client to do 100FDX... anyother clues?
It turns out as the good Ignite-UX manual states -- instal_adm setting ON the Ignite Server only affects LAN booted install clients.
For Media booted (tape or CD helped clients) - the media's INSTALLFS/WINSTALLFS files need to have that directive.
So: (am doing this from a 11.11 system with no tape drive)
From your Ignite server:
instal_adm -d >cfg
add: _hp_lanadmin_args="-X 100FD"
Create your media lif:
/opt/ignite/bin/make_medialif -m -l /var/tmp/new_lif_file -d /var/tmp -r B.11.23 -R
-R
Bring the new_lif_file to the client with the writable boot tape, then create the boot tape:
/usr/bin/dd if=/var/tmp/new_lif_file of=/dev/rmt/0m bs=2k
Boot from TAPE and Ignite from your Igniet-Server and your LAN regardless of instance wil now be plumbed up to 100FDX.
Awesome! Learned something new on the internals of IUX today!
Thanks all!