Abstract: A secured network management domain access system includes a chassis housing a master I/O module that is configured to provide a network management domain, and a management module coupled to the master I/O module. The management module includes an enclosure controller coupled to the master I/O module via a first communication channel, and that retrieves master I/O module secured access information from the master I/O module via the first communication channel. The management module also includes a management service coupled to the enclosure controller via a second communication channel and to the master I/O module via a third communication channel, and that retrieves the master I/O module secured access information from the enclosure controller via the second communication channel, and performs validation operations with the master I/O module via the third communication channel such that the management service may securely access the network management domain via the master I/O module.

Abstract: A resilient TCP/IP connection system includes a first computing device coupled to a second computing device. The second computing device transmits a first TCP connection establishment communication that includes a first computing device TCP connection identifier to the first computing device. In response, the second computing device receives a second TCP connection establishment communication that includes a second computing device TCP connection identifier from the first computing device, and establishes a first resilient TCP connection with the first computing device. The second computing device then provides the second computing device TCP connection identifier in each TCP/IP communication transmitted to the first computing device via the first resilient TCP connection, and identifies the first computing device TCP connection identifier in each TCP/IP communication received from the first computing device via the first resilient TCP connection.

Abstract: A system/network management domain synchronization system includes a first computing system that belongs to a first MCM group and that includes a first computing system I/O module that belongs to a first network management domain, and a second computing system that is coupled to the first computing system. The second computing system includes a second computing system management module that joins the first MCM group and, in response, broadcasts a first announcement that includes a first MCM group identifier for the first MCM group. The second computing system also includes a second computing system I/O module that receives the first announcement, determines that the second computing system management module is included in the second computing system with the second computing system I/O module and, n response, joins the first network management domain.

Abstract: A resilient TCP/IP connection system includes a first computing device coupled to a second computing device. The second computing device transmits a first TCP connection establishment communication that includes a first computing device TCP connection identifier to the first computing device. In response, the second computing device receives a second TCP connection establishment communication that includes a second computing device TCP connection identifier from the first computing device, and establishes a first resilient TCP connection with the first computing device. The second computing device then provides the second computing device TCP connection identifier in each TCP/IP communication transmitted to the first computing device via the first resilient TCP connection, and identifies the first computing device TCP connection identifier in each TCP/IP communication received from the first computing device via the first resilient TCP connection.

Abstract: An automated Link Aggregation Group (LAG) configuration system includes a plurality of slave switch devices that are each coupled to an endhost device by at least one respective link. Each of the plurality of slave switch devices receives a Link Aggregation Group (LAG) communication from the endhost device, and forwards endhost device information in that LAG communication to a master switch device. The master switch device receives endhost device information from each of the plurality of slave switch devices and determines that each of the plurality of slave switch devices are coupled to the endhost device. In response, the master switch device sends a LAG instruction to each of the plurality of slave switch devices that causes the at least one respective link that couples each of the plurality of slave switch devices to the endhost device to be configured in a LAG.

Abstract: An expander I/O module discovery/management system includes a secondary system chassis housing an expander I/O module coupled to a server device. The server device identifies the secondary system chassis and an expander I/O module port utilized by that server device, and then generates and transmits an expander I/O module reporting communication identifying the secondary system chassis and the expander I/O module port. A primary system chassis houses a switching I/O module coupled to the expander I/O module. The switching I/O module receives the expander I/O module reporting communication and determines that the secondary system chassis identified in the expander I/O module reporting communication is different than the primary system chassis. In response, the switching I/O module assigns a virtual slot to the expander I/O module, and assigns a virtual port associated with the virtual slot to the expander I/O module port identified in the expander I/O module reporting communication.

Abstract: An FC fabric login/logout system includes an FC switch device coupled to an endpoint device by an intermediate FC fabric device. The intermediate FC fabric device receives a first FC fabric login from the endpoint device and, in response, performs FC fabric login operations to create an FC fabric session between the endpoint device and the FC switch device, and stores FC fabric session information in hardware table(s). When the intermediate FC fabric device determines that an FC fabric session time period has passed, it ends the FC fabric session by clearing the FC fabric session information from the hardware table(s), and stores the FC fabric session information in software table(s). If the intermediate FC fabric device then receives a second FC fabric login from the endpoint device, it recreates the FC fabric session by transferring the FC fabric session information from the software table(s) to the hardware table(s).

