4.1.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. You can find a detailed explanation of the deployment of each of the nodes in Deployment and basic configuration
Configuration
ON Analytics Configuration: On analytics is the node that is responsible for managing OpenNAC Enterprise data. Since Visibility relies primarily on data collected from the network, it’s important to configure this node correctly.
Network Device Configuration: Most sources of Visibility involve configuration by network devices to provide the information to OpenNAC Enterprise. These can be the configuration of a Port Span, SNMP Traps, DHCP Relay, etc.
Optional:
ON Sensor Configuration: If our use case includes the deployment of ON Sensor nodes that allow us to sniff the network traffic, it will be necessary to perform the correct configuration of these nodes.
Administration
Visibility Policies: These help us regulate network visibility events and the actions to be taken (post-conditions), such as running plugins to improve profiling.
Optional:
Profiling Rules: Profiling is a key point in the visibility use case. This will give us information about what we have connected to the network. If we want to improve and adjust the profiling to the maximum, we will likely need to create some custom rules.
Business Profiles Creation: In a network where visibility is being done, a lot of information is collected, and a large number of devices are discovered. To have everything well organized in the system, it might be interesting to create several business profiles.
Plugins Configuration: Visibility plugins run against network devices and allow us to get more accurate information about them. More information about a device indicates greater accuracy when profiling it.
SNMP Traps Configuration: In the case of using SNMP Traps to discover new devices, it will be necessary to activate this functionality in the administration panel.
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 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
Troubleshooting: The first time the use case is tested after deployment, some problems may appear. In this section, we will see how to analyze them and look for possible failures to correct them. If any of the problems that may appear can be found in the Platform Administration -> Troubleshooting guide.