Prime Infrastructure blocks SNMP during sync causing PRTG alarms

We're running Prime Infrastructure 1.2, and until yesterday we were mainly using it for wireless monitoring. We use PRTG for monitoring the state of the rest of the network. I added our core router (6509-E w/VSS), and during syncs, we will get PRTG alarms (SNMP traffic sensors) saying "No response". The downtime is ~5 minutes (which is the PRTG scanning interval). So, it seems like Prime is preventing other SNMP traffic during the syncs. Is this normal? I don't really like the thought of receiving a boatload of false alarms several times a day.

Hi Brian:
Prime Infrastructure 1.2.0.103 was deferred and removed from Cisco.com in favor of 1.2.1.12, for a number of issues. The current release is 1.3.0.20 Update 1. Between the two, there have been a number of fixes with regards to Java threads being locked, amount of system resources being used by the Oracle engine, size of the backups, and a lot more. You may want to look into getting current to see if the behavior changes.
Clarifying the upgrade path to Prime Infrastructure 1.3.0.20 Update 1
Given the volume of data polled during sync cycles, I could see where Prime Infrastructures questions might dominate or even overwhelm the router's SNMP agent, but there's no process that puts an access-list to prevent the agent processing any other station's traffic while sync is going on. You may want to check the CPU utilization of the SNMP agent (show process cpu | i SNMP ENGINE) before, during and after the sync to see what impact the sync has.

Similar Messages

Prime Infrastructure - Custom SNMP Template

Hi,
Has anyone managed to get the Custom SNMP Template to work in PI 2.x? I can't get it to present any relevant data (yes, with generic dashlets).
I've tried to pull CISCO-ENTITY-SENSOR-MIB and other third-party MIBs with no luck.
I'm starting to suspect this is yet another not-so-ready-feature of PI....
Regards,
Johan

Hi All,
This feature does work..
hope you are following the correct steps:
http://www.cisco.com/c/en/us/td/docs/net_mgmt/prime/infrastructure/2-0/user/guide/prime_infra_ug/create_temps.html
For your reference ,check the verify you are doing all the steps:
Step1:
Design > Custom SNMP Templates > Create the Template
step 2: Design > Monitor configuration
select the template
Name it and other settings...
Step 3::Deploy >Monitoring Deployment
Select the template > click Deploy
select the devices or group of devices.....
Step 4:
Home >Detail dashboard > Devices
click > Add dashlet > device dashlet >> click Gereric Dashlet (configure the generic dashlet by selecting the right template)
Hope it will help
Thanks-
Afroz
****Ratings Encourages Contributors *****

Adding new switch in my network including Cisco Prime Infrastructure

hi all,
if I connect new switch to my network, can I let Cisco PI to apply a specific template of configuration to this switch automatically?
how can I do that ?
thanks in advance

