DX NetOps

Expand all | Collapse all

Traps on Pingable Model

  • 1.  Traps on Pingable Model

    Posted 08-04-2011 12:59 PM
    Environment : Spectrum 9.2 on Linux Red Hat .SS and OC on same server

    Have enabled below setting to get traps for pingable device but still unable to do so

    1.added enable_traps_for_pingables = TRUE in .vnmrc file.
    2. restarted Specto server through SCP
    3. verified that traps are coming on the Spectrum Server through tcpdump

    Folloiwng are confirmation on settings on .alamrc and also trap received on
    server :

    Still traps are not visible in event tab for the pingable model.

    *****************************************************************
    snmpv3_default_auth_protocol=md5
    snmpv3_default_priv_protocol=des
    spm_wait_activate=no
    enable_traps_for_pingables=TRUE
    orb_args=-Dvbroker.se.iiop_tp.scm.iiop_tp.dispatcher.threadMax=100
    -ORBpropStorage .natfwrc
    -Dvbroker.se.iiop_tp.scm.iiop_tp.dispatcher.threadStackSize=1048
    576
    ********************************************************************

    ***OUTPUT of TCPdump on the server (SS x.x.73.101) to capture trap from the pingable model (x.x.78.156)****

    18:20:22.304009 IP (tos 0x0, ttl 63, id 0, offset 0, flags [DF], proto: UDP
    (17), length: 143) x.x.78.156.asf-rmcp > x.x.73.101.snmptrap: { SNMPv1
    { Trap(100)  E:3183.1.1 0.0.0.0 enterpriseSpecific s=552707 1312482016
    [|snmp] } }
    18:20:22.444880 IP (tos 0x0, ttl 63, id 0, offset 0, flags [DF], proto: UDP
    (17), length: 143) x.x.78.156.asf-rmcp > x.x.73.101.snmptrap: { SNMPv1
    { Trap(100)  E:3183.1.1 0.0.0.0 enterpriseSpecific s=527105 1312482016
    [|snmp] } }

    *************************************************************

    ************************************************************
    [root@NOI  Pingable]# more AlertMap
    0.0 0x10306

    1.0 0x10307

    2.0 0x10308 1.3.6.1.2.1.2.2.1.1(1,0)

    3.0 0x10309 1.3.6.1.2.1.2.2.1.1(1,0)

    4.0 0x1030a

    5.0 0x1030b 1.3.6.1.2.1.8.5.1.2(1,0)

    [root@NOI Pingable]# pwd
    /appusr/Spectrum/SS/CsVendor/Cabletron/Pingable
    [root@NOI- Pingable]#
    ****************************************************************

    Regards,
    Neeraj


  • 2.  RE: Traps on Pingable Model

    Posted 08-04-2011 04:07 PM
    You should also check disable_trap_events (0x11cd0), which is an attribute on the Pingable model. It should be set to "false" if you want traps processed. I think the Pingable model type defaults this to "true", in which case you may want to use attribute editor to change the default going forward.


  • 3.  RE: Traps on Pingable Model

    Posted 08-05-2011 12:59 AM
    Have checked as you said , but by default DisableTrapEvents set to No.


  • 4.  RE: Traps on Pingable Model

    Broadcom Employee
    Posted 08-05-2011 03:15 PM
    enable_traps_for_pingables=true should do the trick. I always tell the customers I speak with that if you cycle the SS you should bounce tomcat service as well. Did you try that? Did you check the VNM model ... do you see the traps there?


  • 5.  RE: Traps on Pingable Model

    Posted 08-09-2011 04:22 AM
    1. Do you see any "Unknown alert received from device..." events (0x10801) on the model?

    2. Check the VNM for events "...received from unknown SNMP device..." (0x10802) which Spectrum should create if it receives a trap from a device which is unknown to the system.
    (DisableUnmanagedTraps 0x11cce needs to be set to false/no)

    3. Try to specify your trap-mapping in the global AlertMap and redo your test.

    Regards,
    Jan


  • 6.  RE: Traps on Pingable Model

    Broadcom Employee
    Posted 12-05-2011 12:44 PM
    Hi Neeraj,
    Have any of these hints been helpful? Is this still an ongoing issue?
    Thx,
    Bill