Assisted port identification

BACKGROUND

Field of the Disclosure.

0001This disclosure relates generally to cloud or virtualized computing and the use of generic computers or "servers."

0002In software-centric applications, it is desirable to be able to use a wide variety of servers. These generic servers are often referred to as commercial off-the-shelf or COTS server.

0003One drawback of COTS devices is there is no defined or predictable relationship between the server's physical Ethernet ports and the internal representation. The leftmost physical port on one COTS server might be externally represented as "Port 1" and internally represented as "eth1." On another server, the leftmost "Port 1" might be internally represented as "eth3." A user may add cards to the device to add additional physical ports. Thus there may be two or more clusters of physical ports and the role of the physical ports may not be readily apparent from viewing the external surfaces of the physical device. A device with more physical ports than required for the current use may not remove and replace a malfunctioning physical port but may simply change the operation to ignore the malfunctioning physical port.

0004This variability complicates installation and operation of software on a variety of devices. The hosted software must have some mapping of external physical ports to internal virtual ports. The problem lies in how to determine this mapping in an efficient manner.

0005One approach would be for the system operator ("user") to manually determine the mapping of ports. Typically this approach requires the user to research the Linux interface name usage and how it relates to the physical ports on a given server. An alternative would be to resort to a trial and error process to define this mapping by connecting the various communication cables to various physical ports and hoping that the guessed mapping works.

0006In either case, those approaches are a time consuming and error prone process, especially with inexperienced users or new server hardware. In addition, the mapping may not be as simple at eth0, eth1, eth2, eth3 maps to ports 1, 2, 3, 4.

0007Here is a real world example of a COTS server running a Linux operating system. <figref idref="f0001"><b>FIG. 1</b></figref> displays the example hardware configuration. In this case there are four Ethernet ports arranged with two rows of two ports. In this example, the bottom row of ports is assigned to a numerically lower PCI address than the top row of ports. (For sake of context, PCI is the Peripheral Computer Interconnect and is a local computer bus for attaching hardware to a computer). As a result, the set of Linux Ethernet interface names 104 on the bottom row with eth0 and eth1 and the top row containing interface eth2 and eth3. However, the physical faceplate presents the set of external port names 108 visible to the user starting on the upper row as port 0.1 and 0.2 followed by the lower port names of 0.3 and 0.4. Therefore, the mapping of external port name 108 to internal Ethernet interface 104 would not be a straightforward mapping of numerically increasing port name to interface name.

0008An explicit mapping is required between the physical port names and the logical port names. An example of this mapping is shown in <figref idref="f0001"><b>FIG. 2</b></figref><b>.</b>

0009Note while the physical port names are provided in this example as physical ports 0.1, 0.2, 0.3, and 0.4, the physical port names may be A, B, C, D or WAN, LAN 1, LAN 2, LAN 3, and AUX as the four ports may be used to connect to a Wide Area Network, several local area networks, and to an external memory device.

