'snmpwalk' command fails with "Timeout: No Response from" when using SNMPv2 to query VSX OID branch 1.3.6.1.4.1.2620.1.16 on VSX machine with large number of Virtual Systems

Support Center > Search Results > SecureKnowledge Details

Technical Level

Solution ID	sk97947
Technical Level
Product	VSX, Quantum Appliances, Quantum Scalable Chassis
Version	R75.40VS, R76, R77, R77.10, R77.20, R77.30
OS	Gaia
Platform / Model	2000, 4000, 12000 VSX, 21000 VSX, 61000, Crossbeam, IP1280, IP2450, Intel/PC, Power-1, UTM-1, VSX-1, 41000, 13000
Date Created	30-Dec-2013
Last Modified	13-Aug-2015

Symptoms

'snmpwalk' command fails with "Timeout: No Response from ..." when using SNMPv2 to query VSX OID branch 1.3.6.1.4.1.2620.1.16 on VSX machine with large number of Virtual Systems.

Example:
```
[Expert@HostName]# snmpwalk -v 2c -c public localhost 1.3.6.1.4.1.2620.1.16
Timeout: No Response from localhost
[Expert@HostName]# 
```

If monitoring connections in Virtual Systems with SNMPv2, the returned values are 0 (zero).

Example:

[Expert@HostName]# snmpwalk -v 2c -c public localhost .1.3.6.1.4.1.2620.1.16.23.1.1.2

SNMPv2-SMI::enterprises.2620.1.16.23.1.1.2.1.0 = INTEGER: 12
SNMPv2-SMI::enterprises.2620.1.16.23.1.1.2.2.0 = INTEGER: 0
SNMPv2-SMI::enterprises.2620.1.16.23.1.1.2.3.0 = INTEGER: 0
SNMPv2-SMI::enterprises.2620.1.16.23.1.1.2.4.0 = INTEGER: 0
SNMPv2-SMI::enterprises.2620.1.16.23.1.1.2.5.0 = INTEGER: 0
SNMPv2-SMI::enterprises.2620.1.16.23.1.1.2.6.0 = INTEGER: 0

Output of 'cpstat -f conns vsx' command returns '0' for Virtual System's connections.

Example:

Virtual Devices connections
----------------------------
|ID|Connections| Peak|Limit|
----------------------------
| 0|         12|  230|    0|
| 1|          0|    0|    0|
| 2|          0|    0|    0|
| 3|          0|    0|    0|
| 4|          0|    0|    0|
| 5|          0|    0|    0|
----------------------------

Cause

Current design for processing SNMPv2 queries:

When CPD daemon in Virtual System 0 (VSID0) gets an SNMPv2 request / AMON request (SmartView Monitor) for one of the VSX OIDs, it runs an AMON client ('stattest') to obtain the value of the requested OID from the CPD daemon of the queried Virtual System.

When CPD daemon in Virtual System 0 needs to obtain OIDs of many Virtual Systems, it needs to start an AMON client ('stattest') for each Virtual System, which takes a lot of time.

Meanwhile, the 'snmpwalk' command times out.

Solution

Note: To view this solution you need to Sign In .