UGiMonitor User Guide IDX 33rev C042415

iMonitor User Guide A Component of iVantage NMS
iMonitor User Guide
iDX Release 3.3

A Component of iVantage NMS
April 27, 2015
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
Document Name: UG_iMonitor User Guide iDX 3.3_Rev C_04_24_15

Document Part Number: T0000597
ii
iMonitor User Guide

A Component of iVantage NMS
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
First release of document for iDX 3.3
02/11/2015
Update for iDX 3.3.1
04/27/2015
A warning, Nominal Carrier Equivocation Occurring, has been added

to Chapter 2 and to Appendix B.
iMonitor User Guide

iDX Release 3.3
iii
Revision History
iv
iMonitor User Guide

iDX Release 3.3
Contents
About . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Document Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Getting Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Document Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
The iVantage Network Management System . . . . . . . . . . . . . . . . . . . . . . . . . 21

Chapter 1
Overview of the NMS for iMonitor . . . . . . . . . . . . . . . . . . . . . . . 1
1.1
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.2
Components of the Network Management System . . . . . . . . . . . . . . . . . . . . . . 2
1.3
1.4
1.5
1.2.1
NMS Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.2.2
Server Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Installing iBuilder, iMonitor, and iSite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

1.3.1
System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.3.2
Installation Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Launching iMonitor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.4.1
Logging On to Additional Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.4.2
Multiple Users or PCs Accessing the NMS . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.4.3
Accepting Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Overview of iMonitor Usage and Displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

1.5.1
Time Frames in iMonitor Requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
iMonitor User Guide

iDX Release 3.3
Contents
1.6
1.5.2
Saving Historical Time Ranges across Multiple Displays . . . . . . . . . . . . . . . . 8
1.5.3
Saving iMonitor Results to a File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.5.4
Types of iMonitor Displays. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.5.5
Multicolumn Details Displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.5.6
Multiple vs. Grouped Display Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Using the iMonitor Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

1.6.1
Clicking on Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1.6.2
Globe Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.6.3
iMonitor Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
1.6.4
Using the iMonitor Toolbars and Menu Options . . . . . . . . . . . . . . . . . . . . 15
1.6.5
Selecting Columns for Viewing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Chapter 2
Monitoring Conditions and Events . . . . . . . . . . . . . . . . . . . . . . 29
2.1
2.2
Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
2.1.1
Representing the State of an Element with Icons. . . . . . . . . . . . . . . . . . . 29
2.1.2
Conditions Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
2.1.3
Elements with Multiple Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
2.1.4
Offline State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
2.1.5
Alarms and Warnings on Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
2.1.6
NMS Database Replication Warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Placing an Element Under Observation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

2.2.1
Viewing Conditions or Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
2.2.2
Interpreting Conditions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
2.3
Examples of System Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
2.4
Snapshots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
2.4.1
Network, Teleport and Device Condition Snapshot. . . . . . . . . . . . . . . . . . 47
2.4.2
Network and Line Card Data Snapshot . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Chapter 3
. . . . . . . . . . . . . . . . . . . . 55
3.1
Monitoring Protocol Processor Blades. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
3.2
Using the Remote Probe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

3.2.1
3.3
vi
Monitoring Performance and Status
Modifying the Timeout Duration for a CW or PN Carrier . . . . . . . . . . . . . . 62
CPU Usage on Protocol Processor Blades. . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
iMonitor User Guide

iDX Release 3.3
Contents
3.4
Adaptive TDMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
3.4.1
Timeplan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
3.4.2
Inroute Group Composition Usage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
3.4.3
C/N0 Distribution. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
3.4.4
Upstream C/N0 and Thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
3.5
Inroute Distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
3.5.1
Viewing Inroute Distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
3.5.2
ACQ Bounce from the Inroute Distribution Pane . . . . . . . . . . . . . . . . . . . 79
3.6
Latency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
3.7
Satellite Link Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

3.7.1
Line Card Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
3.7.2
Upstream Performance Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
3.7.3
SATCOM Graph, Remote Status and UCP Information . . . . . . . . . . . . . . . . 96
3.7.4
UCP Graph . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
3.8
Group QoS Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

3.8.1
Group QoS Distribution Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
3.8.2
Group QoS Plot Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
3.8.3
Group QoS List Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
3.9
Control Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
3.10
Monitoring DVB-S2 Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
3.10.1 Monitoring the ACM Gain of DVB-S2 Carrier . . . . . . . . . . . . . . . . . . . . . 127

3.10.2 Monitoring the MODCOD Distribution of a DVB-S2 Carrier . . . . . . . . . . . . 131
3.10.3 Monitoring the MODCOD Utilization of DVB-S2 Remotes . . . . . . . . . . . . . 134
3.10.4 Monitoring the Signal-to-Noise Ratio of DVB-S2 Remotes . . . . . . . . . . . . . 140
3.10.5 Viewing DVB-S2 Hub Line Card Debug Statistics . . . . . . . . . . . . . . . . . . . 142
3.11
Connecting to Network Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
3.11.1 Examining IP Routing and HDLC Information on Remotes. . . . . . . . . . . . . 146
Chapter 4
4.1
Traffic Statistics and Traffic Graphs . . . . . . . . . . . . . . . . . . .
149
Traffic Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

4.1.1
IP Traffic Statistics vs. Satellite Traffic Statistics . . . . . . . . . . . . . . . . . 149
4.1.2
Traffic Statistics Collection Points . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
iMonitor User Guide

iDX Release 3.3
vii
Contents
4.2
4.3
Traffic Graphs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

4.2.1
SAT Traffic Graph . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
4.2.2
IP Traffic Graph . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
Satellite Bandwidth Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Chapter 5
5.1
5.2
Reporting on Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Long Term Bandwidth Usage Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

5.1.1
Generating Long Term Bandwidth Usage Reports. . . . . . . . . . . . . . . . . . 163
5.1.2
Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
5.1.3
Interpreting Long Term Bandwidth Usage Reports . . . . . . . . . . . . . . . . . 167
Remote and Line Card Availability Reports . . . . . . . . . . . . . . . . . . . . . . . . . 168
Appendix A Accessing the NMS Statistics Archive

A.1
A.2
A.3
A.4
viii
163
. . . . . . . . . . . . . . . . . . 171
Optimization of the Statistics Archive . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

A.1.1
Optimized NMS Statistics Archive Storage . . . . . . . . . . . . . . . . . . . . . . 171
A.1.2
Optimized NMS Statistics Archive Lookup . . . . . . . . . . . . . . . . . . . . . . . 172
A.1.3
Archive Consolidation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
NMS Database Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

A.2.1
Connecting to the NMS Archive Database with ODBC . . . . . . . . . . . . . . . 172
A.2.2
Obtaining the ODBC Connection Library . . . . . . . . . . . . . . . . . . . . . . . . 172
A.2.3
Setting up a Simple ODBC Access Account . . . . . . . . . . . . . . . . . . . . . . 172
Basic Archive Database Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

A.3.1
Types of NMS Databases and Supported Access . . . . . . . . . . . . . . . . . . . 173
A.3.2
Database Structure Changes between Releases . . . . . . . . . . . . . . . . . . . 174
A.3.3
Accessing Remote and Network Names from Configuration Database. . . . . 174
A.3.4
Timestamps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
A.3.5
Overview of the Archive Database Tables. . . . . . . . . . . . . . . . . . . . . . . 174
Database Table Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177

A.4.1
Consolidated Statistics Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
A.4.2
IP Statistics Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
A.4.3
Latency Measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
A.4.4
Hub Line Card Statistics and Upstream Channel Statistics . . . . . . . . . . . . 179
A.4.5
Remote Return Channel Statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
iMonitor User Guide

iDX Release 3.3
Contents
A.4.6
Remote Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
A.4.7
Uplink Control Adjustments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
A.4.8
Event Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
A.4.9
Hub and Remote State Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
A.4.10 Protocol Processor State Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

A.4.11 Hub Chassis State Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
A.4.12 Over-the-Air Statistics Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
A.4.13 Over-the-Air Multicast Statistics Tables . . . . . . . . . . . . . . . . . . . . . . . . 190
A.4.14 Mesh Statistics Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
A.4.15 DVB-S2 Statistics Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
A.4.16 Group QoS Statistics Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
A.4.17 Revision Activity and Revision State Tables . . . . . . . . . . . . . . . . . . . . . 196
A.4.18 Inroute Group Composition Statistics . . . . . . . . . . . . . . . . . . . . . . . . . 198
A.4.19 Inroute Slot Usage Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
A.4.20 Remote Power Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
A.5
NMS Statistics Archive Database Structure . . . . . . . . . . . . . . . . . . . . . . . . . 200

A.5.1
Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
A.5.2
Archive Database Table Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
A.5.3
The Archive Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
A.5.4
Table Division Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
A.5.5
Table Selection Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
A.5.6
Converting Data between Table Formats . . . . . . . . . . . . . . . . . . . . . . . 206
A.5.7
Optimizing Archive Database Performance . . . . . . . . . . . . . . . . . . . . . . 207
A.5.8
Selecting from the Restructured Database . . . . . . . . . . . . . . . . . . . . . . 212
Appendix B
Alarms and Warnings
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
B.1
Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
B.2
Warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
Appendix C SNMP Proxy Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
221
C.1
How the Proxy Agent Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
C.2
The iDirect Management Information Base (MIB) . . . . . . . . . . . . . . . . . . . . . 222

C.2.1
Resetting Statistical Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
iMonitor User Guide

iDX Release 3.3
ix
Contents
C.3
C.2.2
iDirect MIB SNMP Traps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
C.2.3
Setting up SNMP Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
Working with HP OpenView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236

C.3.1
Linux SNMP Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
iMonitor User Guide

iDX Release 3.3
List of Figures
Figure 1.
Windows 7 Start Menu Entries for NMS GUI Clients . . . . . . . . . . . . . . . . . . . . . . . 4
Figure 2.
iMonitor Login Information Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Figure 3.
Using the File Menu to Log On To iMonitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Figure 4.
Clearing Automatically Accept Configuration Changes . . . . . . . . . . . . . . . . . . . . 7
Figure 5.
Accept Changes Button Indicating Configuration Change . . . . . . . . . . . . . . . . . . . 7
Figure 6.
Using the Pushpin to Set the Time Range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Figure 7.
Saving iMonitor Results to a File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Figure 8.
iMonitor Main Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Figure 9.
Expand Tree Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Figure 10.
Expanded Tree with Child Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Figure 11.
Collapse Tree Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Figure 12.
Collapsed Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Figure 13.
Sort Preferences Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Figure 14.
Sample Context Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Figure 15.
Fully-Expanded Network in iMonitor Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Figure 16.
iMonitor Title Bar. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Figure 17.
iMonitor Menu Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Figure 18.
iMonitor Main Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Figure 19.
Enabling Audio Notification from the Results Menu. . . . . . . . . . . . . . . . . . . . . . 17
Figure 20.
Disabling Audio Notification from the Results Menu . . . . . . . . . . . . . . . . . . . . . 17
Figure 21.
Audio Notification Properties Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Figure 22.
Condition Log Tab with Acknowledged Conditions . . . . . . . . . . . . . . . . . . . . . . 18
Figure 23.
iMonitor View Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Figure 24.
Selecting Search Criteria on Find Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Figure 25.
Find Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Figure 26.
The Workspace Toolbar in Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Figure 27.
iMonitor Operational Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Figure 28.
iMonitor Status Bar. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Figure 29.
Conditions Pane. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Figure 30.
Legend Pane (Partial View) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Figure 31.
iMonitor Tree with Real-Time Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Figure 32.
Real-Time Status of Remote with Idle and Dormant States Enabled . . . . . . . . . . . 25
Figure 33.
Selecting Columns for Viewing from Context Menu . . . . . . . . . . . . . . . . . . . . . . 26
Figure 34.
Select Columns Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Figure 35.
Select Columns Dialog Box with Show Default Button . . . . . . . . . . . . . . . . . . . . 27
Figure 36.
iMonitor Conditions Pane. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Figure 37.
Disabling a Condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Figure 38.
Clearing the Condition Log Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
iMonitor User Guide

iDX Release 3.3
List of Figures
ii
Figure 39.
Selecting the Toggle Conditions Icon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Figure 40.
Observing Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Figure 41.
Cancelling Observation of an Element . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Figure 42.
Remote Control Panel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Figure 43.
Select Items Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Figure 44.
Conditions Select Time Range Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Figure 45.
Events Time Range Dialog Box with Text Filter . . . . . . . . . . . . . . . . . . . . . . . . 42
Figure 46.
Get Past Drop-Down List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Figure 47.
Conditions Results in Multicolumn Format . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Figure 48.
Conditions Time Line Results in Graphical Format . . . . . . . . . . . . . . . . . . . . . . 43
Figure 49.
Selecting Time Scale in the Conditions Time Line . . . . . . . . . . . . . . . . . . . . . . 44
Figure 50.
Conditions Time Line Tab with Detail Selected . . . . . . . . . . . . . . . . . . . . . . . . 44
Figure 51.
Event Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Figure 52.
Conditions Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Figure 53.
List and Details View of Condition Snapshot . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Figure 54.
Remote Submenu in Condition Snapshot. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Figure 55.
Teleport Condition Snapshot: Detail View. . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Figure 56.
Condition Snapshot: Hovering Mouse in Details View. . . . . . . . . . . . . . . . . . . . . 50
Figure 57.
Network Conditions: Selecting Multiple Remotes in Details View. . . . . . . . . . . . . 51
Figure 58.
Select Remotes Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Figure 59.
Example of Remote Availability Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Figure 60.
Select Items and Stats Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Figure 61.
Network Data Snapshot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Figure 62.
Data Snapshot Right-Click Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Figure 63.
iMonitor Blade Info Pane: Initial View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Figure 64.
iMonitor Blade Info Tabs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Figure 65.
Probe Remote Power for TDMA Remote in Network . . . . . . . . . . . . . . . . . . . . . 57
Figure 66.
Probe Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Figure 67.
Changing the Remote Transmit Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Figure 68.
Probe Dialog Box: Terminal Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Figure 69.
Probe Dialog Box: Reset Remote . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Figure 70.
Probe Dialog Box: Cross Polarization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Figure 71.
Probe Dialog Box: Selecting a Protocol Layer . . . . . . . . . . . . . . . . . . . . . . . . . 61
Figure 72.
Probe Dialog Box: Protocol Layer Operations. . . . . . . . . . . . . . . . . . . . . . . . . . 62
Figure 73.
Setting the Timeout for a CW or PN Carrier in iBuilder . . . . . . . . . . . . . . . . . . . 63
Figure 74.
Select Items Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Figure 75.
Blade CPU Usage: Chart View Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Figure 76.
Blade CPU Usage: List View Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Figure 77.
Select Inroute Groups in Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Figure 78.
Timeplan Graphs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Figure 79.
Timeplan Statistics in Multicolumn List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
iMonitor User Guide

iDX Release 3.3
List of Figures
Figure 80.
IGC Usage Histogram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Figure 81.
IGC Usage Histogram: Changing the Graph Type . . . . . . . . . . . . . . . . . . . . . . . 70
Figure 82.
IGC Usage: Timeline Graph . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Figure 83.
IGC Usage: Multicolumn List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Figure 84.
C/N0 Distribution: Timeline Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Figure 85.
C/N0 Distribution: Multicolumn List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Figure 86.
Select Remotes Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Figure 87.
Figure 88.
Upstream C/N0 and Thresholds: Timeline Tab . . . . . . . . . . . . . . . . . . . . . . . . . 76

Upstream C/N0 and Thresholds: Multicolumn List. . . . . . . . . . . . . . . . . . . . . . . 77
Figure 89.
Select Inroute Groups Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Figure 90.
Inroute Distribution Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Figure 91.
Performing ACQ Bounce . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Figure 92.
Select Items Dialog Box for Latency Measurements. . . . . . . . . . . . . . . . . . . . . . 80
Figure 93.
Select Time Range Dialog Box and Clock Display . . . . . . . . . . . . . . . . . . . . . . . 81
Figure 94.
iMonitor Latency Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Figure 95.
Select Line Cards Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Figure 96.
iMonitor Hub Line Card Statistics Pane: Initial View . . . . . . . . . . . . . . . . . . . . . 84
Figure 97.
Hub Line Card Statistics: Graphical Display and Multicolumn List . . . . . . . . . . . . 85
Figure 98.
HLC Graph Right-Click Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Figure 99.
Hub Line Card Graph: Changing the Scale . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Figure 100.
Hub Line Card Statistics for an SCPC Return Channel and for an XLC-M Line Card. . 88
Figure 101.
Select Remotes Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Figure 102.
iMonitor Upstream Performance Statistics Pane: TDMA and SCPC Channels . . . . . . 91
Figure 103.
Upstream Performance Statistics: Multicolumn List . . . . . . . . . . . . . . . . . . . . . 92
Figure 104.
Upstream Performance Statistics: TDMA and SCPC Buttons . . . . . . . . . . . . . . . . 93
Figure 105.
Remote Upstream Performance Statistics: Graph and Multicolumn List . . . . . . . . 93
Figure 106.
Upstream Performance Graph Right-Click Menu . . . . . . . . . . . . . . . . . . . . . . . . 94
Figure 107.
Remote Upstream Performance Statistics for TDMA and SCPC Return Channels . . . 94
Figure 108.
Remote Performance Statistics CRC Errors: Graph and Multicolumn List. . . . . . . . 96
Figure 109.
Select Items Dialog Box with Remote Pre-Selected. . . . . . . . . . . . . . . . . . . . . . 97
Figure 110.
iMonitor SATCOM Graphs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Figure 111.
Remote Status Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Figure 112.
UCP Info Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Figure 113.
Select Remotes Dialog Box: Selecting Past Data. . . . . . . . . . . . . . . . . . . . . . . 101
Figure 114.
UCP Graphs for Grouped Remotes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Figure 115.
UCP Graph Right-Click Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Figure 116.
UCP Raw Data for Highlighted Remote . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Figure 117.
Selecting QoS Stats from iMonitor Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Figure 118.
Selecting Elements for Group QoS Statistics . . . . . . . . . . . . . . . . . . . . . . . . . 106
Figure 119.
Selecting a Single Node for Group QoS Statistics . . . . . . . . . . . . . . . . . . . . . . 106
Figure 120.
Group QoS Stats: Initial View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
iMonitor User Guide

iDX Release 3.3
iii
List of Figures
iv
Figure 121.
Group QoS Distribution: Group QoS View vs. Remote View. . . . . . . . . . . . . . . . 108
Figure 122.
Group QoS Distribution: Viewing QoS Statistics for a Node . . . . . . . . . . . . . . . . 109
Figure 123.
Group QoS Distribution: Single Group QoS Node Divided Across Main Display . . . . 110
Figure 124.
Group QoS Distribution: Base Measures in Right-Click Menu . . . . . . . . . . . . . . . 110
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.
Group QoS Distribution: Display Controls and Filter Settings . . . . . . . . . . . . . . 112
Figure 128.
Group QoS Distribution: Top Ten Remotes (Allocated) . . . . . . . . . . . . . . . . . . 113
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.
Group QoS Distribution: Replaying Historical Statistics . . . . . . . . . . . . . . . . . . 115
Figure 132.
Group QoS Distribution: Averaging Over the Historical Time Range . . . . . . . . . . 115
Figure 133.
Group QoS Distribution: Zoom Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Figure 134.
Group QoS Distribution: Resizing the Zoom Box . . . . . . . . . . . . . . . . . . . . . . . 117
Figure 135.
Group QoS Distribution: Moving the Zoom Box Horizontally . . . . . . . . . . . . . . . 117
Figure 136.
Group QoS Distribution: Clearing the Horizontal Zoom . . . . . . . . . . . . . . . . . . 118
Figure 137.
Group QoS Distribution: Viewing Statistics after Zooming . . . . . . . . . . . . . . . . 118
Figure 138.
Group QoS Stats: Plot Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Figure 139.
Group QoS Stats for Selected Bandwidth Group . . . . . . . . . . . . . . . . . . . . . . . 120
Figure 140.
Group QoS Stats: Selecting Graphs to View . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Figure 141.
Group QoS Stats: Changing the Scale . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Figure 142.
Group QoS Stats: List Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Figure 143.
Selecting Service Levels to View Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Figure 144.
QoS Service Level Statistics Graph . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Figure 145.
Saving QoS Statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Figure 146.
Control Panel Tab: Example 1Figure 111 on page 99 . . . . . . . . . . . . . . . . . . . . 126
Figure 147.
Control Panel Tab: Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Figure 148.
Selecting Remotes for ACM Gain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Figure 149.
Select Time Range Graphical Slot Display . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Figure 150.
ACM Gain: ACM Gain Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Figure 151.
Selecting Remotes in the Left Pane of the ACM Gain Display . . . . . . . . . . . . . . 129
Figure 152.
Changing the Remotes in the ACM Gain Display . . . . . . . . . . . . . . . . . . . . . . . 130
Figure 153.
Changing the ACM Gain Display. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Figure 154.
ACM Gain: List Data Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Figure 155.
Selecting Remotes for MODCOD Distribution . . . . . . . . . . . . . . . . . . . . . . . . . 132
Figure 156.
MODCOD Distribution Display: MODCOD Tab . . . . . . . . . . . . . . . . . . . . . . . . . 132
Figure 157.
MODCOD Distribution Display: Timeline Tab . . . . . . . . . . . . . . . . . . . . . . . . . 133
Figure 158.
MODCOD Distribution Display: List Data Tab . . . . . . . . . . . . . . . . . . . . . . . . . 134
Figure 159.
Selecting Remotes for MODCOD Utilization . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Figure 160.
MODCOD Utilization Display: Message Structure Tab . . . . . . . . . . . . . . . . . . . . 135
Figure 161.
MODCOD Utilization Display: MODCOD Tab . . . . . . . . . . . . . . . . . . . . . . . . . . 136
iMonitor User Guide

iDX Release 3.3
List of Figures
Figure 162.
MODCOD Utilization Display: Changing the Graph Type . . . . . . . . . . . . . . . . . . 137
Figure 163.
MODCOD Utilization Display: Detailed Data Tab . . . . . . . . . . . . . . . . . . . . . . . 137
Figure 164.
MODCOD Utilization Display: Context Menu. . . . . . . . . . . . . . . . . . . . . . . . . . 139
Figure 165.
Enabling Mouse Tracking for MODCOD Utilization . . . . . . . . . . . . . . . . . . . . . . 139
Figure 166.
MODCOD Utilization: Setting MODCOD Boundaries . . . . . . . . . . . . . . . . . . . . . 139
Figure 167.
MODCOD Utilization: Setting Size of Sparkline Column and Rows. . . . . . . . . . . . 140
Figure 168.
MODCOD Utilization: Setting the Maximum Spark Lines for a Remote. . . . . . . . . 140
Figure 169.
Selecting Remotes SNR Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Figure 170.
ACM SNR Monitoring: SNR Plot Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Figure 171.
ACM SNR Monitoring: List Data Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
Figure 172.
DVB-S2 Hub Debug View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Figure 173.
Viewing Details of DVB-S2 Hub Debug Statistics . . . . . . . . . . . . . . . . . . . . . . . 144
Figure 174.
Hub Debug Statistics: Selecting Structure for Second Tab . . . . . . . . . . . . . . . . 145
Figure 175.
Hub Debug Statistics: ACM Packets Rx Low Example . . . . . . . . . . . . . . . . . . . . 145
Figure 176.
Hub Debug Statistics: Resetting the Counters . . . . . . . . . . . . . . . . . . . . . . . . 146
Figure 177.
Viewing IP Routing and HDLC Information from the Remote Command Line . . . . 147
Figure 178.
Collection Points for IP Usage Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Figure 179.
Collection Points for Satellite and IP Statistics . . . . . . . . . . . . . . . . . . . . . . . 151
Figure 180.
Select Items Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Figure 181.
SAT Traffic: SAT Traffic Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Figure 182.
SAT Traffic: SAT Downstream Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
Figure 183.
SAT Traffic Options Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Figure 184.
Statistics Graphs Show Parameters Section . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Figure 185.
Select Remotes Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
Figure 186.
IP Traffic Graphs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Figure 187.
IP Traffic: Downstream and Upstream Data . . . . . . . . . . . . . . . . . . . . . . . . . 157
Figure 188.
IP Traffic Graph: Context Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
Figure 189.
Selecting Remotes for Grouped Remotes IP Traffic Graph . . . . . . . . . . . . . . . . 159
Figure 190.
Selecting Remotes for the Main Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
Figure 191.
IP Traffic Graph: Sorting Remotes by Traffic Volume . . . . . . . . . . . . . . . . . . . 160
Figure 192.
IP Statistics Options Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Figure 193.
Figure 194.
Real-time SAT Bandwidth Usage Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Figure 195.
Selecting Long Term Bandwidth Usage Parameters. . . . . . . . . . . . . . . . . . . . . 164
Figure 196.
SAT Long Term Bandwidth Usage Report: Totals Tab . . . . . . . . . . . . . . . . . . . 166
Figure 197.
IP Long Term Bandwidth Usage Report: Totals Tab. . . . . . . . . . . . . . . . . . . . . 167
Figure 198.
SAT Long Term Bandwidth Usage Report: Average Tab . . . . . . . . . . . . . . . . . . 167
Figure 199.
Figure 200.
Remote Availability Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
Figure 201.
Default Table Set. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
Figure 202.
Release 6.0 and Earlier Statistics Archiving Process . . . . . . . . . . . . . . . . . . . . 201
iMonitor User Guide

iDX Release 3.3
List of Figures
vi
Figure 203.
New Statistics Archiving Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
Figure 204.
Algorithm for Calculating Database Table Name . . . . . . . . . . . . . . . . . . . . . . 205
Figure 205.
Archive Database after Conversion to 6.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
Figure 206.
Allowing Blocked Content for Database Partitioning Calculator. . . . . . . . . . . . . 209
Figure 207.
Archive Database Partitioning Calculator . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
Figure 208.
Segmented nms_remote_status archive tables . . . . . . . . . . . . . . . . . . . . . . . 212
Figure 209.
SNMP Proxy Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
iMonitor User Guide

iDX Release 3.3
List of Figures
iMonitor User Guide

iDX Release 3.3
vii
List of Tables
Table 1.
Main Toolbar Icons and Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Table 2.
Operational Toolbar Icons and Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Table 3.
Elements and Types of Information Provided . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Table 4.
Real-Time States and Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Table 5.
Explanation of Alarms by Element . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Table 6.
Explanation of Warnings by Element . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Table 7.
Warnings Raised by NMS Database Replication Scripts on MySQL Master . . . . . . . . . 36
Table 8.
Warnings Raised by NMS Database Replication Scripts on MySQL Slave . . . . . . . . . . 37
Table 9.
DVB-S2 Performance Monitoring: Availability for Network Elements . . . . . . . . . . 127
Table 10.
DVB-S2 MODCOD Index Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
Table 11.
Archive Database Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
Table 12.
IP Statistics Record Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Table 13.
lat_stats Record Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
Table 14.
nms_hub_stats Table Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
Table 15.
nms_inroutes Table Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
Table 16.
raw_tdma_rmtrx_stats Record Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
Table 17.
raw_scpc_rmtrx_stats Record Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
Table 18.
nms_remote_status Record Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Table 19.
nms_ucp_info Record Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
Table 20.
event_msg Record Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
Table 21.
state_change_log Record Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
Table 22.
pp_state_change_log Record Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
Table 23.
chassis_state_change_log Record Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
Table 24.
OTA Stats Record Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
Table 25.
OTA Multicast Statistics Record Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
Table 26.
Mesh Statistics Record Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
Table 27.
remote_dvbs2_stats Record Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
Table 28.
hub_dvbs2_stats Record Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
Table 29.
pp_dvbs2_stats Record Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
Table 30.
nms_group_qos_stats Record Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
Table 31.
nms_sl_qos_stats Record Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
Table 32.
rev_activity Record Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
Table 33.
rev_state Record Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
Table 34.
inroute_composit_stats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
Table 35.
inroute_slot_usage_stats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
Table 36.
remote_power_stats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
Table 37.
Default Data Striping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
Table 38.
TABLE_INFO Format and Default Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
iMonitor User Guide

