User guide

3-202
Cisco Transport Manager Release 9.2 GateWay/CORBA User Guide and Programmer Manual
OL-20937-01
Chapter 3 Using CTM GateWay/CORBA Interfaces
3.10.16 createL2Topology
Supported. You can choose to specify bandwidth parameters. By default, bandwidth parameters have
a zero value. If you choose to enter a specific bandwidth value, you must also specify its
corresponding CoS value. The default value for all CoS values is N/A. The sum of all the bandwidth
parameters must be from 1 to 99. The CoS commit value must be from 0 to 7. The following are the
supported bandwidth parameters (Group1Bandwidth and Group2Bandwidth are multicast
bandwidth parameters, and their corresponding CoS values are Group1CoS and Group2CoS):
– Group1Bandwidth
– Group2Bandwidth
– SpMgmtBandwidth
– CommittedBandwidth
– BestEffortBandwidth
– AvvidControlBandwidth
– ClassSpMgmt
– ClassCommitted
– ClassBestEffort
– ClassAvvidControl
– ClassAvvidVoiceVideo
– ClassAReservedBandwidth
– ClassA1Bandwidth
– ClassBCommittedBandwidth
– SpMgmtCoS
– CommittedCoS
– AvvidVoiceVideoCoS
– AvvidControlCoS
– CosCommit
– Group1CoS
– Group2CoS
Caution Group2Bandwidth parameters must be entered along with Group1Bandwidth parameters.
Entering Group2Bandwidth alone creates inconsistency in the L2 topology table.
If the topology is DOT17_RPR, multicast bandwidth parameters are not supported; Group1Bandwidth
and Group2Bandwidth values are not needed. Group1CoS and Group2CoS do not apply to DOT17_RPR.
For DOT17_RPR topologies, you can specify the absolute bandwidth values for the three possible
classes of traffic (A Reserved, A1, and B Committed). For the remaining bandwidth parameters, you
specify to which class of traffic (Class A, B, or C) the parameter belongs. For example, ClassSpMgmt
belongs to Class C-type traffic.
Throws
globaldefs::ProcessingFailureException
EXCPT_INTERNAL_ERROR - Raised in case of nonspecific EMS internal failure.