Configuring Entuity to send notifications to BMC Network Automation

You can configure Entuity to forward device events such as Routing CPU High Utilization and SNMP Not Responding to BMC Network Automation as syslog events. These events are then included in Change Summary reports and can be used in satisfying triggering conditions in the network that warrant notification, such as AvailMonitor Node Down and Configuration Change in past 2 hours. This topic includes the following sections:

• Configuring Entuity when BMC Network Automation is co-located
• Configuring Entuity when BMC Network Automation is on separate server

Configuring Entuity when BMC Network Automation is co-located

The following procedure describes how to configure Entuity to notify BMC Network Automation when the BMC Network Automation is co-located with the Entuity server:

1. Copy the forkevent_ena.cfg file from BCAN_HOME\public\entuity to EYE_INSTALL\etc.
2. View EYE_INSTALL\etc\forkevent_ena.cfg and check the following:
   1. If Entuity is installed on Windows, go to the section called [fork_nt]. 
   2. If Entuity is installed on UNIX, go to the section called [fork_unix]. 

   3. Ensure that the start= and directory= field values are set correctly.
       By default, they are set to the BMC Network Automation default installation directories. Here is an example of what the [fork_nt] section will look like for a default installation:

      [fork_nt]
      start=c:\progra~1\bmcsof~1\bca-networks_jvm\bin\java \-jar
      bcan-syslogdriver-all.jar \-h 127.0.0.1
      args=${event.PAPIDescr} EYE Group ID:${event.PAPIEventGroup},
       ${event.PAPIEventStr}
      type=fork
      directory=<bcan-install-dir>\tools
      

   4. In the following section, ensure that the user name and password match an Entuity logon name and password. The view= field value specifies the Entuity view from which events are forwarded.

      [connection]
      username=admin
      password=admin
      view=Regional
      
3. Edit the following file:
   • (Windows): EYE_INSTALL\etc\startup_WIN32.cfg
   • (UNIX): EYE_INSTALL/etc/startup_UNIX.cfg

4. Add the following lines of code at the end of the file:

   [forkevent]
   state=normal
   type=command
   is_critical=n
   start=${ENTUITY_HOME}${FPS}integ${FPS}ForkEvent${FPS}forkevent
   ${ENTUITY_HOME}${FPS}etc${FPS}forkevent_ena.cfg fork_nt
   
5. Restart the Entuity server processes.

_{Back to top}

Configuring Entuity when BMC Network Automation is on separate server

The following procedure describes how to configure Entuity to notify BMC Network Automation when the BMC Network Automation server is on a separate server from Entuity:

1. Transfer the forkevent_ena.cfg file from BCAN_HOME\public\entuity to EYE_INSTALL\etc.

2. Transfer the bcan-syslogdriver-all.jar file from BCAN_HOME\tools to EYE_INSTALL.

   Note

   Integration with BMC Network Automation requires Java version 1.6 or later to be installed on the Entuity host.

3. View EYE_INSTALL\etc\forkevent_ena.cfg and check the following:
   1. If Entuity is installed on Windows, go to the section called [fork_nt]. If Entuity is installed on UNIX, go to the section called [fork_unix].
      
      1. Change the start= value to specify the path to Java or remove the path specification to defer to the system path.
      2. Change the directory= value to the location of the bcan-syslogdriver-all.jar file. If you followed the previous step, this is EYE_INSTALL.

      3. Ensure the IP address listed after the -h option is the IP address where BMC Network Automation is installed.
         
         Here is an example of what the [fork_nt] section typically looks like when Entuity and BMC Network Automation are not co-located:

         [fork_nt]
         start=java \-jar bcan-syslogdriver-all.jar \--h 192.168.1.10
         args=${event.PAPIDescr} EYE Group ID:${event.PAPIEventGroup},
          ${event.PAPIEventStr}
         type=fork
         directory=c:\entuity

   2. In the following section, ensure that the user name and password match an Entuity logon name and password. The view= value specifies the Entuity view from which events are forwarded.

      [connection]
      username=admin
      password=admin
      view=Regional
      
4. Edit the following file:
   • (Windows): EYE_INSTALL\etc\startup_WIN32.cfg
   • (UNIX): EYE_INSTALL/etc/startup_UNIX.cfg

5. Add the following lines of code to the end of the file:

   [forkevent]
   state=normal
   type=command
   is_critical=n
   start=${ENTUITY_HOME}${FPS}integ${FPS}ForkEvent${FPS}forkevent
    ${ENTUITY_HOME}${FPS}etc${FPS}forkevent_ena.cfg fork_nt
   
6. Restart the Entuity server processes.

_{Back to top}