0010One prior art method for locating the physical port location is through the use of a Linux tool named "ethtool." <b>(see - https://en.wikipedia.org/wiki/Ethtool)</b> This tool contains an "identify" option to trigger the LEDs on the Ethernet port to blink for a given Ethernet interface. In this case, a user would run the ethtool utility specifying the Linux Ethernet interface name along with the "identify" option. Often this results in a blinking LED on the physical port that one can use to map the internal Linux Ethernet interface to the physical port. A problem with this approach is that not all hardware vendors support this functionality, resulting in no blinking LED. In addition, using ethtool requires access to a Linux command line at a privileged level along with some basic Linux knowledge.

0011<nplcit id="ncit0001" npl-type="s"><text>Jayson Broughton article "Fun with ethtool" from Linux Journal 25 May 2011</text></nplcit> teaches a way to make a particular network card within a server blink at the back of the Ethernet adaptor for a period of time. This request to blink can be used to map network card to a particular Ethernet value.

SUMMARY OF THE DISCLOSURE

0012There is provided a method to associate a set of physical ports on a device with a set of software virtual interfaces according to claim 1 and a physical device according to claim 12. Further aspects related to the claimed invention are set out in the dependent claims.

0013This summary is meant to provide an introduction to the concepts that are disclosed within the specification without being an exhaustive list of the many teachings and variations upon those teachings that are provided in the extended discussion within this disclosure. Thus, the contents of this summary should not be used to limit the scope of the claims that follow.

0014Inventive concepts are illustrated in a series of examples, some examples showing more than one inventive concept. Individual inventive concepts can be implemented without implementing all details provided in a particular example. It is not necessary to provide examples of every possible combination of the inventive concepts provide below as one of skill in the art will recognize that inventive concepts illustrated in various examples can be combined together in order to address a specific application.

0015Other systems, methods, features and advantages of the disclosed teachings will be immediately apparent or will become apparent to one with skill in the art upon examination of the following figures and detailed description.

BRIEF DESCRIPTION OF THE FIGURES

0016The disclosure can be better understood with reference to the following figures. The components in the figures are not necessarily to scale, emphasis instead being placed upon illustrating the principles of the disclosure. Moreover, in the figures, like reference numerals designate corresponding parts throughout the different views. <ul id="ul0001" list-style="none" compact="compact"><li><figref idref="f0001"><b>FIG. 1</b></figref> depicts the Linux assignment of interfaces versus the labels on the external faceplate.</li><li><figref idref="f0001"><b>FIG. 2</b></figref> depicts a table that maps between the physical port name and the Linux name for the interface.</li><li><figref idref="f0001"><b>FIG. 3</b></figref> depicts a fiber optic loopback connector plug.</li><li><figref idref="f0002"><b>FIG. 4</b></figref> depicts an Ethernet loopback connector plug.</li><li><figref idref="f0003"><b>FIG. 5</b></figref> depicts a detailed flow chart for port identification.</li><li><figref idref="f0004"><b>FIG. 6</b></figref> provides a high level representation of a physical device loaded with software that includes instructions to implement the teachings of the present disclosure.</li></ul>

DETAILED DESCRIPTION

0017The presently disclosed subject matter is described with specificity to meet statutory requirements. However, the description itself is not intended to limit the scope of this patent. Rather, the inventors have contemplated that the claimed subject matter might also be embodied in other ways, to include different steps or elements similar to the ones described in this document, in conjunction with other present or future technologies. Moreover, although the term "step" may be used herein to connote different aspects of methods employed, the term should not be interpreted as implying any particular order among or between various steps herein disclosed unless and except when the order of individual steps is explicitly described.

0018The present disclosure describes a method for simplified identification and mapping of physical network port names to a Linux Ethernet interfaces or other software virtual interfaces by using an external activation device, being either a connection to an active Ethernet network element or a passive loopback connector.

0019One advantage of the present disclosure over the ethtool solution is that the interface identification and mapping is performed automatically when an activation device is inserted into a network port by an unskilled user. No knowledge of Linux is required, and there is no dependence on the operation of set of LEDs on a given server.

0020While the activation device could be a connection to an active Ethernet network element, it is convenient to have a small loopback connector for use with this process as the activation device. The loopback connector is any device that connects the transmit connections directly to the receive connections on the Ethernet port.

0021For fiber, this is a simple loop of fiber from transmit to receive as shown in loopback connector 150 in <figref idref="f0001"><b>FIG. 3</b></figref><b>.</b> For metallic Ethernet, this is a connection between transmit and receive for each paired signal as shown in the wiring diagram for loopback connector 160 in <figref idref="f0002"><b>FIG. 4</b></figref><b>.</b> Loopback connector 160 is appropriate for an RJ-45 port. Loopback tools are known in the art and are sometimes used as an aid in testing physical connection problems.

0022The teachings of the present disclosure could be adapted for other physical ports beyond a fiber optic port or a FJ-45 port as long as the transmit connections are connected to the receive connections in order to cause the state change from link down to link up as used in the disclosed method.

Overview of the Process.

0023The present disclosure takes advantage of the Ethernet link state that is reported as "up" when an activation device is connected to the physical network port. A user is requested by a screen prompt issued by the device set-up software to insert the activation device into the port they would like to define as a particular physical port and once the activation device is connected, the assisted port identification process creates the mapping between that particular physical port and the Linux interface that is identified as reporting a link up state. The name of the particular physical port may be rather generic such as Port 1 or may be specific to the application such as WAN, LAN-1, or Memory.

0024The user is then instructed to insert the activation device into the next port and this process continues until all physical network ports are mapped to a set of Linux Ethernet interfaces. This method greatly simplifies defining the mapping of physical network ports to Linux interfaces by taking advantage of the link up state and does not depend on hardware that supports manual blinking of the LEDs at the physical ports.

Process Details.

0025The process starts by first enabling all Linux Ethernet interfaces which puts each interface into a state where the link state is reported as down, but if an activation device is connected, then the link state will transition to link up.

0026Once all interfaces are enabled, the user is prompted to connect the activation device to what the user considers to be port 1 or whatever is the first port name to be identified such as WAN. Thus a particular company could have port 1 as the upper left port, the lower left port, or some other port based upon client preference. After the user acknowledges that the activation device is connected, each Ethernet interface is scanned to discover the particular Linux Ethernet interface that is now reporting link up. The mapping between the Linux Ethernet interface to the port name being prompted can now be stored for future use.

0027Finally, the user is prompted to disconnect the activation device and then connect the activation device into the next port to be discovered. This process continues until all ports and Linux Ethernet interfaces are mapped.

<u>FIG. 5.</u>

0028A more detailed description of the process 1000 used to map the physical network port to the Linux Ethernet interface including additional validations is shown in the <figref idref="f0003"><b>FIG. 5</b></figref><b>.</b>

0029A description of the detailed process is described in the following steps: Step 1004-Start.

0030Step 1008-Enable all Ethernet interfaces on the hardware requiring identification. This puts the interface in a mode where the link state is reported as down when no activation device is present, but will switch to link up when an activation device is connected.

0031Step 1012-Scan all Ethernet interfaces in attempt to locate any ports that are already in a link up state.

0032Branch 1016 <ul id="ul0002" list-style="none" compact="compact"><li>If any interface is already in a link up state, process cannot proceed as the activation device for port identification has not yet been inserted, so there must be something else already connected. Communicate message 1020 to remind user that all activation devices connections to the ports to be identified must be removed before starting. Then go to end 1096 to await a new start.</li><li>If all ports are in link down state, the process can proceed to step 1030.</li></ul>

0033Step 1030-set port value to a first specified value. This may be port 1 or otherwise start at the beginning of the set of ports to be identified such as WAN.

0034Step 1034-Request the user to connect an activation device to the physical port that the user associates with the current specified port name in the list of physical ports.

0035Step 1038-Scan all Ethernet interfaces in attempt to locate any ports that are now in a link up state.

0036Branch 1042: <ul id="ul0003" list-style="none" compact="compact"><li>If no interface is in a link up state, the scan was unable to locate a port with an activation device connected. This indicates a problem with the port or an activation device was not correctly connected or the connected activation device is not functional. Therefore, the process cannot proceed without first connecting a functioning activation device to a physical port. Provide a message 1050 to the user to connect a functioning activation device and return to step 1034. One of skill in the art will recognize that the return could be to step 1038 as an alternative.</li><li>If more than one interface is in a link up state, the process cannot proceed as only one activation device should be inserted. The user must remove the additional activation device to proceed. Provide a message 1046 and return to step 1034.</li><li>If a single Ethernet interface is in a link up state, then a single port mapping is identified and further validation occurs at branch 1064.</li></ul>

0037Branch 1064: <ul id="ul0004" list-style="none" compact="compact"><li>If the Ethernet interface that is reporting link up is already assigned to another physical port name, then the process cannot continue as two physical port names cannot be assigned to a single Linux interface. This situation could happen if the user connects the activation device to a previously assigned physical port. The user must connect the activation device with another physical port before proceeding. Proceed to Step 1060 to notify user and then return to step 1034.</li><li>If the interface that is reporting link up is not currently assigned to another physical port name, then the particular physical port selected by the user by connecting the activation device is mapped to the Linux Ethernet interface that is reporting the link up state. The process can proceed to step 1068.</li></ul>

0038Step 1068-Associate the current physical port with the connected activation device to the Linux Ethernet interface with the new link up status.

0039Step 1072-Request User disconnect the activation device from the port just associated with a particular Linux Ethernet interface.

0040Step 1076-Increment the port value N by 1 or otherwise advance in the list of port names.

0041Branch 1080: <ul id="ul0005" list-style="none" compact="compact"><li>If the incremented port value exceeds the set of ports to be associated with Linux Ethernet interfaces to be associated with physical ports, then go to end 1096.</li><li>Otherwise, go to step 1034 and continue the process of identifying another physical port to associate with another particular Linux Ethernet interface.</li></ul>

0042One of skill in the art will recognize that the looping to check for completion of the process to associate all physical ports to virtual ports could be performed before incrementing the port name.

0043<figref idref="f0004"><b>FIG. 6</b></figref> provides a high level representation of a physical device 200 loaded with software that includes instructions to implement the teachings of the present disclosure. A physical device 200 having at least one processor 204 executes instructions stored in memory 208. The instructions are sufficient to implement the teachings of this disclosure or to allow access to additional instructions via one or more communication links (not shown here).

0044The physical device 200 has at least one user interface device 212 suitable to interact and to provide instructions to the user to allow the user to interact with the device to implement the process of associating a set of physical ports (284, 288, 292, and 296) to a corresponding set of software virtual interfaces created and maintained by instructions used by the processor. Note - nothing in this disclosure should be interpreted as limiting the number of physical ports to precisely four ports as the teachings of the present disclosure would be of use whenever there is more than one physical port. The components within device 200 may communicate with other components via one or more communication buses 250.

0045One of skill in the art will recognize that <figref idref="f0004"><b>FIG. 6</b></figref> omits many components found within a physical device 200 such as a power supply. However, <figref idref="f0004"><b>FIG. 6</b></figref> meets or exceeds the obligation of an applicant to furnish a drawing set in a nonprovisional application that shows every feature of the invention specified in the claims (37 CFR §1.83).

ALTERNATIVES AND VARIATIONS.

Change in Physical Ports.

0046If the port mapping needs to be updated for any reason including the addition or removal of physical ports, the process is capable of running multiple times to allow for updates to the port map.

Verification of Port Function.

0047Once all of the port mappings are defined, the process is also capable of establishing a connection to known addresses to further verify connectivity. For example, an interface that is now mapped to a WAN port could attempt to communicate with a remote IP address that is only accessible through a WAN connection.

0048Another possibility would be to use the functionality of the remote IP address to determine the function of the port. The learned association would then be between a physical port and the function of the remote end of the connection.

Not Limited to Linux.

0049In order to avoid a fuzzy disclosure, specific examples were provided which referenced the use of Linux or Linux tools. While the teachings of the present disclosure may be used in a Linux environment, Linux is not a requirement. Any other environment where software may be loaded onto a physical device with at least two physical ports could benefit from the teachings of the present disclosure. One such example is Microsoft Windows.

Use of More than One Activation Device.

0050In many instances, the process will use a single activation device such as a single loopback device, and simply move that single activation device from the first physical port to be associated with a software virtual interface through the sequence of physical ports and software virtual interfaces. Thus, at any given time there is either zero activation devices connected to the array of physical ports or just one activation device connected to the array of physical ports. While this may be the most common implementation, it is not a requirement.

0051The process could sequentially add a new loopback device or other activation device to each new physical port to be associated with a software virtual interface and detecting the new state change from down to up. Thus the final physical port could be identified by connecting an Nth activation device to the array of physical ports while leaving connected N-1 previously connected activation devices.

Assumptions About the Last Physical Port.

0052One of skill in the art will recognize that if N physical ports need to be associated with N software virtual interfaces that after successfully associated the N-1 physical port to the N-1 software virtual interface that the remaining physical port could be assumed to be the physical port to associate with the remaining software virtual interface.

0053One of skill in the art will recognize that some of the alternative implementations set forth above are not universally mutually exclusive and that in some cases additional implementations can be created that employ aspects of two or more of the variations described above. Likewise, the present disclosure is not limited to the specific examples or particular embodiments provided to promote understanding of the various teachings of the present disclosure.