Hello ISAM Community
Well, working at the SNMP trap level of the Appliance may not be a topic as sexy as configuring cool AAC/Federation functionality but someone must do it, right? (-;
Lately our NMS team has upgraded their SNMP trap receiving system from a single host environment to an HA solution, and now SNMP traps are sent across a load-balancer.
Nothing to worry, right?
Well, we just found out by tracing packets that ISAM includes an empty (0.0.0.0) "agent-addr" field when configured to send trap in SNMP V1. When configured in SNMP V2C, it does not include the "agent-addr" field at all.
What happens next is that SNMP traps sent by ISAM Appliance when received in the NMS system lose the originating IP source context therefore it cannot determine from which equipment it originated thus the SNMP Trap to equipment correlation is broken.
Don't know if there was any though given when this sub-system was design and if it is too late to incorporate this? Will probably consider opening an RFE but I welcome any comments or experience sharing on this particular "boring" SNMP trap topic (-;
Sylvain