5.3.2.1.1. NetConf troubleshooting

In this section we can find the most common issues of ON NetConf executions:

5.3.2.1.1.1. No connection

In this case, the execution gives an error because there is no access to the Network Device. We will see an error as the following:

../../../../_images/netconf2.png


To solve that, we need to go to the network devices that are affected by this NetConf execution and check if their IP are correctly configured and we can access them from ON Principal.

../../../../_images/netconf3.png


We can see the logs in ON NetConf -> NetConf Log or looking the following file:

tail -f /var/log/opennac/opennac-job.log
../../../../_images/netconf5.png


5.3.2.1.1.2. No privileges

In this case, the execution gives an error because there are no privileges to connect to the Network Device that permits the device configuration. We will see an error as the following:

../../../../_images/netconf.png


To solve that, we need to go to the network devices that are affected by this NetConf execution and check if their Connection settings are correctly configured.

../../../../_images/netconf1.png


We can see the logs in ON NetConf -> NetConf Log or looking the following log file at ON Principal:

tail -f /var/log/opennac/opennac-job.log
../../../../_images/netconf6.png


5.3.2.1.1.3. Incompatible execution for Brand/Model

In this case, the execution don’t gives an error, but the message of the execution shows that the commands couldn’t be executed. We will see something like the following:

../../../../_images/netconf4.png


To solve that, we need to check the Brand and the Model and see if the commands executed corresponds to the Network Device in case. The principal problem is that the commands are not supported by the network device.