Archive

Tech Tip NV - 'No Data Returned' Polling Failures. 

05-15-2015 04:47 PM

Polling failures doe to 'No Data Returned' alarms can often be prevented by adding the isGet property to the device.

 

Remote into the Poller and open the Console

Groups tab

Select the device

Properties

Add

Name: isGet

Value: 1

click OK

Rediscover the Device

 

By default NV will use Get-Request and Get-BulkRequest for SNMP Polling. Adding the isGet = 1 property configures NV so it will only use the Get-Request for this device.

 

If a device is a poor at responding to SNMP polling such as a Nexus then the Get-BulkRequest will result in the device not being able to send a response with the data for all the OIDs. With isGet it sends a Get-Request for each one and typically correct data is always returned.

 

When the NV MIB Browser successfully gets a response then almost always the isGet property will get NV working. This is because the MIB Browser only uses Get-RequestGet-Request.

 

It is recommended to only use the isGet property at a device level since it does result in a significant increase in network traffic.

Statistics
0 Favorited
2 Views
0 Files
0 Shares
0 Downloads

Tags and Keywords

Comments

08-03-2015 04:16 PM

In regards to the problem polling the ASA devices see this notification from Cisco for details. Also note it specifies the problem was fixed in IOS revisions 9.1.5 and later.

 

http://www.cisco.com/c/en/us/support/docs/security/asa-5500-x-series-next-generation-firewalls/118051-technote-asa-00.html

08-03-2015 02:21 PM

ASA devices will often fail due to 'PDU Too Big' in addition to the above 'No Data Returned'.

 

The PDU Too Big is related to a device side setting for Max-PDU.

 

Typically this failure can be prevented via the ShortOIDLIst property.

 

At the Poller Console 

Groups tab

Select the device

Properties

Add

Name: isGet

Value: 1

click OK

Add

Name: ShortOIDList

Value: 1

click OK

 

 

Rediscover the Device

Related Entries and Links

No Related Resource entered.