Abstract: A device may receive network protocol data identifying a network protocol trace associated with network devices of a network, and may divide the network protocol trace into multiple segments. The device may identify a set of segments, in the multiple segments, that includes a first segment and second segments related to the first segment, and may process the multiple segments, in parallel, to determine first results data corresponding to the multiple segments. The device may process the second segments, in parallel, to determine second results data, and may combine the first results data and the second results data to generate final results data, wherein the final results data indicate utilization by the network devices of a network protocol associated with the network. The device may perform one or more actions based on the final results data.

Abstract: A device may receive network protocol data identifying a network protocol trace associated with network devices of a network, and may divide the network protocol trace into multiple segments. The device may identify a set of segments, in the multiple segments, that includes a first segment and second segments related to the first segment, and may process the multiple segments, in parallel, to determine first results data corresponding to the multiple segments. The device may process the second segments, in parallel, to determine second results data, and may combine the first results data and the second results data to generate final results data, wherein the final results data indicate utilization by the network devices of a network protocol associated with the network. The device may perform one or more actions based on the final results data.

Abstract: A device may receive network protocol data identifying a network protocol trace associated with network devices of a network, and may divide the network protocol trace into multiple segments. The device may identify a set of segments, in the multiple segments, that includes a first segment and second segments related to the first segment, and may process the multiple segments, in parallel, to determine first results data corresponding to the multiple segments. The device may process the second segments, in parallel, to determine second results data, and may combine the first results data and the second results data to generate final results data, wherein the final results data indicate utilization by the network devices of a network protocol associated with the network. The device may perform one or more actions based on the final results data.

Abstract: A network diagnostic component that is placed in-line between a first and second node. The diagnostic component is used to perform a comparison operation on any specified portion of a network data frame. For example, the first node may communicate with the second node using a network data frame that includes one or more data units. The network diagnostic component uses a starting and ending address that specify where in the network data frame to begin and end the comparison operation. A match template that specifies a particular condition for comparison is also used. The network diagnostic component then performs the comparison operation by searching for a data unit that at least partially matches the comparison condition in the portion of the network data frame specified by the starting and ending addresses. The data unit may be located at any location in the specified portion of the data frame.

Abstract: Multi-chassis systems determine their topology and self-organize through a discovery process. The systems include one or more chassis, each with individual blades and ports, which are serially chained together. When the discovery process is initiated, chassis identification data in buffers in each chassis is propagated to adjacent chassis and is then used to initiate communication via a network connection. Once the chassis are able to communicate via the network connection, at least one chassis in the system receives the chassis identification data of each chassis and can thereby identify each chassis. The chain is then divided into one or more sync-groups and master and slave chassis are designated. Each sync-group is configured to ignore data from other sync-groups. Domains are also configured from sets of ports within each sync-group.

Abstract: A multi-chassis system includes at least a first chassis and a second chassis that each includes one or more blades. The one or more blades in turn include one or more ports. The two or more chassis are connected through use of an interconnector. The multi-chassis system may also include access to one or more microprocessors that may execute thereon software that controls the propagation of the arm condition. The arm condition is generated at a first port of a first chassis or network analyzer blade coupled to the first chassis. The arm condition is then transmitted to one or more additional ports of the first chassis while not being transmitted to any ports of the second chassis. Finally, the reception of a precondition for triggering defined by the arm condition is limited to those ports that have received the arm condition.

Abstract: Creation of port domains in a multi-chassis system. The multi-chassis system includes two or more chassis that each includes one or more blades. In one embodiment, a sync group of at least two chassis is created, typically by connecting the two or more chassis with an interconnection means such as a sync-cable. Then, two or more ports of the sync group are selected for inclusion in a port domain. The locations of the ports relative to each other is then determined. Finally, a port domain is generated based on the relative locations of the ports and port domain generation rules. If the ports are on separate chassis, then a global domain is generated if a predetermined number of global domains do not already exist and if the ports are on the same chassis, a local domain is generated regardless of the number of global domains.

Abstract: A multi-chassis system includes at least a first chassis and a second chassis that each includes one or more blades. The one or more blades in turn include one or more ports. The two or more chassis are connected through use of an interconnector. The multi-chassis system may also include access to one or more microprocessors that may execute thereon software that controls the propagation of the arm condition. The arm condition is generated at a first port of a first chassis or network analyzer blade coupled to the first chassis. The arm condition is then transmitted to one or more additional ports of the first chassis while not being transmitted to any ports of the second chassis. Finally, the reception of a precondition for triggering defined by the arm condition is limited to those ports that have received the arm condition.

