IBM 2109 Service Guide - Page 127

setGbicMode, spinSilk, mode is activated, the spinSilk test only tests ports 0 and 3.

Page 127 highlights

setGbicMode The GBIC mode, when enabled, forces the crossPortTest command or the spinSilk command to limit its testing to only those ports whose GBICs are detected as present. To enable GBIC mode, execute the command as shown in Figure 58. switch:admin> setGbicMode 1 Figure 58. setGbicMode 1 command example To disable GBIC mode, execute the command as shown in Figure 59. switch:admin> setGbicMode 0 Figure 59. setGbicMode 0 command example spinSilk | Table 36 on page 112 and Table 37 on page 113 show the spinSilk command, | which verifies the intended functional operation of the switch. It sends frames from | the transmitter on each port through the GBIC and external cable, and back to the | receiver on another port at the full hardware speed of 1Gbps. It exercises the entire | path of the switch. Because the CPU is not comparing data on each frame as with the other two frame tests, the DIAG-DATA error is never reported during the spinSilk test. However, the other error messages defined for the crossPortTest test and their corresponding probable causes and actions are applicable to the spinSilk test. The state of the GBIC mode affects the operation of the spinSilk test. Executing the following command before executing the crossPortTest activates the GBIC mode: switch:admin> setGbicMode 1 When activated, only ports with GBICs installed are included in the spinSilk list of ports to test. For example, if only ports 0 and 3 have GBICs installed and the GBIC mode is activated, the spinSilk test only tests ports 0 and 3. The state of the GBIC mode is saved in flash. It stays activated (even after a restart or a power-on and power-off cycle) until it is disabled as follows: sw:admin> setGbicMode 0 Reset GBIC mode before returning the switch to normal operation. An example mode of operation is to disable the switch, set the GBIC mode to 1, and execute the spinSilk test . In this example, the testing is limited to all ports that have GBICs installed and that are cable loopbacked correctly. Attention: This command must not be performed on an operational switch. Before issuing the spinSilk command, disable the switch by using the switchDisable command. Appendix B. Diagnostics 111

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178

setGbicMode
The GBIC mode, when enabled, forces the
crossPortTest
command or the
spinSilk
command to limit its testing to only those ports whose GBICs are detected
as present.
To enable GBIC mode, execute the command as shown in Figure 58.
To disable GBIC mode, execute the command as shown in Figure 59.
spinSilk
Table 36 on page 112 and Table 37 on page 113 show the
spinSilk
command,
which verifies the intended functional operation of the switch. It sends frames from
the transmitter on each port through the GBIC and external cable, and back to the
receiver on another port at the full hardware speed of 1Gbps. It exercises the entire
path of the switch.
Because the CPU is not comparing data on each frame as with the other two frame
tests, the DIAG-DATA error is never reported during the spinSilk test. However, the
other error messages defined for the crossPortTest test and their corresponding
probable causes and actions are applicable to the spinSilk test.
The state of the GBIC mode affects the operation of the spinSilk test. Executing the
following command before executing the crossPortTest activates the GBIC mode:
switch:admin> setGbicMode 1
When activated, only ports with GBICs installed are included in the spinSilk list of
ports to test. For example, if only ports 0 and 3 have GBICs installed and the GBIC
mode is activated, the spinSilk test only tests ports 0 and 3.
The state of the GBIC mode is saved in flash. It stays activated (even after a restart
or a power-on and power-off cycle) until it is disabled as follows:
sw:admin> setGbicMode 0
Reset GBIC mode before returning the switch to normal operation.
An example mode of operation is to disable the switch, set the GBIC mode to 1,
and execute the spinSilk test . In this example, the testing is limited to all ports that
have GBICs installed and that are cable loopbacked correctly.
Attention:
This command must not be performed on an operational switch.
Before issuing the
spinSilk
command, disable the switch by using the
switchDisable
command.
switch:admin> setGbicMode
1
Figure 58. setGbicMode 1 command example
switch:admin> setGbicMode
0
Figure 59. setGbicMode 0 command example
Appendix B. Diagnostics
111
|
|
|
|
|