IP Library Granted Patent US 9,088,506
Granted Patent B2
US 9,088,506 · App. 13/610,321 · Granted Jul 21, 2015

System and method for data stream mirroring

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 9,088,506
App. No.
13/610,321
Granted
Jul 21, 2015
Kind
B2
Abstract

A mirroring configuration employs an alternate usage of an existing messaging protocol and mechanism for propagating mirroring control for remote mirroring of data streams. A source routing entity, i.e. a router or switch through which the mirrored stream passes, identifies the stream as available for monitoring. The enabled stream propagates from a source network device, typically from a router port, to a mirroring destination in addition to the addressed destination. A stream identifier emulates an identifier from an alternate usage, such as a multicast group identifier for a multicast protocol, and activates mirroring by inserting the stream identifier in publish and join messages of the multicast protocol.

Claims (45)

1. A method of mirroring message traffic comprising:

assigning an identifier to a traffic stream enabled for remote mirroring, the traffic stream corresponding to a port;

mapping the assigned identifier to the port for designating the identifier for remote mirroring, the mapping superceding a multicast group identifier;

receiving a mirroring message containing mirroring information for commencing mirroring, the mirroring message indicative of the assigned identifier and a destination to which a mirrored stream is to be sent;

wherein said mirroring information propagates via a multicast routing protocol and allows remote mirroring to be enabled from a remote capture device by capitalizing on the mirroring information emulating multicast information;

publishing the assigned identifier for receipt by the mirroring destination, the publishing emulating multicast routing and indicative of the remote mirroring, the assigned identifier for including in the mirroring message sent by the mirroring destination; and

transmitting the mirrored stream to the mirroring destination, the mirroring destination defined by a mirroring requester sending the mirroring message.

2. The method of claim 1 further comprising distinguishing, based on the mapping, the mirroring message from the multicast routing; and

invoking remote mirroring for the traffic stream indicated by the assigned identifier rather than invoking the multicast routing.

3. The method of claim 2 wherein the mirroring message is a request to join a group defined by the assigned identifier, the group based on the multicast routing.

4. The method of claim 3 wherein the multicast routing is a group messaging protocol defined by IGMP.

5. The method of claim 1 wherein publishing further comprises route propagation for multicast routing in an IP network.

6. The method of claim 1 further comprising:

identifying, at the mirroring requestor, the traffic stream; and

specifying the traffic stream in the mirrored message for commencing mirroring.

7. The method of claim 6 wherein identifying further comprises publishing each of the designated streams enabled for monitoring, the mirroring requestor responsive to the published streams for generating the mirrored message for commencing mirroring.

8. The method of claim 1 wherein receiving the mirroring message further includes receiving a message indicative of the traffic stream; and designating the enabled stream for mirroring.

9. The method of claim 1 wherein receiving the mirroring message further includes:

receiving a mirroring message differentiating the assigned identifier from the multicast routing;

comparing the mirroring message to a list of enabled streams of traffic; and

concluding, based on a match in the list, that the received mirroring message is for commencing mirroring rather than for the multicast routing.

10. The method of claim 1 wherein said receiving a message for commencing mirroring further comprises activating mirroring by inserting the multicast identifier in publish and join messages of a multicast protocol.

11. A network switching device with mirroring capability comprising:

mirroring logic for generating an identifier to a traffic stream enabled for remote mirroring, the traffic stream corresponding to a port;

a mapping table configured to mapping an association of an assigned identifier to the port for designating the identifier for remote mirroring, the mapping superceding a multicast group identifier;

a network interface responsive to a mirroring requestor for a mirroring message containing mirroring information for commencing mirroring, the mirrored message indicative of the assigned identifier and a destination to which a mirrored stream is to be sent;

wherein said mirroring information propagates via a multicast routing protocol and allows remote mirroring to be enabled from a remote capture device by capitalizing on the mirroring information emulating multicast information;

the network interface configured to transmit the mirrored stream to the mirroring destination, the mirroring destination defined by the mirroring requester sending the mirroring message; and

wherein the mirroring logic is configured to:

distinguish, based on the mapping, the mirroring message from multicast routing; and

invoke remote mirroring for the traffic stream indicated by the assigned identifier rather than invoking the multicast routing.

12. The network switching device of claim 11 wherein the mirroring message is a request to join a group defined by the assigned identifier, the group based on the multicast routing, the multicast routing being is a group messaging protocol defined by IGMP.

13. The network switching device of claim 11 further comprising a comparator for performing a lookup of the mirroring message in a table for determining multicast routing, and

concluding, based on the lookup, that the mirroring message is a request to commence mirroring.

14. The network switching device of claim 13 wherein the multicast routing is a protocol operable to publish the assigned identifier for receipt by the mirroring destination, the publishing emulating the multicast routing and indicative of the remote mirroring, the assigned identifier for including in the mirroring message sent by the mirroring destination.

