METHOD OF AUTOMATIC SETUP BY A FIRST DEVICE OF A SESSION COMPLYING WITH A DYNAMIC ROUTING PROTOCOL WITH A SECOND DEVICE

Abstract

A method of automatic setup by a first device of a session complying with a dynamic routing protocol with a second device. The setup method includes, subsequent to detection by the first device of existence of a connectivity with the second device, the first device being associated with a first autonomous system number and not knowing any autonomous system number associated with the second device: an exchange with the second device including announcement to the second device of the first autonomous system number, and discovery of a second autonomous system number with which the second device is associated; or allocation to the second device of a third autonomous system number and announcement to the second device of the third autonomous system number which has been allocated to it; and setup with the second device of a session according to the routing protocol by using the autonomous system numbers exchanged.

Claims

1. A method for automatically establishing, by a first network device, a session complying with a dynamic routing protocol with a second network device, the first device being associated with a first autonomous system number and not knowing any autonomous system number associated with the second device, said method comprising, following detection by the first device of existence of a connectivity with the second device: exchanging with the second device comprising the advertisement to the second device of the first autonomous system number, said exchanging further comprising: discovery of an autonomous system number, called second autonomous system number, with which the second device is associated; or allocating to the second device an autonomous system number, called third autonomous system number and the advertisement to the second device of the third autonomous system number that has been allocated thereto; and establishing with the second device at least one session according to said routing protocol by using the autonomous system numbers exchanged during the step of exchange between the first and the second device.

2. The method according to claim 1, wherein the exchanging further comprises, following the allocation of the third autonomous system number to the second device: receiving a response from the second device refusing the third autonomous system number that has been allocated thereto by the first device and comprising a fourth autonomous system number with which the second device is already associated; and storing the fourth autonomous system number in association with the second device in replacement of the third autonomous system number.

3. The method according to claim 1 further comprising sending by the first device to the second device a range of autonomous system numbers from which the second device can draw to allocate an autonomous system number to at least a third device.

4. The method according to claim 1 wherein a session is established during the establishing on the initiative of the first device.

5. The method according to claim 1 wherein a session is established during the establishing on the initiative of the second device.

6. The method according to claim 1 wherein the automatic routing protocol is the BGP (Border Gateway Protocol) or the TRIP (Telephony Routing over IP) protocol.

7. The method according to claim 6, wherein, the routing protocol is the BGP protocol, and the advertisements of the first and when appropriate, of the third autonomous system number and/or the discovery of the second autonomous system number are carried out by using router advertisement messages and/or router solicitation messages.

8. The method according to claim 6 wherein, the routing protocol is the BGP protocol, and the advertisements to the second device of the first and when appropriate, of the third autonomous system number are carried out by using a BGP session establishment message OPEN sent by the first device to the second device.

9. The method according to claim 6 wherein, the routing protocol is the TRIP protocol, and the exchanging further comprises: advertising a first IP Telephony Administrative Domain identifier associated with the first device; and discovering a second IP Telephony Administrative Domain identifier associated with the second device, or allocation and exchange of a third IP Telephony Administrative Domain identifier to the second device.

10. A method for communication with a first network device implemented by a second network device, said method comprising: exchanging with the first device comprising: receiving from the first device an autonomous system number, called first autonomous system number, associated with the first device; storing the first autonomous system number in association with the first device; said exchanging further comprising: provisioning the first device with an autonomous system number, called second autonomous system number, with which the second device is associated; or receiving from the first device an autonomous system number, called third autonomous system number, allocated by the first device to the second device and, if the second device is not already associated with an autonomous system number, configuring the second device with the third autonomous system number; and establishing with the first device at least one session according to said routing protocol by using the autonomous system numbers exchanged between the first and the second device.

11. The communication method according to claim 10, wherein, if the second device is already associated with an autonomous system number, called fourth autonomous system number, the exchanging comprises rejecting the third autonomous system number allocated by the first device and provisioning the first device with the fourth autonomous system number with which the second device is associated.

12. A non-transitory computer-readable medium comprising a computer program recorded thereon, the computer program comprising including instructions for executing a method for automatically establishing, by a first network device, a session complying with a dynamic routing protocol with a second network device, when said program is executed by a processor of the first device, the first device being associated with a first autonomous system number and not knowing any autonomous system number associated with the second device, wherein the instructions configure the first device to, following detection by the first device of existence of a connectivity with the second device: exchange with the second device comprising advertisement to the second device of the first autonomous system number, said exchange further comprising: discovery of an autonomous system number, called second autonomous system number, with which the second device is associated; or allocating to the second device an autonomous system number, called third autonomous system number and the advertisement to the second device of the third autonomous system number that has been allocated thereto; and establish with the second device at least one session according to said routing protocol by using the autonomous system numbers exchanged during the step of exchange between the first and the second device.

