Information base for representation of management information in DiffServ

1
Information base for representation of management
information in DiffServ

• Designed by Tsaruk Yaroslav

2
Frameworks for providing Internet QoS

• Integrated Services (IntServ)
• Differentiated Services (DiffServ)
• MPLS (Multiprotocol Lable Switching)
• Trafic engineering and constraint-based routing

3
Differentiated Services

• Based on a model where traffic entering a network
  is classified , possibly conditioned at the
  boundaries of the network, and assigned to
  different service classes
• Here, we avoid complexity and maintenance of
  per-flow state information in core nodes and push
  unavoidable complexity to the network edges
• Provide scalable service differentiated in the
  internet that can be used to permit
  differentiated pricing of internet service
• Separate packet forwarding model from routing
  model

4
Differentiated Services

• Expedited Forwarding
• Guaranteed delay and jitter (similar to ATM CBR)
• Provides a Virtual Leased Line service
• Non-conforming policed on ingress and shaped on
  egress of Diffserv domain
• Manual provisioning or signaling protocols
  required for quantitative guarantees.
• Typically implemented with strict priority
  queuing
• Assured Forwarding (AF)
• Similar to ATM nr-VBR QoS
• Four AF classes with three codepoints each
• AF classes not specifically defined regarding
  performance or priority between classes
• Non-conforming traffic marked at the edge
• RED queuing most often used.
• Better then Best Effort Delivery
• Gold, Silver, Bronze services

5
Comparison DiffServ and IntServ
6
Comparison DiffServ and IntServ
     
7
List of existing mechanisms

• COPS
• SNMP
• CIM

8
Architecture of COPS system
Console
Policies
Policy Server PDP
Policy Storage
COPS/LDAP
COPS
The way of presentation transferred information
is PIB(Policy Information Base)
Network Device
9
COPS

• COPS provides a standard protocol for exchange of
  policy information between network servers and
  network clients, such as routers, switches, load
  balancers, etc.
• COPS provides a model where a network client can
  request a policy from a server. This
  bidirectional, dynamic policy dissemination
  improves upon other models where only a server
  can send policies, i.e. unidirectional
  dissemination.

10
COPS-PR

• COPS-PR is designed to facilitate the
  implementation of new policies as defined by
  Policy Information Bases (PIBs). Network
  professionals can quickly deploy new services and
  configurations across a network, using the
  COPS-PR layer as an extensible mechanism to
  dynamically update network devices with new
  policies.

11
Policy Information Base

• Policy Information Base is an information model
  to describe policies and the format of policy
  information between the PEP and PDP. PIB uses
  ASN.1 representation and Basic Encoding Rule
  coding and is therefore similar to Management
  Information Base (MIB).

12
Architecture of SNMP system
Client
Policies
SNMP
SNMP Manager
Policy Storage
SNMP
SNMP
The way of presentation transferred policy
information is MIB(Management Information Base)
SNMP Managed Device (Agent)
13
Simple Network Management Protocol

• The SNMP gives the user the capability to manage
  a remote network node by setting values and
  monitoring network events. It uses
• Several agents, which are applications running on
  each machine to be monitored or managed.
• One (or more) manager that connects to the agents
  to monitor and manage the devices by getting and
  setting properties and listening to events.

14
Simple Network Management Protocol

• The properties are data variables representing
  resources on the SNMP node handled by this agent.
  The variables are organized in an MIB (Management
  Information Base), a kind of dictionary ordering
  them in a tree structure (the MIB tree) that
  defines them (name, type and description) and
  arranges them in a logical way.

15
Architecture of CIM system
CIM Client
Policies
CIM Server
HTTP/HTTPS
CIM Object Manager
Policy Storage
HTTP/HTTPS
Object Provider
Object Provider
SNMP-MIB Object Provider
HTTP/HTTPS
The way of presentation transferred policy
information is PCIM(Policy Common Information
Model)/ XML
Managed Object
Managed Object
Managed Object
16
Policy representation in CIM
PolicyGroup
PolicyRule
PolicyTime PeriodCondition
PolicyAction
PolicyCondition
17
List of factors for comparison

• Used model of presentation data
• Simplicity of realization agent part
• Simplicity of realization server part
• Information Representation
• Scalability
• Maintenance

18
Used model of presentation data

• CIM schema uses an object-oriented approach for
  describing the schema that management
  applications can use to communicate with each
  other.
• MIB on the other hand is a hierarchical tree view
  of all managed objects.

19
Simple of realization

• SNMP
• Java SNMP API from AdventNet
• COPS
• Intel provide SDK for developing client side
• PBNM-SDK for developing server and client side
  application(Linux RH7.0) from WebSpectrum
• CIM
• Java WBEM API, OpenPegasus

20
CIM base application

• Developed application allow
• Create instances of classes
• PolicyRule
• PolicyCondition
• PolicyAction
• Create associations between this instances
• Specify parameters and allow to modify them

21
Architecture of developed CIM application
CIM Client
Policies
HTTP/HTTPS
CIM Object Manager
Policy Storage
HTTP/HTTPS
HTTP/HTTPS
Developed application based on OpenPegasus
realization CIM server
Network Device
22
Information Representation

• Both CIM and MIB are implementation independent
  when it comes to actually supporting a model like
  that in an agent.
• One of the biggest gains is its representation in
  an XML format and the various options that exist
  today in presenting an XML format in different
  applications (e.g. XSLT)

23
Scalability

• The approach to designing MIB was to allow for
  flexibility of adding new objects. Extensions can
  be added to a private subtree. This allows
  vendors to create objects to manage specific
  entities on their products and to make those
  objects visible to management station. But with
  SNMP a management station can only access
  information for which it knows how to ask.
• Extension in the CIM model involves more work
  than what is needed for adding another
  device/component/application in MIB. One has to
  understand the overall OO schema with the
  underlying design decisions involved in order to
  be able to extend the schema to fit his/her
  purposes. Understanding the different parts of
  the CIM model as well as the relationships/attribu
  tes/methods for each class in the different CIM
  models can be a substantial task.

24
Maintenance

• Nowadays quite many hardware supports SNMP
  protocol
• But insensibly it changes by
• CIM
• Rarely COPS

25
Results of comparison
26
Conclusions

• Base on made analyzes I have to affirm that
• CIM
• To hard for realization(have to specify huge
  number of properties)
• COPS
• Not wide Supported standard
• SNMP
• To hard for realization and does not support
  object oriented paradigm

27
Thank you for attentionQuestions please