Diagnostic tool and method for troubleshooting multicast connectivity flow problem(s) in a layer 2 aggregation network
A diagnostic tool and method are described herein that are capable of diagnosing and localizing a multicast connectivity flow fault within a layer 2 aggregation network. In one application, the diagnostic tool and method can be used by a customer service representative to diagnose why a customer cannot receive a television channel even though they can receive other television channels within an IPTV network.
1. A method for troubleshooting a multicast flow fault which was caused by an unsuccessful Internet Group Management Protocol (IGMP) join operation within a layer 2 aggregation network, said method comprising the steps of:
flooding a MAC discover message which contains a port identification of a target device which had initiated the IGMP join operation through-out at least a portion of said layer 2 aggregation network to discover a MAC address associated with the target device;
receiving a MAC reply message which contains the MAC address from said target device or from a device which is associated with said target device;
sending a request message which contains the discovered MAC address via one or more intermediate nodes towards said target device;
receiving one or more reply messages from said one or more intermediate nodes and said target device; and
analyzing the one or more received reply messages to determine which one of the intermediate nodes and/or the target device had not updated a forwarding database because of the unsuccessful IGMP join operation.
2. The method of claim 1 , wherein each intermediate node upon receiving the MAC reply message keeps track of both the discovered MAC address and a local port which received the MAC reply message.
3. The method of claim 2 , wherein each intermediate node upon receiving said request message inspects the discovered MAC address and forwards a new request message out the local port towards the target device.
4. The method of claim 2 , wherein each intermediate node and said target device upon receiving said request message inspects a multicast number located therein and queries the forwarding database to determine if there is a corresponding multicast number stored therein which is associated with the target device.
5. The method of claim 4 , wherein each intermediate node and said target device which makes a positive determination then sends the reply message which indicates that the multicast number associated with the target device was stored within the forwarding database.
6. The method of claim 4 , wherein each intermediate node and said target device which makes a negative determination then sends the reply message which indicates that the multicast number associated with the target device was not stored within the forwarding database.
7. The method of claim 4 , wherein said multicast number is:
an IP address; or
an Ethernet MAC address.
8. A diagnostic tool for troubleshooting a multicast flow failure which was caused by an unsuccessful Internet Group Management Protocol (IGMP) join operation within a layer 2 aggregation network, said diagnostic tool comprising:
an operator interface which facilitates the following steps:
flooding a MAC discover message which contains a port identification of a target device which had initiated the IGMP join operation through-out at least a portion of said layer 2 aggregation network to discover a MAC address associated with the target device;
receiving a MAC reply message which contains the MAC address from said target device or from a device which is associated with said target device;
sending a request message which contains the discovered MAC address via one or more intermediate nodes towards said target device;
receiving one or more reply messages from the one or more intermediate bridges and said target device; and
analyzing the one or more received reply messages to determine which one of the intermediate nodes and/or the target device had not updated a forwarding database because of the unsuccessful IGMP join operation.
9. The diagnostic tool of claim 8 , wherein each intermediate node upon receiving the MAC reply message keeps track of both the discovered MAC address and a local port which received the MAC reply message.
10. The diagnostic tool of claim 9 , wherein each intermediate node and said target device upon receiving said request message inspects the discovered MAC address and forwards a new request message out the local port towards the target device.
11. The diagnostic tool of claim 9 , wherein each intermediate node and said target device upon receiving said request message inspects a multicast number located therein and queries the forwarding database to determine if there is a corresponding multicast number stored therein which is associated with the target device.
12. The diagnostic tool of claim 11 , wherein each intermediate node which makes a positive determination then sends the reply message which indicates that the multicast number associated with the target device was located within the forwarding database.
13. The diagnostic tool of claim 11 , wherein each intermediate node which makes a negative determination then sends the reply message which indicates that the multicast number associated with the target device was not located within the forwarding database.
14. The diagnostic tool of claim 11 , wherein said multicast number is:
an IP address; or
an Ethernet MAC address.
15. A layer 2 aggregation network, comprising:
a diagnostic tool;
a first Maintenance End Point (MEP);
one or more Maintenance Intermediate Points (MIPs); and
a second MEP, wherein said diagnostic tool interfaces with said first MEP and troubleshoots a multicast flow failure caused by an unsuccessful Internet Group Management Protocol (IGMP) join operation by performing as follows:
discovering a MAC address which is associated with said second MEP, said discovering steps includes:
flooding a MAC discover message which contains a port identification of said second MEP out off said first MEP; and
receiving a MAC reply message which contains the MAC address from said second MEP, wherein each MIP and said first MEP which receives the MAC reply message keeps track of both the discovered MAC address and a local port which received the MAC reply message;
sending a request message which contains the discovered MAC address towards said second MEP via the one or more MIPs, wherein:
each MIP which receives said request message inspects the discovered MAC address and forwards a new request message out the local port behind which resides the second MEP;
each MIP and said second MEP which receives said request message inspects a multicast number located therein and queries a forwarding database to determine if there is a corresponding multicast number stored therein which is associated with the second MEP;
wherein each MIP and said second MEP which makes a positive determination then sends a reply message which indicates that the multicast number associated with said second MEP was stored within the forwarding database; or
wherein each MIP and said second MEP which makes a negative determination then sends a reply message which indicates that the multicast number associated with said second MEP was not stored within the forwarding database;
receiving one or more reply messages from the one or more MIPs and said second MEP; and
analyzing the received reply messages to determine which one of the MIPs and/or said second MEP had failed to update their multicast forwarding database because of the unsuccessful IGMP join operation.
16. A method for troubleshooting a multicast flow failure which was caused by an unsuccessful Internet Group Management Protocol (IGMP) join operation within a layer 2 aggregation network, said method comprising the steps of:
sending a request message which contains a MAC address associated with a target device which initiated the IGMP join operation, obtained by flooding a MAC discover message which contains a port identification of the target device through-out at least a portion of said layer 2 aggregation network, via one or more intermediate nodes towards said target device;
receiving one or more reply messages from said one or more intermediate nodes and said target device; and
analyzing the one or more received reply messages to determine which one of the intermediate nodes and/or said target device had failed to update a forwarding database because of the unsuccessful IGMP join operation.
17. The method of claim 16 , wherein each intermediate node upon receiving said request message inspects the MAC address and forwards a new request message out the local port behind towards the target device.
18. The method of claim 16 , wherein each intermediate node upon receiving said request message inspects a multicast number located therein and queries the forwarding database to determine if there is a corresponding multicast number stored therein which is associated with the target device.
19. The method of claim 18 , wherein each intermediate node and said target device which makes a positive determination then sends the reply message which indicates that the multicast number associated with said target device was stored within the forwarding database.
20. The method of claim 18 , wherein each intermediate node and said target device which makes a negative determination then sends the reply message which indicates that the multicast number associated with said target device was not stored within the forwarding database.