M-Series Appliance Interfaces
Table of Contents
9.1 (EoL)
Expand all | Collapse all
-
- Determine Panorama Log Storage Requirements
-
- Setup Prerequisites for the Panorama Virtual Appliance
- Perform Initial Configuration of the Panorama Virtual Appliance
- Set Up The Panorama Virtual Appliance as a Log Collector
- Set Up the Panorama Virtual Appliance with Local Log Collector
- Set up a Panorama Virtual Appliance in Panorama Mode
- Set up a Panorama Virtual Appliance in Management Only Mode
-
- Preserve Existing Logs When Adding Storage on Panorama Virtual Appliance in Legacy Mode
- Add a Virtual Disk to Panorama on an ESXi Server
- Add a Virtual Disk to Panorama on vCloud Air
- Add a Virtual Disk to Panorama on AWS
- Add a Virtual Disk to Panorama on Azure
- Add a Virtual Disk to Panorama on Google Cloud Platform
- Add a Virtual Disk to Panorama on KVM
- Add a Virtual Disk to Panorama on Hyper-V
- Mount the Panorama ESXi Server to an NFS Datastore
-
- Increase CPUs and Memory for Panorama on an ESXi Server
- Increase CPUs and Memory for Panorama on vCloud Air
- Increase CPUs and Memory for Panorama on AWS
- Increase CPUs and Memory for Panorama on Azure
- Increase CPUs and Memory for Panorama on Google Cloud Platform
- Increase CPUs and Memory for Panorama on KVM
- Increase CPUs and Memory for Panorama on Hyper-V
- Complete the Panorama Virtual Appliance Setup
-
- Convert Your Evaluation Panorama to a Production Panorama with Local Log Collector
- Convert Your Evaluation Panorama to a Production Panorama without Local Log Collector
- Convert Your Evaluation Panorama to VM-Flex Licensing with Local Log Collector
- Convert Your Evaluation Panorama to VM-Flex Licensing without Local Log Collector
- Convert Your Production Panorama to an ELA Panorama
-
- Register Panorama
- Activate a Panorama Support License
- Activate/Retrieve a Firewall Management License when the Panorama Virtual Appliance is Internet-connected
- Activate/Retrieve a Firewall Management License when the Panorama Virtual Appliance is not Internet-connected
- Activate/Retrieve a Firewall Management License on the M-Series Appliance
- Install the Panorama Device Certificate
-
- Migrate from a Panorama Virtual Appliance to an M-Series Appliance
- Migrate a Panorama Virtual Appliance to a Different Hypervisor
- Migrate from an M-Series Appliance to a Panorama Virtual Appliance
- Migrate from an M-100 Appliance to an M-500 Appliance
- Migrate from an M-100 or M-500 Appliance to an M-200 or M-600 Appliance
-
- Configure an Admin Role Profile
- Configure an Access Domain
-
- Configure a Panorama Administrator Account
- Configure Local or External Authentication for Panorama Administrators
- Configure a Panorama Administrator with Certificate-Based Authentication for the Web Interface
- Configure an Administrator with SSH Key-Based Authentication for the CLI
- Configure RADIUS Authentication for Panorama Administrators
- Configure TACACS+ Authentication for Panorama Administrators
- Configure SAML Authentication for Panorama Administrators
-
- Add a Firewall as a Managed Device
-
- Add a Device Group
- Create a Device Group Hierarchy
- Create Objects for Use in Shared or Device Group Policy
- Revert to Inherited Object Values
- Manage Unused Shared Objects
- Manage Precedence of Inherited Objects
- Move or Clone a Policy Rule or Object to a Different Device Group
- Push a Policy Rule to a Subset of Firewalls
- Manage the Rule Hierarchy
- Manage the Master Key from Panorama
- Redistribute User-ID Information to Managed Firewalls
-
- Plan the Transition to Panorama Management
- Migrate a Firewall to Panorama Management and Reuse Existing Configuration
- Migrate a Firewall to Panorama Management and Push a New Configuration
- Migrate a Firewall HA Pair to Panorama Management and Reuse Existing Configuration
- Migrate a Firewall HA Pair to Panorama Management and Push a New Configuration
- Load a Partial Firewall Configuration into Panorama
- Localize a Panorama Pushed Configuration on a Managed Firewall
-
- Add Standalone WildFire Appliances to Manage with Panorama
- Configure Basic WildFire Appliance Settings on Panorama
- Remove a WildFire Appliance from Panorama Management
-
-
- Configure a Cluster and Add Nodes on Panorama
- Configure General Cluster Settings on Panorama
- Remove a Cluster from Panorama Management
- Configure Appliance-to-Appliance Encryption Using Predefined Certificates Centrally on Panorama
- Configure Appliance-to-Appliance Encryption Using Custom Certificates Centrally on Panorama
- View WildFire Cluster Status Using Panorama
- Upgrade a Cluster Centrally on Panorama with an Internet Connection
- Upgrade a Cluster Centrally on Panorama without an Internet Connection
-
-
- Manage Licenses on Firewalls Using Panorama
-
- Supported Updates
- Schedule a Content Update Using Panorama
- Upgrade Log Collectors When Panorama Is Internet-Connected
- Upgrade Log Collectors When Panorama Is Not Internet-Connected
- Upgrade Firewalls When Panorama Is Internet-Connected
- Upgrade Firewalls When Panorama Is Not Internet-Connected
- Upgrade a ZTP Firewall
- Revert Content Updates from Panorama
-
- Preview, Validate, or Commit Configuration Changes
- Enable Automated Commit Recovery
- Compare Changes in Panorama Configurations
- Manage Locks for Restricting Configuration Changes
- Add Custom Logos to Panorama
- Use the Panorama Task Manager
- Reboot or Shut Down Panorama
- Configure Panorama Password Profiles and Complexity
-
-
- Verify Panorama Port Usage
- Resolve Zero Log Storage for a Collector Group
- Replace a Failed Disk on an M-Series Appliance
- Replace the Virtual Disk on an ESXi Server
- Replace the Virtual Disk on vCloud Air
- Migrate Logs to a New M-Series Appliance in Log Collector Mode
- Migrate Logs to a New M-Series Appliance in Panorama Mode
- Migrate Logs to a New M-Series Appliance Model in Panorama Mode in High Availability
- Migrate Logs to the Same M-Series Appliance Model in Panorama Mode in High Availability
- Migrate Log Collectors after Failure/RMA of Non-HA Panorama
- Regenerate Metadata for M-Series Appliance RAID Pairs
- Troubleshoot Registration or Serial Number Errors
- Troubleshoot Reporting Errors
- Troubleshoot Device Management License Errors
- Troubleshoot Automatically Reverted Firewall Configurations
- Complete Content Update When Panorama HA Peer is Down
- View Task Success or Failure Status
- Restore an Expired Device Certificate
- Downgrade from Panorama 9.1
End-of-Life (EoL)
M-Series Appliance Interfaces
The Panorama M-600, M-500, M-200 and M-100 appliances
have several interfaces for communicating with other systems such
as managed firewalls and the client systems of Panorama administrators.
Panorama communicates with these systems to perform various services,
including managing devices (firewalls, Log Collectors, and WildFire
appliances and appliance clusters), collecting logs, communicating
with Collector Groups, deploying software and content updates to
devices, and providing administrative access to Panorama. By default,
Panorama uses its management (MGT) interface for all these services.
However, you can improve security by reserving the MGT interface
for administrative access and dedicating separate interfaces for
the other services. In a large-scale network with multiple subnetworks
and heavy log traffic, using multiple interfaces for device management
and log collection also enables network segmentation and load balancing
(see Configure
Panorama to Use Multiple Interfaces).
When assigning Panorama services to various interfaces, keep
in mind that only the MGT interface allows administrative access
to Panorama for configuration and monitoring tasks. You can assign
any interface to the other services when you Perform
Initial Configuration of the M-Series Appliance. The M-Series
Appliance Hardware Reference Guides explain where to attach
cables for the interfaces. The M-100 appliance support 1Gbps throughput
on all its interfaces: MGT, Eth1, Eth2, and Eth3. In addition to
these interfaces, the M-500 appliance supports 10Gbps throughput
on its Eth4 and Eth5 interfaces.
The M-Series appliances do not support Link Aggregation
Control Protocol (LACP) for aggregating interfaces.
Supported Interfaces
Interfaces can be used for device management, log collection,
Collector Group communication, licensing and software updates. See Configure Panorama to Use Multiple Interfaces for more
information on network segmentation.
Interface | Maximum Speed | M-600 Appliance | M-500 Appliance | M-200 Appliance | M-100 Appliance |
---|---|---|---|---|---|
Management (MGT) | 1Gbps | ||||
Ethernet 1 (Eth1) | 1Gbps | ||||
Ethernet 2 (Eth2) | 1Gbps | ||||
Ethernet 3 (Eth3) | 1Gbps | ||||
Ethernet 4 (Eth4) | 10Gbps | — | — | ||
Ethernet 5 (Eth5) | 10Gbps | — | — |
Logging Rates
Review the logging rates for the all M-Series appliance
models. To achieve the logging rates listed below, the M-Series
appliance must be a single log collector in a collector group and
you must install all the logging disks for your M-Series model. For
example, to achieve 30,000 logs/second for the M-500 appliance,
you must install all 12 logging disks with either 1TB or 2TB disks.
Model Capacities and
Features | M-600 Appliance | M-500 Appliance | M-200 Appliance | M-100 Appliance |
---|---|---|---|---|
Maximum Logging Rate for Panorama in Management Only
mode | Local log storage is not supported | |||
Maximum Logging Rate for Panorama in Panorama
Mode | 25,000 logs/second | 20,000 logs/second | 10,000 logs/second | 10,000 logs/second |
Maximum Logging Rate for Panorama in Log
Collector Mode | 50,000 logs/second | 30,000 logs/second | 28,000 logs/second | 18,000 logs/second |
Maximum Log Storage on Appliance | 48TB (12x8TB RAID disk) |
| 16TB (4x8TB RAID disk) |
|
Default Log Storage on Appliance | 16TB (4x8TB RAID disks) | 4TB (4x2TB RAID disks) | 16TB (4x8TB RAID disks) | 2TB (2x2TB RAID disks) |
SSD Storage on Appliance (for logs that
M-Series appliances generate) | 240GB | 240GB | 240GB | 120GB |
NFS Attached Log Storage | Not available |