System and method for passively monitoring customer control messages in a multicast VPN

• US 7,756,072 B1
• Filed: 12/30/2005
• Issued: 07/13/2010
• Est. Priority Date: 12/30/2005
• Status: Expired due to Fees

• Current Assignee: AT&T Intellectual Property I LP (AT&T, Inc.)
• Original Assignee: AT&T Intellectual Property I LP (AT&T, Inc.)
• Inventors: Papadopoulos, Fragkiskos, Fenner, William
• Primary Examiner(s): Trost, IV; William
• Assistant Examiner(s): MAGLO, EMMANUEL K
• Application Number:
  US11/321,464
• Time in Patent Office: 1,656 Days
• Field of Search: 370/230.1, 370/390, 370/395.24, 370/256, 370/392, 370/432, 705/2, 709/238, 709/248, 709/206, 726/15
• US Class Current: 370/326
• CPC Class Codes: H04L 12/1863 comprising mechanisms for improved reliability, e.g. status reports arrangements for detecting or preventing errors by carrying supervisory signal the return channel H04L1/16
• CPC Class Codes: H04L 12/1886 with traffic restrictions for efficiency improvement, e.g. involving subnets or subdomains
• CPC Class Codes: H04L 12/4675 Dynamic sharing of VLAN information amongst network nodes configuration of the network or of network elements H04L41/08
• CPC Class Codes: H04L 43/0817 by checking functioning

Abstract

A system and method to passively monitor multicast control traffic in the provider backbone. A monitoring station is located within the service provider network. Upon creation of an MVPN session, this monitoring station joins the default multicast distribution tree (“MDT”) in the provider backbone used to handle traffic within that MVPN session, and receives the customer'"'"'s multicast control traffic encapsulated in packets addressed to the default MDT. Using these two kinds of packets, the monitor learns the following information: the identity of the PE routers participating in the MVPN; the identity of the customer multicast groups that are carried on each provider multicast data tree (MDT); the identity of one or more PE routers participating in each customer group, and the identity of the MDT that it is carried on. This information is collected for each customer multicast group, both upstream and downstream at each PE router.

Claims

1. A method for passively monitoring a status of a multicast virtual private network (MVPN) session comprising:

connecting to a multicast data tree associated with the MVPN session;

receiving a first data packet comprising first status information regarding the MVPN session;

storing the first status information regarding the MVPN session to a first database;

receiving a second data packet comprising second status information regarding the MVPN session;

comparing the second status information to the first status information to determine whether the second status information differs from the first status information;

if the second status information differs from the first status information, then;

storing the first status information to a second database, and

storing the second status information to the first database; and

if the second status information does not differ from the first status information, then;

discarding the second data packet, and

incrementing a counter in the first database.

2. The method of claim 1, wherein the first status information comprises an actual configuration of the MVPN session during a first time interval and wherein the second status information comprises an actual configuration of the MVPN session during a second time interval.

3. The method of claim 1, further comprising:

activating a user interface; and

viewing at least one entry of at least one of the first database and the second database.

4. The method of claim 1, further comprising:

prior to comparing the first status information and the second status information, determining whether the first data packet or the second data packet contains customer data;

if the first data packet contains customer data, then discarding the first data packet; and

if the second data packet contains customer data, then discarding the second data packet.

5. The method of claim 2, further comprising:

receiving an expected configuration of the MVPN session;

if the first status information is stored to the first database, then;

comparing the actual configuration of the MVPN session during the first time interval to the expected configuration, and

if the actual configuration of the MVPN session during the first time interval does not match the expected configuration, then providing an alarm; and

if the second status information is stored in the first database, then;

comparing the actual configuration of the MVPN session during the second time interval to the expected configuration, and

if the actual configuration of the MVPN session during the second time interval does not match the expected configuration, then providing an alarm.

6. The method of claim 2, wherein the actual configuration of the MVPN session during the first time interval comprises an identity of at least one participant in the MVPN session during the first time interval and wherein the actual configuration of the MVPN session during the second time interval comprises an identity of at least one participant in the MVPN session during the second time interval.

7. A method for passively monitoring a status of a multicast virtual private network (MVPN) session comprising:

connecting to a multicast data tree associated with the MVPN session;

receiving information regarding an identity of a first participant in the MVPN session and an identity of a second participant in the MVPN session, the second participant being associated with the first participant;

receiving a first data packet comprising first status information regarding the first participant and the second participant in the MVPN session;

storing the first status information regarding to a first database;

receiving a second data packet comprising second status information regarding the first participant and the second participant in the MVPN session;

comparing the second status information to the first status information to determine whether the second status information differs from the first status information;

