iNET-Installation, Startup & Maintenance Guide

Loop-iNET
Installation, Startup & Maintenance

Guide
LOOP TELECOMMUNICATION INTERNATIONAL, INC.

8F, NO. 8, HSIN ANN RD.
SCIENCE-BASED INDUSTRIAL PARK
HSINCHU, TAIWAN
Tel: 886-3-578-7696
Fax: 886-3-578-7695
LoopTelecom.com
 2014 Loop Telecommunication International, Inc. All rights reserved.
Version 12 23 Oct, 2014
Part I Before Installation
Chapter 1 - Loop-iNET Deployment Architecture
Manual Structure
This User‟s Manual is written to follow a user‟s logical activities when using a network
management system and is comprised of the following parts and information:

1. Basic Knowledge – What is the deployment architecture? What software are used
and/or included to make the Loop-iNET work? What key telecommunications concepts
do I need to understand to maximize my use of Loop-iNET for my network?
Part II Installation of Loop-iNET

2. Installation of Loop-iNET – What are the recommended system requirements? How do
I install Loop-iNET servers?
Part III Provisioning

3. Launching the Loop-iNET Application – How do I launch or open Loop-iNET? How do
I create Loop-iNET users under different privileges? How do I start the system
components?
Part IV Loop-iNET System Maintenance

4. Security Management – How do I set user passwords and establish group passwords?
How often should I review the security of my network and what must I do to ensure that
Loop-iNET security management is providing the best possible security at all times?
5. System Monitor – How do I monitor the current status of each system component,
equipment and user? How do I enable and disable a certain component?
6. How to Maintain DB&Files with Loop-iNET – What is needed to back up, restore or
drop in the Loop-iNET database?
7. How to Use the Loop-iNET License Manager – How can I back up, export and import
the license file to keep it very well?
8. How to Use the NTP Service – How do I synchronize the time by using NTP protocol?
Loop-iNET Intelligent Network Management System Page 1

Table of Contents
Part I Before Installation .............................................................................................................. 4
Chapter 1 - Loop-iNET Deployment Architecture ...................................................................... 4
Chapter 2 - Loop-iNET System Architecture ............................................................................. 4
2.1 Management Architecture ........................................................................................... 5
2.2 Software Architecture .................................................................................................. 6
2.3 Loop-iNET System Components ................................................................................. 7
Chapter 3 - Step-by-Step Guide ............................................................................................... 8
Part II Installation & Uninstall ....................................................................................................... 9
Chapter 4 - System Requirements ........................................................................................... 9
Chapter 5 - Server Configuration.............................................................................................. 9
5.2 Server Configurations for Windows ................................................................................. 9
5.2.1 JDK Installation and Configuration............................................................................ 9
5.2.2 MYSQL Database Installation and Configuration .................................................... 16
5.2.2.1 Enable Remote Access to MYSQL Database Server ........................................ 27
5.2.3 ActiveMQ Server Installation and Start-up .............................................................. 30
5.2.4 Web Server Installation and Start-up ...................................................................... 32
5.2.4.1 Tomcat Sever Start-up ..................................................................................... 32
5.2.4.2 Jboss Sever Start-up ....................................................................................... 33
5.3 Server Configurations for Linux ..................................................................................... 34
5.3.1 JDK Installation and Configuration.......................................................................... 34
5.3.2 MYSQL Database Installation and Configuration .................................................... 35
5.3.2.1 Enable Remote Access to MYSQL Database Server ........................................ 38
5.3.3 ActiveMQ Server Installation and Start-up .............................................................. 41
5.3.4 Web Server Installation and Start-up ...................................................................... 43
5.3.4.1 Tomcat Sever Start-up ..................................................................................... 43
5.3.4.2 Jboss Sever Start-up ....................................................................................... 44
Chapter 6 - Loop-iNET Server Installation .............................................................................. 45
6.4 Loop-iNET Server Installation Instructions for Windows ................................................ 45
6.4.1 New Installation...................................................................................................... 45
6.4.2 Upgrade Installation ............................................................................................... 54
6.4.3 Modification............................................................................................................ 57
6.4.4 Uninstall ................................................................................................................. 67
6.5 Loop-iNET Server Installation Instructions for Linux ...................................................... 70
6.5.1 New Installation...................................................................................................... 70
6.5.2 Upgrade Installation ............................................................................................... 81
6.5.3 Modification............................................................................................................ 84
6.5.4 Uninstall ................................................................................................................. 94
Part III –Startup & Provisioning .................................................................................................. 98
Chapter 7 - Launching the Loop-iNET Application .................................................................. 98
7.1 Launching Loop-iNET ................................................................................................... 98
7.2 Registering Loop-iNET License..................................................................................... 98
7.3 Creating Loop-iNET Accounts..................................................................................... 102
7.4 Authenticating Loop-iNET Components ...................................................................... 102
Chapter 8 - DR Site Manager ............................................................................................... 107
8.1 Single Site .............................................................................................................. 108
8.1.1 Site Status ........................................................................................................ 108
8.1.2 Site Provisioning ............................................................................................... 108
8.1.2 Operational Switch............................................................................................ 109
8.2 Disaster Recovery(Optional) ................................................................................... 109
8.2.1 Site Status ........................................................................................................ 109
8.2.2 Site Provisioning ............................................................................................... 109
8.2.3 Operational Switching ....................................................................................... 111

8.2.4 Instance for Warm Standby ............................................................................... 111
8.2.5 Instance for Hot Standby .................................................................................. 116
Part IV – System Maintenance ................................................................................................ 122
Chapter 9 - Security Management ........................................................................................ 122
9.1 User Manager............................................................................................................. 122
9.1.1 Adding a New Group ............................................................................................ 122
9.1.2 Adding a New User .............................................................................................. 126
9.1.3 Querying Users/Groups ........................................................................................ 128
9.1.4 Available Options for User .................................................................................... 129
9.1.5 Available Options for Group.................................................................................. 129
9.2 System Logs............................................................................................................... 130
9.3 Policy ......................................................................................................................... 130
Chapter 10 - System Event/Alarm Query.............................................................................. 133
Chapter 11 - Instructions for Changing IP Address of Loop-iNET Server .............................. 134
Chapter 12 - Instructions for IPv6 Support ............................................................................ 136
Chapter 13 - North Bound Interface(Optional) ...................................................................... 139
Chapter 14 - System Management ....................................................................................... 143
14.1 System Monitor......................................................................................................... 143
14.2 Organization ............................................................................................................. 143
14.3 Set Default Value...................................................................................................... 144
14.4 Mail Server Configuration ......................................................................................... 144
14.5 License Manager ...................................................................................................... 145
14.6 Cloud Disk ................................................................................................................ 148
14.7 Database & File Maintenance ................................................................................... 148
14.7.1 Database Backup/Restore .................................................................................. 148
14.7.1.1 Task Schedule ............................................................................................. 149
14.7.1.2 Backup Files(Current Version) ..................................................................... 153
14.7.1.3 Backup Files(History Version) ...................................................................... 154
14.7.2 Expiration Maintenance ...................................................................................... 154
14.7.3 DB Backup File Mirroring.................................................................................... 156
14.8 Services ................................................................................................................... 157
14.8.1 NTP Time Sync .................................................................................................. 157
14.8.2 Services Configuration ....................................................................................... 157
14.9 Debugging File ......................................................................................................... 157
Part VI Appendices.................................................................................................................. 159
Appendix A Table of Loop-iNET System Alarm Events ........................................................ 159
Appendix B Web Server Memory Modification ..................................................................... 160
1． Instructions for Parameter Setup ................................................................................ 160
2． Tomcat Memory Setup ............................................................................................... 160
2.1 For Windows ........................................................................................................... 160
2.2 For Linux/Uninx ....................................................................................................... 160
3． Jboss Memory Setup ................................................................................................. 160
3.1 For Windows ........................................................................................................... 160
3.2 For Linux/Uninx ....................................................................................................... 161
Appendix C: Frequently Asked Questions ........................................................................... 162
1. Installation & Uninstall ............................................................................................... 162
2. Maintenance ............................................................................................................. 164


Before starting the installation procedures, user shall learn some basic knowledge about Loop-
iNet, such as the deployment architecture and system architecture, which will be detailed in the
sections below.

Loop-iNET uses browser/server distributed architecture in its deployment structure. See the
deployment structure in the Figure below which consists of several components. For increased
reliability and network performance, the user can deploy the system components in different
machines. Loop-iNET supports sub networks that are helpful in managing and organizing your
network. This distributed architecture also allows for network scalability by adding more system
components. Loop-iNET‟s system monitor allows you to know how is the network performance
exactly, based on which you will learn whether you need to add more components or change an
advanced computer. Whether your network is growing or needs to shrink based on your business
needs, you will not have to be concerned about negative changes in performance.
MIB
Topology Alarm ……
configuration
Resource Event NE Panel

Web GUI
Resource Event Damon Notification System

Damon [RD] [ED] Damon [ND] Component
Management
ActiveMQ DB
Common Server [SCMS]
NE Panel Configure
Service Damon
Damon [NPD] Damon [CD] ……
[CSD] core
Trap Receiver Polling Agent

SBI
iNET Server Web Browser
…
Ethernet
Sub-Network
Sub-Network Sub-Network
Sub-Network
Chapter 2 - Loop-iNET System Architecture

Loop-iNET utilizes a browser/server distributed architecture based on industry standard platforms

thus supplying multi-user support. The architecture is designed to allow the various server
components to execute on one or more servers in order to provide scalability and redundancy.
The following diagrams are provided for a very high level explanation of the Loop-iNET
architecture.
 Management Architecture
 Software Architecture
 Loop-iNET System Components
2.1 Management Architecture
Loop-iNET‟s management architecture in the Figure below consists of the following three layers:
 OSS layer(Optional)
 Loop-iNET Layer
 NE Layer
(Optional OSS LAYER )
Software Architecture
iNET LAYER iNET included in iNET Layer
SDH AN1
SDH Third-Party SDH DME AN1

Device
NE LAYER AN1
SDH
AN2 AN2
Loop‟s iNET can support an optional Operational Support System (OSS) Layer that would allow
users to use their own OSS which may offer different operation support modules outside of
network management.
The Loop-iNET Layer can be used as the top layer of the management architecture. It also can
powerfully stand alone to fully provide FCAPS (fault-management, configuration, accounting,
performance, and security) functions.

