Back to results
US 11,106,656 B2Granted
Method and apparatus for a software-seamed and augmented view of an asynchronous network fabric
AssigneeCisco Technology, Inc.
InventorsPraveen Parthasarathy Iyengar, Shrawan Chittoor Surender, Narayanaswami Ganapathy, Srinivas Pitta
Life of this patent
Estimating the term…
Abstract
Methods and systems for tracking transactions in a network fabric, include: receiving a message generated by a node in the network fabric; assigning a uniform fabric identifier (“UFID”) to the node; assigning a uniform transaction identifier (“UTID”) to the message”; appending the UFID and the UTID to the message; and storing the message in a database.
Claims20
A method of tracking transactions in a network fabric, comprising:
- assigning a first uniform fabric identifier (“UFID”) to a first node of a network fabric;
- assigning a first uniform transaction identifier (“UTID”) to a first message associated with a first transaction at the first node;
- appending both of the first UFID and the first UTID to the first message, wherein appending both of the first UFID and the first UTID to the message comprises appending both of the first UFID and the first UTID to a header of the first message;
- storing the first message in a database;
- receiving a second message at the first node;
- determining that a second UFID associated with the second message is not associated with the first node;
- determining, in response to determining that the second UFID associated with the second message is not associated with the first node, a control message associated with the second UFID based on the second UFID and a timestamp associated with the second message;
- determining a second UTID from the control message, the second UTID being associated with a second transaction;
- and
- determining a root cause based on the second transaction.
7 more elements
A system of nodes arranged in a fabric, comprising:
- a first node associated with a first unique fabric identifier (“UFID”) and a counter providing a first unique transaction identifier (“UTID”), the first node operable to generate a first message with a header including the first UFID and the first UTID;
- a second node associated with a second unique fabric identifier (“UFID”) and a counter providing a second unique transaction identifier (“UTID”), the second node operable to generate a second message with a header including the second UFID and the second UTID;
- and
- a data aggregator in communication with the first node and the second node and operable to receive and store the first message and the second message, wherein the first node is operative to:
- receive the second message;
- determine that the second UFID associated with the second message is not associated with the first node;
- determine, in response to determining that the second UFID associated with the second message is not associated with the first node, a control message associated with the second UFID ID based on the second UFID and a timestamp associated with the second message;
- determine the second UTID from the control message, the second UTID being associated with a second transaction at the second node;
- and
- determine a root cause based on the second transaction.
7 more elements
A system, comprising:
- a memory;
- and
- a processor in communications with the memory, wherein the processor is operative to:
- assign a first uniform fabric identifier (“UFID”) to a first node of a network fabric;
- assign a first uniform transaction identifier (“UTID”) to a first message associated with a first transaction at the first node;
- append both of the first UFID and the first UTID to the first message, the processor being operative to append both of the first UFID and the first UTID to the first message comprises the processor being operative to append both of the first UFID and the first UTID to a header of the first message;
- store the first message in the database;
- receive a second message at the first node;
- determine that a second UFID associated with the second message is not associated with the first node;
- determine, in response to determining that the second UFID associated with the second message is not associated with the first node, a control message associated with the second UFID ID based on the second UFID and a timestamp associated with the second message;
- determine a second UTID from the control message, the second UTID being associated with a second transaction;
- and
- determine a root cause based on the second transaction.
10 more elements
Dependencies are inferred from the claim text.