Cisco Cisco Prime Optical 9.8 Developer's Guide
Cisco Prime Optical 9.8 GateWay/CORBA Programmer Reference Guide
OL-29218-01
476
and the other TP in zEnd. For a multipoint FDFr or a PPP FDFr that may be expanded to
multipoint, it is recommended that you specify all the TPs in aEnd.
multipoint, it is recommended that you specify all the TPs in aEnd.
• zEnd TPs—Represents a list of FPs that delimit the FDFr and characterize the edges (entry or
exit points). zEnd TPs are clients of the fdEdge CPTPs. For a bidirectional FDFr, this attribute
may be combined with aEnd TPs to obtain all the FPs that are associated to the FDFr.
may be combined with aEnd TPs to obtain all the FPs that are associated to the FDFr.
• Flexible—Indicates whether the FDFr is fixed or flexible. If the FDFr is fixed, the NMS cannot
modify or delete it and you cannot add or remove FPs.
• Administrative State—Indicates whether the FDFr is locked or unlocked. If the FDFr is
locked, traffic units cannot flow through the FDFr. If the FDFr is unlocked, traffic units are
allowed to flow through the FDFr.
allowed to flow through the FDFr.
• 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
– 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.
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.
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.
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
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