Cisco Cisco Prime Optical 10.3 Developer's Guide

Cisco Prime Optical 10.3 GateWay/CORBA Programmer Reference Guide 

 

 

529

 

When you create a pseudowire, specify the QoS policies to be associated to the pseudowire 
drops. If you specify policy maps, they must be available in the given ME the Ethernet drop 
belongs to. 
Use Case Description 
•  Create the TC profiles for policy maps, class maps, actions, and table maps using the 

createTCProfile interface. The new policies are stored in the EMS database, not in the ME. 

•  Modify and delete QoS policies through the modifyTCProfile and deleteTCProfile interfaces. 
•  Associate the given policies that are already present in the EMS database to an ME using the 

setAdditionalInfo interface, which downloads the given policies to the NE.  

•  Use the getManagedElement interface to get the QoS policies present in an ME. The QoS 

policy names are returned with the additional parameters. 

•  When you create a pseudowire, specify the desired QoS policy map names (at ingress and 

egress) as additional parameters at pseudowire endpoints within the createAndActivateFDFr 
interface. 

This section describes the following interface: 
• 

Synopsis 

Description 
This interface allows you to associate a list of QoS policies to an ME. The NMS provides the 
ME name in the objectName parameter and the list of QoS policies in the additionalInfo 
parameter. The EMS returns the list of policies whose provisioning has succeeded on the given 
ME in the additionalInfo parameter. If provisioning failed for all the given QoS policies, the 
additionalInfo output contains an empty array. 
The following table describes the parameters for additionalInfo in 
TCProfileMgr::setAdditionalInfo. 

class-map

 

String

 

Optional. The user label of the 
class map. The maximum length 
is 39 characters.

 

policy-map

 

String

 

Optional. The user label of the 
policy map. The maximum 
length is 39 characters.

 

table-map

 

String

 

Optional. The user label of the 
table map. The maximum length 
is 39 characters.

 

Each tuple is optional, but can be repeated as many times as needed to direct the EMS to 
provision multiple class maps, policy maps, and table maps on an ME. The order is irrelevant. 

  You cannot modify or delete TC profiles that are provisioned on the node with the current API 

implementation.