HP Integrity Superdome SX1000 User Manual page 307

System entities represent MPs and nodes. The data contained in this file provides information on what
entities can be tested and the basics of how to communicate with each of the entities specified. This file is
normally created by JET. Below is a description of each entry in the file.
Comments Comments in this file are specified by placing a # character at the beginning of the line
containing the comment. End of line comments are not currently supported.
Complex Entries Each complex entry in the file begins with the keyword Complex followed by the complex
name string and the complex's architecture code. A complex entry ends with the keyword End_Complex. Both
of these entries must be on separate own lines.
Example G-18 Complex Entries
Complex <complex name> <architecture code>
.
.
.
End_Complex
Between these tags are the entity instances described below.
Entity Entries Entities exist within the complex tags. There are currently of two types: MP or NODE. Each entity
begins with the keyword Entity, followed by the entity type and its reference number, and ends with the keyword
End_Entity. Each of these tags must be on a separate line as shown below:
Entity <MP|NODE> <reference number>
.
.
.
End_Entity
The fields between the entity tags are described in the following section.
Entity Parameters Each Entity in this file must contain one and only one of the following entries.
If the entity is a Host—meaning that it has an Ethernet presence with its own IP address— then the entity requires a
hostname entry in the file. A hostname entry begins with the keyword Hostname and is followed by the hostname string,
the communication protocol (UDP or TCP), its IP address in dot notation, and the communications port number.
Hostname <host name>
If an entity is not a host, then a reference to the target host entity must be supplied. This reference specifies which host
entity commands targeted to this entity must be directed. This targeting entry begins with the keyword Target_Entity
followed by the entity type (MP|NODE) and its reference number:
Target_Entity<target entity type><target entity ref number>
Firmware information entries:
Firmware Information Entries Each entity must have a firmware information entry. This entry defines the
capabilities of the firmware to processes Scan Requests. A firmware entry begins with the keyword Firmware followed by
the supported sequence queue depth and queue size in kilobytes, and the version of the SDP protocol supported.
Firmware <queue depth>
End of File The complex configuration file must always end with the keyword End_Of_File.
Appendix G
<TCP|UDP> <ip address>
<queue size kBytes>
<port number>
<SDP version>
JUST Exploration Tool
Data Files
295