Cisco Cisco Prime Optical 10.6 Developer's Guide

Cisco Prime Optical 10.6 GateWay/CORBA Programmer Reference Guide 

 

 

281

 

Prime Optical support for DriNode_T structure is as follows: 

•  type 

–  This field defines integer values that categorize the BLSR-DRI as traditional or nontraditional 

BLSR-DRI. In Prime Optical type = 0 means it is a dummy node, 1 = traditional. and 2 = 
nontraditional. 

•  isSecPCA 

–  This field indicates whether or not the RIP option is supported. 

•  DriNodePair_T 

–  This structure holds the primary and secondary nodes. The sDriNodePair structure is as 

follows: 

  globaldefs::NamingAttributes_T PrimaryME—Defines the primary DRI node. 
  globaldefs::NamingAttributes_T SecondaryME —Defines the secondary DRI node. 
  globaldefs::NamingAttributesList requiredRings—Holds the ring information. The first 

name value tuple represents EMS instance and the second one holds the BLSR ring ID. 

Compliance 
Prime Optical-defined. 

Synopsis 

Description 
This interface allows the NMS to add a new managed element to the specified subnetwork. 
If the operation fails, an exception is returned, and the managed element is not added to the subnetwork. 
If the operation succeeds, a managed element is added to the specified subnetwork. The EMS populates 
the ME communication state, its supported layer rates, and emsInSyncState when connectivity to the ME 
is established. 
Prime Optical generates an NT_OBJECT_CREATION event upon successful addition of a managed 
element. 
Parameters 
Name 

meData  MEAdditionData_T  In 

Input data required for the addition of the NE. 

The structure of MEAdditionalData_T is as follows: