Skip to main content

Cornelis Technical Documentation

8.2.4. Sample Files

Sample files are used to create the files necessary to work with certain scripts and commands. They are installed in the /usr/share/opa/samples directory, including the opagentopology sample script.

Note

Do not edit the sample files.

8.2.4.1. Packet Capture Files

The following files are used with opapacketcapture.

Table 43. Packet Capture Files

File

Description

filterFile.txt

Packet filter configuration.

triggerFile.txt

Trigger configuration for the condition to terminate packet capture.



8.2.4.2. Topology Files

The following files are related to topology.

Table 44. Topology Files

File

Description

README.topology

Information about the opagentopology script.

README.xlat_topology

Information about the opaxlattopology script, minimal_topology.xlsx, and detailed_topology.xlsx files.

opagentopology

Script to generate topology file.

Refer to README.topology for an explanation.

opatopology_links.txt

Text CSV values for LinkSummary information. Used as input to opagentopology.

opatopology_FIs.txt

Text CSV values for SuperNIC Nodes information. Used as input to opagentopology.

opatopology_SWs.txt

Text CSV values for Switch Nodes information. Used as input to opagentopology.

opatopology_SMs.txt

Text CSV values for Subnet Manager (SM) information. Used as input to opagentopology.

linksum_swd06.csv

linksum_swd24.csv

Sample CSV configurations.

Refer to README.xlat_topology for an explanation.

detailed_topology.xlsx, minimal_topology.xlsx

Topology files in spreadsheet format.

Refer to Sample Topology Spreadsheets for additional details.Sample Topology Spreadsheets

opamon.conf-sample, opamon.si.conf-sample

Port counter threshold files for use with opareport.



8.2.4.3. Miscellaneous Files

The following files are used for miscellaneous scripts and commands.

Table 45. Miscellaneous Files

File

Description

hostverify.sh

Bash script to help verify the configuration and performance of host nodes.

mac_to_dhcp

Script to help generate DHCP stanzas to append to dhcpd.conf.

Uses host and MAC addresses.

opafastfabric.conf-sample

Configuration file for opafastfabric.

Used in /etc/opa.

opa_ca_openssl.cnf-sample

Configuration file for generation of OpenSSL CA certificate requests.

opa_comp_openssl.cnf-sample

Configuration file for generation of OpenSSL certificate requests.

opamgt_tls.xml-sample

Configuration file for SSL parameters.



8.2.4.4. Sample Topology Spreadsheets

This section describes the sample topology spreadsheet files: detailed_topology.xlsx and minimal_topology.xlsx. Both files are installed in the /usr/share/opa/samples directory.

Note

In this section, <topologyfile> indicates the file you customize for your cluster.

The two sample files, detailed_topology.xlsx and minimal_topology.xlsx, provide a standard format for representing each external link in a cluster. Each row in the minimal_topology.xlsx spreadsheet depicts one link containing Source, Destination, and Cable fields. The detailed_topology.xlsx spreadsheet contains an additional Link field providing link-specific details. In both spreadsheets, the cells cannot contain commas.

Figure 85. minimal_topology.xlsx Example
minimal_topology.xlsx Example


Figure 86. detailed_topology.xlsx Example
detailed_topology.xlsx Example


The previous figures show examples of links between SuperNIC and CN5000 Switch (rows 4-7), SuperNIC and Core Switch (rows 8-11), and CN5000 Switch and Core Switch (rows 12-15).

Source and Destination fields each have the following columns:

  • Rack Group (first row required)

    Use this field to specify a Row or location of cluster hardware. The first row in the spreadsheet must have a value. If the Rack Group or Rack field is empty on any row, the script defaults the value in that field to the closest previous value.

  • Rack (optional)

    Use this field to specify a rack unit number for the device.

  • Name (required)

    User-defined primary name of host or switch. Cornelis recommends that host names match the host names configured in /etc/hosts.

    Hosts use the following information:

    • Host Fabric Interface: Hostname or hostdetails

    • Edge Switch: Switchname

    • Core Leaf: Corename or Lnnn

  • Name-2 (optional)

    For hosts, Name-2 is optional and is output as NodeDetails in the topology XML file.

  • Port (required)

    Port contains the port number of the SuperNIC or Switch port. If the Port field is empty, the script defaults to 1.

  • Type

    Type contains the device type. When creating the spreadsheet to verify external links, use the following values for type: FI, SW, and CL.

    The first row must have a value. If the Type field is empty on any row, the script defaults the value to the closest previous value. The type values are:

    • Host Fabric Interface: FI for SuperNIC adapter

    • Edge Switch: SW

    • Core Leaf: CL for DCS core leaf module

The Cable field has the following columns:

  • Label - Max characters = 57

  • Length

  • Details

Note

Cable values are optional and have no special syntax.

The Link fields have the following columns:

Note

Link fields are optional and have no special syntax. An example can be seen on detailed_topology.xlsx.

8.2.4.4.1. Core Full Statement

At the bottom of each sample topology file, there is a Core Full statement to indicate if the DCS is fully populated with all spine and leaf modules installed. If there are multiple DCSs in the fabric, each DCS should have an entry in your <topologyfile>.xlsx file as shown in the following table.

Table 46. Core Full Statement Definitions

Core Name:Core01

Core Group:row1

Core Rack:rack01

Core Size:576

Core Full:0

Core Name:Core02

Core Group:row1

Core Rack:rack02

Core Size:576

Core Full:0

Core Name: Specified in "Name" Column of <topologyfile>.xlsx

Core Group: Specified in "Rack Group" Column of <topologyfile>.xlsx

Core Rack: Specified in "Rack" Column of <topologyfile>.xlsx

Core Size: Set to 576 for the Director switch. Represents all internal (spine) links for fully populated Director.

0: Use for partially populated director.

1: Use for fully populated director.



8.2.4.4.2. Present Leaf Statement

This section should be used when the Core is partially populated (Core Full:0). Present Leaf Statement is used to specify the list of all present Leafs in the Core. This section can have multiple rows for each partially populated Core in the fabric.

There is no need to list the leaf names that have already been listed in the external link section as either Source Name or Destination Name.

Table 47. Present Leaf Statement Definitions

Core Name:core2

L105

L106

L110

L111

L112

L113

Core Name: Specified in "Name" Column of <topologyfile>.xlsx

Name of Leaf Present

Name of Leaf Present

Name of Leaf Present



8.2.4.4.3. Omitted Spine Statement

This section should also be used when the Core is partially populated (Core Full:0). The Omitted Spine Statement is used to list all the missing Spines from the Core. This section can have multiple rows for each partially populated Core in the fabric.

Table 48. Omitted Spines Statement Definitions

Core Name:core2

S203

S205

Core Name: Specified in "Name" Column of <topologyfile>.xlsx

Name of Missing Spine

Name of Missing Spine



8.2.4.4.4. SM Statement

This section can be used to list all the expected SMs in the fabric. The section can have multiple cells to indicate any number of SMs in a fabric.

Table 49. SM Statement Definition

SM

host01

host02

Name of Host running SM



Note

Expected SM cannot be added with the detail levels, such as within a specific rack or group.

Dynamic Host Configuration Protocol - This network management protocol is used to assign an Internet Protocol (IP) address to a device so they can communicate using IP.

Secure Socket Layer - This is a protocol for establishing secure links between networked computers

Maximum Transmission Unit - This is the size of the largest protocol data unit or data packet that can be sent in a single network layer transaction.

Subnet Manager or Subnet Management