iDX Release 3.3
viii
List of Tables
Table 39.
Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
Table 40.
Warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
Table 41.
iDirect MIB Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
Table 42.
iDirect MIB Statistical Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
Table 43.
iDirect MIB Traps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
Table 44.
SNMP Command Line Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
iMonitor User Guide

iDX Release 3.3
ix
List of Tables
iMonitor User Guide

iDX Release 3.3
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:
The iVantage Network Management System
Overview of the NMS for iMonitor
Monitoring Conditions and Events
Monitoring Performance and Status
Traffic Statistics and Traffic Graphs
Reporting on Networks
Accessing the NMS Statistics Archive
Alarms and Warnings
SNMP Proxy Agent
iMonitor User Guide

iDX Release 3.3
xi
Document Conventions
Document Conventions
This section illustrates and describes the conventions used throughout this document.
Convention Description
Example
Used when the user is required to

type a command at a command
line prompt or in a console.
Type the command:
Terminal
Output
Used when showing resulting

output from a command that was
entered at a command line or on a
console.
crc report all
Screen
Reference
Used when referring to text that

appears on the screen on a
Graphical User Interface (GUI).
1. To add a remote to an inroute group, right-click

the Inroute Group and select Add Remote.
Command
Used when specifying names of

commands, menus, folders, tabs,
dialogs, list boxes, and options.
Hyperlink
Used to show all hyperlinked text

within a document or external
links such as web page URLs.
cd /etc/snmp/
8350.3235 : DATA CRC [

1]
8350.3502 : DATA CRC [5818]
8350.4382 : DATA CRC [ 20]
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.
WARNING: A warning highlights an essential operating or maintenance procedure,

practice, condition, or statement which, if not strictly observed, could result in
injury, death, or long term health hazards.
CAUTION: A caution highlights an essential operating or maintenance procedure,
practice, condition, or statement which, if not strictly observed, could result in
damage to, or destruction of, equipment or a condition that adversely affects
system operation.
NOTE: A note is a statement or other notification that adds, emphasizes, or
clarifies essential information of special importance or interest.
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
Telephone: (703) 648-8151
E-mail: tac@idirect.net
iMonitor User Guide

iDX Release 3.3
Document Set
For sales or product purchasing information contact iDirect Corporate Sales at the following
telephone number or e-mail address:
Telephone: (703) 648-8000
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.
iDX Release Notes
iDX Software Installation Guide or Network Upgrade Procedure Guide
iDX iBuilder User Guide
iDX Technical Reference Guide
iDX Installation and Commissioning Guide for Remote Satellite Routers
iDX Features and Chassis Licensing Guide
iDX Software Installation Checklist/Software Upgrade Survey
iDX Link Budget Analysis Guide
iMonitor User Guide

iDX Release 3.3
xiii
Document Set
xiv
iMonitor User Guide

iDX Release 3.3
The iVantage Network

Management System
iMonitor is a component of the iDirect iVantage Network Management System (NMS). The
iVantage NMS is a complete suite of tools for configuring, monitoring, and controlling iDirect
satellite networks.
NOTE: Beginning with iDX Release 3.1, the Geographic Map is no longer
supported. For questions, please contact the iDirect TAC.
The iVantage NMS consists of the following components:
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.
iMonitor provides network operators with detailed information on real-time and

historical performance of the network. Among its many capabilities, iMonitor allows you
to analyze bandwidth usage; view remote status; view network statistics; monitor
performance of networks, sub-networks and individual network elements; and manage
alarms, warnings and network events. Alarms, warnings and statistics can be forwarded as
SNMP traps. All events and performance statistics are automatically archived. Data
displayed on the iMonitor GUI can be exported directly into Excel for further analysis. A
Network Probe allows detailed investigation of network issues. The iMonitor User Guide
provides instructions for using iMonitor.
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.
iMonitor User Guide

iDX Release 3.3
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.
iMonitor User Guide

iDX Release 3.3
1 Overview of the NMS for

iMonitor
The iDirect Network Management System (the iVantage NMS) is a suite of applications and
servers that provide configuration, control and monitoring of all components of iDirect
networks. The NMS client/server system consists of three series of components:
NMS applications with Graphical User Interfaces (GUIs) for configuring and monitoring
iDirect networks
Databases that store configuration and statistical data
Middleware that manages access to the databases on behalf of users
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.
Operational characteristics are captured in a variety of network statistical data, such as

IP traffic statistics, satellite link quality, and hardware component operating values.
Various graphical displays can be viewed based on these operational characteristics.
Status and statistical data are stored in the historical archive to provide analysis of anomalous
conditions and performance trends.
iMonitor User Guide

iDX Release 3.3
Components of the Network Management System
1.2

The NMS consists of several client/server components that work together to provide the
functions and views necessary to control an iDirect network. These components are briefly
discussed below.
1.2.1 NMS Clients

The iDirect NMS provides three GUI clients, each of which performs specific functions for
networks operators, field installers, and end users.
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.
iBuilder User Guide

iDX Release 3.3
1.2.2 Server Components

The NMS server processes run on NMS Server machines. There are a number of NMS server
processes, each of which performs a specific set of functions.
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.
Real-time Data Server

The real-time data server collects the network statistics produced by the network elements.
These statistics include IP stats for each remote, remote status messages, timeplan slot
assignments, line card statistics, etc. Additionally, the real-time data server provides these
statistics to the GUI clients for real-time and historical display.
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.
NMS Controller Server

The control server manages the PP Controller Server processes running on the NMS server.
Protocol Processor Controller Servers

The Protocol Processor Controller processes control the iDirect processes on each protocol
processor blade.
Chassis Manager Server

The chassis manger server controls access to all hub chassis. The CM server only allows access
to chassis slots that have been licensed by iDirect.
NMS Monitor Script

The NMS monitor script monitors the NMS processes and restarts them automatically if they
terminate abnormally. It records a log file of its activities and can be configured to e-mail
designated recipients when it restarts any of the other servers.
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.
iBuilder User Guide

iDX Release 3.3
Installing iBuilder, iMonitor, and iSite
Database Backup Script

The database backup script runs nightly to back up the data in the primary NMS databases and
copy it to the backup NMS server. The database backup script must be custom-configured for
each customer site.
Database Restore Script

The database restore script runs nightly on the backup NMS server. It restores the primary NMS
database into the backup database for NMS failover purposes.
1.3
Installing iBuilder, iMonitor, and iSite

This section provides the system requirements and procedures for installing the Network
Management System clients.
1.3.1 System Requirements

The NMS GUI clients are Windows PC-based applications that only run under the following
versions of Windows:
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.
1.3.2 Installation Procedure

A single client installer .exe file, nms_clients_setup.exe, installs all three GUI clients. To
install the clients, copy the nms_clients_setup.exe file to the target PC, double-click it, and
follow the prompts.
By default, the clients are installed in the directory C:\Program Files(x86)\iDIRECT. The
installer automatically adds the appropriate entries in the Windows Start menu. To run an
iDirect NMS GUI client, click Start All ProgramsiDirectNMS Clients <RelNo>, where
<RelNo> is the release number. The iBuilder, iMonitor, and iSite clients are displayed, along
with an Uninstall selection.
Figure 1. Windows 7 Start Menu Entries for NMS GUI Clients
iBuilder User Guide

iDX Release 3.3
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.
Figure 2. iMonitor Login Information Dialog Box

3. Click the Server drop-down menu and select the IP address of the primary NMS Server
machine. If the IP address is not in the list, enter it in the Server box.
4. Click OK to log on to the NMS server.
NOTE: To log on, the iMonitor and NMS server versions must match. (For example,
version 3.0.0 of iMonitor can connect only to version 3.0.0 of the NMS server.)
iBuilder User Guide

iDX Release 3.3
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.4.1 Logging On to Additional Servers

To log out of one NMS server and log on to another, select FileLog On to open the Login
Information dialog box. Then enter the User Name, Password and Server IP Address of the
second server.
Figure 3. Using the File Menu to Log On To iMonitor
1.4.2 Multiple Users or PCs Accessing the NMS

Multiple users or multiple sessions can run simultaneously on the NMS. The NMS offers the
following capabilities:
1. Multiple simultaneous sessions of iMonitor and/or iBuilder can run on a single PC. These
versions can be connected to different servers or the same server.
2. Multiple PCs can run the same session of iMonitor and/or iBuilder at any given time and
connect to the same server at the same time.
3. Multiple iBuilder users can modify the configuration data base at the same time.
1.4.3 Accepting Changes

Beginning in iDX Release 3.0, when an iBuilder user modifies the network configuration, by
default the changes are automatically accepted in iMonitor login sessions and the iMonitor
display is automatically updated. This differs from earlier releases which required iMonitor
users to accept the changes before they were displayed.
To be notified of changes and accept those changes before they are displayed, configure
iMonitor to turn on the accept changes functionality as follows:
1. Click the Edit menu and select Preferences.
iBuilder User Guide

iDX Release 3.3
Overview of iMonitor Usage and Displays
2. Clear Automatically accept configuration changes (Figure 4).
Figure 4. Clearing Automatically Accept Configuration Changes

When Automatically accept changes is disabled (i.e., when the check box in Figure 4 is
cleared), then the Accept Changes button works as it did in previous releases. When an
iBuilder user changes the configuration, the Accept Changes button on the iMonitor toolbar
changes color from gray to red.
Figure 5. Accept Changes Button Indicating Configuration Change

To view the changes before accepting them, select ViewConfiguration Changes (see
Configuration Changes Pane on page 25). To accept the changes and update the iMonitor
display, click Accept Changes.
1.5

1.5.1 Time Frames in iMonitor Requests
iMonitor provides three basic time periods for requesting data: Real-time, Historical, and Get
Past.
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.
iBuilder User Guide

iDX Release 3.3
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.
1.5.2 Saving Historical Time Ranges across Multiple Displays

iMonitor can save both Historical and Get Past time ranges and re-use them in other requests.
To save a specified time range:
1. Launch the first display and specify a time range.
2. Click the push pin next to the Time Range button (Figure 6).
The push pin will change to the saved position as shown in Figure 6. All future requests
will automatically use the saved time range until it is removed.
Figure 6. Using the Pushpin to Set the Time Range

3. To remove the saved time range, click the push pin again.
1.5.3 Saving iMonitor Results to a File

iMonitor can save historical or real-time results to disk for the following requests:
Latency
Line card statistics
Events
Conditions
Remote Status/UCP
To save the results:

1. Select Save to in the Select Items dialog box.
2. Click the File button to enter a file name and select a folder for the saved data.
Figure 7. Saving iMonitor Results to a File
iBuilder User Guide

iDX Release 3.3
1.5.4 Types of iMonitor Displays

iMonitor displays data in graphs and multicolumn lists. Events are shown only in multicolumn
lists. Statistical data and conditions may be displayed in both formats, depending on the type
of data.
Graphical displays represent data in graphical charts.
Multicolumn lists represent data arranged in rows and columns.
1.5.5 Multicolumn Details Displays

All iMonitor multicolumn lists share the following characteristics:
Data in multicolumn lists can be sorted in ascending or descending order by clicking a

column heading.
By default, data is sorted by date and time.
Vertical scroll bars function as follows:

If the vertical scroll bar is at the bottom of the pane, the pane scrolls to continually
show new data as it is added to the display.
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.
Multicolumn data can be printed by selecting FilePrint.
The following functions can be selected by right-clicking inside a multicolumn list:

Expand All resizes each column to be the width of either the widest data in that
column, or the width of the column heading, whichever is wider.
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.
1.5.6 Multiple vs. Grouped Display Results

When data is requested for sub-elements (such as remotes) from a higher-level element in the
iMonitor Tree (such as an inroute group), iMonitor opens a dialog box to select the elements
for which to display data. How the data is displayed depends on the type of data requested.
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.
iBuilder User Guide

iDX Release 3.3
Using the iMonitor Interface
1.6

The iMonitor main window is composed of several toolbars and panes which are described
below.
Figure 8. iMonitor Main Window
1.6.1 Clicking on Elements

Right-Clicking
Right-click an element to display a menu of operations that can be performed on that
element.
10
iBuilder User Guide

iDX Release 3.3
Single-Clicking vs. Double-Clicking

When navigating the iMonitor Tree:
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.
Double-click a remote in the iMonitor Tree to display the Control Panel.
1.6.2 Globe Functions

Right-click the Globe at the top of the iMonitor Tree to:
Enable or disable docking of iMonitor panes
Hide the iMonitor Tree
Sort the iMonitor Tree
Expand the iMonitor Tree
Collapse the iMonitor Tree
Using the Docking Feature

Docking is the ability to move an iMonitor pane to another position within iMonitor. A pane can
also be detached from iMonitor and placed elsewhere on the screen. Dockable panes have
double-ridge lines at the top of the pane.
To dock or detach an iMonitor pane:

1. Right-click the double-ridge lines of the pane and select Allow Docking.
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.
iBuilder User Guide

iDX Release 3.3
11
Expanding the iMonitor Tree

To expand the iMonitor Tree to view all of the child elements, select EditExpand Tree.
Figure 9. Expand Tree Selection
Figure 10. Expanded Tree with Child Elements
Collapsing the iMonitor Tree

To collapse the iMonitor Tree to view only the top level elements, select EditCollapse Tree.
Figure 11. Collapse Tree Selection
Figure 12. Collapsed Tree
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
iBuilder User Guide

iDX Release 3.3
Sorting the Tree

To sort the Tree:
1. Right-click in the Tree pane or right-click the double-ridge lines above the Tree pane and
select Sort Tree. Alternatively, select EditSort Tree.
2. In the Sort Preferences dialog box, click the Sort items in drop-down list and select
either Ascending or Descending.
Figure 13. Sort Preferences Dialog Box

3. Click the Sort items by drop-down list and select an option.
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.
iBuilder User Guide

iDX Release 3.3
13
6. Click OK.
NOTE: iMonitor remembers the selected sort preference after logging out and
logging on again.
1.6.3 iMonitor Tree

Right-click an element in the tree to display a menu of options for that element. Click a menu
option to view data, graphs and other information used to monitor and troubleshoot the
network. A sample context menu is shown in Figure 14.
Figure 14. Sample Context Menu

A plus sign (+) next to an element in the Tree indicates that additional elements exist at the
next level, or branch, of the Tree. Click the plus sign (+) to expand the element to view the
next level of the Tree.
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
iBuilder User Guide

iDX Release 3.3
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.
Figure 15. Fully-Expanded Network in iMonitor Tree
1.6.4 Using the iMonitor Toolbars and Menu Options

Title Bar
The Title bar identifies the name of the application (in this case, iMonitor), the iDirect
software version, and the IP address of the server to which iMonitor is connected.
Figure 16. iMonitor Title Bar
Menu Bar
The Menu bar at the top of the display provides access to a number of operations described in
the sections below.
Figure 17. iMonitor Menu Bar
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.
Figure 18. iMonitor Main Toolbar
iBuilder User Guide

iDX Release 3.3
15
Table 1. Main Toolbar Icons and Functions

Toolbar Icon
Function
View elements in the Tree Menu hierarchy.
View Conditions.
Pause the Timeplan Graph.
Resume the Timeplan Graph.

Turn audio on or off when a new alarm or condition is presented or when a
condition is cleared.
Acknowledge a condition.
Open the Find Toolbar next to the Main Toolbar
Accept changes made to the system by another user and update the iMonitor
display with the latest database information.
View the version number of the NMS and system 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
iBuilder User Guide

iDX Release 3.3
Figure 19. Enabling Audio Notification from the Results Menu

3. Select None to disable audio notifications (Figure 20).
Figure 20. Disabling Audio Notification from the Results Menu

4. To set up how often audio notifications repeat, or to specify that the notification should
play only when a new condition occurs:
a. Select ResultsAudio NotificationProperties from the main menu.
b. Select one of the two choices in the Audio Notification Properties dialog box
(Figure 21).
Figure 21. Audio Notification Properties Dialog Box
iBuilder User Guide

iDX Release 3.3
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:
Audio notification stops until a new condition is raised.
All outstanding conditions are acknowledged. Individual conditions cannot be

acknowledged.
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.
Figure 22. Condition Log Tab with Acknowledged Conditions

NOTE: When an operator acknowledges a condition, only that operators view is
affected. No changes are made on the NMS server or to other operator accounts.
18
iBuilder User Guide

iDX Release 3.3
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.
Figure 23. iMonitor View Menu
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.
iBuilder User Guide

iDX Release 3.3
19
Figure 24. Selecting Search Criteria on Find Toolbar

Alternatively, search by clicking the Find (Binocular) button on the main toolbar.
To search using the Find button:
1. Click the Find button on the main toolbar to open the Find dialog box (Figure 25).
Figure 25. Find Dialog Box

2. Enter a new search string or select from earlier search strings.
3. Select the Device Type, Where to search, and select from the Search Criteria.
4. Click the Find Next button repeatedly to find each successive matching element.
The example below uses the Find toolbar to search for a Remote by the Name of e8350-210
in the Network Tree View.
The matching search result is highlighted in the Tree.
20
iBuilder User Guide

iDX Release 3.3
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.
Figure 26. The Workspace Toolbar in Action
Saving and Reloading Workspaces

A workspace can be saved and reloaded at a later time. The workspace file stores the
following information about displays:
The window pane size and position within the workspace.
The parameters specified in the original requests.

NOTE: Only Real-Time and Get Past requests are saved in workspace files. See
Time Frames in iMonitor Requests on page 7.
The following workspace operations can be performed from the main menu:
Select FileSave Workspace or FileSave Workspace As to save the contents of a

workspace.
Select FileOpen Workspace to reload a previously-saved workspace. The saved

requests are automatically resubmitted to the appropriate servers.
Select FileClose Workspace to close a workspace.
iBuilder User Guide

iDX Release 3.3
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.
Figure 27. iMonitor Operational Toolbar

Table 2. Operational Toolbar Icons and Functions
Toolbar Icon
Function
Request a Network Condition Snapshot
Request a Network Data Snapshot
Request a SAT Traffic Graph
Request an IP Stats Graph
Request a Mesh Traffic Graph. (Not supported in iDX Release 3.3)
Request a Timeplan Slot Assignment Graph
Request Latency results
Request a SATCOM Graph
Request a Remote Status/UCP report
Request modem events
Request conditions
22
iBuilder User Guide

iDX Release 3.3
Table 2. Operational Toolbar Icons and Functions (continued)

Toolbar Icon
Function
Request a SAT Long Term Bandwidth Usage report
Request a Long Term Bandwidth Usage report
Place an element under observation
Open a terminal session
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.
Figure 28. iMonitor Status Bar
Connection Details on Status Bar Icon

Hover the mouse pointer over the PC icon next to the user name on the Status bar to view the
IP address(es) of the NMS server(s) to which iMonitor is currently connected.
iBuilder User Guide

iDX Release 3.3
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.
Figure 29. Conditions 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.
Figure 30. Legend Pane (Partial View)
24
iBuilder User Guide

iDX Release 3.3
Configuration Changes Pane

Select ViewConfiguration Changes to see NMS database changes made by other users.
Viewing Real-Time Status

Select ViewReal-Time Status to see the real time status of network elements. The status of
each network element is displayed to the right of the element name in the iMonitor Tree.
Figure 31. iMonitor Tree with Real-Time Status
Idle and Dormant State Status

The Idle and Dormant States feature minimizes the number of TDMA slots that are allocated
to remotes that have no data to transmit. When this feature is enabled, an inactive remote
changes from the Active State to the Idle State and finally to the Dormant State based on
timeouts configured on the iBuilder Remote QoS tab. (See the iBuilder User Guide for
details.)
The Real-Time Status in the iMonitor Tree shows both the status and the state of each remote
with the Idle and Dormant States feature enabled. This is illustrated in Figure 32 for remote
7350.40077.
Figure 32. Real-Time Status of Remote with Idle and Dormant States Enabled
iBuilder User Guide

iDX Release 3.3
25
1.6.5 Selecting Columns for Viewing

In any iMonitor pane with columns, any operator can select the set of columns that will be
displayed whenever that operator views the pane. Once changed, the modified display will
persist for that operator even after log off.
To select which columns to display:
1. Right-click anywhere in the column headings to display the column selection context
menu.
Figure 33. Selecting Columns for Viewing from Context Menu

2. Select or clear individual columns for display from the menu one at a time or select More
to view the Select Columns dialog box (Figure 34).
Figure 34. Select Columns Dialog Box
26
iBuilder User Guide

iDX Release 3.3
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.
iBuilder User Guide

iDX Release 3.3
27
28
iBuilder User Guide

iDX Release 3.3
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.
2.1.1 Representing the State of an Element with Icons

The icon representing a network element in the iMonitor Tree indicates the current state of
that element. The network element states and the Icons that represent them are described in
Table 4.
iMonitor User Guide

iDX Release 3.3
29
Conditions
Table 4. Real-Time States and Icons

State
30
Icon
Meaning
OK
The element is functioning properly. Shown in

order from left to right are a properly
functioning PP, blade, line card, remote, and
chassis.
OK
This icon is seen in the Conditions Log and

indicates that the element is functioning
properly.
Warning
One or more Warning conditions is active for

the element.
Alarm
One or more Alarm conditions are active for

the element (layer 2/3 alarm, unit not
responding, etc.). Warnings may also be
active in the Alarm state.
Mesh Alarm
One or more Mesh Alarm conditions are active

for the element. (Not supported in iDX
Release 3.3.)
Offline
The remote has been sent offline.
Rx Only
The remote is in receive-only mode
Elsewhere
Indicates that a roaming remote is acquired in

a different network.
Sleep Mode
The remote has entered sleep mode.
Unknown
Condition
Condition state unknown
Disabled
Disabled condition
iMonitor User Guide

iDX Release 3.3
Conditions
2.1.2 Conditions Pane

The current state of network elements is also represented in the Conditions Pane. Select
ViewConditions to open that pane at the bottom of iMonitors main window.
Figure 36. iMonitor Conditions Pane

The Conditions pane has tabs showing conditions using the following criteria:
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.
Figure 37. Disabling a 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.
To clear the contents of the Condition Log tab:

1. With the Condition Log tab selected, right-click anywhere in the Conditions Pane.
2. Select Clear List from the menu.
Figure 38. Clearing the Condition Log Tab
iMonitor User Guide

iDX Release 3.3
31
Conditions
2.1.3 Elements with Multiple Conditions

Multiple conditions often exist simultaneously on a network element. In that case, the overall
state of the element reflects the highest severity of any condition as follows:
No conditions: overall state is OK
One or more Warnings: overall state is Warning
One or more Warnings and one or more Alarms: overall state is Alarm
Remote has been sent Offline: overall state is Offline
2.1.4 Offline State

The offline state is a special condition that overrides all other warnings and alarms. This state
applies only to remotes. The offline state can be initiated by a remote user before turning the
remote off, to indicate to the network operator that no problem investigation is necessary.
When a remote is sent offline by the remote user, iMonitor and the NMS event server ignore all
subsequent alarms. If a unit is turned off without sending it offline first, the remote enters
the Alarm state at the hub.
The offline state clears automatically when the remote is turned back on and re-acquires the
network.
2.1.5 Alarms and Warnings on Elements

Table 5 and Table 6 list the alarm and warning conditions that can be raised for the various
elements.
Table 5. Explanation of Alarms by Element
32
Element
Alarm Condition
Explanation
Chassis
Chassis Down
iMonitor cannot communicate with the chassis
Chassis Manager Down
Chassis cannot communicate with NMS chassis manager

process
Protocol
Processor
Protocol Processor Down
The heartbeat has not been received from the Protocol

Processor
Hub Line
Card
Line Card Down
iMonitor cannot communicate with the Hub Line Card
Rx SCPC Loopback C/N
Line card downstream loopback exceeds clear sky C/N.
TDM Lock
Hub line card is no longer locked to the downstream

loopback
10 MHz Clock Alarm
Board does not support 10 MHz clock
GIG E Failed
Gibabit Ethernet Port Failed
Hub Stats Alarm
Stopped receiving statistics from hub line card
Backplane Lost SOF
Hub line card lost backplane Start of Frame
NCR Missing
NCR sync not received from Tx line card
PPS Missing
Hub line card does not detect pulse per second signal
iMonitor User Guide

iDX Release 3.3
Conditions
Table 5. Explanation of Alarms by Element

Element
Alarm Condition
Explanation
Remote
UCP out of Network
Remote has time out on UCP message
LAT Timeout
Stopped receiving echo reply from remote
LL Down
Remote Link Layer is down
Table 6. Explanation of Warnings by Element

Element
Warning Condition
Explanation
Chassis
Power Supply n
Failed
Fan n
Failed
RCM (Ref Clock Module) n
Failed
Four Slot Chassis Over

Temperature
Chassis exceeds temperature limit
Four Slot RCM A Not Present
RCM A has not been installed in the Chassis
Four Slot RCM A Fault
RCM A of the chassis has failed
Four Slot RCM B Not Present
RCM B has not been installed in the chassis
Four Slot RCM B Fault
RCM B of the chassis has failed
Four Slot Power Alarm A Bad
Chassis power supply A has failed
Four Slot Power Alarm A Over

Temperature
Chassis power supply A exceeds temperature limit
Four Slot Power Alarm B Bad
Chassis power supply B has failed
Four Slot Power Alarm B Over

Temperature
Chassis power supply B exceeds temperature limit
Four Slot FSM Not Present
FSM has not been installed on the chassis
Four Slot FSM Fault
FSM has failed on the chassis
Four Slot FSM Fan Fault
FSM fan has failed on the chassis
Four Slot IFM Not Present
IFM has not been installed on the chassis
Four Slot IFM Fault
IFM has failed on the chassis
Four Slot Alarm Disabled
Audible alarms are disabled for the chassis
Four Slot OPM A Fault
OPM A has failed on the chassis
Four Slot OPM B Fault
OPM B has failed on the chassis
Rx Overflow of frames
Downstream Packets per sec. overdrive
Back plane lost 10 MHz Clock
The 10 MHz reference timing signal is absent from the

chassis backplane
Acq Hub CRC Errors
Number of acquisition CRC errors exceeds maximum
Four-Slot
Chassis
Hub Line
Card
iMonitor User Guide

iDX Release 3.3
33
Conditions
Table 6. Explanation of Warnings by Element (continued)
34
Element
Warning Condition
Explanation
(Hub Line
Card)
Traffic Hub CRC errors
Number of traffic CRC errors exceeds maximum
Fll DAC Errors
Internal oscillator is out of calibration. (Also referred

to as Clock DAC)
Downstream PPS overdrive
Downstream overdrive condition detected on line

card
GIGE health
Error on GIGE Ethernet port of the line card
Inroute AGC out or range
AGC measurement above or below defined limits
Loss of NCR Sync
NCR count not synchronized to Master NCR count
Protocol
Processor
Blade CPU high
Blade CPU usage is above the defined limit
Remote
AGC Out of Range
Remote Automatic Gain Control outside limits.
Blade no Encryption License
The remotes PP blade has no encryption license
Calibrated Transmit Power
Transmit power is outside the defined limits
Certificate has Expired
X.509 certificate on TRANSEC remote has expired
Certificate is Invalid
X.509 certificate on TRANSEC remote is invalid
Certificate will Expire
X.509 certificate on TRANSEC remote will expire in 30

days
CRC8 Errors
Number of CRC8 errors exceeds limit
CRC32 Errors
Number of CRC32 errors exceeds limit
Downstream SNR out of range
The downstream C/N measured at the remote is

outside limits
Fan Alarm
An internal fan has failed. Raised for 73xx remotes

only
Fll DAC Errors
Internal oscillator is out of calibration. (Also referred

to as Clock DAC.)
GPS Signal Lost
Mobile remote has lost GPS input
Latency
Measured latency, hub to remote, exceeds the define

