Originated multi-protocol label switching packet maximum length determining method and node

Abstract

The invention discloses a method for determining maximum length of an originally transmitted multi protocol label switching (MPLS) message, a label switched path (LSP) header node, and a LSP middle node. The method comprises transmitting a MPLS echo request message from a LSP header node, and determining the maximum length of originally transmitted MPLS message when receiving a MPLS echo responsemessage indicating that the maximum transmission unit (MTU) of an interface is not enough and returned from a LSP middle node, according to the label stack depth and the interface MTU of the LSP middle node in the response message. By the invention, when the network allocation is changed, the LSP header node can timely regulate the maximum length of originally transmitted MPLS message, so as to prevent retransmission failure of the MPLS message.

Description

Method and node for determining the maximum length of an originating multi-protocol label switching packet technical field The present invention relates to the technical field of MultiProtocol Label Switching (MPLS, MultiProtocolLabelSwitching), in particular to a method for determining the maximum length of an initial MPLS message, a head node of a Label Switched Path (LSP, LabelSwitchedPath), and an LSP intermediate node. Background technique The MPLS system mainly includes two parts: the signaling control plane and the data forwarding plane. Among them, the signaling control plane is responsible for the establishment of the MPLS forwarding path: LSP, but it cannot detect the error of LSP transmission data failure. The data forwarding plane is based on isolated nodes, and cannot know the situation of the upstream and downstream and the entire LSP. Therefore, the MPLS system specially provides an MPLSPing / TraceRoute mechanism to detect the validity and reachability of th...

AI Technical Summary

Problems solved by technology

However, with the upgrade and improvement of network applications, network deployment will change. For example, the number of tunnels in the MPLS network will increase, resulting in changes in the labeling of MPLS packets during network transmission.

Since MPLS network devices may belong to different manufacturers, the manufacturer to which the head node of the LSP belongs may not be able to know the changes in the deployment of the entire network in time, and thus cannot adjust the maximum length of the original MPLS packet in time, resulting in the failure of MPLS packet forwarding.

Images