User guide

3-174
Cisco Transport Manager Release 9.2 GateWay/CORBA User Guide and Programmer Manual
OL-20937-01
Chapter 3 Using CTM GateWay/CORBA Interfaces
3.9.44 addManagedElement
3.9.44 addManagedElement
Synopsis
void addManagedElement(in MEAdditionData_T meData)
raises(globaldefs::ProcessingFailureException);
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.
CTM generates an NT_OBJECT_CREATION event upon successful addition of a managed element.
Parameters
The structure of MEAdditionalData_T is as follows:
struct MEAdditionData_T
{
globaldefs::NamingAttributes_T managedElementName;
globaldefs::NamingAttributes_T containingSubnetworkName;
in string userLabel;
in string nativeEMSName;
in string owner;
in string location;
in string version;
in string productName;
globaldefs::NVSList_T additionalInfo;
};
The description of each field is as follows:
• globaldefs::NamingAttributes_T managedElementName—Name of the managed element to add.
– name="ManagedElement"
– value=Managed Element
• containingSubnetworkName—Name of the subnetwork that contains the managed element.
– name="subnetworkName"
– value=subnetwork name
• string userLabel—User-specified label of the managed element.
• string nativeEMSName—nativeEMSName of the managed element to add.
• string owner—Owner of the managed element.
• string location—Location of the managed element.
• string version—The NMS can specify the ME version; however, this value is overwritten when the
ME is put in service and the EMS retrieves the actual version information.
Name Type Input/Output Description
meData MEAdditionData_T In Input data required for the addition of the NE.