Third-Party Agent Configuration

Third-party SNMP agents require the following tasks to be completed before traps are received:

• Ensuring that Traps Are Received
• Integrating Vendor-Specific SNMP Traps

Ensuring that Traps Are Received

When configuring the SNMP agent or SNMP Remote Network Monitoring (RMON) agent on a network device, configure the agent's trap destination list (trap-target list) to include the ZfS management server station IP address or server name. Refer to the agent's documentation for information on configuring this. ConsoleOne displays alarms for all devices that forward alarms to the management server.

If your network device is using the Management Agent for NetWare, Management Agent for Windows NT Server, NetWare LANalyzer^® Agent^TM, or the LANalyzer Agent for Windows NT, the agent's trap destination list is automatically configured for you. For information on configuring the trap destination list, see Setting Up Discovery for configuration information and Understanding Traffic Analysis for information on configuring the RMON agents.

Integrating Vendor-Specific SNMP Traps

Before AMS can process the alarm, you must include vendor-specific MIBs for the third-party SNMP agents in the management server MIB pool. You can further integrate third-party SNMP agents by annotating the trap definitions in the vendor MIB.

AMS interprets ASN.1 annotations to trap definitions in a MIB to set the severity level and device status assigned to an alarm. The MIBs included with ZfS already include the proper annotations. The annotations provide detail on severity levels and device status to the AMS.

See Using the MIB Tools for information on adding a MIB to the management server's MIB pool and annotating third-party MIBs.