NMS ibuilder training guide v80

Network
Management
g
System (NMS)

NMS iBuilder
Training Guide
v8.0
2007

iBuilder


Copyright Notice
iDirect Technologies Technical Training Manual
Copyright © 2002; 2004 - 2007, iDirect, Inc. All rights reserved. This
training material may not be reproduced, in part or in whole, without the
permission
i i off iDirect,
iDi
t Inc.
I
All other brands or product names are trademarks or registered
trademarks of their respective holders.
Printed in the USA.
No part of this work covered by copyright may be reproduced in any
form. Reproduction, adaptation, or translation without prior written
permission is prohibited, except as allowed under the copyright laws.
This p
publication is provided
p

by
y iDirect Technologies
g
as-is without
warranty of any kind, either express or implied, including, but not limited
to, the implied warranties or conditions of merchantability or fitness for a
particular purpose. iDirect Technologies shall not be liable for any errors
or omissions which may occur in this publication, nor for incidental or
consequential damages of any kind resulting from the furnishing
furnishing,
performance, or use of this publication.
Information published here is current or planned as of the date of
publication of this document. Because we are improving and adding
features to our products continuously
continuously, the information in this document
is subject to change without notice.
IOM - I Chapter 6 - NMS iBuilder

2


NMS Training Objectives
Network Management System Training Objectives

Introduction to NMS Features &
Options
Introduction to NMS Components
iBuilder, v8.0.x (IOM Chapter 6)
iMonitor v8
iMonitor,

v8.0.x
0 x (IOM Chapter 7)
iSite, v8.0.x (IOM Chapter 8)

Familiarization with NMS GUI/Client
iDirect Technical Assistance Center (TAC)
Modules
Instruction on Network Configuration using iBuilder v8.0.x
Menus, Commands and Controls
Network/Component Configuration Tasks

Instruction on Network Monitor Functions using iMonitor v8.0.x
Menus, Commands and Controls
Network/Component Monitor and Status Reporting
IOM - I Chapter 6 - NMS iBuilder

3


NMS Primary Features
iBuilder
Configuration and Control
Creates Network Components
Controls Operational Parameters

iMonitor
Async
y Reporting
p
g of Events,, Alarms,,

Warnings
Real-time and Historical Network
Data Access
“Network
Probe” for Detailed
Network Probe
Investigation
Remote Continuous Wave (CW)
carrier from Probe

iSite
Site Installation Tools
Direct Connection to a Modem
GUI Client
Cli t ffor iSCPC and
dN
Network
t
k
Accelerator
IOM - I Chapter 6 - NMS iBuilder

4


NMS Basic Features
Supports Thousands of Remotes Easily
Client-Server, 3-Tier Architecture
Modularity Flexibility
Modularity,

Flexibility, Simplify Maintenance

Windows Front-End
Familiar Look-and-Feel
Compatible
p
with Windows 2000 & XP

Linux Server Back-End
Performance, Stability, Maturity, Accessibility

SQL Database
Standard Database Storage System (MySQL)

Secure Access w/Individual User Logins with Privilege Levels
Virtual Network Operator
p
(VNO)
(
) Support
pp
(Licensed
(
Feature))
Customer Network Observer (CNO) Support (Licensed Feature)
Remote Access, Even Across Slow Links (i.e. dial-up modem)
SNMP Interface – Reporting
p
g Warnings
g & Alarms

VLAN Tagging (End-to-End)
IOM - I Chapter 6 - NMS iBuilder

5


NMS Architecture
Linux BackBack-End
Remot
e
User

Monitor,
Monitor
Report

Server
Suite

iMonitor

Configuration
Configuration,
Firmware Updates
NOC
Statio
n

Control

Config
Database

iBuilder
NOC
Statio
n

Monitor and
Control

Real-time
Archive

NetMode
m
Networks

Real-time
Network Data

Archive
Consolidation

