DX NetOps

  • Private Community
 View Only

  • 1.  Debug SS Server based on Trap OID, instead of IP address

    Posted Sep 13, 2017 02:23 PM

    The Tech Tip: Debugging trap processing in a Spectrum Distributed SpectroSERVER environment is handy.

    But, how can we adjust so that we can look for a specific trap OID, instead of the device IP address?



  • 2.  Re: Debug SS Server based on Trap OID, instead of IP address

    Posted Sep 13, 2017 02:32 PM

    Are you looking to see if a specific trap oid is configured in Spectrum?

     

    Joe



  • 3.  Re: Debug SS Server based on Trap OID, instead of IP address
    Best Answer

    Broadcom Employee
    Posted Sep 13, 2017 02:45 PM
      |   view attached

    Here’s a couple of examples from an old internal doc.  My apologies, I can’t explain or provide info on what the index, attr, and/or type could have for values.  We just use these specific examples when tracing oids.

    To turn on debug for alert 1.3.6.1.4.10.1.1:

    ./update action=0x10245 mh= index=0,attr=0,type=0x12,val=1.3.6.1.4.11.1 index=1,attr=1,type=0x13,val=1.2.3.4

     

    Cheers

    Jay



  • 4.  Re: Debug SS Server based on Trap OID, instead of IP address

    Posted Sep 13, 2017 02:54 PM

    Thanks, Joe and Jay.

    No, I am not looking if it is configured.

    I am looking for how it is handled (processed) by SS when it is received.  I don't care where it came from (the source); instead I simply want the 'trap' from any source.

    So, while Jays' 'update action' shows the type and val parameters that include an OID (trap id); type 0x12; and an IP address; type 0x13; I think I only need to specify type 0x12.

    This should give me what I was looking for.

    I'll let you know.

    Thanks,

    Jim



  • 5.  Re: Debug SS Server based on Trap OID, instead of IP address

    Posted Sep 14, 2017 09:29 AM

    Thanks guys.  Provided what I needed.



  • 6.  Re: Debug SS Server based on Trap OID, instead of IP address

    Broadcom Employee
    Posted Sep 14, 2017 12:04 PM

    Weird...while the info that shows above was correct, the email reply I actually sent was not all included.  I'm not sure if the whole thing made it through the system or not, so I'm posting to the thread directly what my actual reply was:

     

    Here’s a couple of examples from an old internal doc.  My apologies, I can’t explain or provide info on what the index, attr, and/or type could have for values.  We just use these specific examples when tracing oids.

     

    To turn on debug for alert 1.3.6.1.4.10.1.1:

    ./update action=0x10245 mh=<VNM mh> index=0,attr=0,type=0x12,val=1.3.6.1.4.10.1.1

     

    To turn on debug only for alert OID 1.3.6.1.4.11.1 and IP 1.2.3.4:

     ./update action=0x10245 mh=<VNM mh> index=0,attr=0,type=0x12,val=1.3.6.1.4.11.1 index=1,attr=1,type=0x13,val=1.2.3.4