Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document.
Note: Even the most advanced machine translation cannot match the quality of professional translators.
Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
MCAST/4/FIB
Message
MCAST/4/FIB: There is no free FIB (forwarding mode=[STRING]) index to add a new FIB node (ModId=[ULONG],McIndex=[ULONG],DetailInfo=[STRING]).
Description
The number of multicast forwarding entries has reached the upper limit, and no more new entries can be created.
Parameters
| Parameter Name | Parameter Meaning |
|---|---|
| forwarding mode | Indicates the multicast forwarding mode:
|
| ModId | Indicates the index of a multicast forwarding entry. |
| McIndex | Indicates an index block ID. |
| DetailInfo | Operation information:
|
Possible Causes
The number of multicast forwarding entries has reached the upper limit. Or the resource application failed.
Procedure
- Run the display
multicast forwarding-table command to check the Layer 3 forwarding table or run the display
l2-multicast forwarding-table command to check Layer
2 multicast forwarding table. Determine whether the number of multicast
entries exceeds the product specification. For
the product specifications, log in to Huawei official website to download
the product brochure or product feature list for channel (if your
account is unauthorized, contact Huawei local office).
- If yes, go to step 2.
- If no, the resource application may have failed. Go to step 3.
- Run the reset multicast forwarding-table [ group-address | source-address ] command to delete redundant Layer 3 multicast forwarding entries. Or run the reset igmp-snooping group vlan [ vlan-id ] group-address [ group-address ] command to delete redundant Layer 2 multicast forwarding entries. Then re-configure multicast services. If this log persists, go to step 3.
- Collect log information and configuration information, and then contact technical support personnel. You can collect diagnostic information using the display diagnostic-information command.
