NMS Projects and POCs completed and ongoing for OSS NAM v 1.5 Linkedin

1 Javier Guillermo - Copyright © 2015
PROJECTS AND POCS
LEADED AND COMPLETED

NEXT GENERATION CONTENT DELIVERY NETWORK
NG-CDN NMS POC

NG-CDN SUMMARY
A content delivery network or content distribution network (CDN) is a system of
computers containing copies of data placed at various nodes of a network. A CDN
can improve access to the data it caches by increasing access bandwidth and
redundancy and reducing access latency. Data content types often cached in CDNs
include web objects (text, graphics, URLs and scripts), downloadable objects
(media files, software, documents), applications, live streaming media, and database
queries.
The heart of the project and main Network Element (NE) is the Juniper Networks
Media Flow Controller (MFC) – a next generation content cache streamer designed
to address the converged, rich media demands required for CDN:
 Combines software extensibility with the ability to extract maximum performance from the
underlying hardware platform
 Multi-Protocol and mixed media support for today’s rich media applications
The NMS system used for the project is OpenNMS, OpenNMS is a free and open-
source enterprise grade network monitoring and network management platform. It is
developed and supported by a community of user and developers as well as by the
TheOpenNMS Group, offering commercial services, training and support

NG-CDN NMS OVERVIEW
NMS (Network Management System) refers to the activities, methods, procedures, and tools that pertain to the operation, admin istration,
maintenance, and provisioning of networked systems. common way of characterizing network management functions is FCAPS—Fault,
Configuration, Accounting, Performance and Security
 Fault Management: The goal of fault management is to recognize, isolate, correct and log faults that occur in the network. Furthermore,
it uses trend analysis to predict errors so that the network is always available. This can be established by monitoring different things for
abnormal behavior.
 Configuration Management, its main goals are: simplify configuration of network devices, configure and store configurations for Network
devices and tracking changes
 Accounting/Administration Management: Accounting is often referred to as billing management. The goal is to manage users and gather
usage statistics for users, some examples are disk usage, network utilization, etc…
 Performance Management: enables the manager to prepare the network for the future, as well as to determine the efficiency of the
current network, for example, in wireless networks you can measure dropped calls, in IP you can measure packages drop, Kbytes
transmitted, etc... The network performance addresses the throughput, percentage utilization, error rates and response times areas. By
collecting and analyzing performance data, the network health can be monitored. Trends can indicate capacity or reliability issues
before they become service affecting. Performance thresholds can be set in order to trigger an alarm.
 Security management: Security management is the process of controlling access to assets in the network. In a typical NMS system you
may have dozens of users with different profiles, for example someone responsible for configure a certain Network element class on a
certain area of the network should not be allowed, for security reasons, to modify the settings of other Network elements or the actual
Network Management system or database. Data security can be achieved mainly with authentication and encryption. Authorization to it
configured with OS and DBMS access control settings.
Note: We may see the terms EMS/NMS/OSS/BSS being used to refer to the same system and although there are similarities, they are not
exactly interchangeable. Typically, Element Management Systems (EMS) and Network Management Systems (NMS) perform FCAPS functions
of managing devices - i.e. hosts, switches, routers, etc. for things such as CPU utilization or availability. This info is generally aggregated
upwards to a Operational Support System (OSS) which may be geared to monitoring service or business functions that span multiple devices.
See following diagram that explain the different levels of Network Management, on this project the OSS system will be AT&T’s Vizgems that will
sit on the two higher level of the pyramid while the NMS/EMS side will be covered by OpenNMS/Junos Space.
Another subtle difference is that OSS is typically used more in the telecom space, outside of that space you may also hear the term MoM
(manager of managers) and SLM (Service Level Manager) for day-to-day operations.
BSS stands for Business Support Systems or Billing Support System - they typically interface with specific types of equipment/databases to
generate billing records, revenue and order management for charging customers for service and not for day-to-day operations.

