Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

Why was I able to deploy successfully to a CNS-managed PIX device the first time, but subsequent deployments were unsuccessful?

April 26, 2017able deploy deployments device Pix successfully time unsuccessful

0

Posted

Why was I able to deploy successfully to a CNS-managed PIX device the first time, but subsequent deployments were unsuccessful?

1 Answer

0

Posted

A. This can happen if the configuration pushed during the first deployment contains incorrect CLI commands for the auto-update feature. Check the following: –Make sure the username and password of the CNS server is defined correctly in the auto-update command. –Make sure that you have defined a FlexConfig that contains the necessary name commands. A FlexConfig is necessary because Security Manager 3.1 does not support this command directly. As a result, even though the command was discovered, it does not appear in the full configuration.