Cisco Cisco Prime Optical 10.3 Developer's Guide
Cisco Prime Optical 10.3 GateWay/CORBA Programmer Reference Guide
558
4.10.3.6 getTopLevelTopologicalLink
Synopsis
4.10.4 MPLS-TP LSP Route Inventory Interfaces
The Route object represents the route of an SNC. An SNC route is represented as a partially
ordered series of cross-connections through which the SNC travels. Only SNC layer rate cross-
connections are part of the route. The cross-connections that are part of the route are listed from
the NE on which the SNC starts to the NE on which it ends. LSP aEnd and zEnd are not
available in cross-connections.
This section describes the following interfaces:
•
ordered series of cross-connections through which the SNC travels. Only SNC layer rate cross-
connections are part of the route. The cross-connections that are part of the route are listed from
the NE on which the SNC starts to the NE on which it ends. LSP aEnd and zEnd are not
available in cross-connections.
This section describes the following interfaces:
•
4.10.4.1 getRoute
•
4.10.4.2 getRouteAndTopologicalLinks
•
4.10.4.3 getAllCrossConnections
4.10.4.1 getRoute
Synopsis
Description
The NML-EML interface allows the NMS to retrieve the attributes of a route using the NMS-
specified SNC name. The route information, in the form of ordered cross-connections, must
identify the resources allocated to the SNC at the time of the request and the way in which these
resources are used.
The NMS specifies if it will retrieve resources in the SNC layer only. Because TP tunnel names
are not guaranteed to be unique in the network, you must provide the LSP name in the following
format:
<Native TP-Tunnel name>:TKEY=<TP-Tunnel key>:LSP=<LSP number>
For example, tunnel192_193:TKEY=3.3.3.0:55:5.5.5.0:66:LSP=0.
Parameters
• NamingAttributes sncName—SNC name.
• boolean includeHigherOrderCCs—Specifies whether the higher order cross-connections of
The NML-EML interface allows the NMS to retrieve the attributes of a route using the NMS-
specified SNC name. The route information, in the form of ordered cross-connections, must
identify the resources allocated to the SNC at the time of the request and the way in which these
resources are used.
The NMS specifies if it will retrieve resources in the SNC layer only. Because TP tunnel names
are not guaranteed to be unique in the network, you must provide the LSP name in the following
format:
<Native TP-Tunnel name>:TKEY=<TP-Tunnel key>:LSP=<LSP number>
For example, tunnel192_193:TKEY=3.3.3.0:55:5.5.5.0:66:LSP=0.
Parameters
• NamingAttributes sncName—SNC name.
• boolean includeHigherOrderCCs—Specifies whether the higher order cross-connections of
other SNCs used to carry the queried SNC must be included in addition to the cross-
connections of the queried SNC.
connections of the queried SNC.
• Route_T route—The route of the SNC.