Loading ...
Sorry, an error occurred while loading the content.

46931[mh] xpl errors reported by external hub

Expand Messages
  • George Clark
    Mar 1, 2014
    • 0 Attachment
      Hi Lieven,

      I've found the issue causing the xpl errors being reported by the
      external hub. When Generic_Item.pm sends an xpl status message, it
      makes the following call - line 1119

      if ($send_xpl and $set_by !~ /^xpl/i) {
      &xPL::sendXpl('mhouse.item', 'xpl-stat', 'mhouse.item' =>
      {name => $$ref{object_name}, state => $state,
      state_prev => $$ref{state_prev}, set_by => $set_by, mh_target => $target});

      However in xPL_Item.pm, the msg_type is prepended with the "xpl-"
      prefix. The end result is an xpl message with the msg-type of
      "xpl-xpl-stat" which is rejected by the hub. A quick grep for sendXpl
      shows that all other calls in the core don't use the xpl- prefix. So I
      think it's a simple fix to Generic_Item.pl.

      sub sendXpl {
      if ( defined($xpl_send) ) {
      my ( $target, $msg_type, @data ) = @_;
      my ( $parms, $msg );
      $msg = "xpl-$msg_type\n{\nhop=1\nsource="
      . &xPL::get_xpl_mh_source_info() . "\n";


      Flow-based real-time traffic analytics software. Cisco certified tool.
      Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer
      Customize your own dashboards, set traffic alerts and generate reports.
      Network behavioral analysis & security monitoring. All-in-one tool.
      To unsubscribe from this list, go to: https://lists.sourceforge.net/lists/listinfo/misterhouse-users