Need an account?

Create an account

Help

Cisco Prime Optical GateWay/CORBA User Guide and Programmer Manual, 9.3

Book Contents

Find Matches in This Book

Available Languages

Download Options

Book Title

Cisco Prime Optical GateWay/CORBA User Guide and Programmer Manual, 9.3

Chapter Title

Appendix C: OSS Use Cases and Client Development

PDF - Complete Book (5.39 MB) PDF - This Chapter (129.0 KB)
View with Adobe Reader on a variety of devices

Results

Updated:: February 1, 2018

Chapter: Appendix C: OSS Use Cases and Client Development

C.1 Use Cases to Resynchronize the NMS from the EMS
C.2 Developing a GateWay/CORBA Client

OSS Use Cases and Client Development

This appendix lists interceptors and use cases to resynchronize the NMS from the EMS. This appendix includes the following sections:

C.1 Use Cases to Resynchronize the NMS from the EMS

Table C-1 , Table C-2 , and Table C-3 list use cases to resynchronize the NMS from the EMS.

Table C-1 Use Cases to Resynchronize the NMS from the EMS
Information	Detail
Name	The NMS retrieves Cisco Prime Optical information.
Summary	The NMS retrieves all EMS and ME alarms and information for existing multilayer subnetworks, MEs, PTPs, CTPs, SNCs, and protection groups from Cisco Prime Optical GateWay/CORBA interfaces.
Actor(s)	NMS.
Preconditions	The NMS locates the EmsSessionFactory object and obtains references to EMSMgr_I, MultiLayerSubnetworkMgr_I, ManagedElementMgr_I, EquipmentInventoryMgr_I, MaintenanceMgr_I, ProtectionMgr_I, and PerformanceManagementMgr_I interfaces.
Begins When	The NMS sends a request to retrieve all of the Prime Optical information.
Description	The NMS does the following to request information from the GateWay/CORBA interface: 1. Uses the emsMgr::EMSMgr_I:: getAllEMSSystemActiveAlarms interface to request all EMS alarms. 2. Uses the emsMgr::EMSMgr_I:: getAllTopLevelSubnetworks interface to request all multilayer subnetworks in Prime Optical. Prime Optical returns a list of MultiLayerSubnetwork_T objects with detailed information about a multilayer subnetwork. 3. Uses the emsMgr::EMSMgr_I:: getAllTopLevelTopologicalLinks interface to request all topological links across multiple multilayer subnetworks. Prime Optical returns a list of TopologicalLink_T objects with detailed information about a topological link. 4. For each MultiLayerSubnetwork_T object, Prime Optical uses the multiLayerSubnetwork::MultiLayerSubnetworkMgr_I:: getAllManagedElements interface to request all MEs that belong to that multilayer subnetwork. Prime Optical returns a list of ManagedElement_T objects with detailed information about an ME. For each ManagedElement object, executes the use case “NMS Resynchronizes Information Specific to a Managed Element.” 5. Uses the multiLayerSubnetwork::MultiLayerSubnetworkMgr_I:: getAllVLANs interface to request all VLANs associated with the multilayer subnetwork.
Ends When	The NMS retrieves all Prime Optical information.
Exceptions	Refer to the exceptions thrown by the individual interface method.
Post Conditions	The NMS synchronizes with Prime Optical. The NMS registers with Prime Optical to retrieve notifications related to changes in the managed object on Prime Optical, new alarms, and TCAs.
Traceability	—

