2A Server Configuration
Install the BlueCat LiveAssurance License
If you are running the POC version, you will receive a license from your Sales Executive. In the BlueCat LiveAssurance webUI, browse to and click the Upload License button to apply the license.
Users and Roles
Please refer to Part 6 of the BlueCat LiveAssurance User Guide (Part 6: Settings) for the information required to manage users and role-based access.
Email Notification / SMTP Integrations
Please refer to Part 6 of the BlueCat LiveAssurance User Guide (Part 6: Settings) for the information required to integrate with your email system.
2B Connect Devices for Inspection
Create Credential Sets
The first step to inspecting your devices is to create the credential set - the login credentials that will be used to query the devices.
The credentials also include the subnet which will use those credentials. If all of your devices are using the same credentials, you can simply set this to 0.0.0.0/0 to have it apply to all devices. Otherwise, if your devices use different credentials, you can create multiple credential sets, and then specify the network and mask for each (which can be an exact IP address such as 94.94.94.17/32 or a subnet such as 94.94.0.0/16.)
If there are overlapping Subnets (such as 94.94.94.17/32 and 94.94.0.0/16), the BlueCat LiveAssurance server will try to connect using the most specific subnet. If those credentials fail, it will then try the next most specific subnet. In our example, the /32 subnet would be tried first and then the /16 subnet.
Add Devices
Next, you can add the devices you want to inspect. You just have to provide a name for the device and the IP address. BlueCat LiveAssurance will interrogate the device (using the credential sets you have created) to determine the device vendor, OS, etc.
If the BlueCat LiveAssurance server is unable to communicate with the device, it will return an error. The most common reasons for a communication issue are:
- An issue with the credentials - either
- You have mis-typed the username/password in the Credential Set
- The device’s IP Address is not in the subnet(s) assigned to the Credential Set
- Those credentials don’t exist on that device or don’t have the correct permissions
- Connectivity issues between the device and the BlueCat LiveAssurance server.
This could be
- Basic connectivity between BlueCat LiveAssurance server and device. The easiest way to test this is to logon directly to the BlueCat LiveAssurance server’s Linux interface and ping the device.
- SSH connectivity between the BlueCat LiveAssurance server and the device. Validate that SSH is enabled on the device using port 22.
BlueCat LiveAssurance queries the firewalls on a scheduled basis, varying from every minute to every day depending on the data being retrieved. You should therefore begin to see Alerts within a few minutes.
Further information about adding credentials and devices can be found in the User Guide at: Part 5: Device Management