Analysis Of Network Managment Communications Essay

Published:

By considering the future, in this computerized world all the stuffs can be assigned by IP addresses and controlled from any part of the world through internet as remotely. I have started this work to explain how a non-computer-related item (refrigerator) can be controlled remotely through the internet from any part of the world. More over in this document I have explained about the 2-tier architecture of the component, Object Analysis and MO definition.

1. Major components of refrigerator and 2-tier architecture of the component

There are seven major units in the refrigerator. Those are Automatic defrost, cooling, Temperature control, Lightning, Ice maker, Ice and water dispenser, Door seal and hinges. I want to control the temperature of the fridge remotely. So I need to consider about the cooling and temperature control units inside the fridge. The main component of the cooling unit is the compressor. When Freon gas passes through the compressor it gets compressed. When it leaves from compressor it is converted into the gaseous state. This gas circulates all parts of the fridge and cools the items inside.

Lady using a tablet
Lady using a tablet

Professional

Essay Writers

Lady Using Tablet

Get your grade
or your money back

using our Essay Writing Service!

Essay Writing Service

The second unit is useful for temperature control. Because the device, thermostat is in this unit. The thermostat is the major device to control the temperature inside the fridge.

How it is work :

Thermostat (Temperature controller) is the device to sense the temperature inside the fridge. When it reaches the particular temperature, the device shuts off the electricity to the compressor. But the refrigerator is not completely sealed. There are places like around the door and where the pipes go through inside, that can leak little bit. So when the cool inside the refrigerator starts to leak out and the heat comes in, the thermocouple turns the compressor backs on to cool the refrigerator off again.

By this work flow, once I want to control the temperature remotely. I need to focus all tasks in temperature control unit. And need to control the devise thermostat properly.

2-tier Architecture and concept implementation for refrigerator

MDB (Manager) Server

(Agent)Refrigerator

Temp.Control.Unit MDB is physical database.

Unmanaged objects are network elements that are not managed both physical and logical (passive elements)

Managed Object Thermostat

MDB manage database Agent process

Unmanaged object

The refrigerator or the basic device information considers when the 2-tier architecture implements.

Server(Manager) Agent

Get & Set MIB

Response & Traps

DataBase

The application for the fridge runs in the Server system. When the user wants to control or monitor the fridge, the application runs according to user needs and throws the get or set values to agent. The agent decides to response or trap for request by the Manager.

2. Object Analysis sheet for Temperature controller

Components of the Fridge

Physical components

Mechanical compartmentsUser components

Temperature controller lighting

Cooling system Door seal and hinges

Ice maker

Auto defrost

Ice and water dispenser

Logical components

PowerEnvironmental

Compressor power climate - outside

Attributes of Temperature controller

- Capacity of compressor

- Thermostat reading range

- Thermostat model

- Compressor model

- Length of condenser

Actions of Temperature controller

- On/Off power for compressor

- Increase/decrease Freon pressure.

States of Temperature controller

- Current state of Temperature.

OAS for Temperature controller

Temperature-controller 1

Component

Cardinality

Attributes

Action

Statistics

States

Compressor

1

Size/Model

Freon pressure.

On/Off

Thermostat

1

Range/Model

Compressor.

range

Condenser

Lady using a tablet
Lady using a tablet

Comprehensive

Writing Services

Lady Using Tablet

Plagiarism-free
Always on Time

Marked to Standard

Order Now

1

Length

3. MO Definition

temConTable OBJECT-TYPE

SYNTAX SEQUENCE OF TemConEntry

ACCESS read-only

STATUS mandatory

DESCRIPTION “This table represents the sub-components of a

Temperature controller”

:: = { Temperature-controller 1}

temConEntry OBJECT-TYPE

SYNTAX TemConEntry

ACCESS read-only

STATUS mandatory

DESCRIPTION “A row in the temperature controller table. Rows cannot be created or deleted via direct SNMP operations.”

INDEX { temConIndex }

:: = { temConTable 1}

TemConEntry ::= SEQUENCE {

temConIndex Unsigned32, -- table index

temConCompressorSize Unsigned32, -- attributes

temConCompressorModel OBJECT IDENTIFIER,

temConCompressorPressure Integer32,

temConCompressorState BITS,

temConThermostatRange Integer32,

temConThermostatModel OBJECT IDENTIFIER,

temConCondensorLength Integer32,

temConThermostatState Integer32,

temConThermostatPower BITS,

}

