Commit error: Server error : vsys -> vsys1 constraints failed : Maximum number of virtual systems reached

Reply
Highlighted
L4 Transporter

Commit error: Server error : vsys -> vsys1 constraints failed : Maximum number of virtual systems reached

Hi All,.

while give the commit,..What is this error,.?

Server error : vsys -> vsys1 constraints failed : Maximum number of virtual systems reached

Even i have not enabled vsys capability.

Regards,

Gururaj


Accepted Solutions
Highlighted
L6 Presenter

Trying reverting back to running configuration from the Web-UI ( Setup tab -->operations --rever to running config )or CLi and try doing the commit force from the cli using the command "commit force" from the configuration mode. The subsequent changes should be committed with out any issues. Let us know if that fixes.

Thanks,
Sandeep T

View solution in original post


All Replies
Highlighted
L6 Presenter

Trying reverting back to running configuration from the Web-UI ( Setup tab -->operations --rever to running config )or CLi and try doing the commit force from the cli using the command "commit force" from the configuration mode. The subsequent changes should be committed with out any issues. Let us know if that fixes.

Thanks,
Sandeep T

View solution in original post

Highlighted
L4 Transporter

Yes that solved my problem. but i dont know why this commit failed was caused......When i received the error i saw the object, apps ggroups, etc in the web interface although in the CLI yes.

Why this was caused??? a bug??

THANKS

Highlighted
L6 Presenter

A glitch in the matrix? ;-)

L1 Bithead

I had the same issue- I opened a case with support.

I had just upgraded from 4.1.11 to 4.1.13-

The commit force did not work for me, I would get the same error.

I loaded/reverted to my running configuration, performed a commit and then made my configuration changes again.  In this case I was removing a static route.

This took care of the issue for me, but I would still consider this a bug.

Message was edited by: Shaun Dyer

Highlighted
L0 Member

I had this when installing new device (5.06) with multi sys enabled. A reboot (which is basicaly the same as mentioned above) solved my problem.

Regards Vincent

Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the Live Community as a whole!

The Live Community thanks you for your participation!