To establish an end-to-end connection between two 7750 SR or 7950 XRS nodes through a GMPLS network, a path is required, which is configured via the config>router>gmpls>path path-name context.
The path context consists of a set of numbered entries, each entry representing a resource that the gLSP must follow. The te-link ID is the ID allocated at the node referred to in the hop.
When interoperating with the Nokia 1830 PSS, at least the first and penultimate hops of the gLSP should be included.
The following CLI tree is used to configure a gLSP path:
config>router>gmpls
path path-name
no path path-name
hop hop-index node-id node-id [te-link te-link-id]
[strict | loose]
no hop hop-index
no shutdown
shutdown
where:
node-id: IPv4 address a.b.c.d | 1830-data-plane-node-id 32-bit unsigned integer
In general, the 7750 SR or 7950 XRS node is able to populate the ERO with every hop along the gLSP path from ingress UNI-N to egress UNI-C. However, normally only a loose path across the optical network (from ingress UNI-N to egress UNI-N) is required because the optical network is responsible for path selection between ingress and egress UNI-N. Therefore the user normally just configures hop 1 and hop 4 in the above example. For interoperability with the 1830 PSS, the user must configure a TE Link ID to use on the final hop in the ERO toward the destination UNI-C.
The following example shows how the Path should be configured for interoperability with the 1830 PSS.
Consider the following topology:
A B C D E F
[unic1]------[unin1]-----------[unin2]------[unic2]
where A-F are the TE Link IDs assigned at each end of a link.
Path configuration on unic1:
Hop 1 unic1 A strict
Hop 2 unin2 E loose