Network interface device management using management transport channel
View Patent ↗A master network interface device (M-NID) receives, from a network management system (NMS) via a first peer-to-peer (P2P) transport channel, first data destined for a first client network interface device (C-NID), where the first data is associated with network management functions. The M-NID further receives, from the NMS via the first P2P transport channel, second data destined for a second C-NID, where the second data is associated with network management functions. The M-NID forwards the first data from the M-NID to the destination first C-NID via a second P2P transport channel that is different than the first P2P transport channel. The M-NID also forwards the second data from the M-NID to the destination second C-NID via a third P2P transport channel that is different than the first P2P transport channel.
1. A method, comprising:
receiving, at a master network interface device (M-NID) and from at least one of a first client network interface device (C-NID) or a second C-NID, first data;
forwarding, by the M-NID, the first data to one or more destinations;
receiving, at the M-NID and from at least one of the first C-NID or the second C-NID, second data;
forwarding, by the M-NID, the second data to a network management system (NMS), where the NMS is different than the one or more destinations;
receiving, at the M-NID and from the NMS, via a first peer-to-peer (P2P) transport channel, third data destined for the first C-NID, where the third data is associated with network management functions and is received in response to the forwarded second data;
receiving, at the M-NID and from the NMS, via the first P2P transport channel, fourth data destined for the second C-NID, where the fourth data is associated with network management functions and is received in response to the forwarded second data;
forwarding the third data from the M-NID to the first C-NID via a second P2P transport channel that is different than the first P2P transport channel; and
forwarding the fourth data from the M-NID to the second C-NID via a third P2P transport channel that is different than the first P2P transport channel.
2. The method of claim 1 , where forwarding the third data further comprises:
determining a network address associated with the first C-NID; and
determining the second P2P transport channel based on the determined network address associated with the first C-NID.
3. The method of claim 1 , where forwarding the fourth data further comprises:
determining a network address associated with the second C-NID; and
determining the third P2P transport channel based on the determined network address associated with the second C-NID.
4. The method of claim 1 , where the first P2P transport channel comprises an emulated pseudowire.
5. The method of claim 1 , where the second P2P transport channel is a virtual local area network (VLAN).
6. The method of claim 1 , where the first P2P transport channel is a first virtual local area network (VLAN), where the second P2P transport channel is a second VLAN, and where the third P2P transport channel is a third VLAN that is different than the first and second VLANs.
7. The method of claim 1 , where the second data is received from the first C-NID and is associated with network management functions, the method further comprising:
forwarding the second data from the M-NID to the NMS via the first P2P transport channel.
8. The method of claim 7 , further comprising:
receiving, at the M-NID and from the second C-NID, other data destined for the NMS, where the other data is associated with network management functions; and
forwarding the other data from the M-NID to the NMS via the first P2P transport channel.
9. The method of claim 1 , further comprising:
receiving, at the M-NID and from a third C-NID, fifth data;
forwarding, by the M-NID, the fifth data to the NMS;
receiving, at the M-NID and from the NMS via the first P2P transport channel, sixth data destined for the third C-NID; and
forwarding the sixth data from the M-NID to the third C-NID via a fourth P2P transport channel.
10. A master network interface device (M-NID), comprising:
an interface to:
receive, from at least one of a first client network interface device (C-NID) or a second C-NID, first information;
forward the first information to one or more destinations;
receive, from at least one of the first C-NID or the second C-NID, second information;
forward the second information to a network management system (NMS), where the NMS is different than the one or more destinations;
receive, from the NMS, first data destined for the first C-NID via a first peer to peer (P2P) transport channel, where the first data is associated with network management functions and is received in response to the forwarded second information; and
receive, from the NMS, second data destined for the second C-NID via the first P2P transport channel, where the second data is associated with network management functions and is received in response to the forwarded second information; and
a data router to:
forward the first data from the M-NID to the first C-NID via a second P2P transport channel that is different than the first P2P transport channel; and
forward the second data from the M-NID to the second C-NID via a third P2P transport channel that is different than the first P2P transport channel.
11. The master network interface device of claim 10 , where the first P2P transport channel is an emulated pseudowire or a virtual local area network (VLAN).
12. The master network interface device of claim 10 , where the first P2P transport channel is a first virtual local area network (VLAN), where the second P2P transport channel is a second VLAN, and where the third P2P transport channel is a third VLAN that is different than the first and second VLANs.
13. The master network interface device of claim 10 , where the second information is received from the first C-NID and is associated with network management functions, and
where the data router is further to:
forward the second information from the M-NID to the NMS via the first P2P transport channel.
14. The master network device of claim 13 , where the interface is further to:
receive, from the second C-NID, other information destined for the NMS, where the other information is associated with network management functions, and
where the data router is further to:
forward the other information from the M-NID to the NMS via the first P2P transport channel.
15. The master network interface device of claim 10 , where:
the interface is further to:
receive, from a third C-NID, third information;
forward the third information to the NMS; and
receive, from the NMS via the first P2P transport channel, third data destined for the third C-NID; and
the data router is further to:
forward the third data from the M-NID to the third C-NID via a fourth P2P transport channel.
16. A method, comprising:
receiving, at a master network interface device (M-NID) and from at least one of a first client network interface device (C-NID) or a second C-NID, first data
forwarding, by the M-NID, the first data to one or more destinations;
receiving, at the M-NID and from the first C-NID, via a first peer-to-peer (P2P) transport channel, second data destined for a network management system (NMS), where the first data is associated with network management functions;
receiving, at the M-NID and from the second C-NID, via a second P2P transport channel, third data destined for the NMS, where the second data is associated with network management functions;
forwarding the second data from the M-NID to the NMS via a third P2P transport channel that is different than the first and second P2P transport channels, where the NMS is different than the one or more destinations;
forwarding the third data from the M-NID to the NMS via the third P2P transport channel; and
receiving, at the M-NID and from the NMS, fourth data destined for at least one of the first C-NID or the second C-NID, where the fourth data is received in response to at least one of the forwarded second data or the forwarded third data.
17. The method of claim 16 , where the first, second and third P2P transport channels are different emulated pseudowires or different virtual local area networks (VLANs).
18. The method of claim 16 , where the first P2P transport channel is a first virtual local area network (VLAN), where the second P2P transport channel is a second VLAN, and where the third P2P transport channel is a third VLAN, where the second and third VLANs are different than the first VLAN.
19. The method of claim 16 , further comprising:
forwarding the fourth data data from the M-NID to at least one of the first C-NID or the second C-NID.
20. The method of claim 16 , further comprising:
receiving, at the M-NID and from a third C-NID via a fourth P2P transport channel, fifth data;
forwarding the fifth data from the M-NID to the NMS via the third P2P transport channel;
receiving, at the M-NID and from the NMS via the third P2P transport channel, sixth data destined for the third C-NID; and
forwarding the sixth data from the M-NID to the third C-NID.