Light MIB

1
CMIP based Light MIB Design Implementation
Inho Roh, Ilsoo Ahn Network Systems
Division Samsung Electronics Co. ihroh,
isahn_at_samsung.com
2
Introduction
How to manage efficiently
Increasing heterogeneity and complexity Must
consider expandability efficiency
How?
High speedy Massively interconnected
Proposed various technologies CMIP, CORBA,
Web-based, XML etc.
Simple layout of small, separate network
SNMP(proposed as transition period standard)
Inadequate for the complex network
3
MIB(Management Information Base)
Management information between Manager and
Agent Collection of Information abstracted by
objects Control device by getting or setting
the MIB value
MIB
Table based Architecture Easy to implement
and highly compatible Limitation in
expandability and efficiency
SNMP MIB
Well designed concept with inheritance and
containment High overhead operating on OSI
7-layer stack Difficult to implement and manage
OSI MIB
4
SNMP vs. CMIP
5
Example of Managed Object Reference using
ObjectList attribute
NE1
EH1
Rack
TP1
TP2
TP3
TP4
Link
SOL
Shelf
EH1
SOL
SOL
SOL
EH2
EH3
EH1
Slot
ObjectList Pointer (AOL SOL)
CP2
CP3
CP1
Card
AOL
AOL
AOL
NE Network Element EH EquipmentHolder CP
CircuitPack
TP TerminationPoint AOL AffectedObject
List SOL SupportededByObjectList
6
Naming, Pointer relationships for the SDH Model
sdhNE
Optical SPI TTP
MS Protection Relationship
Naming
RS CTP
RS TTP
Naming
MS CTP
MS TTP
MS TTP
Naming
Naming
unPrCTP
prTTP
unPrCTP
Working channel
Protecting channel
AUG
Connectivity Pointer (Upstream Downstream)
AU4 CTP
AU3 CTP
SPI SDH Physical Interface RS Regenerator
Section MS Multiplexer Section
unPrCTP unProtectedCTP prTTP protectedTTP AU
Administrative Unit
SDH Synchronous Digital Hierarchy TTP Trail
Termination Point CTP Connection Termination
Point
7
Light MIB Implementation using Naming Rule
Light MIB Implementation
No Additional Modeling No Overhead
Insert reference Information for the other MOs to
RDN Id
RDN Id Basic component for MIT DN
configuration Mandatory Field
Naming Rule Rule given to Objects Name Between
Manager and Agent
Use RDN Id with Naming Rule
8
Example of Naming Rule for Encoding and Decoding
ttpId rackId100000 shelfId10000
slotId100 linkId
Encoding Rule
ShelfId
LinkId
1
1
1
5
0
7
RDN Id
RackId
SlotId
Example of TTP ID Naming Rule
Decoding Rule
rackId ttpId/100000 shelfId
(ttpId-ttpId/100000100000)/10000 slotId
(ttpId-ttpId/1000010000)/100 linkId
ttpId-ttpId/100100
9
Implicit MO Reference using Naming Rule
NE1
EH1
Rack
110301
110302
110303
110304
Link
SOL
Shelf
EH1
SOL
SOL
SOL
EH2
EH3
EH1
Slot
Implicit Relationship without using AOL or SOL
CP2
CP3
CP1
Card
AOL
AOL
AOL
NE Network Element EH EquipmentHolder CP
CircuitPack
TP TerminationPoint AOL AffectedObject
List SOL SupportededByObjectList
10
Implicit SDH hierarchy Architecture
sdhNE
110301
Optical SPI TTP
MS Protection Relationship
110301
RS TTP
110301
110401
MS TTP
MS TTP
Naming
Naming
Implicit Relationship without CTP managed Object
110301
unPrCTP
prTTP
unPrCTP
Working channel
Protectingchannel
AUG
Connectivity Pointer (Upstream Downstream)
AU4 CTP
AU3 CTP
SPI SDH Physical Interface RS Regenerator
Section MS Multiplexer Section
unPrCTP unProtectedCTP prTTP protectedTTP AU
Administrative Unit
SDH Synchronous Digital Hierarchy TTP Trail
Termination Point CTP Connection Termination
Point
11
Advantage of Light MIB
Light MIB Easy to implement Easy to Manage
Possible to refer MO only by RDN Id Doesnt
need additional attribute analysis
High Readability
Decreased Management Information
Saves storage space(better performance)
Decreased Network traffic and network load
Uses existing information model No effort for
additional Modeling Change only in Naming Rule
Small Change
12
Conclusions
Importance of Network Management

• How to manage complex and ever-growing network
  efficiently

SNMP(Simple Network Management Protocol)

• Simple and easy to implement but limited
  functions
• Not appropriate for managing complex and
  ever-growing network

CMIP(Common Management Information Protocol)

• Provides high stability and supported various
  functions
• Heavy overhead and complicated implementation and
  management

Light MIB using Naming Rule

• Easy to implement and manage with small change
• Maintains well-designed existing MIB of ITU-T
• Save storage space of Agent and Manager by
  reducing the volume of MIB
• Decreases management traffic and enhances the
  network performance