IP Library Granted Patent US 10,116,577
Granted Patent B2
US 10,116,577 · App. 14/561,038 · Granted Oct 30, 2018

Detecting path MTU mismatch at first-hop router

Inventors: Purushothaman Ramalingam (Chennai, IN); Premnath Sundarababu (Chennai, IN); Mahesh Manivasagam (Chennai, IN)
Assignee: DELL PRODUCTS LP
H04L47/365H04L45/125H04L47/26
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 10,116,577
App. No.
14/561,038
Filed
Dec 4, 2014
Granted
Oct 30, 2018
Kind
B2
Art Unit
2415
USPC
370/235
Abstract

Embodiments of the present invention include systems and methods for detecting and correcting mismatches between a flow's size and the path maximum transmission unit (PMTU) size. In embodiments, a controller is notified of a new flow's size and compares that to the route path's MTU size. If the controller recognizes a mismatch, it informs an information handling device, such as the first-hop router, to notify the sender of the correct path MTU size—thereby effectively and efficiency notifying the sender to correct the MTU size for that flow.

Claims (40)

1. A method for correcting path maximum transmission unit (PMTU) size mismatch comprising:

receiving, at a routing system of a network, a packet for a new flow from a source host system to a destination host system, the packet comprising an initial packet transmission unit size, a source host system routing identifier, and a destination host system routing identifier;

responsive to the routing system not having a forwarding routing match for the new flow in its routing table, forwarding at least some of the routing information of the packet including the initial packet transmission unit size to a central controller system of the network, the central controller system knowing the network's topology formed by network nodes in the network and maximum transmission unit size information of routing interfaces of the network nodes in the network;

receiving a notification from the central controller system of the network that the initial packet transmission unit size for the new flow is a mismatch with a path maximum transmission unit size of a route in the network, the route determined by the central controller system of the network from among a plurality of potential routes in the network using the information representing the network's topology and the route comprising a plurality of network nodes in the network but does not include the central controller and wherein the path maximum transmission unit size of the route in the network is determined by the central controller of the network using maximum transmission unit size information of routing interfaces of network nodes that form the route in the network; and

notifying the source host system of the mismatch between the initial packet transmission unit size and the path maximum transmission unit of the route in the network determined by the central controller system.

2. The method of claim 1 wherein the mismatch represents the initial packet transmission unit size being larger than the path maximum transmission unit size of the route in the network determined by the central controller system and the host system is notified to reduce its packet transmission unit size to match the path maximum transmission unit size.

3. The method of claim 1 wherein the mismatch represents the initial packet transmission unit size being smaller than the path maximum transmission unit size of the route in the network determined by the central controller system and the host system is notified to increase its packet transmission unit size to match the path maximum transmission unit size.

4. The method of claim 1 wherein the method is performed at a first-hop router.

5. The method of claim 4 wherein the notification to the host system is an Internet Control Message Protocol (ICMP) packet that informs the host system of the PMTU size.

6. The method of claim 5 wherein the ICMP packet notifies the host system that the initial packet transmission unit size is too large.

7. The method of claim 5 wherein the ICMP packet notifies the host system that the initial packet transmission unit size is too small.

8. A method for correcting a path maximum transmission unit size mismatch, the method comprising:

receiving, at a central controller system of a network, packet information for a new flow from a source system to a destination system, the packet information comprising a source identifier of the source system for the new flow, a destination identifier of the destination system, and an initial packet transmission unit size;

using the source identifier, the destination identifier, and information representing the network's topology, which is known to the central controller system, to determine a route path in the network from among a plurality of potential routes in the network, the route path comprising a plurality of network nodes in the network but does not include the central controller system;

given the route path, determining a path maximum transmission unit (PMTU) size based upon maximum transmission unit size information of interfaces of the plurality of network nodes along the route path in the network, wherein the maximum transmission unit size information of interfaces is known to the central controller system before a packet for the new flow has traversed the route path;