maximum
Local LAN Disconnect
LAN port on remote is disconnected
Lost Contact
PP has temporarily lost contact with remote
Maximum Tx Power
Remote transmit power is approaching the maximum
Nominal Carrier Equivocation

Occurring
A remote is switching nominal carriers rapidly on a

specific inroute ID
Timing Offset
The remotes timing offset is out of range
Remote Off-line State
The remote has been sent off-line
Remote Temperature
Remote temperature is outside the defined limits
iMonitor User Guide

iDX Release 3.3
Conditions
Table 6. Explanation of Warnings by Element (continued)

Element
Warning Condition
Explanation
Remote Tx Acq CRC
Number of TDMA upstream acquisition CRC errors

exceeds limit
Remote Tx Data CRC
Number of TDMA upstream data CRC errors exceeds

limit
Remote Tx Acq Mismatch
Number of TDMA upstream acquisition bursts from an

unexpected remote exceeds limit
Remote Tx Data Mismatch
Number of TDMA upstream data bursts from an

unexpected remote exceeds limit
Remote Tx Data Missing
Number of TDMA upstream data slots for which no

data was received exceeds limit
Remote Tx SCPC HDLC Error
Number of upstream octet and CRC errors exceeds

limit for SCPC return channel
Remote Tx SCPC Data Mismatch
Number of upstream IP packets from an unexpected

remote exceeds limit for SCPC return channel
Rx SCPC C/N
Remote receive downstream carrier exceeds clear sky

C/N. Value will be -1 or -100.
Upstream C/N0 out of range
The remotes upstream C/N0 measured at the hub is

outside limits
2.1.6 NMS Database Replication Warnings

Beginning with iDX Release 3.1, iDirect supports replication of NMS databases from the
Primary NMS Server (MySQL Master) to one or more Backup NMS Servers (MySQL Slaves). For a
detailed description of this feature, see the chapter titled NMS Database Replication in the
Technical Reference Guide.
The scripts that make up the iDirect replication tool set send warnings and events to the NMS
Event Server for display in iMonitor. For example, on successful completion of any task each
script sends an event listing the task and the fact that it was completed successfully. On any
task failure each script sends a warning listing the task and a brief description of the failure.
NOTE: If NMS Database Replication fails, an active condition will be raised in
iMonitor. It is important to take action to recover from the failure and clear the
condition. If no action is taken, the replication log files on the Primary NMS Server
can no longer be purged and it is possible to run out of disk space. For more
information, see the Technical Reference Guide.
Table 7 lists the iMonitor warnings that can be raised by the NMS Database Replication scripts
that run on the Primary NMS Server (MySQL Master).
iMonitor User Guide

iDX Release 3.3
35
Conditions
Table 7. Warnings Raised by NMS Database Replication Scripts on MySQL Master

Script Name
cr8DbMaster
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
Invalid keep time specification

MySQL account password missing, user: app.
36
iMonitor User Guide

iDX Release 3.3
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.
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
Host is not reachable, skipping.

User idirect cannot ssh into host <slave_ip> without a password, skipping.
FAILED while writing files to slave: <slave_ip>.
MySQL account password missing, user: app
Failed to connect to MySQL database on master with credentials.
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 password missing, user: app.
iMonitor User Guide

iDX Release 3.3
37
Placing an Element Under Observation
2.2

An element can be placed under observation in order to monitor its conditions. The
following elements can be placed under observation:
Protocol Processor
Blade
Line Card
Remote
Chassis
To place an element under observation:

1. Right-click the element in the iMonitor Tree and select Under Observation from the
menu.
2. Select ViewConditions from the main menu or click the Toggle Conditions icon
(eyeglasses) on the main toolbar.
38
iMonitor User Guide

iDX Release 3.3
Figure 39. Selecting the Toggle Conditions Icon

3. Click the Observation View tab to view only the conditions for elements under
observation.
Figure 40. Observing Conditions

4. To cancel observation of an element, right-click a condition and select Cancel
Observation.
Figure 41. Cancelling Observation of an Element

NOTE: Canceling the observation of an element removes that elements
conditions from the Observation View.
iMonitor User Guide

iDX Release 3.3
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.
Figure 42. Remote Control Panel
2.2.1 Viewing Conditions or Events

It can be useful to retrieve events over an extended time period for one or more remotes.
Although it is possible to retrieve all events and sort the results, iMonitor can also filter
historical events. Specify a text filter to display only those events that match the filter.
The text filter is available at the bottom of the historical time range parameters dialog box
(Figure 45 on page 42). A text filter can be entered either prior to retrieving events or from
the Time Range button on an existing events display. The filter values are applied only to the
Event Description section of the event message.
The simplest filter string is a substring of the event description, such as server. Any event
message that contains the specified substring is displayed in the results. The text filter field
also supports Linux regular expressions for complex search filters. For instructions on forming
regular expressions, see any Linux reference book.
40
iMonitor User Guide

iDX Release 3.3
To retrieve and view conditions or events for an element:

1. Right-click the element in the tree and select Conditions or Events to open the Select
Items dialog box.
Figure 43. Select Items Dialog Box

2. To retrieve conditions or events in real-time, click OK.
3. To view past conditions or events, click either Historical or Get Past.
NOTE: A Text Filter in the Get Past time range dialog box (Figure 45) only applies
to the Event Description field of the event message.
a. For Historical data, click Time Range to open the Select Time Range dialog box
(Figure 44 for Conditions and Figure 45 for Events). Alternatively, click the ellipses
(...) next to the Start Time and End Time to set the time range using the graphical
clock.
iMonitor User Guide

iDX Release 3.3
41
Figure 44. Conditions Select Time Range Dialog Box
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
iMonitor User Guide

iDX Release 3.3
Figure 46. Get Past Drop-Down List

4. Select the elements for which to view conditions or events. The options in the Select
Items dialog box differ depending on the level of the element selected in the tree.
5. Click OK to view the conditions or events. For conditions, follow the directions beginning
in Step 6. For events, see Step 10 on page 45.
6. When retrieving conditions, the Conditions pane opens showing the conditions logged
over the specified time period in a multicolumn format (Figure 47).
Figure 47. Conditions Results in Multicolumn Format

NOTE: On the Conditions tab, a remote may have an arrow next to it. Click the
arrow to expand the view to show all conditions for that remote.
7. To view conditions in a graphical format, click the Time Line tab (Figure 48).
Figure 48. Conditions Time Line Results in Graphical Format
iMonitor User Guide

iDX Release 3.3
43
8. Right-click in the Time Line display to view the results in Seconds, Minutes, or Hours.
Figure 49. Selecting Time Scale in the Conditions Time Line

9. Select Detail from the menu (Figure 49) to display the following information:
Name of Network Element
Type and Serial Number of a Remote or Line Card
Current Date
Number of hours it has been up
Number of hours it has been down
Percentage of time it has been up (Up %)
Percentage of time it has been down (Down %)
Figure 50 shows the Conditions Time Line Tab expanded to view details.
Figure 50. Conditions Time Line Tab with Detail Selected
44
iMonitor User Guide

iDX Release 3.3
10. When retrieving data on events, the Events pane appears (Figure 51). Data in the Events
pane is displayed in a multicolumn format only.
Figure 51. Event Results
2.2.2 Interpreting Conditions

By default, conditions are sorted in ascending order based on the timestamp. To re-sort the
conditions, click on the desired column heading.
Each line in the conditions display shows a state change for the element at the timestamp
indicated. A state change occurs when a condition is raised or cleared. If the entry contains
an arrow icon in the first column, additional conditions were active for the element at the
time of the state change. Click the arrow icon to view these conditions and the times at which
they first occurred.
Arrow
Figure 51 shows an example of the conditions display, including elements with multiple
conditions.
iMonitor User Guide

iDX Release 3.3
45
Figure 52. Conditions Example

The example in Figure 51 shows a remote reset resulting in the following conditions:
1. The first entry shows the remote state at the start of the specified time range: the
remote is OK, and the last condition that cleared was DOWNSTREAM_SNR.
2. The next entry shows that the protocol processor lost contact with the remote after the
reset was sent from iBuilder.
3. The next entry shows two conditions: the LOST_CONTACT warning is still active, and has
been joined by the layer 3 alarm LAT_TIMEOUT.
4. Finally, the Protocol Processor declares the remote OUT_OF_NETWORK, and this condition
is added to the list, giving us a total of three simultaneous conditions.
5. The next line shows that two of the three conditions cleared: The remote is back in the
network and the Protocol Processor has re-gained contact with it. The layer 3 alarm at
this point is still active.
6. The next line shows that the last condition, LAT_TIMEOUT, cleared.
7. The last two lines show a separate condition that was raised and cleared in a 15-second
time span.
When multiple conditions are shown, the icon in the left column does not represent the
current state of the remote. Rather, it shows the type of condition that occurred at that time.
For example, in number 5 above, the state of this remote is still ALARM, since the layer 3
alarm is still active. However, this particular entry represents the clearing of two conditions
indicated by the green icon.
46
iMonitor User Guide

iDX Release 3.3
Examples of System Events
2.3
Examples of System Events

By default events are displayed in real-time and are sorted in ascending order by timestamp.
Re-sort the display on any column in ascending or descending order by clicking on the column
heading. Select historical events to view events from the events archive.
Examples of system events include:
2.4
Terminal connection set up or torn down
Uplink control message from the Protocol Processor to remotes
Sweep messages during remote acquisition
Multicast package processed or rejected
Firmware image or options file written to flash
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:
Teleport: Teleport Condition Snapshot
Network: Network Condition Snapshot, Network Data Snapshot, Line Card Data Snapshot
Inroute group: Network Condition Snapshot, Network Data Snapshot, Line Card Data
Snapshot
Remote: Device Condition Snapshot
2.4.1 Network, Teleport and Device Condition Snapshot

Condition Snapshots contain multicolumn lists showing the states of the elements in a
compact view. The Network and Teleport Condition Snapshots show all elements in the
selected teleport, network, or inroute group. The Device Condition Snapshot shows only the
remote.
To view a Condition Snapshot:
1. Right-click a teleport, network, inroute group or remote.
2. Select Network Condition Snapshot, Teleport Condition Snapshot, or Device Condition
Snapshot to view the Condition Snapshot pane.
Figure 53 shows a Network Condition Snapshot launched at the network level of the
tree. (Both the List and Detail views are shown. To toggle between these views, rightclick in the window and selecting List or Details from the menu.
iMonitor User Guide

iDX Release 3.3
47
Snapshots
Figure 53. List and Details View of Condition Snapshot

Depending on the selection, the Condition Snapshot includes the following elements:
Teleport Condition Snapshot includes all protocol processors, protocol processor
blades, chassis, inroute groups, and remotes under the teleport.
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.
Device Condition Snapshot from a remote includes only the remote.
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
iMonitor User Guide

iDX Release 3.3
Snapshots
Figure 54. Remote Submenu in Condition Snapshot

4. In the lower half of the submenu shown in Figure 54 are several options for changing the
Condition Snapshot view:
iMonitor User Guide

iDX Release 3.3
49
Snapshots
Compact Icons
Arrange Icons
List
Details
Details in Group
Real-time Status Only
Activated
5. Figure 55 shows the results of selecting Details for the Teleport Condition Snapshot.
Figure 55. Teleport Condition Snapshot: Detail View

6. Hover the mouse pointer over an element in the snapshot to view information about that
element. Figure 56 shows the mouse pointer hovering over a line card.
Figure 56. Condition Snapshot: Hovering Mouse in Details View

The information in Figure 56 includes:
Model Type and Serial Number
50
iMonitor User Guide

iDX Release 3.3
Snapshots
Type (For example, line card, remote, etc.)
Name
Current Condition
Additional Details about the elements condition or configuration
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.
Multiple Selection Options in Condition Snapshot View

Use Windows multiple-select keys to select any number of remotes from the Network
Condition Snapshot display. The selected elements are used to populate the parameters
dialog windows for the following iMonitor displays:
SAT/IP Traffic Stats
Latency
Events
Conditions
Network Data Snapshot
SAT/IP Long Term Bandwidth Reports
Remote Availability Report
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.
Figure 57. Network Conditions: Selecting Multiple Remotes in Details View

2. With the mouse pointer located over the highlighted elements, right-click and select a
report. For this example, the Remote Availability report was selected.
iMonitor User Guide

iDX Release 3.3
51
Snapshots
Figure 58. Select Remotes Dialog Box

Notice that the resulting Select Remotes (Figure 58) dialog box shows only the remotes
highlighted in Figure 57. When this same report is selected from the Tree, even with these
remotes highlighted, the resulting dialog box lists all of the remotesnot just the
highlighted remotes. Therefore, it is important that the mouse pointer is actually over
the highlighted elements when opening the menu.
3. Make any further selections in the dialog box.
4. Click OK to display the report.
Figure 59. Example of Remote Availability Report
52
iMonitor User Guide

iDX Release 3.3
Snapshots
2.4.2 Network and Line Card Data Snapshot

The Network Data Snapshot shows real-time data and configuration parameters for a group
of remotes in a multicolumn list. The Line Card Data Snapshot provides the same capability
for a group of line cards. This is useful for monitoring real-time data for multiple elements
simultaneously.
To view a network or line card data snapshot:
1. Right-click a network or inroute group.
2. Select Network Data Snapshot or Linecard Data Snapshot to display the Select Items
and Stats dialog box (Figure 60).
Figure 60. Select Items and Stats Dialog Box

The Select Items and Stats dialog box has two panes. The pane on the left lists either
Remotes or Line Cards. (Figure 60 shows remotes because Network Data Snapshot was
selected for this example.) The pane on the right lists all the data available for these
remotes or line cards.
3. In the pane on the left, select the remotes or line cards to view.
By default all elements are displayed in the left-hand pane. To select only Activated
elements, click Active. To clear all selections, click Clear.
4. In the pane on the right:
a. Expand the tree.
b. Select all parameters to view for the selected elements.
iMonitor User Guide

iDX Release 3.3
53
Snapshots
5. Click OK to view the Data Snapshot. Only the selected elements and parameters are
displayed.
Figure 61. Network Data Snapshot

NOTE: Parameters with defined limits, such as upstream C/N0, are displayed in
yellow if the values fall outside those limits. Remotes that are out-of-network are
displayed in red.
6. Right-click anywhere that data appears in the Data Snapshot to view the following
options:
Figure 62. Data Snapshot Right-Click Options

7. Select from the following options:
Copy the data to the clipboard for pasting into other applications
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
Fit the columns to the size of the current window
iMonitor User Guide

iDX Release 3.3
3 Monitoring Performance
and Status
This chapter describes how to view and interpret performance information for iDirect network
elements.
3.1
Monitoring Protocol Processor Blades

The iMonitor Blade Info Pane shows the activity and configuration of protocol processor
blades. This information includes the processes running on each blade, the remotes assigned
to each blade, and the CPU utilization of each blade. For TRANSEC blades, iMonitor also shows
the status of the connection to the Master GKD if GKDs are configured for the TRANSEC
networks.
To view protocol processor blade information:
1. Right-click a protocol processor or a blade in the iMonitor Tree and select Blade Info to
open the Blade Info pane.
Figure 63. iMonitor Blade Info Pane: Initial View

Click the Blade Info Pane tabs and expand the contents to display the following information
about the blades:
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.
iMonitor User Guide

iDX Release 3.3
55
Monitoring Protocol Processor Blades
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.
Figure 64. iMonitor Blade Info Tabs

3. Right-click the blade in any of the first three tabs and select CPU Usage to view real-time
CPU usage in graphical and multicolumn formats. See CPU Usage on Protocol Processor
Blades on page 64 for details.
56
iMonitor User Guide

iDX Release 3.3
Using the Remote Probe
3.2

The Probe is used to perform specific tasks on a single remote. The probe can also retrieve
protocol layer statistics from the Protocol Processor that controls the remote.
The Probe pane (Figure 66 on page 58) is organized in sections with the following functions:
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.
Figure 65. Probe Remote Power for TDMA Remote in Network
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.
iMonitor User Guide

iDX Release 3.3
57
To use the Probe:

1. Right-click a remote in the iMonitor tree and select Probe from the menu to open the
Probe dialog box (Figure 66).
Figure 66. Probe Dialog Box
58
iMonitor User Guide

iDX Release 3.3
2. To change the remote transmit power:

a. Click Change in the Remote Power section to open the Change Remote Tx Power
dialog box.
Figure 67. Changing the Remote Transmit Power

b. Enter the New Tx Power.
NOTE: The New Tx Power cannot exceed the Maximum Power defined for the
remote in iBuilder.
c. Click Set.
3. To connect directly to the remote or protocol processor blade, click Remote or Blade in
the Terminal Sessions area of the Probe dialog box.
Figure 68. Probe Dialog Box: Terminal Sessions

4. To reset the remote, click the Reset button in the Reset Remote area of the Probe dialog
box.
iMonitor User Guide

iDX Release 3.3
59
Figure 69. Probe Dialog Box: Reset Remote

5. To transmit an unmodulated (CW) or modulated (PN) carrier in the Cross Polarization
area of the dialog box (Figure 70):
Figure 70. Probe Dialog Box: Cross Polarization

a. Specify the RF Uplink Frequency. This is the center frequency of the CW or PN
satellite carrier.
b. Specify the BUC LO Frequency translation for the remote BUC. This is the local
oscillator frequency of the BUC. This value is configured in iBuilder in the Frequency
Translation field of the BUC that is assigned to this remote.
c. For a PN carrier, enter a Symbol Rate under Specify Modulated Carrier.
d. Click Start CW to begin transmitting an unmodulated carrier, or click Start PN to
begin transmitting a modulated carrier.
e. Once the carrier is active, click the up and down arrows to adjust the Transmit
Power. Each click adjusts the transmit power up or down by 0.5 dBm.
f.
60
To change to a different frequency, click the Stop button before entering the new
frequency and restarting the carrier.
iMonitor User Guide

iDX Release 3.3
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.
Figure 71. Probe Dialog Box: Selecting a Protocol Layer

NOTE: Interpretation of protocol layer statistics requires knowledge of the
protocol processor software. These statistics can be useful when working with
iDirect support personnel or engineers to understand network performance. They
are not intended for customers working on their own and their meanings are not
documented in this user guide.
7. Select the appropriate button to the right to View the desired data, Reset the statistics,
or perform the Bounce function. To save the statistics to a file, click the Save To File
button.
iMonitor User Guide

iDX Release 3.3
61
Figure 72. Probe Dialog Box: Protocol Layer Operations
3.2.1 Modifying the Timeout Duration for a CW or PN Carrier

A carrier launched from the Cross Polarization section of the Probe automatically stops
transmitting five minutes after the carrier was started or the power was last adjusted. To
modify this timeout in iBuilder:
1. Right-click the remote in the iBuilder Tree and select ModifyItem.
2. Click the Custom tab.
3. In the Remote-side Configuration section of the Custom tab, define the following custom
key:
[OOB_PARAMS]
cross_pol_test_timeout = <Seconds>
where <Seconds> is the carrier timeout in seconds.
The example in Figure 73 sets the timeout to 600 seconds (10 minutes).
62
iMonitor User Guide

iDX Release 3.3
Figure 73. Setting the Timeout for a CW or PN Carrier in iBuilder

4. Click OK to save the remote configuration.
5. Right-click the remote in the iBuilder Tree and select Apply ConfigurationReliable
Remote-Side (TCP).
6. When the confirmation dialog box opens, click Yes to send the changes to the remote.
7. When the new dialog box opens, click Reset Now for the updated timer to take effect on
the remote.
iMonitor User Guide

iDX Release 3.3
63
CPU Usage on Protocol Processor Blades
3.3

To view the CPU Usage of individual protocol processor blades:
1. Right-click a blade in the iMonitor Tree and select CPU Usage. The Select Items dialog
box opens (Figure 74).
NOTE: Only Real-time data is available.

2. Select a blade or blades to monitor. Line Cards and Remotes cannot be selected.
3. Click OK to view the Blade CPU Usage pane. The Chart View tab is selected by default
(Figure 75).
64
iMonitor User Guide

iDX Release 3.3
Figure 75. Blade CPU Usage: Chart View Tab

4. Click the List View tab to view the data in multicolumn format.
Figure 76. Blade CPU Usage: List View Tab

5. CPU Usage information is also available in multicolumn format on the CPU Usage tab. See
Monitoring Protocol Processor Blades on page 55.
iMonitor User Guide

iDX Release 3.3
65
Adaptive TDMA
3.4
Adaptive TDMA
The following iMonitor displays provide analysis of Adaptive TDMA performance:
Timeplan
Inroute Group Composition Usage
C/N0 Distribution
Upstream C/N0 and Thresholds
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 average number of allocated traffic slots per TDMA frame
The average number of free traffic slots per TDMA frame
The Inroute Group Composition (IGC) assigned to the inroute group at the time of each
statistics sample
To view the Timeplan display:

1. Right-click a network or inroute group in the iMonitor tree and select ATDMA StatsTime
Plan to open the Select Inroute Groups dialog box (Figure 77).
Figure 77. Select Inroute Groups in Dialog Box
66
iMonitor User Guide

iDX Release 3.3
Adaptive TDMA
2. Select the Inroute Groups to view.

3. To view historical data, select Historical and enter a Time Range.
4. To view past data that continues to update in real time, select a Get Past time interval.
5. Click OK to view the Timeline tab containing the Timeplan Graphs (Figure 78).
Figure 78. Timeplan Graphs

The Timeline tab has two graphs representing the TDMA Timeplan:
The top graph shows the total TDMA traffic slots (Capacity) and the portion of that
capacity that was allocated (Total Slots) in average traffic slots per frame over time.
Notice in Figure 78 that the Capacity changes (top graph) as different IGCs are
selected for the inroute group (bottom graph).
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.
iMonitor User Guide

iDX Release 3.3
Select Legend to display or hide the legend.
67
Adaptive TDMA
9. To select which graphs to view:

Click All to view both graphs.
Click Slots to view only the graph showing capacity versus total slots.
Click IGC to view only the IGC usage graph.
Click the List Data tab to view the Timeplan statistics in a multicolumn list (Figure 79).
Figure 79. Timeplan Statistics in Multicolumn List

The List Data tab shows the following statistics for each statistics record:
The date and time of the sample
68
The Capacity of the inroute group in slots per frame
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
iMonitor User Guide

iDX Release 3.3
Adaptive TDMA
3.4.2 Inroute Group Composition Usage

The Inroute Group Composition Usage display can be used to look for discrepancies between
actual and expected usage of the IGCs configured for an inroute group. This display can be
launched from the Network and Inroute Group levels of the iMonitor tree. It includes the
following panes per Inroute Group:
A histogram showing the percentage of time each IGC was in use over the selected
statistics period
A time line graph showing the IGC selections over time
A multicolumn list of statistics records showing IGC usage and the Figures of Merit used to
select the next IGC
To view the IGC Usage display:

1. Right-click a network or inroute group in the iMonitor tree and select ATDMA StatsIGC
Usage to open the Select Inroute Groups dialog box (Figure 77 on page 66).
5. Click OK to view the Graph tab containing a histogram showing Inroute Group
Composition Usage (Figure 80).
Figure 80. IGC Usage Histogram

The graph shows the percentage of time each IGC was in use for the time range of the
statistics. For real-time data, the graph updates automatically as new statistics records
are received.
6. 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.
iMonitor User Guide

iDX Release 3.3
69
Adaptive TDMA
7. Right click anywhere in the main window and select Type to change the type of graph
(Figure 81).
Figure 81. IGC Usage Histogram: Changing the Graph Type

8. Click the Timeline tab to view the time periods during which each IGC was in use
(Figure 82). This graph is similar to the graph Timeplan IGC graph shown in Figure 78.
Figure 82. IGC Usage: Timeline Graph

9. Click Hour, Min or Sec to change the time scale on the x axis.
70
iMonitor User Guide

iDX Release 3.3
Adaptive TDMA
Select ChangeBack Color to modify the background color.
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).
Figure 83. IGC Usage: Multicolumn List

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.
iMonitor User Guide

iDX Release 3.3
71
Adaptive TDMA
3.4.3 C/N0 Distribution

The Uplink Control Process (UCP) at the hub continuously adjusts the transmit power of each
remotes upstream TDMA bursts such that all bursts transmitted on each TDMA upstream
carrier are received at approximately the same C/N0 as measured at the hub. The C/N0
Distribution display shows the degree of scattering of these signal quality measurements
around their nominal values. The nominal values are the target detection thresholds of each
carrier in the inroute group. Ideally, the observed values should be clustered close to the
target thresholds. Systematic deviations or large scattering may indicate that the system can
be optimized by adjusting parameters that affect the UCP processing. UCP is discussed in
detail in the chapter Uplink Control Process of the Technical Reference Guide.
The C/N0 Distribution can be observed for individual carriers and for inroute groups. For
individual carriers, the graphs are based on the actual C/N0 values as measured at the hub in
relation to the target thresholds. The target threshold displayed for a carrier is the C/N
threshold from the Link Budget Analysis Guide plus the Fade Slope Margin (M1) and Hysteresis
Margin (M2) configured for the inroute group adjusted for the carrier symbol rate.
Target C/N0 Threshold = LBA Guide C/N Threshold + 10log10 Symbol Rate + M1 + M2
Since the target C/N0 threshold is dependent on the carrier MODCOD, the threshold value for
a carrier changes whenever a new IGC is selected with a different carrier MODCOD assigned.
Figure 84 shows an example of graphs displayed on the C/N0 Distribution Timeline tab.
Figure 84. C/N0 Distribution: Timeline Tab
72
iMonitor User Guide

iDX Release 3.3
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).
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.
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 Single button to display one graph at a time.
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 %.
iMonitor User Guide

iDX Release 3.3
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).
Figure 85. C/N0 Distribution: Multicolumn List

The Current IGC for the inroute group at the time of the sample
For each carrier in the inroute group:
The target threshold at the time of the sample
The C/N0 of the configured upper limit (Max Threshold %)

The C/N0 of the configured lower limit (Min Threshold %)
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.
3.4.4 Upstream C/N0 and Thresholds

The Upstream C/N0 and Thresholds display shows upstream C/N0 measurements for individual
remotes over time. The display includes:
74
The C/N0 of the remotes TDMA bursts as measured at the hub

The nominal TDMA carrier of the remote
The target C/N0 thresholds of all carriers in the remotes inroute group.
iMonitor User Guide

iDX Release 3.3
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).

2. Choose the remotes to view by selecting or clearing the check boxes. To help with the
selection:
The All button selects all remotes.
The Clear button clears all selections.
The Active button selects all active remotes.
The Find Next button finds the next remote in the list that matches the Search
string.

5. Click OK to view the Timeline tab (Figure 87).
iMonitor User Guide

iDX Release 3.3
75
Adaptive TDMA
Figure 87. Upstream C/N0 and Thresholds: Timeline Tab

6. Click a remote in the list on the left to select that remote.
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 Single button to graph one data series at a time.
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
iMonitor User Guide

iDX Release 3.3
Adaptive TDMA
Figure 88. Upstream C/N0 and Thresholds: Multicolumn List

The List Data tab shows the following statistics for each statistics record for the selected
remote:
The Nominal Carrier of the remote
The C/N0 of the remote in dBHz

The IGC in use
The target threshold of each carrier in the inroute group in dBHz
iMonitor User Guide

iDX Release 3.3
77
Inroute Distribution
3.5
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.
3.5.1 Viewing Inroute Distribution

To view the inroute distribution:
1. Right-click a network or an inroute group in the iMonitor Tree and select Inroute
Distribution.
2. When Inroute Distribution is selected for an inroute group, the Inroute Distribution pane
(Figure 90 on page 78) opens immediately.
When Inroute Distribution is selected for a network, the Select Inroute Groups dialog
box opens (Figure 89). In that case:
a. Select the Inroute Groups to include in the display.
Figure 89. Select Inroute Groups Dialog Box

