SW_SNPG
SW_SNPG_1.3.6.1.4.1.2011.5.25.44.99.1 hwCfgRefreshFailAlarm
Description
SW_SNPG/2/REFRESHFAIL:OID [OID] Failed to refresh multicast table. (Index=[INTEGER], Vlan=[OCTET])
Layer 2 multicast forwarding entries failed to be delivered to the chip.
Attribute
| Alarm ID | Alarm Severity | Alarm Type |
|---|---|---|
1.3.6.1.4.1.2011.5.25.44.99.1 |
Major |
processingErrorAlarm(4) |
Parameters
| Name | Meaning |
|---|---|
OID |
Indicates the MIB object ID of the alarm. |
Index |
Indicates the index of a multicast forwarding entry. |
Vlan |
Indicates the ID of the VLAN to which the multicast forwarding entry belongs. |
Possible Causes
Cause 1: The system does not have sufficient memory and therefore cannot allocate memory to the multicast service module.
Cause 2: The number of multicast forwarding entries in the system has reached the upper limit, and new entries cannot be created.
Procedure
- Cause 1: The system does not have sufficient memory and therefore cannot allocate memory to the multicast service module.
Run the display memory-usage command to check the memory usage. If the command output shows that the system memory has been used up, delete unnecessary services to release memory. If the memory has not been used up, go to step 2.
Collect trap, log, and configuration information, and contact technical support personnel.
- Cause 2: The number of multicast forwarding entries in the system has reached the upper limit, and new entries cannot be created.
Run the display l2-multicast forwarding-table command to check Layer 2 multicast forwarding entries in the system. If the command output shows that the number of Layer 2 multicast forwarding entries has reached the upper limit, go to step 2. If not, go to step 3.
Manually update Layer 2 multicast forwarding entries and delete unnecessary entries.
If the Layer 2 multicast forwarding entries are dynamically generated through IGMP snooping, run the reset igmp-snooping group command to update the entries. This command will cause temporary interruption of multicast forwarding. Exercise caution when deciding to use the command.
To delete unnecessary static Layer 2 multicast forwarding entries, run the undo l2-multicast static-group command.
Collect trap, log, and configuration information, and contact technical support personnel.
SW_SNPG_1.3.6.1.4.1.2011.5.25.44.99.2 hwMCastTableLoadAbnormalNotify
Description
SW_SNPG/4/NOTIFYTRAP:[OID] Multicast table of router was full.
The number of Layer 2 multicast forwarding entries has reached the maximum number allowed by the system.
Attribute
| Alarm ID | Alarm Severity | Alarm Type |
|---|---|---|
| 1.3.6.1.4.1.2011.5.25.44.99.2 | Warning | equipmentAlarm(5) |
Impact on the System
New multicast forwarding entries cannot be configured or learned on the switch.
Possible Causes
The total number of Layer 2 multicast forwarding entries exceeds 90% of the upper limit.
Procedure
- Run the display igmp-snooping port-info command
to view forwarding entries of all multicast groups, and then check
whether unnecessary static multicast entries exist.
If so, go to step 2.
If not, go to step 4.
- Run the undo
l2-multicast static-group group-address
x.x.x.x command to delete unnecessary multicast entries
and check whether the alarm hwMCastTableLoadAbnormalResume is generated.
If so, go to step 4.
If not, go to step 3.
- Collect trap, log, and configuration information, and contact technical support personnel.
- End.
SW_SNPG_1.3.6.1.4.1.2011.5.25.44.99.3 hwMCastTableLoadAbnormalResume
Description
SW_SNPG/4/NOTIFYTRAP:[OID] Multicast table of router was normal.
The number of Layer 2 multicast forwarding entries has dropped below the recovery threshold.
Attribute
| Alarm ID | Alarm Severity | Alarm Type |
|---|---|---|
| 1.3.6.1.4.1.2011.5.25.44.99.3 | Warning |
equipmentAlarm(5) |
Possible Causes
Cause 1:
After the number of Layer 2 multicast forwarding entries exceeded 90% of the upper limit, some entries were manually deleted. The number of Layer 2 multicast forwarding entries then dropped below 80% of the upper limit.
Cause 2:
After the number of Layer 2 multicast forwarding entries exceeded 90% of the upper limit, some entries were aged out or some group members left multicast groups. The number of Layer 2 multicast forwarding entries then dropped below 80% of the upper limit.