4.4.2.2. Deployment Steps

To ensure that the use case that we are deploying works correctly, it is necessary to carefully follow the steps we indicate. These may change depending on the requirements and needs in our case.

The mandatory and optional steps are detailed below. Remember it will depend on your specific case.

Architecture

  • Architecture: The first step is the deployment of the nodes needed for this use case. Here we will find the necessary information related to the architecture of the use case. A detailed explanation of the deployment of each one of the nodes will be found in Deployment and basic configuration

Administration

  • Define the Compliance Rules: Rules are the main driver of the Network Device Compliance use case. these define compliance with network device configurations.

  • Define the Compliance Tests: The Tests are groups of rules, these Tests can have different behaviors depending on their configuration.

  • Define the Compliance Tests: Through the test grouping we will create the groups, which will be the ones that will be defined to execute against the Network Devices.

  • Create Net Dev: With the creation of Network Devices in the CMDB we will define the connection properties of each of the devices so that OpenNAC Enterprise can retrieve the configuration information and perform compliance verification.

  • Schedule & run the compliance: The compliance tests can be executed in a specific or planned way, here we will define the period of execution of said compliance tests.

Optional:

  • Compliance Simulation: Once the compliance tests have been created, it is possible to perform simulations through the static configuration files of the network devices. This allows us to quickly verify the configuration of the tests created.

  • Bulk import of devices (client info): If we have a file with the data of the network devices in XML or JSON format compatible with OpenNAC, it is possible to import all of them at once.

Operation

  • Operation : In this step, we will start operating the use case and checking that all the functionalities are working as expected. If we find some unexpected behavior we can go to the troubleshooting step in order to find and fix the issue.

Monitoring

  • Monitoring : At this point we will see how the data is being ingested and saved in ON Analytics. To check this, we can open the different visualizations available for this use case.

Troubleshooting