Abstract: Methods and apparatus to provide command abstraction. In one embodiment, a method includes obtaining information on commands for a plurality of devices including devices of the same type having different command structures, receiving a generic command from a user directed to one of the devices of the same type, determining, using a computer processor, whether the generic command is supported, extracting parameters from the generic command, and generating from the extracted parameters and the generic command a device-specific command for execution by the one of the devices of the same type.

Abstract: The real-time aspects of keep-alive generation are removed from the dynamic routing protocol (DRP) application and are embedded within a Unix-based operating system, which is programmed by DRP. A keep-alive control provides the ability to create a keep-alive message and a timeout interval on a TCP socket. Each socket can have an independent keep-alive message and timeout interval. A keep-alive message is sent whenever the TCP socket sends no normal user output for a duration exceeding the timeout interval. A timeout interval is normally specific in seconds and a keep-alive message is user definable and must not exceed a predetermined length in bytes. System calls are used to set the timeout interval and keep-alive message independently. Both a timeout and a keep-alive message must be set before the timeout becomes active.

Abstract: Methods and apparatus to provide, in a cloud infrastructure environment having a compute layer, a network layer, a storage layer, and management layer, wherein the management layer has no knowledge of at least some of existing infrastructure services, selecting hosts containing host bus adapters and/or network adapters having unique identifiers, using the unique identifiers to analyze the storage layer for: storage groups having host initiators that match the unique identifiers of the host bus adaptors, and/or network file storage (NFS) exports exposed to the unique identifiers as client IP addresses.

Abstract: Methods and apparatus for configuring disaster tolerant clusters of hypervisors as a virtualized service. In an exemplary embodiment, a system discovers WWPNs components, identifies networks zones in SANs having connectivity with at least one of the storage arrays and at least one of the journaling appliances, and creates a disaster recovery service offerings including replication in accordance with the selected service offering.

Abstract: Methods and apparatus to create zones for ports from a storage layer to a compute layer both coupled to a storage area network switch. In one embodiment, the storage layer includes ports in field replaceable unit (FRU) port groups, the port groups in FRU adapters, and the adapters in FRU adapter groups. The ports can be selected to minimize single points of failure.

Abstract: The real-time aspects of keep-alive generation are removed from the dynamic routing protocol (DRP) application and are embedded within a Unix-based operating system, which is programmed by DRP. A keep-alive control provides the ability to create a keep-alive message and a timeout interval on a TCP socket. Each socket can have an independent keep-alive message and timeout interval. A keep-alive message is sent whenever the TCP socket sends no normal user output for a duration exceeding the timeout interval. A timeout interval is normally specific in seconds and a keep-alive message is user definable and must not exceed a predetermined length in bytes. System calls are used to set the timeout interval and keep-alive message independently. Both a timeout and a keep-alive message must be set before the timeout becomes active.

Abstract: The real-time aspects of keep-alive generation are removed from the dynamic routing protocol (DRP) application and are embedded within a Unix-based operating system, which is programmed by DRP. A keep-alive control provides the ability to create a keep-alive message and a timeout interval on a TCP socket. Each socket can have an independent keep-alive message and timeout interval. A keep-alive message is sent whenever the TCP socket sends no normal user output for a duration exceeding the timeout interval. A timeout interval is normally specified in seconds and a keep-alive message is user definable and must not exceed a predetermined length in bytes. System calls are used to set the timeout interval and keep-alive message independently. Both a timeout and a keep-alive message must be set before the timeout becomes active.

Abstract: The real-time aspects of keep-alive generation are removed from the dynamic routing protocol (DRP) application and are embedded within a Unix-based operating system, which is programmed by DRP. A keep-alive control provides the ability to create a keep-alive message and a timeout interval on a TCP socket. Each socket can have an independent keep-alive message and timeout interval. A keep-alive message is sent whenever the TCP socket sends no normal user output for a duration exceeding the timeout interval. A timeout interval is normally specified in seconds and a keep-alive message is user definable and must not exceed a predetermined length in bytes. System calls are used to set the timeout interval and keep-alive message independently. Both a timeout and a keep-alive message must be set before the timeout becomes active.