Enabling scalable virtual machine tracking in a data center fabric
A method is provided in one example embodiment and includes receiving at a first network element a packet from a second network element; processing the packet at the first network element to obtain information regarding an identity of a virtual machine (“VM”) hosted by the second network element contained within the packet; and storing at the first network element the identifying information. The identifying information stored at the first network element is accessible by at least one third network element. In some embodiments, the first network element comprises a physical switch and the second network element comprises a virtual switch.
1. A method, comprising:
receiving at a first network element a packet from a second network element;
processing the packet at the first network element to obtain information regarding an identity of a virtual network interface card (“vNIC”) hosted by the second network element contained within the packet; and
storing at the first network element the identifying information, wherein the identifying information stored at the first network element is accessible by at least one third network element for use by the at least one third network element in troubleshooting and debugging a network;
wherein the identifying information includes an identity of a virtual machine (“VM”) connected to the second network element via the vNIC.
2. The method of claim 1 , wherein the first network element comprises a physical switch.
3. The method of claim 1 , wherein the second network element comprises a virtual switch.
4. The method of claim 1 , wherein the packet is created by the second network element in response to a Virtual Station Interface Discovery and Configuration Protocol (“VDP”) event.
5. The method of claim 1 , wherein the at least one third network element comprises a physical switch.
6. The method of claim 1 , wherein the first network element comprises a leaf switch and the at least one third network element comprises a spine switch connected to the leaf switch.
7. The method of claim 1 , wherein the packet includes a Type-Length-Value (“TLV”) element comprising the identifying information.
8. One or more non-transitory tangible media that includes code for execution and when executed by a processor is operable to perform operations comprising:
receiving at a first network element a packet from a second network element;
processing the packet at the first network element to obtain information regarding an identity of a virtual network interface card (“vNIC”) hosted by the second network element contained within the packet; and
storing at the first network element the identifying information, wherein the identifying information stored at the first network element is accessible by at least one third network element for use by the at least one third network element in troubleshooting and debugging a network;
wherein the identifying information includes an identity of a virtual machine (“VM”) connected to the second network element via the vNIC.
9. The media of claim 8 , wherein the first network element comprises a physical switch.
10. The media of claim 8 , wherein the second network element comprises a virtual switch.
11. The media of claim 8 , wherein the packet is created by the second network element in response to a Virtual Station Interface Discovery and Configuration Protocol (“VDP”) event.
12. The media of claim 8 , wherein the first network element comprises a leaf switch and the at least one third network element comprises a spine switch connected to the leaf switch.
13. The media of claim 8 , wherein the packet includes a Type-Length-Value (“TLV”) element comprising the identifying information.
14. An apparatus comprising:
memory element configured to store data;
a processor operable to execute instructions associated with the data; and
a Virtual Station Interface Discovery and Configuration Protocol (“VDP”) module configured to:
receive a packet from a second network element;
process the packet at the first network element to obtain information regarding an identity of a virtual network interface card (“vNIC”) hosted by the second network element contained within the packet; and
store the identifying information, wherein the stored identifying information is accessible by at least one third network element for use by the at least one third network element in troubleshooting and debugging a network;
wherein the identifying information includes an identity of a a virtual machine (“VM”) connected to the second network element via the vNIC.
15. The apparatus of claim 14 , wherein the first network element comprises a physical switch and the second network element comprises a virtual switch.
16. The apparatus of claim 14 , wherein the first network element comprises a leaf switch and the at least one third network element comprises a spine switch connected to the leaf switch.
17. The apparatus of claim 14 , wherein the packet includes a Type-Length-Value (“TLV”) element comprising the identifying information.