Prime Infrastructure 2.0, interface health monitoring for port group still alarms all interfaces
We're trying to have PI 2.0 stop alarming on PRI b-channels for voice calls. We put necessary interfaces into WAN Int port group which doesn't include b-channels. Configured new monitoring template and deployed on the WAN port group. The default interface monitoring template is not deployed. We still get alarms for ALL interfaces even though not all of them are part of WAN int group. Anyone ran into this?
Re: Prime Infrastructure 2.0, interface health monitoring for po
Here's the email we got from TAC:
"As we discussed a moment ago, the functionality does not currently exist to categorize ports to filter out unwanted ‘port down’ alarms or the subsequent email notification. I filed a bug to address this fact - CSCuj50966. The last time I checked in the future of this component was under discussion. I just followed up with the developers involved, I’ll let you know if there is any worthwhile information to pass along. In the meantime we are left with workarounds, which include applying an email filter on your inbox, or applying cutdown views at the device level for the unimportant interfaces."
This product is garbage if it has no capability to filter out alarms. What if the customer has 100 Voice PRIs and 100 T1s, every time a voice call is placed on the PRIs which coincides with polling will cause the B-channel alert. I'm not even mentioning the problem of LAN ports on switches going up/down constantly. Manually filtering out events for failed PRIs and T1s will be impossible. Prime needs to be able to do such essential task, especially since it has great port grouping capability already. The solution to configure SNMP view on each device for specific interfaces that we want to monitor is very impractical. Configuring filtering on the email server is insane.
Are we the only ones who see this product pretty much unusable without this functionality? The excuse that Prime Infrastructure is still not ready and that LMS should be used for features that PI doesn't have just doesn't cut it anymore. This missing essential functionality is not an add-on feature like compliancy, it's an absolute requirement. If PI can't filter out alarms, then don't sell the product.
My only hope is that this TAC engineer didn't understand the issue.
Question We run asr9001 with XR 6.1.3, and we have a very long delay to
login w/ SSH 1 or 2 to the device compare to IOS device. After
investigation, the there is 1s delay between the client KEXDH_INIT and
the server (XR) KEXDH_REPLY. After debug ssh serv...
Introduction The purpose of this document is to demonstrate the Open
Shortest Path First (OSPF) behavior when the V-bit (Virtual-link bit) is
present in a non-backbone area. The V-bit is signaled in Type-1 LSA only
if the router is the endpoint of one or ...
Hi, I am seeing quite a few issues with patch install and wanted to
share my experience and workaround to this. Login to admin via CLI, then
access root with the “shell” command Issue “df –h” and you’ll probably
see the following directory full or nearly ...