HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: dns problem
Operating System - HP-UX
1833796
Members
4964
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
11-04-2002 07:49 AM
11-04-2002 07:49 AM
dns problem
i have a router (for example router1), it has 5 interfaces. I have a correct DNS settings (it means name router1 is resolved to all 5 interfaces addresses and all these five addresses are correctly resolved to name "router1").
my problem is that i can connect (snmp-get, ping , telnet) only to one router interface, because i have a firewall in my network (between managemnet station and router1). so, i've change dns settings to serve only one ip address , that i can connect from hpov station.
but my sniffer session says that nnm still tries to connect to other 4 addresses.
I've made a reinitialization of OV databases - still the same - NNM tries to connect to unreachable addresses even if there is no information in dns about them. i have killed nscd process and even killed dns (named) process - still my NNM tries to connect to those unreachable addresses (for example during snmp-walking). after rebooting - the same problem. any ideas?
my OS: solaris 8 with NNM 6.
my problem is that i can connect (snmp-get, ping , telnet) only to one router interface, because i have a firewall in my network (between managemnet station and router1). so, i've change dns settings to serve only one ip address , that i can connect from hpov station.
but my sniffer session says that nnm still tries to connect to other 4 addresses.
I've made a reinitialization of OV databases - still the same - NNM tries to connect to unreachable addresses even if there is no information in dns about them. i have killed nscd process and even killed dns (named) process - still my NNM tries to connect to those unreachable addresses (for example during snmp-walking). after rebooting - the same problem. any ideas?
my OS: solaris 8 with NNM 6.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-04-2002 08:11 AM
11-04-2002 08:11 AM
Re: dns problem
Hi,
You could check
/etc/defaultrouter
/etc/rc2.d/S999Routes
if any other routes are being added.
Hope it helps.
Robert-Jan.
You could check
/etc/defaultrouter
/etc/rc2.d/S999Routes
if any other routes are being added.
Hope it helps.
Robert-Jan.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-05-2002 05:14 AM
11-05-2002 05:14 AM
Re: dns problem
With SNMP on a router (multiple NIC interfaces) I generally point the snmp gets at 1 interface. Stats from the rest of the interfaces appear as offsets from that interface.
So
A.B.C.D.1 might be fe0.
A.B.C.D.2 might be fe1.
A.B.C.D.13 might be hssi1
A.B.C.D.14 might be serial4
AFAIK, you can grab _all_ of the statistics from a device through 1 interface.
So
A.B.C.D.1 might be fe0.
A.B.C.D.2 might be fe1.
A.B.C.D.13 might be hssi1
A.B.C.D.14 might be serial4
AFAIK, you can grab _all_ of the statistics from a device through 1 interface.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-05-2002 08:22 AM
11-05-2002 08:22 AM
Re: dns problem
Think you are probably in the wrong group. The Network Management/Openview Network Node Manager at http://forums.itrc.hp.com/cm/CategoryHome/1,,165,00.html
would be more appropriate.
Anyway, NNM has to be finding out about the other addresses either from its database or via SMNP on the good IP address. (I assume nslookup only shows the one address?)
Try deleting the router from all maps. Then close OpenView, and run
ovtopofix -a from a command prompt. You have to turn something else off first and I have forgotten what but it will tell you. Then restart whatever you turned off then start openview and let it find the router again. You can help it by creating the object and giving it the good IP address or just let it cook for a while. If it still tries to get to the bad addresses then best post in the correct group.
Ron
would be more appropriate.
Anyway, NNM has to be finding out about the other addresses either from its database or via SMNP on the good IP address. (I assume nslookup only shows the one address?)
Try deleting the router from all maps. Then close OpenView, and run
ovtopofix -a from a command prompt. You have to turn something else off first and I have forgotten what but it will tell you. Then restart whatever you turned off then start openview and let it find the router again. You can help it by creating the object and giving it the good IP address or just let it cook for a while. If it still tries to get to the bad addresses then best post in the correct group.
Ron
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