Table Of Contents

SESM Troubleshooting Aids

Turning On Installation Logging

Verifying Basic Configurations and Connections

Verifying Operating System Patch Levels

Verifying Successful Installation and Linking of the JVM

Verifying Basic SSG Configuration

Verifying Connection Access Among SESM Components

Using Java Command Line Options

Using Run Time Logging and Debugging Features

Log File Descriptions

Log File Configuration

Isolating a Problem Area

SESM Troubleshooting Aids

---

This chapter describes tools and procedures to use to diagnose and isolate SESM installation and configuration problems. It includes the following topics:

•Turning On Installation Logging

•Verifying Basic Configurations and Connections

•Using Java Command Line Options

•Using Run Time Logging and Debugging Features

•Isolating a Problem Area

Turning On Installation Logging

The log option on the installation command line turns on the installation logging feature.

•On Solaris, the following command runs the GUI mode installation and turns on logging:

solaris> sesm_sol.bin -log [#] @ALL

Where:

# sends logging messages to a file named log.txt. If the # is omitted, messages appear on the console

@ALL indicates to log all messages, which is the recommended procedure

•On Windows NT, the following command runs the GUI mode installation and turns on logging:

C:\> sesm_win.exe -options -log [#] @ALL

Where:

# sends logging messages to a file named log.txt in the SESM installation directory. If the # is omitted, messages appear on the console.

@ALL indicates to log all messages, which is the recommended procedure.

Verifying Basic Configurations and Connections

Use the suggestions in this section to verify basic deployment conditions. Topics are:

•Verifying Operating System Patch Levels

•Verifying Successful Installation and Linking of the JVM

•Verifying Basic SSG Configuration

•Verifying Connection Access Among SESM Components

Verifying Operating System Patch Levels

To display Solaris hardware platform type and operating system versions, enter:

uname -a

prtdiag -v

To determine which patches are installed on the system, examine the following directory:

/var/sadm/patches

To determine if there are any new patches and to download the new patches or patch clusters, go to:

http://sunsolve.sun.com/

To display Windows hardware platform type and operating system versions, choose:

Start > Programs > Accessories > System Tools > System Information

Verifying Successful Installation and Linking of the JVM

---

Note For SESM Release 3.1(9), JVM Version 1.3.1 or later is required. Using the latest available version in the 1.3.1 series is recommended. The SESM applications do not start with JVM versions earlier than Version 1.3.1x.

---

To verify the successful installation and linking of the JVM, execute the following command at the command line:

java -version 

The result should be similar to the following:

java version "1.3.1_04"

Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1_04-b02)

Java HotSpot(TM) Client VM (build 1.3.1_04-b02, mixed mode)

If it is not, or if it displays a version that you did not expect:

1. Check if there is a $JDK_HOME environment variable setting on the system. If there is, make sure it points to a valid JVM. Change the value if it does not point to the JVM you want to use.

2. If there is not a $JDK_HOME environment variable, check the setting of the $JDK_HOME variable in the SESM generic start script. Make sure it points to a valid JVM.

3. On Solaris or Linux platforms, check that /usr/java is linked to the JVM that you want to use. If not, make the link as follows:

ln -s /yourJVMdirectory/bin/java /usr/java

On Windows platforms, Java installations make the adjustments that point to the most recently installed version whenever you execute a Java command.

4. Check the PATH environment variable settings to ensure that the user ID you used to log on to the system is configured to access the setting of $JDK_HOME either in the in the SESM start script or the environment variable.

On any of the installation platforms, you can specify the location of a pre-installed JRE or JDK by starting the installation process on a command line and specifying the javahome parameter, as follows:

installImageName -is:javahome location 

Where:

installImageName is the name of the SESM downloaded image.

location is the path name for the JRE or JDK.

Verifying Basic SSG Configuration

This section describes how to verify basic connectivity between SSG and a SESM web portal. To perform these verifications, use the following command on the SSG platform:

show run

Examine the output for the following:

1. Verify that the SSG feature is enabled on the Cisco network device. Examine the output from the show run command for the following line:

ssg enabled

2. Verify that the Cisco IOS release running on the platform contains the features you are intending to implement. Examine the beginning of the show run output for the version information:

version 12.x.x.x

Check the Release Notes for the Cisco Subscriber Edge Services Manager, Release 3.1(9) for feature compatibility information between SESM releases and Cisco IOS SSG releases.

3. Verify that the SSG default network includes the system on which your SESM web applications are installed. Otherwise, client requests never reach the SESM application, and the client browser eventually times out. To display the default network setting, examine the output from the show run command for the following line:

ssg default-network ipAddress mask

Verifying Connection Access Among SESM Components

Verify that the systems that are hosts to the SESM components have connection access to other components in your deployment by pinging the components. Issue pings from the SESM application system to the following systems:

•SSG platform

•RADIUS server system

•SPE database system (if used in your deployment)

For example, issue the following commands from the SESM server:

ping ssg

ping radiusserver

Where radiusserver and ssg are the DNS names or IP addresses of the RADIUS server and SSG. If any of the pings fail, check the configuration attributes in the application MBeans to ensure that the IP addresses or host names in the MBean attributes are accurate.

Using Java Command Line Options

The SESM application startup scripts execute the java command. You can specify any Java command line option when you run the SESM application startup scripts.

To specify Java options, use -jvm as an option on the startup script command line. For example, you might add the following to the command line when you execute SESM application startup scripts:

-jvm -Djava.compiler=NONE

Using Run Time Logging and Debugging Features

The SESM log files can help troubleshoot SESM applications and deployments. By changing the configuration of the logging and debugging mechanisms, you can change the amount of detail reported and specify message filtering. Two of the log files have debugging mechanisms in addition to the logging features.

All SESM applications use the same logging and debugging features. However, the settings for these features are configured individually for each application.

Log File Descriptions

The log files associated with SESM applications are:

•Jetty HTTP Request log—Contains incoming HTTP requests. You can use this log file to analyze volume and traffic patterns for the web server.

•Jetty log—Contains logging and debugging messages from Jetty. The logging messages record the startup of the Jetty server and all ongoing activity, such as errors trapped by the Jetty server and HTTP errors. If the SESM application fails to start, look at this log. Make sure you monitor this log file for illegal HTTP requests that might indicate attempts to subvert the web server. If you enable debugging, the log file also includes more detailed debugging messages.

•Application log—Contains logging and debugging messages from the SESM application. The logging tool logs SESM web application activity. The debugging mechanism produces messages useful to developers in debugging applications.

You can configure all three of these logs for each SESM portal application and for CDAT. RDP uses only the application log.

Log File Configuration

The installed default configuration places all log files for an application into the logs subdirectory under the application home directory. For example:

SESMinstallDir

nwsp

logs

If the logs directory does not exist, it is created at application runtime.

Table 2-1 shows the MBeans that configure the log files, including the level of verbosity in the logs, message filtering, debugging, file location, and file management.

Table 2-1 Configuring the Log Files

Log Type	MBean Name	Filename Attribute	Default Log Filename
Request log	Server MBean	RequestLog	date.request.log
Jetty log	Log MBean Debug MBean	filename	date.jetty.log
Application log	Logger MBean	logFile	date.application.log

For explanations of the attributes in these MBeans, see the "Logging and Debugging in SESM Applications" chapter in the Cisco Subscriber Edge Services Manager Application Management Guide. To change values of the logging attributes, use the SESM Application Manager. The Application Manager includes an operational scenario for Logging.

Isolating a Problem Area

This section shows procedures for analyzing and isolating the causes of problems in SESM deployments. The section includes two procedures:

•Identifying the Problem Area in SESM Web Portals (Figure 2-1)

•Identifying the Problem Area in RDP (Figure 2-2)

Figure 2-1 Identifying the Problem Area in SESM Web Portals 

   

   

1	See Using Run Time Logging and Debugging Features.
2	See the chapter "Basic SSG Configuration" in the Cisco Subscriber Edge Services Manager Deployment Guide.
3	See the descriptions for the SSG MBean and the AAA MBean in the Cisco Subscriber Edge Services Manager Web Portal Guide.
4	See the descriptions for the SPE MBeans (the Connection and Directory MBeans) in the Cisco Subscriber Edge Services Manager Web Portal Guide.
5	Use CDAT to make sure the subscriber is subscribed to services and has the proper privileges to access those services.
6	See Your Configuration and Log Files and Obtaining Technical Assistance.
7	See Identifying the Problem Area in RDP.

    

Figure 2-2 Identifying the Problem Area in RDP

 

    

1	See Log File Descriptions.
2	See the Cisco Subscriber Edge Services Manager RADIUS Data Proxy Guide.
3	See the Cisco Subscriber Edge Services Manager RADIUS Data Proxy Guide.
4	See the chapter "Basic SSG Configuration" in the Cisco Subscriber Edge Services Manager Deployment Guide.
5	See the "SPE MBeans" section in the Cisco Subscriber Edge Services Manager Web Portal Guide.
6	See the client and server socket components in the RDP MBean and RADIUS Data Proxy MBean, described in the Cisco Subscriber Edge Services Manager RADIUS Data Proxy Guide.
7	See Obtaining Technical Assistance.