|
The thing to do if you really want to use noniptopology is to get out the NetView Programming Guide and read it thoroughly on the topics of gtmd, noniptopology, and xxmap, because there is a serious flaw in your understanding.
None of those things provides automatic device management of any sort. You have to do programming in order for them to work. Basically they comprise a series of APIs to place, update, and manage non-ip things on a submap you can see right along with the IP Internet map where all the familiar IP devices reside.
But that's not what you want to do at all. All you really have is an IP device which does not respond to ping that you can manage with SNMP. It has to be an IP device, else you could not communicate with it using snmpget, which uses an IP transport.
The $ entry in the seed file is for netmon, which manages IP topology. The $ in the seed file says to check status on this device using SNMP, but that does not enable netmon to discover the device, because discovery requires that ping must also be enabled. To have a device monitored by SNMP, which cannot be discovered because you cannot ping it, you would have to add it to the database manually using the loadhosts command, which has been the subject of many appends here lately.
Miss those appends? You can check them out in the archives, which are kept by one helpful user at
http://lists.skills-1st.co.uk/mharc/html/nv-l/ . They are public and searchable.
HTH
James Shanks
Level 3 Support for Tivoli NetView for UNIX and Windows
Tivoli Software / IBM Software Group
 ray.smith@clorox.com
ray.smith@clorox.com
Sent by: owner-nv-l@lists.us.ibm.com
02/25/04 05:20 PM
|
|
All,
The problem is to have NetView auto discover the device using the $snmpget and future similar devices and add the xxmap. At this time it is not performing this operation.
I am attempting to understand the gtmd and noniptopod in order to manage a device for node up that does not support icmp. The device does support snmp and I can walk and get against the device with no problems. The device does return ifadminstatus and ifoperstatus as UP, which I thought I read to be expected for this type of management.
Since the walk does return the expected status I have not loaded the device specific mibs as of yet.
The way it is configured at this time is;
added to xnmsnmpconf with the correct snmp names.
location.conf has been updated so the device will map there
seed file has the entry $192.168.1.1 for snmp status checking
What do I do next?
Although ovstatus shows all gtmd and other daemons are running and well behaved. The noniptopod is NON_WELL_BEHAVED
Ray Smith
IS Engineer
The Clorox Services Company
925-425-4363
|
