Cisco Cisco Prime Network 3.8 故障排查指南
Prime Network ciscoConfigManEvent Trap Flood
Document ID: 117695
Contributed by Thomas Maneri, Cisco TAC Engineer.
Jul 01, 2014
Jul 01, 2014
Contents
Introduction
Problem
Solution
Problem
Solution
Introduction
This document describes the cause, repercussions, and solution to a problem where you receive a flood of
Cisco Configuration management event notification (ciscoConfigManEvent) traps in the Cisco Prime
Network.
Cisco Configuration management event notification (ciscoConfigManEvent) traps in the Cisco Prime
Network.
Problem
Network devices might be configured in such a way that when a show run or conf t command is entered on a
device, the device sends out a ciscoConfigManEvent trap. If the device is monitored by Cisco Prime
Network, you can view these traps in the Trap tab of the Event Vision as Cisco Configuration management
event notification events.
device, the device sends out a ciscoConfigManEvent trap. If the device is monitored by Cisco Prime
Network, you can view these traps in the Trap tab of the Event Vision as Cisco Configuration management
event notification events.
A flood of these traps occurs because Cisco Prime Network executes a show run interface <interface id>
command to the devices for every interface defined within the device. This occurs every polling cycle, which
is every 15 minutes by default. The majority of customers now experience a flood of these types of events.
Large service providers can have a high number of interfaces on each device, and it is common to see several
thousands of these events within the Cisco Prime Network every minute.
command to the devices for every interface defined within the device. This occurs every polling cycle, which
is every 15 minutes by default. The majority of customers now experience a flood of these types of events.
Large service providers can have a high number of interfaces on each device, and it is common to see several
thousands of these events within the Cisco Prime Network every minute.
This causes many side effects, such as:
The Database (DB) becomes full, and the temporary space runs out.
•
Customers experience slow GUI performance due to the large number of events in the DB.
•
There is a high number of orphan events in the DB (events that are not associated with a ticket and
are not archived).
are not archived).
•
There is slower trap and Virtual Network Element (VNE) processing due to the the large number of
events.
events.
•
Solution
The best solution for this problem is to change the configuration of the network devices so that they do not
send these types of traps to the Prime Network server. However, this is not practical in some large service
provider systems. This section provides a workaround for this problem. The goal of this workaround is to
filter the traps as soon as they reach the Event Collector (AVM 100).
send these types of traps to the Prime Network server. However, this is not practical in some large service
provider systems. This section provides a workaround for this problem. The goal of this workaround is to
filter the traps as soon as they reach the Event Collector (AVM 100).
Note: For Cisco Prime Network Versions 4.0 and later, refer to the Cisco Prime Network Administrator
Guide, 4.0 in order to obtain a solution to this problem. The workaround that is described in this document is
for all Active Network Abstraction (ANA) versions as well as all Cisco Prime Network Versions 3.11 and
Guide, 4.0 in order to obtain a solution to this problem. The workaround that is described in this document is
for all Active Network Abstraction (ANA) versions as well as all Cisco Prime Network Versions 3.11 and