NPS VM does not start up if NPS host is rebooted

Symptom

NPS VM does not start up if NPS host is rebooted.

Action

Log in to the NPS toolkit host using valid credentials.
Navigate to the path where the vagrant file is located.
```
cd /<sync_folder>/nps
```
To check the status of the NPS toolkit VM, run the following command:
```
source source.rc
vagrant status
```
If the status is displayed as poweroff, run the following command to bring up the NPS toolkit VM:
```
vagrant up
```
To check the status of the NPS toolkit VM, rerun the following command:
```
vagrant status
```
Once the status is displayed as running, log in to the NPS toolkit VM from outside the NPS toolkit host using the OAM IP.
NOTE:
If the NPS toolkit VM is not accessible from outside the NPS toolkit host using the OAM IP, login/ssh to the NPS toolkit VM from NPS toolkit host and delete the default route created with NAT network.
1. To check the routes configured on the NPS toolkit VM, run the following command:
  route -n
2. To delete the route created with NAT network, run the following command:
  route del -net 0.0.0.0 gw <gateway_ip_for_NAT_network>
Log in to the NPS toolkit VM and wait for a few minutes for the Kubernetes service to come up.
To check the status of all the Pods, run the following commands:
```
kubectl get nodes -n nps
kubectl get pods --all-namespaces
```
NOTE:
All Pods must be in Running state.