Ascertaining the availability of communications between devices

[0001] Applicant claims priority of U.S. provisional applications 60/384,546 filed May 30, 2002 and 60/424,143 filed Nov. 6, 2002.

[0002] The present invention relates generally to measuring the availability of communications between devices, and more particularly to mechanisms for measuring availability of communications paths between network devices.

[0003] As today's data networks become more flexible and powerful, network users use network resources in many different ways. Network resources are used for purposes ranging from data transfer to video on demand. These various usages require differing amounts of bandwidth and other quality of service metrics at different times. Many network users therefore contract for network services through service level agreements (SLAs) with service providers. Pricing for network services depends, amongst other things, upon the availability of the network, as network users do not want to pay for network services during network outages. Therefore, service providers require a means for measuring network availability.

[0004] Availability in IP networks is currently difficult to measure. Service measurements currently depend upon counting lost packets and measuring packet latency. When counting lost packets, individual failures tend to get averaged out. For example, a one in one hundred failing becomes a 1% packet loss, no matter how long the failure lasted. There is currently no way to characterize outages in IP networks with respect to time. Thus, it is difficult to provide an SLA for charging a network user with respect to availability.

[0005] It would be desirable to be able to measure availability of a network with respect to time, so that service providers can offer superior SLAs.

[0006] In accordance with the principles of the invention, a first device generates a first knowledge digest encoding first configuration information that is associated with communications to a second device. The first device receives from the second device messages including second knowledge digests encoding second configuration information. The first device compares the first knowledge digest to the second knowledge digest and produces an indication if the second configuration information encoded in the second knowledge digest is not a subset of the first configuration information encoded in the first knowledge digest. The first device indicates the availability of communications between the first device and the second device as long as second knowledge digests continue to be received from the second device and no indication occurs. The first device indicates the unavailability of communications between the first device and the second device if second knowledge digests are not received from the first network element after an interval of time.

[0007] According to one aspect of the invention, the first and second knowledge digests are fixed length bit arrays, which may be implemented as bloom filters.

[0034] In many system environments, configuration information is associated with two or more communicating devices. In some such systems, one device originates the configuration information, and one or more other devices use the configuration information. The configuration information is often time varying in nature. One example of such a system is a provisioned networking environment. One system in the networking environment, herein referred to as an originating network element, communicates configuration information to other systems—referred to as user network elements—in the networking environment. The configuration information may be related, for example, to communications paths employed by the users to reach the originating network element, or for service parameters associated with those paths, or the like. In such systems, it is advantageous to be able to verify that the configuration information used by a system is in fact the correct configuration information and when explicitly associated with connectivity, simultaneously verify the connectivity is similarly correct. In the network system example, it is advantageous to be able to verify that the configuration information used by a user network element is consistent with the configuration information that was actually issued to it by the originating network element.

[0035] Furthermore, configuration information in such systems may change over time or have subtle differences due to filtering by the user network element. For example, in a networking environment, configuration information issued by an originating network element to user network elements may need to be updated periodically because of routing changes. Such a re-configuration results in a finite delay in synchronizing the sets of configuration information between the originating network element and the user network elements. So, when verifying configuration information, it is further advantageous to be able to ascertain whether a configuration mismatch is a result of a configuration change that has not yet propagated through the system (which may be considered to be an artifact of normal network operations) as opposed to a genuine configuration or connectivity problem.

[0036] Configuration information associated with such systems is often complex, and a given system might maintain configuration information for a large number of other systems. Where it is desirable to periodically verify configuration information, it is often unreasonable to do so by distributing and comparing the configuration information itself, because the overhead of doing so is too intensive. Furthermore, comparison of complex configuration information in, for example, a given network element would most likely occur in software on a central processor (rather than in a distributed, per-interface manner), further over-tasking the system.

[0037] In accordance with the principles of the invention, it is possible to efficiently verify configuration information between two systems without the need to transfer the configuration information in its entirety between systems. This allows the systems operator to verify that there is no misconfiguration—i.e. the device that originates the configuration information has the same overall system view as the devices that are receiving it; further, when the configuration is explicitly associated with connectivity between the systems, that there is no misdirection of information—i.e. the connectivity between devices has not been misdirected. Further, the systems operator can verify that incremental changes to configuration information are propagated in a reasonable amount of time, and that connectivity has been maintained between the originating devices and user devices.

[0038] It should be understood that, for all general and particular systems to which the following described principles of the invention may apply, communication may occur at many different layers between the devices that comprise the system. Thus, a device may be an originating device with regard to one application, while also being a user device with regard to another application. For example, in a networking environment, an internetworking gateway between an ATM and MPLS networks may originate path configuration information at the ATM level, but may at the same time be a user of MPLS configuration information originated from another switch. So, one skilled in the art will understand from the teachings herein that many instantiations of origination and user modes may exist within one device, operating concurrently.

[0039] Referring now to FIG. 1, there is shown a generalized networking system 10 in which the principles of the invention are employed. Referring also to FIG. 2, the processes used by the originating network element 12 and a user network element 14 are shown. An originating network element 12 maintains configuration information 15 which may be related to connection paths to other network elements, or to characteristics associated with those paths, or the like. The originating and user network elements operate as follows:

• • [0040] 1. The configuration information 15 is distributed to other user network elements 14 in accordance with the networking system protocols in known manners (step 16). In accordance with the invention, the originating network element 12 also encodes the configuration information into a knowledge digest 18 (step 20).
  • [0041] 2. The user network elements 14 also encode the configuration information that they have most recently received from the originating network element 12 into a knowledge digest 24 (steps 26, 28).
  • [0042] 3. The user network elements 14 periodically forward their user knowledge digests 24 from a user interface 29 to the originating network element 12 (step 30).
  • [0043] 4. The interface 32 within the originating network element 12 that receives the knowledge digest 24 compares the knowledge digest 24 to the knowledge digest 18 that it maintains for the given user network element 14 (steps 34, 36). A mismatch indicates that the configuration information sent by the originating network element 12 does not match the configuration information currently in use by the user network element 14 (step 38).
  • [0044] 5. The originating network element 12 can then notify, for example, central processing resources 40 within the network element 12 that there may be a misconfiguration (step 42). Or, further analysis may occur as will be further described. If there is no mismatch, then the configuration information is consistent between the originating network element 12 and the user network element 14. If there has been a configuration update (step 44), the originating network element will issue the new configuration information (step 16) and update its knowledge digest (step 20). Otherwise, the originating network element will continue to monitor incoming user knowledge digests (step 34).

[0045] One mechanism for providing a knowledge digest with the desirable properties is known as a bloom filter. A bloom filter is a fixed length lossy knowledge test implemented as a bit array. As shown in FIG. 3, a bloom filter 46 uses hashing techniques to condense a representation of a token of information 48 from a set into one or more bits in a bit array 50. One or more hashes 52 of the information token (e.g. network configuration information) is taken, modulo the length of the bit array 50. The result is used as an offset into the array, to set the bit at that location in the array. The set bit represents the existence of the token of information in the set. If the length of the bit array 50 is less than the size of the set of information tokens 48 (as it should be when used for compression purposes), then there is a given probability that more than one token will hash to the same value. In this scenario the bit being set represents a probability of the token being in the set. If the bit is not set, the probability of set membership is zero. Filter engineering can produce a very high probability that a set bit represents the existence of the information token in the set. The probability of obtaining a false positive result from a bloom filter is:
P_err=(1−(1−1/m)^kn)^k

