Revised Spring 2006 Network Management Theory And Practice 1 Chapter 9 Network Management, MIBs, and MPLS Stephen B. Morris.

Revised Spring 2006Revised Spring 2006 Network Management Theory AnNetwork Management Theory And Practiced Practice

11

Chapter 9Chapter 9

Network Management, MIBs, and MPLSNetwork Management, MIBs, and MPLS

Stephen B. MorrisStephen B. Morris

Revised Spring 2006Revised Spring 2006 Network Management Theory AnNetwork Management Theory And Practiced Practice

22

Network Management Theory and Network Management Theory and PracticePractice

Purpose of this chapter is to draw together the Purpose of this chapter is to draw together the main threads running through the book and main threads running through the book and revisit some of them, now that the foundation revisit some of them, now that the foundation chapters are completedchapters are completed

Revised Spring 2006Revised Spring 2006 Network Management Theory AnNetwork Management Theory And Practiced Practice

33

MIBS Again MIBS Again

MIB can be used to store rules and actionsMIB can be used to store rules and actions Policies consist of conditions (or rules) and Policies consist of conditions (or rules) and

actions taken when conditions are metactions taken when conditions are met Intercolumn dependency an important area of Intercolumn dependency an important area of

MIB designMIB design Where value of column X provides context for Where value of column X provides context for

column Y, or vice versacolumn Y, or vice versa Figure 9-1, an example where a tunnel instance is Figure 9-1, an example where a tunnel instance is

a backup for a primary tunnela backup for a primary tunnel

Revised Spring 2006Revised Spring 2006 Network Management Theory AnNetwork Management Theory And Practiced Practice

44

MIBS AgainMIBS Again

Revised Spring 2006Revised Spring 2006 Network Management Theory AnNetwork Management Theory And Practiced Practice

55

MIBS Again MIBS Again

Two tunnels can be configured to share same set Two tunnels can be configured to share same set of resources (e.g., bandwidth or duplicate of resources (e.g., bandwidth or duplicate resource)resource)

Dependencies contribute to MIB complexityDependencies contribute to MIB complexity Clear rules, best way to implement intercolumn Clear rules, best way to implement intercolumn

dependenciesdependencies NMS should not use agents to infer relationshipsNMS should not use agents to infer relationships MIB objects default values decrease SNMP-MIB objects default values decrease SNMP-

handling software complexity in an NMShandling software complexity in an NMS

Revised Spring 2006Revised Spring 2006 Network Management Theory AnNetwork Management Theory And Practiced Practice

66

MIBS Again MIBS Again

Default values avoid issues with languages such Default values avoid issues with languages such as Java which are slow to handle to handle as Java which are slow to handle to handle exceptions create by null dataexceptions create by null data

SNMP may be approaching a physical limit, due to SNMP may be approaching a physical limit, due to scale of emerging NEs:scale of emerging NEs: MIB design must incorporate this trend and allow MIB design must incorporate this trend and allow

for possible techniques such as compressionfor possible techniques such as compression Larger PDUs could be used because each field Larger PDUs could be used because each field

could be compressedcould be compressed Downside, more complicated PDU handling and Downside, more complicated PDU handling and

slower NE response due to compressed overheadslower NE response due to compressed overhead

Revised Spring 2006Revised Spring 2006 Network Management Theory AnNetwork Management Theory And Practiced Practice

77

MIBS Again MIBS Again

Moving individual packet-handling decisions outside Moving individual packet-handling decisions outside of the NMS increases IP packet high speed of the NMS increases IP packet high speed

MPLS FEC-To-NHLFE (FTN) MPLS FEC-To-NHLFE (FTN) Management Information Management Information Base, another important MPLS MIB providing a Base, another important MPLS MIB providing a framework for moving decisions outside the NMS framework for moving decisions outside the NMS

Forward Equivalence Class (FEC)Forward Equivalence Class (FEC) a group of IP a group of IP packets forwarded with same traffic-handling packets forwarded with same traffic-handling treatmenttreatment

Figure 9-2, illustrates two IP traffic streams feeding Figure 9-2, illustrates two IP traffic streams feeding into an MPLS LER (Edge Router 1)into an MPLS LER (Edge Router 1)

Objective, push the SMTP traffic through LSP and Objective, push the SMTP traffic through LSP and VoIP traffic through the tunnelVoIP traffic through the tunnel

Revised Spring 2006Revised Spring 2006 Network Management Theory AnNetwork Management Theory And Practiced Practice

88

MIBS AgainMIBS Again

Revised Spring 2006Revised Spring 2006 Network Management Theory AnNetwork Management Theory And Practiced Practice

99

Intelligence in Network: Intelligence in Network: ManufacturerManufacturer

Present NMS generation exhibit similar problems Present NMS generation exhibit similar problems of manufacturing systems automation and of manufacturing systems automation and control in 1980s-1990scontrol in 1980s-1990s

Need for distributed intelligence was compelling, Need for distributed intelligence was compelling, local intelligence put great strain on centralized local intelligence put great strain on centralized management and control systemsmanagement and control systems

One solution, use local intelligence in network One solution, use local intelligence in network controllers (similar to SNMP agents)controllers (similar to SNMP agents)

Using local sensors and low-cost processing Using local sensors and low-cost processing power wherever needed rather than in a central power wherever needed rather than in a central locationlocation

Revised Spring 2006Revised Spring 2006 Network Management Theory AnNetwork Management Theory And Practiced Practice

1010

Intelligence in Network: Intelligence in Network: ManufacturerManufacturer

These distribute controllers only reported serious These distribute controllers only reported serious problems to a central supervisory management problems to a central supervisory management systemsystem

This freed the central management system to This freed the central management system to perform more complex calculations, such as perform more complex calculations, such as scheduling production runs and reporting on scrapscheduling production runs and reporting on scrap

NMS probably will need more agent intelligenceNMS probably will need more agent intelligence Path Based Mesh Network (PBMN) provides basis for Path Based Mesh Network (PBMN) provides basis for

this by allowing NEs take some control responsibilitythis by allowing NEs take some control responsibility FTN MIB provides an SNMP-based example of policy FTN MIB provides an SNMP-based example of policy

usageusage

Revised Spring 2006Revised Spring 2006 Network Management Theory AnNetwork Management Theory And Practiced Practice

1111

Pushing FCAPS Into NetworkPushing FCAPS Into Network

FTN MIB provides an SNMP-based example of FTN MIB provides an SNMP-based example of policy usagepolicy usage

Other types of decision-making can be pushed Other types of decision-making can be pushed into network such as billing and accountinginto network such as billing and accounting

Usage-based billing allows for improved SP Usage-based billing allows for improved SP margins and network resource usemargins and network resource use

Riverstone Riverstone Lightweight Flow Accounting ProtocolLightweight Flow Accounting Protocol (LFAP) is an effort to provide more accurate (LFAP) is an effort to provide more accurate billing and accounting in the NEsbilling and accounting in the NEs

Revised Spring 2006Revised Spring 2006 Network Management Theory AnNetwork Management Theory And Practiced Practice

1212

Service-Level Network Service-Level Network ComponentsComponents

Aggregate objects combine base-level Aggregate objects combine base-level components to create some type of higher level components to create some type of higher level serviceservice

Managing complex services remains one of Managing complex services remains one of biggest problems faced by industrybiggest problems faced by industry

New MIBs may be needed to represent these New MIBs may be needed to represent these aggregate objects, realizing them may require aggregate objects, realizing them may require new signaling protocolsnew signaling protocols

Revised Spring 2006Revised Spring 2006 Network Management Theory AnNetwork Management Theory And Practiced Practice

1313

Generic Objects Realized Using Generic Objects Realized Using Software AbstractionSoftware Abstraction

Increasing deployed technology mix in enterprise Increasing deployed technology mix in enterprise networks places growing burden on NMSnetworks places growing burden on NMS

Software components used to realize NMS must Software components used to realize NMS must become increasingly abstractbecome increasingly abstract

Needs to occur at all software levels, with Needs to occur at all software levels, with technology specifics cleanly separated in their technology specifics cleanly separated in their own layersown layers

When application code needs access to NEs via When application code needs access to NEs via SNMP, all calls should be made to separate codeSNMP, all calls should be made to separate code

Business logic should not mix with network Business logic should not mix with network device technology access codedevice technology access code

Revised Spring 2006Revised Spring 2006 Network Management Theory AnNetwork Management Theory And Practiced Practice

1414

Generic Objects Realized Using Generic Objects Realized Using Software AbstractionSoftware Abstraction

Figure 9-3 provides an idea of demarcationFigure 9-3 provides an idea of demarcation All code written to access specific technology All code written to access specific technology

should be generic as possibleshould be generic as possible For example: better to name a class method For example: better to name a class method

getLabelValue()getLabelValue(), can be used for a number of , can be used for a number of label-based technologies (ATM, MPLS, FR, and label-based technologies (ATM, MPLS, FR, and Pseduo-Wires) versus Pseduo-Wires) versus getMPLSLabelValue()getMPLSLabelValue() because it is specifically tied to MPLSbecause it is specifically tied to MPLS

Key point is generic outer codeKey point is generic outer code Technology gets specific only at well defined Technology gets specific only at well defined

points in the codepoints in the code

Revised Spring 2006Revised Spring 2006 Network Management Theory AnNetwork Management Theory And Practiced Practice

1515

Generic Objects Realized Using Generic Objects Realized Using Software AbstractionSoftware Abstraction

Revised Spring 2006Revised Spring 2006 Network Management Theory AnNetwork Management Theory And Practiced Practice

1616

Need For End-to-End SecurityNeed For End-to-End Security

international terrorist threat has altered international terrorist threat has altered managements awareness and prioritymanagements awareness and priority

Disaster recovery planning and service Disaster recovery planning and service survivability now an integral part every network survivability now an integral part every network planningplanning

Need End-to-End security at every network levelNeed End-to-End security at every network level Should employ authentication and encryption Should employ authentication and encryption

when connecting to an NE EMS when connecting to an NE EMS Should use Authentication and encryption to Should use Authentication and encryption to

avoid little or no clear text exchange between an avoid little or no clear text exchange between an NMS and EMS, OSS and NMS, and so onNMS and EMS, OSS and NMS, and so on

Revised Spring 2006Revised Spring 2006 Network Management Theory AnNetwork Management Theory And Practiced Practice

1717

Shrink-Wrapped Solutions or Shrink-Wrapped Solutions or Consultancy Buy-inConsultancy Buy-in

NMS products (and NEs) increasingly NMS products (and NEs) increasingly homogeneous, often offering base-level features, homogeneous, often offering base-level features, fault and performance managementfault and performance management

Better deployment model results if NMS products Better deployment model results if NMS products are well-designed with characteristics such as:are well-designed with characteristics such as: High-quality (standard) MIBsHigh-quality (standard) MIBs Generic software components such as GUIs Generic software components such as GUIs

allowing management of generic connections allowing management of generic connections rather than technology specific objectsrather than technology specific objects

Flow-through provisioning with thin software Flow-through provisioning with thin software layerslayers

Adherence to standard NBIsAdherence to standard NBIs

Revised Spring 2006Revised Spring 2006 Network Management Theory AnNetwork Management Theory And Practiced Practice

1818

Integration with OSS Layers: Integration with OSS Layers: Northbound Interface (NBI)Northbound Interface (NBI)

Communication between OSS and NMS crucial to Communication between OSS and NMS crucial to successful management of large SP networkssuccessful management of large SP networks

OSS needs to communicate with NMS in same OSS needs to communicate with NMS in same way as NMS needs to communicate with EMSway as NMS needs to communicate with EMS

Two ways of implementing an NBI layer:Two ways of implementing an NBI layer: Put software in OSS layerPut software in OSS layer Pus software in NMSPus software in NMS

Ideal arrangement, NMS and OSS use same code Ideal arrangement, NMS and OSS use same code NBI layer investment (NBI layer investment (Figure 9-4Figure 9-4) worthwhile, ) worthwhile,

ease of OSS integrationease of OSS integration

Revised Spring 2006Revised Spring 2006 Network Management Theory AnNetwork Management Theory And Practiced Practice

1919

Roles of QA, IT, and DevelopersRoles of QA, IT, and Developers

Close cooperation needed in vendor organizations Close cooperation needed in vendor organizations to deliver NMS productsto deliver NMS products

Developers should delegate NE administration to IT Developers should delegate NE administration to IT and involve QA in every step of the development and involve QA in every step of the development processprocess

QA assures quality rather than just carrying out QA assures quality rather than just carrying out software integration testingsoftware integration testing

Developers become true knowledge workers—Developers become true knowledge workers—delegating NE administration to the IT and delegating NE administration to the IT and partnering with QA to ensure solution developmentpartnering with QA to ensure solution development

Revised Spring 2006Revised Spring 2006 Network Management Theory AnNetwork Management Theory And Practiced Practice

2020

Thin Software LayersThin Software Layers

Thin software layers in client, middleware, and Thin software layers in client, middleware, and server components of NMS are desirable:server components of NMS are desirable: Has small number of lines of codeHas small number of lines of code Is simple – no excessively complex codeIs simple – no excessively complex code Is fast and easy to modify, maintain, and testIs fast and easy to modify, maintain, and test Spread complexity over adjacent layers as in Spread complexity over adjacent layers as in

network protocol layers (Figure 9-3)network protocol layers (Figure 9-3) Strikes balance between form and function – code Strikes balance between form and function – code

size and complexity minimized while overall size and complexity minimized while overall function optimized.function optimized.

Default database values and flow through Default database values and flow through provisioning minimize code sizeprovisioning minimize code size

Revised Spring 2006Revised Spring 2006 Network Management Theory AnNetwork Management Theory And Practiced Practice

2121

Facilitating a Solution MindsetFacilitating a Solution Mindset

Facilitate NMS products solutions mindset:Facilitate NMS products solutions mindset: Engineers should focus on products not just Engineers should focus on products not just

projectsprojects Take ownership of large product areas (e.g., one Take ownership of large product areas (e.g., one

or more FCAP areas)or more FCAP areas) Adopt strategic interest beyond current software Adopt strategic interest beyond current software

release cyclerelease cycle Product engineers focus on many small, well Product engineers focus on many small, well

defined pieces of workdefined pieces of work Product engineers generally produce best Product engineers generally produce best

solutionssolutions

Revised Spring 2006Revised Spring 2006 Network Management Theory AnNetwork Management Theory And Practiced Practice

2222

SummarySummary

MIBs is central role in network management and MIBs is central role in network management and major theme of bookmajor theme of book

Standard MIBs should be used whenever possibleStandard MIBs should be used whenever possible Network management technology solutions a Network management technology solutions a

challenge for software developerschallenge for software developers MIBs accommodate pushing more intelligence MIBs accommodate pushing more intelligence

into NEs (e.g., FTN MIB)into NEs (e.g., FTN MIB) Increased NE sophistication will improve network Increased NE sophistication will improve network

scalabilityscalability

Revised Spring 2006Revised Spring 2006 Network Management Theory AnNetwork Management Theory And Practiced Practice

2323

SummarySummary

Benefits of NMS:Benefits of NMS: Provide overall network perspective Provide overall network perspective Provide centralized managementProvide centralized management Possible to proactively manage the network using Possible to proactively manage the network using

policiespolicies Adding new NE to an SP network can cost in Adding new NE to an SP network can cost in

excess of $20 million, most likely due to:excess of $20 million, most likely due to: NMS changes required for new hardware and NMS changes required for new hardware and

associated NMS modulesassociated NMS modules Interoperability problems with existing devicesInteroperability problems with existing devices Firmware bugs in new devicesFirmware bugs in new devices Integrating management for NEs into existing OSS Integrating management for NEs into existing OSS

workflows and business practicesworkflows and business practices

Revised Spring 2006Revised Spring 2006 Network Management Theory AnNetwork Management Theory And Practiced Practice

2424

SummarySummary

Similar cost apply to large enterprise networks, Similar cost apply to large enterprise networks, many technologies implemented long before many technologies implemented long before standards establishedstandards established

SNMP standard is widely deployedSNMP standard is widely deployed NMS and NE developers use standard tools such NMS and NE developers use standard tools such

as UML and SDL in conjunction with standard as UML and SDL in conjunction with standard programming languages to create increasingly programming languages to create increasingly open systemsopen systems

SNMPv3 provides security critical to successful SNMPv3 provides security critical to successful network managementnetwork management

Revised Spring 2006Revised Spring 2006 Network Management Theory AnNetwork Management Theory And Practiced Practice

2525

Supplemental MaterialSupplemental Material

The following web page provides information The following web page provides information about SNMPv3: about SNMPv3: Specifications approved by Internet Engineering Specifications approved by Internet Engineering

Steering Group (IESG)Steering Group (IESG) DocumentationDocumentation ImplementationsImplementations

Revised Spring 2006Revised Spring 2006 Network Management Theory AnNetwork Management Theory And Practiced Practice

2626

Supplemental MaterialSupplemental Material

SNMP SNMP AlternativesAlternatives:: Common Management Information Protocol Common Management Information Protocol

(CMIP)(CMIP) Common Management Information Services Common Management Information Services

(CMIS)(CMIS) OSF Distributed Management Environment (DME)OSF Distributed Management Environment (DME) Hierarchical Network Management System Hierarchical Network Management System

(HNMS)(HNMS) HyperMedia Management Schema (HMMS)HyperMedia Management Schema (HMMS)

HyperMedia Management Protocol (HMMP)HyperMedia Management Protocol (HMMP) HyperMedia Management Architecture (HMMA)HyperMedia Management Architecture (HMMA)