Cisco Cisco Prime Optical 10.3 Developer's Guide
Cisco Prime Optical 10.3 GateWay/CORBA Programmer Reference Guide
551
•
•
•
4.10.1 MPLS-TP Tunnel Inventory Interfaces
This section describes the following interfaces:
•
•
•
•
•
•
•
4.10.1.1 getSNC
Synopsis
Description
This interface returns the SubnetworkConnection structure for the TP tunnel SNC identified by
the sncName. Because 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 BFD template order follows the order of the aEnd and zEnd endpoints of the TP tunnel.
Because the order is not stored in the ME, it depends on the order of discovery. The TKEY is
composed as follows:
<source Node ID>:<source Tunnel ID>:<dest Node ID>:<dest Tunnel ID>
The TKEY remains invariant with the order of discovery.
Relevant Data Structures
This interface returns the SubnetworkConnection structure for the TP tunnel SNC identified by
the sncName. Because 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 BFD template order follows the order of the aEnd and zEnd endpoints of the TP tunnel.
Because the order is not stored in the ME, it depends on the order of discovery. The TKEY is
composed as follows:
<source Node ID>:<source Tunnel ID>:<dest Node ID>:<dest Tunnel ID>
The TKEY remains invariant with the order of discovery.
Relevant Data Structures