Submit a ticketCall us

Announcing NCM 7.7
With NCM 7.7, you can examine the rules that make up an access control list for a Cisco ASA device. Then you can apply filters to display only rules that meet the specified criteria, order the rules by line number or by the hit count, and much more.
See new features and improvements.

Home > Success Center > VoIP & Network Quality Manager (VNQM) > TCP connect operation does not display as "down" when it fails

TCP connect operation does not display as "down" when it fails

Created by Brian O'Donovan, last modified by MindTouch on Jun 16, 2016

Views: 16 Votes: 0 Revisions: 6

Overview

The status of TCP connect operation does not change to "down" in VNQM when the operation fails on the device.

Environment

All VNQM versions

Cause 

This is due to a device issue. The value -16 is  invalid.

 

Device returns invalid result - .1.3.6.1.4.1.9.9.42.1.2.10.1.2.<op_number> = INTEGER: -16

Device Model:  cisco887Va

IOS version:    (C880DATA-UNIVERSALK9-M), Version 15.3(1)T, RELEASE SOFTWARE (fc1)

Resolution

  1. Run an SNMP Walk using the procedure here.
  2. Review the SNMP Walk results using a text editor, for example Notepad.
  3. Contact Cisco TAC for a solution to this device issue.

 

Result from SNMP Walk

.1.3.6.1.4.1.9.9.42.1.2.10.1.2.<op_number> = INTEGER: -16

 

Orion does not save results when the operation fails. This is due to the fact that the device does not return a valid result.

 

Valid results:

0 - Other

1 - OK

2 - Disconnected

3 - OverThreshold

4 - Timeout

5 - Busy

6 - NotConnected

7 - Dropped

8 - SequenceError

9 - VerifyError

10 - ApplicationSpecific

11 - DnsServerTimeout

12 - TcpConnectTineout

13 - HttpTransactionTimeout

14 - DnsQueryError

15 - HttpError

16 - Error

 

 

 

Last modified
16:33, 16 Jun 2016

Tags

Classifications

Public