13. A non-transitory computer-readable recording medium on which a computer program is recorded, the computer program comprising instructions for executing a method for communication with a first network device implemented by a second network device, when the instructions are executed by a processor of the second device, wherein the instructions configure the second device to: exchange with the first device comprising: receiving from the first device an autonomous system number, called first autonomous system number, associated with the first device; storing the first autonomous system number in association with the first device; said exchange further comprising: provisioning the first device with an autonomous system number, called second autonomous system number, with which the second device is associated; or receiving from the first device an autonomous system number, called third autonomous system number, allocated by the first device to the second device and, if the second device is not already associated with an autonomous system number, configuring the second device with the third autonomous system number; and establish with the first device at least one session according to said routing protocol by using the autonomous system numbers exchanged between the first and the second device.

14. A network device, called first device, configured to automatically establish a session complying with a dynamic routing protocol with a second network device, the first device being associated with a first autonomous system number and not knowing any autonomous system number associated with the second device, said first device comprising: a processor; and a non-transitory computer-readable medium comprising instructions stored thereon, which when executed by the processor configure the first device to, following detection by the first device of existence of a connectivity with the second device: exchange with the second device, comprising: making an advertisement to the second device of the first autonomous system number; discovering an autonomous system number, called second autonomous system number, with which the second device is associated, or allocating to the second device an autonomous system number, called third autonomous system number, and making an advertisement to the second device of the third autonomous system number that has been allocated thereto; and establish with the second device at least one session according to said routing protocol by using the autonomous system numbers exchanged between the first and the second device.

15. A network device, called second device, configured to automatically establish a session complying with a dynamic routing protocol with a first network device, said second device comprising: processor; and a non-transitory computer-readable medium comprising instructions stored thereon, which when executed by the processor configure the second device to: exchange with the first device, comprising: receiving from the first device an autonomous system number, called first autonomous system number, associated with the first device; storing the first autonomous system number in association with the first device; said exchange further comprising: providing the first device with an autonomous system number, called second autonomous system number, with which the second device is associated; or receiving from the first device an autonomous system number, called third autonomous system number, allocated by the first device to the second device and, if the second device is not already associated with an autonomous system number, configuring the second device with the third autonomous system number; and establish with the first device at least one session complying with said routing protocol by using the autonomous system numbers exchanged between the first and the second device.

16. The network device according to claim 15, wherein the exchange further comprises, if the second device is already associated with an autonomous system number, called fourth autonomous system number, rejecting the third autonomous system number allocated by the first device and providing the first device with the fourth autonomous system number with which the second device is associated.

17. (canceled)

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0078] Other characteristics and advantages of the present invention will emerge from the description given below, with reference to the appended drawings which illustrate an exemplary embodiment thereof devoid of any limiting character. In the figures:

[0079] FIG. 1 diagrammatically represents a communication system according to the invention in a particular embodiment;

[0080] FIG. 2 illustrates a network device of the communication system of FIG. 1, according to the invention in a particular embodiment;

[0081] FIG. 3 represents the hardware architecture of the network device of FIG. 2, in a particular embodiment;

[0082] FIGS. 4 to 6 illustrate the main steps of the automatic establishment and communication methods implemented by the communication devices of the system in FIG. 1, in different embodiments; and

[0083] FIGS. 7 and 8 illustrate examples of application of the invention.

DETAILED DESCRIPTION OF THE INVENTION

[0084] FIG. 1 represents, in its environment, a communication system 1 according to the invention, in a particular embodiment.

[0085] This embodiment comprises the detection of a directly connected i.e. physically connected neighbor node (active link or active interface). Alternatively, it is also possible to consider non-directly connected nodes (i.e. remote nodes); in this case, the multi-hop BGP function (RFC4271) is preferably activated by the BGP nodes.

[0086] In the example considered in FIG. 1, the communication system 1 comprises a plurality of network devices (referenced by means of the letter T, possibly followed by a complement (e.g. T11 or T or even T)) belonging to the network infrastructure of a data center (DC). The devices T are interconnected via one or more communication interfaces (illustrated in the figure in broken lines) and form a communication network R.

[0087] There is no limitation attached to the nature of the network devices T (also called nodes of the network R): they are any network elements, such as for example routers, switches, etc. No limitation is attached either to the nature of the communication interfaces used by the devices T to communicate together within the network R. They may be mobile or fixed, wired or wireless communication interfaces, etc.

[0088] The communication network R formed by the devices T uses a dynamic routing protocol. The invention allows automatic establishment of sessions complying with this routing protocol between different network devices T in order to activate the use of the dynamic routing protocol in the network R. In the embodiment described here, the considered dynamic routing protocol is the BGP protocol.

