Abstract: A Layer 2 network switch is partitionable into a plurality of switch fabrics. The single-chassis switch is partitionable into a plurality of logical switches, each associated with one of the virtual fabrics. The logical switches behave as complete and self-contained switches. A logical switch fabric can span multiple single-chassis switch chassis. Logical switches are connected by inter-switch links that can be either dedicated single-chassis links or logical links. An extended inter-switch link can be used to transport traffic for one or more logical inter-switch links. Physical ports of the chassis are assigned to logical switches and are managed by the logical switch. Legacy switches that are not partitionable into logical switches can serve as transit switches between two logical switches.

Abstract: Copy capability moved into the SAN fabric and provided as a data mover service. A well-known address is utilized to receive copy commands from the hosts. Each switch in the fabric contains a front end or service interface which receives the copy command and manages access control or zoning and LUN mapping. LUN mapping and zoning are based on shared databases. Assuming correct zoning, the service interface will perform any necessary LUN mapping on the received copy command and forward the command to a copy engine to perform the copy operation. The switch service interface also maintains copy operation status, querying the copy engine if necessary, so that any host status requests are also simply handled. Additionally, if multiple copy engines are present, the switches can communicate to perform load balancing.

Abstract: A Layer 2 network switch is partitionable into a plurality of switch fabrics. The single-chassis switch is partitionable into a plurality of logical switches, each associated with one of the virtual fabrics. The logical switches behave as complete and self-contained switches. A logical switch fabric can span multiple single-chassis switch chassis. Logical switches are connected by inter-switch links that can be either dedicated single-chassis links or logical links. An extended inter-switch link can be used to transport traffic for one or more logical inter-switch links. Physical ports of the chassis are assigned to logical switches and are managed by the logical switch. Legacy switches that are not partitionable into logical switches can serve as transit switches between two logical switches.

Abstract: A network of switches that employ Registered State Change Notifications (RSCNs) with enhanced payloads is disclosed. In one embodiment, the network comprises multiple switches coupled together, and multiple node devices each directly-coupled to at least one other switch. Each of the switches preferably provides RSCNs to other switches when a node device state change is detected. One or more of the RSCNs preferably includes a device entry having more than four properties associated with the node device undergoing the state change. The switches receiving the enhanced RSCNs preferably maintain caches of remote node device entries copied from the RSCN device entries. The device entries preferably include one or more of the following: Owner Identifier, Port Type, Port Identifier, Port Name, Node Name, Initial Process Associator, Node IP Address, Class of Service, FC-4 Types, Port IP Address, Fabric Port Name, and Hard Address. Traffic overhead may advantageously be reduced.

Abstract: A method and apparatus for securing networks, focusing on application in Fibre Channel networks. A combination of unique security techniques are combined to provide overall network security. Responsibility for security in the network is assigned to one or more designated entities. The designated entities deploy management information throughout the network to enhance security by modifying the capabilities and operational permissions of the devices participating in the network. For example, through network control: logical management access or physical I/O access may be limited on a per device or per I/O basis; and all devices and ports in the network operate only with other approved devices and ports. These designated entities can better manage network security by exploiting a unique link authentication system as well as a unique push-model secure distributed time service.

Abstract: A network of switches with a distributed name server configuration and caching of remote node device information is disclosed. The network preferably comprises a first switch coupled to a second switch. Each of the switches directly couple to respective node devices. The first switch maintains a name server database about its local node devices, as does the second switch. The second switch further maintains a information cache about remote node devices. The name server preferably notifies other switches of changes to the database, and the cache manager preferably uses the notifications from other switches to maintain the cache. The name server accesses the cache to respond to queries about remote node devices. The cache manager may also aggregate notification messages from other switches when notifying local devices of state changes. Traffic overhead and peak traffic loads may advantageously be reduced.

Abstract: A “high availability” system comprises multiple switches under the control of a control processor (“CP”). The firmware executing on the processor can be changed when desired. Consistent with the high availability nature of the system (i.e., minimal down time), a single CP system implements a firmware change by loading new firmware onto the system, saving state information pertaining to the old firmware, preventing the old firmware from communicating with the switches, bringing the new firmware to an active state and applying the saved state information to the new firmware.

Abstract: A network of switches with a distributed name server configuration and caching of remote node device information is disclosed. The network preferably comprises a first switch coupled to a second switch. Each of the switches directly couple to respective node devices. The first switch maintains a name server database about its local node devices, as does the second switch. The second switch further maintains a information cache about remote node devices. The name server preferably notifies other switches of changes to the database, and the cache manager preferably uses the notifications from other switches to maintain the cache. The name server accesses the cache to respond to queries about remote node devices. The cache manager may also aggregate notification messages from other switches when notifying local devices of state changes. Traffic overhead and peak traffic loads may advantageously be reduced.

Abstract: A network of switches that employ Registered State Change Notifications (RSCNs) with enhanced payloads is disclosed. In one embodiment, the network comprises multiple switches coupled together, and multiple node devices each directly-coupled to at least one other switch. Each of the switches preferably provides RSCNs to other switches when a node device state change is detected. One or more of the RSCNs preferably includes a device entry having more than four properties associated with the node device undergoing the state change. The switches receiving the enhanced RSCNs preferably maintain caches of remote node device entries copied from the RSCN device entries. The device entries preferably include one or more of the following: Owner Identifier, Port Type, Port Identifier, Port Name, Node Name, Initial Process Associator, Node IP Address, Class of Service, FC-4 Types, Port IP Address, Fabric Port Name, and Hard Address. Traffic overhead may advantageously be reduced.

