Forum Discussion

Jana's avatar
Jana
Icon for Altostratus rankAltostratus
Feb 06, 2014

Event subscription in /config/eventd.xml file

Our application subscribes for event notifications from the F5 box by registering in the /config/eventd.xml file. As I understand, for the device to send notifications the enabled 1 /enabled flag needs to be set to '1' in the xml file.


  
    
      15
      200
      200
    
    
      
        9181CCCE-1974-DA0F-ED7D-A58C2FF5188
        192.168.12.184_EventSubscription
        17365880163140632576
        0
        http://192.168.12.184:8080/AppNGWeb/services/Management.EventNotificationPort
        admin
        YWRtaW4=
        -1
        1
        60
        0
        1391582803
        1391582803
        1391586450
        0
        0
        1
      
    
   
`


After setting the flag to '1' and stopping and starting the eventd service, the bigip sends a few packets to the ip:port configured in the xml file and then automatically changes the flag to '0' and sends no more packets.
I would like to understand how the events.xml works and how bigip handles event subscriptions.
BIG-IP Access Policy Manager (APM)
devops
event subscription
iControl
management
security
TMOS
  • Joe_Pruitt's avatar
    Joe_Pruitt
    Sep 11, 2014

    The eventd daemon makes several notification attempts using the Management.EventNotification interface defined in the iControl API. You must have this interface implemented on your endpoint you are pointing the notification to for this to work. If eventd gets a connection issue or invalid response, it marks the notification target down. A while back I wrote a test Event Notification Client and Listener to help debug development with this interface.

     

    You can use the client to test sending messages and Listener to test as an endpoint. If you can use the client to send a message to your endpoint, then eventd should be able to recognize it.

     

    Hope this helps...

     

    -Joe