snmpwalk may fail with error Timeout: No Response from "hostname" when there are more than 1000 TCP or UDP connections
(Doc ID 1357800.1)
Last updated on FEBRUARY 03, 2019
Applies to:Solaris Operating System - Version 11.1 to 11.3 [Release 11.0]
Solaris Operating System - Version 10 3/05 to 10 1/13 U11 [Release 10.0]
Information in this document applies to any platform.
The Solaris 10 or Solaris 11 system would be running the Solaris SNMP Agent, SMA, or a public domain version of Net-SNMP when this issue would occur.
When issuing a snmpwalk command to query the the system the snmpwalk may fail with the following error:
Timeout: No Response from "hostname"
This can occur when there are more than 1000 TCP connections, in any number of states, present in the system's TCP connection table when the command is executed. In most cases of this error it will take 8000 to 15000 connections to trigger the failure.
This mib cache size limitation can also occur with UDP connections.
In other circumstances it be may observed that Solaris 10's SMA agent process, snmpd, consumes a large amount of CPU when there are 10000 to 15000 connections for a sustained period of time or may core dump with a SIGSEGV.
One method of determining the number of TCP connections currently open on the Solaris 10 system would be to run a series of netstat -an commands, note the number of connections in each state, and then totaling the values for a overall number.
netstat-an.out | grep LISTEN | wc -l
netstat-an.out | grep BOUND | wc -l
netstat-an.out | grep ESTABLISHED | wc -l
netstat-an.out | grep CLOSE_WAIT | wc -l
netstat-an.out | grep TIME_WAIT | wc -l
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document