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

# sk166372 - 'cpstat vsx' command not working after an upgrade

| Property | Value |
|----------|-------|
| Solution ID | sk166372 |
| Date Created | 2020-04-17 |
| Last Modified | 2022-01-26 |
| Technical Level | General |
| Products | Security Gateway |
| Versions | R82.10, R82, R81.20 |
| OS | Gaia |

## Symptoms

- 'cpstat vsx -f stat' command displays mismatch value after VSX upgrade, for example:  
`
[Expert@vsxa-v:0]# cpstat vsx -f stat`  
`
Request-Reply mismatch:Request type = Unsigned, 32 bit, Reply type = Integer, 32 bit
`

## Cause

During the upgrade process from R77.10 to R80.20 the vsx.cps file is not updated. Because this file is not updated with the proper syntax changes it is not able to poll, parse, and display the command output correctly.

## Solution

[Contact Check Point Support](https://www.checkpoint.com/support-services/contact-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](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk92739) files from the Security Management and Security Gateways involved in the case.  

In case for some reason you cannot install the hotfix, you can replace the file manually:

Copy vsx.cps file from a working or fresh install of R80.20 VSX deployment.

1. Validate the md5sum of the file on the broken output device.

   **`#md5sum $FWDIR/conf/vsx.cps`**

   Example:

   **`[Expert@VSX-243:0]# md5sum $FWDIR/conf/vsx.cps`
   `e5b602dbb9ec5e414b416258e6107ae0 /opt/CPsuite-R80.20/fw1/conf/vsx.cps`**
2. Validate md5sum of file on working R80.20 VSX system

   **`#md5sum $FWDIR/conf/vsx.cps`**

   Example

   **`[Expert@VSX-244:0]# md5sum $FWDIR/conf/vsx.cps`
   `e12f7da8792bbc3333a64bc3f8d01d08 /opt/CPsuite-R80.20/fw1/conf/vsx.cps`**
3. Notice the differences in the md5sum. The value in step 1 is the carry over from the 77.10 deployment. The value in step 2 is the correct value/file for the R80.20 deployment.

4. Create a copy of the working file from the working environment and verify md5sum:

   **`#cp $FWDIR/conf/vsx.cps /home/admin/vsx.cps_orig`**

   Example

   **`[Expert@VSX-244:0]# cp $FWDIR/conf/vsx.cps /home/admin/vsx.cps_orig`
   `[Expert@VSX-244:0]# md5sum /home/admin/vsx.cps_orig`
   `
   e12f7da8792bbc3333a64bc3f8d01d08 /home/admin/vsx.cps_orig`**
5. Transfer file from working device to non working device into the /home/admin directory.

6. Copy new file into existing non working file

   **`#cp /home/admin/vsx.cps_orig $FWDIR/conf/vsx.cps`**
7. Verify new md5sum: **`[Expert@VSX-243:0]#md5sum $FWDIR/conf/vsx.cps`
   `e12f7da8792bbc3333a64bc3f8d01d08 /opt/CPsuite-R80.20/fw1/conf/vsx.cps`**

8. Verify command output works correctly:

   Example

   **`[Expert@VSX-243:0]# cpstat vsx -f stat`**

   Virtual Devices  
   --------------------------------------------------------------  
   \|ID\|Type \|Name \|Policy \|SIC stat \|  
   --------------------------------------------------------------  
   \| 0\|VSX Gateway \|VSX-243 \|VSX_VSLS_VSX \|Trust established\|  
   \| 1\|Virtual Switch\|EXT_VSW \|InitialPolicy \|Trust established\|  
   \| 2\|Virtual System\|VS_USA \|Standard \|Trust established\|  
   \| 3\|Virtual System\|VS_Texas \|Standard \|Trust established\|  
   \| 4\|Virtual System\|VS_Seattle\|Standard \|Trust established\|  
   --------------------------------------------------------------

---

# 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