3.1 Overview of Set-up
Once the NMS Server is installed and running, it will monitor registered iPECS systems and be available to service NMS clients, and Web browsers. After initial installation, check the
Windows Service status (Section 3.2), and configuration of the following:
• NMS Management Functions (Section 4.1, NMS Server Management) • NMS Users and Authority (Section 4.2, User Accounts Management) • Register iPECS Systems for services (Section 4.3, System Management)
3.2 Checking Windows Service Status
In order for iPECS-NMS to execute properly, verify that Apache HTTP Server, PostgreSQL Database Server, and iPECS-NMS are all running as Windows Services. These Windows services may start automatically when the server is restarted, or may be manually controlled using the Windows Administrative Tools for Services:
From the Windows Control Panel, double-click on Administrative Tools.
Next double-click on Services in the list of available tools.
Within the Services window, check or modify the status of services (ex., in this image, the Apache 2.2 service is in ‘Started’ status, and Startup Type is
‘Automatic’). Using the ‘Properties’ of a specific Service (right-click on a Service), the Startup Type
33
NOTE—The status of the iPECS NMS service also can be checked and changed using the iPECS- NMS Control program (refer to iPECS-NMS Software Package Installation).
3.3 Accessing the iPECS NMS Server Using a Web Browser
iPECS NMS is a Web based application using a Web Browser as the NMS client. Opening your browser and pointing it to the iPECS NMS server automatically opens the NMS client. For optimum performance, use a broadband connection and set the Tools>Internet
Options>Temporary Internet Files>Settings or >Browsing History>Settings (depending on your browser version) to ‘Check for newer versions of stored pages,’ select ‘Automatically’.
To login to the iPECS-NMS, execute the Web browser on the client PC and enter the IP address of the NMS server.
34
On the iPECS-NMS login page, enter the Admin User ID and Password (ex., Admin and default password ‘ipecsnms’ were used in this document). Then click on the [Login] button.
NOTE—The admin account is the iPECS-NMS Superuser account and cannot be deleted, but the password can be changed.
After logging into the NMS server, the iPECS-NMS main page will display. Below, each component of the page is identified followed by a brief description:
(1)
(3)
(4)
(5) (2)
35
(1) iPECS System Explorer –Lists registered systems with Station, CO, and other devices
shown in a tree format. If system groups are created to manage systems (refer to Section 4.4.2), those groups are also displayed in tree format.
(2) Alarm/Fault Summary – For alarm/fault events shows the number of events not yet checked by the administrator. For quick access to events, clicking on [Go to Alarm/Fault Management] moves to the Alarm/Fault management screen.
When an alarm/fault event occurs that is configured to play audible alarm in ‘Alarm/Fault Config’, an alarm sound is played depending on the setting of ‘Audible Alarm’ (Toggle=One Time,
Repeat, or Disabled). When set to ‘Repeat’, alarm can be stopped by clicking [Alarm/Fault Summary] or [Go to Alarm/Fault], or clicking the [Alarm/Fault Analysis] menu tab (Toggle=color change from orange when a new alarm/fault occurs).
(3) Information and Control bar - Displays the selected iPECS System Name (on left) and, the NMS User ID and two indicator blocks (on right):
- Block #1(left) – The left block indicates status of NMS client running on Web browser (blinks at a 5 second interval).
- Block #2 – The right block indicates communication status between NMS client and server (blinks at a 10 second interval).
In the small space to the right of block 2, an animating indicator shows when the NMS client is retrieving data from the MFIM.
(4) NMS Menu - Provides tabs to access NMS Web pages for iPECS system related information and the System, User and NMS configuration pages; clicking on a tab moves to the
corresponding functional page.
(5) Displays functional pages corresponding to each menu – Some pages may have a 2nd-level menu depending on the number of features they provide.
To log out from iPECS-NMS:
Click on the [Log-out] button at the top-right of the screen. If a client web browser is closed without logging-out from the iPECS-NMS (by clicking on the [Log-out] button), the client status will be cleared after about 1 minute, automatically logging out the User.
The iPECS-NMS provides various kinds of information in table format. Most of the tables accept those with row naming (ex., System Information, Additional System Information, Channel
36
Information, Device Information, and Device Network Information), support ‘table sort’ by column order. Click a column header, and the table is arranged in the ascending or descending order of the column. Selection of ascending or descending order toggles each time the column header is clicked.
3.4 NMS Message Exchange Overview
iPECS-NMS exchanges various types of information with the registered iPECS systems using SNMP/Trap messages. The message types and the information exchanged under each operational situation are as described in the following table:
Operational Situation Message Type Message Information
System Configuration
IP Address, Site Name, Firmware Version, Nation Code, etc.
Device Configuration
IP address, Device Type, Firmware Version, Location Mode, etc.
iPECS-NMS Restart System Restart System Registration
Basic Channel Information
Device Number, Physical Number, Logical Number, etc.
Alarm/Fault/System Event (Trap) Refer to Alarm/Fault/System Event Table. KeepAlive Message (Trap) Periodically Sent from MFIM.
Network Traffic Information (if initiated by NMS user)
Ping, Traceroute, Device Traffic, iPECS Ping, iPECS Traffic.
iPECS-NMS Service is Operating
iPECS Firmware File (if initiated by NMS user)
iPECS Device/MFIM Firmware File for Firmware Upgrade.
Detailed Channel Information
CO Name, CO Type, CO Group, Station Name, Station Type, etc.
Device/Channel Status Information Device Status, Channel Status Information. Client is Logged in &
Operating (Retrieved by User
37