iBuilder
iMonitor

IOM - I Chapter 6 - NMS iBuilder

6

NMS Revision Server (RevSvr)
Also known as the NMS Configuration & Upgrade Assistant
Revision Server provides the ability to upgrade firmware and/or
configurations automatically with minimal iBuilder interaction
Upgrade unreachable remotes later using Revision Server after normal
upgrade has completed
Apply multiple new configurations after modification automatically,
automatically and in
the background
Query Revision Server on upgrade status of remotes at anytime
Stop the Revision Server at any time
Upgrade multiple networks simultaneously

Revision Server was designed to make upgrades & configuration
changes simple & reliable for all sizes & types of iDS networks
Large networks make upgrade/downtime scheduling difficult
Many networks operate with itinerant terminals which can be expected to
be in-network
in network < 50 % of the time
IOM - I Chapter 6 - NMS iBuilder

7


NMS Revision Server (RevSvr)
NMS Revision Server – How it works . . . (Duty Cycle)
Revision Server sits idle, waiting for command input
Once initiated,

initiated the duty cycle continues until . . .
All assigned tasks are complete, or . . .
Command received from NMS to stop (via iBuilder user)

First, list of any down – rev
rev’d
d remote determined (after command input)
NMS tracks options file version & software/firmware versions separately
‘Down – rev’d’ remotes do not match NMS server version for one or both
RevServer then creates a single
g p
package
g containing
g required
q
image
g
package and/or options files for all down – rev’d remote
Package is then multicast to remotes using 10 % of Downstream channel
RevServer waits calculated amount of time for operation to complete
Remotes receive the package and process it, as always
Remotes pick out the images (if upgrading) and its own options file, writes to
flash & resets

RevServer repeats steps for all remaining remotes in list
If # down – rev’d remotes = 0, RevServer reverts to inactive (idle) mode
IOM - I Chapter 6 - NMS iBuilder

8

NMS Revision Server (RevSvr)
NMS Revision Server – Duty Cycle
Initialization
Complete

Startup
Begin

Startup
Sequence
GUI “Stop”
Command
Sleep for
Configurable
Minutes

Collect, archive ,&
report results

Inactive State
(Idle)

Nothing
to do

Then . . .

GUI “Start Commit”
Command

GUI “Start Upgrade”
Command

Determine list
of down – rev
remotes
Determine list
of Changes
Pending
remotes

Multicast
package at @
10% of
Downstream
data rate

Build mcast
package (s)

See Release 7.0 Features Document
for current RevServer NMS screens

IOM - I Chapter 6 - NMS iBuilder

9


NMS Revision Server (RevSvr)

NMS Revision Server – Using the Revision Server
Revision Server is used for Image Package and/or Options Files
downloads
Use it for either operation from any configured networks context menu
Launch for software/firmware upgrades with/without options files
Launch for options file only downloads (more frequent use)

Parameters are selected, specifying how the RevServer is to behave
RevServer visibility is provided, displaying steps taken by the server
Messages provided indicate remotes completed & removed from list

Upgrade in progress need not be observed; dialog box can be closed
iBuilder provides monitoring capabilities with Real-time & Historical logs
New tab appears with Network Tree labeled ‘Revision
Revision server’
server
All In Process operations are shown by default

Parameters dialog box can also provide visibility, if reopened
Cancelling an upgrade while in process is also on Parameters dialog box
IOM - I Chapter 6 - NMS iBuilder

10


iDirect’s Group QoS
What does GQoS do? . . .
Significantly Increases the Flexibility of Our Bandwidth
Management Capabilities
Offers Bandwidth Management Capabilities for:

Groups of Remotes
Groups of Applications
VLANs
And More

Significantly Different Paradigm than Traditional iDirect QoS
Advance planning required before migration to iDS Release, v8.0
Differences between iDirect’s GQoS & Traditional iDirect QoS may
result in an increased upgrade time requirement
Traditional iDirect QoS still used by iSCPC, point-to-point Networks
(Traditional QoS Traffic Profile now called iSCPC Profile)

