> Web Element Manager Overview
> The Web Element Manager (WEM) is a Common Object Request Broker Architecture (CORBA)-based application that provides complete Fault, Configuration, Accounting, Performance, and Security (FCAPS) capability for the system under management.
> For maximum flexibility and scalability, the WEM application implements a client-server architecture. This architecture allows remote clients with Java-enabled web browsers to manage one or more systems via the server component which implements the CORBA interfaces. The server component is fully compatible with the fault-tolerant Sun® Solaris® and Cisco MITG Red Hat Enterprise Linux operating systems. For added security, management traffic can be encrypted using the Secure Sockets Layer (SSL) protocol, as shown in the following diagram:
> Supported Features
> FCAPS Support
> The Web Element Manager application provides Fault, Configuration, Accounting, Performance and Security (FCAPS) management functionality for the ASR 5000.
> Fault Management
> Fault management consists of an event logging function wherein all alarms, warnings, and other faults can be configured, reported, and acknowledged by network operations personnel.
> The Simple Network Management Protocol (SNMP) is used by both the Web Element Manager and the chassis to report event notifications. The application’s fault management system offers the following support for generated alarms:

> • | Provide mechanisms for viewing both current and pending alarms for both the chassis and the Web Element Manager server.

> • | Generate audio and visual alerts for alarms based on their severity (the Web Element Manager also supports the configuration of a severity level for each alarm).

> • | Maintain statistics for generated alarms.

> • | Store alarm information in the PostgreSQL® database.

> • | Execute scripts through the Script Server component of the application.

> • | Send E-mail notifications and/or forward notifications to Network Management Servers (NMSs) using a CORBA/IIOP-based Northbound Interface.

> • | Compliancy with the following standards:

> • | TS 32.111-3, 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; Fault Management; Part 3: Alarm Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS)

> • | TS 32.303, 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS)

> Configuration Management
> The Web Element Manager implements an easy to use, point-and-click GUI for providing configuration management for one or more systems. This GUI provides all the flexibility offered by the system’s command Line Interface (CLI), while providing the scalability of performing certain functions across multiple chassis. All configuration information is stored in the PostgreSQL Database.
> At the system-level, the Web Element Manager application provides support for the following:

> • | Adding, modifying, or deleting systems to/from the management system

> • | Performing configuration of card and port-level parameters

> • | Adding, modifying, or deleting contexts

> • | Configuring specific protocols and services within defined contexts such as AAA servers, PDSN services, GGSN services, IP access lists, IP interfaces, IP routes, IP address pools, RADIUS accounting and authentication, PPP, subscribers, and others

> At the network level, the application is capable of transferring configuration and/or software images to multiple systems simultaneously in advance to performing software upgrades.
> The Web Element Manager supports the configuration of all parameters required to perform software upgrades including:

> • | Adding, deleting, and sorting system boot stack entries; these entries allow multiple fall-backs in the event the system experiences an error in the loading of a particular image or configuration file

> • | Configuring network options for bootup

> • | Transferring configuration and image files to/from a chassis

> • | Initiating and monitoring upgrade status

> The Web Element Manager further simplifies the software upgrade process by providing tools for managing system configuration files:

> • | Back-up Tool: Enables the Web Element Manager to transfer a copy of the configuration file currently being used by a managed system at user-defined intervals. Files are transferred to the host server in a specific directory. The number of files to retain in the directory is also configurable. This tool provides a useful mechanism for testing configurations and/or quickly restoring a last-known-good configuration in the event of an error.

> • | Compare Tool: Provides a powerful tool for comparing the configuration files of two managed systems. Once the two files are specified, a dialog appears displaying the two documents side-by-side. Line numbers are added for convenience. Text additions, modifications, and deletions are displayed in different colors for easy recognition. This tool can be useful on its own to determine variations between multiple iterations of the same configuration file, or, when used in conjunction with the Back-up tool, it can provide an audit trail of configuration changes that occurred during system operation.

> Configuration Audit Tool
> WEM Configuration Audit Tool allows users to monitor specified configuration attributes on a selected system or systems. This can be useful in monitoring configuration changes and problems while performing operation and maintenance tasks.
> To effectively use this feature, the user must be familiar how to build queries and interpret query output from the Command Line Interface (CLI). With the Configuration Audit Tool users can:

> • | Schedule custom periodic configuration audits or execute an on demand configuration audit.

> • | Configure report distribution parameters that allow the user to notify various groups of individuals that a report is available.

