SNMP/4/SNMP_BLACKLIST
Possible Causes
Cause 1: The SNMP version was incorrect.
Cause 2: The SNMP packet was too long.
Cause 3: The PDU decoding was incorrect.
Cause 4: ACL rules denied the connection request.
Cause 5: The buffer was insufficient for processing the connection request sent from the NMS.
Cause 6: The group or user name was incorrect.
Cause 7: Authentication or authorization parameters were incorrect.
Cause 8: The trap failed to be sent because VBs were lost or the VB packet size was too small.
Cause 9: No response packets for Inform packets were received.
Cause 10: The proxy failed to perform the Set, Get, GetNext, or GetBulk action.
Procedure
- Cause 1: The SNMP version was incorrect.
Check the SNMP version used on the device.
- Cause 2: The SNMP packet was too long.
Increase the maximum packet length that the SNMP proxy can process.
- Cause 3: The PDU decoding was incorrect.
This log is informational only, and no action is required.
- Cause 4: ACL rules denied the connection request.
Check whether ACL rules are applied for group or user names.
- Cause 5: The buffer was insufficient for processing the
connection request sent from the NMS.
Increase the buffer space.
- Cause 6: The group or user name was incorrect.
Check whether the configured group and user names are correct. If they are incorrect, correct them.
- Cause 7: Authentication or authorization parameters were
incorrect.
Check whether the user name and password are correct and whether the user name and password are correctly entered.
- Cause 8: The trap failed to be sent because VBs were lost
or the VB packet size was too small.
Add VBs or increase the VB packet length.
- Cause 9: No response packets for Inform packets were received.
This log is informational only, and no action is required.
- Cause 10: The proxy failed to perform the Set, Get, GetNext,
or GetBulk action.
This log is informational only, and no action is required.
Previous