Table C-2 NMS Resynchronizes Information Specific to a Managed Element
Information	Detail
Name	The NMS retrieves Prime Optical information specific to the ME.
Summary	The NMS retrieves all PTP, CTP, SNC, and protection group information for the specific ME.
Actor(s)	NMS.
Preconditions	The NMS obtains references to ManagedElementMgr_I, EquipmentInventoryMgr_I, MaintenanceMgr_I, ProtectionMgr_I, and PerformanceManagementMgr_I interfaces. The NMS also obtains the ME name.
Begins When	The NMS sends a request to retrieve all information about an ME. The NMS identifies the name of the ME for which to retrieve information.
Description	The NMS does the following to request information from the GateWay/CORBA interface: 1. Uses the managedElementManager::ManagedElementManager_I:: getAllActiveAlarms interface to request all current alarms on the ME. 2. Uses the equipment::EquipmentInventoryMgr_I:: getAllEquipment interface to request all existing equipment on the ME. Prime Optical returns a list of EquipmentHolder_T objects with detailed information about equipment holders and equipment on the ME. 3. For the equipment information retrieved in EquipmentorHolder_T object, uses the equipment::EquipmentInventoryMgr_I:: getAllSupportedPTPs interface to request all supported PTPs on the equipment. Prime Optical returns a list of TerminationPoint_T objects with detailed PTP information, such as SDH or SONET port, admin state, service state, line code, frame format, and so on. 4. For each TerminationPoint_T object, executes the “NMS Resynchronizes Information Specific to TerminationPoint” use case. 5. Uses the managedElementManager::ManagedElementManager_I:: getAllSNCs interface to request all SNCs originating, terminating, or passing through the ME. Prime Optical returns a list of SubnetworkConnection_T objects with detailed SNC information, such as layer rate, SNC state, SNC protection state, a-end CTP, z-end CTP, and so on. 6. Uses the protection::ProtectionMgr_I:: getAllProtectionGroups interface to request all protection groups created on the ME. Prime Optical returns a list of ProtectionGroup_T objects with detailed protection group information, such as 1:1, 1+1, or 2F-BLSR; revertive or nonrevertive; and so on.
Ends When	The NMS retrieves all ME-specific information.
Exceptions	Refer to the exceptions thrown by the individual interface method.
Post Conditions	The NMS synchronizes information about an ME with Prime Optical.
Traceability	—

Table C-3 NMS Resynchronizes Information Specific to a Termination Point
Information	Detail
Name	The NMS retrieves Prime Optical information specific to the termination point.
Summary	The NMS retrieves all loopback and threshold information for PTPs and CTPs used by the SNC.
Actor(s)	NMS.
Preconditions	The NMS obtains references to ManagedElementMgr_I, MaintenanceMgr_I, and PerformanceManagementMgr_I interfaces. The NMS also obtains a list of PTPs.
Begins When	The NMS sends a request to retrieve all threshold and loopback information on a PTP and on any in-use CTPs. The NMS identifies the name and type (PTP/CTP) of the TP for which to retrieve information.
Description	The NMS does the following to request information from the GateWay/CORBA interface: 1. Uses the maintenanceOps::MaintenanceMgr_I:: getActiveMaintenanceOperations interface to request all loopback information on the TP. Prime Optical returns a list of CurrentMaintenanceOperation_T objects with detailed information about the type of loopback set on the PTP, if any. Prime Optical supports two types of loopback, FACILITY_LOOPBACK and TERMINAL_LOOPBACK. If there are no loopbacks set on the TP, the returned list is empty. 2. Uses the performance::PerformanceManagementMgr_I:: getTCATPParameter interface to request the threshold values set for all PM thresholds on the given TP object. Prime Optical returns the TCAParameter_T object with detailed information about all PM threshold name/value pairs for the PTP. 3. For each PTP that the NMS specifies as the TP, uses the managedElementManager::ManagedElementManager_I:: getContainedInUseTPs interface to request all CTPs contained in the PTP participating in an SNC. Prime Optical returns a list of TerminationPoint_T objects with detailed information about the CTPs participating in an SNC and the associated provisioning details, such as IPPM monitor status, J1 path trace status, and so on. 4. For each CTP object, uses the performance::PerformanceManagementMgr_I:: getTCATPParameter interface to request threshold information. Prime Optical returns a list of TCAParameter_T objects with detailed information about the PM threshold name/value pairs for the CTP.
Ends When	The NMS retrieves loopback and threshold information for all PTPs and CTPs.
Exceptions	Refer to the exceptions thrown by the individual interface method.
Post Conditions	The NMS synchronizes information about a TP object with Prime Optical.
Traceability	—

C.2 Developing a GateWay/CORBA Client

