Sot Monitoring A

e d u ca t io n se rv ice s co u rsew a re
ROUTER INTEGRATED MONITORING SOLUTIONS
Student Guide
Router Integrated Monitoring Solutions
Slide 1
2011 Juniper Networks, Inc. All rights reserved. | www.juniper.net | Proprietary and Confidential
Welcome to the Juniper Networks Router-integrated Monitoring Solutions eLearning module.
SOT-MONITORING-A
Juniper Networks, Inc.
Slide 2
2011 Juniper Networks, Inc. All rights reserved.
CONFIDENTIAL
SOT-MONITORING-A
www.juniper.net | 2
Throughout this module, you will find slides with valuable detailed information. You can stop any slide with the Pause button to study the details. You can also read the notes by using the Notes tab. You can click the Feedback link at anytime to submit suggestions or corrections directly to the Juniper Networks eLearning team.
SOT-MONITORING-A
Slide 3
Course Objectives
After successfully completing this course, you will be able to discuss:
Router Services Product Portfolio StreamScope ERM Telchemy ePM Complimentary monitoring portfolio Triple Play monitoring Framework
CONFIDENTIAL
SOT-MONITORING-A
www.juniper.net | 3
After successfully completing this course, you will be able to discuss: Router Services Product Portfolio StreamScope ERM Telchemy ePM Complimentary monitoring portfolio, and Triple Play monitoring framework.
SOT-MONITORING-A
Slide 4
Router Services Product Portfolio

Router Services
Subscriber and Application Aware products
Innovation Ecosystem
StreamScope eRM Video Analysis TePM VoIP and IP Analysis
Security and NAT products
IMS / Voice and Layer 2 products
Media Enabler Online Advertising and virtually limitless possibilities
Monitoring products
Router-integrated applications extend investment protection, better monetize traffic and assets and improve operations
CONFIDENTIAL
SOT-MONITORING-A
www.juniper.net | 4
The Juniper Router Services Product Portfolio consists of several product lines. These include the Subscriber and Application Aware product line, the Security and Network Address Translation (or NAT) product line, IP Multimedia Subsystem (or IMS) Voice and Layer 2 Product lines, and Junipers Monitoring Products. Juniper also uniquely maintains an Innovation Ecosystem. This Ecosystem permits partners to use the Junos SDK (software development kit) to integrate their advanced applications with Junos and with Junos-based platforms. By integrating advanced applications with the router, Juniper can allow its customers to protect their investment in their infrastructure, better monetize their traffic and assets, and improve their operational environment.
SOT-MONITORING-A
Slide 5
Monitoring Services Product Line

StreamScope eRM
Router-integrated MPEG monitoring analysis developed by Triveni Digital and
Telchemy ePM
Router-integrated multi-layer VoIP and IP service monitoring, developed by Telchemy
J-Flow Active and Passive Monitoring

Router integrated flow monitoring transparently collects flow statistics
Lawful Intercept
Router integrated support flow replication and forwarding to mediation platforms
CONFIDENTIAL
SOT-MONITORING-A
www.juniper.net | 5
This slide presents Junipers Monitoring Services Product line. StreamScope eRM is a router integrated video monitoring and analysis application that was developed by Juniper partner, Triveni Digital. Telchemy ePM is a router-integrated VoIP and IP service monitoring product. It was developed by Juniper partner, Telchemy Incorporated. There is also J-Flow, which is an inherently supported monitoring functionality. Finally, there is lawful intercept which is the router-integrated ability to support flow replication and forwarding to lawful intercept platforms.
SOT-MONITORING-A
Slide 6
True Network - Application Integration

T1600 T640
Partner Applications
MS-PIC
MX960 MX480 MX240
Junos SDK
MS-DPC
M320 M120 M10i

MS-PIC
Juniper Applications
M7i
CONFIDENTIAL
SOT-MONITORING-A
www.juniper.net | 6
This slide is a high-level capture of how partner applications can be integrated with Junos via the Junos SDK, or how Juniper applications can be directly integrated with Junos and hosted on Juniper service parts, including the MS-PIC or MS-DPC, and ultimately deployed on a variety of Junipers routing platforms. Not all applications can be hosted on all of the routing platforms today.
SOT-MONITORING-A
Slide 7
Managing Video Service Quality Is Challenging

Video over IP is a layered distribution model
Video encoded in MPEG frames MPEG encoded in IP packets IP packets transported over network
MPEG MPEG MPEG
IP Packet
MPEG MPEG MPEG MPEG
Fault identification and Isolation is difficult

