lucent navisaccess cartridge guide · c_lu-navis_10-0_qry_profile ... element (ne) interface to...

Lucent NavisAccessCartridge Guide

First EditionSeptember 2008

Oracle ASAP™ Cartridge 1.1 for Lucent NavisAccess DSL

Copyright and Trademark Information

Copyright © 1992, 2008, Oracle and/or its affiliates. All rights reserved.Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this software or related documentation is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065.This software is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications which may create a risk of personal injury. If you use this software in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy and other measures to ensure the safe use of this software. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software in dangerous applications.

This software and documentation may provide access to or information on content, products and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third party content, products and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third party content, products or services.

Lucent NavisAccess Cartridge Guide iii

Contents

1. Cartridge Overview ...................................................................................... 1Cartridge content ................................................................................................................... 2Prerequisites ......................................................................................................................... 2About this guide .................................................................................................................... 2Services, features, and options ............................................................................................. 3Hardware and software requirements ................................................................................... 3

Network element (NE) interface ...................................................................................... 4ASAP version ................................................................................................................. 4

Connecting to the NE ............................................................................................................ 4

2. Installing and Testing the Cartridge ........................................................... 5Downloading the cartridge .................................................................................................... 6Installing the cartridge ........................................................................................................... 7Uninstalling the cartridge ....................................................................................................... 7Testing the cartridge installation ........................................................................................... 8

Communication parameters ........................................................................................... 8Loopback mode ............................................................................................................ 11Live mode ..................................................................................................................... 11Modifying Lucent_NavisAccess_connection.xml .......................................................... 12Testing the installation .................................................................................................. 14

Secure data ......................................................................................................................... 15

3. Atomic Service Description Layer (ASDL) Commands .......................... 17ASDL commands ................................................................................................................ 18

A_LU-NAVIS_10-0_ADD_DSL-HIGHSPEED ............................................................... 19A_LU-NAVIS_10-0_ADD_DSL-SNC ............................................................................ 21A_LU-NAVIS_10-0_ADD_DSL-VIDEO ......................................................................... 24A_LU-NAVIS_10-0_CONFIG_DSL-PORT ................................................................... 26A_LU-NAVIS_10-0_CREATE_DSL-SNC ..................................................................... 28A_LU-NAVIS_10-0_DEL_DSL-SNC ............................................................................. 31A_LU-NAVIS_10-0_QRY_DSL-HIGHSPEED .............................................................. 32A_LU-NAVIS_10-0_QRY_DSL-PORT .......................................................................... 35A_LU-NAVIS_10-0_QRY_DSL-SNC ............................................................................ 38A_LU-NAVIS_10-0_QRY_DSL-VIDEO ........................................................................ 41

User defined exit types (tbl_user_error) .............................................................................. 43

4. Service Definition ....................................................................................... 47Common Service Description Layer (CSDL) commands .................................................... 48

C_LU-NAVIS_10-0_CREATE_SNC ............................................................................. 49C_LU-NAVIS_10-0_DEL_SNC ..................................................................................... 51C_LU-NAVIS_10-0_MOD_HIGHSPEED ...................................................................... 52C_LU-NAVIS_10-0_MOD_PORT ................................................................................. 55C_LU-NAVIS_10-0_MOD_VIDEO ................................................................................ 56C_LU-NAVIS_10-0_QRY_HIGHSPEED ...................................................................... 57C_LU-NAVIS_10-0_QRY_PORT .................................................................................. 58

iv Oracle Corporation

C_LU-NAVIS_10-0_QRY_PROFILE ............................................................................ 59C_LU-NAVIS_10-0_QRY_VIDEO ................................................................................ 60

5. Configuring ASAP to Support Additional NE Instances ........................ 61Extracting source files ......................................................................................................... 65

Loading a new XML file ................................................................................................ 66

Lucent NavisAccess Cartridge Guide 1

1

Cartridge Overview

ASAP cartridges are discrete software components that are developed for the ASAP product. An ASAP cartridge offers specific domain behavior on top of the core ASAP software, and provides the configuration that supports a set of services on a network element (NE).

An ASAP cartridge is not a stand-alone component, but operates in conjunction with the ASAP core product. ASAP cartridges offer the following benefits:

Reduced Time to Market—time to market of new services is reduced through simplified development, implementation, and extension of cartridges on customer sites.Extendable—cartridges can be extended to include additional services and components that deliver business value, without requiring changes to the original cartridge.Simplified Effort—the effort and technical knowledge that is required to perform customizations is reduced.Ease of Installation—cartridges can be installed into an ASAP environment without interfering with the existing install base.

An ASAP cartridge can be used to configure ASAP to provision the following:

NEs from a specific vendor, such as Nortel or Lucent.Technologies, such as Asynchronous Transfer Mode (ATM) and Frame Relay switches, or Internet Protocol (IP) routers.Services that are supported on the NE, such as ATM, IP Virtual Private Networks (VPN), Wireless, or Optical.

An ASAP cartridge supports a particular set of services on an NE. These services are independent of customer-specific service definitions. Professional Services or systems integrators can perform extensions to the cartridge to support customer-specific requirements.

For more information on extending a cartridge, refer to the ASAP Cartridge Development Guide for Service Activation.

Cartridges are designed for a specific technology, software load, and service.

Chapter 1: Cartridge Overview

2 Oracle Corporation

Cartridge contentAn ASAP cartridge contains the following:

An interface to the NEA set of scripts, such as State Tables or Java methodsA set of atomic actions in the form of Atomic Service Description Layer (ASDL) commandsA set of Common Service Description Layer (CSDL) commands that form meaningful servicesSample work ordersInstallation scripts

PrerequisitesSystem integrators such as managers, designers, programmers, and testers who are responsible for the adaptation and integration of ASAP-based solutions should use this manual as a reference. It assumes that readers possess the following skills:

A knowledge of ASAP programming conceptsA good working knowledge of the UNIX operating systemA thorough understanding of service and network provisioningFamiliarity with telecommunications

About this guideThis guide provides a detailed description of the Lucent NavisAccess cartridge. It contains overview and technical information to assist with extending and integrating the cartridge into a customer environment.

The scope of this guide includes ASAP as it pertains to this cartridge. It is not a complete ASAP reference guide.

For additional ASAP information when using this cartridge, refer to the following supporting documentation:

ASAP documentation set—for detailed information on the ASAP core product.ASAP Cartridge Development Guide for Service Activation—for information on how to extend a cartridge.

The Lucent NavisAccess cartridge provides the ASAP service configuration and network element (NE) interface to activate DSL services on Lucent NavisAccess DSL NEs.

Services, features, and options


Services, features, and optionsService provisioning on the Lucent devices includes configuration of the line interface modules (LIM) for interface types of

PPP over EthernetBridged VLAN

The ASAP Cartridge for Lucent Navis Access DSL supports configuration for the following actions:

Hardware and software requirementsThe following sections contain the high-level software and hardware environment requirements for provisioning DSL services using this cartridge, including:

Network element (NE) interfaceASAP version

Table 1: Lucent NavisAccess services

Service Description

Modify DSL TP Port This operation modifies a DSL TP port for a specific set of parameters.

Modify DSL Video SNC This operation modifies a SNC for a specific set of parameters.

Modify High Speed SNC This operation modifies a SNC for a specific set of parameters.

Query DSL Port This operation returns the DSL TP structure for viewing.

Query Video SNC This operation returns the SNC structure for viewing.

Query High Speed SNC This operation returns the SNC structure for viewing.

Query Profile This operation returns a DSL TP structure, a video SNC structure and a high speed SNC structure for viewing.

Delete SNC This operation deletes a SNC port.

Create video SNC This operation creates a new video SNC port.

Chapter 1: Cartridge Overview


Network element (NE) interfaceThis cartridge operates with the the Lucent Navis Access DSL running software v10.0 with VisiBroker 5.2.1 (CORBA 2.5).

ASAP versionThis cartridge was developed and tested using ASAP 4.7.

For more information on the operating environment of this ASAP version, refer to the ASAP 4.7 Release Record.

Connecting to the NEThe ASAP cartridge interfaces directly with the Lucent Navis Access DSL, which complies to TMF814 using CORBA as the transport mechanism.

Note that Lucent has modified four IDLs. These IDLs supercede the standard TMF814 IDLs.


2

Installing and Testing the Cartridge

This chapter describes the following procedures related to installing and testing the cartridge:

Downloading the cartridgeInstalling the cartridgeUninstalling the cartridgeTesting the cartridge installationSecure data

Chapter 2: Installing and Testing the Cartridge


Downloading the cartridgeBefore you can install the cartridge, you must use the internet to download the cartridge’s TAR file from Oracle’s Customer Portal.

Use the following instructions to download, then unTAR the TAR file.

To download the TAR file

