Hello experts,
I have a situation where my customer is hosting multiple tenants by means of virtual contexts. We recently upgraded our Prime Infrastructure to version 3.1 to enable us to apply alarm policies to filter down on both the number and type of events that were triggering alarm email notifications. We would like for each organization to customize or tailor their alarm filters within their respective virtual context, but whenever they attempt to modify the default alarm policies when they attempt to save and activate them, the following error is always displayed: (see attached: pi31_alarm_policies_virtual_context.pdf)
However, if i change context to the ROOT-DOMAIN and apply the very same alarm policies from that context, the policies activate and are saved successfully. (see attached: pi31_root-domain_alarm_policies_successful.pdf) Obviously, we would prefer for each organization to be able to administer their respective virtual contexts (and alarm policies) on their own without requiring outside assistance. I cant find anywhere in the documentation that states alarm policies can only be configured from the ROOT-DOMAIN, but have yet to get the policies applied from within a virtual context. I am hoping someone can point me in the right direction.
TIA,
Brett
Cisco Prime Infrastructure 3.1 versioning information is provided below:
CWALNMPRIRCCK01/admin# show version
Cisco Application Deployment Engine OS Release: 3.1
ADE-OS Build Version: 3.1.0.001
ADE-OS System Architecture: x86_64
Copyright (c) 2009-2016 by Cisco Systems, Inc.
All rights reserved.
Hostname: CWALNMPRIRCCK01
Version information of installed applications
---------------------------------------------
Cisco Prime Infrastructure
********************************************************
Version : 3.1.0
Build : 3.1.0.0.132
Critical Fixes:
PI 3.1.1 ( 1.0.0 )
Device Support:
Prime Infrastructure 3.1 Device Pack 2 ( 2.0 )
CWALNMPRIRCCK01/admin#
