<?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 Re: SNMP Trap or alarm for NSO HA failures (NSO 5.4.x) in NSO Developer Hub Discussions</title>
    <link>https://community.cisco.com/t5/nso-developer-hub-discussions/snmp-trap-or-alarm-for-nso-ha-failures-nso-5-4-x/m-p/4282131#M6037</link>
    <description>&lt;P&gt;Hi again,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I was too quick in my answer. Realized your question was not related to the SNMP configuration.&lt;/P&gt;
&lt;P&gt;Starting with NSO 5.4 you have two options on how to setup HA.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;1. Use the tailf-hcc-4.5 package.&lt;/P&gt;
&lt;P&gt;This will emit the alarms as before, just as you described.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;2. Use the builtin HA functionality.&lt;/P&gt;
&lt;P&gt;I will need to check if there are any alarms defined for this setup.&lt;/P&gt;
&lt;P&gt;Optionally you can install tailf-hcc-5.0 for support of virtual IP and BGP.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I'll geet back to you on 2.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards&lt;/P&gt;
&lt;P&gt;Ulrik&lt;/P&gt;</description>
    <pubDate>Fri, 29 Jan 2021 13:16:06 GMT</pubDate>
    <dc:creator>Ulrik Stridsman</dc:creator>
    <dc:date>2021-01-29T13:16:06Z</dc:date>
    <item>
      <title>SNMP Trap or alarm for NSO HA failures (NSO 5.4.x)</title>
      <link>https://community.cisco.com/t5/nso-developer-hub-discussions/snmp-trap-or-alarm-for-nso-ha-failures-nso-5-4-x/m-p/4280885#M6031</link>
      <description>&lt;P&gt;Hi All!&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Hello! Does NSO 5.4 support Alarms for HA events? For example: failure of master or slave node..? I saw one conversation which says tailf-hcc used to generate node-failure alarm atleast until nso 5.3.. but I can’t find any alarm type for HA in NSO 5.4&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Also in nso 5.4.1 nso_admin_guide - ch11s10s02.html it mentions about node-failure alarm but I can't find that in any YANG model.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I see in tailf-hcc 4.x projects there are 3 alarms:&lt;/P&gt;
&lt;P&gt;identity node-failure {&lt;BR /&gt;base hcc-alarm;&lt;BR /&gt;description&lt;BR /&gt;"The node lost HA connection with its master";&lt;BR /&gt;}&lt;/P&gt;
&lt;P&gt;identity device-node-failure {&lt;BR /&gt;base hcc-alarm;&lt;BR /&gt;description&lt;BR /&gt;"A service node noticed one of its device nodes lost&lt;BR /&gt;HA connection with its master";&lt;BR /&gt;}&lt;/P&gt;
&lt;P&gt;identity bgp-failure {&lt;BR /&gt;base hcc-alarm;&lt;BR /&gt;description&lt;BR /&gt;"A service node noticed it lost its BGP prefix path to&lt;BR /&gt;its master";&lt;BR /&gt;}&lt;BR /&gt;}&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;but this tailf-hcc-alarms.yang is not even present in tailf-hcc 5.x projects.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Any help appreciated!&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;Neetika&lt;/P&gt;</description>
      <pubDate>Wed, 27 Jan 2021 19:56:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/nso-developer-hub-discussions/snmp-trap-or-alarm-for-nso-ha-failures-nso-5-4-x/m-p/4280885#M6031</guid>
      <dc:creator>neetimit</dc:creator>
      <dc:date>2021-01-27T19:56:21Z</dc:date>
    </item>
    <item>
      <title>Re: SNMP Trap or alarm for NSO HA failures (NSO 5.4.x)</title>
      <link>https://community.cisco.com/t5/nso-developer-hub-discussions/snmp-trap-or-alarm-for-nso-ha-failures-nso-5-4-x/m-p/4282129#M6036</link>
      <description>&lt;P&gt;Hi Neetika,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The short answer is yes on both.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The way it works is that any alarm can be forwarded as an SNMP trap and/or notification.&lt;/P&gt;