temConIndex OBJECT-TYPE

SYNTAX Unsigned32

ACCESS read-only

STATUS mandatory

DESCRIPTION “Index into the Temperature Controller table. ”

:: = { temConEntry 1}

temConCompressorSize OBJECT-TYPE

SYNTAX Unsigned32

ACCESS read-only

STATUS mandatory

DESCRIPTION “Size of the compressor”

:: = { temConEntry 2}

temConCompressorModel OBJECT-TYPE

SYNTAX OBJECT IDENTIFIER

ACCESS read-only

STATUS mandatory

DESCRIPTION “Model or the type of the compressor”

:: = { temConEntry 3}

temConCompressorPressure OBJECT-TYPE

SYNTAX Integer32

ACCESS read-only

STATUS mandatory

DESCRIPTION “Pressure of the Compressor”

:: = { temConEntry 4}

temConCompressorState OBJECT-TYPE

SYNTAX BITS {

powerCompOff (0),

powerCompOn (1),

}

ACCESS read-only

STATUS mandatory

DESCRIPTION “Control the power of compressor - On/Off ”

:: = { temConEntry 5}

temConThermostatRange OBJECT-TYPE

SYNTAX INTEGER32

ACCESS read-only

STATUS mandatory

DESCRIPTION “Thermostat temperature range ”

:: = { temConEntry 6}

Part-B

SNMP 2-tier MIB for manageable object

There are many manageable objects in the world; Like router, switch, ATM, workstation, mainframe, and application. In this part I have chosen BRIDGE as a SNMP agent and the Server as a SNMP Manager. The SNMP agent (bridge) should control or monitor the activities by SNMP Manager (Server) through remotely. There are so many things in Bridge (SNMP agent) to control or monitor, ex. Basic Information, port details, STP protocol, Static details and more identifiable information that we can control or listen through remote. In this part the manageable object (bridge) is connected to the server through a local network or directly. User may control or monitor the bridge by accessing the server from remote. See the figure below for how they communicate between them.

Getting & settings MIB values

Sending responses and Traps

SNMP Agent SNMP Manger

SNMP is an Application layer protocol that provides a service to communicate between these. SNMP server is a system that control or monitor the activities of network hosts using SNMP. And the SNMP agent is a software component within managed device. It maintains the data for this device and report to the system. MIB consists of collection of managed objects and this is a virtual information area for NMI. MIB modules are written in the SNMP MIB module as like RFC 1213, RFC 1443.

SMIv2 Object Tree

Managed objects are organized into a Tree hierarchy. The first node is called as root, and anything with children are called as sub-trees and without children are called as leaves. The easy readable for human, the tree object IDs are defineed by numbers and those are separated by dots. So you can use the sequence of numbers instead of strings. This is the concept being used for all MIB-SNMP developments.

You can identify from my screenshot and the coding below, that I have also used the same structure for MIB development for bridge. The bridge is a manageable object. So children nodes going though the mgmt. then

mgmt -> mib2-> snmpBrdige from this snmpBridge divided into 2 trees as snmpStp and snmpStatic. Inside those I have created objects table and object entry to monitor or control the object of bridge.

Proof of Compiled MIB

I have developed these codes to monitor and to control the bridge STP port, state of the port, and STP port value (enable or disable). These all are developed under snmpStpPortEntry. snmpStatic is an another table for the objects static-address, static-receive-port and static-status; those are monitor or control by StaticAddress, StaticReceivePort and StaticStatus.

Source code MIB

-- SNMP SMIv2 - BRIDGE-MIB

-- Extracted from RFC4188 by MG-SOFT MIB

Lady using a tablet
Lady using a tablet

This Essay is

a Student's Work

Lady Using Tablet

This essay has been submitted by a student. This is not an example of the work written by our professional essay writers.

Examples of our work

BRIDGE-MIB DEFINITIONS ::= BEGIN

IMPORTS

MODULE-IDENTITY, OBJECT-TYPE,

Counter32, Integer32, mib-2

FROM SNMPv2-SMI

MacAddress

FROM SNMPv2-TC;

