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 > Log & Event Manager (LEM) > TippingPoint reflects after running Scan for New Nodes

TippingPoint reflects after running Scan for New Nodes

Table of contents
Created by Justin Rouviere, last modified by MindTouch on Jun 23, 2016

Views: 6 Votes: 0 Revisions: 5


The log entries of TippingPoint are generic and several vendor log types are miss identified as TippingPoint when using Scan for New Nodes.  

Development has removed TippingPoint from Scan for New Nodes, but users with previously existing deployments may still see TippingPoint show in the results.


All LEM versions with pre-existing deployments


Note: New deployments of 6.2, 6.2.1 or later should not run into this issue.

If you are seeing TippingPoint after running Scan for New Nodes and receive Unmatched Data or it miss identifies a known vendor appliance then contact Support for remediation.





Last modified
20:23, 22 Jun 2016