Cisco Cisco Prime Optical 10.6 Developer's Guide
Cisco Prime Optical 10.6 GateWay/CORBA Programmer Reference Guide
427
• Mixed configuration
Each pseudowire can carry only one EVC service and is represented and exported directly by one FDFr.
From the Network Circuit Provisioning (NCP) level, the pseudowire is represented by only one service.
For descriptions of pseudowire provisioning and inventory interfaces, see the following sections:
From the Network Circuit Provisioning (NCP) level, the pseudowire is represented by only one service.
For descriptions of pseudowire provisioning and inventory interfaces, see the following sections:
•
•
4.1.11 Pseudowire Flow Domain Fragment
An EVC-based pseudowire with an attachment circuit (AC) type of VLAN-based or port-based is
modeled as an FDFr. In this model, an EVC containing the pseudowire and an FDFr on top the EVC
containing the EVC do not exist; only an FDFr exists.
Ethernet FPs are represented by CTPs and the naming rule depends on the properties of the MFD that
connects it.
The following table lists the MFD types and the corresponding value.
MFD Type
modeled as an FDFr. In this model, an EVC containing the pseudowire and an FDFr on top the EVC
containing the EVC do not exist; only an FDFr exists.
Ethernet FPs are represented by CTPs and the naming rule depends on the properties of the MFD that
connects it.
The following table lists the MFD types and the corresponding value.
MFD Type
Value
Comments
VLAN unaware
/eth=1
Only one FP is present.
VLAN aware with single VLAN
tag
tag
/ethvid=n
Can be used either for Customer
VLAN ID (C-VID) or Service
VLAN ID (S-VID) in MFDs that
only process a single VLAN tag.
VLAN ID (C-VID) or Service
VLAN ID (S-VID) in MFDs that
only process a single VLAN tag.
VLAN aware with one or two
VLAN tags
VLAN tags
[/ethsvid=n][/ethcvid=m]
Either S-VID or C-VID or both
maybe present. The square
brackets (“[ ]”) indicate options.
maybe present. The square
brackets (“[ ]”) indicate options.
Proprietary
/eth=P<string>
—
For descriptions of PW FDFr provisioning and inventory interfaces, see the following sections:
•
•
4.2 Interface Managers
The following interface managers support APIs:
• FlowDomain
• TrafficConditioningProfile
• TrafficConditioningProfile
The following table lists the supported APIs and the corresponding interface manager.
Table 4-1: Interface Managers and APIs
Interface Manager
API
New API
TMF Extension
TrafficConditioningProfile createTCProfile
Yes
No
deleteTCProfile
Yes
No
modifyTCProfile
Yes
No
getAllTCProfiles
Yes
No
getTCProfile
Yes
No
FlowDomain
createMFD
Yes
No
assignCPTPsToMFD
Yes
No
unassignCPTPsFromMFD
Yes
No
deleteMFD
Yes
No
modifyMFD
Yes
No
createFlowDomain
Yes
No
deleteFlowDomain
Yes
No