Contents

Introduction

Products Affected

Related CDETS and SR

Symptoms

Solution

Change Description

Workaround / Recovery Method

Root Cause Analysis

Introduction

This document describes information on a cosmetic issue related to a behavior change in the CLI output of filesystem synchronize command outputs.

Products Affected

Any ASR5500 or VPC-DI platform can be affected.

Related CDETS and SR

Cisco bug ID CSCwi07618 : upgrade rsync

Cisco bug ID CSCwk56061 : Documentation to update the behavior change for filesystem synchronize command outputs.

Symptoms

There is an issue related to a behavior change in the CLI output of filesystem synchronize command seen in StarOS Rel 21.28.m23 and 21.28.mh14 or later. This can cause some questions as to which files are to be updated when synchronizing files or checking before synchronizing files (check only) between management (MIO or CF) cards on the GW. This is a cosmetic change only and does not affect the filesystem synchronization functionality.

Example:

show version

filesystem synchronize /flash checkonly

filesystem synchronize /flash

With the 21.28.x release (Both vPGW VPC-DI Hermes and ASR5500 - 21.28.mh14 and 21.28.m23 or later) this change in behavior can be observed when running the filesystem synchronize commands.

The past behavior states “No files to update” when all files are synchronized between management cards (MIO or CF). It also lists only the files to be updated but does not list all the files that have already been updated. Output can be observed with or without the /flash or all option.

Example:

[local]ASR5500# show version

Wednesday February 12 17:23:36 UTC 2025

Active Software:

Image Version:                  21.26.25

Image Build Number:             90634

Image Description:              Deployment_Build

Image Date:                     Mon Jul 17 19:52:57 EDT 2023

Boot Image:                     /flash/sftp/asr5500-21.26.25.90634.Production.ER.bin

Source Commit ID:               add2fbdb36283a20938771a297d169132e82f0b4

[local]ASR5500# filesystem synchronize /flash checkonly

Wednesday February 12 17:50:01 UTC 2025

1 to be updated on card 6

/flash/sftp/testfile.txt

[local]ASR5500# filesystem synchronize /flash

Wednesday February 12 17:51:20 UTC 2025

1 to be updated on card 6

/flash/sftp/testfile.txt

Are you sure? [Yes|No]: yes

Wednesday February 12 17:51:29 UTC 2025

Updating /flash/sftp/testfile.txt

********************************************************************************

1 updated on card 6

/flash/sftp/testfile.txt

[local]ASR5500# filesystem synchronize /flash checkonly

Wednesday February 12 17:51:37 UTC 2025

No files to update

Now, post rsync upgrade in 21.28.x, lists the files, to be updated on card x, but also ALL the files on the card that are already synchronized and adds (but are newer), and then lists all the files:

[local]ASR5500# filesystem synchronize checkonly

Thursday January 23 17:27:28 UTC 2025

2 to be updated on card 6

/flash/sftp/crash-ASR5500-crash-02-02-25914-6791ef21-core

/flash/sftp/crash-ASR5500-crash-03-00-41201-67916861-core

800 to be updated (but are newer) on card 6

/flash/.engineInfo

/flash/.users

/flash/._.Trashes

..

/flash/sftp/failed_ssd/support_summary_7upqOb.gz

/flash/sftp/failed_ssd/support_summary_k6qkOo.gz

An additional example from the CLI Reference Guide – filesystem synchronize (link provided in Fix section).

You must confirm the synchronization before it is initiated. Here is a command output example:

Note: A file named testfile is created to show the behavior.

[local]QVPC-DI# show version verbose

Active Software:

Image Version:                  21.28.m23.93622

Image Build Number:             93622

[local]QVPC-DI# filesystem synchronize /flash checkonly

2 to be updated (but are newer) on card 2

/flash/module.sys

/flash/staros.bin

[local]QVPC-DI#

[local]QVPC-DI# filesystem synchronize /flash checkonly

1 to be updated on card 2

/flash/testfile

2 to be updated (but are newer) on card 2

/flash/module.sys

/flash/staros.bin

[local]QVPC-DI# filesystem synchronize /flash

1 to be updated on card 2

/flash/testfile

2 to be updated (but are newer) on card 2

/flash/module.sys

/flash/staros.bin

Updating /flash/testfile

********************************************************************************

1 updated on card 2

/flash/testfile

[local]QVPC-DI# filesystem synchronize /flash checkonly

3 to be updated (but are newer) on card 2

/flash/module.sys

/flash/staros.bin

/flash/testfile

qvpc-di:card2-cpu0# cd /flash

qvpc-di:card2-cpu0# ls -lrth

total 200M

-rw-rw-r--    1 root     root      195.9M Apr 28 08:17 staros.bin

-rw-rw-r--    1 root     root         134 Apr 28 08:17 boot.sys

drwxrwxr-x    2 root     root        4.0K Jun  4 06:13 sftp

drwxrwxr-x    2 root     root        4.0K Jun  4 06:13 persistdump

-rw-rw-r--    1 root     root         156 Jun  4 06:13 module.sys

drwxrwxr-x    2 root     root        4.0K Jun  4 06:13 crsh2

-rw-rw-r--    1 root     root        3.7M Jun  4 06:13 crashlog2

drwxrwxr-x    3 root     root        4.0K Jun  4 06:14 patch

-rw-rw-r--    1 root     root          79 Jun  4 06:14 restart_file_cntr.txt

-rw-rw-r--    1 root     root          17 Jun  4 06:22 testfile

qvpc-di:card2-cpu0# cat testfile

staros 21.28.m23

Solution

This issue is understood by Cisco and documentation has been updated to reflect the new behavior.

Cisco bug ID CSCwk56061 - Documentation to update the behavior change for filesystem synchronize command outputs.

Change Description

Book: Command Line Interface Reference Modes E-F

Chapter: Exec Mode Commands (D-S)

Topic:filesystem synchronize

Details: Added the command output example after the Usage Guidelines.

URL:  Command Line Interface Reference, Modes E - F, StarOS Release 21.28

Workaround / Recovery Method

No workaround for this issue is required as this is a cosmetic change and not a change in functionality.

Root Cause Analysis

Changed output of the command, filesystem synchronize /flash checkonly, which is introduced from 21.28.m23 / 21.28.mh14 due to rsync package upgrade Cisco bug ID CSCwi07618.