IOM - I Chapter 6 - NMS iBuilder

11


iDirect’s Group QoS
GQoS Considerations . . .
Group QoS is both powerful yet complex
Efficient & accurate implementation of GQoS requires . . .
An in depth, working knowledge of your network & network elements
An understanding of all known network associated applications

Knowledge of all required bandwidth allocations is also needed
Detailed information regarding your end-user applications needs
to be collected & studied
Additional information required –
Bandwidth allocation strategy – by application or groups of remotes, etc.
B d idth sharing

Bandwidth
h i strategy
t t
att the
th remote,
t if applicable
li bl
Details to detect specific application – protocol, port, addresses, VLAN,
DSCP/TOS, bandwidth requirement, volume of such traffic
Understanding the behavior of current QoS rules – if upgrading
IOM - I Chapter 6 - NMS iBuilder

12


iDirect’s Group QoS
How Does GQoS Work? . . .
Group QoS Based on Hierarchical Bandwidth Model
Multi-Level Tree Structure

Operator Can Configure Each “Node” In the Tree with Bandwidth
Demand/Allocation Properties:
iDirect’s Group QoS Queuing decisions are based on several properties:
Maximum Info Rate ((MIR);
) strictlyy enforced in downstream side and somewhat relaxed
on the upstream side after fulfilling fairness. Rules are applied in the following order . . .
ƒ Priority (first level evaluation process for time slot allocation)
ƒ Cost Based Queuing (if nodes have equal priority, cost determines access)
ƒ Committed Information Rate (CIR) (minimums are satisfied first, when possible)
ƒ Best Effort Queuing (round robin

robin, contention based queuing – low level traffic)

iDirect Protocol Processor is Responsible for All Bandwidth
Management in iDirect Networks
Demand Requests are: . . . driven by Applications
. . . sent to & processed by a Centralized Bandwidth Manager
. . . evaluated on a frequent & periodic basis

Bandwidth Managers (sana/sada) Enforce the Rules for Allocation
Downstream
D
t
- sana
Inroute Group (aka Upstream) – sada
IOM - I Chapter 6 - NMS iBuilder

13


Group QoS Model
Bandwidth
Pool

BW Group
1

BW Group
2

Service

Group 1

Service
Group 2

Service
Group 3

Service
Group 4

Service
Group n

Applications

Applications

Applications

Applications

Applications

Default
Profile

Default
Profile

Default
Profile

Default
Profile

Remote
1

Special
Profile

Remote
2

Remote
3

Remote
ABC

Default
Profile

Special
Profile

Remote
XYZ

IOM - I Chapter 6 - NMS iBuilder

14


GQoS – Definitions
Terms

Definition

Bandwidth Pool

Physical Bandwidth Limit – Network/Outroute for Downstream, Inroute
Group for Upstream. Implicitly defined and not visible on iBuilder GQoS
C fi
Configuration.
ti
Bandwidth allocation decision point for Bandwidth Groups.

Bandwidth Group

Logically Allocated Bandwidth segment. Logical bandwidth aggregation
and distribution point for all Service Groups. Has priority, cost, MaxIR,
and CIR properties
properties. Bandwidth allocation decision point for Service
Groups.

Service Group

Collection of Applications from Application Profiles. Logical bandwidth

aggregation and distribution point for all applications in the group.
Bandwidth allocation decision point for Applications.
Applications

Applications a.k.a.
Application Group

Similar concept with Service Group, but a logical bandwidth aggregation
and distribution point per Virtual Remote. Has priority, cost, MaxIR, and
CIR properties. Bandwidth allocation decision point for Virtual Remotes.

S i P
Service
Profile
fil

NMS Concept
C
t with
ith selected
l t d Applications
A li ti
from
f
Applications
A li ti
Group
G
associated with physical remote.

