Cisco Cisco Prime Optical 9.6 Developer's Guide
Cisco Prime Optical 9.6.3 GateWay/CORBA Programmer Reference Guide
OL-28047-01
485
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).
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
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,
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
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:
name="EMS";value="CompanyName/EMSname"
name="ManagedElement";value="ManagedElementName"
name="FTP";value="/rack=1/shelf=1/port=nn"
For descriptions of LAG provisioning and inventory interfaces, see the following sections:
•
•
•
4.1.7 MPLS and MPLS-TP
Multiprotocol Label Switching (MPLS) allows the forwarding of packets based on labels. In a
normal IP network, the packets are switched based on the destination IP address. In an MPLS
network, the packets are switched based on labels.
In an MPLS network, the labels can be distributed using three different protocols:
• Label Distribution Protocol (LDP)
In an MPLS network, the labels can be distributed using three different protocols:
• Label Distribution Protocol (LDP)
• Resource Reservation Protocol-Traffic Engineering (RSVP-TE)
• Border Gateway Protocol (BGP)
BGP is a routing protocol used in big IP networks where the labeling layer is mostly used to
BGP is a routing protocol used in big IP networks where the labeling layer is mostly used to
implement Layer 3 VPNs. After the labels are distributed within a network, the packets are
labeled and forwarded based on labels. The advantages of labeled networks are:
• Protocol agnostic—Can transport any kind of protocol; for example, IP, ATM, Any Transport
• Protocol agnostic—Can transport any kind of protocol; for example, IP, ATM, Any Transport
over MPLS (AToM).
• High scalability.
• Traffic Engineering—Load balancing and automatic adaption to link changes.