Unsupported content

 

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Known issues and workarounds in continuous compliance for networks

The following issues remain open in this release for the Continuous Compliance for Network Automation solution.

Known issues in the installation program and upgrades

Support ID

Tracking ID

Description

None

INSTALL-1364

The BMC Continuous Compliance for Networks Solution installation is not supported on 32-bit Linux platforms.

None

INSTALL-1273

When you create a change request (CR) with invalid assignment details in the task template, the following message is displayed:

The Assignment Information is not valid. Use the menus provided on the Assignee Company, Assignee, Organization and Assignee Group or the type ahead return function on the Assignee Group or Assignee fields fields to select this information.

Also, assignment issues occur for the following solutions:

  • Continuous Compliance for Databases
  • Continuous Compliance for Networks
  • Continuous Compliance for Servers
  • Triage and Remediation
  • NetApp Solutions

    Workaround: For detailed instructions, see Workarounds for Install-1273 in the BMC Atrium Orchestrator documentation.

None

INSTALL-1235

The BMC Atrium Orchestrator Content installer fails to install the BMC Continuous Compliance for Networks solution.

Workaround:

  1. Using an account with administrative privileges, log on to BMC Remedy Action Request System.
  2. In the Quick Links section, click AR System Administration Console.
  3. Click System > General > Server Information and click the Configuration tab.
  4. Select the Development Cache Mode and Enable Multiple Assign Groups check boxes.
  5. Click Apply.
  6. Install the Continuous Compliance for Networks solution.

None

INSTALL-1366

When you are installing a BSM Solution using the BMC Atrium Orchestrator Content installation program, the user does not get properly assigned in incident and task templates if a number (such as 1) exists in the user name.

Workaround:

In the Remedy Integration page of the BMC Atrium Orchestrator Content installation program, ensure that the User name field does not include a number.

Known issues in the run books

Support ID Tracking ID Description
None MODULE-3027

In the Continuous Compliance for Networks solution, the Emergency or No Impact change is automatically approved and the status is changed to  "Implementation in Progress" instead of "Scheduled".

Workaround:

  1. Navigate to the BMC Remedy AR System home page.
  2. In the Quick Links section, click Application Administration Console.
  3. Click the Custom Configuration tab and then select Foundation > Approval Process Configuration.
  4. Click Open.
  5. Search for "Network Automation - Emergency" Approval Process Configuration.
  6. Click the Status Flow tab, change Status for Approved phase from "Scheduled" to "Implementation In Progress" state.

    This enables the Save button.
  7. Restore to the original "Scheduled" status and click Save.
  8. Repeat steps 5 through 7 for "Network Automation - No Impact" Approval Process Configuration.
Was this page helpful? Yes No Submitting... Thank you

Comments