Re: What determines object name for dual interface machine?
You cannot add an object to a collection if it doesn't exist in the
database by that name. So discovery is at the root of your problem. To
guarantee that an object is discovered by a particular interface, you are
correct that you will have to have an entry in the seedfile.
ovstop netmon, add that interface to the seedfile, locate the cuurent
obejct on the map and delete it from all submaps (which will remove it from
the database), then ovstart netmon and wait for it to be re-discovered.
Tivoli (NetView for UNIX) L3 Support
bryan.s.brook AT LMCO DOT COM on 07/06/98 08:13:52 AM
Please respond to NV-L AT UCSBVM.UCSB DOT EDU
To: NV-L AT UCSBVM.UCSB DOT EDU
cc: (bcc: James Shanks)
Subject: What determines object name for dual interface machine?
We are defining a collection and attempt to define it by an "object list".
Within this list we type in the hostnames of the machines to be included in
the collection. Sometimes the hostname we add isnt there. Why?
Our machines have 2 interfaces:
DNS resolved names: foo (FDDI) and foo_e (ethernet)
If I add foo to my object list -- It fails.
If I add foo_e to my object list -- It works.
Is this because foo_e was the first interface discovered for that machine?
If the topology database was dumped and rediscovered, the object name would
be whatever interface it found first?
How could we ensure the object names coincide with the "real" hostname?
Add entries for FDDI interface in the seedfile?