Cisco III System Message Guide - Page 208

Catalyst Supervisor Engine 32 PISA Cisco IOS System Message Guide, Release 12.2ZY, OL-11469-02, Messages and Recovery Procedures, MMLS Messages

Page 208 highlights

MMLS Messages Chapter 2 Messages and Recovery Procedures Error Message %MMLS-6-MMLS_EGRESS_INCAPABLE_LC_INSERTED: MMLS: Egress incapable line card ([dec]) inserted in forced egress replication mode Explanation An egress-incapable line card was inserted while the system is operating in forced egress replication mode. No multicast traffic can be sourced from this egress-incapable line card. Recommended Action Verify that there is no multicast traffic going through this egress-incapable line card. Error Message %MMLS-6-MMLS_EGRESS_INCAPABLE_LC_PRESENT: MMLS: Egress incapable line card present while forcing replication mode to egress Explanation There is at least one line card that is egress incapable in the system, but forced egress replication mode is configured on the system. Multicast traffic must not be sourced on the egress-incapable line card. Recommended Action Verify that there is no multicast traffic going through this egress-incapable line card. Error Message %MMLS-6-MMLS_LEGACY_LC_PRESENT: MMLS: Legacy line card present, system cannot operate in egress replication mode Explanation There is at least one legacy line card in the system. Because this legacy line card is present, the system cannot operate in egress replication mode if egress replication mode is configured. Recommended Action Remove the legacy line card if you want the system to operate in forced egress replication mode. Error Message %MMLS-6-RPF_ADJ_LIMIT_EXCEEDED: Failed to allocate Adjacency for multicast shortcuts with RPF-vlan: ([dec]), exceeded limit of ([dec]), subsequent flows will be software switched Explanation The maximum number of adjacencies for multicast shortcuts with the same RPF has exceeded the system limit. Any new multicast flows will be switched by the software. Recommended Action The number of multicast flows with the same RPF interface is too large to fit in the hardware. There is no workaround. Error Message %MMLS-6-RP_LIMIT_EXCEEDED: Failed to allocate DF index for Bidir-RP, exceeded limit of ([dec]) RPs for VPN: ([dec]). Shortcuts for RP: ([IP_address]) will be software switched. Explanation The system limit of four route processors per VPN has been exceeded. Multicast flows for the groups served by this RP will be switched by the software. Recommended Action The configured RPs are too large to fit in the DF table for one VPN. Attempt to configure the groups among existing RPs in the hardware, or configure the RP in another VPN. 2-178 Catalyst Supervisor Engine 32 PISA Cisco IOS System Message Guide, Release 12.2ZY OL-11469-02

  • 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
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298
  • 299
  • 300
  • 301
  • 302
  • 303
  • 304
  • 305
  • 306
  • 307
  • 308
  • 309
  • 310
  • 311
  • 312
  • 313
  • 314
  • 315
  • 316
  • 317
  • 318
  • 319
  • 320
  • 321
  • 322
  • 323
  • 324
  • 325
  • 326
  • 327
  • 328
  • 329
  • 330
  • 331
  • 332
  • 333
  • 334
  • 335
  • 336
  • 337
  • 338
  • 339
  • 340
  • 341
  • 342
  • 343
  • 344
  • 345
  • 346
  • 347
  • 348
  • 349
  • 350
  • 351
  • 352
  • 353
  • 354
  • 355
  • 356
  • 357
  • 358
  • 359
  • 360
  • 361
  • 362
  • 363
  • 364
  • 365
  • 366
  • 367
  • 368

2-178
Catalyst Supervisor Engine 32 PISA Cisco IOS System Message Guide, Release 12.2ZY
OL-11469-02
Chapter 2
Messages and Recovery Procedures
MMLS Messages
Error Message
%MMLS-6-MMLS_EGRESS_INCAPABLE_LC_INSERTED: MMLS: Egress incapable
line card ([dec]) inserted in forced egress replication mode
Explanation
An egress-incapable line card was inserted while the system is operating in forced
egress replication mode. No multicast traffic can be sourced from this egress-incapable line card.
Recommended Action
Verify that there is no multicast traffic going through this egress-incapable line
card.
Error Message
%MMLS-6-MMLS_EGRESS_INCAPABLE_LC_PRESENT: MMLS: Egress incapable line
card present while forcing replication mode to egress
Explanation
There is at least one line card that is egress incapable in the system, but forced egress
replication mode is configured on the system. Multicast traffic must not be sourced on the
egress-incapable line card.
Recommended Action
Verify that there is no multicast traffic going through this egress-incapable line
card.
Error Message
%MMLS-6-MMLS_LEGACY_LC_PRESENT: MMLS: Legacy line card present, system
cannot operate in egress replication mode
Explanation
There is at least one legacy line card in the system. Because this legacy line card is
present, the system cannot operate in egress replication mode if egress replication mode is
configured.
Recommended Action
Remove the legacy line card if you want the system to operate in forced egress
replication mode.
Error Message
%MMLS-6-RPF_ADJ_LIMIT_EXCEEDED: Failed to allocate Adjacency for
multicast shortcuts with RPF-vlan: ([dec]), exceeded limit of ([dec]), subsequent
flows will be software switched
Explanation
The maximum number of adjacencies for multicast shortcuts with the same RPF has
exceeded the system limit. Any new multicast flows will be switched by the software.
Recommended Action
The number of multicast flows with the same RPF interface is too large to fit
in the hardware. There is no workaround.
Error Message
%MMLS-6-RP_LIMIT_EXCEEDED: Failed to allocate DF index for Bidir-RP,
exceeded limit of ([dec]) RPs for VPN: ([dec]). Shortcuts for RP: ([IP_address])
will be software switched.
Explanation
The system limit of four route processors per VPN has been exceeded. Multicast flows
for the groups served by this RP will be switched by the software.
Recommended Action
The configured RPs are too large to fit in the DF table for one VPN. Attempt
to configure the groups among existing RPs in the hardware, or configure the RP in another VPN.