GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: new lan interface stops all dce traffic
Operating System - HP-UX
1855265
Members
6862
Online
104109
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
Knowledge Base
Forums
Discussions
- Cloud Mentoring and Education
- Software - General
- HPE OneView
- HPE Ezmeral Software platform
- HPE OpsRamp
Knowledge Base
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
03-18-2000 07:54 AM
03-18-2000 07:54 AM
new lan interface stops all dce traffic
HP9000-800/K series HP-UX 10.20
We just installed a new lan card (100BT) which is
on "lan3". We edited the /etc/rc.config.d/netconf
and rebooted and everything worked fine. All nfs
etc were fine.
The problem was, our terminal connections via the
DCE program lost communications, and we
were forced to fallback to the lan0 10B interface.
I couldn't find any reference within the dce-manager
program to be able to select a particuliar lan interface.
We just installed a new lan card (100BT) which is
on "lan3". We edited the /etc/rc.config.d/netconf
and rebooted and everything worked fine. All nfs
etc were fine.
The problem was, our terminal connections via the
DCE program lost communications, and we
were forced to fallback to the lan0 10B interface.
I couldn't find any reference within the dce-manager
program to be able to select a particuliar lan interface.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-19-2000 04:57 PM
03-19-2000 04:57 PM
Re: new lan interface stops all dce traffic
what specific model(s) of K-class out of interest ? ....K210 ?
FYI :
(1) "DCE utilities and applications open /dev/lan0 (or, depending on the
configuration of the local hosts's
network interfaces, and other /dev/lan* file) in order to obtain the local
host's IEEE 802 address.
This address is used to generate UUIDs."
(2) Page 10-10 'Restricting RPC Addresses'
"The runtime now looks for a RPC_SUPPORTED_NETADDRS
env variable, which allows a user to restrict the
network addresses that a DCE server will advertise in
the namespace/endpoint-map.If this env var is set, only the addresses in the
list will be advertised in the namespace/endpoint-map.Addresses not found on
the list will be excluded from the server's list of available addresses.
The format of the of the RPC_SUPPORTED_NETADDRS string
is as follows:
RPC_SUPPORTED_NETADDRS=protseq:netaddr[,protseq:netaddr]
example:
export RPC_SUPPORTED_NETADDRS=ip:myhost
OR
export RPC_SUPPORTED_NETADDRS=ip:10.3.2.1
will force any servers started in the current shell to support only the
addresses with the name 'myhost' and the network address 10.3.2.1."
So you may have to use the env variable
RPC_SUPPORTED_NETADDRS in multi-lan card
systems that use DCE.
In your 3 lan card system ?, if you are really planning to use all 3 lan cards,
then you have to set the RPC_SUPPORTED_NETADDRS for each of the 3 lan cards
so that DCE can use all 3 lan cards.
The above answer is from a DCE point of view and dependant upon the typpe of
failure, the applications effected and their errors : From a network
perspective checking netstat -rn and using route add may help ?
Alex
FYI :
(1) "DCE utilities and applications open /dev/lan0 (or, depending on the
configuration of the local hosts's
network interfaces, and other /dev/lan* file) in order to obtain the local
host's IEEE 802 address.
This address is used to generate UUIDs."
(2) Page 10-10 'Restricting RPC Addresses'
"The runtime now looks for a RPC_SUPPORTED_NETADDRS
env variable, which allows a user to restrict the
network addresses that a DCE server will advertise in
the namespace/endpoint-map.If this env var is set, only the addresses in the
list will be advertised in the namespace/endpoint-map.Addresses not found on
the list will be excluded from the server's list of available addresses.
The format of the of the RPC_SUPPORTED_NETADDRS string
is as follows:
RPC_SUPPORTED_NETADDRS=protseq:netaddr[,protseq:netaddr]
example:
export RPC_SUPPORTED_NETADDRS=ip:myhost
OR
export RPC_SUPPORTED_NETADDRS=ip:10.3.2.1
will force any servers started in the current shell to support only the
addresses with the name 'myhost' and the network address 10.3.2.1."
So you may have to use the env variable
RPC_SUPPORTED_NETADDRS in multi-lan card
systems that use DCE.
In your 3 lan card system ?, if you are really planning to use all 3 lan cards,
then you have to set the RPC_SUPPORTED_NETADDRS for each of the 3 lan cards
so that DCE can use all 3 lan cards.
The above answer is from a DCE point of view and dependant upon the typpe of
failure, the applications effected and their errors : From a network
perspective checking netstat -rn and using route add
Alex
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