<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Hey, in Network Management</title>
    <link>https://community.cisco.com/t5/network-management/pi-3-0-snmp-trap-alarm-filter/m-p/2802907#M108661</link>
    <description>&lt;P&gt;Hey,&lt;/P&gt;
&lt;P&gt;we found a workaround for this "problem". We configure every access port "&lt;STRONG&gt;no snmp trap link-status&lt;/STRONG&gt;" and "&lt;STRONG&gt;no logging event port link-status&lt;/STRONG&gt;". Now everything is fine.&lt;/P&gt;
&lt;P&gt;In pairs we configured all 800 Switches in 2h. Another possibility is to use a perl script to configure all switches automatically.&lt;/P&gt;
&lt;P&gt;/Hugo&lt;/P&gt;</description>
    <pubDate>Wed, 09 Mar 2016 06:49:41 GMT</pubDate>
    <dc:creator>Danny Sandner</dc:creator>
    <dc:date>2016-03-09T06:49:41Z</dc:date>
    <item>
      <title>PI 3.0 - SNMP Trap / Alarm Filter</title>
      <link>https://community.cisco.com/t5/network-management/pi-3-0-snmp-trap-alarm-filter/m-p/2802906#M108660</link>
      <description>&lt;P&gt;Hey folks,&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;I want to migrate from LMS4.2 to Cisco PI 3.0 and I am testing and configuring PI3.0. Now I have arround 100 network devices in Cisco PI, some routers, some central building distributor and some switches, Catalyst 6k, 3k, NX, and so on.&lt;/P&gt;
&lt;P&gt;In all switches, PI is added as SNMP-server Host traps snmp v2.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Now we get a lot of alarms with "Link Down", mainly user ports. We just want to get notice of link status changes of ports connected to other switches.&lt;/P&gt;
&lt;P&gt;We tried to create Monitoring Policies, but this has no impact to snmp traps coming from the switches.&lt;/P&gt;
&lt;P&gt;How can we filter this alarms in an elegant way?&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Thanks a lot&lt;/P&gt;
&lt;P&gt;/Hugo&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 04 Dec 2015 08:15:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-management/pi-3-0-snmp-trap-alarm-filter/m-p/2802906#M108660</guid>
      <dc:creator>Danny Sandner</dc:creator>
      <dc:date>2015-12-04T08:15:53Z</dc:date>
    </item>
    <item>
      <title>Hey,</title>
      <link>https://community.cisco.com/t5/network-management/pi-3-0-snmp-trap-alarm-filter/m-p/2802907#M108661</link>
      <description>&lt;P&gt;Hey,&lt;/P&gt;
&lt;P&gt;we found a workaround for this "problem". We configure every access port "&lt;STRONG&gt;no snmp trap link-status&lt;/STRONG&gt;" and "&lt;STRONG&gt;no logging event port link-status&lt;/STRONG&gt;". Now everything is fine.&lt;/P&gt;
&lt;P&gt;In pairs we configured all 800 Switches in 2h. Another possibility is to use a perl script to configure all switches automatically.&lt;/P&gt;
&lt;P&gt;/Hugo&lt;/P&gt;</description>
      <pubDate>Wed, 09 Mar 2016 06:49:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-management/pi-3-0-snmp-trap-alarm-filter/m-p/2802907#M108661</guid>
      <dc:creator>Danny Sandner</dc:creator>
      <dc:date>2016-03-09T06:49:41Z</dc:date>
    </item>
  </channel>
</rss>

