|
|
Most telecommunications and network systems, such as SONET/SDH/IDLC, etc. have many NEs connected with each other. If an input message is to be sent from a manager to a particular NE, it might have to pass through other NEs connected in the network. Hence it becomes necessary to make one or more of the NEs in a network as Gateway NEs (GNE) which will provide connection to other NEs.
A GNE will route the input message from a manager to the NE connected to it. TL1 Messages coming from the OSS will be routed by the GNE to the appropriate NEs by using the TID (Target Identifier). The GNE will also route the Autonomous Messages from the NE back to the managers connected.
AdventNet Simulation Toolkit supports the Gateway Network Simulation in TL1. This feature is supported in command line.
Creating the Agent Configurations
The Gateway Network Simulation takes the TL1 agent configuration file as input. Hence, each NE in the network must have the configuration file with .prp extension, which contains the simulated agent configurations. The Gateway NE may or may not implement a configuration file. The configuration files must be created using the AdventNet TL1 Agent Simulator.
The mapping information required to access the simulated TL1 agent based on Target ID must be provided in a text file format. The Gateway Network simulation uses this information to route the messages to the appropriate NE in the network. The format of the Text file is given below:
|
<Target IDs>=<Configuration file name with correct path> |
where,
Target ID - Specify any string as Target Identifier (TID). This string will be used by the TL1 Manager and the Gateway NE to route the TL1 messages.
Configuration file name - The configuration file with .prp extension, which contains the simulated agent configurations of the NEs in the network. This file must be created using TL1 Agent Simulator or Network Simulator.
The entries in a sample property file is given below :
|
Agent1=C:/AdventNet/Simulator4/tl1agents/Agent/sample1.prp Agent2=C:/AdventNet/Simulator4/tl1agents/Agent/sample2.prp |
|
|
Note:
|
Starting the Gateway Network Simulation
The Gateway Network Simulation can be started in command line by executing the StartTL1GNE.bat/.sh found inside the <Simulator_Home>/bin/cmdline directory, with the following options.
Mandatory Options
-m <property file> : The multiple agent property file which contains details of the different configuration files with different TID settings
-p <port number> : The Port Number where the Gateway Network Simulation must be started.
Optional Options
These options must be specified if the Gateway NE implements a configuration file :
-GTID <TID name> : Target ID of the Gateway NE.
-GCONF <conf file name> : The Configuration file used by the Gateway NE.
Example :
1. Starting the Gateway Network Simulation without the Gateway NE configuration :
|
StartTL1GNE.bat -p 8005 -m conf.txt |
2. Starting the Gateway Network Simulation with the Gateway NE configuration
|
StartTL1GNE.bat -p 8005 -m conf.txt -GTID xxx -GCONF sample.prp |
On successful startup of the Gateway Network simulation, the following message is displayed in command line :
TL1 Server started on <port>
Agents started successfully
Now, when a request is made by the TL1 manager with the required Target ID, the Gateway Network Simulator will forward the request to the appropriate NE and provide the response. If no target ID is specified, the Gateway NE will respond to the request if it is started with the -GTID and -GCONF options.
Testing Gateway Network Simulation
Create the TL1 Agent Simulator configurations (minimum two set of configuration) with different Target IDs. The configuration must be created in TL1 Agent Simulator or Network Simulator..
Create the property file as specified in Creating the Property File. It must contain the details of the configuration file, created in Step 1.
Start the Gateway Network Simulator with the required options. This will start the multiple TL1 agents with the specified configurations.
Query the TL1 agent from the manager with their Target IDs and Port number.
|
|
Note: The Target ID used to query the TL1 agent must be the Target ID specified in the property file . |
The GNE will forward the request to the appropriate NE and provide the response. You can also test the agent to send Autonomous messages and execute scripts, if configured for the queried Command code.
Query the TL1 agent from the manager without the TargetID. The Gateway NE will respond to the request.
|
|