Fault Management
Infrastructure
Configuration Management
& Service Design/Creation
Access Logs
Service
Provisioning
Billing
System
Performance Reports &
Analytics
NG-CDN NMS ARCHITECTURE
Junos Space Platform
SNMP
Alarms/Syslogs
Restful APIs
Media
Flow Activate
Customer
Portal
NOCPOPs/Devices
NMS SYSTEM:
OpenNMS
SLA
Monitoring
Usage &
Performance
Reports
OpenNMS
Stat.
Collector
Central
Logger
AT&T/IBM
SNMP Stats
Region BRegion A Region C
Device
Configuration
CSV files
MFC1..MFCnMFC1..MFCn
AT&T’s
VIZGEMS
Aggregation and
Correlation
Alarms
Reporting
Server
ORCHESTRATION
Data warehouse
Filtered/Correlated
SNMP
Events/Alarms
SNMP Stats
CMFM PM

HOW DO OPENNMS AND SPACE LOOK TOGETHER?
Note: OpenNMS was embedded into Junos Space after 11.4, that has OpenNMS 1.9.90.
The release to be used on AT&T will be 11.4P1.3, that upgraded OpenNMS to 1.9.94 that
contains the XML interface that was used to gather XML stats from MFC

HOW DOES IT LOOK AFTER THE IMPLEMENTATION?
These traps can later on be
forwarded to a MoM like
Netcool

MORE FM: SYSLOGS
Note: One of the project challenges was the format of the syslogs coming from the MFC.
Although Syslog is not a standard “per se”, most implementations follow the RFC5424 but
not MFC in versions 11 to 12.1 OpenNMS does have a parser that understands the basic
format described in RFC5424. The workaround was installing and using Syslog-ng and
creating the proper adaptation in OpenNMS though service configurator.

MORE FM: SYSLOGS – SPLUNK POC
Access Logs
Performance Reports
&
Analytics
Central
Logger
AT&T/IBM
SNMP Stats
data files
Data warehouse
Splunk is a tool to analyze any machine
generated data via a web interface, capable
of data correlation, data visualization
(graphs), alert and data export.

DROOLS – BRMS ENGINE
 BRMS or Business Rule Management System is a software used to
define, deploy, execute, monitor and maintain the variety and
complexity of decision logic that used by operational systems within an
organization or enterprise.
 Drools is a BRMS with a forward chaining inference based rules engine.
It is based on the RETE algorithm invented by Dr. Charles Forgy.
o Nodes are annotated when the fact matches a pattern
o When a fact (or combination of facts) causes all the patterns for a given rule to
be satisfied, the corresponding rule is triggered

DROOLS – BRMS ENGINE
A Production Rule is a two-part structure using First Order Logic for knowledge
representation.
when
 <conditions>
then
 <actions>

DROOLS CONFIGURATION – HOW DOES IT LOOKS LIKE?
This example is the rule number 4 on the previous page

NMS PERFORMANCE MANAGEMENT (PM)
The Juniper part for the project will be:
1) Collecting SNMP statistics from MFCs
2) Collecting XML stats from MFC (Under
development)
3) Convert the stats into CSV files that
will be pulled from the AT&T/IBM’s
central logger (Under development)
4) Thresholding (covered under the
previous drooling section) is also part of
PM

SMALL CELL
(FM-PM AND SI WITH NETCOOL)
PROJECTS AND POCS COMPLETED

