1 Module 6 TERAWAVE CONFIDENTIAL – DO NOT COPY Terawave Communications, Inc. Product Overview...

Module 6

TERAWAVE CONFIDENTIAL – DO NOT COPY

Terawave Communications, Inc.

Product Overview Course

Module 6 Craft NMS Interface

Terawave Management System (TMS) NMS Interface

Module 6

Objectives

Upon completion of this module you will: Know the two NMS interfaces supported Be familiar with the purpose, functions and capabilities of the Craft

interface Be familiar with the purpose, functions and capabilities of the

Terawave Management System(TMS) interface Be familiar with the capabilities to interface to other management

systems

Module 6

Contents

The Craft Interface - 4 Installation - 6 Security - 9 Browsing - 13 Alarm Management - 15

The Terawave Management System(TMS) - 18 Report generation - 38 External interfaces - 40 Command levels - 42 Network Auto-Discovery - 44 Software upgrades - 46 Alarm management - 49 Database management - 54 Database matching - 56 NE communication - 58 Connection provisioning - 60 Tests & diagnostics - 62

Module 6

TheCraft

Interface

Module 6

Craft Interface

Purpose

To allow Craftspersons access to individual Network Elements of the PON network for the purpose of: Network Element initialization Network Element hardware provisioning Diagnostics Performance monitoring Setting Threshold Crossing Alert levels

Module 6

Installation

Module 6

The Craft Interface

Hardware/Software Requirements

The Craft interface requires no special software. The actual interface code is part of the OLT and ONT Embedded code

Hardware Any laptop or desktop computer Ethernet connection 128M RAM minimum

Software Windows 95, 98, 2000 or NT Apple OS 9 or later Internet Explorer 5.5 or later Netscape Navigator 4.7

Module 6

The Craft Interface

Physical Connectivity Options

Direct connection

DCN connection

R RDCN

Network

Module 6

Security

Module 6

The Craft Interface

Security – Access Levels

Access capabilities based on ID Password Level (Type of function)

Multiple levels of access Public – Used by management workstations to access certain MIBs

for management purposes Viewer can:

• Only view information Tester can:

• Perform all physical layer tests

• All tasks that can be performed by the Viewer privileges

Module 6

The Craft Interface

Security – Access Levels

Multiple levels of access (Cont’d) Operator can:

• Provision or de-provision cards• Configure ports• Monitor statistics and alarms• Change Operator’s and Viewer’s password• All tasks that can be performed by the Tester and Viewer

privileges Administrator can:

• Create, modify or delete other user accounts for the NE• Zip an NE (wipe out an NE database)• Upgrade System software• Backup/restore configuration databases• Perform login override (in case another user is already logged in

to Craft)• All tasks that can be performed by the Operator, Tester and

Viewer privileges

Module 6

The Craft Interface

Security – Session Timeouts

Configurable on an ONT-by-ONT basis Accessed from the ONT or OLT Craft interface Settable from 30 to 3600 seconds (half minute to 1

hour) Default is 1200 seconds (20 minutes)

Module 6

Browsing

Module 6

The Craft Interface

Browsing

Browsing is the ability to logically access multiple NEs after physically logging in to one NE

From an NE, you can Browse to: An ONT

• On the same PON

• On a different PON An OLT

Browsing is unique to the Craft interface

Module 6

AlarmManagement

Module 6

The Craft Interface

Alarm Management

The Craft interface provides access to local alarm management functions Alarm Reporting Alarm Filtering Alarm Logs

Module 6

The Craft Interface

Login Screen

Module 6

TerawaveManagement

System(TMS)

Module 6

Terawave Management System (TMS)

Overview of TMS Standards it uses Connectivity Options Installation Requirements TMS Installation

Module 6

Definitions

Card A card is defined as an individual module that can be inserted into an

OLT or ONT

Network Element A Network Element is defined as a complete OLT or ONT. A Network

Element includes all the cards provisioned in the OLT or ONT

PON A PON is defined as the fiber that connects to a PCU in an OLT. A

PON also includes all the ONTs connected to that fiber

System A System is defined as an OLT, all the cards in the OLT, all the PONs

connected to the OLT and all the ONTs connected to those PONs

Module 6

Terawave Management System(TMS)

Purpose

