https://community.checkpoint.com/t5/Firewall-and-Security-Management/vsenv-00/m-p/175347#M31984 <P>I recall seeing post about this for R80.40, but not R81+, so I assume its fixed, but will let someone else confirm.</P> Mon, 20 Mar 2023 03:37:04 GMT the_rock 2023-03-20T03:37:04Z https://community.checkpoint.com/t5/Firewall-and-Security-Management/vsenv-00/m-p/175342#M31981 <P>I think have encountered a cosmetic bug in R80.40 VSX, wanted to confirm if it has been fixed before I log it with TAC.</P> <P>To reproduce:</P> <OL> <LI>Enter VS0 (must be done from vs0) <OL> <LI>vsenv</LI> </OL> </LI> <LI>Enter an invalid, all zero VS ID (more than one zero) <OL> <LI>vsenv 00</LI> <LI>Result is&nbsp;vsenv: operation failed, specified Virtual System ID does not exist.</LI> </OL> </LI> <LI>Try doing anything you would on a VSX gateway (fw, cphaprob, cpview, vsx, vsenv, cpconfig etc)<BR /> <OL> <LI>Results are varying forms of errors</LI> </OL> </LI> <LI>Source CPprofile <OL> <LI>. /opt/CPshrd-R80.40/tmp/.CPprofile.sh</LI> </OL> </LI> <LI>Back to normal</LI> </OL> <P>I've been able to reproduce this in up to HFA 156 and about to deploy take 192, can anyone confirm it affects R81?</P> Mon, 20 Mar 2023 03:16:06 GMT https://community.checkpoint.com/t5/Firewall-and-Security-Management/vsenv-00/m-p/175342#M31981 cosmos 2023-03-20T03:16:06Z https://community.checkpoint.com/t5/Firewall-and-Security-Management/vsenv-00/m-p/175347#M31984 <P>I recall seeing post about this for R80.40, but not R81+, so I assume its fixed, but will let someone else confirm.</P> Mon, 20 Mar 2023 03:37:04 GMT https://community.checkpoint.com/t5/Firewall-and-Security-Management/vsenv-00/m-p/175347#M31984 the_rock 2023-03-20T03:37:04Z