Hi,
i followed these steps :
SWITCH SIDE
- configured Prime Infrastructure as snmp-server host;
- enabled snmp-traps for linkup and linkdown events globally;
- disabled snmp-traps for linkup and linkdown on non relevant interfaces using the no snmp trap link-status command
PRIME INFRASTRUCTURE SIDE
- under "Deploy/Monitor Deployment" i deployed template "Interface Health" for all the interested switches
- under "Administration/System Settings/Mail Server Configuration" configured my internal SMTP server to make Prime Infrastructure able to send e-mails
- under "Operate/Alarms & Events" click on "Email Notifications" , then on "Switches and Hubs"
- check the "critical" box , insert the destination e-mail address into the "To" field then click "Save"
- check the "switches and Hubs" box and then click Save
As i know is possible to avoid to configure every single not-interesting port on the switches with "no snmp trap link-status" command (it's a bit annoying when you have tens of switches), using Port Grouping configuration on PI but i tried it without success.
Hope this helps.
Best Regards,

Including Interface Description in Cisco PRime Infrastructure Alarm Message

Hi all,
i succesfully configured a Cisco Prime Infrastructure 2.1 applliance to display an alarm and to send me an e-mail when switch uplink ports goes down.
The text displayed in alarm message is :
port 'interface_id' is down on device 'device_ip_address'
I'd like to include in this text also the interface description so the text will display :
port 'interface_id' 'interface_descriprion' is down on device 'device_ip_address'
Is this possible?
Thankyou in advance

Hi,
i followed these steps :
SWITCH SIDE
- configured Prime Infrastructure as snmp-server host;
- enabled snmp-traps for linkup and linkdown events globally;
- disabled snmp-traps for linkup and linkdown on non relevant interfaces using the no snmp trap link-status command
PRIME INFRASTRUCTURE SIDE
- under "Deploy/Monitor Deployment" i deployed template "Interface Health" for all the interested switches
- under "Administration/System Settings/Mail Server Configuration" configured my internal SMTP server to make Prime Infrastructure able to send e-mails
- under "Operate/Alarms & Events" click on "Email Notifications" , then on "Switches and Hubs"
- check the "critical" box , insert the destination e-mail address into the "To" field then click "Save"
- check the "switches and Hubs" box and then click Save
As i know is possible to avoid to configure every single not-interesting port on the switches with "no snmp trap link-status" command (it's a bit annoying when you have tens of switches), using Port Grouping configuration on PI but i tried it without success.
Hope this helps.
Best Regards,

Prime Infrastructure 2.0: Running an inventory sync removes "snmp-server location" in running-config

Hello,
we're running Prime Infrastructure 2.0 (version VA-2.0.0.0.294).
I was scared as I figured out one hour ago that running an inventory sync (Device Work Center) removes the command snmp-server location and adds the command snmp-server host "PI-ip address" "snmp rw community" in the running-config.
Has someone the same behaviour or can reenact this scenario?!
Can someone imagine that this behaviour has something to do with a configuration setting in PI?
I'm perplexed and got gray hair now.
Thank you for your answers or tips.
Bastian

Hello Rob,
I just successfully installed the patch. The snmp-server location is not touched anymore while running a inventory job.
But PI still enters this string in the running-configuration:
snmp-server host "PI-IP address" " our snmp RW community- string"
although there already exists the entry:
snmp-server host "PI-IP address" version 2c "community-string (not the snmp rw-community-string)"
Do you or anyone else has the same behaviour that PI adds automaically himself as snmp trap receiver with the SNMP-RW community?
Regards
Bastian

Prime Infrastructure 2.1 - Fan-Failure SNMP-Trap Issue

Hello,
I am facing the following Prime Infrastructure (v2.1) issue:
- A Fan-Failure SNMP-Trap from a Cisco 3650 switch doesn't appear on Prime, but a Link-Failure from the same switch does.
- The both events appears on Prime with Syslog.
- The command "snmp-server enable traps envmon fan shutdown supply temperature status" is set up.
- The switch is in "Managed" state in PI, I have checked the ACL at the "snmp-server community" command, it is okay.
- I have set up an SNMP-Trace for the switch on PI, but only "SNMP Null was returned for class com.cisco.server.managedobjects.bridge.Fan3KStats attribute fanIndex" arrived. Please find the log below.
07/02/14 12:39:53.211 TRACE [presence-9] [] Adding attributes for object Fan3KStats[151206060_,1012]
07/02/14 12:39:53.211 TRACE [presence-9] [] Index name : fanIndex
07/02/14 12:39:53.211 TRACE [presence-9] [] Index Value : 1012
07/02/14 12:39:53.211 TRACE [presence-9] [] Device MIB table index: .1012
07/02/14 12:39:53.211 TRACE [presence-9] [] MIB table row index: .1012
07/02/14 12:39:53.211 TRACE [presence-9] []     OID for : fanIndex = 1.3.6.1.2.1.47.1.1.1.1.1.1012
07/02/14 12:39:53.211 TRACE [presence-9] []     OID for : fanOperStatus = 1.3.6.1.4.1.9.9.13.1.4.1.3.1012
07/02/14 12:39:53.211 TRACE [presence-9] [] Get fragment
07/02/14 12:39:53.211 TRACE [presence-9] [] Creating PDU: Get
07/02/14 12:39:53.211 TRACE [presence-9] []     VarBind OID=1.3.6.1.2.1.47.1.1.1.1.1.1010
07/02/14 12:39:53.211 TRACE [presence-9] []     VarBind OID=1.3.6.1.4.1.9.9.13.1.4.1.3.1010
07/02/14 12:39:53.211 TRACE [presence-9] []     VarBind OID=1.3.6.1.2.1.47.1.1.1.1.1.1011
07/02/14 12:39:53.211 TRACE [presence-9] []     VarBind OID=1.3.6.1.4.1.9.9.13.1.4.1.3.1011
07/02/14 12:39:53.211 TRACE [presence-9] []     VarBind OID=1.3.6.1.2.1.47.1.1.1.1.1.1012
07/02/14 12:39:53.211 TRACE [presence-9] []     VarBind OID=1.3.6.1.4.1.9.9.13.1.4.1.3.1012
07/02/14 12:39:53.218 TRACE [presence-9] [] Error Status: 0
07/02/14 12:39:53.218 TRACE [presence-9] [] Error index: 0
07/02/14 12:39:53.218 TRACE [presence-9] [] SNMP Null was returned for class com.cisco.server.managedobjects.bridge.Fan3KStats attribute fanIndex
07/02/14 12:39:53.218 TRACE [presence-9] []     Setting attribute: fanOperStatus
07/02/14 12:39:53.218 TRACE [presence-9] []     SnmpInt Value : ?
07/02/14 12:39:53.218 TRACE [presence-9] [] GetMultiAttributes, storing result, class=com.cisco.server.managedobjects.bridge.Fan3KStats, attr=fanOperStatus
07/02/14 12:39:53.218 TRACE [presence-9] [] SNMP Null was returned for class com.cisco.server.managedobjects.bridge.Fan3KStats attribute fanIndex
07/02/14 12:39:53.218 TRACE [presence-9] []     Setting attribute: fanOperStatus
07/02/14 12:39:53.218 TRACE [presence-9] []     SnmpInt Value : ?
07/02/14 12:39:53.218 TRACE [presence-9] [] GetMultiAttributes, storing result, class=com.cisco.server.managedobjects.bridge.Fan3KStats, attr=fanOperStatus
07/02/14 12:39:53.218 TRACE [presence-9] [] SNMP Null was returned for class com.cisco.server.managedobjects.bridge.Fan3KStats attribute fanIndex
07/02/14 12:39:53.218 TRACE [presence-9] []     Setting attribute: fanOperStatus
07/02/14 12:39:53.218 TRACE [presence-9] []     SnmpInt Value : ?
07/02/14 12:39:53.218 TRACE [presence-9] [] GetMultiAttributes, storing result, class=com.cisco.server.managedobjects.bridge.Fan3KStats, attr=fanOperStatus
07/02/14 12:39:53.218 TRACE [presence-9] [] GetMultiAttributes, assembling attributes
07/02/14 12:39:53.218 TRACE [presence-9] []     MIB lookup, OID for: powerSupplyIndex = 1.3.6.1.2.1.47.1.1.1.1.1
07/02/14 12:39:53.218 TRACE [presence-9] []     GetMultiAttributes needs class=com.cisco.server.managedobjects.bridge.PowerSupply3kStats, field=powerSupplyIndex
07/02/14 12:39:53.218 TRACE [presence-9] []     MIB lookup, OID for: powerSupplyOperStatus = 1.3.6.1.4.1.9.9.13.1.5.1.3
07/02/14 12:39:53.218 TRACE [presence-9] []     GetMultiAttributes needs class=com.cisco.server.managedobjects.bridge.PowerSupply3kStats, field=powerSupplyOperStatus
07/02/14 12:39:53.218 TRACE [presence-9] [] GetMultiAttributes invoked
07/02/14 12:39:53.218 TRACE [presence-9] [] GetMultiAttributes building OIDs for next PDU
07/02/14 12:39:53.218 TRACE [presence-9] [] Adding attributes for object PowerSupply3kStats[151206060_,1009]
- The switch sends the SNMP Trap, based on the followings:
Jul 7 13:38:30 UTC: SNMP: Packet sent via UDP to IP_ADDRESS
Jul 7 13:38:30 UTC: %PLATFORM_THERMAL-6-FRU_FAN_OIR: Switch 1: System fan 1 removed
Jul 7 13:38:30 UTC: %PLATFORM_THERMAL-1-FRU_FAN_NOT_PRESENT: Switch 1: System fan 1 not present
Jul 7 13:38:30 UTC: SNMP: Queuing packet to IP_ADDRESS
Jul 7 13:38:30 UTC: SNMP: V2 Trap, reqid 33202, errstat 0, erridx 0
sysUpTime.0 = 576753333
snmpTrapOID.0 = ciscoEnvMonMIBNotifications.8
ciscoEnvMonFanStatusEntry.2.1010 = Switch 1 - FAN 1, NotExist
ciscoEnvMonFanStatusEntry.3.1010 = 5
Jul 7 13:38:30 UTC: SNMP: Queuing packet to IP_ADDRESS
Jul 7 13:38:30 UTC: SNMP: V2 Trap, reqid 33203, errstat 0, erridx 0
sysUpTime.0 = 576753333
snmpTrapOID.0 = ciscoEnvMonMIBNotifications.8
ciscoEnvMonFanStatusEntry.2.1010 = Switch 1 - FAN 1, NotExist
ciscoEnvMonFanStatusEntry.3.1010 = 5
Jul 7 13:38:30 UTC: SNMP: Queuing packet to IP_ADDRESS
Jul 7 13:38:30 UTC: SNMP: V2 Trap, reqid 33204, errstat 0, erridx 0
sysUpTime.0 = 576753333
snmpTrapOID.0 = ciscoEnvMonMIBNotifications.8
ciscoEnvMonFanStatusEntry.2.1010 = Switch 1 - FAN 1, NotExist
ciscoEnvMonFanStatusEntry.3.1010 = 5
Jul 7 13:38:30 UTC: SNMP: Queuing packet to IP_ADDRESS
Jul 7 13:38:30 UTC: SNMP: V2 Trap, reqid 33205, errstat 0, erridx 0
sysUpTime.0 = 576753333
snmpTrapOID.0 = ciscoEnvMonMIBNotifications.8
ciscoEnvMonFanStatusEntry.2.1010 = Switch 1 - FAN 1, NotExist
ciscoEnvMonFanStatusEntry.3.1010 = 5
Jul 7 13:38:31 UTC: SNMP: Packet sent via UDP to IP_ADDRESS
Jul 7 13:38:31 UTC: SNMP: Packet sent via UDP to IP_ADDRESS
Jul 7 13:38:31 UTC: SNMP: Packet sent via UDP to IP_ADDRESS
Jul 7 13:38:31 UTC: SNMP: Packet sent via UDP to IP_ADDRESS
Jul 7 13:38:45 UTC: SNMP: Packet sent via UDP to IP_ADDRESS
Jul 7 13:38:51 UTC: %PLATFORM_THERMAL-6-FRU_FAN_OIR: Switch 1: System fan 1 inserted
Jul 7 13:38:54 UTC: SNMP: Queuing packet to IP_ADDRESS
Jul 7 13:38:54 UTC: SNMP: V2 Trap, reqid 33206, errstat 0, erridx 0
sysUpTime.0 = 576755733
snmpTrapOID.0 = ciscoEnvMonMIBNotifications.8
ciscoEnvMonFanStatusEntry.2.1010 = Switch 1 - FAN 1, Normal
ciscoEnvMonFanStatusEntry.3.1010 = 1
Jul 7 13:38:54 UTC: SNMP: Queuing packet to IP_ADDRESS
Jul 7 13:38:54 UTC: SNMP: V2 Trap, reqid 33207, errstat 0, erridx 0
sysUpTime.0 = 576755733
snmpTrapOID.0 = ciscoEnvMonMIBNotifications.8
ciscoEnvMonFanStatusEntry.2.1010 = Switch 1 - FAN 1, Normal
ciscoEnvMonFanStatusEntry.3.1010 = 1
Jul 7 13:38:54 UTC: SNMP: Queuing packet to IP_ADDRESS
Jul 7 13:38:54 UTC: SNMP: V2 Trap, reqid 33208, errstat 0, erridx 0
sysUpTime.0 = 576755733
snmpTrapOID.0 = ciscoEnvMonMIBNotifications.8
ciscoEnvMonFanStatusEntry.2.1010 = Switch 1 - FAN 1, Normal
ciscoEnvMonFanStatusEntry.3.1010 = 1
Jul 7 13:38:54 UTC: SNMP: Queuing packet to IP_ADDRESS
Jul 7 13:38:54 UTC: SNMP: V2 Trap, reqid 33209, errstat 0, erridx 0
sysUpTime.0 = 576755733
snmpTrapOID.0 = ciscoEnvMonMIBNotifications.8
ciscoEnvMonFanStatusEntry.2.1010 = Switch 1 - FAN 1, Normal
ciscoEnvMonFanStatusEntry.3.1010 = 1
Jul 7 13:38:55 UTC: SNMP: Packet sent via UDP to IP_ADDRESS
Jul 7 13:38:55 UTC: SNMP: Packet sent via UDP to IP_ADDRESS
Jul 7 13:38:55 UTC: SNMP: Packet sent via UDP to IP_ADDRESS
Jul 7 13:38:55 UTC: SNMP: Packet sent via UDP to IP_ADDRESS
It seems like PI and the switch doesn't understand each other concerning the fan...
Thanks for any ideas, comments and feedbacks,
Csaba

I have the very same problem.
The switch has a power supply error (one of the two is down). There is the syslog message in PI about it, but no event has created, so nor alarm is there as well.
When I check the status of the switch in the Device Work Center, and choose the Environment in Device Details I can see that PI has not realized the power supply error.
However when I click on the Sync for this very device the power supply status is updated, but still no event or alarm.
This is the case with the FANs as well.

Prime Infrastructure 2.1 - Out Of Sync Devices

Hi all,
We are running a Cisco Prime Infrastructure Appliance (Version 2.1) to mange/monitor/configure our wired network infrastructure. We have been able to successfully add all of the network infrastructure devices to Prime and have had relative success in image deployment, reporting etc.
However, my query is in relation to the Configuration Archives. Currently Prime is indicating that 90% of our devices are 'Out of Sync'. I know that this means that there are discrepancies between the startup and running configs. I have compared the startup and running configs on some of the affected devices and the only differences I can see were in relation to the snmp-server contact XXXX entry and the self-signed certificate entry.
Can anyone tell me how I can go about troubleshooting this or how to bring the device configurations back into sync.
Many thanks,
John P

Hi John,
If you navigate to Operate > Configuration Archives it will display a list of all your devices that are listed as out of sync. From here you can sort to the devices that are listed as Out of sync, select the ones that are listed as such and schedule an overwrite. There is also an option to archive immediately after it overwrites as well. It may take a bit for it to update through this page, but navigating to individual devices through device work center and clicking on the configuration archive tab, will yield that the out of sync (startup/running mismatch) message will switch to no.
Regards,
Brandon

Prime Infrastructure 2.2 snmp-server location

We have implemented Cisco Prime Infrastructure 2.2 in our facility. We have each switch loaded in with an "snmp-server location" set for the switches for easier identification and quicker troubleshooting. We would like that location to show in the network topology map as well as in the email alerts it sends if one of those switches goes down. Is this something I am overlooking, and if so, can someone please explain to me how to make this happen?

Hi William,
snmp-server location is synced from the devices & also the info available in various report.
But, if i'm not wrong you want to customize the e-mail body of notifications sent out from the prime.
This functionality is no where discussed in PI user guide & i'm afraid not possible as of now.
Also, there's bug related to snmp-server location even retrieving it from the reports
CSCuj09556 : PI 2.0 corrupts device config by doing snmp set for location after sync
https://tools.cisco.com/bugsearch/bug/CSCuj09556
CSCuo16889 : PI 2.0 - Does not poll sysLocation for 3750 device
https://tools.cisco.com/bugsearch/bug/CSCuo16889
- Ashok
Please rate the post or mark as correct answer as it will help others looking for similar information

Cisco Prime Infrastructure 1.4 SNMP Traps are not converted into Alarms

Hi everybody,
I just configured SNMP Traps on a Cisco Catalyst 3750-x to send to our Cisco Prime Infrastructure 1.4 Appliance.
Now I forced the Switch to send some traps (Power off a Power Supply, Interface errdisable). The only events I see in Alarms & Events on PI is the same information message everytime:
Configuration management event has been recorded in ccmHistoryEventTable.
I think the forced traps should be converted into alarms? Why can't I see them?
Thanks,
Marc

Ok, I started debugging as you said. I get the following output:
Mar 13 09:28:13.711: SNMP: V2 Trap, reqid 11689, errstat 0, erridx 0
sysUpTime.0 = 198609846
snmpTrapOID.0 = ciscoSyslogMIB.2.0.1
clogHistoryEntry.2.1688 = PM
clogHistoryEntry.3.1688 = 5
clogHistoryEntry.4.1688 = ERR_RECOVER
clogHistoryEntry.5.1688 = Attempting to recover from bpduguard err-disable state on Gi1/0/13
clogHistoryEntry.6.1688 = 198609844
Mar 13 09:28:13.737: SNMP: Queuing packet to xx.xx.xx.xx
Looks like the Switch is sending SNMP Traps from the ciscoSyslogMIB. Is this why PI can't show the Traps and convert it into a alarm?
After this test I configured logging (syslog) to the PI. Now the errors are showed but still not converted into alarms. I just want to be notified by email when such errors occurs.
Thanks,
Marc

Prime Infrastructure 2.0 possible to grab SNMP poll from WAN?

Our objective is to monitor all our network devices using Cisco Prime Infrastructure 2.0 which include LAN site and WAN site. LAN site we have various of equipments example cisco router 3800, ASA 5510, Catalyst switch 6500 and other access switches. WAN site we have ASA 5520. Currently our ASA is located at ISP which has its own public IP. Question is, it is possible to monitor our ASA 5520 which at WAN site? Attached is our topology sample.
Note: We has no issues on monitoring LAN equipments.

Hi Remysyaku
Are you able to do snmp polling on ASA from any other software like net-snmp etc.
I mean you need to check whther problem is snmp connectivity or PI is not able to manage ASA.
Also there is a bug due to which ASA5515x will be shown as unsupported in PI 2.0 but ASA 5520 and further should show managed correctly.
Thanks
Mahavir

Prime Infrastructure 2.0 sync config tasks

Hi,
I'd like to know few things about PI 2.0 config handling:
1. Can PI save running config to startup config on a scheduled basis? Let's say once a week on all devices.
2. Can PI save running config to startup config whatsoever?
3. Can PI download running config when it receives a config trap from device when user enters/exits config mode?
4. Can PI export running and startup configs to a external location?
Thanks!

Hi ,
1.
*Scheduled-You can schedule when Prime Infrastructure collects the configurations of
selected devices and specify recurring collections by selecting Operate > Configuration
Archives, then clicking Schedule Archive.
like minute ..daily etc...
3. ASAI K ,this feature work on the bases of syslogs .. we do not have complete support in PI 2.0 yet so I think bases on config chnage syslogs or traps ,config will not be fetched.
4. for tihs check the below thread:
https://supportforums.cisco.com/message/3975460#3975460
Thanks-
Afroz
[Do rate the useful post]
****Ratings Encourages Contributors ****

Cisco Prime Infrastructure 2.1 Inventory Job

My cisco prime infrastructure performs a switch inventory job every night at 22:00 hrs. When I looked at the syslog of the devices in the inventory, I see some entries that I never saw with other LMS versions.
2014-06-30 22:00:01   Local7.Notice   xxx.xxx.xxx.xxx   5410: Jun 30 22:00:00.623 CST: %SYS-5-CONFIG_I: Configured from xxx.xxx.xxx.xxx by snmp
2014-06-30 22:00:01   Local7.Notice   xxx.xxx.xxx.xxx   5411: Jun 30 22:00:01.567 CST: %SYS-5-CONFIG_I: Configured from console by vty1 (xxx.xxx.xxx.xxx)
2014-06-30 22:05:10   Local7.Notice   xxx.xxx.xxx.xxx   5412: Jun 30 22:05:09.008 CST: %SYS-5-CONFIG_I: Configured from console by vty0 (xxx.xxx.xxx.xxx)
I don't understand what the PI is doing with the switches. Does anyone know what is happening during this inventory background job? TIA

Hello all,
we have the same problem maybe; Cisco Prime IF 2.1 is changing the running-configs and produces out-of-syncs ;
it turns so for us is, as if Cisco Prime IF 2.1 a snmp-server host x.x.x.x community entry writes in the running-config,
so are running-and startup-config are out-of-sync; is this correct? Herbert

Cisco prime infrastructure 1.3 makes every 15 minutes cpu high on cisco 800 routers

I have an issue with cisco prime infrastructure 1.3 and cisco 880 routers, every 15 minutes the cpu goes to 100% on those routers, but I cannot find the job on the prime which is causing this, if I look in the job dashboard I have some jobs like sam_poller_22_15_getvpnpoller_27977292 that runs every 15 minutes (other jobs that I see CDBPoller_dmvpnPoller and CDBPoller_getvpnpoller) , probably is it on of these jobs, but how can I stop it (job type : poller job, owner =system) and what are they doing?
thanks for any assistance

This is what i expected. I know many platform like 29xx/39xx or ISR's has known issues with Cisco Prime Infrastructure when it polls CISCO-LICENSE-MGMT-MIB, devices go high on CPU.
You have to block clmgmtLicenseInfoEntry by creating a view on your 800 router by configuring snmp view.
Following is the command/example:
Step 1: Configure SNMP View:
snmp-server view iso included
snmp-server view clmgmtLicenseInfoEntry excluded
Link community string to SNMP View:
snmp-server community view ro|rw
Example per your configuration:
snmp-server view PrimeInfra iso included
snmp-server view PrimeInfra clmgmtLicenseInfoEntry excluded
snmp-server community ArgSnmp view PrimeInfra RO ACLSNMP_RO
OR you can try following on your Cisco PI:
Manually update file below,
Open the /opt/CSCOlumos/conf/sam/template.xml, modify the template id=20 (licensePoller)
Update tag for value 600 to 86400 for all attrributes () of
template id =20
Old: 600
New: 86400
Some known bugs on such issues are :
CSCug97914 and CSCuc72024
Please check and let me know the updates.
-Thanks
Vinod
**Rating Encourages contributors, and its really free. **

Cisco Prime Infrastructure 1.2 config deployment (no copy run start)

I have deployed some CLI templates I have created to configure multiple local accounts on some switches. However the cli templete only appears to accept conf t commands, it will not accept 'write mem' or 'copy run start' at the end to save the altered running config to startup. this results in running and startup being 'out of sync' in the configuration archives, and runs the risk of a power failure causing the config to revert back to startup. Does anyone know how to ensure the altered running config is saved to startup during the config template deployment?

I don't know if this has been fixed in 2.0 or not. By the looks of the bug it hasn't. However, there is a workaround-
https://tools.cisco.com/bugsearch/search?kw=prime%20infrastructure%20copy%20run%20start&pf=prdNm&sb=anfr&srtBy=byRel&bt=custV
BugID
CSCuf89957
Prime Infrastructure - No option to save running config to startup
Conditions:
Prime Infrastructure 1.2/1.3
Workaround:
Create a Configuration Template that runs either:
"do write mem"
Or for devices which no longer support "write mem", use:
"file prompt quiet
do copy run start
no file prompt quiet"

Ask the Expert: Cisco Prime Infrastructure - Implementation and Deployment

Welcome to the Cisco Support Community Ask the Expert conversation.
This Ask The expert Session will cover questions spanning Cisco Prime Infrastructure on Implementation and Deployment on Wired and Wireless. This will be more specific to Customer’s and Partners questions product covering PI on configuration, Features and Menu, Network Monitoring, Maps, Implementation, High Availability and Maintenance and t/s parts.
Monday, February 2nd, 2015 to Friday, February 13th, 2015
Dhiresh Yadav is a customer support engineer in High-Touch Technical Services (HTTS) handling supporting Wireless and Network Management based Cisco products and is based in Bangalore. His areas of expertise include Cisco Prime Infrastructure and Cisco Wireless products. He has over 7 years of industry experience working with large enterprise and service provider networks. He also holds CCNP (RS) and CCIE (DC) certifications.
Afroz Ahmad is a customer support engineer in High-Touch Technical Services (HTTS) handling supporting Wireless and Network Management based Cisco products and is based in Bangalore. His areas of expertise include Cisco NMS products like Prime Infrastructure, LMS, IP SLA and SNMP etc. He has over 7 years of industry experience working with large enterprise and service provider networks. He also holds CCNP (RS),CCIE (DC), and SCJP (Sun Certified Java Professional )
Vinod Kumar Arya is a customer support engineer in High-Touch Technical Services (HTTS) handling supporting Wireless and Network Management based Cisco products and is based in Bangalore. His areas of expertise include Cisco NMS products like Prime Infrastructure, LMS, IP SLA and SNMP etc. He has over 8 years of industry experience working with large enterprise and service provider networks. He also holds VCP 5 and RHCE certifications.
** Remember to use the rating system to let the experts know you have received an adequate response.**
Because of the volume expected during this event, the experts might not be able to answer every question. Remember that you can continue the conversation in the Network Infrastructure community, > Network Management, shortly after the event. This event lasts through February 13th 2015. Visit this forum often to view responses to your questions and those of other Cisco Support Community members.

Hello Wilson,
Thanks for joining us.
1841 should just work fine for net flow . Hope you have a valid "PI Assurance license" installed on the server.
"PI Assurance license" is required for "net-flow" feature
Devices supporting Netflow in PI ::
1400, 1600, 1700 & 1800
2500, 2600 & 2800
3600, 3700, 3750 & 3800
4500 & 4700
AS5300 & 5800
7200, 7300, 7400 & 7500
Catalyst 4500 ASCI
Catalyst 5000, 6500, & 7600 ASCI
ESR 10000 ASCI
GSR 12000 ASCI
Cisco IOS Software Release Version
Supported Cisco Hardware Platforms
11.1CA, 11.1CC
Cisco 7200 and 7500 series, RSP 7200 series
12.0
Cisco 1720, 2600, 3600, 4500, 4700, AS5800
RSP 7000 and 7200 series
uBR 7200 and 7500 series
RSM series
12.0T, 12.0S
Cisco 1720, 2600, 3600, 4500, 4700, AS5800
RSP 7000 and 7200 series
uBR 7200 and 7500 series
RSM series, MGX8800RPM series, and BPx8600 series
12.0(3)T, 12.0(3)S
Cisco 1720, 2600, 3600, 4500, 4700, AS5300, AS5800
RSP 7000 and 7200 series
uBR 7200 and 7500 series
RSM series, MGX8800RPM series, and BPx8650 series
12.0(4)T
Cisco 1400, 1600, 1720, 2500, 2600, 3600, 4500,
4700, AS5300, AS5800
RSP 7000 and 7200 series
uBR 7200 and 7500 series
RSM series, MGX8800RPM series, and BPx8650 series
12.0(4)XE
Cisco 7100 series
12.0(6)S
Cisco 12000 series
NetFlow is also supported by these devices Cisco 800, 1700, 1800, 2800, 3800, 6500, 7300, 7600, 10000, CRS-1 and these Catalyst series switches: 45xx, 55xx, 6xxx.
NetFlow export is also supported on other Cisco switches when using a NetFlow Feature Card (NFFC) or NFFC II and the Route Switch Module (RSM), or Route Switch Feature Card (RSFC). However, check whether version 5 is supported, as most switches export version 7 by default.
You can check the below steps to diagnose the issue::
To verify that NetFlow is exported from a device to PI, follow the steps below:
1)   Browse to Administration > Data Sources page. Check the value in column ‘Last Active Time’ for the ‘Device Data Sources’ table. If the table is empty or the value does not represent recent time, then
it is possible that the device is not exporting NetFlow or PI Assurance license is not applied / expired.
2)   Login to PI console ( via SSH) as root user and run the command:
                netstat –an | grep 9991 – Output of this should be like : udp        0      0 :::9991         :::*
                Check the firewall settings on PI server using the command: firewall -L
1)   Check the configuration on an IOS / IOS –XE device. Run the commands
a)   sh running-config | inc destination
1)   This should list the IP address of the PI SERVER ( along with other outputs if any)
b)   sh running-config | inc 9991
1)   This should list at least one entry.
c)   If the above are fine, then verify that the flow monitor, flow exporter and the flow records are correctly configured on the device.
Refer to the URLs below to configure NetFlow export.
http://preview.cisco.com/en/US/docs/net_mgmt/prime/infrastructure/2.0/user/guide/setup_monitor.html#wp1056427
Thanks-
Afroz
***Ratings Encourages Contributors ****

Prime Infrastructure blocks SNMP during sync causing PRTG alarms

Similar Messages

Maybe you are looking for