Interpreting .diff files

Use this information to help you interpret the difference between the baseline health check and the current health check.

If the results files of a Fast Fabric health check include a file named *.diff, then there is a difference between the baseline and the current health check. This file is generated by the health check comparison algorithm by using the diff command. The first file (file1) is the baseline file, and the second file (file2) is the most recent file.

The default diff format that is used is shown with the context of one line before and after the altered data. This format is the same as a diff –C 1. This command can be changed by entering your preferred diff command and options by using the variable FF_DIFF_CMD in the fastfabric.conf file. For more details, see the Fast Fabric Toolset Users Guide. The following information shows that the default context is being used.

Entries similar to the following example are repeated throughout the *.diff file. These lines indicate how the baseline (file1) differs from the latest (file2) health check.

*** [line 1], [line 2] ****
lines from the baseline file
--- [line 1], [line 2] ----
lines from the most recent file

The first set of lines enclosed in asterisks (*) indicates which line numbers contain the lines from the baseline file that have been altered. The associated line numbers and data from the latest file follow.

Use the man diff command to get more details on diff file.

Several scenarios are shown in the following examples:

The following is an example of what might be seen when swapping two ports on the same host channel adapter (HCA).

***************
*** 25,29 ****
   10g 0x00025500000da080   1 SW IBM logical switch 1
- <->  0x00066a0007000ced   8 SW SilverStorm 9120 GUID=0x00066a00020001d9 Leaf 1,
Chip A
-  10g 0x00025500000da081   1 SW IBM logical switch 2
  <->  0x00066a00d90003d6  14 SW SilverStorm 9024 DDR GUID=0x00066a00d90003d6
   30g 0x00025500000da100   1 CA IBM logical HCA 0
--- 25,29 ----
   10g 0x00025500000da080   1 SW IBM logical switch 1
  <->  0x00066a00d90003d6  14 SW SilverStorm 9024 DDR GUID=0x00066a00d90003d6
+  10g 0x00025500000da081   1 SW IBM logical switch 2
+ <->  0x00066a0007000ced   8 SW SilverStorm 9120 GUID=0x00066a00020001d9 Leaf 1,
Chip A 30g 0x00025500000da100   1 CA IBM logical HCA 0

Use Table 1 to view detailed information about the differences of the baseline and the latest health check information in the previous example.

Table 1. Differences between the baseline and current health check information after swapping two ports on the same host channel adapter (HCA)
HCA Port	Connected to switch port in baseline	Connected to switch port in latest
0x00025500000da080 1 SW IBM logical switch 1	0x00066a0007000ced 8 SW SilverStorm 9120 GUID=0x00066a00020001d9 Leaf 1,	0x00066a00d90003d6 14 SW SilverStorm 9024 DDR GUID=0x00066a00d90003d6
0x00025500000da081 1 SW IBM logical switch 2	0x00066a00d90003d6 14 SW SilverStorm 9024 DDR GUID=0x00066a00d90003d6	0x00066a0007000ced 8 SW SilverStorm 9120 GUID=0x00066a00020001d9 Leaf 1,

Table 1. Differences between the baseline and current health check information after swapping two ports on the same host channel adapter (HCA)

HCA Port

Connected to switch port in baseline

Connected to switch port in latest

0x00025500000da080   1 SW
IBM logical switch 1

0x00066a0007000ced   8 SW
SilverStorm 9120
GUID=0x00066a00020001d9 Leaf 1,

0x00066a00d90003d6  14 SW
SilverStorm 9024 DDR
GUID=0x00066a00d90003d6

0x00025500000da081
1 SW IBM logical switch 2

0x00066a00d90003d6  14 SW
SilverStorm 9024 DDR
GUID=0x00066a00d90003d6

0x00066a0007000ced   8 SW
SilverStorm 9120
GUID=0x00066a00020001d9
Leaf 1,

The following example shows what might be seen after swapping two ports on the same switch:

***************
*** 17,19 ****
   10g 0x00025500000d8b80   1 SW IBM logical switch 1
! <->  0x00066a00d90003d6  15 SW SilverStorm 9024 DDR GUID=0x00066a00d90003d6
   10g 0x00025500000d8b81   1 SW IBM logical switch 2
--- 17,19 ----
   10g 0x00025500000d8b80   1 SW IBM logical switch 1
! <->  0x00066a00d90003d6  14 SW SilverStorm 9024 DDR GUID=0x00066a00d90003d6
   10g 0x00025500000d8b81   1 SW IBM logical switch 2
***************
*** 25,27 ****
   10g 0x00025500000da080   1 SW IBM logical switch 1
! <->  0x00066a00d90003d6  14 SW SilverStorm 9024 DDR GUID=0x00066a00d90003d6
   10g 0x00025500000da081   1 SW IBM logical switch 2
--- 25,27 ----
   10g 0x00025500000da080   1 SW IBM logical switch 1
! <->  0x00066a00d90003d6  15 SW SilverStorm 9024 DDR GUID=0x00066a00d90003d6
   10g 0x00025500000da081   1 SW IBM logical switch 2

Table 2. Differences between the baseline and current health check information after swapping two ports on the same switch.
Switch Port	Connected to HCA port in baseline	Connected to HCA port in latest
0x00066a00d90003d6 15 SW SilverStorm 9024 DDR	0x00025500000d8b80 1 SW IBM logical switch 1	0x00025500000da080 1 SW IBM logical switch 1
0x00066a00d90003d6 14 SW SilverStorm 9024 DDR	0x00025500000d8b80 1 SW IBM logical switch 1	0x00025500000da080 1 SW IBM logical switch 1

Table 2. Differences between the baseline and current health check information after swapping two ports on the same switch.

Switch Port

Connected to HCA port in baseline

Connected to HCA port in latest

0x00066a00d90003d6  15 SW 
SilverStorm 9024 DDR

0x00025500000d8b80   1 SW IBM
logical switch 1

0x00025500000da080   1 SW
IBM logical switch 1

0x00066a00d90003d6  14 SW
SilverStorm 9024 DDR

0x00025500000d8b80   1 SW IBM
logical switch 1

0x00025500000da080   1 SW
IBM logical switch 1