Submit a ticketCall us

Systems Monitoring for Dummies
Our new eBook will teach you the fundamentals and help you create monitors and alerts that are effective, meaningful, and actionable. Monitoring is more than a checkbox on your to-do list. This free eBook will give you practical advice to help you succeed in all aspects of monitoring – discovery, alerting, remediation, and troubleshooting. Don’t miss out on this indispensable resource for newbies, experienced IT pros, and everyone in between. Register Now.

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: 9 Votes: 0 Revisions: 5

Overview

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.

Environment

All LEM versions with pre-existing deployments

Detail

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

Tags

Classifications

Public