Refresh HA1 SSH Keys and Configure Key Options
Table of Contents
Expand All
|
Collapse All
Next-Generation Firewall Docs
-
PAN-OS 9.1 (EoL)
- PAN-OS 11.1 & Later
- PAN-OS 11.0 (EoL)
- PAN-OS 10.2
- PAN-OS 10.1
- PAN-OS 10.0 (EoL)
- PAN-OS 9.1 (EoL)
- Cloud Management of NGFWs
-
- Management Interfaces
-
- Launch the Web Interface
- Configure Banners, Message of the Day, and Logos
- Use the Administrator Login Activity Indicators to Detect Account Misuse
- Manage and Monitor Administrative Tasks
- Commit, Validate, and Preview Firewall Configuration Changes
- Export Configuration Table Data
- Use Global Find to Search the Firewall or Panorama Management Server
- Manage Locks for Restricting Configuration Changes
-
-
- Define Access to the Web Interface Tabs
- Provide Granular Access to the Monitor Tab
- Provide Granular Access to the Policy Tab
- Provide Granular Access to the Objects Tab
- Provide Granular Access to the Network Tab
- Provide Granular Access to the Device Tab
- Define User Privacy Settings in the Admin Role Profile
- Restrict Administrator Access to Commit and Validate Functions
- Provide Granular Access to Global Settings
- Provide Granular Access to the Panorama Tab
- Panorama Web Interface Access Privileges
-
- Reset the Firewall to Factory Default Settings
-
- Plan Your Authentication Deployment
- Configure SAML Authentication
- Configure Kerberos Single Sign-On
- Configure Kerberos Server Authentication
- Configure TACACS+ Authentication
- Configure RADIUS Authentication
- Configure LDAP Authentication
- Configure Local Database Authentication
- Configure an Authentication Profile and Sequence
- Test Authentication Server Connectivity
- Troubleshoot Authentication Issues
-
- Keys and Certificates
- Default Trusted Certificate Authorities (CAs)
- Certificate Deployment
- Configure the Master Key
- Export a Certificate and Private Key
- Configure a Certificate Profile
- Configure an SSL/TLS Service Profile
- Replace the Certificate for Inbound Management Traffic
- Configure the Key Size for SSL Forward Proxy Server Certificates
-
- HA Overview
-
- Prerequisites for Active/Active HA
- Configure Active/Active HA
-
- Use Case: Configure Active/Active HA with Route-Based Redundancy
- Use Case: Configure Active/Active HA with Floating IP Addresses
- Use Case: Configure Active/Active HA with ARP Load-Sharing
- Use Case: Configure Active/Active HA with Floating IP Address Bound to Active-Primary Firewall
- Use Case: Configure Active/Active HA with Source DIPP NAT Using Floating IP Addresses
- Use Case: Configure Separate Source NAT IP Address Pools for Active/Active HA Firewalls
- Use Case: Configure Active/Active HA for ARP Load-Sharing with Destination NAT
- Use Case: Configure Active/Active HA for ARP Load-Sharing with Destination NAT in Layer 3
- Refresh HA1 SSH Keys and Configure Key Options
- HA Firewall States
- Reference: HA Synchronization
-
- Use the Dashboard
- Monitor Applications and Threats
- Monitor Block List
-
- Report Types
- View Reports
- Configure the Expiration Period and Run Time for Reports
- Disable Predefined Reports
- Custom Reports
- Generate Custom Reports
- Generate the SaaS Application Usage Report
- Manage PDF Summary Reports
- Generate User/Group Activity Reports
- Manage Report Groups
- Schedule Reports for Email Delivery
- Manage Report Storage Capacity
- View Policy Rule Usage
- Use External Services for Monitoring
- Configure Log Forwarding
- Configure Email Alerts
-
- Configure Syslog Monitoring
-
- Traffic Log Fields
- Threat Log Fields
- URL Filtering Log Fields
- Data Filtering Log Fields
- HIP Match Log Fields
- IP-Tag Log Fields
- User-ID Log Fields
- Tunnel Inspection Log Fields
- SCTP Log Fields
- Authentication Log Fields
- Config Log Fields
- System Log Fields
- Correlated Events Log Fields
- GTP Log Fields
- Syslog Severity
- Custom Log/Event Format
- Escape Sequences
- Forward Logs to an HTTP/S Destination
- Firewall Interface Identifiers in SNMP Managers and NetFlow Collectors
-
- User-ID Overview
- Enable User-ID
- Map Users to Groups
- Enable User- and Group-Based Policy
- Enable Policy for Users with Multiple Accounts
- Verify the User-ID Configuration
-
- App-ID Overview
- App-ID and HTTP/2 Inspection
- Manage Custom or Unknown Applications
-
- Apply Tags to an Application Filter
- Create Custom Application Tags
- Workflow to Best Incorporate New and Modified App-IDs
- See the New and Modified App-IDs in a Content Release
- See How New and Modified App-IDs Impact Your Security Policy
- Ensure Critical New App-IDs are Allowed
- Monitor New App-IDs
- Disable and Enable App-IDs
- Safely Enable Applications on Default Ports
- Applications with Implicit Support
- Application Level Gateways
- Disable the SIP Application-level Gateway (ALG)
- Maintain Custom Timeouts for Data Center Applications
-
- Best Practices for Securing Your Network from Layer 4 and Layer 7 Evasions
- Set Up Antivirus, Anti-Spyware, and Vulnerability Protection
- Set Up File Blocking
- Prevent Brute Force Attacks
- Customize the Action and Trigger Conditions for a Brute Force Signature
- Enable Evasion Signatures
- Monitor Blocked IP Addresses
- Threat Signature Categories
- Create Threat Exceptions
- Custom Signatures
- Threat Prevention Resources
-
- Decryption Overview
-
- Keys and Certificates for Decryption Policies
- SSL Forward Proxy
- SSL Forward Proxy Decryption Profile
- SSL Inbound Inspection
- SSL Inbound Inspection Decryption Profile
- SSL Protocol Settings Decryption Profile
- SSH Proxy
- SSH Proxy Decryption Profile
- Decryption Profile for No Decryption
- SSL Decryption for Elliptical Curve Cryptography (ECC) Certificates
- Perfect Forward Secrecy (PFS) Support for SSL Decryption
- SSL Decryption and Subject Alternative Names (SANs)
- High Availability Support for Decrypted Sessions
- Decryption Mirroring
- Configure SSL Forward Proxy
- Configure SSL Inbound Inspection
- Configure SSH Proxy
- Configure Server Certificate Verification for Undecrypted Traffic
- Enable Users to Opt Out of SSL Decryption
- Temporarily Disable SSL Decryption
- Configure Decryption Port Mirroring
- Verify Decryption
-
- How Decryption Broker Works
- Layer 3 Security Chain Guidelines
- Configure Decryption Broker with One or More Layer 3 Security Chain
- Transparent Bridge Security Chain Guidelines
- Configure Decryption Broker with a Single Transparent Bridge Security Chain
- Configure Decryption Broker with Multiple Transparent Bridge Security Chains
- Activate Free Licenses for Decryption Features
-
- About Palo Alto Networks URL Filtering Solution
- How Advanced URL Filtering Works
- URL Filtering Use Cases
- Plan Your URL Filtering Deployment
- URL Filtering Best Practices
- Activate The Advanced URL Filtering Subscription
- Configure URL Filtering
- Test URL Filtering Configuration
- Log Only the Page a User Visits
- Create a Custom URL Category
- URL Category Exceptions
- Use an External Dynamic List in a URL Filtering Profile
- Allow Password Access to Certain Sites
- URL Filtering Response Pages
- Customize the URL Filtering Response Pages
- HTTP Header Logging
- Request to Change the Category for a URL
-
-
- Tap Interfaces
-
- Layer 2 and Layer 3 Packets over a Virtual Wire
- Port Speeds of Virtual Wire Interfaces
- LLDP over a Virtual Wire
- Aggregated Interfaces for a Virtual Wire
- Virtual Wire Support of High Availability
- Zone Protection for a Virtual Wire Interface
- VLAN-Tagged Traffic
- Virtual Wire Subinterfaces
- Configure Virtual Wires
- Configure an Aggregate Interface Group
- Use Interface Management Profiles to Restrict Access
- Virtual Routers
- Service Routes
- RIP
- Route Redistribution
-
- DNS Overview
- DNS Proxy Object
- DNS Server Profile
- Multi-Tenant DNS Deployments
- Configure a DNS Proxy Object
- Configure a DNS Server Profile
- Use Case 1: Firewall Requires DNS Resolution
- Use Case 2: ISP Tenant Uses DNS Proxy to Handle DNS Resolution for Security Policies, Reporting, and Services within its Virtual System
- Use Case 3: Firewall Acts as DNS Proxy Between Client and Server
- DNS Proxy Rule and FQDN Matching
- Dynamic DNS Overview
- Configure Dynamic DNS for Firewall Interfaces
-
- NAT Rule Capacities
- Dynamic IP and Port NAT Oversubscription
- Dataplane NAT Memory Statistics
-
- Translate Internal Client IP Addresses to Your Public IP Address (Source DIPP NAT)
- Enable Clients on the Internal Network to Access your Public Servers (Destination U-Turn NAT)
- Enable Bi-Directional Address Translation for Your Public-Facing Servers (Static Source NAT)
- Configure Destination NAT with DNS Rewrite
- Configure Destination NAT Using Dynamic IP Addresses
- Modify the Oversubscription Rate for DIPP NAT
- Reserve Dynamic IP NAT Addresses
- Disable NAT for a Specific Host or Interface
-
-
- Policy Types
- Policy Objects
- Track Rules Within a Rulebase
- Enforce Policy Rule Description, Tag, and Audit Comment
- Move or Clone a Policy Rule or Object to a Different Virtual System
-
- External Dynamic List
- Built-in External Dynamic Lists
- Configure the Firewall to Access an External Dynamic List
- Retrieve an External Dynamic List from the Web Server
- View External Dynamic List Entries
- Exclude Entries from an External Dynamic List
- Enforce Policy on an External Dynamic List
- Find External Dynamic Lists That Failed Authentication
- Disable Authentication for an External Dynamic List
- Register IP Addresses and Tags Dynamically
- Use Dynamic User Groups in Policy
- Use Auto-Tagging to Automate Security Actions
- CLI Commands for Dynamic IP Addresses and Tags
- Application Override Policy
- Test Policy Rules
-
PAN-OS 11.1 & Later
- PAN-OS 11.1 & Later
- PAN-OS 11.0 (EoL)
- PAN-OS 10.2
- PAN-OS 10.1
-
- Tap Interfaces
-
- Layer 2 and Layer 3 Packets over a Virtual Wire
- Port Speeds of Virtual Wire Interfaces
- LLDP over a Virtual Wire
- Aggregated Interfaces for a Virtual Wire
- Virtual Wire Support of High Availability
- Zone Protection for a Virtual Wire Interface
- VLAN-Tagged Traffic
- Virtual Wire Subinterfaces
- Configure Virtual Wires
- Configure a PPPoE Client on a Subinterface
- Configure an IPv6 PPPoE Client
- Configure an Aggregate Interface Group
- Configure Bonjour Reflector for Network Segmentation
- Use Interface Management Profiles to Restrict Access
-
- DHCP Overview
- Firewall as a DHCP Server and Client
- Firewall as a DHCPv6 Client
- DHCP Messages
- Dynamic IPv6 Addressing on the Management Interface
- Configure an Interface as a DHCP Server
- Configure an Interface as a DHCPv4 Client
- Configure an Interface as a DHCPv6 Client with Prefix Delegation
- Configure the Management Interface as a DHCP Client
- Configure the Management Interface for Dynamic IPv6 Address Assignment
- Configure an Interface as a DHCP Relay Agent
-
- DNS Overview
- DNS Proxy Object
- DNS Server Profile
- Multi-Tenant DNS Deployments
- Configure a DNS Proxy Object
- Configure a DNS Server Profile
- Use Case 1: Firewall Requires DNS Resolution
- Use Case 2: ISP Tenant Uses DNS Proxy to Handle DNS Resolution for Security Policies, Reporting, and Services within its Virtual System
- Use Case 3: Firewall Acts as DNS Proxy Between Client and Server
- DNS Proxy Rule and FQDN Matching
-
- NAT Rule Capacities
- Dynamic IP and Port NAT Oversubscription
- Dataplane NAT Memory Statistics
-
- Translate Internal Client IP Addresses to Your Public IP Address (Source DIPP NAT)
- Create a Source NAT Rule with Persistent DIPP
- PAN-OS
- Strata Cloud Manager
- Enable Clients on the Internal Network to Access your Public Servers (Destination U-Turn NAT)
- Enable Bi-Directional Address Translation for Your Public-Facing Servers (Static Source NAT)
- Configure Destination NAT with DNS Rewrite
- Configure Destination NAT Using Dynamic IP Addresses
- Modify the Oversubscription Rate for DIPP NAT
- Reserve Dynamic IP NAT Addresses
- Disable NAT for a Specific Host or Interface
-
- Network Packet Broker Overview
- How Network Packet Broker Works
- Prepare to Deploy Network Packet Broker
- Configure Transparent Bridge Security Chains
- Configure Routed Layer 3 Security Chains
- Network Packet Broker HA Support
- User Interface Changes for Network Packet Broker
- Limitations of Network Packet Broker
- Troubleshoot Network Packet Broker
-
- Enable Advanced Routing
- Logical Router Overview
- Configure a Logical Router
- Create a Static Route
- Configure BGP on an Advanced Routing Engine
- Create BGP Routing Profiles
- Create Filters for the Advanced Routing Engine
- Configure OSPFv2 on an Advanced Routing Engine
- Create OSPF Routing Profiles
- Configure OSPFv3 on an Advanced Routing Engine
- Create OSPFv3 Routing Profiles
- Configure RIPv2 on an Advanced Routing Engine
- Create RIPv2 Routing Profiles
- Create BFD Profiles
- Configure IPv4 Multicast
- Configure MSDP
- Create Multicast Routing Profiles
- Create an IPv4 MRoute
-
-
PAN-OS 11.2
- PAN-OS 11.2
- PAN-OS 11.1
- PAN-OS 11.0 (EoL)
- PAN-OS 10.2
- PAN-OS 10.1
- PAN-OS 10.0 (EoL)
- PAN-OS 9.1 (EoL)
- PAN-OS 9.0 (EoL)
- PAN-OS 8.1 (EoL)
- Cloud Management and AIOps for NGFW
End-of-Life (EoL)
Refresh HA1 SSH Keys and Configure Key Options
If you enable encryption over the HA1 control link, you
can refresh the SSH host keys, change various key options, and reestablish
HA1 sessions between HA peers without restarting the peers.
When you configure active/passive or active/active high availability
(HA), you can enable encryption for the HA1 (control link) connection
between HA firewalls. You may want to secure the HA1 traffic between
HA peers with encryption if the firewalls aren’t located in the
same site.
All Palo Alto Networks firewalls come with Secure
Shell (SSH) pre-configured, and the HA firewalls can act as both
SSH server and SSH client simultaneously. If you enable encryption
on the HA1 control link, you can use the CLI commands that follow
to secure the connection between the HA firewalls. You can change
the default host key type, generate
a new pair of public and private SSH host keys for the HA1 control
link, and configure other HA1 encryption settings. You can enable
the firewalls to use the new host keys and the following settings
without restarting the HA peers, thus avoiding your firewalls going
offline. The firewall reestablishes HA1 sessions with its peer to
synchronize the new SSH key and other settings and also generates
system logs (subtype is ha) for reestablishing
HA1 and HA1-backup sessions.
The following examples show how
to refresh (regenerate) your HA1 SSH keys and change and display
various SSH settings for the HA1 control link after you enable encryption
and access the CLI.
You
must enable encryption and it must be functioning properly on an
HA pair before you can perform the following tasks.
If
you are configuring the HA1 control link with encryption in FIPS-CC mode, you must
set automatic rekeying parameters for session keys.
To
use the same SSH connection settings for each Dedicated Log Collector
(M-series or Panorama™ virtual appliance in Log Collector mode)
in a Collector Group, configure
the settings from the Panorama management server, Commit the changes to Panorama, and then Push the
configuration to the Log Collectors. You can use the set log-collector-group <name> general-setting management ssh commands.
- (Optional) Set the default
host key type.If you enable encryption on the HA1 control link, the firewall uses a default host key type of RSA 2048 unless you change it. The HA1 SSH connection uses only the default host key type to authenticate the HA peers (before an encrypted session is established between them). You can change the default host key type; the choices are ECDSA 256, 384, or 521, or RSA 2048, 3072, or 4096. Change the default host key type if you prefer a longer RSA key length or if you prefer ECDSA rather than RSA. This example sets the default host key type to an ECDSA key of 256 bits. It also reestablishes the HA1 connection using the new host key without restarting the HA peers.
- admin@PA-3250> configure
- admin@PA-3250# set deviceconfig system ssh default-hostkey ha key-type ECDSA key-length 256
- admin@PA-3250# commit
- admin@PA-3250# exit
- admin@PA-3250> request high-availability sync-to-remote ssh-keyAn HA connection must already be established between the HA firewalls. If the firewalls have not yet established an HA connection, you must enable encryption on the control link connection, export the HA key to a network location and import the HA key on the peer. See Configure Active/Passive HA or Configure Active/Active HA.
- (HA1 Backup is configured) admin@PA-3250> request high-availability session-reestablish
- (No HA1 Backup is configured or HA1 Backup link
is down) admin@PA-3250> request high-availability session-reestablish forceYou can force the firewall to reestablish HA1 sessions if there is no HA1 backup, which causes a brief split-brain condition between the two HA peers. (Using the force option when an HA1 backup is configured has no effect.)
- admin@PA-3250> configure
- admin@PA-3250# show deviceconfig system ssh default-hostkey
- Establish when automatic rekeying of the session keys
occurs for SSH over the HA1 control link by setting parameters.The session keys are used for encrypting the traffic between the HA peers. After any one rekeying parameter reaches its configured value, SSH uses the new session encryption keys. The parameters are data, interval (seconds), and packet count. If you set more than one parameter, rekeying occurs when the first parameter reaches its configured value and then the firewall resets all rekeying parameters. You can set a second or third parameter if you aren’t sure that one parameter you configured will reach its specified value as soon as you want rekeying to occur.
- admin@PA-3250> configure
- admin@PA-3250# set deviceconfig system ssh session-rekey ha data 32Rekeying occurs after the volume of data (in megabytes) is transmitted following the previous rekeying. The default is based on the type of cipher you use and ranges from 1GB to 4GB; the range is 10MB to 4,000MB. Alternatively, you can use the set deviceconfig system ssh session-rekey ha data default command, which sets the data parameter to the default value of the individual cipher you are using.If you are configuring the HA1 control link with encryption in FIPS-CC mode, you must set a data value (you cannot let it default) and the value must be no greater than 1000MB.
- admin@PA-3250# set deviceconfig system ssh session-rekey ha interval 3600Rekeying occurs after the specified time interval (in seconds) passes following the previous rekeying. By default, time-based rekeying is disabled (set to none); the range is 10 to 3,600.If you are configuring the HA1 control link with encryption in FIPS-CC mode, you must set a time interval within the range; you cannot leave it disabled.
- admin@PA-3250# set deviceconfig system ssh session-rekey ha packets 27Rekeying occurs after the defined number of packets (2n) are transmitted following the previous rekeying. Enter the exponent to which 2 is raised; for example, 14 configures that a maximum of 214 packets are transmitted before a rekeying occurs. The default is 228; the range is 12 to 27 (212 to 227). Alternatively, you can use the set deviceconfig system ssh session-rekey ha packets default command, which sets the value to 228.Choose rekeying parameters based on your type of traffic and network speeds (in addition to FIPS-CC requirements if they apply to you). Don’t set the parameters so low that they affect SSH performance.
- admin@PA-3250# commit
- admin@PA-3250# exit
- (HA1 Backup is configured) admin@PA-3250> request high-availability session-reestablish
- (No HA1 Backup is configured or HA1 Backup link
is down) admin@PA-3250> request high-availability session-reestablish forceYou can force the firewall to reestablish HA1 sessions if there is no HA1 backup, which causes a brief split-brain condition between the two HA peers. (Using the force option when an HA1 backup is configured has no effect.)
- admin@PA-3250> configure
- admin@PA-3250# show deviceconfig system ssh session-rekey ha
- (Optional) Set the SSH server to use the specified encryption
ciphers for the HA1 sessions.HA1 SSH allows all supported ciphers by default. When you set one or more ciphers, the SSH server advertises only those ciphers while connecting, and if the SSH client (HA peer) tries to connect using a different cipher, the server terminates the connection.
- admin@PA-3250> configure
- admin@PA-3250# set deviceconfig system ssh ciphers ha cipheraes128-cbc—AES 128-bit cipher with Cipher Block Chainingaes128-ctr—AES 128-bit cipher with Counter Modeaes128-gcm—AES 128-bit cipher with GCM (Galois/Counter Mode)aes192-cbc—AES 192-bit cipher with Cipher Block Chainingaes192-ctr—AES 192-bit cipher with Counter Modeaes256-cbc—AES 256-bit cipher with Cipher Block Chainingaes256-ctr—AES 256-bit cipher with Counter Modeaes256-gcm—AES 256-bit cipher with GCM
- admin@PA-3250# commit
- admin@PA-3250# exit
- (HA1 Backup is configured) admin@PA-3250> request high-availability session-reestablish
- (No HA1 Backup is configured or HA1 Backup link
is down) admin@PA-3250> request high-availability session-reestablish forceYou can force the firewall to reestablish HA1 sessions if there is no HA1 backup, which causes a brief split-brain condition between the HA peers. (Using the force option when an HA1 backup is configured has no effect.)
- admin@PA-3250> configure
- admin@PA-3250# show deviceconfig system ssh ciphers ha
- (Optional) Delete a cipher from the set of ciphers
you selected for SSH over the HA1 control link. This example deletes the AES CBC cipher with 128-bit key.
- admin@PA-3250PA-3250> configure
- admin@PA-3250PA-3250# delete deviceconfig system ssh ciphers ha aes128-cbc
- admin@PA-3250# commit
- admin@PA-3250# exit
- (HA1 Backup is configured) admin@PA-3250> request high-availability session-reestablish
- (No HA1 Backup is configured or HA1 Backup link
is down) admin@PA-3250> request high-availability session-reestablish forceYou can force the firewall to reestablish HA1 sessions if there is no HA1 backup, which causes a brief split-brain condition between the two HA peers. (Using the force option when an HA1 backup is configured has no effect.
- admin@PA-3250> configure
- admin@PA-3250# show deviceconfig system ssh ciphers ha
- (Optional) Set the session key exchange algorithm
for HA1 SSH.By default, the SSH server (HA firewall) advertises all the key exchange algorithms to the SSH client (HA peer firewall).If you are using an ECDSA default key type, the best practice is to use an ECDH key algorithm.
- admin@PA-3250> configure
- admin@PA-3250# set deviceconfig system ssh kex ha valuediffie-hellman-group14-sha1—Diffie-Hellman group 14 with SHA1 hashecdh-sha2-nistp256—Elliptic-Curve Diffie-Hellman over National Institute of Standards and Technology (NIST) P-256 with SHA2-256 hashecdh-sha2-nistp384—Elliptic-Curve Diffie-Hellman over NIST P-384 with SHA2-384 hashecdh-sha2-nistp521—Elliptic-Curve Diffie-Hellman over NIST P-521 with SHA2-521 hash
- admin@PA-3250# commit
- admin@PA-3250# exit
- (HA1 Backup is configured) admin@PA-3250> request high-availability session-reestablish
- (No HA1 Backup is configured or HA1 Backup link
is down) admin@PA-3250> request high-availability session-reestablish forceYou can force the firewall to reestablish HA1 sessions if there is no HA1 backup, which causes a brief split-brain condition between the two HA peers. (Using the force option when an HA1 backup is configured has no effect.
- (Optional) Set the message authentication code
(MAC) for HA1 SSH.By default, the server advertises all of the MAC algorithms to the client.
- admin@PA-3250> configure
- admin@PA-3250# set deviceconfig system ssh mac ha valuehmac-sha1—MAC with SHA1 cryptographic hashhmac-sha2-256—MAC with SHA2-256 cryptographic hashhmac-sha2-512—MAC with SHA2-512 cryptographic hash
- admin@PA-3250# commit
- admin@PA-3250# exit
- (HA1 Backup is configured) admin@PA-3250> request high-availability session-reestablish
- (No HA1 Backup is configured or HA1 Backup link
is down) admin@PA-3250> request high-availability session-reestablish forceYou can force the firewall to reestablish HA1 sessions if there is no HA1 backup, which causes a brief split-brain condition between the two HA peers. (Using the force option has no effect when an HA1 backup is configured
- Regenerate ECDSA or RSA host keys for HA1 SSH to replace
the existing keys, and reestablish HA1 sessions between HA peers
using the new keys without restarting the HA peers. The HA peers use the host keys to authenticate each other. This example regenerates the ECDSA 256 default host key.Regenerating a host key does not change your default host key type. To regenerate the default host key you are using, you must specify your default host key type and length when you regenerate. Regenerating a host key that isn’t your default host key type simply regenerates a key that you aren’t using and therefore has no effect.
- admin@PA-3250> configure
- admin@PA-3250# set deviceconfig system ssh regenerate-hostkeys ha key-type ECDSA key-length 256
- admin@PA-3250# commit
- admin@PA-3250# exit
- admin@PA-3250> request high-availability sync-to-remote ssh-keyAn HA connection must already be established between the HA firewalls. If the firewalls have not yet established an HA connection, you must enable encryption on the control link connection, export the HA key to a network location, and import the HA key on the peer. See Configure Active/Passive HA or Configure Active/Active HA.
- (HA1 Backup is configured) admin@PA-3250> request high-availability session-reestablish
- (No HA1 Backup is configured or HA1 Backup link
is down) admin@PA-3250> request high-availability session-reestablish forceYou can force the firewall to reestablish HA1 sessions if there is no HA1 backup, which causes a brief split-brain condition between the two HA peers. (Using the force option when an HA1 backup is configured has no effect.)