Virtual Remote

Applications in the Service Profile associated with physical remote. Has
priority, cost, MaxIR, and CIR properties.

Application Profile

Defines traffic detection rules. Has priority and cost properties associated
with the traffic.
IOM - I Chapter 6 - NMS iBuilder

15


QoS & GQoS at a Glance
Features
Maximum IR
CIR / Trigger CIR
Minimum IR (Upstream)
SLA rule setting based on

Traditional QoS

Group QoS

Per remote

Tiered, App/BW-wise, per VR, per Remote

Per remote / Per Application

Tiered / all application (VR) triggers CIR

Per Remote

Per Remote (for extended burst plan)

Address/Network Range, Port numbers, VLAN, DSCP/TOS, Protocol

Multi-tier demand/allocation

Not Available

App, Svc Group, BW Group

S i P
Service
Profile
fil T
Template
l t

N t Available
Not
A il bl

T
Templates
l t can be
b saved

d & reused
d

Prioritization
BW allocation by group of remotes

Priority, Cost-based, Best Effort
Not Available

Available

BW allocation byy group
g p of apps
pp

Per Remote based,, Not strict

Per Service Group
p

BW allocation per application

Per Remote based, Not strict

Can be strict

Allocated per Remote as a whole

Allocated per Virtual Remote

Inroute BW allocation on time plan
BW allocation management

Hub-side (PPB) for both downstream and upstream

BW consumption management

Hub-side (PPB) and Remote’s
discretion

Hub-side (PPB) and Remote’s discretion
under PPB’s control

Segregation of Bandwidth on a
shared remote

Not Available

Available for up to
two Service Groups

Pre-iDS 8.0 and
on iDS 8.0 as iSCPC Profile

iDS 8.0 for Star/Mesh networks

Availability

IOM - I Chapter 6 - NMS iBuilder

16


GQoS Queuing Schemes – Priority Queues
GQoS Queuing Schemes – Management Traffic
Priority P1 Queues are auto created for NMS traffic to/from remotes
NMS Priority 1 – Traffic is minimal under steady
state operations
steady-state
NMS Traffic is greater during upgrades, configuration updates & other such routine
NMS operations
The default P1 NMS Queues are shown in the table below:
Direction

Traffic Types

Details

NMS_TCP

Upstream/Downstream

TCP traffic

Reliable options file and reset
operations

NMS ICMP
NMS_ICMP

Upstream/Downstream

ICMP traffic

Latency server measurement
operations

NMS_UDP

Upstream

UDP traffic

events, remote status
messages

The NMS Priority Queue may be modified, but it is not recommended
Important statistical information may be lost
Remotes may be reported as ‘Down’
Operational control could be affected/lost
IOM - I Chapter 6 - NMS iBuilder

17


iDS v 8.0 Network Topologies
Five Network Topologies

S

Upstream
Router

iMonitor
Upstream
m Subnet

NOC
Statio
n

Protocol
Processor

Remote 1

Remote 2

Tx Rx

Mesh
Links
Remote 3

iSCPC
Remote

NMS Server
iSCPC
Upstream

iSCPC
Remote

iBuilder
iMonitor

TDMA Upstreams

iSC
CPC

Remot
R
t
e
User

SCPC Downstream

Tunnel S
Subnet

Internet

Star networks, SCPC to TDMA
TRANSEC &
Spread Spectrum
Mesh networks, TDMA to TDMA
Options Supported
iSCPC networks,

networks SCPC to SCPC
TRANSEC networks, SCPC to TDMA
Spread Spectrum networks, SCPC to TDMA

iSCPC
Upstream

iSCPC link
(remote-to-remote
OR remote-to-HLC
OR HLC-to-HLC)

iSCPC
Downstream

iSCPC
D
Downstream
t
S

IOM - I Chapter 6 - NMS iBuilder

18


Gathering Statistics

