Руководство Разработчика для Cisco Cisco Prime Optical 10.6

Cisco Prime Optical 10.6 GateWay/CORBA Programmer Reference Guide 

 

 

23

 

website. The information model allows the EMS to provide an abstraction layer between the EMS and the 
NMS. This standard is generic and is, therefore, applicable to many different EMS and NE 
implementations. Customers implementing a TMF-compliant CORBA interface between a specific NMS 
and Prime Optical must use the GateWay/CORBA product, and will require specific information on what 
API features are implemented and how those features should be used. 

The following table lists the IDL-related changes that occurred between two given releases. 

Cisco Prime Optical 9.3.1 to Cisco 
Prime Optical 9.5 
  

New enumerated PGT_Y_CABLE added to protection.idl 
enum ProtectionGroupType_T 
   { 
    PGT_MSP_1_PLUS_1, 
    PGT_MSP_1_FOR_1, 
    PGT_MSP_1_FOR_N, 
    PGT_2_FIBER_BLSR, 
    PGT_4_FIBER_BLSR, 
    PGT_SPLITTER, 
    PGT_L2_1_PLUS_1, 
    PGT_Y_CABLE 
   }; 

Cisco Prime Optical 9.3 to Cisco 
Prime Optical 9.3.1 

No change 

From R9.2 to Cisco Prime Optical 9.3 
  
  
  
  
  
  
  
  
  
  
  
  

globaldefs.idl (added definition): 
typedef sequence<NamingAttributesList_T> 
NamingAttributesMultipleList_T; 
multiLayerSubnetwork.idl (added API): 
void getRouteAndTopologicalLinks( 
in globaldefs::NamingAttributes_T sncName, 
out subnetworkConnection::Route_T route, 
out topologicalLink::TopologicalLinkList_T topologicalLinkList) 
raises(globaldefs::ProcessingFailureException); 
The following new standard IDLs have been added: 
flowDomain.idl 
flowDomainFragment.idl 
trafficConditioningProfile.idl 
trailNtwProtection.idl 

From R9.1 to R9.2 

No change