1. Login to Oracle MetaLink internet home page (http://www.metalink.oracle.com).

2. Download the cartridge patch to your workstation.

To unTAR the TAR file

1. On you workstation, create a repository directory—the naming of which is your choice.mkdir <repository dir>

2. Untar Lucent.tar.tar xvf Lucent.tar

3. Copy the resulting /Lucent directory and its contents to the repository directory.cp -rf /Lucent <repository_dir>

The directory structure in the repository directory should look like the following illustration. (this illustration describes the minimum required structure; you can enhance this directory structure with additional directories based on your requirements and deliverables). <repository_directory>

Lucent/README/installCartridge/uninstallCartridge/Lucent_NavisAccess_10-0.sar

Starting ASAP

Before installing the cartridge, ensure that ASAP is running.

To start ASAP

1. To start ASAP, execute the following script:start_asap_sys

2. Ensure the ASAP Daemon (DAM_$ENV_ID) is running by checking the ASAP status using the ASAP script “status”.

3. Check whether the WebLogic instance for this ASAP environment is running. If not, start the WebLogic instance.

The ASAP Administration Guide contains more information on starting ASAP, the ASAP Daemon, and WebLogic.

Installing the cartridge


Installing the cartridgeRun the installation script installCartridge to install the cartridge. You will find this script under /Lucent. The script executes the following tasks:

Configures the Lucent NavisAccess-specific NE using the SACT. Deploys the Lucent NavisAccess cartridge service model (only if the Lucent NavisAccess service model is not yet deployed) using the Service Activation Deployment Tool (SADT).Copies the Lucent NavisAccess-specific jar files and the cpp library file to the ASAP environment.Loads the sample work orders to the SRP database.

For information on the SACT and the SADT, refer to the ASAP Administration Guide.

To install the cartridge

1. Run the installCartridge script from /Lucent. At the prompt, type:installCartridge Lucent_NavisAccess_10-0.sar

2. The script prompts you for the values of the following WebLogic login parameters:

WebLogic HostnameWebLogic HTTP PortWebLogic Login User IDWebLogic Login Password

The script loads the NEP-NE configuration and the CSDL-ASDL configuration to the SARM database, and loads sample work orders to the SRP database. The script also copies the cartridge-specific jar files and cpp library file to the ASAP environment.

Note that the isntaller tries to deploy its own NEP and JNEP; consequently, you will likely need to configure lucent_navis_9-2_ne_config.xml. In addition, ensure that the JInterpreter_nam_template file points to the Oracle database.

3. Restart ASAP to upload the cartridge configuration into ASAP.

Uninstalling the cartridgeRun the uninstallation script uninstallCartridge to uninstall the Lucent NavisAccess cartridge. This script is located under Lucent. The script executes the following tasks:

Unconfigures Lucent NavisAccess-specific NEs using the SACT. Undeploys the Lucent NavisAccess cartridge service model (only if the Lucent NavisAccess service model is already deployed) using the Service Activation Deployment Tool (SADT). Removes the Lucent NavisAccess-specific jar files and cpp library file from the ASAP environment.



For more information on the SACT and the SADT, refer to the ASAP Administration Guide.

To uninstall the cartridge

1. Run the uninstallCartridge script from /Lucent. At the prompt, type uninstallCartridge Lucent_NavisAccess_10-0.<timestamp>.sar

2. The script prompts you for the values of the following parameters:

WebLogic HostnameWebLogic HTTP PortWebLogic Login User IDWebLogic Login Password

The script unloads the NEP-NE configuration and CSDL-ASDL configuration from SARM database. It also removes the cartridge specific jar files and cpp library file from the ASAP environment.

Testing the cartridge installationTo test this cartridge installation, you need to know about the network element (NE), services, and basic ASAP configuration. You may need to perform adjustments to provision a service for a specific NE, network, or connectivity configuration.

You can test the cartridge installation using one of the following methods:

Loopback mode—does not actually connect to or send commands to the NE.Live mode—connects to and sends commands to a live NE.

Communication parametersThis static database table contains the communication parameters required to communicate with various external systems. The table consists of the following fields:

dev_type – the protocol used to connect to the device.host – the host NE to which the configured parameter value applies.device – the device for which this parameter value applies.param_label – the label of the communication parameter.param_value – the value of the communication parameter.param_desc – a thorough and accurate description of the communication parameter

Testing the cartridge installation


The following table lists the contents of tbl_comm_param:

Table 2: tbl_comm_param

dev_type

host device param_label param_value param_desc

C LU-NAVIS-HOST Lucent_Navis_dev2

EMSINSTANCE quebec Name of EMS instance as its configured in the Naming Server.


NS_INSTANCE /config/NS_INSTANCE_quebec.ior

Interoperable Object Reference. This file is relative to ASAP_BASE directory.


LISTENER_PORT

38000 Listener port for this device, callback implementation.


LISTENER_PORT

38001 Listener port for this device, callback implementation.


SECURE_USER_PASS

NAVISACCESS2 Key to retrieve the userid/passwd from the secure table.


USERNAME navis_userid User name.


PASSWORD navis_password Password.


EMSINSTANCE ontario Name of EMS instance as its configured in the naming server.


NS_INSTANCE /config/NS_INSTANCE_ontario.ior

Interoperable Object Reference. This file is relative to ASAP_BASE directory.




SECURE_USER_PASS

NAVISACCESS1 Key to retrieve the userid/passwd from the secure table


USERNAME navis_userid User name.


PASSWORD navis_password Password.

C LU-NAVIS-HOST COMMON_DEVICE_CFG

USE_SECURE_DATA

TRUE Flag indicating whether secure login username and password is required.


NE_DIALOG_LOGGING

TRUE Flag to turn On or Off logging of API commands and responses.


ORBINITIALHOST

127.0.0.1 Visibroker host IP address (obsolete now).


ORBINITIALPORT

1570 Visibroker host port (obsolete now).


ORB_PROPERTIES

/config/Lucent_Orb_Properties.cfg

Property file containing orb parameters. This file is relative to ASAP_BASE directory.


USER_ERROR_TYPES_FILE

/config/Lucent_Navis_UserExitTypes.cfg

The user exit types file. This file is relative to ASAP_BASE directory.


dev_type




Loopback modeSet the following parameter to test the cartridge in loopback mode.

Live modeSet the following parameter to test the cartridge in live mode.


LAYER_RATE_FILE

/config/Lucent_LayerRate.cfg

The layer rate file used to map the connection type to the layer rate. This file is relative to ASAP_BASE directory.


PROTOCOL_IDENTIFIER_CONNECTION_TYPE_FILE

/config/Lucent_ProtocolIdentifier.cfg

The ProtocolIdentifier file used to map connection types that are retrieved from Navis and then mapped to their correct syntax for submission back to Navis. This file is relative to ASAP_BASE directory.

Table 3: Loopback Mode Parameter Settings

Configuration Variable Parameter Settings Location

LOOPBACK_ON 1 (default setting) ASAP.cfg

Table 4: Live Mode Parameter Settings

Configuration Variable Parameter Settings Location

LOOPBACK_ON 0 ASAP.cfg


dev_type




Modifying Lucent_NavisAccess_connection.xmlUse the following procedure to modify Lucent_NavisAccess_connection.xml.

To modify Lucent_NavisAccess_connection.xml

1. Create a new source directory under /Lucent. You can give this directory any appropriate, meaningful name you want to.

mkdir <new_source_directory>

2. Copy Lucent_NavisAccess_10-0.sar to this new source directory.

cp Lucent_NavisAccess_10-0.sar ./<new_source_directory>

3. Change directory to <new_source_directory>.cd <new_source_directory>

4. Un-jar Lucent_NavisAccess_10-0.sar This extracts the contents of the sar file (see Figure 1 on page 13 for an example of the resulting file structure).

jar xvf Lucent_NavisAccess_10-0.sar

5. Edit <new_source_directory>/Lucent/common/application_config/Lucent_NavisAccess_connection.xml in with the appropriate changes.

6. Create a new sar file at the <new_source_directory> level. CreateSar $PWD

7. Uninstall the cartridge using Lucent_NavisAccess_10-0.sar in /Lucent (That is, use the original sar file that you copied in Step 2 above—see “Uninstalling the cartridge” on page 7 for uninstallation instructions).

8. After you uninstall the cartridge, rename the sar file in /Lucent so you have a backup copy of it.

9. Copy the new sar file from <new_source_directory> to /Lucent.

10. Reinstall the cartridge (see “Installing the cartridge” on page 7 for installation instructions).



Figure 1: File Structure of the Un-Jared .sar File

META-INF/activation-model.xmlLucent/

NavisAccessDSL/DSL/

sample_wo/sarm/

ne_progs/PLSQL/

control/PLSQL/

nep/PLSQL/

java/lib/

cpp/lib/

service_model/{at least one .xml file}application_config/

common/sarm/

ne_progs/PLSQL/

control/PLSQL/

nep/PLSQL/

java/lib/

cpp/lib/

service_model/application_config/scripts/



Testing the installationThe following procedure describes the steps required to test the cartridge installation in loopback mode. We recommend that you perform the initial cartridge installation test in loopback mode.

To test in loopback mode

1. Stop ASAP by typing the following command at the UNIX prompt:stop_asap_sys

2. Ensure loop back mode is on. See “Loopback mode” on page 11 for a description of how to set the loop back parameter to “On”.

3. Start ASAP by typing:start_asap_sys

4. Send the sample work orders through the SRP Emulator by typing:run_suite $SRP <ctrl_password> <suite name>

You can locate the suite names in /Lucent/sample_wo by typing:grep SUITE * | grep -v END

A list of all available suites appears.

To see the sample work orders, refer to Viewing the sample work orders, below.

For more information on the SRP Emulator, refer to the ASAP Administration Guide.

5. Verify the status of the sample work orders by typing:asap_utils l

All successful work orders return the 104 state.

To view the sample work orders provided with this cartridge, refer to the Lucent NavisAccess cartridge source.

Viewing the sample work orders

You find the sample work orders under the sample_wo directory in the sar file. The following procedure describes how to view the sample work orders.

To view the sample work orders

1. If necessary, create a repository directory under /Lucent, copy the sar file to the new directory and un-jar the sar file, as described by Step 1 through Step 4 in “Modifying Lucent_NavisAccess_connection.xml” on page 12.

2. Locate and view the sample work order files under /Lucent/NavisAccessDSL/DSL/sample_wo.

Secure data


Secure dataUserid and passwords may be stored in ASAP in encrypted format. The ASAP control database has a table tbl_classB_secu that is used for storing customer sensitive communication parameters.

The entry to the table may be stored in a text file with the following format and then loaded into the database using asap_security_tool.

NAME:VALUE:CLASS:S_CACHE:DESCRIPTION

For example:

NAVISACCESS1:user123***password123:1:0:Login userid and password for NavisAccess

Note: The userid and password must be separated by 3 asterisks (***).

To load the above file into tbl_classB_secu use the asap_security_tool script. The syntax of the script is:

asap_security_tool -u $CTRL_USER -p $CTRL_PASSWORD -r <filename>

For more information on the ASAP Security Tool, refer to the ASAP Administration Guide.

Table 5: Secure data

Name Value Class S_CACHE Description

NAVISACCESS1 navis_userid***navis_password 1 0 Login userid and password for NavisAccess

NAVISACCESS2 navis_userid***navis_password 1 0 Login userid and password for NavisAccess


3

Atomic Service Description Layer (ASDL) Commands

ASDL commands represent a set of atomic actions that ASAP can perform on a network element (NE). ASAP can combine ASDLs to create meaningful services (CSDLs) within a cartridge.

This chapter presents detailed information on the ASDL parameters that we provide with this cartridge. The following table lists and describes the type of parameter information that is included.

Table 6: ASDL parameter information

Item Description

Parameter Name Identifies the parameter that is configured for the stated service.

Description Describes the parameter.

Range Describes or lists the range of values that can be used to satisfy this parameter.

Default Value Configures a default value for the parameter so that it is not mandatory for the upstream system to provide a value.

Chapter 3: Atomic Service Description Layer (ASDL) Commands


For a detailed description of the Required and Optional parameter classifications, refer to the ASAP Administration Guide.

ASDL commandsThis cartridge provides the following ASDL commands:

Type Indicates one of the following parameter types:

S—Scalar, specifies the parameter label transmitted on the ASDL command. Scalar parameters are conventional name-value pair parameters.C—Compound, specifies the base name of the compound parameter transmitted on the ASDL command. A compound parameter contains structures or arrays of information that are represented by a particular structure name or compound parameter name. Each compound parameter can contain a large number of elements. If you use compound parameters, you only require a single entry in the ASAP translation tables to call the compound parameter and all its associated parameter elements.I—Indexed, identifies a parameter that contains a sequential numerical index value to tell the SARM that it should execute the same operation (for example, an ASDL command) for all occurrences of that index. Consequently, if there are several options on a particular CSDL command (OPT1, OPT2, OPT3, etc.), you can specify the OPT parameter as an indexed parameter. When you specify the OPT parameter as an indexed parameter, the SARM generates several occurrences of that same ASDL command and each command has a different value for the option being transmitted to the NEP.

For more information on parameter types, refer to the ASAP Developer Reference.

Class Indicates one of the following parameter classifications:

R—Required scalar parameterO—Optional scalar parameterC—Required compound parameterN—Optional compound parameterM—Mandatory indexed parameterI—Optional indexed parameterS—Parameter count


Item Description

ASDL commands


A_LU-NAVIS_10-0_ADD_DSL-HIGHSPEEDA_LU-NAVIS_10-0_ADD_DSL-SNCA_LU-NAVIS_10-0_ADD_DSL-VIDEOA_LU-NAVIS_10-0_CONFIG_DSL-PORTA_LU-NAVIS_10-0_CREATE_DSL-SNCA_LU-NAVIS_10-0_DEL_DSL-SNCA_LU-NAVIS_10-0_QRY_DSL-HIGHSPEEDA_LU-NAVIS_10-0_QRY_DSL-PORTA_LU-NAVIS_10-0_QRY_DSL-SNCA_LU-NAVIS_10-0_QRY_DSL-VIDEO

A_LU-NAVIS_10-0_ADD_DSL-HIGHSPEEDAdds a new SNC (highspeed SNC). To be used only in association with A_LU-NAVIS_10-0_QRY_DSL-SNC and A_LU-NAVIS_10-0_DEL_DSL-SNC. This add function is effectively a merge operation of device parameters with new work order parameters. It is implemented by the Java method com.metasolv.cartridge.oss.lu_navis_10_0.prov.LuNavisProv.addSubNetworkConnection.

Table 7: A_LU-NAVIS_10-0_ADD_DSL-HIGHSPEED

Parameter Name Description RangeDefault Value

Type Class

MCLI Network element (NavisAccess EMS).

S R

MANAGED_ELEMENT

Managed element name. S R

SUBNET_NAME Subnetwork connection name.

S R

UPSTREAM_CONTRACT

(NAVIS_Upstream_Contract). The ATM QoS contract to be used for upstream data transfer. The specified QoS contract must have been configured on the device.

S O



DOWNSTREAM_CONTRACT

(NAVIS_Downstream_Contract). The ATM QoS contract to be used for downstream data transfer. The specified QoS contract must have been configured on the device.

S O

TDP_TEMPLATE (TransmissionDescriptorPointer) Connection template name.

S O

SNCTYPE CSDL return parameter. S O

RATE CSDL return parameter. S O

NAVIS_Connection_Activation_State

CSDL return parameter. S O

NAVIS_Connection_Name


ProtocolIdentifier CSDL return parameter. S O

NAVIS_Downstream_Contract


NAVIS_OAMTestable CSDL return parameter. S O

NAVIS_Upstream_Contract


NAVIS_VPSwitched CSDL return parameter. S O

NAVIS_Bridge_Group CSDL return parameter. S O

NAVIS_VLAN_Type CSDL return parameter. S O

NAVIS_VLAN_Id CSDL return parameter. S O

NAVIS_Frame_Type CSDL return parameter. S O

NAVIS_User_VLAN_Id CSDL return parameter. S O



Type Class

ASDL commands


MML commands/API callsMultilayerSubnetworkInterface. createAndActivateSNC(createData, tolerableImpact, EMSFreedomLevel_T,tpsToModify,theSNC,errorReason)

Output parameters

None.

A_LU-NAVIS_10-0_ADD_DSL-SNCAdds a new SNC (generic). To be used only in association with A_LU-NAVIS_10-0_QRY_DSL-SNC and A_LU-NAVIS_10-0_DEL_DSL-SNC. This add function is effectively a merge operation of device parameters with new work order parameters. It is implemented by

NAVIS_Flow_Services CSDL return parameter. S O

NAVIS_Data_Filter CSDL return parameter. S O

NAVIS_Route_Filter CSDL return parameter. S O

NAVIS_Switching_Type CSDL return parameter. S O

NAVIS_QoS_Interface_Group


NAVIS_Packet_Flows CSDL return parameter. S O

NAVIS_Mac_Address_Learning_limit


AEND_TPNAME[0] CSDL return parameter. S O

ZEND_TPNAME[0] CSDL return parameter. S O



Type Class



the Java method com.metasolv.cartridge.oss.lu_navis_10_0.prov.LuNavisProv.addSubNetworkConnection.

Table 8: A_LU-NAVIS_10-0_ADD_DSL-SNC


Type Class


S R

MANAGED_ELEMENT



S R

UPSTREAM_CONTRACT


S O

DOWNSTREAM_CONTRACT


S O

PROTOCOL_IDENTIFIER

(ProtocolIdentifier) Type of protocol used by the connection.

S O

CONNECTION_STATE (NAVIS_Connection_Activation_State) If the connection is enabled or disabled.

0 (no), 1 (yes) S O

OAM_TESTABLE (NAVIS_OAMTestable) Specifies whether OAM tests can be run on the connection.

0 (no), 1 (yes) S O

ASDL commands


VP_SWITCHED (NAVIS_VPSwitched). Specified if this is a VP switched connection.

0 (no), 1 (yes) S O

PPPoX_SERVER (NAVIS_PPPoX_Server) Name of the PPPoE-server profile to be attached to the output interface. Applicable only for PPPOverEthernet connections.

S O


S O



















Type Class




Output parameters

None.

A_LU-NAVIS_10-0_ADD_DSL-VIDEOAdds a new SNC (video SNC). To be used only in association with A_LU-NAVIS_10-0_QRY_DSL-SNC and A_LU-NAVIS_10-0_DEL_DSL-SNC. This add function is effectively a merge operation of device parameters with new work order parameters. It is implemented by
















Type Class

ASDL commands


the Java method com.metasolv.cartridge.oss.lu_navis_10_0.prov.LuNavisProv.addSubNetworkConnection.

Table 9: A_LU-NAVIS_10-0_ADD_DSL-VIDEO


Type Class


S R

MANAGED_ELEMENT



S R

UPSTREAM_CONTRACT


S O

DOWNSTREAM_CONTRACT


S O


S O











Output parameters

None.

A_LU-NAVIS_10-0_CONFIG_DSL-PORTModifies a DSL TP port. It is implemented by the Java method com.metasolv.cartridge.oss.lu_navis_10_0.prov.LuNavisProv.provisionDSLPort.









Table 10: A_LU-NAVIS_10-0_CONFIG_DSL-PORT


Type Class


S R

MANAGED_ELEMENT


SHELF The shelf on which the configuration is required.

S R

Table 9: A_LU-NAVIS_10-0_ADD_DSL-VIDEO


Type Class

ASDL commands


MML commands/API callsmanagedElementInterface.getTP(tpName,tpHolder);managedElementInterface.setTPData(tpData, modifiedTP);

Example SRQ outputSRQ ID SRQ_EVT EVT_TEXT------- -------- --------------------------------------------------------------------------------2 INFO Initial Reception of Work Order2 INFO Current CSDL 'C_LU-NAVIS_10-0_MOD_PORT' is under provision2 INFO ASDL A_LU-NAVIS_10-0_CONFIG_DSL-PORT for Lucent_Navis Route to NE Lucent_Navis2 INFO ASDL A_LU-NAVIS_10-0_CONFIG_DSL-PORT Provisioning Request to Lucent_Navis2 NE_CMD getManager2 NE_CMD getTP: managedElement: COVEON02OL1, shelf: 1, slot: 5, port: 32 INFO Successful getTP execution2 INFO TransmissionDescriptorPointer: al1_d1184-1184-256_u640-640-2562 NE_CMD setTP: managedElement: COVEON02OL1, shelf: 1, slot:5, port:32 ERROR ProcessingFailureException: Unable to setTPData. type=EXCPT_ENTITY_NOT_FOUND,reason= No Template Information was found for the input Template Name al1_d1184-1184-256_u640-640-256 of ADSL Type.2 ERROR ProvisioningException type=EXCPT_ENTITY_NOT_FOUND,reason= No Template Information was found for the input Template Name al1_d1184-1184-256_u640-640-256 of ADSLType.

SLOT The slot containing the card whose port is to be configured.

S R

PORT The port on the card which is to be configured.

S R

NAVIS_TEMPLATE (TransmissionDescriptorPointer). Connection template name. Indicates the template that must be used while configuring the PTP.

S O

Table 10: A_LU-NAVIS_10-0_CONFIG_DSL-PORT


Type Class



2 INFO ASDL Exit (LU_NAVIS_ENT_NOT_FND) Msg : type=EXCPT_ENTITY_NOT_FOUND,reason= No Template Information was found for the input Template Name al1_d1184-1184-256_u640-640-256 of ADSL Type.2 INFO ASDL A_LU-NAVIS_10-0_CONFIG_DSL-PORT of SRQ 2 Failed2 ERROR ASDL Failure Msg: type=EXCPT_ENTITY_NOT_FOUND,reason= No Template Information was found for the input Template Name al1_d1184-1184-256_u640-640-256 of ADSL Type.2 INFO SRQ Provisioning Stopped

A_LU-NAVIS_10-0_CREATE_DSL-SNCCreates a new SNC. It is implemented by the Java method com.metasolv.cartridge.oss.lu_navis_10_0.prov.LuNavisProv.createSubNetworkConnection.

Table 11: A_LU-NAVIS_10-0_CREATE_DSL-SNC


Type Class


S R

MANAGED_ELEMENT

Managed element name.

S R


S R


S R


S R

EGRESS_SHELF The shelf on which the configuration is required.

S O

EGRESS_SLOT The slot containing the card whose port is to be configured.

S O

EGRESS_PORT The port on the card which is to be configured.

S O

ASDL commands



S R

UPSTREAM_CONTRACT


S O

DOWNSTREAM_CONTRACT


S O

VPI Virtual Path Identifier. 0 S R

VCI Virtual Connection Identifier.

36 S R

EGRESS_VPI Virtual Path Identifier. S O

EGRESS_VCI Virtual Connection Identifier.

S O

PROTOCOL_IDENTIFIER


S O

CONNECTION_STATE

(NAVIS_Connection_Activation_State) If the connection is enabled or disabled.

0 (no), 1 (yes) S O


0 (no), 1 (yes) S O



Type Class




Example SRQ outputSRQ ID SRQ_EVT EVT_TEXT------- -------- -------------------------------------------------------------------------------- 5 INFO Initial Reception of Work Order 5 INFO Current CSDL 'C_LU-NAVIS_10-0_CREATE_SNC' is under provision 5 INFO ASDL A_LU-NAVIS_10-0_CREATE_DSL-SNC for Lucent_Navis Route to NE Lucent_Navis 5 INFO ASDL A_LU-NAVIS_10-0_CREATE_DSL-SNC Provisioning Request to Lucent_Navis 5 NE_CMD getManager 5 INFO LayerRate: 98 5 INFO AEND__attributes: MANAGED_ELEMENT: COVEON02OL1 5 INFO SHELF:1, SLOT: 5, PORT: 8, EGRESS_SHELF: 1, EGRESS_SLOT: 8, EGRESS_PORT: 2 5 INFO VPI: 0, VCI: 36, EGRESS_VPI: null, EGRESS_VCI: null 5 INFO ZEND__attributes: MANAGED_ELEMENT: COVEON02OL1 5 INFO SHELF:1, SLOT: 5, PORT: 8, EGRESS_SHELF: 1, EGRESS_SLOT: 8, EGRESS_PORT: 2 5 INFO VPI: 0, VCI: 36, EGRESS_VPI: null, EGRESS_VCI: null 5 INFO Using 'EMS_Assigned' for ZEnd CTP structure


S O


0 (no), 1 (yes) S O


S O



Type Class

ASDL commands


5 INFO NAVIS_Connection_Name: mslv-PPPOverX, NAVIS_Connection_Type: PPPOverX 5 INFO NAVIS_Upstream_Contract: td_ubr_up_pcr800_mcr0, NAVIS_Downstream_Contract: td_ubr_dwn_pcr3008_mcr0 5 INFO ProtocolIdentifier: null, NAVIS_Connection_Activation_State: 1 5 INFO NAVIS_OAMTestable: 1, NAVIS_PPPoX_Server: null 5 INFO NAVIS_VPSwitched: null, TransmissionDescriptorPointer: null 5 NE_CMD createAndActivateSNC: managedElement: COVEON02OL1, snc: mslv-PPPOverX 5 INFO Successful createAndActivateSNC execution 5 INFO ASDL Exit (LU_NAVIS_SUCCEED) Msg : Successful createAndActivateSNC execution 5 INFO Q Info: Queued: 11:51:00, Start: 11:51:00, Comp: 11:51:04 5 INFO SRQ 5 (Last CSDL C_LU-NAVIS_10-0_CREATE_SNC) has Completed

A_LU-NAVIS_10-0_DEL_DSL-SNCDeletes an SNC. It is implemented by the Java method com.metasolv.cartridge.oss.lu_navis_10_0.prov.LuNavisProv.delSubNetworkConnection.

MML commands/API callsmultilayerSubnetworkInterface. deactivateAndDelete (sncName, tolerableImpact, EMSFreedomLevel_T, tpsToModify, theSNC, errorReason)

Example SRQ outputSRQ ID SRQ_EVT EVT_TEXT------- -------- -------------------------------------------------------------------------------- 4 INFO Initial Reception of Work Order 4 INFO Current CSDL 'C_LU-NAVIS_10-0_DEL_SNC' is under provision 4 INFO ASDL A_LU-NAVIS_10-0_DEL_DSL-SNC for Lucent_Navis Route to NE Lucent_Navis

Table 12: A_LU-NAVIS_10-0_DEL_DSL-SNC


Type Class


S R

MANAGED_ELEMENT



S R



4 INFO ASDL A_LU-NAVIS_10-0_DEL_DSL-SNC Provisioning Request to Lucent_Navis 4 NE_CMD getManager 4 NE_CMD deactivateAndDeleteSNC: managedElement: COVEON02OL1, snc: mslv-PPPOverX 4 INFO Successful deactivateAndDeleteSNC execution 4 INFO ASDL Exit (LU_NAVIS_SUCCEED) Msg : Successful deactivateAndDeleteSNC execution 4 INFO Q Info: Queued: 11:50:51, Start: 11:50:51, Comp: 11:50:54 4 INFO SRQ 4 (Last CSDL C_LU-NAVIS_10-0_DEL_SNC) has Completed

A_LU-NAVIS_10-0_QRY_DSL-HIGHSPEEDReturns the SNC structure (copy of A_LU-NAVIS_10-0_QRY_DSL-SNC). It is implemented by the Java method com.metasolv.cartridge.oss.lu_navis_10_0.prov.LuNavisProv.querySubNetworkConnection.

MML commands/API callsmultilayerSubnetworkInterface.getSNC(sncName, snc);

Output parameters

CSDL Return Parameters for DSL SNC Connection Type

The following entries are explicit parameters that the cartridge will return as CSDL parameters.RATENATIVEEMSNAMENAMEOWNERUSERLABELDIRECTION

Table 13: A_LU-NAVIS_10-0_QRY_DSL-HIGHSPEED


Type Class


S R

MANAGED_ELEMENT



S R

ASDL commands


NETWORKROUTEDSNCSTATESNCTYPESTATICPROTECTIONLEVELREROUTEALLOWED

The following entries are explicit parameters that the cartridge will return as CSDL parameters should NAVIS send any parameters contained in the AEnd descriptor.AEND_EGRESSTRAFFICDESCRIPTORNAMEAEND_INGRESSTRAFFICDESCRIPTORNAMEAEND_LAYER[0]AEND_TERMINATIONMODE[0]AEND_TPNAME[0]AEND_[0][0]

The following entries are explicit parameters that the cartridge will return as CSDL parameters should NAVIS send any parameters contained in the ZEnd descriptor.ZEND_EGRESSTRAFFICDESCRIPTORNAMEZEND_INGRESSTRAFFICDESCRIPTORNAMEZEND_LAYER[0]ZEND_TERMINATIONMODE[0]ZEND_TPNAME[0]ZEND_[0][0]

The following entries are implicit parameters that the cartridge will return as CSDL parameters should NAVIS send any parameters contained in the Additional Info descriptor. The following are example output for Bridged Vlan connection.NAVIS_Connection_NameNAVIS_Connection_Activation_StateNAVIS_Upstream_ContractNAVIS_Downstream_ContractNAVIS_OAMTestable

NAVIS_Bridge_GroupNAVIS_Data_FilterNAVIS_Flow_ServiceNAVIS_Frame_TypeNAVIS_Packet_FlowsNAVIS_QoS_Interface_GroupNAVIS_Route_Filter NAVIS_Switching_TypeNAVIS_User_VLAN_IdNAVIS_VLAN_IdNAVIS_VLAN_TypeNAVIS_VPSwitched

The following entries are implicit parameters that the cartridge will return as CSDL parameters should NAVIS send any parameters contained in the Additional Info descriptor. The following are example output for PPP Over ATM/Ethernet connection.NAVIS_Connection_Name



NAVIS_Connection_TypeNAVIS_Connection_Activation_StateNAVIS_Upstream_ContractNAVIS_Downstream_ContractNAVIS_OAMTestable

NAVIS_PPPoX_ServerNAVIS_VPSwitched

Example SRQ outputSRQ ID SRQ_EVT EVT_TEXT------- -------- -------------------------------------------------------------------------------- 3 INFO Initial Reception of Work Order 3 INFO Current CSDL 'C_LU-NAVIS_10-0_QRY_VIDEO' is under provision 3 INFO ASDL A_LU-NAVIS_10-0_QRY_DSL-SNC for Lucent_Navis Route to NE Lucent_Navis 3 INFO ASDL A_LU-NAVIS_10-0_QRY_DSL-SNC Provisioning Request to Lucent_Navis 3 NE_CMD getManager 3 NE_CMD getSNC: managedElement: COVEON02OL1, snc: mslv-PPPOverX 3 NE_RESP ZEND_EGRESSTRAFFICDESCRIPTORNAME[0] = , AEND_[0][0] = , NAVIS_VPSwitched = 0, NAVIS_Downstream_Contract = td_ubr_dwn_pcr3008_mcr0, AEND_INGRESSTRAFFICDESCRIPTORNAME[0] = , SNCSTATE = 2, RATE = 98, ZEND_LAYER[0] = 98, 3 NE_RESP NAME = EMS=Lucent/NavisAccess;MultiLayerSubnetwork=COVEON02OL1;SubnetworkConnection=mslv-PPPOverX, ZEND_TPNAME[0] = EMS=Lucent/NavisAccess;ManagedElement=COVEON02OL1;PTP=/shelf=1/slot=8/port=2;CTP=/encapsulation=4096;=;, 3 NE_RESP NAVIS_Upstream_Contract = td_ubr_up_pcr800_mcr0, AEND_LAYER[0] = 98, NAVIS_Connection_Name = mslv-PPPOverX, NAVIS_PPPoX_Server = , ZEND_TERMINATIONMODE[0] = 0, OWNER = , NATIVEEMSNAME = , DIRECTION = 1, 3 NE_RESP NAVIS_Connection_Type = PPP over ATM/Ethernet, NAVIS_Connection_Activation_State= 1, ZEND_[0][0] = , NETWORKROUTED = 0, USERLABEL = , NAVIS_OAMTestable = 1, 3 NE_RESP AEND_TPNAME[0] = EMS=Lucent/NavisAccess;ManagedElement=COVEON02OL1;PTP=/shelf=1/slot=5/port=8;CTP=/atmnetworkinterface=1/vpi=0/vci=36;=;, AEND_TERMINATIONMODE[0] = 0, ZEND_INGRESSTRAFFICDESCRIPTORNAME[0] = , 3 NE_RESP AEND_EGRESSTRAFFICDESCRIPTORNAME[0] = , SNCTYPE = 0, STATICPROTECTIONLEVEL = 1,REROUTEALLOWED = 0, 3 INFO Successful getSNC execution 3 INFO ASDL Exit (LU_NAVIS_SUCCEED) Msg : Successful getSNC execution 3 INFO ASDL Current ASDL 'A_LU-NAVIS_10-0_QRY_DSL-SNC' is in 'Lucent_Navis' pending queue of SRQ 1 Completed 3 INFO Q Info: Queued: 11:50:35, Start: 11:50:35, Comp: 11:50:36 3 INFO SRQ 3 (Last CSDL C_LU-NAVIS_10-0_QRY_VIDEO) has Completed

ASDL commands


A_LU-NAVIS_10-0_QRY_DSL-PORTReturns the DSL TP structure. It is implemented by the Java method com.metasolv.cartridge.oss.lu_navis_10_0.prov.LuNavisProv.queryDSLPort.

MML commands/API callsmanagedElementInterface.getTP(tpName,tpHolder);

Output parameters

CSDL Return Parameters for DSL TP Connection Type The following entries are explicit parameters that the cartridge will return as CSDL parameters. NAMEUSERLABELNATIVEEMSNAMEOWNER valueEDGEPOINTDIRECTIONTYPEINGRESSTRAFFICDESCRIPTORNAMEEGRESSTRAFFICDESCRIPTORNAMECONNECTIONSTATETPPROTECTIONASSOCIATION

Table 14: A_LU-NAVIS_10-0_QRY_DSL-PORT


Type Class


S R

MANAGED_ELEMENT



S R


S R


S R



TERMINATIONMODE

The following entries are implicit parameters that the cartridge will return as CSDL parameters should NAVIS send any parameters contained in the Transmission descriptor. The following entry indicates an empty Transmission descriptor list.LAYER[0]

The following entries are implicit parameters that the cartridge will return as CSDL parameters should NAVIS send any parameters contained in the Additional Info descriptor.NAVIS_TP_AlcatelBoostNAVIS_TP_BinLoadingProfileNAVIS_TP_BitMapModeNAVIS_TP_BitSwappingNAVIS_TP_EnabledNAVIS_TP_GainNAVIS_TP_GroupNumberNAVIS_TP_LoopBackNAVIS_TP_MaxMarginEnabledNAVIS_TP_NameNAVIS_TP_SparingModeNAVIS_TP_ThresholdProfileNAVIS_TP_VPSwitchingVPI

DSLtypeDownshiftSnrMgnCfgFirstUsedSubCarrierInterleaveDelayCfgLastChangeLastUsedSubCarrierLatencyCfgLineCodeMaxDataRateCfgMaxDataRateFastCfgMaxDataRateSlowCfgMaxSnrMgnCfgMinDataRateCfgMinDataRateFastCfgMinDataRateSlowCfgMinDownshiftTimeCfgMinSnrMgnCfgMinUpshiftTimeCfgNAVIS_Operational_ModeOutputPowerPortRU-DownshiftSnrMgnCfgRU-FirstUsedSubCarrierRU-InterleaveDelayCfgRU-LastUsedSubCarrierRU-LatencyCfgRU-MaxDataRateCfgRU-MaxDataRateFastCfg

ASDL commands


RU-MaxDataRateSlowCfgRU-MaxSnrMgnCfgRU-MinDataRateCfgRU-MinDataRateFastCfgRU-MinDataRateSlowCfgRU-MinDownshiftTimeCfgRU-MinSnrMgnCfgRU-MinUpshiftTimeCfgRU-RateSelectModeCfgRU-SnrMgnCfgRU-UpshiftSnrCfgRU_OutputPowerRU_RateAdaptRatioCfgRateAdaptRatioCfgRateSelectModeCfgRunningSecsShelfSlotSnrMgnCfgSpectralDensityTrellisCodingCfgUpshiftSnrCfg

Example SRQ outputSRQ ID SRQ_EVT EVT_TEXT------- -------- --------------------------------------------------------------------------------1 INFO Initial Reception of Work Order1 INFO Current CSDL 'C_LU-NAVIS_10-0_QRY_PORT' is under provision1 INFO ASDL A_LU-NAVIS_10-0_QRY_DSL-PORT for Lucent_Navis Route to NE Lucent_Navis1 INFO ASDL A_LU-NAVIS_10-0_QRY_DSL-PORT Provisioning Request to Lucent_Navis1 NE_CMD getManager1 NE_CMD getTP: managedElement: COVEON02OL1, shelf: 1, slot: 5, port: 31 NE_RESP OutputPower = 20, RU-LastUsedSubCarrier = 31, RU-MinDataRateCfg = 512, MinDataRateSlowCfg = 128, MaxDataRateCfg = 1000, RU-MaxDataRateSlowCfg = 1000, TYPE = 0, SpectralDensity = 40, DownshiftSnrMgnCfg = 3, RU-MaxDataRateCfg = 512,1 NE_RESP RateAdaptRatioCfg = 100, RU-SnrMgnCfg = 6, MinDownshiftTimeCfg = 60, NAME = EMS=Lucent/NavisAccess;ManagedElement=COVEON02OL1;PTP=/shelf=1/slot=5/port=3, NAVIS_TP_VPSwitchingVPI = 15, Slot = 5, DIRECTION = 1, SnrMgnCfg = 6,1 NE_RESP RU-LatencyCfg = 1, InterleaveDelayCfg = 16, MinSnrMgnCfg = 6, RU-MinDownshiftTimeCfg = 60, RU-MinDataRateFastCfg = 256, MinUpshiftTimeCfg = 60, LatencyCfg = 1, RU-UpshiftSnrCfg = 3, NATIVEEMSNAME = 1:5:3, OWNER = ,1 NE_RESP NAVIS_TP_ThresholdProfile = default, MaxSnrMgnCfg = 31, FirstUsedSubCarrier = 32, NAVIS_TP_SparingMode = 0, RU_OutputPower = 13, NAVIS_TP_AlcatelBoost = 2, LastChange = 20050606225055.0Z, LineCode = auto-select,1 NE_RESP RU-FirstUsedSubCarrier = 6, RU-MinUpshiftTimeCfg = 60, MaxDataRateFastCfg = 1184, NAVIS_TP_Gain = 20-db, RU-DownshiftSnrMgnCfg = 3,



RunningSecs = 0, NAVIS_TP_BitMapMode = 0, Port = 3, NAVIS_TP_MaxMarginEnabled = 0,1 NE_RESP RU-MinDataRateSlowCfg = 128, UpshiftSnrCfg = 3, TERMINATIONMODE = 0, NAVIS_TP_BitSwapping = 0, LastUsedSubCarrier = 255, MaxDataRateSlowCfg = 8000, EGRESSTRAFFICDESCRIPTORNAME = , TrellisCodingCfg = 1, NAVIS_TP_Enabled = 1,1 NE_RESP NAVIS_Operational_Mode = unknown, RateSelectModeCfg = 1, INGRESSTRAFFICDESCRIPTORNAME = , RU-InterleaveDelayCfg = 16, RU-MinSnrMgnCfg = 6, NAVIS_TP_GroupNumber = 203, MinDataRateFastCfg = 256, USERLABEL = , RU-MaxDataRateFastCfg = 640,1 NE_RESP EDGEPOINT = true, LAYER[0] = 299, RU-MaxSnrMgnCfg = 31, RU-RateSelectModeCfg = 1, TPPROTECTIONASSOCIATION = 0, Shelf = 1, RU_RateAdaptRatioCfg = 100, NAVIS_TP_BinLoadingProfile = default, CONNECTIONSTATE = 0, NAVIS_TP_LoopBack = 0,1 NE_RESP MinDataRateCfg = 1000, DSLtype = Unknown, NAVIS_TP_Name = 1:5:3,1 INFO Successful getTP execution1 INFO ASDL Exit (LU_NAVIS_SUCCEED) Msg : Successful getTP execution1 INFO ASDL Current ASDL 'A_LU-NAVIS_10-0_QRY_DSL-PORT' is in 'Lucent_Navis' pending queue of SRQ 1 Completed1 INFO Q Info: Queued: 11:49:21, Start: 11:49:21, Comp: 11:49:221 INFO SRQ 1 (Last CSDL C_LU-NAVIS_10-0_QRY_PORT) has Completed

A_LU-NAVIS_10-0_QRY_DSL-SNCReturns the SNC structure (generic). It is implemented by the Java method com.metasolv.cartridge.oss.lu_navis_10_0.prov.LuNavisProv.querySubNetworkConnection.


Table 15: A_LU-NAVIS_10-0_QRY_DSL-SNC


Type Class


S R

MANAGED_ELEMENT



S R

ASDL commands


Output parameters

CSDL return parameter.s for DSL SNC connection type

The following entries are explicit parameters that the cartridge will return as CSDL parameters.RATENATIVEEMSNAMENAMEOWNERUSERLABELDIRECTIONNETWORKROUTEDSNCSTATESNCTYPESTATICPROTECTIONLEVELREROUTEALLOWED




NAVIS_Bridge_GroupNAVIS_Data_FilterNAVIS_Flow_ServiceNAVIS_Frame_TypeNAVIS_Packet_Flows



NAVIS_QoS_Interface_GroupNAVIS_Route_Filter NAVIS_Switching_TypeNAVIS_User_VLAN_IdNAVIS_VLAN_IdNAVIS_VLAN_TypeNAVIS_VPSwitched

The following entries are implicit parameters that the cartridge will return as CSDL parameters should NAVIS send any parameters contained in the Additional Info descriptor. The following are example output for PPP Over ATM/Ethernet connection.NAVIS_Connection_NameNAVIS_Connection_TypeNAVIS_Connection_Activation_StateNAVIS_Upstream_ContractNAVIS_Downstream_ContractNAVIS_OAMTestable


Example SRQ outputSRQ ID SRQ_EVT EVT_TEXT------- -------- -------------------------------------------------------------------------------- 3 INFO Initial Reception of Work Order 3 INFO Current CSDL 'C_LU-NAVIS_10-0_QRY_VIDEO' is under provision 3 INFO ASDL A_LU-NAVIS_10-0_QRY_DSL-SNC for Lucent_Navis Route to NE Lucent_Navis 3 INFO ASDL A_LU-NAVIS_10-0_QRY_DSL-SNC Provisioning Request to Lucent_Navis 3 NE_CMD getManager 3 NE_CMD getSNC: managedElement: COVEON02OL1, snc: mslv-PPPOverX 3 NE_RESP ZEND_EGRESSTRAFFICDESCRIPTORNAME[0] = , AEND_[0][0] = , NAVIS_VPSwitched = 0, NAVIS_Downstream_Contract = td_ubr_dwn_pcr3008_mcr0, AEND_INGRESSTRAFFICDESCRIPTORNAME[0] = , SNCSTATE = 2, RATE = 98, ZEND_LAYER[0] = 98, 3 NE_RESP NAME = EMS=Lucent/NavisAccess;MultiLayerSubnetwork=COVEON02OL1;SubnetworkConnection=mslv-PPPOverX, ZEND_TPNAME[0] = EMS=Lucent/NavisAccess;ManagedElement=COVEON02OL1;PTP=/shelf=1/slot=8/port=2;CTP=/encapsulation=4096;=;, 3 NE_RESP NAVIS_Upstream_Contract = td_ubr_up_pcr800_mcr0, AEND_LAYER[0] = 98, NAVIS_Connection_Name = mslv-PPPOverX, NAVIS_PPPoX_Server = , ZEND_TERMINATIONMODE[0] = 0, OWNER = , NATIVEEMSNAME = , DIRECTION = 1, 3 NE_RESP NAVIS_Connection_Type = PPP over ATM/Ethernet, NAVIS_Connection_Activation_State= 1, ZEND_[0][0] = , NETWORKROUTED = 0, USERLABEL = , NAVIS_OAMTestable = 1, 3 NE_RESP AEND_TPNAME[0] = EMS=Lucent/NavisAccess;ManagedElement=COVEON02OL1;PTP=/shelf=1/slot=5/port=8;CTP=/atmnetworkinterface=1/vpi=0/vci=36;=;, AEND_TERMINATIONMODE[0] = 0, ZEND_INGRESSTRAFFICDESCRIPTORNAME[0] = ,

ASDL commands


3 NE_RESP AEND_EGRESSTRAFFICDESCRIPTORNAME[0] = , SNCTYPE = 0, STATICPROTECTIONLEVEL = 1,REROUTEALLOWED = 0, 3 INFO Successful getSNC execution 3 INFO ASDL Exit (LU_NAVIS_SUCCEED) Msg : Successful getSNC execution 3 INFO ASDL Current ASDL 'A_LU-NAVIS_10-0_QRY_DSL-SNC' is in 'Lucent_Navis' pending queue of SRQ 1 Completed 3 INFO Q Info: Queued: 11:50:35, Start: 11:50:35, Comp: 11:50:36 3 INFO SRQ 3 (Last CSDL C_LU-NAVIS_10-0_QRY_VIDEO) has Completed

A_LU-NAVIS_10-0_QRY_DSL-VIDEOReturns the SNC structure (copy of A_LU-NAVIS_10-0_QRY_DSL-SNC). It is implemented by the Java method com.metasolv.cartridge.oss.lu_navis_10_0.prov.LuNavisProv.querySubNetworkConnection.


Output parameters

CSDL return parameter.s for DSL SNC connection type The following entries are explicit parameters that the cartridge will return as CSDL parameters.RATENATIVEEMSNAMENAMEOWNERUSERLABELDIRECTIONNETWORKROUTEDSNCSTATE

Table 16: A_LU-NAVIS_10-0_QRY_DSL-VIDEO


Type Class


S R

MANAGED_ELEMENT



S R



SNCTYPESTATICPROTECTIONLEVELREROUTEALLOWED




NAVIS_Bridge_GroupNAVIS_Data_FilterNAVIS_Flow_ServiceNAVIS_Frame_TypeNAVIS_Packet_FlowsNAVIS_QoS_Interface_GroupNAVIS_Route_Filter NAVIS_Switching_TypeNAVIS_User_VLAN_IdNAVIS_VLAN_IdNAVIS_VLAN_TypeNAVIS_VPSwitched

The following entries are implicit parameters that the cartridge will return as CSDL parameters should NAVIS send any parameters contained in the Additional Info descriptor. The following are example output for PPP Over ATM/Ethernet connection.NAVIS_Connection_NameNAVIS_Connection_TypeNAVIS_Connection_Activation_State

User defined exit types (tbl_user_error)


NAVIS_Upstream_ContractNAVIS_Downstream_ContractNAVIS_OAMTestable


Example SRQ outputSRQ ID SRQ_EVT EVT_TEXT------- -------- -------------------------------------------------------------------------------- 3 INFO Initial Reception of Work Order 3 INFO Current CSDL 'C_LU-NAVIS_10-0_QRY_VIDEO' is under provision 3 INFO ASDL A_LU-NAVIS_10-0_QRY_DSL-SNC for Lucent_Navis Route to NE Lucent_Navis 3 INFO ASDL A_LU-NAVIS_10-0_QRY_DSL-SNC Provisioning Request to Lucent_Navis 3 NE_CMD getManager 3 NE_CMD getSNC: managedElement: COVEON02OL1, snc: mslv-PPPOverX 3 NE_RESP ZEND_EGRESSTRAFFICDESCRIPTORNAME[0] = , AEND_[0][0] = , NAVIS_VPSwitched = 0, NAVIS_Downstream_Contract = td_ubr_dwn_pcr3008_mcr0, AEND_INGRESSTRAFFICDESCRIPTORNAME[0] = , SNCSTATE = 2, RATE = 98, ZEND_LAYER[0] = 98, 3 NE_RESP NAME = EMS=Lucent/NavisAccess;MultiLayerSubnetwork=COVEON02OL1;SubnetworkConnection=mslv-PPPOverX, ZEND_TPNAME[0] = EMS=Lucent/NavisAccess;ManagedElement=COVEON02OL1;PTP=/shelf=1/slot=8/port=2;CTP=/encapsulation=4096;=;, 3 NE_RESP NAVIS_Upstream_Contract = td_ubr_up_pcr800_mcr0, AEND_LAYER[0] = 98, NAVIS_Connection_Name = mslv-PPPOverX, NAVIS_PPPoX_Server = , ZEND_TERMINATIONMODE[0] = 0, OWNER = , NATIVEEMSNAME = , DIRECTION = 1, 3 NE_RESP NAVIS_Connection_Type = PPP over ATM/Ethernet, NAVIS_Connection_Activation_State= 1, ZEND_[0][0] = , NETWORKROUTED = 0, USERLABEL = , NAVIS_OAMTestable = 1, 3 NE_RESP AEND_TPNAME[0] = EMS=Lucent/NavisAccess;ManagedElement=COVEON02OL1;PTP=/shelf=1/slot=5/port=8;CTP=/atmnetworkinterface=1/vpi=0/vci=36;=;, AEND_TERMINATIONMODE[0] = 0, ZEND_INGRESSTRAFFICDESCRIPTORNAME[0] = , 3 NE_RESP AEND_EGRESSTRAFFICDESCRIPTORNAME[0] = , SNCTYPE = 0, STATICPROTECTIONLEVEL = 1,REROUTEALLOWED = 0, 3 INFO Successful getSNC execution 3 INFO ASDL Exit (LU_NAVIS_SUCCEED) Msg : Successful getSNC execution 3 INFO ASDL Current ASDL 'A_LU-NAVIS_10-0_QRY_DSL-SNC' is in 'Lucent_Navis' pending queue of SRQ 1 Completed 3 INFO Q Info: Queued: 11:50:35, Start: 11:50:35, Comp: 11:50:36 3 INFO SRQ 3 (Last CSDL C_LU-NAVIS_10-0_QRY_VIDEO) has Completed

User defined exit types (tbl_user_error)The user defined exit types are placed in file Lucent_NavisAccess_10_0_UserExitTypes.cfg. The following table lists the contents of this file. The user has full control of this file.



Additional error codes may be inserted into this file as and when they are discovered. The corresponding user exit type must exist in tbl_user_error and its respective ASAP exit type.

Note: If this file is removed or its path is incorrect, the user exit type will be defaulted to NO_MATCH_FOUND and is mapped to ASAP exit type FAIL.

Table 17: Contents of NAVISACCESS_USERExitTypes.cfg

LUCENT ERROR CODE USER EXIT TYPE (20 chars) ASAP Exit Code

"No exception thrown "LU_NAVIS_SUCCEED SUCCEED

0 LU_NAVIS_NOT_IMPL FAIL

1 LU_NAVIS_INTERN_ERR FAIL

2 LU_NAVIS_BAD_DATA FAIL

3 LU_NAVIS_OBJ_IN_USE FAIL

4 LU_NAVIS_TP_INVALID_EP FAIL

5 LU_NAVIS_ENT_NOT_FND FAIL

6 LU_NAVIS_TSLOT_USE FAIL

7 LU_NAVIS_PROTECTION FAIL

8 LU_NAVIS_INVALID_ST FAIL

9 LU_NAVIS_NO_COMPLY FAIL

10 LU_NAVIS_ACC_DENIED RETRY_DIS

11 LU_NAVIS_CAPACITY FAIL

12 LU_NAVIS_COMM_LOSS RETRY_DIS

13 LU_NAVIS_ITERATORS FAIL

14 LU_NAVIS_ROUTING FAIL

15 LU_NAVIS_LBL_IN_USE FAIL

IOException RETRY_DIS RETRY_DIS

ConnectionException GEN_ERROR FAIL

Exception GEN_ERROR FAIL

User defined exit types (tbl_user_error)


The following table identifies the error that a particular API can throw.

The following table describes handling of non-Lucent errors.

Table 18: API errors

API Call Throws Error Reason

getEMSSession EXCPT_INTERNAL_ERROR LU_NAVIS_INTERN_ERR

EXCPT_INVALID_INPUT LU_NAVIS_BAD_DATA

EXCPT_ACCESS_DENIED LU_NAVIS_ACC_DENIED

getTP

setTPData

getSNC

deactivateAndDelete

EXCPT_INTERNAL_ ERROR LU_NAVIS_INTERN_ERR


EXCPT_ENTITY_NOT_FOUND LU_NAVIS_ENT_NOT_FND

EXCPT_NE_COMM_LOSS LU_NAVIS_COMM_LOSS

createAndActivate EXCPT_INTERNAL_ERROR LU_NAVIS_INTERN_ERR


EXCPT_ENTITY_NOT_FOUND LU_NAVIS_ENT_NOT_FND

EXCPT_NE_COMM_LOSS LU_NAVIS_COMM_LOSS

EXCPT_USERLABEL_IN_USE LU_NAVIS_LBL_IN_USE

EXCPT_OBJECT_IN_USE LU_NAVIS_OBJ_IN_USE

Table 19: Non-Lucent errors

ExceptionUSER EXIT TYPE (20 characters)

ASAP Exit Code

IOException RETRY_DIS RETRY_DISC

ConnectionException GEN_ERROR FAIL

Exception GEN_ERROR FAIL


4

Service Definition

The Lucent NavisAccess cartridge contains a set of CSDLs that map to one or more ASDL commands. You can also create additional CSDLs that map to existing and newly-created ASDLs. An upstream system can assemble any of these CSDL commands onto a work order for provisioning.

This chapter presents detailed information on the CSDL parameters that we provide in this cartridge. The following table lists and describes the type of parameter information that is included.


Item Description

Parameter Name Identifies the parameter that is configured for the stated service.

Description Describes the parameter.

Range Describes or lists the range of values that can be used to satisfy this parameter.

Default Value Configures a default value for the parameter so that it is not mandatory for the upstream system to provide a value.

Chapter 4: Service Definition


For a detailed description of the Required and Optional parameter classifications, refer to the ASAP Administration Guide.

Common Service Description Layer (CSDL) commands

This cartridge provides the following CSDL commands:

Type Indicates one of the following parameter types:

S—Scalar, specifies the parameter label transmitted on the ASDL command. Scalar parameters are conventional name-value pair parameters.C—Compound, specifies the base name of the compound parameter transmitted on the ASDL command. A compound parameter contains structures or arrays of information that are represented by a particular structure name or compound parameter name. Each compound parameter can contain a large number of elements. If you use compound parameters, you only require a single entry in the ASAP translation tables to call the compound parameter and all its associated parameter elements.I—Indexed, identifies a parameter that contains a sequential numerical index value to tell the SARM that it should execute the same operation (for example, an ASDL command) for all occurrences of that index. Consequently, if there are several options on a particular CSDL command (OPT1, OPT2, OPT3, etc.), you can specify the OPT parameter as an indexed parameter. When you specify the OPT parameter as an indexed parameter, the SARM generates several occurrences of that same ASDL command and each command has a different value for the option being transmitted to the NEP.

For more information on parameter types, refer to the ASAP Developer’s Reference.

Class Indicates one of the following parameter classifications:

R—Required scalar parameterO—Optional scalar parameterC—Required compound parameterN—Optional compound parameterM—Mandatory indexed parameterI—Optional indexed parameterS—Parameter count


Item Description



C_LU-NAVIS_10-0_CREATE_SNCC_LU-NAVIS_10-0_DEL_SNCC_LU-NAVIS_10-0_MOD_HIGHSPEEDC_LU-NAVIS_10-0_MOD_PORTC_LU-NAVIS_10-0_MOD_VIDEOC_LU-NAVIS_10-0_QRY_HIGHSPEEDC_LU-NAVIS_10-0_QRY_PORTC_LU-NAVIS_10-0_QRY_PROFILEC_LU-NAVIS_10-0_QRY_VIDEO

C_LU-NAVIS_10-0_CREATE_SNCCreates a new SNC.

Table 21: C_LU-NAVIS_10-0_CREATE_SNC


Type Class

CONNECTION_STATE (NAVIS_Connection_Activation_State). If the connection is enabled or disabled.

0 (no), 1 (yes) S O

DOWNSTREAM_CONTRACT


S O

EGRESS_PORT The port on the card which is to be configured.

S O

EGRESS_SHELF The shelf on which the configuration is required.

S O

EGRESS_SLOT The slot containing the card whose port is to be configured.

S O



EGRESS_VCI Virtual Connection Identifier

S O

EGRESS_VPI Virtual Path Identifier S O

MANAGED_ELEMENT


NE_ID_LU-NAVIS Network element (NavisAccess EMS).

S R


0 (no), 1 (yes) S O


S R


S O

PROTOCOL_IDENTIFIER


S O


S R


S R


S R



Type Class



Mapping to ASDLs

The following table illustrates the CSDL to ASDL mapping for this service.

C_LU-NAVIS_10-0_DEL_SNCDeletes an SNC.


S O

UPSTREAM_CONTRACT


S O

VCI Virtual Connection Identifier

36 S R

VPI Virtual Path Identifier 0 S R


0 (no), 1 (yes) S O

Table 22: CSDL to ASDL Mapping

CSDL ASDL

C_LU-NAVIS_10-0_CREATE_SNC A_LU-NAVIS_10-0_CREATE_DSL-SNC

Table 23: C_LU-NAVIS_10-0_DEL_SNC


Type Class

MANAGED_ELEMENT




Type Class



Mapping to ASDLs


C_LU-NAVIS_10-0_MOD_HIGHSPEEDModifies an sub-network connection being used for Data traffic.


S R


S R


CSDL ASDL

C_LU-NAVIS_10-0_DEL_SNC A_LU-NAVIS_10-0_DEL_DSL-SNC

Table 25: C_LU-NAVIS_10-0_MOD_HIGHSPEED


Type Class


DOWNSTREAM_CONTRACT


S O

MANAGED_ELEMENT



Table 23: C_LU-NAVIS_10-0_DEL_SNC


Type Class



























S R




Type Class



Mapping to ASDLs





S R


S R


S O

UPSTREAM_CONTRACT


S O



CSDL ASDL

C_LU-NAVIS_10-0_MOD_HIGHSPEED A_LU-NAVIS_10-0_QRY_DSL-SNC

A_LU-NAVIS_10-0_DEL_DSL-SNC

A_LU-NAVIS_10-0_ADD_DSL-HIGHSPEED



Type Class



C_LU-NAVIS_10-0_MOD_PORTModifies a DSL TP port.

Mapping to ASDLs


Table 27: C_LU-NAVIS_10-0_MOD_PORT


Type Class

MANAGED_ELEMENT


NAVIS_TEMPLATE (TransmissionDescriptorPointer). Connection template name. Indicates the template that must be used while configuring the PTP.

S O


S R


S R


S R


S R


CSDL ASDL

C_LU-NAVIS_10-0_MOD_PORT A_LU-NAVIS_10-0_CONFIG_DSL-PORT



C_LU-NAVIS_10-0_MOD_VIDEOModifies an sub-network connection being used for Video traffic.

Table 29: C_LU-NAVIS_10-0_MOD_VIDEO


Type Class


DOWNSTREAM_CONTRACT


S O

MANAGED_ELEMENT













S R





S R



Mapping to ASDLs


C_LU-NAVIS_10-0_QRY_HIGHSPEEDReturns the SNC structure.


S R


S O

UPSTREAM_CONTRACT


S O



CSDL ASDL

C_LU-NAVIS_10-0_MOD_VIDEO A_LU-NAVIS_10-0_QRY_DSL-SNC

A_LU-NAVIS_10-0_DEL_DSL-SNC

A_LU-NAVIS_10-0_ADD_DSL-VIDEO

Table 31: C_LU-NAVIS_10-0_QRY_HIGHSPEED


Type Class

MANAGED_ELEMENT


Table 29: C_LU-NAVIS_10-0_MOD_VIDEO


Type Class



Mapping to ASDLs


C_LU-NAVIS_10-0_QRY_PORTReturns the DSL TP structure.


S R


S R


CSDL ASDL

C_LU-NAVIS_10-0_QRY_HIGHSPEED A_LU-NAVIS_10-0_QRY_DSL-SNC

Table 33: C_LU-NAVIS_10-0_QRY_PORT


Type Class

MANAGED_ELEMENT



S R


S R


S R


S R

Table 31: C_LU-NAVIS_10-0_QRY_HIGHSPEED


Type Class



Mapping to ASDLs


C_LU-NAVIS_10-0_QRY_PROFILEReturns the DSL TP and SNC structure for port, video and highspeed.


CSDL ASDL

C_LU-NAVIS_10-0_QRY_PORT A_LU-NAVIS_10-0_QRY_DSL-PORT

Table 35: C_LU-NAVIS_10-0_QRY_PROFILE


Type Class

MANAGED_ELEMENT



S R


S R


S R


S R

SUBNET_NAME_VIDEO

Subnetwork connection name.

S R



Mapping to ASDLs


C_LU-NAVIS_10-0_QRY_VIDEOReturns the SNC structure.

Mapping to ASDLs



CSDL ASDL

C_LU-NAVIS_10-0_QRY_PROFILE A_LU-NAVIS_10-0_QRY_DSL-PORT

A_LU-NAVIS_10-0_QRY_DSL-VIDEO

A_LU-NAVIS_10-0_QRY_DSL-HIGHSPEED

Table 37: C_LU-NAVIS_10-0_QRY_VIDEO


Type Class

MANAGED_ELEMENT



S R


S R


CSDL ASDL

C_LU-NAVIS_10-0_QRY_VIDEO A_LU-NAVIS_10-0_QRY_DSL-SNC

5

Configuring ASAP to Support Additional NE Instances

You can configure ASAP to support the Lucent NavisAccess DSL - NEP configuration using the Service Activation Configuration Tool (SACT). Refer to the ASAP Administration Guide fore more information.

Below is an example of the Activation.Configuration.XML file for the Lucent NavisAccess cartridge.<?xml version="1.0" encoding="UTF-8"?><activationConfig xmlns="http://www.metasolv.com/ServiceActivation/2003/ActivationConfig" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

<connectionPool name="POOL_LUC"><device name="Lucent_Navis_dev1">

<environment>MY_ASAP_SYS</environment><lineType>CORBA_CONNECTION</lineType>

</device><device name="Lucent_Navis_dev2">

<environment>MY_ASAP_SYS</environment><lineType>CORBA_CONNECTION</lineType>

</device></connectionPool><element name="LU-NAVIS-HOST">

<technology>LUCENT-NAVIS-DSL</technology><softwareLoad>10.0</softwareLoad><nepServerName>$NEP</nepServerName><primaryPool>POOL_LUC</primaryPool><maximumConnections>1</maximumConnections><dropTimeout>2</dropTimeout><spawnThreshold>0</spawnThreshold><killThreshold>0</killThreshold><routingElement name="LU-NAVIS-HOST">

<atomicService/></routingElement><communicationParameter>

<label>EMSINSTANCE</label><value>

<value>ontario</value></value><description>Name of EMS instance as its configured in the Naming

Server</description>

Chapter 5: Configuring ASAP to Support Additional NE Instances


<deviceName>Lucent_Navis_dev1</deviceName><lineType>CORBA_CONNECTION</lineType>

</communicationParameter><communicationParameter>

<label>EMSINSTANCE</label><value>

<value>quebec</value></value><description>Name of EMS instance as its configured in the Naming

Server</description><deviceName>Lucent_Navis_dev2</deviceName><lineType>CORBA_CONNECTION</lineType>


<label>LISTENER_PORT</label><value>

<value>38000</value></value><description>ListenerPort for this device</description><deviceName>Lucent_Navis_dev1</deviceName><lineType>CORBA_CONNECTION</lineType>


<label>LISTENER_PORT</label><value>

<value>38001</value></value><description>ListenerPort for this device</description><deviceName>Lucent_Navis_dev2</deviceName><lineType>CORBA_CONNECTION</lineType>


<label>NS_INSTANCE</label><value>

<value>/config/NS_INSTANCE_ontario.ior</value></value><description>Interoperable Object Reference. This file is relative

to ASAP_BASE directory.</description><deviceName>Lucent_Navis_dev1</deviceName><lineType>CORBA_CONNECTION</lineType>


<label>NS_INSTANCE</label><value>

<value>/config/NS_INSTANCE_quebec.ior</value></value><description>Interoperable Object Reference. This file is relative

to ASAP_BASE directory.</description><deviceName>Lucent_Navis_dev2</deviceName><lineType>CORBA_CONNECTION</lineType>



<label>SECURE_USER_PASS</label><value>

<value>NAVISACCESS1</value></value><description>Key to retreive the userid/passwd from the secure

table</description><deviceName>Lucent_Navis_dev1</deviceName><lineType>CORBA_CONNECTION</lineType>


<label>SECURE_USER_PASS</label><value>

<value>NAVISACCESS2</value></value><description>Key to retreive the userid/passwd from the secure

table</description><deviceName>Lucent_Navis_dev2</deviceName><lineType>CORBA_CONNECTION</lineType>


<label>USERNAME</label><value>

<value>navis_userid</value></value><description>User Name</description><deviceName>Lucent_Navis_dev1</deviceName><lineType>CORBA_CONNECTION</lineType>


<label>USERNAME</label><value>

<value>navis_userid</value></value><description>User Name</description><deviceName>Lucent_Navis_dev2</deviceName><lineType>CORBA_CONNECTION</lineType>


<label>PASSWORD</label><value>

<value>navis_password</value></value><description>Password</description><deviceName>Lucent_Navis_dev1</deviceName><lineType>CORBA_CONNECTION</lineType>


<label>PASSWORD</label><value>

<value>navis_password</value></value><description>Password</description>



<deviceName>Lucent_Navis_dev2</deviceName><lineType>CORBA_CONNECTION</lineType>


<label>USE_SECURE_DATA</label><value>

<value>FALSE</value></value><description>Flag indicating whether Secure Login Username and

Password Required</description><deviceName>COMMON_DEVICE_CFG</deviceName><lineType>CORBA_CONNECTION</lineType>


<label>NE_DIALOG_LOGGING</label><value>

<value>TRUE</value></value><description>Flag to turn On or Off logging of API commands and

responses</description><deviceName>COMMON_DEVICE_CFG</deviceName><lineType>CORBA_CONNECTION</lineType>


<label>ORBINITIALHOST</label><value>

<value>127.0.0.1</value></value><description>Visibroker Host IP address (obsolete now)</

description><deviceName>COMMON_DEVICE_CFG</deviceName><lineType>CORBA_CONNECTION</lineType>


<label>ORBINITIALPORT</label><value>

<value>1771</value></value><description>Visibroker Host Port (obsolete now)</description><deviceName>COMMON_DEVICE_CFG</deviceName><lineType>CORBA_CONNECTION</lineType>


<label>ORB_PROPERTIES</label><value>

<value>/config/Lucent_Orb_Properties.cfg</value></value><description>Property file containing orb parameters. This file is

relative to the ASAP_BASE directory.</description><deviceName>COMMON_DEVICE_CFG</deviceName><lineType>CORBA_CONNECTION</lineType>

</communicationParameter>

Extracting source files


<communicationParameter><label>USER_ERROR_TYPES_FILE</label><value>

<value>/config/Lucent_Navis_UserExitTypes.cfg</value></value><description>The User Exit types file. This file is relative to the

ASAP_BASE directory.</description><deviceName>COMMON_DEVICE_CFG</deviceName><lineType>CORBA_CONNECTION</lineType>


<label>LAYER_RATE_FILE</label><value>

<value>/config/Lucent_LayerRate.cfg</value></value><description>The Layer Rate file used to map the connection type to

the layer rate. This file is relative to the ASAP_BASE directory.</description>

<deviceName>COMMON_DEVICE_CFG</deviceName><lineType>CORBA_CONNECTION</lineType>


<label>PROTOCOL_IDENTIFIER_TYPE_FILE</label><value>

<value>/config/Lucent_ProtocolIdentifier.cfg</value></value><description>The ConnectionType file used to map connection types

that are retrieved from Navis and then mapped to their correct syntax for submission back to Navis.</description>

<deviceName>COMMON_DEVICE_CFG</deviceName><lineType>CORBA_CONNECTION</lineType>

</communicationParameter></element>

</activationConfig>

Extracting source filesBefore you can access an XML file to modify it, you must extract it from the sar file. Use the following procedure to extract source files from the sar file.

To extract source files

1. If necessary, create a repository directory under /Lucent, copy the .sar file to the new directory and un-jar the sar file, as described by Step 1 through Step 4 in “Modifying Lucent_NavisAccess_connection.xml” on page 12.

2. After you un-jar the sar file, you can access the XML files.



Loading a new XML fileWhen you finish modifying an XML, you must create a new sar file, then restart the cartridge using the new file.

Follow the instructions in “Modifying Lucent_NavisAccess_connection.xml” on page 12 for directions on how to load a new XML file.

lucent navisaccess cartridge guide · c_lu-navis_10-0_qry_profile ... element (ne) interface to...

Documents