You are on page 1of 7



The SNMP Agent Simulator enables simulation of standalone SNMP agents to test and demonstrate SNMP-based management applications. Its unique ability to create default values from any SMIcompliant MI or record variables from an e!isting agent and create variations on this basic simulation enables rapid simulation of SNMP devices. All SNMPv"# SNMPv$# and SNMPv% operations &'et ( 'etNe!t ( 'et ul) ( Set ( Traps ( Notifications* are supported. Description It is a very important protocol in the T+P(IP suite. A protocol# ,hich is designed for e!ternal devices to interact ,ith the management system is called SNMP. It allo,s monitoring and managing the net,or) from a single ,or)station or ,or)stations called SNMP managers &Management System*. It ,as originally developed in the Internet community to monitor - troubleshoot devices li)e routers# bridges# etc. SNMP is actually a family of specifications that provide a means for collection of net,or) management data from the devices residing in a net,or).

Existing System For testing a Network Management topology, we need to simulate the network environment in our system. Different vendors are provided simulators for testing. The main disadvantage in this scenario is, the simulators are not open source and free. Buying a simulator for testing is not always economical. Appart from that, as it is not open, customisation also is not possi le. Proposed System !ere we are creating a simulator purely y "A#A. The advantages are$ Free %ustomisa le


&NM' uses a distri uted architecture consisting of management systems ( agents. A management system is any computer running &NM' management software. The primary function of management system is re)uesting information from an agent. &NM' Agent is a process, running in all managed network devices. *ts +o is to constantly gather the information that the NM& may re)uest and respond to re)uests from one or more NM&s with the appropriate data. &NM' manager re)uests data from the agent. The &NM' agent receives this re)uest at port num er ,-, and it responds to the manager accordingly. .nder erroneous conditions, the agent generates trap and notifies it to the NM&. NM& will receive this trap signal at port num er ,-/. DataFlowDiagram.

Communication between Manager and Agent using SNMP.

SNMP Community: A community is a group to which hosts running the &NM' services elong. %ommunities are identified y a community name for e0ample 1pu lic1. The use of a community name provides primitive security. An agent will not accept a re)uest from a management system outside its configured community. An &NM' agent can e a mem er of multiple communities ut the agents ( managers should e the mem ers of the same community to communicate with each other. The &imple Network Management 'rotocol uses a Management *nformation Base2M*B34Agent paradigm.

M*B4Agent paradigm.


A M*B is a virtual data ase that identifies each managea le o +ect y its name, synta0, accessi ility, status, a te0t description and a uni)ue 5 +ect *dentification num er 25*D3. The specifications of managed o +ects and grouping of, and relationship etween, managed o +ects are addressed in M*B6**, which is specified in 7F% ,/,8.

7F% 27e)uests For %omments3 is a pu lished series of documents of protocol standards for the *nternet. These standards descri e the internal working of the *nternet. Most vendors9 agents support M*B6** and their own proprietary 2or 'rivate :nterprise3 M*B.


The network management system uses the availa le Managea le 5 +ects Data ase as a data dictionary of the )uestions it can ask the agent in each managed device. By compiling the various 'rivate M*Bs and M*B6** into the MDB, an NM& user can re)uest and receive the information stored in the agent for each 5*D specified.


5 +ect identifiers represent each managea le o +ect with a uni)ue se)uence of num ers and names. &NM' uses the num er as an a reviated form of the name to make re)uests or data values and to identify each response that carries the values. the o +ects. 5*D is a data pointing structure of A&N.,. 5*D uses dotted decimal format and uni)uely identifies

*n that way, the 'u lic M*B;s managea le o +ects would all start with the names 2*&5.*dentified<5rg.DoD.*nternet.Management.M*B3 and the 5*D 2,.8.-.,./.,3. private M*B;s managea le o +ects would all 5rg.DoD.*nternet.'rivate.:nterprise.3 and the 5*D 2,.8.-.,.=.,3. A start with the names 2*&5.*dentified<

System Requirements
System Requirements Hardware Requirements


+P/0 ".$ '12 Pentium Processor

Memory0 $34 M 5AM 6is) Space0 Minimum %77 M

Java Version

859 ".:.$ is bundled ,ith the product for all operating systems ;racle 6atabase is bundled ,ith the product for all operating systems


The SNM A!ent Si"#$%tor c%n si"#$%te %n SNM &'( SNM &)( SNM &* %!ent in t+o si"p$e Mo,#$es-

'. SMI %n, MIB cre%tion "o,#$eDescription<oad any SMI-compliant MI &s* in the SNMP Agent Simulator and create a basic simulation of the SNMP agent.

SNMP Management Information Base

A Management Information Base (MIB) is a collection of information that is organi2ed hierarchically. MI s are accessed using a net,or)management protocol such as SNMP. They are comprised of managed ob=ects and are identified by ob=ect identifiers. A managed ob=ect &sometimes called a MI ob=ect# an ob=ect# or a MI * is one of any number of specific characteristics of a managed device. Managed ob=ects are comprised of one or more ob=ect instances# ,hich are essentially variables.

Structure of Management Information

The Structure of Management Information (SMI) defines the rules for describing management information# using Abstract Synta! Notation ;ne &ASN."*. The SNMPv" SMI is defined in 5>+ ""33. The SMI ma)es three )ey specifications0 ASN." data types# SMI-specific data types# and SNMP MI tables. ). Con/i!#r%tion %n, M%n%!e"ent Mo,#$e6escription0 +reate variations on this basic simulation by recording real SNMP agents? configuring MI values# SNMP traps and informs # simulating SNMP error conditions# and so on.

SNMPv1 Protocol Operations

SNMP is a simple request(response protocol. The net,or)-management system issues a request# and managed devices return responses. This behavior is implemented by using one of four protocol operations0 'et# 'etNe!t# Set# and Trap. The 'et operation is used by the NMS to retrieve the value of one or more ob=ect instances from an agent. If the agent responding to the 'et operation cannot provide values for all the ob=ect instances in a list# it does not provide any values. The 'etNe!t operation is used by the NMS to retrieve the value of the ne!t ob=ect instance in a table or a list ,ithin an agent. The Set operation is used by the NMS to set the values of ob=ect instances ,ithin an agent. The Trap operation is used by agents to asynchronously inform the NMS of a significant event.

Major features:

:ase of use 7ecord and replay &NM' devices. #alues of &NM' agent M*B nodes can e recorded into >M? file through @.* or command line interface. 7ecorded data file can e modified to simulate different configurations. Multiple agents in one "#M %omplete &NM'v,, v/c and v8 2.&M and #A%M3 support &upport for dynamic row creation and deletion &upport for Bean&hell scripting language that is used in data file to model real time &NM' agent ehavior Trap simulation

:rror simulation &cala ility. The num er of agents on one computer is dependent on availa le system resources %ommunity string inde0ing 2multiple communities per *' address3