International Business Machines Corporation

Extreme Networks, Inc.

Rajeev Kumar Mishra

Lance Warren Russell

Eric Philip Fried

Suresh Sabarathinam

Murali Vaddagiri

Arunachalam Ganapathy

Trishali Satish Nayar

David Jones Craft

Mark D Rogers

Perinkulam I Ganesh

Ranadip Das

Vijayasekhar Mekala

Cheryl L Jennings

Sandeep R Patil

Vinit Jain

David Alan Hepkin

Sivakumar Krishnasamy

Stephen J Tovcimak

Shevaun M Fontenot

Krishnan Uma

Satish Narayan Kharat

Ravi Shankar

Grover Herbert Neuman

Chris Alan Schwendiman

Jeelan Basha Poola

Stephen M Tee

Senthilraj Shanmugavadivel

Edward Shvartsman

Manjunath A Pattanshetti

Dominic Velikakath Peter

Cheryl L Hall

Konagalli N Rajesh

Vijaya S Mekala

Access point cloud controller auto-discovery is provided. An access point, in communication with other access points, receives data indicative of whether each of other access points are managed using a cloud controller or a local controller. When the data is indicative that at least one of the other access points is managed using the cloud controller, the access point is configured to be cloud-controller-managed. When the data is indicative that none of the other access points is managed using the cloud controller, and when the data is further indicative that at least one of the other access points is managed using the local controller, the access point is configured to be local-controller-managed.

Access point cloud controller auto-discovery

A gossiping scheme for sharing node status in a cluster of nodes provides a robust mechanism for determining node status within the cluster. Nodes transmit gossip messages to each other nodes, the gossip messages listing other nodes in the cluster that are operational. When a node does not receive a gossip message from a particular node within a predetermined time period, then the node transmits messages to the other nodes indicating that the particular node is down. However, if another node has received a packet from the particular node within the predetermined time period and receives the node down message, then the other node responds with a node alive message.

Inter-node communication scheme for sharing node operating status

An event notification method for distributed processing systems provides reduction of queue space and event processing bandwidth associated with duplicate events such as a particular event that is duplicated and results in multiple event notifications propagated for multiple consumers. When a duplicate event notification is received at an input to an event notification queue, rather than queuing the duplicate event notification, a sequence number of the event notification already in the queue is updated to indicate to the event consumer, exactly how many duplicate events have been received. The timestamp of the updated event notification may also be set to the timestamp of the most recently received duplicate event notification.

Event overflow handling by coalescing and updating previously-queued event notification

The present invention provides a computer implemented method for communicating a signature in a received email. Initially, a server receives a source email from a source client, the source email comprising a signature index entry, and a body. The server determines for a first recipient that a first associated destination client is capable of rendering a signature of the signature index entry in response to a selection of an indexed signature. The server, responsive to a determination that the destination client is capable of rendering the signature index entry, forwards the source email to the first recipient as a delivered email using the body of the source email such that an indexed signature is present in the body of the delivered email. In addition, a method for generating a signature header is shown that provides a many to one correspondence between indexed signatures and a signature index entry.

Composing, forwarding, and rendering email system

A unique device name is assigned to each of a plurality of shared storage devices in a cluster configuration database defining membership of nodes in a cluster. A particular node among the nodes defined by the cluster configuration database as a member of the cluster searches the cluster configuration database for a device identifier matching a device identifier of a shared storage device hosted by the particular node. In response to finding a matching device identifier in the cluster configuration database, the particular node renames, in a local configuration maintained at the particular node, a storage device associated with the matching device identifier with the unique name assigned to that storage device in the cluster configuration database.

Propagation of unique device names in a cluster system

An event notification system for distributed processing systems provides for replacement of event identifiers associated with transient objects, such as processes within the processing system. An event management interface receives a notification from an event producer that an identifier of an event produced by the event producer is no longer valid. The event management interface blocks event notification for the event and dissociates an event registration entry associated with the event from the event identifier. A new event identifier is received from the event producer by the event management interface, which associates the registration entry with the new event identifier. Event notification for the event is then resumed.

Changing an event identifier of a transient event in an event notification system

In response to a stimulus indicating configuration of a node into a cluster of a plurality of nodes including the node, the node determines whether or not the node has a universally unique identifier (UUID), and if not, the node provides its own persistent self-assigned UUID. The node searches a cluster configuration database for a temporary identifier associated with the node. In response to the node locating the temporary identifier of the node in the cluster configuration database, the node writes its self-assigned UUID into the cluster configuration database and joins the cluster.

Self-assignment of node identifier in a cluster system

Communication between clusters of processing nodes is initiated by designating a link layer address and a target node name in a remote cluster. The link layer address is transmitted to the target node via a regular network transmission. The link layer address is stored locally in each cluster and the nodes in each cluster are signaled that a configuration change has been made, so that gateway nodes in the clusters can obtain the link layer address to use for subsequent communications with the other cluster, such as event notifications of node status changes.

Inter-cluster communications technique for event and health status communications

According to one embodiment of the present disclosure, a method and technique is disclosed for maintaining a network connection during transfer of the workload from a global environment of a logical partition to a workload partition of the logical partition and during any subsequent transfer(s).

Maintaining a network connection of a workload during transfer

Communication ability between nodes in a cluster-based computer system is tracked to inform applications executing on the nodes of the existence and quality of the endpoint-to-endpoint communications available between the nodes. Communications between a node and other nodes are tracked, and a database records the communication ability between the node and the other nodes for each link between the nodes. The tracking and recording are repeated at the other nodes. A registration by an application executing at a particular one of the nodes to receive notifications of changes in the communication ability with another node over a particular link (or in general) will cause notification of the application when the link status changes.

Endpoint-to-endpoint communications status monitoring

Provided are techniques related generally to computer communication and, more specifically, to techniques that provide legacy applications with access to a cluster infrastructure. A pseudo interface layer provides applications with internet protocol (IP) family sockets access to cluster awareness protocols in a manner that may be transparent to both the application and the cluster awareness layer of a kernel.

Exploiting cluster awareness infrastructure through internet socket based applications

Inter-node communication scheme for node status sharing

A second node receives a message from a first node in a cluster environment. The message includes a unique identifier of a shared data storage device including a cluster configuration database that defines membership of nodes in a cluster. In response to receiving the message, the second node attempts to find the shared data storage device. In response to finding the shared data storage device, the second node locates and reads the cluster configuration database on the shared data storage device. The second node then assimilates a cluster configuration update indicated by the cluster configuration database.

Notification of configuration updates in a cluster system

An event notification method for distributed processing systems provides remote and local node event notification in systems that require local registration of an event consumer in order produce an event notifications. To provide notification of an event occurring on a remote node, either event consumers on all nodes in the cluster register locally to receive event notifications and specify that the event is a cluster event, in which case the nodes send notification of their locally-occurring events to all nodes, or remote registrations are accepted at nodes and if a local consumer for the event is not present, a listener thread registers as an event consumer. The listener thread sends the event notifications to the remote nodes registered as consumers for the event by observing communication between the event producer and the local consumer, or receiving the event notifications directly if there is no local consumer.

Growing community of inventors

Bengaluru, India

Rajeev Kumar Mishra