Abstract: Disclosed herein are various aspects of a Fibre Channel (Fibre Channel) fabric having switches that employ Registered State Change Notifications (RSCNs) with enhanced payloads. Two types of RSCN message formats are provided, both including status information about the affected device(s). In one embodiment, a RSCN message format for inter-switch communication provides various information about the affected devices according to one of a plurality of predetermined formats. In another embodiment, a node device RSCN message format provides information about a port state, the identification of the affected port, along with the port and node world wide names and the FC-4 types supported by the node.

Abstract: An port expander Fibre Channel switch presents F_ports to form a first Fibre Channel fabric and N_ports to a second Fibre Channel fabric to appear as node devices. The port expander may be used to connect a plurality of blade servers to a Fibre Channel fabric. Fabric events engendered by the insertion or removal of hot-pluggable devices are handled by the port expander and “event storms” on the Fibre Channel fabric are avoided. The port expander presents the blade servers to the FC fabric as a virtualized N_port.

Abstract: An isolation switch blade Fibre Channel switch presents F_ports to form a first Fibre Channel fabric and N_ports to a second Fibre Channel fabric to appear as node devices. The isolation switch blade may be used to connect a plurality of blade servers to a Fibre Channel fabric. Fabric events engendered by the insertion or removal of hot-pluggable devices are handled by the isolation switch blade and “event storms” on the Fibre Channel fabric are avoided. The isolation switch blade presents the blade servers to the FC fabric as a virtualized N_port.

Abstract: A network of switches with a distributed name server configuration and caching of remote node device information is disclosed. The network preferably comprises a first switch coupled to a second switch. Each of the switches directly couple to respective node devices. The first switch maintains a name server database about its local node devices, as does the second switch. The second switch further maintains a information cache about remote node devices. The name server preferably notifies other switches of changes to the database, and the cache manager preferably uses the notifications from other switches to maintain the cache. The name server accesses the cache to respond to queries about remote node devices. The cache manager may also aggregate notification messages from other switches when notifying local devices of state changes. Traffic overhead and peak traffic loads may advantageously be reduced.

Abstract: An isolation switch blade Fibre Channel switch presents F_ports to form a first Fibre Channel fabric and N_ports to a second Fibre Channel fabric to appear as node devices. The isolation switch blade may be used to connect a plurality of blade servers to a Fibre Channel fabric. Fabric events engendered by the insertion or removal of hot-pluggable devices are handled by the isolation switch blade and “event storms” on the Fibre Channel fabric are avoided. The isolation switch blade presents the blade servers to the FC fabric as a virtualized N_port.

Abstract: Systems particularly a virtualization switch or a storage device, which include virtual ports connected to virtual devices with virtual worldwide names and virtual LUNs. Because Fibre Channel environment hosts can track worldwide names from one port to another and allow continuity in that regard, the virtual worldwide names are provided with relevant virtual LUNs and connected these to virtual ports so that the virtual devices can be moved as desired to overcome failures or to allow load balancing.

Abstract: An isolation switch blade Fiber Channel switch presents F_ports to form a first Fiber Channel fabric and N_ports to a second Fiber Channel fabric to appear as node devices. The isolation switch blade may be used to connect a plurality of blade servers to a Fiber Channel fabric. Fabric events engendered by the insertion or removal of hot-pluggable devices are handled by the isolation switch blade and “event storms” on the Fiber Channel fabric are avoided. The isolation switch blade presents the blade servers to the FC fabric as a virtualized N_port.

Abstract: Embodiments according to the invention relate to frame redirection, which includes methods to intercept and re-route traffic between an initiator and a target. When a frame is redirected, an initiator issues a frame to the target, but the frame is received by a virtual target in a redirection switch by allowing the redirection switch to use the WWN of the actual target. From the perspective of the initiator, the target resides on the redirection switch. From the redirection switch, the frame is sent to the actual target by allowing the redirection switch to use the identity of the initiator. In other words, the redirection switch presents the WWN of the initiator to the target when the redirected frame is sent to the target. From the perspective of the target, the frame is received as if it originated at the initiator.

Abstract: An isolation switch blade Fibre Channel switch presents F_ports to form a first Fibre Channel fabric and N_ports to a second Fibre Channel fabric to appear as node devices. The isolation switch blade may be used to connect a plurality of blade servers to a Fibre Channel fabric. Fabric events engendered by the insertion or removal of hot-pluggable devices are handled by the isolation switch blade and “event storms” on the Fibre Channel fabric are avoided. The isolation switch blade presents the blade servers to the FC fabric as a virtualized N_port.

Abstract: Managing cluster membership and providing and managing locks in the switches forming the interconnecting network. To manage the cluster membership, a zone is created, with indicated members existing in the zone and the zone being managed by the switches. The nodes communicate their membership events, such as alive messages, using an API to work with the switch to which they are attached. The desired membership algorithm is executed by the switches, preferably in a distributed manner. Each switch then enforces the membership policies, including preventing operations from evicted nodes. This greatly simplifies the programs used on the nodes and unburdens them from many time consuming tasks, thus providing improved cluster performance. In a like manner, the switches in the fabric manage the resource locks. The nodes send their lock requests, such as creation and ownership requests, to the switch to which they are connected using an API.

Abstract: A Layer 2 network switch is partitionable into a plurality of switch fabrics. The single-chassis switch is partitionable into a plurality of logical switches, each associated with one of the virtual fabrics. The logical switches behave as complete and self-contained switches. A logical switch fabric can span multiple single-chassis switch chassis. Logical switches are connected by inter-switch links that can be either dedicated single-chassis links or logical links. An extended inter-switch link can be used to transport traffic for one or more logical inter-switch links. Physical ports of the chassis are assigned to logical switches and are managed by the logical switch. Legacy switches that are not partitionable into logical switches can serve as transit switches between two logical switches.