TMS functionality includes: Provisioning Network Elements in the TMS database Provisioning hardware modules in the Network Elements Provisioning services Aggregating & displaying Alarms from Network Elements Resource aggregation – Enables viewing multiple NEs as a single unit

based upon a given set of requirements Alarm aggregation & viewing– Viewing alarms on all NEs from a

centralized platform Performance of diagnostics Setting Threshold Crossing Alert levels

TMS relies on the NE (INT, ONT or OLT) database as the database of record

Module 6

Overview

TMS Options TMS Server – GUI interface, SNMP based, Provider management

platform TMS Client – GUI interface, SNMP based, Provider management or

Customer monitoring/management platform

Supports up to 50 fully loaded OLTs (6,450 NEs) Simultaneous connectivity path to OSs/NMSs and NEs

over a DCN Maximum of 16 simultaneous OS/NMS connections Support existing DCN (X.25 and TCP/IP)

infrastructures

Module 6

Standards

SNMP based management for communication with Terawave equipment IETF Standards

• MIB II: RFC 1213• Medium Attachment Units MIB: RFC2668• Bridge MIB: RFC1493• 802.1q Bridge Table MIB based on IETF Draft draft-ietf-bridge-bridgemib-06

• DS1 MIB: RFC2495• DS3 MIB: RFC2496• AToM MIB: RFC2514, RFC 2515• RMON MIB: RFC1757• SONET/SDH MIB: RFC2558• RS232 communication MIB: RFC1659

ATM forum based standards• CES MIB based on af-vtoa-0078.000• ILMI MIB based on af-ilmi-0065.000

Module 6

Standards

HTTP based management for communication with Terawave equipment We use IETF standard described in RFC 2616

OMG CORBA standard We use OMG CORBA specification 2.2

JAVA 2 is used in TMS development for multi-platform support

XML specification 1.0 Servlet specification 2.2

Module 6

Implementation ArchitectureOSS OSS********

SQL orObject Oriented

DatabaseTMSServer

TMSGUI Client

LAN Hub

Local TW-600Craft Interface

Multiple IP Sessions

Local TW-300Craft Interface

Module 6

Installation Requirements

TMS has hardware and software “recommendations” TMS can operate on platforms less than the minimum

recommendations, but performance and response will be less than acceptable for a standard working environment

TMS is NOT supported on the Linux OS at this time The underlying TMS code is the same as Unix, but the scripting for

installation, startup and shutdown must be written for the Linux OS

Module 6

Installation Requirements, Hardware, Windows

Server Workstation Pentium 800MHz or better 256M RAM (w/o Oracle) 512M RAM (w/Oracle) 512M RAM (If Server and Client run on same computer) 2GB Hard Drive (5 TeraPON Systems) CD-ROM Ethernet NIC card

Client Workstation Pentium 500MHz or better 128M RAM CD-ROM Ethernet NIC card

Module 6

Installation Requirements, Hardware, UNIX

Server Workstation Sun Sparc Ultra 60 or higher 256M memory (RAM) 2GB Hard Drive (5 TeraPON Systems) CD-ROM Ethernet NIC card

Client Workstation/UNIX Sun Sparc Ultra 10 or better 128M Memory (RAM) 100MB hard disk space CD-ROM Ethernet NIC

Module 6

Installation Requirements, Software, Windows Server

TMS application Java runtime Environment (JRE) 1.2.2.008 Windows NT 4.0 (Service Pack 5) or Windows 2000 TCP/IP UNIX - Sun OS 5.8 (Solaris 2.8 or Solaris 8) Web Browser

Windows - Internet Explorer 5.5 or higher UNIX - Netscape Communicator 4.7 or higher

Module 6

Installation Requirements, Software, Windows Client

Windows NT 4.0 or greater OR Windows 95, 98, ME, 2000 or XP

TCP/IP Java Runtime Environment (JRE) 1.2.2.008 Web Browser – Internet Explorer 5.5 or higher

Module 6

Installation Requirements, Software, UNIX

Java Runtime Environment (JRE) 1.2.2.008 Server Workstation – UNIX

Sun OS 5.8 (Solaris 2.8 or Solaris 8)

Client Workstation/UNIX Sun OS 5.8 (Solaris 2.8 or Solaris 8)

Web Browser – Netscape Communicator 4.7 or higher

Module 6

Connectivity Options – Direct Connect, Single PCU