[0089] As mentioned above, in accordance with the BGP protocol, to establish sessions with their neighbors in the network R (i.e. with the devices of the network R with which they have an established physical connection), the different devices of the network R must know the autonomous system number(s) that is (are) associated thereto (i.e. to which they are attached), as well as the autonomous system numbers associated with their neighbors. The invention allows an automatic exchange of these AS numbers between two neighbor devices without requiring, as in the prior art, a prior static (e.g. manual) configuration of these devices with each of these pieces of information (i.e. AS number of the considered device and AS numbers of its neighbors). The invention indeed allows a dynamic configuration of the devices of the network with this information when at least one device of the network R is configured with its own AS number and/or has a range of values in which the AS numbers of its neighbors can be allocated, as more detailed later. This range can be contiguous or non-contiguous.

[0090] The network infrastructure on which the data center is based implements here SDN architecture. This assumption is not, however, a prerequisite for implementing the invention.

[0091] The SDN network infrastructure comprises, in addition to the network devices T, a controller 2 enabling coherent and deterministic operation of the network R of the data center. The controller 2 has, in a known manner, a global and systemic vision of the network R, of its topology, of its components, of the available network functions (virtualized or not), of their status, etc. This controller 2 is capable of defining a routing policy within the network R, based on the BGP protocol, and making it possible to carry the traffic of the data center in accordance with the objectives set by the operator of the data center. It is, in the example illustrated in FIG. 1, connected to one of the network devices T, namely to the device T11.

[0092] In the example illustrated in FIG. 1, the communication system 1 is organized into a plurality of hierarchical levels (three in FIG. 1 referenced NIV1, NIV2 and NIV3), each hierarchical level being itself organized in one or more clusters (i.e. groups) of devices: a cluster for the hierarchical level NIV1 comprising four devices T11, T12, T13 and T14, four clusters for the hierarchical level NIV2 each comprising respectively a device T21, T22, T23 and T24, and four separate clusters also for the hierarchical level NIV3 each comprising respectively the four devices T31, T32, T33 and T34. The network devices of the last hierarchical level NIV3 are connected here to the various virtual or hardware machines (for example servers) of the data center (generally referred S).

[0093] Of course, this network infrastructure architecture and its organization into hierarchical levels and into clusters (comprising one or more devices) is given only by way of illustration, and the invention applies to other types of architectures (having a central unit such as the controller 2 or not). The choice of the architecture of the network R comes under the engineering and the topology of the network, under the size of the data center, etc.

[0094] As mentioned previously, the use of the dynamic routing protocol BGP within the network R formed by the devices T requires the allocation of autonomous system numbers to each of these devices. In the example considered in FIG. 1, the following choices are made by the operator of the data center for this allocation: [0095] use of private AS numbers (for example, belonging to the range 64512-65524 or to the range of values 4200000000-4294967294 in the case of AS numbers coded on 4 bytes); and [0096] use of the same AS number for the network devices located at the same hierarchical level and belonging to the same cluster.

[0097] This AS number allocation policy is given for illustrative purposes only. Other policies may be adopted by the operator of the data center (for example, allocation of the same AS number for all devices belonging to the same hierarchical level, or of the same AS number for all devices of the network, separate AS numbers per address family; etc.).

[0098] In the embodiment described here, the devices T of the network R all comply with the invention: as illustrated in FIG. 2, each device T of the network is equipped here with both means 3 enabling it to establish BGP sessions automatically with its neighbors (i.e. with the other devices of the network R with which it has an established physical, i.e. active connection) according to the invention and to act as a first device within the meaning of the invention with regard thereto, and means 4 enabling it to communicate with its neighbors according to the invention and to act as a second device within the meaning of the invention with regard thereto. However, the means 3 and 4 are not necessarily activated simultaneously, depending on the configuration of the device T. Thus, for example, if the device T is not associated with an AS number with which it has been previously configured (this AS number being stored as such in one of its memories, for example in a non-volatile memory), the means 3 are deactivated while its means 4 can be activated. Conversely, as soon as a device T is configured with an AS number associated therewith, its means 3 can be activated (instead of the means 4 or simultaneously with the means 4).

[0099] These assumptions are not limiting. Alternatively, it is possible to consider configuring some devices of the network R so as to fulfill only the functions of a first device within the meaning of the invention (in other words, these devices are only equipped with means 3). This can be the case for example of the devices belonging to the hierarchical levels having the weakest indices (for example at the level VIN1). It is also possible to consider configuring some devices of the network R (for example the devices belonging to the hierarchical level having the highest index, such as at the level NIV3 in FIG. 1) so as to fulfill only the functions of a second device within the meaning of the invention (in other words, these devices are only equipped with means 4).

