To: | nv-l@lists.tivoli.com |
---|---|
Subject: | RE: Problem with netmon |
From: | "James Shanks" <jshanks@us.ibm.com> |
Date: | Mon, 29 Oct 2001 14:09:53 -0500 |
This is a multipart message in MIME format. Stephen - If you just type "ping <ip_address> or ping <hostname> from the command line and it fails, that is NOT a NetView problem. Ping by itself is a TCP/IP primitive and part of the TCP/IP stack maintained by AIX as part of the base OS. If ping is failing then you have some kind of basic TCP/IP configuration issue. Sorry but problems of that fundamental a level are not my area of expertise. Best I can suggest is that you use SMIT to check the config and restart your interface if it is down. James Shanks Level 3 Support for Tivoli NetView for UNIX and NT Tivoli Software / IBM Software Group "Olson, Stephen J" <stolson@state.pa.us> Sent by: owner-nv-l@tkg.com 10/29/2001 12:58 PM Please respond to IBM NetView Discussion To: "'IBM NetView Discussion'" <nv-l@tkg.com> cc: Subject: RE: [NV-L] Problem with netmon James, I have some good news and some bad news. Good news is the stopsrc/startsrc worked to get netmon up. Bad news is I cannot ping any device off the local subnet. The router is OK, I can ping the devices from an NT desktop pc, but when I ping from my Netview box I get .. __________________________________________________ PING 10.35.135.1: (10.35.135.1): 56 data bytes 0821-069 ping: sendto: Cannot reach the destination network. ping: wrote 10.35.135.1 64 chars, ret=-1 0821-069 ping: sendto: Cannot reach the destination network. ping: wrote 10.35.135.1 64 chars, ret=-1 0821-069 ping: sendto: Cannot reach the destination network. ping: wrote 10.35.135.1 64 chars, ret=-1 _________________________________________________ My netview maps indicate everything is down, but it's not. Any ideas are greatly appreciated. Steve Olson -----Original Message----- From: James Shanks [mailto:jshanks@us.ibm.com] Sent: Monday, October 29, 2001 11:12 AM To: IBM NetView Discussion Subject: Re: [NV-L] Problem with netmon Have you tried just stopping and restarting snmpd? The MIB message is usually NOT the problem unless you don't have the default set which includes rfc1213-MIB-II loaded. Do "stopsrc -s snmpd", wait a few seconds, then "startsrc -s snmpd" and see if it restarts. Count to ten and ovstart netmon. Doesn't help? then check that your /etc/hosts has these two entries first: 127.0.0.1 loopback localhost <your_ip_address> <your_hostname> and that xnmsnmpconf has entries for BOTH of these if you are not using "public" as the default community name. Try an snmpwalk of your own box and see if it works (don't specify the community --let it default). If it does, then netmon should start. If it doesn't then I don't know what to tell you. James Shanks Level 3 Support for Tivoli NetView for UNIX and NT Tivoli Software / IBM Software Group "Olson, Stephen J" <stolson@state.pa.us> Sent by: owner-nv-l@tkg.com 10/29/2001 10:42 AM Please respond to IBM NetView Discussion To: "'IBM NetView Discussion'" <nv-l@tkg.com> cc: Subject: [NV-L] Problem with netmon Greetings to all, First, I may be a little cranky this morning since our Netview box went down after an extended power outage, so I hope I wasn't too harsh with David about his autoresponder. :) AIX 4.3 and netview 5.2 (I know, I know, upgrade!!!) Anyway, this has happened in the past and all I have ever done is restore to solve the problem. If the machine has an abrupt shutdown, netmon will not start. I get the following message ... ____________________________________________________________________- Cannot communicate with SNMP Agent via loopback address (127.0.0.1); it is either not running or has been configured with a community name different from that configured into TME 10 NetView for this system. If a community name ha s been configured into the SNMP Agent, that community name must be configured via xnmsnmpconf and /usr/OV/conf/ovsnmp.conf for address 127.0.0.1 as well as for the hostname or IP address of this system. Or, the /usr/OV/conf/snmpmib and /usr/OV/conf/snmpmib.bin files are corrupted and need to be rebuilt using the Maintain->Rebuild MIB binary file with installation MIB defaults option in smit _____________________________________________________________________ When I tried to rebuild the files, it *really* screwed things up. Any ideas? Thanks in advance, Steve Olson PA State Police _________________________________________________________________________ NV-L List information and Archives: http://www.tkg.com/nv-l _________________________________________________________________________ NV-L List information and Archives: http://www.tkg.com/nv-l Stephen - If you just type "ping <ip_address> or ping <hostname> from the command line and it fails, that is NOT a NetView problem. Ping by itself is a TCP/IP primitive and part of the TCP/IP stack maintained by AIX as part of the base OS. If ping is failing then you have some kind of basic TCP/IP configuration issue. Sorry but problems of that fundamental a level are not my area of expertise. Best I can suggest is that you use SMIT to check the config and restart your interface if it is down. James Shanks Level 3 Support for Tivoli NetView for UNIX and NT Tivoli Software / IBM Software Group
James, I have some good news and some bad news. Good news is the stopsrc/startsrc worked to get netmon up. Bad news is I cannot ping any device off the local subnet. The router is OK, I can ping the devices from an NT desktop pc, but when I ping from my Netview box I get .. __________________________________________________ PING 10.35.135.1: (10.35.135.1): 56 data bytes 0821-069 ping: sendto: Cannot reach the destination network. ping: wrote 10.35.135.1 64 chars, ret=-1 0821-069 ping: sendto: Cannot reach the destination network. ping: wrote 10.35.135.1 64 chars, ret=-1 0821-069 ping: sendto: Cannot reach the destination network. ping: wrote 10.35.135.1 64 chars, ret=-1 _________________________________________________ My netview maps indicate everything is down, but it's not. Any ideas are greatly appreciated. Steve Olson -----Original Message----- From: James Shanks [mailto:jshanks@us.ibm.com] Sent: Monday, October 29, 2001 11:12 AM To: IBM NetView Discussion Subject: Re: [NV-L] Problem with netmon Have you tried just stopping and restarting snmpd? The MIB message is usually NOT the problem unless you don't have the default set which includes rfc1213-MIB-II loaded. Do "stopsrc -s snmpd", wait a few seconds, then "startsrc -s snmpd" and see if it restarts. Count to ten and ovstart netmon. Doesn't help? then check that your /etc/hosts has these two entries first: 127.0.0.1 loopback localhost <your_ip_address> <your_hostname> and that xnmsnmpconf has entries for BOTH of these if you are not using "public" as the default community name. Try an snmpwalk of your own box and see if it works (don't specify the community --let it default). If it does, then netmon should start. If it doesn't then I don't know what to tell you. James Shanks Level 3 Support for Tivoli NetView for UNIX and NT Tivoli Software / IBM Software Group "Olson, Stephen J" <stolson@state.pa.us> Sent by: owner-nv-l@tkg.com 10/29/2001 10:42 AM Please respond to IBM NetView Discussion To: "'IBM NetView Discussion'" <nv-l@tkg.com> cc: Subject: [NV-L] Problem with netmon Greetings to all, First, I may be a little cranky this morning since our Netview box went down after an extended power outage, so I hope I wasn't too harsh with David about his autoresponder. :) AIX 4.3 and netview 5.2 (I know, I know, upgrade!!!) Anyway, this has happened in the past and all I have ever done is restore to solve the problem. If the machine has an abrupt shutdown, netmon will not start. I get the following message ... ____________________________________________________________________- Cannot communicate with SNMP Agent via loopback address (127.0.0.1); it is either not running or has been configured with a community name different from that configured into TME 10 NetView for this system. If a community name ha s been configured into the SNMP Agent, that community name must be configured via xnmsnmpconf and /usr/OV/conf/ovsnmp.conf for address 127.0.0.1 as well as for the hostname or IP address of this system. Or, the /usr/OV/conf/snmpmib and /usr/OV/conf/snmpmib.bin files are corrupted and need to be rebuilt using the Maintain->Rebuild MIB binary file with installation MIB defaults option in smit _____________________________________________________________________ When I tried to rebuild the files, it *really* screwed things up. Any ideas? Thanks in advance, Steve Olson PA State Police _________________________________________________________________________ NV-L List information and Archives: http://www.tkg.com/nv-l _________________________________________________________________________ NV-L List information and Archives: http://www.tkg.com/nv-l |
<Prev in Thread] | Current Thread | [Next in Thread> |
---|---|---|
|
Previous by Date: | RE: Problem with netmon, Olson, Stephen J |
---|---|
Next by Date: | ovwdb filling up with objects, Duble, Ethan |
Previous by Thread: | RE: Problem with netmon, Olson, Stephen J |
Next by Thread: | RE: Problem with netmon, Anthony Roberts |
Indexes: | [Date] [Thread] [Top] [All Lists] |
Archive operated by Skills 1st Ltd
See also: The NetView Web