Problems can crop up in IP or MPEG layer Problems can occur concurrently Problems can be symptoms ofor mask problems in the same or other layers
CONFIDENTIAL
SOT-MONITORING-A
www.juniper.net | 7
This slide presents some of the challenges associated with managing video service quality and shows a very simple diagram of how video is delivered over IP. The video itself is encoded into MPEG frames. These are compressed and encapsulated in IP Packets. The IP Packets are then transported over the network infrastructure. This is a layered distribution model, and with a layered model, there are many challenges in doing fault identification and fault isolation. The reason is that problems can occur in any of the layers. There can be problems occurring concurrently in different layers and there may be product problems in one layer that are a symptom of, or even mask, problems in another layer. So getting to the heart of the matter what is the fault that is occurring and the impairment and how to correct it can be challenging. Of course, these issues are typically customer-facing. So they impact the video experience and the service provider is going to be getting phone calls, dissatisfied customers, potentially lost subscribers, or even a tarnished image, if they cant rapidly identify and stay ahead of these problems and rapidly fix these issues. Thus, a comprehensive set of monitoring tools is necessary to maintain customer satisfaction and video quality.
SOT-MONITORING-A
Slide 8
Introducing StreamScope ERM

Router-integrated video monitoring and analysis (MPEG, MDI) Supported on MX Series Universal Edge Router family today Based on 12 years of DTV expertise from partner Triveni Digital Continuously monitors video for compliance with 200+ rule sets Full suite of management options
CONFIDENTIAL
SOT-MONITORING-A
www.juniper.net | 8
Rapid fault identification and isolation is where StreamScope eRM comes into the picture. This is a router-integrated video monitoring and analysis application. It does multi-layer monitoring and analysis, both at the MPEG and MDI (medium-dependent interface) layers. It is supported on the Juniper Networks MX Series 3D Universal Edge Routers, and is available today. It is based on 12 years of video expertise from Juniper partner, Triveni Digital. Video is the only thing that Triveni Digital focuses on, and so Juniper gains all of their expertise and brings a very mature and sophisticated product into Junipers portfolio by establishing this partnership. StreamScope eRM will continuously monitor video streams for compliance with 200 plus rule sets. Theres also a full suite of management options available to Juniper customers.
SOT-MONITORING-A
Slide 9
How StreamScope eRM Works

IP Flow carrying MPEG encoded video stream Live flow continues unimpeded, copied flow sent to the MS-DPC
StreamScope eRM StreamScope eRM provides MDI and MPEG analysis
Alarms and events can be integrated with NMS/OSS via open interfaces and SNMP
Operator selects flows for monitoring and selects rules that will be analyzed. Alarms are generated when problems occur
Technicians can be proactively alerted
CONFIDENTIAL
SOT-MONITORING-A
www.juniper.net | 9
This simplified diagram explains how StreamScope eRM works. The blue arrow represents an IP flow. It goes from left to right across the screen. There would be many IP packets within that flow and within the IP packets, there would be MPEG frames. The MPEG frames are represented by the white rectangles within the arrow. They traverse the MX Series platform and the StreamScope application is indicated by the magnifying glass icon. There is a Network Operator at the bottom of the screen and there is an NMS (network management system) or OSS (operations support system) represented by the server and cache on the right hand side of the screen. First, the Operator selects what flow to analyze and that command is passed to the system, which copies and redirects MPEG frames and IP packets from the regular flow to the StreamScope eRM which is hosted on an MS-DPC. Analysis is performed on the copied flow and frames, not on the live stream. This means that there is no disruption or added delay or latency to any of the traffic as it traverses the network. It is non-service affecting since the analysis is done on the copied stream. If StreamScope identifies any issues it reports them back to the Operator. It reports events that occur within standard levels and within the Service Providers defined area of tolerance. Events outside this tolerance level or interval, generate alarms. The interface is very customizable and there are many default settings out of the box. Up to 200 rules can implemented and each of those rules can be applied to any of the streams to be monitored. Technicians can be proactively alerted by several means, including SMS messages, e-mails and phone calls, with a code identifying a particular problem. Alarms and events can be easily integrated with the NMS and OSS via open interfaces or via SNMP. If the Juniper router is already integrated with the NMS and OSS, then it is a question of passing more information along that existing integration effort. It is a lot easier to integrate than it would be if there was a separate appliance running a different OS that wasnt integrated already into the NMS or OSS.
SOT-MONITORING-A
10
Slide 10
Management Options
Command Line Interface
Web-based User Interface
SNMP Traps and Alerts
CONFIDENTIAL
SOT-MONITORING-A
www.juniper.net | 10
There are different management options that the network operations team can elect to use with StreamScope eRM. First, the Junos CLI (Command Line Interface) can be used. This is particularly important for installation and for troubleshooting, updating and maintaining the application itself so there is nothing new for the Operator to learn. Then, there is a Web-based user interface, which is an application built into the product and is very intuitive and easy to use. It is simple to configure and set up the streams and apply the rules to the streams, which are then shown in a chosen sampling period. If any alarms occur during that period, it identifies the degree of severity. It helps with fault isolation by indicating what standard is being violated and the severity of the violation so that a route cause analysis on the problem can be obtained. Lastly there is the raw output of SNMP traps and alerts, which can help with a longer term trend analysis.
SOT-MONITORING-A
11
Slide 11
Key StreamScope Positioning Messages

Deployment Flexibility
Easily deployed anywhere there is an MX 3Ddata-center to network edgecreating a comprehensive monitoring environment
Avoids Appliance Proliferation

