<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: snmp timeout from NNM station in Networking</title>
    <link>https://community.hpe.com/t5/networking/snmp-timeout-from-nnm-station/m-p/3076391#M716</link>
    <description>Probably a routing issue.  &lt;BR /&gt;&lt;BR /&gt;On the bad machine if UNIX/Linux &lt;BR /&gt; &lt;BR /&gt;traceroute IPofNNM&lt;BR /&gt; &lt;BR /&gt;and see where it stops.&lt;BR /&gt; &lt;BR /&gt;on a window box the command is &lt;BR /&gt; &lt;BR /&gt;tracert -d IPofNNM&lt;BR /&gt; &lt;BR /&gt;where IPofNNM is the IP address of the NNM station.&lt;BR /&gt; &lt;BR /&gt;If it goes all the way through then do a&lt;BR /&gt;  &lt;BR /&gt;nslookup NNMhostname&lt;BR /&gt;  &lt;BR /&gt;and see what it says.&lt;BR /&gt;&lt;BR /&gt;If it fails right away look at&lt;BR /&gt;&lt;BR /&gt;netstat -rn&lt;BR /&gt; &lt;BR /&gt;Try to figure out how which gateway it would use to get to the IP address of the NNM station.  If there is not a particular route to the subnet of the NNM station then look at the default route (0.0.0.0 0.0.0.0).  There should only be one.  It is easy to add a second one to a window box but it just confuses it.  The default route should point to the gateway which connects to the Internet or to the most other subnets.  If there is a second path which leads to a few subnets then you have to add routes to tell the machine how to get there.&lt;BR /&gt; &lt;BR /&gt;&lt;BR /&gt;On the NNM station do&lt;BR /&gt;  &lt;BR /&gt;nslookup badmachineshostname&lt;BR /&gt; &lt;BR /&gt;Make sure it can find it.  You can run a traceroute in the other direction to see what happens.&lt;BR /&gt;&lt;BR /&gt;If there is a sat link or other major delay in the way you can try to set the timeout to a higher value.  Options/Snmp configuration/Specific nodes&lt;BR /&gt;&lt;BR /&gt;Finally look for overfilled WAN links where packets are being dropped or for router filters or for lists of allowed snmp servers that the box want to talk to.&lt;BR /&gt;&lt;BR /&gt;Ron</description>
    <pubDate>Tue, 23 Sep 2003 10:19:44 GMT</pubDate>
    <dc:creator>Ron Kinner</dc:creator>
    <dc:date>2003-09-23T10:19:44Z</dc:date>
    <item>
      <title>snmp timeout from NNM station</title>
      <link>https://community.hpe.com/t5/networking/snmp-timeout-from-nnm-station/m-p/3076390#M715</link>
      <description>Hello,&lt;BR /&gt;My NNM station has the following problem:&lt;BR /&gt;When I make a snmp request from NNM station&lt;BR /&gt;to one single device,the request goes on timeout.&lt;BR /&gt;Cosider that:&lt;BR /&gt;-the same request from another machine on the same Lan of the NNM station has succefully completed.&lt;BR /&gt;-the same request to any device of my network has succefully completed.&lt;BR /&gt;-I've chenged the router( It isn't a router problem)&lt;BR /&gt;-It isn't a firewall problem.&lt;BR /&gt;&lt;BR /&gt;Have you any suggestion for me.&lt;BR /&gt;Thanks a lot.&lt;BR /&gt;Emiliano.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 23 Sep 2003 08:03:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/networking/snmp-timeout-from-nnm-station/m-p/3076390#M715</guid>
      <dc:creator>Emiliano Panella</dc:creator>
      <dc:date>2003-09-23T08:03:21Z</dc:date>
    </item>
    <item>
      <title>Re: snmp timeout from NNM station</title>
      <link>https://community.hpe.com/t5/networking/snmp-timeout-from-nnm-station/m-p/3076391#M716</link>
      <description>Probably a routing issue.  &lt;BR /&gt;&lt;BR /&gt;On the bad machine if UNIX/Linux &lt;BR /&gt; &lt;BR /&gt;traceroute IPofNNM&lt;BR /&gt; &lt;BR /&gt;and see where it stops.&lt;BR /&gt; &lt;BR /&gt;on a window box the command is &lt;BR /&gt; &lt;BR /&gt;tracert -d IPofNNM&lt;BR /&gt; &lt;BR /&gt;where IPofNNM is the IP address of the NNM station.&lt;BR /&gt; &lt;BR /&gt;If it goes all the way through then do a&lt;BR /&gt;  &lt;BR /&gt;nslookup NNMhostname&lt;BR /&gt;  &lt;BR /&gt;and see what it says.&lt;BR /&gt;&lt;BR /&gt;If it fails right away look at&lt;BR /&gt;&lt;BR /&gt;netstat -rn&lt;BR /&gt; &lt;BR /&gt;Try to figure out how which gateway it would use to get to the IP address of the NNM station.  If there is not a particular route to the subnet of the NNM station then look at the default route (0.0.0.0 0.0.0.0).  There should only be one.  It is easy to add a second one to a window box but it just confuses it.  The default route should point to the gateway which connects to the Internet or to the most other subnets.  If there is a second path which leads to a few subnets then you have to add routes to tell the machine how to get there.&lt;BR /&gt; &lt;BR /&gt;&lt;BR /&gt;On the NNM station do&lt;BR /&gt;  &lt;BR /&gt;nslookup badmachineshostname&lt;BR /&gt; &lt;BR /&gt;Make sure it can find it.  You can run a traceroute in the other direction to see what happens.&lt;BR /&gt;&lt;BR /&gt;If there is a sat link or other major delay in the way you can try to set the timeout to a higher value.  Options/Snmp configuration/Specific nodes&lt;BR /&gt;&lt;BR /&gt;Finally look for overfilled WAN links where packets are being dropped or for router filters or for lists of allowed snmp servers that the box want to talk to.&lt;BR /&gt;&lt;BR /&gt;Ron</description>
      <pubDate>Tue, 23 Sep 2003 10:19:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/networking/snmp-timeout-from-nnm-station/m-p/3076391#M716</guid>
      <dc:creator>Ron Kinner</dc:creator>
      <dc:date>2003-09-23T10:19:44Z</dc:date>
    </item>
  </channel>
</rss>