b. Click OK to open the Inroute Distribution pane.
Figure 90. Inroute Distribution Pane
78
iMonitor User Guide

iDX Release 3.3
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 Allocated (%) row shows:

The total slots per frame allocated to all remotes across all inroutes and the
percentage of the total bandwidth this represents
The total slots per frame allocated on the receive carriers of each line card and the
percentage of the total bandwidth this represents
The Maximum (For Current IGC) row shows:

The total number of slots in all timeplans
The total number of slots in the timeplans for each carrier received by each line card
3.5.2 ACQ Bounce from the Inroute Distribution Pane

The Inroute Distribution display provides the ACQ Bounce function for all remotes or
selected remotes in the inroute group. ACQ Bounce causes remotes to go through the
acquisition process without resetting.
To perform the ACQ Bounce:
1. Select the remotes to bounce in the Inroute Distribution pane.
2. Right-click the selected remotes and select ACQ Bounce form the menu.
Figure 91. Performing ACQ Bounce
iMonitor User Guide

iDX Release 3.3
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.
Figure 92. Select Items Dialog Box for Latency Measurements

2. Select the remotes for which to view latency results.
80
iMonitor User Guide

iDX Release 3.3
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.
Figure 94. iMonitor Latency Pane
iMonitor User Guide

iDX Release 3.3
81
Satellite Link Information
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

Satellite link information can be selected from:
Networks
Line cards
Remotes
3.7.1 Line Card Statistics

The NMS collects hub line card statistics on a regular basis and saves them in the historical
archive. iMonitor can display these statistics either in real-time or from the archive.
The line cards statistics are available from the following levels of the iMonitor Tree view:
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
Date/time the measurement was taken
Model type, serial number and IP address of the line card
Attempted transmits during the time period
Transmitted bytes during the time period
Transmit errors
Acquisition and Traffic CRC errors
TDMA Bursts detected
Received bytes
Receive power in dBm
SCPC carrier frequency offset
Number of DMA resets (receive buffer overflow)
PP line card tunnel receive errors
PP line card tunnel transmit errors
Receive digital gain
Clock DAC (Also called FLL DAC)
iMonitor User Guide

iDX Release 3.3
SCPC loopback clear sky C/N
SCPC loopback symbol offset
SCPC loopback frequency offset
TDM lock (locked or not locked)
Number of times TDM lock was lost
AGC gain
NOTE: Table 14 on page 179 lists all line card statistics archived by the NMS.
To view line card statistics:

1. Right-click a network or line card and select Line Card Stats to open the Select Line
Cards Dialog Box.
Figure 95. Select Line Cards Dialog Box

NOTE: When the line card statistics are displayed from the Network level of the
tree, all line cards in the network are shown in the Line Cards area of the Select
Line Cards dialog box. When displayed for a specific line card, only that line card
is shown in the dialog box.
2. In the Line Cards area of the dialog box, select the line cards for which to view statistics.
3. To retrieve historical statistics from the archive, select Historical and enter a Time
Range.
NOTE: Click the ellipses next to the Start Time and End Time to set the time using
the graphical clock display.
iMonitor User Guide

iDX Release 3.3
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.
5. Click OK to view the Hub Line Card statistics pane.
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
iMonitor User Guide

iDX Release 3.3
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
iMonitor User Guide

iDX Release 3.3
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.
Select None to clear the graph.
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.
Right-click inside the graph to view a menu of display options.
86
iMonitor User Guide

iDX Release 3.3
Figure 98. HLC Graph Right-Click Menu

Figure 98 shows the right-click menu for the Hub Line Card statistics graphs. Use the rightclick menu to change the display. For example:
Select ChangeScale to modify the scales of the x axis or y axis.
Change the background (Back Color) or Text color.
Select Mouse Tracking. Then click and drag along the plot line to view the value of each
data point.
Figure 99 shows the ChangeScale selections.
iMonitor User Guide

iDX Release 3.3
87
Figure 99. Hub Line Card Graph: Changing the Scale

NOTE: The Left, Right and Bottom selections toggle off and on the scale displays
on the left, right and bottom of the selected graph.
In the second tab, right-click anywhere in the column headings to display a menu of fields for
display. Checked fields appear as columns in the display. Figure 100 shows the available fields
for an individual SCPC return channel on an XLC-M line card (on the left) and for the XLC-M
line card itself (on the right).
Figure 100. Hub Line Card Statistics for an SCPC Return Channel and for an XLC-M Line
Card
3.7.2 Upstream Performance Statistics

The NMS collects upstream performance statistics per remote on a regular basis and saves
them in the historical archive. iMonitor can display these statistics either in real-time or from
the archive.
There are two types of upstream performance statistics:
88
iMonitor User Guide

iDX Release 3.3
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:
Network (by selecting Grouped Remotes)
Inroute Group (by selecting Grouped Remotes)
Remote
Upstream performance statistics displayed in iMonitor for remotes transmitting on a TDMA

inroute include:
The number of acquisition bursts received from the remote
The number of missing acquisition bursts
The number of traffic bursts received from the remote
The number of traffic CRC errors in bursts received from the remote
The number of missing traffic bursts
The number of keepalive bursts received from the remote
Upstream performance statistics displayed in iMonitor for remotes transmitting an SCPC

return channel include:
The number of IP packets received from the remote
The number of HDLC errors in packets received from the remote
The number of keepalive packets received from the remote

NOTE: Remote Return Channel Statistics on page 181 describes all upstream
performance statistics archived by the NMS.
To view upstream performance statistics for remotes:

1. In the iMonitor tree, right-click a remote and select Upstream Performance Graph, or
right-click a network or inroute group and select Grouped RemotesUpstream
Performance Graph.
The Select Remotes dialog box (Figure 101) opens.
iMonitor User Guide

iDX Release 3.3
89

NOTE: Select Upstream Performance Graph for Grouped Remotes to show every
remote in a network or inroute group in the Remotes area of the Select Remotes
dialog box. Select Upstream Performance Graph for an individual remote to show
only the selected remote in the dialog box.
2. In the Remotes area of the dialog box, select the remotes for which to view statistics.
3. If desired, select Historical and enter a Time Range to retrieve historical statistics from
the archive.
5. Click OK to view the Upstream Performance Stats pane.
90
iMonitor User Guide

iDX Release 3.3
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.
iMonitor User Guide

iDX Release 3.3
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.
Figure 103. Upstream Performance Statistics: Multicolumn List

Change the graphical display on the US Perf. Graph tab by toggling the buttons to the left of
the graph (Figure 102 on page 91). The graphs (as well as the related information displayed on
the second tab) are different for TDMA and SCPC upstream carriers.
The buttons work as follows:
92
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.
iMonitor User Guide

iDX Release 3.3
NOTE: As shown in Figure 104, hover the mouse pointer over any button for a
description of the buttons function.
Figure 104. Upstream Performance Statistics: TDMA and SCPC Buttons

Figure 105 shows the multicolumn list and graphical view of a remotes TDMA upstream data.
Figure 105. Remote Upstream Performance Statistics: Graph and Multicolumn List
iMonitor User Guide

iDX Release 3.3
93
Right-click inside the graph to view a menu of display options.
Figure 106. Upstream Performance Graph Right-Click Menu

Options for the right-click menu are described on page 87.
In the second tab, right-click anywhere in the column headings to display a menu of fields for
display. All checked fields appear on the screen. Figure 107 shows the available fields for
remotes transmitting on TDMA inbound channels (on the left) and for remotes transmitting
SCPC return channels (on the right).
Figure 107. Remote Upstream Performance Statistics for TDMA and SCPC Return Channels
94
iMonitor User Guide

iDX Release 3.3
Identifying Remotes Causing Rx CRC Errors on Line Cards

Transmit problems on one or more remotes may cause CRC errors on the hub line card that is
receiving the remotes TDMA upstream carrier. CRC errors could be caused by any of a number
of problems: a remote transmitting above the saturation point, a bad cable, interference,
etc.
In earlier releases, the total number of Rx CRC errors on a line card were reported in iMonitor
but these statistics were not available in iMonitor on a per remote basis. Beginning with iDX
Release 3.0, a consolidator process running on the protocol processor collects upstream
performance statistics (including CRC errors) per remote and sends them to the NMS for
logging to the statistics archive and for display in iMonitor. Since CRC errors per remote are
now displayed in iMonitor, it is no longer necessary to log on to the protocol processor blades
to identify which remote or remotes are causing Rx CRC errors at the hub.
Although the total CRC errors continue to be reported for line cards in the hub line card
statistics (see Line Card Statistics on page 82), use caution when drawing conclusions based
on those statistics. It is possible to see CRC errors reported in the hub line card statistics for
slots in which no bursts were actually transmitted. This is caused by false burst detection due
to random noise in the idle slots. False burst detection occurs primarily in IF test networks or
in networks with a high number of idle bursts on the upstream carrier(s).
The per remote upstream performance statistics reported by the protocol processor only
report CRC errors for remotes for assigned slots. If CRC errors are being reported on the line
card that are not being reported for specific remotes, then those CRC errors can be safely
ignored.
If a remote is generating excessive CRC errors at the hub, a warning is displayed in iMonitor.
Based on the TDMA upstream performance statistics, the NMS issues the warning
RemoteTxTDMATrafficCrc whenever any individual remote exceeds the defined limit for
traffic CRC errors. By default, RemoteTxTDMATrafficCrc is issued for a remote when CRC
errors occur in more than 0.01% of a remotes allocated upstream slots. To change this limit in
iBuilder for all remotes, select Global Warnings for Remotes from the Edit menu. To change
this limit in iBuilder for an individual remote, modify the warning on the remotes Warning
Properties tab. See the iBuilder User Guide for details.
Determine the number of TDMA traffic CRC errors caused by specific remotes by examining
the Upstream Performance Statistics in iMonitor. These statistics are discussed in detail in
Upstream Performance Statistics on page 88.
To determine the number of TDMA traffic CRC errors for a remote:
1. In the iMonitor tree, right-click a remote and select Upstream Performance Graph, or
right-click a network or inroute group and select Grouped RemotesUpstream
Performance Graph.
2. 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.
3. Click OK to view the Upstream Performance Stats pane.
4. In the tree to the left of the graph, click the remotes upstream channel.
5. Click the None button to deselect all statistics.
6. Click the second of the two CRC buttons (Data CRC Errors) to graph only traffic CRCs.
iMonitor User Guide

iDX Release 3.3
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.
3.7.3 SATCOM Graph, Remote Status and UCP Information

The SATCOM display shows satellite link characteristics for an individual remote on the
upstream and downstream channels, either in real-time or from the historical archive. This
display is most useful for showing the relationships between hub-side uplink power control
and remote transmit power. It also graphs the frequency and symbol offset calculations
applied to the remote from the Protocol Processor.
The SATCOM display is available only for individual remotes. Because the information in the
display is specific to a remote, selecting multiple remotes from an intermediate level in the
iMonitor tree opens a separate pane for each remote. This display can show up to one week of
UCP and Remote Status from the archive database.
96
iMonitor User Guide

iDX Release 3.3
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.
Note on Remote Rx Power

The receive power measured by the remotes is reported in the Rx Composite Power column
when viewing the Remote Status in iMonitor. Most iDirect remote model types use an RF
wideband power detector to measure Rx power. Evolution X1, X3 and X5 remotes do not have
RF wideband power detectors. Instead, these remote model types measure Rx Power over a
narrower bandwidth centered on the downstream carrier.
Because different model types measure the Rx power over different bandwidths, the Rx
Composite Power reported in iMonitor for an Evolution X1, X3 or X5 remote may be
significantly less than the Rx Composite Power reported for another remote model type when
the two remotes are receiving the same signal. This difference is expected and does not
indicate a problem on either remote.
To view the SATCOM Graph, Remote Status, or UCP Info on remotes, follow the directions
below.
NOTE: This information is also displayed on the remote Control Panel. See
Control Panel on page 125.
1. Right-click a remote and select SATCOM Graph or Remote Status/UCP Info to open the
Select Items dialog box. The remote is pre-selected in the Remotes area of the dialog
box.
Figure 109. Select Items Dialog Box with Remote Pre-Selected

2. To view historical data, select Historical and click Time Range to open the Select Time
Range dialog box. Then enter a Start Time and End Time, or use the slider to set the
Start Time. (See Figure 93 on page 81.)
iMonitor User Guide

iDX Release 3.3
97
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.
Figure 110. iMonitor SATCOM Graphs
98
iMonitor User Guide

iDX Release 3.3
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 1: The downstream signal-to-noise ratio (C/N) as measured at the remote,

superimposed on the number of times the remote has lost lock on the downstream carrier
(TDM lost). The TDM lost value is cumulative since the remote was last powered-up, but
this graph shows only deltas from message to message.
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.
Remote Status and UCP Information

Figure 111 and Figure 112 show examples of the Remote Status and UCP Info data.
NOTE: Some of the content of the remote status message is based on the mode of
operation. Therefore the columns displayed by iMonitor may vary depending on
the remote mode.
Figure 111. Remote Status Data
iMonitor User Guide

iDX Release 3.3
99
NOTE: Remote Status on page 183 describes all upstream performance statistics
archived by the NMS.
Figure 112. UCP Info Data

NOTE: Uplink Control Adjustments on page 184 describes all upstream
performance statistics archived by the NMS.
3.7.4 UCP Graph

The UCP graph is available from the following levels of the iMonitor Tree view:
Inroute Group (by selecting Grouped Remotes)
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
iMonitor User Guide

iDX Release 3.3
Figure 113. Select Remotes Dialog Box: Selecting Past Data

4. Click OK to view the UCP Graph pane.
5. When viewing multiple remotes, click the check boxes in the Name area of the UCP Graph
pane to select remotes for display on the graphs.
iMonitor User Guide

iDX Release 3.3
101
Figure 114. UCP Graphs for Grouped Remotes

As shown in Figure 114, there are four separate UCP graphs, one for each statistic:
Upstream C/N0
102
iMonitor User Guide

iDX Release 3.3
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.
Figure 115. UCP Graph Right-Click Menu

8. Each line on a graph represents the corresponding statistic for one of the remotes
selected in the Name column in Figure 114. Select Legend from the right-click menu to
determine which remote is represented by each line color.
9. To view the raw statistics for a remote, highlight the remote in the Name column and
then click the second tab with the remotes name. These statistics are identical to those
on the UCP Info tab of the SATCOM graph discussed in the previous section.
iMonitor User Guide

iDX Release 3.3
103
Group QoS Statistics
Figure 116. UCP Raw Data for Highlighted Remote

NOTE: To change the list of remotes without relaunching the display, click the
Filter button (Figure 114) to open the Select Remotes dialog box.
3.8

iMonitor displays the following real-time or historical Group QoS Statistics:
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
1. To view QoS statistics, do one of the following:

Right-click a Network or Remote in the iMonitor tree and select Downstream QoS
Stats from the menu.
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.
iMonitor User Guide

iDX Release 3.3
Figure 117. Selecting QoS Stats from iMonitor Menus

NOTE: Right-click a remote and select Downstream QoS Stats or Upstream QoS
Stats from the menu to view all QoS statistics for a single remote.
2. In the Group Tree pane of the Select Group dialog box, select an element in the tree
over which to aggregate the Group QoS statistics. Sub-elements are automatically
selected.
iMonitor User Guide

iDX Release 3.3
105
Figure 118. Selecting Elements for Group QoS Statistics

NOTE: Check Select Single Node to select an individual element in the Group Tree
pane. This is illustrated in Figure 119.
Figure 119. Selecting a Single Node for Group QoS Statistics

3. Select Real time and enter a Start Time, or enter a Start Time and End Time. Duration
will adjust automatically.
NOTE: Alternatively, use the slider to adjust Duration. Start Time and End Time
will adjust automatically.
4. Click OK to view the GQoS Distribution tab.
106
iMonitor User Guide

iDX Release 3.3
Figure 120. Group QoS Stats: Initial View

The Group Stats display has three tabs: the GQoS Distribution tab, the Plot tab and the List
tab. The GQoS Distribution tab is automatically selected when the display opens. Each of
these tabs is described in the following sections.
3.8.1 Group QoS Distribution Tab

The GQoS Distribution tab (Figure 120) of the Group QoS statistics shows requested,
allocated and free bandwidth for downstream carriers (networks) and inroute groups. The
example in Figure 120 shows the default display when the QoS Stats is selected for a network.
Bandwidth can be viewed for nodes in the Group QoS tree, for Remote Service Groups, or for
individual remotes. The display also provides zooming and filtering which is essential for
bandwidth analysis for large networks.
The Multicast Bandwidth Group is shown by default when the Group QoS Distribution tab is
opened for a Network. The Multicast Bandwidth Group can be hidden by clearing Show
Multicast in the right-click menu. For details, see Display Controls and Filters on page 112.
iMonitor User Guide

iDX Release 3.3
107
Group QoS View versus Remote View

The Group QoS Distribution tab provides two ways of viewing the QoS statistics: the Group
QoS View and the Remote View. Right-click anywhere in the main display and select or clear
GQoS View Mode to toggle between these two views. This is illustrated in Figure 121.
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
iMonitor User Guide

iDX Release 3.3
Viewing the Bandwidth for a QoS Node

Figure 122 shows how to view the QoS statistics for individual nodes.
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.
Nodes are highlighted as follows:
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.
iMonitor User Guide

iDX Release 3.3
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.
Figure 124. Group QoS Distribution: Base Measures in Right-Click Menu
110
iMonitor User Guide

iDX Release 3.3
The Base Measures are:
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 Allocated: The width of the nodes is proportional to the bandwidth allocated.
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
iMonitor User Guide

iDX Release 3.3
111
Display Controls and Filters

The menu selections in Figure 127 control which nodes are shown on the screen. Right-click
anywhere in the main display to select from these options.
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.
toggles off and on the Group QoS
Zoom Box is discussed in Using the Zoom Box on page 116.
Averaged is discussed in Viewing Real Time and Historical Data on page 114. (This
selection is only available for historical data.)
The Filter Settings work as follows:
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.
iMonitor User Guide

iDX Release 3.3
Figure 128 shows the ten remotes that have received the most bandwidth in combination with
the Static Base Measure.
Figure 128. Group QoS Distribution: Top Ten Remotes (Allocated)

Remotes can also be removed from and added to the Group QoS Distribution display by
clicking the Filter Remotes button to open the Select Remotes dialog box (Figure 129).
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.
iMonitor User Guide

iDX Release 3.3
113
Viewing Real Time and Historical Data

When viewing Real Time statistics, the Group QoS Distribution display is continuously updated
to show the data from the last record received by the NMS. The real-time display always
represents only the last record received. The display changes as new records are received.
For example, when a Base Measure such as BW Requested or BW Allocated is selected, nodes
in the display appear, disappear, or change width to match the data in each new record. For a
selected node, the statistical data at the bottom of the display also updates automatically to
match each new record.
Historical data can be viewed in three ways:
As individual statistics records
As individual statistics records replayed over the historical time range
As the average values of all statistics records in the historical time range
To view historical data for an individual statistics record:

1. Click and drag the slider at the bottom of the display to select a time within the historical
time range.
NOTE: The date and time at the left of the slider bar updates as the slider moves.
2. Release the mouse button to view the statistics record that includes the selected time.
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
iMonitor User Guide

iDX Release 3.3
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.
Figure 131. Group QoS Distribution: Replaying Historical Statistics

To replay the historical statistics:
1. Move the slider to any start time.
2. Click
to replay the statistics going forward in time.
3. Click
to replay the statistics going backwards in time.
4. Click
to stop replaying the statistics.
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.
iMonitor User Guide

iDX Release 3.3
115
Using the Zoom Box

Use the Zoom Box to zoom in on specific areas of the Group QoS Distribution display. This can
be very useful in networks or inroute groups with large numbers of remotes and virtual
remotes.
To use the Zoom Box:
1. Right-click anywhere in the Group QoS Distribution display and select Zoom Box from the
menu. The Zoom Window opens in the upper right corner of the display (Figure 133).
When the Zoom Window first opens, the area selected in the Zoom Box includes the entire
Zoom Window and therefore the entire display.
Figure 133. Group QoS Distribution: Zoom Window

NOTE: By default, Zoom Horizontal is enabled. With Zoom Horizontal enabled,
the Zoom Box always includes a vertical slice of the display from top to bottom
that can be moved horizontally.
2. To narrow the Zoom Box in the Zoom Window, right-click inside the Zoom Box and drag
the mouse pointer down. Resizing the Zoom Box zooms in on the portion of the Group QoS
distribution display included in the box.
116
iMonitor User Guide

iDX Release 3.3
Figure 134. Group QoS Distribution: Resizing the Zoom Box

3. To move the Zoom Box horizontally in the Zoom Window, click anywhere inside the Zoom
Box and drag the mouse pointer right or left.
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.
iMonitor User Guide

iDX Release 3.3
117
Figure 136. Group QoS Distribution: Clearing the Horizontal Zoom

6. To increase the size of the square Zoom Box, right-click inside the Zoom Box and drag the
mouse pointer up.
7. To decrease the size of the square Zoom Box, right-click inside the Zoom Box and drag the
mouse pointer down.
8. To move the square Zoom Box in the Zoom Window, click anywhere inside the Zoom Box
and drag the mouse pointer in any direction.
9. After the Zoom Box is positioned in the Zoom Window, close the Zoom Window by rightclicking in the main display and clearing the Zoom Box option in the menu. The display
shows only the area contained in the Zoom Box.
Figure 137. Group QoS Distribution: Viewing Statistics after Zooming

10. Hover the mouse pointer over any node in the display to view the Group QoS statistics for
that node.
11. Re-open the Zoom Box to resize the Zoom Box or to move the Zoom Box to a new location.
12. At any time, double-click anywhere in the main display or in the Zoom Window to return
to the full view.
118
iMonitor User Guide

iDX Release 3.3
3.8.2 Group QoS Plot Tab

The Group QoS Plot tab shows timeline graphs of the requested bandwidth, allocated
bandwidth and free bandwidth. To view these graphs:
13. Click the Plot tab.
Figure 138. Group QoS Stats: Plot Tab
iMonitor User Guide

iDX Release 3.3
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.
Figure 139. Group QoS Stats for Selected Bandwidth Group

15. Right-click anywhere in the plot area and highlight Select Graph to view or hide any of
the three graphs. Toggling any of the top three buttons on the left side of the display
performs the same function.
120
iMonitor User Guide

iDX Release 3.3
Figure 140. Group QoS Stats: Selecting Graphs to View

Use the context menu or the toggle buttons to change other aspects of the display. For
example:
Click Hour, Min or Sec to change the scale of the x axis to hours, minutes or seconds.
Select ChangeScale to modify the scales of the x axis or y axis

NOTE: The Tight button automatically adjusts the scale of the y axis to span
exactly the statistical data being reported.
Select Legend to display or hide the legend
Change the background (Back Color) or Text color.
Select Mouse Tracking and drag along the plot line to view the value of each data point.
Figure 141. Group QoS Stats: Changing the Scale

NOTE: The Left, Right and Bottom selections toggle off and on the scale displays
on the left, right and bottom of the selected graph.
iMonitor User Guide

iDX Release 3.3
121
3.8.3 Group QoS List Tab

The Group QoS List tab shows the requested bandwidth, allocated bandwidth and free
bandwidth in a multicolumn display. To view these graphs:
16. Click the List tab to view the Group QoS Stats in a multicolumn list (Figure 142).
Figure 142. Group QoS Stats: List Tab

17. Select elements at different levels of the tree in the left-hand pane to control the
aggregation of the statistics displayed in the table in the right-hand pane. Figure 142
shows the total statistics aggregated over the selected Bandwidth Group.
The following statistics are displayed in the List tab in the right-hand pane of the Group Stats
display:
BW Req shows the total bandwidth requested by the selected subgroup
BW Alloc shows the total bandwidth allocated by the selected subgroup
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.
Viewing QoS Service Level Statistics

The NMS logs the Upstream and Downstream Service Level statistics defined in Table 31 on
page 195. To view Service Level statistics in iMonitor, follow the steps in this section.
Downstream Service Level statistics are always available in iMonitor. However, Upstream
Service Level statistics sent by the remotes to the NMS consume significant satellite
bandwidth. Therefore, to maximize channel efficiency, a remote does not send any Upstream
TDMA or SCPC Service Level statistics to the NMS unless a remote-side custom key is defined.
To enable a remote to send upstream service level statistics to the NMS, use iBuilder to
configure the following custom key in the Remote-Side area of the Remote Custom tab and
apply the changes:
122
iMonitor User Guide

iDX Release 3.3
[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).
Figure 143. Selecting Service Levels to View Statistics

4. Click OK to view the Service Level statistics graph.
iMonitor User Guide

iDX Release 3.3
123
Figure 144. QoS Service Level Statistics Graph

5. Select a Service Level in the tree to view statistics for that Service Level.
6. Click the four top buttons on the left to toggle on and off the four graphs. There is one
graph per Service Level statistic:
Tx kbps / sec shows the traffic in Kbps for the Service Level.
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.
Saving QoS Statistics to an Excel Spreadsheet or to a CSV Formatted

File
To export the Group QoS statistics from the Group Stats List tab to an Excel spreadsheet or to
Comma Separated Variable (CSV) formatted file:
124
iMonitor User Guide

iDX Release 3.3
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.
Figure 145. Saving QoS Statistics

3. Enter a File Name and click Save.
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.
iMonitor User Guide

iDX Release 3.3
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.
Figure 146. Control Panel Tab: Example 1Figure 111 on page 99
126
iMonitor User Guide

iDX Release 3.3
Monitoring DVB-S2 Performance
Figure 147. Control Panel Tab: Example 2
NOTE: A maximum of four Control Panels can be displayed at the same time.
3.10 Monitoring DVB-S2 Performance

iMonitor provides different types of DVB-S2 performance graphs and statistics by right-clicking
the network elements in the iMonitor tree listed in Table 9.
Table 9. DVB-S2 Performance Monitoring: Availability for Network Elements
Type of DVB-S2 Monitoring
iMonitor Tree Level
ACM Gain
Network, Inroute Group, Remote and Tx Line card
MODCOD distribution
Network, Remote and Tx Line Card
MODCOD utilization
Network and Remote
Signal-to-Noise Ratio (SNR)
Network, Inroute Group and Remote
DVB-S2 hub line card debug statistics
Tx Line Card
3.10.1 Monitoring the ACM Gain of DVB-S2 Carrier

The ACM Gain represents the increase in performance achieved on a DVB-S2 outbound carrier
when the MODCOD used to transmit data is higher than the minimum MODCOD configured for
the carrier. View the ACM Gain for the entire carrier by launching the ACM Gain display from
iMonitor User Guide

iDX Release 3.3
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.
Figure 148. Selecting Remotes for ACM Gain

3. Select the remotes to monitor in the Remotes area of the dialog box.
4. Select the Historical check box to select a Time Range for viewing. Otherwise, select a
time interval from the Get Past drop-down menu, or click OK to begin viewing data in
real-time. (Real-time is selected by default from the Get Past drop-down menu.)
NOTE: For historical data, click the ellipses next to Start Time and End Time to
set the Time Range using the graphical clock display.
Figure 149. Select Time Range Graphical Slot Display
128
iMonitor User Guide

iDX Release 3.3
5. Click OK to launch the ACM Gain display. The ACM Gain tab is selected by default.
Figure 150. ACM Gain: ACM Gain Tab

The ACM Gain tab graph (Figure 150) shows the ACM Gain over time for the selected
remote(s) or for the entire DVB-S2 outbound carrier (if the display was launched from the
Line Card level of the iMonitor tree).
6. When launched from the Network or Inroute Group, click on any available remote in the
left pane to display the ACM Gain for that remote. Switch to a new remote at any time by
selecting it.
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.
iMonitor User Guide

iDX Release 3.3
129
Figure 152. Changing the Remotes in the ACM Gain Display

