🛠️ Deployment Options
1. Centralized Deployment
Uses one Panorama instance (or HA pair) for both management and log collection functions. Suitable for small to mid-size environments or where log volume is manageable.
2. Distributed Deployment
Separates management and logging onto different Panorama instances (physical or virtual) for enhanced scalability and performance, especially in large environments:
-
Panorama in Management Only Mode manages devices and policies.
-
Dedicated Log Collectors (Panorama in Log Collector Mode or M-Series appliances) handle log storage, aggregation, and querying.
3. High Availability (HA)
-
Uses an Active/Passive pair of Panorama nodes (same model and mode).
-
Configuration, logs (if applicable), and reporting data are synchronized between peers.
-
Provides failover capability to maintain management and/or logging availability if one node fails.
📊 Mermaid Diagram: Panorama Log Flow and Component Interaction
This sequence diagram illustrates how Panorama components like the management server and log collectors interact with firewalls and administrators:
sequenceDiagram
participant Admin
participant Panorama as Panorama (Management Server)
participant FW as Firewall
participant LC as Log Collector
Admin->>Panorama: Push policies and config via Commit
Panorama->>FW: Deploy configuration and policies
FW-->>Panorama: Acknowledge deployment status
FW->>LC: Send logs (Traffic, Threat, Config, etc.)
LC-->>Panorama: Forward logs (optional) or Index logs
Admin->>Panorama: Query logs/generate reports
Panorama->>LC: Request logs for query
LC-->>Panorama: Return requested log data
Panorama-->>Admin: Display logs and reports