This document provides instructions for configuring an OSS over IP connection in three steps: 1. Configure the DX 200 network element for IP-based connectivity and edit two XML configuration files (EHC001GX.XML and EHC002GX.XML) containing TCP/IP, HTTP, XML, and data parameters. 2. Set up the XML-over-HTTP interface on the DX 200 by entering commands to use the IP interface and restarting the system. 3. Define report formats in MSS, check the logical file names for the XML report format, connect those files to the MEXFIL logical files, and connect MEXFIL to a VTP-3 device to verify that reports

1. Soc Classification level
1 © Nokia Siemens Networks Presentation / Author / Date
Procedure to Config OSS over IP

2. Soc Classification level
2 © Nokia Siemens Networks Presentation / Author / Date
Configuring the DX 200 for IP-based
DCN connection
Same as
MGW

3. Soc Classification level
3 © Nokia Siemens Networks Presentation / Author / Date
Important…………….
There are two s/w packet of OSS core and
OSS core2 . The OSS core2 address should be
There in router in SNMP address.
The OSS core address should be there in XML file
Which is mention in next slide.

4. Soc Classification level
4 © Nokia Siemens Networks Presentation / Author / Date
Configuring the XML-over-HTTP interface
Need to edit and activate two XML files: EHC001GX.XML and
EHC002GX.XML.
These files contain TCP/IP, HTTP, XML, and transferred data
related parameters.
To edit the XML configuration files, you need a web browser.

5. Soc Classification level
5 © Nokia Siemens Networks Presentation / Author / Date
To configure the XML files with a web browser

6. Soc Classification level
6 © Nokia Siemens Networks Presentation / Author / Date
Example of the EHC002GX.XML file
Unlocke
d
Click the Activate... button to activate the XML configuration file.

7. Soc Classification level
7 © Nokia Siemens Networks Presentation / Author / Date
Setting up the XML-over-HTTP interface
Configure the DX 200 network element to use the IP interface by
entering:
ZWOC:2,814,0;
Check the Q3_DX_ALARMS_FORW_ON parameter in the
network element.
ZWOC:2,241,1;
ZUSU:OMU,<index of active OMU unit>:C=DSK;
Restart the system or, if a system restart is not possible, restart the
OMU
(with code loading from the disk):

8. Soc Classification level
8 © Nokia Siemens Networks Presentation / Author / Date
Defining report formats in MSS
To modify the report format when using TCP/IP-based DCN
ZWOC:50,0,5;
ZWOC:50,1,5;
PRFILE Parameter was changed,Restart the OMU
ZUSU:OMU,<index of active OMU unit>:C=DSK;

9. Soc Classification level
9 © Nokia Siemens Networks Presentation / Author / Date
Check The Logical files Names of XML format
From NED to which you want to get generate the
REPORT ( enter MEXFIL in search you will find the
Name of logical files in XML format )….
Connect that files to MEXFIL logical files by ZIIS
Command.

10. Soc Classification level
10 © Nokia Siemens Networks Presentation / Author / Date
Connect the MEXFIL to VTP-3 Device By ZIIS
Command.

11. Soc Classification level
11 © Nokia Siemens Networks Presentation / Author / Date
Checking of Report
We can verify that our MSS generating the report
In XML format for verification.
Connect MEXFIL to your LAPTOP VTP, by
This you can verify the report generating or NOT.