> Source: [sk160832](https://support.checkpoint.com/results/sk/sk160832)

# sk160832 - The vsx_util vsls commands fails to change the VSs priority

| Property | Value |
|----------|-------|
| Solution ID | sk160832 |
| Date Created | 2019-08-19 |
| Last Modified | 2020-10-13 |
| Technical Level | Advanced |
| Products | Security Gateway |
| Versions | R82.10, R82, R81.20 |

## Symptoms

- * The VSs priority change by vsx_util vsls commands succeeded although the priority did not change.
* The policy installation succeeded during the configuration push.

## Cause

The issue concerns the cluster policy not being installed as part of vsx_util vsls redistribute operation (changing priority for example).

The reason that cluster policy wasn't installed is because the policy ID didn't change.

When vsx_util vsls sent the policy installation request, policy was indeed installed on the GW but cluster policy installation wasn't invoked due to the similar policy ID.

## Solution

This solution requires authentication. Please log in to view the full solution.

---

# Agent Instructions

This content is from the Check Point Support Center (https://support.checkpoint.com), the official knowledge base for Check Point cybersecurity products.

## Navigating This Knowledge Base

- **Complete index**: [llms.txt](https://support.checkpoint.com/llms.txt)
- **All SK articles**: [SecureKnowledge Sitemap](https://support.checkpoint.com/sitemaps/secureknowledge-sitemap-index.xml)
- **SK article URL pattern**: `https://support.checkpoint.com/results/sk/{skId}`
- **Markdown responses**: AI bot User-Agents automatically receive `text/markdown` content