[0100] In the embodiment described here, the devices T of the network R according to the invention have the hardware architecture of a computer 5 as illustrated in FIG. 3. They comprise in particular a processor 6, a random access memory 7, a read-only memory 8, a non-volatile flash memory 9, as well as communication means 10 comprising one or several communication interface(s).

[0101] The communication means 10 allow each device T to be connected to one or several other devices T of the network R, and to communicate with these other devices in particular for routing and carrying the traffic within the network, by using the BGP protocol. To this end, the devices T are configured here to listen by default on the TCP port 179, in order to receive the messages relating to the BGP protocol. In order to differentiate the procedure for automatically establishing BGP sessions from the one defined by the current standard, other port numbers can be used if the devices T have been instructed for this purpose beforehand.

[0102] The read-only memory 8 of each network device T constitutes a recording medium according to the invention, readable by the processor 6 and on which computer programs PROG3 and PROG4 are recorded according to the invention: the program PROG3 includes instructions for the execution of the steps of the automatic establishment method according to the invention, while the program PROG4 includes instructions for the execution of the steps of the communication method according to the invention.

[0103] More particularly, the computer program PROG3 defines functional (and software here) modules of the means 3 of the device T, which are configured to implement the steps of the method for automatically establishing a BGP session according to the invention with another device of the network R here referred to as T, when the means 3 of the device T are activated. It is assumed here that the means 3 of the device T are only activated to establish a BGP session with the device T only when the device T is already configured with an autonomous system number associated thereto (i.e., to which it is attached); however, the device T ignores, before implementing the automatic establishment method, any autonomous system number associated with the device T (in other words, the device T does not know an autonomous system number associated with the device T, that is to say, it has not been configured with any autonomous system number associated with the device T).

[0104] The functional modules defined by the program PROG3 are based on and/or control the hardware elements 6-10 of the computer 5 cited above, and comprise in particular here, as illustrated in FIG. 2: [0105] a detection module 3A configured to detect the establishment or existence of a physical connection with the device T; [0106] an exchange module 3B, configured to: [0107] make an advertisement to the network device T of the autonomous system number (first autonomous system number within the meaning of the invention) with which the device T is configured when appropriate and which is associated therewith; [0108] discover an autonomous system number (second autonomous system number within the meaning of the invention), with which the device T is associated where appropriate or allocate to the device T an autonomous system number (third autonomous system number), and make an advertisement to the device T of the autonomous system number that has been allocated thereto; [0109] and an establishment module 3C, configured to establish with the device T a session according to the routing protocol BGP by using the autonomous system numbers associated with the devices T and T.

[0110] The computer program PROG4 defines functional (and software here) modules of the means 4 of the network device T, defined to implement the steps of the communication method according to the invention with another device referred to as T of the network R, when the means 4 of the device T are activated. The means 4 of the device T can be activated whether or not it has been previously configured with an autonomous system number to which it is attached. It is assumed here that the device T does not know (in other words, ignores) the autonomous system number possibly associated with the device T (i.e., it was not configured prior to the implementation of the method for communication with the autonomous system number associated with the device T).

[0111] The functional modules defined by the program PROG4 are based on and/or control the hardware elements 6-10 of the computer 5 cited above, and comprise in particular here, as illustrated in FIG. 2: [0112] a detection module 4A configured to detect the establishment or existence of a physical connection with the device T (this detection module can be the same shared function where appropriate with the detection module 3A defined by the program PROG3); [0113] a exchange module 4B configured to: [0114] receive an advertisement message from the device T comprising an autonomous system number (first autonomous system number within the meaning of the invention) associated with the device T; [0115] store this autonomous system number in association with the device T;

[0116] the exchange module 4B being further configured to: [0117] receive a solicitation message from the device T inviting the device T to provide it with an autonomous system number (second autonomous system number within the meaning of the invention), with which the device T is associated where appropriate and provide the device T with the autonomous system number with which the device T is associated; or [0118] receive an advertisement message from the device T comprising an autonomous system number (third autonomous system number within the meaning of the invention), allocated by the device T to the device T and: [0119] if the device T is not already associated with an autonomous system number, configure the device T with this autonomous system number allocated by the device T; [0120] if the device T is however already associated with an autonomous system number, reject the autonomous system number allocated by the device T and provide the device T with the autonomous system number with which the device T is already associated; [0121] and an establishment module 4C, configured to establish with the device T a session according to the BGP routing protocol by using the autonomous system numbers associated with the devices T and T.

[0122] FIGS. 4 to 6 illustrate the main steps of the automatic establishment and communication methods implemented respectively by the means 3 and 4 of the devices T of the network R in different embodiments and different contexts.

