HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Networking
- >
- snmp timeout from NNM station
Networking
1835340
Members
2872
Online
110078
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-23-2003 01:03 AM
09-23-2003 01:03 AM
snmp timeout from NNM station
Hello,
My NNM station has the following problem:
When I make a snmp request from NNM station
to one single device,the request goes on timeout.
Cosider that:
-the same request from another machine on the same Lan of the NNM station has succefully completed.
-the same request to any device of my network has succefully completed.
-I've chenged the router( It isn't a router problem)
-It isn't a firewall problem.
Have you any suggestion for me.
Thanks a lot.
Emiliano.
My NNM station has the following problem:
When I make a snmp request from NNM station
to one single device,the request goes on timeout.
Cosider that:
-the same request from another machine on the same Lan of the NNM station has succefully completed.
-the same request to any device of my network has succefully completed.
-I've chenged the router( It isn't a router problem)
-It isn't a firewall problem.
Have you any suggestion for me.
Thanks a lot.
Emiliano.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-23-2003 03:19 AM
09-23-2003 03:19 AM
Re: snmp timeout from NNM station
Probably a routing issue.
On the bad machine if UNIX/Linux
traceroute IPofNNM
and see where it stops.
on a window box the command is
tracert -d IPofNNM
where IPofNNM is the IP address of the NNM station.
If it goes all the way through then do a
nslookup NNMhostname
and see what it says.
If it fails right away look at
netstat -rn
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.
On the NNM station do
nslookup badmachineshostname
Make sure it can find it. You can run a traceroute in the other direction to see what happens.
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
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.
Ron
On the bad machine if UNIX/Linux
traceroute IPofNNM
and see where it stops.
on a window box the command is
tracert -d IPofNNM
where IPofNNM is the IP address of the NNM station.
If it goes all the way through then do a
nslookup NNMhostname
and see what it says.
If it fails right away look at
netstat -rn
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.
On the NNM station do
nslookup badmachineshostname
Make sure it can find it. You can run a traceroute in the other direction to see what happens.
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
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.
Ron
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP