network management mibs and mms copyright 1998, systems integration specialists company, inc. all...

Network Management

MIBs and MMS

Copyright 1998, Systems Integration Specialists Company, Inc. All Rights Reserved

NM Architecture

NM Client

E

C

CMIP, SNMP,SNMPv2

AGENT

Management Information Base (MIB) Sources

• ISO Standards (www.iso.ch)– 10742 (DataLink Layer)– 10737 (Network)– 10733 (Transport)– Others: 10165-2,-4,-5,-6

MIB Sources Continued

• IETF (www.ietf.org)– RFC1155 (structure of objects)– RFC1212 (concise definitions)– RFC1213 (MIB-II for TCP/IP)

• ITU (www.itu.ch)– G.851.1, G.852.1, G.853.1, G.853.2

All Management Protocols Have:

• Ability to Monitor attributes

• Ability to Monitor/Set parameters

• Ability to Report/Alarm

Attributes/Parameters are Hierarchical

• Object ID’s are used to alias names– Example:

Internet Management (OBJID)::={ iso org(3) dod(6) 1 2}

How to Model Attributes

TP4, CLTPCLNPOSI DLL

TPO,TCPIPIP DLL

MAC Statistics

MMSACSE

Presentation, Session

Standardize Object Names

• OSIUL - Upper Layer management

• OSILL - Lower Layer– TP4...

• IPLL - Internet Lower Layer

• MACMNGT

Example (IPLL)

IPLL::= {TC P {

ST {tcpMaxConn INTEGER32,tcpActiveOpens INTEGER32,tcpPassiveOpens INTEGER32,tcpAttemptsFails INTEGER32,tcpEstabResets INTEGER32,tcpCurrEstab INTEGER32,.....see RFC1213

}

Similar Attributes for TP4

• Suggest stick to monitoring attributes

• Wait on remote management

• May want to know connection information– Connection Tables– Interface definitions

How to start OSIUL?

• Make use of service primitives for protocol layers.– Confirmed services– Unconfirmed services

Confirmed Services

Network

ReqSent

RespRxd

ErrRxd

DiscardDiscard

ReqRxd

RespSent

Common Class: ConfService

ReqSent INT32UReqRxd INT32URespSent INT32URespRxd INT32UerrSent INT32UerrRxd INT32Udiscard INT32U

UnConfirmed Services

Network

ReqSent

ReqRxd

DiscardDiscard

ReqRxd

ReqSent

Common Class: UnConfService

sent INT32Urxd INT32Udiscard INT32U

Common Class: SummStats

ConnAvail INT32UConnAct INT32UConnPend INT32UPDU INT32U

Let’s Look at OSIUL

OSIUL ::= {APPL,CO,MMS,ACSE,PRES,SESS}

MMS_MNGT::= {SUM SummStatsconfrm ConfServiceunconfrm UnConfServicereject UnConfServicecancel ConfServiceconnect ConfServiceabrt { Usr UnConfService Pro UnConfService }disc ConfService}

What is in APPL?

TimLstPwrUp BTIME6TimLstReset BTIME6InService INT32UNumPwrUps INT32U

What is in CO?

ResetStats BOOLEAN

How to report alarms

• Use UCA Reporting Model– Just need to define names and datasets

What about connection tables?

• Need to know connection pair– Local Address– Remote Peer’s Address

• Eventually need the ability to remotely abort the connection.

• Represents HUGE Security Issue.

Theoretical Addressing ClassA_ADDRESS::= { AE_ADDRESS,

PSEL,SSEL,TSEL,NADDR,MAC

}For generalization: Assume PSEL….MAC canhave multiple formats. Need {

format INT8U,len INT8U,value OCTET64}

Format Definitions

• MAC : (UNKNOWN, ADLC, ETHERNET, FDDI, HDLC, X.25).

• NADDR: (UNKOWN,NONE,IP, CLNP, IPV6,…..)

• TSEL: ( UNKNOWN,NONE, ISO)• SSEL: (UNKNOWN, NONE, ISO, TRIM…)• PSEL: (UNKNOWN, NONE, ISO, TRIM…)

– All readable, none writeable

AE_ADDRESS

• MAP ALL TO VISIBLE STRINGS– AP_TITLE– AE_QUAL*– AP_INVOKE_ID*– AE_INVOKE_ID*

* - Could be mapped to Integer values

Putting it All TogetherConn_table_entry::= { STATS,

CO, --reset PEER_ADDR_PAIR { local A_ADDRESSS, peer A_ADDRESS },ACTIVITY}

ACTIVITY::= TIMES OF LAST TRANSMISSION?TIME OF ESTABLISHMENT

STATS ::= DIFFICULT. IS it needed?

Tricks to Watch Out For

• Connections are dynamic– reference to table needs to be consistent even if

other connections go away.

• Fight the tendency to want to track individual connection statistics on per layer basis

• Need to discuss remote trace ability.

Summary

• In general, the mapping of MIBs to GOMSFE like objects is an appropriate mapping method.

• Need users input to know what needs to be mapped.

Care needs to be taken!

• Some attributes/parameters not locally accessible in embedded systems.

• Concentration on upper layer parameters should be the first work area.