> • | Have the results of a configuration audit automatically distributed via email to specified individuals or view report results directly via WEM.

> • | Create custom configuration attribute groups to be used for auditing a specified system.

> Online Help is available from the following pages:

> • | Configuration Audit Query Information

> • | Configuration Audit Schedule

> • | On Demand Configuration Audit

> • | Configuration Audit Results

> Accounting Management
> Accounting management operations allow users to examine and perform post-process statistical analysis on systems managed by the Web Element Manager application.
> The type of statistics used for element management-based accounting are called bulk statistics. Bulk statistics are grouped into categories called schemas and are polled by the system at fixed polling intervals and then transferred to the Web Element Manager at a different transfer intervals (defined in minutes).
> Once the Web Element Manager server application, called the receiver, has received bulk statistics files from the managed system, these files are parsed and added to the PostgreSQL database. This database is updated as new files are received.
> The Web Element Manager’s accounting management functionality is compliant with TS 32.401, 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; Performance Management (PM); Concept and requirements and allows you to:

> • | Collect statistics pertaining to the transfer and collection of bulk statistics

> • | Views statistics stored on the chassis prior to transfer to the receiver

> • | Graph multiple received bulk statistics over time as either a line or bar graph; these graphs can be printed to network printers accessible by the server

> • | Generate eXtensible Markup Language (XML) files for transfer to a Northbound NMS or bulk statistics processor.

> • | Archive collected bulk statistic information to conserve disk space on the server

> Performance Management
> Performance management operations supported by the Web Element Manager allow users to examine and perform real-time statistical analysis on systems managed by the application as well as on the server on which the application is running.
> Information pertaining to various aspects of the Web Element Manager (CPU and memory utilization, disk space, and process status) and its managed systems (hardware, protocols, software subsystems, and subscribers) is collected in real time and is displayed in tabular format. Alternatively, most of the information can be graphed as a function of time in either line or bar-chart format. Multiple statistics can be graphed simultaneously for quick comparison of data.
> In addition to collecting and providing mechanisms for the real-time viewing of statistical information, the Web Element Manager provides useful monitoring tools similar to those found in the CLI. These tools can be used to monitor active subscriber sessions, protocol flows, and port information. Data collected during this monitor operation can be saved to the client machine for further analysis.
> Security Management
> Security management pertains to the operations related to management users. This includes both Web Element Manager application users and local management users who are configured on the chassis. In many cases, management users can be allowed access to both the system (via its CLI) and the application. It is possible for both management user accounts to share the same username and password.
> The security management features of the Web Element Manager allow you to:

> • | Add, modify, or delete administrative users for both the application and the managed system.

> Regardless of the administrative user type, there are four levels of management user privileges:

> • | Inspector: Inspectors are limited to a small number of read-only Exec Mode commands.The bulk of these are “show” commands giving the inspector the ability to view a variety of statistics and conditions. The Inspector cannot execute show configuration commands and do not have the privilege to enter the Config Mode.

> • | Operator: Operators have read-only privileges to a larger subset of the Exec Mode commands. They can execute all commands that are part of the inspector mode, plus some system monitoring, statistic, and fault management functions. Operators do not have the ability to enter the Config Mode.

> • | Administrator: Administrators have read-write privileges and can execute any command throughout the CLI except for a few security-related commands that can only be configured by Security Administrators. Administrators can configure or modify the system and are able to execute all system commands, including those available to the Operators and Inspectors.

> • | Security Administrator: Security Administrators have read-write privileges and can execute all CLI commands including those available to Administrators, Operators, and Inspectors.

> • | Provide authentication and privilege restoration based on the login information entered by administrative users.

> • | Monitor current system or application-level administrative users in real-time and optionally terminate their management session.

> • | Perform an audit of all managed system configurations performed through both the application and the CLI as well as other operations performed within the application.

