--- title: "Import .MIB files" slug: "import-mib-files" tags: ["Product Usage", "ePolicy Orchestrator – On-prem", "ePO 5.10.x", "ePO 5.10.0"] updated: 2026-09-07T17:46:26Z published: 2026-09-07T17:46:26Z canonical: "docs.trellix.com/import-mib-files" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.trellix.com/llms.txt > Use this file to discover all available pages before exploring further. # Import .MIB files Import .mib files before you set up rules to send notification messages to an SNMP server using an SNMP trap. You must import three .mib files from `\Program Files\McAfee\ePolicy Orchestrator\MIB`. The files must be imported in the following order: 1. NAI-MIB.mib 2. TVD-MIB.mib 3. EPO-MIB.mib These files allow your network management program to decode the data in the SNMP traps into meaningful text. The EPO-MIB.mib file depends on the other two files to define the following traps: - **epoThreatEvent** — This trap is sent when an Automatic Response for an ePO - On-prem Threat Event is triggered. It contains variables that match properties of the Threat event. - **epoStatusEvent** — This trap is sent when an Automatic Response for an ePO - On-prem Status Event is triggered. It contains variables that match the properties of a (Server) Status event. - **epoClientStatusEvent** — This trap is sent when an Automatic Response for an ePO - On-prem Client Status Event is triggered. It contains variables that match the properties of the Client Status event. - **epoTestEvent** — This is a test trap that is sent when you click **Send Test Trap** in the **New SNMP Server** or **Edit SNMP Server** pages. For instructions on importing and implementing .mib files, see the product documentation for your network management program.