Académique Documents
Professionnel Documents
Culture Documents
Copyright 2015, Inc. All rights reserved. Reproduction in whole or in part without permission is prohibited.
Information contained herein is subject to change without notice. The specifications and information regarding the
products in this document are subject to change without notice. All statements, information and recommendations
in this document are believed to be accurate, but are presented without warranty of any kind, express, or implied.
Users must take full responsibility for their application of any products. Trademarks, brand names and products
mentioned in this document are the property of their respective owners. All such references are used strictly in an
editorial fashion with no intent to convey any affiliation with the name or the product's rightful owner.
A Family of iDirect Companies
iDirect, a subsidiary of VT Systems, is a global leader in IP-based satellite communications providing technology that
enables our partners to optimize their networks, differentiate and expand their businesses. The iDirect Intelligent
Platform allows our partners to run their entire business operations more efficiently via a single, unified IP-based
satellite architecture, whether it's providing core IP applications to the enterprise or specialized services to any
number of diverse vertical markets. iDirect is the #1 name in global satellite communications in key industries
including maritime, military/government, and oil and gas.
iDirect
Company web site: www.idirect.net ~ Main Phone: 703.648.8000
TAC Contact Information: Phone: 703.648.8151 ~ Email: tac@idirect.net ~ Web site: tac.idirect.net
iDirect Government, created in 2007, is a wholly owned subsidiary of iDirect and was formed to better serve the
U.S. government and defense communities.
iDirect Government
Company web site: http://www.idirectgov.com ~ Main Phone: 703.648.8118
TAC Contact Information: Phone: 703.648.8111 ~ Email: tac@idirectgov.com ~ Web site: http://tac.idirectgov.com
iDirect Asia Pte Ltd was established in Singapore during 2008 to enhance iDirects value-add and responsiveness to
customers in the Asia Pacific region.
iDirect Asia Pte Ltd
Company web site: http://www.stengg.com ~ Main Phone: 65.6521.7888
TAC Contact Information: Phone: 703.648.8151 ~ Email: tac@idirect.net ~ Web site: tac.idirect.net
ii
Revision History
The following table shows all revisions for this document. To determine if this is the latest
revision, check the TAC Web. Refer to Getting Help on page xii for TAC access information.
Revision
Date
Updates
07/31/2014
02/11/2015
04/27/2015
iii
Revision History
iv
Contents
About . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Document Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Getting Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Document Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
1.1
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.2
1.3
1.4
1.5
1.2.1
NMS Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.2.2
Server Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.3.2
Installation Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Launching iMonitor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.4.1
1.4.2
1.4.3
Accepting Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Contents
1.6
1.5.2
1.5.3
1.5.4
1.5.5
1.5.6
Clicking on Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1.6.2
Globe Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.6.3
iMonitor Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
1.6.4
1.6.5
Chapter 2
2.1
2.2
Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
2.1.1
2.1.2
Conditions Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
2.1.3
2.1.4
Offline State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
2.1.5
2.1.6
2.2.2
Interpreting Conditions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
2.3
2.4
Snapshots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
2.4.1
2.4.2
Chapter 3
. . . . . . . . . . . . . . . . . . . . 55
3.1
3.2
3.3
vi
Contents
3.4
Adaptive TDMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
3.4.1
Timeplan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
3.4.2
3.4.3
C/N0 Distribution. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
3.4.4
3.5
Inroute Distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
3.5.1
3.5.2
3.6
Latency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
3.7
3.7.2
3.7.3
3.7.4
3.8
3.8.2
3.8.3
3.9
3.10
Chapter 4
4.1
149
4.1.2
vii
Contents
4.2
4.3
4.2.2
Chapter 5
5.1
5.2
Reporting on Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.1.2
Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
5.1.3
A.2
A.3
A.4
viii
163
. . . . . . . . . . . . . . . . . . 171
A.1.2
A.1.3
A.2.2
A.2.3
A.3.2
A.3.3
A.3.4
Timestamps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
A.3.5
A.4.2
A.4.3
A.4.4
A.4.5
Contents
A.4.6
A.4.7
A.4.8
A.4.9
Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
A.5.2
A.5.3
A.5.4
A.5.5
A.5.6
A.5.7
A.5.8
Appendix B
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
B.1
Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
B.2
Warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
221
C.1
C.2
ix
Contents
C.3
C.2.2
C.2.3
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
List of Figures
Figure 1.
Figure 2.
Figure 3.
Figure 4.
Figure 5.
Figure 6.
Figure 7.
Figure 8.
Figure 9.
Figure 10.
Figure 11.
Figure 12.
Collapsed Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Figure 13.
Figure 14.
Figure 15.
Figure 16.
Figure 17.
Figure 18.
Figure 19.
Figure 20.
Figure 21.
Figure 22.
Figure 23.
Figure 24.
Figure 25.
Figure 26.
Figure 27.
Figure 28.
Figure 29.
Conditions Pane. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Figure 30.
Figure 31.
Figure 32.
Figure 33.
Figure 34.
Figure 35.
Figure 36.
Figure 37.
Disabling a Condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Figure 38.
List of Figures
ii
Figure 39.
Figure 40.
Observing Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Figure 41.
Figure 42.
Figure 43.
Figure 44.
Figure 45.
Figure 46.
Figure 47.
Figure 48.
Figure 49.
Figure 50.
Figure 51.
Event Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Figure 52.
Conditions Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Figure 53.
Figure 54.
Figure 55.
Figure 56.
Figure 57.
Figure 58.
Figure 59.
Figure 60.
Figure 61.
Figure 62.
Figure 63.
Figure 64.
Figure 65.
Figure 66.
Figure 67.
Figure 68.
Figure 69.
Figure 70.
Figure 71.
Figure 72.
Figure 73.
Figure 74.
Figure 75.
Figure 76.
Figure 77.
Figure 78.
Timeplan Graphs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Figure 79.
List of Figures
Figure 80.
Figure 81.
Figure 82.
Figure 83.
Figure 84.
Figure 85.
Figure 86.
Figure 87.
Figure 88.
Figure 89.
Figure 90.
Figure 91.
Figure 92.
Figure 93.
Figure 94.
Figure 95.
Figure 96.
Figure 97.
Figure 98.
Figure 99.
Figure 100.
Hub Line Card Statistics for an SCPC Return Channel and for an XLC-M Line Card. . 88
Figure 101.
Figure 102.
Figure 103.
Figure 104.
Figure 105.
Figure 106.
Figure 107.
Remote Upstream Performance Statistics for TDMA and SCPC Return Channels . . . 94
Figure 108.
Figure 109.
Figure 110.
Figure 111.
Figure 112.
Figure 113.
Figure 114.
Figure 115.
Figure 116.
Figure 117.
Figure 118.
Figure 119.
Figure 120.
iii
List of Figures
iv
Figure 121.
Group QoS Distribution: Group QoS View vs. Remote View. . . . . . . . . . . . . . . . 108
Figure 122.
Figure 123.
Group QoS Distribution: Single Group QoS Node Divided Across Main Display . . . . 110
Figure 124.
Figure 125.
Group QoS Distribution Base Measure: Bandwidth Allocated vs. Static . . . . . . . . 111
Figure 126.
Group QoS Distribution: Tab Name Change for Base Measure . . . . . . . . . . . . . . 111
Figure 127.
Figure 128.
Figure 129.
Group QoS Distribution: Filtering Remotes with the Filter Remotes Button . . . . . 113
Figure 130.
Group QoS Distribution: Selecting a Statistics Record with the Slider. . . . . . . . . 114
Figure 131.
Figure 132.
Group QoS Distribution: Averaging Over the Historical Time Range . . . . . . . . . . 115
Figure 133.
Figure 134.
Figure 135.
Figure 136.
Figure 137.
Figure 138.
Figure 139.
Figure 140.
Figure 141.
Figure 142.
Figure 143.
Figure 144.
Figure 145.
Figure 146.
Figure 147.
Figure 148.
Figure 149.
Figure 150.
Figure 151.
Selecting Remotes in the Left Pane of the ACM Gain Display . . . . . . . . . . . . . . 129
Figure 152.
Figure 153.
Figure 154.
Figure 155.
Figure 156.
Figure 157.
Figure 158.
Figure 159.
Figure 160.
Figure 161.
List of Figures
Figure 162.
Figure 163.
Figure 164.
Figure 165.
Figure 166.
Figure 167.
Figure 168.
MODCOD Utilization: Setting the Maximum Spark Lines for a Remote. . . . . . . . . 140
Figure 169.
Figure 170.
Figure 171.
Figure 172.
Figure 173.
Figure 174.
Figure 175.
Figure 176.
Figure 177.
Viewing IP Routing and HDLC Information from the Remote Command Line . . . . 147
Figure 178.
Figure 179.
Figure 180.
Figure 181.
Figure 182.
Figure 183.
Figure 184.
Figure 185.
Figure 186.
Figure 187.
Figure 188.
Figure 189.
Figure 190.
Figure 191.
Figure 192.
Figure 193.
Figure 194.
Figure 195.
Figure 196.
Figure 197.
Figure 198.
Figure 199.
Figure 200.
Figure 201.
Figure 202.
List of Figures
vi
Figure 203.
Figure 204.
Figure 205.
Figure 206.
Figure 207.
Figure 208.
Figure 209.
List of Figures
vii
List of Tables
Table 1.
Table 2.
Table 3.
Table 4.
Table 5.
Table 6.
Table 7.
Table 8.
Table 9.
Table 10.
Table 11.
Table 12.
Table 13.
Table 14.
Table 15.
Table 16.
Table 17.
Table 18.
Table 19.
Table 20.
Table 21.
Table 22.
Table 23.
Table 24.
Table 25.
Table 26.
Table 27.
Table 28.
Table 29.
Table 30.
Table 31.
Table 32.
Table 33.
Table 34.
inroute_composit_stats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
Table 35.
inroute_slot_usage_stats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
Table 36.
remote_power_stats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
Table 37.
Table 38.
viii
List of Tables
Table 39.
Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
Table 40.
Warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
Table 41.
Table 42.
Table 43.
Table 44.
ix
List of Tables
About
Purpose
The iMonitor User Guide provides detailed instructions for monitoring iDirect networks using
the iMonitor client application of the iDirect Network Management System (NMS). For details
on configuring iDirect networks, see the iBuilder User Guide.
Audience
The iMonitor User Guide is intended for network operators, network architects, and other
personnel who operate or monitor iDirect networks. It is not intended for end users or field
installers.
Contents
This document contains the following major sections:
This document contains the following major sections:
Reporting on Networks
xi
Document Conventions
Document Conventions
This section illustrates and describes the conventions used throughout this document.
Convention Description
Example
Terminal
Output
Screen
Reference
Command
cd /etc/snmp/
The Remote dialog box has a number of userselectable tabs across the top. The Information
tab is visible when the dialog box opens.
For instructions on adding a line card to the
network tree, see Adding a Line Card on
page 108.
Getting Help
The iDirect Technical Assistance Center (TAC) is available to provide assistance 24 hours a day,
365 days a year. Software user guides, installation procedures, FAQs, and other documents
that support iDirect products are available on the TAC Web site. Access the TAC Website at
http://tac.idirect.net.
The TAC may also be contacted by telephone or email.
xii
E-mail: tac@idirect.net
Document Set
For sales or product purchasing information contact iDirect Corporate Sales at the following
telephone number or e-mail address:
E-mail: SALES@idirect.net
iDirect produces documentation that is technically accurate, easy to use, and helpful to our
customers. Please assist us in improving this document by providing feedback. Send comments
to techpubs@idirect.net.
Document Set
The following iDirect documents are available at http://tac.idirect.net and contain
information relevant to installing and using iDirect satellite network software and equipment.
xiii
Document Set
xiv
iBuilder enables rapid, intuitive configuration of any iDirect network. It allows you to
easily add components to your network, change your current configuration, and download
configuration and software to network elements. The iBuilder Revision Server provides
automated management of software and firmware upgrades for your remote modems.
The iBuilder Group QoS (GQoS) user interface allows advanced network operators a high
degree of flexibility in creating subnetworks and groups of remotes with various levels of
service tailored to their network requirements. The iBuilder User Guide provides detailed
instructions for using iBuilder to configure and manage your network.
iSite allows you to monitor and configure iDirect devices in the field. It includes several
features that aid in the remote commissioning process, including assistance for antenna
pointing, antenna look angle calculation, and cross polarization. An iSite API is available
for custom development. Remotes that support the iSite client do not support Web iSite.
Web iSite is the Web-based version of iSite available for the latest generation of iDirect
remote modems, including the Evolution X1, X7 and e150. Web iSite can be used with any
supported Web browser; therefore, no client software is required. Remotes that support
Web iSite do not support the iSite GUI client discussed above.
ii
A Virtual Network Operator (VNO) license enables network operators to view and
manage only their own networks and remotes, independent of other operators delivering
services out of the same hub. The VNO package makes it possible to scale investments to
actual business growth, significantly reducing initial capital equipment expenses.
Configuring VNOs is described in the iBuilder User Guide.
A Customer Network Observer (CNO) license grants filtered read-only iMonitor access,
allowing customers real-time and historical views into their own network performance
while maintaining overall network privacy. Configuring CNOs is described in the iBuilder
User Guide.
NMS applications with Graphical User Interfaces (GUIs) for configuring and monitoring
iDirect networks
For a description of all iVantage NMS components see The iVantage Network Management
System on page i.
NOTE: iDirect Mesh is not supported in iDX Release 3.3.
1.1
Introduction
This chapter provides important information needed to understand how iMonitor works and
how to use it effectively. This chapter discusses how to prepare for installation; how to use
the tools available in iMonitor; how to create, customize, and print reports; and how to
determine the configuration status of network elements.
iMonitor provides visibility to real-time status and operational characteristics of network
elements.
Status refers to the real-time state of network elements (such as OK, Warning, Alarm).
iMonitor generates warnings and alarms for the various network elements when faults or
anomalous conditions occur. Warnings and alarms are collectively called conditions.
Status and statistical data are stored in the historical archive to provide analysis of anomalous
conditions and performance trends.
1.2
iBuilder
The iBuilder client provides all configuration and control functions to network operators.
Configuration consists of creating network elements (such as networks, line cards, and
remotes) and specifying their operational parameters (such as QoS profiles or IP addresses).
Control consists of applying the specified configurations to the actual network elements;
retrieving active configurations; resetting elements; and upgrading element software and
firmware. Refer to the iBuilder User Guide for more information.
iMonitor
The iMonitor client provides complete visibility to the real-time status and operational data of
network elements. Status refers to the real-time state of network elements, such as OK,
warning, or alarm. Operational data are captured in a variety of network statistical data
tables and displays, revealing, for example, IP traffic statistics, satellite link quality, and
hardware component operating values.
In addition to real-time visibility, iMonitor provides state information and statistics from the
historical archive in order to analyze anomalous conditions and performance trends. This
guide has a complete list of real-time and historical data available through iMonitor.
iSite
The iSite client is used primarily for commissioning new sites and monitoring remotes from
the local LAN side. It contains functions to help installers calculate antenna
azimuth/elevation; perform antenna pointing; and perform cross-polarization and 1 dB
compression tests. It also provides configuration and real-time state/statistical information
for one or more remote units. Instead of interacting with the NMS middleware, iSite connects
directly to each remote to perform all of its operations. iSite does not provide access to
historical information. See the Installation and Commissioning Guide for Remote Satellite
Routers for more on commissioning remotes using iSite.
NOTE: End-users do not need iSite in order to receive or transmit IP data over the
iDirect system.
Configuration Server
The configuration server manages access to the configuration database, which contains all the
element definitions for iDirect networks and their operational parameters. Additionally, the
configuration server provides most network control functions (configuration apply, firmware
download, resetting, etc.). The other servers also use the configuration server to determine
what the network components are.
Event Server
The event server generates warnings and alarms and sends them to iMonitor for display.
Warnings and alarms are collectively known as conditions. The event server also collects
and archives all system events and provides them to iMonitor for display.
Latency Server
The latency server measures round-trip time, or latency, for every active remote in the
networks. These measurements are stored in the archive and provided to iMonitor for display.
Consolidation Script
The consolidation process periodically consolidates records in the statistics archive to
preserve disk space on the server machine. Default consolidation parameters are already
entered into the configuration database. These settings can be tuned to particular storage
requirements as required.
1.3
Windows XP
Windows 7
No additional operating systems are supported. iDirect does not support server-based versions
of Windows.
NOTE: The iDirect clients may not operate correctly below screen resolution 1280
X 1024.
Launching iMonitor
The iDirect clients may not operate correctly in the 32-bit version of Windows 7. If an iDirect
client experiences problems, configure it to run in Windows XP Service Pack 3 compatibility
mode as follows:
1. Right click the .exe file and select Properties.
2. Click the Compatibility tab.
3. Select Run this program in compatibility mode for: Windows XP (Service Pack 3).
4. Click OK.
1.4
Launching iMonitor
iMonitor is initially installed with two default accounts: admin and guest. The admin user
has full access privileges to all iMonitor functionality. The guest account has read-only access.
The passwords for these two accounts are identical to their user names. For information on
setting up user accounts, see the chapter Managing User Accounts and User Groups in the
iBuilder User Guide.
iDirect strongly recommends changing all default passwords as soon as possible after the
installation.
1. To launch iMonitor, double-click the desktop shortcut or select it from the Windows Start
menu.
2. Enter the User Name and Password in the Login Information dialog box.
Launching iMonitor
The iMonitor application automatically connects to the NMS server processes that are
required to perform the NMS functions. If this connection is lost for any reason, iMonitor
automatically reconnects to the servers when they become available.
1.5
Real-time requests display data as it arrives at the NMS. These requests have no end
time; they continue to add data as long as the display is open. Closing either the specific
display or the iMonitor application automatically cancels real-time requests.
Historical requests retrieve data from the historical archive based on the start and end
times specified. These requests are active only until the data is completely delivered to
iMonitor.
Get Past requests represent a hybrid of real-time and historical requests. iMonitor
retrieves the most recent data from the archive, and then continues to display real-time
data until the request is cancelled.
Latency
Events
Conditions
Remote Status/UCP
If the vertical scroll bar is positioned somewhere other than the bottom of the
display, data continues to be added at the bottom, but the display does not scroll.
Multiple rows of data can be selected, copied and pasted into another application such as
Excel for offline viewing and analysis.
Fit to Window resizes all columns to fit inside the current width of the pane (so that
no horizontal scroll bar is required).
Copy copies the column headings and data to the clipboard so that it can be pasted
into an application such as Excel.
Copy without headers copies the data to the clipboard without the column headings.
When the data makes sense only for a single network element, iMonitor launches one
pane for each element.
When the data from multiple elements can be shown together, iMonitor launches a single
pane and displays all data in that pane.
1.6
10
Single-click a plus (+) or minus (-) sign next to an element in the iMonitor Tree to expand
or contract the branches to the next level.
2. Click and hold the double-ridge lines at the top of the pane and drag the pane to a new
position. Depending on its new position, the pane may change shape. The shape of the
new position will be outlined in iMonitor.
3. Release the mouse button to re-dock or detach the pane.
4. To detach a pane completely, double-click the double-ridge lines.
5. To move a detached pane, either click and drag, or right-click in the border at the top of
the pane and select Move.
6. To resize a pane, place the mouse pointer at an edge of the pane and drag the edge to a
new position.
11
Sorting Columns
In any pane with columns, or list controls, sort the entries by the values in any column by
clicking the column heading.
12
2. In the Sort Preferences dialog box, click the Sort items in drop-down list and select
either Ascending or Descending.
4. When sorting by Name, select or clear the Names are case sensitive check box.
5. Click the Apply sort to drop-down to select an element on which to sort.
13
6. Click OK.
NOTE: iMonitor remembers the selected sort preference after logging out and
logging on again.
A minus sign (-) next to an element indicates that the element has been expanded and
children are visible at the next level, or branch, in the Tree. Click the minus sign (-) to hide
the next level of the Tree.
14
In Figure 15, the UAT-RF Network has been expanded as far as possible. The UAT-RF Network
cannot include children in another network; therefore, its only children are the TxRx and Rx
line cards, and the IG_1_UAT-RF Inroute Group. The Inroute Group is a parent element that
can be expanded by clicking its plus sign (+) to reveal its children elements at the next level
of the Tree.
Menu Bar
The Menu bar at the top of the display provides access to a number of operations described in
the sections below.
Toolbar
The main Toolbar (Figure 18) contains context-sensitive buttons for performing a variety of
operations on the currently-selected element without using its context menu. The toolbar
functions are described in Table 1.
15
Function
View elements in the Tree Menu hierarchy.
View Conditions.
Accept changes made to the system by another user and update the iMonitor
display with the latest database information.
Audio Notification
Audio Notification turns on an audible alert whenever a new alarm or condition is raised.
When enabled, audio notifications only sound for newly-raised conditions by default. When a
condition is acknowledged, the audio notification stops, even if the condition has not yet
cleared.
To configure audio notification:
1. Select ResultsAudio Notification from the main menu.
2. Select any or all of the conditions under which to raise audio notifications (Figure 19).
16
17
Acknowledging Conditions
If audio notification is enabled, acknowledging conditions prevents continuous audio
notification, even if the condition that raised the audio notification has not cleared. When
conditions are acknowledged in iMonitor:
To acknowledge conditions:
1. Click the Toggle Conditions icon on the main toolbar or select ViewConditions from
the main menu to open the Conditions pane.
2. On the Conditions pane, select the Condition Log tab.
3. Click the Acknowledgement icon on the main toolbar. On the Condition Log tab, a check
is displayed for all acknowledged conditions as shown in Figure 22.
18
View Menu
Select the View menu on the main menu toolbar to display or hide toolbars, panes, status
items, and workplace windows as shown in Figure 23. Alternatively, right-click in the main
iMonitor pane to see the same options.
Searching iMonitor
Use the Find toolbar to search the NMS for matching elements and display the results in either
the Network Tree View or the Results Window. This becomes increasingly useful as networks
grows larger.
To search using the Find toolbar:
1. Select ViewFind Toolbar to display the Find toolbar.
2. Enter a string in the first box or click the drop-down arrow to select from earlier search
strings.
3. Select an element type in the second drop-down list.
4. Select a search type in the third drop-down list.
5. Select the screen area to search in the last drop-down list.
6. Click the Binoculars icon to begin the search.
Figure Figure 24 shows the options within each search box.
19
20
Workspace Toolbar
The Workspace Toolbar provides a convenient way to organize multiple displays into a series
of virtual workspaces. The four workspaces on the toolbar provide four times the window
space without adding another monitor.
To launch the Workspace toolbar, select ViewWorkspace from the iMonitor main menu.
Four small windows appear on the right-side of the iMonitor main tool bar. Each of these
windows represents a virtual workspace.
Click a workspace window to move from the current workspace to another workspace.
Displays launched in the previous workspace are hidden and a new, blank workspace appears.
A workspace becomes active when a display is launched in that workspace. Active workspaces
are represented by yellow windows in the toolbar. Only displays launched in the selected
workspace are shown on the screen.
Figure 26 shows the Workspace toolbar in action. In this example, the second workspace
contains one or more displays and the other workspaces are empty. Click the fifth workspace
to view all displays in all workspaces.
The following workspace operations can be performed from the main menu:
21
Operational Toolbar
The Operational Toolbar (Figure 27) contains context-sensitive buttons for performing
operations on the currently-selected element without using its context menu. These functions
are described in Table 2.
Function
Request a Network Condition Snapshot
Request conditions
22
Function
Request a SAT Long Term Bandwidth Usage report
Status Bar
The Status bar is located at the bottom of the iMonitor window. It displays the iMonitor user
name and the server connection status. In Figure 28, the connection status is Ready and the
iMonitor user name is admin.
23
Conditions Pane
Select ViewConditions to open the Conditions pane. See Chapter 2, Monitoring Conditions
and Events for complete information on the tabs in this pane.
Legend Pane
The Legend pane displays the Configuration State icons and their meanings. They are
organized by type of element as shown in Figure 30. To view all Legend icons and meanings,
select ViewLegend.
24
Figure 32. Real-Time Status of Remote with Idle and Dormant States Enabled
25
26
3. In the Select Columns dialog box, click the check boxes to select or clear the
corresponding columns for display. (Alternatively, select and clear a check box by first
selecting the column name in the list, and then clicking the Show or Hide button.) Only
selected columns are displayed in the pane.
4. Click Show All or Hide All to select or clear all check boxes.
NOTE: In some cases, the Select Columns dialog box also contains a Show
Default button (Figure 35). Click that button to select only the default columns.
Figure 35. Select Columns Dialog Box with Show Default Button
5. To change the order in which columns appear in the pane:
a. Click a column name to select it.
b. Click the Move Up button to move the selection one place up in the list. This moves
the column to the left in the pane.
c. Click the Move Down button to move the selection down in the list. This moves the
column to the right in the pane.
6. To change the width of a specific column, first select the column name. Then enter the
new width in Width of selected column.
27
28
2 Monitoring Conditions
and Events
iMonitor displays both conditions and events. Conditions (alarms and warnings) indicate a
problem or potential problem in an iDirect network. Events provide real-time information
about the operation of the network but do not indicate a network problem. Table 3 identifies
the types of notifications (conditions or events) iMonitor provides for each element in the
Tree.
Table 3. Elements and Types of Information Provided
2.1
Elements
Type of Incident
Information Provided
Teleport
Conditions
Protocol Processor
Events/Conditions/Blade Info
Blades
Events/Conditions/Blade Info
Network
Events/Conditions
Line Card
Events/Conditions
Inroute Group
Events/Conditions
Remotes
Events/Conditions
Chassis
Conditions
Conditions
Conditions in iMonitor are made up of Alarms and Warnings. Alarms indicate an interruption in
service. Warnings indicate conditions that could result in an interruption of service if not
handled in a timely fashion.
29
Conditions
30
Icon
Meaning
OK
OK
Warning
Alarm
Mesh Alarm
Offline
Rx Only
Elsewhere
Sleep Mode
Unknown
Condition
Disabled
Disabled condition
Conditions
Active Conditions shows all outstanding conditions that have not been cleared. Any
current alarms or warnings are displayed on this tab.
Observation View shows all conditions for specific elements under observation. (See
Placing an Element Under Observation on page 38.)
Disabled Conditions shows all conditions that have been disabled. To disable an active
condition, right-click the condition and select Disable Condition.
Condition Log shows the 500 most recent condition changes. Conditions on the Condition
Log tab are sorted by the time that the condition change occurred by default.
31
Conditions
One or more Warnings and one or more Alarms: overall state is Alarm
32
Element
Alarm Condition
Explanation
Chassis
Chassis Down
Protocol
Processor
Hub Line
Card
TDM Lock
GIG E Failed
NCR Missing
PPS Missing
Hub line card does not detect pulse per second signal
Conditions
Alarm Condition
Explanation
Remote
LAT Timeout
LL Down
Warning Condition
Explanation
Chassis
Power Supply n
Failed
Fan n
Failed
Failed
Rx Overflow of frames
Four-Slot
Chassis
Hub Line
Card
33
Conditions
34
Element
Warning Condition
Explanation
(Hub Line
Card)
GIGE health
Protocol
Processor
Remote
Certificate is Invalid
CRC8 Errors
CRC32 Errors
Fan Alarm
Latency
Lost Contact
Maximum Tx Power
Timing Offset
Remote Temperature
Conditions
Warning Condition
Explanation
Rx SCPC C/N
35
Conditions
Warning
Specified slave does not appear to be an IP address, aborting.
Specified slave matches master hostname, aborting.
Specified slave matches master IP, aborting.
Specified slave is not reachable, aborting.
User idirect cannot ssh into host specified slave without a password,
aborting.
iDirect NMS Servers RPM is not installed, aborting.
MySQL is not installed, aborting.
MySQL account info missing, user: admin.
MySQL account password missing, user: admin.
MySQL account info missing, user: app.
MySQL account password missing, user: app
The database contains DB tables that are not supported in this version of the iDX
product, aborting.
Failed to connect to MySQL database on master with credentials: <db user>, <db
password>.
MySQL is not installed on slave, aborting.
MySQL version on slave does not match MySQL version on master, aborting.
NMS servers not installed on slave <slave>, aborting.
NMS servers version on slave does not match version on master, aborting.
Existing slave server specified. Use -f to force re-creation of an existing slave
server.
mysql-binlog-purge
36
Conditions
Table 7. Warnings Raised by NMS Database Replication Scripts on MySQL Master (continued)
Script Name
mysql-repl-monitor
Warning
Replication error detected on slave.
iDirect NMS Servers RPM is not installed, aborting.
MySQL is not installed, aborting.
Slave is not reachable, aborting.
MySQL is not installed on slave, aborting.
MySQL version on slave does not match MySQL version on master, aborting.
NMS servers is not installed on slave, aborting.
NMS servers version on slave does not match MySQL version on master, aborting.
Failed to connect to MySQL database on slave
repl-file-send
Table 8 lists the iMonitor warnings that can be raised by the NMS Database Replication scripts
that run on a Backup NMS Server (MySQL Slave).
Table 8. Warnings Raised by NMS Database Replication Scripts on MySQL Slave
Script Name
cr8DbSlave
Warning
MySQL account info missing, user: admin.
MySQL account password missing, user: admin.
MySQL account info missing, user: app.
MySQL account password missing, user: app.
37
2.2
Blade
Line Card
Remote
Chassis
2. Select ViewConditions from the main menu or click the Toggle Conditions icon
(eyeglasses) on the main toolbar.
38
39
5. To view the control panel (Figure 42) for a remote under observation, right-click a remote
condition and select Remote Control Panel or double-click the remote condition. See
Control Panel on page 125 for details.
40
41
Figure 45. Events Time Range Dialog Box with Text Filter
b. For Get Past, select a past time interval from the Get Past drop-down list.
42
43
8. Right-click in the Time Line display to view the results in Seconds, Minutes, or Hours.
Current Date
Figure 50 shows the Conditions Time Line Tab expanded to view details.
44
10. When retrieving data on events, the Events pane appears (Figure 51). Data in the Events
pane is displayed in a multicolumn format only.
Arrow
Figure 51 shows an example of the conditions display, including elements with multiple
conditions.
45
46
2.3
2.4
Snapshots
There are two types of snapshots: Conditions Snapshots and Data Snapshots.
The following snapshots can be selected from the appropriate elements in the iMonitor Tree:
Network: Network Condition Snapshot, Network Data Snapshot, Line Card Data Snapshot
Inroute group: Network Condition Snapshot, Network Data Snapshot, Line Card Data
Snapshot
47
Snapshots
Network Condition Snapshot at the network level includes all line cards, inroute
groups and remotes in the network.
Network Condition Snapshot at the inroute group level includes all line cards and
remotes in the inroute group.
3. Right-click a network element in the Condition Snapshot pane for a menu of operations
on that element. Figure 54 shows an example of the remote menu.
48
Snapshots
49
Snapshots
Compact Icons
Arrange Icons
List
Details
Details in Group
Activated
5. Figure 55 shows the results of selecting Details for the Teleport Condition Snapshot.
50
Snapshots
Name
Current Condition
7. Double-click a Remote in the snapshot view to view the Remote Control Panel. See
Control Panel on page 125 for information about the control panel.
Latency
Events
Conditions
The following example illustrates the use of multiple-select to populate a parameters dialog.
1. In the Network Condition Snapshot results view, with Details selected (Figure 57), select
the remotes to use in the parameters dialog box.
51
Snapshots
52
Snapshots
53
Snapshots
5. Click OK to view the Data Snapshot. Only the selected elements and parameters are
displayed.
54
Copy the data without the headers to the clipboard for pasting into other applications
Expand the columns to view the complete data within each column
3 Monitoring Performance
and Status
This chapter describes how to view and interpret performance information for iDirect network
elements.
3.1
The Process tab shows the various software processes running on each blade and the
remotes under each process.
The Remotes tab lists the remotes per network being managed by the blades.
The CPU Usage tab shows the percentages of CPU usage by category and the CPU idle
time.
The GKD tab shows the current Master Global Key Distributor (GKD) and any higherpriority GKDs for each blade. The Master GKD is the GKD currently supplying the TRANSEC
Network Acquisition Keys to the blade for distribution to the TRANSEC remotes.
55
NOTE: The GKD tab is only displayed for blades on TRANSEC Protocol Processors.
2. Click any of the tabs to view different types of information. Figure 64 shows examples of
all four Blade Info tabs.
Notice on the GKD tab (bottom image) that the blade has lost communication with the
configured Master GKD (with priority 30) and has connected to the GKD with priority 20. If
the higher-priority GKD comes back on line, the blade will reconnect to that GKD. For
more information, see the appendix Managing TRANSEC Keys in the iBuilder User Guide.
56
3.2
Use the Remote Power section to change the transmit power of the remotes acquisition
bursts when setting the initial power during commissioning. The remote must be locked to
the downstream carrier to perform this function.
NOTE: Changing the transmit power is not effective if the remote has already
acquired the network. When in the network, the remote transmit power is
automatically controlled by the UCP process at the hub.
Once a remote joins the network, the Transmit Power displayed in the Remote Power
section updates periodically. For TDMA remotes, the Transmit Power displayed is relative
to the reference carrier parameters configured for the remote in iBuilder. This allows
direct comparison between the Configured Initial Power and the Transmit Power.
When a remote is in the network, use the Remote Power section to determine the
correct setting for the remotes initial transmit power during commissioning or to verify
that it is set correctly during network operation. During clear sky operation, the margin
between the Configured Initial Power and the Transmit Power should agree with the
network design.
In Figure 65, the TDMA Initial Power configured in iBuilder is -20 dBm relative to the
reference carrier parameters. The last power relative to reference carrier reported by
the remote is -21.78 dBm. If the remote drops out of the network, it will transmit all
acquisition bursts at -20 dBm relative to the reference carrier regardless of the definition
of the carrier on which the acquisition slot is assigned.
Use the Terminal Sessions section to launch a terminal window on the remote or on the
protocol processor blade controlling the remote. The remote must be in the network and
the client PC must have IP connectivity to the remote to perform this function.
Use the Reset Remote section to reset the remote using a MAC-level message from the
Protocol Processor. The remote does not need to be in the network but must be locked to
the downstream carrier to perform this function.
Use the Cross Polarization section to instruct the remote to transmit an unmodulated
(CW) carrier or modulated (PN) carrier on a specific frequency.
Use the Protocol Processor section to view statistics, reset statistics, view parameters,
bounce the link layer, or perform an ACQ Bounce. Bouncing the link layer causes it to go
through the initialization handshake sequence. ACQ Bounce causes the remote to
reacquire the network. ACQ bounce is discussed in ACQ Bounce from the Inroute
Distribution Pane on page 79.
57
58
59
60
To change to a different frequency, click the Stop button before entering the new
frequency and restarting the carrier.
g. When finished, reset the remote to return the remote to normal operation. Use either
the Reset button on the probe or reset the remote from iBuilder.
NOTE: The remote automatically stops transmitting a carrier started from this
screen five minutes after the carrier was started or the power was last adjusted.
To change this timeout, configure the remote custom key described in Modifying
the Timeout Duration for a CW or PN Carrier on page 62.
6. To view statistics, reset statistics or perform bounce functions, select a layer in the
Protocol Layer drop-down list.
61
62
63
3.3
64
65
Adaptive TDMA
3.4
Adaptive TDMA
The following iMonitor displays provide analysis of Adaptive TDMA performance:
Timeplan
C/N0 Distribution
Each of these displays is discussed in the following sections. See the chapters Adaptive
TDMA and Uplink Control Process in the Technical Reference Guide for details of network
operation when using Adaptive TDMA.
3.4.1 Timeplan
The Timeplan display shows the total capacity of an inroute group versus the allocated
bandwidth over time. The display can be used to verify that the upstream capacity is
allocated efficiently in all conditions. If this is not the case, it may be possible to improve the
upstream efficiency by optimizing the definitions of one or more of the Inroute Group
Compositions (IGCs).
This Timeplan display can be launched from the Network and Inroute Group levels of the
iMonitor tree. The display shows the following statistics over time for an inroute group:
The capacity of the inroute group in traffic slots per TDMA frame
The Inroute Group Composition (IGC) assigned to the inroute group at the time of each
statistics sample
66
Adaptive TDMA
The bottom graph shows a time line of IGC usage. The IGC in use at any time is
represented by the position of the line on the y axis. This graph does not show
capacity.
6. If multiple inroute groups were selected in the Select Inroute Group dialog box, click an
inroute group in the list on the left to switch the display to that inroute group.
7. Click Hour, Min or Sec to change the time scale on the x axis.
8. Use the right-click menu to change the display. For example:
Select ChangeScale to modify the position and scales of the x axis or y axis.
67
Adaptive TDMA
Click Slots to view only the graph showing capacity versus total slots.
Click the List Data tab to view the Timeplan statistics in a multicolumn list (Figure 79).
68
The average number of Allocated Slots per frame for the sample
The average number of Free Slots per frame for the sample
The number of the IGC in use for the inroute group at the time of the sample
Adaptive TDMA
A histogram showing the percentage of time each IGC was in use over the selected
statistics period
A multicolumn list of statistics records showing IGC usage and the Figures of Merit used to
select the next IGC
69
Adaptive TDMA
7. Right click anywhere in the main window and select Type to change the type of graph
(Figure 81).
70
Adaptive TDMA
10. Use the right-click menu to change the display. For example:
Select ChangeScale to modify the position and scales of the x axis or y axis.
Select ChangeText to modify the text color or wording of the title of axis label.
11. Click the List Data tab to view the IGC Usage statistics in a multicolumn list (Figure 83).
The IGC In Use for the inroute group at the time of the sample
The Figure of Merit for each IGC at the time of the statistics sample.
An IGC selection algorithm executes periodically at the hub to determine the best IGC for an
inroute group under current network conditions. Each time the IGC selection algorithm
executes, it computes a Figure of Merit for each IGC. These Figures of Merit are relative
numbers used to compare the IGCs. An IGC with a higher Figure of Merit is better suited for
the current network conditions than an IGC with a lower Figure of Merit. Each time the
selection algorithm executes, the IGC with the highest Figure of Merit is selected as the next
IGC. The frequency with which the algorithm executes is configured in iBuilder.
NOTE: If a fixed IGC is selected in iBuilder for the inroute group, the IGC
selection algorithm is not executed. Therefore, the Figures of Merit on the List
Data tab are all set to zero.
For more information, see the chapter Adaptive TDMA in the Technical Reference Guide and
the section Inroute Groups in the iBuilder User Guide.
71
Adaptive TDMA
72
Adaptive TDMA
The bottom two graphs in Figure 84 show the distribution of C/N0 measurements of TDMA
bursts received at the hub in relation to the target thresholds of two upstream carriers. When
viewed for a carrier, the graph shows both the distribution of C/N0 measurements and the
target threshold of the carrier. The carrier name is displayed in the title of each graph.
The top graph in Figure 84 shows the scattering of the C/N0 measurements for all carriers in
an inroute group. Since the target thresholds can be different for each carrier, the graph is
normalized to show variations from nominal for all carriers rather than the actual
measurements. Zero on the y axis represents nominal for all carriers.
By default, the graph plots the 25th and 75th percentiles of the C/N0 measurements in each
sample. These values can be modified using the MAX MIN button. Ideally, the line
representing the target threshold should be centered between the lines representing the
scattering of the C/N0 measurements. A distribution that is not centered around the target
C/N0 may indicate a problem with the system configuration.
Typically, a variation of approximately 2 dB from the target threshold is considered normal
for the default percentiles. A centered graph with wide variation in C/N0 measurements may
indicate a problem with individual remotes. Problem remotes can be isolated by observing the
Upstream C/N0 and Thresholds of specific remotes as described in Upstream C/N0 and
Thresholds on page 74.
To view the C/N0 Distribution display:
1. Right-click a network or inroute group in the iMonitor tree and select ATDMA StatsC/N0
Distribution to open the Select Inroute Groups dialog box (Figure 77 on page 66).
2. Select the Inroute Groups to view.
3. Enter a Time Range for historical data.
NOTE: Historical is automatically selected in the Select Inroute Group dialog box
and cannot be changed. Only historical data is available for the C/N0 Distribution
display.
4. Click OK to view the Timeline tab (Figure 84).
5. If multiple inroute groups were selected in the Select Inroute Groups dialog box, select
from the inroute group list on the left to switch the display to a different inroute group.
6. Use the right-click menu to change the display. For example:
Select ChangeScale to modify the position and scales of the x axis or y axis.
7. Click the buttons on the left to display or hide graphs or to change the display. A total of
five graphs can be displayed at the same time.
Click Hour, Min or Sec to change the time scale on the x axis.
Click the Area button to color the area between the upper and lower limits.
Click the Carrier button to display or hide the target thresholds on the graphs.
Click the individual carrier buttons (C1, C2, etc.) to display a graph of the C/N0
distribution for the selected carrier. The carrier name is displayed in the graph title.
Click the MAX MIN button to adjust the minimum and maximum percentiles displayed
on the graphs by changing the values for Min Threshold % and Max Threshold %.
73
Adaptive TDMA
Click the IGCs button to display a graph tracking the IGC selection for the inroute
group over time. Use this graph to correlate the C/N0 distributions shown on other
graphs to the IGC in use at any given time.
Click the Thr (Threshold) button to display a graph of the target thresholds for all
carriers in the inroute group over time.
8. Click the List data tab for a multicolumn list of the statistics used to build the graphs
(Figure 85).
The Current IGC for the inroute group at the time of the sample
NOTE: If the number of samples in the statistics record is less than 50, N/A is
displayed in the carrier column and nothing is displayed on the graph for that data
point.
74
The target C/N0 thresholds of all carriers in the remotes inroute group.
Adaptive TDMA
The Upstream C/N0 and Thresholds display can be used to observe the effects of uplink power
control on the transmissions of individual remotes; to investigate performance issues such as
those caused by a poorly pointed antenna; or to help identify carrier interference.
To view the Upstream C/N0 and Thresholds display:
1. Right-click an inroute group or a remote in the iMonitor tree and select ATDMA Stats
Upstream C/N0 and Thresholds to open the Select Remotes dialog box (Figure 86).
The Find Next button finds the next remote in the list that matches the Search
string.
75
Adaptive TDMA
8. Click the buttons on the left to display information on the graph or to change the display.
Click Hour, Min or Sec to change the time scale on the x axis.
Click the None button to clear all data series from the graph.
Click the All button to display all available data series on the graph (C/N0, nominal
carrier, and all carrier thresholds).
Click the C/N0 button to display the C/N0 of the selected remote.
Click the Nominal button to make the line representing the remotes nominal carrier
bold.
Click the individual carrier buttons (C1, C2, etc.) to display the target thresholds of
the selected carriers.
NOTE: Hover the mouse pointer over a carrier button to view the carrier name
(Figure 87).
9. Click the List data tab for a multicolumn list of the statistics used to build the graphs
(Figure 85).
76
Adaptive TDMA
77
Inroute Distribution
3.5
Inroute Distribution
The Inroute Distribution pane shows timeplan slot allocation averaged over a one second
interval for all inroutes in an inroute group. This display is useful for determining how slots
are allocated to remotes across all inroutes in an inroute group. The display shows data in
real-time only. The NMS does not save this data to the archive database.
78
Inroute Distribution
NOTE: The Inroute Distribution pane is specific to individual inroute groups. When
multiple inroute groups are selected, iMonitor launches a separate pane for each
inroute group.
This Inroute Distribution pane (Figure 90) is organized as follows:
There is one row for each remote that was allocated upstream slots in the latest data
sample.
There is one column (on the right) for each receive line card that receives an inroute on
which slots were allocated.
The Remote Name column shows the names of the remotes that received slots.
The Type-SN column shows model type and serial number of each remote.
The Total, Slots/Frame column shows the total slots per frame allocated to each remote
across all inroutes.
The line card Slots/Frame columns show the total slots per frame allocated on the
receive carriers for each line card.
The total slots per frame allocated on the receive carriers of each line card and the
percentage of the total bandwidth this represents
The total number of slots in the timeplans for each carrier received by each line card
79
Latency
3.6
Latency
The NMS measures the round-trip time from the hub to each remote and back every five
seconds. Real-time latency results are available in iMonitor. Latency responses exceeding 800
milliseconds are available from the historical archive and are saved for one week by default.
Latency can be selected in the iMonitor tree for Networks, Inroute Groups and Remotes.
The NMS measures latency by sending an empty ICMP echo request and measuring the elapsed
time until it receives the ICMP echo response from the remote. If the round trip time is
greater than two seconds, iMonitor raises a Warning for the remote. The receipt of the ICMP
echo response is also used to generate the layer 3 latency alarm. The NMS generates a latency
alarm if it misses three consecutive ICMP echo responses. A latency alarm indicates a
potential IP problem.
To view latency measurements for one or more remotes:
1. Right-click a network, inroute group, or remote in the iMonitor Tree and select Latency to
open the Select Items dialog box.
80
Latency
3. For historical data, select Historical and click Time Range to open the Select Time
Range dialog box (Figure 93). Then enter a Start Time and End Time, or use the slider to
set the Start Time.
Figure 93. Select Time Range Dialog Box and Clock Display
NOTE: Alternatively, click the ellipses next to the Start and End times to set the
time using the graphical clock display.
4. To retrieve past data and continue to receive real-time statistics, select a time interval in
the Get Past drop-down list (Figure 92).
5. Click OK to view the Latency pane.
81
NOTE: Historical latency reports show only data for latency timeouts. They do not
show measurements that are below the threshold.
NOTE: Latency is measured from the NMS server. The latency results do not
measure latency from the remotes to arbitrary IP addresses on the public
Internet.
3.7
Networks
Line cards
Remotes
Network
Line Cards
The line card statistics contain information for each line card. Only applicable fields are
displayed depending on the role of the line card (DVB-S2 Tx, Tx/Rx, TDMA Rx, SCPC return Rx,
etc.). Examples of the statistics displayed include:
82
Transmit errors
Received bytes
AGC gain
NOTE: Table 14 on page 179 lists all line card statistics archived by the NMS.
83
4. To retrieve past data and then continue to receive real-time statistics, select a time
interval in the Get Past drop-down list.
Figure 96. iMonitor Hub Line Card Statistics Pane: Initial View
Figure 96 shows the initial view of the Hub Line Card pane launched from the network
level of the tree. Four line cards were selected in the Select Line Card dialog box.
6. In the tree at the left, click a hub line card or an upstream or downstream channel to
view the graph or statistics for that line card or channel.
84
NOTE: For a multichannel line card in SCPC return mode, the upstream channel in
the tree shows the name of the upstream SCPC carrier and the name of the
remote that is transmitting that carrier.
7. Click the buttons on the left to select data for the graph. (See page 86 for a description of
the buttons.)
8. Click the second tab to view the data as a multicolumn list.
Figure 97 on page 85 shows both the HLC Graph tab and the statistics from the second tab for
the eM1D1 line card selected in the tree. In the HLC Graph tab shown in the figure, the Temp
button is selected, resulting in a graphical display of the variation in line card temperature
over time. Selecting a different button (or multiple buttons) would result in a different graph.
Selecting a different line card or an individual upstream or downstream channel on the left
changes which buttons can be selected for the graph. The data displayed on the second tab
changes accordingly.
Figure 97. Hub Line Card Statistics: Graphical Display and Multicolumn List
85
The graphs and buttons available on the HLC Graph tab as well as the related information
displayed on the second tab depend on the line card or channel selected in the tree at the
left of the graph. For example, select a multichannel receive-only line card in SCPC return
mode to examine general line card statistics such as the line card temperature or number of
errors on the GIGE Ethernet port. Select a receive channel on that line card to examine
channel-specific statistics such as the number of bytes received on the SCPC channel and the
number of times TDM lock was lost.
Change the graphical display on the HLC Graph tab by toggling the buttons to the left of the
graph (Figure 96). The buttons work as follows:
The Hour, Min and Sec buttons change the scale of the x axis to hours, minutes or
seconds.
The All, Single and None buttons control which statistics are displayed on the graph:
Select All to automatically select all the statistics appropriate to the selected line
card or channel for display on the graph. After selecting All, click selected buttons to
turn them off one by one.
Select Single to turn the buttons representing individual statistics into toggle buttons.
For example, if the Single and Temp buttons are both selected, then only the
temperature is be displayed on the graph. Selecting the TxAtt button while the Single
button is selected changes the graph from temperature to transmit attempts. If the
Single button is not selected, both statistics are graphed.
The remaining buttons represent the various statistics that can be displayed on the graph.
Select a single statistic button or multiple statistics button. Buttons that are not
appropriate for the selected line card or channel cannot be selected.
NOTE: Hover the mouse pointer over any button for a textual description of the
buttons function.
86
Select Mouse Tracking. Then click and drag along the plot line to view the value of each
data point.
87
Figure 100. Hub Line Card Statistics for an SCPC Return Channel and for an XLC-M Line
Card
88
TDMA upstream performance statistics are collected for remotes that transmit on a TDMA
inroute.
SCPC upstream performance statistics are collected for remotes that transmit an SCPC
upstream carrier.
Upstream performance statistics are available from the following levels of the iMonitor Tree
view:
Remote
The number of traffic CRC errors in bursts received from the remote
89
90
Figure 102. iMonitor Upstream Performance Statistics Pane: TDMA and SCPC Channels
6. In the tree on the left, click a remotes upstream channel to view the graph or statistics
for that remote.
Figure 102 shows sample Upstream Performance Graphs for both a remote transmitting an
SCPC return channel (top) and for a remote transmitting on a TDMA upstream carrier
(bottom).
NOTE: If a remote changed between SCPC and TDMA upstream channels during
the reporting period, two upstream carriers will appear under the remote. Select
either channel to see the graph and statistics data for that carrier type.
91
7. Click the buttons on the left to select data for the graph. (See the description on
page 92.)
8. Click the second tab for a multicolumn list of the remotes Upstream Performance
Statistics.
Figure 103 shows sample data for remotes transmitting both TDMA and SCPC upstream
carriers.
92
The Hour, Min and Sec buttons change the scale of the x axis to hours, minutes or
seconds.
The All, Single and None buttons help control which statistics are displayed on the graph.
(For details see page 86.)
The remaining buttons represent the various statistics that can be displayed on the graph.
Select a single statistic button or multiple statistics button. Buttons that are not
appropriate for the return channel type are not selectable.
For TDMA Upstream Performance Statistics there are two groups of buttons with identical
names. Use the top group to select acquisition statistics; use the bottom group to select
traffic statistics. (This is illustrated in Figure 104 on page 93. TDMA buttons are shown on
the left and SCPC buttons are shown on the right.) For example, use the top Bursts button
to select acquisition bursts; use the bottom Bursts button to select traffic bursts.
NOTE: As shown in Figure 104, hover the mouse pointer over any button for a
description of the buttons function.
Figure 105. Remote Upstream Performance Statistics: Graph and Multicolumn List
93
Figure 107. Remote Upstream Performance Statistics for TDMA and SCPC Return Channels
94
95
7. Click the second tab to see the remotes Upstream Performance Statistics in the form of a
table.
Figure 108. Remote Performance Statistics CRC Errors: Graph and Multicolumn List
Figure 108 shows a graph of TDMA traffic CRC errors for a remote and the data used to build
the graph.
96
In addition to the graph on the SATCOM tab, the Remote Status tab and UCP tab show realtime or historical data in multicolumn lists. The data on the Remote Status tab is reported by
the remote. The data on the UCP tab is reported by the Protocol Processor during uplink
control processing. As with any multicolumn list, right-click in the display to copy multiple
rows from these tabs to paste into another application such as Excel.
97
3. To retrieve past data and then continue to receive real-time statistics, select a time
interval in the Get Past drop-down list.
4. Click OK.
The SATCOM pane contains three tabs (Figure 110). The Remote Status and UCP Info tabs
contain the raw data used to draw the SATCOM graph.
SATCOM Graph
Figure 110 shows an example of the graphs on the SATCOM tab.
98
NOTE: To adjust the color settings on the SATCOM graphs, right-click anywhere
inside the display and select Properties from the context menu.
The SATCOM tab is organized into three graphs. The displays show the following information:
Graph 2: The upstream signal-to-noise ratio adjusted for the symbol rate (C/N0) as
measured at the hub, superimposed on the remotes transmit power.
Graph 3: The symbol timing offset and frequency offset adjustments applied to the
remote by the Protocol Processor uplink control process.
Each graph contains heading text that shows the last values received (either real-time or from
the archive depending on the type of request). Close any of the displays by clicking on the X
in the upper-right corner of the graph.
NOTE: The maximum time range for this pane is one hour. This limit includes both
historical and real-time information.
99
NOTE: Remote Status on page 183 describes all upstream performance statistics
archived by the NMS.
Remote
To view the UCP statistics for a single remote or for multiple remotes on one set of graphs:
1. In the iMonitor tree, right-click a remote and select Remote UCP Graph, or right-click a
network or inroute group and select Grouped RemotesRemote UCP Graph.
2. For the Grouped Remotes option, in the Select Remotes dialog box, select the remotes
to view.
3. If desired, in the Select Remotes dialog box, select Historical and enter a Time Range,
or select a time interval in the Get Past drop-down list. In Figure 113, two hours of past
data are selected in the drop-down list.
100
101
102
Power Adjustment
Timing Offset
Frequency Offset
6. Click the corresponding button on the left to display or hide each graph.
7. Right-click inside the graph to view a menu of display options. General options for the
right-click menu are described on page 87.
103
3.8
Upstream QoS statistics for QoS groups and subgroups for any Inroute Group
Upstream QoS statistics for QoS groups and subgroups for any multichannel line card in
SCPC Return Mode
Downstream QoS statistics for QoS groups and subgroups for any Network
Downstream or upstream QoS statistics for individual remotes or for specific applications
running on individual remotes
104
Right-click an Inroute Group or Remote in the iMonitor tree and select Upstream QoS
Stats from the menu.
Right-click a Multichannel Receive Line Card in SCPC Return Mode and select
Upstream QoS Stats from the Menu.
105
106
107
Figure 121. Group QoS Distribution: Group QoS View vs. Remote View
The display opens to the Group QoS View by default. In the Group QoS View, the Group QoS
tree is ordered as in iBuilder, with the Bandwidth Groups at the top and the Virtual Remotes
at the bottom (Figure 121 on the left). In this view, Virtual Remotes at the bottom of the
screen are directly beneath their applications. Since the bandwidth for a physical remote is
distributed across all of its applications, the bandwidth for one remote is not grouped on the
display in the Group QoS View.
Clearing the GQoS View Mode selection in the right-click menu changes to the Remote View
(Figure 121 on the right). This view adds the physical remotes at the top of the display and
groups the subnodes by remote. Placing all the information for a physical remote in a single
column groups the remotes Virtual Remotes at the bottom of the display. The Remote View
makes it easy to see the amounts of bandwidth requested and used by individual remotes and
how that bandwidth is distributed across each remotes applications.
108
Figure 122. Group QoS Distribution: Viewing QoS Statistics for a Node
Click a node in the tree on the left or hover the mouse pointer over a node in the main display
to show the QoS statistics for that node at the bottom of the display. Figure 122 illustrates
these functions.
For each node, the display shows:
The Name of the QoS node (including its full path in the Group QoS hierarchy)
Requested Bandwidth
Allocated Bandwidth
Free Bandwidth
Configured CIR
Configured MIR
Configured Cost
NOTE: When viewing the data for a physical remote in the Remote View, the
values displayed for Requested Bandwidth, Allocated Bandwidth, and Free
Bandwidth are the sums of each value for all of the remotes Virtual Remotes.
Click a node in the tree to highlight the node in the tree and place a blue border around
the node in the main display.
Hover the mouse pointer over a node in the main display to place a red border around
that node in the main display.
Click a node in the main display to place a blue border around that node in the main
display and highlight the node in the tree.
109
In the Remote View, a QoS node is sometimes represented in multiple places in the main
display. Clicking that node in the tree or clicking a box in the main display highlights all of the
boxes for that QoS node. This is illustrated in Figure 123 for the Default Application.
Figure 123. Group QoS Distribution: Single Group QoS Node Divided Across Main Display
Base Measures
Right-click anywhere in the main display and select a Base Measure (Figure 124) to determine
the relative width of the nodes on the screen.
110
Static: The width of all subnodes of each parent node has the same width.
BW Requested: The width of the nodes is proportional to the bandwidth requested. (This
is the default Base Measure and is illustrated in Figure 120 on page 107.)
BW Free: The width of the nodes is proportional to the free (unused) bandwidth.
Config CIR: The width of the nodes is proportional to the configured Committed
Information Rate (CIR).
Config MIR: The width of the nodes is proportional to the configured Maximum
Information Rate (MIR).
Figure 124 shows the same set of remotes for base measures BW Allocated (on the left) and
Static (on the right).
Figure 125. Group QoS Distribution Base Measure: Bandwidth Allocated vs. Static
Note:
When a new Base Measure is selected, the name of the Group QoS Distribution
tab changes to reflect the selected measure. This is illustrated in Figure 126.
Figure 126. Group QoS Distribution: Tab Name Change for Base Measure
111
Figure 127. Group QoS Distribution: Display Controls and Filter Settings
Select or clear these options to change the display as follows:
GQoS View Mode switches between the GQoS View and Remote View as described in
Group QoS View versus Remote View on page 108.
Show Multicast shows or hides the Multicast Bandwidth Group for a downstream carrier.
(Not available for inroute groups.)
Show Remote Service Groups shows or hides all remote service groups configured for this
network or inroute group.
NOTE: Application Service Groups are always shown.
Toolbar shows or hides the toolbar buttons on the far left of the screen. (See Figure 120
on page 107.)
NOTE: The colored toolbar button
Distribution tab.
Averaged is discussed in Viewing Real Time and Historical Data on page 114. (This
selection is only available for historical data.)
112
Top Ten Rmt (Requested) shows the ten remotes that have requested the most
bandwidth. (This selection is only available in the Remote View.)
Top Ten Rmt (Allocated) shows the ten remotes that have received the most bandwidth.
(This selection is only available in the Remote View.)
Highlight CIR Not Met outlines in red all nodes that did not receive their full CIR.
Figure 128 shows the ten remotes that have received the most bandwidth in combination with
the Static Base Measure.
Figure 129. Group QoS Distribution: Filtering Remotes with the Filter Remotes Button
In the Select Remotes dialog box, move remotes between the Selected Remotes and
Available Remotes sections of the Select Remotes dialog box by selecting the remotes and
clicking the arrow buttons. Remotes in the Available Remotes section of the dialog box are
not shown in the Group QoS Distribution display.
113
As the average values of all statistics records in the historical time range
Figure 130. Group QoS Distribution: Selecting a Statistics Record with the Slider
Figure 130 shows the results of moving the slider to a specific time in the historical time
range with a Virtual Remote selected in the main display. When the slider is released, the
display is updated to show the record that includes the slider time.
114
Replay the statistics over the historical time range by clicking the buttons on the left of the
slider bar. The display automatically steps through the statistics records in the selected
direction.
3. Click
4. Click
5. Click
to replay the statistics in a continuous loop. Clear this selection to stop at the
end of the time range.
To view the statistics averaged over the historical time range:
1. Right-click anywhere in the main display and select Averaged from the menu.
Figure 132. Group QoS Distribution: Averaging Over the Historical Time Range
The Group QoS Distribution display is adjusted to represent the statistics averaged over
the historical time range.
2. Select any node to view the average statistics for that node.
NOTE: The slider is not visible when viewing statistics averaged over the time
range.
115
116
Figure 135. Group QoS Distribution: Moving the Zoom Box Horizontally
4. To widen the Zoom Box in the Zoom Window, right-click inside the Zoom Box and drag the
mouse pointer up.
5. To change the Zoom Box from a vertical slice of the display to a square box, right-click
anywhere in the Group QoS Distribution clear Zoom Horiz.
117
118
119
The Plot tab presents a graphical representation of the data on the List tab. By default,
three graphs appear: BW Requested, BW Allocated and BW Free.
NOTE: The graphs will not appear until a QoS node is selected in the tree view on
the left.
14. Select elements at different levels of the tree in the left-hand pane to control the
aggregation of the statistics displayed in the Plot and List tabs of the right-hand pane.
Figure 139 shows the total statistics aggregated over the selected Remote Service Group.
120
Click Hour, Min or Sec to change the scale of the x axis to hours, minutes or seconds.
Select Mouse Tracking and drag along the plot line to view the value of each data point.
121
Free BW Alloc shows the amount of bandwidth allocated to the subgroup in excess of the
requested bandwidth.
NOTE: The BW Req column only displays correct data when congestion is not
present.
122
[NMS]
sl_stats_report_enabled = 1
To view Service Level statistics in iMonitor:
1. Right-click a network, remote, inroute group, or SCPC multichannel line card in the
iMonitor tree and select Downstream QoS Stats or Upstream QoS Stats as desired.
2. In the Select dialog box, expand a Virtual Remote to see the Service Levels.
3. Select a Service Level or right-click the Virtual Remote to select all Service Levels as
illustrated in Figure 143).
123
Tx packets / sec shows the packets per second for the Service Level.
Rejected Packets shows the number of unreliable packets rejected for transmission
due to a full Service Level queue when Drop Oldest First is not selected for the
Service Level configuration in iBuilder.
Dropped Packets shows the number of unreliable packets dropped from the queue and
not transmitted when Drop Oldest First is selected for the Service Level configuration
in iBuilder.
7. Click the List tab for a multicolumn list of the statistics for the selected Service Level.
124
Control Panel
1. Right-click in the display area of the List tab and select Export to Excel or Export to CSV
from the menu.
2. In the Save As dialog box, browse to the folder in which to save the statistics.
3.9
Control Panel
The Control Panel is available only for individual remotes. It combines a wide variety of
information about one remote into a single, multi-tabbed display. When opened, the Control
Panel automatically requests real-time data for each tab in the pane. Real-time displays
continue to update until the Control Panel is closed. Individual tabs also provide the Historical
and Get Past tools for retrieving data from the archive database.
The Control Panel is composed of the following tabs:
The General tab shows configuration information organized into functional areas. It also
shows a real-time summary that updates continuously.
The Events/Conditions tab shows events and conditions for this remote in real-time or for
a specified time period.
125
Control Panel
The SATCOM tab shows the SATCOM graph for this remote. (See Figure 110 on page 98.)
The SAT Traffic tab shows upstream and downstream satellite traffic graphs for this
remote. (See SAT Traffic Graph on page 151.)
The IP Traffic tab shows upstream and downstream IP traffic graph and IP statistics for
this remote. (See IP Traffic Graph on page 156.) For L2oS networks, IP Traffic statistics
include NMS management IP traffic only.
The Probe tab opens the remote Probe for this remote. (See Using the Remote Probe on
page 57.)
The Remote Status tab shows up to one week of real-time or historical Remote Status
information for this remote. (See page 99.)
The UCP Info tab shows up to one week of real-time or historical UCP information for this
remote. (See Remote Status and UCP Information on page 99.)
The Latency tab opens a latency pane for this remote. (See Latency on page 80.)
The QoS tab shows the current QoS profile settings for this remote.
Figure 146 and Figure 147 show examples of two remote Control Panel tabs.
126
NOTE: A maximum of four Control Panels can be displayed at the same time.
ACM Gain
MODCOD distribution
MODCOD utilization
Tx Line Card
127
the Line Card level of the iMonitor tree. View the ACM Gain achieved by individual remotes by
launching the ACM Gain display from the Network, Inroute Group, or Remote level of the tree.
To view the ACM Gain for DVB-S2 outbound carriers or remotes:
1. Right-click a DVB-S2 network, inroute group, line card, or remote in the iMonitor tree and
select DVB-S2 StatsACM Gain from the menu.
2. When ACM Gain is selected from the Network or Inroute Group menu, the Select Remotes
dialog opens.
128
5. Click OK to launch the ACM Gain display. The ACM Gain tab is selected by default.
Figure 151. Selecting Remotes in the Left Pane of the ACM Gain Display
7. To change the list of remotes without relaunching the display, click the Filter button to
open the Select Remotes dialog box.
129
Select Mouse Tracking and drag along the plot line to view the value of each data
point
9. To see the ACM Gain data in a multicolumn list, click the List Data tab.
130
Low MC shows the minimum MODCOD of the DVB-S2 carrier as configured in iBuilder.
CCM kSym shows the number of kilosymbols that would have been required to transmit
the data if it had all been transmitted using Low MC as the MODCOD.
Actual kSym shows the number of kilosymbols that were actually required to transmit the
data using ACM.
ACM Gain shows the percent gain in efficiency achieved by comparing the CCM bandwidth
that would have been required with the actual bandwidth used.
The remaining columns show the number of kilobytes transmitted at each MODCOD.
131
NOTE: Click the Filter button to change the list of available remotes in the left
pane.
132
5. To see the MODCOD Distribution over time, click the Timeline tab.
133
A Bandwidth Utilization factor of 1 means that all selected statistics records report that
the remote received its downstream data at or above its configured Nominal MODCOD.
The higher the Bandwidth Utilization factor, the worse the bandwidth efficiency. For
example, a Bandwidth Utilization factor of 2 indicates that the remote used twice as
much satellite bandwidth as it would have required to achieve the same information rate
if it had operated at its Nominal MODCOD 100 percent of the time.
134
The Sparkline column provides a graphical indication of which MODCODs the remote
received during the reporting period. There is one vertical line per statistical record.
Each line represents the MODCOD index of the MODCOD reported in the corresponding
record. The MODCOD index range is 0 (QPSK 1/4) to 21 (16APSK 8/9). (See Table 10 on
page 138.) The height of each line is proportional to the index of the MODCOD
reported in the corresponding record.
To configure the settings that affect how the Sparkline data is displayed, right-click a
Sparkline and select options from the context menu. For details, see Customizing the
Display with the Sparkline Context Menu on page 138.
135
The Nominal column shows the Nominal MODCOD configured for the remote at the
time of the latest statistics record of the statistics sample. (The fields of the statistics
record are described on page 137.)
The Current column shows the MODCOD received by the remote in the latest
statistics record of the statistics sample.
The Utilize column shows the overall Bandwidth Utilization factor as calculated from
all records in the statistics sample. (See page 134 for an explanation of the Bandwidth
Utilization factor.)
5. Click the MODCOD tab for a graphical representation of the percentages of data received
at each MODCOD for the remote selected on the Message Structure tab.
136
The configured Nominal MODCOD of the remote at the time of the record
The Bandwidth Utilization factor (BW Utilization) calculated for that specific record.
(See page 134 for an explanation of the Bandwidth Utilization factor.)
137
MODCOD
QPSK 1/4
QPSK 1/3
QPSK 2/5
QPSK 1/2
QPSK 3/5
QPSK 2/3
QPSK 3/4
QPSK 4/5
QPSK 5/6
QPSK 8/9
10
QPSK 9/10
11
8PSK 3/5
12
8PSK 2/3
13
8PSK 3/4
14
8PSK 5/6
15
8PSK 8/9
16
8PSK 9/10
17
16APSK 2/3
18
16APSK 3/4
19
16APSK 4/5
20
16APSK 5/6
21
16APSK 8/9
138
139
Figure 167. MODCOD Utilization: Setting Size of Sparkline Column and Rows
Enter a Width to set the width of the Sparkline column in pixels. You cannot adjust the
column on the GUI to be smaller than this setting. Enter a Height to adjust the height of
the rows (in pixels) on the Message Column tab.
4. Select Apply Filter to open dialog box (Figure 168) to set the maximum number of lines in
a Sparkline.
Figure 168. MODCOD Utilization: Setting the Maximum Spark Lines for a Remote
In Max. Samples, enter the maximum number of lines to display in the Sparkline column
for the selected remote. For example, if 100 is entered for Max. Samples, only the latest
100 records are represented in the Sparkline column for that remote.
140
Perform these steps to monitor the SNR values being reported by remotes to the protocol
processor:
1. Right-click a DVB-S2 network or remote in the iMonitor tree and select DVB-S2 StatsSNR
Graph to open the Select Remotes dialog box.
141
The MODCOD column displays the best MODCOD at which the remote can currently
receive data
The Bitmap column is intended for use by iDirect engineers and support personnel. It
displays the bitmap sent from the protocol processor to the line card representing all
MODCODs at which the remote can currently receive data.
The SNR column displays the SNR values reported by the remote
142
ACM Packets Rx High/Low indicates the number of high and low priority ACM packets
received by the line card from the protocol processor that can be transmitted at a
given MODCOD.
ACM Packets Tx High/Low indicates the number of high and low priority ACM packets
received by the line card from the protocol processor for a specific MODCOD that have
been transmitted.
NOTE: In some cases, the line card may not send the data to the remote at the
remotes maximum MODCOD. To achieve the most efficient frame packing and to
minimize latency, an outbound frame may contain data for multiple remotes with
different maximum MODCODs. ACM Packets Tx High/Low indicates the number of
packets received from the protocol processor per MODCOD that have been
transmitted. It does not indicate whether or not the packets were actually
transmitted at the requested MODCOD.
143
LEGS Tx Data indicates the number of LEGS bytes transmitted at a given MODCOD.
LEGS Tx Padding indicates the number of LEGS padding bytes transmitted at a given
MODCOD.
The Sparkline column provides a graphical indication of the data in each category.
The four remaining columns (Current, Total, Min and Max) track the statistical data
as it is received by iMonitor in real time. All data is set to zero when the display is
first opened or when it is reset. (See Step 5 on page 145.) These columns show the
most recent value received (Current); the sum (Total) of all the values received; and
the minimum (Min) and maximum (Max) values received since opening the screen or
resetting the display.
2. To view the details of any type of statistical data, click the plus sign (+) to the left of the
statistics type. Figure 173 shows the expanded view of the low priority ACM packets
transmitted.
144
3. The Hub Debug Statistics display has two tabs. The row selected in the Message Structure
tab determines which statistics are displayed in the other tab. In Figure 174, the row
containing ACM Packets Rx Low is selected. This causes the corresponding data to be
displayed on the second tab. Notice in Figure 174 that the name of the second tab has
changed to match the selected structure.
Figure 174. Hub Debug Statistics: Selecting Structure for Second Tab
4. Click the tab on the right to view the statistics in real time. All ACM statistics are
displayed by MODCOD.
145
Protocol Processor
Blade
Line Card
Select Connect from the menu to open a terminal session to an element for detailed anomaly
investigation. Contact the iDirect Technical Assistance Center for further information on using
system consoles.
MAC and IP addresses for all remotes in the remotes inroute group.
146
rmtarp displays the MAC and IP addresses for all remotes in this remotes inroute
group. This does not include the remote you are connected to.
Figure 177. Viewing IP Routing and HDLC Information from the Remote Command Line
147
148
4.1
Traffic Statistics
This section describes the satellite statistics and IP statistics collected by the NMS. The
procedure for viewing the Satellite Traffic Graph is described in SAT Traffic Graph on
page 151. The procedure for viewing the IP Traffic Graph is described in IP Traffic Graph on
page 156.
149
To
Internet
Upstream Router
Protocol
Processor
To Internet
Traffic Statistics
150
Traffic Graphs
To Internet
Remote 1
Protocol
Processor
Upstream Router
Remote 2
Remote 3
4.2
Traffic Graphs
This section contains the step-by-step procedures for viewing the following displays in
iMonitor:
Satellite Traffic Graph
Networks
Inroute groups
Remotes
151
Traffic Graphs
152
Traffic Graphs
153
Traffic Graphs
The Hour, Min and Sec buttons change the scale of the x axis to hours, minutes or
seconds.
The Bits and Bytes buttons toggle the scale of the y axis to kilobits per second or
kilobytes per second.
The All and None buttons select all traffic types for the graphs or clear the display.
The Symbol button applies only to the Downstream graph for DVB-S2 ACM networks.
If the Symbol button is selected, the y axis shows the satellite traffic in kilosymbols
per second. Select Bits (Kbps) or Bytes (KBps) to view how the actual satellite
bandwidth consumed on an ACM carrier varies at any given data rate depending on
which MODCODs are being transmitted at the time. Click the Symbol button to view
the total satellite traffic independent of the MODCODs being transmitted.
The Totals button adds a line to the graphs showing the total traffic for all the
selected traffic types.
The last five buttons determine which traffic types are shown on the graphs. Select
any combination of traffic types: Reliable, Unreliable, Overhead, Multicast and
Broadcast.
8. To choose among various display options on the graph, right-click inside the window to
view the menu below.
154
Traffic Graphs
Select Show Parameters to open a statistics options section at the top of the pane
(Figure 184). These selections are described on page 154.
Select Scroll Lock to lock the upstream and downstream scroll bars together for historical
statistics.
Select Units to switch between kilobits per second and kilobytes per second.
Select Activity to choose which IP types to display, or to show the total IP traffic as a
single graph line.
Select Rate Limits to show configured upstream and downstream rate limits. (Satellite
Traffic statistics only.)
Select Copy to copy the current graph display to the client computer clipboard.
155
Traffic Graphs
Networks
Inroute groups
Remotes
IP Traffic Graph can be selected at all three levels of the tree. At the Network and Inroute
Group levels, Grouped RemotesIP Traffic Graph can also be selected.
Select IP Traffic Graph to show the aggregate total IP traffic for all the remotes included in
the graph. Select Grouped RemotesIP Traffic Graph to show the IP traffic of multiple
individual remotes side by side on the same graph.
To view the IP traffic graph:
1. Right-click a network, inroute group, or remote.
2. Click IP Traffic Graph or Grouped RemotesIP Traffic Graph. The Select Remotes
dialog box appears.
156
Traffic Graphs
157
Traffic Graphs
NOTE: IP Statistics Tables on page 177 describes all IP statistics archived by the
NMS.
8. Change the graphical display on the IP Graph tab by toggling the buttons on the left. (See
Figure 186.) The functions of the various buttons are documented on page 154.
9. Right-click anywhere in the graph to select from the context menu (Figure 188). Use this
menu to change the data displayed; change the scale of the graphs; view a legend for the
graphs; or change the look and feel of the display. See page 161 for a description of the
menu options.
158
Traffic Graphs
159
Traffic Graphs
Remotes area and the Available Remotes area. Only Selected Remotes are shown on the
main display.
13. When viewing Grouped RemotesIP Traffic Graph, click the Sort Remotes By button to
open the Sort Remotes By dialog box (Figure 191). Use this dialog box to sort the remotes
on the graph by the volume of traffic to or from the remote.
160
4.3
Select Change to change characteristics of the graph such as text color; the scale of the x
axis and y axis; the data refresh rate; and the units for the y axis.
Select Traffic to show some or all of the following traffic types on the graph: TCP, UDP,
ICMP, IGMP, HTTP, Other. Also select this option to graph the total traffic.
Select Copy Whole Plot to send the current graph to the client computer clipboard.
Select Copy Visible Area to send only the portion of the graph currently visible in
iMonitor to the client computer clipboard.
Select Max Points to limit the number of statistics records used to plot the graph.
Select Refresh Rate to change the data refresh rate for the graph.
Networks
Inroute Groups
161
2. Click SAT Bandwidth Usage to open the Select Remotes dialog box,
162
5 Reporting on Networks
iMonitor can create reports from historical data kept in the statistics archive. These reports
are described in this chapter.
Reports can be generated from the following elements in the iMonitor tree:
Networks
Inroute groups
Remotes
Line cards
The following reports are available from multiple levels of the iMonitor tree:
5.1
Remote Availability
163
164
8. In Time Range, select the time period for the report by selecting a Start Time and an End
Time. Enter time values using the text boxes or click the buttons to the right of the Start
Time and End Time to use the clock tool.
NOTE: By default, six months of data are stored in the statistics archive. To save
IP statistics for longer than six months, contact iDirects Technical Assistance
Center (TAC).
9. Move the Interval slider to specify the time interval represented by each message
returned from the server. This adjusts the granularity of the results depending on the type
of report.
The minimum interval available depends on the Start Time of the report. As the statistics
age, the NMS server automatically consolidates records to save disk space. Shorter
intervals may not be available if the Start Time is far in the past. By default, iMonitor
chooses the shortest possible interval for the selected Start Time. For more information
on how the NMS server consolidates usage records see Accessing the NMS Statistics
Archive on page 171.
10. In the Sort By drop-down list, specify an initial sort order for the report. After the report
is generated, it can be re-sorted by clicking the appropriate column heading.
11. Click OK to run the report. After the server has retrieved the data, iMonitor, displays the
report.
5.1.2 Results
Long Term Bandwidth Usage reports are organized into two tabs: Totals and Average. The
Totals tab shows total kilobytes allocated over the interval represented by each message
returned to iMonitor from the server. There is a total value for each interval at the end of
each row, and a grand total at the bottom of each column. The Average tab shows the same
data in kilobits per second.
Figure 196 shows an example of the Totals tab of the Sat Long Term Bandwidth Report. The
report in Figure 196 is not broken down by IP protocol. When individual IP protocols are
selected on the parameters dialog box (Figure 195), the report shows each protocol in its own
column.
165
Figure 196. SAT Long Term Bandwidth Usage Report: Totals Tab
To view the average data rates in kilobits per second for the same statistics, click the Average
tab.
Figure 197 shows an example of the Totals tab of the IP Long-Term Bandwidth Report. Like
the report in Figure 196, this report is not broken down by IP protocol.
166
Figure 198. SAT Long Term Bandwidth Usage Report: Average Tab
167
The values in these two columns (Figure 198) provide estimates of the bandwidth margins on
the upstream and downstream carriers. These values are estimates only; the actual channel
capacities may be slightly higher or lower depending on a number of factors. However, the
values are accurate enough to determine when to consider adding additional bandwidth to a
particular channel.
NOTE: The Downstream Percent of Max and Upstream Percent of Max columns are
only shown when no IP protocols are selected for the report.
The downstream estimate is reduced by 2.5% to account for overhead. Downstream overhead
includes HDLC framing, timeplans, UCP commands, etc. The theoretical maximum for a
downstream with a 2 Mbps information rate is 2 * .975 = 1.95 Mbps. For the upstream, the
following calculation is used to determine the theoretical maximum in bits per second:
(bytes per slot)*(8 bits per byte)*(slots per frame)*(1000/frame_len)
In the formula, bytes per slot does not include iDirect internal overhead. Also, this
calculation removes unique word and guard band overhead. In a typical network configuration
with small FEC blocks, a 658 Kbps information rate, a 125 ms frame, and 109 traffic slots, the
theoretical maximum would be:
(70 bytes per slot)*8*(109 slots)*(1000/125)= 488320 bps = 488.320 Kbps
The upstream theoretical maximum is an estimate only. Like the downstream estimate, the
actual maximum varies depending on a number of factors, such as the number of remotes in
the network, the minimum data rate for each remote, and IP packet sizes.
Note that a larger report interval may result in the calculation of a relatively lower
percentage of maximum capacity. This is due to the fact that the data rates are averaged over
the entire the interval, so spikes in activity tend to be hidden in the averages for longer
intervals.
5.2
Network
Inroute Groups
This example explains how to generate a Remote Availability report. Perform similar steps to
generate a Line Card Availability report.
To generate a Remote Availability report:
1. Right-click a network, inroute group, or remote in the iMonitor tree and select Remote
Availability to open the Select Remotes dialog box.
168
169
170
The total number of hours during the time range the remote was up
The total number of hours during the time range the remote was down
The averages of the up and down hours and percentages of all remotes in the report
A.1
All-zero IP statistics and SAT statistics are not logged to the archive. For example, these
statistics are not logged for remotes that are out-of-network. The long term bandwidth
reports and usage displays handle missing messages automatically.
NOTE: To access the statistics archive using ODBC, it may be necessary to modify
the reporting software to handle gaps in the data.
Latency measurements below a default threshold of 800 milliseconds are not logged to
the archive; only measurement times above this value are logged.
Consecutive latency time-outs are written to a single entry in the database along with a
count. For example, 10 consecutive latency time-outs are written as a single database
record with a count of -10.
171
Consecutive Sweep messages are written to a single entry in the database along with a
count. For example, 10 consecutive Sweeps are written as a single database record with a
count of 10.
All of these settings can be overridden or modified if necessary. Please contact iDirects
Technical Assistance Center for help changing the default archive behavior.
A.2
172
Account access can be further restricted. For example, connections can be limited to a
specific remote host. For help modifying a MySQL account to provide additional security,
contact the iDirect TAC at (703) 648-8151.
To view the NMS statistics archive using the read-only MySQL account, connect to the
nrd_archive database. Other connection details are the customer responsibility. There are a
number of database clients that support ODBC connections, each with their own
requirements. iDirect is not able to provide support for all the different ODBC clients in the
marketplace.
A.3
173
A.3.4 Timestamps
All raw data received from network elements is time stamped at the NMS prior to being
written to the database. All timestamp fields in the archive database are Linux time_t values,
which represent the number of seconds since January 1, 1970.
174
NOTE: For efficiency, archive data is divided into multiple tables for each data
type. Names of tables that contain data are derived from the base table names
shown in Table 11. When referring to tables in this section, the base table name
is used.
Table 11. Archive Database Tables
Base Table Name
Contains
Data
Saved For
raw_ip_stats
24 hours
ip_minute_stats
30 days
ip_hour_stats
6 months
lat_stats
latency measurement
1 week
nms_hub_stats
1 week
nms_remote_status
remote information
1 week
nms_ucp_info
1 week
event_msg
events sent from protocol processors, hub line cards, and remotes
1 week
state_change_log
hub line card and remote state changes (conditions raised and
lowered)
30 days
pp_state_change_log
30 days
chassis_state_change_log
30 days
raw_ota_stats
24 hours
ota_minute_stats
30 days
ota_hour_stats
6 months
raw_otacast_stats
24 hours
otacast_minute_stats
30 days
otacast_hour_stats
6 months
raw_mesh_stats
24 hours
mesh_minute_stats
30 days
mesh_hour_stats
6 months
remote_dvbs2_stats
30 days
hub_dvbs2_stats
30 days
pp_dvbs2_stats
30 days
nms_group_qos_stats
30 days
nms_sl_qos_stats
30 days
group_qos_hour_stats
6 months
group_qos_minute_stats
30 days
rev_activity
Unlimited
175
Data
Saved For
Contains
rev_state
Unlimited
sl_qos_hour_stats
6 months
sl_qos_minute_stats
30 days
nms_inroutes
1 week
raw_scpc_rmtrx_stats
24 hours
scpc_rmtrx_hour_stats
30 days
scpc_rmtrx_minute_stats
6 months
raw_tdma_rmtrx_stats
24 hours
tdma_rmtrx_hour_stats
30 days
tdma_rmtrx_minute_stats
6 months
inroute_composit_stats
1 week
composit_minute_stats
30 days
composit_hour_stats
6 months
inroute_slot_usage_stats
1 week
slot_usage_minute_stats
30 days
slot_usage_hour_stats
6 months
remote_power_stats
1 week
remote_power_minute_stats
30 days
remote_power_hour_stats
6 months
176
A.4
IP statistics
Over-the-air statistics
Mesh statistics
Statistics consolidation is a multi-step process designed to keep very old data without losing
information, and at the same time optimize disk space usage. As the statistics age, multiple
individual records are combined to form a single record. This method maintains the count of
total traffic sent through the system as the data ages; however, granularity of older statistics
is lost as the length of time increases between the statistics records retained.
Every day, using consolidation parameters from the configuration database, the statistics
consolidator processes the raw statistics tables as follows. (Typical values are used in this
example.)
1. Delete all records from the hour statistics table older than 4464 hours.
2. Consolidate all records from the minute statistics table older than 744 hours into one
record per hour and write that record to the hour statistics table.
3. Delete all records from the minute statistics table older than 744 hours.
4. Consolidate all records from the raw statistics table older than 24 hours into one record
per minute and write that record to the minute statistics table.
5. Delete all records from the raw statistics table older than 24 hours.
177
counts, so that the database records contain only the statistics for the time intervals between
records. The protocol processor continues to send messages to the NMS even if a remote is
out-of-network; the counts for these records contain all zeros.
NOTE: Since higher-layer protocols are transparent to L2oS, the IP statistics
tables only include NMS management traffic in Layer 2 networks.
NOTE: For convenience, HTTP traffic is separated from TCP traffic, but the TCP
counts include HTTP as well. For a total count of traffic, do not include the HTTP
values.
Table 12. IP Statistics Record Format
Column Name
Data Type
Meaning
timestamp
timestamp(14)
t_interval
int(10) unsigned
network_id
smallint(5) unsigned
unique_id
int(10) unsigned
modem_sn
smallint(5) unsigned
rx_tcp_kbyte
double
tx_tcp_kbyte
double
rx_udp_byte
double
tx_udp_kbyte
double
rx_icmp_kbyte
double
tx_icmp_kbyte
double
rx_igmp_kbyte
double
tx_igmp_kbyte
double
rx_http_kbyte
double
tx_http_kbyte
double
rx_other_kbyte
double
tx_other_kbyte
double
178
NOTE: By default, latency statistics are not stored if the measured latency is less
than 800 msec.
Table 13. lat_stats Record Format
Column Name
Data Type
Meaning
timestamp
timestamp(14)
network_id
smallint(5) unsigned
unique_id
int(10) unsigned
modem_sn
int(10) unsigned
rtt
double
ip_addr
varchar(20)
state
smallint(5) unsigned
currently unused
If remotes are not active in the network, i.e. they are deactivated or incomplete in iBuilder,
the latency server will not attempt to measure their latency and no data will be written to
this table in the database for them.
Data Type
Meaning
timestamp
timestamp(14)
network_id
smallint(5) unsigned
unique_id
int(10) unsigned
modem_sn
int(10) unsigned
scpc_num_tx_attempts
int(10) unsigned
scpc_num_tx_bytes
int(10) unsigned
scpc_num_tx_errors
int(10) unsigned
acq_crc_errors
int(10) unsigned
traffic_crc_errors
int(10) unsigned
179
Data Type
Meaning
bursts_detected
int(10) unsigned
bytes_rxed
int(10) unsigned
rx_overflow_frames
int(10) unsigned
rx_composite_power
double
rx_tunnel_errors
int(10) unsigned
tx_tunnel_errors
int(10) unsigned
rx_digital_gain
smallint(5) unsigned
scpc_snr_cal
double
scpc_sym_offset
int(11)
scpc_freq_offset
int(11)
scpc_frame_lock_status
tinyint(4)
lostlock_count
int(10) unsigned
fll_dac
int(10) unsigned
flags
int(10) unsigned
m_time_ticks
int(10) unsigned
m_temp
double
m_tx_power
double
rx_ddc_agc_dac_data
int(10) unsigned
buffer_overflow
int(10) unsigned
fe_agc_dac_val
int(10) unsigned
gige_tx_errors
int(10) unsigned
gige_rx_errors
int(10) unsigned
Transmit (tx) values are always zero for receive-only line cards, and receive (rx) values are
always 0 for transmit-only line cards. While traffic CRCs almost always indicate an anomaly
condition, acquisition CRC values above zero are normal when remotes are coming into the
network. By default iMonitor does not raise a warning condition on acquisition CRCs until they
exceed 200 in a 20 second period.
In addition to the nms_hub_stats message, multichannel line cards also send one statistics
record for each active TDMA or SCPC upstream channel. These channel-specific statistics are
written to the nms_inroutes table. Each nms_inroutes record associated with a nms_hub_stats
180
record contains the same timestamp as the nms_hub_stats record. In addition, the hlc_did
field in each nms_inroutes record equals the modem_sn field of the associated nms_hub_stats
record. (The modem_sn field of the nms_hub_stats record contains the line cards DID.
Although its Data Type is small int, MySQL reserves four bytes for this field.)
NOTE: Channel-specific fields in the nms_hub_stats table (such as lock status and
lock loss) are not valid for line cards in multichannel TDMA or SCPC mode.
Instead, this per-channel information is written to the nms_inroutes table
(Table 15) for each active return channel.
Table 15. nms_inroutes Table Format
Column Name
Data Type
Meaning
timestamp
timestamp(14)
network_id
smallint(5) unsigned
unique_id
int(10) unsigned
hlc_did
int(10) unsigned
inroute_type
int(10) unsigned
inroute_id
int(10) unsigned
digital_rx_gain
int(10) unsigned
rx_cof
int(10) unsigned
tdm_lock_status
int(10) unsigned
tdm_lost_lock_counter
int(10) unsigned
acq_errors
int(10) unsigned
traffic_crc_errors
int(10) unsigned
bursts_detected
int(10) unsigned
bytes_rxed
int(10) unsigned
rx_digital_gain
int(10) unsigned
181
Data Type
Meaning
timestamp
timestamp(14)
t_interval
int(10) unsigned
network_id
smallint(5) unsigned
remote_id
int(10) unsigned
remote_did
int(10) unsigned
acq_bursts
int(10) unsigned
acq_crc
int(10) unsigned
acq_mismatch
int(10) unsigned
acq_missing
int(10) unsigned
data_bursts
int(10) unsigned
data_crc
int(10) unsigned
data_mismatch
int(10) unsigned
data_missing
int(10) unsigned
keepalive
int(10) unsigned
182
Data Type
Meaning
timestamp
timestamp(14)
t_interval
int(10) unsigned
network_id
smallint(5) unsigned
remote_id
int(10) unsigned
remote_did
int(10) unsigned
data_packets
int(10) unsigned
data_hdlc_error
int(10) unsigned
data_mismatch
int(10) unsigned
keepalive
int(10) unsigned
Data Type
Meaning
timestamp
timestamp(14)
network_id
smallint(5) unsigned
unique_id
int(10) unsigned
modem_sn
int(10) unsigned
time_tics
bigint(20) unsigned
snr_cal
double
rx_power
double
power_in_dbm
double
temperature_celcius
double
digital_rx_power
double
lostlock_count
int(10) unsigned
fll_dac
int(10) unsigned
buc_48v
int(10) unsigned
rmtflags
int(10) unsigned
rx_cof
int(11)
scpc_rx_errors
int(10) unsigned
tdma_snr_cal
double
tdma_sym_offset
smallint(6)
tdma_freq_offset
int(11)
tdma_crc_errors
int(10) unsigned
rx_reliable_byte
int(10) unsigned
tx_reliable_byte
int(10) unsigned
rx_unreliable_byte
int(10) unsigned
183
Data Type
Meaning
tx_unreliable_byte
int(10) unsigned
rx_oob_byte
int(10) unsigned
tx_oob_byte
int(10) unsigned
local_fo_correction
int(11)
lost_pl_lock_count
int(10) unsigned
fast_fade_correction
int(10) unsigned
dvb_s2_crc8_error
int(10) unsigned
dvb_s2_crc32_error
int(10) unsigned
dvb_s2_raw_agc
int(10) unsigned
m_tuner_agc_gain
int(10) unsigned
clock_delta_count
int(10) unsigned
scpc_rtn_tx_oob_byte
int(10) unsigned
Meaning
timestamp
timestamp(14)
network_id
smallint(5) unsigned
unique_id
int(10) unsigned
modem_sn
int(10) unsigned
sym_offset
int(11)
power_adjustment
int(11)
freq_offset
int(11)
snr_cal
double
scpc_snr_cal
184
Data Type
double
Data Type
Meaning
timestamp
timestamp(14)
event_level
int(11)
event_class
int(11)
unique_id
int(10) unsigned
modem_sn
int(10) unsigned
time_tics
bigint(20) unsigned
msg
varchar(255)
Data Type
Meaning
timestamp
timestamp(14)
unique_id
int(10) unsigned
modem_sn
int(10) unsigned
185
Data Type
enum
Meaning
current state of the modem after this condition is processed;
values are:
OK
WARNING
ALARM
UNKNOWN
OFFLINE
ELSEWHERE
MESHALARM
SLEEP
STATE_NONE
NOTE: MySQL enumeration types are 1-based, not 0-based.
occurred_at
timestamp(14)
error_type
smallint(6)
error_severity
enum
EVTWarning
EVTAlarm
EVTCleared
EVTOffline
EVTElsewhere
EVTMeshAlarm
EVTSleep
EVTNone
NOTE: MySQL enumeration types are 1-based, not 0-based.
reason
varchar(255)
Interpreting the entries in the state_change_log table requires some understanding of how
the NMS manages conditions and overall element state. It is possible for multiple conditions to
be active for a single hub or remote at any given time. Consider the following scenario:
1. A remote is in steady state with no active conditions. The overall state of the unit is OK.
2. A rain storm in the remotes location causes the SNR of the downstream signal to drop
below the defined low limit. This is condition 1, a warning. The overall state of the unit
changes to WARNING.
3. The storm continues and the protocol processor loses contact with the remote. This is
condition 2, a warning. The overall state of the unit remains at WARNING.
4. The protocol processor is unable to re-gain contact with the remote and declares the
remote out-of-network. This is condition 3, an alarm. The overall state of the unit
changes to ALARM.
186
5. The NMS latency server stops receiving ICMP echo responses from the remote. This is
condition 4, an alarm. The overall state of the unit remains at ALARM.
There are now four simultaneously active conditions, and the overall state of the remote is
ALARM. Each time a new condition is raised for a remote, it is written to the database with
the current time of the NMS server machine in the timestamp field. The occurred_at field is
also given the same timestamp. All pre-existing conditions for that same element are rewritten with the same timestamp in the timestamp field. However, their occurred_at fields
remain unchanged, thus indicating the time those conditions were first raised. Using the
timestamp field as a key, it is possible to determine all active conditions for a remote at any
given time.
When conditions clear, they are rewritten to the state_change_log table with the severity
field set to EVT_CLEARED. When all conditions have cleared the overall state of the unit
returns to OK.
The only conditions with alarm severity are those that cause a service interruption. To
generate a remote up/down report for a given time period, parse the entries in this table and
ignoring all warning conditions.
Data Type
Meaning
timestamp
timestamp(14)
pp_id
int(10) unsigned
blade_id
int(10)unsigned
current_state
enum
OK
WARNING
ALARM
UNKNOWN
OFFLINE
STATE_NONE
Currently, only OK, ALARM, and UNKNOWN are
raised for protocol processors.
occurred_at
timestamp(14)
187
Data Type
enum
reason
Meaning
severity of the condition; values are
varchar(255)
EVTWarning
EVTAlarm
EVTCleared
EVTOffline
EVTNone
Entries in this table can be processed in essentially the same way as hub line card and remote
state changes. See Hub and Remote State Changes on page 185 for more details.
Meaning
timestamp
timestamp(14)
chassis_id
int(10) unsigned
current_state
enum
occurred_at
188
Data Type
timestamp(14)
OK
WARNING
ALARM
UNKNOWN
OFFLINE
STATE_NONE
reason
Data Type
enum
Meaning
severity of this condition; values are:
varchar(255)
EVTWarning
EVTAlarm
EVTCleared
EVTOffline
EVTNone
Data Type
Meaning
timestamp
timestamp(14)
t_interval
int(10) unsigned
network_id
smallint(5)
unsigned
unique_id
int(10) unsigned
modem_sn
int(10) unsigned
current_mc_idx
int(5) unsigned
rx_reliable_kbyte
double
tx_reliable_kbyte
double
double
double
rx_oob_kbyte
double
tx_oob_kbyte
double
rx_unreliable_kbyte
tx_unreliable_kbyte
189
Data Type
Meaning
timestamp
timestamp(14)
t_interval
int(10) unsigned
network_id
smallint(5) unsigned
current_mc_idx
int(5) unsigned
tx_unscaled_mcast_kbye
double
tx_bcast_kbyte
double
tx_mcast_kbyte
double
tx_bcast_ksym
double
tx_mcast_ksym
double
190
Data Type
Meaning
timestamp
timestamp(14)
t_interval
int(10) unsigned
network_id
smallint(5) unsigned
unique_id
int(10) unsigned
modem_sn
smallint(5) unsigned
rx_reliable_kbyte
double
tx_reliable_kbyte
double
rx_unreliable_kbyte
double
tx_unreliable_kbyte
double
rx_oob_kbyte
double
tx_oob_kbyte
double
Data Type
Meaning
timestamp
timestamp(14)
t_interval
int(10) unsigned
network_id
smallint(5) unsigned
remote_did
int(10) unsigned
current_modcod
smallint(5) unsigned
current_modcod_range
int(10) unsigned
available_modcod
smallint(5) unsigned
191
192
Data Type
Meaning
current_SNR
int(10) unsigned
bytes_sent_mc01
int(10) unsigned
bytes_sent_mc02
int(10) unsigned
bytes_sent_mc03
int(10) unsigned
bytes_sent_mc04
int(10) unsigned
bytes_sent_mc05
int(10) unsigned
bytes_sent_mc06
int(10) unsigned
bytes_sent_mc07
int(10) unsigned
bytes_sent_mc08
int(10) unsigned
bytes_sent_mc09
int(10) unsigned
bytes_sent_mc10
int(10) unsigned
bytes_sent_mc11
int(10) unsigned
bytes_sent_mc12
int(10) unsigned
bytes_sent_mc13
int(10) unsigned
bytes_sent_mc14
int(10) unsigned
bytes_sent_mc15
int(10) unsigned
bytes_sent_mc16
int(10) unsigned
bytes_sent_mc17
int(10) unsigned
bytes_sent_mc18
int(10) unsigned
bytes_sent_mc19
int(10) unsigned
bytes_sent_mc20
int(10) unsigned
bytes_sent_mc21
int(10) unsigned
bytes_sent_mc22
int(10) unsigned
bytes_sent_mc23
int(10) unsigned
bytes_sent_mc24
int(10) unsigned
bytes_sent_mc25
int(10) unsigned
bytes_sent_mc26
int(10) unsigned
bytes_sent_mc27
int(10) unsigned
bytes_sent_mc28
int(10) unsigned
Data Type
Meaning
timestamp
timestamp(14)
t_interval
int(10) unsigned
network_id
smallint(5) unsigned
hlc_did
int(10) unsigned
bytes_sent_mc01
int(10) unsigned
bytes_sent_mc02
int(10) unsigned
bytes_sent_mc03
int(10) unsigned
bytes_sent_mc04
int(10) unsigned
bytes_sent_mc05
int(10) unsigned
bytes_sent_mc06
int(10) unsigned
bytes_sent_mc07
int(10) unsigned
bytes_sent_mc08
int(10) unsigned
bytes_sent_mc09
int(10) unsigned
bytes_sent_mc10
int(10) unsigned
bytes_sent_mc11
int(10) unsigned
bytes_sent_mc12
int(10) unsigned
bytes_sent_mc13
int(10) unsigned
bytes_sent_mc14
int(10) unsigned
bytes_sent_mc15
int(10) unsigned
bytes_sent_mc16
int(10) unsigned
bytes_sent_mc17
int(10) unsigned
bytes_sent_mc18
int(10) unsigned
bytes_sent_mc19
int(10) unsigned
bytes_sent_mc20
int(10) unsigned
bytes_sent_mc21
int(10) unsigned
bytes_sent_mc22
int(10) unsigned
bytes_sent_mc23
int(10) unsigned
bytes_sent_mc24
int(10) unsigned
bytes_sent_mc25
int(10) unsigned
bytes_sent_mc26
int(10) unsigned
bytes_sent_mc27
int(10) unsigned
bytes_sent_mc28
int(10) unsigned
193
194
Data Type
Meaning
timestamp
timestamp(14)
t_interval
int(10) unsigned
network_id
smallint(5) unsigned
pp_id
smallint(5) unsigned
pp_blade_id
smallint(5) unsigned
target_hlc_id
smallint(5) unsigned
available_modcod
smallint(5) unsigned
bytes_sent_mc01
int(10) unsigned
bytes_sent_mc02
int(10) unsigned
bytes_sent_mc03
int(10) unsigned
bytes_sent_mc04
int(10) unsigned
bytes_sent_mc05
int(10) unsigned
bytes_sent_mc06
int(10) unsigned
bytes_sent_mc07
int(10) unsigned
bytes_sent_mc08
int(10) unsigned
bytes_sent_mc09
int(10) unsigned
bytes_sent_mc10
int(10) unsigned
bytes_sent_mc11
int(10) unsigned
bytes_sent_mc12
int(10) unsigned
bytes_sent_mc13
int(10) unsigned
bytes_sent_mc14
int(10) unsigned
bytes_sent_mc15
int(10) unsigned
bytes_sent_mc16
int(10) unsigned
bytes_sent_mc17
int(10) unsigned
bytes_sent_mc18
int(10) unsigned
bytes_sent_mc19
int(10) unsigned
bytes_sent_mc20
int(10) unsigned
bytes_sent_mc21
int(10) unsigned
bytes_sent_mc22
int(10) unsigned
bytes_sent_mc23
int(10) unsigned
bytes_sent_mc24
int(10) unsigned
bytes_sent_mc25
int(10) unsigned
bytes_sent_mc26
int(10) unsigned
Data Type
Meaning
bytes_sent_mc27
int(10) unsigned
bytes_sent_mc28
int(10) unsigned
Data Type
Meaning
timestamp
timestamp(14)
t_interval
int(10) unsigned
unique_id
int(10) unsigned
root_id
smallint(5) unsigned
is_vr
smallint(5) unsigned
direction
smallint(5) unsigned
bw_requested
double
bw_allocated
double
free_bandwidth
double
cir_not_satisfied
double
unused
req_not_satisfied
double
unused
loops
double
unused
Data Type
Meaning
timestamp
timestamp(14)
t_interval
int(10) unsigned
unique_id
int(10) unsigned
vr_id
smallint(5) unsigned
profile_id
smallint(5) unsigned
195
Data Type
Meaning
service_level_id
smallint(5) unsigned
direction
smallint(5) unsigned
tx_bytes
double
tx_packets
double
rejected_packets
double
dropped_packets
double
Data Type
Meaning
idx
int(10) unsigned
record index
network_id
smallint(6)
vno_group_id
int(10) unsigned
ofiles_only
tinyint(1)
transmit_rate
float(10,5)
last
timestamp(14)
start
timestamp(14)
nr_tries
int(10) unsigned
nr_remotes
int(10) unsigned
nr_down_rev
int(10) unsigned
flag_status
smallint(6)
credentials
int(10) unsigned
group_address
varchar(25)
196
Data Type
Meaning
idx
int(10) unsigned
record index
user
varchar(32)
nms user
remote_name
varchar(64)
remote_type
varchar(32)
Data Type
Meaning
remote_sn
int(10) unsigned
remote_did
int(11)
remote derived id
remote_family
enum
Values are:
UNKNOWN
NM2
2plus
activity_idx
int(11)
up_rev
int(10) unsigned
date
smallint(6)
rev_status
enum
unknown
cumulative
binary
options
combined
check_cumlative
check_binary
check_options
check_combined
197
Data Type
Meaning
timestamp
timestamp(14)
t_interval
int(10) unsigned
network_id
int(10) unsigned
inroute_group_id
int(10) unsigned
num_compositions
int(10) unsigned
selected
int(10) unsigned
composition_id
int(10) unsigned
figure_of_merit
float
m1_and_m2
int(10) unsigned
198
Data Type
Meaning
timestamp
timestamp(14)
t_interval
int(10) unsigned
network_id
int(10) unsigned
inroute_group_id
int(10) unsigned
num_inroutes
int(10) unsigned
num_remotes
int(10) unsigned
remote_did
int(10) unsigned
inroute_id
int(10) unsigned
total_slots_from_inroutes
int(10) unsigned
Data Type
Meaning
timestamp
timestamp(14)
t_interval
int(10) unsigned
network_id
int(10) unsigned
inroute_group_id
int(10) unsigned
length
int(10) unsigned
remote_did
int(10) unsigned
nomial_carrier_id
int(10) unsigned
power_headroom
int(10)
C_N0
int(10)
mc_and_symbols
int(10) unsigned
199
A.5
A.5.1 Background
Prior to iDS Release 6.1, each archive data type was represented by a single MySQL database
table. Using the raw_ip_stats table as an example, all IP statistics for all remotes were
written directly to this table as they arrived at the NMS. Historical queries for IP statistics
were performed on this table as well. In large networks, the table could grow to well over one
gigabyte. This large size, combined with a large amount of read and write operations, caused
a significant performance load on the NMS servers CPU and degraded response time in the
iMonitor and iBuilder GUIs.
To alleviate this situation, the NMS now uses a multiple-table storage scheme in which each
type of archived data is divided among multiple tables by time and groups of remotes.
Dividing tables in this manner is known as data striping. The following sections discuss this
implementation change in detail.
200
All Remotes
Time Table 0
Time Table 1
Time Table 2
a
at
S
p
tri
Time Table 3
ed
in
gm
se
ur
ho
6-
Time Table 4
Time Table 5
ts
en
Day 2
Day 3
Day 4
Day 5
Table 0
00:00 06:00
12:00 18:00
00:00 06:00
12:00 18:00
Table 1
06:00 12:00
18:00 24:00
06:00 12:00
18:00 24:00
Table 2
12:00 18:00
00:00 06:00
12:00 18:00
Table 3
18:00 24:00
06:00 12:00
18:00 24:00
Table 4
00:00 06:00
12:00 18:00
00:00 06:00
Table 5
06:00 12:00
18:00 24:00
06:00 12:00
Database
Table
Archive Operation
Server
Incoming Stats
201
Database
Tables
Database
Tables
Database
Tables
Database
Tables
Archive
Operation
Table
Selection
Algorithm
Incoming Stats
Server
Incoming Stats
Database
Tables
Database
Tables
202
The type of data IP statistics, events, condition changes, etc. As before, each type of
data has its own table structure
base_table_name
time_interval
second_dimension_table_number
time_table_number
table_type_id
Type of
statistics
data
The number
of time
periods kept
for this
statistics
type
The number of
tables per
time period
kept for the
second
dimension
data type ID
The time
segment
interval in
each table,
in minutes
The second
dimension data
type ID
360
chassis_state_change_log
chassis_id
360
event_msg
unique_id
360
lat_stats
unique_id
360
nms_hub_stats
unique_id
360
nms_remote_status
unique_id
360
nms_ucp_info
unique_id
360
pp_state_change_log
blade_id
360
raw_ip_stats
unique_id
360
raw_ota_stats
unique_id
360
raw_otacast_stats
network_id
10
360
state_change_log
unique_id
11
360
ip_minute_stats
unique_id
12
360
ip_hour_stats
unique_id
13
360
ota_minute_stats
unique_id
14
360
ota_hour_stats
unique_id
15
360
otacast_minute_stats
unique_id
16
360
otacast_hour_stats
network_id
17
360
raw_mesh_stats
unique_id
203
360
mesh_minute_stats
unique_id
19
360
mesh_hour_stats
unique_id
20
360
hub_dvbs2_stats
hlc_id
21
360
pp_dvbs2_stats
pp_blade_id
22
360
remote_dvbs2_stats
remote_did
23
360
nms_sl_qos_stats
unique_id
24
360
nms_group_qos_stats
unique_id
25
360
sl_qos_minute_stats
unique_id
26
360
sl_qos_hour_stats
unique_id
27
360
group_qos_minute_stats
unique_id
28
360
group_qos_hour_stats
unique_id
29
360
dev_state_change_log
unique_id
30
360
raw_tdma_rmtrx_stats
network_id
31
360
tdma_rmtrx_minute_stats
network_id
32
360
tdma_rmtrx_hour_stats
network_id
33
360
raw_scpc_rmtrx_stats
network_id
34
360
scpc_rmtrx_minute_stats
network_id
35
360
scpc_rmtrx_hour_stats
network_id
36
360
nms_inroutes
unique_id
37
360
inroute_slot_usage_stats
inroute_group_id
38
360
slot_usage_minute_stats
inroute_group_id
39
360
slot_usage_hour_stats
inroute_group_id
40
360
remote_power_stats
inroute_group_id
41
360
remote_power_minute_stats
inroute_group_id
42
360
remote_power_hour_stats
inroute_group_id
43
360
inroute_composit_stats
inroute_group_id
44
360
composit_minute_stats
inroute_group_id
45
360
composite_hour_stats
inroute_group_id
204
Database Values:
ttn = TABLE_INFO.time_table_number
tis = (TABLE_INFO.time_interval * 60)
// convert to seconds
sdtn = TABLE_INFO.second_dimension_table_number
btn = TABLE_INFO.base_table_name
Variables:
t
= <timestamp> (Linux time_t)
id
= unique_id of element (e.g. remote)
Calculate the current Remote Index value
remote_index = id % sdtn
Calculate the current Time Index value
time_index = (t base_time) / tis) % ttn
Calculate the current Table Index value
table_index = (ttn * remote_index) + time_index
Derive the appropriate Table Name
table_name = btn <concat> _ <concat> table_index
For example, table_name = event_msg_3
205
Existing
Data
raw _ip_stats_3
Existing
raw _ip_stats
data
Empty
raw _ip_stats_4
raw_ip_stats_5
206
-ad
-DD
-suffix
Running the script with no arguments as shown below renames the existing tables by adding
the suffix old. For example, event_msg_1 becomes event_msg_1_old. After verifying the
data in the new format, remove the renamed tables by entering the command:
./DB-Migration.pl
This converts existing data to new table structure.
207
208
3. When running Windows XP with Service Pack 2, right-click the security message at the top
of the calculator window and select Allow Blocked Content. Then click Yes in the
warning dialog box.
209
210
The Base Table Name (identical to the base_table_name in the TABLE_INFO table on
page 203) represents the table definition for the table set that contains all statistics of
this type. Before calculating the results, select the Base Table Name of interest from this
list.
Time to Keep Data (hrs) represents the amount of time in hours to retain the data for
this Base Table Name before it is overwritten. You can modify this parameter based on
the requirement to keep records of this type on the NMS server and available disk space.
Maximum Table Size (MB) is used to calculate the optimal number of tables that should
be created for this Base Table Name. This parameter is not stored in the database. It is a
limit used by the calculator to help compute the best results. In general, use the default
setting.
Number of Records per Minute is the rate per minute at which records of this type are
being logged for each remote (or other device) in the table set. This is not a configurable
parameter and it varies dynamically with network load. If you have measured a value for
the network for which to optimize the table set, change this parameter to reflect that
value. Otherwise, use the default setting.
Record Size (in bytes) is the size of the database record for this Base Table Name. In
general, use the default setting.
After entering all parameters, click the Calculate Table_Info data button to calculate the
following results:
Time Table Number represents the optimal number of time segments recommended for
this Base Table Name based on the parameters entered. This result corresponds to the
time_table_number in the TABLE_INFO table shown in Table 38 on page 203.
Second Dimension Name represents the number of tables per time period recommended
for this Base Table Name based on the parameters entered. This result corresponds to
the second_dimension_name in the TABLE_INFO table.
Time Interval (hrs) represents the length of time for each time segment recommended
for this Base Table Name based on the parameters entered. This result corresponds to
the time_interval in the TABLE_INFO table.
211
212
TABLE_INFO.second_dimension_table_number = 1
This allows us to ignore this dimension. (Anything modulo 1 equals 0, so there is no
second dimension component to the table index.)
Query start time (start) = 2006-11-20 10:00:00 = 1164016800
Query end time (end) = 2006-11-20 14:00:00 = 1164031200
Calculate all table indexes:
To get the range of table indexes, calculate the index of the query start and end times. Those
two indexes, and everything in between, must be included in the queries.
The first table index is derived from start:
Idx_0
Idx_N
213
214
215
216
B.1
Alarms
Table 39 lists alarms, their descriptions and recommended actions.
Table 39. Alarms
Alarm
Chassis Down
Description
The hub chassis
controller interface
has failed or
become unavailable
from the NMS
Action, Troubleshooting
Note: It is likely that the hub line cards are still operating.
217
Warnings
Description
PP Down
Remote Layer 3
Verify that the NMS server can communicate with the line
cards across upstream router (ping, tracert).
Remote is not in
network (out of
network or link layer
down)
Remote is not
responding to ICMPs,
i.e. has missed 3
ICMPs in a row.
Protocol Processor is
not responding
Remote Layer 2
B.2
Action, Troubleshooting
Warnings
Warnings signal a condition that could possibly result in a future interruption in service if not
handled in a timely fashion. Table 40 lists a subset of warnings, their descriptions and
recommended actions. See Table 6 on page 33 for comprehensive lists of warnings for each
element.
NOTE: The following alarms are classified as warnings in the NMS:
PowerAlarm(1/2), FanAlarm, RCM(A/B)Alarm.
NOTE: Warning limits can be configured using iBuilder. For details on setting
warning limits, see the iBuilder User Guide.
218
Warnings
Warning Condition
PowerAlarm1
Description
Hub chassis power supply 1 failed.
Action, Troubleshooting
Replace power supply 1
FanAlarm
RCMAAlarm
Hub Line
Card
RX_OVERFLOW_FRAMES
DOWNSTREAM_PPS_OVERDRIVE
Downstream packets-per-second
count above fixed limit
BACKPLANE_LOST_10MHZ
219
Warnings
Warning Condition
Description
Action, Troubleshooting
ACQ_HUB_MODEM_CRC
CALIBRATED_TX_POWER
CERTIFICATE_HAS_EXPIRED
CERTIFICATE_INVALID
CERTIFICATE_WILL_EXPIRE
DOWNSTREAM_SNR
LATENCY
LOCAL_LAN_DISCONNECT
Call customer.
MOBILE_LOST_GPS
REMOTE_OFFLINE
SYMBOL_OFFSET
TEMP_LIMIT
Call customer.
TRAFFIC_HUB_MODEM_CRC
UCP_LOST_CONTACT
UPSTREAM_SNR
Contact customer.
220
Warnings
221
Warnings
222
C.1
Statistical information for all remotes and line cards from the NRD Server
The SNMP Proxy Agent Management Information Base (MIB) supports both SNMP Get requests
for polling and SNMP traps for asynchronous notification of status changes. The MIB is
automatically updated to reflect changes in element status and/or configuration, including
the addition and deletion of network elements. It also collects statistical information
regarding network elements.
The SNMP Proxy Agent is automatically installed on the NMS server as part of the iDirect
software release and is included in the normal NMS server startup and shutdown procedure.
223
Figure 209 illustrates how the SNMP Proxy Agent fits into the overall NMS architecture
C.2
224
Available Information
ID
Name
Teleport ID
Current State
List of Warnings
List of Alarms
Available Information
Chassis
ID
Name
Current State
List of Warnings
List of Alarms
DID
Protocol Processor ID
Network ID
Remote Modem
Teleport ID
Remote ID
Inroute Group ID
Name
IP Address
Slot Number
Chassis ID
Type ID
Current State
List of Warnings
List of Alarms
Current Status
Geographic Location
Coordinates
225
Beginning with iDirect Release 7.0, the SNMP MIB supplies the statistical information in
Table 42 for iDirect network elements.
Table 42. iDirect MIB Statistical Information
Statistics Type
Available Information
Data Class
IP Statistics
Remote DID
Not Applicable
Running Total
Running Total
Running Total
Running Total
Running Total
Running Total
Running Total
Running Total
Running Total
Running Total
Running Total
Running Total
Remote DID
Not Applicable
Overwrite
Running Total
Running Total
Running Total
Running Total
Running Total
Running Total
Running Total
Running Total
Running Total
Running Total
226
Available Information
Data Class
Remote UCP
Remote DID
Not Applicable
Upstream C/N0 in dB
Overwrite
Overwrite
Symbol Offset
Overwrite
Frequency Offset in Hz
Overwrite
Downstream SNR
Overwrite
Remote DID
Not Applicable
Remote Name
Not Applicable
Remote SN
Not Applicable
IP address
Overwrite
Latency in seconds
Overwrite
Network Name
Not Applicable
227
Available Information
Data Class
Hub Statistics
Not Applicable
Type SN
Not Applicable
Tx attempts
Running Total
Tx bytes
Running Total
Tx errors
Running Total
Running Total
Running Total
Bursts
Running Total
Rx bytes
Running Total
Rx power
Overwrite
dma reset
Running Total
tunnel rx errors
Running Total
tunnel tx errors
Running Total
Tx Power
Overwrite
Temperature
Overwrite
Time Ticks
Running Total
AGC Gain
Overwrite
MC AGC Gain
Overwrite
Overwrite
Buffer Overflow
Overwrite
Overwrite
Running Total
Running Total
Overwrite
Overwrite
Overwrite
Running Total
Running Total
Running Total
TDMA bursts
Running Total
TDMA Rx bytes
Running Total
TDMA Rx gain
Overwrite
228
Available Information
Data Class
Remote Status
Remote DID
Not Applicable
Down SNR in dB
Overwrite
Tx power in dBm
Overwrite
Rx power in dBm
Overwrite
Digital rx gain in dB
Overwrite
Overwrite
Overwrite
Temperature
Overwrite
TDM lost
Running Total
Running Total
Time ticks
Overwrite
LAN Port
Overwrite
Ethernet mode
Overwrite
Ethernet speed
Overwrite
Ethernet auto-negotiate
Overwrite
Terminal session
Overwrite
iSite session
Overwrite
In Mesh
Overwrite
Running Total
CRC 8 Errors
Running Total
CRC 32 Errors
Running Total
NCR Lost
Running Total
Running Total
Running Total
Overwrite
Overwrite
Overwrite
Running Total
Running Total
Running Total
Running Total
229
Available Information
Data Class
Running Total
Running Total
Running Total
Running Total
Running Total
Running Total
230
Remote DVB-S2
Statistics
Remote DID
Overwrite
Overwrite
Minimum MODCOD
Overwrite
Maximum MODCOD
Overwrite
Curremt MODCOD
Overwrite
Available MODCODs
Overwrite
Current SNR
Overwrite
Bytes on MODCOD 01
Running Total
Bytes on MODCOD 02
Running Total
Bytes on MODCOD 03
Running Total
Bytes on MODCOD 04
Running Total
Bytes on MODCOD 05
Running Total
Bytes on MODCOD 06
Running Total
Bytes on MODCOD 07
Running Total
Bytes on MODCOD 08
Running Total
Bytes on MODCOD 09
Running Total
Bytes on MODCOD 10
Running Total
Bytes on MODCOD 11
Running Total
Bytes on MODCOD 12
Running Total
Bytes on MODCOD 13
Running Total
Bytes on MODCOD 14
Running Total
Bytes on MODCOD 15
Running Total
Bytes on MODCOD 16
Running Total
Bytes on MODCOD 17
Running Total
Bytes on MODCOD 18
Running Total
Hub DVB-S2
Statistics
Available Information
Data Class
Bytes on MODCOD 19
Running Total
Bytes on MODCOD 20
Running Total
Bytes on MODCOD 21
Running Total
Bytes on MODCOD 22
Running Total
Bytes on MODCOD 23
Running Total
Bytes on MODCOD 24
Running Total
Bytes on MODCOD 25
Running Total
Bytes on MODCOD 26
Running Total
Bytes on MODCOD 27
Running Total
Bytes on MODCOD 28
Running Total
Running Total
Running Total
DID
Overwrite
Running Total
Running Total
Running Total
Overwrite
Bytes on MODCOD 01
Running Total
Bytes on MODCOD 02
Running Total
Bytes on MODCOD 03
Running Total
Bytes on MODCOD 04
Running Total
Bytes on MODCOD 05
Running Total
Bytes on MODCOD 06
Running Total
Bytes on MODCOD 07
Running Total
Bytes on MODCOD 08
Running Total
Bytes on MODCOD 09
Running Total
Bytes on MODCOD 10
Running Total
Bytes on MODCOD 11
Running Total
Bytes on MODCOD 12
Running Total
Bytes on MODCOD 13
Running Total
Bytes on MODCOD 14
Running Total
Bytes on MODCOD 15
Running Total
Bytes on MODCOD 16
Running Total
231
Available Information
Data Class
Bytes on MODCOD 17
Running Total
Bytes on MODCOD 18
Running Total
Bytes on MODCOD 19
Running Total
Bytes on MODCOD 20
Running Total
Bytes on MODCOD 21
Running Total
Bytes on MODCOD 22
Running Total
Bytes on MODCOD 23
Running Total
Bytes on MODCOD 24
Running Total
Bytes on MODCOD 25
Running Total
Bytes on MODCOD 26
Running Total
Bytes on MODCOD 27
Running Total
Bytes on MODCOD 28
Running Total
Running Total
232
Remote DID
Overwrite
Rx statistics type
Overwrite
Running Total
Running Total
Running Total
Running Total
Running Total
Running Total
Running Total
Running Total
Running Total
Running Total
Running Total
Running Total
Running Total
Running Total
233
Generate When...
Severity
Network
Elements
snmpProxyStart
N/A
snmpProxyStop
N/A
upstreamSNR
Warning
Remotes
downstreamSNR
Warning
Remotes
tempLimit
Warning
Remotes
latency
Warning
Remotes
symbolOffset
Warning
Remotes
ethernetUnplugged
Warning
Remotes
ucpLostContact
Warning
Remotes
lldown
Alarm
Remotes
ucpOutOfNetwork
Alarm
Remotes
latTimeout
Alarm
Remotes
remoteOffline
Offline
Remotes
lackHubStats
Alarm
Hub Modems
acqHubModemCRC
Warning
Hub Modems
trafficHubModemCRC
Warning
Hub Modems
ppStateTrap
Alarm
Protocol Processor
powerAlarm1, 2, 3
Warning
Chassis
fanAlarm
Warning
Chassis
chassisDown
Alarm
Chassis
scpcRxErrors
Warning
Remotes
fllDacErrors
Warning
Remotes
234
Generate When...
Severity
Network
Elements
rxOverflowFramesHubModem
Warning
downstreamPpsOverdrive
Warning
backplaneLost10Mhz
Warning
calibratedTxPower
Warning
Remotes
txFrequency
Warning
Remotes
mobileLostGps
Warning
Remotes
lcFailure
Alarm
meshError
Alarm
Remotes
meshTdmLockLost
Alarm
meshHubRxScpcSnr
Warning
meshHubRxTdmaSnr
Warning
lineCardAGCOutOFRange
Warning
meshRmtRxScpcSnr
Warning
Remotes
meshRmtRxTDMASnr
Warning
Remotes
remoteAgcOutOfRange
Warning
Remotes
rcmAAlarm
Warning
Chassis
rcmBAlarm
Warning
Chassis
lostChassisConnection
Warning
Chassis
microChassisOverTemp
Warning
Four-Slot Chassis
microRCMANotPresent
Warning
Four-Slot Chassis
microRCMAFault
Warning
Four-Slot Chassis
microRCMBNotPresent
Warning
Four-Slot Chassis
microRCMBFault
Warning
Four-Slot Chassis
microPwrAlarmABad
Warning
Four-Slot Chassis
microPwrAlarmAOverTem
Warning
Four-Slot Chassis
235
Generate When...
Severity
Network
Elements
microPwrAlarmBBad
Warning
Four-Slot Chassis
microPwrAlarmBOverTemp
Warning
Four-Slot Chassis
microFSMNotPresent
Warning
Four-Slot Chassis
microFSMFault
Warning
Four-Slot Chassis
microFSMFanFault
Warning
Four-Slot Chassis
microIFMNotPresent
Warning
Four-Slot Chassis
microIFMFault
Warning
Four-Slot Chassis
microAlarmDisabled
Warning
Four-Slot Chassis
microOPMAFaul
Warning
Four-Slot Chassis
microOPMBFault
Warning
Four-Slot Chassis
reset
Warning
Remote/Line Card
unready
Warning
Line Card
flash
Flash Warning
Warning
Remote/Line Card
activationStatus
Activation Status
Alarm
Remote
elsewhereError
Remote is Elsewhere
Elsewher
e
Remote
backplaneLostSOF
Warning
Chassis
rmtMAXTxPwr
Warning
Remote
bladeCPUHigh
Warning
PP Blade
rmtSleep
Alarm
Remote
hubTenMHzAlarm
Alarm
Line Card
gigeFailed
Alarm
Line Card
gigeHealth
Warning
Line Card
rxOnly
Rx only
Remote
crc8Errors
Warning
Remote
crc32Errors
Warning
Remote
ravenFailed
Raven failed
Alarm
Remote/Line Card
bladeNoEncLic
Warning
PP Blade
rmtAcqBurst
Warning
Remote
rmtCAWillExpire
Warning
Remote
rmtCAExpired
Warning
Remote
rmtCAInvalid
Warning
Remote
236
Generate When...
Severity
Network
Elements
rmttxTDMAAcqCrc
Warning
Remote
rmttxTDMADataCrc
Warning
Remote
rmttxTDMAAcqMismatch
Warning
Remote
rmttxTDMADataMismatch
Warning
Remote
rmttxTDMADataMissing
Warning
Remote
rmttxSCPCLostLock
Alarm
Remote
rmttxSCPCHdlcError
Warning
Remote
rmttxSCPCDataMismatch
Warning
Remote
rmtStatusChange
Warning
Remote
tristateIdle
Warning
Remote
tristateDormant
Warning
Remote
powerAlarm1
Warning
Chassis
powerAlarm2
Warning
Chassis
powerAlarm3
Warning
Chassis
237
C.3
238
snmpbulkget
snmpbulkwalk
snmpcmd
Not a command, but a manual page that describes the common options for the
SNMP commands
snmpconf
snmpdelta
snmpdf
snmpget
snmpgetnext
snmpnetstat
snmpset
snmpstatus
snmptable
snmptest
snmptranslate
snmptrap
snmpwalk
For more information on any of the commands in this list, log in to the NMS server machine
and type the following command:
# man <command name>
This displays the Linux manual entry or man page for the specified command that provides
usage details, output descriptions, etc. Note that some of these commands do not display
anything about iDirect networks, but instead display Linux system characteristics, such as disk
space and network status.
239
240
Index
A
accepting changes automatically 6
accepting changes, disabling auto-accept changes 6
Adaptive TDMA
available displays 66
C/No and thresholds for remotes 74
C/No distribution for inroute groups 72
calculation of target C/No threshold for upstream
carrier 72
figure of merit for selecting IGCs 71
IGC usage display 69
timeplan display 66
alarms
see conditions
archive, see statistics archive
audio notification 16
audio notification for conditions
disabling 17
enabling 16
B
blades
cpu usage 64
monitoring 55
button
accept changes 7
transmissions 95
cw carrier
enabling from remote probe 60
modifying timeout duration 62
D
database replication
recovering from failure condition 35
warnings sent to iMonitor 35
DVB-S2
monitoring ACM gain 127
monitoring carrier MODCOD distribution 131
monitoring MODCOD distribution over time 133
monitoring remote MODCOD utilization 134
monitoring SNR of remotes 140
viewing hub line card statistics 142
E
elements
placing under observation 38
events
examples 47
events and conditions 29
F
find toolbar 19
G
C
conditions
acknowledging 18
alarms and warnings on elements 32
audio notification 16
condition log tab 31
interpreting 45
observation view tab 31
viewing 40
conditions and events 29
conditions pane 24, 31
configuration changes 25
connecting to network elements 146
CRC errors
Identifying Rx errors on line cards caused by remote
geographic map
geographic map no longer supported i
globe
hiding elements 11
sorting elements 11
tree 11
graphs
Group QoS distribution 106
Group QoS plot 119
hub line card 86
IP traffic 156
SAT traffic 151
SATCOM 96
UCP 100
upstream performance 91
241
Group QoS
enabling upstream service level statistics 122
explanation of QoS statistics displayed 122
explanation of Service Level statistics displayed 124
exporting statistics to excel or CSV 125
GQoS distribution display
base measures defined 111
changing the zoom to a square box 117
data displayed per node 109
described 107
display controls and filters 112
filter settings 112
GQoS view vs. remote view 108
methods for viewing historical data 114
real time vs. historical displays 114
replaying historical statistics 115
selecting a base measure 110
using the horizontal zoom 116
viewing bandwidth for individual QoS nodes or
remotes 109
viewing top ten remotes 113
zooming in on the bandwidth pool 116
limitation of BW Req statistic 122
selecting service levels for which to view
statistics 123
viewing service level statistics 122
viewing statistics 104
viewing statistics for a single node 106
viewing statistics for a single remote 105
H
HDLC addresses, viewing on remotes 146
I
iBuilder
description 2
installing 4
idle and dormant states
viewing real-time status 25
iMonitor
description 2
launching 5
using the interface 10
iMonitor Tree 14
see also: tree
installation
NMS applications 4
242
L
latency, monitoring round-trip 80
launching iMonitor 5
legend 24
line card data snapshot 53
line cards
HLC graph display 86
identifying remotes causing Rx CRC errors on 95
statistics on 82
viewing statistics 83
viewing statistics on multichannel line cards 85
logging in
passwords 5
to other servers 6
M
main toolbar 19
mesh
not supported in this release 1
N
network condition snapshot 47
network data snapshot 53
NMS
client applications 2
iVantage NMS components i
main components 1
multiple users accessing 6
servers used 3
NMS database
overview 172
O
observation
placing elements under 38
offline state 32
P
panes
conditions 24
configuration changes 25
legend 24
probe 57
See also dialog boxes
selecting columns for viewing 26
sorting columns in 12
passwords 5
pn carrier
enabling from remote probe 60
modifying timeout duration 62
probe 57
adjusting remote transmit power 59
functions of 57
transmitting a modulated or unmodulated
carrier 60
R
remote status, differences in Rx power reporting 97
remotes
viewing IP and HDLC information on 146
viewing upstream performance statistics per
remote 88
replication
recovering from failure condition 35
warnings sent to iMonitor 35
reports 163 170
line card availability 168
long-term bandwidth usage 163
remote availability 168
requirements
system 4
right-click
menu options 19
S
SAT long term bandwidth usage 163
SAT traffic graph 151
SATCOM graph 96
saving data to files 8
saving workspaces 21
selecting columns for viewing 26
servers 3
snapshots 47
SNMP
iDirect MIB 224
iDirect traps defined 234
resetting MIB statistics 233
setting up traps 237
statistics in MIB 224
support on iDirect 223 239
sorting columns 12
sorting the tree 13
statistics
line card statistics 82
upstream performance 88
statistics archive
accessing
basic information 173
changing the table structure 207
converting data between table formats 206
installing the partitioning calculator on your PC 208
optimized storage 171
partitioning the database 207
querying the restructured database tables 212
restructuring for release 6.1 200
table details 177
using the partitioning calculator 208
status bar 21
system requirements 4
T
teleport condition snapshot 47
time periods
for requesting data 7
243
244
U
UCP graph 100
upstream carriers
Rx CRC errors on 95
statistics on 89
users
multiple 6
W
windows, See panes
See also dialog boxes
workspaces
saving and reloading 21
iDirect
13861 Sunrise Valley Drive, Suite 300
Herndon, VA 20171-6126
+1 703.648.8000
+1 866.345.0983
www.idirect.net
Advancing a Connected World