a. Use the arrow buttons to move remotes between the Available Remotes pane and the
Selected Remotes pane to modify the list.
b. Click OK to return to the main ACM Gain display.
8. Right-click in the graph to change the display by selecting menu options.
Figure 153. Changing the ACM Gain Display

For example, use the right-click menu to:
Change the scales of the x axis or y axis
Display or hide the legend
Change the background or text color
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
iMonitor User Guide

iDX Release 3.3
Figure 154. ACM Gain: List Data Tab

The table on the List Data tab shows the following information for each time period:
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.
3.10.2 Monitoring the MODCOD Distribution of a DVB-S2 Carrier

In an ACM network, the protocol processor adjusts the modulation and coding (MODCOD) of
the outbound channel on a frame-by-frame basis depending on the current receive
capabilities of the individual remotes in the network. When ACM is enabled for a DVB-S2
carrier, you can examine how the downstream data is distributed across the range of
MODCODs configured for the carrier in iBuilder. You can view the MODCOD distribution for all
downstream data by selecting MODCOD distribution from the Tx line card menu. You can view
the MODCOD distribution to specific remotes by selecting MODCOD distribution for a network
or remote.
Perform these steps to view the MODCOD distribution for a DVB-S2 carrier, or for selected
remotes receiving the carrier:
1. Right-click a DVB-S2 network, Tx line card, or remote in the iMonitor tree and select DVBS2 StatsMODCOD Distribution to open the Select Remotes dialog box.
iMonitor User Guide

iDX Release 3.3
131
Figure 155. Selecting Remotes for MODCOD Distribution

2. Select the remotes, type of data, and time range in the dialog box. (See page 128.)
3. Click OK to view the MODCOD Distribution display.
Figure 156. MODCOD Distribution Display: MODCOD Tab

4. If the display was launched from the Network, click on any available remote in the Name
column to display the MODCOD Distribution for that remote. Switch to a new remote at
any time by selecting it.
NOTE: The buttons on the left only apply to the Timeline tab.
NOTE: Click the Filter button to change the list of available remotes in the left
pane.
132
iMonitor User Guide

iDX Release 3.3
5. To see the MODCOD Distribution over time, click the Timeline tab.
Figure 157. MODCOD Distribution Display: Timeline Tab

The Timeline tab graphs the traffic of the selected remote per MODCOD over time. When
viewing the Timeline tab:
a. If the display was launched from the Network, click on any available remote in the
Name column to display the traffic for that remote. Switch to a new remote at any
time by selecting it.
b. Click the Hour, Min or Sec button to change the granularity of the x axis to hours,
minutes or seconds.
c. Select the None or All button to de-select or select all MODCODs.
d. Select Single to turn the MODCOD buttons into toggle buttons. When Single is
selected, only one MODCOD button can be selected at a time.
e. Click the MODCOD buttons to select which MODCODs appear on the graph. There is a
separate line on the graph for each selected MODCOD that is being transmitted. No
line will appear if there is no traffic being transmitted on that MODCOD.
NOTE: Right-click anywhere in the graph and select Legend to view a color-coded
legend of the traffic per MODCOD.
6. To see the MODCOD Distribution data in a multicolumn list, click the List Data tab.
iMonitor User Guide

iDX Release 3.3
133
Figure 158. MODCOD Distribution Display: List Data Tab

The table on the List Data tab shows the Total kilobytes transmitted during the time period as
well as the number of kilobytes transmitted at each MODCOD. For specific remotes, this
includes all data sent to that remote. If the display was launched from the Tx line card, then
the table includes all data transmitted on the DVB-S2 downstream carrier.
3.10.3 Monitoring the MODCOD Utilization of DVB-S2 Remotes

In an ACM network, the protocol processor adjusts the modulation and coding (MODCOD) of
the outbound channel on a frame-by-frame basis depending on the current receive
capabilities of the individual remotes in the network. Ideally, under clear sky conditions, a
remote should receive its downstream data on its configured Nominal MODCOD a high
percentage of the time.
The NMS provides periodic statistics to iMonitor on the operating MODCOD of each remote.
iMonitor uses those statistics to determine how efficiently each remote is consuming
bandwidth relative to its configured Nominal MODCOD. This efficiency of bandwidth usage is
displayed as a single Bandwidth Utilization factor with the following characteristics:
The Bandwidth Utilization factor is always greater than or equal to 1.
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.
To view the MODCOD Utilization for remotes:

1. Right-click a DVB-S2 network or remote in the iMonitor tree. Then select DVB-S2
StatsMODCOD Utilization from the menu to open the Select Remotes dialog box.
134
iMonitor User Guide

iDX Release 3.3
Figure 159. Selecting Remotes for MODCOD Utilization

3. Click OK to view the Message Structure tab of the MODCOD Utilization display. The
display contains one row for each remote.
Figure 160. MODCOD Utilization Display: Message Structure Tab

4. Select a remote in the Structure column. For Historical data (Figure 159), the time range
of the selected remotes data is displayed at the top of the display.
The Message Structure tab contains the following columns:
The Structure column contains the remote names. Select a remote in the Structure
column to display the data for that specific remote on the MODCOD tab or the
Detailed Data tab. (See page 136 and page 137 for descriptions of those tabs.)
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.
iMonitor User Guide

iDX Release 3.3
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.
Figure 161. MODCOD Utilization Display: MODCOD Tab

Figure 161 shows a remote that has received two MODCODs during the time represented
by the statistics. The remote received its outbound data on MODCOD 8PSK-3/5 for 91.95%
of the time and on MODCOD 8PSK-2/3 for 8.05% of the time.
6. To change to a different type of graph (such as a pie chart), right-click anywhere in the
display and select Type. Select a format from the list of options.
136
iMonitor User Guide

iDX Release 3.3
Figure 162. MODCOD Utilization Display: Changing the Graph Type

7. To view a legend showing the color coding of the different MODCODs, right-click anywhere
in the display and select Legend. (See Figure 162.)
8. To see the MODCOD Utilization data in a multicolumn list, click the Detailed Data tab.
Figure 163. MODCOD Utilization Display: Detailed Data Tab

This tab displays all the statistics records currently being analyzed for the specific remote
selected on the Message Structure tab. Each record includes:
The Date and time of the statistics record
The configured Nominal MODCOD of the remote at the time of the record
The Current 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.)
iMonitor User Guide

iDX Release 3.3
137
Determining the MODCOD from the MODCOD Index Number

Some DVB-S2 MODCODs are reported in iMonitor as an index number rather than a name.
Table 10 shows the MODCOD name for each MODCOD index number.
NOTE: The MODCOD Index Numbers (which start at 0) are not identical to the
MODCOD numbers used in the DVB-S2 standard as documented in the iDirect
Technical Reference Guide (which start at 1).
Table 10. DVB-S2 MODCOD Index Numbers
MODCOD Index Number
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
Customizing the Display with the Sparkline Context Menu

Several configurable settings affect how the Sparkline data is displayed on the MODCOD
Utilization Message Structure tab. To modify these settings, right-click a Sparkline to select
menu options in the context menu. (Figure 164). Each option is discussed in this section.
138
iMonitor User Guide

iDX Release 3.3
Figure 164. MODCOD Utilization Display: Context Menu

1. Select Mouse Tracking and then click and drag along the Sparkline to view the MODCOD
Index of each data point. In Figure 165, Mouse Tracking has been enabled and the mouse
is over a line representing a data point with MODCOD index of 12 (8PSK 2/3). See Table 10
on page 138 for the MODCOD index associated with each MODCOD.
Figure 165. Enabling Mouse Tracking for MODCOD Utilization

2. Select Out of Bound to open a dialog box (Figure 166) that differentiates between
MODCODs inside or outside a configured range.
Figure 166. MODCOD Utilization: Setting MODCOD Boundaries

In the dialog box, set a minimum MODCOD index (Min. Boundary) and a Maximum
MODCOD index (Max. Boundary). Then click OK.
Individual spark lines that represent MODCOD indexes that fall within these boundaries
are displayed in one color in the Sparkline column. Individual spark lines that are outside
the boundaries are displayed as a different color.
3. Select Size to open a dialog box (Figure 167) to configure the Width and Height of the
Sparklines.
iMonitor User Guide

iDX Release 3.3
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.
3.10.4 Monitoring the Signal-to-Noise Ratio of DVB-S2 Remotes

In an ACM network, each DVB-S2 remote periodically reports its current Signal-to-Noise Ratio
(SNR) to the protocol processor. Based on the remotes last-reported SNR, the protocol
processor determines the maximum MODCOD at which the remote can currently receive data.
When the protocol processor sends data to the line card destined for that remote, it tells the
line card the maximum MODCOD on which the line card can send the data.
Note that 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. Therefore,
the line card may choose to send the data to the remote at a MODCOD that is lower than its
maximum MODCOD to ensure that all targeted remotes can demodulate the outbound frame.
Note also that critical data such as timeplan messages are sent to all remotes at the lowest
MODCOD configured for the downstream carrier, regardless of the current maximum MODCOD
of the individual remotes.
140
iMonitor User Guide

iDX Release 3.3
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.
Figure 169. Selecting Remotes SNR Monitoring

3. Click OK to view the SNR Plot tab of the SNR Monitoring Display.
Figure 170. ACM SNR Monitoring: SNR Plot Tab

4. Right-click anywhere in the graph to change the display. See page 141 for more details.
5. To see the SNR data in a multicolumn list, click the List Data tab.
iMonitor User Guide

iDX Release 3.3
141
Figure 171. ACM SNR Monitoring: List Data Tab

In the table:
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
3.10.5 Viewing DVB-S2 Hub Line Card Debug Statistics

iMonitor displays detailed hub statistics for DVB-S2 traffic that is sent from the protocol
processor to the line card and then transmitted by the line card on the DVB-S2 outbound
carrier. These are real-time-only statistics collected by the line card and reported to iMonitor.
They are primarily intended to help the iDirect technical support personnel and engineers
perform detailed analysis of the outbound traffic. Therefore, some of the information
displayed in iMonitor may only be meaningful when working directly with iDirect to resolve a
question about DVB-S2 network performance.
To view the DVB-S2 line card statistics in iMonitor:
1. Right-click a DVB-S2 transmit line card in the iMonitor tree and select DVB-S2 StatsHW
Stats from the menu to display the DVB-S2 Hub Debug View (Figure 172).
142
iMonitor User Guide

iDX Release 3.3
Figure 172. DVB-S2 Hub Debug View

The Structure column in Figure 172 shows the following types of statistical data that can
be viewed on this screen:
UDP Rx High/Low indicates the number high and low priority UDP packets received by
the line card from the protocol processor. These packets contain the data for
transmission on the outbound carrier. Each UDP packet is subdivided into ACM
packets. Each ACM packet contains data that can be sent on a specific maximum
MODCOD.
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.
iMonitor User Guide

iDX Release 3.3
143
LEGS Tx Overhead indicates the number of LEGS overhead bytes transmitted at a

given MODCOD. LEGS (Lightweight Encapsulation for Generic Streams) is the low-level
scheme used by iDirect to encapsulate the generic stream on the DVB-S2 outbound
carrier.
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.
BB Frames Tx indicates the number of BB Frames transmitted at a given MODCOD. A

BB Frame is the basic framing structure of the standard DVB-S2 protocol. iDirect uses
short frames for ACM carriers and long frames for CCM carriers.
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.
Figure 173. Viewing Details of DVB-S2 Hub Debug Statistics
144
iMonitor User Guide

iDX Release 3.3
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.
Figure 175. Hub Debug Statistics: ACM Packets Rx Low Example

5. To reset the counters in the display to zeroes, click the Reset View button (Figure 176) at
the top right of the screen.
iMonitor User Guide

iDX Release 3.3
145
Connecting to Network Elements
Figure 176. Hub Debug Statistics: Resetting the Counters

Clicking Reset View clears all values and sparklines and begins accumulating data starting
with the next set of statistics received from the line card.
3.11 Connecting to Network Elements

The Connect option is available in the right-click menu of any of the following network
elements:
Protocol Processor
Blade
Line Card
Remote (also accessible from a remotes Probe dialog box)
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.
3.11.1 Examining IP Routing and HDLC Information on Remotes

The following IP Routing and HDLC information is available using remote terminal commands:
The IP routing table currently loaded on the remote
MAC and IP addresses for all remotes in the remotes inroute group.
To examine this data on a remote:

1. Right-click the remote in the iMonitor Tree and select Connect from the context menu.
2. When the terminal window opens, log on with Username: admin.
3. Enter the following commands to view the IP and HDLC information:
ip table displays the IP routing table on the remote. In the Flags column for any
remote IP address:
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.
ll hdlc shows the HDLC address of this remote.
iMonitor User Guide

iDX Release 3.3
These commands are illustrated in Figure 177.
Figure 177. Viewing IP Routing and HDLC Information from the Remote Command Line
iMonitor User Guide

iDX Release 3.3
147
148
iMonitor User Guide

iDX Release 3.3
4 Traffic Statistics and

Traffic Graphs
This chapter discusses the IP and Satellite Traffic graphs. It also describes the statistics on
which the various graphs are based.
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.
4.1.1 IP Traffic Statistics vs. Satellite Traffic Statistics

Bandwidth usage statistics are divided into two different displays in iMonitor, each
representing different classes of usage: over-the-air bytes (satellite traffic) and upstream LAN
bytes (IP traffic). These statistics differ due to features such as TCP acceleration which
eliminates the need to acknowledge TCP packets over the air and therefore reduces the
number of bytes that must be transmitted.
When the protocol processor accelerates TCP traffic on the downstream carrier, it sends
acknowledgements to the sending server at the time that it queues the traffic for
transmission to the remote. When the client receives and acknowledges the TCP traffic, the
remote does not send the acknowledgement over the satellite link since the protocol
processor has already sent the acknowledgement to the sender.
This technique allows TCP traffic to flow at line rate across the satellite, and it minimizes the
number of TCP ACKs that are transmitted over the air. Because of this, the amount of traffic
flowing upstream from the protocol processor (eth0 to the Internet) differs from the amount
of traffic flowing across the satellite link. A large TCP download, for example, can generate
significant traffic from the eth0 interface of the protocol processor, even though little of that
traffic is transmitted across the satellite.
NOTE: Since higher-layer protocols are transparent to L2oS, the IP traffic graph
and IP statistics only show NMS management traffic in Layer 2 networks.
Monitoring Layer 3 statistics for user traffic in a Layer 2 network must be
performed external to the iDirect system.
The IP Statistics display shows the traffic on the upstream side of protocol processor while
satellite statistics display shows the traffic on the tunnel side of the protocol processor. This
is illustrated in Figure 178.
iMonitor User Guide

iDX Release 3.3
149
To
Internet
Upstream Router
Protocol
Processor
IP Traffic Stats Collected Here
Tunnel Lan Segment
To Internet
Upstream Lan Segment
Traffic Statistics
To line cards, satellite, remotes
SAT Traffic Stats Collected Here
Figure 178. Collection Points for IP Usage Statistics

NOTE: Due to the different collection points for IP and satellite statistics, the IP
Statistics display may show more upstream traffic than is actually possible; i.e.,
greater than the channel rate or configured rate limit. This is normal and not a
cause for concern.
4.1.2 Traffic Statistics Collection Points

Figure 179 shows the collection points for satellite and IP statistics.
150
iMonitor User Guide

iDX Release 3.3
Traffic Graphs
To Internet
Mesh Traffic Stats Collected Here
Remote 1
Protocol
Processor
IP Traffic Stats Collected Here
Tunnel Lan Segment
Upstream Lan Segment
Upstream Router
Remote 2
Remote 3
SAT Traffic Stats Collected Here
Figure 179. Collection Points for Satellite and IP Statistics
4.2
Traffic Graphs
This section contains the step-by-step procedures for viewing the following displays in
iMonitor:
Satellite Traffic Graph
IP Traffic Graph and Grouped RemotesIP Traffic Graph
4.2.1 SAT Traffic Graph

The SAT Traffic Graph can be selected from the following elements in the iMonitor tree:
Networks
Inroute groups
Remotes
To view the satellite traffic graph, follow the directions below:

1. Right-click a network, an inroute group or a remote.
2. Select SAT Traffic Graph from the menu to open the Select Items dialog box. Only
Remotes can be selected in the dialog box.
iMonitor User Guide

iDX Release 3.3
151
Traffic Graphs

3. Select the remotes to view in the graph.
NOTE: For historical or get past data, the granularity of the statistics depends on
the start time selected. Less granularity is available for older statistics due to
archive consolidation. See Optimization of the Statistics Archive on page 171.
6. Click OK to view the SAT Traffic tab of the SAT Traffic display.
152
iMonitor User Guide

iDX Release 3.3
Traffic Graphs
Figure 181. SAT Traffic: SAT Traffic Tab

The SAT Traffic display has three tabs: SAT Traffic (Figure 181), SAT Downstream
(Figure 182), and SAT Upstream. The SAT Upstream tab has the same format as the SAT
Downstream tab, but displays upstream rather than downstream statistics.
NOTE: The SAT Bandwidth Usage display shows the total Kbps traffic in both
directions for selected remotes. See Satellite Bandwidth Usage on page 161.
iMonitor User Guide

iDX Release 3.3
153
Traffic Graphs
Figure 182. SAT Traffic: SAT Downstream Tab

7. Change the graphical display on the SAT Traffic tab by toggling the buttons to the left of
the graphs (Figure 181). The buttons work as follows:
The U and D buttons toggle on and off the Upstream and Downstream graphs. Click
these buttons to display one or both graphs.
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
iMonitor User Guide

iDX Release 3.3
Traffic Graphs
Figure 183. SAT Traffic Options Menu

The menu options include:
Select Show Legend to display a color-coded legend of the graph contents.
Select Show Parameters to open a statistics options section at the top of the pane
(Figure 184). These selections are described on page 154.
Figure 184. Statistics Graphs Show Parameters Section
Select Scroll Lock to lock the upstream and downstream scroll bars together for historical
statistics.
Select Direction to view upstream traffic, downstream traffic, or both.
Select Units to switch between kilobits per second and kilobytes per second.
Select Interval to switch among the following:

Seconds (3 minutes total)
Minutes (1 hour total, averaged over 1 minute)
Hours (12 hours total, averaged over 10 minutes)
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.
Select Properties to modify the default color settings.
iMonitor User Guide

iDX Release 3.3
155
Traffic Graphs
4.2.2 IP Traffic Graph

The IP Traffic Graph can be selected from the following elements in the iMonitor tree:
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.

3. In the Remotes area of the dialog box, select the remotes to view in the graph.
6. Click OK to open the IP Traffic Graph (Figure 186).
156
iMonitor User Guide

iDX Release 3.3
Traffic Graphs
Figure 186. IP Traffic Graphs

7. Click the Upstream Data or Downstream Data tabs to view the statistics used to create
the graphs.
Figure 187. IP Traffic: Downstream and Upstream Data
iMonitor User Guide

iDX Release 3.3
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.
Figure 188. IP Traffic Graph: Context Menu

10. When viewing Grouped RemotesIP Traffic Graph, all selected remotes are shown at
the left of the display (Figure 189). Select or clear the check boxes to show or hide the
traffic of individual remotes. The top image in Figure 189 shows the traffic graph for two
remotes. The bottom image shows the same graph for a single remote.
158
iMonitor User Guide

iDX Release 3.3
Traffic Graphs
Figure 189. Selecting Remotes for Grouped Remotes IP Traffic Graph

NOTE: When viewing multiple remotes on the same graph, select Legend from the
right-click menu to determine which remote is represented by each line color.
11. When viewing Grouped RemotesIP Traffic Graph, click the Filter button (Figure 189)
to open the Select Remotes dialog box (Figure 190).
Figure 190. Selecting Remotes for the Main Display

12. Use the Select Remotes dialog box to change the list of remotes on the left side of the
display (Figure 189). Click the arrow buttons to move remotes between the Selected
iMonitor User Guide

iDX Release 3.3
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.
Figure 191. IP Traffic Graph: Sorting Remotes by Traffic Volume

In the Sort Remotes By dialog box, sort the order that the remotes appear in the Name
column by traffic volume as follows:
a. Select the Direction (Upstream or Downstream).
b. Select a Traffic type, or select Totals to sort by total traffic.
c. Select All Buffered Data to sort the remotes based on the traffic volume in all the
statistics in the time interval; or select Last Data Point to sort the remotes based on
the amount of traffic in the last statistics record received for each remote.
14. To choose among various display options on the IP Traffic Graph, right-click inside the
window to view the menu below.
160
iMonitor User Guide

iDX Release 3.3
Satellite Bandwidth Usage
Figure 192. IP Statistics Options Menu

The menu options are described below. Some of these options perform the same functions as
the buttons on the left side of the display. (See Figure 186.)
4.3
Select Select Graph to view the Upstream and/or Downstream graph.
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 Legend to display a color-coded legend of the graph contents.
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.
Select Manual Refresh to refresh the display immediately.

The Satellite Bandwidth Usage display shows the total upstream and downstream IP and
Satellite traffic in Kbps for individual remotes. Only real-time information is displayed.
The Bandwidth Usage display can be selected from the following elements in the iMonitor
tree:
Networks
Inroute Groups
To view the bandwidth usage:

1. Right-click a network or inroute group.
iMonitor User Guide

iDX Release 3.3
161
2. Click SAT Bandwidth Usage to open the Select Remotes dialog box,

3. Select the remotes to view. Then click OK. to open the SAT Bandwidth Usage results
display (Figure 194).
Figure 194. Real-time SAT Bandwidth Usage Display

4. Click any column heading to sort the data on that field in ascending order or descending
order.
162
iMonitor User Guide

iDX Release 3.3
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
SAT Long Term Bandwidth Usage
IP Long Term Bandwidth Usage
Remote Availability
Line Card Availability
Long Term Bandwidth Usage Reports

Long-term bandwidth usage reports show bandwidth usage for IP and satellite traffic. The
Average Tab of the SAT Long Term Bandwidth Usage report also displays a percent-of-maxcapacity figure which quantifies unused bandwidth margin on both the upstream and
downstream channels. Long-term bandwidth usage reports include all remotes below the
selected element in the iMonitor Tree.
5.1.1 Generating Long Term Bandwidth Usage Reports

To generate a Long Term Bandwidth Usage report:
1. Right-click a network, inroute group, or remote.
2. Select IP Long Term Bandwidth Usage or SAT Long Term Bandwidth Usage to open the
Long Term Bandwidth Usage Parameters dialog box.
iMonitor User Guide

iDX Release 3.3
163
Figure 195. Selecting Long Term Bandwidth Usage Parameters

3. In Remote Devices, select the remotes for the report.
4. Select Total All Remotes to sum the values for all of the selected remotes. Clear this
check box to report on each remote individually.
5. In Direction, select Downstream, Upstream, or Both to report on downstream bandwidth
usage, upstream bandwidth usage, or usage in both directions.
6. In IP Type or OTA Type, select one or more protocol for the report, or select None to
report only on total traffic. Select All to select all of the available IP protocols. This
results in a list of the individual values for each protocol.
7. Select Total Traffic to sum the columns of IP traffic in a Grand Total.
164
iMonitor User Guide

iDX Release 3.3
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.
iMonitor User Guide

iDX Release 3.3
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
iMonitor User Guide

iDX Release 3.3
Figure 197. IP 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.
5.1.3 Interpreting Long Term Bandwidth Usage Reports

In addition to the Kbps values, the Average tab of the SAT Long Term Bandwidth Usage report
contains the percentage of the maximum channel capacity of the upstream and downstream
channels for the interval chosen.
Figure 198. SAT Long Term Bandwidth Usage Report: Average Tab
iMonitor User Guide

iDX Release 3.3
167
Remote and Line Card Availability Reports
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

The Remote Availability report and Line Card Availability report show the amount of time one
or more remotes or line cards were active in the network and able to transmit and receive IP
traffic. Each of these reports also includes a count of the number of times a remote or line
card was out of the network during the reporting period.
These reports are available from the following levels of the iMonitor Tree:
Network
Inroute Groups
Remotes (Remote Availability only)
Line Cards (Line Card Availability only)
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
iMonitor User Guide

iDX Release 3.3

2. Select the remotes for the report.
3. Select a time range for the report.
4. Click OK to view the Remote Availability report.
Figure 200. Remote Availability Report

A sample report is shown in Figure 200. In the report, Up means the time the remote was able
to pass traffic. Down means the time the remote was unable to pass traffic due to a Layer 2
and/or Layer 3 Alarm.
For each remote, the report displays:
The percentage of the time range the remote was up
The percentage of the time range the remote was down
iMonitor User Guide

iDX Release 3.3
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
iMonitor User Guide

iDX Release 3.3
Appendix A Accessing the

NMS Statistics Archive
Many iDirect customers have requested specific reports on various aspects of network
behavior, ranging from IP traffic activity to system uptime to satellite link behavior. iMonitor
allows users to retrieve historical data and populate a number of tabular and graphical
displays. iMonitor also provides long-term bandwidth usage statistics for network usage
profiling.
iDirect also provides support for read-only direct archive access. This appendix explains how
to access the statistics archive and defines specific tables in the archive database.
NOTE: This appendix is intended for technical personnel with experience
developing relational database applications, preferably using ODBC. The statistics
tables in this appendix may also be useful to network operators who want to
understand what statistics are logged at the NMS and the associated fields
displayed on the various iMonitor screens.
A.1
Optimization of the Statistics Archive

The NMS uses the techniques described in this section in order to store the archive data
efficiently and to minimize data retrieval time.
A.1.1 Optimized NMS Statistics Archive Storage

In order to efficiently store the data, the statistics archive eliminates or consolidates certain
records according to the following rules:
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.
iMonitor User Guide

iDX Release 3.3
171
NMS Database Overview
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.1.2 Optimized NMS Statistics Archive Lookup

Large historical requests are divided into multiple segments that are processed separately.
This results in better memory utilization on the server and improved response time in the GUI.
A.1.3 Archive Consolidation

To prevent filling up the NMS servers hard disk, a consolidation process runs every night at
approximately midnight by default. Using rules defined in the configuration database, this
process examines all tables in the archive database and either deletes old records or
combines multiple records into a single record.
Consolidation rules govern how long data is saved. The default consolidation rules are
designed to allow networks to grow large (many hundreds of remotes) without disk space
problems. To modify the default values, contact iDirects Technical Assistance Center (TAC) at
(703) 648-8151 for assistance. The default consolidation values for each table are listed in
Table 11 on page 175.
A.2
NMS Database Overview

A.2.1 Connecting to the NMS Archive Database with ODBC
All statistical archive information is contained in a MySQL relational database on the primary
NMS server machine. MySQL is an open source database server commonly used on Linux
servers. There are many books available on MySQL and there is a wealth of information at
http://www.mysql.com.
A.2.2 Obtaining the ODBC Connection Library

MySQL supports access using the Microsoft standard Open DataBase Connectivity (ODBC). The
installation of MySQL on an NMS server already contains support for ODBC connections.
Therefore, there is nothing to download from the Internet to enable ODBC access on the NMS
server. However, the appropriate ODBC client library must be download from the MySQL Web
site. Full details, including an installation and usage manual, are available at
http://www.mysql.com.
A.2.3 Setting up a Simple ODBC Access Account

Access with ODBC is not secure. Therefore, a specific read-only MySQL account must be set up
to restrict access only to the information required to generate reports. The details of this user
account are typically specific to each customer installation. However, general instructions are
included here for setting up a generic read-only account.
172
iMonitor User Guide

iDX Release 3.3
Basic Archive Database Information
1. Log on to the NMS server as root.

2. Enter the MySQL database utility:
mysql
3. At the mysql prompt, type the following command:
mysql> grant SELECT on *.* to <user>@% identified by <password>;
Where <user> is the user name of the account and <password> is the account
password. Note that the double quotes around password and single quotes around the
percent sign are required.
4. Activate the account:
mysql> flush privileges;
5. Exit the MySQL utility:
mysql> quit;
The user created by this procedure has the following privileges:
Ability to connect from any host
Ability to read all databases
Read-only access to the databases (no write access)
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

