Determines whether the events generated by the software will be logged
locally or on a centralised CPU card within the chassis.
A value of 0 or a value equal to the local slot number will enable local
Event Manager processing (events filtering, logging and trap generation).
Other values determines the central Event Manager CPU slot number (1 to 16).
When central Event Manager is enabled, all the events manager messages are
filtered locally and then sent to the CPU card specified by this object for
recording.
Centralised event manager is avaliable only in CX1000 and CX2000 products.
In single CPU units, like the CX900 or the CX950, the value will be fixed
to 0 allowing local Event Manager processing only.
A log file can be read by the console through UI module. The syntax of
the reading command is defined as follows:
Command: readlog
Determines whether the events generated by the software will be logged
locally or on a centralised CPU card within the chassis.
A value of 0 or a value equal to the local slot number will enable local
Event Manager processing (events filtering, logging and trap generation).
Other values determines the central Event Manager CPU slot number (1 to 16).
When central Event Manager is enabled, all the events manager messages are
filtered locally and then sent to the CPU card specified by this object for
recording.
Centralised event manager is avaliable only in CX1000 and CX2000 products.
In single CPU units, like the CX900 or the CX950, the value will be fixed
to 0 allowing local Event Manager processing only.
A log file can be read by the console through UI module. The syntax of
the reading command is defined as follows:
Command: readlog
Vendor: Memotec Communications
Module: CXEventManager-MIB
[Automatically extracted from oidview.com]
cxEvmLoggingCPU OBJECT-TYPE SYNTAX INTEGER (0..16) ACCESS read-write STATUS mandatory DESCRIPTION "Determines whether the events generated by the software will be logged locally or on a centralised CPU card within the chassis. A value of 0 or a value equal to the local slot number will enable local Event Manager processing (events filtering, logging and trap generation). Other values determines the central Event Manager CPU slot number (1 to 16). When central Event Manager is enabled, all the events manager messages are filtered locally and then sent to the CPU card specified by this object for recording. Centralised event manager is avaliable only in CX1000 and CX2000 products. In single CPU units, like the CX900 or the CX950, the value will be fixed to 0 allowing local Event Manager processing only. A log file can be read by the console through UI module. The syntax of the reading command is defined as follows: Command: readlog
cxEvmLoggingCPU OBJECT-TYPE SYNTAX INTEGER (0..16) ACCESS read-write STATUS mandatory DESCRIPTION "Determines whether the events generated by the software will be logged locally or on a centralised CPU card within the chassis. A value of 0 or a value equal to the local slot number will enable local Event Manager processing (events filtering, logging and trap generation). Other values determines the central Event Manager CPU slot number (1 to 16). When central Event Manager is enabled, all the events manager messages are filtered locally and then sent to the CPU card specified by this object for recording. Centralised event manager is avaliable only in CX1000 and CX2000 products. In single CPU units, like the CX900 or the CX950, the value will be fixed to 0 allowing local Event Manager processing only. A log file can be read by the console through UI module. The syntax of the reading command is defined as follows: Command: readlog
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.495.2.1.5.17.1.0 | cxEvmLoggingCPU | 0 | 0 | None |
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.495.2.1.5.17.2 | cxEvmTriggerFunction | 1 | 1 | Activates the Event Manager triggering mechanism. This triggering mechanism will send a MSG_EVM_TRIG type message that will con… |
| 1.3.6.1.4.1.495.2.1.5.17.3 | cxEvmTrigDestSelector | 1 | 1 | Specifies the module to which the Event Manager triggering function will send the triggering message. Modules are the different t… |
| 1.3.6.1.4.1.495.2.1.5.17.4 | cxEvmTrigDestSapId | 1 | 1 | Specifies the Sap ID to which the Event Manager triggering function should be applied. Range of Values: 0 to 255 Default Value: 0 C… |
| 1.3.6.1.4.1.495.2.1.5.17.5 | cxEvmTrigArgument1 | 1 | 1 | Specifies the value of the first optional parameter that can be used with the triggering function. Range of Values: 0 to 255 Defau… |
| 1.3.6.1.4.1.495.2.1.5.17.6 | cxEvmTrigArgument2 | 1 | 1 | Specifies the value of the second optional parameter that can be used with the triggering function. Range of Values: 0 to 255 Defa… |
| 1.3.6.1.4.1.495.2.1.5.17.7 | cxEvmTrigDestCPU | 1 | 1 | Specifies the destination CPU of the trigger function. For centralised CPU only. A value of 0 means the local CPU. For single… |
| 1.3.6.1.4.1.495.2.1.5.17.8 | cxEvmLogFileTable | 1 | 8 | A table that defines a log file id, size, and filters applied to this file. When saving configuration, the table is saved and wh… |