[0046] Where m=filter size, k=number of hash functions used, and n=number of elements in the set (e.g. number of FECs per LSP). The larger the length of the filter, the smaller the probability of a false positive. However, the length of the filter affects the CV PDU size and makes implementation demands, and so should not be excessively large. Filter operations are most easily performed if the filter size is based on a power of 2 and results in a filter of some even number of octets in length. Increasing the number of hashes also decreases the likelihood of obtaining false positives below a given density of information encoded in the filter. Many known hash algorithms may be used, for example CRC polynomials, MD2, MD5, SHA1, or SHA256 (although a number of these are cryptographic hashes and have properties beyond the simple randomization that a bloom filter requires). The number of undetected faults will rise slightly where there is more than one element per filter.

[0047] When considering a mix of applications sharing a network, one skilled in the art will realize that different applications will have different configuration requirements. The number of tokens that needs to be uniquely identified varies significantly. For example, in a VPN application, between any two provider edge devices, the transport network may only need to encode a single token describing connectivity with a target edge device, while the service layer may need to associate a number of customer routes and other configuration details with the service connectivity. This suggests that in a network that contains a mixture of applications, no one set of filter coding rules will optimize error detection across the set of applications supported by the network.

[0048] When considering detecting misconfiguration and misbranching for filters with heterogeneous coding rules, the generalized equation for false positives can be modified:
P_err=(1−(1−1/m)^kn)^pq

[0049] Where m=the filter length, k=the number of bits per token used by the originator, n is the number of tokens encoded in the originator filter, p is the number of bits per token employed by the user and q is the number of user tokens encoded in the user filter. When minimum, maximum and average tokens per application are known, this generalized equation permits a weighted matrix to be defined such that filter engineering can be tuned for each application relative to both itself and the other applications supported by the system in order to optimize overall fault coverage.

[0050] Referring now to FIG. 4, a variation on the generalized network of FIG. 1 is shown, wherein the configuration verification mechanism is tolerant of transient changes in configuration information. The originating network element 12 is herein shown to maintain two knowledge digests, a current knowledge digest 18 and a cumulative knowledge digest 54. The current knowledge digest 18 encodes the currently distributed configuration information, as previously described. The cumulative knowledge digest 54 encodes the cumulative set of configuration information that has been distributed over some time. In a properly operating system there may be two outcomes (which are specific characteristics of the application being verified):

[0051] 1) The current knowledge digests should eventually be identical at both the user and originating systems.

[0052] 2) The user digest will be a subset of the originator digest (as a result of allowed user policy, or policy applied at some intermediate element).

[0053] But, certain transient exceptions are tolerated (and in fact should be tolerated in order avoid false failure notification). For example, when the user network element 14 receiving the configuration information produces a knowledge digest 24 that is a subset of the current knowledge digest 18 encoding the configuration information sent from the originating network element 12, this may indicate that configuration information has been added to the system, but this information has not yet propagated to the user network element 14. Also, when the knowledge digest 24 is a superset of the current knowledge digest 18, but not a superset of the cumulative digest 54, this may indicate that some configuration information has been removed, but that this information has not yet propagated to the user network element 14. Both such scenarios should be tolerated for some finite amount of time to allow system synchronization. After a predetermined amount of time, if synchronization has not occurred, an error is indicated.

[0054] Referring to FIG. 5, there is shown the process by which the current knowledge digest and cumulative knowledge digest are used by the originating network element 12 to ascertain whether configuration errors exist or whether the system is merely not yet synchronized. At step 56, the incoming knowledge digest 24 received from the network element 14 is compared to the current knowledge digest 18. If the incoming knowledge digest 24 is not a subset of the current knowledge digest 18 (step 58), then the incoming knowledge digest 24 is compared with the cumulative knowledge digest 54 (step 60). If the incoming knowledge digest 24 is a subset of the cumulative knowledge digest 54 that is, if the incoming knowledge digest 24 is the same as, or contains fewer set bits than the cumulative knowledge digest 54 (step 62)—then a synchronization timer is checked (step 64). If the timer has not expired, then it is possible that configuration information has been added by the originating network element 12, but that information has not yet propagated to the network element 14. The interface 32 may or may not choose to notify the central processor 40 that network synchronization has not yet occurred (step 66), and returns to processing incoming knowledge digests. If the timer has expired (step 64), then the network has for some reason failed to synchronize. In this case, an error is indicated (step 68).

[0055] Referring back to step 62, if a mismatch exists but the incoming knowledge digest 24 is not a subset of the cumulative knowledge digest 54, then a configuration error is indicated (step 70), because some configuration information exists at the user network element 14 that was never sent from the originating network element 12.

[0056] Referring back to step 58, if the incoming knowledge digest is 24 is a subset of the current knowledge digest 18, then it is compared to the current knowledge digest 18 to see if the digests match perfectly. If they match, then the configuration information being used at the user network element 14 is correct and there are no synchronization problems (step 72). If the match is not perfect, then the synchronization timer is again checked (step 74). If the timer has not expired, then it is likely that some configuration information has been removed by the originating network element 12, but that the new information has not yet propagated to the user network element 14. The interface 32 may or may not choose to notify the central processor 40 that network synchronization has not yet occurred (step 76), and returns to processing incoming knowledge digests. If the timer has expired (step 74), then the network has failed to synchronize and a synchronization error is indicated (step 78.)

[0057] In the system of FIGS. 4 and 5, the current and cumulative knowledge digests, and the incoming knowledge digests, may be advantageously implemented as bloom filters.

[0058] The principles of the invention can be applied in many different types of systems. For example, tunneling architectures can be tested for misconfiguration, leakage between tunnels, misbranching of tunnels, routing system problems, and the like. Several applications of the invention are now described as examples of how the principles of the invention can be adapted to different types of tunnel architectures.

[0059] 1. MPLS

