Contents

Conclusions and Future Work

API for Network Management with TL-1 protocol was tested with simulated TL-1 Agent in the Computer Technology Laboratory at IIT Delhi. All packages have been developed in Java and successfully tested in Windows environment. New concept of accessing remote CORBA objects through RMI called RMI-IIOP developed by Sun Microsystems and IBM, has been used as communication mechanism. COSNaming Service has been used as naming facility.

TL1 Manager was run on one machine and TL1 Agent was run on another machine. Login is provided for the TL1Manager to view the list agents running on the Network Elements. Several TL1 messages were successfully tested with TL1 Manager and Agent.

6.1 Typical Operations between TL1Manager and TL1Agent:

The following outcome shows the simulation results between TL1Manager and TL1Agent.

manager>start orbds -ORBInitialPort 1070 -ORBInitialHost localhost

manager>java

-Djava.naming.factory.initial=com.sun.jndi.cosnaming.CNCtxFactory

-Djava.naming.provider.url=iiop://localhost:1070

pro.selva.rmiiiop.ManagerAgentImp selva

Java Based API for Network Management with TL1 protocol

Os = Windows 98 (4.10), java version = 1.4.0-beta 3

Local IP Address: 10.64.2.88

(TL1 Manager GUI will appear now!)

TL1CommandSet .tcs is loaded into Tree.

agent>java -Djava.naming.factory.initial=com.sun.jndi.cosnaming.CNCtxFactory

-Djava.naming.provider.url=iiop://localhost:1070 pro.selva.rmiiiop.ui.TL1Client

TL1Agent is running

Local IP Address: 10.64.2.81

Log in to AgentView GUI to view all the agent currently running ... ....

Connect to TL1Agent through TL1Manager GUI .......

Successfully connection established with host = 10.64.2.81

Pick up a TL1 Command from left tree and send it to TL1 Agent.

Sample TL1Commands:

ACT-USER:

This command is used to set-up a session with the Network Element (NE).

Request:

ACT-USER: AGENTID: SELVA: 100::PASSWD;

Request Sent = <CR>

ACT-USER: AGENTID: SELVA: 100::PASSWD;

Response:

Response Message Received from: CT81

<CR>

<LF><LF> Source 2001-12-19 02:04:58<CR>

<LF>M 100 COMPLD<CR>

<LF>;

ALW-MSG-ALL:

This command instructs the NE to enter a mode in which all the REPT ALM and REPT EVT autonomous messages are transmitted.

Request:

ALW-MSG-ALL: AGENTID::549;

Request Sent = <CR>

ALW-MSG-ALL: AGENTID::549;

Response:

Response Message Received From :CT88

<CR>

<LF><LF> Source 2001-12-19 02:09:33<CR>

<LF>M 549 COMPLD<CR>

<LF>;

DGN-EQPT:

DIAGNOSE instructs an NE to initiate a diagnostic routine on one or more equipment units in the NE.

Request:

Request Sent = <CR>

DGN-EQPT:::1::Preliminary,,;

Response:

<CR>

<LF><LF> Source 2001-12-19 02:28:58<CR>

<LF>M 549 COMPLD<CR>

<LF> ``dgn: PASS, 22,8'' <LF>;

EX-EQPT:

EXERCISE instructs a NE to exercise an equipment unit, which may also be associated with a trunk, link, or signaling link.

Request:

Request Sent = <CR>

EX-EQPT:::2::;

Response:

<CR>

<LF><LF> Source 2001-12-19 02:37:58<CR>

<LF>M 2 COMPLD<CR>

<LF> ":"<CR>

<LF>;

RMV-EQPT:

REMOVE instructs an NE to remove one or more equipment units, facilities, ISDN channels, or interfaces, subscriber lines, trunks, links, packet links, or signaling links from service.

Request:

Request Sent = <CR>

RMV-EQPT:::3::;

Response:

<CR>

<LF><LF> Source 2001-12-19 02:42:07<CR>

<LF>M 3 COMPLD<CR>

<LF>;

RTRV-ALM:

RETRIEVE-ALARM instructs a NE to retrieve and send the current status of its alarm conditions associated with one or more equipment units, facilities, subscriber lines, trunks, links, packet links, signaling links, or test access within the NE.

Request:

Request Sent = <CR>

RTRV-ALM-EQPT:::4::;

Response:

<CR>

<LF><LF> Source 2001-12-19 02:43:55<CR>

<LF>M 4 COMPLD<CR>

<LF> ",:,,,,,,,:,,,:,"<CR>

<LF>;

6.2 Future Work:

Java API for NMS provides basic network management functionality on the Network Elements. However this project simulates a generic model of TL1 Agent and does not include any simulation of subscriber lines, trunks, links, and packet links, signaling links or ISDN channels. In future, this can be done so that we can get response related to individual Network Elements.

Both TL1 Manager and TL1 Agent are developed in java, but since this project uses IIOP as underlying protocol, we can have manager and agents written in different languages ensuring CORBA interoperability.