RE: [NV-L] Linux nodes

[James Shanks <jshanks@us.ibm.com>]

I have no difficulties discovering either 32-bit nor 64-bit Linux, so long as the community string is correct and the node responds to snmpwalk. My only suggestion is the same as before. If you cannot determine the source of the problem from the netmon trace, then a call to Support is in order. But if you are not on FixPack4, I'd advise you to get there first. All of their systems will be current.

James Shanks
Level 3 Support for Tivoli NetView for UNIX and Windows
Network Availability Management
Network Management - Development
Tivoli Software, IBM Corp
"Liu, David" <david.liu@eds.com>

"Liu, David" <david.liu@eds.com>
Sent by: nv-l-bounces@lists.ca.ibm.com

11/27/2006 08:36 AM

Please respond to
Tivoli NetView Discussions <nv-l@lists.ca.ibm.com>

To	"Tivoli NetView Discussions" <nv-l@lists.ca.ibm.com>
cc
Subject	RE: [NV-L] Linux nodes

James,
 
Thanks for your reply. I made exactly what you instructed, but couldn't find the answer from the trace logs. What strange is that I found 32-bit Linux machine has no problem while only 64-bit Linux machine has the problem I described below. They are having exactly the same configurations. Any suggestions?
 
regards,
David

---

From: nv-l-bounces@lists.ca.ibm.com [mailto:nv-l-bounces@lists.ca.ibm.com] On Behalf Of James Shanks
Sent: Wednesday, November 08, 2006 5:58 PM
To: Tivoli NetView Discussions
Subject: Re: [NV-L] Linux nodes


Discovery problems are always solved the same way. Get a netmon trace.

First, verify that you have entries in /usr/OV/conf/oid_to_type and /usr/OV/conf/C/oid_to_sym for the sysObjectid that gets returned when you do you snmpwalk. I don't believe that you level of NetView provides any entries for SLES 9, so you have to add them.
MY SLES9 system returns "1.3.6.1.4.1.8072.3.2.10", so I have
1.3.6.1.4.1.8072.3.2.10:Linux:Linux UCD-SNMP Agent:W
in oid_to_type and
1.3.6.1.4.1.8072.3.2.10:Computer:Workstation # Linux
in oid_to_sym

Then edit your seed file and put your SLES9 nodes, by name or IP address, at the top of the file as the first real entries after any comments.
Next, turn on the full netmon trace,
netmon -M -1
and then reload the seed file
netmon -y

After a few minutes, examine the netmon.trace and look for your IP addresses and names in the trace and see whether you can figure out what's going on. Too confusing? Save the trace and call Support. Turn the trace off with "netmon -M 0" so the file doesn't grow too large.

James Shanks
Level 3 Support for Tivoli NetView for UNIX and Windows
Network Availability Management
Network Management - Development
Tivoli Software, IBM Corp
"Liu, David" <david.liu@eds.com>



"Liu, David" <david.liu@eds.com>
Sent by: nv-l-bounces@lists.ca.ibm.com

11/08/2006 09:10 AM
Please respond to
Tivoli NetView Discussions <nv-l@lists.ca.ibm.com>

To	"Tivoli NetView Discussions" <nv-l@lists.ca.ibm.com>
cc
Subject	[NV-L] Linux nodes


Dear list,

NV714, FP3 on Solaris.

I have some Linux nodes (SUSE 9) which need to be monitored by Netview. snmpwalk is OK, but cannot be discovered, or some discovered but after a while interface deleted by Netview (but the node is not deleted, thus showed blue in Netview, because no interface). I have browsed the archive, but couldn't find the answer. Please help.

Regards,
David_______________________________________________
NV-L mailing list
NV-L@lists.ca.ibm.com
Unsubscribe:NV-L-leave@lists.ca.ibm.com
http://lists.ca.ibm.com/mailman/listinfo/nv-l (Browser access limited to internal IBM'ers only)
_______________________________________________
NV-L mailing list
NV-L@lists.ca.ibm.com
Unsubscribe:NV-L-leave@lists.ca.ibm.com
http://lists.ca.ibm.com/mailman/listinfo/nv-l (Browser access limited to internal IBM'ers only)

_______________________________________________
NV-L mailing list
NV-L@lists.ca.ibm.com
Unsubscribe:NV-L-leave@lists.ca.ibm.com
http://lists.ca.ibm.com/mailman/listinfo/nv-l (Browser access limited to 
internal IBM'ers only)