comparing the initial packet transmission unit size with the path maximum transmission unit (PMTU) size determined by the central controller system; and

responsive to determining a mismatch between the initial packet transmission unit size and the path maximum transmission unit (PMTU) size, providing a notification of the PMTU size.

9. The method of claim 8 further comprising the step of:

installing the route path information in a set of one or more information handling devices along the route path.

10. The method of claim 8 wherein the packet information is received via a first-hop router.

11. The method of claim 10 wherein the notification of the PMTU size is provided to the first-hop router that, in turn, notifies the source system.

12. The method of claim 11 wherein the first-hop router notifies the source system by an Internet Control Message Protocol (ICMP) packet that informs the source system of the PMTU size.

13. The method of claim 12 wherein the ICMP packet notifies the source system that the initial packet transmission unit size is too big or too small according to the mismatch.

14. The method of claim 11 wherein the mismatch represents the initial packet transmission unit size being bigger than the PMTU size of the route path and the source system is notified to reduce its packet transmission unit size to match the PMTU size.

15. The method of claim 11 wherein the mismatch represents the initial packet transmission unit size being smaller than the PMTU size of the route path and the source system is notified to increase its packet transmission unit size to match the PMTU size.

16. The method of claim 8 wherein the step of using the source identifier and the destination identifier to determine a route path comprises:

using a load balancer to determine the route path in the network.

17. A central controller system of a network for correcting a path maximum transmission unit size mismatch for a flow of data through the network comprising a plurality of information handling systems, the controller system comprising:

a plurality of ports for facilitating communications with one or more of the plurality of information handling systems communicatively coupled to the controller;

one or more processors that are communicatively coupled to the plurality of ports; and

a non-transitory memory comprising one or more sequences of instructions which, when executed by the one or more processors, causes steps to be performed comprising:

receiving, at the central controller system of the network, packet information for a new flow from a source system to a destination system, the packet information comprising a source identifier of the source system for the new flow, a destination identifier of the destination system, and an initial packet transmission unit size;

using the source identifier, the destination identifier, and information representing the network's topology, which is known to the central controller system, to determine a route path in the network from among a plurality of potential routes in the network, the route path comprising a plurality of network nodes in the network but does not include the central controller system;

given the route path in the network, determining a path maximum transmission unit (PMTU) size based upon maximum transmission unit size information of interfaces of the plurality of network nodes along the route path in the network, wherein the maximum transmission unit size information of interfaces is known to the central controller system before a packet for the new flow has traversed the route path;

comparing the initial packet transmission unit size with the path maximum transmission unit (PMTU) size determined by the central controller system; and

responsive to determining a mismatch between the initial packet transmission unit size and the path maximum transmission unit (PMTU) size, providing a notification of the PMTU size.

18. The controller of claim 17 wherein the non-transitory memory further comprises one or more sequences of instructions which, when executed by the one or more processors, causes steps to be performed comprising:

installing the route path information in a set of one or more information handling devices along the route path.

19. The method of claim 17 wherein the packet information is received via a first-hop router and the notification of the PMTU size is provided to the first-hop router that, in turn, notifies the source system.

20. The method of claim 19 wherein the source system is notified that the initial packet transmission unit size is too big or too small according to the mismatch.

