- Community Home
- >
- Networking
- >
- Legacy
- >
- TippingPoint
- >
- [Help] TippingPoint 660N - Error Updating Policy (...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-22-2014 09:01 PM
04-22-2014 09:01 PM
[Help] TippingPoint 660N - Error Updating Policy (doReinstall)
Hi everybody,
I have a managed TippingPoint 660N by a SMS system. Since 3 months ago, my SMS send me an error email about doReinstall of a policy that enabled by default. The error occured when new digital vaccine was downloaded and installed. Because I didn't really need it so I disabled that policy and that kind of email disappeared.
But this month, I received hundred of error email about this type of error, for example:
- System Log Notification (error): doReinstall: Error updating default policy '13823: HTTP: Red Hat JBoss Seam Framework XML Information Disclosure Vulnerability' [00000002-0002-0002-0002-000000013823] in NetPAL
- System Log Notification (error): doUpdate: Cannot create default policy '13823: HTTP: Red Hat JBoss Seam Framework XML Information Disclosure Vulnerability' [00000002-0002-0002-0002-000000013823] (signature [00000001-0001-0001-0001-000000013823] was not created in NetPAL)
- System Log Notification (error): doReinstall: Error updating default policy '13774: SNMP: FreeBSD bsnmpd getBulkRequest Buffer Overflow Vulnerability' [00000002-0002-0002-0002-000000013774] in NetPAL
I don't know why they occur and how to fix those error. Please help me to solv this. Any help would be great.
Thank you for viewing!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-23-2014 07:13 PM
04-23-2014 07:13 PM
Re: [Help] TippingPoint 660N - Error Updating Policy (doReinstall)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-26-2014 12:46 AM
09-26-2014 12:46 AM
Re: [Help] TippingPoint 660N - Error Updating Policy (doReinstall)
Does anybody have a solution here ?
I got the same problem with LSM.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-12-2015 06:45 AM
01-12-2015 06:45 AM
Re: [Help] TippingPoint 660N - Error Updating Policy (doReinstall)
oddly enough, encountered a similar problem refrencing other filters on one of our 1400n sensors. but the really odd thing is, the error did not crop up on any of the other 1400's we use just one in particular. any info would be helpful.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-12-2015 06:58 AM
01-12-2015 06:58 AM
Re: [Help] TippingPoint 660N - Error Updating Policy (doReinstall)
i have been informed the issue was resolved by checking which file was being dristributed. we encountered the issue when we tried to distribute an old profile.
to try and resolve this issue ensure you are distributing your correct and most up to date profile to ensure this issue does not occur. its an easy mistake to make if you have old or lagacy profiles still available on your SMS