Guest

CiscoWorks Resource Manager Essentials

How to Troubleshoot RME 3.1/3.2 and CM 3.0/3.1 Failure on Solaris

Document ID: 7101



Contents

Introduction
Prerequisites
      Requirements
      Components Used
      Conventions
Symptoms
Reason
Workaround
NetPro Discussion Forums - Featured Conversations
Related Information

Introduction

This document provides information about Common Object Request Broker Architecture (CORBA)-based applications. This document tells how to overcome the failure these CORBA-based applications experience on the Sun Microsystems Solaris operating system.

Note: The information in this document is only applicable for the Solaris versions of CISCOWORKS Resource Manager Essentials versions 3.1 and 3.2, and CISCOWORKS Campus Manager versions 3.0 and 3.01.

Prerequisites

Requirements

There are no specific requirements for this document.

Components Used

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

Conventions

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

Symptoms

CORBA-based applications such as CiscoWorks Campus Manager, Cisco Syslog Analysis, Update Archive, and cwconfig fail to work on Solaris if localhost is the first entry in /etc/hosts.

This error messages displays in the /var/adm/CSCOpx/log/daemons.log file:

----------- 
SyslogAnalyzer Info: host=rscand-nms port=42342 server=LogSvr 
LSsClient custom object created 
LSsClient object created SyslogAnalyzer- Wed Apr 21 10:40:20 EDT 1999 2 Initializing Dmgtd 
924705620332 April 21, 1999 10:40:20 AM ChangeProbeSupplier localhost Error EDSSY0012:    Unable to connect to EDS 
924705620369 April 21, 1999 10:40:20 AM ChangeProbeSupplier localhost Error EDSSY0012:    Unable to connect to EDS
... 
... 
... 
NMCS:Kicking off new device updates ... 
924705623054 April 21, 1999 10:40:23 AM CfgChangeProbe localhost Error EDSAT0001:    Unable to connect to EDS Atom Service 
924705623270 April 21, 1999 10:40:23 AM CfgChangeProbe localhost Error EDSAT0001:    Unable to connect to EDS Atom Service Error getting atom locale
924705623307 April 21, 1999 10:40:23 AM CfgChangeProbe localhost Error EDSAT0001:    Unable to connect to EDS Atom Service Error getting atom locale
924705623372 April 21, 1999 10:40:23 AM CfgChangeProbe localhost Error EDSSY0012:    Unable to connect to EDS 
924705623423 April 21, 1999 10:40:23 AM CfgChangeProbe localhost Error EDSSY0012:    Unable to connect to EDS 
...
---------- 

Reason

CORBA-based applications fail on Solaris because of Solaris bug #4185755.

Java Development Kit (JDK) bug #4163652/4073539 describes how java.net.InetAddress.getLocalHost() in JDK releases earlier than 1.2.2 returns the first line in /etc/hosts instead of the correct host under these circumstances:

  • When nscd (name service) does not run

  • If files is the first source for hosts in /etc/nsswitch.conf (see workaround step 2).

In many cases, localhost is the first entry under /etc/hosts, and is returned as the result of InetAddress.getLocalHost. This causes CORBA services such as GateKeeper to receive traffic directed to the localhost (loopback address). It fails because the client application uses the Domain Name System (DNS) primary IP address to connect to the server.

Workaround

To avoid Solaris failures, take these steps:

  1. Make sure the first entry in /etc/hosts is the hostname of the machine (not localhost).

    Example:

         =======================
         # 
         # Internet host table 
         # 
         100.1.1.1 fred.cisco.com 
         127.0.0.1 localhost loghost 
         ... ... ... 
         ======================= 
  2. Make sure the /etc/nsswitch.conf file specifies the word files before dns.

    Example:

         ======================= 
         # 
         # /etc/nsswitch.files: 
         # 
         # An example file that could be copied over to /etc/nsswitch.conf; it 
         # does not use any naming service. 
         # 
         # "hosts:" and "services:" in this file are used only if the 
         # /etc/netconfig file has a "-" for nametoaddr_libs of "inet" transports. 
         passwd: files 
         group: files 
         hosts: files dns 
         networks: files 
         protocols: files 
         ... ... ... 
         ======================= 

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: Jan 10, 2006Document ID: 7101