DX Application Performance Management

  • Private Community
 View Only
Back to discussions
Expand all | Collapse all

Shell Command Action - Create text file

  • 1.  Shell Command Action - Create text file

    Posted Apr 23, 2014 06:07 AM

    Hello people,

    I need to send trap to NSM through of shell command action and create a text file with information about trap. How do this?

    I need to know how does work the shell command action, because in the workstation user guide have little information.

    Can anybody help me?
    Thank you very much.

    Regards. André Oliveira

     

     



  • 2.  RE: Shell Command Action - Create text file

    Broadcom Employee
    Posted Apr 23, 2014 11:31 AM

    Don't use a shell action; use the updated SNMP alert in 9.1.1 or higher.



  • 3.  RE: Shell Command Action - Create text file

    Posted Apr 23, 2014 12:15 PM

    I already used the "SNMP alert action" but I can't configure the trap and I want configure the trap and choosing the parameters to send to NSM.

    Thanks.



  • 4.  RE: Shell Command Action - Create text file

    Broadcom Employee
    Posted Apr 23, 2014 12:32 PM
      |   view attached

    What more do you need than alert name and value, EM/MOM name, managment module where the alert respondent should go, and the dashboard showing the alert?



  • 5.  RE: Shell Command Action - Create text file

    Posted Apr 30, 2014 09:32 AM

    I don't need anything else. The trap that is sent through the "SNMP alert action" is too large. I need to send only the importation information and only the information that I want.

    Thanks.



  • 6.  RE: Shell Command Action - Create text file

    Broadcom Employee
    Posted Apr 30, 2014 02:58 PM

    Then you can use Shell Action, but you will have to write your own method to send the trap.

    You can use the action to pick which pieces of information to send based upon what order you choose them. It's very important that you remember the order which you chose the elements. You cannot change the index once it's been set.

    Once you've chosen your alert elements, you will need to determine how you will read those commandline indexes. Most people will write a shell script, but it's really up to you how you want to process the information.

    After that, it will be up to you how you send the trap. CA cannot help with that unless you pay for a Services engagement or pay for our Global Delivery team to write a custom solution. There are many ways to send traps, so you can pick one you'd like to use.



  • 7.  RE: Shell Command Action - Create text file

    Posted May 02, 2014 05:56 AM

    Which method?

    Where I create the shell script?

    Thanks



  • 8.  RE: Shell Command Action - Create text file

    Broadcom Employee
    Posted May 03, 2014 01:52 AM

    Can you explain further your question "Which method?".

    The shell script should be placed somewhere under the root EM directory. All you need to do to call it from the shell action is provide the full path to the script.



  • 9.  RE: Shell Command Action - Create text file

    Posted May 06, 2014 05:18 AM

    Sorry.

    Which is the method that I will have to write?

    Where I provided the full path to the script?

    I am beginner in APM sorry.

    Thanks.



  • 10.  RE: Shell Command Action - Create text file

    Broadcom Employee
    Posted May 07, 2014 04:41 PM
      |   view attached

    You need to write basically everything: the shell script to process the input parameters and the program you're using to send the trap.

    The only thing we're providing is the mechanism to pass the metric info. You will need to figure out the rest. You're better off using the SNMP alert action and dealing with the available data at your alerting tool.



  • 11.  RE: Shell Command Action - Create text file

    Broadcom Employee
    Posted May 07, 2014 04:48 PM

    I believe we're now beyond what is supported on APM.

    You should check with other NSM Bridge users over in the IM community see what others are doing there.



  • 12.  RE: Shell Command Action - Create text file

    Broadcom Employee
    Posted May 07, 2014 04:51 PM

    Take a look at the bookshelf info about the integration: http://goo.gl/DWhlr4



  • 13.  RE: Shell Command Action - Create text file

    Posted May 14, 2014 06:44 AM

    I receive the trap in NSM through SNMP alert action, and the trap is:

    %CATD_I_060, SNMPTRAP: -c public 791 10.126.101.125 mtsmchwily01.mch.moc.sgps 6 1 0:00:00 18 OID: 1.3.6.1.4.1.791.4.4.15 .iso.org.dod.internet.private.enterprises.791.4.4.15 VALUE: 2 OID: 1.3.6.1.4.1.791.4.4.16 .iso.org.dod.internet.private.enterprises.791.4.4.16 VALUE: 3 OID: 1.3.6.1.4.1.791.4.4.1 .iso.org.dod.internet.private.enterprises.791.4.4.1 VALUE: Wed May 14 10:44:30 OID: 1.3.6.1.4.1.791.4.4.17 .iso.org.dod.internet.private.enterprises.791.4.4.17 VALUE: 2014-05-14T10:44:30+0100 OID: 1.3.6.1.4.1.791.4.4.2 .iso.org.dod.internet.private.enterprises.791.4.4.2 VALUE: MTSMCHWILY01 OID: 1.3.6.1.4.1.791.4.4.3 .iso.org.dod.internet.private.enterprises.791.4.4.3 VALUE: 10.126.101.125 OID: 1.3.6.1.4.1.791.4.4.4 .iso.org.dod.internet.private.enterprises.791.4.4.4 VALUE: 14/05/14 10:44:30 BST The Alert "CM-STATUS-PTMTSMCOAPP01:8080/ok.htm" exceeded danger target of 1: SuperDomain|MTSMCHWILY01|WebMonitor|DCINTRANET|url|INTRANET|Continente_no_telemovel|ptmtsmcoapp01:Status = 1 OID: 1.3.6.1.4.1.791.4.4.5 .iso.org.dod.internet.private.enterprises.791.4.4.5 VALUE: SuperDomain OID: 1.3.6.1.4.1.791.4.4.6 .iso.org.dod.internet.private.enterprises.791.4.4.6 VALUE: MTSMCHWILY01 OID: 1.3.6.1.4.1.791.4.4.7 .iso.org.dod.internet.private.enterprises.791.4.4.7 VALUE: WebMonitor OID: 1.3.6.1.4.1.791.4.4.8 .iso.org.dod.internet.private.enterprises.791.4.4.8 VALUE: DCINTRANET OID: 1.3.6.1.4.1.791.4.4.9 .iso.org.dod.internet.private.enterprises.791.4.4.9 VALUE: url|INTRANET|Continente_no_telemovel|ptmtsmcoapp01:Status OID: 1.3.6.1.4.1.791.4.4.10 .iso.org.dod.internet.private.enterprises.791.4.4.10 VALUE: 1 OID: 1.3.6.1.4.1.791.4.4.11 .iso.org.dod.internet.private.enterprises.791.4.4.11 VALUE: http://10.126.101.125:8080/console/frameset.do?managementModuleName=Sample&domainName=SuperDomain&dashboardName=Overview OID: 1.3.6.1.4.1.791.4.4.12 .iso.org.dod.internet.private.enterprises.791.4.4.12 VALUE: 1 OID: 1.3.6.1.4.1.791.4.4.13 .iso.org.dod.internet.private.enterprises.791.4.4.13 VALUE: 1 OID: 1.3.6.1.4.1.791.4.4.14 .iso.org.dod.internet.private.enterprises.791.4.4.14 VALUE: no OID: 1.3.6.1.4.1.791.4.4.25 .iso.org.dod.internet.private.enterprises.791.4.4.25 VALUE: 10.126.101.125

    This trap is unfriendly and very big. I needed to filter the information to send to NSM. Do you understand?



  • 14.  RE: Shell Command Action - Create text file

    Broadcom Employee
    Posted May 14, 2014 03:35 PM

    When you say, "unfriendly and big", is this your opinion or is NSM having a problem handling the trap?

    If this is NSM complaining, then you either open a support ticket or seek advise from the NSM community.



  • 15.  RE: Shell Command Action - Create text file

    Posted May 15, 2014 05:22 AM

    Is NSM having a problem handling the trap.

    The trap sent by introscope to NSM is big e unfriendly and the NSM can't trat it. I wanted send to NSM only the important information about alert.

    Thank you very much.



  • 16.  RE: Shell Command Action - Create text file

    Broadcom Employee
    Posted May 15, 2014 05:31 AM

    If you have read the guide, you would have seen this: https://support.ca.com/cadocs/1/CA%20Application%20Performance%20Management%209%201%201-ENU/Bookshelf_Files/HTML/APM_Config_Admin_EN/index.htm?toc.htm?1478780.html?zoom_highlight=OIDs

    If you look at the APM 9.5 NSM Integration Guide, it talks about the issue of CEM sending too much data in the trap and how to resolve the issue: https://support.ca.com/cadocs/0/CA%20Application%20Performance%20Management%209%205-ENU/Bookshelf_Files/HTML/APM_9.5--NSM%20Integration%20Guide/index.htm

    Beyond this, you will need to talk to support, or check with other NSM users in the IM 2.0 community.



  • 17.  RE: Shell Command Action - Create text file

    Broadcom Employee
    Posted May 07, 2014 10:56 PM

    You should take a look at the troubleshooting section of the NSM Integration Guide.

    It describes a scenario where too much data is being sent about CEM to NSM. This may also apply to APM and can be resolved by modifying some regex patterns.



  • 18.  RE: Shell Command Action - Create text file

    Broadcom Employee
    Posted May 08, 2014 12:00 AM

    I've apparently forgotten the basic questions (more caffeine, please):

    1. What version of CA APM are you using?
    2. What version of NSM are you using?
    3. Are both items compatible with each other (check the compatibility matrix for the APM version you're using and NSM Integration Guide)?


  • 19.  RE: Shell Command Action - Create text file

    Posted May 08, 2014 11:50 AM

    Don't worry.

    The version of APM is 9.1.6.

    The version of NSM is 11.2.

    Yes, is compatible.

    Thank you.



  • 20.  RE: Shell Command Action - Create text file

    Broadcom Employee
    Posted May 08, 2014 11:53 AM

    At this point, I would recommend you read the Troubleshooting section of the guide as it pertains to too many objects in the trap.

    The same resolution should work whether it is for CEM or Introscope. If you are unsure at this point, please contact support.



  • 21.  RE: Shell Command Action - Create text file

    Posted May 14, 2014 05:04 AM

    Thanks.

    My problem now is write the shell script.

    What I have to write in the shell script?

    Regards.



  • 22.  RE: Shell Command Action - Create text file

    Broadcom Employee
    Posted May 14, 2014 11:35 AM

    Your shell script will not have OIDs, but the items in my previous screenshot.

    Your script will need to parse the input and send it to your SNMP generator, which sends the script data as a trap.

    Descriptors for the OIDs are available in the documentation. If you cannot find it for your version, please open a ticket with support.



  • 23.  RE: Shell Command Action - Create text file

    Posted May 14, 2014 12:36 PM

    What is the documentation guide?

    Thanks.



  • 24.  RE: Shell Command Action - Create text file

    Broadcom Employee
    Posted May 14, 2014 03:25 PM

    The APM Workstation Guide has details on the alert OIDs that you will need to generate for NSM to accept it.

    Have you bothered to read the troubleshooting guide that mentioned previously which discusses the problem you're having? It tells you how to resolve the issue.



  • 25.  RE: Shell Command Action - Create text file

    Posted May 15, 2014 05:09 AM

    I don't found details on the alert OIDs in APM Workstation Guide.

    yes I read , but the problem isn't about NSM integration with CEM. The problem is about introscope send a big trap to NSM.



  • 26.  RE: Shell Command Action - Create text file
    Best Answer

    Broadcom Employee
    Posted May 15, 2014 05:19 AM

    It's still the same problem; Introscope sends the traps, not CEM, so you really need to read the troubleshooting section of the Integration Guide concerning the large CEM/Introscope traps.



  • 27.  RE: Shell Command Action - Create text file

    Broadcom Employee
    Posted Apr 23, 2014 04:06 PM

    If you really insist on using a shell action, there are instructions in the guide for using it.

    After passing that data to the shell, it will be outside of CA support and you will have to figure it out on your own. Which means you will have to create your own trap generator to read the input data and make sure the NSM knows how to parse your OIDs.