NMS ibuilder training guide v80

Command received from NMS to stop via iBuilder userFirst, list of any down – rev’d remote determined after command input First, list of any down rev d remote determined after command inp

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

i i f iDi t I

permission of iDirect, Inc

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 publication is provided by iDirect Technologies as-is without p p y g

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

consequential damages of any kind resulting from the 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 the information in this document

features to our products continuously, the information in this document

is subject to change without notice.

Familiarization with NMS GUI/Client

Modules 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 Network/Component Monitor and Status Reporting

NMS Primary Features

iBuilder

Configuration and Control

Creates Network Components

iMonitor

Async Reporting of Events, Alarms,

Controls Operational Parameters

Remote Continuous Wave (CW)

carrier from Probe

iSite

Site Installation Tools

Direct Connection to a Modem

GUI Cli t f iSCPC d N t k

GUI Client for iSCPC and Network

Accelerator

NMS Basic Features

Supports Thousands of Remotes Easily

Client-Server, 3-Tier Architecture

Modularity Flexibility Simplify Maintenance

Windows Front-End

Familiar Look-and-Feel

Compatible with Windows 2000 & XP p

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 (VNO) Support (Licensed Feature) p ( ) pp ( )

Customer Network Observer (CNO) Support (Licensed Feature)

Remote Access, Even Across Slow Links (i.e dial-up modem)

SNMP Interface – Reporting Warnings & Alarms p g g &

VLAN Tagging (End-to-End)

NMS Architecture

Linux Back Linux Back End End

Monitor, Report

User

iMonitor

Configuration, Firmware Updates

NetMode m Networks

Config Database

Real-time Archive

Monitor and Control

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

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 and in

Apply multiple new configurations after modification automatically , and in

the background

Query Revision Server on upgrade status of remotes at anytime

Stop the Revision Server at any time

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

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 < 50 % of the time

be in-network < 50 % of the time

NMS Revision Server (RevSvr)

NMS Revision Server – How it works (Duty Cycle)

Revision Server sits idle , waiting for command input

Once initiated the duty cycle continues until Once 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’d remote determined (after command input) First, list of any down rev 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 bothRevServer then creates a single package containing required image g p g g q 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 alwaysRemotes pick out the images (if upgrading) and its own options file, writes to flash & resets

RevServer repeats steps for all remaining remotes in list

RevServer repeats steps for all remaining remotes in list

If # down – rev’d remotes = 0, RevServer reverts to inactive (idle) mode

NMS Revision Server (RevSvr)

NMS Revision Server – Duty Cycle

Initialization Complete Startup

Startup Begin

Inactive State (Idle)

Startup Sequence Begin

Build mcast

Multicast package at @ 10% of Downstream data rate

remotes

Build mcast package (s)

data rate

See Release 7.0 Features Document for current RevServer NMS screens

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 serverMessages provided indicate remotes completed & removed from listMessages 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 server’

New tab appears with Network Tree labeled Revision serverAll 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 boxCancelling an upgrade while in process is also on Parameters dialog box

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)

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.

Bandwidth sharing strategy at the remote, if applicable 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 Understanding the behavior of current QoS rules – if upgrading

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); strictly enforced in downstream side and somewhat relaxed ( ) y

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 contention based queuing low level traffic)

ƒ Best Effort Queuing (round 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 - sanaInroute Group (aka Upstream) – sada

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 Default Special Default Default Default Special Profile Profile Profile Profile Profile Profile Profile

Remote Remote Remote Remote Remote

Remote

1

Remote 2

Remote 3

Remote ABC

Remote XYZ

GQoS – Definitions

Bandwidth Pool Physical Bandwidth Limit – Network/Outroute for Downstream, Inroute

Group for Upstream Implicitly defined and not visible on iBuilder GQoS

C fi ti Configuration.

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 Bandwidth allocation decision point for Service and CIR 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 Bandwidth allocation decision point for 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 fil NMS C t ith l t d A li ti f A li ti G

Service Profile NMS Concept with selected Applications from Applications Group

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.

QoS & GQoS at a Glance

Features Traditional QoS Group QoS

Maximum IR Per remote Tiered, App/BW-wise, per VR, per Remote CIR / Trigger CIR Per remote / Per Application Tiered / all application (VR) triggers CIR Minimum IR (Upstream) Per Remote Per Remote (for extended burst plan) SLA rule setting based on Address/Network Range, Port numbers, VLAN, DSCP/TOS, Protocol

Multi-tier demand/allocation Not Available App, Svc Group, BW Group

Service Profile Template Not Available Templates can be saved & reused

Prioritization Priority, Cost-based, Best Effort

BW allocation by group of remotes Not Available Available

BW allocation by group of apps y g p pp Per Remote based, Not strict , Per Service Group p

BW allocation per application Per Remote based, Not strict Can be strict

Inroute BW allocation on time plan Allocated per Remote as a whole Allocated per Virtual Remote

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 Availability Pre-iDS 8.0 and

on iDS 8.0 as iSCPC Profile

iDS 8.0 for Star/Mesh networks

GQoS Queuing Schemes – Priority Queues

Priority P1 Queues are auto created for NMS traffic to/from remotes

NMS Priority 1 – Traffic is minimal under steady-state operations

GQoS Queuing Schemes – Management Traffic

NMS Priority 1 Traffic is minimal under steady state operationsNMS 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 Upstream/Downstream ICMP traffic Latency server measurement

NMS_ICMP Upstream/Downstream ICMP traffic Latency server measurement

operations NMS_UDP Upstream UDP traffic events, remote status

messages

Important statistical information may be lostRemotes may be reported as ‘Down’

Operational control could be affected/lost

iDS v 8.0 Network Topologies

SCPC Downstream

S

Five Network Topologies

Star networks, SCPC to TDMA

Mesh networks, TDMA to TDMA

iSCPC networks SCPC to SCPC

TRANSEC &

Spread Spectrum Options Supported

TRANSEC networks, SCPC to TDMA

Spread Spectrum networks, SCPC to TDMA

Mesh Links

Remot e User

NOC Statio n

iSCPC

Downstream

iSCPC Upstream iSCPC

iSCPC link (remote-to-remote

OR remote-to-HLC

ORHLC-to-HLC)

iBuilder iMonitor

Downstream

S

Downstream iSCPC

Upstream

SAT Traffic Stats Collected Here

IP Traffic Stats Collected Here

Mesh, SAT and IP Statistics collection

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 XPWindows 2000 Must have Service Pack 3Windows 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)

Run NMS Clients Setup.exe to Install NMS Clients (GUI)

¾Creates Desktop Folderp

¾Folder Contains Shortcut Icons

NMS iBuilder Client Software Login

‘Operator’ Login Information

admin/admin (initial default)

‘select’ Server; enter IP address

(Enlarged for viewing)

enter IP address

(Enlarged for viewing)