3Com 3C63311 Reference Guide - Page 186

Table 28, ATM Forum R-138

Page 186 highlights

174 CHAPTER 5: PATHBUILDER S330 DIAGNOSTICS AND PERFORMANCE STATISTICS Table 28 DS1/E1 UNI Module Alarms (continued) Alarm Meaning Troubleshooting Steps Group [n] Multi IMA ID Different group IMA ID Correct link connections and/or IMA received on different links in an group configuration. IMA group. Group [n] Multi Test Different test procedure ATM Forum (R-138) request from different links in an IMA group from the far end. Use the test procedure from the lowest logical link and ignore the other test procedures. Group [n] Multiple Different frame lengths Make sure that the IMA frame length is M received on different links in an set to the same value for all links. IMA group. Group [n] Multiple Symmetry Different group symmetry Configure the group to be symmetric. received on different links in an 3Com PathBuilder products do not IMA group (symmetrical versus support asymmetric bandwidth for asymmetrical operation). IMA. Group [n] Time Sync Fail The far end transmit clocking mode does not match the near end transmit clocking mode Check configuration. Only CTC (Common Transfer Clock) is supported. If the far end transport clocking is set to ITC (Independent Transfer Clock), change it to CTC. IMA Protocol Mismatch IMA label is not ATM Forum 1.0. Near end and far end IMA protocol versions do no match. Check and correct incompatibility. IMA Remote Loopback Far end loopback detected, external cable loopback or crosstalk. Remove loopback condition. IMA Tx The near end IMA networking Misconnected Tx or Rx link state machine ATM Forum (R-123) detects the link is not connected to the correct FE Tx or Rx links. Remove the link and stop Tx and Rx data. Loss of Differential Relative time difference Synchronization between individual T1s/E1s in (LODS) the IMA group is out of range. ATM Forum (R-122) LODS is declared after the Rx IMA fails to synchronize the IMA link(s) in an IMA group within some time limit. Have your carrier verify the time synch and routing of individual T1s/E1s in the group. Check the IMA group configuration to ensure consistency on the local and remote ends. Loss of IMA Frame (LIF) ATM Forum (R-121) Loss of IMA Frame is detected in the Rx direction for an IMA link UP. There is an IMA frame size mismatch between two ends of the circuit. This can be caused by missing ICP cells (ATM cells that carry protocol information), bad IMA ID, bad sequence number, bad M, bad offset HEC error or CRC error in ICP cells. This problem may occur if the link gets noisy and there is no AFA to prevent the ICP from getting corrupted. It is detected in hardware and may or may not cause an operational problem. Check the IMA group configuration to ensure consistent frame size on the local and remote ends. Check links for evidence of noise. Check to be sure that AFA is enabled. (continued)

  • 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
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262

174
C
HAPTER
5: P
ATH
B
UILDER
S330 D
IAGNOSTICS
AND
P
ERFORMANCE
S
TATISTICS
Group [n] Multi
IMA ID
Different group IMA ID
received on different links in an
IMA group.
Correct link connections and/or IMA
group configuration.
Group [n] Multi Test
ATM Forum (R-138)
Different test procedure
request from different links in
an IMA group from the far
end.
Use the test procedure from the lowest
logical link and ignore the other test
procedures.
Group [n] Multiple
M
Different frame lengths
received on different links in an
IMA group.
Make sure that the IMA frame length is
set to the same value for all links.
Group [n] Multiple
Symmetry
Different group symmetry
received on different links in an
IMA group (symmetrical versus
asymmetrical operation).
Configure the group to be symmetric.
3Com PathBuilder products do not
support asymmetric bandwidth for
IMA.
Group [n] Time
Sync Fail
The far end transmit clocking
mode does not match the near
end transmit clocking mode
Check configuration. Only CTC
(Common Transfer Clock) is supported.
If the far end transport clocking is set to
ITC (Independent Transfer Clock),
change it to CTC.
IMA Protocol
Mismatch
IMA label is not ATM Forum
1.0.
Near end and far end IMA protocol
versions do no match. Check and
correct incompatibility.
IMA Remote
Loopback
Far end loopback detected,
external cable loopback or
crosstalk.
Remove loopback condition.
IMA Tx
Misconnected
ATM Forum (R-123)
The near end IMA networking
Tx or Rx link state machine
detects the link is not
connected to the correct FE Tx
or Rx links.
Remove the link and stop Tx and Rx
data.
Loss of Differential
Synchronization
(LODS)
ATM Forum (R-122)
Relative time difference
between individual T1s/E1s in
the IMA group is out of range.
LODS is declared after the Rx
IMA fails to synchronize the
IMA link(s) in an IMA group
within some time limit.
Have your carrier verify the time synch
and routing of individual T1s/E1s in the
group. Check the IMA group
configuration to ensure consistency on
the local and remote ends.
Loss of IMA Frame
(LIF)
ATM Forum (R-121
)
Loss of IMA Frame is detected
in the Rx direction for an IMA
link UP.
There is an IMA frame size
mismatch between two ends
of the circuit. This can be
caused by missing ICP cells
(ATM cells that carry protocol
information), bad IMA ID, bad
sequence number, bad M, bad
offset HEC error or CRC error
in ICP cells. This problem may
occur if the link gets noisy and
there is no AFA to prevent the
ICP from getting corrupted. It
is detected in hardware and
may or may not cause an
operational problem.
Check the IMA group configuration to
ensure consistent frame size on the
local and remote ends. Check links for
evidence of noise. Check to be sure
that AFA is enabled.
(continued)
Table 28
DS1/E1 UNI Module Alarms (continued)
Alarm
Meaning
Troubleshooting Steps