Installing the WEM Software


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:
 
 
<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:
 
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
Step 2
 
gunzip file_name.tar.gz
file_name is the name of the WEM application installation file.
Step 3
 
tar -xvf file_name.tar
Decompressing the installation file results in the following files:
file_name.tar: A compressed file containing all the application files required for both the script- and GUI-based installation methods.
 
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:
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
Step 2
 
./inst
The following WEM Installer dialog appears:
Step 3
Step 4
WEM Installation Parameter Descriptions
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.
/<ems_dir>/ which is /users/ems by default
Important: The IP address specified must be ICMP reachable.
Important: If the Enforce SSL option is enabled, the configuration settings for the chassis should be changed as needed.
Important: Ports 1 to 1024 are reserved and should not be used.
Important: Ports 1 to 1024 are reserved and should not be used.
Important: Apache port HTTP and HTTPS both should be different to establish the successful connection between WEM client and WEM server.
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.
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.
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.
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.
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 0 to the number specified as the User Limit. A value of 0 disables the implementation of user limits on a per-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.
<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.
Important: This parameter is not required to use the WEM application to manage systems configured to provide data access within the wireless network.
Important: If the file is not found in the specified directory, an error message is displayed.
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.
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.
This parameter is used in conjunction with the Bulkstat FTP Perform Operation parameter.
This parameter is used in conjunction with the Bulkstat FTP User Name parameter.
This parameter is used in conjunction with the Bulkstat FTP Perform Operation parameter.
This parameter is used in conjunction with the Bulkstat FTP Perform Operation parameter.
Archived data is stored to the /<ems_dir>/server/bulkstat_archive directory by default.
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.
Bulkstatistic information retrieved from the chassis via FTP is stored in the /<ems_dir>/server/data directory by default prior to processing.
Important: This option is not present in the console-based installation script.
Important: This option is not present in the console-based installation script.
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.
Once all components have started, the following dialog box appears reporting that the installation was successful.
Step 6
Step 7
 
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:
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
 
cp uninst /<ems_dir>/_uninst/
Step 9
 
cp migrate.tar.gz /<ems_dir>/server/scripts/migrate.tar.gzcp README_MIGRATE /<ems_dir>/server/scripts/README_MIGRATE
Step 10
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
Step 2
 
./inst -console
A message appears welcoming you to the WEM installation.
Step 3
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
Step 6
 
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:
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
 
cp uninst /<ems_dir>/_uninst/
Step 8
 
cp migrate.tar.gz /<ems_dir>/server/scripts/migrate.tar.gzcp README_MIGRATE /<ems_dir>/server/scripts/README_MIGRATE
Step 9
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:
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 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
 
 
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
 
<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
 
shutdown -i 6 -g 0 -y
 
Configuring Link-based IP Multipathing
 
Configuration procedure provided here assumes that:
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 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
 
 
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
 
shutdown -i 6 -g 0 -y
 

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