[0123] More specifically, FIG. 4 illustrates a first embodiment in which a device T of the network R is configured with a private autonomous system number with which it is associated (noted ASN(T) with for example ASN(T)=65500) (step E10). It is assumed in the example illustrated in FIG. 4 that the device T is only configured with its autonomous system number and does not know the autonomous system numbers possibly associated with the other devices of the network R. The device T is for example here the device T11 belonging to the hierarchical level NIV1 of the network R illustrated in FIG. 1. The means 3 of the device T are assumed to be activated. The invention does not impose any chronology concerning steps E50 and E70.

[0124] There is no limitation attached to the way in which the configuration of device T with the autonomous system number ASN(T) was carried out. For example, this configuration could be carried out by the administrator of the network R by connecting thereto via a Telnet session, or by using a protocol such as NETCONF. Alternatively, this configuration could be carried out via the controller 2. The autonomous system number ASN(T) is stored in the non-volatile memory 7 of the device T.

[0125] In the example illustrated in FIG. 4, a device T of the network R is also considered, configured with a private autonomous system number noted ASN(T) with which it is associated. For example ASN(T)=65001 (step E20). It is assumed in the example illustrated in FIG. 4 that the device T is only configured with its own autonomous system number ASN(T) and does not know the possible autonomous system numbers associated with the other devices on the network R, and particularly the one associated with the device T. The device T is for example here the device T21 belonging to the hierarchical level NIV2 of the network R illustrated in FIG. 1. The means 4 of the device T are assumed to be activated. It is assumed here for the sake of simplification that the means 3 of the device T are deactivated.

[0126] As with the device T, there is no limitation attached to the way in which the configuration of the device T with the autonomous system number ASN(T) was carried out. This configuration could be carried out by the administrator of the network R by connecting thereto via a Telnet session, or by using a protocol such as NETCONF. Alternatively, this configuration could be carried out via the controller 2 or via another device of the network, for example by a device of the hierarchical level NIV1 such as the device T12, T13 or T14 (as detailed further subsequently with reference to FIG. 6). The autonomous system number ASN(T) is stored in the non-volatile memory 7 of the device T.

[0127] It is now assumed that a physical connection is established between the device T and the device T, via their respective communication means 10 (step E30). Such a physical connection can be established for example by means of the link-local addresses of the devices T and T. These link-local addresses are, in a manner known per se, automatically configured on a network device during the initialization of its communication interfaces; they allow two neighbor network devices to communicate via said communication interfaces, and are exchanged between these two neighbor devices, for example via a neighbor discovery protocol.

[0128] The establishment of the physical connection between the device T and the device T is detected by the detection module 3A of the device T (step E40).

[0129] This triggers an exchange with the device T initialized by the module 3B of the device T.

[0130] More specifically, during this exchange, the device T, via its module 3B, makes an advertisement to the device T of the autonomous system number ASN(T) associated therewith (step E50). In the example illustrated in FIG. 4, this advertisement is made via the sending by the module 3B of the device T (and via the communication means 10 of the device T and the physical connection established with the device T) of a router solicitation RS message to the device T. This RS message comprises, in a field or in an option of the message, the autonomous system number ASN(T).

[0131] In addition, by means of this same solicitation RS message, the module 3B of the device T solicits the device T, in a field or an option of the message provided for this purpose, so that it provides it with the autonomous system number ASN(T) assigned thereto (discovery of the autonomous system number associated with the device T within the meaning of the invention).

[0132] In other words, the same solicitation RS message is used both here for the advertisement of the autonomous system number associated with device T and for the discovery of the autonomous system number associated with device T. This makes it possible to limit the signaling exchanged between the devices T and T. Alternatively, separate messages can be used; for example, the advertisement of the autonomous system number ASN(T) can be carried out by means of a router advertisement RA message and the discovery of the autonomous system number ASN(T) can be carried out by means of a router solicitation RS message.

[0133] Upon receipt of the RS message sent by the device T, the module 4B of the device T extracts the autonomous system number ASN(T) associated with the device T and stores it, for example in its non-volatile memory 7, in association with the device T (step E60).

[0134] Then it responds to the device T by providing it with (making an advertisement of) the autonomous system number ASN(T) associated therewith (step E70). In the example illustrated in FIG. 4, the autonomous system number ASN(T) is provided to the device T in an advertisement RA message, in a field or an option of this message.

[0135] Upon receipt of the RA message sent by the device T, the module 3B of the device T extracts the autonomous system number ASN(T) associated with the device T and stores it, for example in its non-volatile memory 7, in association with the device T (step E80).

