Cisco Cisco Evolved Programmable Network Manager 1.2 Developer's Guide
MTOSI Interface Details
Cisco EPN Manager OSS Integration Guide for MTOSI
55
Response Parameter
Data Type
Description
zEndTpRefList
NamingAttributeListTyp
e
e
Name of Z-end TP (PTP/CTP/FTP). The termination
point name must be explicit.
point name must be explicit.
VendorExtensions
VendorExtension
ciscoTopologicalLinkExtension. Contains the following
attributes:
attributes:
name
description
directionality
layerRate
4.6.1.4.3 Exceptions
internalError: Indicates that an internal error or exception has occurred as part of this call.
invalidInput: Indicates that the input given to the operation is invalid.
invalidInput: Indicates that the input given to the operation is invalid.
4.7 FlowDomainRetrieval (Carrier Ethernet Inventory)
An EVC Flow Domain Fragment (FDFr) is a logical entity that contains a transparent end-to-end connectivity
between two or more FPs (at the same connectionless layer) within an FD. The FDFr represents a Virtual
Private Network (VPN) for a single customer in the provider network and enables the flow of traffic between
FPs.
The server-layer CPTPs of the FPs that are connected through an FDFr must be assigned to MFDs that are
associated to the FD that contains the FDFr. If traffic arrives at a point that is a member of an FDFr, it
emerges at one or more of the other edge FPs that are members of the same FDFr.
The edge FPs that act as endpoints of the FDFr can be associated with CPTPs connected to customer domains
or to other provider domains (of the same or different providers). The VLAN IDs of the FPs of the same FDFr
must be equal and in particular must be the VLAN ID of the outermost frame. An FDFr may also support
untagged frames or may be unaware of frame tags.
between two or more FPs (at the same connectionless layer) within an FD. The FDFr represents a Virtual
Private Network (VPN) for a single customer in the provider network and enables the flow of traffic between
FPs.
The server-layer CPTPs of the FPs that are connected through an FDFr must be assigned to MFDs that are
associated to the FD that contains the FDFr. If traffic arrives at a point that is a member of an FDFr, it
emerges at one or more of the other edge FPs that are members of the same FDFr.
The edge FPs that act as endpoints of the FDFr can be associated with CPTPs connected to customer domains
or to other provider domains (of the same or different providers). The VLAN IDs of the FPs of the same FDFr
must be equal and in particular must be the VLAN ID of the outermost frame. An FDFr may also support
untagged frames or may be unaware of frame tags.
4.7.1 Flow Domain Fragment Data
The following table lists the flow domain fragment data that can be retrieved by the interface.
Flow Domain Fragment
Data
Data Type
Description
fdfr
FlowDomainFragmentTyp
e
e
Holder element that contains the data for the
flow domain fragment.
flow domain fragment.
name (Object Id)
NamingAttributeType
List of RDN types representing an FDFr. Consists
of MD, FDFR.
of MD, FDFR.
direction
ConnectionDirectionType
Directionality of Ethernet Service.
Note: * always bidirectional.
Note: * always bidirectional.
isFlexible
Boolean
Flexibility of Ethernet Service (fixed or flexible). If
the FDFr is fixed, NMS cannot modify or delete it;
FPs cannot be added or removed.
the FDFr is fixed, NMS cannot modify or delete it;
FPs cannot be added or removed.
administrativeState
AdministrativeStateType
Administrative State of Flow Domain Fragment
(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.
(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.