Avoid qualifying, deploying, managing and maintaining appliances
Investment Protection / Contains CapEx and OpEx

Video flows on any MX interfacefrom 1G to 100Gcan be monitored MX3D and StreamScope eRM can be managed using Junos CLI and same commands
Juniper Sales and Support

Sold and supported via the same processes as all Juniper products.
CONFIDENTIAL
SOT-MONITORING-A
This slide presents some of the key values of SteamScope. First, it is flexible and easy to deploy. It can be installed anywhere there is a Juniper Networks MX Series router: in the data center, next to the video source equipment, at the network edge, before the video streams are turned over to the Layer 2 network and ultimately to the customer and anywhere in between. It helps create a comprehensive monitoring environment while avoiding appliance proliferation. The standard mechanism for video monitoring is to have a standalone appliance and insert it into the network at different points. This presents large capital expenditure and operation expenditure burdens for customers, and adds a high degree of complexity to network design. Service providers are experiencing ever increasing volumes of video traffic, and planning their monitoring environment to accommodate that high bandwidth, high capacity video traffic can be a daunting task, particularly considering the number of appliances needed to manage that environment. By integrating it with routers that already make up the network infrastructure, Juniper helps avoid that problem. This allows customers to protect their investment in the MX Series router and in their infrastructure.
SOT-MONITORING-A
12
Slide 12
Objection Handling
We dont need MPEG analysis, MDI is all that is needed!
Response: While MDI is critical for assessing network layer impacts, it doesnt identify customer impacting MPEG layer issues. MPEG analysis is a critically important at points where video is injected or processed.
We deploy monitoring on service specific equipment!

Response: Network consolidation like integrating video monitoring with routers offers cost controls. Juniper has been careful to provide dedicated and protected resources for each router function and service, so that performance and reliability are maintained even at peak load.
This is too expensive!