This section provides a general description of the Archive Database.
A.3.1 Types of NMS Databases and Supported Access

The NMS stores its information in two separate databases. The configuration database
contains all the configuration information defined in iBuilder: remotes, hub line cards,
carriers, etc. The archive database contains all the real-time statistical information
generated by iDirect networks: IP statistics, remote status, conditions, etc.
iDirect supports read-only access to the archive database only. The configuration database
contains a number of intricate relationships among tables that require detailed knowledge of
the structure to interpret. This structure changes from one release to another to allow
configuration of new features.
iMonitor User Guide

iDX Release 3.3
173
A.3.2 Database Structure Changes between Releases

The structure of the archive database changes from release to release. In most new iDirect
releases, new fields are added to existing tables and new tables are added to the database.
These changes may affect customer-created reports. Therefore, such reports may require
ongoing maintenance. This appendix documents the archive database tables for this release
only. iDirect is not responsible for customer reports that no longer work after an upgrade due
to database structure changes.
A.3.3 Accessing Remote and Network Names from Configuration

Database
There are two exceptions to the restriction on accessing the configuration database: retrieval
of remote names and network names. Entries in the archive database are keyed to individual
remotes by a unique database ID, and do not contain the name assigned to the remote in
iBuilder. To retrieve the remotes name, it is necessary to reference the appropriate table in
the configuration database with the unique ID.
NOTE: Retrieving information based on serial number is not recommended.
Access to historical data will be lost if the hardware is replaced in the field.
In the archive database, remote unique ids in all tables are stored in the column named
unique_id. In the configuration database, this same ID is stored in a table named NetModem
in the column NetModemId. The remote name is in the column named NetModemName.
A sample SQL query that retrieves the remote name from a known remote ID is:
select NetModemName from nms.NetModem where NetModemId = 15;
The configuration database name is nms. That name must be in the query to tell the MySQL
server which database to look in.
In the archive database, network IDs in all tables are stored in the column named
network_id. In the configuration database, this same ID is stored in a table named Network
in the column named NetworkId. The network name is in the column named NetworkName.
A sample SQL query that retrieves a remotes network name from a known network ID is:
select NetworkName from nms.Network where NetworkId = 1;
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.
A.3.5 Overview of the Archive Database Tables

Table 11 lists the archive database table names; the contents of each table; and the time
period for which the data is saved. Each table is described in detail later in this appendix.
174
iMonitor User Guide

iDX Release 3.3
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
IP stats sent from the protocol processor
24 hours
ip_minute_stats
raw IP stats consolidated to one record per minute
30 days
ip_hour_stats
IP minute stats consolidated to one record per hour
6 months
lat_stats
latency measurement
1 week
nms_hub_stats
hub line card statistics
1 week
nms_remote_status
remote information
1 week
nms_ucp_info
uplink control adjustments
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
protocol processor state changes
30 days
chassis_state_change_log
chassis state changes
30 days
raw_ota_stats
over-the-air stats sent from the protocol processor
24 hours
ota_minute_stats
raw ota stats consolidated to one record per minute
30 days
ota_hour_stats
ota minute stats consolidated to one record per hour
6 months
raw_otacast_stats
over-the-air multicast stats sent from the protocol processor
24 hours
otacast_minute_stats
raw otacast stats consolidated to one record per minute
30 days
otacast_hour_stats
otacast minute stats consolidated to one record per hour
6 months
raw_mesh_stats
mesh stats sent from the remote
24 hours
mesh_minute_stats
raw mesh stats consolidated to one record per minute
30 days
mesh_hour_stats
mesh minute stats consolidated to one record per hour
6 months
remote_dvbs2_stats
DVB-S2 statistics per remote
30 days
hub_dvbs2_stats
DVB-S2 statistics per line card
30 days
pp_dvbs2_stats
DVB-S2 statistics per protocol processor blade
30 days
nms_group_qos_stats
group-level GQoS statistics
30 days
nms_sl_qos_stats
service level GQoS statistics
30 days
group_qos_hour_stats
group-level qos stats consolidated to one record per hour
6 months
group_qos_minute_stats
group-level qos stats consolidated to one record per minute
30 days
rev_activity
revserver log per network upgrade
Unlimited
iMonitor User Guide

iDX Release 3.3
175
Table 11. Archive Database Tables (continued)

Base Table Name
Data
Saved For
Contains
rev_state
revserver log per remote per network upgrade
Unlimited
sl_qos_hour_stats
service-level qos stats consolidated to one record per hour
6 months
sl_qos_minute_stats
service-level qos stats consolidated to one record per minute
30 days
nms_inroutes
channel-specific hub line card stats for multichannel line cards
1 week
raw_scpc_rmtrx_stats
SCPC return channel stats per remote
24 hours
scpc_rmtrx_hour_stats
SCPC return channel stats consolidated to one record per hour
30 days
scpc_rmtrx_minute_stats
SCPC return channel stats consolidated to one record per minute
6 months
raw_tdma_rmtrx_stats
TDMA return channel stats per remote
24 hours
tdma_rmtrx_hour_stats
TDMA return channel stats consolidated to one record per hour
30 days
tdma_rmtrx_minute_stats
TDMA return channel stats consolidated to one record per minute
6 months
inroute_composit_stats
Inroute Group Composition (IGC) stats per inroute group
1 week
composit_minute_stats
IGC stats consolidated to one record per minute
30 days
composit_hour_stats
IGC stats consolidated to one record per hour
6 months
inroute_slot_usage_stats
inroute slot usage stats per inroute group
1 week
slot_usage_minute_stats
inroute slot usage stats consolidated to one record per minute
30 days
slot_usage_hour_stats
inroute slot usage stats consolidated to one record per hour
6 months
remote_power_stats
remote power stats
1 week
remote_power_minute_stats
remote power stats consolidated to one record per minute
30 days
remote_power_hour_stats
remote power stats consolidated to one record per hour
6 months
176
iMonitor User Guide

iDX Release 3.3
Database Table Details
A.4

The following sections describe each of the archive tables in some detail. For further
information, please contact the iDirect Technical Assistance Center (TAC).
A.4.1 Consolidated Statistics Tables

Several types of statistics are consolidated by the NMS:
IP statistics
Over-the-air statistics
Over-the-air multicast statistics
Mesh statistics
Group QoS statistics
Service Level QoS statistics
Remote TDMA return channel statistics
Remote SCPC return channel statistics
Inroute Group Composition statistics
Inroute slot usage statistics
Remote power 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.
A.4.2 IP Statistics Tables

As shown in Table 11, there are three base table types for IP statistics, each containing
records that cover a particular period of time. The raw IP statistics are consolidated into
minute and hour IP statistics. The ip_minute_stats table and ip_hour_stats table contain the
same fields as the raw_ip_stats table.
IP statistics for all active remotes are calculated on the protocol processor and sent to the
NMS every five seconds. After sending a statistics message, the protocol processor zeros its
iMonitor User Guide

iDX Release 3.3
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)
time_t that the message arrived at the NMS server
t_interval
int(10) unsigned
interval in seconds that the data covers
network_id
smallint(5) unsigned
identifies the network
unique_id
int(10) unsigned
unique identifier for the remote
modem_sn
remotes serial number
rx_tcp_kbyte
double
kilobytes of TCP data received from the remote (upstream)
tx_tcp_kbyte
double
kilobytes of TCP data sent to the remote (downstream)
rx_udp_byte
double
kilobytes of UDP data received from the remote
tx_udp_kbyte
double
kilobytes of UDP data sent to the remote
rx_icmp_kbyte
double
kilobytes of ICMP data received from the remote
tx_icmp_kbyte
double
kilobytes of ICMP data sent to the remote
rx_igmp_kbyte
double
kilobytes of IGMPdata received from the remote
tx_igmp_kbyte
double
kilobytes of IGMP data sent to the remote
rx_http_kbyte
double
kilobytes of HTTP data received from the remote.
tx_http_kbyte
double
kilobytes of HTTP data sent to the remote
rx_other_kbyte
double
kilobytes of data from other protocol types received from

the remote.
tx_other_kbyte
double
kilobytes of data from other protocol types sent to the

remote
A.4.3 Latency Measurements

The lat_stats table contains latency measurement results for all active remotes in the
network. To generate latency information, the NMS latsvr process sends ICMP echo requests to
all active remotes every five seconds and measures the round trip time. Queries for individual
remotes are offset in time to prevent a burst of messages every five seconds. For remotes
that are out-of-network, the round trip time is -1 or -100. Table 13 shows the contents of the
lat_stats table.
178
iMonitor User Guide

iDX Release 3.3
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)
time_t the round trip time was calculated
network_id
unique_id
int(10) unsigned
modem_sn
int(10) unsigned
rtt
double
the measured round trip time in milliseconds

(-1 or -100 if remote is out-of-network)
ip_addr
varchar(20)
IP address that was queried (management IP

address of the remote)
state
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.
A.4.4 Hub Line Card Statistics and Upstream Channel Statistics

All hub line cards in steady state send a statistics message to the NMS every 20 seconds. This
message serves two purposes: the absence of the message causes an alarm to be raised in
iMonitor, and it contains useful information about the last 20 seconds of hub line card activity.
The data values in each message represent deltas from the previous message. Table 14 shows
the contents of the nms_hub_stats table.
Table 14. nms_hub_stats Table Format
Column Name
Data Type
Meaning
timestamp
timestamp(14)
time_t that the message arrived at the NMS

server
network_id
unique_id
int(10) unsigned
identifies the hub line card
modem_sn
int(10) unsigned
hub line cards DID (not the serial number)
scpc_num_tx_attempts
int(10) unsigned
number of downstream transmit attempts
scpc_num_tx_bytes
int(10) unsigned
number of downstream bytes transmitted
scpc_num_tx_errors
int(10) unsigned
number downstream transmit errors
acq_crc_errors
int(10) unsigned
number of acquisition CRC errors
traffic_crc_errors
int(10) unsigned
number of traffic CRC errors
iMonitor User Guide

iDX Release 3.3
179
Table 14. nms_hub_stats Table Format (continued)

Column Name
Data Type
Meaning
bursts_detected
int(10) unsigned
number of TDMA bursts detected at this hub
bytes_rxed
int(10) unsigned
number of TDMA bytes received at this hub
rx_overflow_frames
int(10) unsigned
number of times the DMA was reset due to an

overflow condition
rx_composite_power
double
output of the receive power detector converted

to dBm.
rx_tunnel_errors
int(10) unsigned
number of receive tunnel errors.
tx_tunnel_errors
int(10) unsigned
number of transmit tunnel errors.
rx_digital_gain
receive digital gain at the hub
scpc_snr_cal
double
calibrated SNR value of the loopback

downstream carrier
scpc_sym_offset
int(11)
downstream loopback symbol offset.
scpc_freq_offset
int(11)
downstream loopback frequency offset.
scpc_frame_lock_status
tinyint(4)
downstream loopback lock status (locked,

unlocked)
lostlock_count
int(10) unsigned
number of times DVB-S2 NCR lock was lost
fll_dac
int(10) unsigned
current value of the frequency locked loop

digital to analog converter
flags
int(10) unsigned
health of GIGE port on evolution line card. 1: up;

0: down
m_time_ticks
int(10) unsigned
line card counter value
m_temp
double
line card temperature
m_tx_power
double
line card transmit power
rx_ddc_agc_dac_data
int(10) unsigned
dual downconverter AGC
buffer_overflow
int(10) unsigned
buffer overflow data for debugging
fe_agc_dac_val
int(10) unsigned
front-end digital measurement of rx power

derived from the composite power
gige_tx_errors
int(10) unsigned
transmit errors on the GIGE port
gige_rx_errors
int(10) unsigned
receive errors on the GIGE port
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
iMonitor User Guide

iDX Release 3.3
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)

server
network_id
unique_id
int(10) unsigned
identifier for the hub line card
hlc_did
int(10) unsigned
unique identifier for the hub line card
inroute_type
int(10) unsigned
SCPC return (1) or TDMA (2)
inroute_id
int(10) unsigned
inroute id of this TDMA or SCPC channel
digital_rx_gain
int(10) unsigned
not used (see rx_digital_gain field)
rx_cof
int(10) unsigned
carrier frequency offset (SCPC return only)
tdm_lock_status
int(10) unsigned
locked or unlocked (SCPC return only)
tdm_lost_lock_counter
int(10) unsigned
number of times SCPC return frame lock was lost
acq_errors
int(10) unsigned
number of acquisition errors (TDMA only)
traffic_crc_errors
int(10) unsigned
number of traffic CRC errors
bursts_detected
int(10) unsigned
number of bursts detected (TDMA only)
bytes_rxed
int(10) unsigned
number of bytes received
rx_digital_gain
int(10) unsigned
receive digital gain at the hub
A.4.5 Remote Return Channel Statistics

The protocol processor collects return channel statistics per remote for both TDMA and SCPC
upstream channels. Return channel statistics for all active remotes are calculated on the
protocol processor and sent to the NMS every five seconds. After sending a statistics message,
the protocol processor zeros its counts, so that every database record contains the delta in
activity from the previous record. 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.
As shown in Table 11, there are two separate table types for remote return channel statistics.
The raw_tdma_rmtrx_stats table (Table 16) contains TDMA upstream statistics per remote.
The raw_scpc_rmtrx_stats table (Table 17) contains SCPC upstream statistics per remote.
In addition, the TDMA and SCPC return channel statistics are consolidated into minute and
hour return channel statistics. The tdma_rmtrx_minute_stats table and
iMonitor User Guide

iDX Release 3.3
181
tdma_rmtrx_hour_stats table contain the same fields as the raw_tdma_rmtrx_stats table

(Table 16). The scpc_rmtrx_minute_stats table and scpc_rmtrx_hour_stats table contain the
same fields as the raw_scpc_rmtrx_stats table (Table 17).
Table 16. raw_tdma_rmtrx_stats Record Format
Column Name
Data Type
Meaning
timestamp
timestamp(14)
t_interval
int(10) unsigned
network_id
remote_id
int(10) unsigned
the remote ID assigned by iBuider
remote_did
int(10) unsigned
acq_bursts
int(10) unsigned
number of acquisition bursts received
acq_crc
int(10) unsigned
number of crc errors in acquisition bursts
acq_mismatch
int(10) unsigned
number of acquisition bursts received from

unexpected remote id
acq_missing
int(10) unsigned
number of allocated aquisition slots for which no

acquisition burst was received
data_bursts
int(10) unsigned
number of traffic bursts received
data_crc
int(10) unsigned
number of crc errors in traffic bursts
data_mismatch
int(10) unsigned
number of traffic bursts received from unexpected

remote id
data_missing
int(10) unsigned
number of allocated traffic slots for which no burst

was received
keepalive
int(10) unsigned
number of keepalive bursts received at the hub
Table 17. raw_scpc_rmtrx_stats Record Format

Column Name
182
Data Type
Meaning
timestamp
timestamp(14)
t_interval
int(10) unsigned
network_id
remote_id
int(10) unsigned
the remote ID assigned by iBuilder
remote_did
int(10) unsigned
data_packets
int(10) unsigned
number of IP packets received
data_hdlc_error
int(10) unsigned
number of octet and crc errors received
data_mismatch
int(10) unsigned
number of data packets received from unexpected

remote id
keepalive
int(10) unsigned
number of keepalive packets received at the hub
iMonitor User Guide

iDX Release 3.3
A.4.6 Remote Status

Remotes in steady state send a status message to the NMS every 20 seconds. This message is
sent as a UDP datagram, so there is no guarantee that every message sent will be received.
However, built-in QoS rules give it higher priority than other traffic, and these messages are
rarely dropped. The message contains status of information about the remote, including
temperature, number of milliseconds since last boot-up, downstream SNR, etc. Table 18
shows the contents of the remote status message.
Table 18. nms_remote_status Record Format
Column Name
Data Type
Meaning
timestamp
timestamp(14)
network_id
unique_id
int(10) unsigned
modem_sn
int(10) unsigned
time_tics
bigint(20) unsigned
number of milliseconds since last boot-up
snr_cal
double
calibrated SNR value of the downstream carrier
rx_power
double
output of the receive power detector converted to dBm
power_in_dbm
double
current transmit power in dBm
temperature_celcius
double
current temperature measured on the board (not

ambient temp)
digital_rx_power
double
derived from the digital gain setting in the demodulator,

converted to dBm
lostlock_count
int(10) unsigned
number of times that the remote has lost lock on the

downstream carrier since the remote restarted
fll_dac
int(10) unsigned
current value of the frequency locked loop digital to

analog converter
buc_48v
int(10) unsigned
24 Volt BUC (0) or 48 Volt BUC (1) (X7 only)
rmtflags
int(10) unsigned
boolean flag field; contact iDirects TAC for latest

definition
rx_cof
int(11)
carrier offset frequency; difference, in Hz, of the

incoming frequency and the receivers reference
frequency
scpc_rx_errors
int(10) unsigned
number of downstream receive errors since last reboot
tdma_snr_cal
double
calibrated SNR value of the upstream carrier
tdma_sym_offset
smallint(6)
TDMA symbol offset
tdma_freq_offset
int(11)
TDMA frequency offset
tdma_crc_errors
int(10) unsigned
number of tdma crc errors during the last interval
rx_reliable_byte
int(10) unsigned
reliable (e.g. TCP) bytes received by the remote
tx_reliable_byte
int(10) unsigned
reliable (e.g. TCP) bytes sent by the remote
rx_unreliable_byte
int(10) unsigned
unreliable (e.g. UDP) bytes received by the remote
iMonitor User Guide

iDX Release 3.3
183
Table 18. nms_remote_status Record Format (continued)

Column Name
Data Type
Meaning
tx_unreliable_byte
int(10) unsigned
unreliable (e.g. UDP) bytes sent by the remote
rx_oob_byte
int(10) unsigned
out-of-band bytes received by the remote
tx_oob_byte
int(10) unsigned
out-of-band bytes sent by the remote over TDMA inroute
local_fo_correction
int(11)
delta between oscillator and receivers reference clock
lost_pl_lock_count
int(10) unsigned
Number of physical layer frame sync lost since restart
fast_fade_correction
int(10) unsigned
Number of fast fade corrections
dvb_s2_crc8_error
int(10) unsigned
Number of CRC8 errors
dvb_s2_crc32_error
int(10) unsigned
Number of CRC32 errors
dvb_s2_raw_agc
int(10) unsigned
Digital AGC gain applied by demodulator
m_tuner_agc_gain
int(10) unsigned
RF AGC gain applied by unlocked tuner
clock_delta_count
int(10) unsigned
clock delta count for DVB-S2 remotes
scpc_rtn_tx_oob_byte
int(10) unsigned
out-of-band bytes sent by the remote over SCPC return
A.4.7 Uplink Control Adjustments

The protocol processor sends uplink control adjustment messages to each in-network remote
periodically. The message is also sent into the NMS for archiving. The timing of each message
is offset, so timestamps typically vary from remote to remote. This message contains
adjustment values for power, frequency, and timing offset to account for a variety of
conditions: satellite drift, weather conditions at the hub or remote, and remote transmit
equipment inaccuracies. The format of the nms_ucp_info table is shown in Table 19.
Table 19. nms_ucp_info Record Format
Column Name
Meaning
timestamp
timestamp(14)
network_id
unique_id
int(10) unsigned
modem_sn
int(10) unsigned
sym_offset
int(11)
timing offset in symbols; the remote applies this offset

to its current frame start delay value
power_adjustment
int(11)
power offset in dBm; the remote adjusts its transmit

power by this value
freq_offset
int(11)
frequency offset; the remote adjusts it current transmit

frequency by this value
snr_cal
double
the current SNR of the remotes transmit signal as

perceived at the hub
scpc_snr_cal
184
Data Type
double
the current SNR of the hub downstream loopback

transmit signal as perceived at the hub
iMonitor User Guide

iDX Release 3.3
A.4.8 Event Messages

All protocol processors, hub line cards, and remotes send in event messages to record certain
situations that arise during operations. Some events cause conditions to be raised in iMonitor
and others are for informational purposes only. Event messages are not sent at regular time
intervals, nor do they follow a specific text format. The format of the event_msg table is
shown in Table 20.
Table 20. event_msg Record Format
Column Name
Data Type
Meaning
timestamp
timestamp(14)
time_t that the message arrived at the NMS server.
event_level
int(11)
a number signifying the severity level of the message. This

field deprecated.
event_class
int(11)
a number signifying the portion of the system that

generated the event. This field is deprecated.
unique_id
int(10) unsigned
unique identifier for the remote or hub line card (0 for

protocol processor events)
modem_sn
int(10) unsigned
the remotes or line cards serial number (0 for protocol

processor events)
time_tics
bigint(20) unsigned
for remotes and line cards, the number of milliseconds since

boot-up; for protocol processors, time_t in milliseconds of
the machine
msg
varchar(255)
free-form event message text
A.4.9 Hub and Remote State Changes

During everyday system operation, situations occasionally arise that require operator
attention, or at least operator notification. These situations are called conditions, and are
associated with a change in the operational state of the network element in question.
Examples of conditions include temperature warnings, SNR below limit warnings, and out-ofnetwork alarms.
All conditions and changes of state are recorded in the archive database. For hub line cards
and remote units, these conditions are recorded in the archive table state_change_log. The
format of this table is shown in Table 21.
Table 21. state_change_log Record Format
Column Name
Data Type
Meaning
timestamp
timestamp(14)
time_t that the condition was raised or cleared
unique_id
int(10) unsigned
unique identifier for the remote or hub line card
modem_sn
int(10) unsigned
remotes or line cards serial number
iMonitor User Guide

iDX Release 3.3
185
Table 21. state_change_log Record Format (continued)

Column Name
current_state
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)
time_t of original condition in the case of multiple

simultaneous conditions
error_type
smallint(6)
Translates to an enumerated condition type; contact iDirect

for values for this release.
error_severity
enum
severity of the condition; values are:
EVTWarning
EVTAlarm
EVTCleared
EVTOffline
EVTElsewhere
EVTMeshAlarm
EVTSleep
EVTNone
NOTE: MySQL enumeration types are 1-based, not 0-based.
reason
varchar(255)
text explanation of the condition
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
iMonitor User Guide

iDX Release 3.3
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.
A.4.10 Protocol Processor State Changes

Protocol processor state changes are stored in the pp_state_change_log table of the statistics
database. The state is set to OK when the event server is receiving heartbeat events from the
protocol processor. The state changes to ALARM when the heartbeat fails to arrive for two
successive timeout periods. Whenever the event server process restarts, it sets the state of
each protocol processor to UNKNOWN until it receives a heartbeat from that protocol
processor.
The format of the pp_state_change_log table is shown in Table 22.
Table 22. pp_state_change_log Record Format
Column Name
Data Type
Meaning
timestamp
timestamp(14)
time_t that this condition was raised or cleared
pp_id
int(10) unsigned
unique identifier for the protocol processor
blade_id
int(10)unsigned
identifies the protocol processor blade
current_state
enum
current state of the protocol processor after this

condition is processed; values are:
OK
WARNING
ALARM
UNKNOWN
OFFLINE
STATE_NONE
Currently, only OK, ALARM, and UNKNOWN are
raised for protocol processors.
occurred_at
iMonitor User Guide

iDX Release 3.3
timestamp(14)
time_t the condition was first raised in case of

multiple simultaneous conditions
187
Table 22. pp_state_change_log Record Format (continued)

Column Name
error_severity
Data Type
enum
reason
Meaning
severity of the condition; values are
varchar(255)
EVTWarning
EVTAlarm
EVTCleared
EVTOffline
EVTNone
text explanation of the condition
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.
A.4.11 Hub Chassis State Changes

Hub chassis state changes are stored in the chassis_state_change_log table. Chassis warnings
are raised for power and fan alarms from the chassis. The event server and iMonitor treat
these alarms as warnings, since service is not interrupted and immediate action is not
absolutely necessary. The ALARM condition is raised only when the event server loses contact
with the hub chassis. In that case, service may still not be interrupted, since the event server
communicates with an independent MIDAS or EDAS controller board on the chassis.
Chassis state changes are stored in the chassis_state_change_log table. The format of this
table is shown in Table 23.
Table 23. chassis_state_change_log Record Format
Column Name
Meaning
timestamp
timestamp(14)
time_t that this condition was raised or cleared
chassis_id
int(10) unsigned
unique identifier for the chassis
current_state
enum
current state of the chassis after this condition is processed;

values are:
occurred_at
188
Data Type
timestamp(14)
OK
WARNING
ALARM
UNKNOWN
OFFLINE
STATE_NONE
time_t this condition was first raised in the case of multiple

simultaneous conditions.
iMonitor User Guide

iDX Release 3.3
Table 23. chassis_state_change_log Record Format (continued)

Column Name
error_severity
reason
Data Type
enum
Meaning
severity of this condition; values are:
varchar(255)
EVTWarning
EVTAlarm
EVTCleared
EVTOffline
EVTNone
text explanation of this condition
A.4.12 Over-the-Air Statistics Tables

As shown in Table 11, there are three separate base table types for over-the-air statistics,
each one containing records that cover a particular period of time. The raw over-the-air
statistics are consolidated into minute and hour over-the-air statistics. The ota_minute_stats
table and ota_hour_stats table contain the same fields as the raw_ota_stats table.
Over-the-air statistics for all active remotes are calculated by the protocol processor and sent
to the NMS every five seconds. After sending a statistics message, the protocol processor
zeros its counts, so that every database record contains the delta in activity from the previous
record. The protocol processor continues to send messages to the NMS even if a remote is outof-network; the counts for these records contain all zeros.
Table 24. OTA Stats 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
int(10) unsigned
current_mc_idx
int(5) unsigned
index of remotes current MODCOD
rx_reliable_kbyte
double
kilobytes of reliable (e.g. TCP) data received
tx_reliable_kbyte
double
kilobytes of reliable (e.g. TCP) data sent to the remote
double
kilobytes of unreliable (e.g. UDP) data received
double
kilobytes of unreliable (e.g. UDP) data sent to the remote
rx_oob_kbyte
double
kilobytes of out-of-band bytes received
tx_oob_kbyte
double
kilobytes of out-of-band bytes sent to the remote
rx_unreliable_kbyte
tx_unreliable_kbyte
iMonitor User Guide

iDX Release 3.3
189
A.4.13 Over-the-Air Multicast Statistics Tables

As shown in Table 11, there are three separate base table types for over-the-air multicast
statistics, each one containing records that cover a particular period of time. The raw overthe-air multicast statistics are consolidated into minute and hour over-the-air multicast
statistics. The otacast_minute_stats table and otacast_hour_stats table contain the same
fields as the raw_otacast_stats table.
Over-the-air multicast statistics for all active remotes are calculated by protocol processor
and sent to the NMS every five seconds. After sending a statistics message, the protocol
processor zeros its counts, so that every database record contains the delta in activity from
the previous record. 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.
Table 25. OTA Multicast Statistics Record Format
Column Name
Data Type
Meaning
timestamp
timestamp(14)
time_t the message arrived at the NMS server
t_interval
int(10) unsigned
network_id
current_mc_idx
int(5) unsigned
index of current MODCOD
tx_unscaled_mcast_kbye
double
unscaled kilobytes of multicast data transmitted
tx_bcast_kbyte
double
kilobytes of broadcast data transmitted
tx_mcast_kbyte
double
kilobytes of multicast data transmitted
tx_bcast_ksym
double
kilosymbols of broadcast data transmitted
tx_mcast_ksym
double
kilosymbols of multicast data transmitted
A.4.14 Mesh Statistics Tables

