Guest

CiscoWorks Resource Manager Essentials

Remote Syslog Analyzer/Collector Not Binding to the RME Server

Document ID: 19111



Contents

Introduction
Prerequisites
      Requirements
      Components Used
      Conventions
Problem
Solution
NetPro Discussion Forums - Featured Conversations
Related Information

Introduction

This document provides information about why a remote Syslog Analyzer/Collector (SAC) fails to bind with the Resource Manager Essentials (RME) server and how to overcome the failure.

Prerequisites

Requirements

There are no specific requirements for this document.

Components Used

This document is not restricted to specific software or hardware versions.

The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.

Conventions

For more information on document conventions, refer to the Cisco Technical Tips Conventions.

Problem

The remote SAC may fail to send syslog messages to the RME box because of a binding problem, which generates this Common Object Request Broker Architecture (CORBA) error:

*bindConnectSAR,Had problems binding to server

The error log at /opt/CSCOsac/lib/SyslogRemoteCollector.log shows this message on the remote box where SAC is installed:

org.omg.CORBA.OBJECT_NOT_EXIST:
Could not locate the following Object:
repository id : IDL:sareceiver/ISaReceiver:1.0
object name : BIGBOY.CISCO.COM::SaReceiver
host name : bigboy.cisco.com
minor code: 0  completed: No
at com.inprise.vbroker.orb.LocatorBidder.getBid(LocatorBidder.java:32)
at com.inprise.vbroker.ProtocolEngine.ManagerImpl.startBidding(ManagerImpl.java:114)
at com.inprise.vbroker.ProtocolEngine.ManagerImpl.getConnector(ManagerImpl.java:104)
at com.inprise.vbroker.orb.DelegateImpl._bind(DelegateImpl.java:184)
at com.inprise.vbroker.orb.DelegateImpl.bind(DelegateImpl.java:144)
at com.inprise.vbroker.CORBA.portable.ObjectImpl._bind(ObjectImpl.java:59)
at com.inprise.vbroker.orb.ORB.bind(ORB.java:1183)
at com.cisco.nm.sysloga.idl.sareceiver.ISaReceiverHelper.bind(ISaReceiverHelper.java:57)
at com.cisco.nm.sysloga.sac.CorbaCommunication.bindConnectSAR(CorbaCommunication.java:347)
at com.cisco.nm.sysloga.sac.CorbaCommunication.connectToOrb(CorbaCommunication.java:326)
at com.cisco.nm.sysloga.sac.FileReader.run(FileReader.java:484)
SyslogAnalyzer- Mon Oct 15 17:37:37 CDT 2001 5 *bindConnectSAR,Had
problems binding to server, will try to reconnect 5 times. Waiting 60 seconds
in between each try.

Solution

Follow these steps to resolve the issue:

  1. On the UNIX box where remote SAC is installed, look at the /opt/CSCOsac/lib/classpath/com/cisco/nm/sysloga/sac/SAenvProperties.ini file and verify its entries.

    • FILE= /var/log/syslog_info—This should be the same as the local7 entry in the /etc/syslog.conf file on the machine that is running RME.

    • SAC_PORT = 9000—This is the port number into which syslog is coming (typically 514).

    • SAC_SERVER: bigboy.cisco.com

    • SAC_SERVER_PORT: 42342

    • VERSION: 1.1

    • BINDNAME: bigboy::SaReceiver (Must match the SAC_SERVER entry.)

    • DEBUG_LEVEL: 4

    • SA_APP_NAME: SyslogAnalyzer

    Note: To make this remote syslog work correctly, the BINDNAME must match the values set for the SAC_SERVER variable, followed by ::SaReceiver.

    For example, if SAC_SERVER is set to bigboy.cisco.com, then the BINDNAME variable must be bigboy::SaReceiver.

  2. They both must also match the PX_HOST parameter on the host that is running RME. The PX_HOST parameter is set in these files:

    • /opt/CSCOpx/lib/classpath/md.propertis

    • /var/sadm/pkg/CSCOmd/pkginfo

  3. After you make these changes, stop and restart the remote SAC:

    #Testbox:/> cd /opt/CSCOsac/lib
    
    #Testbox:/> ./sacStop.sh
      
    Executing the SACstop script
    
    Testbox:/> ./sacStart.sh
    
    Starting Remote Syslog Analyzer Collector...
    The start script has completed.
    #Testbox:/>

This should fix a problem with the remote SAC’s failure to bind to the RME server.

NetPro Discussion Forums - Featured Conversations

Networking Professionals Connection is a forum for networking professionals to share questions, suggestions, and information about networking solutions, products, and technologies. The featured links are some of the most recent conversations available in this technology.
NetPro Discussion Forums - Featured Conversations for Network Management
Network Infrastructure: Network Management
Virtual Private Networks: Network and Policy Management

Related Information



Updated: Oct 26, 2005Document ID: 19111