> Installing the WEM Software
> This chapter provides the step-by-step procedure of installing WEM application using the GUI-based installation wizard and the console-based installation. Additionally it provides instuctions that need to be followed before starting the WEM installation so that it completes successfully.
> This chapter includes the following topics:
> Before You Begin
> Prior to performing the installation procedure, this section previews each step to ensure that your ready to successfully complete the installation. Detailed installation instructions follow.
> <X-Refs (online)>step <$paranum> 1 - Verifying Hardware Status
> The first thing that you need to do is to ensure that the WEM server hardware has been provisioned properly for your application. This includes:

> • | Verifying the correct operating system. This can be accomplished by entering the uname -a command.

> • | Verifying that the hard disk has been partitioned properly using the recommendations outlined in the WEM Server Hardware Sizing and Provisioning Guidelines section.

> • | Verifying network connectivity through the management LAN.

> <X-Refs (online)>step <$paranum> 2 - Setting the WEM Server's Database Environment Strings
> This step is required to configure how the PostgreSQL database engine processes, stores, and retrieves information contained in the various databases stored using the UNIX file subsystem. Failure to configure these settings may cause data loss and will minimally cause errors in the WEM's operation.
> <X-Refs (online)>step <$paranum> 3 - Unpacking the WEM Application Files
> WEM installation files are distributed as a single compressed file. Once the file is obtained, it must be copied to the server and unpacked. It is recommended that you copy the file to a temporary directory on the server.
> <X-Refs (online)>step <$paranum> 4 - Installing the WEM Software
> This step consists of choosing the desired installation method (console-based or the Graphical User Interface (GUI-based) and performing the physical installation onto the WEM server. There are three software components that are installed as part of this procedure. They are:

> • | WEM software

> • | Apache Web Server software

> • | PostgreSQL database engine software

> Important: If you are installing the WEM to upgrade an existing version that is currently installed and running, proceed to Upgrading the WEM Software chapter of this guide.
> <X-Refs (online)>step <$paranum> 5 - Configuring WEM Client Session Management Parameters
> There are numerous client session management parameters that control how many client sessions may be simultaneously accessed, idle timeout periods, and various other client-related items. This configuration file, which resides on the WEM server, should be modified (if needed) prior to starting the WEM server processes.
> Caution: Failure to perform the WEM server startup procedure in the exact order shown in this document may prevent the application from initializing and working properly.
> <X-Refs (online)>step <$paranum> 6 - Configuring IP Multipathing (IPMP) on WEM Server (Optional)
> IPMP, or IP multipathing, is a facility provided by Solaris® to provide physical interface failure detection and transparent network access failover for a system with multiple interfaces on the same IP link. IPMP also provides load spreading of packets for systems with multiple interfaces.
> For IPMP configuration, refer to the Configuring IPMP on WEM Server section.
> Important: IPMP is a feature supported on Sun® Solaris® provided by Sun Microsystems. The configuration is included in Section VI of the System Administration Guide: IP Services from Sun Microsystems. For more information, refer to the Sun documentation
> Setting the PostgreSQL Database System Environment Configurations
> Prior to installing the WEM application onto the WEM server hardware, there are numerous system environment configuration settings that should be configured. While PostgreSQL will be installed during the GUI-based installation procedure, these settings must be configured manually.
> Unpacking the Installation Files
> WEM installation files are distributed as a single compressed file with a “.tar.gz” extension.
> Once the installation file has been copied to the server, use the following procedure to unpack the file.

> Step 1 | Go to the directory in which the file is stored.

> Step 2 | Unzip the file by entering the following command:

> gunzip file_name.tar.gz
> file_name is the name of the WEM application installation file.

> Step 3 | Un-tar the file by entering the following command:

> tar -xvf file_name.tar
> Decompressing the installation file results in the following files:

> • | setup.bin: The installation binary file.

> • | inst: The executable file used to initiate the installation. This file is used for both the console- and GUI-based methods.

> • | uninst: Once the WEM application has been installed, this file must be copied to the /ems/_uninst/ diectory. It is the executable file for uninstalling the application for both the console- and GUI-based methods.

> • | file_name.tar: A compressed file containing all the application files required for both the script- and GUI-based installation methods.

> • | README: A text file containing information pertaining to the release.

> • | migrate.tar.gz: Contains the migrate script and other utilities used to perform migration of WEM from one version to another version.

> • | README_MIGRATE: A text file containing information on using the migrate script.

> Determining the Best Installation Method
> The WEM and its ancillary components such as the Apache web server and PostgreSQL database engine, may be installed in one of the following two methods.

> • | GUI-based method: This method is the most commonly used installation procedure. Requirements for using this method include:

> • | Logon account to the WEM server with display terminal (monitor) attached and some X-Windows client installed on the server.

> • | Network connectivity to WEM server via Telnet or SSH, using some X-Windows client on a remote workstation.

> • | Console-based method: This method is available to users who do not have an X-Windows client available for remote network connectivity to the WEM server via Telnet or SSH.

> Installing the WEM Software using the GUI-Based Installation Wizard
> Follow the instructions below to install the WEM using the GUI-based installation wizard.
> Important: If you are installing the WEM to upgrade an existing version that is currently installed and running, proceed to the Upgrading the WEM Software chapter of this guide.

> Step 1 | Go to the directory in which the WEM installation files are located.

> Step 2 | Execute the setup file by entering the following command:

> ./inst
> The following WEM Installer dialog appears:

> Step 3 | Click Next to proceed.

> Step 4 | Follow the on-screen prompts to progress through the various installation dialogs and configure the parameters as required. Refer to the following table for descriptions of the configurable parameters on each of the installation dialogs.

> WEM Installation Parameter Descriptions

> Parameter | Description | Default Value
> System Setting for Postgres
> | This dialog or script section is informational and contains no configurable parameters. Information pertaining to these variables is located in the Setting the PostgreSQL Database System Environment Configurations section in this chapter. | N/A
> EMS Installation Mode
> Standalone EMS | This dialog or script section determines how the installation will proceed depending on the type of environment the EMS will be running in. Important: At this time, only the Standalone EMS installation mode is available. Future releases will support a Scalable installation mode and a Failover installation mode that requires a Sun Cluster setup. | Enabled
> Destination directory for Element Management System
> Directory Name | The directory on the server in which the WEM is to be installed. The directory can be manually entered in the field provided or selected using the Browse function. | /<ems_dir>/ which is /users/ems by default
> Global Configuration
> Select the IP Address | Choose this option to select one of the server IP addresses automatically detected by the WEM installation process. For the GUI-based installation, the IP address is selected from the drop-down menu. | Null
> Enter the IP Address | Choose this option to manually specify an IP address. This option can be used to specify an address that has not yet been configured on the server The IP address must be entered in the field provided. Important: The IP address specified must be ICMP reachable. | Null
> SSL Configuration
> Enforce SSL | If this option is selected, then the Secure Sockets Layer (SSL) connection is established for client-to-server and server-to-boxer communication. By default, the SSL encryption feature is enabled. Important: If the Enforce SSL option is enabled, the configuration settings for the chassis should be changed as needed. | Enabled
> Content Filtering / Blacklisting Configuration
> Enable Content Filtering | Select this option to enable the content filtering service on WEM. This option when enabled allows the user to configure the Master Content Rating Database Server (MCRDBS) and Central Decision Point (CDP). By default, this option is enabled. | Enabled
> Enable Blacklisting | Select this option to enable the blacklisting feature on WEM. If this option is enabled, the WEM pulls the files containing the blacklisted URLS from external agency, converts them into binary format and then pushes it to the CDP. | Enabled
> EMS Client Configuration
> Fixed Port Range
> Fixed Port | There are a number of applications on the WEM that require event notifications such as graphing, protocol monitoring, Front and Rear view (FRV) screens, alarms, and software upgrades. Each one requires a dedicated port for itself. Select this option if the WEM Server is to send requests (notifications) to WEM Clients on fixed ports. This is useful if a firewall exists between the Server and the Client. The assigned ports can be opened in the firewall to allow notifications. By default, if enabled, the Server uses a block of 11 ports beginning with the port number specified in by Start Port. If this option is not enabled, the operating system randomly selects open ports for use. | Disabled
> Start Port | If the Fixed Port option is enabled, this parameter specifies the initial port number to use for the block of consecutive fixed ports. The port can be configured to any integer value from 1 through 65535. Important: Ports 1 to 1024 are reserved and should not be used. | 40000
> End Port | If the Fixed Port option is enabled, this parameter specifies the last port number to use for the block of consecutive fixed ports. The port can be configured to any integer value from 1 through 65535. Important: Ports 1 to 1024 are reserved and should not be used. | 40010
> Content Filtering Configuration
> Master Content Rating Database (MCRDBS):
> MCRDBS User Name | Enter a username for the MCRDBS in the field provided. | Null
> MCRDBS Password | Enter a password for the MCRDBS user in the field provided. The password is case sensitive. | Null
> MCRDBS Host IP Address | Enter the host IP address of the MCRDBS to which Content Filtering server statistics files are to be sent. | Null
> MCRDBS Host Name | Enter the host name for an MCRDBS server in the field provided. | Null
> Full Database Import Interval(Hrs) | Enter the time interval in hours for Content Filtering Server to import various databases from MCRDBS (Databases: SFMDB). The range is from 2 to 4320 hours. | 24
> Incremental Database Import Interval(Hrs) | Enter the time interval in hours for Content Filtering Server to import various databases from MCRDBS (Databases: SFMDB-INC). The range is from 2 to 720 hours. | 24
> Full Database Backup Limit (number) | Enter the backup limit for full databases. | 4
> Incremental Database Backup Limit(Days) | Enter the backup limit in days for incremental databases. | 30
> Full Database Import Path | Enter the path to locate the SFMDB files in MCRDBS. For example: <Mcrdbs server path>/cfems/<cfems ip address>/sfmdb | Null
> Incremental Database Import Path | Enter the path to locate the SFMDB-INC files in MCRDBS. For example: <MCRDBS server path>/cfems/<cfems ip address>/sfmincdb | Null
> Archive Database Files | Select 1 if you want to archive the database files. | 1
> Central Decision Point (CDP):
> CDP User Name | Enter a username for the CDP in the field provided. | Null
> CDP Password | Enter a password for the CDP user in the field provided. The password is case sensitive. | Null
> CDP Host Name | Enter the CDP host name in the field provided. | Null
> CDP Host IP Address | Enter the host IP address of the CDP to which CDP statistics files are to be sent. | Null
> Optimized Database Export Interval(Hrs) | Enter the time interval in hours for Content Filtering Server to export the OPTCMDB files to CDP. The range is from 2 to 4320 hours. | 72
> Optimized Incr Database Export Interval(Hrs) | Enter the time interval in hours for Content Filtering Server to export the OPTCMDB incremental files to CDP. The range is from 2 to 720 hours. | 24
> Optimized Database File Export Path | Enter the path for Content Filtering Server to export the OPTCMDB files to CDP. | Null
> Trap Configuration | Select 1 to enable trap notifications. | 1
> Blacklisting Configuration
> NCMEC Configuration:
> URL | Enter the cumulative.csv file path at NCMEC. | Null
> User Name | Enter the username required for authentication at the NCMEC site. | Null
> Password | Enter the password required for authentication at the NCMEC site. | Null
> Import interval(Hrs) | Enter the cumulative.csv file import interval in hours. | 24
> Export to CDP interval(Hrs) | Enter the time interval in hours for Content Filtering Server to export OPTCMDB-BL to CDP. The range is from1 to 5 hours. | 2
> Apache Server Configuration
> Apache Port (HTTP) | Enter the TCP port that the Apache web server communicates on in the field provided. Enter the port number as an integer, ranging from 0 through 65535. | 80
> Apache Port (HTTPS) | Enter the TCP port that the Apache web server communicates securely on in the field provided. Enter the port number as an integer, ranging from 0 through 65535. Important: Apache port HTTP and HTTPS both should be different to establish the successful connection between WEM client and WEM server. | 443
> Administrator Email-ID | Enter an e-mail address for the web server administrator in the field provided. Use the username@domain format. | root@localhost
> EMS Server Configuration
> IMG Session Management (ISM):
> Corba Communication Port | Enter the TCP port over which CORBA communication occurs with the system in the field provided. Important: This field will not be displayed if the Enforce SSL parameter in the SSL Configuration panel is enabled. Important: This setting must be identical to the iiop-port setting on the system. The parameter entered here is used as a default value by the application. Once the server installation is complete, IMGs to be managed can be configured each with their own IMG Port value through the client interface. Enter this value as an integer, ranging from 0 to 65535. | 14132
> Corba Communication Port (SSL) | Enter the port over which CORBA communication occurs with the system in the field provided. The corba communication port is configured same as the SSL port on the boxer. Important: This field will not be displayed if the Enforce SSL parameter in the SSL Configuration panel is disabled. Important: This setting must be identical to the siop-port setting on the system. The parameter entered here is used as a default value by the application. Once the server installation is complete, IMGs to be managed can be configured each with their own IMG Port value through the client interface. Enter this value as an integer, ranging from 0 to 65535. | 14131
> Application Server ID | Enter the name by which the WEM CORBA application server is identified to the chassis. Important: This name must match the parameter configuration on the chassis. The parameter entered here is used as a default value by the application. Once the server installation is complete, IMGs to be managed can be configured each with their own ASID value through the client interface. | STARENT
> Application Server Password | Enter the password used by the WEM CORBA application server when communicating with the chassis. Important: This password must match the parameter configuration on the chassis. The parameter entered here is used as a default value by the application. Once the server installation is complete, IMGs to be managed can be configured each with their own password value through the client interface. | Null
> Network Management System (NMS):
> FTP User Name | Enter a name for the WEM user with FTP privileges on the chassis in the field provided. For FTP to work properly between the WEM server and any chassis, an administrator user with FTP privileges must be configured through the system’s CLI. It is highly recommended that this CLI administrator be configured using the “nocli” option, allowing only FTP privileges into the system. If the WEM server is to manage multiple chassis, then this same CLI user must be configured on each of the chassis. | staradmin
> FTP Password | Enter a password for the FTP user in the field provided. The password is case sensitive. | Null
> User Limit | Enter the maximum number of WEM users that can simultaneously access the server. The number can be configured to any integer value from 1 through 100. | 10
> Security Admin Limit | Enter the maximum number of WEM users with Security Administrator privileges that can simultaneously access the server. The number can be configured to any integer value from 1 to the number specified as the User Limit. | 5
> User Session Limit | Enter the maximum number of sessions allowed for a single WEM user. The number can be configured to any integer value from 0 to the number specified as the User Limit. A value of 0 disables the implementation of user limits on a per-context basis. | 5
> Context User Limit | Enter the maximum number of Web Element Management user sessions allowed on a per-system context basis. The number can be configured to any integer value from 0 to the number specified as the User Limit. A value of 0 disables the implementation of user limits on a per-context basis. | 5
> FTP Session Limit | Enter the maximum number of simultaneous FTP sessions allowed to the chassis through the WEM. The number can be configured to any integer value from 1 through 20. | 5
> Subscriber Management Utility URL | Enter the JDBC connectivity information used to connect to the Subscriber Management Utility (SMU). The SMU is an optional utility used in conjunction with the Application Server Database product. The URL must be specified using the following format: <tomcatip>:<tomcatport> <tomcatip> : The IP address of the server on which the SMU database is installed and running. <tomcatport> : The port number used for communication with the database. appdbconf/appdb.jsp specify the location of the SMU Java applet. Important: This parameter is not required to use the WEM application to manage systems configured to provide data access within the wireless network. | http://<tomcatip>:<tomcatport>/ appdbconf/ appdb.jsp
> Storage Server Directory | Enter the name of the directory in which files shared with the storage server are to be stored. | ./flash
> Syslog Config File | Enter the directory path for the syslog configuration file. This is needed for the WEM’s syslog event viewing functionality. Important: If the file is not found in the specified directory, an error message is displayed. | /etc/syslog.conf
> EMS Server Configuration (contd.)
> Fault Management (FM):
> SNMP Trap Port | Enter the TCP port over which SNMP traps are received from the system in the field provided. Enter this value as an integer, ranging from 0 to 65535. | 162
> SMTP Server Name | Enter a host name or IP address for a Simple Mail Transfer Protocol (SMTP) server, if needed, in the field provided. This is the mail server to which notifications are sent. Important: This parameter must be configured in order to send e-mails to new users when a trap is generated. E-mail can be configured for a trap in Alarm Configuration screen. 'SMTP Server name' is used as the E-mail Server for those mails. | Null
> Sender Email-ID | Configure the e-mail address to which the system is to send notifications in the field provided. The e-mail address should be in the form username@domain. Important: This parameter must be configured in order to send e-mails to new users when a trap is generated. E-mail can be configured for a trap in Alarm Configuration screen. 'Sender E-mail ID' is used as the 'From' (Originator) for those mails. | Null
> Bulk Statistics:
> Bulkstat FTP User Name | Enter the name of the user with FTP privileges on the external network management server. This parameter is used in conjunction with the Bulkstat FTP Perform Operation parameter. | anonymous
> Bulkstat FTP Password | Enter the password of the user with FTP privileges on the external network management server. This parameter is used in conjunction with the Bulkstat FTP User Name parameter. | Null
> Host IP Address | Enter the IP address of the external network management server to which XML-parsed bulkstatistic files are to be sent. This parameter is used in conjunction with the Bulkstat FTP Perform Operation parameter. | 127.0.0.1
> Host Base Directory | Enter the directory on the external network management server to which the bulkstatistic files are to be written. The default directory is /tmp. This parameter is used in conjunction with the Bulkstat FTP Perform Operation parameter. | /tmp
> Archive Bulkstat Files | Select this option if the WEM is to archive bulkstatistic information from the chassis. Archived data is stored to the /<ems_dir>/server/bulkstat_archive directory by default. | Disabled
> Generate XML Files | Select this option if the server is to create XML files containing processed bulkstatistic information for forwarding to a remote server. XML-parsed data is stored in the /<ems_dir>/server/xmldata directory by default. Important: Since the Bulkstat Server process is responsible for XML file generation, if this option is not enabled, the Bulkstat Server process is not started. | Disabled
> Bulkstat FTP Perform Operation | Select this option if the server is to transfer XML-parsed bulkstatistic data files to an external network management server. Bulkstatistic information retrieved from the chassis via FTP is stored in the /<ems_dir>/server/data directory by default prior to processing. | Disabled
> User Administration
> EMS Administrator E-Mail Address | Enter an e-mail ID to be used as the originator for e-mails generated during new user account creation or password resets. | Null
> Hardware Inventory
> Hardware Notifier Email-ID | Enter an e-mail ID to be used as the originator for e-mails generated as a result of a hardware change. | Null
> EMS Process Monitor Configuration
> Poll Interval (sec) | Enter the frequency at which process table queries are performed. The interval is measured in seconds. | 30
> Number Of Retries | Configure the number of times the system attempts to communicate with a process prior to taking action. If the process has not responded to the final attempt within the configured timeout interval, the system considers it unreachable and takes action. | 10
> Timeout Interval (sec) | Configure the amount of time the system should wait prior to re-attempting to communicate with an un-responsive process in the field provided. The interval is measured in seconds. Once the time interval has been reached, the system re-attempts communication for the configured number of retries prior to considering the process unreachable and taking action. | 330
> SMTP Server Name | Enter a host name or IP address for a Simple Mail Transfer Protocol (SMTP) server, if needed, in the field provided. This is the mail server to which notifications are sent when processes fail/start. | Null
> To Email-ID | Configure the e-mail address of the individual to be notified in the field provided. E-mail notifications are sent to this individual when the system cannot communicate with a process. The e-mail address should be in the form username@domain. | Takes setting from previous SMTP parameter.
> Monitor Process | EMS Process Monitor functionality is capable of monitoring WEM server processes at pre-configured intervals. In the event of a process becoming unresponsive, the system sends notifications and can re-spawn the process. Refer to the WEM Process Monitor chapter for additional information. The following processes can be monitored:
> • | EMS Server
> • | Bulkstat Server
> • | Bulkstat Parser
> • | Script Server
> • | NorthBound Server
> | All processes enabled
> Postgres Configuration
> User Name | Enter a username for the Postgres database administrator in the field provided. To ensure proper operation and data integrity, the PostgreSQL database instances installed with the WEM should only be used by the application. | postgres
> Password | Enter a password for the user in the field provided. The password is case sensitive. | Null
> Use Local Installation | Select this option to install Postgres on the local server If enabled, the system's local IP address of 127.0.0.1 is used. Important: This option is not present in the console-based installation script. | Enabled
> Use Remote Installation | Select this option to install Postgres on a remote system. If enabled, configure the IP address of the server in the field provided. Important: This option is not present in the console-based installation script. | Disabled
> Element Management System Installation Confirmation
> | This dialog or script section is informational and contains no configurable parameters. | N/A
> Component Starting Panel (Select the components to be started)
> Select the components to be started | Select the WEM software components to start as part of the installation. The following components are available:
> • | Apache Server
> • | EMS Processes
> • | Restore old postgres 7.2.4 database into new postgres 8.2.0
> Upon selecting the component “Restore old postgres 7.2.4 database into new postgres 8.2.0”, the postgres database migration is started from older version to the new version as WEM releases 7.0 and later support only Postgres version 8.2.0. For more details on the database migration process, refer to the log file .dbmigration.log in the /<ems_dir>/server/log directory. Important: Successful installation of the WEM application requires that the Apache Server and EMS processes be started. The default setting is to enable them. Though prompts are provided to disable them, it is highly recommended that you do not modify the default behavior. | All components selected
> Startup Script Panel
> Start EMS at machine startup | Select this option to enable the WEM to start automatically each time the server on which it is installed is rebooted. | Enabled

> Once all components have started, the following dialog box appears reporting that the installation was successful.

> Step 6 | Click the Finish button to exit the GUI-based installation wizard.

> Step 7 | Verify that all WEM processes were successfully started by looking at the on-screen messages in the console window. The following provides a sample of the messages:

> Starting EMS Server...EMS Server started.PID: 1370Logfile generated as:./log/SERVER_LOG_20051220_142931/SERVER_LOGPlease check file /<ems_dir>/server/log/.server.log for additional debug messagesStarting Script Server...Script Server started.PID: 1389Logfile generated as:./log/SCRIPT_LOG_20051220_142937/SCRIPT_LOG
> The following table lists the processes that are started at installation:

> Process | Log File
> EMS Server | .server.log
> Script Server | .scriptserver.log
> BulkStat Server | .bulkstatserver.log
> BulkStat Parser Server | .bulkstatparser.log
> Monitor Server (if enabled) | .watchdog.log
> NorthBound Server | .northboundserver.log
> Notification Service | .notifyservicescript.log

> Important: The NorthBound Server and Notification Service processes are customer-specific and are not operational without the appropriate license. Please contact your local sales representative for additional information.
> All log files are stored in the /<ems_dir>/server/log directory by default. Refer to log files for additional information in the event that one or more of the processes did not start properly.

> Step 8 | Copy the un-installation script to the _uninst directory created during the installation process (/<ems_dir>/_uninst by default) by entering the following command:

> cp uninst /<ems_dir>/_uninst/

> Step 9 | Copy the files pertaining to the migrate script to the scripts directory created during the installation process (/<ems_dir>/server/scripts by default) by entering the following command:

> cp migrate.tar.gz /<ems_dir>/server/scripts/migrate.tar.gzcp README_MIGRATE /<ems_dir>/server/scripts/README_MIGRATE

> Step 10 | Proceed to the WEM Server Files and Operation chapter of this guide for additional information on WEM Server files and functionality.

> Important: Please contact Starent support for default Username and Password.
> Installing the WEM Software using the Console-Based Installation Method
> Follow the instructions below to install the WEM using the console-based installation script.
> Important: If you are installing the WEM to upgrade an existing version that is currently installed and running, proceed to the Upgrading the WEM Software chapter of this guide.

> Step 1 | Go to the directory in which the WEM installation files are located.

> Step 2 | Execute the setup file by entering the following command:

> ./inst -console
> A message appears welcoming you to the WEM installation.

> Step 3 | Enter “1” to proceed.

> Step 4 | Follow the on-screen prompts to proceed through the installation script and configure the various parameters as required. Refer to the WEM Installation Parameter Descriptions table for descriptions of the configurable parameters within each of the sections of the script.

> Once you have completed the installation configuration and all processes have started, you receive a message indicating that the WEM was successfully installed.

> Step 5 | Enter “3” to finish the installation.

> Step 6 | Verify that all WEM processes were successfully started by looking at the on-screen messages in the console window. The following provides a sample of the messages:

> Starting EMS Server...EMS Server started.PID: 1370Logfile generated as:./log/SERVER_LOG_20051220_142931/SERVER_LOGPlease check file /<ems_dir>/server/log/.server.log for additional debug messagesStarting Script Server...Script Server started.PID: 1389Logfile generated as:./log/SCRIPT_LOG_20051220_142937/SCRIPT_LOG
> The following table lists the processes that are started at installation:

> Process | Log File
> EMS Server | .server.log
> Script Server | .scriptserver.log
> BulkStat Server | .bulkstatserver.log
> BulkStat Parser Server | .bulkstatparser.log
> Monitor Server (if enabled) | .watchdog.log
> NorthBound Server | .northboundserver.log
> Notification Service | .notifyservicescript.log

> Important: The NorthBound Server and Notification Service processes are customer-specific and are not operational without the appropriate license. Please contact your local sales representative for additional information.
> All log files are stored in the /<ems_dir>/server/log directory by default. Refer to log files for additional information in the event that one or more of the processes did not start properly.

> Step 7 | Copy the un-installation script to the _uninst directory created during the installation process (/<ems_dir>/_uninst by default) by entering the following command:

> cp uninst /<ems_dir>/_uninst/

> Step 8 | Copy the files pertaining to the migrate script to the scripts directory created during the installation process (/<ems_dir>/server/scripts by default) by entering the following command:

> cp migrate.tar.gz /<ems_dir>/server/scripts/migrate.tar.gzcp README_MIGRATE /<ems_dir>/server/scripts/README_MIGRATE

> Step 9 | Proceed to the WEM Server Files and Operation chapter of this guide for additional information on WEM Server files and functionality.

> Important: Please contact Starent support for default Username and Password.
> Configuring IPMP on WEM Server
> With IPMP, two or more network interface cards (bge0, bge1 etc.) are dedicated for each network to which the host connects. Each interface is assigned a static “test” IP address, which is used to access the operational state of the interface. Each virtual IP address is assigned to an interface, though there may be more interfaces than virtual IP addresses, some of the interfaces being purely for standby purposes. When the failure of an interface is detected its virtual IP addresses are swapped to an operational interface in the group.
> The IPMP load spreading feature increases the machine's bandwidth by spreading the outbound load between all the cards in the same IPMP group.
> Important: IPMP is a feature supported on Sun® Solaris® provided by Sun Microsystems. The configuration is included in Section VI of the System Administration Guide: IP Services from Sun Microsystems. For more information, refer to the Sun documentation
> This section describes following procedures to configured IP Multipathing on WEM server:
> Before proceeding for IPMP configuration here are some terms related to IPMP configuration:

> • | Multipath Interface Group: This the name given to the group of network devices in a multipath configuration.

> • | Test Addresses: These are IP addresses assigned to each board/interface of the multipath group, they do not move but should not be used for connections in or out of the host.

> • | Multipath/float Address - This is the IP address allocated to a Multipath Interface Group that is shared between all devices in the group (either by load sharing or active standby).

> Configuring Probe-based IP Multipathing
> Configuration procedure given here assumes that:

> • | WEM Server Host name is hostname

> • | NIC_1 and NIC_2 are the network interface devices; i.e. bge0, bge1 etc.

> • | Using network device NIC_2 as active and NIC_1 as the Standby

> • | Multipath Interface Group name is multipath_grp

> • | Multipath IP address is <multipath_IP_address>

> • | Test IP address for <NIC_1> interface in <test_IP_address_NIC_1>

> • | Test IP address for <NIC_2> interface in <test_IP_address_NIC_2>

> Step 1 | Ensure that the MAC addresses on the host are unique by setting the local-mac-address parameter to true by running following command as root user:

> Step 2 | Create an /etc/hostname.<NIC_1> for the Standby network device with the following entry:

> <hostname>-<NIC_1> netmask <netmask> broadcast+group <multipath_grp> deprecated -failover standby up
> hostname is name of the Host and NIC_1 is the network device to be set as Standby.
> multipath_grp is Multipath Interface Group name given to the group of network devices in a multipath configuration.
> <netmask> is the sub-netmask used by network.

> Step 3 | Create an /etc/hostname.<NIC_2> for the active network device with the following entry:

> hostnameNIC_2multipath_grphostname
> hostname is name of the Host and NIC_2 is the network device to be set as active.
> multipath_grp is Multipath Interface Group name given to the group of network devices in a multipath configuration.

> Step 4 | Edit the /etc/hosts file using “vi editor” and add the following three entries:

> <multipath_IP_address> <hostname>-active<test_IP_address_NIC_1> <hostname>-NIC_1<test_IP_address_NIC_2> <hostname>-NIC_2
> multipath_IP_address is the IP address allocated to a Multipath Interface Group that is shared between all devices in the group (either by load sharing or Active-Standby).
> test_IP_address_NIC_1 is the IP addresses assigned to NIC_1 interface of the multipath group, they do not move but should not be used for connections in or out of the host.
> test_IP_address_NIC_2 is the IP addresses assigned to NIC_2 interface of the multipath group, they do not move but should not be used for connections in or out of the host.

> Step 5 | Restart the host by supplying following command:

> shutdown -i 6 -g 0 -y
> Configuring Link-based IP Multipathing
> Configuration procedure provided here assumes that:

> • | WEM Server Host name is hostname

> • | NIC_1 and NIC_2 are the network interface devices; i.e. bge0, bge1 etc.

> • | Using network device NIC_1 as active and NIC_2 as the standby

> • | Multipath Interface Group name is multipath_grp

> • | Multipath IP address is <multipath_IP_address>

> • | Test IP address for NIC_1 interface in <test_IP_address_NIC_1>

> • | Test IP address for NIC_2 interface in <test_IP_address_NIC_2>

> • | my_address is associated with Multipath IP address <multipath_IP_address> in the /etc/hosts file

> Step 1 | Ensure that the MAC addresses on the host are unique by setting the local-mac-address parameter to true by running following command as root user:

> Step 2 | Create an /etc/hostname.<NIC_1> for the Active network device with the following entry:

> my_address netmask + broadcast + group multipath_grp up
> my_address is associated with Multipath IP address <multipath_IP_address> in the /etc/host file.
> multipath_grp is Multipath Interface Group name given to the group of network devices in a multipath configuration.

> Step 3 | Create an /etc/hostname.<NIC_2> for the Standby network device with the following entry:

> group multipath_grp up

> Step 4 | Restart the host by supplying following command:

> shutdown -i 6 -g 0 -y

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