> The audit trail functionality supports the configuration of filters defining the type of operations to audit and also provides a dialog for performing the audit in real-time.
> Audit trail results are stored in the PostgreSQL database for later retrieval and analysis.
> The new Network Audit Tool functionality in WEM supports the on-demand or periodic auditing of chassis configuration attributes such as PPP MRU, Auth Sequence, Bulkstats Schema Needs Update, etc.
> Additional Features
> Additional features provided by the Web Element Manager application include:
> High Availability Redundant Server Clustering
> Beginning with Release 12.0 redundant servers can be configured using Oracle Cluster software. Much of the information in the following chapters applies equally to a cluster installation although at this time we recommend using the GUI installation method described in Installing the WEM Software. A separate appendix addresses the differences between a Standalone installation and a Failover installation and it also defines the steps required to create and configure a cluster.
> Management Integration Capabilities
> Utilizing the Object Management Group's (OMG) standard CORBA Northbound interface, the Web Element Manager application can be integrated with higher-level TMN-modeled applications such as network, business, and service layer applications. The OMG's Interface Definition Language (IDL) can be used to develop custom interfaces to various other third-party components such as Application Servers, etc.
> Database Management and Redundancy Support
> All databases used for audit trail, performance and statistical information, event management, and device inventory information will be stored on the Web Element Manager server using the UNIX file system.
> Multiple Language Support
> The Web Element Manager provides the ability for users to select a specific language the information is provided in. The currently supported languages include U.S. English and Korean.
> Context-Sensitive Help System
> The Web Element Manager has a complete web-based Help system that provides user assistance for every screen and function available within the application. This Help system resides on the Web Element Manager server and is accessible from any supported client workstation.
> Stand-alone Offline Help System
> A stand-alone version of the WEM’s online help file is provided with the WEM. This stand-alone help contains content identical to the context-sensitive help. Users can save the standalone (.chm) help file to a local drive to conduct off-line WEM-related research. The standalone help file can be downloaded from the main WEM browser page by clicking the Web Element Manager Offline Help link under Help Resources.
> Multiple OS Support
> Web Element Manager can be installed on servers running the Sun Solaris or the custom Cisco MITG Red Hat Linux Enterprise v5.5 operating systems. For detailed operating system and hardware platform requirements, refer to the Web Element Manager System Requirements section of this chapter.
> Caution: The Cisco MITG RHEL v5.5 OS is a custom image that contains only those software packages required to support compatible Cisco MITG external software applications. Users must not install any other applications on servers running the Cisco MITG v5.5 OS. For detailed software compatibility information, refer to the Cisco MITG RHEL v5.5 OS Application Note.
> Web Element Manager System Requirements
> Important: The hardware required for the Web Element Manager server may vary, depending on the operating system being used, the number of chassis being managed, the number of clients that require access, and other variables. The requirements listed in this section support up to 30 Web Element Manager clients, managing up to 25 chassis.
> Server Hardware Requirements
> This section describes the WEM server hardware requirements for both the Sun Solaris and Cisco MITG Red Hat Enterprise Linux Operating Systems.
> Sun Solaris Server Hardware Requirements
> WEM servers running the Sun Solaris operating system must be deployed on the following hardware platform:

> • | Sun Microsystems Netra™ T5220 server

> • | 1 x 1.2GHz 8 core UltraSPARC T2 processor with 32GB RAM

> • | 2 x 146GB SAS hard disk drives

> • | Quad Gigabit Ethernet interfaces

> • | Internal DVD-ROM drive

> • | AC or DC power supplies depending on the application

> Red Hat Enterprise Linux Server Hardware Requirements
> WEM servers running the Cisco MITG RHEL v5.5 operating system must be deployed on the following hardware platform:

> • | Cisco UCS C210 M2 Rack Server

> • | Intel Xeon X5675 processor with 16 GB DDR3 RAM

> • | 300GB 6Gb SAS 10K RPM SFF Hard Disk Drive

> • | Quad Gigabit Ethernet interfaces

> • | Internal DVD-ROM drive

> • | AC or DC power supplies depending on the application

> Operating System Requirements
> This section describes the Sun Solaris and Cisco MITG Red Hat Enterprise Linux (RHEL) v5.5 operating system requirements for WEM servers.
> Sun Solaris Operating System Requirements
> This section describes the required Sun Solaris OS requirements for WEM servers, including the required OS patches.
> Important: Ensure that all recommended patches are installed before performing a new installation or software upgrade.

> • | Solaris 8 with Recommended Patch Cluster dated on or after April 2006.

> Important: Users based in the United States should ensure that the timezone patch 109809-05 (or later) and libc patch 108993-52 (or later) be installed in support of extended daylight savings time (DST).

> • | Solaris 9 with Recommended Patch Cluster dated on or after April 2006

> Important: Users based in the United States should ensure that the timezone patch 113225-07 (or later) and libc patch 112874-33 (or later) be installed in support of extended daylight savings time (DST) support. In addition, if Solaris 9 is used, it must be installed using the “End User System support 64-bit” software group must be specified during the installation of the operating system. This option installs the libraries required for proper operation of the Web Element Manager.

