Simulator Home

• Management of Agent/Network devices through RMI
• SNMP PDU Scrambler
• SNMP Proxy Agent Simulation
• Gateway NE Simulation

Management of Agent/Network devices through RMI

RMI (Remote Method Invocation) is implemented in the network simulator and the agent simulators, to manage the simulated agent and network behavior from a remote client program. RMI's unique capabilities to load and execute user-defined tasks at runtime, helps in test case automation of manager applications. For example, the automated test environment can change the value of a given OID on a given SNMP agent to simulate different responses that is required for the test cases, trigger traps at any time, etc. SNMP and TL1 RMI client API methods in the simulator can be accessed via RMI from the client program.

Some of the common scenarios that can be performed using RMI client API methods are given below:

• Ability to programmatically update values for a specific SNMP/TL1 device within the simulated network via an RMI interface
• Ability to programmatically configure/re-configure the network behavior ( the RMI interface allows you to
  programmatically do all the things that can be done using Jython scripts to configure behavior)
• Ability to programmatically add/remove an SNMP device through an RMI interface
• Ability to programmatically send SNMP v1/v2/v3 traps and TL1 autonomous messages.
• Ability to programmatically start/stop individual SNMP/TL1 devices in the network
• Ability to programmatically start the TFTP server, transfer files between the client and server and stop the TFTP server

SNMP PDU Scrambler

The SNMP PDU Scrambler is supported in SNMP Agent Simulator and Network Simulator to customize the request/response SNMP PDU by exposing it to the user for customization. The PDU Scrambler Interface enables you to,

• Access to the request PDU for customization, before sending it to the simulator for further processing.
• Update the request PDU with error status and error index values, if the incoming PDU is invalid.
• Access the SNMPScriptInterface object, for working with behavior API methods before processing the request/response PDU.
• Access to the response PDU for customization, before sending it to the socket layer.
• Update the response PDU with proper error status and error index values, if invalid and send a error response to the manager.

SNMP Proxy Agent Simulation

This feature enables testing the functionalities of the NMS/EMS, to manage multiple SNMP agents through a single port. The proxy agent simulation acts as a single gateway for exchanging SNMP messages with the management application and the multiple agents registered with it.

• Enables simulation of multiple SNMP v1 and v2c agents running at the same port with different community strings.

• Receives SNMP requests from the management application and retrieves the response from the appropriate agent using the community strings.

  

Gateway NE Simulation

In most telecommunications and network systems having many NEs, one or more NEs in the network act as the Gateway NE (GNE). TL1 messages coming from the manager will be routed by the GNE to the appropriate NEs. TL1 Gateway NE Simulation facilitates the testing of such scenarios, by simulating multiple NEs with unique Target Identifiers (TID).

• Enables simulation of multiple NEs with unique Target Identifiers (TID).
• The GNE Simulation acts as a single gateway for managing the multiple NEs connected to it, by listening through a single port.
• The GNE can be configured with its own configuration, so that it can respond to the messages appropriate to the GNE.

	Simulator Home