GateWay/CORBA implements APIs defined by the TeleManagement Forum’s Multi Technology Network Management (MTNM) group. These APIs are defined for communication between an NMS and the EMS. The NMS must develop a client application that uses these APIs. The following sections describe the tools required for developing a client application. Sample code is provided.

C.2.1 Recommended Tools

You can develop the CORBA client on UNIX or PC platforms. Cisco recommends the following development tools:

Sun Microsystems Java Development Kit (JDK) 1.6 (available at http://java.sun.com/)
jacORB 2.x

C.2.2 Sample Code in Java

A typical CORBA client application involves the following steps:

Step 1 Initialize the client connection to the object request broker (ORB).

Step 2 Obtain a reference to the naming service.

Step 3 Resolve the reference to EMSSessionFactory. See Get Reference to EMSSessionFactory.

Step 4 Implement NmsSession_IOperations. See Implement NmsSession_IOperations.

Step 5 Retrieve EmsSession by supplying the username and password. See Log In and Retrieve EmsSession.

Step 6 Query EmsSession and obtain a list of managers available for operations. See Retrieve List of Managers.

Step 7 Invoke the desired method on that manager. See getEMS Operation on EMS Manager.

If you want your client to receive notifications from GateWay/CORBA, the following additional steps are required:

Step 8 Obtain a reference to an EventChannel object in the notification server in Step 2.

Step 9 Obtain a ConsumerAdmin object reference.

Step 10 Invoke obtain_notification_push_consumer() on the SupplierAdmin object, specifying CosNotifyChannelAdmin::STRUCTURED_EVENT as a parameter. This operation returns a reference to the StructuredProxyPushSupplier.

Step 11 Implement an instance of StructuredPushConsumer (defined by the OMG).

Step 12 Invoke the connect_structured_push_consumer() operation on the StructuredProxyPushSupplier object to connect the StructuredPushConsumer implementation object to the notification channel.

Step 13 Monitor incoming notifications.

The following sections show sample Java code for the steps required to develop a client application.

Note The sample code shown is for illustrative purposes only; the code might not compile as shown. The sample code does not handle all exceptions.

C.2.2.1 Initialize the Client Connection

// Import OMG packages

import org.omg.CORBA.IntHolder;

import org.omg.CORBA.ORB;

import org.omg.CORBA.Policy;

// Import naming context packages.

import org.omg.CosNaming.NameComponent;

import org.omg.CosNaming.NamingContextExt;

import org.omg.CosNaming.NamingContextExtHelper;

// Import notify channel and event service packages.

import org.omg.CosEventChannelAdmin.AlreadyConnected;

import org.omg.CosEventChannelAdmin.TypeError;

import org.omg.CosNotifyChannelAdmin.AdminLimitExceeded;

import org.omg.CosNotifyChannelAdmin.AdminNotFound;

import org.omg.CosNotifyChannelAdmin.ClientType;

import org.omg.CosNotifyChannelAdmin.ConsumerAdmin;

import org.omg.CosNotifyChannelAdmin.EventChannel;

import org.omg.CosNotifyChannelAdmin.EventChannelHolder;

import org.omg.CosNotifyChannelAdmin.ProxySupplier;

import org.omg.CosNotifyChannelAdmin.StructuredProxyPushSupplier;

import org.omg.CosNotifyChannelAdmin.StructuredProxyPushSupplierHelper;

import org.omg.CosNotifyComm.StructuredPushConsumer;

import org.omg.CosNotifyComm.StructuredPushConsumerPOATie;

// Import POA packages

import org.omg.PortableServer.POA;

import org.omg.PortableServer.POAHelper;

import org.omg.PortableServer.POAPackage.ServantAlreadyActive;

import org.omg.PortableServer.POAPackage.WrongPolicy;

// Import TMF packages

import org.tmforum.mtnm.emsSession.EmsSession_I;

import org.tmforum.mtnm.emsSession.EmsSession_IHolder;

import org.tmforum.mtnm.emsSession.EmsSession_IPackage.managerNames_THolder;

import org.tmforum.mtnm.emsSessionFactory.EmsSessionFactory_I;

import org.tmforum.mtnm.emsSessionFactory.EmsSessionFactory_IHelper;

import org.tmforum.mtnm.nmsSession.NmsSession_I;

import org.tmforum.mtnm.nmsSession.NmsSession_IPOATie;

public static void main(String[] args)

{

try {

// Optional: set up ORB properties: you can set them here or in the launch file for the client

// Properties sys_properties = System.getProperties();

// For JacORB

// sys_properties.put("org.omg.CORBA.ORBClass",

"org.jacorb.orb.ORB"

// sys_properties.put("org.omg.CORBA.ORBSingletonClass",

"org.jacorb.orb.ORBSingleton"

// For Orbix

// sys_properties.put("org.omg.CORBA.ORBClass",

"com.iona.corba.art.artimpl.ORBImpl");

// sys_properties.put("org.omg.CORBA.ORBSingletonClass",

"com.iona.corba.art.artimpl.ORBSingleton");

// For Visibroker

// sys_properties.put("org.omg.CORBA.ORBClass",

"com.inprise.vbroker.orb.ORB"

// sys_properties.put("org.omg.CORBA.ORBSingletonClass",

"com.inprise.vbroker.orb.ORBSingleton"

// For other ORBs check the related ORB programming guide

// Step 1: Initialize the ORB and obtain ROOT POA reference

// Note: ORB_init will process any -ORB arguments

// be called before any other argument processing.

global_orb = ORB.init(args, null);

org.omg.CORBA.Object root_poa = global_orb.resolve_initial_references("RootPOA");

POA rpoa = POAHelper.narrow(root_poa);

POA poa = rpoa.create_POA("myPolicy",null, new Policy[0]);

poa.the_POAManager().activate();

}

