SNMP Trap or alarm for NSO HA failures (NSO 5.4.x)

[neetimit]

Hi All!

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

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. 

I see in tailf-hcc 4.x projects there are 3 alarms:

identity node-failure {
base hcc-alarm;
description
"The node lost HA connection with its master";
}

identity device-node-failure {
base hcc-alarm;
description
"A service node noticed one of its device nodes lost
HA connection with its master";
}

identity bgp-failure {
base hcc-alarm;
description
"A service node noticed it lost its BGP prefix path to
its master";
}
}

but this tailf-hcc-alarms.yang is not even present in tailf-hcc 5.x projects.

Any help appreciated!

Thanks,

Neetika

[Ulrik Stridsman]

Hi Neetika,

The short answer is yes on both.

The way it works is that any alarm can be forwarded as an SNMP trap and/or notification.

The first step is to configure the SNMP agent in NSO:

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;
        }
    }
}

An then enable to forwarding of alarm changes as SNMP/NETCONF notifications:

alarms control notify-about-status-changes true

Feel free to get back to me for more detals.

Ulrik Stridsman

Software Engineer
NSO, ConfD & NSO Applications CTO Group

[Ulrik Stridsman]

Hi again,

I was too quick in my answer. Realized your question was not related to the SNMP configuration.

Starting with NSO 5.4 you have two options on how to setup HA.

1. Use the tailf-hcc-4.5 package.

This will emit the alarms as before, just as you described.

2. Use the builtin HA functionality.

I will need to check if there are any alarms defined for this setup.

Optionally you can install tailf-hcc-5.0 for support of virtual IP and BGP.

I'll geet back to you on 2.

Regards

Ulrik

[neetimit]

Hi Ulrik,

Thank you for taking time to look into this.

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. 

Why is that so?

Also please let me know if you find something on built in HA functionality.

Thanks,

Neetika