[0136] Once the exchange of the autonomous system numbers between the devices T and T has ended, a BGP session is automatically established between these two devices, in a manner known per se (step E90). This BGP session can be established either on the initiative of the device T via its establishment module 3C, or on the initiative of the device T via its establishment module 4C, for example by sending a BGP message OPEN as expected by the BGP protocol.

[0137] It is noted that in this example, the exchange of the autonomous system numbers was initialized by the device T via its means 3. Alternatively, it can be considered that the means 3 of the device T are also activated and that the latter is at the origin of this exchange.

[0138] FIG. 5 illustrates a second embodiment of the invention. In this second embodiment of the invention, the devices T and T are configured as in the example of FIG. 4, each with the autonomous system number with which they are associated (respectively ASN(T)=65500 (step F10) and ASN(T)=65501 (step F20)). It is assumed in the example illustrated in FIG. 5 that the device T does not know the autonomous system number possibly associated with the device T and vice versa.

[0139] For the sake of simplification, it is assumed here that only the means 3 of the device T are activated and only the means 4 of the device T are activated.

[0140] It is assumed that a physical connection is established between the device T and the device T, via their respective communication means 10 in a manner identical to what has been described in step E30 in the first embodiment (step F30).

[0141] The establishment of the physical connection between the device T and the device T is detected by the detection module 3A of the device T (step F40).

[0142] This triggers an exchange with the device T initialized here by the module 3B of the device T.

[0143] More specifically, during this exchange, the device T, via its module 3B, makes an advertisement to the device T of the autonomous system number ASN(T) associated therewith (step F50). In the example illustrated in FIG. 4, this advertisement is made via the sending by the module 3B of the device T (and via the communication means 10 of the device T and the physical connection established with the device T) of a router advertisement RA message to the device T. This RA message comprises, in a field or in an option of the message, the autonomous system number ASN(T).

[0144] Upon receipt of the RA message sent by the device T, the module 4B of the device T extracts the autonomous system number ASN(T) associated with the device T and stores it, for example in its non-volatile memory 7, in association with the device T (step F60).

[0145] Then it responds to the device T by providing it with (making an advertisement of) the autonomous system number ASN(T) associated therewith (step F70). In the example illustrated in FIG. 5, the autonomous system number ASN(T) is provided to the device T in an advertisement RA message, in a field or option of this message.

[0146] Upon receipt of the RA message sent by the device T, the module 3B of the device T extracts the autonomous system number ASN(T) associated with the device T and stores it, for example in its non-volatile memory 7, in association with the device T (step F80). This step of receiving the autonomous system number ASN(T) constitutes a discovery of the autonomous system number associated with the device T within the meaning of the invention.

[0147] Once the exchange of the autonomous system numbers between the devices T and T has ended, a BGP session is automatically established between these two devices, in a manner known per se (step F90). This BGP session can be established either on the initiative of the device T via its establishment module 3C or on the initiative of the device T via its establishment module 4C, for example by sending a BGP message OPEN as provided by the BGP protocol. Steps F50 and F70 can be carried out in any order.

[0148] FIG. 6 illustrates a third embodiment of the invention. In this third embodiment of the invention, only the device T is configured with an autonomous system number ASN(T)=65500 with which it is associated (step G10). This configuration is carried out as in the example of FIG. 4. It is assumed that the device T is not associated with any autonomous system number (a fortiori, the device T is not configured with an autonomous system number associated with the device T). It is also assumed here that only the means 3 of the device T are activated and only the means 4 of the device T are activated.

[0149] It is now assumed that a physical connection is established between the device T and the device T, via their respective communication means 10 in an identical manner to what has been described in step E30 in the first embodiment (step G20).

[0150] The establishment of the physical connection between the device T and the device T is detected by the detection module 3A of the device T (step G30).

[0151] This triggers an exchange with the device T initialized here by the module 3B of the device T.

[0152] More specifically, during this exchange, the device T, via its module 3B, allocates to the device T an autonomous system number noted ASN(T/T) (third autonomous system number within the meaning of the invention) (step G40). This autonomous system number ASN(T/T) is selected by the module 3B of the device T from a predetermined range of values. This range of values was for example provided thereto during its configuration by the administrator of the network R or by the controller 2 or by another device of the network R depending on the way in which the device T was configured. There is no limitation attached to the way in which the module 3B of the device T selects the autonomous system number ASN(T/T) from the range of values at its disposal: this may depend for example on the hierarchical level to which the device T belongs and on policies for allocating autonomous system numbers within the predefined network R, known to the device T, of the cluster to which the device T belongs when appropriate, etc.

[0153] The device T stores in association with the device T the autonomous system number ASN(T/T) that its module 3B has just allocated thereto, for example in its non-volatile memory 7.