snmpBridge MODULE-IDENTITY

LAST-UPDATED "201004240000Z"

ORGANIZATION "University of Greenwich"

CONTACT-INFO

"Email: pratheep_itfac@yahoo.com"

DESCRIPTION

"This version of this MIB module is part of RFC 4188."

REVISION "201004200000Z"

DESCRIPTION

"The MIB module has been converted to SMIv2 format."

::= { mib-2 17 }

-- subtrees in the Bridge MIB

-- ---------------------------------------------------------- --

snmpStp OBJECT IDENTIFIER ::= { snmpBridge 2 }

snmpStatic OBJECT IDENTIFIER ::= { snmpBridge 5 }

-- ---------------------------------------------------------- --

-- The Spanning Tree Port Table

-- ---------------------------------------------------------- --

snmpStpPortTable OBJECT-TYPE

SYNTAX SEQUENCE OF SnmpStpPortEntry

MAX-ACCESS not-accessible

STATUS current

DESCRIPTION

"This table contains the detail for Spanning Tree Protocol."

::= { snmpStp 15 }

snmpStpPortEntry OBJECT-TYPE

SYNTAX SnmpStpPortEntry

MAX-ACCESS not-accessible

STATUS current

DESCRIPTION

"A STP port information list."

INDEX { snmpStpPort }

::= { snmpStpPortTable 1 }

SnmpStpPortEntry ::=

SEQUENCE {

snmpStpPort

Integer32,

snmpStpPortState

INTEGER,

snmpStpPortEnable

INTEGER,

}

snmpStpPort OBJECT-TYPE

SYNTAX Integer32 (1..65535)

MAX-ACCESS read-only

STATUS current

DESCRIPTION

"The port number of the port for which this entry contains STP management information."

::= { snmpStpPortEntry 1 }

snmpStpPortState OBJECT-TYPE

SYNTAX INTEGER {

disabled(1),

blocking(2),

listening(3),

}

MAX-ACCESS read-only

STATUS current

DESCRIPTION

"This is define by port's current state and this is define by STP."

::= { snmpStpPortEntry 3 }

snmpStpPortEnable OBJECT-TYPE

SYNTAX INTEGER {

enabled(1),

disabled(2)

}

MAX-ACCESS read-write

STATUS current

DESCRIPTION

"The enabled/disabled status of the port."

::= { snmpStpPortEntry 4 }

-- ---------------------------------------------------------- --

-- The Static Database (Destination-Address Filtering)

-- ---------------------------------------------------------- --

snmpStaticTable OBJECT-TYPE

SYNTAX SEQUENCE OF SnmpStaticEntry

MAX-ACCESS not-accessible

STATUS current

DESCRIPTION

"A table containing filtering information for specific ports and containing specific destination

addresses are allowed to be forwarded.Entries are valid for unicast and for group/broadcast addresses."

::= { snmpStatic 1 }

snmpStaticEntry OBJECT-TYPE

SYNTAX SnmpStaticEntry

MAX-ACCESS not-accessible

STATUS current

DESCRIPTION

"Filtering information configured into the bridge."

INDEX { snmpStaticAddress, snmpStaticReceivePort }

::= { snmpStaticTable 1 }

SnmpStaticEntry ::=

SEQUENCE {

snmpStaticAddress MacAddress,

snmpStaticReceivePort Integer32,

snmpStaticAllowedToGoTo OCTET STRING,

snmpStaticStatus INTEGER

}

snmpStaticAddress OBJECT-TYPE

SYNTAX MacAddress

MAX-ACCESS read-create

STATUS current

DESCRIPTION

"This is for destination MAC address."

::= { snmpStaticEntry 1 }

snmpStaticReceivePort OBJECT-TYPE

SYNTAX Integer32 (0..65535)

MAX-ACCESS read-create

STATUS current

DESCRIPTION

"The port number of the."

::= { snmpStaticEntry 2 }

snmpStaticStatus OBJECT-TYPE

SYNTAX INTEGER {

other(1),

invalid(2),

permanent(3),

deleteOnReset(4),

deleteOnTimeout(5)

}

MAX-ACCESS read-create

STATUS current

DESCRIPTION

"This object define the status.The default - permanent(3)."

::= { snmpStaticEntry 4 }

END