Mesh Traffic Stats Collected Here

Remote 1

Upstream Router

Protocol
Processor

IP Traffic Stats Collected Here

Tunnel Lan Segment

Upstream
nt
m Lan Segmen

To Internett

NMS Monitoring of Networks

Remote 2

SAT Traffic Stats Collected Here
Remote 3

Mesh, SAT and IP Statistics collection
IOM - I Chapter 6 - NMS iBuilder

19

NMS Client Software Installation
Loading iDS Client Software Components
Download the latest nms_clients.zip from
TAC webpage (version dependent)
PC System Requirements
Windows NT, Windows 2000 or Windows XP
Windows 2000 Must have Service Pack 3
Windows 98/95 are Not Supported
Vista not officially supported, but seems okay

NMS Client – Load Software
Uncompress Files (Using WinZip, Pkzip, etc.)
Includes EDAS.zip file for addressing chassis
EDAS board (unzip & run Setup.exe to install
EDAS SysCheck 3.0)
3 0)
Run NMS Clients Setup.exe to Install NMS
Clients (GUI)
¾Creates Desktop
p Folder
¾Folder Contains Shortcut Icons
IOM - I Chapter 6 - NMS iBuilder

20


NMS iBuilder Client Software Login
‘Operator’ Login Information

admin/admin

(initial default)

‘select’ Server;
enter IP address

(Enlarged for viewing)

IOM - I Chapter 6 - NMS iBuilder

21


Accept/View Changes
No Pending
Changes

Main
Toolbar
“Tool”

Accept
Changes
“View”
Configuration
Changes

“Accept Changes” Icon Turns Red When Changes Have Been Made By
a Second Operator, via iBuilder Since Last Login
Click on This Red Icon to Open “Accept
Accept Changes”

Changes Dialog Box
Agree to “Accept Changes” to Refresh iBuilder Display Only
“Accepting Changes” does not confirm agreement or authorize changes
View current changes via “View Æ Configuration Changes” window
Without Accepting, Operator Display is ‘Stale’ and potentially inaccurate
Closing and re-opening iBuilder will refresh display and ‘accept changes’
IOM - I Chapter 6 - NMS iBuilder

22


iBuilder – Main Screen
Window Banner
Menu Bar

Min, Max, Close

Tool Bar

Open Window
Workspace

Component &
Subcomponent Folders

Network ‘Tree’

Status Bar

IOM - I Chapter 6 - NMS iBuilder

23


iBuilder – Main Screen/Tree View

Expandable/Contractible “Tree” View
Windows Standard “+” and “-” Controls View Detail
Displays NMS Configuration Reference Information
(Network Tree)
Single Click Right Mouse Button to Access
Single-Click
Component Pull-Down Menu for Possible Actions
(Add, Delete, Modify, Clone, View, etc.)

Provides One Entry Point for Configuration Data
“Configuration Status” for a Network Component
Can Be Toggled On/Off Via ‘View’ Menu Option

Network Tree

IOM - I Chapter 6 - NMS iBuilder

24


Configuration Status - “View” Menu

1
2

5

3
4

1. S
1
Select
l t Menu
M
Option
O ti
“View”,
“Vi ” “C
“Configuration
fi
ti
St
Status”,
t ” Et
Etc.
2. Tree Changes to Show the Current Status of All Components
™ “Nominal” Indicates Applied/Up to Date
™ “Changes Pending” Indicates Changes Made/Not Applied
™ “Never
“Ne e Applied” Indicates No Config.
Config from
f om NMS Applied
™ “Deactivated” Indicates Remote is Non-Operational

™ “Incomplete” Indicates Config. Record is Missing Detail
3. “View; Legend” Opens Status Legend for Reference
4 “View; Configuration Changes” Opens Table for Viewing
4.
5. “View; Details” Opens Configuration Detail for Reference
IOM - I Chapter 6 - NMS iBuilder

25