Cisco Subscriber Edge Services Manager Troubleshooting Guide 3.3
Introduction to SESM Solutions
Downloads: This chapterpdf (PDF - 158.0KB) | Feedback

Introduction to SESM Solutions

Table Of Contents

Introduction to SESM Solutions

SESM Installation Images

Subscriber and Service Profiles

SESM Application Management


Introduction to SESM Solutions


This chapter provides introductory information about the Cisco Subscriber Edge Services Manager (SESM) solution. Topics are:

SESM Installation Images

Subscriber and Service Profiles

SESM Application Management

SESM Installation Images

The installation images for SESM are available from the product CD-ROM or from the Cisco web site. SESM images are available for the Sun Solaris 8, Linux Red Hat ES 3.0, and Windows 2000 platforms.

The names of the compressed and executable installation files and the procedures for obtaining the installation images are detailed in the Cisco Subscriber Edge Services Manager Installation Guide.

Subscriber and Service Profiles

SESM solutions require detailed data about subscribers and the services they are authorized to use. We refer to this data as profiles:

Subscriber profiles—Define authentication information, subscribed services, and information about connection and service options and preferences for each subscriber.

Service profiles—Define Connection information for the services that subscribers can subscribe and connect to.

The SESM solution integrates with any one or a combination of the following options to obtain subscriber and service data:

An AAA database managed and accessed by a RADIUS server.

An SPE database (an LDAP directory) accessed through the Cisco SPE application programming interface (API). In SESM deployments, the Cisco Distributed Administration Tool (CDAT) manages the subscriber and service profiles in the database.

A flat file in Merit format, accessed by a SESM portal running as a Demo installation.

SESM Application Management

SESM uses the Java Management Extensions (JMX) specification and its related JMX MBean standards for application configuration. For descriptions of these standards, refer the sun website.http://java.sun.com/products/JavaManagement


A brief introduction to JMX terminology and its relationship to SESM application management follows:

JMX manageable resources—Java objects instrumented to allow spontaneous management by any JMX compliant agent. Each SESM application contains JMX manageable resources.

JMX agent— A management entity implemented in accordance with the JMX Agent Specification. For SESM, the agent is the Cisco ConfigAgent.

Managed beans (MBeans)—Java objects that represent a JMX manageable resource. MBeans for each SESM application are specified in XML files installed in the application's config directory under the SESM installation directory.

JMX server (also called the MBean server)—A registry for objects that are exposed to management operations by an agent. Any object that is registered with the JMX server becomes visible to the agent. In SESM applications, MBeans are registered by the ConfigAgent or by other MBeans.

Administrators can change SESM application configuration by changing the attribute values in MBeans. In this release of SESM, use any of these ways to change MBean attribute values:

Use the Application Manager, a web-based GUI tool. This is the preferred way to manage running SESM applications. The tool includes:

Operational scenarios that present the most-used attributes for quick access and adjustments.

Advanced screens that present all attributes.

A bulk upload feature for importing large mappings of subscriber subnets to SSGs.

Manually edit the XML files associated with the application. XML files are located in the application's config directory (for example, nwsp/config/nwsp.xml). If you use this method, you must stop and restart the application unless you modified WhiteList or Location Mbean for which you have configured file polling for the changes to take effect.

Use the SESM Agent View, a web-based view of managed resources and associated MBeans. The Agent View is an adaptation of the Management Console provided by the HTML adaptor server, which is included with the Sun example JMX server. The Cisco adaptations add persistence features to the server.


Note The Application Manager replaces the SESM Agent View. The Agent View is included in this release of SESM to provide convenience and continuity during migrations from previous releases.