Abstract: An automated Link Aggregation Group (LAG) configuration system includes a plurality of slave switch devices that are each coupled to an endhost device by at least one respective link. Each of the plurality of slave switch devices receives a Link Aggregation Group (LAG) communication from the endhost device, and forwards endhost device information in that LAG communication to a master switch device. The master switch device receives endhost device information from each of the plurality of slave switch devices and determines that each of the plurality of slave switch devices are coupled to the endhost device. In response, the master switch device sends a LAG instruction to each of the plurality of slave switch devices that causes the at least one respective link that couples each of the plurality of slave switch devices to the endhost device to be configured in a LAG.

Abstract: A control information exchange system includes a sender device coupled to a receiver device and including a sender device application that periodically generates and transmits control packets that are directed to the receiver device. A control packet engine in the sender device receives a first control packet from the sender device application, performs a hashing operation on the first control packet to generate a first hash value, stores the first hash value in a sender device database, and transmits the first control packet to the receiver device. When the control packet engine subsequently receives a second control packet from the sender device application, it performs the hashing operation on the second control packet and, in response that hashing operation generating the first hash value, it transmits the first hash value to the receiver device to indicate the second control packet was duplicative of the first control packet.

Abstract: A control information exchange system includes a sender device coupled to a receiver device and including a sender device application that periodically generates and transmits control packets that are directed to the receiver device. A control packet engine in the sender device receives a first control packet from the sender device application, performs a hashing operation on the first control packet to generate a first hash value, stores the first hash value in a sender device database, and transmits the first control packet to the receiver device. When the control packet engine subsequently receives a second control packet from the sender device application, it performs the hashing operation on the second control packet and, in response that hashing operation generating the first hash value, it transmits the first hash value to the receiver device to indicate the second control packet was duplicative of the first control packet.

Abstract: A switching fabric loop prevention system includes first slave switch devices in a switching fabric that each automatically determine a first slave switch device role for themselves based on first directly connected device identification information received from a first directly connected device, and second slave switch devices in the switching fabric that each automatically determine a second slave switch device role for themselves based on second directly connected device identification information received from a second directly connected device. A master switch device in the switching fabric then configures each of the first slave switch devices having the first slave switch device role to prevent first type communications that have been received from one of the second slave switch devices having the second slave switch device role from being forwarded to another of the second slave switch devices having the second slave switch device role.

Abstract: Aspects of the present disclosure relate to systems and methods that help automate the generation of a test vector. Every functional product, be it a service, device, or combination thereof, has one or more documents associated with it. These documents may include such documentation as: (1) Release Notes; (2) Configuration Guides; (3) command line interfaces (CLIs)/application program interfaces (APIs); (4) Data Sheets; (5) Installation Guides; (6) User Manuals; (7) Errata notices; and (8) other documentation. In embodiments, command data-models and ranges and sequence of valid inputs to the data-model are extracted from natural language expressions in documentation related to a specific product. In embodiments, this extracted information is used to generate one or more table of attributes and properties or constraints about which a test vector may be generated for testing a command.

Abstract: A switching fabric role assignment system includes a plurality of switch devices coupled together in a switching fabric. A first switch device included in the plurality of switch devices receives an endhost device identification communication from an endhost device when the endhost device is connected to the first switch device. The first switch device uses the endhost device identification communication to identify an endhost device type of the endhost device and determines, based on the endhost device type, a first switch device role for the first switch device. The first switch device then transmits a first switch device role communication that identifies the first switch device role to a second switch device included in the plurality of switch devices and connected to the first switch device. The second switch device may then determine, based on the first switch device role, a second switch device role for the second switch device.

