Patent application number | Description | Published |
20080314979 | CABLE MANAGEMENT SYSTEMS - In order to monitoring connectivity of cabling in a system comprising chassis components and cables interconnecting the chassis components, machine readable labels are applied to cable connectors and chassis component connectors, the machine readable labels on a cable connector and a chassis component to which the cable connector is connected are scanned, and the scanned connectivity information is recorded. | 12-25-2008 |
20080315889 | FAULT ISOLATION IN INTERCONNECT SYSTEMS - A loopback connector for a system can include a connector arrangement connectable to connector of a system component and/or a cable. The loopback connector can include loopback logic for simulating cable and/or system component functionality. In an example implementation the loopback connector can also operate to protect a system component and/or cable connector during shipping. | 12-25-2008 |
20080315985 | MULTI-SWITCH CHASSIS - In a switch system L groups of the line switch elements are connectable to cables that include L links such that each of the L links within a cable connect to a switch element of a respective one of the L groups. Fabric switch elements are connected such that a fabric switch element is connected to the line switch elements of one of the group of line switch elements. | 12-25-2008 |
20080318465 | CABLE INTERCONNECT SYSTEMS - In order to monitor connectivity status associated with an interconnect cable from the end-points to which either end of the cable is attached, a storage device storing a field replaceable unit identifier is provided to uniquely identify a cable end-point, which identifier can then be accessed to determine the connectivity status. | 12-25-2008 |
20080320117 | CLUSTER SYSTEM MANAGEMENT - In a system having a cluster of system components interconnected by a cluster interconnect fabric, the system components include out-of-band management network interfaces to an out-of-band management network. The system is configured to use the cluster interconnect fabric and the out-of-band management network interfaces to determine the overall connectivity and status of the cluster. | 12-25-2008 |
20100232448 | Scalable Interface for Connecting Multiple Computer Systems Which Performs Parallel MPI Header Matching - An interface device for a compute node in a computer cluster which performs Message Passing Interface (MPI) header matching using parallel matching units. The interface device comprises a memory that stores posted receive queues and unexpected queues. The posted receive queues store receive requests from a process executing on the compute node. The unexpected queues store headers of send requests (e.g., from other compute nodes) that do not have a matching receive request in the posted receive queues. The interface device also comprises a plurality of hardware pipelined matcher units. The matcher units perform header matching to determine if a header in the send request matches any headers in any of the plurality of posted receive queues. Matcher units perform the header matching in parallel. In other words, the plural matching units are configured to search the memory concurrently to perform header matching. | 09-16-2010 |
20100332612 | Caching Data in a Cluster Computing System Which Avoids False-Sharing Conflicts - Managing operations in a first compute node of a multi-computer system. A remote write may be received to a first address of a remote compute node. A first data structure entry may be created in a data structure, which may include the first address and status information indicating that the remote write has been received. Upon determining that the local cache of the first compute node has been updated with the remote write, the remote write may be issued to the remote compute node. Accordingly, the first data structure entry may be released upon completion of the remote write. | 12-30-2010 |
20100332908 | Performing Remote Loads and Stores over Networks - A network adaptor which performs CPU loads and stores to remote memory over network fabrics. The network adaptor receives a transfer request from a compute node and converts the request to a remote transfer request, which is transmitted to the network. The network adaptor then monitors the network connection for a remote completion response. When the network adaptor receives the remote completion response within a specific time period, the network adaptor transmits a first completion response to the compute node. If the network adaptor does not receive the remote completion response within the specific time period, the network adaptor transmits an “early completion response” to the compute node. The network adaptor continues to monitor for the actual response. This allows the compute node to continue processing without having to wait for the actual response to be received. The method handles small payloads efficiently and also accounts for long completion delays. | 12-30-2010 |
20110173396 | Performing High Granularity Prefetch from Remote Memory into a Cache on a Device without Change in Address - Provided is a method, which may be performed on a computer, for prefetching data over an interface. The method may include receiving a first data prefetch request for first data of a first data size stored at a first physical address corresponding to a first virtual address. The first data prefetch request may include second data specifying the first virtual address and third data specifying the first data size. The first virtual address and the first data size may define a first virtual address range. The method may also include converting the first data prefetch request into a first data retrieval request. To convert the first data prefetch request into a first data retrieval request the first virtual address specified by the second data may be translated into the first physical address. The method may further include issuing the first data retrieval request at the interface, receiving the first data at the interface and storing at least a portion of the received first data in a cache. Storing may include setting each of one or more cache tags associated with the at least a portion of the received first data to correspond to the first physical address. | 07-14-2011 |
20120069730 | SYSTEM AND METHOD FOR SUPPORTING MANAGEMENT NETWORK INTERFACE CARD PORT FAILOVER IN A MIDDLEWARE MACHINE ENVIRONMENT - A system and method can support virtual network interface card (NIC) failover in a middleware machine environment. The middleware machine environment includes a local management node and a remote management node. The system provides a local NIC driver and a remote proxy instance on a local management node. The remote proxy instance can associate a machine address with a remote NIC driver on a remote management node that is connected with the local remote management node in a subnet. Furthermore, the remote proxy instance operates to direct packets to and from the remote NIC driver using the machine address. | 03-22-2012 |
20120072562 | PERFORMING PARTIAL SUBNET INITIALIZATION IN A MIDDLEWARE MACHINE ENVIRONMENT - A system and method can perform subnet initialization in a middleware machine environment. In accordance with one embodiment, a plurality of management nodes in the middleware machine environment can be interconnected so that a plurality of subnet managers that are associated with the plurality of management nodes can communicate with each other using an in-band communication protocol. The plurality of subnet managers can negotiate and elect a master subnet manager, which operates to configure and manage the middleware machine environment. The master subnet manager can replicate one or more subnet initialization policies to other subnet managers in the middleware machine environment using the in-band communication protocol. The master subnet manager can then set up a plurality of client nodes in the middleware machine environment based on the one or more subnet initialization policies. | 03-22-2012 |
20120072563 | SYSTEM AND METHOD FOR SUPPORTING WELL DEFINED SUBNET TOPOLOGY IN A MIDDLEWARE MACHINE ENVIRONMENT - A system and method can support a middleware machine environment. The middleware machine environment can include a subnet manager and a plurality of fabric components, wherein each said fabric component is associated with a subnet management agent (SMA). The subnet manager maintains a topology graph that indicates how ports are connected in the subnet. The subnet manager operates to periodically reevaluate one or more states associated with each fabric component in the subnet by determining whether each SMA is responding correctly to a request. | 03-22-2012 |
20120072564 | SYSTEM AND METHOD FOR PROVIDING ETHERNET OVER INFINIBAND VIRTUAL HUB SCALABILITY IN A MIDDLEWARE MACHINE ENVIRONMENT - A system and method can support a middleware machine environment that include one or more gateway nodes. One or more gateways that resides on the one or more gateway nodes are provided in a subnet with a plurality of host servers, wherein each host server is associated with one or more virtual network interface cards (vNICs). The middleware machine environment also include a plurality of virtual hubs (vHUB) on the one or more gateways, with each vHUB associated with one or more said vNICs. The gateways are adapted to connect with an external network, and operate to forward a multicast packet to both the external network and the plurality of host servers via the plurality of vHUBs, and prevent multicast packet traffic loops between the subnet and the external network. | 03-22-2012 |
20120079090 | STATEFUL SUBNET MANAGER FAILOVER IN A MIDDLEWARE MACHINE ENVIRONMENT - A system and method can provide stateful subnet manager failover in a middleware machine environment. The system includes a policy daemon associated with each master subnet manager candidate in a subnet in the middleware machine environment. The policy daemon manages one or more policies for the subnet. The system also includes a transactional interface associated with the policy daemon co-located with a current master subnet manager. The transactional interface allows for updating the one or more policies using a policy update transaction. The policy daemon co-located with the master subnet manager operates to replicate the policy update transaction to one or more policy daemons co-located with the subnet managers that are master candidates associated with the master subnet manager, before committing the policy update transaction. Additionally, when the master subnet manager fails, the subnet managers operate to negotiate with each other and elect a new master subnet manager. | 03-29-2012 |
20120079580 | SYSTEM AND METHOD FOR FACILITATING PROTECTION AGAINST RUN-AWAY SUBNET MANAGER INSTANCES IN A MIDDLEWARE MACHINE ENVIRONMENT - A system and method can support a middleware machine environment that includes a set of subnet manager instances, which reside on one or more nodes in the middleware machine environment and cooperate to provide a highly available subnet manager service within a subnet, wherein each said subnet manager instance is associated with a different private secure key. The subnet manager instances can negotiate with each other and elect a master subnet manager responsible for configuring and managing the middleware machine environment using the private secure key associated with the master subnet manager. The subnet can be reconfigured to be associated with a different private secure key, when a new subnet manager instance is elected as the master subnet manager. An old master subnet manager can be automatically prevented from resuming normal operations as the master subnet manager, in order to avoid undesired consequence such as a “split brain” scenario. | 03-29-2012 |
20120307682 | SYSTEM AND METHOD FOR SUPPORTING SUB-SUBNET IN AN INFINIBAND (IB) NETWORK - A system and method can support multiple domains in an InfiniBand (IB) fabric. The IB fabric can include one or more subnets, wherein each said subnet contains one or more switch nodes. Additionally, at least one said subnet can be divided into one or more sub-subnets, wherein each said sub-subnet is managed by a separate sub-subnet manager that is associated with a unique management key, and wherein said one or more sub-subnets are connected by one or more sub-subnet gateway switch nodes, wherein each sub-subnet gateway switch node belongs to one sub-subnet. | 12-06-2012 |
20120311123 | SYSTEM AND METHOD FOR SUPPORTING CONSISTENT HANDLING OF INTERNAL ID SPACES FOR DIFFERENT PARTITIONS IN AN INFINIBAND (IB) NETWORK - A system and method can support consistent handling of internal ID space for different partitions in an InfiniBand (IB) network. A plurality of partitions can be provided for a subnet with a plurality of hosts, wherein each partition of the subnet includes one or more hosts and each host can be associated with one or more physical HCA instances. Each partition in the subnet can be associated with a separate internal ID space, and a single physical HCA instance is prevented from being shared by different tenants that use a same internal ID value in different partitions. | 12-06-2012 |
20120311670 | SYSTEM AND METHOD FOR PROVIDING SOURCE ID SPOOF PROTECTION IN AN INFINIBAND (IB) NETWORK - A system and method can provide source ID spoof protection in an InfiniBand (IB) fabric. The IB fabric can support a plurality of tenants in a subnet that connects a plurality of physical servers, wherein the plurality of tenants are associated with different partitions in the subnet. Then, the plurality of tenants can use at least one shared service, and the IB fabric can be configured to determine what ID values are legal for different physical servers and different partitions. | 12-06-2012 |
20120311682 | SYSTEM AND METHOD FOR PROVIDING RESTRICTIONS ON THE LOCATION OF PEER SUBNET MANAGER (SM) INSTANCES IN AN INFINIBAND (IB) NETWORK - A system and method can provide subnet manager (SM) restrictions in an InfiniBand (IB) network. A first SM in a subnet in the IB network operates to determine whether a second SM associated with a remote port is trustworthy. Furthermore, the first SM is allowed to send at least one of a request and a response that contains a management key to the second SM, if the first SM determines that the second SM is trustworthy. Additionally, the first SM is prevented from attempting to initiate communication with the second SM, if otherwise. | 12-06-2012 |