Performing sanity check of all hardware

Prerequisites

Ensure that the proxy is not set in the environment variables. To disable the proxy, run the following commands:

unset http_proxy
unset https_proxy

Procedure

Perform sanity check of a server.
1. Perform sanity check of a server using the following command:
```
nps sanity-check -c server
```
  The command provides the reachability status of the server using iLO IP address. The hardware preparation and image provisioning details of all the servers present in the uploaded input JSON is available.
2. Perform sanity check and get the BIOS details and RAID details for a given IP address of a server.
```
nps sanity-check -c server -ip <server_ip> -a <action>
```
  Supported actions are bios_details and raid_details.
Perform sanity check of a switch using the following command:
```
nps sanity-check -c switch -ip <switch_ip> --get <info> -nos <nos_type>
```
Supported info for nos as comware/cumulus are version, management_port, vlan_defaultgw, network_reachability, ha, and bridge_aggregation.

Supported info for nos as aruba are version, management_port, vlan_interfaces, network_reachability, ha, and bridge_aggregation.
NOTE:
- If nos is comware/cumulus, then sanity check must be performed only for data switches.
- If nos is aruba, then sanity check must be performed only on data and borderleaf switches.
- vlan_interfaces is supported only for Aruba borderleaf switches.
- If sanity check fails to get vlan_interfaces details from the borderleaf switch with error "Login failed: session limit reached.", then perform the following steps to clear the session limit.
  Log in to the borderleaf switch that was used in the failing sanity check CLI.
  
  Run https-server session close all and retry the CLI.
nos is the network operating system and the supported <nos_type> are comware, cumulus, and aruba.
The information selected from the supported information list for a given <switch_ip> and <nos_type> is displayed.