IP Library › Granted Patent US 12,438,810
Granted Patent B2
US 12,438,810 · App. 17/946,532 · Granted Oct 7, 2025

Systems and methods for route mismatch identification

Inventors: Edgar Jesus Dorantes Loarca (Olympia, WA); Danyang He (Seattle, WA); Xiangkun Dai (Lynnwood, WA); Oleksandr (Alex) Kadushko (Knoxville, TN); Andi Mullaraj (San Jose, CA); Sharath Vaddempudi (Issaquah, WA)
Assignee: Oracle International Corporation
H04L45/745H04L45/742
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 12,438,810
App. No.
17/946,532
Granted
Oct 7, 2025
Kind
B2
Abstract

Systems and methods for route mismatch identification are disclosed herein. A method of route mismatch identification can create in cache an expected routing table based on expected routing information received by a routing agent of a host from a database accessible by each of the plurality of hosts. The method can include creating in cache an actual routing table based on actual routing information received by the routing agent of the host from an advertising agent of the host, comparing the actual routing table and the expected routing table, and taking an action based on the comparison of the actual routing table and the expected routing table.

Claims (40)

1. A method of identifying a mismatch between a desired route and an actual route, the method comprising:

creating in cache an expected routing table based on expected routing information received by a routing agent of a host from a database accessible by each of a plurality of hosts;

creating in cache an actual routing table based on actual routing information received by the routing agent of the host from an advertising agent of the host;

comparing the actual routing table and the expected routing table; and

taking an action based on the comparison of the actual routing table and the expected routing table.

2. The method of claim 1 , wherein the expected routing table is created by the routing agent.

3. The method of claim 1 , wherein the actual routing table is created by the routing agent.

4. The method of claim 1 , further comprising: receiving updated expected routing information with the routing agent of the host from the database accessible by each of the plurality of hosts; and updating the expected routing table with the updated expected routing information.

5. The method of claim 4 , further comprising comparing the updated expected routing information to the expected routing table; and determining no difference between the updated expected routing information and the expected routing table.

6. The method of claim 4 , further comprising comparing the updated expected routing information to the expected routing table; and determining a difference between the updated expected routing information and the expected routing table.

7. The method of claim 6 , wherein the expected routing table is updated with the updated expected routing table when the difference is determined between the updated expected routing information and the expected routing table.

8. The method of claim 7 , wherein comparing the actual routing table and the expected routing table comprises comparing the updated actual routing table and the updated expected routing table.

9. The method of claim 8 , wherein comparing the actual routing table and the expected routing table comprises determining that the actual routing table matches the expected routing table.

10. The method of claim 8 , wherein comparing the actual routing table and the expected routing table comprises determining a difference between the actual routing table and the expected routing table.

11. The method of claim 10 , further comprising determining a time since initiation of a route change.

12. The method of claim 11 , further comprising comparing the time since initiation of the route change to a threshold value.

13. The method of claim 12 , further comprising triggering an alarm when the time since initiation of the route change is greater than the threshold value.

14. The method of claim 12 , further comprising, when the time since initiation of the route change is less than the threshold value: waiting for an amount of time; and subsequently polling the advertising agent for updated actual routing information.

15. The method of claim 14 , further comprising: updating the actual routing table with the updated actual routing information; comparing the updated expected routing table to the updated actual routing table; and triggering an alarm when the updated actual routing table does not match the expected routing table.

16. A system comprising:

memory comprising a database of expected routing information; and

a plurality of hosts, wherein the database is accessible by each of the plurality of hosts, wherein at least one of the hosts is configured to:

create in cache an expected routing table based on expected routing information received by a routing agent of the host from the database;

create in cache an actual routing table based on actual routing information received by the routing agent from an advertising agent of the host;

compare the actual routing table and the expected routing table; and

take an action based on the comparison of the actual routing table and the expected routing table.

17. The system of claim 16 , wherein the host is further configured to:

receive updated expected routing information with the routing agent of the host from the database accessible by each of the plurality of hosts; and

update the expected routing table with the updated expected routing information.

18. The system of claim 17 , wherein the host is further configured to:

compare the updated expected routing information to the expected routing table; and

determine a difference between the updated expected routing information and the expected routing table, wherein the expected routing table is updated with the updated expected routing table when the difference is determined between the updated expected routing information and the expected routing table.

19. A non-transitory computer-readable storage medium storing a plurality of instructions executable by one or more processors, the plurality of instructions when executed by the one or more processors cause the one or more processors to:

create in cache an expected routing table based on expected routing information received by a routing agent of a host from a database accessible by each of a plurality of hosts;

create in cache an actual routing table based on actual routing information received by the routing agent of the host from an advertising agent of the host;

compare the actual routing table and the expected routing table; and

take an action based on the comparison of the actual routing table and the expected routing table.

20. The non-transitory computer-readable storage medium of claim 19 , wherein the plurality of instructions when executed by the one or more processors cause the one or more processors to:

receive updated expected routing information with the routing agent of the host from the database accessible by each of the plurality of hosts; and

update the expected routing table with the updated expected routing information.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 23, 2022
From: DORANTES LOARCA, EDGAR JESUS; HE, DANYANG; DAI, XIANGKUN; KADUSHKO, OLEKSANDR; MULLARAJ, ANDI; VADDEMPUDI, SHARATH
To: ORACLE INTERNATIONAL CORPORATION
Reel/Frame 061193/0806 →
Continuity (1)
Related Publication 20240098021A1 · Mar 21, 2024
References Cited (20)
US 9246804B1 · Muir et al. · 2016 [cited by applicant]
US 11115309B1 · Scholl · 2021 [cited by applicant]
US 11212216B2 · Beck · 2021 [cited by applicant]
US 12301477B2 · Dorantes Loarca et al. · 2025 [cited by applicant]
US 20060233155A1 · Srivastava · 2006 [cited by applicant]
US 20070189284A1 · Kecskemeti · 2007 [cited by examiner]
US 20070294399A1 · Grossner et al. · 2007 [cited by applicant]
US 20080304497A1 · Viswanath et al. · 2008 [cited by applicant]
US 20120201145A1 · Ree · 2012 [cited by examiner]
US 20190166036A1 · Tappin et al. · 2019 [cited by applicant]
US 20210297339A1 · Yu et al. · 2021 [cited by applicant]
US 20220038309A1 · Boutros et al. · 2022 [cited by applicant]
U.S. Appl. No. 17/946,526 , “Corrected Notice of Allowability”, Apr. 11, 2025, 2 pages. [cited by applicant]
U.S. Appl. No. 17/946,526 , “Non-Final Office Action” dated Jul. 19, 2023, , 22 pages. [cited by applicant]
Zhang , “Top of Rack VS End of Row: Which to Choose for Data Center Network” , Medium , Sep. 12, 2018 , pp. 1-12. [cited by applicant]
U.S. Appl. No. 17/946,526 , “Final Office Action”, Feb. 22, 2024, 21 pages. [cited by applicant]
U.S. Appl. No. 17/946,526 , Non-Final Office Action, Mailed on Sep. 4, 2024, 23 pages. [cited by applicant]
U.S. Appl. No. 17/946,526 , Notice of Allowance, Mailed on Jan. 15, 2025, 8 pages. [cited by applicant]
U.S. Appl. No. 17/946,534 , Non-Final Office Action, Mailed on Jan. 6, 2025, 14 pages. [cited by applicant]
U.S. Appl. No. 17/946,534, Final Office Action, Mailed On Jul. 2, 2025, 14 pages. [cited by applicant]