&lt;P&gt;The first step is to configure the SNMP agent in NSO:&lt;/P&gt;
&lt;PRE&gt;agent {
    enabled;
    ip               0.0.0.0;
    udp-port         4000;
    version {
        v1;
        v2c;
        v3;
    }
    engine-id {
        enterprise-number 32473;
        from-text         testing;
    }
    max-message-size 50000;
}
system {
    contact  "";
    name     "";
    location "";
}
usm {
    local {
        user initial {
            auth {
                sha {
                    password GoTellMom;
                }
            }
            priv {
                des {
                    password GoTellMom;
                }
            }
        }
    }
}
target monitor {
    ip       127.0.0.1;
    udp-port 162;
    tag      [ monitor ];
    timeout  1500;
    retries  3;
    v2c {
        sec-name public;
    }
}
community public {
    sec-name public;
}
notify foo {
    tag  monitor;
    type trap;
}
vacm {
    group initial {
        member initial {
            sec-model [ usm ];
        }
        access usm no-auth-no-priv {
            read-view   internet;
            notify-view internet;
        }
        access usm auth-no-priv {
            read-view   internet;
            notify-view internet;
        }
        access usm auth-priv {
            read-view   internet;
            notify-view internet;
        }
    }
    group public {
        member public {
            sec-model [ v1 v2c ];
        }
        access any no-auth-no-priv {
            read-view   internet;
            notify-view internet;
        }
    }
    view internet {
        subtree 1.3.6.1 {
            included;
        }
    }
    view restricted {
        subtree 1.3.6.1.6.3.11.2.1 {
            included;
        }
        subtree 1.3.6.1.6.3.15.1.1 {
            included;
        }
    }
}&lt;/PRE&gt;
&lt;P&gt;An then enable to forwarding of alarm changes as SNMP/NETCONF notifications:&lt;/P&gt;
&lt;PRE&gt;alarms control notify-about-status-changes true&lt;/PRE&gt;
&lt;P&gt;Feel free to get back to me for more detals.&lt;/P&gt;
&lt;P&gt;Ulrik Stridsman&lt;/P&gt;
&lt;P&gt;Software Engineer&lt;BR /&gt;&lt;SPAN&gt;NSO, ConfD &amp;amp; NSO Applications CTO Group&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 29 Jan 2021 13:08:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/nso-developer-hub-discussions/snmp-trap-or-alarm-for-nso-ha-failures-nso-5-4-x/m-p/4282129#M6036</guid>
      <dc:creator>Ulrik Stridsman</dc:creator>
      <dc:date>2021-01-29T13:08:11Z</dc:date>
    </item>
    <item>
      <title>Re: SNMP Trap or alarm for NSO HA failures (NSO 5.4.x)</title>
      <link>https://community.cisco.com/t5/nso-developer-hub-discussions/snmp-trap-or-alarm-for-nso-ha-failures-nso-5-4-x/m-p/4282131#M6037</link>
      <description>&lt;P&gt;Hi again,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I was too quick in my answer. Realized your question was not related to the SNMP configuration.&lt;/P&gt;
&lt;P&gt;Starting with NSO 5.4 you have two options on how to setup HA.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;1. Use the tailf-hcc-4.5 package.&lt;/P&gt;
&lt;P&gt;This will emit the alarms as before, just as you described.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;2. Use the builtin HA functionality.&lt;/P&gt;
&lt;P&gt;I will need to check if there are any alarms defined for this setup.&lt;/P&gt;
&lt;P&gt;Optionally you can install tailf-hcc-5.0 for support of virtual IP and BGP.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I'll geet back to you on 2.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards&lt;/P&gt;
&lt;P&gt;Ulrik&lt;/P&gt;</description>
      <pubDate>Fri, 29 Jan 2021 13:16:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/nso-developer-hub-discussions/snmp-trap-or-alarm-for-nso-ha-failures-nso-5-4-x/m-p/4282131#M6037</guid>
      <dc:creator>Ulrik Stridsman</dc:creator>
      <dc:date>2021-01-29T13:16:06Z</dc:date>
    </item>
    <item>
      <title>Re: SNMP Trap or alarm for NSO HA failures (NSO 5.4.x)</title>
      <link>https://community.cisco.com/t5/nso-developer-hub-discussions/snmp-trap-or-alarm-for-nso-ha-failures-nso-5-4-x/m-p/4282315#M6038</link>
      <description>&lt;P&gt;Hi Ulrik,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thank you for taking time to look into this.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Another question, I see NSO 5.4 has both tailf-hcc projects 4.5 and 5.0 but I don't see hcc 4.5 for NSO 5.4.1 or NSO 5.4.2.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Why is that so?&lt;/P&gt;
&lt;P&gt;Also please let me know if you find something on built in HA functionality.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;Neetika&lt;/P&gt;</description>
      <pubDate>Thu, 18 Feb 2021 12:17:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/nso-developer-hub-discussions/snmp-trap-or-alarm-for-nso-ha-failures-nso-5-4-x/m-p/4282315#M6038</guid>
      <dc:creator>neetimit</dc:creator>
      <dc:date>2021-02-18T12:17:47Z</dc:date>
    </item>
  </channel>
</rss>

