dslreports logo
 
    All Forums Hot Topics Gallery
spc
Search similar:


uniqs
3053
RonR
join:2003-10-10
Ash Flat, AR

RonR

Member

Provisioning Utility for OBi100/110/200/202/300/302


Screenshot
OBiProv.zip
1,003,365 bytes
Archive
  
OBiProv.exe is a Windows program intended to greatly simplify the steps needed for the provisioning of OBi100, OBi110, OBi200, OBi202, OBi300, and OBi302 devices. Provisioning is a process whereby the devices pull their configuration from a host server at initial startup (and optionally periodically thereafer).

OBiProv compresses all XML files using GZIP and optionally encrypts them using AES or RC4 algorithms.

While either an HTTP or TFTP server may be used, TFTP is used by OBiProv due to its simplicity of installation and ease of use. The steps required to provide provisioning support are:

1. Install a TFTP server if not already present. Two possible sources are:

»tftpd32.jounin.net/

»www.solarwinds.com/produ ··· ver.aspx

2. Create a backup of the target device at:

System Management -> Device Update -> Backup Configuration

'Use OBi Version' must be checked.

Passwords and PINs are not included in the backup file created.

3. Run OBiProv. Enter the TFTP server IP address or hostname. Select a previously created backup file. Enter the applicable passwords and PINs to be added to the provisioning file.

4. Select File -> Output $DM Files. This will create the following files:

OBi100.xml, OBi110.xml, OBi200.xml, OBi202.xml, OB300.xml, OBi302.xml

These files will need to be recreated only if the TFTP server or the
encryption keys are changed.

5. Select File -> Output XML File(s). This will create the provisioning file(s) from the selected backup file. For example, if the selected backup file is backup9CADEF123456.xml, the provisioning file(s) will be:

9CADEF123456-1.xml
9CADEF123456-2.xml (if AES/RC4 encryption was used)

The original backup file will not be altered.

6. Copy the following files into the TFTP server's root directory:

OBi100.xml, OBi110.xml, OBi200.xml, OBi202.xml, OB300.xml, OBi302.xml
9CADEF123456-1.xml
9CADEF123456-2.xml (if AES/RC4 encryption was used)

7. If your router supports DHCP Option 66 (as does those running third party firmware such as Tomato or DD-WRT), enter the following Dnsmasq Custom configuration entry:

dhcp-option=66,"192.168.1.150"

Use the actual IP address of your TFTP server in place of 192.168.1.150.

Provisioning will now be fully automatic, even following a factory reset.

If your router does not support DHCP Option 66 , you will need to set the OBi100, OBi110, OBi200, OBi202, OBi300, and OBi302 devices as follows:

System Management -> Auto Provisioning -> ITSP Provisioning -> ConfigURL

tftp://192.168.1.150/$DM.xml

Use the actual IP address of your TFTP server in place of 192.168.1.150.

This setting will need to be re-entered only if the device is factory reset.

In all cases, set:

System Management -> Auto Provisioning -> ITSP Provisioning -> Method

System Start

8. Reboot the OBi100, OBi110, OBi200, OBi202, OBi300, or OBi302 device.

You should see the TFTP server deliver the appropriate OBi100.xml,
OBi110.xml, OBi200.xml , OBi202.xml , OBi300.xml , or OBi302.xml file followed by 9CADEF123456-1.xml and 9CADEF123456-2.xml (if AES/RC4 encryption was used) after an intervening reboot.

To encrypt the provisioning file, enter an AES or RC4 key in the 'K' field of OBiProv. AES encrytion also requires an entry in the 'iv' field. Both values must be 32 characters long consisting only of hex digits (0-9 and A-F). If both the 'K' and 'iv' fields are populated, AES encrytpion is used. If only the 'K' field is populated, RC4 encryption is used. If both fields are left blank, no
encryption is used.

If the Method field of OBiProv is set to System Start, the target device will only retrieve its provisioning file when the device is rebooted. If Method is set to Periodically and an Interval (in seconds) is specifed, the target device will periodically check the provisioning file and deploy any changes found the next time the device is idle. If Method is set to Disabled, the device will be provisioned only once. To allow further device provisioning, it will be necessary to set:

System Management -> Auto Provisioning -> ITSP Provisioning -> Method

System Start

File -> Output Text File creates a file that lists all parameters generated by OBiProv.

OBiProv configurations may be saved with File -> Export Configuration and restored with File -> Import Configuration.

If OBiProv is executed with a command line option of a configuration filename (for example: OBiProv.exe OBiProv.cfg), the specified configuration file will be loaded at startup.

The following files must be in the same folder as OBiProv.exe:

gzip.exe
libeay32.dll
obcrypt.exe
openssl.exe
ssleay32.dll

Nothing is installed and no modifications are made to Windows by running OBiProv.exe.
Expand your moderator at work