[0060] In FIG. 6 there is shown a Multi-Protocol Label Switched (MPLS) network 110 in which a verification probe in accordance with the principles of the invention can be used. In an MPLS network, data packets to be forwarded across the network 110 are associated with fixed-length labels and then switched across the network from ingress to egress based on label values. In particular, data packets are received at a network element known as an ingress Label Switched Router (LSR) at the edge of the network 110, such as LSR 112. The ingress LSR 112 examines a received data packet 114 and associates the packet with a forwarding policy indicator known in MPLS as a Forwarding Equivalence Class (FEC) 116. Packets are classified into FECs on the basis of sharing common forwarding policy in the MPLS network. FECs may be assigned for example based on an IP address, or a group of IP addresses, or a host address, or a class or type of service assigned to the packet. An FEC acts as a “functional description” of an LSP independent of the particular instantiation or position in the network topology. Examples of FECs for IPv4 addresses and host addresses in accordance with RFC 3036 is shown in FIG. 7. The ingress LSR 112 indexes an FEC to Next Hop Label Forwarding Entry (FTN) table 118 to retrieve a label 120 that is associated with the FEC for the packet. The label is appended to the packet in any of a number of known ways, dependent upon the type of network upon which the MPLS network is implemented. As herein shown, a packet with IP address 192.168.2.1 is assigned an FEC associated with the group of IP addresses 192.168/16. This FEC is used to index the FTN table 118 and retrieve a label of ‘43’. The label ‘43’ is appended to the packet, and the packet is then forwarded to the next LSR 122 along a Label Switched Path (LSP) 124. The LSR 122 uses the label ‘43’ to index a label information base (LIB) 126 to retrieve a new label, herein shown as ‘57’. The LSR 122 swaps the new label ‘57’ for the old label ‘43’, and forwards the packet to the next LSR 128 along the LSP. The LSR 128 swaps the label in the same manner as the LSR 122 did, swapping the label ‘57’ for the label ‘65’, and forwards the packet to the next LSR 130 along the LSP 124. As herein shown, the next LSR 130 is an egress LSR—that is, the LSR 130 is the router at which the MPLS LSP is terminated, all labels have been popped from the packet, and the packet is forwarded on to its destination. The LSRs between the ingress and egress LSRs are referred to as intermediate LSRs, and there may be an arbitrary number of them.

[0061] Some MPLS networks implement a mechanism known as penultimate hop popping (PHP), wherein the intermediate LSR one hop upstream from the egress LSR pops the top label off the label stack, saving the egress LSR from performing the operation. If PHP were enabled in the network 10 of FIG. 1, then the label ‘65’ would have been popped at the intermediate LSR 28.

[0062] There are a variety of known ways to configure LSPs. Provisioning, control driven methods, also known as explicitly routed LSPs (ER-LSPs) may be used to create LSPs. In accordance with these methods, the LSP is created by the ingress LSR, which has specified an explicit path to some degree of detail through the MPLS network to the egress LSR. The path is thus considered “source-routed”. The end-points of ER-LSPs are fixed at specific interfaces and the LSPs are point to point, so that there is a 1-to-1 relationship between the LSP ingress and LSP egress. Protocols that can be used to configure ER-LSPs include CR-LDP and RSVP-TE.

[0063] Application specific mechanisms exist to distributed MPLS labels and associate configuration information with the label. RFC 2547 BGP VPNs use the BGP4 protocol to distribute VPN specific labels, and associate information about the VPN client network with the labels. The LDP protocol includes the ability to distribute labels and configuration information to non-adjacent peers and is used in some proposed implementations of “pseudo wires”.

[0064] Topology driven methods are also available for configuring what are known as implicitly routed LSPs. Topology driven LSPs are currently created via Label Distribution Protocol (LDP) signaling, and are herein referred to as LDP-LSPs. The principles of the invention can be applied to detect mis-configuration and mis-forwarding across the entire MPLS tunnel architecture, regardless of how the labels are distributed. However, LDP-LSPs presents certain complexities; therefore, the application of the invention to LDP-LSP tunnels is herein described in detail.

[0065] Referring to FIG. 8, one mechanism used by LDP for label distribution is known as “downstream unsolicited” label distribution. The egress LSR 130 advertises label/FEC bindings by sending Advertisement messages 134 containing the FEC/label bindings to its peers, herein intermediate LSR 128. Each intermediate LSR along the path compares the label advertisements with its local routing database and configures itself to use the best path for a given FEC based on network routing information available to it. The Advertisement messages 134 eventually propagate to the ingresses, but only knowledge of the FEC is preserved, identification of the egress LSR originating the advertisement is not propagated.

[0066] Referring now to FIG. 9, there is shown another type of label distribution used by LDP, know as “downstream on demand” label distribution. An ingress LSR 112 forwards a label request message 132 into the MPLS network. The label request message 132 propagates downstream. If a downstream LSR receiving the label request message 132, already has an LSP set up for the FEC requested, it returns the label that maps the FEC into the existing LSP in an LDP Advertisement message 134. If it does not have an LSP set up for the FEC requested, it sends a label request message 132 to the next downstream LSR. If no labels have been set up for the FEC at all, then the label request message 132 is eventually received a viable egress LSR for the FEC 30, which assigns a label for the one or more FECs and forwards the label back through the MPLS network in an LDP Advertisement message 134. Advertisements proceed back towards the ingress LSR, which receives the final Advertisement including a label for forwarding to the next hop LSR for the LSP. It is this label that the ingress LSR 112 stores in its FTN 118 for the FEC. According to this process, the egress LSR 130 may associate a group of FECs with an LSP—for example, FECs A, B, and C. Intermediate LSRs may associate a subset of these FECs with the LSP—for example, A and B. The ingress router may in turn associate a further subset of the FECs with the LSP—for instance, just A. So, the egress router 130 associates an LSP with a set of FECs, and the ingress router 112 injects a subset of those FECs into the LSP, where the subset may be all or fewer than all of the FECs associated with the LSP by the egress LSR 112.

[0067] Label bindings for FECs can change over time as the network elements determine the current shortest path for specific FECs in the network and modify the connectivity accordingly. As labels are advertised, LSRs may remember the labels they receive regardless of whether they are using them or not (“liberal label retention”), or LSRs may prune the set of labels retained when compared with the routing database (“conservative label retention”). When using liberal label retention, when the routing protocol receives new information and computes a new view of the network, the best next hop for an FEC may change. When this happens, the LSR will check to see if it has retained a label for that FEC on the new best next hop and will configure itself to use the new label instead of the one it was previously using for the FEC. If an LSR has no label retained for a new next hop—which will frequently be the case when using conservative label retention—it may use downstream on demand label distribution to request one. Thus, LDP MPLS LSPs are transitory in nature.

[0068] In addition, MPLS allows two different modes of label distribution, known as “ordered” and “independent”. In “ordered” mode, an LSR cannot advertise label bindings for an FEC until it has received FEC/label bindings from downstream peers. In “independent” mode, and LSR may advertise label bindings as soon as it has knowledge of an FEC—for instance, from a routing protocol. Such an LSR may advertise a label binding for FEC ‘A’ and a separate label binding for FEC ‘B’ before it receives an aggregated label binding for both FECs ‘A’ and ‘B’ from a downstream LSR.

[0069] To summarize, the attributes of the set of FECs associated with an LSP are:

• • [0070] a number of FECs can be associated with an LSP. These are currently in the form of routing prefixes or host routes, but it is anticipated that they may also be in the form of class of service or quality of service forwarding policies, or any type of treatment that could be common to a group of packets.
  • [0071] The number of FECs associated with an LSP may change over time.
  • [0072] The number of FECs associated with an LSP can be added to, or subtracted from.
  • [0073] An ingress may only choose to use an LSP for a subset of the advertised FECs associated with the LSP.
  • [0074] FEC aggregation does not occur—that is, a more specific FEC prefix will not be subsumed by a more general FEC prefix at an intermediate node.
  • [0075] When an LDP intermediate node receives an FEC advertisement for an LSP, it may choose only to advertise a portion of that list upstream as it may assume for some of the FECs, more optimal paths exist on different LSPs.

