- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- LAN init script initialization file confusion
Operating System - HP-UX
1820603
Members
1714
Online
109626
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
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
Go to solution
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
08-12-2002 11:08 PM
08-12-2002 11:08 PM
Hello,
I want to enforce set up of NICs with fixed parameters on runlevel changes through init scripts.
I have found out how to change a NIC's parameters (e.g. duplex, speed, auto on|off) either by the command lanadmin or by sam.
Unfortunately the NICs will lose these settings on next reboot.
Having a look at the init scripts in /sbin/init.d that fire up the NICs I stumbled over a whole bunch of conf files that are sourced by these scripts, namely the following (as far as ether/lan stuff is concerned)
# ls -1 /etc/rc.config.d/hp[bes]*
/etc/rc.config.d/hpbase100conf
/etc/rc.config.d/hpbtlanconf
/etc/rc.config.d/hpetherconf
/etc/rc.config.d/hpsppci100conf
Now I'm getting really confused, because I don't know which of those is valid for the drivers that drive the NICs on my boxes.
They all initialize the same bunch of shell arrays that hold the parameters for speed, duplex etc. per device.
Things get even more confusing when I have a look at what drivers which drive the ethernet NICs on our boxes.
They seem to differ from box to box (guess this is owe to other chips and components on the NIC boards)
e.g.
one box uses the driver btlan1:
# ioscan -kfdbtlan1
Class I H/W Path Driver S/W State H/W Type Description
==============================================================
lan 2 10/4/8 btlan1 CLAIMED INTERFACE HP HP-PB 100 Base TX card
lan 6 10/4/16 btlan1 CLAIMED INTERFACE HP HP-PB 100 Base TX card
whereas the other uses btlan (and btlan3):
# ioscan -nf -d btlan
Class I H/W Path Driver S/W State H/W Type Description
=========================================================================
lan 2 0/5/0/0/4/0 btlan CLAIMED INTERFACE PCI Ethernet (10110
009)
lan 3 0/5/0/0/5/0 btlan CLAIMED INTERFACE PCI Ethernet (10110
009)
lan 4 0/5/0/0/6/0 btlan CLAIMED INTERFACE PCI Ethernet (10110
009)
lan 5 0/5/0/0/7/0 btlan CLAIMED INTERFACE PCI Ethernet (10110
009)
lan 7 1/12/0/0/4/0 btlan CLAIMED INTERFACE PCI Ethernet (10110
009)
lan 8 1/12/0/0/5/0 btlan CLAIMED INTERFACE PCI Ethernet (10110
009)
lan 9 1/12/0/0/6/0 btlan CLAIMED INTERFACE PCI Ethernet (10110
009)
lan 10 1/12/0/0/7/0 btlan CLAIMED INTERFACE PCI Ethernet (10110
009)
# ioscan -knf -d btlan3
Class I H/W Path Driver S/W State H/W Type Description
===================================================================
lan 0 0/0/0/0 btlan3 CLAIMED INTERFACE PCI Ethernet (10110019)
/dev/ether0
Other boxes still use other drivers.
So which of the parameter initialization files is to be edited?
/etc/rc.config.d/hpbase100conf
/etc/rc.config.d/hpbtlanconf
or
/etc/rc.config.d/hpetherconf
I want to enforce set up of NICs with fixed parameters on runlevel changes through init scripts.
I have found out how to change a NIC's parameters (e.g. duplex, speed, auto on|off) either by the command lanadmin or by sam.
Unfortunately the NICs will lose these settings on next reboot.
Having a look at the init scripts in /sbin/init.d that fire up the NICs I stumbled over a whole bunch of conf files that are sourced by these scripts, namely the following (as far as ether/lan stuff is concerned)
# ls -1 /etc/rc.config.d/hp[bes]*
/etc/rc.config.d/hpbase100conf
/etc/rc.config.d/hpbtlanconf
/etc/rc.config.d/hpetherconf
/etc/rc.config.d/hpsppci100conf
Now I'm getting really confused, because I don't know which of those is valid for the drivers that drive the NICs on my boxes.
They all initialize the same bunch of shell arrays that hold the parameters for speed, duplex etc. per device.
Things get even more confusing when I have a look at what drivers which drive the ethernet NICs on our boxes.
They seem to differ from box to box (guess this is owe to other chips and components on the NIC boards)
e.g.
one box uses the driver btlan1:
# ioscan -kfdbtlan1
Class I H/W Path Driver S/W State H/W Type Description
==============================================================
lan 2 10/4/8 btlan1 CLAIMED INTERFACE HP HP-PB 100 Base TX card
lan 6 10/4/16 btlan1 CLAIMED INTERFACE HP HP-PB 100 Base TX card
whereas the other uses btlan (and btlan3):
# ioscan -nf -d btlan
Class I H/W Path Driver S/W State H/W Type Description
=========================================================================
lan 2 0/5/0/0/4/0 btlan CLAIMED INTERFACE PCI Ethernet (10110
009)
lan 3 0/5/0/0/5/0 btlan CLAIMED INTERFACE PCI Ethernet (10110
009)
lan 4 0/5/0/0/6/0 btlan CLAIMED INTERFACE PCI Ethernet (10110
009)
lan 5 0/5/0/0/7/0 btlan CLAIMED INTERFACE PCI Ethernet (10110
009)
lan 7 1/12/0/0/4/0 btlan CLAIMED INTERFACE PCI Ethernet (10110
009)
lan 8 1/12/0/0/5/0 btlan CLAIMED INTERFACE PCI Ethernet (10110
009)
lan 9 1/12/0/0/6/0 btlan CLAIMED INTERFACE PCI Ethernet (10110
009)
lan 10 1/12/0/0/7/0 btlan CLAIMED INTERFACE PCI Ethernet (10110
009)
# ioscan -knf -d btlan3
Class I H/W Path Driver S/W State H/W Type Description
===================================================================
lan 0 0/0/0/0 btlan3 CLAIMED INTERFACE PCI Ethernet (10110019)
/dev/ether0
Other boxes still use other drivers.
So which of the parameter initialization files is to be edited?
/etc/rc.config.d/hpbase100conf
/etc/rc.config.d/hpbtlanconf
or
/etc/rc.config.d/hpetherconf
Madness, thy name is system administration
Solved! Go to Solution.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-12-2002 11:40 PM
08-12-2002 11:40 PM
Solution
Ralph,
heres the answer; it depends on which driver
Driver duplex file Description Software
btlan hpbtlanconf
btlan0 hpeisabtconf
btlan1 hpbasetconf
btlan3 hpbase100conf Internal (core) LAN card
btlan4 hpgsc100conf
btlan5 hppci100conf "external" PCI card A5230A
btlan6 hpsppci100conf V-class PCI lan card
gelan hpgelanconf GigaBit card A4926A
heres the answer; it depends on which driver
Driver duplex file Description Software
btlan hpbtlanconf
btlan0 hpeisabtconf
btlan1 hpbasetconf
btlan3 hpbase100conf Internal (core) LAN card
btlan4 hpgsc100conf
btlan5 hppci100conf "external" PCI card A5230A
btlan6 hpsppci100conf V-class PCI lan card
gelan hpgelanconf GigaBit card A4926A
Im from Palmerston North, New Zealand, but somehow ended up in London...
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
Learn About
News and Events
Support
© Copyright 2025 Hewlett Packard Enterprise Development LP