Evolution of ethernet networks
View Patent ↗An Ethernet network comprises nodes which support a plurality of different forwarding modes. A range of VLAN Identifiers (VIDs) are allocated to each of the forwarding modes. Connections are configured between a source node and a destination node of the network using different forwarding modes. Packets carrying data traffic are sent to the destination node by selectively setting a VID in a packet to a first value, to transfer a packet via a first connection and a first forwarding mode, and a second value to transfer a packet via the second connection and the second forwarding mode. Packets received from both of the connections and sent on to an end-user. VLAN Identifiers can be allocated to different releases of functionality at nodes (e.g. software releases) such that packets are forwarded via a set of nodes supporting a first release, or via a set of nodes supporting a second release. It is possible to provide a controlled and disruption-free network evolution.
1. A method of transferring packets across an Ethernet network comprising a plurality of nodes, the network supporting a plurality of different forwarding modes, the method comprising:
allocating a range of VLAN Identifiers (VIDs) to each of the forwarding modes, each forwarding mode making a different use of a VID within a header of a packet;
configuring a first connection between a source node and a destination node of the network using a first forwarding mode and a VID in the packet having a first value selected from a first range of VIDs, the first forwarding mode being Provider Backbone Bridging (PBB);
configuring a second connection between the source node and the destination node of the network using a second forwarding mode and a VID in the packet having a second value selected from a second range of VIDs, second forwarding mode being Provider Link State Bridging (PLSB); and
sending packets carrying data traffic to the destination node by selectively:
setting a VID in a packet to the first value, to transfer the packet via the first connection and the first forwarding mode; and,
setting a VID in a packet to the second value to transfer the packet via the second connection and the second forwarding mode.
2. The method according to claim 1 wherein the step of configuring the second connection comprises testing operation of the second connection by sending test packets before sending a packet carrying data traffic over the second connection.
3. The method according to claim 1 wherein the step of configuring the second connection comprises sending test packets which nodes can use to learn the topology of the network and form the second connection before sending packets carrying data traffic over the second connection.
4. The method according to claim 1 wherein data traffic flows are identified by service identifiers, the method further comprising:
storing a look-up table relating a service identifier to a VID value for each of the first connection and the second connection.
5. The method according to claim 4 wherein at least one of:
the source node and the destination node has a plurality of MAC addresses, the method further comprising:
storing a look-up table relating a service identifier to a combination of a MAC address and a VID value for each of the first connection and the second connection; and,
setting a VID and a MAC address when sending a packet carrying traffic to the destination node of the network.
6. The method according to claim 1 wherein packets sent via the first and second connections each carry a data payload, and wherein a packet sent via one of the connections carries a data payload which is contiguous to a data payload carried in a packet sent via the other of the connections.
7. The method according to claim 1 wherein the destination node accepts packets from the first connection and the second connection in the order in which they arrive at the destination node.
8. A method of transferring packets across an Ethernet network comprising a plurality of nodes, the network supporting a plurality of different forwarding modes, wherein a range of VLAN Identifiers (VIDs) has been allocated to each of the forwarding modes, each forwarding mode making a different use of a VID within a header of a packet, the method comprising, at a first node:
receiving a first association between a service identifier for data traffic and a VID having a first value corresponding to a first forwarding mode, the first forwarding mode being Provider Backbone Bridging (PBB);
receiving a second association between the service identifier for data traffic and a second VID having a second value corresponding to a second forwarding mode, second forwarding mode being Provider Link State Bridging (PLSB); and
selectively sending packets carrying data traffic to the destination node by setting a VID in the packet to the first value, to transfer the packet via a first connection using the first forwarding mode, and setting a VID in a packet to the second value to transfer the packet via a second connection using the second forwarding mode.
9. A The method according to claim 8 further comprising receiving an instruction of which connection is to be used, and selecting one of the VIDs based on the received instruction.
10. A The method according to claim 8 further comprising sending test packets with a VID set to the second value to test the second connection before sending packets carrying data traffic over the second connection.
11. A The method according to claim 8 further comprising sending test packets which nodes can use to learn the topology of the network and form the second connection before sending packets carrying data traffic over the second connection.
12. A The method according to claim 8 further comprising receiving an instruction of which forwarding mode to use to send the data traffic.
13. A computer program product comprising a non-transitory machine-readable medium bearing instructions which, when executed by a processor, cause the processor to implement the method of claim 1 .
14. A method of transferring packets across an Ethernet network comprising a plurality of nodes, the method comprising:
configuring a first connection between a source node and a destination node of the network via a first set of nodes of the network, the first set of nodes using a first release of functionality to implement a first packet forwarding mode, the first connection being allocated a VLAN Identifier (VID) having a first value, the first release of functionality including Provider Backbone Bridging (PBB) functionality;
installing a second release of functionality to implement a second packet forwarding mode at at least one node of a second set of nodes, the second release of functionality including Provider Link State Bridging (PLSB) functionality;
configuring a second connection between the source node and the destination node of the network via the second set of the nodes of the network, the second connection being allocated a VLAN Identifier (VID) having a second value;
sending packets carrying data traffic to the destination node by selectively:
setting a VID in a packet to the first value, to transfer the packet via the first connection, and
setting a VID in the packet to the second value to transfer the packet via the second connection.
15. The method according to claim 14 wherein the step of configuring the second connection comprises testing operation of the second connection by sending test packets before the step of sending the second packet carrying traffic.
16. The method according to claim 14 wherein the first set of nodes and the second set of nodes are equal.
17. The method according to claim l 4 wherein each release of functionality is allocated a different range of VIDs.
18. The method according to claim 14 wherein the first release of functionality to implement a packet forwarding mode and the second release of functionality to implement the packet forwarding mode are software releases.
19. A computer program product comprising a non-transitory machine-readable medium bearing instructions which, when executed by a processor, cause the processor to implement the method of claim 14 .