Skip to main content
Skip table of contents

How to receive SNMP Trap Messages

Fiorano Platform can be configured to send trap messages on occurrence of alerts and events, if so desired. This information can be sent to a pre-configured manager address or broadcast on the network for all managers listening so as to enable them to pick up this message. Trap messages can provide valuable and instant information about faults and failures. The following Fiorano Platform specific trap types are presently configured on occurrence of events:

  1. An FPS Event has occurred
  2. An Event Process Event has occurred
  3. A Business Component Event has occurred
  4. An SBW On Exception Event has occurred
  5. A server event has occurred
  6. A HA Server and GateWay State Events has occurred

The above trap numbers can be configured as enterprise specific traps in the manager for appropriate action to be taken as when they are raised.

Tables

In order to utilize the SNMP aware Fiorano Platform system, all you need to do is to configure an SNMP manager (popular ones include HP OpenView and IBM Tivoli NetView) of your choice by loading the Fiorano MIB into it. The manager can now be used to view the data; the agent provides information via six tables as follows:

Table 1: The FPS table (OID = 1.3.6.1.4.1.7163.1.1.2)

This table provides the data about the Fiorano Peer Servers configured with the Enterprise Server. It shows the following details:

  • fpsname: This is the unique name of the Fiorano ESB Peer server as configured in the Fiorano Network.
  • fpsStatus: This field shows the last event received for the peer server.
  • fpsEventTime: This represents the time at which the last event occurred.
Table 2: The Applications table (OID = 1.3.6.1.4.1.7163.1.2.2)

This table shows the data for the Event Processes that are/were running on the network. It provides the following information:

  • appInstanceName: The name of the Event Process instance.
  • appStatus: The status of the Event Process, that is, the last event that was received with respect to the concerned Event Process.
  • appEventTime: The time at which the last event occurred.
Table 3: The Services table (OID = 1.3.6.1.4.1.7163.1.3.2)

This table gives the information regarding the Business Components that are/were running on the Peer Servers that the managed Enterprise Server is connected to. The fields available are the following:

  • serviceGUID: This is a unique string that identifies a Business Component available on a Fiorano ESB Server.
  • serviceInstanceName: Since many instances on the Business Component may be running, a ComponentInstanceName is used to identify the particular instance of the concerned Business Component.
  • serviceAppInstanceName: This identifies the name of the Event Process as a part of which this particular Business Component is/was running.
  • serviceStatus: The status of the Business Component that was last received by the Enterprise Server.
  • serviceEventTime: The time at which the last event occurred.
Table 4: The SBW Events table (OID = 1.3.6.1.4.1.7163.1.4.2)

This table gives the information regarding ON_EXCEPTION events of SBW tracked messages. The fields available are the following:

  • sbwEventCategory: The event category is a Warning as only ON_EXCEPTION events are tracked.
  • sbwEventDesc: This gives the details of the particular port of service on which the event is tracked as well as the Application Instance to which the service belongs to.
  • sbwEventTime: The time at which the last event occurred
  • sbwEventErrorMessage: This gives details such as error code and error message.
Table 5: The Server Events table (1.3.6.1.4.1.7163.1.5.2)

This table gives the information regarding the status of the gateway server that is configured to run the Fiorano servers in HA mode. The event will be generated only when the server is running in HAMode.

  • serverEventaddr: The gateway server machine address.
  • serverEventStatus: This gives the details whether gateway server is running or not.
  • serverEventTime: Time at which the last event occurred
Table 6: The HA Server and Gateway State Events table (OID = 1.3.6.1.4.1.7163.1.6.2)

This table gives Ha Server and GateWay server state change Status Events.

  • haServerStateEventsaddr: The HA Server and Gateway machine addresses.
  • haServerStateEventStatus: This gives the details of HA server status and status whether Gateway server is running or not.
  • haServerStateEventsTime: Time at which the last event occurred.
JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.