catch (SystemException ex) {

// Exception handling

}

C.2.2.2 Get Reference to the Naming Service

// Get Nameservice reference

NamingContext nsRootContext = null;

try {

// Step 2: Get reference to the name service

// Option 1: Resolve initial reference (RIR)

// org.omg.CORBA.Object obj = global_orb.resolve_initial_references("NameService");

// or

// Option 2: corbaloc URL

String objRef = "corbaloc:iiop:gatewayserver.cisco.com:14005/NameServiceGWC";

org.omg.CORBA.Object obj = global_orb.string_to_object(objRef);

/* NOTE: Please replace "gatewayserver.cisco.com" with the name of the server on which CORBA Naming service is running. */

// Narrow to root naming context

NamingContextExt root_context = NamingContextExtHelper.narrow(obj);

}

catch (org.omg.CORBA.ORBPackage.InvalidName inEx) {

// Exception handling

}

C.2.2.3 Get Reference to EMSSessionFactory

Follow the example in Get Reference to the Naming Service to obtain a reference to the naming service.

NameComponent name = new NameComponent[6];

name[0] = new NameComponent("TMF_MTNM", "Class");

name[1] = new NameComponent("Cisco Systems", "Vendor");

name[2] = new NameComponent("Cisco Prime Optical", "EMSInstance");

name[3] = new NameComponent(version, "Version"); //where version = "9_3" for Prime Optical 9.3

name[4] = new NameComponent(ctm_sys_id, "EMS"); // ctm_sys_id = "PrimeOptical"

name[5] = new NameComponent("SessionFactory", "EmsSessionFactory");

try {

org.omg.CORBA.Object emsSessionI = root_context.resolve(name);

}

catch (InvalidName inEx) {

// Exception handling

}

catch (NotFound nfEx) {

// Exception handling

}

C.2.2.4 Implement NmsSession_IOperations

import org.tmforum.mtnm.session.*;

import org.tmforum.mtnm.nmsSession.*;

public class SessionImpl implements NmsSession_IOperations {

Session_I myAssociatedSession = null;

public SessionImpl() {

super();

// TODO Auto-generated constructor stub

}

public void setAssociatedSession(Session_I emsSession) {

myAssociatedSession = emsSession;

}

public Session_I getAssoicatedSession (){ return myAssociatedSession;}

public void eventLossOccurred(String startTime, String notificationId) {