[0154] Then, the module 3B of the device T makes an advertisement to the device T (step G50) of: [0155] the autonomous system number ASN(T) associated with the device T; and [0156] the autonomous system number ASN(T/T) it has just allocated to the device T.

[0157] In the example illustrated in FIG. 6, this advertisement is made via the sending by the module 3B of the device T (and via the communication means 10 of the device T and the physical connection established with the device T) of a single router advertisement RA message to the device T. This RA message comprises, in a field or in another option of the message, the autonomous system number ASN(T), and in another field or in another option of the message, the autonomous system number ASN(T/T). Alternatively, two separate messages can be used.

[0158] Upon receipt of the RA message received from the device T, the module 4B of the device T extracts the autonomous system number ASN(T) associated with the device T and stores it, for example in its non-volatile memory 7, in association with the device T (step G60).

[0159] Furthermore, the module 4B of the device T extracts from the RA message the autonomous system number ASN(T/T) that the device T has allocated thereto (step G70). Then it determines whether the device T already has an autonomous system number with which it is associated (G80 test step).

[0160] In the example considered here, it is assumed that the device T does not have an autonomous system number with which it is already associated (response no to the G80 test step). The module 4B of the device T then configures the device T with the autonomous system number ASN(T/T) that the device T has allocated thereto (step G90). This configuration consists in storing, for example in the non-volatile memory 7, the autonomous system number ASN(T/T) allocated by the device T as autonomous system number associated with the device T. A message of acknowledgment or acceptance of the autonomous system number allocated by the device T is sent here to the device T (step G100).

[0161] If, however, the module 4B determines that the device T is already associated with an autonomous system number (response yes to G80 test step), for example with a number ASN(T), the module 4B of the device T rejects the autonomous system number ASN(T/T) allocated by device T and makes an advertisement to the device T of the autonomous system number ASN(T) to which the device T is already attached (fourth autonomous system number within the meaning of the invention). In the example considered in FIG. 6, the rejection of the autonomous system number ASN(T/T) and the advertisement of the autonomous system number ASN(T) are carried out by the module 4B of the device T by means of a single RA message sent by the device T to the device T (step G110).

[0162] Upon receipt of the RA message, the module 3B of the device T extracts the autonomous system number ASN(T) associated with the device T and stores it in its non-volatile memory 7 in association with the device T in replacement of the autonomous system number ASN(T/T) (step G120).

[0163] Once the exchange of the autonomous system numbers between the devices T and T has ended, a BGP session is automatically established between these two devices, in a manner known per se (step G130). This BGP session can be established either on the initiative of the device T via its establishment module 3C or on the initiative of the device T via its establishment module 4C, for example by sending a BGP message OPEN as provided by the BGP protocol.

[0164] It is noted that in the different embodiments described with reference to FIGS. 4, 5 and 6, the advertisements of the autonomous system numbers ASN(T) and when appropriate ASN(T/T), were carried out by the device T by means of an RA message or an RS message. Alternatively, other messages can be used, such as for example messages created specifically for this purpose, or via a BGP session establishment message OPEN such as the one already defined in the BGP protocol, with the addition of fields appropriate in this message.

[0165] In addition, in the embodiments described above, the establishment of a single BGP session between the devices T and T has been considered. The invention also applies in a multi-instance BGP context. More particularly, the invention also allows the automatic establishment of multiple BGP sessions in parallel, whether these sessions use the same AS numbers or use different AS numbers. If different AS numbers are used to establish BGP sessions in parallel, the exchange step implemented according to the invention between the devices T and T then comprises, in the same manner as what has been previously described for a single AS number, the exchange (including the advertisement, the discovery or the allocation) of the different AS numbers necessary for the establishment of these parallel BGP sessions.

[0166] FIGS. 7 and 8 illustrate two examples of application of the invention.

[0167] More specifically, FIG. 7 illustrates a first example of application in which a network comprising four network devices is considered, namely the devices T21 and T22 which belong to a first hierarchical level, and the network devices T31 and T32 which belong to a second hierarchical level.

[0168] It is assumed that the devices T21 and T22 are each configured beforehand with the same autonomous system number ASN(T21)=65000 and ASN(T22)=65000 which is associated therewith. The device T21 is also configured with a range of values in which it can select values of autonomous system numbers to allocate to its neighboring devices. On the other hand, it is assumed that the devices T31 and T32 are not associated with any autonomous system number.

[0169] It is now assumed that the devices T31 and T32 are physically connected to the devices T21 and T22, and that their interfaces of connection to this physical connection are identified by their local link addresses.

[0170] Upon detection of a physical connection established with the device T31, respectively with the device T32, the device T21 allocates an autonomous system number ASN(T31/T21)=65001 to the device T31, respectively ASN(T32/T21)=65002 to the device T32.