As shown in Table 11, there are three separate base table types for mesh statistics, each one
containing records that cover a particular period of time. The raw mesh statistics are
consolidated into minute and hour mesh statistics. The mesh_minute_stats table and
mesh_hour_stats table contain the same fields as the raw_mesh_stats table.
NOTE: Mesh is not supported in iDX Release 3.3.
Mesh statistics for all active remotes are calculated by the remote and sent to the NMS every
20 seconds. After sending a statistics message, the remote zeros its counts, so that every
database record contains the delta in activity from the previous record. The remote continues
to send messages to the NMS even if a remote is out-of-network; the counts for these records
contain all zeros.
190
iMonitor User Guide

iDX Release 3.3
Table 26. Mesh Statistics Record Format

Column Name
Data Type
Meaning
timestamp
timestamp(14)
t_interval
int(10) unsigned
network_id
unique_id
int(10) unsigned
modem_sn
rx_reliable_kbyte
double
kilobytes of reliable (e.g. TCP) mesh data received

by the remote
tx_reliable_kbyte
double
kilobytes of reliable (e.g. TCP) mesh data sent by the

remote
rx_unreliable_kbyte
double
kilobytes of unreliable (e.g. UDP) mesh data received

by the remote
tx_unreliable_kbyte
double
kilobytes of unreliable (e.g. UDP) mesh data sent by

the remote
rx_oob_kbyte
double
kilobytes of out-of-band mesh data received by the

remote
tx_oob_kbyte
double
kilobytes of out-of-band mesh data sent by the

remote
A.4.15 DVB-S2 Statistics Tables

As shown in Table 11, there are three separate table types for DVB-S2 statistics. The
remote_dvbs2 table (Table 27) contains DVB-S2 statistics per remote as reported by the
protocol processor. The hub_dvbs2_stats table (Table 28) contains DVB-S2 statistics reported
by the line card. The pp_dvbs2_stats table (Table 29) contains DVB-S2 statistics reported by
the protocol processor per blade.
Table 27. remote_dvbs2_stats Record Format
Column Name
Data Type
Meaning
timestamp
timestamp(14)

server
t_interval
int(10) unsigned
network_id
remote_did
int(10) unsigned
current_modcod
bitmap representing the remotes current

MODCOD
current_modcod_range
int(10) unsigned
bitmap representing the remotes available

MODCODs
available_modcod
bitmap representing the networks available

MODCODs
iMonitor User Guide

iDX Release 3.3
191
Table 27. remote_dvbs2_stats Record Format (continued)

Column Name
192
Data Type
Meaning
current_SNR
int(10) unsigned
current SNR as reported by the remote to the pp
bytes_sent_mc01
int(10) unsigned
number of bytes sent at MODCOD 01
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
iMonitor User Guide

iDX Release 3.3
Table 28. hub_dvbs2_stats Record Format

Column Name
Data Type
Meaning
timestamp
timestamp(14)
t_interval
int(10) unsigned
network_id
hlc_did
int(10) unsigned
identifies the hub line card
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
iMonitor User Guide

iDX Release 3.3
193
Table 29. pp_dvbs2_stats Record Format

Column Name
194
Data Type
Meaning
timestamp
timestamp(14)
t_interval
int(10) unsigned
network_id
pp_id
identifies the protocol processor
pp_blade_id
identifies the protocol processor blade
target_hlc_id
identifies the target hub line card
available_modcod
bitmap representing the range of available MODCODs
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
iMonitor User Guide

iDX Release 3.3
Table 29. pp_dvbs2_stats Record Format (continued)

Column Name
Data Type
Meaning
bytes_sent_mc27
int(10) unsigned
bytes_sent_mc28
int(10) unsigned
A.4.16 Group QoS Statistics Tables

As shown in Table 11, there are two separate table types for group QoS statistics. The
nms_group_qos_stats table (Table 30) contains group-level GQoS statistics. The
nms_sl_qos_stats table (Table 31) contains service level GQoS statistics.
In addition, the group-level and service-level statistics are consolidated into minute and hour
Group QoS statistics. The group_qos_minute_stats table and group_qos_hour_stats table
contain the same fields as the nms_group_qos_stats table (Table 30). The sl_qos_minute_stats
table and sl_qos_hour_stats table contain the same fields as the nms_sl_qos_stats table
(Table 31).
Table 30. nms_group_qos_stats Record Format
Column Name
Data Type
Meaning
timestamp
timestamp(14)
t_interval
int(10) unsigned
unique_id
int(10) unsigned
Identifies the group
root_id
GQoS tree root
is_vr
virtual remote or not virtual remote
direction
downstream (0) or upstream (1)
bw_requested
double
amount of bandwidth requested
bw_allocated
double
amount of bandwidth allocated
free_bandwidth
double
amount of free bandwidth
cir_not_satisfied
double
unused
req_not_satisfied
double
unused
loops
double
unused
Table 31. nms_sl_qos_stats Record Format

Column Name
Data Type
Meaning
timestamp
timestamp(14)
t_interval
int(10) unsigned
unique_id
int(10) unsigned
Identifies the remote
vr_id
identifies the virtual remote
profile_id
identifies the group profile
iMonitor User Guide

iDX Release 3.3
195
Table 31. nms_sl_qos_stats Record Format (continued)

Column Name
Data Type
Meaning
service_level_id
identifies the service level
direction
downstream (0) or upstream (1)
tx_bytes
double
number of bytes transmitted
tx_packets
double
number of packets transmitted
rejected_packets
double
number of packets rejected
dropped_packets
double
number of packets dropped
A.4.17 Revision Activity and Revision State Tables

As shown in Table 11, there are two separate table types used to log revision server upgrades.
The rev_activity table (Table 32) contains one record per network upgrade. The rev_state
table (Table 33) contains one record per remote per network upgrade.
Table 32. rev_activity Record Format
Column Name
Data Type
Meaning
idx
int(10) unsigned
record index
network_id
smallint(6)
vno_group_id
int(10) unsigned
identifies the VNO
ofiles_only
tinyint(1)
set to 1 for options-file-only upgrade
transmit_rate
float(10,5)
transmit rate in bytes per second
last
timestamp(14)
end time of upgrade
start
timestamp(14)
start time of upgrade
nr_tries
int(10) unsigned
number of cycles required to upgrade all remotes
nr_remotes
int(10) unsigned
number of remotes upgraded
nr_down_rev
int(10) unsigned
number of remotes not yet upgraded
flag_status
smallint(6)
0: upgrade in progress; 1: upgrade complete;

-1: upgrade stopped in progress
credentials
int(10) unsigned
protocol processor multicast credentials
group_address
varchar(25)
multicast group address
Table 33. rev_state Record Format

Column Name
196
Data Type
Meaning
idx
int(10) unsigned
record index
user
varchar(32)
nms user
remote_name
varchar(64)
identifies the remote
remote_type
varchar(32)
identifies the remote model type
iMonitor User Guide

iDX Release 3.3
Table 33. rev_state Record Format (continued)

Column Name
Data Type
Meaning
remote_sn
int(10) unsigned
remote serial number
remote_did
int(11)
remote derived id
remote_family
enum
Values are:
UNKNOWN
NM2
2plus
Phoenix (used for Evolution remotes)
activity_idx
int(11)
links remote record to network upgrade record using

idx field of rev_activity log
up_rev
int(10) unsigned
0: remote not upgraded; 1: remote upgraded
date
smallint(6)
date and time of upgrade
rev_status
enum
Current state of upgrade cycle. Values are:
iMonitor User Guide

iDX Release 3.3
unknown
cumulative
binary
options
combined
check_cumlative
check_binary
check_options
check_combined
197
A.4.18 Inroute Group Composition Statistics

The protocol processor keeps statistics on each Inroute Group Composition (IGC) configured
for each Inroute Group. Statistics are sent to the NMS every 30 seconds or if the selected IGC
for the inroute group changes.
Table 34. inroute_composit_stats
Column Name
Data Type
Meaning
timestamp
timestamp(14)
t_interval
int(10) unsigned
network_id
int(10) unsigned
inroute_group_id
int(10) unsigned
identifies the inroute group
num_compositions
int(10) unsigned
number of IGCs configured for this inroute group
selected
int(10) unsigned
set to 1 if this is the currently-selected IGC for this

inroute group; otherwise 0.
composition_id
int(10) unsigned
identifies the IGC within this inroute group
figure_of_merit
float
estimation of the relative efficiency of this IGC as

measured against recent network conditions
m1_and_m2
int(10) unsigned
m1 and m2 margins configured for the inroute group

compressed into a single field (not used)
A.4.19 Inroute Slot Usage Statistics

The protocol processor keeps statistics on inroute slot usage for each remote on each inroute.
Inroute slot usage statistics are sent to the NMS every 30 seconds.
Table 35. inroute_slot_usage_stats
Column Name
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
number of inroutes in this inroute group
num_remotes
int(10) unsigned
number of remotes that used this inroute
remote_did
int(10) unsigned
inroute_id
int(10) unsigned
identifies the inroute
total_slots_from_inroutes
int(10) unsigned
number of slots on this inroute allocated to this

remote during reporting interval.
iMonitor User Guide

iDX Release 3.3
A.4.20 Remote Power Statistics

The protocol processor keeps power statistics for each remote in each inroute group. Remote
power statistics are sent to the NMS every 30 seconds.
Table 36. remote_power_stats
Column Name
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
length of the statistics message
remote_did
int(10) unsigned
unique identifier for a remote
nomial_carrier_id
int(10) unsigned
identifies the carrier with the highest threshold

C/N0 this remote can sustain and is allowed to use
power_headroom
int(10)
the amount (in dBs) that this remotes transmit

power can be increased before the remote is no
longer able to transmit on the nominal carrier
C_N0
int(10)
C/N0 of this remote as measured at the hub
mc_and_symbols
int(10) unsigned
MODCOD and symbol rate configured for the

upstream carrier compressed into a single field (not
used)
iMonitor User Guide

iDX Release 3.3
199
NMS Statistics Archive Database Structure
A.5

iDS Release 6.1 and later releases include a major overhaul to the statistics archive database.
The primary goal of this restructuring was to improve overall performance of the NMS server
machines as networks grow, and to improve historical query response times on large
networks.
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.
A.5.2 Archive Database Table Sets

Each type of statistical data that was formerly stored in a single database table is now stored
in multiple tables. All the tables that together contain the records of a particular statistics
type are called a table set. The table set for each type is sized on two dimensions: time and
unique ID. The default values specify a time dimension of 6 x 360 and an ID dimension of 1.
The time dimension consists of two parameters: the number of tables (which defaults to 6)
and the time span of the data in each table (which defaults to 360 minutes). For a complete
list of data types, see Table 38 on page 203.
These two dimensions result in the table set shown in Figure 201. Data in this default table
set is striped across the six tables in six-hour segments (hence the 6 x 360 time dimension).
Day by day, the six tables in the set will have the data striped across them as shown in
Table 37.
200
iMonitor User Guide

iDX Release 3.3
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
Figure 201. Default Table Set

Table 37. Default Data Striping
Day 1
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
A.5.3 The Archive Process

The following two diagrams illustrate how statistics archiving changed beginning with iDS
Release 6.1.
Database
Table
Archive Operation
Server
Incoming Stats
Figure 202. Release 6.0 and Earlier Statistics Archiving Process
iMonitor User Guide

iDX Release 3.3
201
Database
Tables
Database
Tables
Database
Tables
Database
Tables
Archive
Operation
Table
Selection
Algorithm
Incoming Stats
Server
Incoming Stats
Database
Tables
Database
Tables
Figure 203. New Statistics Archiving Process

In all releases beginning with iDS Release 6.1, instead of writing all data to one table as it
arrives at the NMS, the server first passes the data through a table selection algorithm. This
process determines the correct database table for the data that has just arrived. A similar
selection process also occurs when historical data is queried from iMonitor.
The selection rules are based on the following criteria:
202
The type of data IP statistics, events, condition changes, etc. As before, each type of
data has its own table structure
The remotes unique database ID
The current timestamp
iMonitor User Guide

iDX Release 3.3
A.5.4 Table Division Rules

All table selection rules are stored in the NMS configuration database in a table called
TABLE_INFO. This table has the following format and default values:
Table 38. TABLE_INFO Format and Default Contents
second_dimension_name
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 actual tables names,

derived from the base table
name. (These match the
table names in prior
releases)
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
iMonitor User Guide

iDX Release 3.3
raw_mesh_stats
unique_id
203
Table 38. TABLE_INFO Format and Default Contents (continued)

18
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
iMonitor User Guide

iDX Release 3.3
A.5.5 Table Selection Process

Insertion, selection, and deletion operations all use table selection algorithms, based on
current timestamp and current id, to determine which table to access.
The algorithm for calculating a table name for an operation has a number of steps, as shown
below:
Constants:
base_time
= 1072915201 (Linux time_t)
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
Figure 204. Algorithm for Calculating Database Table Name

NOTE: In a distributed NMS system, read TABLE_INFO from the master MySQL
server. This is typically the NMS server running the Configuration Server process.
iMonitor User Guide

iDX Release 3.3
205
A.5.6 Converting Data between Table Formats

After the Upgrade to Release 6.1 or Later
Archive data is not converted to the new format during the NMS upgrade from a pre-iDS 6.1
release. Rather, the new table structure is created with empty tables, and all existing data
remains in the old tables. The following figure illustrates the database structure for
raw_ip_stats statistics after the upgrade to iDS Release 6.1 or later.
raw _ip_stats_0
raw _ip_stats_1
raw_ip_stats_2
Existing
Data
raw _ip_stats_3
Existing
raw _ip_stats
data
Empty
raw _ip_stats_4
raw_ip_stats_5
Figure 205. Archive Database after Conversion to 6.1

After the NMS server restarts, new data arriving at the NMS is archived to the new tables. The
old data will remain in the old tables until it is deleted or converted to the new format.
To convert an existing archive data to the new format:
2. At the command prompt, type:
cd /home/nms/utils/db_maint
3. Convert the archive data by typing:
./DB-Conversion.pl
The DB-Conversion.pl command has the following format and output which can be
displayed by entering the command with the -h qualifier:
./DB-Conversion.pl -h
Usage:
DB-Conversion.pl [-cd=NAME] [-ad=NAME]
-cd : Change config database from [nms]
-ad : Change archive database from [nrd_archive]
206
iMonitor User Guide

iDX Release 3.3
Changing the Table Structure

It is possible to modify the TABLE_INFO settings shown in Table 38 on page 203. For example,
you can change the number of time tables, the second dimension tables, or the time interval.
CAUTION: To modify the default TABLE_INFO settings for a Distributed NMS,
change the database on the master MySQL machine. This is typically the NMS
server machine running the Configuration Server process.
To modify the TABLE_INFO settings:
2. At the command prompt, type:
cd /home/nms/utils/db_maint
3. Stop NMS Services by typing:
service idirect_nms stop
CAUTION: Stop NMS Services before changing the table structure, or run this
process offline.
4. Use the ./DB-Migration.pl script to change the table structure. All forms of this
script are shown below.
./DB-Migration.pl -h
DB-Migration.pl [-cd=NAME] [-ad=NAME] [-DD]
-cd
: Change config database from [nms]
-ad
: Change archive database from [nrd_archive]
-DD
: Do not touch any data outside of the ip_stats
-suffix
: Change suffix for existing tables for database

[nrd_archive], default is "old"
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.
A.5.7 Optimizing Archive Database Performance

The efficiency of archive database access is affected by the size and number of tables for
each statistics type in the archive. iDirect provides a database partitioning calculator to help
determine the optimal size of these tables based on the number of remotes in the network
and the frequency with which the statistics are updated in the archive. After running the
calculator to determine the optimal settings, update the information in columns two through
four of the TABLE_INFO table shown in Table 38 on page 203 to match the results of the
calculations.
iMonitor User Guide

iDX Release 3.3
207
Copying the Archive Database Partitioning Calculator to a PC

The calculator is installed on the NMS server as part of the iDirect software release. Before
using the calculator, copy it to a PC or laptop. The procedure in this section uses Cygwin to
retrieve the calculator. Since remote access to the /home/nms/ directory is not allowed, the
procedure copies the calculator to the /home/idirect/ directory on the NMS server before
transferring it to the PC.
To copy the archive database partitioning calculator to a PC or laptop:
1. Log on to the root account of the NMS server.
2. From the root account, copy the partitioning calculator to a directory on the NMS server
that allows remote access. In this example, the calculator is copied to the /home/idirect/
directory.
cp /home/nms/utils/db_maint/table_info-calculator.htm /home/idirect/
3. Create a folder on the PC or laptop in which to store the calculator.
4. Start Cygwin on the PC or laptop.
5. In the Cygwin window, use the cd command to change to the new folder. The command
syntax is show here using the directory db_calculator at the top level of the C: drive.
cd /c/db_calculator
6. In the Cygwin terminal window, type:
SCP idirect@<IP Address>:/home/idirect/table_info-calculator.htm ./
where <IP Address> is the IP address of the NMS server.
7. Enter the password when prompted. The calculator will be transferred to the PC.
8. Enter the following command to reformat the local copy of the calculator for the Windows
environment.
unix2dos table_info-calculator.htm
9. Close the Cygwin terminal window.
Using the Archive Database Partitioning Calculator

The archive database partitioning calculator is an HTML application that must be run in
Microsofts Internet Explorer (IE) web browser. To use the calculator:
1. On the PC or laptop, navigate to the folder containing the calculator.
2. Right-click the calculator and select Open WithInternet Explorer to display the
calculator in a browser window.
208
iMonitor User Guide

iDX Release 3.3
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.
Figure 206. Allowing Blocked Content for Database Partitioning Calculator

4. Use the calculator to determine the optimal settings for the archive database partitions.
These parameters are described below.
iMonitor User Guide

iDX Release 3.3
209
Figure 207. Archive Database Partitioning Calculator

Figure 207 shows the calculated results for the nms_remote_status table in a network with
750 remotes with a logging rate of four times per minute. The parameters are entered in the
top portion of the screen. Click the Calculate Table_Info data button to run the calculator.
The results appear in the lower (yellow) portion of the screen.
The following parameters can be entered in the calculator.
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.
iMonitor User Guide

iDX Release 3.3
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.
Number of Second Dimension Elements represents approximately the total number of

devices (second dimension elements) associated with the Base Table Name in the
network. Note that if the number of remotes in the network changes significantly,
consider re-executing the calculator and reconfiguring the TABLE_INFO for tables that log
remote statistics. You can vary the number of second dimension elements used by the
calculator in increments of 250.
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.
After calculating the optimal time_table_number, second_dimension_name and

time_interval for all tables to be optimized, log on to the root directory of the NMS server
and use MySQL to change the TABLE_INFO configuration in the NMS database to match the
optimal values.
Figure 208 shows the table set that would be created for nms_remote_status if INFO_TABLE
were modified in accordance with the values calculated in figure Figure 207 on page 210.
iMonitor User Guide

iDX Release 3.3
211
Figure 208. Segmented nms_remote_status archive tables
A.5.8 Selecting from the Restructured Database

Prior to iDS Release 6.1, a single query against a single table was sufficient to select records
from the statistics archive. For instance, prior to 6.1, the following query retrieved all
state_change_log records with time range of 2006-11-20 10:00 to 2006-11-20 14:00:
SELECT * FROM state_change_log WHERE timestamp BETWEEN
20061120100000 AND 20061120140000;
Because all records were in one table, state_change_log, a complete result set was returned.
In the restructured database, a query on a sufficiently large time range (by default, in excess
of six hours) spans multiple tables. When the query time range reaches ttn * tis hours (6 * 6 =
36 hours by default), the result retrieves data from every table in the table set. Up to the ttn
* tis time range limit, you must choose between efficiency and simplicity. When the goal is
efficiency, a query must be pre-processed and split, so that only tables containing matching
records are queried. When the goal is simplicity, simpler queries can be written that may
include tables that do not contribute to the result set.
Identifying the Location of the Result Set

When the result set is guaranteed to come from only one or two tables, it makes sense to
avoid query overhead by applying the query selectively. To do so, first calculate the index for
every table containing records in the query time range. Then, run one query per table index
calculated.
Using the example above and default striping parameters:
Inputs:
Stripe base time (base) = 2004-01-01 00:00:01 = 1072915201
TABLE_INFO.time_table_number (ttn) = 6 tables
TABLE_INFO.time_interval (tis) = 6 hours = 21600 seconds
212
iMonitor User Guide

iDX Release 3.3
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
= ((start base) / tis % ttn

= ((1164016800 1072915201) / 21600) % 6
=5
The last table index derives from end:

Idx_N
= ((end base) / tis) % ttn

= ((1164031200 1072915201) / 21600) % 6
=0
Divide the query among all indexes:

In this case, the first half of our records is in state_change_log_5:
SELECT * FROM state_change_log_5 WHERE timestamp BETWEEN
20061120100000 AND 20061120140000;
and the remaining records are in state_change_log_0:
20061120100000 AND 20061120140000;
Concatenating the two result sets returns the same answer arrived at in the 1st example.
Larger time range:
The procedure is exactly the same with a larger time ranges:
Query start time (start) = 2006-11-20 19:00:00 = 1164049200
Query end time (end) = 2006-11-21 07:00:00 = 1164092400
Idx_0
= ((1165059200 1072915201) / 21600) % 6

= 1
Idx_N
= ((1164092400 1072915201) / 21600) % 6

= 3
The queries to run are:

20061120100000 AND 20061120140000;
20061120100000 AND 20061120140000;
20061120100000 AND 20061120140000;
iMonitor User Guide

iDX Release 3.3
213
Ignoring the Location of the Result Set (Part One)

When the goal is to write simpler scripts, or when query time ranges near the tis * ttn limit,
skip query pre-processing and simply query all tables. There are two portable methods for
doing this:
Multiple queries, external concatenation:
As in the second example, you could make multiple queries, and then concatenate and sort
externally (in Perl, for instance):
20061120100000 AND 20061120140000;
20061120100000 AND 20061120140000;
20061120100000 AND 20061120140000;
20061120100000 AND 20061120140000;
20061120100000 AND 20061120140000;
20061120100000 AND 20061120140000;
Unions:
A slightly simpler method is to use UNIONs:
(SELECT * FROM state_change_log_0 WHERE timestamp BETWEEN
20061120100000 AND 20061120140000)
UNION
20061120100000 AND 20061120140000)
UNION
20061120100000 AND 20061120140000)
UNION
20061120100000 AND 20061120140000)
UNION
20061120100000 AND 20061120140000)
UNION
20061120100000 AND 20061120140000)
ORDER BY timestamp;
With this method, MySQL concatenates and sorts the records. No post-processing is required.
214
iMonitor User Guide

iDX Release 3.3
Ignoring the Location of the Result Set (Part Two)