The network element (NE) Layer consists of Loop‟s network devices. Please see Loop‟s user
manuals for more information specific to these devices.
The Loop-iNET Layer accesses the NE Layer via a southbound interface (SBIF) Simple Network
Management Protocol (SNMP).
2.2 Software Architecture
The software architecture for Loop-iNET consists of a distributed processing platform (DPP). The
DPP consists of three layers as shown in the following software architecture layers and
components (Figure (2-3):
Distributed Processing Platform

 Presentation Layer(Web-GUI)
o NE/Subnet Topology
o MIB Configuration
o Alarm
o Resource
o Event
o NE Panel
 Logic Processing Layer (Loop-iNET Core)
o Resource Daemon
o Event Daemon
o Notification Daemon
o NE Panel Daemon
o Common Service Daemon
o Configure Daemon
o System Component Management Server
 Adaptation Layer (SBI)
o Polling Agent
o Trap Receiver
 Active MQ(Data Transmission)
 Database(Data Storage)
The Presentation Layer(Web-GUI) displays the Loop-iNET powerful functions in web-based

graphic interfaces, where the user can perform all Loop-iNET functions(view management, alarm
management, user management, system management, etc.).
The Logic Processing Layer(Loop-iNET Core) includes the core system components of Loop-
iNET system, which is mainly responsible for data gathering and processing.
The Adaptation Layer(SBI) is the southbound interface, which access the managed devices.
Active MQ(Data Transmission) transmits the data between the three layers as shown in the
Figure.
Database(Data Storage) stores the data of the entire system.
2.3 Loop-iNET System Components
Loop-iNET system consists of the following system components (recall from the Software
Architecture):
 System Component Management Server (SCMS) – It manages all other system

components like a central server. If it doesn‟t work normally, the whole Loop-iNET system will
crash as well.
 Web-Based Graphic User Interface (Web-GUI) – It provides friendly user interfaces for the
user, so the user performs all operations via this component. If it doesn‟t work normally, the
user can‟t access Loop-iNET system interfaces.
 Scan Daemon (SD) –It clears the alarms regularly based on the user settings and
determines whether Loop-iNET system will send out notification mail to the related personnel.
It is also responsible for the part of File Transfer. If it doesn‟t work normally, the Loop-iNET
system may not clear alarms regularly, moreover, the notification mail may not be sent out
successfully; and you may not normally use File Transfer function.
 Polling Agent (PA) – It is responsible for polling the devices through SNMP protocol.
Specifically, it processes the requests sent from other components, and transmits them to the
managed devices. And then, it gathers the message returned from the devices, and sends
back to the components. Thus, if it doesn‟t work normally, the communication between the
device and components will be interrupted.
 Trap Receiver (TR) –It receives the traps sent from the device. If it doesn‟t work normally,
Loop-iNET system may not receive the traps sent from the devices.
 Configure Daemon (CD)＊ –It transmits the data between the Loop-iNET system and the NE.
If it doesn‟t work normally, all devices will be offline, and the user can‟t get MIB value from
MIB tree.
 Common Service Daemon (CSD) ＊ –It provides common services, such as NTP service. If it
doesn‟t work normally, the NTP service may be unavailable too.
 Notification (NF) ＊ –It sends the alarm notifications to the related personnel. If it doesn‟t
work normally, the notification mail may not be sent out successfully.

＊
Event Daemon (ED) –It processes events and produces alarms based on the event filter
settings of Loop-iNET system. If it doesn‟t work normally, Loop-iNET system may not receive
any events or alarms.
 Resource Daemon (RD) ＊ – It gathers the information of the resources within Loop-iNET
system, including the device type, firmware version, CAAS and serial No. If it doesn‟t work
normally, Loop-iNET system may not obtain the related information timely.

Chapter 3 - Step-by-Step Guide
 NE Panel Daemon (NPD) – It processes the NE panel data, which will be presented on the
interface. If it doesn‟t work normally, the user can‟t obtain the NE panel data timely.
 Northbound Interface(NBI) – It is provided to the users to view the data gathered from
Loop-iNET system on the SNMPc interface, which also allows the users to make some
personal configurations.
 Diagnostic Damon (DD) – It diagnoses the telecommunications network which consists of
TDM/IP. If it doesn‟t work normally, the user can‟t diagnose the telecommunications network.
 NE Business Damon (NBD) – It processes the logical operation between Multi-NEs. If it
doesn‟t work normally, the module of related logical operation can‟t work normally.
＊
Note: The components with symbol provide High Availability solution. High Availability(HA)
refers to the availability of resources in a computer system, in the wake of component failures in
the system. In Loop-iNET system, it can be achieved by using the stand-by software components
to ensure availability.
Chapter 3 - Step-by-Step Guide

The table below is a step-by-step guide for you to complete Loop-iNET configuration for the first
time.
Comment or Chapter in the

Step Task
Guide(for more information)
Install the 3rd-party software required and configure the Chapter 5
1 server
Install Loop-iNET server Chapter 6
2
Launch Loop-iNET application and register license file Chapter 7
3
Add user groups and individual users into Loop-iNET Chapter 9
4
Authenticate Loop-iNET components Chapter 7
5
Loop-iNET is ready to provide service –
Perform routine management, such as security
management and system management
Part II Installation & Uninstall
Chapter 4 - System Requirements

Chapter 4 - System Requirements
To begin using and managing your Loop-iNET system, you must install the entire Loop-iNET
environment. This includes tools and Loop-iNET software installation on the operating system.
Before you start to install Loop-iNET, verify that your client and server hardware satisfy the
recommended specification that is listed for servers and clients.
For Server
PARAMETER REQUIREMENTS
Operating System Windows Server 2008/Linux(CentOS)
Java Platform JDK v1.7
Database MYSQL v5.5
Web Server Tomcat v7.x/Jboss v4.x
Message Server ActiveMQ v5.x
For Client
PARAMETER REQUIREMENTS
Operating System Windows
Browser Firefox(v28~32); IE 11
Java Platform JDK v1.7
Loop-iNET supports the operating system of Windows and Linux, hence we will introduce the
configuration and installation steps on Windows and Linux operating systems for your reference.
Chapter 5 - Server Configuration

5.2 Server Configurations for Windows
For the first installation of Loop-iNET server, you need to install and configure the required third-
party software, including JDK, MYSQL, ActiveMQ and Web Server (Tomcat/Jboss). For the
upgrade installation or modification, just skip this section.
5.2.1 JDK Installation and Configuration
Here we take jdk-6u29-windows-i586 as an example to explain. Double-click the *.exe file to

launch the installation. You will access the following screen.

Click Next to continue.

Click Next to install JDK with the default settings, as shown below.
Click Next to proceed, or click Change to modify the installation directory.

Wait patiently when the installation is proceeding.
Click Finish to when you see the following screen.

After that you need to make some settings for the JDK platform.
Right-click My Computer and select Properties. Go to Advanced option and press

Environmental Variables.

Press New button to add a new system variable with the name of JAVA_HOME, and value of
C:\Program Files\Java\jdk1.6.0_29.
Double-click Path under System Variables to add %JAVA_HOME%\bin; to the very beginning.
Close all windows and reboot the system to complete the configurations. (You can test the
configuration by using the „java –version‟ command.)
At last, you need to go to the Control Panel and select Java. You will see the following screen.
Please make sure the option of Check for Updates Automatically is disabled.

5.2.2 MYSQL Database Installation and Configuration
Note: MYSQL requires .NET Framework 4.0 and Windows Service Pack 3 or later.
Double-click on the MYSQL installer, you will access the following screen.
When you see the followings screen, please select Install MYSQL Products.
Check the option I accept the license terms, and then click Next to continue.
Select whether you need the updates based on the specific needs, and click Execute.

Click Next to install the type of Developer Default.
When you return to the screen below, click Next.

Confirm the settings, and click Execute.
When the products are being installed, please wait patiently.

When you see the following screen, please click Next to continue.

Set the root password and click Next to continue. Please note that you have to remember or write
the root password down, because it will be needed during the Loop-iNET installation.

Click Next when the configuration of MYSQL server is completed.
Click Next when the configuration of Samples and Example is completed.

Click Finish to exit the installation.
Note: You have to add the directory of \MySQL Server 5.1\bin into the Windows PATH variable,
but don‟t add it to the very beginning. After that, please reboot the system to make the settings
take effect. Below is a sample screen for your reference.

The following steps are only required for IPv6, which are unnecessary for IPv4.
Right-click My Computer/Manage, double-click Services and Applications/Services, and then

locate MYSQL. Find the directory after default file, as shown below.
Open that file and add the configuration of bind-address=:: under [mysqld], as shown below.
If you want to use Disaster Recovery feature under Site Manager later, please also add the
following configuration under [mysqld] and [mysqldump](See the last line of configuration below),
as listed below. At the meantime, you need to pay attention to the following two points:
1. The user should specify the server ID as required, which is xxxx to be specified in this
example.
2. The recommended settings are provided for reference only, which could be modified
depending on your preference.
[mysqld]
# required unique id between 1 and 2^32 - 1
server-id = xxxx
#for replication

log-bin=mysql-bin
binlog_format=mixed
skip-slave-start
log-slave-updates=1
binlog-do-db=inet
binlog-ignore-db=mysql
replicate-do-db=inet
replicate-ignore-db=mysql
replicate-ignore-table=inet.access_mode_type
replicate-ignore-table=inet.brand
replicate-ignore-table=inet.caas_access_configuration
replicate-ignore-table=inet.card_access_configuration
replicate-ignore-table=inet.component
replicate-ignore-table=inet.component_default_configuration
replicate-ignore-table=inet.component_ip_mac
replicate-ignore-table=inet.component_type
replicate-ignore-table=inet.data
replicate-ignore-table=inet.data_original
replicate-ignore-table=inet.diagnostic_config
replicate-ignore-table=inet.diagnostic_mapping
replicate-ignore-table=inet.dictionary
replicate-ignore-table=inet.ecfm_sync_configuration
replicate-ignore-table=inet.equipment_firmware_configuration
replicate-ignore-table=inet.event_definition
replicate-ignore-table=inet.firmware_version
replicate-ignore-table=inet.help_tip
replicate-ignore-table=inet.i18n
replicate-ignore-table=inet.install_info
replicate-ignore-table=inet.language_config
replicate-ignore-table=inet.mib
replicate-ignore-table=inet.mib_trans
replicate-ignore-table=inet.mibgroup_configuration_relation
replicate-ignore-table=inet.mib_group
replicate-ignore-table=inet.mib_hide
replicate-ignore-table=inet.mib_npxml_relation
replicate-ignore-table=inet.np_xml_version
replicate-ignore-table=inet.online_users
replicate-ignore-table=inet.privilege
replicate-ignore-table=inet.service_type
replicate-ignore-table=inet.sn_access_configuration
replicate-ignore-table=inet.system_info_definition
replicate-ignore-table=inet.sys_event_filter
replicate-ignore-table=inet.sys_event_filter_act
replicate-ignore-table=inet.sys_event_filter_detail
replicate-ignore-table=inet.themes
replicate-ignore-table=inet.transfer_mapping
replicate-ignore-table=inet.transfer_rules
replicate-ignore-table=inet.wallpapers
replicate-ignore-table=inet.xc_sync_configuration
replicate-ignore-table=inet.dr_site
replicate-ignore-table=inet.dr_sync_master_record
replicate-ignore-table=inet.component_function
replicate-ignore-table=inet.fl
replicate-ignore-table=inet.flt
replicate-ignore-table=inet.function
replicate-ignore-table=inet.function_config
replicate-ignore-table=inet.online_users
replicate-ignore-table=inet.product_info
replicate-ignore-table=inet.purchaser
#recommended settings
character-set-server=utf8
default-storage-engine=INNODB
sql-
mode="STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTI
ON"
skip-external-locking
key_buffer_size = 16M
max_allowed_packet = 16M
table_open_cache = 64
sort_buffer_size = 512K
net_buffer_length = 8K
read_buffer_size = 256K
read_rnd_buffer_size = 512K
max_connections=500
#for innodb
innodb_buffer_pool_size = 512M
innodb_additional_mem_pool_size = 2M
innodb_log_file_size = 256M
innodb_log_buffer_size = 8M
innodb_flush_log_at_trx_commit = 2
#innodb_lock_wait_timeout = 50
[mysqldump]
max_allowed_packet = 16M
5.2.2.1 Enable Remote Access to MYSQL Database Server
After the system is rebooted, you need to enable the remote access by performing the following
steps.
Open a command line, and log in with root privilege, as shown below.
a. Log in the MYSQL without a root password.

b. Log in the MYSQL with a root password.
Execute the command of use mysql;

To enable the remote access for the root users, please execute the command of UPDATE user
SET host = '%' WHERE user = 'root' and host = '127.0.0.1';
To grant all privileges onto the root users, please execute the command of GRANT ALL
PRIVILEGES ON *.* TO 'root'@'%' WITH GRANT OPTION;

Execute the command of FLUSH PRIVILEGES; to make the setting take effect, and exit the
terminal.
5.2.3 ActiveMQ Server Installation and Start-up
Note: Please make sure you have installed JDK before installing ActiveMQ server.
The ActiveMQ server can be launched by performing the following steps(ActiveMQ server v5.x as
an example):
Extract the ActiveMQ package in a folder.
Enter the directory of \apache-ActiveMQ-5.5.1\bin, and double-click ActiveMQ.bat to start up

the ActiveMQ server.
You will see the following screen. To stop ActiveMQ server, you just need to press Ctrl+C.
Note: The initial username and password for ActiveMQ is system and manager respectively.
Please remember it or write it down, because it will be needed during the Loop-iNET installation.
However, you could modify it in credentials.properties under the folder of \apache-ActiveMQ-
5.5.1\conf.
The following steps are only required for IPv6, which are unnecessary for IPv4.
Open apache-activemq-5.5.1\conf\activemq.xml, and add the configuration of
<transportConnector name="openwire" uri="tcp://[::]:61616"/> under transportConnectors as
shown below.

5.2.4 Web Server Installation and Start-up

The web server could be either Tomcat or Jboss, so we will introduce the Tomcat and Jboss
installation and configurations as the following respectively.
Note: Before you start Loop-iNET web server, you must specify the memory for the web
server(MaxMemory≥2048M), otherwise, some functions may not work normally. For the
operation instructions, please refer to Appendix B Web Server Memory Modification.
5.2.4.1 Tomcat Sever Start-up
The Tomcat can be launched by performing the following steps:

Extract the Tomcat package in a folder.
Enter the directory of \apache-tomcat\bin, and double-click startup.bat to start up the Tomcat
server.
You will see the following screen. To stop Tomcat server, you just need to press Ctrl+C.
5.2.4.2 Jboss Sever Start-up
The startup of Jboss is quite different from Tomcat, which requires the following steps(Jboss v4.x
as an example):
Extract the Jboss package in a folder.
Open a command window and enter the directory of \jboss-4.2.3.GA\bin, as shown below.

Execute the command run.bat –b $IP Address$ to start up Jboss server. (Note: The IP address
of the machine is required, otherwise, it won’t be accessed by others)
To stop Jboss server, you just need to press Ctrl+C.
5.3 Server Configurations for Linux

Loop-iNET server can be also deployed on a Linux machine. Thus, we will give the configurations
instruction of the third-party software in this section. For the upgrade installation or modification,
just skip this section.
5.3.1 JDK Installation and Configuration
Here we take jdk-6u29-linux-i586-rpm.bin(32-bit) as an example to instruct you install and

configure it step by step.
Download the jdk-6u29-linux-i586-rpm.bin to a specific folder
Execute the following command chmod u+x jdk-6u29-linux-i586-rpm.bin and then execute the
following command ./ jdk-6u29-linux-i586-rpm.bin to install JDK.
When you see the word Done, it indicates the installation is completed. Then close the command
shell.
Open/etc/profile, and add the following to the end:

export JAVA_HOME=/usr/java/jdk1.6.0_29
export PATH=$JAVA_HOME/bin:$PATH
Reboot the system to make all settings take effect.
5.3.2 MYSQL Database Installation and Configuration
Here we take MYSQL v5.5 as an example.
Download the MYSQL server and client package from MYSQL website.
Double-click the installation package of MYSQL server, you will see the following screen. Click
Apply to continue.

Click Install Anyway if you encounter the following screen. If not, please skip to the next step.
When you see the following screen, click OK to complete the installation.
After that, double-click the installation package of MYSQL client, and repeat above steps to
install it.
Make sure the my.cnf file is located under /etc/. If not, please copy my-medium.cnf file from
/usr/share/mysql/ to /etc/, and rename it as my.cnf.
Open /etc/rc.d/init.d/mysql, and modify

basedir=/usr
datadir=/var/lib/mysql
Moreover, you need to perform the following to make sure MYSQL will work normally.
Click System/Management/Service to make sure mysql has been started up, as shown in the
sample screen below.

Click System/Management/Security Level and Firewall, and add port 3306 into the Trusted
Ports, as shown in the sample screen below.
5.3.2.1 Enable Remote Access to MYSQL Database Server
Besides, you need to enable the remote access by performing the following steps.
Open a command line, and log in with root privilege, as shown below.
a. Log in the MYSQL without a root password.
b. Log in the MYSQL with a root password.
Execute the command of use mysql;
To enable the remote access for the root users, please execute the command of UPDATE user
SET host = '%' WHERE user = 'root' and host = '127.0.0.1';

To grant all privileges onto the root users, please execute the command of GRANT ALL
PRIVILEGES ON *.* TO 'root'@'%' WITH GRANT OPTION;
Execute the command of UPDATE user SET Password = PASSWORD('admin') WHERE user
= 'root';. This step is to set the password for the root user, in this example, we set it as admin,
but you can change it as you want. However, please remember it or write it down, because it will
be needed during the Loop-iNET installation.
Execute the command of FLUSH PRIVILEGES; to make the setting take effect, and exit the
terminal.
5.3.3 ActiveMQ Server Installation and Start-up
Note: Please make sure you have installed JDK before installing ActiveMQ server.
The ActiveMQ server can be launched by performing the following steps(ActiveMQ v5.x as an
example):
Extract apache-activemq-5.5.1-bin.tar.gz in a folder, here we extract it under usr/local.

Open a terminal in usr/local/apache-ActiveMQ-5.5.1/bin and execute the following command

of ./ActiveMQ console to start up the ActiveMQ server. A sample screen is shown as below.
Click System/Management/Security Level and Firewall, and add port 61616(the default value)
into the Trusted Ports, as shown in the sample screen below.
Note: The initial username and password for ActiveMQ is system and manager respectively.
Please remember it or write it down, because it will be needed during the Loop-iNET installation.
However, you could modify it in credentials.properties under the folder of /conf.
5.3.4 Web Server Installation and Start-up

The web server could be either Tomcat or Jboss, so we will introduce the Tomcat and Jboss
installation and configurations as the following respectively.
5.3.4.1 Tomcat Sever Start-up
The Tomcat can be launched by performing the following steps(Tomcat v6.x as an example):
Download the Tomcat package and decompile it to a specific folder(/var for example)
Enter /var/tomcat6/bin/, and execute the command of ./catalina.sh run to start up the Tomcat
server.

To stop Tomcat, you just need to press Ctrl+C.
5.3.4.2 Jboss Sever Start-up
The Jboss can be launched by performing the following steps(Jboss v4.x as an example):
Download the Jboss package and decompile it to a specific folder(/var for example)
Enter /var/jboss4/bin/, and execute the command of run.sh –b $IP Address$ to start up the
Jboss server.
Chapter 6 - Loop-iNET Server Installation
To stop Jboss, you just need to press Ctrl+C.

6.4 Loop-iNET Server Installation Instructions for Windows
6.4.1 New Installation

For the first installation of Loop-iNET server, you need to install and configure the required third-
party software, including JDK, MYSQL, ActiveMQ and Web Server (Tomcat/Jboss). For the
upgrade installation or modification, just skip this section. Please refer to Section 3.2 Server
Configuration for Windows for the installation and configuration of the mentioned third-party
software.
Note: Prior to Loop-iNET server installation, please make sure you have started up the ActiveMQ
server and MYSQL server. This is not an installation step but must be performed prior to
installation.
Click the drive containing the Loop-iNET Installation CD, and click Loop-iNET Setup. Wait
patiently when the following window pops up.
Choose the language displayed on Loop-iNET system, click OK to continue.

Input the serial number provided by the vendor in the following screen, and click Next to continue.
It will be needed to generate license file later, so please keep it well.
Click Next to continue, or click Previous to get back to the last screen.
Click Next by selecting I accept the terms of the License Agreement.

Select the components you want to install and click Next. For the function of each component,
please refer to Chapter 2.3.
Click Next to install the program in the default directory, or click Choose to modify the destination
folder.
Choose where to create the program icons, and click Next to continue.
Follow the example given on the screen to select the server path, and then click Next.

a. If you are using Tomcat server, please select the directory of \webapps under the Tomcat
installation folder.
b. If you are using Jboss server, please select the directory of \server\default\deploy under the
Jboss installation folder.
Input the related information of the MYSQL Server as shown below, and click Next to continue. If
you use IPv6, please input the IP address of IPv6 format, such as ::192.168.0.90, ::::c0a8:05A,
etc.
Enter the required information of ActiveMQ server and click Next. If you use IPv6, please input
the IP address of IPv6 format, such as ::192.168.0.90, ::::c0a8:05A, etc.
Note: Please make sure you have started up the ActiveMQ server. The initial username and
password for ActiveMQ is system and manager respectively. However, you could modify it in
credentials.properties under the folder of \apache-ActiveMQ-5.5.1\config.

Confirm the settings and click Install to launch the installation. Or you can click Previous to
modify the settings.
Please wait before the installation completes.

Click OK when you see the following screen.

You will see the popup message as shown below, please click OK and Done. And then reboot
your system to complete the installation manually.
Your installation is now complete. Chapter 7 will explain how to open Loop-iNET on your client
workstation and create the Loop-iNET working environment.
6.4.2 Upgrade Installation
Note: Upgrade requires official license with valid SMA(Software Maintenance Agreement)
purchased. For more detail about the service description, please refer to Loop-iNET Brochure.
Prior to the upgrade installation, please clear the cache of your browser, and make sure the
ActiveMQ and MYSQL are started up. Otherwise, the installation might fail.
If you wish to upgrade to the newer version of Loop-iNET, please double-click the *.exe. You will
see the following screen. Click Yes to proceed, or click No to quit.
Confirm the information and click Install button to launch the upgrade installation.
Wait patiently when the program executes the installation.

Click OK and Done to exit the installation procedure.
6.4.3 Modification
If you need to add, remove or repair the program, please click on the Start/All Programs/Loop-
iNET/Change Loop-iNET Installation.
Add Features
When you see the following screen, click Add Features to add more component(s), and then
click Next.

Click Next to continue, or click Cancel to exit the modification procedure.
Select the components you want to add from the list, and click Next to continue.

Click Done to quit the installation procedure.

Remove Features
When you see the following screen, click Remove Features to remove some component(s) from
your computer, and then click Next.

Deselect the component(s) you want to remove, and click Uninstall.

Wait patiently when the program uninstalls the target components.
When you see the following screen, please click Done to exit.

Repair Product
When you see the following screen, click Repair Product to fix some issues for your Loop-iNET
system, and then click Next.
Click Install to continue, or click Cancel to exit the modification procedure.

Wait patiently when the Loop-iNET program is being repaired.

When you see the following screen, click Done to exit the repair procedure.
6.4.4 Uninstall
If you want to uninstall Loop-iNET program, please click on the Start/All Programs/Loop-
iNET/Change Loop-iNET Installation.
When you see the following screen, click Uninstall Product to remove the entire Loop-iNET

Click Next to uninstall Loop-iNET system, or click Cancel to exit.
Wait patiently when program is collecting information.

Click OK to continue the uninstall when you see the popup hint.

Click Done to complete the uninstall procedure and exit.
Please go to Installation and Uninstall section in Appendix C: Frequently Asked Questions

to find the solutions to some common problems you may encounter during the installation and
uninstall.
6.5 Loop-iNET Server Installation Instructions for Linux
6.5.1 New Installation
Note: Prior to Loop-iNET server installation, please make sure you have started up the ActiveMQ
server and MYSQL server(The remote access privilege should be set). This is not an installation
step but must be performed prior to installation.
Right-click on the Setup.bin, and select Properties, as shown in the Figure below.
Go to Permission option, and select the checkbox of Allow executing file as program.
Double-click the Setup.bin, and select Run in Terminal, as shown below.
Input the serial number provided by the vendor in the following screen, and click Next to continue.

Click Next to continue, or click Previous to get back to the last screen.
Click Next by selecting I accept the terms of the License Agreement.

Select the components you want to install and click Next. For the function of each component,
please refer to Chapter 2.2.3.

Click Next to install the program in the default directory, or click Change to modify the destination
folder.
Choose where to create the program icons, and click Next to continue.
Follow the example given on the screen to select the server path, and then click Next.

a. If you are using Tomcat server, please select the directory of \webapps under the Tomcat
installation folder.
b. If you are using Jboss server, please select the directory of \server\default\deploy under the
Jboss installation folder.
Input the related information of the MYSQL Server as shown below, and click Next to continue.
Enter the required information of ActiveMQ server and click Next.

Note: Please make sure you have started up the ActiveMQ server. The initial username and
password for ActiveMQ is system and manager respectively. However, you could modify it in
credentials.properties under the folder of /config.
Click OK when you see the following screen.

You will see the popup message as shown below, please click OK and Done, and then reboot
Your installation is now complete. Chapter 4 will explain how to open Loop-iNET on your client
workstation and create the Loop-iNET working environment.
6.5.2 Upgrade Installation
Note: Prior to the upgrade installation, please clear the cache of your browser, and make sure the
ActiveMQ and MYSQL are started up. Otherwise, the installation might fail.
If you wish to upgrade to the newer version of Loop-iNET, please double-click Setup.bin. You will
see the following screen. Double-click the Setup.bin, and select Run in Terminal, as shown
below.

Click Yes to proceed, or click No to quit.
Confirm the information and click Install button to launch the upgrade installation.
Wait patiently when the program executes the installation.

Click OK and Done to exit the installation procedure.

6.5.3 Modification
If you need to add, remove or repair the program, please enter the Loop-iNET installation folder
and run Change Loop-iNET Installation.
Add Features
When you see the following screen, click Add Features to add more component(s), and then
click Next.
Select the components you want to add from the list, and click Next to continue.

Click Done to quit the installation procedure.

Remove Features
When you see the following screen, click Remove Features to remove some component(s) from
your computer, and then click Next.

Deselect the component(s) you want to remove, and click Uninstall.
Wait patiently when the program uninstalls the target components.

When you see the following screen, please click Done to exit.
Repair Product
When you see the following screen, click Repair Product to fix some issues for your Loop-iNET

Wait patiently when the Loop-iNET program is being repaired.
When you see the following screen, click Done to exit the repair procedure.

6.5.4 Uninstall
If you want to uninstall Loop-iNET program, please find Change Loop-iNET Installation and
double-click on it.
When you see the following screen, click Uninstall Product to remove the entire Loop-iNET
Click Next to uninstall Loop-iNET system, or click Cancel to exit.
Wait patiently when program is collecting information.

Click OK when you see the following hint.
Click Done to exit the uninstall procedure.

Please go to Installation and Uninstall section in Appendix C: Frequently Asked Questions

to find the solutions to some common problems you may encounter during the installation and
uninstall.

Part III –Startup & Provisioning
Chapter 7 - Launching the Loop-iNET Application

Now that the installation is complete, you‟re ready to open Loop-iNET, build your network into the
system and add some users on Loop-iNET system.

After you complete the installation, you need to manually start up the Loop-iNET components to
make Loop-iNET work. This chapter will instruct you to launch the Loop-iNET applications step by
step.
7.1 Launching Loop-iNET

The Loop-iNET can be launched by performing the following steps:
1. Start up the ActiveMQ and then the web server (Tomcat or Jboss). For how to start
up them, please refer to the respective section under Chapter 5 based on different
operating systems.
2. Double-click the Loop-iNET Start Daemon All icon on the desktop to start up all
system components.
3. Wait patiently before all components are started up.
7.2 Registering Loop-iNET License

Note: Prior to using Loop-iNET features, you need to register license with the serial number
provided by the vendor, which has been used during the Loop-iNET installation. If the serial
number is lost, please consult the sales representative or the vendor.
The Loop-iNET software gives you a 7-day period, for which the data can‟t be reused on the
reinstalled system. However, you can contact Loop sales representatives to apply for a 90-day
trial license, for which the data can be reused if you apply for another 90-day trial period. It is
suggested purchasing the official license before the expired date to prevent data loss on Loop-
iNET system. For more details about the license, please contact Loop sales representative.
Loop-iNET provides a default account for the administrator to log into the system to register
license, create new users and assign privileges. The initial username and password are both
admin, but the password can be changed by the user.
To register the license, please do the following:
Note: Loop-iNET only supports Firefox and IE11 for now. If you use other browsers to access
Loop-iNET, you will see the following screen, and Loop-iNET system might not work properly.

Open your browser and access http://server IP address:8080/inet/ to enter Loop-iNET by

inputting the admin account.
You will access the License Manager screen automatically as shown in the following screen.
Input the required information, and then click Save Registration Code shown at the lower right.
A window will prompt you to save the *.urg file. If it is the first time for you to use Loop-iNET, you
can choose OK to save it into a local folder, and then send it to Loop to generate an official
license. However, if you choose Cancel in the popup window, the program will still give you a 7-
day free using period.
If you use a trial version of Loop-iNET system, the (Trial) will be shown on the upper left as below,
which will be gone after you get registered with an official license.

For more information about License Manager, please see Chapter of License Manager.
With admin account, you can also use Organization, Policy, Database & File Maintenance
features. For how to use these features, please refer to the instructions under corresponding
sections.
7.3 Creating Loop-iNET Accounts

Login with the admin account again to create Loop-iNET users and assign privileges to each user.
For how to create Loop-iNET Accounts, please refer to Section Adding a New Group and
Adding a New User under Chapter Security Manager.
7.4 Authenticating Loop-iNET Components

Once the Loop-iNET user is created, the user needs to login to authenticate the Loop-iNET
components before accessing the powerful features. For the first time to log into Loop-iNET
system, you are required to set a new password for security as prompted below.
To authenticate the Loop-iNET components, please do the following:

Access http://server IP address:8080/inet/ and login with the account created by the administrator.
If you entered the wrong username or password, you will be prompted to enter a correct one. If
you have tried for ten times, your account will be locked for 24 hours. Also, you can contact the
administrator if you want to unlock your account immediately.
If you have entered the wrong password for ten times, you will see the following screen.

When you access the Loop-iNET program as shown below, click iNET START/System/System
Monitor.
In the System Monitor screen, right-click on each component and select Authorize option.
Loop-iNET consists of the following components, as explained below.

 System Component Management Server (SCMS) – It manages all other system

components like a central server.
 Web-Based Graphic User Interface (Web-GUI) – It provides friendly user interfaces for the
user, so the user performs all operations via this component.
 Scan Daemon (SD) – It clears the alarms regularly based on the user settings and
determines whether Loop-iNET system will send out notification mail to the related personnel.
 Polling Agent (PA) – It is responsible for polling the devices through SNMP protocol.
 Trap Receiver (TR) – It receives the traps sent from the device.
 Configure Daemon (CD) –It transmits the data between the Loop-iNET system and the NE.
 Common Service Daemon (CSD) – It provides common services, such as NTP service.
 Notification (NF) –It sends the alarm notifications to the related personnel.
 Event Daemon (ED) – It processes events and produce alarms based on the event filter
settings of Loop-iNET system.
 Resource Daemon (RD) – It gathers the information of the resources within Loop-iNET
system, including the device type, firmware version, CAAS and serial No.
 NE Panel Daemon (NPD) – It processes the NE panel data, which will be presented on the
interface.
 Diagnostic Damon (DD) – It diagnoses the telecommunications network which comprises of
TDM/IP.
 NE Business Damon (NBD) – It processes the logical operation between Multi-NEs.
Then the Authorized column will become Yes, and the Status column will become Working, as
shown below.
For more information about System Monitor, please refer to Chapter of System Monitor.
Now that all Loop-iNET components are authenticated, you‟re ready to open Loop-iNET, build
your network into the system and learn some basic information about the Loop-iNET features.
If any of Loop-iNET components are unauthorized or unregistered, the below window will popup
when you use Admin account login the system. The below screen list the missing component and
the missing reason.
Chapter 8 - DR Site Manager
*Note: Only when you use Admin account login the system will prompt this message.

Loop-iNET Site Manager allows you to manage all your Loop-iNET sites. It is available for single-
site structure and Disaster Recovery (DR) structure. You can monitor and know the Loop-iNET
site status with five operational states, Working, Standby, Running With Fault, Standby With
Fault and Unknown.
In DR structure, you can switch the services from one site to another site to have data integrity
and resume the services when one site is crashed. In addition, in this mode, only one site is
working at a time. When the state of the one site server is working, the state of the other site
server should be standby, and vice versa.
To access this feature, please click iNET START/Site Manager.

8.1 Single Site
8.1.1 Site Status
Clicking Site Status, you could know the current status of the site as seen in Figure below, in
which the protection mode is “None”.
As for the further explanation of site information, please refer to the next topic, Site Provisioning.
8.1.2 Site Provisioning

When you switch to Site Provisioning, you may set
In this screen, you can change the blue items of site provisioning, including iNET Site Name,
Polling Interval(s), Retries, and Actions. Other columns are to provide site information for your
reference.
 iNET Site Name – The setting of iNET Site Name depends on your convenience and
preference.
 Polling Interval(s) – Set the polling interval(30~5000 seconds), which is 300 seconds by
default.
 Retries – Set the retry times(1~10), which is 2 by default.
 Actions –It provides Activate/Deactivate options for you to activate/deactivate the site.
After modifying, you can click on the “Apply” button which is on the bottom of the screen.
8.1.2 Operational Switch

It only takes effect under Warm Standby of Disaster Recovery structure.
8.2 Disaster Recovery(Optional)

* Note: This feature is optional which requires additional charge. For more details about the
charge, please refer to the brochure or contact the sales representative.
The DR structure of Loop-iNET Site Manager assumes that the multiple suites of servers need to
be constructed at different sites.
Please also pay attention to the following points when using iNET Disaster Recovery(DR) service:
1. It requires installing the program of the same version and language.
2. For iNET Disaster Recovery between formal versions, NEs supported by either site can be
shared among the sites.
3. For iNET Disaster Recovery between formal version and trial version, NEs supported by
either site can be only used on the corresponding site.
8.2.1 Site Status

Clicking Site Status, you could know the current status of both sites as seen in Figure below.
As for the further explanation of site information, please refer to the next topic, Site Provisioning.
8.2.2 Site Provisioning

You can click Site Provisioning option to change the settings of the local site and the remote site
at the same time. Also you can modify the blue columns upon your demands, which are
introduced as below. Note that you have to deactivate the site before you change the settings.

 Location – The Local and the Remote sites are relative according to the entry which users
choose.
 iNET Site Role –You may set the Site Role from Primary to Quaternary. The role for each
site under a DR group must be unique.
 iNET Site Name – The setting of iNET Site Name depends on your convenience and
preference.
 Admin State– It is the management condition of the Loop-iNET service. It can be
distinguished into two states. Notice that Admin State shall be changed from Deactivated to
Activated in order to use Disaster Recovery service.
 Operation State –To switch between Working and Standby, it should be operated under
Warm Standby mode in the next menu option, Operational Switching.
It can be differentiated into five states, Working, Standby, Working With Faults, Standby
With Faults and Unknown:
i. Working means the site is in working status.
ii. Standby represents the site is in standby status to protect the working site.
iii. Working With Fault will be displayed when one of the following situations occurs.
a. When some errors occur on daemons of the local site, the Operation State of
Local Site will be displayed as Working With Fault.
b. When the Protection Mode of Local and Remote Sites are both in Working status,
the Operation State of Remote Site will be displayed as Working With Fault.
iv. Standby With Fault will be displayed when one of the following situations occurs.
a. When full synchronization is running between the Sites.
b. When full synchronization between the Sites fails.
c. When there are some errors in component status.
d. When the components on Working site are mismatching.
v. When you see the Operational State shows as Unknown, you need to contact your
administrator to make sure if this is caused by a complete site failure.
 Protection Mode – It provides the options of None, Warm Standby and Hot Standby.
Please select one based on your specific demands. The Protection Mode under a DR
group must be the same, which should be all Warm Standby/Hot Standby.
i. None indicates the site is running independently.
ii. Warm Standby requires manual switching to working status in case of disaster on
protected site. The section below will give an example on how to use Warm
Standby for your reference.
iii. Hot Standby switches to working status automatically in case of disaster on protected
site. Note that the switching time is approximately the seconds of (Retries+1)
multiplying Polling Interval. After that, you need to wait patiently before the
daemons are started up. For more information about Hot Standby, please refer to
Instance for Hot Standby section.

 Polling Interval(s) – Set the polling interval(30~5000 seconds), which is 300 seconds by
default.
 Retries – Set the retry times(1~10), which is 2 by default.
 Message Server IP – It should be determined by the system automatically and cannot be
changed through this GUI.
 DB Server IP –It should be determined by the system automatically and cannot be changed
through this GUI.
 Switching Priority – Switching Priority(0~9999) only works for Hot Standby. The smaller
number indicates higher switching priority.
 Remark –The setting of Remark depends on your convenience and preference.
 Actions –It provides Activate/Deactivate options, and also allows you to delete the remote
site.
8.2.3 Operational Switching

This option only takes effect under Warm Standby mode. You can click Operational Switching
to do the protection switching under Switch To. See figure below. Note that there can only be
one Working site under a DR group, all other sites should be set as Standby.
8.2.4 Instance for Warm Standby

Warm Standby requires manual switching to working status in case of disaster on protected site,
so below will give an example how to use Warm Standby for the user‟s reference.
At first, you need to add remote site(s) first by following the instructions below prior to operation.
Go to Site Provisioning, click Add Remote Site on upper right. The following screen will pop up.
Please input the IP address, username and password (system and manager by default) of the
target message server and click OK button to confirm the setting. You could also use Test
Connection on lower left.

After successfully added a remote site, you are required to do the same settings on the remote
server, as prompted by the message below. Upon successful settings, you will see local and
remote sites as introduced in the sections below.
Log into the remote site, click iNET START/Site Manager, go to Remote Site Authorize
Request. Below is a sample screen.
Check the information of Remote Site Authorize Request, and click Accept/Reject upon
demands.
Once the request is accepted, either site will show both the local and remote sites, as shown
below. Note that you have to deactivate the site first under Site Provisioning before you change
the settings.
Once the site is deactivated, you will be log out automatically. After 10 seconds or so, re-log in
the deactivated site and enter Site Manager to change the Protection Mode as Warm Standby
and click Apply to save the settings.

Repeat the above steps to change into Warm Standby Protection Mode for the Remote Site.
Then you will see the following screen.
Activate both sites by clicking Activate option under Actions.

Go to Operational Switching, choose one site as Working site, keep the other site as Standby.
After you switch the status, you will be log out automatically. After 10 seconds or so, re-log in the
site and enter Site Manager. Below is a sample screen.

Until now, both sites are under Warm Standby Protection Mode. It means the Working site is
protected by the Standby site. In case of any disaster or fault on the Working site, you can
switch the standby site as working manually. Also you may modify the blue columns upon your
demands for the protection, such as Polling Interval and Retry, which are introduced in the
section of Site Provisioning.
If you need to further set the primary site as “Working” operational state, and secondary site as
“Standby” operational state, please go to Recover Operational State on Primary Site.
8.2.5 Instance for Hot Standby
Under Hot Standby mode, the secondary site will switch to Working automatically in case of
disaster on protected site. Below is a sample screen which is a view from the secondary site
under normal operation.
In case the primary site is down, the above interface will change into the following.
The secondary site will switch to Working operation state automatically, as shown below.
After the primary site is recovered, user will see the following screen, in which the secondary site
is Working, while the primary site is considered Working With Fault.

At the same time, we access Site Manager from the primary site, as shown below, in which the
primary site is Working, while the secondary site is considered Working With Fault.
If you need to further set the primary site as Working operational state, and secondary site as
“Standby” operational state, please keep reading the section below.
8.2.5.1 Recover Operational State on Primary Site

Before recovering Working operation state on primary site, please note that it is divided into two
cases. Please refer to either to meet your specific demands.
Case a
If you don‟t need to synchronize the data from the secondary site to the primary site, please
follow the instructions below.
Deactivate the secondary site on the primary site, as shown below.
Re-activate the secondary site, then its “Operation State” will be listed as Standby With Fault.
After a few minutes, normal operational state is restored, in which the primary site is “Working”,
while the secondary site is “Standby”.

Case b
To ensure data integrity, you may need to synchronize the data from the secondary site to the
primary site. In this case, please follow the instructions below.
Deactivate and re-activate the primary site to make it Standby, as shown below.
Deactivate the secondary site after the data synchronization is completed.

And then re-activate the secondary site, it will be in Standby Operation State. As shown below,
the primary site is “Working”, while the secondary site is “Standby” as you expect.

Part IV – System Maintenance
Chapter 9 - Security Management

This part instructs the Loop-iNET system maintenance for more efficient network management,
including Security Management, System Monitor, Data Backup, Restore and Deletion, and so on.

Loop-iNET prevents unauthorized users from logging into your network management system or
exceeding authority operation. The system performs validity checking and controls operational
privilege for users. The security management module is mainly used to record the system and
access logs, manage users, user groups and define security policies for the users in network
management system.
9.1 User Manager

To access the User Management interface of Security Management, click iNET START/Security/
User Manager.
9.1.1 Adding a New Group
To create a Loop-iNET user, you must create Groups first:
Access http://server IP address:8080/inet/ and login with the admin account.

Click iNET START on the left bottom and go to Security/User Manager.
Go to Group tab, click Add option on the upper right, or select Add Group among the right-
clicking options.

Input the required information, including the Group Name and Group Type. Generally, you need
to create a Resource Group and a Function Group respectively. If Active option is selected, the
group to be created will be in working status immediately. Also, you can enter some remarks for
this group.
Click OK button after you confirm the information you have entered.
After you create the Function Group and Resource Group, you need to assign Loop-iNET
features for Function Group that can be accessed by the users under that group, and assign
resources for Resource Group that can be managed by the users under that group.
For Function Group, you need to click Privilege option on the upper right, or select Privilege
among the right-clicking options. Make the selections and click OK button. You can also click the
Copy from button and select a group from the list, to copy the privileges of that group easily. For
more details about these functions, please refer to the sections below.
Note: If you want to deselect one sub-item under a privilege tree, you could press Ctrl key and
click on the text after the checkbox. In the sample screen above, we deselect the Edit function
under DME by pressing Ctrl key and clicking on Edit.

For Resource Group, you need to click Privilege option on the upper right, or select Privilege
among the right-clicking options. Make the selections and click OK button. If there are no
resources in the Loop-iNET network, you need to add some into Loop-iNET first.
9.1.2 Adding a New User
After you complete creating the groups, you can create some Loop-iNET users under User tab:
Go to User tab, click Add option on the upper right, or select Add User among the right-clicking
options.
You are required to fill in the field marked with asterisk, including Username, Password,
Function Group and Resource Group. Please note that the password is case sensitive, while
the username is not. You can also set the following parameters for it, but they are not mandatory.
 Account expiration time- the Loop-iNET system will verify the account regularly. If this filed
is filled, the account will be unavailable after the specified date.
 Password has expired and must be changed(check for yes) - the Loop-iNET system will
verify the login password regularly. Once the password is expired, the old password can‟t
access the Loop-iNET system any more.
 Active option – once it is selected, the user to be created will be in active status
immediately.
 Binding IP – this filed is to restrict the user logging into Loop-iNET system only at the IP
addresses listed here.
 Optional – selecting option, you can enter more specific information for this user, such as
real name, organization, etc.

Click OK button after you confirm the information you have entered.
For more information about User Manager, please refer to Chapter of User Manager.
9.1.3 Querying Users/Groups
If no value is input in the query conditions, you will see the details of all users and groups.
However, you can limit the display results by specifying some query conditions and clicking
Query. For example, you need to view the users under a function group, you just need to select
that group under Function Group field and click Query. For other query conditions under User
tab and Group tab, the operation procedure is almost the same. Below is a sample screen to
query based on the condition of function group.
After that, you can click Revert button to clear the condition, and click Query button again, it will
display all users again.
9.1.4 Available Options for User
 Add – It allows you to add more users into Loop-iNET network. For how to add a user,
please refer to section of Adding a New User.
 Edit – Select a user and click on Edit button to modify the user‟s properties.
 Delete – Select a user and click on Delete button to remove the user from Loop-iNET
system.
 Activate/Deactivate – Right-click on a user and select Activate or Deactivate option to
enable or disable this user.
 Unlock – If the user entered the wrong password for ten times, the account will be locked
and shown as red here. In this case, you need to right-click on that user and press the
Unlock button shown on the right below.
9.1.5 Available Options for Group
 Add – It allows you to add new groups into Loop-iNET network. For how to add a group,
please refer to section of Creating a New Group.
 Edit – Select a group and click on Edit button to modify the group‟s properties, including the
name, type, active status and remarks.
 Delete – Select a group and click on Delete button to remove the group from Loop-iNET
system. Note that if there are some users under that group, you will be unable to delete the
group.
 Activate/Deactivate – Right-click on a group and select Activate or Deactivate option to
enable or disable this group.
 Privilege –Select a group and click on Privilege button to view or modify the function or

resource privileges for a group.
9.2 System Logs

It traces and records all operations in the operation log. For more details, please refer to the
Loop-iNET Main Manual.
9.3 Policy
The Policy can be accessed by clicking iNET START/Security/Policy.
It allows you to define the security policies for the account within Loop-iNET system, including
Password expiration, Automatic account unlock, Account lockout, etc., as shown below.
Note: After you make the modifications, please don‟t forget to restart Web server to make the
modifications take effect.
To restart the web server, please log in with the Admin account, as shown below.
Click on the Reboot option to restart the web server, as shown below.
Click Yes to confirm the operation, then the web server will be restarted.

Chapter 10 - System Event/Alarm Query
Chapter 10 - System Event/Alarm Query

The administrator may query CAAS, Current Alarms and Historical Alarms related to Loop-iNET
system, which are detailed in the corresponding sections in Loop-iNET Main Manual.

Chapter 11 - Instructions for Changing IP Address of Loop-iNET Server
Chapter 11 - Instructions for Changing IP Address of Loop-

iNET Server
Please make sure Loop-iNET server is stopped, and perform the following steps to change the IP
address of Loop-iNET server:
Input the new IP address in proxoolconf.xml under

\Java\jdk1.6.0_29\jre\classes\inet\configuration\hibernate. A sample screen is shown as below.
Input the new IP address in activemq.properties under

Java\jdk1.6.0_29\jre\classes\inet\configuration\activemq. A sample screen is shown as below.
Locate the file of changeIP. bat(for Windows operating system)/changeIP.sh(for Linux operating
system) under the installation path of Loop-iNET, and double-click it to make the modification
take effect.
Lastly, access System Monitor to change the IP address of CSD components. Choose the IP
address in the IP drop-down list and press Apply.
Chapter 11 - Instructions for Changing IP Address of Loop-iNET Server

Chapter 12 - Instructions for IPv6 Support

If you already install the Loop-iNET system, you need to make some modifications on the
configurations of Loop-iNET as instructed below.
Open apache-activemq-5.5.1\conf\activemq.xml, and add the configuration of

<transportConnector name="openwire" uri="tcp://[::]:61616"/> under transportConnectors as
shown below.
Right-click My Computer/Manage, double-click Services and Applications/Services, and then

locate MYSQL. Find the directory after default file, as shown below.
Open that file and add the configuration of bind-address=:: under [mysqld], as shown below.
Open Java\jdk1.6.0_29\jre\classes\inet\configuration\activemq\activemq.properties, and

add the configuration of url=failover:(tcp://[::IP address]:61616) as shown below. The IP
address should be the computer installed with ActiveMQ.

Open Java\jdk1.6.0_29\jre\classes\inet\configuration\hibernate\proxoolconf.xml, and add

the configuration of <driver-url>jdbc:mysql://address=(protocol=tcp)(host=::IP
Address)(port=3306)/inet?useUnicode=true&characterEncoding=utf-8</driver-url> as
shown below. The IP address should be the computer installed with MYSQL.
a. For Tomcat web server, follow the steps below.

I. Open $tomcat_home$/conf/ server.xml
II. Locate the string <Connector port="8080" protocol="HTTP/1.1"
III. Add address="0:0:0:0:0:0:0:0" after above string
IV. Restart Tomcat to make the modification take effect. Below is a sample screen for the
modification.
b. For Jboss web server, execute the command of run -b [::IP Address] under \jboss-
4.2.3.GA\bin to start up the Jboss web server.
Finally, open your browser and access http://[::server IP address]:8080/inet/ to enter Loop-iNET.
In this way, Loop-iNET will support IPv6.
Chapter 13 - North Bound Interface(Optional)

This feature allows the user to view the alarm and inventory data from Loop-iNET server and
make some configurations on SNMPc, which is quite useful and convenient. Below are the
instructions for how to use this feature.
Note: This feature works with the SNMPc, so please make sure you have installed the Castle
Rock software and put the MIB file of iNET-Agent under the directory of \SNMPc Network
Manager\mibfiles.
Log into the SNMPc Management Console, go the toolbar, and click on Config/Mib Database. A
sample screen is shown as below.
Locate the inet-agent.mib and press Compile button. Wait patiently until the following screen
shows up.
Click OK and Done to close the window. Then add the Loop-iNET NBI component as a node into
SNMPc Management Console by following the instructions below.

Click the button shown on the upper right, you will access the following screen.
Name it in Label, and input the address of Loop-iNET NBI component in Address. A sample
screen is shown as below.
Go to the Access column, and set the Read/Write Community as public. And click OK to exit
the settings.
If your settings are correct and successful, the node of Loop-iNET Agent will turn green. A sample
screen is shown as below.
Find iNET Agent under MIB tree, and expand the sub items. You will see four options,
snmpConfigTable, alarmCAASTable, alarmQueueSummaryTable, InventoryTable and iNET-
Agent-Traps. A sample screen is shown as below.

 snmpConfigTable – View and set the configurations of SNMPc console, such as the Port,
Access, Community and Restart.
 AlarmCAASTable – View the CAAS information from Loop-iNET system.
 alarmQueueSummaryTable – View the traps from Loop-iNET system.
 InventoryTable – View the inventory information from Loop-iNET system.
 iNET-Agent-Traps – View the alarm information of iNET-Agent component.
Click on any of it and select the Loop-iNET Agent icon displaying on the screen. And then click
on Start Table, as marked in the screen below. Then you can view the query information
displaying on the main console of SNMPc. Below is a sample screen for querying CAAS
information.
Chapter 14 - System Management

14.1 System Monitor
Loop-iNET System Monitor provides system monitoring and maintenance feature to help the
network administrator know the accurate status of the whole system, including the Component,
Equipment and User. The table below lists the command lines under java.exe process in Task
Manager corresponding to the iNET components. In case Loop-iNET program is down, you may
check it out based on this table. For more details, please refer to the Loop-iNET Main Manual.
Component Name Command Line

CD java –jar CD. jar
CSD java –jar CSD. jar
DD java –jar DD. jar
ED java –jar ED. jar
NBD java –jar NBD. jar
NBI java –jar NBI. jar
NF java –jar NF. jar
NPD java –jar NPD. jar
PA java –jar PA. jar
RD java –jar RD. jar
SCMS java –jar SCMS. jar
SD java –jar SD. jar
TR java –jar TR. jar
GUI Installation Directory\tomcat \conf\
14.2 Organization
This feature helps you to classify the users clearly. After you add a new organization, you can
move the user to it.
To access the organization, please go to iNET START/System/Organization. Then you will see
the following screen.

If no value is input in the query conditions, you will see the results of all current login users.
However, you can limit the display results by specifying some query conditions as instructed in
System Monitor.
You can choose to add or delete an organization by clicking the correspondent buttons at the
right bottom.
14.3 Set Default Value

This feature allows you to set some properties for the resources and users that you will add to
Loop-iNET network. For more details, please refer to the Loop-iNET Main Manual.
14.4 Mail Server Configuration

It allows you to configure the mail server for notification.
In this page, you can set SMTP Server, SMTP Port, Account and Password for email notification
of event. After you complete your settings, you can click on Test Connection button at the
bottom to test if it works normally. If it works normally, you will the information as below.
14.5 License Manager

License Manager allows you to register license, backup, import and export License file.
To access the License Manager, please click iNET START/System/License Manager.

Since we have introduced how to complete License Registration in the Chapter of Launching the
Loop-iNET application, here we will focus on instructing backup, import and export of the license
file.
Click on Import & Export License File tab, you will see the following screen.
 License Backup – Click Export license file to save the license file into a specific directory
on your computer.
 License Import – If you have saved the license file by using Loop-iNET before, you can
import it back to Loop-iNET. You simply click button for the import process.
 License Export – Export the license file into a HTML file to view the details conveniently.
When you click on Import option, you will see the message as shown below. Please carefully
read the message and perform the operation as required before importing license.
Once you click Yes, you will see the following window to import license.

14.6 Cloud Disk

It is provided for the admin account to upload system files required by Loop-iNET. For more
information about it, please refer to section Cloud Disk in the main manual.
14.7 Database & File Maintenance

The purpose of this chapter is to provide guidelines for managing the Loop-iNET database.
Database management includes querying the backup & restoration tasks, occasionally backing
up (or saving) your database & file, restoring from a database& file backup, deleting an expired
database & file backup and remote backup.
14.7.1 Database Backup/Restore

To access this feature, please click iNET START/System/ DB&File Maintenance/Database
Backup/Restore.
14.7.1.1 Task Schedule
Querying Backup Tasks
If no value is input in the query conditions, you will see the all backup tasks. However, you can
limit the display results by specifying some query conditions and clicking Query. For example,
you need to view all one-time-only backups, you just need to select One Time Only under
Frequency field and click Query. For other query conditions, such as Name, Activation Status,
Running Status and Creator, the operation procedure is almost the same. Below is a sample
screen to query the one-time-only backups.

Adding a Backup Task
If you want to save your database and load it into a safe place, you need to click Add button
shown on the upper right. Then it will pop up the window as shown below.
You will have several options for backing up data. You can backup all of your database or just
part of it based on your specific needs. Each backup type is briefly explained as below.
 All - the backup contains all Loop-iNET data, including the system, user, equipments, etc.,
which may take a longer time.
 All Without Security - the backup contains all Loop-iNET data except for the user profile,
user group data, user access data, user function privilege data, user resource privilege data,
and information of subnet, link and equipment.
 Configuration - the backup contains the system default values, threshold settings,
scheduled maintenance tasks, alarm severity color settings, mail server settings, NTP
service settings and event filter data.
 Resource With Security - the backup contains equipment information, equipment status,
topology map data, user profile, organization, user groups, group member and group
privilege.
 Resource - the backup contains equipment information, equipment status and topology map
data.
 User - the backup contains organizations, users, user groups, group members and group
privilege.
 Log - the backup contains alarms, events, notifications, user access logs, reports and
statistics.
 Inventory - the backup contains all inventory information, including equipments, cards and
ports.
For the Execution Frequency Settings, you will have the options of Annual, Monthly, Weekly,
Daily and One time only.

Note: The annual backup will run on 1st, January automatically. For the monthly and weekly types,
you need to select the backup day.
You can also set a time for routinely backing up your database by clicking on the calendar as
marked in the screen below.
Note: If you select the option of Enable schedule, this backup task will be enabled, otherwise
you will need to enable this task manually.
At last, click OK to finish the settings. Then it will be added in the backup list. You can also opt to
execute the scheduled backup task immediately, or delete a certain backup task as you want. All
successful backup files will be saved in the folder of iNET/SCMS/DatabaseBackup under Loop-
iNET installation folder.
14.7.1.2 Backup Files(Current Version)
This feature shows the backup files of the current version, you can go to iNET START/About to
check the current version.
Querying Backup Files
If no value is input in the query conditions, you will see the all current version backup files.
However, you can limit the display results by specifying some query conditions and clicking
Query. For example, you need to view all backup files created by admin, you just need to enter
admin under Creator value and click Query. For other query conditions, such as File Name,
Backup Task and Last Restore By, the operation procedure is almost the same. Below is a
sample screen to query the backup files created by admin.
Check Files With Database
You can click this button to check the backup files with those saved on the database.
Restore
To restore from a database backup, please go to the Backup Files (Current Version) tab and
see the following instruction.
 Select an item from the list.

 Click Restore button at the upper right.
 It will prompt you if you want to restore from this file. Click Yes to continue the restoration
process.
Note: the restore operation will overwrite the data in Loop-iNET system, so please perform it
cautiously.

Reconstruct Backup File List
If you have created some backup files by using Loop-iNET before, you can reconstruct the
backup files saved on the database.
Note: If you wish to reinstall Loop-iNET system due to some reason, please copy the backup files
from iNET/SCMS/DatabaseBackup to a save place first, so that you can put them back to and
reconstruct them to restore after the reinstallation.
Please do the following to reconstruct the backup file list in the database:
 Click Reconstruct Backup File List button on the upper right

 Click Yes to confirm this operation. Then the system will reconstruct all backup files
automatically.
Delete
 Select an item from the list.

 Click Delete button at the upper right.
 Click Yes to confirm this operation. Then the file will be removed from the Loop-iNET
database server permanently. (Please do this cautiously because the deleted files will
disappear permanently and won‟t be retrieved again.)
14.7.1.3 Backup Files(History Version)
This feature shows the backup files of the historical version. The operation and buttons are
almost the same as that introduced in Backup Files(Current Version), so please refer to the
section above for more information.
14.7.2 Expiration Maintenance
It allows you to make schedules to clear up the expired data. To access Expiration Maintenance,
please click iNET START / System / DB&File Maintenance / Expiration Mainenance.
Scheduling Expired Data Maintenance
It is for checking whether the data in the database server is expired.

There are three options on the window you need to set – Execution Frequency Setting, Execution
Time & Active Status, Threshold Settings for Expired Data(Days).
 Execution Frequency Setting – Select the frequency you want to execution the
maintenance, Annual, Monthly, Weekly or Daily.
 Execution Time & Active Status – Specify the Execution Time by the format of HH: MM:SS,
and select whether to enable this maintenance task. If you deselect this option, this
maintenance task will be disabled, which means it won‟t work.
 Threshold Settings for Expired Data – Input the days remaining before the data become
expired.
Click OK to save the settings. Then Loop-iNET program will clear up the expired data as settings
in the schedule. You can also press Execute button to clear the expired data immediately.
Scheduling Backup File Maintenance
It is for checking whether the backup file in the database server is expired.

There are three options on the window you need to set as well – Execution Frequency Setting,
Execution Time & Active Status, Threshold Settings for Expired Data(Days).
 Execution Frequency Setting – Select the frequency you want to execution the
maintenance, Annual, Monthly, Weekly or Daily.
 Execution Time & Active Status – Specify the Execution Time by the format of HH: MM:SS,
and select whether to enable this maintenance task. If you deselect this option, this
maintenance task will be disabled, which means it won‟t work.
 Threshold Settings for Expired Data – Input the days remaining before the backup data
become expired for each backup type.
Click OK to save the settings. Then Loop-iNET program will clear up the expired data as settings
in the schedule. You can also press Execute All button to clear the expired data immediately.
14.7.3 DB Backup File Mirroring

DB Backup File Mirroring provides an extra layer of protection to your data to prevent data loss in
case of disaster. With this feature, all backup files will be also saved in the remote FTP Server set
by the user. It includes two setup options, Remote Mirror FTP Server, and Auto Mirroring to
Remote FTP Server, as shown below.
 Remote Mirror FTP Server – Set up the parameters of FTP server, including the Server IP,
Port, User Name, Password and Mirroring Frequency in minutes.
 Auto Mirroring to Remote FTP Server – Enable/Disable this option by selecting
Activated/Deactivated.
 Test Connection – After you set up the remote mirror FTP server, you may press the Test
Connection button to test whether the connection is normal.
 Manual sync to local – When you click the option on the upper right, the program will sync
the files to the local machine. However, after the sync operation, user needs to press Check
Files With Database button in Backup Files(Current/History Version) to make it take
effect. Please refer to Database Backup/Restore section for more information about
backup/restore.
14.8 Services
14.8.1 NTP Time Sync

From the point of view of network administration, the use of NTP has many advantages since it
permits the automatic synchronization of all connected machines. In other words, the
administrator does not have to go from machine to machine setting the local clock.
For how to sync time among the servers, please refer to the NTP Time Sync section in Loop-
iNET Main Manual.
14.8.2 Services Configuration

For how to configure services, including NTP and TFTP, please refer to the Services
Configuration section in Loop-iNET Main Manual.
14.9 Debugging File

To resolve the problem for you quickly and efficiently, we may need the log file located under the
installation directory for debugging. The table below lists the path locating the debugging file for
each component.
Component Name File Path

CD Installation Directory/iNET/SCMS/log/
CSD Installation Directory/iNET/CSD/log/
DD Installation Directory/iNET/DD/log/
ED Installation Directory/iNET/ED/log/
NBD Installation Directory/iNET/NBD/log/
NBI Installation Directory/iNET/NBI/log/
NF Installation Directory/iNET/NF/log/
NPD Installation Directory/iNET/NPD/log/
PA Installation Directory/iNET/PA/log/
RD Installation Directory/iNET/RD/log/
SCMS Installation Directory/iNET/SCMS/log/
SD Installation Directory/iNET/SD/log/
TR Installation Directory/iNET/TR/log/
GUI Installation Directory/ /tomcat/webapps/log
Part VI Appendices
0Appendix A Table of Loop-iNET System Alarm Events
Part VI Appendices
Appendix A Table of Loop-iNET System Alarm Events
Please see Appendix A in Loop-iNET Main Manual for more details.

Part VI Appendices
0Appendix B Web Server Memory Modification
Appendix B Web Server Memory Modification
1． Instructions for Parameter Setup

1.1 A configuration command instance: JAVA_OPTS=-Xms512m -Xmx1500m (Minimum memory
is 512M, maximum memory is 1500M)
1.2 –Xms stands for the minimum memory(MinMemory), -Xmx stands for maximum memory
(MaxMemory)
1.3 Equation for memory calculation:
a) If all components are installed on the same computer:
i. MaxMemory = Memory available for iNET * 60%;
ii. MinMemory = MaxMemory * 40%;
b) If only iNET Web Server is installed on this computer:
i. MaxMemory = Memory available for iNET;
ii. MinMemory = MaxMemory * 30%;
1.4 If the value of MaxMemory is smaller than 1024, MaxMemory is 1024(i.e., the minimum value
of MaxMemory is 1024）
2． Tomcat Memory Setup
2.1 For Windows

2.1.1 Enter the directory of apache-tomcat/bin/
2.1.2 Open the file of catalina.bat
2.1.3 Add the following command at the beginning: set JAVA_OPTS=-Xms512m -Xmx1500m
(Please refer to 1.3 for Equation)
2.1.4 Save the settings
2.1.5 Restart tomcat
2.2 For Linux/Uninx

2.1.1 Enter the directory of apache-tomcat/bin/
2.1.2 Open the file of catalina.bat
2.1.3 Add the following command at the beginning: AVA_OPTS="-Xms512m -Xmx1500m"
(Please refer to 1.3 for Calculation Equation) Note: You must keep the quotation marks.
2.1.5 Restart tomcat
3． Jboss Memory Setup
3.1 For Windows

3.1.1 Enter the directory of \jboss-4.2.3.GA\bin
3.1.2 Open the file of run.bat
3.1.3 Find the following commands:
3.1.4 Modify the value of -Xms and -Xmx in the second sentence. (Please refer to 1.3 for
Calculation Equation)
3.1.6 Restart Jboss
Part VI Appendices
0Appendix B Web Server Memory Modification
3.2 For Linux/Uninx

3.2.1 Enter the directory of \jboss-4.2.3.GA\bin
3.2.2 Open the file of run.conf
3.2.3 Find the following commands:
3.2.4 Modify the value of -Xms and -Xmx in the second sentence. (Please refer to 1.3 for
Calculation Equation)
3.2.6 Restart Jboss

Part VI Appendices
0Appendix C: Frequently Asked Questions
Appendix C: Frequently Asked Questions

1. Installation & Uninstall
1. Q. What should I do if I see the Java VM error message during the Loop-iNET installation?
A. When you encounter this error message during Loop-iNET installation, please check out the
following points:
1. JDK is installed correctly
2. JDK Environment Variable is set correctly. For more details about setting JDK Environment
Variable, please refer to section of JDK Installation and Configuration based on different
operating systems.
2. Q. What should I do if I see the MYSQL server connection error message during the
Loop-iNET installation?
following points:
1. MYSQL server is installed on the target computer.
2. MYSQL server is started up.
3. MYSQL root password you enter is correct,
4. MYSQL Environment Variable is set correctly. For more details about setting MYSQL
Environment Variable, please refer to section of MYSQL Database Installation and Configuration
based on different operating systems.
Part VI Appendices
3. Q. What should I do if I see the ActiveMQ server connection error message during the
Loop-iNET installation as shown below?
whether the ActiveMQ server is started up, and whether the information you enter is correct. For
more details about ActiveMQ server, please refer to section of ActiveMQ Server Installation and
Start-up based on different operating systems.
4. Q. How can I make sure the JDK is uninstalled completely?
A. When you uninstall JDK, you need to uninstall it from Control Panel first, and then delete all
files under the JDK installation directory manually. Otherwise, it may not work normally when you
reinstall it again.
5. Q. Does Loop-iNET system have a minimum resolution requirement?
A. Yes, Loop-iNET system requires a minimum screen resolution of 1024*768. Otherwise, it

might not work properly.
6. Q. How can I change the MYSQL password in Windows operating system?
A. There are two ways to change the MYSQL password:
a. Open a command line, execute the following commands
mysql -hlocalhost -uxx –pxx

use mysql;
update user set password=password("new_password") where user="root" and host="localhost";
b. Open a command line and execute the following commands:

Part VI Appendices
mysqladmin -hlocalhost -uroot -pold_password password new_password
7. Q. The below error message pops up when I uninstall Loop-iNET?
A. Please check the following two points:

a. Make sure MYSQL is started, which is required by the uninstall process.
b. Check the IP address of Loop-iNET, which shall be consistent with that in MYSQL database.
8. Q. What should I do if I fail to install/remove iNET ?
A. Please check the required third-party software is started up, including ActiveMQ and MYSQL.
Moreover, please confirm whether the network cable has been plugged to ensure successful
connection with MYSQL. With normal connection with ActiveMQ and MYSQL, you may
install/remove iNET successfully.
2. Maintenance
1. Q. Why I can’t start up the Loop-iNET Server?
A. Please check if the ActiveMQ, MYSQL, Web Server and all components of Loop-iNET Server
are started up. If you can‟t see the startup window of ActiveMQ, it means the ActiveMQ fails to be
started up. In this case, please do the following to make Loop-iNET server work normally.
Execute the command of apache-activemq-5.5.1\bin>activemq.bat(for Windows) or apache-

activemq-5.5.1\bin>activemq.sh(for Linux) to start up the ActiveMQ again. If it works, you can
re-start the Loop-iNET Server up. Below is a sample screen when the ActiveMQ is started up
successfully.
Part VI Appendices
If it prompts you “Address already in use”, as shown in the sample screen below, it indicates the
port of ActiveMQ is occupied. In this case, you need to continue the steps below.

Part VI Appendices
You can disable this service using the port of 61616 under the Computer Management. Or you
can just modify the ports of ActiveMQ and Loop-iNET Server by following the steps below.
1. Modify the port of ActiveMQ. Open apache-activemq-5.5.1\conf\activemq.xml, modify the

port and save it. A sample screen is shown as below. After modifying the port, you should
test if the ActiveMQ can be started up normally.
2. If the ActiveMQ can be started up normally, you can then modify the port of Loop-iNET
Server.
Part VI Appendices
Open Java\jdk1.6.0_25\jre\classes\inet\configuration\activemq\activemq.properties,
modify the port and save it. A sample screen is shown as below.
Note: The tools and components of Loop-iNET Server will use some ports as listed below. Please
make sure these ports are available, otherwise, Loop-iNET Server may not work normally.
Name Port
ActiveMQ 61616, 8161(Inbound Rules/Outbound Rules)
FTP 20, 21(Inbound Rules/Outbound Rules)
HTTP 80(Inbound Rules/Outbound Rules)
HTTP Proxy 23080(Inbound Rules/Outbound Rules)
JBoss 8080(Inbound Rules/Outbound Rules)
MySQL 3306(Inbound Rules/Outbound Rules)
NTP Server 123(Inbound Rules/Outbound Rules)
SNMP Port 161(Inbound Rules/Outbound Rules)
Telnet 23(Inbound Rules/Outbound Rules)
Telnet Proxy 23023(Inbound Rules/Outbound Rules)
TFTP 69(Inbound Rules/Outbound Rules)
Tomcat 8080, 8009, 8005, 8443(Inbound
Rules/Outbound Rules)
Trap Port 162((Inbound Rules Only)
Please set up the Inbound Rules/Outbound Rules in the screen below.

Part VI Appendices
2. Q. What should I do if I see the SVG plug-in error message?
A. Please find out the solution in the same section of the Loop-iNET Main Manual.
3. Q. Why can’t I use the telnet function in Loop-iNET?
4. Q. Can I access Loop-iNET system from Windows Server 2003 or 2008?
A. Yes, you can, but you need to remove or disable Internet Explorer Enhanced Security
Configuration (IE ESC) by performing the following steps.
a. Remove IE ESC on Windows Server 2003
1. Click Start/Control Panel/Add or Remove Programs.
2. Click Add/Remove Windows Components.
3. Scroll down and uncheck box for Internet Explorer Enhanced Security Configuration.
4. Click Next, and Finish on next page.
b. Disable IE ESC on Windows Server 2008

1. Close all instance of Internet Explorer.
2. Open Server Manager, and click Configure IE ESC.
3. Click Off radio button under Administrator and User, and click OK.
Finally, open your browser and access http://[::server IP address]:8080/inet/ to enter Loop-iNET.
5. Q. Why the DME shows Offline or New status in Loop-iNET system as shown below?
6. Q. Why Loop-iNET system display NTP port is occupied?
A. If you encounter this situation, please check the below two points:
1. Check whether the NTP serve is closed in operating system. Double-click the time icon at the
lower right of your computer, select Date and Time, enter Internet Time tab, click Change
settings, unchecked the box before Synchronize with an Internet time server on popup
window, then click OK to save the settings. A sample screen is shown as below.
Part VI Appendices
2. Check the settings of Windows Time Properties. Right-click My Computer, select Manager,
then double-click Services, you will see the Windows Time in the middle of this screen, double-
click Windows Time and a window will pop up, please change the Startup Type to Manual and
the Service status to Stop. A sample screen is shown as below.
7. Q. Why 3th-party plug-in is not able to install in some user’s PC?

Part VI Appendices
A. When you use IE browser to access Loop-iNET system, if your PC hasn‟t installed SVG plug-
in，but your IE browser hasn‟t prompt any installation information, please check the settings of
your IE browser. Open your IE browser, click Tools, choose Internet Options, then you will see
the below screen. Access to the Security tab, then click Custom level, a window will popup,
please setup your IE browser according to the red labeled options.

iNET-Installation, Startup & Maintenance Guide

Uploaded by

Document Informationclick to expand document informationiNET-Installation, Startup & Maintenance Guide

Document Informationclick to expand document information

Copyright:

Available Formats

iNET-Installation, Startup & Maintenance Guide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

iNET-Installation, Startup & Maintenance Guide

Uploaded by

Copyright:

Available Formats

Loop-iNET

Installation, Startup & Maintenance

LOOP TELECOMMUNICATION INTERNATIONAL, INC.

Part I Before Installation

Part II Installation of Loop-iNET

Part III Provisioning

Part IV Loop-iNET System Maintenance

Loop-iNET Intelligent Network Management System Page 1

8.2.3 Operational Switching ....................................................................................... 111

Loop-iNET Intelligent Network Management System Page 3

Part I Before Installation

Chapter 1 - Loop-iNET Deployment Architecture

Resource Event NE Panel

Resource Event Damon Notification System

Trap Receiver Polling Agent

iNET Server Web Browser

Chapter 2 - Loop-iNET System Architecture

Loop-iNET utilizes a browser/server distributed architecture based on industry standard platforms

2.1 Management Architecture

(Optional OSS LAYER )

SDH Third-Party SDH DME AN1

Loop-iNET Intelligent Network Management System Page 5

2.2 Software Architecture

Distributed Processing Platform

The Presentation Layer(Web-GUI) displays the Loop-iNET powerful functions in web-based

Database(Data Storage) stores the data of the entire system.

2.3 Loop-iNET System Components

 System Component Management Server (SCMS) – It manages all other system

Loop-iNET Intelligent Network Management System Page 7

Chapter 3 - Step-by-Step Guide

Comment or Chapter in the

Part II Installation & Uninstall

Chapter 5 - Server Configuration

5.2.1 JDK Installation and Configuration

Here we take jdk-6u29-windows-i586 as an example to explain. Double-click the *.exe file to

Loop-iNET Intelligent Network Management System Page 9

Click Next to continue.

Click Next to continue.

Click Next to proceed, or click Change to modify the installation directory.

Loop-iNET Intelligent Network Management System Page 11

Wait patiently when the installation is proceeding.

Click Finish to when you see the following screen.

Right-click My Computer and select Properties. Go to Advanced option and press

Loop-iNET Intelligent Network Management System Page 13

Loop-iNET Intelligent Network Management System Page 15

5.2.2 MYSQL Database Installation and Configuration

Loop-iNET Intelligent Network Management System Page 17

Click Next to install the type of Developer Default.

When you return to the screen below, click Next.

Confirm the settings, and click Execute.

When the products are being installed, please wait patiently.

Loop-iNET Intelligent Network Management System Page 19

Click Next to continue.

Click Next to continue.

Loop-iNET Intelligent Network Management System Page 21

Click Next when the configuration of MYSQL server is completed.

Click Next when the configuration of Samples and Example is completed.

Click Finish to exit the installation.