[0171] Then it makes an advertisement via an RA message sent to the device T31, respectively to the device T32, of its autonomous system number ASN(T21) and the autonomous system number ASN(T31/T21), respectively ASN(T32/T21), it has just allocated thereto.

[0172] Upon receipt of the RA message, the device T31, respectively the device T32, is configured with the autonomous system number ASN(T31/T21), respectively ASN(T32/T21) allocated by the device T21.

[0173] A BGP session is then established between the device T21 and the device T31, respectively between the device T21 and the device T32, by using the exchanged autonomous system numbers.

[0174] In addition, the device T31, respectively the device T32, makes an advertisement, by means of an RA message, of its autonomous system number ASN(T31/T21), respectively ASN(T32/T21) to the device T22, and vice versa. A BGP session is then established between the device T22 and the device T31, respectively between the device T22 and the device T32, by using the exchanged autonomous system numbers.

[0175] At the end of this procedure, the configuration of the network is as illustrated in FIG. 7B.

[0176] FIG. 8 illustrates a second example of application of the invention in which the addition of two devices T25 and T35 is considered in the network represented in FIG. 1 (for the sake of simplification the controller 2 is not represented in the figure). It is assumed that the AS numbers allocated to the other devices of the network R via the implementation of the invention are those represented in FIG. 8, namely: [0177] 65601 for the devices T11, T12, T13 and T14 belonging to the first hierarchical level; [0178] 64901 for the device T21, 64902 for the device T22, 64903 for the device T23 and 64904 for the device T24 belonging to the second hierarchical level; and [0179] 64601 for the device T31, 64602 for the device T32, 64603 for the device T33 and 64604 for the device T34 belonging to the third hierarchical level.

[0180] The newly added devices T25 and T35 do not have the information necessary to establish BGP sessions with their neighbors, and therefore particularly the autonomous system numbers of their neighbors or their own autonomous system numbers to which they are attached. It is assumed that each of the devices of the network (including the two devices T25 and T35) comply with the invention, and that the device T25 is connected via a physical connection to the devices T11, T12, T13 and T14, and the device T35 is connected via a physical connection to the device T25.

[0181] When the link T11-T25 is activated, a control RA message is emitted by the network device T11 to the device T25 comprising in particular: [0182] the autonomous system number of the device T11 (65601); [0183] an autonomous system number to be used by the device T25 and that the device T11 has allocated thereto, for example 64905; [0184] a cluster size of the lower hierarchical level (e.g. size=1); and [0185] a range of values for the allocation of autonomous system numbers to its neighbors belonging to a lower hierarchical level, for example [64601-64899].

[0186] Upon receipt of this RA message, the network device T25 extracts the above-mentioned elements contained in the message and is configured therewith.

[0187] Then a BGP session is automatically established between the network devices T11 and T25, on the initiative of the network device T11 or of the network device T25 from the autonomous system numbers exchanged and associated respectively with the devices T11 and T25.

[0188] If links with the other network devices of the hierarchical level NIV1 are activated (for example, here with the devices T11, T12, T13 and T14), then the network device T25 can in turn make an advertisement of its autonomous system number and discover the one of its neighbors, via RA and RS messages as described above with reference to FIGS. 4 to 6. BGP sessions are then established automatically with these network devices.

[0189] Concomitantly with these exchanges, the network device T25 allocates, among the range of values communicated thereto by the network device T11, an autonomous system number to the network device T35 of the hierarchical level NIV3 to which it is connected and transmits it with its own autonomous system number in a received RA message to the device T35. Following this message, a BGP session is automatically established between the network devices T25 and T35.

[0190] The new extension of the network R then becomes operational (i.e. the new devices of this network T25 and T35 have the necessary BGP routing information and are visible by the other devices of higher level).

[0191] It is noted that the procedure for automatically configuring the network R can be initialized from any device of the network R, and in particular from any hierarchical level. If a device of the network receives several proposals of instructions for configuring several neighbors due to the near-to-near propagation, it must choose a proposal from those it has received and inform its neighbors, as indicated above with reference to FIG. 6.

[0192] The invention has been described here in the context of a network of a data center. Although having a privileged application in this context, the invention can be applied to any type of network using a dynamic routing protocol, and whatever the adopted policy of allocating the autonomous system numbers in this network.

[0193] In addition, the invention has been described here with reference to the dynamic routing protocol BGP. However, it can also be applied to other routing protocols using autonomous system numbers, such as for example the routing protocol TRIP defined in document IETF RFC 3219. The routing protocol TRIP, in addition to the autonomous system numbers, further uses another identifier called IP Telephony Administrative Domain also under the designation ITAD which can be exchanged between the network devices in the same manner as what has just been described for the autonomous system numbers.