[0076] In any type of network, it is highly desirable to be able to test connectivity between an ingress point and an egress point. For MPLS networks, a standard known as ITU-T Y.1711, “OAM mechanism for MPLS networks”, describes mechanisms for user-plane Operation and Maintenance (OAM) functionality for point-to-point (P2P) LSPs. One such mechanism is a Connectivity Verification (CV) probe. Use of the CV probe permits (amongst other things) misbranching (leakage) between ER-LSPs to be detected. Leakage of LDP-LSPs into ER-LSPs can also be detected but leakage of client LSPs (BGP VPN and PW LSPs) and leakage between LDP-LSPs cannot be detected. Misbranching can manifest itself in several forms. First of all, a label can be cross connected onto a label value that is not in use. Traffic containing such a label is discarded at the next LSR on the LSP, as there will be no incoming label map in the LIB for the packet. Secondly, a label can be cross connected onto a label that is being used. This will result in traffic being delivered to the wrong egress point in the network. Finally, an LSR can assign an incorrect FEC to a label at the ingress. This will result in traffic being delivered to the wrong egress point in the network.

[0077] The currently defined CV probe 135 is shown in FIG. 10. CV probes are transmitted periodically (e.g. 1/s), from an ingress LSR to an egress LSR. CV probes are one of several types of OAM messages identified by a pre-defined label value of 14. The payload of the packet with label value 14 contains the CV probe shown. The function type field 136 identifies various types of OAM packets, with ‘01 hex’ identifying a CV packet. The padding field 138 is used to extend the packet to minimum required lengths for various network technologies, and the BIP 16 field 140 is an error detection field. Each CV packet carries a unique Trail Termination Source Identifier (TTSI) 142. The TTSI 142 is composed of the source LSR identifier, and an LSP identifier which serves to function as an access point identifier for the LSP. For ER-LSPs, the TTSI is established at LSP set-up time. As previously described, ER-LSPs are point-to-point, established between fixed interfaces at fixed end points, so that there is a 1-to-1 relationship between the LSP ingress and the LSP egress. Therefore, a CV probe flowing from the ingress to the egress that identifies the access point the ingress believes it is probing is normally sufficient to detect misbranching. When the egress LSR receives a probe with an unexpected TTSI value, it is able to flag the error to network management. For example, if an egress LSR receives CV probes with TTSI values that are unexpected, and receives no CV probes with TTSI values that are expected, then a misbranch error is indicated—that is, labels are cross-connected at some point along the LSP. If the egress LSR receives CV probes with TTSI values that are both expected and unexpected, a particular type of misbranch error known as a mismerge error is indicated—that is, one LSP's labels are being erroneously cross-connected onto another valid LSP. Thus, the currently defined CV probe is able to detect leakage between ER-LSPs, and from LDP-LSPs into ER-LSPs, since the TTSIs from LDP-LSPs will not match the expected TTSI.

[0078] However, the CV probe as currently defined cannot detect leakage between LDP-LSPs, stacked (client) LSPs into LDP-LSPs or from ER-LSPs into LDP-LSPs. This is because there is no fixed association between the ingress/egress points for an LDP-LSP that can be tested. As previously described, there is no explicit binding between LSP end points in an LDP-LSP; they may move over time, between LSRs or between interfaces on a single LSR. Furthermore, an ingress LSR may have a choice of multiple LSPs on multiple interfaces for a given FEC, and may choose to move the FEC to a different LSP. Connectivity between ingress and egress LSRs varies over time as the intermediate LSRs modify label bindings in response to changes in the resources available to the network. So, CV probes injected into an LDP-LSP will emerge at different interfaces and LSRs over time, yet the network is functioning correctly. The CV probe TTSI cannot therefore be relied upon to detect leakage between or from LDP-LSPs. However, it is highly desirable to be able to verify LDP-LSP connectivity, because there are numerous modes of failure that can undermine the correct operation of MPLS LDP-LSPs. In normal operation, FEC to label bindings flow via signaling from the egress towards the network ingress points. An LSR in the network will receive numerous FEC/LSP advertisements, may choose to remember any arbitrary subset, and at any given time selects the optimal LSP to use for an FEC on the basis of information received from other sources (e.g. the interior gateway routing protocol, IGP). Correct operation of the network depends on all LSRs having a synchronized view of the network to base their local MPLS configuration upon and the correct functioning of a significant amount of hardware and software both on and off the forwarding plane. This is a non-trivial system in operation, and adds a layer of complexity to the normal operation of IP networks as once routing convergence has completed, any MPLS re-configuration is still required. A mechanism to audit this behavior would be advantageous. Furthermore, unlike traditional IP networks, the formal decomposition of forwarding policies into FECs, and binding of FECs to paths, simplifies the function of overall verification of the forwarding system. In addition to the usual link and adjacency testing, simply verifying that the set of FECs associated with an LSP ingress corresponds to or is a subset of the set of FECs advertised by the LSP egress NE can catch all manner of misconfiguration, software, or hardware problems not detectable by other means.

[0079] In accordance with the principles of the present invention, a probe is provided to detect leakage between LDP-LSPs, and is distinguishable in some form from the probe used for ER-LSPs such that leakage from ER-LSPs into LDP-LSPs can be detected.

[0080] Furthermore, other applications may be overlaid on the LDP network. These include pseudo wires, BGP VPNs, etc. and it is possible for these to leak into the LDP layer for any of a number of reasons, e.g. lack of synch between MPLS layers, failure to properly configure LDP on an interface etc. So the probe also detects misbranching between layers, as well as within the specific layer.

[0081] First, it is realized that, though the TTSI value of a CV probe does not represent a 1-to-1 binding between an ingress and egress LSR in an LDP-LSP, the set of FECs that represent the forwarding policy from the ingress to the egress is consistent over time. As previously described, the egress LSR will advertise labels for a set of FECs that it will forward. The advertisement is passed back through the network to the ingress LSR, which is assigned labels for all or a subset of the FECs that were advertised by the egress LSR. The ingress LSR examines incoming packets, and maps the packet destinations to the known set of FECs and thereby determines which LSPs to forward the packets upon. So, if the egress LSR has knowledge of the set of FECs being forwarded by ingress LSRs, then the egress LSR can verify that the correct label bindings are being used by the ingress LSRs by comparing the set of FECs the ingress believes it is injecting into the network to the set of FECs the egress advertised. Referring to FIGS. 11 and 12, a basic solution would be:

• • [0082] 1) an egress LSR 130 sends an advertisement message 134 back towards the ingress LSR 112 (step 146). The advertisement message contains a set of FEC/label bindings.
  • [0083] 2) A central processor (CP) 148 in the ingress LSR 112 receives an advertisement message 134 from the next hop LSR (step 150) and binds a subset of the advertised FECs to the label by entering the subset of FECs and the label into the FTN and NHLFE (step 152).
  • [0084] 3) the ingress LSR 112 encodes in a probe message 154 the set of FECs that it knows about or chooses to use for the LSP just bound. The probe is sent from one of the OAM interfaces 155 on the ingress LSR 112 down the LSP to the egress LSR 130 (step 156). This set of FECs can be extracted from the LDP advertisement message, or from the FTN table. To provide ongoing verification, after a certain time interval, the ingress LSR 112 re-sends the probe message 154 (step 158). The ingress LSR 112 continues to periodically send the probe message 154 until the label binding expires (step 160). The label binding may expire, for example, because the ingress LSR 112 has chosen to use a different LSP for the FEC, in which case probe messages will continue to be periodically sent down the new LSP.
  • [0085] 4) The egress LSR 130 receives the probe message 154 (step 162) on one of its OAM interfaces 165 and compares the set of FECs received in the probe 154 against the set of FECs it advertised for the LSP and identifies any mismatches (step 164, step 166, step 168). Any mismatch would indicate a misbranch error. If a mismatch is found, the egress LSR CP 60 is notified of an error (step 162). Various actions may be taken by network management functions in response to the error. Otherwise, the egress LSR 130 continues to monitor the probe messages (step 170).

[0086] Though functional, this solution involves parsing two FEC lists of arbitrary length and ordered arbitrarily, and comparing the sets of information tokens (i.e. individual FECs) contained in the lists to ensure that the ingress list is a perfect subset of the egress list. Each FEC is many bytes long. Such a comparison can be difficult to implement in hardware. An improved solution provides a simple means of encoding knowledge of the FECs associated with an LSP such that a simple mechanical comparison is possible to determine if the ingress believes there are FECs outside the subset advertised by the egress for the LSP. Ideally, a knowledge digest would produce a fixed length bit array encoding the set of FECs for the ingress and egress. Thus, no parsing would be required. Also, these bit arrays should be comparable to establish if the information encoded in one bit array is a subset of the information encoded in the other bit array. This is useful for determining if the set of FECs encoded in one probe message is a subset (i.e. all or fewer) of FECs advertised by the LSP egress. Simple Boolean operations comparing the bit array offered by the ingress with that programmed into the egress would identify if a mismatch exists in the sets of information represented. The processing of a knowledge digest with such properties can be easily implemented in hardware and can provide a highly scalable solution.

[0087] The knowledge digest may be advantageously implemented as a Bloom Filter, as previously described. The bloom filter can be applied as a simple means of representing a set of FECs. The egress LSR creates a filter representing the set of FECs it is advertising for an LSP. The ingress LSR creates a filter representing the set of FECs associated with an LSP and instantiated in the FTN. This should correspond to, or be a subset of, the set of FECs advertised by the egress for the termination of the LSP. Therefore all bits set in the ingress filter should also be set in the egress filter. When there is a mismatch, i.e. when there are bits set in the ingress filter that are not set in the egress filter, it is an authoritative indication that the ingress or an intermediate network element is misdirecting packets. Where there is only a very small statistical probability that the ingress is misdirecting packets.

[0088] More particularly, referring to FIGS. 13 and 14, the bloom filter is applied as follows:

• • [0089] 1) Upon receipt of a label request or prior to receiving an unsolicited binding, the egress LSR 130 encodes the set of FECs it is offering for an LSP into a bloom filter 172 (FIG. 14 steps 180, 182). The OAM module 165 on the interface the LSP is offered upon is programmed with the filter value.
  • [0090] 2) The egress LSR 130 sends an LDP Advertisement message 134 containing the FEC/label bindings to its peers (step 184).
  • [0091] 3) At some point later, the ingress LSR 112 receives an LDP advertisement of an FEC/LSP binding. The ingress LSR 112 loads the label bindings into its FTN (steps 186, 188).
  • [0092] 4) The ingress LSR 112, using the same encoding procedure as was used by the egress LSR 130, encodes the set of FECs it is using for that LSP as a bloom filter 190 (step 192). The ingress may use the set of FECs received in the LDP advertisement, or it may extract the set of FECs from the FTN/NHLFE for the outgoing label.
  • [0093] 5) The ingress LSR 112 sends a probe message 194 containing the bloom filter 190 to the egress LSR 130 by injecting the probe message 194 into the LSP (step 196). The ingress LSR 112 continues to send the probe messages 194 at pre-determined intervals as long as the ingress LSR 112 uses the current label binding for the FEC (steps 196, 198, 200).
  • [0094] 6) The OAM interface 165 on the egress LSR 130 receives the probe message 194 and extracts the filter (step 202). It compares the filters by logically ‘AND’ ing the inverse of the filter programmed into the egress LSR with the filter received from the ingress LSR (step 204). If a non-zero value results (step 206), then the FECs being injected onto the LSP by the ingress LSR 112 are not a subset of the FECs being received on the LSP by the egress LSR 130, and the OAM interface 165 sends a misbranch indication to the CP 160. If a 0 value results, then the FECs being injected onto the LSP by the ingress LSR 112 are a subset of the FECs being received on the LSP by the egress LSR 130, and the network is operating correctly. The egress LSR 130 will continue to monitor the probe messages 94 and perform the misbranching (step 210).

[0095] One special case for consideration relates to deletion of an FEC from an LSP. Under certain circumstances, an LSR may remove an FEC from the set of FECs associated with an LSP. This information will take a variable length of time to propagate across the network. If the LSR immediately modifies the bloom filter associated with the LSP in the OAM module, then false mismatches will occur until the network view of the FECs associated with the LSP is synchronized. This can be addressed in a number of ways. Assuming the egress LSR 130 is removing an FEC from an FEC/LSP binding, it may do any of the following (but is not restricted to these particular solutions):

• • [0096] 1) The egress LSR 130 removing the FEC/LSP binding waits some reasonable length of time before modifying the OAM module 165 with the new filter value.
  • [0097] 2) Referring to FIG. 15, the OAM module 165 contains two filters, one being the current set of FECs advertised for the label, and the other being the cumulative set ever offered for the label. The egress LSR 130 deletes an FEC from an FEC/LSP binding (step 214). The current filter is updated to reflect the new set of FECs (step 216). The filter in an incoming probe message 194 is compared to the current filter (step 218). If there is a mismatch (step 220), indicating that the set of FECs being received from the ingress LSR 112 is not a subset of the set of FECs currently being advertised by the egress LSR 130, then the filter in the incoming probe message 194 is compared to the cumulative filter (step 222). If the filter in the incoming probe message 194 matches the cumulative filter while mismatching the current filter (step 224), then this may indicate that the FEC/LSP bindings have not yet converged, so a warning is generated, not an error (step 226). A timestamp can be associated with the last change such that past a certain length of time (step 228), the warning becomes an error (step 230), indicating that the network has failed to synchronize. If the filter in the incoming probe message 194 does not match either the current or cumulative filter, then a misbranching error is indicated. Some period of time after the FEC/LSP label bindings were changed (step 232), the egress LSR 130 returns to normal single filter processing as previously described (step 234).

[0098] There are many different sorts of protocol probe messages that could be used to transport the knowledge digest from ingress to egress in accordance with the principles of the invention. In one particular implementation, the probe message 94 is adapted for use with the ITU_T Y.1711 OAM standard. The probe message may be implemented as a new type of OAM message. Or, the Y.1711 CV messaging may be modified such that LDP-LSP misbranching detection is possible. As previously described, current implementations of Y.1711 discard CV messages at LDP terminations. At ER terminations, only the TTSI is checked. Referring to FIG. 16, there is shown an example of a specific variation of the ITU_T Y.1711 CV probe message 236 in accordance with the invention, known as an FEC-CV probe message. The function type field 136 encodes a new type of message, the FEC-CV type message. A filter field 240 has been added for storing the bloom filter. Referring to FIG. 17, CV messages are then handled as follows:

