sk182665 - Snapshot schedule fails

Snapshot schedule fails

Product: Smart-1
Version: R81.20, R82
Last Modified: 2025-04-20

Solution

Snapshot schedule fails in these scenarios:

Remote server identity is not known by Gaia.

This usually means that this is the first time you connect to this server. If you trust this identity, add the server to known hosts using the command 'add ssh hba'. For more details, please refer to sk164234.

> set snapshot-scheduled settings snapshot-name-prefix Test_cli description Test_cli target scp path /home/admin/ ip <IP_address> username admin password <password>
> set snapshot-scheduled activation enabled
> set snapshot-scheduled recurrence monthly month 12 days 1 time 10:00

Validate the snapshot schedule:

> show snapshot-scheduled Scheduled snapshot configuration: Name: Test_cli Description: Test_cli Activation: enabled Target: scp Username: admin Ip: <IP_address> UploadPath: /home/admin/ Each January, February, March, April, May, June, July, August, September, October on day 11 at 19:43

> add ssh hba ipv4-address <IP_address> public-key access-mode standalone encoded-data <DATA>

You receive this error when you try to schedule a snapshot:

Remote server identity is not known by Gaia.

This usually means that this is the first time you connect to this server.

If you trust this identity, add the server to known hosts using the command 'add ssh hba'.

For more details, please refer to sk164234.

[DATE TIME] fw cgisu: After parse_and_verify_path(), we have: pname=/web/cgi-bin2/img_mgmt.tcl dname=/web/cgi-bin2

[DATE TIME] fw xpand[PID]: knownhost_cdk: Filename /home/admin/.ssh/known_hosts

[DATE TIME] fw xpand[PID]: knownhost_cdk: Total known hosts 9

[DATE TIME] fw xpand[PID]: knownhost_cdk: Invalid key data, not base64 encoded

> set snapshot-scheduled recurrence monthly month all days 11 time 19:43

Snapshot schedule failed. The snapshot will not be scheduled. NMSNAP0042 Please enter valid month value

> set snapshot-scheduled recurrence monthly month 1,2,3,4,5,6,7,8,9,10 days 11 time 19:43

Solution

This problem was fixed. The fix is included in:

If you choose not to upgrade, Check Point can supply a Hotfix. Contact Check Point Support to get a Hotfix for this issue.

A Support Engineer will make sure the Hotfix is compatible with your environment before providing the Hotfix.

For faster resolution and verification, please collect CPinfo files from the Security Management Server and Security Gateways involved in the case.

Hotfix installation instructions:

Refer to sk168597 - How to install a Hotfix.

NOTE

This solution has been verified for the specific scenario, described by the combination of Product, Version and Symptoms. It may not work in other scenarios.

Article Properties

Access Level: General
Status: Approved by TAC
Date Created: 2024-09-09
Last Modified: 2025-04-20