> • | Solaris 10 with Recommended Patch Cluster dated on or after April 2011.

> Important: Users based in the United States using Solaris 10 should ensure that the timezone patch 138856-02 or later is installed in support of extended Daylight Savings Time (DST).
> Important: The following are important requirements for Solaris 10 users:
> Solaris 10 with Recommended Patch Cluster dated on or after July 16, 2007 and not later than Nov 2010. Solaris 10 Kernel patch released between 137137-09 and 142900-04 may result in kernel panic while executing/invoking system calls. We recommend kernel patch 142900-07
> Important: Do not install the kernel patch beyond 142900-07.
> Solaris 10 Kernel patch released after 142900-07 has an issue, which will result in failure while invoking WEM Monitor subscriber and Monitor protocol screens.
> Important: If you plan to install software and maintain the Web Element Manager application and server remotely, it is recommended that you use an X-Windows client.
> Red Hat Enterprise Linux Operating System Requirements
> This section describes the required Cisco MITG Red Hat Linux (RHEL) operating system (OS) requirements for WEM servers.

> • | Cisco MITG RHEL v5.5 OS

> For hardware platform requirements for the Cisco MITG RHEL v5.5 OS, refer to the Server Hardware Requirements section in this chapter. For information related to installation, refer to the Cisco MITG RHEL OS v5.5 Application Note.
> Caution: The Cisco MITG RHEL v5.5 OS is a custom image that contains only those software packages required to support compatible Cisco MITG external software applications. Users must not install any other applications on servers running the Cisco MITG v5.5 OS. For detailed software compatibility information, refer to the Cisco MITG RHEL v5.5 OS Application Note.
> Client Access Requirements

> • | Workstation supporting Solaris/Sun, Linux, UNIX, Microsoft Windows XP, Windows 2000, Windows 7 or Windows NT operating system

> • | Java Runtime Environment (JRE) version 1.5 or 1.6

> Important: It is recommended that users should use JRE 1.4.2_11 (or later) or 1.5 update 6 (or later).

> • | Java policy file (obtained during initial access to the Web Element Manager server)

> • | Microsoft Internet Explorer version 5.0 (or higher), Netscape Navigator version 4.72 (or higher), or other Internet browser

> • | Access to the Web Element Manager server's host network

> Important: Web Element Manager clients cannot access the Web Element Manager server if the server is separated by an NAT'd firewall or other device that restricts access between the client workstation and server.

> • | Configured application user account on Web Element Manager server

> WEM Architecture
> The WEM architecture consists of the following components:

> • | Host Filesystem

> • | Apache Web Server

> • | WEM Server FCAPS Support

> • | WEM Process Monitor

> • | Bulk Statistics Server

> • | Script Server

> • | PostgreSQL Database Server

> • | Northbound Server

> • | WEM Logger

> Host Filesystem
> Running on the fault-tolerant Sun Solaris or Red Hat Enterprise Linux operating system, the WEM uses the native filesystem for such things as creating and writing to log files, storing alarm and bulk statistic-related information, and configuration file management.
> Apache Web Server
> Remote clients interface with the WEM by establishing session with the server using the Hyper Text Transport Protocol (HTTP). The session is hosted by the Apache Web Server which launches a Java applet providing a graphical user interface for managing the system. When HTTPS is mentioned in the URL instead of HTTP, secure connection is established between the WEM client and WEM server. The Apache Web Server is also used to execute Common Gateway Interfaces (CGIs) invoked by the applet using CORBA/Internet Inter-ORB Protocol (IIOP).
> WEM Server FCAPS Support
> This component provides Fault, Configuration, Accounting, Performance, and Security (FCAPS) functionality.
> Important: The Admin can make any menu or submenu item visible or not visible to users as he sees fit. To show or hide a particular menu option, set the flag in the menu.xml file as described in the Configuration File Parameters chapter of this guide. Please note that it is not possible to actually delete or add a menu or submenu.
> Fault Management
> Fault management consists of an event logging function wherein all alarms, warnings, and other faults can be configured, reported, and acknowledged by network operations personnel.
> The Simple Network Management Protocol (SNMP) is used by both the Web Element Manager and the ASR 5000 to report event notifications. The application’s fault management system offers the following support for generated alarms:

> • | Provide mechanisms for viewing both current and pending alarms for both the chassis and the Web Element Manager server.

> • | Generate audio and visual alerts for alarms based on their severity (the Web Element Manager also supports the configuration of a severity level for each alarm).

> • | Maintain statistics for generated alarms.

> • | Store alarm information in the PostgreSQL® database.

> • | Execute scripts through the Script Server component of the application.

> • | Send E-mail notifications and/or forward notifications to Network Management Servers (NMSs) using a CORBA/IIOP-based Northbound Interface.

> • | Compliance with the following standards:

> • | TS 32.111-3, 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; Fault Management; Part 3: Alarm Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS)

> • | TS 32.303, 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS).

> Configuration Management
> The Web Element Manager implements an easy to use, point-and-click GUI for providing configuration management for one or more systems. This GUI provides all the flexibility offered by the system’s command Line Interface (CLI), while providing the scalability of performing certain functions across multiple systems. All configuration information is stored in the PostgreSQL Database.
> At the system-level, the Web Element Manager application provides support for the following:

> • | Adding, modifying, or deleting systems to/from the management system

> • | Performing configuration of card and port-level parameters

> • | Adding, modifying, or deleting contexts

> • | Configuring specific protocols and services within defined contexts such as AAA servers, PDSN services, GGSN services, IP access lists, IP interfaces, IP routes, IP address pools, RADIUS accounting and authentication, PPP, subscribers, and others

> At the network level, the application is capable of transferring configuration and/or software images to multiple systems simultaneously in advance to performing software upgrades.
> The Web Element Manager supports the configuration of all parameters required to perform software upgrades including:

> • | Adding, deleting, and sorting system boot stack entries; these entries allow multiple fall-backs in the event the system experiences an error in the loading of a particular image or configuration file.

> • | Configuring network options for bootup.

> • | Transferring configuration and image files to/from systems.

> • | Initiating and monitoring upgrade status.

> The Web Element Manager further simplifies the software upgrade process by providing tools for managing system configuration files:

> • | Back-up Tool: Enables the Web Element Manager to transfer a copy of the configuration file currently being used by a managed system at user-defined intervals. Files are transferred to the host server in a specific directory. The number of files to retain in the directory is also configurable. This tool provides a useful mechanism for testing configurations and/or quickly restoring a last-known-good configuration in the event of an error.

> • | Compare Tool: Provides a powerful tool for comparing the configuration files of two managed systems. Once the two files are specified, a dialog appears displaying the two documents side-by-side. Line numbers are added for convenience. Text additions, modifications, and deletions are displayed in different colors for easy recognition. This tool can be useful on its own to determine variations between multiple iterations of the same configuration file, or, when used in conjunction with the Back-up tool, it can provide an audit trail of configuration changes that occurred during system operation.

> Accounting Management
> Accounting management operations allow users to examine and perform post-process statistical analysis on systems managed by the Web Element Manager application.
> The type of statistics used for element management-based accounting are called bulk statistics. Bulk statistics are grouped into categories called schemas and are polled by the system at fixed polling intervals and then transferred to the Web Element Manager at a different transfer intervals (defined in minutes).
> Once the Web Element Manager server application, called the receiver, has received bulk statistics files from the managed system, these files are parsed and added to the PostgreSQL database. This database is updated as new files are received.
> The Web Element Manager’s accounting management functionality is compliant with TS 32.401, 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; Performance Management (PM); Concept and requirements and allows you to:

> • | Collect statistics pertaining to the transfer and collection of bulk statistics.

> • | Views statistics stored on the ASR 5000 prior to transfer to the receiver.

> • | Graph multiple received bulk statistics over time as either a line or bar graph; these graphs can be printed to network printers accessible by the server.

> • | Generate eXtensible Markup Language (XML) files for transfer to a Northbound NMS or bulk statistics processor.

> • | Archive collected bulk statistic information to conserve disk space on the server.

