WO2009049292A1 - Ip network and performance monitoring using ethernet oam - Google Patents

Ip network and performance monitoring using ethernet oam Download PDF

Info

Publication number
WO2009049292A1
WO2009049292A1 PCT/US2008/079732 US2008079732W WO2009049292A1 WO 2009049292 A1 WO2009049292 A1 WO 2009049292A1 US 2008079732 W US2008079732 W US 2008079732W WO 2009049292 A1 WO2009049292 A1 WO 2009049292A1
Authority
WO
WIPO (PCT)
Prior art keywords
node
network
network layer
command
ethernet
Prior art date
Application number
PCT/US2008/079732
Other languages
French (fr)
Inventor
Dinesh Mohan
Paul Unbehagen
Srikanth Keesara
Original Assignee
Nortel Networks Limited
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Nortel Networks Limited filed Critical Nortel Networks Limited
Priority to JP2010529140A priority Critical patent/JP5306365B2/en
Priority to BRPI0818252A priority patent/BRPI0818252A8/en
Priority to CN2008801204441A priority patent/CN101897151B/en
Priority to EP20080837640 priority patent/EP2208312A1/en
Publication of WO2009049292A1 publication Critical patent/WO2009049292A1/en

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00Arrangements for monitoring or testing data switching networks
    • H04L43/10Active monitoring, e.g. heartbeat, ping or trace-route
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/28Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/04Network management architectures or arrangements
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/12Discovery or management of network topologies
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00Routing or path finding of packets in data switching networks
    • H04L45/02Topology update or discovery
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass

Definitions

  • the present invention relates to link state protocol controlled Ethernet networks, and, more particularly, Operations, Administration, and Maintenance (OAM) in a link state protocol controlled Ethernet network.
  • OAM Operations, Administration, and Maintenance
  • BACKGROUND Data communication networks may include various computers, servers, nodes, routers, switches, bridges, hubs, proxies, and other network devices coupled to and configured to pass data to one another. These devices will be referred to herein as "network elements.” Data is communicated through the data communication network by passing protocol data units, such as Internet Protocol packets, Ethernet Frames, data cells, segments, or other logical associations of bits/bytes of data, between the network elements by utilizing one or more communication links between the network elements. A particular protocol data unit may be handled by multiple network elements and cross multiple communication links as it travels between its source and its destination over the network.
  • protocol data units such as Internet Protocol packets, Ethernet Frames, data cells, segments, or other logical associations of bits/bytes of data
  • the various network elements on the communication network communicate with each other using predefined sets of rules, referred to herein as protocols.
  • Different protocols are used to govern different aspects of the communication, such as how signals should be formed for transmission between network elements, various aspects of what the protocol data units should look like, how protocol data units should be handled or routed through the network by the network elements, and how information such as routing information should be exchanged between the network elements.
  • Ethernet is a well known networking protocol that has been defined by the Institute of Electrical and Electronics Engineers (IEEE) as standard 802.1 in Ethernet network architectures, devices connected to the network compete for the ability to use shared telecommunications paths at any given time. Where multiple bridges or nodes are used to interconnect network segments, multiple potential paths to the same destination often exist. The benefit of this architecture is that it provides path redundancy between bridges and permits capacity to be added to the network in the form of additional links. However to prevent loops from being formed, a spanning tree was generally used to restrict the manner in which traffic was broadcast or flooded on the network.
  • IEEE Institute of Electrical and Electronics Engineers
  • a characteristic of a spanning tree is that there is only one path between any pair of destinations in the network, and therefore it was possible to "learn" the connectivity associated with a given spanning tree by watching where packets came from.
  • the spanning tree itself was restrictive and often led to over-utilization of the links that were on the spanning tree and non-utilization of the links that did't part of the spanning tree.
  • the bridges forming the mesh network exchange link state advertisements to enable each node to have a synchronized view of the network topology. This is achieved via the well understood mechanism of a link state routing system.
  • the bridges in the network have a synchronized view of the network topology, have knowledge of the requisite unicast and multicast connectivity, can compute shortest path connectivity between any pair of bridges in the network, and can individually populate their forwarding information bases (FIBs) according to the computed view of the network.
  • FIBs forwarding information bases
  • the network When all nodes have computed their role in the synchronized view and populated their FIBs, the network will have a loop-free unicast tree to any given bridge from the set of peer bridges (those that require communication to that bridge for whatever reason); and a both congruent and loop-free point-to-multipoint (p2mp) multicast tree from any given bridge to the same set or subset of peer bridges per service instance hosted at the bridge.
  • the result is the path between a given bridge pair is not constrained to transiting the root bridge of a spanning tree and the overall result can better utilize the breadth of connectivity of a mesh. In essence every bridge roots one or more trees which define unicast connectivity to that bridge, and multicast connectivity from that bridge.
  • a link state protocol controlled Ethernet network may associate one VID range with shortest path forwarding, such that unicast and multicast traffic may be forwarded using a VID from that range, and traffic engineering paths may be created across the network on paths other than the shortest path, and forwarded using a second VID range.
  • Ethernet OAM As currently defined in IEEE standard 802. lag "Connectivity Fault Management", defines a set of connectivity fault management protocols for use in Ethernet networks. These include: continuity check, link trace, and loopback protocols.
  • the 802. lag standard has been extended to include performance monitoring metrics and messages. This standard is reflected at ITU-T SG 13, Y.1731 - "Requirements for OAM in Ethernet Networks". But the mechanisms described in these standards are not directly applicable to link state protocol Ethernet networks because of some differences in addressing and VLAN semantics and usage between the standards and the link state protocol Ethernet networks. It is desirable to incorporate OAM features for fault identification, isolation, troubleshooting, and performance monitoring purposes into link state protocol Ethernet networks.
  • a method of network monitoring in a first network layer node operating on a link state protocol controlled Ethernet network includes the steps of receiving by a first node a network layer monitoring command from a network layer monitoring requestor, the monitoring command directed to a second node; resolving by the first node the network layer monitoring command into one or more Ethernet OAM command(s); sending the Ethernet OAM command(s) to the second node; receiving results of the Ethernet OAM command(s) from the second node; and returning by the first node the results of the Ethernet OAM command(s) in the form of a network layer response to the network layer monitoring requestor.
  • the step of resolving the network layer monitoring command into one or more Ethernet OAM command(s) can include the steps of: resolving the network layer address of the second node by consulting a forwarding table to associate the network layer address of the second node with an Ethernet MAC node ID associated with second node on the link state protocol controlled Ethernet network; constructing the one or more Ethernet OAM command(s) with the second node Ethernet MAC node ID address as their destination addresses; and consulting the forwarding table to find the next hop address on the link state protocol controlled Ethernet network for forwarding the OAM command(s) towards the second node on the link state protocol controlled Ethernet network.
  • the network layer may conveniently be IP.
  • Example network layer monitoring commands are is IP PING and IP TRACEROUTE, and exemplary Ethernet OAM commands are LBM and LTM.
  • network layer monitoring commands may be one or more performance monitoring commands
  • Ethernet OAM commands can include
  • Y.1731 commands An IP flow can be adjusted between the first node and the second node in response to the network layer response returned to the network layer monitoring requestor.
  • a program product comprising a computer readable medium having embodied therein a computer program for storing data, the computer program useful for network monitoring in a first network layer node operating on a link state protocol controlled Ethernet network.
  • the computer program includes logic for receiving by the first node a network layer monitoring command from a network layer monitoring requestor, the monitoring command directed to a second node; logic for resolving by the first node the network layer monitoring command into one or more Ethernet OAM command(s); logic for sending the Ethernet OAM command(s) to the second node; logic for receiving results of the Ethernet OAM command(s) from the second node; and logic for returning by the first node the results of the Ethernet OAM command(s) in the form of a network layer response to the network layer monitoring requestor.
  • the logic for resolving the network layer monitoring command into one or more Ethernet OAM command(s) can include logic for resolving the network layer address of the second node by consulting a forwarding table to associate the network layer address of the second node with an Ethernet MAC node ID associated with second node on the link state protocol controlled Ethernet network; logic for constructing the one or more Ethernet OAM command(s) with the second node Ethernet MAC node ID address as their destination addresses; and logic for consulting the forwarding table to find the next hop address on the link state protocol controlled Ethernet network for forwarding the OAM command(s) towards the second node on the link state protocol controlled Ethernet network.
  • the network layer may be IP.
  • Example network layer monitoring commands are is IP PING and IP TRACEROUTE, and exemplary Ethernet OAM commands are LBM and LTM.
  • network layer monitoring commands may be one or more performance monitoring commands
  • Ethernet OAM commands can include Y.1731 commands.
  • An IP flow can be adjusted between the first node and the second node in response to the network layer response returned to the network layer monitoring requestor.
  • Fig. 1 is a functional block diagram of a mesh network that may be used to implement a link state protocol controlled Ethernet network
  • Fig. 2 is a schematic representation of one implementation of a network element 12 configured to be used in a link state protocol controlled Ethernet network;
  • Fig. 3 is a schematic representation of a configured link state protocol controlled Ethernet network wherein ⁇ & link state protocol such as IS-IS has executed its discovery phase t ⁇ interconnect bridges in a loop-free configuration using each bridge's Sys-TD, and then and multicast connectivity creates an FVPN between all nudes that arc members of an TSTD.
  • Fig. 4 is a schematic representation of a configured link state protocol controlled Ethernet network similar to Fig. 3 wherein multiple services are now shown mapped as leaves off the discovery phase trees.
  • Fig. 5 is a block diagram of Ethernet OAM maintenance domains as defined by the 802. lag standard.
  • Fig. 6 is a block diagram of an 802. lag OAM packet.
  • Fig. 7 is a flow diagram of the processing of infrastructure level OAM packets at a node of a link state protocol controlled Ethernet network according to an embodiment of the invention
  • Fig. 8 is a flow diagram of an infrastructure level continuity check process performed at a node of a link state protocol controlled Ethernet network according to an embodiment of the invention.
  • Fig. 9 is a flow diagram of the processing of service level OAM packets at a node of a link state protocol controlled Ethernet network according to an embodiment of the invention.
  • Fig. 10 is a flow diagram of an service level continuity check process performed at a node of a link state protocol controlled Ethernet network according to an embodiment of the invention.
  • Fig. 11 is a flow diagram of MEP creation and distribution by a node in a link state protocol controlled Ethernet network according to an embodiment of the invention
  • Fig. 12 is a flow diagram of MEP reception and forwarding table updates in a node in a link state protocol controlled Ethernet network according to an embodiment of the invention
  • Fig. 13 is a flow diagram of MEP of a process of using MEP lookup to sending an OAM command from node A to node B according to an embodiment of the invention
  • Fig. 14 is a schematic diagram of an IP "Ping" command exectuted between two IP nodes on a link state protocol controlled Ethernet network.
  • Fig. 15 is a flow diagram of the processing of an IP level "Ping" command at a node in a link state protocol controlled Ethernet network according to an embodiment of the invention
  • Fig. 16 is a flow diagram of the processing of an IP level "Traceroute" command at a node in a link state protocol controlled Ethernet network according to an embodiment of the invention
  • Fig. 17 is a block diagram of a network wherein a provider is coupled to a customer premise having an IP phone, and all communications occur over a link state protocol controlled Ethernet network. Performance monitoring of the VOIP network occurs at the IP level using Ethernet OAM commands in accordance with the invention;
  • Fig. 18 is a flow diagram of the processing of an IP level performance monitoring command at a node in a link state protocol controlled Ethernet network according to an embodiment of the invention.
  • Link state protocol controlled Ethernet networks provide the equivalent of Ethernet bridged connectivity, but achieve this via configuration of the network element forwarding information bases (FIBs) rather than by flooding and learning.
  • FIBs network element forwarding information bases
  • Using a link state protocol to control an Ethernet network enables the Ethernet network to be scaled from the I AN space to the WAN or provider netw ⁇ rk space by providing more efficient use of network capacity with loop-free shortest path forwarding.
  • a link state protocol controlled Fthernet network ⁇ lie bridges forming the raesb network exchange link state advertisements to enable each node to have a synchronized view of the network topology, This is achieved via the use of a link state routing system.
  • the bridges in the network have a synchronized view of the network topology, have knowledge of the requisite unieast and multicast connectivity, can compute shortest path connectivity between any pair of bridges in the network, and individually can populate their forwarding information bases (TlBs) according to the computed view of the network.
  • TlBs forwarding information bases
  • the network When all nodes have computed their role in the synchronized view and populated their FlBs, the network will have a loop-free unicast tree to any given bridge from the set of peer bridges; and a both congruent and loop-free point- to - multipoint ⁇ 2mp) multicast tree from any given bridge to the same set of peer bridges, lhe result is the path between a given bridge pair is not constrained to transiting the root bridge of a spanning tree and the overall result can better utilize the breadth of connectivity of a mesh.
  • Link state protocol controlled Ethernet networks generally use symmetrical link metrics such that connectivity between any two bridges follows the same path in both directions, and uses common metrics for unicast and multicast connectivity such that there is congrueney ⁇ f forwarding between packed which are multicast and packets which are unicast.
  • MAC configuration may be used to construct shortest path loop-iree connectivity (for both unicast and multicast purposes) between a set of (slightly modified) bridges in order t ⁇ provide transparent I AN service to the C-MAC f Customer MAC) layer or other layer networks that can use a transparent LAN service.
  • This requires the operation of a link state routing protocol within the network in lieu of the spanning tree protocol for the associated VLANfs) and the piggybacking of MAC information on routing system advertisements.
  • Fig. 1 is a schematic representation of an example of a portion of a link state protocol controlled Htbemet network. From the shared network topology each node calculates optimal shortest paths to other provider backbone bridges (PBBj or nodes in the network using a shortest path algorithm. The outcome of the application of the shortest path algorithm across the network, and the corresponding population of the P IB in the bridges, provides a unique tree through the mesh from each bridge to the member bridges of the network.
  • PBBj provider backbone bridge
  • the MAC addresses associated with a bridge arc global to the link state protocol controlled Ethernet network and are used for destination based forwarding. This means they can be simply flooded in routing system advertisements and, upon local convergence of the routing system, can be instantiated in the local bridge forwarding database i v or FIBS as directed by the routing system. In this way distributed computation of layer 2 connectivity can be applied to Ethernet bridges without requiring a distinct signaling system to associate connectivity with topology.
  • a bridge when a bridge has computed that it is on the shortest path between two given bridge nodes, it simply installs the MAC addresses associated with those bridges in the FIB, the unicast MAC addresses pointing to each ⁇ f the bridges of interest and the multicast MAC address(es) pointing from the bridges of interest.
  • a unicast MAC address may refer to a line card, a virtual switch instance (VSIj or IJTsT port. This may be desirable to simplify de-multiplexing of Hows at a destination bridge.
  • Loop suppression is required in the network to maintain connectivity (albeit in a potentially degraded form) during periods of instability (the period between a topology change, advertisement of the topology change by the routing system to all bridges in the network, and re-convergence on a common view of the new topology and corresponding update of forwarding information).
  • Instability in a distributed system frequently means that, at least temporarily, the overall view of the network will not be synchronized. Where the network elements do not have a synchronized view of the network it is possible for transitory loops to be formed.
  • Pl SB networks may use reverse path forwarding checks to minimize loops as described in greater detail in the parent application.
  • Ri 5 FC checks may be performed by causing a network element such as an Ethernet bridge to check packets by comparing the Source MAC address contained in the packet and the segment on which the packet arrives, with the values that arc configured for that same MAC address as a destination in the forwarding database. If the learned segment for the source MAC address would modify a static entry, or there is no static entry, then the packet is discarded.
  • RPFC check;* may optionally be disabled in particular instances as desired.
  • a link state protocol controlled Ethernet network can support service instances, where any service instance only requires connectivity to a subset of the ports and therefore bridges in the network.
  • An identifier that may be used to identify packets associated with a particular service instance is the extended sen ice ⁇ D field (I-SID) defined in ICEE 802.1 ah.
  • I-SID extended sen ice ⁇ D field
  • ⁇ bridge thai finds itself on the shortest path between two bfidges installs the ur ⁇ cast MAC address! ⁇ s) associated with each bridge, and the multicast MAC addresses lor all X-SIDs common to the two bridges.
  • a given edge bridge will have unicast connectivity to all peer bridges, and multicast connectivity unique to each I-SID identified community of interest This will be in the form o( being a leal on a multipoint-to-point f mp2pi unicast tree to each peer, and being the root of an ( S, G) point-to-multipoint (p.?rnp) multicast tree, where S is the address of the source and G is the multicast group address, to the set of peer nodes for each community of interest.
  • S the address of the source
  • G is the multicast group address
  • a link state protocol controlled Khernct network can support native IP. Accordingly, when a node learns an IP address, it will insert the IP address into its link state advertisement to advertise reachability of the IP address to the other nodes on the network. Each node will add this IP address to its link state database. If a packet arrives at an ingress node, the ingress node will read the IP address, determine which node on the link state protocol controlled Ethernet network is aware of the IP address, and construct a MAC header to forward the packet to the correct node.
  • DA/VID of the MAC header is the nodal MAC of the node that advertised the IP address.
  • Unicast and multicast IP forwarding may be implemented.
  • Fig. 2 is a schematic representation of a possible implementation of a network element 12 configured to be used in a link state protocol controlled Ethernet network.
  • the network element 12 includes a routing system module 80 configured to exchange control messages containing routing and other information with peers 12 in the network 10 regarding the network topology using a link state routing protocol.
  • Information received by the routing system 80 may be stored in a link state database 90 or in another manner. As discussed previously, the exchange of information allows nodes on the network to generate a synchronized view of the network topology, which then allows the routing system module 80 to calculate the shortest paths to other nodes on the network.
  • the shortest paths calculated by the routing system 80 will be programmed into a FIB 82 that is populated with the appropriate entries for directing traffic through the network based upon the calculated shortest paths, multicast trees, traffic engineered path entries, and based on other entries.
  • the routing system 80 may exchange route updates containing network layer reachability information.
  • the network layer addresses known by nodes on the network will be stored in a link state database 90 on the network element 12 to allow ingress nodes to select the correct egress node on the link state protocol controlled Ethernet network when a network layer packet arrives.
  • Knowledge of the network layer addressees may also allow multicast forwarding state to be implemented on the network to allow network layer multicast to be handled by the nodes on the network by causing the nodes to install forwarding state between pairs of nodes interested in the same IP multicast.
  • the network element 12 may also include one or more other modules such as a Reverse Path Forwarding Check (RPFC module 84 that may be used to process incoming frames and perform a lookup in the FIB 82 to determine if the port over which the frame was received coincides with the port identified in the FIB 82 for the particular Source MAC. Where the input port does not coincide with the correct port identified in the FIB, the RPFC module may cause the message to be dropped.
  • RPFC module 84 Reverse Path Forwarding Check
  • a destination lookup 86 module determines from the FIB 82 the port or ports over which the frame should be forwarded. If the FIB doesn't have an entry for the DA/VID, the frame is discarded.
  • a link state protocol controlled Kthcrnct network 300 wherein a link state control protocol such as IS-IS has executed its discovery phase to interconnect bridges 3O.?a-h in a loop-free configuration using each bridge ' s Sys-!D, aka nodal-MAC ⁇ )A .
  • a link state control protocol such as IS-IS has executed its discovery phase to interconnect bridges 3O.?a-h in a loop-free configuration using each bridge ' s Sys-!D, aka nodal-MAC ⁇ )A .
  • Ethernet OAM as currently defined in IEEE standard 802. lag "Connectivity Fault Management", incorporated herein by reference, defines a set of connectivity fault management protocols for use in Ethernet networks. These include: continuity check, link trace, and loopback protocols.
  • the 802. lag standard has been extended to include performance monitoring metrics and messages. This standard is reflected at ITU-T SG 13, Y.1731 - “Requirements for OAM in Ethernet Networks", also herein incorporated by reference. But the mechanisms described in these standards are not directly applicable to link state protocol Ethernet networks.
  • link state protocol Ethernet networks incorporate OAM features for fault identification, isolation, troubleshooting, and performance monitoring purposes.
  • the 802. lag CFM messages include the following: Continuity Check - These are "heartbeat" messages issued periodically by maintenance endpoints. They allow maintenance endpoints to detect loss of service connectivity amongst themselves.
  • Link Trace - These are transmitted by a maintenance endpoint on the request of the administrator to track the path (hop-by -hop) to a destination maintenance endpoint. They allow the transmitting node to discover connectivity data about the path. Link trace is similar in concept to UDP Traceroute.
  • Loopback These are transmitted by a maintenance endpoint on the request of the administrator to verify connectivity to another maintenance point. Loopback indicates whether the destination is reachable or not; it does not allow hop-by -hop discovery of the path. It is similar in concept to ICMP Echo (Ping).
  • Maintenance Domains Ethernet CFM within any given service provider network, relies on a functional model consisting of hierarchical maintenance domains, as shown in Fig. 5. A domain is assigned a unique maintenance level (among eight possible) by the administrator, which is useful for defining the hierarchical relationship of domains. If two domains nest, the outer domain must have a higher maintenance level than the inner domain. Shown in Fig. 5 is a customer domain 402 encompassing a provider domain 404, encompassing 2 operator domains 406.
  • FIG. 5 shows an example where a service provider is using the networks of two operators to provide service.
  • the service provider maintenance level is shown It 322.
  • the maintenance levels for Operator A and Operator B are shown at 324.
  • the customer level allows the customer to test connectivity (using connectivity checks) and isolate issues (using loopback and link trace).
  • the physical layer level defines the narrowest possible maintenance domain: a single link domain.
  • Ethernet OAM is used by IP services over link state protocol controlled Ethernet networks for performance monitoring and control.
  • link state protocol controlled Ethernet can implement CFM messages at the infrastructure level, prior to the setup of the first I- SID.
  • CFM messages are utilized by the link layer in Figs. 3 and 4, and at the link OAM level in Fig. 5.
  • diagnostic 0AM can be helpful to test connectivity between nodes, before deploying services among them.
  • the 802. lag CMF message format is shown in Fig. 6.
  • the nodal MAC address derived from the Sys-ID of destination node is used (e.g. Fig. 7, 400, 402, 404). This node level MAC address is installed in the FIB at the time of link state protocol exchanges.
  • Some CFM messages such as mLBM and CCM, employ unique broadcast destination addresses. These addresses are incompatible with the link state Ethernet protocol, in that RPFC will break and loops will result. So, at the infrastructure level, these messages are not used.
  • a change is made to the manner in which LTM CFM messages are addressed at the infrastructure level.
  • the LTM message employs a well-known group multicast MAC address.
  • the invention provides for a modification to the standard implementation.
  • the LTM message in accordance with the invention employs a unicast destination address for the target destination node (Fig. 7 400, 406, 408).
  • the destination address employed is the nodal MAC address derived from the Sys-ID of the target destination node. Since the link state controlled Ethernet network is pre-configured rather than "flood and learn", the path to the destination is known, so a unicast LTM message can follow the preconfigured path to the target node.
  • link state protocol controlled Ethernet provides an opportunity for double checking connectivity at the infrastructure level.
  • an operator can check the link state database itself to see what connections were generated by the link state protocol. (420, 422) And, an operator can run a linktrace from the node or between pairs of nodes (424) to check to see if the LTM and LTR messages show that the actual paths that exist between nodes match the paths that the link state protocol initially set up as reflected by the FIB (426 - 430).
  • Link state protocol controlled Ethernet can also implement CFM at the service level, after the I-SIDs are set up.
  • Ethernet OAM is designed to operate at the I-SID level, and thus the 802. lag and Y.1733 standards can be used and enhanced to provide service level OAM functionality for link state protocol controlled Ethernet.
  • Service level OAM can be used for discovery purposes to validate the topology of the link state protocol controlled Ethernet network.
  • a "show ISID tree" command can be launched from a node to which the ISID is attached (454).
  • an mLBM command wildcard ping
  • a unicast LTM traceroute
  • the previously described mLTM (wildcard traceroute) command can be launched from the ISID node, which will trace the path of the multicast ISID tree (456).
  • the link state protocol has populated all the nodes in the network with their view of the network topology. So, for example, as shown in Fig. 10 steps 500 - 506, where the link state database is an IS-IS database, one can query the IS-IS database for all the end nodes attached to a given ISID. Then, the service level OAM linktrace described above can be run through the dataplane to see if the dataplane topology is in fact arranged as the control plane indicates it should be.
  • a "show ISID path" command (Fig. 9 462) can verify a path between endpoints. For example, to show a path on an ISID 101 between nodes A and B, one would launch an LTM (traceroute) from node A on the ISID 101 to the node B (464). Again, the LTM DA is the unicast DA of the sys-ID (node B) of the destination node - not the standards based CFM DA.
  • the link state protocol has populated all the nodes in the network with their view of the network topology.
  • the link state database is an IS-IS database
  • the service level OAM linktrace described above can be run through the dataplane to see if the dataplane topology is in fact arranged as the control plane indicates it should be.
  • Service OAM can also be used for connectivity verification and fault detection, between I-SID endpoints and within an I-SID.
  • An OAM message equivalent to a CFM CCM can be issued from end nodes attached to I-SIDs as a connectivity check mechanism (Fig 10, 514). Again, these CCM messages will be addressed based on I-SID mDA (i.e. resolved to Sys-IDs), as opposed to CFM-DA. Further, these CCM messages can be issued at every service level. IP subnet level CCM messages are resolved directly to Sys-IDs, while IP-VPN, VRF, etc, are resolved via I-SIDs.
  • the link state protocol controlled Ethernet network allows automatic generation of MEPs and MIPs.
  • each node in the link state protocol controlled Ethernet network automatically instantiates default MD level 802. lag logic, but may do so using Sys-ID names translated to MAC addresses.
  • each node may hash its Sys-ID to derive its MEP and /or MIP (600), and then populate a TLV with this information (602). The TLV is then transmitted in a Link State PDU (LSP) onto the network (604).
  • LSP Link State PDU
  • a node receives such an LSA (610), it associates the received MEP information in the TLV with the end node from which the LSA was received.
  • the receiving node adds an entry to its FIB to associate the MEP with the nodal MAC of the node the LSA was received from to create a MEP/Sys-ID binding.
  • each node then knows what the MIP and MEP points are for every other node in the network.
  • an operator can execute an infrastructure level OAM command from the perspective of a particular node. For example, as shown in Fig. 13 steps 620 - 626, an operator chooses to perform a continuity check between nodes A and B. So, from node A, the operator executes an Ethernet OAM LBM - i.e. "ping" command.
  • Node A checks its link state database for Node B's MEP - previously populated during link state configuration. Once this is known, an LBM message with a destination address of Node B is built. Node A's FIB indicates that the LBM message should be sent to the next hop MIP (if indeed there is a node between A and B), on its way node B.
  • MAID level as set forth in the 802. lag standard with MD level 0, and are always on.
  • the various service levels can also have always-on MEPs for carrying messages such as CCM. These MEPs are created with MAIDs as a function of the service level identifier I-SID, and the MD level appropriate to the domain. MIPs can be created as always on during link state protocol discovery, with the MD level appropriate to the domain.
  • IP OAM in link state protocol Ethernet Networks can map directly to MAC addresses used in forwarding in link state protocol Ethernet networks, as described in co- pending U.S. Patent Application Serial No. 12/151,684, filed May 5, 2008, which is entitled IP FORWARDING ACROSS A LINK STATE PROTOCOL CONTROLLED ETHERNET NETWORK, incorporated by reference herein.
  • a node in a link state protocol controlled Ethernet network learns an IP address, it will insert the IP address into its link state advertisement to advertise reachability of the IP address to the other nodes on the network. Each node will add this LSP with the IP addresses it is announcing to its link state database.
  • the ingress node will read the IP address, determine which node on the link state protocol controlled Ethernet network is aware of the IP address, and construct a MAC header to forward the packet to the correct node.
  • the DA/VID of the MAC header is the nodal MAC - e.g. this may be the Sys-ID - of the node that advertised the IP address.
  • IP subnets can be mapped congruently to the link state protocol controlled Ethernet network
  • the automatic creation of MEPs and MIPs and enhanced OAM for link state protocol controlled Ethernet enable OAM functions for IP, such as Ping and Traceroute capability based on Ethernet OAM.
  • FIG. 14 the link state protocol controlled Ethernet network is again shown, wherein the MEPs and MIPs have been automatically configured as previously described.
  • the node with Sys-ID San Jose is shown having an IP address 10.20.0.16/24.
  • the node with Sys-ID Denver is shown having an IP address 10.20.8.128/24.
  • an operator at the node San Jose enters an IP command "Ping 10.20.8.128" (720). (Or, there may be an equivalent IP name resolved via DNS or some other means of IP to name conversion.)
  • the node at San Jose had previously received an LSA from Denver announcing that 10.20.8.128 was attached thereto, so San Jose's database resolves the destination IP address to the MAC of Denver (722).
  • the IP ping command is resolved as an Ethernet OAM LBM command with Destination Denver (724).
  • the San Jose node checks its FIB to find the MEP for Denver.
  • An LBM is sent to DA Denver, VID MIP (726).
  • an operator at the node San Jose can enter an IP command "Traceroute 10.20.8.128" (740). (Again, there may be an equivalent IP name resolution.)
  • the node at San Jose had previously received an LSA from Denver announcing that 10.20.8.128 was attached thereto, so San Jose's database resolves the destination IP address to the MAC of Denver (742).
  • the IP traceroute command is resolved as an Ethernet OAM LT command with Destination Denver (744).
  • the San Jose node checks its FIB to find the MEP for Denver.
  • An LTM is sent to DA Denver, VID MIP (746).
  • FLR Frame Loss Ratio
  • FLR is defined as a ratio, expressed as a percentage, of the number of service frames not delivered divided by the total number of service frames during time interval T, where the number of service frames not delivered is the difference between the number of service frames sent to an ingress UNI and the number of service frames received at an egress UNI.
  • FLR Two types of FLR measurement are possible, Dual-ended LM (loss measurement) and Single-ended LM.
  • Dual-ended LM is accomplished by exchanging CCM OAM frames that include appropriate counts of frames transmitted and frames received. These counts do not include OAM frames at the MEPs ME Level. Dual-ended LM enables the proactive measurement of both Near End and Far End FLR at each end of a MEG.
  • Single-ended LM is accomplished by the on-demand exchange of LMM and LMR OAM frames. These frames include appropriate counts of frames transmitted and received.
  • Single- ended LM only provides Near End and Far End FLR at the end that initiated the LM Request.
  • Frame Delay (FD) - FD is specified as round trip delay for a frame, where FD is defined as the time elapsed since the start of transmission of the first bit of the frame by a source node until the reception of the last bit of the loop backed frame by the same source node, when the loopback is performed at the frame's destination node.
  • FDV Frame Delay Variation
  • FIG. 17 there is shown one of many applications wherein Ethernet performance OAM is valuable in an IP application.
  • a provider 800 and a customer premise 802.
  • the customer has an IP phone 804 coupled via an access box 806 to the provider 800 via link state protocol controlled Ethernet network 808.
  • link state protocol controlled Ethernet network 808 Within the provider 800 there may be various bridges 810 coupling the network 808 to a server 812 that serves VOIP services to the access box 806 and thus to the IP phone 804.
  • All the devices in Fig. 18 are IP devices.
  • the IP phone, Server, and bridges, along with other bridges and devices not shown, make up the link state protocol controlled Ethernet network. As such, they each have associated therewith a Sys-ID.
  • a link state protocol such as IS-IS has built a unicast loop free communications path between all elements in the network.
  • the IP phone and server have established IP communications in accordance with the methods described in co- pending U.S. Patent Application Serial No. 12/151,684, filed May 5, 2008, which is entitled IP FORWARDING ACROSS A LINK STATE PROTOCOL CONTROLLED ETHERNET NETWORK, incorporated by reference herein.
  • the IP phone IP subnet is learned by the IP phone node and inserted into its link state advertisement to advertise reachability of the IP subnet to the other nodes on the link state protocol controlled Ethernet network.
  • the IP subnet of the server is learned by the server node and inserted into its link state advertisement to advertise reachability of its IP subnet to the other nodes on the link state protocol controlled
  • Ethernet network If a packet arrives at an ingress node, the ingress node will read the IP address, determine which node on the link state protocol controlled Ethernet network is aware of the IP address, and construct a MAC header to forward the packet to the correct node.
  • the DA/VID of the MAC header is the nodal MAC of the node that advertised the IP address.
  • an IP flow i.e. VOIP
  • An IP flow from the Server to the IP phone will resolve to the MAC of the node to which the server is attached.
  • IP level commands such as "ping” and “traceroute” that can be mapped directly to link state Ethernet commands.
  • IP level performance monitoring functionality is provided based on link state Ethernet OAM commands and feedback.
  • the server 812 monitor delay and jitter for a particular VOIP stream associated with the IP phone 804.
  • this task is enabled by the fact that the VOIP stream is carried over link state protocol controlled Ethernet, and can thus take direct advantage of the OAM functions described herein.
  • an operator can launch a command from the server node 812 "monitor delay, jitter for IP phone over next hour" (820).
  • the IP level OAM command would be resolved at the server 812 to a series of Ethernet level OAM commands between the server 812 and the IP phone 804.
  • the OAM level commands that will be used in this example are FD and FDV.
  • the MAC address for node that has the IP phone attached or the phone itself is resolved by checking the FIB (822). Then the OAM FD and FDV commands can be forwarded from the node attached to the server 812 to the to the node attached to the IP phone 804 the MIP bridge 810 forwarding path specified in the server 812's FIB for the identified time period (826). Performance statistics can thus be collected for the IP flow in a very detailed manner not heretofore available for IP flows on Ethernet networks. The VOIP flow can then be adjusted (828), if needed, based on the resulting feedback from OAM commands.
  • IP performance monitoring can be implemented in accordance with the invention for many IP technologies, including IP telephony, IP TV/video, mobile IP, data center, etc.
  • Link state protocol controlled Ethernet enables IP performance monitoring and control in order to unite many disparate types and levels of IP domains and devices.
  • the ability to utilize Ethernet OAM performance monitoring directly at the IP level in accordance with the invention enables IP traffic control levels for voice, data, and video that will easily lend to detailed LSAs.
  • the present invention may be implemented as one or more computer-readable software programs embodied on or in one or more articles of manufacture.
  • the article of manufacture can be, for example, any one or combination of a floppy disk, a hard disk, hard-disk drive, a CD-ROM, a DVD-ROM, a flash memory card, an EEPROM, an EPROM, a PROM, a RAM, a ROM, or a magnetic tape.
  • any standard or proprietary, programming or interpretive language can be used to produce the computer-readable software programs. Examples of such languages include C, C++, Pascal, JAVA, BASIC, Visual Basic, and Visual C++.
  • the software programs may be stored on or in one or more articles of manufacture as source code, object code, interpretive code, or executable code.

Abstract

Network and performance monitoring in a link state protocol controlled Ethernet network. A first node receives a network layer monitoring command from a network layer monitoring requestor. The monitoring command is directed to a second node. The first node resolves the network layer monitoring command into one or more Ethernet OAM command(s); The first node sends the Ethernet OAM command(s) to the second node, receives the results of the Ethernet OAM command(s) from the second node; and returns the results of the Ethernet OAM command(s) in the form of a network layer response to the network layer monitoring requestor. Furthermore, network layer monitoring commands may be one or more performance monitoring commands, and the Ethernet OAM commands can include Y.1731 commands. An IP flow can be adjusted between the first node and the second node in response to the network layer response returned to the network layer monitoring requestor.

Description

IP NETWORK AND PERFORMANCE MONITORING USING ETHERNET
OAM
Cross-reference to related applications
This application claims priority to the U.S. Provisional Patent Application
Serial No. 60/979,438, filed October 12, 2007, which is entitled PLSB AND IP SHORTCUTS OAM, the content of which is hereby incorporated herein by reference.
This application is related to co-pending U.S. Patent Application Serial No. 12/249,941, filed October 12, 2008, which is entitled IP NETWORK AND PERFORMANCE MONITORING USING ETHERNET OAM; U.S. Patent Application Serial No. 12/249,944, filed October 12, 2008, which is entitled AUTOMATIC MEP PROVISIONING IN A LINK STATE CONTROLLED ETHERNET NETWORK; and U.S. Patent Application Serial No. 12/249,946, filed on October 12, 2008, which is entitled CONTINUITY CHECK MANAGEMENT IN A LINK STATE CONTROLLED ETHERNET NETWORK, co-owned by Nortel Networks Limited, and also to co-pending U.S. Patent Application Serial No. 12/151,684, filed May 5, 2008, which is entitled IP FORWARDING ACROSS A LINK STATE PROTOCOL CONTROLLED ETHERNET NETWORK, also co- owned by Nortel Networks Limited.
TECHNICAL FIELD
The present invention relates to link state protocol controlled Ethernet networks, and, more particularly, Operations, Administration, and Maintenance (OAM) in a link state protocol controlled Ethernet network.
BACKGROUND Data communication networks may include various computers, servers, nodes, routers, switches, bridges, hubs, proxies, and other network devices coupled to and configured to pass data to one another. These devices will be referred to herein as "network elements." Data is communicated through the data communication network by passing protocol data units, such as Internet Protocol packets, Ethernet Frames, data cells, segments, or other logical associations of bits/bytes of data, between the network elements by utilizing one or more communication links between the network elements. A particular protocol data unit may be handled by multiple network elements and cross multiple communication links as it travels between its source and its destination over the network.
The various network elements on the communication network communicate with each other using predefined sets of rules, referred to herein as protocols. Different protocols are used to govern different aspects of the communication, such as how signals should be formed for transmission between network elements, various aspects of what the protocol data units should look like, how protocol data units should be handled or routed through the network by the network elements, and how information such as routing information should be exchanged between the network elements.
Ethernet is a well known networking protocol that has been defined by the Institute of Electrical and Electronics Engineers (IEEE) as standard 802.1 in Ethernet network architectures, devices connected to the network compete for the ability to use shared telecommunications paths at any given time. Where multiple bridges or nodes are used to interconnect network segments, multiple potential paths to the same destination often exist. The benefit of this architecture is that it provides path redundancy between bridges and permits capacity to be added to the network in the form of additional links. However to prevent loops from being formed, a spanning tree was generally used to restrict the manner in which traffic was broadcast or flooded on the network. A characteristic of a spanning tree is that there is only one path between any pair of destinations in the network, and therefore it was possible to "learn" the connectivity associated with a given spanning tree by watching where packets came from. However the spanning tree itself was restrictive and often led to over-utilization of the links that were on the spanning tree and non-utilization of the links that weren't part of the spanning tree.
To overcome some of the limitations inherent in Ethernet networks implementing a spanning tree, a link state protocol controlled Ethernet network was disclosed in application No. 11/537,775, filed October 2, 2006, entitled "Provider
Link State Bridging," the content of which is hereby incorporated herein by reference.
As described in greater detail in that application, rather than utilizing a learned network view at each node by using the Spanning Tree Protocol (STP) algorithm combined with transparent bridging, in a link state protocol controlled Ethernet network the bridges forming the mesh network exchange link state advertisements to enable each node to have a synchronized view of the network topology. This is achieved via the well understood mechanism of a link state routing system. The bridges in the network have a synchronized view of the network topology, have knowledge of the requisite unicast and multicast connectivity, can compute shortest path connectivity between any pair of bridges in the network, and can individually populate their forwarding information bases (FIBs) according to the computed view of the network.
When all nodes have computed their role in the synchronized view and populated their FIBs, the network will have a loop-free unicast tree to any given bridge from the set of peer bridges (those that require communication to that bridge for whatever reason); and a both congruent and loop-free point-to-multipoint (p2mp) multicast tree from any given bridge to the same set or subset of peer bridges per service instance hosted at the bridge. The result is the path between a given bridge pair is not constrained to transiting the root bridge of a spanning tree and the overall result can better utilize the breadth of connectivity of a mesh. In essence every bridge roots one or more trees which define unicast connectivity to that bridge, and multicast connectivity from that bridge.
When customer traffic enters a provider network, the customer MAC address (C-MAC DA) is resolved to a provider MAC address (B-MAC DA), so that the provider may forward traffic on the provider network using the provider MAC address space. Additionally, the network elements on the provider network are configured to forward traffic based on Virtual LAN ID (VID) so that different frames addressed to the same destination address but having different VIDs may be forwarded over different paths through the network. In operation, a link state protocol controlled Ethernet network may associate one VID range with shortest path forwarding, such that unicast and multicast traffic may be forwarded using a VID from that range, and traffic engineering paths may be created across the network on paths other than the shortest path, and forwarded using a second VID range. In order to add true carrier class features to link state protocol controlled Ethernet, certain Operations, Administration, and Management (OAM) features are desirable. Ethernet OAM as currently defined in IEEE standard 802. lag "Connectivity Fault Management", defines a set of connectivity fault management protocols for use in Ethernet networks. These include: continuity check, link trace, and loopback protocols. The 802. lag standard has been extended to include performance monitoring metrics and messages. This standard is reflected at ITU-T SG 13, Y.1731 - "Requirements for OAM in Ethernet Networks". But the mechanisms described in these standards are not directly applicable to link state protocol Ethernet networks because of some differences in addressing and VLAN semantics and usage between the standards and the link state protocol Ethernet networks. It is desirable to incorporate OAM features for fault identification, isolation, troubleshooting, and performance monitoring purposes into link state protocol Ethernet networks.
SUMMARY OF THE INVENTION
In accordance with the invention, there is provided a method of network monitoring in a first network layer node operating on a link state protocol controlled Ethernet network. The method includes the steps of receiving by a first node a network layer monitoring command from a network layer monitoring requestor, the monitoring command directed to a second node; resolving by the first node the network layer monitoring command into one or more Ethernet OAM command(s); sending the Ethernet OAM command(s) to the second node; receiving results of the Ethernet OAM command(s) from the second node; and returning by the first node the results of the Ethernet OAM command(s) in the form of a network layer response to the network layer monitoring requestor. The step of resolving the network layer monitoring command into one or more Ethernet OAM command(s) can include the steps of: resolving the network layer address of the second node by consulting a forwarding table to associate the network layer address of the second node with an Ethernet MAC node ID associated with second node on the link state protocol controlled Ethernet network; constructing the one or more Ethernet OAM command(s) with the second node Ethernet MAC node ID address as their destination addresses; and consulting the forwarding table to find the next hop address on the link state protocol controlled Ethernet network for forwarding the OAM command(s) towards the second node on the link state protocol controlled Ethernet network. The network layer may conveniently be IP. Example network layer monitoring commands are is IP PING and IP TRACEROUTE, and exemplary Ethernet OAM commands are LBM and LTM.
Furthermore, network layer monitoring commands may be one or more performance monitoring commands, and the Ethernet OAM commands can include
Y.1731 commands. An IP flow can be adjusted between the first node and the second node in response to the network layer response returned to the network layer monitoring requestor.
Also in accordance with the invention, there is provided a program product comprising a computer readable medium having embodied therein a computer program for storing data, the computer program useful for network monitoring in a first network layer node operating on a link state protocol controlled Ethernet network. The computer program includes logic for receiving by the first node a network layer monitoring command from a network layer monitoring requestor, the monitoring command directed to a second node; logic for resolving by the first node the network layer monitoring command into one or more Ethernet OAM command(s); logic for sending the Ethernet OAM command(s) to the second node; logic for receiving results of the Ethernet OAM command(s) from the second node; and logic for returning by the first node the results of the Ethernet OAM command(s) in the form of a network layer response to the network layer monitoring requestor.
The logic for resolving the network layer monitoring command into one or more Ethernet OAM command(s) can include logic for resolving the network layer address of the second node by consulting a forwarding table to associate the network layer address of the second node with an Ethernet MAC node ID associated with second node on the link state protocol controlled Ethernet network; logic for constructing the one or more Ethernet OAM command(s) with the second node Ethernet MAC node ID address as their destination addresses; and logic for consulting the forwarding table to find the next hop address on the link state protocol controlled Ethernet network for forwarding the OAM command(s) towards the second node on the link state protocol controlled Ethernet network. The network layer may be IP. Example network layer monitoring commands are is IP PING and IP TRACEROUTE, and exemplary Ethernet OAM commands are LBM and LTM.
Furthermore, network layer monitoring commands may be one or more performance monitoring commands, and the Ethernet OAM commands can include Y.1731 commands. An IP flow can be adjusted between the first node and the second node in response to the network layer response returned to the network layer monitoring requestor.
BRIEF DESCRIPTION OF THE DRAWINGS
Aspects of the present invention are pointed out with particularity in the appended claims. The present invention is illustrated by way of example in the following drawings in which like references indicate similar elements. The following drawings disclose various embodiments of the present invention for purposes of illustration only and are not intended to limit the scope of the invention. For purposes of clarity, not every component may be labeled in every figure. In the figures:
Fig. 1 is a functional block diagram of a mesh network that may be used to implement a link state protocol controlled Ethernet network;
Fig. 2 is a schematic representation of one implementation of a network element 12 configured to be used in a link state protocol controlled Ethernet network;
Fig. 3 is a schematic representation of a configured link state protocol controlled Ethernet network wherein & link state protocol such as IS-IS has executed its discovery phase tυ interconnect bridges in a loop-free configuration using each bridge's Sys-TD, and then and multicast connectivity creates an FVPN between all nudes that arc members of an TSTD. Fig. 4 is a schematic representation of a configured link state protocol controlled Ethernet network similar to Fig. 3 wherein multiple services are now shown mapped as leaves off the discovery phase trees.
Fig. 5 is a block diagram of Ethernet OAM maintenance domains as defined by the 802. lag standard.
Fig. 6 is a block diagram of an 802. lag OAM packet.
Fig. 7 is a flow diagram of the processing of infrastructure level OAM packets at a node of a link state protocol controlled Ethernet network according to an embodiment of the invention;
Fig. 8 is a flow diagram of an infrastructure level continuity check process performed at a node of a link state protocol controlled Ethernet network according to an embodiment of the invention;
Fig. 9 is a flow diagram of the processing of service level OAM packets at a node of a link state protocol controlled Ethernet network according to an embodiment of the invention;
Fig. 10 is a flow diagram of an service level continuity check process performed at a node of a link state protocol controlled Ethernet network according to an embodiment of the invention;
Fig. 11 is a flow diagram of MEP creation and distribution by a node in a link state protocol controlled Ethernet network according to an embodiment of the invention; Fig. 12 is a flow diagram of MEP reception and forwarding table updates in a node in a link state protocol controlled Ethernet network according to an embodiment of the invention;
Fig. 13 is a flow diagram of MEP of a process of using MEP lookup to sending an OAM command from node A to node B according to an embodiment of the invention;
Fig. 14 is a schematic diagram of an IP "Ping" command exectuted between two IP nodes on a link state protocol controlled Ethernet network.
Fig. 15 is a flow diagram of the processing of an IP level "Ping" command at a node in a link state protocol controlled Ethernet network according to an embodiment of the invention;
Fig. 16 is a flow diagram of the processing of an IP level "Traceroute" command at a node in a link state protocol controlled Ethernet network according to an embodiment of the invention;
Fig. 17 is a block diagram of a network wherein a provider is coupled to a customer premise having an IP phone, and all communications occur over a link state protocol controlled Ethernet network. Performance monitoring of the VOIP network occurs at the IP level using Ethernet OAM commands in accordance with the invention;
Fig. 18 is a flow diagram of the processing of an IP level performance monitoring command at a node in a link state protocol controlled Ethernet network according to an embodiment of the invention. Link state protocol controlled Ethernet networks provide the equivalent of Ethernet bridged connectivity, but achieve this via configuration of the network element forwarding information bases (FIBs) rather than by flooding and learning. Using a link state protocol to control an Ethernet network enables the Ethernet network to be scaled from the I AN space to the WAN or provider netwυrk space by providing more efficient use of network capacity with loop-free shortest path forwarding. Rather than utilizing a learned network view at each node by using the Spanning Tree Protocol (STP) algorithm combined with transparent bridging, in a link state protocol controlled Fthernet network {lie bridges forming the raesb network exchange link state advertisements to enable each node to have a synchronized view of the network topology, This is achieved via the use of a link state routing system. The bridges in the network have a synchronized view of the network topology, have knowledge of the requisite unieast and multicast connectivity, can compute shortest path connectivity between any pair of bridges in the network, and individually can populate their forwarding information bases (TlBs) according to the computed view of the network. When all nodes have computed their role in the synchronized view and populated their FlBs, the network will have a loop-free unicast tree to any given bridge from the set of peer bridges; and a both congruent and loop-free point- to - multipoint φ2mp) multicast tree from any given bridge to the same set of peer bridges, lhe result is the path between a given bridge pair is not constrained to transiting the root bridge of a spanning tree and the overall result can better utilize the breadth of connectivity of a mesh.
Link state protocol controlled Ethernet networks generally use symmetrical link metrics such that connectivity between any two bridges follows the same path in both directions, and uses common metrics for unicast and multicast connectivity such that there is congrueney υf forwarding between packed which are multicast and packets which are unicast.
MAC configuration may be used to construct shortest path loop-iree connectivity (for both unicast and multicast purposes) between a set of (slightly modified) bridges in order tυ provide transparent I AN service to the C-MAC f Customer MAC) layer or other layer networks that can use a transparent LAN service. This requires the operation of a link state routing protocol within the network in lieu of the spanning tree protocol for the associated VLANfs) and the piggybacking of MAC information on routing system advertisements. Fig. 1 is a schematic representation of an example of a portion of a link state protocol controlled Htbemet network. From the shared network topology each node calculates optimal shortest paths to other provider backbone bridges (PBBj or nodes in the network using a shortest path algorithm. The outcome of the application of the shortest path algorithm across the network, and the corresponding population of the P IB in the bridges, provides a unique tree through the mesh from each bridge to the member bridges of the network.
The MAC addresses associated with a bridge (unicast and multicast) arc global to the link state protocol controlled Ethernet network and are used for destination based forwarding. This means they can be simply flooded in routing system advertisements and, upon local convergence of the routing system, can be instantiated in the local bridge forwarding database ivor FIBS as directed by the routing system. In this way distributed computation of layer 2 connectivity can be applied to Ethernet bridges without requiring a distinct signaling system to associate connectivity with topology. In its simplest form, when a bridge has computed that it is on the shortest path between two given bridge nodes, it simply installs the MAC addresses associated with those bridges in the FIB, the unicast MAC addresses pointing to each υf the bridges of interest and the multicast MAC address(es) pointing from the bridges of interest.
It tshouid be understood that although a -.ingle unicast MAC address per bridge has been described, nothing precludes the use of finer granularity, and a unicast MAC address may refer to a line card, a virtual switch instance (VSIj or IJTsT port. This may be desirable to simplify de-multiplexing of Hows at a destination bridge.
Loop suppression is required in the network to maintain connectivity (albeit in a potentially degraded form) during periods of instability ( the period between a topology change, advertisement of the topology change by the routing system to all bridges in the network, and re-convergence on a common view of the new topology and corresponding update of forwarding information). Instability in a distributed system frequently means that, at least temporarily, the overall view of the network will not be synchronized. Where the network elements do not have a synchronized view of the network it is possible for transitory loops to be formed. Pl SB networks may use reverse path forwarding checks to minimize loops as described in greater detail in the parent application. Ri5FC checks may be performed by causing a network element such as an Ethernet bridge to check packets by comparing the Source MAC address contained in the packet and the segment on which the packet arrives, with the values that arc configured for that same MAC address as a destination in the forwarding database. If the learned segment for the source MAC address would modify a static entry, or there is no static entry, then the packet is discarded. RPFC check;* may optionally be disabled in particular instances as desired.
A link state protocol controlled Ethernet network can support service instances, where any service instance only requires connectivity to a subset of the ports and therefore bridges in the network. One example of an identifier that may be used to identify packets associated with a particular service instance is the extended sen ice ΪD field (I-SID) defined in ICEE 802.1 ah. Λ bridge thai finds itself on the shortest path between two bfidges installs the urήcast MAC address! εs) associated with each bridge, and the multicast MAC addresses lor all X-SIDs common to the two bridges. The consequence of this is that a given edge bridge will have unicast connectivity to all peer bridges, and multicast connectivity unique to each I-SID identified community of interest This will be in the form o( being a leal on a multipoint-to-point f mp2pi unicast tree to each peer, and being the root of an ( S, G) point-to-multipoint (p.?rnp) multicast tree, where S is the address of the source and G is the multicast group address, to the set of peer nodes for each community of interest. f urther as described in co-persding U.S. Patent Application Serial No. 12/151,684, filed May 5, 2008, which is entitled IP FORWARDING ACROSS A LINK STATE PROTOCOL CONTROLLED ETHERNET NETWORK, herein incorporated by reference in its entirety, a link state protocol controlled Khernct network can support native IP. Accordingly, when a node learns an IP address, it will insert the IP address into its link state advertisement to advertise reachability of the IP address to the other nodes on the network. Each node will add this IP address to its link state database. If a packet arrives at an ingress node, the ingress node will read the IP address, determine which node on the link state protocol controlled Ethernet network is aware of the IP address, and construct a MAC header to forward the packet to the correct node. The DA/VID of the MAC header is the nodal MAC of the node that advertised the IP address. Unicast and multicast IP forwarding may be implemented. Fig. 2 is a schematic representation of a possible implementation of a network element 12 configured to be used in a link state protocol controlled Ethernet network. The network element 12 includes a routing system module 80 configured to exchange control messages containing routing and other information with peers 12 in the network 10 regarding the network topology using a link state routing protocol.
Information received by the routing system 80 may be stored in a link state database 90 or in another manner. As discussed previously, the exchange of information allows nodes on the network to generate a synchronized view of the network topology, which then allows the routing system module 80 to calculate the shortest paths to other nodes on the network. The shortest paths calculated by the routing system 80 will be programmed into a FIB 82 that is populated with the appropriate entries for directing traffic through the network based upon the calculated shortest paths, multicast trees, traffic engineered path entries, and based on other entries.
The routing system 80 may exchange route updates containing network layer reachability information. The network layer addresses known by nodes on the network will be stored in a link state database 90 on the network element 12 to allow ingress nodes to select the correct egress node on the link state protocol controlled Ethernet network when a network layer packet arrives. Knowledge of the network layer addressees may also allow multicast forwarding state to be implemented on the network to allow network layer multicast to be handled by the nodes on the network by causing the nodes to install forwarding state between pairs of nodes interested in the same IP multicast.
The network element 12 may also include one or more other modules such as a Reverse Path Forwarding Check (RPFC module 84 that may be used to process incoming frames and perform a lookup in the FIB 82 to determine if the port over which the frame was received coincides with the port identified in the FIB 82 for the particular Source MAC. Where the input port does not coincide with the correct port identified in the FIB, the RPFC module may cause the message to be dropped.
If the frame passes the RPFC 84 module, a destination lookup 86 module determines from the FIB 82 the port or ports over which the frame should be forwarded. If the FIB doesn't have an entry for the DA/VID, the frame is discarded.
It should also be understood that the modules described are for illustrative purposes only and may be implemented by combining or distributing functions among the modules of a node as would be understood by a person of skill in the art. Referring to Mg. 3, there is shown a link state protocol controlled Kthcrnct network 300 wherein a link state control protocol such as IS-IS has executed its discovery phase to interconnect bridges 3O.?a-h in a loop-free configuration using each bridge's Sys-!D, aka nodal-MAC ¥)A . Once an ISlD is configured, for example !S]D 23, an IS-IS update is sent out, and multicast connectivity creates the hVPfS between all nodes that are members of ISII) .^3, A different set of IS-IS updates is sent out to create multicast connectivity tor ISID 10, Once the ISIDs are created, all forwarding is then completed over the paths that were created using the Sys-lDs during link state discovery. Referring further to Fig, 4, every service is a leat of this base topology. IP subnets 30o map directly to Sys-IDs, as described in co-pending U.S. Patent Application Serial No. 12/151,684, filed May 5, 2008, which is entitled IP FORWARDING ACROSS A LINK STATE PROTOCOL CONTROLLED ETHERNET NETWORK, herein incorporated by reference in its entirety. YRFt, 308 map -via ISIDh, as described in co-pending CS. Patent Application Serial Nu. 12, 215.350, tiled June 26, 2008, which is entitled IMPLEMENTATION OF VPNs OVER LINK STATE PROTOCOL CONTROLLED ETHERNET NETWORK, herein incorporated by reference in its entirety.
Ethernet OAM as currently defined in IEEE standard 802. lag "Connectivity Fault Management", incorporated herein by reference, defines a set of connectivity fault management protocols for use in Ethernet networks. These include: continuity check, link trace, and loopback protocols. The 802. lag standard has been extended to include performance monitoring metrics and messages. This standard is reflected at ITU-T SG 13, Y.1731 - "Requirements for OAM in Ethernet Networks", also herein incorporated by reference. But the mechanisms described in these standards are not directly applicable to link state protocol Ethernet networks. In accordance with the invention, link state protocol Ethernet networks incorporate OAM features for fault identification, isolation, troubleshooting, and performance monitoring purposes.
The 802. lag CFM messages include the following: Continuity Check - These are "heartbeat" messages issued periodically by maintenance endpoints. They allow maintenance endpoints to detect loss of service connectivity amongst themselves.
Link Trace - These are transmitted by a maintenance endpoint on the request of the administrator to track the path (hop-by -hop) to a destination maintenance endpoint. They allow the transmitting node to discover connectivity data about the path. Link trace is similar in concept to UDP Traceroute.
Loopback - These are transmitted by a maintenance endpoint on the request of the administrator to verify connectivity to another maintenance point. Loopback indicates whether the destination is reachable or not; it does not allow hop-by -hop discovery of the path. It is similar in concept to ICMP Echo (Ping). Maintenance Domains Ethernet CFM, within any given service provider network, relies on a functional model consisting of hierarchical maintenance domains, as shown in Fig. 5. A domain is assigned a unique maintenance level (among eight possible) by the administrator, which is useful for defining the hierarchical relationship of domains. If two domains nest, the outer domain must have a higher maintenance level than the inner domain. Shown in Fig. 5 is a customer domain 402 encompassing a provider domain 404, encompassing 2 operator domains 406. Maintenance endpoints (squares) reside at the edge of a maintenance domain, whereas maintenance intermediate points (circles) are internal to the domain. Hence, an intermediate point will forward CFM packets (unless it is a loopback or link trace destined for that intermediate point), while endpoints do not forward CFM packets because they must keep them within the domain. The only exception to this is when an endpoint is also acting as an intermediate point for a higher-level domain, in which case it will forward CFM packets as long as they are part of the higher-level domain. Fig. 5 shows an example where a service provider is using the networks of two operators to provide service. The service provider maintenance level is shown It 322. The maintenance levels for Operator A and Operator B are shown at 324. Two special-case maintenance levels are the customer level (320) and the physical layer level (326). The customer level allows the customer to test connectivity (using connectivity checks) and isolate issues (using loopback and link trace). The physical layer level, on the other hand, defines the narrowest possible maintenance domain: a single link domain.
In accordance with first aspects of the invention, modifications are made to Ethernet OAM standards in order to adjust for differences between classical spanning tree based Ethernet and link state protocol controlled Ethernet. In accordance with second aspects of the invention, novel service level OAM features take advantage of link state protocol controlled Ethernet. In accordance with third aspects of the invention, Ethernet OAM is used by IP services over link state protocol controlled Ethernet networks for performance monitoring and control. Infrastructure OAM
In accordance with the invention, link state protocol controlled Ethernet can implement CFM messages at the infrastructure level, prior to the setup of the first I- SID. Thus CFM messages are utilized by the link layer in Figs. 3 and 4, and at the link OAM level in Fig. 5. At this point, diagnostic 0AM can be helpful to test connectivity between nodes, before deploying services among them.
The 802. lag CMF message format is shown in Fig. 6. Some CFM messages in accordance with the 802. lag standard, i.e. LBM messages, employ unicast destination addresses. It is useful to be able to use these CFM messages for diagnostic purposes to check the topology of the link state controlled Ethernet network. In order to do so, proper destination addresses of the nodes in the link state topology are needed. Thus, in accordance with the invention and as shown in Fig. 6, For CFM messages that employ unicast destination addresses, i.e. LBM an LBR messages, the nodal MAC address derived from the Sys-ID of destination node is used (e.g. Fig. 7, 400, 402, 404). This node level MAC address is installed in the FIB at the time of link state protocol exchanges.
Some CFM messages, such as mLBM and CCM, employ unique broadcast destination addresses. These addresses are incompatible with the link state Ethernet protocol, in that RPFC will break and loops will result. So, at the infrastructure level, these messages are not used. In further accordance with the invention, a change is made to the manner in which LTM CFM messages are addressed at the infrastructure level. According to the standard, the LTM message employs a well-known group multicast MAC address. However, in a link state controlled Ethernet network, there are no multicast entries in any node FIB until the 1st I-SID has been established. So, a standard LTM message received by a link state controlled Ethernet network node at this stage would be dropped. Therefore, the invention provides for a modification to the standard implementation. The LTM message in accordance with the invention employs a unicast destination address for the target destination node (Fig. 7 400, 406, 408). Again, the destination address employed is the nodal MAC address derived from the Sys-ID of the target destination node. Since the link state controlled Ethernet network is pre-configured rather than "flood and learn", the path to the destination is known, so a unicast LTM message can follow the preconfigured path to the target node.
Referring now to Fig. 8, the use of link state protocol controlled Ethernet with OAM provides an opportunity for double checking connectivity at the infrastructure level. For a given node or nodes in the link state controlled Ethernet network, an operator can check the link state database itself to see what connections were generated by the link state protocol. (420, 422) And, an operator can run a linktrace from the node or between pairs of nodes (424) to check to see if the LTM and LTR messages show that the actual paths that exist between nodes match the paths that the link state protocol initially set up as reflected by the FIB (426 - 430).
Service level OAM
Link state protocol controlled Ethernet can also implement CFM at the service level, after the I-SIDs are set up. Ethernet OAM is designed to operate at the I-SID level, and thus the 802. lag and Y.1733 standards can be used and enhanced to provide service level OAM functionality for link state protocol controlled Ethernet. mLT
In a classic flood and reverse path learning Ethernet network, all I-SIDs follow the same multicast distribution path rooted at a single multicast source address. But in the link state protocol controlled Ethernet network, each service instance, i.e. ISID, roots a multicast distribution path. So, if one wants to troubleshoot a service instance path in a link state protocol controlled Ethernet network, then instead of using a unicast LTM or a standards based multicast LTM that is incongruent with the ISID path, it makes sense to use a new alternative. In accordance with one aspect of the invention, a new OAM link trace message is therefore provided at the service level. This link trace message, instead of using a multicast standard Ethernet DA of Fig. 6, uses as its DA an I-SID multicast address (Fig. 9 456). By using the ISID multicast DA, the linktrace will follow the optimized multicast path rooted from the node for which the trace is launched, rather than from the classic Ethernet multicast tree.
Discovery
Service level OAM can be used for discovery purposes to validate the topology of the link state protocol controlled Ethernet network. For example, referring to Fig. 9, a "show ISID tree" command can be launched from a node to which the ISID is attached (454). According to one option, an mLBM command (wildcard ping) can be launched from the ISID node, using the ISID mDA - not the CFM mDA of the 802. lag standard (458). Or, for each ISID end-point, a unicast LTM (traceroute) can be launched within the ISID (460). According to an alternate option, the previously described mLTM (wildcard traceroute) command can be launched from the ISID node, which will trace the path of the multicast ISID tree (456).
Note that the link state protocol has populated all the nodes in the network with their view of the network topology. So, for example, as shown in Fig. 10 steps 500 - 506, where the link state database is an IS-IS database, one can query the IS-IS database for all the end nodes attached to a given ISID. Then, the service level OAM linktrace described above can be run through the dataplane to see if the dataplane topology is in fact arranged as the control plane indicates it should be.
Discovery can also be used to validate paths in the network. A "show ISID path" command (Fig. 9 462) can verify a path between endpoints. For example, to show a path on an ISID 101 between nodes A and B, one would launch an LTM (traceroute) from node A on the ISID 101 to the node B (464). Again, the LTM DA is the unicast DA of the sys-ID (node B) of the destination node - not the standards based CFM DA. Connectivity
Again, the link state protocol has populated all the nodes in the network with their view of the network topology. So, for example, as shown in Fig. 10 steps 508 - 512, where the link state database is an IS-IS database, one can query from any node in the IS-IS database for the I-SID path between node A and node B. Or, one can query from and endnode on I-SID for the path to the other endnode - for example, query from endnode A to show the path to endnode B. Then, the service level OAM linktrace described above can be run through the dataplane to see if the dataplane topology is in fact arranged as the control plane indicates it should be.
Service OAM can also be used for connectivity verification and fault detection, between I-SID endpoints and within an I-SID. An OAM message equivalent to a CFM CCM can be issued from end nodes attached to I-SIDs as a connectivity check mechanism (Fig 10, 514). Again, these CCM messages will be addressed based on I-SID mDA (i.e. resolved to Sys-IDs), as opposed to CFM-DA. Further, these CCM messages can be issued at every service level. IP subnet level CCM messages are resolved directly to Sys-IDs, while IP-VPN, VRF, etc, are resolved via I-SIDs.
MEP/MIP Automatic Generation
In accordance with aspects of the invention, the link state protocol controlled Ethernet network allows automatic generation of MEPs and MIPs. As part of link trace protocol discovery, each node in the link state protocol controlled Ethernet network automatically instantiates default MD level 802. lag logic, but may do so using Sys-ID names translated to MAC addresses. In accordance with the invention, as shown in Fig. 11, at the infrastructure level, each node may hash its Sys-ID to derive its MEP and /or MIP (600), and then populate a TLV with this information (602). The TLV is then transmitted in a Link State PDU (LSP) onto the network (604). In Fig. 12, it shows when a node receives such an LSA (610), it associates the received MEP information in the TLV with the end node from which the LSA was received. The receiving node adds an entry to its FIB to associate the MEP with the nodal MAC of the node the LSA was received from to create a MEP/Sys-ID binding. Thus each node then knows what the MIP and MEP points are for every other node in the network.
Thus, an operator can execute an infrastructure level OAM command from the perspective of a particular node. For example, as shown in Fig. 13 steps 620 - 626, an operator chooses to perform a continuity check between nodes A and B. So, from node A, the operator executes an Ethernet OAM LBM - i.e. "ping" command. In accordance with the invention, Node A checks its link state database for Node B's MEP - previously populated during link state configuration. Once this is known, an LBM message with a destination address of Node B is built. Node A's FIB indicates that the LBM message should be sent to the next hop MIP (if indeed there is a node between A and B), on its way node B.
As was shown in Fig. 5, different maintenance domains are associated with different MEP and MIP MD levels. Thus, at the service level, different sets of MEPs and MIPs are specified. The link state protocol controlled Ethernet network allows for dynamic auto configuration of MEPs and MIPs as needed at various service levels. At the infrastructure level, port MEPs for monitoring links are instantiated at a
"default" MAID level as set forth in the 802. lag standard with MD level 0, and are always on. The various service levels can also have always-on MEPs for carrying messages such as CCM. These MEPs are created with MAIDs as a function of the service level identifier I-SID, and the MD level appropriate to the domain. MIPs can be created as always on during link state protocol discovery, with the MD level appropriate to the domain.
IP OAM in link state protocol Ethernet Networks As previously described, IP addresses can map directly to MAC addresses used in forwarding in link state protocol Ethernet networks, as described in co- pending U.S. Patent Application Serial No. 12/151,684, filed May 5, 2008, which is entitled IP FORWARDING ACROSS A LINK STATE PROTOCOL CONTROLLED ETHERNET NETWORK, incorporated by reference herein. As explained therein, when a node in a link state protocol controlled Ethernet network learns an IP address, it will insert the IP address into its link state advertisement to advertise reachability of the IP address to the other nodes on the network. Each node will add this LSP with the IP addresses it is announcing to its link state database. If a packet arrives at an ingress node, the ingress node will read the IP address, determine which node on the link state protocol controlled Ethernet network is aware of the IP address, and construct a MAC header to forward the packet to the correct node. The DA/VID of the MAC header is the nodal MAC - e.g. this may be the Sys-ID - of the node that advertised the IP address.
Since IP subnets can be mapped congruently to the link state protocol controlled Ethernet network, the automatic creation of MEPs and MIPs and enhanced OAM for link state protocol controlled Ethernet enable OAM functions for IP, such as Ping and Traceroute capability based on Ethernet OAM.
For example, referring to Fig. 14 the link state protocol controlled Ethernet network is again shown, wherein the MEPs and MIPs have been automatically configured as previously described. The node with Sys-ID San Jose is shown having an IP address 10.20.0.16/24. The node with Sys-ID Denver is shown having an IP address 10.20.8.128/24. Referring to Fig. 15, an operator at the node San Jose enters an IP command "Ping 10.20.8.128" (720). (Or, there may be an equivalent IP name resolved via DNS or some other means of IP to name conversion.) The node at San Jose had previously received an LSA from Denver announcing that 10.20.8.128 was attached thereto, so San Jose's database resolves the destination IP address to the MAC of Denver (722). The IP ping command is resolved as an Ethernet OAM LBM command with Destination Denver (724). The San Jose node checks its FIB to find the MEP for Denver. An LBM is sent to DA Denver, VID MIP (726). Assuming infrastructure continuity between Denver and San Jose, the LBR is returned to San Jose. Similarly, referring to Fig. 16, an operator at the node San Jose can enter an IP command "Traceroute 10.20.8.128" (740). (Again, there may be an equivalent IP name resolution.) The node at San Jose had previously received an LSA from Denver announcing that 10.20.8.128 was attached thereto, so San Jose's database resolves the destination IP address to the MAC of Denver (742). The IP traceroute command is resolved as an Ethernet OAM LT command with Destination Denver (744). The San Jose node checks its FIB to find the MEP for Denver. An LTM is sent to DA Denver, VID MIP (746).
Performance Monitoring The 802. lag standard has been extended to include performance monitoring metrics and messages. This standard is reflected at ITU-T SG 13, Y.1731 - Requirements for OAM in Ethernet Networks, herein incorporated by reference. The following performance parameters are measured by appropriate OAM messages: 1) Frame Loss Ratio (FLR) - FLR is defined as a ratio, expressed as a percentage, of the number of service frames not delivered divided by the total number of service frames during time interval T, where the number of service frames not delivered is the difference between the number of service frames sent to an ingress UNI and the number of service frames received at an egress UNI. Two types of FLR measurement are possible, Dual-ended LM (loss measurement) and Single-ended LM. Dual-ended LM is accomplished by exchanging CCM OAM frames that include appropriate counts of frames transmitted and frames received. These counts do not include OAM frames at the MEPs ME Level. Dual-ended LM enables the proactive measurement of both Near End and Far End FLR at each end of a MEG. Single-ended LM is accomplished by the on-demand exchange of LMM and LMR OAM frames. These frames include appropriate counts of frames transmitted and received. Single- ended LM only provides Near End and Far End FLR at the end that initiated the LM Request.
2) Frame Delay (FD) - FD is specified as round trip delay for a frame, where FD is defined as the time elapsed since the start of transmission of the first bit of the frame by a source node until the reception of the last bit of the loop backed frame by the same source node, when the loopback is performed at the frame's destination node.
3) Frame Delay Variation (FDV) - FDV is a measure of the variations in the FD between a pair of service frames, where the service frames belong to the same CoS (class of service) instance on a point-to-point ethernet connection.
Note again that IP subnets in many cases map congruently to the link state protocol controlled Ethernet network. Now, the automatic creation of MEPs and MIPs and enhanced OAM and performance monitoring for link state protocol controlled Ethernet enable fine grained, detailed "SONET-style" OAM for IP over Ethernet that has heretofore not been available.
Referring to Fig. 17, there is shown one of many applications wherein Ethernet performance OAM is valuable in an IP application. Shown is a provider 800 and a customer premise 802. The customer has an IP phone 804 coupled via an access box 806 to the provider 800 via link state protocol controlled Ethernet network 808. Within the provider 800 there may be various bridges 810 coupling the network 808 to a server 812 that serves VOIP services to the access box 806 and thus to the IP phone 804. All the devices in Fig. 18 are IP devices. The IP phone, Server, and bridges, along with other bridges and devices not shown, make up the link state protocol controlled Ethernet network. As such, they each have associated therewith a Sys-ID. A link state protocol such as IS-IS has built a unicast loop free communications path between all elements in the network. The IP phone and server have established IP communications in accordance with the methods described in co- pending U.S. Patent Application Serial No. 12/151,684, filed May 5, 2008, which is entitled IP FORWARDING ACROSS A LINK STATE PROTOCOL CONTROLLED ETHERNET NETWORK, incorporated by reference herein. In short, the IP phone IP subnet is learned by the IP phone node and inserted into its link state advertisement to advertise reachability of the IP subnet to the other nodes on the link state protocol controlled Ethernet network. Likewise, the IP subnet of the server is learned by the server node and inserted into its link state advertisement to advertise reachability of its IP subnet to the other nodes on the link state protocol controlled
Ethernet network. If a packet arrives at an ingress node, the ingress node will read the IP address, determine which node on the link state protocol controlled Ethernet network is aware of the IP address, and construct a MAC header to forward the packet to the correct node. The DA/VID of the MAC header is the nodal MAC of the node that advertised the IP address. In this case, an IP flow (i.e. VOIP) from the IP phone to the server will resolve to the MAC of the node to which the IP phone is attached. An IP flow from the Server to the IP phone will resolve to the MAC of the node to which the server is attached.
As was described previously with regard to CFM OAM an operator can perform IP level commands such as "ping" and "traceroute" that can be mapped directly to link state Ethernet commands. In further accordance with the invention, IP level performance monitoring functionality is provided based on link state Ethernet OAM commands and feedback.
For example, referring to Fig. 18, it is desirable for the server 812 to monitor delay and jitter for a particular VOIP stream associated with the IP phone 804. In accordance with the invention, this task is enabled by the fact that the VOIP stream is carried over link state protocol controlled Ethernet, and can thus take direct advantage of the OAM functions described herein. For instance, an operator can launch a command from the server node 812 "monitor delay, jitter for IP phone over next hour" (820). The IP level OAM command would be resolved at the server 812 to a series of Ethernet level OAM commands between the server 812 and the IP phone 804. The OAM level commands that will be used in this example are FD and FDV. First, the MAC address for node that has the IP phone attached or the phone itself is resolved by checking the FIB (822). Then the OAM FD and FDV commands can be forwarded from the node attached to the server 812 to the to the node attached to the IP phone 804 the MIP bridge 810 forwarding path specified in the server 812's FIB for the identified time period (826). Performance statistics can thus be collected for the IP flow in a very detailed manner not heretofore available for IP flows on Ethernet networks. The VOIP flow can then be adjusted (828), if needed, based on the resulting feedback from OAM commands.
IP performance monitoring can be implemented in accordance with the invention for many IP technologies, including IP telephony, IP TV/video, mobile IP, data center, etc. Link state protocol controlled Ethernet enables IP performance monitoring and control in order to unite many disparate types and levels of IP domains and devices. The ability to utilize Ethernet OAM performance monitoring directly at the IP level in accordance with the invention enables IP traffic control levels for voice, data, and video that will easily lend to detailed LSAs.
The present invention may be implemented as one or more computer-readable software programs embodied on or in one or more articles of manufacture. The article of manufacture can be, for example, any one or combination of a floppy disk, a hard disk, hard-disk drive, a CD-ROM, a DVD-ROM, a flash memory card, an EEPROM, an EPROM, a PROM, a RAM, a ROM, or a magnetic tape. In general, any standard or proprietary, programming or interpretive language can be used to produce the computer-readable software programs. Examples of such languages include C, C++, Pascal, JAVA, BASIC, Visual Basic, and Visual C++. The software programs may be stored on or in one or more articles of manufacture as source code, object code, interpretive code, or executable code.
Although the invention has been shown and described with reference to specific preferred embodiments, it should be understood by those skilled in the art that various changes in form and detail may be made therein without departing from the spirit and scope of the invention as defined by the following claims. We claim:

Claims

1. A method of network monitoring in a first network layer node operating on a link state protocol controlled Ethernet network, the method comprising the steps of:
receiving by the first node a network layer monitoring command from a network layer monitoring requestor, the monitoring command directed to a second node; resolving by the first node the network layer monitoring command into one or more Ethernet OAM command(s); sending the Ethernet OAM command(s) to the second node; receiving results of the Ethernet OAM command(s) from the second node; and returning by the first node the results of the Ethernet OAM command(s) in the form of a network layer response to the network layer monitoring requestor.
2. The method of claim 1 wherein the step of resolving by the first node the network layer monitoring command into one or more Ethernet OAM command(s) comprises the steps of: resolving the network layer address of the second node by consulting a forwarding table to associate the network layer address of the second node with an Ethernet MAC node ID associated with second node on the link state protocol controlled Ethernet network; constructing the one or more Ethernet OAM command(s) with the second node Ethernet MAC node ID address as their destination addresses; consulting the forwarding table to find the next hop address on the link state protocol controlled Ethernet network for forwarding the OAM command(s) towards the second node on the link state protocol controlled Ethernet network.
3. The method of claim 2 wherein the network layer is IP.
4. The method of claim 3 wherein the network layer monitoring command is IP PING, and wherein the Ethernet OAM command is LBM.
5. The method of claim 3 wherein the network layer monitoring command is IP TRACEROUTE, and wherein the Ethernet OAM command is LTM.
6. The method of claim 3 wherein the network layer monitoring command is one or more performance monitoring commands, and wherein the Ethernet OAM commands include Y.1731 commands.
7. The method of claim 4 further comprising the step of adjusting by the first node an IP flow between the first node and the second node in response to the network layer response returned to the network layer monitoring requestor.
8. A program product comprising a computer readable medium having embodied therein a computer program for storing data, the computer program useful for network monitoring in a first network layer node operating on a link state protocol controlled Ethernet network, the computer program comprising: logic for receiving by the first node a network layer monitoring command from a network layer monitoring requestor, the monitoring command directed to a second node; logic for resolving by the first node the network layer monitoring command into one or more Ethernet OAM command(s); logic for sending the Ethernet OAM command(s) to the second node; logic for receiving results of the Ethernet OAM command(s) from the second node; and logic for returning by the first node the results of the Ethernet OAM command(s) in the form of a network layer response to the network layer monitoring requestor.
9. The computer program of claim 8 wherein the logic for resolving by the first node the network layer monitoring command into one or more Ethernet OAM command(s) comprises: logic for resolving the network layer address of the second node by consulting a forwarding table to associate the network layer address of the second node with an Ethernet MAC node ID associated with second node on the link state protocol controlled Ethernet network; logic for constructing the one or more Ethernet OAM command(s) with the second node Ethernet MAC node ID address as their destination addresses; logic for consulting the forwarding table to find the next hop address on the link state protocol controlled Ethernet network for forwarding the OAM command(s) towards the second node on the link state protocol controlled Ethernet network.
10. The computer program of claim 9 wherein the network layer is IP.
11. The computer program of claim 10 wherein the network layer monitoring command is IP PING, and wherein the Ethernet OAM command is LBM.
12. The computer program of claim 10 wherein the network layer monitoring command is IP TRACEROUTE, and wherein the Ethernet OAM command is LTM.
13. The computer program of claim 10 wherein the network layer monitoring command is one or more performance monitoring commands, and wherein the Ethernet OAM commands include Y.1731 commands.
14. The method of claim 11 further comprising the step of adjusting by the first node an IP flow between the first node and the second node in response to the network layer response returned to the network layer monitoring requestor.
PCT/US2008/079732 2007-10-12 2008-10-13 Ip network and performance monitoring using ethernet oam WO2009049292A1 (en)

Priority Applications (4)

Application Number Priority Date Filing Date Title
JP2010529140A JP5306365B2 (en) 2007-10-12 2008-10-13 Operation status monitoring using IP network and Ethernet OAM
BRPI0818252A BRPI0818252A8 (en) 2007-10-12 2008-10-13 PERFORMANCE AND IP NETWORK MONITORING USING ETHERNET OAM
CN2008801204441A CN101897151B (en) 2007-10-12 2008-10-13 IP network and performance monitoring using Ethernet OAM
EP20080837640 EP2208312A1 (en) 2007-10-12 2008-10-13 Ip network and performance monitoring using ethernet oam

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US97943807P 2007-10-12 2007-10-12
US60/979,438 2007-10-12

Publications (1)

Publication Number Publication Date
WO2009049292A1 true WO2009049292A1 (en) 2009-04-16

Family

ID=40549624

Family Applications (3)

Application Number Title Priority Date Filing Date
PCT/US2008/079732 WO2009049292A1 (en) 2007-10-12 2008-10-13 Ip network and performance monitoring using ethernet oam
PCT/US2008/079825 WO2009049311A1 (en) 2007-10-12 2008-10-14 Continuity check management in a link state controlled ethernet network
PCT/US2008/079803 WO2009049307A1 (en) 2007-10-12 2008-10-14 Automatic mep provisioning in a link state controlled ethernet network

Family Applications After (2)

Application Number Title Priority Date Filing Date
PCT/US2008/079825 WO2009049311A1 (en) 2007-10-12 2008-10-14 Continuity check management in a link state controlled ethernet network
PCT/US2008/079803 WO2009049307A1 (en) 2007-10-12 2008-10-14 Automatic mep provisioning in a link state controlled ethernet network

Country Status (7)

Country Link
US (5) US7996559B2 (en)
EP (3) EP2208312A1 (en)
JP (5) JP5306365B2 (en)
KR (6) KR20100096086A (en)
CN (4) CN101897151B (en)
BR (3) BRPI0818252A8 (en)
WO (3) WO2009049292A1 (en)

Cited By (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2010139281A1 (en) * 2009-06-04 2010-12-09 中兴通讯股份有限公司 Method and apparatus for detecting ethernet operation, administration and maintenance (oam)
WO2011003478A1 (en) 2009-07-10 2011-01-13 Telefonaktiebolaget Lm Ericsson (Publ) Loss measurement for multicast data delivery
CN102439948A (en) * 2009-04-24 2012-05-02 华为技术有限公司 Determining the group address for an ethernet-based multicast communication
CN102752138A (en) * 2012-06-30 2012-10-24 华为技术有限公司 Asynchronous configuration management method and network device
CN102801567A (en) * 2012-08-28 2012-11-28 北京傲天动联技术有限公司 Method for automatically discovering hierarchical network topology and method for establishing hierarchical network topology
WO2012177213A3 (en) * 2011-06-20 2013-04-25 Telefonaktiebolaget L M Ericsson (Publ) Methods and devices for monitoring a data path
EP2720420A1 (en) * 2012-10-12 2014-04-16 Alcatel Lucent Method for exchanging information for establishing a path between two nodes of a communication network
CN104270280A (en) * 2014-09-02 2015-01-07 烽火通信科技股份有限公司 System and method for realizing LSP (Label Switching Path) ping and tracert on router
CN104639416A (en) * 2009-11-13 2015-05-20 瑞典爱立信有限公司 Provider edge bridge with remote customer service interface
EP2852098A4 (en) * 2012-06-30 2015-05-20 Huawei Tech Co Ltd Method, node and system for detecting performance of layer three virtual private network
CN105790996A (en) * 2014-12-26 2016-07-20 北京华为朗新科技有限公司 Distributed gateway backup processing method and network equipment
EP3116160A4 (en) * 2014-04-04 2017-01-11 Huawei Technologies Co., Ltd Oam packet processing method, network device and network system
CN108206746A (en) * 2016-12-16 2018-06-26 华为技术有限公司 A kind of network transmission control method and relevant device

Families Citing this family (68)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2238721B1 (en) * 2007-08-01 2013-04-10 Telefonaktiebolaget LM Ericsson (publ) Gmpls based oam provisioning
US7996559B2 (en) * 2007-10-12 2011-08-09 Nortel Networks Limited Automatic MEP provisioning in a link state controlled Ethernet network
IL192140A0 (en) * 2008-06-12 2009-02-11 Ethos Networks Ltd Method and system for transparent lan services in a packet network
US8184526B2 (en) * 2008-09-15 2012-05-22 Ciena Corporation Systems and methods for Connectivity Fault Management extensions for automated activation of services through association of service related attributes
IL194412A (en) * 2008-09-28 2012-04-30 Eci Telecom Ltd Technique for combating loops in communication network
US8045570B2 (en) * 2008-09-30 2011-10-25 Nortel Networks Limited Extended private LAN
US8441941B2 (en) * 2008-10-06 2013-05-14 Cisco Technology, Inc. Automating identification and isolation of loop-free protocol network problems
US9100269B2 (en) * 2008-10-28 2015-08-04 Rpx Clearinghouse Llc Provisioned provider link state bridging (PLSB) with routed back-up
US8767587B1 (en) 2009-01-21 2014-07-01 Cisco Technology, Inc. Exploratory linktrace operations in a computer network
US8125914B2 (en) * 2009-01-29 2012-02-28 Alcatel Lucent Scaled Ethernet OAM for mesh and hub-and-spoke networks
EP2394392B1 (en) * 2009-02-05 2019-04-10 Telefonaktiebolaget LM Ericsson (publ) Topological location discovery in an ethernet network
US8605603B2 (en) * 2009-03-31 2013-12-10 Cisco Technology, Inc. Route convergence based on ethernet operations, administration, and maintenance protocol
US20110022728A1 (en) * 2009-07-22 2011-01-27 Telefonaktiebolaget Lm Ericsson (Publ) Link state routing protocols for database synchronization in gmpls networks
CN101640610B (en) * 2009-09-02 2012-01-11 中兴通讯股份有限公司 Method and system for automatic discovery of Ethernet link
KR20110067871A (en) * 2009-12-15 2011-06-22 한국전자통신연구원 Network access apparatus and method for watching and controlling traffic using oam packet in ip network
US8270314B2 (en) * 2009-12-29 2012-09-18 Cisco Technology, Inc. Synthetic frame loss ratio
US8416696B2 (en) * 2010-01-04 2013-04-09 Cisco Technology, Inc. CFM for conflicting MAC address notification
US8976680B2 (en) * 2010-03-15 2015-03-10 Juniper Networks, Inc. Operations, administration, and management fields for packet transport
US8873401B2 (en) * 2010-03-16 2014-10-28 Futurewei Technologies, Inc. Service prioritization in link state controlled layer two networks
RU2012130857A (en) * 2010-03-26 2014-05-10 РОКСТАР КОНСОРЦИУМ ЮЭс ЛП METHOD OF RESTORING COMMUNICATION DURING THE MALFUNCTION OF THE COMMUNICATION CHANNEL AND METHOD OF TRANSFER OF TRAFFIC (OPTIONS)
JP5534006B2 (en) * 2010-04-15 2014-06-25 日本電気株式会社 Transmission apparatus, transmission method, and computer program
US8396955B2 (en) * 2010-07-08 2013-03-12 Fujitsu Limited Systems and methods for discovery of network topology using service OAM
US8817594B2 (en) * 2010-07-13 2014-08-26 Telefonaktiebolaget L M Ericsson (Publ) Technique establishing a forwarding path in a network system
JP5530864B2 (en) * 2010-08-31 2014-06-25 株式会社日立製作所 Network system, management server, and management method
US8553562B2 (en) 2010-09-08 2013-10-08 Telefonaktiebolaget L M Ericsson (Publ) Automated traffic engineering for multi-protocol label switching (MPLS) with link utilization as feedback into the tie-breaking mechanism
US8553584B2 (en) * 2010-09-08 2013-10-08 Telefonaktiebolaget L M Ericsson (Publ) Automated traffic engineering for 802.1AQ based upon the use of link utilization as feedback into the tie breaking mechanism
US9300540B2 (en) * 2010-11-09 2016-03-29 Avaya Inc. Multicast network diagnostics
WO2012075163A1 (en) * 2010-11-30 2012-06-07 Eastlake Donald E Rd Systems and methods for multi-level switching of data frames
US20120140639A1 (en) * 2010-12-03 2012-06-07 Ip Infusion Inc. Convergence for connectivity fault management
US9143431B2 (en) * 2010-12-29 2015-09-22 Cisco Technology, Inc. Hiding a service node in a network from a network routing topology
CN102025571B (en) * 2010-12-30 2015-08-12 中兴通讯股份有限公司 The method and apparatus that multipoint link packet loss is measured
US9258140B2 (en) * 2011-01-06 2016-02-09 Tejas Networks Ltd Architecture for routing data of a customer network over provider's network in provider backbone bridges
WO2012131697A1 (en) * 2011-03-31 2012-10-04 Tejas Networks Limited Optimizing forward database for a bursty network traffic
CN103609066B (en) * 2011-04-28 2017-04-26 华为技术有限公司 Method and node for querying operation administration maintenance configuration information
US9264328B2 (en) 2011-11-07 2016-02-16 Ciena Corporation Systems and methods for dynamic operations, administration, and management
CN102571495B (en) * 2012-01-17 2015-01-28 深圳市汉普电子技术开发有限公司 Method and device for checking network topological structure for wire arrangement of printed circuit board
CN102651702A (en) * 2012-05-09 2012-08-29 华为技术有限公司 Ethernet performance measurement method and equipment
US9203549B2 (en) * 2012-06-06 2015-12-01 Ciena Corporation Systems and methods for operational simplification of carrier ethernet networks
US8687501B1 (en) 2012-07-25 2014-04-01 Overture Networks, Inc. Automatic detection and configuration of Ethernet OAM protocols
US9094313B2 (en) * 2012-09-12 2015-07-28 Verizon Patent And Licensing Inc. Data and media access controller (MAC) throughputs
US11102077B2 (en) * 2012-09-27 2021-08-24 Hewlett Packard Enterprise Development Lp Transmit specific along blocked link
US9313093B2 (en) 2012-11-14 2016-04-12 Ciena Corporation Ethernet fault management systems and methods
CN103078791B (en) * 2013-01-31 2016-08-10 华为技术有限公司 OAM message processing method, equipment and system
US9288069B2 (en) * 2013-03-11 2016-03-15 Cisco Technology, Inc. Loop avoidance technique for the multicast control plane
US9692677B2 (en) * 2013-06-12 2017-06-27 Avaya Inc. Implementing multicast link trace connectivity fault management in an Ethernet network
US9160651B2 (en) 2013-07-24 2015-10-13 Telefonaktiebolaget L M Ericsson (Publ) Metric biasing for bandwidth aware tie breaking
US9166887B2 (en) 2013-12-26 2015-10-20 Telefonaktiebolaget L M Ericsson (Publ) Multicast convergence
US9769044B1 (en) 2014-09-29 2017-09-19 Juniper Networks, Inc. Internet protocol service performance monitoring
CN105656705A (en) * 2014-11-12 2016-06-08 中兴通讯股份有限公司 Method and device for detecting multicast function of access equipment
US9641458B2 (en) * 2015-02-19 2017-05-02 Accedian Network Inc. Providing efficient routing of an operations, administration and maintenance (OAM) frame received at a port of an ethernet switch
US9596167B1 (en) 2015-04-24 2017-03-14 Juniper Networks, Inc. Internet protocol virtual private network service performance monitoring
US10951962B2 (en) 2015-08-10 2021-03-16 Delta Energy & Communications, Inc. Data transfer facilitation to and across a distributed mesh network using a hybrid TV white space, Wi-Fi and advanced metering infrastructure construct
US11172273B2 (en) 2015-08-10 2021-11-09 Delta Energy & Communications, Inc. Transformer monitor, communications and data collection device
WO2017058435A1 (en) 2015-10-02 2017-04-06 Delta Energy & Communications, Inc. Supplemental and alternative digital data delivery and receipt mesh network realized through the placement of enhanced transformer mounted monitoring devices
CN108370333B (en) * 2015-12-09 2021-05-18 华为技术有限公司 System, method and node for performance measurement in a segmented routing network
MX2018010238A (en) * 2016-02-24 2019-06-06 Delta Energy & Communications Inc Distributed 802.11s mesh network using transformer module hardware for the capture and transmission of data.
US10652633B2 (en) 2016-08-15 2020-05-12 Delta Energy & Communications, Inc. Integrated solutions of Internet of Things and smart grid network pertaining to communication, data and asset serialization, and data modeling algorithms
US11023606B2 (en) * 2016-10-02 2021-06-01 Vmware, Inc. Systems and methods for dynamically applying information rights management policies to documents
US10203998B2 (en) * 2017-02-22 2019-02-12 Accenture Global Solutions Limited Automatic analysis of a set of systems used to implement a process
US10587488B2 (en) * 2018-06-29 2020-03-10 Juniper Networks, Inc. Performance monitoring support for CFM over EVPN
EP3840298A4 (en) 2018-08-15 2021-09-22 Sony Group Corporation Network monitoring system, network monitoring method, and program
US11483195B2 (en) 2018-09-20 2022-10-25 Ciena Corporation Systems and methods for automated maintenance end point creation
JP6985611B2 (en) * 2018-10-11 2021-12-22 日本電信電話株式会社 Failure location estimation method and failure location estimation device
CN113709049A (en) * 2020-05-20 2021-11-26 中兴通讯股份有限公司 Method for creating intermediate point of maintenance entity group, node and readable storage medium
US11405315B2 (en) * 2020-09-25 2022-08-02 Juniper Networks, Inc. Multi-hop physical layer data collection protocol
US11438220B2 (en) * 2021-01-28 2022-09-06 Cisco Technology, Inc. Identifying redundant network links using topology graphs
US11349723B1 (en) * 2021-01-29 2022-05-31 Hewlett Packard Enterprise Development Lp Identification mapping for network devices
CN113407458B (en) * 2021-07-09 2023-07-14 广州博冠信息科技有限公司 Interface testing method and device, electronic equipment and computer readable medium

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070014290A1 (en) * 2005-07-12 2007-01-18 Cisco Technology, Inc. Address resolution mechanism for ethernet maintenance endpoints
US20070025256A1 (en) * 2005-07-12 2007-02-01 Cisco Technology, Inc. Broadband access node with a virtual maintenance end point

Family Cites Families (59)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5546540A (en) 1991-01-14 1996-08-13 Concord Communications, Inc. Automatic topology monitor for multi-segment local area network
US5734824A (en) 1993-02-10 1998-03-31 Bay Networks, Inc. Apparatus and method for discovering a topology for local area networks connected via transparent bridges
JPH07235929A (en) 1994-02-25 1995-09-05 Nippon Telegr & Teleph Corp <Ntt> Route confirming method
US5706440A (en) 1995-08-23 1998-01-06 International Business Machines Corporation Method and system for determining hub topology of an ethernet LAN segment
US5867396A (en) * 1995-08-31 1999-02-02 Xilinx, Inc. Method and apparatus for making incremental changes to an integrated circuit design
US5737319A (en) * 1996-04-15 1998-04-07 Mci Corporation Dynamic network topology determination
JP3036526B2 (en) * 1998-09-09 2000-04-24 日本電気株式会社 ATM test apparatus, ATM test method used therefor, and recording medium storing control program therefor
JP2000163344A (en) * 1998-11-27 2000-06-16 Nec Corp Data base recovery system for network management system
US6108702A (en) 1998-12-02 2000-08-22 Micromuse, Inc. Method and apparatus for determining accurate topology features of a network
US7058024B1 (en) * 1999-02-03 2006-06-06 Lucent Technologies, Inc. Automatic telecommunications link identification system
US6937576B1 (en) 2000-10-17 2005-08-30 Cisco Technology, Inc. Multiple instance spanning tree protocol
US7535826B1 (en) * 2000-12-11 2009-05-19 Juniper Networks, Inc Routing protocols for accommodating nodes with redundant routing facilities
US6590868B2 (en) * 2001-06-02 2003-07-08 Redback Networks Inc. Method and apparatus for restart communication between network elements
US7088674B2 (en) * 2001-12-27 2006-08-08 Alcatel Canada Inc. Method and apparatus for checking continuity of leaf-to-root VLAN connections
US7177325B2 (en) * 2002-07-25 2007-02-13 Micrel, Incorporated Operations, administration and maintenance (OAM) systems and methods for packet switched data networks
WO2004027580A2 (en) * 2002-09-20 2004-04-01 Nortel Networks Limited System and method for managing an optical networking service
US7505413B2 (en) * 2004-09-09 2009-03-17 Cariden Technologies, Inc. Methods and systems to perform traffic engineering in a metric-routed network
US7697419B1 (en) * 2002-11-22 2010-04-13 Allied Telesyn International Corporation Apparatus and method for managing a set of switches in a computer network
US7643424B2 (en) * 2003-03-22 2010-01-05 At&T Intellectual Property L, L.P. Ethernet architecture with data packet encapsulation
US7747716B2 (en) 2003-04-28 2010-06-29 Alcatel-Lucent Usa Inc. Injecting addresses to enable OAM functions
US7827308B2 (en) * 2003-05-23 2010-11-02 Alcatel-Lucent Canada Inc. Optical wavekey network and a method for distributing management information therein
EP1492381B1 (en) * 2003-06-24 2007-01-10 Alcatel Digital subscriber line access network with improved authentication, authorization, accounting and configuration control for multicast services
US8010643B2 (en) * 2003-08-01 2011-08-30 Opnet Technologies Inc System and methods for simulating traffic generation
US7701936B2 (en) * 2003-09-05 2010-04-20 Alcatel-Lucent Usa Inc. Obtaining path information related to a bridged network
US20050099954A1 (en) 2003-11-10 2005-05-12 Nortel Networks Limited Ethernet OAM network topography discovery
JP3725146B2 (en) * 2004-02-24 2005-12-07 株式会社エヌ・ティ・ティ・ドコモ Communication network management apparatus and communication network communication confirmation test method
US8923292B2 (en) * 2004-04-06 2014-12-30 Rockstar Consortium Us Lp Differential forwarding in address-based carrier networks
US8054751B2 (en) 2004-05-10 2011-11-08 Alcatel Lucent Remote access link fault indication mechanism
US20050259589A1 (en) * 2004-05-24 2005-11-24 Metrobility Optical Systems Inc. Logical services loopback
US7512141B2 (en) * 2004-07-08 2009-03-31 Alcatel Lucent Domain configuration in an ethernet OAM network having multiple levels
US7827307B2 (en) * 2004-09-29 2010-11-02 Cisco Technology, Inc. Method for fast switchover and recovery of a media gateway
JP2006174156A (en) 2004-12-16 2006-06-29 Nippon Telegr & Teleph Corp <Ntt> Network congestion scale determining method and system
GB2421671A (en) * 2004-12-22 2006-06-28 Marconi Comm Gmbh A node selects a source of timing information using network topology and the timing status of network nodes
US20060153220A1 (en) 2004-12-22 2006-07-13 Alcatel System and method for reducing OAM frame leakage in an ethernet OAM domain
US7688742B2 (en) * 2005-01-14 2010-03-30 Alcatel Lucent System and method for monitoring end nodes using ethernet connectivity fault management (CFM) in an access network
US7873057B2 (en) * 2005-04-26 2011-01-18 Accedian Networks Inc. Power over ethernet management devices and connection between ethernet devices
CN1859154B (en) 2005-05-08 2010-12-22 华为技术有限公司 Performance managing method between household gateway and broad band remote access server
CN100403689C (en) * 2005-05-16 2008-07-16 华为技术有限公司 Method for detecting Ethernet user line state
US7856001B2 (en) 2005-06-15 2010-12-21 U4Ea Wireless, Inc. Wireless mesh routing protocol utilizing hybrid link state algorithms
JP4546351B2 (en) * 2005-07-29 2010-09-15 富士通株式会社 Multicast trace route system in IP multicast network
WO2007038856A1 (en) 2005-10-05 2007-04-12 Nortel Networks Limited Provider link state bridging
US20110174307A1 (en) * 2006-01-04 2011-07-21 Lessi Stephane Device for Supplying Oxygen to the Occupants of an Aircraft and Pressure Regulator for Such a Device
US7742432B2 (en) * 2006-01-05 2010-06-22 International Busniness Machines Corporation Topology comparison
US7898982B2 (en) * 2006-03-22 2011-03-01 Alcatel Lucent Logical group endpoint discovery for data communication network
US8331266B2 (en) 2006-06-14 2012-12-11 Nokia Siemens Networks Oy LAN topology detection and assignment of addresses
CN1866879A (en) 2006-06-21 2006-11-22 烽火通信科技股份有限公司 Method for realizing ADSL CPE tele-management by SNMP
US7622089B1 (en) * 2006-07-19 2009-11-24 Uop Llc Conically shaped screenless internals for radial flow reactors
CN100450101C (en) * 2006-08-30 2009-01-07 华为数字技术有限公司 Conversion control method and system of OAM message
CN100550785C (en) * 2006-08-30 2009-10-14 华为技术有限公司 A kind of method of ethernet device link failure detection and system thereof
US20080101241A1 (en) * 2006-10-31 2008-05-01 Nortel Networks Limited Ethernet OAM at intermediate nodes in a PBT network
US20080107027A1 (en) * 2006-11-02 2008-05-08 Nortel Networks Limited Engineered paths in a link state protocol controlled Ethernet network
US7684352B2 (en) * 2006-11-02 2010-03-23 Nortel Networks Ltd Distributed storage of routing information in a link state protocol controlled network
US8085674B2 (en) * 2007-04-11 2011-12-27 Alcatel Lucent Priority trace in data networks
US9118433B2 (en) 2007-05-07 2015-08-25 Alcatel Lucent GPON OAM using IEEE 802.1ag methodology
US8125560B1 (en) * 2007-08-13 2012-02-28 Ambarella, Inc. System for topology based automatic focus
US7996559B2 (en) * 2007-10-12 2011-08-09 Nortel Networks Limited Automatic MEP provisioning in a link state controlled Ethernet network
US7894450B2 (en) 2007-12-31 2011-02-22 Nortel Network, Ltd. Implementation of VPNs over a link state protocol controlled ethernet network
US9432213B2 (en) 2007-12-31 2016-08-30 Rpx Clearinghouse Llc IP forwarding across a link state protocol controlled ethernet network
US7990855B2 (en) * 2008-07-11 2011-08-02 Alcatel-Lucent Usa Inc. Method and system for joint reverse link access and traffic channel radio frequency overload control

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070014290A1 (en) * 2005-07-12 2007-01-18 Cisco Technology, Inc. Address resolution mechanism for ethernet maintenance endpoints
US20070025256A1 (en) * 2005-07-12 2007-02-01 Cisco Technology, Inc. Broadband access node with a virtual maintenance end point

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"CARRIER ETHERNET", IXIACOM., 25 September 2007 (2007-09-25), XP008134336, Retrieved from the Internet <URL:http://www.ixiacom.com/pdfs/library/white_papers/carrier_ethernet.pdf> [retrieved on 20081222] *

Cited By (25)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102439948A (en) * 2009-04-24 2012-05-02 华为技术有限公司 Determining the group address for an ethernet-based multicast communication
AU2010256133B2 (en) * 2009-06-04 2013-08-01 Zte Corporation Method and apparatus for detecting ethernet operation, administration and maintenance (OAM)
US8670331B2 (en) 2009-06-04 2014-03-11 Zte Corporation Method and apparatus for detecting Ethernet operation, administration and maintenance (OAM)
WO2010139281A1 (en) * 2009-06-04 2010-12-09 中兴通讯股份有限公司 Method and apparatus for detecting ethernet operation, administration and maintenance (oam)
WO2011003478A1 (en) 2009-07-10 2011-01-13 Telefonaktiebolaget Lm Ericsson (Publ) Loss measurement for multicast data delivery
CN104639416A (en) * 2009-11-13 2015-05-20 瑞典爱立信有限公司 Provider edge bridge with remote customer service interface
CN104639416B (en) * 2009-11-13 2018-06-01 瑞典爱立信有限公司 A kind of provider's Edge Bridge and for the method in provider's Edge Bridge
US9191290B2 (en) 2011-06-20 2015-11-17 Telefonaktiebolaget L M Ericsson (Publ) Methods and devices for monitoring a data path
WO2012177213A3 (en) * 2011-06-20 2013-04-25 Telefonaktiebolaget L M Ericsson (Publ) Methods and devices for monitoring a data path
EP2852098A4 (en) * 2012-06-30 2015-05-20 Huawei Tech Co Ltd Method, node and system for detecting performance of layer three virtual private network
CN102752138A (en) * 2012-06-30 2012-10-24 华为技术有限公司 Asynchronous configuration management method and network device
US9774494B2 (en) 2012-06-30 2017-09-26 Huawei Technologies Co., Ltd. Method, node, and system for detecting performance of layer 3 virtual private network
CN102801567B (en) * 2012-08-28 2015-07-08 北京傲天动联技术股份有限公司 Method for automatically discovering hierarchical network topology and method for establishing hierarchical network topology
CN102801567A (en) * 2012-08-28 2012-11-28 北京傲天动联技术有限公司 Method for automatically discovering hierarchical network topology and method for establishing hierarchical network topology
CN104718732A (en) * 2012-10-12 2015-06-17 阿尔卡特朗讯 Method for exchanging information for establishing a path between two nodes of a communication network
US9461906B2 (en) 2012-10-12 2016-10-04 Alcatel Lucent Method for exchanging information for establishing a path between two nodes of a communication network
EP2720420A1 (en) * 2012-10-12 2014-04-16 Alcatel Lucent Method for exchanging information for establishing a path between two nodes of a communication network
CN104718732B (en) * 2012-10-12 2018-01-19 阿尔卡特朗讯 For to establish the method that path exchanges information between the two of communication network node
WO2014056863A1 (en) * 2012-10-12 2014-04-17 Alcatel Lucent Method for exchanging information for establishing a path between two nodes of a communication network
EP3116160A4 (en) * 2014-04-04 2017-01-11 Huawei Technologies Co., Ltd Oam packet processing method, network device and network system
US10116546B2 (en) 2014-04-04 2018-10-30 Huawei Technologies Co., Ltd. OAM packet processing method, network device, and network system
CN104270280A (en) * 2014-09-02 2015-01-07 烽火通信科技股份有限公司 System and method for realizing LSP (Label Switching Path) ping and tracert on router
CN105790996A (en) * 2014-12-26 2016-07-20 北京华为朗新科技有限公司 Distributed gateway backup processing method and network equipment
CN108206746A (en) * 2016-12-16 2018-06-26 华为技术有限公司 A kind of network transmission control method and relevant device
EP3468101A4 (en) * 2016-12-16 2019-07-17 Huawei Technologies Co., Ltd. Method for controlling network transmission and related apparatus

Also Published As

Publication number Publication date
US20090232005A1 (en) 2009-09-17
BRPI0818254A2 (en) 2015-04-14
BRPI0818252A8 (en) 2016-03-08
US7898965B2 (en) 2011-03-01
BRPI0818246A8 (en) 2016-03-08
CN101904184B (en) 2013-06-12
JP2011501539A (en) 2011-01-06
EP2208312A1 (en) 2010-07-21
CN101897151A (en) 2010-11-24
JP2013179628A (en) 2013-09-09
US9059918B2 (en) 2015-06-16
KR20130132664A (en) 2013-12-04
KR20100100784A (en) 2010-09-15
JP2011501538A (en) 2011-01-06
BRPI0818246A2 (en) 2015-04-07
BRPI0818252A2 (en) 2015-04-07
CN101904184A (en) 2010-12-01
US20090232006A1 (en) 2009-09-17
JP2015080248A (en) 2015-04-23
WO2009049307A1 (en) 2009-04-16
KR20140130523A (en) 2014-11-10
KR101487572B1 (en) 2015-01-29
US8918538B2 (en) 2014-12-23
BRPI0818254A8 (en) 2016-03-08
JP2011501537A (en) 2011-01-06
US20120287795A1 (en) 2012-11-15
US7996559B2 (en) 2011-08-09
US8264970B2 (en) 2012-09-11
CN103607326A (en) 2014-02-26
WO2009049311A1 (en) 2009-04-16
US20110255417A1 (en) 2011-10-20
CN101904134A (en) 2010-12-01
JP5306365B2 (en) 2013-10-02
KR20140146143A (en) 2014-12-24
JP5366959B2 (en) 2013-12-11
JP5325887B2 (en) 2013-10-23
EP2206367A1 (en) 2010-07-14
EP2210374A1 (en) 2010-07-28
KR20100105542A (en) 2010-09-29
KR20100096086A (en) 2010-09-01
US20090234969A1 (en) 2009-09-17
CN101897151B (en) 2013-06-26

Similar Documents

Publication Publication Date Title
US7898965B2 (en) IP network and performance monitoring using ethernet OAM
US10523560B2 (en) Service level agreement based next-hop selection
US10454812B2 (en) Service level agreement based next-hop selection
JP5550757B2 (en) Ethernet network controlled by IP forwarding with link state protocol
US8588081B2 (en) Monitoring a flow set to detect faults
US8767587B1 (en) Exploratory linktrace operations in a computer network
US9819586B2 (en) Network-based ethernet switching packet switch, network, and method
WO2014111900A1 (en) Methods and devices for implementing shortest path bridging mac mode support over a virtual private lan service network
WO2020212997A1 (en) Generating and utilizing topology information for an ethernet ring to support network management
Artham Virtual Private Lan Service (Architecture)

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 200880120444.1

Country of ref document: CN

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 08837640

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2010529140

Country of ref document: JP

WWE Wipo information: entry into national phase

Ref document number: 2512/DELNP/2010

Country of ref document: IN

NENP Non-entry into the national phase

Ref country code: DE

REEP Request for entry into the european phase

Ref document number: 2008837640

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2008837640

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 20107010464

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: PI0818252

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20100412