Connector
The FireMon Connector is a lightweight agent that runs inside your network so Connect can work with systems reachable only from inside it, such as Palo Alto Panorama, VMware NSX Manager, Cisco Firewall Management Center, Fortinet FortiManager, and Infoblox Grid Manager. It makes only outbound connections, so your inbound firewall rules stay as they are.
Capabilities
| Capability | Integration | What it does |
|---|---|---|
| Group Export | Palo Alto Panorama | Pushes a Connect Group's IP addresses to your firewalls as a Dynamic Address Group (DAG), kept in sync automatically. |
| Group Export | VMware NSX | Pushes a Connect Group's IP addresses to an NSX Group, kept in sync automatically. |
| Group Export | Cisco Firewall Management Center | Pushes a Connect Group's IP addresses to an FMC dynamic object, kept in sync automatically, with no deployment needed after the first. |
| Group Export | Fortinet FortiManager | Pushes a Connect Group's IP addresses to a FortiManager address group, kept in sync automatically, and can install the policy packages that reference it. |
| Inventory Discovery | Infoblox | Reads your Grid Manager's networks and used IPs and brings them into Connect's inventory. |
See Integrations for setup details on each.
How it works
- You run the Connector inside your network: as a standalone binary on a workstation or server, as a
systemdservice on an existing Linux host, or as a VMware appliance (OVA). See Installation and Deploying the OVA appliance. - You pair it to your Connect account with a short-lived, single-use registration code generated from Settings > Connectors in Connect.
- Once paired, the Connector polls Connect for work and connects to your on-prem systems (Panorama, NSX, FMC, FortiManager, Infoblox) to carry it out. Every connection starts from the Connector.
- The Connector keeps itself up to date automatically. See Updates.
In this section
- Installation: download and pair the native binary, or install it as a Linux service
- Deploying the OVA appliance: run the Connector as a VMware virtual appliance
- Network Requirements: firewall rules, DNS, and NTP the Connector needs
- Security & Data Protection: how credentials and data are protected, and how to decommission an appliance
- Integrations: set up Panorama, VMware NSX, Cisco FMC, and FortiManager Group Export, and Infoblox Inventory Discovery
- Updates: how the Connector keeps itself current
- Troubleshooting: common issues and fixes