Problem Establishing a GMPLS LSP

This case study describes a problem with establishing a Generalized Multiprotocol Label Switching (GMPLS) label-switched path (LSP). Specifically, the configuration of the data channel is incorrect because the configuration includes different interface types at both ends of the tunnel. The principles and solution used in this case study also apply to control channel configuration.

The chapter includes a brief summary of GRE tunnels within the context of GMPLS, an example network scenario, and commands to troubleshoot and resolve the problem. (See Table 12.)

The troubleshooting process described in this case study should not be followed rigidly; it is a basis from which you can develop your own process to suit your particular situation.

Table 12: Problem Establishing a GRE Tunnel Checklist

Troubleshooting Tasks	Command or Action
Troubleshooting GMPLS and GRE Tunnel
Symptom	show mpls lsp show rsvp session
Cause	The cause of the problem with the GMPLS LSP is the configuration of different interface types at both ends of the GMPLS data channel.
Troubleshooting Commands	show mpls lsp extensive show rsvp session detail show link-management peer show link-management te-link show configuration protocols mpls monitor start filename show log filename
Solution	Configure both ends of the data channel with the same switching type. show configuration protocols link-management show mpls lsp show link-management te-link
Conclusion	Both ends of a GMPLS data must be the same encapsulation or interface type.
Router Configurations	show configuration | no-more