BMC ProactiveNet 9. Pages Blog. Page tree. Browse pages. Remove Read Confirmation. A t tachments 3 Page History People who can view. Default: mcxa, the default specified in the mcxa. Required - if the port number has been changed from in mcxa. To stop an Adapter, the Adapter must be enabled, and the engine manager must already be running. To start or stop an Adapter by using the mcxactrl.
When executing the mcxactrl. The default port number recorded in the CtrlPort Adapter definition in the mcxa. For information about additional command line options, see Table 14 on page I by using the mcxa. Table 13 on page 61 lists the command line options that you can use to enable tracing with the mcxa. Each time the Adapter is started, a new trace file is created and old logs are rotated.
A value of 0 zero removes all old trace files. For more information and default values, see the header of the mcxa. You can specify a different trace file in a different location by using the mcxa.
For more information about command line options, see Table 13 on page This setting will apply to all Adapters running in the Adapter framework. When the Adapter encounters a major or fatal error in the configuration file, the Adapter reports the error in the trace file according to the trace level. When the error does not come from the configuration file, the Adapter reports the error to the cell whose name corresponds to the ServerName parameter of the [default] unnamed section of the configuration file.
Table 15 describes the status events. Accessing the Web-based interface. Publishing MIB files. Viewing or editing the MAP file. Unpublishing MIB files. You must specify at least one MIB file. A new row is added below the existing row. You can simultaneously publish a maximum of 10 MIB files. To identify the exact reason for this message, you must check the output of the mib2map. The event classes are displayed in a tree structure. You can select an event class, and then add new variables, or edit and remove existing variables from that event class.
The modifications that you make in the mcsnmptrapd. You can add, edit, or remove the following variables from the mcsnmptrapd. You can then modify the data for the event classes on your local computer.
When you retrieve the event classes data from the server, the mcsnmptrapd. While you are modifying the mcsnmptrapd. I To add a variable, click Add New. In the Add New Variable dialog box, select the variable, and enter or select the value for that variable. To edit a variable, click the value of that variable. In the Update Value dialog box, modify the value. To remove a variable, select the check box next to that variable, and click Remove. I I 4 To save the changes, click Save.
The changes made to the event class are saved on your local computer. You can edit more than one event class before you save the changes on the server. The modifications made to the event classes in the mcsnmptrapd.
The asterisk indicates that the mcsnmptrapd. The MIB files are listed in an alphabetical order. Press the Shift or Ctrl key to select multiple files. The Unpublish button is enabled only when you select at least one MIB file. You have to install the mcsnmptrapdmib. Though the entries do not have to be listed consecutively in the. Instead, it runs as a service.
It reads events generated on Microsoft Windows operating systems, formats them into the BAROC language, and forwards the events to the cell. Event gathering occurs from three basic event logs maintained by the Microsoft Event Log service: system, application, and security. The Adapter can automatically discover these event logs, so if new event logs are defined, basic events are produced.
This file also contains classes for standard events sent by the msend CLI. Use the console to view the test events. The Performance window is displayed in the Chart display mode, as shown in Figure 13 on page The Alerts icon and available logs icons appear in the right pane. The setting window for the new alert is displayed. The alert is added to the Performance Monitor and the Event Log. You use the Performance Monitor to create test events, perform a few small operations, such as opening an application, maximizing and minimizing an application window, or moving the mouse vigorously.
Allow the Performance Monitor to generate alerts during the test. Events display in the Event Viewer window. IP Adapter architecture. IP Adapters configuration.
IP Adapter types. TCP Client Adapter. TCP Server Adapter. Telnet Adapter. UDP Client Adapter. UDP Server Adapter. Overview The IP Adapters use the various protocols of the IP protocol suite to establish connections with programs from which you want to generate events. With the IP Adapters, you are able to specify the connection method to the data source and the type of parsing that you want performed on the collected data.
Data that is collected using an IP connection is parsed into a Perl hash name-value pair data tokens by a parser that you specify. The parsed data is passed to a mapping function, which converts the data tokens into events. The events are sent to msend, which passes them to the cell. The IP Adapters are bundled with three pluggable parsers.
You specify which parser you want to use as a parameter in the Adapter configuration. When an Adapter is started, it registers to the loop. The loop checks to see if any file descriptors are active.
When a descriptor becomes active, the Adapter receives the new data. IP Adapters configuration The Adapter configuration is contained in a list of parameters that are recorded in the Adapter definition in the mcxa. Each Adapter has unique parameters that apply only to that instance of the parameter. In addition, global and common parameters also determine the configuration of an Adapter parameter instance where instance-specific parameters do not override them.
With the variety of different Adapters that are available, you can select the means for collecting event data that is most appropriate to your requirements. Specific parameters determine how a single instance of an Adapter behaves.
However, Adapter behavior is also determined by global and common parameters. The settings of global and common parameters affect multiple instances of various types of Adapters. The Adapter passes the data stream to a parser. The parser parses the data stream into data tokens, which the mapping function converts into events. Table 16 Parameter instanceName TCP Client Adapter configuration parameters part 1 of 3 Description name of the Adapter instance The instance name is the first entry in the Adapter configuration and must be enclosed in square brackets.
By default, the Adapter will bind to the default interface. Valid values: host name or IP address Note: Do not specify localhost, LocalPort local port number to which the TCP Client Adapter binds Default: ANY Mapfile name of the MAP file used to generate events from the tokenized data required Parser parser instance to use to parse and tokenize the client input stream required You must code the name of another section in the mcxa.
It is not valid to code the name of a parser type as would be used in the Engine parameter. Optionally, you can enable tracing by setting the tracing parameters in the global section of the mcxa. For more information, see the event that is created for this error. These clients send data streams to the Adapter. Instead, the Adapter interprets Telnet information as raw data. Table 17 Parameter instanceName TCP Server Adapter configuration parameters part 1 of 2 Description name of the Adapter instance The instance name is the first entry in the Adapter configuration and must be enclosed in square brackets.
To eliminate looping problems with SGA, each command is accepted or rejected only once and the reply is consistent every time. The current Telnet Adapter supports a minimal set of Telnet Negotiation commands. Table 18 Parameter instanceName Telnet Adapter configuration parameters part 1 of 4 Description name of the Adapter instance The instance name is the first entry in the Adapter configuration and must be enclosed in square brackets.
After this time, the connection is considered unsuccessful. Default: 15 seconds LocalHost local IP address on a computer with multiple network interfaces to which the Telnet Adapter binds Specify a value for this parameter only when the Adapter is on a computer that has multiple network interfaces.
Default: 60 RestartWhenDone reestablishes a connection when it fails or is broken due to a hang-up Valid values: I I 0 — no reconnect 1 — reconnect Default: 0 TelnetAuthTimeout maximum time, in seconds, to wait for the completion of the authentication phase required TelnetCommand command to execute after logging onto the remote computer required 92 BMC Impact Event Adapters User Guide Telnet Adapter Table 18 Parameter Telnet Adapter configuration parameters part 4 of 4 Description password used to connect to the remote computer required TelnetPassword TelnetUsername user name used to connect to the remote computer required Figure 16 shows a sample Telnet Adapter configuration, as it would appear in the mcxa.
Table 19 Parameter instanceName UDP Client Adapter configuration parameters part 1 of 2 Description name of the Adapter instance The instance name is the first entry in the Adapter configuration and must be enclosed in square brackets. ConnectTimeout maximum time a connection will stay active After the period of time specified in ConnectTimeout has expired, the Adapter closes the connection.
No more data will be received from that connection. If no ConnectTimeout value is specified or if the value specified is 0, the timer is disabled. This is the default behavior. Engine type of Adapter in use. LocalHost local IP address on a computer with multiple network interfaces to which the UDP Client Adapter binds Specify a value for this parameter only when the Adapter is on a computer that has multiple network interfaces. Valid values: host name or IP address Warning: Do not specify localhost, Table 20 Parameter instanceName UDP Server Adapter configuration parameters part 1 of 2 Description name of the Adapter instance The instance name is the first entry in the Adapter configuration and must be enclosed in square brackets.
Default: 15 IdleTimeout LocalHost local IP address on a computer with multiple network interfaces to which the UDP Client Adapter binds Specify a value for this parameter only when the Adapter is on a computer that has multiple network interfaces. Note: Do not specify localhost, This engine cannot be replaced or modified. You do not need to specify the parser in the Adapter definition.
For each IP Adapter, you must specify a parser in the Adapter definition in the mcxa. The IP Adapter requests the parser as an object. The parameter LogRecordSeparator contains the record separator of the events. In other cases, the parsing will be multi-lined. I LogRegExpr is not empty. In this case, the regular expression contained in LogRegExpr will be applied to the log file from the point at which the previous successful matching stopped. LogVarPrefix contains the names of variables containing subpatterns.
The parser returns each value as a token to the mapper. To specify the CSV parser 1 Using a text editor, open the mcxa. Table 21 on page describes the parameters that you can modify in the parser definition. Default: comma , FieldSeparator KeepEmptyRecords indicates whether empty records are formatted as tokens and passed to the mapping function required Valid values: I I 1 — tokenize empty records 0 — discard empty records Default RecordNegFilter a regular expression that acts as a criterion to which each parsed record is compared If the criterion is included in the record, the record is discarded.
RecordPosFilter a regular expression that acts as a criterion to which each parsed record is compared If the string is included in the record, the record is formatted as a token and passed to the mapping function. You cannot rename it. VarPrefix variable prefix used by the mapper Each token will be returned as prefix Default: varlog Default variables sent to the mapper are named varlog0, varlog1, Specifying a Fixed-width column parser The fixed-width parser, MA::Parser::FixedWidth, is a pluggable parser that parses a datastream into records.
From each record, a field is extracted based on a fixed-width format. To specify the fixed-width parser 1 Using a text editor, open the mcxa. Table 22 on page describes the parameters that you can modify in the parser definition. Chapter 8 BMC Impact Event Adapters parsers Specifying a Fixed-width column parser Table 22 Parameter Fixed-Width parser parameters part 1 of 2 Description FieldDefinitions a numerical pair that specifies which data are used in a field The first number in the pair specifies from which character in the string to begin collecting data.
The second number specifies how many consecutive characters are to be included in the field. Figure 20 shows a sample parser definition for a parser named MyParser.
Defining Fields The contents of each field are determined by a pair of numbers. Each record from which the field is extracted is a string of data. The first field number indicates the starting position in the record at which the string field begins. The second number indicates the length of the string. A starting number of 5 indicates that the string begins with the sixth character in the record string. The A is at position 0, and then starting from position 0, three characters are selected to comprise the field.
The L is at position 11, and then starting from position 11, two characters are selected to comprise the field. Either number in the field specification can include a negative number. I When the starting point the first number is negative, the starting position is determined from the end of the record. The S is at position -8, and then starting from position -8, three characters are selected to comprise the field.
I When the field length the second number is negative, the end point of the string is calculated by counting back that number of characters from the end of the string and including everything in between the start point and up to that end point. The string starts at I position 8 and includes all but the last three characters in the record string. The string starts at G position and includes all but the last four characters in the record string.
Jira links Workflow Read Confirmation. Created by Confluence Admin on Jul 28, On UNIX computers, you start the engine manager mxca process from the command line. For instructions, see Starting the engine manager process from the command line and Starting the adapter processes as services. For more information, see Using instance control to start and stop adapters.
When running on Microsoft Windows computers, all adapters that use the engine manager can be started from the command line or from the Services window. Starting the engine manager process from the command line At a command prompt, run the mcxa. Use one of the following option formats: Designate a cell name by specifying -n cellname.
This format option maps the specified cell name to the host, port, and encryption key by looking the values up in the mcell. Designate a host, port, and encryption key by using -n host:port key.
Use a single colon : in the command to send output to the specified trace file. Note Command-line interface options take priority over options in the mcxa. Note Do not use the kill -9 command to stop the adapters unless they are in an infinite loop. Note If you stop and start the BMC Event Adapters service in quick succession, or use the restart option in the service manager, you might see the following error messages in the operator console: Couldn't be an UDP server on port 16 mcxactrl.
Warning Use the CtrlPort Adapter with caution. Note Double hyphens must precede the options of the mcxactrl. Parameter Description --debug Activates debugging of the procedure that is specified starting, stopping, listing, and so on Optional For more information, contact BMC Software support. Optional --stop instancename Stops the specified adapter instance. Optional --stopmgr Stops the engine manager specified with --mgr. Note After the CtrlPort Adapter is enabled, you can run the mcxactrl.
Note Double hyphens, not single hyphens, must precede the arguments in the mcxactrl. Content Tools. Reporter Replacement. Activates debugging of the procedure that is specified starting, stopping, listing, and so on Optional For more information, contact BMC Software support. Engine manager affected by the command Optional Default: mcxa , the default specified in the mcxa.
0コメント