Skip to main content

volume flexcache config-refresh

Refresh FlexCache configuration for a peer volume

Availability: This command is available to cluster administrators at the advanced privilege level.

Description​

The volume flexcache config-refresh command is used to refresh the FlexCache configuration. It can be used to update the configuration on either the FlexCache or origin of a FlexCache cluster. This command only needs to be run if the automatic refresh failed and the corresponding EMS was generated.

Note
This command must be run on the peer cluster. For example, refresh of origin of a FlexCache volume must be run from the FlexCache cluster. Refresh a FlexCache volume must be run from the of an origin of a FlexCache cluster.

Parameters​

-peer-vserver <vserver name> - Peer Vserver
Name of the Vserver for which the configuration is being refreshed.
-peer-volume <volume name> - Peer Volume
Name of the volume for which the configuration is being refreshed.
-peer-endpoint-type {cache|origin} - Origin/Cache Volume
The peer-endpoint-type specifies the FlexCache endpoint type of the peer volume. Possible values are cache for FlexCache volumes and origin for origin of a FlexCache volumes.

Examples​

The following example triggers config-refresh on origin of a FlexCache volume "origin1". 

cluster1::> flexcache config-refresh -peer-vserver vs34 -peer-volume origin1 -peer-endpoint-type origin
        (volume flexcache config-refresh)

The following example triggers config-refresh on FlexCache volume "fc1".

cluster1::> flexcache config-refresh -peer-vserver vs34 -peer-volume fc1 -peer-endpoint-type cache
        (volume flexcache config-refresh)

The following example triggers config-refresh on FlexCache volume "fc1" with an incorrect peer-endpoint-type.

cluster1::> flexcache config-refresh -peer-vserver vs34 -peer-volume fc1 -peer-endpoint-type origin
            (volume flexcache config-refresh)

            Error: command failed: Failed to store the configuration for peer volume "fc1"
                   in Vserver "vs34" on cluster "cluster1". Check the FlexCache
                   configuration on the local cluster and retry the operation.