IBM 2109 Service Guide - Page 113

Crossporttest, Diag-cminocap, Diag-cmidata, Diag-cmicksum.

Page 113 highlights

| Table 32. cmiTest example | Synopsis cmiTest [passCount] | Availability Administrator | Description Use this command to verify that the multiplexed 4-bit control message | interface (CMI) point-to-point connection between two ASICs is | functioning properly. Also use it to verify that a message with a bad | checksum sets the error and interrupt status bits of the destination | ASIC and that a message with a good checksum does not set an error | or interrupt bit in any ASIC. | The Test method is displayed below. Complete the following for each | source ASIC X and each destination ASIC Y in the switch. Do not | complete this test if ASIC X = ASIC Y. | 1. Generate the CMI data D. | 2. Send data from source X to destination Y. | 3. Check destination Y for the following: | v The capture flag is set. | v The data (D) is received as expected . | v If the checksum test is good, the CMI error bit and the EMI error | interrupt status bit are not set. | v If the checksum test is bad, the CMI error bit and the CMI error | interrupt status bit are set. | 4. Check that all ASICs (other than Y) do not have: | v The capture flag set | v The CMI error bit set | v The CMI error interrupt status bit set | Below are the possible error messages if failures are detected: | DIAG-CMISA1 | DIAG-CMINOCAP | DIAG-CMICKSUM | DIAG-CMIINVCAP | DIAG-CMIDATA | DIAG-INTNIL | DIAG-BADINT | Operands This command has the following operand: | passCount Specify the number of times to execute this test. The | default value is 1. This operand is optional. | | Related error messages: DIAG-BADINIT, DIAG-INTNIL, DIAG-CMISA1, | DIAG-CMINOCAP, DIAG-CMIINVCAP, DIAG-CMIDATA, DIAG-CMICKSUM. crossPortTest The crossPortTest command verifies the intended functional operation of the switch by sending frames from the transmitter on each port through the GBIC and external cable and back to the receiver on another port. It exercises the entire path of the switch. | Figure 37 on page 98 shows the recommended connection when executing the | crossPortTest. The cables need not be connected as such. A port can be | connected to any port in the same switch provided the connection is of the same | technology; meaning copper ports must connect to copper ports, SWL ports to SWL | ports, and LWL ports to LWL ports. Appendix B. Diagnostics 97

  • 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

Table 32. cmiTest example
Synopsis
cmiTest [passCount]
Availability
Administrator
Description
Use this command to verify that the multiplexed 4-bit control message
interface (CMI) point-to-point connection between two ASICs is
functioning properly. Also use it to verify that a message with a bad
checksum sets the error and interrupt status bits of the destination
ASIC and that a message with a good checksum does not set an error
or interrupt bit in any ASIC.
The Test method is displayed below. Complete the following for each
source ASIC X and each destination ASIC Y in the switch. Do not
complete this test if ASIC X = ASIC Y.
1.
Generate the CMI data D.
2.
Send data from source X to destination Y.
3.
Check destination Y for the following:
v
The capture flag is set.
v
The data (D) is received as expected .
v
If the checksum test is good, the CMI error bit and the EMI error
interrupt status bit are not set.
v
If the checksum test is bad, the CMI error bit and the CMI error
interrupt status bit are set.
4.
Check that all ASICs (other than Y) do
not
have:
v
The capture flag set
v
The CMI error bit set
v
The CMI error interrupt status bit set
Below are the possible error messages if failures are detected:
DIAG-CMISA1
DIAG-CMINOCAP
DIAG-CMICKSUM
DIAG-CMIINVCAP
DIAG-CMIDATA
DIAG-INTNIL
DIAG-BADINT
Operands
This command has the following operand:
passCount
Specify the number of times to execute this test. The
default value is 1. This operand is optional.
Related error messages
: DIAG-BADINIT, DIAG-INTNIL, DIAG-CMISA1,
DIAG-CMINOCAP, DIAG-CMIINVCAP, DIAG-CMIDATA, DIAG-CMICKSUM.
crossPortTest
The
crossPortTest
command verifies the intended functional operation of the
switch by sending frames from the transmitter on each port through the GBIC and
external cable and back to the receiver on another port. It exercises the entire path
of the switch.
Figure 37 on page 98 shows the recommended connection when executing the
crossPortTest
. The cables need not be connected as such. A port can be
connected to any port in the same switch provided the connection is of the same
technology; meaning copper ports must connect to copper ports, SWL ports to SWL
ports, and LWL ports to LWL ports.
Appendix B. Diagnostics
97
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|