if the second status information differs from the first status information, then;

storing the first status information to a second database, and

storing the second status information to the first database; and

if the second status information does not differ from the first status information, then;

discarding the second data packet, and

incrementing a counter in the first database.

8. The method of claim 7, further comprising:

receiving an expected configuration of the MVPN session;

if the first status information is stored to the first database, then;

comparing the first status information to the expected configuration, and

if the first status information does not match the expected configuration, then providing an alarm; and

if the second status information is stored in the first database, then;

comparing the second status information to the expected configuration, and

if the second status information does not match the expected configuration, then providing an alarm.

9. The method of claim 7, further comprising:

activating a user interface; and

viewing at least one entry of at least one of the first database and the second database.

10. A system for passively monitoring status of a multicast virtual private network (MVPN) session comprising:

a processor connected to a multicast data tree associated with the MVPN session,

a first data packet comprising first status information regarding the MVPN session;

a first database for storage of the first status information;

a second data packet comprising second status information regarding the MVPN session; and

the processor for;

comparing the second status information to the first status information to determine whether the second status information is different from the first status information,

if the second status information is different from the first status information, then;

storing the first status information to a second database, and

storing the second status information to the first database, and

if the second status information is not different from the first status information, then;

discarding the second data packet, and

incrementing a counter in the first database.

11. The system of claim 10, wherein the first status information comprises an actual configuration of the MVPN session during a first time interval and wherein the second status information comprises an actual configuration of the MVPN session during a second time interval.

12. The system of claim 10, wherein the processor is further for:

receiving an expected configuration of the MVPN session;

if the first status information is stored to the first database, then;

comparing the actual configuration of the MVPN session during the first time interval to the expected configuration, and

if the actual configuration of the MVPN session during the first time interval does not match the expected configuration, then providing an alarm; and

if the second status information is stored in the first database, then;

comparing the actual configuration of the MVPN session during the second time interval to the expected configuration, and

if the actual configuration of the MVPN session during the second time interval does not match the expected configuration, then providing an alarm.

13. A system for passively monitoring a status of a multicast virtual private network (MVPN) session comprising:

a processor connected to a multicast data tree associated with the MVPN session,

information regarding an identity of a first participant in the MVPN session and an identity of a second participant in the MVPN session, the second participant being associated with the first participant;

a first data packet comprising first status information regarding the first participant and the second participant in the MVPN session;

a second data packet comprising second status information regarding the first participant and the second participant in the MVPN session;

a first database for storage of the first status information; and

the processor for;

comparing the second status information to the first status information to determine whether the second status information is different from the first status information

if the second status information is different from the first status information, then;

storing the first status information to a second database, and

storing the second status information to the first database, and

if the second status information is not different from the first status information, then;

discarding the second data packet, and

incrementing a counter in the first database.

14. The system of claim 13, wherein the processor is further for:

receiving an expected configuration of the MVPN session;

if the first status information is stored to the first database, then;

comparing the first status information to the expected configuration, and

if the first status information does not match the expected configuration, then providing an alarm; and

if the second status information is stored in the first database, then;

comparing the second status information to the expected configuration, and

if the second status information does not match the expected configuration, then providing an alarm.

15. A computer readable medium having a program in computer readable code which, when executed by a computer, cause the computer to:

connect to a multicast data tree associated with a multicast virtual private network (MVPN) session;

receive a first data packet comprising first status information regarding the MVPN session;

store the first status information regarding the MVPN session to a first database;

receive a second data packet comprising second status information regarding the MVPN session;

compare the second status information to the first status information to determine whether the second status information differs from the first status information;

if the second status information differs from the first status information, then;

store the first status information to a second database, and

store the second status information to the first database; and

if the second status information does not differ from the first status information, then;

discard the second data packet, and

increment a counter in the first database.

16. A computer readable medium having a program in computer readable code which, when executed by a computer, cause the computer to:

connect to a multicast data tree associated with a multicast virtual private network (MVPN) session;

receive information regarding an identity of a first participant in the MVPN session and an identity of a second participant in the MVPN session, the second participant being associated with the first participant;

receive a first data packet comprising first status information regarding the first participant and the second participant in the MVPN session;

store the first status information regarding the MVPN session to a first database;

receive a second data packet comprising second status information regarding the first participant and the second participant in the MVPN session;

compare the second status information to the first status information to determine whether the second status information differs from the first status information;

if the second status information differs from the first status information, then;

store the first status information to a second database, and

store the second status information to the first database; and

if the second status information does not differ from the first status information, then;

discard the second data packet, and

increment a counter in the first database.