Response: Have you considered the TCO of qualifying, implementing, managing and maintaining appliances, given video growth rate?
CONFIDENTIAL
SOT-MONITORING-A
This slide presents some common objections that customers put forward. First, the network operator often states that there is no need to do MPEG analysis. Either that comes with their MPEG encoding equipment or it is outside of their domain and all they need is MDI, or the Media Delivery Index. This is the IP layer of performance monitoring that captures parameters such as jitter and delay so that the impact of video on those network layer issues can be understood. The response to this objection is that MDI is absolutely critical to network layer impact and that Juniper does not discount its importance. However, it doesnt help a customer identify MPEG layer issues. Typically, the MPEG encoding device is at a single point in the network and is more of an encoding device than an MPEG monitor, so it doesnt have the feature set of a true monitoring device. Furthermore, in this multi layered distribution system that is video over IP, it is recognized that a problem in an IP layer can mask an MPEG layer, or multiple MPEG layer problems which can be occurring and impacting video service quality. The ability to rapidly identify and isolate those issues is absolutely critical. Another objection is that dedicated equipment is used for monitoring services. Junipers solution decouples the interface from the monitor. Any Ethernet interface on the MX Series can be used to monitor video traffic, as long as the video flow is coming in over that interface, it can be copied, and the copy can be redirected to the MS-DPC for analysis. What the customer already has does not have to be removed, but as video traffic continues to increase, Juniper can help the customer stay ahead of the spending curve by integrating some of the monitoring onto the router environment. In response to the objection of cost, appliances are comparatively cheap, however, the cost of maintaining the scale-all of those appliances, qualifying them and upgrading them and doing the rip out and reinstall of a higher bandwidth or reinstall of a higher capacity device, is expensive from a TCO point of view.
SOT-MONITORING-A
13
Slide 13
Performance Considerations
Passive monitoring no delay or jitter introduced to live traffic Restricted to one CPU on MS-DPC only other CPU cant be used (for StreamScope eRM or any other application Monitors up to ~1.5Gbps of video traffic
~ 700 SDTV streams or ~200 HDTV streams concurrently HDTV and SDTV can be mixed without restriction MPEG2 and MPEG4 streams can be mixed without restriction
No performance impact related to number of rules in effect per stream all 200 + rules can be applied per monitored stream
CONFIDENTIAL
SOT-MONITORING-A
This slide presents some topics to consider when discussing performance. Juniper monitors copied streams, so even though deep MPEG analysis is being performed with up to 200 rule sets per flow, no delay or jitter is introduced into the live traffic. Therefore, the customer experience is not impacted in any way. Today, StreamScope ePM is restricted to running on a single CPU on the MS-DCP; the other CPU cannot be used for StreamScope or other applications. Presently, Juniper has the capacity to monitor up to about 1.5 Gbps of video traffic. This represents about 700 SDTV streams or about 200 HDTV streams concurrently. It is possible to have all of the rules on all of the streams up to maximum system capacity without any impact to the viewer experience or to the video performance. HDTV and SDTV can be mixed and matched without restriction, as well as MPEG2 and MPEG4.
SOT-MONITORING-A
14
Slide 14
StreamScope eRM Summary

Most comprehensive solution
Identify / isolate issues at multiple layers Monitor for 200+ rule sets
High availability, performance and scale

Leverages resiliency MX platform Separate control, forwarding and service planes Pay as you grow: low risk investment protection
Optimized Cost
Consolidationgreen dividend, less real-estate, less complexity Same inventoryMS-DPC for any service (also future-proof)
CONFIDENTIAL
SOT-MONITORING-A
In summary, StreamScope ERM is a solution for identifying and isolating issues at multiple layers within an IP stream. There is a comprehensive rule set and deep analysis of the underlying issues and performance associated with video distribution over IP. All the advantages of the MX Series are extended to StreamScope eRM, so all the resiliency, scale and performance that is expected of the MX is obtained when integrating Junos and the MX with a third party application like StreamScope. This solution provides architectural integrity, with separation of control plane, forwarding plane, and service plane. This ensures that primarily there is a routing platform, and in this case a monitoring application is added, with no functionality removed from the routing functions or control plane functions to support the value added service of monitoring. Each service has its own resources which are protected, therefore performance and reliability remain high. Also, the solution presents a low risk and investment protecting approach. Customers are adding to a platform that has been well proven within their network, is already in line with all the video flows over the network, and can easily scale by purchasing more licenses or more MS-DPCs as needed. They are able to consolidate functions of monitoring appliances with a very powerful routing platform. It occupies less real estate, there is less design complexity, less interfaces consumed, and can use the MS-DPC for different applications; not just StreamScope eRM, but NAT, firewall, SBC (session border controller), Deep Inspection and many other capabilities.
SOT-MONITORING-A
15
Slide 15
Introducing Telchemy ePM

Router-integrated VoIP and IP monitoring and analysis that monitors performance from the users' perspective Incorporates 11+ years of monitoring expertise from partner Telchemy Active monitoring for preand post deployment operations Supported on M Series and MX Series platforms today
Product portfolio addresses the service monitoring requirements of service providers and major enterprises
CONFIDENTIAL
SOT-MONITORING-A
Telchemy ePM provides a comprehensive router integrated VoIP (voice-over IP) and IP monitoring and analysis solution. It provides metrics that show the performance from the users perspective, in terms of voice quality and what the user would experience in using the service as opposed to a more Service Provider-centric look at errors or conditions that could exist. Juniper builds on over 11 years of experience from Telchemy. The product is well proven and deployed globally in some of the largest networks in the world and with some of the most widely used equipment types. It has a lot of pre- and post-deployment capabilities, so it is designed for many use cases and applications. It is supported on both the Juniper Networks M Series the 7i, 10i, 120, and 320 as well as the MX Series the 960, 480 and 240.
SOT-MONITORING-A
16
Slide 16
How Telchemy ePM (TePM) Works

A Centralized Controller software runs on workstation to configure and control agent tests and report real time test results Results are visualized by test and path Web services API for integration with other applications
TePM Controller Export data to NMS/OSS via SOAP/XML RPC
Operator:
Customize test plans Drag and drop test plans Start/stop tests Test results reported back to Controller
OSS / NMS
TePM Agent enabled element SIP device
Distributed Agents run on service cards and offer multiple concurrent active voice, network and application tests
VoIP calls with SIP, RTP, voice payloads Network app tests (DHCP, DNS, Web.) IP troubleshooting tests
M or MX Series Router
TePM Agent
TWAMP capable device IP addressable device
CONFIDENTIAL
SOT-MONITORING-A
There are two main components to TePM. There is a controller, which is centralized and allows an Operator to do test plan customization, to initiate, and end-test, and to analyze the results of those tests. There are also distributed agents. These are the software elements that conduct the test and they are deployed on the M or MX Series on MS-DPCs or MS-PICs. There can be one agent that runs multiple concurrent tests and the tests can be at several different layers. They test at the service layer for SIP or VoIP testing, at the network layer as well as at the IP layer. There are also multi-layered tests. Communication can occur with other Telchemy enabled applications that are running on third party devices. End user devices like SIP devices or VoIP phones can also be reached as well as other TWAMP-capable devices (Two Way Active Monitoring Protocol) and tests can be run between them. Any IP addressable device can be reached and a ping test or a trace route or even path tests to these types of devices can be run.
SOT-MONITORING-A
17
Slide 17
Simplified and Intuitive Test Environment

Simple GUI configures tests and visualizes test results Includes config wizard Use with any platform running Java v1.5 higher
Test Points
Path Statistics
Test Plans
Dashboard
Test Results
Controller View
CONFIDENTIAL
SOT-MONITORING-A
This slide presents the one screen view of everything that an operator needs with the simple GUI that allows him to identify test points, create test plans, start/stop tests, identify the statistics that are critical, whether doing a voice layer test or an IP layer test or a network layer test. Optionally, he can look at the service end-to-end across the path and obtain an aggregate quality look at all the layers as the path is traversed. All the results are in detail and can be expanded as necessary. The tests can be scheduled for a certain time, they can recur, or one time ad hoc tests can be performed. Tests that mirror the service requirements that will be deployed in the future can be created, and then run so that some stress can be put on network links to see how the network impacts the service before deploying it. It can help with service rollout before getting into the rollout, as well as for capacity planning.
SOT-MONITORING-A
18
Slide 18
Comprehensive Diagnostic Testing

Path tests
tests IP path to any given IP addressable device.
Hop-by-hop tests
available bandwidth, congestion, duplex mismatch, packet loss , firewall
Network application tests

Synthetic transactions for DHCP, DNS, HTTP, POP, DHCP, SMTP, TWAMP
Reports performance at each layer

IP, TCP/UDP, service, transaction
TePM Controller
Server
End test point Intermediate test point
M or MX with TePM Agent
CONFIDENTIAL
SOT-MONITORING-A
This slide presents a high level view of the IP layer and network layer diagnostic test that can be performed. The path test can be done end-to-end or on a hop-by-hop basis. Synthetic transactions can be created and initiated on the network between devices and the performance of those applications can be observed and the reports can be generated for every layer involved in the communication. In the example on the slide, the test is initiated on an agent that is running on the M or MX Series router, hosted on an MS-PIC or MS-DPC. A number of weigh points have been identified, whether they are switches or routers. This represents a hop-by-hop test. There is an end-point identified: the server. Once the test is initiated and run for some period of time, or one time, the information is then gathered on the Controller dashboard for analysis.
SOT-MONITORING-A
19
Slide 19
Comprehensive VoIP Diagnostic Tests

SIP Call with RTP, RTCP SR/RR/XR Selectable codec, voice payloads, narrowband and wideband Selectable packet size and spacing; separate ToS class for signaling, media; Multiple concurrent calls to multiple destinations MOS scores, R factors and wide range of IP metrics
Bidirectional metrics reported (if remote endpoint supports RTCP XR)
SIP Phone Element w/ TePM Agent
End test point Intermediate test point
TePM Controller
M or MX with TePM Agent
CONFIDENTIAL
SOT-MONITORING-A
This slide presents more about VoIP and the wide selection of different payloads and delivering mechanisms, packet sizing, and spacing, that exist. The test case can be fine tuned to mirror what is being seen in the network or what should be deployed in the network. Multiple calls can be conducted concurrently to multiple destinations. The TePM can set up a test where a SIP phone is called and the quality to the phone is analyzed. For service providers that have a persistent problem that they are having trouble identifying or troubleshooting, they can use this tool to troubleshoot to the end device in real time. They can troubleshoot deep into the network, analyze intermediate test points as well as end points, whether they are end devices or third party devices that support an IP address. They can obtain MOS scores (Mean Opinion Scores), which give an approximation of quality from the subscribers perspective.
SOT-MONITORING-A
20
Slide 20
Detailed Voice Quality (MOS) Metrics

Highlights include
MOS-LQ, MOS-CQ Modem/Fax performance Packet loss / discard rate Burst (loss / discard) length and density (RFC3611) Gap (loss/ discard) length and density (RFC3611) IP network round trip delay, end system delay and symmetric one way delay PPDV (RFC3550) and MAPDV jitter (ITU-T G.1020) Out-of-sequence and duplicate packets Route taken by call
CONFIDENTIAL
SOT-MONITORING-A
This slide presents the MOS scores that a service Provider would analyze. It indicates the quality and reliability of the connection and provides many other metrics that a technician could use to ensure that steps are taken to improve quality or that the quality is within the desired range.
SOT-MONITORING-A
21
Slide 21
Advanced Operational Capabilities

Path statistics
Aggregated across calls / tests each path (agent pair) for
Route performance
Data correlated to identify problem IP segments
Web Services API

Controller has an XML/RPC API SOAP/XML interface available Web Services API replicates functions available through GUI and supports multiple concurrent connections
Path Stats and Route Performance views
CONFIDENTIAL
SOT-MONITORING-A
There are many advanced operational capabilities built into this solution. There are APIs for exporting results to longer term storage, for long-term trend analysis, and the ability to correlate across multiple layers within the session or that the service is running over. That is, the service layer, network layer, and IP layer can all be correlated and can be measured against a standard for service quality. It provides a holistic look, which would be missing if using a disparate set of tools or vendors that make up the tool kit for monitoring a VoIP or IP environment.
SOT-MONITORING-A
22
Slide 22
Key Positioning Messages

Addresses Service Lifecycle Monitoring
Pre-deployment testing to test networks ability to handle traffic load Post-deployment multilayer SLA monitoring and capacity planning Post-deployment multilayer troubleshooting Strong historical analysis, reporting and visualization feature set
Deployment Flexibility and Comprehensiveness

Easily deployed anywhere there is an M or MX Series routerdata-center to network edgecreating a comprehensive monitoring environment
Partner Expertise and Install Base

Extends Juniper router scale and performance to monitoring environment Integrated with hundreds of Telchemy enabled3rd party devices
Unified Sales and Support

Sold and supported via the same processes as all Juniper products.
CONFIDENTIAL
SOT-MONITORING-A
TePM covers the life cycle of monitoring. Pre-deployment tests help understand network capacity, the implications of capacity and performance on new services, or expanded services that are being considered. In a post deployment environment, how to achieve SLA (service level agreement) monitoring? How to continue to garner information about network capacities so that planning for a future expansion can be performed? Just like with the StreamScope, where there is an MX Series router, a monitoring point can be implemented. In the case of Telchemy, this can also extend to existing M Series. This is something that has been in development for a decade, so it has an advanced and mature feature set.
SOT-MONITORING-A
23
Slide 23
Performance Considerations
There is no limit to the number of TePM agents that can connect to a given TePM Controller
Limit may be imposed by OS in the # of IP sockets available
Agent performance limited by

Available service card CPU cycles packet I/O delays JUNOS system events
VoIP monitoring performance

MS100: 200 concurrent VoIP calls MSDPC: 400 concurrent VoIP calls
Unused or removed agents should be removed from the Controller to prevent periodic connection attempts Controller logs can grow infinitely large - periodic manual rotation of logs is suggested
The number of simultaneous IP probe and network application tests are independent of VoIP tests because they run on a separate CPU core
CONFIDENTIAL
SOT-MONITORING-A
There are a variety of performance considerations to be aware of. There is no limit to the number of TePM agents that can connect to a controller, but there is going to be some limitation in the operating system of how many agents they can concurrently control. By removing agents, or if there are agents in the network that are underutilized, they should be removed, because they will occasionally try to connect to the controller, which consumes some of the controller cycles. Controller logs can continue to grow, so some type of manual rotation on a recurring basis will be important to plan for and conduct. Agent-wise, the performance is limited by the CPU cycles available on the service card any basic packet I/O delays, and other Junos system events that set precedence, or that may occur impact performance. There are a number of different metrics that govern how many concurrent calls a single service PIC/DPC can manage. Simultaneous IP and network application tests can be run without performance impact because they are independent of the VoIP test and they run on a separate CPU core.
SOT-MONITORING-A
24
Slide 24
TePM Summary
High performance, scalable solution
Scales to large number of concurrent monitoring sessions Performance meets fine inter-packet spacing requirements TePM Controller efficiently manages distributed TePM Agents Advanced feature set Provides MOS scores and a broad set of metrics for active tests Is interoperable with other products via TWAMP formats (rfc5357) TWAMP requester functionality is planned for a future release Cost effective Wide range of OSS integration options Pay as you grow: low risk investment protection
CONFIDENTIAL
SOT-MONITORING-A
TePM is a high performance, scalable, optimized solution for Voice over IP and IP tests at multi-layer level. It gives the performance metrics to include the users perspective with important parameters like MOS scores. It has built in TWAMP functionality and is a cost effective way to do comprehensive, ubiquitously deployed VoIP testing/ monitoring environments. It is a critical component for assuring voice quality.
SOT-MONITORING-A
25
Slide 25
Complimentary Monitoring Portfolio

StreamScope eRM
High Performance Passive Video Monitoring Transport Stream Analysis, Elementary Analysis, Frame Analysis
TePM
High Performance Active Voice and IP Monitoring IP probes for UDP, TCP, ICMP, HTTP, TWAMP, etc Robust MOS scoring per codec, SIP metrics
J-Flow
Active and Passive IP Flow Monitoring IP probes for UDP, TCP, ICMP, HTTP, TWAMP, etc
CONFIDENTIAL
SOT-MONITORING-A
J-flow, TePM as well as StreamScope eRM can be used together to solve customer service issues and there is no overlap in the positioning or feature set of the platforms. There is a lot of room for customers to use multiple products to solve different problems within the network.
SOT-MONITORING-A
26
Slide 26
Putting It All Together: Triple Play Example

Datacenter NOC
TePM Controller StreamScope eRM UI Junos CLI
StreamScope eRM for MPEG monitoring and analysis
A B C
RTR 1
B
A B C
RTR 2
TePM for VoIP monitoring and analysis
A B C
RTR 3
J-Flow for active and passive IP flow monitoring and analysis
VoIP Stream Video Stream
CONFIDENTIAL
SOT-MONITORING-A
In this diagram, the orange line represents VoIP calls that may be going through the network and traversing the IP infrastructure. There are some routers in the infrastructure. The green line is the video that is passing over the IP infrastructure. In the NOC (network operations center), the TePM controller is run; also, it is accessible to the eRM and UI the web-based browser or other mechanisms that can be used to monitor StreamScope. There is also the Junos CLI, for all of these applications, as well as the infrastructure elements. On the lower right-hand side of the diagram is represented the layer two access network. There are in some cases, CPE (customer premises equipment) devices that are doing limited routing and end user devices like HDTVs or SIP phones. There is the ability to put the StreamScope application, the Telchemy application, and the J-Flow application all on one network element and provide comprehensive monitoring for all service types across the network. In a Triple Play scenario, the sessions are traveling over IP, whatever they are supporting. J-Flow allows a comprehensive monitoring of the IP network to see how those flows are operating. Detailed VoIP monitoring can be performed at any given monitoring point using Telchemy, allowing comprehensive MDI and MPEG analysis. The MPEG analysis is particularly critical at router number one and router number 3. This is the first point where video streams enter the IP infrastructure. This means that quality MPEG streams are coming into the network and a clean signal exits at the network edge. Before it reaches the customer, the provider can validate that the signal is clean. This will help with fault isolation and with rapid time to repair.
SOT-MONITORING-A
27
Slide 27
Router-integrated Triple Play Monitoring Framework
Single network element

TePM VoIP monitor StreamScope eRM video monitoring J-Flow IP flow monitoring
Extends MX scale, performance and reliability to monitoring environment Easily implemented wherever the MX Series router is deployeddatacenter thru network edge creating a comprehensive monitoring environment MX 3D Universal Edge Router Easily and consistently integrated with NMS / OSS
CONFIDENTIAL
SOT-MONITORING-A
This slide presents the Juniper Networks MX Series 3D router as providing the foundation for a Triple Play monitoring environment. The MX3D is deployed to support video in many customer networks today. Adding VoIP, video and IP monitoring capabilities are all incremental benefits on top of that basic deployment model. Each of these can be integrated on one network element. All the benefits of the MX in terms of scale, performance and reliability are naturally inherited by the monitoring environment. It is easily implemented by adding MS-DPCs and the software is simple compared to qualifying new hardware, new vendors, and new applications into the network. Because the work has already been done to integrate with NMS and OSS, again its a very small incremental effort to integrate these applications into that environment.
SOT-MONITORING-A
28
Slide 28
Router-integrated Triple Play Monitoring Savings

Router-integrated Triple Play Monitoring Traditional Triple Play Monitoring
Video Monitoring appliances IP Probes VoIP monitor Switch
TePM VoIP monitor StreamScope eRM video monitoring J-Flow IP flow monitoring
CONFIDENTIAL
SOT-MONITORING-A
How does this play out from a capital expenditure and operations expenditure perspective? This slide presets a comparison between a traditional Triple Play Monitoring environment and a router-integrated scenario. The basic router provides the infrastructure underpinning. However, with the traditional approach, there will be a need to add a switch and some type of VoIP monitoring appliance to the network. Of course, these devices are all going to have to be interconnected. Whereas with Juniper, and the router integrated approach, an MS-DPC can be installed and the application added to the router. For IP Probe capabilities, in the traditional environment, yet another appliance is added. In the router integrated approach, this can be run on the router either on the MS-DPC or on the RE (routing engine), providing a holistic and consolidated approach to network monitoring. Finally, there are video monitoring appliances that need to be added to the traditional Triple Play Monitoring environment. Again, all of these devices have to be networked with port mirroring or monitoring configured. It adds a fair degree of complexity and is difficult to scale. With StreamScope eRM, by adding an MS-DPC, the monitoring is done right on the infrastructure component that is supporting all of the flows. The value in terms of space, power, and complexity reduction are all very apparent as these features are consolidated onto the router.
SOT-MONITORING-A
29
Slide 29
Course Summary
In this course, you learned to discuss:
Router Services Product Portfolio StreamScope ERM Telchemy ePM Complimentary monitoring portfolio Triple Play monitoring Framework
CONFIDENTIAL
SOT-MONITORING-A
In this course, you learned to discuss: Router Services Product Portfolio StreamScope ERM Telchemy ePM Complimentary monitoring portfolio, and Triple Play monitoring framework.
SOT-MONITORING-A
30
Slide 30
Additional Resources
Education Services training classes
http://www.juniper.net/training/technical_education/
Juniper Networks Certification Program Web site

www.juniper.net/certification
Juniper Networks documentation and white papers

www.juniper.net/techpubs
To submit errata or for general questions

elearning@juniper.net
CONFIDENTIAL
SOT-MONITORING-A
For additional resources or to contact the Juniper Networks eLearning team, click the links on the screen.
SOT-MONITORING-A
31
Slide 31
Evaluation and Survey

You have reached the end of this Juniper Networks eLearning module You should now return to your Juniper Learning Center to take the assessment and the student survey
After successfully completing the assessment, you will earn credits that will be recognized through certificates and non-monetary rewards The survey will allow you to give feedback on the quality and usefulness of the course
CONFIDENTIAL
SOT-MONITORING-A
You have reached the end of this Juniper Networks eLearning module. You should now return to your Juniper Learning Center to take the assessment and the student survey. After successfully completing the assessment, you will earn credits that will be recognized through certificates and non-monetary rewards. The survey will allow you to give feedback on the quality and usefulness of the course.
SOT-MONITORING-A
32
Slide 32
2011 Juniper Networks, Inc.
Juniper Networks, Junos, Steel-Belted Radius, NetScreen, and ScreenOS are registered trademarks of Juniper Networks, Inc. in the United States and other countries. The Juniper Networks Logo, the Junos logo, and JunosE are trademarks of Juniper Networks, Inc. All other trademarks, service marks, registered trademarks, or registered service marks are the property of their respective owners. Juniper Networks reserves the right to change, modify, transfer, or otherwise revise this publication without notice.
CONFIDENTIAL
SOT-MONITORING-A
Juniper Networks, Inc. All rights reserved. Juniper Networks, the Juniper Networks logo, Junos, NetScreen and ScreenOS are registered trademarks of Juniper Networks, Inc. in the United States and other countries. JunosE is a trademark of Juniper Networks, Inc. All other trademarks, service marks, registered trademarks or registered service marks are the property of their respective owners. Juniper Networks reserves the right to change, modify, transfer or otherwise revise this publication without notice.
SOT-MONITORING-A
33
Slide 33
CONFIDENTIAL
SOT-MONITORING-A
34
ed u ca t i o n ser vic e s co u rsew a re
Co rp o rat e and Sal es Headq uart ers Junip er Net w orks, Inc. 119 4 Nort h Mat hil da Avenue Sunnyvale, CA 9 4 0 8 9 USA Phone: 8 8 8 .JUNIPER ( 8 8 8 .58 6 .4737) o r 4 0 8 .745 .20 0 0 Fax: 4 0 8 .74 5.210 0 w w w .juniper.net
APAC Headq uart ers Junip er Net w orks ( Hong Kong) 26 / F, Cit yp laza One 1111 Kings Road Taiko o Shing, Hong Kong Phone: 8 52.2332.36 36 Fax: 8 52.2574 .78 0 3
EMEA Head q uart ers Juniper Net w orks Irel and Airside Business Park Sw ord s, Count y Dub l in, Irel and Phone: 35.31.8 9 0 3.6 0 0 EMEA Sales: 0 0 8 0 0 .4 5 8 6 .4737 Fax: 35.31.8 9 0 3.6 0 1
Co pyright 20 10 Junip er Net w orks, Inc. Al l right s reserved. Junip er Net w orks, t he Juniper Net w orks logo, Junos, Net Screen, and ScreenOS are regist ered t radem arks o f Junip er Net w orks, Inc. in t he Unit ed St at es and o t her count ries. Al l o t her t rad em arks, service m arks, regist ered m arks, or regist ered service m arks are t he pro pert y of t heir respect ive ow ners. Juniper Net w o rks assum es no responsibil it y f or any inaccuracies in t his docum ent . Juniper Net w orks reserves t he right t o change, m od if y, t ransf er, or ot herw ise revise t his pub l icat ion w it hout not ice.

Sot Monitoring A

Încărcat de

Informații document

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

Sot Monitoring A

Încărcat de

Drepturi de autor:

Formate disponibile

e d u ca t io n se rv ice s co u rsew a re

ROUTER INTEGRATED MONITORING SOLUTIONS

Router Integrated Monitoring Solutions

Router Integrated Monitoring Solutions

Welcome to the Juniper Networks Router-integrated Monitoring Solutions eLearning module.

Juniper Networks, Inc.

Router Integrated Monitoring Solutions

2011 Juniper Networks, Inc. All rights reserved.

Juniper Networks, Inc.

Router Integrated Monitoring Solutions

2011 Juniper Networks, Inc. All rights reserved.

Juniper Networks, Inc.

Router Integrated Monitoring Solutions

Router Services Product Portfolio

Security and NAT products

IMS / Voice and Layer 2 products

Media Enabler Online Advertising and virtually limitless possibilities

Juniper Networks, Inc.

Router Integrated Monitoring Solutions

Monitoring Services Product Line

J-Flow Active and Passive Monitoring

2011 Juniper Networks, Inc. All rights reserved.

Juniper Networks, Inc.

Router Integrated Monitoring Solutions

True Network - Application Integration

MX960 MX480 MX240

M320 M120 M10i

2011 Juniper Networks, Inc. All rights reserved.

Juniper Networks, Inc.

Router Integrated Monitoring Solutions

Managing Video Service Quality Is Challenging

Fault identification and Isolation is difficult

2011 Juniper Networks, Inc. All rights reserved.

Juniper Networks, Inc.

Router Integrated Monitoring Solutions

Introducing StreamScope ERM

2011 Juniper Networks, Inc. All rights reserved.

Juniper Networks, Inc.

Router Integrated Monitoring Solutions

How StreamScope eRM Works

StreamScope eRM StreamScope eRM provides MDI and MPEG analysis

Technicians can be proactively alerted

2011 Juniper Networks, Inc. All rights reserved.

Juniper Networks, Inc.

Router Integrated Monitoring Solutions

Web-based User Interface

SNMP Traps and Alerts

2011 Juniper Networks, Inc. All rights reserved.

Juniper Networks, Inc.

Router Integrated Monitoring Solutions

Key StreamScope Positioning Messages

Avoids Appliance Proliferation

Investment Protection / Contains CapEx and OpEx

Juniper Sales and Support

2011 Juniper Networks, Inc. All rights reserved.

Juniper Networks, Inc.

Router Integrated Monitoring Solutions

We deploy monitoring on service specific equipment!

This is too expensive!

2011 Juniper Networks, Inc. All rights reserved.

Juniper Networks, Inc.

Router Integrated Monitoring Solutions

2011 Juniper Networks, Inc. All rights reserved.

Juniper Networks, Inc.