Direct 10bT LAN connection TMS Server can only be connected to a PCU module Craft/NMS port TMS Server communicates with ONTs through a dedicated

Embedded Operations Channel (EOC) PVC within the PON EOC can be 128Kbps-1.536Mbps TW-600

TMS™

Module 6

Connectivity Options – Direct Connect, Multiple PCUs

10bT LAN connection thru Hub TMS can always communicate with the network no matter

which PCU is Master

TW-600 PCU

TeraPONTM

Module 6

Connectivity Options – Indirect Connection

IP connection through router network Separate management DCN

Local TW-300 Craft Interface

LAN Hub

Local TW-600 Craft Interface

Management DCN

TMS Server

TMS GUI

Module 6

Connectivity Options – In-Band Management

A dedicated PVC transported within the NIM card Uplink OC-3c or OC-12c.

Module 6

Connectivity Options – ONT Craft Port

If direct connectivity to the OLT TMS/Craft port is not possible and an In-Band Management PVC is not an option, the OLT can be managed by the TMS Server connecting to the Craft port of an ONT connected to the OLT

Module 6

Database Management

TMS uses an ObjectStore database from Excelon Information stored includes:

Inventory (OLTs, ONTs, Slots, Cards, Ports) Connections/services EPS configuration PVCs BW groups

Module 6

ReportGeneration

Module 6

Report Generation

WITHOUT optional Oracle database connection: Inventory lists Bandwidth Usage

• ONT

• PON

• Uplink Service connection records Customer Name & Circuit ID

WITH optional Oracle database connection: Audit logs Performance Data storage

Module 6

ExternalInterfaces

Module 6

Interface to OSSs

CORBA A native CORBA interface for exporting information to a higher level

management platform is under study

TL1 Not supported at this time on the Terawave product line A requirement for a TL1 interface is under study

SNMP Terawave equipment incorporates standard v1 SNMP MIBS for Traps Terawave equipment incorporates standard v2 SNMP MIBS for

general use Terawave equipment can use SNMP to report Alarms and Threshold

Crossing alerts (TCAs) to a centralized SNMP based Network Management System

Full SNMP support for configuration and/or connection management from a centralized SNMP based Network Management System is under study

Module 6

Command Levels

Module 6

Command Levels

Port – Affects only a single port Card – Affects only a single card Network Element - Affects all elements of the same

type within the Network Element PON - Affects all elements of the same type within the

entire PON System – Affects all elements of the same type within

the entire system

Module 6

NetworkAuto-Discovery

Module 6

Network Auto-Discovery

Auto-Discovery takes place soon as you Register an OLT

TMS will Auto-Discover any Terawave network equipment already installed TMS must be able to communicate with the OLT Auto-Discovery includes

• OLT Configuration

• PONs

• ONT Configuration

• All service connections that have already been provisioned

Module 6

TMS SoftwareUpgrade Options

Module 6

Software Upgrades

Levels Of Upgrade

Card Allows software download only for a specific card on a specific

Network Element

Network Element Allows the option to download new software to the same type of card

on a specific Network Element. Multiple cards of the same type on a Network Element will be downloaded to at the same time

PON Allows the option to download new software to the same type of card

in EVERY Network Element in the APON

System Allows the option to download new software to the same type of card

in EVERY Network Element in the System

Module 6

Software Upgrades

Sources Of Upgrade

Local Local is defined as the CD Drive or Hard Drive of the TMS Server

workstation

Intranet Intranet is defined as a server located somewhere within the

corporate Intranet

Terawave FTP Site New versions of software are available from the Terawave FTP site

Module 6

TMS AlarmManagement

Module 6

Alarm Management

Alarms can be viewed on multiple levels ONT OLT System

• Includes OLT & ONT alarms

• Local Active

• History

• All Local Active

• Events

• TCA Events

• RMON Events Network

• Includes all Systems

Module 6

Alarm Management

Alarm management is performed on a System basis, administered by the OLT

Alarm management consists of two functions Alarm Reporting – What NMS workstations do you want information

reported to. IP address dependent

• Will report Alarms to 3 workstations

• TMS automatically uses one IP address Alarm Filtering – Severity of Alarms and what you want to do with the

Alarms

• Severity – Critical, Major, Minor, Informational

• Filter

– Ignore them

– Keep them local

– Report them to NMS workstations