> Performance Management
> Performance management operations supported by the Web Element Manager allow users to examine and perform real-time statistical analysis on systems managed by the application as well as on the server on which the application is running.
> Information pertaining to various aspects of the Web Element Manager (CPU and memory utilization, disk space, and process status) and its managed systems (hardware, protocols, software subsystems, and subscribers) is collected in real time and is displayed in tabular format. Alternatively, most of the information can be graphed as a function of time in either line or bar-chart format. Multiple statistics can be graphed simultaneously for quick comparison of data.
> In addition to collecting and providing mechanisms for the real-time viewing of statistical information, the Web Element Manager provides useful monitoring tools similar to those found in the CLI. These tools can be used to monitor active subscriber sessions, protocol flows, and port information. Data collected during this monitor operation can be saved to the client machine for further analysis.
> Security Management
> Security management pertains to the operations related to management users. This includes both Web Element Manager application users and local management users who are configured on the chassis. In many cases, management users can be allowed access to both the system (via its CLI) and the application. It is possible for both management user accounts to share the same username and password.
> While it is possible to authenticate users via RADIUS server configuration, each RADIUS server has its own configuration that is outside the scope of this document. However, you can find the mapping information you would need to configure each of the four levels of administrative user in the “CLI Administrative Users” section of the CLI Overview chapter in the Command Line Interface Reference.
> The security management features of the Web Element Manager allow you to:

> • | Add, modify, or delete administrative users for both the application and the managed system.

> • | Regardless of the administrative user type, there are four levels of management user privileges:

> • | Inspector: Inspectors are limited to a small number of read-only Exec Mode commands.The bulk of these are “show” commands giving the inspector the ability to view a variety of statistics and conditions. The Inspector cannot execute show configuration commands and do not have the privilege to enter the Config Mode.

> • | Operator: Operators have read-only privileges to a larger subset of the Exec Mode commands. They can execute all commands that are part of the inspector mode, plus some system monitoring, statistic, and fault management functions. Operators do not have the ability to enter the Config Mode.

> • | Administrator: Administrators have read-write privileges and can execute any command throughout the CLI except for a few security-related commands that can only be configured by Security Administrators. Administrators can configure or modify the system and are able to execute all system commands, including those available to the Operators and Inspectors.

> • | Security Administrator: Security Administrators have read-write privileges and can execute all CLI commands including those available to Administrators, Operators, and Inspectors.

> • | Provide authentication and privilege restoration based on the login information entered by administrative users.

> • | Monitor current system or application-level administrative users in real-time and optionally terminate their management session.

> • | Perform an audit of all managed system configurations performed through both the application and the CLI as well as other operations performed within the application.

> The audit trail functionality supports the configuration of filters defining the type of operations to audit and also provides a dialog for performing the audit in real-time.
> Audit trail results are stored in the PostgreSQL database for later retrieval and analysis.
> The new Network Audit Tool functionality in WEM supports the on-demand or periodic auditing of chassis configuration attributes such as PPP MRU, Auth Sequence, Bulkstats Schema Needs Update, etc.
> ANSI T1.276 Compliance
> The WEM supports ANSI standard T1.276, providing a set of baseline security features to help mitigate security risks in the management of telecommunication networks. New users will be sent a randomly generated password automatically, and will be prompted to provide a new password upon first login. New passwords must meet strict requirements to comply with the ANSI standard:

> • | Passwords must be a minimum of eight characters long.

> • | Passwords must not be a repeat or the reverse of the associated user ID.

> • | Passwords must not be more than three of the same characters used consecutively.

> • | Passwords must contain at least three of the following character types:

> • | At least one lower case alpha character

> • | At least one upper case alpha character

> • | At least one numeric character

> • | At least one special character

> Users will also be required to change passwords after a configurable number of days, and will be barred from reusing the same password for a configurable number of password change cycles. Too many failed login attempts will result in an account lockout, which may be removed either by an administrator or by waiting for a defined period of time to elapse.
> WEM Process Monitor
> The Process Monitor (PSMon) is a Perl script that monitors the status of processes pertaining to the WEM application.
> The script is a plain text Apache-style configuration file that allows the user to define a set of rules. These rules describe what processes should always be running on the system, any limitations on concurrent instances, Time-To-Live (TTL), and maximum CPU/memory usage of processes. It can be run as a stand alone program or a fully functional background daemon.
> PSMon scans the UNIX process table and, using the set of defined rules, will re-spawn any dead processes, and/or slay or “deal with” any aggressive or illegal processes. The number of retries and time interval the PSMon scans the table is configurable meaning that it will never try to start the process if 'number of retries' exceeds in given time interval.
> PSMon logs events to syslog and to a log file and is equipped with customizable e-mail notification facilities.
> Bulk Statistics Server
> The Bulk Statistics Server process is responsible for collecting and processing all bulk statistic-related information from the system as part of the WEM’s accounting management functionality.
> The Bulk Statistics Server parses collected statistics and stores the information in the PostgreSQL database. If XML file generation and transfer is required, this element generates the XML output and can send it to a Northbound NMS or an alternate bulk statistics server for further processing.
> Additionally, if archiving of the collected statistics is desired, the Bulk Statistics server writes the files to an alternative directory on the server. A specific directory can be configured by the administrative user or the default directory can be used. Regardless, the directory can be on a local filesystem or on an NFS-mounted filesystem on the WEM server.
> Script Server
> The WEM supports the ability to configure the properties for alarms. One of the properties that can be configured is specifying a script that can be executed upon receipt of that alarm. The Script Server process is responsible for executing the specified script.
> Upon receipt of the alarm, the WEM Server FCAPS Support function passes the name of the script to execute and the trap logged time to the Script Server. An acknowledgement is sent and the script is executed by the Script Server. In the event, an error is experienced while executing the script, the Script Server generates an SNMP trap.
> PostgreSQL Database Server
> The PostgreSQL Database consists of multiple databases maintaining information pertaining to the following WEM functions:

> • | Configuration: This database contains tables which maintain configuration information for user details, topology for maps and manageable systems.

> • | Trap: This database contains tables which maintain SNMP trap configuration information and all the received SNMP traps.

> • | MIB: This database contains all the information required to translate SNMP Object identifiers to proper MIB names and their types as given in the MIB file.

> • | Audit Trail: This database contains table that maintains the configuration trail including the following:

> • | Configuration performed on each system through the WEM

> • | Configuration done through the system’s CLI (this is known via the CORBA notification service)

> • | Login/out from the WEM and system CLI

> • | The addition/deletion of a new system in the managed system list

> • | Bulk Statistics: This database contains various tables containing counter values periodically received from the system via the File Transfer Protocol (FTP).

> Northbound Server
> The Northbound Server process is responsible for collecting and transmitting information about WEM system management to an NMS.
> WEM supports the Northbound Interface as defined in the 3GPP standards for Telecom Management. 3GPP defines a standard interface (Interface-N) between the EMS and the NMS. It also defines Integration Reference Points (IRPs) through which various aspects of system management (FCAPS) are performed by the NMS.
> When the Northbound Server process is enabled, WEM will respond to NMS requests by fetching the required information and transmitting it over the CORBA interface.
> Northbound Server is a separately licensed feature.
> Currently, WEM supports five IRPs defined by the 3GPP standards. The supported IRPs and corresponding 3GPP standards are:

> • | Alarm: 3GPP TS 32.111-3 (V6.6.0)

> • | Basic CM: 3GPP TS 32.603 (V6.4.0)

> • | Notification: 3GPP TS 32.303 (V6.6.0)

> • | Communication Surveillance: 3GPP TS 32.353 (V6.4.0)

> • | Entry Point: 3GPP 32.363 (V6.4.0)

> The supported Network Resource Model is:

> • | Generic Network Resource (NRM) IRP: 3GPP TS 32.623 (v6.50)

> The following table lists the Northbound Interface operations and notifications that are supported for each of the IRPs:

> IRP Category | Notification/Operation Description
> Alarm | Notifications | notifyNewAlarm
> notifyAckStateChanged
> notifyClearedAlarm
> notifyAlarmListRebuilt
> Operations | get_alarm_irp_versions
> clear_alarms
> get_alarm_list
> next_alarmInformations
> get_alarm_count
> acknowledge_alarms
> unacknowledge_alarms
> Basic CM | Notifications | Not Applicable
> Operations | get_basic_cm_irp_version
> find_managed_objects
> next_basicCmInformations
> Notification | Notifications | not applicable
> Operations | get_notification_irp_versions
> attach_push
> change_subscription_filter
> get_subscription_status
> get_subscription_ids
> detach
> Communication Surveillance | Notifications | notifyHeartbeat
> Operations | get_CS_IRP_versions
> get_heartbeat_period
> set_heartbeat_period
> trigger_heartbeat
> Entry Point | Notifications | Not Applicable
> Operations | get_EP_IRP_versions
> get_IRP_outline
> get_IRP_reference
> release_IRP_reference

> ‌
> WEM Logger
> The WEM application generates and stores logs pertaining to server installation and operation. The logs can be stored locally or to another server. In addition, the WEM provides enhanced logging functionality for customizing log output and log files.

Cisco Systems Inc.
Tel: 408-526-4000
Fax: 408-527-0883