HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- network card driver problem
Operating System - HP-UX
1833758
Members
2699
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
04-12-2000 01:59 AM
04-12-2000 01:59 AM
network card driver problem
Hi,
I am running HP-UX 10.20 on two hosts that back up each other.
When one has its lan interfaces up, the other one has its lan interfaces down,
and viceversa. Both with the same (set of) IP addresses.
So far so good, there is no conflict because only one interface with the same
IP address is up at a given time, right? ... well, not quite.
It occasionally happens that the driver btlan4 is monitoring the interface that
is down, and in a number of cases (i.e. the cable gets disconnected momentarily
or the device at the other end of the cable goes down) then btlan4 will
interpret that something may be wrong with the card itself, prints a message,
boots the card, and bingo, it comes UP instead of DOWN. Now we have two
interfaces (itself and the counterpart interface on the other host) both up and
both with the same IP address !!.
That creates havok on the network.
Does anyone out there know how to tell btlan4 NOT to be so intelligent and NOT
to boot/monitor the interface card ?
Failing that, does anyone know how to tell it to bring the interfaces
ifconfig'ed down by default?
Any other ideas?
Thanks in advance,
Ricardo.
-------
I am running HP-UX 10.20 on two hosts that back up each other.
When one has its lan interfaces up, the other one has its lan interfaces down,
and viceversa. Both with the same (set of) IP addresses.
So far so good, there is no conflict because only one interface with the same
IP address is up at a given time, right? ... well, not quite.
It occasionally happens that the driver btlan4 is monitoring the interface that
is down, and in a number of cases (i.e. the cable gets disconnected momentarily
or the device at the other end of the cable goes down) then btlan4 will
interpret that something may be wrong with the card itself, prints a message,
boots the card, and bingo, it comes UP instead of DOWN. Now we have two
interfaces (itself and the counterpart interface on the other host) both up and
both with the same IP address !!.
That creates havok on the network.
Does anyone out there know how to tell btlan4 NOT to be so intelligent and NOT
to boot/monitor the interface card ?
Failing that, does anyone know how to tell it to bring the interfaces
ifconfig'ed down by default?
Any other ideas?
Thanks in advance,
Ricardo.
-------
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-09-2000 02:32 PM
05-09-2000 02:32 PM
Re: network card driver problem
in 10.20, i don't believe there is a way to tell a 100bt lan card to come up as s/w state DOWN by default. in 11.0, there is a variable in the /etc/rc.config.d/netconf file.
one alternative is to create a startup script that does ifconfig's it DOWN.
one idea for two systems that use the same ip address is to cluster them together in MCServiceGuard. however, that is something you will have to decide according to your particular scenario.
Sincerely,
Rashmi Kadambi
one alternative is to create a startup script that does ifconfig's it DOWN.
one idea for two systems that use the same ip address is to cluster them together in MCServiceGuard. however, that is something you will have to decide according to your particular scenario.
Sincerely,
Rashmi Kadambi
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-12-2000 06:47 AM
05-12-2000 06:47 AM
Re: network card driver problem
In /etc/rc.config/netconf where the interfaces are configured you should have the option of including the following parameter for each interface that is defined:
INTERFACE_STATE: Desired interface state at boot time. Either up or down, default is up.
This means that if the index number of 2 refers to a card that you wish to be configured but remain "down", then then entry in netconf should look like:
INTERFACE_STATE[2]="down"
If this parameter is omitted or set to "" then the default value of "up" is assigned.
INTERFACE_STATE: Desired interface state at boot time. Either up or down, default is up.
This means that if the index number of 2 refers to a card that you wish to be configured but remain "down", then then entry in netconf should look like:
INTERFACE_STATE[2]="down"
If this parameter is omitted or set to "" then the default value of "up" is assigned.
"Unfortunately you can't out-program stupidity"
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