Module 6

Alarm Management – Alarm Logs

Alarm Logs ONT

• All Local Active - Log• Local Active - Report• Local History• Events• TCA Events – Non-Ethernet events• RMON Events – Ethernet events

OLT• All Local Active - Log• Local Active - Report• System Active – Active alarms from OLT and all ONTs on all

PONs• Local History• Events• TCA Events• RMON Events

Module 6

Alarm Management – Alarm Logs

Alarm Logs TMS

• Network - Includes alarms/events from all Systems

– Active

– History

– Events

– TCA events

• Alarms/Events are stored in the TMS computer RAM. A computer restart or power failure will wipe out all Alarms and Events from TMS

• After a TMS restart, Active Alarms will be retrieved through the Synchronization process

• Short term Alarms/Events are stored in tomcat/webapps/EyeWave/db

Module 6

DatabaseManagement

Module 6

Database Management

Configuration Database Backup Can be done on multiple levels

• System

• Network Element

Configuration Database Restore Can be done on multiple levels

• System

• Network Element Must restart each Network Element that has had the database

restored

Module 6

DatabaseMatching

Module 6

TMS Database Matching

TMS to Network Elements

Network Element database always assumed to be most correct

Ability exists to “synchronize” the TMS configuration databases with the NE databases

“Synchronize” can be performed on multiple levels Network Element System

An Auto-Synchronize is performed by TMS with each NE once a day (around midnight)

Module 6

Network ElementCommunication

Module 6

“Keep-Alive” Signals

Periodic Keep-Alive Every two minutes a keep alive SNMP request message is sent from

the TMS to a NE that is provisioned in TMS The NE is expected to respond to the message. If no response is

received, 3 retries are done over a 7 second period. If all requests fail, then the lightning bolt is displayed

Normal Operation During normal user operation, if any SNMP request fails, 3 retries are

done over a 7 second period. If all requests fail, then the dagger would go through the NE

Module 6

ConnectionProvisioning

Module 6

Connection Provisioning

Connection provisioning can be done from Craft or TMS interface

Point-and-click, pull-down menus Keyboard action kept to a minimum

Module 6

Tests&

Diagnostics

Module 6

Tests & Diagnostics

Most testing and loopbacks can be done from TMS Local NE tests and diagnostics that require the NE to

be isolated from the PON can only be done from Craft

Module 6

Objectives

Revisited

Know the two NMS interfaces supported Be familiar with the purpose, functions and capabilities

of the Craft interface Be familiar with the purpose, functions and capabilities

of the Terawave Management System(TMS) interface Be familiar with the capabilities to interface to other

management systems

Module 6

Terawave Communications, Inc.Terawave Communications, Inc.

Lighting The First Mile™

1 Module 6 TERAWAVE CONFIDENTIAL – DO NOT COPY Terawave Communications, Inc. Product Overview...

Documents

Click here to start the show * 6 Day Schedule 6 Day Schedule * NMS Master Schedule NMS Master Schedule * Teams Teams * Lockers Lockers * After School

Bezirksmeisterschaft - nms-badvigaun.salzburg.at · 269 Pichler Hubert NMS Bad Vigaun 36 258 Schnaitmann Mathias NMS Adnet 37 250 Wallinger Philipp NMS Abtenau 38 255 Eder Markus

Cisco NMS Guide

NMS Physiology

Nms chapter 01

Xedge 6000 Version 6.2 - GDCgdc.com/gdceng/pubs/manuals/relnote/032r901_v621_02.pdf · ProSphere NMS Version 6.X User Manual ProSphere NMS Version 6.X Installation and Release Notes

Nms 9882 nms ppt

NMS v1-6 User-Guide En

NMS Best Practice

NMS DOcument

2 iDirect NMS iMonitor Module, V6.0, 080105-1

CMTS & NMS

Pasolink NMS

Version 1 - Induo AB -3AS NMS SATELLINE -3AS NMS Epic SATELLINE -3AS NMS 869 SATELLINE -3AS VHF Radio Data Modems USER GUIDE Version 1.0SATELLINE-3AS NMS / NMS Epic / NMS 869 / VHF

Philips NMS 1205 Music Module Expander V1E

Spleen NMS

NMS Connectivity Checking

Tutorial NMS

Pasolink NMS ENG

Predstavitev nms