- Nonlinear Code Management in EJB3
- Database Access via C# ADO.NET
- C# Reflection
- Object Relational Mapping and Java Persistence: Data Modeling and Legacy Schemas
- C# GUI Programming
- C# Assembly Programming
- Using the C# system.io Namespace
- Using C# Generics
- An Introduction to Concurrent Java Programming
- Using C# Interfaces
- Getting Your Software onto Linux
- What’s Wrong with Modern Software Development?
- Building a Solid Foundation for JPA and Hibernate
- Java Patterns for MPLS Network Management, Part 2
- Java Patterns for MPLS Network Management, Part 1
- Getting Started with Spring Web Flow
- Application Contexts for Spring Web Services
- Spring Web Services with SOAPUI
- Hit the Ground Running with the Spring Framework
- Building Multithreaded C# Applications
- Hosting an LDAP Server in VMWare
- Integrating Linux Into Your Windows Environment
- Understanding C# Object Serialization and Object Graphs
- Further Subversion Steps: Get Motoring with TortoiseSVN
- Further Steps with the Java Sound API
- 5 Easy Steps to Using Virtualization Technology
- Five Steps to Getting Started Server-Side with PHP
- Targeted Client Upgrades: Creating a Flexible, Low-cost Application Upgrade Mechanism
- Java DMK and Legacy IT Management
- Aspect-Oriented Programming: A Tool for Internationalization
- Achieving Separation of Concerns Using BPEL
- Mobile Java with J2ME
- Graph Algorithms in Java
- Design Patterns in Java: The Observer
- Five Steps to Managing Unstructured Data with Derby
- Using the Java Sound API
- Moving C++ and Java Programmers Up the Value Chain
- Java Nuts and Bolts: Copy Constructors, Cloning, and Linked Structures
- Further Steps with Derby: Derby Embedded in a Browser
- Further Steps with Derby: Defining and Accessing Your Data
- IT Management Using C# with WMI
- Using Derby as a Network Database Server Engine
- Five Steps to Further Success with Subversion
- Improve Software Installation with AntInstaller
- Multithreaded Java GUI Programming
- The C++ Strategy Pattern for Multiple Network Events
- Java Collections and Iterators
- The C++ State Pattern for Network Operations
- C++ Nuts and Bolts: Casts, Call-by-Reference, and Inheritance
- Getting Started with Subversion on Windows
- Getting Started with Derby
- C# Callback and Event Mechanisms
- Some Rules for Safer Java Programming
- Inheritance and Polymorphism in C++ and C#
- IT Management: Dipping into the Platform with C#
- C# and IT Management Infrastructure
- C++ to C# Migration
- Service Oriented Architecture with Apache Axis
- Speech-Enable Your Java Software
- Generic C++ for Networks
- C++ Inheritance and Polymorphism
- Thinking Recursively with C++
- Aspect-Oriented Programming for Production Code
- C++ Modularity with Namespaces and Exception Handling
- C++ Chain of Responsibility Pattern: Network Events
- The Web Services Distributed Management (WSDM) Standard
- MPLS Network Design Nuts and Bolts
- BPEL: The Next Big Thing in Software?
- On-Demand Computing: A New Paradigm
- Software Plasticity with Aspect-Oriented Programming
- Parser Configuration in JAXP
- Publish and Subscribe Using C++ and the Observer Pattern
- Java Application Servers: Seven Things You Should Know
- Legacy IT Management using C++
- Software Futures: Architecture
- Saving Money with Legacy Data
- Saving Money with Legacy Source Code
- MPLS and Ethernet: Seven Things You Need To Know
- Quality of Service, Part 2 of 2: Managing Enterprise QoS
- Quality of Service, Part 1 of 2: Elements of Enterprise QoS for Voice Over IP
- The Need for Autonomic Computing
- A Blade Server Primer
- Workflow-Based Network Management
- SNMP Versus Command-Line Interface (CLI) for Network Management
- Security and the Management Plane, Part 2
- Security and the Management Plane, Part 1
- Network Management and MPLS
- Managing Large Networks: Problems and Solutions
- Getting my first iPhone app into the App Store
Having just posted my first iPhone to the App store, I wanted to briefly describe the experience and at the same time to debunk some myths I’ve heard about since I started.
- SOA and IT Strategy
It's a rare organization that has a comprehensive IT strategy. Why does a strategy matter? For one thing, IT is now part of the DNA of all organizations. So, an effective strategy is a key business element.
- IT staff and contractors - why they matter
IT salaries and contract rates in free fall
- A day in the life of a software contractor - Forming good relationships
I wanted to share a few findings with you about my recent forays into the world of software contracting.
- The path to programming excellence ? C++ to Java from C, Pascal and others
I’ve probably used more programming languages down the years than is good for me. And like many other programmers, I mostly use Java nowadays. During my most recent product development, I made a foray back into C in order to do some Ethernet protocol analysis. Some languages are just better than others for such tasks - remember C is a system language so you can use it to dig right into the platform. Java is more constrained because of the JVM boundary. In the end, I integrated the down-to-the-metal C code right back into Java using JNI.
- Moving up the value chain
Following on from my previous posting on decision-making quality, I wanted to talk a little about the related subject of the value chain.
- Decision-making Quality
The need for forward momentum is perhaps one of the negative consequences of the fast pace of modern life. This issue is discussed in ex-world chess champion, Garry Kasparov’s latest book “How life imitates chess”. Kasparov feels that decision-making suffers if insufficient time is taken. He’s not alone. Edward de Bono – the inventor of lateral thinking once said that apart from extreme emergencies there is rarely a need to think quickly. Warren Buffett moved his offices out of
From the author of
Network Management, MIBs and MPLS: Principles, Design and Implementation
Introduction
Multiprotocol label switching (MPLS) continues to grow in popularity with global service providers (SPs), particularly in Europe [1]. At the same time, the deployment of MPLS-based services—for example, RFC 2547 Internet Protocol (IP) VPN—is proving to be something of a challenge [2] to those SPs for the following reasons:
Cost and difficulty of deploying and operating MPLS network management
MPLS competes with and may potentially replace existing technologies
Deployment of MPLS technology
Legacy technology support
This article focuses on the first of these problems, that of managing MPLS technologies.
In many ways, MPLS provides the best of both IP and asynchronous transfer mode (ATM) by combining traffic engineering, subnetwork connections, and different quality of service (QoS) models. IP, on the other hand, provides just a best-effort datagram service. Bringing together these two domains (IP and the ATM-connection-oriented telecoms world) requires an integrated approach to network management. In this article, we'll look at some of the reasons why this process may be more difficult than expected. The benefits of effective MPLS network management can be realized if the technology is integrated into the SP workflows and business processes.
MPLS provides the possibility of a unified core network for both SPs and enterprises. In this scheme, legacy technologies such as ATM, frame relay, and Ethernet can be pushed out of the core network to the edges. The resulting core network is then packet-based using MPLS and some specified QoS mechanism such as DiffServ, IntServ, and so on. Having a single connection-oriented, QoS-based core technology provides a foundation for standard signaling protocols such as Resource Reservation Protocol with traffic engineering extensions (RSVP-TE) and Label Distribution Protocol (LDP). This can then facilitate rapid service deployment, improving the SP's return on investment (ROI). The deployed network management system (NMS) is a critical element in realizing ROI and is used to support the five major network management functional areas. In many cases, more than one system is needed to realize the overall NMS capability.
The five functional areas of network management for MPLS are known by the acronym FCAPS:
Fault. Network devices generate data indicating problems or matters of interest to a network manager.
Configuration. Modifies the network in some fashion, such as creating a label-switched path (LSP). Often called provisioning in the telecoms world.
Accounting (or billing). Enables an operator to determine usage of network resources. End users may be billed or the data may be used for accounting analysis, such as ROI calculation.
Performance. Determines whether the network is operating within required limits. This factor is increasingly critical as service-level agreements (SLAs) are used by SPs to differentiate their services. SLAs are being used within enterprise networks in the form of contracts between IT and the various departments. Performance analysis may also be used by network planners to decide whether infrastructure upgrades are required.
Security. This area is increasingly critical with the growing number and level of sophistication of network attacks. The focus here is ensuring that network resources are protected from unauthorized access.
FCAPS can be seen as baseline capability, and deployed NMS products may well exceed this level. Many NMS offerings don't offer configuration capabilities, however; the network operator must use the individual device's element management system (EMS)—often a Telnet-based menu program that runs on devices such as routers, switches, hubs, etc. Where NMS products offer less than the full FCAPS, the end user may need to provide proprietary software to fill out the NMS capability. Many SPs employ large teams of technicians to carry out base-level device configuration; these tasks may arguably be better handled by software in the NMS/OSS layer. The Operations Support System layer (OSS) resides above the NMS and provides business management capabilities such as those described in the following table.
|
Process |
Example |
|
Workflow management |
Creating/modifying/deleting virtual circuits. |
|
Trouble ticketing |
"Router 10, interface 3 in Chicago has gone down." The problem is recorded and the operator may choose to create a specific workflow item to resolve the matter. |
|
Network planning |
"Is the fiber optic link between New York and Denver in need of replacement?" |
NMS products may provide application programming interfaces (APIs)—often based on CORBA—for use by OSS components. OSS applications can then call into the NMS via the API to handle situations such as these:
Retrieving all alarms on a given device
Creating a virtual circuit (for example, an LSP) between two nodes
Modifying the reserved bandwidth on a selected LSP because the associated enterprise customer has increased its subscription
Increasing the bandwidth allocated to an LSP
The OSS exists to support the SP workflows and business processes. The required OSS capabilities may be fulfilled by the NMS, or the OSS can even directly use the underlying devices via SNMP, XML mechanisms, and so forth. The OSS has a higher-level view than the NMS of the managed objects deployed in the network.
Account Sign In
View your cart