To: | "'nv-l@lists.us.ibm.com'" <nv-l@lists.us.ibm.com> |
---|---|
Subject: | RE: [nv-l] seed file |
From: | "Evans, Bill" <Bill.Evans@hq.doe.gov> |
Date: | Mon, 8 Mar 2004 15:21:39 -0500 |
Delivery-date: | Mon, 08 Mar 2004 20:30:33 +0000 |
Envelope-to: | nv-l-archive@lists.skills-1st.co.uk |
Reply-to: | nv-l@lists.us.ibm.com |
Sender: | owner-nv-l@lists.us.ibm.com |
Another important item is to use only one name in DNS for each router. All the interfaces on that device should resolve to the same name. The name should resolve to the loopback address for the router. This gives you the best functioning of NetView although there is a continuing argument from many who want a unique DNS name for each interface for other reasons. I find the device name qualified by the interface name (e.g. Router.Serial1/0) gives the uniqueness I need for interfaces. When necessary I override the DNS with a local hosts file to achieve this. In my present situation the DNS has only the loopback address and I use hosts to resolve the other names. Bill Evans -----Original Message-----
Chris,
netmon reads the entries from the seedfile, pings the node, if it
If you put multiple IPs in the seedfile for the same device it will be
The best practice is to add a single interface from each device. Paul Christopher J Petrina wrote: >
|
<Prev in Thread] | Current Thread | [Next in Thread> |
---|---|---|
|
Previous by Date: | RE: [nv-l] Node Display not synchronized, Stephen Hochstetler |
---|---|
Next by Date: | RE: [nv-l] seed file, CMazon |
Previous by Thread: | Re: [nv-l] seed file, Paul |
Next by Thread: | RE: [nv-l] seed file, CMazon |
Indexes: | [Date] [Thread] [Top] [All Lists] |
Archive operated by Skills 1st Ltd
See also: The NetView Web