• • [0099] 1) If the CV message 236 arrives at an LDP-LSP termination (egress LSR 130), (step 242) and the function type field 136 indicates that it is not an FEC-CV probe message (step 244), i.e. the message is of an unexpected type, then misbranching from an ER-LSP (or other LSP type using CV) into an LDP-LSP is occurring (step 250).
  • [0100] 2) If the CV message arrives at an LDP-LSP termination and the function type field 136 indicates that it is an FEC-CV probe message (step 244), then perform the previously described misbranching test (step 252, 253). If the misbranching test fails, then indicate a misbranch (step 250).
  • [0101] 3) If the CV message arrives at an ER-LSP termination (step 254), and the function type field 136 indicates that is not a traditional CV probe message (step 255), i.e. the message is of an unexpected type, then misbranching from an LDP-LSP into an ER-LSP is occurring (step 250).
  • [0102] 4) If the CV message arrives at an ER-LSP termination and the function type field 136 indicates that is a traditional CV probe message (step 255), then check the TTSI (step 256). If the TTSI is not a match (step 257), then indicate a misbranch (step 250).

[0103] Note that in the above descriptions, the probe message travels from the ingress to the egress LSR. If PHP is enabled, it should be understood that misbranching can then only be detected by the PHP LSR, since the probe message will terminate there.

[0104] The principles of the invention can also be applied to test for proper operation in a load-sharing tunnel environment. Again, the invention can be applied to all types of MPLS tunnels, regardless of the method of label distribution. For purposes of example, the application of the invention to load-sharing LDP-LSP tunnels is now described.

[0105] One method of load sharing used in MPLS networks is known as Equal Cost Multipath (ECMP). As implemented in MPLS, an intermediate LSR when encountering a selection of outgoing paths to the same destination of equal cost may choose to inverse multiplex the traffic destined to the destination over the set of paths. However, flow ordering of the IP payloads must be preserved. This is done in some implementations by incorporating the IP source and destination addresses into the path selection algorithm such that any given source-destination pair resolves to the same path.

[0106] If a misbranching fault occurs on a set of ECMP MPLS LSPs, then the network will appear to misbehave for only an apparently random subset of packets originating from any point upstream of the fault. Thus, one can expend unnecessary time and effort as they cannot diagnose the fault from any arbitrary upstream point in the LSP. So, in accordance with a further aspect of the invention, availability probes are provided that allow the identification of the upstream LSR closest to the point of failure as possible.

[0107] Referring now to FIG. 18, there is shown the process of FIG. 14 as modified to identify the upstream LSR closest to the point of failure as possible. Like steps to xx of FIG. 14 are labeled xxa in FIG. 18. Recall from FIG. 16 that an FEC-CV probe message includes the TTSI field 142, which includes an LSR-ID of the LSR sending the probe. In addition, referring to FIG. 19, the generic MPLS label format is shown. Included is the label field 320, an EXP field 322 that can be used for traffic engineering purposes, and a BS field 324 that indicates as to whether a label is at the bottom of a label stack. Also included is a time-to-live (TTL) field 326, which indicates the number of hops the probe has taken, or in other words indicates the number of LSRs the probe has traversed. In the following, TTL fields are extracted from the label stacked on top of the FEC-CV probe message.

[0108] At step 206a, when the bloom filter for the incoming probe is compared against the egress LSR bloom filter and a mismatch is found, then the TTSI from the FEC-CV probe message is saved, and the TTL is extracted from the next label in the stack and is also saved. (step 394a). For subsequently received FEC-CV probe messages (step 396a), the TTL is compared to the prior saved TTL (step 398a). If the newly received TTL is larger than the prior saved TTL (step 400a), indicating that the newly received FEC-CV probe traveled a shorter distance and is therefore was issued from an LSR that is closer to the misbranching fault than the LSR that issued the prior probe, then the prior saved TTSI is overwritten with the newly received TTSI (step 402a) and the prior saved TTL replaced with the newly received TTL. After a period of time, the saved TTSI will contain the LSR-ID of the LSR closest to the misbranching fault.

[0109] Now that connectivity can be tested, further applications become feasible. For example, tunnel availability can be measured. In accordance with the principles of the invention, tunnel availability can be measured across MPLS tunnels regardless of the type of label assignments being used. The example herein presented applies tunnel availability measurement to LDP-LSP tunnels. As previously described, LDP-LSPs can move between LSRs or between different interfaces on an LSR as routing changes over time. Numerous ingress LSRs can be sending packets to the same FEC on multiple interfaces. Thus, an egress LSR may receive a series of probe messages containing a filter encoding certain FECs on several interfaces. But, each interface will receive the FEC from a unique ingress LSR. When the LSP moves, the egress LSR will no longer receive the probe messages for a particular FEC/ingress LSR combination on one interface, but may start receiving the same probe messages on another interface. If the egress LSR is capable of recognizing that the probe messages are in fact still arriving, then the egress LSR can verify LDP-LSP availability.

[0110] Referring now to FIGS. 20 and 21, there is shown an MPLS network 110 in which the egress LSR is capable of tracking LDP-LSP availability. In FIG. 21A two flow diagrams are shown. Each OAM interface 165a and 165b execute the same algorithm, the steps of which are labeled with like reference numbers followed by ‘a’ and ‘b’ respectively. Availability is evaluated as follows:

