The Manager provides an option to generate and store the signature set and/or device image file on an application directory. You can export the generated file to a directory or a CD, manually ship the CD to a remote location, and then use a TFTP server to transfer the file onto the device.
You can select the device deployment mechanism while adding a new device. By default, all devices added to the Manager have the deployment mode as Direct. Devices with Direct mode have the signature set/software directly pushed to the devices as it has been done in the past. Devices for which you want the signature set/software to be manually pushed can be done by selecting the update mode as Indirect. If required, you can edit the deployment mode later.
Follow this procedure to configure a new device for Indirect update:
Steps:
Go to → → → .
The Device Manager page is displayed.
Select the Sensors tab and click
.png "GUID-0208387A-BF4A-410F-9CFB-52AE08321E35-low.png")
.The Add Device - Step 1 of 2 panel is displayed.
Enter a device name against Name.
Provide Shared Secret details.
Confirm the Confirm Shared Secret details.
Select IPS Sensor against Device Type drop-down.
Select Indirect against Deployment Mode drop-down and click Save.
Add Device - Step 1 of 2 window.jpg "GUID-A35DD220-0636-4E2D-8FB9-C5FCA1843FA6-low.jpg")
The device is configured for Indirect updates.
Note
The Deployment Mode configured on the Primary device of the Fail-Over Pair determines the signature file generation for download.
Note
If the Deployment Mode for the Primary device is configured as Indirect, two individual signature files are generated for Primary and Secondary devices, irrespective of the Secondary device configuration.
Note
If the Deployment Mode for the Primary device is configured as Direct, the signature file is downloaded Direct to both the devices, irrespective of the Secondary device configuration.