Cisco Cisco Prime Optical 10.6 Developer's Guide
Cisco Prime Optical 10.6 GateWay/CORBA Programmer Reference Guide
423
• FDFr state—Indicates one of the following values:
– Active—All MFDFrs and all edge FPs and internal FPs for the FDFr are active in the
network.
– Partial—All parts (MFDFrs or FPs) of the FDFr either were not created during the creation
operation or were not deleted during the deletion operation.
• FDFr type—Represents the type of the FDFr:
– Point-to-point
– Point-to-multipoint (E-Tree)
– Multipoint
– Point-to-multipoint (E-Tree)
– Multipoint
An FP is a point in a connectionless layer, which represents an association between a CPTP and an FDFr.
An FP is modeled as a connection termination point (CTP) and it is either an FDFr endpoint where traffic
enters or exits an FDFr or an FDFr internal point used to define the route of an FDFr.
FPs are created as CTP objects when the associated FDFr is created and are deleted when the associated
FDFr is deleted. FPs do not exist without an associated FDFr. As a result, only in-use FPs are represented
as CTP objects at the interface, and therefore only in-use FPs can be inventoried.
For Ethernet, FPs are always bidirectional. Operations on frames, which either enter or exit an FDFr are
defined on the CTP object. The connectionless layered parameters are specified in the layered
transmission parameters attribute inherited from the TP object. This attribute represents the technology-
specific parameters associated with the different connectionless layers that are supported by the FP. If the
NMS does not provide a name for the FP, the Element Management System (EMS) uses the FDFr VLAN
ID.
For descriptions of EVC FDFr provisioning and inventory interfaces, see the following sections:
An FP is modeled as a connection termination point (CTP) and it is either an FDFr endpoint where traffic
enters or exits an FDFr or an FDFr internal point used to define the route of an FDFr.
FPs are created as CTP objects when the associated FDFr is created and are deleted when the associated
FDFr is deleted. FPs do not exist without an associated FDFr. As a result, only in-use FPs are represented
as CTP objects at the interface, and therefore only in-use FPs can be inventoried.
For Ethernet, FPs are always bidirectional. Operations on frames, which either enter or exit an FDFr are
defined on the CTP object. The connectionless layered parameters are specified in the layered
transmission parameters attribute inherited from the TP object. This attribute represents the technology-
specific parameters associated with the different connectionless layers that are supported by the FP. If the
NMS does not provide a name for the FP, the Element Management System (EMS) uses the FDFr VLAN
ID.
For descriptions of EVC FDFr provisioning and inventory interfaces, see the following sections:
•
•
4.1.6 Link Aggregation
Link Aggregation (LAG) is supported using the Link Aggregation Control Protocol (LACP). LACP
guarantees the compatibility of both sides of the aggregated link. LACP, which is specified in IEEE
802.3ad, has many attributes and configuration parameters that are handled at the EMS level. LAG
support in Multi-Technology Network Management (MTNM) version 3.5 does not deal with these
attributes and configuration parameters at the NMS level.
A LAG is represented by an FTP, and the new layer rate defined for it is LR_LAG_Fragment(305). The
LAG FTP is the Edge CPTP. A LAG FTP may either be created by the EMS and discovered by the NMS
or it can be created by the NMS using the createFTP() operation.
A LAN port, which usually can be an edge CPTP, cannot be an edge CPTP if it is a member of a LAG.
Whether created by an EMS or NMS, LAG FTPs act like other fragment TPs. You can configure the
maximum number of allowed members using the AllocationMaximum attribute. You can configure a
specific number of members using the AllocatedNumber attribute.
If LAGs are created by the EMS, the EMS creates all the potential LAG FTPs that it can handle, each
with FragmentServerLayer set to a layer rate at which LAG can be supported and with
AllocationMaximum set to the maximum number of members that can be supported for that layer rate.
As with Cisco equipment, an Ethernet LAG port can aggregate client Ethernet ports of different ME cards
(for example, PTSA_GE). The corresponding FTP is logically positioned on the unique shelf of the ME
itself. As a result, the FTP name does not contain any reference to slots:
guarantees the compatibility of both sides of the aggregated link. LACP, which is specified in IEEE
802.3ad, has many attributes and configuration parameters that are handled at the EMS level. LAG
support in Multi-Technology Network Management (MTNM) version 3.5 does not deal with these
attributes and configuration parameters at the NMS level.
A LAG is represented by an FTP, and the new layer rate defined for it is LR_LAG_Fragment(305). The
LAG FTP is the Edge CPTP. A LAG FTP may either be created by the EMS and discovered by the NMS
or it can be created by the NMS using the createFTP() operation.
A LAN port, which usually can be an edge CPTP, cannot be an edge CPTP if it is a member of a LAG.
Whether created by an EMS or NMS, LAG FTPs act like other fragment TPs. You can configure the
maximum number of allowed members using the AllocationMaximum attribute. You can configure a
specific number of members using the AllocatedNumber attribute.
If LAGs are created by the EMS, the EMS creates all the potential LAG FTPs that it can handle, each
with FragmentServerLayer set to a layer rate at which LAG can be supported and with
AllocationMaximum set to the maximum number of members that can be supported for that layer rate.
As with Cisco equipment, an Ethernet LAG port can aggregate client Ethernet ports of different ME cards
(for example, PTSA_GE). The corresponding FTP is logically positioned on the unique shelf of the ME
itself. As a result, the FTP name does not contain any reference to slots:
For descriptions of LAG provisioning and inventory interfaces, see the following sections:
•