Branch Intelligent Management System 7.0 (E0104)
Copyright (c) 2012-2013 Hewlett-Packard Development Company, L.P. and its licensors.
Table of Contents
1. What's New in this Release
2. Problems Fixed in this Release
3. BIMS Software Distribution Contents
4. BIMS Software Features
5. Installation Prerequisites
6. Client Prerequisites
7. New Installation
8. Upgrade Installation
9. Un-Installation
10. Distributed Deployment
11. TCP Port Usage
12. Known Problems
IMC
What's New in this Release
The version IMC BIMS 7.0 (E0104) can be installed directly or upgraded from IMC BIMS 5.2
(E0401) and its patches versions, IMC BIMS 7.0 (E0101) and IMC BIMS 7.0 (E0102).
Features released in IMC BIMS 7.0 (E0104)
Send alarms by message gateway.
Exhibit device monitor data by charts.
Add device up statistic report.
View 3G signal strength of device in topology.
Features released in IMC BIMS 7.0 (E0102)
CPE Alarm
o Configuration change alarming.
Resource
o Matching a branch device by using BIMS username.
Configuration Management
o Restore configuration by time.
o Baseline software for CPE Type.
System Configuration
o Forward operation log to Syslog.
Features released in IMC BIMS 5.2 (E0401H01)
None.
Features released in IMC BIMS 5.2 (E0401)
Homepage
o Traffic statistics trend graph-today.
o Location view.
o Top5 worst SIM card signal strength-today.
o Top5 traffic of devices-this month.
o Top5 SIM card offline duration-this month.
Quick Start
o Service processing.
o Function list.
GIS Map
o View devices in GIS map.
Resource Management
o Add/modify/delete device.
o Import device from file/UAM.
o Export device.
o Switch primary and secondary phone numbers.
o Deploy SMS.
o SMS deployment history for device.
o Locate in GIS.
o Locate in topology.
o Add/modify/delete location view.
o Location view tree.
o Add/modify/delete service provider view.
o Add/delete/move telephone card.
Performance Management
o View performance details.
o Set RSSI Thresholds.
Option Management
o SMS gateway configuration.
o BIMS parameter configuration.
o Block GPS globally.
o UAM server configuration.
[ Table of Contents ]
Problems Fixed in this Release
IMC BIMS 7.0 (E0104) fixes the following problems after IMC BIMS 5.2 (E0401).
Resolved Problems in IMC BIMS 7.0 (E0104)
1. When "Common Password Status" is enabled, there should be an option named "Change
ACS Password to Random String".
2. CPE authenticated by ACS username cannot be imported.
Resolved Problems in IMC BIMS 7.0 (E0102)
1. The menu and button of Data model pop window are all Chinese in HP English version.
2. The 'Modify Status Polling Interval' function doesn't work.
3. The upgrade of BIMS component will fail when upgrading form BIMS 5.0-E0105 or
earlier.
4. The WanconnectionDevice parameter is not available when a WAN IP connection and
WAN PPP connection are added.
5. Modifying a WAN IP connection has failed.
Resolved Problems in IMC BIMS 5.2 (E0401H01)
1. Deployment result for a single device is not displayed in the SMS deployment operation
logs.
2. There will be two same device items in CPE list in BIMS.
3. Performance monitoring data will be abnormal.
4. The configuration task pushed by IVM has failed to be deployed.
5. The deployment task automatically created by the system to apply the configuration of an
old CPE on a new CPE has failed to be deployed.
6. BIMS-Only log files of today are saved on the auto-configuration server.
Resolved Problems in IMC BIMS 5.2 (E0401)
1. Fail to run the automatic deployment task using a configuration template, whose name
contains spaces..
[ Table of Contents ]
BIMS Software Distribution Contents
The BIMS distribution list contains the following files and folders:
1. BIMS\manual\readme_bims_7.0 (E0104).html - this file
2. BIMS\install - the BIMS installation program for Windows and Red Hat Enterprise
Linux
[ Table of Contents ]
Installation Prerequisites
Server Requirements
The following are the minimum hardware and software requirements for running BIMS on a
server:
Minimum hardware requirements
o Pentium 4 3.0GHz processor
o 4096M of RAM
o 50G hard disk space
Operating system (Versions marked X64 are recommended):
o Windows Server 2003 with Service Pack 2
o Windows Server 2003 X64 with Service Pack 2 and KB942288
o Windows Server 2003 R2 with Service Pack 2
o Windows Server 2003 R2 X64 with Service Pack 2 with
KB942288
o Windows Server 2008 with Service Pack 2
o Windows Server 2008 X64 with Service Pack 2
o Windows Server 2008 R2 X64 with Service Pack 1
o Windows Server 2012 X64 with KB2836988
o Red Hat Enterprise Linux 5 (Enterprise and Standard versions
only)
o Red Hat Enterprise Linux 5 X64 (Enterprise and Standard versions
only)
o Red Hat Enterprise Linux 5.5 (Enterprise and Standard versions
only)
o Red Hat Enterprise Linux 5.5 X64 (Enterprise and Standard
versions only)
o Red Hat Enterprise Linux 5.9 (Enterprise and Standard versions
only)
o Red Hat Enterprise Linux 5.9 X64 (Enterprise and Standard
versions only)
o Red Hat Enterprise Linux 6.1 X64 (Enterprise and Standard
versions only)
o Red Hat Enterprise Linux 6.4 X64 (Enterprise and Standard
versions only)
VMware:
o VMware Workstation 6.5.x
o VMware Workstation 9.0.x
o VMware ESX Server 4.x
o VMware ESX Server 5.x
Hyper-V:
o Windows Server 2008 R2 Hyper-V
o Windows Server 2012 Hyper-V
Database
o Microsoft SQL Server 2005 Service Pack 4 (Windows only)
o Microsoft SQL Server 2008 Service Pack 3 (Windows only)
o Microsoft SQL Server 2008 R2 Service Pack 2 (Windows only)
o Microsoft SQL Server 2012 Service Pack 1 (Windows only)
o Oracle 11g Release 1 (Linux only)
o Oracle 11g Release 2 (Linux only)
o Oracle 11g Release 2 (64-bit) (Linux only)
o MySQL Enterprise Server 5.1 (Linux and Windows) (Up to 1000
devices are supported)
o MySQL Enterprise Server 5.5 (Linux and Windows) (Up to 1000
devices are supported)
o MySQL Enterprise Server 5.6 (Linux and Windows) (Up to 1000
devices are supported)
IMC Platform Compatibility
o HP IMC Platform version: HP IMC PLAT 7.0 (E0102) or later
Note: 64-bit operating systems are recommended over 32-bit operating systems because of the
larger amount of available memory for applications.
Note: Optimal hardware requirements vary with scale, other management factors, and are
specific to each infrastructure. Please consult HP, or your local account teams and precise
requirements can be provided.
[ Table of Contents ]
Client Prerequisites
PC Requirements
Minimum hardware requirements
o Pentium 4 2.0GHz processor
o 2048M of RAM
o 50G hard disk space
Operating system
o Windows XP SP3 or later
Browser
o IE 9.0 or 10.0 is recommended.
o Firefox 20 or later is recommended.
o Chrome 26 or later is recommended.
o Turn off the blocking settings in the browser.
o Add the IMC website to the trusted sites of the browser.
o The client resolution is 1280*768 at least.
o JRE 1.6.0_update10 or later is recommended. If a client has no
JRE, IMC prompts the user to install JRE for the client.
[ Table of Contents ]
New Installation
Before installing BIMS, make sure the IMC is installed correctly. To install BIMS, click Install
button on the Monitor tab of the Intelligent Deployment Monitoring Agent, then select the
components sub-directory of the install package, and click OK button to launch the installation
wizard.
For detailed installation instructions, please refer to IMC Installation Guide.
[ Table of Contents ]
Upgrade Installation
This program can be upgraded from IMC BIMS 5.2 (E0401) and its patches versions, IMC
BIMS 7.0 (E0101) and IMC BIMS 7.0 (E0102).
Follow these instructions to upgrade IMC:
1. Back up the IMC database on the Environment tab in the Intelligent Deployment
Monitoring Agent.
2. Stop the IMC system in the Intelligent Deployment Monitoring Agent.
3. Click Install on the Monitor tab of the Intelligent Deployment Monitoring Agent.
4. Select the install/components subdirectory of the upgrade package, and click OK.
5. After the installation is complete, the Intelligent Deployment Monitoring Agent lists the
components that need to be upgraded. Click OK to start upgrading the components.
6. If this is a distributed deployment, upgrade the components deployed on the slave servers
separately.
7. After the update is complete, start all processes in the Intelligent Deployment Monitoring
Agent window.
For more information about installation instructions, please refer to IMC Installation Guide.
[ Table of Contents ]
Un-Installation
You can remove BIMS component through the intelligent deployment monitoring agent. Perform
the following steps:
1. Select Start/All Programs/HP Intelligent Management Center/HP Deployment
Monitoring Agent.
2. In the window displayed, select Stop IMC in the Monitor tab to stop all processes of
IMC.
3. In the Deploy tab, right-click the BIMS component, select Uninstall the Component
from the shortcut menu.
4. A dialog box appears, indicating that the component was successfully removed. Click
OK.
[ Table of Contents ]
Distributed Deployment
Port
Usage
TCP 8025
Used to receive SHUTDOWN command for the jserver process.
TCP 9091
The JMX monitoring port used by the jserver process.
TCP 9044
Used to receive SHUTDOWN command to the HP IMC Server service process.
TCP 9055
Used to receive SHUTDOWN command to the Deployment Monitoring Agent
process.
TCP 61616
Used for communication in a Master-Slave deployment environment.
TCP 61626
Used for communication to the HP IMC Server and Deployment Monitoring
Agent.
UDP 161
Used to access network elements through SNMP.
UDP 162
Used to accept SNMP Traps from network elements.
TCP 22
SSH/SFTP port, which the configuration center uses to back up and restore the
device software and configuration file through SSH/SFTP.
TCP 20/21
FTP port, which the configuration center uses to back up and restore the device
software and configuration file through FTP.
The BIMS ACS modules may be installed on more than one server to meet specific performance
requirements. A typical scenario is where the system has one Master server with BIMS Platform
deployed and multiple Slave servers with BIMS ACS modules deployed.
To install the BIMS on a Slave Server, perform the following steps:
1. Select Start/All Programs/HP Intelligent Management Center/HP Deployment
Monitoring Agent.
2. In the window displayed, select Stop IMC in the Monitor tab to stop all processes of
IMC.
3. In the Deploy tab, right-click the BIMS ACS component, select Deploy the Component
from the shortcut menu.
4. A dialog box appears, indicating that the component was successfully deployed. Click
OK.
[ Table of Contents ]
TCP Port Usage
The BIMS Server will BIND to and use the following TCP/IP Ports.
TCP 23
Telnet port, which the resource management module, ACL management module,
and configuration center use to access the device through Telnet.
TCP 25
SMTP port, which the resource management module uses to send alarms through
email.
ICMP
ICMP port, which the resource management module uses to discover devices and
check the reachability of the devices.
UDP 69
IMC-specific tftp daemon.
TCP 80
Used to launch the web network management system of the device.
TCP 443
HTTPS port, which the virtual network management module uses to obtain
VMware virtual network data in SSL.
UDP
514/515
IMC-specific syslog daemon.
TCP/UDP
137
NetBIOS name resolution service port, used by the IMC resource management
module and terminal access module.
TCP 8080
IMC-specific web server for HTTP protocol (can be changed when installation).
TCP 8443
IMC-specific web server for HTTPS protocol (can be changed when installation).
TCP 9090
Port for the CPE to access BIMS ACS through HTTP (can be changed after
installation).
TCP 9443
Port for the CPE to access BIMS ACS through HTTPS (can be changed after
installation).
TCP 8800
iMF listening port.
TCP 1433
SQL Server database listening port (Windows only).
[ Table of Contents ]
Known Problems
Installation/Upgrade/Patch
For a correct installation, the installation path can contain letters, digits, underlines, and
spaces, but cannot other special characters.
In Linux, the Oracle SIDs must be consistent if you adopt a distributed deployment for
BIMS or install BIMS and database separately.
If the system installed with the BIMS has insufficient memory, java overflow may occur.
Please install the BIMS in a 64-bit OS and add more memory.
[ Table of Contents ]
Issued: Dec 2013
Copyright (c) 2012-2013 Hewlett-Packard Development Company, L.P. and its licensors.
Loading...