• • [0111] 1) Upon receipt of a label request, the egress LSR 130 encodes the set of FECs it is offering for an LSP into a bloom filter 172 (FIG. 21 steps 404, 406). All OAM interfaces on the egress LSR 130 are programmed with the filter value. As herein shown, the OAM interfaces 165a and 165b are programmed with the filter value.
  • [0112] 2) The egress LSR 130 sends an Advertisement message 134 containing the FEC/label bindings to the ingress LSR 112 (step 408).
  • [0113] 3) At some point later, the ingress LSR 112 receives an LDP advertisement of an FEC/LSP binding. The ingress LSR 112 loads the label bindings into its FTN (steps 410, 412).
  • [0114] 4) The ingress LSR 112 encodes the set of FECs it is using for that LSP as a bloom filter 190 (step 414). The ingress may use the set of FECs received in the LDP advertisement, or it may extract the set of FECs from the FTN/NHLFE for the outgoing label.
  • [0115] 5) The ingress LSR 112 sends a probe message 194 containing the bloom filter 190 and its LSR-ID (FIG. 12) to the egress LSR 30 by injecting the probe message 194 into the LSP (step 416). The ingress LSR 112 continues to send the probe messages 94 at predetermined intervals. (steps 416, 418, 420).
  • [0116] 6) The egress LSR 130 receives the probe message 194 at the OAM interface 165a and extracts the filter (step 422). The previously described misbranching test is performed (steps 424, 426). If the misbranching test determines that the network is operating correctly, and the interface 156a has not seen the combination of FEC and LSR-ID before, then the OAM interface 156a notifies the CP 60 of availability of the FEC/ingress LSR combination at the interface 156a (step 428a). The CP 160 starts the availability state machine 430. The egress LSR 130 continues to monitor the receipt of probe messages at the proper intervals (step 432a). If the FEC/LSR-ID combination has previously been recognized, then the interface 156a continues to listen for probe messages containing this combination.
  • [0117] 7) A routing change causes a shift of traffic from the OAM interface 156a to the OAM interface 156b.
  • [0118] 8) The OAM interface 156a stops receiving the probe messages 194. After a predetermined interval during which no probe messages 194 are received, the OAM interface 156a notifies the CP 160 that the ingress LSR is unavailable for the FEC on the interface 156a (step 434a). The availability state machine 430 is so notified.
  • [0119] 9) Meanwhile, the FEC/ingress LSR combination has become available on another interface 156b. The OAM interface 156b begins receiving the probe messages 194 for the FEC/ingress LSR combination (step 436b). After performing the misbranching test and determining that the FECs are a subset of previously programmed FECs (steps 422, 424, 426), the OAM interface 156b notifies the CP 160 that the FECs are available from the ingress LSR on the interface 156b (step 428b). The availability state machine 430 is so notified.
  • [0120] 10) The availability state machine 430 correlates the unavailability of the FEC/LSR-ID combination on the OAM interface 156a to the availability of the same FEC/LSR-ID combination on the OAM interface 156b, and thus can indicate that no outage has occurred and the LSP is continuously available. This information can be used by higher level applications that manage SLAs.

[0121] In accordance with a preferred implementation, the probe messages 194 are FEC-CV messages as shown in FIG. 16, and the ingress and egress LSRs 112 and 130 operate in accordance with ITU-T Y.1711 as modified herein. As a further example, in accordance with ITU-T Y.1711 availability criteria, availability is defined as receiving two consecutive probe messages for an LSP. Also in accordance with Y.1711, CV messages are issued once per second. FIG. 22 shows how the availability state machine 430 would operate if these criteria are used:

• • [0122] An FEC/ingress LSR combination is available on a first OAM interface 156a on the egress LSR 130 availability state machine 430 keeps track of the time ‘t’ that the FEC became available (steps 440, 442).
  • [0123] The FEC/ingress LSR combination switches to a second OAM interface 156b on the egress LSR 30.
  • [0124] The availability state machine 430 notes that the OAM interface 156b declares the FEC/ingress LSR combination available at time ‘t’+2 seconds (steps 444, 446).
  • [0125] The availability state machine 430 notes that the OAM interface 156a declares the FEC/ingress LSR combination unavailable at time ‘t’+3 seconds (step 448).

[0126] In these circumstances, the availability state machine 430 is able to determine that the FEC/ingress LSR combination actually was continuously available, since the FEC/ingress LSR combination became available on a second interface before it became unavailable on the first interface (step 450.)

[0127] Another scenario would be:

• • [0128] An FEC/ingress LSR combination is available on a first OAM interface 156a on the egress LSR 30 (steps 440, 442) at time ‘t’.
  • [0129] Probe messages 194 for the FEC/ingress LSR combination stop appearing at the OAM interface 156a (step 452). The FEC has not appeared on any other interface (step 444).
  • [0130] The availability state machine 430 notes that the OAM interface 156a declares the FEC/ingress LSR combination unavailable at time ‘t’+3 seconds (step 454).
  • [0131] The FEC/ingress LSR combination appears on the OAM interface 156b at time ‘t’+5 seconds.
  • [0132] The availability state machine notes that the OAM interface 56b declares the FEC/ingress LSR combination available at time ‘t’+7 seconds (step 456).

[0133] In this case the availability state machine 430 is able to correlate the notification times to determine that an outage occurred at time ‘t’ and lasted for 5 seconds (step 458). If the FEC/ingress LSR combination never appears on another interface, the availability state machine will timeout (step 460).

[0134] In FIG. 23 there is shown the CV message handling of FIG. 17, modified to allow availability testing. If a CV message arrives at an interface (step 242), and the message is associated with an LDP-LSP (step 244), and the type field indicates that this is an FEC-CV message (step 242), then the misbranching test is performed as previously described (step 252, 253). After the misbranching test, then if availability is being tracked (step 470), then availability status is updated (step 472) in accordance with the mechanisms described in FIGS. 20-22. For non-LDP LSPs, further CV processing to test availability can be performed in known manners (step 474).

[0135] LDP-LSP availability measurement has particular application where the egress LSR has advertised itself as an FEC. This occurs for example in known RFC 2547 IP-VPNs, many layer 2 VPN applications, and applications that eliminate BGP in the core. In all these cases, it is highly advantageous for the egress LSR to be able to track the other edge LSRs that are communicating with it. In addition, the LDP-LSP availability measurement is advantageous in that it is automated and does not require configuration. The egress LSR simply starts tracking ingress LSRs that are communicating with it, and provides an automatic indication when one of the ingress LSRs stops communicating.

[0136] Note that the user network element, for example the ingress LSR, frequently does not know who the originating node is for a FEC advertisement and the egress node may not be aware of the set of ingresses that will use the FEC advertisement. Therefore, by sending the probe messages, the ingress node effectively registers for availability measurement with an unknown originator/egress node and binds it's identity via the bloom filter representation of the FEC in such a way that the egress can verify correct connectivity and configuration. This is contrasted with known availability measurement techniques in which both nodes must be configured with explicit knowledge of each other. Provisioning steps are advantageously reduced when setting up the network. The egress node turns on, advertises FECs, starts receiving probes and performs availability on those it receives. Furthermore, the availability testing mechanism herein described can be used to probe application specifics, whereas many other techniques can only test reachability of the egress node.

[0137] The LDP-LSP availability measurement techniques as herein described are highly advantageous in that probe processing takes place at the egress LSR interfaces, and the central processing functions need only correlate the availability results received from the interfaces. This solution is more scalable than solutions wherein all availability processing is performed by a central processing function. In addition, whereas availability of IP networks with respect to time was heretofore impossible, the availability of IP networks on MPLS can now be measured.

[0138] 2. RFC 2547 BGP VPN

[0139] The principles of the invention are further applicable to RFC 2547 BGP MPLS VPNs, described in [2547bis] Rosen et al., “BGP/MPLS VPNs”, draft-ietf-ppvpn-rfc2547bis-03.txt, October 2002—hereinafter referred to as 2547 BGP VPNs. Referring to FIG. 24, a 2547 BGP VPN defines two roles: the customer, who is the user of provider networking services; and the provider, who is the operator of the network. Three classes of networking platforms support these roles:

[0140] CE: Customer Edge. The CE 500 is the customer networking device directly attached to the provider network 502.

[0141] PE: Provider Edge. The PE 504 is the service aware provider networking device interposed between the CE 500 and the provider's core network element 506s.

[0142] P: Provider network elements. The P's 506 are the service unaware switching/routing devices that simply forward traffic through the provider core and are VPN service unaware.