Assignments (16)
RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (053546/0001) Recorded Jun 23, 2022
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
To: DELL MARKETING L.P. (ON BEHALF OF ITSELF AND AS SUCCESSOR-IN-INTEREST TO CREDANT TECHNOLOGIES, INC.); DELL INTERNATIONAL L.L.C.; DELL PRODUCTS L.P.; DELL USA L.P.; EMC CORPORATION; DELL MARKETING CORPORATION (SUCCESSOR-IN-INTEREST TO FORCE10 NETWORKS, INC. AND WYSE TECHNOLOGY L.L.C.); EMC IP HOLDING COMPANY LLC
Reel/Frame 071642/0001 →
RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (045455/0001) Recorded May 20, 2022
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
To: DELL MARKETING CORPORATION (SUCCESSOR-IN-INTEREST TO ASAP SOFTWARE EXPRESS, INC.); DELL MARKETING L.P. (ON BEHALF OF ITSELF AND AS SUCCESSOR-IN-INTEREST TO CREDANT TECHNOLOGIES, INC.); DELL USA L.P.; DELL INTERNATIONAL L.L.C.; DELL PRODUCTS L.P.; DELL MARKETING CORPORATION (SUCCESSOR-IN-INTEREST TO FORCE10 NETWORKS, INC. AND WYSE TECHNOLOGY L.L.C.); EMC CORPORATION (ON BEHALF OF ITSELF AND AS SUCCESSOR-IN-INTEREST TO MAGINATICS LLC); EMC IP HOLDING COMPANY LLC (ON BEHALF OF ITSELF AND AS SUCCESSOR-IN-INTEREST TO MOZY, INC.); SCALEIO LLC
Reel/Frame 061753/0001 →
RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (040136/0001) Recorded Apr 26, 2022
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
To: DELL MARKETING CORPORATION (SUCCESSOR-IN-INTEREST TO ASAP SOFTWARE EXPRESS, INC.); DELL MARKETING L.P. (ON BEHALF OF ITSELF AND AS SUCCESSOR-IN-INTEREST TO CREDANT TECHNOLOGIES, INC.); DELL USA L.P.; DELL INTERNATIONAL L.L.C.; DELL PRODUCTS L.P.; DELL MARKETING CORPORATION (SUCCESSOR-IN-INTEREST TO FORCE10 NETWORKS, INC. AND WYSE TECHNOLOGY L.L.C.); EMC CORPORATION (ON BEHALF OF ITSELF AND AS SUCCESSOR-IN-INTEREST TO MAGINATICS LLC); EMC IP HOLDING COMPANY LLC (ON BEHALF OF ITSELF AND AS SUCCESSOR-IN-INTEREST TO MOZY, INC.); SCALEIO LLC
Reel/Frame 061324/0001 →
RELEASE OF SECURITY INTEREST Recorded Nov 3, 2021
From: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH
To: ASAP SOFTWARE EXPRESS, INC.; AVENTAIL LLC; CREDANT TECHNOLOGIES, INC.; DELL USA L.P.; DELL INTERNATIONAL, L.L.C.; DELL MARKETING L.P.; DELL PRODUCTS L.P.; DELL SOFTWARE INC.; DELL SYSTEMS CORPORATION; EMC CORPORATION; EMC IP HOLDING COMPANY LLC; FORCE10 NETWORKS, INC.; MAGINATICS LLC; MOZY, INC.; SCALEIO LLC; WYSE TECHNOLOGY L.L.C.
Reel/Frame 058216/0001 →
SECURITY AGREEMENT Recorded Apr 22, 2020
From: CREDANT TECHNOLOGIES INC.; DELL INTERNATIONAL L.L.C.; DELL MARKETING L.P.; DELL PRODUCTS L.P.; DELL USA L.P.; EMC CORPORATION; FORCE10 NETWORKS, INC.; WYSE TECHNOLOGY L.L.C.; EMC IP HOLDING COMPANY LLC
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A.
Reel/Frame 053546/0001 →
SECURITY AGREEMENT Recorded Mar 21, 2019
From: CREDANT TECHNOLOGIES, INC.; DELL INTERNATIONAL L.L.C.; DELL MARKETING L.P.; DELL PRODUCTS L.P.; DELL USA L.P.; EMC CORPORATION; FORCE10 NETWORKS, INC.; WYSE TECHNOLOGY L.L.C.; EMC IP HOLDING COMPANY LLC
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A.
Reel/Frame 049452/0223 →
SECURITY AGREEMENT Recorded Sep 21, 2016
From: ASAP SOFTWARE EXPRESS, INC.; AVENTAIL LLC; CREDANT TECHNOLOGIES, INC.; DELL USA L.P.; DELL INTERNATIONAL L.L.C.; DELL MARKETING L.P.; DELL PRODUCTS L.P.; DELL SOFTWARE INC.; DELL SYSTEMS CORPORATION; EMC CORPORATION; EMC IP HOLDING COMPANY LLC; FORCE10 NETWORKS, INC.; MAGINATICS LLC; MOZY, INC.; SCALEIO LLC; SPANNING CLOUD APPS LLC; WYSE TECHNOLOGY L.L.C.
To: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS COLLATERAL AGENT
Reel/Frame 040134/0001 →
SECURITY AGREEMENT Recorded Sep 21, 2016
From: ASAP SOFTWARE EXPRESS, INC.; AVENTAIL LLC; CREDANT TECHNOLOGIES, INC.; DELL USA L.P.; DELL INTERNATIONAL L.L.C.; DELL MARKETING L.P.; DELL PRODUCTS L.P.; DELL SOFTWARE INC.; DELL SYSTEMS CORPORATION; EMC CORPORATION; EMC IP HOLDING COMPANY LLC; FORCE10 NETWORKS, INC.; MAGINATICS LLC; MOZY, INC.; SCALEIO LLC; SPANNING CLOUD APPS LLC; WYSE TECHNOLOGY L.L.C.
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
Reel/Frame 040136/0001 →
RELEASE OF REEL 035104 FRAME 0043 (NOTE) Recorded Sep 14, 2016
From: BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS COLLATERAL AGENT
To: DELL SOFTWARE INC.; DELL PRODUCTS L.P.; COMPELLENT TECHNOLOGIES, INC.
Reel/Frame 040027/0123 →
RELEASE OF REEL 035103 FRAME 0809 (TL) Recorded Sep 14, 2016
From: BANK OF AMERICA, N.A., AS COLLATERAL AGENT
To: DELL SOFTWARE INC.; DELL PRODUCTS L.P.; COMPELLENT TECHNOLOGIES, INC.
Reel/Frame 040027/0934 →
RELEASE OF REEL 035103 FRAME 0536 (ABL) Recorded Sep 13, 2016
From: BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT
To: DELL SOFTWARE INC.; DELL PRODUCTS L.P.; COMPELLENT TECHNOLOGIES, INC.
Reel/Frame 040016/0864 →
SUPPLEMENT TO PATENT SECURITY AGREEMENT (NOTES) Recorded Feb 26, 2015
From: DELL PRODUCTS L.P.; DELL SOFTWARE INC.; COMPELLENT TECHNOLOGIES, INC.
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
Reel/Frame 035104/0043 →
SUPPLEMENT TO PATENT SECURITY AGREEMENT (TERM LOAN) Recorded Feb 26, 2015
From: DELL PRODUCTS L.P.; DELL SOFTWARE INC.; COMPELLENT TECHNOLOGIES, INC.
To: BANK OF AMERICA, N.A., AS COLLATERAL AGENT
Reel/Frame 035103/0809 →
SUPPLEMENT TO PATENT SECURITY AGREEMENT (ABL) Recorded Feb 26, 2015
From: DELL PRODUCTS L.P.; DELL SOFTWARE INC.; COMPELLENT TECHNOLOGIES, INC.
To: BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT
Reel/Frame 035103/0536 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 4, 2014
From: RAMALINGAM, PURUSHOTHAMAN; SUNDARABABU, PREMNATH
To: DELL PRODUCTS L.P.
Reel/Frame 034381/0109 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 4, 2014
From: RAMALINGAM, PURUSHOTHAMAN; SUNDARABABU, PREMNATH; MANIVASAGAM, MAHESH
To: DELL PRODUCTS L.P.
Reel/Frame 034381/0165 →
Continuity (1)
Related Publication 20160164794A1 · Jun 9, 2016