Cisco Cisco Prime Optical 10.3 Developer's Guide
Cisco Prime Optical 10.3 GateWay/CORBA Programmer Reference Guide
508
Object modify notifications are not generated.
4.6.2 MPLS-TP LSP Provisioning Interfaces
This section describes the following interfaces:
•
•
•
•
4.6.2.1 createAndActivateSNC
Synopsis
Description
This interface allows you to create and activate a subnetwork connection (an LSP) in a single
command. As per TMF standards, an SNC name is assigned by the EMS when it creates an SNC.
However, if the NMS must control the SNC name, you can use the additionalInfo parameter
sncName.
The LSP name must match the TP tunnel circuit name. As TP tunnel names are not guaranteed to
be unique in the network, you must provide the TP tunnel name in the following format:
<Native TP-Tunnel name>:TKEY=<TP-Tunnel key>
For example, tunnel192_193:TKEY=3.3.3.0:55:5.5.5.0:66.
The TKEY represents the TP tunnel key and is returned as an additional parameter whenever
retrieving the corresponding SNC. The layer rate that applies to the LSP circuits is
LR_MPLS_PATH (166), which provides MPLS path layering to the TP tunnel entity.
This interface allows you to create and activate a subnetwork connection (an LSP) in a single
command. As per TMF standards, an SNC name is assigned by the EMS when it creates an SNC.
However, if the NMS must control the SNC name, you can use the additionalInfo parameter
sncName.
The LSP name must match the TP tunnel circuit name. As TP tunnel names are not guaranteed to
be unique in the network, you must provide the TP tunnel name in the following format:
<Native TP-Tunnel name>:TKEY=<TP-Tunnel key>
For example, tunnel192_193:TKEY=3.3.3.0:55:5.5.5.0:66.
The TKEY represents the TP tunnel key and is returned as an additional parameter whenever
retrieving the corresponding SNC. The layer rate that applies to the LSP circuits is
LR_MPLS_PATH (166), which provides MPLS path layering to the TP tunnel entity.
Local and out labels in the endpoints and midpoints are automatically assigned by the network. To
modify them, use the modifySNC API.
The EMS must guarantee that the same SID is shared among all the MEs traversed by all TP
tunnel LSPs. If the route proposed by the EMS for the new LSP crosses MEs that are different
from the ones currently belonging to the TP tunnel, the EMS must verify if the same SID is also
available on the new MEs. If the same SID is not available, the EMS must pick up a new SID
and reassign to the same MEs.
Relevant Data Structures
tunnel LSPs. If the route proposed by the EMS for the new LSP crosses MEs that are different
from the ones currently belonging to the TP tunnel, the EMS must verify if the same SID is also
available on the new MEs. If the same SID is not available, the EMS must pick up a new SID
and reassign to the same MEs.
Relevant Data Structures