AT&T’S SMALL CELL SUMMARY
AT&T is developing and deploying Small Cells (a.k.a Metrocells) - 3G (PMATT
#102918) and Multi-Standard (3G, 4G and Wi-Fi [PMATT #134692]) to improve
spectral efficiency and increase capacity and coverage of the mobility network
To support the Small Cell deployment, PMATT project 161626 (Juniper) was
created to develop a transport solution that included Routers, Switches, Time
Synchronization Devices (TCAs) as well as Network management system (NMS)
cluster. These Routes and Switches are referred to as Small Cell Router (SCR)
and Small Cell Switch (SCS). In current implementation, Small Cell traffic route
through the Public Internet to the National Technology Center (NTC) for initial set
up and to the Regional Technology Center (RTC) for bearer and signaling flow.
This backhaul architecture was sufficient to meet the time to market demand but it
is limited in bandwidth, introduces provisioning complexity and turn-up of the
service and in some cases is cost prohibitive. Therefore, a new architecture is
proposed which will utilize L2 Ethernet as a transport much like our current Macro
Cellsite deployments.
In phase 1 Layer-2 transport solution, small cell sites leverages existing backhaul
deployed for macro cell site. In later phase, dedicated backhaul for small cell over
L2 Ethernet infrastructure shall be developed.

NETWORK MANAGEMENT ARCHITECTURE FOR SMALL CELL
NML: Network
Management Layer
SML: Service
Management Layer
BML: Business
Management Layer
EML: Element Management Layer
NEL: Network element Layer
Manage the overall business, e.g.
market share, employee
satisfaction, achieving return of
investment
Manage the services offered to
the customers, for example: service
quality, time to market objectives,
achieving customer service level,
etc.. Manage the network and
systems that deliver those
services
Routers, Switches, Firewalls, BTS, MSC, etc…
Manage the elements
comprising the networks
and systems
Manage the overall business, e.g.
market share, employee
satisfaction, achieving return of
investment
OpenNMS/Space
AT&T’s CANOPI,
Vizgems, NETCOOL

AT&T SMALL CELL PHASE 1 (FM-PM COMPLETED)
We can see custom
made traps as well as
custom made
Thresholding/correlation
rules being forwarded to
Netcool
See below triggered
threshold examples
extending MIB
functionality

AT&T SMALL CELL PHASE 1 (CUSTOM MADE REPORTS)

PROJECTS AND POCS COMPLETED
BELL CANADA LWMoM– CPP

CUSTOMER PROBLEM 1/2
 Project originated in response to Bell’s RFP for Next Generation Carrier Ethernet (NGCE)
 Bell’s network was previously based on single vendor hardware and management solution
 New vendor’s solution required to inter-operate and co-exist with current network
Challenge:
Customer wanted to
keep using their
current Network
Management System
and procedures for
Juniper equipment,
minimizing the impact
on network operators
Alu 5620 SAM
(service aware manager)
Alu 7750
Routers
SNMP Traps
XML Config Files
NGCE
SAM Operator
Service
Activation/
Provisioning
Juniper MX
RoutersJuniper Core
Network
XML/CLI
telnet-SSH
SNMP Traps
XML/CLI
telnet-SSH

CUSTOMER PROBLEM 2/2
To handle management of new network elements, 3 architecture models
were discussed:
• Model 1: Separate network management and provisioning systems to
support Bell’s existing NGCE network and new network elements. This model
assumes that vendor’s network elements are managed independently from
the 7750 and service provisioning between the 2 hardware platforms is done
in 2 separate steps.
• Model 2: Integration of the vendor’s network elements into Alcatel-Lucent
5620 Service Aware Manager (SAM). In this model, Bell is interested to see
what capabilities the vendor supports for their network elements to be
managed via 5620 SAM and service provisioning to flow through SAM.
• Model 3: Manager of Manager Approach to Fault Management and a
Provisioning Mediator to interface to Vendor’s OSS/EMS and SAM. This
model assumes that a Manager of Managers (MoM) is required to facilitate
fault management and provisioning to SAM and the vendor’s OSS/EMS.

REFERENCE ARCHITECTURE 1/2
Initial approach was Model 2
Alu 5620 SAM
(service aware manager)
NOC Alarm
Banner
NetCool/OmniBus
Java Messaging
Service
Alu 5650 CPAM
(Control Plane Assurance Manager)
Webtop GUI Bell OSS
(Scripts, Tools)
Physical
Topology
LSP into
Alu 7750
Routers
SNMP Traps
XML Config Files
NGCE
BBNE Stats
Juniper MX
RoutersJuniper Core
Network
Challenge: Being
able to fully integrate
Juniper devices in Alu
5620 DB and being
able to use service
templates that will
configure the MX
devices.
SNMP Traps
SNMP Traps
Inventory CM/Service
Provisioning
Activation
SAM-o XML/SOAP
Netconf XML Config
Files/CLI
PM Data – SNMP
stats
JMS Connector
Bell’s NGCE OSS
EMC Smarts
SNMP Traps

REFERENCE ARCHITECTURE 2/2
Alu 7750
Routers
SNMP Traps
XML Config Files
NGCE
Juniper MX
RoutersJuniper Core
Network
SNMP Traps Inventory
CM/Service
Provisioning
Activation
Netconf XML Config
Files/CLI
PM Data – SNMP
stats
Bell NGCE
OSS
Model 3 was the
final model
agreed with
Customer
Challenge:
Same as in Model 2,
plus complexities of
integrating a
Manager of
Managers (MoM)
Network
Activate
Provisioning Mediator LWMoM - CPP
SAM-O XML/SOAP REST API
Service
Insight
Operator

DELIVERED SERVICES
 What services were delivered?
– Requirements gathering, architecture analysis and solution concept definition
– RFP response (NMS/OSS portion) and pre-sales support
– Solution creation (POC)
– Delivery of the POC on customer site
– Initial POC ATP (Model 2) in just 3 weeks
– Development of final agreed solution (LWMoM Model 3) is ongoing, POC presented
by Space BU
 Time frame
– Initial scoping started in Q3 2012
– First POC of model 2 was delivered at the end of Q4 2012
– Development of the final solution estimated completion date is 2H 2013
 Resources
– Customer Account Team
– 2 PS CoE solution architects
– 6-8 Space BU resources to develop LWMoM; a.k.a., Cross Provisioning Platform
(CPP)

INITIAL POC (CONFIGURATIO AUTOMATION THROUGH SAM) 1/2
The top figure
shows a VLL
activation between
an ALU router and
Juniper MX router
(on SAM is a
generic device)
The bottom figure
shows the SAM
service inventory
for this activation

INITIAL POC (CONFIGURATIO AUTOMATION THROUGH SAM) 2/2
This sample shows
changes in the
actual configuration
on the device

ANOTHER EXAMPLE: PROVISIONING A VLL SERVICE
Operator specifies the following:
 Name for the service - uniqueness enforced
 Description
 Type of the service - drop-down list of available service types
 VLL E-pipe, VLL A-pipe, VPN, etc…
 Customer - drop-down list of customers obtained from NA
 Two end-points. For each end-point,
 Router - drop-down list of PE routers obtained from NA and SAM
 UNI - drop-down list of valid physical interfaces on the selected router
 Outer VLAN Id - app can suggest an unused vlan for the selected UNI
 Description
 VC ID - app suggests an unused VCID between the selected PE pair.
Can be changed by operator
 Date and time for activation - or immediate
All values are validated by the app when operator clicks Create

VLL SERVICE TYPES
A VLL Service Type represents a particular service offering.
Each VLL Service Type is tied to:
 A Service Definition in Network Activate that embodies the
configuration required on MX for this service offering.
 This in turn is tied to a QoS Profile created using QoS Design
 Also may be tied to a Service Template created in Network Activate
 When the provisioning app invokes API on Network Activate, it refers to
this Service Definition.
 A template (or script) that embodies the configuration required on
ALU 7750 for this service offering.
 When the provisioning app invokes NBI on SAM, it should be able to
refer to this template/script

PROVISIONING A VLL SERVICE - GUI

VLL SERVICE TYPES - GUI
Provisioning app provides a workspace with a list of all available
service types.
Each service type has:
 A name
 Name of a Service Definition in Network Activate
 Name of a template/script in SAM

CREATING A NEW SERVICE TYPE
Workflow for creating a new service type:
 Create a new Service Definition in Network Activate
 May involve creating a QoS Profile and a Service Template that are
used by the Service Definition
 Create a new template/script in SAM (if not already existing)
 Provisioning app provides a GUI to create the new service type
 User selects the underlying Service Definition (from a drop-down)
 User enters the name of the template/script in SAM.
– It will be possible to present a drop-down if SAM NBI allows retrieval of this
information
 User provides a name for the new Service Type
Once created, the new service type will be available in the drop-
down list of service types presented by the Create VLL Service
GUI.

CREATING A NEW SERVICE TYPE - GUI

POC: BLINQ NLOS
INTEGRATION WITH JUNOS
SPACE FOR WINDMOBILE,
CERAGON AND AT&T
PROJECTS AND POCS ONGOING

SMALL CELL BACKHAUL – NEW PROBLEM,
NEW SOLUTION
 True NLOS
 Low TCO
 Reliable
 Predictable
 Quick Install
 Simple to
PLAN
 One HOP link
 4G Capacity
 Synchronizati
on
BLiNQ RI
Intelligent Radio Interface
Problem
Definition
BLiNQ’s Solution
Most flexible small cell backhaul at lowest total backhaul network cost
NetLiNQ
Deployment Assistant
Capacity Optimization
BLiNQ SDP
Scalable Delivery Platform

X-1200 SOLUTION
BLINQ 2ND GENERATION NLOS PRODUCT
Backbone of X-1200 Product Family is a dual carrier MIMO cognitive
radio architecture assisted by cost effective smart antenna systems.
 High capacity spectrum and flexible
solution to achieve lowest TCO
 Delivers high capacity up to 500 Mbps per sector 
1.5 Gbps per cell, future-proof for long term
 Highly effective spectrum usage of reuse of 1
 Exploits multipath utilizing smart antenna systems
 Provides quick installation and SON capability
 Technology is highly flexible& adaptable
 Architecture has great scalability and low cost per bit
 In coordination with NetLiNQ, X-1200 product family
can leverage various optimization tools for capacity
and true SON
APRBM
HUB
X-1200 combines reliability from licensed carrier
and capacity from unlicensed carrier resulting in
true carrier-grade NLOS backhaul.

BENEFITS OF A DUAL-CARRIER, LICENSED/UNLICENSED
NLOS BACKHAUL APPROACH
Carrier aggregation brings capacity increase with additional channel in
unlicensed band for offload
 Up to 500 Mbps peak capacity utilizing only 20 MHz of licensed or
lightly-licensed spectrum. High capacity using low cost spectrum.
Dual carriers provides redundancy and resiliency for carrier-grade
performance
 Licensed carrier as control channel provides reliable pipe in cases of
unlicensed band interference or avoidance intervals
A combination licensed/unlicensed product provides mechanism for
advanced scheduling
 Real-time traffic management ties traffic priority to appropriate radio
resource
APRBM
HUB
X-1200 combines reliability from licensed carrier
and capacity from unlicensed carrier resulting in
true carrier-grade NLOS backhaul.

BLINQ FM POC PHASE 1 COMPLETED
Traps have to be coded into
Space/OpenNMS o proper
alarms are displayed

CANOPI SYSTEM INTEGRATION (SI-CM) POC
CANOPI
stands for
Converged
AT&T
Network
Operation of
Provisioning
& Inventory

AT&T’s Automatic Configuration tool
PoC

Processes and Configuration Management
CM-Automation: What’s it all about?
› By incorporating automation into your
network operation you can:
› Increase staff efficiency and team
productivity will be focus on higher priority
issues.
› Delivering consistency services every
time.
› Reduce network downtime to a minimum.
› Exponentially multiply that productivity
over and above the benefits you gained
initially.
› Have peace of mind task are being
completed properly.
› Better operate existing network services.
› Enhancing configuration consistency
across multiple systems.
› Ability to define, build, orchestrate,
manage, and report on workflows that
support system and network operational
processes .
› Visibility and Reporting
› Automate error detection, diagnosis and
troubleshooting.
Patch Mgmt
Backup Handling
Automation
Validate Design
SW Deployment
Monitoring
Completion of SOW
Audit
Asset
Identification
Reporting
Automation Solution

Tools Set used for
Juniper PS Team
and customer to
support:
Configuration
Management,
Performance
Management, Fault
Management,
Network Audit and
Integration Projects
Routers
Switches
Cloud
Routers
Switches
Junos
OSS
XML
XML
CLI
CLI
XML
XML
INPUT DATA
Existing IP Network
OUTPUT DATADATA PROCESSING
Customer/Juniper IP Network Plans
(xls Data fills)
XML
XML
XML/SLAX Plans
(Router, Data Management.
IP Relations)
Create, Merge current IP Network
with Network Planning Data
XML
XML
XML/SLAX/CLI Plans
Operative & New Network
Upload
Download
Activate
DB
•Rollout.
•Scheduling
•Follow-up
•Reporting
CLI Plans (Packet Core,
Routing Checking)
Use Open source Tools
( Perl, Python,Tk, Shell,
MySQL, XML, SLAX etc)
Agile SW Management
IP Network
User and Customer
Satisfaction
Junos Space

CM CONFIGURATOR – POC
USING SPACE REST API WEB SERVICES
Junos Space
REST API
Services)
Data Dump in
XML or/and
Excel
Format.

NMS Projects and POCs completed and ongoing for OSS NAM v 1.5 Linkedin

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to NMS Projects and POCs completed and ongoing for OSS NAM v 1.5 Linkedin

Similar to NMS Projects and POCs completed and ongoing for OSS NAM v 1.5 Linkedin (20)

NMS Projects and POCs completed and ongoing for OSS NAM v 1.5 Linkedin