If log contains an entry of the form: ERROR [org.jboss.naming.NamingService] Starting failed jboss:service=Naming java.rmi.server.ExportException: Port already in use: 1098; nested exception is: java.net.BindException: Address already in use: JVM_Bind

Use netstat to determine what process is connecting to the 1098 port.

Then either:

• Disable the conflicting process.
• Change the JBoss RmiPort property of the "Naming" service(in the jboss-service.xml file) to a different value.

http://wiki.jboss.org/wiki/Wiki.jsp?page=UsingJBossBehindAFirewall

 

netPrefect™ Engine

The following ports should be opened:

• 8443:tcp (for HTTPs)
• 8193:tcp (for JMS)
• 1098:tcp and 1099:tcp (for the JBoss Naming Service)

(see http://wiki.jboss.org/wiki/Wiki.jsp?page=UsingJBossBehindAFirewall)

netPrefect™ Server Manager

This depends on the Server Manager Machine configuration Remote Service Port and Console Server Port settings. For the defaults you will need to open:

• 8200:tcp (for Remote Services)
• 8199:tcp (for the Console Server)

 

This is a problem with Java 5.0's InetAddress isReachable method. It will be fixed in Java 6.0. There is currently no workaround for this issue. We would recommend that customers don't run auto discovery on a Windows platform with the network cable unplugged.

 

It is likely that the SNMP Agent on the remote device is not configured with the required MIB.
For example, a GET of the "memoryAvailableBytes" OID from the WINDOWS-NT-PERFORMANCE MIB will return

memoryAvailableBytes|1.3.6.1.4.1.311.1.1.3.1.1.1.1.0|No such object

if the MIB has not been installed on the target Windows machine.
Refer to the SNMP section in the Administration Guide for instructions on configuring SNMP Agents.

 

This is because some Linux distributions return 127.0.0.1 as the location of a resource, located on the server. The client then tries to access the resource locally, resulting in the exception.

Either:

Update the /etc/hosts file on the machine running netPrefect™ Engine, replacing the line of the form:

127.0.0.1 machinename.hostnetwork machinename localhost.localdomain localhost

with the following line:

127.0.0.1 localhost.localdomain localhost

Or

Add the following line to /usr/local/jboss/bin/run.conf file:

JAVA_OPTS="$JAVA_OPTS -Djava.rmi.server.hostname=`ifconfig eth0|grep 'inet addr:' | sed 's/inet addr://' | awk '{print $1}'`"

 

Where the Managed Resource does not use strings as its normal output mechanism (such as in the case of SNMP), the output is converted to human readable strings before any processing or logging is performed.

Special hardware is needed to convert the protocol of the AS/400 system console, to allow either TCP/IP Telnet access or RS232 Serial access.

IBM document the product as follows, but its use with netPrefect™ has yet to be proven:

"A Client Access/400 Console Adapter and Client Access/400 software, which allow a PC to be used at the System Console. Attachment is via an asynchronous communication line from the model 150 e-server to the serial port on the PC, utilising the Console Attachment Cables."

The hardware that netPrefect™ requires, in order to connect to a Managed Resource , is largely dependent on the type of transport chosen to connect to the managed Managed Resource. Each transport description below outlines any special hardware required, in order to complete a connection to netPrefect™.

There are two basic ways to connect a system with a serial console port to the netPrefect™ Server:

1. Direct - Connect the serial console port to a "COM" port on the netPrefect™ server.
2. Via a network connection, such as a terminal server (or network accessible COM port server) - connect the serial console port to a the server serial port, and then connect this server to the netPrefect™ Server, via the LAN or WAN.

Which one you choose will depend on a number of factors:

• Distance from the system to the netPrefect™ Server.
• Requirement to avoid using the network.
• The number of COM ports directly available to your netPrefect™ Server limits the number of consoles that can be managed.