[0143] The PE 504 instantiates virtual entities known as Virtual Routing and Forwarding engines (VRFs) 508 to communicate with each CE. Each VRF 508 exchanges routing information with a respective CE 500 to obtain a view of the customer network topology behind the CE device. This information is used to build a local routing table associated with the PE-CE interface. The PE 504 uses the Border Gateway Protocol (BGP-4) to flood copies of the VRF routing table to other PEs 504 in the network that communicate to other customer sites within the VPN. The routing table is associated with a per-platform MPLS label that maps to the interface to which the CE 500 is connected. Thus, other VRFs 508 in the VPN have sufficient information to know which packets to forward to the customer site via the originating VRF and respective CE. MPLS is commonly used to forward VPN traffic across the core to remote VPN sites, though other protocols may be used. As shown in FIG. 24, CEs 1, 4, and 7 are members of a VPN 510. The VRF 508 in PE1 builds a routing table via protocol exchange with the CE1 (line labeled ‘1’). It advertises the routing table to all other VRFs 508 in the VPN 510 via BGP (line labeled ‘2’).

[0144] In accordance with the principles of the invention, probes containing knowledge digests can be exchanged between 2547 VRFs in order to verify: synchronization of views of the VRF forwarding tables; correct configuration of the VRFs; and correct functioning of the MPLS connectivity between VRFs (i.e. traffic is not being misdirected).

[0145] Referring now to FIG. 25, the invention operates in a 2547 VPN environment as follows:

[0146] 1) The originating PE 504 constructs two knowledge digests per VRF 508. The current knowledge digest 510 corresponds to the current set of information advertised for the VRF 508. This would include but not be limited to the route distinguisher (RD)—used to create distinct routes to a common IP address; the VRF loopback address, and may include the VRF forwarding table entries. The cumulative knowledge digest 512 corresponds to the cumulative set of information advertised (the difference being additional forwarding table entries). The knowledge digests are loaded into an OAM interface 513.
2) The originating VRF 508 advertises configuration information to the user VRFs via BGP advertisement 520
3) The user PEs 505 construct a user knowledge digest 514 per originating VRF 508 containing the set of information received from BGP. The user knowledge digest 514 is loaded into an OAM interface 516.
4) The user PEs 505 periodically send a copy of their user knowledge digest 514 to the originating PE 505 in a probe message 518 using the LSP associated with the VRF/PE combination. The probe message 518 may be a variation of the FEC-CV message previously described, or may be a message associated with any other protocol. Note that implementation simplicity suggests that use of a common message design for FEC-CV would be the most advantageous instantiation for MPLS.
5) Upon receipt of a probe message containing a digest, the originator executes the process previously described in FIG. 5 to verify:

• • [0147] correct configuration of the user VRF
  • [0148] correct connectivity with the user VRF
  • [0149] end to end synchronization of information with user VRF

[0150] The user and originator knowledge digests are conveniently implemented as bloom filters.

[0151] It should be noted that numerous variations of RFC 2547 exist. For example, VRFs can be identified via unique IPv6 addresses instead of MPLS labels. GRE or other tunneling mechanisms may be used instead of MPLS. The principles of the invention are broadly applicable to the verification of BGP VPNs regardless of the transport layer employed.

[0152] It should also be noted that 2547 BGP VPNs are an overlay on an LDP MPLS network. So, besides inter-VPN leakage, leakage into lower layers may also occur, for example into the LDP or RSVP-TE layers. Thus, it is advantageous to combine the VPN leakage detection described herein with the other leakage detections described herein.

[0153] 3. Pseudo-Wires

[0154] The principles of the invention are further applicable to what are known as “Pseudo wires”, which is the emulation of services (such as ATM, FR, TDM etc.) over tunnels, commonly instantiated as MPLS LSPs. These are frequently implemented as point to point, therefore the basic operation as outlined in FIG. 1 is applicable.

[0155] In all environments in which the principles of the invention may be applied, simple hardware implemented on each interface of an ingress and egress device can be used to compare the bloom filters necessary for configuration testing, so that the central processor need not perform the necessary calculations for all interfaces. The simplicity of the Boolean test allows it to be executed at very high speeds. Thus, the invention herein described provides a highly scalable means of testing configuration, connectivity, availability, and other attributes of tunnels at line-rate speeds.

[0156] In accordance with a further aspect of the invention, in some or all of the environments in which the invention may be applied, it can be useful at times to implement non-repudiation of the probe messages containing the knowledge filters. This provides a way for a user network device to verify that a probe message was actually sent from an originator network device, and vice-versa, and thus is not a spoof or other form of malicious or erroneous message. Accordingly, when hashing a token to produce a bloom filter, each token is concatenated with a secret key shared between the user and originator. Filter comparisons will only match (or appear as a subset) if the keys match. Thus, further security is provided.

[0157] The present invention is not to be limited in scope by the specific embodiments described herein. Indeed, various modifications of the present invention, in addition to those described herein, will be apparent to those of ordinary skill in the art from the foregoing description and accompanying drawings. Further, although the present invention has been described herein in the context of a particular implementation in a particular environment for a particular purpose, those of ordinary skill in the art will recognize that its usefulness is not limited thereto and that the present invention can be beneficially implemented in any number of environments for any number of purposes. As has been described, MPLS FECs may encode various types of forwarding policy information, such as common destination prefixes, or such as common quality or class of service information. However, forwarding policy information may be encoded in other ways. For example, in MPLS networks that implement DiffServ, DiffServ scheduling classes (PSCs) can be verified using the principles of the invention. DiffServ PSCs define groups of packets that receive common quality of service or class of service treatment. PSC information would be encoded in a similar format to the existing FEC information. The PSC information would then be used to populate the bloom filters. One skilled in the art will realize from the teachings herein that the principles of the invention are applicable beyond MPLS networks. Other types of networks associate configuration information with packet switched connections, or simply between any pair of end systems. For example, ATM networks associate configuration information with channel and path connections. The mechanisms of the present invention could be employed to audit, for example, VCC traffic management and quality of service characteristics that are programmed into individual ATM switches. In such networks, it may be advantageous to encode the configuration information associated with a path through the network in a fixed-length bit array such as a bloom filter so that the ATM switches along the path can verify that they are receiving packets in accordance with the proper traffic management or QoS configuration. Similarly MPLS LSPs can be considered to be a specific instantiation of the concept of “tunnels”. The mechanisms in the invention have applicability to “tunnels” in general, such as IPSEC, L2TP, GRE or other such tunneling mechanisms. Furthermore, the invention is not confined to simple one way probing between the user and originator. Loopback or Ping type transactions may also benefit from the use of knowledge digests that permit the user to probe originators and make their own determination as to the existence of a problem. One skilled in the art will also realize from the teachings herein that bloom filters can advantageously be used to verify forwarding policy in any environment where information is forwarded from one device to another based upon forwarding policy rules. The logical functions have been described generally herein, yet the skilled artisan will realize that the functionality of the described logic may in fact be partitioned amongst several different controllers, or may all be included within a single controller. Though most advantageously implemented in hardware when applied in an MPLS environment, the invention may also be implemented in software in MPLS or other environments. All such modifications are intended to fall within the scope of the following appended claims. Accordingly, the claims set forth below should be construed in view of the full breadth and spirit of the present invention as disclosed herein.