Junos OS

 View Only

IMPORTANT MODERATION NOTICE

This community is currently under full moderation, meaning  all posts will be reviewed before appearing in the community. Please expect a brief delay—there is no need to post multiple times. If your post is rejected, you'll receive an email outlining the reason(s). We've implemented full moderation to control spam. Thank you for your patience and participation.



Expand all | Collapse all

Include port descriptions for snmp traps

This thread has been viewed 9 times
  • 1.  Include port descriptions for snmp traps

    Posted 02-11-2022 12:35
    My company has started to do some network monitoring through a 3rd party service. I have noticed that port descriptions are not being sent in the trap messages. Those would be very helpful to us in determining what is connected to our ports (Our Brocades and other equipment does send the interface description). I am testing in our lab, but can not find the answer I am looking for after hours of research.
    I am using Model: ex2300-24t
    Junos: 15.1X53-D58.3. Here's my output of show snmp (some info redacted for security):

    {master:0}[edit snmp]
    Username# show
    filter-interfaces {
    all-internal-interfaces;
    }
    v3 {
    usm {
    local-engine {
    user icinga {
    authentication-md5 *******************## SECRET-DATA
    }
    privacy-des {
    privacy-key "*******************************************"; ## SECRET-DATA
    }
    }
    user username {
    authentication-md5 {
    authentication-key "********************************************"; ## SECRET-DATA
    }
    privacy-des {
    privacy-key "*******************************************************"; ## SECRET-DATA
    }
    }
    }
    }
    vacm {
    security-to-group {
    security-model usm {
    security-name icinga {
    group view-all;
    }
    security-name nextech {
    group view-all;
    }
    }
    }
    access {
    group view-all {
    default-context-prefix {
    security-model usm {
    security-level privacy {
    read-view view-all;
    notify-view view-all;
    }
    }
    }
    }
    }
    }
    target-address COLLECTOR {
    address 192.168.8.46;
    tag-list COLLECTORS_TAG;
    target-parameters COLLECTOR-PARAMETERS;
    }
    target-parameters COLLECTOR-PARAMETERS {
    parameters {
    message-processing-model v3;
    security-model usm;
    security-level privacy;
    security-name nextech;
    }
    notify-filter ALL;
    }
    notify chassis-trap-list {
    type trap;
    tag chassis-trap-receivers;
    }
    notify NOTIFY_ALL {
    type trap;
    tag COLLECTORS_TAG;
    }
    notify-filter chassis-traps {
    oid jnxChassisOKTraps include;
    }
    notify-filter ALL {
    oid .1 include;
    }
    }
    engine-id {
    use-mac-address;
    }
    view view-all {
    oid .1 include;
    }
    view inventory-only {
    oid jnxBoxAnatomy include;
    oid system include;
    }
    view system-level {
    oid jnxBoxAnatomy include;
    oid 1.3.6.1.2.1.2 include;
    oid 1.3.6.1.2.1.14 include;
    oid 1.3.6.1.2.1.15 include;
    }
    view limited {
    oid 1.3.6.1.2.1.2 include;
    }
    community "C@nUcm3n0w" {
    authorization read-only;
    clients {
    Clients with /32 IP
    }
    }
    community "1C@ncUn0w" {
    authorization read-write;
    clients {
    192.168.8.46/32;
    }
    }
    trap-options {
    source-address 10.33.161.13;
    }
    trap-group SevOne {
    version v2;
    categories {
    authentication;
    chassis;
    link;
    routing;
    startup;
    services;
    }
    targets {
    XXX.XXX.XXX.XXX;
    }
    }

    Here is a sample of the messages we are getting that an interface description would be helpful:
    Juniper location-off-or2.company.org 10.33.161.11 ge-1/0/1 AdminStatus up OperStatus down

    Here is one from our Brocades, it shows Phone for the port description:

    Foundry locat-off-or2.company.org 10.32.161.13 GigabitEthernet1/1/15 Phone AdminStatus up OperStatus down

    ------------------------------
    Rob Carfrae
    ------------------------------


  • 2.  RE: Include port descriptions for snmp traps

    Posted 05-16-2022 19:50

    Hi Rob,

    Here is the OID for interface alias if it can help in any way. (verified on EX3400)

    1.3.6.1.2.1.31.1.1.1.18

    //Andreas



    ------------------------------
    Andreas
    ------------------------------