Abstract: A switching fabric configuration and management system includes switch devices. Each of the switch devices identifies a domain in a switching fabric database in that switch device, and determines others of the switch devices that share the domain. Each of the switch devices may then communicate with the others of the switch devices that share the domain to designate a master switch device and one or more slave switch devices from the switch devices that share the domain. The designation of the master switch device and the one or more slave switch devices configures the master switch device and the one or more slave switch devices as a switching fabric. Each slave switch devices then reports their slave switch device status to the master switch device, and the master switch device performs at least one control operation on the at least one slave switch device.

Abstract: A switching fabric loop prevention system includes first slave switch devices in a switching fabric that each automatically determine a first slave switch device role for themselves based on first directly connected device identification information received from a first directly connected device, and second slave switch devices in the switching fabric that each automatically determine a second slave switch device role for themselves based on second directly connected device identification information received from a second directly connected device. A master switch device in the switching fabric then configures each of the first slave switch devices having the first slave switch device role to prevent first type communications that have been received from one of the second slave switch devices having the second slave switch device role from being forwarded to another of the second slave switch devices having the second slave switch device role.

Abstract: An automated Link Aggregation Group (LAG) configuration system includes a plurality of slave switch devices that are each coupled to an endhost device by at least one respective link. Each of the plurality of slave switch devices receives a Link Aggregation Group (LAG) communication from the endhost device, and forwards endhost device information in that LAG communication to a master switch device. The master switch device receives endhost device information from each of the plurality of slave switch devices and determines that each of the plurality of slave switch devices are coupled to the endhost device. In response, the master switch device sends a LAG instruction to each of the plurality of slave switch devices that causes the at least one respective link that couples each of the plurality of slave switch devices to the endhost device to be configured in a LAG.

Abstract: An FC fabric login/logout system includes an FC switch device coupled to an endpoint device by an intermediate FC fabric device. The intermediate FC fabric device receives a first FC fabric login from the endpoint device and, in response, performs FC fabric login operations to create an FC fabric session between the endpoint device and the FC switch device, and stores FC fabric session information in hardware table(s). When the intermediate FC fabric device determines that an FC fabric session time period has passed, it ends the FC fabric session by clearing the FC fabric session information from the hardware table(s), and stores the FC fabric session information in software table(s). If the intermediate FC fabric device then receives a second FC fabric login from the endpoint device, it recreates the FC fabric session by transferring the FC fabric session information from the software table(s) to the hardware table(s).

Abstract: An Ethernet SAN system includes an initiator device and a target device coupled together by an Ethernet fabric that includes a plurality of Ethernet switch devices. The Ethernet switch devices exchange L2 FIP domain exchange multicast frames that include domain information associated with each of the Ethernet switch devices. That domain information is then used to exchange L2 FIP path exchange multicast frames that include path information associated with each of the Ethernet switch devices. That path information is then used to calculate path costs associated with at least some of the Ethernet switch devices. Those path costs are then used to exchange L2 FIP device exchange unicast frames that include device information associated with the initiator device and the target device. The Ethernet switch devices then transmit data between the initiator device and the target device based on the device information and the path costs.

Abstract: A module is tested for compatibility with a chassis without being inserted into the chassis. A platform specification and chassis configuration is obtained. Information about the module is received from an NFC tag attached to the module. The information about the module is analyzed against the platform specification and chassis configuration. Based on the analysis, one of a set of conditions is determined to exist. A first condition exists when the module will not be supported according to the platform specification. A second condition exists when the module will be supported and there are no empty slots for which the module will be compatible with the chassis configuration. A third condition exists when the module will be supported and there is at least one empty slot for which the module will be compatible with the chassis configuration. An indication, perceptible to a user, of a determined condition is generated.

Abstract: A module is tested for compatibility with a chassis without being inserted into the chassis. A platform specification and chassis configuration is obtained. Information about the module is received from an NFC tag attached to the module. The information about the module is analyzed against the platform specification and chassis configuration. Based on the analysis, one of a set of conditions is determined to exist. A first condition exists when the module will not be supported according to the platform specification. A second condition exists when the module will be supported and there are no empty slots for which the module will be compatible with the chassis configuration. A third condition exists when the module will be supported and there is at least one empty slot for which the module will be compatible with the chassis configuration. An indication, perceptible to a user, of a determined condition is generated.