Abstract: Creation of port domains in a multi-chassis system. The multi-chassis system includes two or more chassis that each includes one or more blades. In one embodiment, a sync group of at least two chassis is created, typically by connecting the two or more chassis with an interconnection means such as a sync-cable. Then, two or more ports of the sync group are selected for inclusion in a port domain. The locations of the ports relative to each other is then determined. Finally, a port domain is generated based on the relative locations of the ports and port domain generation rules. If the ports are on separate chassis, then a global domain is generated if a predetermined number of global domains do not already exist and if the ports are on the same chassis, a local domain is generated regardless of the number of global domains.

Abstract: A network diagnostic component that is placed in-line between a first and second node. The diagnostic component is used to perform a comparison operation on any specified portion of a network data frame. For example, the first node may communicate with the second node using a network data frame that includes one or more data units. The network diagnostic component uses a starting and ending address that specify where in the network data frame to begin and end the comparison operation. A match template that specifies a particular condition for comparison is also used. The network diagnostic component then performs the comparison operation by searching for a data unit that at least partially matches the comparison condition in the portion of the network data frame specified by the starting and ending addresses. The data unit may be located at any location in the specified portion of the data frame.

Abstract: The present invention provides for using description files to configure components in a distribute system. Computer-readable media store data structures representing a component mapping and a component description. Computer systems can utilize the data structures to access components in a diagnostic chassis. In some embodiments, a computer system receives application instructions for accessing a component. The computer system refers to the component mapping to identify components that are to be configured to implement the received application instructions. The computer system generates mapped application instructions in accordance with the referred to component mapping. The computer system refers to the component description to identify compatible low-level instructions for configuring the identified components. The computer system sends the compatible low-level instructions to the identified components to configure the identified components to implement the received application instructions.

Abstract: The present invention provides for a firmware description language for accessing firmware registers. Computer-readable media store a data structure representing a firmware description language that includes at least a blade type field containing a blade type value that represents a blade type and a register description field containing a one or more register configuration values for accessing a register at a blade of the blade type represented in the blade type field. In some embodiments, a computer system receives application instructions for accessing a firmware register. The computer system refers to the firmware description language to identify register attributes of the firmware register. The computer system generates low-level instructions for accessing the firmware register in accordance with register attributes referred to in the firmware description language. The computer system issues the low-level instructions for accessing the firmware register.

Abstract: The present invention provides for creating description files used to configure components in a distributed system. A computer or program developer accesses an application type. The computer or program developer accesses a hardware specification. The computer or program developer identifies relevant registers from the hardware specification that are to be manipulated to implement the application type. The computer or program developer generates a description file that corresponds the relevant registers to the application type.

Abstract: The present invention provides for managing resources of chassis that include configurable network diagnostic modules. A computer system receives a request to allocate a chassis resource to a requesting entity. The computer system sends an allocation request message to a chassis that includes the chassis resource. The chassis receives an allocation request message from the requesting computer system. The chassis determines if the requested chassis resource is currently being utilized. The chassis refers to allocation rules to determine if the requested chassis resource can be allocated to satisfy the resource allocation request. The chassis allocates one or more resources according to the allocation rules and returns an allocation response to the requesting computer system. The computer system receives the allocation response and presents the allocation response at the requesting computer system.

Abstract: Multi-chassis systems determine their topology and self-organize through a discovery process. The systems include one or more chassis, each with individual blades and ports, which are serially chained together. When the discovery process is initiated, chassis identification data in buffers in each chassis is propagated to adjacent chassis and is then used to initiate communication via a network connection. Once the chassis are able to communicate via the network connection, at least one chassis in the system receives the chassis identification data of each chassis and can thereby identify each chassis. The chain is then divided into one or more sync-groups and master and slave chassis are designated. Each sync-group is configured to ignore data from other sync-groups. Domains are also configured from sets of ports within each sync-group.

Abstract: The present invention provides for discovering diagnostic port functionality in a distributed system. A computer system requests network addresses for one or more chassis. A chassis receives the request for a network address and returns a corresponding network address at least for the chassis. The computer system receives one or more network addresses corresponding to the one or more chassis. The computer system requests resource data from each of the one or more corresponding network addresses. The chassis receives the request for resource data and returns resource data representing at least the current configuration of the chassis to the requesting computer system. The computer system receives resource data representing the configuration of the one or more chassis. The computer system presents the received resource data at the requesting computer system.