15. The network switching device of claim 11 wherein the mirroring logic is further configured to:

identify, at the mirroring requestor, the traffic stream; and

specify the traffic stream in the mirroring message for commencing mirroring, wherein identifying further comprises publishing each of the designated streams enabled for monitoring, the mirroring requestor responsive to the published streams for generating the message for commencing mirroring.

16. The network switching device of claim 11 wherein the network switching device invokes the interface for receiving a mirroring message differentiating the assigned identifier from the multicast routing, and invokes the comparator for:

comparing the mirroring message to a list of enabled streams of traffic; and

concluding, based on a match in the list, that the received mirroring message is for commencing mirroring rather than for the multicast routing.

17. The network switching device of claim 11 wherein the assigned identifier includes an IP source address and IP multicast destination address, the assigned identifier responsive to a request to join a multicast group.

18. The network switching device of claim 11 further comprising designating a subset range of multicast addresses for the assigned identifier, the subset range distinct from multicast addresses employed for multicast usage.

19. The network switching device of claim 17 wherein the assigned identifier employing an upper 12 bits for storing a node identifier and a lower 12 bits as a source of the mirrored stream.

20. The network switching device of claim 11 wherein said received message for commencing mirroring further comprises activating mirroring by inserting the multicast identifier in publish and join messages of a multicast protocol.

Assignments (13)
AMENDED SECURITY AGREEMENT Recorded Aug 18, 2023
From: EXTREME NETWORKS, INC.; AEROHIVE NETWORKS, INC.
To: BANK OF MONTREAL
Reel/Frame 064782/0971 →
SECURITY INTEREST Recorded May 1, 2018
From: EXTREME NETWORKS, INC.
To: BANK OF MONTREAL
Reel/Frame 046050/0546 →
RELEASE OF SECURITY INTEREST Recorded May 1, 2018
From: SILICON VALLEY BANK
To: EXTREME NETWORKS, INC.
Reel/Frame 046051/0775 →
BANKRUPTCY COURT ORDER RELEASING ALL LIENS INCLUDING THE SECURITY INTEREST RECORDED AT REEL/FRAME 030083/0639 Recorded Dec 15, 2017
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A.
To: AVAYA INC.
Reel/Frame 045012/0666 →
BANKRUPTCY COURT ORDER RELEASING ALL LIENS INCLUDING THE SECURITY INTEREST RECORDED AT REEL/FRAME 029608/0256 Recorded Dec 15, 2017
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A.
To: AVAYA INC.
Reel/Frame 044891/0801 →
BANKRUPTCY COURT ORDER RELEASING ALL LIENS INCLUDING THE SECURITY INTEREST RECORDED AT REEL/FRAME 041576/0001 Recorded Dec 15, 2017
From: CITIBANK, N.A.
To: AVAYA INC.; AVAYA INTEGRATED CABINET SOLUTIONS INC.; OCTEL COMMUNICATIONS LLC (FORMERLY KNOWN AS OCTEL COMMUNICATIONS CORPORATION); VPNET TECHNOLOGIES, INC.
Reel/Frame 044893/0531 →
THIRD AMENDED AND RESTATED PATENT AND TRADEMARK SECURITY AGREEMENT Recorded Oct 31, 2017
From: EXTREME NETWORKS, INC.
To: SILICON VALLEY BANK
Reel/Frame 044639/0300 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 15, 2017
From: AVAYA INC.; AVAYA COMMUNICATION ISRAEL LTD; AVAYA HOLDINGS LIMITED
To: EXTREME NETWORKS, INC.
Reel/Frame 043569/0047 →
SECOND AMENDED AND RESTATED PATENT AND TRADEMARK SECURITY AGREEMENT Recorded Jul 14, 2017
From: EXTREME NETWORKS, INC.
To: SILICON VALLEY BANK
Reel/Frame 043200/0614 →
SECURITY INTEREST Recorded Jan 27, 2017
From: AVAYA INC.; AVAYA INTEGRATED CABINET SOLUTIONS INC.; OCTEL COMMUNICATIONS CORPORATION; VPNET TECHNOLOGIES, INC.
To: CITIBANK, N.A., AS ADMINISTRATIVE AGENT
Reel/Frame 041576/0001 →
SECURITY AGREEMENT Recorded Mar 13, 2013
From: AVAYA, INC.
To: BANK OF NEW YORK MELLON TRUST COMPANY, N.A., THE
Reel/Frame 030083/0639 →
SECURITY AGREEMENT Recorded Jan 10, 2013
From: AVAYA, INC.
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A.
Reel/Frame 029608/0256 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 11, 2012
From: KEESARA, SRIKANTH; STRONG, RICHARD THOMAS; BULL, BRIAN THOMAS
To: AVAYA INC.
Reel/Frame 028937/0266 →