Troubleshooting

7 Troubleshooting

Following are the fixes for the common issues:

To check status of named process, run the following command:
```
sudo service named status
```
In case the named process is down, it can be started manually by performing the following command:
```
 sudo service named start
```
To check status of DNDIST process, run the following command:
```
sudo service dnsdist status
```
If loadbalancer is set to "Yes", but dnsdist process is down, it can be started manually by performing the following command:
```
sudo service dnsdist start
```
Alarm 70902 (ENUM MP CPU Overload) and Alarm 70903 (ENUM MP HDD full) are raised on basis of the measurement values from SysMetric. These can be referred by running the following command:
```
sysmetric -W
```
In the event of restart, alerts are generated for the NS records. To clear alarms, these records must be deleted and then re-added.
If loadbalancer is set to "Yes" and the IMI IP is down, the query response time increases and queries will get timed out.
To recover from congestion, traffic must be reduced to below 5k TPS.
In case of any issues with replication of DNS records or zones, restart the vENUM MP so that replication can resume.
In case of the error scenarios, the ENUM measurements are pegged. For information related to ENUM measurements, see Oracle Communications Measurements guide.