Abstract:
Embodiments which utilize a topology view GUI with elements in each of storage and general network views which indicate the connection to the alternate network via an icon. Properly selecting the icon causes the topology view of the other network to appear. This method allows the connections between the networks to be readily viewed without cluttering either topology and allows quick context changes to occur at the same point.

Description:
BACKGROUND OF THE INVENTION 
       [0001]    1. Field of the Invention 
         [0002]    The invention relates to network management, and particularly to network management using topology views, and more particularly to network management of multiple, connected networks having different protocols using a single network manager with multiple topology views. 
         [0003]    2. Description of the Prior Art 
         [0004]    Computer networks are becoming more complicated with each passing moment. This is due in large part to the increased complexity and capability of the networks. This increased complexity and capability is in turn due to larger number of elements, such as switches and routers, and to the capabilities of each element. 
         [0005]    One area where this is occurring is in the data center. Typically data centers have had two separate networks, one for general networking and one for storage. The general networking was done over Ethernet networks, typically having three layers, edge, aggregation and core, to interconnect individual computers to servers. The storage was done using Fibre Channel (FC) networks, where servers or hosts were connected to storage units. 
         [0006]    Because of the separate nature of the two networks and the different protocols, each has managed independently. Local area network (LAN) administrations would manage the Ethernet network, while storage administrators would manage the FC networks. 
         [0007]    Conventionally the management was done either using a command line interface (CLI) on each device or using a network manager program. The CLI approach had the greatest flexibility and capability but at the expense of a long learning curve. Various graphical user interface (GUI) techniques were also used, primarily either in a tree format or a topology format. The tree format allowed easier access to the individual devices but at the expense of more difficulty in understanding the network as a whole. The topology format excelled at understanding the network as a whole but at the expense of the individual device. 
         [0008]    Recent changes in data center networking have greatly complicated data center network management. The first complication has been the development of the Fibre Channel over Ethernet (FCoE) protocol. This protocol uses FC logic and control methods but over an Ethernet physical layer. A gateway device connects the previously separate Ethernet LAN and the FC SAN (storage area network). FCoE has allowed a much greater number of hosts to have direct access to the SAN storage units. However, management of the Ethernet and FC networks has still been separated, though they are interconnected. 
         [0009]    The second change has been the development of Ethernet fabrics, where multiple paths are developed with an Ethernet physical or L 2  layer, as opposed to the prior single path spanning tree protocol (STP). Now the data center networks can become flatter L 2  networks, doing away with the three-tier structure for peer-to-peer operations on the same layer. 
         [0010]    Combining these two new advances, FCoE and Ethernet fabrics, into a single network has further compounded management problems. FCoE has required combined management of the formally distinct networks for general communications and storage, while Ethernet fabrics have greatly added to the number of devices at one layer on the network. These management problems have stretched the preferred topology view management tools to complexity levels which obscure the networks, obviating the primary advantage of the topology view for management. 
         [0011]    It would be desirable to have a GUI, topology view management technique which addressed the combined networks and large number of devices in one layer in a more intuitive, easy to manage manner. 
       BRIEF SUMMARY OF THE INVENTION 
       [0012]    Embodiments, according to the present invention, utilize a topology view GUI with elements in each of the storage and general network views which indicate the connection to the alternate network via an icon. Properly selecting the icon causes the topology view of the other network to appear. This method allows the connections between the networks to be readily viewed without cluttering either topology and allows quick context changes to occur at the same point. Therefore the topology view remains a useful management tool. 
     
    
     
       BRIEF DESCRIPTION OF THE FIGURES 
         [0013]      FIG. 1  is a block diagram of a network having connected storage and general networking networks and a management network according to the preferred embodiment. 
           [0014]      FIG. 2  is a screenshot of a graphical user interface (GUI) of the storage network of  FIG. 1  according to the preferred embodiment. 
           [0015]      FIG. 3  is a screenshot of the GUI of  FIG. 2  with the storage fabrics expanded according to the preferred embodiment. 
           [0016]      FIG. 4  is a screenshot of a portion of the GUI of  FIG. 3  with a view linkage option illustrated according to the preferred embodiment. 
           [0017]      FIG. 5  is a screenshot of a GUI of the general networking fabric after selecting the view linkage of  FIG. 4  according to the preferred embodiment. 
           [0018]      FIG. 6  is a screenshot of the GUI of  FIG. 5  with a view linkage option illustrated according to the preferred embodiment. 
           [0019]      FIG. 7  is a screenshot of the general networking fabrics GUI with a switch selected and the options illustrated according to the preferred embodiment. 
           [0020]      FIG. 8  is a screenshot of the storage fabrics GUI with a fabric selected and the options illustrated according to the preferred embodiment. 
           [0021]      FIG. 9  is a screenshot of the general networking fabrics GUI with an event log window according to the preferred embodiment. 
           [0022]      FIG. 10  is the screenshot of  FIG. 9  with a log event in the storage fabrics selected and the options illustrated according to the preferred embodiment. 
           [0023]      FIG. 11  is a screenshot of the storage fabrics GUI after selecting the locate option in  FIG. 10  according to the preferred embodiment. 
           [0024]      FIG. 12  is a screenshot if the storage fabrics GUI with a log event in the general networking fabrics selected and the options illustrated according to the preferred embodiment. 
           [0025]      FIG. 13  is a screenshot of the general networking fabrics GUI after selecting the locate option of  FIG. 12  according to the preferred embodiment. 
       
    
    
     DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT 
       [0026]    Referring to  FIG. 1 , an exemplary network  100  for use with the present invention is illustrated. A backbone storage fabric  102  is connected to an edge storage fabric  104  and a general networking fabric  106 . Preferably the storage fabrics  102  and  104  are Fibre Channel (FC) fabrics connected by a router. The general networking fabric  106  is preferably an Ethernet fabric, such as one based on VDX switches from Brocade Communications Systems, Inc., which form an Ethernet fabric as more fully disclosed in U.S. patent application Ser. Nos. 13/098,360, entitled “Converged Network Extension,” filed Apr. 29, 2011; 12/725,249, entitled “Redundant Host Connection in a Routed Network,” filed 16 Mar. 2010;13/087,239, entitled “Virtual Cluster Switching,” filed 14 Apr. 2011; 13/092,724, entitled “Fabric Formation for Virtual Cluster Switching,” filed 22 Apr. 2011; 13/092,580, entitled “Distributed Configuration Management for Virtual Cluster Switching,” filed 22 Apr. 2011; 13/042,259, entitled “Port Profile Management for Virtual Cluster Switching,” filed 07 Mar. 2011; 13/092,460, entitled “Advanced Link Tracking for Virtual Cluster Switching,” filed 22 April 2011; No. 13/092,701, entitled “Virtual Port Grouping for Virtual Cluster Switching,” filed 22 Apr. 2011; 13/092,752, entitled “Name Services for Virtual Cluster Switching,” filed 22 Apr. 2011; 13/092,877, entitled “Traffic Management for Virtual Cluster Switching,” filed 22 Apr. 2011; and 13/092,864, entitled “Method and System for Link Aggregation Across Multiple Switches,” filed 22 Apr. 2011, all hereby incorporated by reference. The backbone fabric  102  is illustrated as having a directly connected storage unit  108  and host  116 , while the edge fabric  104  has attached a storage unit no and hosts  112  and  114 . The general networking fabric  106  has a series of hosts  118 ,  120 ,  122  and  124  connected. The hosts  118 - 124  preferably include FCoE capabilities to access the storage units  108 ,  110 . This is an exemplary network and many other topologies can utilize the present invention, particularly networks having two interconnected, different protocols generally managed by different administrators. 
         [0027]    The backbone fabric  102  is illustrated as being formed by two switches  130 ,  132 , while the edge fabric  104  is formed by one switch  134 . The general networking fabric  106  is illustrated as being formed by two switches  136  and  138 , with one of the switches  136 ,  138  acting as an FCoE gateway. This is a simplified example for purposes of explanation as a normal network will include many more switches in each fabric. Each of these switches  130 - 138  is connected by an Ethernet link to a management LAN  140 . A management station  142  is connected to the management LAN  140  to manage the switches  130 - 138  and thus the backbone fabric  102 , edge fabric  104  and general networking fabric  106 . The management station  142  can be a conventional PC running management software as described below or can be a server in a client-server management environment, with the client PCs connecting to the server to manage the network. The management station  142  includes a processor and non-volatile storage for software executed by the processor. The software causes the processor to manage the network as described herein. In the case of single PC running the software, the software causes the PC to communicate with the various switches and network elements and to provide displays as described below. In the case of a client-server environment, the server software causes the server to communicate with the various switches and network elements to obtain the relevant data. In one embodiment the server software provides web pages or the like to clients executing a browser, the web pages providing the displays and operations. In another embodiment, management software is also executing on the client PCs, with the server acting primarily as a database and the client software accessing the server database to obtain the information then provided on the client PC to produce the displays and operation described below. Therefore the operations described below operate on the appropriate computers and the screenshots are from the computer being operated by the network administrator. 
         [0028]    Referring now to  FIG. 2 , a screenshot  200  of a graphical user interface (GUI) of a management station according to the preferred embodiment is shown. Two primary windows are illustrated, a tree window  202  and a topology window  204 . Above the tree window  202  are tabs to select a dashboard view using a dashboard tab  206 , a storage fabric view using a SAN tab  208  and a general networking view using an IP tab  210 . The tree and topology windows  202  and  204  are illustrating the storage fabrics in  FIG. 2 . The topology window  204  is showing the storage network in fully collapsed format, with icons to represent a general networking fabric  220 , a backbone fabric  222  and an edge fabric  224 . Links are shown connecting the icons  220 ,  222  and  224  to illustrate the interconnection of the fabrics. 
         [0029]      FIG. 3  illustrates the storage network in fully expanded format. The screenshot  300  has the fully expanded tree window  302  and the fully expanded topology window  304 . The backbone fabric  322  is illustrated as including a switch group  330 , to which two hosts  332  and  334  and storage unit  336  are connected. The edge fabric  324  includes a router  344 , switches  340 ,  342  and  346  and an access gateway  348 . A host  350  is connected to switch  340 , while a host  352  and four storage units  354 - 360  are connected to switches  342  and  346 . The general network fabric icon  320  is not expanded as in the preferred embodiment this is a linkage icon, the components being fully displayed in another view, as described below. 
         [0030]    In  FIG. 4 , the network administrator has moved the cursor to the general networking fabric icon  320  and right-clicked the mouse. This causes an option menu to appear. In the illustrated embodiment the only option is an Ethernet Fabrics option. Left clicking or selecting this option results in the screenshot  500  of  FIG. 5  appearing. 
         [0031]      FIG. 5  illustrates the screenshot  500  showing the general networking fabric view with a tree window  502  and a topology window  504 . The topology window  504  illustrates two switches  506  and  508  which form the simplified general networking fabric of the illustrated embodiment. The switch  508  is connected to the backbone fabric icon  510 , which represents the storage network, just as the general networking fabric icon  320  represented to the general networking fabric in the storage network video. 
         [0032]    In  FIG. 6 , the administrator has selected and right-clicked the backbone fabric icon  510 , resulting in the option menu with options including Fabric and Properties. Left clicking on the Fabric option returns the administrator to the screenshot  300  of  FIG. 3 , as this completes the linkage from the general networking topology view. 
         [0033]      FIGS. 7 and 8  illustrate the differences in right-clicking on conventional switches as opposed to the linkage icons as described in  FIGS. 5 and 6 .  FIGS. 7 and 8  show long option menus appearing as appropriate for the particular switch. This illustrates the different meaning applied to the linkage icons. 
         [0034]      FIG. 9  shows screenshot  900 . The illustrated screenshot  900  is of the general networking fabric. Additional windows of an event log window  960  and minimap window  962  are now present. The event log window  960  is a list of the most recent events and system log entries for the monitored devices. In  FIG. 10  the administrator has selected a log entry  1002  related to a switch in the storage fabrics and then right-clicked on the entry to obtain an option menu. One of the options is Locate. Selecting the Locate option causes the screenshot  1100  of  FIG. 11  to appear; which is a storage fabrics view. The relevant device is placed in the center of the topology window  1104 . Thus, selecting the Locate option for a device in the other fabric causes the same screen change as selecting the option on the linkage icons. 
         [0035]      FIG. 12  illustrates the selection of an event from a device in the general networking fabric and the options available. Left-clicking the Locate option causes the general networking view to appear as shown in  FIG. 13 , with the device centered and highlighted. 
         [0036]    The use of linkage icons in the topology views or the Locate option in a log view allows the administrator to move back and forth easily between the available fabrics. The linkage icons are shown properly connected in each topology view, allowed administrators to see the alternate fabric in context of the current fabric, but without overly cluttering the view. This makes it easier to manage the network and yet allows quick access to the other portions of the network. 
         [0037]    While Fibre Channel and Ethernet fabrics have been used as exemplary network protocols, the present invention can be used with other networks and the like, particularly when networks with different protocols are interconnected but yet need to be managed jointly for best results. 
         [0038]    While particular icons have been used to represent the non-viewed network, it is understood that many other icons can be used, though preferably the icons are not the same as used to represent individual devices or groups to allow easier recognition of which icon is a linkage icon. 
         [0039]    While only a single linkage has been shown in each view, it is understood that there could be multiple linkages in each view, to similar protocol networks or to different protocol networks. 
         [0040]    While a right click to provide an option menu and then selection of an item in that option menu has been used to illustrate the linkage to the other network, it is understood that other mechanisms could be used, such as depression of a key and then selection of the linkage icon, and the present invention is not limited to any particular selection method. 
         [0041]    The above specification, examples, and data provide a complete description of the structure and use of exemplary embodiments of the invention. Since many embodiments of the invention can be made without departing from the spirit and scope of the invention, the invention resides in the claims hereinafter appended. Furthermore, structural features of the different embodiments may be combined in yet another embodiment without departing from the recited claims.