MySQL has a feature that makes querying multiple tables even simpler. A MERGE table is a
collection of identical tables that can be used as a single table. To create a MERGE table of
state_change_log_X:
CREATE TABLE state_change_log_merged (
`timestamp` timestamp(14) NOT NULL,
ùnique_id` int(10) unsigned NOT NULL default '0',
`modem_sn` int(10) unsigned NOT NULL default '0',
`current_state`
enum('OK','WARNING','ALARM','UNKNOWN','OFFLINE','ELSEWHERE','MESHAL
ARM','SLEEP','STATE_NONE') default NULL,
òccurred_at` timestamp(14) NOT NULL,
èrror_type` smallint(6) default NULL,
èrror_severity`
enum('EVTWarning','EVTAlarm','EVTCleared','EVTOffline','EVTElsewher
e','EVTMeshAlarm','EVTSleep','EVTNone') default 'EVTNone',
reason` varchar(255) default NULL,
KEY ÌDX_TIME_UQ` (`timestamp`,ùnique_id`))
TYPE=MERGE
UNION=(state_change_log_0, state_change_log_1, state_change_log_2,
state_change_log_3, state_change_log_4, state_change_log_5);
Most of the CREATE statement consists of a copy of state_change_log_Xs CREATE statement.
(You can view it by issuing the query SHOW CREATE TABLE state_change_log_0.) The
differences are the name, of course; the TYPE or ENGINE clause, which tells MySQL what
kind of table were creating (normally MyISAM); and an additional UNION clause, which
identifies the list of tables in the collection.
With a MERGE table interface to the restructured database, pre-iDS 6.1 queries require only
one change:
SELECT * FROM state_change_log_merged WHERE timestamp BETWEEN
20061120100000 AND 20061120140000 ORDER BY timestamp;
A query on a MERGE table behaves, internally, the same way as the UNION query. MySQL runs
the query on every table in the collection then collates the results (as directed by the ORDER
BY clause.) The sole benefit is shorter, cleaner queries.
iMonitor User Guide

iDX Release 3.3
215
216
iMonitor User Guide

iDX Release 3.3
Appendix B Alarms and

Warnings
The iDirect NMS provides real-time notification of system anomalies, classified by severity.
iMonitor displays the or real-time state and operational characteristics of network elements.
The real-time state indicates the status (OK, Warning or Alarm) of the network elements. The
status of the network elements helps to diagnose and resolve operational problems in the
network.
For a list of real-time states select ViewLegend from the iMonitor main menu or see Table 4
on page 30. To see the current status of network elements, observe the icons representing
those elements in the iMonitor tree. For a textual description of the status of each element in
the tree, select ViewView Real Time Status from the iMonitor main menu.
Alarms indicate an interruption in service or remote sites that are out-of-network. Warnings
indicate potential problems and system values that are out of range.
This appendix provides troubleshooting recommendations for a subset of alarms and warnings.
Not all warnings are listed in this appendix. See Table 6 on page 33 for a comprehensive list of
warnings for each network element.
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
Verify that the network path to the hub chassis is

available from the NMS server (ping, tracert).
Verify that the hub chassis is powered up.
Verify that the chassis controller card (MIDAS or EDAS) is

connected to the upstream LAN, not the tunnel LAN.
Note: It is likely that the hub line cards are still operating.
iMonitor User Guide

iDX Release 3.3
217
Warnings
Table 39. Alarms (continued)

Alarm
Description
Line Card Down
PP Down
Remote Layer 3
Verify that the NMS server can communicate with the line
cards across upstream router (ping, tracert).
Verify that the chassis slot is powered on in iBuilder.
In case of line card failure, check status LED on line card

front panel. Solid Red LED indicates that the line card has
detected a fault, or Application software or firmware
cannot be loaded. Replace the line card or reload
firmware images.
Verify that the network path to Protocol Processor is

available from the NMS server (ping, tracert).
Verify that the Protocol Processor is powered up and

operational.
Remote is not in
network (out of
network or link layer
down)
Verify that the configuration is complete and activated in

iBuilder.
Check the stability of the RF link
Check history in iMonitor of Tx Power and Down C/N of

remote. Higher Tx power and lower C/N indicate
degradation.
Short-term may indicate rain fade.
Long-term may indicate degradation of installation.
Check RF chain: BUC, LNB, cables, connectors for
moisture. Dish positioning.
Remote is not
responding to ICMPs,
i.e. has missed 3
ICMPs in a row.
This can be due to high traffic load. (Remote may still be

in network.)
Verify that the network path to the remote is available

from the NMS server (tracert, ping) or where the network
path is broken.
Protocol Processor is
not responding
Remote Layer 2
B.2
Line card is powered

off or has failed.
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
iMonitor User Guide

iDX Release 3.3
Warnings
NOTE: If NMS Database Replication is enabled, take action to clear all

Replication Failed warnings and their associated conditions. Allowing the
condition to persist for a long time can cause the Primary NMS to run out of disk
space.
Table 40. Warnings
Device
Hub
Chassis
Warning Condition
PowerAlarm1
Description
Hub chassis power supply 1 failed.
Replace power supply 1
If one of the three Power

Supply Modules fails, the other two
Power Supply Modules are capable of
sourcing enough power to make up
for the failed supply module.
PowerAlarm2
Hub chassis power supply 2 failed
Replace power supply 2
FanAlarm
A Fan failure is reported if the any of

the three Fan Modules propeller
spins below a predetermined
revolution-per-minute (RPM).
Verify the Fan Alarm Status on

the rear of the hub chassis. A
failed fan will be indicated by
the red color LED.
A fully loaded 20 slot hub chassis can

remain in operation with two of the
three Fan Modules still functioning.
Replace failed cooling fan
Hub chassis reference clock module

(RCM) A failed.
If RCM [A, B] is set to external

clock mode, check for loss of 10
MHz clock source.
RCMAAlarm
Check RCM A for failure. Replace

reference clock module A.
RCMBAlarm
Hub chassis reference clock module

(RCM) B failed.
If RCM [A, B] is set to external

clock mode, check for loss of 10
MHz clock source.
Check RCM B for failure. Replace
reference clock module B.
Hub Line
Card
RX_OVERFLOW_FRAMES
Received frames are lost. Total of

received and transmitted frames
exceed hub line cards performance
limits.
DOWNSTREAM_PPS_OVERDRIVE
Downstream packets-per-second
count above fixed limit
BACKPLANE_LOST_10MHZ
Line card lost the chassis backplane

10 MHz timing signal
iMonitor User Guide

iDX Release 3.3
Add new hub line card and

dedicate one line card to
transmission only.
Verify that both RCMs are

installed and functional. If they
are, this could mean a possible
chassis backplane failure;
contact the TAC for further
assistance.
219
Warnings
Table 40. Warnings (continued)

Device
Remote
Warning Condition
Description
ACQ_HUB_MODEM_CRC
Line cards acquisition CRC count

above defined limit of 200 within 15
seconds.
Normal during acquisition

process.
CALIBRATED_TX_POWER
Remotes transmit power below or

above defined power limits
CERTIFICATE_HAS_EXPIRED
TRANSEC remotes X.509 certificate

has expired.
Issue a new X.509 certificate to

remote.
CERTIFICATE_INVALID

is invalid

remote.
CERTIFICATE_WILL_EXPIRE

will expire in 30 days.

remote.
DOWNSTREAM_SNR
Downstream C/N as measured at

remote is below or above limits
Weak signal could be due to rain

fade.
Check transmit power levels in
iBuilder.
LATENCY
Measured latency, hub to remote is

more than 2000 ms.
Increased latency may be related

to high traffic load.
LOCAL_LAN_DISCONNECT
LAN port on remote is disconnected.
Call customer.
MOBILE_LOST_GPS
Mobile remotes GPS has stopped

functioning.
Do not reset the remote.
Nominal Carrier Equivocation

Occurring
A remote is switching nominal

carriers rapidly on a specific inroute
ID.
Re-evaluate power levels for

remote.
REMOTE_OFFLINE
Remote has been taken offline by

local operator. This causes all alarms
and warnings from this remote to be
ignored.
This is not an alarm or warning.
SYMBOL_OFFSET
Remote timing offset below or above

calculated limits
Verify exact geographic location

of satellite, hub, and remote.
Adjust in order to minimize
offset.
TEMP_LIMIT
Remotes on-board temperature is

below/above defined limits
Call customer.
TRAFFIC_HUB_MODEM_CRC
Line cards traffic CRC count above

defined limit of 10 in 15 seconds.
Check for timing problem, power

problem, RF link.
UCP_LOST_CONTACT
Protocol Processor has temporarily

lost contact with remote.
Possibly due to rain fade.
UPSTREAM_SNR
Remote C/N as measured at hub is

below or above limits
Weak signal could be due to rain

fade.
Contact customer.
When remote rejoins the

network, this condition clears.
Check transmit power levels in

iBuilder and iMonitor to
determine if the remote is
transmitting at max power.
220
iMonitor User Guide

iDX Release 3.3
Warnings
iMonitor User Guide

iDX Release 3.3
221
Warnings
222
iMonitor User Guide

iDX Release 3.3
Appendix C SNMP Proxy

Agent
The iDirect NMS includes an SNMP proxy agent that provides real-time status, statistical
information, and basic configuration information to any interested SNMP client.
C.1
How the Proxy Agent Works

The SNMP Proxy Agent is a client of the NMS Configuration Server, NMS Event Server, NRD
Server and Latency Server. The Proxy Agent receives the following information from each of
these NMS processes:
The list of network elements from the Configuration Server
The real-time status of each element from the Event Server
Statistical information for all remotes and line cards from the NRD Server
Latency information from the Latency 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.
iMonitor User Guide

iDX Release 3.3
223
The iDirect Management Information Base (MIB)
Figure 209 illustrates how the SNMP Proxy Agent fits into the overall NMS architecture
Figure 209. SNMP Proxy Architecture
C.2

The SNMP MIB supplies the information in Table 41 for iDirect network elements.
Table 41. iDirect MIB Contents
Element Type
Protocol Processor
224
Available Information
ID
Name
Teleport ID
Current State
List of Warnings
List of Alarms
Condition Raised (trap)
Condition Cleared (trap)
iMonitor User Guide

iDX Release 3.3
Table 41. iDirect MIB Contents (continued)

Element Type
Chassis
ID
Name
Current State
List of Warnings
List of Alarms
DID
Protocol Processor ID
Network ID
Remote Modem
iMonitor User Guide

iDX Release 3.3
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
Data Class
IP Statistics
Remote DID
Not Applicable
Rx tcp packets in bytes
Running Total
Rx udp packets in bytes
Running Total
Rx icmp packets in bytes
Running Total
Rx igmp packets in bytes
Running Total
Rx http packets in bytes
Running Total
Rx other packets in bytes
Running Total
Tx tcp packets in bytes
Running Total
Tx udp packets in bytes
Running Total
Tx icmp packets in bytes
Running Total
Tx igmp packets in bytes
Running Total
Tx http packets in bytes
Running Total
Tx other packets in bytes
Running Total
Ip statistics last updated timestamp

OTA Statistics
Remote DID
Not Applicable
OTA Mode: always DVBS2
Overwrite
Downstream reliable in bytes
Running Total
Downstream unreliable in bytes
Running Total
Downstream overhead in bytes
Running Total
Downstream multicast in bytes
Running Total
Downstream broadcast in bytes
Running Total
Downstream total in kilobytes
Running Total
Upstream reliable in bytes
Running Total
Upstream unreliable in bytes
Running Total
Upstream overhead in bytes
Running Total
Upstream total in kilobytes
Running Total
OTA statistics last updated Timestamp
226
iMonitor User Guide

iDX Release 3.3
Table 42. iDirect MIB Statistical Information (continued)

Statistics Type
Data Class
Remote UCP
Remote DID
Not Applicable
Upstream C/N0 in dB
Overwrite
Power Adjustment in dBm
Overwrite
Symbol Offset
Overwrite
Frequency Offset in Hz
Overwrite
Downstream SNR
Overwrite
Remote UCP statistics last updated Timestamp

Latency
Remote DID
Not Applicable
Remote Name
Not Applicable
Remote SN
Not Applicable
IP address
Overwrite
Latency in seconds
Overwrite
Network Name
Not Applicable
Latency statistics last updated Timestamp
iMonitor User Guide

iDX Release 3.3
227

Statistics Type
Data Class
Hub Statistics
Line Card DID
Not Applicable
Type SN
Not Applicable
Tx attempts
Running Total
Tx bytes
Running Total
Tx errors
Running Total
Acq CRC errors
Running Total
Traffic CRC errors
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
Gigabit Ethernet Status
Overwrite
Buffer Overflow
Overwrite
Front End Rx Power
Overwrite
GIGE transmit errors
Running Total
GIGE receive errors
Running Total
SCPC return Rx gain
Overwrite
SCPC return carrier offset
Overwrite
SCPC return lock status
Overwrite
SCPC return lost lock count
Running Total
TDMA AGC errors
Running Total
TDMA traffic errors
Running Total
TDMA bursts
Running Total
TDMA Rx bytes
Running Total
TDMA Rx gain
Overwrite
Hub statistics last updated Timestamp
228
iMonitor User Guide

iDX Release 3.3

Statistics Type
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
Fll dac (also referred to as Clock DAC)
Overwrite
Rx Carrier Frequency Offset
Overwrite
Temperature
Overwrite
TDM lost
Running Total
SCPC downsteam errors (N/A in iDX 3.3)
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
Fast Fade Corrections
Running Total
CRC 8 Errors
Running Total
CRC 32 Errors
Running Total
NCR Lost
Running Total
Physical Layer Sync Lost
Running Total
Clock Delta Count
Running Total
Digital AGC Gain
Overwrite
Tuner AGC Gain
Overwrite
Frequency Oscillator Offset
Overwrite
TDMA CRC Errors
Running Total
TDMA Calibrated SNR
Running Total
TDMA Symbol Offset
Running Total
TDMA Frequency Offset
Running Total
iMonitor User Guide

iDX Release 3.3
229

Statistics Type
Data Class
Reliable Bytes Received
Running Total
Unreliable Bytes Received
Running Total
Out of Band Bytes Received
Running Total
Reliable Bytes Transmitted
Running Total
Unreliable Bytes Transmitted
Running Total
Out of Band Bytes Transmitted
Running Total
Remote Status last updated Timestamp
230
Server Start Time
This Timestamp specifies the start time of the

statistical Data
Remote DVB-S2
Statistics
Remote DID
Overwrite
Clear Sky MODCOD
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
iMonitor User Guide

iDX Release 3.3

Statistics Type
Hub DVB-S2
Statistics
iMonitor User Guide

iDX Release 3.3
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
DVB-S2 Statistics Time
Running Total
Total Bytes on all MODCODs
Running Total
DID
Overwrite
High Priority Bytes Transmitted
Running Total
Low Priority Bytes Transmitted
Running Total
Dummy Frames Transmitted
Running Total
Gigibit Ethernet Status
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

Statistics Type
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
Total Bytes on all MODCODs
Running Total
DVB-S2 Statistics Time

Remote Upstream
Statistics
232
Remote DID
Overwrite
Rx statistics type
Overwrite
TDMA acquisition bursts
Running Total
TDMA acquisition CRC errors
Running Total
TDMA missing acquisition bursts
Running Total
TDMA mismatch ac qui st ion bursts
Running Total
TDMA traffic bursts
Running Total
TDMA traffic CRC errors
Running Total
TDMA missing traffic bursts
Running Total
TDMA mismatch traffic bursts
Running Total
TDMA keepalive bursts
Running Total
SCPC return packets
Running Total
SCPC return octet and CRC errors
Running Total
SCPC return mismatch packets
Running Total
SCPC return keepalive packets
Running Total
Remote upstream statistics time
Running Total
iMonitor User Guide

iDX Release 3.3
C.2.1 Resetting Statistical Data

There are two classes of statistics contained in the MIB: cumulative statistics, such as IP
statistics and CRC errors; and discrete snapshot measurements, such as temperature and
frequency offset.
Each time statistics arrive from the network and the MIB is updated, new values for
cumulative statistics are added to current values, creating running totals. In contrast, new
values for discrete statistics overwrite the old values. These two types of statistics are
distinguished in Table 42 by the Data Class column.
Cumulative statistics are useful in determining a total value since a previous time. In order to
reset the start time for cumulative statistics (that is, to reset the counts to zero), a special
object type is included in the MIB. When referenced, this object will reset all the statistics
counters to zero.
The object is defined in the MIB as follows:
resetAllStatTables OBJECT-TYPE
SYNTAX
Unsigned32
MAX-ACCESS read-write
STATUS
current
DESCRIPTION " This field will reset all the statistical
tables under the idirectstats OID"
::= {idirectstats 7}
To reset the statistical data:
1. Log in to the NMS server machine as root.
2. Using the vi editor, edit the Net-SNMP daemon configuration file snmpd.conf:
cd /etc/snmp
vi snmpd.conf
3. Add the following line to the file:
rwcommunity private
NOTE: Add the above line only if snmpd.conf does not already contain it.
4. Restart the snmpd service:
Example: /etc/init.d/snmpd restart
5. Use the SNMP SET command to set the MIB Object resetAllStatTables to 1.
Usage: snmpset -v 2c -c private <NMS server Ipaddress>
resetAllStatTables.0 u 1
Data types and table entry names are available from the MIB. The MIB is defined in the
following file on the NMS server machine:
/usr/share/snmp/mibs/IDIRECT-REMOTE-MIB.txt
iMonitor User Guide

iDX Release 3.3
233
C.2.2 iDirect MIB SNMP Traps

The iDirect SNMP Proxy Agent sends traps to any configured trap recipient based on network
element state changes and raised or cleared element conditions. See the next section of this
document for information on configuring trap recipients.
The complete list of traps is shown in Table 43. You will receive each trap when the specified
anomaly arises, and again when the condition clears. The trap-level field in the MIB specifies
the severity.
Table 43. iDirect MIB Traps
Trap Name
Generate When...
Severity
Network
Elements
snmpProxyStart
SNMP Proxy Agent starts up
N/A
SNMP Proxy Agent
snmpProxyStop
SNMP Proxy Agent shuts down
N/A
SNMP Proxy Agent
upstreamSNR
Upstream C/N0 goes outside specified limits
Warning
Remotes
downstreamSNR
Downstream SNR goes outside specified limits
Warning
Remotes
tempLimit
Onboard temperature goes outside specified

limits
Warning
Remotes
latency
Latency measurement exceeds high limit
Warning
Remotes
symbolOffset
Symbol offset goes outside specified limits
Warning
Remotes
ethernetUnplugged
The local LAN port is non-functional
Warning
Remotes
ucpLostContact
The protocol processor loses contact with a

remote
Warning
Remotes
lldown
The protocol processors link layer interface

for a remote goes down
Alarm
Remotes
ucpOutOfNetwork
The protocol processor declares a remote out

of network
Alarm
Remotes
latTimeout
Latency measurements are failing
Alarm
Remotes
remoteOffline
The remote has been commanded offline
Offline
Remotes
lackHubStats
The NMS is no longer receiving hub statistics
Alarm
Hub Modems
acqHubModemCRC
Acquisition CRC count exceeds high limit
Warning
Hub Modems
trafficHubModemCRC
Traffic CRC count exceeds high limit
Warning
Hub Modems
ppStateTrap
The NMS has stopped hearing from the

protocol processor
Alarm
Protocol Processor
powerAlarm1, 2, 3
The specified power supply has failed
Warning
Chassis
fanAlarm
One of the fans has failed
Warning
Chassis
chassisDown
The NMS cannot contact the chassis
Alarm
Chassis
scpcRxErrors
A remote has received errors on the

downstream
Warning
Remotes
fllDacErrors
A remotes digital-to-analog converter (DAC) is

operating outside the defined limits
Warning
Remotes
234
iMonitor User Guide

iDX Release 3.3
Table 43. iDirect MIB Traps (continued)

Trap Name
Generate When...
Severity
Network
Elements
rxOverflowFramesHubModem
Receive Overflow Frames, data lost
Warning
Hub Line Card
downstreamPpsOverdrive
Packets-per-second overdrive between PP and

line card
Warning
Hub Line Card
backplaneLost10Mhz
The line card lost the backplane 10 MHz clock

signal
Warning
Hub Line Card
calibratedTxPower
Transmit power is above or below the

calibrated limit
Warning
Remotes
txFrequency
Transmit frequency is above or below the

calibrated limit
Warning
Remotes
mobileLostGps
Mobile remote lost the GPS signal
Warning
Remotes
lcFailure
Line card has failed
Alarm
Hub Line Card
meshError
Mesh mode has changed: Remote is not in

mesh mode
Alarm
Remotes
meshTdmLockLost
TDM lock lost
Alarm
Hub Line Card
meshHubRxScpcSnr
The Hub downstream Rx loopback C/N

exceeds the calibrated hub clear sky C/N
Warning
Hub Line Card
meshHubRxTdmaSnr
The Hub TDMA C/N exceeds the calibrated hub

clear sky C/N
Warning
Hub Line Card
lineCardAGCOutOFRange
AGC gain out of range
Warning
Hub Line Card
meshRmtRxScpcSnr
The remote downstream Rx C/N exceeds the

calibrated remote clear sky C/N
Warning
Remotes
meshRmtRxTDMASnr
The remote Rx TDMA loopback C/N exceeds

the calibrated remote clear sky C/N
Warning
Remotes
remoteAgcOutOfRange
AGC gain out of range
Warning
Remotes
rcmAAlarm
The Reference Clock Module control timer A is

in error
Warning
Chassis
rcmBAlarm
The Reference Clock Module control timer B is

in error
Warning
Chassis
lostChassisConnection
Lost connection to Chassis Manager Server
Warning
Chassis
microChassisOverTemp
Chassis over temperature alarm
Warning
Four-Slot Chassis
microRCMANotPresent
RCM A has not been installed in the Chassis
Warning
Four-Slot Chassis
microRCMAFault
RCM A of the chassis has failed
Warning
Four-Slot Chassis
microRCMBNotPresent
RCM B has not been installed in the chassis
Warning
Four-Slot Chassis
microRCMBFault
RCM B of the chassis has failed
Warning
Four-Slot Chassis
microPwrAlarmABad
Chassis power supply A has failed
Warning
Four-Slot Chassis
microPwrAlarmAOverTem
Chassis power supply A exceeds temperature

limit
Warning
Four-Slot Chassis
iMonitor User Guide

iDX Release 3.3
235

Trap Name
Generate When...
Severity
Network
Elements
microPwrAlarmBBad
Chassis power supply B has failed
Warning
Four-Slot Chassis
microPwrAlarmBOverTemp
Chassis power supply B exceeds temperature

limit
Warning
Four-Slot Chassis
microFSMNotPresent
FSM has not been installed on the chassis
Warning
Four-Slot Chassis
microFSMFault
FSM has failed on the chassis
Warning
Four-Slot Chassis
microFSMFanFault
FSM fan has failed on the chassis
Warning
Four-Slot Chassis
microIFMNotPresent
IFM has not been installed on the chassis
Warning
Four-Slot Chassis
microIFMFault
IFM has failed on the chassis
Warning
Four-Slot Chassis
microAlarmDisabled
Audible alarms are disabled for the chassis
Warning
Four-Slot Chassis
microOPMAFaul
OPM B has failed on the chassis
Warning
Four-Slot Chassis
microOPMBFault
OOPM B fault alarm
Warning
Four-Slot Chassis
reset
Reset has occurred
Warning
Remote/Line Card
unready
Not ready for failover
Warning
Line Card
flash
Flash Warning
Warning
Remote/Line Card
activationStatus
Activation Status
Alarm
Remote
elsewhereError
Remote is Elsewhere
Elsewher
e
Remote
backplaneLostSOF
Backplane lost Start Of Frame
Warning
Chassis
rmtMAXTxPwr
Remote exceeds Max Tx Power
Warning
Remote
bladeCPUHigh
High CPU usage on Blade
Warning
PP Blade
rmtSleep
Remote Sleep Alarm
Alarm
Remote
hubTenMHzAlarm
Hub 10MHz Alarm
Alarm
Line Card
gigeFailed
GIGE Port Failed
Alarm
Line Card
gigeHealth
GIGE Port Health Warning
Warning
Line Card
rxOnly
Remote in Rx Only mode
Rx only
Remote
crc8Errors
CRC 8 errors high
Warning
Remote
crc32Errors
CRC 32 errors high
Warning
Remote
ravenFailed
Raven failed
Alarm
Remote/Line Card
bladeNoEncLic
Blade has no encryption license
Warning
PP Blade
rmtAcqBurst
Remote acquisition Burst Warning
Warning
Remote
rmtCAWillExpire
Remotes X.509 certificate will expire
Warning
Remote
rmtCAExpired
Remote X.509 certificate has expired
Warning
Remote
rmtCAInvalid
Remotes X.509 certificate is invalid
Warning
Remote
236
iMonitor User Guide

iDX Release 3.3

Trap Name
Generate When...
Severity
Network
Elements
rmttxTDMAAcqCrc
Remotes TDMA acquisition CRC errors high
Warning
Remote
rmttxTDMADataCrc
Remotes TDMA traffic CRC errors high
Warning
Remote
rmttxTDMAAcqMismatch
Remotes TDMA Acquisition mismatch high
Warning
Remote
rmttxTDMADataMismatch
Remotes TDMA traffic mismatch high
Warning
Remote
rmttxTDMADataMissing
Remotes TDMA data missing high
Warning
Remote
rmttxSCPCLostLock
SCPC return lost lock
Alarm
Remote
rmttxSCPCHdlcError
SCPC return octet and CRC errors high
Warning
Remote
rmttxSCPCDataMismatch
SCPC return data mismatch high
Warning
Remote
rmtStatusChange
Remote real-time status changed
Warning
Remote
tristateIdle
Remote has entered the Idle state
Warning
Remote
tristateDormant
Remote has entered the Dormant state
Warning
Remote
powerAlarm1
Power supply 1 has failed
Warning
Chassis
powerAlarm2
Power supply 2 has failed
Warning
Chassis
powerAlarm3
Power supply 3 has failed (not used)
Warning
Chassis
C.2.3 Setting up SNMP Traps

To enable the SNMP Proxy Agent to send traps for network element state changes, you must
designate one or more machines to receive them. The machine name is a parameter in one of
Net-SNMPs configuration files.
To designate a machine to receive traps, use the following procedure:
1. Log on to the NMS server machine as root.
2. Use the vi editor to edit the Net-SNMP daemon configuration file:
cd /etc/snmp/
vi snmpd.conf
NOTE: In a few instances, the SNMP trap configuration has been moved into
/home/nms/snmpsvr/para_cfg.opt. If the instructions above are not accurate,
execute these commands instead:
cd /home/nms/snmpsvr/
vi para_cfg.opt
3. Add a line for each machine to receive SNMP Version 1 (v1) traps:
trapsink host [community [port]]
where host is the name of the machine to which to send the traps. The community and
port strings are optional.
4. Add a line for each machine to receive SNMP Version 2 (v2) traps:
iMonitor User Guide

iDX Release 3.3
237
Working with HP OpenView
trap2sink host [community [port]]

where host is the name of the machine to which to send the traps. The community and
port strings are optional.
CAUTION: Do not change or remove any other lines in this file.
C.3

The SNMP product installed on the NMS server machine is an open-source package called NetSNMP. The MIB syntax processing is slightly different between this package and HP OpenView.
When using HP OpenView as your SNMP client software, you must load the special HP
OpenView-specific MIB instead of the MIB that comes standard with our agent.
The HP OpenView MIB can found on the NMS server machine in the following location:
/home/nms/snmpsvr/IDIRECT-REMOTE-MIB.hpov.txt
C.3.1 Linux SNMP Tools

The Net-SNMP package supplies a number of command-line utilities that perform various
SNMP-related functions. These commands are listed in Table 44, along with a one-line
description of what each one does.
Table 44. SNMP Command Line Utilities
Command Name Severity
238
snmpbulkget
Communicates with a network entity using SNMP GETBULK Requests
snmpbulkwalk
Communicates with a network entity using SNMP BULK Requests
snmpcmd
Not a command, but a manual page that describes the common options for the
SNMP commands
snmpconf
Creates and modifies SNMP configuration files
snmpdelta
Monitor deltas of integer valued SNMP variables
snmpdf
Gets a listing of disk space usage on a remote machine via SNMP
snmpget
Communicates with a network entity using SNMP GET Requests
snmpgetnext
Communicates with a network entity using SNMP GET NEXT Requests
snmpnetstat
Show network status using SNMP
snmpset
Communicates with a network entity using SNMP SET Requests
snmpstatus
Retrieves important information from a network entity
snmptable
Obtain and print an SNMP table
snmptest
Communicates with a network entity using SNMP Requests
snmptranslate
Translate SNMP object Id (OID) values into more useful information
snmptrap
Sends an SNMP trap to a manager
iMonitor User Guide

iDX Release 3.3
Table 44. SNMP Command Line Utilities (continued)

Command Name Severity
snmpusm
Creates and maintains SNMPv3 users on a remote entity
snmpwalk
Communicates with a network entity using SNMP GETNEXT Requests
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.
iMonitor User Guide

iDX Release 3.3
239
240
iMonitor User Guide

iDX Release 3.3
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
iMonitor User Guide

iDX Release 3.3
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
IP long term bandwidth usage 163

IP routing table, viewing on remotes 146
IP traffic graph 156
sorting remotes by traffic volume 160
iSite 2
iVantage NMS components i
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
iMonitor User Guide

iDX Release 3.3
offline state 32
Rx power as reported by different model types 97
P
panes
conditions 24
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
iMonitor User Guide

iDX Release 3.3
243
time ranges, saving 8

timeplan display 66
toolbars
find 19
icons 19
legend 24
main 15, 19
main menu 19
status bar 21
view menu 19
tree
description 14
sorting the tree 13
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
iMonitor User Guide

iDX Release 3.3
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

UGiMonitor User Guide IDX 33rev C042415

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

UGiMonitor User Guide IDX 33rev C042415

Încărcat de

Drepturi de autor:

Formate disponibile

iMonitor User Guide A Component of iVantage NMS

iMonitor User Guide

iDX Release 3.3

April 27, 2015

Document Name: UG_iMonitor User Guide iDX 3.3_Rev C_04_24_15

iMonitor User Guide

First release of document for iDX 3.3

Update for iDX 3.3.1

A warning, Nominal Carrier Equivocation Occurring, has been added

iMonitor User Guide

iMonitor User Guide

The iVantage Network Management System . . . . . . . . . . . . . . . . . . . . . . . . . 21

Overview of the NMS for iMonitor . . . . . . . . . . . . . . . . . . . . . . . 1

Components of the Network Management System . . . . . . . . . . . . . . . . . . . . . . 2

Installing iBuilder, iMonitor, and iSite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Logging On to Additional Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Multiple Users or PCs Accessing the NMS . . . . . . . . . . . . . . . . . . . . . . . . . 6

Overview of iMonitor Usage and Displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Time Frames in iMonitor Requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

iMonitor User Guide

Saving Historical Time Ranges across Multiple Displays . . . . . . . . . . . . . . . . 8

Saving iMonitor Results to a File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Types of iMonitor Displays. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Multicolumn Details Displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Multiple vs. Grouped Display Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Using the iMonitor Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Using the iMonitor Toolbars and Menu Options . . . . . . . . . . . . . . . . . . . . 15

Selecting Columns for Viewing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Monitoring Conditions and Events . . . . . . . . . . . . . . . . . . . . . . 29

Representing the State of an Element with Icons. . . . . . . . . . . . . . . . . . . 29

Elements with Multiple Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Alarms and Warnings on Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

NMS Database Replication Warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Placing an Element Under Observation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Viewing Conditions or Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Examples of System Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Network, Teleport and Device Condition Snapshot. . . . . . . . . . . . . . . . . . 47

Network and Line Card Data Snapshot . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Monitoring Protocol Processor Blades. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Using the Remote Probe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Monitoring Performance and Status

Modifying the Timeout Duration for a CW or PN Carrier . . . . . . . . . . . . . . 62

CPU Usage on Protocol Processor Blades. . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

iMonitor User Guide

Inroute Group Composition Usage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Upstream C/N0 and Thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Viewing Inroute Distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

ACQ Bounce from the Inroute Distribution Pane . . . . . . . . . . . . . . . . . . . 79

Satellite Link Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Line Card Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Upstream Performance Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

SATCOM Graph, Remote Status and UCP Information . . . . . . . . . . . . . . . . 96

UCP Graph . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

Group QoS Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Group QoS Distribution Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Group QoS Plot Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Group QoS List Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

Control Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

Monitoring DVB-S2 Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

3.10.1 Monitoring the ACM Gain of DVB-S2 Carrier . . . . . . . . . . . . . . . . . . . . . 127

Connecting to Network Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

3.11.1 Examining IP Routing and HDLC Information on Remotes. . . . . . . . . . . . . 146

Traffic Statistics and Traffic Graphs . . . . . . . . . . . . . . . . . . .